Wireless Intelligent Network Support For Location Based Services (3GPP2)

3GPP2 X.
S0009-0
Version 1.0
Date: June 2004
Wireless Intelligent Network Support for

Location Based Services
COPYRIGHT
3GPP2 and its Organizational Partners claim copyright in this document and individual
Organizational Partners may copyright and issue documents or standards publications in
individual Organizational Partner's name based on this document. Requests for
reproduction of this document should be directed to the 3GPP2 Secretariat at
secretariat@3gpp2.org. Requests to reproduce individual Organizational Partner's
documents should be directed to that Organizational Partner. See www.3gpp2.org for more
information.
Revision History
Revision Date
Rev. 0 Initial Publication June 2004
X.S0009
1 WIRELESS INTELLIGENT NETWORK SUPPORT FOR LOCATION BASED SERVICES

2
3
4
5 CONTENTS
6
7
List of Figures ......................................................................................................................................................... v
8
9
10
List of Tables.......................................................................................................................................................... vi
11
12 Revision History....................................................................................................................................................vii
13
14 Introduction ............................................................................................................................................................. 1
15
16 1 Objective ................................................................................................................................................... 1
17
18
2 References................................................................................................................................................. 1
19
3 Organization.............................................................................................................................................. 1
20
21 4 Assumptions.............................................................................................................................................. 2
22
23 5 Editorial Conventions ............................................................................................................................... 3
24
25 Feature Descriptions................................................................................................................................................ 4
26
27 2 References................................................................................................................................................. 4
28
2.1 Normative References ................................................................................................................ 4
29
30 2.2 Informative References .............................................................................................................. 4
31
32 3 Definitions and Concepts.......................................................................................................................... 5
33 3.1 Definitions .................................................................................................................................. 5
34
35 4 Fleet and Asset Management (FAM)........................................................................................................ 6
36
4.1 Normal Procedures With Successful Outcome .......................................................................... 6
37
38 4.2 Exception Procedures or Unsuccessful Outcome....................................................................... 8
39
4.3 Alternative Procedures ............................................................................................................... 9
40
41 4.4 Interactions With Other Wireless Services................................................................................. 9
42
43
5 Location Based Charging (LBC) ............................................................................................................ 10
44 5.1 Normal Procedures With Successful Outcome ........................................................................ 10
45
46
5.2 Exception Procedures or Unsuccessful Outcome..................................................................... 12
47 5.3 Alternative Procedures ............................................................................................................. 13
48
5.4 Interactions With Other Wireless Services............................................................................... 13
49
50
6 Location-Based Information Service (LBIS).......................................................................................... 17
51
52 6.1 Normal Procedures With Successful Outcome ........................................................................ 17
53 6.2 Exception Procedures or Unsuccessful Outcome..................................................................... 19
54
55
6.3 Alternative Procedures ............................................................................................................. 20
56 6.4 Interactions with Other Wireless Services ............................................................................... 20
57
58 7 Enhanced Call Routing (ECR)................................................................................................................ 22
59
60
i Contents
X.S0009
7.1 Normal Procedures With Successful Outcome.........................................................................22 1

2
7.2 Exception Procedures or Unsuccessful Outcome .....................................................................23 3
7.3 Alternative Procedures..............................................................................................................24 4

5
7.4 Interactions With Other Wireless Services ...............................................................................24 6
7
TIA/EIA-41.1-D Modifications.............................................................................................................................26 8
9
4 Symbols and Abbreviations ....................................................................................................................26 10
11
8.1 Fleet and Asset Management (FAM)........................................................................................27 13

14
8.1.1 FAM for MS in Home System ...................................................................................27
15
8.1.1.1 FAM for MS Powers on in Home System................................................27 16
8.1.1.2 FAM for MS Power Down .......................................................................29 17
8.1.2 FAM Tracking of Target MS .....................................................................................30 18

19
8.1.3 Single Introducing Star Invocation of FAM Tracking ...............................................33
20
8.1.4 Feature Code Invocation of FAM Tracking ...............................................................35 21
8.2 Location Based Charging (LBC) ..............................................................................................37 22

23
8.2.1 LBC Call Origination .................................................................................................37
24
8.2.2 LBC Call Delivery: Local Termination at Originating MSC .....................................40 25
8.2.3 LBC Call Termination in Visited System ..................................................................45 26
8.2.4 Successful Position Determination for LBC After Intersystem Handoff ...................50 27
28
8.2.5 Unsuccessful LBC Call Origination: LIR Service Denial..........................................52
29
8.3 Location Based Information Services (LBIS)...........................................................................53 30
8.3.1 Single_Introducing_Star Invocation of LBIS on SCP................................................53 31

32
8.3.2 Single_introducing_Star Invocation of LBIS on a Service Node ..............................54
33
8.3.3 Feature Code Invocation of LBIS...............................................................................56 34
8.3.4 Unsuccessful Single_introducing_Star Invocation of LBIS on a Service Node ........58 35
36
8.3.5 LBIS Invocation Upon MS Registration ....................................................................60
37
8.3.6 LBIS Triggered in the Visited System: SLP and MPC on Same Platform ................62 38
8.3.7 LBIS Triggered in Visited System: Separate SLP and MPC .....................................64 39
40
8.4 Enhanced Call Routing (ECR)..................................................................................................67
41
8.4.1 Successful Enhanced Call Routing.............................................................................67 42
8.4.2 Unsuccessful Enhanced Call Routing: MS Position Not Available ...........................69 43
8.4.3 Unsuccessful Enhanced Call Routing: LIR Service Denial .......................................71 44

45
8.4.4 Unsuccessful Enhanced Call Routing: Routing Number Not Available....................72
46
8.4.5 Successful Enhanced Call Routing Invoked by Dialing Special Number..................74 47
8.5 Non-SIM Registration Reporting..............................................................................................76 48

49
8.5.1 Non-SIM Report of MS Registration .........................................................................76
50
8.5.2 Non-SIM Report of MS Registration to Multiple SCFs.............................................78 51
8.5.3 Non-SIM Report of MS Deregistration......................................................................80 52
8.5.4 Activation or Deactivation of Registration Report.....................................................81 53

54
8.5.5 Activation or Deactivation of Registration Report: MDN MS Identifier...................82
55
56
58
5 Data Transfer Services ............................................................................................................................83
59
60
Contents ii
X.S0009
1 5.1 SS7-Based Data Transfer Services ........................................................................................... 83

2
3 6 Application Services ............................................................................................................................... 83
4
6.4 MAP Operations....................................................................................................................... 83
5
6 6.4.1 General ....................................................................................................................... 83
7 6.4.1.2 Operation Specifiers................................................................................. 83
8 6.4.2 Operation Definitions................................................................................................. 83
9
6.4.2.13 FeatureRequest......................................................................................... 84
10
11
6.4.2.29 MSInactive ............................................................................................... 89
12 6.4.2.30 OriginationRequest .................................................................................. 90
13 6.4.2.37 RegistrationNotification........................................................................... 95
14 6.4.2.h ServiceRequest......................................................................................... 96
15
6.4.2.i AnalyzedInformation ............................................................................... 99
16
6.4.2.z CallControlDirective .............................................................................. 104
17
18
6.4.2.an InterSystemPositionRequest .................................................................. 106
19 6.4.2.au LCSParameterRequest ........................................................................... 110
20 6.4.2.av StatusNotificationRequest...................................................................... 111
21
6.5 Map Parameters ...................................................................................................................... 112
22
23 6.5.1 General ..................................................................................................................... 112
24 6.5.1.1 Parameter Identifiers .............................................................................. 112
25 6.5.2 Parameter Definitions .............................................................................................. 112
26
6.5.2.gw RegistrationReport ................................................................................. 112
27
28
29
TIA/EIA-41.6-D Modifications .......................................................................................................................... 113
30 4.14 Feature Request ...................................................................................................................... 113
31
4.14.1 MSC Detecting Feature Request.............................................................................. 113
32
33 4.28 Location Request .................................................................................................................... 116
34 4.28.2 HLR Receiving LocationRequest INVOKE ............................................................ 116
35
4.30 MS Inactive ............................................................................................................................ 121
36
37 4.30.X HLR Initiating an MS Inactive................................................................................. 121
38 4.30.Y SCF Receiving an MSInactive INVOKE................................................................. 121
39
4.31 Origination Request................................................................................................................ 123
40
41 4.31.1 MSC Initiating an Origination Request ................................................................... 123
42 4.38 Registration Notification ........................................................................................................ 128
43
4.38.X HLR Initiating a Registration Notification .............................................................. 128
44
45 4.38.Y SCF Receiving a RegistrationNotification INVOKE .............................................. 128
46 4.T Call Control Directive ............................................................................................................ 130
47
4.T.1 SCF Initiating a Call Control Directive ................................................................... 130
48
49 4.T.2 MSC Receiving a CallControlDirective INVOKE .................................................. 131
50 4.Y LCS Parameter Request.......................................................................................................... 133
51
4.Y.2 SCF Initiating an LCS Parameter Request............................................................... 133
52
53 4.W InterSystem Position Request................................................................................................. 134
54 4.W.2 SCF Initiating an InterSystem Position Request...................................................... 134
55
56
4.FF Status Notification Request .................................................................................................... 135
57 4.FF.1 SCF Initiating Status Notification Request .............................................................. 135
58 4.FF.2 HLR Receiving StatusNotificationRequest INVOKE ............................................. 135
59
60
iii Contents
X.S0009
6.Y WIN Service Logic .................................................................................................................137 1

2
7 Operation Timer Values ........................................................................................................................139 3
4
Annex A (informative) ........................................................................................................................................140 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
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Contents iv
X.S0009
1
2
LIST OF FIGURES
3
4 Introduction
5
6 Feature Descriptions
7
8 TIA/EIA-41.1-D Modifications
9
11
12
Figure 1 FAM: MS Powers on in Home System ............................................................................. 27
13 Figure 2 FAM for MS Power Down................................................................................................ 29
14
Figure 3 FAM Tracking of Target MS ............................................................................................ 30
15
16 Figure 4 Single Introducing Star Invocation of FAM Tracking ...................................................... 33
17
Figure 5 Feature Code Invocation of FAM Tracking ...................................................................... 35
18
19 Figure 6 LBC Call Origination ........................................................................................................ 37
20
Figure 7 LBC Call Delivery: Local Termination at Originating MSC............................................ 41
21
22 Figure 8 LBC Call Termination in Visited System (1 of 2) ............................................................ 45
23 Figure 9 LBC Call Termination in Visited System (2 of 2) ............................................................ 48
24
25
Figure 10 Successful Position Determination for LBC After Intersystem Handoff.......................... 50
26 Figure 11 Unsuccessful LBC Call Origination: LIR Service Denial ................................................ 52
27
28
Figure 12 Single_Introducing_Star Invocation of LBIS on SCP ...................................................... 53
29 Figure 13 LBIS Invocation on Service Node from the Single_Introducing_Star Trigger ................ 54
30
Figure 14 Feature Code Invocation of LBIS ..................................................................................... 56
31
32 Figure 15 Unsuccessful Single_introducing_Star Invocation of LBIS on a Service Node ............... 58
33
Figure 16 LBIS Invocation Upon MS Registration ........................................................................... 60
34
35 Figure 17 LBIS Triggered in Visited System: SLP and MPC on Same Platform ............................. 62
36
Figure 18 LBIS Triggered in Visited System: Separate SLP and MPC ............................................ 64
37
38 Figure 19 Successful Enhanced Call Routing ................................................................................... 67
39 Figure 20 Unsuccessful Enhanced Call Routing: MS Position Not Available.................................. 69
40
41
Figure 21 Unsuccessful Enhanced Call Routing: LIR Service Denial .............................................. 71
42 Figure 22 Unsuccessful Enhanced Call Routing: Routing Number Not Available........................... 72
43
44
Figure 23 Successful Enhanced Call Routing Invoked by Dialing a Special Number...................... 74
45 Figure 24 Non-SIM Report of MS Registration ................................................................................ 76
46
Figure 25 Non-SIM Report of MS Registration to Multiple SCFs ................................................... 78
47
48 Figure 26 Non-SIM Report of MS Deregistration............................................................................. 80
49
Figure 27 Activation or Deactivation of Registration Report ........................................................... 81
50
51 Figure 28 Activation or Deactivation of Registration Report: MDN MS Identifier ......................... 82
52
54
56
57 Annex A (informative)
58
59
60
v List of Figures
X.S0009
LIST OF TABLES 1
2
3
4
Introduction
5
6
Feature Descriptions
7
Table 1 LBC Subscription Options.................................................................................................11 8
9
Table 2 LBIS Subscription Options................................................................................................18
10
11
TIA/EIA-41.1-D Modifications 12
13
15
17
Table 1 MTP Message Priority Values for TIA/EIA-41 Operations...............................................83
18
Table 2 TIA/EIA-41 MAP Operation Specifiers .............................................................................83 19
20
Table 3 Summary of MAP Operations ...........................................................................................83
21
Table 4 TIA/EIA-41 MAP Parameter Identifiers .........................................................................112 22
23
25
Table 1 SCF MSInactive Response ..............................................................................................122
26
Table 2 SCF RegistrationNotification Response ..........................................................................129 27
28
Table 3 HLR StatusNotificationRequest Response ......................................................................136
29
Table 63 Operation Timer Values ..................................................................................................139 30
31
Annex A (informative) 32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
List of Tables vi
X.S0009
1
2
REVISION HISTORY
3
4
5 Revision Date Remarks
6
0 June 2004 Initial Publication
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
vii Revision History

X.S0009
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
This page is intentiaonlly left blank.
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Revision History viii

X.S0009
1
2
INTRODUCTION
3
4 Fleet and Asset Management (FAM), Location Based Charging (LBC), Location Based
5 Information Service (LBIS) and Enhanced Call Routing (ECR) are WIN-based services that
6
enable the services to be tailored based on the subscriber’s current location (i.e., geographic
7
position). This document presents a recommended plan for the implementation of Wireless
8
Intelligent Network (WIN) capabilities that support these services.
9
10
11
12 1 OBJECTIVE
13
14
The purpose of this document is to describe FAM, LBC, LBIS and ECR, and to specify the
15
intersystem operations that enable a wireless system to provide these location-based services.
16
17
18
19 2 REFERENCES
20
21 This document builds on the following American National Standards Institute (ANSI)
22
standards:
23
24 TIA-664 TIA-664-000-B, Wireless Features Description; Telecommunications
25 Industry Association; July 2003
26
27 TIA/EIA-41 TIA/EIA-41-D, Cellular Radiotelecommunications Intersystem
28 Operations; Telecommunications Industry Association; December 1997
29
30 IS-764 TIA/EIA/IS-764, Wireless Calling Name Feature Descriptions;
31 Telecommunications Industry Association; April 1998
32
33 IS-771 TIA/EIA/IS-771, Wireless Intelligent Network; Telecommunication
34 Industry Association; December 1998.
35
36 IS-848 TIA/EIA/IS-848, Wireless Intelligent Network Capabilities for Enhanced
37 Charging Services; Telecommunications Industry Association:
38 October, 2000
39
40 J-STD-036 TIA/EIA J-STD-036-A, Wireless Enhanced Emergency Services Phase II;
41 Telecommunications Industry Association; March 2002
42
43
DMH TIA/EIA-124-D, Wireless Radio Telecommunication Intersystem Non-
44 Signaling Data Communication DMH (Data Message Handler);
45 Telecommunications Industry Association; December 2001
46
47
TIA-826 TIA-826-A, Wireless Intelligent Network Capabilities for Pre-Paid
48 Charging; Telecommunications Industry Association; November 2003
49
50
TIA-881 TIA-881, Location Services Enhancements; Telecommunications Industry
51
Association; March 2004
52
53
54 3 ORGANIZATION
55
56
This document is organized as follows:
57
58
59
60
Objective 1 Introduction
X.S0009
• The Feature Descriptions section provides feature descriptions for FAM, LBC, LBIS 1
2
and ECR according to the structure of TIA-664 “Wireless Features Descriptions”.
3
• The TIA/EIA-41.1-D Modifications section provides the modifications and additions 4
to TIA/EIA-41-D Chapter 1 “Functional Overview”. 5

6
to TIA/EIA-41-D Chapter 3 “Automatic Roaming Information Flows”. 8

9
• The TIA/EIA-41.5-D Modifications section the modifications and additions to 10
TIA/EIA-41-D Chapter 5 “Signaling Protocol”. 11
12
to TIA/EIA-41-D Chapter 6 “Signaling Procedures”. 14
15
• Annex A (informative) illustrates the relationship between TIA-881 and this document. 16
17
18
4 ASSUMPTIONS 19
20
21
The following assumptions were used in the development of this document: 22
23
a. The capabilities supported by this document are independent of any position
24
determination technology.
25
26
b. This document supports position information requests which are call associated and
27
non-call associated.
28
c. Position information storage is outside the scope of this document. 29

30
d. Subscriber profile information applicable to location based services in this document 31
uses the HLR-based profile access defined in TIA/EIA-41. 32

33
e. Zone operations and zone transition detection is the responsibility of application 34
service logic and is outside the scope of this document. 35
36
f. If an application requires periodic position information updates, the application can 37
periodically query an MPC for the Target MS position. 38
39
g. The interactions of location based services with multi-party and redirected calls are not 40
covered by this document and are for further study. 41
42
h. WIN service logic can perform application authentication and LIR authorization. The 43
WIN Service Logic platform has the current Location Information Restriction (LIR) 44
information available. 45
46
i. The interaction of the Location Based Charging service (LBC) and the Pre-paid 47
Charging (PPC) service has not been considered. 48
49
j. For the Enhanced Call Routing (ECR) service, WIN service logic is capable of making 50
the necessary association between geoposition received and routing digits for the 51
nearest ECR service center. The mechanism by which WIN service logic makes this 52
association is outside the scope of this document. 53
54
k. For subscriber-based location services, the SCF network entity will store the Mobile 55
Position Capability (MPCAP) for the subscriber (i.e., provisioned or obtained from the 56
HLR via the LCSParameterRequest operations). 57
58
59
60
Introduction 2 Assumptions
X.S0009
1
2
5 EDITORIAL CONVENTIONS
3
4 The following editorial conventions are used for this document:
5
6 • underline: addition
7
8 • cross out: deletion
9
10
• change bar: indicates additions or deletions
11
• new sub-sections are identified in the sub-section heading
12
13 • for clarity, new sub-sections are shown with vertical change bars but are not underlined
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Editorial Conventions 3 Introduction

X.S0009
FEATURE DESCRIPTIONS 1
2
3
This section provides the feature and service descriptions for Fleet and Asset Management 4
(FAM), Location Based Charging (LBC), Location Based Information Service (LBIS) and 5
Enhanced Call Routing (ECR) according to the structure of TIA/EIA-664. These are WIN based 6
services that can be tailored for the subscriber based on the MS user’s current geographic 7
8
position.
9
10
2 REFERENCES 11
12
13
14
2.1 Normative References 15

16
(See TIA-664, Page 3) 17
18
The following standards contain provisions that, through reference in this text, constitute 19
provisions of this Standard. At the time of publication, the editions indicated were valid. All 20
standards are subject to revision, and parties to agreements based on this Standard are 21
encouraged to investigate the possibility of applying the most recent editions of the standards 22
indicated below. ANSI and TIA maintain registers of currently valid national standards 23
published by them. 24
25
[IS-848] TIA/EIA/IS-848, Wireless Intelligent Network Capabilities for Enhanced 26
Charging Services; Telecommunications Industry Association; October 2000 27
28
[TIA-881] TIA-881, Location Services Enhancements; Telecommunications Industry 29
Association; March 2004 30
31
32
2.2 Informative References 33
34
(See TIA-664, Page 4)
35
The following references were used in the preparation of this document to ensure compatibility 36
with landline features. 37

38
• S.R0019, Location-Based Services System (LBSS); 3rd Generation Partnership 39
Project 2; September 22, 2000 40

41
• Standards Requirements Document, Wireless Intelligent Network Enhancements to 42
Support Location-Based Services [WIN Phase III]; Cellular Telecommunications 43
Industry Association; December 13, 1999 44

45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Feature Descriptions 4 References

X.S0009
1
2
3 DEFINITIONS AND CONCEPTS
3
4
5
3.1 Definitions
6
7 (See TIA-664, Page 6)
8
9 ECR
10
Enhanced Call Routing
11
12
13 FAM
14
Fleet and Asset Management
15
16
17 Geographic Zone
18
A geographic area assigned by a service provider that has meaning to the subscriber.
19
20
21 LBC
22 Location Based Charging
23
24
25 LBIS
26 Location Based Information Service
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Definitions and Concepts 5 Feature Descriptions

X.S0009
4 FLEET AND ASSET MANAGEMENT (FAM) 1

2
3
Fleet and Asset Management (FAM) enables the position of one or more mobile stations to be 4
tracked. A mobile station’s position information can be tracked if the MS is idle or engaged in 5
a call. 6
7
8
For typical FAM operation, two roles of FAM users are defined: FAM Member and FAM 9
Supervisor. 10
11
12
The FAM Member role applies to the FAM user or asset being tracked or monitored. All FAM
13
Members are equipped with appropriate mobile stations.
14
15
The FAM Supervisor role applies to the FAM user who is tracking (e.g., obtaining the position 16
of) active FAM Members. A FAM user may operate under both FAM Member and FAM 17
Supervisor roles simultaneously. A FAM Supervisor may activate or de-activate FAM service 18
for a FAM Member. FAM Supervisors may or may not be equipped with mobile stations. A 19
20
FAM Supervisor has a group of one or more FAM Members defined which it can track. A FAM
21
Supervisor may also be a FAM Member of a group.
22
23
For example, the FAM Supervisor can be the leader of a fleet, the owner of an asset or the parent 24
of a child. The FAM Member can be a driver of a fleet vehicle, the asset or the child. 25
26
27
The FAM Supervisor can have access to real-time geographic position information for all of the 28
FAM Members in its defined group. If this information is not available, the “best” available 29
position information may be provided with an indication of the reason the real-time information 30
is not available.The report of the FAM Member’s MS position includes the time at which the 31
position was determined. 32
33
34
FAM does not impact a FAM Member’s ability to originate or terminate calls.
35
36
Applicability to Telecommunications Services 37
38
FAM is applicable to all telecommunication services. 39
40
41
4.1 Normal Procedures With Successful Outcome 42

43
44
Authorization 45
46
FAM may be provided after pre-arrangement with the service provider. FAM Members must be 47
assigned to a FAM group. 48

49
50
De-Authorization 51
52
FAM may be withdrawn at the subscriber’s request or for administrative reasons. 53
54
55
Registration
56
57
FAM shall be registered upon authorization.
58
59
60
Feature Descriptions 6 Fleet and Asset Management (FAM)

X.S0009
1 De-Registration
2
3 FAM shall be de-registered upon de-authorization.
4
5
6 Activation
7
8 FAM may be activated upon authorization.
9
10
FAM Supervisor Role Activation of Group FAM Member
11
12
A FAM Supervisor may activate a FAM Member in a FAM group by specifying a FAM
13 activation feature code, as in:
14
15 * FC + FAM Member Identifier + SEND .
16
17
If the activation is accepted, the FAM Supervisor shall receive feature confirmation treatment.
18
19
20 If the FAM Member Identifier is not present, then the activation applies to the FAM
21 Supervisor’s own FAM Member status.
22
23
24
De-Activation
25
26
FAM shall be de-activated upon de-authorization.
27
28 FAM Supervisor Role De-Activation of Group Member
29
30
A FAM Supervisor may de-activate a FAM Member in a FAM group by specifying a FAM de-
31
activation feature code, as in:
32
33 * FC0 + FAM Member Identifier + SEND .
34
35
If the de-activation is accepted, the FAM Supervisor shall receive feature confirmation
36
treatment.
37
38
39 If the FAM Member Identifier is not present, then the de-activation applies to the FAM
40 Supervisor’s own FAM Member status.
41
42
43
Invocation
44
45
FAM Supervisor FAM Member Invocation
46
47 FAM is invoked when a FAM Supervisor requests the position information for a FAM
48 Member’s MS. The FAM Supervisor can request the current position information or multiple
49 reports of the FAM Member’s MS position. Multiple reports can be provided for a specified
50 duration of time (e.g., 24 hours). The reports can be provided periodically (e.g., every 30
51 minutes), when the location of the FAM Member’s MS changes (e.g., when the MS registers in
52 a new MSC), when the status of the FAM Member’s MS changes (e.g., when the MS powers
53
on, powers down, becomes inactive, becomes active), or when a call event (call origination or
54
termination) occurs.
55
56
57
58
59
60
Fleet and Asset Management (FAM) 7 Feature Descriptions

X.S0009
FAM Member Invocation 1

2
FAM is invoked when a FAM Member initiates the sending of the MS’s position information 3
to the FAM Supervisor. 4
5
Normal Operation with Successful Outcome 6

7
8
FAM Supervisor Initiated Operation 9
10
When a FAM Supervisor requests a FAM Member’s position information, the FAM Supervisor
11
will receive the position information.
12
13
FAM Member Initiated Operation 14
15
When a FAM Member initiates the sending of the MS’s position, the FAM Supervisor will be
16
sent the position information.
17
18
Call Detail Record 19
20
The system should record call detail information for the following: 21
22
• FAM activation and de-activation events 23
24
• FAM invocation events 25
26
• FAM usage duration
27
See DMH for the specific information to be included for each element. 28
29
30
4.2 Exception Procedures or Unsuccessful Outcome 31

32
33
34
Registration
35
36
None identified.
37
38
De-Registration 39
40
None identified. 41
42
43
Activation
44
45
None identified.
46
47
De-Activation 48
49
None identified. 50
51
52
Invocation
53
54
If the network determines that the position information for the specified FAM Member is not
55
available, the network may send the best available position information and the reason that the 56
position information is not available (e.g., MS inactive). 57
58
59
60
Feature Descriptions 8 Fleet and Asset Management (FAM)

X.S0009
1 Exceptions While Roaming

2
3 FAM may not be active for the MS when the MS is roaming outside the FAM service area.
4
5
6 Position information may not be available when an MS is roaming outside the FAM service
7 area.
8
9
Optionally, notification may be provided to the FAM Supervisor that the FAM member is
10
outside the FAM service area.
11
12
13 Exceptions During Intersystem Handoff
14
15 None identified.
16
17
18 4.3 Alternative Procedures
19
20
None identified.
21
22
23
24
4.4 Interactions With Other Wireless Services
25
26 No interactions have been identified with the following exceptions:
27
28
Location Information Restriction (LIR)
29
30
LIR is invoked before FAM.
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Fleet and Asset Management (FAM) 9 Feature Descriptions

X.S0009
5 LOCATION BASED CHARGING (LBC) 1

2
3
Location Based Charging (LBC) permits wireless subscribers to be charged different rates for 4
telecommunications services based on MS position. Different rates may be charged based on 5
position or changes in position. Different rates may be charged for the duration of the call or 6
any part thereof. LBC may be made available to individual subscribers or to groups of 7
8
subscribers based on logical associations or locations.
9
10
LBC Services for Individual Subscribers 11
12
LBC can be an individual subscriber service. LBC presents the opportunity to individually 13
define and benefit from geographical areas or zones that have been custom designed for that 14
particular subscriber’s daily route and life style. These geographical areas could be designed to 15
maximize benefit from the LBC service by providing lower rates for usage in a subscriber’s 16
most frequently visited areas. Examples could be a home zone or an office zone. The LBC 17
18
service could provide yet another rate for usage in shopping malls or golf courses or country
19
clubs. LBC services might also offer different rates for usage based on time of day or day of
20
week in the zones that they have defined.
21
22
Optional notification to subscribers of their current zone or billing tier may be provided. 23
Optional notification of changes in zone or billing tier may also be provided as the subscriber 24
crosses a geographic boundary 25

26
27
LBC Services for Commercial Business Groups 28
29
LBC can provide services for commercial business groups. LBC can provide corporate campus 30
areas, work zones or business zones that have multiple tier billing rates for groups of 31
commercials users. LBC may include Freephone (FPH), Premium Rate Charging (PRC) and 32
other specialized services that are based on the MS position (see IS-848). 33
34
35
Virtual national campus zones can also be part of a commercial LBC application supporting a 36
multiple location virtual national campus. Optional notification to commercial users as to which 37
zone or billing tier they are currently in may be provided. 38
39
40
Applicability to Telecommunications Services
41
42
LBC is applicable to all telecommunications services.
43
44

46
47
48
Authorization
49
50
LBC is provided after pre-arrangement with service providers.
51
52
53
54
55
56
57
58
59
60
Feature Descriptions 10 Location Based Charging (LBC)

X.S0009
1 The authorization may have the following subscription options:

