X.S0010-A v1.0 010504

3GPP2 X.S0010-A Version: 1.
0 Date: 5 January 2004
Pre-Paid Charging Enhancements for CircuitSwitched Data and Short Message Services
COPYRIGHT 3GPP2 and its Organizational Partners claim copyright in this document and individual Organizational Partners may copyright and issue documents or standards publications in individual Organizational Partner's name based on this document. Requests for reproduction of this document should be directed to the 3GPP2 Secretariat at secretariat@3gpp2.org. Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See www.3gpp2.org for more information.
X.S0010-A
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
PRE-PAID CHARGING ENHANCEMENTS FOR CIRCUIT SWITCHED DATA AND SHORT MESSAGE SERVICES
CONTENTS
List of Figures...................................................................................................................................................v List of Tables .................................................................................................................................................. vi Revision History ............................................................................................................................................ vii Introduction.......................................................................................................................................................1 1 2 3 4 General ...............................................................................................................................................1 References ..........................................................................................................................................1 Editorial Conventions.........................................................................................................................1 Assumptions .......................................................................................................................................2
IS-826 Chapter 2 Modifications .......................................................................................................................4 3 Definitions and Concepts ...................................................................................................................4 3.1 5 Definitions............................................................................................................................4
Wireless Intelligent Network Feature Descriptions ...........................................................................5 5.A Pre-Paid Charging (PPC) .....................................................................................................5 5.A.1 Normal Procedures with Successful Outcome ......................................................5 5.A.2 Exception Procedures or Unsuccessful Outcome................................................11 5.A.3 Alternate Procedures ...........................................................................................12 5.A.4 Interactions With Other Network Services..........................................................13
IS-826 Chapter 3 Modifications......................................................................................................................17 4 5 Symbols and Abbreviations .............................................................................................................17 Network Reference Model ...............................................................................................................18 5.X Network Reference Model for Pre-Paid Charging Enhancements ....................................18 5.X.1 Interface Reference Points...................................................................................18 5.X.1.1 Reference Point M4 .......................................................................18 5.X.2 Messages Across Network Interfaces..................................................................19
IS-826 Chapter 4 Modifications .....................................................................................................................20 8 Wireless Intelligent Network (WIN Scenarios.................................................................................20 8.8 8.X Call Processing Resumption Point.....................................................................................20 WIN Pre-Paid Charging Scenarios ....................................................................................21 8.X.1 MS Registration...................................................................................................21 8.X.2 MS Call Origination: Calling Party Disconnect (SN Based) ..............................23 8.X.3 MS Call Origination: Calling Party Disconnect..................................................24 8.X.4 MS Call Origination: Calling Party Disconnect - No Pre-Call Announcement ..25 8.X.10 Three-Way Calling: Calling Party Disconnect....................................................26
i
Contents
X.S0010-A
8.X.13 8.X.16 8.X.18 8.X.20 8.X.33 8.X.41
Three-Way Calling: Insufficient Balance for Third-Party Call .......................... 27 MS Call Origination with Abbreviated Dialing.................................................. 28 Abbreviated Dialing: Insufficient Balance for Call ............................................ 29 Call Origination: Charge Rate Dependent on MS Location ............................... 30 MS-to-MS Call: SN Based.................................................................................. 31 Circuit-Switched Data Services .......................................................................... 32 8.X.41.1 MS Circuit-Switched Data Call Origination: Called Party Disconnect ..................................................................................... 33 8.X.41.2 MS Circuit-Switched Data Call Origination: Mid-Call Notification of Low Balance ............................................................................. 36 8.X.41.3 MS Circuit-Switched Data Call Origination: Service Logic Directed Call Release................................................................................... 40 8.X.41.4 Circuit-Switched Data Call Delivery: Intersystem Termination... 44 8.X.41.5 SCP-Based Call Forwarding Busy on Call Collision.................... 50 8.X.41.6 SCP-Based Call Forwarding Busy on Circuit-Switched Data Call ....................................................................................................... 57 8.X.42 Short Message Services ...................................................................................... 62 8.X.42.1 PPC for MS-Originated Short Message Accepted by the Network ....................................................................................................... 63 8.X.42.2 PPC for MS-Originated Short Message Delivered to Destination SME............................................................................................... 66 8.X.42.3 PPC for MS-Originated Short Message Not Accepted by the Network ......................................................................................... 70 8.X.42.4 PPC for MS-Originated Short Message: Message Not Accepted by Destination SME ........................................................................... 71 8.X.42.5 PPC for MS-Originated Short Message Purged by Originators Home MC ...................................................................................... 73 8.X.42.6 PPC for MS-Terminated Short Message Delivered to Subscriber 76 8.X.42.7 PPC for MS-Terminated Short Message Accepted by Home MC 81 8.X.42.8 MS-Terminated Short Message Not Delivered: Low Balance...... 82 8.X.42.9 MS-Terminated Short Message Not Delivered: MS Inaccessible 83 IS-826 Chapter 5 Modifications..................................................................................................................... 86 5 Data Transfer Services..................................................................................................................... 86 5.1 6 SS7-Based Data Transfer Services.................................................................................... 86
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
Application Services........................................................................................................................ 86 6.4 MAP Operations................................................................................................................ 86 6.4.1 General................................................................................................................ 86 6.4.1.2 Operation Specifiers ...................................................................... 86 6.4.2 Operation Definitions.......................................................................................... 86 6.4.2.13 FeatureRequest .............................................................................. 87 6.4.2.24 InterSystemPage............................................................................ 89 6.4.2.30 OriginationRequest........................................................................ 90 6.4.2.40 RoutingRequest ............................................................................. 94 6.4.2.46 TransferToNumberRequest ........................................................... 97 6.4.2.51 UnsolicitedResponse ..................................................................... 99 6.4.2.h ServiceRequest ............................................................................ 101 6.4.2.i AnalyzedInformation .................................................................. 106
ii
Contents
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
6.4.2.m 6.4.2.t 6.4.2.u 6.4.2.aa 6.4.2.ad 6.4.2.ag 6.4.2.ag 6.4.2.ax 6.5
FacilitySelectedAndAvailable .....................................................110 TBusy...........................................................................................112 TNoAnswer..................................................................................116 OAnswer ......................................................................................120 TAnswer.......................................................................................122 OCalledPartyBusy........................................................................124 ONoAnswer .................................................................................126 ShortMessageAnalyzed................................................................128
Map Parameters ...............................................................................................................131 6.5.1 General ..............................................................................................................131 6.5.1.1 Parameter Identifiers....................................................................131 6.5.2 Parameter Definitions........................................................................................132 6.5.2.2 ActionCode ..................................................................................132 6.5.2.97 Profile...........................................................................................133 6.5.2.125 SMS_CauseCode .........................................................................134 6.5.2.j TDMAServiceCode .....................................................................137 6.5.2.cu ResumePIC ..................................................................................138 6.5.2.dg TriggerList ...................................................................................139 6.5.2.dj WINOperationsCapability ...........................................................140 6.5.2.hn SMS_BearerLength......................................................................141 6.5.2.ho SMS_BillingID ............................................................................142 6.5.2.hp SMS_Event ..................................................................................143 6.5.2.hq SMS_EventNotification...............................................................144 6.5.2.hr SMS_PendingMessageCount.......................................................146 6.5.2.hs TriggerCriteria .............................................................................147
ANNEX A: ASN.1 NOTATION FOR WIN PARAMETERS ......................................................148
IS-826 Chapter 6 Modifications ...................................................................................................................149 4 Intersystem Procedures ..................................................................................................................149 4.14 4.25 4.31 4.46 Feature Request................................................................................................................149 4.14.1 MSC Detecting Feature Request .......................................................................149 InterSystem Page .............................................................................................................152 4.25.2 MSC Receiving InterSystemPage INVOKE .....................................................152 Origination Request .........................................................................................................154 4.31.1 MSC Initiating an Origination Request.............................................................154 SMS Delivery Point-to-Point...........................................................................................158 4.46.6 MC Receiving an SMSDeliveryPointToPoint INVOKE ..................................158 4.46.7 Originating MC Supplementary Services..........................................................161 4.46.9 MC Initiating SMS Delivery Point-To-Point to an MS-Based SME ................163 Analyzed Information ......................................................................................................165 4.A.1 MSC Initiating an Analyzed Information..........................................................165 Facility Selected And Available ......................................................................................168 4.E.1 MSC Initiating a Facility Selected And Available ............................................168 TBusy...............................................................................................................................170 4.M.1 MSC Initiating a TBusy.....................................................................................170 TNoAnswer......................................................................................................................173
4.A 4.E 4.M 4.N
Contents
iii
X.S0010-A
4.N.1 4.U 4.W 4.Z 4.AA 4.XX
MSC Initiating a TNoAnswer........................................................................... 173
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
OAnswer.......................................................................................................................... 176 4.U.1 MSC Initiating an OAnswer ............................................................................. 176 TAnswer .......................................................................................................................... 176 4.W.1 MSC Initiating a TAnswer................................................................................ 176 OCalledPartyBusy ........................................................................................................... 176 4.Z.1 MSC Initiating an OCalledPartyBusy............................................................... 176 ONoAnswer..................................................................................................................... 176 4.AA.1 MSC Initiating an ONoAnswer ........................................................................ 176 Short Message Analyzed ................................................................................................. 177 4.XX.1 MC Initiating Short Message Analyzed............................................................ 177 4.XX.2 SCF Receiving ShortMessageAnalyzed INVOKE........................................... 178
Operation Timer Values ................................................................................................................ 180
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
iv
Contents
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
LIST OF FIGURES
Introduction IS-826 Chapter 2 Modifications IS-826 Chapter 3 Modifications Figure X Network Reference Model for Pre-Paid Charging Enhancements ....................................18
IS-826 Chapter 4 Modifications Figure 8.8 Call Processing Resumption Point.....................................................................................................20 Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 MS Registration .................................................................................................................21 MS Circuit-Switched Data Call Origination: Called Party Disconnect.............................33 MS Circuit-Switched Data Call Origination: Mid-Call Notification of Low Balance ......36 MS Circuit-Switched Data Call Origination: Service Logic Directed Call Release .........40 Circuit-Switched Data Call Delivery: Intersystem Termination .......................................45 SCP-Based Call Forwarding Busy on Call Collision (1 of 2) ...........................................50 SCP-Based Call Forwarding Busy on Call Collision (2 of 2) ...........................................55 SCP-Based Call Forwarding Busy on Circuit-Switched Data Call (1 of 2) ......................57 SCP-Based Call Forwarding Busy on Circuit-Switched Data Call (2 of 2) ......................61
Figure 10 PPC for MS-Originated Short Message Accepted by the Network...................................63 Figure 11 PPC for MS-Originated Short Message Delivered to Destination SME ...........................66 Figure 12 PPC for MS-Originated Short Message Not Accepted by the Network............................70 Figure 13 PPC for MS-Originated Short Message: Message Not Accepted by Destination SME ....71 Figure 14 PPC for MS-Originated Short Message Purged by Originators Home MC .....................73 Figure 15 PPC for MS-Terminated Short Message Delivered to Subscriber.....................................76 Figure 16 PPC for MS-Terminated Short Message Accepted by Home MC ....................................81 Figure 17 Figure 18 MS-Terminated Short Message Not Delivered: Low Balance .........................................82 MS-Terminated Short Message Not Delivered: MS Inaccessible ....................................83
IS-826 Chapter 5 Modifications IS-826 Chapter 6 Modifications
List of Figures
X.S0010-A
LIST OF TABLES
Introduction IS-826 Chapter 2 Modifications Table 1 PPC Subscription Options .............................................................................................. 6
1 2 3 4 5 6 7 8 9
IS-826 Chapter 3 Modifications Table X Message Interfaces ....................................................................................................... 19
10 11 12 13
IS-826 Chapter 4 Modifications IS-826 Chapter 5 Modifications Table 1 Table 8 Table 10 Table 11 Table 12 MTP Message Priority Values for TIA/EIA-41 Operations......................................... 86 TIA/EIA-41 MAP Operation Specifiers....................................................................... 86 Summary of MAP Operations ...................................................................................... 86 NE Combinations for SM_ANLYZD ........................................................................ 128 TIA/EIA-41 MAP Parameter Identifiers .................................................................... 131
14 15 16 17 18 19 20 21 22 23 24 25 26
Table A-1 ASN.1 Notation for WIN Parameters......................................................................... 148 IS-826 Chapter 6 Modifications Table 1 Table 63 SCF ShortMessageAnalyzed Response...................................................................... 179 Operation Timer Values ............................................................................................. 180
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
vi
List of Tables
X.S0010-A
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
REVISION HISTORY
Revision 0 A Date June 2000 December 2003 Remarks Initial Publication of N.S0018 Revised for Publication as X.S0010-A
Revision History
vii
X.S0010-A
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
This page is intentionally left blank.
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
viii
Revision History
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
INTRODUCTION
Pre-Paid Charging (PPC) enables the subscriber to pay for telecommunication services prior to usage. This document presents a recommended plan for the implementation of Wireless Intelligent Network (WIN) capabilities that support PPC for circuit-switched data and short message services (SMS). The WIN capabilities that support PPC are for use in the Wireless Radiotelephone Service.
GENERAL
This document describes the additions and modifications to TIA/EIA/IS-826, Wireless Intelligent Network Capabilities for Pre-Paid Charging, to support circuit-switched data and short message services.
REFERENCES
This document builds on the following American National Standards Institute (ANSI) standards: TIA/EIA-664 TIA/EIA-41 TIA/EIA-664-A, Wireless Features Description; Telecommunications Industry Association; July 2000 TIA/EIA-41-D, Cellular Radiotelecommunications Intersystem Operations; Telecommunications Industry Association; December 1997 TIA/EIA/IS-737, IS-41-C Enhancements for Circuit Mode Services; Telecommunications Industry Association; December 1997 TIA/EIA/IS-807, Internationalization; August 1999 TIA/EIA-41-D Enhancements for Telecommunications Industry Association;
IS-737 IS-807
IS-826 IS-841 IS-848
TIA/EIA/IS-826, Wireless Intelligent Network Capabilities for PrePaid Charging; Telecommunications Industry Association; June 2000 TIA/EIA/IS-841, MDN Based Message Centers; Telecommunications Industry Association; September 2000 TIA/EIA/IS-848, Wireless Intelligent Network Capabilities for Enhanced Charging Services; Telecommunications Industry Association; October 2000 TIA/EIA-124-D, Wireless Radio Telecommunication Intersystem Non-Signaling Data Communication DMH (Data Message Handler); Telecommunications Industry Association; December 2001
DMH
EDITORIAL CONVENTIONS
The following editorial conventions are used for this document: underline: addition
General
Introduction
X.S0010-A
cross out: deletion
1 2
change bar: indicates additions or deletions new sub-sections are identified in the sub-section heading for clarity, new sub-sections are shown with vertical change bars but are not underlined
3 4 5 6 7 8 9 10
ASSUMPTIONS
The following assumptions were used in the development of this document: a. b. c. d. e. f. g. h. i. j. k. l. MS originated Asynchronous Data Service (ADS) shall only be of type Data Only. MS terminated Asynchronous Data Service (ADS) shall only be of types One Number per Service and Two-Stage Dialing. MS originated Group 3 Facsimile Service (G3 Fax) shall only be of type G3 Fax Only. MS terminated Group 3 Facsimile Service (G3 FAX) shall be of types One Number per Service and Two-Stage Dialing. PPC for Short Message Service (SMS) applies to both MS originated SMS (MO SMS) and MS terminated SMS (MT SMS). Single call activation is not applicable for SMS PPC. For pre-paid MS originated SMS, the short message is first to be routed to the subscriber's Home Message Center (MC). For pre-paid MS terminated SMS, the short message is routed to the subscribers Home Message Center (MC) before delivery to the Serving MSC. Support for pre-paid SMS is based on enhancements to the existing Short Message DeliveryPoint-to-Point Bearer Service specified in TIA/EIA-664. The ability of a subscriber to refuse delivery of an SMS message and not be charged for the message, is not considered in this document. A number of different SMS charging models are supported by this document. The PPC service logic is responsible for maintaining associations of multiple SMDPP message transport transactions involved in a short message delivery from originator to destination. An example would be the association of the SMDPP transport of the short message from the originating MS (SME) to the MC, with the SMDPP transport of the short message from the MC to the destination MS (SME). When the MS is not engaged in a voice or circuit-switched data call, PPC account balance notification may use SMS. When the MS is engaged in a voice call, PPC for SMS activity may use the account balance notification mechanisms used for voice calls.
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
m. n.
Introduction
Assumptions
X.S0010-A
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
o.
When the MS is engaged in a circuit-switched data call, PPC for an SMS activity may use the account balance notification mechanisms used for circuit-switched data calls. The points in processing where an MC queries or notifies the PPC subscriber's SCF for short message services can be provisioned in the FE on a per subscriber basis. This document does not specify any new capabilities (e.g., WIN triggers) that support PPC for supplementary short message services. Credit for PPC SMS messages discarded by the PPC service logic or by network MC failure or congestion may be handled by post-processing to reconcile the PPC debited funds. Details of this post-processing are outside the scope of this document. For circuit-switched data services, the MSC does not convey information about mid-call changes in the MS's service configuration to PPC service logic. Mid-call changes may occur as a result of Service Negotiation or Intersystem Handoff. For circuit-switched data services, the MSC does not convey information about Data Privacy to the PPC service logic. PPC service logic may require TDMA circuit-switched data rate information for call rating. This document enhances the TDMAServiceCode parameter to enable the MSC to specify the TDMA digital traffic channel data rate applicable at specific points in call processing. In this document, the use of the adjective accepted to describe service type information means that the service type information was: a) filtered by the Serving MSC to reflect its capabilities; b) reflects the result of negotiation of service configuration that may have occurred with the MS at the onset of the call; or c) both a and b.
p.
q. r.
s.
t. u.
v.
Assumptions
Introduction
X.S0010-A
IS-826 CHAPTER 2 MODIFICATIONS

This section provides additions and modifications to IS-826 Chapter 2, Feature Description, required to support circuit-switched data and short message services (SMS).
1 2 3 4 5 6 7
3
3.1
DEFINITIONS AND CONCEPTS

Definitions
(see IS-826, page 2-1) Chargeable Event
8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
A chargeable event is any event initiated either by the subscriber or by the network that may result in a decrease of the subscribers PPC account balance. A chargeable event may occur during a voice, short message or circuit-switched data telecommunications service. A chargeable event has a beginning and an end, which are used to start and stop the corresponding PPC invocation. The remainder of this section is retained unchanged.
25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
IS-826 Chapter 2 Modications
Denitions and Concepts
X.S0010-A
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
WIRELESS INTELLIGENT NETWORK FEATURE DESCRIPTIONS

Pre-Paid Charging (PPC)
(see IS-826 page 1-2)
5.A
PPC allows the subscriber to pay for voice telecommunication services prior to usage. A PPC subscriber establishes an account with the service provider to access voice telecommunications services in home and roaming networks. Charges for voice telecommunication services are applied to the PPC account by decrementing the account in real time. The PPC subscriber may be notified about the account information at the beginning, during, or at the end of the voice telecommunications service. When the account balance is low, the subscriber may be notified so that the subscriber may refill the account. When the account balance is below a pre-defined threshold, the subscribers use of voice telecommunications services may be de-authorized. PPC may be activated for all telecommunication services calls or for a single voice or circuit-switched data call on a single call basis. For All-ServicesCalls activation, charges for all voice telecommunications services invoked are applied to the PPC account. For Single-Call activation, only charges for voice or circuit-switched data telecommunications services invoked in association with the call origination are applied to the PPC account. Applicability to Telecommunications Services PPC is applicable to voice, short message and circuit-switched data telecommunications services. For circuit-switched data telecommunications services, PPC is only applicable for the following: MS originated ADS of type Data Only. MS terminated ADS of types One Number per Service and Two-Stage Dialing. MS originated Group 3 Fax (G3Fax) of type Data Only. MS terminated Group 3 FAX (G3 FAX) of types One Number per Service and Two-Stage Dialing.
In the future, PPC may apply to other telecommunications services. In this document, the usual billing practice is referred to as post-usage billing (PUB).
5.A.1
Normal Procedures with Successful Outcome

Authorization PPC is provided after pre-arrangement with the service provider.
Wireless Intelligent Network Feature Descriptions
X.S0010-A
The authorization may have the following subscription options:

Subscription Options Single-Call Activation Values Demand. The subscriber is authorized to activate PPC for a single voice or circuit switched data call origination. Permanent. PPC may not be activated for single voice or circuit switched data call originations. All-ServicesCalls Activation Demand. The subscriber is authorized to control the activation and de-activation of PPC for all telecommunication services calls. Permanent. PPC is active for all telecommunication services calls while authorized.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Table 1 PPC Subscription Options De- Authorization PPC may be withdrawn at the subscribers request or for administrative reasons. Registration PPC has no registration. De-Registration PPC has no de-registration. Activation If the subscriber is authorized for Permanent All-ServicesCalls Activation, PPC is activated upon authorization. PPC may be activated by a Demand All-ServicesCalls Activation authorized subscriber by specifying a feature code, as in: * FC +
SEND
19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
41 42
If the activation is accepted, the system shall indicate success with feature confirmation treatment1. If PPC is activated while a call or short message delivery is in progress, the activation shall not affect the call or short message delivery in progress. PPC may be activated by a Demand Single-Call Activation authorized subscriber by specifying a feature code and a termination address: * FC + # + termination address + * FC + termination address +
SEND
43 44 45 46 47 48 49 50
; or
51 52
SEND
53 54 55 56 57 58
1. Feature conrmation treatment for circuit-switched data services may be limited to text notications.
59 60
X.S0010-A
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
If the activation is accepted, the system shall indicate success with feature confirmation treatment1. In this case PPC applies only to charges for voice or circuit-switched data telecommunication services associated with the call origination attempt. De-Activation PPC shall be de-activated upon de-authorization. PPC may be de-activated by a Demand All-ServicesCalls Activation authorized subscriber by specifying a feature code, as in: * FC0 +
SEND
If the de-activation is accepted, the system shall indicate success with feature confirmation treatment1. If PPC is de-activated while a call or short message delivery is in progress, the de-activation shall not affect the call or short message delivery in progress. For a Single-Call activation, PPC is automatically de-activated after the single call attempt is cleared. Invocation PPC is invoked when a chargeable event begins and PPC is active. Normal Operation with Successful Outcome PPC subscribers may have a normal PUB account. For those subscribers, the PPC and PUB service profiles do not have to be identical. For a subscriber who has both PPC and PUB profiles, the Single-Call PPC profile has precedence over the All-ServicesCalls profile. A PPC subscriber may request the notification of current PPC account information at any time from the PPC Pre-Paid Charging system, while not in an active call.
Normal operation with account balance above threshold
PPC subscribers can use all subscribed voice telecommunication services in a normal manner when their account balance is above a threshold level. When PPC is invoked, the PPC account is decremented in real time. Telecommunication Voice telecommunication services may be charged to the PPC account at a flat rate, on invocation, or according to usage duration, type of service, or any combination thereof. The PPC subscriber may be notified about the account information and charges associated with voice telecommunication services at the beginning, during and/or at the end of the voice telecommunication services. Notification may be provided by tone announcement or display text sent to the MS (e.g., SMS). Text notifications are sent to the MS for circuitswitched data services. If PPC is active, the PPC account balance is above a threshold level, and Call Delivery is provisioned, Call Delivery shall be supported.
X.S0010-A
If PPC is active, the PPC account balance is above a threshold level, and SMS is provisioned, SMS shall be supported. Final routing information is required by the PPC system before accurate charging can be applied against the PPC account.
Normal operation when a threshold condition is reached during a voice call
1 2 3 4 5 6 7 8 9 10 11 12
If the PPC account balance reaches a threshold level while one or more voice calls are in progress, one of the following procedures can be used: The call continues without interruption. If the PPC subscriber is engaged in one of the calls, the subscriber is notified. If the subscriber is not engaged in one of the calls, the subscriber or the subscribers proxy (e.g., voice mail system, assistant, etc.) may be notified. The call continues without interruption. If the PPC subscriber is engaged in one of the calls, the subscriber is notified during the call. If the subscriber is not engaged in one of the calls, the subscriber or the subscribers proxy may be notified. Every call that is not ended in a timely manner is dropped.
13 14 15 16 17 18 19 20 21 22 23 24
If the PPC subscriber does not disconnect at the end of a call, the subscriber may be connected to customer service or to an automatic system to enable the subscriber to refill the account. If the PPC account balance reaches a threshold level, the invocation of another chargeable service may be denied. Notification may be provided by tone, announcement, voice mail, SMS, etc. Notifications are played only to the PPC subscriber or to the subscribers proxy (e.g., voice mail system), not to the other parties on the calls.
Normal operation when threshold condition is reached during circuit-switched data call
25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42
If the PPC account balance reaches a threshold level while a circuit-switched data call is in progress, one of the following procedures can be used: The call continues without interruption. A text notification is sent to the MS. The call continues without interruption. A text notification is sent to the MS. The call is dropped if it is not ended in a timely manner.
43 44 45 46 47 48 49 50 51 52
If the PPC account balance reaches a threshold level, the invocation of another chargeable service may be denied.
Normal operation when a threshold condition is reached during short message delivery
53 54 55 56 57 58 59 60
If the PPC account balance reaches a threshold level while a short message delivery is in progress, one of the following procedures can be used: The short message delivery continues without interruption.
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
A text notification is sent to the MS. The short message delivery continues without interruption. A text notification is sent to the MS. The message is discarded without delivery.
If the PPC account balance reaches a threshold level, the invocation of another chargeable service may be denied.
Normal operation with insufficient balance for a voice call
If the PPC account balance is below a pre-set threshold, a notification shall be provided to the subscriber. If the subscriber originates a voice call, the network may route the call to customer service to help the subscriber to refill the account. Incoming calls may be given the subscriber inaccessible treatment and an appropriate notification may be provided to the PPC subscriber (e.g., special alerting, text message). Some call cases may be allowed to proceed normally such as: Calls to emergency services Calls to and from customer service
Normal operation with insufficient balance for a circuit-switched data call
If the PPC account balance is below a pre-set threshold, a notification shall be provided to the subscriber. If the subscriber originates a circuit-switched data call, the network may send a text notification to the MS to help the subscriber refill the account and deny the call origination. Incoming calls may be given subscriber inaccessible treatment and an appropriate notification may be provided to the PPC subscriber (e.g., special alerting, text message).
Normal operation with insufficient balance for SMS
If the PPC account balance is below a pre-set threshold, a notification shall be provided to the subscriber. If the subscriber originates a short message, the message origination may be denied and a text notification sent to the MS to help the subscriber refill the account. For short messages destined for the subscriber, the message may be discarded and a text notification sent to the MS (e.g., text message, special alerting).
Chargeable Events
The chargeable events for All-ServicesCalls activation subscribers: 1. Call Voice call termination to a PPC subscriber 2. beginning: alerting, or called party answers, end: disconnect (network- or user-initiated), or connection failure (radio or network), or abandon, or reject, or no answer
Call Voice call origination by a PPC subscriber beginning: traffic voice channel seizure, or ring back, or called party answers, end: busy, or disconnect (network- or user-initiated), or connection failure (radio or network), or abandon, or no answer
3.
Wireless services invoked on behalf of the PPC subscriber during a voice call:
X.S0010-A
In cases where the invocation of services causes calls to be placed, these calls are chargeable events with the same beginning and end conditions as described above. Additionally, the activation or the invocation of services may be chargeable events.
1 2 3 4 5 6 7
4.
Wireless Services invoked on behalf of the PPC subscriber outside a voice call In cases where the invocation of wireless services causes calls to be placed, these calls are chargeable events subject to the same beginning and end conditions as described above. Additionally, the activation or the invocation of wireless services may themselves be chargeable events.
8 9 10 11 12 13 14
5.
Short message origination by a PPC subscriber the short message is accepted by the network the message is discarded by the network the message is delivered to the recipient network or an intervening network
15 16 17 18 19 20 21 22 23
6.
Short message destined for a PPC subscriber the short message is accepted by the network the message is discarded by the network the message is delivered to the PPC subscriber
24 25 26 27
7.
Other charges associated with the PPC account (e.g., monthly fees, SMS supplementary service usage.)
28 29 30 31 32 33 34 35
The chargeable events for Single-Call activation subscribers: 1. Call Voice call origination 2. Same as All-ServicesCalls chargeable events
Services invoked on behalf of the PPC subscriber associated with the voice call origination In cases where the invocation of wireless services causes calls to be placed, these calls are chargeable events subject to the same beginning and end conditions as those described above. Additionally, the activation or the invocation of wireless services may themselves be chargeable events.
36 37 38 39 40 41 42 43
3.
Other charges: same as All-ServicesCalls chargeable events
44 45
Call Detail Record The system should record call detail information for the following: a. b. c. PPC activation PPC de-activation PPC invocation
46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
See DMH for the specific information to be included for each element.
10
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
5.A.2
Exception Procedures or Unsuccessful Outcome

Registration None identified. De-Registration None identified. Activation
Permanent Activation
If the subscriber is not authorized for a request, the system shall apply feature denial treatment (e.g., tone, announcement, text notification)1.
Demand Activation
If the subscriber is not authorized for the request, the system shall apply feature denial treatment (e.g., tone, announcement, text notification)1 when activation is attempted. If PPC cannot be activated, an indication shall be provided to the subscriber that PPC is not available (e.g., tone, announcement, text notification)2. If the subscriber is authorized for PUB, then PUB shall remain active and a notice to this effect may also be presented to the subscriber. De-Activation If the subscriber is not authorized for a request, the system shall apply feature denial treatment (e.g., tone, announcement, text notification)1. If PPC cannot be de-activated, a notification (e.g., tone, announcement, text notification SMS or tone)2 that PPC is still active shall be presented to the subscriber. For Single-Call activation, if PPC cannot be de-activated at the end of the call origination, PPC shall remain active and a notice to this effect may also be presented to the subscriber2.
Demand De-Activation
If the subscriber is not authorized for the request, the system shall apply feature denial treatment when de-activation is attempted (e.g., tone, announcement, text notification)1.
1. Feature denial treatment for circuit-switched data services may be limited to text notications. 2. The treatment for circuit-switched data services may be limited to text notications.
11
X.S0010-A
Invocation If PPC cannot be invoked for a call origination, an appropriate error indication is provided to the subscriber (e.g., tone, announcement, text notification)1 and the call origination is denied. If PPC cannot be invoked for a call to a PPC subscriber, subscriber inaccessible treatment may be provided to the calling party and an appropriate notification may be provided to the PPC subscriber1. If PPC cannot be invoked for services invoked on behalf of the PPC subscriber, the service shall be denied. An appropriate notification may be provided to the PPC subscriber1. Some calls, such as calls to and from customer service, may be allowed to proceed normally even if the PPC subscribers account balance does not allow normal call origination and termination. Exceptions While Roaming If a subscriber with PPC active roams into a system that does not support PPC, the following services may be available to the subscriber: 1. 2. 3. 4. 5. 6. 7. 8. Calls to home customer service or to local customer service. Receive text notification SMS messages informing the subscriber that PPC is unavailable. Receive announcements indicating PPC is unavailable. Receive a notice to activate PUB if that service is authorized. Activate PUB. Calls to a single number specified by the home system (e.g., hot line). Calls to locally allowed numbers (e.g., emergency service calls). Credit card calls.
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
Exceptions During Intersystem Handoff None identified.
43 44 45 46
5.A.3
Alternate Procedures
If the subscribers account balance is below the threshold, the subscriber may activate a PUB account to obtain service.
47 48 49 50 51 52 53 54 55 56 57 58
1. The treatment for circuit-switched data services may be limited to text notications.
59 60
12
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
5.A.4
Interactions With Other Network Services

Asynchronous Data Service (ADS) PPC is invoked before ADS.
Not applicable.
Call ForwardingBusy (CFB) PPC is invoked before CFB. Call ForwardingDefault (CFD) PPC is invoked before CFD. Call ForwardingNo Answer (CFNA) PPC is invoked before CFNA. Call ForwardingUnconditional (CFU) PPC is invoked before CFU. Call Transfer (CT) Interaction between PPC and CT is beyond the scope of this standard. Call Waiting (CW) PPC is invoked before CW. Calling Name Presentation (CNAP) PPC is invoked before CNAP. Calling Name Restriction (CNAR) None identified. Calling Number Identification Presentation (CNIP) PPC is invoked before CNIP. Calling Number Identification Restriction (CNIR) None identified. Conference Calling (CC) Interaction between PPC and CC is beyond the scope of this standard.
13
X.S0010-A
Data Privacy (DP) PPC is invoked before DP.

