3GPP2
of 156
Transcript of 3GPP2
-
7/31/2019 3GPP2
1/156
3GPP2 N.S0007-0
Version 1.0
DCCH (Clarification of Audit Order with Forced Re-Registration in Pre-TIA/EIA-136-A Implementation)
COPYRIGHT
3GPP2 and its Organizational Partners claim copyright in this document and individual
Organizational Partners may copyright and issue documents or standards publications in
individual Organizational Partner's name based on this document. Requests for reproduction
of this document should be directed to the 3GPP2 Secretariat at [email protected]. Requests
to reproduce individual Organizational Partner's documents should be directed to that
Organizational Partner. See www.3gpp2.org for more information.
-
7/31/2019 3GPP2
2/156
July 19, 1997 N.S0007-0 v 1.0
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
i Table of Contents
CONTENTS
LIST OF TABLES........................................................... ........................................................ iv
LIST OF FIGURES ................................................ ....................................................... .......... vi
FOREWORD........................................................................................................................viii
REVISION HISTORY................. ........................................................ ................................... viii
1 INTRODUCTION.........................................................................................................1
1.1 GENERAL BACKGROUND AND ASSUMPTIONS... ..... ...... ..... ...... ..... ..... ...... ..... 1
1.2 Symbols and Abbreviations......... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ..... ...... ..... 2
1.3 Definitions.......................................................................................................3
2 REFERENCES ................................................... ........................................................ . 4
2.1 Normative References..... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... . 4
3 STAGE 1 SERVICE DESCRIPTIONS......... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... . 5
3.1 Non-Public Service Mode (NP)..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ..... ...... ..... 5
3.1.1 Normal Procedures With Successful Outcome. ... ... ... ... ... ... ... ... ... ... ... ... ... ... .. 5
3.1.2 Exception Procedures or Unsuccessful Outcome ... ... ... ... ... ... ... ... ... ... ... ... ... ... 6
3.1.3 Alternative Procedures...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ... 7
3.1.4 Interactions With Other Wireless Services.. ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... 7
3.2 User Group (UG)............................................... ................................................ 8
3.2.1 Normal Procedures With Successful Outcome. ... ... ... ... ... ... ... ... ... ... ... ... ... ... .. 8
3.2.2 Exception Procedures or Unsuccessful Outcome ... ... ... ... ... ... ... ... ... ... ... ... ... . 103.2.3 Alternative Procedures...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... . 11
3.2.4 Interactions With Other Wireless Services.. ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... . 11
4 INTERSYSTEM HANDOFF INFORMATION FLOWS........ ...... ..... ...... ...... ..... ...... ..... ..... 14
4.2 FacilitiesDirective2...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... . 14
4.2.1 Successful FacilitiesDirective2 (IS-41.2-C Page10).... ... ... ... ... ... ... ... ... ... ... .. 15
4.5 HandoffBack2 ................................................... .............................................. 18
4.5.1 Successful HandoffBack2 (IS-41.2-C Page 19) ... ... ... ... ... ... ... ... ... ... ... ... ... ... 18
4.7 HandoffMeasurementRequest2........ ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... . 21
4.7.1 Successful HandoffMeasurementRequest2 (IS-41.2-C Page 26).. .. .. .. .. .. .. .. .. .. . 21
4.9 HandoffToThird2...... ..... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ..... 24
4.9.1 Successful HandoffToThird2 (IS-41.2-C Page 33)... ... ... ... ... ... ... ... ... ... ... ... .. 24
5.10 Successful Handoff-Forward for MAHO with Measurement Confirmation (New) .. .. .. .. . 27
5 AUTOMATIC ROAMING INFORMATION FLOWS.. ...... ..... ...... ...... ..... ...... ..... ..... ...... ... 30
4.19 MSInactive ...................................................... .............................................. 30
4.19.1 Successful MSInactive: MS Declared Inactive (IS-41.3-C Page 83). .. .. .. .. .. .. .. 30
4.19.2 Successful MSInactive: MS Deregistered (IS-41.3-C Page 84) .. .. .. .. .. .. .. .. .. .. . 32
-
7/31/2019 3GPP2
3/156
N.S0007-0 v 1.0 July 19, 1997
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
Table of Contents ii
4.21 QualificationDirective ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... .. 34
4.21.2 Successful QualificationDirective: Re-authorization and Update Profile
(IS-41.3-C Page 92)........ ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... .. 34
4.21.3 Successful QualificationDirective: Update Profile Only (IS-41.3-C Page
94) ....................................................... ............................................ 35
4.22 QualificationRequest....... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... .... 36
4.22.2 Successful QualificationRequest: Authorization Confirmed and Profile
Returned (IS-41.3-C Page 99) ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... .... 36
4.22.3 Successful QualificationRequest: Profile Returned Only (IS-41.3-C Page
102)....................................................... ........................................... 38
4.27 RegistrationNotification ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... 40
4.27.2 Successful RegistrationNotification: Confirmed at the HLR (IS-41.3-C
Page 120). ....................................................... .................................. 40
4.30 RoutingRequest..... ....................................................... .................................. 42
4.30.1 Successful Indirect RoutingRequest: TLDN Returned (IS-41.3-C Page
128)....................................................... ........................................... 42
5.1 Registration ........................................................ ........................................... 44
5.1.a Initial Registration with Download of PSID/RSID List (new).. .. .. .. .. .. .. .. .. .. .. 44
5.7 DCCH Operations (new)......... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... .. 46
5.7.1 DCCH Registration (new)........ ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... 46
5.7.2 DCCH Call Delivery (new).. ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... .... 48
5.7.3 QualificationDirective: Update Profile and Control Channel Mode (new).. .. .. . 50
5.7.4 DCCH Call Termination without Profile (new)...... ... ... ... ... ... ... ... ... ... ... ... .. 52
5.7.5 InterSystemPage for a DCCH Capable MS (new).. ... ... ... ... ... ... ... ... ... ... ... ... 53
5.7.6 InterSystemPage2 for a DCCH Capable MS (new) ... ... ... ... ... ... ... ... ... ... ... ... 54
6.1 Call Delivery....................................................... ........................................... 55
6.1.a CD Invocation to a User Group on Another MSC (new)... ... ... ... ... ... ... ... ... .. 55
6.a User Group Operations (new)......... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... .. 576.a.1 Initial Registration in a User Group.. ..... ...... ...... ..... ...... ..... ...... ...... ..... .... 57
6.b User Zone Scenarios ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... .... 59
6.b.1 User Zone Registration..... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... .. 59
6.b.2 User Zone PSID Removal......... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... .... 60
6.b.3 Cancel Zone Change Tone ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... .. 62
6.b.4 User Zone Not Supported by Serving MSC..... ... ... ... ... ... ... ... ... ... ... ... ... ... .. 64
6.b.5 User Zone Only Service......... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... .. 66
6.b.6 Preferred User Zone Service.. ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... .... 68
6 IS-41.5-C SIGNALING PROTOCOL MODIFICATIONS.. ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... 70
6.1 Existing IS-41-C Operations ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... .... 70
6.4.2.12 FacilitiesDirective2 (IS-41.5-C Page 42)... ... ... ... ... ... ... ... ... ... .. 70
6.4.2.17 HandoffBack2 (IS-41.5-C Page 52) ... ... ... ... ... ... ... ... ... ... ... ... ... 74
6.4.2.19 HandoffMeasurementRequest2 (IS-41.5-C Page 56).. .. .. .. .. .. .. .. .. 78
6.4.2.21 HandoffToThird2 (IS-41.5-C Page 60)... ... ... ... ... ... ... ... ... ... ... .. 80
6.4.2.25 InterSystemPage (IS-41.5-C Page 68) ... ... ... ... ... ... ... ... ... ... ... .. 84
6.4.2.26 InterSystemPage2 (IS-41.5-C Page 70)... ... ... ... ... ... ... ... ... ... ... . 87
6.4.2.30 MSInactive (IS-41.5-C Page 76) ...... ..... ...... ..... ..... ...... ..... .... 89
-
7/31/2019 3GPP2
4/156
July 19, 1997 N.S0007-0 v 1.0
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
iii Table of Contents
6.4.2.32 QualificationDirective (IS-41.5-C Page 80) ... ... ... ... ... ... ... ... ... . 90
6.4.2.33 QualificationRequest (IS-41.5-C Page 82)... ... ... ... ... ... ... ... ... ... 92
6.4.2.38 RegistrationNotification (IS-41.5-C Page 90) ... ... ... ... ... ... ... ... . 94
6.4.2.41 RoutingRequest (IS-41.5-C Page 95) ... ... ... ... ... ... ... ... ... ... ... ... 96
6.3 Existing Parameters...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ..... 99
6.5.1.2 Parameter Identifiers........ ..... ...... ..... ...... ..... ...... ...... ..... ...... . 996.5.2.13 AuthorizationDenied (IS-41.5-C Page 144).. .. .. .. .. .. .. .. .. .. .. .. .. ..101
6.5.2.97 Profile (IS-41.5-C Page 230) ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...102
6.5.2.121 SignalQuality (IS-41.5-C Page 250) ... ... ... ... ... ... ... ... ... ... ... ...104
6.5.2.153 TDMAChannelData (IS-41.5-C Page 296) ... ... ... ... ... ... ... ... ... .106
6.5.2.154 TerminalType (IS-41.5-C Page 297) ... ... ... ... ... ... ... ... ... ... ... ...108
6.5.2.160 TransactionCapability (IS-41.5-C Page 307).. .. .. .. .. .. .. .. .. .. .. .. ..110
6.4 New Parameters ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ....113
6.5.2.aa BaseStationManufacturerCode (new)... .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..113
6.5.2.ab BSMCStatus (new)..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ....114
6.5.2.ac ControlChannelMode (new).... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ..115
6.5.2.ad NonPublicData (new).. ...... ..... ...... ..... ...... ...... ..... ...... ..... ....116
6.5.2.ae PagingFrameClass (new) ...... ...... ..... ...... ..... ...... ...... ..... ...... 118
6.5.2.af PSID_RSIDInformation (new).. ... ... ... ... ... ... ... ... ... ... ... ... ... ...119
6.5.2.ag PSID_RSIDList (new) ......................................................121
6.5.2.ah ServicesResult (new).........................................................122
6.5.2.ai SOCStatus (new) ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... 123
6.5.2.aj SystemOperatorCode (new) ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...124
6.5.3.ak TargetCellIDList (new) ...... ..... ...... ..... ..... ...... ..... ...... ..... ....125
6.5.2.i TDMAServiceCode (TSB-76) ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...126
6.5.2.j TDMATerminalCapability (TSB-76)... ... ... ... ... ... ... ... ... ... ... ...127
6.5.2.k TDMAVoiceCoder (TSB-76) ..............................................130
6.5.2.al UserGroup (new).. ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ....131
6.5.2.am UserZoneData (new)......... ..... ...... ..... ...... ..... ..... ...... ..... ...... 132
7 SIGNALING PROCEDURES. ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ..... ...... ..134
7.1 Existing IS-41-C Procedures..... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... 134
4.28.2 HLR Receiving LocationRequest INVOKE (IS-41-C Page 192) .. .. .. .. .. .. .. .. ..134
4.41.1 HLR Initiating a Routing Request (IS-41-C Page 252).. ... ... ... ... ... ... ... ... ... .138
4.41.3 MSC Receiving RoutingRequest INVOKE (IS-41-C Page 256) .. .. .. .. .. .. .. .. ..140
7.2 New IS-41-C Procedures...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ....147
5.12 Flexible Alerting (FA) ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... 147
5.12.A HLR User Group Incoming Call Invocation (new). ... ... ... ... ... ... ... ... ... ... ... ..147
-
7/31/2019 3GPP2
5/156
N.S0007-0 v 1.0 July 19, 1997
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
List of Tables iv
LIST OF TABLES
Table 1 UG Subscription Options ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ..... ...... ..... 9
Table 3 FE Combinations for FACDIR2... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... .. 14
Table 6 FE Combinations for HANDBACK2....... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... .... 18
Table 8 FE Combinations for HANDMREQ2 ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... .... 21
Table 10 FE Combinations for HANDTHIRD2.... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... 24
Table 33 FacilitiesDirective2 INVOKE Parameters.... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... 71
Table 34 FacilitiesDirective2 RETURN RESULT Parameters ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... . 73
Table 43 HandoffBack2 INVOKE Parameters... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... 75
Table 44 HandoffBack2 RETURN RESULT Parameters.. ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... . 77
Table 47 HandoffMeasurementRequest2 INVOKE Parameters .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. . 78
Table 51 HandoffToThird2 INVOKE Parameters ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... . 81
Table 52 HandoffToThird2 RETURN RESULT Parameters.... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... . 83
Table 59 InterSystemPage INVOKE Parameters... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... .. 85
Table 61 InterSystemPage2 INVOKE Parameters... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... 87
Table 68 MSInactive INVOKE Parameters..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... 89
Table 72 QualificationDirective INVOKE Parameters...... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... . 90
Table 74 QualificationRequest INVOKE Parameters ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... .. 92
Table 75 QualificationRequest RETURN RESULT Parameters.... ... ... ... ... ... ... ... ... ... ... ... ... ... .. 93
Table 84 RegistrationNotification INVOKE Parameters..... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... .. 94
Table 90 RoutingRequest INVOKE Parameters... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... 97
Table 118 IS-41 MAP Parameter Identifiers (continued) ........................................................ 99
Table 118 IS-41 MAP Parameter Identifiers (continued) .......................................................100
Table 126 AuthorizationDenied Reason value...... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...101
Table 175 SignalQuality value.. ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...104
Table 192 TDMAChannelData value.. ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... .....107
Table 193 TerminalType value.. ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...109
Table 198 TransactionCapability parameter.... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ..111
Table 198 TransactionCapability parameter (concluded). ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... .112
Table 2 BSMCStatus value. ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ..... 114
Table 3 ControlChannelMode value.... ...... ..... ...... ..... ...... ...... ..... ...... ..... ..... ...... ..... ...... ..115
Table 4 NonPublicData parameter........ ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ..... ...... ..... .117
Table 5 PagingFrameClass value.......... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... .....118
Table 6 PSID_RSIDInformation value ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... .120
-
7/31/2019 3GPP2
6/156
July 19, 1997 N.S0007-0 v 1.0
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
List of Tablesv
Table 7 ServicesResult parameter ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ....122
Table 8 SOCStatus value ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ..... ...... ..123
Table 9 TDMAServiceCode value......... ..... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... .126
Table 10 TDMATerminalCapability value.. ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ..128
Table 11 TDMATerminalCapability value (concluded)) ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... 129
Table 12 TDMAVoiceCoder value......... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... .130
Table 13 User Group value ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..131
-
7/31/2019 3GPP2
7/156
N.S0007-0 v 1.0 July 19, 1997
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
List of Figures vi
LIST OF FIGURES
Figure 4 Successful FacilitiesDirective2..... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... .... 15
Figure 9 Successful HandoffBack2 ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... .... 18
Figure 12 Successful HandoffMeasurementRequest2... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... . 21
Figure 15 Successful HandoffToThird2. ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... .... 24
Figure 0 Successful Handoff-Forward for MAHO with Measurement Confirmation .. .. .. .. .. .. .. .. .. 28
Figure 43 Successful MSInactive: MS Declared Inactive... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... . 30
Figure 44 Successful MSInactive: MS Deregistered ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... . 32
Figure 48 Successful QualificationDirective: Re-authorization and Update Profile. .. .. .. .. .. .. .. .. .. .. . 34
Figure 49 Successful QualificationDirective: Update Profile Only.... ... ... ... ... ... ... ... ... ... ... ... ... ... 35
Figure 52 Successful QualificationRequest: Authorization Confirmed and Profile Returned.. .. .. .. . 36
Figure 53 Successful QualificationRequest: Profile Returned Only... ... ... ... ... ... ... ... ... ... ... ... ... ... 38
Figure 65 Successful RegistrationNotification: Confirmed at the HLR ... ... ... ... ... ... ... ... ... ... ... ... 40
Figure 69 Successful Indirect RoutingRequest: TLDN Returned ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... 42
Figure 1 Initial Registration with Download of PSID/RSID List. ... ... ... ... ... ... ... ... ... ... ... ... ... .. 44
Figure 2 DCCH Registration.... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... . 46
Figure 3 DCCH Call Delivery ..... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ..... 48
Figure 4 QualificationDirective: Update Profile and Control Channel Mode .. .. .. .. .. .. .. .. .. .. .. .. .. .. 50
Figure 5 DCCH Call Termination without Profile ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ..... 52
Figure 6 InterSystemPage for a DCCH Capable MS ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... . 53
Figure 7 InterSystemPage2 for a DCCH Capable MS..... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... . 54
Figure 115 CD Invocation to a User Group on Another MSC ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... . 55
Figure 8 Initial Registration in a User Group. ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... . 57
Figure 9 User Zone Registration...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... . 59
Figure 10 UZ PSID Removal.. ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ..... ...... ..... ..... 60
Figure 11 Cancel Zone Change Tone ...... ..... ...... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... .. 62
Figure 12 UZ Not Supported by Serving MSC.. ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ... 64
Figure 13 User Zone Only Service.......... ..... ...... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... .. 66
Figure 14 Preferred User Zone Service.. ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ..... ...... ..... . 68
Figure 20 AuthorizationDenied parameter.... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... .101
Figure 105 Profile Macro ................................................. ..........................................102
Figure 129 SignalQuality parameter ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ..... .....104
Figure 168 TDMAChannelData parameter ..... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...106
Figure 169 TerminalType parameter ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ..... .....108
-
7/31/2019 3GPP2
8/156
July 19, 1997 N.S0007-0 v 1.0
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
List of Figuresvii
Figure 175 TransactionCapability parameter...... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...110
Figure 15 Base Station Manufacturer Code parameter ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... .113
Figure 16 BSMCStatus parameter ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... 114
Figure 17 ControlChannelMode parameter ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... .....115
Figure 18 NonPublicData parameter........ ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... .116
Figure 19 PagingFrameClass parameter. ..... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ....118
Figure 20 PSID_RSIDInformation parameter... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...119
Figure 21 PSID_RSIDList parameter... ..... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... .....121
Figure 22 ServicesResult parameter ..... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ....122
Figure 23 SOCStatus parameter.. ..... ...... ..... ...... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... .123
Figure 24 SystemOperatorCode parameter... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ...124
Figure 30 TargetCellIDList parameter ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ..... ...... ..... ...... .125
Figure 25 TDMAServiceCode parameter.. ..... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ..126
Figure 26 TDMATerminalCapability parameter ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ..127
Figure 27 TDMAVoiceCoder parameter. ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..130
Figure 28 UserGroup parameter.......... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ..... ...... ..... 131
Figure 29 UserZoneData parameter ..... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... 132
-
7/31/2019 3GPP2
9/156
N.S0007-0 v 1.0 July 19, 1997
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
Foreword viii
FOREWORD
The present Interim Standard (IS) contains recommendations to give networking support
for Systems and Mobile Stations built according to the IS-136 andIS-136-A air interface
specifications, specifically the Digital Control Channel functions, for both the 800 MHz
and 1800 MHz Hyperbands.
This IS adds service descriptions to the following Standard:
TIA/EIA-664, Cellular Features Description
This IS adds functionality to the following IS-41-C Interim Standard:
IS-41.2-C, Cellular Radiotelecommunications Intersystem Operations: Intersystem
Handoff Information Flows
IS-41.3-C, Cellular Radiotelecommunications Intersystem Operations: AutomaticRoaming Information Flows
IS-41.5-C, Cellular Radiotelecommunications Intersystem Operations: Signaling
Protocols
IS-41.6-C, Cellular Radiotelecommunications Intersystem Operations: Signaling
Procedures
Note:
This document cannot be used as a standalone source of specifications. The published IS-
41-C specification must be at hand. The Stage 2 tables and figures, as well as the Stage
3 message tables only show the additions, modifications, or deletions from the original
IS-41-C text. The table of contents reflects this fact.
REVISION HISTORY
Revision Date Remarks
0 July 1997 Gustavo Pavn (Ericsson) - Editor
-
7/31/2019 3GPP2
10/156
July 19, 1997 N.S0007-0 v 1.0
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
Introduction1
1 INTRODUCTION
This Interim Standard (IS) identifies the necessary Stage 1 descriptions, as well as Stage 2
and 3 changes and additions to IS-41-C, in order to support basic roaming and handoff
scenarios for wireless systems following the IS-136-A air interface specification.
1.1 GENERAL BACKGROUND AND ASSUMPTIONS
This IS provides Stage 1 descriptions for two new IS-136-A based features:
Non-Public Mode Service, and
User Groups.
This IS provides Stage 2 and 3 information for these two features, as well as the
following items related toIS-136-A infrastructure functions:
Protocol Versions,
Service Code,
Bandwidth,
Private and Residential System Identity (PSID/RSID),
System Operator Codes (SOC),
Base Station Manufacturer Code (BSMC),
Hyperbands,
Paging Frame Class (PFC),
Control Channel Mode (CCM),
Terminal Capability Information.
This IS assumes that only Extension-2 operations (e.g. FacilitiesDirective2) will be
enhanced in future revisions of IS-41.
-
7/31/2019 3GPP2
11/156
N.S0007-0 v 1.0 July 19, 1997
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
Introduction 2
1.2 Symbols and Abbreviations
General
The acronym omt as it appears in the message flow diagrams within this document
refers to the DCCH Forward Broadcast Control Channel.
Abbreviations
BSMC Base Station Manufacturer Code
BSMCS BSMCStaus Parameter
CCM ControlChannelMode Parameter
NP Non-Public Service Mode
NPDATA NonPublicData Parameter
PFC PagingFrameClass Parameter
PRINFO PSID/RSIDInformation Parameter
PRLIST PSID/RSIDList Parameter
PSID Private System Identifier
RSID Residential System Identifier
SERVRSLT ServicesResult Parameter
SOC System Operator Code
SOCS SOCStatus Parameter
TDMASC TDMAServiceCode Parameter
TDMAVC TDMAVoiceCoder Parameter
TERMCAP TDMATerminalCapability Parameter
UG User Group
UZ User Zone
UZDATA UserZoneData Parameter
-
7/31/2019 3GPP2
12/156
July 19, 1997 N.S0007-0 v 1.0
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
Introduction3
1.3 Definitions
Base Station Manufacturer Code (BSMC)
An indicator that uniquely identifies the manufacturer of the Base Station equipment. It
allows a Mobile Station to acquire services offered by a specific vendors Base Station.See IS-136-A.
Control Channel Mode (CCM)
An indicator that uniquely identifies the last known Control Channel (Analog or Digital)
used by an MS to access the system.
Paging Frame Class (PFC)
The number of Hyperframes over which an MS has a single instance of Paging Channel
allocation, therefore allowing the MS to sleep. SeeIS-136-A.
Private System ID (PSID)
A non-public (private) system identifier that is only accessible by authorized users. See
SID andIS-136-A.
Residential System Identifier (RSID)
A non-public system identifier that is only accessible by users on a residential system.
See SID andIS-136-A.
System Identification (SID)
A mandatory system identifier that shall be broadcast by a Base Station.
System Operator Code (SOC)
An indicator that uniquely identifies the System Operator. It allows a Mobile Station to
acquire services offered by a specific System Operator. SeeIS-136-A.
User Group (UG)
A limited number of subscribers associated by a common Directory Number, that can be
alerted simultaneously when registerd as group members.
User Zone (UZ)
An entity specified by associated PSIDs, RSIDs, SIDs or NIDs that may offer
differentiating services or flavors of services beyond those offered by the Public System.
-
7/31/2019 3GPP2
13/156
N.S0007-0 v 1.0 July 19, 1997
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
Introduction 4
2 REFERENCES
2.1 Normative References
TIA/EIA TSB76; IS-41-C Enhancements for PCS Multi-Band Support;Telecommunications Industry Association; September 1996.
TIA/EIA IS-41.1-C; Cellular Radiotelecommunications Intersystem
Operations: Functional Overview; Telecommunications Industry
Association; February 1996.
TIA/EIA IS-41.2-C; Cellular Radiotelecommunications Intersystem
Operations: Intersystem Handoff Information Flows; Telecommunications
Industry Association; February 1996.
TIA/EIA IS-41.3-C; Cellular Radiotelecommunications Intersystem
Operations: Automatic Roaming Information Flows; Telecommunications
Industry Association; February 1996.
TIA/EIA IS-41.4-C; Cellular Radiotelecommunications IntersystemOperations: Operations, Administration, and Maintenance Information
Flows and Procedures; Telecommunications Industry Association; February
1996.
TIA/EIA IS-41.5-C; Cellular Radiotelecommunications Intersystem
Operations: Signaling Protocols; Telecommunications Industry
Association; February 1996.
TIA/EIA IS-41.6-C; Cellular Radiotelecommunications Intersystem
Operations: Signaling Procedures; Telecommunications Industry
Association; February 1996.
TIA/EIA IS-136.1-A; TDMA Cellular/PCS - Radio Interface - Mobile
Station - Base Station Compatibility - Digital Control Channel;Telecommunications Industry Association; October 1996.
TIA/EIA IS-136.2-A; TDMA Cellular/PCS - Radio Interface - Mobile
Station - Base Station Compatibility - Traffic Channels and FSK Control
Channel; Telecommunications Industry Association; October 1996.
TIA/EIA IS-124-A; Wireless Radio Telecommunications Intersystem Non-
Signaling Data Communication DMH (Data Message Handler);
Telecommunications Industry Association; May 1997.
-
7/31/2019 3GPP2
14/156
July 19, 1997 N.S0007-0 v 1.0
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
Service Descriptions Non-Public Mode Service (NP)5
3 STAGE 1 SERVICE DESCRIPTIONS
3.1 Non-Public Service Mode (NP)
Non-Public Service Mode (NP) permits a subscriber to access available wireless serviceon a business telephone system (or private system) or a residential telephone system.
An application of Non-Public Mode Service is the User Zone (UZ). User Zones are
defined as entities (geographic, logical, or both), specified primarily by the Private
System Identifier (PSID), Residential System Identifier (RSID), System Identifier (SID),
or Network Identifier (NID) associated with the zones. User Zones provide an
optimization that allows for a mapping (maintained in the serving MSCs) to multiple
PSID/RSID/SID/NIDs, so that network traffic related to PSID/RSID/SID/NID downloads
is minimized.
A subscriber may obtain NP service via User Zones using the UZ Identifier. A UZ may
consist of a coverage area as small as a cell sector or a group of cells that overlay thePublic Wireless System, and may be a subset of a PSID/RSID/SID/NID. Alternatively,
User Zones spanning many systems may be identified by a common User Zone Identifier
in all these systems.
UZ's or PSID/RSIDs can offer differentiating flavors of services beyond those offered by
the Public System, based on criteria such as preferential charging areas, specific location
identities, zone unique features, etc. An end user may receive an in-call indication via a
tone or an MS display (icon) when a UZ or PSID/RSID is transitioned.
Applicability to Telecommunications Services
NP is applicable to all telecommunication services as offered by the private or residential
system operator.
3.1. 1 Normal Procedures With Successful Outcome
Authorization
NP is provided after pre-arrangement with the home or other service providers. The
service provider authorizes the base stations that operate in the NP mode. The business
or residential equipment owner or the service provider may authorize mobile stations that
may use these base stations. The MS may be programmed with the identifiers of private
and residential systems on which the MS may autonomously try to register. The MS
may have a priority of systems which it uses to determine the preferred system for
registration. The subscriber may have the capability to add, change, or delete this priority
system list stored in the MS.
De-Authorization
NP may be withdrawn at the subscribers request or for administrative reasons.
Registration
NP is registered upon authorization.
-
7/31/2019 3GPP2
15/156
N.S0007-0 v 1.0 July 19, 1997
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
Non-Public Mode Service (NP) Service Descriptions6
De-Registration
NP is de-registered upon de-authorization.
NP Activation
NP may be activated upon authorization.
De-Activation
NP shall be de-activated upon de-authorization.
Invocation
NP is invoked by the MS if the MS finds a control channel that supports NP and an MS
registration is accepted by the private or residential system.
If an MS does not autonomously register for NP, the subscriber may be presented with a
list of private system identifications or residential system identifications. The subscriber
may select a system and attempt a test registration in order to determine the subscribers
authorization. If the system accepts this test registration, then the subscriber can select a
private or residential system for normal MS registration if authorized for NP.
Normal Operation With Successful Outcome
Once NP is invoked, normal operation for the private or residential system is perceived by
the subscriber (e.g., 4-digit dialing, business features).
Call Detail Record
The private or residential system may record call detail information for the following:
a. Registrations (successful and unsuccessful).
b. Mobile originations.
c. Mobile terminations.
d. Features invoked.
e. Number of UZ calls.
f. Number of UZ calls with transition.
g. User Zone Identifier(s) and duration in each UZ.
h. PSID/RSID/SID/NID and duration in each.
3. 1.2 Exception Procedures or Unsuccessful Outcome
Registration
If the subscriber is not authorized for the request, the system may give further information
to the subscriber (e.g., other systems to access) and reject the registration. The MS
provides a capability not to register again with systems that reject a registration. This
list may be deleted upon MS power down.
De-Registration
A de-registration failure should provide the subscriber an indication that mobile terminated
calls may not be forwarded (i.e., Call Delivery feature may not be invoked).
-
7/31/2019 3GPP2
16/156
July 19, 1997 N.S0007-0 v 1.0
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
Service Descriptions Non-Public Mode Service (NP)7
Activation
None identified.
De-Activation
None identified.
Invocation
None identified.
Exceptions While Roaming
None identified.
Exceptions During Intersystem Handoff
None identified.
3.1 .3 Alternative ProceduresNone identified.
3.1. 4 Interactions With Other Wireless Services
These interactions are beyond the scope of this standard.
-
7/31/2019 3GPP2
17/156
N.S0007-0 v 1.0 July 19, 1997
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
User Group (UG) Service Descriptions8
3.2 User Group (UG)
User Group (UG) allows for a number of UG capable MSs to register for operation within
a specific user group. This group of MSs can be alerted as a group (i.e., simultaneously)
when a call is made to the directory number associated with the group.
MSs registered in a User Group can receive distinctive alerting for incoming calls to the
User Group. In other words, the service provider can establish different ringing patterns
based on whether the call is to the MIN or to the User Group.
MSs are allowed to be authorized in multiple User Groups, but can be active in only one
User Group at a time. MSs may be active in both an FA/MAH group and a User Group
at the same time.
MSs can request to be activated on a particular User Group, or request to be activated
without specifying a Group ID (in which case they will be assigned a default User
Group). MSs can also request to be deactivated from the User Group in which they are
currently active. The MS user shall be provided an indication of the result (success orfailure) of a user group request.
A user group can be associated with a geographical area known as the domain of the user
group. When the MS roams into an area which lies outside the domain of the active user
group, the MS user may be provided an indication that the MS is no longer active within
the group.
Applicability to Telecommunications Services
UG is applicable to voice telecommunication services.
3. 2.1 Normal Procedures With Successful Outcome
Authorization
A user group is defined by the service provider by associating it with a directory number.
The associated directory number identifies the User Group; this number is used in special
user group alerting. A distinctive alerting pitch, cadence, or both may also be specified
for the user group.
Membership in a user group may be provided after pre-arrangement with the service
provider. UG authorization may have the following subscription options for each defined
user group:
-
7/31/2019 3GPP2
18/156
July 19, 1997 N.S0007-0 v 1.0
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
Service Descriptions User Group (UG)9
Table 1 UG Subscription Options
Subscription Options Values
Membership Type Demand. A UG member is
authorized to activate and
de-activate his membership in a
user group.Permanent. A UG member is
always an active member of the
authorized user group(s) when
determined appropriate by the
service provider.
De-Authorization
UG may be withdrawn at the subscribers request or for administrative reasons.
Registration
UG shall be registered upon authorization.
De-Registration
UG shall be de-registered upon de-authorization.
Individual members of the UG may be deleted at any time by the service provider.
Activation
Demand Member Activation of a Subscribers Default User Group(s)
A User Group Demand Membership Authorized member may activate his membership in
a default User Group through an activation request during registration which does not have
a specified UGID.
If the activation is accepted, the user shall receive feature confirmation.
Demand Member Activation of a Specified User Group(s)
A User Group Demand Membership Authorized member may activate his membership in
a User Group through an activation request during registration which has a specified User
Group.
If the activation is accepted, the user shall receive feature confirmation.
De-Activation
UG shall be de-activated upon de-authorization.
Demand Member De-Activation of a Subscribers Active User Group
A User Group Demand Membership Authorized member may de-activate his or her
membership in the currently active User Group through a de-activation request.
If the activation is accepted, the user shall receive feature confirmation.
-
7/31/2019 3GPP2
19/156
N.S0007-0 v 1.0 July 19, 1997
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
User Group (UG) Service Descriptions10
Invocation
UG is invoked when there is an incoming call to the DN associated with the UG. UG
may be invoked with a revertive call from one member of the User Group (i.e., a MS user
who is currently active in a User Group may call the DN associated with that group) to
reach another member of the User Group.
Normal Operation with Successful Outcome
For an incoming call to a UG Directory Number, all active members of the User Group
are paged using special User Group paging. The MS user must respond to the User
Group page by performing a manual action upon the terminal. The first MS user to
respond to the User Group page alert is alerted normally and has an opportunity to answer
the call. No other User Group members receive alerting or have an opportunity to answer
the call.
While the User Group is being paged, the calling party hears call progress tones or other
announcements. The call progress tones may be generated by the originating system to
allow uniform call progress treatment.
Call Detail Record
The system should record call detail information for the following:
a. Mobile Terminations.
See future revisions of IS-124-A for the specific information to be included for each
element.
3. 2.2 Exception Procedures or Unsuccessful Outcome
Registration
None identified.
De-Registration
None identified.
Activation
If the subscriber is already active in the specified group, the user shall receive feature
confirmation.
De-Activation
If the subscriber is already inactive in the specified group, the user shall receive feature
confirmation.
Invocation
None identified.
Exceptions While Roaming
An MS authorized with the "permanent" type of membership (see table 1) may
not be automatically activated in the user group when the MS is roaming outside the
-
7/31/2019 3GPP2
20/156
July 19, 1997 N.S0007-0 v 1.0
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
Service Descriptions User Group (UG)11
domain of the group. An MS user authorized with the "demand" type of membership
may not be able to successfully activate membership in the user group when the MS is
roaming outside the domain of the group.
Exceptions During Intersystem Handoff
None identified.
3.2 .3 Alternative Procedures
None identified.
3.2. 4 Interactions With Other Wireless Services
Asynchronous Data Service (ADS)
None identified. User Group applies to voice telecommunications service only.
Call Delivery (CD)
None identified.
Call ForwardingBusy (CFB)
None identified.
Call ForwardingDefault (CFD)
None identified.
Call ForwardingNo Answer (CFNA)
None identified.
Call ForwardingUnconditional (CFU)
None identified.
Call Transfer (CT)
None identified.
Call Waiting (CW)
None identified.
Calling Name Presentation (CNAP)None identified.
Calling Number Identification Presentation (CNIP)
None identified.
Calling Number Identification Restriction (CNIR)
None identified.
-
7/31/2019 3GPP2
21/156
N.S0007-0 v 1.0 July 19, 1997
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
User Group (UG) Service Descriptions12
Conference Calling (CC)
None identified.
Do Not Disturb (DND)
None identified.
Emergency Services (9-1-1)
None identified.
Flexible Alerting (FA)
None identified.
Group 3 Facsimile Service (G3 Fax)
None identified. User Group ID applies to voice telecommunications service only.
Incoming Call Screening (ICS)
None identified. Incoming calls to a User Group directory number are not subject to
Incoming Call Screening.
Message Waiting Notification (MWN)
None identified.
Mobile Access Hunting (MAH)
None identified.
Network Directed System Selection (NDSS)
None identified.
Non-Public Mode Service (NP)
None identified.
Over-the-Air Activation (OTA)
None identified.
Password Call Acceptance (PCA)
None identified.
Preferred Language (PL)
None identified.
Priority Access and Channel Assignment (PACA)
None identified.
Remote Feature Control (RFC)
None identified.
-
7/31/2019 3GPP2
22/156
July 19, 1997 N.S0007-0 v 1.0
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
Service Descriptions User Group (UG)13
Selective Call Acceptance (SCA)
None identified.
Speech Option Selection (SOS)
None identified.
Subscriber PIN Access (SPINA)
None identified.
Subscriber PIN Intercept (SPINI)
None identified.
Three-Way Calling (3WC)
None identified.
User Group ID (UGID)
Not applicable.
Voice Controlled Services (VCS)
None identified.
Voice Message Retrieval (VMR)
None identified.
Voice Privacy (VP)
None identified.
Voice-based User Identification (VUI)
None identified.
-
7/31/2019 3GPP2
23/156
N.S0007-0 v 1.0 July 19, 1997
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
FacilitiesDirective2 Intersystem Handoff Operations14
4 INTERSYSTEM HANDOFF INFORMATIONFLOWS
4 .2 FacilitiesDirective2
The FacilitiesDirective2 (FACDIR2) operation is used by the Anchor MSC, the Serving
MSC or a Tandem MSC to request that the Target MSC initiate the Handoff-Forward
task. This operation differs from the FacilitiesDirective operation in its addition of
support for CDMA, multi-band TDMA, and NAMPS Mss.
The MobileOnChannel operation is then used by the Target MSC to inform the
requesting system that the Target MSC has successfully completed the Handoff-Forward
task.1
The following table lists the possible combinations of invoking and responding Fes.
Table 3 FE Combinations for FACDIR2
INVOKING FE RESPONDING FE
Case 1 Anchor MSC Target MSC
Case 2 Serving MSC Target MSC
Case 3 Tandem MSC Target MSC
One of two possible results is returned:
1. Notification that the request was accepted, including the parameters of the
voice channel selected by the Target MSC on the designated cell.
2. Notification that the request was unsuccessful because a voice channel on
the designated cell is not available.
1The MobileOnChannel operation is included here because it completes the transaction
initiated with the FacilitiesDirective2 operation.
-
7/31/2019 3GPP2
24/156
July 19, 1997 N.S0007-0 v 1.0
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
Intersystem Handoff Operations FacilitiesDirective215
4.2 .1 Successful FacilitiesDirective2 (IS-41.2-C Page10)
This scenario describes the successful use of the FacilitiesDirective2 operation.
a
b
FACDIR2 [RequestedServiceInfo, RequestedTargetInfo]
MSC MSC
facdir2 [GrantedServiceInfo, GrantedTargetInfo]
HOT
TargetSystem
ServingSystem
cMSONCH [ ]
Figure 4 Successfu l Faci li tiesDirect ive2
-
7/31/2019 3GPP2
25/156
N.S0007-0 v 1.0 July 19, 1997
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
FacilitiesDirective2 Intersystem Handoff Operations16
a. The Serving MSC determines that a call should be handed off to a target system. It
sends a FACDIR2 to the Target MSC, directing the Target MSC to initiate a
Handoff-Forward task.
Parameters are as in Section 4.1.1, Step-a, with the exception that ChannelInfo1 is not
included and with the following additions:
Parameters Usage Type
RequestedService-
Information
Set of parameters for Requested Service
Information
[ChannelData] Indicates the SAT Color Code, Voice Mobile
Attenuation Code, DTX-Mode, and the
channel number of the serving channel, if
analog.
O
[TDMAChannelData] Indicates the Rate, Digital Verification Color
Code, Digital Mobile Attenuation Code,
DTX-Mode, Hyperband, and the channel
number of the serving channel, if TDMA.
O
[TDMAServiceCode ] Identifies the requested Service Code used in
this call. (Extension to the TDMACallMode
parameter).
O
[BSMC] Identifies the base station manufacturer code
of the serving Base Station.
O
[SOC] Identifies the system operator code
associated with the served MS.
O
[TDMATerminal-
Capability]
Indicates the Terminal Capability: Async
Data or G3 Fax Support, STU-III, Supported
Frequency Bands, 800 MHz Analog Speech,
Half Rate, Full Rate, Double Rate, Triple
Rate support, Protocol Version and Voice
Coder capabilities.
O
TerminalType Indicates the radio frequency interface
standard supported by the associated MS.
O
-
7/31/2019 3GPP2
26/156
July 19, 1997 N.S0007-0 v 1.0
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
Intersystem Handoff Operations FacilitiesDirective217
b. If a voice channel on the designated target cell is available, the Target MSC
increases the Segment Counter in the received BillingID parameter by one and uses
the new BillingID for the new call segment. It then returns a facdir2 to the
requesting MSC, and initiates a Handoff-Forward task.
Parameters Usage Type
GrantedTargetInfo: Set of parameters for Target Service
Information.
[ChannelData] Indicates the SAT Color Code, Voice Mobile
Attenuation Code, DTX-Mode, and the
channel number of the target channel, if
analog.
O
[TDMAChannelData] Indicates the Rate, Digital Verification Color
Code, Digital Mobile Attenuation Code,
DTX-Mode, Hyperband, Timeslot, and the
channel number of the target channel, if
TDMA.
O
GrantedServiceInfo: Set of parameters for Granted Service
Information.
[BSMC-Status] Indicates whether or not the BSMC in the
target environment is the same as that of the
Base Station currently serving the MS .
O
[SOC-Stat us] Indicates whether or not the SOC in the target
environment is the same as that currently
associated with the served MS .
O
[TDMAV oice C oder ] Identifies the actual Voice Coder provided by
the target Base Station
O
c. After having initiated the Handoff-Forward task, if the MS is received on the
designated voice channel, the Target MSC completes the voice path between the
voice channel and the inter-MSC trunk and then sends a MSONCH to the initiator of
the Handoff-Forward task (the Serving MSC in this scenario).
-
7/31/2019 3GPP2
27/156
N.S0007-0 v 1.0 July 19, 1997
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
HandoffBack2 Intersystem Handoff Operations18
4.5 HandoffBack2
The HandoffBack2 (HANDBACK2) operation is used by the Serving MSC to request that
the Target MSC initiate the Handoff-Back task. This task is used to handoff a call to a
Target MSC to which the Serving MSC is already connected, for the call in question, via
an inter-MSC trunk. This operation differs from the HandoffBack operation in its additionof support for CDMA and multi-band TDMA MSs.
The following table lists the possible combinations of invoking and responding Fes.
Table 6 FE Combinations for HANDBACK2
INVOKING FE RESPONDING FE
Case 1 Serving MSC Target MSC
4.5 .1 Successful HandoffBack2 (IS-41.2-C Page 19)
This scenario describes the successful use of the HandoffBack2 operation.
a
b
HANDBACK2 [RequestedTargetInfo, RequestedServiceInfo]
MSC MSC
handback2 [GrantedTargetInfo, GrantedServiceInfo]
HOT
ServingSystem
TargetSystem
Figure 9 Successful HandoffBack2
-
7/31/2019 3GPP2
28/156
July 19, 1997 N.S0007-0 v 1.0
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
Intersystem Handoff Operations HandoffBack219
a. The Serving MSC determines that a call should be handed off to a target system to
which it is already connected, for the call in question, via an inter-MSC trunk. It
sends a HANDBACK2 to the Target MSC, directing the Target MSC to initiate a
Handoff-Back task.
Parameters are as in Section 4.4.1, Step-a, with the exception that ChannelInfo1 is not
included and with the following additions:
Parameters Usage Type
RequestedServiceInfo Set of parameters for Requested Service
Information.
[ChannelData] Indicates the SAT Color Code, Voice Mobile
Attenuation Code, DTX-Mode, and the
channel number of the serving channel, if
analog.
O
[TDMAChannelData] Indicates the Rate, Digital Verification Color
Code, Digital Mobile Attenuation Code,
DTX-Mode, Hyperband, and the channel
number of the serving channel, if TDMA.
O
[BSMC] Identifi es the base station manufacturer code
of the serving Base Station.
O
[SOC] Identifies the system operator code
associated with the served MS.
O
[TDMAServiceCode ] Identifies the requested Service Code used in
this call. (Extension to the TDMACallMode
parameter).
O
[TerminalType] Indicates the radio frequency interface
standard supported by the associated MS.
O
[TDMATerminal-
Capability]
Indicates the Terminal Capability: Async
Data or G3 Fax Support, STU-III, Supported
Frequency Bands, 800 MHz Analog Speech,
Half Rate, Full Rate, Double Rate, Triple
Rate support, Protocol Version and Voice
Coder capabilities.
O
[TDMAVoiceCoder] Indicates the Voice Coder capabilities of the
Mobile Station
O
-
7/31/2019 3GPP2
29/156
N.S0007-0 v 1.0 July 19, 1997
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
HandoffBack2 Intersystem Handoff Operations20
b. The Target MSC increases the Segment Counter in the received BillingID parameter
by one. If a voice channel on the designated target cell is available, it returns a
handback2 to the requesting MSC, and initiates a Handoff-Back task.
Parameters Usage Type
GrantedTargetInfo: Set of parameters for Target Service
Information.
[ChannelData] Indicates the SAT Color Code, Voice Mobile
Attenuation Code, DTX-Mode, and the
channel number of the target channel, if
analog.
O
[TDMAChannelData ] Indicates the Rate, Digital Verification Color
Code, Digital Mobile Attenuation Code,
DTX-Mode, Hyperband , Timeslot, and the
channel number of the target channel, if
TDMA.
O
GrantedServiceInfo: Set of parameters for Granted ServiceInformation.
[BSMC-Status] Indicates whether or not the BSMC in the
target environment is the same as that of the
Base Station currently serving the MS .
O
[SOC-Status] Indicates whether or not the SOC in the target
environment is the same as that currently
associated with the served MS .
O
[TDMAV oice C oder ] Identifies the actual Voice Coder provided by
the target Base Station
O
-
7/31/2019 3GPP2
30/156
-
7/31/2019 3GPP2
31/156
N.S0007-0 v 1.0 July 19, 1997
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
HandoffMeasurementRequest2 22 Intersystem Handoff Operations
Parameters are as in Section 4.6.1, Step-a, with the exception that ChannelInfo1 is not
included and with the following additions:
Parameters Usage Type
CurrentServingInfo: Set of parameters for Current Serving
Information
[ChannelData] Indicates the SAT Color Code, Voice Mobile
Attenuation Code, DTX-Mode, and the
channel number of the target channel, if
analog.
O
[TDMAChannelData] Indicates the Rate, Digital Verification Color
Code, Digital Mobile Attenuation Code,
DTX-Mode, Hyperband , Timeslot, and the
channel number of the target channel, if
TDMA.
O
[TDMATerminal-
Capability]
Indicates the Terminal Capability: Async
Data or G3 Fax Support, STU-III, Supported
Frequency Bands, 800 MHz Analog Speech,
Half Rate, Full Rate, Double Rate, TripleRate support, Protocol Version and Voice
Coder capabilities.
O
TargetCellIDList Indicates TargetCell IDs from which
measurements of M S signal strength need to
be made.
O
b. The candidate MSC identifies the candidate cell sites corresponding to the
ServingCellID in the HANDMREQ2. It performs location measurements in
accordance with the MSCs internal algorithm.
Note that for an 800 MHz to 1900 MHz TDMA handoff, the signal strength
measurements need to be compensated due to the target measurements being made
using nominal ERP tables.
When all expected internal responses are received, if the best candidate cell site does
not meet the quality criteria of the candidate MSC, the candidate MSC may elect to
end the location process. In this case, no handmreq2 is returned.
Otherwise:
For analog or TDMA traffic channels, the candidate MSC converts the
location quality values to the appropriate signal quality parameter values
with respect to the maximum power levels allowed in the candidate cell
sites, the current MS power level in the serving cell site and station class
mark.
For CDMA traffic channels, the candidate MSC converts the location
quality values to the CDMASignalQuality parameter value and includes the
TargetOneWayDelay value, if available.
-
7/31/2019 3GPP2
32/156
July 19, 1997 N.S0007-0 v 1.0
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
Intersystem Handoff Operations 23 HandoffMeasurementRequest2
The results are returned to the Serving MSC in a handmreq2.
Parameters Usage Type
MeasurementInformation: A list of parameters with Measurement
Information
[CDMATarget-
MeasurementList]
Include for CDMA. O
[TargetMeasurementList] Include for AMPS, NAMPS or TDMA. O
-
7/31/2019 3GPP2
33/156
N.S0007-0 v 1.0 July 19, 1997
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
HandoffToThird2 24 Intersystem Handoff Operations
4.9 HandoffToThird2
The HandoffToThird2 (HANDTHIRD2) operation is used by the Serving MSC (non-
Anchor) to initiate a handoff with path minimization. This operation differs from the
HandoffToThird operation in its support of dual-mode CDMA and multi-band TDMA
MSs.
The following table lists the possible combinations of invoking and responding Fes.
Table 10 FE Combinat ions for HANDTHIRD2
INVOKING FE RESPONDING FE
Case 1 Serving MSC Anchor MSC
Case 2 Serving MSC Tandem MSC
Case 3 Tandem MSC Tandem MSC
4.9 .1 Successful HandoffToThird2 (IS-41.2-C Page 33)This scenario describes the successful use of the HandoffToThird2 operation.
a
b
HANDTHIRD2 [RequestedServiceInfo, RequestedTargetInfo]
MSC MSC
handthird2 [GrantedServiceInfo, GrantedTargetInfo]
HTTT
ServingSystem
AnchorSystem
Figure 15 Successful HandoffToThird2
-
7/31/2019 3GPP2
34/156
July 19, 1997 N.S0007-0 v 1.0
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
Intersystem Handoff Operations 25 HandoffToThird2
a. The Serving MSC determines that a call should be handed off to a target system and
that path minimization may be possible. It sends a HANDTHIRD2 to the MSC
which had previously handed off the call to the Serving MSC (i.e., the Anchor
MSC in this scenario), requesting that a handoff with path minimization be
performed.
Parameters are as in Section 4.8.1, Step-a, with the exception that ChannelInfo1 is notincluded and with the following additions:
Parameters Usage Type
RequestedServiceInfo: Set of parameters for Requested Service
Information
[ChannelData] Indicates the SAT Color Code, Voice Mobile
Attenuation Code, DTX-Mode , and the
channel number of the serving channel, if
analog.
O
[TDMAChannelData ] Indicates the Rate, Digital Verification Color
Code, Digital Mobile Attenuation Code,
DTX-Mode, Hyperband , and the channel
number of the serving channel, if TDMA.
O
[BSMC] Identifies the base station manufacturer code
of the serving Base Station.
O
[SOC] Identifies the system operator code
associated with the served MS.
O
[TDMAServiceCode ] Identifies the requested Service Code used in
this call. (Extension to the TDMACallMode
parameter).
O
[TerminalType] Indicates the radio frequency interface
standard supported by the associated MS.
O
[TDMATerminal-
Capabi lity ]
Indicates the Terminal Capability: Async
Data or G3 Fax Support, STU-III, Supported
Frequency Bands, 800 MHz Analog Speech,
Half Rate, Full Rate, Double Rate, Triple
Rate support, Protocol Version and Voice
Coder capabilities.
O
[TDMAVoiceCoder] Indicates the Voice Coder capabilities of the
Mobile Station.
O
-
7/31/2019 3GPP2
35/156
N.S0007-0 v 1.0 July 19, 1997
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
HandoffToThird2 26 Intersystem Handoff Operations
b. If the receiving MSC accepts the request to perform a handoff with path
minimization, and a voice channel on the target system is found available, the
receiving MSC returns the parameters of the selected voice channel to the Serving
MSC in a handthird2.
Parameters Usage Type
GrantedService-
Information:
Set of parameters for Granted Service
Information.
[BSMC-Status] Indicates whether or not the BSMC in the
target environment is the same as that of the
Base Station currently serving the MS .
O
[SOC-Status] Indicates whether or not the SOC in the target
environment is the same as that currently
associated with the served MS .
O
[TDMAV oice C oder ] Identifies the actual Voice Coder provided by
the target Base Station
O
GrantedTargetInfo: Set of parameters for Target Service
Information.
[ChannelData] Indicates the SAT Color Code, Voice Mobile
Attenuation Code, DTX-Mode , and the
channel number of the target channel, if
analog.
O
[TDMAChannelData ] Indicates the Rate, Digital Verification Color
Code, Digital Mobile Attenuation Code,
DTX-Mode, Hyperband , Timeslot, and the
channel number of the target channel, if
TDMA.
O
-
7/31/2019 3GPP2
36/156
July 19, 1997 N.S0007-0 v 1.0
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
Basic Intersystem Handoff Scenarios 27 Measurement Confirmation
5.10 Successful Handoff-Forward for MAHO withMeasurement Confirmation (New)
This scenario describes the successful Handoff-Forward process in the case where a Mobile
Assisted Handoff is performed using Measurement Confirmation. This is done to address a
problem that is caused by an MS which, while reporting MAHO measurements, does notinclude the Digital Verification Color Code (DVCC; see IS-136.2, Section 2.4.3) nor the
Coded DVCC (CDVCC; see IS-136.2, Sections 1.2.5 & 2.4.3). This omission leads to
cases where the MS may have measured a forward channel erroneously from a cell or
sector not in the immediate handoff viscinity. RF emission patterns are hard to contain,
and other radio transmission anomalies (tunneling, etc) are typically the cause of these
erroneous readings. By performing a corresponding HandoffMeasurementRequest
operation, the Serving MSC is able to confirm whether or not certain suspect
measurements are for valid border cells or sectors, prior to handoff, thus improving the
probability that a good handoff will occur.
-
7/31/2019 3GPP2
37/156
N.S0007-0 v 1.0 July 19, 1997
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
Measurement Confirmation 28 Basic Intersystem Handoff Scenarios
Handoff-Forward for MAHO with Measurement Confirmation
Anchor & Serving
System
A
Target
System
B
a
MSC MSC
call in progress
Initial ConnectionsA B
X
Y
MS
Served MS
X
h
j
MHOT
i
c
d
e
f
HANDMREQ [TargetCellIDList]
LMMRThandmreq
FACDIR
HOTfacdir
MSONCH
handoff complete
Resulting Connections
A B
ghandoff order
X arrives on new channel
MAT
QUERY w/ PERMISSION
CONV w/ PERMISSION
RESPONSE
X
SINGLE
TCAP
TRANSACTION
Y
acall in progress
bMAHO measurements
Figure 0 Successful Handoff-Forward for MAHO with MeasurementConfirmation
a. A call involving the served MS is in progress.
-
7/31/2019 3GPP2
38/156
July 19, 1997 N.S0007-0 v 1.0
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
Basic Intersystem Handoff Scenarios 29 Measurement Confirmation
b. The Serving MSC elects, based on its internal algorithm, to determine if a handoff
to an adjacent candidate MSC is appropriate. Directed by the Serving MSC which
provides a list of MAHO Channels (corresponding to individual neighboring cells or
sectors) to the MS, the MS makes MAHO measurements and returns them to the
MSC. The MSC maps the MAHO channel numbers into associated TargetCellIDs.
c. The Serving MSC, using service related statistics regarding dropped or poor handoffs
may send a HANDMREQ or HANDMREQ2 containing the TargetCellIDList
parameter, which is a list of TargetCellID parameters of suspect cells or sectors, to
the MSC associated with the suspect measurement(s). The Serving MSC may send
several handoff measurement requests to different MSCs. The Serving MSC
typically picks only those MSCs, whose cells or sectors have in the past been party
to poor or dropped handoffs.
d. The MSC performs location measurements for the cells and sectors identified in the
TargetCellIDList, in accordance with the MSCs internal algorithm and