2
3
Subscription Options Values
4
5
Demand. The subscriber is authorized to activate LBC for a single
6 call origination.
7
Single-Call Activation
8 Permanent. LBC may not be activated for single call originations.
9
10
Demand. The subscriber is authorized to control the activation and
11 All-Services Activation de-activation of LBC for all telecommunications services.
12
Permanent. LBC is active for all telecommunications services.
13
14 Table 1 LBC Subscription Options
15
16
17
De-Authorization
18
19
LBC may be withdrawn at the subscriber’s request, the business customer’s request or for
20
administrative reasons.
21
22 Registration
23
24 LBC has no registration.
25
26
27 De-Registration
28
29 LBC has no de-registration.
30
31
Activation
32
33
LBC can be activated using special feature codes on a subscriber or business customer basis.
34
35
36 LBC may be activated by a Demand “All-Services” Activation authorized subscriber by
37 specifying a feature code, as in:
38
39 * FC + SEND .
40
41
42
If the activation is accepted, the system shall indicate success with feature confirmation
43 treatment.
44
45
LBC may be activated by a Demand “Single-Call” Activation authorized subscriber by
46
specifying a feature code and a termination address:
47
48
49
* FC + # + termination address + SEND , or
50
51 * FC + termination address + SEND .
52
53
54
treatment. In this case LBC applies only to charges for voice telecommunication services
55
associated with the call origination attempt.
56
57
58
59
60
Location Based Charging (LBC) 11 Feature Descriptions

X.S0009
De-Activation 1
2
LBC can be de-activated using special feature codes on a subscriber or business customer basis. 3
4
LBC may be de-activated by a Demand “All-Services” Activation authorized subscriber by 5
specifying a feature code, as in: 6

7
8
* FC0 + SEND .
9
10
If the de-activation is accepted, the system shall indicate success with feature confirmation 11
treatment. 12
13
14
For a “Single-Call” activation, LBC is automatically de-activated after the single call attempt is
15
cleared. 16
17
Invocation 18
19
LBC may be invoked by initial mobile station registration, autonomous registration, or by calls 20
placed or received by the mobile station. 21

22
23
Normal Operation with Successful Outcome 24
25
Upon invocation, LBC can determine the MS location and establish the current zone of the 26
subscriber. LBC would notify the subscriber of their current zone. As the subscriber changes 27
zones the subscriber may be notified of changes to their zone and the rate may be changed. 28
29
30
Call Detail Record
31
32
The system should record call detail information for the following:
33
34
• LBC activation and de-activation events
35
• LBC invocation events 36

37
• MS position information at invocation (e.g., Serving Cell ID, Location Area ID, or 38
geographic position) 39
40
• Zone identification 41
42
• Zone boundary crossing 43
44
See DMH for the specific information to be included for each element.
45
46
47
5.2 Exception Procedures or Unsuccessful Outcome 48
49
50
Registration 51
52
None identified. 53
54
De-Registration 55
56
None identified. 57
58
59
60

X.S0009
1 Activation
2
3 None identified.
4
5
6 De-Activation
7
8 None identified.
9
10
Invocation
11
12
None identified
13
14
15 Exceptions While Roaming
16
17 If a mobile station with LBC active roams into a system that does not support the LBC location
18 service, the following services may be available to the subscriber:
19
20 a. Call to customer service.
21
b. Optional notification of the out of coverage situation using an appropriate method
22
(e.g., MS Display, SMS notification).
23
24
25 Exceptions During Intersystem Handoff
26
27 When the subscriber is handed off to a system that does not support LBC, the LBC service will
28 not be available in that system. Notification about rate change and zone change may not be
29 available and the LBC zone or location dependent rate will not be applied to the remainder of
30 the call.
31
32
33 The following services may be available to the subscriber:
34
35
a. Optional notification of the out of service coverage situation (e.g., warning tone, SMS
36
notification).
37
38
39
5.3 Alternative Procedures
40
41 If the LBC subscriber has “blocked” their location information, the network shall not provide
42 the mobile station location information to any service logic application unless specifically
43 authorized to do so. In such cases, the location information will not be available to the LBC
44 service logic, and alternative procedures shall be applied (e.g., call denial, connection to
45
customer service). See interaction with LIR service1.
46
47
48
49
5.4 Interactions With Other Wireless Services
50
51 No interactions have been identified with the following exceptions:
52
53
Call Delivery (CD)
54
55
LBC is invoked before CD.
56
57
58
59 1 See TIA-881 for a description of the Location Information Restriction (LIR) service
60

X.S0009
Call Forwarding—Busy (CFB) 1

2
LBC is invoked before CFB. 3

4
5
Call Forwarding—Default (CFD) 6
7
LBC is invoked before CFD. 8
9
10
Call Forwarding—No Answer (CFNA)
11
12
LBC is invoked before CFNA.
13
14
Call Forwarding—Unconditional (CFU) 15
16
LBC is invoked before CFU. 17
18
19
Call Transfer (CT)
20
21
LBC is invoked before CT.
22
23
Call Waiting (CW) 24
25
LBC is invoked before CW. 26
27
28
Calling Name Presentation (CNAP)
29
30
LBC is invoked before CNAP.
31
32
Calling Number Identification Presentation (CNIP) 33
34
LBC is invoked before CNIP. 35
36
37
Conference Calling (CC) 38
39
LBC is invoked before CC. 40
41
Data Privacy (DP) 42

43
For Further Study. 44

45
46
Do Not Disturb (DND) 47
48
LBC is invoked before DND 49
50
Emergency Services (9-1-1) 51

52
Emergency Services is invoked before LBC. 53

54
55
Enhanced Call Routing (ECR) 56
57
LBC is invoked before ECR. 58
59
60

X.S0009
1 Flexible Alerting (FA)

2
3 LBC is invoked before FA.
4
5
6 Group 3 Facsimile Service (G3 Fax)
7
8 Not applicable.
9
10
Incoming Call Screening (ICS)
11
12
LBC is invoked before ICS.
13
14
15 Location Based Information Services (LBIS)
16
17 LBC is invoked before LBIS.
18
19
20
21
LIR is invoked before LBC.
22
23
24 Message Waiting Notification (MWN)
25
26 LBC is invoked before MWN.
27
28
Mobile Access Hunting (MAH)
29
30
Interaction between LBC and MAH is beyond the scope of this standard.
31
32
33 Network Directed System Selection (NDSS)
34
35 LBC is invoked before NDSS.
36
37
38
Non-Public Mode Service (NP)
39
40
LBC is invoked before NP.
41
42 Over-the-Air Activation (OTA)
43
44 For Further Study.
45
46
47
Password Call Acceptance (PCA)
48
49
LBC is invoked before PCA.
50
51 Preferred Language (PL)
52
53 LBC is invoked before PL.
54
55
56 Priority Access and Channel Assignment (PACA)
57
58 LBC is invoked before PACA.
59
60

X.S0009
Remote Feature Control (RFC) 1

2
LBC is invoked before RFC. 3

4
5
Selective Call Acceptance (SCA) 6
7
LBC is invoked before SCA. 8
9
10
Speech Option Selection (SOS)
11
12
LBC is invoked before SOS.
13
14
Speech-to-Text Conversion (STC) 15
16
18
19
Subscriber PIN Access (SPINA)
20
21
For Further Study.
22
23
Subscriber PIN Intercept (SPINI) 24
25
27
28
Three-Way Calling (3WC)
29
30
LBC is invoked before 3WC.
31
32
User Group ID (UGID) 33
34
LBC is invoked before UGID. 35
36
37
Voice Controlled Dialing (VCD) 38
39
LBC is invoked before VCD. 40
41
Voice Controlled Feature Control (VCFC) 42

43
LBC is invoked before VCFC. 44

45
46
Voice Message Retrieval (VMR) 47
48
LBC is invoked before VMR. 49
50
Voice Privacy (VP) 51

52

54
55
Voice-based User Identification (VUI) 56
57
59
60

X.S0009
1
2 6 LOCATION-BASED INFORMATION SERVICE
3
4
(LBIS)
5
6 Location-Based Information Service (LBIS) allows subscribers to access information services
7 for which the information content is tailored to the current position of the MS.
8
9
Examples of LBIS include:
10
11 • Wireless network operator customer service,
12
13 • Concierge (hotel and restaurant finder) service,
14
15 • Travel and tourism information service,
16
17
• Automobile association roadside assistance service,
18
• Directory assistance (local yellow pages),
19
20
• Self-location (“Where am I?”) service,
21
22 • Traffic information service to help subscribers avoid traffic congestion.
23
24
25
The information may be delivered to the subscriber through various means, such as:
26
• Announcement,
27
28
• Call set-up to an Interactive Voice Response system,
29
30 • Graphical display (map, floor plan, picture, image),
31
32 • Text message,
33
34 • Call set-up to an operator.
35
36
LBIS may be invoked either:
37
38 1. Manually by the subscriber entering a feature code or originating a call to a directory
39 number associated with the specific location-based information service; or
40
41 2. Automatically by the network (such as the “power on” or “zone change” indicator); or
42
43 3. Periodically as determined by service logic.
44
45
46
47
LBIS is applicable to all telecommunications services.
48
49
50
51
6.1 Normal Procedures With Successful Outcome
52
53
Authorization
54
55
LBIS may be made generally available for all subscribers by the service provider or after pre-
56
57
arrangement with the service provider.
58
59
60
Location-Based Information Service (LBIS) 17 Feature Descriptions

X.S0009
LBIS may be authorized for the following options: 1

2
3
Subscription Options Values
4
Subscribed. The subscriber is authorized to invoke LBIS by dialing a 5

feature code or an appropriate directory number. 6
Manual Invocation
7
Not subscribed. 8
9
Permanent. LBIS is active while authorized.
10
Activation Demand. The subscriber is authorized to control the activation and 11
de-activation of LBIS. 12
13
Table 2 LBIS Subscription Options 14
15
16
De-Authorization
17
18
LBIS may be withdrawn at the subscriber’s request or for administrative reasons.
19
20
Registration 21
22
LBIS has no registration. 23
24
25
De-Registration
26
27
LBIS has no de-registration.
28
29
Activation 30
31
LBIS may be activated upon authorization. 32
33
34
LBIS may be activated by a Demand Activation authorized subscriber specifying a LBIS 35
activation feature code, as in: 36
37
* FC + SEND . 38
39
40
41
treatment.
42
43
De-Activation 44
45
LBIS shall be de-activated upon de-authorization. 46
47
48
LBIS Demand De-Activation
49
LBIS may be de-activated by a Demand Activation authorized subscriber specifying a LBIS 50
de-activation feature code, as in: 51
52
* FC0 + SEND . 53
54
55
If the de-activation is accepted, the system shall indicate success with feature confirmation 56
treatment. 57
58
59
60
Feature Descriptions 18 Location-Based Information Service (LBIS)

X.S0009
1 Invocation
2
3 LBIS may be invoked upon authorization.
4
5
6 Manual Invocation
7 LBIS may be invoked by a Manual Invocation authorized subscriber originating a call to a
8 directory number for which LBIS is active, as in:
9
10
* FC + SEND .
11
12
13 Normal Operation with Successful Outcome
14
15 This section describes a normal sequence of procedures for LBIS operation.
16
17
Manual Invocation
18
19 • Subscriber invokes the information service by entering a feature code or originating a
20 call to a directory number associated with that service;
21
22 • The subscriber is connected to the service provider;
23
24
• The service provider tailors the information content as per the current MS location and
25
provides the information to the subscriber in the context of the call.
26
27 Automatic Invocation
28
29
• Network automatically connects the subscriber to the service provider when subscriber
30
powers on the mobile station;
31
• The service provider tailors the information content as per the current MS location and
32
33
provides the information to the subscriber;
34
• The information is provided to the subscriber.
35
36
37 Data Record
38
39 The following data shall be recorded:
40
41 1. LBIS invocation activities and events.
42
43
2. LBIS usage duration and times.
44
3. Application or Service Identifier.
45
46 See DMH for the specific information to be included for each element.
47
48
49
50
6.2 Exception Procedures or Unsuccessful Outcome
51
52
Registration
53
54
None identified.
55
56
57 De-Registration
58
59 None identified.
60

X.S0009
Activation 1
2
None identified. 3
4
5
De-Activation 6
7
None identified. 8
9
10
Invocation
11
12
If the subscriber cannot be connected to the LBIS service provider or the location information
13
is not available to the LBIS service provider, the appropriate treatment, such as the Special
14
Information Tone for intercept, should be provided.
15
16
Exceptions While Roaming 17
18
None identified. 19
20
21
Exceptions During Intersystem Handoff 22
23
None identified. 24
25
26
6.3 Alternative Procedures 27
28
None identified. 29
30
31
6.4 Interactions with Other Wireless Services 32

33
34
No interactions have been identified with the following exceptions:
35
36
Emergency Services (9-1-1) 37
38
Emergency Services is invoked before LBIS. 39
40
41
Flexible Alerting (FA)
42
43
For further study.
44
45
Location Based Charging (LBC) 46
47
LBC is invoked before LBIS. 48
49
50
51
52
LIR is invoked before LBIS.
53
54
Mobile Access Hunting (MAH) 55
56
For further study. 57
58
59
60
Feature Descriptions 20 Location-Based Information Service (LBIS)

X.S0009

2
3 OTA is invoked before LBIS.
4
5
6 Subscriber PIN Access (SPINA)
7
8 SPINA is invoked before LBIS.
9
10
Subscriber PIN Intercept (SPINI)
11
12
SPINI is invoked before LBIS
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
7 ENHANCED CALL ROUTING (ECR) 1

2
3
Enhanced Call Routing (ECR) allows calls to be routed to the appropriate destination based on 4
the position of the MS. The following are examples of ECR calls: 5
6
• The MS user dials #427 (i.e., #GAS) and the call is routed to the nearest gas station. 7
8
• The MS user’s call is completed via the lowest cost route. 9
10
• The MS user’s call is sent to a toll free 800 number.
11
12
• The MS user’s call is routed to the nearest private network node.
13
14
As an option, the call may be air time free to the caller and the called party may be charged for 15
the air time. 16
17
18
19
20
ECR is applicable to all telecommunications services.
21
22
23
25
26
Authorization 27
28
ECR may be generally available or after pre-arrangement with the service provider. 29
30
De-Authorization 31
32
ECR may be withdrawn at the subscriber’s request or for administrative reasons. 33

34
35
Registration 36
37
ECR has no registration. 38
39
De-Registration 40
41
ECR has no de-registration. 42

43
44
Activation 45
46
ECR has no activation. 47
48
49
De-Activation
50
51
ECR has no de-activation.
52
53
54
55
56
57
58
59
60
Feature Descriptions 22 Enhanced Call Routing (ECR)