Not applicable.
1 2 3 4 5 6
Do Not Disturb (DND) PPC is invoked before DND. Emergency Services (9-1-1) Emergency Services takes precedence over PPC. Flexible Alerting (FA) Interaction between PPC and FA is beyond the scope of this standard. Group 3 Facsimile (G3 Fax) PPC is invoked before G3 Fax.
Not applicable.
7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
Incoming Call Screening (ICS) PPC is invoked before ICS. Message Waiting Notification (MWN) PPC is invoked before MWN. Mobile Access Hunting (MAH) Interaction between PPC and MAH is beyond the scope of this standard. Network Directed System Selection (NDSS) None identified. Non-Public Mode Service (NP) PPC interaction with NP is for further study. Over-the-Air Service Provisioning (OTASP) None identified. Password Call Acceptance (PCA) PPC is invoked before PCA.
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
14
X.S0010-A
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
Preferred Language (PL) Announcements related to PPC should be presented to the PPC subscriber in the subscribers preferred language. Text notifications related to PPC shall be sent to the MS in the subscribers preferred language. Pre-Paid Charging (PPC) Not applicable. Priority Access and Channel Assignment (PACA) PPC is invoked before PACA. Remote Feature Control (RFC) Interaction between PPC and RFC is beyond the scope of this standard. Selective Call Acceptance (SCA) PPC is invoked before SCA. Service Negotiation (SN) PPC interaction with SN is for further study. Short Message Services (SMS) PPC is invoked upon detection of an SMS chargeable events (see 5.A.1).
Not applicable.
Subscriber Confidentiality (SC) None identified. Subscriber PIN Access (SPINA) PPC interaction with SPINA is for further study. Subscriber PIN Intercept (SPINI) PPC interaction with SPINI is for further study. Three-Way Calling (3WC) PPC is invoked before 3WC. User Group ID (UGID) PPC interaction with UGID is for further study.
15
X.S0010-A
Voice Message Retrieval (VMR) PPC is invoked before VMR. Voice Privacy (VP) PPC is invoked before VP.
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
16
X.S0010-A
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

This section provides additions and modifications to IS-826 Chapter 3, Modifications to TIA/EIA-41.1-D Functional Overview, required to support circuit-switched data and short message services.
SYMBOLS AND ABBREVIATIONS

(See TIA/EIA-41, page 1-14) (See IS-771, page 3-8) (See IS-826, page 3-9)
The omitted portion of this section is retained without modification.

RESUMEPIC ResumePIC parameter
SM_ANLYZD sm_anlyzd SMS_BRLEN SMS_BILLID SMS_EVENT SMS_EVENTNOT SMS_PMCNT
ShortMessageAnalyzed INVOKE ShortMessageAnalyzed RETURN RESULT SMS_BearerLength parameter SMS_BillingID parameter SMS_Event parameter SMS_EventNotification parameter SMS_PendingMessageCount parameter
Symbols and Abbreviations
17
X.S0010-A
5
5.X
NETWORK REFERENCE MODEL

Network Reference Model for Pre-Paid Charging Enhancements
(New Section for TIA/EIA-41.1-D, section 5)
1 2 3 4 5 6 7 8 9 10 11 12 13
The network reference model for Pre-Paid Charging enhancements for short message services is shown below:
M3
14 15 16
SME
17 18 19 20 21
M1
22
M2
23 24 25
MSC
MC
26
HLR
27 28 29 30 31
T1
M4
T2
32 33 34 35 36
SCP
37 38 39 40
Figure X Network Reference Model for Pre-Paid Charging Enhancements
41 42 43
5.X.1
Interface Reference Points

An interface exists when two Network Entities are interconnected through exactly one Reference Point.
44 45 46 47 48 49
5.X.1.1
Reference Point M4 Reference point M4 is the interface between the MC and the SCP.
50 51 52 53 54 55 56 57 58 59 60
18
Network Reference Model
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
5.X.2
Messages Across Network Interfaces

This section describes the protocols and messages used across network interfaces for PrePaid Charging Enhancements for short message services. Table X Message Interfaces
Network Interface M4 Network Entity MC SCP Protocol TIA/EIA-41 Operations ShortMessageAnalyzed
Network Reference Model for Pre-Paid Charging Enhancements
19
X.S0010-A

This section provides additions and modifications to IS-826 Chapter 4, Modifications to TIA/EIA-41.3-D to Automatic Roaming Information Flows, required to support circuitswitched data and short message services.
1 2 3 4 5 6 7 8
WIRELESS INTELLIGENT NETWORK (WIN SCENARIOS

Call Processing Resumption Point
(See IS-771 Chapter 4, page 4-152) This scenario illustrates the operation when a RESUMEPIC parameter is included in the response from service logic to an SSF/CCF (i.e., MSC). Originating or Serving System SSF/ CCF WIN_OPERATION [Parameter Set] TIMER SCF
9 10 11 12 13
8.8
14 15 16 17 18 19 20 21 22 23 24 25 26
27 28 29 30
Other PDUs as applicable
31
32 33 34 35
win_operation [Parameters, RESUMEPIC]
36 37 38 39
Figure 8.8 Call Processing Resumption Point a. An armed trigger is encountered at the SSF/CCF (e.g., Originating or Terminating MSC). The criteria for the trigger are satisfied and the appropriate query (e.g., LOCREQ, TBUSY) is sent to the service control function (SCF) per the address information associated with the trigger. The response timer for the operation is started. b. Other protocol data units (PDUs) may be exchanged according to the needs of the service logic program (SLP) at the SCF.
40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
c. The RETURN RESULT for the operation invoked at Step-a is sent to the SSF/CCF and includes a RESUMEPIC parameter. The SSF/CCF examines the received information, and if it is compatible with the current state of call processing, the SSF/CCF resumes call processing at the resumption point indicated by the RESUMEPIC parameter. Note: If the RESUMEPIC parameter is not included in the RETURN RESULT, the SSF/CCF continues call processing where pre-WIN procedures would continue.
20
Wireless Intelligent Network (WIN Scenarios
X.S0010-A
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
8.X
8.X.1
WIN Pre-Paid Charging Scenarios

MS Registration
(See IS-826 Chapter 4, page 4-2)
This scenario describes MS registration in a new serving system by a PPC subscriber with PPC active and an account balance above threshold. The subscribers service profile indicates the circuit-switched data services (and other subscriber services) that are applicable for the MS.
Serving HLR VLR MSC
REGNOT [MSCID, MSID, ESN, TRANSCAP, WINCAP, QUALCODE] a REGNOT [MSCID, MSID, ESN, TRANSCAP, WINCAP, QUALCODE] RNT regnot [Profile {TRIGADDRLIST}] RNT c regnot [Profile {TRIGADDRLIST}]
Figure 1 MS Registration a. The Serving MSC determines that a roaming MS is within its service area. The Serving MSC sends a REGNOT to its VLR requesting subscriber profile and authorization information. The TRANSCAP parameter is set to indicate the Serving MSC can process the TRIGADDRLIST parameter. The WINCAP parameter is set to indicate the WIN capabilities of the Serving MSC.
Parameters MSCID MSID ESN TRANSCAP WINCAP QUALCODE Serving MSC MSCID. Served MS MSID. Served MS ESN. Serving MSCs transaction capability. Serving MSCs WIN capability. Type of qualification information required. Usage Type R R R R R R
b. The Serving VLR determines the MS is not known to the VLR. The Serving VLR forwards the REGNOT to the HLR associated with the MS. c. The HLR determines that authorization can be granted to the MS. It returns the requested information to the Serving VLR in the regnot. The TRIGADDRLIST parameter is set to indicate the Origination_Attempt_Authorized, Calling_Routing_Address_Available, O_Answer, O_Disconnect, T_Answer, and T_Disconnect triggers are active and to specify routing to the network entity (e.g., SCP, SN) that contains the PPC service logic program. For circuit-switched data services, the
21
X.S0010-A
CDMAServiceOptionsList parameter indicates the authorized service options for a CDMA MS; the TDMADataFeaturesIndicator parameter indicates the allowed data services for a TDMA MS. Note: the TRIGADDRLIST parameter may also arm triggers for other WIN services. d. The VLR forwards the regnot to the Serving MSC.
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
22
X.S0010-A
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
8.X.2
MS Call Origination: Calling Party Disconnect (SN Based)

This scenario describes PPC invocation upon call origination by a PPC subscriber with PPC active and an account balance above threshold. The calling MS disconnects first and no end of call announcement is provided to the subscriber. d. The Serving MSC analyzes the dialed digits and prepares to route the call. The MSC detects the Calling_Routing_Address_Available trigger and sends an ANLYZD to the SN associated with this trigger.
Parameters MSCID MSID MDN BILLID DGTSDIAL RoutingInfo: [DSTDGTS] [CARDGTS] [ROUTDGTS] TRIGTYPE TOD TDO Serving MSC MSCID. Served MS MSID. Mobile directory number. Include if available. BillingID. Used to relate queries for this call. Digits entered by served MS. Call routing information: DestinationDigits. The network address of the destination. CarrierDigits. Interexchange carrier for call setup. Include if applicable. RoutingDigits. Special routing instructions. Include if applicable. Indicates the trigger encountered. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time. R O O R R R Usage Type R R O R RO
The remainder of this section is retained unchanged.
23
X.S0010-A
8.X.3
MS Call Origination: Calling Party Disconnect

1 2 3 4 5 6 7 8 9 10 11 12 13
This scenario describes PPC invocation upon call origination by a PPC subscriber with PPC active and an account balance above threshold. The calling party disconnects first, hence no end of call announcement is provided. d. The Serving MSC analyzes the dialed digits and prepares to route the call. The MSC detects the Calling_Routing_Address_Available trigger and sends an ANLYZD to the SCP associated with this trigger.
Parameters MSCID TRANSCAP WINCAP MSID MDN BILLID DGTSDIAL RoutingInfo: [DSTDGTS] [CARDGTS] [ROUTDGTS] TRIGTYPE TOD TDO Serving MSC MSCID. Serving MSCs transaction capability. Serving MSCs WIN capability. Served MS MSID. Mobile directory number. Include if available. BillingID. Used to relate queries for this call. Digits entered by served MS. Call routing information: DestinationDigits. The network address of the destination. CarrierDigits. Interexchange carrier for call setup. Include if applicable. RoutingDigits. Special routing instructions. Include if applicable. Indicates the trigger encountered. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time. R O O R R R Usage Type R R R R O R RO
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
24
X.S0010-A
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
8.X.4
MS Call Origination: Calling Party Disconnect - No Pre-Call Announcement

This scenario differs from the previous scenario in that no announcement is played when an MS originates the call to inform the subscriber of their current account balance. The calling party disconnects first and there is no end of call announcement. d. The Serving MSC analyzes the dialed digits and prepares to route the call. The MSC detects the Calling_Routing_Address_Available trigger and sends an ANLYZD to the SCP associated with this trigger.
Parameters MSCID TRANSCAP WINCAP MSID MDN BILLID DGTSDIAL RoutingInfo: [DSTDGTS] [CARDGTS] [ROUTDGTS] TRIGTYPE TOD TDO Serving MSC MSCID. Serving MSCs transaction capability. Serving MSCs WIN capability. Served MS MSID. Mobile directory number. Include if available. BillingID. Used to relate queries for this call. Digits entered by served MS. Call routing information: DestinationDigits. The network address of the destination. CarrierDigits. Interexchange carrier for call setup. Include if applicable. RoutingDigits. Special routing instructions. Include if applicable. Indicates the trigger encountered. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time. R O O R R R Usage Type R R R R O R RO
25
X.S0010-A
8.X.10
Three-Way Calling: Calling Party Disconnect

1 2 3 4 5 6 7 8 9 10 11 12
This scenario describes PPC invocation for a Three-Way call. The calling party disconnects before the last party on the call and no end of call announcement is provided. x. The Serving MSC analyzes the dialed digits and prepares to route the call to the third party. The MSC detects the Calling_Routing_Address_Available trigger and sends an ANLYZD to the SCP associated with this trigger.
Parameters MSCID TRANSCAP WINCAP MSID MDN BILLID DGTSDIAL RoutingInfo: [DSTDGTS] [CARDGTS] [ROUTDGTS] TRIGTYPE FEATIND TOD TDO Serving MSC MSCID. Serving MSCs transaction capability. Serving MSCs WIN capability. Served MS MSID. Mobile directory number. Include if available. BillingID. Used to relate queries for this call. Digits entered by served MS. Call routing information: DestinationDigits. The network address of the destination. CarrierDigits. Interexchange carrier for call setup. Include if applicable. RoutingDigits. Special routing instructions. Include if applicable. Indicates the trigger encountered. FeatureIndicator. Indicates the feature invoked with the call (e.g., Three-Way Calling). TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time. R O O R R R R Usage Type R R R R O R RO
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
26
X.S0010-A
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
8.X.13
Three-Way Calling: Insufficient Balance for Third-Party Call

This scenario describes PPC invocation for a Three-Way call with an insufficient balance for the third-party call. x. The Serving MSC analyzes the dialed digits and prepares to route the call to the third party. The MSC detects the Calling_Routing_Address_Available trigger and sends an ANLYZD to the SCP associated with this trigger.
Parameters MSCID TRANSCAP WINCAP MSID MDN BILLID DGTSDIAL RoutingInfo: [DSTDGTS] [CARDGTS] [ROUTDGTS] TRIGTYPE FEATIND TOD TDO Serving MSC MSCID. Serving MSCs transaction capability. Serving MSCs WIN capability. Served MS MSID. Mobile directory number. Include if available. BillingID. Used to relate queries for this call. Digits entered by served MS. Call routing information: DestinationDigits. The network address of the destination. CarrierDigits. Interexchange carrier for call setup. Include if applicable. RoutingDigits. Special routing instructions. Include if applicable. Indicates the trigger encountered. FeatureIndicator. Indicates the feature invoked with the call (e.g., Three-Way Calling). TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time. R O O R R R R Usage Type R R R R O R RO
27
X.S0010-A
8.X.16
MS Call Origination with Abbreviated Dialing

1 2 3 4 5 6 7 8 9 10 11 12 13
This scenario describes PPC invocation for an MS call origination with a WIN-based abbreviated dialing service. The subscriber enters # and the abbreviated dialing number as in: h. The Serving MSC prepares to route the call. The MSC detects the Calling_Routing_Address_Available trigger and sends an ANLYZD to SCP-1, the SCP associated with this trigger.
Parameters MSCID WINCAP MSID MDN BILLID DGTSDIAL RoutingInfo: [DSTDGTS] [CARDGTS] [ROUTDGTS] TRIGTYPE TOD TDO Serving MSC MSCID. Serving MSCs WIN capability. Served MS MSID. Mobile directory number. Include if available. BillingID. Used to relate queries for this call. Digits entered by served MS. Call routing information: DestinationDigits. The network address of the destination. CarrierDigits. Interexchange carrier for call setup. Include if applicable. RoutingDigits. Special routing instructions. Include if applicable. Indicates the trigger encountered. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time. R O O R R R Usage Type R R R O R RO
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
28
X.S0010-A
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
8.X.18
Abbreviated Dialing: Insufficient Balance for Call

This scenario describes PPC invocation for an MS call origination with a WIN-based abbreviated dialing service. Due to an insufficient balance, the call is disconnected. h. The Serving MSC prepares to route the call. The MSC detects the Calling_Routing_Address_Available trigger and sends an ANLYZD to SCP-1, the SCP associated with this trigger.
Parameters MSCID WINCAP MSID MDN BILLID DGTSDIAL RoutingInfo: [DSTDGTS] [CARDGTS] [ROUTDGTS] TRIGTYPE TOD TDO Serving MSC MSCID. Serving MSCs WIN capability. Served MS MSID. Mobile directory number. Include if available. BillingID. Used to relate queries for this call. Digits entered by served MS. Call routing information: DestinationDigits. The network address of the destination. CarrierDigits. Interexchange carrier for call setup. Include if applicable. RoutingDigits. Special routing instructions. Include if applicable. Indicates the trigger encountered. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time. R O O R R R Usage Type R R R O R RO
29
X.S0010-A
8.X.20
Call Origination: Charge Rate Dependent on MS Location

1 2 3 4 5 6 7 8 9 10 11 12 13
This scenario describes PPC invocation upon call origination by a PPC subscriber with PPC active and an account balance above threshold. The rate of charging for the call is dependent on the location of the MS. d. The Serving MSC analyzes the dialed digits and prepares to route the call. The MSC detects the Calling_Routing_Address_Available trigger and sends an ANLYZD to the SN associated with this trigger.
Parameters MSCID WINCAP MSID MDN BILLID DGTSDIAL RoutingInfo: [DSTDGTS] [CARDGTS] [ROUTDGTS] TRIGTYPE TOD TDO SCELLID LOCID Serving MSC MSCID. Serving MSCs WIN capability. Served MS MSID. Mobile directory number. Include if available. BillingID. Used to relate queries for this call. Digits entered by served MS. Call routing information: DestinationDigits. The network address of the destination. CarrierDigits. Interexchange carrier for call setup. Include if applicable. RoutingDigits. Special routing instructions. Include if applicable. Indicates the trigger encountered. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time. ID of the cell serving the MS. Location Area ID. Include if available. R O O R R R R O Usage Type R R R O R RO
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
30
X.S0010-A
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
8.X.33
MS-to-MS Call: SN Based

This scenario describes an MS-to-MS call. Both users are PPC subscribers of the same system. Both subscribers are currently in the home service area. d. The Serving MSC analyzes the dialed digits and prepares to route the call. The MSC detects the Calling_Routing_Address_Available trigger and sends an ANLYZD to the SN associated with this trigger.
Parameters MSCID WINCAP MSID MDN BILLID TOD TDO RoutingInfo: [DSTDGTS] [CARDGTS] [ROUTDGTS] DGTSDIAL TRIGTYPE Serving MSC MSCID. Serving MSCs WIN capability. Served MS MSID. Mobile directory number. Include if available. BillingID. Used to relate queries for this call. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time. Call routing information: DestinationDigits. The network address of the destination. CarrierDigits. Interexchange carrier for call setup. Include if applicable. RoutingDigits. Special routing instructions. Include if applicable. Digits entered by served MS. Indicates the trigger encountered. R O O RO R Usage Type R R R O R R R
31
X.S0010-A
8.X.41
Circuit-Switched Data Services

(new for IS-826 Chapter 4, Section 8.X)
1 2 3 4 5 6 7 8 9
The scenarios in this section depict interactions between network entities in situations related to PPC support of circuit-switched data services (ADS and G3 FAX) under automatic roaming conditions. PPC is applicable for the following: MS originated ADS of type Data Only. MS terminated ADS of types One Number per Service and Two-Stage Dialing. MS originated Group 3 Fax (G3Fax) of type Data Only. MS terminated Group 3 FAX (G3 FAX) of types One Number per Service and Two-Stage Dialing.
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
PPC is not applicable to other types of ADS and G3 FAX.
32
X.S0010-A
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
8.X.41.1
MS Circuit-Switched Data Call Origination: Called Party Disconnect This scenario illustrates PPC invocation upon a circuit-switched data call origination by a PPC subscriber with PPC active and an account balance above threshold. The call is initially authorized by the PPC service platform. The PPC platform is notified prior to call setup to enable the current account balance to be sent to the MS. The called party disconnects first.
Serving SCP MSC IWF MS origination ORREQ [MSCID, MSID, MDN, ServiceType, BILLID, DGTSDIAL, TRIGTYPE] orreq [DMH_SVCID] ORT c d anlyzd [DISPTEXT, ACTCODE] ANZT e display text call setup f g h OANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO] answer i j
a b
ANLYZD [MSCID, MSID, MDN, BILLID, DGTSDIAL, ServiceType, RoutingInfo, TRIGTYPE, TOD, TDO]
answer
disconnect ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO] odisconnect [ ] ODT
k l m MS release n
Figure 2 MS Circuit-Switched Data Call Origination: Called Party Disconnect a. An MS circuit-switched data call origination with dialed digits is received by the Serving MSC. b. The Serving MSC detects the Origination_Attempt_Authorized trigger and sends an ORREQ to the network entity (SCP) associated with this trigger.
Parameters MSCID MSID Serving MSC MSCID. Served MS MSID. Usage Type R R
33
X.S0010-A
Parameters MDN ServiceType: [CDMAServiceOption] [TDMAServiceCode] BILLID DGTSDIAL TRIGTYPE
Usage Mobile directory number. Include if available. The service type for the call: Indicates the requested CDMA service option for the call (e.g., ADS, G3Fax). Indicates the requested TDMA service code for the call. BillingID. Used to relate queries for this call. Digits entered by served MS. Indicates the trigger encountered.
Type O R O O R R R
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
c. The SCP determines the subscriber is authorized for the requested data service and has PPC active. The subscribers account balance is above the threshold level. The SCP sends an orreq to the Serving MSC to indicate call processing shall continue. The DMH_SVCID parameter is set to indicate that PPC was invoked. d. The Serving MSC analyzes the dialed digits and prepares to route the call. The MSC detects the Calling_Routing_Address_Available trigger and sends an ANLYZD to the network entity (SCP) associated with this trigger.
Parameters MSCID MSID MDN BILLID DGTSDIAL ServiceType: [CDMAServiceOption] [TDMAServiceCode] RoutingInfo: [DSTDGTS] [CARDGTS] [ROUTDGTS] TRIGTYPE TOD TDO Serving MSC MSCID. Served MS MSID. Mobile directory number. Include if available. BillingID. Used to relate queries for this call. Dialed digits. The service type for the call: Indicates the current CDMA service option for the call (e.g., ADS, G3Fax). Indicates the current TDMA service code for the call. Call routing information: DestinationDigits. The network address of the destination. CarrierDigits. Interexchange carrier for call setup. Include if applicable. RoutingDigits. Special routing instructions. Include if applicable. Indicates the trigger encountered. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time. R O O R R R Usage Type R R O R R R O O
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
34
X.S0010-A
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
e. The SCP sends an anlyzd to the Serving MSC. The DISPTEXT parameter is set to indicate the current account balance. The ACTCODE parameter is set to indicate that display text shall be presented to the calling MS. f. The Serving MSC sends the received display text to the MS. g. The MSC extends the MS originated call. h. The call is answered by the called party. i. The Serving MSC detects the O_Answer trigger and sends an OANSWER to the network entity associated with this trigger.
Parameters MSCID MSID MDN BILLID TRIGTYPE TOD TDO Serving MSC MSCID. Served MS MSID. Mobile directory number. Include if available. BillingID. Used to relate queries for this call. Indicates the trigger encountered. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time. Usage Type R R O R R R R
Upon receipt of the OANSWER, the SCP begins decrementing the subscribers account balance. j. The call is cut through and connected. k. The called party disconnects. l. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT to the network entity associated with this trigger.
Parameters MSCID MSID MDN BILLID TRIGTYPE RELCAUSE TOD TDO Serving MSC MSCID. Served MS MSID. Mobile directory number. Include if available. BillingID. Used to relate queries for this call. Indicates the trigger encountered. Call release cause. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time. Usage Type R R O R R R R R
Upon receipt of the ODISCONNECT, the SCP stops decrementing the subscribers account balance. m. The SCP sends an empty odisconnect to the Serving MSC. n. The Serving MSC releases the MS.
35
X.S0010-A
8.X.41.2
MS Circuit-Switched Data Call Origination: Mid-Call Notification of Low Balance This scenario illustrates PPC invocation upon a circuit-switched data call origination by a PPC subscriber with PPC active and an account balance above threshold. The MS is notified of a low-account balance during the call. The MS disconnects.
1 2 3 4 5 6 7 8 9 10 11 12
a b
13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
answer
28 29 30 31 32 33 34
CCDIR [MSCID, MSID, BILLID, DISPTEXT] display text ccdir [ ] MS disconnect ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO] odisconnect [ ] ODT
35
k l m n o p call release q
36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
CCDT
Figure 3 MS Circuit-Switched Data Call Origination: Mid-Call Notification of Low Balance a. An MS circuit-switched data call origination with dialed digits is received by the Serving MSC.
51 52 53 54 55 56 57 58 59 60
36
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
b. The Serving MSC detects the Origination_Attempt_Authorized trigger and sends an ORREQ to the network entity (SCP) associated with this trigger.
Parameters MSCID MSID MDN ServiceType: [CDMAServiceOption] [TDMAServiceCode] BILLID DGTSDIAL TRIGTYPE Serving MSC MSCID. Served MS MSID. Served MS MDN. Include if available. The service type for the call: Indicates the requested CDMA service option for the call (e.g., ADS, G3Fax). Indicates the requested TDMA service code for the call. BillingID. Used to relate queries for this call. Digits entered by served MS. Indicates the trigger encountered. Usage Type R R O R O O R R R
Parameters MSCID MSID MDN BILLID DGTSDIAL ServiceType: [CDMAServiceOption] [TDMAServiceCode] RoutingInfo: [DSTDGTS] [CARDGTS] [ROUTDGTS] Serving MSC MSCID. Served MS MSID. Served MS MDN. Include if available. BillingID. Used to relate queries for this call. Dialed digits. The service type for the call: Indicates the current CDMA service option for the call (e.g., ADS, G3Fax). Indicates the current TDMA service code for the call. Call routing information: DestinationDigits. The network address of the destination. CarrierDigits. Interexchange carrier for call setup. Include if applicable. RoutingDigits. Special routing instructions. Include if applicable. R O O Usage Type R R O R R R O O
37
X.S0010-A
Parameters TRIGTYPE TOD TDO
Usage Indicates the trigger encountered. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time.
Type R R R
2 3 4 5 6 7 8
Parameters MSCID MSID MDN BILLID TRIGTYPE TOD TDO Serving MSC MSCID. Served MS MSID. Served MS MDN. Include if available. BillingID. Used to relate queries for this call. Indicates the trigger encountered. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time. Usage Type R R O R R R R
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
Upon receipt of the OANSWER, the SCP begins decrementing the subscribers account balance. j. The call is cut through and connected. k. The subscribers account balance reaches a threshold level and the SCP sends a CCDIR to the Serving MSC with the DISPTEXT parameter set to indicate a low balance. l. The Serving MSC sends the received display text to the MS. m. The Serving MSC responds to the SCP with a ccdir. n. The MS ends the call. o. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT to the network entity associated with this trigger.
Parameters MSCID MSID MDN BILLID Serving MSC MSCID. Served MS MSID. Served MS MDN. Include if available. BillingID. Used to relate queries for this call. Usage Type R R O R
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
38
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
Parameters TRIGTYPE RELCAUSE TOD TDO
Usage Indicates the trigger encountered. Call release cause. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time.
Type R R R R
Upon receipt of the ODISCONNECT, the SCP stops decrementing the subscribers account balance. p. The SCP sends an empty odisconnect to the Serving MSC. q. The Serving MSC releases the call.
39
X.S0010-A
8.X.41.3
MS Circuit-Switched Data Call Origination: Service Logic Directed Call Release This scenario illustrates PPC invocation upon a circuit-switched data call origination by a PPC subscriber with service logic directed call release.
1 2 3 4 5 6 7 8 9 10 11
a b
12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
answer
27 28 29 30 31 32 33
CCDIR [MSCID, MSID, BILLID, DISPTEXT] display text ccdir [ ]
34
k l m
35 36 37 38 39 40 41
CCDT
CCDIR [MSCID, MSID, BILLID, DISPTEXT, ACTCODE] display text CCDT call release ccdir [ ] ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO] odisconnect [ ] ODT
42
n o p q r s call release t
43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
Figure 4 MS Circuit-Switched Data Call Origination: Service Logic Directed Call Release
40
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
a. An MS circuit-switched data call origination with dialed digits is received by the Serving MSC. b. The Serving MSC detects the Origination_Attempt_Authorized trigger and sends an ORREQ to the network entity (SCP) associated with this trigger.
Parameters MSCID MSID MDN ServiceType: [CDMAServiceOption] [TDMAServiceCode] BILLID DGTSDIAL TRIGTYPE Serving MSC MSCID. Served MS MSID. Served MS MDN. Include if available. The service type for the call: Indicates the requested CDMA service option for the call (e.g., ADS, G3Fax). Indicates the requested TDMA service code for the call. BillingID. Used to relate queries for this call. Digits entered by served MS. Indicates the trigger encountered. Usage Type R R O R O O R R R
Parameters MSCID MSID MDN BILLID DGTSDIAL ServiceType: [CDMAServiceOption] [TDMAServiceCode] Serving MSC MSCID. Served MS MSID. Served MS MDN. Include if available. BillingID. Used to relate queries for this call. Dialed digits. The service type for the call: Indicates the current CDMA service option for the call (e.g., ADS, G3Fax). Indicates the current TDMA service code for the call. Usage Type R R O R R R O O
41
X.S0010-A
Parameters RoutingInfo: [DSTDGTS] [CARDGTS] [ROUTDGTS] TRIGTYPE TOD TDO
Usage Call routing information: DestinationDigits. The network address of the destination. CarrierDigits. Interexchange carrier for call setup. Include if applicable. RoutingDigits. Special routing instructions. Include if applicable. Indicates the trigger encountered. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time.
Type
2 3 4
R O O R R R
5 6 7 8 9 10 11 12 13 14 15 16 17
Parameters MSCID MSID MDN BILLID TRIGTYPE TOD TDO Serving MSC MSCID. Served MS MSID. Served MS MDN. Include if available. BillingID. Used to relate queries for this call. Indicates the trigger encountered. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time. Usage Type R R O R R R R
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
Upon receipt of the OANSWER, the SCP begins decrementing the subscribers account balance. j. The call is cut through and connected. k. The subscribers account balance reaches a threshold level and the SCP sends a CCDIR to the Serving MSC with the DISPTEXT parameter set to indicate a low balance. l. The Serving MSC sends the received display text to the MS. m. The Serving MSC responds to the SCP with a ccdir. n. The SCP determines the call shall be disconnected (e.g., a PPC service logic program instance timer expires). The SCP sends a CCDIR to the Serving MSC. The DISPTEXT parameter is set to notify the user of the disconnect. The ACTCODE parameter is set to indicate that the call shall be disconnected.
44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
42
X.S0010-A
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
o. The Serving MSC sends the received display text to the MS. p. The Serving MSC releases the call leg to the called party. q. The Serving MSC sends a ccdir to the SCP reporting completion of the action. r. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT to the network entity associated with this trigger.
Parameters MSCID MSID MDN BILLID TRIGTYPE RELCAUSE TOD TDO Serving MSC MSCID. Served MS MSID. Served MS MDN. Include if available. BillingID. Used to relate queries for this call. Indicates the trigger encountered. Call release cause. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time. Usage Type R R O R R R R R
s. The SCP sends an empty odisconnect to the Serving MSC. t. The Serving MSC releases the MS.
43
X.S0010-A
8.X.41.4
Circuit-Switched Data Call Delivery: Intersystem Termination This scenario describes PPC invocation upon circuit-switched data Call Delivery with intersystem termination.
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
44
X.S0010-A
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
Originating System MSC call origination HLR
PPC SCP VLR
Serving MSC
a LOCREQ [MSCID, BILLID, DGTSDIAL, ServiceType, TRIGTYPE, TRANSCAP, WINCAP] b LRT locreq [MSCID, MIN, IMSI, ServiceType, TRIGADDRLIST] c d ANZT anlyzd [DMH_SVCID] e f ROUTREQ [MSCID, MSID, BILLID, ServiceType] ROUTREQ [MSCID, MSID, BILLID, ServiceType] LRT RRT RRT routreq [TLDN, ServiceType] i routreq [TLDN, ServiceType] locreq [MSCID, MIN, IMSI, TERMLIST, REDIND, ServiceType]
ANLYZD [MSCID, MSID, BILLID, DGTSDIAL, RoutingInfo, REDIND, TRIGTYPE, ServiceType, TOD, TDO]
ANLYZD [MSCID, BILLID, DGTSDIAL, MSID, ServiceType, TRIGTYPE]
LOCREQ [MSCID, BILLID, DGTSDIAL, ServiceType, TRIGTYPE, TRANSCAP, WINCAP]
g h
j k l
ANZT call setup
anlyzd [ ]
m n MS answer o p cut through q r s tdisconnect [DMH_SVCID] TDT t call release u
TANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, ServiceType, TOD, TDO]
MS disconnect TDISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]
Figure 5 Circuit-Switched Data Call Delivery: Intersystem Termination a. A circuit-switched data call origination and the dialed MS address digits (i.e., directory number) are received by the Originating MSC.
45
X.S0010-A
b. The Originating MSC detects the Mobile_Termination trigger and sends a LOCREQ to the HLR associated with the MS; this association is made through the dialed MS address digits (which may not be the MSID). The TRANSCAP parameter is set to indicate the MSC can process the TRIGADDRLIST parameter. The WINCAP parameter indicates the triggers supported by the MSC. The TRIGTYPE parameter is set to indicate the Mobile_Termination trigger was encountered. The ServiceType information is set to indicate the requested service type for the call.
Parameters MSCID BILLID DGTSDIAL ServiceType: [CDMAServiceOption] [TDMAServiceCode] TRIGTYPE TRANSCAP WINCAP Usage Originating MSCs MSCID. BillingID assigned by the Originating MSC for this call. Dialed MS address digits. The service type for the call: Indicates the requested CDMA service option for the call (e.g., ADS, G3Fax). Indicates the requested TDMA service code for the call. Indicates the trigger encountered. Originating MSCs transaction capability. Originating MSCs WIN capability. Type R R R O O O R R R
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
c. The HLR sends the locreq to the Originating MSC with the TRIGADDRLIST parameter set to indicate the Initial_Termination, Location and Called_Routing_Address_Available triggers shall be armed.
Parameters MSCID MIN IMSI ServiceType: [CDMAServiceOption] [TDMAServiceCode] TRIGADDRLIST Serving MSC MSCID. Called MS MIN. Called MS IMSI. Include if available. The service type for the call: Indicates the requested CDMA service option for the call (e.g., ADS, G3Fax). Indicates the requested TDMA service code for the call. WIN Triggers to arm for this call leg. Usage Type R R O R O O R
34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53
d. The Originating MSC detects the Initial_Termination trigger and sends an ANLYZD to the SCP indicated in the TRIGADDRLIST parameter. The TRIGTYPE parameter is set to indicate the Initial_Termination trigger was detected.
Parameters MSCID BILLID Usage Originating MSCs MSCID. BillingID. Used to relate queries for this call. Type R R
54 55 56 57 58 59 60
46
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
Parameters DGTSDIAL MSID ServiceType: [CDMAServiceOption] [TDMAServiceCode] TRIGTYPE
Usage Dialed MS address digits. Called MS MSID. The service type for the call: Indicates the requested CDMA service option for the call (e.g., ADS, G3Fax). Indicates the requested TDMA service code for the call. Indicates the trigger encountered.
Type R R R O O R
e. The SCP determines the called subscriber has PPC active and that the account balance is above the threshold level. The SCP sends an anlyzd to the Originating MSC. The DMH_SVCID parameter is set to indicate that PPC was invoked. f. The Originating MSC detects the Location trigger and sends a LOCREQ to the HLR. The TRIGTYPE parameter is set to indicate the Location trigger was encountered. g. The HLR determines call processing shall continue and sends a ROUTREQ to the VLR. The ServiceType information is set to indicate the requested type of circuit-switched data service. h. The VLR forwards the ROUTREQ to the Serving MSC. i. The Serving MSC allocates a TLDN for the circuit-switched data call to the MS and returns the TLDN to the VLR in the routreq. The ServiceType information is set to indicate the accepted circuit-switched service type. j. The VLR forwards the routreq to the HLR. k. The HLR sends the locreq to the Originating MSC with instructions to set up the circuit-switched data call to the subscriber.
Parameters MSCID MIN IMSI REDIND TERMLIST ServiceType: [CDMAServiceOption] [TDMAServiceCode] Serving MSC MSCID. Called MS MIN. Called MS IMSI. Include if available. DMH_RedirectionIndicator. Reason for extending the incoming call. Call termination information. The service type for the call: Indicates the accepted CDMA service option for the call (e.g., ADS, G3Fax). Indicates the accepted TDMA service code for the call. Usage Type R R O R R R O O
47
X.S0010-A
l. The Originating MSC prepares to setup the call to the Serving MSC and detects the Called_Routing_Address_Available trigger. The Originating MSC sends an ANLYZD to the SCP associated with this trigger.
Parameters MSCID MSID BILLID DGTSDIAL RoutingInfo: [DSTDGTS] [CARDGTS] [ROUTDGTS] REDIND TRIGTYPE ServiceType: [CDMAServiceOption] [TDMAServiceCode] TOD TDO Usage Originating MSCs MSCID. Called MS MSID. BillingID. Used to relate queries for this call. Dialed MS address digits. Call routing information: DestinationDigits. The network address of the destination. CarrierDigits. Interexchange carrier for call setup. Include if applicable. RoutingDigits. Special routing instructions. Include if applicable. DMH_RedirectionIndicator. Reason for extending the incoming call. Indicates the trigger encountered. The service type for the call: Indicates the current CDMA service option for the call (e.g., ADS, G3Fax). Indicates the current TDMA service code for the call. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time. R O O R R R O O R R Type R R R R
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
m. The SCP sends an anlyzd to the MSC. n. The Originating MSC sets up the call to the subscriber. o. The MS answers the circuit-switched data call. p. The Serving MSC detects the T_Answer trigger and sends a TANSWER to the SCP associated with this trigger.
Parameters MSCID MSID MDN BILLID TRIGTYPE Serving MSC MSCID. Served MS MSID. Mobile directory number. Include if available. BillingID. Used to relate queries for this call. Indicates the trigger encountered. Usage Type R R O R R
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
48
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
Parameters ServiceType: [CDMAServiceOption] [TDMAServiceCode] TOD TDO
Usage The service type for the call: Indicates the current CDMA service option for the call (e.g., ADS, G3Fax). Indicates the current TDMA service code for the call. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time.
Type R O O R R
Note, the Service Type information reflects any service configuration negotiation that may have occurred with the MS. q. The calling party is connected to the MS. r. The MS ends the call. s. The Serving MSC detects the T_Disconnect trigger and sends an TDISCONNECT to the SCP associated with this trigger.
Parameters MSCID MSID MDN BILLID TRIGTYPE RELCAUSE TOD TDO Serving MSC MSCID. Served MS MSID. Mobile directory number. Include if available. BillingID. Used to relate queries for this call. Indicates the trigger encountered. Call release cause. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time. Usage Type R R O R R R R R
Upon receipt of the TDISCONNECT, the SCP stops decrementing the subscribers account balance. t. The SCP sends a tdisconnect to the Serving MSC. The DMH_SVCID parameter is set to indicate PPC was invoked. u. The Serving MSC releases the call.
49
X.S0010-A
8.X.41.5
SCP-Based Call Forwarding Busy on Call Collision This scenario describes PPC interaction with SCP-based call forwarding on a busy condition encountered after circuit-switched data call delivery.
1 2 3 4 5
PPC SCP
CF SCP VLR
Serving MSC
6 7 8 9 10 11
a LOCREQ [MSCID, BILLID, DGTSDIAL, ServiceType, TRIGTYPE, TRANSCAP, WINCAP] b LRT locreq [MSCID, MIN, IMSI, ServiceType, TRIGADDRLIST] c d ANZT anlyzd [DMH_SVCID] e f ROUTREQ [MSCID, MSID, BILLID, ServiceType] ROUTREQ [MSCID, MSID, BILLID, ServiceType] LRT RRT RRT routreq [TLDN, ServiceType] i routreq [TLDN, ServiceType] locreq [MSCID, MIN, IMSI, TERMLIST, REDIND, ServiceType]
ANLYZD [MSCID, MSID, MDN, BILLID, DGTSDIAL, RoutingInfo, REDIND, TRIGTYPE, ServiceType, TOD, TDO]
12 13 14 15 16 17 18 19 20 21 22 23 24
ANLYZD [MSCID, BILLID, DGTSDIAL, MSID, TRIGTYPE, ServiceType]
g h
25 26 27 28 29 30 31 32
j k l
33 34 35 36 37 38
ANZT call setup
anlyzd [ ]
m n MS busy o p q r s
39 40 41 42 43 44 45 46 47 48 49
REDREQ [MSCID, MSID, BILLID, REDREASON, ServiceType] redreq [ ] call release TBUSY [MSCID, MSID, BILLID, TRIGTYPE, ServiceType] RRT
50 51 52 53 54
TBT
SIM Interaction
t u
55 56 57 58
tbusy [REDIND, TERMLIST, TRIGADDRLIST]
Figure 6 SCP-Based Call Forwarding Busy on Call Collision (1 of 2)
59 60
50
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
a. A circuit-switched data call origination and the dialed MS address digits (i.e., directory number) are received by the Originating MSC. b. The Originating MSC detects the Mobile_Termination trigger and sends a LOCREQ to the HLR associated with the MS; this association is made through the dialed MS address digits (which may not be the MSID). The TRANSCAP parameter is set to indicate the MSC can process the TRIGADDRLIST parameter. The WINCAP parameter indicates the triggers supported by the MSC. The TRIGTYPE parameter is set to indicate the Mobile_Termination trigger was encountered. The ServiceType information is set to indicate the requested service type for the call.
c. The HLR sends the locreq to the Originating MSC with the TRIGADDRLIST parameter set to indicate the Initial_Termination, Location, T_Busy, T_No_Answer and Called_Routing_Address_Available triggers shall be armed.
Parameters MSCID Usage Originating MSCs MSCID. Type R
51
X.S0010-A
Parameters BILLID DGTSDIAL MSID ServiceType: [CDMAServiceOption] [TDMAServiceCode] TRIGTYPE
Usage BillingID. Used to relate queries for this call. Dialed MS address digits. Called MS MSID. The service type for the call: Indicates the requested CDMA service option for the call (e.g., ADS, G3Fax). Indicates the requested TDMA service code for the call. Indicates the trigger encountered.
Type R R R R O O R
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
e. The SCP determines the called subscriber has PPC active and that the account balance is above the threshold level. The SCP sends an anlyzd to the Originating MSC. The DMH_SVCID parameter is set to indicate that PPC was invoked. f. The Originating MSC detects the Location trigger and sends a LOCREQ to the HLR. The TRIGTYPE parameter is set to indicate the Location trigger was encountered. g. The HLR determines call processing shall continue and sends a ROUTREQ to the VLR. The ServiceType information is set to indicate the requested type of circuit-switched data service. h. The VLR forwards the ROUTREQ to the Serving MSC. i. The Serving MSC allocates a TLDN for the circuit-switched data call to the MS and returns the TLDN to the VLR in the routreq. The ServiceType information is set to indicate the accepted circuit-switched service type. j. The VLR forwards the routreq to the HLR. k. The HLR sends the locreq to the Originating MSC with instructions to set up the circuit-switched data call to the subscriber.
Parameters MSCID MIN IMSI REDIND TERMLIST ServiceType: [CDMAServiceOption] [TDMAServiceCode] Serving MSC MSCID. Called MS MIN. Called MS IMSI. Include if available. DMH_RedirectionIndicator. Reason for extending the incoming call. Call termination information. The service type for the call: Indicates the accepted CDMA service option for the call (e.g., ADS, G3Fax). Indicates the accepted TDMA service code for the call. Usage Type R R O R R R O O
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
52
X.S0010-A
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
l. The Originating MSC prepares to setup the call to the Serving MSC and detects the Called_Routing_Address_Available trigger. The Originating MSC sends an ANLYZD to the SCP associated with this trigger.
Parameters MSCID MSID MDN BILLID DGTSDIAL RoutingInfo: [DSTDGTS] [CARDGTS] [ROUTDGTS] REDIND TRIGTYPE ServiceType: [CDMAServiceOption] [TDMAServiceCode] TOD TDO Usage Originating MSCs MSCID. Called MS MSID. Called MS MDN. BillingID. Used to relate queries for this call. Dialed MS address digits. Call routing information: DestinationDigits. The network address of the destination. CarrierDigits. Interexchange carrier for call setup. Include if applicable. RoutingDigits. Special routing instructions. Include if applicable. DMH_RedirectionIndicator. Reason for extending the incoming call. Indicates the trigger encountered. The service type for the call: Indicates the current CDMA service option for the call (e.g., ADS, G3Fax). Indicates the current TDMA service code for the call. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time. R O O R R R O O R R Type R R O R R
m. The SCP sends an anlyzd to the MSC. n. The Originating MSC sets up the call to the subscriber. o. The MS is engaged in a call and Call Waiting is not applicable. p. The Serving MSC sends a REDREQ to the Originating MSC indicating the MS is busy.
Parameters MSCID MSID BILLID REDREASON Serving MSC MSCID. Serve MS MSID. Call ID to reference BillingID of the Originating MSC. Identifies reason (i.e., busy). for the redirection request Usage Type R R R R
53
X.S0010-A
Parameters ServiceType: [CDMAServiceOption] [TDMAServiceCode]
Usage The service type for the call: Indicates the current CDMA service option for the call (e.g., ADS, G3Fax). Indicates the current TDMA service code for the call.
Type R O O
2 3 4 5 6 7 8 9 10 11 12 13
q. The Originating MSC responds with a redreq. r. The Originating MSC releases the call leg to the Serving MSC. s. The Originating MSC detects the T_Busy trigger and sends a TBUSY to the SCP associated with this trigger. The ServiceType information is set to indicate the current circuit-switched service type. t. The SCP may send a query (e.g., SERVREQ, SEARCH) to a SIM on another service logic network entity to determine which, if any, triggers should be armed for the forwarded call. u. The service logic determines the call should be forwarded. The SCP sends a tbusy to the MSC. In this scenario, the TERMLIST parameter indicates call forwarding to the PSTN. The TRIGADDRLIST parameter is included to arm triggers for the forwarded call (e.g., Calling_Routing_Address_Available, O_Answer, O_Disconnect).
Parameters TERMLIST REDIND TRIGADDRLIST Usage Call termination information. DMH_RedirectionIndicator. Reason for extending the incoming call. Indicates WIN triggers for the forwarded call leg. Type R R R
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
54
X.S0010-A
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
Originating System MSC HLR
PPC SCP
CF SCP VLR
Serving MSC
ANLYZD [MSCID, MSID, BILLID, RoutingInfo, REDIND, TRIGTYPE, ServiceType, TOD, TDO] v ANZT call forward setup answer y OANSWER [MSCID, MSID, BILLID, TRIGTYPE, TOD, TDO] z cut-through aa disconnect ab ODISCONNECT [MSCID, MSID, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO] ac ODT call release odisconnect [ ] ad ae anlyzd [DMH_SVCID] w x
Figure 7 SCP-Based Call Forwarding Busy on Call Collision (2 of 2) v. The Serving MSC analyzes the routing information and prepares to route the call. The MSC detects the Calling_Routing_Address_Available trigger and sends an ANLYZD to the SCP associated with this trigger.
Parameters MSCID MSID BILLID RoutingInfo: [DSTDGTS] [CARDGTS] [ROUTDGTS] REDIND TRIGTYPE Usage Originating MSCs MSCID. Called MS MSID. BillingID. Used to relate queries for this call. Call routing information: DestinationDigits. The network address of the destination. CarrierDigits. Interexchange carrier for call setup. Include if applicable. RoutingDigits. Special routing instructions. Include if applicable. DMH_RedirectionIndicator. Reason for extending the incoming call. Indicates the trigger encountered. R O O R R Type R R R
55
X.S0010-A
Parameters ServiceType: [CDMAServiceOption] [TDMAServiceCode] TOD TDO
Usage The service type for the call: Indicates the current CDMA service option for the call (e.g., ADS, G3Fax). Indicates the current TDMA service code for the call. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time.
Type R O O R R
2 3 4 5 6 7 8 9 10 11 12 13
w. The SCP sends an anlyzd to the MSC. The DMH_SVCID parameter is set to indicate PPC was invoked. x. The Originating MSC forwards the call. y. The call is answered. z. The Originating MSC detects the O_Answer trigger and sends an OANSWER to the SCP associated with this trigger. aa. The call is cut through and connected. ab. The MSC receives a disconnect indication for the terminating party. The MSC releases the call leg toward the terminating party. ac. The Originating MSC detects the O_Disconnect trigger and sends an ODISCONNECT to the SCP associated with this trigger. Upon receipt of the ODISCONNECT, the SCP stops decrementing the subscribers account balance. ad. The SCP sends an empty odisconnect to the Originating MSC. ae. The MSC releases the call leg to the calling party.
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
56
X.S0010-A
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
8.X.41.6
SCP-Based Call Forwarding Busy on Circuit-Switched Data Call This scenario describes PPC interaction with SCP-based call forwarding busy.
PPC SCP
CF SCP VLR
Serving MSC
a LOCREQ [MSCID, BILLID, DGTSDIAL, ServiceType, TRIGTYPE, TRANSCAP, WINCAP] b LRT locreq [MSCID, MIN, IMSI, ServiceType, TRIGADDRLIST] c d ANZT anlyzd [DMH_SVCID] e f ROUTREQ [MSCID, MSID, BILLID, ServiceType] ROUTREQ [MSCID, MSID, BILLID, ServiceType] RRT LRT RRT routreq [ACCDEN=Busy] i routreq [ACCDEN=Busy] locreq [MSCID, MIN, IMSI, ACCDEN=Busy] TBUSY [MSCID, MSID, BILLID, TRIGTYPE, ServiceType] j k l m n o ANZT call forward setup answer r OANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO] s cut-through t anlyzd [DMH_SVCID] p q g h
ANLYZD [MSCID, BILLID, DGTSDIAL, MSID, ServiceType, TRIGTYPE]
TBT
SIM Interaction
tbusy [REDIND, TERMLIST, TRIGADDRLIST] ANLYZD [MSCID, MSID, MDN, BILLID, RoutingInfo, REDIND, TRIGTYPE, ServiceType, TOD, TDO]
Figure 8 SCP-Based Call Forwarding Busy on Circuit-Switched Data Call (1 of 2) a. A circuit-switched data call origination and the dialed MS address digits (i.e., directory number) are received by the Originating MSC.
57
X.S0010-A
b. The Originating MSC detects the Mobile_Termination trigger and sends a LOCREQ to the HLR associated with the MS; this association is made through the dialed MS address digits (which may not be the MSID). The TRANSCAP parameter is set to indicate the MSC can process the TRIGADDRLIST parameter. The WINCAP parameter indicates the triggers supported by the MSC. The TRIGTYPE parameter is set to indicate the Mobile_Termination trigger was encountered. The ServiceType information is set to indicate the requested service type for the call.
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
c. The HLR sends the locreq to the Originating MSC with the TRIGADDRLIST parameter set to indicate the Initial_Termination, Location, Called_Routing_Address_Available, T_Busy and T_No_Answer triggers shall be armed.
34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53
Parameters MSCID BILLID Usage Originating MSCs MSCID. BillingID. Used to relate queries for this call. Type R R
54 55 56 57 58 59 60
58
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
Parameters DGTSDIAL MSID ServiceType: [CDMAServiceOption] [TDMAServiceCode] TRIGTYPE
Usage Dialed MS address digits. Called MS MSID. The service type for the call: Indicates the requested CDMA service option for the call (e.g., ADS, G3Fax). Indicates the requested TDMA service code for the call. Indicates the trigger encountered.
Type R R R O O R
e. The SCP determines the called subscriber has PPC active and that the account balance is above the threshold level. The SCP sends an anlyzd to the Originating MSC. The DMH_SVCID parameter is set to indicate that PPC was invoked. f. The Originating MSC detects the Location trigger and sends a LOCREQ to the HLR. The TRIGTYPE parameter is set to indicate the Location trigger was encountered. g. The HLR determines call processing shall continue and sends a ROUTREQ to the VLR. The ServiceType is information is set to indicate the type of circuit-switched data call. h. The VLR forwards the ROUTREQ to the Serving MSC. i. The MS is engaged in a call and Call Waiting is not applicable. The Serving MSC sends a routreq to the VLR with the ACCDEN parameter set to indicate Busy. j. The VLR forwards the routreq to the HLR. k. HLR-based call forwarding is not applicable. The HLR sends the locreq to the Originating MSC and relays the received ACCDEN parameter. l. The Originating MSC detects the T_Busy trigger and sends a TBUSY to the SCP associated with this trigger. The ServiceType is set to indicate the requested service type for the call. m. The SCP may send a query (e.g., SERVREQ, SEARCH) to a SIM on another service logic network entity to determine which, if any, triggers should be armed for the forwarded call. n. The service logic determines the call should be forwarded. The SCP sends a tbusy to the MSC. In this scenario, the TERMLIST parameter indicates call forwarding to the PSTN. The TRIGADDRLIST parameter is included to arm triggers for the forwarded call (e.g., Calling_Routing_Address_Available, O_Answer, O_Disconnect).
Parameters TERMLIST REDIND TRIGADDRLIST Usage Call termination information. DMH_RedirectionIndicator. Reason for extending the incoming call. Indicates WIN triggers for the forwarded call leg. Type R R R
59
X.S0010-A
o. The Serving MSC analyzes the routing information and prepares to route the call. The MSC detects the Calling_Routing_Address_Available trigger and sends an ANLYZD to the SCP associated with this trigger.
Parameters MSCID MSID MDN BILLID RoutingInfo: [DSTDGTS] [CARDGTS] [ROUTDGTS] REDIND TRIGTYPE ServiceType: [CDMAServiceOption] [TDMAServiceCode] TOD TDO Usage Originating MSCs MSCID. Called MS MSID. Called MS MDN. BillingID. Used to relate queries for this call. Call routing information: DestinationDigits. The network address of the destination. CarrierDigits. Interexchange carrier for call setup. Include if applicable. RoutingDigits. Special routing instructions. Include if applicable. DMH_RedirectionIndicator. Reason for extending the incoming call. Indicates the trigger encountered. The service type for the call: Indicates the current CDMA service option for the call (e.g., ADS, G3Fax). Indicates the current TDMA service code for the call. TimeOfDay. The current time (UTC). TimeDateOffset. The time offset of local civil time. R O O R R R O O R R Type R R R R
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
p. The SCP sends an anlyzd to the MSC. The DMH_SVCID parameter is set to indicate PPC was invoked. q. The Originating MSC forwards the call. r. The call is answered. s. The Originating MSC detects the O_Answer trigger and sends an OANSWER to the SCP associated with this trigger. t. The call is cut through and connected.
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
60
X.S0010-A
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
Originating System MSC HLR
PPC SCP
CF SCP VLR
Serving MSC
disconnect u ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO] v ODT call release odisconnect [ ] w x
Figure 9 SCP-Based Call Forwarding Busy on Circuit-Switched Data Call (2 of 2) u. The MSC receives a disconnect indication for the terminating party. The MSC releases the call leg toward the terminating party. v. The Originating MSC detects the O_Disconnect trigger and sends an ODISCONNECT to the SCP associated with this trigger. Upon receipt of the ODISCONNECT, the SCP stops decrementing the subscribers account balance. w. The SCP sends an empty odisconnect to the Originating MSC. x. The MSC releases the call leg to the calling party.
61
X.S0010-A
8.X.42
Short Message Services

