3GPP2

3GPP2 N.S0007-0 Version 1.
DCCH (Clarification of Audit Order with Forced ReRegistration 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 shoyler@tia.eia.org. Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See www.3gpp2.org for more information.
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
CONTENTS
LIST OF TABLES................................................................................................................... iv LIST OF FIGURES ................................................................................................................. vi FOREWORD ........................................................................................................................ viii REVISION HISTORY............................................................................................................ viii 1 INTRODUCTION ......................................................................................................... 1 1.1 1.2 1.3 2 GENERAL BACKGROUND AND ASSUMPTIONS.............................................. 1 Symbols and Abbreviations................................................................................. 2 Definitions....................................................................................................... 3
REFERENCES ............................................................................................................ 4 2.1 Normative References......................................................................................... 4
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 User Group (UG)............................................................................................... 8 3.2.1 Normal Procedures With Successful Outcome............................................. 8 3.2.2 Exception Procedures or Unsuccessful Outcome ........................................ 10 3.2.3 Alternative Procedures .......................................................................... 11 3.2.4 Interactions With Other Wireless Services ................................................ 11
3.2
INTERSYSTEM HANDOFF INFORMATION FLOWS.................................................... 14 4.2 4.5 4.7 4.9 5.10 FacilitiesDirective2.......................................................................................... 14 4.2.1 Successful FacilitiesDirective2 (IS-41.2-C Page10).................................... 15 HandoffBack2 ................................................................................................. 18 4.5.1 Successful HandoffBack2 (IS-41.2-C Page 19) .......................................... 18 HandoffMeasurementRequest2............................................................................ 21 4.7.1 Successful HandoffMeasurementRequest2 (IS-41.2-C Page 26)..................... 21 HandoffToThird2............................................................................................. 24 4.9.1 Successful HandoffToThird2 (IS-41.2-C Page 33)...................................... 24 Successful Handoff-Forward for MAHO with Measurement Confirmation (New) ......... 27
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
Table of Contents
N.S0007-0 v 1.0
July 19, 1997
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 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 RegistrationNotification ................................................................................... 40 4.27.2 Successful RegistrationNotification: Confirmed at the HLR (IS-41.3-C Page 120) .......................................................................................... 40 RoutingRequest .............................................................................................. 42 4.30.1 Successful Indirect RoutingRequest: TLDN Returned (IS-41.3-C Page 128).................................................................................................. 42 Registration ................................................................................................... 44 5.1.a Initial Registration with Download of PSID/RSID List (new)...................... 44 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 Call Delivery.................................................................................................. 55 6.1.a CD Invocation to a User Group on Another MSC (new)............................. 55 User Group Operations (new)............................................................................. 57 6.a.1 Initial Registration in a User Group........................................................ 57 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
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
4.22
4.27
4.30
5.1 5.7
6.1 6.a 6.b
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
48 49 50 51 52 53 54 55 56 57 58 59 60
Table of Contents
ii
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
6.4.2.32 6.4.2.33 6.4.2.38 6.4.2.41 6.3
QualificationDirective (IS-41.5-C Page 80) ............................ 90 QualificationRequest (IS-41.5-C Page 82).............................. 92 RegistrationNotification (IS-41.5-C Page 90) ......................... 94 RoutingRequest (IS-41.5-C Page 95) .................................... 96
Existing Parameters......................................................................................... 99 6.5.1.2 Parameter Identifiers........................................................... 99 6.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 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
6.4
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 New IS-41-C Procedures..................................................................................147 Flexible Alerting (FA) ....................................................................................147 5.12.A HLR User Group Incoming Call Invocation (new) ....................................147
7.2 5.12
iii
Table of Contents
N.S0007-0 v 1.0
July 19, 1997
LIST OF TABLES
Table 1 Table 3 Table 6 Table 8 Table 10 Table 33 Table 34 Table 43 Table 44 Table 47 Table 51 Table 52 Table 59 Table 61 Table 68 Table 72 Table 74 Table 75 Table 84 Table 90 Table 118 Table 118 Table 126 Table 175 Table 192 Table 193 Table 198 Table 198 Table 2 Table 3 Table 4 Table 5 Table 6 UG Subscription Options ................................................................................... 9 FE Combinations for FACDIR2 ........................................................................ 14 FE Combinations for HANDBACK2.................................................................. 18 FE Combinations for HANDMREQ2 ................................................................. 21 FE Combinations for HANDTHIRD2................................................................. 24 FacilitiesDirective2 INVOKE Parameters............................................................. 71 FacilitiesDirective2 RETURN RESULT Parameters .............................................. 73 HandoffBack2 INVOKE Parameters..................................................................... 75 HandoffBack2 RETURN RESULT Parameters ...................................................... 77 HandoffMeasurementRequest2 INVOKE Parameters ............................................... 78 HandoffToThird2 INVOKE Parameters ................................................................ 81 HandoffToThird2 RETURN RESULT Parameters.................................................. 83 InterSystemPage INVOKE Parameters................................................................. 85 InterSystemPage2 INVOKE Parameters............................................................... 87 MSInactive INVOKE Parameters........................................................................ 89 QualificationDirective INVOKE Parameters.......................................................... 90 QualificationRequest INVOKE Parameters ........................................................... 92 QualificationRequest RETURN RESULT Parameters............................................. 93 RegistrationNotification INVOKE Parameters....................................................... 94 RoutingRequest INVOKE Parameters.................................................................. 97 IS-41 MAP Parameter Identifiers (continued) ........................................................ 99 IS-41 MAP Parameter Identifiers (continued) .......................................................100 AuthorizationDenied Reason value.....................................................................101 SignalQuality value........................................................................................104 TDMAChannelData value................................................................................107 TerminalType value........................................................................................109 TransactionCapability parameter........................................................................111 TransactionCapability parameter (concluded)........................................................112 BSMCStatus value .........................................................................................114 ControlChannelMode value..............................................................................115 NonPublicData parameter.................................................................................117 PagingFrameClass value..................................................................................118 PSID_RSIDInformation value ..........................................................................120
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
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
Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13
ServicesResult parameter .................................................................................122 SOCStatus value ...........................................................................................123 TDMAServiceCode value.................................................................................126 TDMATerminalCapability value .......................................................................128 TDMATerminalCapability value (concluded)) ......................................................129 TDMAVoiceCoder value..................................................................................130 User Group value ...........................................................................................131
List of Tables
N.S0007-0 v 1.0
July 19, 1997
LIST OF FIGURES
Figure 4 Figure 9 Figure 12 Figure 15 Figure 0 Figure 43 Figure 44 Figure 48 Figure 49 Figure 52 Figure 53 Figure 65 Figure 69 Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 115 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 20 Figure 105 Figure 129 Figure 168 Figure 169 Successful FacilitiesDirective2........................................................................... 15 Successful HandoffBack2 .................................................................................. 18 Successful HandoffMeasurementRequest2............................................................. 21 Successful HandoffToThird2 .............................................................................. 24 Successful Handoff-Forward for MAHO with Measurement Confirmation .................. 28 Successful MSInactive: MS Declared Inactive....................................................... 30 Successful MSInactive: MS Deregistered ............................................................. 32 Successful QualificationDirective: Re-authorization and Update Profile ...................... 34 Successful QualificationDirective: Update Profile Only........................................... 35 Successful QualificationRequest: Authorization Confirmed and Profile Returned......... 36 Successful QualificationRequest: Profile Returned Only.......................................... 38 Successful RegistrationNotification: Confirmed at the HLR .................................... 40 Successful Indirect RoutingRequest: TLDN Returned ............................................. 42 Initial Registration with Download of PSID/RSID List .......................................... 44 DCCH Registration ......................................................................................... 46 DCCH Call Delivery ....................................................................................... 48 QualificationDirective: Update Profile and Control Channel Mode ............................ 50 DCCH Call Termination without Profile ............................................................. 52 InterSystemPage for a DCCH Capable MS .......................................................... 53 InterSystemPage2 for a DCCH Capable MS......................................................... 54 CD Invocation to a User Group on Another MSC ................................................. 55 Initial Registration in a User Group .................................................................... 57 User Zone Registration..................................................................................... 59 UZ PSID Removal.......................................................................................... 60 Cancel Zone Change Tone ................................................................................ 62 UZ Not Supported by Serving MSC................................................................... 64 User Zone Only Service.................................................................................... 66 Preferred User Zone Service ............................................................................... 68 AuthorizationDenied parameter..........................................................................101 Profile Macro ...........................................................................................102
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
SignalQuality parameter ..................................................................................104 TDMAChannelData parameter ..........................................................................106 TerminalType parameter ..................................................................................108
56 57 58 59 60
List of Figures
vi
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
Figure 175 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Figure 20 Figure 21 Figure 22 Figure 23 Figure 24 Figure 30 Figure 25 Figure 26 Figure 27 Figure 28 Figure 29
TransactionCapability parameter........................................................................110 Base Station Manufacturer Code parameter ..........................................................113 BSMCStatus parameter ...................................................................................114 ControlChannelMode parameter ........................................................................115 NonPublicData parameter.................................................................................116 PagingFrameClass parameter ............................................................................118 PSID_RSIDInformation parameter.....................................................................119 PSID_RSIDList parameter...............................................................................121 ServicesResult parameter .................................................................................122 SOCStatus parameter......................................................................................123 SystemOperatorCode parameter.........................................................................124 TargetCellIDList parameter ..............................................................................125 TDMAServiceCode parameter ...........................................................................126 TDMATerminalCapability parameter .................................................................127 TDMAVoiceCoder parameter ............................................................................130 UserGroup parameter.......................................................................................131 UserZoneData parameter ..................................................................................132
vii
List of Figures
N.S0007-0 v 1.0
July 19, 1997
FOREWORD
The present Interim Standard (IS) contains recommendations to give networking support for Systems and Mobile Stations built according to the IS-136 and IS-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:
2 3 4 5 6 7 8 9 10 11 12
TIA/EIA-664, Cellular Features Description
13 14
This IS adds functionality to the following IS-41-C Interim Standard:
15 16 17
IS-41.2-C, Cellular Radiotelecommunications Intersystem Operations: Intersystem Handoff Information Flows IS-41.3-C, Cellular Radiotelecommunications Intersystem Operations: Automatic Roaming Information Flows IS-41.5-C, Protocols IS-41.6-C, Procedures Cellular Radiotelecommunications Intersystem Operations: Signaling
18 19 20
21 22 23 24
25 26 27 28
Cellular Radiotelecommunications Intersystem Operations: Signaling
29 30 31
Note: This document cannot be used as a standalone source of specifications. The published IS41-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.
32 33 34 35 36 37 38 39 40
REVISION HISTORY
Revision
0
41 42 43 44
Date
July 1997
Remarks
Gustavo Pavn (Ericsson) - Editor
45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
Foreword
viii
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
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 to IS-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.
Introduction
N.S0007-0 v 1.0
July 19, 1997
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 BSMCS CCM NP NPDATA PFC PRINFO PRLIST PSID RSID SERVRSLT SOC SOCS TDMASC TDMAVC TERMCAP UG UZ UZDATA Base Station Manufacturer Code BSMCStaus Parameter ControlChannelMode Parameter Non-Public Service Mode NonPublicData Parameter PagingFrameClass Parameter PSID/RSIDInformation Parameter PSID/RSIDList Parameter Private System Identifier Residential System Identifier ServicesResult Parameter System Operator Code SOCStatus Parameter TDMAServiceCode Parameter TDMAVoiceCoder Parameter TDMATerminalCapability Parameter User Group User Zone UserZoneData Parameter
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
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
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. See IS-136-A.
Private System ID (PSID) A non-public (private) system identifier that is only accessible by authorized users. See SID and IS-136-A.
Residential System Identifier (RSID) A non-public system identifier that is only accessible by users on a residential system. See SID and IS-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. See IS-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.
Introduction
N.S0007-0 v 1.0
July 19, 1997
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 Intersystem Operations: 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 NonSignaling Data Communication DMH (Data Message Handler); Telecommunications Industry Association; May 1997.
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
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
3 STAGE 1 SERVICE DESCRIPTIONS

3.1 Non-Public Service Mode (NP)
Non-Public Service Mode (NP) permits a subscriber to access available wireless service on 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 the Public 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.
Service Descriptions
Non-Public Mode Service (NP)
N.S0007-0 v 1.0
July 19, 1997
De-Registration
1 2 3 4
NP is de-registered upon de-authorization.

NP Activation
5 6 7 8
NP may be activated upon authorization.

De-Activation
9 10 11 12
NP shall be de-activated upon de-authorization.

Invocation
13 14 15 16 17
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
18 19 20 21 22 23 24 25 26 27 28 29
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
30 31 32
The private or residential system may record call detail information for the following: a. b. c. d. e. f. g. Registrations (successful and unsuccessful). Mobile originations. Mobile terminations. Features invoked. Number of UZ calls. Number of UZ calls with transition. User Zone Identifier(s) and duration in each UZ.
33 34 35 36 37 38 39 40 41 42 43 44 45 46
h. PSID/RSID/SID/NID and duration in each.
3.1.2
Exception Procedures or Unsuccessful Outcome

Registration
47 48 49 50 51 52 53 54 55
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
56 57
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).
58 59 60
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
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 Procedures
None identified.
3.1.4
Interactions With Other Wireless Services

These interactions are beyond the scope of this standard.
N.S0007-0 v 1.0
July 19, 1997
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 or failure) 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
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
UG is applicable to voice telecommunication services.
3.2.1
Normal Procedures With Successful Outcome

Authorization
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
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:
User Group (UG)
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
Table 1
UG Subscription Options Values

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.
Subscription Options
Membership Type
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.
User Group (UG)
N.S0007-0 v 1.0
July 19, 1997
Invocation
1 2 3 4 5 6 7
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
8 9 10 11 12 13 14 15 16 17
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
18 19 20 21 22 23 24 25
The system should record call detail information for the following: a. Mobile Terminations.
26 27 28 29 30 31
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
32 33 34 35 36 37
None identified.
De-Registration
38 39 40 41
None identified.
Activation
42 43 44 45 46
If the subscriber is already active in the specified group, the user shall receive feature confirmation.
De-Activation
47 48 49 50 51
If the subscriber is already inactive in the specified group, the user shall receive feature confirmation.
Invocation
52 53 54
None identified.
Exceptions While Roaming
55 56 57 58 59 60
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
User Group (UG)
10
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
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.
11
User Group (UG)
N.S0007-0 v 1.0
July 19, 1997
Conference Calling (CC)
1 2 3 4
None identified.
Do Not Disturb (DND)
5 6 7 8
None identified.
Emergency Services (9-1-1)
9 10 11 12
None identified.
Flexible Alerting (FA)
13 14 15 16
None identified.
Group 3 Facsimile Service (G3 Fax)
17 18 19 20
None identified. User Group ID applies to voice telecommunications service only.

Incoming Call Screening (ICS)
21 22 23 24 25
None identified. Incoming calls to a User Group directory number are not subject to Incoming Call Screening.
Message Waiting Notification (MWN)
26 27 28 29
None identified.
Mobile Access Hunting (MAH)
30 31 32
None identified.
Network Directed System Selection (NDSS)
33 34 35 36
None identified.
37 38 39 40
None identified.
Over-the-Air Activation (OTA)
41 42 43 44
None identified.
Password Call Acceptance (PCA)
45 46
None identified.
Preferred Language (PL)
47 48 49 50
None identified.
Priority Access and Channel Assignment (PACA)
51 52 53 54 55 56
None identified.
Remote Feature Control (RFC)
57 58 59 60
None identified.
User Group (UG)
12
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
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.
13
User Group (UG)
N.S0007-0 v 1.0
July 19, 1997
4 INTERSYSTEM HANDOFF INFORMATION FLOWS

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 Case 1 Case 2 Case 3 Anchor MSC Serving MSC Tandem MSC RESPONDING FE Target MSC Target MSC Target MSC
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
One of two possible results is returned: 1. 2. Notification that the request was accepted, including the parameters of the voice channel selected by the Target MSC on the designated cell. Notification that the request was unsuccessful because a voice channel on the designated cell is not available.
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
1The MobileOnChannel operation is included here because it completes the transaction
57 58 59 60
initiated with the FacilitiesDirective2 operation.
FacilitiesDirective2
14
Intersystem Handoff Operations
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
4.2.1
Successful FacilitiesDirective2 (IS-41.2-C Page10)

This scenario describes the successful use of the FacilitiesDirective2 operation.
Serving System MSC Target System MSC
FACDIR2 [RequestedServiceInfo, RequestedTargetInfo]
HOT
facdir2 [GrantedServiceInfo, GrantedTargetInfo] b
MSONCH [ ]
Figure 4
Successful FacilitiesDirective2
15
N.S0007-0 v 1.0
July 19, 1997
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 RequestedServiceInformation [ChannelData] Usage Set of parameters for Requested Service Information Indicates the SAT Color Code, Voice Mobile Attenuation Code, DTX-Mode, and the channel number of the serving channel, if analog. Indicates the Rate, Digital Verification Color Code, Digital Mobile Attenuation Code, DTX-Mode, Hyperband, and the channel number of the serving channel, if TDMA. Identifies the requested Service Code used in this call. (Extension to the TDMACallMode parameter). Identifies the base station manufacturer code of the serving Base Station. Identifies the system operator code associated with the served MS. 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. Indicates the radio frequency interface standard supported by the associated MS. O Type
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
[TDMAChannelData]
20 21 22 23 24
[TDMAServiceCode]
25 26 27
[BSMC] [SOC] [TDMATerminalCapability]
O O O
28 29 30 31 32 33 34 35 36 37 38 39 40
TerminalType
41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
16
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
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 GrantedTargetInfo: [ChannelData] Usage Set of parameters for Target Service Information. Indicates the SAT Color Code, Voice Mobile Attenuation Code, DTX-Mode, and the channel number of the target channel, if analog. 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. Set of parameters for Granted Service Information. Indicates whether or not the BSMC in the target environment is the same as that of the Base Station currently serving the MS. Indicates whether or not the SOC in the target environment is the same as that currently associated with the served MS. Identifies the actual Voice Coder provided by the target Base Station O O Type
[TDMAChannelData]
GrantedServiceInfo: [BSMC-Status]
[SOC-Status]
[TDMAVoiceCoder]
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).
17
N.S0007-0 v 1.0
July 19, 1997
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 addition of 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 Case 1 Serving MSC RESPONDING FE Target MSC
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
4.5.1
Successful HandoffBack2 (IS-41.2-C Page 19)

This scenario describes the successful use of the HandoffBack2 operation.
Serving System MSC Target System MSC
20 21 22 23 24 25 26 27 28 29 30
HANDBACK2 [RequestedTargetInfo, RequestedServiceInfo]
31
32 33
HOT
handback2 [GrantedTargetInfo, GrantedServiceInfo] b
34 35 36 37 38
Figure 9
Successful HandoffBack2
39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
HandoffBack2
18
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
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 RequestedServiceInfo [ChannelData] Usage Set of parameters for Requested Service Information. Indicates the SAT Color Code, Voice Mobile Attenuation Code, DTX-Mode, and the channel number of the serving channel, if analog. Indicates the Rate, Digital Verification Color Code, Digital Mobile Attenuation Code, DTX-Mode, Hyperband, and the channel number of the serving channel, if TDMA. Identifies the base station manufacturer code of the serving Base Station. Identifies the system operator code associated with the served MS. Identifies the requested Service Code used in this call. (Extension to the TDMACallMode parameter). Indicates the radio frequency interface standard supported by the associated MS. 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. Indicates the Voice Coder capabilities of the Mobile Station O Type
[TDMAChannelData]
[BSMC] [SOC] [TDMAServiceCode]
O O O
[TerminalType] [TDMATerminalCapability]
O O
[TDMAVoiceCoder]
19
HandoffBack2
N.S0007-0 v 1.0
July 19, 1997
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 GrantedTargetInfo: [ChannelData] Usage Set of parameters for Target Service Information. Indicates the SAT Color Code, Voice Mobile Attenuation Code, DTX-Mode, and the channel number of the target channel, if analog. 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. Set of parameters for Granted Service Information. Indicates whether or not the BSMC in the target environment is the same as that of the Base Station currently serving the MS. Indicates whether or not the SOC in the target environment is the same as that currently associated with the served MS. Identifies the actual Voice Coder provided by the target Base Station O O Type
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
[TDMAChannelData ]
16 17 18 19 20 21
GrantedServiceInfo: [BSMC-Status]
22 23 24 25 26 27 28
[SOC-Status]
29 30 31 32
[TDMAVoiceCoder]
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
20
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
4.7
HandoffMeasurementRequest2
The HandoffMeasurementRequest2 (HANDMREQ2) operation is sent by the Serving MSC to any adjacent MSCs to request a signal quality measurement on the specified channel. This operation differs from the HandoffMeasurementRequest operation in its addition of support for CDMA and multi-band TDMA MSs. The following table lists the possible combinations of invoking and responding FEs. Table 8 FE Combinations for HANDMREQ2 INVOKING FE Case 1 Serving MSC RESPONDING FE Adjacent MSC
4.7.1
Successful HandoffMeasurementRequest2 (IS-41.2-C Page 26)

This scenario describes the successful use of the HandoffMeasurementRequest2 operation where signal quality measurements are returned.
Serving System MSC Adjacent System MSC
HANDMREQ2 [CurrentServingInfo]
LMMRT
handmreq2 [MeasurementInfo] b
Figure 12 a.
Successful
The Serving MSC elects, based on its internal algorithm, to determine if a handoff to an adjacent candidate MSC is appropriate. The Serving MSC sends a HANDMREQ2 to the candidate MSC (the Serving MSC may send several handoff measurement requests to different candidate MSCs).
21
N.S0007-0 v 1.0
July 19, 1997
Parameters are as in Section 4.6.1, Step-a, with the exception that ChannelInfo1 is not included and with the following additions: Parameters CurrentServingInfo: [ChannelData] Usage Set of parameters for Current Serving Information Indicates the SAT Color Code, Voice Mobile Attenuation Code, DTX-Mode, and the channel number of the target channel, if analog. 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. 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. Indicates TargetCellIDs from which measurements of MS signal strength need to be made. O Type
1 2 3 4 5 6 7 8 9 10 11 12
[TDMAChannelData]
13 14 15 16 17 18
[TDMATerminalCapability]
19 20 21 22 23 24 25
TargetCellIDList
26 27 28 29
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.
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
22
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
The results are returned to the Serving MSC in a handmreq2.

