3GPP2 X.S0004-540-E v 2.0

Date: July 2007

Mobile Application Part (MAP) -

OPERATIONS SIGNALING PROTOCOLS

COPYRIGHT

3GPP2 and its Organizational Partners claim copyright in this document and individual OPs may copyright and issue documents or standards publications in individual Organizationial Partner’s name based on this document. Requests for reproduction of this document should be directed to the 3GPP2 Secretariat at [email protected]. Requests to reproduce individual Organizationial Part- ner’s documents should be directed to that Organizational Partner. See www.3gpp2.org for more information. REVISION HISTORY

Revision Date Remarks X.S0004-540-E v2.0 July 2007 Incorporated changes from Miscel- laneous Rev. E standards. X.S0004-540-E v2.0

1 2 PART 540 3 4 5 6 1 MAP OPERATIONS 7 8 9 10 1.1 General 11 12 This specification supports systems conforming to air-interface technologies AMPS, NAMPS, 13 ® 1 14 TDMA and CDMA, including cdma2000 . 15 16 17 1.2 Operation Formats 18 19 This Standard employs the TCAP operation formats defined in ANSI T1.114 with the exceptions and 20 21 limitations specified in 1.3.1. 22 23 24 1.2.1 Parameters cross references 25 26 The references pertaining to the parameters included in each of the operations refer to MAP-550-E. 27 For example the ActionCode parameter includes a cross reference 2.2. This should be read as MAP- 28 550-2.2. 29 30 31 32 1.3 Operation Specifiers 33 34 Table 1 MAP Operation Specifiers 35 36 Operation Name Operation Specifier 37 38 H G F E D C B A Decimal 39 40 not used 00000000 0 41 HandoffMeasurementRequest 0 0 000001 1 42 43 FacilitiesDirective 0 0 000010 2 44 MobileOnChannel 0 0 000011 3 45 46 HandoffBack 00000100 4 47 FacilitiesRelease 0 0 000101 5 48 49 QualificationRequest 00000110 6 50 QualificationDirective 00000111 7 51 52 Blocking 00001000 8 53 54 Unblocking 00001001 9 55 56 1 cdma2000® is the trademark for the technical nomenclature for certain specifications and standards of the Organizational 57 ® 58 Partners (OPs) of 3GPP2. Geographically (and as of the date of publication), cdma2000 is a registered trademark of the 59 Telecommunications Industry Association (TIA-USA) in the United States. 60 540 - 1 MAP OPERATIONS X.S0004-540-E v2.0

1 Operation Name Operation Specifier 2 H G F E D C B A Decimal 3 4 ResetCircuit 00001010 10 5 6 TrunkTest 00001011 11 7 TrunkTestDisconnect 00001100 12 8 9 RegistrationNotification 00001101 13 10 RegistrationCancellation 00001110 14 11 12 LocationRequest 00001111 15 13 RoutingRequest 00010000 16 14 15 FeatureRequest 00010001 17 16 Reserved 00010010 18 17 18 Reserved 00010011 19 19 UnreliableRoamerDataDirective00010100 20 20 21 Reserved 00010101 21 22 23 MSInactive 00010110 22 24 TransferToNumberRequest 00010111 23 25 26 RedirectionRequest 00011000 24 27 HandoffToThird 00011001 25 28 29 FlashRequest 00011010 26 30 AuthenticationDirective 00011011 27 31 32 AuthenticationRequest 00011100 28 33 BaseStationChallenge 00011101 29 34 35 AuthenticationFailureReport 00011110 30 36 CountRequest 00011111 31 37 38 InterSystemPage 00100000 32 39 40 UnsolicitedResponse 00100001 33 41 BulkDeregistration 00100010 34 42 43 HandoffMeasurementRequest2 00100011 35 44 FacilitiesDirective2 00100100 36 45 46 HandoffBack2 00100101 37 47 HandoffToThird2 00100110 38 48 49 AuthenticationDirectiveForward 00100111 39 50 AuthenticationStatusReport 00101000 40 51 52 Reserved 00101001 41 53 InformationDirective 00101010 42 54 55 InformationForward 00101011 43 56 57 InterSystemAnswer 00101100 44 58 59 60 Operation Specifiers 540 - 2 X.S0004-540-E v2.0

1 Operation Name Operation Specifier 2 3 H G F E D C B A Decimal 4 5 InterSystemPage2 00101101 45 6 InterSystemSetup 00101110 46 7 8 OriginationRequest 0 0 101111 47 9 RandomVariableRequest 0 0 110000 48 10 11 RedirectionDirective 00110001 49 12 13 RemoteUserInteractionDirective00110010 50 14 SMSDeliveryBackward 00110011 51 15 16 SMSDeliveryForward 00110100 52 17 SMSDeliveryPointToPoint 00110101 53 18 19 SMSNotification 00110110 54 20 SMSRequest 0 0 110111 55 21 22 OTASPRequest 0 0 111000 56 23 Reserved 00111001 57 24 25 ChangeFacilities 0 0 111010 58 26 ChangeService 0 0 111011 59 27 28 ParameterRequest 0 0 111100 60 29 30 TMSIDirective 00111101 61 31 NumberPortabilityRequest 0 0 111110 62 32 33 ServiceRequest 00111111 63 34 AnalyzedInformation 01000000 64 35 36 ConnectionFailureReport 01000001 65 37 ConnectResource 01000010 66 38 39 DisconnectResource 01000011 67 40 FacilitySelectedAndAvailable 0 1 000100 68 41 42 InstructionRequest 01000101 69 43 Modify 01000110 70 44 45 ResetTimer 01000111 71 46 47 Search 01001000 72 48 SeizeResource 01001001 73 49 50 SRFDirective 01001010 74 51 TBusy 01001011 75 52 53 TNoAnswer 01001100 76 54 Release 01001101 77 55 56 SMSDeliveryPointToPointAck 01001110 78 57 MessageDirective 01001111 79 58 59 60 540 - 3 Operation Specifiers X.S0004-540-E v2.0

1 Operation Name Operation Specifier 2 H G F E D C B A Decimal 3 4 Values 80-100 Reserved xxxxxxxx 80-100 5 6 InterSystemSMSPage 01100101 101 7 Values 102-110 Reserved 102-110 8 9 InterSystemSMSDelivery- 01101111 111 10 PointToPoint 11 QualificationRequest2 01110000 112 12 13 Other Values Reserved xxxxxxxx … 14 11100000 224 15 16 Reserved for Protocol Extension through … 17 11111111 255 18 19 20 21 1.3.1 Mapping of Operations onto TCAP Package Types 22 23 The following table lists the mapping of MAP Operations onto ANSI TCAP package types. 24 25 Table 2 Mapping of MAP Operations onto TCAP Package Types 26 27 Operation Name Component Type Package Type 28 29 ChangeFacilities INVOKE (LAST) CONVERSATION WITHOUT PERMISSION 30 RETURN RESULT (LAST) CONVERSATION WITH PERMISSION 31 RETURN ERROR CONVERSATION WITH PERMISSION 32 REJECT CONVERSATION WITH PERMISSION 33 34 ConnectionFailure INVOKE (LAST) CONVERSATION WITH PERMISSION 35 Report RETURN ERROR CONVERSATION WITH PERMISSION 36 REJECT CONVERSATION WITH PERMISSION 37 38 ConnectResource INVOKE (LAST) CONVERSATION WITHOUT PERMISSION 39 RETURN ERROR CONVERSATION WITH PERMISSION 40 41 REJECT CONVERSATION WITH PERMISSION 42 DisconnectResource INVOKE (LAST) CONVERSATION WITHOUT PERMISSION 43 RETURN ERROR CONVERSATION WITH PERMISSION 44 45 REJECT CONVERSATION WITH PERMISSION 46 FacilitiesDirective INVOKE (LAST) QUERY WITH PERMISSION 47 RETURN RESULT (LAST) CONVERSATION WITH PERMISSION 48 49 RETURN ERROR RESPONSE 50 REJECT RESPONSE 51 52 FacilitiesDirective2 INVOKE (LAST) QUERY WITH PERMISSION 53 RETURN RESULT (LAST) CONVERSATION WITH PERMISSION 54 RETURN ERROR RESPONSE 55 REJECT RESPONSE 56 57 58 59 60 Operation Specifiers 540 - 4 X.S0004-540-E v2.0

1 Operation Name Component Type Package Type 2 3 InstructionRequest INVOKE (LAST) CONVERSATION WITH PERMISSION 4 RETURN RESULT (LAST) RESPONSE 5 6 RETURN ERROR RESPONSE 7 REJECT RESPONSE 8 MobileOnChannel INVOKE (LAST) RESPONSE 9 10 RemoteUser INVOKE (LAST) CONVERSATION WITHOUT PERMISSION 11 InteractionDirective RETURN RESULT (LAST) CONVERSATION WITH PERMISSION 12 13 RETURN ERROR CONVERSATION WITH PERMISSION 14 REJECT CONVERSATION WITH PERMISSION 15 ResetTimer INVOKE (LAST) CONVERSATION WITHOUT PERMISSION 16 17 RETURN ERROR CONVERSATION WITH PERMISSION 18 REJECT CONVERSATION WITH PERMISSION 19 SeizeResource INVOKE (LAST) QUERY WITH PERMISSION 20 21 RETURN RESULT (LAST) CONVERSATION WITHOUT PERMISSION 22 RETURN ERROR RESPONSE 23 REJECT RESPONSE 24 25 SMSDeliveryPoint- INVOKE (LAST) UNIDIRECTIONAL 26 ToPointAck 27 SRFDirective INVOKE (LAST) CONVERSATION WITHOUT PERMISSION 28 29 RETURN RESULT (LAST) CONVERSATION WITH PERMISSION 30 RETURN ERROR RESPONSE 31 REJECT RESPONSE 32 33 All other operations INVOKE (LAST) QUERY WITH PERMISSION 34 RETURN RESULT (LAST) RESPONSE 35 RETURN ERROR RESPONSE 36 37 REJECT RESPONSE 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 540 - 5 Operation Specifiers X.S0004-540-E v2.0

1 2 OPERATION DEFINITIONS 2 3 The following table summarizes the operations defined for the MAP: 4 5 6 Table 3 Summary of MAP Operations 7 Operation Reference 8 9 AnalyzedInformation 2.1 10 11 AuthenticationDirective 2.2 12 AuthenticationDirectiveForward 2.3 13 14 AuthenticationFailureReport 2.4 15 AuthenticationRequest 2.5 16 17 AuthenticationStatusReport 2.6 18 BaseStationChallenge 2.7 19 20 Blocking 2.8 21 BulkDeregistration 2.9 22 23 ChangeFacilities 2.10 24 25 ChangeService 2.11 26 ConnectionFailureReport 2.12 27 28 ConnectResource 2.13 29 CountRequest 2.14 30 31 DisconnectResource 2.15 32 FacilitiesDirective 2.16 33 34 FacilitiesDirective2 2.17 35 FacilitiesRelease 2.18 36 37 FacilitySelectedAndAvailable 2.19 38 FeatureRequest 2.20 39 40 FlashRequest 2.21 41 42 HandoffBack 2.22 43 HandoffBack2 2.23 44 45 HandoffMeasurementRequest 2.24 46 HandoffMeasurementRequest2 2.25 47 48 HandoffToThird 2.26 49 HandoffToThird2 2.27 50 51 InformationDirective 2.28 52 InformationForward 2.29 53 54 InstructionRequest 2.30 55 InterSystemAnswer 2.31 56 57 InterSystemPage 2.32 58 59 60 OPERATION DEFINITIONS 540 - 6 X.S0004-540-E v2.0

1 Table 3 Summary of MAP Operations 2 3 Operation Reference 4 InterSystemPage2 2.33 5 6 InterSystemSetup 2.34 7 8 InterSystemSMSDeliveryPointToPoint 2.35 9 InterSystemSMSPage 2.36 10 11 LocationRequest 2.37 12 MessageDirective 2.38 13 14 MobileOnChannel 2.39 15 Modify 2.40 16 17 MSInactive 2.41 18 NumberPortabilityRequest 2.42 19 20 OriginationRequest 2.43 21 OTASPRequest 2.44 22 23 ParameterRequest 2.45 24 25 QualificationDirective 2.46 26 QualificationRequest 2.47 27 28 QualificationRequest2 2.48 29 RandomVariableRequest 2.49 30 31 RedirectionDirective 2.50 32 RedirectionRequest 2.51 33 34 RegistrationCancellation 2.52 35 RegistrationNotification 2.53 36 37 Release 2.54 38 RemoteUserInteractionDirective 2.55 39 40 ResetCircuit 2.56 41 42 ResetTimer 2.57 43 RoutingRequest 2.58 44 45 Search 2.59 46 SeizeResource 2.60 47 48 ServiceRequest 2.61 49 SMSDeliveryBackward 2.62 50 51 SMSDeliveryForward 2.63 52 SMSDeliveryPointToPoint 2.64 53 54 SMSDeliveryPointToPointAck 2.65 55 56 57 58 59 60 540 - 7 OPERATION DEFINITIONS X.S0004-540-E v2.0

Table 3 Summary of MAP Operations 1 2 Operation Reference 3 4 SMSNotification 2.66 5 SMSRequest 2.67 6 7 SRFDirective 2.68 8 TBusy 2.69 9 10 TMSIDirective 2.70 11 TNoAnswer 2.71 12 13 TransferToNumberRequest 2.72 14 TrunkTest 2.73 15 16 TrunkTestDisconnect 2.74 17 18 Unblocking 2.75 19 UnreliableRoamerDataDirective 2.76 20 21 UnsolicitedResponse 2.77 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 OPERATION DEFINITIONS 540 - 8 X.S0004-540-E v2.0

1 2.1 AnalyzedInformation 2 3 4 The AnalyzedInformation (ANLYZD) operation is used by the MSC to provide notification to a 5 service logic network element (e.g., SCP, SN) that a trigger criteria at the Analyzed_Information DP 6 has been satisfied. Service logic may then invoke a service or services. An SCP may usethe 7 AnalyzedInformation (ANLYZD) operation to obtain an IMS Routing address from a VCC AS. 8 9 10 11 The following table lists the valid combinations of invoking and responding FEs. 12 INVOKING FE RESPONDING FE 13 14 Case 1 MSC SCP 15 16 Case 2 MSC SN 17 Case 3 SCP VCC AS 18 19 The AnalyzedInformation operation is initiated with a TCAP INVOKE (LAST). This is carried by 20 a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 21 22 23 AnalyzedInformation INVOKE Parameters Timer: ANZT 24 Field Value Type Reference Notes 25 26 Identifier SET [NATIONAL 18] M 520-1.3.2.1 27 28 Length variable octets M 520-1.3.2.1 29 Contents 30 31 BillingID (Originating) M 2.23 a 32 Digits (Dialed) M 2.105 33 34 MSCID (Originating) M 2.151 b 35 TransactionCapability M 2.285 36 37 TriggerType M 2.289 c 38 WINCapability M 2.299 d 39 40 CallingPartyName O 2.29 e 41 42 CallingPartyNumberDigits1 O 2.30 e, n 43 CallingPartyNumberDigits2 O 2.31 e, n 44 45 CallingPartySubaddress O 2.34 e 46 ConferenceCallingIndicator O 2.84 f 47 48 ElectronicSerialNumber O 2.112 g 49 IMSI O 2.127 g, m 50 51 LocationAreaID O 2.135 h 52 MobileDirectoryNumber O 2.139 i 53 54 MobileIdentificationNumber O 2.140 g, m 55 MSCIdentificationNumber O 2.152 j 56 57 OneTimeFeatureIndicator O 2.167 k 58 59 PreferredLanguageIndicator O 2.179 60 540 - 9 AnalyzedInformation X.S0004-540-E v2.0

1 RedirectingNumberDigits O 2.198 e 2 RedirectingPartyName O 2.200 e 3 4 RedirectingSubaddress O 2.201 e 5 ServingCellID O 2.225 h 6 7 SystemMyTypeCode O 2.260 8 TerminationAccessType O 2.279 l 9 10 Notes: 11 12 a. Include to identify the call. 13 14 b. Include to identify the requesting MSC. 15 16 c. Include to identify the trigger encountered. 17 d. Include to identify the WIN capabilities supported. 18 19 e. Include if available (i.e., provided in call origination). 20 21 f. Include to indicate the number of conferees already in the call. 22 23 g. Include if available to identify the MS. 24 25 h. Include if available (information related to MS origination). 26 27 i. Include if available for recording purposes (see DMH). 28 j. Include to identify the MSC sending the message and to indicate that the MSC is capable 29 of accepting digits in the international format. 30 31 k. Include if any OneTimeFeatureIndicator status bits are set (i.e., have value of 1). 32 33 l. Include if call involves a special access situation (e.g., Roamer port access). 34 35 m. Include as the service key, if applicable. 36 37 n. Send only the National (Significant) Number (with Nature of Number set to National) if the 38 E.164 country code of the caller’s number matches the E.164 country code used for 39 numbers from the MSC’s Country’s Numbering Plan. 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 AnalyzedInformation 540 - 10 X.S0004-540-E v2.0

1 The AnalyzedInformation operation success is reported with a TCAP RETURN RESULT (LAST). 2 This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 3 4 5 AnalyzedInformation RETURN RESULT Parameters 6 Field Value Type Reference Notes 7 8 Identifier SET [NATIONAL 18] M 520-1.3.2.2 9 Length variable octets M 520-1.3.2.2 10 11 Contents 12 13 AccessDeniedReason O 2.1 a 14 ActionCode O 2.2 b 15 16 AnnouncementList O 2.10 c 17 CarrierDigits O 2.37 d 18 19 ConferenceCallingIndicator O 2.84 e 20 Digits (Dialed) O 2.105 f 21 22 DisplayText O 2.106 d, m 23 DisplayText2 O 2.107 d, m 24 25 DMH_AccountCodeDigits O 2.108 g 26 DMH_AlternateBillingDigits O 2.109 g 27 28 DMH_BillingDigits O 2.110 g 29 30 DMH_RedirectionIndicator O 2.111 g, h 31 NoAnswerTime O 2.165 i 32 33 OneTimeFeatureIndicator O 2.167 j 34 RedirectingNumberDigits O 2.198 d 35 36 RoutingDigits O 2.209 d 37 TerminationList O 2.280 l 38 39 TerminationTriggers O 2.283 d 40 TriggerAddressList O 2.286 d 41 42 43 Notes: 44 a. Include if access is denied. If included, no other optional parameters shall be included (with 45 the exception of the AnnouncementList parameter). 46 47 b. Include if action to be performed is not implied through presence of other parameters. 48 49 c. Include if one or more tones or announcements are to be applied to the MS. 50 51 d. Include if applicable. 52 53 e. Include to direct that ongoing call be transformed into a Conference Call. 54 55 f. Include if digits remain to be translated by the MSC. 56 g. Include if available for recording purposes (see DMH). 57 58 h. Include if redirection may apply. 59 60 540 - 11 AnalyzedInformation X.S0004-540-E v2.0

i. Include to request an override of the Serving MSC's default No Answer Time value. 1 2 j. Include if modification to normal feature processing is required for the call in progress. 3 4 k. Intentionally left for future changes. 5 6 l. Include if call routing is required. 7 m. Include only one of these mutually exclusive parameters. 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 AnalyzedInformation 540 - 12 X.S0004-540-E v2.0

1 2.2 AuthenticationDirective 2 3 4 The AuthenticationDirective (AUTHDIR) operation is used to request modification of an MS’s 5 authentication parameters. It is also used to transport encryption parameters to the Serving MSC for 6 CDMA OTASP, TDMA OTASP and CDMA OTAPA. 7 8 The following table lists the valid combinations of invoking and responding FEs. 9 10 INVOKING FE RESPONDING FE 11 Case 1 AC HLR 12 13 Case 2 HLR Serving VLR 14 Case 3 Serving VLR Serving MSC 15 16 17 The AuthenticationDirective operation allows one or more of several possible authentication 18 processes to be initiated, including: 19 20 1. An update of SharedSecretData (SSD) when SSD is shared. 21 2. An update of SSD when SSD is not shared. 22 3. An update of the CallHistoryCount (COUNT) parameter value. 23 24 4. A Unique Challenge when SSD is shared (i.e., VLR-initiated). 25 5. A Unique Challenge when SSD is not shared (i.e., AC-initiated). 26 6. Revocation of SSD sharing. 27 28 7. OTA reauthentication. 29 30 The AuthenticationDirective operation is initiated with a TCAP INVOKE (LAST). This is carried 31 by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 32 33 AuthenticationDirective INVOKE Parameters Timer: ADT 34 35 Field Value Type Reference Notes 36 Identifier SET [NATIONAL 18] M 520-1.3.2.1 37 38 Length variable octets M 520-1.3.2.1 39 40 Contents 41 ElectronicSerialNumber M 2.112 42 43 MSID M 2.153 o, l 44 AuthenticationAlgorithmVersion O 2.11 a 45 46 AuthenticationResponseReauthentication O 2.16 q 47 AuthenticationResponseUniqueChallenge O 2.17 b 48 49 CallHistoryCount O 2.26 c 50 CarrierDigits O 2.37 r 51 52 CaveKey O 2.38 p 53 CDMAPrivateLongCodeMask O 2.61 m 54 55 DenyAccess O 2.100 d 56 57 DestinationDigits O 2.103 r 58 LocationAreaID O 2.135 e 59 60 540 - 13 AuthenticationDirective X.S0004-540-E v2.0

1 MobileStationMIN O 2.142 j 2 MSCID O 2.151 n 3 4 RandomVariableReauthentication O 2.191 q 5 RandomVariableSSD O 2.192 f 6 7 RandomVariableUniqueChallenge O 2.193 b 8 RoutingDigits O 2.209 r 9 10 SenderIdentificationNumber O 2.215 g 11 ServiceIndicator O 2.221 k 12 13 SharedSecretData O 2.227 c 14 SignalingMessageEncryptionKey O 2.228 m 15 16 SSDNotShared O 2.253 h 17 18 UpdateCount O 2.292 i 19 VoicePrivacyMask O 2.297 m 20 21 Notes: 22 23 a. May be included if SharedSecretData parameter is included. 24 25 b. Include if the Serving MSC shall initiate a Unique Challenge to the MS. 26 c. Include if the SystemCapabilities include CAVE Execution and AC administration policies 27 28 allow distribution of the SSD. 29 d. Include if release of system resources allocated for this access may be initiated by the MSC. 30 This may include disconnection of any call in progress. 31 32 e. May be included from VLR to Serving MSC. Usage from the HLR or AC is not defined. 33 34 f. Include if the Serving MSC shall initiate an SSD update to the MS. 35 36 g. May be included to identify the functional entity sending this message. 37 38 h. Include if the SSD at the VLR shall be discarded. 39 40 i. Include if the Serving MSC shall initiate a COUNT Update to the MS. 41 j. Include for CDMA OTASP to indicate the MIN value currently in the MS’s permanent 42 memory, for backward compatibility with IS-725, (Not included for CDMA OTAPA). 43 44 k. Include for CDMA and TDMA OTASP and CDMA OTAPA. 45 46 l. For CDMA OTASP, contains the Activation_MIN. For CDMA OTAPA, contains the MS’s 47 MSID at the start of the OTAPA session. 48 49 m. Include to transport encryption parameters to the Serving MSC. 50 51 n. Include for CDMA OTASP (but not for CDMA OTAPA) to identify Serving System. This 52 parameter is not included when AuthenticationDirective INVOKE is sent from the VLR to 53 the Serving MSC. 54 55 56 57 58 59 60 AuthenticationDirective 540 - 14 X.S0004-540-E v2.0