X.S0009
1 Invocation
2
3 For initiation of ECR from the mobile station, the user enters the “#” abbreviated dialing code
4
followed by supplementary digits (e.g., any number of digits to be interpreted by the MSC). The
5
following are examples:
6
7
# + XX + SEND .
8
9
Where XX indicates any number of supplementary digits that represent an abbreviated dialing
10
string.
11
12
13
# + DN + SEND .
14
15 Where DN indicates a directory number (NPA-NXX-XXXX).
16
17
18 # + ZZ + DN + SEND .
19
20 Where ZZ indicates supplementary digits followed by a DN (directory number).
21
22
Normal Operation with Successful Outcome
23
24
This section describes a normal sequence of procedures for ECR operation:
25
26
27
1. The MS user dials an abbreviated dialing sequence such as # + XX + SEND .
28
2. The network routes the call to the appropriate geographic destination based on the
29
position of the MS and the dialed digits. For example, if the MS user dials #427
30
(i.e., #GAS), the call will be routed to the nearest gas station. Or, if the MS user dials
31
# + DN, the call will be routed to the nearest network node.
32
33
34 Call Detail Record
35
36 The system should record call detail information for the following:
37
38 • Identity of the calling party.
39
40
• The called number.
41
• MS position.
42
43 • Call duration and times.
44
45 • Identity of the party that should be billed for the ECR call.
46
47 • Special routing details (e.g., virtual private network).
48
49
See DMH for the specific information to be included for each element.
50
51
52 7.2 Exception Procedures or Unsuccessful Outcome
53
54
55 Registration
56
57 None identified.
58
59
60
Enhanced Call Routing (ECR) 23 Feature Descriptions

X.S0009
De-Registration 1
2
None identified. 3
4
5
Activation 6
7
None identified. 8
9
10
De-Activation
11
12
None identified.
13
14
Invocation 15
16
If the MS position is not available at the time of call setup, local exception procedure shall be 17
used. 18
19
20
Exceptions While Roaming
21
22
None identified.
23
24
Exceptions During Intersystem Handoff 25
26
None identified. 27
28
29
7.3 Alternative Procedures 30

31
32
At the option of the serving wireless service provider, originating ECR calls may be billed to
33
the called party.
34
35
36
7.4 Interactions With Other Wireless Services 37
38
No interactions have been identified with the following exceptions: 39
40
41
Emergency Services (9-1-1)
42
43
Emergency Services is invoked before ECR.
44
45
Location Based Charging (LBC) 46
47
LBC is invoked before ECR. 48
49
50
51
52
LIR is invoked before ECR.
53
54
Mobile Access Hunting (MAH) 55
56
For further study. 57
58
59
60
Feature Descriptions 24 Enhanced Call Routing (ECR)

X.S0009

2
3 OTA is invoked before ECR.
4
5
6 Subscriber PIN Access (SPINA)
7
8 SPINA is invoked before ECR.
9
10
Subscriber PIN Intercept (SPINI)
11
12
SPINI is invoked before ECR.
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Enhanced Call Routing (ECR) 25 Feature Descriptions

X.S0009
TIA/EIA-41.1-D MODIFICATIONS 1
2
3
This section provides new functional overview information for Wireless Intelligent Network 4
Capabilities for Location Based Services according to the structure of TIA/EIA-41-D Chapter 1. 5
6
7
4 SYMBOLS AND ABBREVIATIONS 8

9
(See TIA/EIA-41.1-D, page 1-14) 10

11
REGREPORT RegistrationReport parameter 12
STATNOTREQ StatusNotificationRequest INVOKE 13
14
statnotreq StatusNotificationRequest RETURN RESULT
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41.1-D Modifications 26 Symbols and Abbreviations

X.S0009
1
2 TIA/EIA-41.3-D MODIFICATIONS
3
4 This section provides the additions and modifications to TIA/EIA-41-D Chapter 3 automatic
5 roaming information flows for Wireless Intelligent Network Capabilities for Location Based
6 Services.
7
8
9
8.1 Fleet and Asset Management (FAM)
10
11
12 8.1.1 FAM for MS in Home System
13
14
15
8.1.1.1 FAM for MS Powers on in Home System
16
This scenario illustrates the successful invocation of FAM when an MS powers on and registers
17
18
in the home system.
19
20
Home System
21
22 MS MSC HLR PDE MPC SCP
23
24
MS powers on
25 a
26
REGNOT [MSCID, MSID, ESN, MPCAddressInfo]
27
b
28
RNT
29 regnot [Profile]
c
30
31 REGNOT [MSCID, MSID, ESN, MPCAddressInfo]
32
d
RNT
33 regnot [ ]
34 e
35 ISPOSREQ [MIN, IMSI, MPCAP, PQOS, POSREQTYPE, MSCID, LCSCID]
36 f
37
38 MPC-MSC-PDE Communications to Determine MS Geoposition IPRT g
39
40 isposreq [POSINFO, POSRSULT, LCSBILLID]
h
41
42
Figure 1 FAM: MS Powers on in Home System
43
44
a. An MS with FAM service powers on in the subscriber’s home system.
45
46
b. The MSC sends a REGNOT to the HLR.
47
48 c. The HLR determines that authorization can be granted to the MS. It returns the requested
49 information to the MSC in the regnot.
50
51 d. The HLR has Registration Reporting active for the MS. Upon detecting the MS power-on
52 registration, the HLR determines that the change in MS registration status shall be reported
53 to the SCP. The HLR relays the REGNOT received at Step-b to the SCP and includes the
54
applicable parameters received from the VLR.
55
56
Parameters Usage Type
57
58 MSCID Serving MSC MSCID. R
59
60
Fleet and Asset Management (FAM) 27 TIA/EIA-41.3-D Modifications

X.S0009
1
Parameters Usage Type 2
3
MSID Target MS MSID. R
4
ESN Target MS ESN. R 5

6
MPCAddressInfo: Serving MPC address information. Include if an MPC is R 7
associated with the Serving MSC. 8
9
[MPCADDR] Include when there is a single form of network address O
10
for the Serving MPC.
11
[MPCADLIST] Include when there is more than one form of network O 12
address for the Serving MPC. 13
14
e. The SCP sends a regnot to the HLR. 15
16
f. The SCP determines that the MS is authorized for FAM service and the MS position is 17
required. The SCP examines the subscriber’s LIR information and verifies that the MS 18
position can be obtained. The SCP sends an ISPOSREQ to the Serving MPC. 19
20
22
MIN Target MS MIN. Include if available. O 23
24
IMSI Target MS IMSI. Include if available. O
25
MPCAP MS positioning capability. R 26

27
PQOS Requested position quality of service. R 28
29
POSREQTYPE Type of position information requested. R
30
31
MSCID Serving MSC MSCID. R
32
LCSCID Requesting LCS Client ID. R 33
34
The POSREQTYPE parameter is set to indicate Return the updated position. 35

36
g. The Serving MPC verifies that the request for the Target MS position has been received 37
from an authorized entity (e.g., SCP). To satisfy the requested PQOS, the Serving MPC 38
determines that the current position of the Target MS must be obtained. 39

40
The Serving MPC obtains the information on the current radio environment of the MS, selects 41
a PDE and directs the PDE to obtain the Target MS geoposition. The PDE determines the 42
Target MS position (see TIA-881). 43

44
h. The MPC returns the geographic position of the MS to the SCP in the isposreq. 45
46
Steps f-h can be repeated periodically to obtain updated MS position information. 47
48
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41.3-D Modifications 28 Fleet and Asset Management (FAM)

X.S0009
1 8.1.1.2 FAM for MS Power Down

2
3 This scenario illustrates the successful invocation of FAM when an MS powers down.
4
5 Home System
6
7
MS MSC HLR PDE MPC SCP
8
9
10 MS power down
11
a
12
MSINACT [MSID, ESN, DEREG]
13 b
14 MSIT
msinact [ ]
15 c
16
17
d
18
MSIT
19 msinact [ ]
e
20
21 Figure 2 FAM for MS Power Down
22
23
a. The MS powers down. The Serving MSC determines that deregistration of the MS is
24
required.
25
26
b. The Serving MSC sends an MSINACT to the HLR and includes the DEREG parameter. The
27
MSC may choose to remove all record of the MS from its memory.
28
29 c. The HLR de-registers the MS and sends an empty msinact to the serving MSC.
30
31 d. The HLR has Registration Reporting active for the MS. Upon the MS deregistration, the
32 HLR determines that a change in the MS registration status shall be reported to the SCP.
33 The HLR relays the MSINACT received at Step-b to the SCP and includes the parameters
34
received from the VLR.
35
36 e. The SCP returns an msinact to the HLR.
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
8.1.2 FAM Tracking of Target MS 1

2
This scenario illustrates tracking of a Target MS. The MS may be idle. The MS is de-registered 3
4
by the serving system (e.g., MS power down) while the Target MS is being tracked. The FAM
5
SLPI determines that the MS is unavailable, and tracking is suspended. Registration reporting
6
is not in use for this scenario.
7
8
Serving
9
10
SCP HLR VLR MSC PDE MPC 11
12
13
LPREQ [MSCID, MDN]
14
a
15
LPRT lpreq [MIN, IMSI, ESN, MSCID, MPCAddressInfo, MPCAP] 16
b 17
ISPOSREQ [MIN, IMSI, PQOS, POSREQTYPE, MPCAP, MSCID, LCSCID] 18

c 19
20
MPC-MSC-PDE Communications
ISPRT d 21
to Determine MS Geoposition
22
isposreq [POSINFO, POSRSULT, LCSBILLID]
e 23
24
25
f
27
MPC-MSC-PDE Communications 28
ISPRT g
to Determine MS Geoposition 29
isposreq [POSINFO, POSRSULT, LCSBILLID] 30

h 31
32
33
i 34
35
msinact [ ] MSIT
j 36
37
MSINACT [MSID, ESN, DEREG] 38
k
39
msinact [ ] MSIT 40
l 41
42

m 44
45
ISPRT n 46
47
isposreq [POSRSULT, LCSBILLID]
o 48
49
LPREQ [MSCID, MDN]
50
p
51
LPRT lpreq [ACCDEN]
52
q 53
54
Figure 3 FAM Tracking of Target MS
55
56
a. A FAM SLPI determines that tracking of a FAM member is requested. The SCP examines 57
the subscriber’s LIR information and verifies that the FAM member’s position can be 58
obtained. The SCP sends an LPREQ to the HLR associated with the FAM member. 59
60

X.S0009
1
2 Parameters Usage Type
3
MSCID SCP MSCID. R
4
5 MDN MS MDN. R
6
7 b. The MS is registered in a serving system. The HLR returns an lpreq to the SCP. The
8 MPCAP parameter is set to indicate the MS’s positioning capability.
9
10 c. The SCP sends an ISPOSREQ to the Serving MPC.
11
13
14 MIN Target MS MIN. Include if available. O
15
16
17
PQOS Requested position quality of service. R
18
19 POSREQTYPE Type of position information requested. R
20
21 MPCAP MS positioning capability. R
22
23
24
LCSCID Requesting LCS Client ID. R
25
26
The POSREQTYPE parameter is set to indicate Return the updated position.
27
28 d. The Serving MPC verifies that the request for the Target MS position has been received
29
from an authorized entity (e.g., SCP). To satisfy the requested PQOS, the Serving MPC
30
determines that the current position of the Target MS must be obtained.
31
32 The Serving MPC obtains the information on the current radio environment of the MS, selects
33
a PDE and directs the PDE to obtain the Target MS geoposition. The PDE determines the
34
Target MS position (see TIA-881).
35
36 e. The MPC returns the geographic position of the MS to the SCP in the isposreq.
37
38 f. The FAM SLPI determines that the updated position of the FAM member is required. The
39 SCP sends an ISPOSREQ to the Serving MPC. Parameters are as in Step-c.
40
41 g. The Serving MPC verifies that the request for the Target MS position has been received
42 from an authorized entity (e.g., SCP). To satisfy the requested PQOS, the Serving MPC
43 determines that the current position of the Target MS must be obtained.
44
46 a PDE and directs the PDE to obtain the Target MS geoposition. The PDE determines the
47 Target MS position (see TIA-881).
48
49 h. The MPC returns the geographic position of the MS to the SCP in the isposreq.
50
51 Steps f-h can be repeated to obtain updated geoposition information.
52
53
i. The Serving MSC determines that de-registration of a served MS is required (e.g., MS
54
power down). The Serving MSC sends an MSINACT to the VLR and includes the DEREG
55 parameter. At this point, the MSC removes all record of the MS from its memory.
56
57
j. The Serving VLR sends an empty msinact to the Serving MSC.
58
59
60

X.S0009
k. The Serving VLR determines that deregistration of an MS is required based either on the 1
2
receipt of an MSINACT from the Serving MSC or on internal algorithms. It sends an
3
MSINACT, including a DeregistrationType parameter, to the HLR. The VLR removes all
4
record of the MS from its memory.
5
6
l. The HLR sends an empty msinact to the Serving VLR and removes its pointer to the
7
VLR.
8
In this scenario, Registration Reporting is not active for the MS. The HLR does not relay the 9
10
MSINACT received at Step-k to the SCP.
11
m. The FAM SLPI determines that the updated position of the FAM member is required. The 12
SCP sends an ISPOSREQ to the Serving MPC. Parameters are as in Step-c. 13

14
n. The Serving MPC verifies that the request for the Target MS position has been received 15

18
a PDE and directs the PDE to obtain the Target MS geoposition. The MS is not available at 20
this time. 21
22
o. The MPC sends an isposreq to the SCP. The POSRSULT parameter is set to indicate 23
MSID is not known. 24

25
p. The SCP sends an LPREQ to the HLR associated with the FAM member. 26
27

29
MSCID SCP MSCID. R 30
31
MDN MS MDN. R
32
33
q. The Target MS is not registered in a serving system. The HLR sends an lpreq to the SCP 34
and includes the ACCDEN parameter set to indicate Inactive. 35
36
The FAM SLPI suspends tracking of the FAM member. 37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
1
8.1.3 Single Introducing Star Invocation of FAM Tracking
2
3 This scenario illustrates a FAM Supervisor invoking FAM tracking of a Target MS (FAM
4
Member) by entering a single introducing star invocation code. The Target MS may be idle. The
5
FAM SLPI returns the Target MS information to the FAM Supervisor after the invocation. In
6
this scenario, the Target MS and FAM Supervisor are served by different MSCs.
7
8
9
Supervisor Serving Member
10
11 MS MSC SCP HLR MPC PDE MSC MS
12
13 *FC + FAM member identifier
14 a
15
ORREQ [MSCID, MSID, BILLID, DGTSDIAL, TRIGTYPE]
16 b
17
18 LPREQ [MSCID, MDN]
c
19
LPRT
20 lpreq [MIN, IMSI, ESN, MSCID, MPCAddressInfo, MPCAP]
21
d
22 ISPOSREQ [MIN, IMSI, PQOS, POSREQTYPE, MSCID, MPCAP, LCSCID]
23 e
24 ORT
25
ISPRT MPC-MSC-PDE Communications f
26 to Determine MS Geoposition
27
28
g
29
30 orreq [DMH_SVCID, ANNLIST, DISPTEXT, ACTCODE]
h
31
32 announcement with display
33
i
34
Figure 4 Single Introducing Star Invocation of FAM Tracking
35
36
37
a. The FAM Supervisor enters a single introducing star invocation code and the FAM member
38
identifier to obtain the position of the FAM member.
39
b. The MSC serving the FAM Supervisor detects a subscriber-based dialed digits trigger and
40
41
sends an ORREQ to the address of the network entity (SCP) associated with the trigger type.
42
c. The FAM SLPI validates the identity of the FAM supervisor. The FAM SLPI examines the
43
Target MS’s LIR information and verifies that the FAM member’s position can be obtained.
44
45
If the FAM SLPI does not already have the Serving MPC address information and the Serving
46
MSC MSCID for the Target MS, the SCP sends an LPREQ to the HLR associated with the
47
Target MS. The LPREQ requests the network address of the MPC that is associated with the
48
49
MSC in which the Target MS is registered.
50
51
52
MSCID SCP MSCID. R
53
54 MDN MS MDN. R
55
56
d. The Target MS is registered in a serving system. The HLR returns an lpreq to the SCP.
57
The MPCAP parameter is set to indicate the Target MS’s positioning capability.
58
59
60

X.S0009
e. The SCP sends an ISPOSREQ to the Serving MPC. 1

2
3
4

6
IMSI Target MS IMSI. Include if available. O 7
8
9
10
11
13
MSCID Serving MSC MSCID. R 14
15
16
17
The POSREQTYPE parameter is set to indicate Return the updated position. 18
19
f. The Serving MPC verifies that the request for the Target MS position has been received
20
21
23
The Serving MPC obtains the information on the current radio environment of the MS, selects
24
25
27
g. The MPC returns the geographic position of the MS to the SCP in the isposreq.
28
h. The FAM SLPI determines the appropriate feature treatment based on the received 29
30
information. In this scenario, the FAM SLPI determines that the position information shall
31
be displayed and an announcement provided to alert the FAM Supervisor’s MS that a
32
message has arrived. The SCP sends an orreq to the MSC serving the FAM Supervisor.
33
34
i. The Serving MSC sends a message to display to the FAM Supervisor’s MS along with an
35
optional tone or announcement to alert the MS that a message has arrived.
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
1
8.1.4 Feature Code Invocation of FAM Tracking
2
3 This scenario illustrates a FAM Supervisor invoking FAM tracking of a Target MS (FAM
4
Member) by entering a feature code. The Target MS may be idle. The FAM SLPI returns the
5
Target MS information to the FAM Supervisor after the invocation. In this scenario, the Target
6
MS and FAM Supervisor are served by different MSCs. The Target MS and FAM Supervisor
7
8
are associated with the same HLR.
9
10
Supervisor Serving Member
11
12 MS MSC SCP HLR MPC PDE MSC MS
13
14
*FC + FAM member identifier
15 a
16
FEATREQ [MSCID, MSID, BILLID, DGTSDIAL]
17
b
18
19 FEATREQ [MSCID, MSID, BILLID, DGTSDIAL]
c
20
22
d
23 LPRT
lpreq [MIN, IMSI, ESN, MSCID, MPCAddressInfo, MPCAP]
24 e
26 f
27
FRRT FRRT
28
ISPRT MPC-MSC-PDE Communications g
29
30
h
32
33 featreq [FEATRES, DMH_SVCID, ANNLIST, DISPTEXT, ACTCODE]
34
i
35 featreq [FEATRES, DMH_SVCID, ANNLIST, DISPTEXT, ACTCODE]
36 j
37
announcement with display
38 k
39
40 Figure 5 Feature Code Invocation of FAM Tracking
41
42 a. The FAM Supervisor enters a feature code and the FAM member identifier to obtain the
43 position of the FAM member.
44
45 b. The MSC serving the FAM Supervisor encounters the Home_System_Feature_Code trigger
46 and sends a FEATREQ to the calling MS’s HLR including the digits dialed.
47
48 c. The HLR determines that the feature code shall be handled by another network entity. The
49 HLR forwards the FEATREQ with the received parameters to the SCP.
50
51 d. The FAM SLPI examines the Target MS’s LIR information and verifies that the FAM
52 member’s position can be obtained. If the FAM SLPI does not already have the Serving
53 MPC address information and the Serving MSC MSCID for the Target MS, the SCP sends
54 an LPREQ to the HLR associated with the Target MS. The LPREQ requests the network
55 address of the MPC that is associated with the MSC in which the Target MS is registered.
56
57
58
59
60

X.S0009
1
3
MSCID SCP MSCID. R
4
MDN MS MDN. R 5
6
e. The Target MS is registered in a serving system. The HLR returns an lpreq to the SCP. 7
The MPCAP parameter is set to indicate the Target MS’s positioning capability. 8
9
f. The SCP sends an ISPOSREQ to the Serving MPC. 10
11

13
15
17
18
POSREQTYPE Type of position information requested. R 19

20
22
23
24
25
26
27
g. The Serving MPC verifies that the request for the Target MS position has been received 28
29
30
31
33
34
35
h. The MPC returns the geographic position of the MS to the SCP in the isposreq. 36
37
i. The FAM SLPI determines the appropriate feature treatment based on the received 38
information. In this scenario, the FAM SLPI determines that the position information shall 39
be displayed and an announcement provided to alert the FAM Supervisor’s MS that a 40

41
message has arrived. The SCP sends a featreq to the HLR with the FEATRES,
42
DISPTEXT, ANNLIST and ACTCODE parameters set appropriately.
43
j. The HLR forwards the featreq and all received parameters to the MSC serving the FAM 44
45
Supervisor.
46
k. The Serving MSC sends a message to display to the FAM Supervisor’s MS along with an 47
tone or announcement to alert the MS that a message has arrived. 48

49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
1
2
8.2 Location Based Charging (LBC)
3
4
8.2.1 LBC Call Origination
5
6
This scenario illustrates the successful invocation of LBC for call origination.
7
8
Serving
9
10
11 MS MSC PDE MPC SCP
12
13 MS origination
14 a
15
ORREQ [MSCID, MSID, BILLID, MPCAP, TRIGTYPE, MPCAddressInfo]
16 b
17
ISPOSREQ [MIN, IMSI, PQOS, POSREQTYPE, MPCAP, MSCID, LCSCID]
18 c
19 ORT
20
MPC-MSC-PDE Communications to Determine MS Geoposition IPRT d
21
e
23
24 orreq [GEOPOS, DMH_SVCID, CHARGEINFO]
25
f
26 call set up
27 g
28
answer
29 h
30
OANSWER [MSCID, MSID, BILLID, TRIGTYPE]
31 i
32
33
34
ISPOSREQ [MIN, IMSI, PQOS, POSREQTYPE, MSCID, MPCAP, LCSCID]
j
35
36
37
MPC-MSC-PDE Communications to Determine MS Geoposition IPRT k
38
39 l
40
CCDIR [MSID, BILLID, GEOPOS, CHARGEINFO, ANNLIST]
41 m
42
zone change notification
43 CCDT n
44
45 ccdir [ ]
o
46
47
48
MS disconnect
49 p
50
51 ODISCONNECT [MSCID, MSID, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]
q
52
ODT
53 odisconnect [DMH_SVCID]
54
r
55 call release
56 s
57
58
Figure 6 LBC Call Origination
59
60
Location Based Charging (LBC) 37 TIA/EIA-41.3-D Modifications

X.S0009
a. A subscriber with LBC service originates a call. 1

2
b. The MSC detects the All_Calls trigger and sends an ORREQ to the SCP. The ORREQ 3
includes the MPCAddressInfo set to indicate the address of the Serving MPC. The MPCAP 4
parameter is set to indicate the positioning capability of the MS. 5

6
c. The SCP checks the subscriber’s LIR information. If the MS position can be determined, the 7
SCP sends an ISPOSREQ to the Serving MPC. The POSREQTYPE parameter is set to 8
indicate Return the updated position. 9

10
d. The Serving MPC verifies that the request for the Target MS position has been received 11

14
Target MS position (see TIA-881) 17

18
e. The MPC returns the geographic position of the MS to the SCP in the isposreq. 19
20
f. The SCP sends an orreq to the Serving MSC. The DMH_SVCID parameter is set to 21
indicate that LBC was invoked. The CHARGEINFO parameter is set to indicate the rate 22
plan that shall be applied. The GEOPOS parameter is set to the initial MS geoposition for 23
recording purposes. 24
25
Note: If the Target MS position could not be determined (i.e., no POSINFO parameter 26
received at Step-e), the LBC call may proceed, but the LBC zone or location dependent rate 27
will not be applied for the remainder of the call and the subscriber will not receive any zone 28
change notification. In this case, the LBC SLPI will not include the CHARGEINFO and 29
30
GEOPOS parameters in the orreq sent to the Serving MSC.
31
g. The Serving MSC sets up the call. 32

33
h. The call is answered by the called party. 34
35
i. The Serving MSC detects the O_Answer trigger and sends an OANSWER to the SCP. 36
37
j. The SCP determines that the current MS geoposition is required. The SCP sends an 38
ISPOSREQ to the Serving MPC. The POSREQTYPE parameter is set to indicate Return the 39
updated position. 40
41
k. The Serving MPC verifies that the request for the Target MS position has been received 42
45
49
l. The MPC returns the geographic position of the MS to the SCP in the isposreq. 50
51
m. If the MS has changed charging zones, the SCP sends a CCDIR to the Serving MSC with the
52
CHARGEINFO parameter set to indicate the new charge information for the call. The
53
ANNLIST parameter indicates that a charging zone change notification be played to the MS. 54
55
n. The Serving MSC applies the charging zone change notification to the MS. The charging
56
zone change notification is only applied to the calling MS (i.e., the called party does not hear
57
the warning). 58
59
60
TIA/EIA-41.3-D Modifications 38 Location Based Charging (LBC)

X.S0009
1 o. The Serving MSC sends a ccdir to the SCP indicating the requested actions were
2
completed.
3
4 Steps j-o can be repeated periodically to detect MS charging zone changes.
5
6 p. The MS disconnects.
7
8 q. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT to the
9 SCP.
10
11
r. The SCP responds with an odisconnect to the Serving MSC.
12
s. The Serving MSC releases the call.
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
8.2.2 LBC Call Delivery: Local Termination at Originating MSC 1

2
This scenario illustrates LBC call delivery with local termination at the Originating MSC. 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
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
1
Serving
2
3
4 MSC PDE MPC HLR SCP
5
6 call origination
7 a
8
LOCREQ [MSCID, BILLID, DGTSDIAL, TRANSCAP, WINCAP, TRIGTYPE]
9 b
10 LRT
11
locreq [MIN, IMSI, MSCID, TRIGADDRLIST, TERMLIST, REDIND]
c
12
13 ANLYZD [MSCID, BILLID, MSID, RoutingInfo, REDIND, TRIGTYPE, EXTMSCID]
d
14
16
e
17 LPRT
lpreq [MIN, IMSI, ESN, MSCID, MPCAddressInfo, MPCAP]
18 f
19 ISPOSREQ [LCSCID, MIN, IMSI, PQOS, POSREQTYPE, MSCID, MPCAP]
20 ANZT g
21
22 MPC-MSC-PDE Communications to Determine MS Geoposition IPRT h
23
i
25
26 anlyzd [GEOPOS, DMH_SVCID, CHARGEINFO]
27
j
28
29 MS answer k
30
TANSWER [MSCID, MSID, BILLID, TRIGTYPE]
31 l
32
33
ISPOSREQ [LCSCID, MIN, IMSI, PQOS, POSREQTYPE, MSCID, MPCAP]
34 m
35
36
MPC-MSC-PDE Communications to Determine MS Geoposition IPRT
37 n
39
o
40 CCDIR [MSID, BILLID, GEOPOS, CHARGEINFO, ANNLIST]
41 p
42
43 zone change notification CCDT q
44
ccdir [ ]
45 r
46
47
48
MS disconnect s
49
50 TDISCONNECT [MSID, BILLID, TRIGTYPE]
51
t
TDT
52 tdisconnect [DMH_SVCID]
53 u
54
call release
55 v
56
57 Figure 7 LBC Call Delivery: Local Termination at Originating MSC
58
59
60

X.S0009
a. A call origination and the dialed MS address digits (i.e., directory number) are received by 1
2
the Originating MSC.
3
b. The Originating MSC detects the Mobile_Termination trigger and sends a LOCREQ to the 4
HLR associated with the MS; this association is made through the dialed MS address digits 5
6
(which may not be the MSID). The TRANSCAP parameter is set to indicate the MSC can
7
process the TRIGADDRLIST parameter. The WINCAP parameter indicates the triggers
8
supported by the MSC. The TRIGTYPE parameter is set to indicate the Mobile_Termination
9
trigger was encountered. 10
11
c. The HLR sends the locreq to the Originating MSC with the TRIGADDRLIST parameter
12
set to indicate the Called_Routing_Address_Available, T_Answer and T_Disconnect triggers
13
shall be armed. 14
15
17
MIN Called MS MIN. R
18
IMSI Called MS IMSI. Include if available. O 19

20
MSCID Serving MSC MSCID R 21
22
TRIGADDRLIST WIN Triggers to arm for this call leg. R 23
24
TERMLIST Call termination information. R
25
REDIND DMH_RedirectionIndicator. Reason for extending the R 26

incoming call. 27
28
d. The Originating MSC prepares to terminate the call. The MSC detects the 29
Called_Routing_Address_Available trigger and sends an ANLYZD to the SCP associated 30
with this trigger. The REDIND parameter is set to indicate CD Local. 31

32
33
34
MSCID Originating MSC MSCID. R 35

36
BILLID BillingID. Used to relate queries for this call. R 37
38
MSID Called MS MSID. R
39
40
RoutingInfo Call routing information. R
41
incoming call. 43
44
TRIGTYPE Indicates the trigger encountered. R
45
46
EXTMSCID Serving MSC MSCID. R
47
48
e. The LBC SLPI examines the Target MS’s LIR information and verifies that the MS’s
49
position can be obtained. If the LBC SLPI does not already have the Serving MPC address
50
information and the Serving MSC MSCID for the Target MS, the SCP sends an LPREQ to 51
the HLR associated with the Target MS. The LPREQ requests the network address of the 52
MPC that is associated with the MSC in which the Target MS is registered. 53
54
56
58
MDN MS MDN. R
59
60

X.S0009
1 f. The Target MS is registered in a serving system. The HLR returns an lpreq to the SCP.
2
3
4 g. The SCP sends an ISPOSREQ to the Serving MPC. The POSREQTYPE parameter is set to
5 indicate Report the updated position
6
7 h. The Serving MPC verifies that the request for the Target MS position has been received
10
14
15 i. The MPC returns the geographic position of the MS to the SCP in the isposreq.
16
17 j. The SCP sends an anlyzd to the Originating MSC. The DMH_SVCID parameter is set to
18 indicate that LBC was invoked. The CHARGEINFO parameter is set to indicate the rate
19 plan that shall be applied. The GEOPOS parameter is set to the initial MS geoposition for
20 recording purposes.
21
22 Note: If the Target MS position could not be determined (i.e., no POSINFO parameter
23 received at Step-i), the LBC call may proceed, but the LBC zone or location dependent rate
24 will not be applied for the remainder of the call and the subscriber will not receive any zone
25 change notification. In this case, the LBC SLPI will not include the CHARGEINFO and
26
GEOPOS parameters in the anlyzd sent to the Originating MSC.
27
28 k. The Originating MSC pages and alerts the MS. The MS answers.
29
30 l. The MSC detects the T_Answer trigger. The MSC sends a TANSWER to the SCP associated
31 with this trigger.
32
33 m. The SCP determines that the current MS geoposition is required. The SCP sends an
34 ISPOSREQ to the Serving MPC. The POSREQTYPE parameter is set to indicate Return the
35 updated position.
36
37 n. The Serving MPC verifies that the request for the Target MS position has been received
40
44
45 o. The MPC returns the geographic position of the MS to the SCP in the isposreq.
46
47
p. If the MS has changed charging zones, the SCP sends a CCDIR to the Serving MSC with the
48 CHARGEINFO parameter set to indicate the new charge information for the call. The
49 ANNLIST parameter indicates that a charging zone change notification be played to the MS.
50
51
q. The Serving MSC applies the charging zone change notification to the MS. The charging
52 zone change notification is only applied to the called MS (i.e., the calling party does not hear
53 the warning).
54
55
r. The Serving MSC sends a ccdir to the SCP indicating the requested actions were
56 completed.
57
58
Steps k-p can be repeated periodically to detect MS charging zone changes.
59
60

X.S0009
s. The MS disconnects. 1
2
t. The Serving MSC detects the T_Disconnect trigger and sends a TDISCONNECT to the SCP. 3
4
u. The SCP responds with a tdisconnect to the Serving MSC. 5
6
v. The Serving MSC releases the call. 7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
1
8.2.3 LBC Call Termination in Visited System
2
3 This scenario illustrates LBC call termination in the visited system.
4
5 Home Serving
6
7
MSC HLR SCP VLR MSC PDE MPC
8
9
10 call origination
11 a
12
LOCREQ [MSCID, BILLID, DGTSDIAL, TRANSCAP, WINCAP, TRIGTYPE]
13
b
14
15 ROUTREQ [MSID, BILLID]
c
16
17 ROUTREQ [MSID, BILLID]
18
d
LRT RRT RRT
19 routreq [TLDN]
20 e
21
routreq [TLDN]
22 f
23
24
locreq [MSCID, MIN, IMSI, TRIGADDRLIST, TERMLIST, REDIND]
g
25
ANLYZD [MSCID, BILLID, MSID, RoutingInfo, REDIND, TRIGTYPE, EXTMSCID]
26
h
27
29
i
30 LPRT
31
lpreq [MPCAddressInfo, MPCAP]
j
32
k
34
35 ANZT
36 ISPRT l
37
m
39
40 anlyzd [GEOPOS, DMH_SVCID, CHARGEINFO]
41
n
42 call setup
43 o
44
45 MS answer p
46
TANSWER [MSCID, MSID, BILLID, TRIGTYPE]
47 q
48
49 Figure 8 LBC Call Termination in Visited System (1 of 2)
50
51 a. A call origination and the dialed MS address digits (i.e., directory number) are received by
52 the Originating MSC.
53
54 b. The Originating MSC detects the Mobile_Termination trigger and sends a LOCREQ to the
55 HLR associated with the MS; this association is made through the dialed MS address digits
56 (which may not be the MSID). The TRANSCAP parameter is set to indicate the MSC can
57
process the TRIGADDRLIST parameter. The WINCAP parameter indicates the triggers
58
59
60

X.S0009
supported by the MSC. The TRIGTYPE parameter is set to indicate the Mobile_Termination 1
2
trigger was encountered.
3
c. The HLR determines call processing shall continue and sends a ROUTREQ to the VLR. 4
5
d. The VLR forwards the ROUTREQ to the Serving MSC. 6
7
e. The Serving MSC allocates a TLDN and returns it to the VLR in the routreq. 8
9
f. The VLR forwards the routreq to the HLR. 10
11
g. The HLR sends the locreq to the Originating MSC with instructions to set up the call to
12
the subscriber.
13
14
16
MSCID Serving MSC MSCID R
17
MIN Called MS MIN. R 18

19
IMSI Called MS IMSI. Include if available. O 20
21
TRIGADDRLIST WIN Triggers to arm for this call leg. R
22
23
TERMLIST Call termination information. R
24
incoming call. 26
27
The TRIGADDRLIST parameter is set to indicate the Called_Routing_Address_Available, 28
T_Answer and T_Disconnect triggers shall be armed 29
30
h. The Originating MSC prepares to route the call. The MSC detects the 31
Called_Routing_Address_Available trigger and sends an ANYLZD to the SCP associated 32
with this trigger. 33
34

36
MSCID Originating MSC MSCID. R 37
38
BILLID BillingID. Used to relate queries for this call. R 39
40
MSID Called MS MSID. R
41
RoutingInfo Call routing information. R 42

43
incoming call. 45
46
TRIGTYPE Indicates the trigger encountered. R
47
EXTMSCID Serving MSC MSCID. R 48

49
i. The LBC SLPI examines the Target MS’s LIR information and verifies that the MS’s 50
51
position can be obtained. If the LBC SLPI does not already have the Serving MPC address
52
information and the Serving MSC MSCID for the Target MS, the SCP sends an LPREQ to
53
the HLR associated with the Target MS. The LPREQ requests the network address of the
54
MPC that is associated with the MSC in which the Target MS is registered. 55
56
58
MSCID SCP MSCID. R
59
60

X.S0009
1
3
MDN MS MDN. R
4
5
j. The Target MS is registered in a serving system. The HLR returns an lpreq to the SCP.
6
7
8
k. The SCP sends an ISPOSREQ to the Serving MPC. The POSREQTYPE parameter is set to
9
indicate Report the updated position
10
11 l. The Serving MPC verifies that the request for the Target MS position has been received
12
13
14
16
17
18
19 m. The MPC returns the geographic position of the MS to the SCP in the isposreq.
20
21 n. The SCP sends an anlyzd to the Originating MSC. The DMH_SVCID parameter is set to
22 indicate that LBC was invoked. The CHARGEINFO parameter is set to indicate the rate
23 plan that shall be applied. The GEOPOS parameter is set to the initial MS geoposition for
24
recording purposes.
25
26 Note: If the Target MS position could not be determined (i.e., no POSINFO parameter
27 received at Step-m), the LBC call may proceed, but the LBC zone or location dependent rate
28
will not be applied for the remainder of the call and the subscriber will not receive any zone
29
change notification. In this case, the LBC SLPI will not include the CHARGEINFO and
30
GEOPOS parameters in the anlyzd sent to the Originating MSC.
31
32
o. The Originating MSC sets up the call to the subscriber.
33
34 p. The MS answers the call.
35
36 q. The MSC detects the T_Answer trigger. The MSC sends a TANSWER to the SCP associated
37 with this trigger.
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
1
Home Serving
2
3
MSC HLR SCP VLR MSC PDE MPC 4
5
6
7
ISPOSREQ [MIN, IMSI, PQOS, POSREQTYPE, MSCID, MPCAP, LCSCID] 8
r 9
10
ISPRT s
13
t 14
15
CCDIR [MSID, BILLID, GEOPOS, CHARGEINFO, ANNLIST]
u 16
17
zone change 18
CCDT v
notification 19
ccdir [ ] 20
w 21
22
23
24
MS disconnect x
25
TDISCONNECT [MSID, BILLID, TRIGTYPE] 26
y 27
tdisconnect [DMH_SVCID] TDT 28

z 29
30
call release
aa 31
32
call release
ab 33
34
Figure 9 LBC Call Termination in Visited System (2 of 2) 35
36
r. The SCP determines that the current MS geoposition is required. The SCP sends an 37
ISPOSREQ to the Serving MPC. The POSREQTYPE parameter is set to indicate Return the 38
updated position. 39
40
s. The Serving MPC verifies that the request for the Target MS position has been received 41

44

48
t. The MPC returns the geographic position of the MS to the SCP in the isposreq. 49
50
u. If the MS has changed charging zones, the SCP sends a CCDIR to the Serving MSC with the 51
CHARGEINFO parameter set to indicate the new charge information for the call. The 52
ANNLIST parameter indicates that a charging zone change notification be played to the MS. 53
The GEOPOS parameter indicates the geographic position of the MS for recording purposes. 54
55
v. The Serving MSC applies the charging zone change notification to the MS. The charging 56
zone change notification is only applied to the called MS (i.e., the calling party does not hear 57
the warning). 58
59
60

X.S0009
1 w. The Serving MSC sends a ccdir to the SCP indicating the requested actions were
2
completed.
3
4 Steps p-u can be repeated periodically to detect MS charging zone changes.
5
6 x. The MS disconnects.
7
8 y. The Serving MSC detects the T_Disconnect trigger and sends a TDISCONNECT to the SCP.
9
10
z. The SCP responds with a tdisconnect to the Serving MSC.
11
aa. The Serving MSC releases the call.
12
13 ab. The Originating MSC releases the call.
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
8.2.4 Successful Position Determination for LBC After Intersystem Handoff 1

2
This scenario illustrates LBC charging and successful determination of a Target MS position 3
4
after an intersystem handoff. The Target MS is on a call for which LBC has been invoked and
5
the MS has been handed off to a new MSC. The updated position of the Target MS can be
6
determined.
7
8
Anchor Serving
9
10
SCP MPC MSC MSC MPC PDE 11
12
13
14
ISPOSREQ [MIN, IMSI, POSREQTYPE, PQOS, MSCID, MPCAP, LCSCID] 15
a
16
ISPOSREQ [MPCID (Home), MIN, IMSI, POSREQTYPE, PQOS, MPCAP, LCSCID, LCSBILLID] 17
b 18
ISPOSREQFWD [MPCID (Home), MIN, IMSI, PQOS, POSREQTYPE, MPCAP, LCSCID, LCSBILLID] 19
c 20
21
ISPOSREQ [MPCID (Home), MIN, IMSI, PQOS, POSREQTYPE, MPCAP,
22
MOBINFO, MSCID, SCELLID, LCSCID, LCSBILLID]
d 23
IPRT 24
IPRT IPRT IPRFT
25
MPC-MSC-PDE Communications e 26
27
f 29
isposreqfwd [POSINFO, POSRSULT, LCSBILLID] 30

g 31
32
h 33
34
i 35
36
Figure 10 Successful Position Determination for LBC After Intersystem Handoff 37
38
a. A call for an LBC subscriber is ongoing. Sometime later during the ongoing call, the SCP 39
requires the updated position of the Target MS. To determine the updated Target MS 40
41
geoposition, the SCP sends an ISPOSREQ to the MPC that is associated with the MSC in
42
which the MS last registered. The ISPOSREQ includes the requested PQOS, the network
43
address of the MSC in which the MS last registered, and the LCS Client ID. The
44
POSREQTYPE parameter indicates that updated MS position is needed. 45
46
48
MIN Target MS MIN. Include if available. O
49

51
POSREQTYPE Type of position information requested. R 52
53
54
55
56
58
LCSCID LCS Client ID. R 59
60

X.S0009
1 b. The Anchor MPC verifies that the request for the Target MS position has been received from
2
an authorized entity (i.e., the SCP). To satisfy the required PQOS, the Anchor MPC
3
determines that the current position of the Target MS must be obtained. The Anchor MPC
4
uses the indicated PQOS priority to select the processing priority for the geoposition request.
5
6
The MPC sends an ISPOSREQ to the Anchor MSC to obtain information on the current
7
radio environment of the Target MS. The POSREQTYPE is set to indicate updated MS
8 position is needed.
9
10
c. The MS is on a call and has been handed off to another MSC. The Anchor MSC sends an
11
ISPOSREQFWD toward the Serving MSC. The POSREQTYPE is set to indicate updated
12 MS position is needed.
13
15
16
MPCID Anchor MPC MPCID. R
17
18
19 IMSI Target MS IMSI. Include if available. O
20
21 POSREQTYPE Type of position information requested. R
22
LCSCID LCS Client ID. R
23
24
MPCAP MS positioning capability. R
25
26 PQOS Requested position quality of service. R
27
28 d. The Serving MSC sends an ISPOSREQ to its associated MPC requesting the indicated MS’s
29 position. The Serving MPC includes the current MS positioning capabilities (MPCAP
30
parameter), the received POSREQTYPE, PQOS and MSCID parameters, and the
31
MOBINFO, SCELLID parameters.
32
33 e. The Serving MPC verifies that the request for the Target MS position has been received
34
from an authorized entity (e.g., SCP). Based on the received PQOS, the Serving MSC
35
selects a PDE and directs the PDE to obtain the Target MS position (see TIA-881).
36
37 f. The Serving MPC returns the Target MS position to the Serving MSC in the isposreq.
38
39 g. The Serving MSC returns the Target MS position to the Anchor MSC in the
40 isposreqfwd.
41
42 h. The Anchor MSC returns the Target MS position to the Anchor MPC in the isposreq.
43
44 i. The Anchor MPC returns the Target MS position to the SCP in the isposreq.
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
8.2.5 Unsuccessful LBC Call Origination: LIR Service Denial 1

2
This scenario illustrates unsuccessful LBC call origination due to service denial based on the 3
4
subscriber’s LIR.
5
Home 6
7
8
MS MSC SCP
9
10
11
MS origination
a 12
13
ORREQ [MSCID, MSID, BILLID, MPCAP, TRIGTYPE, MPCAddressInfo] 14
b
15
ORT
orreq [ACCDEN, ANNLIST] 16
c 17
announcement 18
d 19
20
Figure 11 Unsuccessful LBC Call Origination: LIR Service Denial 21
22
a. A subscriber with LBC service originates a call. 23
24
b. The MSC detects the All_Calls trigger and sends an ORREQ to the SCP. The ORREQ 25
includes the MPCAddressInfo set to indicate the address of the Serving MPC. The MPCAP 26
28
c. The SCP checks the subscriber’s LIR information and determines that the Target MS’s 29
position information is blocked. Based on home service provider policy, the LBC SLPI 30
denies the service requested. The SCP sends an orreq to the MSC. The ACCDEN 31
parameter is set to indicate the denial of the service request. The ANNLIST parameter is set 32
to indicate the announcement to be played to the MS. 33
34
Note: Alternatively, home service provider policy may permit the call to proceed. 35
36
d. The MSC plays an announcement to the MS to indicate the reason the LBC call could not be 37
completed. The MSC releases the MS. 38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
1
2
8.3 Location Based Information Services (LBIS)
3
4
8.3.1 Single_Introducing_Star Invocation of LBIS on SCP
5
6
This scenario illustrates the invocation of a location based information service (LBIS) when the
7
subscriber enters a feature code. The Serving MSC detects the Single_Introducing_Star trigger,
8
9
and the destination for the call is dependent on the MS position.
10
Serving System Serving System
11
12
13 MS MSC SCP MPC PDE
14
15
*FC
16 a
17
ORREQ [MSCID, MSID, DGTSDIAL, SCELLID, MPCAP, MPCAddressInfo, TRIGTYPE]
18 b
19 ORT
20
ISPOSREQ [MSID, POSREQTYPE, PQOS, MSCID, SCELLID, MPCAP, LCSCID]
21
c
22
IPRT
23
24 MPC-MSC-PDE Communications to Determine MS Geoposition d
25
27 e
28
orreq [TERMLIST, DMH_SVCID]
29 f
30
call setup
31 g
32
33 Figure 12 Single_Introducing_Star Invocation of LBIS on SCP
34
35 a. A feature code string is received from a served MS.
36
37 b. The Serving MSC detects the Single_Introducing_Star trigger and sends an ORREQ to the
38 calling party’s SCP. The SCP determines that the MS is authorized for the LBIS service and
39 that the subscriber’s LIR information allows the MS position to be determined.
40
41 c. If the SCP determines that MS position information is needed, the SCP sends an ISPOSREQ
42 to the Serving MPC.
43
47
51
52 e. The serving MPC returns the position information to the SCP in the isposreq.
53
54 f. The SCP determines the destination for the call based on the received position information,
55 and sends an orreq to the Serving MSC.
56
57
g. The MSC sets up the call.
58
59
60
Location Based Information Services (LBIS) 53 TIA/EIA-41.3-D Modifications

X.S0009
8.3.2 Single_introducing_Star Invocation of LBIS on a Service Node 1

2
This scenario illustrates the invocation of a location based information service (LBIS) when the 3
4
subscriber enters a feature code. The Serving MSC detects the Single_Introducing_Star trigger.
5
LBIS is provided by a separate service node. The MS position determines the information
6
delivered by the service node in an IVR interaction.
7
8
9
10
MS MSC SCP SN MPC PDE 11
12
*FC 13
a 14
ORREQ [MSCID, MSID, DGTSDIAL, SCELLID, MPCAP, MPCAddressInfo, TRIGTYPE] 15

b 16
17
SERVREQ [SRVID, MSID, DGTSDIAL, SCELLID, MPCAP, MPCAddressInfo, MSCID (Serving)]
c 18
19
ISPOSREQ [MSID, POSREQTYPE, PQOS, MSCID, SCELLID, MPCAP, LCSCID]
20
d
21
ORT SVRT IPRT
22
MPC-MSC-PDE Communications to Determine MS Geoposition e 23
24
f 26
27
servreq [TERMLIST, DMH_SVCID]
g 28
29
orreq [TERMLIST, DMH_SVCID]
h 30
31
call setup 32
i
33
Figure 13 LBIS Invocation on Service Node from the Single_Introducing_Star Trigger 34

35
36
a. A feature code string is received from a served MS.
37
b. The Serving MSC detects the Single_Introducing_Star trigger and sends an ORREQ to the 38
39
calling party’s SCP.
40
c. The SCP determines that LBIS shall be invoked for the MS at another NE. The SCP sends a 41
SERVREQ to the SN. The SRVID parameter is set to indicate the LBIS to invoke. The SCP 42
43
relays the MSID, DGTSDIAL, SCELLID, MPCAddressInfo and MPCAP parameters
44
received from the Serving MSC. The MSCID parameter is set to the Serving MSC MSCID.
45
The MSID identifies the subscriber.
46
47
d. The SN examines the subscriber’s LIR information and determines the MS position can be
48
determined. The SN sends an ISPOSREQ to the Serving MPC.
49
e. The Serving MPC verifies that the request for the Target MS position has been received 50
51
from an authorized entity (e.g., SN). To satisfy the requested PQOS, the Serving MPC
52
53
55
56
57
f. The Serving MPC returns the position information to the SN. 58

59
60
TIA/EIA-41.3-D Modifications 54 Location Based Information Services (LBIS)

X.S0009
1 g. The SN allocates a TLDN for the specialized LBIS resource based on the received position
2
information, and includes the TERMLIST parameter in the servreq.
3
4 h. The SCP forwards the TERMLIST to the MSC in the orreq.
5
6 i. The MSC sets up the call to the SN. The SN provides the LBIS.
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
8.3.3 Feature Code Invocation of LBIS 1

2
This scenario illustrates the invocation of a location based information service (LBIS) when the 3
4
Home_System_Feature_Code trigger is detected. Based on the MS’s position information,
5
display text and an announcement are sent to the MS.
6
7
Serving System
8
9
MS MSC PDE MPC HLR SCP 10
11
12
*FC
a 13
14
FEATREQ [MSCID, MSID, DGTSDIAL, MPCAP]
b 15
16
FEATREQ [MSCID, MSID, DGTSDIAL, MPCAP] 17
c
18
LPREQ [MSCID, MSID] 19
d
20
FRRT LPRT
lpreq [MDN, ESN, MPCAddressInfo, MSCID, MPCAP] 21
e 22
ISPOSREQ [MSID, POSREQTYPE, PQOS, MSCID, MPCAP, LCSCID] 23

f 24
FRRT 25
MSC-PDE-MPC Communications to Determine MS Geoposition IPRT g 26
27
h 28
29
featreq [FEATRES, DMH_SVCID, DISPTEXT, ANNLIST, ACTCODE] 30
i
31
featreq [FEATRES, DMH_SVCID, DISPTEXT, ANNLIST, ACTCODE] 32
j 33
display text with announcement 34

k 35
36
Figure 14 Feature Code Invocation of LBIS 37
38
a. A feature code string is received from a served MS. 39
40
b. The Serving MSC detects the Home_System_Feature_Code trigger and sends a FEATREQ 41
to the MS’s HLR. 42
43
c. The HLR determines that the feature code needs to be handled by another NE. The HLR
44
forwards the FEATREQ with the received parameters to the SCP. 45
46
d. The SCP determines that the MS is authorized for the LBIS service and that the subscriber’s
47
LIR information allows the MS position to be determined. The SCP determines that the MS
48
position information must be obtained. 49
50
If the SCP does not have the Serving MPC address information or the MPCAP for the Target
51
MS, the SCP sends an LPREQ to the HLR.
52
53
e. The HLR determines that the MS is active and registered in the serving system. The HLR
54
returns an lpreq to the SCP. The MPCAddressInfo is set to the Serving MPC’s address
55
information.
56
57
f. The SCP sends an ISPOSREQ to the serving MPC to request the MS position. The PQOS
58
parameter is set to indicate the quality of service requested.
59
60

X.S0009
1 g. The Serving MPC verifies that the request for the Target MS position has been received
2
3
4
5 h. The Serving MPC obtains the information on the current radio environment of the MS,
6
selects a PDE and directs the PDE to obtain the Target MS geoposition. The PDE determines
7
the Target MS position (see TIA-881).
8
9 i. The Serving MPC returns the position information to the SCP.
10
11 j. The SCP determines the appropriate feature treatment based on the received position
12 information. In this scenario, the SCP determines that display text with an announcement
13 shall be provided. The SCP sends a featreq to the HLR with the FEATRES, ANNLIST,
14
DISPTEXT and ACTCODE parameters set accordingly.
15
16 k. The HLR relays the featreq to the Serving MSC with the parameters received from the
17 SCP.
18
19 l. The Serving MSC sends display text to the subscriber’s MS along with an optional tone or
20 announcement to notify the subscriber that a message has arrived.
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
8.3.4 Unsuccessful Single_introducing_Star Invocation of LBIS on a 1

2
Service Node 3
4
This scenario illustrates unsuccessful invocation of a location based information service (LBIS)
5
when the subscriber enters a feature code. The Serving MSC detects the
6
Single_Introducing_Star trigger. LBIS is provided by a separate service node. The MS position
7
cannot be determined and the LBIS service cannot be provided to the MS. 8
9
10
11
MS MSC SCP SN MPC PDE 12
13
14
*FC
a 15
16
ORREQ [MSCID, MSID, DGTSDIAL, SCELLID, MPCAP, MPCAddressInfo, TRIGTYPE]
b 17
18
SERVREQ [SRVID, MSID, DGTSDIAL, SCELLID, MPCAP, MPCAddressInfo, MSCID (Serving)]
19
c
20
ISPOSREQ [MSID, POSREQTYPE, PQOS, MSCID, SCELLID, MPCAP, LCSCID] 21
d
22
ORT SVRT IPRT
23
MPC-MSC-PDE Communications to Determine MS Geoposition e 24

25
isposreq [POSRSULT, LCSBILLID] 26
f
27
servreq [ACCDEN, ANNLIST] 28
g 29

h 31
32
announcement
i 33
34
Figure 15 Unsuccessful Single_introducing_Star Invocation of LBIS on a Service Node 35
36
a. A feature code string is received from a served MS. 37
38
b. The Serving MSC detects the Single_Introducing_Star trigger and sends an ORREQ to the 39
calling party’s SCP. 40
41
c. The SCP determines that LBIS shall be invoked for the MS at another NE. The SCP sends a 42
SERVREQ to the SN. The SRVID parameter is set to indicate the LBIS to invoke. The SCP 43
relays the MSID, DGTSDIAL, SCELLID, MPCAddressInfo and MPCAP parameters 44
received from the Serving MSC. The MSCID parameter is set to the Serving MSC MSCID. 45
The MSID identifies the subscriber. 46
47
d. The SN examines the subscriber’s LIR information and determines the MS position can be 48
determined. The SN sends an ISPOSREQ to the Serving MPC. 49
50
e. The Serving MPC verifies that the request for the Target MS position has been received 51
from an authorized entity (e.g., SN). To satisfy the requested PQOS, the Serving MPC 52
54
a PDE and directs the PDE to obtain the Target MS geoposition. The PDE attempts to 56
determine the Target MS position (see TIA-881). The Target MS position information cannot 57
be determined. 58
59
60

X.S0009
1 f. The Serving MPC returns an isposreq to the SN. The POSRSULT parameter is set to
2
indicate that the Target MS position could not be determined.
3
4 g. The SN cannot provide the LBIS related to the Target MS position. The SN sends a servreq
5 to the SCP. The ACCDEN parameter is set to indicate the service denial. The ANNLIST
6
parameter is set to indicate the announcement to be played to the MS.
7
8 h. The SCP forwards the received parameters to the MSC in the orreq.
9
10 i. The MSC plays an announcement to the MS to indicate the reason that the LBIS could not
11 be completed. The MSC releases the MS.
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
8.3.5 LBIS Invocation Upon MS Registration 1

2
This scenario illustrates invocation of LBIS at MS power-on registration. The MS geographic 3

4
position determines the information delivered by an SN in an IVR interaction. An example is
5
receiving personalized connecting flight information upon landing at an airport and turning on
6
the MS.
7
8
Serving System
9
10
SN HLR VLR MSC PDE MPC 11
12
13
14
a
15
REGNOT [MSCID, MSID, ESN, MPCAddressInfo] 16
b 17
regnot [Profile] RNT RNT 18

c 19
20
regnot [Profile]
d 21
22
e 23
RNT 24
regnot [ ] 25
f
26
ISPOSREQ [MSID, PQOS, POSREQTYPE, MSCID, MPCAP] 27
g
28
29
IPRT h

i 32
33
call setup to MS
j 34
35
Figure 16 LBIS Invocation Upon MS Registration 36
37
a. The Serving MSC determines that a roaming MS is within its service area; the Serving MSC 38
may detect the MS’s presence through autonomous registration, call origination, call 39
termination (i.e., a page response following a call to the roamer port) or a service order. The 40
41
Serving MSC sends a REGNOT to its VLR.
42
b. The VLR determines that (a) the MS had previously registered with an MSC within the 43
domain of the VLR, but the MS has been reported inactive by the VLR, (b) the MS is not 44
45
known to the VLR, or (c) the requested information cannot be made available for the
46
indicated MS. The VLR forward the REGNOT to the HLR associated with the MS.
47
c. The HLR determines that authorization can be granted to the MS. It returns the requested 48
49
information to the VLR in the regnot.
50
d. The VLR forwards the regnot to the Serving MSC. 51

52
e. The HLR has Registration Reporting active for the MS. Upon detecting the MS power-on 53
registration, the HLR reports a change in the Target MS registration status by relaying the 54
55
56
57
58
59
60

X.S0009
1 REGNOT received at Step-b to the SN. The HLR includes the applicable parameters received
2
from the VLR.
3
4
5
7
8 MSID Target MS MSID. R
9
10
ESN Target MS ESN. R
11
MPCAddressInfo: Serving MPC address information. Include if an MPC is R
12 associated with the Serving MSC.
13
14 [MPCADDR] Include when there is a single form of network address O
15 for the Serving MPC.
16
[MPCADLIST] Include when there is more than one form of network O
17
address for the Serving MPC.
18
19
f. The SN returns a regnot to the HLR.
20
21 g. If the SN determines the subscriber’s LIR mode information allows the MS position to be
22
determined and that the MS geoposition is required, the SN sends an ISPOSREQ to the
23
Serving MPC.
24
25 h. The Serving MPC verifies that the request for the Target MS position has been received
26
from an authorized entity (e.g., SN). To satisfy the requested PQOS, the Serving MPC
27
28
30
31
32
33 i. The Serving MPC returns the position information to the SN.
34
35 j. The SN determines that an announcement shall be presented to the subscriber. The SN
36 initiates a voice call to the MS.
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
8.3.6 LBIS Triggered in the Visited System: SLP and MPC on Same Platform 1
2
This scenario depicts the successful invocation of LBIS when a roaming subscriber dials a digit 3
4
string (#JAVA) corresponding to a subscriber-based dialed digit trigger. The LBIS SLP is
5
located on a service platform (SCP) that also supports the Home MPC function.
6
7
Home Serving
8
SCP 9
PDE MPC MSC MS 10
MPC
11
#JAVA 12
a 13
14
ORREQ [MSCID, MSID, DGTSDIAL, BILLID, TRIGTYPE, MPCAddressInfo, MPCAP]
b 15
16
ISPOSREQ [MIN, IMSI, PQOS, POSREQTYPE, MPCAP, MSCID, LCSCID, LCSBILLID]
c 17
ORT 18
19
IPRT MPC-MSC-PDE Communications to Determine MS Geoposition d
20
e
22
orreq [DMH_SVCID, TERMLIST] 23
f 24
call setup 25
g 26
27
Figure 17 LBIS Triggered in Visited System: SLP and MPC on Same Platform 28
29
a. An LBIS subscriber originates a call in the serving system. 30
31
b. The Serving MSC detects a subscriber-based dialed digits trigger and sends an ORREQ to the 32
address of the network entity (SCP) associated with the trigger type. The ORREQ includes 33
the MPCAddressInfo set to indicate the address of the Serving MPC. The MPCAP 34
36
c. The LBIS SLPI checks the subscriber’s LIR information maintained by the Home MPC. The 37
Home MPC is on the same platform as the LBIS SLP. Therefore, there are no intersystem 38
operations required. 39
40
For this scenario, the LBIS is authorized to obtain the subscriber’s geographic position. The 41
LBIS SLPI sends an ISPOSREQ to the Serving MPC. The PQOS parameter is set to indicate 42
the required position quality of service required for the LBIS. The MSID received at Step-b 43
is relayed. The LCSBILLID parameter is set to the value assigned by the Home MPC for the 44
position information request. 45

46
from an authorized entity (e.g., Home MPC, SCP). To satisfy the requested PQOS, the 48
Serving MPC determines that the current position of the Target MS must be obtained. 49
50

54
e. The Serving MPC returns the geographic position of the MS to the SCP in the isposreq. 55
The LCSBILLID parameter is set to the value assigned by the Serving MPC for the Home 56
MPC request. 57
58
59
60

X.S0009
1 f. The LBIS SLPI determines the call destination based on the MS position. The LBIS SLPI
2
sends an orreq to the Serving MSC. The DMH_SVCID parameter is set to indicate that
3
LBIS was invoked. The TERMLIST parameter is set to indicate routing for the call.
4
5 g. The Serving MSC sets up the call.
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
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
8.3.7 LBIS Triggered in Visited System: Separate SLP and MPC 1

2
This scenario depicts the successful invocation of LBIS when a roaming subscriber dials a digit 3
4
string (#JAVA) corresponding to a subscriber-based dialed digit trigger. The LBIS SLP and the
5
Home MPC are located on separate platforms. The Home MPC authorizes the LBIS LCS Client
6
request and verifies that the Target MS subscriber’s LIR permits the LBIS to obtain the Target
7
MS position. 8
9
Home Serving
10
11
MPC SCP MPC PDE MSC MS 12
13
14
#JAVA
a 15
16
ORREQ [MSCID, DGTSDIAL, MSID, MPCAddressInfo, MPCAP]
b 17
18
ISPOSREQ [MIN, IMSI, LCSCID, MSCID, MPCAddressInfo, POSREQTYPE, MPCAP, PQOS]
19
c
20
ISPOSREQ [MPCID, MIN, IMSI, LCSCID, MSCID, MPCAddressInfo, POSREQTYPE, PQOS, MPCAP, LCSBILLID]
21
d
ORT 22
23
IPRT IPRT MPC-MSC-PDE Communications to Determine MS Geoposition e 24

f 26

g 28
29
orreq [DMH_SVCID, TERMLIST]
h 30
31
call setup 32
i
33
Figure 18 LBIS Triggered in Visited System: Separate SLP and MPC 34

35
36
a. An LBIS subscriber originates a call in the serving system.
37
b. The Serving MSC detects a subscriber-based dialed digits trigger and sends an ORREQ to the 38
39
address of the network entity (SCP) associated with the trigger type. The ORREQ includes
40
the MPCAddressInfo set to indicate the address of the Serving MPC. The MPCAP
41
parameter is set to indicate the positioning capability of the MS.
42
43
c. For this scenario, the LBIS SLP is not on the same platform as the Home MPC. The LBIS
44
SLPI sends an ISPOSREQ to the Home MPC. The PQOS parameter is set to indicate the
45
required position quality of service required for the LBIS.
46
47
48
49
50
52
LCSCID Requesting LCS Client ID. R 53
54
55
MPCAddressInfo: Serving MPC address information. Include if an MPC is R 56

associated with the Serving MSC. 57
58
59
60

X.S0009
1
2
3
4
for the Serving MPC.
5
6 [MPCADLIST] Include when there is more than one form of network O
7 address for the Serving MPC.
8
9
10
MPCAP MS positioning capability. R
11
13
14 d. The Home MPC verifies that the requesting LCS Client (LBIS) is authorized to obtain the
15 Target MS position. The Home MPC also verifies that the Target MS subscriber’s LIR
16 information permits the LBIS to obtain position information. The Home MPC sends an
17 ISPOSREQ to the Serving MPC requesting position information for the Target MS.
18
19
20
21 MPCID Home MPC MPCID. R
22
23 MIN Target MS MIN. Include if available. O
24
25
26
27
29
30 MPCAddressInfo: Serving MPC address information. Include if an MPC is R
associated with the Serving MSC.
31
32
33 for the Serving MPC.
34
35 [MPCADLIST] Include when there is more than one form of network O
36
address for the Serving MPC.
37
38
39 MPCAP MS positioning capability. R
40
42
LCSBILLID LCS Billing ID. R
43
44
45
e. The Serving MPC verifies that the request for the Target MS position has been received
46 from an authorized entity (e.g., Home MPC). To satisfy the requested PQOS, the Serving
47 MPC determines that the current position of the Target MS must be obtained.
48
49
The Serving MPC obtains the information on the current radio environment of the MS, selects
52
53
f. The Serving MPC returns the geographic position of the MS to the Home MPC in the
54 isposreq.
55
56
g. The Home MPC returns the geographic position of the Target MS to the LBIS SLPI.
57
58
59
60

X.S0009
h. The LBIS SLPI determines the call destination based on the MS position. The LBIS SLPI 1
2
sends an orreq to the Serving MSC. The DMH_SVCID parameter is set to indicate that
3
LBIS was invoked. The TERMLIST parameter is set to indicate routing for the call.
4
i. The Serving MSC sets up the call. 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
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
1
2
8.4 Enhanced Call Routing (ECR)
3
4
8.4.1 Successful Enhanced Call Routing
5
6
This scenario illustrates successful Enhanced Call Routing to route the call to the gas station
7
closest to the MS position. The MS is a WIN subscriber and has subscribed to the ECR service.
8
9
Serving System
10
11
12 MS MSC PDE MPC SCP
13
14 MS origination
15 a
16
ORREQ [MSCID, MSID, DGTSDIAL, MPCAP, MPCAddressInfo, TRIGTYPE]
17 b
18 ORT
19
ISPOSREQ [MIN, IMSI, POSREQTYPE, PQOS, MSCID, MPCAP, LCSCID]
20
c
21
22
23 IPRT d
24
26 e
27
orreq [TERMLIST, DMH_SVCID, GEOPOS]
28 f
29
call setup
30 g
31
32 Figure 19 Successful Enhanced Call Routing
33
34 a. A subscriber with ECR service originates a call to the closest provider of that LBS service
35 (e.g. the subscriber dials #GAS to locate the nearest gas station).
36
37 b. The Serving MSC detects the Single_Introducing_Pound trigger and sends an ORREQ to the
38 SCP associated with that trigger. The Serving MSC includes the Serving MPC address
39 information and the MPCAP parameter set to indicate the positioning capability of the MS.
40
41 c. The SCP determines that the ECR service is active for the subscriber. The ECR SLPI checks
42 the LIR privacy settings for the subscriber. For this scenario, the ECR service is authorized
43 to obtain the Target MS geographic position. If the geographic position of the MS is required
44
to determine the appropriate routing, the SCP sends an ISPOSREQ to the serving MPC to
45
request the MS position. The PQOS parameter indicates the quality of service requested.
46
48
49
50
52
53
54
55 e. The Serving MPC returns the MS geoposition to the SCP in the isposreq.
56
57 f. Based on the geoposition of the MS, the service logic program determines the appropriate
58 routing digits associated with the closest provider of that ECR service. Note: this
59 determination may be performed by the SCP directly or it may query an external application
60
Enhanced Call Routing (ECR) 67 TIA/EIA-41.3-D Modifications

X.S0009
for this information. The SCP populates the TERMLIST with the appropriate ECR routing 1
2
information. The SCP sends an orreq to the Serving MSC. The DMH_SVCID parameter
3
is set to indicate ECR has been invoked. The GEOPOS information is set to record the
4
geographic position of the MS for recording purposes.
5
6
g. The Serving MSC sets up the call.
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41.3-D Modifications 68 Enhanced Call Routing (ECR)

X.S0009
1
8.4.2 Unsuccessful Enhanced Call Routing: MS Position Not Available
2
3 This scenario illustrates unsuccessful Enhanced Call Routing because the geographic position
4
of the MS is not available. The MS is a WIN subscriber and has subscribed to the ECR service.
5
6 Serving System
7
8
MS MSC PDE MPC SCP
9
10
11 MS origination
12
a
13 ORREQ [MSCID, MSID, DGTSDIAL, MPCAP, MPCAddressInfo, TRIGTYPE]
14 b
15 ISPOSREQ [MIN, IMSI, POSREQTYPE, PQOS, MSCID, MPCAP, LCSCID]
16 c
17 ORT
18
19 IPRT d
20
21 isposreq [POSRSULT, LCSBILLID]
e
22
23 orreq [ACCDEN, ANNLIST]
24
f
25 announcement
26 g
27
28
Figure 20 Unsuccessful Enhanced Call Routing: MS Position Not Available
29
30 a. A user dials a feature code to contact the nearest gas station.
31
32
b. The Serving MSC detects the Single_Introducing_Pound trigger and sends an ORREQ to the
35
36
c. The SCP determines that the ECR service is active for the subscriber. In this scenario, the
37 geographic position of the MS is required to determine the appropriate routing. The ECR
38 SLPI checks the LIR privacy settings for the subscriber. For this scenario, the ECR service is
39 authorized to obtain the Target MS geographic position. The SCP sends an ISPOSREQ to
40 the Serving MPC to request the MS position. The PQOS parameter indicates the quality of
41 service requested.
42
46
48 a PDE and directs the PDE to obtain the Target MS geoposition. The PDE attempts to obtain
49 the Target MS position (see TIA-881).
50
51 e. The MS position is not available. The Serving MPC sends an isposreq to the SCP with
52 the POSRSULT parameter set to indicate Requested Position is not available.
53
54 f. The SCP cannot determine the appropriate ECR routing because the MS geographic position
55 information is not available. The SCP includes the ACCDEN and ANNLIST parameters in
56 the orreq sent to the Serving MSC. The ACCDEN parameter indicates denial of this
57 service request. The ANNLIST parameter specifies the announcement to be played to the
58 MS.
59
60

X.S0009
g. The Serving MSC plays an announcement to the MS to indicate the reason the ECR call 1
2
could not be completed. The MSC releases the MS.
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
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
1
8.4.3 Unsuccessful Enhanced Call Routing: LIR Service Denial
2
3 This scenario illustrates unsuccessful Enhanced Call Routing due to service denial based on the
4
subscriber’s LIR information.
5
6 Serving System
7
8
MS MSC PDE MPC SCP
9
10
11 MS origination
12
a
13 ORREQ [MSCID, MSID, DGTSDIAL, MPCAP, MPCAddressInfo, TRIGTYPE]
14 b
15 ORT orreq [ACCDEN, ANNLIST]
16 c
17
announcement
18 d
19
20 Figure 21 Unsuccessful Enhanced Call Routing: LIR Service Denial
21
22 a. A user dials a feature code to contact the nearest gas station.
23
24 b. The Serving MSC detects the Single_Introducing_Pound trigger and sends an ORREQ to the
27
28 c. The SCP determines that the ECR service is active. The SCP verifies the LIR privacy
29 settings of the subscriber and denies the service requested based on the LIR information. The
30 SCP sends an orreq to the MSC with the ACCDEN and ANNLIST parameters. The
31
ACCDEN parameter indicates denial of this service request. The ANNLIST parameter
32
specifies the announcement to be played to the MS
33
34 d. The MSC plays an announcement to the MS to indicate the reason the ECR call could not be
35
completed. The MSC releases the MS.
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
8.4.4 Unsuccessful Enhanced Call Routing: Routing Number Not Available 1

2
This scenario illustrates unsuccessful Enhanced Call Routing to route the call to the gas station 3
4
closest to the MS position. The SCP is unable to make the necessary association between the
5
MS geographic position and the routing number for the nearest ECR service provider.
6
7
Serving System
8
9
MS MSC PDE MPC SCP 10
11
MS origination 12
a 13
14
ORREQ [MSCID, MSID, DGTSDIAL, MPCAP, MPCAddressInfo, TRIGTYPE]
b 15
ORT 16
17
ISPOSREQ [MIN, IMSI, POSREQTYPE, PQOS, MSCID, MPCAP, LCSCID]
c 18
19
20
MPC-MSC-PDE Communications IPRT d 21
22
e 24

f 26
27
announcement
g 28
29
Figure 22 Unsuccessful Enhanced Call Routing: Routing Number Not Available 30
31
a. A user dials a feature code to contact the nearest gas station. 32
33
b. The Serving MSC detects the Single_Introducing_Pound trigger and sends an ORREQ to the 34
SCP associated with that trigger. The Serving MSC includes the Serving MPC address 35
information and the MPCAP parameter set to indicate the positioning capability of the MS. 36
37
c. The SCP determines that the ECR service is active for the subscriber. If the geographic 38
position of the MS is required to determine the appropriate routing, the ECR SLPI checks 39
the LIR privacy settings for the subscriber. The SCP sends an ISPOSREQ to the Serving 40
MPC to request the MS position. The PQOS parameter indicates the quality of service 41
requested. 42
43

47

51
e. The Serving MPC returns the MS position information to the SCP in the isposreq. 52
53
f. The service logic program is unable to obtain the appropriate routing digits associated with 54
the closest provider of that ECR service. Note: This could be due to either internal 55
processing error at the SCP or a failure in communication with an external database used to 56
obtain this information. The SCP sends an orreq to the MSC with the ACCDEN and 57
58
59
60

X.S0009
1 ANNLIST parameters. The ACCDEN parameter indicates denial of this service request. The
2
ANNLIST parameter specifies the announcement to be played to the MS.
3
4 g. The MSC plays an announcement to the MS to indicate the reason the ECR call could not be
5 completed. The MSC releases the MS.
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
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
8.4.5 Successful Enhanced Call Routing Invoked by Dialing Special Number 1

2
This scenario illustrates successful Enhanced Call Routing to route the call to the gas station 3
4
closest to the MS position. ECR is invoked by the MS user dialing a specific digit string
5
recognized by the Serving MSC.
6
7
Serving System
8
9
MS MSC PDE MPC SCP 10
11
MS origination 12
a 13
14
ANLYZD [MSCID, MSID, DGTSDIAL, TRIGTYPE] 15
b
16
17
ISPOSREQ [MIN, IMSI, POSREQTYPE, PQOS, MSCID, MPCAP, LCSCID
c 18
ANZT 19
ISPOSREQ [MIN, IMSI, POSREQTYPE, PQOS, MPCAP, LCSCID, LIRAUTH, LCSBILLID] 20

d 21
22
IPRT
isposreq [MSCID, SCELLID, MPCAP, MOBINFO] 23
IPRT e 24
25
f
28
g 29
30
31
anlyzd [TERMLIST, DMH_SVCID, GEOPOS]
h 32
33
call setup 34
i 35
36
Figure 23 Successful Enhanced Call Routing Invoked by Dialing a Special Number
37
38
a. An MS user originates a call to the closest provider of that LBS service (e.g. the subscriber 39
dials #GAS to locate the nearest gas station). 40
41
b. The user dialed a called number for which a Specific_Called_Party_Digit_String trigger is
42
armed. The Serving MSC sends an ANLYZD to the SCP associated with the trigger. 43
44
c. The SCP sends an ISPOSREQ requesting the MS position to the VAS MPC associated with
45
the Serving MSC.
46
47
d. The Serving MPC assigns an LCS Billing ID for the position information request. The
48
Serving MPC sends an ISPOSREQ to the Serving MSC requesting Target MS
49
information. The LIRAUTH parameter is set to indicate the LCS Client is User
50
Authorized and requests authorization of the geoposition request.
51
e. The LIR Mode information for the subscriber indicates the requesting LCS Client is 52
authorized to obtain the indicated MS’s position information. The Serving MSC sends an 53
isposreq to the Serving MPC. 54
55
f. The Serving MPC selects a PDE and directs the PDE to obtain the Target MS geoposition. 56
The PDE determines the Target MS position (see TIA-881). 57
58
g. The Serving MPC returns the MS geoposition to the SCP in the isposreq.
59
60

X.S0009
1 h. Based on the geoposition of the MS, the service logic program determines the appropriate
2
routing digits associated with the closest provider of that ECR service. Note: this
3
determination may be performed by the SCP directly or it may query an external application
4
for this information. The SCP populates the TERMLIST with the appropriate ECR routing
5
6
information. The SCP sends an anlyzd to the Serving MSC. The DMH_SVCID parameter
7
is set to indicate ECR has been invoked. The GEOPOS information is set to record the
8 geographic position of the MS for recording purposes.
9
10
i. The Serving MSC sets up the call.
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
8.5 Non-SIM Registration Reporting 1

2
3
The scenarios in this section illustrate how Registration Reporting relates to the location based
4
services shown in this document. 5
6
8.5.1 Non-SIM Report of MS Registration 7

8
9
This scenario illustrates the report of MS registration in a serving system.
10
Serving System 11
12
13
SCP HLR VLR MPC PDE MSC MS
14
15
MS power on 16
a 17
18
b 19
20
c 21
RNT RNT 22
regnot [Profile] 23
d
24
regnot [Profile] 25
e
26
f 28
RNT
regnot [ ] 29
g 30

h 32
33
34
IPRT i
36
j
38
39
Figure 24 Non-SIM Report of MS Registration 40
41
a. An MS powers on in a new serving system. 42
43
b. The Serving MSC determines that a roaming MS is within its service area. The Serving 44
MSC sends a REGNOT to the VLR. The MPCAddressInfo is set to the address information 45
of the Serving MPC. 46
47
c. The Serving VLR determines that either (a) the MS had previously registered with an MSC 48
within the domain of the VLR but the MS has been reported inactive by the VLR, (b) the MS 49
is not known to the VLR, or (c) the requested information cannot be made available for the 50
indicated MS. 51
52
Under these conditions, the Serving VLR forwards the REGNOT to the HLR associated with 53
the MS. 54
55
d. The HLR determines that authorization can be granted to the MS. It returns the requested 56
information to the Serving VLR in the regnot. 57
58
e. The VLR forwards the regnot to the Serving MSC. 59
60
TIA/EIA-41.3-D Modifications 76 Non-SIM Registration Reporting

X.S0009
1 f. The HLR determines that a report of the MS registration is required. The HLR relays the
2
REGNOT received at Step-c to the SCP.
3
4 g. The SCP responds with an empty regnot.
5
6 h. If the SCP determines that the geographic position of the MS is required, the SCP examines
7 the subscriber’s LIR information and verifies that the MS position can be obtained. The SCP
8 sends an ISPOSREQ to the Serving MPC.
9
10 The POSREQTYPE parameter is set to indicate Return the updated position.
11
12 i. The Serving MPC verifies that the request for the Target MS position has been received
15
19
20 j. The MPC returns the geographic position of the MS to the SCP in the isposreq.
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Non-SIM Registration Reporting 77 TIA/EIA-41.3-D Modifications

X.S0009
8.5.2 Non-SIM Report of MS Registration to Multiple SCFs 1

2
This scenario illustrates the report of MS registration in a serving system to multiple SCFs. 3
4
Serving System 5
6
7
SCP-1 SCP-2 HLR VLR MSC MPC PDE
8
9
MS power on 10
a 11
b 13
14
c 15
RNT RNT 16
regnot [Profile]
d 17
18
regnot [Profile] 19
e
20
f
22
RNT
regnot [ ] 23
g 24
25
h 26
RNT 27
regnot [ ]
i 28
29
j
31
IPRT k
isposreq [POSRSULT, POSINFO, LCSBILLID] 34
l 35

m 37
38
IPRT MPC-MSC-PDE Communications n 39
40
isposreq [POSRSULT, POSINFO, LCSBILLID]
o 41
42
Figure 25 Non-SIM Report of MS Registration to Multiple SCFs 43
44
a. An MS powers on in a new serving system. 45

46
b. The Serving MSC determines that a roaming MS is within its service area. The Serving 47
MSC sends a REGNOT to the VLR. The MPCAddressInfo is set to the address information 48
of the Serving MPC. 49

50
c. The Serving VLR determines that either (a) the MS had previously registered with an MSC 51
within the domain of the VLR but the MS has been reported inactive by the VLR, (b) the MS 52
is not known to the VLR, or (c) the requested information cannot be made available for the 53
indicated MS. 54
55
Under these conditions, the Serving VLR forwards the REGNOT to the HLR associated with 56
the MS. 57
58
59
60

X.S0009
1 d. The HLR determines that authorization can be granted to the MS. It returns the requested
2
information to the Serving VLR in the regnot.
3
4 e. The VLR forwards the regnot to the Serving MSC.
5
6 f. The HLR determines that a report of the MS registration to SCP-1 is required (e.g., based on
7 provisioning at HLR). The HLR relays the REGNOT received at Step-c to SCP-1.
8
9 g. SCP-1 responds with an empty regnot.
10
11
h. The HLR determines that a report of the MS registration to SCP-2 is also required (e.g.,
12 based on provisioning at HLR). The HLR relays the REGNOT received at Step-c to SCP-2.
13
14
i. SCP-2 responds with an empty regnot.
15
j. If SCP-1 determines that the geographic position of the MS is required, SCP-1 examines the
16
subscriber’s LIR information and verifies that the MS position can be obtained. SCP-1 sends
17
18
an ISPOSREQ to the Serving MPC.
19
20
21 k. The Serving MPC verifies that the request for the Target MS position has been received
22
23
24
26
27
28
29 l. The MPC returns the geographic position of the MS to SCP-1 in the isposreq.
30
31 m. If SCP-2 determines that the geographic position of the MS is required, SCP-2 examines the
32 subscriber’s LIR information and verifies that the MS position can be obtained. SCP-2 sends
33 an ISPOSREQ to the Serving MPC.
34
35 The POSREQTYPE parameter is set to indicate Return the updated position.
36
37 n. The Serving MPC verifies that the request for the Target MS position has been received
40
44
45 o. The MPC returns the geographic position of the MS to SCP-2 in the isposreq.
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
8.5.3 Non-SIM Report of MS Deregistration 1

2
This scenario illustrates the successful report of MS deregistration when the MS powers down. 3
4
Serving System 5
6
7
SCP HLR VLR MSC MS
8
9
MS power down 10
a 11

b 13
MSIT 14
msinact [ ]
c 15
16
d 17
MSIT 18
msinact [ ] 19
e
20
f
22
MSIT
msinact [ ] 23
g 24
25
Figure 26 Non-SIM Report of MS Deregistration
26
27
a. The MS powers down. 28
29
b. The Serving MSC determines that deregistration of a served MS is required. The Serving
30
MSC sends an MSINACT to the VLR and includes the DEREG parameter. At this point, the 31
MSC may choose to remove all record of the MS from its memory. 32
33
c. The Serving VLR sends an empty msinact to the Serving MSC.
34
35
d. The Serving VLR determines that deregistration of an MS is required based either on the
36
receipt of an MSINACT from the Serving MSC or on internal algorithms. It sends an
37
MSINACT, including a DeregistrationType parameter, to the HLR. At this point, the VLR
38
may choose to remove all record of the MS from its memory. 39
40
e. The HLR sends an empty msinact to the Serving VLR and removes its pointer to the
41
VLR.
42
43
f. The HLR determines that a report of the MS deregistration is required. The HLR relays the
44
MSINACT received at Step-d to the SCP.
45
g. The SCP responds with an empty msinact. The SCP ends any ongoing position 46
47
determination for the Target MS (e.g., for FAM) and cancels any scheduled position
48
determination requests for the Target MS.
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
1
8.5.4 Activation or Deactivation of Registration Report
2
3 This scenario illustrates the activation or de-activation of registration reporting to an SCP for an
4
indicated MS. The MS is identified by the MS MSID.
5
6
7
8
SCP HLR
9
10
11 STATNOTREQ [MSCID, MSID, REGREPORT, DESTADDRS]
12 a
13 SNRT statnotreq [ ]
14 b
15
16 Figure 27 Activation or Deactivation of Registration Report
17
18 a. A service logic program (SLP) determines that registration reporting for an MS shall be
19 activated or deactivated. The SCP sends a STATNOTREQ to the HLR associated with the
20 MS.
21
22
23
24 MSCID SCP MSCID. R
25
26 MSID MS MSID. R
27
REGREPORT RegistrationReport. Activation or deactivation of R
28
registration report.
29
30 DESTADDRS Destination address for registration reporting. Include if O
31 applicable.
32
33 b. The HLR activates or de-activates registration reporting of the indicated MS for the
34 designated network entity. The HLR responds with a statnotreq to the designated
35 network entity.
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
8.5.5 Activation or Deactivation of Registration Report: MDN MS Identifier 1

2
This scenario illustrates the activation or de-activation of registration reporting to an SCP for an 3
4
indicated MS. The MS is identified by the MS MDN.
5
6
7
8
SCP HLR
9
10
STATNOTREQ [MSCID, MDN, REGREPORT, DESTADDRS] 11

a 12
SNRT 13
statnotreq [ ]
b 14
15
Figure 28 Activation or Deactivation of Registration Report: MDN MS Identifier 16
17
a. A service logic program (SLP) determines that registration reporting for an MS shall be 18
activated or deactivated. The SCP sends a STATNOTREQ to the HLR associated with the 19
MS. 20
21
22
23
25
MDN MS MDN. R 26
27
REGREPORT RegistrationReport. Activation or deactivation of R
28
registration report.
29
DESTADDRS Destination address for registration reporting. Include if O 30
applicable. 31
32
b. The HLR activates or de-activates registration reporting of the indicated MS for the 33
designated network entity. The HLR responds with a statnotreq to the designated 34
network entity. 35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
1
3
4 This section provides the additions and modifications to TIA/EIA-41-D Chapter 5 signaling
5 protocol for Wireless Intelligent Network Capabilities for Location Based Services.
6
7
8
9
5 DATA TRANSFER SERVICES
10
11
12 5.1 SS7-Based Data Transfer Services
13
(See TIA/EIA-41.5-D, page 5-6)
14
15
Table 1 MTP Message Priority Values for TIA/EIA-41 Operations
16
17 TIA/EIA-41 Operation MTP Message Priority
18
19 StatusNotificationRequest 0
20
21
22
23
24 6 APPLICATION SERVICES
25
26
27
28
6.4 MAP Operations
29
30
31
6.4.1 General
32
6.4.1.2 Operation Specifiers
33
34 (See TIA/EIA-41.5-D, page 5-24)
35
36 Table 2 TIA/EIA-41 MAP Operation Specifiers
37
38
Operation Name Operation Specifier
39
H G F E D C B A Decimal
40
41 StatusNotificationRequest 0 1 1 0 0 1 1 1 103
42
43
44
45 6.4.2 Operation Definitions
46
47
48
Table 3 Summary of MAP Operations
49
50 Operation Reference
51
52 StatusNotificationRequest 6.4.2.av
53
54
55
56
57
58
59
60
Data Transfer Services 83 TIA/EIA-41.5-D Modifications

X.S0009
6.4.2.13 FeatureRequest 1
2
3
(See IS-751, page 24)
4
(See IS-771, page 4-09) 5
(See IS-848, page 5-04) 6

7
The FeatureRequest (FEATREQ) operation is used to request feature-related treatment on 8
behalf of a registered MS. The following table lists the valid combinations of invoking and 9
responding NEs. 10
11
INVOKING NE RESPONDING NE 12
13
Case 1 Serving MSC HLR 14
15
Case 2 Serving MSC Serving VLR
16
(Note)
17
Case 3 Serving VLR HLR 18
(Note) 19
20
Case 4 HLR SCP or SN 21
22
Case 5 SCP or SN SCP or SN
23
24
Case 1 above is termed a ‘direct’ FeatureRequest operation, since it occurs directly between the 25
Serving MSC and the HLR without the involvement of the VLR. 26
27
One of several possible results is returned: 28
29
1. Notification that the feature request was successful with an (optional) indication of the 30
treatment to provide the served MS. 31
32
2. Notification that the feature request was unsuccessful with an (optional) indication of
33
the treatment to provide the served MS.
34
Possible served MS treatment includes provision of a tone or announcement, call release, or 35
further call routing based on the specifics of the feature request. 36
37
Note: These cases are no longer recommended. 38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41.5-D Modifications 84 MAP Operations

X.S0009
1 The FeatureRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a
2 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows:
3
4
FeatureRequest INVOKE Parameters Timer: FRT
5
6 Field Value Type Reference Notes
7
Identifier SET [NATIONAL 18] M 6.3.2.1
8
9 Length variable octets M 6.3.2.1
10
Contents
11
12 Digits (Dialed) M 6.5.2.58
13
ElectronicSerialNumber M 6.5.2.63
14
15 MSID M 6.5.2.bv a
16 BillingID (Originating) O 6.5.2.16 b
17
18
CallingPartyName O 6.5.2.bw c
19 CallingPartyNumberDigits1 O 6.5.2.21 d
20
CallingPartyNumberDigits2 O 6.5.2.22 d
21
22 CallingPartySubaddress O 6.5.2.25 d
23
ConferenceCallingIndicator O 6.5.2.49 e
24
25 MobileDirectoryNumber O 6.5.2.80 f
26
MobilePositionCapability O 6.5.2.fm d, l
27
28 MSCID (Serving) O 6.5.2.82 g
29
MSCIdentificationNumber O 6.5.2.83 d
30
31 OneTimeFeatureIndicator O 6.5.2.88 h
32 PC_SSN O 6.5.2.93 i
33
34
SenderIdentificationNumber O 6.5.2.116 j
35 TransactionCapability O 6.5.2.160 k
36
37
Notes:
38
39 a. Include the identifier with which the MS last accessed the system, unless that identifier
40 was a MIN-based IMSI, in which case the MobileIdentificationNumber (populated
41 with the MIN derived from that IMSI) should be included.
42
43
b. Include for recording purposes or for call correlation (see DMH).
44
c. Include if calling party name information is known.
45
46 d. Include if applicable.
47
48 e. Include to indicate the number of conferees already in the call.
49
f. Include if available for recording purposes or for call correlation (see DMH).
50
51 g. Include to identify the Anchor MSC. (This may become the Originating MSC for
52 subsequent call redirection.)
53
54 h. Include if any OneTimeFeatureIndicator parameter status bits are set (i.e., have value
55 of 1).
56
57
i. Include if SS7 may be used for subsequent call redirection.
58
j. Include to identify the network entity sending the message.
59
60
MAP Operations 85 TIA/EIA-41.5-D Modifications

X.S0009
k. Include on IS-41-C or later. 1

2
l. Include if known, to identify the MS’s position capabilities. The value from the MS 3
takes precedence over the value from the service profile, if both are available. 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
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
1 The FeatureRequest operation success is reported with a TCAP RETURN RESULT (LAST).
2
This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
3
4
FeatureRequest RETURN RESULT Parameters
5
7
8
10
Contents
11
12 FeatureResult M 6.5.2.67
13
AccessDeniedReason O 6.5.2.1 a
14
15 ActionCode O 6.5.2.2 b
16
AnnouncementList O 6.5.2.6 c
17
18 CallingPartyNumberString1 O 6.5.2.23 d
19 CallingPartyNumberString2 O 6.5.2.24 d
20
21
CallingPartySubaddress O 6.5.2.25 d
22 CarrierDigits O 6.5.2.28 d
23
ConferenceCallingIndicator O 6.5.2.49 e
24
25 Digits (Dialed) O 6.5.2.58 f
26
DisplayText O 6.5.2.bx p, qg
27
28 DMH_AccountCodeDigits O 6.5.2.59 h
29
DMH_AlternateBillingDigits O 6.5.2.60 h
30
31 DMH_BillingDigits O 6.5.2.61 h
32
DMH_RedirectionIndicator O 6.5.2.62 d
33
34 DMH_ServiceID O 6.5.2.ei r
35 GroupInformation O 6.5.2.69 i
36
37
MobileDirectoryNumber O 6.5.2.80 h
38 NoAnswerTime O 6.5.2.87 d
39
OneTimeFeatureIndicator O 6.5.2.88 j
40
41 PACAIndicator O 6.5.2.91 k
42
PilotNumber O 6.5.2.95 i
43
44 PreferredLanguageIndicator O 6.5.2.96 d, l
45
RedirectingNumberDigits O 6.5.2.107 d
46
47 RedirectingNumberString O 6.5.2.108 d
48
RedirectingSubaddress O 6.5.2.109 d
49
50 ResumePIC O 6.5.2.cu q
51 RoutingDigits O 6.5.2.114 d
52
53
TerminationList O 6.5.2.156 n
54 TerminationTriggers O 6.5.2.57 d
55
TriggerAddressList O 6.5.2.de o
56
57
58
59
60

X.S0009
Notes: 1
2
a. Include if access is denied. If included, no other optional parameters shall be included 3
(with the exception of the AnnouncementList parameter). 4
5
b. Include if action to be performed is not implied through presence of other parameters.
6
c. Include if provision of one or more tones or announcements is required. 7

8
d. Include if applicable. 9
10
e. Include to direct that ongoing call be transformed into a Conference Call. 11
12
f. Include if digits remain to be translated by the MSC.
13
g. Include for local termination to an MS if a related feature is active. 14
15
h. Include if applicable and for recording purposes (see DMH). 16
17
i. Include for multi-leg calls.
18
j. Include if modification to normal feature processing is required for call in progress. 19

20
k. Include to indicate PACA priority level. 21
22
l. This parameter may only be included if the AnnouncementList parameter is present. 23
24
m. Include to indicate the PIC where call processing is to resume.
25
n. Include if call routing is required. 26

27
o. Include to indicate address associated with active WIN triggers. 28
29
p. Include if a LocalTermination parameter is included in the TerminationList parameter 30
and display text shall be presented to the called MS. 31
32
q. Include if the ActionCode parameter is included and is set to indicate that display text
33
shall be presented to the calling MS.
34
r. Include for recording purposes if a WIN service was invoked. 35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
1 6.4.2.29 MSInactive
2
(See TIA/EIA 41.3-D, page 3-82)
3
4 The MSInactive (MSINACT) operation is used to indicate that an MS is inactive. The
5 MSInactive operation is also used by the Serving VLR to notify the HLR of the cancellation of
6
an MS’s registration. The MSInactive operation is used by the HLR to provide the MS’s
7
CallHistoryCount to the AC when the SSD is shared with the VLR, and the VLR cancels the
8
MS’s registration. When Registration Reporting is active at the HLR for an MS, the MSInactive
9
10
operation is used by the HLR to notify an SCF network entity that the MS is inactive or that the
11
MS’s registration has been cancelled.
12
The following table lists the valid combinations of invoking and responding NEs.
13
14
15
INVOKING NE RESPONDING NE
16
Case 1 Serving MSC Serving VLR
17
18 Case 2 Serving VLR HLR
19
20 Case 3 HLR AC
21
Case 4 HLR SCP or SN
22
23
24
25
26
27 The remainder of this section is retained unchanged.
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
6.4.2.30 OriginationRequest 1
2
(See TIA/EIA 41.5-D, page 5-81)
3
(See IS-737, page 5-36)
(See IS-771, page 4-20) 4
(See IS-826, page 5-07) 5
(See IS-848, page 5-08) 6
7
The OriginationRequest (ORREQ) operation is used to request call origination treatment on
8
behalf of a registered MS. The OriginationRequest may be relayed by an intervening HLR to
9
enable a subscriber roaming in a TIA/EIA-41 pre-WIN serving system to access a WIN service
10
(or a limited form of that service) for which the service logic program has been placed on an
11
SCP distinct from the subscriber’s HLR.
12
The following table lists the possible combinations of invoking and responding NEs. 13
14
15
INVOKING NE RESPONDING NE
16
Case 1 Serving MSC HLR 17
18
Case 2 HLR SCP 19
20
Case 3 Serving MSC SCP
21
22
One of several possible results is returned: 23

24
1. Notification that the origination request was successful with routing instructions. 25
26
2. Notification that the origination request was unsuccessful with an (optional) indication 27
of the treatment to provide the served MS. 28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
1 The OriginationRequest operation is initiated with a TCAP INVOKE (LAST). This is carried
2
by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows:
3
4
OriginationRequest INVOKE Parameters Timer: ORT
5
7
8
10
Contents
11
12 BillingID (Originating) M 6.5.2.16
13
Digits (Dialed) M 6.5.2.58
14
15 ElectronicSerialNumber M 6.5.2.63
16
MSCID (Originating MSC) M 6.5.2.82
17
18 MSID M 6.5.2.bv a
19 OriginationTriggers M 6.5.2.90
20
21
TransactionCapability M 6.5.2.160
22 CallingPartyName O 6.5.2.bw b
23
CallingPartyNumberDigits1 O 6.5.2.21 c
24
25 CallingPartyNumberDigits2 O 6.5.2.22 c
26
CallingPartySubaddress O 6.5.2.25 c
27
28 CDMAServiceOption O 6.5.2.f d
29
FeatureIndicator O 6.5.2.ej e
30
31 LocationAreaID O 6.5.2.77 c, f
32
MobileDirectoryNumber O 6.5.2.80 g
33
34 MobilePositionCapability O 6.5.2.fm c, q
35 MobInfo AMPS **Macro** O 6.5.2.fn r
36
37
MobInfo CDMA **Macro** O 6.5.2.fo s
38 MobInfo TDMA **Macro** O 6.5.2.fp t
39
MobInfo NAMPS **Macro** O 6.5.2.fq u
40
41 MPCAddress O 6.5.2.ha v, x, y
42
MPCAddressList O 6.5.2.hm w, x, y
43
44 MSCIdentificationNumber O 6.5.2.83 h
45
OneTimeFeatureIndicator O 6.5.2.88 i
46
47 PC_SSN (Originating MSC) O 6.5.2.93 j
48
PreferredLanguageIndicator O 6.5.2.96 k
49
50 SenderIdentificationNumber O 6.5.2.116 l
51 ServingCellID O 6.5.2.117 c, f
52
53
TriggerType O 6.5.2.dh n
54 TDMAServiceCode O 6.5.2.i o
55
WINCapability O 6.5.2.di p
56
57
58
59
60

X.S0009
Notes: 1
2
a. Include the identifier with which the MS last accessed the system, unless that identifier 3
was a MIN-based IMSI, in which case the MobileIdentificationNumber (populated 4
with the MIN derived from that IMSI) should be included. 5
6
b. Include if calling party name information is known.
7
c. Include if applicable. 8
9
d. Include to specify requested CDMA service information. 10
11
e. Include to identify a feature invoked for the call (e.g., Three-Way Calling). 12
13
f. Include if the current location area information is available.
14
g. Include if available for recording purposes (see DMH). 15
16
h. Include to identify the MSC initiating the message. 17
18
i. Include if any OneTimeFeatureIndicator status bits are set (i.e., have value of 1).
19
j. Include if SS7 may be used for subsequent call redirection. 20

21
k. Include if available. 22
23
l. Include if different from the MSCIdentificationNumber to identify the network entity 24
sending the message. 25
26
m. Include if the current serving cell identity is available.
27
n. Include to identify the trigger encountered. 28

29
o. Include to specify requested TDMA service information. 30
31
p. Include to identify the WIN capabilities supported. 32
33
q. Include if known, to identify the MS’s position capabilities. The value from the MS
34
takes precedence over the value from the service profile, if both are available.
35
r. Include if an AMPS channel is in use. 36
37
s. Include if a CDMA channel is in use. 38
39
t. Include if a TDMA channel is in use.
40
u. Include if an NAMPS channel is in use. 41

42
v. Include to specify the network address of the MPC associated with the Serving MSC 43
when there is a single form of the network address for the MPC, if applicable. 44
45
w. Include to specify the list of addresses for the MPC associated with the Serving MSC 46
when there is more than one form of network address for the MPC, if applicable. 47
48
x. These parameters are mutually exclusive.
49
y. See TIA-881. 50
51
52
53
54
55
56
57
58
59
60

X.S0009
1 The OriginationRequest operation success is reported with a TCAP RETURN RESULT

2
(LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as
3
follows:
4
5
OriginationRequest RETURN RESULT Parameters
6
8
9
11
Contents
12
13 AccessDeniedReason O 6.5.2.1 a
14
ActionCode O 6.5.2.2 b
15
16 AnnouncementList O 6.5.2.6 c
17
CallingPartyNumberString1 O 6.5.2.23 d, e
18
19 CallingPartyNumberString2 O 6.5.2.24 d, e
20
CallingPartySubaddress O 6.5.2.25 d, e, f
21
22 CarrierDigits O 6.5.2.28 g
23 Digits (Dialed) O 6.5.2.58 h
24
25
DisplayText O 6.5.2.bx u, vd, e
26 DMH_AccountCodeDigits O 6.5.2.59 i
27
DMH_AlternateBillingDigits O 6.5.2.60 i
28
29 DMH_BillingDigits O 6.5.2.61 i
30
DMH_ChargeInformation O 6.5.2.eo i, j
31
32 DMH_RedirectionIndicator O 6.5.2.62 i, k
33
DMH_ServiceID O 6.5.2.ei l
34
35 GeographicPosition O 6.5.2.fk i, w
36
GroupInformation O 6.5.2.69 m
37
38 MobileDirectoryNumber O 6.5.2.80 i
39 NoAnswerTime O 6.5.2.87 n
40
41
OneTimeFeatureIndicator O 6.5.2.88 o
42 PilotNumber O 6.5.2.95 m
43
PreferredLanguageIndicator O 6.5.2.96 g, p
44
45 RedirectingNumberDigits O 6.5.2.107 f
46
RedirectingNumberString O 6.5.2.108 d
47
48 RedirectingSubaddress O 6.5.2.109 d, e
49
ResumePIC O 6.5.2.cu q
50
51 RoutingDigits O 6.5.2.114 g
52
TerminationList O 6.5.2.156 r
53
54 TerminationTriggers O 6.5.2.57 s
55 TriggerAddressList O 6.5.2.de t
56
57
58
59
60

X.S0009
Notes: 1
2
5
6
c. Include if one or more tones or announcements are to be applied to the MS. 7

8
d. Include if a LocalTermination parameter is included in the TerminationList parameter. 9
10
e. Include if the related feature is active. 11
12
f. Include if a PSTNTermination parameter or an IntersystemTermination parameter is
13
included within the TerminationList parameter.
14
g. Include if applicable. 15
16
h. Include if digits remain to be translated by the MSC. 17
18
i. Include if available for recording purposes (see DMH).
19
j. Include to indicate charge information for the call. 20

21
k. Include if redirection may apply. 22
23
l. Include for recording purposes if a WIN service was invoked. 24
25
m. Include for multi-leg calls.
26
n. Include to request an override of the Serving MSC’s default No Answer Time value. 27
28
o. Include if modification to normal feature processing is required for the call in progress. 29
30
p. This parameter may only be included if the AnnouncementList parameter is present. 31
32
q. Include to indicate the PIC where call processing is to resume.
33
r. Include if call routing is required. 34
35
s. Include to indicate processing in the Originating MSC for failed call attempts. 36
37
t. Include to indicate address associated with active WIN triggers.
38
u. Include if a LocalTermination parameter is included in the TerminationList parameter 39
and display text shall be presented to the called MS. 40

41
v. Include if the ActionCode parameter is included and is set to indicate that display text 42
shall be presented to the calling MS. 43
44
w. Include to specify the geographic position of the MS. 45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
1 6.4.2.37 RegistrationNotification
2
(See TIA/EIA-41.3, page 3-118)
3
4 The RegistrationNotification (REGNOT) operation is used to report the location of an MS and,
5 optionally, to (a) validate the MS or (b) validate the MS and obtain its profile information. It is
6 also used for delivering the Serving MSC’s routing address to the Desired OTAF in support of
7 TDMA OTASP. It is also used to notify an SCF network entity of an MS registration event when
8 Registration Reporting is active at the HLR for the MS.
9
10 The following table lists the possible combinations of invoking and responding NEs.
11
12 INVOKING NE RESPONDING NE
13
14
Case 1 Serving (or Bordering) Serving (or Bordering)
MSC VLR
15
16
Case 2 Serving (or Bordering) HLR
17 VLR
18
19 Case 3 HLR SCP or SN
20
21
22
23
24 The remainder of this section is retained unchanged.
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
6.4.2.h ServiceRequest 1
2
(See IS-826, page 5-15)
3
4
The ServiceRequest (SERVREQ) operation is used by service logic to invoke specific service 5
logic execution on another network entity (NE) containing the service logic for the requested 6
services. 7
8
The following table lists the valid combinations of invoking and responding NEs. 9
10
12
Case 1 HLR SCP or SN 13
14
Case 2 SCP or SN SCP or SN
15
Case 3 SCP or SN HLR 16

17
18
The ServiceRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a 19
TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 20
21
ServiceRequest INVOKE Parameters Timer: SVRT 22
23
Field Value Type Reference Notes
24
Identifier SET [NATIONAL 18] M 6.3.2.1 25

26
Length variable octets M 6.3.2.1
27
Contents 28
29
ServiceID M 6.5.2.bz
30
AccessDeniedReason O 6.5.2.1 c, d 31
32
AvailabilityType O 6.5.2.15 c, e
33
BillingID O 6.5.2.16 a, f 34
35
CallingPartyName O 6.5.2.bw a
36
CallingPartyNumberDigits1 O 6.5.2.21 a 37
CallingPartyNumberDigits2 O 6.5.2.22 b 38
39
CallingPartySubaddress O 6.5.2.25 a 40
CarrierDigits O 6.5.2.28 p 41
42
ConditionallyDeniedReason O 6.5.2.48 c, d
43
DataAccessElementList O 6.5.2.cd c 44
45
DestinationDigits O 6.5.2.56 q
46
Digits (Dialed) O 6.5.2.58 a 47
48
DMH_RedirectionIndicator O 6.5.2.62 c
49
DMH_ServiceID O 6.5.2.ei c, r 50
51
ElectronicSerialNumber O 6.5.2.63 c, s
52
ExtendedMSCID O 6.5.2.64 c, t 53
FeatureIndicator O 6.5.2.ej c, u 54
55
GroupInformation O 6.5.2.69 c 56
LegInformation O 6.5.2.75 c 57
58
LocationAreaID O 6.5.2.77 c
59
60

X.S0009
1
MobileDirectoryNumber O 6.5.2.80 c, g
2
3 MobileIdentificationNumber O 6.5.2.81 c
4
MobilePositionCapability O 6.5.2.fm c, y
5
6 MPCAddress O 6.5.2.ha z, ab, ac
7
MPCAddressList O 6.5.2.hm aa, ab, ac
8
9 MSCID (Invoking) O 6.5.2.82 c, h
10
MSCIN (Invoking) O 6.5.2.83 c, i
11
12 MSID O 6.5.2.bv c, g
13 PC_SSN O 6.5.2.93 i, j
14
15
PilotBillingID O 6.5.2.94 c
16 PilotNumber O 6.5.2.95 c
17
PreferredLanguageIndicator O 6.5.2.96 a
18
19 RedirectingPartyName O 6.5.2.by a
20
RedirectingNumberDigits O 6.5.2.107 a
21
22 RedirectingSubaddress O 6.5.2.109 a
23
RedirectionReason O 6.5.2.110 a, c
24
25 RoutingDigits O 6.5.2.114 v
26
SenderIdentificationNumber O 6.5.2.116 k
27
28 ServingCellID O 6.5.2.117 c
29 SystemMyTypeCode O 6.5.2.147 l
30
31
TerminationAccessType O 6.5.2.155 c
32 TimeDateOffset O 6.5.2.dd c, w
33
TimeofDay O 6.5.2.em c, x
34
35 TransactionCapability O 6.5.2.160 m
36
TriggerType O 6.5.2.dh n
37
38 WINCapability O 6.5.2.di o
39
40 Notes:
41 a. Include if available.
42
43 b. Include if user provided, passed screening calling party number is available.
44
45
c. Include if applicable.
46
d. Include if a RoutingRequest operation was completed prior to the ServiceRequest
47
operation, and access was denied.
48
49 e. Include when MS is predictably unavailable for Call Delivery (e.g., slotted mode or
50 sleep mode).
51
52 f. Include to correlate service usage with call instance
53
54
g. Include if the MSID is available and is not the same as the Digits (Dialed).
55
h. Include to identify invoking MSC.
56
57 i. Include if SS7 is used.
58
59 j. Not for international applications.
60

X.S0009
k. Include to identify invoking FE. 1

2
l. Include to indicate the vendor type of the invoking FE. 3
4
m. Include to indicate the capabilities of the MSC that the invoking FE (e.g., HLR, SCP, 5
SN) chooses to convey to the NE (e.g., SCP, SN) with the service logic for the 6
requested services. 7
8
n. Include to identify the trigger encountered by the MSC.
9
o. Include to indicate the WIN capabilities supported 10

11
p. Include to identify the interexchange carrier for call routing. 12
13
q. Include to identify the network address of the called party for call routing. 14
15
r. Include to identify the Service Logic Program invoked on behalf of the MS.
16
s. Include to identify the MS. 17
18
t. Include to identify the MSC serving the MS if not indicated by the MSCID parameter. 19
20
u. Include to identify a feature invoked for the call (e.g., Three-Way Calling).
21
v. Include to identify special routing information for call routing. 22

23
w. Include to indicate the time offset of Local Civil Time with respect to Coordinated 24
Universal Time (UTC). 25
26
x. Include to indicate the time of day in UTC. 27
28
y. Include to identify the MS’s position capabilities.
29
z. Include if applicable, to specify the network address of the MPC associated with the 30
Serving MSC when there is a single form of the network address for the MPC. 31
32
aa. Include if applicable, to specify the list of addresses for the MPC associated with the 33
Serving MSC when there is more than one form of network address for the MPC. 34
35
ab. These parameters are mutually exclusive. 36
37
ac. See TIA-881.
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
1 6.4.2.i AnalyzedInformation
2
(See IS-848, page 5-12)
3
(See IS-771, page 5-34)
4
5 The AnalyzedInformation (ANLYZD) operation is used by the MSC to provide notification to
6 a service logic network element (e.g., SCP, SN) that a trigger criteria at the
7 Analyzed_Information DP has been satisfied. Service logic may then invoke a service or
8 services.
9
11
13
14
Case 1 MSC SCP
15
Case 2 MSC SN
16
17
18 The AnalyzedInformation operation is initiated with a TCAP INVOKE (LAST). This is carried
19 by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows
20
21
AnalyzedInformation INVOKE Parameters Timer: ANZT
22
24
25
27
Contents
28
29 BillingID (Originating) M 6.5.2.16 a
30
Digits (Dialed) M 6.5.2.58
31
32 MSCID (Originating) M 6.5.2.82 b
33 TransactionCapability M 6.5.2.160
34
35
TriggerType M 6.5.2.dh c
36 WINCapability M 6.5.2.di d
37
CallingPartyName O 6.2.5.bw e, m
38
39 CallingPartyNumberDigits1 O 6.5.2.21 e
40
CallingPartyNumberDigits2 O 6.5.2.22 e
41
42 CallingPartySubaddress O 6.5.2.25 e
43
CarrierDigits O 6.5.2.ep n, o
44
45 ConferenceCallingIndicator O 6.5.2.49 f
46
DestinationDigits O 6.5.2.56 n, p
47
48 DMH_BillingIndicator O 6.5.2.ep y
49 DMH_RedirectionIndicator O 6.5.2.62 q
50
51
ElectronicSerialNumber O 6.5.2.63 g, r
52 FeatureIndicator O 6.5.2.ej s
53
ExtendedMSCID O 6.5.2.64 z
54
55 LocationAreaID O 6.5.2.77 h, t
56
MobileDirectoryNumber O 6.5.2.80 i
57
58 MSCIdentificationNumber O 6.5.2.83 j
59
60

X.S0009
1
MSID O 6.5.2.bv g, r
2
OneTimeFeatureIndicator O 6.5.2.88 k 3
4
PreferredLanguageIndicator O 6.5.2.96
5
RedirectingNumberDigits O 6.5.2.107 e 6
7
RedirectingPartyName O 6.5.2.by b, m
8
RedirectingSubaddress O 6.5.2.109 e 9
10
Routing Digits O 6.5.2.114 n, u
11
ServingCellID O 6.5.2.117 h, v 12
SystemMyTypeCode O 6.5.2.147 13
14
TerminationAccessType O 6.5.2.155 l 15
TimeDateOffset O 6.5.2.dd w 16
17
TimeOfDay O 6.5.2.em x
18
19
Notes:
20
a. Include to identify the call. 21
22
b. Include to identify the requesting MSC. 23
24
c. Include to identify the trigger encountered.
25
d. Include to identify the WIN capabilities supported. 26
27
e. Include if available (i.e., provided in call origination). 28
29
f. Include to indicate the number of conferees already in the call.
30
g. Include to identify the MS. 31

32
h. Include if available (information related to MS origination). 33
34
i. Include if available for recording purposes (see DMH). 35
36
j. Include to identify the MSC sending the message, if the MSC is capable of accepting
37
digits in the international format.
38
k. Include if any OneTimeFeatureIndicator status bits are set (i.e., have value of 1). 39
40
l. Include if call involves a special access situation (e.g., Roamer port access). 41
42
m. Include as the service key, if applicable 43
44
n. Include if applicable and a routing address is available.
45
o. Include to identify the interexchange carrier for call routing. 46
47
p. Include to identify the network address of the called party for call routing. 48
49
q. Include to identify the reason for extending the call.
50
r. Include if available. 51
52
s. Include to identify a feature invoked for the call (e.g. Three Way Calling).l 53
54
t. Include if current location area information is available. 55
56
u. Include to identify special routing information for call routing.
57
v. Include if the current serving cell identity is available. 58

59
60

X.S0009
1 w. Include to indicate the time offset of Local Civil Time with respect to Coordinated
2 Universal Time (UTC).
3
4 x. Include to indicate the time of day (UTC).
5
6
y. Include to indicate the type of special billing to be applied for this call (e.g. Freephone
7
call, Third Party charging).
8
z. Include if available to identify the MSC serving the MS for call delivery
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
The AnalyzedInformation operation success is reported with a TCAP RETURN RESULT 1
(LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as 2
follows: 3
4
5
AnalyzedInformation RETURN RESULT Parameters
6
Field Value Type Reference Notes 7
8
9
Length variable octets M 6.3.2.2 10
11
Contents
12
AccessDeniedReason O 6.5.2.1 a 13
14
ActionCode O 6.5.2.2 b
15
AlertCode O 6.5.2.3 p 16
AnnouncementList O 6.5.2.6 c 17
18
CarrierDigits O 6.5.2.28 d 19
ConferenceCallingIndicator O 6.5.2.49 e 20
21
Digits (Dialed) O 6.5.2.58 f
22
DisplayText O 6.5.2.bx d, m 23
24
DMH_AccountCodeDigits O 6.5.2.59 g
25
DMH_AlternateBillingDigits O 6.5.2.60 g 26
27
DMH_BillingDigits O 6.5.2.61 g
28
DMH_BillingIndicator O 6.5.2.ep g, q 29
30
DMH_ChargeInformation O 6.5.2.eo g, r
31
DMH_RedirectionIndicator O 6.5.2.62 g, h 32
DMH_ServiceID O 6.5.2.ei n 33
34
GeographicPosition O 6.5.2.fk s, t 35
NoAnswerTime O 6.5.2.87 i 36
37
OneTimeFeatureIndicator O 6.5.2.88 j
38
RedirectingNumberDigits O 6.5.2.107 d 39
40
ResumePIC O 6.5.2.cu k
41
RoutingDigits O 6.5.2.114 d 42
43
TerminationList O 6.5.2.156 l
44
TerminationTriggers O 6.5.2.159 d 45
46
TriggerAddressList O 6.5.2.de d, o
47
Notes: 48
49
52
53
c. Include if one or more tones or announcements are to be applied to the MS. 54

55
d. Include if applicable. 56
57
e. Include to direct that ongoing call be transformed into a Conference Call. 58
59
60

X.S0009
1 f. Include if digits remain to be translated by the MSC.

2
3 g. Include if available for recording purposes (see DMH).
4
5
h. Include if redirection may apply.
6
i. Include to request an override of the Serving MSC's default No Answer Time value.
7
8 j. Include if modification to normal feature processing is required for the call in progress.
9
10 k. Include to indicate the PIC where call processing is to resume.
11
12
l. Include if call routing is required.
13
m. Refer to IS-764.
14
15 n. Include for recording purposes if a WIN service was invoked.
16
17 o. Include to indicate address associated with active WIN triggers.
18
p. Include to specify special alerting treatment.
19
20 q. Include to indicate the type of billing to be applied for the call.
21
22 r. Include to indicate the charge information for the call.
23
24
s. Include to specify the geographic position of the MS.
25
t. Include if applicable for recording purposes (see DMH).
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
6.4.2.z CallControlDirective 1
2
(See IS-848, page 5-19)
3
The CallControlDirective (CCDIR) operation is used during call processing to control MSC 4
operation for the indicated call. 5

6
The CallControlDirective operation is initiated with a TCAP INVOKE (LAST). This is carried 7
by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 8
9
CallControlDirective INVOKE Parameters Timer: CCDT 10
11
12
Identifier SET [NATIONAL 18] M 6.3.2.1 13

14
15
Contents 16
17
BillingID M 6.5.2.16 a
18
MSCID M 6.5.2.82 b 19
20
MSID M 6.5.2.bv
21
ActionCode O 6.5.2.2 d 22
23
AnnouncementList O 6.5.2.6 e
24
DisplayText O 6.5.2.bx f 25
DMH_AccountCodeDigits O 6.5.2.59 g 26
27
DMH_AlternateBillingDigits O 6.5.2.60 g 28
DMH_BillingDigits O 6.5.2.61 g 29
30
DMH_ChargeInformation O 6.5.2.eo g, o
31
DMH_RedirectionIndicator O 6.5.2.62 g, h 32
33
ElectronicSerialNumber O 6.5.2.63 i, j
34
GeographicPosition O 6.5.2.fk g, p 35
36
MobileDirectoryNumber O 6.5.2.80 k
37
PreferredLanguageIndicator O 6.5.2.96 l, m 38
39
TerminationList O 6.5.2.156 h
40
TriggerAddressList O 6.5.2.de n 41
42
Notes: 43
a. Include to identify the call 44

45
b. Include to identify the initiating network entity 46
47
c. Include to identify the subscriber. 48
49
d. Include if action to be performed is not implied through presence of other parameters
50
e. Include if provision of one or more tones or announcements is required 51
52
f. Include if display information is to be presented to the MS. 53
54
g. Include if applicable and for recording purposes (see DMH),
55
h. Include if call routing is required (for further study). 56

57
i. Include if available. 58
59
60

X.S0009
1 j. Include to identify the MS.

2
3 k. Include if available for recording purposes (see DMH).
4
5
l. Include if applicable.
6
m. This parameter may only be included if the AnnouncementList parameter is present.
7
8 n. The use of this parameter is for further study.
9
10 o. Include to indicate charge information for the call.
11
12
p. Include to specify the geographic position of the MS.
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
6.4.2.an InterSystemPositionRequest 1
2
(See TIA-881, page 141)
3
The InterSystemPositionRequest (ISPOSREQ) operation is used to request MS position 4
information between network elements. This message may also be used to ascertain an MS’s 5
cell, sector, channel and TMSI information. 6

7
9
INVOKING NE RESPONDING NE INTERFACE 10

11
Case 1 MPC MSC E3 12
13
Case 2 MSC MPC E3 14
15
Case 3 PDE MSC E12 16
17
Case 4 PDE MPC E5
18
19
Case 5 External LCS Client MPC L1
20
21
Case 6 MPC MPC L3
22
Case 7 SCP MPC L4 23

24
Case 8 SN MPC L4 25
26
Case 9 HLR MPC (Home) L2 27
28
29
There are several possible results returned, as: 30
31
a. Requested position information (e.g., initial, current, last). 32
33
b. Mobile channel information is returned, when the responding MSC is serving the MS. 34
35
c. Reason for the requested information not being returned.
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
1 The InterSystemPositionRequest operation is initiated with a TCAP INVOKE (LAST). This is

2
carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as
3
follows:
4
5
InterSystemPositionRequest INVOKE Parameters Timer: IPRT
6
8
9
11
Contents
12
13 PositionRequestType M 6.5.2.fs
14
ActionCode O 6.5.2.2 o
15
16 CDMAPSMMCount O 6.5.2.gb h
17
Digits (Dialed) O 6.5.2.58 j
18
19 ElectronicSerialNumber O 6.5.2.63 d
20
EmergencyServicesRoutingDigits O 6.5.2.bs d, f
21
22 IMSI O 6.5.2.bu d
23 LCSBillingID O 6.5.2.gx k
24
25
LIRAuthorization O 6.5.2.gy l
26 LCS_Client_ID O 6.5.2.go d
27
MobileDirectoryNumber O 6.5.2.80 d
28
29 MobileIdentificationNumber O 6.5.2.81 d
30
MobInfo_AMPS **Macro** O 6.5.2.fn b, p
31
32 Mobinfo_CDMA **Macro** O 6.5.2.fo a, p
33
Mobinfo_NAMPS **Macro** O 6.5.2.fp c, p
34
35 Mobinfo_TDMA **Macro** O 6.5.2.fq g, p
36
MobilePositionCapability O 6.5.2.fm e
37
38 MPCAddress O 6.5.2.ha s, u
39 MPCAddressList O 6.5.2.hm t, u
40
41
MPCID O 6.5.2.hb m
42 MSCID (Serving) O 6.5.2.82 q
43
NetworkTMSI O 6.5.2.bl d
44
45 PC_SSN (Serving MSC) O 6.5.2.93 r
46
PositionQualityOfService O 6.5.2.hc n
47
48 ServingCellID O 6.5.2.117 p, v
49
TDMA_MAHORequest O 6.5.2.gu i
50
51
Notes:
52
53 a. Include if an CDMA channel is in use.
54
55
b. Include if an AMPS channel is in use.
56
c. Include if an NAMPS channel is in use.
57
58
d. Include if known.
59
60

X.S0009
e. Include if known to identify the MS’s position capabilities. If not received, the Serving 1
2
MPC may use local procedures to determine the Target MS position.
3
f. Include for an emergency services call when the initiating entity is an MSC. 4
5
g. Include if a TDMA channel is in use. 6
7
h. Include if the MSC should collect Pilot Strength Measurements from the MS. 8
9
i. Include if the MSC should collect TDMA MAHO Measurements from the MS. 10
11
j. For Value Added Services, include if the geographic position request is call-related
12
and validation that the dialed digits have the expected value is requested.
13
14
k. For Value Added Services, an MPC shall include the LCSBillingID it assigned for the
15
geographic position request. Other network elements shall include a value received;
16
otherwise they shall not include this parameter.
17
18
l. For Value Added Services, include from Serving MPC to Serving MSC to indicate that
19
the MSC must verify that the Target MS LIR mode permits position determination for
20
this LIR authorization type1. The absence of this parameter indicates the LCS Client 21
is authorized for the position information request. 22
23
m. For Value Added Services, include to identify the MPC that originally initiated the
24
position request.
25
n. For Value Added Services, include to indicate the requested Position Quality of 26
Service. 27
28
o. For Value Added Services, include if action to be performed is not implied through 29
presence of other parameters. 30
31
p. Include when the initiating entity is an MSC.
32
q. Include for Case 2. Include if known for Cases 6, 7 and 8. 33

34
r. Include if available for Case 6. 35
36
s. For Value Added Services, include if available for Case 9 to specify the network 37
address of the VAS MPC associated with the Serving MSC when there is a single form 38
of network address for the MPC. 39
40
t. For Value Added Services, include if available for Case 9 to specify the list of
41
addresses for the VAS MPC associated with the Serving MSC when there is more than
42
one form of network address for the MPC.
43
u. These parameters are mutually exclusive. 44

45
v. Include if available for Cases 7 and 8 to relay the value received from the Serving 46
MSC. 47
48
49
50
51
52
53
54
55
56
1 The Serving MPC includes the LIRAuthorization parameter when it does not have the Target MS LIR Mode in- 57
formation and the request for position information was not received from an authorized entity (e.g., the Home 58
MPC for the Target MS). 59

60

X.S0009
1 The InterSystemPositionRequest operation success is reported with a TCAP RETURN

2 RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is
3 encoded as follows:
4
5
InterSystemPositionRequest RETURN RESULT Parameters
6
8
9
11
Contents
12
13 PositionResult M 6.5.2.ft
14
LCSBillingID O 6.5.2.gx i
15
16 MobilePositionCapability O 6.5.2.fm e
17 MobInfo_AMPS **Macro** O 6.5.2.fn c, e
18
19
MobInfo_CDMA **Macro** O 6.5.2.fo b, e
20 MobInfo_NAMPS **Macro** O 6.5.2.fp g, e
21
MobInfo_TDMA **Macro** O 6.5.2.fq a, e
22
23 MSCID (Serving) O 6.5.2.82 f
24
PositionInformation O 6.5.2.fr h
25
26 ServingCellID O 6.5.2.117 d
27
28 Notes:
29
a. Include if a TDMA channel is in use.
30
31 b. Include if a CDMA channel is in use.
32
33 c. Include if an AMPS channel is in use.
34
35 d. Include if known when the responding entity is an MSC.
36
37
e. Include if known when the responding entity is the Serving MSC. Include information
38
for the current operating mode of the MS.
39
f. Include to identify the Serving MSC.
40
41
g. Include if an NAMPS channel is in use.
42
43 h. Include if known.
44
45 i. For Value Added Services, an MPC shall include the LCS Billing ID it assigned for
46 this geographic position request. Other network entities shall include a value received
47 from an associated RETURN RESULT; otherwise they shall not include this
48 parameter.
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
6.4.2.au LCSParameterRequest 1
2
(See TIA-881, Section 5)
3
The LCSParameterRequest (LPREQ) operation is used to request information from an HLR that 4
is necessary to obtain the position of an MS, most notably the network address of the Serving 5
Value Added Services MPC. The response from the HLR may also indicate that the MS is not 6
available for positioning services. 7

8
10
12
Case 1 Home MPC HLR 13
14
Case 2 SCP or SN HLR
15
16
The LCSParameterRequest operation is initiated with a TCAP INVOKE (LAST). This is carried 17
by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 18
19
20
LCSParameterRequest INVOKE Parameters Timer: LPRT
21
23
24
Length variable octets M 6.3.2.1 25
26
Contents
27
MPCID O 6.5.2.hb a 28
29
MSCID O 6.5.2.82 c
30
MobileDirectoryNumber O 6.5.2.80 b 31
MSID O 6.5.2.bv b 32
33
Notes: 34
35
a. Include to identify the MPC initiating the request. 36
37
b. One of these mutually exclusive parameters must be present to identify the Target MS.
38
c. Include to identify the SCF network entity initiating the request. 39
40
41
The remainder of this section is retained unchanged. 42

43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
1 6.4.2.av StatusNotificationRequest
2
(New for TIA/EIA-41.5-D, Section 6)
3
4 The StatusNotificationRequest (STATNOTREQ) operation is used to request HLR notification
5 of a change in the mobility status of the MS.
6
8
10
11 Case 1 SCP or SN HLR
12
13
The StatusNotificationRequest operation is initiated with a TCAP INVOKE (LAST). This is
14
carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as
15
follows:
16
17
StatusNotificationRequest INVOKE Parameters Timer: SNRT
18
20
21 Identifier SET [NATIONAL 18] M 6.3.2.1
23
24
Contents
25 MSCID M 6.5.2.82 a
26
DestinationAddress O 6.5.2.ck b
27
28 MobileDirectoryNumber O 6.5.2.80 c
29
MSID O 6.5.2.bv c
30
31 RegistrationReport O 6.5.2.gw d
32
33 Notes:
34
a. Include to identify the network entity initiating the request.
35
36 b. Include to identify the address of the network entity to receive registration status
37 reports.
38
39 c. One of these mutually exclusive parameters must be present to identify the MS.
40
d. Include to request changes to registration status reported by the HLR.
41
42
43 The StatusNotificationRequest operation success is reported with a TCAP RETURN RESULT
44 (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as
45 follows:
46
47 StatusNotificationRequest RETURN RESULT Parameters
48
49
50 Identifier SET [NATIONAL 18] M 6.3.2.2
51
52
53 Contents
54
55
56
57
58
59
60

X.S0009
6.5 Map Parameters 1

2
3
6.5.1 General 4
5
6
6.5.1.1 Parameter Identifiers 7
(See TIA/EIA-41.5-D, page 5-119) 8
9
Table 4 TIA/EIA-41 MAP Parameter Identifiers 10
11
Parameter Identifier Name Parameter Identifier Code Reference 12
13
H G F E D C B A
14
RegistrationReport 1 0 0 1 1 1 1 1 6.5.2.gw 15
16
1 0 0 0 0 0 1 0 17
0 1 1 0 1 1 1 0 18
19
20
6.5.2 Parameter Definitions 21

22
23
6.5.2.gw RegistrationReport 24
(New for TIA/EIA-41-D Chapter 5, Section 6.5.2) 25
26
The RegistrationReport (REGREPORT) parameter activates and deactivates reporting of MS
27
registration and MS inactive status changes to the requesting network entity. 28
29
Identifier RegistrationReport M 6.5.1.2 31
IMPLICIT OCTET STRING 32

33
34
Contents 35
36
H G F E D C B A octet Notes
37
Reserved REG 1 a 38
39
••• n b
40
41
Notes: 42
a. Reserved bits shall be ignored on receipt and set to zero on sending. 43
44
b. Ignore extra octets, if received. Send only defined (or significant) octets. 45
46
47
Registration Reporting (REG) (octet 1 – bit A) 48
49
Decimal Value Meaning 50
51
0 Registration Reporting OFF: The HLR is not requested to report
52
changes in the Registration and Inactive status of the MS to the
53
requesting entity.
54
1 Registration Reporting ON: The HLR is requested to report changes 55
in the Registration and Inactive status of the MS to the requesting entity. 56
57
58
59
60
TIA/EIA-41.5-D Modifications 112 Map Parameters

X.S0009
1
3
4 This section provides the additions and modifications to TIA/EIA-41-D Chapter 6 signaling
5 procedures for Wireless Intelligent Network Capabilities for Location Based Services.
6
7
8 4.14 Feature Request
9
10
11
4.14.1 MSC Detecting Feature Request
12
(See TIA-826, page 149)
13
14 When performing digit analysis of the dialed digits received from the MS, the MSC detects that
15
the dialed digits are a feature control access. It shall perform the following:
16
17 1 Include the BillingID parameter set to identify the current call for billing and redirection
18 purposes.
19
20
2 Include the Digits (Dialed) parameter set to the digits received from the MS.
21 3 Include the ElectronicSerialNumber parameter set to identify the MS.
22
23
4 Include the MobileIdentificationNumber parameter set to identify the MS.
24 5 Include the MSCID parameter set to the identity of the MSC.
25
6 IF any indicator is set in the OneTimeFeatureIndicator parameter:
26
27 6-1 Include the OneTimeFeatureIndicator parameter.
28
7 ENDIF.
29
30 8 Include SenderIdentificationNumber parameter set to the identification number of the
31 MSC.
32
9 Include TransactionCapability parameter set appropriately.
33
34 10 IF known:
35
10-1 Include the MobilePositionCapability parameter set to identify the position
36
determination capability of the MS.
37
38 11 ENDIF.
39
12 IF the subscriber is involved in a conference call:
40
41 12-1 Include the ConferenceCallingIndicator parameter set to the number of conferees
42 currently in the call.
43
13 ENDIF.
44
45 14 Send a FeatureRequest INVOKE to the HLR associated with the MS.
46 15 Start the Feature Request Response Timer (FRRT).
47
48
16 WAIT for Feature Request response:
49 17 WHEN a RETURN RESULT is received:
50
51
17-1 Stop timer (FRRT).
52 17-2 IF the message can be processed:
53
17-2-1 IF the MS is still connected:
54
55 17-2-1-1 IF the AnnouncementList parameter is received:
56
17-2-1-1-1 IF the PreferredLanguageIndicator parameter is received:
57
58 17-2-1-1-1-1 Use the received Preferred Language value as the subscriber's
59 preferred language for playing this announcement list.
60
Feature Request 113 TIA/EIA-41.6-D Modifications

X.S0009
17-2-1-1-2 ENDIF. 1
2
17-2-1-1-3 Execute the “Play All Announcements in the AnnouncementList” task 3
(see 3.2.5). 4
17-2-1-2 ELSEIF the FeatureResult parameter indicates Successful operation: 5

6
17-2-1-2-1 Provide a successful indication to the MS. 7
17-2-1-3 ELSE: 8
9
17-2-1-3-1 Provide an unsuccessful indication to the MS. 10
17-2-1-4 ENDIF. 11
12
17-2-1-5 IF the OneTimeFeatureIndicator parameter is received:
13
17-2-1-5-1 Store the received OneTimeFeatureIndicator parameter. 14
15
17-2-1-6 ENDIF.
16
17-2-1-7 IF the TriggerAddressList parameter is received: 17
18
17-2-1-7-1 If the call is being redirected:
19
17-2-1-7-1-1 Arm the triggers indicated by the TriggerAddressList parameter for 20
the redirected call. 21
22
17-2-1-7-2 ELSE:
23
17-2-1-7-2-1 Disarm any previously armed subscribed WIN triggers for the 24
remainder of the call in progress. 25
26
17-2-1-7-2-2 Arm the triggers indicated by the TriggerAddressList parameter for
27
the remainder of the call in progress.
28
17-2-1-7-3 ENDIF. 29
30
17-2-1-8 ENDIF.
31
17-2-1-9 IF the ConferenceCallingIndicator parameter is received: 32
17-2-1-9-1 Execute the “MSC CC Invocation” task (see 5.10.3). 33

34
17-2-1-10 ENDIF. 35
17-2-1-11 IF an ActionCode parameter is received: 36

37
17-2-1-11-1 Execute the “MSC ActionCode Processing” task (see 3.2.9) 38
17-2-1-12 ENDIF. 39
40
17-2-1-13 IF the MS is in a state capable of routing a call (e.g., after dialing a feature
41
code from an idle state or a call hold state). 42
17-2-1-13-1 IF the TerminationList parameter is received: 43
44
17-2-1-13-1-1 IF WIN triggers remain to be processed at the
45
Collected_Information or the Analyzed_Information DP: 46
17-2-1-13-1-1-1 Return to the calling task. 47
48
17-2-1-13-1-2 ELSE:
49
17-2-1-13-1-2-1 Execute the “MSC Routing Points Of Return” task (see 3.2.6). 50
51
17-2-1-13-1-3 ENDIF.
52
17-2-1-13-2 ENDIF. 53
54
17-2-1-14 ENDIF.
55
17-2-1-15 IF Digits (Dialed) parameter is received: 56
17-2-1-15-1 Set MS dialed digits to the received Digits (Dialed) parameter value. 57
58
17-2-1-15-2 IF the type of digits is unknown: 59
60
TIA/EIA-41.6-D Modifications 114 Feature Request

X.S0009
1 17-2-1-15-2-1 Process the dialed number locally to set the PointOfReturn.

2
3
17-2-1-15-3 ENDIF.
4 17-2-1-15-4 IF WIN triggers remain to be processed at the Collected_Information or
5 the Analyzed_Information DP:
6
7
17-2-1-15-4-1 Return to the calling task.
8 17-2-1-15-5 ENDIF.
9
10
17-2-1-16 ELSE:
11 17-2-1-16-1 Use Digits (Dialed) parameter included in the FeatureRequest INVOKE
12 as MS dialed digits.
13
14
17-2-1-17 ENDIF.
15 17-2-1-18 GOTO AuthorizedSubscriberOrigination (see 3.2.3).
16
17-2-2 ENDIF.
17
18 17-3 ELSE (the message cannot be processed):
19
17-3-1 Execute “Local Recovery Procedures” task (see 3.5.1).
20
21 17-3-2 IF the MS is still connected:
22
17-3-2-0-1 Provide an unsuccessful indication to the MS.
23
24 17-3-3 ENDIF.
25 17-4 ENDIF.
26
27
18 WHEN a RemoteUserInteractionDirective INVOKE is received:
28 18-1 Stop timer (FRRT).
29
30
18-2 Execute the “MSC Remote User Interaction” task (see 4.39.2).
31 18-3 Start the Feature Request Response Timer (FRRT).
32
18-4 Remain in this state.
33
34 19 WHEN a RETURN ERROR or REJECT is received:
35
19-1 Stop timer (FRRT).
36
37 19-2 Execute “Local Recovery Procedures” task (see 3.5.1).
38
19-3 IF the MS is still connected:
39
40 19-3-1 Provide an unsuccessful indication to the MS.
41 19-4 ENDIF.
42
43
20 WHEN the MS disconnects:
44 20-1 Remain in this state (to handle possible call abandons).
45
46
21 WHEN timer (FRRT) expires:
48
21-2 IF the MS is still connected:
49
50 21-2-1 Provide an unsuccessful indication to the MS.
51
21-3 ENDIF.
52
53 22 ENDWAIT.
54
23 Exit this task.
55
56
57
58
59
60
Feature Request 115 TIA/EIA-41.6-D Modifications

X.S0009
4.28 Location Request 1

2
3
4
4.28.2 HLR Receiving LocationRequest INVOKE 5
(see IS-826, page 6-42) 6
7
When an HLR receives a LocationRequest INVOKE, it shall perform the following:1 8
9
1 IF the received message can be processed: 10
1-1 IF the received TriggerType parameter indicates the Mobile_Termination trigger has 11
been encountered AND IF there are WIN triggers required for providing services to 12
the subscriber AND IF the Location trigger is applicable for the call AND IF the 13
14
received WINCapability parameter indicates the triggers are supported:
15
1-1-1 Include the TriggerAddressList parameter set to indicate active triggers for this 16
call the requesting MSC. 17
18
1-1-2 Include all pertinent parameters.
19
1-1-3 Send a RETURN RESULT to the requesting MSC. 20
1-1-4 Exit this task. 21

22
1-2 ELSE (Execute feature incoming call tasks to determine the feature processing and 23
PointOfReturn): 24
2: 25
1-2-1 IF WIN services are required
26
1-2-1-1 Execute the “WIN Service Logic” task (see 6.Y.), as needed. 27
28
1-2-1-2 Include parameters received from the service logic task.
29
1-2-1-3 IF a PointOfReturn shall be set: 30
31
1-2-1-3-1 Set the PointOfReturn.
32
1-2-1-4 ENDIF. 33
1-2-2 ENDIF. 34
35
1-2-3 IF the CallingPartyNumberDigits1 parameter was received: 36
1-2-3-1 IF the received Digits (Dialed) equal the CallingPartyNumberDigits1 (an MS 37
dialed its own directory number): 38

39
1-2-3-1-1 CASE revertive treatment OF: 40
1-2-3-1-2 VMR: 41
42
1-2-3-1-2-1 Execute “HLR VMR Revertive Call Invocation” task (see 5.23.3). 43
1-2-3-1-3 FA: 44
45
1-2-3-1-3-1 Execute “HLR FA Revertive Call Invocation” task (see 5.12.4).
46
1-2-3-1-4 MAH: 47
48
1-2-3-1-4-1 Execute “HLR MAH Revertive Call Invocation” task (see 5.14.5).
49
1-2-3-1-5 DEFAULT: 50
51
1-2-3-1-5-1 Include the AnnouncementCode parameter within the
52
AnnouncementList set to an accessed denied announcement.
53
1-2-3-1-5-2 Set the PointOfReturn to ToneTermination. 54
55
1-2-3-1-6 ENDCASE.
56
1 Note that the feature interaction is per TIA/EIA-664 and may be different in actual implementations. 57
2 WIN services can be invoked at any point in HLR feature processing before the Location Request RETURN 58
RESULT is sent. 59
60
TIA/EIA-41.6-D Modifications 116 Location Request

X.S0009
1 1-2-3-1-7 Send a RETURN RESULT to the requesting MSC.

2
3
1-2-3-1-8 Exit this task.
4 1-2-3-2 ENDIF.
5
6
1-2-4 ENDIF.
7 1-2-5 Set the called or dialed party equal to the received Digits (Dialed) parameter.
8
1-2-6 Execute the “HLR FA Incoming Call Invocation” task (see 5.12.3).
9
10 1-2-7 IF the PointOfReturn is indicated:
11
1-2-7-1 GOTO LocReqPointOfReturn.
12
13 1-2-8 ENDIF.
14
1-2-9 Execute the “HLR MAH Incoming Call Invocation” task (see 5.14.4).
15
17 1-2-10-1 GOTO LocReqPointOfReturn.
18
19
1-2-11 ENDIF.
20 (At this point it can be assumed that a mobile directory number was dialed.)
21
22
1-2-12 Execute the “HLR CFU Incoming Call Invocation” task (see 5.5.5).
24
1-2-13-1 GOTO LocReqPointOfReturn.
25
26 1-2-14 ENDIF.
27
1-2-15 Execute the “HLR SCA Incoming Call Invocation” task (see 5.19.7).
28
30
1-2-16-1 IF the PointOfReturn is Accepted:
31
32 1-2-16-1-1 GOTO Call Accepted.
33 1-2-16-2 ELSE:
34
35
1-2-16-2-1 GOTO LocReqPointOfReturn.
36 1-2-16-3 ENDIF.
37
38
1-2-17 ENDIF.
39 1-2-18 Execute the “HLR PCA Incoming Call Invocation” task (see 5.15.7).
40
1-2-19 IF the PointOfReturn is indicated:
41
42 1-2-19-1 IF the PointOfReturn is Accepted:
43
1-2-19-1-1 GOTO Call Accepted.
44
45 1-2-19-2 ELSE:
46
1-2-19-2-1 GOTO LocReqPointOfReturn.
47
48 1-2-19-3 ENDIF.
49 1-2-20 ENDIF.
50
51
1-3 ENDIF.
52 Call Accepted:
53
54
1-4 Execute the “HLR CFNA Incoming Call Invocation” task (see 5.4.5).
55 1-5 IF the PointOfReturn is indicated:
56
1-5-1 GOTO LocReqPointOfReturn.
57
58 1-6 ENDIF.
59
60
Location Request 117 TIA/EIA-41.6-D Modifications

X.S0009
1-7 Execute the “HLR CFD Incoming Call Invocation” task (see 5.3.5). 1
2
1-8 IF the PointOfReturn is indicated: 3
1-8-1 GOTO LocReqPointOfReturn. 4

5
1-9 ENDIF. 6
1-10 Execute the “HLR DND Incoming Call Invocation” task (see 5.11.3). 7
8
1-11 IF the PointOfReturn is indicated:
9
1-11-1 GOTO LocReqPointOfReturn. 10
11
1-12 ENDIF.
12
(HLR-based features are complete at this point.) 13
14
1-13 IF termination to the MS is authorized:
15
1-13-1 Execute the “HLR CD Incoming Call Invocation” task (see 5.1.3). 16
1-13-2 IF the PointOfReturn is not indicated: 17

18
1-13-2-1 (This is the default treatment for LocationRequests.) 19
1-13-2-2 Include the AnnouncementCode parameter within the AnnouncementList 20
parameter set to Reorder or other appropriate announcement. 21

22
1-13-2-3 Set the PointOfReturn to ToneTermination (this is the default treatment). 23
1-13-3 ENDIF. 24
25
1-14 ELSE (termination to the MS is not authorized: 26
1-14-1 Include the AnnouncementCode parameter in the AnnouncementList parameter 27
set to an appropriate announcement. 28

29
1-14-2 Set the PointOfReturn to ToneTermination. 30
1-15 ENDIF. 31
32
LocReqPointOfReturn (parameters may be included already and the PointOfReturn should be
33
selected by the feature processing tasks): 34
1-16 CASE PointOfReturn OF: 35
36
1-17 ToneTermination:
37
1-17-1 Include the AccessDeniedReason parameter set to the proper value (see the 38
following table). 39
40
1-17-2 Include the MSCID parameter set to the identity of the Originating MSC.
41
1-18 LocalTermination: 42
43
1-18-1 Include the MSCID parameter set to the identity of the Serving MSC.
44
1-18-2 Execute the “HLR CNIP Terminating Call Invocation” task (see 5.8.1). 45
46
1-18-3 IF the a preferred interexchange carrier is applicable:
47
1-18-3-1 Include the Digits (Carrier) parameter set to the MS’s preferred interexchange 48
carrier. 49
50
1-18-4 ENDIF.
51
1-19 IntersystemTermination: 52
1-19-1 Include the MSCID parameter set to the identity of the Serving MSC. 53
54
1-19-2 IF the PC_SSN of the Serving MSC is known: 55
1-19-2-1 Include the PC_SSN parameter as received. 56

57
1-19-3 ENDIF. 58
1-19-4 Execute the “HLR CNIP Redirecting Call Invocation” task (see 5.8.2). 59
60

X.S0009
1 1-19-5 IF the a preferred interexchange carrier is applicable:

2
3
1-19-5-1 Include the Digits (Carrier) parameter set to the MS’s preferred interexchange
4 carrier.
5 1-19-6 ENDIF.
6
7
1-20 PSTNTermination:
8 1-20-1 Include the MSCID parameter set to the identity of the Originating MSC.
9
10
1-20-2 IF selection of interexchange carrier is applicable:
11 1-20-2-1 Include the Digits (Carrier) parameter set to the MS’s preferred interexchange
12 carrier.
13
14
1-20-3 ENDIF.
15 1-20-4 Execute the “HLR CNIP Redirecting Call Invocation” task (see 5.8.2).
16
1-20-5 IF the a preferred interexchange carrier is applicable:
17
18 1-20-5-1 Include the Digits (Carrier) parameter set to the MS’s preferred interexchange
19 carrier.
20
1-20-6 ENDIF.
21
22 1-21 MultipleTermination:
23
1-21-1 IF at least one of the routes on the list is for a LocalTermination:
24
25 1-21-1-1 Execute the “HLR CNIP Terminating Call Invocation” task (see 5.8.1).
26
1-21-2 ENDIF.
27
28 1-21-3 IF at least one of the routes on the list is for a IntersystemTermination or a
29 PSTNTermination:
30
1-21-3-1 Execute the “HLR CNIP Redirecting Call Invocation” task (see 5.8.2).
31
32 1-21-4 ENDIF.
33 1-21-5 IF the a preferred interexchange carrier is applicable:
34
35
1-21-5-1 Include the Digits (Carrier) parameter set to the MS’s preferred interexchange
36 carrier.
37 1-21-6 ENDIF.
38
39
1-22 DEFAULT:
40 1-22-1 Send a RETURN ERROR with Error Code SystemFailure.
41
42
1-22-2 Exit this task.
43 1-23 ENDCASE.
44
1-24 IF the TriggerType parameter received from the requesting MSC indicates the
45
46
Mobile_Termination trigger has been encountered AND IF there are WIN triggers
47
required for providing services for the subscriber AND IF the received WINCapability
48 parameter indicates the triggers are supported:
49 1-24-1 Include the TriggerAddressList parameter set to indicate active triggers for this
50
call.
51
52 1-25 ENDIF.
53 1-26 Send a RETURN RESULT to the requesting MSC.
54
55
2 ELSE (the received message cannot be processed):
56 2-1 Send a RETURN ERROR with a proper Error Code value (see the following table) to
57 the requesting MSC.
58
59
3 ENDIF.
60
Location Request 119 TIA/EIA-41.6-D Modifications

X.S0009
4 Exit this task. 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
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
1
2
4.30 MS Inactive
3
4
5
4.30.X HLR Initiating an MS Inactive
6 (New for TIA/EIA-41.6-D, Section 4.30)
7
When the HLR determines that the MS is inactive or is no longer registered in a serving system
8
9
AND one or more SCF network entities have activated Registration Reporting for the MS, the
10
HLR shall perform the following:
11
1 FOR all SCF network entities that have activated Registration Reporting for the MS:
12
13 1-1 Include the MSID parameter set to the MS identity.
14
1-2 Include the ElectronicSerialNumber set to the MS identity.
15
16 1-3 IF the MS is no longer registered in a serving system:
17
1-3-1 Include the DeregistrationType parameter set to the appropriate deregistration
18
type (this may have been received from the serving system).
19
20 1-4 ENDIF.
21
1-5 Include other applicable parameters.
22
23 1-6 Send an MSInactive INVOKE to the destination address for the SCF network entity.
24 1-7 Start the MS Inactive Timer (MSIT).
25
26
1-8 WAIT for an MS Inactive response:
27 1-9 WHEN a RETURN RESULT is received:
28
29
1-9-1 Stop the timer (MSIT).
30 1-10 WHEN a RETURN ERROR OR REJECT is received:
31
1-10-1 Stop the timer (MSIT).
32
33 1-10-2 Execute the “Local Recovery Procedures” task (see 3.5.1).
34
1-11 WHEN the timer (MSIT) expires:
35
37
1-12 ENDWAIT.
38
39 2 ENDFOR.
40 3 Exit this task.
41
42
43 4.30.Y SCF Receiving an MSInactive INVOKE
44 (New for TIA/EIA-41.6-D, Section 4.30)
45
46 When the SCF receives an MSInactive INVOKE, it shall perform the following:
47
48
1 IF the received message can be processed:
49 1-1 Set the MS’s state to inactive.
50
51
1-2 IF the DeregistrationType parameter is received:
52 1-2-1 Clear the SCF’s serving system information (e.g., Serving MSC MSCID, Serving
53 MPC address information).
54
55
1-3 ENDIF.
56 1-4 Send an empty RETURN RESULT to the HLR.
57
58
59 2-1 Execute the “Local Recovery Procedures” task (see 3.5.1).
60
MS Inactive 121 TIA/EIA-41.6-D Modifications

X.S0009
2-2 Send a RETURN ERROR with the proper Error Code value (see the following table). 1
2
3 ENDIF. 3
4 Exit this task. 4

5
Table 1 SCF MSInactive Response 6

7
Problem Detection and Recommended Response from SCF to HLR 8
9
RETURN ERROR Problem Definition 10
Error Code 11
12
UnrecognizedIMSI The supplied IMSI parameter is not recognized.
13
UnreconizedMIN The supplied MobileIdentificationNumber parameter is not recognized. 14
15
UnrecognizedESN The supplied ElectronicSerialNumber parameter is not recognized.
16
OperationSequenceProblem MS Inactive reporting is not active for the indicated MS. 17
18
The requested MAP operation is recognized, but not supported by the receiving entity, or
OperationNotSupported 19
the requesting HLR is not authorized. 20
MissingParameter An expected, or required, optional parameter was not received. 21

22
ParameterError A supplied parameter has an encoding problem. 23
24
A required resource (e.g., data base access, functional entity) is not presently accessible
SystemFailure 25
due to a failure. Human intervention may be required for resolution.
26
UnrecognizedParameterValue A supplied parameter value is unrecognized or has non-standard value. 27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41.6-D Modifications 122 MS Inactive

X.S0009
1
2
4.31 Origination Request
3
4
5
4.31.1 MSC Initiating an Origination Request
6 (See TIA-826, page 154)
7
When the MSC determines that an active origination trigger has been encountered requiring call
8
9
processing to be suspended while the HLR or another network entity must performs digit
10
analysis (for other than a feature code) or otherwise executes service logic, and that trigger
11 criteria have been met, it shall perform the following:
12
13
1 Include the BillingID (Originating) parameter set to the billing identifier for the call
14
assigned by the current Originating MSC.
15 2 Include the Digits (Dialed) parameter set to the digits received from the MS.
16
17
3 Include the ElectronicSerialNumber parameter set to identify the originating MS.
18 4 Include the MobileIdentificationNumber parameter set to identify the originating MS.
19
5 Include the MSCID parameter set to the identity of the Originating MSC.
20
21 6 Include the TransactionCapability parameter set to identify the current capabilities.
22
7 Include the WINCapability parameter set to identify the current TriggerCapability and the
23
current WINOperationsCapability.
24
25 8 IF the trigger that was encountered was armed by the TriggerAddressList parameter (a
26 WIN trigger was encountered):
27
8-1 Include the TriggerType parameter set to identify the trigger that was encountered.
28
29 8-2 Include the OriginationTriggers parameter set to indicate that no trigger was
30 encountered.
31
8-3 IF there is a Value Added Services (VAS) MPC associated with this MSC:
32
33 8-3-1 IF known:
34
8-3-1-1 Include the MobilePositionCapability parameter set to identify the position
35
determination capability of the MS.
36
37 8-3-2 ENDIF.
38
8-3-3 IF the MSC is currently serving the MS:
39
40 8-3-3-1 Include the applicable parameters defined in the technology specific Mobinfo
41 macros.
42
8-3-3-2 Include the ServingCellID parameter set to the cell currently serving the MS.
43
44 8-3-4 ENDIF.
45
8-3-5 IF there is a single form of the network address for the MPC:
46
47 8-3-5-1 Include the MPCAddress parameter set to the network address of the MPC.
48 8-3-6 ELSE (there are multiple forms of the MPC address):
49
50
8-3-6-1 Include the MPCAddressList parameter set to the list of network addresses
51 for the MPC.
52 8-3-7 ENDIF.
53
54
8-4 ENDIF.
55 8-5 Include other applicable parameters.
56
57
8-6 Send an OriginationRequest INVOKE to the service logic host address obtained from
58
the TriggerAddressList for the trigger that was encountered.
59 9 ELSE (the trigger that was encountered was armed by the OriginationTriggers parameter):
60
Origination Request 123 TIA/EIA-41.6-D Modifications

X.S0009
9-1 Include the OriginationTriggers parameter set to identify the triggering event. 1
2
9-2 Include other applicable parameters. 3
9-3 Send an OriginationRequest INVOKE to the MS's associated HLR. 4

5
10 ENDIF. 6
11 Start the Origination Request Timer (ORT). 7
8
12 WAIT for Origination Request response:
9
13 WHEN a RETURN RESULT is received: 10
11
Origination Request RETURN RESULT Treatment:
12
13-1 Stop timer (ORT), if it is running. 13
14
13-2 IF the message can be processed:
15
13-2-1 IF the incoming call is still connected: 16
13-2-1-1 IF the AnnouncementList parameter is received: 17

18
13-2-1-1-1 IF the PreferredLanguageIndicator parameter is received: 19
13-2-1-1-1-1 Use the received Preferred Language value as the subscriber's 20
preferred language for playing this announcement list. 21

22
13-2-1-1-2 ENDIF. 23
13-2-1-1-3 Execute the “Play All Announcements in the AnnouncementList” task 24
(see 3.2.5). 25
26
13-2-1-2 ENDIF. 27
13-2-1-3 IF the TriggerAddressList parameter is received: 28

29
13-2-1-3-1 If the call is being redirected: 30
13-2-1-3-1-1 Arm the triggers indicated by the received TriggerAddressList 31
parameter for the redirected call. 32

33
13-2-1-3-2 ELSE: 34
13-2-1-3-2-1 Disarm any previously armed subscribed WIN triggers for the 35
remainder of the call in progress. 36

37
13-2-1-3-2-2 Arm the triggers indicated by the received TriggerAddressList 38
parameter for the remainder of the call in progress. 39
13-2-1-3-3 ENDIF. 40
41
13-2-1-4 ENDIF. 42
13-2-1-5 IF the AccessDeniedReason parameter is received AND IF it can be acted 43
upon: 44
45
13-2-1-5-1 IF the O_Called_Party_Busy trigger is armed for the subscriber: 46
13-2-1-5-1-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X). 47
48
13-2-1-5-1-2 Include the TriggerType parameter set to indicate
49
O_Called_Party_Busy. 50
13-2-1-5-1-3 Include the FailureCause parameter set according to the received 51
AccessDeniedReason parameter value. 52

53
13-2-1-5-1-4 Execute the “MSC Initiating an OCalledPartyBusy” task (see 4.Z.1). 54
13-2-1-5-1-5 Return to the calling task with a successful indication. 55
56
13-2-1-5-2 ENDIF.
57
13-2-1-5-3 IF AnnouncementList parameter is not received: 58
59
60
TIA/EIA-41.6-D Modifications 124 Origination Request

X.S0009
1 13-2-1-5-3-1 Apply the default treatment appropriate for the received AccessDe-
2
niedReason value.
3
4 13-2-1-5-3-2 Return to the calling task.
5 13-2-1-5-4 ENDIF.
6
7
13-2-1-6 ELSEIF the OriginationRequest INVOKE was sent after detecting a non-
8 WIN trigger:
9 13-2-1-6-1 IF neither the TerminationList parameter nor ActionCode parameter nor
10
Digits (Dialed) parameter is received (an error condition?):
11
12 13-2-1-6-1-1 Execute the “Apply Access Denial Treatment” task (see 3.4.5).
13 13-2-1-6-1-2 Return to the calling task.
14
15
13-2-1-6-2 ENDIF.
16 13-2-1-7 ENDIF.
17
18
13-2-1-8 IF the TerminationList parameter is received:
21
22
23 13-2-1-8-2 ENDIF.
24
13-2-1-8-3 Execute the “MSC Routing Points Of Return” task (see 3.2.6).
25
26 13-2-1-9 ENDIF.
27
13-2-1-10 IF the ActionCode parameter is received:
28
29 13-2-1-10-1 Execute the “MSC ActionCode Processing” task (see 3.2.9).
30
13-2-1-11 ENDIF.
31
32 13-2-1-12 IF the Digits (Dialed) parameter is received.
33 13-2-1-12-1 Set the MS dialed digits to the received Digits (Dialed) parameter value.
34
35
13-2-1-12-2 IF the type of digits is unknown:
36 13-2-1-12-2-1 Process the dialed number locally to set the PointOfReturn (this may
37 include local feature code processing).
38
39
13-2-1-12-3 ENDIF:
42
43
44 13-2-1-12-5 ENDIF.
45
46
13-2-1-13 ELSE:
47 13-2-1-13-1 Use the Digits (Dialed) parameter included in the OriginationRequest
48 INVOKE as MS dialed digits.
49
50
13-2-1-14 ENDIF.
51 13-2-1-15 GOTO AuthorizedSubscriberOrigination (see 3.2.3).
52
13-2-2 ELSE (call abandoned):
53
54 13-2-2-1 Execute the “Local Recovery Procedures” task (see 3.5.1).
55
13-2-2-2 Exit this task.
56
57 13-2-3 ENDIF.
58
13-3 ELSE (the message cannot be processed):
59
60

X.S0009
13-3-1 Execute “Local Recovery Procedures” task (see 3.5.1). 1

2
13-4 ENDIF. 4
5
14 WHEN a RemoteUserInteractionDirective INVOKE is received: 6
14-1 Stop timer (ORT). 7
8
14-2 Execute the “MSC Remote User Interaction” task (see 4.39.2).
9
14-3 Start the Origination Request Timer (ORT). 10
11
12
15 WHEN a ConnectResource INVOKE is received: 13
14
15-1 Stop the timer (ORT).
15
15-2 Execute the “MSC Receiving ConnectResource INVOKE” task (see 4.B.3). 16
15-3 CASE MSC Connect Resource result OF: 17

18
15-4 Disconnect Resource received: 19
15-4-1 Start the timer (ORT). 20

21
15-4-2 Remain in this state. 22
15-5 OriginationRequest RETURN RESULT received: 23
24
15-5-1 GOTO OriginationRequest RETURN RESULT Treatment.
25
15-6 SSFT expiration: 26
27
15-6-1 Start the timer (ORT).
28
30
15-7 call abandoned:
31
15-7-1 Execute the “Local Recovery Procedures” task (see 3.5.1). 32

34
15-8 resource disconnect: 35

37
15-9 failure at MSC: 39
40
15-9-1 Start the timer (ORT).
41
43
15-10 message error:
44
46
15-10-2 Remain in this state.
47
15-11 ENDCASE. 48
16 WHEN the MS disconnects: 49

50
16-1 Remain in this state (to handle possible call abandons). 51
17 WHEN a RETURN ERROR or REJECT is received: 52

53
17-1 Stop timer (ORT). 54
17-2 Execute “Local Recovery Procedures” task (see 3.5.1). 55
56
17-3 Provide an unsuccessful indication to the MS.
57
17-4 Exit this task. 58
59
60
TIA/EIA-41.6-D Modifications 126 Origination Request

X.S0009
1 18 WHEN timer (ORT) expires:

2
3
18-1 Execute “Local Recovery Procedures” task (see 3.5.1).
4 18-2 Provide an unsuccessful indication to the MS.
5
6
18-3 Exit this task.
7 19 ENDWAIT.
8
20 Return to the calling task.
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

X.S0009
4.38 Registration Notification 1

2
3
4
4.38.X HLR Initiating a Registration Notification 5
(New for TIA/EIA-41.6-D, Section 4.38) 6
7
When the MS is registered in a new Serving MSC or has become Active (i.e., HLR has received
8
a RegistrationNotification INVOKE from the serving system and the registration status has 9
changed) and one or more SCF network entities have activated Registration Reporting for the 10
MS, the HLR shall perform the following: 11
12
1 FOR all SCF network entities that have activated Registration Reporting for the MS: 13
1-1 Relay the applicable RegistrationNotification INVOKE parameters received from the 14
Serving VLR. 15
16
1-2 Send a RegistrationNotification INVOKE to the destination address for the SCF 17
network entity. 18
1-3 Start the Registration Notification Timer (RNT). 19

20
1-4 WAIT for a Registration Notification response: 21
1-5 WHEN a RETURN RESULT is received: 22
23
1-5-1 Stop the timer (RNT).
24
1-6 WHEN a RETURN ERROR OR REJECT is received: 25
26
1-6-1 Stop the timer (RNT).
27
29
1-7 WHEN the timer (RNT) expires:
30
1-8 ENDWAIT. 32
33
2 ENDFOR. 34
3 Exit this task. 35

36
37
4.38.Y SCF Receiving a RegistrationNotification INVOKE 38
(New for TIA/EIA-41.6-D, Section 4.38) 39

40
When the SCF receives a RegistrationNotification INVOKE, it shall perform the following: 41
42
1 IF the received message can be processed: 43
1-1 Update the current registration information for the MS (e.g., Serving MSC identity, 44
Serving MPC address information). 45

46
1-2 Set the MS status information to indicate the MS is Active. 47
1-3 Send an empty RETURN RESULT to the HLR. 48
49
50
2-1 Execute the “Local Recovery Procedures” task (see 3.5.1). 51
52
2-2 Send a RETURN ERROR with the proper Error Code value (see the following table).
53
3 ENDIF. 54
55
56
57
58
59
60
TIA/EIA-41.6-D Modifications 128 Registration Notification

X.S0009
1 4 Exit this task.

2
3 Table 2 SCF RegistrationNotification Response
4
5 Problem Detection and Recommended Response from SCF to HLR
6
7 RETURN ERROR Problem Definition
8 Error Code
9
UnrecognizedIMSI The supplied IMSI parameter is not recognized.
10
11 UnreconizedMIN The supplied MobileIdentificationNumber parameter is not recognized.
12
13
UnrecognizedESN The supplied ElectronicSerialNumber parameter is not recognized.
14 OperationSequenceProblem Registration Reporting is not active for the indicated MS.
15
16 The requested MAP operation is recognized, but not supported by the receiving entity, or
OperationNotSupported
17 the requesting HLR is not authorized.
18 MissingParameter An expected, or required, optional parameter was not received.
19
20 ParameterError A supplied parameter has an encoding problem.
21
22 SystemFailure
23
24 UnrecognizedParameterValue A supplied parameter value is unrecognized or has non-standard value.
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Registration Notification 129 TIA/EIA-41.6-D Modifications

X.S0009
4.T Call Control Directive 1

2
(See IS-826, page 6-65) 3
4
5
4.T.1 SCF Initiating a Call Control Directive 6
7
When the SCF network entity determines that call processing actions are required for a call
8
being processed by an MSC, it shall perform the following: 9
10
1 Include the BillingID parameter set to identify the call.
11
2 Include the MSCID parameter set to the identity of the SCF network entity. 12
13
3 Include the MSID parameter set to identify the subscriber.
14
4 Include the ElectronicSerialNumber parameter. 15
5 IF a tone or announcement is to be played to the MS or to the party associated with the MS 16

17
(e.g., the called party when the call is forwarded on behalf of the subscriber):
18
5-1 Include the AnnouncementList parameter set to indicate the tone or announcement. 19
6 ENDIF. 20
21
7 IF display text is to be presented to the MS: 22
7-1 Include the DisplayText parameter set to the display text. 23

24
8 ENDIF. 25
9 IF specific MSC call processing action is required: 26
27
9-1 Include the ActionCode parameter set appropriately.
28
10 ENDIF. 29
30
11 IF the MS call shall be redirected:
31
11-1 Include the TerminationList parameter set appropriately. 32
33
12 ENDIF.
34
13 IF DMH parameters are to be recorded by the MSC: 35
13-1 Include the applicable parameters for data recording. 36

37
14 ENDIF. 38
15 Include other applicable parameters. 39

40
16 Send a CallControlDirective to the MSC associated with this call. 41
17 Start the Call Control Directive Timer (CCDT). 42
43
18 WAIT for a Call Control Directive response.
44
46
19-1 Stop the timer (CCDT).
47
19-2 IF the message can be processed: 48
49
19-2-1 IF the requested actions were completed:
50
19-2-1-1 Return to the calling task with a successful indication. 51
19-2-2 ELSE: 52
53
19-2-2-1 Return to the calling task with an unsuccessful indication and the received 54
parameters. 55
19-2-3 ENDIF. 56
57
19-3 ELSE: 58
19-3-1 Execute “Local Recovery Procedures” task (see 3.5.1). 59

60
TIA/EIA-41.6-D Modifications 130 Call Control Directive

X.S0009
1 19-3-2 Return to the calling task with an unsuccessful indication.

2
3
19-4 ENDIF.
4 20 WHEN a RETURN ERROR is received:
5
6
8
20-3 Return to the calling task with an unsuccessful indication.
9
10 21 WHEN a REJECT is received:
11
12
14
15
16 22 WHEN the timer (CCDT) expires:
18
19
20 23 ENDWAIT.
21
22
23 4.T.2 MSC Receiving a CallControlDirective INVOKE
24
25 Upon receipt of a CallControlDirective INVOKE, the MSC shall perform the following:
26
27
1 IF the received message can be processed:
28 1-1 IF call setup is in progress for the call associated with the received BillingID parameter
29 value:
30
31
1-1-1 Include the CallStatus parameter set to indicate Call Setup in Progress.
32 1-1-2 Send a RETURN RESULT.
33
34
1-1-3 Exit this task.
35 1-2 ENDIF.
36
1-3 IF the subscriber indicated by the received MSID parameter is engaged in a locally
37
38
allowed call:
39 1-3-1 Include the CallStatus parameter set to indicate Locally Allowed Call – No Action.
40
1-3-2 Send a RETURN RESULT.
41
42 1-3-3 Exit this task.
43
1-4 ENDIF.
44
45 1-5 IF the AnnouncementList parameter is received:
46
1-5-1 Execute the “Play All Announcements in the AnnouncementList” task (see 3.2.5).
47
48 1-6 ENDIF.
49 1-7 IF the DisplayText parameter is received:
50
51
1-7-1 Send the display text to the MS.
52 1-8 ENDIF.
53
54
1-9 IF DMH parameters are received:
55 1-9-1 Record the received DMH parameters.
56
1-10 ENDIF.
57
58 1-11 Send an empty RETURN RESULT.
59
60
Call Control Directive 131 TIA/EIA-41.6-D Modifications

X.S0009
1-12 IF the ActionCode parameter is received: 1

2
1-12-1 Execute the “MSC ActionCode Processing” task (see 3.2.9). 3
1-12-2 IF the received ActionCode parameter value indicates Release leg and redirect 4
subscriber: 5
6
1-12-2-1 IF the TerminationList parameter is received: 7
1-12-2-1-1 Execute the “MSC Route the Call Leg Externally” task (see 3.3.8). 8
9
1-12-2-2 ELSE: 10
1-12-2-2-1 Execute “Local Recovery Procedures” task (see 3.5.1). 11
12
1-12-2-2-2 Exit this task.
13
1-12-2-3 ENDIF. 14
15
1-13 ENDIF.
16
2 ELSE (the received message cannot be processed). 17
18
2-1 Execute “Local Recovery Procedures” task (see 3.5.1).
19
2-2 Send a RETURN ERROR with the proper Error Code value (see the following table). 20
3 ENDIF. 21
22
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41.6-D Modifications 132 Call Control Directive

X.S0009
1
2
4.Y LCS Parameter Request
3 (See TIA-881, Section 6)
4
5
6
4.Y.2 SCF Initiating an LCS Parameter Request
7 (New for TIA/EIA-41.6-D Section 4)
8
When an SCF network entity determines that the location services parameter information is
9
required, it shall perform the following:
10
11
1 Include the MSCID parameter set to identify the SCF network entity.
12
13 2 Include an MS identity parameter (i.e., MobileDirectoryNumber or
14 MobileIdentificationNumber or IMSI) to identify the Target MS.
15
3 Send an LCSParameterRequest INVOKE to the MS’s HLR.
16
17 4 Start the LCS Parameter Request Timer (LPRT).
18 5 Wait for an LCS Parameter Request response.
19
20
6 WHEN a RETURN RESULT is received:
21 6-1 Stop the timer (LPRT).
22
23
24 6-2-1 Return to the calling task with the received parameters.
25
26
28
6-3-2 Return to the calling task with a failure indication.
29
30 6-4 ENDIF.
31
7 WHEN a RETURN ERROR or REJECT is received:
32
33 7-1 Stop the timer (LPRT).
35
36
7-3 Return to the calling task with a failure indication.
37 8 WHEN the timer (LPRT) expires:
38
39
8-1 Execute the “Local Recovery Procedures” task (see 3.5.1).
40 8-2 Return to the calling task with a failure indication.
41
9 ENDWAIT.
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
LCS Parameter Request 133 TIA/EIA-41.6-D Modifications

X.S0009
4.W InterSystem Position Request 1

2
(See TIA-881, Section 6) 3
4
5
4.W.2 SCF Initiating an InterSystem Position Request 6
(New for TIA/EIA-41.6-D Section 4) 7
8
Upon request, the SCF network entity shall perform the following:
9
1 Include the PositionRequestType parameter set to indicate the type of MS position 10

11
information required.
12
2 Include the LCSClientID parameter to identity the LCS Client. 13
3 Include the PositionQualityOfService parameter set to indicate the requested position 14

15
quality of service as applicable.
16
4 Include other applicable parameters. 17
5 Send an InterSystemPositionRequest INVOKE to the MPC indicated in the request. 18

19
6 Start the InterSystem Position Request Timer (IPRT). 20
7 WAIT for an InterSystem Position Request response: 21

22
8-1 Stop the timer (IPRT). 24
25
26
8-2-1 Return to the calling task with the received parameters. 27
28
29
31
8-3-2 Return to the calling task with a failure indication.
32
8-4 ENDIF. 33
9 WHEN a RETURN ERROR or REJECT is received: 34

35
9-1 Stop the timer (IPRT). 36
9-2 Execute the “Local Recovery Procedures” task (see 3.5.1). 37

38
9-3 Return to the calling task with a failure indication. 39
10 WHEN the timer (IPRT) expires: 40
41
42
10-2 Return to the calling task with a failure indication. 43
44
11 ENDWAIT.
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41.6-D Modifications 134 InterSystem Position Request

X.S0009
1
2
4.FF Status Notification Request
3 (New for TIA/EIA-41.6-D, Section 4)
4
5
6
4.FF.1 SCF Initiating Status Notification Request
7
When an SCF network entity determines that notification of a change in the MS mobility status
8
9
is required, it shall perform the following:
10
1 Include the MSCID parameter set to identify the SCF network entity.
11
12 2 Include an MS identity parameter (i.e., MobileDirectoryNumber or
13 MobileIdentificationNumber or IMSI) to identify the MS.
14
3 IF activation of registration reporting for the MS is required:
15
16 3-1 Include the RegistrationReport parameter set appropriately.
17
3-2 Include the DestinationAddress parameter set to the address of the SCF network entity.
18
19 4 ELSEIF de-activation of registration reporting for the MS is required:
20 4-1 Include the RegistrationReport parameter set appropriately.
21
22
5 ENDIF.
23 6 Send a StatusNotificationRequest INVOKE to the MS’s HLR.
24
25
7 Start the Status Notification Request Timer (SNRT).
26 8 WAIT for a Status Notification Request response.
27
9 WHEN a RETURN RESULT is received:
28
29 9-1 Stop the timer (SNRT).
30
31
32 9-2-1 Return to the calling task with a successful indication and the received parameters.
33
34
36 9-3-2 Return to the calling task with a failure indication.
37
38
9-4 ENDIF.
39 10 WHEN a RETURN ERROR or REJECT is received:
40
41
10-1 Stop the timer (SNRT).
43
10-3 Return to the calling task with a failure indication.
44
45 11 WHEN the timer (SNRT) expires:
46
47
48 11-2 Return to the calling task with a failure indication.
49
12 ENDWAIT.
50
51
52 4.FF.2 HLR Receiving StatusNotificationRequest INVOKE
53
54 When an HLR receives a StatusNotificationRequest INVOKE, it shall perform the following:
55
56 1 IF the received message cannot be processed:
57
1-1 Send a RETURN ERROR with a proper Error Code value (see the following table) to
58
the requesting network entity.
59
60
Status Notification Request 135 TIA/EIA-41.6-D Modifications

X.S0009
1-2 Exit this task. 1

2
2 ENDIF. 3
3 IF the RegistrationReport parameter is received: 4

5
3-1 IF activation of registration reporting for the indicated MS is requested: 6
3-1-1 Activate registration reporting for the MS to the requesting network entity. 7
8
3-1-2 Store the received DestinationAddress parameter information for reporting
9
mobility status changes to the requesting network entity. 10
3-2 ELSE (de-activation of registration reporting is requested): 11
12
3-2-1 De-activate registration reporting for the indicated MS to the requesting network
13
entity. 14
3-2-2 Remove any stored destination address information used to report mobility status 15
changes for the indicated MS to the requesting network entity. 16

17
3-3 ENDIF. 18
20
Table 3 HLR StatusNotificationRequest Response 21
22
Problem Detection and Recommended Response from HLR 23
24
RETURN ERROR Problem Definition 25
Error Code 26
MSID/HLRMismatch The supplied MSID parameter is not in the HLR’s range of MSIDs (suspect routing error). 27
28
ResourceShortage A required HLR resource is temporarily not available (e.g., congestion). 29
The requested MAP operation is recognized but not supported by the HLR, or the 30
OperationNotSupported
requesting entity is not authorized. 31
32
MissingParameter An expected, or required, optional parameter was not received.
33
ParameterError A supplied parameter has an encoding problem. 34
35
SystemFailure 36
37
UnrecognizedParameterValue A supplied parameter value is unrecognized or has non-standard value. 38
39
The supplied MobileDirectoryNumber parameter is not in the HLR’s range of MDNs or
UnrecognizedMDN 40
the supplied MobileDirectoryNumber parameter is not presently assigned to an MS.
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41.6-D Modifications 136 Status Notification Request

X.S0009
1
2
6.Y WIN Service Logic
3 (See IS-848, page 6-71)
4
5 When WIN service logic is invoked, the SCF network entity shall perform the following1:
6
7
1 Execute the WIN service logic program.
8 2 WAIT for completion of WIN service logic execution.
9
10
3 WHEN execution of WIN service logic is complete:
11 3-1 Include applicable parameters.
12
3-2 Return to the calling task.
13
14 4 WHEN data is to be retrieved from an SDF network entity:
15
4-1 Execute the “SCF Initiating a Search” task (see 4.I.1).
16
17 4-2 Remain in this state.
18
5 WHEN data is to be updated in an SDF network entity:
19
20 5-1 Execute the “SCF Initiating a Modify” task (see 4.G.1).
21 5-2 Remain in this state.
22
23
6 WHEN user interaction is required:
24 User interaction required
25
26
6-1 IF an SRF network entity external to the MSC is indicated:
27 6-1-1 Execute “SCF Initiating a Seize Resource” task (see 4.J.1).
28
6-1-2 IF the task was unsuccessful:
29
30 6-1-2-1 Include parameters for default treatment.
31
6-1-2-2 Return to the calling task.
32
33 6-1-3 ELSE (the task was successful):
34
6-1-3-1 Execute the “SCF Initiating Connect Resource” task (see 4.B.1).
35
36 6-1-3-2 IF the task was unsuccessful:
37 6-1-3-2-1 Include parameters for default treatment.
38
39
6-1-3-2-2 Return to the calling task.
40 6-1-3-3 ENDIF.
41
42
6-1-3-4 IF further user interaction is required:
43 6-1-3-4-1 Execute the “SCF Initiating Disconnect Resource” task (see 4.D.1).
44
6-1-3-4-2 GOTO User Interaction Required.
45
46 6-1-3-5 ELSEIF immediate disconnection of the MSC to the SRF network entity is
47 required:
48
6-1-3-5-1 Execute the “SCF Initiating Disconnect Resource” task (see 4.D.1).
49
50 6-1-3-6 ENDIF.
51
6-1-4 ENDIF.
52
53 6-2 ELSE (an SRF network entity external to the MSC is not indicated):
54
6-2-1 Execute “Initiation of Remote User Interaction Directive” task (see 4.39.1).
55
56 6-3 ENDIF.
57
58
1 This procedure identifies interactions with other procedures and may be different than actual
59 implementations.
60
WIN Service Logic 137 TIA/EIA-41.6-D Modifications

X.S0009
6-4 Remain in this state. 1

2
7 WHEN remote service logic execution is required: 3
7-1 Execute “SCF Initiating Service Request” task (see 4.K.1). 4

5
7-2 IF the remote service logic execution is unsuccessful: 6
7-2-1 Include parameters for default treatment. 7
8
7-2-2 Return to the calling task.
9
7-3 ENDIF. 10
11
12
8 WHEN call control intervention is required: 13
14
8-1 Execute the “SCF Initiating a Call Control Directive” task (see 4.T.1)
15
8-2 8-2 Remain in this state. 16
9 WHEN MS location information is required: 17

18
9-1 Execute the “SCF Initiating a Position Request” task (see 4.BB.1) 19

21
10 WHEN MS geoposition information is required: 22
10-1 IF geoposition information is to be obtained from the Serving MPC: 23
24
10-1-1 Set the message destination to the address of the Serving MPC.
25
10-2 ELSE (Obtain the geoposition information from the Home MPC): 26
27
10-2-1 Set the message destination to the address of the Home MPC.
28
10-3 ENDIF. 29
30
10-4 Execute the “SCF Initiating an InterSystem Position Request” task (see 4.W.2).
31
11 WHEN location services parameters are required for the Target MS: 33
34
11-1 Execute the “SCF Initiating an LCS Parameter Request” task (see 4.EE.1) 35

37
12 WHEN mobility status information is required for an MS: 38
12-1 Execute the “SCF Initiating a Status Notification Request” task (see 4.FF.1) 39
40
41
13 ENDWAIT. 42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41.6-D Modifications 138 WIN Service Logic

X.S0009
1
2 7 OPERATION TIMER VALUES
3 (See TIA/EIA-41.6-D, page 6-397)
4 (See IS-764, page 65)
5 (See IS-771, page 6-130)
6
7
The following table provides a summary of the timers used for MAP operations. The timer
8 values specified in this table are default values only and should be optimized for actual operating
9 environments. Some timers are locally defined and are not in this table (e.g., alerting timer, no
10 answer timer, page response timer, maximum interaction timer, interdigit timer).
11
12
Table 63 Operation Timer Values
13
Timer Default Start when Normally stopped when Action when
14
(sec.) timer expires
15
16 ••• ••• ••• ••• •••
17
ANZT 58 16 AnalyzedInformation INVOKE AnalyzedInformation Execute
18
(or a subsequent Remote- RETURN RESULT or Recovery
19
Analyzed UserInteractionDirective RETURN ERROR is Procedures
20 Information Timer RETURN RESULT) is sent, or received, RemoteUser-
21 a subsequent Disconnect- InteractionDirective INVOKE
22 Resource INVOKE is is received, or Connect-
23 received. Resource INVOKE is
24 received.
25
FRRT 58 16 FeatureRequest INVOKE (or FeatureRequest RETURN Execute
26
a subsequent RemoteUser- RESULT, FeatureRequest Recovery
27 (See Note 2) InteractionDirective INVOKE) RETURN ERROR, or a Procedures
28 is sent. RemoteUserInteraction-
29 Feature Request Directive INVOKE is received.
30 Response Timer
31
ORT 58 16 OriginationRequest INVOKE OriginationRequest RETURN Execute
32
(or a subsequent Remote- RESULT, OriginationRequest Recovery
33
Origination UserInteractionDirective RETURN ERROR, or a Procedures
34 Request Timer INVOKE) is sent. RemoteUserInteraction-
35 Directive INVOKE is received.
36
37
SNRT 6 StatusNotificationRequest StatusNotificationRequest Execute
INVOKE is sent RETURN RESULT or recovery
38
Status Notification RETURN ERROR is received procedures
39
Request Timer
40
41 SVRT 58 6 ServiceRequest INVOKE is ServiceRequest RETURN Execute
42 sent RESULT or RETURN recovery
43 Service Request ERROR is received procedures
44
Timer
45 ••• ••• ••• ••• •••
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Operation Timer Values 139 TIA/EIA-41.6-D Modifications

X.S0009
ANNEX A (INFORMATIVE) 1
2
3
The diagram below illustrates the relationship between TIA-881 and this document. TIA-881 4
provides the intersystem extensions to J-STD-036 for wireless network support for location- 5
based services. This document builds on TIA-881 to provide additional capabilities between the 6
SCF and other wireless network elements to enable WIN services to utilize wireless network 7
8
MS position determination capabilities. This diagram illustrates two things:
9
a. How different types of LCS clients can utilize position determination capabilities in 10
the network through WIN SCF, directly to the MPC through a standardized interface, 11
12
and through the internet either to a WIN SCF network entity or directly to the MPC.
13
b. The network interfaces between network elements have been enhanced by TIA-881 14
only, TIA-843 only, or both. 15

16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Annex A (informative) 140

X.S0009
1
2
3
4
SS7 Intersystem Operations Internet
5
6
7
SCP LCS Internet
8
LCS Client client

9
10
WIN-based
11
LCS client
12
13
14
15
16
17
18
19
20
HLR MSC
21
22
PDE
23
24
PDE
25
26
27
28
29 Home MPC Serving MPC
30
31
32
33
34
Intersystem Operation Enhancements
35
36 TIA-881 only
37
38
39
40
TIA-843 only
41
42
43
TIA-881 and TIA-843
44
45
46 TIA-843 only (possible future development)
47
48
49 Neither TIA-881 nor TIA-843
50
51
(May be standardized elsewhere)
52
53
54
55
56
57
58
59
60
141 Annex A (informative)

Wireless Intelligent Network Support For Location Based Services (3GPP2)

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Wireless Intelligent Network Support For Location Based Services (3GPP2)

Hochgeladen von

Copyright:

Verfügbare Formate

3GPP2 X.

Wireless Intelligent Network Support for

1 WIRELESS INTELLIGENT NETWORK SUPPORT FOR LOCATION BASED SERVICES

7.1 Normal Procedures With Successful Outcome.........................................................................22 1

7.3 Alternative Procedures..............................................................................................................24 4

8.1 Fleet and Asset Management (FAM)........................................................................................27 13

8.1.2 FAM Tracking of Target MS .....................................................................................30 18

8.2 Location Based Charging (LBC) ..............................................................................................37 22

8.3.1 Single_Introducing_Star Invocation of LBIS on SCP................................................53 31

8.4.3 Unsuccessful Enhanced Call Routing: LIR Service Denial .......................................71 44

8.5 Non-SIM Registration Reporting..............................................................................................76 48

8.5.4 Activation or Deactivation of Registration Report.....................................................81 53

1 5.1 SS7-Based Data Transfer Services ........................................................................................... 83

6.Y WIN Service Logic .................................................................................................................137 1

Annex A (informative) ........................................................................................................................................140 5

vii Revision History

Revision History viii

• The TIA/EIA-41.1-D Modifications section provides the modifications and additions 4

to TIA/EIA-41-D Chapter 1 “Functional Overview”. 5

to TIA/EIA-41-D Chapter 3 “Automatic Roaming Information Flows”. 8

c. Position information storage is outside the scope of this document. 29

uses the HLR-based profile access defined in TIA/EIA-41. 32

Editorial Conventions 3 Introduction

2.1 Normative References 15

with landline features. 37

Project 2; September 22, 2000 40

Industry Association; December 13, 1999 44

Feature Descriptions 4 References

Deﬁnitions and Concepts 5 Feature Descriptions

4 FLEET AND ASSET MANAGEMENT (FAM) 1

4.1 Normal Procedures With Successful Outcome 42

assigned to a FAM group. 48

Feature Descriptions 6 Fleet and Asset Management (FAM)

Fleet and Asset Management (FAM) 7 Feature Descriptions

FAM Member Invocation 1

Normal Operation with Successful Outcome 6

4.2 Exception Procedures or Unsuccessful Outcome 31

Feature Descriptions 8 Fleet and Asset Management (FAM)

1 Exceptions While Roaming

Fleet and Asset Management (FAM) 9 Feature Descriptions

5 LOCATION BASED CHARGING (LBC) 1

crosses a geographic boundary 25

5.1 Normal Procedures With Successful Outcome 45

Feature Descriptions 10 Location Based Charging (LBC)

1 The authorization may have the following subscription options:

Location Based Charging (LBC) 11 Feature Descriptions

specifying a feature code, as in: 6

placed or received by the mobile station. 21

• LBC invocation events 36

Feature Descriptions 12 Location Based Charging (LBC)

Location Based Charging (LBC) 13 Feature Descriptions

Call Forwarding—Busy (CFB) 1

LBC is invoked before CFB. 3

Data Privacy (DP) 42

For Further Study. 44

Emergency Services (9-1-1) 51

Emergency Services is invoked before LBC. 53

Feature Descriptions 14 Location Based Charging (LBC)

1 Flexible Alerting (FA)

Location Based Charging (LBC) 15 Feature Descriptions

Remote Feature Control (RFC) 1

LBC is invoked before RFC. 3