Parameters MeasurementInformation: [CDMATargetMeasurementList] [TargetMeasurementList] Usage A list of parameters with Measurement Information Include for CDMA. Include for AMPS, NAMPS or TDMA. O O Type
23
N.S0007-0 v 1.0
July 19, 1997
4.9
HandoffToThird2
The HandoffToThird2 (HANDTHIRD2) operation is used by the Serving MSC (nonAnchor) 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 Combinations for HANDTHIRD2
INVOKING FE Case 1 Case 2 Case 3 Serving MSC Serving MSC Tandem MSC RESPONDING FE Anchor MSC Tandem MSC Tandem MSC
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
4.9.1
Successful HandoffToThird2 (IS-41.2-C Page 33)

This scenario describes the successful use of the HandoffToThird2 operation.
Serving System MSC Anchor System MSC
21 22 23 24 25 26 27 28 29 30 31 32
HANDTHIRD2 [RequestedServiceInfo, RequestedTargetInfo]
33 34 35
HTTT
handthird2 [GrantedServiceInfo, GrantedTargetInfo] b
36 37 38 39
Figure 15
Successful HandoffToThird2
40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
HandoffToThird2
24
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
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 not included and with the following additions: Parameters RequestedServiceInfo: [ChannelData] Usage Set of parameters for Requested Service Information Indicates the SAT Color Code, Voice Mobile Attenuation Code, DTX-Mode, and the channel number of the serving channel, if analog. Indicates the Rate, Digital Verification Color Code, Digital Mobile Attenuation Code, DTX-Mode, Hyperband, and the channel number of the serving channel, if TDMA. Identifies the base station manufacturer code of the serving Base Station. Identifies the system operator code associated with the served MS. Identifies the requested Service Code used in this call. (Extension to the TDMACallMode parameter). Indicates the radio frequency interface standard supported by the associated MS. 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. Indicates the Voice Coder capabilities of the Mobile Station. O Type
[TDMAChannelData ]
[BSMC] [SOC] [TDMAServiceCode]
O O O
[TerminalType] [TDMATerminalCapability]
O O
[TDMAVoiceCoder]
25
HandoffToThird2
N.S0007-0 v 1.0
July 19, 1997
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 GrantedServiceInformation: [BSMC-Status] Usage Set of parameters for Granted Service Information. Indicates whether or not the BSMC in the target environment is the same as that of the Base Station currently serving the MS. Indicates whether or not the SOC in the target environment is the same as that currently associated with the served MS. Identifies the actual Voice Coder provided by the target Base Station Set of parameters for Target Service Information. Indicates the SAT Color Code, Voice Mobile Attenuation Code, DTX-Mode, and the channel number of the target channel, if analog. 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 O Type
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
[SOC-Status]
16 17 18 19
[TDMAVoiceCoder]
20 21 22
GrantedTargetInfo: [ChannelData]
23 24 25 26 27 28 29 30
[TDMAChannelData ]
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
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
5.10
Successful Handoff-Forward for MAHO with Measurement 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 not include 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.
Basic Intersystem Handoff Scenarios
27
Measurement Confirmation
N.S0007-0 v 1.0
July 19, 1997
1 2
Handoff-Forward for MAHO with Measurement Confirmation
3 4 5 6 7
Initial Connections
A X Y
Anchor & Serving System A MSC Target System B MSC
8 9
10 11 12 13 14 15 16
Served MS X MS
17 18 19 20 21 22
call in progress MAHO measurements HANDMREQ [TargetCellIDList]
a b c d e facdir f g X arrives on new channel h MSONCH i j
23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45
LMMRT
FACDIR QUERY w/ PERMISSION
handmreq
HOT
SINGLE TCAP TRANSACTION CONV w/ PERMISSION handoff order
MAT
MHOT
RESPONSE
handoff complete
Resulting Connections
A Y X B
46 47 48 49 50 51 52 53
Figure 0 a.
Successful Handoff-Forward for MAHO with Measurement Confirmation A call involving the served MS is in progress.
54 55 56 57 58 59 60
28
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
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. 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. The MSC performs location measurements for the cells and sectors identified in the TargetCellIDList, in accordance with the MSCs internal algorithm and returns the results to the Serving MSC in a handmreq or handmreq2. The Serving MSC compares the MAHO measurement received from the MS to the measurement made by the corresponding cells or sector. If the comparison shows that the two measurements are widely differing in value, then the MSC determines that this cell or sector is suspect and will avoid handing the MS off to it. If the comparison is within some reasonable limit (based on an internal algorithm), then the Serving MSC determines that the call should be handed off to the candidate (now Target) MSC and that the Target MSC is not already on the call path. It sends a FACDIR to the Target MSC, directing the Target MSC to initiate a HandoffForward task. A voice channel on the designated target cell is available; therefore, the Target MSC increases the Segment Counter in the received BillingID parameter by one and uses the new BillingID for the new call segment, returns a facdir to the requesting MSC, and initiates a Handoff-Forward task. On receipt of the facdir, the Serving MSC sends a Mobile Handoff Order to the served MS. The MS is received on the designated voice channel; therefore, ... ...the Target MSC completes the voice path between the voice channel and the interMSC trunk and sends a MSONCH to the initiator of the Handoff-Forward task, the Serving MSC, informing the requesting system that the Target MSC has successfully completed the Handoff-Forward task. The Serving MSC, on receipt of the MSONCH, completes the handoff process. The interMSC trunk should be connected at this time if it has not already been connected.
c.
d.
e.
f.
g h. i.
29
N.S0007-0 v 1.0
July 19, 1997
5 AUTOMATIC ROAMING INFORMATION FLOWS

4.19
4.19.1
2 3 4 5 6
MSInactive
Successful MSInactive: MS Declared Inactive (IS-41.3-C Page 83)
This operation scenario describes the use of the MSInactive operation to declare an MS inactive.
Serving System MSC VLR HLR
7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
MSINACT [MIN, ESN, LOCID, SERVRSLT]
23
24 25
MSIT
msinact [ ] b
26 27 28 29 30 31
MSINACT [MIN, ESN, LOCID]
32
33 34
MSIT
msinact [ ] d
35 36 37 38
Figure 43 a.
Successful MSInactive: MS Declared Inactive
39 40 41 42 43 44 45 46
If the Serving MSC determines that an MS is no longer active, it may report the MSs inactivity by sending an MSINACT to the Serving VLR.
Parameters MIN ESN LOCID SERVRSLT Usage Served MS MIN. Served MS ESN. MSs LocationAreaID. Include if available. Result of a service action (e.g., PSID/RSID download to a MS in a User Zone). Type R R O O
47 48 49 50 51 52
b. c.
The Serving VLR sends an empty msinact to the Serving MSC. The Serving VLR determines that an MS is inactive based either on the receipt of an MSINACT from the Serving MSC or on internal algorithms. It may report the MSs inactivity by sending an MSINACT to the HLR. The HLR sends an empty msinact to the Serving VLR.
53 54 55 56 57 58
d.
59 60
MSInactive
30
Automatic Roaming Operations
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
31
MSInactive
N.S0007-0 v 1.0
July 19, 1997
4.19.2
Successful MSInactive: MS Deregistered (IS-41.3-C Page 84)

This operation scenario describes the use of the MSInactive operation to deregister an MS and convey the CallHistoryCount from the VLR, through the HLR to the AC.
Serving System
2 3 4 5 6 7 8 9 10
MSC
VLR
HLR
AC
11 12 13
MSINACT [MIN, ESN, LOCID, DEREG, SERVRSLT]
14
15 16
MSIT
msinact [ ] b
17 18 19 20
MSINACT [MIN, ESN, LOCID, DEREG, COUNT, SERVRSLT]
21
22 23
MSIT
msinact [ ] d
24 25 26 27
MSINACT [MIN, ESN, COUNT]
28 29 30
MSIT
msinact [ ] f
31 32 33 34 35
Figure 44 a.
Successful MSInactive: MS Deregistered
36 37 38 39 40 41 42 43 44 45 46
The Serving MSC determines that deregistration of a served MS is required. This may be due to receipt of an MS power-down indication, MS inactivity, or loss of radio contact. The Serving MSC sends an MSINACT, including a DeregistrationType parameter, to its VLR. At this point, the MSC may choose to remove all record of the MS from its memory.
Parameters MIN ESN DEREG LOCID SERVRSLT Usage Served MS MIN. Served MS ESN. Indication that MS is to be deregistered. MSs LocationAreaID. Include if available. Result of a service action (e.g., PSID/RSID download to a MS in a User Zone). Type R R R O O
47 48 49 50 51 52 53 54
b. c.
Same as Section 4.19.1, Step-b. The Serving VLR determines that deregistration of an MS is required based either on the receipt of an MSINACT from the Serving MSC or on internal algorithms. It
55 56 57 58 59 60
MSInactive
32
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
sends an MSINACT, including a DeregistrationType parameter, to the HLR. At this point, the VLR may choose to remove all record of the MS from its memory.
Parameters are as in Step-a, with the following addition: Parameters COUNT Usage CallHistoryCount. Include if MS registration is canceled and if SSD is shared. Type O
d. e.
The HLR sends an empty msinact to the Serving VLR and removes its pointer to the VLR. If SSD is shared and CallHistoryCount was received from the Serving VLR, the HLR sends an MSINACT to the AC.
Parameters MIN ESN COUNT Usage Served MS MIN. Served MS ESN. CallHistoryCount received from VLR. Type R R R
f.
The AC sends an empty msinact to the HLR.
33
MSInactive
N.S0007-0 v 1.0
July 19, 1997
4.21
4.21.2
QualificationDirective
Successful QualificationDirective: Re-authorization and Update Profile (IS-41.3-C Page 92)
This operation scenario describes the QualificationDirective operation when authorization is confirmed and the MSs profile is also supplied.
Serving System HLR VLR MSC
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
QUALDIR [MIN, ESN, MYTYP, QUALCODE, AUTHPER, Profile]
18 19 20 21
QDT
qualdir [ ] b
22 23 24 25
QUALDIR [MIN, ESN, MYTYP, LOCID, QUALCODE, AUTHPER, Profile]
26
27 28
QDT
qualdir [ ] d
29 30 31 32 33
Figure 48
Successful QualificationDirective: Re-authorization and Update Profile a-d. Same as Section 4.20.1, Steps a-d.
Parameters are as in Section 4.20.1, Steps a-d, with the following modifications to both Steps a and c: Parameters QUALCODE Profile: [PSID/RSIDList] [UserGroup] Usage Type of qualification = validation and profile. Subscribers profile information: List of acceptable PSIDs/RSIDs for the indicated MS. Indicates the User Group allocation Status. O O Type R
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
Note: Steps c and d are optional and are executed only if the service or call in progress may be discontinued.
34
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
4.21.3
Successful QualificationDirective: Update Profile Only (IS41.3-C Page 94)

This operation scenario describes the QualificationDirective operation when the request is to update the MSs profile only.
QUALDIR [MIN, ESN, MYTYP, QUALCODE, Profile {NonPublicData, UserZoneData}]
QDT
qualdir [ ] b
QUALDIR [MIN, ESN, MYTYP, LOCID, QUALCODE, Profile{NonPublicData, UserZoneData}]
QDT
qualdir [ ] d
Figure 49
Successful QualificationDirective: Update Profile Only
a-d. Same as Section 4.21.2, Steps a-d.

Parameters are as in Section 4.21.2, Steps a-d, with the AUTHPER parameter omitted in Steps a and c, and with the following modification to both Steps a and c: Parameters QUALCODE Profile: NonPublicData UserZoneData Usage Type of qualification = profile only. Subscribers profile information: Used to update a subscriber's User Zone related attributes, applicable in all MSCs. Used to update a subscriber's User Zone identifier information on a per-MSCID basis. O O Type MBC
35
N.S0007-0 v 1.0
July 19, 1997
4.22
4.22.2
QualificationRequest
Successful QualificationRequest: Authorization Confirmed and Profile Returned (IS-41.3-C Page 99)
This operation scenario describes the QualificationRequest operation when authorization is confirmed and the MSs profile is also requested.
2 3 4 5 6 7 8 9 10 11 12 13 14 15
QUALREQ [MIN, ESN, MSCID, MYTYP, QUALCODE, SYSACCTYPE, TRANSCAP, UserGroup] a QUALREQ [MIN, ESN, MSCID, MYTYP, QUALCODE, SYSACCTYPE, TRANSCAP, UserGroup] b
16 17 18 19 20 21 22 23 24 25
QRT
QRT
qualreq [AUTHPER, HLRID, MYTYP, Profile]
26
27 28 29 30
qualreq [AUTHPER, HLRID, MYTYP, Profile]
31 32 33 34 35
Figure 52
Successful QualificationRequest: Authorization Confirmed and Profile Returned a-b. Same as Section 4.22.1, Steps a-b.
Parameters are as in Section 4.22.1, Steps a-b, with the following modification to both Steps a and b: Parameters QUALCODE Usage Type of request = validation and profile. Type R
36 37 38 39 40 41 42 43 44 45
a.
After determining that a roaming MS is now within its service area or that a previously registered roaming MS has requested activation in a new User Group, the Serving MSC sends a QUALREQ to its VLR. The Serving MSC may detect the MSs presence through autonomous registration, call origination, call termination (i.e., a page response following a call to the roamer port) or a service order.
46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
36
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
Parameters MIN ESN MSCID MYTYP QUALCODE SYSACCTYPE TRANSCAP
Usage Served MS MIN. Served MS ESN. Serving MSC MSCID. Serving MSC vendor identification. Type of request = validation and profile. Indicates the type of system access. Indicates the serving systems transaction capability at the current time. Specifies the MS users request for User Group allocation or de-allocation.
Type R R R MBC R R R
UserGroup
b. c.
Same as Step a. The HLR determines that authorization can be granted to the MS and returns this indication, as well as the MSs profile, to the Serving VLR in the qualreq.
Parameters are as in Section 4.21.1, Step-c, with the following addition: Parameters Profile: [PSID/RSIDList] [UserGroup] Usage Subscribers profile information: List of acceptable PSIDs/RSIDs for the MS. Indicates the User Group allocation Status. O O Type
d.
The VLR sends a qualreq to the Serving MSC.

Parameters are as in Step-c, with the following modification: Parameters HLRID [MSCID] MYTYP Usage HLR MSCID. Include if received in Step-c. VLR vendor identification. Type O MBC
37
N.S0007-0 v 1.0
July 19, 1997
4.22.3
Successful QualificationRequest: Profile Returned Only (IS-41.3-C Page 102)

