3GPP2 N.S0028
Version 1.0.0
Version Date: April 2002

N.S0028-0
(This page is intentionally left blank)

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

N.S0028-0
1
2
3
0
A
A
B
B
March 2001
May 2001
June 2001
July 2001
March 2002
0
1
3
5
Post Ballot version with ballot comments
Version 0- Addition of GPRS in GSM Foreign Mode
Version 1 – Editorial Changes
Version 3: Addition of CDMA/GSM two way roaming
Version V&V: Addition of CDMA/GSM two way and one roaming
4
5
Version 1 ii

N.S0028-0
1
2
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
10
11
12
13
1
14
15
16
17
2
3
Introduction.....................................................................................................................
1
1.1 General ..............................................................................................................
1
1.2
Purpose..............................................................................................................
1
1.3
Scope.................................................................................................................
1
1.4 Organization.......................................................................................................
1
References .....................................................................................................................
3
Definitions and Acronyms................................................................................................
4
3.1
Definitions ..........................................................................................................
4
3.2
Acronyms ...........................................................................................................
6
18 4 Overview of Internetwork Roaming..................................................................................
8
19
20
21
22
23
24
25
26
5 IIF Reference Model and Description...............................................................................
9
5.1
Reference Model ................................................................................................
9
5.2
Description .........................................................................................................
9
5.2.1
Provisioned Subscriber Data ...............................................................
10
Version 1
5.3
Interworking for Network Interfaces...................................................................
11
5.3.1
HLR - VLR Interface............................................................................
12
5.3.2
Originating / Gateway MSC - Serving MSC Interface............................
13
5.3.3
MC / SMS-SC - Serving MSC Interface ...............................................
14 iii

18 2
19
20
21
3
22 4
23
24
25
26
5
1
2
3
4
5
6
N.S0028-0
5.3.4
HLR – SGSN Interface.........................................................................
16
5.4
IIF Implementation Alternatives.........................................................................
16
5.4.1
IIF Resides within a GSM Network Entity..............................................
17
5.4.2
IIF Resides within ANSI-41 Network Entity ...........................................
17
5.4.3
IIF Resides within External Network Element........................................
18
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
14
15
16
17
1 Introduction.....................................................................................................................1
1.1 General ..............................................................................................................1
1.2
Purpose..............................................................................................................1
1.3
Scope.................................................................................................................1
1.4 Organization.......................................................................................................1
References .....................................................................................................................2
Definitions and Acronyms................................................................................................3
3.1
Definitions ..........................................................................................................3
3.2
Acronyms ...........................................................................................................4
Overview of Internetwork Roaming..................................................................................6
IIF Reference Model and Description...............................................................................7
5.1
Reference Model ................................................................................................7
5.2
Description .........................................................................................................7
5.2.1
Provisioned Subscriber Data .................................................................7
Version 1 iv

5
6
7
8
9
10
11
3
4
1
2
N.S0028-0
5.3
Interworking for Network Interfaces.....................................................................8
5.3.1
HLR - VLR Interface..............................................................................8
5.3.2
Originating / Gateway MSC - Serving MSC Interface............................10
5.3.3
MC / SMS-SC - Serving MSC Interface ...............................................10
5.4
IIF Implementation Alternatives.........................................................................12
5.4.1
IIF Resides within a GSM Network Entity..............................................12
5.4.2
IIF Resides within ANSI-41 Network Entity ...........................................12
5.4.3
IIF Resides within External Network Element........................................13
5.4.4
IIF Resides within Both ANSI-41 and GSM Network Entities.................13
Version 1 v

1
2
3
4
5
There are no tables in this volume.
N.S0028-0
Version 1 vi

N.S0028-0
1
2
10
11
12
13
14
15
3
6
7
4
5
8
9
16
17
18
19
20
21
22
Figure 1: IIF Reference Model ...................................................................................................
9
Figure 2: HLR - VLR Interface...................................................................................................
12
Figure 3: Originating / Gateway MSC - Serving MSC Interface..................................................
14
Figure 4: MC / SMS-SC - Serving MSC Interface ......................................................................
15
Figure 5: HLR- SGSN Interface.................................................................................................
16
Figure 6: IIF Resides within GSM Network Element ..................................................................
17
Figure 7: IIF Resides within ANSI-41 Network Element .............................................................
17
Figure 8: IIF Resides within External Network Element .............................................................
18
Figure 9: IIF Resides within both ANSI-41 and GSM Network Elements ....................................
18
Figure 1: IIF Reference Model ................................................................................................... 7
Figure 2: HLR - VLR Interface.................................................................................................... 9
Figure 3: Originating / Gateway MSC - Serving MSC Interface..................................................10
Figure 4: MC / SMS-SC - Serving MSC Interface ......................................................................11
Figure 5: IIF Resides within GSM Network Element ..................................................................12
Figure 6: IIF Resides within ANSI-41 Network Element .............................................................12
Figure 7: IIF Resides within External Network Element .............................................................13
Figure 8: IIF Resides within both ANSI-41 and GSM Network Elements ....................................13
Version 1 vii

N.S0028-0
1
2
11
12
13
14
15
16
17
18
19
20
3
4
5
6
7
8
9
10
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
This foreword is not part of this standard.
This standard addresses the interworking and interoperability between ANSI-41 MAP and GSM based networks in the support of subscribers roaming between networks. The objective of the standard is to achieve fully automatic, two-way interoperability between the heterogeneous networks. Services supported by this standard are described along with the associated information flows and message mappings. However, not all services and associated capabilities of ANSI-41 MAP and GSM MAP are supported by this standard. In general the attempt has been to focus on the key subscriber services needed in the market.
The focus of the first release of this standard was on common GSM and ANSI-136 TDMA services and associated network signaling (i.e. ANSI-41 MAP and GSM MAP). A prerequisite for this interoperability is multi-mode mobile stations with an enhanced SIM card for roaming between ANSI-136, GSM, and AMPS networks.
The first release of the standard did not define or require changes to existing ANSI-41 MAP or
GSM MAP to achieve the described interworking and interoperability. However, due to differences between the services and associated capabilities of the MAP protocols, complete and fully transparent interoperability may not have been achieved for some services. Future releases of this standard may require changes to ANSI-41 MAP, GSM MAP and the associated services to achieve full transparency while roaming between the different networks.
Additional or alternate service descriptions, information flows, and message mappings may be required to support other air interfaces supported by ANSI-41 MAP (e.g., IS-95, CDMA2000).
This may be accomplished in a future release of this standard.
Aspects of TIA/EIA-136 Revision C have been incorporated into the standard.
Revision A adds GPRS service capability in GSM Foreign Mode.
Revision BC adds two way roaming between GSM and IS-95 CDMA systems . A prerequisite for this interoperability is multi-mode mobile stations with an enhanced SIM card for roaming between IS-95 and GSM networks.
Information disclosed in this document is subject to the export jurisdiction of the US Department of
Commerce as specified in Export Administration Regulations (title 15 CFR parts 730 through 774 inclusive). The information contained herein may not be exported or re-exported to Cuba, Iran, Iraq, Libya,
North Korea, Sudan, or Syria. Contact the Telecommunications Industry Association, Arlington, VA or http://ftp.tiaonline.org/tr-45/tr45ahag/public%20documents .
Version 1 viii

4
5
6
1
2
3
9
10
7
8
11
12
13
14
15
16 (This page is intentionally left blank)
N.S0028-0
Version 1 ix

N.S0028-0
1
2
3
11
12
13
14
15
16
7
8
9
10
4
5
6
When a subscriber to one network type (e.g., ANSI-41) roams to a network of another type (e.g.,
GSM), interworking and interoperability functions are required to support roaming and enable service. This standard describes an Interworking and Interoperability Function (IIF) to support this cross-technology roaming between ANSI-41 and GSM networks. The IIF supports a multi-mode mobile station with a removable Subscriber Identity Module (SIM). The standard also defines the required network message mappings between ANSI-41 MAP and GSM MAP to support the mobile terminal and associated services.
This standard includes the support of cross-technology roaming between an ANSI-41 based network and a GPRS network. The GPRS network may be coupled with a GSM network. This feature requires enhancement to the Interworking and Interoperability Function (IIF) which supports a multi-mode mobile station and Subscriber Identity Module (SIM) with GPRS functionality.
17
18
19
20
21
22
23
The purpose for this standard is to define and describe the functions necessary for roaming between ANSI-41 MAP and GSM MAP based networks in the support of roaming subscribers.
This includes a capability to allow a subscriber to an ANSI-41 based network (e.g., a TDMA or
CDMAn ANSI-136 native subscriber) with a mobile terminal supporting GPRS service to roam to a GPRS network in GSM Foreign Mode. GPRS support for IS-95 handsets is not addressed in this release of the standard.
24
25
26
27
28
29
The scope of this standard are the services, information flows and message mappings which require interworking and interoperability functional specifications to support roaming between
ANSI-41 MAP and GSM MAP networks.
The scope of this volume is to provide a description of interstandard roaming along with an overview and network reference model for the Interworking and Interoperability Function (IIF).
30
31
32
33
34
35
36
37
38
This standard is divided into four separate volumes:
Volume 0 - Overview and Network Reference Model
Volume 1 - Service Descriptions
Volume 2 - Information Flows
Volume 3 - Message Mappings
Volume 0 is organized as follows:
1 Introduction - provides an overview, purpose, scope, and organization of this volume.
1

1
2
3
4
5
6
7
8
9
10
N.S0028-0
2 References - is a list of references used in the preparation of this volume of this Interim
Standard.
3 Definitions and Acronyms - defines words and acronyms that are used in this volume of this
Interim Standard.
4 Overview of Internetwork Roaming - provides an overview of interstandard roaming and defines the terms used to describe it.
5 IIF Reference Model and Description - provides an architecture description of the
Interoperability and Interworking Function (IIF), an overview of its functionality, and description of its relationship and interfaces to other network elements.
Version 1 2

N.S0028-0
1
2
3
7
8
9
4
5
6
10
11
12
13
14
15
16
Compatibility Standard,” March 2000, ANSI.
[2] TIA/EIA-41-D: “Cellular Radiotelecommunications Intersystem Operations,” December 1997,
ANSI.
[3] TIA/EIA-553: “Mobile Station – Land Station Compatibility Specification,” September 1989,
ANSI.
[4] GSM 09.02 Version 6.2.0 Release 1997 “Digital cellular telecommunication system (Phase
2+); Mobile Application Part (MAP) specification”, August 1998, ETSI.
[5] TIA/EIA/IS-129, “Interworking/Interoperability Between DCS 1900 and IS-41 Based MAPs for
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 ”IS-41 support for data services for digital terminals (TDMA and CDMA)”
19
20
21
[9] TIA/EIA/TSB58E A “Administration of Parameter Value Assignments for TIA/EIA Spread
Spectrum Standards” , January 2002
22
23
24
25
26
27
28
29
30
31
[10] TIA/EIA-95-B - Mobile Station-Base Station Compatibility Standard for Dual-Mode Spread
Spectrum Systems; Published October 1998.
[11] "TIA/EIA-IS-2000-A, cdma2000 Series, March 2000, plus addenda"Mobile Station-Base
Station Compatibility Standard for Dual-Mode Spread Spectrum Systems;
[12] TIA/EIA-868 – ANSI-41-D Network Based Enhancements to support one-way roaming to
GSM, Published TBD.
[12]"Enhanced Cryptographic Algorithms, Revision B," TR45AHAG, Published TBD
3

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

N.S0028-0
14
15
16
17
18
10
11
12
1
2
3
4
5
6
7
8
9
13
24
25
26
27
28
19
20
21
22
23
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
CDMA Foreign Mode
CDMA foreign mode indicates the condition or state of a GSM native subscriber accessing a
CDMA network.
CDMA Native Mode
CDMA native mode indicates the condition or state of an CDMA native subscriber accessing an
CDMA network.
CDMA Native Subscriber
CDMA native subscriber indicates an end user whose primary or home subscription resides in an
CDMA network. These subscribers include both home subscribers from the CDMA network, as well as roamers from other CDMA networks.
GPRS in GSM Foreign Mode
GPRS in GSM Foreign Mode is a subset of GSM Foreign Mode and indicates the condition or state of an ANSI41136 native subscriber accessing a GPRS network; the GPRS network may be coupled with a GSM network.
GSM
Global System for Mobile Communications (GSM) defines both air interface and network intersystem protocol standards for mobile stations (MS), base station systems (BSS), and network switching systems (NSS).
GSM Mode
GSM mode indicates the condition or state of a mobile station accessing a GSM network.
GSM Foreign Mode
GSM foreign mode indicates the condition or state of an ANSI41136 or an IS-95 native subscriber accessing a GSM network.
GSM Native Mode
GSM native mode indicates the condition or state of a GSM native subscriber accessing a GSM network.
GSM Native Subscriber
GSM native subscriber indicates an end user whose primary or home subscription resides in a
GSM network. These subscribers include both home subscribers from the GSM network, as well as roamers from other GSM networks.
Mobile Equipment
The radio transceiver, main processing unit, and man-machine interface necessary to access the radio network.
Mobile Station
The mobile equipment and the SIM together make up the mobile station, which is the wireless radiotelephone used by the subscriber.
Subscriber Identity Module (SIM)
A smart card that plugs into the mobile equipment and that contains the authentication algorithms, and stores service-oriented subscription information.
5

1
N.S0028-0
4
5
2
3
AC
AuC
AMPS
ANSI
Authentication Center in ANSI TIA/EIA-41 based networks
Authentication Center in GSM networks
Advanced Mobile Phone Service
American National Standards Institute
23
24
25
26
27
19
20
21
22
12
13
14
15
16
17
18
10
11
8
9
6
7
CDMA
ESN
ETSI
GMSC
GSM
GGSN
GPRS
HLR
HPLMN
Electronic Serial Number
European Telecommunications Standards Institute
Gateway Mobile Switching Center
Global System for Mobile Communication
Gateway GPRS Serving Node
General Packet Radio Service
Home Location Register
Home Public Land Mobile Network
IIF
IMSI
ITU
Interworking and Interoperability Function
International Mobile Subscriber Identity
International Telecommunications Union
MAP Mobile Application Part
MC ANSI41136 Message Center (for SMS)
MIN
MSC
MSID
MSISDN
Code-Division Multiple Access
Mobile Identification Number
Mobile Switching Center
Mobile Station Identity
Mobile Subscriber ISDN Number
Version 1 6

3
4
1
2
5
6
7
10
11
12
8
9
PLMN
SGSN
Public Land Mobile Network
Serving GPRS Support Node
SMS Short Message Service
SMS-GMSC GSM Short Message Service Gateway Mobile Switching Center
SMS-IWMSC GSM Short Message Service Interworking Mobile Switching Center
SMS-SC GSM Short Message Service Center
SS7
TDMA
TIA
VLR
Signaling System 7
Time Division Multiple Access
Telecommunications Industry Association
Visited Location Register
N.S0028-0
7

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

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

1
2
N.S0028-0
In most cases, the IIF interprets a signaling message in one protocol and converts it to the equivalent operation in the other network protocol.
24
25
26
27
32
33
40
41
42
43
44
34
35
36
37
38
39
28
29
30
31
13
14
15
16
17
18
19
20
21
22
23
3
4
5
6
7
8
9
10
11
12
The IIF does not duplicate the subscriber’s existing HLR, but provides a gateway to any visited network that uses a foreign MAP protocol. The original source of subscription data remains in the home network’s HLR. Most of this data shall not reside in the IIF, but shall be dynamically converted and translated between GSM and ANSI-41 MAP messages as needed.
Nevertheless, some basic subscriber identity information needs to be provisioned in the IIF to support this mapping process, such as:
•
International Mobile Subscriber Identity (IMSI)
•
Mobile Identification Number (MIN)
•
Electronic Serial Number (ESN)
•
Terminal type
•
Network Access Mode (non-GPRS, GPRS or both)
Authentication and encryption services are critical functions that shall be supported with network interoperability. These capabilities are managed in both GSM and ANSI-41 networks by the
Authentication Center (AuC or AC), which can be physically separated from the associated HLR or integrated with it. Different authentication processes and algorithms are defined for GSM and
ANSI-41. Therefore, subscriber specific authentication data shall be provisioned and maintained on both a GSM AuC and ANSI-41 AC, in order to support service on either network.
Subscriber data that needs to be maintained includes:
For ANSI-13641 network:
•
Ki (GSM subscriber authentication key)
•
Triplets or groups of Kc (cipher key), RAND, XRES,CKSN (cipher key sequence number), and SRES (signed response) for GSM based authentication and ciphering
•
A-key (AMPS/ANSI-136 or IS-95 authentication key)
•
SSD-A (AMPS/ANSI-136 or IS-95 shared secret data for authentication)
•
SSD-B (AMPS/ANSI-136 or IS-95 shared secret data used for generated signaling message encryption (SME) and voice privacy (VP) masks: the
CDMAPrivateLongCodeMask or the TDMA VoicePrivacyMask .
The foreign mode Authentication Center can be integrated into the IIF gateway or implemented as a separate network element.
Optionally, IIF may support one way-roaming only from CDMA to GSM network. In this case no data is provisioned at IIF level and ANSI-41 HLR/AC must be compliant with TIA/EIA -868 [11].
All the changes are made on the assumption the new requirements for UIM/handsets are working.
The following items are basic assumptions on which the optional one-way roaming scenario is based:
The IIF is not provisioned with any subscriber data
There is no subscriber specific data stored in the IIF.
The Home System is enhanced to support ANSI -41-to-GSM roaming
The ANSI-41 Home System has enhanced authentication capabilities to support roaming of subscribers to GSM systems. Subscribers may be using multi-mode mobile stations capable of
Version 1 10

N.S0028-0
24
25
26
27
28
29
30
15
16
17
18
19
20
21
22
23
31
32
33
34
35
36
37
8
9
10
11
12
13
14
1
2
3
4
5
6
7
38
39
40
41
42
43 roaming into a GSM system or UIMs that are inserted into GSM terminal equipment. A valid SSD is generated in the UIM before the user can roam to a GSM system
A valid SSD value must be generated in the UIM (or multi-mode MS) before the subscriber can roam into a GSM system. The IIF functions as a VLR in its interaction with the ANSI -41 Home
System
The ANSI-41 AC shares SSD with the IIF for subscribers roaming in a GSM network. The IIF generates the triplets (RAND, XRES, KC) used by the GSM system. The triplet generation function is specified in section 2.2.4.1 of “Enhanced Cryptographic Algorithms, Revision B.”
After the subscriber is registered in a GSM system, the IIF reports authentication failures to the
ANSI-41 system using the AuthenticationFailureReport operation.
SSD is shared with the IIF until registration in the GSM system is canceled. The ANSI -41
AC/HLR can cancel registration using the RegistrationCancellation operation.
The IIF shall remove the subscriber’s SSD when registration in the GSM system is canceled.
SSD Update cannot be performed when the MS is roaming in a GSM system
A new SystemCapabilities parameter value shall be defined to indicate a GSM system
A SystemCapabilities parameter value indicating GSM system shall be used by the IIF to indicate that the Serving network is using GSM authentication and privacy procedures. This indicates that
SSD Update cannot be performed. It also indicates that the ESN sent to the ANSI-41 home system was not received from the MS. The IIF functions as a GSM HLR/AC in its interactions with the GSM system
The IIF provides the GSM triplets needed for authentication and privacy in the GSM system. The
IIF generates triplets using the SSD value stored in the UIM (or multi-mode MS).
When roaming in a GSM system, the UIM uses the “authentication” algorithm supported by the IIF
When roaming is a GSM system, the UIM (or multi-mode MS) must use an authentication algorithm supported by the IIF for the computation of the cipher key and the response to the random challenge.
The ANSI-41 home system is expected to update SSD when the MS returns to an ANSI-41 system
The subscriber’s SSD should be updated when the user returns to an ANSI-41 system.
The IIF shall prevent disclosure of SSD values received from ANSI -41 systems
The IIF shall provide a secure method of storing SSD values received from ANSI-41 systems.
The
SSD values shall not be disclosed nor transmitted to any other network entity.
The IIF shall be able to request the MS’s ESN in the AuthenticationRequest INVOKE sent to the home ANSI-41 system
To support GPRS service in GSM Foreign Mode, GPRS specific subscriber data also needs to be provisioned in the IIF such as :
•
GGSN-list (GGSN Number and optional IP address)
•
PDP Type
•
PDP Address (if dynamic addressing is not allowed)
•
Quality of Service Subscribed
44
45
46
47
48
49
This following describes the individual network interfaces for which interoperability is provided by the IIF. For each particular interoperability function and interface interworking, the IIF simultaneously emulates a network element using foreign protocol messaging and a corresponding network element using native protocol messaging. For each particular messaging operation, the IIF converts the operation from the foreign protocol to the native protocol, and vice
11

1
2
3
4
5
6
7
8
N.S0028-0 versa. The emulation functions in the IIF conform to existing ANSI-41 and GSM protocols when communicating over the external interfaces.
The following figures depict the emulated network elements within the IIF using hashed lines. The hashed lines connecting emulated network elements within the IIF represent internal, conversion or mapping interfaces. All solid connecting lines depict standard ANSI-41 or GSM interfaces based on existing protocol.
The arrow above each figure represents information exchange for the top half of the figure, while the arrow below each figure represents information exchange for the bottom half of the figure.
9
10
11
12
13
14
The IIF provides an interface between the subscriber's HLR and any VLR which uses a foreign network signaling protocol. This interworking is provided over the interface reference "D" depicted in the network reference model. Figure 2 below depicts the interworking and control interface provided by the IIF in this case.
ANSI-41 subscriber roaming to GSM network
ANSI-41
HLR
ANSI-41
VLR
D
D
ANSI-41
VLR
ANSI-41
HLR
GSM
HLR
GSM
VLR
D
D
GSM
VLR
GSM
HLR
15
16
17
18
19
20
21
22
23
24
25
26
27
GSM subscriber roaming to ANSI-41 network
Figure 2: HLR - VLR Interface
5.3.1.1 ANSI-136 Foreign Mode Implementation for GSM Subscriber
When a GSM native subscriber operates in ANSI-136 foreign mode, the mobile station shall use the ANSI-136 air interface. The interoperability gateway or IIF shall provide both ANSI-41 HLR and GSM VLR emulation to allow the subscriber to automatically register and obtain service. To the visited ANSI-41 network, the subscriber appears to register with the IIF, emulating an
ANSI-41 HLR. This emulated ANSI-41 HLR acts as a limited proxy for the actual GSM HLR, with the true GSM HLR retaining ultimate control. At the same time, to the home GSM network, the subscriber appears to register from the IIF, emulating a GSM VLR. The IIF links ANSI-41 MAP operations and data to the equivalent GSM MAP operations and data, and vice versa, in order to support interoperability.
Version 1 12

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

1
2
3
4
5
6
7
N.S0028-0 signaling is supported over this interface. Figure 3 below depicts the interworking and control interface provided by the IIF in this case.
This interface is key to supporting optimal routing for late call forwarding, where the serving MSC wishes to signal back to the originating or gateway MSC in order to request forwarding of the call.
In order to support optimal routing for late call forwarding, the IIF provides originating or gateway
MSC emulation.
ANSI-41 subscriber roaming to GSM network
ANSI-41
Originating
MSC
ANSI-41
Serving
MSC
E
E
ANSI-41
Serving
MSC
ANSI-41
Originating
MSC
GSM
Gateway
MSC
GSM
Serving
MSC
E
E
GSM
Serving
MSC
GSM
Gateway
MSC
8
9
10
GSM subscriber roaming to ANSI-41 network
Figure 3: Originating / Gateway MSC - Serving MSC Interface
11
12
13
14
15
16
17
18
19
20
The IIF provides an interface from the subscriber's short message service message center (MC /
SMS-SC) to a serving MSC which uses a foreign network signaling protocol. This interworking is provided over the interface references "Q" and "E" depicted in the network reference model. In the case of ANSI-41 messaging, the MC has a direct "Q" interface to the serving MSC. In the case of GSM messaging, the SMS-SC interfaces with the serving MSC via the SMS Interworking
MSC (SMS-IWMSC) or the SMS Gateway MSC (SMS-GMSC) over the "E" interface. Figure 4 below depicts the interworking and control interface provided by the IIF in this case.
Version 1 14

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

1
N.S0028-0
2
3
4
5
6
7
8
The IIF provides an interface between the subscriber's HLR and any SGSN which uses a foreign network signaling protocol. This interworking is provided over the interface reference "Gr" depicted in the network reference model. Figure 5 below depicts the interworking and control interface provided by the IIF in this case.
ANSI-41 Subscriber roaming to GPRS network
ANSI-41
HLR
D ANSI-41
VLR
GSM
HLR
Gr
SGSN
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
TIA/EIA-41
Network Entities
GSM Network
Entities
Figure 5: HLR- SGSN Interface
5.3.4.1 GPRS in GSM Foreign Mode Implementation for ANSI41136 Subscriber
When an ANSI41136 native subscriber operates GPRS in GSM foreign mode, the mobile station shall use the GSM air interface. The interoperability gateway or IIF shall provide both GSM HLR and ANSI-41 VLR emulation to allow the subscriber to automatically register and obtain service.
To the visited GSM network, the subscriber appears to register with the IIF, emulating a GSM
HLR. This emulated GSM HLR acts as a limited proxy for the actual ANSI-41 HLR, with the true
ANSI-41 HLR retaining ultimate control. At the same time, to the home ANSI-41 network, the subscriber appears to register from the IIF, emulating an ANSI-41 VLR. The IIF links GSM MAP operations and data to the equivalent ANSI-41 MAP operations and data, and vice versa, in order to support interoperability.
To support GSM foreign mode operation, a GSM Authentication Center (AuC) can be integrated into the IIF gateway or implemented as a separate network element.
24
25
26
27
There are four alternatives for the implementation of the IIF functional element with respect to the network reference model and the network entities that are served. See “5 IIF Reference Model and Description” for applicable interfaces.
Version 1 16

N.S0028-0
5
6
1
2
3
4
The IIF may reside entirely inside an existing GSM network entity as a separate functional element. Each of the interfaces can be supported with this implementation alternative.
T IA / E I A - 4 1
N e t w o r k
E l e m e n t
G S M
N e t w o r k
E l e m e n t
I IF
Figure 6: IIF Resides within GSM Network Element
7
8
9
10
The IIF may reside entirely inside an existing ANSI-41 network entity as a separate functional element. Each of the interfaces can be supported with this implementation alternative.
T IA /E IA - 4 1
N e t w o r k
E le m e n t
G S M
N e t w o r k
E l e m e n t
II F
11
12
13
Figure 7: IIF Resides within ANSI-41 Network Element
17

1
N.S0028-0
2
3
4
The IIF may reside external to any existing ANSI-41 or GSM network entity as a separate network element. Each of the interfaces can be supported with this implementation alternative.
External
Network
Element
IIF
5
6
7
TIA/EIA-41
Network
Element
GSM
Network
Element
Figure 8: IIF Resides within External Network Element
8
9
10
11
12
13
14
15
Finally, the IIF may reside within both existing ANSI-41 and GSM network entities at the same time. In this case, each individual subscriber is likely to be served by one particular IIF, although the use of multiple IIFs per subscriber is possible. Again, each of the interfaces can be supported with this implementation alternative. While multiple IIFs can support one particular subscriber, each network interworking function would be supported by one specific IIF implementation.
TIA/EIA-41
Network
Element
GSM
Network
Element
IIF IIF
16
17
Figure 9: IIF Resides within both ANSI-41 and GSM Network Elements
Version 1 18

N.S0028-0
1
9
10
7
8
2
3
4
5
6
11
12
13
14
15
This standard addresses the interworking and interoperability between ANSI-41 MAP[3] and GSM
MAP[21] based networks in the support of subscribers roaming between networks. The interworking and interoperability functionality of the services, information flows, and message mappings are specified.
This standard consists of four Volumes:
Volume 0 - Overview and Interworking Reference Model
Volume 1 - Service Descriptions
Volume 2 - Information Flows
Volume 3 - Message Mappings
This is Volume 1. Volume 1 is based on ANSI-664[1] and GSM stage 1’s (see GSM 02-series e.g.,
GSM 02.04, etc. in the References section). Some modifications (primarily simplifications) were made for the purpose of specifying the degree of interoperability desired. ANSI-664 services and GSM services do not necessarily align.
Ballot Version i

1
N.S0028-0
2
3
4
A
A
A
Revision Date
0
A
A
A
A
March 2001
April 12, 2001
May 23, 2001
June 26, 2001
August 01, 2001
August 01, 2001
August 14, 2001
August 15, 2001
B
B
July 2001
March 2002
Version Comments
0
1
2
4
5
6
3
5
Initial Release J-STD-038
Added Section 4.10 GPRS.
Misc. editorial changes.
New Foreword; Modifications to 4.10.2.4.
Editorial changes; Modifications to 4.10.2.8 SMS Impacts.
Editorial changes; Modifications to 4.10 GPRS.
Ballot Version; Modifications to 4.10 GPRS
Version 3: Addition of CDMA/GSM two way roaming
Version V&V: Addition of CDMA/GSM two way and one roaming
5
Ballot Version ii

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

There are no figures in this volume.
N.S0028-0
Ballot Version vii

1
N.S0028-0
2
11
12
13
14
15
16
17
18
19
20
21
22
23
24
3
7
8
9
10
4
5
6
25
26
27
This foreword is not part of this standard.
This standard addresses the interworking and interoperability between ANSI-41 MAP and GSM based networks in the support of subscribers roaming between networks. The objective of the standard is to achieve fully automatic, two-way interoperability between the heterogeneous networks.
Services supported by this standard are described along with the associated information flows and message mappings. However, not all services and associated capabilities of ANSI-41 MAP and GSM
MAP are supported by this standard. In general the attempt has been to focus on the key subscriber services needed in the market.
The focus of the first release of this standard was on common GSM and ANSI-136 TDMA services and associated network signaling (i.e. ANSI-41 MAP and GSM MAP). A pre-requisite for this interoperability is multi-mode mobile stations with an enhanced SIM card for roaming between ANSI-
136, GSM, and AMPS networks.
The first release of the standard did not define or require changes to existing ANSI-41 MAP or GSM
MAP to achieve the described interworking and interoperability. However, due to differences between the services and associated capabilities of the MAP protocols, complete and fully transparent interoperability may not have been achieved for some services. Future releases of this standard may require changes to ANSI-41 MAP, GSM MAP and the associated services to achieve full transparency while roaming between the different networks.
Additional or alternate service descriptions, information flows, and message mappings may be required to support other air interfaces supported by ANSI-41 MAP (e.g., IS-95, cdmaOne and cdma2000). This may be accomplished in a future release of this standard.
Aspects of TIA/EIA-136 Rev C have been incorporated into this standard.
Revision A adds the capability of getting GPRS services when roaming in GSM Foreign Mode.
Revision B adds roaming between GSM and CDMA systems
Ballot Version viii

N.S0028-0
1
2
3
11
12
13
14
15
8
9
10
4
5
6
7
When a subscriber to one network type (e.g., ANSI-41) roams to a network of another type (e.g.,
GSM), interworking and interoperability functions are required to support roaming and enable service.
This standard describes an Interworking and Interoperability Function (IIF) to support this crosstechnology roaming between ANSI-41 and GSM networks. The IIF supports a multi-mode mobile station with a removable Subscriber Identity Module (SIM). The standard also defines the required network message mappings between ANSI-41 MAP and GSM MAP to support the mobile terminal and associated services.
This standard includes the support of cross-technology roaming from an ANSI-41 based network to a
GPRS network. The GPRS network may be coupled with a GSM network. This feature requires enhancement to the Interworking and Interoperability Function (IIF) which supports a multi-mode mobile station and Subscriber Identity Module (SIM) with GPRS functionality.
16
17
18
19
20
21
22
The purpose for this standard is to define and describe the functions necessary for roaming between
ANSI-41 MAP and GSM MAP based networks in the support of roaming subscribers. This includes a capability to allow a subscriber to an ANSI-41 based network (e.g., an ANSI-136 or CDMA native subscriber) with a mobile terminal supporting GPRS service to roam to a GPRS network in GSM
Foreign Mode.
23
35
36
37
32
33
34
24
25
26
27
28
29
30
31
The scope of this standard are the services, information flows, and message mappings which require interworking and interoperability functional specifications to support roaming between ANSI-41 MAP and GSM MAP networks.
The scope of this volume is a high level (stage 1) description of the services and functionality required to support GSM and ANSI-41 network interoperability. In particular, when in foreign mode (roaming in non-native mode technology), subscribers are able to: roam and register (with authentication); originate and terminate calls; have the following supplementary services operate:
- Call Forwarding,
- Call Waiting,
- Calling Number Identification Presentation - Line Identification Presentation,
- Call Barring, and
- GSM Multi-Party - ANSI-41 3-way Calling and Conference;
Ballot Version 1

N.S0028-0
1
2
3
4 have Short Message Service access and Message Waiting Notification; have Late Call Forwarding optimally routed; and have GPRS service in GSM Foreign Mode.
5
13
14
15
10
11
12
6
7
8
9
This standard is organized into the following volumes:
Volume 0 - Overview and Interworking Reference Model
Volume 1 - Service Descriptions
Volume 2 - Information Flows
Volume 3 - Message Mappings
This volume 1 is organized according to the following:
2 References - a list of references.
3 Definitions and Acronyms - definions of words and acronyms.
4 Stage 1 Service Descriptions - descriptions of the interoperable network features.
Ballot Version 2

N.S0028-0
1
2
3
4
5
6
7
8
13
14
15
16
17
18
19
20
21
22
23
24
25
26
9
10
11
12
33
34
35
36
37
38
27
28
29
30
31
32
[1] TIA/EIA-664: “Cellular Features Description”, Telecommunications Industry Association;
February 2000, ANSI.
[2] TIA/EIA-136: “TDMA Cellular/PCS--Radio Interface--Mobile Station-Base Station Compatibility
Standard,” March 2000, ANSI.
[3] TIA/EIA-41-D: “Cellular Radiotelecommunications Intersystem Operations,” December 1997,
ANSI.
[4] TIA/EIA/IS-751, "TIA/EIA 41-D Modifications to Support IMSI, February 1998".
[5] TIA/EIA/IS-807, "TIA/EIA-41-D Enhancements for Internationalization".
[6] EIA/TIA-553: “Mobile Station – Land Station Compatibility Specification,” September 1989,
ANSI.
[7] “Common Cryptographic Algorithms, Revision C,” October 27, 1998, TR45AHAG.
[8] TIA/EIA-136-510 “Authentication, encryption of signaling information/user data and privacy”.
[9] GSM 02.04 version 6.1.1 Release 1997, “General on Supplementary Services”, (Phase 2+),
ETSI.
[10] GSM 02.09 version 6.1.0 Release 1997, “Digital cellular telecommunications system Security
Aspects”, (Phase 2+), ETSI.
[11] GSM 02.30 version 6.1.0 Release 1997, “Man-Machine Interface (MMI) of the Mobile Station”,
(Phase 2+), ETSI.
[12] GSM 02.41 version 6.0.0, Release 1997, "Operator Determined Barring (ODB)", (Phase 2+),
ETSI.
[13] GSM 02.79 version 6.0.0, Release 1997, “Support of Optimal Routeing (SOR) Service
Definition (Stage 1)”, (Phase 2+), ETSI.
[14] GSM 02.81 version 7.0.0 Release 1998, “Line Identification Supplementary Services – Stage 1“
(Phase 2+), ETSI.
[15] GSM 02.82 version 6.0.0 Release 1997, “Call Forwarding (CF) Supplementary Services - Stage
1” (Phase 2+), ETSI.
[16] GSM 02.83 version 6.0.0 Release 1997, “Call Waiting (CW) and Call Holding (HOLD)
Supplementary Services - Stage 1”, (Phase 2+), ETSI.
[17] GSM 02.84 version 6.0.0 Release 1997, “MultiParty (MPTY) Supplementary Services – Stage
1”, (Phase 2+), ETSI.
[18] GSM 02.85 version 6.0.0 Release 1997, “Closed User Group (CUG) Supplementary Services –
Stage 1 ”, (Phase 2+), ETSI.
[19] GSM 02.86 version 6.0.0 Release 1997, “Advice of Charge (AOC) Supplementary Services –
Stage 1”, (Phase 2+), ETSI.
[20] GSM 02.88 version 6.0.0 Release 1997, “Call Barring (CB) Supplementary Services – Stage 1”
(Phase 2+), ETSI.
Ballot Version 3

N.S0028-0
1
2
3
4
[21] GSM 09.02 version 6.2.0 Release 1997, “Digital cellular communication system (Phase2+);
Mobile Application Part (MAP) specification”, August 1998, ETSI
[22] GSM 02.60 version 6.3.1 Release 1997 “General Packet Radio Service (GPRS); Service
Description, Stage 1
5 [23] TIA/EIA/IS 737A”IS-41 support for data services for digital terminals (TDMA and CDMA)”
6 [24] TIA/EIA/IS 735 “IS-41 support for IS-95-A (advanced CDMA)”
7
8
9
10
11
12
13
14
15
16
17
[25] TIA/EIA/TSB58-E “Administration of Parameter Value Assignments for TIA/EIA Spread
Spectrum Standards” , January 2002
[26] TIA/EIA-95-B - Mobile Station-Base Station Compatibility Standard for Dual-Mode Spread
Spectrum Systems; Published October 1998.
[27] "TIA/EIA-IS-2000-A, cdma2000 Series, March 2000, plus addenda"Mobile Station-Base Station
Compatibility Standard for Dual-Mode Spread Spectrum Systems;
[28] TIA/EIA-868 – ANSI-41-D Network Based Enhancements to support one-way roaming to
GSM, Published TBD. [12]"Enhanced Cryptographic Algorithms, Revision B," TR45AHAG, Published TBD
Ballot Version 4

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

N.S0028-0
48
49
50
51
38
39
40
41
42
43
32
33
34
35
36
37
44
45
46
47
24
25
26
27
28
29
30
31
13
19
20
21
22
23
14
15
16
17
18
7
8
9
10
1
2
3
4
5
6
11
12
GSM
Global System for Mobile Communications (GSM) defines both air interface and network intersystem protocol standards for mobile stations (MS), base station systems (BSS), and network switching systems (NSS).
GSM CS attached
GSM circuit-switched services attached means that the subscriber is attached to a GSM MSC. This is also referred to as IMSI attached.
GSM CS detached
GSM circuit-switched services detached means that the subscriber is detached from a GSM MSC.
This is also referred to as IMSI detached.
GSM Foreign Mode
GSM foreign mode indicates the condition or state of an ANSI-136 ANSI-41 native subscriber accessing a GSM network.
GPRS HLR
General Packet Radio Service Home Location Register is the HLR responsible for GPRS functions. It interfaces with the SGSN and GGSN and Authentication Center.
GSM Mode
GSM mode indicates the condition or state of a mobile station accessing a GSM network.
GSM Native Mode
GSM native mode indicates the condition or state of a GSM native subscriber accessing a GSM network.
GSM Native Subscriber
GSM native subscriber indicates an end user whose primary or home subscription resides in a GSM network. These subscribers include both home subscribers from the GSM network, as well as roamers from other GSM networks.
CDMA
CDMA as used in this document, refers to TIA/EIA -95 [9] or TIA/EIA-2000 [10], which is a CDMA air interface protocol standard for mobile stations and their associated base stations. CDMA is a dual-mode standard that includes digital (CDMA) operation and analog (AMPS) operation. CDMA networks use ANSI-41 for intersystem signaling.
CDMA Mode
CDMA mode indicates the condition or state of a mobile station accessing an CDMA network.
Ballot Version 6

N.S0028-0
28
29
30
31
32
33
34
35
36
37
15
16
17
18
19
20
21
22
23
24
25
26
27
1
2
3
4
5
6
7
8
9
10
11
12
13
14
38
39
CDMA Foreign Mode
CDMA foreign mode indicates the condition or state of a GSM native subscriber accessing a CDMA network.
CDMA Native Mode
CDMA native mode indicates the condition or state of an CDMA native subscriber accessing an
CDMA network.
CDMA Native Subscriber
CDMA native subscriber indicates an end user whose primary or home subscription resides in an
CDMA network. These subscribers include both home subscribers from the CDMA network, as well as roamers from other CDMA networks.
GPRS in GSM Foreign Mode
GPRS in GSM Foreign Mode is a subset of GSM Foreign Mode and indicates the condition or state of an ANSI136 41 native subscriber accessing a GPRS network; the GPRS network may be coupled with a GSM network.
Late Call Forwarding
Call Forwarding invoked after the call has been offered to the terminating VMSC (e.g., CFB,
CFNA/CFNRy, CFNRc) .
Mobile Equipment
The radio transceiver, main processing unit, and man-machine interface necessary to access the radio network.
Mobile Station
The mobile equipment and the SIM together make up the mobile station, which is the wireless radiotelephone used by the subscriber.
Subscriber Identity Module
A smart card that plugs into the mobile equipment and that contains the authentication algorithms, and stores service-oriented subscription information.
Ballot Version 7

N.S0028-0
1
17
18
19
20
13
14
15
16
21
22
23
24
25
29
30
31
32
26
27
28
10
11
12
8
9
4
5
6
7
2
3
CFB
CFNA
CFNRc
CFNRy
CS
EDGE
EIA
ESN
ETSI
FC
FSM
GGSN
GPRS
GSM
HLR
HPLMN
IIF
IMSI
ITU
MAP
AC
AuC
AMPS
ANSI
BAIC
BAOC
BIC-Roam
BMI
BOIC
BOIC-exHC
CDMA
Authentication Center in ANSI TIA/EIA-41 based networks
Authentication Center in GSM networks
Advanced Mobile Phone Service
American National Standards Institute
Barring of All Incoming Calls
Barring of All Outgoing Calls
Barring of Incoming Calls while Roaming Outside HPLMN Country
Base Station, Mobile Switching System, and Interworking Function
Barring of Outgoing International Calls
Baring of Outgoing International Calls Except to HPLMN Country
Code-Division Multiple Access
Call Forwarding Busy
Call Forwarding No Answer
Call Forwarding Not Reachable
Call Forwarding No Reply
Circuit-Switched
Enhanced Data Rates Through Global Evolution
Electronics Industry Association
Electronic Serial Number
European Telecommunications Standards Institute
Feature Code
GSM Forward Short Message
Gateway GPRS Support Node
General Packet Radio Service
Global System for Mobile Communications
Home Location Register
Home Public Land Mobile Network
Interworking and Interoperability Function
International Mobile Subscriber Identity
International Telecommunications Union
Mobile Application Part
Ballot Version 8

12
13
14
15
16
10
11
8
9
3
4
1
2
5
6
7
20
21
22
23
24
17
18
19
MC
ME
MO
MS
MSC
MT
MWN
ODB
OTA
PCS
PIN
PLMN
SGSN
SID
SIM
SMDPP
SMS
SMS-C
TDMA
TIA
UWCC
VLR
VPLMN
ANSI41136 Message Center (for SMS)
Mobile Equipment
Mobile Originated
Mobile Station
Mobile Switching Center
Mobile Terminated
Message Waiting Notification
Operator Determined Barring
Over-the-Air Activation
Personal Communications Service
Personal Identification Number
Public Land Mobile Network
Serving GPRS Support Node
System Identity
Subscriber Identity Module
ANSI-41 SMS message
Short Message Service
GSM Short Message Service Center
Time Division Multiple Access
Telecommunications Industry Association
Universal Wireless Communications Consortium
Visitor Location Register
Visitor Public Land Mobile Network
N.S0028-0
Ballot Version 9

N.S0028-0
1
9
10
11
12
6
7
8
2
3
4
5
When in foreign mode (e.g., GSM or ANSI-136 ANSI-41 subscribers accessing respectively ANSI-
41136 or GSM networks), subscribers are able: to roam and register (with authentication) to originate and terminate calls to have the following supplementary services operate: o Call Forwarding, o Call Waiting, Calling Number/Line Identification Presentation, o Call Barring, and o GSM Multi-Party - ANSI-41 3-way Calling and Conference; to have short message service and Message Waiting Notification; and to have late call forwarding optimally routed.
13
14
15
16
Authentication defines the ability for a wireless network to confirm the identity of a mobile station at the time of connection, and to ensure the validity of this identity during the complete connection time.
This is achieved through the use of cryptographic schemes based on secret key algorithms.
17
23
24
25
26
27
28
18
19
20
21
22
29
30
31
32
33
34
35
36
The authentication procedure starts based on network events received by the mobile station. These events include mobile station origination, termination, registration and R-DATA messages in ANSI -41
TDMA or CDMA-136 . These events are dependent of the technology used and are different in GSM and ANSI-136. The authentication procedure involves an authentication center on the network side and an authentication module in the mobile station. It is initiated by a random number sent from the authentication center to the authentication module. The authentication module uses this random value and a combination of secret data and internal values to create an authentication value and a key that is optionally used for encryption. This authentication value is sent back to the authentication center, which verifies its validity by computing it again based on the same input. A successful outcome of the authentication process occurs only when it can be demonstrated that the authentication module and the authentication center possess identical sets of secret values.
Optionally, IIF may support one way-roaming only from CDMA to GSM network. In this case since no data is provisioned at IIF level, IIF must generate the GSM triplets using as input the authentication parameters returned by ANSI-41 HLR/AC, and ANSI-41 HLR/AC must be compliant with PN-4925 (to be published as TIA/EIA-868 [28]. All the changes are made on the assumption the new requirements for UIM/handsets are working.
4.1.1.1 Applicability to Telecommunications Services
Not identified.
Ballot Version 10

N.S0028-0
1
8
9
10
11
12
13
5
6
7
2
3
4
In ANSI41136 native and foreign mode, the authentication procedure is done according to the procedures defined in TIA/EIA-136-510 [8] for TDMA or according to TIA/EIA-95 for a CDMA..
In GSM native and foreign mode, the authentication procedure is done according to the procedures defined in GSM 02.09 [10].
ANSI-136 Mode
The ANSI-136 authentication module is defined by the ANSI-136 directory. It holds the secret data and internal values used during the authentication process.
The secret data used in the ANSI-136 authentication process is the shared secret data (SSD). The internal values used within the ANSI-136 authentication process are the ESN, the MIN1 and the
MIN2.
CDMA Mode
14
15
16
17
The secret data used in the CDMA authentication process is the shared secret data (SSD). The internal values used within the CDMA authentication process are the ESN, and the IMSI.
Authentication on IMSI is done in a CDMA mobile according to the IS-95 specification by extracting
10 digits from the IMSI. (IMSI_S).
25
26
27
28
22
23
24
18
19
20
21
ANSI-41 Mode
The ANSI-41 authentication module is defined by the air-interface specific directory in the mobile station. The data used for authentication is as define by the Common Cryphtograpic Algorithm
( CAVE)add reference).
GSM Mode
The GSM authentication module is defined by the GSM directory in the SIM. The SIM card can support multiple GSM subscriptions and each one has its own authentication module.
The secret data used in the GSM authentication process is the Ki. There is no internal data used in the GSM authentication process.
33
34
35
36
37
38
39
29
30
31
32
4.1.2.1 Authorization (or Provision)
In GSM mode, the secret data (Ki) is stored in advance in the network’s Authentication Center (AuC) as well as the SIM’s authentication module at the time of personalization of the SIM. This secret data on the SIM cannot be modified after the issuance of the SIM.
In ANSI mode, the secret data (A-key) is stored in advance in the network’s Authentication Center
(AC) as well as the mobile’s station authentication module at the time of provisioning. This secret data maybe overwritten with a new value via reprovisioning or over the air parameter administration
In ANSI136 41, the shared secret data (SSD) is generated from a root secret data (A-Key). This root secret data is stored in advance in the authentication module and can be modified after issuance. The generation of the secret data is done by the authentication center issuing an SSD UPDATE request with the appropriate parameters.
Ballot Version 11

N.S0028-0
1
2
4.1.2.2 De-Authorization (or Withdrawal)
The de-authorization is done at the Authentication Center.
3
4
4.1.2.3 Registration
None identified.
5
6
4.1.2.4 De-Registration (or Erasure)
None identified.
7
8
4.1.2.5 Activation
Activation is performed by the operator or serving system.
9
10
4.1.2.6 De-Activation
De-activation is performed by the operator or serving system.
11
12
13
14
15
16
4.1.2.7 Invocation
The authentication function is invoked in the mobile station by selecting the appropriate directory
(GSM or ANSI41136 ) on the authentication module and sending the appropriate command ( RUN
AUTH ALGO or RUN CAVE)command , with the appropriate parameters (random value, option flag, internal values). The authentication function is invoked in the network by the receipt of an authentication message from the mobile station.
17
18
19
20
4.1.2.8 Normal Operation with Successful Outcome
If the Authentication Signature result calculated by the mobile station and sent to the BMI (Base
Station, Mobile Switching Center, Interworking Function) matches the result calculated by the BMI then call processing and feature access is allowed by the BMI.
21
22
23
In the event that the mobile station cannot provide the correct Authentication Signature result to the
BMI then call processing and feature access is may be denied not allowed by the BMI.
24
25
4.1.3.1 Registration
None identified.
26
27 None identified.
28
29
4.1.3.3 Activation
None identified.
30
31
4.1.3.4 De-Activation
None identified.
32 4.1.3.5 Invocation
Ballot Version 12

N.S0028-0
1 None identified.
2
3 None identified.
4
5
4.1.3.7 Exceptions During Intersystem Handoff
None identified.
6
7
8
None identified.
9
10
11
12
4.1.5.1 Advice of charge (AoC)
None identified.
13
14
4.1.5.2 Barring of All Outgoing Calls (BAOC)
None identified.
15
16
4.1.5.3 Barring of Outgoing International Calls (BOIC)
None identified.
17
18
19
4.1.5.4 Barring of Outgoing International Calls except those directed to the Home PLMN
(BOIC-exHC)
None identified.
20
21
4.1.5.5 Barring of All Incoming Calls (BAIC)
None identified.
22
23
4.1.5.6 Barring of Incoming Calls when Roaming Outside the Home PLMN (BIC-Roam)
None identified.
24
25
26
4.1.5.7 Call Delivery (CD)
If the Authentication Signature result at the mobile station does not match that of the BMI then Call
Delivery shall not be allowed.
27
28 None identified.
29
Ballot Version 13

N.S0028-0
1 None identified.
2
3
4.1.5.10 Call Forwarding—No Answer / No Reply (CFNA / CFNRy)
None identified.
4
5
4.1.5.11 Call Forwarding—Not Reachable (CFNRc)
None identified.
6
7
4.1.5.12 Call Forwarding—Unconditional (CFU)
None identified.
8
9
4.1.5.13 Call Transfer (CT)
None identified.
10
11
4.1.5.14 Call Waiting / Call Hold (CW / HOLD)
None identified.
12
13
4.1.5.15 Calling Number / Line Identification Presentation (CNIP / CLIP)
None identified.
14
15
4.1.5.16 Calling Number / Line Identification Restriction (CNIR / CLIR)
None identified.
16
17
4.1.5.17 Calling Name Presentation (CNAP)
None identified.
18
19
4.1.5.18 Calling Name Restriction (CNAR)
None identified.
20
21
4.1.5.19 Closed User Group (CUG)
None identified.
22
23
24
25
4.1.5.20 Conference Calling / Multi Party Service (CC / MPTY)
A special challenge shall be made to the mobile station by the BMI in order to activate this feature. If the Authentication Signature result at the mobile station does not match that of the BMI then this feature shall not be allowed.
26
27
4.1.5.21 Do Not Disturb (DND)
None identified.
28
29
4.1.5.22 Emergency Services (Future)
None identified.
Ballot Version 14

N.S0028-0
1
2
4.1.5.23 Flexible Alerting (FA)
None identified.
3
4
4.1.5.24 Message Waiting Notification (MWN)
None identified.
5
6
4.1.5.25 Mobile Access Hunting (MAH)
None identified.
7
8
4.1.5.26 Password Call Acceptance (PCA)
None identified.
9
10
4.1.5.27 Preferred Language (PL)
None identified.
11
12
4.1.5.28 Priority Access and Channel Assignment (PACA)
None identified.
13
14
4.1.5.29 Remote Feature Control (RFC)
None identified.
15
16
4.1.5.30 Selective Call Acceptance (SCA)
None identified.
17
18
4.1.5.31 Subscriber PIN Access (SPINA)
The Authentication Feature shall take precedence over the SPINA feature.
19
20
4.1.5.32 Subscriber PIN Intercept (SPINI)
The Authentication Feature shall take precedence over the SPINI feature.
21
22
23
24
4.1.5.33 Three-Way Calling / Multi Party Service (3WC / MPTY)
A special challenge shall be made to the mobile station by the BMI in order to activate this feature. If the Authentication Signature result at the mobile station does not match that of the BMI then this feature shall not be allowed.
25
26
27
28
4.1.5.34 Voice Message Retrieval (VMR)
If this feature requires the mobile station to originate a call from the mobile station and the
Authentication Signature result at the mobile station does not match that of the BMI then this feature shall not be allowed.
29 4.1.5.35 Voice Privacy (VP)
Ballot Version 15

N.S0028-0
1
2
3
The Voice Privacy elements (e.g., for ANSI41136 ,TDMA or CDMA ) are derived from the same secret A-Key as for the Authentication algorithm. If the HLR/AC for the mobile subscriber does not have knowledge of this information it shall not be able to activate the Voice Privacy feature.
Ballot Version 16

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

N.S0028-0
1
2
3
4
5
6
Call Forwarding—Unconditional (CFU) permits a called subscriber to send incoming calls addressed to the called subscriber’s Directory Number to another Directory Number (forward-to number) or to the called subscriber’s designated voice mail box.
7
8
9
4.2.2.1.1 Applicability to Telecommunications Services
CFU is applicable to voice telecommunication services.
10
11
4.2.2.2 Normal Procedures With Successful Outcome
12
13
14
15
16
17
4.2.2.2.1 Authorization (or Provision)
CFU may be generally available or may be provided after pre-arrangement with the service provider.
The authorization (provision) may have subscription options. These options are defined in either
GSM 02.82[15] (i.e., GSM native mode subscribers) or ANSI-664[1] (e.g., ANSI41,TDMA136 or
CDMA native mode subscribers). Authorization or Provisioning may occur while operating in foreign mode.
18
19
20
4.2.2.2.2 De-Authorization (or Withdrawal)
CFU may be withdrawn by the service provider, at the subscriber’s request or for administrative reasons. De-authorization or withdrawal may occur while operating in foreign mode.
30
31
32
33
34
35
36
21
22
23
24
25
26
27
28
29
4.2.2.2.3 Registration
If the subscriber is authorized for Fixed Registration, the forward-to number shall be registered upon authorization (provision). Mobile stations operating in foreign mode may attempt to perform registration procedures normally supported in native mode.
The forward-to-number may be registered by the service provider upon authorization (provision) for
Variable Registration subscribers
GSM foreign mode: A forward-to-number may be registered by a Variable Registration authorized subscriber specifying the CFU registration feature code and a forward-to number termination address as in:
FC + termination address + SEND .
Alternatively, if the mobile station offers menu driven control of registration, the mobile station is expected to generate the equivalent GSM functional signaling towards the network.
ANSI-41 foreign mode: Registration can take place with an appropriate control procedure by the subscriber, per GSM 02.30[11]. In ANSI-41 foreign mode, if the equivalent GSM feature code (MMI) is manually entered by the user, the mobile station is expected to issue the relevant ANSI13641 feature code entry.
Ballot Version 18

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

N.S0028-0
1
2
The serving system may provide a courtesy call to the forward-to number shortly after this feature is activated permitting the subscriber to verify the validity of the forward-to-number.
3
4
5
4.2.2.2.6 De-Activation
GSM foreign mode: CFU may be de-activated by a Demand Activation authorized subscriber specifying the CFB de-activation feature code, as in:
6
13
14
15
16
7
8
9
10
11
12
FC0 + SEND .
Alternatively, if the mobile station offers menu driven control of de-activation, the mobile station is expected to generate the equivalent GSM functional signaling.
ANSI-41 foreign mode: The user may deactivate CFU by means of an appropriate control procedure
(e.g., as described in GSM 02.30[11]). In ANSI-41 foreign mode, if the equivalent GSM feature code
(MMI) is manually entered by the user, the mobile station is expected to issue the necessary ANSI-
13641 feature code to the network.
If the de-activation is accepted, the system shall indicate success using either GSM or ANSI13641 signaling techniques depending on the mode of operation. Registered information shall not be erased.
CFU shall be de-activated upon de-authorization (withdrawal) or de-registration (erasure).
17
18
4.2.2.2.7 Invocation
The feature treatment is invoked unconditionally when there is an incoming call and CFU is active.
19
20
21
22
23
24
25
26
4.2.2.3 Normal Operation with Successful Outcome
When CFU is active, incoming calls for the subscriber shall be forwarded unconditionally to the forward-to number.
GSM Foreign Mode: When an incoming call is forwarded unconditionally the forward-to-party shall receive a notification that the call has been forwarded. The calling party may also receive a notification that the call has been forwarded.
ANSI-41 foreign mode: When an incoming call is forwarded unconditionally the served mobile subscriber may receive a notification that the call has been forwarded.
27
28
29
30
4.2.2.3.1 Call Detail Record / Charging Requirements
For GSM and ANSI-41 based network interoperability, no new or special recording capabilities are needed.
Ballot Version 20

N.S0028-0
1
2
3
4.2.2.4 Exception Procedures or Unsuccessful Outcome
9
10
11
12
7
8
4
5
6
4.2.2.4.1 Registration
If the system cannot accept a registration request, the served mobile subscriber shall receive a notification that registration of call forwarding unconditional was not successful. Possible causes are: service not subscribed to; forward-to number is invalid directory number; use of an operator access prefix; insufficient information; forward-to number is a special service code (e.g., police); forward-to number is the directory number of the mobile subscriber herself.
13
14
15
4.2.2.4.2 De-Registration (Erasure)
If the subscriber is not authorized for the request, the system shall apply feature denial treatment when de-registration is attempted.
16
17
18
4.2.2.4.3 Activation
If the subscriber is not authorized for the request, or if a forward-to-number is not properly registered, the system shall apply feature denial treatment when activation is attempted.
19
20
21
4.2.2.4.4 De-Activation
If the subscriber is not authorized for the request, the system shall apply feature denial treatment when de-activation is attempted.
22
23
24
25
26
27
28
4.2.2.4.5 Invocation
If the forwarded call cannot be routed to the forward-to-destination, then the call shall be given the appropriate treatment, such as applying the Special Information Tone for intercept to the calling party.
Precautions shall be taken to preclude undesirable looping of forwarded numbers within the MSC or between the MSC and other switching centers. If such looping is detected, the call forwarding shall be given the appropriate treatment, such as applying the Special Information Tone for intercept to the calling party.
29
30
4.2.2.4.6 Exceptions While Roaming
None identified.
31
32
4.2.2.4.7 Exceptions During Intersystem Handoff
None identified.
33
Ballot Version 21

N.S0028-0
1 None identified.
2
3
4.2.2.6 Interactions With Other Features and Services
4
5
4.2.2.6.1 Advice of charge (AoC)
See GSM 02.86[19].
6
7
4.2.2.6.2 Barring of All Outgoing Calls (BAOC)
None identified at this time..
8
9
4.2.2.6.3 Barring of Outgoing International Calls (BOIC)
None identified at this time..
10
11
12
4.2.2.6.4 Barring of Outgoing International Calls except those directed to the Home PLMN
(BOIC-exHC)
None identified at this time.
13
14
4.2.2.6.5 Barring of All Incoming Calls (BAIC)
None identified at this time.
15
16
4.2.2.6.6 Barring of Incoming Calls when Roaming Outside the Home PLMN (BIC-Roam)
None identified at this time.
17
18
19
4.2.2.6.7 Call Delivery (CD)
CFU takes precedence over CD. That is, calls arriving when CFU is active are forwarded unconditionally and not given CD treatment.
20
21
22
4.2.2.6.8 Call Forwarding—Busy (CFB)
CFU takes precedence over CFB. That is, calls arriving when CFU is active shall be forwarded unconditionally and not given CFB treatment
23
24
25
4.2.2.6.9 Call Forwarding—Default (CFD)
CFU takes precedence over CFD. That is, calls arriving when CFU is active shall be forwarded unconditionally and not given CFD treatment.
26
27
28
4.2.2.6.10 Call Forwarding—No Answer / No Reply /Not Reachable (CFNA / CFNRy/CFNRc)
CFU takes precedence over CFNA/CFNRy/CFNRc. That is, an incoming call arriving for a subscriber with both CFU and CFNA/CFNRy/CFNRc active shall be forwarded with CFU.
29
30
4.2.2.6.11 Call Transfer (CT)
None identified.
Ballot Version 22

N.S0028-0
1
2
3
4.2.2.6.12 Call Waiting / Call Hold (CW / HOLD)
CFU takes precedence over CW. That is, calls arriving when CFU is active shall be forwarded unconditionally and not given CW treatment.
4
5
6
7
4.2.2.6.13 Calling Number / Line Identification Presentation (CNIP / CLIP)
When a call has been forwarded and the forward-to user has been provided with the CNIP / CLIP supplementary service, the forward-to user shall receive the number of the original calling user, if this calling user has not subscribed to or invoked the CNIR / CLIR supplementary service.
8
9
10
11
12
13
4.2.2.6.14 Calling Number / Line Identification Restriction (CNIR / CLIR)
If the calling number indicates presentation restricted, the calling number shall not be presented to the called party or the forward-to-party.
If the called (redirecting) subscriber has CFU active and CNIR is either Permanently Restricted or the default is Presentation Restricted, the redirecting number shall indicate presentation restricted to prevent presentation to the forward-to-party or to the forward-to station.
14
15
16
17
4.2.2.6.15 Calling Name Presentation (CNAP)
When a call has been forwarded and the forward-to-party has been provided with the CNAP supplementary service, the forward-to user shall receive the name of the original calling user, if this calling user has not subscribed to or invoked the CNAR or CNIR / CLIR supplementary service.
18
19
20
21
22
23
4.2.2.6.16 Calling Name Restriction (CNAR)
If the calling name or number indicates presentation restricted, the calling name or number shall not be presented to the called party or the forward-to-party.
If the called (redirecting) subscriber has CFU active and CNAR or CNIR is either Permanently
Restricted, or the default is Presentation Restricted, the redirecting name shall indicate presentation restricted to prevent presentation to the forward-to-party.
24
25
4.2.2.6.17 Closed User Group (CUG)
See GSM 02.85[18].
26
27
4.2.2.6.18 Conference Calling / Multi Party Service (CC / MPTY)
None identified.
28
29
4.2.2.6.19 Do Not Disturb (DND)
None identified at this time.
30
31
4.2.2.6.20 Emergency Services (Future)
None identified at this time.
32
33
4.2.2.6.21 Flexible Alerting (FA)
None identified at this time.
34 4.2.2.6.22 Message Waiting Notification (MWN)
Ballot Version 23

N.S0028-0
1 None identified.
2
3
4.2.2.6.23 Mobile Access Hunting (MAH)
None identified at this time.
4
5
4.2.2.6.24 Password Call Acceptance (PCA)
None identified at this time.
6
7
4.2.2.6.25 Preferred Language (PL)
None identified.
8
9
4.2.2.6.26 Priority Access and Channel Assignment (PACA)
None identified at this time.
10
11
12
4.2.2.6.27 Remote Feature Control (RFC)
CFU Registration shall be allowed via RFC in ANSI41136 mode, or via functional messaging in GSM mode.
13
14
4.2.2.6.28 Selective Call Acceptance (SCA)
None identified at this time.
15
16
4.2.2.6.29 Subscriber PIN Access (SPINA)
None identified at this time.
17
18
4.2.2.6.30 Subscriber PIN Intercept (SPINI)
None identified.
19
20
4.2.2.6.31 Three-Way Calling / Multi Party Service (3WC / MPTY)
None identified.
21
22
4.2.2.6.32 Voice Message Retrieval (VMR)
None identified.
23
24
25
4.2.2.6.33 Voice Privacy (VP)
None identified.
Ballot Version 24

N.S0028-0
1
2
3
4
5
6
7
Call Forwarding—Busy (CFB) permits a called subscriber to have the system send incoming calls addressed to the called subscriber’s Directory Number to another Directory Number (forward-to number) or to the called subscriber’s designated voice mail box, when the subscriber is engaged in a call or service. CFB does not impact a subscriber’s ability to originate calls.
8
9
4.2.3.1.1 Applicability to Telecommunications Services
CFB is applicable to voice telecommunications services.
10
11
4.2.3.2 Normal Procedures With Successful Outcome
12
13
14
15
16
17
4.2.3.2.1 Authorization (or Provision)
CFB may be generally available or may be provided after pre-arrangement with the service provider.
The authorization (provision) may have the subscription options. These options are defined in either
GSM 02.82[15] (i.e., GSM native mode subscribers) or ANSI-664[1] (e.g., ANSI41,TDMA136 or
CDMA native mode subscribers). Authorization or Provisioning may occur while operating in foreign mode.
18
19
20
4.2.3.2.2 De-Authorization (or Withdrawal)
CFB may be withdrawn at the subscriber’s request or for administrative reasons. De-authorization or withdrawal may occur while operating in foreign mode.
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
4.2.3.2.3 Registration
If the subscriber is authorized for Fixed Registration, the forward-to number shall be registered upon authorization (provision).
The CFB forward-to number may be registered by the service provider upon authorization (provision) for Variable Registration subscribers. Mobile stations operating in foreign mode may attempt to perform registration procedures normally supported in native mode.
GSM foreign mode: A forward-to-number may be registered by a Variable Registration authorized subscriber specifying the CFB registration feature code and a forward-to number termination address as in:
FC + termination address + SEND .Alternatively, if the mobile station offers menu driven control of registration, the mobile station is expected to generate the equivalent GSM functional signaling towards the network.
ANSI-41 foreign mode: Registration may take place with an appropriate control procedure by the subscriber, per GSM 02.30[11]. In ANSI-41 foreign mode, if the equivalent GSM mode feature code
(MMI) is manually entered by the user, the mobile station is expected to issue the relevant ANSI-
13641 feature code entry.
Ballot Version 25

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

N.S0028-0
1
2
The serving system may provide a courtesy call to the forward-to number shortly after this feature is activated permitting the subscriber to verify the validity of the forward-to number.
3
4
5
4.2.3.2.6 De-Activation
GSM foreign mode: CFB may be de-activated by a Demand Activation authorized subscriber specifying the CFB de-activation feature code, as in:
6
13
14
15
16
7
8
9
10
11
12
FC0 + SEND .
Alternatively, if the mobile station offers menu driven control of de-activation, the mobile station is expected to generate the equivalent GSM functional signaling.
ANSI-41 foreign mode: The user may deactivate CFB by means of an appropriate control procedure
(e.g., as described in GSM 02.30[11]). In ANSI-41 foreign mode, if the equivalent GSM mode feature code (MMI) is manually entered by the user, the mobile station is expected to issue the necessary
ANSI13641 feature code to the network.
If the de-activation is accepted, the system shall indicate success with using either GSM or ANSI-
13641 signaling techniques depending on the mode of operation. Registered information shall not be erased.
CFB shall be de-activated upon de-authorization (withdrawal) or de-registration (erasure).
17
18
19
4.2.3.2.7 Invocation
The feature treatment is invoked when there is an incoming call while the subscriber is considered to be busy (i.e., in any state other than the idle state) and CFB is active.
20
21
22
23
24
25
26
27
28
4.2.3.3 Normal Operation with Successful Outcome
When CFB is active, incoming calls for the subscriber shall be forwarded to the forward-to number when the subscriber is considered to be busy.
GSM Foreign Mode: When an incoming call is forwarded on mobile subscriber busy with the condition network determined user busy (NDUB) the forward-to-party shall receive a notification that the call has been forwarded. The calling party may also receive a notification that the call has been forwarded.
ANSI-41 foreign mode: When an incoming call is forwarded due to a busy condition the served mobile subscriber may receive a notification that the call has been forwarded.
29
30
31
32
4.2.3.3.1 Call Detail Record / Charging Requirements
For GSM and ANSI-41 based network interoperability, no new or special recording capabilities are needed.
Ballot Version 27

1
N.S0028-0
2
3
4.2.3.4 Exception Procedures or Unsuccessful Outcome
10
11
12
13
8
9
4
5
6
7
4.2.3.4.1 Registration
If the system cannot accept a registration request, the served mobile subscriber shall receive a notification that call forwarding on mobile subscriber busy registration was not successful. Possible causes are: service not subscribed to; forward-to number is invalid directory number; use of an operator access prefix; insufficient information; forward-to number is a special service code (e.g., police); forward-to number is the directory number of the mobile subscriber herself.
14
15
16
4.2.3.4.2 De-Registration (Erasure)
If the subscriber is not authorized for the request, the system shall apply feature denial treatment when de-registration is attempted.
17
18
19
4.2.3.4.3 Activation
If the subscriber is not authorized for the request, or if a forward-to number is not properly registered, the system shall apply feature denial treatment when activation is attempted.
20
21
22
4.2.3.4.4 De-Activation
If the subscriber is not authorized for the request, the system shall apply feature denial treatment when de-activation is attempted.
23
24
25
26
27
28
29
4.2.3.4.5 Invocation
If the forwarded call cannot be routed to the forward-to destination, then the call shall be given the appropriate treatment, such as applying the Special Information Tone for intercept to the calling party.
Precautions shall be taken to preclude undesirable looping of forwarded numbers within the MSC or between the MSC and other switching centers. If such looping is detected, the call forwarding shall be given the appropriate treatment, such as applying the Special Information Tone for intercept to the calling party.
30
31
4.2.3.4.6 Exceptions While Roaming
None identified.
32
33
34
4.2.3.4.7 Exceptions During Intersystem Handoff
None identified.
Ballot Version 28

N.S0028-0
1
2
3
None identified.
4
5
4.2.3.6 Interactions With Other Features and Services
6
7
4.2.3.6.1 Advice of charge (AoC)
See GSM 02.86[19].
8
9
4.2.3.6.2 Barring of All Outgoing Calls (BAOC)
None identified at this time.
10
11
4.2.3.6.3 Barring of Outgoing International Calls (BOIC)
None identified at this time.
12
13
14
4.2.3.6.4 Barring of Outgoing International Calls except those directed to the Home PLMN
(BOIC-exHC)
None identified at this time.
15
16
4.2.3.6.5 Barring of All Incoming Calls (BAIC)
None identified at this time.
17
18
4.2.3.6.6 Barring of Incoming Calls when Roaming Outside the Home PLMN (BIC-Roam)
None identified at this time.
23
24
25
26
19
20
21
22
4.2.3.6.7 Call Delivery (CD)
CD affects CFB. That is, if CD is inactive while the subscriber is roaming, the subscriber is considered to be inaccessible. Even if the subscriber has CFB active, incoming calls shall be given the subscriber inaccessible treatment.
If CD is active and registered for a roaming subscriber, or if the subscriber is at home, CFB works normally.
If the call is delivered to the subscriber, the subscriber is busy, and the subscriber has CFB active, the call shall be diverted to the CFB forward-to number.
27
28
4.2.3.6.8 Call Forwarding—Busy (CFB)
Not applicable.
29
30
31
4.2.3.6.9 Call Forwarding—Default (CFD)
CFB takes precedence over CFD. That is, calls arriving to a busy subscriber with CFB and CFD 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
2
CFB is mutually exclusive with CFNA / CFNRy. That is, calls arriving to a busy subscriber with CFB and CFNA / CFNRy active shall be forwarded by CFB and not given CFNA / CFNRy treatment.
3
4
5
4.2.3.6.11 Call Forwarding—Not Reachable (CFNRc)
CFB is mutually exclusive with CFNRc. That is, calls arriving to a busy subscriber with CFB and
CFNRc active shall be forwarded by CFB and not given CFNRc treatment.
6
7
8
4.2.3.6.12 Call Forwarding—Unconditional (CFU)
CFU takes precedence over CFB. That is, calls arriving when CFU is active shall be forwarded unconditionally and not given CFB treatment.
9
10
4.2.3.6.13 Call Transfer (CT)
None identified.
11
12
13
14
15
16
17
4.2.3.6.14 Call Waiting / Call Hold (CW / HOLD)
CW is invoked before CFB. If a call arrives for a busy subscriber able to receive a second call, the called subscriber has both CW and CFB active, and no call is already waiting to be answered; the call is presented to the subscriber with CW notification. If the CW call is not accepted, CFB is not invoked.
If a call arrives for a busy subscriber, the called subscriber has both CW and CFB active, and if the called subscriber is unable to receive a second call or has a call waiting to be answered; the call shall be forwarded immediately by CFB.
18
19
20
21
4.2.3.6.15 Calling Number / Line Identification Presentation (CNIP / CLIP)
When a call has been forwarded and the forward-to user has been provided with the CNIP / CLIP supplementary service, the forward-to user shall receive the number of the original calling user, if this calling user has not subscribed to or invoked the CNIR / CLIR supplementary service.
22
23
24
25
26
27
4.2.3.6.16 Calling Number / Line Identification Restriction (CNIR / CLIR)
If the calling number indicates presentation restricted, the calling number shall not be presented to the called party, the called station, the forward-to party, or the forward-to station.
If the called (redirecting) subscriber has CFB invoked and either the CNIR mode is Permanently
Restricted or the CNIR Default is Presentation Restricted, the redirecting number shall indicate presentation restricted to prevent presentation to the forward-to party or to the forward-to station.
28
29
30
31
4.2.3.6.17 Calling Name Presentation (CNAP)
When a call has been forwarded and the forward-to user has been provided with the CNAP supplementary service, the forward-to user shall receive the name of the original calling user, if this calling user has not subscribed to or invoked the CNAR or CNIR / CLIR supplementary service.
32
33
34
35
36
37
38
4.2.3.6.18 Calling Name Restriction (CNAR)
If the calling name or number indicates presentation restricted, the calling name or number shall not be presented to the called party, the called station, the forward-to party, or the forward-to station.
If the called (redirecting) subscriber has CFB invoked and either the CNAR or CNIR mode is
Permanently Restricted, or the CNAR or CNIR Default is Presentation Restricted, the redirecting name shall indicate presentation restricted to prevent presentation to the forward-to party or to the forward-to station.
Ballot Version 30

N.S0028-0
1
2
4.2.3.6.19 Closed User Group (CUG)
See GSM 02.85[18].
3
4
4.2.3.6.20 Conference Calling / Multi Party Service (CC / MPTY)
None identified.
5
6
4.2.3.6.21 Do Not Disturb (DND)
None identified at this time.
7
8
4.2.3.6.22 Emergency Services
None identified at this time.
9
10
4.2.3.6.23 Flexible Alerting (FA)
None identified at this time.
11
12
4.2.3.6.24 Message Waiting Notification (MWN)
None identified.
13
14
4.2.3.6.25 Mobile Access Hunting (MAH)
None identified at this time.
15
16
4.2.3.6.26 Password Call Acceptance (PCA)
None identified at this time.
17
18
4.2.3.6.27 Preferred Language (PL)
None identified.
19
20
4.2.3.6.28 Priority Access and Channel Assignment (PACA)
None identified at this time.
21
22
23
4.2.3.6.29 Remote Feature Control (RFC)
CFB Registration shall be allowed via RFC in ANSI41136 mode, or via functional messaging in GSM mode.
24
25
4.2.3.6.30 Selective Call Acceptance (SCA)
None identified at this time.
26
27
4.2.3.6.31 Subscriber PIN Access (SPINA)
None identified at this time.
28
29
4.2.3.6.32 Subscriber PIN Intercept (SPINI)
None identified.
Ballot Version 31

N.S0028-0
1
2
4.2.3.6.33 Three-Way Calling / Multi Party Service (3WC / MPTY)
None identified.
3
4
4.2.3.6.34 Voice Message Retrieval (VMR)
None identified.
5
6
7
4.2.3.6.35 Voice Privacy (VP)
None identified.
Ballot Version 32

N.S0028-0
1
2
3
11
12
13
14
15
16
4
8
9
10
5
6
7
Call Forwarding—No Answer (CFNA) permits a called subscriber to have the system send incoming calls addressed to the called subscriber’s Directory Number to another Directory Number (forward-to number) or to the called subscriber’s designated voice mail box, when the subscriber fails to answer, or is otherwise inaccessible (including no paging response, the subscriber’s location is not known the subscriber is reported as inactive, Call Delivery not active for a roaming subscriber, Do Not Disturb active, etc.).
Call Forwarding No Reply (CFNRy) permits a called subscriber to have the system send all incoming calls, or just those associated with a specific Basic service group, addressed to the called mobile subscriber's directory number and which meet no reply to another directory number.
Call Forwarding Not Reachable (CFNRc) permits a called subscriber to have the system send all incoming calls, or just those associated with a specific Basic service group, addressed to the called mobile subscriber's directory number and which meet not reachable to another directory number.
17
18
4.2.4.1.1 Applicability to Telecommunications Services
CFNA/CFNRy/CFNRc is applicable to voice telecommunication services.
19
20
4.2.4.2 Normal Procedures With Successful Outcome
21
22
23
24
25
26
4.2.4.2.1 Authorization (or Provision)
CFNA/CFNRy/CFNRc may be generally available or may be provided after pre-arrangement with the service provider. The authorization (provision) may have subscription options. These options are defined in either GSM 02.82[15] (i.e., GSM native mode subscribers) or ANSI-664[1] (e.g., ANSI136
41, TDMA or CDMA native mode subscribers). Authorization or Provisioning may occur while operating in foreign mode.
27
28
29
4.2.4.2.2 De-Authorization (or Withdrawal)
CFNA/CFNRy/CFNRc may be withdrawn by the service provider, at the subscriber’s request, or for administrative reasons. De-authorization or withdrawal may occur while operating in foreign mode.
30
31
32
33
34
35
36
37
38
4.2.4.2.3 Registration
If the subscriber is authorized for Fixed Registration, the forward-to number shall be registered upon authorization (provision). Mobile stations operating in foreign mode may attempt to perform registration procedures normally supported in native mode.
The forward-to-number may be registered by the service provider upon authorization (provision) for
Variable Registration subscribers
GSM foreign mode: A forward-to-number may be registered by a Variable Registration authorized subscriber specifying the CFNA registration feature code and a forward-to number termination address as in:
Ballot Version 33

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

N.S0028-0
1
2
3
4
5
6
7
8
9
10
Alternatively, if the mobile station offers menu driven control of activation, the mobile station is expected to generate the equivalent GSM functional signaling.
ANSI-41 foreign mode: The MS shall be allowed to activate CFNRy/CFNRc by using an appropriate control procedure (e.g. using the MMI command described in GSM 02.30[11]). In ANSI-41 foreign mode, if the equivalent GSM feature code (MMI) is manually entered by the user, the mobile station is expected to issue the necessary ANSI13641 feature code to the network.
If the activation is accepted, the system shall indicate success using either GSM or ANSI13641 signaling techniques depending on the mode of operation.
The serving system may provide a courtesy call to the forward-to number shortly after this feature is activated permitting the subscriber to verify the validity of the forward-to-number.
11
12
13
14
21
22
23
24
25
15
16
17
18
19
20
4.2.4.2.6 De-Activation
GSM foreign mode: CFNA may be de-activated by a Demand Activation authorized subscriber specifying the CFNA de-activation feature code, as in:
FC0 + SEND .
Alternatively, if the mobile station offers menu driven control of de-activation, the mobile station is expected to generate the equivalent GSM functional signaling.
ANSI-41 foreign mode: The user may deactivate CFNRy/CFNRc by means of an appropriate control procedure (e.g., as described in GSM 02.30[11]). In ANSI-41 foreign mode, if the equivalent GSM feature code (MMI) is manually entered by the user, the mobile station is expected to issue the necessary ANSI13641 feature code to the network.
If the de-activation is accepted, the system shall indicate success using either GSM or ANSI13641 signaling techniques depending on the mode of operation. Registered information shall not be erased.
CFNA/CFNRy/CFNRc shall be de-activated upon de-authorization (withdrawal) or de-registration
(erasure).
26
27
28
4.2.4.2.7 Invocation
The feature treatment is invoked when there is an incoming call and either CFNA, CFNRy or CFNRc is active and the necessary conditions have been met – see GSM 02.82[15] and ANSI-664[1].
29
30
31
32
33
34
35
36
4.2.4.3 Normal Operation with Successful Outcome
When CFNA/CFNRy/CFNRc is active, incoming calls for the subscriber shall be forwarded due to not reachable (e.g., no response to paging) or no reply to the forward-to number.
GSM Foreign Mode: When an incoming call is forwarded due to no reply or not reachable, the forward-to-party shall receive a notification that the call has been forwarded. The calling party may also receive a notification that the call has been forwarded.
ANSI-41 foreign mode: When an incoming call is forwarded due to no answer the served mobile subscriber may receive a notification that the call has been forwarded.
37
38
39
4.2.4.3.1 Call Detail Record / Charging Requirements
For GSM and ANSI-41 based network interoperability, no new or special recording capabilities are needed.
Ballot Version 35

1
N.S0028-0
2
3
4.2.4.4 Exception Procedures or Unsuccessful Outcome
9
10
11
12
7
8
4
5
6
4.2.4.4.1 Registration
If the system cannot accept a registration request, the served mobile subscriber shall receive a notification that registration of CFNA/CFNRy/CFNRc was not successful. Possible causes are: service not subscribed to; forward-to number is invalid directory number; use of an operator access prefix; insufficient information; forward-to number is a special service code (e.g., police); forward-to number is the directory number of the mobile subscriber herself.
13
14
15
4.2.4.4.2 De-Registration (Erasure)
If the subscriber is not authorized for the request, the system shall apply feature denial treatment when de-registration is attempted.
16
17
18
4.2.4.4.3 Activation
If the subscriber is not authorized for the request, or if a forward-to-number is not properly registered, the system shall apply feature denial treatment when activation is attempted.
19
20
21
4.2.4.4.4 De-Activation
If the subscriber is not authorized for the request, the system shall apply feature denial treatment when de-activation is attempted.
22
23
24
25
26
27
28
4.2.4.4.5 Invocation
If the forwarded call cannot be routed to the forward-to-destination, then the call shall be given the appropriate treatment, such as applying the Special Information Tone for intercept to the calling party.
Precautions shall be taken to preclude undesirable looping of forwarded numbers within the MSC or between the MSC and other switching centers. If such looping is detected, the call forwarding shall be given the appropriate treatment, such as applying the Special Information Tone for intercept to the calling party.
29
30
4.2.4.4.6 Exceptions While Roaming
None identified.
31
32
4.2.4.4.7 Exceptions During Intersystem Handoff
None identified.
33
Ballot Version 36

N.S0028-0
1 None identified.
2
3
4.2.4.6 Interactions With Other Features and Services
4
5
4.2.4.6.1 Advice of charge (AoC)
See GSM 02.86[19].
6
7
4.2.4.6.2 Barring of All Outgoing Calls (BAOC)
None identified at this time.
8
9
4.2.4.6.3 Barring of Outgoing International Calls (BOIC)
None identified at this time.
10
11
12
4.2.4.6.4 Barring of Outgoing International Calls except those directed to the Home PLMN
(BOIC-exHC)
None identified at this time.
13
14
4.2.4.6.5 Barring of All Incoming Calls (BAIC)
None identified at this time.
15
16
4.2.4.6.6 Barring of Incoming Calls when Roaming Outside the Home PLMN (BIC-Roam)
None identified at this time.
21
22
23
24
17
18
19
20
4.2.4.6.7 Call Delivery (CD)
CD affects CFNA. That is, if CD is inactive while the subscriber is roaming, the subscriber is considered to be inaccessible. If the subscriber has CFNA active, incoming calls shall be diverted to the CFNA forward-to number.
If CD is active and registered for a roaming subscriber, or if the subscriber is at home, CFNA works normally.
If the call is presented to the subscriber, the call is not answered, and the subscriber has CFNA active, the call shall be diverted to the CFNA forward-to number.
25
26
27
28
4.2.4.6.8 Call Forwarding—Busy (CFB)
CFB is mutually exclusive with CFNA/CFNRy/CFNRc. That is, calls arriving to a busy subscriber with
CFB and CFNA/CFNRy/CFNRc active shall be forwarded by CFB and not given
CFNA/CFNRy/CFNRc treatment.
29
30
31
4.2.4.6.9 Call Forwarding—Default (CFD)
CFNA takes precedence over CFD. That is, an incoming call to an inaccessible or non-answering subscriber with both CFNA and CFD active shall be forwarded using CFNA.
32 4.2.4.6.10 Call Transfer (CT)
Ballot Version 37

N.S0028-0
1
2
None identified.
Ballot Version 38

N.S0028-0
1
2
3
4
5
6
7
4.2.4.6.11 Call Waiting / Call Hold (CW / HOLD)
CW is invoked before CFNA/CFNRy. If a call arrives for a busy subscriber able to receive a second call, the called subscriber has both CW and CFNA/CFNRy active, and no call is waiting to be answered; the call is presented to the subscriber with CW notification. If the call is not answered within a period of time after applying the first CW notification, it shall be given no answer treatment.
CFNRc is invoked before CW.
8
9
10
11
4.2.4.6.12 Calling Number / Line Identification Presentation (CNIP / CLIP)
When a call has been forwarded and the forward-to user has been provided with the CNIP / CLIP supplementary service, the forward-to user shall receive the number of the original calling user, if this calling party has not subscribed to or invoked the CNIR / CLIR supplementary service.
12
13
14
15
16
17
4.2.4.6.13 Calling Number / Line Identification Restriction (CNIR / CLIR)
If the calling number indicates presentation restricted, the calling number shall not be presented to the called party or the forward-to-party.
If the called (redirecting) subscriber has CFNA/CFNRy/CFNRc active and CNIR is either Permanently
Restricted or the default is Presentation Restricted, the redirecting number shall indicate presentation restricted to prevent presentation to the forward-to-party or to the forward-to station.
18
19
20
21
4.2.4.6.14 Calling Name Presentation (CNAP)
When a call has been forwarded and the forward-to-party has been provided with the CNAP supplementary service, the forward-to user shall receive the name of the original calling user, if this calling user has not subscribed to or invoked the CNAR or CNIR / CLIR supplementary service.
22
23
24
25
26
27
4.2.4.6.15 Calling Name Restriction (CNAR)
If the calling name or number indicates presentation restricted, the calling name or number shall not be presented to the called party or the forward-to-party.
If the called (redirecting) subscriber has CFNA/CFNRy/CFNRc active and CNAR or CNIR is either
Permanently Restricted, or the default is Presentation Restricted, the redirecting name shall indicate presentation restricted to prevent presentation to the forward-to-party.
28
29
4.2.4.6.16 Closed User Group (CUG)
See GSM 02.85[18].
30
31
4.2.4.6.17 Conference Calling / Multi Party Service (CC / MPTY)
None identified.
32
33
4.2.4.6.18 Do Not Disturb (DND)
None identified at this time.
34
35
4.2.4.6.19 Emergency Services
None identified at this time.
Ballot Version 39

N.S0028-0
1
2
4.2.4.6.20 Flexible Alerting (FA)
None identified at this time.
3
4
4.2.4.6.21 Message Waiting Notification (MWN)
None identified.
5
6
4.2.4.6.22 Mobile Access Hunting (MAH)
None identified at this time.
7
8
4.2.4.6.23 Password Call Acceptance (PCA)
None identified at this time.
9
10
4.2.4.6.24 Preferred Language (PL)
None identified.
11
12
4.2.4.6.25 Priority Access and Channel Assignment (PACA)
None identified at this time.
13
14
15
4.2.4.6.26 Remote Feature Control (RFC)
CFNA/CFNRy/CFNRc Registration shall be allowed via RFC in ANSI13641 mode, or via functional messaging in GSM mode.
16
17
4.2.4.6.27 Selective Call Acceptance (SCA)
None identified at this time.
18
19
4.2.4.6.28 Subscriber PIN Access (SPINA)
None identified at this time.
20
21
4.2.4.6.29 Subscriber PIN Intercept (SPINI)
None identified.
22
23
4.2.4.6.30 Three-Way Calling / Multi Party Service (3WC / MPTY)
None identified.
24
25
4.2.4.6.31 Voice Message Retrieval (VMR)
None identified.
26
27
28
4.2.4.6.32 Voice Privacy (VP)
None identified.
Ballot Version 40

N.S0028-0
1
2
3
4
5
6
7
8
Call Forwarding—Default (CFD) permits a called subscriber to send incoming calls addressed to the called subscriber’s Directory Number to the subscriber’s designated voice mail box or to another
Directory Number (forward-to number), when the subscriber is engaged in a call, does not respond to paging, does not answer the call within a specified period after being alerted or is otherwise inaccessible (including no paging response, the subscriber’s location is not known, the subscriber is reported as inactive, Call Delivery not active for a roaming subscriber, Do Not Disturb active, etc.).
9
10
4.2.5.1.1 Applicability to Telecommunications Services
CFD is applicable to voice telecommunication services.
11
12
4.2.5.2 Normal Procedures With Successful Outcome
13
14
15
16
17
4.2.5.2.1 Authorization (or Provision)
CFD may be generally available or may be provided after pre-arrangement with the service provider.
The authorization (provision) may have subscription options. These options are defined in
ANSI-664[1] (e.g., ANSI136 41, TDMA or CDMA native mode subscribers). Authorization or
Provisioning may occur while operating in foreign mode.
18
19
20
4.2.5.2.2 De-Authorization (or Withdrawal)
CFD may be withdrawn by the service provider, at the subscriber’s request, or for administrative reasons. De-authorization or withdrawal may occur while operating in foreign mode.
30
31
32
33
34
25
26
27
28
29
21
22
23
24
4.2.5.2.3 Registration
If the subscriber is authorized for Fixed Registration, the forward-to number shall be registered upon authorization (provision). Mobile stations operating in foreign mode may attempt to perform registration procedures normally supported in native mode.
The forward-to-number may be registered by the service provider upon authorization (provision) for
Variable Registration subscribers
GSM foreign mode: A forward-to-number may be registered by a Variable Registration authorized subscriber specifying the CFD registration feature code and a forward-to number termination address as in:
FC + termination address + SEND .
Alternatively, if the mobile station offers menu driven control of registration, the mobile station is expected to generate the equivalent GSM functional signaling towards the network.
If the registration is accepted, the system shall indicate success using either GSM signaling techniques.
35
36
37
4.2.5.2.4 De-Registration (or Erasure)
Mobile stations operating in foreign mode, may attempt to perform De-Registration or Erasure procedures normally supported in native mode.
Ballot Version 41

N.S0028-0
6
7
8
9
1
2
3
4
5
A forward-to-number may be de-registered upon de-activation (at the home service provider option).
GSM foreign mode: If the de-registration is to be separate from de-activation, the de-registration feature code must be distinct from the corresponding de-activation feature code.
GSM foreign mode: CFD may be de-registered by a Variable Registration authorized subscriber specifying the CFD de-registration feature code, as in:
FC0 + SEND .
Alternatively, if the mobile station offers menu driven control of registration, the mobile station is expected to generate the equivalent GSM functional signaling towards the network.
CFD shall be de-registered upon de-authorization or withdrawal.
19
20
21
22
23
24
25
10
11
12
13
14
15
16
17
18
4.2.5.2.5 Activation
Mobile stations operating in foreign mode may attempt to perform Activation procedures normally supported in native mode.
If the subscriber is authorized for Permanent Activation, CFD shall be activated upon authorization
(provision).
CFD may be activated upon authorization or registration for Demand Activation authorized subscribers. CFD may be activated upon registration for Variable Registration authorized subscribers.
GSM foreign mode: A previously registered forward-to-number may be activated by a Demand
Activation authorized subscriber specifying a CFD activation feature code, as in:
FC + SEND .
Alternatively, if the mobile station offers menu driven control of activation, the mobile station is expected to generate the equivalent GSM functional signaling.
If the activation is accepted, the system shall indicate success using GSM or ANSI13641 signaling techniques.
The serving system may provide a courtesy call to the forward-to number shortly after this feature is activated permitting the subscriber to verify the validity of the forward-to-number.
26
27
28
29
30
31
32
33
34
35
4.2.5.2.6 De-Activation
GSM foreign mode: CFD may be de-activated by a Demand Activation authorized subscriber specifying the CFD de-activation feature code, as in:
FC0 + SEND .
Alternatively, if the mobile station offers menu driven control of de-activation, the mobile station is expected to generate the equivalent GSM functional signaling.
If the de-activation is accepted, the system shall indicate success using either GSM signaling techniques. Registered information shall not be erased.
CFD shall be de-activated upon de-authorization (withdrawal) or de-registration (erasure).
Ballot Version 42

N.S0028-0
1
2
3
4
4.2.5.2.7 Invocation
The feature treatment is invoked when there is an incoming call, CFD is active and the necessary conditions have been met – See ANSI-664[1].
8
9
10
5
6
7
4.2.5.3 Normal Operation with Successful Outcome
When CFD is active, incoming calls for the subscriber shall be forwarded due to not reachable (e.g., no response to paging), no reply, or busy to the forward-to number.
GSM Foreign Mode: When an incoming call is forwarded due to CFD, the forward-to-party shall receive a notification that the call has been forwarded. The calling party may also receive a notification that the call has been forwarded.
11
12
13
4.2.5.3.1 Call Detail Record / Charging Requirements
For GSM and ANSI-41 based network interoperability, no new or special recording capabilities are needed.
14
15
4.2.5.4 Exception Procedures or Unsuccessful Outcome
20
21
22
16
17
18
19
23
24
4.2.5.4.1 Registration
If the system cannot accept a registration request, the served mobile subscriber shall receive a notification that registration of CFD was not successful. Possible causes are: service not subscribed to; forward-to number is invalid directory number; use of an operator access prefix; insufficient information; forward-to number is a special service code (e.g., police); forward-to number is the directory number of the mobile subscriber herself.
25
26
27
4.2.5.4.2 De-Registration (Erasure)
If the subscriber is not authorized for the request, the system shall apply feature denial treatment when de-registration is attempted.
28
29
30
4.2.5.4.3 Activation
If the subscriber is not authorized for the request, or if a forward-to-number is not properly registered, the system shall apply feature denial treatment when activation is attempted.
31
32
33
34
4.2.5.4.4 De-Activation
If the subscriber is not authorized for the request, the system shall apply feature denial treatment when de-activation is attempted.
Ballot Version 43

1
N.S0028-0
2
3
4
5
6
7
8
4.2.5.4.5 Invocation
If the forwarded call cannot be routed to the forward-to-destination, then the call shall be given the appropriate treatment, such as applying the Special Information Tone for intercept to the calling party.
Precautions shall be taken to preclude undesirable looping of forwarded numbers within the MSC or between the MSC and other switching centers. If such looping is detected, the call forwarding shall be given the appropriate treatment, such as applying the Special Information Tone for intercept to the calling party.
9
10
4.2.5.4.6 Exceptions While Roaming
None identified.
11
12
4.2.5.4.7 Exceptions During Intersystem Handoff
None identified.
13
14 None identified.
15
16
17
18
19
4.2.5.6 Interactions With Other Features and Services
4.2.5.6.1 Call Delivery (CD)
CD affects CFD. That is, if CD is inactive while the subscriber is roaming, the subscriber is considered to be inaccessible. If the subscriber has CFD active, incoming calls shall be diverted to the CFD forward-to number.
20
21
22
4.2.5.6.2 Call Forwarding—Busy (CFB)
CFB takes precedence over CFD. That is, calls arriving to a busy subscriber with CFB and CFD active shall be forwarded by CFB and not given CFD treatment.
23
24
4.2.5.6.3 Call Transfer (CT)
None identified.
25
26
27
28
29
4.2.5.6.4 Call Waiting / Call Hold (CW / HOLD)
CW is invoked before CFD. If a call arrives for a busy subscriber able to receive a second call, the called subscriber has both CW and CFD active, and no call is waiting to be answered; the call is presented to the subscriber with CW notification. If the call is not answered within a period of time after applying the first CW notification, it shall be given no answer treatment.
30
31
32
33
4.2.5.6.5 Calling Number / Line Identification Presentation (CNIP / CLIP)
When a call has been forwarded and the forward-to user has been provided with the CNIP / CLIP supplementary service, the forward-to user shall receive the number of the original calling user, if this calling user has not subscribed to or invoked the CNIR / CLIR supplementary service.
34 4.2.5.6.6 Calling Number / Line Identification Restriction (CNIR / CLIR)
Ballot Version 44

N.S0028-0
1
2
3
4
5
If the calling number indicates presentation restricted, the calling number shall not be presented to the called party or the forward-to-party.
If the called (redirecting) subscriber has CFD active and CNIR is either Permanently Restricted or the default is Presentation Restricted, the redirecting number shall indicate presentation restricted to prevent presentation to the forward-to-party or to the forward-to station.
6
7
8
9
4.2.5.6.7 Calling Name Presentation (CNAP)
When a call has been forwarded and the forward-to-party has been provided with the CNAP supplementary service, the forward-to user shall receive the name of the original calling user, if this calling user has not subscribed to or invoked the CNAR or CNIR / CLIR supplementary service.
10
11
12
13
14
15
4.2.5.6.8 Calling Name Restriction (CNAR)
If the calling name or number indicates presentation restricted, the calling name or number shall not be presented to the called party or the forward-to-party.
If the called (redirecting) subscriber has CFD active and CNAR or CNIR is either Permanently
Restricted, or the default is Presentation Restricted, the redirecting name shall indicate presentation restricted to prevent presentation to the forward-to-party.
16
17
4.2.5.6.9 Closed User Group (CUG)
See GSM 02.85[18].
18
19
4.2.5.6.10 Conference Calling / Multi Party Service (CC / MPTY)
None identified.
20
21
4.2.5.6.11 Do Not Disturb (DND)
None identified at this time.
22
23
4.2.5.6.12 Emergency Services
None identified at this time.
24
25
4.2.5.6.13 Flexible Alerting (FA)
None identified at this time.
26
27
4.2.5.6.14 Message Waiting Notification (MWN)
None identified.
28
29
4.2.5.6.15 Mobile Access Hunting (MAH)
None identified at this time.
30
31
4.2.5.6.16 Password Call Acceptance (PCA)
None identified at this time.
32 4.2.5.6.17 Preferred Language (PL)
Ballot Version 45

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

N.S0028-0
1
2
3
4.2.5.6.18 Priority Access and Channel Assignment (PACA)
None identified at this time.
4
5
6
4.2.5.6.19 Remote Feature Control (RFC)
CFD Registration shall be allowed via RFC in ANSI13641 mode, or via functional messaging in GSM mode.
7
8
4.2.5.6.20 Selective Call Acceptance (SCA)
None identified at this time.
9
10
4.2.5.6.21 Subscriber PIN Access (SPINA)
None identified at this time.
11
12
4.2.5.6.22 Subscriber PIN Intercept (SPINI)
None identified.
13
14
4.2.5.6.23 Three-Way Calling / Multi Party Service (3WC / MPTY)
None identified.
15
16
4.2.5.6.24 Voice Message Retrieval (VMR)
None identified.
17
18
4.2.5.6.25 Voice Privacy (VP)
None identified.
Ballot Version 47

N.S0028-0
1
2
12
13
14
15
7
8
9
10
11
3
4
5
6
16
17
Optimal Routing for Late Call Forwarding is a network feature which enables calls for a mobile subscriber who is not available to be routed from the called party HPLMN directly to a specified forward-to destination.
In GSM Optimal Routing for Late Call Forwarding by the HPLMN is a subset of the capabilities provided in GSM Support for Optimal Routing (SOR) Phase I per GSM 02.79[13]. With SOR, the interrogating PLMN (IPLMN) decides whether or not to optimize routing by taking into account information provided by the called party HPLMN. The HPLMN can decide, on a call-by-call basis, whether or not to allow OR.
GSM SOR provides additional capabilities for OR under other conditions and by systems other than the HPLMN, which are outside the scope of this feature.
In ANSI-41 networks Optimal Routing for Late Call Forwarding can be provided automatically for every call by ANSI-41 call delivery procedures, and is not considered a supplementary service.
OR is a network feature, and therefore is transparent to the subscriber, except possibly in charging.
There is no subscriber initiated registration, activation, or invocation.
18
19
20
4.3.1.1 Applicability to Telecommunications Services
Optimal Routing for Late Call Forwarding is applicable to all circuit switched Telecommunications
Service.
28
29
30
31
32
21
22
23
24
25
26
27
33
34
35
36
37
38
39
Optimal Routing for Late Call Forwarding refers to the scenario in which party A (mobile or wireline) attempts to call mobile subscriber B who may have calls forwarded to party C (mobile or wireline). In
GSM, the consideration of whether or not to invoke OR depends upon the relative locations HPLMN-
B, VPLMN-B, and HPLMN-C. Both the HPLMN-B and the VPLMN-B must be capable of supporting
Optimal Routing for Late Call Forwarding. The VPLMN-B determines if Optimal Routing for Late Call
Forwarding is feasible, but the HPLMN-B controls the invocation of this feature.
Using GSM terminogy, the interrogating PLMN (IPLMN) in the following scenario is HPLMN-B.
Party A originates a call to party B. A may be a fixed or mobile subscriber, and A may be in any country.
HPLMN- B acts as the interrogating PLMN, and launches a query to the HLR to determine the location and status of B.
If the response from the HLR indicates that B is active and reachable, then HPLMN-B proceeds to initiate call setup to VPLMN-B.
Upon receipt of call setup request from HPLMN-B, VPLMN-B proceeds to page B. If call cannot be completed successfully (e.g., Busy, No Page Response or No Answer), and B has call forwarding active, then HPLMN-B proceeds to initiate call forwarding to the forward-to number. Call setup to the forward to party is done directly from HPLMN-B rather than through VPLMN-B. Without optimal 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
1
2
For GSM and ANSI-41 based network interoperability, no new or special recording capabilities are needed.
3
4
5
6
4.3.3.1 Non-support for OR in the called party HPLMN
If the HPLMN of the called party is a GSM system which does not support OR, Optimal Routing for
Late Call Forwarding cannot be invoked.
7
8
9
10
4.3.3.2 Non-support for OR in the called party VPLMN
If a subscriber whose HPLMN is an ANSI-41 or GSM system that supports OR registers in a VPLMN with a GSM system that does not support OR, then Optimal Routing for Late Call Forwarding cannot be invoked.
11
12
13
14
15
4.3.3.3 Calls to special mobile network numbers
If the called number is a special mobile network number of the HPLMN and the HPLMN is a GSM system, then the HPLMN has to guarantee that the call terminates at the correct destination. This can be achieved by denying OR for this call or by sending an appropriate error cause, or by implementing special handling.
16
17 None identified.
18
19
4.3.3.5 Exceptions during Intersystem Handoff
None identified.
20
21 None identified.
22
23
24
25
4.3.5.1 Advice of Charge
Depending on the particular call scenario, AoC may not work properly. For example, the subscriber may be charged a rate that is associated with non-optimal routing.
26
27
4.3.5.2 Barring of All Outgoing Calls (BAOC)
None identified.
28
29
4.3.5.3 Barring of Outgoing International Calls (BOIC)
None identified.
30
31
32
4.3.5.4 Barring of All Incoming Calls (BAIC)
BAIC takes precedence over Optimal Routing for Late Call Forwarding, and all incoming calls are given denial treatment.
Ballot Version 49

N.S0028-0
1
2
Barring of Incoming Calls when Roaming Outside the Home PLMN Country (BIC-Roam)
No impact.
3
4
5
6
4.3.5.5 Call Forwarding Busy (CFB)
The interaction between Optimal Routing for Late Call Forwarding and CFB is as described in 4.3.1 above. Optimal Routing for Late Call Forwarding does not impact the forwarded number or the ultimate call delivery to the forwarded party – only intermediate routing.
7
8
9
10
4.3.5.6 Call Forwarding Default (CFD)
The interaction between Optimal Routing for Late Call Forwarding and CFD is as described in 4.3.1 above. Optimal Routing for Late Call Forwarding does not impact the forwarded number or the ultimate call delivery to the forwarded party – only intermediate routing.
11
12
13
14
4.3.5.7 Call Forwarding Busy No Answer / No Reply (CFNA)
The interaction between Optimal Routing for Late Call Forwarding and CFNA is as described in 4.3.1.
Optimal Routing for Late Call Forwarding does not impact the forwarded number or the ultimate call delivery to the forwarded party – only intermediate routing.
15
16
17
18
4.3.5.8 Call Forwarding—Not Reachable (CFNRc)
There is no interaction between Optimal Routing for Late Call Forwarding and CFU since CFU is invoked in the called party HPLMN before call setup to the serving system is initiated. (ANSI-41: it depends on when paging occurs!).
19
20
21
4.3.5.9 Call Forwarding Unconditional (CFU)
There is no interaction between Optimal Routing for Late Call Forwarding and CFU since CFU is invoked in the called party HPLMN before call setup to the serving system is initiated.
22
23
4.3.5.10 Call Transfer (CT)
None identified.
24
25
4.3.5.11 Call Waiting / Call Hold (CW / HOLD)
None identified.
26
27
4.3.5.12 Calling Number / Line Identification Presentation (CNIP / CLIP)
None identified.
28
29
4.3.5.13 Calling Number / Line Identification Restriction (CNIR / CLIR)
None identified.
30
31
4.3.5.14 Calling Name Presentation (CNAP)
None identified.
32
33
4.3.5.15 Calling Name Restriction (CNAR)
None identified.
Ballot Version 50

N.S0028-0
1
2
4.3.5.16 Closed User Group (CUG)
None identified.
3
4
4.3.5.17 Do Not Disturb (DND)
Same as CFU.
5
6
4.3.5.18 Emergency Services
None identified.
7
8
4.3.5.19 Law Enforcement or CALEA
None identified.
9
10
4.3.5.20 Message Waiting Notification (MWN)
None identified.
11
12
4.3.5.21 Mobile Access Hunting (MAH)
None identified.
13
14
4.3.5.22 Password Call Acceptance (PCA)
Applicable to ANSI-136 ( ANSI-41 ) networks only. None identified.
15
16
4.3.5.23 Preferred Language (PL)
None identified.
17
18
4.3.5.24 Priority Access and Channel Assignment (PACA)
Applicable to ANSI-136 ( ANSI-41 ) networks only. None identified.
19
20
4.3.5.25 Remote Feature Control (RFC)
Applicable to ANSI-136 ( ANSI-41 ) networks only. None identified.
21
22
23
4.3.5.26 Selective Call Acceptance (SCA)
Applicable to ANSI-136 ( ANSI-41 ) networks only. Callers that are not able to provide the correct password are given denial treatment. Calls that are allowed may be subjected to OR treatment.
24
25
4.3.5.27 Subscriber PIN Access (SPINA)
Applicable to ANSI-136 ( ANSI-41 ) networks only. None identified.
26
27
4.3.5.28 Subscriber PIN Intercept (SPINI)
Applicable to ANSI-136 ( ANSI-41 ) networks only. None identified.
28
29
4.3.5.29 Voice Message Retrieval (VMR)
None identified.
Ballot Version 51

N.S0028-0
1
2
4.3.5.30 Voice Privacy (VP)
None identified.
3
4
5
4.3.5.31 3-Way Calls or Conference Calls
None identified.
Ballot Version 52

N.S0028-0
1
2
3
4
5
6
7
8
9
10
11
12
13
Call Waiting (CW) provides notification to a controlling subscriber of an incoming call while the subscriber’s call is in the 2-way state. Subsequently, the controlling subscriber can either answer or ignore the incoming call. If the controlling subscriber answers the second call, it may alternate between the two calls.
This service operates when the traffic channel at the controlling subscriber is not available and is engaged in an active or held call. When a third party attempts to connect to that termination, the controlling subscriber is given an appropriate indication of the waiting call. The maximum number of waiting calls at one time per mobile access is one. In ANSI13641 mode, this means that no further calls are offered to the subscriber while a call is waiting. In GSM mode, another call can be offered to the subscriber while a call is waiting, but only one call may be waiting at any time.
14
15
16
4.4.1.1 Applicability to Telecommunications Services
Call Waiting is applicable to circuit switched voice telecommunications services.
17
18
23
24
25
26
19
20
21
22
4.4.2.1 Authorization (or Provision)
No new authorization procedures are needed for either GSM or ANSI-41 foreign mode operation of call waiting. The following describes authorization procedures for both GSM and ANSI13641 native modes.
CW may be generally available or may be provided after pre-arrangement with the service provider.
GSM native subscriber: This supplementary service is provisioned for all Basic services subscribed to and to which it is applicable, i.e. not provisioned to any subset of these BS.
ANSI41136 native subscriber: CW may be authorized for the following options:
27
Activation
Table 1: CW Subscription Options
Subscription Options
Temporary Cancellation
Values
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.
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

1
N.S0028-0
2
3
4.4.2.2 De-Authorization (or Withdrawal)
CW may be withdrawn at the subscriber’s request or for administrative reasons.
4
5
4.4.2.3 Registration
CW has no registration.
6
7
4.4.2.4 De-Registration (or Erasure)
CW has no de-registration.
18
19
20
21
22
23
24
8
9
10
11
12
13
14
15
16
17
4.4.2.5 Activation
In both GSM and ANSI-41 foreign modes, the subscriber shall be provided with menu selections by the mobile station to allow him/or her to activate the call waiting feature. Menu selections shall also be available to the subscriber while in native mode as well. In addition, the user may also be able to activate call waiting (depending on individual service provider’s preference) through the use of the keypad, as follows:
ANSI13641 native and foreign modes:
CW may be activated upon authorization.
CW may be activated by a Demand Activation authorized subscriber specifying a CW activation feature code, as in:
FC +
SEND
.
If the activation is accepted, the system shall indicate success with feature confirmation treatment.
GSM native and foreign modes: This supplementary service shall be activated either collectively for all applicable Basic Services or on a Basic Service group basis by the subscriber using a control procedure, as specified in GSM 02.30[11], or by the service provider. The controlling subscriber shall be informed by the network of the success or otherwise of her action.
32
33
34
35
25
26
27
28
29
30
31
36
4.4.2.6 De-Activation
In both GSM and ANSI-41 foreign modes, the subscriber shall be provided with menu selections by the mobile station to allow him/or her to de-activate the call waiting feature. Menu selections shall also be available to the subscriber while in native mode as well. In addition, the user may also be able to de-activate call waiting (depending on individual service provider’s preference) through the use of the keypad, as follows:
ANSI13641 native and foreign mode:
CW shall be de-activated upon de-authorization.
CW Demand De-Activation:
CW may be de-activated by a Demand Activation authorized subscriber specifying a CW de-activation feature code, as in:
FC0 + SEND .
Ballot Version 54

N.S0028-0
5
9
10
11
6
7
8
1
2
3
4
12
13
14
15
16
17
18
19
20
21
22
23
If the de-activation is accepted, the system shall indicate success with feature confirmation treatment.
Temporary Cancellation During a Call (ANSI13641 Native Mode Only):
CW may be canceled during a single call by a Demand Cancellation authorized subscriber issuing a flash request and then specifying a CCW feature code, as in:
FC0 + SEND .
If the cancellation is accepted, the system may indicate success with feature confirmation treatment and then reconnect the call. At the completion of the call, CW shall resume the activation state prior to using the cancel CW feature code.
Temporary Cancellation With a Call Setup Request (ANSI13641 Native Mode Only):
CW may be canceled for a single call concurrently with a call request by a Demand Cancellation authorized subscriber specifying a CCW feature code and a termination address, as in:
FC0 + # + termination address + SEND .
Alternatively:
FC + termination address + SEND is possible, if a fixed length Temporary Cancellation feature code is distinct from the de-activation feature code.
If the cancellation is accepted, the system may indicate success with feature confirmation treatment and then the call is allowed to proceed toward the termination address. At the completion of the call,
CW shall resume the activation state prior to using the cancel CW feature code.
GSM native and foreign mode: The service shall be deactivated either collectively for all applicable
Basic Services or on a Basic Service group basis by the subscriber using a control procedure, as specified in GSM 02.30[11], or by the service provider. The controlling subscriber shall be informed by the network of the success or otherwise of her action.
24
25
26
27
28
29
30
4.4.2.7 Invocation
CW is invoked when a incoming call attempt arrives for a subscriber who is already engaged in conversation on a prior call, who does not have another call waiting, and who has CW active.
There are functions or actions which exist on GSM (in GSM 02.83[16]), but do not exist in ANSI-
13641 , and vice versa (see charts below). In order to achieve a seamless user Interface when roaming, it would be better to either provide the menu selections as it is in a GSM handset, or some other mechanism that can achieve the same goal.
31
32
33
34
35
36
37
38
39
40
Menu selections shall be provided by the mobile station, in both foreign and native modes, to allow the subscriber to control the operation of calls involving call waiting. Because, in general, GSM networks provide more capabilities related to call waiting operation, the menu-driven procedures may be different for a given subscriber depending on whether the serving network is GSM or ANSI13641 .
In addition to the use of menu selections, a subscriber may use the keypad entries (shown in the tables below) to control the operation of calls involving call waiting. Note that the subscriber would need to use different set of keypad entries depending on whether the serving network is GSM or
ANSI13641 , and thus the use of the shown keypad entries to control the operation of the calls is not encouraged. In general, the menu-driven approach would be preferred instead.
Ballot Version 55

N.S0028-0
1
2
The following tables describe the call party actions and system reactions for CW on GSM and ANSI-
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 13641 System Reaction
Action Party Action
A call arrives from a calling party for a controlling subscriber in a two-way conversation and with
CW active.
A call arrives from a calling party for a controlling subscriber in a two-way conversation and with CW active.
CW notification is applied to the controlling subscriber. The CW notification is repeated once if the waiting call is not answered.
Audible ringing is applied to the calling party until the call is answered or given no answer treatment. Go to the 2-way CW notification state.
Ballot Version 56

N.S0028-0
5
6
1
2
3
The CW notification may be an audible Call Waiting Tone injected into the voice path, a message on the alphanumeric display, or both.
4 Table 3: 2-Way Notification State for Call Waiting
State 2-way CW The controlling subscriber is in a two-way notification conversation with the other party and call waiting notification is applied.
GSM Called Party ANSI4 1 36 System Reaction
Action Party Action
The controlling subscriber signals a flash request by pressing 2 +
SEND
The controlling subscriber requests a disconnect by pressing the
END
SEND
key .
key.
The controlling subscriber signals a flash request by pressing 1 +
key .
The controlling subscriber signals a flash request by pressing 0 +
SEND
key .
The controlling subscriber signals a flash request by pressing the SEND key without digits.
The controlling subscriber requests a disconnect by pressing the key.
No equivalent function.
No equivalent function.
END
Remove the call waiting notification. Place the other party on hold. Connect the controlling subscriber and the calling party. Go to the
2-way CW state.
Release the other party.
Remove the call waiting notification. Apply the alerting to the controlling subscriber for the calling party. Go to the Alerting state.
Release the other party.
Remove the call waiting notification. Connect the controlling subscriber and the calling party. Go to the
2-way CW notification state.
Remove the call waiting notification. Place the UDUB condition to the calling party for busying treatment. Go to the 2-way CW notification state.
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.
GSM Called Party ANSI4 1 36 System Reaction
Action party Action
The controlling subscriber signals a flash request by pressing 2 + SEND key.
No equivalent function.
The controlling subscriber signals a flash request by pressing the SEND key without digits.
The controlling subscriber requests a disconnect by pressing the
END key.
The controlling subscriber signals a flash request by pressing 1+ key.
SEND
The controlling subscriber signals a flash request by pressing 0+ SEND key.
The controlling subscriber requests a disconnect by pressing the END key.
No equivalent function.
No equivalent function.
No equivalent function.
Place the other party on hold. Connect the controlling subscriber and the third party.
Remain in the 2-way CW state.
Release the other party.
Apply the recall distinctive alerting for the third party to recall the controlling subscriber. Optionally apply audible alerting to the held party. Go to the
Alerting state.
Release the other party.
Connect the controlling subscriber and the held party. Go to the 2-way
CW notification state.
The held party is released. Remain in the
2-way CW state.
Release all calls.
2
3
4
5
4.4.3.1 Call Detail Record / Charging Requirements
For GSM and ANSI-41 based network interoperability, no new or special recording capabilities are needed.
6
7
8
4.4.3.2 Interrogation
In foreign modes, the interrogation procedure is not supported.
GSM native mode
Ballot Version 58

N.S0028-0
1
2
3
4
The controlling subscriber may interrogate the network by the use of a control procedure, as specified in GSM 02.30[11]. The network shall respond with an appropriate indication telling the subscriber whether the service is supported in this network and, if so, provide a list of all Basic Service groups to which the Call waiting supplementary service is active.
5
6
7
8
4.4.4.1 Registration
None identified.
9
10 None identified.
11
12
13
4.4.4.3 Activation
If the subscriber is not authorized for the request, the system shall apply feature denial treatment when activation is attempted.
14
15
16
17
18
19
20
21
4.4.4.4 De-Activation
Demand De-Activation: If the subscriber is not authorized for the request, the system shall apply feature denial treatment when de-activation is attempted.
Temporary Cancellation (ANSI13641 native mode only): If the subscriber is not authorized for the request, the system shall apply feature denial treatment when de-activation is attempted.
Temporary Cancellation With a Call Setup Request (ANSI13641 native mode only): If the subscriber is not authorized for a Temporary Cancellation request made concurrently with a call setup request, the system shall apply feature denial treatment and the call setup shall be denied.
22
23
24
4.4.4.5 Invocation
If the controlling subscriber is not authorized, if the controlling subscriber is alerting the other party, or if resources are not available; give the calling party busy treatment. Remain in the 2-way state.
25
26 None identified.
27
28
4.4.4.7 Exceptions During Intersystem Handoff
None identified.
29
30 None identified.
31
32
Ballot Version 59

N.S0028-0
1
2
4.4.6.1 Advice of charge (AoC)
None identified.
3
4
4.4.6.2 Barring of All Outgoing Calls (BAOC)
None identified.
5
6
4.4.6.3 Barring of Outgoing International Calls (BOIC)
None identified.
7
8
9
4.4.6.4 Barring of Outgoing International Calls except those directed to the Home PLMN
(BOIC-exHC)
None identified.
10
11
4.4.6.5 Barring of All Incoming Calls (BAIC)
None identified.
12
13
4.4.6.6 Barring of Incoming Calls when Roaming Outside the Home PLMN (BIC-Roam)
None identified.
14
15
16
17
18
19
20
4.4.6.7 Call Delivery (CD)
No interactions between CD and CW in foreign mode.
While the subscriber is in native mode, CD may affect CW. That is, if CD is inactive while the subscriber is roaming, the subscriber is considered to be inaccessible. Even if the subscriber has CW active, incoming calls shall be given the subscriber inaccessible treatment.
If CD is active and registered for a roaming subscriber, or if the subscriber is at home, CW works normally.
21
22
23
24
25
26
27
CW is invoked before CFB. If a call arrives for a busy subscriber able to receive a second call, the called subscriber has both CW and CFB active, and no call is already waiting to be answered; the call is presented to the subscriber with CW notification. If the CW call is not accepted, CFB is not invoked.
If a call arrives for a busy subscriber, the called subscriber has both CW and CFB active, and if the called subscriber is unable to receive a second call or has a call waiting to be answered; the call shall be forwarded immediately by CFB.
28
29
30
31
32
33
34
35
CW is invoked before CFD. If a call arrives for a busy subscriber able to receive a second call, the called subscriber has both CW and CFD active, and no call is waiting to be answered; the call is presented to the subscriber with CW notification. If the call is not answered within a period of time after applying the first CW notification, it shall be given no answer treatment.
If a call arrives for a busy subscriber, the called subscriber has both CW and CFD active, and if the called subscriber is unable to receive a second call or has a call waiting to be answered; the call shall be forwarded immediately by CFD.
Ballot Version 60

N.S0028-0
1
2
3
4
5
6
7
8
4.4.6.10 Call Forwarding—No Answer / No Reply (CFNA / CFNRy)
CW is invoked before CFNA. If a call arrives for a busy subscriber able to receive a second call, the called subscriber has both CW and CFNA active, and no call is waiting to be answered; the call is presented to the subscriber with CW notification. If the call is not answered within a period of time after applying the first CW notification, it shall be given no answer treatment.
If a call arrives for a busy subscriber, the called subscriber has both CW and CFNA active, and if the called subscriber is unable to receive a second call or has a call waiting to be answered; the call shall be given busy treatment.
9
10
4.4.6.11 Call Forwarding—Not Reachable (CFNRc)
None identified.
11
12
13
4.4.6.12 Call Forwarding—Unconditional (CFU)
CFU takes precedence over CW. That is, calls arriving when CFU is active are forwarded unconditionally and not given CW treatment.
14
15
16
4.4.6.13 Call Transfer (CT)
CT and CW are mutually exclusive. A call incoming to a controlling subscriber setting up or engaged in a CT shall be given busy treatment, even if the called subscriber has CW active.
17
18
4.4.6.14 Call Waiting / Call Hold (CW / HOLD)
Not applicable.
19
20
21
4.4.6.15 Calling Number / Line Identification Presentation (CNIP / CLIP)
If the called subscriber has CNIP and CW active, the CNI shall be presented with the CW notification according to CNIP’s procedures.
22
23
4.4.6.16 Calling Number / Line Identification Restriction (CNIR / CLIR)
None identified.
24
25
4.4.6.17 Calling Name Presentation (CNAP)
None identified.
26
27
4.4.6.18 Calling Name Restriction (CNAR)
None identified.
28
29
4.4.6.19 Closed User Group (CUG)
None identified.
30
31
32
4.4.6.20 Conference Calling / Multi Party Service (CC / MPTY)
CC takes precedence over CW. If CC is invoked, CW shall not be invoked for an incoming call and the subscriber shall be considered to be busy.
33 4.4.6.21 Do Not Disturb (DND)
Ballot Version 61

N.S0028-0
1
2
DND takes precedence over CW. That is, calls arriving for a subscriber with DND and CW active shall be refused and not be given CW treatment.
3
4
4.4.6.22 Emergency Services
None identified.
5
6
7
8
9
4.4.6.23 Flexible Alerting (FA)
CW of the FA Pilot Directory Number shall apply to calls to the Pilot Directory Number when the FA group is considered to be busy, but one or more members that have CW active are able to accept a
CW call. CW alerting shall be applied to the members of the FA group able to accept a CW call. If the
FA Pilot Directory Number does not have CW active, CW may not apply.
10
11
12
13
14
15
16
17
4.4.6.24 Message Waiting Notification (MWN)
MWN pip tone may not be applied if the affected subscriber has requested CW cancellation or has
CW de-active.
MWN pip tone shall not be applied for the call waiting legs of a call.
The CW activation feature code may be the same as the MWN pip tone activation feature code. The
CW de-activation feature code may be the same as the MWN pip tone de-activation feature code.
The Cancel Call Waiting (CCW) feature code may be the same as the Cancel Message Waiting
Notification (CMWN) feature code.
18
19
20
21
22
23
24
25
26
4.4.6.25 Mobile Access Hunting (MAH)
Interaction between MAH and CW is beyond the scope of this Standard. The following describes a possible implementation:
For a single user MAH group, CW may be applied to a busy MAH member.
For a multiple user MAH group, CW of the MAH Pilot Directory Number shall apply to calls to the Pilot
Directory Number when the MAH group is considered to be busy, but one or more of the MAH members that have CW active are able to accept a CW call. CW alerting shall be applied to the members of the MAH group able to accept a CW call. If the MAH Pilot Directory Number does not have CW active, CW may not apply.
27
28
29
4.4.6.26 Password Call Acceptance (PCA)
PCA takes precedence over CW. Incoming calls to the subscriber with PCA and CW active shall be screened by the PCA feature before being considered for CW.
30
31
4.4.6.27 Preferred Language (PL)
None identified.
32
33
34
4.4.6.28 Priority Access and Channel Assignment (PACA)
PACA has precedence over CW. The CW feature shall not be invoked for incoming calls to a subscriber waiting for a PACA channel, as the subscriber shall be considered to be busy.
35
36
4.4.6.29 Remote Feature Control (RFC)
None identified.
Ballot Version 62

N.S0028-0
1
2
3
4.4.6.30 Selective Call Acceptance (SCA)
SCA takes precedence over CW. Incoming calls to the subscriber with SCA and CW active shall be screened by the SCA feature before being considered for CW.
4
5
4.4.6.31 Subscriber PIN Access (SPINA)
CW feature code requests shall be denied for an MS while SPINA is active.
6
7
4.4.6.32 Subscriber PIN Intercept (SPINI)
None identified.
8
9
10
11
12
13
14
4.4.6.33 Three-Way Calling / Multi Party Service (3WC / MPTY)
3WC and CW are mutually exclusive. A call incoming to a controlling subscriber setting up or engaged in a three-way call shall be given busy treatment, even if the called subscriber has CW active.
A flash request from a subscriber authorized for 3WC, while CW alerting is being applied, shall be used to respond to the CW call. If the controlling subscriber still desires a three-way call, it must first dispose of the CW call before requesting a three-way call.
15
16
4.4.6.34 Voice Message Retrieval (VMR)
None identified.
17
18
19
4.4.6.35 Voice Privacy (VP)
None identified.
Ballot Version 63

N.S0028-0
1
2
3
4
5
6
7
8
9
10
11
12
13
ANSI13641 Mode: Three-Way Calling (3WC) provides the subscriber the capability of adding a third party to an established two-party call, so that all three parties may communicate in a three-way call. If either of the two non-controlling parties to an established three-way call disconnects, the remaining party is re-connected to the controlling subscriber as a normal two-party call. If the controlling subscriber of a three-way call disconnects, the conference circuit and all other parties are released.
Digits included with flash requests when a termination address is not expected may be ignored.
Native mode user interface capabilities while operating in foreign mode are mobile station dependent.
GSM Mode: Once a multi-party call is active, remote parties may be added, disconnected or separated (i.e. removed from the multi-party call but remain connected to the served mobile subscriber). The maximum number of remote parties is 5.
14
15
4.5.1.1 Applicability to Telecommunications Services
3WC/MPTY is applicable to voice telecommunication services.
16
17
18
19
20
21
22
23
4.5.2.1 Authorization (or Provision)
GSM native subscribers: This supplementary service is provisioned for all Basic services subscribed to and to which it is applicable, i.e. not provisioned to any subset of these BS. The provision of the Call Hold supplementary service is also required.
ANSI13641 native subscribers: 3WC may be generally available or may be provided after prearrangement with the service provider.
24
25
4.5.2.2 De-Authorization (or Withdrawal)
3WC/MPTY may be withdrawn at the subscriber’s request or for administrative reasons.
26
27
4.5.2.3 Registration
3WC/MPTY has no registration.
28
29
4.5.2.4 De-Registration (or Erasure)
3WC/MPTY has no de-registration.
30
31
4.5.2.5 Activation
3WC/MPTY is activated upon authorization.
32
33
4.5.2.6 De-Activation
3WC/MPTY shall be de-activated upon de-authorization.
Ballot Version 64

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

N.S0028-0
13
14
15
16
17
18
19
7
8
9
10
11
12
5
6
1
2
3
4
If the third party answers, the system allows a conversation with the third party.
If the third party disconnects, the system releases the third party. Connects the held party.
If an incoming call arrives for the controlling subscriber, the system applies busy treatment to the calling party.
If the held party disconnects, the system releases the held party.
4. A connection is established between the controlling subscriber, a second party and a third party.
If the controlling subscriber presses the SEND key without digits, the system releases the third party. Connect the controlling subscriber and the second party.
If the controlling subscriber presses the END key, the system releases the controlling subscriber and two other parties.
If the controlling subscriber enters digits + SEND key, the system ignores any accompanying digits. Releases the third party. Connect the controlling subscriber and the second party.
If the third party answers, the system allows a conversation with the third party.
If the third party disconnects, the system releases the third party and connects the controlling subscriber and the second party.
If an incoming call arrives for the controlling subscriber, the system applies busy treatment to the calling party.
If the second party disconnects, the system releases the second party. Connect the controlling subscriber and the third party.
20
21
22
Only the served mobile subscriber shall be able to add remote parties to the multi-party call as specified in GSM 02.84[17].
23
24
25
26
4.5.3.2.1 Beginning the multi-party call
When the served mobile subscriber invokes multi-party, the network joins the active call and the call on hold together into a multi-party call in which the served mobile subscriber and the remote parties can all communicate with one another.
27
28
29
30
31
32
33
34
35
36
37
4.5.3.2.2 Managing an active multi-party call
During an active multi-party call, the served mobile subscriber shall be able to:
1. Add another remote party, to which a private communication has been established, if the number of remote parties does not then exceed the maximum number allowed, which results in an active multi-party call.
A MPTY invoke notification shall be sent towards all remote parties. A Retrieve notification
(according to GSM 02.83[16]) shall be sent towards all previously held remote parties.
2. Put the connection to multi-party call on hold:
(i.e., place her connection to the multi-party call on hold (and typically later retrieve it)). The served mobile subscriber may make an enquiry call (e.g., to a potential new remote party) or process a
Ballot Version 66

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

N.S0028-0
8
9
10
4
5
6
7
1
2
3
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
1. Disconnect the single active call.
2. Disconnect the held MPTY.
3. Disconnect both. All calls, even if they are on hold, shall be released.
4. Join the single active call and the held MPTY together.
This would result in an active MPTY, except if the number of remote parties exceeds the number allowed.
A MPTY invoke notification shall be sent towards all remote parties.
A Retrieve notification (according to GSM 02.83[16]) shall be sent towards the previously held remote party.
5. Alternate between both calls.
b) Active MPTY and held call
If the served mobile subscriber is connected to a active MPTY and has a single call on hold, she is able to:
1. Disconnect the active MPTY.
2. Disconnect the single held call.
3. Disconnect both. All calls, even if they are on hold, shall be released.
4. Join the single held call and the active MPTY together.
This would result in an active MPTY, except if the number of remote parties exceeds the number allowed.
A MPTY invoke notification shall be sent towards all remote parties. A Retrieve notification
(according to GSM 02.83[16]) shall be sent towards all previously held remote parties.
5. Alternate between both calls.
If the served mobile subscriber is connected to an active Multi Party call and has a single call on hold, a request for establishing a private communication shall be rejected by the network. (Because this would lead to an active call and two calls on hold, which is not supported according to the GSM
Call Hold Supplementary Service).
An indication shall be given to the served mobile subscriber with the reason for failure.
29
30
31
32
33
34
35
4.5.3.2.5 Remote parties in a Multi-Party Call
Any of the remote parties shall be able to:
1. Put her connection to the multi-party call on hold (and typically later retrieve it). The requirements of the Call Hold service then apply;
2. Release from the multi-party call.
If a remote party releases and no remote party then remains, the requirements of the normal call release procedures then apply.
Ballot Version 68

N.S0028-0
1
2
3
4.5.3.3 Call Detail Record / Charging Requirements
For GSM and ANSI-41 based network interoperability, no new or special recording capabilities are needed.
4
5
6
7
8
9
4.5.3.4 Interrogation
GSM mode
The controlling subscriber may interrogate the network by the use of a control procedure, as specified in GSM 02.30[11]. The network shall respond with an appropriate indication telling the subscriber whether the service is supported in this network and, if so, provide a list of all Basic Service groups to which the Call waiting supplementary service is active.
10
11
12
13
4.5.4.1 Registration
None identified.
14
15 None identified.
16
17
4.5.4.3 Activation
None identified.
18
19
4.5.4.4 De-Activation
None identified.
20
21
27
28
29
30
31
32
33
34
22
23
24
25
26
35
36
4.5.4.5 Invocation
ANSI13641 Mode
The controlling subscriber is alerting the other party, or the controlling subscriber is in a two-way conversation with the other party, if the controlling subscriber presses the SEND key, the system applies denial treatment. Retain connections.
One party is on hold, and the system is waiting for the controlling subscriber to enter a feature code or the address of a third party, if the controlling subscriber enters the termination address + SEND key, if the subscriber is not authorized for the request, resources are not available, or the termination address was not acceptable; then ignore any accompanying digits and the system applies denial treatment. Retain existing connection to party on hold. if the controlling subscriber enters *FC + SEND key, if the subscriber is not authorized for the request, resources are not available, or the termination address was not acceptable; then ignore any accompanying digits and the system applies denial treatment. Retain existing connection to party on hold. if the controlling subscriber enters *FC + # + termination address + SEND key, if the subscriber is not authorized for the request, resources are not available, or the termination address was not
Ballot Version 69

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

N.S0028-0
7
8
5
6
1
2
3
4
If the controlling subscriber enters *FC + # + termination address +
SEND
, the system acts upon the feature code. If the other party is alerting, the controlling subscriber is not authorized for the request, resources are not available, or the termination address was not acceptable; the system applies for denial treatment. Reconnects the controlling subscriber and the second party.
GSM Mode
None identified.
9
10
11
12
4.5.6.1 Advice of charge (AoC)
None identified.
13
14
4.5.6.2 Barring of All Outgoing Calls (BAOC)
None identified.
15
16
4.5.6.3 Barring of Outgoing International Calls (BOIC)
None identified.
17
18
19
4.5.6.4 Barring of Outgoing International Calls except those directed to the Home PLMN
(BOIC-exHC)
None identified.
20
21
4.5.6.5 Barring of All Incoming Calls (BAIC)
None identified.
22
23
4.5.6.6 Barring of Incoming Calls when Roaming Outside the Home PLMN (BIC-Roam)
None identified.
24
25
4.5.6.7 Call Delivery (CD)
None identified.
26
27 None identified.
28
29 None identified.
30 4.5.6.10 Call Forwarding—No Answer / No Reply (CFNA / CFNRy)
Ballot Version 71

N.S0028-0
1 None identified.
2
3
4.5.6.11 Call Forwarding—Not Reachable (CFNRc)
None identified.
4
5
4.5.6.12 Call Forwarding—Unconditional (CFU)
None identified.
8
9
10
11
12
13
14
15
16
6
7
4.5.6.13 Call Transfer (CT)
ANSI13641 Mode
CT takes precedence over 3WC. When the controlling subscriber disconnects on an active three-way call, and also has CT active, then the disconnect shall be used to transfer the call and the two noncontrolling parties remain connected.
To avoid a call transfer, the controlling subscriber may force a three-way call to disconnect by sending a flash request to drop the last party added and then disconnecting the remaining party.
3WC takes precedence over CT for the interpretation of flash requests. If the controlling subscriber presses SEND in the Holding 2-way state (and both CT and 3WC are active), the result is a conference request rather than a CT drop party request. If the controlling subscriber presses SEND while in the 3-way state, the last party is requested to be dropped.
22
23
24
25
17
18
19
20
21
26
27
28
29
30
31
32
4.5.6.14 Call Waiting / Call Hold (CW / HOLD)
ANSI13641 Mode
3WC and CW are mutually exclusive. A call incoming to a controlling subscriber setting up or engaged in a three-way call shall be given busy treatment, even if the called subscriber has CW active.
A flash request from a subscriber authorized for 3WC, while CW alerting is being applied, shall be used to respond to the CW call. If the controlling subscriber still desires a three-way call, it must first dispose of the CW call before requesting a three-way call.
GSM Mode
A user who is active on a multi-party call, either as the served mobile subscriber or as remote party, may receive an indication of a waiting call, provided that the maximum number of calls at the mobile equipment is not exceeded.
After the multi-party call has been put on hold by this user, the waiting call may be accepted by the user.
Any party involved in an active multi-party call may place the connection to the multi-party call on hold and later retrieve it.
33
34
4.5.6.15 Calling Number / Line Identification Presentation (CNIP / CLIP)
None identified.
35
36
4.5.6.16 Calling Number / Line Identification Restriction (CNIR / CLIR)
ANSI13641 Mode
Ballot Version 72

N.S0028-0
1
2
3
4
If the 3WC controlling subscriber activates the Temporary CNIR Mode during the setup of a 3WC leg, then the Temporary CNIR activation applies only to that call leg.
If the 3WC controlling subscriber de-activates the Temporary CNIR Mode during the setup of a 3WC leg, then the Temporary CNIR de-activation applies only to that call leg.
5
6
4.5.6.17 Calling Name Presentation (CNAP)
None identified.
7
8
4.5.6.18 Calling Name Restriction (CNAR)
None identified.
9
10
11
4.5.6.19 Closed User Group (CUG)
None identified.
See GSM 02.85[18], Section 1.6.84.1.
22
23
24
25
26
18
19
20
21
12
13
14
15
16
17
4.5.6.20 Conference Calling / Multi Party Service (CC / MPTY)
ANSI13641 Mode
3WC takes precedence over CC. That is, a subscriber cannot add more parties to a 3WC call (in effect trying to convert the 3WC call into a CC call). A 3WC can be converted to a two-way call with a flash request to drop the last party. The two-way call can be converted into a conference call.
GSM Mode
It shall be possible for any remote party in a multi-party call to alternate between two different multiparty calls.
Served Mobile Subscriber:
The served mobile subscriber cannot control more than one multi-party call at a time.
It shall not be possible to invoke multi-party service if either or both of the initial calls are active parts of one or two other multi-party calls.
Multi-Party call controlled by one of the remote parties:
The network shall not be required to prevent that a leg to one of the other remote parties can be part of another multi-party call controlled by that remote party.
27
28
29
30
31
4.5.6.21 Connected line identification presentation
GSM Native Subscriber
Remote parties in an existing multi-party call who have subscribed to connected line number identification presentation shall not receive a new remote party’s number whenever a served mobile subscriber adds a new remote party to the multi-party call.
32
33
4.5.6.22 Do Not Disturb (DND)
None identified.
34 4.5.6.23 Emergency Services
Ballot Version 73

N.S0028-0
1 None identified.
2
3
4.5.6.24 Flexible Alerting (FA)
None identified.
4
5
4.5.6.25 Message Waiting Notification (MWN)
MWN pip tone shall only be applied for the first leg of the call.
6
7
4.5.6.26 Mobile Access Hunting (MAH)
None identified.
8
9
4.5.6.27 Password Call Acceptance (PCA)
None identified.
10
11
4.5.6.28 Preferred Language (PL)
None identified.
12
13
4.5.6.29 Priority Access and Channel Assignment (PACA)
None identified.
14
15
4.5.6.30 Remote Feature Control (RFC)
None identified.
16
17
4.5.6.31 Selective Call Acceptance (SCA)
None identified.
18
19
4.5.6.32 Subscriber PIN Access (SPINA)
3WC shall not be activated while SPINA is active.
20
21
22
23
4.5.6.33 Subscriber PIN Intercept (SPINI)
The service provider may require the 3WC invoking subscriber (with SPINI active) to enter the SPINI
PIN when initiating a three-way call. That is, the subscriber shall be requested to enter the SPINI PIN, if the call leg to the third party meets the call type criteria for SPINI.
24
25
4.5.6.34 Three-Way Calling / Multi Party Service (3WC / MPTY)
Not applicable.
26
27
4.5.6.35 Voice Message Retrieval (VMR)
None identified.
28
29
30
4.5.6.36 Voice Privacy (VP)
None identified.
Ballot Version 74

N.S0028-0
1
2
3
4
5
6
7
8
9
Calling Number Identification Presentation (CNIP) or Calling Line Identification Presentation (CLIP) provides the number identification of the calling party to the called subscriber. The terminating network may receive the Calling Number Identification (CNI) as part of basic call setup. CNIP / CLIP does not impact a subscriber's ability to originate calls or to receive calls.
10
11
12
4.6.1.1 Applicability to Telecommunications Services
For GSM native mode: CLIP applies to all circuit switched telecommunication services.
For ANSI native mode: CNIP applies to voice telecommunication services only.
13
14
15
16
The definition of which feature capabilities are mapped between GSM (in GSM 02.81[14]) and ANSI-
13641 modes is described below.
17
18
19
20
21
4.6.2.1 ANSI-41 foreign mode Capabilities (GSM --> ANSI13641 Feature Mapping)
The ability of the subscriber’s serving system to override calling number or line presentation restriction invoked from the calling party’s serving system or PLMN is not supported.
Connected Line Identification Presentation and Restriction (COLP / COLR) is not supported.
Interrogation of the status of CLIP is not supported.
22
23
24
25
26
4.6.2.2 GSM Foreign Mode Capabilities (ANSI13641 --> GSM Feature Mapping)
The ability to display multiple calling party numbers, a sub-address, or a redirecting number is not explicitly defined.
If the called subscriber has call forwarding unconditional active, the ability to present the calling number identification to the subscriber during an abbreviated (or reminder) alert is not supported.
27
28
29
4.6.3.1 Authorization (or Provision)
CNIP / CLIP shall be generally available after pre-arrangement with the service provider.
30
31
4.6.3.2 De-Authorization (or Withdrawal)
CNIP / CLIP may be withdrawn at the subscriber’s request or for administrative reasons.
32 4.6.3.3 Registration
Ballot Version 75

N.S0028-0
1 CNIP / CLIP has no registration.
2
3
4.6.3.4 De-Registration (or Erasure)
CNIP / CLIP has no de-registration (or erasure).
4
5
4.6.3.5 Activation
CNIP / CLIP shall be activated upon authorization (or provision).
6
7
4.6.3.6 De-Activation
CNIP / CLIP shall be de-activated upon de-authorization (or withdrawal).
8
9
10
4.6.3.7 Invocation
The network automatically invokes CNIP / CLIP upon incoming call set-up when calling number identification is available and presentation is not restricted.
17
18
19
20
21
22
11
12
13
14
15
16
If CNIP / CLIP service is authorized and active, and calling number identification is available, the called party’s serving network shall provide the calling number identification during alerting on incoming calls. In addition to or instead of the calling number identification the subscriber shall also be given a Presentation Indicator and Screening Indicator associated with the calling number identification.
The originating network shall be capable of transmitting up to 15 digits of calling party number. The subscriber’s serving system must likewise be capable of delivering up to 15 digits of calling party number.
If CNIP / CLIP service is not authorized or active, no calling number identification, presentation indicator, or screening indicator shall be delivered to the subscriber, even if it is available to the serving system.
23
24
25
4.6.4.1 Call Detail Record / Charging Requirements
For GSM and ANSI-41 based network interoperability, no new or special recording capabilities are needed.
26
27
28
4.6.4.2 Interrogation
GSM mode only: The subscriber can request the status of the CLIP supplementary service.
29
30
31
32
4.6.5.1 Registration
None identified.
33
Ballot Version 76

N.S0028-0
1 None identified.
2
3
4.6.5.3 Activation
None identified.
4
5
4.6.5.4 De-Activation
None identified.
10
11
12
6
7
8
9
4.6.5.5 Invocation
In some situations with insufficient signaling capability, if the calling party number identification is not available, the called party / subscriber shall receive an indication that calling number identity is not available. This indication may include an alphanumeric display indicatingnumber not available.
For an international call with calling party number identification not available, the called party / subscriber shall receive an indication that calling number identity is not available. This indication may include an alphanumeric display indicating number not available.
13
14
15
Some serving systems may not offer CNIP / CLIP to any subscriber. In this case, the subscriber shall receive no indication or display during alerting of an incoming call.
16
17
18
4.6.5.7 Exceptions During Intersystem Handoff
Some serving systems may not offer CNIP / CLIP to any subscriber. In this case, the subscriber shall receive no indication or display during alerting of an incoming call.
19
20
21
None identified.
22
23
24
25
4.6.7.1 Advice of charge (AoC)
None identified.
26
27
4.6.7.2 Barring of All Outgoing Calls (BAOC)
None identified.
28
29
4.6.7.3 Barring of Outgoing International Calls (BOIC)
None identified.
30
31
32
4.6.7.4 Barring of Outgoing International Calls except those directed to the Home PLMN
(BOIC-exHC)
None identified.
Ballot Version 77

N.S0028-0
1
2
4.6.7.5 Barring of All Incoming Calls (BAIC)
When BAIC is active, the subscriber shall receive no calling party identification or display.
3
4
5
4.6.7.6 Barring of Incoming Calls when Roaming Outside the Home PLMN (BIC-Roam)
When BIC-Roam is active and invoked, the subscriber shall receive no calling party identification or display.
6
7
4.6.7.7 Call Delivery (CD)
When Call Delivery is not active, the subscriber shall receive no calling party identification or display.
8
9 None identified.
10
11 None identified.
12
13
4.6.7.10 Call Forwarding—No Answer / No Reply (CFNA / CFNRy)
None identified.
14
15
4.6.7.11 Call Forwarding—Not Reachable (CFNRc)
None identified.
16
17
18
19
4.6.7.12 Call Forwarding—Unconditional (CFU)
ANSI13641 mode only: If the called subscriber has CNIP / CLIP active, the calling number identification may be presented to the subscriber during an abbreviated (or reminder) alert in accordance with CNIP / CLIP procedures.
20
21
4.6.7.13 Call Transfer (CT)
None identified.
22
23
24
4.6.7.14 Call Waiting / Call Hold (CW / HOLD)
If the called subscriber has CNIP / CLIP active, the calling party identification shall be presented to the subscriber with the call waiting notification.
25
26
4.6.7.14.1 Calling Number / Line Identification Presentation (CNIP / CLIP)
Not applicable.
27
28
4.6.7.15 Calling Number / Line Identification Restriction (CNIR / CLIR)
CNIR / CLIR takes precedence over CNIP / CLIP.
29
30
31
4.6.7.16 Calling Name Presentation (CNAP)
Authorization and activation of CNAP may be linked to the authorization and activation of CNIP /
CLIP.
Ballot Version 78

N.S0028-0
1
2
3
4.6.7.17 Calling Name Restriction (CNAR)
Authorization and activation of CNAR may be linked to the authorization and activation of CNIR /
CLIR.
4
5
4.6.7.18 Closed User Group (CUG)
None identified.
6
7
4.6.7.19 Conference Calling / Multi Party Service (CC / MPTY)
None identified.
8
9
10
4.6.7.20 Do Not Disturb (DND)
DND takes precedence over CNIP / CLIP. When DND is active and invoked, the subscriber shall receive no calling party identification or display.
11
12
4.6.7.21 Emergency Services
None identified.
13
14
4.6.7.22 Flexible Alerting (FA)
None identified.
15
16
4.6.7.23 Message Waiting Notification (MWN)
None identified.
17
18
4.6.7.24 Mobile Access Hunting (MAH)
None identified.
19
20
4.6.7.25 Over the Air Activation (OTA)
None identified.
21
22
4.6.7.26 Password Call Acceptance (PCA)
None identified.
23
24
4.6.7.27 Preferred Language (PL)
It shall be possible to present information in the subscriber’s preferred language.
25
26
4.6.7.28 Priority Access and Channel Assignment (PACA)
None identified.
27
28
4.6.7.29 Remote Feature Control (RFC)
None identified.
29 4.6.7.30 Selective Call Acceptance (SCA)
Ballot Version 79

N.S0028-0
1 None identified.
2
3
4.6.7.31 Subscriber PIN Access (SPINA)
None identified.
4
5
4.6.7.32 Subscriber PIN Intercept (SPINI)
None identified.
6
7
4.6.7.33 Three-Way Calling / Multi Party Service (3WC / MPTY)
None identified.
8
9
4.6.7.34 Voice Message Retrieval (VMR)
None identified.
10
11
12
4.6.7.35 Voice Privacy (VP)
None identified.
Ballot Version 80

N.S0028-0
1
2
25
26
27
28
29
30
31
32
33
13
14
15
16
17
18
19
20
21
22
23
24
34
35
36
37
38
39
40
10
11
12
7
8
9
3
4
5
6
Call Barring (CB) Supplementary service consists of Outgoing Call Barring (OCB) and Incoming Call
Barring (ICB). It denies a mobile subscriber the ability to originate/terminate certain types of calls.
These can be applied separately per basic service group.
Operator Determined Barring (ODB) allows the network operator or service provider to regulate, by means of an exceptional procedure, access by the subscribers to services, by the barring of certain categories of outgoing or incoming calls or of roaming.
The purpose of this network feature is to be able to limit the service provider's financial exposure to new subscribers, or to those who have not promptly paid their bills. It may only be applied to the service provider's own subscribers.
Application of Operator Determined Barring is controlled by the Service Provider on a subscriberbasis (automatically applies to all basic service groups), by administrative interaction with the HLR; this interface is not standardized.
With the exception of the barring of roaming, the HLR effects Operator Determined Barring in a similar manner to Service Provider Call Barring supplementary service. Consequently, the VLR and
MSC also execute the relevant Barring Conditions in similar manners. It is noted that there is no password usage. Roaming is barred by the HLR when the MS is in a PLMN other than the Home
PLMN or not in the Home PLMN Country as applicable.
Operator Determined Barring is a GSM feature. An identical feature does not exist in ANSI-41, although portions of it may be implemented by an operator using ANSI-41. The following sections separately describe the following GSM ODB options for which interoperability can be supported in some form at least (note that the first two are also Call Barring supplementary services):
Barring outgoing calls
Barring incoming calls
Barring of roaming
Barring of Supplementary Services Management
Barring of registration of call forward-to numbers
Barring of invocation of call transfer
Description of Barring of Outgoing Calls
The operator may select a barring program that prevents certain types of outgoing calls from being originated by the MS.
ODB in GSM is documented in GSM 02.41[12]. Call Barring Supplementary Services in GSM is documented in GSM 02.88[20].
Barring of outgoing calls with a wider range of conditions can be implemented using the ANSI-41
Origination Indicator parameter, which is provided by the HLR to the serving MSC/VLR upon subscriber registration, as defined in Chapter 5 of ANSI-41[3]. The Origination Indicator specifies which types of call originations are permitted, as opposed to which types of call originations are barred or restricted in GSM.
Ballot Version 81

N.S0028-0
9
10
1
2
3
4
5
6
7
The main problem for roaming interoperability is that for GSM and ANSI-41 the call barring programs are based on different screening criteria. In GSM barring is based on the concept of PLMN, and calls are generally permitted to all terminals within the country of a particular PLMN (i.e., fixed and mobile terminals). ANSI-41 allows more specific barring programs such as ‘local calls only’, or a specific DN.
As a result of this conflict, IIF functionality is required to support subscribers using their non-native mode.
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
Bar all outgoing international calls
Origination denied
National long distance allowed (which includes local calls).
Bar all outgoing international calls except to HPLMN country (BOICexHC)
National long distance allowed (which includes local calls).
Table 6: GSM Foreign Mode Interoperability for Outgoing Call Restrictions
ANSI-41 Native Mode
GSM Equivalent (option: either ODB or
OCB)
Origination denied Bar all outgoing calls (BAOC)
Local Calls Only Allowed Bar all outgoing calls (BAOC)
Selected leading digits of directory number allowed
Bar all outgoing calls (BAOC)
National long distance allowed Bar outgoing international calls (BOIC)
Allow international calls No barring
Allow single directory number only
(i.e., hotline)
Bar all outgoing calls (BAOC)
11
12
13
14
15
16
4.7.1.1 Description of Barring of Incoming Calls
Barring of incoming calls takes place at the HLR for native mode and foreign mode. To support interoperability of barring incoming calls when roaming outside the HPLMN country (BIC-Roam), the true serving system identity (SID) must be passed to the HLR upon registration. Otherwise, this feature must be supported from the IIF.
17
18
19
20
21
22
4.7.1.2 Description of ODB Barring of Roaming
Barring of roaming takes place at the HLR. There is no IIF involvement, beyond the mapping of registration operations between GSM and ANSI-41 based networks. Upon activation of ODB for barring of roaming and ODB Barring of all Outgoing Calls when Roaming Outside the HPLMN country, the HLR can be set to deny registration. The degree of granularity to which roaming can be denied (e.g., roaming outside home PLMN country) shall be determined by the HLR capabilities.
Ballot Version 82

N.S0028-0
1
2
3
4
5
6
4.7.1.3 Description of ODB Barring of Supplementary Services Management.
Barring of supplementary services management takes place at the HLR. There is no IIF involvement
(other than transfer of services management requests between GSM and ANSI-41 based networks).
Upon activation of ODB for barring of supplementary services management, the HLR can be set to deny these user operations. The degree to which supplementary services management can be denied shall be determined by the HLR capabilities.
7
8
9
10
11
12
4.7.1.4 Description of ODB Barring of Registration of Call Forward-to Numbers
Barring of registration of call forward-to numbers takes place at the HLR. There is no IIF involvement.
Upon activation of ODB for barring of registration of call forward-to numbers, the HLR can be set to deny registration of these numbers. The degree of granularity to which registration can be denied
(e.g., Barring of registration of any international call forward-to number) shall be determined by the
HLR capabilities.
13
14
15
16
4.7.1.5 Description of ODB Barring of Invocation of Call Transfer
Barring of call transfer is possible in ANSI-41 based networks by restriction in the subscriber profile.
There is no IIF involvement. It is not possible to conditionally bar call transfer (based on the charging conditions for the various call legs) as described in the GSM ODB Stage 1 description.
17
18
19
4.7.1.6 Applicability to Telecommunications Services
CB and ODB applies to all telecommunications services except emergency calls and possibly certain outgoing free calls (e.g., calls to customer care).
20
21
22
ODB is an administrative feature. There are no user procedures for authorization, de-authorization, registration, or de-registration.
23
24
25
26
4.7.2.1 Activation
Activation Option
Table 7: Call Barring Activation Options
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 activation
Determined by the service provider at provisioning time or at a later date due to administrative reasons. Can be controlled by the subscriber in GSM native mode.
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 activation
Determined by the service provider at provisioning time or at a later date due to administrative reasons. Can be controlled by the subscriber in GSM native mode.
3
4
5
6
4.7.2.3 Invocation
Call Barring and ODB are invoked automatically by the network for subscribers that have it active, upon subscriber or network actions that are barred.
7
8
9
10
11
12
13
14
15
A subscriber that attempts to originate a call for which call barring or operator determined barring of outgoing calls has been activated shall receive call denial treatment (e.g., a re-order tone and announcement). Likewise, a caller that attempts to terminate a call for which call barring or operator determined barring of incoming calls has been activated shall receive call denial treatment (e.g., a reorder tone and announcement).
A subscriber that attempts to perform other barred operations (e.g., management of supplementary services) shall receive a notification indicating denial of the operation.
Call Barring and ODB does not affect the origination of emergency calls.
16
17
18
19
4.7.3.1 Call Detail Record
For GSM and ANSI-41 based network interoperability, no new or special recording capabilities are needed.
20
21
22
23
24
4.7.4.1 Provisioning
Since GSM PLMNs may not support many of the provisioning criteria in ANSI-41 networks, service provisioning shall revert to the closest available criterion as described above.
25
26 None identified.
Ballot Version 84

N.S0028-0
1
2
3
4.7.4.3 Exceptions during Intersystem Handoff
None identified.
4
5
6
7
8
9
10
4.7.5.1 Advice of Charge (AoC) or Prepaid Charging (PPC)
AoC and PPC take precedence over Call Barring and ODB in the following sense. If service is denied by the AoC or PPC application due to non-payment, then calls shall not be delivered to or sent from the mobile subscriber even if the barring program criteria are met. Whether or not forwarding to the diversion number is done is beyond the scope of this document.
11
12
13
14
15
16
4.7.5.2 Barring of Incoming Calls (Call Barring Supplementary Services)
Calls shall be denied if either Operator Determined Barring or Barring Of Incoming Calls determine that the call is to be barred.
If a call is barred due to both Operator Determined Barring and Barring Of Incoming Calls, then the message or notification returned towards the caller shall be the same as if the barring was due solely to Operator Determined Barring.
17
18
19
20
21
22
4.7.5.3 Barring of Outgoing Calls (Call Barring Supplementary Services)
Calls shall be denied if either Operator Determined Barring or Barring Of Outgoing Calls determine that the call is to be barred.
If a call is barred due to both Operator Determined Barring and Barring Of Outgoing Calls, then the message or notification returned towards the caller shall be the same as if the barring was due solely to Operator Determined Barring.
23
24
25
26
27
4.7.5.4 Call Delivery (CD)
Call Barring and ODB takes precedence over CD. If an incoming call arrives for a subscriber with
Barring / ODB and CD active, the call is managed by the barring program first. Only if Call Barring and ODB accepts the call, is CD attempted. If Barring / ODB refuses the call, the call is given barring /
ODB refusal treatment.
28
29
30
31
32
33
34
35
36
Call Barring (CB)/ODB takes precedence over CFB. If an incoming call arrives for a subscriber with both CB/ODB and CFB active, the call is screened by the CB/ODB program first. If CB and ODB accepts the call, an attempt is made to deliver or terminate the call to the subscriber. If the subscriber is busy, then CFB is invoked.
If CFB is in contravention of a Call Barring / Operator Determined Barring Category, when the latter is activated, then the activation shall result in making CFB quiescent. If the subscriber attempts to activate a new CFB program in contravention of a Call Barring / Operator Determined Barring
Category, then the activation shall be denied, and the subscriber informed of the denial.
37 4.7.5.6 ANSI13641 Call Forwarding—Default (CFD)
Ballot Version 85

N.S0028-0
11
12
13
14
15
16
17
18
5
6
7
8
1
2
3
4
9
10
CB/ODB takes precedence over CFD. If an incoming call arrives for a subscriber with CB/ODB and
CFD active, the call is screened by CB/ODB first. If CB and ODB accepts the call, an attempt is made to deliver or terminate the call to the subscriber. If the subscriber does not or cannot answer the call, then CFD is invoked.
If CFD is in contravention of a Call Barring / Operator Determined Barring Category, when the latter is activated, then the activation shall result in making CFD quiescent. If the subscriber attempts to activate a new CFD program in contravention of a Call Barring / Operator Determined Barring
Category, then the activation shall be denied, and the subscriber informed of the denial.
Call Forwarding—No Answer (ANSI13641 CFNA = GSM CF No Reply (CFNRy) and GSM CF Not
Reachable (CFNRc))
CB/ODB takes precedence over CFNA. If an incoming call arrives for a subscriber with CB/ODB and
CFNA active, the call is screened by CB/ODB first. If CB and ODB accepts the call, an attempt is made to deliver or terminate the call to the subscriber. If the subscriber does not or cannot answer the call, then CFNA is invoked.
If CFNA is in contravention of a Call Barring / Operator Determined Barring Category, when the latter is activated, then the activation shall result in making CFNA quiescent. If the subscriber attempts to activate a new CFNA program in contravention of a Call Barring / Operator Determined Barring
Category, then the activation shall be denied, and the subscriber informed of the denial.
19
20
21
22
23
24
25
26
27
28
29
30
Interaction between ODB and CFU is beyond the scope of this Standard. The following describes a possible implementation:
CB/ODB takes precedence over CFU. If an incoming call arrives for a subscriber with CB/ODB and
CFU active, incoming calls are denied according to the ODB option, except when Barring of Incoming
Calls when Roaming Outside the HPLMN country is active, CFU has precedence).
If CFU is in contravention of a Call Barring/ Operator Determined Barring Category, when the latter is activated, then the activation shall result in making CFU quiescent, (except in the case of Barring of
Incoming Calls when Roaming outside the HPLMN Country, in which case CFU takes precedence). If the subscriber attempts to activate a new CFU program in contravention of a Call Barring / Operator
Determined Barring Category, then the activation shall be denied, and the subscriber informed of the denial.
31
32
33
34
If the subscriber attempts to invoke a call transfer in contravention of a Call Barring / Operator
Determined Barring category, then the invocation shall be denied, and the subscriber informed of the denial.
35
36
37
4.7.5.9 Call Waiting (CW) or Call Hold (CH)
ODB takes precedence over CW. Incoming calls to the subscriber with CB/ODB and CW active shall be screened by the CB/ODB feature before being considered for CW.
38
39
4.7.5.10 Calling Number/Line Identification Presentation (CNIP/CLIP)
None identified.
40
41
42
4.7.5.11 Calling Number/Line Identification Restriction (CNIR/CLIR)
If the calling number indicatespresentation restricted, the calling number shall not be presented to the called party, the called station, the diversion party, or the diversion station.
Ballot Version 86

N.S0028-0
1
2
3
4
5
4.7.5.12 Closed User Group (CUG)
See GSM 02.85[18].
If a call is barred due to both Call Barring / Operator Determined Barring and CUG restrictions, then the message or notification returned towards the caller shall be the same as if the barring was due solely to Call Barring / Operator Determined Barring.
6
7
4.7.5.13 Conference Calling / Multi Party Service (CC / MPTY)
None identified.
8
9
10
11
12
4.7.5.14 Do Not Disturb (DND)
Interaction between CB/ODB and DND is beyond the scope of this Standard. The following describes a possible implementation:
CB/ODB takes precedence over DND. That is, an incoming call to a subscriber with CB/ODB and
DND active is given CB/ODB treatment.
13
14
15
4.7.5.15 Emergency Services
Emergency Services takes precedence over CB/ODB. A call to or from an authorized emergency service bureau shall not be refused by CB/ODB.
16
17
18
19
20
21
4.7.5.16 Flexible Alerting (FA)
Interaction between FA and CB/ODB is beyond the scope of this Standard. The following describes a possible implementation:
CB/ODB on the FA Pilot Directory Number takes precedence over FA. That is, calls to the FA Pilot
Directory Number with ODB active are given ODB treatment first. If CB/ODB screening fails, the call is refused. If CB/ODB screening passes, the call is given FA treatment.
22
23
4.7.5.17 Message Waiting Notification (MWN)
None identified.
24
25
26
27
28
29
4.7.5.18 Mobile Access Hunting (MAH)
Interaction between MAH and CB/ODB is beyond the scope of this Standard. The following describes a possible implementation:
CB/ODB of the MAH Pilot Directory Number takes precedence over MAH. That is, calls to the MAH
Pilot Directory Number with CB/ODB active are given CB/ODB treatment first. If CB/ODB screening fails, the call is refused. If CB/ODB screening passes, the call is given MAH treatment.
30
31
4.7.5.19 Password Call Acceptance (BIC)
Not applicable.
32
33
4.7.5.20 Preferred Language (PL)
None identified.
34 4.7.5.21 Priority Access and Channel Assignment (PACA)
Ballot Version 87

N.S0028-0
1 None identified.
2
3
4.7.5.22 Remote Feature Control (RFC)
TBD.
4
5
4.7.5.23 Subscriber PIN Access (SPINA)
None identified
6
7
4.7.5.24 Subscriber PIN Intercept (SPINI)
None identified.
8
9
4.7.5.25 Three-Way Calling (3WC)
None identified.
10
11
4.7.5.26 Voice Message Retrieval (VMR)
None identified.
12
13
4.7.5.27 Voice Privacy (VP)
None identified.
Ballot Version 88

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

N.S0028-0
1
2
This section describes the normal procedures that result in a successful outcome.
3
4
5
6
7
8
4.8.2.1 Authorization (or Provision)
The service is made available to an individual subscriber after necessary arrangements have been made with the home service provider. Authorized service may include:
Only mobile originated SMS teleservices
Only mobile terminated SMS teleservices
Both mobile originated and mobile terminated SMS teleservices
9
10
11
12
13
14
15
4.8.2.2 De-Authorization (or Withdrawal)
The service is removed on an individual basis from subscribers provided with the service after necessary arrangements have been made with the home service provider. Authorized service may include:
Only mobile originated SMS teleservices
Only mobile terminated SMS teleservices
Both mobile originated and mobile terminated SMS teleservices
16
17
18
19
20
4.8.2.3 Registration
Mobile terminated SMS teleservice registration shall be as a result of Authorization.
For mobile originated SMS teleservices the following information shall be registered in the mobile station:
SMS-C address(es) as needed for different mobile originated SMS teleservices or applications.
21
22
23
24
4.8.2.4 De-Registration (or Erasure)
Mobile terminated SMS teleservice de-registration shall be as a result of withdrawal.
For mobile originated SMS teleservices the following information may be erased in the mobile station:
SMS-C address(es) as needed for different mobile originated SMS teleservices or applications.
25
26
27
28
4.8.2.5 Activation
Both mobile originated and mobile terminated SMS teleservices shall be activated as the result of authorization. When operating in GSM or ANSI-41 foreign mode, there is no special activation process required.
29
30
31
32
33
4.8.2.6 De-Activation
Both mobile originated and mobile terminated SMS teleservice de-activation shall be the result of deauthorization. When operating in GSM or ANSI-41 foreign mode, there is no special de-activation process required.
Ballot Version 90

N.S0028-0
1
2
3
4
4.8.2.7 Invocation
Invocation shall be the result of:
A mobile station needing to send user data to another Short Message Entity (SME).
A SME needing to send user data to a mobile station.
5
6
7
8
4.8.2.8 Interrogation
Interrogation shall not be possible for mobile terminated SMS teleservices.
For mobile originated SMS teleservices, the user shall be able to interrogate if they have any SMS-C addresses registered on their mobile station.
19
20
21
15
16
17
18
9
10
11
12
13
14
For mobile terminated SMS teleservices, the following normal operation applies. Upon receiving a request from an SME, the SMS-C shall:
Determine the location of the mobile station
Attempt to deliver the user data to the mobile station
If notification was requested, an indication shall be passed back to the user.
For mobile originated SMS teleservices, the following normal operation applies. The mobile station shall send user data to the network including the following information:
Destination address;
Home SMS-C address;
Originating mobile identifier
If notification is required.
If notification was requested, an indication shall be passed back to the user.
22
23
4.8.3.1 Call Detail Record / Charging Requirements
For GSM and ANSI13641 interoperability, no new or special recording capabilities are needed.
24
25
26
27
This section describes abnormal situations not described in “Normal Operation with Successful
Outcome”. Procedures on time-outs, unexpected signaling responses, and other such events may be defined.
28
29
30
4.8.4.1 Authorization (or Provision)
An attempt to re-provision an already provisioned service shall result in an indication to the service provider.
31
32
33
4.8.4.2 De-Authorization / Withdrawal
An attempt to withdraw a service that has not been provisioned shall result in an indication being provided to the service provider.
Ballot Version 91

N.S0028-0
1
2
4.8.4.3 Registration
None identified at this time.
3
4 Not applicable.
5
6
4.8.4.5 Activation
Not applicable.
7
8
4.8.4.6 De-Activation
Not applicable.
16
17
18
19
20
13
14
15
9
10
11
12
21
22
23
24
25
4.8.4.7 Invocation
For mobile terminated teleservices, if the SMS-C attempts to deliver user data to the mobile station and is unsuccessful, an indication shall be presented to the SMS-C. Possible causes may include: insufficient network resources; service not supported; service not subscribed to; insufficient mobile memory resources; insufficient information; conflicting situation with other supplementary services (e.g., call barring has been activated); subscriber not reachable.
For mobile originated teleservices, if the mobile station attempts to deliver user data to the network and is unsuccessful, the user shall be presented with an indication. Possible causes may include: insufficient network resources service not supported service not subscribed to insufficient information; conflicting situation with other supplementary services (e.g., call barring has been activated).
26
27
4.8.4.8 Interrogation
Not applicable.
28
29 None.
30
31
4.8.4.10 Exceptions during Intersystem Handoff
None Identified
Ballot Version 92

N.S0028-0
1
2 None Identified
3
4
5
6
4.8.6.1 Advice of charge (AoC)
None Identified
7
8
4.8.6.2 Barring of All Outgoing Calls (BAOC)
Per GSM 02.04[9], BAOC shall inhibit SMS origination, but this interaction is generally not invoked.
9
10
4.8.6.3 Barring of Outgoing International Calls (BOIC)
Per GSM 02.04[9], BOIC shall inhibit SMS origination, but this interaction is generally not invoked.
11
12
13
14
4.8.6.4 Barring of Outgoing International Calls except those directed to the Home PLMN
(BOIC-exHC)
Per GSM 02.04[9], BOIC-exHC shall inhibit SMS origination, but this interaction is generally not invoked.
15
16
4.8.6.5 Barring of All Incoming Calls (BAIC)
Per GSM 02.04[9], BAIC shall inhibit SMS delivery, but this interaction is generally not invoked.
17
18
4.8.6.6 Barring of Incoming Calls when Roaming Outside the Home PLMN (BIC-Roam)
Per GSM 02.04[9], BIC-Roam shall inhibit SMS delivery, but this interaction is generally not invoked.
19
20
4.8.6.7 Call Delivery (CD)
None Identified
21
22 None Identified
23
24 None Identified
25
26
4.8.6.10 Call Forwarding—No Answer / No Reply (CFNA / CFNRy)
None Identified
27
28
4.8.6.11 Call Forwarding—Not Reachable (CFNRc)
None Identified
29 4.8.6.12 Call Forwarding—Unconditional (CFU)
Ballot Version 93

N.S0028-0
1 None Identified
2
3
4.8.6.13 Call Transfer (CT)
None Identified
4
5
4.8.6.14 Call Waiting / Call Hold (CW / HOLD)
None Identified
6
7
4.8.6.15 Calling Number / Line Identification Presentation (CNIP / CLIP)
None Identified
8
9
4.8.6.16 Calling Number / Line Identification Restriction (CNIR / CLIR)
None Identified
10
11
4.8.6.17 Calling Name Presentation (CNAP)
None Identified
12
13
4.8.6.18 Calling Name Restriction (CNAR)
None Identified
14
15
4.8.6.19 Closed User Group (CUG)
None Identified
16
17
4.8.6.20 Conference Calling / Multi Party Service (CC / MPTY)
None Identified
18
19
4.8.6.21 Do Not Disturb (DND)
None Identified
20
21
4.8.6.22 Emergency Services
None Identified
22
23
4.8.6.23 Flexible Alerting (FA)
None Identified
24
25
4.8.6.24 Message Waiting Notification (MWN)
None Identified
26
27
4.8.6.25 Mobile Access Hunting (MAH)
None Identified
28 4.8.6.26 Password Call Acceptance (PCA)
Ballot Version 94

1 None Identified
2
3
4.8.6.27 Preferred Language (PL)
None Identified
4
5
4.8.6.28 Priority Access and Channel Assignment (PACA)
None Identified
6
7
4.8.6.29 Remote Feature Control (RFC)
None Identified
8
9
4.8.6.30 Selective Call Acceptance (SCA)
None Identified
10
11
4.8.6.31 Subscriber PIN Access (SPINA)
None Identified
12
13
4.8.6.32 Subscriber PIN Intercept (SPINI)
None Identified
14
15
4.8.6.33 Three-Way Calling / Multi Party Service (3WC / MPTY)
None Identified
16
17
4.8.6.34 Voice Message Retrieval (VMR)
None Identified
18
19
4.8.6.35 Voice Privacy (VP)
None Identified
N.S0028-0
Ballot Version 95

N.S0028-0
1
2
10
11
12
13
14
15
16
17
3
4
5
6
7
8
9
Message Waiting Notification (MWN) informs authorized and activated subscribers when a voice message is available for retrieval.
MWN may use pip tone, alert pip tone, or a MS display indication (including message waiting indication and message waiting count) to inform a subscriber of an unretrieved voice message(s).
Once all voice messages have been retrieved, the pip tone, alert pip tone, or a MS display indication must be removed.
Pip tone notification provides an audible, stuttered tone to the subscriber in the initial moment of a call origination or termination. Alert pip tone provides an audible alert tone to the subscriber when the MS is idle. MS display indication provides an icon or display text or both indications of the number of unretrieved voice messages (i.e. count).
If MS display indication with count is provided, and the number of unretrieved voice messages has increased, the display indication on the MS must be updated.
MWN does not impact a subscriber’s ability to originate calls or to receive calls, or to use other features or supplementary services.
18
19
4.9.1.1 Applicability to Telecommunications Services
Message Waiting Notification applies to voice telecommunication services.
20
21
22
4.9.1.2 GSM and ANSI13641 interoperability Feature Mapping
The definition of which feature capabilities are mapped between GSM and ANSI13641 modes is described below.
23
24
25
26
4.9.1.2.1 ANSI-41 foreign mode Capabilities (GSM --> ANSI13641 Feature Mapping)
MWN is done via an MS display message waiting indication. An MS display message waiting count is provided to the MS as available. The MS shall be capable of receiving the count.
MWN via an MS display indication may be supplemented with audible pip tone alerting.
27
28
29
4.9.1.2.2 GSM Foreign Mode Capabilities (ANSI13641 --> GSM Feature Mapping)
Audible pip tone notification is not supported, but MS display indication shall be provided as required.
The ability to activate and de-activate various means of MWN alerting shall not be supported.
30
31
32
33
34
35
4.9.2.1 Authorization (or Provision)
MWN may be generally available or may be provided after pre-arrangement with the service provider.
Pip tone, alert pip tone, or MS display indication (including message waiting indication and message waiting count) are provided at the option of the service provider in ANSI13641 mode. Only MS display indication is provided in GSM mode.
Ballot Version 96

N.S0028-0
1
2
Authorization on demand by the subscriber, as described in ANSI-664[1], shall be optionally supported in ANSI13641 native mode only.
3
4
4.9.2.2 De-Authorization (or Withdrawal)
MWN is withdrawn by the service provider.
5
6
4.9.2.3 Registration
MWN is registered upon authorization.
7
8
4.9.2.4 De-Registration (or Erasure)
MWN is de-registered upon de-authorization.
9
10
11
4.9.2.5 Activation
MWN shall be activated upon authorization. Activation on demand by the subscriber, as described in
ANSI-664[1], shall be optionally supported in ANSI13641 native mode only.
12
13
4.9.2.6 De-Activation
MWN shall be de-activated upon de-authorization.
19
20
21
22
23
24
25
26
14
15
16
17
18
4.9.2.7 Invocation
MWN alert pip tone is invoked when the first voice message is left in a VMS for a particular subscriber. MWN alert pip tone is also invoked upon MS power up and there is one or more unretrieved voice messages in the VMS. Alert pip tone notification is provided when authorized by the service provider in ANSI13641 mode only.
MWN pip tone is invoked when a voice message is left and remains unretrieved in a Voice Message
System (VMS) for a particular subscriber, and the subscriber originates a call or answers an incoming call. Pip tone notification is provided when authorized by the service provider in ANSI13641 mode only.
MS display indication is invoked when a voice message is left in a VMS for a particular subscriber. It is also invoked when ANSI-41 registration procedures are invoked for a subscriber and there is an unretrieved voice message in the VMS for the subscriber. In ANSI13641 mode, the message waiting count indication may be updated each time the number of messages in the VMS changes.
27
28
29
30
31
32
33
34
35
36
Alert pip tone shall be applied when the MS powers up and a voice message remains unretrieved in the VMS. The alert pip tone shall also be applied when the first voice message is left on a VMS and the MS is available and not engaged in a call or service request.
Pip tone notification shall be inserted into the voice channel when the subscriber originates a call or answers an incoming call and a voice message is awaiting retrieval.
The MS display message waiting indication shall be provided to an MS as long as there is an unretrieved voice message in the VMS. The MS display indication (including message waiting indication and message waiting count) is removed from the MS after the last voice message has been retrieved from the VMS.
37 4.9.3.1 Call Detail Record / Charging Requirements
Ballot Version 97

N.S0028-0
1
2
For GSM and ANSI-41 based network interoperability, no new or special recording capabilities are needed.
3
4
4.9.3.2 Interrogation
Not applicable
5
6
7
8
4.9.4.1 Registration
None identified.
9
10 None identified.
11
12
4.9.4.3 Activation
None identified.
13
14
4.9.4.4 De-Activation
None identified.
15
16
4.9.4.5 Invocation
None identified.
17
18 None identified.
19
20
4.9.4.7 Exceptions During Intersystem Handoff
None identified.
21
22 None identified.
23
24
25
26
4.9.6.1 Advice of charge (AoC)
None identified.
27
28
4.9.6.2 Barring of All Outgoing Calls (BAOC)
None identified.
Ballot Version 98

N.S0028-0
1
2
4.9.6.3 Barring of Outgoing International Calls (BOIC)
None identified.
3
4
5
4.9.6.4 Barring of Outgoing International Calls except those directed to the Home PLMN
(BOIC-exHC)
None identified.
6
7
4.9.6.5 Barring of All Incoming Calls (BAIC)
None identified.
8
9
4.9.6.6 Barring of Incoming Calls when Roaming Outside the Home PLMN (BIC-Roam)
None identified.
10
11
4.9.6.7 Call Delivery (CD)
None identified.
12
13 None identified.
14
15 None identified.
16
17
4.9.6.10 Call Forwarding—No Answer / No Reply (CFNA / CFNRy)
None identified.
18
19
4.9.6.11 Call Forwarding—Not Reachable (CFNRc)
None identified.
20
21
4.9.6.12 Call Forwarding—Unconditional (CFU)
None identified.
22
23
4.9.6.13 Call Transfer (CT)
None identified.
24
25
4.9.6.14 Call Waiting / Call Hold (CW / HOLD)
No pip tone notification shall be provided if call waiting has been deactivated.
26
27
4.9.6.15 Calling Number / Line Identification Presentation (CNIP / CLIP)
None identified.
28
29
4.9.6.16 Calling Number / Line Identification Restriction (CNIR / CLIR)
None identified.
Ballot Version 99

N.S0028-0
1
2
4.9.6.17 Calling Name Presentation (CNAP)
None identified.
3
4
4.9.6.18 Calling Name Restriction (CNAR)
None identified.
5
6
4.9.6.19 Closed User Group (CUG)
None identified.
7
8
4.9.6.20 Conference Calling / Multi Party Service (CC / MPTY)
Any pip tone notification shall only be applied to the primary leg of a multiparty call.
9
10
11
12
13
4.9.6.21 Do Not Disturb (DND)
MWN MS indication, count, and pip tone takes precedence over DND. MWN indication and pip tone may still be applied while DND is active.
DND takes precedence over MWN alert pip tone. That is, while DND is active, alerting shall not be applied.
14
15
4.9.6.22 Emergency Services
None identified.
16
17
4.9.6.23 Flexible Alerting (FA)
None identified.
18
19
4.9.6.24 Message Waiting Notification (MWN)
Not applicable.
20
21
4.9.6.25 Mobile Access Hunting (MAH)
None identified.
22
23
4.9.6.26 Over the Air Activation (OTA)
None identified.
24
25
4.9.6.27 Password Call Acceptance (PCA)
None identified.
26
27
4.9.6.28 Preferred Language (PL)
None identified.
28
29
4.9.6.29 Priority Access and Channel Assignment (PACA)
None identified.
Ballot Version 100

1
2
4.9.6.30 Remote Feature Control (RFC)
None identified.
3
4
4.9.6.31 Selective Call Acceptance (SCA)
None identified.
5
6
4.9.6.32 Subscriber PIN Access (SPINA)
None identified.
7
8
4.9.6.33 Subscriber PIN Intercept (SPINI)
None identified.
9
10
4.9.6.34 Three-Way Calling / Multi Party Service (3WC / MPTY)
Any pip tone notification shall only be applied to the primary leg of a three-way call.
11
12
4.9.6.35 Voice Message Retrieval (VMR)
None identified.
13
14
15
4.9.6.36 Voice Privacy (VP)
None identified.
N.S0028-0
Ballot Version 101

N.S0028-0
1
2
3
9
10
11
4
5
6
7
8
GPRS in GSM Foreign mode applies to the case where an ANSI-41 based subscriber (e.g., an ANSI-
41, TDMA or CDMA136 native subscriber) has registered on a GPRS network [22].
GPRS in GSM Foreign Mode allows a subscriber to an ANSI-41 based network (e.g., an ANSI41,
TDMA or CDMA136 native subscriber) to obtain GPRS service (i.e., register for service) in GSM
Foreign Mode. There is no impact on ANSI-41 Foreign Mode. There is no communication between a
GSM SGSN and an ANSI-41 MSC and a mobile can not operate simultaneously on GPRS and ANSI-
41 systems.
In GSM Foreign Mode it is required that the handset register on a GSM network or a GPRS network to be in GSM Foreign Mode. The GPRS network may be coupled with a GSM network (i.e., one
PLMN can provide both GSM circuit-switched and packet service).
12
13
GPRS is applicable to telecommunications services and can be a bearer for SMS teleservices.
14
15
16
17
Subscribers operating GPRS in GSM foreign mode (e.g., ANSI41, TDMA or CDMA136 native subscribers) shall be able to send and receive GPRS service packets when attached to a GPRS network.
18
19
20
21
4.10.2.1 Authorization (or Provision)
GPRS subscription data must be provisioned and stored on the IIF, acting as the GPRS HLR. It may be possible to provision a TDMA ANSI-41 native subscriber with GPRS only service and no GSM CS service.
22
23
24
4.10.2.2 De-Authorization (or Withdrawal)
The de-authorization shall be possible at the IIF, acting as the GPRS HLR, as well as at the
Authentication Center.
25
26
27
4.10.2.3 Authentication
The GPRS network shall query the IIF, acting as a GPRS HLR, to verify the authentication parameters. This may occur upon with GPRS attach and GPRS routing area update operations.
31
32
33
34
28
29
30
4.10.2.4 ANSI-41 registration
ANSI-41 registration occurs when the subscriber roams into an ANSI-41 network and is: registered on a GSM MSC and a GPRS SGSN; or registered on a GPRS SGSN; or registered on a GSM MSC.
ANSI-41 registration in all of these conditions shall result in a cancel location towards one or both of 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
5
6
7
1
2
3
4
8
9
The MS shall perform a GPRS attach to access GPRS services. This can be immediately after the
MS has been switched on or later as the user decides to use the GPRS service.
A successful GPRS attach requires a valid GPRS subscription.
The GPRS attach itself may be performed as one of the following:
GPRS only attach; or
GPRS attach when GSM CS attached; or combined GPRS and GSM CS attach.
If one of the above GPRS attaches takes place when previously registered on an ANSI-41 network, normal registration cancellation within the ANSI-41 network shall take place.
16
17
18
19
20
13
14
15
10
11
12
4.10.2.6 GPRS Detach
A GPRS detach allows: an MS to inform the network that it does not want to access GPRS services any longer; and the network to inform the MS that it does not have access to the GPRS services any longer.
The GPRS detach itself may be performed as one of the following:
GPRS only detach;
GPRS detach when GSM CS attached; combined GPRS and GSM CS detach.
The MS is detached either explicitly or implicitly as follows:
Explicit Detach: the network or the MS explicitly requests detach.
Implicit Detach: the network detaches the MS, without notifying the MS.
27
28
29
30
31
21
22
23
24
25
26
4.10.2.7 GPRS Routing Area Update
A routing area update occurs when a GPRS attached MS detects that it has entered a new routing area or when the periodic routing area update timer has expired. These may be combined with GSM
CS location area updates depending on the network mode of operation.
The following GPRS Routing Area Updates are possible: intra SGSN Routing Area Update. inter SGSN Routing Area Update.
The following combined RA and LA updates takes place when an association exists between the
SGSN and the MSC [22]: combined Intra SGSN RA and LA update. combined Inter SGSN RA and LA update.
32
33
4.10.2.8 SMS Impacts
GPRS has the following impacts on SMS:
Ballot Version 103

N.S0028-0
17
18
19
20
21
22
23
5
6
7
8
1
2
3
4
9
10
11
12
13
14
15
16
When operating GPRS in GSM Foreign mode, and both GPRS attached and GSM CS attached, the mobile may originate mobile-originated SMS messages either thru the GSM network or the GPRS network. When operating only in GPRS mode, SMS originations thru the
GPRS network shall be possible.
When operating GPRS in GSM Foreign mode, and both GPRS attached and GSM CS attached, the mobile shall receive mobile-terminated SMS messages either thru the GSM network or the GPRS network. When operating in GPRS only mode, SMS terminations shall be possible.
For GSM native subscribers in GSM native mode, the GSM SMS Service Center (i.e., SMSC) queries the combined GSM-GPRS HLR for routing information and the HLR responds with both the SGSN address as well as the GSM MSC address. Then the SMSC decides to send the SMS message to either the GPRS SGSN or the GSM MSC.
For GPRS in GSM Foreign Mode the ANSI MC shall query the ANSI-41 HLR for the ANSI-41 MSC address and shall be instructed to route the ANSI-41 formatted SMS message to the IIF, emulating both an ANSI-41 MSC and a GSM SMSC, for any of the following conditions: when the subscriber is both GSM CS attached and GPRS attached; or when the subscriber is GPRS only attached; or when the subscriber is GSM CS only attached.
The IIF shall then convert the mobile-terminated ANSI-41 SMS message to a GSM-formatted SMS message and, acting like a GSM SMSC, send it to the GSM MSC or the GPRS SGSN. If the MS is reachable a Network option for routing the SMS messages may be as follows: first - send to the GPRS SGSN; second - send to the GSM MSC.
24
25
26
27
28
29
30
31
32
33
34
35
In the event that the IIF is not able to authenticate the GPRS subscriber, the GPRS service shall be denied. If the ANSI-41 registration process fails due to location update failure or authentication failure, the MS shall be denied access to the GPRS network.
In the event that the IIF receives a mobile terminating ANSI-41 formatted SMS message, and if the
IIF detects that the GSM Foreign Mode subscriber is not reachable (for both packet and circuitswitched services), the IIF shall reply to the ANSI-41 Message Center with an error and when the IIF detects that the subscriber is again reachable, either GPRS or non-GPRS, then the IIF shall notify the
Message Center to retransmit the ANSI-41 formatted SMS message to the IIF.
The GPRS SGSN shall notify (i.e., alert) the IIF, acting as a GPRS HLR, when the handset has memory available and when the handset is “MS present”.
GSM GPRS HLR fault recovery procedures shall also apply to the IIF acting as the GPRS HLR.
36
37
4.10.3.1 GPRS Attach
None identified.
38
39
4.10.3.2 GPRS Detach
None identified.
40 4.10.3.3 Exceptions While Roaming
Ballot Version 104

N.S0028-0
1 None identified.
2
3
4.10.3.4 Exceptions During Intersystem Handoff
None identified.
4
5
None identified.
6
7
8
9
4.10.5.1 Advice of charge (AoC)
None identified
10
11
12
13
4.10.5.2 Authentication
GSM authentication procedures are required to be supported by the IIF in the GPRS home network.
For GPRS in GSM Foreign Mode the authentication procedure is done according to the procedures defined in GSM 02.09[21].
14
15
16
4.10.5.3 Barring of All Outgoing Calls (BAOC)
ODB_BAOC may be provisioned in the IIF, acting as a GPRS HLR, and it applies to Mobile
Originated SMS via the GPRS network.
17
18
19
4.10.5.4 Barring of Outgoing International Calls (BOIC)
ODB_BOIC may be provisioned in the IIF, emulating a GPRS HLR, and it applies to Mobile
Originated SMS via the GPRS network.
20
21
22
23
4.10.5.5 Barring of Outgoing International Calls except those directed to the Home PLMN
(BOIC-exHC)
ODB_BOIC-exHC may be provisioned in the IIF, emulating a GPRS HLR, and it applies to Mobile
Originated SMS via the GPRS network.
24
25
26
4.10.5.6 Operator Determined Barring PLMN-specific
Four ODB PLMN-specific barring programs may be provisioned in the IIF, emulating a GPRS HLR, and each applies to Mobile Originated SMS via the GPRS network.
27
28
29
4.10.5.7 Barring of All Incoming Calls (BAIC)
ODB_BAIC may be provisioned in the IIF, emulating a GPRS HLR, and it applies for GPRS and
Mobile Terminated SMS deliveries thru the GPRS network.
30
31
4.10.5.8 Barring of Incoming Calls when Roaming Outside the Home PLMN (BIC-Roam)
None identified.
32 4.10.5.9 Call Delivery (CD)
Ballot Version 105

N.S0028-0
1
2
3
4
5
6
When a subscriber receives a call termination attempt when operating in GSM foreign mode (e.g.,
ASNI41, TDMA or CDMA136 native subscriber) and connected to a GPRS network, the GSM
Circuit-switched paging is sent through the GPRS SGSN and the IIF is not impacted.
1
Call terminations to the subscriber (e.g., ANSI41, TDMA or CDMA136 native subscriber) operating in
GPRS only mode shall not be possible. However, it is possible for the IIF to send a SMS message to the user thru the GPRS network indicating the calling party number of the missed call.
7
8
4.10.5.10 Call Forwarding—Busy (CFB)
None identified.
9
10
4.10.5.11 Call Forwarding—Default (CFD)
None identified.
11
12
4.10.5.12 Call Forwarding—No Answer / No Reply (CFNA / CFNRy)
None identified.
13
14
4.10.5.13 Call Forwarding—Not Reachable (CFNRc)
None identified.
15
16
4.10.5.14 Call Forwarding—Unconditional (CFU)
None identified.
17
18
4.10.5.15 Call Transfer (CT)
None identified.
19
20
4.10.5.16 Call Waiting / Call Hold (CW / HOLD)
None identified.
21
22
4.10.5.17 Calling Number / Line Identification Presentation (CNIP / CLIP)
None identified.
23
24
4.10.5.18 Calling Number / Line Identification Restriction (CNIR / CLIR)
None identified.
25
26
4.10.5.19 Calling Name Presentation (CNAP)
None identified.
27 4.10.5.20 Calling Name Restriction (CNAR)
1 The MSC and SGSN are both GSM.
Ballot Version 106

1 None identified.
2
3
4.10.5.21 Closed User Group (CUG)
None identified.
4
5
4.10.5.22 Conference Calling / Multi Party Service (CC / MPTY)
None identified.
6
7
4.10.5.23 Do Not Disturb (DND)
None identified.
8
9
4.10.5.24 Emergency Services (Future)
None identified.
10
11
4.10.5.25 Flexible Alerting (FA)
None identified.
12
13
4.10.5.26 Message Waiting Notification (MWN)
None identified.
14
15
4.10.5.27 Mobile Access Hunting (MAH)
None identified.
16
17
4.10.5.28 Password Call Acceptance (PCA)
None identified.
18
19
4.10.5.29 Preferred Language (PL)
None identified.
20
21
4.10.5.30 Priority Access and Channel Assignment (PACA)
None identified.
22
23
4.10.5.31 Remote Feature Control (RFC)
None identified.
24
25
4.10.5.32 Selective Call Acceptance (SCA)
None identified.
26
27
4.10.5.33 Subscriber PIN Access (SPINA)
None identified.
28 4.10.5.34 Subscriber PIN Intercept (SPINI)
Ballot Version 107
N.S0028-0

N.S0028-0
1 None identified.
2
3
4.10.5.35 Three-Way Calling / Multi Party Service (3WC / MPTY)
None Identified.
4
5
4.10.5.36 Voice Message Retrieval (VMR)
None identified.
6
7
8
4.10.5.37 Voice Privacy (VP)
None identified.
Ballot Version 108

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

N.S0028
1
Revision Date Version Comment
0
A
March 2001
April 2001 0
Inclusion of agreed Ballot Comments
Rev A – Inclusion of GPRS authentication failure and registration failure. Alignment of section 4.13 with previous agreed ballot comments.
Editorial changes
B
B
A June 2001
A 1 st
August 2001
A
A
A
14 th
August
2001
15 th
August
2001
26 th
November
2001
July 2001
March 2002
2
6
3
5
4
5
Various technical & editorial changes incorporated th during August 7 Conference call
Ballot Version - Technical changes to 4.13 GPRS
Incorporation of agreed ballot comments from both TIA and T1.
Version 3: Addition of CDMA/GSM two way roaming
Version V&V: Addition of CDMA/GSM two way and one roaming
2
Post Ballot Version ii

N.S0028
1 Contents
2 Abstract ..............................................................................................................................................
i
3 Document Revision History ................................................................................................................
ii
4 List of Tables ...................................................................................................................................
xiii
5 List of Figures .................................................................................................................................
xiv
7 1
8
9
10
11
6 Foreword .......................................................................................................................................
xxiii
Introduction ...........................................................................................................................
1
1.1 General........................................................................................................................
1
1.2
Purpose .......................................................................................................................
1
1.3
Scope ..........................................................................................................................
1
1.4 Organization ................................................................................................................
1
12 2
13 3
14
15
16 4
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
References............................................................................................................................
Stage 2 Information Flows ...................................................................................................
3
Definitions and Acronyms ......................................................................................................
5
3.1
Definitions....................................................................................................................
5
3.2
Acronyms ....................................................................................................................
9
12
4.1
Location Registration .................................................................................................
12
4.1.1
Location Registration in GSM Foreign Mode .....................................................
12
4.1.1.1
MS registers in a GSM network when previously registered in an ANSI-41 network 12
4.1.1.2
MS location updates in a different MSC/VLR.....................................................
14
4.1.1.3
IMSI Detach .....................................................................................................
15
4.1.1.4
IMSI Attach.......................................................................................................
16
4.1.2
Location Registration in ANSI-41 Foreign Mode................................................
17
4.1.2.1
MS registers in an ANSI-41 network when previously registered in a GSM network 17
4.1.2.2
MS location updates in a different MSC/VLR.....................................................
19
4.1.2.3
MS Powers Off .................................................................................................
20
4.1.2.4
MS Powers On .................................................................................................
20
4.1.3
Location Registration in Native Mode................................................................
20
4.1.3.1
MS registers in an ANSI-41 network when previously registered in a GSM network 20
4.1.3.2
MS registers in a GSM network when previously registered in an ANSI-41 network 22
4.2
Fault Recovery Procedures........................................................................................
24
4.2.1
Fault Recovery Procedures in GSM Foreign Mode............................................
24
4.2.1.1
Recovery from Failure at the ANSI-41 HLR.......................................................
24
4.2.1.2
Recovery from Failure at the IIF........................................................................
25
4.2.1.3
Recovery from Failure at the serving GSM VLR ................................................
26
4.2.2
Fault Recovery Procedures in ANSI-41 Foreign Mode ......................................
27
Post Ballot Version iii

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

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

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

N.S0028
8
9
10
11
12
13
5
6
7
1
2
3
4
14
15
16
17
18
19
24
25
26
27
28
20
21
22
23
4.13.2.5
GPRS Detach Followed By Purge .................................................................
206
4.13.2.6
IIF - Initiated Detach.....................................................................................
208
4.13.3
SMS Scenarios...............................................................................................
209
4.13.3.1
SMS Scenarios for Mobile Terminated SMS while GPRS Attached ...............
209
4.13.3.1.1 Successful Mobile Terminated ANSI-41 SMS (CMT) Mapped to GSM SMS 209
4.13.3.1.2 Successful Mobile Terminating ANSI-41 SMS (GHOST/WEMT) Mapped to
GSM SMS ......................................................................................................
211
4.13.3.1.3 Unsuccessful Mobile Terminated Delivery (Failure at SGSN) ......................
212
4.13.3.1.4 Unsuccessful Mobile Terminated Delivery (Failure at IIF) ............................
213
4.13.3.1.5 Alerting for an ANSI-41 Subscriber for GPRS in GSM Foreign Mode...........
214
4.13.4
Message Flows for Mobile Originated SMS when operating GPRS in GSM Foreign
Mode .................................................................................................
215
4.13.4.1 Successful Mobile Originated SMS to MC......................................................
215
4.13.4.2 Unsuccessful Mobile Originated (Failure at MC).............................................
216
4.13.4.3 Unsuccessful Mobile Originated (Failure at IIF) ..............................................
217
4.13.5
Message Waiting Notification while GPRS Attached in GSM Foreign Mode ....
218
4.13.5.1 Indicator in ANSI-41 Registration Notification Return Result mapped to GSM SMS 219
4.13.5.2 ANSI-41 Qualification Directive mapped to GSM SMS ...................................
221
4.13.5.3 Handling at SMS delivery failure at the SGSN or at the Mobile Station ...........
222
4.13.6. Call Delivery Scenarios..................................................................................
224
4.13.6.1 Call Delivery Scenarios in GSM Foreign Mode while GSM CS and GPRS
Attached.........................................................................................................
224
4.13.6.1.1 Call Delivery to ANSI-41 Subscriber Roaming on a GSM/GPRS Network...
224
4.13.6.1.2 Call Delivery to ANSI-41 Subscriber Roaming in a GPRS Network
(Unsuccessful)................................................................................................
226
4.13.6.2
Successful Network-Requested PDP Context Activation Procedure ..............
228
4.13.6.3
Unsuccessful Network-Requested PDP Context Activation Procedure...........
229
4.13.7
Packet Domain Subscriber Data in the IIF......................................................
229
29 Annex 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
37
38
39
40
1 Introduction ...........................................................................................................................1
1.1 General........................................................................................................................1
1.2 Purpose .......................................................................................................................1
1.3 Scope ..........................................................................................................................1
1.4 Organization ................................................................................................................1
Post Ballot Version vii

N.S0028
1 2 References............................................................................................................................2
2
3
4
3 Definitions and Acronyms ......................................................................................................3
3.1 Definitions....................................................................................................................3
3.2 Acronyms ....................................................................................................................6
5
19
20
21
22
23
14
15
16
17
18
6
7
8
9
10
11
12
13
37
38
39
40
41
42
33
34
35
36
28
29
30
31
32
24
25
26
27
43
44
45
46
4 Stage 2 Information Flows .....................................................................................................9
4.1 Location Registration ...................................................................................................9
4.1.1 Location Registration in GSM Foreign Mode .......................................................9
4.1.1.1 MS registers in a GSM network when previously registered in an ANSI-41 network 9
4.1.1.2 MS location updates in a different MSC/VLR.....................................................11
4.1.1.3 IMSI Detach .....................................................................................................12
4.1.1.4 IMSI Attach.......................................................................................................13
4.1.2 Location Registration in ANSI-41 Foreign Mode................................................14
4.1.2.1 MS registers in an ANSI-41 network when previously registered in a GSM network 14
4.1.2.2 MS location updates in a different MSC/VLR.....................................................16
4.1.2.3 MS Powers Off .................................................................................................17
4.1.2.4 MS Powers On .................................................................................................17
4.1.3 Location Registration in Native Mode................................................................17
4.1.3.1 MS registers in an ANSI-41 network when previously registered in a GSM network 17
4.1.3.2 MS registers in a GSM network when previously registered in an ANSI-41 network 19
4.2 Fault Recovery Procedures........................................................................................21
4.2.1 Fault Recovery Procedures in GSM Foreign Mode............................................21
4.2.1.1 Recovery from Failure at the ANSI-41 HLR.......................................................21
4.2.1.2 Recovery from Failure at the IIF........................................................................22
4.2.1.3 Recovery from Failure at the serving GSM VLR ................................................23
4.2.2 Fault Recovery Procedures in ANSI-41 Foreign Mode ......................................24
4.2.2.1 Recovery from Failure at the GSM HLR............................................................24
4.2.2.2 Recovery from Failure at the IIF........................................................................25
4.2.2.3 Recovery from Data Failure at the ANSI-41 VLR...............................................25
4.3 Authentication............................................................................................................26
4.3.1 ANSI-41 Foreign Mode Authentication Activation ..............................................26
4.3.1.1 Receiving AUTHREQ Message ........................................................................26
4.3.1.2 Receiving AFREPORT Message ......................................................................28
4.3.1.3 Receiving ASREPORT Message ......................................................................30
4.3.1.4 Receiving BSCHALL Message .........................................................................32
4.3.1.5 Receiving AUTHDIR Message..........................................................................34
4.3.1.6 Receiving COUNTREQ Message .....................................................................36
4.3.2 GSM Foreign Mode Authentication Activation ...................................................38
4.3.2.1 Authentication Related Messages.....................................................................38
4.4 Subscriber Data Management....................................................................................40
4.4.1 Subscriber Data Management Procedures in ANSI-41 Foreign Mode................40
4.4.1.1 Subscriber Deletion ..........................................................................................40
4.4.1.2 Subscriber Data Modification ............................................................................41
Post Ballot Version viii

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

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

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

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

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

N.S0028
1
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
15 Figure 46: CFU registration...........................................................................................................
73
16 Figure 47: CFU deregistration (erasure) ........................................................................................
74
17 Figure 48: CFU activation .............................................................................................................
75
18 Figure 49: CFU deactivation .........................................................................................................
76
19 Figure 50: CFU invocation ............................................................................................................
77
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
3
Figure 67: Calling number/ line identification presentation: mobile station or fixed terminal to mobile station – GSM Foreign Mode .....................................................................
104
4
5
Figure 68: Calling number/ line identification presentation: mobile station or fixed terminal to 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
12
Figure 74: Invocation of Barring of Supplementary Services Management – ANSI-41 Foreign
Mode ....................................................................................................................
113
13
14
Figure 75: Short Message from a TDMA or CDMA CMT phone to a GHOST or WEMT mobile station, both in native mode ..................................................................................
115
15
16
Figure 76: Short Message from a GHOST or WEMT mobile station to a TDMA CMT or CDMA
CMT Phone, both in native mode ..........................................................................
116
17 Figure 77: Successful Mobile Terminating ANSI-41 SMS (CMT) mapped to GSM SMS...............
118
18
19
Figure 78: Successful Mobile Terminating ANSI-41 SMS (GHOST/WEMT) mapped to GSM
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
8
Figure 101: Clearing of MWN Information after Retrieval of Messages while in ANSI-41
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
13
Figure 105: GSM SMS mapped to ANSI-41 Qualification Directive and to Registration
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
21
Figure 114: Combined GPRS and GSM attach (Option 2: Without timer and without support 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
25
Figure: 117: Inter-SGSN routing area update when GSM CS and GPRS Attached (MSC 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
28 Figure 119: Combined attach when registered on a ANSI-41 MSC (Option 2: without timer ).......
202
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
33
Figure 123: Successful Mobile Terminating ANSI-41 SMS (GHOST/WEMT) mapped to GSM
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
6
Figure 130: Indicator in ANSI-41 Registration Notification Return Result mapped to GSM
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
10
Figure 32: Unsuccessful Call Delivery to an ANSI-136 Subscriber Roaming in a GSM
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
13 Figure 35: CFU registration...........................................................................................................50
14 Figure 36: CFU deregistration (erasure) ........................................................................................52
15 Figure 37: CFU activation .............................................................................................................54
16 Figure 38: CFU deactivation .........................................................................................................56
17 Figure 39: CFU invocation ............................................................................................................57
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
24 Figure 46: CFU registration...........................................................................................................70
25 Figure 47: CFU deregistration (erasure) ........................................................................................71
26 Figure 48: CFU activation .............................................................................................................72
27 Figure 49: CFU deactivation .........................................................................................................73
28 Figure 50: CFU invocation ............................................................................................................74
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
11
12
Figure 67: Calling number/ line identification presentation: mobile station or fixed terminal to mobile station – GSM Foreign Mode .....................................................................101
13
14
Figure 68: Calling number/ line identification presentation: mobile station or fixed terminal to 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
20
21
Figure 74: Invocation of Barring of Supplementary Services Management – ANSI-41 Foreign
Mode ....................................................................................................................110
22
23
Figure 75: Short Message from a TDMA CMT phone to a GHOST mobile station, both in native mode..........................................................................................................112
24
25
Figure 76: Short Message from a GHOST mobile station to a TDMA CMT Phone, both in 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
16
Figure 101: Clearing of MWN Information after Retrieval of Messages while in ANSI-41
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
20
21
Figure 105: GSM SMS mapped to ANSI-41 Qualification Directive and to Registration
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
29
Figure 114: Combined GPRS and GSM attach (Option 2: Without timer and without support 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
33
Figure: 117: Inter-SGSN routing area update when GSM CS and GPRS Attached (MSC remains constant) .................................................................................................182
34 Figure 118: Combined Attach when registered on a ANSI-41 MSC (Option 1: With timer) ...........186
35 Figure 119: Combined attach when registered on a ANSI-41 MSC (Option 2: without timer ).......190
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
12
Figure 130: Indicator in ANSI-41 Registration Notification Return Result mapped to GSM
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
2
10
11
12
13
3
4
5
6
7
8
9
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
This foreword is not part of this standard.
This standard addresses the interworking and interoperability between TIA/EIA IS41 MAP and GSM based networks in the support of subscribers roaming between networks. The objective of the standard is to achieve fully automatic, two-way interoperability between the heterogeneous networks.
Services supported by this standard are described along with the associated information flows and message mappings. However, not all services and associated capabilities of ANSI-41 MAP and GSM
MAP are supported by this standard. In general the attempt has been to focus on the key subscriber services needed in the market.
The focus of the first release of this standard was on common GSM and ANSI-136 TDMA services and associated network signaling (i.e. ANSI-41 MAP and GSM MAP). A pre-requisite for this interoperability is multi-mode mobile stations with an enhanced SIM card for roaming between
ANSI-136, GSM, and AMPS networks.
The first release of the standard did not define or require changes to existing ANSI-41 MAP or GSM
MAP to achieve the described interworking and interoperability. However, due to differences between the services and associated capabilities of the MAP protocols, complete and fully transparent interoperability may not have been achieved for some services. Future releases of this standard may require changes to ANSI-41 MAP, GSM MAP and the associated services to achieve full transparency while roaming between the different networks.
Additional or alternate service descriptions, information flows, and message mappings may be required to support other air interfaces supported by ANSI-41 MAP (e.g., IS-95, CDMA2000). This may be accomplished in future release of this standard.
Existing ANSI-41 and GSM standard specifications cover the use and value of timers controlling the various operations. Therefore, these timers are not part of this standard. However, care should be taken when allocating actual timer values in order to support interoperability between ANSI-41 MAP and GSM MAP.
Aspects of TIA/EIA-136 Rev C have been incorporated into this standard.
Revision A adds GPRS service capability in GSM Foreign Mode.
Revision B adds two way roaming between GSM and CDMA systems
Information disclosed in this document is subject to the export jurisdiction of the US Department of Commerce as specified in Export Administration Regulations (title 15 CFR parts 730 through 774 inclusive). The information contained herein may not be exported or re-exported to Cuba, Iran, Iraq, Libya, North Korea,
Sudan, or Syria. Contact the Telecommunications Industry Association, Arlington, VA or http://ftp.tiaonline.org/tr-45/tr45ahag/public%20documents .
Post Ballot Version xxiii

N.S0028
1
2
10
11
12
13
14
15
16
17
18
3
4
5
6
7
8
9
19
20
21
22
23
24
When a subscriber to one network type (e.g., ANSI-41) roams to a network of another type (e.g.,
GSM), interworking and interoperability functions are required to support the subscriber and enable service. This standard describes an Interworking and Interoperability Function (IIF) to support this cross-technology roaming between ANSI-41 and GSM networks. The IIF supports a multi-mode mobile station with a removable Subscriber Identity Module (SIM). The standard also defines the required network message mappings between ANSI-41 MAP and GSM MAP to support the mobile terminal and associated services.
This standard includes the support of cross-technology roaming from an ANSI-41 based network to a
GPRS network. The GPRS network may be coupled with a GSM network. This feature requires enhancement to the Interworking and Interoperability Function (IIF) which supports a multi-mode mobile station and Subscriber Identity Module (SIM) with GPRS functionality.
Optionally, IIF may support one way-roaming only from CDMA to GSM network. In this case since no data is provisioned at IIF level, IIF must generate the GSM triplets using as input the authentication parameters returned by ANSI-41 HLR/AC. and ANSI-41 HLR/AC must be compliant with PN-4925 (to be published as TIA/EIA-868 [28]. All the changes are made on the assumption the new requirements for UIM/handsets are working. (Annex B)
The purpose for this standard is to define and describe the functions necessary for roaming between
ANSI-41 MAP [1] and GSM MAP [6] based networks in the support of roaming subscribers. This includes a capability to allow a subscriber to an ANSI-41 based network (e.g., an ANSI136 41,
TDMA or CDMA native subscriber) with a mobile terminal supporting GPRS service to roam to a
GPRS network in GSM Foreign Mode.
25
26
27
28
29
30
The scope of this standard are the services, information flows and message mappings which require interworking and interoperability functional specifications to support roaming between ANSI-41 MAP and GSM MAP networks.
The scope of this volume describes the “Information Flows” and addresses the functionality required to support GSM and ANSI-41 network interoperability.
31
35
36
37
32
33
34
38
This standard is organized into the following volumes:
Volume 0 – Overview and Interworking Reference Model
Volume 1 – Service Descriptions
Volume 2 – Information Flows
Volume 3 – Message Mappings
This volume is organized according to the following:
2 References - a list of references specific to this volume of the Standard.
Post Ballot Version 1

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

N.S0028
1
2
3
[1] TIA/EIA IS-41-D: “Cellular Radiotelecommunications Intersystem Operations,” December
1997, ANSI.
4 [2]
5 [3]
TIA/EIA/IS-751: “TIA/EIA-41-D Modifications to support IMSI”, PN-3892 version 7.
TIA/EIA/IS-807: “TIA/EIA-41-D Enhancements for Internationalization”
6
7
8
[4] TS 100 901 v 6.1.0 (1998-07); “Digital cellular telecommunications system (Phase 2+);
Technical realization of the Short Message Service (SMS); Point-to-Point (PP),” (GSM 03.40 version 6.1.0 Release 1997)
9
10
[5] TS 100 542 v 7.0.1 (1999-07); "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services;Stage2 (GSM 03.81 version 7.0.1 Release 1998).
11
12
13
14
[6]
[7]
TS 100 974 v 6.2.0 (1998-11): “Digital cellular telecommunication system (Phase 2+); Mobile
Application Part (MAP) specification,” (GSM 09.02 version 6.2.0 Release 1997).
TS 100 974 v 7.1.0 (1999-08): “Digital cellular telecommunication system (Phase 2+); Mobile
Application Part (MAP) specification,” (GSM 09.02 version 7.1.0 Release 1998).
15
16
17
18
19
20
21
22
[8] TS 101 629 v 6.0.0 (1999-04): "Digital cellular telecommunication system (Phase 2+);
Support of Optimal Routeing (SOR); Service definition (Stage 1)". (GSM 02.79 v 6.0.0
Release 1997)
[9] TS 101 045 v 6.2.0 (1999-11): "Digital cellular telecommunication system (Phase 2+);
Support of Optimal Routeing (SOR); Technical realisation" (GSM 03.79 v 6.2.0 Release
1997).
[10] Draft ETSI EN 301 344: “Digital cellular telecommunication system (Phase 2+); General
Packet Radio Service; Service description (Stage 2)" (GSM 03.60 v 6.8.0 Release 1997).
23
24
25
26
27
28
29
30
31
32
33
34
35
[14] TIA/EIA-95-B - Mobile Station-Base Station Compatibility Standard for Dual-Mode Spread
Spectrum Systems; Published October 1998.
[15] "TIA/EIA-IS-2000-A, cdma2000 Series, March 2000, plus addenda"Mobile Station-Base Station
Compatibility Standard for Dual-Mode Spread Spectrum Systems;
[16] TIA/EIA-868 – ANSI-41-D Network Based Enhancements to support one-way roaming to
GSM, Published TBD. [12]"Enhanced Cryptographic Algorithms, Revision B," TR45AHAG, Published TBD
Post Ballot Version 3

1
N.S0028
Post Ballot Version 4

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

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

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

N.S0028
1
2
3
4
5
6
7
8
9
10
11
12
GSM Native Subscriber
GSM native subscriber indicates an end user whose primary or home subscription resides in a GSM network. These subscribers include both home subscribers from the GSM network, as well as roamers from other GSM networks.
Mobile Station
The mobile equipment and the SIM together make up the mobile station, which is the wireless radiotelephone used by the subscriber.
Subscriber Identity Module
A smart card that plugs into the mobile equipment and that contains the authentication algorithms, and stores service-oriented subscription information.
Post Ballot Version 8

1
14
15
16
17
18
19
10
11
12
13
20
21
22
23
24
8
9
6
7
2
3
4
5
29
30
31
32
25
26
27
28
AC
ADN
AuC
AMPS
ANSI
BAIC
BAOC
BIC-Roam
Authentication Center in TIA/EIA-41 based networks
Abbreviated Dialing Numbers
Authentication Center in GSM networks
Advanced Mobile Phone Service
American National Standards Institute
Barring of All Incoming Calls
Barring of All Outgoing Calls
Barring of Incoming Calls while Roaming Outside HPLMN Country
BOIC Barring of Outgoing International Calls
BOIC-exHC Baring of Outgoing International Calls Except to HPLMN Country
CDMA
CFB
Code-Division Multiple Access
Call Forwarding Busy
CFNA
CFNRc
CFNRy
CFU
CPHS
DCS
Call Forwarding No Answer
Call Forwarding Not Reachable
Call Forwarding No Reply
Call Forwarding Unconditional
Common PCN Handset Specification
Data Coding Scheme
EIA
ESN
Electronics Industry Association
Electronic Serial Number
ETSI
FDN
FSM
European Telecommunications Standards Institute
EUI ESN Usage Indicator
FC Feature
Fixed Dialing Numbers
GGSN
GHOST
GMSC
GPRS
GSM
HLPI
Gateway GPRS Support Node
GSM Hosted SMS Teleservice
Gateway Mobile Switching Center
General Packet Radio Service
Global System for Mobile Communications
Higher Layer Protocol Indicator
Post Ballot Version 9
N.S0028

N.S0028
12
13
14
15
16
10
11
8
9
3
4
1
2
5
6
7
28
29
30
31
32
24
25
26
27
20
21
22
23
17
18
19
HLR
HPLMN
IIF
IMEI
IMSI
Home Location Register
Home Public Land Mobile Network
Interworking and Interoperability Function
International Mobile Equipment Identifier
International Mobile Subscriber Identity
IRDB
ITU
Intelligent Roaming Database
International Telecommunications Union
MAP Mobile Application Part
MC ANSI136 41 Message Center (for SMS)
MDN Mobile Directory Number
ME Mobile
MIN Mobile Identification Number
MO Mobile
MS Mobile
MWN
NAM
NSDB
ODB
OTA
PCS
PDU
PIN
PLMN
PRN
PSAP
MSC
MSCIN
MSID
MSISDN
Mobile Switching Center
MSC Identification Number
Mobile Station Identity
Mobile Subscriber ISDN Number
MSRN Mobile Station Routing Number
MT Mobile
Message Waiting Notification
Numeric Assignment Module
Network Selection Database
Operator Determined Barring
Personal Communications Service
Packet Data Unit
Personal Identification Number
Public Land Mobile Network
Provide Roaming Number
Public Safety Access Point
Post Ballot Version 10

12
13
14
15
16
10
11
8
9
3
4
1
2
5
6
7
20
21
22
23
17
18
19
SESN
SGSN
SIM Electronic Serial Number
Serving GPRS Support Node
SID System
SIM Subscriber Module
SMDPP Short Message Delivery Point-to-Point
SMS
SMS-C
SOC
SS7
Short Message Service
GSM Short Message Service Center
System Operator Code
Signaling System 7
TDMA Time Division Multiple Access
TP-FCS TP Cause
TIA Telecommunications Industry Association
TLDN
TMSI
Temporary Location Directory Number
Temporary Mobile Station Identity
TS Teleservice
TSAR
UWCC
UDH
VLR
VPLMN
WAP
WEMT
Teleservice Segmentation and Reassembly
Universal Wireless Communications Consortium
Universal Data Header
Visitor Location Register
Visitor Public Land Mobile Network
Wireless Application Protocol
Wireless Enhanced Messaging Teleservices
24
N.S0028
Post Ballot Version 11

9
10
11
N.S0028
1
2
3
4
5
6
7
8
B.1.1.2 4.1.1.1 MS registers in a GSM network when previously registered in an
ANSI-41 network
When an ANSI136 41 subscriber registers in a GSM network, when previously registered in an
ANSI-41 network, the MS performs a location update using the IMSI as shown in Figure 1. The IIF emulates both a GSM HLR/AuC and an ANSI-41 VLR in this case.
MS
Update Location Req
(IMSI)
MSC/
VLR
IIF
Authentication Info
Authentication Info Ack
Authentication Req
Authentication Res
Update Location Req
(IMSI)
REGNOT
(MIN/IMSI)
HLR
REGCANC
MSC/
VLR regcanc regnot
Insert Sub Data k
Insert Sub Data Ack
Update Location Ack m
Update Location Ack
GSM NETWORK
ANSI-41 NETWORK
Figure 1: Registration on a GSM Network – GSM Foreign Mode n l j i a b c d e f g h
Post Ballot Version 12

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

N.S0028
1
2
3
B.1.1.3 4.1.1.2 MS location updates in a different MSC/VLR
When an ANSI136 41 subscriber roams within a GSM PLMN and registers in a different MSC/VLR area, the MS performs a location update using the IMSI as shown in Figure 2.
MS
Update Location Req
(IMSI)
MSC/
VLR
IIF
Authentication Info
Authentication Info Ack
Authentication Req
Authentication Res
PVLR
Update Location Req
(IMSI)
Cancel Location
Cancel Location Ack
REGNOT regnot
Insert Sub Data
Insert Sub Data Ack
Update Location Ack
Update Location Ack
HLR
4
5
11
12
13
14
15
16
17
18
6
7
8
9
10
Figure 2: Registration in a different MSC/VLR – GSM Foreign Mode a. MS powers up and registers in a different MSC/VLR in the same GSM network. The MS sends an Update Location Request (which includes the IMSI) to the network. b. If the serving VLR does not have authentication information in order to perform authentication i.e. authentication triplets, it requests authentication information from the IIF. The IIF emulates a GSM HLR/AuC in this case. c. The IIF returns the necessary authentication information. d. VLR initiates authentication towards the MS. e. MS responds to the authentication request. f g h a b c d e j i l k m n
Post Ballot Version 14

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

N.S0028
1
9
10
11
5
6
7
8
2
3
4
12
B.1.1.5 4.1.1.4 IMSI
If an MS powers on and registers on the same MSC/VLR (that has not deleted the subscriber record) while operating in GSM Foreign mode and the IMSI Attach procedure is supported, it shall perform an
IMSI Attach as described in GSM 09.02 [6]. Neither the IIF or the home HLR is informed.
If an MS powers on and registers on the same MSC/VLR (that has deleted the subscriber record), while operating in GSM Foreign mode and the IMSI Attach procedure is supported, it shall perform an
IMSI Attach as described in GSM 09.02 [6]. The IIF shall be informed as shown in Section 4.1.1.2.
(however the IIF shall not send a Cancel Location to the MSC/VLR as it is the same MSC/VLR).
If an MS powers on and registers on a different MSC/VLR, while operating in GSM Foreign mode and the IMSI Attach procedure is supported, it shall perform an IMSI Attach as described in GSM 09.02
[6]. The IIF shall be informed as shown in Section 4.1.1.2.
Post Ballot Version 16

N.S0028
1
2
3
4
5
6
B.1.1.6 4.1.2.1
GSM network
MS registers in an ANSI-41 network when previously registered in a
When a GSM subscriber registers in an ANSI-41 network, when previously registered in a GSM network, the MS performs a location update using an IMSI or MIN as shown in Figure 3. The IIF emulates both an ANSI-41 HLR and a GSM VLR in this case.
MS
MSC/
VLR
IIF
HLR
MSC/
VLR
Registration
(MIN/IMSI)
AUTH REQ
Auth req
REGNOT a b c d e
Update Location Req
(IMSI)
Cancel Location
Update Location Ack
Cancel Loc Ack f g h
Reg_ack regnot j i
GSM NETWORK
ANSI-41 NETWORK
7
10
11
12
13
14
15
16
17
18
19
8
9
Figure 3: Registration on an ANSI-41 network – ANSI-41 Foreign Mode a. Upon MS power up, if global authentication is active, the MS first sends an Authentication message to the network. The MS then sends a Registration message (which includes the IMSI or MIN) to the network. b. If global authentication is active upon registration, the serving VLR initiates an AUTHREQ towards the IIF. The IIF emulates an ANSI-41 HLR/AC in this case.
The reported ESN for this subscriber shall be dynamic to support SIM-based roaming. The IIF shall authenticate the subscriber using this reported ESN.
Post Ballot Version 17

N.S0028
16
17
18
19
20
21
22
10
11
12
13
14
15
4
5
6
7
8
9
1
2
3
23
24 c. The IIF acknowledges the authentication request. If authentication is successful, the IIF shall store the reported ESN as the currently validated dynamic ESN for this subscriber. The currently validated dynamic ESN shall be maintained by the ANSI-41 HLR emulation function in the IIF. d. VLR sends a REGNOT message to the IIF. e. The IIF translates the ANSI-41 MAP REGNOT into a GSM MAP Update Location Request
(which includes the IMSI) and sends the Update Location Request to the subscribers home
HLR. The IIF is emulating a GSM VLR when it sends the Update Location Request. f. The HLR updates its location information and deletes the previous VLR record by sending a
Cancel Location to the previous VLR. g. The VLR acknowledges the Cancel Location. Note: The GSM Insert Subscriber data procedure between the HLR and the IIF takes place between steps g and h. h. The HLR acknowledges the Update Location Request i. The IIF acknowledges the REGNOT. The acknowledgement also contains the subscriber data download to the new serving VLR.
The MSC/VLR acknowledges the Registration message from the MS.
Post Ballot Version 18

N.S0028
1
2
3
B.1.1.7 4.1.2.2 MS location updates in a different MSC/VLR
When a GSM subscriber roams within an ANSI-41 network and registers in a different MSC/VLR area, the MS performs a location update using an IMSI or MIN as shown in Figure 4.
MS
Registration
(MIN/IMSI)
MSC/
VLR
AUTH REQ
Auth req
REGNOT
IIF
PVLR
REGCANC
(MIN) regcanc
Location Update Req
Location Update Ack regnot
Reg_ack
HLR j f g h i a b c d e
4
7
8
9
10
11
12
13
14
15
16
17
18
19
5
6
Figure 4: Registration in a different MSC/VLR – ANSI-41 Foreign Mode a. MS powers up and registers in a new MSC/VLR in the same ANSI-41 network. If global authentication is active, the MS sends an Authentication message to the network. The MS also sends a Registration message (which includes the IMSI / MIN) to the network. b. If global authentication is active upon registration, the serving VLR initiates an AUTHREQ towards the IIF. The IIF emulates an ANSI-41 HLR/AC in this case.
The reported ESN for this subscriber shall be dynamic to support SIM-based roaming. The IIF shall authenticate the subscriber using this reported ESN. c. The IIF acknowledges the authentication request. If authentication is successful, the IIF shall store the reported ESN as the currently validated dynamic ESN for this subscriber.
Post Ballot Version 19

N.S0028
10
11
12
13
14
15
16
17
18
19
4
5
6
7
8
9
1
2
3
20
The currently validated dynamic ESN shall be maintained by the ANSI-41 HLR emulation function in the IIF. d. VLR sends a REGNOT message to the IIF. e. The IIF deletes the subscriber record in the previous VLR (PVLR), by sending a REGCANC to the PVLR. f. The PVLR acknowledges the REGCANC. g. Optionally, the IIF may send an Update Location Request to the HLR to indicate the changed location. h. The HLR acknowledges the update location. i. The IIF acknowledges the REGNOT. j. The new serving MSC/VLR acknowledges the Registration message from the MS.
B.1.1.8 4.1.2.3 MS Off
21
22
23
24
If a mobile station powers off while operating in ANSI-41 Foreign mode, the IIF receives an MS
INACTIVE message from the serving VLR. This results in the IIF setting the ‘IMSI Detached’ Flag. If the MS remains inactive for an extended period of time (determined by operator), the IIF may delete the subscriber record associated with that MS and send an MS Purge to the HLR.
29
30
31
32
33
25
26
27
28
B.1.1.9 4.1.2.4 MS On
If a mobile station powers on and registers on an MSC/VLR, while operating in ANSI-41 Foreign mode, normal registration procedures apply.
B.1.1.10 4.1.3.1
GSM network
MS registers in an ANSI-41 network when previously registered in a
When an ANSI subscriber registers in an ANSI-41 network (Native Mode), when previously registered in a GSM Network (Foreign Mode), the MS performs a location update and the temporary subscriber data in the IIF is deleted as shown in figure 5.
Post Ballot Version 20

N.S0028
MS
Registration
(MSID)
MSC/
VLR
AUTH REQ
HLR IIF PVLR a b
Auth req c
Reg_ack
REGNOT
(MSID) regnot
REGCANC
(MSID) regcanc
Cancel Location
(IMSI)
Cancel Location Ack f g h j i d e
ANSI-41 NETWORK
GSM NETWORK
1
2
3
4
5
13
14
15
16
17
18
6
7
8
9
10
11
12
19
20
21
22
23
24
25
Figure 5: Registration in an ANSI-41 Network (Native Mode) a. MS powers up and registers in a new MSC/VLR in an ANSI-41 network.
If global authentication is active upon registration, the serving VLR initiates an AUTHREQ towards the ANSI-41 HLR.
The reported ESN for this subscriber shall be dynamic to support SIM-based roaming. The HLR shall authenticate the subscriber using this reported ESN. c. The HLR acknowledges the authentication request. If authentication is successful, the HLR shall store the reported ESN as the currently validated dynamic ESN for this subscriber. d. The serving VLR sends a REGNOT to the HLR. e. The HLR sends a REGCANC to the IIF. f. The IIF deletes the temporary subscriber data and sends a Cancel Location to the previous VLR in the GSM network. g. The previous VLR deletes the relevant subscriber data and acknowledges the request. h. The IIF acknowledges the REGCANC. i. HLR updates the new serving VLR. j. The VLR acknowledges the update towards the MS.
Post Ballot Version 21

N.S0028
1
2
3
4
5
B.1.1.11 4.1.3.2
41 network
MS registers in a GSM network when previously registered in an ANSI-
When a GSM subscriber registers in a GSM network (Native Mode), when previously registered in an
ANSI-41 Network (Foreign Mode), the MS performs a location update and the temporary subscriber data in the IIF is deleted as shown in figure 6.
MS
MSC/
VLR
HLR
Update Location Req
(IMSI)
Update Location Req
(IMSI)
Cancel Location
(IMSI)
IIF
REGCANC
(MSID) regcanc
PVLR
Cancel Location Ack
Insert Sub Data
Update Location Ack
Insert Sub Data Ack
Update Location Ack
GSM NETWORK ANSI-41 NETWORK j f g i h d e a b c
13
14
15
16
17
18
19
20
8
9
10
11
12
6
7
Figure 6: Registration in a GSM Network (Native Mode) a. MS powers up and registers in a new MSC/VLR in a GSM network. b. The serving VLR sends an Update Location Request to the HLR. c. The HLR sends a Cancel Location to the IIF. d. The IIF deletes the temporary subscriber data and sends a REGCANC to the previous VLR in the
ANSI-41 network. e. The Previous VLR deletes the relevant subscriber data and acknowledges the request. f. The IIF acknowledges the Cancel Location Request.
Post Ballot Version 22

4
5
6
7
8
1
2
3
9 g. HLR updates the new serving VLR. h. The VLR acknowledges the update. i. The HLR acknowledges the Update Location Request. j. The VLR acknowledges the Update Location Request towards the MS.
N.S0028
Post Ballot Version 23

N.S0028
1
9
10
11
12
13
14
15
16
17
2
3
4
5
6
7
8
After a fault of a location register, the fault recovery procedures ensure that the subscriber data in the
VLR becomes consistent with the subscriber data that are stored in the IIF (emulating an HLR) or that subscriber data in the IIF (emulating a VLR) becomes consistent with the subscriber data that are stored in the HLR for the MS concerned, and that the location information in the IIF (emulating an
HLR) and VLR or the HLR and IIF (emulating a VLR) reflect accurately the current location of the MS.
Existing fault recovery procedures described in GSM 09.02 [6] or ANSI-41D [1] are directly applicable to the IIF, while the IIF is emulating a GSM or ANSI 41 functional entity.
B.1.1.12 4.2.1.1 Recovery from Failure at the ANSI-41 HLR
When the ANSI-41 HLR returns to a stable state after suffering a failure, it shall send the IIF
(emulating an ANSI-41 VLR) an UnreliableRoamerDataDirective message (UNRELDIR) as described in ANSI 41.3 D [1], informing the IIF that it has experienced a failure which has rendered the HLR’s roaming MS data unreliable. Figure 7 below shows the call flow.
When the roaming MS next makes radio contact, the serving GSM VLR shall initiate the location updating procedure towards the IIF.
VLR
IIF
HLR
RESET
UNRELDIR unreldir a b c
GSM NETWORK ANSI-41 NETWORK
18
19
20
21
22
23
24
25
26
27
28
29
30
Figure 7: Failure at the ANSI-41 HLR (GSM Foreign Mode) a. HLR returns to stable state following a failure and sends an UNRELDIR towards the IIF. b. The IIF acknowledges the request and removes all the temporary subscriber data of all the MSs associated with that HLR from its memory. c. The IIF may reload its data from a non-volatile backup (optional) and shall send a RESET towards each of the serving VLRs. The RESET message contains a unique identity, identifying the ANSI-41 HLR that failed and that is connected to the IIF.
When the MS next establishes authenticated radio contact (including a mobile originated call attempt), the VLR initiates location updating towards the IIF (See 4.1.1).
Post Ballot Version 24

N.S0028
1
2
3
4
5
6
B.1.1.13 4.2.1.2 Recovery from Failure at the IIF
If the IIF suffers a failure, it shall follow the recovery procedure described in GSM 09.02 [6] section
19.3.2 (i.e. IIF is acting like a GSM HLR). As part of the recovery procedure, the IIF shall send all the serving GSM VLRs a RESET message for each associated ANSI-41 HLR as shown in step a) in
Figure 8. The message shall contain a unique identifier for the ANSI-41 HLR. In addition, the IIF shall send a BULKDEREG to all affected ANSI-41 HLRs (i.e. IIF is acting like an ANSI-41 VLR).
VLR
RESET
IIF
HLR
BULKDEREG bulkdereg a b c
ANSI-41 NETWORK GSM NETWORK
7
16
17
18
19
20
8
9
10
11
12
13
14
15
Figure 8: IIF Failure (GSM Foreign Mode) a. The IIF sends a RESET towards each of the affected VLRs, containing a unique identity, identifying the ANSI-41 HLRs connected to the IIF. b. The IIF sends a BULKDEREG towards all the affected ANSI-41 HLRs. On reception of the
BULKDEREG the HLR(s) follow(s) the procedures as described in ANSI-41.6D [1]. c. The ANSI-41 HLR(s) responds with a bulkdereg.
When the MS next establishes authenticated radio contact (including a mobile originated call attempt), the VLR initiates location updating towards the IIF (See 4.1.1).
Post Ballot Version 25

N.S0028
1
2
3
4
5
6
B.1.1.14 4.2.1.3 Recovery from Failure at the serving GSM VLR
If the VLR suffers a failure, it shall follow the recovery procedure described in GSM 09.02 [6] section
19.3.1. As part of the recovery procedure, when a MS next establishes authenticated radio contact, the VLR shall initiate location updating towards the IIF (See 4.1.1).
If the VLR receives a request for a roaming number from the IIF following a failure, the VLR shall send a RESTORE DATA message to the IIF as shown in Figure 9.
VLR
PROVIDE ROAMING NO
PROVIDE ROAMING NO ACK
RESTORE DATA
INSERT SUB DATA
INSERT SUB DATA ACK
RESTORE DATA ACK
IIF
HLR
ROUTREQ routreq g
ANSI-41 NETWORK h c d a b f e
GSM NETWORK
9
10
11
12
13
14
15
16
7
8
Figure 9: Terminating Call Flow following a GSM VLR Failure a. Terminating call arrives for MS following a GSM VLR failure. b,c,d The IIF follows normal mobile terminated call handling procedures (See 4.5.2.1). e. The VLR may request more authentication sets prior to sending Restore Data to the IIF to request subscriber data. f. The IIF downloads subscriber data to the VLR.
17
18 g. The VLR acknowledges the operation. h. The IIF acknowledges the Restore Data Operation.
19
Post Ballot Version 26

N.S0028
1
2
3
4
5
6
7
B.1.1.15 4.2.2.1 Recovery from Failure at the GSM HLR
When a GSM HLR undergoes a restart, it shall follow the procedures described in GSM 09.02 [6] section 19.3.2. As part of the recovery procedure, the HLR sends the IIF a RESET message, informing the IIF that it has experienced a failure, which has rendered the HLR’s roaming MS data unreliable. When the roaming MS next makes radio contact, the serving ANSI-41 VLR shall initiate the location updating procedure towards the IIF. Figure 10 below shows the call flow.
HLR
IIF
VLR
RESET
UNRELDIR unreldir a b c
ANSI-41 NETWORK
GSM NETWORK
8
9
10
17
18
19
20
21
22
23
24
11
12
13
14
15
16
Figure 10: Failure at a GSM HLR (ANSI-41 Foreign Mode) a. The HLR follows the recovery procedures described in GSM 09.02 [6] section 19.3.2. The affected sends a RESET towards the IIF. b. The IIF follows the procedures described in GSM 09.02 [6] section 19.3.2 on reception of the
RESET and sends an UNRELDIR towards each of the serving ANSI-41 VLRs. The UNRELDIR message contains a unique identity, identifying the affected GSM HLR. c. The VLR follows the procedures described in ANSI-41.3 [1] and ANSI-41.6 [1] and acknowledges the UNRELDIR.
When the MS next establishes authenticated radio contact (including a mobile originated call attempt), the VLR initiates location updating towards the IIF (See 4.1.2.1).
Post Ballot Version 27

N.S0028
10
11
12
13
14
15
16
17
18
1
2
3
4
5
6
7
8
9
B.1.1.16 4.2.2.2 Recovery from Failure at the IIF
If the IIF suffers a failure, it shall follow the recovery procedure described in ANSI-41.6 [1] (i.e. IIF is acting like an ANSI HLR). As part of the recovery procedure, the IIF shall send all the serving
ANSI-41 VLRs an UNRELDIR message for each associated GSM HLR as shown in steps b and c in
Figure 10. The message shall contain a unique identifier for the GSM HLR.
When the MS next establishes authenticated radio contact (including a mobile originated call attempt), the VLR initiates location updating towards the IIF (See 4.1.2.2).
If following an IIF failure, the IIF receives a request for routing information, it shall send a RESTORE
DATA towards the requesting GSM HLR.
B.1.1.17 4.2.2.3 Recovery from Data Failure at the ANSI-41 VLR
If the ANSI-41 VLR suffers a failure, it shall follow the recovery procedure described in ANSI-41.6 [1].
As part of the recovery procedure, when an MS next establishes authenticated radio contact, the VLR shall initiate location updating towards the IIF.
Upon receipt of a BULKDEREG, the IIF shall clear the location pointer for those MSs that were registered on that VLR. If following the reception of a BULKDEREG, the IIF receives a request for routing information, the terminating call towards the MS shall not be possible until the MS has performed a successful location registration.
Post Ballot Version 28

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

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

N.S0028
1 B.1.1.19 4.3.1.2 Receiving AFREPORT Message
2
3
B.1.1.19.1 4.3.1.2.1 Successful AFREPORT Response Received from ANSI-41 AC
ANSI-41
Serving
System
MSC/VLR IIF
ANSI-41
AC
8
9
AFREPORT a
AFREPORT b afreport c afreport d
6
7
4
5 Figure 13: AFREPORT - Successful Case a,b,c,d The IIF is emulating an ANSI-41 HLR. For successful processing, see to ANSI-41 [1].
Post Ballot Version 31

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

N.S0028
1 B.1.1.20 4.3.1.3 Receiving ASREPORT Message
2
3
B.1.1.20.1 4.3.1.3.1 Successful ASREPORT Response Received from ANSI-41 AC
ANSI-41
Serving
System
MSC/VLR IIF
ANSI-41
AC
ASREPORT
ASREPORT asreport a b c asreport d
4
5
6
Figure 15: ASREPORT - Successful Case
7 a,b,c,d The IIF is emulating an ANSI-41 HLR. For successful processing, see to ANSI-41 [1].
8
Post Ballot Version 33

N.S0028
1
2
B.1.1.20.2 4.3.1.3.2 ASREPORT Failure Reported by IIF
ANSI-41
Serving
System
MSC/VLR IIF
ANSI-41
AC
ASREPORT
ASREPORT asreport
(error handling) asreport
(error handling) d
3
4
5
Figure 16: ASREPORT - Unsuccessful Case
6 a,b,c,d The IIF is emulating an ANSI-41 HLR. For error handling see to ANSI-41 [1].
7 a b c
Post Ballot Version 34

N.S0028
1 B.1.1.21 4.3.1.4 Receiving BSCHALL Message
2
3
B.1.1.21.1 4.3.1.4.1 Successful BSCHALL Response Received from ANSI-41 AC
ANSI-41
Serving
System
MSC/VLR IIF
ANSI-41
AC
BSCHALL
BSCHALL bschall a b c bschall d
4
5
6
Figure 17: BSCHALL - Successful Case
7 a,b,c,d The IIF is emulating an ANSI-41 HLR. For successful processing, see to ANSI-41 [1].
8
Post Ballot Version 35

N.S0028
1
2
B.1.1.21.2 4.3.1.4.2 BSCHALL Failure Reported by IIF
ANSI-41
Serving
System
MSC/VLR IIF
ANSI-41
AC
BSCHALL
BSCHALL bschall
(error handling) bschall
(error handling) d
3
4
5
Figure 18: BSCHALL - Unsuccessful Case
6 a,b,c,d The IIF is emulating an ANSI-41 HLR. For error handling see to ANSI-41 [1].
7 a b c
Post Ballot Version 36

N.S0028
1 B.1.1.22 4.3.1.5 Receiving AUTHDIR Message
2
3
B.1.1.22.1 4.3.1.5.1 Successful AUTHDIR Response Received from Serving System
ANSI-41
Serving
System
MSC/VLR IIF
ANSI-41
AC
AUTHDIR authdir
AUTHDIR a b c authdir d
4
5
6
Figure 19: AUTHDIR - Successful Case
7 a,b,c,d The IIF is emulating an ANSI-41 HLR. For successful processing, see to ANSI-41 [1].
8
Post Ballot Version 37

N.S0028
1
2
B.1.1.22.2 4.3.1.5.2 AUTHDIR failure Received from Serving System
ANSI-41
Serving
System
MSC/VLR IIF
ANSI-41
AC
AUTHDIR
AUTHDIR authdir
(error handling) authdir
(error handling) d
3
4
5
Figure 20: AUTHDIR - Unsuccessful Case
6 a,b,c,d The IIF is emulating an ANSI-41 HLR. For error handling see to ANSI-41 [1].
7 a b c
Post Ballot Version 38

N.S0028
1 B.1.1.23 4.3.1.6 Receiving COUNTREQ Message
2
3
B.1.1.23.1 4.3.1.6.1 Successful COUNTREQ Response Received from Serving System
ANSI-41
Serving
System
MSC/VLR IIF
ANSI-41
AC
COUNTREQ countreq
COUNTREQ a b c countreq d
4
5
6
Figure 21: COUNTREQ - Successful Case
7 a,b,c,d The IIF is emulating an ANSI-41 HLR. For successful processing, see to ANSI-41 [1].
8
Post Ballot Version 39

N.S0028
1
2
B.1.1.23.2 4.3.1.6.2 COUNTREQ Failure Received from Serving System
ANSI-41
Serving
System
MSC/VLR IIF
ANSI-41
AC
COUNTREQ
COUNTREQ countreq
(error handling) countreq
(error handling) d
3
4
5
Figure 22: COUNTREQ - Unsuccessful Case
6 a,b,c,d The IIF is emulating an ANSI-41 HLR. For error handling see to ANSI-41 [1]. a b c
7
Post Ballot Version 40

1
2
B.1.2
B.1.2.1 4.3.2.1 Authentication Related Messages
3
4
B.1.2.1.1 4.3.2.1.1 Receiving SEND_AUTHENTICATION_INFO (Version 2 MAP)
GSM
Serving
System
GSM
AuC
IIF MSC/VLR
N.S0028
SEND_AUTH_INFO send_auth_info
SEND_AUTH_INFO a b c send_auth_info d
5
6
7
Figure 23: SEND_AUTH_INFO
8 a,b,c,d The IIF is emulating a GSM HLR. For successful processing, see to GSM 09.02 [6].
9
Post Ballot Version 41

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

N.S0028
1
2
3
4
5
6
7
Two types of subscriber data management procedures are defined in GSM 09.02 [6]. These procedures impact the GSM subscribers HLR, the IIF and the serving VLR when the subscriber is operating in ANSI-41 Foreign Mode. For these procedures, only modification to temporary subscriber data in the IIF is addressed. The procedures are (1) Subscriber Deletion and (2) Subscriber Data
Modification.
8
9
10
B.1.2.2 4.4.1.1 Subscriber
In this procedure, temporary subscriber data shall be removed from the HLR, IIF and the serving
MSC/VLR as shown in Figure 25.
MSC/
VLR
REGISTRATION_
CANCELLATION
Registration_ cancellation
IIF
Cancel Location
HLR
Delete Subscriber
OMC a b
Cancel Location Ack c d e
Subscriber Deleted f
11
12
13
14
15
16
17
18
19
ANSI-41 NETWORK
GSM NETWORK
Figure 25: Subscriber Deletion – ANSI-41 Foreign Mode a. Operations and Maintenance Center (OMC) initiates a request to delete a subscriber. b. The HLR deletes the subscriber data from the HLR and sends a Cancel Location request to the IIF. c. The IIF deletes the temporary subscriber data from the IIF and sends a Registration
Cancellation to the serving MSC/VLR. The CancellationType in this operation shall be set to
“Discontinue” to tear down any active call. d. The VLR deletes the subscriber data from the VLR and returns an acknowledgement to the
IIF.
Post Ballot Version 43

N.S0028
1
2
3
4
5
6
7
8 e. The IIF acknowledges the cancel location request.
The HLR acknowledges the delete subscriber request.
B.1.2.3 4.4.1.2 Subscriber Data Modification
The OMC can modify subscriber data in several different ways e.g. withdrawal of a basic or supplementary service, roaming modifications, data modifications to both HLR and VLR. Depending on the data modification required, one of three MAP procedures is initiated from the HLR towards the
IIF. These procedures are described in more detail in GSM 09.02 [6].
9
10
11
B.1.2.3.1 4.4.1.2.1 Insert Subscriber Data Procedure
Where data is required to be modified in the HLR, IIF and the serving VLR, the HLR initiates the
Insert Subscriber Data Procedure towards the IIF as shown in Figure 26.
MSC/
VLR
QUALDIR qualdir
IIF
HLR OMC
Modify Subscriber Data a
Insert Subscriber Data b c d
Insert Subscriber Data Ack e
Subscriber Data Modified f
12
ANSI-41 NETWORK
GSM NETWORK
Figure 26: Insert Subscriber Data Procedure
13
14
15
16
17
18
19
20 a. OMC initiates a request to modify subscriber data. b. The HLR modifies the subscriber data in the HLR and initiates the Insert Subscriber Data
Operation towards the IIF. c. The IIF modifies the subscriber data in the IIF and sends a QUALDIR to the serving MSC/VLR.
There may be some cases where the subscriber data change cannot be mapped to an associated ANSI136 41 subscriber profile modification. In this case, no QualDir operation shall be initiated. d. The serving MSC/VLR modifies the subscriber data and acknowledges the QUALDIR
Post Ballot Version 44

N.S0028
1
2
3
4
5
6 e. The IIF acknowledges the Insert Subscriber Data Request. f. The HLR acknowledges the request to modify subscriber data.
B.1.2.3.2 4.4.1.2.2 Delete Subscriber Data Procedure
If a basic or supplementary service is withdrawn, which requires a change to VLR data, the HLR initiates the Delete Subscriber Data Procedure towards the IIF as shown in Figure 27.
MSC/
VLR
QUALDIR qualdir
IIF
HLR OMC
Modify Subscriber Data a
Delete Subscriber Data b c d
Delete Subscriber Data Ack e
Subscriber Data Modified f
ANSI-41 NETWORK
GSM NETWORK
7
8
9
10
11
12
13
14
15
16
17
18 a. b. c. d. e. f.
Figure 27: Delete Subscriber Data Procedure
OMC initiates a request to modify subscriber data.
The HLR deletes the relevant subscriber data in the HLR and initiates the Delete Subscriber
Data Operation towards the IIF.
The IIF deletes the relevant subscriber data in the IIF and sends a QUALDIR to the serving
MSC/VLR. There may be some cases where the subscriber data deletion cannot be mapped to an associated ANSI136 41 subscriber profile modification. In this case, no QualDir operation shall be initiated.
The serving MSC/VLR deletes the relevant subscriber data and acknowledges the QUALDIR.
The IIF acknowledges the Delete Subscriber Data Request.
The HLR acknowledges the request to modify subscriber data.
Post Ballot Version 45

N.S0028
1
2
3
B.1.2.3.3 4.4.1.2.3 Cancel Location Procedure
If roaming modifications are required, which require the subscriber to be removed from the VLR data, the HLR initiates the Cancel Location Procedure towards the IIF as shown in Figure 28.
MSC/
VLR
REGISTRATION_
CANCELLATION
Registration_ cancellation
IIF
HLR OMC
Modify Subscriber Data a
Cancel Location d
Cancel Location Ack e
Subscriber Data Modified f b c
ANSI-41 NETWORK
GSM NETWORK
Figure 28: Cancel Location Procedure 4
8
9
10
11
12
5
6
7 a. b.
OMC initiates a request to modify subscriber data.
The HLR deletes the relevant subscriber data in the HLR and initiates the Cancel Location
Operation towards the IIF. c. The IIF deletes the temporary subscriber data in the IIF and sends a REGCANC to the serving MSC/VLR. d. The serving MSC/VLR deletes the relevant subscriber data and acknowledges the
REGCANC. e. The IIF acknowledges the Cancel Location Request.
13
14
The HLR acknowledges the request to modify subscriber data.
Post Ballot Version 46

N.S0028
1
2
3
4
5
Subscriber data management procedures are defined in ANSI 41-D, Section 6. These procedures impact the ANSI136 41 subscribers HLR, the IIF and the serving VLR when the subscriber is operating in GSM Foreign Mode. For these procedures, only modification to temporary subscriber data in the IIF is addressed.
6
7
8
9
B.1.2.4 4.4.2.1 Subscriber
The OMC may request that subscriber data relating to a particular subscriber is removed from the
HLR. In this case, subscriber data shall also be removed from the IIF and the serving MSC/VLR as shown in Figure 29.
Sub Data Delete
REGCANC b
Cancel Location
Canc el Loc ation Ack regc anc
Sub Data Delete Ack e f
10
11
12
13
14
15
16
17
18
Figure 29: Subscriber Deletion- GSM Foreign Mode a. OMC initiates a request to delete a subscriber b. The HLR deletes the subscriber data from the HLR and sends a REGCANC to the IIF. c. The IIF deletes the temporary subscriber data from the IIF and sends a Cancel Location to the serving VLR. d. The VLR acknowledges the cancel location e. The IIF acknowledges the REGCANC f. The HLR acknowledges the request to delete subscriber data.
Post Ballot Version 47

N.S0028
1
2
3
4
B.1.2.5 4.4.2.2 Modifying Subscriber Data
The OMC may request that subscriber data relating to a particular subscriber is modified (e.g., the authorization or de-authorization of a particular feature). In this case, subscriber data may also be required to be modified in the IIF and the serving MSC/VLR as shown in Figure 30.
Sub Data Change
QUALDIR b
Insert Sub Data
Insert Sub Data Ack qualdir e
Sub Dat a Change Ack f
5
6
7
8
9
10
11
12
13
14
15
16
17
18
Figure 30: Subscriber Data Modification a. OMC initiates a request to modify subscriber data b. The HLR modifies the subscriber data from the HLR and sends a QUALDIR to the IIF. c. The IIF modifies the temporary subscriber data and sends Insert Subscriber Data to the VLR if for example, a feature has been authorized or activated.
Note: The IIF sends a Delete Subscriber Data message if for example, a feature has been de-authorized or de-activated. There may be multiple ISD or DSD operations. There may be some cases where the subscriber data change cannot be mapped to an associated GSM subscriber profile modification. In this case, no ISD or DSD operation shall be initiated. d. The VLR acknowledges the request e. The IIF acknowledges the QUALDIR f. The HLR acknowledges the request to modify subscriber data
Post Ballot Version 48

N.S0028
5
6
7
8
9
10
11
1
2
3
4
This section depicts the interactions between network entities in various situations related to GSM and ANSI-41 foreign mode operation and automatic call delivery. These scenarios are not meant to be exhaustive.
Activation and deactivation of call delivery is not required to be supported.
Automatic call delivery is invoked when an incoming call attempt arrives for a subscriber who is roaming. Call delivery scenarios for both the case in which an ANSI136 41 subscriber is roaming in a
GSM network and the case in which a GSM subscriber is roaming in an ANSI-41 network are provided.
12 B.1.2.6 4.5.2.1
Incoming Call
From PSTN
Call Delivery to ANSI136 41 Subscriber Roaming in GSM Network
Serving System
MSC/
VLR
HLR
IIF
GSM
MSC/
VLR a
LOCREQ b
ROUTREQ c
Provide Roaming No.
d
PRN Ack e routreq f locreq g
Call setup h
13
14
15
16
17
18
19
20
21
22
23
Figure 31: Call Delivery to ANSI-41 Subscriber Roaming in a GSM Network a. A call origination and the dialed MS address digits (i.e., directory number) are received by the
Originating MSC from the PSTN destined to a subscriber to the ANSI-41 network. b. The Originating MSC sends a LOCREQ to the HLR associated with the called subscriber; this association is made through the dialed MS address digits. c. The HLR sends a ROUTREQ to the IIF emulating the VLR where the MS is registered. d. The IIF forwards a Provide Roaming Number message to the VLR/GSM MSC where the MS is registered. If necessary, mapping from MIN to IMSI is done by the IIF. e. The VLR/GSM MSC returns a Provide Roaming Number Ack message to the IIF that includes an
MSRN.
Post Ballot Version 49

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

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

N.S0028
1
2
3
4
5
6
7
8
18
19
20
21
22
23
9
10
11
12
13
14
15
16
17
24
25
26
27
B.1.2.9 4.5.2.4 Call Delivery to a GSM Subscriber Roaming in ANSI-41 Network –
Unsuccessful Case
In the following scenario, call delivery to a GSM subscriber roaming in an ANSI-41 network fails because the user is either ‘not reachable’ as determined by the IIF or does not answer a page sent by the serving system during the processing of the RouteRequest message, and call forwarding is not active for the subscriber.
Serving System
Incoming Call
From PSTN
GSM
MSC/
VLR
GSM
HLR
IIF MSC/
VLR a
Send Routing Info b
Provide Roaming No.
c
ROUTREQ d
routreq[ACCDEN] e
PRN Ret Error f
SRI Ret Error g
Figure 34: Unsuccessful Call Delivery to GSM Subscriber Roaming in an ANSI-41 Network a. A call origination and the dialed MS address digits (i.e., directory number) are received by the
Originating MSC from the PSTN destined to a subscriber to the GSM network. b. The Gateway GSM MSC sends a Send Routing Information message to the GSM HLR associated with the called subscriber; this association is made through the dialed MS address digits. c. The GSM HLR sends a Provide Roaming Number message to the IIF emulating the VLR where the MS is registered. If necessary, mapping from IMSI to MIN is done beforehand by the IIF. If the IIF determines that the called subscriber is not reachable, it returns an absent subscriber error as in step f. d. If the IIF determines that the subscriber is reachable, it forwards a ROUTREQ message to the
VLR/MSC where the MS is registered. e. The VLR/MSC pages the subscriber does not get a response and returns a routreq message with an AccessDeniedReason parameter set to NoPageResponse. f. The IIF returns a Provide Roaming Number Return Error message with the error code set to
Subscriber Absent to the subscriber’s GSM HLR. g. The GSM HLR sends a Send Routing Information Return Error message to the Gateway GSM
MSC with the Subscriber Absent error code, and the appropriate treatment (e.g. announcement) is provided to the incoming call by the Gateway GSM MSC.
Post Ballot Version 52

N.S0028
1
2
3
4
The scenarios in this section illustrate the call forwarding information flows applicable to a GSM native subscriber roaming in an ANSI-41 network (i.e., ANSI-41 foreign mode).
5
6
7
B.1.2.10 4.6.1.1 Call forwarding unconditional (CFU)
The following scenarios illustrate the call forwarding unconditional (CFU) information flows applicable to ANSI-41 foreign mode operation.
8
9
10
B.1.2.10.1 4.6.1.1.1 CFU
This scenario illustrates the CFU registration information flows applicable to ANSI-41 foreign mode operation.
GSM
Home System
ANSI-136
Serving System
Subscriber
IIF
HLR VMSC
2
MS
GSM ANSI-41 feature code digits
11
12
13
REG_SS reg_ss
ISD isd
[TCAP End]
FEATREQ [digits] featreq [success]
QUALDIR qualdir
Figure 35: CFU registration feature confirmation g h f e i j c d a b k
Post Ballot Version 53

N.S0028
1
2
3
4
5
6
7
8
24
25
26
27
28
29
19
20
21
22
23
30
31
32
33
9
10
11
12
13
14
15
16
17
18 a. The ANSI-41 serving system receives dialed digits from the subscriber’s mobile station (MS). The serving system detects a “*” character as the first dialed digit. This indicates that the dialed digits are a feature code string.
1 b. The serving system sends a FEATREQ message to the IIF, including the digits received from the subscriber. c. The IIF parses the received digit string. In this case, the subscriber has requested to register a call forwarding number. The IIF sends a REG_SS message to the GSM HLR.
2 d. The HLR processes the request and returns a reg_ss message to the IIF, indicating operation success. e. The IIF sends a featreq message to the serving system, indicating a successful feature control request. f. The serving system sends a feature confirmation signal to the subscriber. g. The GSM HLR initiates a service profile update by sending an Insert Subscriber Data (ISD) message to the IIF, containing the new or modified profile data (e.g., the new call forward number). h. The IIF responds with an ISD acknowledgement message. Note that, if the subscriber’s profile is too large for a single ISD message, then multiple ISD exchanges may be executed between the
GSM HLR and the IIF. i. The GSM HLR completes the operation by closing the TCAP transaction. j. The IIF converts the revised GSM profile data into ANSI-41 equivalents. If this results in a change in the value of the subscriber’s ANSI-41 profile, the IIF includes the revised ANSI-41 profile data in a QUALDIR message it sends to the serving system. k. The serving system stores the new profile information and responds with a qualdir message.
34
35
36
37
B.1.2.10.2 4.6.1.1.2 CFU (erasure)
This scenario illustrates the CFU deregistration information flows applicable to ANSI-41 foreign mode 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).
Post Ballot Version 54

N.S0028
GSM
Home System
HLR
GSM
IIF
ANSI-41
ANSI-136
Serving System
VMSC
2
Subscriber
MS
1
2
16
17
18
19
20
21
22
23
24
25
10
11
12
13
14
15
3
4
5
6
7
8
9 feature code digits a
FEATREQ [digits] b
ERASE_SS c erase_ss d featreq [success] e feature confirmation f
ISD g isd h
[TCAP End] i
QUALDIR j qualdir k
Figure 36: CFU deregistration (erasure) a. The ANSI-41 serving system receives dialed digits from the subscriber’s mobile station (MS). The serving system detects a “*” character as the first dialed digit. This indicates that the dialed digits are a feature code string. b. The serving system sends a FEATREQ message to the IIF, including the digits received from the subscriber. c. The IIF parses the received digit string. In this case, the subscriber has requested to erase a call forwarding number. The IIF sends an ERASE_SS message to the GSM HLR. d. The HLR processes the request and returns an erase_ss message to the IIF, indicating operation success. e. The IIF sends a featreq message to the serving system, indicating a successful feature control request. f. The serving system sends a feature confirmation signal to the subscriber. g. The GSM HLR initiates a service profile update by sending an Insert Subscriber Data (ISD) message to the IIF, containing the new or modified profile data (e.g., the new ss-status value).
Post Ballot Version 55

N.S0028
8
9
10
5
6
7
11
12
1
2
3
4 h. The IIF responds with an ISD acknowledgement message. Note that, if the subscriber’s profile is too large for a single ISD message, then multiple ISD exchanges may be executed between the
GSM HLR and the IIF. i. The GSM HLR completes the operation by closing the TCAP transaction. j. The IIF converts the revised GSM profile data into ANSI-41 equivalents. If this results in a change in the value of the subscriber’s ANSI-41 profile, the IIF includes the revised ANSI-41 profile data in a QUALDIR message it sends to the serving system. k. The serving system stores the new profile information and responds with a qualdir message.
Post Ballot Version 56

N.S0028
1
2
3
4
B.1.2.10.3 4.6.1.1.3 CFU
This scenario illustrates the CFU activation information flows applicable to ANSI-41 foreign mode operation.
GSM
Home System
ANSI-136
Serving System
Subscriber
IIF
HLR VMSC
2
MS
GSM ANSI-41
5
6
12
13
14
15
16
17
7
8
9
10
11
18
19
20
21
22
23
24 feature code digits a
FEATREQ [digits] b
ACT_SS c act_ss d featreq [success] e feature confirmation f
ISD g isd h
[TCAP End] i
QUALDIR j qualdir k
Figure 37: CFU activation a. The ANSI-41 serving system receives dialed digits from the subscriber’s mobile station (MS). The serving system detects a “*” character as the first dialed digit. This indicates that the dialed digits are a feature code string. b. The serving system sends a FEATREQ message to the IIF, including the digits received from the subscriber. c. The IIF parses the received digit string. In this case, the subscriber has requested to activate call forwarding. The IIF sends an ACT_SS message to the GSM HLR. d. The HLR processes the request and returns an act_ss message to the IIF, indicating operation success. e. The IIF sends a featreq message to the serving system, indicating a successful feature control request. f. The serving system sends a feature confirmation signal to the subscriber.
Post Ballot Version 57

N.S0028
8
9
10
5
6
7
1
2
3
4
11
12
13
14
15
16 g. The GSM HLR initiates a service profile update by sending an Insert Subscriber Data (ISD) message to the IIF, containing the new or modified profile data (e.g., the new ss-status value). h. The IIF responds with an ISD acknowledgement message. Note that, if the subscriber’s profile is too large for a single ISD message, then multiple ISD exchanges may be executed between the
GSM HLR and the IIF. i. The GSM HLR completes the operation by closing the TCAP transaction. j. The IIF converts the revised GSM profile data into ANSI-41 equivalents. If this results in a change in the value of the subscriber’s ANSI-41 profile, the IIF includes the revised ANSI-41 profile data in a QUALDIR message it sends to the serving system. k. The serving system stores the new profile information and responds with a qualdir message.
Post Ballot Version 58

N.S0028
1
2
3
B.1.2.10.4 4.6.1.1.4 CFU
This scenario illustrates the CFU deactivation information flows applicable to ANSI-41 foreign mode operation.
GSM
Home System
ANSI-136
Serving System
Subscriber
IIF
HLR VMSC
2
MS
GSM ANSI-41
4
5
10
11
12
13
14
15
6
7
8
9
16
17
18
19
20
21
22
23 feature code digits a
FEATREQ [digits] b
DEACT_SS c deact_ss d featreq [success] e feature confirmation f
ISD g isd h
[TCAP End] i
QUALDIR j qualdir k
Figure 38: CFU deactivation a. The ANSI-41 serving system receives dialed digits from the subscriber’s mobile station (MS). The serving system detects a “*” character as the first dialed digit. This indicates that the dialed digits are a feature code string. b. The serving system sends a FEATREQ message to the IIF, including the digits received from the subscriber. c. The IIF parses the received digit string. In this case, the subscriber has requested to deactivate call forwarding. The IIF sends a DEACT_SS message to the GSM HLR. d. The HLR processes the request and returns a deact_ss message to the IIF, indicating operation success. e. The IIF sends a featreq message to the serving system, indicating a successful feature control request. f. The serving system sends a feature confirmation signal to the subscriber.
Post Ballot Version 59

N.S0028
8
9
10
5
6
7
1
2
3
4
11
12
13
14
15
16
17
18 g. The GSM HLR initiates a service profile update by sending an Insert Subscriber Data (ISD) message to the IIF, containing the new or modified profile data (e.g., the new ss-status value). h. The IIF responds with an ISD acknowledgement message. Note that, if the subscriber’s profile is too large for a single ISD message, then multiple ISD exchanges may be executed between the
GSM HLR and the IIF. i. The GSM HLR completes the operation by closing the TCAP transaction. j. The IIF converts the revised GSM profile data into ANSI-41 equivalents. If this results in a change in the value of the subscriber’s ANSI-41 profile, the IIF includes the revised ANSI-41 profile data in a QUALDIR message it sends to the serving system. k. The serving system stores the new profile information and responds with a qualdir message.
B.1.2.10.5 4.6.1.1.5 CFU
While in ANSI-41 foreign mode, the GSM subscriber does not have the capability to interrogate the
CFU service. An attempt to perform such an operation shall result in an error response
19
20
21
B.1.2.10.6 4.6.1.1.6 CFU
This scenario illustrates the CFU invocation information flows applicable to ANSI-41 foreign mode operation.
GSM
Gateway
GSM
Home System
ANSI-136
Serving System
IIF
GMSC HLR VMSC
2
GSM ANSI-41
22
23
24
25
26
27
28
29
30
31
32 incoming call a
SRI b sri [CFU#] c forward call to CFU # d
Figure 39: CFU invocation a. The GSM gateway MSC (GMSC) receives an incoming call for the subscriber. b. The GMSC sends a SRI message to the HLR. c. The GSM HLR determines that the subscriber has CFU registered and active; therefore, the HLR responds with the subscriber’s CFU forward-to number in the sri message. d. The GMSC forwards the call to the CFU forward-to number.
Post Ballot Version 60

N.S0028
1
2
3
4
B.1.2.11 4.6.1.2 Call forwarding busy (CFB)
The following scenarios illustrate the call forwarding busy (CFB) information flows applicable to ANSI-
41 foreign mode operation.
5
6
7
B.1.2.11.1 4.6.1.2.1 CFB
See 4.6.1.1.1 for the CFB registration information flows applicable to ANSI-41 foreign mode operation, since they are the same as those for CFU.
14
15
16
17
18
19
8
9
10
11
12
13
B.1.2.11.2 4.6.1.2.2 CFB (erasure)
See 4.6.1.1.2 for the CFB deregistration information flows applicable to ANSI-41 foreign mode operation, since they are the same as those for CFU.
B.1.2.11.3 4.6.1.2.3 CFB
See 4.6.1.1.3 for the CFB activation information flows applicable to ANSI-41 foreign mode operation, since they are the same as those for CFU.
B.1.2.11.4 4.6.1.2.4 CFB
See 4.6.1.1.4 for the CFB deactivation information flows applicable to ANSI-41 foreign mode operation, since they are the same as those for CFU.
B.1.2.11.5 4.6.1.2.5 CFB
While in ANSI-41 foreign mode, the GSM subscriber does not have the capability to interrogate the
CFB service. An attempt to perform such an operation shall result in an error response.
20
21
22
B.1.2.11.6 4.6.1.2.6 CFB
The following scenarios illustrate the CFB invocation information flows applicable to ANSI-41 foreign mode operation.
23
24
25
26
B.1.2.11.6.1 4.6.1.2.6.1 CFB invocation (Scenario 1a, “CFB#=MSRN method”)
In this scenario, the busy condition is detected by the ANSI-41 serving system when the
RoutingRequest Invoke message is received, and the IIF returns the CFB forward-to number (i.e., as the MSRN) to the GSM HLR in the ProvideRoamingNumber Return Result message.
Post Ballot Version 61

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

N.S0028
1
2
3
4
B.1.2.11.6.2 4.6.1.2.6.2 CFB invocation (Scenario 1b, “AbsentSubscriber method”)
In this scenario, the busy condition is detected by the ANSI-41 serving system when the
RoutingRequest Invoke message is received, and the IIF returns an AbsentSubscriber error code to the GSM HLR in the ProvideRoamingNumber Return Error message.
GSM
Gateway
GSM
Home System
ANSI-136
Serving System
IIF
GMSC HLR VMSC
2
GSM ANSI-41
5
6
14
15
16
17
18
19
20
7
8
9
10
11
12
13 incoming call a
SRI b
PRN c
ROUTREQ d
Subscriber is detected busy routreq [Busy] e f prn_RE
[AbsentSubscriber] g sri [CFNRc #] h forward call to CFNRc# i
Figure 41: CFB invocation (Scenario 1b, “AbsentSubscriber method”) a-f. Same as Section 4.6.1.2.6.1, steps a-f. g. The IIF determines that CFB is active for the subscriber. The IIF sends the AbsentSubscriber error code in a ProvideRoamingNumber Return Error message.
NOTE: This directs the GSM HLR to initiate CFNRc processing if this feature is active in the subscriber’s profile. While this handling complies with the GSM MAP Version 2 standard and avoids the potential problems of other approaches, it requires that the CFNRc feature be active and does not allow different handling of busy versus not reachable conditions. h. The GSM HLR returns an sri message, directing the GMSC to forward the call to the CFNRc forward-to number.
21
22
23 i. The GMSC forwards the call to the CFB forward-to number.
Post Ballot Version 63

N.S0028
1
2
3
4
5
B.1.2.11.6.3 4.6.1.2.6.3 CFB invocation (Scenario 2, without OR)
In this scenario, the busy condition is detected by the ANSI-41 serving system after the
RoutingRequest Invoke message is received and while attempting to complete the call to the TLDN, and optimal routing is not invoked.
GSM
Gateway
GSM
Home System
ANSI-136
Serving System
IIF
GMSC HLR VMSC
2
GSM ANSI-41
6
7
8
9
10
11
12
13
14
15
16
17 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
REDREQ [Busy, BillingID1] i j redreq [reject] k
TRANUMREQ [Busy] l tranumreq [CFB #] m forward call to CFB # n
Figure 42: CFB invocation (Scenario 2, without OR) a. The GSM GMSC receives an incoming call for the subscriber. b. The GMSC sends a SRI message to the HLR. c. The HLR sends a PRN message to the current GSM serving system; i.e., the IIF. d. The IIF sends a ROUTREQ message to the ANSI-41 serving system. Note that this message shall contain the MSCID and PC_SSN parameters corresponding to the IIF. The serving system may use this information to route any subsequent REDREQ message, as in step-j.
Post Ballot Version 64

N.S0028
32
33
34
35
36
37
17
18
19
20
21
11
12
13
14
15
16
8
9
10
5
6
7
1
2
3
4
22
23
24
25
26
27
28
29
30
31 e. The serving system determines that the subscriber is available; therefore, it returns a routreq message, containing a routing number (called a temporary local directory number, or TLDN, in
ANSI-41) to the IIF. f. The IIF responds to the GSM HLR with a prn message including the MSRN that it derives from the TLDN; i.e., if the received TLDN is not in international format, then the IIF converts the TLDN into international format for use as the MSRN by adding country code digit(s) associated with the country of the serving system. g. The GSM HLR returns an sri message containing the MSRN to the GMSC. h. The GMSC establishes a call to the MSRN. i. The serving system determines that the subscriber is busy. Note: If call waiting (CW) is active, the serving system would normally invoke CW under these circumstances. j. The serving system sends a REDREQ message to the IIF (e.g., using the routing information provided in step-d), indicating that call redirection is requested due to a subscriber busy condition. k. Since the IIF is not able to redirect the call (i.e., optimal routing is not possible), it rejects the redirection request. l. If the serving system is able to redirect the call, it sends a TRANUMREQ message to the IIF, requesting the CFB forward-to number. Note that not all ANSI-41 systems have implemented this redirection capability. Without this capability, the call shall fail, possibly with a tone or announcement to the calling party. m. The IIF determines that CFB is active for the subscriber. Therefore, the IIF responds with a tranumreq message including the subscriber’s CFB forward-to number. n. The serving system forwards the call to the CFB forward-to number.
B.1.2.11.6.4 4.6.1.2.6.4 CFB invocation (Scenario 2, with OR)
In this scenario, the busy condition is detected by the ANSI-41 serving system after the
RoutingRequest Invoke message is received and while attempting to complete the call to the TLDN, and optimal routing is invoked.
This scenario is covered in Section 4.7.1.
Post Ballot Version 65

N.S0028
1
2
3
B.1.2.12 4.6.1.3 Call forwarding no reply (CFNRy)
The following scenarios illustrate the call forwarding no reply (CFNRy) information flows applicable to
ANSI-41 foreign mode operation.
4 B.1.2.12.1 4.6.1.3.1 CFNRy
10
11
12
7
8
9
13
14
15
16
17
18
19
5
6
See 4.6.1.1.1 for the CFNRy registration information flows applicable to ANSI-41 foreign mode operation, since they are the same as those for CFU.
3
B.1.2.12.2 4.6.1.3.2 CFNRy deregistration (erasure)
See 4.6.1.1.2 for the CFNRy deregistration information flows applicable to ANSI-41 foreign mode operation, since they are the same as those for CFU.
3
B.1.2.12.3 4.6.1.3.3 CFNRy
See 4.6.1.1.3 for the CFNRy activation information flows applicable to ANSI-41 foreign mode operation, since they are the same as those for CFU.
3
B.1.2.12.4 4.6.1.3.4 CFNRy
See 4.6.1.1.4 for the CFNRy deactivation information flows applicable to ANSI-41 foreign mode operation, since they are the same as those for CFU.
3
B.1.2.12.5 4.6.1.3.5 CFNRy
The following scenarios illustrate the CFNRy invocation information flows applicable to ANSI-41 foreign mode operation.
3
The ANSI-136 serving system may not directly support CFNRy registration or activation, but only support registration or activation of call forwarding no answer (CFNA). In this case, CFNA registration or activation shall result in the registration or activation of both CFNRy and call forwarding not reachable
(CFNRc).
Post Ballot Version 66

N.S0028
1
2
3
B.1.2.12.5.1 4.6.1.3.5.1 CFNRy invocation (Scenario 1, without OR)
In this scenario, the no reply condition is detected by the ANSI-41 serving system while attempting to complete the call to the TLDN, and optimal routing is not invoked.
GSM
Gateway
GSM
Home System
ANSI-136
Serving System
IIF
GMSC HLR VMSC
2
GSM ANSI-41
4
5
6
7
8 incoming call a
SRI b
PRN c
ROUTREQ [BillingID1] d routreq [TLDN] e prn [MSRN] f sri [MSRN] g setup call to MSRN h
Subscriber does not answer
REDREQ [No answer, BillingID1] i j redreq [reject]
TRANUMREQ [No Answer] l tranumreq [CFNRy #] k m forward call to CFNRy # n
Figure 43: CFNRy invocation (Scenario 1, without OR) a-h. Same as Section 4.6.1.2.6.3, steps a-h.
9
10
11
12
13
14
15
16
17 i. The serving system determines that the subscriber does not answer the alert. j. The serving system sends a REDREQ message to the IIF (e.g., using the routing information provided in step-d), indicating that call redirection is requested due to a subscriber no answer condition. k. Since the IIF is not able to redirect the call (i.e., optimal routing is not possible), it rejects the redirection request
Post Ballot Version 67

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

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

N.S0028
1
2
3
B.1.2.13.5.1 4.6.1.4.5.1 CFNRc invocation (Scenario 1)
In this scenario, the not reachable condition is detected either by the IIF or by the ANSI-41 serving system when the RoutingRequest Invoke message is received.
GSM
Gateway
GSM
Home
ANSI-136
Serving
GMSC HLR
GSM
IIF
ANSI-41
VMSC
2
4
5
24
25
26
27
28
18
19
20
21
22
23
12
13
14
15
16
17
6
7
8
9
10
11 incoming call a
SRI b
PRN c
ROUTREQ d
No response to paging routreq [No response] e f prn_RE
[AbsentSubscriber] g sri [CFNRc #] h forward call to CFNRc# i
Figure 44: CFNRc invocation (Scenario 1) a. The GSM GMSC receives an incoming call for the subscriber. b. The GMSC sends a SRI message to the HLR. c. The HLR sends a PRN message to the current GSM serving system (i.e., the IIF). d. If the IIF determines that the called subscriber is not reachable, it returns an absent subscriber error, otherwise, the IIF sends a ROUTREQ message to the ANSI-41 serving system. e. The serving system determines that the subscriber is no reachable (e.g., does not respond to paging). f. Therefore, the serving system returns a routreq message, containing the AccessDeniedReason parameter set to the value No Page Response. g. The IIF determines that CFNRc is active for the subscriber. The IIF sends the AbsentSubscriber error code in a ProvideRoamingNumber Return Error message. h. The GSM HLR returns a sri message, directing the GMSC to forward the call to the CFNRc forward-to number. i. The GMSC forwards the call to the CFB forward-to number.
Post Ballot Version 70

N.S0028
1
2
3
4
B.1.2.13.5.2 4.6.1.4.5.2 CFNRc invocation (Scenario 2, without OR)
In this scenario, the not reachable condition is detected by the ANSI-41 serving system after the
RoutingRequest Invoke message is received and while attempting to complete the call to the TLDN, and optimal routing is not invoked.
GSM
Gateway
GSM
Home System
ANSI-136
Serving System
IIF
GMSC HLR VMSC
2
GSM ANSI-41
5
6
7
13
14
15
16
17
18
8
9
10
11
12 incoming call a
SRI b
PRN c
ROUTREQ [BillingID1] 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
Figure 45: CFNRc invocation (Scenario 2, without OR) a-h. Same as Section 4.6.1.2.6.3, steps a-h. i. The serving system determines that the mobile station does not respond to paging. j. The serving system sends a REDREQ message to the IIF (e.g., using the routing information provided in step d), indicating that call redirection is requested due to a subscriber no page response condition. k. Since the IIF is not able to redirect the call (i.e., optimal routing is not possible), it rejects the redirection request.
Post Ballot Version 71

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

N.S0028
1
2
3
B.1.3
The scenarios in this section illustrate the call forwarding information flows applicable to an ANSI136
41 native subscriber roaming in a GSM network; i.e., GSM foreign mode.
4
5
6
B.1.3.1 4.6.2.1 Call forwarding unconditional (CFU)
The following scenarios illustrate the call forwarding unconditional (CFU) information flows applicable to GSM foreign mode operation.
7
8
9
B.1.3.1.1 4.6.2.1.1 CFU
This scenario illustrates the CFU registration information flows applicable to GSM foreign mode operation.
ANSI-41
Home System
GSM
Serving System
Subscriber
IIF
HLR VMSC
2
MS
ANSI-41 GSM
10
11
12
19
20
21
22
23
24
25
26
13
14
15
16
17
18
27
28
29
30
A_REG_SS a
REG_SS b
FEATREQ [digits] c featreq [success] d reg_ss e a_reg_ss f
Figure 46: CFU registration a. The GSM serving system receives an A_REG_SS message from the subscriber’s mobile station
(MS), indicating that the subscriber wishes to change his CFU forward-to number. b. The serving system sends a REG_SS message to the IIF, constructed based on the information received in the A_REG_SS message. c. The IIF translates the information received in the REG_SS message into a corresponding digit string (e.g., based on internal tables) and sends this string to the ANSI-41 HLR in a FEATREQ message. d. The HLR processes the request and returns a featreq message to the IIF, indicating operation success. e. The IIF sends a reg_ss message to the serving system, indicating a successful feature control request. f. The serving system sends a registration response message to the subscriber.
Post Ballot Version 73

N.S0028
1
2
3
4
5
Note: The process of registering the call forward number may also result in activation of the service.
This is based on HLR (i.e., carrier) determined policy.
B.1.3.1.2 4.6.2.1.2 CFU (erasure)
This scenario illustrates the CFU deregistration information flows applicable to GSM foreign mode operation.
ANSI-41
Home System
GSM
Serving System
Subscriber
IIF
HLR VMSC
2
MS
ANSI-41 GSM
6
7
19
20
21
22
23
24
25
26
27
13
14
15
16
17
18
8
9
10
11
12
A_ERASE_SS a
ERASE_SS b
FEATREQ [digits] c featreq [success] d erase_ss e a_erase_ss f
Figure 47: CFU deregistration (erasure) a. The GSM serving system receives an A_ERASE_SS message from the subscriber’s mobile station (MS), indicating that the subscriber wishes to deregister the CFU service. b. The serving system sends an ERASE_SS message to the IIF, constructed based on the information received in the A_ERASE_SS message. c. The IIF translates the information received in the ERASE_SS message into a corresponding digit string (e.g., based on internal tables) and sends this string to the ANSI-41 HLR in a FEATREQ message. d. The HLR processes the request and returns a featreq message to the IIF, indicating operation success. e. The IIF sends an erase_ss message to the serving system, indicating a successful feature control request. f. The serving system sends a deregistration response message to the subscriber.
Note: The process of deregistering the call forward service also results in deactivation of the service.
Post Ballot Version 74

N.S0028
1
2
3
B.1.3.1.3 4.6.2.1.3 CFU
This scenario illustrates the CFU activation information flows applicable to GSM foreign mode operation.
ANSI-41
Home System
GSM
Serving System
Subscriber
IIF
HLR VMSC
2
MS
ANSI-41 GSM
23
24
25
26
27
4
5
10
11
12
13
14
15
6
7
8
9
16
17
18
19
20
21
22
A_ACT_SS a
ACT_SS b
FEATREQ [digits] c featreq [success] d act_ss e a_act_ss f
Figure 48: CFU activation a. The GSM serving system receives an A_ACT_SS message from the subscriber’s mobile station
(MS), indicating that the subscriber wishes to activate the CFU service. b. The serving system sends an ACT_SS message to the IIF, constructed based on the information received in the A_ACT_SS message. c. The IIF translates the information received in the ACT_SS message into a corresponding digit string (e.g., based on internal tables) and sends this string to the ANSI-41 HLR in a FEATREQ message. d. The HLR processes the request and returns a featreq message to the IIF, indicating operation success. e. The IIF sends an act_ss message to the serving system, indicating a successful feature control request. f. The serving system sends an activation response message to the subscriber.
B.1.3.1.4 4.6.2.1.4 CFU
This scenario illustrates the CFU deactivation information flows applicable to GSM foreign mode operation.
Post Ballot Version 75

N.S0028
ANSI-41
Home System
HLR
ANSI-41
IIF
GSM
GSM
Serving System
VMSC
2
Subscriber
MS
1
2
3
9
10
11
12
13
14
4
5
6
7
8
15
16
17
18
19
20
21
A_DEACT_SS a
DEACT_SS b
FEATREQ [digits] c featreq [success] d deact_ss e a_deact_ss f
Figure 49: CFU deactivation a. The GSM serving system receives an A_DEACT_SS message from the subscriber’s mobile station (MS), indicating that the subscriber wishes to deactivate the CFU service. b. The serving system sends a DEACT_SS message to the IIF, constructed based on the information received in the A_DEACT_SS message. c. The IIF translates the information received in the DEACT_SS message into a corresponding digit string (e.g., based on internal tables) and sends this string to the ANSI-41 HLR in a FEATREQ message. d. The HLR processes the request and returns a featreq message to the IIF, indicating operation success. e. The IIF sends a deact_ss message to the serving system, indicating a successful feature control request. f. The serving system sends a deactivation response message to the subscriber.
Post Ballot Version 76

N.S0028
1
2
3
4
B.1.3.1.5 4.6.2.1.5 CFU
This scenario illustrates the CFU invocation information flows applicable to GSM foreign mode operation.
ANSI-41
Originating MSC
ANSI-41
Home System
GSM
Serving System
IIF
GMSC HLR VMSC
2
ANSI-41 GSM
5
6
10
11
12
7
8
9
13
14
15 incoming call a
LOCREQ b locreq [CFU#] c forward call to CFU # d
Figure 50: CFU invocation a. The ANSI-41 originating MSC (OMSC) receives an incoming call for the subscriber. b. The OMSC sends a LOCREQ message to the HLR. c. The HLR determines that the subscriber has CFU registered and active; therefore, the HLR responds with the subscriber’s CFU forward-to number in the locreq message. d. The OMSC forwards the call to the CFU forward-to number.
Post Ballot Version 77

N.S0028
1
2
3
4
5
6
7
8
B.1.3.2 4.6.2.2 Call forwarding busy (CFB)
The following scenarios illustrate the call forwarding busy (CFB) information flows applicable to GSM foreign mode operation.
Since the ANSI-41 HLR does not provide the CFB forward-to number to the serving system until the feature is actually invoked—versus the GSM method, whereby the HLR provides the forward-to number(s) to the serving system as part of the subscriber’s profile information at registration time— the IIF shall use the ANSI-41 TransferToNumberRequest operation to obtain the CFB forward-to number. This is illustrated in Figure 51.
ANSI-41
Home System
GSM
Serving System
Subscriber
IIF
HLR VMSC
2
MS
ANSI-41 GSM a
Normal registration process
9
10
20
21
22
23
24
25
26
27
28
29
11
12
13
14
15
16
17
18
19
TRANUMREQ b tranumreq c
TRANUMREQ d tranumreq e
ISD f isd g
[TCAP End] h
Figure 51: Obtaining forward-to numbers a. The subscriber registers on a GSM serving system using the normal registration signaling process. b. If the subscriber’s ANSI-41 profile indicates that CFB is authorized and active, and the IIF determines that it does may not have the current CFB forward-to number, then the IIF sends a
TRANUMREQ message to the HLR requesting the CFB forward-to number. c. The HLR responds with the CFB forward-to number in the tranumreq message. d. If the subscriber’s ANSI-41 profile indicates that CFNA is authorized and active, and the IIF determines that it does may not have the current CFNA forward-to number, then the IIF sends a
TRANUMREQ message to the HLR requesting the CFNA forward-to number. e. The HLR responds with the CFNA forward-to number in the tranumreq message. f-h. If the CFB forward-to number or CFNA forward-to number, or both numbers do not correspond with the numbers previously provided to the GSM serving system, then the IIF sends the modified information to the GSM serving system using the InsertSubscriberData operation. The CFNA forward-to number shall be populated as both the CFNRc and CFNRy forward-to numbers.
Post Ballot Version 78

N.S0028
1
2
3
B.1.3.2.1 4.6.2.2.1 CFB
This scenario illustrates the CFB registration information flows applicable to GSM foreign mode operation.
ANSI-41
Home System
GSM
Serving System
Subscriber
IIF
HLR VMSC
2
MS
ANSI-41 GSM
4
5
10
11
12
13
14
15
6
7
8
9
16
17
18
19
20
21
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
Figure 52: CFB registration a. The GSM serving system receives an A_REG_SS message from the subscriber’s mobile station
(MS), indicating that the subscriber wishes to change his call forwarding number. b. The serving system sends a REG_SS message to the IIF, constructed based on the information received in the A_REG_SS message. c. The IIF translates the information received in the REG_SS message into a corresponding digit string (e.g., based on internal tables) and sends this string to the ANSI-41 HLR in a FEATREQ message. d. The HLR processes the request and returns a featreq message to the IIF, indicating operation success. e. The IIF sends a reg_ss message to the serving system, indicating a successful feature control request.
Post Ballot Version 79

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

N.S0028
1
2
3
B.1.3.2.2 4.6.2.2.2 CFB (erasure)
This scenario illustrates the CFB deregistration information flows applicable to GSM foreign mode operation.
ANSI-41
Home System
GSM
Serving System
Subscriber
IIF
HLR VMSC
2
MS
ANSI-41 GSM
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
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
Figure 53: CFB deregistration (erasure) a. The GSM serving system receives an A_ERASE_SS message from the subscriber’s mobile station (MS), indicating that the subscriber wishes to deregister the call forward service. b. The serving system sends an ERASE_SS message to the IIF, constructed based on the information received in the A_ERASE_SS message. c. The IIF translates the information received in the ERASE_SS message into a corresponding digit string (e.g., based on internal tables) and sends this string to the ANSI-41 HLR in a FEATREQ message. d. The HLR processes the request and returns a featreq message to the IIF, indicating operation success. e. The IIF sends an erase_ss message to the serving system, indicating a successful feature control request. f. The serving system sends a deregistration response message to the subscriber.
Post Ballot Version 81

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

N.S0028
11
12
13
14
15
16
17
18
19
8
9
10
5
6
7
1
2
3
4 c. The IIF translates the information received in the ACT_SS message into a corresponding digit string (e.g., based on internal tables) and sends this string to the ANSI-41 HLR in a FEATREQ message. d. The HLR processes the request and returns a featreq message to the IIF, indicating operation success. e. The IIF sends an act_ss message to the serving system, indicating a successful feature control request. f. The serving system sends an activation response message to the subscriber. g-h. If the subscriber’s ANSI-41 profile changes as a result of the operation (e.g., the service was previously authorized but not active), the HLR sends a QUALDIR message to the IIF, containing the new profile information. i-k. If the subscriber’s GSM profile has changed as a result of these operations, then the IIF sends the modified profile information to the serving system via an InsertSubscriberData message exchange.
20
21
22
B.1.3.2.4 4.6.2.2.4 CFB
This scenario illustrates the CFB deactivation information flows applicable to GSM foreign mode operation.
ANSI-41
Home System
GSM
Serving System
Subscriber
IIF
HLR VMSC
2
MS
ANSI-41 GSM
A_DEACT_SS
23
24
FEATREQ [digits] featreq [success]
QUALDIR qualdir
DEACT_SS deact_ss
ISD isd
[TCAP End]
Figure 55: CFB deactivation a_deact_ss g h f e i j c d a b k
Post Ballot Version 83

N.S0028
27
28
29
30
1
18
19
20
21
22
23
24
25
26
12
13
14
15
16
17
6
7
8
9
10
11
2
3
4
5 a. The GSM serving system receives an A_DEACT_SS message from the subscriber’s mobile station (MS), indicating that the subscriber wishes to deactivate the call forward service. b. The serving system sends a DEACT_SS message to the IIF, constructed based on the information received in the A_DEACT_SS message. c. The IIF translates the information received in the DEACT_SS message into a corresponding digit string (e.g., based on internal tables) and sends this string to the ANSI-41 HLR in a FEATREQ message. d. The HLR processes the request and returns a featreq message to the IIF, indicating operation success. e. The IIF sends a deact_ss message to the serving system, indicating a successful feature control request. f. The serving system sends a deactivation response message to the subscriber. g-h. If the subscriber’s ANSI-41 profile changes as a result of the operation (e.g., the service was previously authorized and active), the HLR sends a QUALDIR message to the IIF, containing the new profile information. i-k. If the subscriber’s GSM profile has changed as a result of these operations, then the IIF sends the modified profile information to the serving system via an InsertSubscriberData message exchange.
B.1.3.2.5 4.6.2.2.5 CFB
The following scenarios illustrate the CFB invocation information flows applicable to GSM foreign mode operation.
Post Ballot Version 84

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

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

N.S0028
ANSI-41
Originating MSC
OMSC
ANSI-41
Home System
HLR
ANSI-41
IIF
GSM
GSM
Serving System
VMSC
2
9
10
11
12
1
2
3
4
5
6
7
8
13 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
Figure 57: CFNA invocation (Scenario 1, without OR) a-h. Same as Section 4.6.2.2.5.1, steps a-h. i-j. The serving system determines that the subscriber does not answer the alert and forwards the call to the CFNRy forward-to number.
B.1.3.3.5.2 4.6.2.3.5.2 CFNA invocation (Scenario 1, with OR)
In this scenario, the no reply condition is detected by the GSM serving system while attempting to complete the call to the TLDN, and optimal routing is invoked.
This scenario is addressed in Section 4.7.2.
Post Ballot Version 87

N.S0028
1
10
11
12
2
3
4
5
6
7
8
9
13
14
15
16
17
18
19
20
21
The following scenarios cover the interoperability to support Optimal Routing for Late Call
Forwarding. The signaling is based on ANSI-41 Rev. D [1] and GSM 9.02 [6].
From GSM 02.79 [8] and GSM 03.79 [9], Late Call Forwarding is Call Forwarding performed after the call has been extended to the Visited PLMN (VPLMN) of the forwarding subscriber (i.e., Conditional
Call Forwarding on Busy, Conditional Call Forwarding on No Reply, and Conditional Call Forwarding on Not Reachable detected in the VPLMN of the forwarding subscriber). Late Call Forwarding may be invoked in the Interrogating PLMN (IPLMN) or in the VPLMN of the forwarding subscriber.
Assumptions:
1) The Subscriber has forwarding enabled.
2) Optimal Routing is enabled.
The following scenarios address the case where the forwarding attempt is done by the IPLMN.
B.1.3.4 4.7.1.1 ANSI-41 Foreign Mode - Success condition
Scenario: GSM Subscriber A makes a call origination attempt at GMSC-A to a GSM Subscriber B who is roaming and registered in an ANSI-41 network at MSC-B. Subscriber B has call forwarding set to an address at MSC-C. n o j i h f
GSM
(GMSC-A) a b
Call Origination
Send Routing Info c d
[ORphase,
GMSC#,CR#,
ORinterrog(Opt.)]
GSM
(B’s HLR)
Provide Roaming Number
[GMSC#,CR#,
ORinterrog(Opt.)]
IIF e
ANSI-41
(MSC-B/VLR)
ROUTEREQ [billing ID]
Routereq [TLDN]
Provide Roaming Number Ack[MSRN] g
Send Routing InfoAck [MSRN, FIR] k
Establish Connection Attempt
REDREQ [REDREASON, billing ID]
Resume Call Handling [CR#,reason, forwarding#]
Send Routing Info [forwarding reason]
Send Routing InfoAck [forwarding #] l m
Resume Call HandlingAck redreq
Connection Release p
Call Forward Setup
(MSC-C)
Figure 58: Optimal Routing with Late Call Forwarding (ANSI-41 Foreign Mode) Success Case d e f g j i h a b c k n o l m p
Post Ballot Version 88

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

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

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

N.S0028
6
7
13
14
15
16
17
18
8
9
10
11
12
19
20
21
22
23
24
25
26
1
2
3
4
5
B.1.3.6 4.7.2.1 GSM Foreign Mode - Success Case
Scenario: ANSI-41 Subscriber A makes a call origination attempt at ANSI-41 MSC-A to ANSI-41
Subscriber B roaming and registered in a GSM network at MSC-B. Subscriber B has call forwarding set to an address at MSC-C. Subscriber B is not IMSI detached. n o l m p j i h k d e f g a b c
ANSI-41
(MSC-A)
Call Origination
LOCREQ
Locreq [TLDN]
ANSI-41
(B’s HLR)
ROUTEREQ
Routereq [TLDN]
IIF
GSM
(VLR/MSC-B)
Provide Roaming Number[GMSC#,CR#]
Provide Roaming NumberAck [MSRN]
Establish Connection Attempt
Resume Call Handling [CR#,reason]
REDREQ [REDREASON]
TRANUMREQ [REDREASON] tranumreq redreq
Connection Release
Resume Call HandlingAck
Call Forward Setup
(MSC-C)
Figure 60: Optimal Routing with Late Call Forwarding (GSM Foreign Mode) Success Case a. ANSI-41 MSC-A receives a call origination stimulus from Subscriber A. b. The ANSI-41 MSC-A sends an ANSI-41-Location Request message for routing information to
Subscriber B's ANSI-41 HLR with the MSCID address of the originating MSC (ANSI-41 MSC-A). c. Subscriber B's ANSI-41 HLR determines that Subscriber B is roaming at MSC-B and sends a
ANSI-41-Routing Request message number with the MSCID address of the ANSI-41 MSC-A received in step b. to an IIF acting on behalf of MSC-B to get a roaming number. d. The IIF relays this request to GSM MSC/VLR-B by sending a GSM-Provide Roaming Number message. The IIF generates two parameters: the Call Reference number (for the VLR/MSC-B to use in the GSM-RCH) and the GMSC address set to the IIF address, to indicate that the IIF is capable of supporting optimal routing for late call forwarding. e. GSM MSC/VLR-B acknowledges the GSM - Provide Roaming Number message with the Mobile
Subscriber Roaming Number (MSRN). f. Upon receipt of this message, the IIF sends the TLDN to Subscriber B's ANSI-41 HLR in the
ANSI-41-Routing Request message. d e f g j i h k a b c n o l m p
Post Ballot Version 92

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

N.S0028
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
B.1.3.7 4.7.2.2 GSM Foreign Mode - Failure case
Scenario: ANSI-41 Subscriber A makes a call origination attempt at ANSI-41 MSC-A to ANSI-41
Subscriber B roaming and registered in a GSM network at MSC-B. Subscriber B has call forwarding set to an address at MSC-C. Optimal Routing fails at IPLMN. Subscriber B is not IMSI detached. n o l m d e f g j i h a b
ANSI-41
(MSC-A)
Call Origination
LOCREQ c k
Locreq [TLDN]
ANSI-41
(B’s HLR)
ROUTEREQ
Routereq [TLDN]
IIF
GSM
(VLR/MSC-B)
Provide Roaming Number [GMSC#,CR#]
Provide Roaming NumberAck [MSRN]
Establish Connection Attempt
Resume Call Handling [CR#,reason]
REDREQ [REDREASON]
TRANUMREQ [REDREASON] tranumreq redreq (reject)
Resume Call Handling Error
(MSC-C)
Forward Call d e f g j i h k a b c n o l m
Figure 61: Optimal Routing with Late Call Forwarding (GSM Foreign Mode) Failure Case a.-l.These steps are the same as the Success Case. m. The redirection request at step j. is rejected. n. The IIF sends a GSM-Resume Call Handling Error message to GSM MSC-B. o. The GSM MSC-B forwards the incoming call to MSC-C.
Post Ballot Version 94

N.S0028
1
5
6
7
2
3
4
This section depicts the interactions between network entities in various situations related to GSM and ANSI-41 foreign mode operation and Call Waiting (CW).
B.1.3.8 4.8.1.1 ANSI-41 Foreign Mode Successful Call Waiting Activation
This scenario describes a successful call waiting activation by a native GSM subscriber roaming in an
ANSI-41 network.
Serving System
MS MSC/
VLR
IIF GSM
HLR
*FC [SEND]
8
9 feature confirmation call release
FEATREQ [DGTSDIAL]
ActivateSS
ActivateSS Ack featreq [FEATRESULT, ANNLIST]
QUALDIR qualdir
Insert Subscriber Data
ISD Ack
Figure 62: ANSI-41 Foreign Mode Call Waiting Activation g h f e c b d a j i k
10
11
12
13
14 a. The subscriber requests activation of call waiting. The MS converts the user-entered MMI/menu selections to feature codes. (e.g. *FC). The MS sends this feature code string to the Serving
MSC. During analysis of the digit string, the Serving MSC detects a feature code string. b. The digit string is included in a FEATREQ and sent from the Serving MSC to the IIF emulating the
HLR associated with the MS.
Post Ballot Version 95

N.S0028
17
18
19
20
10
11
12
13
14
15
16
7
8
9
1
2
3
4
5
6 c. The IIF determines the digit string pertains to the activation of call waiting and then sends an
Activate SS message to the HLR to request activation of call waiting. 5 d. The HLR returns an Activate SS Ack message to the IIF indicating a successful activation of call waiting. e. The IIF sends a featreq to the Serving MSC containing the feature request confirmation indication. f. When the featreq is received from the IIF, the Serving MSC provides treatment to the served MS based on the information contained in the response. In this case, the treatment is to apply feature confirmation. g. The Serving MSC releases the call. h. Because the request resulted in a change to the subscriber’s service profile (i.e., the call waiting feature was activated), the HLR reports the change by sending an Insert Subscriber Data message to the IIF emulating the Serving MSC/VLR. i. The IIF returns an Insert Subscriber Data Ack message to the HLR. j. The IIF sends a QUALDIR message to the Serving MSC/VLR. k. The Serving MSC/VLR returns a qualdir to the IIF.
B.1.3.9 4.8.1.2 ANSI-41 Foreign Mode Unsuccessful Call Waiting Activation
The following scenario describes an unsuccessful call waiting activation by a native GSM subscriber roaming in an ANSI-41 network.
5 Most likely, the GSM 02.30 standardized MMI would be mapped to the equivalent GSM functional message.
Post Ballot Version 96

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

N.S0028
1
2
3
B.1.3.10 4.8.1.3 GSM Foreign Mode Feature Activation
This scenario describes a successful call waiting activation by a native ANSI136 41 subscriber roaming in a GSM network.
4
5
12
13
14
15
9
10
11
6
7
8
16
17
18
19
20
21 a. b. c. d. e. f.
MS
GSM
MSC/
VLR
IIF HLR
Activate SS
Activate SS Ack
Activate SS
Activate SS Ack a b
FEATREQ [DGTSDIAL] c featreq [FEATRESULT, ANNLIST] d f e
QUALDIR
Insert Subscriber Data g h
ISD Ack qualdir j i
Figure 64: GSM Foreign Mode Call Waiting Activation
The subscriber requests activation of call waiting. The MS interprets the user-entered
MMI/menu selections. The MS sends a request for activation of call waiting (by issuing an
Activate SS operation).
The Serving GSM MSC sends an Activate SS message to the IIF emulating the HLR associated with the subscriber. The message specifies the call waiting supplementary service for the activation being requested.
The IIF converts the call waiting Activate SS message to a particular feature code (e.g. *FC).
The IIF includes this feature code (including *) in the Digits (Dialed) parameter of a
FEATREQ message and sends the message to the subscriber’s HLR.
The HLR returns a featreq message to the IIF indicating a successful call waiting activation.
The IIF returns an Activate SS Ack message back to the Serving GSM MSC. Any parameters the HLR may have included that provide instructions for treatment towards the user (such as
AnnouncementList) shall be ignored by the IIF and not mapped into the message sent to the
Serving GSM MSC.
When the Activate SS Ack message is received from the IIF, the Serving GSM MSC sends a message to the MS to indicate that the call waiting activation had been successful.
Post Ballot Version 98

N.S0028
1
2
3
4
5
6 g. h. i. j.
Because the request resulted in a change to the subscriber’s service profile (i.e., the call waiting feature was activated), the HLR reports the change by sending a QUALDIR message to the IIF emulating the Serving GSM MSC/VLR.
The IIF sends an Insert Subscriber Data message to the Serving GSM MSC/VLR.
The Serving GSM MSC/VLR returns an Insert Subscriber Data Ack to the IIF.
The IIF returns a qualdir message to the HLR.
10
11
12
13
7
8
9
Note that the GSM foreign mode unsuccessful call waiting activation case parallels the ANSI-41 foreign mode unsuccessful call waiting activation case shown in the previous section.
B.1.3.11 4.8.2.1 ANSI-41 Foreign Mode Call Waiting Deactivation
This scenario describes a successful call waiting deactivation by a native GSM subscriber roaming in an ANSI-41 network.
Post Ballot Version 99

N.S0028
MS
ANSI-136 Serving System
MSC/
VLR
IIF GSM
HLR
*FC0 [SEND] feature confirmation call release
FEATREQ [DGTSDIAL]
DeactivateSS
DeactivateSS Ack featreq [FEATRESULT, ANNLIST]
Insert Subscriber Data
ISD Ack
QUALDIR qualdir f g d e a c b h j i k
1
2
9
10
11
12
3
4
5
6
7
8
Figure 65: ANSI-41 Foreign Mode Call Waiting Deactivation a. The subscriber selects a menu entry in order to deactivate call waiting. The MS converts the user-entered MMI/menu selections to feature codes. (e.g. *FC0). The MS sends this digit string towards the network. The digit string is received by the Serving MSC. During analysis of the digit string, the Serving MSC detects a feature code string. b. The dialed digits are included in a FEATREQ and sent from the Serving MSC to the IIF emulating the HLR associated with the MS. c. The IIF determines the digit string pertains to the deactivation of call waiting and then sends a
Deactivate SS message to the HLR to request deactivation of call waiting. 7 d. The HLR returns a Deactivate SS Ack message to the IIF indicating a successful deactivation of call waiting.
7 Most likely, the GSM 02.30 standardized MMI would be mapped to the equivalent GSM functional message.
Post Ballot Version 100

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

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

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

N.S0028
1
2
3
4
5
6
B.1.3.13 4.9.1.1 GSM Mode
If CNIP / CLIP service is authorized and active, the calling party number is available and presentation is allowed, the called party’s serving network shall provide the calling party number to the called party during call alerting as in Figure 67 below.
MSC
Incoming call to DN
HLR IIF
LOCREQ
(Calling Party No)
ROUTREQ
(Calling Party No)
Routreq (TLDN = MSRN)
Provide Roaming No
(Calling Party No))
Prov Roaming No Ack
(MSRN)
Locreq (TLDN = MSRN)
MSC/
VLR
Call Setup
(Calling Party No)
Alert
(Calling Party No,
PI, SI, Sub-address)
MS i f g h a b c d e
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
ANSI-41 NETWORK GSM NETWORK
Figure 67: Calling number/ line identification presentation: mobile station or fixed terminal to mobile station – GSM Foreign Mode a. An incoming call for the called party is received at his/her home network. b. The calling party number may be carried in the calling party number digits parameter as specified in TIA/EIA-41-5-D [1]. c. The calling party number may be carried in the calling party number string parameter as specified in TIA/EIA-41-5-D [1]. d. The calling party number may be carried in the additional signal information element as specified in GSM 09.02 [7]. e. The VLR returns a roaming number for routing purposes. f. The IIF maps the MSRN it receives from the VLR into the TLDN field in the routreq.
Post Ballot Version 104

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

N.S0028
1
2
3
4
5
B.1.3.14 4.9.1.2 ANSI-41 Mode
If CNIP / CLIP service is authorized and active, the calling party number is available and presentation is allowed, the called party’s serving network shall provide the calling party number to the called party during call alerting as in Figure 68 below.
GMSC
Incoming call to DN
Send Routing Info
(Calling Party No)
HLR
IIF
Provide Roaming No
(Calling Party No)
ROUTREQ
(Calling Party No)) routreq
(TLDN)
Prov Roaming No Ack
(MSRN =TLDN)
MSC/
VLR
SRI Ack
(MSRN = TLDN)
Call Setup
(Calling Party No)
Alert
(Calling Party No)
MS i f g h a b c d e
6
7
15
16
17
18
19
20
8
9
10
11
12
13
14
21
22
23
24
25
ANSI-41 NETWORK
GSM NETWORK
Figure 68: Calling number/ line identification presentation: mobile station or fixed terminal to mobile station – ANSI-41 Foreign Mode a. An incoming call for the called party is received at his/her home network. b. The calling party number may be carried in the additional signal information element as specified in GSM 09.02 [7]. c. The calling party number may be carried in the additional signal information element as specified in GSM 09.02 [7]. d. The calling party number may be carried in the calling party number string parameter as specified in ANSI-41.5 [1]. e. The MSC returns a TLDN for routing purposes f. The IIF maps the TLDN it receives from the MSC into the MSRN field in the Provide Roaming No
Ack. g. The HLR returns an SRI Ack to the GMSC with the routing information it received from the IIF.
Post Ballot Version 106

N.S0028
27
28
29
30
31
32
33
23
24
25
26
5
6
7
8
9
1
2
3
4
10
11
12
13
14
15
16
17
18
19
20
21
22
34 h. The trunk signaling between the MSC’s may transit a number of intermediate signaling networks of various capabilities. As such, there is no guarantee that the calling party number can be conveyed using the ISUP/TUP signaling capabilities. i. The mobile station receives an incoming call alert, which contains the calling party identification information.
Note: Where a calling party number is delivered both via MAP signaling and ISUP/TUP signaling, the number delivered via MAP signaling takes precedence.
B.1.3.14.1 4.9.1.2.1 Interrogation
The subscriber cannot request the status of the supplementary service in ANSI-41 Foreign mode.
B.1.3.15 4.9.2.1 General
If the calling subscriber has calling number/line identification restriction authorized and active and it is impossible to indicate to the terminating network (due to interworking) that the number shall not be presented to the terminating party, the calling number/line identity shall not be delivered to the terminating network.
B.1.3.16 4.9.2.2 GSM Mode
If CNIR / CLIR service is authorized and active, the calling party number is available and presentation is restricted, the called party’s serving network shall not present the calling party number to the called party during call alerting. An indication that the calling party number is restricted shall be delivered to the called party.
B.1.3.16.1 4.9.2.2.1 Interrogation
The subscriber can request the status of the CNIR /CLIR supplementary service and be informed if the service is provided to him/her and which mode is provided, i.e. permanent or temporary and if temporary, what the default value is (i.e. allowed or restricted).
B.1.3.17 4.9.2.3 ANSI-41 Mode
If CNIR / CLIR service is authorized and active, the calling party number is available and presentation is restricted, the called party’s serving network shall not present the calling party number to the called party during call alerting. An indication that the calling party number is restricted shall be delivered to the called party.
B.1.3.17.1 4.9.2.3.1 Interrogation
The subscriber cannot request the status of the supplementary service.
Post Ballot Version 107

N.S0028
1
5
6
7
8
2
3
4
9
10
11
12
13
This section describes the interoperability at the IIF to support ANSI-41 outgoing call restrictions,
GSM Operator Determined Barring (ODB), and GSM Call Barring Supplementary Services. The scenarios included are illustrative and not exhaustive.
ODB is a GSM administrative feature. As described in associated Stage 1 documentation, direct mapping of many GSM ODB or call barring options does not exist in ANSI136 41 mode. Likewise, many ANSI-41 outgoing call restrictions do not directly map to equivalent GSM ODB or call barring options.
These call flows apply only to Call Barring Supplementary Services, ANSI-41 call restrictions, or ODB programs (e.g., Barring of Outgoing Calls) for which barring is performed at the VLR. Any barring or call restrictions applied in the HLR shall result in the appropriate restrictions being downloaded to the serving VLR/MSC via the IIF.
14
15
16
B.1.3.18 4.10.1.1 Activation of Call Restrictions while in GSM Foreign Mode
This scenario describes the successful activation of call restrictions for a native ANSI136 41 subscriber roaming in a GSM network at a time when the subscriber is currently registered.
HLR IIF
VLR/
MSC
17
18
19
20
21
22
23
24
25
26
27
28
29
QUALDIR a
Insert Subscriber Data b
ISD Ack c qualdir d
Figure 69: Activation of Call Restriction - GSM Foreign Mode a. Call restrictions are applied at the ANSI-41 HLR. The HLR sends an appropriate
QualificationDirective INVOKE message to the IIF emulating the VLR where the subscriber is roaming. b. The IIF forwards a corresponding Insert Subscriber Data message to the GSM VLR. c. The VLR sends an Insert Subscriber Data acknowledgement to the IIF. d. The IIF forwards a QualificationDirective RETURN RESULT message to the HLR.
Post Ballot Version 108

N.S0028
1
2
3
B.1.3.19 4.10.1.2 Activation of Call Barring while in ANSI-41 Foreign Mode
This scenario describes the successful application of ODB or call barring for a native GSM subscriber roaming in an ANSI-41 network.
HLR IIF
VLR/
MSC
10
11
12
13
14
7
8
9
4
5
6
15
16
17
Insert Subscriber Data a
QUALDIR b qualdir c
ISD Ack d
Figure 70: Activation of Call Barring – ANSI-41 Foreign Mode a. ODB or call barring is applied at the GSM HLR. The HLR sends an appropriate Insert Subscriber
Data message to the IIF emulating the VLR where the subscriber is roaming. b. The IIF forwards a corresponding QualificationDirective INVOKE message to the ANSI-41 VLR. c. The VLR sends a QualificationDirective RETURN RESULT to the IIF. d. The IIF forwards an Insert Subscriber Data acknowledgement message to the HLR.
B.1.3.20 4.10.2.1 GSM Mode
Barring of incoming calls is performed at the ANSI-41 HLR. There is no IIF involvement.
18
19
20
21
22
23
B.1.3.21 4.10.2.2 ANSI-41 Mode
Barring of incoming calls is performed at the GSM HLR. There is no IIF involvement.
Barring of Roaming is performed at the HLR. The following subsections, however, illustrate the signaling at the IIF when a barred subscriber attempts to roam into a GSM or ANSI-41 Foreign network.
24
25
26
B.1.3.22 4.10.3.1 GSM Mode
This scenario describes the successful barring of roaming for a native ANSI136 41 subscriber attempting to roam into a GSM network.
Post Ballot Version 109

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

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

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

N.S0028
1
2
3
B.1.3.25 4.10.4.2 ANSI-41 Mode
This scenario describes the successful ODB barring of supplementary services management for a native GSM subscriber in an ANSI-41 network.
MSC/
VLR IIF HLR
10
11
12
13
7
8
9
14
15
16
17
18
4
5
6
FEATREQ a
Activate SS b
A ctivate SS Ack c featreq d
Figure 74: Invocation of Barring of Supplementary Services Management – ANSI-41 Foreign
Mode a. A native GSM subscriber with ODB barring of Supplementary Services Management active, roaming in an ANSI-41 network, attempts to activate a supplementary service. The MSC sends a
FeatureRequest INVOKE to the IIF emulating the subscriber’s HLR. b. The IIF issues an Activate SS message to the HLR. c. The HLR, determining that ODB barring is in effect for this subscriber, sends an Activate SS acknowledgement, with User Error set to SS Subscription Violation to the IIF. d. The IIF issues a FeatureRequest RETURN RESULT, with FeatureResult set to Unsuccessful to the VLR. The VLR denies the activation.
Post Ballot Version 113

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

N.S0028
1
2
3
4
5
If the mobile station only supports GHOST (GSM Hosted SMS Teleservice) or WEMT , there shall be a need for CMT (Cellular Messaging Transport) to GHOST /WEMT and GHOST /WEMT to CMT conversion in the ANSI-41 network (i.e., in native mode), most probably in the Message Centers. This is depicted in the next two diagrams.
6
7
8
B.1.3.26 4.11.2.1 Short Message from CMT Mobile Station to GHOST /WEMT Mobile
Station both in Native Mode
MS-A
SMD-REQ (CMT)
TDMA
MSC
SMDPP (CMT) smdpp [ACK]
MC-A
SMD-ACK
SMDPP (CMT) smdpp [ACK]
MC-B
SMSREQ smsreq
SMDPP (GHOST)
TDMA
HLR
TDMA
MSC
(SMS delivered to
Mobile Station using GHOST) smdpp [ACK] a b c d e f g i h
13
14
15
9
10
11
12
Figure 75: Short Message from a TDMA or CDMA CMT phone to a GHOST or WEMT mobile station, both in native mode
Notes:
Message Center B (MC-B) is responsible for converting CMT to GHOST /WEMT .
MC-A and MC-B could be one and the same.
16
Post Ballot Version 115

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

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

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

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

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

N.S0028
1
2
B.1.3.30 4.11.3.3 Unsuccessful Mobile Terminated Delivery (Failure at MSC)
The following scenario applies to short message delivery failure in either CMT or GHOST /WEMT
ANSI-41
GSM
MC HLR IIF VMSC
SMSREQ smsreq
SMDPP
smdpp [NAK]
FORWARD SHORT MESSAGE
Forward Short Message f b c d e
3
17
18
19
20
21
22
23
24
25
26
27
11
12
13
14
15
16
8
9
10
4
5
6
7 format.
Figure 79: Unsuccessful Mobile Terminated Delivery (Failure at MSC) a. The ANSI-41 MC sends a SMSRequest Invoke message to the HLR, including as arguments the
MIN (MSISDN) of the mobile station and SMS Notification Indicator. b. The HLR determines if the message shall be forwarded to the MS and sends a response back in a SMSRequest Return Result, with the SMS_Address set to the IIF address (point code or E.164 address). c. The MC formats a GHOST /WEMT teleservice or a CMT short message and sends it to the IIF in an SMDPP message. d. Upon receipt of the SMDPP message, the IIF builds a FORWARD SHORT MESSAGE, stripping off the GHOST /WEMT teleservice and using the encapsulated GSM SMS transfer PDU, and routes it to the VMSC. If the message received is in the CMT format, the IIF maps this information into a short message in GSM format. e. The VMSC packages the GSM SMS RP-DATA into a CP-DATA message and delivers it across the GSM air interface to the mobile station. The mobile station negatively acknowledges either the CP-DATA message or the RP-DATA message. The VMSC sends a negative acknowledgement Forward Short Message (with appropriate cause value) back to the IIF. f. The IIF maps the received Forward Short Message into a SMDPP Return Result and sends it to the MC. In addition, the IIF sets one of the GSM SMS flags as defined in the GSM 03.40 specification [4] according to the error cause received from the VMSC; that is, the Mobile
Subscriber Not Reachable Flag (MNRF) shall be set if the error cause is “absent subscriber”, and the Memory Capacity Exceeded Flag (MCEF) shall be set if the error cause is “memory capacity exceeded”. Additionally, the IIF emulating the ANSI-41 MSC shall set and store the SMS
Delivery Pending flag with the MC parameters received in the SMDPP (for later delivery in the
Post Ballot Version 121

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

N.S0028
1
2
3
4
B.1.3.31 4.11.3.4 Unsuccessful Mobile Terminated Delivery (Failure at IIF)
The following scenario applies to short message delivery failure in either CMT or GHOST /WEMT format.
ANSI-41
GSM
MC HLR IIF VMSC
SMSREQ smsreq
SMDPP
smdpp [NAK] b c d
8
9
10
11
12
13
14
15
16
17
5
6
7
Figure 80: Unsuccessful Mobile Terminated Delivery (Failure at IIF) a. The ANSI-41 MC sends a SMSRequest Invoke message to the HLR, including as arguments the
MIN (MSISDN) or IMSI of the mobile station and SMS Notification Indicator. b. The HLR determines if the message shall be forwarded to the MS and sends a response back in a SMSRequest Return Result, with the SMS_Address set to the IIF address (point code or E.164 address). c. The MC formats a GHOST /WEMT teleservice and sends it to the IIF in an SMDPP message. d. Upon receipt of the SMDPP message, the IIF examines the GSM 03.40 HLR flags (MNRF/MCEF) and determines that the MS is unable to receive a Short Message. The IIF indicates this fact in the SMDPP Return Result. It includes the cause for the failure in the SMS_CauseCode parameter of the SMDPP Return Result. The IIF shall set & store the SMS Delivery Pending Flag with the data received in the SMDPP message (for later delivery in the SMSNOT).
Post Ballot Version 123

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

1
2
B.1.3.33 4.11.4.1 Successful GSM SMS mapped to ANSI136 41 (CMT) SMS
N.S0028
GSM
ANSI-41
SMSC HLR IIF MSC
SMS
Delivery
SEND ROUTING INFO FOR SM
Send Routing Info For SM
FORWARD SHORT MESAGE
Forward Short Message
SMDPP (CMT)
(SMS delivered to
Mobile Station) smdpp [CMT] d e f g h b c
3
21
22
23
24
25
15
16
17
18
19
20
10
11
12
13
14
7
8
9
4
5
6
Figure 82: Successful GSM SMS mapped to ANSI136 41 (CMT) SMS a. The GSM Short Message Service Center (SMSC) receives a short message for a specific subscriber. Note: This step is shown for completeness only and is not repeated in subsequent call flows. b. The SMS-GMSC originates a Send Routing Info for Short Message to the GSM HLR of the short message recipient to request a routing address for delivering the short message to that subscriber. c. Since the subscriber has a current valid location stored in the HLR, the HLR returns it to the
SMS-GMSC in the Send Routing Info for Short Message Result message. d. The SMS-GMSC then sends a Forward Short Message to the IIF, seen as the serving GSM
MSC/VLR. e. Upon reception of the Forward Short Message from the SMS-GMSC, the IIF originates a Short
Message Delivery Point to Point message to the serving ANSI-41 MSC/VLR after having translated the short message into IS136 41 CMT format. The IIF is then acting as an ANSI136
41 Message Center. f. The serving ANSI-41 MSC/VLR sends the short message to the mobile station and an acknowledgement is sent back to the MSC/VLR.
Post Ballot Version 125

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

N.S0028
1
2
3
4
5
6
B.1.3.34 4.11.4.2 Successful GSM SMS mapped to ANSI136 41 (GHOST /WEMT ) SMS
This method uses the tunneling concept. Instead of translating the GSM SMS to an ANSI136 41
CMT SMS format, the IIF shall package the GSM SMS into an ANSI-136TDMA SMS with the teleservice GHOST (GSM Hosted SMS Teleservice) or CDMA SMS with teleservice WEMT..
GSM
ANSI-41
SMSC HLR IIF MSC
SEND ROUTING INFO FOR SM
Send Routing Info For SM
FORWARD SHORT MESAGE
Forward Short Message
REPORT SM DELIVERY STATUS
Report SM Delivery Status
SMDPP (GHOST) smdpp [ACK]
7
8
9
10
11
12
13
14
15
16
17
Figure 83: Successful GSM SMS mapped to ANSI136 41 (GHOST /WEMT ) SMS a. The SMSC receives a request to deliver a short message to a GSM subscriber. It sends to the
GSM HLR a SEND ROUTING INFO FOR SM, including as arguments the MSISDN, Priority, and
Service Centre address. b. The HLR determines if the message shall be forwarded to the MS and sends a response back to the SMSC in a Send Routing Info for SM, including as arguments the IMSI of the MS and
Network Node Number of the IIF. c. The SMSC originates a FORWARD SHORT MESSAGE to the address provided by the HLR (i.e.,
IIF), including as arguments the IMSI, Service Centre Address, and GSM SMS-DELIVER PDU
(and optionally if more messages are to be sent).
18
19
20
21
Upon receipt of the FORWARD SHORT MESSAGE, the IIF shall build an ANSI-41 SMDPP , encapsulating the GSM SMS transfer PDU in the GHOST /WEMT teleservice. The IIF shall route the SMDPP message to the serving MSC. The serving MSC maps the SMDPP message into an
R-DATA message and sends it to the mobile station over the TDMA or CDMAANSI-136 air d e f g h b c
Post Ballot Version 127

N.S0028
8
9
10
11
12
4
5
6
7
1
2
3 interface. The mobile station shall acknowledge receipt of the R-DATA message and
GHOST /WEMT teleservice by sending an R-DATA ACCEPT message to the MSC. d. After receiving the R-DATA ACCEPT message, the serving MSC sends a positive acknowledgement SMDPP Return Result to the IIF. e. The IIF maps the received SMDPP Return Result to a Forward Short Message, and sends it to the GSM SMSC. f. The SMSC send a REPORT SM DELIVERY STATUS to the HLR, including as arguments the
MSISDN, SMSC Address, and Successful Transfer. The SMSC sends this message based on the procedures described in GSM 03.40 [4] and GSM 09.02 [6]. g. The HLR shall set the appropriate flags as specified in the GSM specifications (GSM 09.02 and
03.40), then send a Report SM Delivery Status to the SMSC.
13
14
B.1.3.35 4.11.4.3 Unsuccessful GSM SMS mapped to ANSI136 41 SMS (Failure at MS)
The following scenario applies to short messages delivered in either CMT or GHOST /WEMT format.
GSM
ANSI-41
SMSC HLR IIF MSC
SEND ROUTING INFO FOR SM
Send Routing Info For SM
FORWARD SHORT MESAGE
Forward Short Message
REPORT SM DELIVERY STATUS
Report SM Delivery Status
SMDPP smdpp [NAK] d e f g h b c
15
16
17
18
19
20
21
22
Figure 84: Successful GSM SMS mapped to ANSI136 41 SMS (Failure at MS) a. The SMSC receives a request to deliver a short message to a GSM subscriber. It sends to the
GSM HLR a SEND ROUTING INFO FOR SM, including as arguments the MSISDN, Priority, and
Service Center address. b. The HLR determines if the message shall be forwarded to the MS and sends a response back to the SMSC in a Send Routing Info for SM, including as arguments the IMSI of the MS and
Network Node Number of the IIF.
Post Ballot Version 128

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

N.S0028
GSM
ANSI-41
SMSC HLR IIF
MSC
SEND ROUTING INFO FOR SM
Send Routing Info For SM
FORWARD SHORT MESAGE
Forward Short Message
REPORT SM DELIVERY STATUS
Report SM Delivery Status
SMDPP smdpp [NAK] d e f g h b c
1
8
9
10
11
12
13
14
15
5
6
7
2
3
4
16
17
18
19
20
21
22
23
24
Figure 85: Unsuccessful Delivery to GSM Subscriber (Postponed at MSC) a. The SMSC receives a request to deliver a short message to a GSM subscriber. It sends to the
GSM HLR a SEND ROUTING INFO FOR SM, including as arguments the MSISDN, Priority, and
Service Centre address. b. The HLR determines if the message shall be forwarded to the MS and sends a response back to the SMSC in a Send Routing Info for SM, including as arguments the IMSI of the MS and
Network Node Number of the IIF. c. The SMSC originates a FORWARD SHORT MESSAGE to the address provided by the HLR (i.e.,
IIF), including as arguments the IMSI, Service Centre Address, and GSM SMS-DELIVER PDU
(and optionally if more messages are to be sent). d. Upon receipt of the FORWARD SHORT MESSAGE, the IIF builds an ANSI-41 SMDPP message, encapsulating the GSM SMS transfer PDU in a GHOST /WEMT teleservice, and routes it to the serving MSC. The IIF can also convert the message into ANSI136 41 CMT format. The addressed MS is temporarily unavailable for short message delivery and notification was requested. e. The MSC responds with a negative acknowledgement SMS_CauseCode carried in the SMDPP
Return Result indicating delivery is postponed and returns it to the source of the corresponding
SMDPP (i.e., IIF). The MSC sets its SMS Delivery Pending Flag. f. The IIF sets the SMS Delivery Pending Flag in the IIF and maps the received SMDPP Return
Result into a Forward Short Message and sends it to the SMSC, after mapping the
SMS_CauseCode to the appropriate GSM MAP error. g. The SMSC sends a REPORT SM DELIVERY STATUS to the HLR, including as arguments the
MSISDN, SMSC Address, and Error Cause. The SMSC sends this message based on the procedures described in GSM 03.40 [4] and GSM 09.02 [6].
Post Ballot Version 130

N.S0028
1
2
3 h. The HLR shall set the appropriate flags as specified in the GSM specifications (GSM 09.02 and
03.40), then send a Report SM Delivery Status to the SMSC.
Post Ballot Version 131

N.S0028
1
2
B.1.3.37 4.11.4.5 Unsuccessful Delivery to GSM Subscriber (Failure at IIF)
GSM
ANSI-41
SMSC HLR IIF MSC
SEND ROUTING INFO FOR SM
Send Routing Info For SM
FORWARD SHORT MESAGE b c
Forward Short Message
REPORT SM DELIVERY STATUS
Report SM Delivery Status f d e
10
11
12
7
8
9
3
4
5
6
13
14
15
16
17
18
19
20
Figure 86: Unsuccessful Delivery to GSM Subscriber (Failure at IIF) a. The SMSC receives a request to deliver a short message to a GSM subscriber. It sends to the
GSM HLR a SEND ROUTING INFO FOR SM, including as arguments the MSISDN, Priority, and
Service Centre address. b. The HLR determines if the message shall be forwarded to the MS and sends a response back to the SMSC in a Send Routing Info for SM, including as arguments the IMSI of the MS and Network
Node Number of the IIF. c. The SMSC originates a FORWARD SHORT MESSAGE to the address provided by the HLR (i.e.,
IIF), including as arguments the IMSI, Service Centre Address, and GSM SMS-DELIVER PDU
(and optionally if more messages are to be sent). d. Upon receipt of the FORWARD SHORT MESSAGE at the IIF, if the subscriber is known to be unavailable or the SMS Waiting Indicator flag is set, then the IIF builds a Forward Short Message and send it back to the SMSC. e. The SMSC sends a REPORT SM DELIVERY STATUS to the HLR, including as arguments the
MSISDN, SMSC Address, and Error Cause. f. The HLR shall set the appropriate flags as specified in the GSM specifications (GSM 09.02 and
03.40) and sends a Report SM Delivery Status to the SMSC. The SMSC sends this message based on the procedures described in GSM 03.40 [4] and GSM 09.02 [6].
21
22
23
24
B.1.3.38 4.11.4.6 Alerting for a GSM Subscriber in ANSI-41 Foreign Mode
In the event that the delivery of the short message to the ANSI-41 network is not possible, the IIF shall be notified by the serving ANSI-41 MSC/VLR when the subscriber is available again. This shall be done by receiving a Registration Notification or an SMS Notification message. This is illustrated in
Post Ballot Version 132

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

N.S0028
1
2
3
4
5
This section describes the message flows for originating a short message to the subscriber’s home message center when the mobile station is operating in GSM Foreign Mode. The following scenarios 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
FORWARD SHORT MESSAGE
Forward Short Message
SMDPP smdpp [ACK] b c d
7
8
9
10
11
12
13
14
15
16
17
Figure 88: Successful Mobile Originated Delivery a. The VMSC originates a FORWARD SHORT MESSAGE to the address provided by the MS (i.e.,
IIF), including as arguments the Service Centre Address, MSISDN and GSM SMS-SUBMIT PDU. b. Upon receipt of the FORWARD SHORT MESSAGE, the IIF builds an ANSI-41 SMDPP message, encapsulating the GSM SMS transfer PDU in a GHOST /WEMT teleservice, and routes it to the originator’s home MC. The IIF can also map the Forward Short Message into a CMT short message. c. The MC sends a positive acknowledgement SMDPP Return Result to the IIF. d. The IIF maps the received SMDPP Return Result to a Forward Short Message, and sends it to the VMSC.
18
Post Ballot Version 134

1 B.1.3.40 4.11.5.2 Unsuccessful Mobile Originated (Failure at MC)
N.S0028
GSM
ANSI-41
VMSC HLR IIF MC
FORWARD SHORT MESSAGE
Forward Short Message
SMDPP smdpp [NAK] b c d
2
3
4
5
6
7
8
9
10
11
12
13
Figure 89: Unsuccessful Mobile Originated (Failure at MC) a. The VMSC originates a FORWARD SHORT MESSAGE to the address provided by the MS (i.e.,
IIF), including as arguments the Service Centre Address, MSISDN and GSM SMS-SUBMIT PDU. b. Upon receipt of the FORWARD SHORT MESSAGE, the IIF builds an ANSI-41 SMDPP message encapsulating the GSM SMS transfer PDU in a GHOST /WEMT teleservice, and routes it to the
MC. The IIF can also map the Forward Short Message into a CMT short message. c. The MC sends a negative acknowledgement SMDPP Return Result to the IIF. d. The IIF maps the received SMDPP Return Result to a Forward Short Message with the appropriate cause code value, and sends it to the VMSC.
Post Ballot Version 135

N.S0028
1 B.1.3.41 4.11.5.3 Unsuccessful Mobile Originated (Failure at IIF)
ANSI-41 GSM
VMSC HLR
FORWARD SHORT MESSAGE
Forward Short Message
IIF MC a b
5
6
7
8
9
2
3
4
Figure 90: Unsuccessful Mobile Originated (Failure at IIF) a. The VMSC originates a FORWARD SHORT MESSAGE to the address provided by the MS (i.e.,
IIF), including as arguments the Service Centre Address, MSISDN and GSM SMS-SUBMIT PDU. b. Upon receipt of the FORWARD SHORT MESSAGE, the IIF builds a negative acknowledgement
Forward Short Message and sends it to the VMSC.
10
11
12
13
14
This section describes the message flows for originating a short message to the subscriber’s home message center when the mobile station is operating in ANSI-41 Foreign Mode. The following scenarios apply to short messages originated in either CMT or GHOST /WEMT format.
Post Ballot Version 136

1 B.1.3.42 4.11.6.1 Successful Mobile Originated Delivery
ANSI-41 GSM
VMSC HLR IIF
SMDPP
smdpp [ACK]
SMSC
N.S0028
FORWARD SHORT MESSAGE
Forward Short Message b c d
7
8
9
10
11
12
2
3
4
5
6
Figure 91: Successful Mobile Originated Delivery – ANSI-41 Foreign Mode a. The VMSC originates a SMDPP invoke to the address provided by the MS (i.e., IIF), including as arguments the Teleservice Server Address, MIN (MSISDN), and GSM SMS-SUBMIT PDU encapsulated in the GHOST /WEMT teleservice. The mobile originated message can also be in the CMT format. b. Upon receipt of the SMDPP invoke, the IIF builds a FORWARD SHORT MESSAGE, and routes it to the SMSC. c. The SMSC sends a positive acknowledgement Forward Short Message to the IIF. d. The IIF maps the received Forward Short Message to a SMDPP Return Result and sends it to the
VMSC.
Post Ballot Version 137

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
smdpp [NAK]
FORWARD SHORT MESSAGE
Forward Short Message b c d
2
3
8
9
10
4
5
6
7
11
12
13
14
Figure 92: Successful Mobile Originated (Failure at SMSC) – ANSI-41 Foreign Mode a. The VMSC originates a SMDPP invoke to the address provided by the MS (i.e., IIF), including as arguments the Teleservice Server Address, MIN (MSISDN) and GSM SMS-SUBMIT PDU encapsulated in the GHOST /WEMT teleservice. The mobile originated message can also be in the CMT format. b. Upon receipt of the SMDPP message, the IIF builds a FORWARD SHORT MESSAGE, stripping off the GHOST GHOST/WEMT teleservice and using the encapsulated GSM SMS transfer PDU, and routes it to the SMSC. c. The SMSC sends a negative acknowledgement Forward Short Message to the IIF. d. The IIF maps the received Forward Short Message into a SMDPP Return Result and sends it to the VMSC.
Post Ballot Version 138

1
2
B.1.3.44 4.11.6.3 Unsuccessful Mobile Originated (Failure at IIF)
ANSI-41 GSM
VMSC HLR IIF SMSC
N.S0028
SMDPP
smdpp [NAK] a b
3
4
5
6
7
8
9
10
11
Figure 93: Unsuccessful Mobile Originated (Failure at IIF) – ANSI-41 Foreign Mode a. The VMSC originates a SMDPP invoke to the address provided by the MS (i.e., IIF), including as arguments the Teleservice Server Address, MIN (MSISDN) and GSM SMS-SUBMIT PDU encapsulated in the GHOST /WEMT teleservice. The mobile originated message can also be in the CMT format. b. Upon receipt of the SMDPP message, the IIF builds a negative acknowledgement SMDPP
Return Result and sends it to the VMSC.
Post Ballot Version 139

N.S0028
4
9
10
11
12
13
5
6
7
8
14
1
2
3
This contribution illustrates the interactions between network entities in various situations related to
GSM and ANSI-41 foreign mode operation and Message Waiting Notification.
For a native ANSI136 41 subscriber roaming in a GSM environment, there can be two events that trigger the IIF to send the Message Waiting Notification (MWN) using the GSM SMS to the Mobile
Station (MS). The first one is at registration (location update), if there is an indication in the ANSI-41
HLR that messages have been delivered to the subscriber’s voice mail box, the ANSI-41 HLR shall indicate that in the Registration Notification Return Result message. This shall trigger the IIF to send a GSM SMS with the MWN information. This is shown in Section 4.12.1.1 The second event is when the HLR receives a Message Waiting Notification for a subscriber that is already registered. In this case, the ANSI-41 HLR shall send a Qualification Directive message to the IIF which shall translate it into a GSM SMS with MWN indication. This is shown in Section 4.12.1.2
Post Ballot Version 140

N.S0028
1
2
B.1.3.45 4.12.1.1
GSM SMS
Indicator in ANSI-41 Registration Notification Return Result mapped to
3
28
29
30
31
32
33
34
35
36
37
38
39
19
20
21
22
7
8
9
10
11
23
24
25
26
27
12
13
14
15
16
17
18
4
5
Vmail
VMS
“Message Waiting
Notification”
ANSI-
41
IIF
GSM
MSC/VLR
MS a b
UPDATE
LOCATION
REGNOT regnot (MWNCOUNT,
MWNTYPE)
①
INSERT_SUB_DATA
Insert_sub_data
Update Loc Req c d e f g h update location
FORW.SHORT
MESSAGE (MWN)
Update Loc Accept
SMS Delivery (MWN)
SMS Delivery Ack
Forw.Short
Message i j k l m
② n
Figure 94: Indicator in ANSI-41 Registration Notification Return Result mapped to GSM SMS a. The Voice Mail System (VMS) receives a voice mail for a specific subscriber. b. The VMS send the “Message Waiting Notification” (MWN) to the ANSI-41 HLR of the voice mail recipient. Note that the interface between the VMS and the ANSI-41 HLR is not standardized in
ANSI-41 [1]. Note also that at that point in time, the subscriber is not registered in any serving system, so the HLR just keeps the information that a voice mail was received. c. The Mobile Station accesses a serving system and originates an update location request.
Post Ballot Version 141

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

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

N.S0028
10
29
30
31
32
25
26
27
28
33
34
35
36
37
38
39
40
41
42
18
19
20
21
22
23
24
11
12
13
14
15
16
17
5
6
7
8
9
1
2
3
4 f. The serving GSM MSC/VLR sends the short message with the MWN information to the mobile station. g. The mobile station acknowledges the delivery of the short message. h. The serving GSM MSC/VLR sends the result of the Forward Short Message to the IIF.
➁ At this point, the IIF clears the MWN flag. The reception of the Forward Short Message Result without error indicates that the MWN information was delivered successfully to the Mobile Station.
B.1.3.47 4.12.1.3 Handling when GSM MSC/VLR only supports GSM Phase 1 (MAP V1)
After the IIF has received a Qualification Directive message with MWN information or received the
MWN information through a Registration Notification Return Result, a Forward Short Message with
MWN information needs to be sent to the serving GSM MSC/VLR. This was shown in Sections
4.12.1.1 and 4.12.1.2. However, it is possible that the serving GSM MSC/VLR does not support the
MAP V2 Application Context. In this case, the IIF shall receive an ABORT message and shall re-send the Forward Short Message with MWN information using MAP V1 instead of MAP V2. This is illustrated in the following diagram.
IIF
GSM
MSC/
VLR
MS
MWN “Information”
①
FORW.SHORT
MSG (MWN) – V2
ABORT
FORW.SHORT
MSG (MWN) – V1
SMS Delivery (MWN) a b d e
②
Forw.Short
Message
SMS Delivery Ack f g
Figure 96: Handling when GSM MSC/VLR only supports GSM Phase 1 (MAP V1) a. The IIF receives Message Waiting Notification (MWN) information from a Qualification Directive or a Registration Notification Return Result. This was described in Sections 4.12.1.1 and
4.12.1.2.
➀ At this point, the IIF sets the MWN flag. This is an indication that Message Waiting Notification is to be delivered to the Mobile Station.
Post Ballot Version 144

N.S0028
21
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
28
29
30
31
22
23
24
25
26
27
8
9
10
5
6
7
11
12
13
14
15
1
2
3
4
16
17
18
19
20 b. The IIF originates an SMS with MWN information by sending Forward Short Message using MAP
V2 to the serving GSM MSC/VLR. The IIF is then acting as a GSM SMS-GMSC. The IIF is to encode the MWN information in the SMS with three methods, namely, UDH, DCS, and CPHS. c. Since the serving GSM MSC/VLR does not support the MAP V2 Application Context, it returns an
Abort message to the IIF. d. The IIF then re-sends a Forward Short Message with MWN information to the serving GSM
MSC/VLR, but this time using MAP V1. In this case, the MWN information can be encoded with only two encoding methods, namely, DCS and CPHS. e. The serving GSM MSC/VLR sends the short message with the MWN information to the mobile station. f. The mobile station acknowledges the delivery of the short message. g. The serving GSM MSC/VLR sends the result of the Forward Short Message to the IIF.
➁ At this point, the IIF clears the MWN flag. The reception of the Forward Short Message Result without error indicates that the MWN information was delivered successfully to the Mobile Station.
B.1.3.48 4.12.1.4 Handling at SMS delivery failure at the IIF
This section describes the case where the error occurs at the IIF, for example, an unrecognized
Mobile Identity Number (MIN).
VMS
ANSI-
41
IIF
Vmail Delivery a
“Message Waiting
Notification” b
QUALDIR (MWNCOUNT),
MWNTYPE)
Qualdir Return Error
Figure 97: Handling at SMS delivery failure at the IIF a. The Voice Mail System (VMS) receives a voice mail for a specific subscriber. b. The VMS send the “Message Waiting Notification” (MWN) to the ANSI-41 HLR of the voice mail recipient. Note that the interface between the VMS and the ANSI-41 HLR is not standardized in
ANSI-41 [1]. c. Since the subscriber has a current valid location stored in the HLR, the HLR initiates a
Qualification Directive message with the MWN information to the IIF acting as the serving ANSI-
41 MSC/VLR. The MWN information consists of two parameters:
MessageWaitingNotificationCount (MWNCOUNT) and MessageWaitingNotificationType
(MWNTYPE). For a description of these parameters, see to the ANSI-41-D specifications, sections 6.5.2.78 and 6.5.2.79 [1].
Post Ballot Version 145

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

N.S0028
1
2
8
26
27
28
29
22
23
24
25
15
16
17
18
9
10
11
12
13
14
19
20
21
34
35
36
37
38
30
31
32
33
3
4
5
6
7
B.1.3.49 4.12.1.5
Station
Handling at SMS delivery failure at the MSC/VLR or at the Mobile
The IIF is to keep a Message Waiting Notification (MWN) flag for each subscriber in its database. In the event of a failure to deliver a short message with MWN to the mobile station, the IIF is to keep the
MWN flag set. Another Forward Short Message with MWN information shall be sent, triggered by the reception of a subsequent GSM Update Location message, a Ready for Short Message, or a Note
MS Present message. This is illustrated in the following diagram.
MWN “Information”
①
Time elapsed
IIF
GSM
MSC/
VLR
FORW.SHORT
MSG (MWN) – V2
SMS Delivery (MWN)
Error, Abort,
Reject, timeout
SMS Delivery Error
MS a b d e
UPDATE LOCATION
READY FOR SM
(AlertReason) -V2 f g h
②
NOTE MS PRES – V1
“Acknowledgement”
FORW.SHORT
MSG (MWN) – V2
Forw.Short
Message
SMS Delivery (MWN)
SMS Delivery Ack j i k l m n
Figure 98: Handling at SMS delivery failure at the MSC/VLR or at the MS a. The IIF receives Message Waiting Notification (MWN) information from a Qualification Directive or a Registration Notification Return Result. This was described in Sections 4.12.1.1 and
4.12.1.2.
Post Ballot Version 147

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

1
2
3
B.1.3.50 4.12.2.1 GSM SMS mapped to ANSI-41 Qualification Directive
N.S0028
Post Ballot Version 149

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

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

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

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

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

155
N.S0028
GSM
SC
Vmail
Retrieval
FORW. MOBILE
TERM SM ( mwn)
GSM
SMS-
GMSC
SEND ROUTING
INFO FOR SM ( mwn)
Send Routing
Info for SM
FORW. SHORT
MESSAGE ( mwn)
GSM
HLR
IIF
ANSI-41
MSC
QUALDIR(MWNCOUNT,
MWNTYPE)
( mwn delivered to
Mobile Station)
Qualdir
1
Forw . Short Message (error: absent sub.)
GSM
SC
Forw . Mobile
Term SM (error)
GSM
SMS-
GMSC
Report SM (error)
DeliveryStatus
GSM
HLR
IIF
TDMA
MSC
2
3
4
5
Vmail
Retrieval a
FORW. MOBILE
TERM SM (mwn) b
SEND ROUTING
INFO FOR SM (mwn)
Send Routing
Info for SM
FORW. SHORT
MESSAGE (mwn) c d e
QUALDIR(MWNCOUNT,
MWNTYPE) f
(mwn delivered to
Mobile Station)
Qualdir g h
Forw. Short Message (error: absent sub.) i
Forw. Mobile
Term SM (error) j
Report SM (error)
DeliveryStatus k
Figure 101: Clearing of MWN Information after Retrieval of Messages while in ANSI-41 Foreign mode – Qualdir Method a. The voice mail messages are retrieved from the GSM subscriber. a b c d e f g h i j k
Post Ballot Version

N.S0028
40
41
42
43
44
45
46
47
34
35
36
37
38
39
28
29
30
31
32
33
22
23
24
25
26
27
17
18
19
20
21
11
12
13
14
15
16
8
9
10
5
6
7
1
2
3
4 b. The SC sends the Forward Mobile Terminating Short Message with Message Waiting Notification
(MWN) information set to “clear” to the GSM SMS-GMSC. c. The GSM SMS-GMSC enquires about the subscriber location by sending the Send Routing
Information For Short Message to the HLR. d. The HLR replies with the Send Routing Information For Short Message result. It is assumed that the native GSM subscriber has already made a registration in the ANSI-41 MSC/VLR. Another requirement is that the Service Center sets the priority of this SMS to “high” to make sure that the
SMS is sent (Section 3.2.5 of GSM 03.40). This is necessary since the IIF had previously responded with absent subscriber and the HLR had set some flags that could have prevented the delivery of this new SMS. e. The GSM SMS-GMSC originates an SMS with MWN information (set to “clear”) by sending
Forward Short Message to IIF then acting as a serving GSM MSC/VLR. This requires a GSM phase 2 support or higher. f. Upon reception of the Forward Short Message with MWN information (set to “clear”), the IIF shall initiate a Qualification Directive message with MWN information (set to “clear”) to the serving
ANSI-41 MSC/VLR. The IIF is then acting as an ANSI-41 HLR. The MWN information consists of two parameters: MessageWaitingNotificationCount (MWNCOUNT) and
MessageWaitingNotificationType (MWNTYPE). For a description of these parameters, see to the
ANSI-41-D specifications, sections 6.5.2.78 and 6.5.2.79 [1]. g. In this step, the MWN information (set to “clear”) shall be delivered to the mobile station. h. The serving ANSI-41 MSC/VLR sends the Qualification Directive Return Result to the IIF. Note that this result message does not guaranty that the MWN information (set to ”clear”) was delivered successfully to the Mobile Station, it just means that the MSC/VLR received the
Qualification Directive message, so the MWN flag shall not be cleared at this point by the IIF. i. The IIF sends the result of the Forward Short Message to the GSM SMS-GMSC with error code
“absent subscriber” so that the home system assumes that the delivery failed in case the subscriber goes back to the home system without having received the clearing notification from the serving MSC. This way, at the reception of the Update Location message, the HLR shall send an Alert-SC message so that the MWN information (in a short message) is once again sent to the
Mobile Station. j. The SMS-GMSC sends the result of the Forward Mobile Terminating Short Message to the
Service Center. Note that depending on the Service Center implementation, this may cause the
SMS to be re-sent periodically instead of waiting for the ALERTSC message indicating that the subscriber is again available to receive short messages. k. The SMS-GMSC reports the error to the HLR, which shall set the proper flags as per GSM 03.40
[4] so that an Alert-SC message is sent when necessary as explained in step i above.
Post Ballot Version 156

N.S0028
1
2
B.1.3.53 4.12.2.4 Handling at SMS delivery failure at the IIF
GSM
SC
GSM
SMS-
GMSC
GSM
HLR
IIF
3
4
21
22
23
24
25
15
16
17
18
19
20
26
27
28
9
10
11
12
13
14
5
6
7
8
Vmail
Retrieval a
FORW. MOBILE
TERM SM (MWN)
SEND ROUTING
INFO FOR SM (MWN)
Send Routing
Info for SM
FORW. SHORT
MESSAGE (MWN) b c d e
Forw. Short Message (error) f
Forw. Mobile
Term SM (error) g
Report SM (error)
DeliveryStatus h
Figure 102: Handling at SMS delivery failure at the IIF a. The GSM Service Center (SC) receives a voice mail for a specific subscriber. b. The SC sends the Forward Mobile Terminating Short Message with Message Waiting Notification
(MWN) information to the GSM SMS-GMSC. c. The GSM SMS-GMSC enquires about the subscriber location by sending the Send Routing
Information For Short Message to the HLR. d. The HLR replies with the Send Routing Information For Short Message result. It is assumed that the native GSM subscriber has already made a registration in the ANSI-41 MSC/VLR. e. The GSM SMS-GMSC originates an SMS with MWN information by sending Forward Short
Message to IIF then acting as a serving GSM MSC/VLR. f. Upon reception of the Forward Short Message with MWN information, the IIF encounters an error and sends the result of the Forward Short Message to the GSM SMS-GMSC with the proper error code as per GSM Specifications 09.02 [6]. g. The SMS-GMSC sends the result of the Forward Mobile Terminating Short Message to the
Service Center. h. The SMS-GMSC reports the error to the HLR, which sets the proper flags as per GSM 03.40 [4] so that an Alert-SC message is sent when necessary.
Post Ballot Version 157

N.S0028
1
2
3
B.1.3.54 4.12.2.5
GSM
SC
Handling at SMS delivery failure at the MSC/VLR – QualDir Method
GSM
SMS-
GMSC
Vmail
Delivery
FORW. MOBILE
TERM SM (MWN)
SEND ROUTING
INFO FOR SM (MWN)
Send Routing
Info for SM
FORW. SHORT
MESSAGE (MWN)
GSM
HLR
IIF
ANSI-41
MSC
①
QUALDIR(MWNCOUNT,
MWNTYPE)
Qualdir Return Error a d e f g b c
Forw . Short Message (error)
Forw . Mobile
Term SM (error)
Report SM (error)
DeliveryStatus h i j
GSM
SC
GSM
SMS-
GMSC
GSM
HLR
IIF
TDMA
MSC
Vmail
Delivery
FORW. MOBILE
TERM SM (MWN)
SEND ROUTING
INFO FOR SM (MWN)
Send Routing
Info for SM
FORW. SHORT
MESSAGE (MWN)
①
QUALDIR(MWNCOUNT,
MWNTYPE)
Qualdir Return Error
Forw. Short Message (error)
Forw. Mobile
Term SM (error)
Report SM (error)
DeliveryStatus
4
5
6
7
Figure 103: Handling at SMS delivery failure at the MSC/VLR Qualdir Method a. The GSM Service Center (SC) receives a voice mail for a specific subscriber. a d e f g b c h i j
Post Ballot Version 158

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

N.S0028
GSM
SC
GSM
SMS-
GMSC
GSM
HLR
IIF
TDMA
MSC
Vmail
Delivery
FORW. MOBILE
TERM SM (MWN)
SEND ROUTING
INFO FOR SM (MWN)
Send Routing
Info for SM
FORW. SHORT
MESSAGE (MWN)
Forw. Mobile
Term SM (error)
Forw. Short Message (error)
Report SM (error)
DeliveryStatus
SMDPP (GHOST, MWN) smdpp (error)
1
2
20
21
22
23
24
25
15
16
17
18
19
26
27
28
29
30
9
10
11
12
13
14
6
7
8
3
4
5
Figure 104: Handling at SMS delivery failure at the MSC/VLR – GHOST /WEMT SMS Method a. The GSM Service Center (SC) receives a voice mail for a specific subscriber. b. The SC sends the Forward Mobile Terminating Short Message with Message Waiting Notification
(MWN) information to the GSM SMS-GMSC. c. The GSM SMS-GMSC inquires about the subscriber location by sending the Send Routing
Information for Short Message to the HLR. d. The HLR replies with the Send Routing Information for Short Message result. It is assumed that the native GSM subscriber has already made a registration in the ANSI-41 MSC/VLR. e. The GSM SMS-GMSC originates an SMS with MWN information by sending Forward Short
Message to IIF then acting as a serving GSM MSC/VLR. This requires GSM phase 2 support or higher. f. Upon reception of the Forward Short Message with MWN information, the IIF shall initiate a Short
Message Delivery Point to Point with Teleservice GHOST /WEMT to the serving ANSI-41
MSC/VLR. The IIF is then acting as an ANSI136 41 Message Center (MC). Inside of this GHOST or WEMT short message is the GSM short message containing the MWN information. g. The serving ANSI-41 MSC/VLR encounters an error and sends the Short Message Delivery Point to Point Return error to the IIF. h. The IIF sends the result of the Forward Short Message to the GSM SMS-GMSC with the proper error code. . i. The SMS-GMSC sends the result of the Forward Mobile Terminating Short Message to the
Service Center. a b c d e f g h i j
Post Ballot Version 160

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

N.S0028
1
2
3
B.1.3.56 4.12.2.7 GSM SMS mapped to ANSI-41 Qualification Directive and to
Registration Notification Return Result
Post Ballot Version 162

N.S0028
1
Vmail
Delivery
GSM
SC
GSM
SMS-
GMSC
GSM
HLR
FORW. MOBILE
TERM SM (MWN)
SEND ROUTING
INFO FOR SM (MWN)
Send Routing
Info for SM
FORW. SHORT
MESSAGE (MWN)
ANSI-41
MSC 2
IIF ANSI-41
MSC 1
Forw . Short Message (error: absent sub.)
Forw . Mobile
Term SM (error)
Report SM (error)
DeliveryStatus
①
QUALDIR
(MWNCOUNT,
MWNTYPE)
(MWN delivered to
Mobile Station) h i j k l a b c d e f g
Time elapsed
REGNOT
Regnot (MWNCOUNT,
MWNTYPE)
(MWN delivered to
Mobile Station) n o
Post Ballot Version 163

N.S0028
GSM
SC
GSM
SMS-
GMSC
GSM
HLR
TDMA
MSC 2
IIF TDMA
MSC 1
Vmail
Delivery
FORW. MOBILE
TERM SM (MWN)
SEND ROUTING
INFO FOR SM (MWN)
Send Routing
Info for SM
FORW. SHORT
MESSAGE (MWN)
①
QUALDIR
(MWNCOUNT,
MWNTYPE)
8
9
10
11
12
13
14
15
4
5
6
7
16
17
18
19
20
21
22
1
2
3
(MWN delivered to
Mobile Station)
Forw. Mobile
Term SM (error)
Forw. Short Message (error: absent sub.)
Report SM (error)
DeliveryStatus
Time elapsed
REGNOT
Regnot(MWNCOUNT,
MWNTYPE) l j m n
(MWN delivered to
Mobile Station) o
Figure 105: GSM SMS mapped to ANSI-41 Qualification Directive and to Registration
Notification Return Result a. The GSM Service Center (SC) receives a voice mail for a specific subscriber. b. The SC sends the Forward Mobile Terminating Short Message with Message Waiting Notification
(MWN) information to the GSM SMS-GMSC c. The GSM SMS-GMSC inquires about the subscriber location by sending the Send Routing
Information For Short Message to the HLR. d. The HLR replies with the Send Routing Information For Short Message result. It is assumed that the native GSM subscriber has already made a registration in the ANSI-41 MSC/VLR. e. The GSM SMS-GMSC originates an SMS with MWN information by sending Forward Short
Message to IIF then acting as a serving GSM MSC/VLR. This requires GSM phase 2 support or higher.
① At this point, the IIF sets the MWN flag. This is an indication that Message Waiting Notification is to be delivered to the Mobile Station. If the handset only supports GSM phase 1, then a pure text SMS shall be delivered to the IIF. The IIF shall then translate it into a CMT or GHOST /WEMT
IS-136ANSI-41 SMS. Note that this then becomes a simple SMS mapping covered in Section
4.11. h i j k a d e f g b c
Post Ballot Version 164

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

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

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

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

N.S0028
MS
GPRS Attach Req
(IMSI)
SGSN
IIF
Authentication Info
Authentication Info Ack
Authentication Req
Authentication Res
Update GPRS Location Req
(IMSI, SGSN Address)
REGNOT
Regnot ack
Insert Sub Data
Insert Sub Data Ack
HLR
GPRS Attach Accept
Update GPRS Location Ack k l
7
8
9
10
11
12
13
14
15
16
17
18
19
20
1
2
3
4
5
6
GSM NETWORK
ANSI-41 NETWORK
Figure 107: GPRS Attach (Option 2: without timer) a. MS performs a GPRS Attach. b. If the Serving GPRS Support Node (SGSN) does not have authentication information in order to perform authentication i.e. authentication triplets, it requests authentication information from the
IIF. The IIF emulates a GSM HLR/AuC in this case supporting GPRS. c. The IIF returns the necessary authentication information, if applicable. d. SGSN initiates authentication towards the MS. e. MS responds to the authentication request. f. SGSN initiates a MAP GPRS location update towards the IIF. The Update GPRS Location
Request contains the IMSI. g. The REGNOT shall contain the MSID (MIN/IMSI), the ESN, the MSCID etc. If SIM-based roaming is authorized, an initially provisioned, fixed ESN for this subscriber shall be passed in the
REGNOT to the subscriber’s HLR. The ANSI-41 HLR records the address of the IIF as the serving ANSI-41 MSC. Although call delivery may not be possible, SMS delivery is made possible by registering the IIF as the ANSI-41 MSC with the ANSI-41 HLR. h. The ANSI-41 HLR sends an acknowledgment to the registration with a regnot. The IIF may ignore the CS-related profile information, since the MS is only GPRS-attached (and not GSM CSattached). Only the provisioned SMS parameters in the regnot (profile) may be mapped and sent to the SGSN in an Insert Subscriber Data message. a b c d e g f h i j
Post Ballot Version 169

N.S0028
8
9
10
11
1
2
3
4
5
6
7 i. The IIF validates whether the GPRS service request is authorized. Since GPRS service is requested, and the subscriber is currently PS-deregistered, it initiates the GSM MAP Insert
Subscriber Data Procedure towards the SGSN after the subscriber has been successfully authorized. This procedure is used to download GPRS subscriber data to the SGSN. Multiple
Insert Subscriber Data transactions may be necessary to complete the transfer of subscriber data to the SGSN. j. The SGSN acknowledges the ISD Operation(s). k. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the IIF returns an acknowledgement to the Update GPRS Location Request. l. The SGSN acknowledges the GPRS Attach request.
Post Ballot Version 170

N.S0028
1 4.13.1.2 GPRS Attach when currently registered in an ANSI-41 network
2
3
4
5
6
If an MS requests GPRS service when currently registered in an ANSI-41 network, the SGSN sends an Update GPRS location update using its IMSI. The IIF acts like a GPRS HLR/AuC and an ANSI-41
VLR in this case. To the subscriber's ANSI-41 HLR, the subscriber becomes registered on the IIF acting as an ANSI-41 MSC. If timer GPRS_LU is used then the message flow is as shown in Figure
108. If timer GPRS_LU is not used then the message flow is as shown in Figure 109.
10
11
12
13
7
8
9
14
15
16
17
MS
SGSN
MSC IIF
HLR
PMSC/
VLR
GPRS Attach Req
(IMSI)
Authentication Info
Authentication Info Ack a b c
Authentication Req
Authentication Res d e
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
GSM NETWORK ANSI-41 NETWORK
Figure 108: GPRS Attach when currently registered in ANSI-41 (Option 1: with timer) a. MS performs a GPRS Attach. b. If the Serving GPRS Support Node (SGSN) does not have authentication information in order to perform authentication i.e. authentication triplets, it requests authentication information from the
IIF. The IIF emulates a GSM HLR/AuC in this case supporting GPRS. c. The IIF returns the necessary authentication information, if applicable. d. SGSN initiates authentication towards the MS. e. MS responds to the authentication request. f. SGSN initiates a MAP GPRS location update towards the IIF. The Update GPRS Location
Request contains the IMSI.
Post Ballot Version 171

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

N.S0028
MS
SGSN
IIF
GPRS Attach Req
(IMSI)
Authentication Info
Authentication Info Ack
Authentication Req
Authentication Res
HLR
Update GPRS Location Req
(IMSI, SGSN
Address)
REGNOT
(MSID, ESN
F
,
MSCID or MSCIN)
REGCAN
MSC/
VLR f g h a b c d e regcan regnot j i
Insert Sub Data k
Insert Sub Data Ack l
Update GPRS Location Ack m
9
10
11
12
13
14
1
2
3
4
5
6
7
8
GPRS Attach Ack
GSM NETWORK
ANSI-41 NETWORK
Figure 109: GPRS Attach when currently registered in ANSI-41 (Option 2: without timer) a. MS performs a GPRS Attach. . n b. If the Serving GPRS Support Node (SGSN) does not have authentication information in order to perform authentication i.e. authentication triplets, it requests authentication information from the
IIF. The IIF emulates a GSM HLR/AuC in this case supporting GPRS. c. The IIF returns the necessary authentication information, if applicable. d. SGSN initiates authentication towards the MS. e. MS responds to the authentication request. f. SGSN initiates a MAP GPRS location update towards the IIF. The Update GPRS Location
Request contains the IMSI. g. The REGNOT shall contain the MSID (MIN/IMSI), the ESN, the MSCID, etc. If SIM-based roaming is authorized, an initially provisioned, fixed ESN for this subscriber shall be passed in the
REGNOT to the subscriber’s HLR. The ANSI-41 HLR records the address of the IIF as the
Post Ballot Version 173

N.S0028
1
2
3
4
5
12
13
14
15
16
17
6
7
8
9
10
11 serving ANSI-41 MSC. Although call delivery may not be possible, SMS delivery is made possible by registering the IIF as the ANSI-41 MSC with the ANSI-41 HLR. h. The ANSI-41 HLR updates its location information and deletes the previous VLR record by sending a REGCANC to the previous MSC/VLR. i. The VLR acknowledges the REGCANC. j. The ANSI-41 HLR sends an acknowledgment to the registration with a regnot. k. The IIF validates whether the GPRS service request is authorized. Since GPRS service is requested, and the MS is currently PS-deregistered, it initiates the GSM MAP Insert Subscriber
Data Procedure towards the SGSN after the subscriber has been successfully authorized. This procedure is used to download GPRS subscriber data to the SGSN. Multiple Insert Subscriber
Data transactions may be necessary to complete the transfer of subscriber data to the SGSN. l. The SGSN acknowledges the ISD Operation(s). m. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the IIF returns an acknowledgement to the Update GPRS Location Request. n. The SGSN acknowledges the GPRS Attach request.
Post Ballot Version 174

N.S0028
1 4.13.1.3 Inter-SGSN routing area update
2
3
4
If an MS requests a GPRS routing area update while registered on a GPRS SGSN only. The message flow is as shown in Figure 110 and 111, depending on whether the timer GPRS_LU is supported on the IIF.
5
6
7
8
9
10
11
12
13
14
15
MS SGSN
IIF inter-SGSN Routing Area Update
(IMSI)
Authentication Info
Authentication Info Ack
Authentication Req
Authentication Res
Update GPRS Location Req (IMSI)
HLR
Cancel Location
Prev
SGSN a b c d e f f
Cancel Location Ack
Insert Sub Data
Insert Sub Data Ack i j j
Update gprs location ack
GPRS_LU
REGNOT
REGCANC inter-SGSN Routing Area Update Accept
GPRS NETWORK l regcanc n
Regnot ack o p
ANSI-41
GPRS NETWORK
Figure 110: Inter-SGSN routing area update (Option 1: with timer) a. MS sends a Routing Area Update request. b. If the Serving GPRS Support Node (SGSN) does not have authentication information in order to perform authentication i.e. authentication triplets, it requests authentication information from the
IIF. The IIF emulates a GSM HLR/AuC in this case supporting GPRS. c. The IIF returns the necessary authentication information, if applicable. d. SGSN initiates authentication towards the MS. e. MS responds to the authentication request. f. SGSN initiates a MAP GPRS location update towards the IIF. The Update GPRS Location
Request contains the IMSI. The IIF starts the GPRS_LU timer. g. The IIF (acting like a GPRS HLR) shall also send a Cancel Location to the previous SGSN.
Post Ballot Version 175

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

N.S0028
1
2
3
4
Related to Figure 110, if a negative regnot response is received from the ANSI-41 HLR, (then as a Network option) the IIF may perform an initiated detach procedure as described in section
4.13.2.6. p. The SGSN acknowledges the GPRS routing area update.
7
8
9
10
5
6
11
12
13
14
15
16
MS SGSN inter-SGSN Routing Area Update
(IMSI)
Authentication Info
Authentication Info Ack
Authentication Req
Authentication Res
Update GPRS Location Req (IMSI)
IIF HLR
Cancel Location
Prev
SGSN
Cancel Location Ack a b c d e f f
REGNOT
REGCANC regcanc
Regnot ack j j i i l l
Insert Sub Data
Insert Sub Data Ack
Update gprs location ack inter-SGSN Routing Area Update Accept
GPRS NETWORK n
ANSI-41 o p
GPRS NETWORK
Figure 111: Inter-SGSN routing area update (Option 2: without timer) a. MS sends a Routing Area Update request. . b. If the Serving GPRS Support Node (SGSN) does not have authentication information in order to perform authentication i.e. authentication triplets, it requests authentication information from the IIF. The IIF emulates a GSM HLR/AuC in this case supporting GPRS. c. The IIF returns the necessary authentication information, if applicable. d. SGSN initiates authentication towards the MS. e. MS responds to the authentication request. f. SGSN initiates a MAP GPRS location update towards the IIF. The Update GPRS Location
Request contains the IMSI. g. The IIF sends a Cancel Location to the previous SGSN. h. IIF shall receive an acknowledgement for the Cancel Location.
Post Ballot Version 177

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

N.S0028
1 4.13.1.4 GPRS- Attach when only GSM CS Attached
2
3
4
If an MS roams while registered in a GSM serving MSC, and the MS requests GPRS attach, the MS performs a GPRS attach and the network responds as shown in Figure 112. Note that the GSM MSC does not update the IIF (emulating the GSM HLR). The serving MSC remains constant.
10
11
12
13
14
5
6
7
8
9
MS
SGSN
MSC IIF
HLR
PMSC/
VLR
GPRS Attach Req
(IMSI)
Authentication Req
Authentication Res
Authentication Info
Authentication Info Ack a b c d e
Update GPRS Location Req (IMSI) f f
REGNOT
REGCANC regcanc
Regnot ack i i j j
Insert Sub Data
Insert Sub Data Ack l l
Update gprs location ack
BSSAP+-Location Update Req n
BSSAP+-Location Update Accept
GPRS Attach Accept
GSM NETWORK
ANSI-41
Figure 112: GPRS Attach when GSM CS Attached. o p
GSM NETWORK a. MS performs a GPRS Attach. b. If the Serving GPRS Support Node (SGSN) does not have authentication information in order to perform authentication i.e. authentication triplets, it requests authentication information from the
IIF. The IIF emulates a GSM HLR/AuC in this case supporting GPRS. c. The IIF returns the necessary authentication information, if applicable. d. SGSN initiates authentication towards the MS. e. MS responds to the authentication request. f. SGSN initiates a MAP GPRS location update towards the IIF. The Update GPRS Location
Request contains the IMSI.
Post Ballot Version 179

N.S0028
5
6
7
8
9
10
11
12
13
1
2
3
4
20
21
22
14
15
16
17
18
19 g. If the IIF implementation supports multiple MSCIDs, then it shall send a REGNOT to the ANSI-41
HLR with the MSCID corresponding to the new SGSN. h. This is a continuation of the optional procedure started in item g. IIF receives REGCANC. i. This is a continuation of the optional procedure started in item g. IIF sends regcanc response. j. This is a continuation of the optional procedure started in item g. IIF receives regnot response.] k. The IIF validates whether the GPRS service request is authorized. Since GPRS service is requested, and the MS is currently PS-deregistered, it initiates the GSM MAP Insert Subscriber
Data Procedure towards the SGSN after the subscriber has been successfully authorized. This procedure is used to download GPRS subscriber data to the SGSN. Multiple Insert Subscriber
Data transactions may be necessary to complete the transfer of subscriber data to the SGSN. l. The SGSN acknowledges the ISD Operation(s). m. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the IIF returns an acknowledgement to the Update GPRS Location Request. n. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
The GSM MSC creates the association with the SGSN by storing the SGSN Number. The MSC does not see a need to notify the IIF (emulating the GSM HLR, since there is no change to the
CS location update parameters). o. The GSM MSC acknowledges the BSSAP+LocationUpdateRequest over the Gs interface by sending the Accept message. p. The SGSN acknowledges the GPRS Attach request from the MS.
Post Ballot Version 180

N.S0028
1
2 4.13.1.5 Combined GSM and GPRS attach when not currently registered
3
4
5
If an MS requests a combined GSM and GPRS attach when not registered in the IIF, then the SGSN first requests a GPRS location update to the IIF (acting as a GPRS HLR) and then a CS location update through the GSM MSC as depicted in Figure 114.
14
15
16
17
18
9
10
11
6
7
8
12
13
MS
SGSN
MSC
IIF
HLR
Combined Attach Req
(IMSI)
Authentication Info
Authentication Info Ack
Authentication Req
Authentication Res
Update GPRS Location Req (IMSI)
Insert Sub Data
Insert Sub Data Ack GPRS_LU g h
Update gprs location ack i
BSSAP+-Location Update Req j
Update Location Req k
REGNOT
Insert Subscriber Data
Regnot ack
Combined Attach Accept
ISD ack
Update Location ack
BSSAP+-Location Update Accept
GSM NETWORK ANSI-41 NETWORK r n o p q l m f c d e a b
Figure 113: Combined GPRS and GSM attach (Option 1: With timer). a. MS performs a GPRS attach. b. If the Serving GPRS Support Node (SGSN) does not have authentication information in order to perform authentication i.e. authentication triplets, it requests authentication information from the
IIF. The IIF emulates a GSM HLR/AuC in this case supporting GPRS. c. The IIF returns the necessary authentication information, if applicable. d. SGSN initiates authentication towards the MS. e. MS responds to the authentication request. f. SGSN initiates a MAP GPRS location update towards the IIF. The Update GPRS Location
Request contains the IMSI. The IIF starts timer GPRS LU. g. The IIF validates whether the GPRS service request is authorized. Since GPRS service is requested, and the MS is currently PS-deregistered, it initiates the GSM MAP Insert Subscriber
Post Ballot Version 181

N.S0028
14
15
16
22
23
24
25
17
18
19
20
21
26
27
28
4
5
6
1
2
3
7
8
9
10
11
12
13
Data Procedure towards the SGSN after the subscriber has been successfully authorized. This procedure is used to download GPRS subscriber data to the SGSN. Multiple Insert Subscriber
Data transactions may be necessary to complete the transfer of subscriber data to the SGSN. h. The SGSN acknowledges the ISD Operation(s). i. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the IIF returns an acknowledgement to the Update GPRS Location Request. j. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
The GSM MSC creates the association with the SGSN by storing the SGSN Number. k. The MSC determines that it needs to notify the IIF (emulating the GSM HLR), since there is a change to the CS location update parameters. The MSC sends the Update Location operation to the IIF (emulating the GSM HLR). The IIF stops timer GPRS LU. l. The IIF shall send a Registration Notification (REGNOT) to the ANSI-41 HLR to indicate the changed location (MSCID associated with the new GSM MSC).
If SIM-based roaming is authorized, an initially provisioned, fixed ESN for this subscriber shall be passed in the REGNOT to the subscriber’s HLR. This ESN may not match the currently validated dynamic ESN for this subscriber, but the HLR shall also accept this fixed ESN for this subscriber. m. The ANSI-41 HLR acknowledges the registration and sends back the subscriber’s information.
This information is for non-GPRS services. n. The IIF sends MAP INSERT SUBSCRIBER DATA message(s) to the GSM MSC providing GSM
CS information based on the contents of the regnot (profile). o. The GSM MSC acknowledges receipt of the Insert Subscriber Data information. p. The IIF acknowledges the completion of the Update Location procedure and sends the Update
Location Acknowledgement to the GSM MSC. q. The GSM MSC acknowledges the BSSAP+LocationUpdateRequest over the Gs interface to the
SGSN by sending the Accept message. r. The SGSN acknowledges the combined GPRS and GSM Attach request from the MS.
Post Ballot Version 182

N.S0028
1
2
3
MS
SGSN
MSC
IIF
HLR
Combined Attach Req
(IMSI) a
Authentication Info b
Authentication Req
Authentication Res
Authentication Info Ack c d e
Update GPRS Location Req (IMSI) f
REGNOT g
Regnot ack h
Insert Sub Data i
Insert Sub Data Ack j
Update gprs location ack k
BSSAP+-Location Update Req l
Update Location Req m
Insert Subscriber Data
ISD ack
Combined Attach Accept
Update Location ack
BSSAP+-Location Update Accept
GSM NETWORK ANSI-41 NETWORK r n o p q
Figure 114: Combined GPRS and GSM attach (Option 2: Without timer and without support for multiple MSCIDs).
Post Ballot Version 183

N.S0028
23
24
25
26
27
28
29
30
17
18
19
20
21
22
31
32
33
34
35
36
37
38
39
40
1
2
3
4
5
6
7
12
13
14
15
16
8
9
10
11 a. MS performs a GPRS attach. b. If the Serving GPRS Support Node (SGSN) does not have authentication information in order to perform authentication i.e. authentication triplets, it requests authentication information from the
IIF. The IIF emulates a GSM HLR/AuC in this case supporting GPRS. c. The IIF returns the necessary authentication information, if applicable. d. SGSN initiates authentication towards the MS. e. MS responds to the authentication request. f. SGSN initiates a MAP GPRS location update towards the IIF. The Update GPRS Location
Request contains the IMSI. g. The IIF shall send a Registration Notification (REGNOT) to the ANSI-41 HLR to indicate the changed location.
If SIM-based roaming is authorized, an initially provisioned, fixed ESN for this subscriber shall be passed in the REGNOT to the subscriber’s HLR. This ESN may not match the currently validated dynamic ESN for this subscriber, but the HLR shall also accept this fixed ESN for this subscriber. h. The ANSI-41 HLR acknowledges the registration and sends back the subscriber’s information in the regnot response. i. The IIF validates whether the GPRS service request is authorized. Since GPRS service is requested, and the MS is currently PS-deregistered, it initiates the GSM MAP Insert Subscriber
Data Procedure towards the SGSN after the subscriber has been successfully authorized. This procedure is used to download GPRS subscriber data to the SGSN. Multiple Insert Subscriber
Data transactions may be necessary to complete the transfer of subscriber data to the SGSN. j. The SGSN acknowledges the ISD Operation(s). k. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the IIF returns an acknowledgement to the Update GPRS Location Request. l. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
The GSM MSC creates the association with the SGSN by storing the SGSN Number. m. The MSC determines that it needs to notify the IIF (emulating the GSM HLR), since there is a change to the CS location update parameters. The MSC sends the Update Location operation to the IIF (emulating the GSM HLR). The IIF does not send a REGNOT in this case, because it does not support multiple MSCIDs. n. The IIF sends MAP INSERT SUBSCRIBER DATA message(s) to the GSM MSC providing GSM
CS information based on the contents of the regnot (profile). o. The GSM MSC acknowledges receipt of the Insert Subscriber Data information. p. The IIF acknowledges the completion of the Update Location procedure and sends the Update
Location Acknowledgement to the GSM MSC. q. The GSM MSC acknowledges the BSSAP+LocationUpdateRequest over the Gs interface to the
SGSN by sending the Accept message. r. The SGSN acknowledges the combined GPRS and GSM Attach request from the MS.
Post Ballot Version 184

1
2
MS
SGSN
Combined Attach Req
(IMSI)
MSC
Authentication Info
Authentication Info Ack
Authentication Req
Authentication Res
Update GPRS Location Req (IMSI)
IIF
HLR
REGNOT
Regnot ack
Insert Sub Data
Insert Sub Data Ack
Update gprs location ack a b f c d e g h j i k
N.S0028
GSM NETWORK
ANSI-41 NETWORK
Post Ballot Version 185

N.S0028
MS
SGSN MSC IIF HLR
1
2
3
BSSAP+-Location Update Req
Update Location Req
REGNOT
REGCANC regcanc regnot
Insert Sub Data
Insert Sub Data Ack
Update Location ack
GPRS Attach Accept/
Routing Area Update
Accept
BSSAP+-Location Update Accept s t n
o
p
q
r u v
l
m
GSM NETWORK
ANSI-41 NETWORK
Figure 115: Combined GPRS and GSM attach (Option 3: IIF supports multiple MSCIDs).
Post Ballot Version 186

N.S0028
12
13
14
15
16
8
9
10
11
17
18
19
20
21
22
1
2
3
4
5
6
7
27
28
29
30
31
23
24
25
26
32
33
34
35
36
37
38
39
40
41
42 a. MS performs a GPRS attach. b. If the Serving GPRS Support Node (SGSN) does not have authentication information in order to perform authentication i.e. authentication triplets, it requests authentication information from the
IIF. The IIF emulates a GSM HLR/AuC in this case supporting GPRS. c. The IIF returns the necessary authentication information, if applicable. d. SGSN initiates authentication towards the MS. e. MS responds to the authentication request. f. SGSN initiates a MAP GPRS location update towards the IIF. The Update GPRS Location
Request contains the IMSI. g. The IIF shall send a Registration Notification (REGNOT) to the ANSI-41 HLR to indicate the changed location (MSCID associated to the new GSM SGSN).
If SIM-based roaming is authorized, an initially provisioned, fixed ESN for this subscriber shall be passed in the REGNOT to the subscriber’s HLR. This ESN may not match the currently validated dynamic ESN for this subscriber, but the HLR shall also accept this fixed ESN for this subscriber. h. The ANSI-41 HLR acknowledges the registration and sends back the subscriber’s information in a regnot response. i. The IIF validates whether the GPRS service request is authorized. Since GPRS service is requested, and the MS is currently PS-deregistered, it initiates the GSM MAP Insert Subscriber
Data Procedure towards the SGSN after the subscriber has been successfully authorized. This procedure is used to download GPRS subscriber data to the SGSN. Multiple Insert Subscriber
Data transactions may be necessary to complete the transfer of subscriber data to the SGSN. j. The SGSN acknowledges the ISD Operation(s). k. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the IIF returns an acknowledgement to the Update GPRS Location Request. l. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
The GSM MSC creates the association with the SGSN by storing the SGSN Number. m. The MSC determines that it needs to notify the IIF (emulating the GSM HLR), since there is a change to the CS location update parameters. The MSC sends the Update Location operation to the IIF (emulating the GSM HLR). n. The IIF shall send a Registration Notification (REGNOT) to the ANSI-41 HLR to indicate the changed location (MSCID associated to the new GSM MSC).
If SIM-based roaming is authorized, an initially provisioned, fixed ESN for this subscriber shall be passed in the REGNOT to the subscriber’s HLR. This ESN may not match the currently validated dynamic ESN for this subscriber, but the HLR shall also accept this fixed ESN for this subscriber. o. IIF receives a REGCANC. The IIF needs to keep both the current MSCID associated to the
SGSN as well as the current MSCID associated to the MSC. The IIF must also keep a record of the last MSCID which was sent to the ANSI-41 HLR to know that is the one stored in the ANSI-41
HLR. p. IIF sends regcanc response. q. The ANSI-41 HLR acknowledges the registration and sends back the subscriber’s information. r. The IIF sends MAP INSERT SUBSCRIBER DATA message(s) to the GSM MSC providing GSM
CS information based on the contents of the regnot (profile).
Post Ballot Version 187

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

N.S0028
1 4.13.1.6 Combined Inter-SGSN Routeing Area/Location Area Update
2
3
4
5
If an MS requests a combined routeing area update when previously registered on a different SGSN and GSM MSC, then the SGSN first requests a GPRS location update to the IIF (acting as a GPRS
HLR) and then a CS location update.
MS SGSN
MSC inter-SGSN Routing Area Update
(IMSI)
Authentication Info
Authentication Info Ack
Authentication Req
Authentication Res
Update GPRS Location Req (IMSI)
IIF
HLR
Cancel Location
Prev
SGSN
PMSC/
VLR a b c d e f
Cancel Location Ack
REGNOT
REGCANC regcanck
Regnot ack j j i i l l
Insert Sub Data
Insert Sub Data Ack
Update gprs location ack
GSM NETWORK n o
ANSI-41
GSM NETWORK
Post Ballot Version 189

N.S0028
MS
SGSN
MSC
BSSAP+-Location Update Req
IIF HLR
Update Location Req
Cancel Location
Prev
SGSN
PMSC/
VLR
Cancel Location Ack p q r s
REGNOT
Insert Sub Data
Insert Sub Data Ack
Update Location ack
GPRS Attach Accept/
Routing Area Update
Accept
BSSAP+-Location Update Accept
REGCANC regcanc regnot y z t u v w x aa bb
10
11
12
13
14
15
8
9
16
1
2
3
4
5
6
7
GSM NETWORK
ANSI-41
GSM NETWORK
Figure 116: Combined Inter-SGSN RA/LA update a. MS sends a Routeing Area Update request b. If the Serving GPRS Support Node (SGSN) does not have authentication information in order to perform authentication i.e. authentication triplets, it requests authentication information from the
IIF. The IIF emulates a GSM HLR/AuC in this case supporting GPRS. c. The IIF returns the necessary authentication information, if applicable. d. SGSN initiates authentication towards the MS. e. MS responds to the authentication request. f. SGSN initiates a MAP GPRS location update towards the IIF. The Update GPRS Location
Request contains the IMSI. g. In the case of a combined attach when registered on a different MSC and SGSN, and in the case of a combined inter-SGSN routing area update case when previously registered on a different
MSC and SGSN, the IIF (acting like a GPRS HLR) shall also send a Cancel Location to the previous SGSN h. IIF shall receive an acknowledgement for the Cancel Location.
Post Ballot Version 190

N.S0028
22
23
24
25
26
27
28
29
30
14
15
16
17
18
19
20
21
36
37
38
39
31
32
33
34
35
40
41
42
1
2
3
4
5
6
7
8
9
10
11
12
13 i. If the IIF implementation supports multiple MSCIDs, then it shall send a REGNOT to the ANSI-41
MSC with the MSCID corresponding to the new SGSN. j. This is a continuation of the optional procedure started in item i. IIF receives REGCANC. The IIF needs to keep both the current MSCID associated to the SGSN as well as the current MSCID associated to the MSC. The IIF must also keep a record of the last MSCID which was sent to the
ANSI-41 HLR to know that is the one stored in the ANSI-41 HLR. k. This is a continuation of the optional procedure started in item i. IIF sends regcanc response. l. This is a continuation of the optional procedure started in item i. IIF receives regnot response. m. The IIF validates whether the GPRS service request is authorized. Since GPRS service is requested, and the MS is currently PS-deregistered, it initiates the GSM MAP Insert Subscriber
Data Procedure towards the SGSN after the subscriber has been successfully authorized. This procedure is used to download GPRS subscriber data to the SGSN. Multiple Insert Subscriber
Data transactions may be necessary to complete the transfer of subscriber data to the SGSN. n. The SGSN acknowledges the ISD Operation(s). o. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the IIF returns an acknowledgement to the Update GPRS Location Request. p. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
The GSM MSC creates the association with the SGSN by storing the SGSN Number. q. The MSC determines that it needs to notify the IIF (emulating the GSM HLR), since there is a change to the CS location update parameters, so the IIF sends the Update Location operation to the IIF (emulating the GSM HLR). r. The IIF sends a Cancel Location to the previous GSM MSC/VLR if a change in MSC has been detected. s. The IIF receives the Cancel Location acknowledgement. t. If the IIF implementation supports multiple IIF MSCIDs, then it shall send a Registration
Notification (REGNOT) to the ANSI-41 HLR to indicate the changed location (MSCID associated to the new GSM MSC).
If SIM-based roaming is authorized, an initially provisioned, fixed ESN for this subscriber shall be passed in the REGNOT to the subscriber’s HLR. This ESN may not match the currently validated dynamic ESN for this subscriber, but the HLR shall also accept this fixed ESN for this subscriber. u. This is a continuation of the optional procedure started in item t. The IIF receives a REGCANC if the MSCID just sent in item (t) is a different one than stored in the ANSI-41 HLR. IIF receives
REGCANC. The IIF needs to keep both the current MSCID associated to the SGSN as well as the current MSCID associated to the MSC. The IIF must also keep a record of the last MSCID which was sent to the ANSI-41 HLR to know that is the one stored in the ANSI-41 HLR. v. This is a continuation of the optional procedure started in item t. The IIF acknowledges the regcanc. w. This is a continuation of the optional procedure started in item t. The IIF receives the regnot response with the subscriber’s information. This information is for non-GPRS services. x. The IIF sends MAP INSERT SUBSCRIBER DATA message(s) to the GSM MSC providing GSM
CS information based on the contents of the regnot (profile). y. The GSM MSC acknowledges receipt of the Insert Subscriber Data information.
Post Ballot Version 191

N.S0028
1
2
3
4
5
6
7
8 z. The IIF acknowledges the completion of the Update Location procedure and sends the Update
Location Acknowledgement to the GSM MSC. aa. The GSM MSC acknowledges the BSSAP+LocationUpdateRequest over the Gs interface to the
SGSN by sending the Accept message. bb. The SGSN acknowledges the GPRS Attach request from the MS.
Post Ballot Version 192

N.S0028
1
2
4.13.1.7 Inter-SGSN routing area update when GSM CS and GPRS attached (GSM MSC remains constant)
3
4
5
6
7
An MS request a GPRS routing area update while registered in a GSM serving MSC and GPRS attached. In this case, the change of routing areas is within one Location area (and the MSC remains constant) as shown in Figure 118. Note that the GSM MSC does not update the IIF (emulating the
GSM HLR).
Post Ballot Version 193

N.S0028
1
MS
SGSN
MSC IIF inter-SGSN Routing Area Update
(IMSI)
Authentication Info
Authentication Info Ack
Authentication Req
Authentication Res
Update GPRS Location Req (IMSI)
HLR Prev
SGSN
Cancel Location
Cancel Location Ack
REGNOT
REGCANC regcanc
Regnot ack
Insert Sub Data
Insert Sub Data Ack
Update gprs location ack
GSM NETWORK j i l n o
ANSI-41
GSM NETWORK a b c d e f f
MS
Routing Area Update
Accept
SGSN
MSC
BSSAP+-Location Update Req
IIF
BSSAP+-Location Update Accept
GSM NETWORK
HLR Prev
SGSN p q
ANSI-41 r
GSM NETWORK
2
3
Figure: 117: Inter-SGSN routing area update when GSM CS and GPRS Attached (MSC remains constant)
Post Ballot Version 194

N.S0028
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
17
18
19
20
21
12
13
14
15
16
1
2
3
4
5
6
7
8
9
10
11 a. MS sends a Routing Area Update request. b. If the Serving GPRS Support Node (SGSN) does not have authentication information in order to perform authentication i.e. authentication triplets, it requests authentication information from the
IIF. The IIF emulates a GSM HLR/AuC in this case supporting GPRS. c. The IIF returns the necessary authentication information, if applicable. d. SGSN initiates authentication towards the MS. e. MS responds to the authentication request. f. SGSN initiates a MAP GPRS location update towards the IIF. The Update GPRS Location
Request contains the IMSI. g. The IIF (acting like a GPRS HLR) shall send a Cancel Location to the previous SGSN h. IIF shall receive an acknowledgement for the Cancel Location. i. If the IIF implementation supports multiple MSCIDs, then it shall send a REGNOT to the ANSI-41
MSC with the MSCID corresponding to the new SGSN. The IIF shall correlate that MSCID with the GSM MSCID when receiving mobile terminated SMS messages (so that the IIF can deliver them to the MSC). j. This is a continuation of the optional procedure started in item i. IIF receives REGCANC. The IIF needs to keep both the current MSCID associated to the SGSN as well as the current MSCID associated to the MSC. The IIF must also keep a record of the last MSCID which was sent to the
ANSI-41 HLR to know that is the one stored in the ANSI-41 HLR. k. This is a continuation of the optional procedure started in item i. IIF sends regcanc response. l. This is a continuation of the optional procedure started in item i. IIF receives regnot response. m. The IIF validates whether the GPRS service request is authorized. Since GPRS service is requested, it initiates the GSM MAP Insert Subscriber Data Procedure towards the SGSN after the subscriber has been successfully authorized. This procedure is used to download GPRS subscriber data to the SGSN. Multiple Insert Subscriber Data transactions may be necessary to complete the transfer of subscriber data to the SGSN. n. The SGSN acknowledges the ISD Operation(s). o. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the IIF returns an acknowledgement to the Update GPRS Location Request. p. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface. q. The MSC determines that it does not need to notify the IIF (emulating the GSM HLR), since there is no change to the CS location update parameters, so the IIF does not send the Update Location operation to the IIF (emulating the GSM HLR). The GSM MSC acknowledges the
BSSAP+LocationUpdateRequest over the Gs interface to the SGSN by sending the Accept message. r. The SGSN acknowledges the Routing Area Update request from the MS.
38
Post Ballot Version 195

N.S0028
1 4.13.1.8 Combined Attach When Currently Registered in an ANSI-41 MSC
2
3
4
This scenario describes the case where a mobile that is currently registered in an ANSI-41 MSC performs a combined attach for both GPRS and non-GPRS services.
Post Ballot Version 196

1
N.S0028
MS
GPRS Attach Req
(IMSI)
SGSN
MSC
Authentication Info
Authentication Info Ack
Authentication Req
Authentication Res
IIF
Update GPRS Location Req (IMSI)
HLR
Insert Sub Data
Insert Sub Data Ack
Update gprs location ack
GPRS_LU
BSSAP+-Location Update Req
Update Location Req
REGNOT
GSM NETWORK
REGCANC regcanc
ANSI-41 l n
ANSI-41
PMSC/
VLR a b c d e f f j j i i
Post Ballot Version 197

N.S0028
MS
SGSN
MSC
Insert Sub Data
Insert Sub Data Ack
Update Locationack
BSSAP+-Location Update Accept
IIF HLR
Regnot ack
GPRS Attach Accept o p q r s t
GSM NETWORK ANSI-41 NETWORK
1
2
3
4
Figure 118: Combined Attach when registered on a ANSI-41 MSC (Option 1: With timer)
Post Ballot Version 198

N.S0028
16
17
18
19
20
9
10
11
12
13
14
15
29
30
31
32
33
34
35
21
22
23
24
25
26
27
28
36
37
38
39
40
41
1
2
3
4
5
6
7
8 a. MS performs a GPRS Attach. b. If the Serving GPRS Support Node (SGSN) does not have authentication information in order to perform authentication i.e. authentication triplets, it requests authentication information from the
IIF. The IIF emulates a GSM HLR/AuC in this case supporting GPRS. c. The IIF returns the necessary authentication information, if applicable. d. SGSN initiates authentication towards the MS. e. MS responds to the authentication request. f. SGSN initiates a MAP GPRS location update towards the IIF. The Update GPRS Location
Request contains the IMSI. The IIF starts timer GPRS LU. g. The IIF validates whether the GPRS service request is authorized. Since GPRS service is requested, and the MS is currently PS-deregistered, it initiates the GSM MAP Insert Subscriber
Data Procedure towards the SGSN after the subscriber has been successfully authorized. This procedure is used to download GPRS subscriber data to the SGSN. Multiple Insert Subscriber
Data transactions may be necessary to complete the transfer of subscriber data to the SGSN. h. The SGSN acknowledges the ISD Operation(s). i. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the IIF returns an acknowledgement to the Update GPRS Location Request. j. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
The GSM MSC creates the association with the SGSN by storing the SGSN Number. k. The MSC determines that it needs to notify the IIF (emulating the GSM HLR), since there is a change to the CS location update parameters. The MSC sends the Update Location operation to the IIF (emulating the GSM HLR). The IIF stops timer GPRS LU. l. The IIF shall send a Registration Notification (REGNOT) to the ANSI-41 HLR to indicate the changed location (MSCID associated with the new GSM MSC).
If SIM-based roaming is authorized, an initially provisioned, fixed ESN for this subscriber shall be passed in the REGNOT to the subscriber’s HLR. This ESN may not match the currently validated dynamic ESN for this subscriber, but the HLR shall also accept this fixed ESN for this subscriber. m. The HLR updates its location information and deletes the previous VLR record by sending a
REGCANC to the previous MSC/VLR. n. The VLR acknowledges the REGCANC. o. The ANSI-41 HLR acknowledges the registration and sends back the subscriber’s information.
This information is for non-GPRS services p. The IIF sends MAP INSERT SUBSCRIBER DATA message(s) to the GSM MSC providing GSM
CS information based on the contents of the regnot (profile). q. The GSM MSC acknowledges receipt of the Insert Subscriber Data information. r. The IIF acknowledges the completion of the Update Location procedure and sends the Update
Location Acknowledgement to the GSM MSC. s. The GSM MSC acknowledges the BSSAP+LocationUpdateRequest over the Gs interface to the
SGSN by sending the Accept message. t. The SGSN acknowledges the combined GPRS and GSM attach request from the MS.
Post Ballot Version 199

1
N.S0028
Post Ballot Version 200

1
N.S0028
MS
SGSN
MSC
GPRS Attach Req (IMSI)
Authentication Info
Authentication Info Ack
Authentication Req
Authentication Res
IIF
Update GPRS Location Req (IMSI)
HLR
REGNOT
REGCANC regcanc
PMSC/
VLR
Regnot ack j j i i a b c d e f f
Insert Sub Data
Insert Sub Data Ack l l
Update gprs location ack
GSM NETWORK
ANSI-41 NETWORK
Post Ballot Version 201

N.S0028
MS
SGSN MSC IIF
HLR
PMSC/
VLR
GPRS Attach Accept
BSSAP+-Location Update Req
Update Location Req
REGNOT
REGCANC regcanc regnot
Insert Sub Data
Insert Sub Data Ack
Update Location ack
BSSAP+-Location Update Accept
n
o u v p
q
r
s
t w x
1
2
GSM NETWORK
ANSI-41 NETWORK
Figure 119: Combined attach when registered on a ANSI-41 MSC (Option 2: without timer )
Post Ballot Version 202

N.S0028
1
8
9
10
11
12
13
14
15
16
2
3
4
5
6
7
17
18
19
20
21
22
23
24
25
26
27
28
34
35
36
37
38
39
40
41
29
30
31
32
33 a. MS performs a GPRS attach. b. If the Serving GPRS Support Node (SGSN) does not have authentication information in order to perform authentication i.e. authentication triplets, it requests authentication information from the IIF. The IIF emulates a GSM HLR/AuC in this case supporting GPRS. c. The IIF returns the necessary authentication information, if applicable. d. SGSN initiates authentication towards the MS. e. MS responds to the authentication request. f. SGSN initiates a MAP GPRS location update towards the IIF. The Update GPRS Location
Request contains the IMSI. g. The IIF shall send a Registration Notification (REGNOT) to the ANSI-41 HLR to indicate the changed location.
If SIM-based roaming is authorized, an initially provisioned, fixed ESN for this subscriber shall be passed in the REGNOT to the subscriber’s HLR. This ESN may not match the currently validated dynamic ESN for this subscriber, but the HLR shall also accept this fixed ESN for this subscriber. h. ANSI-41 HLR sends a REGCANC to the ANSI-41 MSC on which the MS was previously registered. i. ANSI-41 MSC sends regcanc response. j. The ANSI-41 HLR acknowledges the registration and sends back the subscriber’s information in a regnot response. k. The IIF validates whether the GPRS service request is authorized. Since GPRS service is requested, and the MS is currently PS-deregistered, it initiates the GSM MAP Insert
Subscriber Data Procedure towards the SGSN after the subscriber has been successfully authorized. This procedure is used to download GPRS subscriber data to the SGSN. Multiple
Insert Subscriber Data transactions may be necessary to complete the transfer of subscriber data to the SGSN. l. The SGSN acknowledges the ISD Operation(s). m. Once the IIF has received an acknowledgement to the Insert Subscriber Data operation, the
IIF returns an acknowledgement to the Update GPRS Location Request. n. The SGSN sends a BSSAP+LocationUpdateRequest to the GSM MSC over the Gs interface.
The GSM MSC creates the association with the SGSN by storing the SGSN Number (e.g. for later CS paging over the Gs interface upon a call delivery attempt). o. The MSC determines that it needs to notify the IIF (emulating the GSM HLR), since there is a change to the CS location update parameters. The MSC sends the Update Location operation to the IIF (emulating the GSM HLR). p. If the IIF implementation supports multiple MSCIDs, then it shall send a Registration
Notification (REGNOT) to the ANSI-41 HLR to indicate the changed location (MSCID associated to the new GSM MSC).
If SIM-based roaming is authorized, an initially provisioned, fixed ESN for this subscriber shall be passed in the REGNOT to the subscriber’s HLR. This ESN may not match the currently
Post Ballot Version 203

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

N.S0028
8
9
10
11
12
13
14
15
16
17
18
19
20
21
1
2
3
4
5
6
7
22
23
24
25
26
27
28
29
30
31
32
33
34
4.13.1.9 Authentication Failure at the IIF
In any of the scenarios shown previously in 4.13.1 (assuming authentication is performed), authentication may fail at the IIF.
In the event that authentication fails at the IIF (emulating a GSM HLR), it shall send a response to the
SGSN indicating the reason for failure.
Note: The ANSI-41 HLR is not informed about a registration attempt if authentication fails at the IIF.
4.13.1.10 Registration Failure at the ANSI-41HLR
In any of the scenarios shown previously in 4.13.1 where the ANSI-41 HLR is informed about the registration attempt (assuming authentication is successful or not performed), the registration procedure may fail.
In the event that the ANSI-41 HLR denies the registration attempt, it shall send a regnot to the IIF indicating the reason for failure. If the IIF determines that the MS is already registered in an SGSN, it shall send a Cancel Location to the SGSN. Otherwise, the IIF sends an update GPRS location response indicating the reason for failure.
4.13.2.1
GSM CS (IMSI) Detach while GPRS and GSM CS Attached
A GPRS mobile attached for both GPRS and non-GPRS services can request a detach for circuit services (IMSI detach). The IIF is not notified about the MS initiated detachment and hence the ANSI-
41 HLR is not informed.
4.13.2.2 GPRS Detach While Attached for Both GPRS and GSM CS Services
A GPRS mobile attached for both GPRS and non-GPRS services can request a GPRS detach. The
IIF is not notified about the MS initiated detachment and hence the ANSI-41 HLR is not informed.
4.13.2.3 GPRS Detach While Attached for GPRS Services Only
In GPRS, the GPRS HLR is not notified when a GPRS subscriber performs a GPRS detach. Hence, the IIF (which is emulating the GPRS HLR) shall not be notified of the GPRS detach. In this case, a
GPRS subscriber performs a Detach request that is handled by the SGSN and GGSN to remove MM and PDP contexts. There is no interworking with circuit services.
4.13.2.4 Combined GPRS Detach and GSM CS (IMSI) Detach
A GPRS mobile attached for both GPRS and non-GPRS services can request a combined detach from GPRS and non-GPRS services. The IIF is not notified about the MS initiated detachment and hence the ANSI-41 HLR is not informed.
Post Ballot Version 205

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

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

N.S0028
1
2
3
4
4.13.2.6 IIF - Initiated Detach
The IIF initiated detach procedure is initiated by the IIF. The procedure results in the removal of a subscribers PDP contexts at the SGSN.
Cancel Location
Detach Request
Delete PDP Context Request
Delete PDP Context Response
GPRS Detach Indication
Detach Accept
Cancel Location Ack
5
11
12
13
14
15
16
6
7
8
9
10
17
18
19
20
21
22
23
24
25
Figure 121: IIF - Initiated Detach a. The IIF requests deletion of a subscribers PDP contexts from the SGSN by sending a Cancel
Location (IMSI, Cancellation Type) to the SGSN with Cancellation Type set to Subscription
Withdraw.
1 b. The SGSN informs the MS that it has been detached by sending Detach Request (Detach
Type) to the MS. Detach Type shall indicate that the MS is not requested to make a new attach and PDP context activation.
1 c. The active PDP contexts in the GGSNs are de-activated by the SGSN sending Delete PDP
Context Request messages to the GGSNs.
1 d. The GGSNs acknowledge the Delete Request
1 e. If the MS was both IMSI-attached and GPRS–attached the SGSN sends a GPRS Detach
Indication (IMSI) to the VLR.
1 f. The MS sends a Detach Accept to the SGSN any time after step b.
1 g. The SGSN confirms the deletion of the PDP contexts with a Cancel Location Ack (IMSI).
1
Post Ballot Version 208

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

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

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

N.S0028
1
2
4.13.3.1.3 Unsuccessful Mobile Terminated Delivery (Failure at SGSN)
The following scenario applies to short message delivery failure in either CMT or GHOST /WEMT
ANSI-41
GSM
MC HLR IIF SGSN
SMSREQ smsreq
SMDPP smdpp [NAK]
FORWARD SHORT MESSAGE
Forward Short Message b f c d e
3 format.
4
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
5
6
7
8
Figure 124: Unsuccessful Mobile Terminated Delivery (Failure at SGSN) a. The ANSI-41 MC sends a SMSRequest Invoke message to the HLR, including as arguments the
MIN (MSISDN) of the mobile station and SMS Notification Indicator. b. The HLR determines if the message shall be forwarded to the MS and sends a response back in a SMSRequest Return Result, with the SMS_Address set to the IIF address (point code or E.164 address). c. The MC formats a GHOST /WEMT teleservice or a CMT short message and sends it to the IIF in an SMDPP message. d. Upon receipt of the SMDPP message, the IIF builds a FORWARD SHORT MESSAGE, stripping off the GHOST /WEMT teleservice and using the encapsulated GSM SMS transfer PDU, and routes it to the SGSN. If the message received is in the CMT format, the IIF maps this information into a short message in GSM format. e. The SGSN packages the GSM SMS RP-DATA into a CP-DATA message and delivers it across the GSM air interface to the mobile station. The mobile station negatively acknowledges either the CP-DATA message or the RP-DATA message. The SGSN sends a negative acknowledgement Forward Short Message (with appropriate cause value) back to the IIF. f. The IIF maps the received Forward Short Message into a SMDPP Return Result and sends it to the MC. In addition, the IIF sets one of the GSM SMS flags as defined in the GSM 03.40 specification [4] according to the error cause received from the SGSN; that is, the Mobile
Subscriber Not GPRS Reachable Flag (MNRG) shall be set if the error cause is “absent
Post Ballot Version 212

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

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

N.S0028
1
2
3
4
5
6
This section describes the message flows for originating a short message to the subscriber’s home message center when the mobile station is operating GPRS in GSM Foreign Mode. The following scenarios apply to short messages delivered to the MC in either CMT or GHOST /WEMT format.
4.13.4.1 Successful Mobile Originated SMS to MC
GSM
ANSI-41
SGSN HLR IIF MC
FORWARD SHORT MESSAGE
Forward Short Message
SMDPP smdpp [ACK] b c d
7
10
11
12
13
14
15
16
17
18
19
8
9
Figure 127: Successful Mobile Originated Delivery a. The SGSN originates a FORWARD SHORT MESSAGE to the address provided by the MS (i.e.,
IIF), including as arguments the Service Center Address, MSISDN and GSM SMS-SUBMIT PDU. b. Upon receipt of the FORWARD SHORT MESSAGE, the IIF builds an ANSI-41 SMDPP message, encapsulating the GSM SMS transfer PDU in a GHOST /WEMT teleservice, and routes it to the originator’s home MC. The IIF can also map the Forward Short Message into a CMT short message. c. The MC sends a positive acknowledgement SMDPP Return Result to the IIF. d. The IIF maps the received SMDPP Return Result to a Forward Short Message, and sends it to the SGSN.
Post Ballot Version 215

N.S0028
1
2
4.13.4.2 Unsuccessful Mobile Originated (Failure at MC)
GSM
SGSN HLR IIF
ANSI-41
MC
FORWARD SHORT MESSAGE
Forward Short Message
SMDPP smdpp [NAK] b c d
5
6
7
8
9
10
11
12
13
3
4
Figure 128: Unsuccessful Mobile Originated Delivery (Failure at MC) a. The SGSN originates a FORWARD SHORT MESSAGE to the address provided by the MS (i.e.,
IIF), including as arguments the Service Centre Address, MSISDN and GSM SMS-SUBMIT PDU. b. Upon receipt of the FORWARD SHORT MESSAGE, the IIF builds an ANSI-41 SMDPP message encapsulating the GSM SMS transfer PDU in a GHOST /WEMT teleservice, and routes it to the
MC. The IIF can also map the Forward Short Message into a CMT short message. c. The MC sends a negative acknowledgement SMDPP Return Result to the IIF. d. The IIF maps the received SMDPP Return Result to a Forward Short Message with the appropriate cause code value, and sends it to the SGSN.
Post Ballot Version 216

1 4.13.4.3 Unsuccessful Mobile Originated (Failure at IIF)
GSM
SGSN HLR
FORWARD SHORT MESSAGE
Forward Short Message
IIF
ANSI-41
MC
N.S0028 a b
5
6
7
8
9
2
3
4
Figure 129: Unsuccessful Mobile Originated (Failure at IIF) a. The SGSN originates a FORWARD SHORT MESSAGE to the address provided by the MS (i.e.,
IIF), including as arguments the Service Centre Address, MSISDN and GSM SMS-SUBMIT PDU. b. Upon receipt of the FORWARD SHORT MESSAGE, the IIF builds a negative acknowledgement
Forward Short Message and sends it to the SGSN.
10
Post Ballot Version 217

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

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

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

1
2 4.13.5.2 ANSI-41 Qualification Directive mapped to GSM SMS
N.S0028
.............................................................
TDMA
VMS
TDMA
HLR IIF
Vmail
Delivery
“Message Waiting
Notification”
QUALDIR(MWNCOUNT,
MWNTYPE)
① qualdir
FORW. SHORT
MESSAGE (MWN)
GSM
SGSN MS
Forw. Short
Message
SMS Delivery (MWN)
SMS DeliveryAck a b c d e f g h
②
3
21
22
23
24
25
26
15
16
17
18
19
20
10
11
12
13
14
7
8
9
4
5
6
Figure 131: ANSI-41 Qualification Directive mapped to GSM SMS a. The Voice Mail System (VMS) receives a voice mail for a specific subscriber. b. The VMS send the “Message Waiting Notification” (MWN) to the ANSI-41 HLR of the voice mail recipient. Note that the interface between the VMS and the ANSI-41 HLR is not standardized in
ANSI-41 [1]. c. Since the subscriber has a current valid location stored in the HLR, the HLR initiates a
Qualification Directive message with the MWN information to the IIF acting as the serving ANSI-
41 MSC/VLR. The MWN information consists of two parameters:
MessageWaitingNotificationCount (MWNCOUNT) and MessageWaitingNotificationType
(MWNTYPE). For a description of these parameters, refer to the ANSI-41-D specifications, sections 6.5.2.78 and 6.5.2.79 [1].
➀ At this point, the IIF sets the MWN flag. This is an indication that Message Waiting Notification is to be delivered to the Mobile Station. d. The IIF sends the result of the Qualification Directive message to the ANSI-41 HLR. e. The IIF also originates an SMS with MWN information by sending a Forward Short Message to the serving GSM SGSN. The IIF is then acting as a GSM SMS-GMSC. The IIF is to encode the
MWN information in the SMS with three methods, namely, UDH, DCS, and CPHS. Refer to
Volume 3 for the encoding details.
Post Ballot Version 221

N.S0028
5
6
7
8
9
1
2
3
4
10
11
12
13
14
15 f. The serving GSM SGSN sends the short message with the MWN information to the mobile station. g. The mobile station acknowledges the delivery of the short message. h. The serving GSM SGSN sends the result of the Forward Short Message to the IIF.
➁ At this point, the IIF clears the MWN flag. The reception of the Forward Short Message Result without error indicates that the MWN information was delivered successfully to the Mobile Station.
4.13.5.3 Handling at SMS delivery failure at the SGSN or at the Mobile Station
The IIF is to keep a Message Waiting Notification (MWN) flag for each subscriber in its database. In the event of a failure to deliver a short message with MWN to the mobile station, the IIF is to keep the
MWN flag set. Another Forward Short Message with MWN information shall be sent, triggered by the reception of a subsequent GSM Update Location message, a Ready for Short Message, or a Note
MS Present message. This is illustrated in the following diagram.
IIF
GSM
SGSN MS
MWN “Information”
①
FORW. SHORT
MSG (MWN) – V3
SMS Delivery (MWN)
SMS Delivery Error
Error, Abort,
Reject, timeout
Time elapsed
UPDATE GPRS LOCATION
READY FOR SM
(AlertReason) – V3
“Acknowledgement”
FORW. SHORT
MSG (MWN) – V3
SMS Delivery (MWN)
SMS Delivery Ack
Forw. Short
Message
② i j f g h a b c d e k l m n
16
17 Figure 132: Handling at SMS delivery failure at the SGSN or at the MS
Post Ballot Version 222

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

N.S0028
1
2
3
4
5
6
This section describes the scenarios for call delivery to an MS that is roaming in a GPRS network in
GSM foreign mode.
4.13.6.1 Call Delivery Scenarios in GSM Foreign Mode while GSM CS and GPRS Attached
4.13.6.1.1 Call Delivery to ANSI136 41 Subscriber Roaming on a GSM/GPRS Network
MS
Paging Procedure
SUSPEND To
BSS
GSM
SGSN
PAGING-REQ
MSC
PRN prn
IIF
ROUTEREQ routereq
ANSI
HLR
ISUP signaling / SS7
LOCREQ locreq
O-MSC
Incoming call a b d e f c g j i h k
7
8
9
10
11
12
13
14
15
16
17
Figure 133: Call Delivery to ANSI136 41 Subscriber Roaming in GSM/GPRS Network a. The originating ANSI-41 MSC receives an incoming call from the PSTN for a subscriber that is roaming in a GSM/GPRS network. This MS is registered simultaneously with an SGSN and a
GSM MSC/VLR. b. The O-MSC sends a LOCREQ to the ANSI-41 HLR c. The ANSI-41 HLR knows the address of the IIF (acting as an ANSI-41 serving MSC) and sends a
ROUTEREQ to it d. The call may be delivered if the IIF determines that the called MS is registered with on a GSM
MSC/VLR. As such, the IIF (acting as a GSM HLR) sends the serving GSM MSC/VLR a MAP
Provide Roaming Number (PRN).
Post Ballot Version 224

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

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

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

N.S0028
1
2
3
4
5
4.13.6.2 Successful Network-Requested PDP Context Activation Procedure
The network requested PDP Context Activation procedure allows the GGSN to initiate the activation of a PDP context when a data packet arrives for a particular PDP address and no PDP context has been previously established.
PDP PDU
SRI for GPRS
SRI for GPRS Ack
PDU Notification Request
PDU Notification Response
Request PDP context Activation
Activate PDP context Request
Send Auth Info
Send Auth Info Ack
Create PDP Context Request
Create PDP Context Response
Activate PDP context Accept
8
9
10
11
12
13
14
15
16
17
6
7
1 Figure 135: Successful Network Requested PDP context Activation
1 a. When receiving a PDP PDU the GGSN follows the procedures described in GSM 03.60 [10]
1 b. The GGSN may send a Send Routeing Information for GPRS (IMSI) message to the IIF.
1 c. The IIF determines if the request can be served. If the request can be served it returns a Send
Routeing Information for GPRS Ack (IMSI, SGSN Address) to the GGSN. If the request cannot be served it returns a Send Routeing Information for GPRS Ack (IMSI, MAP Error Cause). d. Steps d through l are provided for completeness and are outside the scope of this specification.
Note: Certain security procedures as in step h) may be invoked.
Post Ballot Version 228

N.S0028
1
5
6
7
8
9
10
2
3
4
4.13.6.3 Unsuccessful Network-Requested PDP Context Activation Procedure
If the PDP context requested by the GGSN cannot be established, the IIF in conjunction with the
SGSN and GGSN may perform the Protection and Mobile User Activity Procedures as described in
GSM 03.60 [10]. The IIF acting as a GPRS HLR shall follow the same procedures as the GSM HLR.
GPRS subscriber data shall be provisioned in the IIF (emulating a GPRS HLR) to support GPRS service capability in GSM Foreign mode. The IIF shall store the same subscription information as identified in GSM 03.60 [10].
It may be possible to provision an ANSI136 41 native subscriber with GPRS-only service (and no
GSM CS service)
11
Post Ballot Version 229

N.S0028
1
2
3
4
5
6
7
The following is an example of some of the timers defined in existing ANSI-41 and GSM specifications.
As an example, the GSM timer controlling, the Update Location Request is defined to be in the range
15s to 30s whereas the equivalent ANSI-41 timer controlling the REGNOT is defined to be a default value of 12s.
Post Ballot Version 230

N.S0028
GSM
Operation
LOCATION REGISTRATION PROCEDURES
Timer Value ANSI-41
Operation
15s to 30s REGNOT
Timer Value
12s Update
Location
Request
Insert Sub
Data
15s to 30s
GSM
Operation
Provide
Roaming
Number
CALL DELIVERY PROCEDURES
Timer Value ANSI-41
Operation
15s to 30s ROUTREQ
Timer Value
10s
SUBSCRIBER DATA MANAGEMENT PROCEDURES
GSM
Operation
Timer Value ANSI-41
Operation
Timer Value
15s to 30s REGCANC 6s Cancel
Location
Request
Delete Sub
Data
15s to 30s QUALDIR 6s
SUPPLEMENTARY SERVICE PROCEDURES
Timer Value Timer Value GSM
Operation
REGISTER SS
ERASE SS
ACTIVATE SS
DE-ACTIVATE
SS
15s to 30s
15s to 30s
15s to 30s
15s to 30s
ANSI-41
Operation
FEATREQ 16s
GSM
Operation
Resume Call
Handling
OPTIMAL ROUTING PROCEDURES
Timer Value ANSI-41
Operation
15s to 30s REDREQ
Timer Value
22s
1
2
3
GSM
Operation
Forward SM
SHORT MESSAGE PROCEDURES
Timer Value ANSI-41
Operation
1m to 10m SMDPP
Timer Value
6s
Notes: GSM timer values are defined as a range of values, whereas ANSI-41 defines a default timer value.
4
Post Ballot Version 231

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

N.S0028
1
2
8
9
10
11
12
13
14
15
16
3
4
5
This scenario illustrates the successful authentication of an MS on the initial MS access is a GSM system
ANSI-41 GSM
AC
HLR
IIF
MSC/
VLR
MSC/
VLR
Location area update (IMSI) a
SEND_AUTH_INFO (IMSI) b
AUTHREQ (MSCID, SYSCAP, MSID, ESN, SYSAC) c
AUTHREQ (MSCID, SYSCAP, MSID, ESN, SYSAC) d
ART
Authreq (SSD, ESN)
ART e
Authreq (SSD, ESN)
SEND_AUTH_INFO ack (AuthenticationSetList) g authentication (RAND) h
ASRRT authentication ack (SRES) i
UPDATE LOCATION (IMSI)
ASREPORT (MSCID, MSID, UCHALRPT) j k
ASREPORT (MSCID, MSID, UCHALRPT) l
ASRRT asreport[] m asreport[]
REGNOT [MSCID, TRANSCAP, SYSCAP, MSID, ESN, SYSAC] o
6
7 Figure 136 – Successful Authentication on Initial Access in GSM System a) The MS determines that a new serving system has been entered. The MS registers at the new GSM serving system and provides its IMSI.
b) The GSM serving system sends a SEND_AUTHENTICATION_INFO to the IIF. c) The IIF sends an AUTHREQ to the HLR associated with the MS. The MSCID parameter identifies the
IIF. The SYSCAP parameter is set to indicate GSM system. The ESN parameter is set to a default value. The SYSACCTYPE parameter is set to indicate GSM system access.
Post Ballot Version 233

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

N.S0028
1
2
3
4
This scenario illustrates an authentication failure on the initial MS access is a GSM system.
The GSM system reports the authentication failure to the IIF.
AC
ANSI-41
HLR
IIF
GSM
MSC/
VLR
MSC/
VLR
Location area update (IMSI) a
SEND_AUTH_INFO (IMSI) b
AUTHREQ (MSCID, SYSCAP, MSID, ESN, SYSAC) c
AUTHREQ (MSCID, SYSCAP, MSID, ESN, SYSAC) d
ART
Authreq (SSD, ESN)
ART e
Authreq (SSD, ESN)
SEND_AUTH_INFO ack (AuthenticationSetList) g authentication (RAND) h
ASRRT authentication ack (SRES) i
UPDATE LOCATION (IMSI)
ASREPORT (MSCID, MSID, UCHALRPT) j k
ASREPORT (MSCID, MSID, UCHALRPT) l asreport[DENACC]
ASRRT
ASRRT m asreport[DENACC]
AUTHENTICATION_FAILURE o
5
6
7
Figure 137 - Authentication Failure on Initial Access in GSM System
Post Ballot Version 235

N.S0028
9
10
11
12
13
14
15
16
17
18
19
4
5
6
7
8
1
2
3 a-i. Same as Scenario 5.Y.1, Steps a-i. j) The GSM system compares the response received from the MS with the expected response. In this scenario, the response does equal to the expected response. The GSM system sends an
AUTHENTICATION_FAILURE to the IIF. The subscriber’s IMSI is used to identify the MS. k) The IIF sends an ASREPORT to the HLR associated with the MS. The UCHALRPT parameter is set to indicate Unique Challenge failed. l) The HLR forwards the ASREPORT to the AC. m) The AC includes the DENACC parameter and sends an asreport to the HLR. n) The HLR forwards the asreport to the IIF. The IIF removes the SSD, ESN and other information stored for the MS. o) The IIF sends an AUTHENTICATION_FAILURE ack to the GSM system. p) The GSM system sends a location area update reject to the MS.
Post Ballot Version 236

N.S0028
1
2
3
4
5
6
This scenario illustrates an authentication failure on the initial MS access is a GSM system. The GSM system doe not report the authentication failure to the IIF
AC
ANSI-41
HLR
IIF
GSM
MSC/
VLR
MSC/
VLR
Location area update (IMSI) a
SEND_AUTH_INFO (IMSI) b
AUTHREQ (MSCID, SYSCAP, MSID, ESN, SYSAC) c
AUTHREQ (MSCID, SYSCAP, MSID, ESN, SYSAC) d
ART
Authreq (SSD, ESN)
ART e
Authreq (SSD, ESN)
SEND_AUTH_INFO ack (AuthenticationSetList) g
ASRRT authentication (RAND) timer authentication ack (SRES) h i
Location area update reject j
10
11
12
13
7
8
9
14
15
16
17
18
19 timer expiry
ASREPORT (MSCID, MSID, UCHALRPT) k l
ASREPORT (MSCID, MSID, UCHALRPT) asreport[DENACC]
ASRRT
ASRRT m asreport[DENACC] o
Figure 138 - Authentication Failure on Initial Access in GSM System – Authentication
Failure Message Not Supported a-i. Same as Scenario 5.Y.1, Steps a-i. j) The GSM system compares the response received from the MS with the expected response. In this scenario, the response does equal to the expected response. The GSM system compares the response received from the MS with the expected response. In this scenario, the response does equal to the expected response. The GSM system sends a location area update reject to the MS. k) An IIF timer expires when no message for the MS is received from the GSM system.
Post Ballot Version 237

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

N.S0028
1
2
3
4
5
6
7
8
9
10
11
This scenario illustrates a GSM system requesting addition triplets after the MS is register in the serving GSM system.
ANSI-41 GSM
AC
HLR
IIF
MSC/
VLR
MSC/
VLR
SEND_AUTHENTICATION_INFO (IMSI) a
SEND_AUTH_INFO ack (AuthenticationSetList) b
Figure 139 - GSM System Request for Additional Triplets a) The GSM system determines that additional triplets are required and sends a
SEND_AUTHENTICATION_INFO to the IIF. The IMSI identifies the subscriber. b) The IIF computes one or more groups of triplets and includes them in the response to the GSM system. (Note, the IIF may have pre-computed triplets for the MS that it sends to the GSM system).
Post Ballot Version 239

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

N.S0028
5
6
3
4
1
2
Version Comments Revision Date
0
A
March 2001
May 23, 2001
A
A
A
A
A
July 9, 2001
August 1, 2001
August 14, 2001
August 15, 2001
November 27,
2001 draft
0
2
3
Initial Release J-STD-038
GPRS text added: section 4.6.
Misc. editorial changes.
Editorial changes. Ballot version.
Incorporation of agreed ballot comments
B
B
July 2001
March 2002
3
5
Version 3: Addition of CDMA/GSM two way roaming
Version V&V: Addition of CDMA/GSM two way and one roaming
ii

1
2
3
N.S0028
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
11
12
13
14
1 INTRODUCTION ........................................................................................................................
1
1.1 General...............................................................................................................................................
1
1.2 Purpose...............................................................................................................................................
1
1.3 Scope ..................................................................................................................................................
1
1.4 Organization ......................................................................................................................................
1
15 2 REFERENCES...........................................................................................................................
3
16
17
18
3 DEFINITIONS AND ACRONYMS ...............................................................................................
4
3.1
Definitions ..........................................................................................................................................
4
3.2
Acronyms ...........................................................................................................................................
6
23
24
25
26
27
19
20
21
22
4 MESSAGE MAPPINGS............................................................................................................
10
4.1
Mobility Procedures.........................................................................................................................
10
4.1.1
Location Registration .................................................................................................................
10
4.1.2
Fault Recovery ...........................................................................................................................
23
4.2
Call Handing Procedures.................................................................................................................
26
4.2.1 Automatic Call Delivery.............................................................................................................
26
4.2.2
Invocation of Conditional Call Forwarding in ANSI-41 Foreign Mode ........................................
40
4.2.3
Optimal Routing after Late Call Forwarding ...............................................................................
44
4.3
Supplementary Services Procedures................................................................................................
53 iii

N.S0028
9
10
11
12
5
6
7
8
1
2
3
4
4.3.1
SS Activation and Deactivation...................................................................................................
53
4.3.2
SS Registration and Erasure........................................................................................................
70
4.3.3
Retrieval of Forward-To Number................................................................................................
94
4.3.4 Calling Number / Line Identification Presentation/Restriction .....................................................
98
4.4
O&M Procedures...........................................................................................................................
105
4.4.1
Detailed Procedures..................................................................................................................
105
4.4.2
Mapping of Messages, Parameters & Parameter Values.............................................................
106
4.4.3
Error Handling .........................................................................................................................
126
4.5
Short Message Procedures (ANSI-41 Network) ............................................................................
131
4.5.1
Short Message Service via CMT...............................................................................................
131
4.5.2
Short Message Service via GHOST or WEMT..........................................................................
150
4.5.3
Message Waiting Notification...................................................................................................
161
13
14
15
16
17
18
4.6 GPRS IN GSM FOREIGN MODE........................................................................................
170
4.6.1 Mobility Procedures .................................................................................................................
170
4.6.2 Automatic Call Delivery...........................................................................................................
177
4.6.3
Short Message Procedures for ANSI-41 subscriber ...................................................................
180
4.6.4 Short Message Service via GHOST or WEMT..........................................................................
183
4.6.5 Message Waiting Notification...................................................................................................
184
19
20
21
22
23
24
25
26
27
28
29
30
31
ANNEX A SHORT MESSAGE SERVICE PROCEDURES WITHIN AN ANSI-136 NETWORK ......
186
A.1
CMT to GHOST Delivery..............................................................................................................
186
A.1.1
Detailed Procedures..................................................................................................................
186
A.1.2
Mapping of Messages, Parameters & Parameter Values.............................................................
186
A.1.3
Error Handling .........................................................................................................................
188
A.2
GHOST to CMT Delivery..............................................................................................................
188
A.2.1
Detailed Procedures..................................................................................................................
189
A.2.2
Mapping of Messages, Parameters & Parameter Values.............................................................
190
A.2.3
Error Handling .........................................................................................................................
194
A.3
Callback Number ...........................................................................................................................
195
A.3.1
Detailed Procedures..................................................................................................................
195
A.3.2
Message Mapping, Parameters and Parameters Values ..............................................................
196
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
5
6
7
3
4
1 INTRODUCTION ........................................................................................................................1
1.1 General ..................................................................................................................................1
1.2 Purpose .................................................................................................................................1
1.3 Scope.....................................................................................................................................1
1.4 Organization..........................................................................................................................1
8 2 REFERENCES...........................................................................................................................3
9
10
11
3 DEFINITIONS AND ACRONYMS ...............................................................................................4
3.1
Definitions .............................................................................................................................4
3.2
Acronyms ..............................................................................................................................6
12
20
21
22
23
24
25
26
27
28
13
14
15
16
17
18
19
29
30
31
32
4 MESSAGE MAPPINGS..............................................................................................................9
4.1
Mobility Procedures..............................................................................................................9
4.1.1
Location Registration........................................................................................................9
4.1.2
Fault Recovery...............................................................................................................22
4.2
Call Handing Procedures....................................................................................................25
4.2.1 Automatic Call Delivery ..................................................................................................25
4.2.2
Invocation of Conditional Call Forwarding in ANSI-41 Foreign Mode...............................38
4.2.3
Optimal Routing after Late Call Forwarding ....................................................................42
4.3
Supplementary Services Procedures.................................................................................51
4.3.1
SS Activation and Deactivation.......................................................................................51
4.3.2
SS Registration and Erasure ..........................................................................................68
4.3.3
Retrieval of Forward-To Number ....................................................................................92
4.3.4 Calling Number / Line Identification Presentation/Restriction...........................................96
4.4
O&M Procedures ............................................................................................................... 103
4.4.1
Detailed Procedures..................................................................................................... 103
4.4.2
Mapping of Messages, Parameters & Parameter Values .............................................. 104
4.4.3
Error Handling.............................................................................................................. 123
4.5
Short Message Procedures (ANSI-136 Network) ............................................................. 128
4.5.1
Short Message Service via CMT .................................................................................. 128
4.5.2
Short Message Service via GHOST.............................................................................. 145
4.5.3
Message Waiting Notification ....................................................................................... 156
33
34
4.6 GPRS IN GSM FOREIGN MODE........................................................................................ 165
4.6.1 Mobility Procedures...................................................................................................... 165 v

N.S0028
1
2
3
4
4.6.2 Automatic Call Delivery ................................................................................................ 172
4.6.3
Short Message Procedures for ANSI-136 subscriber .................................................... 175
4.6.4 Short Message Service via GHOST.............................................................................. 178
4.6.5 Message Waiting Notification ....................................................................................... 179
10
11
12
13
14
15
16
17
5
6
7
8
9
ANNEX A SHORT MESSAGE SERVICE PROCEDURES WITHIN AN ANSI-136 NETWORK ...... 181
A.1
CMT to GHOST Delivery.................................................................................................... 181
A.1.1
Detailed Procedures..................................................................................................... 181
A.1.2
Mapping of Messages, Parameters & Parameter Values .............................................. 181
A.1.3
Error Handling.............................................................................................................. 183
A.2
GHOST to CMT Delivery.................................................................................................... 183
A.2.1
Detailed Procedures..................................................................................................... 184
A.2.2
Mapping of Messages, Parameters & Parameter Values .............................................. 185
A.2.3
Error Handling.............................................................................................................. 189
A.3
Callback Number............................................................................................................... 190
A.3.1
Detailed Procedures..................................................................................................... 190
A.3.2
Message Mapping, Parameters and Parameters Values............................................... 191
A.3.3
Error Handling.............................................................................................................. 191
18
19
20
ANNEX B CAUSE CODE MAPPING AT NON-IIF NODES............................................................ 192
vi

N.S0028
1
16
17
18
19
20
21
22
23
24
25
26
12
13
14
15
27
28
29
10
11
7
8
9
5
6
2
3
4
Table 1: Location Updating in GSM Foreign Mode Message Mapping ........................................
13
Table 2: Location Updating in ANSI-41 Foreign Mode Message Mapping...................................
14
Table 3: MS Purging Message Mapping.....................................................................................
14
Table 4: Location Cancellation Message Mapping......................................................................
14
Table 5: UPDATE_LOCATION_REQUEST ↔ REGNOT Parameter Mapping............................
14
Table 6: INSERT_SUBSCRIBER_DATA_REQUEST ↔ regnot Parameter Mapping ..................
16
Table 7: UPDATE LOCATION RESPONSE ↔ regnot Parameter Mapping ................................
17
Table 8: MS_PURGE_REQUEST ↔ MS INACTIVE Parameter Mapping...................................
17
Table 9: CANCEL_LOCATION_REQUEST ↔ REGCANC Parameter Mapping .........................
18
Table 10: UPDATE_LOCATION_RESPONSE to regnot Error Mapping .....................................
21
Table 11: regnot return errors to UPDATE_LOCATION_RESPONSE Error Mapping .................
22
Table 12 Fault Recovery Message Mapping ..............................................................................
24
Table 13: GSM RESET ↔ ANSI UNRELDIR Parameter Mapping ..............................................
24
Table 14: Automatic Call Delivery Message Mapping.................................................................
28
Table 15: ROUTREQ ↔ PROVIDE_ROAMING_NUMBER_REQUEST Parameter
Mapping ...................................................................................................................
29
Table 16: Provide Roaming Number Response ↔ Routreq Return Result Parameter
Mapping ...................................................................................................................
31
Table 17: PROVIDE_ROAMING_NUMBER_RESPONSE to Routreq Return Error Mapping
(ANSI-41Foreign Mode) ...........................................................................................
31
Table 18: Routreq Return Error to Provide Roaming Number Response Error Mapping
(GSM Foreign mode)................................................................................................
32
Table 19: Provide Roaming Number Request default parameter ................................................
33
Table 20: RoutingRequest Return Result default parameters .....................................................
34
Table 21: Routing Request Invoke default parameter.................................................................
35
Table 22: PRN response User Error to routreq Return Error Mapping .......................................
38 vii

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

N.S0028
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
1
2
3
7
8
9
10
11
12
4
5
6
13
14
15
Table 49: Activate/Deactivate SS Response default parameter values .......................................
61
Table 50: Feature Request Invoke to Activate/Deactivate SS Request Parameter Mapping........
62
Table 51: Activate/Deactivate SS Request default parameter.....................................................
62
Table 52: FeatureRequest Return Result default parameter.......................................................
63
Table 53: FeatureRequest Return Result to User Error in the Activate/Deactivate SS
Response Error Mapping..........................................................................................
66
Table 54: FeatureRequest Return Error to Activate/Deactivate SS Response Error
Mapping ...................................................................................................................
66
Table 55: Activate/Deactivate SS Response User Error to FeatureRequest Return Result
Mapping ...................................................................................................................
67
Table 56: Activate/Deactivate SS Response User Error to FeatureRequest Return Error
Mapping ...................................................................................................................
68
Table 57: Activate/Deactivate SS Response Provider Error to Feature Request Return
Error Mapping ..........................................................................................................
69
Table 58: Supplementary Service Registration Message Mapping .............................................
72
Table 59: Register SS Request ↔ FEATREQ parameter mapping.............................................
73
Table 60: Register SS Response ↔ Feature Request Return Result Parameter Mapping ..........
74
Table 61: Register SS Response ↔ Return Error Parameter Mapping .......................................
75
Table 62: Register SS Request to Feature Request Invoke parameter mapping.........................
76
Table 63: FEATREQ default parameter......................................................................................
77
Table 64: Register SS Response default parameter values........................................................
78
Table 65: FEATREQ to Register SS Request parameter mapping .............................................
79
Table 66: Register SS Request default parameter......................................................................
79
Table 67: FeatureRequest Return Result default parameter.......................................................
80
Table 68: FeatureRequest Return Result to User Error in the Register SS Response mapping ...................................................................................................................
82
Table 69: Supplementary Service Erasure Message Mapping ....................................................
85
Table 70: Erase SS Request ↔ FEATREQ parameter mapping.................................................
85
Table 71: Erase SS Response ↔ Feature Request Return Result parameter mapping ..............
86
Table 72: Erase SS Response ↔ Return Error parameter mapping ...........................................
87
Table 73: Erase SS Request to FEATREQ parameter mapping .................................................
88 ix

N.S0028
20
21
22
23
24
25
16
17
18
19
8
9
10
11
12
13
14
15
26
27
28
29
30
31
32
1
2
3
6
7
4
5
Table 74: Feature Request Invoke default parameter.................................................................
89
Table 75: Erase SS Response default parameter values............................................................
90
Table 76: FEATREQ to Erase SS Request parameter mapping ................................................
91
Table 77: Erase SS Request default parameter .........................................................................
91
Table 78: FeatureRequest Return Result default parameter.......................................................
92
Table 79: FeatureRequest Return Result to Register SS Response User Error ..........................
93
Table 80: Retrieval of Forward-to-Number in GSM Foreign Mode ..............................................
95
Table 81: TransferToNumberRequest Return Result to Insert Subscriber Data parameter mapping ...................................................................................................................
96
Table 82: TransferToNumberRequest Return Result to Insert Subscriber Data Request value mapping..........................................................................................................
97
Table 83: Routing Request ↔ Provide Roaming Number Request (Network Provided number) Parmater Mapping......................................................................................
99
Table 84: Routing Request ↔ Provide Roaming Number Request (User Provided number)
Parameter Mapping................................................................................................
100
Table 85: Routing Request ↔ Provide Roaming Number Request (Two calling party numbers) Parameter Mapping ................................................................................
101
Table 86: Routing Request ↔ Provide Roaming Number Request(Caller Id Restricted)
Parameter Mapping................................................................................................
103
Table 87: Cancel_Location_Request ↔ REGCAN (Subscriber Deletion) Mapping ...................
107
Table 88: Mapping of GSM MAP Messages ↔ ANSI MAP Messages (Subscriber Data
Modification)...........................................................................................................
107
Table 89: Delete_Subscriber_Data ↔ Qualdir Mapping (Subscriber Data Modification)............
107
Table 90: CANCEL_LOCATION_REQUEST ↔ REGCANC Parameter Mapping .....................
108
Table 91: INSERT_SUBSCRIBER_DATA_REQUEST ↔ QUALDIR Parameter Mapping.........
108
Table 92: INSERT_SUBSCRIBER_DATA_REQUEST ↔ profile ‘macro’ Mapping....................
109
Table 93: Forwarding Information List to Calling Features Indicator Parameter Mapping ..........
112
Table 94: Regional Subscription Data to Geographic Authorization Parameter Mapping...........
114
Table 95: Call Barring Information List to Origination Indicator Parameter Mapping ..................
114
Table 96: SSData List to Calling Features Indicator Parameter Mapping ..................................
117
Table 97: Operator Determined Barring general data to Origination Indicator
Parameter Mapping................................................................................................
119
x

N.S0028
14
15
16
17
18
19
7
8
9
10
1
2
3
4
5
6
11
12
13
25
26
27
28
29
30
20
21
22
23
24
31
32
33
34
35
36
Table 98: Operator Determined Barring HPLMN data to Origination Indicator Parameter
Mapping .................................................................................................................
121
Table 99: Operator Determined Barring HPLMN data to Restriction digits Parameter
Mapping .................................................................................................................
121
Table 100: Call Barring Information List to SMS Origination Restrictions Parameter
Mapping .................................................................................................................
122
Table 101: Call Barring Information List to SMS Termination Restrictions Parameter
Mapping .................................................................................................................
123
Table 102: Call Barring Information List to Termination Restriction Code Parameter
Mapping .................................................................................................................
124
Table 103: SSData List to SMS Origination Restrictions Parameter Mapping ...........................
125
Table 104: SSData List to SMS Termination Restrictions Parameter Mapping..........................
125
Table 105: ISD_RESPONSE and DSD_RESPONSE to Qualdir Return Error Mapping.............
130
Table 106: Qualdir Return Error to INSERT_SUBSCRIBER_DATA_RESPONSE and
DELETE_SUSBCRIBER_DATA_RESPONSE Error Mapping .................................
130
If the response to FSM indicates a failure in the delivery of the short message, the IIF shall map the cause value received to a corresponding SMS_CauseCode value in the SMDPP Return Result, as described in.............................................................
132
Table 107: Short Message Service in GSM Foreign Mode (for CMT) Message Mapping ..........
134
Table 108: Short Message Service in ANSI-41 Foreign Mode (for CMT) Message Mapping ....
134
Table 109: SMDPP to MT_Forward Short Message Parameter Mapping for GSM Foreign
Mode......................................................................................................................
135
Table 110: MT_Forward Short Message to SMDPP Parameter Mapping for ANSI-41
Foreign Mode.........................................................................................................
136
Table 111: SM-RP-UI in MT_FORWARD_SHORT_MESSAGE for MAP V2 Parameter
Values for GSM Foreign Mode ...............................................................................
136
Table 112: SM-RP-UI in MT_FORWARD_SHORT_MESSAGE for MAP V1 Parameter
Encoding for GSM Foreign Mode............................................................................
138
Table 113: SMS_Bearer Data in Mobile Terminating SMDPP Parameter Encoding for
ANSI-41 Foreign Mode...........................................................................................
139
Table 114: Forward_Short_Message to ANSI-41_SMDPP Parameter Mapping for MO SMS in GSM Foreign Mode ............................................................................................
140
Table 115: ANSI-41 SMDPP to GSM Forward_Short_Message Parameter Mapping for MO
SMS in ANSI-41 Foreign Mode...............................................................................
141
Table 116: Forward_Short_Message to SMS_CauseCode Values in SMDPP Return Result
Error Mapping ........................................................................................................
147 xi

N.S0028
16
17
18
19
20
21
22
23
24
25
10
11
12
13
8
9
14
15
26
27
28
29
30
31
32
33
34
35
1
2
3
4
5
6
7
Table 117: SMDPP to Forward_Short_Message Error Mapping ...............................................
149
If the User Error parameter is populated in the GSM_FSM_ACK, then map this value into the SMS_CauseCode according to.........................................................................
151
Next, it populates the stored originating SMSC address and transaction ID. If the User
Error parameter is populated in GSM_FSM_ACK, then this value is mapped into the SMS_CauseCode according to.........................................................................
153
Table 118: Short Message Service (for GHOST or WEMT) Message Mapping.........................
153
Table 119: Alerting for an ANSI-41 Subscriber in GSM Foreign Mode Parameter Mapping.......
154
Table 120: Alerting for a GSM Subscriber in ANSI-41 Foreign Mode Parameter Mapping ........
155
Table 121: SMDPP to Forward Short Message for Mobile Terminated
GHOST/WEMTTeleservice Parameter Mapping in GSM Foreign Mode ..................
155
Table 122: Forward Short Message to SMDPP for Mobile Terminated GHOST/WEMT
Teleservice Parameter Mapping in ANSI Foreign Mode ..........................................
156
Table 123: Forward Short Message to SMDPP for Mobile Originated GHOST/WEMT in
GSM Foreign Mode Parameter Mapping.................................................................
157
Table 124: SMDPP to Forward Short Message for Mobile Originated GHOST/WEMT
Teleservice Parameter Mapping in ANSI-41 Foreign Mode .....................................
158
Table 125: HLPI for GHOST ....................................................................................................
158
The IIF is responsible for mapping GSM MAP_FSM_ACK Return Errors to ANSI-41
SMS_CauseCodes according to.............................................................................
159
Table 126: Teleservice Server Address Mapping in IIF.............................................................
160
Table 127: Message Waiting Notification in GSM Foreign Mode Message Mapping .................
163
Table 128: Message Waiting Notification in ANSI-41 Foreign Mode Message Mapping ............
163
Table 129: Regnot to Forward Short Message for Message Waiting Notification Parameter
Mapping .................................................................................................................
164
Table 130: QUALDIR to Forward Short Message for Message Waiting Notification
Parameter Mapping................................................................................................
164
Table 131: Forward Short Message to QUALDIR for Message Waiting Notification
Parameter Mapping................................................................................................
165
Table 132: Forward Short Message to SMDPP for Message Waiting Notification Parameter
Mapping .................................................................................................................
165
Table 133: SM-RP-UI in Message FORWARD-SHORT-MESSAGE For MAP V2 Parameter
Encoding................................................................................................................
166
Table 134: SM-RP-UI in Message FORWARD_SHORT-MESSAGE for MAP V1 Parameter
Encoding................................................................................................................
168
xii

N.S0028
16
17
18
19
20
21
10
11
12
13
14
15
26
27
28
29
30
22
23
24
25
31
32
4
5
6
7
8
9
1
2
3
Table 135: qualdir return error to FORWARD_SHORT_MESSAGE response Error
Mapping .................................................................................................................
169
Table 136: SMSDPP to FORWARD_SHORT_MESSAGE response Error Mapping .................
169
Table 137: Location Updating GPRS in GSM Foreign Mode Message Mapping .......................
171
Table 138: MAP_UPDATE_GPRS_LOCATION_REQUEST → REGNOT Parameter
Mapping .................................................................................................................
172
Table 139: MAP_INSERT_SUBSCRIBER_DATA_REQUEST → regnot Parameter Mapping ...
173
Table 140: MAP_UPDATE GPRS LOCATION RESPONSE → regnot Parameter Mapping.......
174
Table 141: MAP_INSERT_SUBSCRIBER_DATA_REQUEST → profile ‘macro’ Mapping.........
175
Table 141 A: ROUTREQ → MT_Forward Short Message Parameter Mapping ........................
178
If the response to FSM indicates a failure in the delivery of the short message, the IIF shall map the cause value received to a corresponding SMS_CauseCode value in the SMDPP Return Result, as described in.............................................................
181
Table 142: Alerting for an ANSI-41 Subscriber for GPRS in GSM Foreign Mode Parameter
Mapping .................................................................................................................
182
If the User Error parameter is populated in the GSM_FSM_ACK, then map this value into the SMS_CauseCode according to.........................................................................
183
Table 143: ANSI-136-710 to GHOST Parameter Mapping........................................................
187
Table 144: TP Derived Values .................................................................................................
188
Table 145: GHOST to ANSI-136-710 Parameter Mapping........................................................
190
Table 146: CMT Derived Values ..............................................................................................
191
Table 147: SMS_CauseCode to TP-STATUS Mapping ............................................................
192
Table 148: SMS-STATUS-REPORT Derived Values................................................................
194
Table 149: RP-ERROR Cause to R-Cause for Mobile Station Response to Mobile
Terminated Transfer Attempt. .................................................................................
197
Table 150: ANSI-41 SMS_CauseCode to ANSI-136 R-Cause Code Mapping ..........................
198
Table 151: ANSI-136 R-Cause Code to RP-ERROR Cause Mapping within the Mobile
Station ...................................................................................................................
198
Table 152: UPDATE_LOCATION_REQUEST ->REGNOT Parameter Mapping .......................
199
Table 1: Location Updating in GSM Foreign Mode Message Mapping ........................................12
Table 2: Location Updating in ANSI-41 Foreign Mode Message Mapping...................................13
Table 3: MS Purging Message Mapping.....................................................................................13
xiii

N.S0028
14
15
16
17
18
19
20
21
10
11
12
13
22
23
24
25
26
27
28
29
30
31
6
7
4
5
8
9
1
2
3
Table 4: Location Cancellation Message Mapping......................................................................13
Table 5: UPDATE_LOCATION_REQUEST ↔ REGNOT Parameter Mapping............................13
Table 6: INSERT_SUBSCRIBER_DATA_REQUEST ↔ regnot Parameter Mapping ..................15
Table 7: UPDATE LOCATION RESPONSE ↔ regnot Parameter Mapping ................................16
Table 8: MS_PURGE_REQUEST ↔ MS INACTIVE Parameter Mapping...................................16
Table 9: CANCEL_LOCATION_REQUEST ↔ REGCANC Parameter Mapping .........................17
Table 10: UPDATE_LOCATION_RESPONSE to regnot Error Mapping .....................................20
Table 11: regnot return errors to UPDATE_LOCATION_RESPONSE Error Mapping .................21
Table 12 Fault Recovery Message Mapping ..............................................................................23
Table 13: GSM RESET ↔ ANSI UNRELDIR Parameter Mapping ..............................................23
Table 14: Automatic Call Delivery Message Mapping.................................................................27
Table 15: ROUTREQ ↔ PROVIDE_ROAMING_NUMBER_REQUEST Parameter
Mapping ...................................................................................................................28
Table 16: Provide Roaming Number Response ↔ Routreq Return Result Parameter
Mapping ...................................................................................................................30
Table 17: PROVIDE_ROAMING_NUMBER_RESPONSE to Routreq Return Error Mapping
(ANSI-41Foreign Mode) ...........................................................................................30
Table 18: Routreq Return Error to Provide Roaming Number Response Error Mapping
(GSM Foreign mode)................................................................................................30
Table 19: Provide Roaming Number Request default parameter ................................................31
Table 20: RoutingRequest Return Result default parameters .....................................................32
Table 21: Routing Request Invoke default parameter.................................................................33
Table 22: PRN response User Error to routreq Return Error Mapping .......................................36
Table 23: PRN Response Provider Error to routereq Return Error Mapping................................36
Table 24: RoutingRequest Return Result to User Error in the PRN response Error Mapping ......37
Table 25: Routing Request Return Error to PRN User Error Mapping.........................................37
Table 26: ROUTEREQ Return Result to Provide Roaming Number Response parameter mapping (Option 1)...................................................................................................39
Table 27: ROUTREQ Return Result to Provide Roaming Number Response Parameter
Mapping (Option 2)...................................................................................................40
Table 28: Return Error to User Error in the PRN response Error Mapping ..................................41
xiv

N.S0028
14
15
16
17
18
19
20
21
10
11
12
13
26
27
28
29
22
23
24
25
6
7
4
5
8
9
1
2
3
Table 29: Optimal Routing for Late Call Forwarding Message Mapping......................................44
Table 30: GSM Provide_Roaming_Number ↔ ANSI-41 ROUTEREQ Parameter Mapping.........45
Table 31: Mapping of Parameter values.....................................................................................46
Table 32: Provide_Roaming_Number_Response ↔ routereq Parameter Mapping.....................46
Table 33: Mapping of Parameter Values ....................................................................................46
Table 34: Resume_Call_Handling ↔ REDREQ Parameter Mapping..........................................47
Table 35: Mapping of Parameters Values ..................................................................................47
Table 36: Resume_Call_Handling_Response ↔ redreq Parameter Mapping .............................47
Table 37: ANSI-41 Redirection_Reason to GSM Forwarding_Reason........................................48
Table 38: GSM Forwarding_Reason to ANSI-41 Redirection_Reason........................................48
Table 39: Provide_Roaming_Number to Routing_Request Error Mapping..................................49
Table 40: Routing_Request to Provide_Roaming_Number Error Mapping..................................49
Table 41: Resume_Call_Handling to Redirection_Request Error Mapping .................................50
Table 42: Redirection_Request to Resume_Call_Handling Error Mapping .................................50
Table 43: Supplementary Service Activation and Deactivation Message Mapping ......................54
Table 44: Activate/Deactivate SS Request ↔ FEATREQ Parameter Mapping............................54
Table 45: Activate/Deactivate SS Response ↔ Feature Request Return Result Parameter
Mapping ...................................................................................................................56
Table 46: Activate/Deactivate SS Response ↔ Feature Request Return Error Mapping.............57
Table 47: Activate/Deactivate SS Request to FEATREQ Parameter Mapping ............................57
Table 48: FEATREQ default parameter......................................................................................58
Table 49: Activate/Deactivate SS Response default parameter values .......................................59
Table 50: Feature Request Invoke to Activate/Deactivate SS Request Parameter Mapping........60
Table 51: Activate/Deactivate SS Request default parameter.....................................................60
Table 52: FeatureRequest Return Result default parameter.......................................................61
Table 53: FeatureRequest Return Result to User Error in the Activate/Deactivate SS
Response Error Mapping..........................................................................................64
Table 54: FeatureRequest Return Error to Activate/Deactivate SS Response Error
Mapping ...................................................................................................................64
xv

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

N.S0028
14
15
16
17
18
19
20
21
7
8
9
10
11
12
13
1
2
3
4
5
6
26
27
28
29
30
31
32
33
22
23
24
25
Table 81: TransferToNumberRequest Return Result to Insert Subscriber Data parameter mapping ...................................................................................................................94
Table 82: TransferToNumberRequest Return Result to Insert Subscriber Data Request value mapping..........................................................................................................95
Table 83: Routing Request ↔ Provide Roaming Number Request (Network Provided number) Parmater Mapping......................................................................................97
Table 84: Routing Request ↔ Provide Roaming Number Request (User Provided number)
Parameter Mapping..................................................................................................98
Table 85: Routing Request ↔ Provide Roaming Number Request (Two calling party numbers) Parameter Mapping ..................................................................................99
Table 86: Routing Request ↔ Provide Roaming Number Request(Caller Id Restricted)
Parameter Mapping................................................................................................101
Table 87: Cancel_Location_Request ↔ REGCAN (Subscriber Deletion) Mapping ...................105
Table 88: Mapping of GSM MAP Messages ↔ ANSI MAP Messages (Subscriber Data
Modification)...........................................................................................................105
Table 89: Delete_Subscriber_Data ↔ Qualdir Mapping (Subscriber Data Modification)............105
Table 90: CANCEL_LOCATION_REQUEST ↔ REGCANC Parameter Mapping .....................106
Table 91: INSERT_SUBSCRIBER_DATA_REQUEST ↔ QUALDIR Parameter Mapping.........106
Table 92: INSERT_SUBSCRIBER_DATA_REQUEST ↔ profile ‘macro’ Mapping....................107
Table 93: Forwarding Information List to Calling Features Indicator Parameter Mapping ..........109
Table 94: Regional Subscription Data to Geographic Authorization Parameter Mapping...........111
Table 95: Call Barring Information List to Origination Indicator Parameter Mapping ..................111
Table 96: SSData List to Calling Features Indicator Parameter Mapping ..................................114
Table 97: Operator Determined Barring general data to Origination Indicator
Parameter Mapping................................................................................................116
Table 98: Operator Determined Barring HPLMN data to Origination Indicator Parameter
Mapping .................................................................................................................118
Table 99: Operator Determined Barring HPLMN data to Restriction digits Parameter
Mapping .................................................................................................................118
Table 100: Call Barring Information List to SMS Origination Restrictions Parameter
Mapping .................................................................................................................119
Table 101: Call Barring Information List to SMS Termination Restrictions Parameter
Mapping .................................................................................................................120
xvii

N.S0028
14
15
16
17
18
19
20
21
8
9
10
11
12
13
4
5
6
7
1
2
3
28
29
30
31
32
33
34
35
36
22
23
24
25
26
27
Table 102: Call Barring Information List to Termination Restriction Code Parameter
Mapping .................................................................................................................121
Table 103: SSData List to SMS Origination Restrictions Parameter Mapping ...........................122
Table 104: SSData List to SMS Termination Restrictions Parameter Mapping..........................122
Table 105: ISD_RESPONSE and DSD_RESPONSE to Qualdir Return Error Mapping.............127
Table 106: Qualdir Return Error to INSERT_SUBSCRIBER_DATA_RESPONSE and
DELETE_SUSBCRIBER_DATA_RESPONSE Error Mapping .................................127
If the response to FSM indicates a failure in the delivery of the short message, the IIF shall map the cause value received to a corresponding SMS_CauseCode value in the SMDPP Return Result, as described in.............................................................129
Table 107: Short Message Service in GSM Foreign Mode (for CMT) Message Mapping ..........131
Table 108: Short Message Service in ANSI-136 Foreign Mode (for CMT) Message
Mapping .................................................................................................................131
Table 109: SMDPP to MT_Forward Short Message Parameter Mapping for GSM Foreign
Mode......................................................................................................................132
Table 110: MT_Forward Short Message to SMDPP Parameter Mapping for ANSI-41
Foreign Mode.........................................................................................................133
Table 111: SM-RP-UI in MT_FORWARD_SHORT_MESSAGE for MAP V2 Parameter
Values for GSM Foreign Mode ...............................................................................133
Table 112: SM-RP-UI in MT_FORWARD_SHORT_MESSAGE for MAP V1 Parameter
Encoding for GSM Foreign Mode............................................................................134
Table 113: SMS_Bearer Data in Mobile Terminating SMDPP Parameter Encoding for
ANSI-41 Foreign Mode...........................................................................................135
Table 114: Forward_Short_Message to ANSI-41_SMDPP Parameter Mapping for MO SMS in GSM Foreign Mode ............................................................................................136
Table 115: ANSI-41 SMDPP to GSM Forward_Short_Message Parameter Mapping for MO
SMS in ANSI-41 Foreign Mode...............................................................................137
Table 116: Forward_Short_Message to SMS_CauseCode Values in SMDPP Return Result
Error Mapping ........................................................................................................142
Table 117: SMDPP to Forward_Short_Message Error Mapping ...............................................144
If the User Error parameter is populated in the GSM_FSM_ACK, then map this value into the SMS_CauseCode according to.........................................................................146
Next, it populates the stored originating SMSC address and transaction ID. If the User
Error parameter is populated in GSM_FSM_ACK, then this value is mapped into the SMS_CauseCode according to.........................................................................148
Table 118: Short Message Service (for GHOST) Message Mapping ........................................148
xviii

N.S0028
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
1
7
8
9
10
11
12
13
2
3
4
5
6
14
15
Table 119: Alerting for an ANSI-136 Subscriber in GSM Foreign Mode Parameter Mapping.....149
Table 120: Alerting for a GSM Subscriber in ANSI-136 Foreign Mode Parameter Mapping.......150
Table 121: SMDPP to Forward Short Message for Mobile Terminated GHOST Teleservice
Parameter Mapping in GSM Foreign Mode.............................................................150
Table 122: Forward Short Message to SMDPP for Mobile Terminated GHOST Teleservice
Parameter Mapping in ANSI Foreign Mode.............................................................151
Table 123: Forward Short Message to SMDPP for Mobile Originated GHOST in GSM
Foreign Mode Parameter Mapping .........................................................................152
Table 124: SMDPP to Forward Short Message for Mobile Originated GHOST Teleservice
Parameter Mapping in ANSI-41 Foreign Mode........................................................153
Table 125: HLPI for GHOST ....................................................................................................153
The IIF is responsible for mapping GSM MAP_FSM_ACK Return Errors to ANSI-41
SMS_CauseCodes according to.............................................................................154
Table 126: Teleservice Server Address Mapping in IIF.............................................................154
Table 127: Message Waiting Notification in GSM Foreign Mode Message Mapping .................158
Table 128: Message Waiting Notification in ANSI-136 Foreign Mode Message Mapping ..........158
Table 129: Regnot to Forward Short Message for Message Waiting Notification Parameter
Mapping .................................................................................................................159
Table 130: QUALDIR to Forward Short Message for Message Waiting Notification
Parameter Mapping................................................................................................159
Table 131: Forward Short Message to QUALDIR for Message Waiting Notification
Parameter Mapping................................................................................................160
Table 132: Forward Short Message to SMDPP for Message Waiting Notification Parameter
Mapping .................................................................................................................160
Table 133: SM-RP-UI in Message FORWARD-SHORT-MESSAGE For MAP V2 Parameter
Encoding................................................................................................................161
Table 134: SM-RP-UI in Message FORWARD_SHORT-MESSAGE for MAP V1 Parameter
Encoding................................................................................................................163
Table 135: qualdir return error to FORWARD_SHORT_MESSAGE response Error
Mapping .................................................................................................................164
Table 136: SMSDPP to FORWARD_SHORT_MESSAGE response Error Mapping .................164
Table 137: Location Updating GPRS in GSM Foreign Mode Message Mapping .......................166
Table 138: MAP_UPDATE_GPRS_LOCATION_REQUEST → REGNOT Parameter
Mapping .................................................................................................................167
xix

N.S0028
4
5
6
7
8
9
1
2
3
10
11
12
13
14
15
16
17
18
19
Table 139: MAP_INSERT_SUBSCRIBER_DATA_REQUEST → regnot Parameter Mapping ...168
Table 140: MAP_UPDATE GPRS LOCATION RESPONSE → regnot Parameter Mapping.......169
Table 141: MAP_INSERT_SUBSCRIBER_DATA_REQUEST → profile ‘macro’ Mapping.........170
Table 141 A: ROUTREQ → MT_Forward Short Message Parameter Mapping ........................173
Table 142: Alerting for an ANSI-136 Subscriber for GPRS in GSM Foreign Mode
Parameter Mapping................................................................................................177
Table 143: ANSI-136-710 to GHOST Parameter Mapping........................................................182
Table 144: TP Derived Values .................................................................................................183
Table 145: GHOST to ANSI-136-710 Parameter Mapping........................................................185
Table 146: CMT Derived Values ..............................................................................................186
Table 147: SMS_CauseCode to TP-STATUS Mapping ............................................................187
Table 148: SMS-STATUS-REPORT Derived Values................................................................189
Table 149: RP-ERROR Cause to R-Cause for Mobile Station Response to Mobile
Terminated Transfer Attempt. .................................................................................192
Table 150: ANSI-41 SMS_CauseCode to ANSI-136 R-Cause Code Mapping ..........................193
Table 151: ANSI-136 R-Cause Code to RP-ERROR Cause Mapping within the Mobile
Station ...................................................................................................................193
xx

1
2
3
4
5
There are no figures in this volume.
N.S0028
xxi

N.S0028
1
2
22
23
24
25
26
27
28
29
30
31
32
33
34
38
39
40
35
36
37
8
9
10
11
5
6
7
12
13
14
15
16
17
18
19
20
21
3
4
This foreword is not part of this standard.
This standard addresses the interworking and interoperability between ANSI-41 MAP and GSM based networks in the support of subscribers roaming between networks. The objective of the standard is to achieve fully automatic, two-way interoperability between the heterogeneous networks. Services supported by this standard are described along with the associated information flows and message mappings. However, not all services and associated capabilities of ANSI-41
MAP and GSM MAP are supported by this standard. In general the attempt has been to focus on the key subscriber services needed in the market.
The focus of this the first release of this standard is on common GSM and ANSI-136 TDMA services and associated network signaling (i.e. ANSI-41 MAP and GSM MAP). A pre-requisite for this interoperability is Multi-mode mobile stations with an enhanced SIM card for roaming between
ANSI-136, GSM, and AMPS networks.
The first release of the standard did not define or require changes to existing ANSI-41 MAP or GSM
MAP to achieve the described interworking and interoperability. However, due to differences between the services and associated capabilities of the MAP protocols, complete and fully transparent interoperability may not have been achieved for some services. Future releases of this standard may require changes to ANSI-41 MAP, GSM MAP and the associated services to achieve full transparency while roaming between the different networks.
Additional or alternate service descriptions, information flows, and message mappings may be required to support other air interfaces supported by ANSI-41 MAP (e.g., IS-95, cdmaOne, and cdma2000). This may be accomplished in future release of this standard.
Aspects of TIA/EIA-136 Revision C have been incorporated into this standard.
Revision A adds the capability of getting GPRS services when roaming in GSM Foreign Mode.
Revision B adds two way roaming between GSM and CDMA systems
Information disclosed in this document is subject to the export jurisdiction of the US Department of
Commerce as specified in Export Administration Regulations (title 15 CFR parts 730 through 774 inclusive).
The information contained herein may not be exported or re-exported to Cuba, Iran, Iraq, Libya, North Korea,
Sudan, or Syria. Contact the Telecommunications Industry Association, Arlington, VA or http://ftp.tiaonline.org/tr-45/tr45ahag/public%20documents
xxii

1
2
3
6
7
4
5
(This page intentionally left blank.)
N.S0028
xxiii

N.S0028
1
2
3
4
12
13
14
15
16
8
9
10
5
6
7
11
17
18
19
20
When a subscriber to one network type (e.g., ANSI-41) roams to a network of another type
(e.g., GSM), interworking and interoperability functions are required to support roaming and enable service. This standard describes an Interworking and Interoperability Function (IIF) to support this cross-technology roaming between ANSI-41 and GSM networks. The IIF supports a multi-mode mobile station with a removable Subscriber Identity Module (SIM). The standard also defines the required network message mappings between ANSI-41 MAP and GSM MAP to support the mobile terminal and associated services.
This standard includes the support of cross-technology roaming from an ANSI-41 based network to a GPRS network. The GPRS network may be coupled with a GSM network. This feature requires enhancement to the Interworking and Interoperability Function (IIF) which supports a multi-mode mobile station and Subscriber Identity Module (SIM) with GPRS functionality.
Optionally, IIF may support one way-roaming only from CDMA to GSM network. In this case, all the relevant mapping tables described are applicable only in GSM Foreign Mode and for this scenario they applied as unidirectional only. (Annex C)
21
22
23
24
25
26
27
The purpose for this standard is to define and describe the functions necessary for roaming between ANSI-41 MAP and GSM MAP based networks in the support of roaming subscribers.
This includes a capability to allow a subscriber to an ANSI-41 based network (e.g., an ANSI-
136 41, TDMA or CDMA native subscriber) with a mobile terminal supporting GPRS service to roam to a GPRS network in GSM Foreign Mode.
28
29
30
31
32
33
34
The scope of this standard are the services, information flows, and message mappings which require interworking and interoperability functional specifications to support roaming between
ANSI-41 MAP [6] and GSM MAP [3] networks.
The scope of this volume is to describe the processing, messages and parameters for
GPRS/GSM and ANSI-41 network interoperability.
35
36
37
This standard is organized into the following volumes:
1

N.S0028
6
7
4
5
8
9
10
11
12
13
1
2
3
14
15
16
17
18
Volume 0 - Overview and Interworking Reference Model
Volume 1 - Service Descriptions
Volume 2 - Information Flows
Volume 3 - Message Flows
This volume is organized according to the following:
2 References - is a list of references specific to this volume of the standard.
3 Definitions and Acronyms - defines words and acronyms that are used in this volume of the standard.
4 Message Mappings - describes the stage 3 processing required to map messages between ANSI-41 and GSM MAP.
Annex A Short Message Service Procedures within an ANSI-136 Network - contains a description of mapping CMT to GHOST mapping for Short Messages.
Annex B Cause Code Mapping at non-IIF nodes - contains a description of cause code mappings at non-IIF nodes.
Annex C One-way roaming from CDMA to GSM - contains a descriptio
Of the optional one-way roaming procedures, mappings
2

N.S0028
1
2
3
4
5
6
7
GSM 03.18 Version 6.2.0 Release 1997 “ Digital cellular communication system (Phase
2+); Basic call handling; Technical realisation”, November 1998, ETSI.
GSM 03.79 version 6.2.0 release 1997, “Digital cellular telecommunications system
(Phase 2+); Support of Optimal Routeing (SOR) Technical Realisation”.
8
9
10
11
GSM 09.02 Version 6.2.0 Release 1997 “ Digital cellular communication system (Phase
2+); Mobile Application Part (MAP) specification”, August 1998, ETSI;
GSM 02.60 version 6.3.1 Release 1997 “General Packet Radio Service (GPRS); Service
Description, Stage 1”
17
18
31
32
33
19
20
21
22
23
24
25
26
27
28
29
30
12
13
14
15
16
GSM 03.60 version 6.8.0 Release 1997 “General Packet Radio Service (GPRS); Stage
2”
TIA/EIA-41-D: “Cellular Radiotelecommunications Intersystem Operations,” December
1997, ANSI.
TIA/EIA/IS-751: “TIA/EIA-41-D Modifications to support IMSI”, February 1998
[8] TIA/EIA/IS-807: “TIA/EIA-41-D Enhancements for Internationalization”, August 1999
[8] TIA/EIA/IS 737A”IS-41 support for data services for digital terminals (TDMA and CDMA)”
[9] TIA/EIA/TSB58-E “Administration of Parameter Value Assignments for TIA/EIA Spread
Spectrum Standards” , January 2002
[10] TIA/EIA-95-B - Mobile Station-Base Station Compatibility Standard for Dual-Mode Spread
Spectrum Systems; Published October 1998.
[11] "TIA/EIA-IS-2000-A, cdma2000 Series, March 2000, plus addenda"Mobile Station-Base
Station Compatibility Standard for Dual-Mode Spread Spectrum Systems;
[12] TIA/EIA-868 – ANSI-41-D Network Based Enhancements to support one-way roaming to
GSM, Published TBD. [12]"Enhanced Cryptographic Algorithms, Revision B," TR45AHAG, Published
TBD
3

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

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

N.S0028
9
10
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
11
12
13
14
15
16
17
18
19
20
38
39
40
6
7
8
1
2
3
4
5
Global System for Mobile Communications (GSM) defines both air interface and network intersystem protocol standards for mobile stations (MS), base station systems (BSS), and network switching systems (NSS).
GSM CS attached
GSM circuit-switched services attached means that the subscriber is attached to a GSM MSC.
This is also referred to as IMSI attached.
GSM CS detached
GSM circuit-switched services detached means that the subscriber is detached from a GSM
MSC. This is also referred to as IMSI detached.
GSM Mode
GSM mode indicates the condition or state of a mobile station accessing a GSM network.
GSM Foreign Mode
GSM foreign mode indicates the condition or state of an ANSI136 41 native subscriber accessing a GSM network.
GSM Native Mode
GSM native mode indicates the condition or state of a GSM native subscriber accessing a GSM network.
GSM Native Subscriber
GSM native subscriber indicates an end user whose primary or home subscription resides in a
GSM network. These subscribers include both home subscribers from the GSM network, as well as roamers from other GSM networks.
Mobile Station
The mobile equipment and the SIM together make up the mobile station, which is the wireless radiotelephone used by the subscriber.
Subscriber Identity Module
A smart card that plugs into the mobile equipment and that contains the authentication algorithms, and stores service-oriented subscription information.
41
42
43
44
45
46
AC
ANSI
Authentication center
American National Standards Institute
BAIC Barring of All Incoming Calls
BAOC Barring of All Outgoing Calls
6

N.S0028
12
13
14
15
16
10
11
8
9
3
4
1
2
5
6
7
28
29
30
31
32
24
25
26
27
20
21
22
23
17
18
19
BIC-Roam
BMI
BOIC
BOIC-exHC
Barring of Incoming Calls while Roaming Outside HPLMN Country
Base Station, Mobile Switching System, and Interworking Function
Barring of Outgoing International Calls
Barring of Outgoing International Calls Except to HPLMN Country
CDMA Code-Division Multiple Access
CFB Call Forwarding Busy
CFNA Call Forwarding No Answer
CFNRc Call Forwarding Not Reachable
CFNRy Call Forwarding No Reply
CFU Call Forwarding Unconditional
CPHS Common PCN Handset Specification
CS
DCS
EDGE
EIA
ESN
Circuit-Switched
Data Coding Scheme
Enhanced Data Rates Through Global Evolution
Electronics Industry Association
Electronic Serial Number
ETSI
FC
FSM
European Telecommunications Standards Institute
Feature Code
Forward Short Message
GGSN Gateway GPRS Support Node
GHOST GSM Hosted SMS Teleservice
GMSC Gateway Mobile Switching Center
GPRS General Packet Radio Service
GSM
HLPI
Global System for Mobile Communications
Higher Layer Protocol Indicator
HLR Home Location Register
HPLMN Home Public Land Mobile Network
IIF
IMSI
ITU
MAP
MC
Interworking and Interoperability Function
International Mobile Subscriber Identity
International Telecommunications Union
Mobile Application Part
ANSI136 41 Message Center (for SMS)
7

N.S0028
12
13
14
15
16
10
11
8
9
3
4
1
2
5
6
7
28
29
30
31
32
24
25
26
27
20
21
22
23
17
18
19
MDN
ME
MIN
MO
Mobile Directory Number
Mobile Equipment
Mobile Identification Number
Mobile Originated
MS Mobile Station
MSC Mobile Switching Center
MSCID MSC Identification Number
MSID Mobile Station Identity
MSISDN Mobile Subscriber ISDN Number
MSRN Mobile Station Routing Number
MT Mobile Terminated
MWN
ODB
OR
PCS
PDU
Message Waiting Notification
Operator Determined Barring
Optimal Routing
Personal Communication Service
Packet Data Unit
PIN Personal Identification Number
PLMN Public Land Mobile Network
SGSN Serving GPRS Support Node
PRN
SC
SID
SIM
Provide Roaming Number
Service Center
System Identity
Subscriber Identity Module
SMDPP Short Message Delivery Point-to-Point
SME Short Message Entity
SMS Short Message Service
SMS-C GSM Short Message Service Center
SS7 Signaling System 7
TDMA Time Division Multiple Access
TIA
TLDN
Telecommunications Industry Association
Temporary Location Directory Number
TSAR Teleservice Segmentation and Reassembly
8

3
4
5
6
1
2
UDH
VLR
Universal Data Header
Visitor Location Register
VPLMN Visitor Public Land Mobile Network
WEMT Wireless Enhanced Messaging Teleservices
N.S0028
9

1
N.S0028
27
28
29
30
31
32
33
34
35
36
2
3
4
5
6
7
8
9
19
20
21
22
23
15
16
17
18
10
11
12
13
14
24
25
26
The IIF shall perform the translation of messages, parameters and parameter values in accordance with the tables included in this volume of the standard. The following notation is used in accordance with the definitions given in GSM 09.02 [3] and ANSI-41 [6], [7], 0.
Within the following tables, the parameters are identified as either being:
M Mandatory,
C Conditional
O Service Provider Optional
The following notation is used in this standard to identify parameters as being syntactically optional but semantically required to be sent by the IIF in order to support interoperability:
R Required.
Refer to GSM 09.02 [3] and ANSI-41 [6], [7], 0 for a description of the messages, parameters and parameter values.
When the IIF receives either a GSM MAP message or an ANSI MAP message, it shall apply the following rules regarding the handling of parameters within those messages:
The IIF shall populate mandatory parameters in messages sent by the IIF, regardless of whether mapping of parameters is possible.
The IIF may populate optional parameters in messages sent by the IIF, regardless of whether mapping of parameters is possible.
All parameters shall be populated in accordance with GSM 09.02 [3] or ANSI-41 [6], [7], 0.
Where there is no direct mapping for parameters, a hyphen (‘-‘) has been entered in the corresponding table.
Existing mobility procedures described in either GSM 09.02 [3] or ANSI-41 [6] are also directly applicable to the IIF when it is emulating a GSM or ANSI-41 functional network element.
Enhancements/modifications to ANSI-41 [7], 0 are also applicable.
The location registration procedure is used to update the location information held in the network. This location information is used to route incoming calls and short messages to the roaming subscriber.
10

N.S0028
1
2
3
4
4.1.1.1 Detailed Procedures
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
40
41
42
43
44
32
33
34
35
36
37
38
39
5
6
7
8
9
10
11
12
The Location registration procedure is also used to cancel location information held in the network.
The IIF contains location information (vlr number) relating to the roaming subscriber. Therefore, the IIF needs to be updated at each change in VLR. The IIF shall translate GSM MAP messages to ANSI-41 MAP messages and vice versa, when the subscribers home HLR needs updating. The subscriber’s home HLR needs to be updated only in the following cases:
When the subscriber’s MS registers in a GSM network, when previously registered in an ANSI-
41 network;
When the subscribers MS registers in an ANSI-41 network, when previously registered in a
GSM network;
Optionally, the subscriber’s home HLR may be updated in the following cases:
When the subscribers MS (accessing a GSM Network) registers in another VLR within the same GSM network;
When the subscribers MS (accessing an ANSI-41 Network) registers in another VLR within the same ANSI-41 network;
When the HLR is updated, the IIF conveys a unique identifier to the HLR identifying the serving
MSC/VLR.
If the IIF receives a GSM MAP _UPDATE_LOCATION_REQUEST, it shall compare the received location information with any previously stored location information. If the received and previously stored location information are different, the IIF shall determine if the location updating is allowed and update the corresponding subscriber record accordingly and send a
GSM MAP _CANCEL_LOCATION_REQUEST to the old VLR. If there is no previously stored location information in the IIF, the IIF shall determine if the location updating is allowed and update the corresponding subscriber record accordingly. In either case, if the HLR is required to be updated, then the IIF shall send an ANSI_MAP_REGNOT to the HLR and await a response.
If the response indicates that the location updating procedure has been successful, then the IIF shall update the corresponding subscriber record and send a GSM MAP
_INSERT_SUBSCRIBER_DATA_REQUEST to the serving VLR and await a response. If the response indicates success, the IIF completes the location updating procedure by sending a
GSM MAP _UPDATE_LOCATION_RESPONSE to the serving VLR. The GSM MAP
_UPDATE_LOCATION_RESPONSE contains a unique identifier, identifying the HLR.
Otherwise, the IIF sends a GSM MAP _UPDATE_LOCATION_RESPONSE to the serving VLR indicating the reason why the location updating procedure was not successful.
If the response indicates that the location updating procedure has been unsuccessful, then the
IIF shall not update the corresponding subscriber record and shall send a GSM MAP
_UPDATE_LOCATION_RESPONSE to the serving VLR indicating the reason for failure.
If the IIF receives an ANSI_MAP_REGNOT, it shall compare the received location information with any previously stored location information. If the received and previously stored location
11

N.S0028
23
24
25
26
27
28
29
30
9
10
11
6
7
8
1
2
3
4
5
12
13
14
15
16
17
18
19
20
21
22
39
40
41
42
43
44
45
46
31
32
33
34
35
36
37
38 information is different, the IIF shall update the corresponding subscriber record and send an
ANSI_MAP_REGCANC to the old VLR. If there is no previously stored location information in the IIF, the corresponding subscriber record is updated. In either case, if the HLR is required to be updated, then the IIF shall send a GSM MAP _UPDATE_LOCATION_REQUEST to the HLR and await a response.
If the response indicates that the location updating procedure has been successful, then the IIF shall update the corresponding subscriber record and send an ANSI_MAP_regnot to the serving VLR. The ANSI_MAP_regnot contains a unique identifier, identifying the HLR.
If the response indicates that the location updating procedure has been unsuccessful, then the
IIF shall not update the corresponding subscriber record and shall send an ANSI_MAP_regnot to the serving VLR indicating the reason for failure.
If the IIF receives a GSM MAP _MS_PURGE_REQUEST, it shall check the contents of the message for errors. If errors exist, the IIF shall send a GSM MAP _MS_PURGE_RESPONSE indicating the reason for failure and the MS purged flag shall not be set. If no errors exist, the
IIF shall check if the received VLR number matches the stored VLR number.
If the received VLR number and the stored VLR number match, the IIF shall set the MS purged flag and shall send both a GSM MAP _MS_PURGE_RESPONSE to the VLR (including the
Freeze TMSI parameter) and an ANSI_MAP_MS_INACTIVE to the HLR and awaits a response from the HLR.
If the received VLR number and the stored VLR number do not match, the IIF sends a GSM
MAP _PURGE_MS_RESPONSE containing an empty result to indicate successful outcome and the MS purged flag is not set.
When the IIF receives a response from the HLR, it shall follow the VLR procedures outlined in
ANSI-41 [6].
If the IIF receives an ANSI_MAP_MS_INACTIVE, it shall check the contents of the message for errors. If errors exist, the IIF shall send an ANSI_MAP_ms_inactive indicating the reason for failure and shall not set the MS state to inactive. If no errors exist, the IIF shall set the MS state to inactive and follow the HLR procedures described in ANSI-41 [6]. If the state of the MS remains inactive for a period of time (time controlled by operator), the IIF may send a GSM
MAP _MS_PURGE_REQUEST to the HLR.
If the IIF receives a GSM MAP _CANCEL_LOCATION_REQUEST as part of a location cancellation procedure it shall check the contents of the message for errors. If errors exist, the corresponding temporary subscriber data is not deleted and the IIF shall send a GSM MAP
_CANCEL_LOCATION_RESPONSE indicating the reason for failure to the HLR. If no errors exist, the IIF shall delete the corresponding temporary subscriber data and send an
ANSI_MAP_REGCANC to the VLR and await a response.
If the response indicates that the location cancellation procedure has been successful, then the
IIF shall send a GSM MAP _CANCEL_LOCATION_RESPONSE to the HLR.
If the response indicates that the location cancellation procedure has been unsuccessful, then the IIF shall send a GSM MAP _CANCEL_LOCATION_RESPONSE to the HLR indicating successful deletion of subscriber data (i.e., ignore the error).
If the IIF receives an ANSI_MAP_REGCANC and the message can be processed, the IIF shall delete the corresponding temporary subscriber data and send a GSM MAP
_CANCEL_LOCATION_REQUEST to the VLR and await a response.
12

N.S0028
17
18
19
20
1
2
3
4
5
6
7
8
9
If the response indicates that the location cancellation procedure has been successful, then the
IIF shall send an ANSI_MAP_regcanc to the HLR.
If the response indicates that the location cancellation procedure has been unsuccessful, then the IIF shall send an ANSI_MAP_regcanc to the HLR indicating successful deletion of subscriber data (i.e., ignore the error). The IIF may retry to sending the
ANSI_MAP_REGCANC before responding to the HLR.
If the IIF receives an ANSI_MAP_REGCANC and the message cannot be processed, the corresponding temporary subscriber data shall not be deleted and the IIF shall send an
ANSI_MAP_regcanc to the HLR indicating reason for failure.
10
11
4.1.1.2 Mapping of Messages, Parameters & Parameter Values
12
13
14
15
4.1.1.2.1 Mapping of Messages
Table 1 shows the mapping between GSM MAP messages and ANSI MAP messages related 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 Regnot
1
1
This message can also contain error values if the location updating procedure is unsuccessful.
If the location updating procedure fails, the mapping is as shown in 4.1.1.3.
13

N.S0028
1
2
3
4
5
6
7
8
Table 2 shows the mapping between GSM MAP messages and ANSI MAP messages related to Location Registration in ANSI-41 Foreign Mode.
Table 2: Location Updating in ANSI-41 Foreign Mode Message Mapping
GSM MAP Messages ANSI MAP Messages
UPDATE_LOCATION_REQUEST REGNOT
UPDATE_LOCATION_RESPONSE Regnot
Table 3 shows the mapping between GSM MAP messages and ANSI MAP messages (MS
Purging, regardless of mode of operation)
GSM MAP Messages
Table 3: MS Purging Message Mapping
ANSI MAP Messages
9
10
11
12
13
14
Table 4 shows the mapping between GSM MAP messages and ANSI MAP messages related to Location Cancellation.
Table 4: Location Cancellation Message Mapping
GSM MAP Messages ANSI MAP Messages
CANCEL_LOCATION_REQUEST REGCANC
CANCEL_LOCATION_RESPONSE regcanc
15
16
17
18
19
4.1.1.2.2 Mapping of Parameters
Table 5 through Table 9 shows the mapping of parameters, which the IIF shall perform regardless of the mode of operation (GSM Foreign Mode or ANSI-41 Foreign Mode).
Table 5: UPDATE_LOCATION_REQUEST ↔ REGNOT Parameter Mapping
GSM MAP
_UPDATE_LOCATION_REQUE
ST
Status ANSI_MAP_REGNOT Status
MSC Address M
1
M
MSID M
MSCID (Serving MSC)
1
M
14

N.S0028
3
4
5
6
7
1
2 Table 5: UPDATE_LOCATION_REQUEST ↔ REGNOT Parameter Mapping (concluded)
GSM MAP
_UPDATE_LOCATION_REQUE
ST
Status ANSI_MAP_REGNOT Status
VLR Number M -
- PC_SSN (Serving MSC or VLR) O
O
TerminalType
2
O
TransactionCapability
2
- O
Supported CAMEL Phases C -
1
These parameters are used to convey a unique identifier from the IIF to the HLR, identifying the serving MSC/VLR.
2
Parameters are included in ANSI specifications IS-41-C and later.
15

N.S0028
1
2
3
4
Table 6 shows the mapping of parameters for GSM MAP
_INSERT_SUBSCRIBER_DATA_REQUEST to regnot.
Table 6: INSERT_SUBSCRIBER_DATA_REQUEST ↔ regnot Parameter Mapping
GSM MAP
_INSERT_SUBSCRIBER_DATA
_REQUEST
Status regnot Status
M
HLR)
5
6
7
8
9
10
11
IMSI C -
1
This parameter is itself a macro containing a number of other parameters. As far as mapping of parameters is concerned, the IIF shall map the contents of the ‘Profile’ macro in the ANSI-41-
D ‘regnot’ to the contents of the GSM MAP _INSERT_SUBSCRIBER_DATA_REQUEST as shown in Table 92
16

1
N.S0028
Table 7: UPDATE LOCATION RESPONSE ↔ regnot Parameter Mapping
GSM MAP
_UPDATE_LOCATION_RESPO
NSE
Status regnot Status
M
HLR)
HLR number
1, 2
(HLR)
2
R
4
5
6
7
8
9
2
3
10
1
The presence of this parameter is mandatory in case of successful HLR updating.
2
These parameters are used to convey a unique identifier from the IIF to the serving MSC/VLR, identifying the HLR.
3
This parameter is itself a macro containing a number of other parameters. As far as mapping of parameters is concerned, the IIF shall map the contents of the ‘Profile’ macro in the ANSI-41-
D ‘regnot’ to the contents of the GSM MAP _INSERT_SUBSCRIBER_DATA_REQUEST as shown in Table 92.
Table 8: MS_PURGE_REQUEST ↔ MS INACTIVE Parameter Mapping
GSM MAP
_MS_PURGE_REQUEST
Status
VLR Number C -
11
12
17

1
N.S0028
Table 9: CANCEL_LOCATION_REQUEST ↔ REGCANC Parameter Mapping
GSM MAP
_CANCEL_LOCATION_REQUE
ST
Status ANSI_MAP_REGCANC Status
Cancellation Type C
1
MSID M
O
9
10
11
12
13
14
15
2
3
4
1
Cancellation Type is only used between the HLR and the SGSN for GPRS procedures.
Cancellation Type is not applicable between HLR and VLR.
5
6
7
8
4.1.1.3 Error Handling
Error handling defined in GSM 09.02 [3] and ANSI-41 [6] is directly applicable to the IIF, when the IIF is emulating a GSM or ANSI-41 network functional element.
If the Location Updating procedure fails at an ANSI-41 HLR, the HLR shall respond by either sending:
An ANSI_MAP_regnot in a TCAP RETURN RESULT indicating authorization denied
(AUTHDEN) to the IIF, with one of the following reasons as defined in ANSI-41 [6]:
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
8
9
5
6
7
3
4
1
2
TerminalType mismatch
The ANSI-MAP-regnot may optionally, indicate:
•
The authorization period (DENAUTHPER) as defined in ANSI-41 [6]
•
Access Info as defined in ANSI-41 [6]
Or, an ANSI_MAP_regnot in a TCAP RETURN ERROR one of the following error codes as defined in ANSI-41 [6]:
Appropriate Error Codes in ANSI_MAP_regnot RETURN ERROR
Error Codes
MSID/HLRMismatch
ResourceShortage
OperationNotSupported
ParameterError
SystemFailure
19

N.S0028
4
5
6
7
8
9
10
11
12
13
14
1
2
3
15
Appropriate Error Codes in ANSI_MAP_regnot RETURN ERROR (concluded)
Error Codes
UnrecognizedParameterValue
MissingParameter
The IIF is therefore responsible for mapping any errors it receives from the HLR in the ANSI-
MAP-regnot to an equivalent error in the GSM-MAP-UPDATE-LOCATION RESPONSE towards the serving GSM MSC/VLR.
The GSM-MAP-UPDATE-LOCATION RESPONSE may include one the following ‘user’ errors as defined in GSM 09.02 [3]:
Appropriate User Errors
User Errors unknown subscriber; roaming not allowed; system failure; unexpected data value.
The following ‘provider errors’ (protocol related errors) are also defined in GSM 09.02 [3]:
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.
20

N.S0028
1
2
3
4
5
6
7
8
If the Location Updating procedure fails at a GSM HLR, it returns a GSM MAP
_UPDATE_LOCATION_RESPONSE to the IIF, indicating a ‘user error’ as indicated above.
The IIF is therefore responsible for mapping any errors it receives into a corresponding error in the ANSI_MAP_regnot towards the serving ANSI MSC/VLR. For further description of these errors and when they are used, refer to either GSM 09.02 [3] or ANSI-41 [6].
Table below provides the mapping of both user errors and provider errors to the equivalent value in either the AUTHDEN parameter in the ANSI_MAP_regnot RETURN RESULT or the
RETURN ERROR for ANSI-41 Foreign Mode.
9 Table 10: UPDATE_LOCATION_RESPONSE to regnot Error Mapping
UPDATE_LOCATION_RESPONSE
(Errors)
Unknown subscriber roaming not allowed system failure unexpected data value duplicated invoke Id not supported service
Regnot
SystemFailure
Not Authorized for the MSC
SystemFailure
SystemFailure
SystemFailure
SystemFailure mistyped parameter resource limitation initiating release unexpected response from the peer service completion failure no response from the peer invalid response received
SystemFailure
SystemFailure
SystemFailure
SystemFailure
SystemFailure
SystemFailure
SystemFailure
10
11
12
13
Table 11 provides the mapping for GSM Foreign Mode.
21

N.S0028
1
2 Table 11: regnot return errors to UPDATE_LOCATION_RESPONSE Error Mapping
Regnot
Delinquent account
Invalid serial number
Stolen unit
Duplicate unit
Unassigned directory number
UPDATE_LOCATION_RESPONSE
(Errors)
System failure
System failure
System failure
System failure
System failure
Multiple access
Not Authorized for the MSC
Missing authentication parameters
TerminalType mismatch
System failure
Roaming not allowed
System failure
System failure
3
4
5
6
7
8
If the Location Cancellation procedure fails at the IIF, existing procedures described in GSM
09.02 [3] and ANSI-41 [6] apply.
22

N.S0028
1
2
3
4
5
6
7
8
9
After the fault of a location register, the fault recovery procedures ensure that subscriber data in the VLR becomes consistent with the subscriber data stored in the IIF or that subscriber data in the IIF becomes consistent with the subscriber data that are stored in the HLR for the MS concerned and that the location information in the IIF and VLR or HLR and IIF reflect accurately the current location of the MS.
26
27
28
29
30
31
19
20
21
22
23
24
25
32
33
34
35
36
10
11
12
13
14
15
16
17
18
4.1.2.1 Detailed Procedures
If the IIF receives an ANSI_MAP_UNRELDIR, it shall send a RETURN RESULT and clear the records of those MSs associated with the requesting HLR. The IIF shall then send a GSM MAP
_RESET towards the serving VLR containing a unique identity, identifying the ANSI-41 HLR.
When the MS concerned next establishes authenticated radio contact (including a mobile originated call attempt), the IIF shall receive a GSM MAP _UPDATE_LOCATION_REQUEST and shall follow the procedures outlined in
4.1.1 Location Registration.
If the IIF receives a GSM MAP _RESET, it shall derive all involved MSs of that HLR either from the HLR Identity List (if present), or from the HLR number. The IIF shall then mark these MSs with the indicator "Location Information Confirmed in HLR" set to "Not Confirmed". The IIF shall then send an ANSI_MAP_UNRELDIR towards the serving VLR containing a unique identity, identifying the GSM HLR. The status "Not Confirmed" of the indicator "Location Information
Confirmed in HLR" forces the IIF to invoke the GSM MAP _UPDATE_LOCATION service after establishment of authenticated radio contact with the MS concerned.
If the IIF suffers a failure, while operating in GSM Foreign Mode, it shall send a GSM MAP
_RESET to the serving GSM VLR once it has returned to a stable state. The IIF shall not receive a response. The IIF may also send an ANSI_MAP_BULKDEREG to the ANSI-41 HLR.
If the IIF suffers a failure, while operating in ANSI-41Foreign Mode, it shall send an
ANSI_MAP_UNRELDIR to the serving ANSI-41 VLR once it has returned to a stable state. The
IIF shall receive an indication of success or failure.
If the IIF receives an ANSI_MAP_BULKDEREG, it shall send a RETURN RESULT to the requesting VLR and clear the location pointer of those MSs that were registered in the requesting VLR. Otherwise, the IIF shall send a RETURN ERROR with an appropriate error value to the requesting VLR.
37
38
39
40
41
4.1.2.2 Mapping of Messages, Parameters & Parameter Values
The IIF shall perform the mapping of messages, parameters and parameter values related to fault recovery in accordance with the tables presented in 4.1.2.2.
23

N.S0028
1
2
3
4
5
4.1.2.2.1 Mapping of Messages
Table 12 shows the mapping between GSM MAP messages and ANSI MAP messages related to fault recovery in either mode of operation (GSM Foreign mode or IS136 41 Foreign mode)
6
7
Table 12 Fault Recovery Message Mapping
GSM MAP Messages ANSI MAP Messages
RESET UNRELDIR
13
14
15
16
8
9
10
11
4.1.2.2.2 Mapping of Parameters
Table 13 shows the mapping of parameters, which the IIF shall perform regardless of the mode of operation (GSM Foreign Mode or ANSI-41Foreign Mode).
12 Table 13: GSM RESET ↔ ANSI UNRELDIR Parameter Mapping
GSM MAP _RESET
HLR Id LIST
HLR Number
1
Status ANSI_MAP_UNRELDIR
U
Status
(HLR)
1
R
1
These parameters are used to convey a unique identifier from the IIF to the serving VLR, identifying the true HLR.
24

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

N.S0028
1
2
3
4
5
6
7
Existing call handling procedures described in either GSM 09.02 [3] or ANSI-41 [6] are also directly applicable to the Interworking and Interoperability Function (IIF) when it is emulating a
GSM or ANSI-41 functional network element.
8
9
29
30
31
32
33
21
22
23
24
25
26
27
28
15
16
17
18
19
20
34
35
36
10
11
12
13
14
4.2.1.1 Detailed Procedures
The Automatic Call Delivery procedure is invoked in the IIF, when a terminating call attempt results in a request for routing information from the IIF.
The following procedures are applicable at the IIF for Automatic Call Delivery:
If the IIF receives an ANSI MAP_RoutingRequest Invoke message from the ANSI-41 HLR, it shall check if the terminating call can be placed to that subscriber. The IIF shall then deduce the IMSI from the MSID for that subscriber and populate the corresponding field of the
MAP_PROVIDE_ROAMING_NUMBER message.
The IIF shall store the BillingID received in the ANSI MAP_RoutingRequest Invoke message to later be able to populate the corresponding field in the ANSI MAP_RoutingRequest Return
Result message.
If the MobileDirectoryNumber field is present and in an international format in the
MAP_RoutingRequest Invoke message, the IIF shall populate the MSISDN field in the
MAP_PROVIDE_ROAMING_NUMBER message with it. If the MobileDirectoryNumber is in
National format, the IIF shall convert it to an International format before populating the MSISDN field
1
.
The IIF shall then populate the MSC Number field in the
MAP_PROVIDE_ROAMING_NUMBER message with the serving MSC Number that had been stored in the IIF at the time of the subscriber’s location registration.
The IIF shall then send the MAP_PROVIDE_ROAMING_NUMBER message to the GSM
MSC/VLR and wait for a response.
If the response indicates that the retrieval of routing information procedure has been successful, the IIF shall deduce the MSRN from the MAP_PROVIDE_ROAMING_NUMBER 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
8
9
10
11
12
13
14
1
2
3
4
5
6
7
IIF shall populate the BillingID field with the value of the BillingID received in the
RoutingRequest Invoke message.
The IIF shall then populate the MSCID (Serving) field with its own ID and forward it to the ANSI-
41 HLR.
If the response is unsuccessful, the IIF shall map any error code it receives to either an
AccessDeniedReason value in the MAP_RoutingRequest Return Result or to an Error Code in a Return Error message.
For the cases of failure at the IIF on reception of the MAP_RoutingRequest Invoke message
(e.g. missing expected parameter, unknown subscriber), the procedures described in ANSI-41
[6] are also applicable to the IIF.
For the cases of failure at the IIF on reception of the PROVIDE_ROAMING_NUMBER response, the procedures described in GSM 09.02 [3] for retrieval of routing information are also applicable to the IIF.
19
20
21
22
23
24
25
26
27
28
29
30
15
16
17
18
31
32
33
34
35
36
37
38
39
40
If the IIF receives a MAP_PROVIDE_ROAMING_NUMBER message from the GSM HLR, it shall check if the terminating call can be placed to that subscriber.
If the IIF determines that the subscriber is Not Reachable, it shall send a
MAP_PROVIDE_ROAMING_NUMBER Response message with User Error field indicating
Absent Subscriber to the GSM HLR.
Otherwise, the IIF shall deduce the MSID and ESN from the IMSI and populate the corresponding fields of the ANSI MAP_RoutingRequest Invoke.
The IIF shall create a billing ID for that transaction and populate the corresponding field of the
ANSI MAP_RoutingRequest Invoke.
The MSCID address field shall be set to the IIF address.
The IIF shall also assign a predefined value (vendor specific) to the SystemMyTypeCode field, indicating the IIF vendor identity.
If the MSISDN field is present in the MAP_PROVIDE_ROAMING_NUMBER, the IIF shall populate the MobileDirectoryNumber field in the RoutingRequest Invoke message with it
1
.
The IIF shall set the MSCIdentificationNumber and PC_SSN fields to its own ID.
The IIF shall then send the RoutingRequest Invoke message to the ANSI-41 MSC/VLR and wait for a response.
If the response indicates that the retrieval of routing information procedure has been successful, the IIF shall deduce the MSRN from the Digits (Destination) field of the
RoutingRequest Return Result and populate the MSRN field in the
MAP_PROVIDE_ROAMING_NUMBER ack. The MSRN shall have an E.164 format. Therefore, if the TLDN is not in international format, the IIF shall add the country code digits associated with the country of the serving system The IIF shall then forward the
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
8
9
10
11
1
2
3
4
5
6
7
If the response is unsuccessful, the IIF may receive a RoutingRequest Return Result with the field AccessReasonDenied present, or a ReturnError message with an Error Code value. The
IIF shall map any Access Reason Denied or Error Code it receives to a User or Provider Error in the MAP_PROVIDE_ROAMING_NUMBER return error.
For the cases of failure at the IIF on reception of the MAP_PROVIDE_ROAMING_NUMBER request, (e.g. missing expected parameter, unidentified subscriber), the procedure described in
GSM 09.02 [3] for retrieval of routing information are applicable to the IIF.
For the cases of failure at the IIF on reception of the MAP_RoutingRequest Invoke message return Result, the procedure described in ANSI-41 [6] for automatic call delivery is applicable to the IIF.
12
13
14
15
16
17
18
4.2.1.2 Mapping of Messages, Parameters & Parameter Values
4.2.1.2 presents the mapping of messages, parameters and parameter values that the IIF shall perform. The mapping in the following tables is applicable to the generic Call delivery scenarios. For mapping of parameters relevant to the Optimal Routing cases, refer to 4.2.3. For mapping of parameters relevant to CLIP/CLIR refer to 4.3.4.
19
20
21
22
23
4.2.1.2.1 Mapping of Messages
Table 14 shows the mapping between GSM MAP messages and ANSI MAP messages related to Automatic Call Delivery regardless of the mode of operation (GSM Foreign Mode or ANSI-41
Foreign Mode)
24 Table 14: Automatic Call Delivery Message Mapping
GSM MAP Message
PROVIDE ROAMING NUMBER
REQUEST
PROVIDE ROAMING NUMBER
REQUEST REPONSE
ANSI-41 MAP Message
Routreq routereq
25
28

N.S0028
1
2
3
4
5
6
7
4.2.1.2.2 Mapping of Parameters
Table 15 and Table 16 show the mapping of parameters, which the IIF shall perform regardless of the mode of operation (GSM Foreign Mode or ANSI-41 Foreign Mode).
Table 15: ROUTREQ ↔ PROVIDE_ROAMING_NUMBER_REQUEST Parameter Mapping
Status
BillingID (Originating) M
Request
-
MSCID (Originating MSC)
SystemMyTypeCode (Originating
MSC)
M
M -
M
O - CallingPartyNumberString1
(Note 1)
CallingPartyNumberString2
(Note 1)
O -
DMH_AlternateBillingDigits O -
(Note 2) (Note 3)
MSCIdentificationNumber R -
PC_SSN (Originating MSC) R -
SenderIdentificationNumber O -
R
(Note 4)
29

N.S0028
1
2
-
-
-
Table 15: ROUTREQ ↔ PROVIDE_ROAMING_NUMBER_REQUEST Parameter Mapping
(concluded)
Status
Request
- MSC Number M
-
GMSC address
GSM Bearer Capability
Network Signal Info
Announcement
Call Reference Number
R
(Note 5)
C
C
C
R
(Note 5)
8
9
10
11
12
3
4
5
6
7
CDMAServiceOption O -GSM BearerServiceCode or
GSM TeleService
O (Note 6)
Note 1: For encoding of those parameters, refer to “4.3.4 Calling Number/Line Identification
Presentation/Restriction”.
Note 2: If present from the PRN request
Note 3: May also be directly retrieved from the subscriber profile pre-provisioned in the IIF.
Note 4: Only if the IIF requires it to be included in the call data record
Note 5: Only for Optimal Routing after late Call Forwarding
-Note 6: Optional, if the network settings support data, a mapping may be performed as described in Table 92
30

N.S0028
1
2
3
4
5
6
The following table shows the mapping of parameters between the Provide Roaming Number
Response and the Routing Request Return Result messages regardless of the mode of operation (GSM Foreign Mode or ANSI-41 Foreign Mode).
Table 16: Provide Roaming Number Response ↔ Routreq Return Result Parameter
Mapping
Provide Roaming Number ack
Roaming Number*
Status
M
Routreq Return Result
Digits (Destination)
Status
R
User Error* R
(Note
1)
AccessDeniedReason
R
(Note
2)
10
11
12
13
14
7
8
9
15
16
17
18
19
20
-
GSM BearerServiceCode or GSM
TeleService (Note 3)
O
* These parameters are mutually exclusive
Note 1: If the request is unsuccessful.
PC_SSN (Serving MSC)
CDMAServiceOption
O
O
Note 2: If User Error is present in Provide Roaming Number ack.
-Note 3: Optional, if the network settings support data, a mapping may be performed as described in Table 92
Or
Table 17: PROVIDE_ROAMING_NUMBER_RESPONSE to Routreq Return Error Mapping
(ANSI-41Foreign Mode)
Provide Roaming Number ack Status
User Error
Provider Error
Status RoutingRequest Return
Error
C
C
Error Code O
For detailed mapping of User/Provider Error parameter value to the AccessDeniedReason parameter, see Table 22 and Table 23.
31

1
2
N.S0028
Table 18: Routreq Return Error to Provide Roaming Number Response Error Mapping
(GSM Foreign mode)
Routing Request Return Error Status
Error Code
Status Provide Roaming Number ack
O User Error C
3
32

N.S0028
9
10
1
2
3
4
5
6
7
4.2.1.2.2.1 Mapping of parameter values in GSM Foreign Mode
Default parameter value
Table 19 presents how the IIF shall populate the parameters of the Provide Roaming Number message to be sent to the GSM VLR. These fields do not have an equivalent in the received
Routing Request Invoke message.
8 Table 19: Provide Roaming Number Request default parameter
Parameter Name
MSC Number
Status
M
Value
ISDN number of the serving MSC.
Stored in the IIF at the time of location registration.
GSM Bearer Capability
Network Signal Info
Suppression of Announcement
Call Reference Number
GMSC address
OR Interrogation
Alerting Pattern
CCBS Call
C
C
C
C
C
C
C
C be present if the LMSI was sent to the
IIF at location updating
Shall be absent
Shall be absent
CAMEL Specific Information Element
(IE)
Not required unless Optimal Routing for LateCall Forwarding is supported by the IIF.
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)
Not required to be sent by the IIF
(however may be received as a result of Optimal Routing)
CAMEL Specific Information Element
(IE)
CCBS Specific IE
33

N.S0028
6
7
1
2
3
4
Table 20 presents how the IIF shall populate the parameters of the Routing Request Return
Result message to be sent to the ANSI-41 HLR. These fields cannot be mapped from the 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.
See Table 24 AccessDeniedReason O
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
34

N.S0028
1
8
2
3
4
5
6
7
4.2.1.2.2.2 Mapping of parameter values in ANSI-41 Foreign Mode
Default parameter value
Table 21 presents how the IIF shall populate the parameters of the Routing Request Invoke message to be sent to the ANSI-41 VLR. These fields cannot be mapped from the received
Provide Roaming Number request message.
Table 21: Routing Request Invoke default parameter
BillingID (Originating) M
MSCID (Originating MSC)
SystemMyTypeCode (IIF vendor Id)) M
AlertCode
CallingPartyNumberString1
CallingPartyNumberString2
CallingPartySubaddress
DestinationDigits
DMH_AccountCodeDigits
DMH_AlternateBillingDigits
DMH_BillingDigits
LegInformation
LocationAreaID
NoAnswerTime
OneTimeFeatureIndicator
PC_SSN (Originating MSC)
PilotBillingID
M
O
O
O
O
O
O
O
O
O
O
O
O
O
O
Shall be created by the IIF 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.
Shall be set to the IIF address.
Assigned by the IIF
May be absent
See Table 83 to Table 86
See Table 83 to Table 86
See Table 83 to Table 86
Shall be absent
Shall be absent
Shall be absent
Shall be absent
Shall be absent (not a multileg call)
Shall be absent information may be required at a later time by the ANSI VMSC to redirect the call.
Shall be absent
Shall be absent
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.
Shall be absent [multi leg call] a multi-leg call]
9
35

1
N.S0028
Table 21: Routing Request Invoke default parameter (concluded)
RedirectingNumberString
RedirectingSubAddress
SenderIdentificationNumber
O
O
O
Shall be absent
Shall be absent
Shall be absent
Termination which is also the default value)
VoiceMailboxNumber
VoiceMailPIN
-CDMAServiceOption
O
O
O treatment to apply (termination or redirection)
Shall be absent
Shall be absent
From Profile or from Location Request
Invoke if received
2
3
4
5
6
7
8
9
4.2.1.3 Error Handling
The following tables present the appropriate GSM MSC/VLR negative response to a Provide
Roaming Number message as described in GSM 09.02 [3].
Appropriate User Error value:
User Error value
Absent Subscriber
No roaming Number available
Facility Not supported
System Failure
Data Missing
Unexpected Data Value
Appropriate Provider Error value:
Provider Error value
Duplicated Invoke ID
Not supported service
Mistyped parameter
Resource limitation
Initiating Release
36

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

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

N.S0028
1
2
3
4
5
6
7
8
9
The IIF is responsible for the mapping of the AccessDeniedReason received in the
RoutingRequest Return Result or Error Code received in the Return Error to the appropriate
User Error/Provider Error in the Provide Roaming Number response message.
The following tables present the preferred mapping.
Table 24: RoutingRequest Return Result to User Error in the PRN response Error
Mapping
AccessDeniedReason received in the
RoutingRequest Return Result
User Error in the PRN response
No page Response Absent Subscriber
10
11 Table 25: Routing Request Return Error to PRN User Error Mapping
Error Code value User Error in the PRN response
12
13
39

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

N.S0028
8
9
10
11
12
13
14
15
16
17
18
4
5
6
7
1
2
3
If the message can be processed and optimal routing is supported, the IIF shall follow the procedures outlined in 4.2.3 of this document for Optimal Routing for late call forwarding.
If the message can be processed but optimal routing is not supported, the IIF shall send an ANSI_MAP_redreq Reject message. On receipt of the Reject message, the serving MSC may attempt to redirect the call by sending a
TRANUMREQ message to the IIF.
If the message cannot be processed, the IIF shall send an ANSI_MAP redreq
Return Reject message with the appropriate error code. On receipt of the Return
Reject message, the serving MSC may attempt to redirect the call by sending a
TRANUMREQ message to the IIF.
If the IIF receives an ANSI_MAP_TRANUMREQ, it shall determine if the message can be processed.
If the message can be processed, the IIF shall send an ANSI_MAP_tranumreq indicating the forwarded-to-number.
If the message cannot be processed, the IIF shall send an ANSI_MAP tranumreq indicating the reason for failure.
19
20
21
22
4.2.2.2 Mapping of Messages, Parameters & Parameter Values
4.2.2.2 presents the mapping of messages, parameters and parameter values that the IIF shall perform.
23
24
25
26
4.2.2.2.1 Mapping of Messages
These messages are the same as those in 4.2.1.2.1.
27
28
29
30
4.2.2.2.2 Mapping of Parameters
Table 26 represents how the IIF shall map the value of the parameter it has received to populate the fields of the message it shall transmit.
31
32
33
34
Table 26: ROUTEREQ Return Result to Provide Roaming Number Response parameter mapping (Option 1)
Routing Request Return Result Status Provide Roaming Number ack. Status
AccessDeniedReason = Busy,
Inactive, No Page Response or
Unavailable
C
41

N.S0028
1
2
3
4
5
Table 27: ROUTREQ Return Result to Provide Roaming Number Response Parameter
Mapping (Option 2)
Return Error
AccessDeniedReason = Busy,
Inactive, No Page Response or
Unavailable
Status Provide Roaming Number ack
O User Error = Absent Subscriber
Status
C
Default parameters value
N/A
6
7
8
9
10
4.2.2.3 Error Handling
The following table presents the appropriate GSM MSC/VLR negative response to a Provide
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
Unexpected Data Value
11
12 Appropriate Provider Error value:
Provider Error value
Duplicated Invoke ID
Not supported service
Mistyped parameter
Resource limitation
Initiating Release
Unexpected response from the peer
Service Completion Failure
No response from the peer
Invalid response received
13
42

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

N.S0028
29
30
31
32
33
34
35
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
An optimal routing for late call forwarding procedure covers the interoperability between
ANSI-41 and GSM MAP signaling to support Optimal Routing after Late Call Forwarding. This signaling is based on ANSI-41 [6] and GSM 9.02 [3].
From GSM 03.79 [2], a Late Call Forwarding procedure is defined as Call Forwarding performed after the call has been extended to the Visited PLMN (VPLMN) of the forwarding subscriber. This forwarding is based on subscription of supplementary services like Conditional
Call Forwarding on Busy, Conditional Call Forwarding on No Reply, and Conditional Call
Forwarding on Not Reachable detected in the VPLMN of the forwarding subscriber. Note that the Late Call Forwarding procedure may be invoked in the Interrogating PLMN (IPLMN) or in the VPLMN of the forwarding subscriber.
The procedure is applicable when the Subscriber has appropriate forwarding service active; and Optimal Routing is enabled.
24
25
26
27
28
16
17
18
19
20
21
22
23
4.2.3.1 Detailed Procedures
Roaming may occur either from ANSI-41 to GSM network or vice versa. Since the solutions and ultimate functionality provided to the roaming subscriber are not symmetrical, the Optimal
Routing for Late Call Forwarding procedure is different in both cases. 4.2.3.1 defines roaming procedures when roaming from GSM to ANSI-41 network and roaming from ANSI-41 to GSM network respectively.
When the IIF receives a GSM-Provide Roaming Number message, it stores GMSC Address,
Call Reference Number and OR Interrogation Indicator parameters if they are present. It then sends an ANSI-41Routing Request message to the VLR and awaits a response.
If successful ANSI-41 Routing Request response is received from VLR, it converts Temporary
Location Directory Number (TLDN) in to Mobile Subscriber Roaming Number (MSRN) and send this information to HLR in GSM-Provide Roaming Number Acknowledge message.
Otherwise, the IIF sends a GSM-Provide Roaming Number negative response to HLR and discards GMSC Address, Call Reference Number and OR Interrogation Indicator parameter information if present.
If the IIF receives ANSI-41 Redirection Request message, it shall check GMSC Address.
36
37
38
39
If GMSC Address is available, it shall map Redirection Reason parameter to Forwarding
Reason. The IIF sends this information in addition to the Call Reference Number and
Forwarding Number in GSM-Resume Call Handling message to originating MSC using GMSC
Address and await a response.
44

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

N.S0028
1
2
3
4.2.3.2 Mapping of Messages, Parameters & Parameter Values
4
5
6
7
4.2.3.2.1 Mapping of Messages
Table 29 shows the translation between GSM MAP messages and ANSI-41 MAP messages related to Optimal Routing Support for Late Call Forwarding procedure.
8 Table 29: Optimal Routing for Late Call Forwarding Message Mapping
GSM MAP Message ANSI-41 MAP Message
GSM-Provide Roaming Number Request ROUTEREQ
GSM- Provide Roaming Number
Acknowledge routereq
GSM-Resume Call Handling REDREQ
GSM-Resume Call Handling Acknowledge redreq
9
10
11
12
13
14
4.2.3.2.2 Mapping of Parameters
The following tables show the mapping of parameters, which the IIF shall perform regardless of the mode of operation.
46

3
4
-
-
-
-
-
-
-
N.S0028
1
2 Table 30: GSM Provide_Roaming_Number ↔ ANSI-41 ROUTEREQ Parameter Mapping
GSM Provide_Roaming_Number Status ANSI-41-Route_Request
(ROUTEREQ)
Status
MSC Number
MSISDN (Note 1)
GSM Bearer Capability
ISDN BC
ISDN LLC
ISDN HLC
Alerting Pattern
GMSC Address (Note 2)
Call Reference Number
OR Interrogation Indicator
-
M
R
C
C
R
R
C
C
C
C
-
MDN
-
-
-
-
-
-
-
-
MSCID (Originating MSC)
System My Type Code
M
R
M
CNIinfoASCII:
CallingPartyNumber-String 1 O
CallingPartyNumber- String 2 O
Redirecting Number O
Calling Party Subaddress O
Redirecting Subaddress O
DMHData:
DMH AccountCodeDigits
DMH AlternateBillingDigits
O
O
47

N.S0028
1
2
3
Table 30: GSM Provide_Roaming_Number ↔ ANSI-41 ROUTEREQ Parameter Mapping
(concluded)
GSM Provide_Roaming_Number Status ANSI-41-Route_Request
(ROUTEREQ)
- DMH_BillingDigits
Status
O
- MobileDirectoryNumber O
8
9
4
5
6
7
Note 1: Alternatively a provisioning number may be mapped to the MDN.
Note 2: The GMSC Address is used by the IIF to route information to the originating MSC.
IMSI
MSISDN
Table 31: Mapping of Parameter values
MSID
ESN
MDN
Billing ID
MSCID
See Automatic Call Delivery
See Automatic Call Delivery
See Automatic Call Delivery
See Automatic Call Delivery
See Automatic Call Delivery
Table 32: Provide_Roaming_Number_Response ↔ routereq Parameter Mapping
Provide_Roaming_Number_Res ponse
Roaming Number
Status
M
ANSI-41 Route_Request
(routereq)
TLDN [DGTSDEST]
Status
M
User Error C ACCDEN (Note 1) M
10
11
12
13
14
Note 1: Used only with the negative response of ANSI-41-Routing Request message.
Table 33: Mapping of Parameter Values
Roaming Number TLDN
MSCID
BILLID
User Error ACCDEN
See Automatic Call Delivery
See Automatic Call Delivery
See Automatic Call Delivery
See Automatic Call Delivery
48

N.S0028
1
2 Table 34: Resume_Call_Handling ↔ REDREQ Parameter Mapping
GSM Resume_Call_Handling
Call Reference Number
Basic Service group
Status
M
M
ANSI-41 Redirection_Request
(REDREQ)
-
-
Status
ForwardingData:
Forwarding Reason M REDREASON
Forwarded-to-Number M -
Notification to Calling Party
Forwarded-to-Subaddress
CUG Interlock
CUG Outgoing Access
Originating CSI
M
C
C
C
C
-
-
-
-
-
M
3
4
5
6
IMSI
Forwarding
Reason
Table 35: Mapping of Parameters Values
MSID
MSN
BILLID
See Automatic Call Delivery
See Automatic Call Delivery
See Automatic Call Delivery
Resume_Call_Handling_Respon se
Table 36: Resume_Call_Handling_Response ↔ redreq Parameter Mapping
Status Redirection_Request Status
7
8
49

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

N.S0028
26
27
28
29
30
31
1
32
33
9
10
11
5
6
7
8
2
3
4
12
13
14
15
16
17
18
19
20
21
22
4.2.3.3 Error Handling
Negative Response of GSM-Provide Roaming Number
The serving MSC determines that it is unable to provide a routing number and returns this indication to the IIF via a GSM Provide Roaming Number RETURN ERROR component with an error code.
Negative Response of GSM-Resume Call Handling
The Originating MSC determines that it is unable to redirect the call and returns this indication to the IIF via a GSM Resume Call Handling RETURN ERROR component with an error code.
Negative Response of ANSI-41-Routing Request (ROUTEREQ)
If TERMTRMT (TerminationTreatment) indicates termination to an MS, the Serving MSC consults its internal data structures to determine if the MS is already engaged in a call on this
MSC. If termination is to a voice mailbox, the Serving MSC verifies the VMS availability. Finding the MS or VMS busy (or otherwise unable to receive calls), the Serving MSC returns an appropriate indication to the IIF in the ANSI-41 Routing Request response message (routreq).
Parameters included are MSCID and ACCDEN. The IIF then forwards the response of ANSI-41
Routing Request message to the HLR.
Negative Response of ANSI-41-Redirection Request (REDREQ)
The Originating MSC determines that it is unable to redirect the call and returns this indication to the Serving MSC via an ANSI-41-Redirection Request RETURN ERROR component with an error code.
23
24
4.2.3.3.1 Error Code Mapping
25 Table 39: Provide_Roaming_Number to Routing_Request Error Mapping
Provide_Roaming_Number User and
Provider Errors
OR not allowed (Note 1)
Routing_Request Error Codes
-
Note 1: If 'OR not allowed' is returned, the IIF should retry the Provide_Roaming_Number operation without the OR indication to allow for normal routing
For other error mappings see Automatic Call Delivery, Error Handling, GSM Foreign Mode.
Table 40: Routing_Request to Provide_Roaming_Number Error Mapping
Routing_Request Error Codes Provide_Roaming_Number User Errors
- -
For error mappings see Automatic Call Delivery, Error Handling, ANSI136 41 Foreign Mode.
51

N.S0028
1
3
4
5
6
2
7
8
Table 41: Resume_Call_Handling to Redirection_Request Error Mapping
Resume_Call_Handling
User and Provider Errors
OR not allowed (Note 1)
Forwarding failed
Duplicated Invoke ID
Not Supported Service
Mistyped Parameter
Resource Limitation
Initiating Release
Unexpected Response From the Peer
Service Completion Failure
No Response from the Peer
Invalid Response Received
Redirection_Request
Error Codes
SystemFailure
SystemFailure
SystemFailure
System Failure
System Failure
System Failure
SystemFailure
SystemFailure
SystemFailure
SystemFailure
SystemFailure
Note 1: This error should not occur. The process requires the GMSC support OR.
Table 42: Redirection_Request to Resume_Call_Handling Error Mapping
Redirection_Request
Error Codes
MissingParameter
UnrecognizedParameterValue
UnrecognizedMIN
UnrecognizedESN
MIN/HLRMismatch
OperationSequenceProblem
TrunkUnavailable
SystemFailure
FeatureInactive
ParameterError
OperationNotSupported
ResourceShortage
Resume_Call_Handling
User Errors
OR-NotAllowed ForwardingFailed
OR-NotAllowed ForwardingFailed
OR-NotAllowed ForwardingFailed
OR-NotAllowed ForwardingFailed
OR-NotAllowed ForwardingFailed
OR-NotAllowed ForwardingFailed
OR-NotAllowed ForwardingFailed
OR-NotAllowed ForwardingFailed
OR-NotAllowed ForwardingFailed
OR-NotAllowed ForwardingFailed
OR-NotAllowed ForwardingFailed
OR-NotAllowed ForwardingFailed
52

N.S0028
1
2
3
9
10
11
6
7
8
4
5
12
Because of the similarities in the procedures and signaling between the supplementary service activation and deactivation cases, these are combined into one description. Furthermore, 4.3.1 makes use of terms such as "Activate/Deactivate" or
"MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS". In all cases in which such terms are used, for activation cases the terms "Activate" or "MAP_ACTIVATE_SS" terms apply. For deactivation cases, the terms "Deactivate" or "MAP_DEACTIVATE_SS" apply.
27
28
35
36
37
38
39
29
30
31
32
33
34
13
14
15
16
17
18
19
20
21
22
23
24
25
26
4.3.1.1 Detailed Procedures
4.3.1.1 contains the procedures in the IIF for the case in which the subscriber requests either an activation or deactivation of one of the following supplementary services while roaming in foreign mode (i.e., while roaming in a network of a technology different from that of its home network):
•
Call Waiting (in both GSM and ANSI136 41 foreign modes)
•
Call Forwarding Unconditional (in both GSM and ANSI136 41 foreign modes)
•
Call Forwarding Busy (in both GSM and ANSI136 41 foreign modes)
•
Call Forwarding No Reply (in ANSI136 41 foreign-mode only)
•
Call Forwarding Not Reachable (in ANSI136 41 foreign-mode only)
•
Call Forwarding No Answer (in GSM foreign-mode only)
While in GSM Foreign Mode, the principal role of the IIF, with respect to supplementary service activation and deactivation, is that of handling the GSM MAP_ACTIVATE_SS message (for activation) or the GSM MAP_DEACTIVATE_SS message (for deactivation), as follows: If the
IIF receives an GSM MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS message from the GSM serving system, it shall verify the correct format and content of the message as described in
GSM 09.02 [3].
For cases in which the received message contains a "Basic service" parameter, the IIF shall also verify that the request for activation/deactivation applies to (at least) speech. If the received request does not include "speech" as one of the services to which the request applies, the IIF shall respond with either a GSM MAP_ACTIVATE_SS or GSM MAP_DEACTIVATE_SS
Response message that includes a "User error" parameter with a value of "Illegal SS
53

N.S0028
10
11
12
13
5
6
7
8
9
1
2
3
4
22
23
24
25
26
27
14
15
16
17
18
19
20
21 operation". Note that cases in which no "Basic service" parameter is included in the received message are acceptable, since, by default, no "Basic service" parameter indicates that the request applies to all services.
If the format and content of the message is correct, the IIF shall determine the location of the subscriber’s HLR and send to it an ANSI-41 FeatureRequest INVOKE message populated as described in Table 44 and Table 48. If a failure occurs at the IIF on reception of the GSM
MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS message (e.g. missing data), the procedures described in GSM 09.02 [3] are applicable to the IIF.
If, in response to the ANSI-41 FeatureRequest INVOKE, the IIF receives an ANSI-41
FeatureRequest Return Result message with a FeatureResult parameter set to successful, the
IIF shall send a GSM MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS Response message back towards the serving system populated as described in Table 45.
If, in response to the ANSI-41 FeatureRequest INVOKE, the IIF instead receives an ANSI-41
FeatureRequest Return Result message with a FeatureResult parameter set to unsuccessful, the IIF shall send a GSM MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS Response message back towards the serving system populated as described in Table 45 and Table 53.
If, in response to the ANSI-41 FeatureRequest INVOKE, the IIF instead receives an ANSI-41
FeatureRequest Return Error message, the IIF shall send a GSM MAP_ACTIVATE_SS/
MAP_DEACTIVATE_SS Response message back towards the serving system populated as described in Table 54.
Note that successful supplementary service activation/deactivation cases in GSM foreign mode may result in the subscriber's ANSI-41 HLR sending out an ANSI-41 QUALDIR message to the serving system. For these cases, the IIF would need to map the message to a GSM MAP
Insert Subscriber Data message. The mapping of an ANSI-41 QUALDIR message to a GSM
MAP Insert Subscriber Data message is covered in the Subscriber Data Management.
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
4.3.1.1.2 ANSI136 41 Foreign Mode
While in ANSI136 41 Foreign Mode, the principal role of the IIF, with respect to supplementary service activation, is that of handling the ANSI-41 FeatureRequest INVOKE message, as follows: If the IIF receives an ANSI-41 FeatureRequest INVOKE message from the ANSI-41 serving system, it shall verify the correct format and content of the message as described in
ANSI-41 [6].
If format and content of the message is correct, the IIF shall determine the location of the subscriber’s HLR and send a GSM MAP_ACTIVATE_SS/MAP_DEACTIVATE_SS Request message populated as described inTable 44 and Table 50.
For cases in which the FeatureRequest INVOKE message includes a feature code corresponding to Call Forwarding No Answer, and if the IIF is configured to do so, the IIF may send two MAP_ACTIVATE_SS/ MAP_DEACTIVATE_SS messages, one indicating Call
Forwarding No Reply and the other indicating Call Forwarding Not Reachable. These messages may be sent in parallel. The mapping in Table 44 and Table 50 would still be applicable.
For the cases of failure at the IIF on reception of the ANSI-41 FeatureRequest Return Result message (e.g. parameter error, unrecognized subscriber), the procedures described in ANSI-41
[6] are applicable to the IIF.
54

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

N.S0028
1
9
10
2
3
4.3.1.2 Mapping of Messages, Parameters & Parameter Values
4
5
6
7
4.3.1.2.1 Mapping of Messages
The following table shows the mapping of messages for the Activation and Deactivation of
Supplementary Services.
8 Table 43: Supplementary Service Activation and Deactivation Message Mapping
GSM MAP Message
Activate SS Request
Deactivate SS Request
Activate SS Request Response
ANSI-41 MAP Message
FEATREQ
FEATREQ featreq
Deactivate SS Request Response featreq
11
12
13
14
15
16
4.3.1.2.2 Mapping of parameters
The following tables show the mapping between the parameters in GSM MAP messages and parameters in the corresponding ANSI-41 messages. The relationships between the parameters shown in the tables are meant to be bi-directional.
Table 44: Activate/Deactivate SS Request ↔ FEATREQ Parameter Mapping
Activate/Deactivate SS Request Status FEATREQ Status
Basic services
-
C -
MSID (Either MIN or IMSI) M
17
18
56

N.S0028
1
2 Table 44: Activate/Deactivate SS Request ↔ FEATREQ Parameter Mapping (concluded)
Activate/Deactivate SS Request Status FEATREQ Status
3
4
57

N.S0028
1
2
Table 45: Activate/Deactivate SS Response ↔ Feature Request Return Result Parameter
Mapping
Status Feature Request Return Result Status Activate/Deactivate SS
Response
Call forwarding information
Call barring information
C
C
-
-
User Error
Provider Error
-
C
O
Announcement List
-
Access Denied Reason
O
O
3
4
5
6
7
8
Note 1: The FeatureResult parameter shall be mapped to “Unsuccessful” if a User Error or a
Provider Error is received in the ACTIVATE/DEACTIVATE SS RESPONSE. Or, a User Error mapped to an appropriate value shall be returned if the FeatureResult parameter is set to
“Unsuccessful”. See Table 53
58

N.S0028
10
11
12
13
14
15
1 Table 46: Activate/Deactivate SS Response ↔ Feature Request Return Error Mapping
Activate/Deactivate SS
Response
Call forwarding information
Call barring information
C
C
SS-Data C
User Error C Error Code
Provider Error O
Status
O
2
3
4
5
6
7
8
4.3.1.2.2.1 Mapping of parameter values in GSM Foreign Mode
Activate/Deactivate SS Request to Feature Request Invoke mapping
This table represents how the IIF shall map the value of the parameter it has received to populate the fields of the message it shall transmit.
9 Table 47: Activate/Deactivate SS Request to FEATREQ Parameter Mapping
Activate/Deactivate SS Request Status FEATREQ Status
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.
Note that no parameter in the FeatureRequest INVOKE message currently supports the mapping from the GSM MAP parameter "Basic service". The "GSM Foreign Mode" part of
4.3.2 SS Registration and Erasure contains procedures pertaining to the handling of the "Basic service" parameter, when included in the received GSM MAP message.
59

N.S0028
1
2
3
4
5
6
Default parameter values
This table presents how the IIF shall populate the parameters of the Feature Request Invoke message to be sent to the ANSI-41 VLR. These fields cannot be mapped from the received
Activate/Deactivate SS request message.
Table 48: FEATREQ default parameter
9
10
7
8
11
12
13
14
15
16
17
MSID (Either MIN or IMSI)
BillingID (Originating)
CallingPartyNumberString1
CallingPartyNumberString2
CallingPartySubaddress
ConferenceCallingIndicator
MSCID (Serving)
M
O
O
O
O
O
O previously received during GSM
MAP_OPEN procedures.
Shall be obtained from mapping from the
IMSI received previously (during GSM
MAP_OPEN procedures)
Not required to be included in message.
Not required to be included in message.
Not required to be included in message.
Not required to be included in message.
Not required to be included in message. from IIF’s data.
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.
May be included from IIF data.
Not required to be included in message.
May be included from IIF data.
May be included from IIF data.
MSCIdentificationNumber
OneTimeFeatureIndicator
PC_SSN
SenderIdentificationNumber
O
O
O
O
IIF’s MAP interworking capabilities.
Feature Request Return Result to Activate/Deactivate SS Response mapping
Mapping of parameter values
For the successful case (in which a FeatureRequest Return Result is received with the
FeatureResult parameter set to “successful”) there are no meaningful parameter mappings to support. For those successful cases, the “Default parameter values” describes how the corresponding GSM Activate/Deactivate SS Response message shall be populated. For the unsuccessful cases, 4.3.1.3 Error Handling describes the appropriate mappings.
60

N.S0028
1
2
3
4
5
6
7
8
9
Default parameter values
This table describes the population of the parameters in the Activate/Deactivate SS Response message for successful activation/deactivation cases (i.e. when the received Feature Request
Return Result contains a FeatureResult parameter set to “successful”).
Table 49: Activate/Deactivate SS Response default parameter values
Activate/Deactivate SS
Response
Call forwarding information C
Call barring 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.
Subscriber activation/deactivation of call barring services not required to be supported by IIF, thus population of this parameter not required. 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.
61

N.S0028
1
5
6
7
8
2
3
4
4.3.1.2.2.2 Mapping of parameter values in ANSI136 41 Foreign Mode
Feature Request Invoke to Activate/Deactivate SS Request mapping
Table 50 represents how the IIF shall map the value of the parameter it has received to populate the fields of the message it shall transmit.
17
18
19
20
21
22
23
24
25
26
27
9 Table 50: Feature Request Invoke to Activate/Deactivate SS Request Parameter Mapping
FEATREQ
Digits (Dialed)
Status
M
Activate/Deactivate SS Request
SS-Code
The IIF shall support a table mapping ANSI-41 feature codes to GSM supplementary service operations.
Status
M
10
11
12
13
14
15
Default parameter values
Table 51 presents how the IIF shall populate the parameters of the Activate/Deactivate SS
Request message to be sent to the GSM HLR. These fields do not have an equivalent in the received Feature Request Invoke message.
16 Table 51: Activate/Deactivate SS Request default parameter
Parameter Name
Basic services
Status
C
Value
Not required to be included.
(Activation/deactivation operation shall apply to all service groups when absent.)
GSM Activate/Deactivate SS Response to ANSI-41 Feature Request Return Result mapping
Mapping of parameter values
For the successful case (in which there’s no User error or Provider Error in the received GSM
Activate/Deactivate SS Response message), there are no meaningful parameter mappings to support. For those successful cases, the “Default parameter values” describes how the corresponding ANSI-41 FeatureRequest Return Result shall be populated. For the unsuccessful cases, Table 46 describes the appropriate mappings.
62

N.S0028
1
2
3
4
5
6
7
8
Default parameter values
Table 52 presents how the IIF shall populate the parameters of the Feature Request Return
Result message to be sent to the ANSI-41 VLR for successful activation cases. Note that the population of the message may differ for non-activation cases.
Table 52: FeatureRequest Return Result default parameter
Parameter Name
FeatureResult
AccessDeniedReason
ActionCode
AnnouncementList
CallingPartyNumberString1
CallingPartyNumberString2
CallingPartySubaddress
CarrierDigits
ConferenceCallingIndicator
Digits (Dialed)
DMH_AccountCodeDigits
DMH_AlternateBillingDigits
DMH_BillingDigits
DMH_RedirectionIndicator
GroupInformation
MobileDirectoryNumber
NoAnswerTime
OneTimeFeatureIndicator
PACAIndicator
PilotNumber
RedirectingNumberDigits
RedirectingNumberString
RedirectingSubaddress
RoutingDigits
TerminationList
TerminationTriggers
Status
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
M
O
O
O
Default Value
Set to “successful”
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
63

N.S0028
1
2
3
4
5
6
7
8
9
10
4.3.1.3 Error Handling
The following table presents the appropriate GSM MSC/VLR negative response to an
Activate/Deactivate SS message as described in GSM 09.02 [3].
Appropriate User Error value:
User Error value
System Failure
Data Missing
Unexpected Data Value
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
Appropriate Provider Error value:
Provider Error value
Duplicated Invoke ID
Not supported service
Mistyped parameter
Resource limitation
Initiating Release
Unexpected response from the peer
Service Completion Failure
No response from the peer
Invalid response received
64

N.S0028
6
7
8
1
2
3
4
5
9
10
The following table presents the appropriate ANSI-41 MSC/VLR negative response to a
Feature Request Invoke message as described in ANSI-41 [6].
Appropriate AccessDeniedReason parameter values in the FeatureRequest Return Result
(Note, however, that none of these values are applicable to the feature activation scenarios):
AccessDeniedReason
Unassigned directory number
Inactive
Busy
No page Response
Unavailable
TerminationDenied
Appropriate Error Code parameter value in the Return Error message:
Error Code value
UnrecognizedMIN
UnrecognizedESN
MIN/HLRMismatch
OperationSequenceProblem
ResourceShortage
OperationNotSupported
ParameterError
SystemFailure
UnrecognizedParameterValue
65

N.S0028
1
2
3
4
5
6
7
8
9
10
11
12
13
For cases in which a FeatureRequest Return Result is received by the IIF with a FeatureResult parameter set to “unsuccessful”, if the AnnouncementList parameter is also present, the IIF may use the contents of the AnnouncementList in order to provide a better mapping to the User
Error in the Activate/Deactivate SS Response message, as shown in Table 53:
Table 53: FeatureRequest Return Result to User Error in the Activate/Deactivate SS
Response Error Mapping
FeatureRequest Return Result
FeatureResult ="unsuccessful"
AnnouncementList="UnauthorizedFeature
Code"
Activate/Deactivate SS Response
User Error = "SS subscription violation"
Or
User Error = “Illegal SS Operation”
User Error="System Failure" FeatureResult ="unsuccessful"
AnnouncementList not present
Table 54: FeatureRequest Return Error to Activate/Deactivate SS Response Error
Error Code value
Mapping
User Error
14
15
66

N.S0028
1
2
3
4
5
6
7
8
4.3.1.3.2 ANSI136 41 Foreign Mode
The IIF is responsible for the translation of the User Error/Provider Error received in the
Activate/Deactivate SS Response to either the appropriate FeatureRequest Return Result message (with FeatureResult set to “unsuccessful” and, if supported, the AnnouncementList parameter) or Error Code in the FeatureRequest Return Error, as shown in the following two tables (Table 55 and Table 56).
9
10
Table 55: Activate/Deactivate SS Response User Error to FeatureRequest Return Result
Mapping
FeatureRequest Return Result Activate/Deactivate SS Response User
Error
SS subscription violation FeatureResult="unsuccessful"
AnnouncementList =
“UnauthorizedFeatureCode” (if parameter supported by serving system)
11
12
67

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

N.S0028
1
2
3
4
5
Table 57: Activate/Deactivate SS Response Provider Error to Feature Request Return
Error Mapping
Provider Error value received in
Activate/Deactivate SS Response
Duplicated Invoke ID
Not supported service
Mistyped parameter
Resource limitation
Initiating Release
Unexpected response from the peer
Service Completion Failure
No response from the peer
Invalid response received
Feature Request Return Error
Error Code
System Failure
System Failure
System Failure
System Failure
System Failure
System Failure
System Failure
System Failure
System Failure
69

N.S0028
1
2
3
4
5
4.3.2.1 Registration
13
14
15
16
17
6
7
8
9
10
11
12
4.3.2.1.1 contains the procedures in the IIF for the case in which the subscriber requests registration of information in association with one of the following supplementary services while roaming in foreign mode (i.e., while roaming in a network of a technology different from that of its home network):
•
Call Forwarding Unconditional (in both GSM and ANSI136 41 foreign modes)
•
Call Forwarding Busy (in both GSM and ANSI136 41 foreign modes)
•
Call Forwarding No Reply (in ANSI136 41 foreign-mode only)
•
Call Forwarding Not Reachable (in ANSI136 41 foreign-mode only)
•
Call Forwarding No Answer (in GSM foreign-mode only)
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
4.3.2.1.1.1 GSM Mode
While in GSM Foreign Mode, the principal role of the IIF, with respect to supplementary service registration is that of handling the GSM MAP_REGISTER_SS as follows: If the IIF receives an
GSM MAP_REGISTER_SS message from the GSM serving system, it shall verify the correct format and content of the message as described in GSM 09.02 [3].
For cases in which the received message contains a "Basic service" parameter, the IIF shall also verify that the request for registration applies to (at least) speech. If the received request does not include "speech" as one of the services to which the request applies, the IIF shall respond with either a GSM MAP_REGISTER_SS Response message that includes a "User error" parameter with a value of "Illegal SS Operation". Note that cases in which no "Basic service" parameter is included in the received message are acceptable, since, by default, no
"Basic service" parameter indicates that the request applies to all services.
If the format and content of the message is correct, the IIF shall determine the location of the subscriber’s HLR and send to it an ANSI-41 FeatureRequest INVOKE message populated as described in Table 59, Table 62 and Table 63. If a failure occurs at the IIF on reception of the
GSM MAP_REGISTER_SS message (e.g. missing data), the procedures described in GSM
09.02 [3] are applicable to the IIF.
70

N.S0028
5
6
7
8
1
2
3
4
9
10
11
12
13
14
15
16
17
If, in response to the ANSI-41 FeatureRequest INVOKE, the IIF receives an ANSI-41
FeatureRequest Return Result message with a FeatureResult parameter set to successful, the
IIF shall send a GSM MAP_REGISTER_SS Response message back towards the serving system populated as described in Table 60 and Table 64.
If, in response to the ANSI-41 FeatureRequest INVOKE, the IIF instead receives an ANSI-41
FeatureRequest Return Result message with a FeatureResult parameter set to unsuccessful, the IIF shall send a GSM MAP_REGISTER_SS Response message back towards the serving system as described in 4.3.2.2.3 Error Handling.
If, in response to the ANSI-41 FeatureRequest INVOKE, the IIF instead receives an ANSI-41
FeatureRequest Return Error message, the IIF shall send a GSM MAP_REGISTER_SS
Response message back towards the serving system as described in 4.3.2.2.3 Error Handling.
Note that successful supplementary service registration cases in GSM foreign mode may result in the subscriber's ANSI-41 HLR sending out an ANSI-41 QUALDIR message to the serving system. For these cases, the IIF would need to map the message to a GSM MAP Insert
Subscriber Data message. The mapping of an ANSI-41 QUALDIR message to a GSM MAP
Insert Subscriber Data message is covered in the Subscriber Data Management.
18
19
32
33
34
35
25
26
27
28
29
30
31
20
21
22
23
24
36
37
38
39
40
41
42
43
44
45
46
47
48
4.3.2.1.1.2 ANSI136 41 Foreign Mode
While in ANSI136 41 Foreign Mode, the principal role of the IIF, with respect to supplementary service registration, is that of handling the ANSI-41 FeatureRequest INVOKE message, as follows: if the IIF receives an ANSI-41 FeatureRequest INVOKE message from the ANSI-41 serving system, it shall verify the correct format and content of the message as described in
ANSI-41 [6]. If format and content of the message is correct, the IIF shall determine the location of the subscriber’s HLR and send a GSM MAP_REGISTER_SS Request message populated as described in in Table 59, Table 66 and Table 67. For cases in which the
FeatureRequest INVOKE message includes a feature code corresponding to Call Forwarding
No Answer, and if the IIF is configured to do so, the IIF may send two MAP_REGISTER_SS messages, one indicating Call Forwarding No Reply and the other indicating Call Forwarding
Not Reachable. These messages may be sent in parallel. The mapping in Table 59, Table 66 and Table 73 should still be applicable.
For the cases of failure at the IIF on reception of the ANSI-41 FeatureRequest Return Result message (e.g. parameter error, unrecognized subscriber), the procedures described in ANSI-41
[6] are applicable to the IIF.
If, in response to the a GSM MAP_REGISTER_SS Request message, the IIF receives a GSM
MAP_REGISTER_SS Response message with neither a User Error nor Provider Error parameter, the IIF shall send an ANSI-41 FeatureRequest Return Result message back towards the serving system populated as described in Table 60 and Table 67. For those cases in which two requests had been previously sent by the IIF, the IIF would wait until receiving the responses to both requests before sending the FeatureRequest Return Result message. For cases in which both responses indicate success, the mapping in Table 60 may be applied to either of the responses (as an IIF implementation option). For cases in which one of the responses indicates success and the other failure, the mapping in Table 60 applies to the successful response.
If, in response to the GSM MAP_REGISTER_SS Request message, the IIF instead receives a
GSM MAP_REGISTER_SS Response message with a User Error, the IIF shall send either an
ANSI-41 FeatureRequest Return or a Return Error as described in 4.3.2.2.3 Error Handling.
71

N.S0028
1
2
3
4
5
6
7
8
9
10
11
If a Provider Error parameter is included in the received GSM MAP_REGISTER_SS Response message, the IIF shall send an ANSI-41 FeatureRequest Return Error message populated with an Error Code as described in 4.3.2.2.3 Error Handling. For cases in which two requests had been previously sent by the IIF, and both responses indicate failure, the procedures described may be applied to either of the responses (as an IIF implementation option).
Note that successful supplementary service registration cases in ANSI136 41 foreign mode may result in the subscriber's GSM HLR sending out a GSM MAP Insert Subscriber Data message to the serving system. For these cases, the IIF would need to map the message to an ANSI-41 QUALDIR message. The mapping of GSM MAP Insert Subscriber Data message to an ANSI-41 QUALDIR message is covered in the Subscriber Data Management.
12
13
14
15
16
4.3.2.1.2 Mapping of Messages, Parameters & Parameter Values
4.3.2.1.2 presents the mapping of messages, parameters and parameter values that the IIF shall perform.
17
18
19
4.3.2.1.2.1 Mapping of Messages
Table 58 shows the mapping of messages for Supplementary Service Registration
20 Table 58: Supplementary Service Registration Message Mapping
GSM MAP Message
REGISTER SS REQUEST
ANSI-41 MAP Message
FEATREQ
REGITER SS REQUEST RESPONSE featreq
21
72

8
9
10
N.S0028
1
2
3
4
5
6
7
4.3.2.1.2.2 Mapping of parameters
The following tables show the mapping between the parameters in GSM MAP messages and parameters in the corresponding ANSI-41 messages. The relationships between the parameters shown in the tables are meant to be bi-directional.
Table 59: Register SS Request ↔ FEATREQ parameter mapping
REGISTER SS REQUEST Status FEATREQ Status
M
C Forwarded-to number with subaddress
Basic services
No reply condition time
EMLPP default priority
C
C
C
-
-
-
- MSID (Either MIN or IMSI) M
73

N.S0028
1 Table 60: Register SS Response ↔ Feature Request Return Result Parameter Mapping
Register SS Response
EMLPP default priority
Forwarding information
User Error
Provider Error
Status
C
C
C
O
Feature Request Return Result
-
-
FeatureResult (Note 1)
Announcement List
-
Status
M
O
- Access Denied Reason O
2
3
4
5
6
7
8
Note 1: The FeatureResult parameter shall be mapped to an error value if a User Error is received in the REGISTER SS RESPONSE, or the User Error shall be mapped to an appropriate value if an Unsuccessful value is received in Feature Result. See Table 68.
74

1
4
5
2
3 .
N.S0028
Table 61: Register SS Response ↔ Return Error Parameter Mapping
Register SS Response
EMLPP default priority
Forwarding information
User Error
Provider Error
C
C
C
O
Status Return Error
Error Code
Status
O
75

N.S0028
1
9
10
11
12
13
14
2
3
4
5
6
7
4.3.2.1.2.2.1 Mapping of parameter values in GSM Foreign Mode
Register SS Request to Feature Request Invoke mapping
Table 62 represents how the IIF shall map the value of the parameter it has received to populate the fields of the message it shall transmit.
8 Table 62: Register SS Request to Feature Request Invoke parameter mapping
Register SS Request
SS-Code/
Forwarded-to number with subaddress
Status
M
C
FEATREQ
Digits (Dialed)
This parameter is made up of 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.
Status
M
Note that no parameter in the FeatureRequest INVOKE message currently supports the mapping from the GSM MAP parameter "Basic service". The "GSM Foreign Mode" of
4.3.2 SS Registration and Erasure contains procedures pertaining to the handling of the "Basic service" parameter, when included in the received GSM MAP message.
76

N.S0028
1
2
3
4
5
6
7
8
Default parameter values
Table 63 presents how the IIF shall populate the parameters of the Feature Request Invoke message to be sent to the ANSI-41 HLR. These fields cannot be mapped from the received
Register SS request message.
Table 63: FEATREQ default parameter
9
10
11
12
13
14
15
16
MSID (Either MIN or IMSI)
BillingID (Originating)
CallingPartyNumberString1
CallingPartyNumberString2
CallingPartySubaddress
ConferenceCallingIndicator
M
O
O
O
O
O obtained from GSM MAP_OPEN information.
Shall be obtained from mapping from the
IMSI previously obtained from GSM
MAP_OPEN information.
Not required to be included in message.
Not required to be included in message.
Not required to be included in message.
Not required to be included in message.
Not required to be included in message.
MSCID (Serving)
OneTimeFeatureIndicator
PC_SSN
SenderIdentificationNumber
O
O
O
O from IIF’s data.
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.
Serving MSC's address.
Not required to be included in message.
May be included from IIF data.
May be included from IIF data.
IIF’s MAP interworking capabilities.
Feature Request Return Result to Register SS Response mapping
Mapping of parameter values
For the successful case (in which a FeatureRequest Return Result is received with the
FeatureResult parameter set to “successful”) there are no meaningful parameter mappings to
77

N.S0028
1
2
3
4
5
6
7
8
9
10
11
12
13 support. For those successful cases, the “Default parameter values” describes how the corresponding GSM Register SS Response message shall be populated. For the unsuccessful cases, refer to 4.3.2.2.3 Error Handling.
Default parameter values
Table 64 describes the population of the parameters in the Register SS Response message for successful registration cases (i.e. when the received Feature Request Return Result contains a
FeatureResult parameter set to “successful”).
Table 64: Register SS Response default parameter values
Register SS Response
Call forwarding information
EMLPP default priority
Status
C
C
Default Value
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.
Not applicable. May be ignored when received.
78

N.S0028
1
2
3
4
5
6
7
4.3.2.1.2.2.2 Mapping of parameter values ANSI136 41
Feature Request Invoke to Register SS Request mapping
Foreign Mode
Table 65 represents how the IIF shall map the value of the parameter it has received to populate the fields of the message it shall transmit.
8
Digits (Dialed)
Digits (Dialed)
M
M
SS-Code
The IIF shall support a table mapping ANSI-41 feature codes to GSM supplementary service operations (e.g. CFB registration)
Forwarded-to number with subaddress
Populated from the forwarded-to number portion of the Digits
(Dialed) parameter.
M
M
9
10
11
12
13
Default parameter values
Table 66 presents how the IIF shall populate the parameters of the Register SS Request message to be sent to the GSM HLR. These fields do not have an equivalent in the received
Feature Request Invoke message.
14
FEATREQ
Table 65: FEATREQ to Register SS Request parameter mapping
Status Register SS Request Status
15
16
Parameter Name
Basic services
No reply condition time
EMLPP default
Table 66: Register SS Request default parameter
Status Value
C Not required to be included. (Registration operation shall apply to all service groups when absent.)
C
C
Not required to be included.
Not required to be included.
79

N.S0028
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
16
17
18
GSM Register SS Response to ANSI-41 Feature Request Return Result mapping
Mapping of parameter values
For the successful case (in which there’s no User error or Provider Error in the received GSM
Register SS Response message), there are no meaningful parameter mappings to support.
For those successful cases, the “Default parameter values” describes how the corresponding
ANSI-41 FeatureRequest Return Result shall be populated. For the unsuccessful cases, refer to 4.3.2.2.3 Error Handling.
Default parameter values
Table 67 presents how the IIF shall populate the parameters of the Feature Request Return
Result message to be sent to the ANSI-41 VLR for successful supplementary service registration cases. Note that the population of the message may differ for non-registration cases.
Table 67: FeatureRequest Return Result default parameter
Parameter Name
FeatureResult
AccessDeniedReason
ActionCode
AnnouncementList
CallingPartyNumberString1
CallingPartyNumberString2
CallingPartySubaddress
CarrierDigits
ConferenceCallingIndicator
Digits (Dialed)
DMH_AccountCodeDigits
DMH_AlternateBillingDigits
DMH_BillingDigits
DMH_RedirectionIndicator
GroupInformation
MobileDirectoryNumber
NoAnswerTime
OneTimeFeatureIndicator
Status Default Value
M
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
Set to “successful”
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
80

3
4
1
2 Table 67: FeatureRequest Return Result default parameter (concluded)
Parameter Name
PACAIndicator
PilotNumber
RedirectingNumberDigits
RedirectingNumberString
RedirectingSubaddress
RoutingDigits
TerminationList
TerminationTriggers
O
O
O
O
Status Default Value
O
O
Not required to be included.
Not required to be included.
O
O
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
N.S0028
81

N.S0028
1
2
3
7
8
9
10
4
5
6
The error handling procedures specified for supplementary service activation apply also for the supplementary service registration case, with the following modification: the User Error values
"SS subscription violation", "Negative PW Check", and "Number of PW Attempts Violation", although valid for the activation case, are not valid for the registration case. If any of those values are received in the User Error parameter of a Register SS Response, they may be mapped to "System Failure". Also, the IIF may not include any of those User Error values in the Register SS Response messages it sends.
11
12
Table 68: FeatureRequest Return Result to User Error in the Register SS Response mapping
FeatureRequest Return Result
FeatureResult ="unsuccessful"
AnnouncementList="UnauthorizedFeature
Code"
FeatureResult ="unsuccessful"
AnnouncementList not present
User Error in the Register SS Response
User Error = "SS subscription violation"
User Error="System Failure"
13
14
15
4.3.2.2 Erasure
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
4.3.2.2.1.1
4.3.2.2.1 contains the procedures in the IIF for the case in which the subscriber requests erasure (de-registration) of information in association with one of the following supplementary services while roaming in foreign mode (i.e., while roaming in a network of a technology different from that of its home network):
•
Call Forwarding Unconditional (in both GSM and ANSI136 41 foreign modes)
•
Call Forwarding Busy (in both GSM and ANSI136 41 foreign modes)
•
Call Forwarding No Reply (in ANSI136 41 foreign-mode only)
•
Call Forwarding Not Reachable (in ANSI136 41 foreign-mode only)
•
Call Forwarding No Answer (in GSM foreign-mode only)
GSM Foreign Mode
82

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

N.S0028
13
14
15
16
17
8
9
10
11
12
18
19
20
21
22
23
24
25
1
2
3
4
5
6
7
26
27
28
29
30
31
32 feature code corresponding to Call Forwarding No Answer, and if the IIF is configured to do so, the IIF may send two MAP_ERASE_SS messages, one indicating Call Forwarding No Reply and the other indicating Call Forwarding Not Reachable. These messages may be sent in parallel.
The mapping in Table 70,Table 75 and Table 77 would still be applicable.
For the cases of failure at the IIF on reception of the ANSI-41 FeatureRequest Return Result message (e.g. parameter error, unrecognized subscriber), the procedures described in ANSI-41
[6] are applicable to the IIF.
If in response to the a GSM MAP_ERASE_SS Request message, the IIF receives a GSM
MAP_ERASE_SS Response message with neither a User Error nor Provider Error parameter, the IIF shall send an ANSI-41 FeatureRequest Return Result message back towards the serving system populated as described in Table 71. For those cases in which two requests had been previously sent by the IIF, the IIF would wait until receiving the responses to both requests before sending the FeatureRequest Return Result message. For cases in which both responses indicate success, the mapping in Table 71 may be applied to either of the responses (as an IIF implementation option). For cases in which one of the responses indicates success and the other failure, the mapping in Table 71, Table 75 and Table 86 applies to the successful response.
If, in response to the GSM MAP_ERASE_SS Request message, the IIF instead receives a
GSM MAP_ERASE_SS Response message with a User Error, the IIF shall send either an
ANSI-41 FeatureRequest Return Result or a Return Error as described in 4.3.2.2.3 Error
Handling If a Provider Error parameter is included in the received GSM MAP_ERASE_SS
Response message, the IIF shall send an ANSI-41 FeatureRequest Return Error message populated with an Error Code. For cases in which two requests had been previously sent by the
IIF, and both responses indicate failure, the procedures described in 4.3.2.2.3 Error Handling may be applied to either of the responses (as an IIF implementation option).
Note that successful supplementary service erasure cases in ANSI136 41 foreign mode may result in the subscriber's GSM HLR sending out a GSM MAP Insert Subscriber Data message to the serving system. For these cases, the IIF would need to map the message to an ANSI-41
QUALDIR message. The mapping of GSM MAP Insert Subscriber Data message to an ANSI-
41 QUALDIR message is covered in the Subscriber Data Management.
33
34
35
36
37
4.3.2.2.2 Mapping of Messages, Parameters & Parameter Values
4.3.2.2.2 presents the mapping of messages, parameters and parameter values that the IIF shall perform.
38
39
40
4.3.2.2.2.1 Mapping of Messages
84

11
12
13
N.S0028
1
2
3
Table 69 shows the mapping of messages for Supplementary Service Erasure.
Table 69: Supplementary Service Erasure Message Mapping
GSM MAP Message
ERASE SS REQUEST
ANSI-41 MAP Message
FEATREQ
ERASE SS REQUEST RESPONSE featreq
4
5
6
7
8
9
10
4.3.2.2.2.2 Mapping of parameters
The following tables show the mapping between the parameters in GSM MAP messages and parameters in the corresponding ANSI-41 messages. The relationships between the parameters shown in the tables are meant to be bi-directional.
Table 70: Erase SS Request ↔ FEATREQ parameter mapping
Erase SS Request Status FEATREQ Status
Basic services
-
C -
MSID (Either MIN or IMSI) M
85

1
N.S0028
Table 71: Erase SS Response ↔ Feature Request Return Result parameter mapping
Erase SS Response
Forwarding information
Status
C
Feature Request Return Result
-
Status
User Error
Provider Error
-
C
O
Announcement List
-
Access Denied Reason
O
O
2
3
4
5
6
Note 1: The FeatureResult parameter shall be mapped to an error value if a User Error is received in the ERASE SS RESPONSE
86

N.S0028
3
4
5
6
1
2 Table 72: Erase SS Response ↔ Return Error parameter mapping
Erase SS Response
Call forwarding information
User Error
Provider Error
C
C
O
Status Return Error
-
Error Code
Status
O
87

N.S0028
9
10
11
12
13
14
1
2
3
4
5
6
7
4.3.2.2.2.2.1 Mapping of parameter values in GSM Foreign Mode
Erase SS Request to Feature Request Invoke mapping
Table 73 represents how the IIF shall map the value of the parameter it has received to populate the fields of the message it shall transmit.
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.
Note that no parameter in the FeatureRequest INVOKE message currently supports the mapping from the GSM MAP parameter "Basic service". The "GSM Foreign Mode" part of
4.3.2 SS Registration and Erasure contains procedures pertaining to the handling of the "Basic service" parameter, when included in the received GSM MAP message.
88

N.S0028
1
2
3
4
5
6
7
Default parameter values
Table 74 presents how the IIF shall populate the parameters of the Feature Request Invoke message to be sent to the ANSI-41 VLR. These fields cannot be mapped from the received
Erase SS request message.
Table 74: Feature Request Invoke default parameter
8
9
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.
BillingID (Originating) O Not required to be included in message.
CallingPartyNumberString1 O
CallingPartyNumberString2 O
CallingPartySubaddress O
ConferenceCallingIndicator O
Not required to be included in message.
Not required to be included in message.
Not required to be included in message.
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
OneTimeFeatureIndicator O
PC_SSN O
SenderIdentificationNumber O
May be included from IIF data.
Not required to be included in message.
May be included from IIF data.
May be included from IIF data.
TransactionCapability O If included, it shall be populated based on
IIF’s MAP interworking capabilities.
89

N.S0028
6
7
8
9
10
11
12
4
5
13
14
15
16
1
2
3
17
18
19
Feature Request Return Result to Erase SS Response mapping
Mapping of parameter values
For the successful case (in which a FeatureRequest Return Result is received with the
FeatureResult parameter set to “successful”) there are no meaningful parameter mappings to support. For those successful cases, the “Default parameter values” describes how the corresponding GSM Erase SS Response message shall be populated. For the unsuccessful cases, refer to 4.3.2.2.3 Error Handling
Default parameter values
Table 75 describes the population of the parameters in the Erase SS Response message for successful erasure cases (i.e. when the received Feature Request Return Result contains a
FeatureResult parameter set to “successful”).
Table 75: Erase SS Response default parameter values
Erase SS Response Status Default Value
Call forwarding information
C The suggested values for the fields in this parameter 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.
90

N.S0028
1
9
10
11
12
13
14
15
16
17
18
2
3
4
5
6
7
4.3.2.2.2.2.2 Mapping of parameter values in ANSI-
Feature Request Invoke to Erase SS Request mapping
136 41 Foreign Mode
Table 76 represents how the IIF shall map the value of the parameter it has received to populate the fields of the message it shall transmit.
8 Table 76: FEATREQ to Erase SS Request parameter mapping
FEATREQ
Digits (Dialed)
Status
M
Erase SS Request
SS-Code
The IIF shall support a table mapping ANSI-41 feature codes to GSM supplementary service operations (e.g. CFB erasure)
Default parameter values
Status
M
This table presents how the IIF shall populate the parameters of the Erase SS Request message to be sent to the GSM HLR. These fields do not have an equivalent in the received
Feature Request Invoke message.
Parameter Name
Basic services
Table 77: Erase SS Request default parameter
Status Value
C Not required to be included. (Registration operation shall apply to all service groups when absent.)
91

N.S0028
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
GSM Erase SS Response to ANSI-41 Feature Request Return Result mapping
Mapping of parameter values
For the successful case (in which there is no User error or Provider Error present in the received GSM Erase SS Response message), there are no meaningful parameter mappings to support. For those successful cases, the “Default parameter values” describes how the corresponding ANSI-41 FeatureRequest Return Result shall be populated. For the unsuccessful cases, refer to 4.3.2.2.3 Error Handling.
Default parameter values
This table presents how the IIF shall populate the parameters of the Feature Request Return
Result message to be sent to the ANSI-41 HLR for successful erasure cases. Note that the population of the message may differ for non-erasure cases.
Table 78: FeatureRequest Return Result default parameter
Parameter Name
FeatureResult
AccessDeniedReason
ActionCode
AnnouncementList
CallingPartyNumberString1
CallingPartyNumberString2
CallingPartySubaddress
CarrierDigits
ConferenceCallingIndicator
Digits (Dialed)
DMH_AccountCodeDigits
DMH_AlternateBillingDigits
DMH_BillingDigits
DMH_RedirectionIndicator
GroupInformation
MobileDirectoryNumber
NoAnswerTime
Status
O
O
O
O
O
O
O
O
O
O
O
M
O
O
O
O
O
Default Value
Set to “successful”
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
92

N.S0028
15
16
17
3
4
5
9
10
11
6
7
8
12
13
14
1
2 Table 78: FeatureRequest Return Result default parameter (concluded)
Parameter Name
OneTimeFeatureIndicator
PACAIndicator
PilotNumber
RedirectingNumberDigits
RedirectingNumberString
RedirectingSubaddress
RoutingDigits
TerminationList
TerminationTriggers
O
O
O
O
O
O
O
Status
O
O
Default Value
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
Not required to be included.
The error handling procedures specified for supplementary service activation apply also for the supplementary service erasure case, with the following modification: the User Error values "SS subscription violation", "SS incompatibility", "Negative PW Check", and "Number of PW
Attempts Violation", although valid for the activation case, are not valid for the erasure case. If any of those values are received in the User Error parameter of a Register SS Response, they may be mapped to "System Failure". Also, the IIF may not include any of those User Error values in the Erase SS Response messages it sends.
Table 79: FeatureRequest Return Result to Register SS Response User Error
FeatureRequest Return Result
FeatureResult ="unsuccessful"
AnnouncementList="UnauthorizedFeature
Code"
FeatureResult ="unsuccessful"
AnnouncementList not present
User Error in the Erase SS Response
User Error = "SS subscription violation"
User Error="System Failure"
93

N.S0028
1
2
3
38
39
40
41
34
35
36
37
27
28
29
30
31
32
33
22
23
24
25
26
4
5
9
10
11
12
13
14
15
16
17
18
19
6
7
8
20
21
4.3.3.1 Detailed Procedures
The following procedures are applicable at the IIF for retrieval of forwarded-to-number, in GSM foreign mode. These procedures are applicable for Call Forwarding Busy (CFB) and Call
Forwarding No Answer (CFNA), which will be referred to as Conditional Call Forwarding.
In GSM, the HLR provides the forwarded-to-number(s) to the serving MSC/VLR as part of the profile update procedure, in the MAP_Insert_Subscriber_Data message (or, as part of the response to a MAP_Interrogate_SS request). The ANSI-41 HLR, however, only provides this information when the Call Forwarding feature is actually invoked. Therefore, in GSM foreign mode, in order to the able to include the forwarded-to-number(s) in the
MAP_Insert_Subscriber_Data message to the serving system during profile updates, the IIF has to, beforehand, explicitly request the ANSI-41 HLR for the forwarded-to-number(s). The IIF makes this request to the ANSI-41 HLR via the TransferToNumberRequest Invoke message.
(Note that two separate TRANUMREQ messages may be needed: one for CFB and another for
CFNA. The two requests may be sent in parallel by the IIF). The IIF shall then store the received forwarded-to numbers for subsequent use.
Specifically, before a MAP_Insert_Subscriber_Data message is sent by the IIF, the IIF shall determine if it needs to query the ANSI-41 HLR for the CFB or CFNA forwarded-to number(s).
In general, the IIF needs to query the ANSI-41 HLR at least for the case in which the
CFB/CFNA feature is authorized and active for the subscriber, and the profile update procedure is being performed immediately after an initial successful location update of the subscriber in
GSM foreign mode
1
. Other cases for initiating the query may be supported by the IIF as follows: a) After a recent successful forwarded-to number registration pertaining to either the CFB or
CFNA feature.
(Note, however, that a query after a forwarded-to number registration may not be necessary if the IIF saves the forwarded-to number while processing the registration messages.)
After a successful location update when either the CFB or CFNA feature is authorized, but not necessarily active.
(This case differs from the mandatory case in that the CFB/CFNA feature need not be active in order to initiate the query. Supporting this case would make it unnecessary for the query to be performed after an activation of the CFB/CFNA feature) b) After a recent successful activation of either the CFB or CFNA feature.
(Note that this case would only be needed if the IIF had not queried the ANSI-41 HLR previously. In particular if the IIF, during the initial location update, does not perform the query because the CFB/CFNA feature is not active.) 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
16
17
18
19
20
21
22
11
12
13
14
15
6
7
8
9
10
1
2
3
4
5
(Supporting this case would be useful for accounting for the possibility of a network administrator-initiated change of the forwarded-to DN(s)).
The IIF shall populate the TransferToNumberRequest Invoke message in a manner compliant with ANSI-41 [6]. The IIF shall then send the TransferToNumberRequest Invoke message to the ANSI-41 HLR, start the Transfer-To-Number Request Timer, and wait for a response.
If the response indicates that the retrieval of forwarded-to-number procedure has been successful, the IIF shall map the forwarded-to-number information (along with any other subscriber profile information received in either the QualificationDirective Invoke or
RegistrationNotification RETURN RESULT) into a MAP_Insert_Subscriber_Data Request message. As shown in Table 81 and Table 82, the Forwarded-to-Number field of the
TransferToNumberRequest RETURN RESULT shall be mapped from the Digits (Destination) field in the MAP_Insert_Subscriber_Data message. In addition, if the registration deals with Call
Forwarding No Answer, the No Reply Condition Time parameter in the
MAP_Insert_Subscriber_Data message should be populated with the content of the
NoAnswerTime field in the TransferToNumberRequest RETURN RESULT message.
In case of a failure, the IIF may receive either a TransferToNumberRequest RETURN RESULT with the field AccessDeniedReason present, or a Return Error or Reject message with an Error
Code value. For those cases in which a failure occurs, the IIF shall continue to use a previously obtained forwarded-to number, if available. If no previously obtained forwarded-to number is available at the IIF, the IIF shall not populate the corresponding information (i.e., the
Forwarded-to-Number field within the Forwarding Information List parameter) in the
MAP_Insert_Subscriber_Data Request message.
23
24
25
26
27
28
29
4.3.3.2 Mapping of Messages, Parameters & Parameter Values
Note: the mapping of the QualificationDirective Invoke message to the
MAP_Insert_Subscriber_Data Request message is described in details in 4.4 O&M
Procedures. Therefore, 4.3.3.2 focuses on the mapping of TransferToNumberRequest return result to the relevant MAP_Insert_Subscriber_Data field. Not all Insert Subscriber Data fields are shown in the following tables.
30
31
32
33
4.3.3.2.1 Mapping of Messages
The following table shows the mapping of messages for Retrieval of Forward-to-Number in
GSM Foreign Mode.
34
35
36
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
95

N.S0028
1
8
9
10
11
12
13
2
3
4
5
4.3.3.2.2 Mapping of parameters
The following tables are only for GSM Foreign Mode.
6
7
Table 81: TransferToNumberRequest Return Result to Insert Subscriber Data parameter
mapping
Status Insert Subscriber Data Status TransferToNumberRequest
Return Result
Digits (Destination) or TerminationList (see Note 1)
M
O
Forwarded-to-Number (within
Forwarding Information List)
C
Digits (Carrier)
DMH_RedirectionIndicator (Set to CFB or CFNA)
O -
DMH_AlternateBillingDigits O -
O -
C
Forwarding Information List)
CDMAServiceOption (Note 2) O -GSM BearerServiceCode or GSM
TeleService
O
Note 1: When TerminationList parameter is present, the Digits (Destination) parameter is ignored.
-Note 2: Optional, if the network settings support data, a mapping may be performed as described in Table 92
96

N.S0028
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
1
2
3
4
5
6
7
8
9
TransferToNumberRequest Return Result to Insert Subscriber Data Request
Mapping of parameters value
Table 82 represents how the IIF shall map the value of the parameter it has received to populate the fields of the message it shall transmit.
Table 82: TransferToNumberRequest Return Result to Insert Subscriber Data Request value mapping
Status Insert Subscriber Data Request Status TransferToNumberRequest Return
Result
Digits (Destination) or
DestinationDigits parameter within
TerminationList (See Note 1)
This is the forwarded-to-number.
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
M
O
Forwarding Information List
Forwarded-to-Number
(See Note 2)
E.164 format
C
C
CDMAServiceOption (Note 3) O
Forwarding Information List
No Reply Condition time
-GSM BearerServiceCode or GSM
TeleService
O
Note 1: When TerminationList parameter is present, the Digits (Destination) parameter of the
TransferToNumberRequest RETURN RESULT is ignored.
Note 2: There may be up to three forwarded-to number parameters with the Insert Subscriber
Data Request message mapped from TransferToNumberRequest information: one for Call
Forwarding Busy, one for Call Forwarding No Reply (mapped from CFNA results), and another for Call Forwarding Not Reachable (also mapped from CFNA results).
Note 3: Optional, if the network settings support data, a mapping may be performed as described in Table 92.
Default parameter value
The other parameters in the TransferToNumberRequest Return Result message are not mapped to any of the Insert Subscriber Data Request parameters.
97

N.S0028
1
2
3
4
5
6
7
4.3.3.3 Error Handling
No mapping between ANSI-41 and GSM MAP messages is required for cases in which the forwarded-to number retrieval operation fails. Refer to 4.3.3.1 Detailed Procedures for a description of the IIF procedures when the forwarded-to number retrieval operation fails.
8
9
10
11
12
The calling number/line identification Presentation/Restriction procedure is used to determine whether the calling party number should be presented to the called party.
13
14
4.3.4.1 Handling of calling number/ line identification presentation
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
4.3.4.1.2
If CNIP / CLIP service is authorized and active, the calling party number is available and presentation is allowed, the called party’s serving network shall provide the calling party number to the called party during call alerting.
If the IIF receives a GSM MAP _PROVIDE_ROAMING_Request with the Calling Party Number in the Additional Signal Info field correctly populated, the IIF shall send an
ANSI_MAP_ROUTEREQ to the serving MSC/VLR with the Calling Party Number field correctly mapped.
If the IIF receives an ANSI_MAP_ROUTREQ with the Calling Party Number field in the
Additional Signal Info field correctlty populated, the IIF shall send a GSM MAP
_PROVIDE_ROAMING_NUMBER_Request to the serving MSC/VLR with the Calling Party
Number field correctly mapped.
Mapping of Messages, Parameters & Parameter Values
31
32
33
34
35
4.3.4.1.2.1 Mapping of Messages
The mapping of messages is in accordance with 4.2.1, with the exception that GSM 09.02 [3] is supported.
98

N.S0028
1
2
3
4
5
6
7
8
9
10
11
12
4.3.4.1.2.2 Mapping of Parameters
The following tables show the mapping of parameters specific to handling calling number/line presentation/restrcition, which the IIF shall perform regardless of the mode of operation (GSM
Foreign Mode or ANSI136 41 Foreign Mode). The mapping of other parameters not specific to handling calling number/line presentation/restriction can be found in 4.2.1, with the exception that GSM 09.02 [3] is supported.
Note: The tables are constructed in such a way that the parameter names appear first and any information contained within those parameters are shown as indented text.
13
14
15
16
Table 83: Routing Request ↔ Provide Roaming Number Request (Network Provided number) Parmater Mapping
Routing Request
CallingPartyNumberString1
(Network Provided No):-
Type Of Digits:- Calling Party
Number
Nature of Number:- National,
Presentation Allowed, Network
Provided
Numbering Plan:- Telephony
Numbering
Encoding:- IA5
Characters:- Digits
Status Provide Roaming Number
O AdditionalSignalInfo:-
CallingPartyNumber:-
-
Screening Indicator: Network
Provided
Presentation Indicator:
Presentation Allowed
-
-
Line Identity: E164 address of
Calling Party
C
Status
99

N.S0028
1
2
3
4
5
6
Table 84: Routing Request ↔ Provide Roaming Number Request (User Provided number) Parameter Mapping
Route Request
CallingPartyNumberString2
(User Provided No):-
Type Of Digits:- Calling Party
Number
Nature of Number:-
National,Presentation Allowed,
User Provided, not screened
Numbering Plan:- Telephony
Numbering
Encoding:- IA5
Characters:- Digits
Status Provide Roaming Number
O AddititonalSignalInfo:-
CallingPartyNumber:-
-
-
Screening Indicator: User
Provided, not screened
Presentation Indicator:
Presentation Allowed
-
Line Identity: E164 address of
Calling Party
Status
C
100

N.S0028
1
2
3
Table 85: Routing Request ↔ Provide Roaming Number Request (Two calling party numbers) Parameter Mapping
Route Request
CallingPartyNumberString1
(Network Provided No):-
Type Of Digits:- Calling Party
Number
Nature of Number:- National,
Presentation Allowed,
Network Provided
Numbering Plan:- Telephony
Numbering
Encoding:-IA5
Characters:- Digits
CallingPartyNumberString2
(User Provided No):-
Type Of Digits:- Calling Party
Number
Nature of Number:- National,
Presentation Allowed
User Provided
Numbering Plan:- Telephony
Numbering
Encoding:- IA5
Characters:- Digits
O
Status Provide Roaming Number
O AdditionalSignalInfo:-
CallingPartyNumber:-
-
Screening Indicator: Network
Provided
-
Presentation Indicator:
Presentation Allowed
-
Line Identity: E164 address of
Calling Party
-
Generic Number:-
-
Screening Indicator: User
Provided, not screened
-
Line Identity: E164 address of
Calling Party
Status
C
101

N.S0028
1
2
4.3.4.2 Handling of calling number/ line identification restriction
3
4
9
10
11
12
5
6
7
8
13
4.3.4.2.1 Detailed Procedures
If the calling subscriber has calling number/line identification restriction authorized and active and it is impossible to indicate to the terminating network (due to interworking) that the number shall not be presented to the terminating party, the calling number/line identity shall not be delivered to the terminating network.
If CNIR / CLIR service is authorized and active, the calling party number is available and presentation is restricted, the called party’s serving network shall not present the calling party number to the called party during call alerting. An indication that the calling party number is restricted shall be delivered to the called party.
14
15
4.3.4.2.2 Mapping of Messages, Parameters and Parameter Values
16
17
18
19
4.3.4.2.2.1 Mapping of Messages
Messages for Calling number/line identification restriction is the same as 4.3.4.1.
20
21
22
23
24
25
4.3.4.2.2.2 Mapping of Parameters
The following table shows the mapping of parameters for calling name/line restriction, which the
IIF shall perform regardless of the mode of operation (ANSI-41 Foreign Mode or GSM Foreign mode).
102

N.S0028
4
5
1
2
3
Table 86: Routing Request ↔ Provide Roaming Number Request(Caller Id Restricted)
Parameter Mapping
Routing Request Status Provide Roaming Number Status
CallingPartyNumberString1
(Network Provided No):-
Type Of Digits:- Calling Party
Number
Nature of Number:- National,
Presentation Restricted,
Network Provided
Numbering Plan:- Telephony
Numbering
Encoding:- IA5
Characters:-Digits
O AdditionallSignalInfo:-
CallingPartyNumber:-
-
Screening Indicator: Network
Provided,
Presentation Indicator:
Presentation Restrcited
-
-
Line Identity: E164 address of
Calling Party
C
103

N.S0028
1
14
15
16
17
18
2
3
4
5
6
7
8
9
10
11
12
13
4.3.4.3 Error Handling
For the cases of failure at the IIF on reception of an ANSI_ MAP_RoutingRequest return Result, the procedures described in ANSI-41 [6] for automatic call delivery is applicable to the IIF.
For the cases of failure at the IIF on resception of a GSM MAP
_PROVIDE_ROAMING_NUMBER_Response, the procedures described in GSM 09.02 [3] are applicable to the IIF.
If the IIF receives a GSM MAP _PROVIDE_ROAMING_NUMBER_Request indicating an error code, the IIF shall map that error code it receives to a suitable error in the ANSI_MAP_routereq as described in 4.2.1
If the IIF receives an ANSI_MAP_routreq indicating an error code, the IIF shall map that error code it receives to a suitable error in the GSM MAP
_PROVIDE_ROAMING_NUMBER_Response as described in 4.2.1.
104

N.S0028
1
2
3
4
5
6
7
Existing operation and maintenance procedures described in either GSM 09.02 [3] or ANSI-41
[6] are also directly applicable to the IIF when it is emulating a GSM or ANSI-41 functional network element. Enhancements/modifications to ANSI-41 [7], 0 are also applicable.
13
14
15
16
17
18
19
8
9
10
11
12
Subscriber data management procedures are used to either delete or modify, subscriber data held in the network. These procedures are initiated by the OMC.
Subscriber data management procedures also cover ANSI-41 specific procedures, describing the retrieval of subscriber data from network elements.
The IIF contains both permanent subscriber data (can only be changed by administration means) and temporary subscriber data (may be changed as a result of normal operation of the system) relating to the roaming subscriber.
20
21
22
23
24
25
26
4.4.1.1 Subscriber Deletion Procedure
If the IIF receives a GSM MAP _CANCEL_LOCATION_REQUEST, it shall follow the location cancellation procedures outlined in this document for Location Registration (see 4.1.1).
If the IIF receives an ANSI_MAP_REGCANC, it shall follow the location cancellation procedures outlined in this document for Location Registration (see 4.1.1).
27
28
29
30
31
32
33
34
35
36
4.4.1.2 Subscriber Data Modification Procedure (ANSI136 41 Foreign Mode)
If the IIF receives either a GSM MAP _INSERT_SUBSCRIBER_DATA_REQUEST, or a GSM
MAP _DELETE_SUBSCRIBER_DATA_REQUEST, it shall follow the VLR procedures described in GSM 09.02 [3].
As part of the subscriber data modification procedure, the IIF may send an
ANSI_MAP_QUALDIR to the serving ANSI-41 VLR and await a response.
If the response indicates success, the IIF shall modify the corresponding subscriber data and send a GSM MAP _INSERT_SUBSCRIBER_DATA_RESPONSE to the GSM HLR.
105

N.S0028
1
2
3
4
If the response indicates failure, the received subscriber data is stored by IIF even if there is a failure reported from the visited (foreign mode) system and the IIF shall send the reason for failure in a GSM MAP _INSERT_SUBSCRIBER_DATA_RESPONSE to the GSM HLR.
5
6
7
8
9
10
11
12
13
14
15
16
4.4.1.3 Subscriber Data Modification Procedure (GSM Foreign Mode)
If the IIF receives an ANSI_MAP_QUALDIR, it shall follow the VLR procedures described in
ANSI-41 [6].
As part of the subscriber data modification procedure, the IIF may send either a GSM MAP
_INSERT_SUBSCRIBER_DATA_REQUEST or a GSM MAP
_DELETE_SUBSCRIBER_DATA_REQUEST to the serving GSM VLR and await a response.
If the response indicates success, the IIF shall modify the corresponding subscriber data and send an ANSI_MAP_qualdir to the ANSI-41 HLR.
If the response indicates failure, the received subscriber data is stored by IIF even if there is a failure reported from the visited (foreign mode) system and the IIF shall send the reason for failure in the ANSI_MAP_qualdir to the ANSI-41 HLR.
17
18
19
20
21
22
4.4.1.4 Subscriber Data Retrieval
If the IIF receives an ANSI_MAP_QUALREQ, it shall follow the ANSI-41 HLR procedures described in ANSI-41 [6]. The IIF is not required to retrieve subscriber data from the GSM
HLR.
23
24
25
26
27
The IIF shall perform the translation of messages, parameters and parameter values related to subscriber data management in accordance with the tables presented.
28
29
30
31
32
33
4.4.2.1 Mapping of Messages
Table 87 shows the mapping between GSM MAP messages and ANSI-41 MAP messages related to Subscriber Deletion. Table 88 and Table 89, show the mapping between GSM MAP messages and ANSI-41 MAP messages related to Subscriber Data Modification.
106

N.S0028
12
13
14
15
16
17
18
19
20
1
10
11
2 Table 87: Cancel_Location_Request ↔ REGCAN (Subscriber Deletion) Mapping
GSM MAP Messages ANSI MAP Messages
CANCEL_LOCATION_REQUEST REGCANC
CANCEL_LOCATION_RESPONSE (Note 1) regcanc return result
CANCEL_LOCATION_RESPONSE (Note 2) regcanc Return Error
6
7
8
9
3
4
5
Note 1: In the successful case, the CANCEL_LOCATION_RESPONSE is an empty result i.e. contains no parameters other than the invoke Id.
Note 2: This message can also contain error values if the subscriber deletion procedure is unsuccessful. If the subscriber deletion procedure fails, the mapping is as shown. See 4.4.3
Error Handling for more information.
Table 88: Mapping of GSM MAP Messages ↔ ANSI MAP Messages (Subscriber Data
Modification)
GSM MAP Messages ANSI MAP Messages
INSERT_SUBSCRIBER_DATA_REQUEST QUALDIR
(Note 2)
INSERT_SUBSCRIBER_DATA_RESPONSE
(Note 1) qualdir Return Error
Table 89: Delete_Subscriber_Data ↔ Qualdir Mapping (Subscriber Data Modification)
GSM MAP Messages ANSI MAP Messages
DELETE_SUBSCRIBER_DATA_REQUEST QUALDIR
DELETE_SUBSCRIBER_DATA_RESPONSE qualdir Return Result (Note 2)
DELETE_SUBSCRIBER_DATA_RESPONSE
(Note 1) qualdir Return Error
Note 1: These messages can also contain error values if the subscriber data modification procedure is unsuccessful. If the subscriber data modification procedure fails, the mapping is as shown. See 4.4.3 Error Hanlding for more information.
Note 2: The qualdir Return Result is an empty response i.e. contains no parameters other than the Invoke Id.
107

N.S0028
1
2
3
4
5
6
4.4.2.2 Mapping of Parameters
The following tables show the mapping of parameters, which the IIF shall perform regardless of the mode of operation (GSM Foreign Mode or ANSI-41 Foreign Mode).
Table 90: CANCEL_LOCATION_REQUEST ↔ REGCANC Parameter Mapping
CANCEL_LOCATION_REQUEST Status REGCANC Status
LMSI C
Cancellation Type C Cancellation Type O
7
8
9
10
Note 1: Cancellation Type is only used between the HLR and the SGSN for GPRS procedures.
Cancellation Type is not applicable between HLR and VLR.
Table 91: INSERT_SUBSCRIBER_DATA_REQUEST ↔ QUALDIR Parameter Mapping
INSERT_SUBSCRIBER_DATA_
REQUEST
Status QUALDIR Status
MSID M
SystemMyTypeCode (HLR or
VLR)
M
11
12
13
14
15
16
1
O
1
This parameter is itself a macro containing a number of other parameters. As far as mapping of parameters is concerned, the IIF shall map the contents of the ‘Profile’ macro in the ANSI-41-
D ‘QUALDIR Invoke’ to the contents of the GSM MAP
_INSERT_SUBSCRIBER_DATA_REQUEST as shown in Table 92.
108

N.S0028
1
2 Table 92: INSERT_SUBSCRIBER_DATA_REQUEST ↔ profile ‘macro’ Mapping
INSERT_SUBSCRIBER_DATA_
REQUEST
Status
- O
Subscriber Status
Bearer service List
Teleservice List
Forwarding information List
C
C
C
C
-
-
CallingFeaturesIndicator
1
O
Regional Subscription Data C -
3
4
Call barring information List
3
C OriginationIndicator
2
O
VLR CAMEL Subscription Info
4
C OriginationTriggers
4
O
CUG information List
SS-Data List
EMLPP Subscription Data
Operator Determined Barring
General data
Operator Determined Barring
HPLMN data
5
Operator Determined Barring
HPLMN data
5
Roaming Restriction Due To
Unsupported Feature
C -
C
6
CallingFeaturesIndicator
1
O
C -
C OriginationIndicator
2
O
C OriginationIndicator
2
O
C RestrictionDigits
C -
O
Call barring information List
3
C SMS_OriginationRestrictions
7
O
Call barring information List
3
C SMS_TerminationRestrictions
8
O
109

N.S0028
1
2
3
Table 92: INSERT_SUBSCRIBER_DATA_REQUEST ↔ profile ‘macro’ Mapping
(concluded)
INSERT_SUBSCRIBER_DATA_
REQUEST
Status
Call barring information List
3
C TerminationRestrictionCode O
VLR CAMEL Subscription Info C TerminationTriggers
4
O
Voice Broadcast Data
Voice Group Call Data
C
C -
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
4
10
11
12
5
6
7
8
9
13
14
15
SS-Data List
6
SS-Data List
6
SMS_OriginationRestrictions
7
SMS_TerminationRestrictions
O
8
O
-GSM BearerServiceCode or GSM
TeleService
O CDMAServiceOptionList
9
O
1
The CallingFeaturesIndicator parameter provides a status of several ANSI supplementary services. This information may map into one or more GSM MAP parameters as shown in Table
92.
2
The OriginationIndicator parameter defines the type of calls that a MS is allowed to make.
This information may map into one or more GSM MAP parameters as shown in Table 92.
3
The Call barring information List is a list of the call barring supplementary services that are either active, quiescent or not active for individual or all teleservices. This information may map into one or more ANSI MAP parameters as shown in Table 92.
4
If this information is received by the IIF it does have to be mapped.
5
Operator Determined Barring HPLMN data may map into one or more ANSI MAP parameters as shown in Table 92.
6
The SS-Data List may map into one or more ANSI MAP parameters as shown in Table 92.
7
The SMS_OriginationRestrictions may map into one or more GSM MAP parameters as shown in Table 92.
8
The SMS_TerminationRestrictions may map into one or more ANSI MAP parameters as shown in Table 92.
9
The CDMAServiceOptionList may map into one or more GSM MAP parameters (e.g.:
ADS (9.6kbps) to “CDA-9600 bps” BearerServiceCode;
G3FAX to “FacsimileGroup3” GSMTeleService;
Packet Data Service (PDS) to “dataPDS” BearerServiceCode).
Parameter Value Mapping
Table 93 through Table 104 shows the mapping of parameter values (more commonly referred to as ASN.1 data types in GSM09.02 [3] which the IIF shall perform based on the parameter mapping shown in Table 92. If there is no direct mapping for parameter values, a ‘-‘ has been entered in the corresponding table. The implication therefore, is that those services/features
110

N.S0028
1
2
3
4
5 and/or subscription options may not be available when roaming in either a GSM or ANSI-41
PLMN.
The ASN.1 data type encoding is specified in GSM09.02 [3].
111

N.S0028
2
3
1 Table 93: Forwarding Information List to Calling Features Indicator Parameter Mapping
GSM_Forwarding Information List
SSCode
AllForwardingSS
CFU
AllConditionalForwardingSS
CFB
CFNRy
CFNRc
CD
BasicService
2
Refer to GSM 09.02[1] for Basic Service
Codes
SSStatus
Q P R A
3
0 0 0 0
0 0 0 1
4
0 0 1 0
4
0 0 1 1
4
0 1 0 0
0 1 0 1
4
0 1 1 0
0 1 1 1
1 0 0 0
4
1 0 0 1
4
1 0 1 0
4
1 0 1 1
4
ANSI-41_Calling Features Indicator
FeatureActivityStatus
CFU + CFNA +CFB
CFU
-
CFNA +CFB
CFB
CFNA
1
CFNA
1
-
FeatureActivityStatus
-
-
Not authorized
-
Authorized but de-activated
-
Authorized but de-activated
Authorized and activated
-
-
-
-
112

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

N.S0028
1
2
7
8
3
4
5
6
Table 94: Regional Subscription Data to Geographic Authorization Parameter Mapping
GSM_Regional Subscription Data
ZoneCode
See GSM 09.02 [1] for definition of zone code
1
ANSI-41_Geographic Authorization
GeographicAuthorization
Authorized for all MarketIDs served by the
VLR
Authorized for this MarketID only
Authorized for this MarketID and SwitchNo only
Authorized for this locationAreaID within a
MarketID only
1
Based on the zone code, which identifies those regions or zones where a roaming is allowed, these values may map to one or more values in the Geographic Authorization.
Table 95: Call Barring Information List to Origination Indicator Parameter Mapping
GSM_Call Barring Information List
SSCode
See Note (a)
AllBarringSS
1
BarringOfOutgoingCalls
1
BAOC
1
BOIC
2
BOIC-exHC
2
BAOC
BAOC, BOIC, BOIC-exHC
ANSI-41_Origination Indicator
Allowed Call Types
Prior Agreement
Orignation denied
Origination denied
Origination denied
3
National long distance
4
National long distance
Local calls only
5
Selected leading digits of directory
114

N.S0028
1
2
3
4
5
6
7
8
9
Table 95: Call Barring Information List to Origination Indicator Parameter Mapping
(concluded)
GSM_Call Barring Information List
-
BAOC,BOIC, BOIC-exHC
-
BarringOfIncomingCalls
BAIC
BIC-Roam
BAOC
BasicService
See GSM 09.02[1] for Basic Service codes
SSStatus
Q P R A
See GSM 09.02[1] for SSStatus values
-
-
ANSI-41_Origination Indicator or of international E.164 number
6
Selected leading digits of directory number or of international E.164 number and local calls
6
International calls
-
-
-
-
Single Directory number or international
E.164 number
Note (a): If the origination indicator value received indicates ‘prior agreement’ this may map into one or more GSM SS Codes depending on the agreement between roaming partners.
12
If the IIF receives any of these GSM SSCodes, they shall map to the same ANSI-41 allowed call type as shown in Table 95.
115

5
6
7
8
9
1
2
3
4
N.S0028
3
If the IIF receives the ANSI-41 allowed call type set to ‘origination denied’, this shall be mapped as shown in Table 95.
4
If the IIF receives the ANSI-41 allowed call type set to ‘national long distance’, this shall be mapped as shown in Table 95.
5
If the IIF receives the ANSI-41 allowed call type set to ‘local calls only’ this shall be mapped as shown in Table 95.
6
If the IIF receives the ANSI-41 allowed call type as shown, this may be mapped to one or more
GSM SSCode values as shown in Table 95.
116

1
3
4
2 Table 96: SSData List to Calling Features Indicator Parameter Mapping
COLP
COLR
CNAP
ECT
CCBS-A
CCBS-B
AoCI
AoCC
-
CLIP
CLIP
MPTY
Note (a)
CLIR
GSM_SSData List
SSCode
-
-
-
CW + CH
-
-
-
-
-
-
-
-
ANSI-41_Calling Features Indicator
FeatureActivityStatus
CW
CT
VP
CD
3WC
CNIROver
CNIR
CNIP2
CNIP1
PCW
117
N.S0028

N.S0028
1
2
3
Table 96: SSData List to Calling Features Indicator Parameter Mapping (concluded)
GSM_SSData List
UUS
PLMNSpecific
BasicService
1
See GSM 09.02[1] for Basic Service codes
SSStatus(need to map to SMSMo & MT
Restriction in ANSI)
Q P R A
0 0 0 0
0 0 0 1
2
0 0 1 0
2
0 0 1 1
2
0 1 0 0
0 1 0 1
0 1 1 0
2
0 1 1 1
1 0 0 0
2
1 0 0 1
2
1 0 1 0
2
1 0 1 1
2
1 1 0 0
2
1 1 0 1
2
1 1 1 0
2
1 1 1 1
2
CLIRestrictionOption
3
Permanent
TemporaryDefaultRestricted
TemporaryDefaultAllowed
OverrideCategory
4
OverrideEnabled
OverrideDisabled
ANSI-41_Calling Features Indicator
-
-
-
FeatureActivityStatus
-
-
Not authorized
-
Authorized but de-activated
Authorized and activated
-
-
-
-
-
-
-
-
-
Authorized and activated
Feature Activity Status
-
Authorized and activated
Authorized and deactivated
Feature Activity Status
Authorized and activated
Authorized and deactivated
118

N.S0028
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
Note (a): There is no equivalent GSM SSCode value for CNIROver. The override restriction capability in GSM is a subscription option whose value is reflected by the OverrideCategory
1
GSM allows supplementary services to be operated on a per basic service group basis. ANSI-
41 on the other hand has no concept of basic service groups. Therefore, one or more GSM basic services or basic service groups shall map to all basic services in ANSI-41.
2
These combinations are not applicable to the GSM supplementary services defined by their
SSCode in Table 96
3
The CLIRestriction option is equivalent to the ANSI-41 Feature Activity Status, CNIR. If the
CLIRestriction is temporary default restricted, this equates to the value ‘Authorized and activated’ in the CNIR feature activity status. If the CLIRestriction is temporary default allowed, this equates to the value ‘Authorized but deactivated’ in the CNIR feature activity status. There is no equivalent in ANSI-41 to permanently restricted.
4
The GSM override category is equivalent to the ANSI-41 Feature Activity Status, CNIROver.
If the Override Category is enabled, this equates to the value ‘Authorized and activated’ in the
CNIROver feature activity status. If the Override Category is disabled, this equates to the value
‘Authorized but deactivated’ in the CNIROver feature activity status.
Table 97: Operator Determined Barring general data to Origination Indicator
Parameter Mapping
GSM_Operator determined barring (general) ANSI-41_Origination Indicator
ODB-General data
AllOG-callsBarred
InternationalOGCalls Barred
1
InternationalOGCallsNotToHPLMN-
CountryBarred
1
InterzonalOGCallsBarred
1
InterzonalOGCallsNotToHPLMN-
CountryBarred
1
Allowed Call Types
Origination denied
National long distance
2
National long distance
Selected leading digits of directory number or of international E.164 number and local calls
Selected leading digits of directory number or of international E.164 number and local calls
119

N.S0028
8
9
10
11
4
5
6
7
1
2
3
Table 97: Operator Determined Barring general data to Origination Indicator
Parameter Mapping (concluded)
GSM_Operator determined barring (general) ANSI-41_Origination Indicator
InterzonalandInternationalOGCallsNotToHPL
MN-CountryBarred
1
PremiumRateInformationOGCallsBarred
1
PremiumRateEntertainmentOGCallsBarred
1
SSAccessBarred
AllECTBarred
ChargeableECTBarred
InternationalECTBarred
InterzonalECTBarred
DoublyChargedECTBarred
MultipleECTBarred
-
-
-
-
Selected leading digits of directory number or of international E.164 number and local calls
Selected leading digits of directory number or of international E.164 number and local calls
Selected leading digits of directory number or of international E.164 number and local calls
-
-
Note: The mapping shown in Table 97 applies in one direction only i.e. from GSM to ANSI-41.
The corresponding ANSI-41 values received by the IIF in “profile” macro parameter, it shall be mapped according to Table 95.
1
If the IIF receives any of these GSM ODB general data, they shall map to the same ANSI-41 allowed call type as shown in Table 97.
120

N.S0028
7
8
1
2
3
4
5
6
Table 98: Operator Determined Barring HPLMN data to Origination Indicator Parameter
Mapping
ANSI-41_Origination Indicator GSM_Operator determined barring
(HPLMN)
ODB-HPLMN data
PLMN-SpecificBarringType1
Allowed Call Types
-
Table 99: Operator Determined Barring HPLMN data to Restriction digits Parameter
Mapping
ANSI-41_Restriction Digits GSM_Operator determined barring
(HPLMN)
ODB-HPLMN data
PLMN-SpecificBarringType1
Type of Number
-
121

N.S0028
1
2
3
4
Table 100: Call Barring Information List to SMS Origination Restrictions Parameter
Mapping
GSM_Call Barring Information List
-
-
-
-
-
BAIC
BIC-Roam
SSCode
AllBarringSS
BarringOfOutgoingCalls
BAOC
-
-
BOIC
BOIC-exHC
BAOC
BarringOfIncomingCalls
ANSI-41_SMS Origination Restrictions
Default
-
-
Block All
-
-
-
-
Allow Specific
Allow All
-
-
Direct
Block Direct
Allow Direct
ForceMessageCenter
Force Indirect
122

N.S0028
7
8
1
2
3
4
5
6
Table 100: Call Barring Information List to SMS Origination Restrictions Parameter
Mapping (concluded)
GSM_Call Barring Information List
BasicService
See GSM 09.02[1] for Basic Service codes
SSStatus
Q P R A
See GSM 09.02[1] for SSStatus values
-
ANSI-41_SMS Origination Restrictions
-
Table 101: Call Barring Information List to SMS Termination Restrictions Parameter
Mapping
GSM_Call Barring Information List
SSCode
AllBarringSS
BarringOfOutgoingCalls
BAOC
-
-
BOIC
BOIC-exHC
BAOC
BarringOfIncomingCalls
BAIC
BIC-Roam
-
-
-
BasicService
See GSM 09.02[1] for Basic Service codes
SSStatus
Q P R A
See GSM 09.02[1] for SSStatus values
ANSI-41_SMS Termination Restrictions
-
-
Default
-
-
Block All
Allow Specific
-
-
-
Allow All
-
-
-
Reserve Charges
Block Direct
Allow Direct
123

N.S0028
1
2
3
4
Table 102: Call Barring Information List to Termination Restriction Code Parameter
Mapping
GSM_Call Barring Information List
SSCode
AllBarringSS
BarringOfOutgoingCalls
BAOC
BOIC
BOIC-exHC
BAOC
BarringOfIncomingCalls
BAIC
BIC-Roam
-
BasicService
See GSM 09.02[1] for Basic Service codes
SSStatus
Q P R A
See GSM 09.02[1] for SSStatus values
-
-
ANSI-41_Termination Restriction Code
-
-
-
-
-
Termination RC
-
-
Termination denied
-
Unrestricted
124

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

N.S0028
1
9
10
11
12
6
7
8
2
3
4
5
13
14
15
16
17
18
19
20
21
22
23
24
Error handling defined in GSM 09.02 [3] and ANSI-41 [6] is directly applicable to the IIF, when the IIF is emulating a GSM or ANSI-41 network functional element.
Subscriber Deletion
If the Subscriber Deletion procedure fails at an ANSI-41 VLR, the VLR shall respond by either sending:
An ANSI_MAP_regcanc in a TCAP RETURN RESULT indicating cancellation denied
(CANDEN) to the IIF, with one of the following reasons as defined in ANSI-41 [6]
Appropriate CANDEN Values in ANSI_MAP_regcanc RETURN RESULT
CANDEN Value
Multiple access
Busy
The ANSI_MAP regcanc may optionally indicate:
•
CallHistoryCount
•
ControlChannelData
•
ReceivedSignalQuality
•
SMS_MessageWaitingIndicator
•
SystemAccessData as defined in ANSI-41 [6]
Or, an ANSI_MAP regcanc in a TCAP RETURN ERROR one of the following error codes as defined in ANSI-41 [6]:
Appropriate Error Codes in ANSI_MAP_regcanc RETURN ERROR
Error Codes
UnrecognizedESN
OperationSequenceProblem
ResourceShortage
OperationNotSupported
ParameterError
SystemFailure
126

N.S0028
8
9
10
1
2
3
4
5
6
7
11
12
13
14
15
16
17
18
19
20
21
The IIF is therefore responsible for mapping any errors it receives from the ANSI-41 VLR in the
ANSI_MAP regcanc to an equivalent error in the GSM MAP
_CANCEL_LOCATION_RESPONSE towards the GSM HLR.
The GSM MAP _CANCEL_LOCATION_RESPONSE may include one the following ‘user’ errors as defined in GSM 09.02 [3]:
Appropriate User Errors
User Errors unexpected data value; data missing;
The following ‘provider errors’ (protocol related errors) are also defined in GSM 09.02 [3]:
Appropriate Provider Errors
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.
If the Subscriber Deletion procedure fails at a GSM VLR, it returns a GSM MAP
_CANCEL_LOCATION_RESPONSE to the IIF, indicating an ‘user error’ as indicated above. The
IIF is therefore responsible for mapping any errors it receives into a corresponding error in the
ANSI_MAP regcanc towards the ANSI-41 HLR. For further description of these errors and when they are used, refer to either GSM 09.02 [3] or ANSI-41 [6].
The « Location Registration » provides the mapping of both user errors and provider errors in the GSM MAP _CANCEL_LOCATION_RESPONSE to the equivalent value in either the
CANDEN parameter in the ANSI_MAP regcanc RETURN RESULT or the RETURN ERROR.
127

N.S0028
9
10
11
12
13
14
15
16
17
18
1
5
6
7
8
2
3
4
19
Subscriber Data Modification
If the Subscriber Data Modification procedure fails at an ANSI-41 VLR, the VLR shall respond by sending:-
An ANSI_MAP qualdir in a TCAP RETURN ERROR with one of the following reasons as defined in ANSI-41 [6]:
Appropriate Provider Errors
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.
The IIF is therefore responsible for mapping any errors it receives from the ANSI-41 VLR in the
ANSI_MAP qualdir to an equivalent error in the GSM MAP
_INSERT_SUBSCRIBER_DATA_RESPONSE or the GSM MAP
_DELETE_SUSBCRIBER_DATA_RESPONSE towards the GSM HLR.
The GSM MAP _INSERT_SUBSCRIBER_DATA_RESPONSE and the GSM
MAP_DELETE_SUBSCRIBER_DATA RESPONSE may include one the following ‘user’ errors as defined in GSM 09.02 [3]:
Appropriate User Errors
User Errors unidentified subscriber; data missing; unexpected data value.
128

N.S0028
1
2
3
4
8
9
10
5
6
7
11
12
13
14
15
16
The following ‘provider errors’ are also defined in GSM 09.02 [3]:
Appropriate Provider Errors
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.
If the Subscriber Data Modification procedure fails at a GSM VLR, it returns either a GSM MAP
_INSERT_SUBSCRIBER_DATA_RESPONSE or a GSM MAP
_DELETE_SUBSCRIBER_DATA_RESPONSE to the IIF, indicating a ‘user error’ as indicated above. The IIF is therefore responsible for mapping any errors it receives into a corresponding error in the ANSI_MAP qualdir towards the ANSI-41 HLR. For further description of these errors and when they are used, refer to either GSM 09.02 [3] or ANSI-41 [6].
Table 105 below provides the mapping of both user errors and provider errors in the GSM MAP
_INSERT_SUBSCRIBER_DATA_RESPONSE and GSM MAP
_DELETE_SUBSCRIBER_DATA_RESPONSE to the equivalent value in the ANSI_MAP qualdir RETURN ERROR for ANSI-41 Foreign mode. Table 106 provides the mapping for GSM
Foreign mode.
129

N.S0028
6
7
8
1
2
3
4
5
Table 105: ISD_RESPONSE and DSD_RESPONSE to Qualdir Return Error Mapping
INSERT/DELETE_SUBSCRIBER_DATA_
RESPONSE (Errors)
Unidentified subscriber
Data missing
Unexpected data value
Duplicated Invoke Id
Not supported service
Mistyped parameter
Resource limitation
Initiating release
Unexpected response from the peer
Service completion failure
No response from the peer
Invalid response received
Qualdir Return Error
Unrecognized MSID
SystemFailure
SystemFailure
SystemFailure
SystemFailure
SystemFailure
SystemFailure
SystemFailure
SystemFailure
SystemFailure
SystemFailure
SystemFailure
Table 106: Qualdir Return Error to INSERT_SUBSCRIBER_DATA_RESPONSE and
DELETE_SUSBCRIBER_DATA_RESPONSE Error Mapping
Qualdir Return Error
Unrecognized MSID
Unrecognized ESN
ResourceShortage
OperationNotSupported
ParameterError
SystemFailure
UnrecognizedParameterValue
Missing Parameter
INSERT/DELETE_SUBSCRIBER_DATA_
RESPONSE (Errors)
Unidentified subscriber
Unexpected data value
Unexpected data value
Unexpected data value
Unexpected data value
Unexpected data value
Unexpected data value
Data Missing
130

N.S0028
1
2
3
4
5
6
136 41
Existing mobility procedures described in either GSM 09.02 [3] or ANSI-41 [6] are also directly applicable to the IIF when it is emulating a GSM or ANSI-41 functional network element.
7
8
9
10
11
The Short Message Service procedure is used to deliver short text messages to and from mobile subscribers.
12
13
14
15
16
17
4.5.1.1 Detailed Procedures
The following procedures are applicable at the IIF for Short Message Service. Mobile
Terminating SMS and Mobile Originated SMS using the CMT teleservice ID are described in
4.5.1.1.
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
4.5.1.1.1 Mobile Terminating SMS in GSM foreign mode
If the IIF receives an ANSI-41 Short Message Delivery Point to Point message from the home
Message Center, it shall check if the subscriber location is known and if the subscriber is active.
If both conditions are true, the IIF shall format and send a GSM_
MAP_FORWARD_SHORT_MESSAGE to the GSM MSC/VLR serving the mobile. Refer to
Table 109 for the mapping of parameters from ANSI_SMDPP to GSM MAP
_FORWARD_SHORT_MESSAGE.
If a successful response is received for the FSM, the IIF shall send a SMDPP Return Result message to the home Message Center
If the subscriber’s location is not known, or if the subscriber is inactive or if the response to the
FSM indicates the short message was not delivered to the mobile, the IIF shall set the SMS
Delivery Pending flag for the subscriber. The IIF shall then send an SMDPP Return Result message with an appropriate SMS_CauseCode value to the home MC. Refer to 4.5.1.3 Error
Handling for the values of SMS_CauseCode returned.
If errors are detected when the SMDPP is received, the message may be rejected if it cannot be processed or if mandatory parameters are missing. Otherwise, the IIF shall send an SMDPP
Return Result message with the appropriate SMS_CauseCode value. Refer to 4.5.1.3 Error
Handling for the description of error conditions and corresponding SMS_CauseCode values.
131

N.S0028
8
9
10
11
12
6
7
4
5
1
2
3
If the response to FSM indicates a failure in the delivery of the short message, the IIF shall map the cause value received to a corresponding SMS_CauseCode value in the
SMDPP Return Result, as described in
Table 116.
If the response to FSM indicates that the receiving entity does not support MAP V2, the GSM
MAP_FORWARD_SHORT_MESSAGE is formatted in MAP V1 and sent again to the serving
MSC/VLR.
13
14
15
16
17
18
19
20
21
4.5.1.1.2 Alerting in GSM Foreign Mode
If the IIF receives a GSM MAP _READY_FOR-SHORT_MESSAGE (MAP V2) or a
GSM_UPDATE_LOCATION message, or a GSM MAP _NOTE_MS_PRESENT message (MAP
V1) and the Delivery pending flag is set for the subscriber, the IIF shall send an
ANSI_MAP_SMS_NOTIFICATION message to the home Message Center. The flag shall then be cleared. The home MC shall re-send message SMDPP to deliver the short message to the subscriber as described previously.
33
34
35
36
37
38
39
28
29
30
31
32
22
23
24
25
26
27
4.5.1.1.3 Mobile Terminating SMS in ANSI136 41 Foreign Mode
If the IIF receives a GSM_FORWARD_SHORT_MESSAGE, it shall format and send an
ANSI_MAP Short Message Delivery Point to Point message to the serving TDMA ANSI-41
MSC/VLR. Refer to Table 110, Table 111 and Table 112 for the mapping of parameters from
GSM MAP _FORWARD_SHORT_MESSAGE to ANSI_SMDPP.
If the IIF receives a positive acknowledgment to the SMDPP message, it shall send a positive acknowledgment to the Forward Short Message.
If the IIF receives a negative acknowledgment to the SMDPP message, it shall set the Mobile
Not Reachable flag for the subscriber and shall map the received SMS_CauseCode value into a corresponding error code in the FSM Response message as described in Table 117.
If the IIF detects errors in the FORWARD_SHORT_MESSAGE, an error indication is sent in the response message. This shall cause the GSM MSC/VLR to send an error indication to the GSM
HLR. Refer to 4.5.1.3 Error Handling for error detection on reception of FSM.
If a Return Error or Reject is received in response to the ANSI_MAP_SMSDPP INVOKE, the error code is mapped into the corresponding Forward Short Message error code as described in Table 117.
132

N.S0028
1
2
3
4
5
6
7
8
4.5.1.1.4 Alerting in ANSI136 41 Foreign Mode
If the IIF receives an ANSI_MAP Registration Notification message or an ANSI_MAP SMS
Notification message, and the SMS Delivery Pending flag is set for a mobile subscriber, it shall send a GSM MAP _READY_FOR-SHORT_MESSAGE (MAP V2) or a GSM MAP
_NOTE_MS_PRESENT message (MAP V1) to the GSM HLR. This shall cause the HLR to send an indication to the GSM SMSC that shall trigger the re-sending of the Short message.
9
10
11
12
13
14
15
16
17
18
19
20
21
22
4.5.1.1.5 Mobile Originating SMS in GSM Foreign Mode
If the IIF receives a GSM_FORWARD_SHORT_MESSAGE for a mobile originated short message, it shall format and send an ANSI_MAP_SMDPP message to the serving TDMA
ANSI-41 Message Center. Refer to Table 114 for the mapping of parameters from GSM MAP
_FORWARD_SHORT_MESSAGE to ANSI_SMDPP.
If the IIF receives a positive acknowledgment to the SMDPP message, it shall send a positive acknowledgment to the Forward Short Message.
If the IIF receives a negative acknowledgment to the SMDPP message, it shall map the received SMS_CauseCode value into a corresponding error code in the FSM Response message as described in Table 117
If the IIF detects errors in the FORWARD_SHORT_MESSAGE, an error indication is sent in the response message. Refer to 4.5.1.3 for the handling of errors at the reception of FSM.
31
32
33
34
35
36
37
38
23
24
25
26
27
28
29
30
4.5.1.1.6 Mobile Originating SMS in ANSI136 41 Foreign Mode
If the IIF receives an ANSI-SMDPP message from the Serving MSC, it shall format and send a
GSM MAP_FORWARD_SHORT_MESSAGE to the GSM Message Center of the subscriber.
Refer to Table 115 for the mapping of parameters from ANSI_SMDPP to GSM MAP
_FORWARD_SHORT_MESSAGE.
If a successful response is received for the FSM, the IIF shall send a SMDPP Return Result message to the MSC/VLR.
If errors are detected when the SMDPP is received, the message may be rejected if it cannot be processed or if mandatory parameters are missing. Otherwise, the IIF shall send an SMDPP
Return Result message with the appropriate SMS_CauseCode value. Refer to 4.5.1.3 Error
Handling for the description of error conditions and corresponding SMS_CauseCode values.
If the response to FSM indicates that the receiving entity does not support MAP V2, the GSM
MAP_FORWARD_SHORT_MESSAGE is formatted in MAP V1 and sent again to the serving
MSC/VLR.
133

N.S0028
13
14
15
1
2
3
4.5.1.2 Mapping of Messages, Parameters & Parameter Values
4
5
6
7
8
9
10
11
4.5.1.2.1 Mapping of Messages
The IIF shall perform the mapping of messages, parameters and parameter values related to
Short Message Service in accordance with the tables presented.
Table 107 shows the mapping between ANSI MAP messages and GSM MAP messages related to Short Message Service in GSM Foreign Mode. Table 108 shows the mapping between GSM MAP messages and ANSI MAP messages related to Short Message Service in
ANSI136 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
Table 108: Short Message Service in ANSI136 41 Foreign Mode (for CMT) Message
Mapping
GSM MAP Messages
FORWARD_SHORT_MESSAGE
ANSI MAP Messages
SMDPP
16
17
134

N.S0028
9
10
7
8
1
2
3
4
4.5.1.2.2 Mapping of Parameters
Table 109 through Table 115 show the mapping of parameters, which the IIF shall perform.
5
6
Table 109: SMDPP to MT_Forward Short Message Parameter Mapping for GSM Foreign
Mode
ANSI SMDPP
SMS_OriginalDestinationAddres s (= MSID)
SMS-Originating-Address (= MC
Address)
User Data Unit (in
SMS_Bearer_Data)
-
Status GSM MT FSM
Note 1
O
Note 1
O SM-RP-OA = IIF address in international format. See 4.5.2.4
M SM-RP-UI
See Table 111 and Table 112 for details of encoding of this parameter.
M
M
Status
M
More Messages to Send = no M
Note 2
Note 1: MSID and SMS_Original_Destination_Address should be the same.
Note 2: This parameter is only valid for MAP V2.
135

N.S0028
4
5
6
7
8
9
10
11
12
1
2
3
Table 110: MT_Forward Short Message to SMDPP Parameter Mapping for ANSI-41
Foreign Mode
GSM MT FSM
SM-RP-DA= IMSI
SM-RP-UI
-
SM-RP-OA (=SMS-SC Address) M
Status ANSI SMDPP
M
M
Status
MSID R
ESN O
SMS Bearer Data
See Table 113 for encoding of this parameter.
SMS Teleservice Identifier set to value (= CMT)
M
M
SMSOriginating Address (= IIF
Address) See 4.5.2.4
R
The IIF shall support the mapping of parameters in Forward Short Message in both MAP V1 and MAP V2. Encoding of parameter SM-RP-UI is different depending on the MAP version being encoded in the message. The two following tables describe the coding for each version of MAP.
Table 111describes the setting of field values for parameter SM-RP-UI for MAP V2.
Table 111: SM-RP-UI in MT_FORWARD_SHORT_MESSAGE for MAP V2 Parameter Values 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”
Set to value “A status report is not requested” Status Report Indication
Protocol Identifier Set to value “0”
Service Center Time Stamp Created by the IIF
User Data Length
User Data
Number of characters
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

1
2
Originating Address
N.S0028
octets (152 characters) for MAP V2 (160 characters for
MAP V1).
The address of the original SME. Use the value received in parameter SMS Original Originating Address in
SMDPP.
137

N.S0028
8
9
1
2
3
4
5
6
7
Table 111: SM-RP-UI in MT_FORWARD_SHORT_MESSAGE for MAP V2 Parameter Values 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”.
The following table describes the setting of field values for parameter SM-RP-UI for MAP V1.
Table 112: SM-RP-UI in MT_FORWARD_SHORT_MESSAGE for MAP V1 Parameter
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
User Data
Originating Address
Data Coding Scheme
Number of characters
The address of the original SME. Use the value received in parameter SMS Original Originating Address in
SMDPP.
Use the coding value “default alphabet”
138

N.S0028
4
5
1
2
3
Table 113: SMS_Bearer Data in Mobile Terminating SMDPP Parameter Encoding for
ANSI-41 Foreign Mode
FIELD VALUE
Message type indicator (M) 000 “SMS Deliver”
Message Reference (M)
Privacy Indicator (M)
Urgency Indicator (M) created by IIF
000 “Not restricted”
11 “Very urgent” if class 0 coded in the TP-DCS received,
01 “Normal” otherwise.
Set to value “Delivery acknowledge prohibited” Delivery ack request (M)
Manual ack request (M)
Message Updating (M)
Validity (M)
Display time (M)
User Data Unit (M)
Set to value “Manual acknowledge prohibited”
1 “new”
000 “indefinite”
01 “Default”
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.
139

N.S0028
1
2
3
Table 114: Forward_Short_Message to ANSI-41_SMDPP Parameter Mapping for MO SMS in GSM Foreign Mode
GSM Forward Short Message Status ANSI SMDPP Status
4
5
SM-RP-OA (A-MSISDN)
SM-RP-UI: TP-Destination address (B-MSISDN)
SM-RP-DA (IIF Address)
SM-RP-UI
TP-Message-Type-Indicator
TP-Reject-Duplicates (ignored)
TP-Validity-Period
TP-Validity-Period-Format
TP-Reply-Path (ignored)
TP-User-Data-Header-Indicator
(ignored)
TP-Status-Report-Request
(ignored)
TP-Message-Reference
TP-Protocol-Identifier (ignored)
TP-Data-Coding-Scheme
TP-User-Data-Length
M
Note 1
M
M
M
SMS Teleservice ID = CMT
SMS_Originating Address (=IIF
Address)
SMS_Original Originating
Address (= A-MSID)
M
O
SMS_Original
DestinationOriginating Address
Sub Address (not sent)
SMS_Original Destination
Address
O
R
SMS_Original Originating
Address Sub Address (not sent)
O
SMS_Charge Indicator (not sent) O
SMS_Message Count (not sent) O
SMS_Notification Indicator (not sent)
SMS_Destination Address (= MC address retrieved from mapping in database) See 4.5.2.4
SMS Bearer Data
TP-Message-Type-Indicator
TP-Validity-Period
TP-Delivery-Ack-Request
(=prohibit)
TP-Message-Reference
TP-Urgent-Indicator
TP-User-Data-Unit
R
O
R
M
140

N.S0028
9
10
4
5
6
1
2
3
Table 114: Forward_Short_Message to ANSI-41_SMDPP Parameter Mapping for MO SMS in GSM Foreign Mode (concluded)
GSM Forward Short Message Status ANSI SMDPP
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)
Status
Note 1: MSID and ESN are supplied based on MSISDN received in SM-RP-OA
7
8
Table 115: ANSI-41 SMDPP to GSM Forward_Short_Message Parameter Mapping for MO
SMS in ANSI-41 Foreign Mode
ANSI SMDPP
SMS Teleservice ID
Status
M
GSM Forward Short Message
-
Status
ESN O
SMS_Charge Indicator O -
SMS_Message Count
SMS_Notification Indicator
O
O
-
-
141

N.S0028
4
5
1
2
3
Table 115: ANSI-41 SMDPP to GSM Forward_Short_Message Parameter Mapping for MO
SMS in ANSI-41 Foreign Mode (continued)
ANSI SMDPP
SMS_Destination Address (IIF
Address)
Status GSM Forward Short Message
(retrieved from mapping in IIF database) see 4.5.2.4
SMS_Original Destination
Address (B-MSISDN)
SMS_Original Destination Sub
Address
SMS_Originating Address
SMS_Original Originating
Address (A-MSID)
SMS_Original Originating Sub
Address
SMS Bearer Data
- TP-Message-Type-
Indicator
-
-
- TP-Validity-Period
-
-
-
-
- TP-Message-Reference
- TP-User-Data-Unit
TP-Urgent-Indicator
- TP-Delivery-Ack-Request
(ignored)
SM-RP-UI
O -
O -
O -
M SM-RP-UI
- TP-Message-Type-
Indicator
- TP-Reject-Duplicates
=TRUE
- 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-Protocol-Identifier = 0
- TP-Data-Coding-Scheme
TP-User-Data-Length
TP-User-Data
Status
O SM-RP-OA: M
M
M
142

N.S0028
1
2
3
Table 115: ANSI-41 SMDPP to GSM Forward_Short_Message Parameter Mapping for MO
SMS in ANSI-41 Foreign Mode (concluded)
ANSI SMDPP
- TP-Privacy_Indicator
-
-
-
-
-
-
(ignored)
TP-Manual-Ack-Request
(ignored)
TP-Message-Updating
(ignored)
TP-Deferred-Delivery-
Time (ignored)
TP-Call-Back-Number
(ignored)
TP-Call-Back-Number-
Presentation-Indicator
(ignored)
TP-Call-Back-Number-
Alpha-Tag (ignored)
- TP-Multilingual-Call-
Back-Number (ignored)
- TP-Multilingual-Call-
Back-Number-Alpha
(ignored)
TP-Multilingual-Destination-
Address (ignored)
- User Data
MSG_ENCODING: For
CDMA, possible values are unspecified, IS-91 EPM, 7-bit
ASCII, and IA5.
MST:Message type IS-95 or IS-136 is used
NUM_FIELDS: Number of characters. Messages above GSM limit will be truncated.
CHARi: IS-95 or IS-136
SMS message itself
Status GSM Forward Short Message
TP-Destin a tion-Address =
SMS-Original-Destination
Address.
Status
143

1
N.S0028
144

N.S0028
1
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
6
7
8
9
10
11
12
2
3
4
5
4.5.1.3 Error Handling
Error handling at the reception of a Forward Short Message in the IIF
1. If a mandatory parameter is missing (MAP V2), a Forward Short Message Response with the indication “Data Missing” is sent back to the SMS-GMSC.
2. If a mandatory parameter is missing (MAP V1), a Forward Short Message Response with the indication “Mistyped Parameter” is sent back to the SMS-GMSC. sent in the following cases:
•
A parameter tag is not one of those associated with the operation.
•
The received value is not a value of the type associated with the operation.
•
Erroneous tag and length information.
•
Exceeding of the defined size of an ASN.1 module.
Response with the indication “Unexpected Data Value” is sent back to the SMS-GMSC. with the indication “Unexpected Data Value” is sent back to the SMS-GMSC.
6. If the subscriber is not connected in the IIF or if the profile is not available, Forward
Short Message Response with the indication “Unidentified Subscriber” is sent back to the SMS-GMSC.
7. If location is unknown or inactive, send back to the SMS-GMSC a Forward Short
Message Response message with the indication “Absent Subscriber”.
8. If the subscriber has an ANSI SMS termination restriction, a Forward Short Message
Response message with indication “Facility Not Supported” is sent back to the SMS-
GMSC.
9. If the short message contents could not be extracted from the SM-RP-UI parameter, send back to the SMS-GMSC a Forward Short Message Response message with the indication “System Failure”.
145

N.S0028
13
14
15
16
17
18
19
20
21
22
23
24
30
31
32
33
34
25
26
27
28
29
4
5
6
7
8
9
10
11
12
1
2
3
Error Handling at the Reception of ANSI-41 SMDPP
1. If the subscriber is not connected in the IIF then a SMDPP RR with cause code “SMS
Termination Denied” is returned.
If the ESN received does not match stored ESN then a SMDPP RR with cause code
“SMS Termination Denied” or “Address Translation Failure” is returned.
When the SMSNotification Indicator: “Notify when available” is not set, and the MS is inactive or the subscriber’s location is unknown, a SMDPP RR with one of the following cause codes is returned:
•
“SMS Termination Denied”
•
“Destination Out of Service”
•
“No page response”
•
“Destination no longer at this address”
When the SMSNotification Indicator: “Notify when available” is set, and the MS is inactive or the subscribers location is unknown then a SMDPP RR with cause code
“SMS Delivery Postponed” is returned.
If the subscriber does not have SMS service then a SMDPP RR with cause code “SMS
Termination Denied” is returned.
2. If a SMDPP Invoke arrives at the IIF WITH A Teleservice ID that is not supported by the
IIF, then it shall return a SMDPP RR with cause code “Invalid Teleservice ID”.
3. If a mandatory parameter is missing or if the MSID parameter is missing, a SMDPP RR with cause code “Missing mandatory parameter” is returned.
4. If the subscriber’s profile is not available, a SMDPP RR with cause code “Destination No
Longer at this Address” is returned.
5. If the GSM MSC/VLR is on a Barring List, a SMDPP RR with cause code “SMS Delivery
Postponed” “SMS Termination Denied” is returned.
6. If any other error is detected, a SMDPP RR with cause code “Network Failure” is returned.
Note: The IIF should not use “SMS Delivery Postponed” if the ANSI-41 MC indicates that it doesn’t require notification, or the IIF doesn’t set the delivery pending flag.
Error Mapping from GSM FSM to ANSI SMDPP to support Mobile Terminating SMS in
GSM Foreign and Mobile Originating SMS in ANSI-41 Foreign Mode
146

N.S0028
3
4
1
2
5
6
7
8
Table 116: Forward_Short_Message to SMS_CauseCode Values in SMDPP Return Result
Error Mapping
GSM FORWARD_SHORT_MESSAGE
RESPONSE
Absent Subscriber
Subscriber Busy for MT SMS
Memory Capacity exceeded
System Failure
DataMissing
UnexpectedDataValue
ANSI SMDPP Return Result SMS-
CauseCode Value
SMS Delivery Postponed OR No Page
Response
SMS Delivery Postponed OR Destination
Busy
Destination resource shortage
Other network problem OR Network failure
Other general problem OR Missing
Mandatory Parameter
Encoding problem OR Unexpected
Parameter value
147

N.S0028
1
2
3
4
5
6
7
Table 116: Forward_Short_Message to SMS_CauseCode Values in SMDPP Return Result
Error Mapping (concluded)
GSM FORWARD_SHORT_MESSAGE
RESPONSE
FacilityNotSupported
ANSI SMDPP Return Result SMS-
CauseCode Value
SMS not supported
Unknown Subscriber
Illegal Subscriber
SM-DeliveryFailure cause: Equipment Protocol Error
SM-DeliveryFailure cause: Equipment Not SM-Equipped
SM-DeliveryFailure cause: unknownSC
Address translation failure
Address translation failure OR SMS termination denied
Other radio interface problem OR No
Acknowledgement
Other terminal problem OR No
Acknowledgement
Address translation failure
SM-DeliveryFailure cause: SC-Congestion Network resource shortage OR No
Acknowledgement
SM-DeliveryFailure cause: invalid SME-
Addr
SM-DeliveryFailure cause: subscriberNotSC-Subscriber
Absent Subscriber SM
Address translation failure OR No
Acknowledgement
SMS origination denied OR No
Acknowledgement
Encoding Error
No acknowledgment OR No page response
Network Failure
Unidentified Subscriber Address Vacant
Illegal Equipment
Any other error
Other General Problems
Network Failure
Note: Unidentified Subscriber and Illegal Equipment may be treated as Any Other Error and may be mapped to Network failure.
148

N.S0028
1
2
3
4
Error Mapping from ANSI SMSDPP to GSM FSM to support Mobile Terminating SMS in
ANSI-41 Foreign Mode and Mobile Originated SMS in GSM Foreign Mode
Table 117: SMDPP to Forward_Short_Message Error Mapping
SMSDPP (Cause Code)
Destination Busy
Address Vacant
No Page Response
No Acknowledgement
Destination Out of Service
Destination No Longer at this Address
SMS not supported
FORWARD_SHORT_MESSAGE
Response
Subscriber Busy for MT-SMS
Absent Subscriber
Absent Subscriber
Absent Subscriber
Absent Subscriber
Absent Subscriber
FacilityNotSupported
Destination resource shortage
Other radio interface problem
Unrecognized parameter value or
Encoding problem
Radio interface incompatibility or Other terminal problems
SMS Delivery Postponed
Any other value
SM-DeliveryFailure with cause
“MemoryCapacityExceeded”
SM-DeliveryFailure with cause
“equipmentProtocolError”
SM-DeliveryFailure with cause
“equipmentProtocolError”
SM-DeliveryFailure with cause
“equipmentProtocolError”
Absent Subscriber OR System Failure
System Failure
5
149

1
N.S0028
2
3
7
8
9
10
11
4
5
6
4.5.2.1 Detailed Procedures
SMS Alert Procedure
The SMS Alert procedure is used for alerting the SMSC when the mobile subscriber is active and available for short messaging after a short message transfer has failed because the mobile subscriber is not reachable or when the Mobile Station (MS) has indicated that it has no memory capacity to accept a short message.
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
4.5.2.1.1 Alerting for an ANSI-
IIF Receiving a READY_FOR_SM
136 41 Subscriber in GSM Foreign Mode
Upon receipt of a READY_FOR_SM message, the IIF shall store the originating Visited MSC
(VMSC) address in the subscriber’s profile and Invoke ID. It shall map the
GSM_READY_FOR_SM message to the ANSI_SMSNOT INVOKE message as described in
Table 119.
It shall populate the SMS_Address parameter with the IIF address. All other parameters are ignored.
The ANSI_SMSNOT INVOKE is then transmitted to the subscriber’s SMSC with local
Transaction ID. Finally, the IIF shall return a READY_FOR_SM_ACK message with no arguments to the originating VMSC.
IIF Receiving a SMSNOT RETURN RESULT
Upon receipt of a SMSNOT RR message, the IIF shall associate the SMSNOT Transaction ID with the Invoke ID.
29
30
31
32
33
34
35
36
37
4.5.2.1.2 Alerting for a GSM Subscriber in ANSI-
IIF Receiving a SMSNOT INVOKE
136 41 Foreign Mode
Upon receipt of a SMSNOT message, the IIF shall store the originating VMSC address and
Transaction ID. The IIF shall map the ANSI_SMSNOT message to the
GSM_READY_FOR_SM. The parameters shall be mapped as described in Table 120.
The GSM_READY_FOR_SM is transmitted to the subscriber’s HLR with local Invoke ID.
Finally, the IIF shall return a SMSNOT RR to the originating VMSC.
150

N.S0028
1
7
8
9
10
11
12
13
2
3
4
5
6
14
15
16
17
IIF Receiving a REGNOT INVOKE
Alternatively, the IIF may receive a REGNOT message indicating an update in location of the
MS. Upon receipt of the REGNOT message, the IIF shall determine if the SMS Delivery
Pending Flag is set. If the DPF is not set, the IIF follow normal procedures according to 4.1.1
Location Registration. If the DPF is set, the IIF shall store the originating VMSC address and Transaction ID. The IIF shall create a GSM_READY_FOR_SM.
The content of the MSID is mapped to the equivalent IMSI and place in the IMSI parameter.
The Alert Reason parameter is populated with the value - MS Present. All other parameters are ignored.
The GSM_READY_FOR_SM is transmitted to the subscriber’s HLR with local Invoke ID. .
Finally, the IIF shall return a REGNOT RR to the originating VMSC.
IIF Receiving a GSM_READY_FOR_SM_ACK
Upon receipt of a GSM_READY_FOR_SM_ACK message, the IIF shall associate the
GSM_READY_FOR_SM_ACK Invoke ID with Transaction ID.
Short Message Service for GHOST
33
34
35
36
37
38
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
4.5.2.1.3 SMS Delivery for an ANSI136 41
IIF Receiving SMSDeliveryPointToPoint INVOKE
Subscriber in GSM Foreign Mode
Upon receipt of an SMSDeliveryPointToPoint INVOKE message, the IIF shall store the originating MC address and transaction ID. It shall map the ANSI_SMDPP message into a
GSM_FSM message and populate the subscriber’s known VMSC into the DPC. The mapping of parameters is described in Table 121.
The IIF transmits the GSM_FSM message with local Invoke ID.
IIF Receiving FORWARD_SHORT_MESSAGE_ACK
Upon receipt of the FORWARD_SHORT_MESSAGE_ACK message, the IIF shall associate the
Invoke ID with SMDPP transaction ID and map the GSM_FSM_ACK message into an
ANSI_SMDPP RETURN RESULT.
Next, it populates the stored originating SMSC address into the DPC and populates the transaction ID.
If the User Error parameter is populated in the GSM_FSM_ACK, then map this value into the SMS_CauseCode according to
Table 116.
151

1
2
N.S0028
Finally, the ANSI_SMDPP RR is transmitted to the originating SMSC.
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
4.5.2.1.4 SMS Delivery for a GSM Subscriber in ANSI136 41 Foreign Mode
IIF Receiving MT_FORWARD_SHORT_MESSAGE
Upon receipt of the MT_FORWARD_SHORT_MESSAGE message, the IIF shall store the originating SMSC address and Invoke ID. It shall map the GSM_FSM message into an
ANSI_SMDPP INVOKE message and populate the subscriber’s known VMSC into the DPC.
The mapping of parameters is described in Table 122.
The IIF transmits the ANSI_SMDPP INVOKE message with local transaction ID
IIF Receiving SMDPP RETURN RESULT
Upon receipt of a SMSDeliveryPointToPoint RR message, the IIF shall associate the SMDPP transaction ID with Invoke ID and map the ANSI_SMDPP RR to GSM_FSM_ACK.
Next, it populates the stored originating SMSC address and Invoke ID. If the SMS_CauseCode parameter is populated in the ANSI_SMDPP RR message, then map value into User error parameter according to Table 117.
Finally, transmit the GSM_FSM_ACK to the originating SMSC.
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
4.5.2.1.5 SMS Origination for an ANSI136 41
IIF Receiving MO_FORWARD_SHORT_MESSAGE
Subscriber in GSM Foreign Mode
Upon receipt of a MO_FORWARD_SHORT_MESSAGE, the IIF shall store the address of the originating VMSC and Invoke ID. It shall map the GSM_MO_FSM to ANSI_SMDPP INVOKE.
The address of the subscriber’s TSA (from the SM RP DA – Service Center Address) is mapped according to 4.5.2.4 into the SMS_DestinationAddress. The mapping of parameters is described in Table 123.
The IIF transmits the ANSI_SMDPP INVOKE message with local transaction ID.
IIF Receiving SMDPP RETURN RESULT
Upon receipt of a SMSDeliveryPointToPoint RR message, the IIF shall associate the SMDPP transaction ID with Invoke ID and map the ANSI_SMDPP RR to the GSM_FSM_ACK.
Next, it populates the stored originating SMSC address and Invoke ID. If SMS_CauseCode parameter is populated in the ANSI_SMDPP RR message, then map value into User error parameter according to Table 117.
Finally, transmit the GSM_FSM_ACK to the originating VMSC.
37
38
4.5.2.1.6 SMS Origination for a GSM Subscriber in ANSI136 41 Foreign Mode
152

N.S0028
11
12
13
14
15
16
17
18
19
1
8
9
10
5
6
2
3
4
7
IIF Receiving SMSDeliveryPointToPoint INVOKE
Upon receipt of an SMSDeliveryPointToPoint INVOKE message, the IIF shall store the address of the originating VMSC and Transaction ID and map the ANSI_SMDPP INVOKE to the
GSM_MO_FSM. The mapping of parameters is described in Table 124.
The IIF transmits the GSM_FSM message with local Invoke ID.
IIF Receiving FORWARD_SHORT_MESSAGE_ACK
Upon receipt of the FORWARD_SHORT_MESSAGE_ACK message, the IIF shall associate the
Invoke ID with SMDPP transaction ID. The GSM_FSM_ACK message is mapped into an
ANSI_SMDPP RETURN RESULT.
Next, it populates the stored originating SMSC address and transaction ID. If the User
Error parameter is populated in GSM_FSM_ACK, then this value is mapped into the
SMS_CauseCode according to
Table 116.
Finally, transmit the ANSI_SMDPP RR to the originating VMSC.
20
21
22
23
24
4.5.2.2 Mapping of Messages, Parameters & Parameter Values
The IIF shall perform the mapping of messages, parameters and parameter values related to
Short Message Service in accordance with the tables presented next.
25
26
4.5.2.2.1
27
Mapping of Messages
Table 118: Short Message Service (for GHOST or WEMT ) Message Mapping
ANSI MAP Messages GSM MAP Messages
SMSNOT READY_FOR_SM
28
29
30
4.5.2.2.2 Mapping of Parameters
153

5
6
1
2
3
4
N.S0028
The mapping of the GSM MAP _READY_FOR_SM message to the ANSI_SMSNOT message is per Table 119.
Table 119: Alerting for an ANSI136 41 Subscriber in GSM Foreign Mode Parameter
Mapping
GSM MAP _READY_FOR_SM Status ANSI_SMSNOT Status
Alert Reason (MS present or
Memory Available)
MSID M
M -
SMS_Address (IIF Address) R
154

N.S0028
1
2
3
4
The mapping of the ANSI_SMSNOT message to the GSM MAP _READY_FOR_SM message is per Table 120.
Table 120: Alerting for a GSM Subscriber in ANSI136 41 Foreign Mode Parameter
Mapping
ANSI_SMSNOT Status GSM MAP _READY_FOR_SM Status
5
MSID M
SMS_Address (Serving MSC) O -
Alert Reason (MS present) M
6
7
8
9
10
11
12
13
14
4.5.2.2.3 SMS Delivery for an ANSI136 41 Subscriber in GSM Foreign Mode
When the IIF receives an SMDPP Invoke from an ANSI136/ 41 SMSC for an ANSI136/ 41 MS roaming in a GSM network, it stores the Originating MC address, converts the SMDPP to a
MAP_FSM, replaces the Originating Address by the address of the IIF, and sends the message to the serving GSM MSC. Upon receipt of the MAP_FSM_ACK from the serving MSC, the IIF converts the message to an SMDPP Return Result, replaces the Originating Address with its own address and replaces the Destination Address with the previously stored address of the
ANSI136/ 41 SMSC. See Table 121.
15
16
Table 121: SMDPP to Forward Short Message for Mobile Terminated GHOST /WEMT
Teleservice Parameter Mapping in GSM Foreign Mode
SMDPP Status
SMS Bearer Data M SM-RP-UI
MSID (Note 1) O
SMS_OriginalDestinationAddres s (= MSID) (Note 1)
O
M
SMS Teleservice ID =GHOST or
WEMT
M -
ESN O
M
SMS_DestinationAddress O -
SMS_NotificationIndicator O -
SMS_OriginalDestinationSub
Address
O -
O - SMS_Original Originating
Address
SMS_Original Originating
Address Sub Address
SMS_Originating Address (= MC
Address)
O -
O SM-RP-OA (set to IIF address)
See 4.5.2.4
M
17
155

1
2
N.S0028
Note 1: MSID and SMS-Original-Destination Address should be the same
3
4
8
9
10
5
6
7
4.5.2.2.4 SMS Delivery for a GSM Subscriber in ANSI136 41 Foreign Mode
When the IIF receives a MAP_FSM destined for an MS roaming in an ANSI-136/41 network, it stores the originating Service Center address locally, and replaces the Service Center Address in the outgoing SMDPP message by E.164 address of the IIF. Upon receipt of an SMDPP
Return Result from the serving ANSI136/ 41 MSC, the IIF converts it to a MAP_FSM_ACK, and places the previously stored Originating Service Center address in the Destination Address.
See Table 122.
11
12
Table 122: Forward Short Message to SMDPP for Mobile Terminated GHOST /WEMT
Teleservice Parameter Mapping in ANSI Foreign Mode
SM-RP-DA =
IMSI
M MSID R
SMS-Original_Destination-
Address = MSID
M SMS_Originating Address = IIF
Address . See 4.5.2.4
O
O SM-RP-OA =
Service center address OA
More Messages to Send
13
14
15
16
4.5.2.2.5
C
SMS Origination for an ANSI-
GHOST or WEMT
-
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)
136 41
M
-
Subscriber in GSM Foreign Mode
156

N.S0028
1
2
3
4
5
6
7
When the IIF receives a MAP_FSM originated from a MS roaming in a GSM network, it stores the VMSC address locally and replaces the VMSC address in the outgoing SMDPP message by the E.164 address of the IIF (placed in the SCCP Calling Party Address). Upon receipt of an
SMDPP Return Result from the MC, the IIF converts it to a MAP_FSM_ACK and places the previously stored VMSC address in the SCCP Called Party Address. See Table 123.
Table 123: Forward Short Message to SMDPP for Mobile Originated GHOST /WEMT in
GSM Foreign Mode Parameter Mapping
GSM MO FSM
SM-RP-DA =
Service Center Address DA = IIF
Address
SM-RP-OA =
A-MSISDN
Status ANSI SMDPP
M SMS_DestinationAddress= MC
Address. See 4.5.2.4
M
Note 1
SMS_OriginalOriginating Address
=A-MSID
Status
R
R
GHOST or WEMT (Set by IIF)
IIF address)
M
O
8
9
10
-
-
SMS_Charge Indicator (Not used)
SMS_Message Count (Not used) used)
(Not used)
-
-
SMS_Original Destination Sub
Address (Not used)
SMS_Original Originating
Address Sub Address (Not used)
Note 1: MSID and ESN are mapped from MSISDN received in SM-RP-OA
11
12
13
14
15
16
17
18
4.5.2.2.6 SMS Origination for a GSM Subscriber in ANSI136 41 Foreign Mode
When the IIF receives a SMDPP Invoke originated from a MS roaming in an ANSI136 41 network, it stores the VMSC address locally and replaces the VMSC address in the outgoing
MT FSM message by the E.164 address of the IIF (placed in the SCCP Calling Party Address).
It also internally maps the TSA
F
from the SMS_Destination Address into the TSA
H
and places that value in the RP-Destination Address per 4.5.2.4 Identification of the IIF SS7 Address for
Mobile Originated Services. Upon receipt of a MAP_FSM_ACK from the MC, the IIF converts it
157

1
2
N.S0028
to a SMDPP Return Result and places the previously stored VMSC address in the SCCP
Called Party Address. See Table 124.
3
4
5
6
7
8
Table 124: SMDPP to Forward Short Message for Mobile Originated GHOST /WEMT
Teleservice Parameter Mapping in ANSI-41 Foreign Mode
ANSI SMDPP Status GSM MO FSM Status
SMS Bearer Data
SMS Teleservice ID =GHOST or
WEMT
M SM-RP-UI
M -
M
ESN O
SMS_Charge Indicator
SMS_Destination Address
(Note 1)
O -
O SM-RP-DA: Service Center
Address (retrieved from mapping in IIF database). See 4.5.2.4
M
SMS_Message Count
SMS_Notification Indicator
SMS_Original Destination
Address
SMS_Original Destination Sub
Address
SMS_Original Originating
Address
(A-MSID)
O
O
-
-
O -
O -
O SM-RP-OA M
SMS_Original Originating
Address Sub Address
SMS_Originating Address
O -
O -
Note 1: If MSID is received it should be the same as the SMS_OriginalOriginating Address
GHOST shall use the HLPI shown below. TSAR may or may not be applied to the GHOST teleservice.
9
HLPI Subfield
Table 125: HLPI for GHOST
Coding
Teleservice Type Indicator Subfield
Teleservice Segmentation and
Reassembly Subfield
0 - Standardized Teleservice
May or may not have TSAR sub-layer
0 - No TSAR
1 - TSAR is being used
Teleservice Protocol Identifier Subfield
000111
10
158

N.S0028
1
2
4.5.2.3 Error Handling
6
7
8
3
4
5
4.5.2.3.1 Error handling at the reception of a Forward Short Message in the IIF
Refer to 4.5.1.3 Error Handling
4.5.2.3.2 Error handling at the reception of a SMDPP message in the IIF
Refer to 4.5.1.3 Error Handling
9
10
11
12
4.5.2.3.3 Cause Code Mapping at the IIF
At the IIF, the ANSI-41 SMS_CauseCode is mapped to a return error in the GSM
MAP_FSM_ACK message according to Table 117
13
14
15
16
17
18
19
The IIF is responsible for mapping GSM MAP_FSM_ACK Return Errors to ANSI-41
SMS_CauseCodes according to
Table 116.
20
21
30
31
32
33
34
22
23
24
25
26
27
28
29
35
36
37
38
4.5.2.4 Identification of the IIF SS7 Address for Mobile Originated Services
The following SS7 address mapping scheme is defined in order to resolve the ambiguity that occurs when a roaming subscriber attempts to invoke mobile originated teleservices.
Specifically, instead of using only a single Teleservice Server Address (TSA) as the SS7 SCCP
Called Party Address, a pair of E.164 addresses are defined for each Teleservice Server
Address Center (e.g., MC or SMSC). This pair of addresses (native and foreign mode TSAs) is used to enable the routing of incoming messages to the IIF from the serving foreign network, while messages that originate in a network that uses the same technology as the home network bypass the IIF and are routed directly to the MC. The native mode address can be translated using global title translation to the actual SS7 address (DPC and SSN) of the MC while the foreign mode address is a virtual address that points (via global title translation) to the IIF.
There is a one-to-one mapping in the IIF between the home and foreign mode addresses for each MC, as shown in Table 126. Note that there is a many-to-one relationship between the virtual addresses and the actual IIF address.
While roaming in foreign mode, the mobile station uses the foreign mode address in order to ensure that messages are first routed to the IIF. The IIF performs message translation, and inserts the native mode address, i.e., an E.164 number that is translatable by the network to the actual MC destination SS7 address.
159

1
2
3
N.S0028
Table 126: Teleservice Server Address Mapping in IIF
Home Technology Address
TSA
H1
TSA
H2
TSA
H3
↔
↔
↔
Foreign Technology Address
TSA
F1
TSA
F2
TSA
F3
160

N.S0028
1
2
3
4
5
6
The Message Waiting Notification procedure is used to notify a mobile subscriber of voice mail messages added or removed in his voice mail system.
10
11
12
13
7
8
9
4.5.3.1 Detailed Procedures
The following procedures are applicable at the IIF for Message Waiting Notification.
GSM Foreign Mode
Two events can trigger the sending of updated MWN information by the IIF to the serving GSM
MSC/VLR, when an ANSI136 41 native subscriber is roaming in GSM Foreign Mode.
24
25
26
27
28
29
30
31
32
33
34
35
36
37
14
15
16
17
18
19
20
21
22
23
4.5.3.1.1 Registration Notification Return Result with MWN Information Received
When the ANSI136 41 native subscriber registers in a GSM MSC/VLR, a GSM
MAP_UPDATE_LOCATION message is received at the IIF. This shall trigger an ANSI MAP
REGISTRATION_NOTIFICATION message to be sent by the IIF to the TDMA ANSI-41 home
HLR.
If the IIF receives a Registration Notification Return Result message with MWNCOUNT and
MWNTYPE parameters set to valid values, it shall set the Message Waiting Notification flag and it shall send a GSM MAP_INSERT_SUB_DATA message(s) to the GSM MSC/VLR from which it had received a previous GSM MAP_UPDATE_LOCATION message.
The IIF shall also send an Update Location acknowledge message and send it to the GSM
MSC/VLR.
The IIF shall then format and send a GSM MAP_FORWARD_SHORT_MESSAGE. Refer to
Table 129 for the mapping of parameters from ANSI-Regnot return result to GSM MAP
_FORWARD_SHORT_MESSAGE.
If a successful response is received for the FSM, the IIF shall clear the Message Waiting
Notification flag.
If the response to FSM indicates that the receiving node does not support MAP V2, the
GSM_FSM message shall be reformatted in MAP V1 and sent again.
If the response to FSM indicates an error condition, or if a time out occurs, the MWN information is sent in a new GSM MAP _FORWARD_SHORT_MESSAGE when the IIF receives a new GSM MAP _UPDATE_LOCATION, GSM MAP
_READY_FOR_SHORT_MESSAGE or GSM MAP _NOTE_MS_PRESENT message.
38
39
4.5.3.1.2 Qualification Directive Invoke Received
161

10
11
12
13
14
15
16
6
7
8
9
1
2
3
4
5
17
18
19
20
N.S0028
If the IIF receives a QUALDIR INVOKE message from the TDMA ANSI-41 HLR with
MWNCOUNT and MNWTYPE parameters set to valid values, it shall set the Message waiting
Notification flag and it shall send a GSM MAP FORWARD_SHORT_MESSAGE. Refer to Table
130 for the mapping of parameters between ANSI-QUALDIR and GSM-
_MAP_FORWARD_SHORT_MESSAGE.
If an error is detected in the QUALDIR INVOKE message, a Reject or Return Error message is sent back to the sending node. No other processing is executed.
If a successful response is received for the FSM, the IF shall clear the Message Waiting
Notification flag.
If the error in the response to FSM indicates that the receiving node does not support MAP V2, the GSM_FSM message shall be reformatted in MAP V1 and sent again.
If an error is received in the response to FSM, or if a time out occurs, the MWN information is sent in a new GSM MAP _FORWARD_SHORT_MESSAGE when the IIF receives a new GSM
MAP _UPDATE_LOCATION, GSM MAP _READY_FOR_SHORT_MESSAGE or GSM MAP
_NOTE_MS_PRESENT message.
ANSI136 41 Foreign Mode
Two methods of delivering Message Waiting Notification to a native GSM subscriber roaming in
ANSI136 41 are supported.
21
22
23
24
25
26
27
28
29
30
36
37
38
39
31
32
33
34
35
4.5.3.1.3 GSM SMS Mapped to ANSI-41 Qualification Directive Invoke
If the IIF receives a GSM_FORWARD_SHORT_MESSAGE with MWN information, it shall set the message waiting Notification flag and it shall format and send an ANSI_MAP_ QUALDIR message to the serving ANSI-41 MSC/VLR. Refer to Table 131 for the mapping of parameters from GSM MAP _FORWARD_SHORT_MESSAGE to ANSI_QUALDIR.
When the IIF receives a positive acknowledgment to the Qualification Directive message, it shall send an acknowledgment to the Forward Short Message with an error indication of
“absent subscriber”. This shall ensure that the MWN information is delivered again from the home system when the subscriber returns home.
If the MS registers in a different ANSI-41 MSC/VLR after some time, the MWN information is delivered in the Registration Return Result message
If the IIF detects errors in the FORWARD_SHORT_MESSAGE, an error indication is sent in the response message. This shall cause the GSM MSC/VLR to send an error indication to the GSM
Message Center.
If a Return Error or Reject is received in response to the ANSI_MAP Qualification Directive
INVOKE, the error code is mapped into the corresponding Forward Short Message error code as described in Table 135.
162

N.S0028
1
8
9
10
2
3
4
5
6
7
11
12
13
14
15
16
17
4.5.3.1.4 GSM SMS Mapped to TDMAANSI-41 SMS using GHOST or WEMT
If the IIF receives GSM MAP _FORWARD_SHORT_MESSAGE for a mobile that is GHOST or
WEMT capable, it shall send an ANSI_MAP Short Message Delivery Point to Point INVOKE message. Refer to Table 132 for the mapping of parameters from GSM MAP
_FORWARD_SHORT_MESSAGE to ANSI-SMDPP.
When the Return Result for the SMDPP is received, the IIF sends back a positive acknowledgement to the Forward Short Message.
If the IIF detects errors in the FORWARD_SHORT_MESSAGE, an error indication is sent in the response message. This shall cause the GSM MSC/VLR to send an error indication to the GSM
Message Center.
If a Return Error or Reject is received in response to the ANSI_MAP Short Message Delivery
Point to Point INVOKE, the error code is mapped into the corresponding Forward Short
Message error code as described in Table 117.
18
19
20
21
22
23
24
25
26
27
28
4.5.3.2 Mapping of Messages, Parameters & Parameter Values
The IIF shall perform the mapping of messages, parameters and parameter values related to message waiting notification in accordance with the tables presented. Within the following tables, the parameters are identified as either being Mandatory (M), Conditional (C), Service
Provider Optional (O) or Service User Optional (U) in accordance with the definitions given in
GSM 09.02 [3] and ANSI-41 [6], [7], 0.
Table 127 shows the mapping between ANSI MAP messages and GSM MAP messages related to Message Waiting Notification in GSM Foreign ModeTable 128 shows the mapping between GSM MAP messages and ANSI MAP messages related to Message Waiting
Notification in ANSI136 41 Foreign Mode.
29 Table 127: Message Waiting Notification in GSM Foreign Mode Message Mapping
ANSI MAP Messages GSM MAP Messages
Regnot FORWARD_SHORT_MESSAGE
QUALDIR FORWARD_SHORT_MESASGE
30
31
32
Table 128: Message Waiting Notification in ANSI136 41 Foreign Mode Message Mapping
GSM MAP Messages ANSI MAP Messages
FORWARD_SHORT_MESSAGE QUALDIR
FORWARD_SHORT_MESSAGE SMDPP
163

19
20
21
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
N.S0028
When the IIF receives either a GSM MAP message or an ANSI MAP message, it shall apply the following rules regarding the handling of parameters within those messages:
The IIF shall populate mandatory parameters in messages sent by the IIF, regardless of whether mapping of parameters is possible.
The IIF may populate optional parameters in messages sent by the IIF, regardless of whether mapping of parameters is possible.
All parameters shall be populated in accordance with either GSM 09.02 [3] or ANSI-41 [6], [7],
0.
Table 129 through Table 134 show the mapping of parameters, which the IIF shall perform regardless of the mode of operation (GSM Foreign Mode or ANSI136 41 Foreign Mode).
Where there is no direct mapping for parameters, a ‘-‘ has been entered in the corresponding table.
Table 129: Regnot to Forward Short Message for Message Waiting Notification
Parameter Mapping
ANSI-41 Regnot Return Result Status GSM MT FSM
MWNCount (from Profile)
MWNType (from Profile)
O
O
SM-RP-DA = IMSI
SM-RP-OA = IIF address
SM-RP-UI
See Table 133 and Table 134 for details of encoding of this parameter.
More Messages to Send = no
Status
M
M
M
M
Note 1
17
18
Table 130: QUALDIR to Forward Short Message for Message Waiting Notification
Parameter Mapping
ANSI-41 QUALDIR
MSID
MWNCount (from Profile)
MWNType (from Profile)
_
GSM MT FSM
SM-RP-DA (M) = IMSI
SM-RP-OA (M) = IIF address
SM-RP-UI (M)
See Table 133 and Table 134 for details of encoding of this parameter.
More Messages to Send (M) = no
(Note 1)
Note 1: This parameter is only valid for MAP V2.
164

N.S0028
7
8
4
5
6
1
2
3
Table 131: Forward Short Message to QUALDIR for Message Waiting Notification
Parameter Mapping
GSM MT FSM
IMSI
Status ANSI QUALDIR
M MSID
ESN
Status
M
M
M
Profile only
SystemMyTypeCode M _
SM-RP-UI M MWNCount (in Profile)
MWNType (in Profile)
R
R
Table 132: Forward Short Message to SMDPP for Message Waiting Notification
Parameter Mapping
GSM MT FSM
SM-RP-UI (M)
Originating Address
IMSI
Status
M
ANSI SMDPP
SMS_BearerData
Status
M
M
M
GHOST or WEMT
SMS-OriginalOriginatingAddress O
M ESN
MSID
O
R
165

4
5
1
2
3
N.S0028
Table 133: SM-RP-UI in Message FORWARD-SHORT-MESSAGE For MAP V2 Parameter
Encoding
FIELD VALUE ENCODING
METHOD
All Message Type
Indicator
More Messages to
Send
Reply Path
Status Report
Indication
Protocol Identifier
Set to value “SMS-DELIVER”
Set to value “No more messages are waiting for the MS in this SC”
Set to value “TP-Reply-Path is not set in this
SMS-DELIVER”
Set to value “A status report is not requested”
Set to value “0”
All
All
All
Service Center Time
Stamp
Created by the IIF
User Data Length Number of characters
Originating Address Encoded as follows to support delivering 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 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.
All
All
All
CPHS
166

N.S0028
4
5
1
2
3
Table 133: SM-RP-UI in Message FORWARD-SHORT-MESSAGE For MAP V2 Parameter
Encoding (concluded)
FIELD VALUE ENCODING
METHOD
DCS Data Coding Scheme - Set bit numbers 7654 to discard (value
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
Indicator parameter (one bit) indicating that the UD
User Data field contains a Header. Set to value “The beginning of the TP-UD field contains a
Header in addition to the short message”. one space character using the default alphabet
User Data Header - First octet: Length of the User Data
Header.
- Second octet: Information Element
Identifier (IEI) = Special SMS Message
Indication (value 01).
- 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
UD
UD
UD
167

4
5
1
2
3
N.S0028
Table 134: SM-RP-UI in Message FORWARD_SHORT-MESSAGE for MAP V1 Parameter
Encoding
FIELD VALUE
Message Type Indicator
More Messages to Send
Protocol Identifier
Set to value “SMS-DELIVER”
Set to value “No more messages are waiting for the MS in this SC”
Set to value “0”
ENCODING
METHOD
All
All
All
All
All
All
Service Center Time Stamp Created by the IIF
User Data Length Number of characters
User Data one space character using the default alphabet
Originating Address
Data Coding Scheme
Encoded as follows to support delivering 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.
- Set bit numbers 7654 to discard (value
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).
CPHS
DCS
168

N.S0028
1
2
3
4.5.3.3 Error Handling
4
5
6
4.5.3.3.1 Error Handling at the Reception of a Forward Short Message
Refer to 4.5.1.3 Error Handling
7
8
4.5.3.3.2
9
10
Error Mapping from ANSI QUALDIR to GSM FSM
Table 135: qualdir return error to FORWARD_SHORT_MESSAGE response Error
Mapping
QUALDIR (Errors)
Unrecognized MSID
Unrecognized ESN
FORWARD_SHORT_MESSAGE
SMS Delivery Failure
SMS Delivery Failure
11
12
13
4.5.3.3.3
14
Error Mapping from ANSI SMSDPP to GSM FSM
Table 136: SMSDPP to FORWARD_SHORT_MESSAGE response Error Mapping
SMSDPP (Cause Code)
Destination Busy
Address Vacant
No Pager Response
No Acknowledgement
Destination Out of Service
Destination No Longer at this Address
SMS Delivery Postponed
FORWARD_SHORT_MESSAGE
Subscriber Busy for MT-SMS
Absent Subscriber
Absent Subscriber
Absent Subscriber
Absent Subscriber
Absent Subscriber
Absent Subscriber
Any other value System Failure
15
16
169

N.S0028
1
2
3
4
5
6
The following text describes the procedures in the IIF for the case in which an ANSI136 41 subscriber requests GPRS service while operating in GSM foreign mode.
Note: There is no GPRS service for GSM subscribers roaming in an ANSI136 41 radio environment.
7
8
9
10
11
12
Existing mobility procedures described in either GSM 09.02 [3] or ANSI-41 [6] are also directly applicable to the IIF when it is emulating a GSM or ANSI-41 functional network element.
Enhancements and modifications to GSM 02.60 [4] and ANSI-41 [7], 0 are also applicable.
13
14
15
16
17
4.6.1.1 Detailed Procedures
The following text contains the procedures in the IIF for the case in which the ANSI-41 subscriber requests GPRS services while roaming in foreign mode (i.e., while roaming in a
GSM network).
30
31
32
33
34
35
36
37
38
39
25
26
27
28
29
18
19
20
21
22
23
24
The IIF contains location information (SGSN number) relating to the roaming subscriber.
Therefore, the IIF needs to be updated at each change in SGSN. The IIF shall translate GSM
MAP messages to ANSI-41 MAP messages and vice versa when the subscribers home ANSI-
41 HLR needs updating. The subscriber’s ANSI-41 HLR shall be updated in the following cases:
•
When the subscriber’s MS registers in an SGSN in a GSM network, when previously registered in an ANSI-41 network;
•
When the subscriber’s MS registers in an ANSI-41 network, when previously registered in an SGSN in a GSM network;
The subscriber’s home HLR may be updated in the following cases:
•
When the subscriber’s MS (accessing a GSM Network) registers in another SGSN within the same GSM network. The IIF acts like a GPRS HLR/AuC in this case.
•
When the subscriber’s MS (accessing a GSM network) registers in a SGSN when previously registered in a GSM VLR within the same GSM network.
When the HLR is updated, the IIF conveys a unique identifier to the ANSI-41 HLR identifying the SGSN/GSM VLR or IIF, depending on Multiple MSCIDs optional support.
If the IIF receives a GSM_ MAP_UPDATE_GPRS_LOCATION _REQUEST, it shall compare the received routing area information with any previously stored routing area information. If the received and previously stored routing area information are different, the IIF shall determine if the location updating is allowed and update the corresponding subscriber record accordingly
170

N.S0028
29
30
31
32
33
34
35
36
21
22
23
24
25
26
27
8
9
10
11
12
13
4
5
6
7
1
2
3
14
15
16
17
18
19
20 and send a GSM MAP _CANCEL_LOCATION_REQUEST to the old SGSN. If there is no previously SGSN stored routing area information in the IIF, the IIF shall determine if the location updating is allowed and update the corresponding subscriber record accordingly.
If the IIF receives a GSM MAP _MS_PURGE_REQUEST, it shall check the contents of the message for errors. If errors exist, the IIF shall send a GSM MAP _MS_PURGE_RESPONSE indicating the reason for failure and the MS purged flag shall not be set. If no errors exist, the
IIF shall check if the received SGSN number matches the stored SGSN number.
If the received SGSN number and the stored SGSN number match, the IIF shall set the MS purged flag and shall send both a GSM MAP _MS_PURGE_RESPONSE to the SGSN and an
ANSI_MAP_MS_INACTIVE to the ANSI-41 HLR and awaits a response from the HLR.
If the received SGSN number and the stored SGSN number do not match, the IIF sends a GSM
MAP _PURGE_MS_RESPONSE containing an empty result to indicate that the MS purged flag is not set.
If the MS requests a combined GSM and GPRS attach, then the SGSN requests a GPRS location update to the IIF (acting as a GPRS HLR) and then the GSM-MSC requests a CS location update. CS location update and mobility procedures are described in 4.1 Mobility
Procedures.
4.6.1.2 Mapping of Messages, Parameters & Parameter Values
The following tables present the mapping of presents the mapping of messages, parameters and parameter values that the IIF shall perform.
4.6.1.2.1 Mapping of Messages
Table 137 shows the mapping between GSM MAP messages and ANSI MAP messages related to GPRS Location Registration when necessary.
28 Table 137: Location Updating GPRS in GSM Foreign Mode Message Mapping
GSM MAP Messages ANSI MAP Messages
MAP_UPDATE_GPRS_LOCATION_REQUEST REGNOT
MAP_INSERT_SUBSCRIBER_DATA_REQUEST
1
regnot
MAP_UPDATE_GPRS_LOCATION_RESPONSE regnot
2
1
This procedure is used to download GPRS subscriber data to the SGSN.
2
This message can also contain error values if the location updating procedure is unsuccessful.
If the location updating procedure fails, the mapping is as shown in 4.1.1.3.
Table 3 shows the mapping between GSM MAP messages and ANSI MAP messages for MS
Purge operation. Table 4 shows the mapping between GSM MAP messages and ANSI MAP messages related to Location Cancellation.
171

1
2
3
4
5
N.S0028
4.6.1.2.1.2 Mapping of Parameters
The following tables show the mapping between the parameters in GSM MAP messages and parameters in the corresponding ANSI-41 messages when necessary.
Table 138: MAP_UPDATE_GPRS_LOCATION_REQUEST → REGNOT Parameter Mapping
GSM MAP
_UPDATE_GPRS_LOCATION_
REQUEST
Status ANSI_MAP_REGNOT Status
SGSN address
SGSN Number
M
M
M
MSID M
MSCID (Serving MSC)
1
M
-
6
10
11
7
8
9
- PC_SSN (Serving MSC or VLR) O
SystemAccessType
2
- O
TerminalType
2
O
TransactionCapability
2
- O
1
This parameter is used to convey an identity from the IIF to the ANSI-41 HLR identifying either the SGSN or the IIF. In the case where the IIF supports multiple MSCIDs this identity is a unique identity associated with the SGSN. Otherwize, the identity shall be that of the IIF.
2
Parameters are included in ANSI-41-C and later.
172

N.S0028
1
2
3
4
Table 139 shows the mapping of parameters for GSM MAP
_INSERT_SUBSCRIBER_DATA_REQUEST to Regnot when necessary.
Table 139: MAP_INSERT_SUBSCRIBER_DATA_REQUEST → regnot Parameter Mapping
GSM MAP
_INSERT_SUBSCRIBER_DATA
_REQUEST
Status regnot Status
M
HLR)
5
6
7
8
9
10
11
IMSI C -
1
This parameter is itself a macro containing a number of other parameters. As far as mapping of parameters is concerned, the IIF shall map the contents of the ‘Profile’ macro in the ANSI-41-
D ‘regnot’ to the contents of the GSM MAP _INSERT_SUBSCRIBER_DATA_REQUEST as shown in Table 140:
173

1
N.S0028
Table 140: MAP_UPDATE GPRS LOCATION RESPONSE → regnot Parameter Mapping
GSM MAP _UPDATE_
GPRS_LOCATION_RESPONSE
Statu s regnot Status
M
HLR)
HLR number
1, 2
3
O
10
11
12
13
5
6
7
8
9
2
3
4
1
The presence of this parameter is mandatory in case of successful HLR updating.
2
These parameters are used to convey a unique identifier from the IIF to the serving MSC/VLR, identifying the HLR.
3
This parameter is itself a macro containing a number of other parameters. As far as mapping of parameters is concerned, the IIF shall map the contents of the ‘Profile’ macro in the ANSI-41-
D ‘regnot’ to the contents of the GSM MAP _INSERT_SUBSCRIBER_DATA_REQUEST as shown in Table 92.
As far as mapping of parameters is concerned, the IIF shall map the contents of the ‘Profile’ macro in the ANSI-41-D GSM MAP _INSERT_SUBSCRIBER_DATA_REQUEST as shown in
Table 141:
174

N.S0028
1
2 Table 141: MAP_INSERT_SUBSCRIBER_DATA_REQUEST → profile ‘macro’ Mapping
MAP_INSERT_SUBSCRIBER_D
ATA_REQUEST
Status regnot Status
- O
Subscriber Status
Bearer service List
Teleservice List
Forwarding information List
C
C
C
C
-
-
CallingFeaturesIndicator
1
O
Regional Subscription Data C -
Call barring information List
3
C OriginationIndicator
2
O
VLR CAMEL Subscription Info
4
C OriginationTriggers
4
O
CUG information List
SS-Data List
EMLPP Subscription Data
Operator Determined Barring
General data
Operator Determined Barring
HPLMN data
5
Operator Determined Barring
HPLMN data
5
Roaming Restriction Due To
Unsupported Feature
C -
C
6
CallingFeaturesIndicator
1
O
C -
C OriginationIndicator
2
O
C OriginationIndicator
2
O
C RestrictionDigits
C -
O
Call barring information List
3
C SMS_OriginationRestrictions
7
O
Call barring information List
3
C SMS_TerminationRestrictions
8
O
175

1
2
3
4
11
12
13
14
15
16
5
6
7
8
9
10
22
23
24
25
17
18
19
20
21
N.S0028
Table 141: MAP_INSERT_SUBSCRIBER_DATA_REQUEST → macro profile Mapping
(concluded)
MAP_INSERT_SUBSCRIBER_D
ATA_REQUEST
Status
Call barring information List
3
C TerminationRestrictionCode O
VLR CAMEL Subscription Info C TerminationTriggers
4
O
Voice Broadcast Data
Voice Group Call Data
C
C -
SS-Data List
6
SS-Data List
6
North American Equal Access preferred Carrier Id
Roaming Restricted In SGSN
Due To Unsupported Feature
9
GPRS Subscription Data
10
Network access mode
11
SMS_OriginationRestrictions
U -
C -
7
SMS_TerminationRestrictions
O
8
O
1
The CallingFeaturesIndicator parameter provides a status of several ANSI supplementary services. This information may map into one or more GSM MAP parameters as shown in Table
92.
2
The OriginationIndicator parameter defines the type of calls that a MS is allowed to make.
This information may map into one or more GSM MAP parameters as shown in Table 92.
3
The Call barring information List is a list of the call barring supplementary services that are either active, quiescent or not active for individual or all teleservices. This information may map into one or more ANSI MAP parameters as shown in Table 92.
4
Camel/WIN interworking is out of the scope of this version of the standard.
5
Operator Determined Barring HPLMN data may map into one or more ANSI MAP parameters as shown in Table 92.
6
The SS-Data List may map into one or more ANSI MAP parameters as shown in Table 92.
7
The SMS_OriginationRestrictions may map into one or more GSM MAP parameters as shown in Table 92.
8
The SMS_TerminationRestrictions may map into one or more ANSI MAP parameters as shown in Table 92.
9
The IIFmay decide to include this parameter in the request if certain services or features are indicated as not supported by the SGSN. This parameter is used only by the SGSN.
10
This parameter contains a list of PDP-contexts a user has subscribed to. At GPRS location updating the IIF shall include the complete GPRS Subscription Data. When there is a change in
176

N.S0028
4
5
6
7
8
9
1
2
3
10
11
12
GPRS subscriber data the IIF shall include only the new and/or modified PDP contexts. When the SGSN receives GPRS Subscription Data it shall check if the received data has to be considered as the entire GPRS subscription data. If so, it shall replace the stored GPRS
Subscription Data with the received data set, otherwise it shall replace the data only for the modified PDP contexts (if any) and add the new PDP contexts (if any) to the stored GPRS
Subscription Data. If GPRS Subscription Data is omitted in the Insert Subscriber Data operation the SGSN shall keep the previously stored GPRS Subscription Data.If the SGSN detects that there is overlapping in the information received within a dialogue, it shall send the error
Unexpected Data Value. This parameter is used only by the SGSN.
11
This parameter defines the access capabilities of a registered MS.
Error handling, Fault Recovery procedures and Error Code mapping are described in 4.1
Mobility Procedures.
13
14
15
16
17
18
19
The Automatic Call Delivery procedure is invoked in the IIF, when a terminating call attempt results in a request for routing information from the IIF.
The following procedures are applicable at the IIF for GPRS in GSM Foreign mode Automatic
Call Delivery:
20
21
22
23
24
25
26
27
28
29
30
31
4.6.2.1 Detailed Procedures
If the IIF receives an ANSI MAP_RoutingRequest Invoke message from the ANSI-41 HLR, it shall check if the terminating call can be placed to that subscriber. Call delivery to an MS that is roaming in a GPRS network in GSM foreign mode shall be delivered only if the subscriber is registered with a GSM serving MSC/VLR. As such, the IIF (acting as a GSM HLR) sends the
GSM serving MSC/VLR a MAP Provide Roaming Number (PRN) see 4.2.1 Call Delivery.
If the MS is attached for GPRS-only services, incoming calls are not deliverable to the subscriber. Upon the reception of ROUTEREQ, the IIF determines if the MS is attached for
GPRS-only services and if so, the IIF shall not deliver the call. The IIF sends a routreq with the field “AccessDeniedReason” set to “No Page Response” or “Unavailable”.
32
33
34
35
36
37
38
39
40
4.6.2.1.1 Mapping of Messages, Parameters & Parameter Values
In this case, the IIF has the calling party DN available (from the ROUTEREQ message). Upon the reception of a ROUTREQ, if the MS is only GPRS attached, the IIF proceeds to act as an
SMS-SC and sends an FSM to the SGSN requesting the SGSN to deliver an SMS message containing the calling party’s DN to the MS. The mapping of parameters is shown in the following table:
177

1
N.S0028
Table 141 A: ROUTREQ → MT_Forward Short Message Parameter Mapping
4
5
2
3
6
BillingID (Originating)
MSCID (Originating MSC)
-
SystemMyTypeCode (Originating
MSC)
M -
M international format. See
4.5.2.4
M
More Messages to Send = no M
M -
M
CallingPartyNumberString1
(Note 1)
CallingPartyNumberString2
(Note 1)
O SM-RP-UI
O SM-RP-UI
M
M
DMH_AlternateBillingDigits O -
(Note 2)
MSCIdentificationNumber R -
PC_SSN (Originating MSC) R -
R
178

N.S0028
1
-
-
-
Table 141 A : ROUTREQ → MT_Forward Short Message Parameter Mapping (concluded)
ROUTREQ Status Status
SenderIdentificationNumber O -
- MSC Number M
-
GMSC address
GSM Bearer Capability
Network Signal Info
Announcement
Call Reference Number
R
C
C
C
R
5
6
7
2
3
4
8
9
10
11
12
13
14
Note 1: For encoding of those parameters, refer to “4.3.4 Calling Number/Line Identification
Presentation/Restriction”.
Note 2: May also be directly retrieved from the subscriber profile pre-provisioned in the IIF.
15
4.6.2.1.1.1 Error Code Mapping
Appropriate errors for an MS attached to both GPRS and non-GPRS services are described in
4.2.1.3
Appropriate AccessDeniedReason parameter values in the RoutingRequest Return Result for the case of a call delivery attempt to an MS attached for GPRS-only services:
AccessDeniedReason
Unavailable
No page Response
179

4
5
6
7
8
1
2
3
N.S0028
The following describes the procedures for MS terminated and MS originated SMS while the
MS is roaming in a GPRS network in GSM foreign mode and is GPRS attached.
Existing mobility procedures described in either GSM 09.02 [3] and GSM 03.60 [5] or ANSI-41
[6], [7], 0 are also directly applicable to the IIF when it is emulating a GPRS, GSM or ANSI-41 functional network element.
If the MS is both GSM CS attached as well as GPRS attached, then the IIF shall act as a GSM
SMS-SC.
9
10
11
12
4.6.3.1 Short Message Service via CMT
The Short Message Service procedure is used to deliver short text messages to and from mobile subscribers.
13
14
15
16
17
4.6.3.1.1 Detailed Procedures
The following procedures are applicable at the IIF for Short Message Service. Mobile
Terminating SMS and Mobile Originated SMS using the CMT teleservice ID are described.
18
19
25
26
27
28
29
30
20
21
22
23
24
31
32
33
34
4.6.3.1.1.1 Mobile Terminating SMS
If the IIF receives an ANSI-41 Short Message Delivery Point to Point message it shall check if the MS location is known and if the subscriber is reachable. If both conditions are true, the IIF shall format and send a GSM_ MAP_FORWARD_SHORT_MESSAGE (FSM) to the SGSN serving the mobile. Refer to Table 109 for the mapping of parameters from ANSI_SMDPP to
GSM MAP _FORWARD_SHORT_MESSAGE.
If a successful response is received for the FSM, the IIF shall return SMDPP Return Result message. If the MS's location is not known, or if the MS is not reachable or if the response to the FSM indicates the short message was not delivered to the mobile, the IIF shall set the SMS
Delivery Pending flag for the subscriber. The IIF shall then return an SMDPP Return Result message with an appropriate SMS_CauseCode value. Refer to 4.5.1.3 Error Handling for the values of SMS_CauseCode returned.
If errors are detected when the SMDPP is received, the message may be rejected if it cannot be processed or if mandatory parameters are missing. Otherwise, the IIF shall return a SMDPP
Return Result message with the appropriate SMS_CauseCode value. Refer to 4.5.1.3 Error
Handling for the description of error conditions and corresponding SMS_CauseCode values.
180

N.S0028
4
5
1
2
3
6
7
8
If the response to FSM indicates a failure in the delivery of the short message, the IIF shall map the cause value received to a corresponding SMS_CauseCode value in the
SMDPP Return Result, as described in
Table 116.
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
32
33
34
35
36
37
38
26
27
28
29
30
31
39
40
4.6.3.1.1.2 Alerting for GPRS in GSM Foreign Mode in either CMT or GHOST /WEMT format
The SMS Alert procedure is used for alerting the SGSN when the MS is available for short messaging after a short message transfer has failed because the mobile subscriber is not reachable or when the MS has indicated that it has no memory capacity to accept a short message.
Upon receipt of a READY_FOR_SM message, the IIF shall store the originating SGSN address and Invoke ID in the subscriber’s profile. It shall map the GSM_READY_FOR_SM message to the ANSI_SMSNOT INVOKE message as described in Table 119.
It shall populate the SMS_Address parameter with the IIF address. All other parameters are ignored.
The ANSI_SMSNOT INVOKE is then transmitted to the subscriber’s SGSN with local
Transaction ID. Finally, the IIF shall return a READY_FOR_SM_ACK message with no arguments to the originating SGSN.
Upon receipt of a SMSNOT RR message, the IIF shall associate the SMSNOT Transaction ID with the Invoke ID.
If the IIF receives a GSM MAP _READY_FOR-SHORT_MESSAGE and the Delivery pending flag is set for the subscriber, the IIF shall send an ANSI_MAP_SMS_NOTIFICATION message to the home Message Center. The IIF shall clear the MNRG flag if Alert Reason is set to MS present or The Memory Capacity Exceeded Flag ( MCEF) flag if Alert Reason is set to Memory
Available and the flags were previously set. If the Alert Reason indicates the mobile present for non GPRS situation, or when the update location procedure has been successfully completed or Supplementary Service Control request is received, the MS not reachable flag (MNR) is cleared and the service centre alert procedure is initiated. If the memory capacity exceeded flag is set, the MS not reachable flag is cleared and stored reason for absence for non GPRS are cleared but the alert procedure is not started. If the Alert Reason indicates the mobile present for GPRS situation, or when the Update GPRS location procedure has been successfully completed, the MS not reachable for GPRS (MNRG) flag is cleared and the service centre alert procedure is initiated. The mapping of parameters is described in Table 142.
The ANSI-41 MC shall re-send message SMDPP to deliver the short message to the subscriber.
181

1
2
3
N.S0028
Table 142: Alerting for an ANSI136 41 Subscriber for GPRS in GSM Foreign Mode
Parameter Mapping
GSM MAP _READY_FOR_SM Status ANSI_SMSNOT Status
4
5
Alert Reason M
MSID M
-
Alert Reason Indicator
1
C
SMS_Address (IIF Address) R
1
This parameter indicates that the alert reason is sent to the HLR due to GPRS activity.
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
4.6.3.1.1.3 Mobile Originating SMS for GPRS in GSM Foreign Mode
If the IIF receives a GSM_FORWARD_SHORT_MESSAGE for a mobile originated short message, it shall format and send an ANSI_MAP_SMDPP message to the home Message
Center. Refer to Table 114 for the mapping of parameters from GSM MAP
_FORWARD_SHORT_MESSAGE to ANSI_SMDPP.
If the IIF receives a positive acknowledgment to the SMDPP message, it shall send a positive acknowledgment to the Forward Short Message.
If the IIF receives a negative acknowledgment to the SMDPP message, it shall map the received SMS_CauseCode value into a corresponding error code in the FSM Response message as described in Table 117. Also the IIF shall set the Mobile Not Reachable for GPRS
(MNRG) GSM SMS flag.
If the IIF detects errors in the FORWARD_SHORT_MESSAGE, an error indication is sent in the response message. Refer to 4.5.1.3 for the handling of errors at the reception of FSM.
182

N.S0028
1
2
3
4
5
4.6.3.1.2 Mapping of Messages, Parameters & Parameter Values
The IIF shall perform the mapping of messages, parameters and parameter values related to
Short Message Service in accordance with the tables presented in 4.5.1.2.1.
6
7
8
4.6.3.1.3 Error Handling
Error handling is described in 4.5.1.3
9
10
11
12
4.6.4.1 Detailed Procedures
27
28
29
30
31
32
33
13
14
15
16
17
18
19
20
21
22
23
24
25
26
4.6.4.1.1 SMS Delivery for an ANSI136 41 Subscriber for GPRS in GSM Foreign
Mode
Upon receipt of an SMSDeliveryPointToPoint INVOKE message, the IIF shall store the originating MC address and transaction ID. It shall map the ANSI_SMDPP message into a
GSM_FSM message and populate the subscriber’s known SGSN into the DPC. The IIF transmits the GSM_FSM message with local Invoke ID.
The mapping of parameters is described in Table 121.
The IIF transmits the GSM_FSM message with local Invoke ID.
Upon receipt of the FORWARD_SHORT_MESSAGE_ACK message, the IIF shall associate the
Invoke ID with SMDPP transaction ID and map the GSM_FSM_ACK message into an
ANSI_SMDPP RETURN RESULT.
Next, it populates the stored originating SGSN address into the DPC and populates the transaction ID.
If the User Error parameter is populated in the GSM_FSM_ACK, then map this value into the SMS_CauseCode according to
Table 116.
Finally, the ANSI_SMDPP RR is transmitted to the originator.
183

N.S0028
1
9
10
11
12
13
14
2
3
4
5
6
7
8
Upon receipt of a MO_FORWARD_SHORT_MESSAGE, the IIF shall store the address of the originating SGSN and Invoke ID. It shall map the GSM_MO_FSM to ANSI_SMDPP INVOKE.
The address of the subscriber’s TSA (from the SM RP DA – Service Center Address) is mapped according to 4.5.2.4 into the SMS_DestinationAddress. The IIF transmits the
ANSI_SMDPP INVOKE message with local transaction ID. The mapping of parameters is described in Table 123.
Upon receipt of a SMSDeliveryPointToPoint RR message, the IIF shall associate the SMDPP transaction ID with Invoke ID and map the ANSI_SMDPP RR to the GSM_FSM_ACK.
Next, it populates the stored originating SGSN address and Invoke ID. If SMS_CauseCode parameter is populated in the ANSI_SMDPP RR message, then map value into User error parameter according to Table 117.
Finally, transmit the GSM_FSM_ACK to the originating SGSN.
15
16
17
18
19
4.6.4.2 Mapping of Messages, Parameters & Parameter Values
The IIF shall perform the mapping of messages, parameters and parameter values related to
Short Message Service in accordance with the tables presented in 4.5.2.2.
20
21
22
4.6.4.3 Error Handling
Error handling is described in 4.5.1.3
23
24
25
26
27
28
29
The Message Waiting Notification procedure is used to notify a mobile subscriber of voice mail messages added or removed in his voice mail system. 4.6.5 shows only the changes needed to support GPRS service for an ANSI136 41 subscriber in GSM foreign mode.
If the subscriber is both GSM CS attached as well as GPRS attached, then the IIF shall act like a GSM SMS-SC.
30
31
32
33
34
35
36
37
38
4.6.5.1 Detailed Procedures
4.6.5.1.1 Registration Notification Return Result with MWN Information Received
When the IIF receives a Registration Notification Return Result message with MWNCOUNT and MWNTYPE parameters set to valid values, it shall send a GSM SMS with the MWN information.
The IIF shall then format and send a GSM MAP_FORWARD_SHORT_MESSAGE. Refer to
Table 129 for the mapping of parameters from ANSI-41 regnot return result to GSM MAP
_FORWARD_SHORT_MESSAGE.
184

N.S0028
7
8
9
10
11
12
13
1
2
3
4
5
6
14
15
16
17
18
19
If a successful response is received for the FSM, the IIF shall clear the Message Waiting
Notification flag.
If the response to FSM indicates an error condition, or if a time out occurs, the MWN information is sent in a new GSM MAP _FORWARD_SHORT_MESSAGE when the IIF receives a new GSM MAP _UPDATE_GPRS_LOCATION, GSM MAP
_READY_FOR_SHORT_MESSAGE or GSM MAP _NOTE_MS_PRESENT message.
When the IIF receives a QUALDIR INVOKE message from the ANSI-41 HLR with
MWNCOUNT and MNWTYPE parameters set to valid values, it shall set the Message waiting
Notification flag and the IIF shall send a GSM MAP FORWARD_SHORT_MESSAGE. Refer to
Table 130 for the mapping of parameters between ANSI-QUALDIR and GSM-
_MAP_FORWARD_SHORT_MESSAGE.
If an error is detected in the QUALDIR INVOKE message, a Reject or Return Error message is sent back to the sending node. No other processing is executed.
If a successful response is received for the FSM, the IIF shall clear the Message Waiting
Notification flag.
If an error is received in the response to FSM, or if a time out occurs, the MWN information is sent in a new GSM MAP _FORWARD_SHORT_MESSAGE when the IIF receives a new GSM
MAP _UPDATE_GPRS_LOCATION, GSM MAP _READY_FOR_SHORT_MESSAGE or GSM
MAP _NOTE_MS_PRESENT message.
20
21
22
23
4.6.5.2 Mapping of Messages, Parameters & Parameter Values
The IIF shall perform the mapping of messages, parameters and parameter values related to message waiting notification in accordance with 4.5.3.2.
24
25
26
27
4.6.5.3 Error Handling
Error Handling Refer to 4.5.1.3
28
29
30
31
32
33
34
4.6.5.3.1 Error Mapping
Refer to 4.5.3.3.2 Error Mapping.
185

1
2
N.S0028
5
6
7
8
9
10
11
12
13
14
3
4
(Normative)
GHOST may be used as the delivery teleservice from a short message entity to a mobile station operating in ANSI-136 Native Mode through a SMSC, which is providing IIF functionality at the GSM TP-layer. In this case, normal ANSI-41 procedures are used to deliver the GHOST teleservice between ANSI-41 network elements and normal ANSI-136 procedures are used to deliver the GHOST teleservice from the serving MSC to the mobile station. The SMSC is responsible for identifying the MS as GHOST capable and for packaging the short message in the proper format using the GHOST teleservice for delivery to the MS.
15
16
17
18
19
20
If the short message entity is an MS originating a message using the Cellular Messaging
Teleservice (CMT) teleservice to the GHOST MS, then upon receipt of the CMT message the
SMSC proceeds as follows.
27
28
29
30
31
32
33
21
22
23
24
25
26
After determining the incoming CMT message is destined for an MS that supports the GHOST teleservice, (the method to perform this identification is internal to the SMSC and beyond the scope of this standard) the SMSC shall determine the status and location of the targeted MS using normal ANSI-41 procedures.
If the MS is unavailable or the location is unknown, the SMSC shall set an internal retry schedule or wait for notification from HLR. Otherwise, it shall populate address delivery information and optional parameters per normal ANSI-41 procedures. Next, it shall map the contents of the SMS_BearerData per Table 143 and populate the SMS_TeleserviceIdentifier with the GHOST teleservice identifier. Finally, it shall transmit the SMDPP INVOKE message to the serving MSC.
34
35
36
37
When the SMSC receives the SMDPP Invoke message from a CMT capable MS, the SMSC follows normal ANSI-41 procedures except it replaces the CMT value of 32513d with the
186

N.S0028
1
2
3
4
GHOST value. In addition, the following parameter mapping related to ANSI-136-710 shall be performed as indicated in Table 143.
5 Table 143: ANSI-136-710 to GHOST Parameter Mapping.
SMDPP/CMT Parameter Status Handling
ANSI-136 Message Type
Indicator
ANSI-136 Message Reference
ANSI-136 Privacy Indicator
ANSI-136 Urgency Indicator
ANSI-136 Delivery
Acknowledgement Request
M
M
M
M
M
Only SMS_SUBMIT shall be relayed as a GHOST message.
SMS_DELIVERY_ACK and
SMS_MANUAL_ACK shall be discarded if the destination is a
GHOST MS.
-
-
Not mapped. Handled by the SMSC.
Not mapped. See note 1.
ANSI-136 Manual
Acknowledgement Request
ANSI-136 Message Updating
M -
ANSI-136 User Data Unit
ANSI-136 Validity Period
M
M
O
Not mapped. Handled internally by the
MC.
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
Not mapped. Handled internally by the
MC.
ANSI-136 Deferred Delivery Time
ANSI-136 Call Back Number
ANSI-136 Call Back Number
Presentation
O Not mapped. Handled internally by the
MC.
O See §A.3.1
O -
ANSI-136 Call Back Number
Alpha Tag
O -
6
7
8
9
10
11
12
13
Note 1: In GSM, delivery acknowledgement indicates that the data is stored at the MS. In ANSI-
136, delivery acknowledgement is triggered by an action of the MS user (displaying the message). Therefore this parameter is not mapped. It is a local decision for the operator as to how to treat MO messages requesting these acknowledgements. The recommended procedure for operators is for the MC to return a SMS DELIVERY ACK to the originator upon receipt of a positive delivery confirmation from the terminating mobile. The procedures and format of the
SMS DELIVERY ACK message shall follow ANSI-136-710.
187

1
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 message
Status Value/derivation
TP-Message-Type-Indicator M SMS-DELIVER
TP-More-Messages-To-Send M Set appropriately by the MC based on the MC message store. 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-Protocol-Identifier
TP-Service-Center-Timestamp
M
M
SMS_OriginalOriginatingAddress
Set to 00000000
136 User Data Unit
Set bit number 3 per §A.2.1
Set bit numbers 1&0 to value “Class 1”.
Set by the MC to the appropriate value
136 User Data Unit
136 User Data Unit.
4
5
6
7
8
9
No additional error handling procedures beyond those in ANSI-41D are required.
10
11
12
13
14
GHOST may be used to deliver teleservices from a mobile station operating in ANSI-136 Native
Mode to an MS-based short message entity, which only supports the CMT ID without the involvement of an IIF.
188

N.S0028
1
26
27
28
29
30
2
3
8
9
10
11
12
4
5
6
7
13
14
15
16
17
18
19
20
21
22
23
24
25
31
32
The mobile station formulates a GSM SMS PDU and adds the GHOST header to the GSM
SMS PDU. If required, it adds the TSAR header to the GHOST teleservice. Next, it inserts the
GHOST teleservice into the Higher Layer Protocol Data Unit of the R-Data Unit and adds the
GHOST HLPI. An R-DATA message is formulated and sent to the ANSI-136 BMI.
The ANSI-136 MSC follows normal procedures and translates the R-DATA message to an
ANSI-41 SMDPP Invoke message and sends it to the originator’s home MC. The MC destination address can be specified in the Teleservice Server Address. {Alternatively, MIN to
MC GTT or a routing table in the MSC may be used if the TSA is not present.} The MSC does not open the Higher Layer Protocol Data Unit, but converts it directly to SMS_BearerData.
For the mobile station in ANSI-136 Native Mode, the Teleservice Server Address shall indicate that the home Teleservice Server is the home Message Center. Upon receipt of the SMDPP
Invoke message, the SMSC responds with a SMDPP RR per normal ANSI-41 procedures.
The SMSC then identifies the destination address as an MS that supports CMT. (The method to perform this identification is internal to the SMSC and beyond the scope of this standard.) It then determines the status and location of the targeted MS using normal ANSI-41 procedures.
If the MS is unavailable or location is unknown, the SMSC shall set its internal retry schedule or wait for notification from HLR
Otherwise, it shall populate the address delivery information and optional parameters per normal ANSI-41 procedures. Next, it maps the contents of the SMS_BearerData per Table 145 and MT CMT message are derived from
Table 146 and populates the SMS_TeleserviceIdentifier with the CMT teleservice identifier.
Finally, the SMSC transmits the SMDPP Invoke message to the serving MSC.
Supported user data mappings
The following user data mappings should be supported:
IS-136 Encoding
IRA/ITU.T50
User Specific
GSM TP-Data-Coding-Scheme
GSM Default Alphabet. Mapping of the user data content should be performed.
8-bit data. No mapping of user data content needs to be performed.
189

1
N.S0028
9
10
2
3
4
5
6
7
When the SMSC receives the SMDPP Invoke message from a GHOST capable MS, the SMSC follows normal ANSI-41 procedures except it replaces the GHOST value of {to be provided by
TR45.3} with the CMT value of 32513d. In addition, the following parameter mapping related to
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
TP-Reply-Path
Set appropriately by the MC based on the
MC message store.
Set to “TP-Reply-Path parameter is not set”
TP-User-Data-Header-Indicator
TP-Status-Report-Indicator
Set to “the TP-UD field contains only the short message”
Set to “a status report will not be returned to the SME”
TP-Originating-Address
TP-Protocol-Identifier
TP-Data-Coding-Scheme
TP-Service-Center-Timestamp
TP-User-Data-Length
Set to the
SMS_OriginalOriginatingAddress
Set to 00000000
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”.
Set by the MC to the appropriate value
TP-User-Data
Set based on information in the ANSI-136
User Data Unit
Set based on information in the ANSI-136
User Data Unit.
190

N.S0028
1
2
3
Table 146 describes where the parameters in the MT CMT message are derived from
SMDPP/GHOST Parameter
TP-Message-Type-Indicator
TP-Reject-Duplicates
TP-Validity-Period-Format
Table 146: CMT Derived Values
Handling
Only SMS-SUBMIT shall be relayed as a
CMT message. SMS-STATUS-REPORT shall be discarded if the destination is a
CMT MS.
Not mapped. Handled internally by the
MC.
Not mapped. Handled internally by the
MC.
TP-User-Data-Header-Indicator
TP-Status-Report-Request
TP-Message-Reference
TP-Destination-Address
TP-Protocol-Identifier
TP-Data-Coding-Scheme
TP-Validity-Period
TP-User-Data-Length
TP-User-Data
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
Not mapped. Handled internally by the
MC. See Table 148
Mapped to ANSI-136 Message Reference
Mapped to
SMS_OriginalDestinationAddress
Not mapped. Handled internally by the
MC.
Mapped to ANSI-136 User Data Unit
Not mapped. Handled internally by the
MC.
Mapped to ANSI-136 User Data Unit
Mapped to ANSI-136 User Data Unit
4
5
6
7
8
9
If the TP-Status-Report-Request is requested, then Table 148 provides mapping to identify the status of a message being sent to a CMT mobile from a GHOST mobile. The SMS-STATUS-
REPORT is encapsulated in a new SMDPP message to the status requester. The derived values for the SMS-STATUS-REPORT are contained in Table 148.
191

3
4
1
N.S0028
2 Table 147: SMS_CauseCode to TP-STATUS Mapping
(ANSI-41)
None sent. Positive
ACK.
(future item for SMPP interworking)
Short message transaction completed
0000000
(GSM)
Short message received by the SME
Short message forwarded by the SC to the SME but the SC is unable to confirm delivery
Reserved values the SC
0000 0010 Network resource shortage
0010 0100 SMS delivery postponed
Not mapped
0100 0010 Other radio interface problems
0010000..0011111 Values specific to each SC
Temporary error,
SC still trying to transfer SM
0100000 Congestion
0100010 No response from SME
Not mapped 0100101 available
Error in SME
Not mapped
0110 0000 Encoding problem
0010 0110 Destination no longer at this address
0110000..0111111 Values specific to each SC
Permanent error,
SC is not making any more transfer attempts
1000000 Remote procedure error
192

N.S0028
1
2 Table 147: SMS_CauseCode to TP-STATUS Mapping (concluded)
(ANSI-41)
0010 0111 Other terminal problem
Not mapped
Not mapped
MC internal procedure
MC internal procedure
MC internal procedure
MC internal procedure
1000010
1000011
1000101
1000110
1000111
1001000
1001001
(GSM)
Connection rejected by SME
Not obtainable available
No interworking available
SM Validity Period Expired
SM Deleted by originating
SME
SM Deleted by SC
Administration
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)
Not mapped
0010 0011 Destination resource shortage
Not mapped
Not mapped
0110 0100 SMS not supported
1010000..1011111 Values specific to each SC
Temporary error,
SC is not making any more transfer attempts
1100000 Congestion
1100001
1100010
1100011
SME busy
No response from SME
Service rejected
Not mapped 1100101 available
Error in SME
3
4
5
Not mapped 1110000..1111111
All other values mapped to Service Rejected (0110 0011).
Values specific to each SC
193

1
2
N.S0028
Table 148: SMS-STATUS-REPORT Derived Values
Parameter in SMS-STATUS-
REPORT
Status Value/derivation
TP-Message-Type-Indicator M
TP-User-Data-Header-Indication O
TP-More-Messages-to-Send
TP-Status-Report-Qualifier
M
M
TP-Message-Reference
TP-Recipient-Address
M
M
TP-Service-Center-Time-Stamp M
TP-Discharge-Time M
TP-Status M
Set to “SMS-STATUS-REPORT”
Not used or Set to value = 0
Set to value = 1
Set to value = 0
Set by the MC to the appropriate value
Set by the MC to the appropriate value
Set by the MC to the appropriate value
Set by the MC to the appropriate value
Set per Table 147
3
4
5
6
7
8
9
No additional error handling procedures beyond those in ANSI-41D are required.
194

N.S0028
1
2
10
11
12
13
8
9
6
7
3
4
5
The Callback service enables SMS subscribers to be able to return calls to callers automatically in an easy-to-use manner. Callers may provide their callback number to the SMSC by various methods, including:
DTMF entry through a voicemail system, etc.
Paging the SMS subscriber directly (e.g., numeric paging entry)
Automatically through the Original Origination Address
As part of the text body of a short message
The callback number can be dialed through a single button (e.g., pressing the SEND key) or a simple key sequence (i.e., 3 or less keystrokes) of the MS. Using the capabilities of the MS, the user may edit the callback number prior to originating the call.
14
15
16
17
18
19
20
21
22
23
24
25
26
27
A.3.1.1 CMT to GHOST
The CMT mobile shall follow existing procedures as described in ANSI-136-710 to transmit a callback number. If the MO-SMS is routed through an IIF to get to the subscriber’s home
SMSC, callback number information is in the application layer of the message and thus is passed transparently.
Upon receipt at the SMSC, if the message contains the Callback Number parameter, then the
SMSC shall extract the callback number from this parameter and place it at the end of the TP-
User-Data field preceded by the phrase “CALLBACK: <space>”. Carriers should limit the message size they inform their subscribers that they are allowed to send to account for the sending of the callback number.
28
29
30
31
32
33
34
35
36
37
38
39
A.3.1.2 External SME (SMPP to GHOST)
Upon receiving of a submitted short message for delivery, the SMSC shall determine if the recipient’s mobile requires short message delivery via GHOST. This determination by the
SMSC is an internal process and is beyond the scope of this document. If the recipient’s mobile uses CMT to receive short messages, then the SMSC shall delivery the message via procedures as defined in ANSI-136-710. If the recipient’s mobile uses GHOST, then the SMSC shall extract the callback number from the SMPP callback_num parameter and place it at the end of the TP-User-Data field preceded by the phrase “CALLBACK: <space>”. Carriers should limit the message size they inform their subscribers that they are allowed to send to account for the sending of the callback number.
195

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
N.S0028
A.3.1.3 GHOST to CMT
Since there is no GSM equivalent to the ANSI-136 Callback Number parameter, two solutions exist to provide equivalent feature functionality.
1. The SMSC shall parse each message looking for a callback number based upon a set of rules to determine the Callback number. It shall then place this number in the ANSI-136 Callback Number parameter.
2. The SMSC shall transparently map the TP-User-Data to the SMS_BearerData per Table 122. The MS shall be capable of parsing the message and extracting the callback number based upon the number appearing in the MS display screen.
The subscriber shall be able to press one button (e.g., SEND key) to callback the number showing on the display screen.
Solution 2 above is the recommended procedure to provide a callback number under this scenario.
16
17
18
19
20
21
22
A.3.2.1 CMT to GHOST
Mapping for messages, parameters and parameter values shall be as according to §A.1.2
Mapping of Messages, Parameters & Parameter Values.
23
24
25
26
27
A.3.2.2 External SME
ANSI-41/136 mapping for messages, parameters and parameter values for a GHOST message is not affected by the Callback Number procedures.
28
29
30
31
32
A.3.2.3 GHOST to CMT
Mapping for messages, parameters and parameter values shall be as according to §A.2.2
Mapping of Messages, Parameters & Parameter Values.
33
34
35
36
No additional error handling procedures beyond those in ANSI-41D are required.
196

N.S0028
1
12
13
14
15
16
17
18
2
5
6
7
8
9
3
4
(Informative)
This annex is informative and describes processing that does not affect the IIF.
A mobile station shall respond to a received GHOST teleservice after processing the relay layer. If the relay layer generates a failure, then the mobile station shall map the resulting RP-
Cause value into its equivalent R-Cause code according to Table 149.
10
11
Table 149: RP-ERROR Cause to R-Cause for Mobile Station Response to Mobile
Terminated Transfer Attempt.
GSM RP-ERROR Cause
Memory capacity exceeded (22)
Invalid short message transfer reference value (81)
Semantically incorrect message(95)
Invalid mandatory information (96)
Message type nonexistent or not implemented (97)
Message not compatible with short message protocol state (98)
Information element nonexistent or not implemented (99)
Protocol error, unspecified (111)
Interworking, unspecified (127)
All other values
ANSI-136 R-Cause
Memory capacity exceeded (22)
Invalid short message transfer reference value (81)
Invalid message, unspecified (95)
Mandatory information element error (96)
Message type non-existent or not implemented (97)
Message not compatible with the short message transfer state (101)
Information element non-existent or not implemented (99)
Protocol error, unspecified (111)
Interworking, unspecified (127)
Protocol error, unspecified (111)
At the ANSI-136 MSC, the R-Cause code returned by a mobile station is mapped into a corresponding ANSI-41 SMS_CauseCode for inclusion in an SMDPP Return Result message.
At the ANSI-136 MSC, the ANSI-41 SMS_CauseCodes are mapped to ANSI-136 R-DATA
REJECT R-Cause codes according to Table 150. The mobile station in turn maps the R-Cause codes to RP-ERROR Causes according to Table 151.
197

3
4
5
1
2
N.S0028
Table 150: ANSI-41 SMS_CauseCode to ANSI-136 R-Cause Code Mapping
ANSI-41 SMS_CauseCode
Network failure (3)
Other network problems (5)
ANSI-136 R-Cause
Network out of order (38)
Network out of order (38)
SMS origination denied (97)
SMS not supported (100)
Address translation failure (1)
Unidentified subscriber (28) or
Facility rejected (29)
Requested facility not implemented (69)
Destination out of service (27) or
Unknown subscriber (30)
Congestion (42) Network resource shortage (2)
Table 151: ANSI-136 R-Cause Code to RP-ERROR Cause Mapping within the Mobile
Station
ANSI-136 R-Cause
Destination out of service (27)
Unidentified subscriber (28)
Facility rejected (29)
RP-ERROR Cause
Destination out of service (27)
Unidentified subscriber (28)
Facility rejected (29)
Unknown subscriber (30)
Network out of order (38)
Congestion (42)
Unknown subscriber (30)
Network out of order (38)
Congestion (42)
Requested facility not implemented ((69) Requested facility not implemented (69)
6
7
12
13
14
15
10
11
8
9
(Informative)
Optionally, IIF may support one way-roaming only from CDMA to GSM networks.
In this case, all the mapping tables are applicable only in GSM Foreign Mode.
The IIF maps the ANSI-41 authentication parameters to the GSM triplets
All the changes are made on the assumption that the new requirements for UIM/handsets are working. Table 152 shows the location updating mapping in the GSM foreign mode.
198

N.S0028
1
10
11
7
8
9
4
5
6
2
3
Table 152: UPDATE_LOCATION_REQUEST ->REGNOT Parameter Mapping
GSM MAP
_UPDATE_LOCATION_REQUE
ST
IMSI
MSC Address
-
-
-
Status
M
M
1
ANSI_MAP_REGNOT
ElectronicSerialNumber
MSID
MSCID (Serving MSC)
1
QualificationInformationCode
SystemMyTypeCode
MSCIdentificationNumber
Status
M
M
M
M
M
O
Table 152: UPDATE_LOCATION_REQUEST ↔ REGNOT Parameter Mapping (concluded)
GSM MAP
_UPDATE_LOCATION_REQUE
ST
Status ANSI_MAP_REGNOT Status
VLR Number
-
-
-
LMSI
Supported CAMEL Phases
-
M
U
C
-
PC_SSN (Serving MSC or VLR) O
SystemAccessType
2
O
TerminalType
2
TransactionCapability
2
O
O
-
-
-SYSACCTYPE
3
O
1
These parameters are used to convey a unique identifier from the IIF to the HLR, identifying the serving MSC/VLR.
2
Parameters are included in ANSI specifications IS-41-C and later.
3
SYSACCTYPE parameter is required for the one-way CDMA to GSM roaming optional scenario and in this case the parameter must be set by IIF to indicate GSM access type.
199

1
2
N.S0028
200