1 o. The HLR includes the IMSI type of MSID if the IMSI was present in the last message 2 received from the Serving System; otherwise the HLR includes the 3 MobileIdentificationNumber type of MSID. This may not be the type of MSID received 4 from the AC. The VLR includes the type of MSID last received from the Serving MSC; this 5 may not be the type of MSID received from the HLR. 6 7 p. Include for TDMA OTASP to transport TDMA Enhanced Privacy and Encryption 8 parameters to the Serving MSC. 9 10 q. Include if the Serving MSC shall initiate Reauthentication of the MS. 11 12 r. Include if authentication failed and the AC/HLR determines the call should be redirected. 13 These parameters may be included if the DenyAccess parameter is present. 14 15 16 The AuthenticationDirective operation success is reported with a TCAP RETURN RESULT 17 (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows. 18 19 AuthenticationDirective RETURN RESULT Parameters 20 21 Field Value Type Reference Notes 22 Identifier SET [NATIONAL 18] M 520-1.3.2.2 23 24 Length variable octets M 520-1.3.2.2 25 26 Contents 27 CallHistoryCount O 2.26 a 28 29 Notes: 30 31 a. Include if available at the VLR. 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 540 - 15 AuthenticationDirective X.S0004-540-E v2.0

2.3 AuthenticationDirectiveForward 1 2 3 The AuthenticationDirectiveForward (AUTHDIRFWD) operation is sent from the Anchor MSC 4 toward the Serving MSC to request initiation of one or more authentication processes for the 5 indicated MS.This operation can be relayed through the Tandem MSC(s). 6 7 The following table lists the valid combinations of invoking and responding FEs. 8 9 INVOKING FE RESPONDING FE 10 Case 1 Anchor MSC Serving MSC 11 12 Case 2 Anchor MSC Tandem MSC 13 14 Case 3 Tandem MSC Serving MSC 15 16 The AuthenticationDirectiveForward operation is initiated with a TCAP INVOKE (LAST). This is 17 carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as 18 follows: 19 20 21 AuthenticationDirectiveForward INVOKE Parameters Timer: ADFT 22 Field Value Type Reference Notes 23 24 Identifier SET [NATIONAL 18] M 520-1.3.2.1 25 26 Length variable octets M 520-1.3.2.1 27 Contents 28 29 InterMSCCircuitID M 2.129 30 AuthenticationResponseUniqueChallenge O 2.17 a 31 32 IMSI O 2.127 c 33 MobileIdentificationNumber O 2.140 c 34 35 RandomVariableUniqueChallenge O 2.193 a 36 UpdateCount O 2.292 b 37 38 Notes: 39 40 a. Include if the Serving MSC shall initiate a Unique Challenge to the indicated MS. 41 42 b. Include if the Serving MSC shall initiate a COUNT Update to the MS. 43 44 c. Include if available. At least one of these parameters shall be present. 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 AuthenticationDirectiveForward 540 - 16 X.S0004-540-E v2.0

1 The AuthenticationDirectiveForward operation success is reported with a TCAP RETURN 2 RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded 3 as follows: 4 5 6 AuthenticationDirectiveForward RETURN RESULT Parameters 7 Field Value Type Reference Notes 8 9 Identifier SET [NATIONAL 18] M 520-1.3.2.2 10 11 Length variable octets M 520-1.3.2.2 12 Contents 13 14 CountUpdateReport O 2.88 a 15 UniqueChallengeReport O 2.291 b 16 17 Notes: 18 19 a. Include to report outcome related to COUNT Update. 20 21 b. Include to report outcome related to Unique Challenge. 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 540 - 17 AuthenticationDirectiveForward X.S0004-540-E v2.0

2.4 AuthenticationFailureReport 1 2 3 The AuthenticationFailureReport (AFREPORT) operation is used to report on the failure of an 4 autonomously initiated authentication operation for an MS. 5 6 The following table lists the valid combinations of invoking and responding FEs. 7 8 INVOKING FE RESPONDING FE 9 Case 1 Serving MSC Serving VLR 10 11 Case 2 Serving VLR HLR 12 Case 3 HLR AC 13 14 15 The AuthenticationFailureReport operation is initiated with a TCAP INVOKE (LAST). This is 16 carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as 17 follows: 18 19 20 AuthenticationFailureReport INVOKE Parameters Timer: AFRT 21 Field Value Type Reference Notes 22 23 Identifier SET [NATIONAL 18] M 520-1.3.2.1 24 Length variable octets M 520-1.3.2.1 25 26 Contents 27 28 ElectronicSerialNumber M 2.112 29 MSID M 2.153 e, f 30 31 ReportType M 2.204 32 SystemAccessType M 2.258 33 34 SystemCapabilities (Serving) M 2.259 35 CallHistoryCount O 2.26 a 36 37 CallHistoryCountExpected O 2.27 a 38 MSCID (Serving MSC) O 2.151 b 39 40 SenderIdentificationNumber O 2.215 d 41 TerminalType O 2.278 g 42 43 44 Notes: 45 a. Include if ReportType parameter value is COUNT mismatch. 46 47 b. Should be included on IS-41-C or later. 48 c. Intentionally left for future modifications. 49 50 d. May be included to identify the functional entity sending the message. 51 e. Include the identifier with which the MS last accessed the system, unless that identifier was 52 a MIN-based IMSI, in which case the MobileIdentificationNumber (populated with the 53 MIN derived from that IMSI) should be included. 54 55 f. The HLR may replace the IMSI parameter, if received, by the MobileIdentificationNumber 56 parameter before forwarding this message to the AC. 57 58 g. May be included if received from the MS. 59 60 AuthenticationFailureReport 540 - 18 X.S0004-540-E v2.0

1 The AuthenticationFailureReport operation success is reported with a TCAP RETURN RESULT 2 (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows. 3 4 5 AuthenticationFailureReport RETURN RESULT Parameters 6 Field Value Type Reference Notes 7 8 Identifier SET [NATIONAL 18] M 520-1.3.2.2 9 Length variable octets M 520-1.3.2.2 10 11 Contents 12 13 AuthenticationAlgorithmVersion O 2.11 a 14 AuthenticationResponseUniqueChallenge O 2.17 b 15 16 CallHistoryCount O 2.26 c 17 CarrierDigits O 2.37 j 18 19 DenyAccess O 2.100 d 20 DestinationDigits O 2.103 j 21 22 MobileIdentificationNumber O 2.140 i 23 RandomVariableSSD O 2.192 e 24 25 RandomVariableUniqueChallenge O 2.193 b 26 RoutingDigits O 2.209 j 27 28 SharedSecretData O 2.227 c 29 30 SSDNotShared O 2.253 f 31 TerminalType O 2.278 g 32 33 UpdateCount O 2.292 h 34 35 Notes: 36 a. May be included if the SharedSecretData parameter is included. 37 38 b. Include if the MSC-V shall initiate a Unique Challenge to the MS. 39 c. Include if the SystemCapabilities include CAVE execution and AC administration policies 40 allow distribution of the SSD. 41 42 d. Include if the MSC may initiate a release of system resources allocated for this access. This 43 may include disconnection of any call in progress. 44 e. Include if the MSC-V shall initiate an SSD update to the MS. 45 46 f. Include if the VLR shall discard the SSD. 47 g. Include the value provisioned for this subscription on IS-41-C or later. 48 49 h. Include if the MSC-V shall initiate a COUNT Update to the MS. 50 i. Include if: 51 52 - SSD or pending SSD is shared, 53 - MIN is needed for authentication calculations, and 54 - MIN was not present as the MSID in the corresponding INVOKE. 55 56 j. Include if authentication failed and the AC/HLR determines the call should be redirected. 57 These parameters may be included if the DenyAccess parameter is present. 58 59 60 540 - 19 AuthenticationFailureReport X.S0004-540-E v2.0

1 2.5 AuthenticationRequest 2 3 The AuthenticationRequest (AUTHREQ) operation is used to request authentication of an 4 authentication-capable MS. 5 6 The following table lists the valid combinations of invoking and responding FEs. 7 8 INVOKING FE RESPONDING FE 9 10 Case 1 Serving MSC Serving VLR 11 Case 2 Serving VLR HLR 12 13 Case 3 HLR AC 14 15 Authentication may be initiated under various circumstances including: 16 17 1. When the MS is informed that authentication is required on system accesses and: 18 - the MS attempts initial registration, 19 - the MS attempts call origination, 20 - the MS attempts call termination, 21 - the MS issues an in-call flash request, 22 - the MS re-registers, or 23 - the MS issues an in-call flash request while global challenge is not in use. 24 25 2. When the MS is informed that authentication is not required on system accesses 26 and the MS attempts an initial system access (e.g., registration, origination, page 27 response). 28 29 Also, the AuthenticationRequest operation may vary depending on whether SSD is shared or not. 30 Note that the AuthenticationRequest (AUTHREQ) operation may result in a Network Directed 31 System Selection (NDSS) procedure. 32 33 34 The AuthenticationRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by 35 a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows. 36 37 AuthenticationRequest INVOKE Parameters Timer: ART 38 39 Field Value Type Reference Notes 40 Identifier SET [NATIONAL 18] M 520-1.3.2.1 41 42 Length variable octets M 520-1.3.2.1 43 44 Contents 45 ElectronicSerialNumber M 2.112 46 47 MSCID (Serving MSC) M 2.151 48 MSID M 2.153 k, l 49 50 SystemAccessType M 2.258 51 SystemCapabilities (Serving) M 2.259 52 53 AuthenticationData O 2.13 a 54 AuthenticationResponse O 2.14 c 55 56 CallHistoryCount O 2.26 c 57 CDMANetworkIdentification (Serving MSC) O 2.57 m 58 59 60 AuthenticationRequest 540 - 20 X.S0004-540-E v2.0

1 ConfidentialityModes (Actual) O 2.85 e 2 3 ControlChannelMode O 2.87 n 4 Digits (Dialed) O 2.105 g 5 6 PC_SSN (Serving MSC or VLR or HLR) O 2.176 h 7 8 RandomVariable O 2.189 c 9 SenderIdentificationNumber O 2.215 i 10 11 ServiceRedirectionCause O 2.222 o 12 SuspiciousAccess O 2.256 q 13 14 TerminalType O 2.278 j 15 TransactionCapability O 2.285 p 16 17 Notes: 18 19 a. Include if the authentication data input to the authentication signature calculation 20 procedures cannot be derived from other parameters (e.g., the SystemAccessType 21 parameter value is set to Call origination and the air interface encoding of dialed digits is 22 not TBCD). 23 24 b. This entry intentionally left blank. 25 26 c. Include if authentication parameters were requested and received on this system access. 27 28 d. This entry intentionally left blank. 29 30 e. Include if the SystemAccessType value is Flash Request and Signaling Message 31 Encryption is not active. 32 33 f. This entry intentionally left blank. 34 g. Include if the SystemAccessType value is Call Origination or Flash Request. 35 36 h. Include to override lower layer addressing if the receiving VLR, HLR, or AC is known to 37 be in the same national SS7 network. If included, it identifies the functional entity sending 38 the message. 39 40 i. May be included to identify the functional entity sending the message. 41 42 j. Should be included on IS-41-C or later. 43 44 k. Include the identifier with which the MS last accessed the system, unless that identifier was 45 a MIN-based IMSI, in which case the MobileIdentificationNumber (populated with the 46 MIN derived from that IMSI) should be included. 47 48 l. The HLR may replace the IMSI parameter, if received, by the MobileIdentificationNumber 49 parameter before forwarding this message to the AC. 50 51 m. Include for NDSS to identify the serving network. 52 53 n. Include for NDSS to identify the operating mode of the MS. 54 o. Include for NDSS to indicate reason of MS registration or access. 55 56 p. Include if system is NDSS capable. 57 58 q. Include if the access is suspicious, (e.g., if the access contains anomalous information such 59 as (extraneous digits). 60 540 - 21 AuthenticationRequest X.S0004-540-E v2.0

The AuthenticationRequest operation success is reported with a TCAP RETURN RESULT (LAST). 1 This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 2 3 4 AuthenticationRequest RETURN RESULT Parameters 5 6 Field Value Type Reference Notes 7 Identifier SET [NATIONAL 18] M 520-1.3.2.2 8 9 Length variable octets M 520-1.3.2.2 10 Contents 11 12 AnalogRedirectRecord O 2.8 j 13 AuthenticationAlgorithmVersion O 2.11 a 14 15 AuthenticationFailureEvent O 2.14 r 16 AuthenticationResponseUniqueChallenge O 2.17 b 17 CallHistoryCount O 2.26 c 18 19 CarrierDigits O 2.37 o 20 CaveKey O 2.38 d, p 21 22 CDMAPrivateLongCodeMask O 2.61 d 23 CDMARedirectRecord O 2.62 k 24 25 DataKey O 2.93 q 26 DenyAccess O 2.100 e 27 28 DestinationDigits O 2.103 o 29 MobileIdentificationNumber O 2.140 l 30 31 RoamingIndication O 2.208 m 32 ServiceRedirectionInfo O 2.223 j, k 33 RandomVariableSSD O 2.192 f 34 35 RandomVariableUniqueChallenge O 2.193 b 36 RoutingDigits O 2.209 o 37 38 SharedSecretData O 2.227 c 39 SignalingMessageEncryptionKey O 2.228 g, n, p 40 41 SSDNotShared O 2.253 h 42 UpdateCount O 2.292 i 43 44 VoicePrivacyMask O 2.297 d, n 45 46 Notes: 47 48 a. May be included if the SharedSecretData parameter is included. 49 50 b. Include if the Serving MSC shall initiate a Unique Challenge to the MS. 51 52 c. Include if the SystemCapabilities include CAVE Execution and AC administration policies 53 allow distribution of the SSD. 54 55 d. Include if appropriate and the SystemAccessType value is Call Origination or Page 56 Response. 57 58 59 60 AuthenticationRequest 540 - 22 X.S0004-540-E v2.0

1 e. Include if the MSC may initiate a release of system resources allocated for this access. This 2 may include disconnection of any call in progress. 3 4 f. Include if the Serving MSC shall initiate an SSD update. 5 6 g. Include if the SystemAccessType value is Call Origination or Page Response. 7 8 h. Include if the VLR shall discard the SSD. 9 i. Include if the Serving MSC should initiate COUNT Update to the MS. 10 11 j. Include for NDSS if HLR is to redirect the MS to an analog system. 12 13 k. Include for NDSS if HLR is to redirect the MS to a CDMA system. 14 15 l. Include if: 16 17 - SSD or pending SSD is shared, 18 19 - MIN is needed for authentication calculations, and 20 - MIN was not present as the MSID in the corresponding INVOKE. 21 22 m. Include for CDMA to support Enhanced Roaming Indicator. 23 24 n. Include if the SystemAccessType is set to Autonomous Registration and the MS Terminal 25 Type requires this parameter (e.g., PACS). 26 27 o. Include if authentication failed and the AC/HLR determines the call should be redirected. 28 These parameters may be included if the DenyAccess parameter is present. 29 30 p. Include if appropriate and the received SystemAccessType value is Autonomous 31 registration. 32 33 q. Include if applicable (e.g., MS is able to make data calls). 34 35 r. This parameter is used by the AC to inform the VLR of a failed authentication event without 36 denying access for the call. 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 540 - 23 AuthenticationRequest X.S0004-540-E v2.0

2.6 AuthenticationStatusReport 1 2 3 The AuthenticationStatusReport (ASREPORT) operation is used to report on the outcome of an 4 authentication operation initiated by the AC or VLR if SSD is shared. 5 6 The following table lists the valid combinations of invoking and responding FEs. 7 8 INVOKING FE RESPONDING FE 9 Case 1 Serving MSC Serving VLR 10 11 Case 2 Serving VLR HLR 12 Case 3 HLR AC 13 14 15 The AuthenticationStatusReport operation is initiated with a TCAP INVOKE (LAST). This is 16 carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as 17 follows: 18 19 20 AuthenticationStatusReport INVOKE Parameters Timer: ASRT 21 Field Value Type Reference Notes 22 23 Identifier SET [NATIONAL 18] M 520-1.3.2.1 24 Length variable octets M 520-1.3.2.1 25 26 Contents 27 28 ElectronicSerialNumber M 2.112 29 MSID M 2.153 k, l, f 30 31 SystemCapabilities (Serving) M 2.259 32 CountUpdateReport O 2.88 a 33 34 EnhancedPrivacyEncryptionReport O 2.114 m 35 MSCID (Serving) O 2.151 i 36 37 ReauthenticationReport O 2.196 j 38 SenderIdentificationNumber O 2.215 b 39 40 ServiceIndicator O 2.221 e 41 SignalingMessageEncryptionReport O 2.229 h 42 43 SSDUpdateReport O 2.254 c 44 45 UniqueChallengeReport O 2.291 d 46 VoicePrivacyReport O 2.298 g 47 48 Notes: 49 50 a. Include if report related to COUNT Update. 51 52 b. Include to identify the functional entity sending the message. 53 54 c. Include if report related to SSD Update. 55 d. Include if report related to Unique Challenge. 56 57 e. Include for OTASP (CDMAand TDMA) and CDMA OTAPA. 58 59 60 AuthenticationStatusReport 540 - 24 X.S0004-540-E v2.0

1 f. For CDMA OTASP, contains the Activation_MIN. For CDMA OTAPA contains the MS’s 2 MSID at the start of the OTAPA session. 3 4 g. Include to indicate the result of attempting to activate voice privacy on the air-interface 5 following MS Reauthentication during a CDMA or TDMA OTASP session or a CDMA 6 OTAPA session. 7 8 h. Include to indicate the result of attempting to activate signaling message encryption on the 9 air-interface following MS Reauthentication during a CDMA or TDMA OTASP session or 10 a CDMA OTAPA session. 11 12 i. Include to identify the Serving MSC. 13 14 j. Include if report related to TDMA Reauthentication. 15 16 k. Include the identifier with which the MS last accessed the system, unless that identifier was 17 a MIN-based IMSI, in which case the MobileIdentificationNumber (populated with the 18 MIN derived from that IMSI) should be included. 19 20 l. The HLR may replace the IMSI parameter, if received, by the MobileIdentificationNumber 21 paramter before forwarding this message to the AC. 22 23 m. Include if report related to TDMA Enhanced Privacy and Encryption. 24 25 The AuthenticationStatusReport operation success is reported with a TCAP RETURN RESULT 26 (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 27 28 29 AuthenticationStatusReport RETURN RESULT Parameters 30 Field Value Type Reference Notes 31 32 Identifier SET [NATIONAL 18] M 520-1.3.2.2 33 Length variable octets M 520-1.3.2.2 34 35 Contents 36 37 AuthenticationAlgorithmVersion O 2.11 a 38 AuthenticationResponseUniqueChallenge O 2.17 b 39 40 CallHistoryCount O 2.26 c 41 CarrierDigits O 2.37 h 42 43 DenyAccess O 2.100 d 44 DestinationDigits O 2.103 h 45 46 MobileIdentificationNumber O 2.140 i 47 RandomVariableSSD O 2.192 e 48 49 RandomVariableUniqueChallenge O 2.193 b 50 RoutingDigits O 2.209 h 51 52 SharedSecretData O 2.227 c 53 54 SSDNotShared O 2.253 f 55 UpdateCount O 2.292 g 56 57 Notes: 58 59 a. May be included if the SharedSecretData parameter is included. 60 540 - 25 AuthenticationStatusReport X.S0004-540-E v2.0

b. Include if the Serving MSC shall initiate a Unique Challenge to the MS. 1 2 c. Include if the SystemCapabilities include CAVE Execution and AC administration policies 3 allow distribution of the SSD. 4 5 d. Include if the MSC may initiate a release of system resources allocated for this access. This 6 may include disconnection of any call in progress. 7 8 e. Include if the Serving MSC shall initiate an SSD update to the MS. 9 10 f. Include if the VLR shall discard the SSD. 11 g. Include if the Serving MSC shall initiate a COUNT Update to the MS. 12 13 h. Include if authentication failed and the AC/HLR determines the call should be redirected. 14 These parameters may be included if the DenyAccess parameter is present. 15 16 i. Include if: 17 18 - SSD or pending SSD is shared. 19 20 - MIN is needed for authentication calculations, and 21 22 - MIN was not present as the MSID in the corresponding INVOKE. 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 AuthenticationStatusReport 540 - 26 X.S0004-540-E v2.0

1 2.7 BaseStationChallenge 2 3 4 The BaseStationChallenge (BSCHALL) operation is used to request a response to a Base Station 5 Challenge Order received from an MS. 6 7 The following table lists the valid combinations of invoking and responding FEs. 8 9 INVOKING FE RESPONDING FE 10 Case 1 Serving MSC Serving VLR 11 12 Case 2 Serving VLR HLR 13 Case 3 HLR AC 14 15 16 The BaseStationChallenge operation is initiated with a TCAP INVOKE (LAST). This is carried by 17 a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 18 19 BaseStationChallenge INVOKE Parameters Timer: BSCT 20 21 Field Value Type Reference Notes 22 23 Identifier SET [NATIONAL 18] M 520-1.3.2.1 24 Length variable octets M 520-1.3.2.1 25 26 Contents 27 ElectronicSerialNumber M 2.112 28 29 MSID M 2.153 c, d, e 30 RandomVariableBaseStation M 2.190 31 32 SenderIdentificationNumber O 2.215 a 33 ServiceIndicator O 2.221 b 34 35 36 Notes: 37 a. Include to identify the functional entity sending the message. 38 39 b. Include for CDMA OTASP or CDMA OTAPA. 40 41 c. For CDMA OTASP, contains the Activation_MIN. For CDMA OTAPA contains the MS’s 42 MSID at the start of the OTAPA session. 43 44 d. Include the identifier with which the MS last accessed the system unless that identifier was 45 a MIN-based IMSI, in which case the MobileIdentificationNumber (populated with the 46 MIN derived from that IMSI) should be included. 47 48 e. The HLR may replace the IMSI parameter by the MobileIdentificationNumber parameter 49 before forwarding this message to the AC. 50 51 52 53 54 55 56 57 58 59 60 540 - 27 BaseStationChallenge X.S0004-540-E v2.0

The BaseStationChallenge operation success is reported with a TCAP RETURN RESULT (LAST). 1 This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 2 3 4 BaseStationChallenge RETURN RESULT Parameters 5 Field Value Type Reference Notes 6 7 Identifier SET [NATIONAL 18] M 520-1.3.2.2 8 9 Length variable octets M 520-1.3.2.2 10 Contents 11 12 AuthenticationResponseBaseStation M 2.15 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 BaseStationChallenge 540 - 28 X.S0004-540-E v2.0

1 2.8 Blocking 2 3 4 The Blocking (BLOCKING) operation is used to inform an MSC that the designated circuit has been 5 removed from service. 6 7 The following table lists the possible combinations of invoking and responding FEs. 8 INVOKING FE RESPONDING FE 9 10 Case 1 MSC MSC 11 12 13 The Blocking operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 14 QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 15 16 Blocking INVOKE Parameters Timer: BLKT 17 18 Field Value Type Reference Notes 19 Identifier SET [NATIONAL 18] M 520-1.3.2.1 20 21 Length variable octets M 520-1.3.2.1 22 Contents 23 24 InterMSCCircuitID M 2.129 25 26 The Blocking operation success is reported with a TCAP RETURN RESULT (LAST). This is 27 carried by a TCAP RESPONSE package. This parameter Set is encoded as follows: 28 29 30 Blocking RETURN RESULT Parameters 31 Field Value Type Reference Notes 32 33 Identifier SET [NATIONAL 18] M 520-1.3.2.2 34 35 Length zero octets M 520-1.3.2.2 36 Contents 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 540 - 29 Blocking X.S0004-540-E v2.0

2.9 BulkDeregistration 1 2 3 This BulkDeregistration (BULKDEREG) operation is used by a VLR to inform the HLR that all MS 4 data associated with the HLR has been removed from the VLR. 5 6 The following table lists the valid combinations of invoking and responding FEs 7 8 INVOKING FE RESPONDING FE 9 Case 1 Serving VLR HLR 10 11 12 The BulkDeregistration operation is initiated with a TCAP INVOKE (LAST). This is carried by a 13 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 14 15 BulkDeregistration INVOKE Parameters Timer: BDT 16 17 Field Value Type Reference Notes 18 19 Identifier SET [NATIONAL 18] M 520-1.3.2.1 20 Length variable octets M 520-1.3.2.1 21 22 Contents 23 SenderIdentificationNumber M 2.215 24 25 26 27 TheBulkDeregistration operation success is reported with a TCAP RETURN RESULT (LAST). 28 29 This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 30 31 BulkDeregistration RETURN RESULT Parameters 32 33 Field Value Type Reference Notes 34 Identifier SET [NATIONAL 18] M 520-1.3.2.2 35 36 Length zero octets M 520-1.3.2.2 37 Contents 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 BulkDeregistration 540 - 30 X.S0004-540-E v2.0

1 2.10 ChangeFacilities 2 3 4 The ChangeFacilities (CHGFAC) operation is used to connect appropriate facilities at each MSC, on 5 the forward handoff chain in order to effect in-call service change. This operation is invoked from 6 the Anchor MSC only if a change of facilities is needed and facilities have not been reserved. This 7 operation is not needed in the multiple vocoder case. 8 9 The following table lists the valid combinations of invoking and responding FEs. 10 11 INVOKING FE RESPONDING FE 12 Case 1 Anchor MSC/IWF Serving MSC 13 14 Case 2 Anchor MSC/IWF Tandem MSC 15 Case 3 Tandem MSC Tandem MSC 16 17 Case 4 Tandem MSC Serving MSC 18 19 One of the following results is returned: 20 21 1. Notification that the appropriate facilities, were successfully connected at each MSC on the 22 forward handoff chain, and existing facilities were released. 23 24 2. Notification that needed facilities were not allocated at an MSC on the forward handoff 25 chain. In this case, existing facilities were left intact in order to continue supporting the 26 current service. 27 28 The ChangeFacilities operation is initiated with a TCAP INVOKE(LAST). This is carried by a 29 TCAP CONVERSATION WITHOUT PERMISSION package. The Parameter Set is encoded as 30 follows: 31 32 ChangeFacilities INVOKE Parameters Timer: CFT 33 34 Field Value Type Reference Notes 35 36 Identifier SET [NATIONAL 18] M 520-1.3.2.1 37 Length variable octets M 520-1.3.2.1 38 39 Contents 40 CDMAPrivateLongCodeMask O 2.61 f 41 42 CDMAServiceConfigurationRecord O 2.65 b 43 44 DataKey O 2.93 f 45 DataPrivacyParameters O 2.94 i, f 46 47 ElectronicSerialNumber O 2.112 c 48 InterMSCCircuitID O 2.129 a, c 49 50 IMSI O 2.127 j 51 ISLPInformation O 2.132 d 52 53 MobileIdentificationNumber O 2.140 j 54 RandomVariable O 2.189 f 55 56 SecondInterMSCCircuitID O 2.213 c, g 57 TDMABandwidth O 2.267 h 58 59 60 540 - 31 ChangeFacilities X.S0004-540-E v2.0

1 TDMAServiceCode O 2.273 e 2 VoicePrivacyMask O 2.297 f 3 4 Notes: 5 6 a. Include to indicate the InterMSCCircuitID of the existing service. Always include. 7 8 b. Include appropriate CDMA records that describe the granted service. 9 c. Include to identify the existing call. 10 11 d. Include appropriate ISLP Information, if needed, for circuit-mode (e.g., ADS, G3 Fax) 12 services. If excluded for circuit mode data calls, interpret as ISLP supported. 13 14 e. Include appropriate TDMA parameters that describe the granted service. 15 16 f. Include appropriate privacy parameters for the granted service, if available and if allowed 17 for the user. 18 19 g. Include to indicate the InterMSCCircuitID of the new circuit required to support the new 20 service. 21 22 h. Include appropriate TDMA parameters that describe the granted service. If omitted, assume 23 to be Full-rate Digital Traffic Channel value. 24 25 i. Do not include if previously sent in a handoff invoke message (e.g., FacilitiesDirective2, 26 HandoffBack2, or HandofftoThird2). 27 28 j. Include if available. At least one of these parameters should be present. 29 30 The ChangeFacilities operation success is reported with a TCAP RETURN RESULT(LAST). This 31 is carried by a TCAP CONVERSATION WITH PERMISSION package. The Parameter Set is 32 encoded as follows: 33 34 35 ChangeFacilities RETURN RESULT Parameters 36 37 Field Value Type Reference Notes 38 Identifier SET [NATIONAL 18] M 520-1.3.2.2 39 40 Length variable octets M 520-1.3.2.2 41 Contents 42 43 ReasonList O 2.195 a 44 45 Notes: 46 47 a. Include to identify the reason(s) for change request failure (e.g., service not allowed). 48 49 50 51 52 53 54 55 56 57 58 59 60 ChangeFacilities 540 - 32 X.S0004-540-E v2.0

1 2.11 ChangeService 2 3 4 The ChangeService (CHGSERV) operation is used by the Serving MSC to request the Anchor MSC 5 to grant an MS its Service Change Request that came as a result of either an initial request or as a 6 result of a negotiated In Call Service Change request between the Serving MSC and the MS. 7 8 ChangeService only supports the ability to change a single service. It does not support multiple 9 service scenarios. 10 11 The following table lists the valid combinations of invoking and responding FEs. 12 13 INVOKING FE RESPONDING FE 14 Case 1 Serving MSC Anchor MSC/IWF 15 16 Case 2 Serving MSC Tandem MSC 17 Case 3 Tandem MSC Tandem MSC 18 19 Case 4 Tandem MSC Anchor MSC/IWF 20 21 The following results are possible: 22 23 1. A notification that the requested service, which could be the initial requested 24 service or a negotiated service arrived at using an earlier invocation of the 25 CHGSERV operation, was granted. 26 2. A notification that the in-call service change request was unsuccessful, and the 27 associated reason(s) for the failure are returned. The unsuccessful case occurs 28 29 because the requested service is not allowed for the user or cannot be supported at 30 all MSCs on the forward handoff chain. 31 3. A substitute allowed or preferred service (or a list of services, possibly ranked) to 32 be used for service negotiation with the MS is returned to the Serving MSC 33 because the requested service is not allowed or cannot be supported at all MSCs 34 on the forward handoff chain. 35 36 The ChangeService operation is initiated with a TCAP INVOKE(LAST). This is carried by a TCAP 37 QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 38 39 40 ChangeService INVOKE Parameters Timer: CST 41 Field Value Type Reference Notes 42 43 Identifier SET [NATIONAL 18] M 520-1.3.2.1 44 Length variable octets M 520-1.3.2.1 45 46 Contents 47 48 CDMAServiceConfigurationRecord O 2.65 a 49 CDMAServiceOptionList O 2.67 b 50 51 ChangeServiceAttributes O 2.80 c 52 ElectronicSerialNumber O 2.112 d 53 54 InterMSCCircuitID O 2.129 j 55 IMSI O 2.127 k 56 57 ISLPInformation O 2.132 e 58 MobileIdentificationNumber O 2.140 k 59 60 540 - 33 ChangeService X.S0004-540-E v2.0

1 TDMABandwidth O 2.267 g 2 TDMADataMode O 2.272 i 3 4 TDMAServiceCode O 2.273 f 5 TDMAVoiceMode O 2.276 h 6 7 Notes: 8 9 a. Include appropriate CDMA service configuration information that describes the requested 10 service. 11 12 b. Include, if available, to indicate additional services (for service negotiation) related to the 13 requested service. Services not supported by the tandem MSC and Anchor MSC will be 14 filtered. 15 16 c. Include to indicate attributes describing the nature of the service change request. This 17 parameter indicates whether or not a ChangeFacilities operation is necessary to reserve and 18 activate the facilities required for the requested service. This parameter indicates whether 19 or not this operation is executed after successful Service Negotiation between the Serving 20 MSC and the MS. 21 22 d. Include if appropriate. 23 24 e. Include if applicable for circuit-mode (e.g., ADS, G3Fax) services. If excluded for circuit 25 mode data calls, interpret as ISLP supported. 26 27 f. Include appropriate TDMA parameters that describe the requested service. 28 29 g. Include appropriate TDMA parameters that describe the requested service. If omitted, 30 assume to be Full-rate Digital Traffic Channel. 31 h. Include for a requested service change to voice mode. 32 33 i. Include for a requested service change to data or fax mode. 34 35 j. Include to indicate the InterMSCCircuitID of the existing service. Always include. 36 37 k. Include if available. At least one of these parameters should be present. 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 ChangeService 540 - 34 X.S0004-540-E v2.0

1 The ChangeService operation success is reported with a TCAP RETURN RESULT(LAST). This is 2 carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 3 4 5 ChangeService RETURN RESULT Parameters 6 Field Value Type Reference Notes 7 8 Identifier SET [NATIONAL 18] M 520-1.3.2.2 9 Length variable octets M 520-1.3.2.2 10 11 Contents 12 13 CDMAPrivateLongCodeMask O 2.61 f 14 CDMAServiceConfigurationRecord O 2.65 b 15 16 CDMAServiceOptionList O 2.67 c 17 ChangeServiceAttributes O 2.80 d 18 19 DataKey O 2.93 f 20 DataPrivacyParameters O 2.94 g, f 21 22 RandomVariable O 2.189 f 23 ReasonList O 2.195 a 24 25 TDMAServiceCode O 2.273 e 26 VoicePrivacyMask O 2.297 f 27 28 29 Notes: 30 a. Include to list the reasons for change request failure. 31 32 b. Include appropriate CDMA service configuration information that describes the granted 33 service or a substitute service. 34 35 c. Include to indicate the authorized service options for service negotiation. Services not 36 supported by the Anchor MSC and Tandem MSC shall be filtered. 37 38 d. Include to indicate whether or not the use of new facilities and the removal of old facilities 39 was accomplished with the execution of a ChangeFacilities operation. 40 41 e. Include to describe the granted service for TDMA systems, or include to indicate that the 42 requested service was denied. 43 44 f. Include privacy parameters for the granted service, if available and if allowed for the user. 45 46 g. Do not include if previously sent in a handoff invoke message (e.g., FacilitiesDirective2, 47 HandoffBack2, or HandofftoThird2). 48 49 50 51 52 53 54 55 56 57 58 59 60 540 - 35 ChangeService X.S0004-540-E v2.0

2.12 ConnectionFailureReport 1 2 3 The ConnectionFailureReport (CONNFAILRPT) operation is used by the MSC to report to a service 4 logic network element the failure of a connection to an IP or SN. 5 6 The following table lists the valid invoking and responding FEs. 7 8 INVOKING FE RESPONDING FE 9 Case 1 MSC HLR or SCP or SN 10 11 Case 2 HLR SCP or SN 12 Case 3 SCP or SN HLR or SCP or SN 13 14 The ConnectionFailureReport operation is initiated with a TCAP INVOKE (LAST). This is carried 15 by a TCAP CONVERSATION WITH PERMISSION package. The Parameter Set is encoded as 16 17 follows: 18 19 ConnectionFailureReport INVOKE Parameters Timer: CFRT 20 21 Field Value Type Reference Notes 22 Identifier SET [NATIONAL 18] M 520-1.3.2.1 23 24 Length variable octets M 520-1.3.2.1 25 Contents 26 27 FailureType M 2.119 28 29 FailureCause O 2.118 a 30 31 Notes: 32 a. Include if the ISUP Cause Indicator is available. 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 ConnectionFailureReport 540 - 36 X.S0004-540-E v2.0

1 2.13 ConnectResource 2 3 4 The ConnectResource (CONNRES) operation is used by a Service Control Function (SCF) to request 5 the establishment of a connection between a Service Switching Function (SSF) and a Specialized 6 Resource Function (SRF) when the SCF determines that a specialized resource is needed for service 7 logic execution. 8 9 The following table lists the valid invoking and responding FEs. 10 11 INVOKING FE RESPONDING FE 12 Case 1 HLR or SCP or SN MSC 13 14 Case 2 HLR SCP or SN 15 Case 3 SCP or SN HLR or SCP or SN 16 17 The ConnectResource operation is initiated with a TCAP INVOKE (LAST). This is carried by a 18 19 TCAP CONVERSATION WITHOUT PERMISSION package. The Parameter Set is encoded as 20 follows: 21 22 ConnectResource INVOKE Parameters Timer: (note a) 23 24 Field Value Type Reference Notes 25 Identifier SET [NATIONAL 18] M 520-1.3.2.1 26 27 Length variable octets M 520-1.3.2.1 28 Contents 29 30 DestinationDigits M 2.103 31 32 CarrierDigits O 2.37 b 33 RoutingDigits O 2.209 b 34 35 Notes: 36 37 a. The SCF starts the WIN Response Timer (WINRT) awaiting an InstructionRequest INVOKE from 38 the SRF. The SCF also starts the Reset Timer (REST). When the ResetTimer expires, the SCF sends 39 a ResetTimer INVOKE toward the SSF (i.e., MSC) to initialize and start the Service Switching 40 Function Timer (SSFT). 41 When an intervening SCF receives the ConnectResource INVOKE, it stops the Service Request 42 Timer (SVRT), sends a ConnectResource INVOKE to the requesting SSF, and starts the Service 43 Control Function Timer (SCFT). 44 45 b. Include if applicable. 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 540 - 37 ConnectResource X.S0004-540-E v2.0

2.14 CountRequest 1 2 3 The CountRequest (COUNTREQ) operation is used to obtain the current value of the 4 CallHistoryCount parameter. 5 6 The following table lists the valid combinations of invoking and responding FEs. 7 8 INVOKING FE RESPONDING FE 9 Case 1 AC HLR 10 11 Case 2 HLR Old Serving VLR 12 13 The CountRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 14 QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 15 16 17 CountRequest INVOKE Parameters Timer: CRT 18 19 Field Value Type Reference Notes 20 Identifier SET [NATIONAL 18] M 520-1.3.2.1 21 22 Length variable octets M 520-1.3.2.1 23 Contents 24 25 ElectronicSerialNumber M 2.112 26 MSID M 2.153 b 27 28 SenderIdentificationNumber O 2.215 a 29 30 Notes: 31 32 a. Include to identify the functional entity sending the message. 33 34 b. The HLR includes the IMSI type of MSID if the IMSI was present in the last message 35 received from the Old Serving System; othewise the HLR includes the 36 MobileIdentificationNumber type of MSID. This may not be the type of MSID received 37 from the AC. 38 39 40 The CountRequest operation success is reported with a TCAP RETURN RESULT (LAST). This is 41 carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 42 43 CountRequest RETURN RESULT Parameters 44 45 Field Value Type Reference Notes 46 Identifier SET [NATIONAL 18] M 520-1.3.2.2 47 48 Length variable octets M 520-1.3.2.2 49 50 Contents 51 CallHistoryCount O 2.26 a 52 53 Notes: 54 55 a. Include if CallHistoryCount was maintained by the VLR. 56 57 58 59 60 CountRequest 540 - 38 X.S0004-540-E v2.0

1 2.15 DisconnectResource 2 3 4 The DisconnectResource (DISCONNRES) operation is used by the SCF to instruct the SSF to release 5 a connection established between the SSF and an SRF when the SCF determines that this connection 6 should be released. This operation is normally applicable after a ConnectResource operation. 7 8 The following table lists the valid invoking and responding FEs. 9 10 INVOKING FE RESPONDING FE 11 Case 1 HLR or SCP or SN MSC 12 13 Case 2 HLR SCP or SN 14 Case 3 SCP or SN HLR or SCP or SN 15 16 The DisconnectResource operation is initiated with a TCAP INVOKE (LAST). This is carried by a 17 TCAP CONVERSATION WITHOUT PERMISSION package. The Parameter Set is encoded as 18 19 follows: 20 21 DisconnectResource INVOKE Parameters Timer: (note a) 22 23 Field Value Type Reference Notes 24 Identifier SET [NATIONAL 18] M 520-1.3.2.1 25 26 Length variable octets M 520-1.3.2.1 27 Contents 28 29 30 Notes: 31 32 a. When the SSF receives the DisconnectResource; INVOKE, it stops the Service Switching Function 33 Timer (SSFT) and initializes and starts the operation timer that was stopped when the 34 ConnectResource INVOKE was received. 35 When an intervening SCF receives the DisconnectResource INVOKE, it stops the Service Control 36 Function Timer (SCFT), sends a DisconnectResource INVOKE to the requesting SSF, and initializes 37 and starts the Service Request Timer (SVRT) that was stopped when the ConnectResource INVOKE 38 was received. 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 540 - 39 DisconnectResource X.S0004-540-E v2.0

2.16 FacilitiesDirective 1 2 3 The FacilitiesDirective (FACDIR) operation is used to request that the Target MSC initiate the 4 Handoff-Forward task. 5 6 The following table lists the valid combinations of invoking and responding FEs. 7 8 INVOKING FE RESPONDING FE 9 Case 1 Anchor MSC Target MSC 10 11 Case 2 Serving MSC Target MSC 12 Case 3 Tandem MSC Target MSC 13 14 15 One of two possible results is returned: 16 17 1. Notification that the request was accepted, including the parameters of the voice 18 channel selected by the Target MSC on the designated cell. 19 2. Notification that the request was unsuccessful because a voice channel on the 20 designated cell is not available. 21 22 The FacilitiesDirective operation is initiated with a TCAP INVOKE (LAST). This is carried by a 23 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 24 25 FacilitiesDirective INVOKE Parameters Timer: HOT 26 27 Field Value Type Reference Notes 28 29 Identifier SET [NATIONAL 18] M 520-1.3.2.1 30 Length variable octets M 520-1.3.2.1 31 32 Contents 33 BillingID (Anchor MSC) M 2.23 i 34 35 ChannelData (Serving) M 2.81 a 36 37 ElectronicSerialNumber M 2.112 38 InterMSCCircuitID M 2.129 39 40 InterSwitchCount M 2.130 41 MobileIdentificationNumber M 2.140 42 43 ServingCellID M 2.225 44 StationClassMark M 2.255 45 46 TargetCellID M 2.263 47 ConfidentialityModes (Desired) O 2.85 b 48 49 HandoffReason O 2.125 c 50 HandoffState O 2.126 d 51 52 SignalingMessageEncryptionKey O 2.228 e 53 54 TDMABurstIndicator (Serving) O 2.268 f 55 TDMACallMode O 2.269 g 56 57 TDMAChannelData (Serving) O 2.270 f 58 59 60 FacilitiesDirective 540 - 40 X.S0004-540-E v2.0

1 VoicePrivacyMask O 2.297 h 2 3 Notes: 4 5 a. This parameter has a length of 0 if a TDMA channel is in use. 6 7 b. Include if MS supports Signaling Message Encryption or Voice Privacy. The parameter 8 shall be carried forward in any subsequent handoff. 9 10 c. Include if known. 11 12 d. Include if call is still in the awaiting answer or alerting state. 13 14 e. Include if Signaling Message Encryption may apply. The parameter shall be carried 15 forward in any subsequent handoff. 16 f. Include if a TDMA channel is in use. 17 18 g. Include to indicate the acceptable call mode. 19 20 h. Include if the Voice Privacy may apply. The parameter shall be carried forward in any 21 subsequent handoff. 22 23 i. The first six octets are assigned by the Anchor MSC but the segment counter is modified as 24 the call is handed off. 25 26 27 The FacilitiesDirective operation success is reported with a TCAP RETURN RESULT (LAST). 28 This is carried by a TCAP CONVERSATION WITH PERMISSION package. The Parameter Set is 29 encoded as follows: 30 31 FacilitiesDirective RETURN RESULT Parameters 32 33 Field Value Type Reference Notes 34 35 Identifier SET [NATIONAL 18] M 520-1.3.2.2 36 Length variable octets M 520-1.3.2.2 37 38 Contents 39 ChannelData (Target) M 2.81 a 40 41 ConfidentialityModes (Actual) O 2.85 b 42 TDMABurstIndicator (Target) O 2.268 c 43 44 TDMAChannelData (Target) O 2.270 d 45 46 Notes: 47 48 a. This parameter has a length of 0 if a TDMA channel has been assigned. 49 50 b. Include if ConfidentialityModes was requested to reflect actual assignment. 51 c. May be included if a TDMA channel has been assigned. 52 53 d. Include if a TDMA channel has been assigned. 54 55 56 57 58 59 60 540 - 41 FacilitiesDirective X.S0004-540-E v2.0

2.17 FacilitiesDirective2 1 2 3 The FacilitiesDirective2 (FACDIR2) operation is used to request that the Target MSC initiate the 4 Handoff-Forward task. This operation differs from the FacilitiesDirective operation in its addition 5 of support for CDMA, multi-band TDMA, and NAMPS MSs. 6 7 The following table lists the valid combinations of invoking and responding NEs. 8 9 INVOKING NE RESPONDING NE 10 11 Case 1 Anchor MSC Target MSC 12 13 Case 2 Serving MSC Target MSC 14 15 Case 3 Tandem MSC Target MSC 16 17 One of two possible results is returned: 18 19 1. Notification that the request was accepted, including the parameters of the voice channel 20 selected by the Target MSC on the designated cell. 21 22 2. Notification that the request was unsuccessful because a voice channel on the designated 23 cell is not available. 24 25 26 The FacilitiesDirective2 operation is initiated with a TCAP INVOKE (LAST). This is carried by a 27 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 28 29 FacilitiesDirective2 INVOKE Parameters Timer: HOT 30 31 Field Value Type Reference Notes 32 33 Identifier SET [NATIONAL 18] M 520-1.3.2.1 34 Length variable octets M 520-1.3.2.1 35 36 Contents 37 BillingID (Anchor MSC) M 2.23 a 38 39 ElectronicSerialNumber M 2.112 40 InterMSCCircuitID M 2.129 41 42 InterSwitchCount M 2.130 43 ServingCellID M 2.225 b 44 45 AlertCode O 2.4 c 46 BaseStationManufacturerCode O 2.21 d 47 48 CaveKey O 2.38 e 49 50 CDMA2000HandoffInvokeIOSData O 2.39 f 51 CDMABandClassList O 2.44 g 52 53 CDMACallMode O 2.45 h, i, j 54 CDMAChannelData (Serving) O 2.46 k, av 55 56 h CDMAConnectionReferenceList O 2.54 , l, m 57 58 CDMAMobileProtocolRevision O 2.55 h , n 59 60 FacilitiesDirective2 540 - 42 X.S0004-540-E v2.0

1 CDMAMSMeasuredChannelIdentity O 2.56 o 2 3 CDMAPrivateLongCodeMask O 2.61 p 4 CDMAServiceConfigurationRecord O 2.65 h 5 , q, r 6 CDMAServiceOptionList O 2.67 h, s 7 8 CDMAServingOneWayDelay O 2.68 b, h 9 10 CDMAStationClassMark O 2.72 h, n, t, u 11 h n 12 CDMAStationClassMark2 O 2.73 , 13 CDMATargetMAHOList O 2.75 v 14 15 CDMATargetMeasurementList O 2.77 w 16 ChannelData (Serving) O 2.81 x 17 18 ConfidentialityModes (Desired) O 2.85 y 19 DataKey O 2.93 m 20 21 DataPrivacyParameters O 2.94 z 22 23 HandoffReason O 2.125 aa 24 HandoffState O 2.126 ab 25 26 IMSI O 2.127 ac 27 ISLPInformation (Desired) O 2.132 ad 28 29 MobileIdentificationNumber O 2.140 ac 30 h 31 MSLocation O 2.155 32 NAMPSCallMode O 2.156 j, ae 33 34 NAMPSChannelData (Serving) O 2.157 af 35 36 NonPublicData O 2.166 ag 37 RandomVariable O 2.189 m 38 39 SignalingMessageEncryptionKey O 2.228 ah 40 SpecialHandling O 2.249 ai 41 42 StationClassMark O 2.255 x, aj, ak 43 44 SystemOperatorCode O 2.261 al 45 TargetCellID O 2.263 am 46 47 TDMABandwidth (Desired) O 2.267 an 48 TDMABurstIndicator (Serving) O 2.268 aj 49 50 TDMACallMode O 2.269 j, ao, aj 51 52 TDMAChannelData (Serving) O 2.270 aj 53 54 55 56 57 58 59 60 540 - 43 FacilitiesDirective2 X.S0004-540-E v2.0

1 TDMAServiceCode O 2.273 aq ap, 2 TDMATerminalCapability O 2.274 aq 3 4 TDMAVoiceCoder O 2.275 ar 5 TerminalType O 2.278 as 6 7 UserZoneData O 2.294 at 8 9 VoicePrivacyMask O 2.297 au 10 Notes: 11 a. The first six octets are assigned by the Anchor MSC but the segment counter is mod- 12 ified as the call is handed off. 13 14 b. For CDMA, the ServingCellID and CDMAServingOneWayDelay parameters cor- 15 respond to the active set member having the shortest signal path to the MS (time ref- 16 erence cell). 17 c. Include if the MS is alerting to specify special alerting treatment. 18 19 d. Include if the MS is IS-136 or later and BSMC-specific signaling is supported. 20 e. Include if available and TDMA Enhanced Privacy and Encryption apply. This pa- 21 rameter shall be carried forward in subsequent handoffs. 22 23 f. If the Serving MSC and the Target MSC support TIA/EIA/IS-2001-A (IOS v4.1) or 24 later, include to convey required cdma2000 IOS handoff invoke information (e.g., 25 IS-2000 Channel Identity, IS-2000 Service Configuration Record, IS-2000 Mobile 26 Capabilities, [see IOS]). 27 g. Include to indicate band classes and band subclasses supported by the MS. 28 29 h. Include if CDMA handoff. 30 i. Include to indicate the acceptable call mode if other than AMPS (i.e., CDMA or 31 NAMPS). 32 j. The values in these parameters shall not contain conflicting information. 33 34 k. The Long Code Mask field should be set to the long code mask in use at the Serving 35 MSC. 36 l. Include to indicate state information for the requested service option(s) connection 37 reference. 38 m. Include for CDMA data privacy, if applicable and if authorized for the user. 39 40 n. Include to indicate information for the current band in use. 41 o. Include to indicate the band class and frequency that has been measured by the MS 42 in preparation for hard handoff. 43 p. This parameter shall be provided if the MS supports CDMA and is authorized to 44 have Voice Privacy and the CDMAPrivateLongCodeMask parameter is available. 45 46 q. Include to indicate a requested service configuration other than the one agreed upon 47 by the Serving and Target Systems. 48 r. Include if the Serving MSC, the Target MSC, or both support only an A-Interface prior 49 to IOS version 4.1. 50 s. Include to indicate the authorized service options. 51 t. Include if an 800 MHz CDMA channel is in use for an IS-41-C system. 52 u. Ignore on reception if the CDMAStationClassMark2 is also received and recognized. 53 54 v. Include for either the CDMA MAHO case or the CDMA forced handoff case. 55 w. Include for the CDMA non-MAHO case. 56 x. Include if an AMPS or NAMPS channel is in use. 57 58 59 60 FacilitiesDirective2 540 - 44 X.S0004-540-E v2.0

1 y. Include if MS supports Signaling Message Encryption, Voice Privacy, Data Privacy, 2 or TDMA Enhanced Privacy and Encryption. This parameter shall be carried for- 3 ward in subsequent handoffs. 4 5 z. Include to indicate last known value of DP Data field. Do not include if contained in 6 the CDMAConnectionReferenceList parameter. 7 aa. Include if known. 8 ab. Include if call is in the awaiting answer or alerting state. 9 10 ac. Include if available. At least one of these parameters should be present. 11 ad. Include appropriate ISLP information, if needed for circuit mode (e.g., ADS, 12 G3Fax) services. If not included for circuit mode data calls, interpret as ISLP sup- 13 ported. 14 15 ae. Include to indicate the acceptable call mode if other than AMPS (i.e., NAMPS). 16 af. Include if an NAMPS channel is in use. 17 ag. Include to provide information regarding Non-Public Information Display (e.g., User 18 Zone updates) at the target system. 19 ah. Include if MS supports Signaling Message Encryption, Voice Privacy or Data Privacy. 20 This parameter shall be carried forward in subsequent handoffs. 21 ai. Include if any fields in this parameter are non-zero. 22 23 aj. Include if a TDMA channel is in use. 24 ak. Include if the CDMA MS supports 800 MHz analog operation and the target system 25 does not support CDMA. 26 al. Include if the MS is IS-136 or later and SOC-specific signaling is supported. 27 am. Include if an AMPS, NAMPS, or a TDMA handoff. 28 an. Include to describe the requested TDMA traffic channel. If omitted for data calls, as- 29 sume to be Full-rate Digital Traffic Channel only. 30 ao. Include to indicate the acceptable call mode. 31 32 ap. Include to indicate the requested TDMA service information. 33 aq. Include if MS is TDMA IS-136 or later. 34 ar. Include to indicate subscriber or network preferences for Voice Coder selection 35 when multiple voice coders exist. If not included, or if preferences cannot be sup- 36 ported, the receiving system will select Voice Coder based on Terminal Capability. 37 38 as. Include for statistical purposes. 39 at. Include if the MS user is authorized for User Zone Service. Include to permit the 40 Target MSC to validate MS selection of User Zone. 41 42 au. This parameter shall be provided if the MS supports TDMA and is authorized to 43 have Voice Privacy and the VoicePrivacyMask parameter is available. 44 av. Include for CDMA handoff, if available. 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 540 - 45 FacilitiesDirective2 X.S0004-540-E v2.0

The FacilitiesDirective2 operation success is reported with a TCAP RETURN RESULT (LAST). 1 This is carried by a TCAP CONVERSATION WITH PERMISSION package. The Parameter Set is 2 encoded as follows: 3 4 5 FacilitiesDirective2 RETURN RESULT Parameters 6 7 Field Value Type Reference Notes 8 Identifier SET [NATIONAL 18] M 520-1.3.2.2 9 10 Length variable octets M 520-1.3.2.2 11 Contents 12 13 BSMCStatus O 2.25 a 14 CDMA2000HandoffResponseIOSData O 2.40 b 15 16 CDMAChannelData (Target) O 2.46 c, d 17 CDMACodeChannelList O 2.51 c 18 , e 19 CDMAConnectionReferenceList O 2.54 c, f, g 20 21 CDMASearchParameters O 2.63 c, h 22 23 c CDMASearchWindow O 2.64 , i 24 25 CDMAServiceConfigurationRecord O 2.65 c , j, k 26 ChannelData (Target) O 2.81 l, m 27 28 ConfidentialityModes (Actual) O 2.85 n 29 ISLPInformation (Actual) O 2.132 o 30 31 NAMPSChannelData (Target) O 2.157 p 32 SOCStatus O 2.262 a 33 34 TargetCellID O 2.263 q 35 36 a TDMABurstIndicator (Target) O 2.268 37 38 TDMAChannelData (Target) O 2.270 r 39 TDMAVoiceCoder (Target) O 2.275 s 40 41 Notes: 42 a. May be included if target is a TDMA channel. 43 b. If the Serving MSC and the Target MSC support TIA/EIA/IS-2001-A (IOS v4.1) or 44 later, include to convey required cdma2000 IOS handoff response information 45 (e.g. IS-95 Channel Identity, IS-2000 Channel Identity, IS-2000 Service Configura- 46 47 tion Record, IS-2000 Non-Negotiable Service Configuration Record, Extended 48 Handoff Direction Parameters, Hard Handoff Parameters, [see IOS]). 49 c. Include if target is a CDMA channel. 50 d. Include only when IS-95 channels are to be used at the Target MSC. 51 Note: The presence of this parameter does not preclude the use of the 52 53 CDMA2000HandoffResponseIOSData parameter to convey this same information. 54 e. For cdma2000 mobiles, the CDMACodeChannelList is used for the Fundamental 55 Channel (FCH). 56 f. Include to indicate state information for the granted service option(s) connection ref- 57 erence. 58 59 60 FacilitiesDirective2 540 - 46 X.S0004-540-E v2.0

1 g. Include appropriate granted privacy parameters, if available and if allowed for the us- 2 er. 3 h. Include for implementations without the CDMA2000HandoffResponseIOSData pa- 4 rameter. 5 i. Include when communicating with TIA/EIA-41-D or earlier system. (replaced 6 by CDMASearchParameters). 7 8 j. If the CDMAServiceConfigurationRecord was received in the INVOKE, include to in- 9 dicate a granted service configuration, other than the one agreed upon by the Serving 10 and Target Systems. 11 k. Include if the Serving MSC, the Target MSC, or both support only an A interface prior 12 to IOS v4.1. This information will be ignored if the same information is received within 13 the CDMA2000HandoffResponseIOSData parameter. 14 l. Include if target is an AMPS or NAMPS channel. 15 m. For forced handoffs to an analog voice channel, include the VMAC value set to the 16 target system’s expected MS power level at handoff for the identified AMPS or 17 NAMPS Channel Number. 18 n. Include to reflect actual assignment if ConfidentialityModes (Desired) parameter was 19 present in the INVOKE. 20 o. Include appropriate ISLP Information, if needed, for circuit-mode (e.g., ADS, G3 Fax) 21 services. If excluded for circuit mode data calls, interpret as ISLP Supported. 22 23 p. Include if target is an NAMPS channel. 24 q. Include for an AMPS, NAMPS, or a TDMA handoff. 25 r. Include if target is a TDMA channel. 26 s. Include to indicate the granted Voice Coder if applicable. If not included the MS 27 28 shall continue using the current Voice Coder. 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 540 - 47 FacilitiesDirective2 X.S0004-540-E v2.0

2.18 FacilitiesRelease 1 2 3 The FacilitiesRelease (FACREL) operation is used to request that allocated resources for a call 4 segment be released. 5 6 INVOKING FE RESPONDING FE 7 8 Case 1 MSC MSC 9 (Serving, Target, Anchor, or Tandem) (Serving, Target, Anchor, or Tandem) 10 11 The FacilitiesRelease operation is initiated with a TCAP INVOKE (LAST). This is carried by a 12 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 13 14 15 FacilitiesRelease INVOKE Parameters Timer: CTT 16 17 Field Value Type Reference Notes 18 Identifier SET [NATIONAL 18] M 520-1.3.2.1 19 20 Length variable octets M 520-1.3.2.1 21 Contents 22 23 InterMSCCircuitID M 2.129 24 ReleaseReason M 2.203 25 26 BillingID O 2.23 a 27 IMSI O 2.127 b 28 29 MobileIdentificationNumber O 2.140 b 30 31 Notes: 32 33 a. Include for reporting the number of segments toward the Anchor MSC (see DMH). 34 35 b. Include if required by interconnection agreement. 36 37 The FacilitiesRelease operation success is reported with a TCAP RETURN RESULT (LAST). This 38 is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 39 40 41 FacilitiesRelease RETURN RESULT Parameters 42 43 Field Value Type Reference Notes 44 Identifier SET [NATIONAL 18] M 520-1.3.2.2 45 46 Length variable octets M 520-1.3.2.2 47 Contents 48 49 BillingID O 2.23 a 50 51 Notes: 52 53 a. Include for reporting the number of segments toward the Anchor MSC (see DMH). 54 55 56 57 58 59 60 FacilitiesRelease 540 - 48 X.S0004-540-E v2.0

1 2.19 FacilitySelectedAndAvailable 2 3 4 The FacilitySelectedAndAvailable (FAVAIL) operation is used by a Serving MSC to obtain call 5 treatment instructions from an SCP or SN. 6 7 The following table lists the valid combinations of invoking and responding FEs. 8 INVOKING FE RESPONDING FE 9 10 Case 1 MSC SCP 11 12 Case 2 MSC SN 13 14 The FacilitySelectedAndAvailable operation is initiated with a TCAP INVOKE (LAST). This is 15 carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as 16 follows: 17 18 FacilitySelectedAndAvailable INVOKE Parameters Timer: FAVT 19 20 Field Value Type Reference Notes 21 22 Identifier SET [NATIONAL 18] M 520-1.3.2.1 23 Length variable octets M 520-1.3.2.1 24 25 Contents 26 BillingID (Serving) M 2.23 27 28 MSCID(Serving) M 2.151 29 TransactionCapability M 2.285 30 31 TriggerType M 2.289 a 32 WINCapability M 2.299 b 33 34 CallingPartyName O 2.29 c 35 36 CallingPartyNumberDigits1 O 2.30 c 37 CallingPartyNumberDigits2 O 2.31 c 38 39 CallingPartySubaddress O 2.34 c 40 ElectronicSerialNumber O 2.112 41 42 GroupInformation O 2.124 c 43 IMSI O 2.127 c, d 44 45 LegInformation O 2.133 c 46 LocationAreaID O 2.135 c 47 48 MobileDirectoryNumber O 2.139 d, e 49 MobileIdentificationNumber O 2.140 c, d 50 51 MSCIdentificationNumber O 2.152 f 52 53 OneTimeFeatureIndicator O 2.167 g 54 PilotBillingID O 2.177 c 55 56 PilotNumber O 2.178 c 57 PreferredLanguageIndicator O 2.179 c 58 59 60 540 - 49 FacilitySelectedAndAvailable X.S0004-540-E v2.0

1 RedirectingNumberDigits O 2.198 c 2 RedirectingPartyName O 2.200 c 3 4 RedirectingSubaddress O 2.201 c 5 ServingCellID O 2.225 c 6 7 SystemMyTypeCode O 2.260 8 TerminationAccessType O 2.279 h 9 10 Notes: 11 12 a. Indicates the detected trigger. 13 14 b. Include to identify the WIN capabilities supported. 15 16 c. Include if available. 17 d. One must be present for use as service key. 18 19 e. Include if available for recording purposes (see DMH). 20 21 f. Include to identify the MSC sending the message. 22 23 g. Include if any OneTimeFeatureIndicator status bits are set (i.e., have value of 1). 24 25 h. Include if call involves a special access situation (e.g., Roamer port access). 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 FacilitySelectedAndAvailable 540 - 50 X.S0004-540-E v2.0

1 The FacilitySelectedAndAvailable operation success is reported with a TCAP RETURN RESULT 2 (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 3 4 5 FacilitySelectedAndAvailable RETURN RESULT Parameters 6 Field Value Type Reference Notes 7 8 Identifier SET [NATIONAL 18] M 520-1.3.2.2 9 Length variable octets M 520-1.3.2.2 10 11 Contents 12 13 AccessDeniedReason O 2.1 a 14 ActionCode O 2.2 b 15 16 AlertCode O 2.4 c 17 DisplayText O 2.106 d, i 18 19 DisplayText2 O 2.107 i, d 20 DMH_AccountCodeDigits O 2.108 e 21 22 DMH_AlternateBillingDigits O 2.109 e 23 DMH_BillingDigits O 2.110 e 24 25 DMH_RedirectionIndicator O 2.111 e, f 26 NoAnswerTime O 2.165 g 27 28 OneTimeFeatureIndicator O 2.167 h 29 30 TerminationTriggers O 2.283 d 31 TriggerAddressList O 2.286 d 32 33 Notes: 34 35 a. Include if access is denied. If included, no other optional parameters shall be included. 36 37 b. Include if action to be performed is not implied through presence of other parameters. 38 39 c. Include to specify special alerting treatment. 40 41 d. Include if applicable. 42 e. Include if available for recording purposes (see DMH). 43 44 f. Include if redirection may apply. 45 46 g. Include to request an override of the Serving MSC's default No Answer Time value. 47 48 h. Include if modification to normal feature processing is required for the call in progress. 49 50 i. Include only one of these mutually exclusive parameters. 51 52 53 54 55 56 57 58 59 60 540 - 51 FacilitySelectedAndAvailable X.S0004-540-E v2.0

2.20 FeatureRequest 1 2 3 4 This operation was named RemoteFeatureControlRequest prior to 5 revision C of IS-41. 6 7 8 The FeatureRequest (FEATREQ) operation is used to request feature-related treatment on behalf of 9 a registered MS. 10 11 The following table lists the valid combinations of invoking and responding FEs. 12 13 INVOKING FE RESPONDING FE 14 15 Case 1 Serving MSC HLR 16 (Note 1) 17 18 Case 2 Serving MSC OTAF 19 (Note 2) 20 Case 3 HLR SCP or SN 21 22 Case4 Serving MSC Serving VLR 23 (Note 3) 24 25 Case 5 Serving VLR HLR 26 (Note 3) 27 28 Notes: 29 30 1. This case is termed a ‘direct' FeatureRequest operation, since it occurs directly 31 between the Serving MSC and the HLR without the involvement of the VLR. 32 2. This case is only applicable to CDMA OTASP. 33 3. These cases are no longer recommended. 34 35 The FeatureRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 36 QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 37 38 39 FeatureRequest INVOKE Parameters Timer: FRRT 40 Field Value Type Reference Notes 41 42 Identifier SET [NATIONAL 18] M 520-1.3.2.1 43 44 Length variable octets M 520-1.3.2.1 45 Contents 46 47 Digits (Dialed) M 2.105 48 ElectronicSerialNumber M 2.112 49 50 MSID M 2.153 k 51 BillingID (Originating) O 2.23 a 52 53 CallingPartyName O 2.29 j 54 CallingPartyNumberDigits1 O 2.30 b, l 55 56 CallingPartyNumberDigits2 O 2.31 b, l 57 58 CallingPartySubaddress O 2.34 b 59 60 FeatureRequest 540 - 52 X.S0004-540-E v2.0

1 ConferenceCallingIndicator O 2.84 c 2 3 MobileDirectoryNumber O 2.139 d 4 MobileIdentificationNumber O 2.140 n 5 6 MSCID (Serving) O 2.151 e 7 8 MSCIdentificationNumber O 2.152 m 9 OneTimeFeatureIndicator O 2.167 f 10 11 PC_SSN O 2.176 g 12 SenderIdentificationNumber O 2.215 h 13 14 SystemMyTypeCode (originating MSC) O 2.260 o 15 TransactionCapability O 2.285 i 16 17 Notes: 18 19 a. Include for recording purposes or for call correlation (see DMH). 20 21 b. Include if applicable. 22 23 c. Include to indicate the number of conferees already in the call. 24 25 d. Include if available for recording purposes (see DMH). 26 e. Include to identify the Anchor MSC. (This may become the Originating MSC for 27 subsequent call redirection.) 28 29 f. Include if any OneTimeFeatureIndicator parameter status bits are set (i.e., have value of 1). 30 31 g. Include if SS7 may be used for subsequent call redirection. 32 33 h. Include if different from the MSCIdentificationNumber to identify the functional entity 34 sending the message. 35 36 i. Include on IS-41-C or later. 37 38 j. Include if calling party name information is known. 39 k. Include the identifier with which the MS last accessed the system, unless that identifier was 40 41 a MIN-based IMSI, in which case the MobileIdentificationNumber (populated with the 42 MIN derived from that IMSI) should be included. 43 l. Send only the National (Significant) Number (with Nature of Number set to National) if 44 45 the E.164 country code of the caller’s number matches the E.164 country code used for 46 numbers from the MSC’s Country’s numbering plan. 47 m. Include to identify the initiating MSC and to indicate that the MSC is capable of accepting 48 49 digits in the international format. 50 n. Include if known and if the IMSI has been included as MSID. 51 52 o. Include if available to identify the originating system manufacturer. 53 54 55 56 57 58 59 60 540 - 53 FeatureRequest X.S0004-540-E v2.0

The FeatureRequest operation success is reported with a TCAP RETURN RESULT (LAST). This 1 is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 2 3 4 FeatureRequest RETURN RESULT Parameters 5 Field Value Type Reference Notes 6 7 Identifier SET [NATIONAL 18] M 520-1.3.2.2 8 9 Length variable octets M 520-1.3.2.2 10 Contents 11 12 FeatureResult M 2.121 13 AccessDeniedReason O 2.1 a 14 15 ActionCode O 2.2 b 16 AnnouncementList O 2.10 c 17 18 CallingPartyNumberString1 O 2.32 d 19 CallingPartyNumberString2 O 2.33 d 20 21 CallingPartySubaddress O 2.34 d 22 23 CarrierDigits O 2.37 d 24 ConferenceCallingIndicator O 2.84 e 25 26 Digits (Dialed) O 2.105 f 27 Digits (Destination) O 2.105 l 28 29 DisplayText O 2.106 m, p 30 DisplayText2 O 2.107 m, p 31 32 DMH_AccountCodeDigits O 2.108 g 33 DMH_AlternateBillingDigits O 2.109 g 34 35 DMH_BillingDigits O 2.110 g 36 DMH_RedirectionIndicator O 2.111 d 37 38 GroupInformation O 2.124 h 39 40 MobileDirectoryNumber O 2.139 g 41 NoAnswerTime O 2.165 d 42 43 OneTimeFeatureIndicator O 2.167 i 44 PACAIndicator O 2.171 j 45 46 PilotNumber O 2.178 h 47 PreferredLanguageIndicator O 2.179 q 48 49 RedirectingNumberDigits O 2.198 d 50 RedirectingNumberString O 2.199 d 51 52 RedirectingSubaddress O 2.201 d 53 RoutingDigits O 2.209 d 54 55 TerminationList O 2.280 k 56 57 58 59 60 FeatureRequest 540 - 54 X.S0004-540-E v2.0

1 TerminationTriggers O 2.283 d 2 3 TriggerAddressList O 2.286 o 4 5 Notes: 6 7 a. Include if access is denied. If included, no other optional parameters shall be included (with 8 the exception of the AnnouncementList parameter). 9 10 b. Include if action to be performed is not implied through presence of other parameters. 11 c. Include if provision of one or more tones or announcements is required. 12 13 d. Include if applicable. 14 15 e. Include to direct that ongoing call be transformed into a Conference Call. 16 17 f. Include if digits remain to be analyzed by the MSC. Encode the Digits (dialed) as 18 International if: 19 20 - The digits being returned are the result of a stored translation of the termination address into 21 a destination address (e.g., the expansion of an abbreviated dialing string), and 22 23 - the Serving MSC is known to be capable of accepting digits in an International format (e.g., 24 the MSCIdentificationNumber parameter was received). 25 26 g. Include if applicable and for recording purposes (see DMH). 27 h. Include for multileg calls. 28 29 i. Include if modification to normal feature processing is required for call in progress. 30 31 j. Include to indicate PACA priority level. 32 33 k. Include if call routing is required. 34 35 l. Include to return a Temporary Reference Number from an OTAF for CDMA OTASP. 36 37 m. Include for local termination to an MS if a related feature is active. 38 n. Intentionally left for future modifications. 39 40 o. Include to indicate addresses associated with active WIN triggers. 41 42 p. Include only one of these mutually exclusive parameters. 43 44 q. May be included to identify the Preferred Language to use when playing announcements. 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 540 - 55 FeatureRequest X.S0004-540-E v2.0

2.21 FlashRequest 1 2 3 The FlashRequest (FLASHREQ) operation is used to forward a flash received from an MS engaged 4 in a call toward the Anchor MSC (possibly via one or more Tandem MSCs). 5 6 The following table lists the valid combinations of invoking and responding FEs. 7 8 INVOKING FE RESPONDING FE 9 Case 1 Serving MSC Anchor MSC 10 11 Case 2 Serving MSC Tandem MSC 12 Case 3 Tandem MSC Tandem MSC 13 14 Case 4 Tandem MSC Anchor MSC 15 16 The FlashRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 17 QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 18 19 20 FlashRequest INVOKE Parameters Timer: FRT 21 22 Field Value Type Reference Notes 23 Identifier SET [NATIONAL 18] M 520-1.3.2.1 24 25 Length variable octets M 520-1.3.2.1 26 Contents 27 28 Digits (Dialed) M 2.105 a 29 InterMSCCircuitID M 2.129 30 31 ConfidentialityModes (Actual) O 2.85 b 32 ElectronicSerialNumber O 2.112 33 34 EmergencyServicesRoutingDigits O 2.113 d 35 36 IMSI O 2.127 c 37 MobileIdentificationNumber O 2.140 c 38 39 Notes: 40 41 a. The Digits parameter is sent non-encrypted. 42 43 b. Include if either the SignalingMessageEncryptionKey parameter or the CaveKey parameter 44 was provided to the Serving MSC. 45 46 c. Include if available. 47 48 d. Include to specify the location of the MS. 49 50 51 52 53 54 55 56 57 58 59 60 FlashRequest 540 - 56 X.S0004-540-E v2.0

1 The FlashRequest operation success is reported with a TCAP RETURN RESULT (LAST). This is 2 carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 3 4 5 FlashRequest RETURN RESULT Parameters 6 Field Value Type Reference Notes 7 8 Identifier SET [NATIONAL 18] M 520-1.3.2.2 9 Length zero octets M 520-1.3.2.2 10 11 Contents 12 13 SpecialHandling O 2.249 a 14 15 Notes: 16 17 a. Include if any fields in this parameter are non-zero. 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 540 - 57 FlashRequest X.S0004-540-E v2.0

2.22 HandoffBack 1 2 3 The HandoffBack (HANDBACK) operation is used by the Serving MSC to request that the Target 4 MSC initiate the Handoff-Back task. This task is used to handoff a call to a Target MSC to which 5 the Serving MSC is already connected, for the call in question, via an inter-MSC trunk. 6 7 The following table lists the valid combinations of invoking and responding FEs. 8 9 INVOKING FE RESPONDING FE 10 Case 1 Serving MSC Target MSC 11 12 13 One of two possible results is returned: 14 15 1. Notification that the request was accepted, including the parameters of the voice 16 17 channel selected by the Target MSC on the designated cell. 18 2. Notification that the request was unsuccessful because a voice channel on the 19 designated cell is not available. 20 21 The HandoffBack operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 22 QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 23 24 HandoffBack INVOKE Parameters Timer: HOT 25 26 Field Value Type Reference Notes 27 28 Identifier SET [NATIONAL 18] M 520-1.3.2.1 29 Length variable octets M 520-1.3.2.1 30 31 Contents 32 ChannelData (Serving) M 2.81 a 33 34 InterMSCCircuitID M 2.129 35 MobileIdentificationNumber M 2.140 36 37 ServingCellID M 2.225 38 39 TargetCellID M 2.263 40 BillingID O 2.23 b 41 42 ConfidentialityModes (Desired) O 2.85 c 43 HandoffReason O 2.125 d 44 45 HandoffState O 2.126 e 46 SignalingMessageEncryptionKey O 2.228 c, f 47 48 TDMABurstIndicator (Serving) O 2.268 g 49 TDMACallMode O 2.269 h, g 50 51 TDMAChannelData (Serving) O 2.270 g 52 VoicePrivacyMask O 2.297 i 53 54 55 Notes: 56 a. This parameter has a length of 0 if a TDMA channel is in use. 57 58 b. Include to maintain segment count. 59 60 HandoffBack 540 - 58 X.S0004-540-E v2.0

1 c. Include if MS supports Signaling Message Encryption or Voice Privacy. The parameter 2 shall be carried forward in any subsequent handoff. 3 4 d. Include if known. 5 6 e. Include if the call is in the awaiting answer or alerting state. 7 8 f. Include if Signaling Message Encryption may apply. This parameter shall be carried 9 forward in any subsequent handoff. 10 11 g. Include if a TDMA channel is in use. 12 h. Include to indicate acceptable call modes. 13 14 i. Include if the Voice Privacy may apply. This parameter shall be carried forward in any 15 subsequent handoff. 16 17 18 The HandoffBack operation success is reported with a TCAP RETURN RESULT (LAST). This is 19 carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 20 21 HandoffBack RETURN RESULT Parameters 22 23 Field Value Type Reference Notes 24 25 Identifier SET [NATIONAL 18] M 520-1.3.2.2 26 Length variable octets M 520-1.3.2.2 27 28 Contents 29 ChannelData (Target) M 2.81 a 30 31 ConfidentialityModes (Actual) O 2.85 b 32 TDMABurstIndicator (Target) O 2.268 c 33 34 TDMAChannelData (Target) O 2.270 d 35 36 Notes: 37 38 a. This parameter has a length of 0 if a TDMA channel has been assigned. 39 40 b. Include if ConfidentialityModes was requested to reflect actual assignment. 41 42 c. May be included if a TDMA channel has been assigned. 43 d. Include if a TDMA channel has been assigned. 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 540 - 59 HandoffBack X.S0004-540-E v2.0

2.23 HandoffBack2 1 2 3 The HandoffBack2 (HANDBACK2) operation is used by the Serving MSC to request that the Target 4 MSC initiate the Handoff-Back task. This task is used to handoff a call to a Target MSC to which 5 the Serving MSC is already connected, for the call in question, via an inter-MSC trunk. This 6 operation differs from the HandoffBack operation in its addition of support for CDMA, multi-band 7 TDMA, and NAMPS MSs. 8 9 The following table lists the valid combinations of invoking and responding FEs. 10 11 INVOKING FE RESPONDING FE 12 13 Case 1 Serving MSC Target MSC 14 15 16 The HandoffBack2 operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 17 QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 18 19 HandoffBack2 INVOKE Parameters Timer: HOT 20 21 Field Value Type Reference Notes 22 23 Identifier SET [NATIONAL 18] M 520-1.3.2.1 24 Length variable octets M 520-1.3.2.1 25 26 Contents 27 BillingID M 2.23 28 29 InterMSCCircuitID M 2.129 30 ServingCellID M 2.225 a 31 32 BaseStationManufacturerCode O 2.21 b 33 CaveKey O 2.38 c 34 35 CDMA2000HandoffInvokeIOSData O 2.39 d 36 CDMABandClassList O 2.42 e 37 38 CDMACallMode O 2.45 f, g, h 39 40 CDMAChannelData (Serving) O 2.46 f , i, j 41 42 CDMAConnectionReferenceList O 2.54 f, k, l 43 CDMAMobileProtocolRevision O 2.55 f 44 45 CDMAMSMeasuredChannelIdentity O 2.56 m 46 CDMAPrivateLongCodeMask O 2.61 n 47 48 CDMAServiceConfigurationRecord O 2.65 f, o, p 49 50 f CDMAServiceOptionList O 2.67 , q 51 CDMAServingOneWayDelay O 2.68 a f 52 , 53 CDMAStationClassMark O 2.72 f, ae, r, s 54 55 CDMAStationClassMark2 O 2.73 f, ae 56 57 CDMATargetMAHOList O 2.75 t 58 59 60 HandoffBack2 540 - 60 X.S0004-540-E v2.0

1 CDMATargetMeasurementList O 2.77 u 2 3 ChannelData (Serving) O 2.81 v 4 ConfidentialityModes (Desired) O 2.85 w 5 6 DataKey O 2.93 l 7 8 DataPrivacyParameters O 2.94 x 9 HandoffReason O 2.125 y 10 11 HandoffState O 2.126 z 12 IMSI O 2.127 aa 13 14 InterSwitchCount O 2.130 y 15 16 ISLPInformation O 2.132 ab 17 MobileIdentificationNumber O 2.140 aa 18 19 MSLocation O 2.155 f 20 21 NAMPSCallMode O 2.156 h, ac 22 23 NAMPSChannelData (Serving) O 2.157 ad 24 RandomVariable O 2.189 l 25 26 SignalingMessageEncryptionKey O 2.228 w 27 SpecialHandling O 2.249 ae 28 29 StationClassMark O 2.255 v, af, ag 30 31 SystemOperatorCode O 2.261 ah 32 TargetCellID O 2.263 ai 33 34 TDMABandwidth (Desired) O 2.267 aj 35 TDMABurstIndicator (Serving) O 2.268 af 36 37 TDMACallMode O 2.269 h, af, ak 38 39 TDMAChannelData (Serving) O 2.270 af 40 TDMAServiceCode O 2.273 al, am 41 42 TDMATerminalCapability O 2.273 al 43 TDMAVoiceCoder O 2.275 an 44 45 TerminalType O 2.278 ao 46 VoicePrivacyMask O 2.297 ap 47 48 Notes: 49 a. For CDMA, the ServingCellID and CDMAServingOneWayDelay parameters cor- 50 respond to the active set member having the shortest signal path to the MS (time ref- 51 erence cell). 52 53 b. Include if MS is IS-136 or later and BSMC-specific signaling is supported. 54 c. Include if available and TDMA Enhanced Privacy and Encryption apply. This pa- 55 rameter shall be carried forward in subsequent handoffs. 56 57 58 59 60 540 - 61 HandoffBack2 X.S0004-540-E v2.0

d. If the Serving MSC and the Target MSC support TIA/EIA/IS-2001-A (IOS v4.1) or 1 later, include to convey required cdma2000 handoff invoke information (e.g., 2 IS-2000 Channel Identity, IS-2000 Mobile Capabilities, IS-2000 Service Configu- 3 ration Record, [see IOS]). 4 5 e. Include to indicate band classes and band subclasses supported by the MS. 6 f. Include if CDMA handoff. 7 8 g. Include to indicate the acceptable call mode of other than AMPS (i.e., CDMA or 9 NAMPS). 10 h. The values in these parameters shall not contain conflicting information. 11 i. The Long Code Mask field should be set to the long code mask in use at the serving 12 MSC. 13 14 j. Include only when IS-95 channels are in use at the Serving MSC. 15 Note: use of the CDMA2000HandoffInvokeIOSData parameter to convey this infor- 16 mation is required for CDMA2000 and later channels. 17 k. Include to indicate state information for the requested service option(s) connection 18 reference. 19 l. Include for CDMA data privacy, if applicable and if authorized for the user. 20 m. Include to indicate the band class and frequency that has been measured by the MS 21 in preparation for hard handoff. 22 n. This parameter shall be provided if the MS supports CDMA and is authorized to have 23 Voice Privacy and the CDMAPrivateLongCodeMask (CDMAPLCM) parameter is 24 available. 25 o. Include to indicate a requested service configuration other than the one agreed upon 26 by the Serving and Target Systems. 27 28 p. Include if the Serving MSC and the Target MSC support only an A-interface prior to 29 IOS version 4.1. 30 q. Include to indicate the authorized service options. 31 r. Include if an 800 MHz CDMA channel is in use for an IS-41-C system. 32 s. Ignore on reception if the CDMAStationClassMark2 is also received and recognized. 33 t. Include for either the CDMA MAHO case or the forced CDMA handoff case. 34 35 u. Include for the CDMA non-MAHO case. 36 v. Include if an AMPS or NAMPS channel is in use. 37 w. Include if MS supports Signaling Message Encryption, Voice Privacy, Data Privacy, 38 39 or TDMA Enhanced Privacy and Encryption. This parameter shall be carried for- 40 ward in subsequent handoffs. 41 x. Include to indicate last known value of DP Data field. Do not include if contained in 42 CDMAConnectionReferenceList 43 y. Include if known. 44 45 z. Include if the call is in the awaiting answer or alerting state. 46 aa. Include if available. At least one of these parameters should be present. 47 48 ab. Include appropriate ISLP Information, if needed, for circuit-mode (e.g., ADS, G3 Fax) 49 services. If excluded for circuit mode data calls, interpret as ISLP supported. 50 ac. Include to indicate the acceptable call mode if other than AMPS (i.e., NAMPS). 51 ad. Include if an NAMPS channel is in use. 52 ae. Include to indicate information for the current band in use. 53 af. Include if a TDMA channel is in use. 54 ag. Include if the CDMA MS supports 800 MHz analog operation and the target system 55 does not support CDMA. 56 57 ah. Include if the MS is IS-136 or later and SOC-specific signaling is supported. 58 ai. Include if an AMPS, NAMPS or a TDMA handoff. 59 60 HandoffBack2 540 - 62 X.S0004-540-E v2.0

1 aj. Include to describe the requested TDMA traffic channel. If omitted for data calls, as- 2 sume to be Full-rate Digital Traffic Channel only. 3 ak. Include to indicate acceptable call modes. 4 al. Include if MS is TDMA IS-136 or later. 5 6 am. Include to indicate requested TDMA service information. 7 an. Include to indicate subscriber or network preferences for Voice Coder selection 8 when multiple voice coders exist. If not included, or if preferences can not be sup- 9 ported, the receiving system will select the Voice Coder based on the Mobile Sta- 10 tion’s terminal capabilities. 11 12 ao. Include for statistical purposes. 13 ap. This parameter shall be provided if the MS supports TDMA and is authorized to 14 have Voice Privacy and the VoicePrivacyMask (VPMASK) parameter is available. 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 540 - 63 HandoffBack2 X.S0004-540-E v2.0

The HandoffBack2 operation success is reported with a TCAP RETURN RESULT (LAST). This is 1 carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 2 3 4 HandoffBack2 RETURN RESULT Parameters 5 Field Value Type Reference Notes 6 7 Identifier SET [NATIONAL 18] M 520-1.3.2.2 8 9 Length variable octets M 520-1.3.2.2 10 Contents 11 12 BSMCStatus O 2.25 a 13 CDMA2000HandoffResponseIOSData O 2.40 b 14 15 CDMAChannelData (Target) O 2.46 c, d 16 CDMACodeChannelList O 2.51 c, e 17 18 CDMAConnectionReferenceList O 2.54 c, f, g 19 CDMASearchParameters O 2.63 c, h 20 21 CDMASearchWindow O 2.64 c, i 22 23 CDMAServiceConfigurationRecord O 2.65 c, j, k 24 ChannelData (Target) O 2.81 l, m 25 26 ConfidentialityModes (Actual) O 2.85 n 27 NAMPSChannelData (Target) O 2.157 o 28 29 SOCStatus O 2.262 a 30 TargetCellID O 2.263 p 31 32 TDMABurstIndicator (Target) O 2.268 a 33 TDMAChannelData (Target) O 2.270 q 34 35 TDMAVoiceCoder (Target) O 2.275 r 36 37 Notes: 38 a. May be included if target is a TDMA channel. 39 b. If the Serving MSC and the Target MSC support TIA/EIA/IS-2001-A (IOS v4.1) or 40 later, include to convey required cdma2000 IOS handoff response information (e.g. 41 IS-95 Channel Identity, IS-2000 Channel Identity, IS-2000 Service Configuration 42 Record, IS-2000 Non-Negotiable Service Configuration Record, Extended Handoff 43 Direction Parameters, Hard Handoff Parameters, [see IOS]). 44 45 c. Include if target is a CDMA channel. 46 d. Include only when IS-95 channels are to be used at the Target MSC. 47 Note: this does not preclude use at the CDMA2000HandoffResponseIOSData pa- 48 rameter to convey this same information. 49 50 e. For cdma2000 mobiles, the CDMACodeCHannelList is used for the Fundamental 51 Channel. 52 f. Include appropriate granted privacy parameters, if available and if allowed for the 53 user. 54 55 g. Include to indicate state information for the granted service option(s) connection ref- 56 erence. 57 58 59 60 HandoffBack2 540 - 64 X.S0004-540-E v2.0

1 h. Include for implementations without the CDMA2000HandoffResponseIOSData pa- 2 rameter. 3 4 i. Include when communicating with TIA/EIA-41-D or earlier system. (replaced 5 by CDMASearchParameters). 6 j. If the CDMAServiceConfigurationRecord was received in the INVOKE, include to 7 indicate a granted service configuration, other than the one agreed upon by the Serv- 8 ing and Target Systems. 9 10 k. Include if the Serving MSC, the Target MSC, or both support only an A-interface 11 prior to IOS v4.1. 12 l. Include if target is an AMPS or NAMPS channel. 13 m. For forced handoffs to an analog voice channel, include the VMAC value set to the 14 target system’s expected MS power level at handoff for the identified AMPS or 15 16 NAMPS Channel Number. 17 n. Include to reflect actual assignment if ConfidentialityModes (Desired) parameter 18 was present in the INVOKE. 19 o. Include if target is an NAMPS channel. 20 21 p. Include if the TargetCellID is different than that received in the INVOKE for an 22 AMPS, NAMPS, or a TDMA handoff. 23 q. Include if target is a TDMA channel. 24 25 r. Include to indicate the granted Voice Coder if applicable. If not included the MS 26 shall continue using the current Voice Coder. 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 540 - 65 HandoffBack2 X.S0004-540-E v2.0

2.24 HandoffMeasurementRequest 1 2 3 The HandoffMeasurementRequest (HANDMREQ) operation is sent by the Serving MSC to selected 4 adjacent MSCs to request a signal quality measurement on the specified channel. 5 6 The following table lists the valid combinations of invoking and responding FEs. 7 8 INVOKING FE RESPONDING FE 9 Case 1 Serving MSC Adjacent MSC 10 11 12 This request should result in a response with one or more candidate cells. 13 The HandoffMeasurementRequest operation is initiated with a TCAP INVOKE (LAST). This is 14 15 carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as 16 follows: 17 18 HandoffMeasurementRequest INVOKE Parameters Timer: LMMRT 19 20 Field Value Type Reference Notes 21 Identifier SET [NATIONAL 18] M 520-1.3.2.1 22 23 Length variable octets M 520-1.3.2.1 24 25 Contents 26 ChannelData (Serving) M 2.81 a 27 28 ServingCellID M 2.225 29 StationClassMark M 2.255 30 31 TDMACallMode O 2.269 b 32 TDMAChannelData (Serving) O 2.270 c 33 34 Notes: 35 36 a. This parameter has a length of 0 if a TDMA channel measurement is requested. 37 38 b. Include to indicate the current call modes. 39 40 c. Include if a TDMA channel measurement is requested. 41 42 The HandoffMeasurementRequest operation success is reported with a TCAP RETURN RESULT 43 (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 44 45 46 HandoffMeasurementRequest RETURN RESULT Parameters 47 48 Field Value Type Reference Notes 49 Identifier SET [NATIONAL 18] M 520-1.3.2.2 50 51 Length variable octets M 520-1.3.2.2 52 Contents 53 54 SignalQuality M 2.230 a 55 TargetCellID M 2.263 a 56 57 58 59 60 HandoffMeasurementRequest 540 - 66 X.S0004-540-E v2.0

1 Notes: 2 3 a. TargetCellID and SignalQuality parameters must appear in pairs. Multiple pairs may be 4 returned. 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 540 - 67 HandoffMeasurementRequest X.S0004-540-E v2.0

2.25 HandoffMeasurementRequest2 1 2 3 The HandoffMeasurementRequest2 (HANDMREQ2) operation is sent by the Serving MSC to 4 selected adjacent MSCs to request a signal quality measurement on the specified channel. This 5 operation differs from the HandoffMeasurementRequest operation in its addition of support for 6 CDMA, multi-band TDMA, and NAMPS MSs. 7 8 The following table lists the valid combinations of invoking and responding FEs. 9 10 INVOKING FE RESPONDING FE 11 Case 1 Serving MSC Adjacent MSC 12 13 14 The HandoffMeasurementRequest2 operation is initiated with a TCAP INVOKE (LAST). This is 15 carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as 16 follows: 17 18 HandoffMeasurementRequest2 INVOKE Timer: LMMRT 19 20 Field Value Type Reference Notes 21 22 Identifier SET [NATIONAL 18] M 520-1.3.2.1 23 Length variable octets M 520-1.3.2.1 24 25 Contents 26 ServingCellID M 2.225 27 28 CDMACallMode O 2.45 a, b 29 30 CDMAChannelData (Serving) O 2.46 b 31 CDMAServiceConfigurationRecord O 2.65 b 32 33 CDMAServingOneWayDelay O 2.68 b 34 CDMAStationClassMark O 2.72 k 35 36 CDMAStationClassMark2 O 2.73 l 37 ChannelData (Serving) O 2.81 c 38 39 MSLocation O 2.155 b 40 NAMPSCallMode O 2.156 d 41 42 NAMPSChannelData (Serving) O 2.157 e 43 StationClassMark O 2.255 c, f 44 45 TargetCellIDList O 2.264 j 46 47 TDMABandwidth (Desired) O 2.267 i 48 TDMACallMode O 2.269 g 49 50 TDMAChannelData (Serving) O 2.270 f 51 TDMAServiceCode O 2.273 h 52 53 Notes: 54 55 a. Include to indicate the current call mode if CDMA or NAMPS. 56 57 b. Include if a CDMA channel measurement is requested. 58 59 60 HandoffMeasurementRequest2 540 - 68 X.S0004-540-E v2.0

1 c. Include if an AMPS or NAMPS channel measurement is requested. 2 3 d. Include to indicate the current call mode if other than AMPS (i.e., NAMPS). 4 5 e. Include if an NAMPS channel measurement is requested. 6 7 f. Include to indicate the current call mode, if NAMPS. 8 g. Include to indicate the current call mode, if TDMA. 9 10 h. Include to indicate requested TDMA service information. 11 12 i. Include to describe the requested TDMA traffic channel. If omitted for data calls, assume 13 to be Full-rate Digital Traffic Channel only. 14 15 j. Include to indicate the list of cells and sectors on which measurements are required. The 16 inclusion of this parameter and the sending of the HandoffMeasurementRequest2 INVOKE 17 is based on service related statistics gathered by the Serving MSC regarding past handoff 18 performance with border cells and sectors in neighboring MSCs. See section 520, 19 Successful Handoff-Forward for MAHO with Measurement confirmation. 20 21 k. Include if an 800 MHz channel is in use for an IS-41-C system. 22 23 l. Include to indicate information for the current band in use. 24 25 The HandoffMeasurementRequest2 operation success is reported with a TCAP RETURN RESULT 26 27 (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 28 29 HandoffMeasurementRequest2 RETURN RESULT Parameters 30 31 Field Value Type Reference Notes 32 Identifier SET [NATIONAL 18] M 520-1.3.2.2 33 34 Length variable octets M 520-1.3.2.2 35 Contents 36 37 CDMATargetMeasurementList O 2.77 a 38 TargetMeasurementList O 2.266 b 39 40 41 Notes: 42 a. Include for CDMA measurement. 43 44 b. Include for AMPS, NAMPS, or TDMA measurement. 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 540 - 69 HandoffMeasurementRequest2 X.S0004-540-E v2.0

2.26 HandoffToThird 1 2 3 The HandoffToThird (HANDTHIRD) operation is used by the Serving MSC (non-Anchor) to 4 initiate a handoff with path minimization. 5 6 The following table lists the valid combinations of invoking and responding FEs. 7 8 INVOKING FE RESPONDING FE 9 Case 1 Serving MSC Anchor MSC 10 11 Case 2 Serving MSC Tandem MSC 12 Case 3 Tandem MSC Tandem MSC 13 14 15 The HandoffToThird operation is initiated with a TCAP INVOKE (LAST). This is carried by a 16 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 17 18 HandoffToThird INVOKE Parameters Timer: HTTT 19 20 Field Value Type Reference Notes 21 22 Identifier SET [NATIONAL 18] M 520-1.3.2.1 23 Length variable octets M 520-1.3.2.1 24 25 Contents 26 ElectronicSerialNumber M 2.112 27 28 InterMSCCircuitID M 2.129 29 InterSwitchCount (Serving) M 2.130 30 31 MobileIdentificationNumber M 2.140 32 MSCID (Target) M 2.151 33 34 ServingCellID M 2.225 35 36 StationClassMark M 2.255 37 TargetCellID M 2.263 38 39 BillingID O 2.23 a 40 ChannelData (Serving) O 2.81 b 41 42 ConfidentialityModes (Desired) O 2.85 c 43 HandoffReason O 2.125 d 44 45 SignalingMessageEncryptionKey O 2.228 c 46 TDMABurstIndicator (Serving) O 2.268 e 47 48 TDMACallMode O 2.269 f 49 TDMAChannelData (Serving) O 2.270 e 50 51 VoicePrivacyMask O 2.297 g 52 53 Notes: 54 55 a. Include to maintain segment count. 56 57 b. Include if the current call mode is AMPS. 58 59 60 HandoffToThird 540 - 70 X.S0004-540-E v2.0

1 c. Include if MS supports Signaling Message Encryption or Voice Privacy. The parameter 2 shall be carried forward in any subsequent handoff. If one parameter is present, they all 3 must be present. 4 5 d. Include if known. 6 7 e. Include if a TDMA channel is in use. 8 9 f. Include to indicate the acceptable call mode. 10 11 g. Include if Voice Privacy may apply. 12 13 The HandoffToThird operation success is reported with a TCAP RETURN RESULT (LAST). This 14 is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 15 16 17 HandoffToThird RETURN RESULT Parameters 18 Field Value Type Reference Notes 19 20 Identifier SET [NATIONAL 18] M 520-1.3.2.2 21 Length variable octets M 520-1.3.2.2 22 23 Contents 24 25 ChannelData (Target) O 2.81 a 26 ConfidentialityModes (Actual) O 2.85 b 27 28 TDMABurstIndicator (Target) O 2.268 c 29 TDMAChannelData (Target) O 2.270 d 30 31 Notes: 32 33 a. Include if an AMPS channel has been assigned. 34 35 b. Include to reflect actual assignment if the ConfidentialityModes parameter was present in 36 the INVOKE. 37 38 c. May be included if a TDMA channel has been assigned. 39 40 d. Include if a TDMA channel has been assigned. 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 540 - 71 HandoffToThird X.S0004-540-E v2.0

2.27 HandoffToThird2 1 2 3 The HandoffToThird2 (HANDTHIRD2) operation is used by the Serving MSC (non-Anchor) to 4 initiate a handoff with path minimization. This operation differs from the HandoffToThird operation 5 in its support of dual-mode CDMA, multi-band TDMA, and NAMPS MSs. 6 7 The following table lists the valid combinations of invoking and responding FEs. 8 9 INVOKING FE RESPONDING FE 10 Case 1 Serving MSC Anchor MSC 11 12 Case 2 Serving MSC Tandem MSC 13 Case 3 Tandem MSC Tandem MSC 14 15 16 The HandoffToThird2 operation is initiated with a TCAP INVOKE (LAST). This is carried by a 17 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 18 19 HandoffToThird2 INVOKE Parameters Timer: HTTT 20 21 Field Value Type Reference Notes 22 23 Identifier SET [NATIONAL 18] M 520-1.3.2.1 24 Length variable octets M 520-1.3.2.1 25 26 Contents 27 BillingID M 2.23 28 29 ElectronicSerialNumber M 2.112 30 InterMSCCircuitID M 2.129 31 32 InterSwitchCount (Serving) M 2.130 33 34 MSCID (Target) M 2.151 35 ServingCellID M 2.225 a 36 37 BaseStationManufacturerCode O 2.21 b 38 CaveKey O 2.38 c 39 40 CDMA2000HandoffInvokeIOSData O 2.39 d 41 CDMABandClassList O 2.44 e 42 43 CDMACallMode O 2.45 f, g 44 CDMAChannelData (Serving) O 2.46 f, h, i 45 46 CDMAConnectionReferenceList O 2.54 f, j 47 CDMAMobileProtocolRevision O 2.55 f, k 48 49 CDMAMSMeasuredChannelIdentity O 2.56 l 50 51 CDMAPrivateLongCodeMask O 2.61 m 52 CDMAServiceConfigurationRecord O 2.65 f, n, o 53 54 CDMAServiceOptionList O 2.67 f, p 55 CDMAServingOneWayDelay O 2.68 a, f 56 57 CDMAStationClassMark O 2.72 f, k, q, r 58 59 60 HandoffToThird2 540 - 72 X.S0004-540-E v2.0

1 CDMAStationClassMark2 O 2.73 f, k 2 3 CDMATargetMAHOList O 2.75 s 4 CDMATargetMeasurementList O 2.77 t 5 6 ChannelData (Serving) O 2.81 u 7 8 ConfidentialityModes (Desired) O 2.85 v 9 DataKey O 2.93 w 10 11 DataPrivacyParameters O 2.94 x 12 HandoffReason O 2.125 y 13 14 HandoffState O 2.126 z 15 IMSI O 2.127 aa 16 17 ISLPInformation O 2.132 ab 18 MobileIdentificationNumber O 2.140 aa 19 20 MSLocation O 2.155 f 21 NAMPSCallMode O 2.156 g, ac 22 23 NAMPSChannelData (Serving) O 2.157 ad 24 25 RandomVariable O 2.189 w 26 SignalingMessageEncryptionKey O 2.228 v 27 28 SpecialHandling O 2.249 ae 29 StationClassMark O 2.255 u, ak, af 30 31 SystemOperatorCode O 2.261 ag 32 TargetCellID O 2.263 ah 33 34 TDMABandwidth (Desired) O 2.267 ai 35 TDMABurstIndicator (Serving) O 2.268 ak 36 37 TDMACallMode O 2.269 g, aj, ak 38 TDMAChannelData (Serving) O 2.270 ak 39 40 TDMAServiceCode O 2.273 al, am 41 42 TDMATerminalCapability O 2.274 al 43 TDMAVoiceCoder O 2.275 an 44 45 TerminalType O 2.278 ao 46 UserZoneData O 2.294 ap 47 48 VoicePrivacyMask O 2.297 aq 49 50 Notes: 51 a. For CDMA, the ServingCellID and CDMAServingOneWayDelay parameters cor- 52 respond to the active set member having the shortest signal path to the MS (time ref- 53 erence cell). 54 b. Include if the MS is IS-136 or later and BSMC-specific signaling is supported. 55 56 c. Include if available and TDMA Enhanced Privacy and Encryption apply. This pa- 57 rameter shall be carried forward in subsequent handoffs. 58 59 60 540 - 73 HandoffToThird2 X.S0004-540-E v2.0

d. If the Serving MSC and the Target MSC support TIA/EIA/IS-2001-A (IOS v4.1) or 1 later, include to convey required cdma2000 handoff invoke information (e.g., 2 IS-2000 Channel Identity, IS-2000 Mobile Capabilities, IS-2000 Service Configura- 3 tion Record, [see IOS]). 4 5 e. Include to indicate band classes and band subclasses supported by the MS. 6 f. Include if CDMA handoff. 7 8 g. The values in these parameters shall not contain conflicting information. 9 h. The Long Code Mask field should be set to the long code mask in use at the Serving 10 MSC. 11 i. Include only when IS-95 channels are in use at the Serving MSC. 12 Note: use at the CDMA2000HandoffInvokeIOSData parameter to convey this infor- 13 14 mation is required for CDMA2000 and later channels. 15 j. Include to indicate state information for the requested service option(s) connection 16 reference. 17 k. Include to indicate information for the current band in use. 18 19 l. Include to indicate the band class and frequency that has been measured by the MS 20 in preparation for hard handoff. 21 m. This parameter shall be provided if the MS supports CDMA and is authorized to 22 have Voice Privacy and the CDMAPrivateLongCodeMask parameter is available. 23 24 n. Include to indicate a requested service configuration other than the one agreed upon 25 by the Serving and Target Systems. 26 o. Include if the Serving MSC, the Target MSC, or both support only an A-interface 27 prior to IOS v4.1. 28 29 p. Include to indicate the authorized service options. 30 q. Include if an 800 MHz CDMA channel is in use for an IS-41-C system. 31 r. Ignore on reception if the CDMAStationClassMark2 parameter is also received and 32 recognized. 33 34 s. Include for either the CDMA MAHO case or the forced handoff case. 35 t. Include for the CDMA non-MAHO case. 36 u. Include if an AMPS or NAMPS channel is in use. 37 38 v. Include if MS supports Signaling Message Encryption, Voice Privacy, Data Privacy, 39 or TDMA Enhanced Privacy and Encryption. This parameter shall be carried for- 40 ward in subsequent handoffs. 41 w. Include for CDMA data privacy, if applicable and if authorized for the user. 42 43 x. Include to indicate last known value of DP Data filed. Do not include if contained in 44 CDMAConnectionReferenceList. 45 y. Include if known. 46 47 z. Include if the call is in the awaiting answer or alerting state. 48 aa. Include if available. At least one of these parameters should be present. 49 ab. Include appropriate ISLP Information, if needed, for circuit-mode (e.g., ADS, G3 50 Fax) services. If excluded for circuit mode data calls, interpret as ISLP supported. 51 52 ac. Include to indicate the current call mode if other than AMPS (i.e., NAMPS). 53 ad. Include if an NAMPS channel is in use. 54 ae. Include if any fields in this parameter are non-zero. 55 56 af. Include if the CDMA MS supports 800 MHz analog operation and the target system 57 does not support CDMA. 58 59 60 HandoffToThird2 540 - 74 X.S0004-540-E v2.0

1 ag. Include if the MS is IS-136 or later and SOC-specific signaling is supported. 2 ah. Include if an AMPS, NAMPS or a TDMA handoff. 3 4 ai. Include to describe the requested TDMA traffic channel. If omitted for data calls, 5 assume to be Full-rate Digital Traffic Channel only. 6 aj. Include to indicate the acceptable call mode. 7 8 ak. Include if TDMA channel is in use. 9 al. Include if MS is TDMA IS-136 or later. 10 am. Include to indicate requested TDMA service information. 11 12 an. Include to indicate subscriber or network preferences for Voice Coder selection 13 when multiple voice coders exist. If not included, or if preferences can not be sup- 14 ported, the receiving system will select a Voice Coder based on Terminal Capability. 15 ao. Include for statistical purposes. 16 17 ap. Include if the MS is authorized for User Zone Service. Include to permit the Target 18 MSC to validate MS selection of User Zone. 19 aq. This parameter shall be provided if the MS supports TDMA and is authorized to 20 have Voice Privacy and the VoicePrivacyMask (VPMASK) parameter is available. 21 22 23 24 25 The HandoffToThird2 operation success is reported with a TCAP RETURN RESULT (LAST). This 26 is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 27 28 HandoffToThird2 RETURN RESULT Parameters 29 30 Field Value Type Reference Notes 31 32 Identifier SET [NATIONAL 18] M 520-1.3.2.2 33 Length variable octets M 520-1.3.2.2 34 35 Contents 36 BSMCStatus O 2.25 a 37 38 CDMA2000HandoffResponseIOSData O 2.40 b 39 40 CDMAChannelData (Target) O 2.46 c, r 41 CDMACodeChannelList O 2.51 c, d 42 43 CDMAConnectionReferenceList O 2.54 c, e, f 44 CDMASearchParameters O 2.63 c, g 45 46 CDMASearchWindow O 2.64 c, h 47 CDMAServiceConfigurationRecord O 2.65 c, i, j 48 49 ChannelData (Target) O 2.81 k, l 50 ConfidentialityModes (Actual) O 2.85 m 51 52 NAMPSChannelData (Target) O 2.157 n 53 SOCStatus O 2.262 a 54 55 TargetCellID O 2.263 o 56 57 58 59 60 540 - 75 HandoffToThird2 X.S0004-540-E v2.0

1 TDMABurstIndicator (Target) O 2.268 a 2 TDMAChannelData (Target) O 2.270 p 3 4 TDMAVoiceCoder (Target) O 2.275 q 5 Notes: 6 a. May be included if target is a TDMA channel. 7 8 b. If the Serving MSC and the Target MSC support TIA/EIA/IS-2001-A (IOS v4.1) or 9 later, include to convey required cdma2000 IOS handoff response information (e.g., 10 IS-2000 Channel Identity, IS-2000 Service Configuration Record, IS-2000 Non-Ne- 11 gotiable Service Configuration Record, Extended Handoff Direction Parameters, 12 Hard Handoff Parameters, [see IOS]). 13 14 c. Include if target is a CDMA channel. 15 d. For cdma2000 mobiles, the CDMACodeChannelList is used for the Fundamental 16 Channel. 17 e. Include to indicate state information for the granted service option(s) connection ref- 18 erence. 19 20 f. Include appropriate requested privacy parameters, if available and if allowed for the 21 user. 22 g. Include for implementations without the CDMA2000HandoffResponseIOSData pa- 23 rameter. 24 25 h. Include when communicating with TIA-41-D or earlier system. (replaced 26 by CDMASearchParameters). 27 i. Include to indicate a granted service configuration, other than the one agreed upon 28 by the Serving and Target Systems. 29 30 j. Include if the serving MSC, the Target MSC, or both support only an A-Interface 31 prior to IOS version 4.1. 32 k. Include if target is an AMPS or NAMPS channel. 33 l. For forced handoffs to an analog voice channel, include the VMAC value set to the 34 35 target system’s expected MS power level at handoff for the identified AMPS or 36 NAMPS Channel Number. 37 m. Include to reflect actual assignment if ConfidentialityModes (Desired) parameter 38 was present in the INVOKE. 39 n. Include if target is an NAMPS channel. 40 41 o. Include for an AMPS, NAMPS, or a TDMA handoff. 42 p. Include if target is a TDMA channel. 43 44 q. Include to indicate the granted Voice Coder if applicable. If not included the MS 45 shall continue using the current Voice Coder. 46 r. Include only when IS-95 channels are to be used at the Target MSC. 47 Note: this does not preclude use at the CDMA2000HandoffResponseIOSData pa- 48 rameter to convey this same information. 49 50 51 52 53 54 55 56 57 58 59 60 HandoffToThird2 540 - 76 X.S0004-540-E v2.0

1 2.28 InformationDirective 2 3 4 The InformationDirective (INFODIR) operation is used by the HLR to direct the serving system to 5 provide a specified notification to an idle MS. 6 7 The following table lists the valid combinations of invoking and responding FEs. 8 9 INVOKING FE RESPONDING FE 10 Case 1 HLR Serving VLR 11 12 Case 2 Serving VLR Serving MSC 13 14 The InformationDirective is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 15 QUERY WITH PERMITION package. The Parameter Set is encoded as follows: 16 17 18 InformationDirective INVOKE Parameters Timer: IDT 19 20 Field Value Type Reference Notes 21 Identifier SET [NATIONAL 18] M 520-1.3.2.1 22 23 Length variable octets M 520-1.3.2.1 24 Contents 25 26 ElectronicSerialNumber M 2.112 27 MSID M 2.153 e 28 29 AlertCode O 2.4 a 30 AnnouncementList O 2.10 b 31 32 CallingPartyNumberString1 O 2.32 c 33 34 CallingPartyNumberString2 O 2.33 c 35 CallingPartySubaddress O 2.34 c 36 37 DisplayText O 2.106 c, f 38 DisplayText2 O 2.107 c, f 39 40 RedirectingNumberString O 2.199 c 41 RedirectingSubaddress O 2.201 c 42 43 SenderIdentificationNumber O 2.215 d 44 45 Notes: 46 47 a. Include if MS is to be alerted. 48 49 b. Include if one or more tones or announcements are to be applied to the MS. 50 c. Include if authorized and available. 51 52 d. May be included to identify the functional entity sending the message. 53 54 e. The HLR includes the IMSI type of MSID if the IMSI was present in the last message 55 received from the Serving System; otherwise the HLR includes the 56 MobileIdentificationNumber type of MSID. The VLR includes the type of MSID last 57 received from the Serving MSC; this may not be the type of MSID received from the HLR. 58 59 60 540 - 77 InformationDirective X.S0004-540-E v2.0

f. Include only one of these mutually exclusive parameters. 1 2 The InformationDirective operation success is reported with a TCAP RETURN RESULT (LAST). 3 This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 4 5 6 InformationDirective RETURN RESULT Parameters 7 Field Value Type Reference Notes 8 9 Identifier SET [NATIONAL 18] M 520-1.3.2.1 10 11 Length variable octets M 520-1.3.2.1 12 Contents 13 14 AlertResult O 2.5 a 15 16 Notes: 17 18 a. Include if requested via AlertCode parameter in the InformationDirective INVOKE. 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 InformationDirective 540 - 78 X.S0004-540-E v2.0

1 2.29 InformationForward 2 3 4 The InformationForward (INFOFWD) operation is used by the Anchor MSC to transfer information 5 concerning the Served MS to the Serving MSC after handoff (e.g., a message waiting status change). 6 7 The following table lists the valid combinations of invoking and responding FEs. 8 9 INVOKING FE RESPONDING FE 10 Case 1 Anchor MSC Serving MSC 11 12 Case 2 Anchor MSC Tandem MSC 13 Case 3 Tandem MSC Serving MSC 14 15 16 The InformationForward operation is initiated with a TCAP INVOKE (LAST). This is carried by a 17 TCAP QUERY WITH PERMITION package. The Parameter Set is encoded as follows: 18 19 InformationForward INVOKE Parameters Timer: IFT 20 21 Field Value Type Reference Notes 22 23 Identifier SET [NATIONAL 18] M 520-1.3.2.1 24 Length variable octets M 520-1.3.2.1 25 26 Contents 27 InterMSCCIrcuitID M 2.129 28 29 MobileIdentificationNumber O 2.140 e 30 AlertCode O 2.4 a 31 32 AnnouncementList O 2.10 a 33 34 CallingPartyNumberString1 O 2.32 b 35 CallingPartyNumberString2 O 2.33 b 36 37 CallingPartySubaddress O 2.34 b 38 DisplayText O 2.106 c, d 39 40 DisplayText2 O 2.107 c, d 41 ElectronicSerialNumber O 2.112 a 42 43 IMSI O 2.127 e 44 MessageWaitingNotificationCount O 2.136 a 45 46 MessageWaitingNotificationType O 2.137 a 47 RedirectingNumberString O 2.199 b 48 49 RedirectingSubaddress O 2.201 b 50 51 Notes: 52 53 a. Include if appropriate. 54 b. Include if MS is authorized for CNIP. 55 56 c. Include if available. 57 d. Include only one of these mutually exclusive parameters. 58 59 e. Include if available. At least one of these parameters should be present. 60 540 - 79 InformationForward X.S0004-540-E v2.0

The InformationForward operation success is reported with a TCAP RETURN RESULT (LAST). 1 This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 2 3 4 InformationForward RETURN RESULT Parameters 5 6 Field Value Type Reference Notes 7 Identifier SET [NATIONAL 18] M 520-1.3.2.1 8 9 Length variable octets M 520-1.3.2.1 10 Contents 11 12 AlertResult O 2.5 a 13 14 Notes: 15 16 a. Include if requested via AlertCode parameter in the corresponding INVOKE. 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 InformationForward 540 - 80 X.S0004-540-E v2.0

1 2.30 InstructionRequest 2 3 4 The InstructionRequest (INSTREQ) operation is used by the SRF to obtain instructions from the 5 SCF for the particular resource seized. This operation is used when the SRF determines that one of 6 its resources, allocated by a SeizeResource operation, has been seized through the establishment of 7 a connection from the SSF. 8 9 The following table lists the valid combinations of invoking and responding FEs. 10 11 INVOKING FE RESPONDING FE 12 Case 1 IP SCP or SN or HLR 13 14 Case 2 SN SCP or SN or HLR 15 16 The InstructionRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a 17 TCAP CONVERSATION WITH PERMISSION package. The Parameter Set is encoded as follows: 18 19 InstructionRequest INVOKE Parameters Timer: IRT 20 (note a) 21 22 Field Value Type Reference Notes 23 24 Identifier SET [NATIONAL 18] M 520-1.3.2.1 25 Length zero octets M 520-1.3.2.1 26 27 Contents 28 29 30 Notes: 31 32 a. The Instruction Request Timer (IRT) is started when an InstructionRequest INVOKE is 33 sent and stopped when an SRFDirective INVOKE or an InstructionRequest RETURN 34 RESULT is received by the SRF. 35 36 37 The InstructionRequest operation success is reported with a TCAP RETURN RESULT (LAST). 38 This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 39 40 InstructionRequest RETURN RESULT Parameters 41 42 Field Value Type Reference Notes 43 44 Identifier SET [NATIONAL 18] M 520-1.3.2.2 45 Length zero octets M 520-1.3.2.2 46 47 Contents 48 49 50 51 52 53 54 55 56 57 58 59 60 540 - 81 InstructionRequest X.S0004-540-E v2.0

2.31 InterSystemAnswer 1 2 3 The InterSystemAnswer (ISANSWER) operation can be used in two types of scenarios: 4 5 • It is used by a Border MSC to notify the Serving MSC that an MS has successfully answered an 6 alert in the Border MSC. 7 • It is used by either an Anchor MSC or a Serving MSC after handoff has occurred to indicate that 8 9 a call in the awaiting answer or alerting state has been answered. 10 The following table lists the valid combinations of invoking and responding FEs. 11 12 13 INVOKING FE RESPONDING FE 14 Case 1 Anchor MSC Serving MSC 15 16 Case 2 Serving MSC Anchor MSC 17 18 The InterSystemAnswer operation is initiated with a TCAP INVOKE (LAST). This is carried by a 19 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 20 21 22 InterSystemAnswer INVOKE Parameters Timer: ISAT 23 Field Value Type Reference Notes 24 25 Identifier SET [NATIONAL 18] M 520-1.3.2.1 26 27 Length variable octets M 520-1.3.2.1 28 Contents 29 30 InterMSCCircuitID M 2.129 31 ElectronicSerialNumber O 2.112 a 32 33 IMSI O 2.127 b 34 MobileIdentificationNumber O 2.140 b 35 36 Notes: 37 38 a. Include if appropriate. 39 40 b. Include if available. At least one of these parameters should be present. 41 42 43 The InterSystemAnswer operation success is reported with a TCAP RETURN RESULT (LAST). 44 This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 45 46 InterSystemAnswer RETURN RESULT Parameters 47 48 Field Value Type Reference Notes 49 50 Identifier SET [NATIONAL 18] M 520-1.3.2.2 51 Length zero octets M 520-1.3.2.2 52 53 Contents 54 55 56 57 58 59 60 InterSystemAnswer 540 - 82 X.S0004-540-E v2.0

1 2.32 InterSystemPage 2 3 4 The InterSystemPage (ISPAGE) operation is used by a Serving MSC to request a Border MSC to 5 either (a) page an MS, or (b) listen for a page response from an MS, in the Border MSC prior to Call 6 Delivery. If the MS’s presence is confirmed on the Border MSC, the MS should be registered in the 7 Border MSC and the call is delivered directly to the Border MSC. 8 9 The following table lists the valid combinations of invoking and responding FEs. 10 11 INVOKING FE RESPONDING FE 12 13 Case 1 Serving MSC Border MSC 14 15 The InterSystemPage operation is initiated with a TCAP INVOKE (LAST). This is carried by a 16 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 17 18 19 InterSystemPage INVOKE Parameters Timer: ISPRT 20 Field Value Type Reference Notes 21 22 Identifier SET [NATIONAL 18] M 520-1.3.2.1 23 24 Length variable octets M 520-1.3.2.1 25 Contents 26 27 BillingID (Originating) M 2.23 28 ElectronicSerialNumber M 2.112 29 30 AlertCode O 2.4 a 31 CallingPartyName O 2.29 a 32 33 CallingPartyNumberDigits1 O 2.30 a 34 CallingPartyNumberDigits2 O 2.31 a 35 36 CallingPartyNumberString1 O 2.32 a 37 38 CallingPartyNumberString2 O 2.33 a 39 CallingPartySubaddress O 2.34 a 40 41 CDMA2000MobileSupportedCapabilities O 2.41 q 42 CDMABandClass O 2.42 x 43 44 CDMABandClassList O 2.44 ab 45 CDMAMobileProtocolRevision O 2.55 c 46 47 CDMAServiceOption O 2.66 m 48 CDMAServiceOptionList O 2.67 o 49 50 CDMASlotCycleIndex O 2.70 b 51 CDMAStationClassMark O 2.72 x, y 52 53 CDMAStationClassMark2 O 2.73 x 54 55 ControlChannelMode O 2.87 v 56 DMH_AccountCodeDigits O 2.108 a 57 58 DMH_AlternateBillingDigits O 2.109 a 59 60 540 - 83 InterSystemPage X.S0004-540-E v2.0

1 DMH_BillingDigits O 2.110 a 2 DisplayText O 2.106 a, r 3 4 DisplayText2 O 2.107 a, r 5 ExtendedMSCID (Serving MSC) O 2.116 d 6 7 ExtendedSystemMyTypeCode (Serving MSC) O 2.117 e 8 IMSI O 2.127 s 9 10 LegInformation O 2.133 f 11 LocationAreaID O 2.135 f 12 13 MINExtension O 2.138 f 14 MobileDirectoryNumber O 2.139 a 15 16 MobileIdentificationNumber O 2.140 s 17 18 MSCIdentificationNumber (Originating MSC) O 2.152 z 19 MSCID (Originating MSC) O 2.151 g 20 21 MSIDUsage O 2.154 t 22 NoAnswerTime O 2.165 a 23 24 NetworkTMSI O 2.158 s 25 OneTimeFeatureIndicator O 2.167 f 26 27 PageCount O 2.172 aa 28 PageIndicator O 2.173 h 29 30 PageResponseTime O 2.174 u 31 PagingFrameClass O 2.175 w 32 33 PC_SSN (Originating MSC) O 2.176 i 34 35 PilotBillingID O 2.177 j 36 PilotNumber O 2.178 k 37 38 PreferredLanguageIndicator O 2.179 a 39 RedirectingNumberDigits O 2.198 a 40 41 RedirectingNumberString O 2.199 a 42 RedirectingPartyName O 2.200 a 43 44 RedirectingSubaddress O 2.201 a 45 SenderIdentificationNumber (Serving MSC) O 2.215 d 46 47 SystemMyTypeCode (Originating MSC) O 2.260 l 48 TDMADataFeaturesIndicator O 2.271 p 49 50 TDMAServiceCode O 2.273 n 51 52 TerminalType O 2.278 f 53 TerminationTreatment O 2.282 f 54 55 TerminationTriggers O 2.283 a 56 TriggerAddressList O 2.286 a 57 58 59 60 InterSystemPage 540 - 84 X.S0004-540-E v2.0

1 Notes: 2 3 a. Include if available (i.e., provided in the associated RoutingRequest INVOKE). 4 5 b. Included when the Serving MSC knows that the MS is operating in CDMA Slotted Mode. 6 c. Include if a CDMA channel is in use. 7 8 d. Include to identify the Serving MSC. 9 10 e. Include to identify Serving MSC manufacturer. 11 f. Include if known. 12 13 g. Include to identify originating system. 14 15 h. Include if request is to listen only. May include if request is to page. 16 17 i. Include if available for subsequent call redirection. 18 j. Include if appropriate. 19 20 k. Include on a multi-leg call. 21 22 l. Include to identify originating system manufacturer. 23 24 m. Include to specify requested CDMA service information 25 n. Include to specify requested TDMA service information 26 27 o. Include to indicate preferred CDMA service options in descending order of preference 28 29 p. Include to indicate allowed TDMA data services. 30 q. Include for cdma2000 MSs or later. 31 32 r. Include only one of these mutually exclusive parameters. 33 34 s. Include if available. At least one parameter should be present. 35 36 t. For TDMA, identifies the MSID last used to calculate the control channel and paging slot. 37 u. Include to indicate the maximum time that the receiving system has to respond to this 38 message. 39 40 v. Include if the MS is Digital Control Channel capable, to indicate the last known access 41 mode. 42 43 w. Include if the MS is Digital Control Channel capable, to indicate the current Paging Frame 44 Class for the Mobile Station. 45 46 x. Include to indicate information about the current band in use. 47 48 y. Include if an 800 MHz CDMA channel is in use for an IS-41-C system. 49 z. Include to identify the originating MSC and to indicate that the MSC is capable of 50 accepting digits in the international format. 51 52 aa. Include to indicate the recommended number of sequential paging attempts that the 53 receiving system is expected to do. 54 55 ab. Include to indicate other CDMA band classes supported. 56 57 58 59 60 540 - 85 InterSystemPage X.S0004-540-E v2.0

The InterSystemPage operation success is reported with a TCAP RETURN RESULT (LAST). This 1 is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 2 3 4 InterSystemPage RETURN RESULT Parameters 5 Field Value Type Reference Notes 6 7 Identifier SET [NATIONAL 18] M 520-1.3.2.2 8 9 Length variable octets M 520-1.3.2.2 10 Contents 11 12 AccessDeniedReason O 2.1 a 13 BillingID (Terminating) O 2.23 b, d 14 15 CDMAServiceOption O 2.66 g 16 ConditionallyDeniedReason O 2.83 c 17 18 Digits (Destination) O 2.105 d 19 ExtendedMSCID (Border MSC) O 2.116 d 20 21 ExtendedSystemMyTypeCode (Border MSC) O 2.117 d 22 23 MSCIdentificationNumber O 2.152 e 24 PC_SSN (Border MSC) O 2.176 f 25 26 TDMAServiceCode O 2.273 h 27 28 Notes: 29 30 a. Include if access may be denied. 31 b. Required for recording purposes (see DMH). 32 33 c. Include if Call Waiting is possible. 34 35 d. If one parameter is present, they all must be present. 36 37 e. Include to identify the Border MSC. 38 39 f. Include if Digits (Destination) parameter is provided, SS7 is used, and the Originating MSC 40 and the Border MSC may be in the same national SS7 network. 41 42 g. Include to identify accepted CDMA service information. 43 h. Include to identify accepted TDMA service information. 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 InterSystemPage 540 - 86 X.S0004-540-E v2.0

1 2.33 InterSystemPage2 2 3 4 The InterSystemPage2 (ISPAGE2) operation is used by a Serving MSC that has received a call via 5 a TLDN to request a Border MSC to either (a) page an MS, or (b) listen for a page response from an 6 MS, in the Border MSC. If an MS’s presence is confirmed in the Border MSC, the call is terminated 7 to the Border MSC via intersystem trunk facilities. 8 9 The following table lists the valid combinations of invoking and responding FEs. 10 11 INVOKING FE RESPONDING FE 12 Case 1 Serving MSC Border MSC 13 14 15 The InterSystemPage2 operation is initiated with a TCAP INVOKE (LAST). This is carried by a 16 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 17 18 InterSystemPage2 INVOKE Parameters Timer: ISPRT 19 20 Field Value Type Reference Notes 21 Identifier SET [NATIONAL 18] M 520-1.3.2.1 22 23 Length variable octets M 520-1.3.2.1 24 Contents 25 26 BillingID (Anchor MSC) M 2.23 27 28 ElectronicSerialNumber M 2.112 29 AlertCode O 2.4 a 30 31 CallingPartyNumberString1 O 2.32 a 32 CallingPartyNumberString2 O 2.33 a 33 34 CallingPartySubaddress O 2.34 a 35 CDMA2000MobileSupportedCapabilities O 2.41 j 36 37 CDMABandClass O 2.42 u 38 CDMABandClassList O 2.44 w 39 40 CDMAMobileProtocolRevision O 2.55 c 41 CDMAServiceOption O 2.66 f 42 43 CDMAServiceOptionList O 2.67 h 44 45 CDMASlotCycleIndex O 2.70 b 46 CDMAStationClassMark O 2.72 u, v 47 48 CDMAStationClassMark2 O 2.73 u 49 ControlChannelMode O 2.87 s 50 51 DisplayText O 2.106 a, x 52 DisplayText2 O 2.107 a, x 53 54 IMSI O 2.127 k 55 LocationAreaID O 2.135 d 56 57 MINExtension O 2.138 d 58 MobileDirectoryNumber O 2.139 a 59 60 540 - 87 InterSystemPage2 X.S0004-540-E v2.0

1 MobileIdentificationNumber O 2.140 k 2 MSIDUsage O 2.154 l 3 4 NetworkTMSI O 2.158 k 5 NonPublicData O 2.166 m 6 7 PageCount O 2.172 n 8 PageIndicator O 2.173 e 9 10 PageResponseTime O 2.174 o 11 PagingFrameClass O 2.175 t 12 13 PSID_RSIDList O 2.184 p, q 14 RedirectingNumberString O 2.199 a 15 16 RedirectingSubaddress O 2.201 a 17 18 TerminalType O 2.278 d 19 TDMADataFeaturesIndicator O 2.271 i 20 21 TDMAServiceCode O 2.273 g 22 UserZoneData O 2.294 q, r 23 24 Notes: 25 26 a. Include if available (i.e., provided in associated RoutingRequest INVOKE). 27 28 b. Included when the Serving MSC knows that the MS is operating in CDMA Slotted Mode. 29 30 c. Include if a CDMA channel is in use. 31 d. Include if known. 32 33 e. Include if request is to listen only. May include if request is to page. 34 35 f. Include to specify requested CDMA service information. 36 37 g. Include to specify requested TDMA service information. 38 39 h. Include to indicate the authorized service options for the MS that are also supported by the 40 sending network entity. 41 42 i. Include to indicate allowed TDMA data services. 43 j. Include for cdma2000 MSs or later. 44 45 k. Include if available. At least one parameter should be present. 46 47 l. For TDMA, identifies the MSID last used to calculate the control channel and paging slot. 48 49 m. Include to provide information regarding Non-Public Information Display (e.g., User Zone 50 updates) in the border system. 51 52 n. Include to indicate the recommended number of sequential paging attempts that the 53 receiving system is expected to do. 54 55 o. Include to indicate the maximum time that the receiving system has to respond to this 56 message. 57 58 p. For TDMA, include to indicate the list of accepted PSIDs/RSIDs for the indicated MS. 59 60 InterSystemPage2 540 - 88 X.S0004-540-E v2.0

1 q. The PSID_RSIDList and UserZoneData parameters are mutually exclusive. 2 3 r. Include to perform User Zone updates at the Border System. 4 5 s. Include if the MS is Digital Control Channel capable to indicate the last known access 6 mode. 7 8 t. Include if the MS is Digital Control Channel capable to indicate the current Paging Frame 9 Class for the Mobile Station. 10 11 u. Include to indicate information about the last reported band class and band subclass (if 12 applicable) in use. When multiple band classes or multiple band subclasses apply due to 13 overlapping spectrum definitions, the included band class and band subclass (if applicable) 14 is based on value reported by the RAN. 15 16 v. Include if an 800 MHz CDMA channel is in use for an IS-41-C or TIA/EIA-41-D system. 17 w. Include to indicate the band classes and band subclasses supported by the MS. 18 19 x. Include only one of these mutually exclusive parameters. 20 21 22 The InterSystemPage2 operation success is reported with a TCAP RETURN RESULT (LAST). This 23 is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 24 25 26 InterSystemPage2 RETURN RESULT Parameters 27 Field Value Type Reference Notes 28 29 Identifier SET [NATIONAL 18] M 520-1.3.2.2 30 31 Length variable octets M 520-1.3.2.2 32 Contents 33 34 AccessDeniedReason O 2.1 a 35 AuthenticationResponse O 2.14 b 36 37 CallHistoryCount O 2.26 b 38 CDMAServiceOption O 2.66 d 39 40 RANDC O 2.188 h 41 RandomVariable O 2.189 c 42 43 SystemAccessType O 2.258 b 44 SystemCapabilities (Border MSC) O 2.259 g 45 46 TDMADataMode O 2.272 e 47 48 TDMAServiceCode O 2.273 f 49 TerminalType O 2.278 g 50 51 Notes: 52 53 a. Include if MS is not available or if access may be denied. 54 55 b. Include if authentication parameters were received from the MS. 56 57 c. Include if authentication parameters were received from the MS and the value of RAND 58 used by the MS to compute AUTHR was determined. 59 60 540 - 89 InterSystemPage2 X.S0004-540-E v2.0

d. Include to identify accepted CDMA service information. 1 2 e. Include TDMA data services. 3 4 f. Include to identify accepted TDMA service information. 5 6 g. Included for IS-778 or later. 7 h. Include if authentication parameters were received from the MS and the value of RAND 8 9 used by the MS to compute AUTHR cannot be determined. 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 InterSystemPage2 540 - 90 X.S0004-540-E v2.0

1 2.34 InterSystemSetup 2 3 4 The InterSystemSetup (ISSETUP) operation is used by a Serving MSC to request a Border MSC to 5 perform call setup actions; i.e., connect the voice channel in which the MS confirmation has been 6 received to the intersystem trunk facility specified by the Serving MSC. 7 8 The following table lists the valid combinations of invoking and responding FEs. 9 10 INVOKING FE RESPONDING FE 11 Case 1 Serving MSC Border MSC 12 13 14 The InterSystemSetup operation is initiated with a TCAP INVOKE (LAST). This is carried by a 15 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 16 17 InterSystemSetup INVOKE Parameters Timer: ISSRT 18 19 Field Value Type Reference Notes 20 21 Identifier SET [NATIONAL 18] M 520-1.3.2.1 22 Length variable octets M 520-1.3.2.1 23 24 Contents 25 BillingID (Anchor MSC) M 2.23 26 27 ElectronicSerialNumber M 2.112 28 InterMSCCircuitID M 2.129 29 30 CaveKey O 2.38 a, b 31 32 CDMAPrivateLongCodeMask O 2.61 a 33 ChangeServiceAttributes O 2.80 d 34 35 DataKey O 2.93 e 36 DisplayText O 2.106 a, g 37 38 DisplayText2 O 2.107 a, g 39 IMSI O 2.127 c 40 41 ISLPInformation (Desired) O 2.132 f 42 MobileIdentificationNumber O 2.140 c 43 44 SignalingMessageEncryptionKey O 2.228 a 45 VoicePrivacyMask O 2.297 a 46 47 48 Notes: 49 a. Include if available. 50 51 b. Include for TDMA Enhanced Privacy and Encryption. 52 53 c. Include if available. At least one parameter should be present. 54 55 d. Include to indicate whether or not a Service Negotiation operation is required. 56 57 e. Include if available and CDMA data privacy is authorized for the user. 58 59 60 540 - 91 InterSystemSetup X.S0004-540-E v2.0

f. Include appropriate ISLP Information, if needed, for circuit-mode (e.g., ADS, G3 Fax) 1 services. If excluded for circuit mode data calls, interpret as ISLP supported. 2 3 g. Include only one of these mutually exclusive parameters. 4 5 6 The InterSystemSetup operation success is reported with a TCAP RETURN RESULT (LAST). This 7 is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 8 9 InterSystemSetup RETURN RESULT Parameters 10 11 Field Value Type Reference Notes 12 Identifier SET [NATIONAL 18] M 520-1.3.2.2 13 14 Length variable octets M 520-1.3.2.2 15 Contents 16 17 CDMAServiceOption O 2.66 a 18 19 SetupResult O 2.226 b 20 ISLPInformation (Actual) O 2.132 c 21 22 Notes: 23 24 a. Include to identify the final CDMA service information negotiated. 25 26 b. Include to report the result of the operation. 27 28 c. Include appropriate ISLP information for circuit-mode services. 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 InterSystemSetup 540 - 92 X.S0004-540-E v2.0

1 2.35 InterSystemSMSDeliveryPointToPoint 2 3 4 The InterSystemSMSDeliveryPointToPoint (ISSMDPP) operation is used to relay an SMS message 5 from the Serving MSC for an MS-based SME to a Border MSC. 6 7 The following table lists the valid combinations of invoking and responding FEs. 8 INVOKING FE RESPONDING FE 9 10 Case 1 MSC MSC 11 12 13 The InterSystemSMSDeliveryPointToPoint operation is initiated with a TCAP INVOKE (LAST). 14 This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as 15 follows: 16 17 InterSystemSMSDeliveryPointToPoint INVOKE Parameters Timer: SMT 18 19 Field Value Type Reference Notes 20 21 Identifier SET [NATIONAL 18] M 520-1.3.2.1 22 Length variable octets M 520-1.3.2.1 23 24 Contents 25 SMS_BearerData M 2.233 26 27 SMS_TeleserviceIdentifier M 2.246 28 29 IMSI O 2.127 a 30 MobileIdentificationNumber O 2.140 a 31 32 SignalingMessageEncryptionKey O 2.228 b 33 SMS_MessageCount O 2.237 c 34 35 SMS_OriginalOriginatingAddress O 2.242 d 36 SMS_OriginalOriginatingSubaddress O 2.243 e 37 38 Notes: 39 40 a. Include if available. At least one parameter should be present. 41 42 b. Include if available. 43 44 c. Include if applicable. If not received, assume value 0. 45 46 d. Include to identify the SME from which the short message originated (e.g., the MDN, if 47 originated by an MS-based SME). 48 49 e. Include if applicable. 50 51 52 53 54 55 56 57 58 59 60 540 - 93 InterSystemSMSDeliveryPointToPoint X.S0004-540-E v2.0

The InterSystemSMSDeliveryPointToPoint operation success is reported with a TCAP RETURN 1 RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded 2 as follows: 3 4 5 InterSystemSMSDeliveryPointToPoint RETURN RESULT Parameters 6 7 Field Value Type Reference Notes 8 Identifier SET [NATIONAL 18] M 520-1.3.2.2 9 10 Length variable octets M 520-1.3.2.2 11 Contents 12 13 SMS_BearerData O 2.233 a 14 SMS_CauseCode O 2.234 b 15 16 17 18 Notes: 19 a. Include for positive or negative acknowledgments, when applicable. 20 21 b. Include for all negative acknowledgments. 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 InterSystemSMSDeliveryPointToPoint 540 - 94 X.S0004-540-E v2.0

1 2.36 InterSystemSMSPage 2 3 4 The InterSystemSMSPage (ISSMSPAGE) operation is a general purpose operation that is used to 5 convey an MS-terminated short message or in general any other information or encapsulated data to 6 a Border MSC. 7 8 The following table lists the valid combinations of invoking and responding FEs. 9 10 INVOKING FE RESPONDING FE 11 12 Case 1 Serving MSC Border MSC 13 14 The InterSystemSMSPage operation is initiated with a TCAP INVOKE (LAST). This is carried by 15 a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 16 17 18 InterSystemSMSPage INVOKE Parameters Timer: ISSPT 19 Field Value Type Reference Notes 20 21 Identifier SET [NATIONAL 18] M 520-1.3.2.1 22 Length variable octets M 23 520-1.3.2.1 24 Contents 25 26 SMS_BearerData M 2.236 27 28 SMS_TeleserviceIdentifier M 2.249 29 CDMA2000MobileSupportedCapabilities O 2.42 a 30 31 CDMASlotCycleIndex O 2.71 b 32 33 CDMAStationClassMark O 2.73 c, d 34 35 ElectronicSerialNumber O 2.113 e 36 37 IMSI O 2.130 f 38 LocationAreaID O 2.138 g 39 40 MobileIdentificationNumber O 2.143 f 41 42 NetworkTMSI O 2.161 f 43 44 PageIndicator O 2.173 h 45 46 PageResponseTime O 2.174 i 47 48 SMS_ChargeIndicator O 2.238 j 49 SMS_DestinationAddress O 2.239 k 50 51 SMS_OriginalDestinationAddress O 2.243 l 52 53 SMS_OriginalDestinationSubaddress O 2.244 m 54 55 SMS_OriginalOriginatingAddress O 2.245 n 56 57 SMS_OriginalOriginatingSubaddress O 2.246 m 58 SMS_OriginatingAddress O 2.247 o 59 60 540 - 95 InterSystemSMSPage X.S0004-540-E v2.0

Notes: 1 2 a. Include for cdma2000 mobiles or later. 3 4 b. Included when the Serving MSC knows that the MS is operating in CDMA Slotted Mode. 5 6 c. Include to indicate information of the current band in use. 7 d. Include if an 800 MHz CDMA channel is in use for an IS-41-C system. 8 9 e. Include to identify the destination MS. 10 11 f. Include if known and available, may be excluded if the parameter is known not to be 12 supported by the Border MSC. At least one parameter shall be included. 13 14 g. Include if known. 15 16 h. Include if request is to listen only. May include if request is to page. 17 18 i. Include to indicate the maximum time that the receiving system has to respond to this 19 message. 20 21 j. Include if applicable. If not received, charge message originator. 22 k. Include if different than the destination address (MobileIdentificationNumber or 23 underlying data transport destination address). May require an interconnection agreement 24 25 to facilitate interworking between network types. 26 l. Include if different than the destination address (MobileIdentificationNumber, 27 SMS_DestinationAddress, or underlying data transport destination address). 28 29 m. Include if applicable. 30 31 n. Include if different than the originating address (SMS_OriginatingAddress or underlying 32 data transport originating address). 33 34 o. Include if different than the MobileIdentificationNumber, or if not carried by the 35 underlying data transport. May require an interconnection agreement to facilitate 36 interworking between network types. 37 38 39 40 41 42 The ISSMSPAGE operation success is reported with a TCAP RETURN RESULT (LAST). This is 43 carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 44 45 InterSystemSMSPage RETURN RESULT Parameters 46 47 Field Value Type Reference Notes 48 Identifier SET [NATIONAL 18] M 520-1.3.2.2 49 50 Length variable octets M 520-1.3.2.2 51 Contents 52 53 SMS_BearerData O 2.236 a 54 55 SMS_CauseCode O 2.237 b 56 57 58 59 60 InterSystemSMSPage 540 - 96 X.S0004-540-E v2.0

1 Notes: 2 3 a. Include for positive acknowledgments, when applicable. 4 5 b. Include for all negative acknowledgments. 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 540 - 97 InterSystemSMSPage X.S0004-540-E v2.0

2.37 LocationRequest 1 2 3 The LocationRequest (LOCREQ) operation is used by an Originating MSC to obtain call treatment 4 instructions from the HLR. The call is identified by the dialed MS address digits received by the 5 Originating MSC. 6 7 The following table lists the valid combinations of invoking and responding FEs. 8 9 INVOKING FE RESPONDING FE 10 11 Case 1 Originating MSC HLR 12 13 The LocationRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a 14 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 15 16 17 LocationRequest INVOKE Parameters Timer: LRT 18 Field Value Type Reference Notes 19 20 Identifier SET [NATIONAL 18] M 520-1.3.2.1 21 Length variable octets M 520-1.3.2.1 22 23 Contents 24 25 BillingID (Originating) M 2.23 26 Digits (Dialed) M 2.105 27 28 MSCID (Originating) M 2.151 29 SystemMyTypeCode (Originating) M 2.260 30 31 CallingPartyName O 2.29 a 32 CallingPartyNumberDigits1 O 2.30 a, j 33 34 CallingPartyNumberDigits2 O 2.31 a, j 35 CallingPartySubaddress O 2.34 a 36 37 CDMAServiceOption O 2.66 f 38 MSCIdentificationNumber O 2.152 b 39 40 PC_SSN O 2.176 c 41 42 RedirectingNumberDigits O 2.198 a 43 RedirectingPartyName O 2.200 a 44 45 RedirectingSubaddress O 2.201 a 46 TerminationAccessType O 2.279 d 47 48 TDMAServiceCode O 2.273 g 49 TransactionCapability O 2.285 e 50 51 TriggerType O 2.289 i 52 WINCapability O 2.299 h 53 54 Notes: 55 56 a. Include if available (i.e., provided in call origination). 57 58 59 60 LocationRequest 540 - 98 X.S0004-540-E v2.0

1 b. Include to identify the initiating MSC and to indicate that the MSC is capable of accepting 2 digits in the international format. 3 4 c. Include if SS7 may be used for subsequent call redirection. 5 6 d. Include if call involves a special access situation (e.g., Roamer port access). 7 8 e. Include on IS-41-C or later. 9 f. Include to identify requested CDMA service information. 10 11 g. Include to identify requested TDMA service information. 12 13 h. Include to identify the WIN capabilities supported. 14 15 i. Include to identify the trigger encountered. 16 17 j. Send only the National (Significant) Number (with Nature of Number set to National) if the 18 E.164 country code of the caller’s number matches the E.164 country code used for 19 numbers from the MSC’s Country’s numbering plan. This consideration only applies for 20 MS to MS calls recognized as such by the MSC serving the calling MS. 21 22 23 The LocationRequest operation success is reported with a TCAP RETURN RESULT (LAST). This 24 is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 25 26 LocationRequest RETURN RESULT Parameters 27 28 Field Value Type Reference Notes 29 Identifier SET [NATIONAL 18] M 520-1.3.2.2 30 31 Length variable octets M 520-1.3.2.2 32 Contents 33 34 ElectronicSerialNumber M 2.112 a 35 36 MobileIdentificationNumber M 2.140 a 37 MSCID (Serving MSC) M 2.151 b 38 39 AccessDeniedReason O 2.1 c 40 AnnouncementList O 2.10 d 41 42 CallingPartyNumberString1 O 2.32 e 43 CallingPartyNumberString2 O 2.33 e 44 45 CDMAServiceOption O 2.66 p 46 Digits (Carrier) O 2.105 f, g 47 48 Digits (Destination) O 2.105 g, h, s 49 DisplayText O 2.106 e, r 50 51 DisplayText2 O 2.107 e, r 52 53 DMH_AccountCodeDigits O 2.108 i 54 DMH_AlternateBillingDigits O 2.109 i 55 56 DMH_BillingDigits O 2.110 i 57 DMH_RedirectionIndicator O 2.111 j 58 59 GroupInformation O 2.124 k 60 540 - 99 LocationRequest X.S0004-540-E v2.0

1 IMSI O 2.127 t 2 MobileDirectoryNumber O 2.139 i 3 4 NoAnswerTime O 2.165 l 5 OneTimeFeatureIndicator O 2.167 m 6 7 PC_SSN (Serving MSC or VLR) O 2.176 n 8 RedirectingNumberDigits O 2.198 j 9 10 RedirectingNumberString O 2.199 e 11 RedirectingSubaddress O 2.201 e, j 12 13 RoutingDigits O 2.209 f 14 TDMAServiceCode O 2.273 q 15 16 TerminationList O 2.280 o 17 18 TerminationTriggers O 2.283 f 19 TriggerAddressList O 2.286 f 20 21 Notes: 22 23 a. Value is all zeroes, if unknown. 24 25 b. Value is MSCID (Originating), if access is denied or routing to a directory number. 26 c. Include if access may be denied. 27 28 d. Include if one or more tones or announcements is to be applied to the calling party. 29 30 e. Include for local termination (e.g., the LocalTermination parameter is included within the 31 TerminationList parameter) if a related feature is active. 32 33 f. Include if applicable. 34 35 g. Include if call is to be routed over a network. 36 37 h. Use only with system not capable of using the TerminationList parameter. 38 i. Include if available for recording purposes (see DMH). 39 40 j. Include if available and call redirection may apply. 41 42 k. Include for multi-leg calls. 43 44 l. Include to request an override of the Originating MSC’s default No Answer Time value. 45 46 m. Include if modification to normal feature processing is required for a call in progress. 47 48 n. Include for possible screening by the Originating MSC for call redirection attempts on this 49 leg. 50 o. Include if call routing is required. 51 52 p. Include to identify accepted CDMA service information. 53 54 q. Include to identify accepted TDMA service information. 55 56 r. Include only one of these mutually exclusive parameters. 57 58 59 60 LocationRequest 540 - 100 X.S0004-540-E v2.0

1 s. Encode the Digits (Destination) as International if it is known that the Originating MSC 2 can accept the digits in this format (e.g., the MSCIdentificationNumber parameter was 3 received in the INVOKE) and an HLR stored number is being provided. 4 5 t. Include if available. 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 540 - 101 LocationRequest X.S0004-540-E v2.0

2.38 MessageDirective 1 2 3 The MessageDirective (MSGDIR) operation is used to update the message waiting information (e.g., 4 type and count of messages waiting) in a mobile subscriber’s HLR. 5 6 The following table lists the valid combinations of invoking and responding FEs. 7 8 INVOKING FE RESPONDING FE 9 Case 1 VMS HLR 10 11 Case 2 MC HLR 12 Case 3 MSC HLR 13 14 (VMS Host System) 15 Case 4 VMS MC 16 17 The MessageDirective operation is initiated with a TCAP INVOKE (LAST). This is carried by a 18 TCAP QUERY WITH PERMISION package. The Parameter Set is encoded as follows: 19 20 21 MessageDirective INVOKE Parameters Timer: MDT 22 23 Field Value Type Reference Notes 24 Identifier SET [NATIONAL 18] M 520-1.3.2.1 25 26 Length variable octets M 520-1.3.2.1 27 Contents 28 29 MessageWaitingNotificationCount O 2.136 a 30 MobileDirectoryNumber O 2.139 b, c 31 32 MSID O 2.153 b, c 33 34 Notes: 35 36 a. Include to indicate the type and number of messages waiting for the subscriber. 37 38 b. Include to identify the MS. 39 40 c. One of these parameters, but not both, must be included in each instance of the message. 41 42 The MessageDirective operation success is reported with a TCAP RETURN RESULT (LAST). This 43 is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 44 45 46 MessageDirective RETURN RESULT Parameters 47 Field Value Type Reference Notes 48 49 Identifier SET [NATIONAL 18] M 520-1.3.2.2 50 51 Length variable octets M 520-1.3.2.2 52 Contents 53 54 55 56 57 58 59 60 MessageDirective 540 - 102 X.S0004-540-E v2.0

1 2.39 MobileOnChannel 2 3 4 The MobileOnChannel (MSONCH) operation is invoked from the Target MSC to confirm the arrival 5 of the MS on the new channel, and thus a successful handoff. The MobileOnChannel completes a 6 transaction started with a FacilitiesDirective or a FacilitiesDirective2 operation invocation. 7 8 The following table lists the valid combinations of invoking and responding FEs. 9 10 INVOKING FE RESPONDING FE 11 Case 1 Target MSC Serving MSC 12 13 14 The MobileOnChannel operation is initiated with a TCAP INVOKE (LAST). This is carried by a 15 TCAP RESPONSE package. The Parameter Set is encoded as follows: 16 17 MobileOnChannel INVOKE Parameters 18 19 Field Value Type Reference Notes 20 21 Identifier SET [NATIONAL 18] M 520-1.3.2.1 22 Length zero octets M 520-1.3.2.1 23 24 Contents 25 26 27 Note that a RETURN RESULT or a RETURN ERROR component is never expected in reply to the 28 MobileOnChannel INVOKE message. 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 540 - 103 MobileOnChannel X.S0004-540-E v2.0

2.40 Modify 1 2 3 The Modify (MODIFY) operation is used by a service control function (SCF) to update data items 4 stored in a remote service data function (SDF) that have been changed as a result of service logic 5 processing. 6 7 The following table lists the valid combinations of invoking and responding FEs. 8 9 INVOKING FE RESPONDING FE 10 Case 1 SCP or SN SCP or SN 11 12 Case 2 SCP or SN HLR 13 Case 3 HLR SCP or SN 14 15 The Modify operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 16 17 QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 18 19 Modify INVOKE Parameters Timer: MT 20 21 Field Value Type Reference Notes 22 Identifier SET [NATIONAL 18] M 520-1.3.2.1 23 24 Length variable octets M 520-1.3.2.1 25 Contents 26 27 DatabaseKey M 2.91 a 28 29 ModificationRequestList M 2.146 30 31 Notes: 32 a. Parameter value is determined by bi-lateral negotiation between sender and receiver to be 33 34 interpreted as a database key. For example, possible values might be mobile DN, mobile 35 identification number, or a proprietary database key. 36 37 The Modify operation success is reported with a TCAP RETURN RESULT (LAST). This is carried 38 by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 39 40 41 Modify RETURN RESULT Parameters 42 Field Value Type Reference Notes 43 44 Identifier SET [NATIONAL 18] M 520-1.3.2.2 45 46 Length variable octets M 520-1.3.2.2 47 Contents 48 49 ModificationResultList M 2.148 a 50 51 Notes: 52 53 a. The ModificationResultList parameter contains one ModificationResult for each 54 ModificationRequest in the ModificationRequestList parameter in the Modify INVOKE. 55 Each of the ModificationResults corresponds to one of the ModificationRequests. The 56 ModificationResults are included in the ModificationResultList in the same order as the 57 corresponding ModificationRequests are included in the ModificationRequestList. 58 59 60 Modify 540 - 104 X.S0004-540-E v2.0

1 2.41 MSInactive 2 3 4 5 This operation was named CSSInactive prior to revision C of IS-41. 6 7 8 The MSInactive (MSINACT) operation is used to indicate that an MS is inactive. The MSInactive 9 operation is also used by the Serving VLR to notify the HLR of the cancellation of an MS’s 10 registration. The MSInactive operation is used by the HLR to provide the MS’s CallHistoryCount to 11 the AC when the SSD is shared with the VLR, and the VLR cancels the MS’s registration. 12 13 The following table lists the valid combinations of invoking and responding FEs. 14 15 INVOKING FE RESPONDING FE 16 Case 1 Serving MSC Serving VLR 17 18 Case 2 Serving VLR HLR 19 20 Case 3 HLR AC 21 22 The MSInactive operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 23 QUERY WITH PERMISSION package. The parameter set is encoded as follows: 24 25 26 MSInactive INVOKE Parameters Timer: MSIT 27 Field Value Type Reference Notes 28 29 Identifier SET [NATIONAL 18] M 520-1.3.2.1 30 Length variable octets M 520-1.3.2.1 31 32 Contents 33 34 ElectronicSerialNumber M 2.112 35 MSID M 2.153 h 36 37 CallHistoryCount O 2.26 a 38 DeregistrationType O 2.101 b 39 40 DestinationDigits O 2.103 g 41 LocationAreaID O 2.135 c 42 43 SenderIdentificationNumber O 2.215 d 44 ServicesResult O 2.224 f 45 46 SMS_MessageWaitingIndicator O 2.238 e 47 48 Notes: 49 50 a. Include if MS registration is canceled and if the SSD is shared. 51 52 b. Include from VLR to HLR and HLR to AC for MS deregistration. 53 54 c. May be included from MSC-V to VLR. Usage in the HLR is not defined. 55 d. May be included to identify the functional entity sending this message. 56 57 e. Include to indicate that an SMS message is pending delivery. 58 59 f. Include to indicate result of a PSID/RSID delivery to an MS. 60 540 - 105 MSInactive X.S0004-540-E v2.0

g. Include when received from MS in De-registration. 1 2 h. Include the identifier with which the MS last accessed the system, unless that identifier was 3 a MIN-based IMSI, in which case the MobileIdentificationNumber (populated with the 4 MIN derived from that IMSI) should be included. 5 6 7 The MSInactive operation success is reported with a TCAP RETURN RESULT (LAST). This is 8 carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 9 10 11 MSInactive RETURN RESULT Parameters 12 Field Value Type Reference Notes 13 14 Identifier SET [NATIONAL 18] M 520-1.3.2.2 15 16 Length variable octets M 520-1.3.2.2 17 Contents 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 MSInactive 540 - 106 X.S0004-540-E v2.0

1 2.42 NumberPortabilityRequest 2 3 4 The NumberPortabilityRequest (NPREQ) operation is used to request routing information when digit 5 analysis indicates that the called Directory Number (DN) is a portable number. 6 7 The following table lists the valid combinations of invoking and responding FEs. 8 9 INVOKING FE RESPONDING FE 10 Case 1 MSC NPDB 11 12 13 The NPREQ operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 14 QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 15 16 NumberPortabilityRequest INVOKE Parameters Timer: NPT 17 18 Field Value Type Reference Notes 19 20 Identifier SET [NATIONAL 18] M 520-1.3.2.1 21 Length variable octets M 520-1.3.2.1 22 23 Contents 24 Digits (Dialed) M 2.105 25 26 CallingPartyNumberDigits1 O 2.30 a 27 MSCID O 2.151 b 28 29 MSID (Originating) O 2.153 a 30 31 Notes: 32 33 a. The inclusion of this parameter is no longer recommended. 34 35 b. Include to identify the MSC sending the query. 36 37 38 39 The NPREQ operation success is reported with a TCAP RETURN RESULT (LAST). This is carried 40 by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 41 42 43 NumberPortabilityRequest RETURN RESULT Parameters 44 Field Value Type Reference Notes 45 46 Identifier SET [NATIONAL 18] M 520-1.3.2.2 47 Length variable octets M 520-1.3.2.2 48 49 Contents 50 51 RoutingDigits O 2.209 a 52 53 Notes: 54 55 a. Include to indicate the LRN. This parameter is required when the number has been ported. 56 57 58 59 60 540 - 107 NumberPortabilityRequest X.S0004-540-E v2.0

2.43 OriginationRequest 1 2 3 The OriginationRequest (ORREQ) operation is used to request call origination treatment on behalf of 4 a registered MS. It is also used for TDMA OTASP, where it may be sent by the MSC to the OTAF 5 when an MS OTASP origination is received by the MSC. This OTASP origination may be initiated 6 from either an unprogrammed or preprogrammed MS. An SCP may use the OriginationRequest 7 (ORREQ) operation to obtain an IMS Routing address from a VCC AS. 8 9 10 The following table lists the valid combinations of invoking and responding FEs. 11 12 INVOKING FE RESPONDING FE 13 14 Case 1 Serving MSC HLR 15 Case 2 Serving MSC OTAF 16 (Note 1) 17 18 Case 3 HLR SCP 19 Case 4 Serving MSC SCP 20 21 Case 5 SCP VCC AS 22 23 Notes: 24 25 Note 1 is only applicable to TDMA OTASP. 26 27 28 The OriginationRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a 29 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 30 31 OriginationRequest INVOKE Parameters Timer: ORT 32 33 Field Value Type Reference Notes 34 35 Identifier SET [NATIONAL 18] M 520-1.3.2.1 36 Length variable octets M 520-1.3.2.1 37 38 Contents 39 BillingID (originating) M 2.23 40 41 Digits (Dialed) M 2.105 42 ElectronicSerialNumber M 2.112 43 44 MSID M 2.153 g 45 46 MSCID (Originating MSC) M 2.151 47 OriginationTriggers M 2.169 48 49 TransactionCapability M 2.285 50 CallingPartyName O 2.29 h 51 52 CallingPartyNumberDigits1 O 2.30 a, m 53 CallingPartyNumberDigits2 O 2.31 a, m 54 55 CallingPartySubaddress O 2.34 a 56 CDMAServiceOption O 2.66 n 57 58 LocationAreaID O 2.135 a 59 60 OriginationRequest 540 - 108 X.S0004-540-E v2.0

1 MobileDirectoryNumber O 2.139 b 2 3 MobileIdentificationNumber O 2.140 p 4 MSCIdentificationNumber O 2.152 c 5 6 OneTimeFeatureIndicator O 2.167 d 7 8 PC_SSN (Originating MSC) O 2.176 e 9 PreferredLanguageIndicator O 2.179 k 10 11 SenderIdentificationNumber O 2.215 f 12 ServingCellID O 2.225 a 13 14 SMS_Address O 2.232 i 15 SystemCapabilities O 2.259 j 16 17 SystemMyTypeCode (originating MSC) O 2.260 q 18 TriggerType O 2.289 l 19 20 TDMAServiceCode O 2.273 o 21 WINCapability O 2.299 a 22 23 Notes: 24 25 a. Include if applicable. 26 27 b. Include if available for recording purposes (see DMH). 28 29 c. Include to identify the initiating MSC and to indicate that the MSC is capable of accepting 30 digits in the international format. 31 32 d. Include if any OneTimeFeatureIndicator status bits are set (i.e., have value of 1). 33 34 e. Include if SS7 may be used for subsequent call redirection. 35 f. Include if different from the MSCIdentificationNumber to identify the functional entity 36 37 sending the message. 38 g. Include the identifier with which the MS last accessed the system, unless that identifier was 39 a MIN based IMSI, in which case the MobileIdentificationNumber (populated with the 40 41 MIN derived from that IMSI) should be included. 42 h. Include if calling party name information is known. 43 44 i. Include for TDMA OTASP call origination if routing of teleservice message is applicable. 45 46 j. Include for TDMA OTASP call origination if the system is capable of authentication, voice 47 privacy and signaling message encryption. 48 49 k. Include if available. 50 51 l. Include to identify the trigger encountered. 52 53 m. Send only the National (Significant) Number (with Nature of Number set to National) if the 54 E.164 country code of the caller’s number matches the E.164 country code used for 55 numbers from the MSC’s Country’s Numbering Plan. 56 57 n. Include to specify requested CDMA service information. 58 o. Include to specify requested TDMA service information. 59 60 540 - 109 OriginationRequest X.S0004-540-E v2.0

p. Include if known and if the IMSI has been included as MSID. 1 2 q. Include if available to identify the originating system manufacturer. 3 4 The OriginationRequest operation success is reported with a TCAP RETURN RESULT (LAST). 5 This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 6 7 OriginationRequest RETURN RESULT Parameters 8 9 Field Value Type Reference Notes 10 11 Identifier SET [NATIONAL 18] M 520-1.3.2.2 12 Length variable octets M 520-1.3.2.2 13 14 Contents 15 AccessDeniedReason O 2.1 a 16 17 ActionCode O 2.2 b 18 AnnouncementList O 2.10 c 19 20 CallingPartyNumberString1 O 2.32 d, e 21 22 CallingPartyNumberString2 O 2.33 d, e 23 CallingPartySubaddress O 2.34 d, e, f 24 25 CarrierDigits O 2.37 g 26 Digits (Dialed) O 2.105 h 27 28 DisplayText O 2.106 d, e, r 29 DisplayText2 O 2.107 d, e, r 30 31 DMH_AccountCodeDigits O 2.108 i 32 DMH_AlternateBillingDigits O 2.109 i 33 34 DMH_BillingDigits O 2.110 i 35 DMH_RedirectionIndicator O 2.111 i, j 36 37 GroupInformation O 2.124 k 38 39 MobileDirectoryNumber O 2.139 i 40 NoAnswerTime O 2.165 l 41 42 OneTimeFeatureIndicator O 2.167 m 43 PilotNumber O 2.178 k 44 45 PreferredLanguageIndicator O 2.179 s, t 46 RedirectingNumberDigits O 2.198 f 47 48 RedirectingNumberString O 2.199 d 49 RedirectingSubaddress O 2.201 d, e 50 51 RoutingDigits O 2.209 g 52 TerminationList O 2.280 n 53 54 TerminationTriggers O 2.283 o 55 56 TriggerAddressList O 2.286 q 57 58 59 60 OriginationRequest 540 - 110 X.S0004-540-E v2.0

1 Notes: 2 3 a. Include if access is denied. If included, no other optional parameters shall be included (with 4 the exception of the AnnouncementList parameter). 5 6 b. Include if action to be performed is not implied through presence of other parameters. 7 8 c. Include if one or more tones or announcements are to be applied to the MS. 9 d. Include if a LocalTermination parameter is included in the TerminationList parameter. 10 11 e. Include if the related feature is active. 12 13 f. Include if a PSTNTermination parameter or an IntersystemTermination parameter is 14 included within the TerminationList parameter. 15 16 g. Include if applicable. 17 18 h. Include if digits remain to be translated by the MSC. Encode the Digits (Dialed) as 19 International if: 20 21 - The digits being returned are the results of a stored translation of the termination address 22 into a destination address (e.g., the expansion of an abbreviated dialing string), and 23 24 - the serving MSC is known to be capable of accepting digits in International format (e.g., 25 the MSCIdentificationNumber parameter was received) in the corresponding INVOKE. 26 27 i. Include if available for recording purposes (see DMH). 28 j. Include if redirection may apply. 29 30 k. Include for multi-leg calls. 31 32 l. Include to request an override of the Serving MSC’s default No Answer Time value. 33 34 m. Include if modification to normal feature processing is required for the call in progress. 35 36 n. Include if call routing is required. 37 o. Include to indicate processing in the Originating MSC for failed call attempts. 38 39 p. Intentionally left for future modifications. 40 41 q. Include to indicate address associated with active WIN triggers. 42 43 r. Include only one of these mutually exclusive parameters. 44 45 s. Include to identify the Preferred Language. 46 47 t. This parameter may only be included if the AnnouncementList parameter is present. 48 49 50 51 52 53 54 55 56 57 58 59 60 540 - 111 OriginationRequest X.S0004-540-E v2.0

2.44 OTASPRequest 1 2 3 The OTASPRequest (OTASPREQ) operation is used by the OTAF to request the initiation of certain 4 AC procedures (such as A-key Generation, SSD Update and Commit or Release a temporary A-key, 5 etc.), and to also return certain parameters. 6 7 The following table lists the valid combinations of invoking and responding FEs: 8 9 INVOKING FE RESPONDING FE 10 Case 1 OTAF HLR 11 12 Case 2 HLR AC 13 14 The OTASPRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a 15 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 16 17 18 OTASPRequest INVOKE Parameters Timer: OTART 19 Field Value Type Reference Notes 20 21 Identifier SET [NATIONAL 18] M 520-1.3.2.1 22 23 Length variable octets M 520-1.3.2.1 24 Contents 25 26 ActionCode O 2.2 a 27 AKeyProtocolVersion O 2.3 b 28 29 AuthenticationData O 2.13 c 30 AuthenticationResponse O 2.14 c 31 32 CallHistoryCount O 2.26 c 33 ElectronicSerialNumber O 2.112 d 34 35 MSID O 2.153 d, e 36 MobileStationMSID O 2.143 f 37 38 MobileStationPartialKey O 2.144 g 39 40 MSCID (Serving MSC) O 2.151 h, n 41 NewlyAssignedMSID O 2.161 i, o 42 43 PC_SSN O 2.176 n 44 RandomVariable O 2.189 c 45 46 RandomVariableBaseStation O 2.190 m 47 ServiceIndicator O 2.221 j 48 49 SystemCapabilities O 2.259 k 50 TerminalType O 2.278 l 51 52 Notes: 53 54 a. Include to identify action to be performed. 55 56 57 58 59 60 OTASPRequest 540 - 112 X.S0004-540-E v2.0

1 b. Include for CDMA OTAPA to identify available version(s) of A-key Generation 2 procedure(s) at the MS if the generation of public encryption values is being requested. 3 Include for TDMA OTA to specify the A-Key protocol version supported if the action code 4 indicates an A-Key operation. 5 6 c. Received from the MS during CDMA OTASP (or CDMA OTAPA) in the Re-Authenticate 7 Response OTASP Data Message. Include for CDMA OTASP or CDMA OTAPA when re- 8 authenticating the MS. 9 10 d. Include to identify the MS. 11 12 e. For CDMA OTASP, contains the Activation_MIN. For CDMA OTAPA, contains the MS’s 13 MSID at the start of the OTAPA session. IF the MS has both a MIN and an IMSI at the start 14 of the OTAPA session then the MIN form of the MSID is used. 15 For TDMA OTA, the MSID parameter contains either the MS generated Activation_MIN, 16 or the MS’s real MIN or IMSI, as applicable. 17 18 f. Include for CDMA OTASP but not for CDMA OTAPA. Only use the MobileStationIMSI 19 form of the MobileStationMSID if the IMSI_T was received from the MS at OTASP call 20 1 21 origination and a MIN is not programmed in the MS. 22 g. Include for CDMA OTASP or CDMA OTAPA if A-key is to be generated. Include for 23 24 TDMA OTA if the MS partial key is being supplied to the AC. 25 h. Include for CDMA OTASP to identify the Serving System if either SSD Update or 26 Reauthentication is being requested. (Not available for OTAPA). 27 28 i. Include for CDMA OTASP or CDMA OTAPA if the ActionCode indicates Commit A-Key 29 and if a new MIN has been assigned to the MS or, for an MS that has no MIN programmed 30 2 3 31 (or whose MIN is being erased), if a new IMSI has been assigned to the MS. Otherwise 32 this parameter is not included. The NEWMIN form of this parameter should be used if both 33 a new MIN and a new IMSI are assigned to the MS. 34 35 j. Include for CDMA OTASP, CDMA OTAPA and TDMA OTASP. 36 k. Include for CDMA OTASP to identify the serving system’s authentication capabilities. 37 38 l. The MS’s Terminal Type. Include for CDMA OTASP or CDMA OTAPA, if needed by the 39 AC, when the ActionCode indicates Commit A-key. [Refer to CDMA and AUTH] 40 41 m. Include for CDMA OTAPA, when the ActionCode indicates Generate Authentication 42 Signature, to transport the RAND_OTAPA to the AC. 43 44 n. Include for TDMA OTA to specify the address of the MSC if the initiation of an AC 45 procedure (as specified by the ACTCODE) is being requested. 46 For MSCIDs, the HLR may translate the MSCID into the appropriate (e.g., SS7, X.25) 47 48 49 1 It may be necessary to upload a NAM parameter block to determine this for an unknown MS. (For CDMA OTASP, if the 50 OTAF initiates an SSD update, the AC uses the received MS_MSID to calculate AUTHU whereas the MS uses its MIN, if one 51 is programmed. If a MIN is programmed in the MS, the SSD update cannot succeed unless the MS_MSID provides that MIN 52 to the AC.) 53 54 2 It may be necessary to upload a NAM parameter block to determine this for an unknown MS that has initiated a CDMA 55 OTASP session. 56 3 57 A new MIN must be assigned to replace the existing MIN or the existing MIN must be erased from memory for an unknown 58 MS that has a previously programmed MIN. (Otherwise, the MS would use that old MIN for its authentication calculations, 59 but the AC would not have that old MIN available for its authentication calculations.) 60 540 - 113 OTASPRequest X.S0004-540-E v2.0

address variant. In the case when one VLR serves multiple MSCs, the HLR will include this 1 address in the message being forwarded toward the MSC (from the AC). The HLR will use 2 this address to route to the VLR. The VLR will use this address to route to the appropriate 3 MSC. The VLR will not include this address in the message to MSC. 4 5 o. Include for TDMA OTASP to specify the MSID that will be assigned to the MS, as a result 6 of this OTASP session, if the MIN parameter contains as activation MIN. 7 8 9 The OTASPRequest operation success is reported with a TCAP RETURN RESULT (LAST). This 10 is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 11 12 OTASPRequest RETURN RESULT Parameters 13 14 Field Value Type Reference Notes 15 16 Identifier SET [NATIONAL 18] M 520-1.3.2.2 17 Length variable octets M 520-1.3.2.2 18 19 Contents 20 AKeyProtocolVersion O 2.3 a 21 22 AuthenticationResponseBaseStation O 2.15 g 23 24 BaseStationPartialKey O 2.22 b 25 DenyAccess O 2.100 c 26 27 EnhancedPrivacyEncryptionReport O 2.114 h 28 ModulusValue O 2.149 b 29 30 OTASP_ResultCode O 2.170 d 31 PrimitiveValue O 2.180 b 32 33 SignalingMessageEncryptionReport O 2.229 e 34 SSDUpdateReport O 2.254 f 35 36 UniqueChallengeReport O 2.291 f 37 VoicePrivacyReport O 2.298 e 38 39 40 Notes: 41 a. Included to indicate the selected A-key generation protocol procedure. 42 43 b. Include for CDMA to return Public Encryption Values to the OTAF. 44 Include for TDMA if the public encryption values are known 45 46 c. Include for CDMA OTA to convey authentication failure or count mismatch during the Re- 47 Authentication procedure. 48 49 d. Include for CDMA to convey information other than what can be conveyed in the 50 DenyAccess, UniqueChallengeReport, SSDUpdateReport, 51 SignalingMessageEncryptionReport, and the VoicePrivacyReport parameters. 52 Include for TDMA if the OTASP result code is known. 53 54 e. Include for CDMA to convey the values received by the AC in the 55 AuthenticationStatusReport INVOKE during the Re-Authentication procedure. Include for 56 TDMA to convey the values received by the AC in the AuthenticationStatusReport 57 INVOKE during the SSD update and re-authentication procedures. 58 59 60 OTASPRequest 540 - 114 X.S0004-540-E v2.0

1 f. Include for CDMA to convey the values received by the AC in the 2 AuthenticationStatusReport INVOKE during the SSD update procedure. 3 Include for TDMA to convey the values received by the AC in the 4 AuthenticationStatusReport INVOKE during the SSD update and re-authentication 5 procedures. 6 7 g. Include for CDMA OTAPA to transport the AUTH_OTAPA, the authentication signature 8 value generated by the AC, to the OTAF. 9 10 h. Include if report related to TDMA Enhanced Privacy and Encryption. 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 540 - 115 OTASPRequest X.S0004-540-E v2.0

2.45 ParameterRequest 1 2 3 The Parameter Request (PARMREQ) operation is used to obtain the required parameters associated 4 with the MS. 5 6 The following table lists the valid combinations of invoking and responding FEs: 7 8 INVOKING FE RESPONDING FE 9 Case 1 New Serving VLR Old Serving VLR 10 11 Case 2 Serving MSC Serving VLR 12 13 One of two possible results is returned: 14 15 1. The ParameterRequest operation is successful. 16 2. Notification that ParameterRequest is unsuccessful with an appropriate denied 17 reason. 18 19 The ParameterRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a 20 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 21 22 23 ParameterRequest INVOKE Parameters Timer: PRT 24 Field Value Type Reference Notes 25 26 Identifier SET [NATIONAL 18] M 520-1.3.2.1 27 28 Length variable octets M 520-1.3.2.1 29 Contents 30 31 RequiredParametersMask M 2.205 32 ElectronicSerialNumber O 2.112 a 33 34 MSID O 2.153 b 35 MSCID O 2.151 c 36 37 NetworkTMSI O 2.158 b 38 PC_SSN O 2.176 d 39 40 SenderIdentificationNumber O 2.215 e 41 SystemMyTypeCode O 2.260 f 42 43 44 Notes: 45 a. Include if appropriate. 46 47 b. Include to identify the MS; at least one should be provided. 48 49 c. Include to identify initiating MSC. 50 51 d. Include if SS7 is used. 52 53 e. May be included to identify the functional entity sending this message. 54 f. Include to identify the originating system manufacturer. 55 56 57 58 59 60 ParameterRequest 540 - 116 X.S0004-540-E v2.0

1 The ParameterRequest operation success is reported with a TCAP RETURN RESULT (LAST). This 2 is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 3 4 5 ParameterRequest RETURN RESULT Parameters 6 Field Value Type Reference Notes 7 8 Identifier SET [NATIONAL 18] M 520-1.3.2.2 9 Length variable octets M 520-1.3.2.2 10 11 Contents 12 13 ElectronicSerialNumber O 2.112 a 14 IMSI O 2.127 a 15 16 LocationAreaID O 2.135 a 17 MobileIdentificationNumber O 2.140 a 18 19 NetworkTMSI O 2.158 a 20 ReasonList O 2.195 b 21 22 Notes: 23 24 a. Include as indicated in RequiredParametersMask received in the ParameterRequest Invoke. 25 26 b. Include if the required parameters are unavailable. 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 540 - 117 ParameterRequest X.S0004-540-E v2.0

2.46 QualificationDirective 1 2 3 The QualificationDirective (QUALDIR) operation is used to update the authorization information, 4 profile information, or both, previously obtained for an MS. 5 6 The following table lists the valid combinations of invoking and responding FEs. 7 8 INVOKING FE RESPONDING FE 9 Case 1 HLR Serving VLR 10 11 Case 2 Serving VLR Serving MSC 12 13 The QualificationDirective operation is initiated with a TCAP INVOKE (LAST). This is carried by 14 15 a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 16 17 QualificationDirective INVOKE Parameters Timer: QDT 18 19 Field Value Type Reference Notes 20 Identifier SET [NATIONAL 18] M 520-1.3.2.1 21 22 Length variable octets M 520-1.3.2.1 23 Contents 24 25 ElectronicSerialNumber M 2.112 26 27 MSID M 2.153 j 28 QualificationInformationCode M 2.187 29 30 SystemMyTypeCode (HLR or VLR) M 2.260 31 AnalogRedirectRecord O 2.8 l 32 33 AuthorizationDenied O 2.18 a 34 AuthorizationPeriod O 2.19 b 35 36 CDMARedirectRecord O 2.62 m 37 ControlChannelMode O 2.87 k 38 39 DeniedAuthorizationPeriod O 2.99 c 40 Digits (Carrier) O 2.105 d, e 41 42 Digits (Destination) O 2.105 d, f, p 43 44 LocationAreaID O 2.135 g 45 Profile **Macro** O 2.182 h, q 46 47 RoamingIndication O 2.208 n 48 SenderIdentificationNumber O 2.215 i 49 50 ServiceRedirectionInfo O 2.223 l, m, o 51 52 Notes: 53 54 a. If included, no other optional parameters except the DeniedAuthorizationPeriod parameter 55 shall be present. 56 57 b. Include if validation is being updated. 58 59 60 QualificationDirective 540 - 118 X.S0004-540-E v2.0

1 c. May be included if the AuthorizationDenied parameter is present to indicate the interval 2 before re-authorization may be attempted. 3 4 d. Use only on systems not capable of supporting the TransactionCapability parameter. 5 6 e. Include if profile is being updated and preferred carrier is applicable. 7 8 f. Include if profile is being updated and originations are restricted to selected leading digits 9 of a directory number or of an international E.164 number (e.g., set to NPA-NXX to restrict 10 originations to a 6-digit NANP office code or set to NPA-NXX-XXXX to restrict 11 originations to a single NANP directory number). 12 13 g. May be included from VLR to Serving MSC. Usage from the HLR is not defined. 14 15 h. Include applicable parameter(s) (see 2.182). 16 i. May be included to identify the functional entity sending the message. 17 18 j. The HLR includes the IMSI type of MSID if the IMSI was present in the last message 19 received from the Serving System; otherwise the HLR includes the 20 MobileIdentificationNumber type of MSID. The VLR includes the type of MSID last 21 received from the Serving MSC; this may not be the type of MSID received from the HLR. 22 23 k. Include if MS is Digital Control Channel capable, to indicate the last known access mode. 24 25 l. Include for NDSS if HLR is to redirect the MS to an analog system. 26 27 m. Include for NDSS if HLR is to redirect the MS to a CDMA system. 28 29 n. Include for CDMA to support Enhanced Roaming Indicator. 30 31 o. Include if the MS NDSS feature is to be suppressed or activated. 32 p. Encode the Digits (Destination) as International if it is known that the serving MSC can 33 accept the digits in this format (e.g., the MSCIdentificationNumber parameter was received 34 35 during registration). 36 q. The DMH_BillingDigits, MobileDirectoryNumber and RestrictionDigits parameters 37 should be encoded as International when loaded into the profile if it is known that the 38 39 serving MSC can accept them in this format (e.g., the MSCIdentificationNumber parameter 40 was received during registration). 41 42 The QualificationDirective operation success is reported with a TCAP RETURN RESULT (LAST). 43 This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 44 45 46 QualificationDirective RETURN RESULT Parameters 47 Field Value Type Reference Notes 48 49 Identifier SET [NATIONAL 18] M 520-1.3.2.2 50 51 Length zero octets M 520-1.3.2.2 52 Contents 53 54 55 56 57 58 59 60 540 - 119 QualificationDirective X.S0004-540-E v2.0

2.47 QualificationRequest 1 2 3 The QualificationRequest (QUALREQ) operation is used (a) to request validation of an MS, (b) to 4 request an MS’s profile information, or (c) both. 5 6 The following table lists the valid combinations of invoking and responding FEs. 7 8 INVOKING FE RESPONDING FE 9 Case 1 Serving MSC Serving VLR 10 11 Case 2 Serving VLR HLR 12 13 The QualificationRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a 14 15 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 16 17 QualificationRequest INVOKE Parameters Timer: QRT 18 19 Field Value Type Reference Notes 20 Identifier SET [NATIONAL 18] M 520-1.3.2.1 21 22 Length variable octets M 520-1.3.2.1 23 Contents 24 25 ElectronicSerialNumber M 2.112 26 27 MSID M 2.153 c 28 QualificationInformationCode M 2.187 29 30 SystemMyTypeCode (MSC or VLR) M 2.260 31 CDMANetworkIdentification (Serving) O 2.57 i 32 33 ControlChannelMode O 2.87 j 34 LocationAreaID O 2.135 d 35 36 MSCID (Serving MSC or Originating MSC) O 2.151 a 37 MSCIdentificationNumber O 2.152 m 38 39 ServiceRedirectionCause O 2.222 k 40 SenderIdentificationNumber O 2.215 b 41 42 SystemAccessType O 2.258 a 43 44 TerminalType O 2.278 j 45 TransactionCapability O 2.285 a, f, l 46 47 UserGroup O 2.293 e 48 UserZoneData O 2.294 g 49 50 WINCapability O 2.299 h 51 52 Notes: 53 54 a. Should be included on IS-41-C or later. 55 b. May be included to identify the functional entity sending the message. 56 57 58 59 60 QualificationRequest 540 - 120 X.S0004-540-E v2.0

1 c. Include the identifier with which the MS last accessed the system, unless that identifier was 2 a MIN-based IMSI, in which case the MobileIdentificationNumber (populated with the 3 MIN derived from that IMSI) should be included. 4 5 d. May be included from MSC to VLR. 6 7 e. Include if a change in the allocation status of a User Group is requested by the MS user. 8 9 f. Include if system is User Zone capable. 10 11 g. Include to indicate the UZID indicated by the subscriber’s chosen PSID/RSID. 12 h. Include to identify the WIN capabilities supported. 13 14 i. Include for NDSS to identify the serving network. 15 16 j. Include for NDSS to identify the operating mode of the MS. 17 18 k. Include for NDSS to indicate reason for MS registration or access. 19 20 l. Include if the system is NDSS capable. 21 m. Include to identify the initiating MSC and to indicate that the MSC is capable of accepting 22 23 digits in the international format. 24 25 The QualificationRequest operation success is reported with a TCAP RETURN RESULT (LAST). 26 This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 27 28 29 QualificationRequest RETURN RESULT Parameters 30 Field Value Type Reference Notes 31 32 Identifier SET [NATIONAL 18] M 520-1.3.2.2 33 Length variable octets M 520-1.3.2.2 34 35 Contents 36 37 SystemMyTypeCode (VLR or HLR) M 2.260 38 AnalogRedirectRecord O 2.8 i 39 40 AuthorizationDenied O 2.18 a 41 AuthorizationPeriod O 2.19 b 42 43 CDMARedirectRecord O 2.62 j 44 ControlChannelMode O 2.87 h 45 46 DeniedAuthorizationPeriod O 2.99 c 47 Digits (Carrier) O 2.105 d 48 49 Digits (Destination) O 2.105 e, l 50 MSCID (HLR) O 2.151 f 51 52 Profile **Macro** O 2.182 g, m 53 54 RoamingIndication O 2.208 k 55 ServiceRedirectionInfo O 2.223 i, j 56 57 58 59 60 540 - 121 QualificationRequest X.S0004-540-E v2.0

Notes: 1 2 a. If included, no other optional parameter except the DeniedAuthorizationPeriod parameter 3 shall be present. 4 5 b. Include if validation requested. 6 7 c. May be included if the AuthorizationDenied parameter is present to indicate the interval 8 before re-authorization may be attempted. 9 10 d. Include if profile requested and preferred carrier is applicable and TransactionCapability 11 parameter is not received. 12 13 e. Include if profile requested and originations are restricted to selected leading digits of 14 directory numbers or of international E.164 numbers, (e.g., NPA-NXX or 15 NPA-NXX-XXXX for NANP) and TransactionCapability parameter is not received. 16 17 f. Include on IS-41-C and later and authorization is not denied. 18 g. Include applicable parameter(s) (see 2.182). 19 20 h. Include if the MS is Digital Control Channel capable, to indicate the last known access 21 mode. 22 23 i. Include for NDSS if HLR is to redirect the MS to an analog system. 24 25 j. Include for NDSS if HLR is to redirect the MS to a CDMA system. 26 27 k. Include for CDMA to support Enhanced Roaming Indicator. 28 29 l. Encode the Digits (Destination) as International if it is known that the serving MSC can 30 accept the digits in this format (e.g., the MSCIdentificationNumber parameter was received 31 in the INVOKE). 32 33 m. The DMH_BillingDigits, MobileDirectoryNumber and RestrictionDigits parameters 34 should be encoded as International when loaded into the profile if it is know that the serving 35 MSC can accept them in this format (e.g., the MSCIdentificationNumber parameter was 36 received in the INVOKE). 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 QualificationRequest 540 - 122 X.S0004-540-E v2.0

1 2.48 QualificationRequest2 2 3 4 The QualificationRequest2 operation is used (a) to request validation of an MS, (b) to request an 5 MS’s profile information, or (c) both. 6 7 The following table lists the valid combinations of invoking and responding FEs. 8 INVOKING FE RESPONDING FE 9 10 Case 1 Serving MSC Serving VLR 11 12 Case 2 Serving VLR HLR 13 14 15 16 The QualificationRequest2 operation is initiated with a TCAP INVOKE (LAST). This is carried by 17 a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 18 19 20 QualificationRequest2 INVOKE Parameters Timer: QRT 21 Field Value Type Reference Notes 22 23 Identifier SET [NATIONAL 18] M 520-1.3.2.1 24 Length variable octets M 520-1.3.2.1 25 26 Contents 27 MSCID (Serving MSC or Originating MSC) M 2.154 28 29 QualificationInformationCode M 2.190 30 31 SystemAccessType M 2.261 32 SystemMyTypeCode (MSC or VLR) M 2.263 33 34 TransactionCapability M 2.288 a 35 CDMANetworkIdentification (Serving) O 2.58 b 36 37 ControlChannelMode O 2.88 c 38 ElectronicSerialNumber O 2.113 d 39 40 LocationAreaID O 2.138 e 41 MobileDirectoryNumber O 2.142 f 42 43 MSCIdentificationNumber O 2.155 g 44 MSID O 2.156 d, h 45 46 NonPublicData O 2.169 47 48 ServiceRedirectionCause O 2.225 i 49 SenderIdentificationNumber O 2.218 j 50 51 TerminalType O 2.281 k 52 UserGroup O 2.297 l 53 54 UserZoneData O 2.298 m 55 WINCapability O 2.303 n 56 57 58 59 60 540 - 123 QualificationRequest2 X.S0004-540-E v2.0

Notes: 1 2 a. Include if system is User Zone capable. 3 4 b. Include for NDSS to identify the serving network. 5 6 c. Include for NDSS to identify the operating mode of the MS. 7 d. Include if known (e.g., not an MDN-based request). 8 9 e. May be included from MSC to VLR. 10 11 f. Include if this is a request for validation and profile based on a subscriber’s MDN. 12 13 g. Include to identify the initiating MSC and to indicate that the MSC is capable of accepting 14 digits in the international format. 15 16 h. Include the identifier with which the MS last accessed the system, unless that identifier was 17 a MIN-based IMSI, in which case the MobileIdentificationNumber (populated with the 18 MIN derived from that IMSI) should be included. 19 20 i. Include for NDSS to indicate reason of MS registration or access. 21 22 j. Include to identify the functional entity sending the message. 23 k. Include if the system is NDSS capable. 24 25 l. Include if a change in the allocation status of a User Group is requested by the MS user. 26 27 m. Include to indicate the UZID indicated by the subscriber’s chosen PSID/RSID. 28 29 n. Include to identify the WIN capabilities supported. 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 QualificationRequest2 540 - 124 X.S0004-540-E v2.0

1 The QualificationRequest2 operation success is reported with a TCAP RETURN RESULT (LAST). 2 This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 3 4 QualificationRequest2 RETURN RESULT Parameters 5 6 Field Value Type Reference Notes 7 8 Identifier SET [NATIONAL 18] M 520-1.3.2.2 9 Length variable octets M 520-1.3.2.2 10 11 Contents 12 SystemMyTypeCode (VLR or HLR) M 2.263 13 14 AnalogRedirectRecord O 2.8 a 15 AuthorizationDenied O 2.19 b 16 17 AuthorizationPeriod O 2.20 c 18 CDMARedirectRecord O 2.63 d 19 20 ControlChannelMode O 2.88 e 21 DeniedAuthorizationPeriod O 2.100 f 22 23 Digits (Carrier) O 2.106 g 24 25 Digits (Destination) O 2.106 h, i 26 ElectronicSerialNumber O 2.113 j 27 28 IMSI O 2.130 k 29 MobileIdentificationNumber O 2.143 k 30 31 MSCID (HLR) O 2.154 l 32 Profile **Macro** O 2.185 m, n 33 34 RoamingIndication O 2.211 o 35 36 ServiceRedirectionInfo O 2.226 a, d 37 38 Notes: 39 a. Include for NDSS if HLR is to redirect the MS to an analog system. 40 41 b. If included, no other optional parameters except the DeniedAuthorizationPeriod parameter 42 shall be present. 43 44 c. Include if validation requested. 45 46 d. Include for NDSS if HLR is to redirect the MS to a CDMA system. 47 48 e. Include if the MS is Digital Control Channel capable, to indicate the last known access 49 mode. 50 f. May be included if the AuthorizationDenied parameter is present to indicate the interval 51 52 before re-authorization may be attempted. 53 g. Include if profile requested and preferred carrier is applicable and TransactionCapability 54 parameter is not received. 55 56 h. Include if profile requested and originations are restricted to selected leading digits of 57 directory numbers or of international E.164 numbers, (e.g., NPA-NXX or 58 NPA-NXX-XXXX for NANP) and TransactionCapability parameter is not received. 59 60 540 - 125 QualificationRequest2 X.S0004-540-E v2.0

i. Encode the Digits (Destination) as International if it is known that the serving MSC can 1 accept the digits in this format (e.g. the MSCIdentificationNumber parameter was received 2 in the INVOKE). 3 4 j. Include if available. 5 6 k. Include if available. At least one shall be included. 7 8 l. Include if authorization is not denied. 9 10 m. Include applicable parameter(s) (see 2.185). 11 n. The DMH_BillingDigits, MobileDirectoryNumber and RestrictionDigits parameters 12 13 should be encoded as International when loaded into the profile if it is know that the serving 14 MSC can accept them in this format (e.g. the MSCIdentificationNumber parameter was 15 received in the INVOKE). 16 17 o. Include for CDMA to support Enhanced Roaming Indicator. 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 QualificationRequest2 540 - 126 X.S0004-540-E v2.0

1 2.49 RandomVariableRequest 2 3 4 The RandomVariableRequest (RANDREQ) operation is used by the Serving MSC to request the value 5 of RAND from a Border MSC corresponding to the RANDC received from an MS. This operation 6 may be used if the value of RANDC received from an MS corresponds to a RAND value that may 7 be transmitted by a Border MSC which is transmitting the same SID as the Serving MSC. 8 9 The following table lists the valid combinations of invoking and responding FEs. 10 11 INVOKING FE RESPONDING FE 12 Case 1 Serving MSC Border MSC 13 14 15 The RandomVariableRequest operation is initiated with a TCAP INVOKE (LAST). This is carried 16 by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 17 18 RandomVariableRequest INVOKE Parameters Timer: RANDRT 19 20 Field Value Type Reference Notes 21 22 Identifier SET [NATIONAL 18] M 520-1.3.2.1 23 Length variable octets M 520-1.3.2.1 24 25 Contents 26 MSCID (Serving MSC) M 2.151 27 28 RANDC M 2.188 29 30 ServingCellID M 2.225 31 32 The RandomVariableRequest operation success is reported with a TCAP RETURN RESULT 33 (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 34 35 RandomVariableRequest RETURN RESULT Parameters 36 37 Field Value Type Reference Notes 38 39 Identifier SET [NATIONAL 18] M 520-1.3.2.2 40 Length variable octets M 520-1.3.2.2 41 42 Contents 43 RandomVariable M 2.189 a 44 45 RANDValidTime M 2.194 a 46 47 Notes: 48 49 a. Include only when the RANDC received in the INVOKE can be associated with a currently 50 or recently transmitted RAND. 51 52 53 54 55 56 57 58 59 60 540 - 127 RandomVariableRequest X.S0004-540-E v2.0

2.50 RedirectionDirective 1 2 3 The RedirectionDirective (REDDIR) operation is used during feature processing to direct the MSC 4 to forward the indicated call. 5 6 The following table lists the valid combinations of invoking and responding FEs. 7 8 INVOKING FE RESPONDING FE 9 Case 1 Adjunct MSC Originating MSC 10 11 12 The RedirectionDirective operation is initiated with a TCAP INVOKE (LAST). This is carried by a 13 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 14 15 RedirectionDirective INVOKE Parameters Timer: RDT 16 17 Field Value Type Reference Notes 18 19 Identifier SET [NATIONAL 18] M 520-1.3.2.1 20 Length variable octets M 520-1.3.2.1 21 22 Contents 23 BillingID (Originating) M 2.23 24 25 Digits (Destination) M 2.105 26 27 ElectronicSerialNumber M 2.112 28 SystemMyTypeCode (MSC) M 2.260 29 30 Digits (Carrier) O 2.105 a 31 DMH_AccountCodeDigits O 2.108 b 32 33 DMH_AlternateBillingDigits O 2.109 b 34 DMH_BillingDigits O 2.110 b 35 36 IMSI O 2.127 f 37 MobileIdentificationNumber O 2.140 f 38 39 MSCIdentificationNumber O 2.152 c 40 RedirectingNumberString O 2.199 d 41 42 RedirectingSubaddress O 2.201 d 43 44 SenderIdentificationNumber O 2.215 e 45 46 Notes: 47 a. Include if applicable. 48 49 b. Include if available for recording purposes (see DMH). 50 51 c. Include to identify the initiating MSC and to indicate that the MSC is capable of accepting 52 digits in the international format. 53 54 d. Optionally, include to override normal Originating MSC redirection number treatment. 55 56 57 58 59 60 RedirectionDirective 540 - 128 X.S0004-540-E v2.0

1 e. Include if different from the MSCIdentificationNumber to identify the functional entity 2 sending the message. 3 4 f. Include if available. At least one of these parameters should be present. 5 6 7 The RedirectionDirective operation success is reported with a TCAP RETURN RESULT (LAST). 8 This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 9 10 RedirectionDirective RETURN RESULT Parameters 11 12 Field Value Type Reference Notes 13 Identifier SET [NATIONAL 18] M 520-1.3.2.2 14 15 Length zero octets M 520-1.3.2.2 16 Contents 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 540 - 129 RedirectionDirective X.S0004-540-E v2.0

2.51 RedirectionRequest 1 2 3 The RedirectionRequest (REDREQ) operation is used by the Serving MSC to request redirection of 4 a call by the Originating MSC. 5 6 The following table lists the valid combinations of invoking and responding FEs. 7 8 INVOKING FE RESPONDING FE 9 Case 1 Serving MSC Originating MSC 10 11 12 The RedirectionRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a 13 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 14 15 RedirectionRequest INVOKE Parameters Timer: RDRT 16 17 Field Value Type Reference Notes 18 19 Identifier SET [NATIONAL 18] M 520-1.3.2.1 20 Length variable octets M 520-1.3.2.1 21 22 Contents 23 BillingID (Originating) M 2.23 24 25 ElectronicSerialNumber M 2.112 26 27 RedirectionReason M 2.202 28 AnnouncementList O 2.10 f, g 29 30 CDMAServiceOption O 2.66 d 31 CommandCode O 2.82 h 32 33 IMSI O 2.127 c 34 LegInformation O 2.133 a 35 36 MobileIdentificationNumber O 2.140 c 37 MSCIdentificationNumber O 2.152 b 38 39 PreferredLanguageIndicator O 2.179 g, i 40 TDMAServiceCode O 2.273 e 41 42 43 Notes: 44 a. Include if available (i.e., if provided in the associated RoutingRequest INVOKE 45 component). 46 47 b. Include to identify Serving MSC. 48 49 c. Include if available. At least one of these parameters should be present. 50 51 d. Include if CDMA channel is in use to allow distinctive forwarding based on Service Type. 52 53 e. Include if TDMA channel is in use to allow distinctive forwarding based on Service Type. 54 55 f. Include to direct the Originating MSC to provide tone or announcement. If present, 56 AnnouncementList is used (instead of the RedirectionReason) to generate Originating 57 System announcements to the calling party. 58 59 60 RedirectionRequest 540 - 130 X.S0004-540-E v2.0

1 g. Include only if available and CommandCode is also included. 2 3 h. Include to allow/deny the Originating System to initiate a TRANUMREQ towards the 4 HLR. Absence of CommandCode should default to allow TRANUMREQ. 5 6 i. Include to specify the called party’s preferred language. 7 8 The RedirectionRequest operation success is reported with a TCAP RETURN RESULT (LAST). 9 This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 10 11 12 RedirectionRequest RETURN RESULT Parameters 13 14 Field Value Type Reference Notes 15 Identifier SET [NATIONAL 18] M 520-1.3.2.2 16 17 Length zero octets M 520-1.3.2.2 18 Contents 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 540 - 131 RedirectionRequest X.S0004-540-E v2.0

2.52 RegistrationCancellation 1 2 3 The RegistrationCancellation (REGCAN) operation is used to report, to the responding FE, that a 4 previously registered MS is no longer in its serving area. The VLR may possess additional 5 information which allows it to determine that the RegistrationCancellation INVOKE is invalid, 6 thereby causing the VLR to deny the cancellation. 7 8 The following table lists the valid combinations of invoking and responding FEs. 9 10 INVOKING FE RESPONDING FE 11 12 Case 1 HLR prior Serving VLR 13 Case 2 prior Serving VLR prior Serving MSC 14 15 16 The RegistrationCancellation operation is initiated with a TCAP INVOKE (LAST). This is carried 17 by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 18 19 RegistrationCancellation INVOKE Parameters Timer: RCT 20 21 Field Value Type Reference Notes 22 23 Identifier SET [NATIONAL 18] M 520-1.3.2.1 24 Length variable octets M 520-1.3.2.1 25 26 Contents 27 ElectronicSerialNumber M 2.112 28 29 MSID M 2.153 d 30 CancellationType O 2.36 a 31 32 ControlChannelData O 2.86 b 33 ReceivedSignalQuality O 2.197 b 34 35 SenderIdentificationNumber O 2.215 c 36 SystemAccessData O 2.257 b 37 38 39 Notes: 40 a. Include if applicable. 41 42 b. Include if registration cancellation is the result of multiple access arbitration. 43 44 c. May be included to identify the functional entity sending the message. 45 46 d. The HLR includes the IMSI type of MSID if the IMSI was present in the last message 47 received from the Serving System; otherwise the HLR includes the 48 MobileIdentificationNumber type of MSID. The VLR includes the type of MSID last 49 received from the Serving MSC; this may not be the type of MSID received form the HLR. 50 51 52 53 54 55 56 57 58 59 60 RegistrationCancellation 540 - 132 X.S0004-540-E v2.0

1 The RegistrationCancellation operation success is reported with a TCAP RETURN RESULT 2 (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 3 4 5 RegistrationCancellation RETURN RESULT Parameters 6 Field Value Type Reference Notes 7 8 Identifier SET [NATIONAL 18] M 520-1.3.2.2 9 Length variable octets M 520-1.3.2.2 10 11 Contents 12 13 CallHistoryCount O 2.26 a 14 CancellationDenied O 2.35 b 15 16 ControlChannelData O 2.86 b 17 ReceivedSignalQuality O 2.197 b 18 19 SMS_MessageWaitingIndicator O 2.238 c 20 SystemAccessData O 2.257 b 21 22 Notes: 23 24 a. Include if SSD is shared. 25 26 b. Include if registration cancellation is denied. 27 28 c. Include to indicate that an SMS message is pending delivery. 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 540 - 133 RegistrationCancellation X.S0004-540-E v2.0

2.53 RegistrationNotification 1 2 3 The RegistrationNotification (REGNOT) operation is used to report the location of an MS and, 4 optionally, to (a) validate the MS or (b) validate the MS and obtain its profile information. It is also 5 used for delivering the Serving MSC’s routing address to the desired OTAF in support of TDMA 6 OTASP. 7 8 The following table lists the valid combinations of invoking and responding FEs. 9 10 INVOKING FE RESPONDING FE 11 Case 1 Serving (or Bordering) MSC Serving (or Bordering) VLR 12 13 Case 2 Serving (or Bordering) VLR HLR 14 Case 3 Serving VLR OTAF 15 16 (Note 1) 17 18 Note: 19 1. Case 3 is only applicable to TDMA OTASP. 20 21 The RegistrationNotification operation is initiated with a TCAP INVOKE (LAST). This is carried 22 by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 23 24 25 RegistrationNotification INVOKE Parameters Timer: RNT 26 Field Value Type Reference Notes 27 28 Identifier SET [NATIONAL 18] M 520-1.3.2.1 29 30 Length variable octets M 520-1.3.2.1 31 Contents 32 33 ElectronicSerialNumber M 2.112 34 MSID M 2.153 l 35 36 MSCID (Serving MSC) M 2.151 37 QualificationInformationCode M 2.187 38 39 SystemMyTypeCode (Serving MSC or VLR) M 2.260 40 AvailabilityType O 2.20 a 41 42 BorderCellAccess O 2.24 b 43 CDMANetworkIdentification (Serving) O 2.57 q 44 45 ControlChannelData O 2.86 b 46 47 ControlChannelMode O 2.87 n, r 48 ExtendedMSCID (VLR) O 2.116 c 49 50 LocationAreaID O 2.135 d 51 MSC_Address O 2.150 m 52 53 MSCIdentificationNumber (Serving MSC) O 2.152 t 54 PC_SSN (Serving MSC or VLR) O 2.176 e 55 56 ReceivedSignalQuality O 2.197 b 57 ReportType O 2.204 f 58 59 60 RegistrationNotification 540 - 134 X.S0004-540-E v2.0

1 SenderIdentificationNumber O 2.215 g 2 3 ServiceRedirectionCause O 2.222 s 4 SMS_Address O 2.232 h 5 6 SMS_MessageWaitingIndicator O 2.238 i 7 8 SystemAccessData O 2.257 b 9 SystemAccessType O 2.258 j 10 11 SystemCapabilities O 2.259 k 12 TerminalType O 2.278 j 13 14 TransactionCapability O 2.285 j 15 UserGroup O 2.293 o 16 17 WINCapability O 2.299 p 18 19 Notes: 20 21 a. Include when MS is predictably unavailable for Call Delivery (e.g., slotted mode or sleep 22 mode). 23 24 b. Include if access occurred in a border cell (based on internal algorithms). 25 c. Included by VLR if its MSCID is different than the MSC’s MSCID. 26 27 d. May be included from MSC to VLR. 28 29 e. Include to override lower layer addressing if the receiving VLR or HLR is known to be in 30 the same national SS7 network. 31 32 f. Include if authentication parameters were requested by the Serving MSC (AUTH=1 in the 33 Overhead Message Train) but were not received from the MS for the system access. 34 35 g. May be included to identify message sender. 36 37 h. Include to indicate that the Serving MSC supports Short Message Service, or, for TDMA, 38 that the Serving MSC supports teleservice message delivery (e.g., CMT, OATS). 39 40 i. Include if the MS was previously registered with this VLR, the MS is registering to a new 41 serving MSC that does not support SMS, and an SMS message is pending delivery in the 42 previous serving system. This is only used between a VLR and an HLR. 43 44 j. Include on IS-41-C and later. 45 k. Include if the system is authentication capable (including voice channel authentication only 46 systems where all flags are zero). 47 48 l. Include the identifier with which the MS last accessed the system, unless that identifier was 49 a MIN-based IMSI, in which case the MobileIdentificationNumber (populated with the 50 MIN derived from that IMSI) should be included. 51 52 m. Include for CDMA OTA, if the Serving MSC does not support SMS but does support any 53 other service (e.g., CDMA OTAPA) which needs to convey the current routing address of 54 the Serving MSC. 55 56 n. Include if the MS is Digital Control Channel capable to indicate whether an analog or 57 digital control channel was used by the MS in this access. 58 59 60 540 - 135 RegistrationNotification X.S0004-540-E v2.0

o. Include if a change in allocation status of a User Group is requested by the MS user. 1 2 p. Include to identify the WIN capabilities supported. 3 4 q. Include for NDSS to identify the serving network. 5 6 r. Include for NDSS to identify the operating mode of the MS. 7 s. Include for NDSS to indicate reason of MS registration or access. 8 9 t. Include to identify the initiating MSC and to indicate that the MSC is capable of accepting 10 digits in the international format. 11 12 13 The RegistrationNotification operation success is reported with a TCAP RETURN RESULT 14 (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 15 16 RegistrationNotification RETURN RESULT Parameters 17 18 Field Value Type Reference Notes 19 20 Identifier SET [NATIONAL 18] M 520-1.3.2.2 21 Length variable octets M 520-1.3.2.2 22 23 Contents 24 SystemMyTypeCode (VLR or HLR) M 2.260 25 26 AnalogRedirectRecord O 2.8 a 27 28 AuthorizationDenied O 2.18 b 29 AuthorizationPeriod O 2.19 c 30 31 CDMARedirectRecord O 2.62 d 32 ControlChannelData O 2.86 e 33 34 DeniedAuthorizationPeriod O 2.99 f 35 Digits (Carrier) O 2.105 g 36 37 Digits (Destination) O 2.105 h, i 38 MINExtension O 2.148 j 39 40 MSCID (HLR) O 2.151 k 41 MSID O 2.153 l 42 43 Profile **Macro** O 2.182 m, n 44 45 ReceivedSignalQuality O 2.197 e 46 RoamingIndication O 2.208 o 47 48 SenderIdentificationNumber O 2.215 p 49 ServiceRedirectionInfo O 2.223 a, d 50 51 SMS_MessageWaitingIndicator O 2.238 q 52 SystemAccessData O 2.257 e 53 54 Notes: 55 a. Include for NDSS if HLR is to redirect the MS to an analog system. 56 b. If included, only the ControlChannelData, DeniedAuthorizationPeriod, Received- 57 58 SignalQuality, and SystemAccessData optional parameters have significance. 59 60 RegistrationNotification 540 - 136 X.S0004-540-E v2.0

1 c. Include if validation requested. 2 d. Include for NDSS if HLR is to redirect the MS to a CDMA system. 3 4 e. Include if AuthorizationDenied parameter is included with value of Multiple Access. 5 f. May be included if the AuthorizationDenied parameter is present to indicate the in- 6 terval before re-authorization may be attempted. 7 8 g. Include if the profile is requested, the preferred carrier is applicable, and the Carrier- 9 Digits parameter is not included in the Profile macro. 10 h. Include if profile requested and originations are restricted to selected leading digits 11 of directory numbers or of international E.164 numbers, (e.g., NPA-NXX or 12 NPA-NXX-XXXX for NANP) and TransactionCapability parameter is not re- 13 ceived. 14 15 i. Encode the Digits (Destination) as International if it is known that the serving MSC 16 can accept the digits in this format (e.g., the MSCIdentificationNumber parameter 17 was received in the INVOKE). 18 j. Include if available and the MX field in the TransactionCapability parameter in the 19 corresponding REGNOT was set to 1. 20 21 k. Include on IS-41-C and later and authorization is not denied. 22 l. Include MIN if available and IMSI was included in INVOKE. Include IMSI if avail- 23 able and MIN was included in INVOKE. 24 25 m. Include applicable parameter(s) (see 2.182). 26 n. The DMH_BillingDigits, MobileDirectoryNumber and RestrictionDigits parame- 27 ters should be encoded as International when loaded into the profile if it is known 28 that the serving MSC can accept them in this format (e.g., the MSCIdentification- 29 Number parameter was received in the INVOKE). 30 31 o. Include for CDMA to support Enhanced Roaming Indicator. 32 p. May be included to identify the functional entity sending the message. 33 q. Include to indicate that an SMS message is pending delivery. 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 540 - 137 RegistrationNotification X.S0004-540-E v2.0

2.54 Release 1 2 3 The Release (RELEASE) operation is used to request the release of paging resources associated to 4 an MS. 5 6 The following table lists the valid combinations of invoking and responding FEs. 7 8 INVOKING FE RESPONDING FE 9 Case 1 MSC MSC 10 11 The Release operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 12 QUERY WITH PERMISION package. The Parameter Set is encoded as follows: 13 14 15 Release INVOKE Parameters Timer: RELT 16 17 Field Value Type Reference Notes 18 Identifier SET [NATIONAL 18] M 520-1.3.2.1 19 20 Length variable octets M 520-1.3.2.1 21 Contents 22 23 IMSI O 2.127 a 24 MobileIdentificationNumber O 2.140 a 25 26 Notes: 27 28 a. Include if available. At least one of these parameters should be present 29 30 31 The Release operation success is reported with a TCAP RETURN RESULT (LAST). This is carried 32 by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 33 34 Release RETURN RESULT Parameters 35 36 Field Value Type Reference Notes 37 38 Identifier SET [NATIONAL 18] M 520-1.3.2.2 39 Length variable octets M 520-1.3.2.2 40 41 Contents 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 Release 540 - 138 X.S0004-540-E v2.0

1 2.55 RemoteUserInteractionDirective 2 3 4 The RemoteUserInteractionDirective (RUIDIR) operation is used by the HLR, SCP or SN to 5 remotely direct the operation of an MSC (or other functional entity) which provides user interaction; 6 i.e., the RUI-MSC. The RUI-MSC may be an Originating MSC, a Serving MSC or some other 7 functional entity capable of user interaction. The RemoteUserInteractionDirective may be passed 8 through an intervening HLR, SCP or SN when a ServiceRequest has been used to invoke service 9 logic on another network element. 10 11 The following table lists the valid combinations of invoking and responding FEs. 12 13 INVOKING FE RESPONDING FE 14 15 Case 1 HLR or SCP or SN RUI-MSC 16 Case 2 SCP or SN HLR or SCP or SN 17 18 Case 3 HLR SCP or SN 19 20 The RemoteUserInteractionDirective operation is initiated with a TCAP INVOKE (LAST). This is 21 carried by a TCAP CONVERSATION WITHOUT PERMISSION package. The Parameter Set is 22 encoded as follows: 23 24 25 RemoteUserInteractionDirective INVOKE Parameters Timer: RUDT 26 27 Field Value Type Reference Notes 28 Identifier SET [NATIONAL 18] M 520-1.3.2.1 29 30 Length variable octets M 520-1.3.2.1 31 Contents 32 33 AnnouncementList M 2.10 34 DigitCollectionControl M 2.104 35 36 37 The RemoteUserInteractionDirective operation success is reported with a TCAP RETURN 38 RESULT (LAST). This is carried by a TCAP CONVERSATION WITH PERMISSION package. 39 The Parameter Set is encoded as follows: 40 41 RemoteUserInteractionDirective RETURN RESULT Parameters 42 43 Field Value Type Reference Notes 44 Identifier SET [NATIONAL 18] M 520-1.3.2.2 45 46 Length variable octets M 520-1.3.2.2 47 48 Contents 49 Digits (Dialed) O 2.105 a 50 51 Notes: 52 53 a. Include if call has not been abandoned. The number of digits returned may be zero, 54 implying that the user did not dial before time-out. 55 56 57 58 59 60 540 - 139 RemoteUserInteractionDirective X.S0004-540-E v2.0

2.56 ResetCircuit 1 2 3 The ResetCircuit (RESETCKT) operation is used by an MSC to restore information about circuit 4 conditions which has been lost due to, for example, a restart. It may also be used to when placing 5 circuits into service. 6 7 The following table lists the valid combinations of invoking and responding FEs. 8 9 INVOKING FE RESPONDING FE 10 11 Case 1 MSC MSC 12 13 The ResetCircuit operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 14 QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 15 16 17 ResetCircuit INVOKE Parameters Timer: RSTT 18 Field Value Type Reference Notes 19 20 Identifier SET [NATIONAL 18] M 520-1.3.2.1 21 Length variable octets M 520-1.3.2.1 22 23 Contents 24 25 InterMSCCircuitID M 2.129 26 27 The ResetCircuit operation success is reported with a TCAP RETURN RESULT (LAST). This is 28 carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 29 30 ResetCircuit RETURN RESULT Parameters 31 32 Field Value Type Reference Notes 33 34 Identifier SET [NATIONAL 18] M 520-1.3.2.2 35 Length variable octets M 520-1.3.2.2 36 37 Contents 38 TrunkStatus M 2.290 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 ResetCircuit 540 - 140 X.S0004-540-E v2.0

1 2.57 ResetTimer 2 3 4 The ResetTimer (RESETTIMER) operation is used by the SCF to initialize and start an operation 5 timer and avoid the timeout that would otherwise occur. 6 7 The following table lists the valid invoking FEs. 8 INVOKING FE RESPONDING FE 9 10 Case 1 HLR or SCP or SN MSC 11 12 Case 2 HLR SCP or SN 13 Case 3 SCP or SN HLR or SCP or SN 14 15 The ResetTimer operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 16 CONVERSATION WITHOUT PERMISSION package. The Parameter Set is encoded as follows: 17 18 19 ResetTimer INVOKE Parameters Timer: (note a) 20 Field Value Type Reference Notes 21 22 Identifier SET [NATIONAL 18] M 520-1.3.2.1 23 24 Length variable octets M 520-1.3.2.1 25 Contents 26 27 28 Notes: 29 30 a. When the SSF network entity (MSC) receives the ResetTimer INVOKE, it initializes and 31 starts the active Service Switching Function Timer (SSFT). When an intervening SCF 32 network entity receives the ResetTimer INVOKE, it sends a ResetTimer INVOKE to the 33 MSC, and initializes and starts the active Service Control Function Timer (SCFT). 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 540 - 141 ResetTimer X.S0004-540-E v2.0

2.58 RoutingRequest 1 2 3 The RoutingRequest (ROUTREQ) operation is used to inquire as to the preferred method of routing 4 a pending call to the identified MS. 5 6 The following table lists the valid combinations of invoking and responding FEs. 7 8 INVOKING FE RESPONDING FE 9 Case 1 HLR Serving VLR 10 11 Case 2 Serving VLR Serving MSC 12 Case 3 HLR Serving MSC 13 14 (Note 1) 15 16 Note: 17 1. Case 3 above is termed a ‘direct‘ RoutingRequest operation, since it occurs 18 directly between the HLR and the Serving MSC without the involvement of the 19 VLR (e.g., voice mail delivery, voice mail storage, special dialogue). 20 21 The RoutingRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a 22 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 23 24 25 RoutingRequest INVOKE Parameters Timer: RRT 26 Field Value Type Reference Notes 27 28 Identifier SET [NATIONAL 18] M 520-1.3.2.1 29 30 Length variable octets M 520-1.3.2.1 31 Contents 32 33 BillingID (Originating) M 2.23 a 34 ElectronicSerialNumber M 2.112 35 36 MSCID (Originating MSC) M 2.151 37 SystemMyTypeCode (Originating MSC) M 2.260 38 39 AlertCode O 2.4 b 40 CallingPartyName O 2.29 x 41 42 CallingPartyNumberDigits1 O 2.30 c, aa 43 44 CallingPartyNumberDigits2 O 2.31 c, aa 45 CallingPartyNumberString1 O 2.32 c, aa 46 47 CallingPartyNumberString2 O 2.33 c, aa 48 CallingPartySubaddress O 2.34 c 49 50 ControlChannelMode O 2.87 s 51 CDMAServiceOption O 2.66 v 52 53 DestinationDigits O 2.103 d, e 54 DisplayText O 2.106 c, ac 55 56 DisplayText2 O 2.107 c, ac 57 DMH_AccountCodeDigits O 2.108 f 58 59 60 RoutingRequest 540 - 142 X.S0004-540-E v2.0

1 DMH_AlternateBillingDigits O 2.109 f 2 3 DMH_BillingDigits O 2.110 f 4 LegInformation O 2.133 g 5 6 LocationAreaID O 2.135 f, h 7 8 MobileDirectoryNumber O 2.139 f 9 MSID O 2.153 t, r 10 11 MSCIdentificationNumber O 2.152 i 12 NoAnswerTime O 2.165 j 13 14 OneTimeFeatureIndicator O 2.167 k 15 PC_SSN (Originating MSC) O 2.176 l 16 17 PilotBillingID O 2.177 m 18 PilotNumber O 2.178 m 19 20 RedirectingNumberDigits O 2.198 c, aa 21 RedirectingNumberString O 2.199 c, aa 22 23 RedirectingPartyName O 2.200 z 24 25 RedirectingSubaddress O 2.201 c 26 SenderIdentificationNumber O 2.215 n 27 28 TDMAServiceCode O 2.273 w 29 TerminationTreatment O 2.282 o 30 31 TerminationTriggers O 2.283 f, ad 32 TransactionCapability (Originating MSC) O 2.285 ab 33 34 TriggerAddressList O 2.286 y 35 UserGroup O 2.293 u 36 37 VoiceMailboxNumber O 2.295 p 38 VoiceMailboxPIN O 2.296 q 39 40 Notes: 41 42 a. Required to identify originating call. 43 44 b. Include to specify special alerting treatment. 45 46 c. Include if related feature is active. 47 48 d. Optionally include if TerminationTreatment parameter value is Dialogue, to select a 49 dialogue or to provide information to a dialogue. 50 51 e. Optionally include if TerminationTreatment parameter value is VoiceMailRetrieval or 52 VoiceMailStorage to select the voice mail system. 53 54 f. Include if available and if TerminationTreatment parameter value is MS termination. 55 g. Include if TerminationTreatment parameter value is MS termination and this is a multileg 56 call (e.g., an FA call). 57 58 h. May be included from VLR to MSC-V. Usage is not defined from HLR to VLR. 59 60 540 - 143 RoutingRequest X.S0004-540-E v2.0

i. Include to identify Originating MSC. 1 2 j. Include to inform the serving system of the recommended no-answer time-out. 3 4 k. Include if modification to normal feature processing is required for call in progress. 5 6 l. Include if available (e.g., from received parameter or lower layers) for subsequent call 7 redirection. 8 9 m. Include on a multi-leg call. 10 n. May be included to identify the functional entity sending the message. 11 12 o. Include to differentiate termination types, defaulting to value MS termination. 13 14 p. Include if the TerminationTreatment parameter value is VoiceMailRetrieval or 15 VoiceMailStorage and the mailbox is not the MobileIdentificationNumber. 16 17 q. Optional, if the TerminationTreatment parameter value is VoiceMailRetrieval or 18 VoiceMailStorage. 19 20 r. When this message is used in accessing a feature at an adjunct MSC (e.g., for voice message 21 retrieval), the HLR includes the type of MSID appropriate to the MS and the feature being 22 accessed. Otherwise the HLR includes the IMSI type of MSID if the IMSI was present in 23 the last message received from the Serving System and it includes the 24 MobileIdentificationNumber type of MSID when the IMSI was not present in the last 25 message received from the Serving System. The VLR includes the type of MSID last 26 received from the Serving MSC; this may not be the type of MSID received from the HLR. 27 28 s. Include if the MS is Digital Channel Control capable to indicate which control channel 29 mode shall be use to page the MS. 30 31 t. Required unless UserGroup parameter is included. 32 33 u. Include for user group alerting. If this parameter is included do not include 34 MobileIdentificationNumber. 35 36 v. Include to identify requested CDMA service information. 37 38 w. Include to identify requested TDMA service information. 39 x. Include if available when a Calling Party Number String parameter has been included. 40 41 y. Include if the WIN trigger address list information is to be modified for this call. 42 43 z. Include if available when a RedirectingNumberString parameter has been included. 44 45 aa. The digits form of this information is included for service logic invocations from the 46 Serving MSC. The string form of this information is included for presentation to the MS. 47 48 ab. Include to inform the serving system of the Originating MSC capabilities. 49 50 ac. Include only one of these mutually exclusive parameters. 51 ad. Include if termination triggers are to be modified for this call. 52 53 54 55 56 57 58 59 60 RoutingRequest 540 - 144 X.S0004-540-E v2.0

1 The RoutingRequest operation success is reported with a TCAP RETURN RESULT (LAST). This 2 is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 3 4 5 RoutingRequest RETURN RESULT Parameters 6 Field Value Type Reference Notes 7 8 Identifier SET [NATIONAL 18] M 520-1.3.2.2 9 Length variable octets M 520-1.3.2.2 10 11 Contents 12 13 MSCID (Serving) M 2.151 14 AccessDeniedReason O 2.1 a 15 16 BillingID (Anchor) O 2.23 b 17 CDMAServiceOption O 2.66 g 18 19 ConditionallyDeniedReason O 2.83 c 20 Digits (Destination) O 2.105 d 21 22 MSCIdentificationNumber O 2.152 e 23 PC_SSN (Serving MSC) O 2.176 f 24 25 TDMAServiceCode O 2.273 h 26 27 Notes: 28 29 a. Include if access may be denied. 30 31 b. Include for recording purposes (see DMH). 32 33 c. Include if Call Waiting is possible. 34 d. Include to carry a Temporary Local Directory Number (TLDN). 35 36 e. Include to identify the Serving MSC. 37 38 f. Include for possible screening by the Originating MSC for call redirection attempts on this 39 leg. 40 41 g. Include to identify the accepted CDMA service information. 42 43 h. Include to identify the accepted TDMA service information. 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 540 - 145 RoutingRequest X.S0004-540-E v2.0

2.59 Search 1 2 3 The Search (SEARCH) operation is used by a Service Control Function (SCF) to request data items 4 stored in a remote Service Data Function (SDF). 5 6 The following table lists the valid combinations of invoking and responding FEs. 7 8 INVOKING FE RESPONDING FE 9 Case 1 SCP or SN SCP or SN 10 11 Case 2 SCP or SN HLR 12 Case 3 HLR SCP or SN 13 14 The Search operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY 15 WITH PERMISSION package. The Parameter Set is encoded as follows: 16 17 18 Search INVOKE Parameters Timer: ST 19 20 Field Value Type Reference Notes 21 Identifier SET [NATIONAL 18] M 520-1.3.2.1 22 23 Length variable octets M 520-1.3.2.1 24 Contents 25 26 DatabaseKey M 2.91 a 27 ServiceDataAccessElementList M 2.217 b 28 29 30 Notes: 31 a. The parameter value is determined by bi-lateral negotiation between sender and receiver to 32 be interpreted as a database key. For example, possible values might be MDN, MIN or a 33 34 proprietary database key. 35 b. For this use of the ServiceDataAccessElementList parameter, the optional Change and 36 DataValue parameters are not included in any of the individual DataAccessElements in the 37 38 DataAccessElementList component of any of the ServiceDataAccessElements. For this 39 use, only the mandatory DataID parameter is included in those DataAccessElements. 40 41 The Search operation success is reported with a TCAP RETURN RESULT (LAST). This is carried 42 by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 43 44 45 Search RETURN RESULT Parameters 46 Field Value Type Reference Notes 47 48 Identifier SET [NATIONAL 18] M 520-1.3.2.2 49 50 Length variable octets M 520-1.3.2.2 51 Contents 52 53 ServiceDataAccessElementList M 2.217 a 54 55 56 57 58 59 60 Search 540 - 146 X.S0004-540-E v2.0

1 Notes: 2 3 a. For this use of the ServiceDataAccessElementList parameter, the optional Change 4 parameter is not included in any of the individual DataAccessElements in the 5 DataAccessElementList component of any ServiceDataAccessElement. For this use, the 6 optional DataValue parameter may be present in any of those DataAccessElements. 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 540 - 147 Search X.S0004-540-E v2.0

2.60 SeizeResource 1 2 3 The SeizeResource (SEIZERES) operation is used by the SCF to request an SRF resource required 4 by the SCF for service logic execution. 5 6 The following table lists the valid combinations of invoking and responding FEs. 7 8 INVOKING FE RESPONDING FE 9 Case 1 HLR IP or SN 10 11 Case 2 SCP IP or SN 12 Case 3 SN IP or SN 13 14 The SeizeResource operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 15 QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 16 17 18 SeizeResource INVOKE Parameters Timer: SZRT 19 20 Field Value Type Reference Notes 21 Identifier SET [NATIONAL 18] M 520-1.3.2.1 22 23 Length variable octets M 520-1.3.2.1 24 Contents 25 26 PreferredLanguageIndicator O 2.179 27 PrivateSpecializedResource O 2.181 a 28 29 SpecializedResource O 2.250 a 30 31 Notes: 32 33 a. At least one of these parameters must be included. 34 35 The SeizeResource operation success is reported with a TCAP RETURN RESULT (LAST). This is 36 37 carried by a TCAP CONVERSATION WITHOUT PERMISSION package. The Parameter Set is 38 encoded as follows: 39 40 SeizeResource RETURN RESULT Parameters 41 42 Field Value Type Reference Notes 43 Identifier SET [NATIONAL 18] M 520-1.3.2.2 44 45 Length variable octets M 520-1.3.2.2 46 47 Contents 48 DestinationDigits M 2.103 a 49 50 Notes: 51 52 a. Specialized resource address. 53 54 55 56 57 58 59 60 SeizeResource 540 - 148 X.S0004-540-E v2.0

1 2.61 ServiceRequest 2 3 4 The ServiceRequest (SERVREQ) operation is used by service logic to invoke specific service logic 5 execution on another functional entity (FE) containing the service logic for the requested services. 6 7 The following table lists the valid combinations of invoking and responding FEs. 8 INVOKING FE RESPONDING FE 9 10 Case 1 HLR SCP or SN 11 12 Case 2 SCP or SN SCP or SN 13 Case 3 SCP or SN HLR 14 15 The ServiceRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 16 QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 17 18 19 ServiceRequest INVOKE Parameters Timer: SVRT 20 Field Value Type Reference Notes 21 22 Identifier SET [NATIONAL 18] M 520-1.3.2.1 23 24 Length variable octets M 520-1.3.2.1 25 Contents 26 27 ServiceID M 2.220 28 AccessDeniedReason O 2.1 c, d 29 30 AvailabilityType O 2.20 c, e 31 BillingID O 2.23 a, f 32 33 CallingPartyName O 2.29 a 34 CallingPartyNumberDigits1 O 2.30 a 35 36 CallingPartyNumberDigits2 O 2.31 b 37 38 CallingPartySubaddress O 2.34 a 39 ConditionallyDeniedReason O 2.83 c, d 40 41 DataAccessElementList O 2.90 c 42 Digits (Dialed) O 2.105 a 43 44 GroupInformation O 2.124 c 45 IMSI O 2.127 p 46 47 LegInformation O 2.133 c 48 LocationAreaID O 2.135 c 49 50 MobileDirectoryNumber O 2.139 c, g 51 MobileIdentificaitonNumber O 2.140 p 52 53 MSCID (Invoking) O 2.151 c, h 54 55 MSCIdentificationNumber (Invoking) O 2.152 c, i 56 PC_SSN O 2.176 i, j 57 58 PilotBillingID O 2.177 c 59 60 540 - 149 ServiceRequest X.S0004-540-E v2.0

1 PilotNumber O 2.178 c 2 PreferredLanguageIndicator O 2.179 a 3 4 RedirectingPartyName O 2.200 a 5 RedirectingNumberDigits O 2.198 a 6 7 RedirectingSubaddress O 2.201 a 8 RedirectionReason O 2.202 a, c 9 10 SenderIdentificationNumber O 2.215 k 11 ServingCellID O 2.225 c 12 13 SystemMyTypeCode O 2.260 l 14 TerminationAccessType O 2.279 c 15 16 TimeDateOffset O 2.284 c 17 18 TransactionCapability O 2.285 m 19 TriggerType O 2.289 n 20 21 WINCapability O 2.299 o 22 23 Notes: 24 a. Include if available. 25 26 b. Include if user provided, passed screening calling party number is available. 27 28 c. Include if applicable. 29 30 d. Include if a RoutingRequest operation was completed prior to the ServiceRequest 31 operation, and access was denied. 32 33 e. Include when MS is predictably unavailable for Call Delivery (e.g., slotted mode or sleep 34 mode). 35 36 f. Include to correlate service usage with call instance. 37 g. Include if available for recording purposes (see DMH) 38 39 h. Include to identify invoking MSC. 40 41 i. Include if SS7 is used. 42 43 j. Not for international applications. 44 45 k. Include to identify invoking FE. 46 47 l. Include to indicate the vendor type of the invoking FE. 48 m. Include to indicate the capabilities of the MSC that the invoking FE (e.g., HLR, SCP, SN) 49 chooses to convey to the NE (e.g., SCP, SN) with the service logic for the requested 50 51 services. 52 n. Include to identify the trigger encountered by the MSC. 53 54 o. Include to indicate the WIN capabilities supported. 55 56 p. Include as the service key, if applicable 57 58 59 60 ServiceRequest 540 - 150 X.S0004-540-E v2.0

1 The ServiceRequest operation success is reported with a TCAP RETURN RESULT (LAST). This 2 is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 3 4 5 ServiceRequest RETURN RESULT Parameters 6 Field Value Type Reference Notes 7 8 Identifier SET [NATIONAL 18] M 520-1.3.2.2 9 Length variable octets M 520-1.3.2.2 10 11 Contents 12 13 AccessDeniedReason O 2.1 c 14 ActionCode O 2.2 d 15 16 AlertCode O 2.4 e 17 AnnouncementList O 2.10 f 18 19 CallingPartyName O 2.29 a 20 CallingPartyNumberString1 O 2.32 a 21 22 CallingPartyNumberString2 O 2.33 a 23 CallingPartySubaddress O 2.34 a 24 25 CarrierDigits O 2.37 a 26 Digits (Dialed) O 2.105 g 27 28 DisplayText O 2.106 a, b 29 30 DisplayText2 O 2.107 a, b 31 DMH_AccountCodeDigits O 2.108 a 32 33 DMH_AlternateBillingDigits O 2.109 a 34 DMH_BillingDigits O 2.110 a 35 36 DMH_RedirectionIndicator O 2.111 a 37 GroupInformation O 2.124 a 38 39 MobileDirectoryNumber O 2.139 a 40 NoAnswerTime O 2.165 a 41 42 RedirectingNumberDigits O 2.198 a 43 RedirectingNumberString O 2.199 a 44 45 RedirectingPartyName O 2.200 a 46 47 RedirectingSubaddress O 2.201 a 48 RoutingDigits O 2.209 a 49 50 TerminationList O 2.280 h 51 52 Notes: 53 54 a. Include if applicable. 55 b. Include only one of these mutually exclusive parameters 56 57 c. Include if service logic determines access to the MS is denied. 58 59 d. Include if action to be performed is not implied through presence of other parameters. 60 540 - 151 ServiceRequest X.S0004-540-E v2.0

e. Include to specify special alerting treatment. 1 2 f. Include if one or more tones or announcements are to be applied to the MS. 3 4 g. Include if digits remain to be translated by the MSC. 5 6 h. Include if call routing is required. 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 ServiceRequest 540 - 152 X.S0004-540-E v2.0

1 2.62 SMSDeliveryBackward 2 3 4 The SMSDeliveryBackward (SMDBACK) operation is a general purpose operation that is used to 5 convey an MS-originated short message or in general any other information or encapsulated data to 6 the Anchor MSC after handoff. 7 8 The following table lists the valid combinations of invoking and responding FEs. 9 10 INVOKING FE RESPONDING FE 11 Case 1 Serving MSC Anchor MSC 12 13 Case 2 Serving MSC Tandem MSC 14 Case 3 Tandem MSC Tandem MSC 15 16 Case 4 Tandem MSC Anchor MSC 17 18 The SMSDeliveryBackward operation is initiated with a TCAP INVOKE (LAST). This is carried 19 by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 20 21 SMSDeliveryBackward INVOKE Parameters Timer: SBT 22 23 Field Value Type Reference Notes 24 25 Identifier SET [NATIONAL 18] M 520-1.3.2.1 26 Length variable octets M 520-1.3.2.1 27 28 Contents 29 InterMSCCircuitID M 2.129 30 31 MSID M 2.153 h 32 33 SMS_BearerData M 2.233 34 SMS_TeleserviceIdentifier M 2.246 35 36 ElectronicSerialNumber O 2.112 a 37 SMS_ChargeIndicator O 2.235 b 38 39 SMS_DestinationAddress O 2.236 c 40 SMS_OriginalDestinationAddress O 2.240 d 41 42 SMS_OriginalDestinationSubaddress O 2.241 a 43 SMS_OriginalOriginatingAddress O 2.242 e 44 45 SMS_OriginalOriginatingSubaddress O 2.243 a 46 SMS_TransactionID O 2.248 g 47 48 49 Notes: 50 a. Include if applicable. 51 52 b. Include if applicable. If not received, charge message originator. 53 54 c. Include if an MC address is specified by the originating SME. 55 56 d. Include to identify the SME to which the short message is destined (e.g., the MDN, for 57 termination to an MS-based SME). 58 59 60 540 - 153 SMSDeliveryBackward X.S0004-540-E v2.0

e. Include to identify the SME from which the short message originated (e.g., the MDN, if 1 originated by an MS-based SME). 2 3 f. Intentionally left for future modifications. 4 5 g. Include if TDMA to identify an MS based SMS originating SME. 6 7 h. Include the identifier with which the MS last accessed the system, unless that identifier was 8 a MIN-based IMSI, in which case the MobileIdentificationNumber (populated with the 9 MIN derived from that IMSI) should be included. 10 11 The SMSDeliveryBackward operation success is reported with a TCAP RETURN RESULT 12 13 (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 14 15 SMSDeliveryBackward RETURN RESULT Parameters 16 17 Field Value Type Reference Notes 18 Identifier SET [NATIONAL 18] M 520-1.3.2.2 19 20 Length variable octets M 520-1.3.2.2 21 Contents 22 23 SMS_BearerData O 2.233 a 24 25 SMS_CauseCode O 2.234 b 26 SMS_TransactionID O 2.248 c 27 28 Notes: 29 30 a. Include for positive acknowledgments, when applicable. 31 32 b. Include for all negative acknowledgments. 33 34 c. Include if TDMA to identify an MS based SMS originating SME. 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 SMSDeliveryBackward 540 - 154 X.S0004-540-E v2.0

1 2.63 SMSDeliveryForward 2 3 4 The SMSDeliveryForward (SMDFWD) operation is a general purpose operation that is used to convey 5 an MS-terminated short message or in general any other information or encapsulated data to the 6 Serving MSC after handoff. 7 8 The following table lists the valid combinations of invoking and responding FEs. 9 10 INVOKING FE RESPONDING FE 11 Case 1 Anchor MSC Serving MSC 12 13 Case 2 Anchor MSC Tandem MSC 14 Case 3 Tandem MSC Tandem MSC 15 16 Case 4 Tandem MSC Serving MSC 17 18 The SMSDeliveryForward operation is initiated with a TCAP INVOKE (LAST). This is carried by 19 a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 20 21 SMSDeliveryForward INVOKE Parameters Timer: SFT 22 23 Field Value Type Reference Notes 24 25 Identifier SET [NATIONAL 18] M 520-1.3.2.1 26 Length variable octets M 520-1.3.2.1 27 28 Contents 29 InterMSCCircuitID M 2.129 30 31 SMS_BearerData M 2.233 32 33 SMS_TeleserviceIdentifier M 2.246 34 ElectronicSerialNumber O 2.112 b 35 36 IMSI O 2.127 h 37 MobileIdentificationNumber O 2.140 a, h 38 39 SMS_ChargeIndicator O 2.235 c 40 SMS_OriginalDestinationAddress O 2.240 e 41 42 SMS_OriginalDestinationSubaddress O 2.241 b 43 SMS_OriginalOriginatingAddress O 2.242 f 44 45 SMS_OriginalOriginatingSubaddress O 2.243 b 46 SMS_OriginatingAddress O 2.244 g 47 48 49 Notes: 50 a. Include to identify the destination MS. 51 52 b. Include if applicable. 53 54 c. Include if applicable. If not received, charge message originator. 55 56 d. Intentionally left for future modifications. 57 58 e. Include to identify the SME to which the short message is destined (e.g., the MDN, for 59 termination to the MS-based SME). 60 540 - 155 SMSDeliveryForward X.S0004-540-E v2.0

f. Include to identify the SME from which the short message originated (e.g., the MDN, if 1 originated by an MS-based SME). 2 3 g. Include if the MC address may be sent to the MS. 4 5 h. Include if available. At least one of these parameters should be present. 6 7 The SMSDeliveryForward operation success is reported with a TCAP RETURN RESULT (LAST). 8 9 This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 10 11 SMSDeliveryForward RETURN RESULT Parameters 12 13 Field Value Type Reference Notes 14 Identifier SET [NATIONAL 18] M 520-1.3.2.2 15 16 Length variable octets M 520-1.3.2.2 17 Contents 18 19 SMS_BearerData O 2.233 a 20 21 SMS_CauseCode O 2.234 b 22 23 Notes: 24 a. Include for positive acknowledgments, when applicable. 25 26 b. Include for all negative acknowledgments. 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 SMSDeliveryForward 540 - 156 X.S0004-540-E v2.0

1 2.64 SMSDeliveryPointToPoint 2 3 4 The SMSDeliveryPointToPoint (SMDPP) operation is a general purpose operation that is used to 5 convey a short message or in general any other information or encapsulated data from one point to 6 another point and report on the success of failure of that transfer (for example, as used in SMS and 7 OTASP). 8 9 The following table lists the valid combinations of invoking and responding FEs. 10 11 INVOKING FE RESPONDING FE 12 Case 1 SME MC 13 14 Case 2 MC MC 15 Case 3 MC SME 16 17 Case 4 SME SME 18 Case 5 SME OTAF 19 20 (Note 1) 21 Case 6 OTAF SME 22 23 (Note 1) 24 Case 7 OTAF MSC 25 (Note 2) 26 27 28 Notes: 29 1. Cases 5 and 6 are only applicable to TDMA OTA. 30 31 2. Case 7 is only applicable to CDMA OTA. 32 33 34 2.64.1 SMSDeiveryPointToPoint Parameter Sets: PointToPont Variant 35 36 The SMSDeliveryPointToPoint operation is initiated with a TCAP INVOKE (LAST). This is carried 37 by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 38 39 40 SMSDeliveryPointToPoint INVOKE Parameters Timer: SMT 41 Field Value Type Reference Notes 42 43 Identifier SET [NATIONAL 18] M 520-1.3.2.1 44 45 Length variable octets M 520-1.3.2.1 46 Contents 47 48 SMS_BearerData M 2.233 49 SMS_TeleserviceIdentifier M 2.246 50 51 ActionCode O 2.2 j 52 ElectronicSerialNumber O 2.112 a 53 54 InterMessageTime O 2.128 o 55 MSID O 2.153 a, i, m 56 57 NewlyAssignedMIN O 2.161 k 58 59 NewlyAssignedIMSI O 2.160 k 60 540 - 157 SMSDeliveryPointToPoint X.S0004-540-E v2.0

1 NewMINExtension O 2.163 l 2 ServiceIndicator O 2.221 p 3 4 SMS_ChargeIndicator O 2.235 b 5 SMS_DestinationAddress O 2.236 c 6 7 SMS_MessageCount O 2.237 d 8 SMS_NotificationIndicator O 2.239 e 9 10 SMS_OriginalDestinationAddress O 2.240 f 11 SMS_OriginalDestinationSubaddress O 2.241 g 12 13 SMS_OriginalOriginatingAddress O 2.242 h 14 SMS_OriginalOriginatingSubaddress O 2.243 g 15 16 SMS_OriginatingAddress O 2.244 c 17 18 TemporaryReferenceNumber O 2.277 n 19 Notes: 20 21 a. Include if known on MS-to-MC deliveries to identify the originating MS-based SME. 22 Include if known on MC-to-MS deliveries to identify the destination MS-based SME. 23 Include if known if the operation is used for CDMA OTASP or CDMA OTAPA. 24 25 b. Include if applicable. If not received, charge the message originator. 26 27 c. May be included if not carried by the underlying data transport. May require an 28 interconnection agreement to facilitate interworking between network types. 29 30 d. Include if applicable. If not received, assume value 0. 31 32 e. Include if no notification is necessary. If not received, assume notification is requested. 33 34 f. Include to identify the SME to which the short message is destined (e.g., the MDN, for 35 termination to an MS-based SME). 36 37 g. Include if applicable. 38 h. Include to identify the SME from which the short message originated (e.g., the MDN, if 39 originated by an MS-based SME). 40 41 i. When this message is sent from an MC to the Anchor or Serving MSC for an MS-based 42 SME, the MC includes the MSID set to MIN, if available; otherwise the MSID is set to 43 IMSI. 44 45 j. Include for CDMA OTASP or CDMA OTAPA if action to be performed is not implied 46 through presence of other parameters. 47 48 k. Include for CDMA OTASP or CDMA OTAPA in requests to initiate MSC procedures1 if 49 50 a value has been assigned for the MS during the current OTASP or OTAPA session. 51 l. Include for CDMA OTASP or CDMA OTAPA in requests to initiate MSC procedures1 if 52 53 a new IMSI_M has been assigned for the MS during the current OTASP or OTAPA session. 54 55 56 57 1 The MSC procedures are "Registration Following Successful OTA" and "Notification of Newly Assigned MIN (or IMSI_M) 58 or IMSI or Both Following Successful OTASP or OTAPA". 59 60 SMSDeliveryPointToPoint 540 - 158 X.S0004-540-E v2.0

1 m. For CDMA OTASP, contains the Activation_MIN. For CDMA OTAPA, contains the MS's 2 MSID at the start of the OTAPA session. If the MS has both a MIN and an IMSI at the start 3 of the OTAPA session then the MIN form of the MSID is used. 4 5 n. Include for CDMA OTASP when requesting MSC attachment to the OTAF to provide a 6 correlation between the OTASP voice and data connections. 7 8 o. Include if applicable for CDMA OTAPA when the ActionCode value is Allocate Resource 9 and inter-message timing should be different from the system default. 10 11 p. Include for CDMA OTASP or CDMA OTAPA. 12 13 The SMSDeliveryPointToPoint operation success is reported with a TCAP RETURN RESULT 14 15 (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 16 17 SMSDeliveryPointToPoint RETURN RESULT Parameters 18 19 Field Value Type Reference Notes 20 Identifier SET [NATIONAL 18] M 520-1.3.2.2 21 22 Length variable octets M 520-1.3.2.2 23 Contents 24 25 AuthorizationDenied O 2.18 h 26 DenyAccess O 2.100 c 27 28 ElectronicSerialNumber O 2.112 d 29 30 MobileStationMSID O 2.143 e 31 MSCID O 2.151 f 32 33 SMS_BearerData O 2.233 a 34 SMS_CauseCode O 2.234 b 35 36 SystemCapabilities O 2.259 g 37 38 Notes: 39 40 a. Include for positive or negative acknowledgments, when applicable. 41 42 b. Include for all negative acknowledgments. 43 c. Include for CDMA OTASP in the response to an attachment request if the AC has denied 44 service to this MS. 45 46 d. Include in response to an attachment request, for CDMA OTASP. 47 48 e. Include for CDMA OTASP in the response to an attachment request to indicate the MIN or 49 IMSI value currently in the MS’s permanent memory. 50 51 f. Include for CDMA OTASP in the response to an attachment request to identify the Serving 52 System. 53 54 g. Include for CDMA OTASP in the response to an attachment request to identify the serving 55 system’s authentication capabilities. 56 57 h. Include for CDMA OTASP in the response to an attachment request if the HLR had 58 previously denied authorization to this MS or the registration attempt was unsuccessful. 59 60 540 - 159 SMSDeliveryPointToPoint X.S0004-540-E v2.0

2.64.2 SMSDeiveryPointToPoint Parameter Sets: Broadcast Variant 1 2 The SMSDeliveryPointToPoint operation is initiated with a TCAP INVOKE (LAST). This is carried 3 4 by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 5 6 SMSDeliveryPointToPoint INVOKE Parameters Timer: SMT 7 8 Field Value Type Reference Notes 9 Identifier SET [NATIONAL 18] M 520-1.3.2.1 10 11 Length variable octets M 520-1.3.2.1 12 Contents 13 14 SMS_BearerData M 2.233 15 16 SMS_TeleserviceIdentifier M 2.246 17 BroadcastCategory O 2.303 a 18 19 BroadcastCategorySpecificInformation O 2.304 b 20 BroadcastMessageIdentifier O 2.305 c 21 22 BroadcastMessageStatus O 2.306 d 23 BroadcastMessageStatus O 2.307 e 24 25 BroadcastPeriodicity O 2.308 f 26 BroadcastServiceGroup O 2.309 b 27 28 BroadcastZoneIdentifier O 2.310 g, l 29 BroadcastZoneIdentifierList O 2.311 h, l 30 31 PreferredLanguageIndicator O 2.179 i 32 33 SMS_DestinationAddress O 2.236 j 34 SMS_OriginalOriginatingAddress O 2.242 k 35 36 SMS_OriginalOriginatingSubaddress O 2.243 b 37 SMS_OriginatingAddress O 2.244 j 38 39 Notes: 40 41 a. Include to indicate the SMDPP is being used for broadcast and to specify the category of 42 information being sent in the broadcast message. If the BroadcastCategory parameter is 43 present, but the BroadcastMessageIdentifier parameter is not, all messages from the 44 particular SME of the indicated category are identified. 45 46 b. Include if applicable. 47 48 c. Include to uniquely identify the broadcast message over the network originating from a 49 particular SME (i.e., unique on a per-SME basis). If the BroadcastMessageIdentifier is not 50 present, all messages from the particular SME of the indicated category are identified. 51 52 d. Include to indicate the priority of a broadcast message. If absent, treat as “normal” priority. 53 54 e. Include to indicate the status of a broadcast message. If absent, treat as “new” message. 55 56 f. Include if applicable to indicate periodicity of broadcast. 57 g. May be included to indicate the domain over which the broadcast is to be made or canceled. 58 59 60 SMSDeliveryPointToPoint 540 - 160 X.S0004-540-E v2.0

1 h. May be included to indicate the list of domains of various types over which the broadcast 2 is to be made or canceled. 3 4 i. Include to indicate the language used for the SMS Bearer Data in the broadcast. Required 5 for CDMA. For CDMA, the MC re-encodes the PreferredLanguageIndicator from the value 6 specified in Part 550, Section 2.180 for the language in use to the value specified in TSB58. 7 8 j. May be included if not carried by the underlying data transport. May require an 9 interconnection agreement to facilitate interworking between network types. 10 11 k. Include if not the same as the originating address (SMS_OriginatingAddress; or the 12 underlying data transport originating address). 13 14 l. These parameters are mutually exclusive. If both parameters are absent from a BTTC 15 message received by an MC, the broadcast or cancellation will be across all MSCs in the 16 broadcast domain of the MC. If both parameters are absent from a BTTC message received 17 by an MSC, the broadcast or cancellation will be across the whole MSC. 18 19 20 The SMSDeliveryPointToPoint operation success is reported with a TCAP RETURN RESULT 21 (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 22 23 SMSDeliveryPointToPoint RETURN RESULT Parameters 24 25 Field Value Type Reference Notes 26 Identifier SET [NATIONAL 18] M 520-1.3.2.2 27 28 Length variable octets M 520-1.3.2.2 29 30 Contents 31 SMS_BearerData O 2.233 a 32 33 SMS_CauseCode O 2.234 b 34 35 Notes: 36 37 a. Include for positive or negative acknowledgments, when applicable. 38 b. Include for all negative acknowledgments. 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 540 - 161 SMSDeliveryPointToPoint X.S0004-540-E v2.0

2.65 SMSDeliveryPointToPointAck 1 2 3 The SMSDeliveryPointToPointAck (SMDPPACK) operation is used to convey a Short Message 4 acknowledgement to an MS-originated short message or in general any other information or 5 encapsulated data when an MS has handed off after initiating an SMS origination. 6 7 The following table lists the valid combinations of invoking and responding FEs. 8 9 INVOKING FE RESPONDING FE 10 Case 1 Anchor MSC Serving MSC 11 12 Case 2 Anchor MSC Tandem MSC 13 Case 3 Tandem MSC Tandem MSC 14 15 Case 4 Tandem MSC Serving MSC 16 17 The SMSDeliveryPointToPointAck operation is initiated with a TCAP INVOKE (LAST). This is 18 carried by a TCAP UNIDIRECTIONAL package. 19 20 21 SMSDeliveryPointToPointAck INVOKE Parameters 22 Field Value Type Reference Notes 23 24 Identifier SET [NATIONAL 18] M 520-1.3.2.1 25 Length variable octets M 520-1.3.2.1 26 27 Contents 28 29 InterMSCCircuitID M 2.129 30 IMSI O 2.127 d 31 32 MobileIdentificationNumber O 2.140 d 33 SMS_BearerData O 2.233 a 34 35 SMS_CauseCode O 2.234 b 36 SMS_TransactionID O 2.248 c 37 38 Notes: 39 40 a. Include for positive acknowledgements, when applicable. 41 42 b. Include for all negative acknowledgements. 43 44 c. For TDMA, include to identify the SMS origination initiated by an MS that has been 45 handed off after it initiated an SMS origination. 46 47 d. Include if available. At least one of these parameters should be present. 48 49 50 51 52 53 54 55 56 57 58 59 60 SMSDeliveryPointToPointAck 540 - 162 X.S0004-540-E v2.0

1 2.66 SMSNotification 2 3 4 The SMSNotification (SMSNOT) operation is used to report a change in an MS’s ability to receive 5 teleservice messages based on the location or status of the MS. This message, at a minimum, is used 6 to report the accessibility of an MS following a postponed SMSRequest or 7 SMSDeliveryPointToPoint. This message may also be used to revoke delivery permission 8 previously granted with either an SMSRequest or an SMSNotification. 9 10 The following table lists the valid combinations of invoking and responding FEs. 11 12 INVOKING FE RESPONDING FE 13 Case 1 HLR MC 14 15 Case 2 MSC MC 16 Case 3 HLR OTAF 17 18 (Note 1) 19 Case 4 MSC OTAF 20 21 (Note 2) 22 23 Notes: 24 1. Case 3 is applicable to both CDMA and TDMA OTA. 25 26 2. Case 4 is only applicable to TDMA OTA. 27 The SMSNotification operation is initiated with a TCAP INVOKE (LAST). This is carried by a 28 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 29 30 31 SMSNotification INVOKE Parameters Timer: SNT 32 33 Field Value Type Reference Notes 34 Identifier SET [NATIONAL 18] M 520-1.3.2.1 35 36 Length variable octets M 520-1.3.2.1 37 Contents 38 39 ElectronicSerialNumber M 2.112 40 MSID M 2.153 c 41 42 MobileDirectoryNumber O 2.139 f 43 SMS_AccessDeniedReason O 2.231 a 44 45 SMS_Address O 2.232 a, b 46 47 SMS_TeleserviceIdentifier O 2.246 e 48 TransactionCapability (Serving MSC) O 2.285 d 49 50 Notes: 51 52 a. These parameters are mutually exclusive; however, one must be present. 53 54 b. Included to indicate the temporary routing address of an MS-based SME. 55 56 c. Include the MIN form of the MSID if the MS has a MIN; otherwise include the IMSI form 57 of the MSID. 58 59 60 540 - 163 SMSNotification X.S0004-540-E v2.0

d. Include if routing of SMS messages to the specified MS is allowed and if any applicable 1 capabilities (e.g., SCCP-based segmentation and reassembly) are set. 2 3 e. Include for TDMA if the notification is issued by the HLR independent of a postponed 4 (previous) SMSRequest to initiate a SMS teleservice on an MS. 5 6 f. Include if applicable. 7 8 9 The SMSNotification operation success is reported with a TCAP RETURN RESULT (LAST). This 10 is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 11 12 SMSNotification RETURN RESULT Parameters 13 14 Field Value Type Reference Notes 15 Identifier SET [NATIONAL 18] M 520-1.3.2.2 16 17 Length variable octets M 520-1.3.2.2 18 19 Contents 20 SMS_MessageCount O 2.237 a 21 22 Notes: 23 24 a. Set to value zero if the MC does not have SMS message delivery pending for the MS 25 identified. 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 SMSNotification 540 - 164 X.S0004-540-E v2.0

1 2.67 SMSRequest 2 3 4 The SMSRequest (SMSREQ) operation is used to request an MS’s current SMS routing address with 5 a default to request notification when the MS becomes available if the MS is not currently available. 6 7 The following table lists the valid combinations of invoking and responding FEs. 8 9 INVOKING FE RESPONDING FE 10 Case 1 MC HLR 11 12 Case 2 HLR Serving VLR 13 Case 3 Serving VLR Serving MSC 14 15 Case 4 OTAF HLR 16 (Note 1) 17 18 Notes: 19 20 1. Case 4 is applicable to both CDMA and TDMA OTA. 21 The SMSRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 22 23 QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 24 25 SMSRequest INVOKE Parameters Timer: SRT 26 27 Field Value Type Reference Notes 28 Identifier SET [NATIONAL 18] M 520-1.3.2.1 29 30 Length variable octets M 520-1.3.2.1 31 Contents 32 33 MSID O 2.153 e, f, g 34 ElectronicSerialNumber O 2.112 a 35 36 MobileDirectoryNumber O 2.139 e 37 38 ServiceIndicator O 2.221 d 39 SMS_NotificationIndicator O 2.239 b 40 41 SMS_TeleserviceIdentifier O 2.246 c 42 43 Notes: 44 45 a. Include if known. 46 b. Include to specify notification requirements. If not included, implies notification shall be 47 48 sent when MS becomes available (default). 49 c. Include to identify the teleservice for which the request is being made. 50 51 d. Include to identify CDMA OTAPA service. 52 53 e. At least one parameter must be present (i.e. either MSID or MobileDirectoryNumber) when 54 this message is sent from the MC to the HLR. 55 56 57 58 59 60 540 - 165 SMSRequest X.S0004-540-E v2.0

f. The HLR includes the IMSI type of MSID if the IMSI was present in the last message 1 received from the Serving System; otherwise the HLR includes the 2 MobileIdentificationNumber type of MSID. The VLR includes the type of MSID last 3 received from the Serving MSC; this may not be the type of MSID received form the HLR 4 5 g. This parameter is mandatory when the message is sent from the HLR to the VLR or from 6 the VLR to the MSC. 7 8 9 The SMSRequest operation success is reported with a TCAP RETURN RESULT (LAST). This is 10 carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 11 12 SMSRequest RETURN RESULT Parameters 13 14 Field Value Type Reference Notes 15 16 Identifier SET [NATIONAL 18] M 520-1.3.2.2 17 Length variable octets M 520-1.3.2.2 18 19 Contents 20 ElectronicSerialNumber O 2.112 a 21 22 MSID O 2.153 e 23 24 SMS_AccessDeniedReason O 2.231 b, c 25 SMS_Address O 2.232 c, d 26 27 SMS_CauseCode O 2.234 g 28 TransactionCapability (Serving MSC) O 2.285 f 29 30 Notes: 31 32 a. Include if not received in SMSRequest INVOKE and SMS delivery is allowed. 33 34 b. Include if delivery of SMS messages is denied or deferred. 35 36 c. These parameters are mutually exclusive. 37 38 d. Include if routing of SMS messages is applicable. 39 e. Include the mobile station identifier that should be used for SMS delivery. This parameter 40 is only included by the HLR. The MSID should be the MIN type if available, otherwise the 41 42 MSID should be an IMSI. 43 f. Include if routing of SMS messages to the specified MS is allowed and if any applicable 44 capabilities (e.g., SCCP-based segmentation and reassembly) are set. 45 46 g. Include for TDMA, to specify the failure cause for this request (e.g. if a request is sent to 47 an HLR or MSC that does not support the specified teleservice). 48 49 50 51 52 53 54 55 56 57 58 59 60 SMSRequest 540 - 166 X.S0004-540-E v2.0

1 2.68 SRFDirective 2 3 4 The SRFDirective (SRFDIR) operation is used by service control logic to direct the operation of an 5 IP (or other network entity) which provides user interaction. 6 7 The following table lists the valid combinations of invoking and responding FEs. 8 INVOKING FE RESPONDING FE 9 10 Case 1 HLR IP 11 12 Case 2 SCP IP 13 Case 3 SN IP 14 15 The SRFDirective operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 16 CONVERSATION WITHOUT PERMISSION package. The Parameter Set is encoded as follows: 17 18 19 SRFDirective INVOKE Parameters Timer: SRFDT 20 Field Value Type Reference Notes 21 22 Identifier SET [NATIONAL 18] M 520-1.3.2.1 23 24 Length variable octets M 520-1.3.2.1 25 Contents 26 27 AnnouncementList O 2.10 a, d 28 DigitCollectionControl O 2.104 b 29 30 ExecuteScript O 2.115 c, d 31 32 Notes: 33 34 a. When the AnnouncementList parameter is present, the ExecuteScript parameter shall not 35 be included. 36 37 b. This parameter may only be included if the AnnouncementList parameter is present. 38 39 c. When the ExecuteScript parameter is present, the AnnouncementList and 40 DigitCollectionControl parameters shall not be included. 41 d. At least one of these parameters must be present. 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 540 - 167 SRFDirective X.S0004-540-E v2.0

The SRFDirective operation success is reported with a TCAP RETURN RESULT (LAST). This is 1 carried by a TCAP CONVERSATION WITH PERMISSION package. The Parameter Set is 2 encoded as follows: 3 4 5 SRFDirective RETURN RESULT Parameters 6 7 Field Value Type Reference Notes 8 Identifier SET [NATIONAL 18] M 520-1.3.2.2 9 10 Length variable octets M 520-1.3.2.2 11 Contents 12 13 Digits (Dialed) O 2.105 a, b 14 ScriptResult O 2.212 c 15 16 Notes: 17 18 a. This may only be included when the AnnouncementList parameter is present in the 19 SRFDIR. 20 21 b. The number of digits returned may be zero, indicating either implying the user did not enter 22 digits before time-out or that all announcements were played. 23 24 c. This may only be included when the ExecuteScript parameter is included in the SRFDIR. 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 SRFDirective 540 - 168 X.S0004-540-E v2.0

1 2.69 TBusy 2 3 4 The TBusy (TBUSY) operation is used by an MSC to obtain call treatment instructions from an SCP 5 or SN for the called party. 6 7 The following table lists the valid combinations of invoking and responding FEs. 8 INVOKING FE RESPONDING FE 9 10 Case 1 MSC SCP 11 12 Case 2 MSC SN 13 14 The TBusy operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY 15 WITH PERMISSION package. The Parameter Set is encoded as follows: 16 17 TBusy INVOKE Parameters Timer: TBT 18 19 Field Value Type Reference Notes 20 21 Identifier SET [NATIONAL 18] M 520-1.3.2.1 22 Length variable octets M 520-1.3.2.1 23 24 Contents 25 BillingID (Invoking) M 2.23 a 26 27 MSCID M 2.151 b 28 TransactionCapability M 2.285 29 30 TriggerType M 2.289 c 31 WINCapability M 2.299 d 32 33 CallingPartyName O 2.29 e 34 CallingPartyNumberDigits1 O 2.30 e 35 36 CallingPartyNumberDigits2 O 2.31 e 37 38 CallingPartySubaddress O 2.34 e 39 CDMAServiceOption O 2.66 k 40 41 ElectronicSerialNumber O 2.112 f 42 GroupInformation O 2.124 f 43 44 IMSI O 2.127 f, h 45 LegInformation O 2.133 f 46 47 LocationAreaID O 2.135 g 48 MobileDirectoryNumber O 2.139 h, i 49 50 MobileIdentificationNumber O 2.140 f, h 51 MSCIdentificationNumber O 2.152 b 52 53 OneTimeFeatureIndicator O 2.167 j 54 55 PilotBillingID O 2.177 f 56 PilotNumber O 2.178 f 57 58 PreferredLanguageIndicator O 2.179 g 59 60 540 - 169 TBusy X.S0004-540-E v2.0

1 RedirectingNumberDigits O 2.198 e 2 RedirectingSubaddress O 2.201 e 3 4 RedirectionReason O 2.202 f 5 ServingCellID O 2.225 g 6 7 SystemMyTypeCode O 2.260 8 TDMAServiceCode O 2.273 l 9 10 TerminationAccessType O 2.279 f 11 12 Notes: 13 14 a. Include to identify the call at the invoking MSC 15 b. Include to identify the invoking MSC. 16 17 c. Include to identify the trigger encountered. 18 19 d. Include to identify the WIN capabilities supported. 20 21 e. Include if available (i.e., provided in call origination). 22 23 f. Include if available. 24 g. Include if available. (Note: this information element may not be available when this 25 26 operation is initiated by a non-Serving MSC.) 27 h. One must be present for use as a service key. 28 29 i. Include if available for recording purposes (see DMH). 30 31 j. Include if any OneTimeFeatureIndicator status bits are set (i.e., have value of 1). 32 33 k. Include if CDMAServiceOption is known to allow distinctive forwarding based on Service 34 Type. 35 36 l. Include if TDMAServiceCode is known to allow distinctive forwarding based on Service 37 Type. 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 TBusy 540 - 170 X.S0004-540-E v2.0

1 The operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a 2 TCAP RESPONSE package. The Parameter Set is encoded as follows: 3 4 5 TBusy RETURN RESULT Parameters 6 Field Value Type Reference Notes 7 8 Identifier SET [NATIONAL 18] M 520-1.3.2.2 9 Length variable octets M 520-1.3.2.2 10 11 Contents 12 13 AccessDeniedReason O 2.1 a 14 ActionCode O 2.2 b 15 16 AnnouncementList O 2.10 c 17 CallingPartyNumberString1 O 2.32 d, e 18 19 CallingPartyNumberString2 O 2.33 d, e 20 CarrierDigits O 2.37 21 22 DisplayText O 2.106 d, e, m 23 DisplayText2 O 2.107 d, e, m 24 25 DMH_AccountCodeDigits O 2.108 f 26 DMH_AlternateBillingDigits O 2.109 f 27 28 DMH_BillingDigits O 2.110 f 29 30 DMH_RedirectionIndicator O 2.111 f 31 GroupInformation O 2.124 g 32 33 OneTimeFeatureIndicator O 2.167 h 34 PilotNumber O 2.178 g 35 36 RedirectingNumberDigits O 2.198 i 37 RedirectingNumberString O 2.199 d, e 38 39 RedirectingSubaddress O 2.201 i 40 RoutingDigits O 2.209 41 42 TerminationList O 2.280 k 43 TerminationTriggers O 2.283 l 44 45 TriggerAddressList O 2.286 l 46 47 Notes: 48 49 a. Include if access is denied. If included, no other optional parameters shall be included (with 50 the exception of the AnnouncementList parameter). 51 52 b. Include if action to be performed is not implied through presence of other parameters. 53 54 c. Include if one or more tones or announcements are to be applied to the MS. 55 56 d. Include if a LocalTermination parameter is included in the TerminationList parameter. 57 e. Include if the related feature is active. 58 59 60 540 - 171 TBusy X.S0004-540-E v2.0

f. Include if available for recording purposes (see DMH). 1 2 g. Include for multi-leg calls. 3 4 h. Include if modification to normal feature processing is required for the call in progress. 5 6 i. Include if call is being redirected. 7 j. Intentionally left for future modifications. 8 9 k. Include if call routing is required. 10 11 l. Include if applicable. 12 13 m. Include only one of these mutually exclusive parameters. 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 TBusy 540 - 172 X.S0004-540-E v2.0

1 2.70 TMSIDirective 2 3 4 The TMSIDirective (TMSIDIR) operation is used to assign the MS’s full TMSI or TMSI Code 5 within a TMSI Zone. The INVOKE comes from the serving system (e.g., VLR). 6 7 The following table lists the valid combinations of invoking and responding FEs: 8 9 INVOKING FE RESPONDING FE 10 Case 1 Serving VLR Serving MSC 11 12 One of two possible results is returned: 13 14 1. The TMSIDirective operation is successful. 15 16 2. Notification that TMSIDirective is unsuccessful with an appropriate denied 17 reason. 18 The TMSIDirective operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 19 20 QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 21 22 TMSIDirective INVOKE Parameters Timer: TDT 23 24 Field Value Type Reference Notes 25 Identifier SET [NATIONAL 18] M 520-1.3.2.1 26 27 Length variable octets M 520-1.3.2.1 28 Contents 29 30 ElectronicSerialNumber M 2.112 31 MSID M 2.153 32 33 NetworkTMSIExpirationTime M 2.159 34 35 NewNetworkTMSI M 2.164 36 LocationAreaID O 2.135 a 37 38 NetworkTMSI O 2.158 a 39 40 Notes: 41 42 a. Include if known. 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 540 - 173 TMSIDirective X.S0004-540-E v2.0

The TMSIDirective operation success is reported with a TCAP RETURN RESULT (LAST). This is 1 carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 2 3 4 TMSI Directive RETURN RESULT Parameters 5 Field Value Type Reference Notes 6 7 Identifier SET [NATIONAL 18] M 520-1.3.2.2 8 9 Length variable octets M 520-1.3.2.2 10 Contents 11 12 DenyAccess O 2.100 b 13 ElectronicSerialNumber O 2.112 b 14 15 MSID O 2.153 b 16 ReasonList O 2.195 a 17 18 Notes: 19 20 a. Include if no response from the MS. 21 22 b. Include if MS fails authentication. 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 TMSIDirective 540 - 174 X.S0004-540-E v2.0

1 2.71 TNoAnswer 2 3 4 The TNoAnswer (TNOANS) operation is used by an MSC to obtain call treatment instructions from 5 an SCP or SN for the called party. 6 7 The following table lists the valid combinations of invoking and responding FEs. 8 INVOKING FE RESPONDING FE 9 10 Case 1 MSC SCP 11 12 Case 2 MSC SN 13 14 The TNoAnswer operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 15 QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 16 17 TNoAnswer INVOKE Parameters Timer: TNAT 18 19 Field Value Type Reference Notes 20 21 Identifier SET [NATIONAL 18] M 520-1.3.2.1 22 Length variable octets M 520-1.3.2.1 23 24 Contents 25 BillingID (Invoking) M 2.23 a 26 27 MSCID M 2.151 b 28 TransactionCapability M 2.285 29 30 TriggerType M 2.289 c 31 WINCapability M 2.299 d 32 33 CallingPartyName O 2.29 e 34 CallingPartyNumberDigits1 O 2.30 e 35 36 CallingPartyNumberDigits2 O 2.31 e 37 38 CallingPartySubaddress O 2.34 e 39 CDMAServiceOption O 2.66 k 40 41 ElectronicSerialNumber O 2.112 f 42 GroupInformation O 2.124 f 43 44 IMSI O 2.127 f, h 45 LegInformation O 2.133 f 46 47 LocationAreaID O 2.135 g 48 MobileDirectoryNumber O 2.139 h, i 49 50 MobileIdentificationNumber O 2.140 f, h 51 OneTimeFeatureIndicator O 2.167 j 52 53 PilotBillingID O 2.177 f 54 55 PilotNumber O 2.178 f 56 PreferredLanguageIndicator O 2.179 g 57 58 RedirectingNumberDigits O 2.198 e 59 60 540 - 175 TNoAnswer X.S0004-540-E v2.0

1 RedirectingSubaddress O 2.201 e 2 RedirectionReason O 2.202 f 3 4 ServingCellID O 2.225 g 5 SystemMyTypeCode O 2.260 6 7 TDMAServiceCode O 2.273 l 8 TerminationAccessType O 2.279 f 9 10 Notes: 11 12 a. Include to identify the call at the invoking MSC 13 14 b. Include to identify the invoking MSC. 15 16 c. Include to identify the trigger encountered. 17 d. Include to identify the WIN capabilities supported. 18 19 e. Include if available (i.e., provided in call origination). 20 21 f. Include if available. 22 23 g. Include if available. (Note: this information element may not be available when this 24 operation is initiated by a non-Serving MSC.) 25 26 h. One must be present for use as a service key. 27 28 i. Include if available for recording purposes (see DMH). 29 j. Include if any OneTimeFeatureIndicator status bits are set (i.e., have value of 1). 30 31 k. Include if CDMAServiceOption is known to allow distinctive forwarding based on Service 32 Type. 33 34 l. Include if TDMAServiceCode is known to allow distinctive forwarding based on Service 35 Type. 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 TNoAnswer 540 - 176 X.S0004-540-E v2.0

1 The TNoAnswer operation success is reported with a TCAP RETURN RESULT (LAST). This is 2 carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 3 4 5 TNoAnswer RETURN RESULT Parameters 6 Field Value Type Reference Notes 7 8 Identifier SET [NATIONAL 18] M 520-1.3.2.2 9 Length variable octets M 520-1.3.2.2 10 11 Contents 12 13 AccessDeniedReason O 2.1 a 14 ActionCode O 2.2 b 15 16 AnnouncementList O 2.10 c 17 CallingPartyNumberString1 O 2.32 d, e 18 19 CallingPartyNumberString2 O 2.33 d, e 20 CarrierDigits O 2.37 21 22 DisplayText O 2.106 d, e, m 23 DisplayText2 O 2.107 d, e, m 24 25 DMH_AccountCodeDigits O 2.108 f 26 DMH_AlternateBillingDigits O 2.109 f 27 28 DMH_BillingDigits O 2.110 f 29 30 DMH_RedirectionIndicator O 2.111 f 31 GroupInformation O 2.124 g 32 33 OneTimeFeatureIndicator O 2.167 h 34 PilotNumber O 2.178 g 35 36 RedirectingNumberDigits O 2.198 i 37 RedirectingNumberString O 2.199 d, e 38 39 RedirectingSubaddress O 2.201 i 40 RoutingDigits O 2.209 41 42 TerminationList O 2.280 k 43 TerminationTriggers O 2.283 l 44 45 TriggerAddressList O 2.286 l 46 47 Notes: 48 49 a. Include if access is denied. If included, no other optional parameters shall be included (with 50 the exception of the AnnouncementList parameter). 51 52 b. Include if action to be performed is not implied through presence of other parameters. 53 54 c. Include if one or more tones or announcements are to be applied to the MS. 55 56 d. Include if a LocalTermination parameter is included in the TerminationList parameter. 57 e. Include if the related feature is active. 58 59 60 540 - 177 TNoAnswer X.S0004-540-E v2.0

f. Include if available for recording purposes (see DMH). 1 2 g. Include for multi-leg calls. 3 4 h. Include if modification to normal feature processing is required for the call in progress. 5 6 i. Include if call is being redirected. 7 j. Intentionally left for future modifications. 8 9 k. Include if call routing is required. 10 11 l. Include if applicable. 12 13 m. Include only one of these mutually exclusive parameters. 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 TNoAnswer 540 - 178 X.S0004-540-E v2.0

1 2.72 TransferToNumberRequest 2 3 4 The TransferToNumberRequest (TRANUMREQ) operation is used during feature processing to 5 obtain an MS’s forward-to number from the HLR. 6 7 The following table lists the valid combinations of invoking and responding FEs. 8 9 INVOKING FE RESPONDING FE 10 Case 1 Originating MSC HLR 11 12 Case 2 Serving MSC HLR 13 Case 3 HLR SCP 14 15 The TransferToNumberRequest operation is initiated with a TCAP INVOKE (LAST). This is 16 carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as 17 18 follows: 19 20 TransferToNumberRequest INVOKE Parameters Timer: TTNRT 21 22 Field Value Type Reference Notes 23 Identifier SET [NATIONAL 18] M 520-1.3.2.1 24 25 Length variable octets M 520-1.3.2.1 26 Contents 27 28 ElectronicSerialNumber M 2.112 29 MSID M 2.151 f 30 31 RedirectionReason M 2.202 32 33 SystemMyTypeCode (MSC) M 2.260 34 BillingID (Originating) O 2.23 a 35 36 CallingPartyName O 2.29 k 37 CallingPartyNumberDigits1 O 2.30 k 38 39 CallingPartyNumberDigits2 O 2.31 k 40 CallingPartySubaddress O 2.34 k 41 42 CDMAServiceOption O 2.66 h 43 GroupInformation O 2.124 b 44 45 LegInformation O 2.133 c 46 MobileIdentificationNumber O 2.140 n 47 48 MSCID (Originating) O 2.151 d 49 50 MSCIdentificationNumber O 2.152 l 51 PilotBillingID O 2.177 m 52 53 PilotNumber O 2.178 m 54 RedirectingNumberDigits O 2.198 g 55 56 RedirectingSubaddress O 2.201 g 57 SenderIdentificationNumber O 2.215 j 58 59 60 540 - 179 TransferToNumberRequest X.S0004-540-E v2.0

1 TDMAServiceCode O 2.273 i 2 TransactionCapability O 2.285 e 3 4 Notes: 5 6 a. Include to identify the Originating MSC and its BillingID for subsequent call redirection. 7 8 b. Include if available (i.e., if provided in the associated RoutingRequest INVOKE or 9 LocationRequest RETURN RESULT) for the None Reachable termination trigger. 10 11 c. Include if available (i.e., if provided in the associated RoutingRequest INVOKE or 12 LocationRequest RETURN RESULT) for any termination trigger except None Reachable. 13 d. Included on TIA-41-D or later. 14 15 e. Include on IS-41-C or later. 16 17 f. Use the MobileIdentificationNumber form of the MSID if the IMSI is known to be a 18 MIN-based IMSI. 19 20 g. Include if available (i.e., provided in call origination) for the None Reachable termination 21 trigger. 22 23 h. Include if CDMA channel is in use to allow distinctive forwarding based on Service Type. 24 25 i. Include if TDMA channel is in use to allow distinctive forwarding based on Service Type. 26 27 j. May be included to identify the network entity sending the message. 28 k. Include if available (i.e., provided in call origination). 29 30 l. Include to identify the initiating MSC and to indicate that the MSC is capable of accepting 31 digits in the international format. 32 33 m. Include if available. 34 35 n. Include if known and if the IMSI has been included as MSID. 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 TransferToNumberRequest 540 - 180 X.S0004-540-E v2.0

1 The TransferToNumberRequest operation success is reported with a TCAP RETURN RESULT 2 (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 3 4 5 TransferToNumberRequest RETURN RESULT Parameters 6 Field Value Type Reference Notes 7 8 Identifier SET [NATIONAL 18] M 520-1.3.2.2 9 Length variable octets M 520-1.3.2.2 10 11 Contents 12 13 Digits (Destination) M 2.105 a 14 AccessDeniedReason O 2.1 b 15 16 ActionCode O 2.2 c 17 AnnouncementList O 2.10 d 18 19 CallingPartyNumberString1 O 2.32 e 20 CallingPartyNumberString2 O 2.33 e 21 22 CallingPartySubaddress O 2.34 e, f 23 Digits (Carrier) O 2.105 g 24 25 DisplayText O 2.106 e, k 26 DisplayText2 O 2.107 e, k 27 28 DMH_AccountCodeDigits O 2.108 h 29 30 DMH_AlternateBillingDigits O 2.109 h 31 DMH_BillingDigits O 2.110 h 32 33 DMH_RedirectionIndicator O 2.111 h 34 GroupInformation O 2.124 i 35 36 MobileDirectoryNumber O 2.139 h 37 NoAnswerTime O 2.165 g 38 39 RedirectingNumberDigits O 2.198 f 40 RedirectingNumberString O 2.199 e 41 42 RedirectingSubaddress O 2.201 e, f 43 TerminationList O 2.280 j 44 45 TerminationTriggers O 2.283 g 46 47 Notes: 48 49 a. Encode the Digits (Destination) as International if it is known that the requesting MSC can 50 accept the digits in this format (e.g., the MSCIdentificationNumber parameter was received 51 in the INVOKE) and an HLR stored number is being provided. 52 This parameter is ignored if the TeminationList parameter is provided. 53 54 b. Include if access is denied. If included, no other optional parameters shall be included (with 55 the exception of the AnnouncementList or ActionCode). 56 57 c. Include if action to be performed is not implied through presence of other parameters. 58 59 d. Include if one or more tones or announcements are to be applied to the MS. 60 540 - 181 TransferToNumberRequest X.S0004-540-E v2.0

e. Include if related feature is active and if a LocalTermination parameter is included within 1 the TerminationList parameter. 2 3 f. Optionally include if a PSTNTermination parameter or an IntersystemTermination 4 parameter is included within the TerminationList parameter. 5 6 g. Include if applicable. 7 8 h. Include if available for recording purposes (see DMH). 9 10 i. Include for multi-leg calls. 11 j. Include if call routing is required. 12 13 k. Include only one of these mutually exclusive parameters. 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 TransferToNumberRequest 540 - 182 X.S0004-540-E v2.0

1 2.73 TrunkTest 2 3 4 The TrunkTest (TTEST) operation is used by an MSC to request that the designated trunk be placed 5 in a test configuration (e.g., loop-back) at a remote MSC. 6 7 The following table lists the possible combinations of invoking and responding FEs. 8 9 INVOKING FE RESPONDING FE 10 Case 1 MSC MSC 11 12 The TrunkTest operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 13 QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 14 15 16 TrunkTest INVOKE Parameters Timer: TTT 17 Field Value Type Reference Notes 18 19 Identifier SET [NATIONAL 18] M 520-1.3.2.1 20 21 Length variable octets M 520-1.3.2.1 22 Contents 23 24 InterMSCCircuitID M 2.129 25 SeizureType M 2.214 26 27 The TrunkTest operation success is reported with a TCAP RETURN RESULT (LAST). This is 28 29 carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 30 31 TrunkTest RETURN RESULT Parameters 32 33 Field Value Type Reference Notes 34 Identifier SET [NATIONAL 18] M 520-1.3.2.2 35 36 Length zero octets M 520-1.3.2.2 37 Contents 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 540 - 183 TrunkTest X.S0004-540-E v2.0

2.74 TrunkTestDisconnect 1 2 3 The TrunkTestDisconnect (TTESTDISC) operation is used by an MSC to request that the 4 designated trunk at a remote MSC be disconnected from its test configuration (e.g., loop-back). 5 6 The following table lists the possible combinations of invoking and responding FEs. 7 8 INVOKING FE RESPONDING FE 9 Case 1 MSC MSC 10 11 The TrunkTestDisconnect operation is initiated with a TCAP INVOKE (LAST). This is carried by 12 a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 13 14 15 TrunkTestDisconnect INVOKE Parameters Timer: TTDT 16 17 Field Value Type Reference Notes 18 Identifier SET [NATIONAL 18] M 520-1.3.2.1 19 20 Length variable octets M 520-1.3.2.1 21 Contents 22 23 InterMSCCircuitID M 2.129 24 25 The TrunkTestDisconnect operation success is reported with a TCAP RETURN RESULT (LAST). 26 This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 27 28 29 TrunkTestDisconnect RETURN RESULT Parameters 30 Field Value Type Reference Notes 31 32 Identifier SET [NATIONAL 18] M 520-1.3.2.2 33 Length zero octets M 520-1.3.2.2 34 35 Contents 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 TrunkTestDisconnect 540 - 184 X.S0004-540-E v2.0

1 2.75 Unblocking 2 3 4 The Unblocking (UNBLOCKING) operation is used to inform an MSC of the reinsertion into service 5 of a certain circuit. 6 7 The following table lists the possible combinations of invoking and responding FEs. 8 9 INVOKING FE RESPONDING FE 10 Case 1 MSC MSC 11 12 The Unblocking operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP 13 QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 14 15 16 Unblocking INVOKE Parameters Timer: UBLKT 17 Field Value Type Reference Notes 18 19 Identifier SET [NATIONAL 18] M 520-1.3.2.1 20 21 Length variable octets M 520-1.3.2.1 22 Contents 23 24 InterMSCCircuitID M 2.129 25 26 The Unblocking operation success is reported with a TCAP RETURN RESULT (LAST). This is 27 carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 28 29 Unblocking RETURN RESULT Parameters 30 31 Field Value Type Reference Notes 32 33 Identifier SET [NATIONAL 18] M 520-1.3.2.2 34 Length zero octets M 520-1.3.2.2 35 36 Contents 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 540 - 185 Unblocking X.S0004-540-E v2.0

2.76 UnreliableRoamerDataDirective 1 2 3 The UnreliableRoamerDataDirective (UNRELDIR) operation is used by the HLR to inform a VLR 4 that it has experienced a failure which has rendered its roaming MS data unreliable. 5 6 The following table lists the valid combinations of invoking and responding FEs. 7 8 INVOKING FE RESPONDING FE 9 Case 1 HLR Serving VLR 10 11 The UnreliableRoamerDataDirective operation is initiated with a TCAP INVOKE (LAST). This is 12 carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as 13 14 follows: 15 16 UnreliableRoamerDataDirective INVOKE Parameters Timer: URDDT 17 18 Field Value Type Reference Notes 19 Identifier SET [NATIONAL 18] M 520-1.3.2.1 20 21 Length variable octets M 520-1.3.2.1 22 Contents 23 24 MSCID (HLR) O 2.151 a 25 26 SenderIdentificationNumber O 2.215 b 27 28 Notes: 29 a. Include on IS-41-C and later. 30 31 b. Include to identify the functional entity sending the message. 32 33 34 The UnreliableRoamerDataDirective operation success is reported with a TCAP RETURN 35 RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded 36 as follows: 37 38 UnreliableRoamerDataDirective RETURN RESULT Parameters 39 40 Field Value Type Reference Notes 41 42 Identifier SET [NATIONAL 18] M 520-1.3.2.2 43 Length zero octets M 520-1.3.2.2 44 45 Contents 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 UnreliableRoamerDataDirective 540 - 186 X.S0004-540-E v2.0

1 2.77 UnsolicitedResponse 2 3 4 The UnsolicitedResponse (UNSOLRES) operation is used by a Border MSC to notify neighboring 5 MSCs that an unsolicited or unexpected page response has been received from an MS, that the MS’s 6 presence in the Border MSC has been confirmed, and that a TLDN has been assigned. 7 8 The following table lists the valid combinations of invoking and responding FEs. 9 10 INVOKING FE RESPONDING FE 11 Case 1 Border MSC Serving MSC 12 13 The UnsolicitedResponse operation is initiated with a TCAP INVOKE (LAST). This is carried by a 14 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows: 15 16 17 UnsolicitedResponse INVOKE Parameters Timer: URT 18 19 Field Value Type Reference Notes 20 Identifier SET [NATIONAL 18] M 520-1.3.2.1 21 22 Length variable octets M 520-1.3.2.1 23 Contents 24 25 BillingID (Anchor) M 2.23 26 ElectronicSerialNumber M 2.112 27 28 MSID M 2.153 d 29 CDMAServiceOption O 2.66 e 30 31 Digits (Destination) O 2.105 a 32 33 ExtendedMSCID (Border MSC) O 2.116 a 34 ExtendedSystemMyTypeCode (Border MSC) O 2.117 a 35 36 PC_SSN (Border MSC) O 2.176 a, b 37 SystemAccessType O 2.258 c 38 39 TDMAServiceCode O 2.273 e 40 41 Notes: 42 43 a. Include if Temporary Local Directory Number (TLDN) is available. 44 45 b. Include if SS7 is used. 46 c. Include for IS-41-C or later. 47 48 d. Include the identifier with which the MS accessed the system, unless that identifier was a 49 MIN-based IMSI, in which case the MobileIdentificationNumber (populated with the MIN 50 derived from that IMSI) should be included. 51 52 e. Include to indicate the service type in which the MS responded to a page. 53 54 55 The UnsolicitedResponse operation success is reported with a TCAP RETURN RESULT (LAST). 56 This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows: 57 58 59 60 540 - 187 UnsolicitedResponse X.S0004-540-E v2.0

1 2 3 UnsolicitedResponse RETURN RESULT Parameters 4 Field Value Type Reference Notes 5 6 Identifier SET [NATIONAL 18] M 520-1.3.2.2 7 8 Length variable octets M 520-1.3.2.2 9 Contents 10 11 AccessDeniedReason O 2.1 j 12 AlertCode O 2.4 a 13 14 BillingID (Originating) O 2.23 b 15 CallingPartyName O 2.29 g 16 17 CallingPartyNumberDigits1 O 2.30 d 18 CallingPartyNumberDigits2 O 2.31 d 19 20 CallingPartyNumberString1 O 2.32 c 21 CallingPartyNumberString2 O 2.33 c 22 23 CallingPartySubaddress O 2.34 c 24 25 DisplayText O 2.106 g, i 26 DisplayText2 O 2.107 g, i 27 28 DMH_AccountCodeDigits O 2.108 d 29 DMH_AlternateBillingDigits O 2.109 d 30 31 DMH_BillingDigits O 2.110 d 32 ExtendedMSCID (Originating MSC) O 2.116 e 33 34 ExtendedSystemMyTypeCode (Originating MSC) O 2.117 f 35 LegInformation O 2.133 g 36 37 MobileDirectoryNumber O 2.139 d 38 MSCIdentificationNumber (Origination MSC) O 2.152 g 39 40 OneTimeFeatureIndicator O 2.167 g 41 42 PC_SSN (Originating MSC) O 2.176 h 43 PilotBillingID O 2.177 g 44 45 PilotNumber O 2.178 g 46 PreferredLanguageIndicator O 2.179 g 47 48 RedirectingNumberDigits O 2.198 d 49 RedirectingNumberString O 2.199 c 50 51 RedirectingPartyName O 2.200 g 52 RedirectingSubaddress O 2.201 c 53 54 TerminationTreatment O 2.282 g 55 TerminationTriggers O 2.283 g 56 57 TriggerAddressList O 2.286 g 58 59 60 UnsolicitedResponse 540 - 188 X.S0004-540-E v2.0

1 Notes: 2 3 a. Include to specify special alerting treatment. 4 5 b. Include for subsequent call redirection at the originating MSC and for recording purposes 6 (see DMH). 7 8 c. Include if related feature is active. 9 d. Include if available. 10 11 e. Include to identify originating system. 12 13 f. Include to identify originating system manufacturer. 14 15 g. Include if available (e.g., provided in the associated RoutingRequest INVOKE). 16 17 h. Include if SS7 may be used for subsequent call redirection. 18 19 i. Include only one of these mutually exclusive parameters. 20 j. Include when the operation cannot be completed (e.g. MS responded to a page in the border 21 system with a service type that differs from the one used by the system that paged). If 22 23 present other parameters may be ignored. 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 540 - 189 UnsolicitedResponse X.S0004-540-E v2.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 UnsolicitedResponse 540 - 190