This operation scenario describes the QualificationRequest operation when the request is to retrieve the MSs profile only.
Serving System MSC VLR QUALREQ [MIN, ESN, MSCID, MYTYP, QUALCODE, SYSACCTYPE, TRANSCAP] a QUALREQ [MIN, ESN, MSCID, MYTYP, QUALCODE, SYSACCTYPE, TRANSCAP] b HLR
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
QRT
QRT
qualreq [HLRID, MYTYP, Profile{NonPublicData, UserZoneData]
24 25 26
qualreq [HLRID, MYTYP, Profile{NonPublicData, UserZoneData}]
27
28 29 30 31
Figure 53
Successful QualificationRequest: Profile Returned Only
a-b. Same as Section 4.22.1, Steps a-b.

Parameters are as in Section 4.22.1, Steps a-b, with the following modification to both Steps a and b: Parameters QUALCODE Usage Type of request = profile only. Type R
32 33 34 35 36 37 38 39
c.
The HLR retrieves the MSs profile and returns it to the Serving VLR in the qualreq. Parameters are as in Section 4.22.2, Step-c, with the deletion of the AUTHPER parameter and the addition of User Zone parameters as shown below.
40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
38
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
Parameters are as in Section 4.22.2, Step-c, with the following modifications: Parameters MYTYP HLRID [MSCID] Profile: NonPublicData UserZoneData Usage VLR vendor identification. HLR MSCID. Include if received in Step-c. Subscribers profile information: Used to update a subscriber's User Zone related attributes, applicable in all MSCs. Used to update a subscriber's User Zone identifier information on a per-MSCID basis. O O Type MBC O
d.
The VLR sends a qualreq to the Serving MSC.

Parameters are as in Section 4.22.2, Step-c, with the following modifications: Parameters MYTYP HLRID [MSCID] Profile: NonPublicData UserZoneData Usage VLR vendor identification. HLR MSCID. Include if received in Step-c. Subscribers profile information: Used to update a subscriber's User Zone related attributes, applicable in all MSCs. Used to update a subscriber's User Zone identifier information on a per-MSCID basis. O O Type MBC O
39
N.S0007-0 v 1.0
July 19, 1997
4.27
4.27.2
RegistrationNotification
Successful RegistrationNotification: Confirmed at the HLR (IS-41.3-C Page 120)
This operation scenario describes the RegistrationNotification operation when confirmed at the HLR.
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
REGNOT [IDInfo, QUALCODE, SYSACCTYPE, TERMTYPE, AVTYP, SMSADDR, AuthError, BORDERACC, AccessInfo, TRANSCAP] a REGNOT [IDInfo, QUALCODE, SYSACCTYPE, TERMTYPE, AVTYP SMSADDR, AuthError, BORDERACC, AccessInfo, TRANSCAP] b
17 18 19 20 21 22 23 24
RNT
RNT regnot [AUTHPER, MYTYP, HLRID, Profile{NonPublicData, UserZoneData}]
25 26 27
28 29
regnot [AUTHPER, MYTYP, Profile{NonPublicData, UserZoneData}] d
30 31 32 33
Figure 65 a.
Successful RegistrationNotification: Confirmed at the HLR Same as Section 4.27.1, Step-a, with the addition of the following parameter.
Parameters IDInfo: [UserGroup] Usage Set of identification parameters in REGNOT: Specifies the MS users request for User Group allocation or de-allocation. O Type
34 35 36 37 38 39 40 41 42 43 44
b.
The Serving VLR determines that either (a) the MS had previously registered with an MSC within the domain of the VLR but the MS has been reported inactive by the VLR, (b) the MS is not known to the VLR, or (c) the requested information cannot be made available for the indicated MS. Under these conditions, the Serving VLR forwards the REGNOT to the HLR associated with the MS.
45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
40
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
Parameters are as in Step-a, with the following modifications: Parameters [PC_SSN] [MYTYP] Usage Serving VLR PC_SSN. Include if SS7 carriage services are used. Serving VLR vendor identification. Type O MBC
c.
The HLR determines that authorization can be granted to the MS. requested information to the Serving VLR in the regnot.
It returns the
Parameters are as in Section 4.27.1, Step-b, with the following additions and modifications: Parameters HLRID [MSCID] MYTYP Profile: [PSID/RSIDList] [UserGroup] NonPublicData UserZoneData Usage HLR MSCID to key MS record against for a subsequent UnreliableRoamerDataDirective. HLR vendor identification. Subscribers profile information. Include if profile requested in QUALCODE: List of acceptable PSIDs/RSIDs for the MS. Indicates the User Group allocation Status. Used to update a subscriber's User Zone related attributes, applicable in all MSCs. Used to update a subscriber's User Zone identifier information on a per-MSCID basis. O O O O Type R MBC
d.
The VLR forwards the regnot to the Serving MSC.

Parameters are as in Step-c, with the exception that the HLRID parameter is not included and with the following modification: Parameters MYTYP Profile: NonPublicData UserZoneData Usage VLR vendor identification. Subscribers profile information. Include if profile requested in QUALCODE: Used to update a subscriber's User Zone related attributes, applicable in all MSCs. Used to update a subscriber's User Zone identifier information on a per-MSCID basis. O O Type MBC
41
N.S0007-0 v 1.0
July 19, 1997
4.30
4.30.1
RoutingRequest
Successful Indirect RoutingRequest: TLDN Returned (IS-41.3-C Page 128)
This operation scenario describes a successful indirect RoutingRequest operation (i.e., via the VLR), with a TLDN returned.
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
ROUTREQ [RoutReqID, TERMTRMT, TERMTRIG, ALRTCODE, LEGINFO, OTFI, CNIinfoASCII, DMHData, VMSPIN, VMBOX] a ROUTREQ [RoutReqID, TERMTRMT, TERMTRIG, ALRTCODE, LEGINFO, OTFI, CNIinfoASCII, DMHData, VMSPIN, VMBOX] b
17 18 19 20 21 22 23 24
RRT
RRT
routreq [MSCID, BILLID, PC_SSN, TLDN] c
25 26 27 28 29 30
routreq [MSCID, BILLID, PC_SSN, TLDN]
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
Figure 69
Successful Indirect RoutingRequest: TLDN Returned
RoutingRequest
42
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
a.
The HLR sends a ROUTREQ to the Serving VLR.

Parameters RoutReqID [BillingID] [MIN] [ESN] [MSCID] [UserGroup] Usage Set of identification parameters in ROUTREQ: Call ID for billing and redirection purposes. Served MS MIN. Served MS ESN. Originating MSC MSCID for use in any subsequent redirection. Specifies the User Group identifier for special UG paging. R R R R O Type
b. c.
The VLR forwards the ROUTREQ to the Serving MSC. Parameters are as in Step-a. If TerminationTreatment indicates termination to an MS, the Serving MSC consults its internal data structures to determine if the MS is already engaged in a call on this MSC. If termination is to a voice mailbox, the Serving MSC will verify the VMS availability. Finding the MS or VMS able to accept incoming calls, the Serving MSC allocates a TLDN (Temporary Local Directory Number) and returns this information to the VLR in the routreq.
Parameters MSCID BILLID TLDN [DGTSDEST] PC_SSN Usage Serving MSC MSCID for use in subsequent inter-MSC call. Terminating billing ID. Required for recording purposes. Temporary Local Directory Number for interMSC call routing. Serving MSC PC_SSN. Include if SS7 carriage services are used. Type R R R O
d.
The VLR forwards the routreq to the HLR. Parameters are as in Step-c.
43
RoutingRequest
N.S0007-0 v 1.0
July 19, 1997
5.1
5.1.a
Registration
Initial Registration with Download of PSID/RSID List (new)
This scenario describes initial MS registration with download of acceptable PSIDs and RSIDs to the Serving MSC.
New Serving System Old Serving System HLR VLR-1 MSC-1
2 3 4 5 6 7 8 9 10 11 12
MS
MSC-2
VLR-2
13 14 15
omt (PSID/RSIDIndMatch=1) register REGNOT REGNOT REGCANC REGCANC
16
a b c d e f regcanc g h i j k
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
RNT
RNT
RCT
regcanc regnot [PSID/RSIDList]
RCT
regnot [PSID/RSIDList] register accept (PSID/RSIDIDs)
38 39 40 41
Figure 1
Initial Registration with Download of PSID/RSID List
42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
Registration
44
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
a.
The MS determines from the Overhead Message Train (OMT) that its new system either is on its PSID/RSID approved list or allows for attempted independent match from an MS (PSID/RSID Independent Match =1). The MS sends a registration message to the Serving MSC. After receiving the registration message from the MS, the Serving MSC sends a REGNOT to its VLR. Since the MS is unrecognized by the VLR, the VLR sends a REGNOT to the HLR associated with the MS. Note that the regnot from the VLR to the MSC is contingent upon the response received from the HLR. Since the MS was previously registered elsewhere, the HLR sends a REGCANC to the previously visited VLR (VLR-1). That VLR, upon receipt of the cancellation message, essentially removes all record of the MS from its memory. VLR-1 sends a REGCANC to the previously visited MSC (MSC-1). That MSC, upon receipt of the cancellation message, essentially removes all record of the MS from its memory. MSC-1 sends a regcanc to VLR-1. VLR-1 sends a regcanc to the HLR. The HLR sends a regnot to the VLR including a list of PSIDs/RSIDs and the necessary accompanying information. VLR sends a regnot to MSC-2. The MSC responds to the MS with a registration accept (specific to IS-136), including a list of PSID/RSID IDs. This list may not be the same list passed down in the regnot from the HLR. It is possible that the list has been "filtered" by the MSC.
b. c. d.
e.
f.
g. h. i. j. k.
DCCH Automatic Roaming Operations
45
Registration
N.S0007-0 v 1.0
July 19, 1997
5.7
DCCH Operations (new)

This section illustrates the following new DCCH registration scenarios: DCCH Registration for New Control Channel Mode. DCCH Call Delivery. Qualification Directive to update Profile and Control Channel Mode. DCCH Call Termination without Profile. InterSystemPage for a DCCH Capable MS. InterSystemPage2 for a DCCH Capable MS.
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
5.7.1
DCCH Registration (new)

This scenario describes the registration and validation process as a DCCH Capable MS changes control channel mode.
Serving System HLR VLR-2 MSC-2
18 19 20 21 22 23 24 25 26 27
REGNOT [CCM] REGNOT [CCM]
28
a b
29 30 31 32 33 34 35
RNT RNT
regnot[profile, CCC] c regnot[profile, CCC] d
36 37 38 39 40 41
Figure 2
DCCH Registration
42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
DCCH Roaming
46
Basic Roaming Operations
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
a.
After determining that a roaming MS within its service area has changed control channel mode, the Serving MSC may send a REGNOT to its VLR with an indication of the accessed Control Channel Mode
Parameters ControlChannelMode Usage Indicates whether an analog or digital control channel was used by the MS in this access. Type O
b. c. h.
The VLR optionally sends a REGNOT to the HLR associated with the MS. message relays the accessed Control Channel Mode.
The
The HLR sends a regnot to the VLR. This message contains the Subscribers profile and Terminal Type. The VLR sends a regnot to the MSC. The profile, Terminal Type is included in the message.
47
DCCH Roaming
N.S0007-0 v 1.0
July 19, 1997
5.7.2
DCCH Call Delivery (new)

This scenario describes call delivery to a DCCH capable MS that is outside the serving area of the MSC where the call originates. The Serving MSC can interact with its associated HLR and VLR to obtain DCCH information for an MS.
Originating System MSC call origination LOCREQ [DGTSDIAL] ROUTREQ [MIN, CCM] ROUTREQ [MIN, CCM] HLR Serving System VLR MSC
2 3 4 5 6 7 8 9 10 11 12 13 14
a b c d e f
15 16 17 18 19 20 21 22 23 24 25 26 27
RRT
QUALREQ
RRT
QUALREQ
LRT
qualreq
QRT
qualreq
QRT
g h i j
28 29 30 31 32 33 34 35 36
routreq[TLDN] routreq locreq call setup
TLDNAT
k l
37 38 39 40 41 42 43 44
Figure 3 a. b. c.
DCCH Call Delivery
A call origination is received by the Originating MSC. The Originating MSC sends a LOCREQ to the HLR associated with the MS. The HLR sends a ROUTREQ to the VLR where the MS is registered. The latest Control Channel Mode is included in the message.
Parameters ControlChannelMode Usage Indicates the preferred Control Channel Mode used to page the MS. Type O
45 46 47 48 49 50 51 52 53 54 55
d.
The VLR then forwards the ROUTREQ to the current Serving MSC. In reaction to the ROUTREQ, the Serving MSC pages the MS on the appropriate Control Channel.
56 57 58 59 60
DCCH Roaming
48
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
Parameters ControlChannelMode
Usage Indicates the preferred Control Channel Mode used to page the MS.
Type O
e. f.
The Serving MSC may then obtain the service profile of the MS from its VLR by sending it a QUALREQ. If the MS is unknown to the VLR or if the information requested by the MSC is not available at the VLR, the VLR sends a QUALREQ to the HLR associated with the MS. The HLR sends a qualreq to the VLR. The profile is included in the message. The VLR sends a qualreq to the Serving MSC. The profile is included in the message. The Serving MSC allocates a TLDN (Temporary Local Directory Number) and returns this information to the VLR in the routreq. The VLR sends the routreq to the HLR. When the routreq is received by the HLR, it returns a locreq to the Originating MSC. The Originating MSC establishes a voice path to the Serving MSC using existing interconnection protocols (e.g. SS7) and the routing information specified in the locreq.
g. h. i. j. k. l.
49
DCCH Roaming
N.S0007-0 v 1.0
July 19, 1997
5.7.3
QualificationDirective: Channel Mode (new)
Update Profile and Control
2 3 4 5 6 7 8
This scenario describes the QualificationDirective operation when authorization is confirmed and the MSs profile and latest Control Channel Mode is also supplied.
9 10 11 12 13 14
QUALDIR [MIN, ESN, Profile, CCM, TermType]
15
16 17
QDT
qualdir [ ] b
18 19 20 21 22 23
QUALDIR [MIN, ESN, Profile, CCM, TermType]
24
25 26
QDT
qualdir [ ] d
27 28 29 30 31
Figure 4
QualificationDirective: Update Profile and Control Channel Mode a. The HLR reports the change in the MSs service profile by sending a QUALDIR to the VLR where the MS is registered.
Parameters QUALCODE ControlChannelMode TerminalType Usage Type of qualification = validation and profile. Indicates the last known Control Channel Mode used by the MS to access the system. Indicates what Terminal Type the MS is expected to report upon system access. Type MBC O O
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
DCCH Roaming
50
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
b. c.
The VLR sends an empty qualdir to the HLR. The VLR reports the change in the MSs service profile by sending a QUALDIR to the Serving MSC.
Parameters QUALCODE ControlChannelMode TerminalType Usage Type of qualification = validation and profile. Indicates the last known Control Channel Mode used by the MS to access the system. Indicates what Terminal Type the MS is expected to report upon system access. Type MBC O O
d.
On receipt of the QUALDIR, the Serving MSC sends an empty qualdir to the VLR.
51
DCCH Roaming
N.S0007-0 v 1.0
July 19, 1997
5.7.4
DCCH Call Termination without Profile (new)

This scenario describes the delivery of the profile information to the Serving MSC when call termination or message delivery is attempted to a registered MS without the profile being present in the Serving MSC.
Serving System MS MSC VLR HLR
2 3 4 5 6 7 8 9 10 11 12 13 14
call arrival QUALREQ QUALREQ
a b c
15 16 17 18 19 20 21
QRT
QRT
qualreq [CCM] d e f
22 23 24 25 26 27
qualreq [CCM] call termination
28 29 30
Figure 5 a. b. c. d.
DCCH Call Termination without Profile
31 32 33 34 35 36
The Serving MSC receives a call termination request for the served MS. If the service profile of the MS is unknown to the MSC, it sends a QUALREQ to the VLR. If the service profile of the MS is unknown to the VLR, it sends a QUALREQ to the HLR associated with the MS. The HLR sends a qualreq to the Serving MSCs VLR, including the Control Channel Mode.
Parameters ControlChannelMode Usage Indicates the last known Control Channel Mode used by the MS to access the system. Type O
37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
e. f.
The VLR sends a qualreq to the Serving MSC, including the MSs service profile information, Control Channel Mode. The call termination then proceeds.
DCCH Roaming
52
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
5.7.5
InterSystemPage for a DCCH Capable MS (new)

This scenario describes the InterSystemPage operation when the invoke carries paging information.
Serving System MSC Border System MSC
ISPAGE [CCM, PFC]
ISPRT
ispage b
Figure 6 a.
InterSystemPage for a DCCH Capable MS
The Serving MSC sends an ISPAGE to the Border MSC, including an indication of the area where the MSs presence was last detected, an indication of whether to page or just listen for an unsolicited page response, an indication of the last known Control Channel Mode used by the MS to access the system, and other relevant parameters. The parameters are the same as Section 4.15 with the following additions:
Parameters ControlChannelMode PagingFrameClass Usage Indicates thethe preferred Control Channel Mode used to page the MS. Indicates the current PagingFrameClass for the Mobile Station. Type O O
b.
The Border MSC determines that the MS is present, assigns it to a voice/traffic channel, allocates it a TLDN, and returns this information to the Originating MSC in the ispage.
53
DCCH Roaming
N.S0007-0 v 1.0
July 19, 1997
5.7.6
InterSystemPage2 for a DCCH Capable MS (new)

This operation scenario describes the InterSystemPage2 operation when the invoke carries paging information.
Serving System MSC Border System MSC
2 3 4 5 6 7 8 9 10 11 12 13
ISPAGE2 [CCM, PFC]
14
15 16
ISPRT
ispage2 b
17 18 19 20 21
Figure 7 a.
InterSystemPage2 for a DCCH Capable MS
22 23 24 25 26 27 28 29 30 31 32 33 34
The Serving MSC sends an ISPAGE2 to the Border MSC, including an indication of the area where the MSs presence was last detected, an indication of whether to page or just listen for an unsolicited page response, an indication of the last known Control Channel Mode used by the MS to access the system, and other relevant parameters. The parameters are the same as Section 4.15 with the following additions:
Parameters ControlChannelMode PagingFrameClass Usage Indicates thethe preferred Control Channel Mode used to page the MS. Indicates the current PagingFrameClass for the Mobile Station. Type O O
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
b.
The Border MSC determines that the MS is present, assigns it to a voice/traffic channel, determines if authentication should be performed, and returns this information to the Serving MSC in the ispage2.
DCCH Roaming
54
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
6.1
6.1.a
Call Delivery
CD Invocation to a User Group on Another MSC (new)
This scenario describes call delivery to a User Group that has one or more active members. The active members are all roaming in one particular MSC and this MSC is different from the one in which the call originates.
Originating System MSC call origination LOCREQ [DGTSDIAL] ROUTREQ [UserGroup] c ROUTREQ [UserGroup] d HLR Serving System VLR MSC
a b
RRT
QUALREQ
RRT
QUALREQ
e f
LRT
qualreq
QRT
qualreq
QRT
g h i j
routreq[TLDN] routreq[TLDN] locreq[TERMLIST, REDIND] call setup
TLDNAT
k l
Figure 115 a. b. c.
CD Invocation to a User Group on Another MSC
A call origination and the dialed User Group address digits (i.e., directory number) are received by the Originating MSC. The Originating MSC sends a LOCREQ to the HLR associated with the directory number; this association is made through the dialed User Group address digits. If the dialed User Group address digits are assigned to a legitimate User Group, the HLR sends a ROUTREQ to the VLR where the active members are registered. The ROUTREQ includes the User Group parameter with the MIN omitted. The VLR then forwards the ROUTREQ to the MSC where the active members are registered.
d.
Voice Feature Scenarios
55
Call Delivery
N.S0007-0 v 1.0
July 19, 1997
The MSC performs special User Group paging using the user group identifier provided in the ROUTREQ. One or more MSs respond to the User Group page. e. f. With respect to the first valid page response received, the Serving MSC may then obtain the service profile of the MS from its VLR by sending it a QUALREQ. If the MS is unknown to the VLR or if the information requested by the MSC is not available at the VLR, the VLR sends a QUALREQ to the HLR associated with the MS. The HLR sends a qualreq to the VLR. The VLR sends a qualreq to the MSC. With respect to the first valid page response received, the MSC allocates a TLDN (Temporary Local Directory Number) and returns this information to the VLR in the routreq.2 (Other page responses are discarded). The VLR sends the routreq to the HLR. When the routreq is received by the HLR3, it returns a locreq to the Originating MSC. The locreq includes routing information in the form of the TerminationList parameter, along with an indication of the reason for extending the incoming call (i.e., for CD) in the RedirectionIndicator parameter. The Originating MSC establishes a voice path to the Serving MSC using existing interconnection protocols (e.g., SS7) and the routing information specified in the locreq.
1 2 3 4 5 6 7 8 9 10
g. h. i.
11 12 13 14 15 16 17 18
j. k.
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
l.
2 Throughout this document, the acronym TLDN is used in figures and descriptions to refer t o
54 55 56 57 58 59 60
the Digits(Destination), or DGTSDEST, parameter.

3 When a User Group has active members roaming in multiple MSCs, the HLR sends a ROUTREQ
to each Serving VLR/MSC. For purposes of extending the call, the HLR selects the first routreq to process and discards all others received.
Call Delivery
56
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
6.a
6.a.1
User Group Operations (new)

Initial Registration in a User Group
This scenario describes registration in a User Group.
New Serving System Old Serving System HLR VLR-1 MSC-1
MS
MSC-2
VLR-2
omt (UserGroup=1) register (UGID) REGNOT[UserGroup] REGNOT[UserGroup] REGCANC REGCANC
a b c d e f g h i j k
RNT
RNT
RCT
regcanc
RCT
regcanc
regnot[UserGroup] regnot[UserGroup] register accept (UGID)
Figure 8
Initial Registration in a User Group
57
User Group Operations
N.S0007-0 v 1.0
July 19, 1997
a. b. c. d.
The MS determines from the Overhead Message Train (OMT) that its current or new serving system supports User Group registration. The MS sends a registration message to the Serving MSC, requesting allocation in a selected User Group. After receiving the registration message from the MS, the Serving MSC sends a REGNOT to its VLR. Since the MS is unrecognized by the VLR, the VLR sends a REGNOT to the HLR associated with the MS. Note that the regnot from the VLR to the MSC is contingent upon the response received from the HLR. Since the MS was previously registered elsewhere, the HLR sends a REGCANC to the previously visited VLR (VLR-1). That VLR, upon receipt of the cancellation message, essentially removes all record of the MS from its memory. VLR-1 sends a REGCANC to the previously visited MSC (MSC-1). That MSC, upon receipt of the cancellation message, essentially removes all record of the MS from its memory. MSC-1 sends a regcanc to VLR-1. VLR-1 sends a regcanc to the HLR. The HLR sends a regnot to the VLR including the UserGroup parameter indicating that the MS has been allocated in the requested User Group. VLR sends a regnot to MSC-2. The MSC responds to the MS with a registration accept indicating the User Group status of the MS.
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
e.
f.
g. h. i. j. k.
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 Operations
58
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
6.b
6.b.1
User Zone Scenarios

User Zone Registration
This scenario describes the use of the RegistrationNotification to download NonPublicData and UserZoneData in the Profile, when an MS registers in a User Zone.
Initial Registration
a REGNOT [MSCID]
b REGNOT [MSCID]
RNT
RNT regnot [Profile {NonPublicData, UserZoneData}]

d regnot [Profile {NonPublicData, UserZoneData}] e
Registration Accept
f
Figure 9 a.
User Zone Registration
The MS roams into the coverage area of an MSC which is broadcasting PSIDs, one of which matches a MS-stored PSID. The MS registers with the MSC using this PSID. The Serving MSC sends a REGNOT to the VLR containing the MSCID parameter associated with the Serving MSC. Optionally, the MSC may return an immediate Registration Accept to the MS
b.
c. d.
The VLR forwards the REGNOT to the HLR. The HLR, based on the MSCID, determines that the MS is in an MSC with UZs and there is a subscribed Global UZ. It returns a regnot to the VLR with a Profile containing the NonPublicData and UserZoneData parameters. The VLR forwards the regnot to the Serving MSC. Upon receiving the NonPublicData and UserZoneData parameters in the Profile, the MSC maps the UZIdentifier(s) into PSID(s) and determines that the user is authorized for the selected UZ. The MSC sends a Registration Accept message to the MS. The MS then displays the ID of the PSID and the user may then make or receive calls in the User Zone.
e. f.
59
User Zone Operation
N.S0007-0 v 1.0
July 19, 1997
6.b.2
User Zone PSID Removal

This scenario describes the use of the RegistrationNotification to remove a PSID, (i.e., prevent an MS getting service in that PSID) in a User Zone.
2 3 4 5 6 7 8 9 10 11 12 13
REGNOT [MSCID]
a b REGNOT [MSCID] c
14 15 16 17 18 19 20
RNT RNT
regnot [Profile {no UZ-Data}] d regnot [Profile {no UZ-Data}] e
21 22 23 24 25 26 27
Audit Order (to force reg)

f
28 29 30
Forced Registration
g
31 32 33
Reg Reject (remove PSID)

h
34 35
Registration (to Public)

i
36 37
Registration Accept
j
38 39
Figure 10 a.
UZ PSID Removal
40 41 42 43 44 45 46 47 48 49 50 51
The MS roams into the coverage area of an MSC which is broadcasting PSIDs, one of which matches a MS-stored PSID. The MS registers with the MSC using this PSID. The Serving MSC sends a REGNOT to the VLR containing the MSCID parameter associated with the Serving MSC. Optionally, the MSC may return an immediate Registration Accept to the MS.
b.
c. d.
The VLR forwards the REGNOT to the HLR. The HLR determines that the MS is in an MSC which no longer has a subscribed UZ. It returns a regnot to the VLR with a Profile, but one which doesn't contain the NonPublicData and UserZoneData parameters. The VLR forwards the regnot to the Serving MSC. If the MSC had sent a Registration Accept in Step-b, before sending the REGNOT to the VLR, it would at this point need to send an Audit Order to the MS.
52 53 54 55 56 57
e. f.
58 59 60
User Zone Scenarios
60
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
g. h.
This would force the MS to register ... ... to which the MSC sends a Registration Reject message to the MS with the appropriate cause code set for "PSID/RSID removal". Otherwise (i.e., if the MSC not had sent a Registration Accept in Step-b), upon receiving no NonPublicData and UserZoneData parameters in the Profile, the MSC sends a Registration Reject message to the MS with the appropriate cause code set for "PSID/RSID removal". This effectively prevents the MS from getting service on that PSID.
i. j.
The MS may initiate a re-registration on the Public System. The MSC responds with a Registration Accept message to the MS.
61
User Zone Scenarios
N.S0007-0 v 1.0
July 19, 1997
6.b.3
Cancel Zone Change Tone

This scenario describes the use of the FeatureRequest to prevent an MS from receiving a Zone Change Tone, when it transitions between User Zones, Public Systems or both.
2 3 4 5 6 7 8 9 10 11 12
* FC + SEND a FEATREQ b FEATREQ c
13 14 15 16 17 18 19 20 21
FRRT
FRRT featreq [FEATRESULT]

d
22 23 24
featreq [FEATRESULT] e QUALDIR [Profile{NonPublicDta}] QUALDIR [Profile{NonPublicData] g qualdir f
25 26 27 28 29 30 31
QDT
qualdir
QDT
h i
32 33 34 35 36 37
Figure 11 Cancel Zone Change Tone a. b. c. d. A registered MS user decides to cancel User Zone Change Tone from playing during zone transitions. The user enters the appropriate *FC sequence. The Serving MSC sends a FEATREQ to the VLR containing the feature code in the DialedDigits parameter. The VLR forwards the FEATREQ to the HLR. The HLR determines that the MS user wants to cancel the zone change tone and modifies the user's UZ profile to de-activate the tone. It then returns a featreq to the VLR with the FeatureResult parameter set to "successful". The VLR forwards the featreq to the MSC. The MSC sends the MS a tone or announcement indicating that the code has been received. The HLR now sends the VLR a QUALDIR to indicate zone change deactivation has occurred. The VLR forwards the QUALDIR to the MSC. The MSC returns a qualdir to the VLR.
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56
e. f. g. h.
57 58 59 60
User Zone Scenarios
62
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.
The VLR forwards the qualdir to the HLR. Subsequent zone transitions will result in no change tone.
63
User Zone Scenarios
N.S0007-0 v 1.0
July 19, 1997
6.b.4
User Zone Not Supported by Serving MSC

This scenario describes the use of the RegistrationNotification to restrict an MS user who has "User Zone Only Service" from obtaining any service (public and non-public mode) when the Serving MSC is not UZ capable.
2 3 4 5 6 7 8 9 10 11 12 13 14
a
15 16 17 18
REGNOT [MSCID, TRANSCAP {UZCI=Not UZ Capable}] b
19 20 21 22
REGNOT [MSCID, TRANSCAP {UZCI=Not UZ Capable}] c
23 24 25 26
RNT
RNT
regnot [ORIGIND, TERMRES] d
27 28 29 30
regnot [ORIGIND, TERMRES] e
31 32 33 34
Call Origination
35
36 37 38
Call Denied Announcement
39
40 41
Figure 12
UZ Not Supported by Serving MSC
42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
User Zone Scenarios
64
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
a. b.
An MS registers on a Serving MSC. The Serving MSC sends a REGNOT to the VLR containing the MSCID parameter associated with the Serving MSC, and the TRANSCAP parameter with the UZCapabilityIndicator set to indicate that the MSC is not UZ capable. Optionally, the MSC may return an immediate Registration Accept to the MS.
c. d.
The VLR forwards the REGNOT to the HLR. The HLR determines that the MS user has "UZ Only Service" and that since the Serving MSC is UZ incapable, it returns a regnot to the VLR containing the OriginationIndicator parameter set to "Originations Denied" and the TerminationsRestrictionCode parameter set to "Terminations Denied". The HLR however does not make these changes in its version of the subscriber record in order to avoid preventing the user from ever getting service again in other (e.g., public) service areas.
e. f. g.
The VLR forwards the regnot to the Serving MSC and the MSC sends a RegistrationAccept to the MS (if not already sent in Step b). The MS attempts to originate a call. The MSC denies the call.
65
User Zone Scenarios
N.S0007-0 v 1.0
July 19, 1997
6.b.5
User Zone Only Service

This scenario describes the use of the RegistrationNotification to allow an MS user who has "User Zone Only Service" to only obtain UZ service (i.e., no service in the Public System) when the Serving MSC is UZ capable.
2 3 4 5 6 7 8 9 10 11 12 13
a
14 15 16 17 18
REGNOT [MSCID, TRANSCAP {UZCI=UZ Capable}] b
19 20 21 22
RNT
REGNOT [MSCID, TRANSCAP {UZCI=UZ Capable}] c regnot [Profile{UserZoneData, RNT NonPublicData=UZ Only}] d regnot [Profile{UZUniqueData, UZGlobalData=UZ Only}] e
23 24 25 26 27 28 29 30 31 32 33 34
Registration Accept
35
36 37 38 39
Figure 13
User Zone Only Service
40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
User Zone Scenarios
66
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
a. b.
An MS registers on a Serving MSC. The Serving MSC sends a REGNOT to the VLR containing the MSCID parameter associated with the Serving MSC, and also the TRANSCAP parameter with the UZCapabilityIndicator set to indicate that the MSC is UZ capable. Optionally, the MSC may return an immediate Registration Accept to the MS.
c. d.
The VLR forwards the REGNOT to the HLR. The HLR determines that the MS user has "UZ Only Service". It returns a regnot to the VLR containing the Profile with the UserZoneData and the NonPublicData, with the "UZ Only Service" field set to "Service not available outside this UZ". The VLR forwards the regnot to the Serving MSC. The MSC may return a Registration Accept to the MS, and only allows calls that are made or received on the designated User Zone.
e. f.
67
User Zone Scenarios
N.S0007-0 v 1.0
July 19, 1997
6.b.6
Preferred User Zone Service

This scenario describes the use of the QualificationRequest to enable the HLR to return User Zone profile elements appropriate to the UZID indicated by the subscriber's chosen PSID/RSID (referenced for convenience in the Flow Diagram as "preferred UZID").
2 3 4 5 6 7 8 9 10 11 12 13
14
15 16
REGNOT [MSCID, TRANSCAP {UZCI=UZ Capable}] b
17 18 19 20 21
RNT
REGNOT [MSCID, TRANSCAP {UZCI=UZ Capable}] c
22 23 24 25 26
RNT regnot [Profile {NonPublicData, UserZoneData}]

d
27 28
regnot [Profile {NonPublicData, UserZoneData}] e
29 30 31 32 33
Registration Accept
f
34 35 36 37
QUALREQ [UserZoneData {preferred UZID}]
38
39 40
QUALREQ [UserZoneData {preferred UZID}] h
41 42 43 44 45
QRT
QRT
qualreq[Profile {for preferred UZID}] i
46 47 48
qualreq [Profile {for preferred UZID}] j
49 50 51 52 53 54
Figure 14
Preferred User Zone Service
55 56 57 58 59 60
User Zone Scenarios
68
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
a. b.
An MS registers on a Serving MSC with a PSID/RSID. The Serving MSC sends a REGNOT to the VLR containing the MSCID parameter associated with the Serving MSC, and also the TRANSCAP parameter with the UZCapabilityIndicator set to indicate that the MSC is UZ capable. Optionally, the MSC may return an immediate Registration Accept to the MS.
c. d.
The VLR forwards the REGNOT to the HLR. The HLR determines that the MS is in an MSC with UZs and there is a subscribed Global UZ. It returns a regnot to the VLR with a Profile containing the NonPublicData and UserZoneData parameters. The VLR forwards the regnot to the Serving MSC. Upon receiving the NonPublicData and UserZoneData parameters in the Profile, the MSC maps the UZIdentifier(s) into PSID(s) and determines that the user is authorized for the selected UZ.
e.
f. g.
The MSC sends a Registration Accept message to the MS. Since the Serving MSC received UZ information for this subscriber at Step-e, the Serving MSC is aware that the HLR supports the UZ capability with Preferred UZ Service. Because the HLR supports the UZ capability, and the MS had registered in the Serving MSC on a PSID/RSID in Step a, the Serving MSC sends a QUALREQ to the VLR containing the UserZoneData populated with the UZID indicated by the subscriber's chosen PSID/RSID. The VLR forwards the QUALREQ to the HLR. The HLR returns a qualreq to the VLR with a Profile containing elements appropriate to the UZID indicated by the subscriber's chosen PSID/RSID. The VLR forwards the qualreq to the Serving MSC. This enables the MSC to provide the MS user the appropriate grade of service as specified in the profile elements returned from the HLR.
h. i. j.
69
User Zone Scenarios
N.S0007-0 v 1.0
July 19, 1997
6 IS-41.5-C SIGNALING PROTOCOL MODIFICATIONS

6.1 Existing IS-41-C Operations
2 3 4 5 6 7 8 9
6 . 4 . 2 . 1 2 FacilitiesDirective2 (IS-41.5-C Page 42) The FacilitiesDirective2 operation is used 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, NAMPS and multi-band TDMA and NAMPS MSs. The FacilitiesDirective2 operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows:
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
Facilities Directive 2
70
Operation Definitions
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
Table 33
Field Identifier Length Contents BillingID ElectronicSerialNumber InterMSCCircuitID InterSwitchCount
FacilitiesDirective2 INVOKE Parameters

Timer: HOT Type M M Reference 6.4.1.2 6.4.1.1 Notes Value SET [NATIONAL 18] variable octets
FacilitiesDirective2 INVOKE Parameters
M M M M M M O O O O O O O O O O O O O O O O O O O O O O O O O O O O
6.5.2.16 6.5.2.63 6.5.2.72 6.5.2.73 6.5.2.81 6.5.2.117 6.5.2.aa 6.5.2.29 6.5.2.30 6.5.2.34 6.5.2.36 6.5.2.38 6.5.2.41 6.5.2.43 6.5.2.45 6.5.2.47 6.5.2.50 6.5.2.70 6.5.2.71 6.5.2.84 6.5.2.85 6.5.2.86 6.5.2.120 6.5.2.143 6.5.2.aj 6.5.2.148 6.5.2.151 6.5.2.152 6.5.2.153 6.5.2.i 6.5.2.j 6.5.2.k 6.5.2.154 6.5.2.167 a aa c, d, e c c f a, c c g h i j k l c e, m n j i, n, o bb b o e, o, p o x x y z q
MobileIdentificationNumber ServingCellID BaseStationManufacturerCode CDMACallMode CDMAChannelData (Serving) CDMAMobileProtocolRevision CDMAPrivateLongCodeMask CDMAServingOneWayDelay CDMAStationClassMark CDMATargetMAHOList CDMATargetMeasurementList ChannelData (Serving) ConfidentialityModes (Desired) HandoffReason HandoffState MSLocation NAMPSCallMode NAMPSChannelData (Serving) SignalingMessageEncryptionKey StationClassMark SystemOperatorCode TargetCellID TDMABurstIndicator (Serving) TDMACallMode TDMAChannelData (Serving) TDMAServiceCode TDMATerminalCapability TDMAVoiceCoder TerminalType VoicePrivacyMask
Notes: a. For CDMA, the ServingCellID and CDMAServingOneWayDelay parameters correspond to the active set member having the shortest signal path to the MS (time reference cell).
71
N.S0007-0 v 1.0
July 19, 1997
b. c. d. e. f.
Include if an AMPS, NAMPS, or a TDMA handoff. Include if CDMA handoff. Include to indicate the acceptable call mode if other than AMPS (i.e., CDMA or NAMPS). The values in these parameters shall not contain conflicting information. This parameter shall be provided if the MS supports CDMA and is authorized to have Voice Privacy and the CDMAPrivateLongCodeMask (CDMAPLCM) parameter is available. Include for either the CDMA MAHO case or the forced handoff case. Include for the CDMA non-MAHO case. Include if an AMPS or NAMPS channel is in use. Include if MS supports Signaling Message Encryption or Voice Privacy. The parameter shall be carried forward in any subsequent handoff. If one parameter is present, they all must be present. Include if known. Include if call is in the awaiting answer or alerting state.
1 2 3 4 5 6 7 8 9 10 11 12
g. h. i. j.
13 14 15 16 17 18 19 20 21 22 23 24
k. l.
m. Include to indicate the acceptable call mode if other than AMPS (i.e., NAMPS). n. o. p. q. Include if an NAMPS channel is in use. Include if a TDMA channel is in use. Include to indicate the acceptable call mode if other than AMPS (i.e., TDMA). This parameter shall be provided if the MS supports TDMA and is authorized to have Voice Privacy and the VoicePrivacyMask (VPMASK) parameter is available. Include if the MS is IS-136 or later. Include to indicate Voice Coder preferences. Include for statistical purposes.
25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
x. y. z.
41 42
aa. Include if the MS is IS-136 or later and BSMC-specific signaling is supported. bb. Include if the MS is IS-136 or later and SOC-specific signaling is supported.
43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
72
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
The FacilitiesDirective2 operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP CONVERSATION WITH PERMISSION package. The Parameter Set is encoded as follows: Table 34 FacilitiesDirective2 Parameters RETURN RESULT
FacilitiesDirective2 RETURN RESULT Parameters Field Identifier Length Contents BSMCStatus CDMAChannelData (Target) CDMACodeChannelList CDMASearchWindow ChannelData (Target) ConfidentialityModes (Actual) NAMPSChannelData (Target) SOCStatus TargetCellID TDMABurstIndicator (Target) TDMAChannelData (Target) TDMAVoiceCoder (Target) O O O O O O O O O O O O 6.5.2.ab 6.5.2.30 6.5.2.33 6.5.2.37 6.5.2.47 6.5.2.50 6.5.2.86 6.5.2.ai 6.5.2.148 6.5.2.151 6.5.2.153 6.5.2.k f a a a b c d f e f g h Value SET [NATIONAL 18] variable octets Type M M Reference 6.4.1.2 6.4.1.1 Notes
Notes: a. b. c. d. e. f. Include if target is a CDMA channel. Include if target is an AMPS or NAMPS channel. Include to reflect actual assignment if ConfidentialityModes (Desired) parameter was present in the INVOKE. Include if target is an NAMPS channel. Include if the TargetCellID is different than that received in the INVOKE for AMPS, NAMPS, TDMA handoff. May be included if target is a TDMA channel. See parameter definition.
g. Include if target is a TDMA channel. h. Include to indicate the granted Voice Coder. If not included the MS shall continue using the current Voice Coder.
73
N.S0007-0 v 1.0
July 19, 1997
6 . 4 . 2 . 1 7 HandoffBack2 (IS-41.5-C Page 52) The HandoffBack2 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 addition of support for CDMA, NAMPS and multi-band TDMA and NAMPS MSs. The HandoffBack2 operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows:
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
74
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
Table 43
HandoffBack2 INVOKE Parameters

Timer: HOT Type M M Reference 6.4.1.2 6.4.1.1 Notes
HandoffBack2 INVOKE Parameters Field Identifier Length Contents BillingID InterMSCCircuitID MobileIdentificationNumber ServingCellID BaseStationManufacturerCode CDMACallMode CDMAChannelData (Serving) CDMAMobileProtocolRevision CDMAPrivateLongCodeMask CDMAServingOneWayDelay CDMAStationClassMark CDMATargetMAHOList CDMATargetMeasurementList ChannelData (Serving) ConfidentialityModes (Desired) HandoffReason HandoffState MSLocation NAMPSCallMode NAMPSChannelData (Serving) SignalingMessageEncryptionKey StationClassMark SystemOperatorCode TargetCellID TDMABurstIndicator (Serving) TDMACallMode TDMAChannelData (Serving) TDMAServiceCode TDMATerminalCapability TDMAVoiceCoder TerminalType VoicePrivacyMask M M M M O O O O O O O O O O O O O O O O O O O O O O O O O O O O Value SET [NATIONAL 18] variable octets
6.5.2.16 6.5.2.72 6.5.2.81 6.5.2.117 6.5.2.aa 6.5.2.29 6.5.2.30 6.5.2.34 6.5.2.36 6.5.2.38 6.5.2.41 6.5.2.43 6.5.2.45 6.5.2.47 6.5.2.50 6.5.2.70 6.5.2.71 6.5.2.84 6.5.2.85 6.5.2.86 6.5.2.120 6.5.2.143 6.5.2.aj 6.5.2.148 6.5.2.151 6.5.2.152 6.5.2.153 6.5.2.i 6.5.2.j 6.5.2.k 6.5.2.154 6.5.2.167 a u c, d, e c c f a, c c g h i j k l c e, m n j i, n, o v b o e, o, p o r r s t q
Notes:
75
HandoffBack2
N.S0007-0 v 1.0
July 19, 1997
a.
For CDMA, the ServingCellID and CDMAServingOneWayDelay parameters correspond to the active set member having the shortest signal path to the MS (time reference cell). Include if AMPS, NAMPS or TDMA handoff. Include if CDMA handoff. Include to indicate the acceptable call mode of other than AMPS (i.e., CDMA or NAMPS). The values in these parameters shall not contain conflicting information. This parameter shall be provided if the MS supports CDMA and is authorized to have Voice Privacy and the CDMAPrivateLongCodeMask (CDMAPLCM) parameter is available. Include for either the CDMA MAHO case or the forced handoff case. Include for the CDMA non-MAHO case. Include if an AMPS or NAMPS channel is in use. Include if MS supports Signaling Message Encryption or Voice Privacy. The parameter shall be carried forward in any subsequent handoff. If one parameter is present, they all must be present. Include if known. Include if the call is in the awaiting answer or alerting state.
1 2 3 4 5 6
b. c. d. e. f.
7 8 9 10 11 12 13 14 15 16 17 18 19
g. h. i. j.
20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41
k. l.
m. Include to indicate the acceptable call mode if other than AMPS (i.e., NAMPS). n. o. p. q. Include if an NAMPS channel is in use. Include if a TDMA channel is in use. Include to indicate acceptable call modes if other than AMPS (i.e., TDMA). This parameter shall be provided if the MS supports TDMA and is authorized to have Voice Privacy and the VoicePrivacyMask (VPMASK) parameter is available. Include if the MS is IS-136 or later. Include to inform Voice Coder preferences. Include for statistical purposes. Include if the MS is IS-136 or later and BSMC-specific signaling is supported. Include if the MS is IS-136 or later and SOC-specific signaling is supported.
r. s. t. u. v.
42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
HandoffBack2
76
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
The HandoffBack2 operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: Table 44 HandoffBack2 RETURN RESULT Parameters
HandoffBack2 RETURN RESULT Parameters Field Identifier Length Contents BSMCStatus CDMAChannelData (Target) CDMACodeChannelList CDMASearchWindow ChannelData (Target) ConfidentialityModes (Actual) NAMPSChannelData (Target) SOCStatus TargetCellID TDMABurstIndicator (Target) TDMAChannelData (Target) TDMAVoiceCoder (Target) O O O O O O O O O O O O 6.5.2.ab 6.5.2.30 6.5.2.33 6.5.2.37 6.5.2.47 6.5.2.50 6.5.2.86 6.5.2.ai 6.5.2.148 6.5.2.151 6.5.2.153 6.5.2.k f a a a b c d f e f g h Value SET [NATIONAL 18] variable octets Type M M Reference 6.4.1.2 6.4.1.1 Notes
g. Include if target is a TDMA channel. h. Include to indicate the granted Voice Coder. If not included the MS shall continue using the current Voice Coder.
77
HandoffBack2
N.S0007-0 v 1.0
July 19, 1997
6 . 4 . 2 . 1 9 HandoffMeasurementRequest2 (IS-41.5-C Page 56) The HandoffMeasurementRequest2 operation is sent by the Serving MSC to any adjacent MSCs to request a signal quality measurement on the specified channel. This operation differs from the HandoffMeasurementRequest operation in its addition of support for CDMA, NAMPS and multi-band TDMA and NAMPS MSs. The HandoffMeasurementRequest2 operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: Table 47 HandoffMeasurementRequest2 Parameters INVOKE INVOKE Timer: LMMRT
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
HandoffMeasurementRequest2 Field
Identifier Length Contents ServingCellID CDMACallMode CDMAChannelData (Serving) CDMAServingOneWayDelay CDMAStationClassMark ChannelData (Serving) MSLocation NAMPSCallMode NAMPSChannelData (Serving) StationClassMark TargetCellIDList TDMACallMode TDMAChannelData (Serving) TDMATerminalCapability
Value
SET [NATIONAL 18] variable octets
Type Reference Notes

M M 6.4.1.2 6.4.1.1
21 22 23 24
M O O O O O O O O O O O O O
6.5.2.117 6.5.2.29 6.5.2.30 6.5.2.38 6.5.2.41 6.5.2.47 6.5.2.84 6.5.2.85 6.5.2.86 6.5.2.143 6.5.2.ak 6.5.2.152 6.5.2.153 6.5.2.j a, b b b b c b d e c, f i g f h
25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45
Notes: a. b. c. d. e. f. Include to indicate the current call mode if other than AMPS (i.e., CDMA or NAMPS). Include if a CDMA channel measurement is requested. Include if an AMPS or NAMPS channel measurement is requested. Include to indicate the current call mode if other than AMPS (i.e., NAMPS). Include if an NAMPS channel measurement is requested. Include if a TDMA channel measurement is requested.
46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
78
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
g. h. i.
Include to indicate the current call mode, if other than AMPS (i.e., TDMA). Include if the MS is IS-136 or later. Include to indicate the list of cells and sectors on which measurements are required. The inclusion of this parameter and the sending of the HANDMREQ2 INVOKE is based on service related statistics gathered by the Serving MSC regarding past handoff performance with border cells and sectors in neighboring MSCs. See section 5.10, Successful HandoffForward for MAHO with Measurement confirmation.
The HandoffMeasurementRequest2 operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
Note: The HandoffMeasurementRequest2 RETURN RESULT is not changed.
79
N.S0007-0 v 1.0
July 19, 1997
6 . 4 . 2 . 2 1 HandoffToThird2 (IS-41.5-C Page 60) The HandoffToThird2 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, NAMPS and multi-band TDMA Mobile Stations. The HandoffToThird2 operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows:
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
80
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
Table 51
HandoffToThird2 INVOKE Parameters

Timer: HTTT Type M M Reference 6.4.1.2 6.4.1.1 Notes
HandoffToThird2 INVOKE Parameters Field Identifier Length Contents BillingID ElectronicSerialNumber InterMSCCircuitID InterSwitchCount (Serving) MobileIdentificationNumber MSCID (Target) ServingCellID BaseStationManufacturerCode CDMACallMode CDMAChannelData (Serving) CDMAMobileProtocolRevision CDMAPrivateLongCodeMask CDMAServingOneWayDelay CDMAStationClassMark CDMATargetMAHOList CDMATargetMeasurementList ChannelData (Serving) ConfidentialityModes (Desired) HandoffReason HandoffState MSLocation NAMPSCallMode NAMPSChannelData (Serving) SignalingMessageEncryptionKey StationClassMark SystemOperatorCode TargetCellID TDMABurstIndicator (Serving) TDMACallMode TDMAChannelData (Serving) TDMAServiceCode TDMATerminalCapability TDMAVoiceCoder TerminalType VoicePrivacyMask M M M M M M M O O O O O O O O O O O O O O O O O O O O O O O O O O O O Value SET [NATIONAL 18] variable octets
6.5.2.16 6.5.2.63 6.5.2.72 6.5.2.73 6.5.2.81 6.5.2.82 6.5.2.117 6.5.2.aa 6.5.2.29 6.5.2.30 6.5.2.34 6.5.2.36 6.5.2.38 6.5.2.41 6.5.2.43 6.5.2.45 6.5.2.47 6.5.2.50 6.5.2.70 6.5.2.71 6.5.2.84 6.5.2.85 6.5.2.86 6.5.2.120 6.5.2.143 6.5.2.aj 6.5.2.148 6.5.2.151 6.5.2.152 6.5.2.153 6.5.2.i 6.5.2.j 6.5.2.k 6.5.2.154 6.5.2.167 a u c, d, e c c f a, c c g h i j k t c e, l m j i, m, n v b n n, o, e n q q r s p
Notes:
81
HandoffToThird2
N.S0007-0 v 1.0
July 19, 1997
a.
For CDMA, the ServingCellID and CDMAServingOneWayDelay parameters correspond to the active set member having the shortest signal path to the MS (time reference cell). Include if AMPS, NAMPS or TDMA handoff. Include if CDMA handoff. Include to indicate the acceptable call modes if other than AMPS (i.e., CDMA or NAMPS). The values in these parameters shall not contain conflicting information. This parameter shall be provided if the MS supports CDMA and is authorized to have Voice Privacy and the CDMAPrivateLongCodeMask (CDMAPLCM) parameter is available. Include for either the CDMA MAHO case or the forced handoff case. Include for the CDMA non-MAHO case. Include if an AMPS or NAMPS channel is in use. Include if MS supports Signaling Message Encryption or Voice Privacy. The parameter shall be carried forward in any subsequent handoff. If one parameter is present, they all must be present. Include if known. Include to indicate the current call mode if other than AMPS (i.e., NAMPS).
1 2 3 4 5 6
b. c. d. e. f.
7 8 9 10 11 12 13 14 15 16 17 18 19
g. h. i. j.
20 21 22 23 24 25 26 27 28 29
k. l.
m. Include if an NAMPS channel is in use. n. o. p. Include if a TDMA channel is in use. Include to indicate the acceptable call modes. This parameter shall be provided if the MS supports TDMA and is authorized to have Voice Privacy and the VoicePrivacyMask (VPMASK) parameter is available. Include if the MS is TDMA capable. Include to inform Voice Coder preferences. Include for statistical purposes. Include if the call is in the awaiting answer or alerting state. Include if the MS is IS-136 or later and BSMC-specific signaling is supported. Include if the MS is IS-136 or later and SOC-specific signaling is supported.
30 31 32 33 34 35 36 37 38 39 40 41
q. r. s. t. u. v.
42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
HandoffToThird2
82
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
The HandoffToThird2 operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: Table 52 HandoffToThird2 Parameters RETURN RESULT
HandoffToThird2 RETURN RESULT Parameters Field Identifier Length Contents BSMCStatus CDMAChannelData (Target) CDMACodeChannelList CDMASearchWindow ChannelData (Target) ConfidentialityModes (Actual) NAMPSChannelData (Target) SOCStatus TargetCellID TDMABurstIndicator (Target) TDMAChannelData (Target) TDMAVoiceCoder (Target) O O O O O O O O O O O O 6.5.2.ab 6.5.2.30 6.5.2.33 6.5.2.37 6.5.2.47 6.5.2.50 6.5.2.86 6.5.2.ai 6.5.2.148 6.5.2.151 6.5.2.153 6.5.2.k f a a a b c d f e f g h Value SET [NATIONAL 18] variable octets Type M M Reference 6.4.1.2 6.4.1.1 Notes
g. Include if target is a TDMA channel. h. Include to indicate the granted Voice Coder. If not included, the MS shall continue using the current Voice Coder.
83
HandoffToThird2
N.S0007-0 v 1.0
July 19, 1997
6 . 4 . 2 . 2 5 InterSystemPage (IS-41.5-C Page 68) The InterSystemPage operation is used by a Serving MSC to request a Border MSC to either (a) page an MS, or (b) listen for a page response from an MS, in the Border MSC prior to Call Delivery. If the MSs presence is confirmed on the Border MSC, the MS should be registered in the Border MSC and the call is delivered directly to the Border MSC. The InterSystemPage operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows:
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
IntersystemPage
84
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
Table 59
InterSystemPage INVOKE Parameters Timer: ISPRT Type Reference Notes

M M 6.4.1.2 6.4.1.1
InterSystemPage INVOKE Parameters Field

Identifier Length Contents BillingID (Originating) ElectronicSerialNumber MobileIdentificationNumber AlertCode CallingPartyNumberString1 CallingPartyNumberString2 CallingPartySubaddress CDMASlotCycleIndex CDMAStationClassMark ControlChannelMode DMH_AccountCodeDigits DMH_AlternateBillingDigits DMH_BillingDigits ExtendedMSCID (Serving MSC) ExtendedSystemMyTypeCode (Serving MSC) LegInformation LocationAreaID MobileDirectoryNumber MSCID (Originating MSC) MSCIdentificationNumber OneTimeFeatureIndicator PageIndicator PagingFrameClass PC_SSN (Originating MSC) PilotBillingID PilotNumber RedirectingNumberString RedirectingSubaddress SenderIdentificationNumber SystemMyTypeCode (Originating MSC) TerminalType TerminationTreatment TerminationTriggers M M M O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O
Value
6.5.2.16 6.5.2.63 6.5.2.81 6.5.2.3 6.5.2.23 6.5.2.24 6.5.2.25 6.5.2.40 6.5.2.41 6.5.2.ac 6.5.2.59 6.5.2.60 6.5.2.61 6.5.2.64 6.5.2.65 6.5.2.75 6.5.2.77 6.5.2.80 6.5.2.82 6.5.2.83 6.5.2.88 6.5.2.92 6.5.2.ae 6.5.2.93 6.5.2.94 6.5.2.95 6.5.2.108 6.5.2.109 6.5.2.116 6.5.2.147 6.5.2.154 6.5.2.158 6.5.2.159 a a a a b c m a a a d e f f a g f f h n i j k a a f l f f a
85
IntersystemPage
N.S0007-0 v 1.0
July 19, 1997
Notes: a. b. c. d. e. f. g. h. i. j. k. l. Include if available (i.e., provided in the associated RoutingRequest INVOKE). Included when the Serving MSC knows that the MS is operating in CDMA Slotted Mode. Include if a CDMA channel is in use. Include to identify serving system. Include to identify serving system manufacturer. Include if known. Include to identify originating system. Include if request is to listen only. May include if request is to page. Include if available for subsequent call redirection. Include if appropriate. Include on a multileg call. Include to identify originating system manufacturer.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
m. Include if the MS is Digital Control Channel capable to indicate the last known access mode. n. Include if the MS is Digital Control Channel capable to indicate the current Paging Frame Class for the Mobile Station.
25 26 27 28 29 30
The InterSystemPage operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
31 32 33 34 35
Note: The InterSystemPage RETURN RESULT is not changed.
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
IntersystemPage
86
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
6 . 4 . 2 . 2 6 InterSystemPage2 (IS-41.5-C Page 70) The InterSystemPage2 operation is used by a Serving MSC that has received a call via a TLDN to request a Border MSC to either (a) page an MS, or (b) listen for a page response from an MS, in the Border MSC. If an MSs presence is confirmed in the Border MSC, the call is terminated to the Border MSC via intersystem trunk facilities. The InterSystemPage2 operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: Table 61 InterSystemPage2 INVOKE Parameters Timer: ISPRT Type Reference Notes
M M 6.4.1.2 6.4.1.1
InterSystemPage2 INVOKE Parameters Field

Identifier Length Contents BillingID (Originating) ElectronicSerialNumber MobileIdentificationNumber AlertCode CallingPartyNumberString1 CallingPartyNumberString2 CallingPartySubaddress ControlChannelMode CDMASlotCycleIndex CDMAStationClassMark LocationAreaID MobileDirectoryNumber PageIndicator PagingFrameClass RedirectingNumberString RedirectingSubaddress TerminalType M M M O O O O O O O O O O O O O O
Value
6.5.2.16 6.5.2.63 6.5.2.81 6.5.2.3 6.5.2.23 6.5.2.24 6.5.2.25 6.5.2.ac 6.5.2.40 6.5.2.41 6.5.2.77 6.5.2.80 6.5.2.92 6.5.2.ae 6.5.2.108 6.5.2.109 6.5.2.154 a a a a f b c d a e g a a d
Notes: a. b. c. d. e. Include if available (i.e., provided in associated RoutingRequest INVOKE). Included when the Serving MSC knows that the MS is operating in CDMA Slotted Mode. Include if a CDMA channel is in use. Include if known. Include if request is to listen only. May include if request is to page.
87
IntersystemPage2
N.S0007-0 v 1.0
July 19, 1997
f. g.
Include if the MS is Digital Control Channel capable to indicate the last known access mode. Include if the MS is Digital Control Channel capable to indicate the current Paging Frame Class for the Mobile Station.
1 2 3 4 5 6 7
The InterSystemPage2 operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
8 9 10 11
Note: The InterSystemPage2 RETURN RESULT is not changed.
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
IntersystemPage2
88
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
6 . 4 . 2 . 3 0 MSInactive (IS-41.5-C Page 76)
This operation was named CSSInactive prior to this revision of the Interim Standard.
The MSInactive operation is used to indicate that an MS is inactive. The MSInactive operation is also used by the Serving VLR to notify the HLR of the cancellation of an MSs registration. The MSInactive operation is used by the HLR to provide the MSs CallHistoryCount to the AC when the SSD is shared with the VLR, and the VLR cancels the MSs registration. The MSInactive operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: Table 68 MSInactive INVOKE Parameters Timer: MSIT Type Reference Notes
M M 6.4.1.2 6.4.1.1
MSInactive INVOKE Parameters Field

Identifier Length Contents ElectronicSerialNumber MobileIdentificationNumber CallHistoryCount DeregistrationType LocationAreaID SenderIdentificationNumber Services Result SMS_MessageWaitingIndicator M M O O O O O O
Value
6.5.2.63 6.5.2.81 6.5.2.18 6.5.2.55 6.5.2.77 6.5.2.116 6.5.2.ah 6.5.2.129 a b c d f e
Notes: a. b. c. d. e. f. Include if MS registration is canceled and if the SSD is shared. Include from VLR to HLR and HLR to AC for MS deregistration. May be included from MSC-V to VLR. Usage in the HLR is not defined. Include to identify the functional entity sending this message. Include to indicate that an SMS message is pending delivery. Include to indicate result of a PSID/RSID delivery to an MS.
The MSInactive operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
Note: MSInactive RETURN RESULT is not changed.
89
MSInactive
N.S0007-0 v 1.0
July 19, 1997
6 . 4 . 2 . 3 2 QualificationDirective (IS-41.5-C Page 80) The QualificationDirective operation is used to update the authorization information, profile information, or both, previously obtained for an MS. The QualificationDirective operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: Table 72 QualificationDirective INVOKE Parameters Timer: QDT
2 3 4 5 6 7 8 9 10 11 12 13
QualificationDirective INVOKE Parameters Field

Identifier Length Contents ElectronicSerialNumber MobileIdentificationNumber QualificationInformationCode SystemMyTypeCode (HLR or VLR) AuthorizationDenied AuthorizationPeriod ControlChannelMode DeniedAuthorizationPeriod Digits (Carrier) Digits (Destination) LocationAreaID Profile **Macro** SenderIdentificationNumber M M M M O O O O O O O O O
14 15 16 17 18 19 20
Value

M M 6.4.1.2 6.4.1.1
6.5.2.63 6.5.2.81 6.5.2.99 6.5.2.147 6.5.2.13 6.5.2.14 6.5.2.ac 6.5.2.53 6.5.2.58 6.5.2.58 6.5.2.77 6.5.2.97 6.5.2.116 a b j c d, e d, f g h i
21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43
Notes: a. b. c d. e. f. g. h. i. If included, no other optional parameters shall be present. Include if validation is being updated. May be included if the AuthorizationDenied parameter is present to indicate the interval before re-authorization may be attempted. Use only on systems not capable of supporting the TransactionCapability parameter. Include if profile is being updated and preferred carrier is applicable. Include if profile is being updated and originations are restricted to NPA-NXX or NPA-NXX-XXXX. May be included from VLR to MSC-V. Usage from the HLR is not defined. Include applicable parameter(s) (see 6.5.2.97). Include to identify the functional entity sending the message.
44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
90
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
j.
Include if the MS is Digital Control Channel capable to indicate the last known access mode.
The QualificationDirective operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
Note: The QualificationDirective RETURN RESULT is not changed.
91
N.S0007-0 v 1.0
July 19, 1997
6 . 4 . 2 . 3 3 QualificationRequest (IS-41.5-C Page 82) The QualificationRequest operation is used (a) to request validation of an MS or (b) to request validation of an MS and obtain its profile information. The QualificationRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: Table 74 QualificationRequest INVOKE Parameters Timer: QRT
2 3 4 5 6 7 8 9 10 11 12
QualificationRequest INVOKE Parameters Field

Identifier Length Contents ElectronicSerialNumber MobileIdentificationNumber QualificationInformationCode SystemMyTypeCode (MSC or VLR) MSCID (Serving MSC or Originating MSC) SenderIdentificationNumber UserGroup SystemAccessType TransactionCapability NonPublicData UserZoneData M M M M O O O O O O O
13 14
Value

M M 6.4.1.2 6.4.1.1
15 16 17 18 19 20
6.5.2.63 6.5.2.81 6.5.2.99 6.5.2.147 6.5.2.82 6.5.2.116 6.5.2.al 6.5.2.145 6.5.2.160 6.5.2.ad 6.5.2.am e a b c a a,d
21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38
Notes: a. b. c. d. e. Should be included on IS-41-C or later. Include to identify the functional entity sending the message. Include if a change in the allocation status of a User Group is requested by the MS user. Include if the system is User Zone capable. Include to indicate the UZID indicated by the subscriber's chosen PSID/RSID.
39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
92
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
The QualificationRequest operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: Table 75 QualificationRequest Parameters RETURN RESULT
QualificationRequest RETURN RESULT Parameters Field

Identifier Length Contents SystemMyTypeCode (VLR or HLR) AuthorizationDenied AuthorizationPeriod ControlChannelMode DeniedAuthorizationPeriod Digits (Carrier) Digits (Destination) MSCID (HLR) Profile **Macro** M O O O O O O O O 6.5.2.147 6.5.2.13 6.5.2.14 6.5.2.ac 6.5.2.53 6.5.2.58 6.5.2.58 6.5.2.82 6.5.2.97 a b h c d e f g
Value

M M 6.4.1.2 6.4.1.1
Notes: a. If included, no other optional parameters shall be present.
b. Include if validation requested. c. d. e. f. g. h. May be included if the AuthorizationDenied parameter is present to indicate the interval before re-authorization may be attempted. Include if profile requested and preferred carrier is applicable and TransactionCapability parameter is not received. Include if profile requested and originations are restricted to NPA-NXX or NPA-NXX-XXXX and TransactionCapability parameter is not received. Include on IS-41-C and later and authorization is not denied. Include applicable parameter(s) (see 6.5.2.97). Include if the MS is Digital Control Channel capable to indicate the last known access mode.
93
N.S0007-0 v 1.0
July 19, 1997
6 . 4 . 2 . 3 8 RegistrationNotification (IS-41.5-C Page 90) The RegistrationNotification operation is used to report the location of an MS and, optionally, to (a) validate the MS or (b) validate the MS and obtain its profile information. The RegistrationNotification operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: Table 84 RegistrationNotification INVOKE Parameters Timer: RNT
2 3 4 5 6 7 8 9 10 11 12 13 14
RegistrationNotification INVOKE Parameters Field

Identifier Length Contents ElectronicSerialNumber MobileIdentificationNumber MSCID (Serving MSC) QualificationInformationCode SystemMyTypeCode (Serving MSC or VLR) AvailabilityType BorderCellAccess ControlChannelData ControlChannelMode ExtendedMSCID (VLR) LocationAreaID PC_SSN (Serving MSC or VLR) ReceivedSignalQuality ReportType SenderIdentificationNumber SMS_Address SMS_MessageWaitingIndicator SystemAccessData SystemAccessType SystemCapabilities TerminalType TransactionCapability UserGroup M M M M M O O O O O O O O O O O O O O O O O O
15 16 17 18 19
Value

M M 6.4.1.2 6.4.1.1
20 21
6.5.2.63 6.5.2.81 6.5.2.82 6.5.2.99 6.5.2.147 6.5.2.15 6.5.2.17 6.5.2.51 6.5.2.ac 6.5.2.64 6.5.2.77 6.5.2.93 6.5.2.106 6.5.2.111 6.5.2.116 6.5.2.123 6.5.2.129 6.5.2.144 6.5.2.145 6.5.2.146 6.5.2.154 6.5.2.160 6.5.2.al a b b l c d e b f g h i b j f, k j j m
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
Notes: a. Include when MS is predictably unavailable for Call Delivery (e.g., slotted mode or sleep mode).
58 59 60
94
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
b. c. d. e. f.
Include if access occurred in a border cell (based on internal algorithms). Included by VLR if its MSCID is different than the MSCs MSCID. May be included from MSC to VLR. Include to override lower layer addressing. Include if authentication parameters were requested by the Serving MSC (AUTH=1 in the Overhead Message Train) but were not received from the MS for the system access. Include to identify message sender. Include to indicate that the Serving MSC supports Short Message Service. Include if the MS was previously registered with this VLR, the MS is registering to a new serving MSC that does not support SMS, and an SMS message is pending delivery in the previous serving system. This is only used between a VLR and an HLR. Include on IS-41-C and later. Include if the system is authentication capable (including voice channel authentication only systems where all flags are zero). Include if the MS is Digital Control Channel capable to indicate whether an analog or Digital Control Channel was used by the MS in this access.
g. h. i.
j. k. l.
m. Include if a change in the allocation status of a User Group is requested by the MS user. The RegistrationNotification operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
Note: The RegistrationNotification RETURN RESULT is not changed.
95
N.S0007-0 v 1.0
July 19, 1997
6 . 4 . 2 . 4 1 RoutingRequest (IS-41.5-C Page 95) The RoutingRequest operation is used to inquire as to the preferred method of routing a pending call to the identified MS. The RoutingRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows:
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
RoutingRequest
96
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
Table 90
RoutingRequest INVOKE Parameters Timer: RRT Type Reference Notes

M M 6.4.1.2 6.4.1.1
RoutingRequest INVOKE Parameters Field

Identifier Length Contents BillingID (Originating) ElectronicSerialNumber MobileIdentificationNumber MSCID (Originating MSC) SystemMyTypeCode (Originating MSC) AlertCode CallingPartyNumberString1 CallingPartyNumberString2 CallingPartySubaddress ControlChannelMode DestinationDigits DMH_AccountCodeDigits DMH_AlternateBillingDigits DMH_BillingDigits LegInformation LocationAreaID MobileDirectoryNumber MobileIdentificationNumber MSCIdentificationNumber NoAnswerTime OneTimeFeatureIndicator PC_SSN (Originating MSC) PilotBillingID PilotNumber RedirectingNumberString RedirectingSubaddress SenderIdentificationNumber TerminationTreatment TerminationTriggers UserGroup VoiceMailboxNumber VoiceMailboxPIN M M M M M O O O O O O O O O O O O O O O O O O O O O O O O O O O
Value
6.5.2.16 6.5.2.63 6.5.2.81 6.5.2.82 6.5.2.147 6.5.2.3 6.5.2.23 6.5.2.24 6.5.2.25 6.5.2.ac 6.5.2.56 6.5.2.59 6.5.2.60 6.5.2.61 6.5.2.75 6.5.2.77 6.5.2.80 6.5.2.81 6.5.2.83 6.5.2.87 6.5.2.88 6.5.2.93 6.5.2.94 6.5.2.95 6.5.2.108 6.5.2.109 6.5.2.116 6.5.2.158 6.5.2.159 6.5.2.al 6.5.2.165 6.5.2.166
b c c c r d, e f f f g f, h f t i k j l m m c c n o f s p q
Notes:
97
RoutingRequest
N.S0007-0 v 1.0
July 19, 1997
a. b. c. d. e. f.
Required to identify originating call. Include to specify special alerting treatment. Include if related feature is active. Optionally include if TerminationTreatment parameter value is Dialogue, to select a dialogue or to provide information to a dialogue. Optionally include if TerminationTreatment parameter value is VoiceMailRetrieval or VoiceMailStorage to select the voice mail system. Include if available and if TerminationTreatment parameter value is M S termination.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
g. Include if TerminationTreatment parameter value is MS termination and this is a multileg call (e.g., an FA call). h. i. j. k. l. May be included from VLR to MSC-V. Usage is not defined from HLR to VLR. Include to identify Originating MSC. Include if modification to normal feature processing is required for call in progress. Include to inform the serving system of the recommended no-answer timeout. Include if available (e.g., from received parameter or lower layers) for subsequent call redirection.
20 21 22 23 24 25 26 27 28 29 30 31 32
m. Include on a multileg call. n. o. p. Include to identify the functional entity sending the message. Include to differentiate termination types, defaulting to value MS termination. Include if the TerminationTreatment parameter value is VoiceMailRetrievalor VoiceMailStorage, and the mailbox is not the MobileIdentificationNumber. Optional, if the TerminationTreatment VoiceMailRetrieval or VoiceMailStorage. parameter value is
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
q. r. s. t
Include if the MS is Digital Control Channel capable to indicate which Control Channel mode shall be used to page the MS. Include for user group alerting. If this parameter is included, do not include MobileIdentificationNumber. Required unless UserGroup parameter is included.
48 49 50
The RoutingRequest operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
51 52 53 54
Note: The RoutingRequest RETURN RESULT is not changed.
55 56 57 58 59 60
RoutingRequest
98
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
6.3
6.5.1.2
Existing Parameters
Parameter Identifiers The following table lists the IS-41 MAP Parameter Identifiers. Table 118
IS-41 MAP Parameter Identifiers (continued)

H Parameter Identifier Code G F E D C B A 1 0 1 0 0 0 1 0 1 0 0 0 1 0 1 0 0 0 1 0 1 0 0 1 1 0 1 0 0 1 1 0 1 0 0 1 1 0 1 0 0 1 1 0 1 0 0 1 1 0 1 0 0 1 1 0 1 0 0 1 0 0 1 0 0 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1 0 1 1 0 1 1 0 1 1 0 0 1 0 0 1 0 0 1 0 0 1 0 0 1 0 0 1 0 0 1 0 0 1 0 0 1 0 0 1 0 0 1 0 0 1 0 0 1 0 1 1 0 1 1 0 1 1 0 1 1 0 0 1 0 0 1 0 1 1 0 1 1 0 1 1 0 1 1 0 0 1 0 0 1 0 0 1 0 0 1 0 1 1 0 1 1 0 0 1 0 0 1 0 1 1 0 1 1 0 0 1 0 0 1 0 1 1 0 1 1 1 0 1 1 1 1 1 0 1 1 1 1 1 0 1 1 1 1 1 0 1 1 1 1 1 0 1 1 1 Reference 6.5.2.i
Parameter Identifier Name TDMAServiceCode
TDMATerminalCapability
6.5.2.j
TDMAVoiceCoder
6.5.2.k
BaseStationManufacturerCode
6.5.2.aa
BSMCStatus
6.5.2.ab
ControlChannelMode
6.5.2.ac
NonPublicData
6.5.2.ad
PagingFrameClass
6.5.2.ae
PSID_RSIDInformation
6.5.2.af
PSID_RSIDList
6.5.2.ag
Parameter Identifiers
99
MAP Parameters
N.S0007-0 v 1.0
July 19, 1997
Table 118
IS-41 MAP Parameter Identifiers (continued)

Parameter Identifier Code H G F E D C B A 1 0 1 0 0 1 1 0 1 0 0 1 1 0 1 0 0 1 1 0 1 0 0 1 1 0 1 0 0 1 1 0 1 0 0 1 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 0 0 1 0 0 1 0 0 1 0 0 1 0 1 1 0 1 1 0 1 1 0 1 1 0 1 1 0 1 1 0 0 1 0 0 1 0 1 1 0 1 1 0 1 1 0 1 1 0 0 1 0 0 1 0 0 1 0 0 1 0 1 1 0 1 1 0 0 1 0 0 1 1 0 1 1 1 1 1 0 1 1 1 1 1 0 1 1 1 Reference 6.5.2.ah
1 2
Parameter Identifier Name ServicesResult
3 4 5 6 7 8
SOCStatus
6.5.2.ai
9 10 11 12
SystemOperatorCode
6.5.2.aj
13 14 15 16
TargetCellIDList
6.5.2.ak
17 18 19
UserGroup
6.5.2.al
20 21 22 23
UserZoneData
6.5.2.am
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
MAP Parameters
100
Parameter Identifiers
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
6 . 5 . 2 . 1 3 AuthorizationDenied (IS-41.5-C Page 144) The AuthorizationDenied (AUTHDEN) parameter is used to indicate that the MS is not authorized. Field
Identifier Length Contents
Value
AuthorizationDenied IMPLICIT Unsigned Enumerated 1 octet

M M 6.5.1.2 6.5.1.1
octet Notes
1
AuthorizationDenied Reason
Figure 20 Table 126
AuthorizationDenied parameter AuthorizationDenied Reason value
AuthorizationDenied Reason (octet 1)

Bits H G F E D C B A 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 0 0 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 0 1 0 1 Value 0 1 2 3 4 5 6 7 8 9 10 11 Meaning Not used. Delinquent account. Invalid serial number. Stolen unit. Duplicate unit. Unassigned directory number. Unspecified. Multiple access. Not Authorized for the MSC. Missing authentication parameters. TerminalType mismatch. Requested Service Code Not Supported.
0 0
0 0
1 1
0 0
12 through Reserved. Treat the same as value 6, Unspecified.
1 1 1 1
0 1 1 0
1 1 0 0
1 1 0 0
223 224 through Reserved for IS-4 1 protocol extension. If unknown, Treat the same as value 6, Unspecified.
1 1
1 1
1 1
1 1
255
Parameter Definitions
101
AuthorizationDenied
N.S0007-0 v 1.0
July 19, 1997
6 . 5 . 2 . 9 7 Profile (IS-41.5-C Page
230)
2 3
The Profile is a collection of the subscribers calling profile information. This information is a list of optional parameters. The Profile macro has been defined solely for editorial convenience, and does not affect the encoding in any way. PROFILE Type Reference Notes
Contents AuthenticationCapability CallingFeaturesIndicator CarrierDigits DMH_AccountCodeDigits DMH_AlternateBillingDigits DMH_BillingDigits GeographicAuthorization MessageWaitingNotificationCount MessageWaitingNotificationType MobileDirectoryNumber OriginationIndicator OriginationTriggers PACAIndicator PreferredLanguageIndicator RestrictionDigits RoutingDigits PSID_RSIDList SMS_OriginationRestrictions SMS_TerminationRestrictions SPINIPIN SPINITriggers TerminationRestrictionCode TerminationTriggers UserGroup NonPublicData UserZoneData O O O O O O O O O O O O O O O O O O O O O O O O O O 6.5.2.8 6.5.2.20 6.5.2.28 6.5.2.59 6.5.2.60 6.5.2.61 6.5.2.68 6.5.2.78 6.5.2.79 6.5.2.80 6.5.2.89 6.5.2.90 6.5.2.91 6.5.2.96 6.5.2.113 6.5.2.114 6.5.2.ag 6.5.2.136 6.5.2.138 6.5.2.139 6.5.2.140 6.5.2.157 6.5.2.159 6.5.2.al 6.5.2.ad 6.5.2.am a b c d d d e f g d h i j k l m u, w n o q r s t p v v, w
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
Figure 105 Notes: a. b. c.
Profile Macro
Include on IS-41-C or later. Include to identify feature authorization and activity. Include if preferred carrier is applicable and TransactionCapability supported.
56 57 58 59 60
Profile Macro
102
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
d. e. f. g. h. i. j. k. l.
Include if available for recording purposes (see DMH). Include if available for certain authorization restricted areas. Include if MessageWaitingNotificationType is Message Waiting Indication and number of messages waiting is authorized. Include if Message Waiting Notification feature is active and a message is waiting. Include to indicate the type of calls allowed for origination service. Include to indicate OriginationRequest triggers. Include to identify the PACA feature. Include to identify the Preferred Language feature. Include if originations are restricted to NPA-NXX or NPA-NXX-XXXX and TransactionCapability supported.
m. Include for special routing information. n. o. p. q. r. s. t. u. v. Include for MS originated Short Message Service. Include for MS terminated Short Message Service. Include to specify the User Group allocation status. Include if local SPINI operation supported. Include to indicate Subscriber PIN Intercept triggers. Include to indicate the type of call termination service. Include to indicate the RedirectionRequest or TransferToNumberRequest triggers. Include to indicate the list of acceptable PSIDs/RSIDs for the indicated MS. Include to perform User Zone updates at the serving system.
w. The PSID_RSIDList and UserZoneData parameters are mutually exclusive.
103
Profile Macro
N.S0007-0 v 1.0
July 19, 1997
6.5.2.121
SignalQuality (IS-41.5-C Page 250) The SignalQuality (SIGQUAL) parameter is used to indicate to a requesting MSC, the relative received signal strength of an MS for which a location process has been performed. Field
2 3 4 5 6 7
Value
SignalQuality IMPLICIT Unsigned Integer (0..255) 1 octet

M M 6.5.1.2 6.5.1.1
8 9 10 11 12 13 14
octet Notes
1
15 16 17 18 19 20 21
SignalQuality
Figure 129 Table 175 SignalQuality (octet 1)
SignalQuality parameter SignalQuality value
22 23
Bits H G F E D C B A 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 1 0 0 0 1 0 1 1 0 1 0 1 1
Value 0
Meaning Not a usable signal.
24 25 26 27
0 0 0 0 0 0 1 0 0 0 1 0 1 1 0 1 1 1 0 1 1 1 1 1 1 1 1 1
1 through Reserved. Treat as Not a usable signal. 8 9 through Usable signal range. 245 246 through Reserved. Treat the same as interference. 254 255 Interference.
28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44
The concept of the SignalQuality value for handoff purposes is summarized in the figure on the next page. Each cell site is assumed to be equipped with a scanning receiver capable of being tuned to any cellular channel and which contains circuitry that produces an output proportional to a characteristic of the received signal suitable for evaluating a proposed handoff operation. This output is then converted by means of appropriate A/D circuits to a digital value in a range with reasonable resolution. Values within this range shall be suitably adjusted with respect to the Candidate cells power level, the maximum power level that an MS is allowed to transmit in the candidate cell, the MS maximum power level, the current MS power level (VMAC or DMAC) in the serving cell, and the power class indicated in the station class mark. The adjusted value shall then be linearly mapped onto the signal quality scale.
45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
SignalQuality
104
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
The following example illustrates how the received signal strength of an MS can be adjusted: The current power level of the MS in the serving cell is subtracted from the maximum possible power level in the candidate cell. The result is multiplied by the difference in the Effective Radiated Power (ERP) between two consecutive levels. This value is then added to the received signal strength. The result is the adjusted value that shall be mapped to the signal quality scale. For the TDMA 800 MHz to 1800 MHz case, the adjusted signal quality is obtained by adding to the received signal strenth the difference between the serving Effective Radiated Power (ERPs) corresponding to the serving power level, MS power class, and serving Hyperband, and the target Effective Radiated Power (ERPt ) corresponding to the target power level, MS power class and targe Hyperband. ASQ = MSS + [ERPs (PL, SCM, Hyperband) - ERPt (PL, SCM, Hyperband)] ASQ: MSS: ERP: PL: SCM: Adjusted Signal Quality Measured Signal Strength Effective Radiated Power Power Level Station Class Mark
Note: The maximum possible power level of the MS in the candidate cell is the lesser of: the maximum transmit power level allowed in the candidate cell (this value may be obtained from an internal database of the serving system). the maximum power level corresponding to the power class of the MS.
105
TDMAChannelData
N.S0007-0 v 1.0
July 19, 1997
6.5.2.153
TDMAChannelData (IS-41.5-C Page 296)
2 3
This parameter was named DigitalChannelData prior to this revision of the Interim Standard.
The TDMAChannelData (TDMADATA) parameter is used to indicate the Rate, the Digital Verification Color Code (DVCC), the Digital Mobile Attenuation Code (DMAC), and the Channel Number (CHNO) of a TDMA digital channel. Rate, DVCC, Hyperband, DMAC, and Channel Number are in accordance with TDMA If an optional TDMAChannelData parameter is received in a transaction with a mandatory ChannelData parameter and the ChannelData parameter length is greater than zero, respond with a RETURN ERROR indicating ParameterError.
Field Identifier Length Contents H G Reserved DVCC HyperBand MSB Channel Number (CHNO) LSB DMAC F E D C TSR B A octet Notes 1 2 3 4 5 a b a, b, c b Value TDMAChannelData IMPLICIT OCTET STRING 5 octets Type M M Reference 6.5.1.2 6.5.1.1 Notes
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
TDMAChannelData parameter
Reserved bits shall be ignored on receipt and set to zero on sending. See TDMA for encoding of these fields. DMAC indicates the current power level of the MS associated with the digital channel being reported.
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
TDMAChannelData
106
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
Table 192
TDMAChannelData value
Time Slot and Rate indicator (TSR) (octet 1)

Bits H G F E D C B A 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 1 1 1 1 1 1 1 1 0 0 0 1 1 1 1 0 0 0 1 1 0 1 1 0 0 0 1 1 0 0 1 1 0 0 1 1 1 0 1 0 1 0 1 Value 0 1 2 3 4 5 6 9 10 11 12 13 14 15 Meaning Analog (not used if ChannelData is present). Assigned to Timeslot 1 and 4, full rate. Assigned to Timeslot 2 and 5, full rate. Assigned to Timeslot 3 and 6, full rate. Assigned to timeslots 1, 4 and 2, 5, do u b l e rate. Assigned to timeslots 1, 4 and 3, 6, double rate. Assigned to timeslots 2, 5 and 3, 6, do u b l e rate. Assigned to Timeslot Assigned to Timeslot Assigned to Timeslot Assigned to Timeslot Assigned to Timeslot Assigned to Timeslot Assigned to Timeslots 6 Triple rate. 1, 2, 3, 4, 5, 6, 1, half rate. half rate. half rate. half rate. half rate. half rate. 2, 3, 4, 5,
X X X X X
Other values are reserved. Treat a reserved value the same as value 0, Analog.
HyperBand (HBAND) (octet 3; bits E - H)

Bits H G F E D C B A 0 0 0 0 0 0 0 0 0 1 1 0 1 1 1 1 Value 0 1 2 through Reserved. Treat the same as value 0, 800 MHz. 15 Meaning 800 MHz. 1800 MHz.
107
TDMAChannelData
N.S0007-0 v 1.0
July 19, 1997
6.5.2.154
TerminalType
(IS-41.5-C Page 297)
2 3
The TerminalType (TERMTYP) parameter identifies the radio frequency interface standard supported by the associated MS. The values of this parameter are derived from the Mobile Protocol Capability Indicator (see AMPS, TDMA, NAMPS, or CDMA MPCI) over the analog control channel, the CDMA control channel Mobile Protocol Revision Level (see CDMA MOB_P_REV), or other means.
Field Identifier Length Contents H G F E D C B A octet Notes 1 Value TerminalType IMPLICIT Unsigned Enumerated 1 octet Type M M Reference 6.5.1.2 6.5.1.1 Notes
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
Terminal Type
Figure 169
TerminalType parameter
TerminalType
108
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
Table 193 Terminal Type (octet 1)
TerminalType value
Bits H G F E D C B A 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 1 1 1 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 1 1 0 1 1 0 0 0 1 1 0
Value 0 1 2 3 4 5
Meaning Not used. Not distinguished (e.g., EIA/TIA-553, IS-54-A, IS-88, IS-91, IS-94). IS-54-B. IS-136. J-STD-011. IS-136-A.
0 0 0 0 0 0 0 0 0 0
0 1 1 0 1 0 1 0 1 0
1 1 0 0 0 1 1 0 1 1
6 through Reserved. Treat a reserved value the same as value 2, IS-54-B. 31 32 33 34 IS-95. IS-95-A. J-STD-008.
0 0 0 0 0 0 1 1 1 1
1 1 0 0 0 0 0 0 0 0
1 1 0 0 1 1 0 1 0 1
35 through Reserved. Treat a reserved value the same as value 33, IS-95-A 63 64 65 66 67 68 through Reserved. Treat a reserved value the same as value 1. Not distinguished. 223 224 through Reserved for IS-41 protocol extension. If unknown, treat a reserved value the same as value 1, Not distinguished. 255 IS-88. IS-94. IS-91. J-STD-014.
0 1
0 0
0 1
0 0
1 1 1 1
0 1 1 0
1 1 0 0
1 1 0 0
1 1
1 1
1 1
1 1
109
TerminalType
N.S0007-0 v 1.0
July 19, 1997
6.5.2.160
TransactionCapability (IS-41.5-C Page 307) The TransactionCapability (TRANSCAP) parameter indicates a systems transaction capability at the current time (i.e., this capability may change over time).
Field Identifier Length Contents H G F UZCI E SPINI TL D RUI C ANN B BUSY A PROF octet 1 2 Notes a a a, b Value TransactionCapability IMPLICIT OCTET STRING variable octets Type M M Reference 6.5.1.2 6.5.1.1 Notes
2 3 4 5 6 7 8 9 10 11 12 13 14 15
Reserved Reserved
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
Multiple Terminations
Figure 175 Notes: a. b.
TransactionCapability parameter
Set reserved values to 0 when sending, ignore if received. Ignore extra octets, if received. Send only defined (or significant) octets.
TransactionCapability
110
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
Table 198
TransactionCapability parameter
Profile (PROF) (octet 1, bit A)

Bits H G F E D C B A 0 1 Value 0 1 Meaning The system is not capable of supporting the IS-41-C profile parameters. The system is capable of supporting the IS-41-C profile parameters.
Busy Detection (BUSY) (octet 1, bit B)

Bits H G F E D C B A 0 1 Value 0 1 Meaning The system is not capable of detecting a busy condition at the current time. The system is capable of detecting a busy condition at the current time.
Announcements (ANN) (octet 1, bit C)

Bits H G F E D C B A 0 Value 0 Meaning The system is not capable of honoring the AnnouncementList parameter at the current time. The system is capable of honoring the AnnouncementList parameter at the current time.
Remote User Interaction (RUI) (octet 1, bit D)

Bits H G F E D C B A 0 1 Value 0 1 Meaning The system is not capable of interacting with the user. The system is capable of interacting with the user.
Subscriber PIN Intercept (SPINI) (octet 1, bit E)

Bits H G F E D C B A 0 1 Value 0 1 Meaning The system is not capable of supporting local SPINI operation at the current time. The system is capable of supporting local SPINI operation.
111
N.S0007-0 v 1.0
July 19, 1997
Table 198
TransactionCapability parameter (concluded)
1 2 3
UZCapabilityIndicator (UZCI) (octet 1, bit F)

Bits H G F E D C B A 0 1 Value 0 1 Meaning The system is not User Zone capable at the current time. The system is User Zone capable at the current time.
4 5 6 7 8 9 10 11 12
Multiple Terminations (octet 2, bits A-D)

Bits H G F E D C B A 0 0 0 0 Value 0 Meaning The system cannot accept a termination at this time (i.e., cannot accept routing information).
13 14 15 16 17 18 19
0 0 1 1
0 1
1 1
1 through The system supports the number of call legs indicated. 15
20 21 22 23 24 25
TerminationList (TL) (octet 2, bit E)

Bits H G F E D C B A 0 1 Value 0 1 Meaning The system is not capable of supporting the TerminationList parameter at the current time. The system is capable of supporting the TerminationList parameter at the current time.
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
112
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
6.4
New Parameters
6 . 5 . 2 . a a BaseStationManufacturerCode (new) The BaseStationManufacturerCode (BSMC) parameter specifies the manufacturer of the base station that is currently serving the MS (see IS-136 for enumeration of values).
Field Identifier Length Contents H G F E D C B A octet Notes 1 Value BSMCData IMPLICIT OCTET STRING 1 octet Type M M Reference 6.5.1.2 6.5.1.1 Notes
Base Station Manufacturer Code
Figure 15 Base Station Manufacturer Code parameter
113
BSMCData
N.S0007-0 v 1.0
July 19, 1997
6 . 5 . 2 . a b BSMCStatus (new) The BSMCStatus (BSMCS) parameter indicates whether the target environment after an intersystem handoff shall support the same base station manufacturer code (BSMC) that is currently serving the MS.
Field Identifier Length Contents H G F E D C B A octet Notes 1 Value BSMCStatus IMPLICIT OCTET STRING 1 octet Type M M Reference 6.5.1.2 6.5.1.1 Notes
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
BSMC Status
17 18 19 20 21 22
Figure 16
BSMCStatus parameter
Table 2 BSMC Status (octet 1)
BSMCStatus value
23 24 25 26
Bits H G F E D C B A 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1
Value 0 1
Meaning Same BSMC Value shall not be supported. Same BSMC Value shall be supported.
27 28 29 30 31 32
0 0
0 0 0 0 1 1 1 1
1 0
2 through Reserved. Treat the same as value 0, Same BSMC Value shall not be supported. 255
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
1 1
1 1
BSMCStatus
114
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
6 . 5 . 2 . a c ControlChannelMode (new) The ControlChannelMode (CCM) parameter indicates the last known Control Channel (Analog or Digital) used by the MS to access the system. Field
Value
ControlChannelMode IMPLICIT OCTET STRING variable octets

M M 6.5.1.2 6.5.1.1
octet Notes
1
Control Channel Mode
Figure 17 Notes: a.
ControlChannelMode parameter
Ignore extra octets, if received. Send only defined (or significant) octets. Table 3 ControlChannelMode value
Control Channel Mode (octet 1)

Bits H G F E D C B A 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 1 1 Value 0 1 2 Meaning Unknown. MS is in Analog CC Mode. MS is in Digital CC Mode.
0 0 0 0 0 1 1 1
1 1 1 1
1 1 0 0
3 through Reserved. Treat the same as value 0, Unknown. 223 224 through Reserved for IS-41 protocol extension. If unknown, treat the same as value 0, Unknown. 255
1 0 0 0 1 1 1 1
1 1
1 1
115
ControlChannelMode
N.S0007-0 v 1.0
July 19, 1997
6 . 5 . 2 . a d NonPublicData (new) The NonPublicData (NPDATA) parameter is used to update a subscriber's attributes related to Non-Public Mode Service, applicable in all MSCs.
Field Identifier Length Contents H G PRDO F E CATS D C B NPOS A octet 1 Notes a a, b Value NonPublicData IMPLICIT OCTET STRING variable octets Type M M Reference 6.5.1.2 6.5.1.1 Notes
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
NonPublicData parameter
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
NonPublicData
116
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
Table 4
NonPublicData parameter
NP Only Service (NPOS) (octet 1, bits A and B)

Bits H G F E D C B A 0 0 0 1 1 0 1 1 Value 0 1 2 3 Meaning Not used. Service not available outside this UZ set or PSID/RSID list. Service also available outside this UZ set or PSID/RSID list. Reserved; treat as value 2, Service also available outside this UZ set or PSID/RSID list.
Charging Area Tone Service (CATS) (octet 1, bits C - F)

Bits H G F E D C B A 0 0 0 0 0 0 0 1 Value 0 1 Meaning Not used. Not authorized for service in this UZ set or PSID/RSID list; do not provide in-call Transition Tone. Authorized but deactivated; do not provide in-call Transition Tone. Authorized and activated; provide incall Transition tone.
0 0 0 0
1 0 1 1
2 3
0 1 0 0
1 1
1 1
4 through Reserved; treat as value 1, Not authorized for service in this UZ set or PSID/RSID list; do not provide incall Transition Tone. 15
PSID/RSID Download Order (PRDO) (octet 1, bits G and H)

Bits H G F E D C B A 0 0 1 1 0 1 0 1 Value 0 1 2 3 Meaning Not used. Do not download PSID/RSID. Download PSID/RSID. Reserved; treat as value 1, Do not download PSID/RSID.
117
NonPublicData
N.S0007-0 v 1.0
July 19, 1997
6 . 5 . 2 . a e PagingFrameClass (new) The PagingFrameClass (PFC) parameter indicates the number of hyperframes over which a MS has a single instance of Paging Channel allocation, therefore allowing the MS to sleep . Field
2 3 4 5 6 7
Value
PagingFrameClass IMPLICIT OCTET STRING variable octets

M M 6.5.1.2 6.5.1.1
8 9 10 11 12 13 14
octet Notes
1
15 16 17
Paging Frame Class
18 19 20 21 22 23 24 25
Figure 19 Notes: a.
PagingFrameClass parameter
Ignore extra octets, if received. Send only defined (or significant) octets. Table 5 PagingFrameClass value
26 27
Paging Frame Class (octet 1)

Bits H G F E D C B A 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 Value 0 1 2 3 4 5 6 7 Meaning PagingFrameClass PagingFrameClass PagingFrameClass PagingFrameClass PagingFrameClass PagingFrameClass PagingFrameClass PagingFrameClass 1 2 3 4 5 6 7 8 (1.28 seconds). (2.56 seconds) (3.84 seconds) (7.68 seconds) (15.36 seconds) (30.72 seconds) (61.44 seconds) (122.88 seconds)
28 29 30 31 32 33 34 35 36 37 38 39 40 41
0 0
0 0 1 0 0 1 1 1
0 0
1 1 1 1
1 1 0 0
8 through Reserved. Treat the same as value 0, PagingFrameClass 1. 223 224 through Reserved for IS-41 protocol extension. If unknown, treat the same as value 0, PagingFrameClass 1. 255
42 43 44 45 46 47
1 0 0 0
48 49 50 51 52 53 54 55 56 57 58 59 60
1 1
1 1
1 1
1 1
PagingFrameClass
118
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
6 . 5 . 2 . a f PSID_RSIDInformation (new) The PSID_RSIDInformation (PRINFO) parameter defines the information necessary for Non-Public Mode registration. The minimum length of this parameter is 3 octets.
Field Identifier Length Contents H G F E D C P/R Type PSID/RSID LSB MSB SID, SOC or MCC LSB MSB MCC LSB B A P/R octet Notes 1 2 3 4 5 6 7 a Value PSID_RSIDInformation IMPLICIT OCTET STRING variable octets Type M M Reference 6.5.1.2 6.5.1.1 Notes
Reserved MSB
PSID_RSIDInformation parameter
Reserved bits shall be ignored on receipt and set to zero on sending. Ignore extra octets, if received. Send only defined (or significant) octets.
119
N.S0007-0 v 1.0
July 19, 1997
Table 6
PSID_RSIDInformation value
1 2 3
PSID/RSID Indicator (octet 1, bit A)

Bits H G F E D C B A 0 1 Value 0 1 Meaning PSID. RSID.
4 5 6 7 8 9
PSID/RSID Type (octet 1, bits B-D)

Bits H G F E D C B A 0 0 0 0 0 1 0 1 1 0 1 0 0 1 0 1 0 Value 0 1 2 3 4 Meaning SID Specific. (PSID Only) SOC Specific, National SOC. (PSID or RSID) SOC Specific, International SOC. (PSID or RSID) Nationwide. (PSID Only) International. (PSID Only)
10 11 12 13 14 15 16 17 18 19 20 21
1 ... 1 1 1
5 through 7 Reserved. NOTE: If received--should be ignored (i.e., not passed on to the mobile).
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
120
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
6 . 5 . 2 . a g PSID_RSIDList (new) The PSID_RSIDList (PRLIST) parameter specifies PSID/RSID information which is used in the registration process.
Field Identifier Length Contents PSID_RSIDInformation PSID_RSIDInformation M O 6.5.2.af 6.5.2.af a Value PSID_RSIDList IMPLICIT SEQUENCE OF variable Type M M Reference 6.5.1.2 6.5.1.1 Notes
Figure 21 PSID_RSIDList parameter Notes: a. Optionally include additional PSID/RSID information parameters.
121
PSID/RSIDList
N.S0007-0 v 1.0
July 19, 1997
6 . 5 . 2 . a h ServicesResult (new) The ServicesResult (SERVRSLT) parameter is used to indicate the outcome of a service action (e.g., the download of PSID/RSIDs to a mobile station).
Field Identifier Length Contents H G F E D C B PRDR A octet 1 Notes a a, b Value ServicesResult IMPLICIT OCTET STRING variable octets Type M M Reference 6.5.1.2 6.5.1.1 Notes
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Reserved
ServicesResult parameter
20 21 22 23 24 25 26
Set reserved values to 0 when sending, ignore if received. Ignore extra octets, if received. Send only defined (or significant) octets. Table 7 ServicesResult parameter
27 28
PSID/RSID Download Result (PRDR) (octet 1, bits A and B)

Bits H G F E D C B A 0 0 1 1 0 1 0 1 Value 0 1 2 3 Meaning No Indication. Unsuccessful PSID/RSID download. Successful PSID/RSID download. Reserved. Treat the same as value 0, No Indication.
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
ServicesResult
122
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
6 . 5 . 2 . a i SOCStatus (new) The SOCStatus (SOCS) parameter indicates whether the target environment after an intersystem handoff shall support the same system operator code (SOC) that is currently serving the MS.
Field Identifier Length Contents H G F E D C B A octet Notes 1 Value SOCStatus IMPLICIT OCTET STRING 1 octet Type M M Reference 6.5.1.2 6.5.1.1 Notes
SOC Status
Figure 23
SOCStatus parameter
Table 8 SOC Status (octet 1)

Bits
SOCStatus value
H G F E D C B A 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0
Value 0
Meaning Same SOC Value shall not be supported. Same SOC Value shall be supported.
0 0 0 0 0 0 0 0
1 1
1 1
1 1
1 1
1 2 through Reserved. Treat a reserved value the same as value 0, Same SOC Value shall not be supported. 255
123
SOCStatus
N.S0007-0 v 1.0
July 19, 1997
6 . 5 . 2 . a j SystemOperatorCode (new) The SystemOperatorCode (SOC) parameter specifies the system operator that is currently providing service to a MS (see IS-136 for enumeration of values).
Field Identifier Length Contents H MSB G F E D C B A octet Notes 1 LSB 2 Value SOC IMPLICIT OCTET STRING 2 octets Type M M Reference 6.5.1.2 6.5.1.1 Notes
2 3 4 5 6 7 8 9 10 11 12 13 14 15
System Operator Code
16 17 18
Figure 24
SystemOperatorCode parameter
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
SOCData
124
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
6 . 5 . 2 . a k TargetCellIDList (new)t The TargetCellIDList (TCELLIDLIST) parameter specifies the IDs of cells to be used in the handoff measurement process.
Field Identifier Length Contents TargetCellID TargetCellID M O 6.5.2.148 6.5.2.148 a Value TargetCellIDList IMPLICIT SEQUENCE OF variable Type M M Reference 6.5.1.2 6.5.1.1 Notes
Figure 30 Notes: a.
TargetCellIDList parameter
Optionally include additional TargetCellID parameters.
125
TargetCellIDList
N.S0007-0 v 1.0
July 19, 1997
6.5.2.i
TDMAServiceCode (new) The TDMAServiceCode (TDMASC) parameter is used to indicate the acceptable or current mode of a call in accordance with TDMA. TDMASC is an extension to the TDMACallMode parameter.
Field Identifier Length Contents H G F E D C B A octet Notes 1 Value TDMAServiceCode IMPLICIT OCTET STRING variable octets Type M M Reference 6.5.1.2 6.5.1.1 Notes
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Service Code
18 19 20 21 22 23 24 25
Figure 25 Notes: a.
TDMAServiceCode parameter
Ignore extra octets, if received. Send only defined (or significant) octets. Table 9 TDMAServiceCode value
26 27
Service Code (octet 1)

Bits H G F E D C B A 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 0 1 1 0 1 1 0 0 1 1 0 1 0 1 Value 0 1 2 3 4 5 6 7 Meaning Analog Speech Only. Digital Speech Only. Analog or Digital Speech, Analog Preferred. Analog or Digital Speech, Digital Preferred. Asynchronous Data. G3 Fax. Not Used (Service Rejected). STU III (Secure Telephone Unit).
28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43
0 0
0 0
1 0 1 1
0 0
1 1
1 1
1 1
8 through Reserved. Treat a reserved value the same as value 0, Analog Speech Only. 255
44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
TDMAServiceCode
126
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
6.5.2.j
TDMATerminalCapability (TSB-76) The TDMATerminalCapability (TERMCAP) parameter indicates the capabilities of a TDMA mobile station. It identifies if the mobile station is capable of Asynchronous Data or Group 3 Fax, its supported frequency bands, its analog speech capability at 800 MHz, its Voice Coder and bandwidth capabilities. The minimum length of this parameter is 4 octets.
Field Identifier Length Contents H G F E D C B A octet Notes 1 2 3 STU3 G3FAX ADS 4 a Value TDMATerminalCapability IMPLICIT OCTET STRING variable octets Type M M Reference 6.5.1.2 6.5.1.1 Notes
Supported Frequency Band Voice Coder Protocol Version 3RATE 2RATE FRATE HRATE AVOX
TDMATerminalCapability parameter
This field indicates the MS VoiceCoder capability. Ignore extra octets, if received. Send only defined (or significant) octets.
127
N.S0007-0 v 1.0
July 19, 1997
Table 10
TDMATerminalCapability value
1 2 3
Supported Frequency Band (octet 1)

Bits H G F E D C B A 0 1 0 1 0 1 0 1 0 1 0 1 0 1 X Value Meaning 800 MHz A&B band not acceptable. 800 MHz A&B band acceptable. 1800 MHz A&B band not acceptable 1800 MHz A band acceptable. 1800 MHz B band not acceptable. 1800 MHz B band acceptable. 1800 MHz C band not acceptable. 1800 MHz C band acceptable. 1800 MHz D band not acceptable. 1800 MHz D band acceptable. 1800 MHz E band not acceptable. 1800 MHz E band acceptable. 1800 MHz F band not acceptable. 1800 MHz F band acceptable. Reserved. Ignore on reception, use any acceptable value.
4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
Voice Coder (octet 2)

Bits H G F E D C B A 0 1 0 1 X X X X X X Value Meaning VSELP Voice Coder not acceptable. VSELP Voice Coder acceptable. IS-641 Voice Coder not acceptable. IS-641 Voice Coder acceptable. Reserved. Use any other acceptable value.
28 29 30 31 32 33 34 35
Protocol Version (octet 3)

Bits H G F E D C B A 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 1 0 1 Value 0 1 2 3 4 Meaning EIA-553 or IS-54-A. TIA/EIA-627 (IS-54-B). IS-136. Permanently Reserved (ANSI J-STD-011). Treat the same as value 4, IS-136-A. IS-136-A.
36 37 38 39 40 41 42 43 44 45 46
0 0 0 0
0 0 0 0
0 1 0 1 1 1
0 0 0 1
1 1
1 1
1 1
5 through Reserved. Treat a reserved value the same as value 0, EIA-553 or IS-54-A. 255
47 48 49 50 51 52 53 54 55 56 57 58 59 60
128
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
Table 11
TDMATerminalCapability value
(concluded))
Asynchronous Data (ADS) (octet 4, bit A)

Bits H G F E D C B A 0 1 Value Meaning Asynchronous Data not supported Asynchronous Data supported
Group 3 Fax (G3FAX) (octet 4, bit B)

Bits H G F E D C B A 0 1 Value Meaning Group 3 Fax not supported. Group 3 Fax supported.
Secure Telephone Unit III (STU3) (octet 4, bit C)

Bits H G F E D C B A 0 1 Value Meaning Secure Telephone Unit III not supported. Secure Telephone Unit III supported.
Analog Voice (AVOX) (octet 4, bit D)

Bits H G F E D C B A 0 1 Value Meaning Analog Voice not supported Analog Voice supported.
Half Rate (HRATE) (octet 4, bit E)

Bits H G F E D C B A 0 1 Value Meaning Half Rate not supported. Half Rate supported.
Full Rate (FRATE) (octet 4, bit F)

Bits H G F E D C B A 0 1 Value Meaning Full Rate not supported. Full Rate supported.
Double Rate (2RATE) (octet 4, bit G)

Bits H G F E D C B A 0 1 Value Meaning Double Rate not supported. Double Rate supported.
Triple Rate (3RATE) (octet 4, bit H)

Bits H G F E D C B A 0 1 Value Meaning Triple Rate not supported. Triple Rate supported.
129
N.S0007-0 v 1.0
July 19, 1997
6.5.2.k
TDMAVoiceCoder
(TSB-76)
2 3
The TDMAVoiceCoder (TDMAVC) parameter is used to indicate the selected voice coder or a list of the preferred voice coders.
Field Identifier Length Contents H G F E D C B A octet Notes 1 a, b Value TDMAVoiceCoder IMPLICIT OCTET STRING variable octets Type M M Reference 6.5.1.2 6.5.1.1 Notes
4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Reserved Reserved
VoiceCoder 1
VoiceCoder m
a, b
19 20 21
Figure 27 Notes: a.
TDMAVoiceCoder parameter
22 23 24
Voice coders should be listed in priority order.
25 26 27 28 29 30
b. Reserved bits shall be ignored on receipt and set to zero on sending. Table 12 VoiceCoder (octet 1)
Bits H G F E D C B A 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 1 1 0 1 1 Value 0 1 2 Meaning Not used. VSELP Voice Coder acceptable. IS-641 Voice Coder acceptable.
TDMAVoiceCoder value
31 32 33 34 35 36 37 38
0 1 1 0
3 through Reserved. Ignore on reception, use any acceptable value. 5 6 Reserved for SOC/BSMC Specific signaling. If unknown, use any acceptable value.
39 40 41 42 43 44 45 46 47
0 1 1 1 1 1 1 1
1 1
0 0 0 1
7 through Reserved. Ignore on reception, use any acceptable value. 12 13 through Reserved for IS-41 protocol extension. If unknown, use any acceptable value. 15
48 49 50 51 52 53 54 55 56 57 58 59 60
1 1
TDMAVoiceCoder
130
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
6 . 5 . 2 . a l UserGroup (new) The UserGroup (UG) parameter indicates the allocation status of a MS in a User Group. It contains a status indicator and optionally the User Group identifier. The minimum length of this parameter is 1 octet.
Field Identifier Length Contents H G F E D C B A octet Notes 1 2 3 a,b c Value UserGroup IMPLICIT OCTET STRING variable octets Type M M Reference 6.5.1.2 6.5.1.1 Notes
Number of Digits 2nd BCD Digit 4th BCD Digit
Group Info 1st BCD Digit 3rd BCD Digit
nth BCD Digit
n-1st BCD Digit
UserGroup parameter
If user group identifier is not to be included, encode Number of Digits as zero. If user group identifier is included, the maximum number of digits is 15. User group identifier. Encode as BCD digits. Table 13 User Group value
Group Info (octet 1, bits A through D)

Bits H G F E D C B A 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 1 1 0 1 1 0 0 0 1 Value 0 1 2 3 4 Meaning Request for indicated user group allocation. Request for unspecified user group allocation. Request to de-allocate MS from currently allocated user group . MS allocated in the indicated user group. MS de-allocated from user group.
1 1
1 1
5 through Reserved. Treat a reserved value the same as value 1, Request for unspecified user group allocation.. 15
131
UserGroup
N.S0007-0 v 1.0
July 19, 1997
6 . 5 . 2 . a m UserZoneData (new) The UserZoneData (UZDATA) parameter is used to update a subscriber's User Zone identifier information on a per-MSCID basis, and to include the UZID indicated by the subscriber's chosen PSID/RSID. Note that the mapping of UserZoneData and PSID/RSID is by bi-lateral agreement. The minimum length of this parameter is 4 octets.
Field Identifier Length Contents H G F E D C B A octet 1 UZ Identifier 1 2 3 Reserved UZPAC 1 UZ Priority Indicator 1 4 (4*m-3) UZ Identifier m (4*m-2) (4*m-1) Reserved UZPAC m UZ Priority Indicator m (4*m) f, h i e, g b, c, h d a, g Notes Value UserZoneData IMPLICIT OCTET STRING variable octets Type M M Reference 6.5.1.2 6.5.1.1 Notes
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
Figure 29 Notes: a.
UserZoneData parameter
Include information on User Zone Identifier (UZID) number 1.
b. Include UZ Profile Action Code (UZPAC) for UZID number 1, with: 0 = not used. 1 = New Profile for this UZID. 2 = Modified Profile for this UZID. 3 = Delete Profile for this UZID. Set the value of UZPAC to 1, when this parameter contains the UZID indicated by the subscribers chosen PSID/RSID.
41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
UserZoneData
132
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
c.
Include UZ Priority Indicator (UZPI) for UZID number 1, with: 0 = Priority Level 0 (highest) 1 = Priority Level 1 2 = Priority Level 2 3 = Priority Level 3 4 = Priority Level 4 5 = Priority Level 5 6 = Priority Level 6 7 = Priority Level 7 8 = Priority Level 8 9 = Priority Level 9 10 = Priority Level 10 11 = Priority Level 11 12 = Priority Level 12 13 = Priority Level 13 14 = Priority Level 14 15 = Priority Level 15 (lowest) Set the value of UZPI to 0, when this parameter contains the UZID indicated by the subscribers chosen PSID/RSID.
d. e. f. g.
Include information on UZID, UZPAC & UZPI for UZIDs 2, 3, etc., up to (m-1). Include information on UZID number m. Include information on UZ Profile Action Code (UZPAC) and UZ Priority Indicator (UZPI) for UZID number m. User Zone Identifier values (shown in hexadecimal below): 0 = Reserved. 1-FFFFFF = valid UZ zone number.
h. i.
133
UserZoneData
N.S0007-0 v 1.0
July 19, 1997
7 SIGNALING PROCEDURES
7.1
4.28.2
2 3 4
Existing IS-41-C Procedures

HLR Receiving LocationRequest INVOKE (IS-41-C Page 192)
When an HLR receives a LocationRequest INVOKE, it shall perform the following:4 1 1-1 1-2 1-2-1 1-2-1-1 1-2-1-2 1-2-1-2-1 1-2-1-3 1-2-1-3-1 1-2-1-4 1-2-1-4-1 1-2-1-5 1-2-1-5-1 1-2-1-5-2 1-2-1-6 1-2-1-7 1-2-1-8 1-2-2 1-3 1-2 1-3 1-4 1-4-1 1-5 1-6 1-7 ENDIF. Set the called or dialed party equal to the received Digits (Dialed) parameter. Execute the HLR FA Incoming Call Invocation task (see 5.12.3). IF the PointOfReturn is indicated: GOTO LocReqPointOfReturn. ENDIF. Execute the HLR MAH Incoming Call Invocation task (see 5.14.4). IF the PointOfReturn is indicated: FA: Execute HLR FA Revertive Call Invocation task (see 5.12.4). MAH: Execute HLR MAH Revertive Call Invocation task (see 5.14.5). DEFAULT: Include the AnnouncementCode parameter within AnnouncementList set to an accessed denied announcement. Set the PointOfReturn to ToneTermination. ENDCASE. Send a RETURN RESULT to the requesting MSC. Exit this task. ENDIF. the IF the received message can be processed: (Execute feature incoming call tasks to determine the feature processing and PointOfReturn.) IF the CallingPartyNumberDigits1 parameter was received: IF the received Digits (Dialed) equal the CallingPartyNumberDigits1 (an MS dialed its own directory number): CASE revertive treatment OF: VMR: Execute HLR VMR Revertive Call Invocation task (see 5.23.3).
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
4Note that the feature interaction is per IS-53 and may be different in actual implementations.
58 59 60
4.28 Location Request
134
Intersystem Procedures
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
1-7-1 1-8 1-8A 1-8B 1-8B-1 1-8C 1-9 1-10 1-10-1 1-11 1-12 1-13 1-13-1 1-13-1-1 1-13-2 1-13-2-1 1-13-3 1-14 1-15 1-16 1-16-1 1-16-1-1 1-16-2 1-16-2-1 1-16-3 1-17 1-18 1-19 1-19-1 1-20 1-21 1-22 1-22-1 1-23 1-24 1-25 1-25-1 1-26
GOTO LocReqPointOfReturn. ENDIF. Execute the HLR User Group Incoming Call Invocation task (see 5.12.x). IF the PointOfReturn is indicated: GOTO LocReqPointOfReturn. ENDIF. (At this point it can be assumed that a mobile directory number was dialed.) Execute the HLR CFU Incoming Call Invocation task (see 5.5.5). IF the PointOfReturn is indicated: GOTO LocReqPointOfReturn. ENDIF. Execute the HLR SCA Incoming Call Invocation task (see 5.19.7). IF the PointOfReturn is indicated: IF the PointOfReturn is Accepted: GOTO Call Accepted. ELSE: GOTO LocReqPointOfReturn. ENDIF. ENDIF. Execute the HLR PCA Incoming Call Invocation task (see 5.15.7). IF the PointOfReturn is indicated: IF the PointOfReturn is Accepted: GOTO Call Accepted. ELSE: GOTO LocReqPointOfReturn. ENDIF. ENDIF. Execute the HLR CFNA Incoming Call Invocation task (see 5.4.5). IF the PointOfReturn is indicated: GOTO LocReqPointOfReturn. ENDIF. Execute the HLR CFD Incoming Call Invocation task (see 5.3.5). IF the PointOfReturn is indicated: GOTO LocReqPointOfReturn. ENDIF. Execute the HLR DND Incoming Call Invocation task (see 5.11.3). IF the PointOfReturn is indicated: GOTO LocReqPointOfReturn. ENDIF.
Call Accepted:
135
N.S0007-0 v 1.0
July 19, 1997
(HLR-based features are complete at this point.) 1-27 1-27-1 1-27-2 1-27-2-1 1-27-2-2 IF termination to the MS is authorized: Execute the HLR CD Incoming Call Invocation task (see 5.1.3). IF the PointOfReturn is not indicated: (This is the default treatment for LocationRequests.) Include the AnnouncementCode parameter within the AnnouncementList parameter set to Reorder or other appropriate announcement. Set the PointOfReturn to ToneTermination (this is the default treatment). ENDIF. ELSE (termination to the MS is not authorized): Include the AnnouncementCode parameter in the AnnouncementList parameter set to an appropriate announcement. Set the PointOfReturn to ToneTermination. ENDIF.
1 2 3 4 5 6 7 8 9 10 11 12 13 14
1-27-2-3 1-27-3 1-28 1-28-1 1-28-2 1-29
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
LocReqPointOfReturn (parameters may be included already and the PointOfReturn should be selected by the feature processing tasks): 1-30 1-31 1-31-1 1-31-2 1-32 1-32-1 1-32-2 1-32-3 1-32-3-1 1-32-4 1-33 1-33-1 1-33-2 1-33-2-1 1-33-3 1-33-4 1-33-5 1-33-5-1 1-33-6 1-34 1-34-1 CASE PointOfReturn OF: ToneTermination: Include the AccessDeniedReason parameter set to the proper value (see the following table). Include the MSCID parameter set to the identity of the Originating MSC. LocalTermination: Include the MSCID parameter set to the identity of the Serving MSC. Execute the HLR CNIP Terminating Call Invocation task (see 5.8.1). IF the a preferred interexchange carrier is applicable: Include the Digits (Carrier) parameter set to the MSs preferred interexchange carrier. ENDIF. IntersystemTermination: Include the MSCID parameter set to the identity of the Serving MSC. IF the PC_SSN of the Serving MSC is known: Include the PC_SSN parameter as received. ENDIF. Execute the HLR CNIP Redirecting Call Invocation task (see 5.8.2). IF the a preferred interexchange carrier is applicable: Include the Digits (Carrier) parameter set to the MSs preferred interexchange carrier. ENDIF. PSTNTermination: Include the MSCID parameter set to the identity of the Originating MSC.
47 48 49 50 51 52 53 54 55 56 57 58 59 60
136
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
1-34-2 1-34-2-1 1-34-3 1-34-4 1-34-5 1-34-5-1 1-34-6 1-35 1-35-1 1-35-1-1 1-35-2 1-35-3 1-35-3-1 1-35-4 1-35-5 1-35-5-1 1-35-6 1-36 1-36-1 1-36-2 1-37 1-38 2 2-1 3 4
IF selection of interexchange carrier is applicable: Include the Digits (Carrier) parameter set to the MSs preferred interexchange carrier. ENDIF. Execute the HLR CNIP Redirecting Call Invocation task (see 5.8.2). IF the a preferred interexchange carrier is applicable: Include the Digits (Carrier) parameter set to the MSs preferred interexchange carrier. ENDIF. MultipleTermination: IF at least one of the routes on the list is for a LocalTermination: Execute the HLR CNIP Terminating Call Invocation task (see 5.8.1). ENDIF. IF at least one of the routes on the list is for a IntersystemTermination or a PSTNTermination: Execute the HLR CNIP Redirecting Call Invocation task (see 5.8.2). ENDIF. IF the a preferred interexchange carrier is applicable: Include the Digits (Carrier) parameter set to the MSs preferred interexchange carrier. ENDIF. DEFAULT: Send a RETURN ERROR with Error Code SystemFailure. Exit this task. ENDCASE. Send a RETURN RESULT to the requesting MSC. Send a RETURN ERROR with a proper Error Code value (see the following table) to the requesting MSC.
ELSE (the received message cannot be processed):
ENDIF. Exit this task.
137
N.S0007-0 v 1.0
July 19, 1997
4.41.1
HLR Initiating a Routing Request (IS-41-C Page 252)

When an HLR requires a temporary routing address to a termination, such as, an MS, a mail box on a voice mail system, an interaction dialog, or other voice resource, or the HLR must solicit a response to a User Group page, it shall perform the following (termination specific parameter should already be included): 1 2 2 2-1 Relay the received BillingID parameter to identify the call on the Originating MSC. Include the called MobileIdentificationNumber parameter set to identify the called (or affected) MS. IF the HLR is soliciting a response to a User Group page: Include the UserGroup parameter to identify the group of mobiles to page.
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
2A ELSE 2A-1 Include the called MobileIdentificationNumber parameter set to identify the called (or affected) MS.
2B ENDIF. 3 4 5 6 6-1 7 8 8-1 9 Include the called ElectronicSerialNumber parameter set to identify the called (or affected) MS. Relay the received MSCID parameter to identify the Originating MSC. Relay the received SystemMyTypeCode parameter to identify the manufacturer of the Originating MSC. IF the PC_SSN parameter is received: Relay the received PC_SSN parameter to address the Originating MSC. ENDIF. IF the MSCIdentificationNumber parameter is received: Relay the received MSCIdentificationNumber parameter to Originating MSC. ENDIF. mobile directory number that is not the address the
21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38
10 IF the call is to a MobileIdentificationNumber: 10-1 11 ENDIF.
39 40 41 42 43 44 45
Include MobileDirectoryNumber parameter.
12 IF subscriber services are modified for this call: 12-1 Include OneTimeFeatureIndicator parameter set for this particular call. 13 ENDIF. 14 Include SenderIdentificationNumber parameter set to the HLRs identification number. 15 Execute the HLR CNIP Terminating Call Invocation task (see 5.8.1). 16 Send a RoutingRequest INVOKE to the VLR (or other system) with which the MS is currently registered. 17 Start the Routing Request Timer (RRT). 18 WAIT for a Routing Request response. 19 WHEN a RETURN RESULT is received:
46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
4.41 Routing Request
138
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
19-1 19-2 19-2-1 19-2-2 19-3 20-1 20-2 20-3 20-4 20-4-1 20-5 21-1 21-2
Stop timer (RRT). IF the message cannot be processed: Execute Local Recovery Procedures task (see 3.5.1). Include the AccessDeniedReason parameter set to Termination Denied. ENDIF. Stop timer (RRT). Execute Local Recovery Procedures task (see 3.5.1). Include the AccessDeniedReason parameter set to Termination Denied. IF the Error Code indicates UnrecognizedMIN OR IF the Error Code indicates OperationNotSupported: Clear the HLRs pointer to the VLR serving the MS. ENDIF. Execute Local Recovery Procedures task (see 3.5.1). Include the AccessDeniedReason parameter set to Termination Denied.
20 WHEN a RETURN ERROR or REJECT is received:
21 WHEN timer (RRT) expires:
22 ENDWAIT. 23 Return to the calling task.
139
N.S0007-0 v 1.0
July 19, 1997
4.41.3
MSC Receiving RoutingRequest INVOKE (IS-41-C Page 256)

When an MSC receives a RoutingRequest INVOKE, it shall perform the following: 1 1-1 1-1-1 1-2 1-2-1 1-2-1 1-2-1-1 1-2-2 1-2-2-1 1-2-3 1-3 1-4 1-4-1 1-4-1-1 1-4-1-2 1-4-1-3 1-4-1-3-1 1-4-1-4 1-4-1-4-1 1-4-1-4-2 1-4-1-5 1-4-2 1-4-2-1 1-4-2-2 1-4-2-3 1-4-2-3-1 1-4-2-4 1-4-2-4-1 1-4-2-4-2 1-4-2-5 1-4-3 1-4-4 1-4-4-1 ENDIF. IF the MSC does not have the MSs service profile information. Optionally execute the MSC Initiating a Qualification Request task (see 4.33.1). ENDIF. IF the termination treatment indicates an MS termination: IF the MS is inactive: Include the AccessDeniedReason parameter set to Inactive. Include the MSCID parameter set to the identity of the MSC. IF a TLDN should be returned: (Fall through to select a TLDN.) ELSE: Send a RETURN RESULT to the requesting VLR. Exit this task. ENDIF. ELSEIF the MS is not available: Include the AccessDeniedReason parameter set to Unavailable. Include the MSCID parameter set to the identity of the MSC. IF a TLDN should be returned: (Fall through to select a TLDN.) ELSE: Send a RETURN RESULT to the requesting VLR. Exit this task. ENDIF. IF the received message can be processed: IF the TerminationTreatment parameter is received: Set the termination treatment to the received TerminationTreatment parameter. ELSE: Set the termination treatment to MS termination (the default treatment). IF the UserGroup parameter is received: Set the termination treatment to UserGroupTermination. ELSE: Set the termination treatment to MSTermination (the default treatment). ENDIF.
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
140
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
1-4-5 1-4-6 1-4-6-1 1-4-6-1-1 1-4-6-1-2 1-4-6-1-2-1 1-4-6-1-2-2 1-4-6-1-2-3 1-4-6-1-3 1-4-6-1-3-1 1-4-6-1-4 1-4-6-1-4-1 1-4-6-1-4-2
ENDIF. IF the MS is not busy:5 IF pre-routing call paging is to be performed: Execute the Page an MS Procedure (see 3.3.3). IF the paging was successful on a bordering system. Relay all parameter received via the InterSystemPage RETURN RESULT or UnsolicitedResponse INVOKE. Send a RETURN RESULT to the requesting VLR. Exit this task. ELSEIF the paging was locally successful. (Fall through to select a TLDN.) ELSE (the paging was unsuccessful): Relay the indicated AccessDeniedReason parameter. IF a TLDN should be returned: (Fall through to select a TLDN.) ELSE: Send a RETURN RESULT to the requesting VLR. Exit this task. ENDIF. ENDIF. ELSE (no pre-routing paging): (Fall through to select a TLDN.) ENDIF. ELSE (the MS is busy)1: IF there is another call pending (for the Call Waiting feature) or the call is not in a two-way talking state (e.g., PACA requested, alerting, awaiting answer, awaiting page response, CC invoked, 3WC invoked, CT invoked): Include the AccessDeniedReason parameter set to Busy. Include the MSCID parameter set to the identity of the MSC. IF a TLDN should be returned: (Fall through to select a TLDN.) ELSE: Send a RETURN RESULT to the requesting VLR. Exit this task.
1-4-6-1-4-2-1 1-4-6-1-4-3 1-4-6-1-4-3-1 1-4-6-1-4-3-2 1-4-6-1-4-4 1-4-6-1-5 1-4-6-2 1-4-6-2-1 1-4-6-3 1-4-7 1-4-7-1
1-4-7-1-1 1-4-7-1-2 1-4-7-1-3 1-4-7-1-3-1 1-4-7-1-4 1-4-7-1-4-1 1-4-7-1-4-2
busy or call pending can be defined as either a) actual calls in the MSC or b) a combination of actual calls in the MSC or TLDNs assigned. Choice b) uses less of the call redirection procedures and thereby routes calls faster. Choice a) better handles abandoned calls more properly.
5MS
141
N.S0007-0 v 1.0
July 19, 1997
1-4-7-1-5 1-4-7-2 1-4-7-2-1 1-4-7-2-1-1 1-4-7-2-1-1-1 1-4-7-2-1-2 1-4-7-2-1-2-1
ENDIF. ELSE (Call Waiting is possible): IF the OneTimeFeatureIndicator is received for the incoming call: IF the .: RoutingRequest; is set to .: RoutingRequest;: Set the incoming call waiting type equal to Normal CW. ELSE: Set the incoming call waiting type to the Call Waiting for Incoming Call field of the received OneTimeFeatureIndicator. ENDIF. ELSE (the OneTimeFeatureIndicator parameter was not received): Set the incoming call waiting type equal to Normal CW. ENDIF. CASE incoming call waiting type OF: No CW: Include the AccessDeniedReason parameter set to Busy. Include the MSCID parameter set to the identity of the MSC. IF a TLDN should be returned: (Fall through to select a TLDN.) ELSE: Send a RETURN RESULT to the requesting VLR. Exit this task. ENDIF. Return to the calling task with a Busy indication. Normal CW: IF the existing call has Normal CW: IF the TerminationTreatment parameter is received (the false sense of this test is also for backward compatibility): Include the ConditionallyDeniedReason parameter set to Waitable. ENDIF. (Fall through to select a TLDN.) ELSE: Include the AccessDeniedReason parameter set to Busy. Include the MSCID parameter set to the identity of the MSC. IF a TLDN should be returned: (Fall through to select a TLDN.) ELSE: Send a RETURN RESULT to the requesting VLR. Exit this task. ENDIF.
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
1-4-7-2-1-3 1-4-7-2-2 1-4-7-2-2-1 1-4-7-2-3 1-4-7-2-4 1-4-7-2-5 1-4-7-2-5-1 1-4-7-2-5-2 1-4-7-2-5-3 1-4-7-2-5-3-1 1-4-7-2-5-4 1-4-7-2-5-4-1 1-4-7-2-5-4-2 1-4-7-2-5-5 1-4-7-2-5-6 1-4-7-2-6 1-4-7-2-6-1 1-4-7-2-6-1-1 1-4-7-2-6-1-1-1 1-4-7-2-6-1-2 1-4-7-2-6-1-3 1-4-7-2-6-2 1-4-7-2-6-2-1 1-4-7-2-6-2-2 1-4-7-2-6-2-3 1-4-7-2-6-2-3-1 1-4-7-2-6-2-4 1-4-7-2-6-2-4-1 1-4-7-2-6-2-4-2 1-4-7-2-6-2-5
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
142
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
1-4-7-2-6-3 1-4-7-2-7 1-4-7-2-7-1 1-4-7-2-7-1-1 1-4-7-2-7-1-1-1 1-4-7-2-7-1-2 1-4-7-2-7-1-3 1-4-7-2-7-2 1-4-7-2-7-2-1 1-4-7-2-7-2-2 1-4-7-2-7-2-3 1-4-7-2-7-2-3-1 1-4-7-2-7-2-4 1-4-7-2-7-2-4-1 1-4-7-2-7-2-4-2 1-4-7-2-7-2-5 1-4-7-2-7-3 1-4-7-2-8 1-4-7-3 1-4-8 1-5 1-5A 1-5A-1 1-5A-2 1-5A-2-1 1-5A-2-2 1-5A-2-3 1-5A-3 1-5A-3-1 1-5A-4 1-5A-4-1 1-5A-4-2 1-5A-4-3 1-5A-5 1-5B ENDIF. ENDIF. ENDIF. ENDIF.
ENDIF. Priority CW: IF the existing call has Call Waiting field is Normal CW or Priority CW: IF the TerminationTreatment parameter is received (the false sense of this test is also for backward compatibility): Include the ConditionallyDeniedReason parameter set to Waitable. ENDIF. (Fall through to select a TLDN.) ELSE: Include the AccessDeniedReason parameter set to Busy. Include the MSCID parameter set to the identity of the MSC. IF a TLDN should be returned: (Fall through to select a TLDN.) ELSE: Send a RETURN RESULT to the requesting VLR. Exit this task. ENDIF. ENDIF. ENDCASE.
IF the termination treatment indicates a UserGroupTermination: Execute the Page an MS task (see 3.3.3) using the User Group identifier. IF the paging was successful on a bordering system: Relay all parameters received via the InterSystemPage RETURN RESULT or UnsolicitedResponse INVOKE. Send a RETURN RESULT to the requesting VLR. Exit this task. ELSEIF the paging was locally successful: (Fall through to select a TLDN.) ELSE (the paging was unsuccessful): Relay the indicated AccessDeniedReason parameter. Send a RETURN RESULT to the requesting VLR. Exit this task. ENDIF. (TLDN is selected here.)
143
N.S0007-0 v 1.0
July 19, 1997
1-6 1-6-1 1-6-2 1-6-2-1 1-6-2-2 1-6-2-3
IF TLDN is available: CASE termination treatment OF: MSTermination, UserGroupTermination: Store the MobileIdentificationNumber parameter of the MS to page. Store the ElectronicSerialNumber parameter of the MS to page. IF the TerminationTriggers parameter is received: Store the TerminationTriggers parameter. ENDIF. IF the LegInformation parameter is received: Store the LegInformation parameter. ENDIF. IF the GroupInformation parameter is received: Store the GroupInformation parameter. ENDIF. IF the MobileDirectoryNumber parameter is received: Store the MobileDirectoryNumber parameter. ENDIF. IF the AlertCode parameter is received: Store the AlertCode parameter. ENDIF. Execute the MSC Record the DMH Parameters task. Assign a TLDN to the indicated MS. VoiceMailDelivery: IF the Digits (Destination) parameter is received: Store the received Digits (Destination) parameter as the voice mail system identifier. ELSE: Store a default voice mail system identifier. ENDIF. IF the VoiceMailboxNumber parameter is received: Store the VoiceMailboxNumber as the voice mail box number. ELSE: Store the MSs MobileIdentificationNumber as the voice mail box number. ENDIF. IF the VoiceMailboxPIN parameter is received: Store the VoiceMailboxPIN as the voice mail PIN. ENDIF. Assign a TLDN for the indicated voice mail delivery. VoiceMailRetrieval: IF the Digits (Destination) parameter is received:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
1-6-2-3-1 1-6-2-4 1-6-2-5 1-6-2-5-1 1-6-2-6 1-6-2-7 1-6-2-7-1 1-6-2-8 1-6-2-9 1-6-2-9-1 1-6-2-10 1-6-2-11 1-6-2-11-1 1-6-2-12 1-6-2-13 1-6-2-14 1-6-3 1-6-3-1 1-6-3-1-1 1-6-3-2 1-6-3-2-1 1-6-3-3 1-6-3-4 1-6-3-4-1 1-6-3-5 1-6-3-5-1 1-6-3-6 1-6-3-7 1-6-3-7-1 1-6-3-8 1-6-3-9 1-6-4 1-6-4-1
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
144
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
1-6-4-1-1 1-6-4-2 1-6-4-2-1 1-6-4-3 1-6-4-4 1-6-4-4-1 1-6-4-5 1-6-4-5-1 1-6-4-6 1-6-4-7 1-6-4-7-1 1-6-4-8 1-6-4-9 1-6-5 1-6-5-1 1-6-5-1-1 1-6-5-1-2 1-6-5-1-3 1-6-5-2 1-6-5-2-1 1-6-5-3 1-6-6 1-6-6-1 1-6-7 1-6-8 1-6-9 1-6-10 1-6-11 1-6-11-1 1-6-12 1-6-13 1-6-14 1-6-14-1 1-6-15 1-6-16
Store the received Digits (Destination) parameter as the voice mail system identifier. ELSE: Store a default voice mail system identifier. ENDIF. IF the VoiceMailboxNumber parameter is received: Store the VoiceMailboxNumber as the voice mail box number. ELSE: Store the MSs MobileIdentificationNumber as the voice mail box number. ENDIF. IF the VoiceMailboxPIN parameter is received: Store the VoiceMailboxPIN as the voice mail PIN. ENDIF. Assign a TLDN for the indicated voice mail retrieval. DialogTermination: IF a DestinationDigits parameter was received: Store the received DestinationDigits parameter as the dialog identification. Store the MobileIdentificationNumber and ElectronicSerialNumber for subsequent interactions. Assign a TLDN for the indicated dialog. ELSE: Send a RETURN ERROR with an Error Code MissingParameter. ENDIF. DEFAULT: Send a RETURN ERROR UnrecognizedParameterValue. ENDCASE. Include the Digits (Destination) parameter set equal to the TLDN. Assign a billing identifier to the TLDN. Include the BillingID parameter set equal to the TLDN billing identifier. IF a OneTimeFeatureIndicator parameter is received with received messages: Store the parameter overriding the MS profile information. ENDIF. Store the received MSCID parameter as the Originating MSC identifier and information related to the indicated termination with the assigned TLDN. IF the CallingPartyNumberString1 parameter is received: Store the CallingPartyNumberString1 parameter to identify the calling party. ENDIF. IF the CallingPartyNumberString2 parameter is received: with an Error Code
145
N.S0007-0 v 1.0
July 19, 1997
1-6-16-1 1-6-17 1-6-18 1-6-18-1 1-6-19 1-6-20 1-6-20-1 1-6-21 1-6-22 1-6-22-1 1-6-23 1-6-24 1-6-24-1 1-6-25 1-6-26 1-6-27 1-6-28 1-6-29 1-6-30 1-7 1-7-1 1-7-2 1-7-3 1-8 2 2-1 3 4
Store the CallingPartyNumberString2 parameter to identify the calling party. ENDIF. IF the CallingPartySubaddress parameter is received: Store the CallingPartySubaddress parameter to identify the calling party. ENDIF. IF the RedirectingNumberString parameter is received: Store the RedirectingNumberString parameter to identify the calling party. ENDIF. IF the RedirectingSubaddress parameter is received: Store the RedirectingSubaddress parameter to identify the calling party. ENDIF. IF the MSCIdentificationNumber parameter is received: Store the MSCIdentificationNumber parameter to identify the calling party. ENDIF. Include the MSCID parameter set to the identity of the MSC. Include the MSCIdentificationNumber parameter set to the MSCs ID information. Include the PC_SSN parameter with the Type set to Serving MSC and the PC and SSN fields set to the MSCs point code and subsystem number. Send a RETURN RESULT to the requesting VLR. Execute the Wait for TLDN Call task (see 3.3.2). ELSE (no TLDN is available): Discard any included parameters. Send a RETURN ERROR with Error Code ResourceShortage to the requesting VLR. Exit this task. ENDIF.
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
ELSE (the received message cannot be processed): Send a RETURN ERROR with a proper Error Code value (see the following table) to the requesting VLR. ENDIF. Exit this task.
146
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
7.2
New IS-41-C Procedures
5.12
5.12.A
Flexible Alerting (FA)