(new for IS-826 Chapter 4, Section 8.X)
1 2 3 4 5 6 7
The scenarios in this section depict interactions between network entities in situations related to PPC support of short message services under automatic roaming conditions. The following abbreviations, which are described in TIA/EIA-41.3-D Section 7, are used in this section: SMD-REQUEST An implementation dependent air interface message for a short message delivery request. SMD-ACK SMD-NAK {A} {AAs MC} {As MSC} {B} {BBs MC} {Bs MSC} ACK NACK An implementation dependent air interface message for a short message delivery positive acknowledgment. An implementation dependent air interface message for a short message delivery negative acknowledgment. The address of SME A. The address of SME A implying the address of SME As home MC. The address of the MSC serving MS-based SME A. The address of SME B. The address of SME B implying the address of SME Bs home MC. The address of the MSC serving MS-based SME B. ([ACK]) Absence of cause code. ([NACK=cause code]) Presence of a cause code.
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
62
X.S0010-A
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
8.X.42.1
PPC for MS-Originated Short Message Accepted by the Network This scenario illustrates successful PPC invocation for an MS-originated short message. The PPC account is updated when the network accepts the short message.
A B Serving MSC MC Home PPC SCP Destination SME
Originator MS SME SMD-REQ
a SMDPP SM_ANLYZD b c d e f SMDPP SMT smdpp
SAOT
SMT smdpp [ACK] SMD-ACK
SMAT
sm_anlyzd [ACK]
g h
Figure 10 PPC for MS-Originated Short Message Accepted by the Network a. The MS-based SME formulates and sends an air interface SMD-REQUEST to the serving MSC.
Parameters SMS_OriginalDestinationAddress SMS_OriginalOriginatingAddress SMS_TeleserviceIdentifier SMS_BearerData SMS_DestinationAddress Usage Network address of the destination SME (i.e., {B}). Network address of the originating SME (i.e., {A}). Identification of the teleservice, used for interpreting the SMS_BearerData. Any desired message. Network address of the originating SMEs MC (i.e., {AAs MC}). Type R R R R O
b. The serving MSC converts the SMD-REQUEST into an SMDPP and forwards it toward the subscribers home MC as indicated by subscribers service profile.
Parameters MSID ESN Usage MSID of originating MS-based SME. ESN of originating MS-based SME. Type O O
63
X.S0010-A
Parameters SMS_ChargeIndicator SMS_MessageCount SMS_NotificationIndicator SMS_OriginalDestinationAddress SMS_OriginalDestinationSubAddress SMS_OriginalOriginatingAddress SMS_OriginalOriginatingSubAddress SMS_TeleserviceIdentifier SMS_BearerData SMS_DestinationAddress SMS_OriginatingAddress
Usage Charging options for SMS message. Include if received. Number of SMS messages pending delivery. Include if applicable. Used to control sending of subsequent SMS notification messages. Network address of the destination SME (i.e., {B}). Subaddress of the destination SME. Include if applicable. Network address of the originating SME (i.e., {A}). Subaddress of the originating SME. Include if applicable. Identification of the teleservice, used for interpreting the SMS_BearerData. Message received from MS-based SME. Network address of the originating SMEs MC (i.e., {AAs MC}. Network address of the originating SMEs MSC (i.e., {As MSC}.
Type O O O R O R O R R R O
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
c. The MSs home MC prepares to accept the short message and determines that the original originator is provisioned and configured for PPC of MS-originated short messages. The MC sends an SM_ANLYZD to the PPC SCP for the subscriber.
Parameters SMS_Event TOD TDO SMS_TeleserviceIdentifier SMS_BearerLength SMS_PendingMessageCount MSID ESN MDN SMS_ChargeIndicator Usage Type of SMS event encountered (i.e., MS-originated short message accepted by network). TimeOfDay of the event for the originators home MC TimeDateOffset of the event for the originators home MC. Identification of the teleservice, used for interpreting the SMS_BearerData. Length of the original SMS bearer data received from the MS-based SME. Number of short messages in the MC that are pending delivery to and from this MS-based SME. MSID of originating MS-based SME. ESN of originating MS-based SME. MDN of originating MS-based SME Charging options for SMS message. Include if received. Type R R R R R O R O O O
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
64
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
Parameters SMS_DestinationAddress SMS_OriginalDestinationAddress SMS_OriginalDestinationSubAddress SMS_OriginalOriginatingAddress SMS_OriginalOriginatingSubAddress SMS_OriginatingAddress SMS_BillingID
Usage Network address of the originating SMEs MC (i.e., {AAs MC}. Network address of the destination SME (i.e., {B}). Include if received and applicable. Network address of the originating SME (i.e., {A}). Include if received and applicable. Network address of the originating SMEs MSC (i.e., {As MSC}). MCs generated Billing Identifier for this short message.
Type R R O R O O R
d. The SCP updates the subscribers account balance sends an sm_anlyzd to the MC.
Parameters SMS_BearerData Usage Include to indicate the cost of the deduction and updated account balance. Used by the MC to notify the PPC end-user {A}. Include to identify the service that was invoked for this short message. Type O
DMH_SVCID
e. The originators home MC accepts the short message and returns an smdpp to the Originating MSC. The MC optionally generates an SMS data record containing the received DMH_SVCID parameter value.
Parameters SMS_BearerData Usage Include if received in Step-d. Type O
f. The MSC converts the smdpp into an air interface SMD-ACK message. The MS-based SME correlates the response with the original request. g. The originators home MC stores the messages and possibly waits until further delivery actions are taken. The originators home MC may also remove the short message before delivery for any other reasons. The originators home MC forwards the SMDPP towards the destination SME. The parameters are as in Step-b. h. The destination SME responds by returning an smdpp to the originators home MC.
65
X.S0010-A
8.X.42.2
PPC for MS-Originated Short Message Delivered to Destination SME This scenario illustrates successful PPC invocation for an MS-originated short message. The PPC account is updated when the network accepts the short message and when the short message is successfully delivered to the destination SME.
1 2 3 4 5 6 7 8 9 10
11 12 13 14
a SMDPP SM_ANLYZD b c d e f SM_ANLYZD SMAT SMDPP SMT SM_ANLYZD SMAT sm_anlyzd [ACK] smdpp [ACK] sm_anlyzd [ACK]
15 16 17 18 19 20 21 22 23 24 25 26 27 28
SAOT
SMAT
sm_anlyzd [ACK]
g h i j k l
29 30 31 32 33 34 35 36 37 38 39 40 41 42 43
Figure 11 PPC for MS-Originated Short Message Delivered to Destination SME a-c. Same as Scenario 8.X.42.1, Steps a-c. d. The PPC SCP updates the subscribers account balance. The PPC SCP determines that this subscriber is to be charged for further processing of this short message service and includes the SMS_EventNotification parameter in the sm_anlyzd sent to the home MC. The SMS_EventNotification parameter is set to indicate the events that shall be reported to the PPC SCP. In this scenario, the SMS_EventNotification is set to indicate MS-originated short message delivery attempt towards destination, Successful MSoriginated short message delivery towards destination, Unsuccessful MS-originated short message delivery towards destination, and MS-originated short message purged by MC.
Parameters SMS_EventNotification Usage The SMS events to be reported for this particular short message delivery. Type R
44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
66
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
Parameters SMS_BearerData
Usage Include to indicate the cost of the deduction and updated account balance. Used by the MC to notify the PPC end-user {A}. Include to identify the service that was invoked for this short message.
Type O
DMH_SVCID
e-f. Same as Scenario 8.X.42.1, Steps e-f. g. The subscribers home MC is ready to send the short message to the destination MC. The MC determines that an SMS notification event is applicable. The MC sends an SM_ANLYZD to the PPC SCP. The SMS_Event parameter is set to indicate MSoriginated short message delivery attempt towards destination.
Parameters SMS_Event TOD TDO SMS_TeleserviceIdentifier SMS_BearerLength SMS_PendingMessageCount MSID ESN MDN SMS_ChargeIndicator SMS_DestinationAddress SMS_OriginalDestinationAddress SMS_OriginalDestinationSubAddress SMS_OriginalOriginatingAddress SMS_OriginalOriginatingSubAddress SMS_OriginatingAddress SMS_BillingID Usage Type of SMS event encountered. TimeOfDay of the event for the originators home MC TimeDateOffset of the event for the originators home MC. Identification of the teleservice, used for interpreting the SMS_BearerData. Length of the original SMS bearer data received from the MS-based SME. Number of short messages in the MC that are pending delivery to and from the MS-based SME. MSID of originating MS-based SME. ESN of originating MS-based SME. MDN of originating MS-based SME Charging options for SMS message. Include if received. Network address of the originating SMEs MC (i.e., {BBs MC}. Network address of the destination SME (i.e., {B}). Include if received and applicable. Network address of the originating SME (i.e., {A}). Include if received and applicable. Network address of the originating SMEs MC (i.e., {AAs MC}). Billing Identifier originally assigned by MC for this short message. Type R R R R R O R O O O O R O R O R R
67
X.S0010-A
h. The PPC SCP verifies that the PPC subscribers account balance is sufficient and reserves a deduction from the PPC subscribers account for the cost of this chargeable event. The SCP sends an sm_anlyzd to the subscribers home MC.
Parameters SMS_BearerData Usage Include to indicate the deduction and the updated account balance. Used by the MC to notify the PPC end-user {A}. Include to identify the service that was invoked. Type O
1 2 3 4 5 6 7 8 9
DMH_SVCID
10 11 12 13 14 15 16
i. The home MC sends an SMDPP to the destination MC with the short message received from the MS-SME. j. The destination MC accepts the received short message and responds with an smdpp. k. The MC determines that an SMS notification event is applicable. The MC sends an SM_ANLYZD to the PPC SCP. The SMS_Event parameter is set to indicate Successful MS-originated short message delivery towards destination.
Parameters SMS_Event TOD TDO SMS_TeleserviceIdentifier SMS_BearerLength SMS_PendingMessageCount MSID ESN MDN SMS_ChargeIndicator SMS_DestinationAddress SMS_OriginalDestinationAddress SMS_OriginalDestinationSubAddress SMS_OriginalOriginatingAddress SMS_OriginalOriginatingSubAddress SMS_OriginatingAddress Usage Type of SMS event encountered. TimeOfDay of the event for the originators home MC TimeDateOffset of the event for the originators home MC. Identification of the teleservice, used for interpreting the SMS_BearerData. Length of the original SMS bearer data received from the MS-based SME. Number of short messages in the MC that are pending delivery to and from the MS-based SME. MSID of originating MS-based SME. ESN of originating MS-based SME. MDN of originating MS-based SME Charging options for SMS message. Include if received. Network address of the originating SMEs MC (i.e., {BBs MC}. Network address of the destination SME (i.e., {B}). Include if received and applicable. Network address of the originating SME (i.e., {A}). Include if received and applicable. Network address of the originating SMEs MC (i.e., {AAs MC}). Type R R R R R O R O O O O R O R O R
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
68
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
Parameters SMS_BillingID
Usage Billing Identifier originally assigned by MC for this short message.
Type R
l. The PPC SCP commits the deduction that has been reserved in the PPC subscribers account balance. The SCP sends an sm_anlyzd to the subscribers home MC.
Parameters SMS_BearerData Usage Include to indicate the deduction and the updated account balance. Used by the MC to notify the PPC end-user {A}. Include to identify the service that was invoked. Type O
DMH_SVCID
69
X.S0010-A
8.X.42.3
PPC for MS-Originated Short Message Not Accepted by the Network This scenario illustrates unsuccessful PPC invocation for an MS-originated short message. The PPC account does not have a sufficient balance for the MS-originated short message.
1 2 3 4 5 6 7 8 9
10 11 12 13
a SMDPP SM_ANLYZD b c d e f
14 15 16 17 18 19 20 21 22 23 24 25 26
SAOT
SMT smdpp [NACK]
SMAT
sm_anlyzd [NACK]
SMD-NACK
Figure 12 PPC for MS-Originated Short Message Not Accepted by the Network a-c. Same as Section 8.X.42.1, Steps a-c. d. The PPC SCP examines the subscribers account balance. In this scenario, the PPC subscribers account balance is not sufficient for this chargeable event. The PPC SCP sends an sm_anlyzd to the originators home MC indicating the SMS origination is denied.
Parameters SMS_CauseCode SMS_BearerData DMH_SVCID Usage Indicating Service denied. Include to indicate the account balance information. Used by the MC to notify the PPC subscriber {A}. Include to identify the service that was invoked for the short message origination. Type R O O
27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44
e. The subscribers home MC rejects the short message and returns an smdpp to the Originating MSC.
Parameters SMS_CauseCode SMS_BearerData Usage Indicating SMS Origination Denied. Include if applicable or if received at Step-d. Type R O
45 46 47 48 49 50 51 52 53
f. The MSC converts the smdpp into an air interface SMD-NACK message. The MSbased SME correlates the response with the original request and informs the end-user of the rejection.
54 55 56 57 58 59 60
70
X.S0010-A
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
8.X.42.4
PPC for MS-Originated Short Message: Message Not Accepted by Destination SME This scenario illustrates PPC invocation for an MS-originated short message. The PPC account is updated when the network accepts the short message and when the network attempts to deliver the short message to the destination SME. The destination SME does not accept the short message.
a SMDPP SM_ANLYZD b c d e f SM_ANLYZD SMAT SMDPP SMT SM_ANLYZD SMAT sm_anlyzd [ACK] smdpp [NACK] sm_anlyzd [ACK]
SAOT
SMAT
sm_anlyzd [ACK]
g h i j k l
Figure 13 PPC for MS-Originated Short Message: Message Not Accepted by Destination SME a-i. Same as Scenario 8.X.42.2, Steps a-i. j. The destination SME does not accept the short message and returns an smdpp with a negative acknowledgement. k. The MC determines that an SMS notification event is applicable. The MC sends an SM_ANLYZD to the PPC SCP. The SMS_Event parameter is set to indicate Unsuccessful MS-originated short message delivery towards destination.
Parameters SMS_Event Usage Type of SMS event encountered. Type R
71
X.S0010-A
Parameters TOD TDO SMS_TeleserviceIdentifier SMS_BearerLength SMS_PendingMessageCount MSID ESN MDN SMS_ChargeIndicator SMS_DestinationAddress SMS_OriginalDestinationAddress SMS_OriginalDestinationSubAddress SMS_OriginalOriginatingAddress SMS_OriginalOriginatingSubAddress SMS_OriginatingAddress SMS_BillingID
Usage TimeOfDay of the event for the originators home MC TimeDateOffset of the event for the originators home MC. Identification of the teleservice, used for interpreting the SMS_BearerData. Length of the original SMS bearer data received from the MS-based SME. Number of short messages in the MC that are pending delivery to and from the MS-based SME. MSID of originating MS-based SME. ESN of originating MS-based SME. MDN of originating MS-based SME Charging options for SMS message. Include if received. Network address of the destination SMEs MC (i.e., {BBs MC}. Network address of the destination SME (i.e., {B}). Include if received and applicable. Network address of the originating SME (i.e., {A}). Include if received and applicable. Network address of the originating SMEs MC (i.e., {AAs MC}). Billing Identifier originally assigned by MC for this short message.
Type R R R R O R O O O O R O R O R R
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
l. The PPC SCP does not commit the deduction that has been reserved in the PPC subscribers account balance. The SCP sends an sm_anlyzd to the subscribers home MC.
Parameters SMS_BearerData DMH_SVCID Usage Include to indicate the account balance. Used by the MC to notify the PPC end-user {A}. Include to identify the service that was invoked. Type O O
41 42 43 44 45 46 47 48 49 50 51
The home MC may discard the short message or store it for delivery at a later time.
52 53 54 55 56 57 58 59 60
72
X.S0010-A
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
8.X.42.5
PPC for MS-Originated Short Message Purged by Originators Home MC This scenario illustrates PPC invocation for an MS-originated short message. The PPC account is updated when the network accepts the short message. The originators home MC purges the short message (e.g., delivery time-out, memory shortage) before it is delivered to the destination SME. The subscriber is notified when the MC deletes the short message.
a SMDPP SM_ANLYZD b c d e f SM_ANLYZD SMAT SMDPP sm_anlyzd [ACK]
SAOT
SMAT
sm_anlyzd [ACK]
g h i j
SMD-REQ SMD-ACK SADT SMT
k smdpp [ACK] l
Figure 14 PPC for MS-Originated Short Message Purged by Originators Home MC a-f. Same as Scenario 8.X.42.2, Steps a-f. g. The subscribers home MC deletes the message. The MC determines that an SMS notification event is applicable. The MC sends an SM_ANLYZD to the PPC SCP. The SMS_Event parameter is set to indicate MS-originated short message purged by MC.
Parameters SMS_Event TOD TDO Usage Type of SMS event encountered. TimeOfDay of the event for the originators home MC TimeDateOffset of the event for the originators home MC. Type R R R
73
X.S0010-A
Parameters SMS_TeleserviceIdentifier SMS_BearerLength SMS_PendingMessageCount MSID ESN MDN SMS_ChargeIndicator SMS_DestinationAddress SMS_OriginalDestinationAddress SMS_OriginalDestinationSubAddress SMS_OriginalOriginatingAddress SMS_OriginalOriginatingSubAddress SMS_OriginatingAddress SMS_BillingID
Usage Identification of the teleservice, used for interpreting the SMS_BearerData. Length of the original SMS bearer data received from the MS-based SME. Number of short messages in the MC that are pending delivery to and from the MS-based SME. MSID of originating MS-based SME. ESN of originating MS-based SME. MDN of originating MS-based SME Charging options for SMS message. Include if received. Network address of the originating SMEs MC (i.e., {BBs MC}. Network address of the destination SME (i.e., {B}). Include if received and applicable. Network address of the originating SME (i.e., {A}). Include if received and applicable. Network address of the originating SMEs MC (i.e., {AAs MC}). Billing Identifier originally assigned by MC for this short message.
Type R R O R O O O O R O R O R R
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
h. The PPC SCP may adjust the subscribers account balance because the message was deleted before delivery. The SCP sends an sm_anlyzd to the home MC.
Parameters SMS_BearerData Usage Include to indicate the credit and updated account balance. Used by the MC to notify the PPC enduser {A}. Include to identify the service that was invoked. Type O
37 38 39 40 41 42 43 44
DMH_SVCID
45 46
i. Optionally, the originators home MC may notify the MS-SME that the short message was purged before it was delivered to the destination SME. The MC sends an SMDPP to the Serving MSC that contains the short message to present to the subscriber. The SMS_ChargeIndicator parameter is set to indicate that no charge is applied to the message.
Parameters MSID MSID of the MS-SME. Usage Type R
47 48 49 50 51 52 53 54 55 56 57 58 59 60
74
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
Parameters SMS_BearerData
Usage The message to be sent to the MS-SME based on the bearer data received from the PPC SCP in the previous step. Network address of the destination SME. Network address of the originating SME. Identification of the teleservice, used for interpreting the SMS_BearerData. Indicates No Charge shall be applied to this short message.
Type R
SMS_OriginalDestinationAddress SMS_OriginalOriginatingAddress SMS_TeleserviceIdentifier SMS_ChargeIndicator
R R R R
j. The MSC forwards the SMD-REQUEST to the SME using the air interface address of the MS (e.g., MSID). k. The originating SME responds with an SMD-ACK to acknowledge acceptance of the SMD-REQUEST. l. The Serving MSC sends a positive acknowledgement to the MC.
75
X.S0010-A
8.X.42.6
PPC for MS-Terminated Short Message Delivered to Subscriber This scenario illustrates successful MS-terminated short message delivery by the PPC subscribers home MC. The PPC account is updated when the destination MS-SME receives the short message.
1 2 3 4 5 6 7
B Destination MS SME
Destination Serving MSC PPC SCP
Destination Home HLR MC
A Source SME
8 9 10 11 12 13 14
SMDPP SM_ANLYZD sm_anlyzd [ACK] SMAT SMT
a b c
15 16 17 18 19 20 21
smdpp [ACK]
22 23
SMSREQ smsreq [SMSADDR] SRT SM_ANLYZD sm_anlyzd [ACK] SMAT
24
e f g h
25 26 27 28 29 30 31 32 33
SMDPP SMD-REQ SMD-ACK SADT smdpp [ACK] SM_ANLYZD sm_anlyzd [ACK] SMAT SMT
i j k l m n
34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51
Figure 15 PPC for MS-Terminated Short Message Delivered to Subscriber a. The subscribers home MC receives an SMDPP requesting delivery of a short message to an MS-based SME.
Parameters SMS_BearerData SMS_OriginalDestinationAddress SMS_OriginalOriginatingAddress Usage Message received for MS-based SME. Network address of the destination SME (i.e., {B}) Network address of the originating SME (i.e., {A}) Type R R R
52 53 54 55 56 57 58 59 60
76
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
Parameters SMS_TeleserviceIdentifier
Usage Identification of the teleservice, used for interpreting the SMS_BearerData.
Type R
b. The home MC is about to accept the short message received from the source SME. The MC determines that PPC is applicable for short messages to the destination SME (i.e., MS-terminated SMS). The MC sends an SM_ANLYZD to the PPC SCP associated with the subscriber.
Parameters SMS_Event TOD TDO SMS_TeleserviceIdentifier SMS_BearerLength SMS_PendingMessageCount MSID ESN MDN SMS_ChargeIndicator SMS_DestinationAddress SMS_OriginalDestinationAddress SMS_OriginalDestinationSubAddress SMS_OriginalOriginatingAddress SMS_OriginalOriginatingSubAddress SMS_OriginatingAddress SMS_BillingID Usage Type of SMS event encountered (i.e., MS-terminated short message accepted by network). TimeOfDay of the event for the destinations home MC TimeDateOffset of the event for the destinations home MC. Identification of the teleservice, used for interpreting the SMS_BearerData. Length of the original SMS bearer data received for the destination MS-based SME. Number of short messages in the MC that are pending delivery to and from the MS-based SME. MSID of destination MS-based SME. ESN of destination MS-based SME. MDN of destination MS-based SME Charging options for SMS message. Include if received. Network address of the destination SMEs MC (i.e., {BBs MC}. Network address of the destination SME (i.e., {B}). Include if received and applicable. Network address of the originating SME (i.e., {A}). Include if received and applicable. Network address of the originating SMEs MC (i.e., {AAs MC}). MCs generated Billing Identifier for this short message. Type R R R R R O R O O O O R O R O R R
c. The PPC SCP verifies that the subscribers account balance is sufficient and updates the PPC subscribers account for the chargeable event. The PPC SCP determines that this subscriber is to be charged for further processing of this short message service and includes the SMS_EventNotification parameter in the sm_anlyzd sent to the home MC. The SMS_EventNotification parameter is set to
77
X.S0010-A
indicate the events that shall be reported to the PPC SCP. In this scenario, the SMS_EventNotification is set to indicate MS-terminated short message delivery attempt to MS-based SME, Successful MS-terminated short message delivery to MS-based SME, Unsuccessful MS-terminated short message delivery to MS-based SME, and MSterminated short message purged by MC.
Parameters SMS_EventNotification SMS_BearerData DMH_ServiceID Usage The SMS events to be reported for this particular short message delivery. Include to indicate the account balance information. Used by the MC to notify the PPC subscriber {B}. Include to identify the service that was invoked for this SMS. Type R O O
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
d. The home MC sends an smdpp toward the source SME. The destinations home MC stores the short message and possibly waits until further delivery actions are taken. e. The MC does not have the current SMS routing address for the destination MS-baed SME. The MC sends an SMSREQ to the HLR associated with the MS and includes the applicable MS identifier. f. The HLR responds with an smsreq. The SMSADDR parameter is set to indicate the current address that can be used to route the short message. Note: Though not shown in this scenario, the HLR may forward the SMSREQ to the serving VLR to obtain the current routing address for short message delivery. g. The home MC is prepared to deliver the short message to the destination MS-SME. The MC determines that an SMS event notification is applicable (see Step-c). The MC sends an SM_ANLYZD to the PPC SCP associated with the subscriber.
Parameters SMS_Event Usage Type of SMS event encountered (i.e., MS-terminated short message delivery attempt to MS-based SME). TimeOfDay of the event for the destinations home MC TimeDateOffset of the event for the destinations home MC. Identification of the teleservice, used for interpreting the SMS_BearerData. Length of the original SMS bearer data received for the destination MS-based SME. Number of short messages in the MC that are pending delivery to and from the MS-based SME. MSID of destination MS-based SME. ESN of destination MS-based SME. MDN of destination MS-based SME Charging options for SMS message. Include if received. Type R
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
TOD TDO SMS_TeleserviceIdentifier SMS_BearerLength SMS_PendingMessageCount MSID ESN MDN SMS_ChargeIndicator
R R R R O R O O O
40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
78
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
Parameters SMS_DestinationAddress SMS_OriginalDestinationAddress SMS_OriginalDestinationSubAddress SMS_OriginalOriginatingAddress SMS_OriginalOriginatingSubAddress SMS_OriginatingAddress SMS_BillingID
Usage Network address of the originating SMEs MC (i.e., {BBs MC}. Network address of the destination SME (i.e., {B}). Include if received and applicable. Network address of the originating SME (i.e., {A}). Include if received and applicable. Network address of the originating SMEs MC (i.e., {AAs MC}). Billing Identifier originally assigned by MC for this short message.
Type O R O R O R R
h. The PPC SCP verifies that the subscribers account balance is sufficient and reserves a deduction from the PPC subscribers account for the chargeable event. The SCP sends an sm_anlyzd to the home MC.
Parameters SMS_BearerData DMH_ServiceID Usage Include to indicate the account balance information. Used by the MC to notify the PPC subscriber {B}. Include to identify the service that was invoked for this SMS. Type O O
i. The home MC sends an SMDPP toward the destination SME using the current SMS routing address for the MS-based SME.
Parameters MSID SMS_BearerData SMS_OriginalDestinationAddress SMS_OriginalOriginatingAddress SMS_TeleserviceIdentifier Usage MSID of destination MS-based SME. Message received for MS-based SME. Network address of the destination SME (i.e., {B}) Network address of the originating SME (i.e., {A}) Identification of the teleservice, used for interpreting the SMS_BearerData. Type R R R R R
j. The Serving MSC sends an SMD-REQUEST to the destination SME using the air interface address of the MS-based SME (e.g., MSID). k. The destination SME responds with a positive acknowledgment (SMD-ACK) to signal the acceptance of the SMD-REQUEST. l. The Serving MSC translates the SMD-ACK into an smdpp positive acknowledgement and returns it to the subscribers home MC.
79
X.S0010-A
m. Following successful delivery of the short message to the MS-SME, the subscribers home MC determines that an SMS event notification is applicable (see Step-c). The MC sends an SM_ANLYZD to the PPC SCP associated with the subscriber.
Parameters SMS_Event Usage Type of SMS event encountered (i.e., Successful MSterminated short message delivery to MS-based SME). TimeOfDay of the event for the destinations home MC TimeDateOffset of the event for the destinations home MC. Identification of the teleservice, used for interpreting the SMS_BearerData. Length of the original SMS bearer data received for the destination MS-based SME. Number of short messages in the MC that are pending delivery to and from the MS-based SME. MSID of destination MS-based SME. ESN of destination MS-based SME. MDN of destination MS-based SME Charging options for SMS message. Include if received. Network address of the originating SMEs MC (i.e., {BBs MC}. Network address of the destination SME (i.e., {B}). Include if received and applicable. Network address of the originating SME (i.e., {A}). Include if received and applicable. Network address of the originating SMEs MC (i.e., {AAs MC}). Billing Identifier originally assigned by MC for this short message. Type R
1 2 3 4 5 6 7 8 9
TOD TDO SMS_TeleserviceIdentifier SMS_BearerLength SMS_PendingMessageCount MSID ESN MDN SMS_ChargeIndicator SMS_DestinationAddress SMS_OriginalDestinationAddress SMS_OriginalDestinationSubAddress SMS_OriginalOriginatingAddress SMS_OriginalOriginatingSubAddress SMS_OriginatingAddress SMS_BillingID
R R R R O R O O O O R O R O R R
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
n. The PPC SCP applies the deduction that has been reserved to the subscribers account balance. The SCP sends an sm_anlyzd to the subscribers home MC.
Parameters SMS_BearerData Usage Include to indicate the cost of the deduction and updated account balance. Used by the MC to notify the PPC end-user {B}. Include to identify the service that was invoked. Type O
49 50 51 52 53 54 55 56
DMH_SVCID
57 58 59 60
80
X.S0010-A
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
8.X.42.7
PPC for MS-Terminated Short Message Accepted by Home MC This scenario illustrates successful MS-terminated short message delivery when the short message is accepted by the PPC subscribers home MC. PPC charging only occurs when the short message is accepted by the destination SMEs home MC.
A Source SME
a b c
smdpp [ACK]
SMSREQ smsreq [SMSADDR] SRT SMDPP SMD-REQ SMD-ACK SADT smdpp [ACK] SMT
e f g h i j
Figure 16 PPC for MS-Terminated Short Message Accepted by Home MC a-b. Same as Scenario 8.X.42.6, Steps a-b. c. The PPC SCP verifies that the subscribers account balance is sufficient and updates the PPC subscribers account for the chargeable event. The PPC SCP determines no additional charges shall apply for this short message delivery. The SCP sends an sm_anlyzd to the home MC.
Parameters SMS_BearerData DMH_ServiceID Usage Include to indicate the account balance information. Used by the MC to notify the PPC subscriber {B}. Include to identify the service that was invoked for this SMS. Type O O
d-f. Same as Scenario 8.X.42.6, Steps d-f. g-j. Same as Scenario 8.X.42.6, Steps i-l.
81
X.S0010-A
8.X.42.8
MS-Terminated Short Message Not Delivered: Low Balance This scenario illustrates unsuccessful delivery of a short message to the destination PPC subscriber. The subscribers account balance is not sufficient for the short message delivery.
1 2 3 4 5 6 7
A Source SME
8 9 10 11 12 13 14
a b c
15 16 17 18 19 20 21
smdpp [ACK]
22 23
SMSREQ smsreq [SMSADDR] SRT SM_ANLYZD sm_anlyzd [NACK] SMAT
24
e f g h
25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45
Figure 17 MS-Terminated Short Message Not Delivered: Low Balance a-g. Same as scenario 8.X.42.6, Steps a-g, but in this scenario, the destination subscribers PPC account balance is not sufficient to deliver the message to the MS-SME. h. The PPC SCP examines the subscribers account balance. In this scenario, the PPC subscribers account balance is not sufficient for this chargeable event. The PPC SCP sends an sm_anlyzd to the subscribers home MC.
Parameters SMS_CauseCode SMS_BearerData Usage Indicating Service denied. Include to indicate the account balance information. Used by the MC to notify the PPC subscriber {B}. Type R O
46 47 48
Upon receipt of the sm_anlyzd, the subscribers home MC may discard the short message or store it for delivery at a later time.
49 50 51 52 53 54 55 56 57 58 59 60
82
X.S0010-A
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
8.X.42.9
MS-Terminated Short Message Not Delivered: MS Inaccessible This scenario illustrates unsuccessful delivery of a short message to the destination PPC subscriber. The subscribers account balance is not low, but the destination MS-SME is not accessible.
A Source SME
a b c
smdpp [ACK]
SMSREQ smsreq [SMSADDR] SRT SM_ANLYZD sm_anlyzd [ACK] SMAT
e f g h
SMDPP SMD-REQ SADT MS inaccessible smdpp [NACK] SM_ANLYZD sm_anlyzd [ACK] SMAT SMT
i j k l m n
Figure 18 MS-Terminated Short Message Not Delivered: MS Inaccessible a-j. Same as scenario 8.X.42.6, Steps a-j. k. The destination MS-SME is not accessible and does not respond to the SMDREQUEST message. l. The Serving MSC sends a negative acknowledgement to the subscribers home MC.
83
X.S0010-A
m. Following unsuccessful delivery of the short message to the MS-SME, the subscribers home MC determines that an SMS event notification is applicable (see Step-c). The MC sends an SM_ANLYZD to the PPC SCP associated with the subscriber.
Parameters SMS_Event Usage Type of SMS event encountered (i.e., Unsuccessful MS-terminated short message delivery to MSbased SME). TimeOfDay of the event for the destinations home MC TimeDateOffset of the event for the destinations home MC. Identification of the teleservice, used for interpreting the SMS_BearerData. Length of the original SMS bearer data received for the destination MS-based SME. Number of short messages in the MC that are pending delivery to and from the MS-based SME. MSID of destination MS-based SME. ESN of destination MS-based SME. MDN of destination MS-based SME Charging options for SMS message. Include if received. Network address of the originating SMEs MC (i.e., {BBs MC}. Network address of the destination SME (i.e., {B}). Include if received and applicable. Network address of the originating SME (i.e., {A}). Include if received and applicable. Network address of the originating SMEs MC (i.e., {AAs MC}). Billing Identifier originally assigned by MC for this short message. Type R
1 2 3 4 5 6 7 8 9
TOD TDO SMS_TeleserviceIdentifier SMS_BearerLength SMS_PendingMessageCount MSID ESN MDN SMS_ChargeIndicator SMS_DestinationAddress SMS_OriginalDestinationAddress SMS_OriginalDestinationSubAddress SMS_OriginalOriginatingAddress SMS_OriginalOriginatingSubAddress SMS_OriginatingAddress SMS_BillingID
R R R R O R O O O O R O R O R R
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
n. The PPC SCP does not apply the deduction that has been reserved for the short message delivery, to the subscribers account balance. The SCP sends an sm_anlyzd to the subscribers home MC.
Parameters SMS_BearerData DMH_SVCID Usage Include to indicate the account balance. Used by the MC to notify the PPC end-user {B}. Include to identify the service that was invoked. Type O O
49 50 51 52 53 54 55 56 57 58 59 60
84
X.S0010-A
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
Upon receipt of the sm_anlyzd, the subscribers home MC may discard the short message or store it for delivery at a later time.
85
X.S0010-A

This section provides additions and modifications to IS-826 Chapter 5, Modifications to TIA/EIA-41.5-D Signaling Protocol, required to support circuit-switched data and short message services.
1 2 3 4 5 6 7
5
5.1
DATA TRANSFER SERVICES

SS7-Based Data Transfer Services
(See TIA/EIA-41, page 5-6)
8 9 10 11 12 13 14 15
Table 1 MTP Message Priority Values for TIA/EIA-41 Operations

TIA/EIA-41 Operation
ShortMessageAnalyzed MTP Message Priority 0
16 17 18 19 20 21 22 23
6
6.4
6.4.1
6.4.1.2
APPLICATION SERVICES
MAP Operations
General
Operation Specifiers
24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
Table 8 TIA/EIA-41 MAP Operation Specifiers

Operation Name H ShortMessageAnalyzed 0 G 1 F 1 Operation Specifier E 0 D 1 C 0 B 0 A 1 Decimal 105
40 41 42 43 44
6.4.2
Operation Definitions
45 46 47 48
Table 10 Summary of MAP Operations

Operation ShortMessageAnalyzed Reference 6.4.2.ax
49 50 51 52 53 54 55 56 57 58 59 60
86
Data Transfer Services
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
6.4.2.13
FeatureRequest
(See IS-848, page 5-04)
The omitted portion of this section is retained without modification. The FeatureRequest operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
FeatureRequest RETURN RESULT Parameters Field Identifier Length Contents FeatureResult AccessDeniedReason ActionCode AnnouncementList CallingPartyNumberString1 CallingPartyNumberString2 CallingPartySubaddress CarrierDigits ConferenceCallingIndicator Digits (Dialed) DisplayText DMH_AccountCodeDigits DMH_AlternateBillingDigits DMH_BillingDigits DMH_RedirectionIndicator GroupInformation MobileDirectoryNumber NoAnswerTime OneTimeFeatureIndicator PACAIndicator PilotNumber PreferredLanguageIndicator RedirectingNumberDigits RedirectingNumberString RedirectingSubaddress
ResumePIC
Value SET [NATIONAL 18] variable octets
Type M M M O O O O O O O O O O O O O O O O O O O O O O O O
O
Reference 6.3.2.2 6.3.2.2 6.5.2.67 6.5.2.1 6.5.2.2 6.5.2.6 6.5.2.23 6.5.2.24 6.5.2.25 6.5.2.28 6.5.2.49 6.5.2.58 6.5.2.bx 6.5.2.59 6.5.2.60 6.5.2.61 6.5.2.62 6.5.2.69 6.5.2.80 6.5.2.87 6.5.2.88 6.5.2.91 6.5.2.95 6.5.2.96 6.5.2.107 6.5.2.108 6.5.2.109
6.5.2.cu
Notes
a b c d d d d e f l, o g g g d h g d i j h d, p d d d
m
RoutingDigits TerminationList TerminationTriggers TriggerAddressList
O O O O
6.5.2.114 6.5.2.156 6.5.2.57 6.5.2.de
d k d n
MAP Operations
87
X.S0010-A
Notes: a. b. c. d. e. f. g. h. i. j. k. l.
m.
Include if access is denied. If included, no other optional parameters shall be included (with the exception of the AnnouncementList parameter). Include if action to be performed is not implied through presence of other parameters. Include if provision of one or more tones or announcements is required. Include if applicable. Include to direct that ongoing call be transformed into a Conference Call. Include if digits remain to be translated by the MSC. Include if applicable and for recording purposes (see DMH). Include for multi-leg calls. Include if modification to normal feature processing is required for call in progress. Include to indicate PACA priority level. Include if call routing is required. Include for local termination to an MS if a related feature is active.
Include to indicate the PIC where call processing is to resume.
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
n. o. p.
Include to indicate address associated with active WIN triggers. Refer to IS-764. This parameter may only be included if the AnnouncementList parameter is present.
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
88
MAP Operations
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
6.4.2.24
InterSystemPage
The omitted portion of this section is retained without modification. The InterSystemPage operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
InterSystemPage RETURN RESULT Parameters Field Identifier Length Contents WINCapability O O O 6.5.2.di zz Value SET [NATIONAL 18] variable octets Type M M Reference 6.3.2.2 6.3.2.2 Notes
Notes:
zz. Include to identify the Border MSCs WIN capabilities if the TriggerAddressList parameter was received.
MAP Operations
89
X.S0010-A
6.4.2.30
OriginationRequest
(See IS-826, page 5-07) (See IS-848, page 5-08) (See IS-737, page 5-36) (See IS-751, page 27)
1 2 3 4 5 6
The OriginationRequest operation is used to request call origination treatment on behalf of a registered MS. The OriginationRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows:
OriginationRequest INVOKE Parameters Field Identifier Length Contents BillingID (Originating) Digits (Dialed) ElectronicSerialNumber MSCID (Originating MSC) MSID OriginationTriggers TransactionCapability CallingPartyName CallingPartyNumberDigits1 CallingPartyNumberDigits2 CallingPartySubaddress CDMAServiceOption FeatureIndicator LocationAreaID MobileDirectoryNumber MSCIdentificationNumber OneTimeFeatureIndicator PC_SSN (Originating MSC) PreferredLanguageIndicator SenderIdentificationNumber ServingCellID TriggerType TDMAServiceCode WINCapability M M M M M M M O O O O O O O O O O O O O O O O O 6.5.2.16 6.5.2.58 6.5.2.63 6.5.2.82 6.5.2.bv 6.5.2.90 6.5.2.160 6.5.2.bw 6.5.2.21 6.5.2.22 6.5.2.25 6.5.2.f 6.5.2.ej 6.5.2.77 6.5.2.80 6.5.2.83 6.5.2.88 6.5.2.93 6.5.2.96 6.5.2.116 6.5.2.117 6.5.2.dh 6.5.2.i 6.5.2.di b c, d c, d c e f c, g h i j k i m c, n o p q a Value SET [NATIONAL 18] variable octets Type M M Timer: ORT Reference 6.3.2.1 6.3.2.1 Notes
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
90
MAP Operations
X.S0010-A
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
Notes: a. Include the identifier with which the MS last accessed the system, unless that identifier was a MIN-based IMSI, in which case the MobileIdentificationNumber (populated with the MIN derived from that IMSI) should be included. Include if calling party name information is known. Include if applicable. Send only the National (Significant) Number (with Nature of Number set to National) if the E.164 country code of the callers number matches the E.164 country code used for numbers from the MSCs Countrys Numbering Plan. Include to specify requested CDMA service information. Include to identify a feature invoked for the call (e.g., Three-Way Calling). Include if the current location area information is available. Include if available for recording purposes (see DMH). Include to identify the initiating MSC and to indicate that the MSC is capable of accepting digits in the international format. Include if any OneTimeFeatureIndicator status bits are set (i.e., have value of 1). Include if SS7 may be used for subsequent call redirection. Include if available. Include if different from the MSCIdentificationNumber to identify the functional entity sending the message. Include if the current serving cell identity is available. Include to identify the trigger encountered. Include to specify requested TDMA service information. Include to identify the WIN capabilities supported.
b. c. d.
e. f. g. h. i. j. k. l. m. n. o. p. q.
MAP Operations
91
X.S0010-A
The OriginationRequest operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
OriginationRequest RETURN RESULT Parameters Field Identifier Length Contents AccessDeniedReason ActionCode AnnouncementList CallingPartyNumberString1 CallingPartyNumberString2 CallingPartySubaddress CarrierDigits Digits (Dialed) DisplayText DMH_AccountCodeDigits DMH_AlternateBillingDigits DMH_BillingDigits DMH_ChargeInformation DMH_RedirectionIndicator DMH_ServiceID GroupInformation MobileDirectoryNumber NoAnswerTime OneTimeFeatureIndicator PilotNumber PreferredLanguageIndicator RedirectingNumberDigits RedirectingNumberString RedirectingSubaddress
ResumePIC
1 2 3 4 5 6
Type M M
Reference 6.3.2.2 6.3.2.2
Notes
7 8 9 10 11 12
O O O O O O O O O O O O O O O O O O O O O O O O
O
6.5.2.1 6.5.2.2 6.5.2.6 6.5.2.23 6.5.2.24 6.5.2.25 6.5.2.28 6.5.2.58 6.5.2.bx 6.5.2.59 6.5.2.60 6.5.2.61 6.5.2.eo 6.5.2.62 6.5.2.ei 6.5.2.69 6.5.2.80 6.5.2.87 6.5.2.88 6.5.2.95 6.5.2.96 6.5.2.107 6.5.2.108 6.5.2.109
6.5.2.cu
a b c d, e d, e d, e, f g h u, v d, e i i i i, j i, k l m i n o m g, p f d d, e
q
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
O O O O
6.5.2.114 6.5.2.156 6.5.2.57 6.5.2.de
g r s t
Notes: a. Include if access is denied. If included, no other optional parameters shall be included (with the exception of the AnnouncementList parameter).
57 58 59 60
92
MAP Operations
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
b. c. d. e. f. g. h.
Include if action to be performed is not implied through presence of other parameters. Include if one or more tones or announcements are to be applied to the MS. Include if the related feature is active. Include if a LocalTermination parameter is included in the TerminationList parameter. Include if a PSTNTermination parameter or an IntersystemTermination parameter is included within the TerminationList parameter. Include if applicable. Include if digits remain to be translated by the MSC. Encode the Digits (Dialed) as International if: the digits being returned are the results of a stored translation of the termination address into a destination address (e.g., the expansion of an abbreviated dialing string), and the serving MSC is known to be capable of accepting digits in International format (e.g., the MSCIdentificationNumber parameter was received.
i. j. k. l. m. n. o. p.
q.
Include if available for recording purposes (see DMH). Include to indicate charge information for the call. Include if redirection may apply. Include for recording purposes if a WIN service was invoked. Include for multi-leg calls. Include to request an override of the Serving MSCs default No Answer Time value. Include if modification to normal feature processing is required for the call in progress. This parameter may only be included if the AnnouncementList parameter is present.
r. s. t. u. v.
Include if call routing is required. Include to indicate processing in the Originating MSC for failed call attempts. Include to indicate address associated with active WIN triggers. Include if a LocalTermination parameter is included in the TerminationList parameter and display text shall be presented to the called MS. Include if the ActionCode parameter is included and is set to indicate that display text shall be presented to the calling MS.
MAP Operations
93
X.S0010-A
6.4.2.40
RoutingRequest
(See TIA/EIA-41, page 5-99) (See IS-771, page 5-23) (See IS-737, page 5-39) (See IS-751, page 29)
1 2 3 4 5 6
The RoutingRequest operation is used to inquire as to the preferred method of routing a pending call to the identified MS. The RoutingRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows:
RoutingRequest INVOKE Parameters Field Identifier Length Contents BillingID (Originating) ElectronicSerialNumber MSCID (Originating MSC) MSID SystemMyTypeCode (Originating MSC) AlertCode CallingPartyName CallingPartyNumberDigits1 CallingPartyNumberDigits2 CallingPartyNumberString1 CallingPartyNumberString2 CallingPartySubaddress CDMAServiceOption DestinationDigits DisplayText DMH_AccountCodeDigits DMH_AlternateBillingDigits DMH_BillingDigits LegInformation LocationAreaID MobileDirectoryNumber MSCIdentificationNumber NoAnswerTime OneTimeFeatureIndicator PC_SSN (Originating MSC) PilotBillingID PilotNumber RedirectingNumberDigits RedirectingPartyName M M M M M O O O O O O O O O O O O O O O O O O O O O O O O 6.5.2.16 6.5.2.63 6.5.2.82 6.5.2.bv 6.5.2.147 6.5.2.3 6.5.2.bw 6.5.2.21 6.5.2.22 6.5.2.21 6.5.2.22 6.5.2.25 6.5.2.f 6.5.2.56 6.5.2.bx 6.5.2.59 6.5.2.60 6.5.2.61 6.5.2.75 6.5.2.77 6.5.2.80 6.5.2.83 6.5.2.87 6.5.2.88 6.5.2.93 6.5.2.94 6.5.2.95 6.5.2.107 6.5.2.by b r, u, v c, t c, t c c c w d, e c, y f f f g f, h f i j k l m m c, t s, u v a Value SET [NATIONAL 18] variable octets Type M M Timer: RRT Reference 6.3.2.1 6.3.2.1 Notes
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
94
MAP Operations
X.S0010-A
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
RedirectingSubaddress SenderIdentificationNumber TerminationTreatment TerminationTriggers TDMAServiceCode TriggerAddressList VoiceMailboxNumber VoiceMailboxPIN
O O O O O O O O
6.5.2.109 6.5.2.116 6.5.2.158 6.5.2.159 6.5.2.i 6.5.2.de 6.5.2.164 6.5.2.165
c n o f x u p q
Notes: a. b. c. d. e. f. g. h. i. j. k. l. m. n. o. p. q. r. s. t. Required to identify originating call. Include to specify special alerting treatment. Include if related feature is active. Optionally include if TerminationTreatment parameter value is Dialogue, to select a dialogue or to provide information to a dialogue. Optionally include if TerminationTreatment parameter value VoiceMailRetrieval or VoiceMailStorage to select the voice mail system. is
Include if available and if TerminationTreatment parameter value is MS termination. Include if TerminationTreatment parameter value is MS termination and this is a multileg call (e.g., an FA call). May be included from VLR to MSC-V. Usage is not defined from HLR to VLR. Include to identify Originating MSC. Include to inform the serving system of the recommended no-answer time-out. Include if modification to normal feature processing is required for call in progress. Include if available (e.g., from received parameter or lower layers) for subsequent call redirection. Include on a multileg call. Include to identify the functional entity sending the message. Include to differentiate termination types, defaulting to value MS termination. Include if the TerminationTreatment parameter value is VoiceMailRetrieval or VoiceMailStorage and the mailbox is not the MobileIdentificationNumber. Optional, if the TerminationTreatment parameter value is VoiceMailRetrieval; or VoiceMailStorage. Include if available when a Calling Party Number String parameter has been included. Include if available when a Redirecting Number String parameter has been included. Digits are included for service logic invocations from the Serving MSC. Strings are included for presentation to the MS.
MAP Operations
95
X.S0010-A
u. v.
Include to indicate address associated with active WIN triggers. When this message is used in accessing a feature at an adjunct MSC (e.g., for voice message retrieval), the HLR includes the type of MSID appropriate to the MS and the feature being accessed; otherwise the HLR includes the type of MSID last received from the Serving System. The VLR includes the type of MSID last received from the Serving MSC; this may not be the type of MSID received from the HLR. Include to identify requested CDMA service information. Include to identify requested TDMA service information.
1 2 3 4 5 6 7 8 9 10 11 12 13
w. x.
The InterSystemPage operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
RoutingRequest RETURN RESULT Parameters Field Identifier Length Contents CDMAServiceOption TDMAServiceCode WINCapability O O O O O 6.5.2.f 6.5.2.i 6.5.2.di g h i Value SET [NATIONAL 18] variable octets Type M M Reference 6.3.2.2 6.3.2.2 Notes
14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
Notes:
33 34 35
g. h. i.
Include to identify accepted CDMA service information. Include to identify accepted TDMA service information Include when received from the Border MSC (i.e., InterSystemPage RETURN RESULT) to identify the Border MSCs WIN capabilities.
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
96
MAP Operations
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
6.4.2.46
TransferToNumberRequest
(See IS-826, page 5-11) (See IS-737, page 5-43) (See IS-751, page 31)
The TransferToNumberRequest operation is used during feature processing to obtain an MSs forward-to number from the HLR. The TransferToNumberRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows:
TransferToNumberRequest INVOKE Parameters Field Identifier Length Contents ElectronicSerialNumber MSID RedirectionReason SystemMyTypeCode (MSC) BillingID (Originating) CDMAServiceOption GroupInformation LegInformation MSCID (Originating MSC) MSCIdentificationNumber PilotBillingID PilotNumber SenderIdentificationNumber TransactionCapability TDMAServiceCode WINCapability M M M M O O O O O O O O O O O O 6.5.2.63 6.5.2.bv 6.5.2.110 6.5.2.147 6.5.2.16 6.5.2.f 6.5.2.69 6.5.2.75 6.5.2.82 6.5.2.83 6.5.2.94 6.5.2.95 6.5.2.116 6.5.2.160 6.5.2.i 6.5.2.di a j b c d e f f g e k i h Value SET [NATIONAL 18] variable octets Type M M Timer: TTNRT Reference 6.3.2.1 6.3.2.1 Notes
Notes: a. b. Include to identify the Originating MSC and its BillingID for subsequent call redirection. Include if available (i.e., if provided in the associated RoutingRequest INVOKE or LocationRequest RETURN RESULT) for the None Reachable termination trigger. Include if available (i.e., if provided in the associated RoutingRequest INVOKE or LocationRequest RETURN RESULT) for any termination trigger except None Reachable. Include on TIA/EIA-41 or later. Include on IS-41-C or later. Include if available. Include to identify the network entity sending the message.
c.
d. e. f. g.
MAP Operations
97
X.S0010-A
h. i. j. k.
Use the MobileIdentificationNumber form of the MSID if the IMSI is known to be a MIN-based IMSI. Include to identify the WIN capabilities supported. Include if CDMA channel is in use to allow distinctive forwarding based on Service Type. Include if TDMA channel is in use to allow distinctive forwarding based on Service Type.
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
98
MAP Operations
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
6.4.2.51
UnsolicitedResponse
(See IS-771, page 5-27) (See IS-737, page 5-44)
The omitted portion of this section is retained without modification. The UnsolicitedResponse operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
UnsolicitedResponse RETURN RESULT Parameters Field Identifier Length Contents AccessDeniedReason AlertCode BillingID (Originating) CallingPartyName CallingPartyNumberDigits1 CallingPartyNumberDigits2 CallingPartyNumberString1 CallingPartyNumberString2 CallingPartySubaddress DMH_AccountCodeDigits DMH_AlternateBillingDigits DMH_BillingDigits ExtendedMSCID (Originating MSC) ExtendedSystemMyTypeCode (Originating MSC) LegInformation MobileDirectoryNumber MSCIdentificationNumber (Origination MSC) OneTimeFeatureIndicator PC_SSN (Originating MSC) PilotBillingID PilotNumber PreferredLanguageIndicator RedirectingNumberDigits RedirectingNumberString RedirectingPartyName RedirectingSubaddress TerminationTreatment O O O O O O O O O O O O O O O O O O O O O O O O O O O 6.5.2.1 6.5.2.16 6.5.2.16 6.5.2.bw 6.5.2.21 6.5.2.22 6.5.2.23 6.5.2.24 6.5.2.25 6.5.2.59 6.5.2.60 6.5.2.61 6.5.2.64 6.5.2.65 6.5.2.75 6.5.2.80 6.5.2.83 6.5.2.88 6.5.2.93 6.5.2.94 6.5.2.95 6.5.2.96 6.5.2.107 6.5.2.108 6.5.2.by 6.5.2.109 6.5.2.158 i a b g, i d d c c c d d d e f g d g g h g g g d c g c g Value SET [NATIONAL 18] variable octets Type M M Reference 6.3.2.2 6.3.2.2 Notes
MAP Operations
99
X.S0010-A
TerminationTriggers TriggerAddressList
O O
6.5.2.159 6.5.2.de
g g
1 2 3 4
Notes: a. b. c. d. e. f. g. h. i. Include to specify special alerting treatment. Include for subsequent call redirection at the originating MSC and for recording purposes (see DMH). Include if related feature is active. Include if available. Include to identify originating system. Include to identify originating system manufacturer. Include if available (e.g., provided in the associated RoutingRequest INVOKE). Include if SS7 may be used for subsequent call redirection. Include when the MS responded to a page in the border system with a service type that differs from the one used by the system that paged.
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
100
MAP Operations
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
6.4.2.h
ServiceRequest
(See IS-826, page 5-15)
The ServiceRequest (SERVREQ) operation is used by service logic to invoke specific service logic execution on another network entity (NE) containing the service logic for the requested services. The ServiceRequest operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows:
ServiceRequest INVOKE Parameters Field Identifier Length Contents ServiceID AccessDeniedReason AvailabilityType BillingID CallingPartyName CallingPartyNumberDigits1 CallingPartyNumberDigits2 CallingPartySubaddress CarrierDigits CDMAServiceOption ConditionallyDeniedReason DataAccessElementList DestinationDigits Digits (Dialed) DMH_RedirectionIndicator DMH_ServiceID ElectronicSerialNumber ExtendedMSCID FeatureIndicator GroupInformation LegInformation LocationAreaID MobileDirectoryNumber MSCID (Invoking) MSCIdentificationNumber (Invoking) MSID PC_SSN PilotBillingID M O O O O O O O O O O O O O O O O O O O O O O O O O O O 6.5.2.bz 6.5.2.15 6.5.2.82 6.5.2.16 6.5.2.bw 6.5.2.21 6.5.2.22 6.5.2.25 6.5.2.28 6.5.2.f 6.5.2.48 6.5.2.cd 6.5.2.56 6.5.2.58 6.5.2.62 6.5.2.ej 6.5.2.63 6.5.2.64 6.5.2.ej 6.5.2.69 6.5.2.75 6.5.2.77 6.5.2.80 6.5.2.82 6.5.2.83 6.5.2.bv 6.5.2.93 6.5.2.94 c, d c, e a, f a a b a p y c, d c q a c c, r c, s c, t c, u c c c c, g c, h c, i c, g i, j c Value SET [NATIONAL 18] variable octets Type M M Timer: SVRT Reference 6.3.2.1 6.3.2.1 Notes
MAP Operations
101
X.S0010-A
PilotNumber PreferredLanguageIndicator RedirectingPartyName RedirectingNumberDigits RedirectingSubaddress RedirectionReason RoutingDigits SenderIdentificationNumber ServingCellID SystemMyTypeCode TDMAServiceCode TerminationAccessType TimeDateOffset TimeOfDay TransactionCapability TriggerType WINCapability
O O O O O O
6.5.2.95 6.5.2.96 6.5.2.by 6.5.2.107 6.5.2.109 6.5.2.110 6.5.2.114
c a a a a a v k c l z c c, w c, x m n o
1 2 3 4 5 6 7 8 9 10 11
O O O O O O O O O O
6.5.2.116 6.5.2.117 6.5.2.147 6.5.2.i 6.5.2.155 6.5.2.dd 6.5.2.em 6.5.2.160 6.5.2.dh 6.5.2.di
12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
Notes: a. b. c. d. e. f. g. h. i. j. k. l. m. Include if available. Include if user provided, passed screening calling party number is available. Include if applicable. Include if a RoutingRequest operation was completed prior to the ServiceRequest operation, and access was denied. Include when MS is predictably unavailable for Call Delivery (e.g., slotted mode or sleep mode). Include to correlate service usage with call instance. Include if the MSID is available and is not the same as the Digits (Dialed). Include to identify invoking MSC. Include if SS7 is used. Not for international applications. Include to identify invoking FE. Include to indicate the vendor type of the invoking FE. Include to indicate the capabilities of the MSC that the invoking FE (e.g., HLR, SCP, SN) chooses to convey to the NE (e.g., SCP, SN) with the service logic for the requested services. Include to identify the trigger encountered by the MSC. Include to indicate the WIN capabilities supported. Include to identify the interexchange carrier for call routing.
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
n. o. p.
58 59 60
102
MAP Operations
X.S0010-A
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
q. r. s. t. u. v. w. x. y. z.
Include to identify the network address of the called party for call routing. Include to identify the Service Logic Program invoked on behalf of the MS. Include to identify the MS. Include to identify MSC serving the MS if not indicated by the MSCID parameter. Include to identify a feature invoked for the call (e.g., Three-Way Calling). Include to identify special routing information for call routing. Include to indicate the time offset of Local Civil Time with respect to Coordinated Universal Time (UTC). Include to indicate the time of day in UTC. Include to specify CDMA service information. Include to specify TDMA service information.
MAP Operations
103
X.S0010-A
The ServiceRequest operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
ServiceRequest RETURN RESULT Parameters Field Identifier Length Contents AccessDeniedReason ActionCode AlertCode AnnouncementList CallingPartyName CallingPartyNumberString1 CallingPartyNumberString2 CallingPartySubaddress CarrierDigits Digits (Dialed) DisplayText DMH_AccountCodeDigits DMH_AlternateBillingDigits DMH_BillingDigits DMH_ChargeInformation DMH_RedirectionIndicator DMH_ServiceID GroupInformation MobileDirectoryNumber NoAnswerTime RedirectingNumberDigits RedirectingNumberString RedirectingPartyName RedirectingSubaddress
ResumePIC
1 2 3 4 5 6
Type M M
Reference 6.3.2.2 6.3.2.2
Notes
7 8 9 10 11 12
O O O O O O O O O O O O O O O O O O O O O O O O
O
6.5.2.1 6.5.2.2 6.5.2.3 6.5.2.6 6.5.2.bw 6.5.2.23 6.5.2.24 6.5.2.25 6.5.2.28 6.5.2.58 6.5.2.bx 6.5.2.59 6.5.2.60 6.5.2.61 6.5.2.eo 6.5.2.62 6.5.2.ei 6.5.2.69 6.5.2.80 6.5.2.87 6.5.2.107 6.5.2.108 6.5.2.by 6.5.2.109
6.5.2.cu
b c d e a a a a a f a a a a a, k a i a a a a a a a
q
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
RoutingDigits TerminationList TriggerAddressList
O O O
6.5.2.114 6.5.2.156 6.5.2.de
a h a, j
51 52 53
Notes: a. b. Include if applicable. Include if service logic determines access to the MS is denied.
54 55 56 57 58 59 60
104
MAP Operations
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
c. d. e. f.
g.
Include if action to be performed is not implied through presence of other parameters. Include to specify special alerting treatment. Include if one or more tones or announcements are to be applied to the MS. Include if digits remain to be translated by the MSC.
h. i. j. k.
Include if call routing is required. Include for recording purposes if a WIN service was invoked. Include to indicate address associated with active WIN triggers. Include to indicate charge information for the call.
MAP Operations
105
X.S0010-A
6.4.2.i
AnalyzedInformation
(See IS-848, page 5-12)
1 2 3 4 5 6 7 8
The AnalyzedInformation (ANLYZD) operation is used by the MSC to provide notification to a service logic network element (e.g., SCP, SN) that a trigger criteria at the Analyzed_Information DP has been satisfied. Service logic may then invoke a service or services. The AnalyzedInformation operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows:
AnalyzedInformation INVOKE Parameters Field Identifier Length Contents BillingID (Originating) Digits (Dialed) MSCID (Originating) TransactionCapability TriggerType WINCapability CallingPartyName CallingPartyNumberDigits1 CallingPartyNumberDigits2 CallingPartySubaddress CarrierDigits CDMAServiceOption ConferenceCallingIndicator DestinationDigits DMH_BillingIndicator DMH_RedirectionIndicator ElectronicSerialNumber FeatureIndicator LocationAreaID MobileDirectoryNumber MSCIdentificationNumber MSID OneTimeFeatureIndicator PreferredLanguageIndicator RedirectingNumberDigits RedirectingPartyName RedirectingSubaddress M M M M M M O O O O O O O O O O O O O O O O O O O O O 6.5.2.16 6.5.2.58 6.5.2.82 6.5.2.160 6.5.2.dh 6.5.2.di 6.5.2.bw 6.5.2.21 6.5.2.22 6.5.2.25 6.5.2.28 6.5.2.f 6.5.2.49 6.5.2.56 6.5.2.ep 6.5.2.62 6.5.2.63 6.5.2.ej 6.5.2.77 6.5.2.80 6.5.2.83 6.5.2.bv 6.5.2.88 6.5.2.96 6.5.2.107 6.5.2.by 6.5.2.109 e e e c d e e e e m, n y f m, o x p g, q r h, s i j g, q k b a Value SET [NATIONAL 18] variable octets Type M M Timer: ANZT Reference 6.3.2.1 6.3.2.1 Notes
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
106
MAP Operations
X.S0010-A
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
RoutingDigits ServingCellID SystemMyTypeCode TDMAServiceCode TerminationAccessType TimeDateOffset TimeOfDay
O O O O O O O
6.5.2.114 6.5.2.117 6.5.2.147 6.5.2.i 6.5.2.155 6.5.2.dd 6.5.2.em
m, t h, u
z l v w
Notes: a. b. c. d. e. f. g. h. i. j. k. l. m. n. o. p. q. r. s. t. u. v. w. x. y. Include to identify the call. Include to identify the requesting MSC. Include to identify the trigger encountered. Include to identify the WIN capabilities supported. Include if available (i.e., provided in call origination). Include to indicate the number of conferees already in the call. Include to identify the MS. Include if available (information related to MS origination). Include if available for recording purposes (see DMH). Include to identify the MSC sending the message, if the MSC is capable of accepting digits in the international format. Include if any OneTimeFeatureIndicator status bits are set (i.e., have value of 1). Include if call involves a special access situation (e.g., Roamer port access). Include if applicable and a routing address is available. Include to identify the interexchange carrier for call routing. Include to identify the network address of the called party for call routing. Include to identify the reason for extending the call. Include if available. Include to identify a feature invoked for the call (e.g., Three-Way Calling). Include if the current location area information is available. Include to identify special routing information for call routing. Include if the current serving cell identity is available. Include to indicate the time offset of Local Civil Time with respect to Coordinated Universal Time (UTC). Include to indicate the time of day in UTC. Include to indicate the type of special billing to be applied for this call (e.g., Freephone call, third party charging). Include to indicate the CDMA service information for the call.
MAP Operations
107
X.S0010-A
z.
Include to indicate the TDMA service information for the call.
1 2
The AnalyzedInformation operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
AnalyzedInformation RETURN RESULT Parameters Field Identifier Length Contents AccessDeniedReason ActionCode AlertCode AnnouncementList CarrierDigits ConferenceCallingIndicator Digits (Dialed) DisplayText DMH_AccountCodeDigits DMH_AlternateBillingDigits DMH_BillingDigits DMH_BillingIndicator DMH_ChargeInformation DMH_RedirectionIndicator DMH_ServiceID NoAnswerTime OneTimeFeatureIndicator RedirectingNumberDigits
ResumePIC
3 4 5 6 7 8
Type M M
Reference 6.3.2.2 6.3.2.2
Notes
9 10 11 12 13 14
O O O O O O O O O O O O O O O O O O
O
6.5.2.1 6.5.2.2 6.5.2.3 6.5.2.6 6.5.2.28 6.5.2.49 6.5.2.58 6.5.2.bx 6.5.2.59 6.5.2.60 6.5.2.61 6.5.2.ep 6.5.2.eo 6.5.2.62 6.5.2.ei 6.5.2.87 6.5.2.88 6.5.2.107
6.5.2.cu
a b p c d e f d, m g g g g, q g, r g, h n i j d
k
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
O O O O
6.5.2.114 6.5.2.156 6.5.2.159 6.5.2.de
d l d d, o
43 44 45 46 47 48
Notes: a. b. c. d. Include if access is denied. If included, no other optional parameters shall be included (with the exception of the AnnouncementList parameter). Include if action to be performed is not implied through presence of other parameters. Include if one or more tones or announcements are to be applied to the MS. Include if applicable.
49 50 51 52 53 54 55 56 57 58 59 60
108
MAP Operations
X.S0010-A
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
e. f. g. h. i. j.
k.
Include to direct that ongoing call be transformed into a Conference Call. Include if digits remain to be translated by the MSC. Include if available for recording purposes (see DMH). Include if redirection may apply. Include to request an override of the Serving MSC's default No Answer Time value. Include if modification to normal feature processing is required for the call in progress.
l. m. n. o. p. q. r.
Include if call routing is required. Refer to IS-764. Include for recording purposes if a WIN service was invoked. Include to indicate address associated with active WIN triggers. Include to specify special alerting treatment. Include to indicate the type of billing to be applied for the call. Include to indicate the charge information for the call.
MAP Operations
109
X.S0010-A
6.4.2.m
FacilitySelectedAndAvailable
(See IS-848, page 5-17)
1 2 3 4
The omitted portion of this section is retained without modification. The FacilitySelectedAndAvailable operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
FacilitySelectedAndAvailable RETURN RESULT Parameters Field Identifier Length Contents AccessDeniedReason ActionCode AlertCode DisplayText DMH_AccountCodeDigits DMH_AlternateBillingDigits DMH_BillingDigits DMH_ChargeInformation DMH_RedirectionIndicator DMH_ServiceID NoAnswerTime OneTimeFeatureIndicator
ResumePIC
5 6 7 8 9 10 11 12
Type M M
Reference 6.3.2.2 6.3.2.2
Notes
13 14 15 16 17 18
O O O O O O O O O O O O
O
6.5.2.1 6.5.2.2 6.5.2.3 6.5.2.bx 6.5.2.59 6.5.2.60 6.5.2.61 6.5.2.eo 6.5.2.62 6.5.2.ei 6.5.2.87 6.5.2.88
6.5.2.cu
a b c d, j e e e e, m e, f k g h
i
19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42
TerminationTriggers TriggerAddressList
O O
6.5.2.159 6.5.2.de
d d, l
Notes: a. b. c. d. e. f. g. h. Include if access is denied. If included, no other optional parameters shall be included (with the exception of the AnnouncementList parameter). Include if action to be performed is not implied through presence of other parameters. Include to specify special alerting treatment. Include if applicable. Include if available for recording purposes (see DMH). Include if redirection may apply. Include to request an override of the Serving MSC's default No Answer Time value. Include if modification to normal feature processing is required for the call in progress.
43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
110
MAP Operations
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
i.
j. k. l. m.
Refer to IS-764. Include for recording purposes if a WIN service was invoked. Include to indicate address associated with active WIN triggers. Include to indicate charge information for the call.
MAP Operations
111
X.S0010-A
6.4.2.t
TBusy
(See IS-826, page 5-29)
1 2 3 4 5 6
The TBusy (TBUSY) operation is used by an MSC to obtain call treatment instructions from an SCP or SN for the called party. The TBusy operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows:
TBusy INVOKE Parameters Field Identifier Length Contents BillingID (Invoking) MSCID TransactionCapability TriggerType WINCapability CallingPartyNumberDigits1 CallingPartyNumberDigits2 CallingPartySubaddress CDMAServiceOption ElectronicSerialNumber GroupInformation LegInformation LocationAreaID MobileDirectoryNumber MSCIdentificationNumber MSID OneTimeFeatureIndicator PilotBillingID PilotNumber PreferredLanguageIndicator RedirectingNumberDigits RedirectingSubaddress RedirectionReason ServingCellID SystemMyTypeCode TerminationAccessType TDMAServiceCode M M M M M O O O O O O O O O O O O O O O O O O O O O O 6.5.2.16 6.5.2.82 6.5.2.160 6.5.2.dh 6.5.2.di 6.5.2.21 6.5.2.22 6.5.2.25 6.5.2.f 6.5.2.63 6.5.2.69 6.5.2.75 6.5.2.77 6.5.2.80 6.5.2.83 6.5.2.bv 6.5.2.88 6.5.2.94 6.5.2.95 6.5.2.96 6.5.2.107 6.5.2.109 6.5.2.110 6.5.2.117 6.5.2.147 6.5.2.155 6.5.2.i f m c d e e e l f f f g h, i b h, k j f f g e e f g a b Value SET [NATIONAL 18] variable octets Type M M Timer: TBT Reference 6.3.2.1 6.3.2.1 Notes
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
Notes: a. Include to identify the call at the invoking MSC
57 58 59 60
112
MAP Operations
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
b. c. d. e. f. g. h. i. j. k. l. m.
Include to identify the invoking MSC. Include to identify the trigger encountered. Include to identify the WIN capabilities supported. Include if available (i.e., provided in call origination). Include if available. Include if available. (Note: this information element may not be available when this operation is initiated by a non-Serving MSC.) One must be present for use as a service key. Include if available for recording purposes (see DMH). Include if any OneTimeFeatureIndicator status bits are set (i.e., have value of 1). Include to identify the MS. Include to specify current CDMA service information. Include to specify current TDMA service information.
MAP Operations
113
X.S0010-A
The TBusy operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
TBusy RETURN RESULT Parameters Field Identifier Length Contents AccessDeniedReason ActionCode AnnouncementList CallingPartyNumberString1 CallingPartyNumberString2 CarrierDigits DisplayText DMH_AccountCodeDigits DMH_AlternateBillingDigits DMH_BillingDigits DMH_RedirectionIndicator DMH_ServiceID GroupInformation OneTimeFeatureIndicator PilotNumber PreferredLanguageIndicator RedirectingNumberDigits
ResumePIC
1 2 3 4 5
Type M M
Reference 6.3.2.2 6.3.2.2
Notes
6 7 8 9 10 11
O O O O O O O O O O O O O O O O O
O
6.5.2.1 6.5.2.2 6.5.2.6 6.5.2.23 6.5.2.24 6.5.2.28 6.5.2.bx 6.5.2.59 6.5.2.60 6.5.2.61 6.5.2.62 6.5.2.ei 6.5.2.69 6.5.2.88 6.5.2.95 6.5.2.96 6.5.2.107
6.5.2.cu
a b c d, e d, e l d, e, m f f f f n g h g l, o i
j
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
O O O O
6.5.2.114 6.5.2.156 6.5.2.57 6.5.2.de
l k l l, p
41 42 43
Notes: a. b. c. d. e. f. g. Include if access is denied. If included, no other optional parameters shall be included (with the exception of the AnnouncementList parameter). Include if action to be performed is not implied through presence of other parameters. Include if one or more tones or announcements are to be applied to the MS. Include if a LocalTermination parameter is included in the TerminationList parameter. Include if the related feature is active. Include if available for recording purposes (see DMH). Include for multi-leg calls.
44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
114
MAP Operations
X.S0010-A
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
h. i.
j.
Include if modification to normal feature processing is required for the call in progress. Include if call is being redirected.
k. l. m. n. o. p.
Include if call routing is required. Include if applicable. Refer to IS-764. Include for recording purposes if a WIN service was invoked. This parameter may only be included if the AnnouncementList parameter is present. Include to indicate address associated with active WIN triggers.
MAP Operations
115
X.S0010-A
6.4.2.u
TNoAnswer
(See IS-826, page 5-33)
1 2 3 4 5 6
The TNoAnswer (TNOANS) operation is used by an MSC to obtain call treatment instructions from an SCP or SN for the called party. The TNoAnswer operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows:
TNoAnswer INVOKE Parameters Field Identifier Length Contents BillingID (Invoking) MSCID TransactionCapability TriggerType WINCapability CallingPartyNumberDigits1 CallingPartyNumberDigits2 CallingPartySubaddress CDMAServiceOption ElectronicSerialNumber GroupInformation LegInformation LocationAreaID MobileDirectoryNumber MSCIdentificationNumber MSID OneTimeFeatureIndicator PilotBillingID PilotNumber PreferredLanguageIndicator RedirectingNumberDigits RedirectingSubaddress RedirectionReason ServingCellID SystemMyTypeCode TerminationAccessType TDMAServiceCode M M M M M O O O O O O O O O O O O O O O O O O O O O O 6.5.2.16 6.5.2.82 6.5.2.160 6.5.2.dh 6.5.2.di 6.5.2.21 6.5.2.22 6.5.2.25 6.5.2.f 6.5.2.63 6.5.2.69 6.5.2.75 6.5.2.77 6.5.2.80 6.5.2.83 6.5.2.bv 6.5.2.88 6.5.2.94 6.5.2.95 6.5.2.96 6.5.2.107 6.5.2.109 6.5.2.110 6.5.2.117 6.5.2.147 6.5.2.155 6.5.2.i f m c d e e e l f f f g h, i b h, k j f f g e e f g a b Value SET [NATIONAL 18] variable octets Type M M Timer: TNAT Reference 6.3.2.1 6.3.2.1 Notes
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
Notes: a. Include to identify the call at the invoking MSC.
57 58 59 60
116
MAP Operations
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
b. c. d. e. f. g. h. i. j. k. l. m.
Include to identify the invoking MSC. Include to identify the trigger encountered. Include to identify the WIN capabilities supported. Include if available (i.e., provided in call origination). Include if available. Include if available. (Note: this information element may not be available when this operation is initiated by a non-Serving MSC.) One must be present for use as a service key. Include if available for recording purposes (see DMH). Include if any OneTimeFeatureIndicator status bits are set (i.e., have value of 1). Include to identify the MS. Include to specify current CDMA service information. Include to specify current TDMA service information.
MAP Operations
117
X.S0010-A
The TNoAnswer operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
TNoAnswer RETURN RESULT Parameters Field Identifier Length Contents AccessDeniedReason ActionCode AnnouncementList CallingPartyNumberString1 CallingPartyNumberString2 CarrierDigits DisplayText DMH_AccountCodeDigits DMH_AlternateBillingDigits DMH_BillingDigits DMH_RedirectionIndicator DMH_ServiceID GroupInformation OneTimeFeatureIndicator PilotNumber PreferredLanguageIndicator RedirectingNumberDigits
ResumePIC
1 2 3 4 5
Type M M
Reference 6.3.2.2 6.3.2.2
Notes
6 7 8 9 10 11
O O O O O O O O O O O O O O O O O
O
6.5.2.1 6.5.2.2 6.5.2.6 6.5.2.23 6.5.2.24 6.5.2.28 6.5.2.bx 6.5.2.59 6.5.2.60 6.5.2.61 6.5.2.62 6.5.2.ei 6.5.2.69 6.5.2.88 6.5.2.95 6.5.2.96 6.5.2.107
6.5.2.cu
a b c d, e d, e l d, e, m f f f f n g h g l, o i
j
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
O O O O
6.5.2.114 6.5.2.156 6.5.2.57 6.5.2.de
l k l l, p
41 42 43
Notes: a. b. c. d. e. f. g. Include if access is denied. If included, no other optional parameters shall be included (with the exception of the AnnouncementList parameter). Include if action to be performed is not implied through presence of other parameters. Include if one or more tones or announcements are to be applied to the MS. Include if a LocalTermination parameter is included in the TerminationList parameter. Include if the related feature is active. Include if available for recording purposes (see DMH). Include for multi-leg calls.
44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
118
MAP Operations
X.S0010-A
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
h. i.
j.
Include if modification to normal feature processing is required for the call in progress. Include if call is being redirected.
k. l. m. n. o. p.
Include if call routing is required. Include if applicable. Refer to IS-764. Include for recording purposes if a WIN service was invoked. This parameter may only be included if the AnnouncementList parameter is present. Include to indicate address associated with active WIN triggers.
MAP Operations
119
X.S0010-A
6.4.2.aa
OAnswer
(See IS-826, page 5-40)
1 2 3 4 5 6 7
The OAnswer (OANSWER) operation is used by the MSC to provide notification to a service logic network entity that a trigger criteria at the O_Answer DP has been satisfied. Service logic may then invoke a service or services. The OAnswer operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP UNIDIRECTIONAL package. The Parameter Set is encoded as follows:
OAnswer INVOKE Parameters Field Identifier Length Contents BillingID (Originating) ElectronicSerialNumber MSCID (Originating) MSID TimeDateOffset TimeOfDay TriggerType CDMAServiceOption FeatureIndicator LocationAreaID MobileDirectoryNumber MSCIdentificationNumber RedirectionReason ServingCellID SystemMyTypeCode TDMAServiceCode M M M M M M M O O O O O O O O O 6.5.2.16 6.5.2.63 6.5.2.82 6.5.2.bv 6.5.2.dd 6.5.2.em 6.5.2.dh 6.5.2.f 6.5.2.ej 6.5.2.77 6.5.2.80 6.5.2.83 6.5.2.110 6.5.2.117 6.5.2.147 6.5.2.i n a b c d e f g m k h, i j l f h, m Value SET [NATIONAL 18] variable octets Type M M Reference 6.3.2.1 6.3.2.1 Notes
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
Notes: a. b. c. d. e. f. g. h. i. Include to identify the call. Include to identify the subscriber. Include to identify the requesting MSC. Include to identify MS. Include to indicate the time offset of Local Civil Time with respect to Coordinated Universal Time (UTC). Include to indicate the time of day in UTC. Include to identify the trigger encountered. Include if applicable. Include if the current location area information is available.
42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
120
MAP Operations
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
j. k. l. m. n.
Include if available for recording purposes (see DMH). Include to identify a feature invoked for the call (e.g., Three-Way Calling). Include to identify the MSC initiating the message.Include if the current serving cell identity is available. Include if available to indicate the CDMA service information for the call. Include if available to indicate the TDMA service information for the call.
MAP Operations
121
X.S0010-A
6.4.2.ad
TAnswer
(See IS-826, page 5-45)
1 2 3 4 5 6 7
The TAnswer (TANSWER) operation is used by the MSC to provide notification to a service logic network entity that a trigger criteria at the T_Answer DP has been satisfied. Service logic may then invoke a service or services. The TAnswer operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP UNIDIRECTIONAL package. The Parameter Set is encoded as follows:
TAnswer INVOKE Parameters Field Identifier Length Contents BillingID (Originating) ElectronicSerialNumber MSCID MSID TimeDateOffset TimeOfDay TransactionCapability TriggerType WINCapability CDMAServiceOption FeatureIndicator LocationAreaID MobileDirectoryNumber MSCIdentificationNumber RedirectionReason ServingCellID SystemMyTypeCode TerminationAccessType TDMAServiceCode M M M M M M M M M O O O O O O O O O O 6.5.2.16 6.5.2.63 6.5.2.82 6.5.2.bv 6.5.2.dd 6.5.2.em 6.5.2.160 6.5.2.dh 6.5.2.di 6.5.2.f 6.5.2.ej 6.5.2.77 6.5.2.80 6.5.2.83 6.5.2.110 6.5.2.117 6.5.2.147 6.5.2.155 6.5.2.i m o n j g, h i k f g, l f a b c b d e Value SET [NATIONAL 18] variable octets Type M M Reference 6.3.2.1 6.3.2.1 Notes
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
Notes: a. b. c. d. e. f. Include to identify the call. Include to identify MS. Include to identify the requesting MSC. Include to indicate the time offset of Local Civil Time with respect to Coordinated Universal Time (UTC). Include to indicate the time of day in UTC. Include to identify the trigger encountered.
48 49 50 51 52 53 54 55 56 57 58 59 60
122
MAP Operations
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
g. h. i. j. k. l. m. n. o.
Include if applicable. Include if the current location area information is available. Include if available for recording purposes (see DMH). Include to identify a feature invoked for the call (e.g., Three-Way Calling). Include to identify the MSC sending the message. Include if the current serving cell identity is available. Include if call involves a special access situation (e.g., Roamer port access). Include if available to indicate the CDMA service information for the call. Include if available to indicate the TDMA service information for the call.
MAP Operations
123
X.S0010-A
6.4.2.ag
OCalledPartyBusy
(See IS-848, page 5-23)
1 2 3 4
The omitted portion of this section is retained without modification. The OCalledPartyBusy operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
OCalledPartyBusy RETURN RESULT Parameters Field Identifier Length Contents AccessDeniedReason ActionCode AnnouncementList CarrierDigits DMH_AccountCodeDigits DMH_AlternateBillingDigits DMH_BillingDigits DMH_ChargeInformation DMH_RedirectionIndicator DMH_ServiceID NoAnswerTime OneTimeFeatureIndicator PreferredLanguageIndicator RedirectingNumberDigits RoutingDigits TerminationList TriggerAddressList O O O O O O O O O O O O O O O O O 6.5.2.1 6.5.2.2 6.5.2.6 6.5.2.28 6.5.2.59 6.5.2.60 6.5.2.61 6.5.2.eo 6.5.2.62 6.5.2.ei 6.5.2.87 6.5.2.88 6.5.2.96 6.5.2.107 6.5.2.114 6.5.2.156 6.5.2.de n a b c e e e d, e e, f g h i c, j k c l m Value SET [NATIONAL 18] variable octets Type M M Reference 6.3.2.2 6.3.2.2 Notes
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
Notes: a. b. c. d. e. f. g. Include if action to be performed is not implied through presence of other parameters. Include if one or more tones or announcements are to be applied to the MS. Include if applicable. Include to indicate charge information for the call. Include if available for recording purposes (see DMH). Include if redirection may apply. Include for recording purposes if a WIN service was invoked.
46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
124
MAP Operations
X.S0010-A
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
h. i. j. k. l. m. n.
Include to request an override of the Serving MSCs default No Answer Time value. Include if modification to normal feature processing is required for the call in progress. This parameter may only be included if the AnnouncementList parameter is present. Include if a PSTNTermination parameter or an IntersystemTermination parameter is included within the TerminationList parameter. Include if call routing is required. Include to indicate WIN triggers for call redirection. Include if access is denied. If included, no other optional parameters shall be included (with the exception of AnnouncementList parameter).
MAP Operations
125
X.S0010-A
6.4.2.ag
ONoAnswer
(See IS-848, page 5-27)
1 2 3 4
The omitted portion of this section is retained without modification. The ONoAnswer operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
ONoAnswer RETURN RESULT Parameters Field Identifier Length Contents AccessDeniedReason ActionCode AnnouncementList CarrierDigits DMH_AccountCodeDigits DMH_AlternateBillingDigits DMH_BillingDigits DMH_ChargeInformation DMH_RedirectionIndicator DMH_ServiceID NoAnswerTime OneTimeFeatureIndicator PreferredLanguageIndicator RedirectingNumberDigits RoutingDigits TerminationList TriggerAddressList O O O O O O O O O O O O O O O O O 6.5.2.1 6.5.2.2 6.5.2.6 6.5.2.28 6.5.2.59 6.5.2.60 6.5.2.61 6.5.2.eo 6.5.2.62 6.5.2.ei 6.5.2.87 6.5.2.88 6.5.2.96 6.5.2.107 6.5.2.114 6.5.2.156 6.5.2.de n a b c e e e d, e e, f g h i c, j k c l m Value SET [NATIONAL 18] variable octets Type M M Reference 6.3.2.2 6.3.2.2 Notes
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
Notes: a. b. c. d. e. f. g. h. Include if action to be performed is not implied through presence of other parameters. Include if one or more tones or announcements are to be applied to the MS. Include if applicable. Include to indicate charge information for the call. Include if available for recording purposes (see DMH). Include if redirection may apply. Include for recording purposes if a WIN service was invoked. Include to request an override of the Serving MSCs default No Answer Time value.
45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
126
MAP Operations
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
i. j. k. l. m. n.
Include if modification to normal feature processing is required for the call in progress. This parameter may only be included if the AnnouncementList parameter is present. Include if a PSTNTermination parameter or an IntersystemTermination parameter is included within the TerminationList parameter. Include if call routing is required. Include to indicate WIN triggers for call redirection. Include if access is denied. If included, no other optional parameters shall be included (with the exception of AnnouncementList parameter).
MAP Operations
127
X.S0010-A
6.4.2.ax
ShortMessageAnalyzed
(New for TIA/EIA-41.5, Section 6.4.2)
1 2 3 4 5 6 7
The ShortMessageAnalyzed (SM_ANLYZD) operation is used by the MC to provide notification to a service logic network element (e.g., SCP, SN) that an SMS event criteria has been satisfied. Service logic may then invoke a service or services. The following table lists the possible combinations of invoking and responding NEs. Table 11 NE Combinations for SM_ANLYZD
INVOKING NE Case 1 Case 2 MC MC RESPONDING NE SCP SN
8 9 10 11 12 13 14 15 16 17
The ShortMessageAnalyzed operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows:
ShortMessageAnalyzed INVOKE Parameters Field Identifier Length Contents SMS_BearerLength SMS_BillingID SMS_Event SMS_TeleserviceIdentifier ElectronicSerialNumber MobileDirectoryNumber MSID SMS_ChargeIndicator SMS_DestinationAddress SMS_PendingMessageCount SMS_OriginalDestinationAddress SMS_OriginalDestinationSubaddress SMS_OriginalOriginatingAddress SMS_OriginalOriginatingSubaddress SMS_OriginatingAddress TimeDateOffset TimeOfDay M M M M O O O O O O O O O O O O O 6.5.2.hn 6.5.2.ho 6.5.2.hp 6.5.2.137 6.5.2.63 6.5.2.80 6.5.2.bv 6.5.2.126 6.5.2.127 6.5.2.hr 6.5.2.131 6.5.2.132 6.5.2.133 6.5.2.134 6.5.2.135 6.5.2.dd 6.5.2.em a b c d e, f e, f, g e, f, g h i j k l m l n o p Value SET [NATIONAL 18] variable octets Type M M Timer: SMAT Reference 6.3.2.1 6.3.2.1 Notes
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
Notes: a. Include to indicate the length of the original SMS_BearerData received in the SMSDeliveryPointToPoint INVOKE.
55 56 57 58 59 60
128
MAP Operations
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
b. c. d. e. f. g. h. i. j. k. l. m. n. o. p.
Include to indicate the Message Center generated Billing Identifier for this short message. Include to indicate the SMS event encountered. Include to indicate the teleservice for which the SMS message applies. Include if available. Include to identify the MS. At least one of these parameters must be present. Include if received to specify the charging options for an SMS message. Include to identify the network address of the destination only if different than the SMS_OriginalDestinationAddress. Include if available to indicate the number of SMS messages in the MC pending delivery for and from this MS-based SME. Include to identify the network address of the final destination SME. Include if applicable. Include to identify the network address of the initial originating SME. Include to identify the network address of the originator only if different than the SMS_OriginalOriginatingAddress. Include to indicate the time offset of Local Civil Time with respect to Coordinated Universal Time (UTC). Include to indicate the time of day in UTC.
MAP Operations
129
X.S0010-A
The ShortMessageAnalyzed operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
ShortMessageAnalyzed RETURN RESULT Parameters Field Identifier Length Contents DMH_ServiceID SMS_BearerData SMS_CauseCode SMS_EventNotification O O O O 6.5.2.ei 6.5.2.124 6.5.2.125 6.5.2.hq a b c d Value SET [NATIONAL 18] variable octets Type M M Reference 6.3.2.2 6.3.2.2 Notes
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Notes: a. b. c. d. Include for recording purposes if a WIN service was invoked. Include to provide information for the subscriber, if applicable. Include to specify the treatment if continued processing of the short message delivery is not applicable. Include to specify subsequent SMS events for this short message that require service logic notification.
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
130
MAP Operations
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
6.5
6.5.1
6.5.1.1
Map Parameters
General
Parameter Identifiers
Table 12 TIA/EIA-41 MAP Parameter Identifiers

Parameter Identifier Name H ReservedResumePIC 1 1 0 SMS_BearerLength 1 1 0 SMS_BillingID 1 1 0 SMS_Event 1 1 0 SMS_EventNotification 1 1 0 SMS_PendingMessageCount 1 1 0 TriggerCriteria 1 1 0 0 0 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Parameter Identifier Code G F E D C B A 1 0 0 1 1 1 1 0 0 1 0 1 1 0 1 1 0 0 1 0 0 1 0 0 1 0 0 1 1 1 1 1 1 1 1 0 1 1 0 1 1 1 1 1 1 1 0 0 1 0 1 1 1 0 1 1 1 1 1 0 1 1 1 6.5.2.hs 6.5.2.hr 6.5.2.hq 6.5.2.hp 6.5.2.ho 6.5.2.hn 6.5.2.cu Reference
1 0 0 1 0 1
1 0 1 1 0 1 1 0 0 1 0 0 1 0 0 1 0 0 1 0 1 1 0 1 1 0 0 1 0 0 1 0 0 1 0 0
Map Parameters
131
X.S0010-A
6.5.2
Parameter Definitions
1 2 3 4
6.5.2.2
ActionCode
(See IS-826, page 5-51)
5 6 7
The ActionCode (ACTCODE) parameter specifies the nature of the action (e.g., disconnect the call) to be performed by the designated functional entity.
Field Identifier Length Contents H G F E Action D C B A octet 1 Notes Value ActionCode IMPLICIT OCTET STRING variable octets Type M M Reference 6.5.1.2 6.5.1.1 Notes
8 9 10 11 12 13 14 15 16 17 18 19 20
21 22
Notes: a. Action
Decimal Value 24 Present display text to calling MS. Send the display text received in the DisplayText parameter to the calling MS. Meaning
23
Ignore extra octets, if received. Send only defined (or significant) octets.
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
132
Map Parameters
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
6.5.2.97
Profile
(See TIA/EIA-41.5-D, page 5-234) (See IS-737, page 66)
The Profile is a collection of the subscribers calling profile information. This information is a list of optional parameters. The Profile macro has been defined solely for editorial convenience, and does not affect the encoding in any way.
PROFILE Type Contents CDMAServiceOptionList TDMADataFeaturesIndicator O O 6.5.2.g 6.5.2.az xx yy Reference Notes
Notes:
xx. yy.
Include to indicate preferred CDMA service options in descending order of preference. Include to indicate allowed TDMA data services.
Map Parameters
133
X.S0010-A
6.5.2.125
SMS_CauseCode
(See TIA/EIA-41, page 5-262) (See IS-725-A, page 111)
1 2 3 4
The SMS_CauseCode (SMSCAUSE) parameter indicates a reason for not delivering an SMS or OTASP message or indicates certain conditions at the Serving MSC for use during OTASP.
Field Identifier Length Contents H G F E D C B A octet 1 Notes a b Value SMS_CauseCode IMPLICIT OCTET STRING variable octets Type M M Reference 6.5.1.2 6.5.1.1 Notes
5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
SMS Cause Code
Notes: a. b. Only the SMS_CauseCode SMS delivery postponed is used to indicate that an SMS message is pending delivery and that notification shall be provided. Ignore extra octets, if received. Send only defined (or significant) octets.
21 22 23 24 25 26 27
SMS Cause Code (octet 1)

Decimal Value 0 Meaning Address vacant. SMS Destination Address is valid but not currently allocated to an SMS terminal. The MIN MSID associated with a valid destination address is not known to its HLR. Address translation failure. The SMS Destination Address is invalid (e.g., address is not a recognized address type, address is not for a known or possible SMS functional entity, the MSID associated with a destination MS address does not correspond to its HLR, the ESN associated with a destination MS does not match the expected value, the SMS_DestinationAddress, SMS_OriginalDestinationAddress, destination MSID, or original destination subaddress does not match the address of a destination SME). For CDMA OTASP, the TRN, the Activation_MIN, or the ESN is currently not allocated to an OTASP call. Network resource shortage. Network transmission failed due to lack of a network resource shortage or link capacity. Network failure. A network node failed, a link failed or a required operation failed. Invalid Teleservice ID. The SMS_TeleserviceIdentifier is not known, is not supported or is not authorized by an addressed functional entity. Other network problem. Unsupported network interface. The intersystem network interface required for the delivery of the received message is not supported. Reserved. Treat the same as value 5, Other network problem. No page response. The addressed MS-based SME is known, but it does not respond to a page. SMS Notification is not pending.
28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51
2 3 4 5 6 through 31 32
52 53 54 55 56 57 58 59 60
134
Map Parameters
X.S0010-A
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

Decimal Value Meaning Destination busy. The destination MS-based SME is SMS capable, but is currently engaged in a call, a service or a call mode that precludes the use of SMS or the destination SME is congested. This value shall only be used between the MSC and the MC when allowed by bilateral agreement. SMS Notification is not pending. No acknowledgment. The destination SME does not acknowledge receipt of the SMS delivery (e.g., SMS or an OTASP Data message). This value may be used when Terminal busy and No page response are not appropriate. SMS Notification is not pending. Destination resource shortage. A required terminal resource (e.g., memory) is not available to process this message. SMS notification is not pending. SMS delivery postponed. Delivery is not currently possible (e.g., No page response, Destination busy, No acknowledgment, Destination out of service, Other terminal problem), but SMS notification is pending. Destination out of service. The addressed destination is out of service for an extended period of time (e.g., MS sleep, inactive, power off). SMS notification is not pending. Destination no longer at this address. The MS-based SME is no longer at the temporary SMS routing address. The message sender should not re-use the temporary SMS routing address. SMS notification is not pending. Other terminal problem. A terminal problem other than described above. SMS notification is not pending. Reserved. Treat the same as value 39, Other terminal problem. Reserved. Treat the same as value 36, SMS delivery postponed. Radio interface shortage. There is no channel available or there is radio congestion at this time. Radio interface incompatibility. The MS for an MS-based SME is operating in a mode that does not support SMS at this time. This cause code may also be used to indicate that the air interface does not support OTASP Data Message delivery. Other radio interface problem. A radio interface problem to an MSbased SME other than described above Unsupported Base Station Capability. Base Station does not support this service (e.g., SMS, OTASP, OTAPA). Reserved. Treat the same as value 66, Other radio interface problem. Encoding problem. The size of a parameter or field is not what is expected. Service origination denied. The originating MSID is not recognized, the originating address is not allowed for the originating MS, the ESN does not match the originating MSID, the origination is not authorized, the originating address is not recognized. Service termination denied. The destination is not authorized to receive this service message, the MC refused the message, the destination SME refused the message, the destination is not authorized for a required supplementary service, etc. This cause code may also be used to indicate that an MS rejected an OTASP Data Message.
33
34
35
36
37
38
39 through 47 through 63 64
65
66 67 through 95 96
97
98
Map Parameters
135
X.S0010-A

Decimal Value 99 Meaning Supplementary service not supported. The originating supplementary service is not known or supported, the sender is not authorized for an originating supplementary service, etc. Service not supported. The service is not supported by an addressed network functional entity. Reserved. Treat the same as value 107, Other general problems. Missing expected parameter. An optional parameter that is required for a particular function. Missing mandatory parameter. A parameter is missing that is mandatory for a particular message. Unrecognized parameter value. A known parameter has a unknown or unsupported value. Unexpected parameter value. A known parameter has a known, but unexpected value. User Data size error. The User Data size is too large for access technology, transport network, or call mode, etc. The User Data size is not what is expected for the indicated teleservice Other general problems. Session not active. An OTASP or OTAPA session does not currently exist for the MS. The session may have been terminated (e.g., due to loss of the associated traffic channel). Service denied. Short message service denied by service logic. Reserved. Treat the same as value 107, Other general problems. Reserved for TIA/EIA-41 protocol extension. If unknown, treat the same as value 107, Other general problems.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
100 101 102 103 104 105
17 18 19 20 21 22 23 24
106 107 108 109 through 223 through 255
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
136
Map Parameters
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
6.5.2.j
TDMAServiceCode
(See IS-737, page 78)
The TDMAServiceCode (TDMASC) parameter is used to indicate the acceptable or current mode of a call in accordance with TDMA. TDMASC is an extension to the TDMACallMode parameter.
Field Identifier Length Contents H G F E D C B A octet 1 Data Rate 2 b a Notes Value TDMAServiceCode IMPLICIT OCTET STRING variable octets Type M M Reference 6.5.1.2 6.5.1.1 Notes
Service Code Reserved
Notes: a. b. Ignore extra octets, if received. Send only defined (or significant) octets. Reserved bits shall be ignored on receipt and set to zero on sending.
Service Code (octet 1)

Decimal Value 0 1 2 3 4 5 6 7 through 255 Analog Speech Only. Digital Speech Only. Analog or Digital Speech, Analog Preferred. Analog or Digital Speech, Digital Preferred. Asynchronous Data. G3 Fax. Not Used (Service Rejected). STU-III. Reserved. Treat reserved values the same as value 0, Analog Speech Only. Meaning
Data Rate (octet 2, bits A-D)

Decimal Value 0 1 2 3 4 through 15 Not used. Half-Rate Digital Traffic Channel. Full-Rate Digital Traffic Channel. Double Full-Rate Digital Traffic Channel. Triple Full-Rate Digital Traffic Channel. Reserved. If unknown, treat the same as value 2, Full-Rate Digital Traffic Channel. Meaning
Map Parameters
137
X.S0010-A
6.5.2.cu
ResumePIC
(See IS-771, page 5-89) The ResumePIC (RESUMEPIC) parameter identifies the point in call (PIC) at which call processing should resume.
Field Identifier Length Contents H G F E D C B A octet 1 Notes a Value ResumePIC IMPLICIT Unsigned Enumerated one octet Type M M Reference 6.5.1.2 6.5.1.1 Notes
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Point In Call
Notes: a. Refer to TIA/EIA-41.7.
17 18 19
Point In Call (octet 1) Decimal Value 0 1 2 3 4 5 6 8 9 10 11 through 31 32 33 34 35 36 37 38 39 through 223 through 255 Not used. Continue Call Processing. Collect_Information PIC. Analyze_Information PIC. Select_Route PIC. Authorize_Origination_Attempt PIC. Authorize_Call_Setup PIC. O_Alerting PIC. O_Active PIC. O_Suspended PIC. O_Null PIC. Reserved. Treat the same as value 1, Not used. Select_Facility PIC. Present_Call PIC. Authorize_Termination_Attempt PIC. T_Alerting PIC. T_Active PIC. Present_Call PIC. T_Suspended PIC. T_Null PIC. Reserved. If unknown, ignore when received. Reserved for TIA/EIA-41 protocol extension. If unknown, ignore when received. Meaning
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
138
Map Parameters
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
6.5.2.dg
TriggerList
(See IS-771, page 5-104)
The TriggerList (TRIGLIST) parameter provides an address and one or more triggers associated with that address.
Field Identifier Length Contents DestinationAddress WIN_TriggerList TriggerCriteria M M O 6.5.2.ck 6.5.2.dk 6.5.2.hs b a TriggerList IMPLICIT SET variable octets Value Type M M Reference 6.5.1.2 6.5.1.1 Notes
Notes: a. b. This form of address is SS7 specific. Include to specify additional trigger criteria for the associated list of WIN triggers.
Map Parameters
139
X.S0010-A
6.5.2.dj
WINOperationsCapability
(See IS-848, page 5-46)
1 2 3 4 5 6
The WINOperationsCapability (WINOPCAP) parameter is used to specify the WIN operations and capabilities supported by the sending network element.
Field Identifier Length Contents H G F E D CSD C POS B A octet 1 2 Notes a b Value WINOperationsCapability IMPLICIT OCTET STRING variable octets Type M M Reference 6.5.1.2 6.5.1.1 Notes
7 8 9 10 11 12 13 14 15 16 17 18
Reserved
CCDIR CONN
Notes: a. b. Reserved bits shall be ignored on receipt and set to zero on sending. Ignore extra octets, if received. Send only defined (or significant) octets.
19 20 21 22 23 24
Connect Resource (CONN) (octet 1, bit A)

Decimal Value 0 Meaning Sender is not capable of supporting the ConnectResource, DisconnectResource, ConnectionFailureReport and ResetTimer (SSFT timer) operations. Sender is capable of supporting the ConnectResource, DisconnectResource, ConnectionFailureReport and ResetTimer (SSFT timer) operations.
25 26 27 28 29 30 31 32 33 34
CallControlDirective (CCDIR) (octet 1, bit B)

Decimal Value 0 1 Meaning Sender is not capable of supporting the CallControlDirective operation. Sender is capable of supporting the CallControlDirective operation.
35 36 37 38 39 40 41 42
PositionRequest (POS) (octet 1, bit C)

Decimal Value 0 1 Meaning Sender is not capable of supporting the PositionRequest operation. Sender is capable of supporting the PositionRequest operation.
43 44 45 46 47
Circuit-Switched Data (CSD) (octet 1, bit D)

Decimal Value 0 1 Meaning Sender is not capable of supporting WIN trigger-based circuit-switched data services. Sender is capable of supporting WIN trigger-based circuit-switched data services.
48 49 50 51 52 53 54 55 56 57 58 59 60
140
Map Parameters
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
6.5.2.hn
SMS_BearerLength
The SMS_BearerLength (SMS_BRLEN) parameter specifies the length of the SMS Bearer Data.
Field Identifier Length Contents H MSB G F E D C B A octet 1 LSB 2 Notes Value SMS_BearerLength IMPLICIT OCTET STRING two octets Type M M Reference 6.5.1.2 6.5.1.1 Notes
SMS Bearer Length
Map Parameters
141
X.S0010-A
6.5.2.ho
SMS_BillingID
1 2 3 4 5 6 7
The SMS_BillingID (SMS_BILLID) parameter is assigned by the subscribers Home MC when a short message is received for PPC SMS. The SMS_BillingID is used to correlate operations and events related to a specific short message.
Field Identifier Length Contents H MSB G F E D C B A octet 1 LSB 2 3 4 ID Number LSB 5 6 c Notes a b Value SMS_BillingID IMPLICIT OCTET STRING variable octets Type M M Reference 6.5.1.2 6.5.1.1 Notes
8 9 10 11 12 13 14 15 16 17 18 19 20
MarketID MC Number
MSB
21 22 23 24
25 26
Notes: a. b. c. d. Refer to the MSCID parameter (see 6.5.2.82) for the definition of this field. MC number represents a particular MC associated with a common MarketID. ID Number is a unique number assigned by the MC identified in the MarketID and MC Number fields. Ignore extra octets, if received. Send only defined (or significant) octets.
27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
142
Map Parameters
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
6.5.2.hp
SMS_Event
The SMS_Event (SMS_EVENT) parameter identifies an individual SMS chargeable event.

Field Identifier Length Contents H G F E D C B A octet 1 Notes Value SMS_Event IMPLICIT Unsigned Enumerated 1 octet Type M M Reference 6.5.1.2 6.5.1.1 Notes
SMS Event
SMS Event (octet 1)

Decimal Value 0 1 2 3 4 5 through 128 129 130 131 132 133 through 223 224 through 255 Unspecified. MS-originated short message accepted by network. MS-originated short message delivery attempt towards destination. Successful MS-originated short message delivery towards destination. Unsuccessful MS-originated short message delivery towards destination. MS-originated short message purged by MC. Reserved. Treat a reserved value the same as value 0, Unspecified. MS-terminated short message accepted by network. MS-terminated short message delivery attempt to MS-Based SME. Successful MS-terminated short message delivery to MS-Based SME. Unsuccessful MS-terminated short message delivery to MSBased SME. MS-terminated short message purged by MC. Reserved. Treat a reserved value the same as value 0, Unspecified. Reserved for TIA/EIA-41 protocol extension. If unknown, treat the same as value 0, Unspecified. Meaning
Map Parameters
143
X.S0010-A
6.5.2.hq
SMS_EventNotification
1 2 3 4 5 6 7
The SMS_EventNotification (SMS_EVENTNOT) parameter is used by an SCF to request notification of WIN SMS events at an MC for a short message. This request supersedes any previously requested notification of SMS events for the short message.
Field Identifier Length Contents H G Reserved Reserved F E MO-P MT-P D C B A MO-N MT-N octet 1 2 Notes a a b Value SMS_EventNotification IMPLICIT OCTET STRING variable octets Type M M Reference 6.5.1.2 6.5.1.1 Notes
8 9 10 11 12 13 14 15 16 17 18 19 20
MO-UD MO-SD MO-DA MT-UD MT-SD MT-DA
21 22 23 24 25 26
MS-Originated Short Message Network (MO-N) (octet 1, bit A)

Decimal Value 0 1 Meaning No notification requested for MS-originated short message accepted by network event. Notification is requested for MS-originated short message accepted by network event.
27 28 29 30 31 32 33 34 35 36 37 38
MS-Originated Short Message Delivery Attempt (MO-DA) (octet 1, bit B)

Decimal Value 0 1 Meaning No notification requested for MS-originated short message delivery attempt towards destination event. Notification is requested for MS-originated short message delivery attempt towards destination event.
39 40 41 42 43
Successful MS-Originated Short Message Delivery (MO-SD) (octet 1, bit C)

Decimal Value 0 1 Meaning No notification requested for Successful MS-originated short message delivery towards destination event. Notification is requested for Successful MS-originated short message delivery towards destination event.
44 45 46 47 48 49 50 51
Unsuccessful MS-Originated Short Message Delivery (MO-UD) (octet 1, bit D)

Decimal Value 0 1 Meaning No notification requested for Unsuccessful MS-originated short message delivery towards destination event. Notification is requested for Unsuccessful MS-originated short message delivery towards destination event.
52 53 54 55 56 57 58 59 60
144
Map Parameters
X.S0010-A
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
MS-Originated Short Message Purged (MO-P) (octet 1, bit E)

Decimal Value 0 1 Meaning No notification requested for MS-originated short message purged by MC event. Notification is requested for MS-originated short message purged by MC event.
MS-Terminated Short Message Network (MT-N) (octet 2, bit A)

Decimal Value 0 1 Meaning No notification requested for MS-terminated short message accepted by network event. Notification is requested for MS-terminated short message accepted by network event.
MS-Terminated Short Message Delivery Attempt (MT-DA) (octet 2, bit B)

Decimal Value 0 1 Meaning No notification requested for MS-terminated short message delivery attempt to MS-based SME event. Notification is requested for MS-terminated short message delivery attempt to MS-based SME event.
Successful MS-Terminated Short Message Delivery (MT-SD) (octet 2, bit C)

Decimal Value 0 1 Meaning No notification requested for Successful MS-terminated short message delivery to MS-based SME event. Notification is requested for Successful MS-terminated short message delivery to MS-based SME event.
Unsuccessful MS-Terminated Short Message Delivery (MT-UD) (octet 2, bit D)

Decimal Value 0 1 Meaning No notification requested for Unsuccessful MS-terminated short message delivery to MS-based SME event. Notification is requested for Unsuccessful MS-terminated short message delivery to MS-based SME event.
MS-Terminated Short Message Purged (MT-P) (octet 2, bit E)

Decimal Value 0 1 Meaning No notification requested for MS-terminated short message purged by MC event. Notification is requested for MS-terminated short message purged by MC event.
Map Parameters
145
X.S0010-A
6.5.2.hr
SMS_PendingMessageCount
1 2 3 4 5 6 7 8
The SMS_PendingMessageCount (SMS_PMCNT) parameter is used to indicate the number of SMS messages pending delivery. The number of messages pending does not include SMS messages generated by the MC or by service logic, nor does the pending message count include free of charge SMS messages1.
Field Identifier Length Contents H MSB G F E D C B A octet 1 LSB 2 3 LSB 4 Notes a Value ActionCode IMPLICIT OCTET STRING four octets Type M M Reference 6.5.1.2 6.5.1.1 Notes
9 10 11 12 13 14 15 16 17
MO-SMS Pending Message Count
18 19 20
MSB
MT-SMS Pending Message Count
21 22 23
Notes: a. b. A value of 0 indicates no pending MS-originated short messages for the MS. A value of 0 indicates no pending MS-terminated short messages for the MS.
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
1. The ChargeIndicator parameter is used to determine that an SMS message is free of charge.
59 60
146
Map Parameters
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
6.5.2.hs
TriggerCriteria
The TriggerCriteria parameter is used to identify the criteria for a WIN trigger list.
Field Identifier Length Contents H G F E Reserved D C B A CSD octet 1 Notes a b Value TriggerCriteria IMPLICIT OCTET STRING variable octets Type M M Reference 6.5.1.2 6.5.1.1 Notes
Circuit-Switched Data (CSD) (octet 1, bit A)

Decimal Value 0 1 Meaning Trigger list is not applicable for circuit-switched data calls. Trigger list is applicable for circuit-switched data calls.
Map Parameters
147
X.S0010-A
ANNEX A: ASN.1 NOTATION FOR WIN PARAMETERS

(See IS-771, page 5-111)
1 2 3 4 5 6 7 8
This annex is informative and is not considered part of this Interim Standard. This annex provides the ASN.1 notation for the new parameters defined in this Interim Standard. Table A-1
Parameter
ResumePIC
9 10 11
ASN.1 Notation for WIN Parameters

Acronym
RESUMEPIC
12 13 14 15 16 17
ASN.1 Notation
ResumePIC::= IMPLICIT UNSIGNED ENUMERATED { Continue_Call_Processing (1), Collect_Information PIC (2), Analyze_Information PIC (3), Select_Route PIC (4), Select_Facility PIC (32), Present_Call PIC (33), ...}
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
148
ANNEX A: ASN.1 NOTATION FOR WIN PARAMETERS
X.S0010-A
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

This section provides additions and modifications to IS-826 Chapter 6, Modifications to TIA/EIA-41.6-D Signaling Procedures, required to support circuit-switched data and short message services.
4
4.14
4.14.1
INTERSYSTEM PROCEDURES
Feature Request
MSC Detecting Feature Request
(see IS-848, page 6-20)
When performing digit analysis of the dialed digits received from the MS, the MSC detects that the dialed digits are a feature control access. It shall perform the following: 1 2 3 4 5 6 6-1 7 8 9 Include the BillingID parameter set to identify the current call for billing and redirection purposes. Include the Digits (Dialed) parameter set to the digits received from the MS. Include the ElectronicSerialNumber parameter set to identify the MS. Include the MobileIdentificationNumber parameter set to identify the MS. Include the MSCID parameter set to the identity of the MSC. IF any indicator is set in the OneTimeFeatureIndicator parameter: Include the OneTimeFeatureIndicator parameter. ENDIF. Include SenderIdentificationNumber parameter set to the identification number of the MSC. Include TransactionCapability parameter set appropriately. Include the ConferenceCallingIndicator parameter set to the number of conferees currently in the call.
10 IF the subscriber is involved in a conference call: 10-1
11 ENDIF. 12 Send a FeatureRequest INVOKE to the HLR associated with the MS. 13 Start the Feature Request Response Timer (FRRT). 14 WAIT for Feature Request response: 15 WHEN a RETURN RESULT is received: 15-1 15-2 15-2-1 15-2-1-1 15-2-1-1-1 Stop timer (FRRT). IF the message can be processed: IF the MS is still connected: IF the AnnouncementList parameter is received: IF the PreferredLanguageIndicator parameter is received:
Intersystem Procedures
149
X.S0010-A
15-2-1-1-1-1 15-2-1-1-2 15-2-1-1-3 15-2-1-2 15-2-1-2-1 15-2-1-3 15-2-1-3-1 15-2-1-4 15-2-1-5 15-2-1-5-1 15-2-1-6 15-2-1-7 15-2-1-7-1 15-2-1-7-1-1 15-2-1-7-2 15-2-1-7-2-1 15-2-1-7-2-2 15-2-1-7-3 15-2-1-8 15-2-1-9 15-2-1-9-1 15-2-1-10 15-2-1-11 15-2-1-11-1 15-2-1-12 15-2-1-13 15-2-1-13-1 15-2-1-13-1-1 15-2-1-13-1-1-1 15-2-1-13-1-2 15-2-1-13-1-2-1 15-2-1-13-1-3 15-2-1-13-2 15-2-1-14 ENDIF.
Use the received Preferred Language value as the subscriber's preferred language for playing this announcement list. ENDIF. Execute the Play All Announcements in the AnnouncementList task (see 3.2.5). ELSEIF the FeatureResult parameter indicates Successful operation: Provide a successful indication to the MS. ELSE: Provide an unsuccessful indication to the MS. ENDIF. IF the OneTimeFeatureIndicator parameter is received: Store the received OneTimeFeatureIndicator parameter. ENDIF. IF the TriggerAddressList parameter is received: IF the call is being redirected: Arm the triggers indicated by the TriggerAddressList parameter for the redirected call. ELSE: Disarm any previously armed subscribed WIN triggers for the remainder of the call in progress. Arm the triggers indicated by the TriggerAddressList parameter for the remainder of the call in progress. ENDIF. ENDIF. IF the ConferenceCallingIndicator parameter is received: Execute the MSC CC Invocation task (see 5.10.3). ENDIF. IF an ActionCode parameter is received: Execute the MSC ActionCode Processing task (see 3.2.9) ENDIF. IF the MS is in a state capable of routing a call (e.g., after dialing a feature code from an idle state or a call hold state). IF the TerminationList parameter is received: IF WIN triggers remain to be processed at Collected_Information or the Analyzed_Information DP: Return to the calling task. ELSE: Execute the MSC Routing Points Of Return task (see 3.2.6). ENDIF. ENDIF. the
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
150
Feature Request
X.S0010-A
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
15-2-1-15 15-2-1-15-1 15-2-1-15-2 15-2-1-15-2-1 15-2-1-15-3 15-2-1-15-4 15-2-1-15-4-1 15-2-1-15-5 15-2-1-16 15-2-1-16-1 15-2-1-17 15-2-1-18
15-2-1-19 15-2-1-19-1 15-2-1-19-1-1 15-2-1-19-2 15-2-1-19-2-1 15-2-1-19-3 15-2-1-19-3-1 15-2-1-19-3-2 15-2-1-19-4 15-2-1-20 15-2-1-20-1 15-2-1-21
IF Digits (Dialed) parameter is received: Set MS dialed digits to the received Digits (Dialed) parameter value. IF the type of digits is unknown: Process the dialed number locally to set the PointOfReturn. ENDIF. IF WIN triggers remain to be processed at Collected_Information or the Analyzed_Information DP: Return to the calling task. ENDIF. ELSE: Use Digits (Dialed) parameter included in the FeatureRequest INVOKE as MS dialed digits. ENDIF. GOTO AuthorizedSubscriberOrigination (see 3.2.3).
IF the ResumePIC parameter is received: IF the value of the ResumePIC parameter is Continue Call Processing: Return to the calling task. ELSEIF the value of the ResumePIC parameter is a valid transition: GOTO the entry point indicated by the ResumePIC parameter. ELSE: Execute Local Recovery Procedures task (see 3.5.1). Exit this task. ENDIF. ELSE: GOTO AuthorizedSubscriberOrigination (see 3.2.3). ENDIF.
the
15-2-2 15-3 15-3-1 15-3-2 15-3-2-0-1 15-3-3 15-4 16-1 16-2 16-3 16-4 17-1 17-2 17-3
ENDIF. ELSE (the message cannot be processed): Execute Local Recovery Procedures task (see 3.5.1). IF the MS is still connected: Provide an unsuccessful indication to the MS. ENDIF. ENDIF. Stop timer (FRRT). Execute the MSC Remote User Interaction task (see 4.39.2). Start the Feature Request Response Timer (FRRT). Remain in this state. Stop timer (FRRT). Execute Local Recovery Procedures task (see 3.5.1). IF the MS is still connected:
16 WHEN a RemoteUserInteractionDirective INVOKE is received:
17 WHEN a RETURN ERROR or REJECT is received:
Feature Request
151
X.S0010-A
17-3-1 17-4 18-1 19-1 19-2 19-2-1 19-3
Provide an unsuccessful indication to the MS. ENDIF. Remain in this state (to handle possible call abandons). Execute Local Recovery Procedures task (see 3.5.1). IF the MS is still connected: Provide an unsuccessful indication to the MS. ENDIF.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
18 WHEN the MS disconnects: 19 WHEN timer (FRRT) expires:
20 ENDWAIT. 21 Exit this task.
16 17 18
4.25
4.25.2
InterSystem Page
MSC Receiving InterSystemPage INVOKE
(See TIA/EIA-41.6-D, page 6-177)
19 20 21 22 23 24 25 26 27 28
When an MSC receives an InterSystemPage INVOKE, it shall perform the following: 1 1-1 1-1-1 1-2 1-3 1-3-1 1-3-2 1-3-3 1-4 1-4-1 1-4-2 1-4-3 1-5 1-5-1 1-5-2 1-6 1-6-1 1-7 IF the received message can be processed: IF the MSC is currently executing the MSC Detecting an Unsolicited Page Response procedure: Exit this task. ENDIF. IF the MS is currently in a call or service process: Include AccessDeniedReason parameter set to Busy1. Send a RETURN RESULT to the requesting MSC. Exit this task. ELSEIF the indicated Service Type is not supported: Include the AccessDeniedReason parameter set to Service Rejected by System. Send a RETURN RESULT to the requesting MSC. Exit this task. ELSEIF paging should be performed: Determine the area to page base on the receive LocationAreaID parameter.2 Page the mobile. ELSE: Only listen for a page response. ENDIF.
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
1. Handling of Call Waiting in this situation is for further study. 2. The paging area, identied by the location area ID, is dened per inter-system agreement.
57 58 59 60
152
InterSystem Page
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
1-8 1-9 1-10 1-10-1 1-10-2 1-10-2-1 1-10-2-2 1-10-2-3 1-10-3 1-10-3-1 1-10-3-2 1-10-3-3 1-10-4 1-10-5 1-10-5-1 1-10-6 1-10-7 1-10-8 1-10-8-1 1-10-8-2 1-10-8-3 1-10-9 1-10-9-1 1-10-9-2
Start a page response timer. WAIT for an MS response: WHEN the page response is received: Stop the page response timer. IF the page response (e.g., TDMA Service Code or CDMA Service Option parameters) indicates service rejected by the MS. Include the AccessDeniedReason parameter set to Service Rejected by MS. Send a RETURN RESULT. Exit this task. ELSEIF the system does not support the indicated Service Type (in the area where the MS is located): Include the AccessDeniedReason parameter set to Service Rejected by System. Send a RETURN RESULT. Exit this task. ENDIF IF the Border MSC needs to retrieve the MSs qualification information, optionally: Execute MSC Initiating a Qualification Request task (see 4.33.1). ENDIF. Process the MS presence confirmation procedure.1 IF the MS presence confirmation fails: Include the AccessDeniedReason parameter set to No Page Response. Send a RETURN RESULT. Exit this task. ELSE (the presence confirmation is successful): Execute MSC Initiating an Authentication Request task (see 4.4.1) to authenticate the MS. IF the MS is authentic: IF a TLDN is available: Assign a TLDN to the indicated MS. Assign a billing identifier to the TLDN. Store the Originating MSC ID information and information related to the indicated MS with the assigned TLDN. Include the MSCID parameter set to the identity of the MSC. Include the Digits: (Destination); parameter set to the assigned TLDN. Include the BillingID (Serving) parameter set to the TLDN billing identifier.
1-10-9-2-1 1-10-9-2-1-1 1-10-9-2-1-2 1-10-9-2-1-3 1-10-9-2-1-4 1-10-9-2-1-5 1-10-9-2-1-6
1. MS presence conrmation consists of paging the MS and voice channel assignment with either SAT detection or voice channel audit.
InterSystem Page
153
X.S0010-A
1-10-9-2-1-7 1-10-9-2-1-7-1 1-10-9-2-1-8 1-10-9-2-1-9 1-10-9-2-1-10 1-10-9-2-1-11 1-10-9-2-2 1-10-9-2-2-1 1-10-9-2-2-2 1-10-9-2-2-3 1-10-9-2-3 1-10-9-3 1-10-9-3-1 1-10-9-3-2 1-10-9-4 1-10-10 1-11 1-11-1 1-11-2 1-12 2 2-1 2-2 3 4 ENDIF.
IF the TriggerAddressList parameter was received: Include the WINCapability parameter set to identify the MSCs WIN capability. ENDIF. Send a RETURN RESULT. Execute MSC Initiating MS Registration task (see 4.38.1) to properly register the MS. Execute the Wait for TLDN Call task (see 3.3.2). ELSE (no TLDN is available): Execute Local Recovery Procedures task (see 3.5.1). Include the Error Code parameter set to ResourceShortage. Send a RETURN ERROR. ENDIF. ELSE (MS is not authentic): Execute Local Recovery Procedures task (see 3.5.1). Exit this task. ENDIF.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41
WHEN the page response timer expires: Include the AccessDeniedReason parameter set to No Page Response. Send a RETURN RESULT. ENDWAIT. Execute Local Recovery Procedures task (see 3.5.1). Send a RETURN ERROR with a proper Error Code value (see the following table).
ELSE (the received message cannot be processed):
ENDIF. Exit this task.
4.31
4.31.1
Origination Request
MSC Initiating an Origination Request
(see IS-848, page 6-30)
42 43 44 45 46 47 48 49 50 51 52 53 54 55 56
When the MSC determines that an active origination trigger has been encountered requiring call processing to be suspended while the HLR or another network entity must performs digit analysis (for other than a feature code) or otherwise executes service logic, and that trigger criteria have been met, it shall perform the following: 1 2 3 Include the BillingID (Originating) parameter set to the billing identifier for the call assigned by the current Originating MSC. Include the Digits (Dialed) parameter set to the digits received from the MS. Include the ElectronicSerialNumber parameter set to identify the originating MS.
57 58 59 60
154
Origination Request
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
4 5 6 7 8 8-1 8-2 8-3 8-4 9 9-1 9-2 9-3
Include the MobileIdentificationNumber parameter set to identify the originating MS. Include the MSCID parameter set to the identity of the Originating MSC. Include the TransactionCapability parameter set to identify the current capabilities. Include the WINCapability parameter set to identify the current TriggerCapability and the current WINOperationsCapability. IF the trigger that was encountered was armed by the TriggerAddressList parameter (a WIN trigger was encountered): Include the TriggerType parameter set to identify the trigger that was encountered. Include the OriginationTriggers parameter set to indicate that no trigger was encountered. Include other applicable parameters. Send an OriginationRequest INVOKE to the service logic host address obtained from the TriggerAddressList for the trigger that was encountered. ELSE (the trigger that was encountered was armed by the OriginationTriggers parameter): Include the OriginationTriggers parameter set to identify the triggering event. Include other applicable parameters. Send an OriginationRequest INVOKE to the MS's associated HLR.
10 ENDIF. 11 Start the Origination Request Timer (ORT). 12 WAIT for Origination Request response: 13 WHEN a RETURN RESULT is received: Origination Request RETURN RESULT Treatment: 13-1 13-2 13-2-1 13-2-1-1 13-2-1-1-1 13-2-1-1-1-1 13-2-1-1-2 13-2-1-1-3 13-2-1-2 13-2-1-3 13-2-1-3-1 13-2-1-3-1-1 13-2-1-3-2 13-2-1-3-2-1 Stop timer (ORT), if it is running. IF the message can be processed: IF the incoming call is still connected: IF the AnnouncementList parameter is received: IF the PreferredLanguageIndicator parameter is received: Use the received Preferred Language value as the subscriber's preferred language for playing this announcement list. ENDIF. Execute the Play All Announcements in the AnnouncementList task (see 3.2.5). ENDIF. IF the TriggerAddressList parameter is received: IF the call is being redirected: Arm the triggers indicated by the received TriggerAddressList parameter for the redirected call. ELSE: Disarm any previously armed subscribed WIN triggers for the remainder of the call in progress.
Origination Request
155
X.S0010-A
13-2-1-3-2-2 13-2-1-3-3 13-2-1-4 13-2-1-5 13-2-1-5-1 13-2-1-5-1-1 13-2-1-5-1-2 13-2-1-5-1-3 13-2-1-5-1-4 13-2-1-5-1-5 13-2-1-5-2 13-2-1-5-3 13-2-1-5-3-1 13-2-1-5-3-2 13-2-1-5-4 13-2-1-6 13-2-1-6-1 13-2-1-6-1-1 13-2-1-6-1-2 13-2-1-6-2 13-2-1-7 13-2-1-8 13-2-1-8-1 13-2-1-8-1-1 13-2-1-8-2 13-2-1-8-3 13-2-1-9 13-2-1-10 13-2-1-10-1 13-2-1-11 13-2-1-12 13-2-1-12-1 ENDIF.
Arm the triggers indicated by the received TriggerAddressList parameter for the remainder of the call in progress. ENDIF. ENDIF. IF the AccessDeniedReason parameter is received AND IF it can be acted upon: IF the O_Called_Party_Busy trigger is armed for the subscriber: Execute the MSC Check of Serial Trigger Limit task (see 6.X). Include the TriggerType O_Called_Party_Busy. parameter set to indicate
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Include the FailureCause parameter set according to the received AccessDeniedReason parameter value. Execute the MSC Initiating an OCalledPartyBusy task (see 4.Z.1). Return to the calling task with a successful indication. ENDIF. IF AnnouncementList parameter is not received: Apply the default treatment appropriate for the received AccessDeniedReason value. Return to the calling task. ENDIF. ELSEIF the OriginationRequest INVOKE was sent after detecting a nonWIN trigger: IF neither the TerminationList parameter nor ActionCode parameter nor Digits (Dialed) parameter is received (an error condition?): Execute the Apply Access Denial Treatment task (see 3.4.5). Return to the calling task. ENDIF. IF the TerminationList parameter is received: IF WIN triggers remain to be processed at Collected_Information or the Analyzed_Information DP: Return to the calling task. ENDIF. Execute the MSC Routing Points Of Return task (see 3.2.6). ENDIF. IF the ActionCode parameter is received: Execute the MSC ActionCode Processing task (see 3.2.9). ENDIF. IF the Digits (Dialed) parameter is received. Set the MS dialed digits to the received Digits (Dialed) parameter value. the
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
156
Origination Request
X.S0010-A
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
13-2-1-12-2 13-2-1-12-2-1 13-2-1-12-3 13-2-1-12-4 13-2-1-12-4-1 13-2-1-12-5 13-2-1-13 13-2-1-13-1 13-2-1-14 13-2-1-15
13-2-1-16 13-2-1-16-1 13-2-1-16-1-1 13-2-1-16-2 13-2-1-16-2-1 13-2-1-16-3 13-2-1-16-3-1 13-2-1-16-3-2 13-2-1-16-4 13-2-1-17 13-2-1-17-1 13-2-1-18
IF the type of digits is unknown: Process the dialed number locally to set the PointOfReturn (this may include local feature code processing). ENDIF. IF WIN triggers remain to be processed at Collected_Information or the Analyzed_Information DP: Return to the calling task. ENDIF. ELSE: Use the Digits (Dialed) parameter included OriginationRequest INVOKE as MS dialed digits. ENDIF. GOTO AuthorizedSubscriberOrigination (see 3.2.3).
IF the ResumePIC parameter is received: IF the value of the ResumePIC parameter is Continue Call Processing: Return to the calling task. ELSEIF the value of the ResumePIC parameter is a valid transition: GOTO the entry point indicated by the ResumePIC parameter. ELSE: Execute the Local Recovery Procedures task (see 3.5.1). Exit this task. ENDIF. ELSE: GOTO AuthorizedSubscriberOrigination (see 3.2.3). ENDIF.
the
in
the
13-2-2 13-2-2-1 13-2-2-2 13-2-3 13-3 13-3-1 13-3-2 13-4 14-1 14-2 14-3 14-4 15-1 15-2 15-3 15-4
ELSE (call abandoned): Execute the Local Recovery Procedures task (see 3.5.1). Exit this task. ENDIF. ELSE (the message cannot be processed): Execute Local Recovery Procedures task (see 3.5.1). Exit this task. ENDIF. Stop timer (ORT). Execute the MSC Remote User Interaction task (see 4.39.2). Start the Origination Request Timer (ORT). Remain in this state. Stop the timer (ORT). Execute the MSC Receiving ConnectResource INVOKE task (see 4.B.3). CASE MSC Connect Resource result OF: Disconnect Resource received:
15 WHEN a ConnectResource INVOKE is received:
Origination Request
157
X.S0010-A
15-4-1 15-4-2 15-5 15-5-1 15-6 15-6-1 15-6-2 15-7 15-7-1 15-7-2 15-8 15-8-1 15-8-2 15-9 15-9-1 15-9-2 15-10 15-10-1 15-10-2 15-11 16-1 17-1 17-2 17-3 17-4 18-1 18-2 18-3
Start the timer (ORT). Remain in this state. OriginationRequest RETURN RESULT received: GOTO OriginationRequest RETURN RESULT Treatment. SSFT expiration: Start the timer (ORT). Remain in this state. call abandoned: Execute the Local Recovery Procedures task (see 3.5.1). Exit this task. resource disconnect: Start the timer (ORT). Remain in this state. failure at MSC: Start the timer (ORT). Remain in this state. message error: Start the timer (ORT). Remain in this state. ENDCASE. Remain in this state (to handle possible call abandons). Stop timer (ORT). Execute Local Recovery Procedures task (see 3.5.1). Provide an unsuccessful indication to the MS. Exit this task. Execute Local Recovery Procedures task (see 3.5.1). Provide an unsuccessful indication to the MS. Exit this task.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
16 WHEN the MS disconnects: 17 WHEN a RETURN ERROR or REJECT is received:
18 WHEN timer (ORT) expires:
19 ENDWAIT. 20 Return to the calling task.
48 49 50
4.46
4.46.6
SMS Delivery Point-to-Point

MC Receiving an SMSDeliveryPointToPoint INVOKE
51 52 53 54 55 56 57 58 59 60
Upon receipt of a SMSDeliveryPointToPoint INVOKE, the MC shall do the following:
158
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
1 1-1
IF the message can be processed: IF the SMS_DestinationAddress parameter is received: Set the destination address with SMS_DestinationAddress parameter. the address in the received
1-1-1 1-2 1-2-1 1-3 1-3-1 1-4 1-4-1 1-4-2 1-4-3 1-5 1-6 1-6-1 1-7 1-7-1 1-8 1-9 1-9-1 1-10 1-10-1 1-11 1-11-1 1-11-2 1-11-3 1-12 1-13 1-13-1 1-14 1-14-1 1-15 1-16 1-16-1 1-16-1-1
ELSEIF the MobileIdentificationNumber parameter is received: Set the destination address to the MobileIdentificationNumber. ELSEIF the underlying transport can carry the destination address: Set the destination address with the destination address used by the underlying transport mechanism. ELSE: Include the SMS_CauseCode parameter set to Missing Expected Parameter. Send a RETURN RESULT. Exit this task. ENDIF. IF the SMS_OriginalDestinationAddress parameter is received: Set the original destination address with the address in the received SMS_OriginalDestinationAddress parameter. ELSE: Set the original destination address with the destination address. ENDIF. IF the SMS_OriginatingAddress parameter is received: Set the originating address with received SMS_OriginatingAddress. ELSEIF the underlying transport can carry the originating address: Set the originating address with the originating address used by the underlying transport mechanism. ELSE: Include the SMS_CauseCode parameter set to Missing Expected Parameter. Send a RETURN RESULT. Exit this task. ENDIF. IF the SMS_OriginalOriginatingAddress parameter is received: Set the original originating address with the address in the received SMS_OriginalOriginatingAddress parameter. ELSE: Set the original originating address with the originating address. ENDIF. IF the original originating address is the same as the destination address (originating supplementary services may have been requested): IF the original originating address is a SME homed to this MC, the destination is a legitimate subscriber and the Teleservice is legitimate for the subscriber: IF the SMS event MS-originated short message accepted by network is active for the originating subscriber:
159
X.S0010-A
1-16-1-1-1 1-16-1-1-2 1-16-1-1-2-1 1-16-1-1-2-2 1-16-1-1-2-3 1-16-1-1-3
Execute the MC Initiating a Short Message Analyzed task (see 4.XX.1). IF the request is refused: Include the SMS_CauseCode parameter set to SMS origination denied. Send a RETURN RESULT. Exit this task. ELSEIF the request failed AND network operator policy dictates that short message processing shall not proceed upon operation failure: Include the SMS_CauseCode parameter set to SMS origination denied. Send a RETURN RESULT. Exit this task. ENDIF. ENDIF. Process the message with the indicated teleservice for immediate originating supplementary service processing (e.g., unacceptable bearer data, canned responses for delivery schedules) indicated by the message or the originating subscribers SMS profile information. Send a RETURN RESULT message with parameters loaded according to the teleservice. GOTO the Originating MC Supplementary Services task (see 4.46.7). ELSE: Include the SMS_CauseCode parameter indicating the proper value (e.g., SMS origination denied, Supplementary service not supported). Send a RETURN RESULT. ENDIF.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
1-16-1-1-3-1 1-16-1-1-3-2 1-16-1-1-3-3 1-16-1-1-4 1-16-1-2 1-16-1-3
20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
1-16-1-4 1-16-1-5 1-16-2 1-16-2-1 1-16-2-2 1-16-3 1-17 1-17-1 1-17-1-1 1-17-1-1-1 1-17-1-1-2 1-17-1-1-2-1 1-17-1-1-2-2 1-17-1-1-2-3 1-17-1-1-3
ELSEIF the Original Destination Address is the same as the Destination Address (terminating supplementary services may have been requested): IF the destination address is a SME homed to this MC, the destination is a legitimate subscriber and the Teleservice is legitimate for the subscriber: IF the SMS event MS-terminated short message accepted by network is active for the terminating subscriber: Execute the MC Initiating a Short Message Analyzed task (see 4.XX.1). IF the request is refused: Include the SMS_CauseCode parameter set to SMS termination denied. Send a RETURN RESULT. Exit this task. ELSEIF the request failed AND network operator policy dictates that short message processing shall not proceed upon operation failure:
160
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
1-17-1-1-3-1 1-17-1-1-3-2 1-17-1-1-3-3 1-17-1-1-4 1-17-1-2 1-17-1-3 ENDIF.
Include the SMS_CauseCode parameter set to SMS termination denied. Send a RETURN RESULT. Exit this task. ENDIF. Process the message with the indicated teleservice for immediate terminating supplementary service processing (e.g., unacceptable bearer data, canned responses for on vacation, travel schedules) indicated by the message or the destination subscribers SMS profile information. Send an SMSDeliveryPointToPoint RETURN RESULT message with parameters loaded according to the teleservice. GOTO the Terminating MC Supplementary Services task (see 4.46.8). ELSE: Include the SMS_CauseCode parameter indicating the proper value (e.g., Address translation failure, Address vacant, Invalid Teleservice ID, SMS termination denied, Supplementary service not supported, SMS not supported). Send a RETURN RESULT. ENDIF.
1-17-1-4 1-17-1-5 1-17-2 1-17-2-1
1-17-2-2 1-17-3 1-18 1-18-1 1-18-2 1-19 2 2-1 2-2 3 4
ELSE (the message may have been misrouted to this MC): Include the SMS_CauseCode parameter indicating the proper value. Send a RETURN RESULT. ENDIF. Include the SMS_CauseCode parameter indicating the proper value. Send a RETURN RESULT.
ELSE (the message cannot be processed):
ENDIF. Exit this task.
4.46.7
Originating MC Supplementary Services

When the Originating MC is ready to processes a pending SMSDeliveryPointToPoint INVOKE, the MC shall do the following: 1 Perform any delayed originating supplementary services (e.g., delayed delivery, repeated delivery, distribution list) indicated by the message or the originating subscribers SMS profile information. WHILE originating supplementary service remains incomplete: Schedule the message for delivery and, when ready, continue. IF it becomes necessary for the MC to purge the short message (e.g., systemic memory shortage) AND the SMS event MS-originated short message purged by MC is active for the originating subscriber: Release storage for the message.
2 2-1 2-2
2-2-1
161
X.S0010-A
2-2-2 2-2-3 2-3 2-4 2-4-1 2-4-2 2-4-2-1 2-4-2-2 2-4-3 2-4-3-1 2-4-3-2 2-4-4 2-5 2-6 2-7 2-8 2-9 2-10 2-10-1 2-10-1-1 2-10-2 2-10-3 2-10-3-1 2-10-3-2 2-10-4 2-11 2-11-1 2-11-1-1 2-11-2 2-11-3 2-12 3 4
Execute the MC Initiating a Short Message Analyzed task (see 4.XX.1). Exit this task. ENDIF. IF the SMS event MS-originated short message delivery attempt towards destination is active for the originating subscriber: Execute the MC Initiating a Short Message Analyzed task (see 4.XX.1). IF the request is refused: Release storage for the message. Exit this task. ELSEIF the request failed AND network operator policy dictates that short message processing shall not proceed upon operation failure: Release storage for the message. Exit this task. ENDIF. ENDIF. Set the Destination Address to the Original Destination Address. Include the SMS_BearerData parameter set by the SMS teleservice. Include the SMS_TeleserviceIdentifier parameter set to identify the SMS teleservice. Execute the Initiating SMS Delivery Point-To-Point task (see 4.46.2).1 IF the request is accepted: IF the SMS event Successful MS-originated short message delivery towards destination is active for the originating subscriber: Execute the MC Initiating a Short Message Analyzed task (see 4.XX.1). ENDIF. IF the supplementary service is complete: Release storage for the message. Exit this task. ENDIF. ELSE (the request is denied): IF the SMS event Unsuccessful MS-originated short message delivery towards destination is active for the originating subscriber: Execute the MC Initiating a Short Message Analyzed task (see 4.XX.1). ENDIF. Execute Local Recovery Procedures task (see 3.5.1). ENDIF.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57
ENDWHILE. Exit this task.
1. This message may be internal to a single MC when the originating SME and destination SME are served by the same MC.
58 59 60
162
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
4.46.9
MC Initiating SMS Delivery Point-To-Point to an MS-Based SME

Upon request to send a point-to-point SMS message to an MS-based SME, the MC shall do the following: 1 1-1 2 3 IF notification is already pending for this MIN: GOTO Wait for Notification. ENDIF. IF the address for the indicated MS is not current (as determined by internal algorithms of the MC., e.g., any time between never to until revoked): IF notification of the presence of the MS is required: Optionally, include the SMS_NotificationIndicator parameter set to Notify when available. ELSE: Include the SMS_NotificationIndicator parameter set to Do not notify when available. ENDIF. Execute the MC Initiating SMS Request task (see 4.48.1). IF the request was accepted: Store the temporary routing address and the current time. GOTO Send the message. ELSEIF the request was denied or unavailable: Execute Local Recovery Procedures task (see 3.5.1). Exit this task. ELSE (the request was postponed which can only happen when notification is requested): Queue the request. WAIT for MS to become available to receive a short message: WHEN SMSNotification is passed (see 4.47.3): Remove the request from the queue. Store the temporary routing address and the current time. WHEN the validity of the message expires: IF the SMS event MS-terminated short message purged by MC is active for the terminating subscriber: Execute the MC Initiating a Short Message Analyzed task (see 4.XX.1). ENDIF. Remove the request from the queue. Exit this task. ENDWAIT. ENDIF.
Get SMS Address: 3-1 3-1-1 3-2 3-2-1 3-3 3-4 3-5 3-5-1 3-5-2 3-6 3-6-1 3-6-2 3-7
Wait for Notification: 3-7-1 3-7-2 3-7-3 3-7-3-1 3-7-3-2 3-7-4 3-7-4-1 3-7-4-1-1 3-7-4-2 3-7-4-3 3-7-4-4 3-7-5 3-8
163
X.S0010-A
4 5 5-1 5-2
ENDIF. IF the SMS event MS-terminated short message delivery attempt to MS-based SME is active for the originating subscriber: Execute the MC Initiating a Short Message Analyzed task (see 4.XX.1). IF the request is refused: Release storage for the message. Exit this task. ELSEIF the request failed AND network operator policy dictates that short message processing shall not proceed upon operation failure: Release storage for the message. Exit this task. ENDIF. ENDIF. IF notification of the presence of the MS is required: Optionally, include the SMS_NotificationIndicator parameter set to Notify when available. Optionally, include the SMS_MessageCount parameter set to the number of messages pending delivery to this MS. ELSE: Include the SMS_NotificationIndicator parameter set to Do not notify when available. ENDIF.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43
Send the message:
5-2-1 5-2-2 5-3 5-3-1 5-3-2 5-4 6 7 7-1 7-2 8 8-1 9
10 Set the underlying transport destination address to the temporary routing address of the MS (from the SMS_Address parameter). 11 Include the MobileIdentificationNumber parameter set to identify the destination MS. 12 Include the ElectronicSerialNumber parameter set to further identify the destination MS. 13 Include the SMS_BearerData parameter set by the SMS teleservice. 14 Include the SMS_TeleserviceIdentifier parameter set to identify the SMS teleservice. 15 Execute the Initiating SMS Delivery Point-To-Point task (see 4.46.2). 16 IF the indication was accepted: 16-1 16-1-1 16-2 16-3 17-1 IF the SMS event Successful MS-terminated short message delivery to MS-based SME is active for the terminating subscriber: Execute the MC Initiating a Short Message Analyzed task (see 4.XX.1). ENDIF. Exit this task. GOTO Wait for Notification.
44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
17 ELSEIF the indication was postponed. 18 ELSEIF the request resulted in a SMS_CauseCode value of Destination resource shortage: 18-1 IF the SMS event Unsuccessful MS-terminated short message delivery to MSbased SME is active for the terminating subscriber:
164
X.S0010-A
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
18-1-1 18-2 18-3 19-1 19-1-1 19-2 19-3
Execute the MC Initiating a Short Message Analyzed task (see 4.XX.1). ENDIF. Exit this task (the MC will get no further notification). IF the SMS event Unsuccessful MS-terminated short message delivery to MSbased SME is active for the terminating subscriber: Execute the MC Initiating a Short Message Analyzed task (see 4.XX.1). ENDIF. Execute Local Recovery Procedures task (see 3.5.1).
19 ELSE (the request was denied):
20 ENDIF. 21 Exit this task.
4.A
4.A.1
Analyzed Information
MSC Initiating an Analyzed Information
(see IS-848, page 6-40)
When the MSC determines that an active trigger at the Analyzed_Information DP has been encountered requiring call processing to be suspended while an SCF network entity executes service logic, and that trigger criteria have been met, the MSC shall perform the following: 1 2 3 4 5 6 7 8 9 Include the BillingID parameter set to the billing identifier for the call assigned by the current Originating MSC. Include the Digits (Dialed) parameter set to the digits received from the MS. Include the MSCID parameter set to the identity of the Originating MSC. Include the TransactionCapability parameter set to identify the current capabilities. 5 Include the TriggerType parameter set to identify the trigger that was encountered. Include other applicable parameters. Include the WINCapability parameter set to identify the current TriggerCapability and the current WINOperationsCapability. Send an AnalyzedInformation INVOKE to the SCF network entity address obtained from the TriggerAddressList parameter for the trigger that was encountered. Start the Analyzed Information Timer (ANZT).
10 WAIT for Analyzed Information response: 11 WHEN a RETURN RESULT is received: AnalyzedInformation RETURN RESULT Treatment: 11-1 11-2 11-2-1 11-2-1-1 11-2-1-1-1 Stop timer (ANZT) if it is running. IF the message can be processed: IF the incoming call is still connected: IF the AnnouncementList parameter is received: Execute Play All Announcements in the AnnouncementList task (see 3.2.5).
165
X.S0010-A
11-2-1-2 11-2-1-3 11-2-1-3-1 11-2-1-3-2 11-2-1-4 11-2-1-5 11-2-1-5-1 11-2-1-5-1-1 11-2-1-5-2 11-2-1-5-2-1 11-2-1-5-2-2 11-2-1-5-3 11-2-1-6 11-2-1-7 11-2-1-7-1 11-2-1-8 11-2-1-9 11-2-1-9-1 11-2-1-10 11-2-1-11 11-2-1-11-1 11-2-1-12 11-2-1-13 11-2-1-13-1 11-2-1-13-1-1 11-2-1-13-2 11-2-1-13-3 11-2-1-14 11-2-1-15 11-2-1-15-1 11-2-1-15-2 11-2-1-15-2-1 11-2-1-15-3 11-2-1-15-4
ENDIF. IF the AccessDeniedReason parameter is received AND IF it can be acted upon: Execute the Apply Access Denial Treatment task (see 3.4.5). Exit this task. ENDIF IF the TriggerAddressList parameter is received: IF the call is being redirected: Arm the triggers indicated by the received TriggerAddressList parameter for the redirected call. ELSE: Disarm any previously armed subscribed WIN triggers for the remainder of the call in progress. Arm the triggers indicated by the received TriggerAddressList parameter for the remainder of the call in progress. ENDIF. ENDIF. IF the ActionCode parameter is received: Execute the MSC ActionCode Processing task (see 3.2.9). ENDIF. IF the AlertCode parameter is received: Store the received AlertCode parameter value and discard any previously received value. ENDIF. IF the DisplayText parameter is received: Store the received DisplayText parameter value and discard any previously received value. ENDIF. IF the TerminationList parameter is received: IF WIN triggers remain Analyzed_Information DP: Return to the calling task. ENDIF. Execute the MSC Routing Point Of Return task (see 3.2.6). ENDIF. IF the Digits (Dialed) parameter is received: Set the MS dialed digits to the received Digits (Dialed) parameter value. IF the type of digits is unknown: Process the dialed number locally to set the PointOfReturn. ENDIF. IF WIN triggers remain Analyzed_Information DP: to be processed at the to be processed at the
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
166
X.S0010-A
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
11-2-1-15-4-1 11-2-1-15-5 11-2-1-16 11-2-1-16-1 11-2-1-17

11-2-1-18 11-2-1-18-1 11-2-1-18-1-1 11-2-1-18-2 11-2-1-18-2-1 11-2-1-18-3 11-2-1-18-3-1 11-2-1-18-3-2 11-2-1-18-4 11-2-1-19 ENDIF.
Return to the calling task. ENDIF. ELSE: Use the Digits (Dialed) parameter included AnalyzedInformation INVOKE as MS dialed digits. ENDIF.
IF the ResumePIC parameter is received: IF the value of the ResumePIC parameter is Continue Call Processing: Return to the calling task. ELSEIF the value of the ResumePIC parameter is a valid transition: GOTO the entry point indicated by the ResumePIC parameter. ELSE: Execute Local Recovery Procedures task (see 3.5.1). Exit this task. ENDIF.
in
the
11-2-2 11-2-2-1 11-2-2-2 11-2-3 11-3 11-3-1 11-3-2 11-4 12-1 12-1-1 12-1-2 12-1-3 12-2 12-3 13-1 13-2 13-3 13-4 13-4-1 13-4-2 13-5 13-5-1 13-6 13-6-1
ELSE (call abandoned): Execute the Local Recovery Procedures task (see 3.5.1). Exit this task. ENDIF. ELSE (the message cannot be processed): Execute Local Recovery Procedures task (see 3.5.1). Exit this task. ENDIF. IF the call is still connected Stop timer (ANZT). Execute the MSC Remote User Interaction task (see 4.39.2). Start the AnalyzedInformation Timer (ANZT). ENDIF Remain in this state. Stop the timer (ANZT). Execute the MSC Receiving ConnectResource INVOKE task (see 4.B.3). CASE MSC Connect Resource result OF: Disconnect Resource received: Start the timer (ANZT). Remain in this state. AnalyzedInformation RETURN RESULT received: GOTO AnalyzedInformation RETURN RESULT Treatment. SSFT expiration: Start the timer (ANZT).
167
X.S0010-A
13-6-2 13-7 13-7-1 13-7-2 13-8 13-8-1 13-8-2 13-9 13-9-1 13-9-2 13-10 13-10-1 13-10-2 13-11 14-1 14-2 14-3 15-1 15-2 15-3 16-1 16-2
Remain in this state. call abandoned: Execute the Local Recovery Procedures task (see 3.5.1). Exit this task. resource disconnect: Start the timer (ANZT). Remain in this state. failure at MSC: Start the timer (ANZT). Remain in this state. message error: Start the timer (ANZT). Remain in this state. ENDCASE. Stop the timer (ANZT). Execute the Local Recovery Procedures task (see 3.5.1). Exit this task. Stop timer (ANZT). Execute Local Recovery Procedures task (see 3.5.1). Exit this task. Execute Local Recovery Procedures task (see 3.5.1). Exit this task.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41
14 WHEN the incoming call disconnects:
16 WHEN timer (ANZT) expires:
17 ENDWAIT. 18 Return to the calling task.
4.E
4.E.1
Facility Selected And Available

MSC Initiating a Facility Selected And Available
(see IS-848, page 6-44)
42 43 44 45 46 47 48
When the MSC determines that an active Terminating_Resource_Available trigger has been encountered requiring call processing to be suspended while an SCF network entity executes service logic, and that trigger criteria have been met, it shall perform the following: 1 2 3 Include the BillingID parameter set to the billing identifier for the call assigned by the current Serving MSC. Include the MSCID parameter set to the identity of the Serving MSC. Include the TransactionCapability parameter set to identify the current capabilities.
49 50 51 52 53 54 55 56 57 58 59 60
168
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
4 5 6 6-1 7 8 9
Include the TriggerType parameter set to identify the trigger that was encountered. Include the WINCapability parameter set to identify the current TriggerCapability and the current WINOperationsCapability of the MSC. IF the call leg was established with a PilotBillingID parameter: Include the PilotBillingID parameter set to the same value as received. ENDIF. Include other applicable parameters. Send a FacilitySelectedAndAvailable INVOKE to the SCF network entity indicated by the TriggerAddressList parameter for the trigger that was encountered.
10 Start the Facility Selected And Available Timer (FAVT). 11 WAIT for Facility Selected And Available response: 12 WHEN a RETURN RESULT is received: FacilitySelectedAndAvailable RETURN RESULT Treatment: 12-1 12-2 12-2-1 12-2-1-1 12-2-1-1-1 12-2-1-1-2 12-2-1-2 12-2-1-3 12-2-1-3-1 12-2-1-3-2 12-2-1-4 12-2-1-5 12-2-1-5-1 12-2-1-6 12-2-1-7 12-2-1-7-1 12-2-1-8 12-2-1-9 12-2-1-9-1 12-2-1-10
12-2-1-11 12-2-1-11-1 12-2-1-11-1-1 12-2-1-11-2 12-2-1-11-2-1
Stop the timer (FAVT), if the timer is still running. IF the message can be processed: IF the incoming call is still connected: IF the AccessDeniedReason parameter is received AND IF it can be acted upon: Execute the Apply Access Denial Treatment task (see 3.4.5). Return to the calling task. ENDIF IF the TriggerAddressList parameter is received: Disarm any previously armed subscribed WIN triggers for the remainder of the call in progress. Arm the triggers indicated by the received TriggerAddressList parameter for the remainder of the call in progress. ENDIF. IF the AlertCode parameter is received: Store the received AlertCode parameter value and discard any previously received value. ENDIF. IF the DisplayText parameter is received: Store the received DisplayText parameter value and discard any previously received value. ENDIF. IF the ActionCode parameter is received: Execute the MSC ActionCode Processing task (see 3.2.9). ENDIF.
IF the ResumePIC parameter is received: IF the value of the ResumePIC parameter is Continue: Return to the calling task. ELSEIF the value of the ResumePIC parameter is a valid transition: GOTO the entry point indicated by the ResumePIC parameter.
169
X.S0010-A
12-2-1-11-3 12-2-1-11-3-1 12-2-1-11-3-2 12-2-1-11-4 12-2-1-12
ELSE: Execute Local Recovery Procedures task (see 3.5.1). Exit this task. ENDIF. ENDIF.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
12-2-2 12-2-2-1 12-2-2-2 12-2-3 12-3 12-3-1 12-3-2 12-4 13-1 13-2 14-1 14-2 14-3 15-1 15-2
ELSE (call abandoned): Execute the Local Recovery Procedures task (see 3.5.1). Exit this task. ENDIF. ELSE (the message cannot be processed): Execute Local Recovery Procedures task (see 3.5.1). Exit this task. ENDIF. Execute the Local Recovery Procedures task (see 3.5.1). Exit this task. Stop timer (FAVT). Execute Local Recovery Procedures task (see 3.5.1). Exit this task. Execute Local Recovery Procedures task (see 3.5.1). Exit this task.
21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
15 WHEN timer (FAVT) expires:
16 ENDWAIT 17 Return to the calling task.
4.M
4.M.1
TBusy
MSC Initiating a TBusy
(see IS-848, page 6-46)
38 39 40 41 42 43 44
When the MSC determines that an active T_Busy trigger armed by a TriggerAddressList parameter has been encountered requiring call processing to be suspended while an SCF network entity executes service logic, and that trigger criteria have been met, the MSC shall perform the following: 1 2 2-1 3 3-1 Include the MSCID parameter set to the identity of the MSC. IF the MSC is the Originating MSC: Include the Originating MSCs calls BillingID parameter to identify the call for subsequent call redirection. ELSEIF the MSC is the Serving MSC: Include the Serving MSCs BillingID parameter to identify the call for subsequent call redirection.
45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
170
TBusy
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
4 5 6 7 8 8-1 9
ENDIF. Include the TransactionCapability parameter set to identify the current capabilities. Include the TriggerType parameter set to identify the trigger that was encountered. Include the WINCapability parameter set to identify the current TriggerCapability and the current WIN Operations Capability. IF the call leg was established with a PilotBillingID parameter: Include the PilotBillingID parameter set to the same value as received. ENDIF.
10 Include other applicable parameters. 11 Send a TBusy INVOKE to the SCF network entity indicated by the TriggerAddressList parameter. 12 Start the TBusy Timer (TBT). 13 WAIT for a TBusy response: 14 WHEN a RETURN RESULT is received: TBusy RETURN RESULT Treatment: 14-1 14-2 14-2-1 14-2-1-1 14-2-1-1-1 14-2-1-2 14-2-1-3 14-2-1-3-1 14-2-1-4 14-2-1-5 14-2-1-5-1 14-2-1-6 14-2-1-7 14-2-1-7-1 14-2-1-8 14-2-1-9 14-2-1-9-1 14-2-1-10
14-2-1-11 14-2-1-11-1 14-2-1-11-1-1 14-2-1-11-2 14-2-1-11-2-1 14-2-1-11-3 14-2-1-11-3-1
Stop the timer (TBT), if it is running. IF the message can be processed: IF the incoming call is still connected: IF the AnnouncementList parameter is received: Execute the Play All Announcements in the AnnouncementList task (see 3.2.5). ENDIF. IF AccessDeniedReason parameter is received: Return to the calling task with an unsuccessful indication. ENDIF. IF the TriggerAddressList parameter is received: Arm the triggers indicated by the received TriggerAddressList parameter for the redirected call. ENDIF. IF the ActionCode parameter is received: Execute the MSC ActionCode Processing task (see 3.2.9). ENDIF. IF the TerminationList parameter is received: Execute the MSC Routing Points of Return task (see 3.2.6). ENDIF.
IF the ResumePIC parameter is received: IF the value of ResumePIC parameter is Continue: Return to the calling task. ELSEIF the transition indicated by the ResumePIC parameter is valid: GOTO the entry point indicated by the ResumePIC parameter. ELSE: Return to the calling task with an unsuccessful indication.
TBusy
171
X.S0010-A
14-2-1-11-4 14-2-1-12
ENDIF. ENDIF.
1 2 3 4 5 6
14-2-2 14-2-2-1 14-2-2-2 14-2-3 14-3 14-3-1 14-4 15-1 15-1-1 15-1-2 15-1-3 15-2 15-3 16-1 16-2 16-3 16-4 16-4-1 16-4-2 16-5 16-5-1 16-6 16-6-1 16-6-2 16-7 16-7-1 16-7-2 16-8 16-8-1 16-8-2 16-9 16-9-1 16-9-2 16-10 16-10-1 16-10-2 16-11
ELSE (call abandoned): Execute the Local Recovery Procedures task (see 3.5.1). Exit this task. ENDIF. ELSE (the message cannot be processed): Return to the calling task with an unsuccessful indication. ENDIF. IF the call is still connected: Stop the timer (TBT). Execute the MSC Remote User Interaction task (see 4.39.2). Start the TBusy Timer (TBT). ENDIF Remain in this state. Stop the timer (TBT). Execute the MSC Receiving ConnectResource INVOKE task (see 4.B.3). CASE MSC Connect Resource result OF: Disconnect Resource received: Start the timer (TBT). Remain in this state. TBusy RETURN RESULT received: GOTO TBusy RETURN RESULT Treatment. SSFT expiration: Start the timer (TBT). Remain in this state. call abandoned: Execute the Local Recovery Procedures task (see 3.5.1). Exit this task. resource disconnect: Start the timer (TBT). Remain in this state. failure at MSC: Start the timer (TBT). Remain in this state. message error: Start the timer (TBT). Remain in this state. ENDCASE.
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
172
TBusy
X.S0010-A
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
17 WHEN the incoming call disconnects: 17-1 17-2 18-1 18-2 19-1 Execute the Local Recovery Procedures task (see 3.5.1). Exit this task. Stop the timer (TBT). Return to the calling task with an unsuccessful indication. Return to the calling task with an unsuccessful indication.
19 WHEN the timer (TBT) expires: 20 ENDWAIT. 21 Return to the calling task.
4.N
4.N.1
TNoAnswer
MSC Initiating a TNoAnswer
(see IS-848, page 6-48)
When the MSC determines that an active T_No_Answer trigger armed by a TriggerAddressList parameter has been encountered requiring call processing to be suspended while an SCF network entity executes service logic, and that trigger criteria have been met, the MSC shall perform the following: 1 2 2-1 3 3-1 4 5 6 7 8 8-1 9 Include the MSCID parameter set to the identity of the MSC. IF the MSC is the Originating MSC: Include the Originating MSCs calls BillingID parameter to identify the call for subsequent call redirection. ELSEIF the MSC is the Serving MSC: Include the Serving MSCs BillingID parameter to identify the call for subsequent call redirection. ENDIF. Include the TransactionCapability parameter set to identify the current capabilities. Include the TriggerType parameter set to identify the trigger that was encountered. Include the WINCapability parameter set to identify the current TriggerCapability and the current WIN Operations Capability. IF the call leg was established with a PilotBillingID parameter: Include the PilotBillingID parameter set to the same value as received. ENDIF.
10 Include other applicable parameters. 11 Send a TNoAnswer INVOKE to the SCF network entity indicated by the TriggerAddressList parameter. 12 Start the TNoAnswer Timer (TNAT). 13 WAIT for a TNoAnswer response: 14 WHEN a RETURN RESULT is received: TNoAnswer RETURN RESULT Treatment:
TNoAnswer
173
X.S0010-A
14-1 14-2 14-2-1 14-2-1-1
Stop the timer (TNAT), if it is running. IF the message can be processed: IF the incoming call is still connected: IF the AnnouncementList parameter is received: Execute the Play All Announcements in the AnnouncementList task (see 3.2.5). ENDIF. IF AccessDeniedReason parameter is received: Execute the Apply Access Denial Treatment task (see 3.4.5). Return to the calling task. ENDIF. IF the TriggerAddressList parameter is received: Arm the triggers indicated by the received TriggerAddressList parameter for the redirected call. ENDIF. IF the ActionCode parameter is received: Execute the MSC ActionCode Processing task (see 3.2.9). ENDIF. IF the TerminationList parameter is received: Execute the MSC Routing Points of Return task (see 3.2.6). ENDIF.
IF the ResumePIC parameter is received: IF the value of ResumePIC parameter is Continue: Return to the calling task. ELSEIF the transition indicated by the ResumePIC parameter is valid: GOTO the entry point indicated by the ResumePIC parameter. ELSE: Return to the calling task with an unsuccessful indication. ENDIF. ENDIF.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
14-2-1-1-1 14-2-1-2 14-2-1-3 14-2-1-3-1 14-2-1-3-2 14-2-1-4 14-2-1-5 14-2-1-5-1 14-2-1-6 14-2-1-7 14-2-1-7-1 14-2-1-8 14-2-1-9 14-2-1-9-1 14-2-1-10
14-2-1-11 14-2-1-11-1 14-2-1-11-1-1 14-2-1-11-2 14-2-1-11-2-1 14-2-1-11-3 14-2-1-11-3-1 14-2-1-11-4 14-2-1-12
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
14-2-2 14-2-2-1 14-2-2-2 14-2-3 14-3 14-3-1 14-4 15-1 15-1-1 15-1-2 15-1-3
ELSE (call abandoned): Execute the Local Recovery Procedures task (see 3.5.1). Exit this task. ENDIF. ELSE (the message cannot be processed): Return to the calling task with an unsuccessful indication. ENDIF. IF the call is still connected: Stop the timer (TNAT). Execute the MSC Remote User Interaction task (see 4.39.2). Start the TBusy Timer (TNAT).
53 54 55 56 57 58 59 60
174
TNoAnswer
X.S0010-A
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
15-2 15-3 16-1 16-2 16-3 16-4 16-4-1 16-4-2 16-5 16-5-1 16-6 16-6-1 16-6-2 16-7 16-7-1 16-7-2 16-8 16-8-1 16-8-2 16-9 16-9-1 16-9-2 16-10 16-10-1 16-10-2 16-11 17-1 17-2 18-1 18-2 19-1
ENDIF Remain in this state. Stop the timer (TNAT). Execute the MSC Receiving ConnectResource INVOKE task (see 4.B.3). CASE MSC Connect Resource result OF: Disconnect Resource received: Start the timer (TNAT). Remain in this state. TNoAnswer RETURN RESULT received: GOTO TNoAnswer RETURN RESULT Treatment. SSFT expiration: Start the timer (TNAT). Remain in this state. call abandoned: Execute the Local Recovery Procedures task (see 3.5.1). Exit this task. resource disconnect: Start the timer (TNAT). Remain in this state. failure at MSC: Start the timer (TNAT). Remain in this state. message error: Start the timer (TNAT). Remain in this state. ENDCASE. Execute the Local Recovery Procedures task (see 3.5.1). Exit this task. Stop the timer (TNAT). Return to the calling task with an unsuccessful indication. Return to the calling task with an unsuccessful indication.
19 WHEN the timer (TNAT) expires: 20 ENDWAIT. 21 Return to the calling task.
TNoAnswer
175
X.S0010-A
4.U
4.U.1
OAnswer
MSC Initiating an OAnswer
(see IS-826, page 6-68)
1 2 3 4 5 6 7 8 9 10 11
When the MSC determines that an active O_Answer trigger armed by a TriggerAddressList parameter has been encountered requiring call processing to notify the SCF network entity, and trigger criteria have been met, the MSC shall perform the following: The remainder of this section is retained unchanged.
12 13 14 15
4.W
4.W.1
TAnswer
MSC Initiating a TAnswer
(see IS-826, page 6-72)
16 17 18 19 20 21 22 23 24 25 26 27
When the MSC determines that an active T_Answer trigger armed by a TriggerAddressList parameter has been encountered requiring call processing to notify the SCF network entity and trigger criteria have been met, the MSC shall perform the following: The remainder of this section is retained unchanged.
28 29 30 31
4.Z
4.Z.1
OCalledPartyBusy
MSC Initiating an OCalledPartyBusy
(see IS-848, page 6-51)
32 33 34 35 36 37 38 39 40 41 42 43
When the MSC determines that an active O_Called_Party_Busy trigger armed by a TriggerAddressList parameter has been encountered requiring call processing to be suspended while an SCF network entity executes service logic, and trigger criteria have been met, the MSC shall perform the following: The remainder of this section is retained unchanged.
44 45 46 47
4.AA ONoAnswer
4.AA.1 MSC Initiating an ONoAnswer
(see IS-848, page 6-55)
48 49 50 51 52 53 54
When the MSC determines that an active O_No_Answer trigger armed by a TriggerAddressList parameter has been encountered requiring call processing to be
55 56 57 58 59 60
176
OAnswer
X.S0010-A
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
suspended while an SCF network entity executes service logic, and trigger criteria have been met, the MSC shall perform the following: The remainder of this section is retained unchanged.
4.XX
4.XX.1
Short Message Analyzed

(New for TIA/EIA-41.6-D, Section 4)
MC Initiating Short Message Analyzed

When the MC determines that an active SMS event has been encountered for this short message that requires short message processing to be suspended while an SCF network entity executes service logic, the MC shall perform the following: 1 2 3 4 5 6 7 8 9 Include the SMS_BearerLength parameter set to the length of the SMS bearer data for the short message. Include the SMS_BillingID parameter set to the billing identifier for the short message. Include the SMS_Event parameter set to identify the event that was encountered. Include the SMS_TeleserviceID parameter set to the SMS teleservice identifier for the short message. If available, include the MobileDirectoryNumber parameter set to the MS-based SME Mobile Directory Number. If available, include the MSID parameter set to the MS-based SME MSID. Include other available parameters that are applicable. Send an ShortMessageAnalyzed INVOKE to the SCF network entity address obtained from the MS-Based SME subscribers profile for the event that was encountered. Start the Short Message Analyzed Timer (SMAT).
10 WAIT for ShortMessageAnalyzed response: 11 WHEN a RETURN RESULT is received: 11-1 11-2 11-2-1 11-2-1-1 11-2-2 11-2-3 11-2-3-1 11-2-4 11-2-5 11-3 11-3-1 Stop the timer (SMAT). IF the message can be processed: IF the SMS_CauseCode parameter is received: Return to the calling task with all received parameters and a refused indication. ENDIF. IF the SMS_EventNotification parameter is received: Set the events indicated by the received SMS_EventNotification parameter with the associated SMS message for further processing. ENDIF. Return to the calling task with all received parameters and an accepted indication. ELSE (the message cannot be processed): Execute Local Recovery Procedures task (see 3.5.1).
177
X.S0010-A
11-4 12-1 12-2 13-1
ENDIF. Stop the timer (SMAT). Execute Local Recovery Procedures task (see 3.5.1). Execute Local Recovery Procedures task (see 3.5.1).
1 2 3 4 5 6 7 8 9 10 11 12 13
13 WHEN the timer (SMAT) expires: 14 ENDWAIT. 15 Return to the calling task with a failed indication.
4.XX.2
SCF Receiving ShortMessageAnalyzed INVOKE

When an SCF network entity receives an ShortMessageAnalyzed INVOKE, it shall perform the following: 1 1-1 1-2 1-3 2 2-1 3 4 IF the received message can be processed: Execute WIN Service Logic task (see 6.Y). Relay the parameters received from the service logic task. Send a RETURN RESULT to the requesting MC. ELSE (the received message cannot be processed): Send a RETURN ERROR with the proper Error Code value (see the following table) to the requesting MC. ENDIF. Exit this task.
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
178
X.S0010-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
Table 1 SCF ShortMessageAnalyzed Response Problem Detection and Recommended Response from SCF
RETURN ERROR Error Code
MSID/HLRMismatch UnrecognizedMIN UnrecognizedESN UnrecognizedIMSI ResourceShortage OperationNotSupported MissingParameter ParameterError SystemFailure UnrecognizedParameterValue
Problem Definition The supplied MSID parameter is not in the network entitys range of MSIDs (suspect routing error). The network entity does not presently have a record for the supplied MobileIdentificationNumber parameter. The network entity presently has a record for the supplied MSID parameter, but the supplied ElectronicSerialNumber parameter does not match the ESN in that record. The network entity does not presently have a record for the supplied IMSI parameter. A required resource (e.g., internal memory record, network entity is fully occupied) is temporarily not available (e.g., congestion). The requested MAP operation is recognized, but not supported by the receiving network entity, or the requesting network entity is not authorized. An expected, or required, optional parameter was not received. Include the Parameter Identifier in question as the FaultyParameter parameter. A supplied parameter has an encoding problem. Include the Parameter Identifier in question as the FaultyParameter parameter. A required resource (e.g., data base access, functional entity) is not presently accessible due to a failure. Human intervention may be required for resolution. A supplied parameter value is unrecognized or has non-standard value. Include the Parameter Identifier in question as the FaultyParameter parameter.
179
X.S0010-A
OPERATION TIMER VALUES

1 2 3 4
The following table provides a summary of the timers used for MAP operations. The timer values specied in this table are default values only and should be optimized for actual operating environments. Some timers are locally dened and are not in this table (e.g., alerting timer, no answer timer, page response timer, maximum interaction timer, interdigit timer). Table 63 Operation Timer Values
Timer SMAT Short Message Analyzed Timer Default (sec.) 16 Start when ShortMessageAnalyzed INVOKE is sent Normally stopped when ShortMessageAnalyzed RETURN RESULT or RETURN ERROR is received Action when timer expires Execute recovery procedures
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
180
Operation Timer Values

X.S0010-A v1.0 010504

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

X.S0010-A v1.0 010504

Hochgeladen von

Copyright:

Verfügbare Formate

3GPP2 X.S0010-A Version: 1.

0 Date: 5 January 2004

8.X.13 8.X.16 8.X.18 8.X.20 8.X.33 8.X.41

6.4.2.m 6.4.2.t 6.4.2.u 6.4.2.aa 6.4.2.ad 6.4.2.ag 6.4.2.ag 6.4.2.ax 6.5

ANNEX A: ASN.1 NOTATION FOR WIN PARAMETERS ......................................................148

4.A 4.E 4.M 4.N

4.N.1 4.U 4.W 4.Z 4.AA 4.XX

MSC Initiating a TNoAnswer........................................................................... 173

Operation Timer Values ................................................................................................................ 180

IS-826 Chapter 5 Modifications IS-826 Chapter 6 Modifications

IS-826 Chapter 3 Modifications Table X Message Interfaces ....................................................................................................... 19

This page is intentionally left blank.

IS-826 IS-841 IS-848

cross out: deletion

IS-826 CHAPTER 2 MODIFICATIONS

DEFINITIONS AND CONCEPTS

IS-826 Chapter 2 Modications

Denitions and Concepts

WIRELESS INTELLIGENT NETWORK FEATURE DESCRIPTIONS

Normal Procedures with Successful Outcome

Wireless Intelligent Network Feature Descriptions

IS-826 Chapter 2 Modications

The authorization may have the following subscription options:

IS-826 Chapter 2 Modications

Pre-Paid Charging (PPC)

Pre-Paid Charging (PPC)

IS-826 Chapter 2 Modications

IS-826 Chapter 2 Modications

Pre-Paid Charging (PPC)

Normal operation with insufficient balance for a circuit-switched data call

Pre-Paid Charging (PPC)

IS-826 Chapter 2 Modications

Other charges: same as All-ServicesCalls chargeable events

IS-826 Chapter 2 Modications

Pre-Paid Charging (PPC)

Exception Procedures or Unsuccessful Outcome

Pre-Paid Charging (PPC)

IS-826 Chapter 2 Modications

Exceptions During Intersystem Handoff None identified.

IS-826 Chapter 2 Modications

Pre-Paid Charging (PPC)

Interactions With Other Network Services

Pre-Paid Charging (PPC)

IS-826 Chapter 2 Modications

Data Privacy (DP) PPC is invoked before DP.

IS-826 Chapter 2 Modications

Pre-Paid Charging (PPC)

Pre-Paid Charging (PPC)

IS-826 Chapter 2 Modications

IS-826 Chapter 2 Modications

Pre-Paid Charging (PPC)

IS-826 CHAPTER 3 MODIFICATIONS

SYMBOLS AND ABBREVIATIONS

The omitted portion of this section is retained without modification.

SM_ANLYZD sm_anlyzd SMS_BRLEN SMS_BILLID SMS_EVENT SMS_EVENTNOT SMS_PMCNT

Symbols and Abbreviations

IS-826 Chapter 3 Modications

NETWORK REFERENCE MODEL

Figure X Network Reference Model for Pre-Paid Charging Enhancements

Interface Reference Points

IS-826 Chapter 3 Modications

Network Reference Model