HLR User Group Incoming Call Invocation (new)
When the HLR determines that the received dialed digits identify a User Group, it shall perform the following tasks: 1 1-1 1-2 1-3 1-3-1 1-4 1-5 2 3 3-1 3-1-1 3-1-2 3-1-3 3-2 4 4-1 4-2 5 ELSE: Include the AccessDeniedReason parameter set to NoPageResponse. Set the PointOfReturn to ToneTermination. ENDIF. FOR all Serving MSCs in which members of the User Group are known to be active: Include the UserGroup parameter set to the identifier of the User Group. Include the AlertCode parameter set appropriately. IF triggers should be set for the terminating party at the terminating switch for this call: Include the TerminationTriggers parameter. ENDIF. Execute the HLR Initiating a RoutingRequest task (see 4.41.1). ENDFOR. IF at least one RoutingRequest RETURN RESULT containing Digits(Destination) is received: WITH respect to the first RoutingRequest RETURN RESULT containing Digits(Destination) received: Include the Digits(Destination) parameter within an IntersystemTermination parameter. Include other relevant parameters within the IntersystemTermination parameter. Set the PointOfReturn to IntersystemTermination. ENDWITH.
Voice Feature Procedures
147
5.12 Flexible Alerting (FA)

3GPP2

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3GPP2

Uploaded by

Copyright:

Available Formats

3GPP2 N.S0007-0 Version 1.

DCCH (Clarification of Audit Order with Forced ReRegistration in Pre-TIA/EIA-136-A Implementation)

July 19, 1997

REFERENCES ............................................................................................................ 4 2.1 Normative References......................................................................................... 4

July 19, 1997

6.1 6.a 6.b

July 19, 1997

6.4.2.32 6.4.2.33 6.4.2.38 6.4.2.41 6.3

July 19, 1997

July 19, 1997

Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13

July 19, 1997

July 19, 1997

July 19, 1997

TIA/EIA-664, Cellular Features Description

This IS adds functionality to the following IS-41-C Interim Standard:

Cellular Radiotelecommunications Intersystem Operations: Signaling

July 19, 1997

GENERAL BACKGROUND AND ASSUMPTIONS

July 19, 1997

Symbols and Abbreviations

July 19, 1997

July 19, 1997

July 19, 1997

3 STAGE 1 SERVICE DESCRIPTIONS

Normal Procedures With Successful Outcome

NP may be withdrawn at the subscribers request or for administrative reasons.

NP is registered upon authorization.

Non-Public Mode Service (NP)

July 19, 1997

NP is de-registered upon de-authorization.

NP may be activated upon authorization.

NP shall be de-activated upon de-authorization.

h. PSID/RSID/SID/NID and duration in each.

Exception Procedures or Unsuccessful Outcome

Non-Public Mode Service (NP)

July 19, 1997

Interactions With Other Wireless Services

Non-Public Mode Service (NP)

July 19, 1997

User Group (UG)

UG is applicable to voice telecommunication services.

Normal Procedures With Successful Outcome

User Group (UG)

July 19, 1997

UG Subscription Options Values

UG may be withdrawn at the subscribers request or for administrative reasons.

UG shall be registered upon authorization.

User Group (UG)

July 19, 1997

Exception Procedures or Unsuccessful Outcome

User Group (UG)

July 19, 1997

Interactions With Other Wireless Services

None identified. User Group applies to voice telecommunications service only.

User Group (UG)

July 19, 1997

Conference Calling (CC)

None identified. User Group ID applies to voice telecommunications service only.

User Group (UG)

July 19, 1997

Selective Call Acceptance (SCA)

User Group (UG)