X.S0010-A_v1.0_010504

3GPP2 X.S0010-A Version: 1.0 Date: 5 January 2004

Pre-Paid Charging Enhancements for Circuit-Switched 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 [email protected]. 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

Contents i

PRE-PAID CHARGING ENHANCEMENTS FORCIRCUIT SWITCHED DATA AND SHORT MESSAGE SERVICES

CONTENTS

List of Figures...................................................................................................................................................v

List of Tables .................................................................................................................................................. vi

Revision History ............................................................................................................................................ vii

Introduction.......................................................................................................................................................1

1 General ...............................................................................................................................................1

2 References ..........................................................................................................................................1

3 Editorial Conventions.........................................................................................................................1

4 Assumptions .......................................................................................................................................2

IS-826 Chapter 2 Modifications .......................................................................................................................4

3 Definitions and Concepts ...................................................................................................................4

3.1 Definitions............................................................................................................................4

5 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 Symbols and Abbreviations .............................................................................................................17

5 Network Reference Model ...............................................................................................................18

5.X Network Reference Model for Pre-Paid Charging Enhancements ....................................18

5.X.1 Interface Reference Points...................................................................................185.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 Call Processing Resumption Point.....................................................................................20

8.X 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

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

Contentsii

8.X.13 Three-Way Calling: Insufficient Balance for Third-Party Call .......................... 27

8.X.16 MS Call Origination with Abbreviated Dialing.................................................. 28

8.X.18 Abbreviated Dialing: Insufficient Balance for Call ............................................ 29

8.X.20 Call Origination: Charge Rate Dependent on MS Location ............................... 30

8.X.33 MS-to-MS Call: SN Based.................................................................................. 31

8.X.41 Circuit-Switched Data Services .......................................................................... 328.X.41.1 MS Circuit-Switched Data Call Origination: Called Party

Disconnect ..................................................................................... 338.X.41.2 MS Circuit-Switched Data Call Origination: Mid-Call Notification

of Low Balance ............................................................................. 368.X.41.3 MS Circuit-Switched Data Call Origination: Service Logic Directed

Call Release................................................................................... 408.X.41.4 Circuit-Switched Data Call Delivery: Intersystem Termination... 448.X.41.5 SCP-Based Call Forwarding Busy on Call Collision.................... 508.X.41.6 SCP-Based Call Forwarding Busy on Circuit-Switched Data Call

....................................................................................................... 57

8.X.42 Short Message Services ...................................................................................... 628.X.42.1 PPC for MS-Originated Short Message Accepted by the Network

....................................................................................................... 638.X.42.2 PPC for MS-Originated Short Message Delivered to Destination

SME............................................................................................... 668.X.42.3 PPC for MS-Originated Short Message Not Accepted by the

Network......................................................................................... 708.X.42.4 PPC for MS-Originated Short Message: Message Not Accepted by

Destination SME ........................................................................... 718.X.42.5 PPC for MS-Originated Short Message Purged by Originator’s

Home MC...................................................................................... 738.X.42.6 PPC for MS-Terminated Short Message Delivered to Subscriber 768.X.42.7 PPC for MS-Terminated Short Message Accepted by Home MC 818.X.42.8 MS-Terminated Short Message Not Delivered: Low Balance...... 828.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 SS7-Based Data Transfer Services.................................................................................... 86

6 Application Services........................................................................................................................ 86

6.4 MAP Operations................................................................................................................ 86

6.4.1 General................................................................................................................ 866.4.1.2 Operation Specifiers...................................................................... 86

6.4.2 Operation Definitions.......................................................................................... 866.4.2.13 FeatureRequest .............................................................................. 876.4.2.24 InterSystemPage............................................................................ 896.4.2.30 OriginationRequest........................................................................ 906.4.2.40 RoutingRequest ............................................................................. 946.4.2.46 TransferToNumberRequest ........................................................... 976.4.2.51 UnsolicitedResponse ..................................................................... 996.4.2.h ServiceRequest ............................................................................ 1016.4.2.i AnalyzedInformation .................................................................. 106

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

Contents iii

6.4.2.m FacilitySelectedAndAvailable .....................................................1106.4.2.t TBusy...........................................................................................1126.4.2.u TNoAnswer..................................................................................1166.4.2.aa OAnswer ......................................................................................1206.4.2.ad TAnswer.......................................................................................1226.4.2.ag OCalledPartyBusy........................................................................1246.4.2.ag ONoAnswer .................................................................................1266.4.2.ax ShortMessageAnalyzed................................................................128

6.5 Map Parameters ...............................................................................................................131

6.5.1 General ..............................................................................................................1316.5.1.1 Parameter Identifiers....................................................................131

6.5.2 Parameter Definitions........................................................................................1326.5.2.2 ActionCode ..................................................................................1326.5.2.97 Profile...........................................................................................1336.5.2.125 SMS_CauseCode .........................................................................1346.5.2.j TDMAServiceCode .....................................................................1376.5.2.cu ResumePIC ..................................................................................1386.5.2.dg TriggerList ...................................................................................1396.5.2.dj WINOperationsCapability ...........................................................1406.5.2.hn SMS_BearerLength......................................................................1416.5.2.ho SMS_BillingID ............................................................................1426.5.2.hp SMS_Event ..................................................................................1436.5.2.hq SMS_EventNotification...............................................................1446.5.2.hr SMS_PendingMessageCount.......................................................1466.5.2.hs TriggerCriteria .............................................................................147

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

IS-826 Chapter 6 Modifications ...................................................................................................................149

4 Intersystem Procedures ..................................................................................................................149

4.14 Feature Request................................................................................................................149

4.14.1 MSC Detecting Feature Request .......................................................................149

4.25 InterSystem Page .............................................................................................................152

4.25.2 MSC Receiving InterSystemPage INVOKE.....................................................152

4.31 Origination Request .........................................................................................................154

4.31.1 MSC Initiating an Origination Request.............................................................154

4.46 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

4.A Analyzed Information ......................................................................................................165

4.A.1 MSC Initiating an Analyzed Information..........................................................165

4.E Facility Selected And Available ......................................................................................168

4.E.1 MSC Initiating a Facility Selected And Available ............................................168

4.M TBusy...............................................................................................................................170

4.M.1 MSC Initiating a TBusy.....................................................................................170

4.N TNoAnswer......................................................................................................................173

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

Contentsiv

4.N.1 MSC Initiating a TNoAnswer........................................................................... 173

4.U OAnswer.......................................................................................................................... 176

4.U.1 MSC Initiating an OAnswer ............................................................................. 176

4.W TAnswer .......................................................................................................................... 176

4.W.1 MSC Initiating a TAnswer................................................................................ 176

4.Z OCalledPartyBusy........................................................................................................... 176

4.Z.1 MSC Initiating an OCalledPartyBusy............................................................... 176

4.AA ONoAnswer..................................................................................................................... 176

4.AA.1 MSC Initiating an ONoAnswer ........................................................................ 176

4.XX Short Message Analyzed................................................................................................. 177

4.XX.1 MC Initiating Short Message Analyzed............................................................ 177

4.XX.2 SCF Receiving ShortMessageAnalyzed INVOKE........................................... 178

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

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 v

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


Figure 8.8

Call Processing Resumption Point.....................................................................................................20

Figure 1 MS Registration .................................................................................................................21

Figure 2 MS Circuit-Switched Data Call Origination: Called Party Disconnect.............................33

Figure 3 MS Circuit-Switched Data Call Origination: Mid-Call Notification of Low Balance ......36

Figure 4 MS Circuit-Switched Data Call Origination: Service Logic Directed Call Release .........40

Figure 5 Circuit-Switched Data Call Delivery: Intersystem Termination .......................................45

Figure 6 SCP-Based Call Forwarding Busy on Call Collision (1 of 2) ...........................................50

Figure 7 SCP-Based Call Forwarding Busy on Call Collision (2 of 2) ...........................................55

Figure 8 SCP-Based Call Forwarding Busy on Circuit-Switched Data Call (1 of 2) ......................57

Figure 9 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 Originator’s 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 MS-Terminated Short Message Not Delivered: Low Balance .........................................82

Figure 18 MS-Terminated Short Message Not Delivered: MS Inaccessible ....................................83



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 Tablesvi

LIST OF TABLES

Introduction


Table 1 PPC Subscription Options .............................................................................................. 6

IS-826

Chapter 3 Modifications

Table X Message Interfaces ....................................................................................................... 19



Table 1 MTP Message Priority Values for TIA/EIA-41 Operations......................................... 86

Table 8 TIA/EIA-41 MAP Operation Specifiers....................................................................... 86

Table 10 Summary of MAP Operations ...................................................................................... 86

Table 11 NE Combinations for SM_ANLYZD ........................................................................ 128

Table 12 TIA/EIA-41 MAP Parameter Identifiers .................................................................... 131

Table A-1 ASN.1 Notation for WIN Parameters......................................................................... 148


Table 1 SCF ShortMessageAnalyzed Response...................................................................... 179

Table 63 Operation Timer Values ............................................................................................. 180

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 vii

REVISION HISTORY

Revision Date Remarks

0 June 2000 Initial Publication of N.S0018

A December 2003 Revised for Publication as X.S0010-A

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 Historyviii

This page is intentionally left blank.

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

General 1 Introduction

INTRODUCTION

Pre-Paid Charging (PPC) enables the subscriber to pay for telecommunication servicesprior to usage. This document presents a recommended plan for the implementation ofWireless Intelligent Network (WIN) capabilities that support PPC for circuit-switched dataand short message services (SMS). The WIN capabilities that support PPC are for use inthe Wireless Radiotelephone Service.

1 GENERAL

This document describes the additions and modifications to

TIA/EIA/IS-826

, WirelessIntelligent Network Capabilities for Pre-Paid Charging, to support circuit-switched dataand short message services.

2 REFERENCES

This document builds on the following American National Standards Institute (ANSI)standards:

TIA/EIA-664 TIA/EIA-664-A

, Wireless Features Description; TelecommunicationsIndustry Association; July 2000

TIA/EIA-41 TIA/EIA-41-D

, Cellular Radiotelecommunications IntersystemOperations; Telecommunications Industry Association;December 1997

IS-737 TIA/EIA/IS-737

,

IS-41-C

Enhancements for Circuit Mode Services;Telecommunications Industry Association; December 1997


,

TIA/EIA-41-D

Enhancements forInternationalization; Telecommunications Industry Association;August 1999


, Wireless Intelligent Network Capabilities for Pre-Paid Charging; Telecommunications Industry Association; June 2000


, MDN Based Message Centers; TelecommunicationsIndustry Association; September 2000


, Wireless Intelligent Network Capabilities forEnhanced Charging Services; Telecommunications IndustryAssociation; October 2000

DMH TIA/EIA-124-D

, Wireless Radio Telecommunication IntersystemNon-Signaling Data Communication DMH (Data Message Handler);Telecommunications Industry Association; December 2001

3 EDITORIAL CONVENTIONS

The following editorial conventions are used for this document:

• underline: addition

X.S0010-A

Introduction 2 Assumptions

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

•

cross out

: deletion

• 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 notunderlined

4 ASSUMPTIONS

The following assumptions were used in the development of this document:

a. MS originated Asynchronous Data Service (ADS) shall only be of type

DataOnly

.

b. MS terminated Asynchronous Data Service (ADS) shall only be of types

OneNumber per Service

and

Two-Stage Dialing

.

c. MS originated Group 3 Facsimile Service (G3 Fax) shall only be of type

G3 FaxOnly

.

d. MS terminated Group 3 Facsimile Service (G3 FAX) shall be of types

OneNumber per Service

and

Two-Stage Dialing

.

e. PPC for Short Message Service (SMS) applies to both MS originated SMS (MOSMS) and MS terminated SMS (MT SMS).

f. Single call activation is not applicable for SMS PPC.

g. For pre-paid MS originated SMS, the short message is first to be routed to thesubscriber's Home Message Center (MC).

h. For pre-paid MS terminated SMS, the short message is routed to the subscriber’sHome Message Center (MC) before delivery to the Serving MSC.

i. Support for pre-paid SMS is based on enhancements to the existing Short MessageDelivery–Point-to-Point Bearer Service specified in

TIA/EIA-664

.

j. The ability of a subscriber to refuse delivery of an SMS message and not becharged for the message, is not considered in this document.

k. A number of different SMS charging models are supported by this document.

l. The PPC service logic is responsible for maintaining associations of multipleSMDPP message transport transactions involved in a short message delivery fromoriginator to destination. An example would be the association of the SMDPPtransport of the short message from the originating MS (SME) to the MC, with theSMDPP transport of the short message from the MC to the destination MS (SME).

m. When the MS is not engaged in a voice or circuit-switched data call, PPC accountbalance notification may use SMS.

n. When the MS is engaged in a voice call, PPC for SMS activity may use theaccount balance notification mechanisms used for voice calls.

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

Assumptions 3 Introduction

o. When the MS is engaged in a circuit-switched data call, PPC for an SMS activitymay use the account balance notification mechanisms used for circuit-switcheddata calls.

p. The points in processing where an MC queries or notifies the PPC subscriber'sSCF for short message services can be provisioned in the FE on a per subscriberbasis.

q. This document does not specify any new capabilities (e.g., WIN triggers) thatsupport PPC for supplementary short message services.

r. Credit for PPC SMS messages discarded by the PPC service logic or by networkMC failure or congestion may be handled by post-processing to reconcile the PPCdebited funds. Details of this post-processing are outside the scope of thisdocument.

s. For circuit-switched data services, the MSC does not convey information aboutmid-call changes in the MS's service configuration to PPC service logic. Mid-callchanges may occur as a result of Service Negotiation or Intersystem Handoff.

t. For circuit-switched data services, the MSC does not convey information aboutData Privacy to the PPC service logic.

u. PPC service logic may require TDMA circuit-switched data rate information forcall rating. This document enhances the TDMAServiceCode parameter to enablethe MSC to specify the TDMA digital traffic channel data rate applicable atspecific points in call processing.

v. In this document, the use of the adjective “accepted” to describe service typeinformation means that the service type information was: a) filtered by theServing MSC to reflect its capabilities; b) reflects the result of negotiation ofservice configuration that may have occurred with the MS at the onset of the call;or c) both ‘a’ and ‘b’.

X.S0010-A

IS-826 Chapter 2 Modifications 4 Definitions and Concepts

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

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).

3 DEFINITIONS AND CONCEPTS

3.1 Definitions

(see IS-826, page 2-1)

Chargeable Event

A chargeable event is any event initiated either by the subscriber or by the network that mayresult in a decrease of the subscriber’s PPC account balance. A chargeable event may occurduring a voice, short message or circuit-switched data telecommunications service. Achargeable event has a beginning and an end, which are used to start and stop thecorresponding PPC invocation.

The remainder of this section is retained unchanged.

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 5 IS-826 Chapter 2 Modifications

5 WIRELESS INTELLIGENT NETWORK

FEATURE DESCRIPTIONS

5.A Pre-Paid Charging (PPC)

(see IS-826 page 1-2)

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 inreal time. The PPC subscriber may be notified about the account information at thebeginning, during, or at the end of the

voice

telecommunications service. When the accountbalance 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 subscriber’s use of

voice

telecommunications services may be de-authorized.

PPC may be activated for all telecommunication services

calls

or for a single voice orcircuit-switched data call

on a single call basis

. For “All-Services

Calls

” activation, chargesfor all

voice

telecommunications services invoked are applied to the PPC account. For“Single-Call” activation, only charges for voice or circuit-switched datatelecommunications services invoked in association with the call origination are applied tothe PPC account.

Applicability to Telecommunications Services

PPC is applicable to voice, short message and circuit-switched data telecommunicationsservices. For circuit-switched data telecommunications services, PPC is only applicable forthe 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.

X.S0010-A

IS-826 Chapter 2 Modifications 6 Pre-Paid Charging (PPC)

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

The authorization may have the following subscription options:

De- Authorization

PPC may be withdrawn at the subscriber’s 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-Services

Calls

” Activation, PPC isactivated upon authorization.

PPC may be activated by a Demand “All-Services

Calls

” Activation authorized subscriberby specifying a feature code, as in:

FC + .

If the activation is accepted, the system shall indicate success with feature confirmation

treatment

1

. If PPC is activated while a call or short message delivery is in progress, theactivation shall not affect the call or short message delivery in progress.

PPC may be activated by a Demand “Single-Call” Activation authorized subscriber byspecifying a feature code and a termination address:

FC + # + termination address + ; or

FC + termination address + .

Subscription Options Values

Single-Call Activation 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-Services

Calls

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.

Table 1 PPC Subscription Options

1. Feature confirmation treatment for circuit-switched data services may be limited to text notifications.

* SEND

* SEND

* SEND

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 (PPC) 7 IS-826 Chapter 2 Modifications

If the activation is accepted, the system shall indicate success with feature confirmation

treatment

1

. In this case PPC applies only to charges for voice or circuit-switched datatelecommunication 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-Services

Calls

” Activation authorizedsubscriber by specifying a feature code, as in:

FC0 + .

If the de-activation is accepted, the system shall indicate success with feature confirmation

treatment

1

. If PPC is de-activated while a call or short message delivery is in progress, thede-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 callattempt 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 andPUB service profiles do not have to be identical. For a subscriber who has both PPC andPUB 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 anytime 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 normalmanner when their account balance is above a threshold level. When PPC is invoked, thePPC account is decremented in real time. Telecommunication Voice telecommunicationservices may be charged to the PPC account at a flat rate, on invocation, or according tousage duration, type of service, or any combination thereof.

The PPC subscriber may be notified about the account information and charges associatedwith voice telecommunication services at the beginning, during and/or at the end of the voicetelecommunication services. Notification may be provided by tone announcement ordisplay text sent to the MS (e.g., SMS). Text notifications are sent to the MS for circuit-switched data services.

If PPC is active, the PPC account balance is above a threshold level, and Call Delivery isprovisioned, Call Delivery shall be supported.

* SEND

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 PPC is active, the PPC account balance is above a threshold level, and SMS isprovisioned, SMS shall be supported.

Final routing information is required by the PPC system before accurate charging can beapplied against the PPC account.

Normal operation when a threshold condition is reached during a voice call

If the PPC account balance reaches a threshold level while one or more voice calls are inprogress, 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. Ifthe subscriber is not engaged in one of the calls, the subscriber or the subscriber’sproxy (e.g., voice mail system, assistant, etc.) may be notified. The call continueswithout interruption.

• If the PPC subscriber is engaged in one of the calls, the subscriber is notifiedduring the call. If the subscriber is not engaged in one of the calls, the subscriberor the subscriber’s proxy may be notified. Every call that is not ended in a timelymanner is dropped.

If the PPC subscriber does not disconnect at the end of a call, the subscriber may beconnected to customer service or to an automatic system to enable the subscriber to refillthe account.

If the PPC account balance reaches a threshold level, the invocation of another chargeableservice may be denied.

Notification may be provided by tone, announcement, voice mail, SMS, etc. Notificationsare played only to the PPC subscriber or to the subscriber’s 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

If the PPC account balance reaches a threshold level while a circuit-switched data call is inprogress, 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 atimely manner.


Normal operation when a threshold condition is reached during short message delivery

If the PPC account balance reaches a threshold level while a short message delivery is inprogress, 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 withoutinterruption.

• A text notification is sent to the MS. The message is discarded without delivery.


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 tothe subscriber. If the subscriber originates a voice call, the network may route the call tocustomer service to help the subscriber to refill the account. Incoming calls may be giventhe subscriber inaccessible treatment and an appropriate notification may be provided to thePPC 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 tothe subscriber. If the subscriber originates a circuit-switched data call, the network maysend a text notification to the MS to help the subscriber refill the account and deny the callorigination. Incoming calls may be given subscriber inaccessible treatment and anappropriate notification may be provided to the PPC subscriber (e.g., special alerting, textmessage).

Normal operation with insufficient balance for SMS

If the PPC account balance is below a pre-set threshold, a notification shall be provided tothe subscriber. If the subscriber originates a short message, the message origination may bedenied and a text notification sent to the MS to help the subscriber refill the account. Forshort messages destined for the subscriber, the message may be discarded and a textnotification 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

– beginning: alerting, or called party answers,

– end: disconnect (network- or user-initiated), or connection failure (radio ornetwork), or abandon, or reject, or no answer

2. 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


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

– In cases where the invocation of services causes calls to be placed, these callsare chargeable events with the same beginning and end conditions asdescribed above. Additionally, the activation or the invocation of servicesmay be chargeable events.

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 endconditions as described above. Additionally, the activation or the invocationof wireless services may themselves be chargeable events.

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

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

7. Other charges associated with the PPC account (e.g., monthly fees, SMSsupplementary service usage.)

The chargeable events for “Single-Call” activation subscribers:

1. Call Voice call origination

– Same as “All-ServicesCalls” chargeable events

2. Services invoked on behalf of the PPC subscriber associated with the voice callorigination

– In cases where the invocation of wireless services causes calls to be placed,these calls are chargeable events subject to the same beginning and endconditions as those described above. Additionally, the activation or theinvocation of wireless services may themselves be chargeable events.

3. Other charges: same as “All-ServicesCalls” chargeable events

Call Detail Record

The system should record call detail information for the following:

a. PPC activation

b. PPC de-activation

c. PPC invocation

See DMH for the specific information to be included for each element.

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 forPUB, then PUB shall remain active and a notice to this effect may also be presented to thesubscriber.

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 callorigination, 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 notifications.2. The treatment for circuit-switched data services may be limited to text notifications.

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

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 isdenied.

If PPC cannot be invoked for a call to a PPC subscriber, subscriber inaccessible treatmentmay 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 normallyeven if the PPC subscriber’s account balance does not allow normal call origination andtermination.

Exceptions While Roaming

If a subscriber with PPC active roams into a system that does not support PPC, thefollowing services may be available to the subscriber:

1. Calls to home customer service or to local customer service.

2. Receive text notification SMS messages informing the subscriber that PPC isunavailable.

3. Receive announcements indicating PPC is unavailable.

4. Receive a notice to activate PUB if that service is authorized.

5. Activate PUB.

6. Calls to a single number specified by the home system (e.g., hot line).

7. Calls to locally allowed numbers (e.g., emergency service calls).

8. Credit card calls.

Exceptions During Intersystem Handoff

None identified.

5.A.3 Alternate Procedures

If the subscriber’s account balance is below the threshold, the subscriber may activate aPUB account to obtain service.

1. The treatment for circuit-switched data services may be limited to text notifications.

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 Forwarding—Busy (CFB)

PPC is invoked before CFB.

Call Forwarding—Default (CFD)

PPC is invoked before CFD.

Call Forwarding—No Answer (CFNA)

PPC is invoked before CFNA.

Call Forwarding—Unconditional (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.

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

Data Privacy (DP)

PPC is invoked before DP.

Not applicable.

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.

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.

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 thesubscriber’s preferred language. Text notifications related to PPC shall be sent to the MSin the subscriber’s 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.

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

Voice Message Retrieval (VMR)

PPC is invoked before VMR.

Voice Privacy (VP)

PPC is invoked before VP.

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

Symbols and Abbreviations IS-826 Chapter 3 Modifications17

IS-826 CHAPTER 3 MODIFICATIONSThis section provides additions and modifications to IS-826 Chapter 3, Modifications toTIA/EIA-41.1-D Functional Overview, required to support circuit-switched data and shortmessage services.

4 SYMBOLS AND ABBREVIATIONS(See TIA/EIA-41, page 1-14)

(See IS-771, page 3-8)(See IS-826, page 3-9)

RESUMEPIC ResumePIC parameter

SM_ANLYZD ShortMessageAnalyzed INVOKE

sm_anlyzd ShortMessageAnalyzed RETURN RESULT

SMS_BRLEN SMS_BearerLength parameter

SMS_BILLID SMS_BillingID parameter

SMS_EVENT SMS_Event parameter

SMS_EVENTNOT SMS_EventNotification parameter

SMS_PMCNT SMS_PendingMessageCount parameter

The omitted portion of this section is retained without modification.

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

Network Reference Model18

5 NETWORK REFERENCE MODEL

5.X Network Reference Model for Pre-Paid Charging Enhancements

(New Section for TIA/EIA-41.1-D, section 5)

The network reference model for Pre-Paid Charging enhancements for short messageservices is shown below:

5.X.1 Interface Reference Points

An interface exists when two Network Entities are interconnected through exactly oneReference Point.

5.X.1.1 Reference Point M 4

Reference point M4 is the interface between the MC and the SCP.

Figure X Network Reference Model for Pre-Paid Charging Enhancements

Q

M1M2

T2

SME

MC HLR

SCP

M4T1

MSC

M3

N

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

Network Reference Model for Pre-Paid Charging Enhancements

IS-826 Chapter 3 Modifications19

5.X.2 Messages Across Network Interfaces

This section describes the protocols and messages used across network interfaces for Pre-Paid Charging Enhancements for short message services.

Table X Message Interfaces

Network Interface Network Entity Protocol Operations

M4 MC – SCP TIA/EIA-41 ShortMessageAnalyzed

X.S0010-A

IS-826 Chapter 4 Modifications 20 Wireless Intelligent Network (WIN Scenarios

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

IS-826 CHAPTER 4 MODIFICATIONSThis section provides additions and modifications to IS-826 Chapter 4, Modifications toTIA/EIA-41.3-D to Automatic Roaming Information Flows, required to support circuit-switched data and short message services.

8 WIRELESS INTELLIGENT NETWORK (WIN SCENARIOS

8.8 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 responsefrom service logic to an SSF/CCF (i.e., MSC).

a. An armed trigger is encountered at the SSF/CCF (e.g., Originating or Terminating MSC). Thecriteria for the trigger are satisfied and the appropriate query (e.g., LOCREQ, TBUSY) is sent to theservice control function (SCF) per the address information associated with the trigger. Theresponse timer for the operation is started.

b. Other protocol data units (PDUs) may be exchanged according to the needs of the service logicprogram (SLP) at the SCF.

c. The RETURN RESULT for the operation invoked at Step-a is sent to the SSF/CCF and includes aRESUMEPIC parameter. The SSF/CCF examines the received information, and if it iscompatible with the current state of call processing, the SSF/CCF resumes call processing at theresumption point indicated by the RESUMEPIC parameter.

Note: If the RESUMEPIC parameter is not included in the RETURN RESULT, the SSF/CCFcontinues call processing where pre-WIN procedures would continue.

Figure 8.8 Call Processing Resumption Point

Originating or Serving System

TIMER

SCF

win_operation [Parameters, RESUMEPIC]

WIN_OPERATION [Parameter Set]

SSF/CCF

Other PDUs as applicable

a

b

c

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

WIN Pre-Paid Charging Scenarios 21 IS-826 Chapter 4 Modifications

8.X WIN Pre-Paid Charging Scenarios

8.X.1 MS Registration(See IS-826 Chapter 4, page 4-2)

This scenario describes MS registration in a new serving system by a PPC subscriber withPPC active and an account balance above threshold. The subscriber’s service profileindicates the circuit-switched data services (and other subscriber services) that areapplicable for the MS.

a. The Serving MSC determines that a roaming MS is within its service area. The ServingMSC sends a REGNOT to its VLR requesting subscriber profile and authorizationinformation. The TRANSCAP parameter is set to indicate the Serving MSC can processthe TRIGADDRLIST parameter. The WINCAP parameter is set to indicate the WINcapabilities of the Serving MSC.

b. The Serving VLR determines the MS is not known to the VLR. The Serving VLRforwards the REGNOT to the HLR associated with the MS.

c. The HLR determines that authorization can be granted to the MS. It returns therequested information to the Serving VLR in the regnot. The TRIGADDRLISTparameter is set to indicate the Origination_Attempt_Authorized,Calling_Routing_Address_Available, O_Answer, O_Disconnect, T_Answer, andT_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

Figure 1 MS Registration

Parameters Usage Type

MSCID Serving MSC MSCID. R

MSID Served MS MSID. R

ESN Served MS ESN. R

TRANSCAP Serving MSC’s transaction capability. R

WINCAP Serving MSC’s WIN capability. R

QUALCODE Type of qualification information required. R

Serving

a

b

c

d

regnot [Profile {TRIGADDRLIST}]

REGNOT [MSCID, MSID, ESN, TRANSCAP, WINCAP, QUALCODE]

MSCHLR VLR

REGNOT [MSCID, MSID, ESN, TRANSCAP, WINCAP, QUALCODE]

RNT RNT

regnot [Profile {TRIGADDRLIST}]

X.S0010-A

IS-826 Chapter 4 Modifications 22 WIN Pre-Paid Charging Scenarios

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

CDMAServiceOptionsList parameter indicates the authorized service options for aCDMA MS; the TDMADataFeaturesIndicator parameter indicates the allowed dataservices 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.

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)(See IS-826 Chapter 4, page 4-3)

This scenario describes PPC invocation upon call origination by a PPC subscriber with PPCactive and an account balance above threshold. The calling MS disconnects first and no endof call announcement is provided to the subscriber.

• • •

d. The Serving MSC analyzes the dialed digits and prepares to route the call. The MSCdetects the Calling_Routing_Address_Available trigger and sends an ANLYZD to theSN associated with this trigger.




MDN Mobile directory number. Include if available. O

BILLID BillingID. Used to relate queries for this call. R

DGTSDIAL Digits entered by served MS. R O

RoutingInfo: Call routing information:

[DSTDGTS] DestinationDigits. The network address of thedestination.

R

[CARDGTS] CarrierDigits. Interexchange carrier for call setup.Include if applicable.

O

[ROUTDGTS] RoutingDigits. Special routing instructions. Includeif applicable.

O

TRIGTYPE Indicates the trigger encountered. R

TOD TimeOfDay. The current time (UTC). R

TDO TimeDateOffset. The time offset of local civil time. R


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.3 MS Call Origination: Calling Party Disconnect(See IS-826 Chapter 4, page 4-6)

This scenario describes PPC invocation upon call origination by a PPC subscriber with PPCactive and an account balance above threshold. The calling party disconnects first, henceno end of call announcement is provided.

• • •

d. The Serving MSC analyzes the dialed digits and prepares to route the call. The MSCdetects the Calling_Routing_Address_Available trigger and sends an ANLYZD to theSCP associated with this trigger.











R


O


O





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

(See IS-826 Chapter 4, page 4-11)

This scenario differs from the previous scenario in that no announcement is played whenan MS originates the call to inform the subscriber of their current account balance. Thecalling 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 MSCdetects the Calling_Routing_Address_Available trigger and sends an ANLYZD to theSCP associated with this trigger.











R


O


O





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.10 Three-Way Calling: Calling Party Disconnect(See IS-826 Chapter 4, page 4-23)

This scenario describes PPC invocation for a Three-Way call. The calling party disconnectsbefore 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 thirdparty. The MSC detects the Calling_Routing_Address_Available trigger and sends anANLYZD to the SCP associated with this trigger.











R


O


O


FEATIND FeatureIndicator. Indicates the feature invoked withthe call (e.g., Three-Way Calling).

R




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(See IS-826 Chapter 4, page 4-34)

This scenario describes PPC invocation for a Three-Way call with an insufficient balancefor the third-party call.

• • •

x. The Serving MSC analyzes the dialed digits and prepares to route the call to the thirdparty. The MSC detects the Calling_Routing_Address_Available trigger and sends anANLYZD to the SCP associated with this trigger.











R


O


O


FEATIND FeatureIndicator. Indicates the feature invoked withthe call (e.g., Three-Way Calling).

R




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.16 MS Call Origination with Abbreviated Dialing(See IS-826 Chapter 4, page 4-41)

This scenario describes PPC invocation for an MS call origination with a WIN-basedabbreviated dialing service. The subscriber enters # and the abbreviated dialing number asin:

• • •

h. The Serving MSC prepares to route the call. The MSC detects theCalling_Routing_Address_Available trigger and sends an ANLYZD to SCP-1, the SCPassociated with this trigger.










R


O


O





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(See IS-826 Chapter 4, page 4-49)

This scenario describes PPC invocation for an MS call origination with a WIN-basedabbreviated dialing service. Due to an insufficient balance, the call is disconnected.

• • •

h. The Serving MSC prepares to route the call. The MSC detects theCalling_Routing_Address_Available trigger and sends an ANLYZD to SCP-1, the SCPassociated with this trigger.










R


O


O





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.20 Call Origination: Charge Rate Dependent on MS Location(See IS-826 Chapter 4, page 4-52)

This scenario describes PPC invocation upon call origination by a PPC subscriber with PPCactive and an account balance above threshold. The rate of charging for the call isdependent on the location of the MS.

• • •











R


O


O




SCELLID ID of the cell serving the MS. R

LOCID Location Area ID. Include if available. O


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(See IS-826 Chapter 4, page 4-88)

This scenario describes an MS-to-MS call. Both users are PPC subscribers of the samesystem. Both subscribers are currently in the home service area.

• • •












R


O


O




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 Circuit-Switched Data Services(new for IS-826 Chapter 4, Section 8.X)

The scenarios in this section depict interactions between network entities in situationsrelated to PPC support of circuit-switched data services (ADS and G3 FAX) underautomatic 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 andTwo-Stage Dialing.

PPC is not applicable to other types of ADS and G3 FAX.

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 aPPC subscriber with PPC active and an account balance above threshold. The call isinitially authorized by the PPC service platform. The PPC platform is notified prior to callsetup to enable the current account balance to be sent to the MS. The called partydisconnects first.

a. An MS circuit-switched data call origination with dialed digits is received by theServing MSC.

b. The Serving MSC detects the Origination_Attempt_Authorized trigger and sends anORREQ to the network entity (SCP) associated with this trigger.

Figure 2 MS Circuit-Switched Data Call Origination: Called Party Disconnect




MS origination

orreq [DMH_SVCID]

ORREQ [MSCID, MSID, MDN, ServiceType, BILLID, DGTSDIAL, TRIGTYPE]

ORT

Serving

a

b

c

d

e

f

g

h

i

MSC

IWFSCP

call setup

answer

OANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO]

answer

disconnect

MS release

ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]

ODT

j

k

odisconnect [ ]

ANLYZD [MSCID, MSID, MDN, BILLID, DGTSDIAL, ServiceType, RoutingInfo, TRIGTYPE, TOD, TDO]

anlyzd [DISPTEXT, ACTCODE] ANZT

display text

l

m

n

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. The SCP determines the subscriber is authorized for the requested data service and hasPPC active. The subscriber’s account balance is above the threshold level. The SCPsends an orreq to the Serving MSC to indicate call processing shall continue. TheDMH_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 MSCdetects the Calling_Routing_Address_Available trigger and sends an ANLYZD to thenetwork entity (SCP) associated with this trigger.


ServiceType: The service type for the call: R

[CDMAServiceOption] Indicates the requested CDMA service option forthe call (e.g., ADS, G3Fax).

O

[TDMAServiceCode] Indicates the requested TDMA service code for thecall.

O


DGTSDIAL Digits entered by served MS. R







DGTSDIAL Dialed digits. R


[CDMAServiceOption] Indicates the current CDMA service option for thecall (e.g., ADS, G3Fax).

O

[TDMAServiceCode] Indicates the current TDMA service code for thecall.

O



R


O


O





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 toindicate the current account balance. The ACTCODE parameter is set to indicate thatdisplay 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 networkentity associated with this trigger.

Upon receipt of the OANSWER, the SCP begins decrementing the subscriber’s accountbalance.

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 thenetwork entity associated with this trigger.

Upon receipt of the ODISCONNECT, the SCP stops decrementing the subscriber’saccount balance.

m. The SCP sends an empty odisconnect to the Serving MSC.

n. The Serving MSC releases the MS.















RELCAUSE Call release cause. R



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.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 aPPC subscriber with PPC active and an account balance above threshold. The MS isnotified of a low-account balance during the call. The MS disconnects.

a. An MS circuit-switched data call origination with dialed digits is received by the ServingMSC.

Figure 3 MS Circuit-Switched Data Call Origination: Mid-Call Notification of Low Balance

MS origination

orreq [DMH_SVCID]


ORT

Serving

a

b

c

d

e

f

g

h

i

MSC

IWFSCP

call setup

answer


answer

MS disconnect

call release


ODT

j

k

l

m

display text

n

odisconnect [ ]

CCDIR [MSCID, MSID, BILLID, DISPTEXT]

display textCCDT

ccdir [ ]

o

p

q



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








MDN Served MS MDN. Include if available. O



O


O












O


O



R


O


O

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








k. The subscriber’s account balance reaches a threshold level and the SCP sends a CCDIRto 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 thenetwork entity associated with this trigger.


















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



p. The SCP sends an empty odisconnect to the Serving MSC.

q. The Serving MSC releases the call.






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.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 aPPC subscriber with service logic directed call release.

Figure 4 MS Circuit-Switched Data Call Origination: Service Logic Directed Call Release

MS origination

orreq [DMH_SVCID]


ORT

Serving

a

b

c

d

e

f

g

h

i

MSC

IWFSCP

call setup

answer


answer

call release

call release


ODT

j

k

l

m

display text

n

odisconnect [ ]

CCDIR [MSCID, MSID, BILLID, DISPTEXT]

display textCCDT

ccdir [ ]

o

p

q



display text

CCDT

ccdir [ ]

r

s

t

CCDIR [MSCID, MSID, BILLID, DISPTEXT, ACTCODE]

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 theServing MSC.










O


O












O


O

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








k. The subscriber’s account balance reaches a threshold level and the SCP sends a CCDIRto 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 programinstance timer expires). The SCP sends a CCDIR to the Serving MSC. The DISPTEXTparameter is set to notify the user of the disconnect. The ACTCODE parameter is set toindicate that the call shall be disconnected.



R


O


O













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 thenetwork entity associated with this trigger.

s. The SCP sends an empty odisconnect to the Serving MSC.

t. The Serving MSC releases the MS.










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.4 Circuit-Switched Data Call Delivery: Intersystem Termination

This scenario describes PPC invocation upon circuit-switched data Call Delivery withintersystem termination.

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., directorynumber) are received by the Originating MSC.

Figure 5 Circuit-Switched Data Call Delivery: Intersystem Termination

call origination

locreq [MSCID, MIN, IMSI, ServiceType, TRIGADDRLIST]

LOCREQ [MSCID, BILLID, DGTSDIAL, ServiceType, TRIGTYPE, TRANSCAP, WINCAP]

anlyzd [DMH_SVCID]

ROUTREQ [MSCID, MSID, BILLID, ServiceType]

locreq [MSCID, MIN, IMSI, TERMLIST, REDIND, ServiceType]

ANLYZD [MSCID, BILLID, DGTSDIAL, MSID, ServiceType, TRIGTYPE]

TDT

LRT

Serving

VLR MSCHLR

a

b

c

d

e

f

g

h

i

Originating System

MSC

ANZT

LRT


RRT RRT


routreq [TLDN, ServiceType]

ANZT

ANLYZD [MSCID, MSID, BILLID, DGTSDIAL, RoutingInfo, REDIND, TRIGTYPE, ServiceType, TOD, TDO]

anlyzd [ ]

call setup

j

k

l

m

n

o

p

q

r

s

t

u

TANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, ServiceType, TOD, TDO]

MS answer

cut through

call release

TDISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]

tdisconnect [DMH_SVCID]

MS disconnect

PPC

SCP


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 Originating MSC detects the Mobile_Termination trigger and sends a LOCREQ tothe HLR associated with the MS; this association is made through the dialed MSaddress digits (which may not be the MSID). The TRANSCAP parameter is set toindicate the MSC can process the TRIGADDRLIST parameter. The WINCAPparameter indicates the triggers supported by the MSC. The TRIGTYPE parameter isset to indicate the Mobile_Termination trigger was encountered. The ServiceTypeinformation is set to indicate the requested service type for the call.

c. The HLR sends the locreq to the Originating MSC with the TRIGADDRLISTparameter set to indicate the Initial_Termination, Location andCalled_Routing_Address_Available triggers shall be armed.

d. The Originating MSC detects the Initial_Termination trigger and sends an ANLYZD tothe SCP indicated in the TRIGADDRLIST parameter. The TRIGTYPE parameter is setto indicate the Initial_Termination trigger was detected.


MSCID Originating MSC’s MSCID. R

BILLID BillingID assigned by the Originating MSC for thiscall.

R

DGTSDIAL Dialed MS address digits. R

ServiceType: The service type for the call: O


O


O


TRANSCAP Originating MSC’s transaction capability. R

WINCAP Originating MSC’s WIN capability. R



MIN Called MS MIN. R

IMSI Called MS IMSI. Include if available. O



O


O

TRIGADDRLIST WIN Triggers to arm for this call leg. R




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 determines the called subscriber has PPC active and that the account balance isabove the threshold level. The SCP sends an anlyzd to the Originating MSC. TheDMH_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-switcheddata 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 andreturns the TLDN to the VLR in the routreq. The ServiceType information is set toindicate 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 thecircuit-switched data call to the subscriber.


MSID Called MS MSID. R


[CDMAServiceOption] Indicates the requested CDMA service option forthe call (e.g., ADS, G3Fax). O

[TDMAServiceCode] Indicates the requested TDMA service code for thecall. O






REDIND DMH_RedirectionIndicator. Reason for extending theincoming call.

R

TERMLIST Call termination information. R


[CDMAServiceOption] Indicates the accepted CDMA service option for thecall (e.g., ADS, G3Fax).

O

[TDMAServiceCode] Indicates the accepted TDMA service code for thecall.

O


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 theCalled_Routing_Address_Available trigger. The Originating MSC sends an ANLYZD tothe SCP associated with this trigger.

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 SCPassociated with this trigger.








R


O


O


R




O


O









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


Note, the Service Type information reflects any service configuration negotiation thatmay 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 theSCP associated with this trigger.

Upon receipt of the TDISCONNECT, the SCP stops decrementing the subscriber’saccount balance.

t. The SCP sends a tdisconnect to the Serving MSC. The DMH_SVCID parameter isset to indicate PPC was invoked.

u. The Serving MSC releases the call.



O


O













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.5 SCP-Based Call Forwarding Busy on Call Collision

This scenario describes PPC interaction with SCP-based call forwarding on a busycondition encountered after circuit-switched data call delivery.

Figure 6 SCP-Based Call Forwarding Busy on Call Collision (1 of 2)

call origination



anlyzd [DMH_SVCID]


locreq [MSCID, MIN, IMSI, TERMLIST, REDIND, ServiceType]

ANLYZD [MSCID, BILLID, DGTSDIAL, MSID, TRIGTYPE, ServiceType]

LRT

PPC Serving

a

b

c

d

e

f

g

h

i

Originating System

ANZT

LRT


RRT RRT



ANZT

ANLYZD [MSCID, MSID, MDN, BILLID, DGTSDIAL, RoutingInfo, REDIND, TRIGTYPE, ServiceType, TOD, TDO]

anlyzd [ ]

call setup

j

k

l

m

n

o

p

q

r

s

t

u

REDREQ [MSCID, MSID, BILLID, REDREASON, ServiceType]

MS busy

CF

RRT

call release

SCP VLR MSCHLRMSC SCP

TBUSY [MSCID, MSID, BILLID, TRIGTYPE, ServiceType]

TBT

tbusy [REDIND, TERMLIST, TRIGADDRLIST]

SIM Interaction

redreq [ ]


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. The HLR sends the locreq to the Originating MSC with the TRIGADDRLISTparameter set to indicate the Initial_Termination, Location, T_Busy, T_No_Answer andCalled_Routing_Address_Available triggers shall be armed.





R




O


O










O


O




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. 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-switcheddata service.


i. The Serving MSC allocates a TLDN for the circuit-switched data call to the MS andreturns the TLDN to the VLR in the routreq. The ServiceType information is set toindicate the accepted circuit-switched service type.


k. The HLR sends the locreq to the Originating MSC with instructions to set up thecircuit-switched data call to the subscriber.






O


O







R



[CDMAServiceOption] Indicates the accepted CDMA service option for thecall (e.g., ADS, G3Fax).

O

[TDMAServiceCode] Indicates the accepted TDMA service code for thecall.

O


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 theCalled_Routing_Address_Available trigger. The Originating MSC sends an ANLYZD tothe SCP associated with this trigger.

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.




MDN Called MS MDN. O





R


O


O


R




O


O





MSID Serve MS MSID. R

BILLID Call ID to reference BillingID of the OriginatingMSC.

R

REDREASON Identifies reason for the redirection request(i.e., busy).

R

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. 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 SCPassociated with this trigger. The ServiceType information is set to indicate the currentcircuit-switched service type.

t. The SCP may send a query (e.g., SERVREQ, SEARCH) to a SIM on another servicelogic network entity to determine which, if any, triggers should be armed for theforwarded call.

u. The service logic determines the call should be forwarded. The SCP sends a tbusy tothe MSC. In this scenario, the TERMLIST parameter indicates call forwarding to thePSTN. The TRIGADDRLIST parameter is included to arm triggers for the forwardedcall (e.g., Calling_Routing_Address_Available, O_Answer, O_Disconnect).



O


O




R

TRIGADDRLIST Indicates WIN triggers for the forwarded call leg. R


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


v. The Serving MSC analyzes the routing information and prepares to route the call. TheMSC detects the Calling_Routing_Address_Available trigger and sends an ANLYZD tothe SCP associated with this trigger.

Figure 7 SCP-Based Call Forwarding Busy on Call Collision (2 of 2)







R


O


O


R


anlyzd [DMH_SVCID]

OANSWER [MSCID, MSID, BILLID, TRIGTYPE, TOD, TDO]

ANLYZD [MSCID, MSID, BILLID, RoutingInfo, REDIND, TRIGTYPE, ServiceType, TOD, TDO]

PPC Serving

aa

Originating System

ANZT

odisconnect [ ]

CF

v

w

x

y

z

ab

ac

ad

ae

call forward setup

answer

cut-through

disconnect

ODISCONNECT [MSCID, MSID, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]

ODT

call release


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

w. The SCP sends an anlyzd to the MSC. The DMH_SVCID parameter is set to indicatePPC 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 SCPassociated with this trigger.

aa. The call is cut through and connected.

ab. The MSC receives a disconnect indication for the terminating party. The MSC releasesthe call leg toward the terminating party.

ac. The Originating MSC detects the O_Disconnect trigger and sends an ODISCONNECTto the SCP associated with this trigger.


ad. The SCP sends an empty odisconnect to the Originating MSC.

ae. The MSC releases the call leg to the calling party.



O


O




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.


Figure 8 SCP-Based Call Forwarding Busy on Circuit-Switched Data Call (1 of 2)

call origination



anlyzd [DMH_SVCID]


locreq [MSCID, MIN, IMSI, ACCDEN=Busy]

ANLYZD [MSCID, BILLID, DGTSDIAL, MSID, ServiceType, TRIGTYPE]

LRT

PPC Serving

a

b

c

d

e

f

g

h

i

Originating System

ANZT

LRT


RRTRRT


routreq [ACCDEN=Busy]

ANZT

call forward setup

j

k

l

m

n

o

p

q

r

s

t

CF


tbusy [REDIND, TERMLIST, TRIGADDRLIST]

TBUSY [MSCID, MSID, BILLID, TRIGTYPE, ServiceType]

TBT SIM Interaction

anlyzd [DMH_SVCID]

ANLYZD [MSCID, MSID, MDN, BILLID, RoutingInfo, REDIND, TRIGTYPE, ServiceType, TOD, TDO]

answer


cut-through

routreq [ACCDEN=Busy]

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. The HLR sends the locreq to the Originating MSC with the TRIGADDRLISTparameter set to indicate the Initial_Termination, Location,Called_Routing_Address_Available, T_Busy and T_No_Answer triggers shall be armed.





R




O


O










O


O





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. 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.


i. The MS is engaged in a call and Call Waiting is not applicable. The Serving MSC sendsa routreq to the VLR with the ACCDEN parameter set to indicate Busy.


k. HLR-based call forwarding is not applicable. The HLR sends the locreq to theOriginating MSC and relays the received ACCDEN parameter.

l. The Originating MSC detects the T_Busy trigger and sends a TBUSY to the SCPassociated with this trigger. The ServiceType is set to indicate the requested servicetype for the call.

m. The SCP may send a query (e.g., SERVREQ, SEARCH) to a SIM on another servicelogic network entity to determine which, if any, triggers should be armed for theforwarded call.

n. The service logic determines the call should be forwarded. The SCP sends a tbusy tothe MSC. In this scenario, the TERMLIST parameter indicates call forwarding to thePSTN. The TRIGADDRLIST parameter is included to arm triggers for the forwardedcall (e.g., Calling_Routing_Address_Available, O_Answer, O_Disconnect).





O


O





R

TRIGADDRLIST Indicates WIN triggers for the forwarded call leg. R


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 analyzes the routing information and prepares to route the call. TheMSC detects the Calling_Routing_Address_Available trigger and sends an ANLYZD tothe SCP associated with this trigger.

p. The SCP sends an anlyzd to the MSC. The DMH_SVCID parameter is set to indicatePPC 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 SCPassociated with this trigger.

t. The call is cut through and connected.




MDN Called MS MDN. R




R


O


O


R




O


O



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


u. The MSC receives a disconnect indication for the terminating party. The MSC releasesthe call leg toward the terminating party.

v. The Originating MSC detects the O_Disconnect trigger and sends an ODISCONNECTto the SCP associated with this trigger.


w. The SCP sends an empty odisconnect to the Originating MSC.

x. The MSC releases the call leg to the calling party.

Figure 9 SCP-Based Call Forwarding Busy on Circuit-Switched Data Call (2 of 2)

PPC ServingOriginating System

odisconnect [ ]

CF

u

v

w

x

disconnect


ODT

call release


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 Short Message Services(new for IS-826 Chapter 4, Section 8.X)

The scenarios in this section depict interactions between network entities in situationsrelated 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 inthis section:

SMD-REQUEST An implementation dependent air interface message for a shortmessage delivery request.

SMD-ACK An implementation dependent air interface message for a shortmessage delivery positive acknowledgment.

SMD-NAK An implementation dependent air interface message for a shortmessage delivery negative acknowledgment.

{A} The address of SME A.

{A ⇒ A’s MC} The address of SME A implying the address of SME A’s homeMC.

{A’s MSC} The address of the MSC serving MS-based SME A.

{B} The address of SME B.

{B ⇒ B’s MC} The address of SME B implying the address of SME B’s homeMC.

{B’s MSC} The address of the MSC serving MS-based SME B.

ACK ([ACK]) Absence of cause code.

NACK ([NACK=cause code]) Presence of a cause code.

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. The MS-based SME formulates and sends an air interface SMD-REQUEST to theserving MSC.

b. The serving MSC converts the SMD-REQUEST into an SMDPP and forwards it towardthe subscriber’s home MC as indicated by subscriber’s service profile.

Figure 10 PPC for MS-Originated Short Message Accepted by the Network


SMS_OriginalDestination-Address

Network address of the destination SME (i.e., {B}). R

SMS_OriginalOriginating-Address

Network address of the originating SME (i.e., {A}). R

SMS_TeleserviceIdentifier Identification of the teleservice, used for interpretingthe SMS_BearerData.

R

SMS_BearerData Any desired message. R

SMS_DestinationAddress Network address of the originating SME’s MC(i.e., {A⇒ A’s MC}).

O


MSID MSID of originating MS-based SME. O

ESN ESN of originating MS-based SME. O

SMDPP

SMD-REQ

SM_ANLYZD

SMT

Serving

MCMSC

a

b

c

d

e

f

g

h

Originator

SAOT

MSSME

A

Home

PPCSCP

B

SMD-ACK

sm_anlyzd [ACK]

smdpp [ACK]

SMDPP

SMT smdpp

SMAT

Destination

SME

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. The MS’s home MC prepares to accept the short message and determines that theoriginal originator is provisioned and configured for PPC of MS-originated shortmessages. The MC sends an SM_ANLYZD to the PPC SCP for the subscriber.

SMS_ChargeIndicator Charging options for SMS message. Include ifreceived.

O

SMS_MessageCount Number of SMS messages pending delivery. Includeif applicable.

O

SMS_NotificationIndicator Used to control sending of subsequent SMSnotification messages.

O



SMS_OriginalDestination-SubAddress

Subaddress of the destination SME. Include ifapplicable.

O



SMS_OriginalOriginating-SubAddress

Subaddress of the originating SME. Include ifapplicable.

O


R

SMS_BearerData Message received from MS-based SME. R

SMS_DestinationAddress Network address of the originating SME’s MC(i.e., {A⇒ A’s MC}.

R

SMS_OriginatingAddress Network address of the originating SME’s MSC(i.e., {A’s MSC}.

O


SMS_Event Type of SMS event encountered (i.e., MS-originatedshort message accepted by network).

R

TOD TimeOfDay of the event for the originator’s home MC R

TDO TimeDateOffset of the event for the originator’s homeMC.

R


R

SMS_BearerLength Length of the original SMS bearer data received fromthe MS-based SME.

R

SMS_PendingMessageCount Number of short messages in the MC that are pendingdelivery to and from this MS-based SME.

O

MSID MSID of originating MS-based SME. R


MDN MDN of originating MS-based SME O


O


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


d. The SCP updates the subscriber’s account balance sends an sm_anlyzd to the MC.

e. The originator’s home MC accepts the short message and returns an smdpp to theOriginating MSC. The MC optionally generates an SMS data record containing thereceived DMH_SVCID parameter value.

f. The MSC converts the smdpp into an air interface SMD-ACK message. The MS-basedSME correlates the response with the original request.

g. The originator’s home MC stores the messages and possibly waits until further deliveryactions are taken. The originator’s home MC may also remove the short message beforedelivery for any other reasons.

The originator’s home MC forwards the SMDPP towards the destination SME. Theparameters are as in Step-b.

h. The destination SME responds by returning an smdpp to the originator’s home MC.

SMS_DestinationAddress Network address of the originating SME’s MC(i.e., {A⇒ A’s MC}.

R




Include if received and applicable. O





SMS_OriginatingAddress Network address of the originating SME’s MSC(i.e., {A’s MSC}).

O

SMS_BillingID MC’s generated Billing Identifier for this shortmessage.

R


SMS_BearerData Include to indicate the cost of the deduction andupdated account balance. Used by the MC tonotify the PPC end-user {A}.

O

DMH_SVCID Include to identify the service that was invoked forthis short message.

O


SMS_BearerData Include if received in Step-d. O


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.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 theshort message is successfully delivered to the destination SME.

a-c. Same as Scenario 8.X.42.1, Steps a-c.

d. The PPC SCP updates the subscriber’s account balance. The PPC SCP determines thatthis subscriber is to be charged for further processing of this short message service andincludes the SMS_EventNotification parameter in the sm_anlyzd sent to the homeMC. The SMS_EventNotification parameter is set to indicate the events that shall bereported to the PPC SCP. In this scenario, the SMS_EventNotification is set to indicateMS-originated short message delivery attempt towards destination, Successful MS-originated short message delivery towards destination, Unsuccessful MS-originatedshort message delivery towards destination, and MS-originated short message purgedby MC.

Figure 11 PPC for MS-Originated Short Message Delivered to Destination SME


SMS_EventNotification The SMS events to be reported for this particular shortmessage delivery.

R

SMDPP

SMD-REQ

SM_ANLYZD

SMT

Serving

MCMSC

a

b

c

d

e

f

g

h

i

Originator

SAOT

j

k

l

MSSME

A

Home

PPCSCP

B

SMD-ACK

sm_anlyzd [ACK]

smdpp [ACK]

SMDPP

SMT smdpp [ACK]

Destination

SME

SMAT

SMAT sm_anlyzd [ACK]

SMAT sm_anlyzd [ACK]

SM_ANLYZD

SM_ANLYZD

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. Same as Scenario 8.X.42.1, Steps e-f.

g. The subscriber’s 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 anSM_ANLYZD to the PPC SCP. The SMS_Event parameter is set to indicate MS-originated short message delivery attempt towards destination.

SMS_BearerData Include to indicate the cost of the deduction andupdated account balance. Used by the MC tonotify the PPC end-user {A}.

O

DMH_SVCID Include to identify the service that was invoked forthis short message.

O


SMS_Event Type of SMS event encountered. R



R


R


R

SMS_PendingMessageCount Number of short messages in the MC that are pendingdelivery to and from the MS-based SME.

O





O

SMS_DestinationAddress Network address of the originating SME’s MC(i.e., {B⇒ B’s MC}.

O









SMS_OriginatingAddress Network address of the originating SME’s MC(i.e., {A⇒ A’s MC}).

R

SMS_BillingID Billing Identifier originally assigned by MC for thisshort message.

R


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. The PPC SCP verifies that the PPC subscriber’s account balance is sufficient andreserves a deduction from the PPC subscriber’s account for the cost of this chargeableevent. The SCP sends an sm_anlyzd to the subscriber’s home MC.

i. The home MC sends an SMDPP to the destination MC with the short message receivedfrom 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 anSM_ANLYZD to the PPC SCP. The SMS_Event parameter is set to indicate SuccessfulMS-originated short message delivery towards destination.


SMS_BearerData Include to indicate the deduction and the updatedaccount balance. Used by the MC to notify thePPC end-user {A}.

O

DMH_SVCID Include to identify the service that was invoked. O





R


R


R


O





O


O










R

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 PPC SCP commits the deduction that has been reserved in the PPC subscriber’saccount balance. The SCP sends an sm_anlyzd to the subscriber’s home MC.


R


SMS_BearerData Include to indicate the deduction and the updatedaccount balance. Used by the MC to notify thePPC end-user {A}.

O



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.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.

a-c. Same as Section 8.X.42.1, Steps a-c.

d. The PPC SCP examines the subscriber’s account balance. In this scenario, the PPCsubscriber’s account balance is not sufficient for this chargeable event. The PPC SCPsends an sm_anlyzd to the originator’s home MC indicating the SMS origination isdenied.

e. The subscriber’s home MC rejects the short message and returns an smdpp to theOriginating MSC.

f. The MSC converts the smdpp into an air interface SMD-NACK message. The MS-based SME correlates the response with the original request and informs the end-user ofthe rejection.

Figure 12 PPC for MS-Originated Short Message Not Accepted by the Network


SMS_CauseCode Indicating “Service denied”. R

SMS_BearerData Include to indicate the account balance information.Used by the MC to notify the PPC subscriber {A}.

O

DMH_SVCID Include to identify the service that was invoked for theshort message origination.

O


SMS_CauseCode Indicating “SMS Origination Denied”. R

SMS_BearerData Include if applicable or if received at Step-d. O

SMDPP

SMD-REQ

SM_ANLYZD

SMT

Serving

MCMSC

a

b

c

d

e

f

Originator

SAOT

MSSME

A

Home

PPCSCP

B

SMD-NACK

sm_anlyzd [NACK]

smdpp [NACK]

SMAT

Destination

SME

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 byDestination SME

This scenario illustrates PPC invocation for an MS-originated short message. The PPCaccount is updated when the network accepts the short message and when the networkattempts to deliver the short message to the destination SME. The destination SME doesnot accept the short message.

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 anegative acknowledgement.

k. The MC determines that an SMS notification event is applicable. The MC sends anSM_ANLYZD to the PPC SCP. The SMS_Event parameter is set to indicateUnsuccessful MS-originated short message delivery towards destination.

Figure 13 PPC for MS-Originated Short Message: Message Not Accepted by Destination SME



SMDPP

SMD-REQ

SM_ANLYZD

SMT

Serving

MCMSC

a

b

c

d

e

f

g

h

i

Originator

SAOT

j

k

l

MSSME

A

Home

PPCSCP

B

SMD-ACK

sm_anlyzd [ACK]

smdpp [ACK]

SMDPP

SMT smdpp [NACK]

Destination

SME

SMAT

SMAT

SMAT

SM_ANLYZD

SM_ANLYZD

sm_anlyzd [ACK]

sm_anlyzd [ACK]

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 PPC SCP does not commit the deduction that has been reserved in the PPCsubscriber’s account balance. The SCP sends an sm_anlyzd to the subscriber’s homeMC.

The home MC may discard the short message or store it for delivery at a later time.



R


R


R


O





O

SMS_DestinationAddress Network address of the destination SME’s MC(i.e., {B⇒ B’s MC}.

O










R


R


SMS_BearerData Include to indicate the account balance. Used by theMC to notify the PPC end-user {A}.

O



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 Originator’s Home MC

This scenario illustrates PPC invocation for an MS-originated short message. The PPCaccount is updated when the network accepts the short message. The originator’s home MCpurges the short message (e.g., delivery time-out, memory shortage) before it is deliveredto the destination SME. The subscriber is notified when the MC deletes the short message.

a-f. Same as Scenario 8.X.42.2, Steps a-f.

g. The subscriber’s home MC deletes the message. The MC determines that an SMSnotification event is applicable. The MC sends an SM_ANLYZD to the PPC SCP. TheSMS_Event parameter is set to indicate MS-originated short message purged by MC.

Figure 14 PPC for MS-Originated Short Message Purged by Originator’s Home MC





R

SMDPP

SMD-REQ

SM_ANLYZD

SMT

Serving

MCMSC

a

b

c

d

e

f

g

h

i

Originator

SAOT

j

k

l

MSSME

A

Home

PPCSCP

B

SMD-ACK

sm_anlyzd [ACK]

smdpp [ACK]

Destination

SME

SMAT

SMAT

SMT

SMDPP

SMD-ACK

SMD-REQ

SADT

smdpp [ACK]

SM_ANLYZD

sm_anlyzd [ACK]

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. The PPC SCP may adjust the subscriber’s account balance because the message wasdeleted before delivery. The SCP sends an sm_anlyzd to the home MC.

i. Optionally, the originator’s home MC may notify the MS-SME that the short messagewas purged before it was delivered to the destination SME.

The MC sends an SMDPP to the Serving MSC that contains the short message to presentto the subscriber. The SMS_ChargeIndicator parameter is set to indicate that no chargeis applied to the message.


R


R


O





O


O










R


R


SMS_BearerData Include to indicate the credit and updated accountbalance. Used by the MC to notify the PPC end-user {A}.

O



MSID MSID of the MS-SME. R


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. The MSC forwards the SMD-REQUEST to the SME using the air interface address ofthe MS (e.g., MSID).

k. The originating SME responds with an SMD-ACK to acknowledge acceptance of theSMD-REQUEST.

l. The Serving MSC sends a positive acknowledgement to the MC.

SMS_BearerData The message to be sent to the MS-SME based on thebearer data received from the PPC SCP in theprevious step.

R


Network address of the destination SME. R


Network address of the originating SME. R


R

SMS_ChargeIndicator Indicates “No Charge” shall be applied to this shortmessage.

R


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.6 PPC for MS-Terminated Short Message Delivered to Subscriber

This scenario illustrates successful MS-terminated short message delivery by the PPCsubscriber’s home MC. The PPC account is updated when the destination MS-SMEreceives the short message.

a. The subscriber’s home MC receives an SMDPP requesting delivery of a short messageto an MS-based SME.

Figure 15 PPC for MS-Terminated Short Message Delivered to Subscriber


SMS_BearerData Message received for MS-based SME. R


Network address of the destination SME (i.e., {B}) R


Network address of the originating SME (i.e., {A}) R

SMDPP

SMD-REQ

SM_ANLYZD

SMT

Serving

MCMSC

a

b

c

d

e

f

g

h

i

Destination

SADT

j

k

l

m

n

MSSME

B

Home

PPCSCP

A

SMD-ACK

sm_anlyzd [ACK]

smdpp [ACK]

SMDPP

SMT

smdpp [ACK]

SMAT

Source

SMEHLR

Destination Destination

SMSREQ

smsreq [SMSADDR] SRT

SMAT

SM_ANLYZD

sm_anlyzd [ACK]

SMAT

SM_ANLYZD

sm_anlyzd [ACK]

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 home MC is about to accept the short message received from the source SME. TheMC 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 associatedwith the subscriber.

c. The PPC SCP verifies that the subscriber’s account balance is sufficient and updates thePPC subscriber’s account for the chargeable event.

The PPC SCP determines that this subscriber is to be charged for further processing ofthis short message service and includes the SMS_EventNotification parameter in thesm_anlyzd sent to the home MC. The SMS_EventNotification parameter is set to


R


SMS_Event Type of SMS event encountered (i.e., MS-terminatedshort message accepted by network).

R

TOD TimeOfDay of the event for the destination’s homeMC

R

TDO TimeDateOffset of the event for the destination’shome MC.

R


R

SMS_BearerLength Length of the original SMS bearer data received forthe destination MS-based SME.

R


O

MSID MSID of destination MS-based SME. R

ESN ESN of destination MS-based SME. O

MDN MDN of destination MS-based SME O


O

SMS_DestinationAddress Network address of the destination SME’s MC(i.e., {B⇒ B’s MC}.

O










R

SMS_BillingID MC’s generated Billing Identifier for this shortmessage.

R


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

indicate the events that shall be reported to the PPC SCP. In this scenario, theSMS_EventNotification is set to indicate MS-terminated short message delivery attemptto MS-based SME, Successful MS-terminated short message delivery to MS-based SME,Unsuccessful MS-terminated short message delivery to MS-based SME, and MS-terminated short message purged by MC.

d. The home MC sends an smdpp toward the source SME.

The destination’s home MC stores the short message and possibly waits until furtherdelivery actions are taken.

e. The MC does not have the current SMS routing address for the destination MS-baedSME. The MC sends an SMSREQ to the HLR associated with the MS and includes theapplicable MS identifier.

f. The HLR responds with an smsreq. The SMSADDR parameter is set to indicate thecurrent address that can be used to route the short message.

Note: Though not shown in this scenario, the HLR may forward the SMSREQ to theserving 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. TheMC determines that an SMS event notification is applicable (see Step-c). The MC sendsan SM_ANLYZD to the PPC SCP associated with the subscriber.


SMS_EventNotification The SMS events to be reported for this particular shortmessage delivery.

R

SMS_BearerData Include to indicate the account balance information.Used by the MC to notify the PPC subscriber {B}.

O

DMH_ServiceID Include to identify the service that was invoked forthis SMS.

O


SMS_Event Type of SMS event encountered (i.e., MS-terminatedshort message delivery attempt to MS-basedSME).

R


R


R


R


R


O





O

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. The PPC SCP verifies that the subscriber’s account balance is sufficient and reserves adeduction from the PPC subscriber’s account for the chargeable event. The SCP sendsan sm_anlyzd to the home MC.

i. The home MC sends an SMDPP toward the destination SME using the current SMSrouting address for the MS-based SME.

j. The Serving MSC sends an SMD-REQUEST to the destination SME using the airinterface address of the MS-based SME (e.g., MSID).

k. The destination SME responds with a positive acknowledgment (SMD-ACK) to signalthe acceptance of the SMD-REQUEST.

l. The Serving MSC translates the SMD-ACK into an smdpp positive acknowledgementand returns it to the subscriber’s home MC.


O










R


R



O


O



SMS_BearerData Message received for MS-based SME. R


Network address of the destination SME (i.e., {B}) R


Network address of the originating SME (i.e., {A}) R


R


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

m. Following successful delivery of the short message to the MS-SME, the subscriber’shome MC determines that an SMS event notification is applicable (see Step-c). The MCsends an SM_ANLYZD to the PPC SCP associated with the subscriber.

n. The PPC SCP applies the deduction that has been reserved to the subscriber’s accountbalance. The SCP sends an sm_anlyzd to the subscriber’s home MC.


SMS_Event Type of SMS event encountered (i.e., Successful MS-terminated short message delivery to MS-basedSME).

R


R


R


R


R


O





O


O










R


R


SMS_BearerData Include to indicate the cost of the deduction andupdated account balance. Used by the MC tonotify the PPC end-user {B}.

O


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 shortmessage is accepted by the PPC subscriber’s home MC. PPC charging only occurs whenthe short message is accepted by the destination SME’s home MC.

a-b. Same as Scenario 8.X.42.6, Steps a-b.

c. The PPC SCP verifies that the subscriber’s account balance is sufficient and updates thePPC subscriber’s account for the chargeable event.

The PPC SCP determines no additional charges shall apply for this short messagedelivery. The SCP sends an sm_anlyzd to the home MC.

d-f. Same as Scenario 8.X.42.6, Steps d-f.

g-j. Same as Scenario 8.X.42.6, Steps i-l.

Figure 16 PPC for MS-Terminated Short Message Accepted by Home MC



O


O

SMDPP

SMD-REQ

SM_ANLYZD

SMT

Serving

MCMSC

a

b

c

d

e

f

g

h

i

Destination

SADT

j

MSSME

B

Home

PPCSCP

A

sm_anlyzd [ACK]

smdpp [ACK]

SMDPP

SMT

smdpp [ACK]

SMAT

Source

SMEHLR


SMSREQ


SMD-ACK

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.8 MS-Terminated Short Message Not Delivered: Low Balance

This scenario illustrates unsuccessful delivery of a short message to the destination PPCsubscriber. The subscriber’s account balance is not sufficient for the short messagedelivery.

a-g. Same as scenario 8.X.42.6, Steps a-g, but in this scenario, the destination subscriber’sPPC account balance is not sufficient to deliver the message to the MS-SME.

h. The PPC SCP examines the subscriber’s account balance. In this scenario, the PPCsubscriber’s account balance is not sufficient for this chargeable event. The PPC SCPsends an sm_anlyzd to the subscriber’s home MC.

Upon receipt of the sm_anlyzd, the subscriber’s home MC may discard the shortmessage or store it for delivery at a later time.

Figure 17 MS-Terminated Short Message Not Delivered: Low Balance


SMS_CauseCode Indicating “Service denied”. R


O

SMDPP

SM_ANLYZD

SMT

Serving

MCMSC

a

b

c

d

e

f

g

h

Destination

MSSME

B

Home

PPCSCP

A

sm_anlyzd [ACK]

smdpp [ACK]

SMAT

Source

SMEHLR


SMSREQ


SMAT

SM_ANLYZD

sm_anlyzd [NACK]

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 PPCsubscriber. The subscriber’s account balance is not low, but the destination MS-SME is notaccessible.

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 SMD-REQUEST message.

l. The Serving MSC sends a negative acknowledgement to the subscriber’s home MC.

Figure 18 MS-Terminated Short Message Not Delivered: MS Inaccessible

SMDPP

SMD-REQ

SM_ANLYZD

SMT

Serving

MCMSC

a

b

c

d

e

f

g

h

i

Destination

SADTj

k

l

m

n

MSSME

B

Home

PPCSCP

A

sm_anlyzd [ACK]

smdpp [ACK]

SMDPP

SMT

smdpp [NACK]

SMAT

Source

SMEHLR


SMSREQ


SMAT

SM_ANLYZD

sm_anlyzd [ACK]

SMAT

SM_ANLYZD

sm_anlyzd [ACK]

MS inaccessible

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

m. Following unsuccessful delivery of the short message to the MS-SME, the subscriber’shome MC determines that an SMS event notification is applicable (see Step-c). The MCsends an SM_ANLYZD to the PPC SCP associated with the subscriber.

n. The PPC SCP does not apply the deduction that has been reserved for the short messagedelivery, to the subscriber’s account balance. The SCP sends an sm_anlyzd to thesubscriber’s home MC.


SMS_Event Type of SMS event encountered (i.e., UnsuccessfulMS-terminated short message delivery to MS-based SME).

R


R


R


R


R


O





O


O










R


R


SMS_BearerData Include to indicate the account balance. Used by theMC to notify the PPC end-user {B}.

O


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 subscriber’s home MC may discard the shortmessage or store it for delivery at a later time.

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

Data Transfer Services86

IS-826 CHAPTER 5 MODIFICATIONSThis section provides additions and modifications to IS-826 Chapter 5, Modifications toTIA/EIA-41.5-D Signaling Protocol, required to support circuit-switched data and shortmessage services.

5 DATA TRANSFER SERVICES

5.1 SS7-Based Data Transfer Services(See TIA/EIA-41, page 5-6)

6 APPLICATION SERVICES

6.4 MAP Operations

6.4.1 General

6.4.1.2 Operation Specifiers(See TIA/EIA-41, page 5-24)

6.4.2 Operation Definitions(See TIA/EIA-41, page 5-27)

Table 1 MTP Message Priority Values for TIA/EIA-41 Operations

TIA/EIA-41 Operation MTP Message Priority

ShortMessageAnalyzed 0

Table 8 TIA/EIA-41 MAP Operation Specifiers

Operation Name Operation Specifier

H G F E D C B A Decimal

ShortMessageAnalyzed 0 1 1 0 1 0 0 1 105

Table 10 Summary of MAP Operations

Operation Reference

ShortMessageAnalyzed 6.4.2.ax

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

MAP Operations IS-826 Chapter 5 Modifications87

6.4.2.13 FeatureRequest(See IS-848, page 5-04)

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 asfollows:


FeatureRequest RETURN RESULT Parameters

Field Value Type Reference Notes

Identifier SET [NATIONAL 18] M 6.3.2.2

Length variable octets M 6.3.2.2

Contents

FeatureResult M 6.5.2.67

AccessDeniedReason O 6.5.2.1 a

ActionCode O 6.5.2.2 b

AnnouncementList O 6.5.2.6 c

CallingPartyNumberString1 O 6.5.2.23 d

CallingPartyNumberString2 O 6.5.2.24 d

CallingPartySubaddress O 6.5.2.25 d

CarrierDigits O 6.5.2.28 d

ConferenceCallingIndicator O 6.5.2.49 e

Digits (Dialed) O 6.5.2.58 f

DisplayText O 6.5.2.bx l, o

DMH_AccountCodeDigits O 6.5.2.59 g

DMH_AlternateBillingDigits O 6.5.2.60 g

DMH_BillingDigits O 6.5.2.61 g

DMH_RedirectionIndicator O 6.5.2.62 d

GroupInformation O 6.5.2.69 h

MobileDirectoryNumber O 6.5.2.80 g

NoAnswerTime O 6.5.2.87 d

OneTimeFeatureIndicator O 6.5.2.88 i

PACAIndicator O 6.5.2.91 j

PilotNumber O 6.5.2.95 h

PreferredLanguageIndicator O 6.5.2.96 d, p

RedirectingNumberDigits O 6.5.2.107 d

RedirectingNumberString O 6.5.2.108 d

RedirectingSubaddress O 6.5.2.109 d

ResumePIC O 6.5.2.cu m

RoutingDigits O 6.5.2.114 d

TerminationList O 6.5.2.156 k

TerminationTriggers O 6.5.2.57 d

TriggerAddressList O 6.5.2.de n

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

MAP Operations88

Notes:

a. Include if access is denied. If included, no other optional parameters shall beincluded (with the exception of the AnnouncementList parameter).

b. Include if action to be performed is not implied through presence of otherparameters.

c. Include if provision of one or more tones or announcements is required.

d. Include if applicable.

e. Include to direct that ongoing call be transformed into a Conference Call.

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

g. Include if applicable and for recording purposes (see DMH).

h. Include for multi-leg calls.

i. Include if modification to normal feature processing is required for call inprogress.

j. Include to indicate PACA priority level.

k. Include if call routing is required.

l. Include for local termination to an MS if a related feature is active.

m. Include to indicate the PIC where call processing is to resume.

n. Include to indicate address associated with active WIN triggers.

o. Refer to IS-764.

p. This parameter may only be included if the AnnouncementList parameter ispresent.

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(See TIA/EIA-41, page 5-71)

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 asfollows:

Notes:

• • •

zz. Include to identify the Border MSC’s WIN capabilities if the TriggerAddressListparameter was received.


InterSystemPage RETURN RESULT Parameters




Contents

• • • O

WINCapability O 6.5.2.di zz

• • • O

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

MAP Operations90

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)

The OriginationRequest operation is used to request call origination treatment on behalf ofa registered MS.

The OriginationRequest operation is initiated with a TCAP INVOKE (LAST). This iscarried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encodedas follows:

OriginationRequest INVOKE Parameters Timer: ORT




Contents

BillingID (Originating) M 6.5.2.16

Digits (Dialed) M 6.5.2.58

ElectronicSerialNumber M 6.5.2.63

MSCID (Originating MSC) M 6.5.2.82

MSID M 6.5.2.bv a

OriginationTriggers M 6.5.2.90

TransactionCapability M 6.5.2.160

CallingPartyName O 6.5.2.bw b

CallingPartyNumberDigits1 O 6.5.2.21 c, d

CallingPartyNumberDigits2 O 6.5.2.22 c, d

CallingPartySubaddress O 6.5.2.25 c

CDMAServiceOption O 6.5.2.f e

FeatureIndicator O 6.5.2.ej f

LocationAreaID O 6.5.2.77 c, g

MobileDirectoryNumber O 6.5.2.80 h

MSCIdentificationNumber O 6.5.2.83 i

OneTimeFeatureIndicator O 6.5.2.88 j

PC_SSN (Originating MSC) O 6.5.2.93 k

PreferredLanguageIndicator O 6.5.2.96 i

SenderIdentificationNumber O 6.5.2.116 m

ServingCellID O 6.5.2.117 c, n

TriggerType O 6.5.2.dh o

TDMAServiceCode O 6.5.2.i p

WINCapability O 6.5.2.di q

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 thatidentifier was a MIN-based IMSI, in which case the MobileIdentificationNumber(populated with the MIN derived from that IMSI) should be included.

b. Include if calling party name information is known.

c. Include if applicable.

d. Send only the National (Significant) Number (with Nature of Number set toNational) if the E.164 country code of the caller’s number matches the E.164country code used for numbers from the MSC’s Country’s Numbering Plan.

e. Include to specify requested CDMA service information.

f. Include to identify a feature invoked for the call (e.g., Three-Way Calling).

g. Include if the current location area information is available.

h. Include if available for recording purposes (see DMH).

i. Include to identify the initiating MSC and to indicate that the MSC is capable ofaccepting digits in the international format.

j. Include if any OneTimeFeatureIndicator status bits are set (i.e., have value of 1).

k. Include if SS7 may be used for subsequent call redirection.

l. Include if available.

m. Include if different from the MSCIdentificationNumber to identify the functionalentity sending the message.

n. Include if the current serving cell identity is available.

o. Include to identify the trigger encountered.

p. Include to specify requested TDMA service information.

q. Include to identify the WIN capabilities supported.

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

MAP Operations92

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 asfollows:

Notes:


OriginationRequest RETURN RESULT Parameters




Contents




CallingPartyNumberString1 O 6.5.2.23 d, e


CallingPartySubaddress O 6.5.2.25 d, e, f

CarrierDigits O 6.5.2.28 g

Digits (Dialed) O 6.5.2.58 h

DisplayText O 6.5.2.bx u, v d, e

DMH_AccountCodeDigits O 6.5.2.59 i

DMH_AlternateBillingDigits O 6.5.2.60 i

DMH_BillingDigits O 6.5.2.61 i

DMH_ChargeInformation O 6.5.2.eo i, j

DMH_RedirectionIndicator O 6.5.2.62 i, k

DMH_ServiceID O 6.5.2.ei l

GroupInformation O 6.5.2.69 m

MobileDirectoryNumber O 6.5.2.80 i

NoAnswerTime O 6.5.2.87 n

OneTimeFeatureIndicator O 6.5.2.88 o

PilotNumber O 6.5.2.95 m

PreferredLanguageIndicator O 6.5.2.96 g, p

RedirectingNumberDigits O 6.5.2.107 f

RedirectingNumberString O 6.5.2.108 d

RedirectingSubaddress O 6.5.2.109 d, e

ResumePIC O 6.5.2.cu q

RoutingDigits O 6.5.2.114 g

TerminationList O 6.5.2.156 r

TerminationTriggers O 6.5.2.57 s

TriggerAddressList O 6.5.2.de t

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. Include if one or more tones or announcements are to be applied to the MS.

d. Include if the related feature is active.

e. Include if a LocalTermination parameter is included in the TerminationListparameter.

f. Include if a PSTNTermination parameter or an IntersystemTermination parameteris included within the TerminationList parameter.

g. Include if applicable.

h. 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 terminationaddress into a destination address (e.g., the expansion of an abbreviated dialingstring), and

• the serving MSC is known to be capable of accepting digits in Internationalformat (e.g., the MSCIdentificationNumber parameter was received.

i. Include if available for recording purposes (see DMH).

j. Include to indicate charge information for the call.

k. Include if redirection may apply.

l. Include for recording purposes if a WIN service was invoked.

m. Include for multi-leg calls.

n. Include to request an override of the Serving MSC’s default No Answer Timevalue.

o. Include if modification to normal feature processing is required for the call inprogress.

p. This parameter may only be included if the AnnouncementList parameter ispresent.

q. Include to indicate the PIC where call processing is to resume.

r. Include if call routing is required.

s. Include to indicate processing in the Originating MSC for failed call attempts.

t. Include to indicate address associated with active WIN triggers.

u. Include if a LocalTermination parameter is included in the TerminationListparameter and display text shall be presented to the called MS.

v. Include if the ActionCode parameter is included and is set to indicate that displaytext shall be presented to the calling MS.

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

MAP Operations94

6.4.2.40 RoutingRequest(See TIA/EIA-41, page 5-99)

(See IS-771, page 5-23)(See IS-737, page 5-39)


The RoutingRequest operation is used to inquire as to the preferred method of routing apending call to the identified MS.

The RoutingRequest operation is initiated with a TCAP INVOKE (LAST). This is carriedby a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded asfollows:

RoutingRequest INVOKE Parameters Timer: RRT




Contents

BillingID (Originating) M 6.5.2.16 a


MSCID (Originating MSC) M 6.5.2.82

MSID M 6.5.2.bv v

SystemMyTypeCode (Originating MSC) M 6.5.2.147

AlertCode O 6.5.2.3 b

CallingPartyName O 6.5.2.bw r, u, v

CallingPartyNumberDigits1 O 6.5.2.21 c, t

CallingPartyNumberDigits2 O 6.5.2.22 c, t

CallingPartyNumberString1 O 6.5.2.21 c



CDMAServiceOption O 6.5.2.f w

DestinationDigits O 6.5.2.56 d, e

DisplayText O 6.5.2.bx c, y

DMH_AccountCodeDigits O 6.5.2.59 f

DMH_AlternateBillingDigits O 6.5.2.60 f

DMH_BillingDigits O 6.5.2.61 f

LegInformation O 6.5.2.75 g

LocationAreaID O 6.5.2.77 f, h

MobileDirectoryNumber O 6.5.2.80 f

MSCIdentificationNumber O 6.5.2.83 i

NoAnswerTime O 6.5.2.87 j

OneTimeFeatureIndicator O 6.5.2.88 k

PC_SSN (Originating MSC) O 6.5.2.93 l

PilotBillingID O 6.5.2.94 m

PilotNumber O 6.5.2.95 m

RedirectingNumberDigits O 6.5.2.107 c, t

RedirectingPartyName O 6.5.2.by s, u

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. Required to identify originating call.

b. Include to specify special alerting treatment.

c. Include if related feature is active.

d. Optionally include if TerminationTreatment parameter value is Dialogue, toselect a dialogue or to provide information to a dialogue.

e. Optionally include if TerminationTreatment parameter value isVoiceMailRetrieval or VoiceMailStorage to select the voice mail system.

f. Include if available and if TerminationTreatment parameter value is MStermination.

g. Include if TerminationTreatment parameter value is MS termination and this is amultileg call (e.g., an FA call).

h. May be included from VLR to MSC-V. Usage is not defined from HLR to VLR.

i. Include to identify Originating MSC.

j. Include to inform the serving system of the recommended no-answer time-out.

k. Include if modification to normal feature processing is required for call inprogress.

l. Include if available (e.g., from received parameter or lower layers) for subsequentcall redirection.

m. Include on a multileg call.

n. Include to identify the functional entity sending the message.

o. Include to differentiate termination types, defaulting to value MS termination.

p. Include if the TerminationTreatment parameter value is VoiceMailRetrieval orVoiceMailStorage and the mailbox is not the MobileIdentificationNumber.

q. Optional, if the TerminationTreatment parameter value is VoiceMailRetrieval; orVoiceMailStorage.

r. Include if available when a Calling Party Number String parameter has beenincluded.

s. Include if available when a Redirecting Number String parameter has beenincluded.

t. Digits are included for service logic invocations from the Serving MSC. Stringsare included for presentation to the MS.

RedirectingSubaddress O 6.5.2.109 c

SenderIdentificationNumber O 6.5.2.116 n

TerminationTreatment O 6.5.2.158 o

TerminationTriggers O 6.5.2.159 f

TDMAServiceCode O 6.5.2.i x

TriggerAddressList O 6.5.2.de u

VoiceMailboxNumber O 6.5.2.164 p

VoiceMailboxPIN O 6.5.2.165 q

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

MAP Operations96

u. Include to indicate address associated with active WIN triggers.

v. When this message is used in accessing a feature at an adjunct MSC (e.g., forvoice message retrieval), the HLR includes the type of MSID appropriate to theMS and the feature being accessed; otherwise the HLR includes the type of MSIDlast received from the Serving System. The VLR includes the type of MSID lastreceived from the Serving MSC; this may not be the type of MSID received fromthe HLR.

w. Include to identify requested CDMA service information.

x. Include to identify requested TDMA service information.

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 asfollows:

Notes:

• • •

g. Include to identify accepted CDMA service information.

h. Include to identify accepted TDMA service information

i. Include when received from the Border MSC (i.e., InterSystemPage RETURNRESULT) to identify the Border MSC’s WIN capabilities.

RoutingRequest RETURN RESULT Parameters




Contents

• • • O

CDMAServiceOption O 6.5.2.f g

TDMAServiceCode O 6.5.2.i h

WINCapability O 6.5.2.di i

• • • O

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)


The TransferToNumberRequest operation is used during feature processing to obtain anMS’s forward-to number from the HLR.

The TransferToNumberRequest operation is initiated with a TCAP INVOKE (LAST). Thisis carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set isencoded as follows:

Notes:

a. Include to identify the Originating MSC and its BillingID for subsequent callredirection.

b. Include if available (i.e., if provided in the associated RoutingRequest INVOKEor LocationRequest RETURN RESULT) for the None Reachable terminationtrigger.

c. Include if available (i.e., if provided in the associated RoutingRequest INVOKEor LocationRequest RETURN RESULT) for any termination trigger except NoneReachable.

d. Include on TIA/EIA-41 or later.

e. Include on IS-41-C or later.

f. Include if available.

g. Include to identify the network entity sending the message.

TransferToNumberRequest INVOKE Parameters Timer: TTNRT




Contents


MSID M 6.5.2.bv h

RedirectionReason M 6.5.2.110

SystemMyTypeCode (MSC) M 6.5.2.147

BillingID (Originating) O 6.5.2.16 a

CDMAServiceOption O 6.5.2.f j

GroupInformation O 6.5.2.69 b

LegInformation O 6.5.2.75 c

MSCID (Originating MSC) O 6.5.2.82 d

MSCIdentificationNumber O 6.5.2.83 e

PilotBillingID O 6.5.2.94 f

PilotNumber O 6.5.2.95 f

SenderIdentificationNumber O 6.5.2.116 g

TransactionCapability O 6.5.2.160 e

TDMAServiceCode O 6.5.2.i k

WINCapability O 6.5.2.di i

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

MAP Operations98

h. Use the MobileIdentificationNumber form of the MSID if the IMSI is known tobe a MIN-based IMSI.

i. Include to identify the WIN capabilities supported.

j. Include if CDMA channel is in use to allow distinctive forwarding based onService Type.

k. Include if TDMA channel is in use to allow distinctive forwarding based onService Type.


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 UnsolicitedResponse operation success is reported with a TCAP RETURN RESULT(LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded asfollows:


UnsolicitedResponse RETURN RESULT Parameters




Contents

AccessDeniedReason O 6.5.2.1 i

AlertCode O 6.5.2.16 a

BillingID (Originating) O 6.5.2.16 b

CallingPartyName O 6.5.2.bw g, i

CallingPartyNumberDigits1 O 6.5.2.21 d

CallingPartyNumberDigits2 O 6.5.2.22 d




DMH_AccountCodeDigits O 6.5.2.59 d

DMH_AlternateBillingDigits O 6.5.2.60 d

DMH_BillingDigits O 6.5.2.61 d

ExtendedMSCID (Originating MSC) O 6.5.2.64 e

ExtendedSystemMyTypeCode (Originating MSC) O 6.5.2.65 f

LegInformation O 6.5.2.75 g

MobileDirectoryNumber O 6.5.2.80 d

MSCIdentificationNumber (Origination MSC) O 6.5.2.83 g

OneTimeFeatureIndicator O 6.5.2.88 g

PC_SSN (Originating MSC) O 6.5.2.93 h

PilotBillingID O 6.5.2.94 g

PilotNumber O 6.5.2.95 g

PreferredLanguageIndicator O 6.5.2.96 g


RedirectingNumberString O 6.5.2.108 c

RedirectingPartyName O 6.5.2.by g

RedirectingSubaddress O 6.5.2.109 c

TerminationTreatment O 6.5.2.158 g

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

MAP Operations100

Notes:

a. Include to specify special alerting treatment.

b. Include for subsequent call redirection at the originating MSC and for recordingpurposes (see DMH).

c. Include if related feature is active.

d. Include if available.

e. Include to identify originating system.

f. Include to identify originating system manufacturer.

g. Include if available (e.g., provided in the associated RoutingRequest INVOKE).

h. Include if SS7 may be used for subsequent call redirection.

i. Include when the MS responded to a page in the border system with a service typethat differs from the one used by the system that paged.

TerminationTriggers O 6.5.2.159 g

TriggerAddressList O 6.5.2.de g

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 specificservice logic execution on another network entity (NE) containing the service logic for therequested services.

The ServiceRequest operation is initiated with a TCAP INVOKE (LAST). This is carriedby a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded asfollows:

ServiceRequest INVOKE Parameters Timer: SVRT




Contents

ServiceID M 6.5.2.bz

AccessDeniedReason O 6.5.2.15 c, d

AvailabilityType O 6.5.2.82 c, e

BillingID O 6.5.2.16 a, f

CallingPartyName O 6.5.2.bw a

CallingPartyNumberDigits1 O 6.5.2.21 a

CallingPartyNumberDigits2 O 6.5.2.22 b

CallingPartySubaddress O 6.5.2.25 a

CarrierDigits O 6.5.2.28 p

CDMAServiceOption O 6.5.2.f y

ConditionallyDeniedReason O 6.5.2.48 c, d

DataAccessElementList O 6.5.2.cd c

DestinationDigits O 6.5.2.56 q

Digits (Dialed) O 6.5.2.58 a

DMH_RedirectionIndicator O 6.5.2.62 c

DMH_ServiceID O 6.5.2.ej c, r

ElectronicSerialNumber O 6.5.2.63 c, s

ExtendedMSCID O 6.5.2.64 c, t

FeatureIndicator O 6.5.2.ej c, u

GroupInformation O 6.5.2.69 c

LegInformation O 6.5.2.75 c

LocationAreaID O 6.5.2.77 c

MobileDirectoryNumber O 6.5.2.80 c, g

MSCID (Invoking) O 6.5.2.82 c, h

MSCIdentificationNumber (Invoking) O 6.5.2.83 c, i

MSID O 6.5.2.bv c, g

PC_SSN O 6.5.2.93 i, j

PilotBillingID O 6.5.2.94 c

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

MAP Operations102

Notes:

a. Include if available.

b. Include if user provided, passed screening calling party number is available.


d. Include if a RoutingRequest operation was completed prior to the ServiceRequestoperation, and access was denied.

e. Include when MS is predictably unavailable for Call Delivery (e.g., slotted modeor sleep mode).

f. Include to correlate service usage with call instance.

g. Include if the MSID is available and is not the same as the Digits (Dialed).

h. Include to identify invoking MSC.

i. Include if SS7 is used.

j. Not for international applications.

k. Include to identify invoking FE.

l. Include to indicate the vendor type of the invoking FE.

m. 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 forthe requested services.

n. Include to identify the trigger encountered by the MSC.

o. Include to indicate the WIN capabilities supported.

p. Include to identify the interexchange carrier for call routing.

PilotNumber O 6.5.2.95 c

PreferredLanguageIndicator O 6.5.2.96 a

RedirectingPartyName O 6.5.2.by a

RedirectingNumberDigits O 6.5.2.107 a

RedirectingSubaddress O 6.5.2.109 a

RedirectionReason O 6.5.2.110 a

RoutingDigits 6.5.2.114 v

SenderIdentificationNumber O 6.5.2.116 k

ServingCellID O 6.5.2.117 c

SystemMyTypeCode O 6.5.2.147 l

TDMAServiceCode O 6.5.2.i z

TerminationAccessType O 6.5.2.155 c

TimeDateOffset O 6.5.2.dd c, w

TimeOfDay O 6.5.2.em c, x

TransactionCapability O 6.5.2.160 m

TriggerType O 6.5.2.dh n

WINCapability O 6.5.2.di o

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. Include to identify the network address of the called party for call routing.

r. Include to identify the Service Logic Program invoked on behalf of the MS.

s. Include to identify the MS.

t. Include to identify MSC serving the MS if not indicated by the MSCID parameter.

u. Include to identify a feature invoked for the call (e.g., Three-Way Calling).

v. Include to identify special routing information for call routing.

w. Include to indicate the time offset of Local Civil Time with respect to CoordinatedUniversal Time (UTC).

x. Include to indicate the time of day in UTC.

y. Include to specify CDMA service information.

z. Include to specify TDMA service 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

MAP Operations104

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 asfollows:

Notes:

a. Include if applicable.

b. Include if service logic determines access to the MS is denied.

ServiceRequest RETURN RESULT Parameters




Contents

AccessDeniedReason O 6.5.2.1 b

ActionCode O 6.5.2.2 c

AlertCode O 6.5.2.3 d

AnnouncementList O 6.5.2.6 e

CallingPartyName O 6.5.2.bw a

CallingPartyNumberString1 O 6.5.2.23 a

CallingPartyNumberString2 O 6.5.2.24 a

CallingPartySubaddress O 6.5.2.25 a

CarrierDigits O 6.5.2.28 a


DisplayText O 6.5.2.bx a

DMH_AccountCodeDigits O 6.5.2.59 a

DMH_AlternateBillingDigits O 6.5.2.60 a

DMH_BillingDigits O 6.5.2.61 a

DMH_ChargeInformation O 6.5.2.eo a, k

DMH_RedirectionIndicator O 6.5.2.62 a

DMH_ServiceID O 6.5.2.ei i

GroupInformation O 6.5.2.69 a

MobileDirectoryNumber O 6.5.2.80 a

NoAnswerTime O 6.5.2.87 a

RedirectingNumberDigits O 6.5.2.107 a

RedirectingNumberString O 6.5.2.108 a

RedirectingPartyName O 6.5.2.by a

RedirectingSubaddress O 6.5.2.109 a

ResumePIC O 6.5.2.cu q

RoutingDigits O 6.5.2.114 a

TerminationList O 6.5.2.156 h

TriggerAddressList O 6.5.2.de a, j

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. Include if action to be performed is not implied through presence of otherparameters.

d. Include to specify special alerting treatment.

e. Include if one or more tones or announcements are to be applied to the MS.


g. Include to indicate the PIC where call processing is to resume.

h. Include if call routing is required.

i. Include for recording purposes if a WIN service was invoked.

j. Include to indicate address associated with active WIN triggers.

k. Include to indicate charge information for the call.

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

MAP Operations106

6.4.2.i AnalyzedInformation(See IS-848, page 5-12)

The AnalyzedInformation (ANLYZD) operation is used by the MSC to providenotification to a service logic network element (e.g., SCP, SN) that a trigger criteria at theAnalyzed_Information DP has been satisfied. Service logic may then invoke a service orservices.

The AnalyzedInformation operation is initiated with a TCAP INVOKE (LAST). This iscarried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encodedas follows:

AnalyzedInformation INVOKE Parameters Timer: ANZT




Contents


Digits (Dialed) M 6.5.2.58

MSCID (Originating) M 6.5.2.82 b


TriggerType M 6.5.2.dh c

WINCapability M 6.5.2.di d

CallingPartyName O 6.5.2.bw e

CallingPartyNumberDigits1 O 6.5.2.21 e


CallingPartySubaddress O 6.5.2.25 e

CarrierDigits O 6.5.2.28 m, n

CDMAServiceOption O 6.5.2.f y

ConferenceCallingIndicator O 6.5.2.49 f

DestinationDigits O 6.5.2.56 m, o

DMH_BillingIndicator O 6.5.2.ep x

DMH_RedirectionIndicator O 6.5.2.62 p

ElectronicSerialNumber O 6.5.2.63 g, q

FeatureIndicator O 6.5.2.ej r

LocationAreaID O 6.5.2.77 h, s


MSCIdentificationNumber O 6.5.2.83 j

MSID O 6.5.2.bv g, q

OneTimeFeatureIndicator O 6.5.2.88 k

PreferredLanguageIndicator O 6.5.2.96

RedirectingNumberDigits O 6.5.2.107 e

RedirectingPartyName O 6.5.2.by e

RedirectingSubaddress O 6.5.2.109 e

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 to identify the call.

b. Include to identify the requesting MSC.

c. Include to identify the trigger encountered.

d. Include to identify the WIN capabilities supported.

e. Include if available (i.e., provided in call origination).

f. Include to indicate the number of conferees already in the call.

g. Include to identify the MS.

h. Include if available (information related to MS origination).


j. Include to identify the MSC sending the message, if the MSC is capable ofaccepting digits in the international format.

k. Include if any OneTimeFeatureIndicator status bits are set (i.e., have value of 1).

l. Include if call involves a special access situation (e.g., Roamer port access).

m. Include if applicable and a routing address is available.

n. Include to identify the interexchange carrier for call routing.

o. Include to identify the network address of the called party for call routing.

p. Include to identify the reason for extending the call.

q. Include if available.

r. Include to identify a feature invoked for the call (e.g., Three-Way Calling).

s. Include if the current location area information is available.

t. Include to identify special routing information for call routing.

u. Include if the current serving cell identity is available.

v. Include to indicate the time offset of Local Civil Time with respect to CoordinatedUniversal Time (UTC).

w. Include to indicate the time of day in UTC.

x. Include to indicate the type of special billing to be applied for this call(e.g., Freephone call, third party charging).

y. Include to indicate the CDMA service information for the call.

RoutingDigits O 6.5.2.114 m, t

ServingCellID O 6.5.2.117 h, u

SystemMyTypeCode O 6.5.2.147

TDMAServiceCode O 6.5.2.i z

TerminationAccessType O 6.5.2.155 l

TimeDateOffset O 6.5.2.dd v

TimeOfDay O 6.5.2.em w

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

MAP Operations108

z. Include to indicate the TDMA service information for the call.

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 asfollows:

Notes:





AnalyzedInformation RETURN RESULT Parameters




Contents



AlertCode O 6.5.2.3 p


CarrierDigits O 6.5.2.28 d

ConferenceCallingIndicator O 6.5.2.49 e


DisplayText O 6.5.2.bx d, m

DMH_AccountCodeDigits O 6.5.2.59 g

DMH_AlternateBillingDigits O 6.5.2.60 g

DMH_BillingDigits O 6.5.2.61 g

DMH_BillingIndicator O 6.5.2.ep g, q

DMH_ChargeInformation O 6.5.2.eo g, r

DMH_RedirectionIndicator O 6.5.2.62 g, h

DMH_ServiceID O 6.5.2.ei n

NoAnswerTime O 6.5.2.87 i



ResumePIC O 6.5.2.cu k

RoutingDigits O 6.5.2.114 d

TerminationList O 6.5.2.156 l


TriggerAddressList O 6.5.2.de d, o

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. Include to direct that ongoing call be transformed into a Conference Call.


g. Include if available for recording purposes (see DMH).

h. Include if redirection may apply.

i. Include to request an override of the Serving MSC's default No Answer Timevalue.

j. Include if modification to normal feature processing is required for the call inprogress.

k. Include to indicate the PIC where call processing is to resume.

l. Include if call routing is required.

m. Refer to IS-764.

n. Include for recording purposes if a WIN service was invoked.

o. Include to indicate address associated with active WIN triggers.

p. Include to specify special alerting treatment.

q. Include to indicate the type of billing to be applied for the call.

r. Include to indicate the charge information for the call.

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

MAP Operations110

6.4.2.m FacilitySelectedAndAvailable (See IS-848, page 5-17)

The FacilitySelectedAndAvailable operation success is reported with a TCAP RETURNRESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set isencoded as follows:

Notes:



c. Include to specify special alerting treatment.


e. Include if available for recording purposes (see DMH).

f. Include if redirection may apply.

g. Include to request an override of the Serving MSC's default No Answer Timevalue.

h. Include if modification to normal feature processing is required for the call inprogress.


FacilitySelectedAndAvailable RETURN RESULT Parameters




Contents



AlertCode O 6.5.2.3 c

DisplayText O 6.5.2.bx d, j

DMH_AccountCodeDigits O 6.5.2.59 e

DMH_AlternateBillingDigits O 6.5.2.60 e

DMH_BillingDigits O 6.5.2.61 e

DMH_ChargeInformation O 6.5.2.eo e, m

DMH_RedirectionIndicator O 6.5.2.62 e, f

DMH_ServiceID O 6.5.2.ei k

NoAnswerTime O 6.5.2.87 g

OneTimeFeatureIndicator O 6.5.2.88 h

ResumePIC O 6.5.2.cu i


TriggerAddressList O 6.5.2.de d, l

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. Include to indicate the PIC where call processing is to resume.

j. Refer to IS-764.

k. Include for recording purposes if a WIN service was invoked.

l. Include to indicate address associated with active WIN triggers.

m. Include to indicate charge information for the call.

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

MAP Operations112

6.4.2.t TBusy(See IS-826, page 5-29)

The TBusy (TBUSY) operation is used by an MSC to obtain call treatment instructionsfrom an SCP or SN for the called party.

The TBusy operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAPQUERY WITH PERMISSION package. The Parameter Set is encoded as follows:

Notes:

a. Include to identify the call at the invoking MSC

TBusy INVOKE Parameters Timer: TBT




Contents

BillingID (Invoking) M 6.5.2.16 a

MSCID M 6.5.2.82 b







CDMAServiceOption O 6.5.2.f l

ElectronicSerialNumber O 6.5.2.63 f

GroupInformation O 6.5.2.69 f

LegInformation O 6.5.2.75 f

LocationAreaID O 6.5.2.77 g

MobileDirectoryNumber O 6.5.2.80 h, i

MSCIdentificationNumber O 6.5.2.83 b

MSID O 6.5.2.bv h, k







RedirectionReason O 6.5.2.110 f

ServingCellID O 6.5.2.117 g


TerminationAccessType O 6.5.2.155 f

TDMAServiceCode O 6.5.2.i m

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. Include to identify the invoking MSC.





g. Include if available. (Note: this information element may not be available whenthis operation is initiated by a non-Serving MSC.)

h. One must be present for use as a service key.



k. Include to identify the MS.

l. Include to specify current CDMA service information.

m. Include to specify current TDMA service 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

MAP Operations114

The TBusy operation success is reported with a TCAP RETURN RESULT (LAST). Thisis carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:

Notes:




d. Include if a LocalTermination parameter is included in the TerminationListparameter.

e. Include if the related feature is active.

f. Include if available for recording purposes (see DMH).

g. Include for multi-leg calls.

TBusy RETURN RESULT Parameters




Contents






CarrierDigits O 6.5.2.28 l

DisplayText O 6.5.2.bx d, e, m




DMH_RedirectionIndicator O 6.5.2.62 f


GroupInformation O 6.5.2.69 g



PreferredLanguageIndicator O 6.5.2.96 l, o

RedirectingNumberDigits O 6.5.2.107 i

ResumePIC O 6.5.2.cu j

RoutingDigits O 6.5.2.114 l


TerminationTriggers O 6.5.2.57 l

TriggerAddressList O 6.5.2.de l, p

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. Include if call is being redirected.

j. Include to indicate the PIC where call processing is to resume.


l. Include if applicable.

m. Refer to IS-764.


o. This parameter may only be included if the AnnouncementList parameter ispresent.

p. Include to indicate address associated with active WIN triggers.

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

MAP Operations116

6.4.2.u TNoAnswer(See IS-826, page 5-33)

The TNoAnswer (TNOANS) operation is used by an MSC to obtain call treatmentinstructions from an SCP or SN for the called party.

The TNoAnswer operation is initiated with a TCAP INVOKE (LAST). This is carried bya TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows:

Notes:

a. Include to identify the call at the invoking MSC.

TNoAnswer INVOKE Parameters Timer: TNAT




Contents

BillingID (Invoking) M 6.5.2.16 a

MSCID M 6.5.2.82 b







CDMAServiceOption O 6.5.2.f l

ElectronicSerialNumber O 6.5.2.63 f

GroupInformation O 6.5.2.69 f

LegInformation O 6.5.2.75 f

LocationAreaID O 6.5.2.77 g

MobileDirectoryNumber O 6.5.2.80 h, i

MSCIdentificationNumber O 6.5.2.83 b

MSID O 6.5.2.bv h, k








ServingCellID O 6.5.2.117 g


TerminationAccessType O 6.5.2.155 f

TDMAServiceCode O 6.5.2.i m

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. Include to identify the invoking MSC.





g. Include if available. (Note: this information element may not be available whenthis operation is initiated by a non-Serving MSC.)

h. One must be present for use as a service key.



k. Include to identify the MS.

l. Include to specify current CDMA service information.

m. Include to specify current TDMA service 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

MAP Operations118

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:

Notes:




d. Include if a LocalTermination parameter is included in the TerminationListparameter.

e. Include if the related feature is active.

f. Include if available for recording purposes (see DMH).

g. Include for multi-leg calls.

TNoAnswer RETURN RESULT Parameters




Contents






CarrierDigits O 6.5.2.28 l

DisplayText O 6.5.2.bx d, e, m




DMH_RedirectionIndicator O 6.5.2.62 f


GroupInformation O 6.5.2.69 g



PreferredLanguageIndicator O 6.5.2.96 l, o

RedirectingNumberDigits O 6.5.2.107 i

ResumePIC O 6.5.2.cu j

RoutingDigits O 6.5.2.114 l


TerminationTriggers O 6.5.2.57 l

TriggerAddressList O 6.5.2.de l, p

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. Include if call is being redirected.

j. Include to indicate the PIC where call processing is to resume.



m. Refer to IS-764.


o. This parameter may only be included if the AnnouncementList parameter ispresent.

p. Include to indicate address associated with active WIN triggers.

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

MAP Operations120

6.4.2.aa OAnswer(See IS-826, page 5-40)

The OAnswer (OANSWER) operation is used by the MSC to provide notification to aservice 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 aTCAP UNIDIRECTIONAL package. The Parameter Set is encoded as follows:

Notes:


b. Include to identify the subscriber.

c. Include to identify the requesting MSC.

d. Include to identify MS.

e. Include to indicate the time offset of Local Civil Time with respect to CoordinatedUniversal Time (UTC).

f. Include to indicate the time of day in UTC.

g. Include to identify the trigger encountered.

h. Include if applicable.

i. Include if the current location area information is available.

OAnswer INVOKE Parameters




Contents


ElectronicSerialNumber M 6.5.2.63 b

MSCID (Originating) M 6.5.2.82 c

MSID M 6.5.2.bv d

TimeDateOffset M 6.5.2.dd e

TimeOfDay M 6.5.2.em f

TriggerType M 6.5.2.dh g

CDMAServiceOption O 6.5.2.f m

FeatureIndicator O 6.5.2.ej k

LocationAreaID O 6.5.2.77 h, i

MobileDirectoryNumber O 6.5.2.80 j

MSCIdentificationNumber O 6.5.2.83 l


ServingCellID O 6.5.2.117 h, m


TDMAServiceCode O 6.5.2.i n

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. Include if available for recording purposes (see DMH).

k. Include to identify a feature invoked for the call (e.g., Three-Way Calling).

l. Include to identify the MSC initiating the message.Include if the current servingcell identity is available.

m. Include if available to indicate the CDMA service information for the call.

n. Include if available to indicate the TDMA service information for the call.

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

MAP Operations122

6.4.2.ad TAnswer(See IS-826, page 5-45)

The TAnswer (TANSWER) operation is used by the MSC to provide notification to aservice 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 aTCAP UNIDIRECTIONAL package. The Parameter Set is encoded as follows:

Notes:


b. Include to identify MS.

c. Include to identify the requesting MSC.

d. Include to indicate the time offset of Local Civil Time with respect to CoordinatedUniversal Time (UTC).

e. Include to indicate the time of day in UTC.

f. Include to identify the trigger encountered.

TAnswer INVOKE Parameters




Contents


ElectronicSerialNumber M 6.5.2.63 b

MSCID M 6.5.2.82 c

MSID M 6.5.2.bv b

TimeDateOffset M 6.5.2.dd d

TimeOfDay M 6.5.2.em e


TriggerType M 6.5.2.dh f

WINCapability M 6.5.2.di

CDMAServiceOption O 6.5.2.f n

FeatureIndicator O 6.5.2.ej j

LocationAreaID O 6.5.2.77 g, h


MSCIdentificationNumber O 6.5.2.83 k


ServingCellID O 6.5.2.117 g, l


TerminationAccessType O 6.5.2.155 m

TDMAServiceCode O 6.5.2.i o

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. Include if applicable.

h. Include if the current location area information is available.


j. Include to identify a feature invoked for the call (e.g., Three-Way Calling).

k. Include to identify the MSC sending the message.

l. Include if the current serving cell identity is available.

m. Include if call involves a special access situation (e.g., Roamer port access).

n. Include if available to indicate the CDMA service information for the call.

o. Include if available to indicate the TDMA service information for the call.

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

MAP Operations124

6.4.2.ag OCalledPartyBusy(See IS-848, page 5-23)

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 asfollows:

Notes:

a. Include if action to be performed is not implied through presence of otherparameters.

b. Include if one or more tones or announcements are to be applied to the MS.


d. Include to indicate charge information for the call.



g. Include for recording purposes if a WIN service was invoked.


OCalledPartyBusy RETURN RESULT Parameters




Contents

AccessDeniedReason O 6.5.2.1 n

ActionCode O 6.5.2.2 a

AnnouncementList O 6.5.2.6 b

CarrierDigits O 6.5.2.28 c




DMH_ChargeInformation O 6.5.2.eo d, e


DMH_ServiceID O 6.5.2.ei g

NoAnswerTime O 6.5.2.87 h


PreferredLanguageIndicator O 6.5.2.96 c, j

RedirectingNumberDigits O 6.5.2.107 k

RoutingDigits O 6.5.2.114 c


TriggerAddressList O 6.5.2.de m

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. Include to request an override of the Serving MSC’s default No Answer Timevalue.

i. Include if modification to normal feature processing is required for the call inprogress.

j. This parameter may only be included if the AnnouncementList parameter ispresent.

k. Include if a PSTNTermination parameter or an IntersystemTermination parameteris included within the TerminationList parameter.


m. Include to indicate WIN triggers for call redirection.

n. Include if access is denied. If included, no other optional parameters shall beincluded (with the exception of AnnouncementList parameter).

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

MAP Operations126

6.4.2.ag ONoAnswer(See IS-848, page 5-27)

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:

Notes:

a. Include if action to be performed is not implied through presence of otherparameters.

b. Include if one or more tones or announcements are to be applied to the MS.


d. Include to indicate charge information for the call.



g. Include for recording purposes if a WIN service was invoked.

h. Include to request an override of the Serving MSC’s default No Answer Timevalue.


ONoAnswer RETURN RESULT Parameters




Contents

AccessDeniedReason O 6.5.2.1 n

ActionCode O 6.5.2.2 a

AnnouncementList O 6.5.2.6 b

CarrierDigits O 6.5.2.28 c




DMH_ChargeInformation O 6.5.2.eo d, e


DMH_ServiceID O 6.5.2.ei g

NoAnswerTime O 6.5.2.87 h


PreferredLanguageIndicator O 6.5.2.96 c, j

RedirectingNumberDigits O 6.5.2.107 k

RoutingDigits O 6.5.2.114 c


TriggerAddressList O 6.5.2.de m

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. Include if modification to normal feature processing is required for the call inprogress.

j. This parameter may only be included if the AnnouncementList parameter ispresent.

k. Include if a PSTNTermination parameter or an IntersystemTermination parameteris included within the TerminationList parameter.


m. Include to indicate WIN triggers for call redirection.

n. Include if access is denied. If included, no other optional parameters shall beincluded (with the exception of AnnouncementList parameter).

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

MAP Operations128

6.4.2.ax ShortMessageAnalyzed(New for TIA/EIA-41.5, Section 6.4.2)

The ShortMessageAnalyzed (SM_ANLYZD) operation is used by the MC to providenotification to a service logic network element (e.g., SCP, SN) that an SMS event criteriahas been satisfied. Service logic may then invoke a service or services.

The following table lists the possible combinations of invoking and responding NEs.

The ShortMessageAnalyzed operation is initiated with a TCAP INVOKE (LAST). This iscarried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encodedas follows:

Notes:

a. Include to indicate the length of the original SMS_BearerData received in theSMSDeliveryPointToPoint INVOKE.

Table 11 NE Combinations for SM_ANLYZD

INVOKING NE RESPONDING NE

Case 1 MC SCP

Case 2 MC SN

ShortMessageAnalyzed INVOKE Parameters Timer: SMAT




Contents

SMS_BearerLength M 6.5.2.hn a

SMS_BillingID M 6.5.2.ho b

SMS_Event M 6.5.2.hp c

SMS_TeleserviceIdentifier M 6.5.2.137 d

ElectronicSerialNumber O 6.5.2.63 e, f

MobileDirectoryNumber O 6.5.2.80 e, f, g

MSID O 6.5.2.bv e, f, g

SMS_ChargeIndicator O 6.5.2.126 h

SMS_DestinationAddress O 6.5.2.127 i

SMS_PendingMessageCount O 6.5.2.hr j

SMS_OriginalDestinationAddress O 6.5.2.131 k

SMS_OriginalDestinationSubaddress O 6.5.2.132 l

SMS_OriginalOriginatingAddress O 6.5.2.133 m

SMS_OriginalOriginatingSubaddress O 6.5.2.134 l

SMS_OriginatingAddress O 6.5.2.135 n

TimeDateOffset O 6.5.2.dd o

TimeOfDay O 6.5.2.em p

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. Include to indicate the Message Center generated Billing Identifier for this shortmessage.

c. Include to indicate the SMS event encountered.

d. Include to indicate the teleservice for which the SMS message applies.

e. Include if available.

f. Include to identify the MS.

g. At least one of these parameters must be present.

h. Include if received to specify the charging options for an SMS message.

i. Include to identify the network address of the destination only if different than theSMS_OriginalDestinationAddress.

j. Include if available to indicate the number of SMS messages in the MC pendingdelivery for and from this MS-based SME.

k. Include to identify the network address of the final destination SME.


m. Include to identify the network address of the initial originating SME.

n. Include to identify the network address of the originator only if different than theSMS_OriginalOriginatingAddress.

o. Include to indicate the time offset of Local Civil Time with respect to CoordinatedUniversal Time (UTC).

p. Include to indicate the time of day in UTC.

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

MAP Operations130

The ShortMessageAnalyzed operation success is reported with a TCAP RETURNRESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set isencoded as follows:

Notes:

a. Include for recording purposes if a WIN service was invoked.

b. Include to provide information for the subscriber, if applicable.

c. Include to specify the treatment if continued processing of the short messagedelivery is not applicable.

d. Include to specify subsequent SMS events for this short message that requireservice logic notification.

ShortMessageAnalyzed RETURN RESULT Parameters




Contents

DMH_ServiceID O 6.5.2.ei a

SMS_BearerData O 6.5.2.124 b

SMS_CauseCode O 6.5.2.125 c

SMS_EventNotification O 6.5.2.hq d

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

Map Parameters IS-826 Chapter 5 Modifications131

6.5 Map Parameters

6.5.1 General

6.5.1.1 Parameter Identifiers(See TIA/EIA-41, page 5-119)

Table 12 TIA/EIA-41 MAP Parameter Identifiers

Parameter Identifier Name Parameter Identifier Code Reference

H G F E D C B A

• • • • • • • • •

ReservedResumePIC 1 0 0 1 1 1 1 1 6.5.2.cu

1 0 0 0 0 0 1 0

0 0 0 0 1 0 1 0

• • • • • • • • •

SMS_BearerLength 1 0 0 1 1 1 1 1 6.5.2.hn

1 0 0 0 0 0 1 0

0 1 1 1 1 1 1 0

SMS_BillingID 1 0 0 1 1 1 1 1 6.5.2.ho

1 0 0 0 0 0 1 0

0 1 1 1 1 1 1 1

SMS_Event 1 0 0 1 1 1 1 1 6.5.2.hp

1 0 0 0 0 0 1 1

0 0 0 0 0 0 0 0

SMS_EventNotification 1 0 0 1 1 1 1 1 6.5.2.hq

1 0 0 0 0 0 1 1

0 0 0 0 0 0 0 1

SMS_PendingMessageCount 1 0 0 1 1 1 1 1 6.5.2.hr

1 0 0 0 0 0 1 1

0 0 0 0 0 0 1 0

TriggerCriteria 1 0 0 1 1 1 1 1 6.5.2.hs

1 0 0 0 0 0 1 1

0 0 0 0 0 0 1 1

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

Map Parameters132

6.5.2 Parameter Definitions

6.5.2.2 ActionCode(See IS-826, page 5-51)

The ActionCode (ACTCODE) parameter specifies the nature of the action (e.g., disconnectthe call) to be performed by the designated functional entity.

Notes:

a. Ignore extra octets, if received. Send only defined (or significant) octets.


Identifier ActionCodeIMPLICIT OCTET STRING

M 6.5.1.2


Contents

H G F E D C B A octet Notes

Action 1

• • • n a

Action

Decimal Value Meaning

• • •

24 Present display text to calling MS . Send the display text received in the DisplayText parameter to the calling MS.

• • •

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)


The Profile is a collection of the subscriber’s calling profile information. This informationis a list of optional parameters. The Profile macro has been defined solely for editorialconvenience, and does not affect the encoding in any way.

Notes:

• • •

xx. Include to indicate preferred CDMA service options in descending order ofpreference.

yy. Include to indicate allowed TDMA data services.

PROFILE

Type Reference Notes

Contents

• • •

CDMAServiceOptionList O 6.5.2.g xx

TDMADataFeaturesIndicator O 6.5.2.az yy

• • •

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

Map Parameters134

6.5.2.125 SMS_CauseCode(See TIA/EIA-41, page 5-262)

(See IS-725-A, page 111)

The SMS_CauseCode (SMSCAUSE) parameter indicates a reason for not delivering anSMS or OTASP message or indicates certain conditions at the Serving MSC for use duringOTASP.

Notes:

a. Only the SMS_CauseCode SMS delivery postponed is used to indicate that anSMS message is pending delivery and that notification shall be provided.

b. Ignore extra octets, if received. Send only defined (or significant) octets.


Identifier SMS_CauseCodeIMPLICIT OCTET STRING

M 6.5.1.2


Contents


SMS Cause Code 1 a

• • • n b

SMS Cause Code (octet 1)


0Address 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.

1

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.

2 Network resource shortage . Network transmission failed due to lack of a network resource shortage or link capacity.

3 Network failure . A network node failed, a link failed or a required operation failed.

4 Invalid Teleservice ID . The SMS_TeleserviceIdentifier is not known, is not supported or is not authorized by an addressed functional entity.

5 Other network problem .

6 Unsupported network interface . The intersystem network interface required for the delivery of the received message is not supported.

through 31 Reserved. Treat the same as value 5, Other network problem.

32 No page response . The addressed MS-based SME is known, but it does not respond to a page. SMS Notification is not pending.

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


33

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.

34

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.

35Destination resource shortage . A required terminal resource (e.g., memory) is not available to process this message. SMS notification is not pending.

36SMS 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.

37Destination 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.

38

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.

39 Other terminal problem . A terminal problem other than described above. SMS notification is not pending.

through 47 Reserved. Treat the same as value 39, Other terminal problem.

through 63 Reserved. Treat the same as value 36, SMS delivery postponed.

64 Radio interface shortage . There is no channel available or there is radio congestion at this time.

65

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.

66 Other radio interface problem . A radio interface problem to an MS-based SME other than described above

67 Unsupported Base Station Capability . Base Station does not support this service (e.g., SMS, OTASP, OTAPA).

through 95 Reserved. Treat the same as value 66, Other radio interface problem.

96 Encoding problem . The size of a parameter or field is not what is expected.

97

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.

98

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.



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

Map Parameters136

99Supplementary service not supported . The originating supplementary service is not known or supported, the sender is not authorized for an originating supplementary service, etc.

100 Service not supported . The service is not supported by an addressed network functional entity.

101 Reserved. Treat the same as value 107, Other general problems.

102 Missing expected parameter . An optional parameter that is required for a particular function.

103 Missing mandatory parameter . A parameter is missing that is mandatory for a particular message.

104 Unrecognized parameter value . A known parameter has a unknown or unsupported value.

105 Unexpected parameter value . A known parameter has a known, but unexpected value.

106User 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

107 Other general problems .

108Session 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).

109 Service denied . Short message service denied by service logic.

through 223 Reserved. Treat the same as value 107, Other general problems.

through 255 Reserved for TIA/EIA-41 protocol extension. If unknown, treat the same as value 107, Other general problems.



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 orcurrent mode of a call in accordance with TDMA. TDMASC is an extension to theTDMACallMode parameter.

Notes:

a. Ignore extra octets, if received. Send only defined (or significant) octets.

b. Reserved bits shall be ignored on receipt and set to zero on sending.


Identifier TDMAServiceCodeIMPLICIT OCTET STRING

M 6.5.1.2


Contents


Service Code 1

Reserved Data Rate 2 b

• • • n a

Service Code (octet 1)


0 Analog Speech Only .

1 Digital Speech Only .

2 Analog or Digital Speech, Analog Preferred .

3 Analog or Digital Speech, Digital Preferred .

4 Asynchronous Data .

5 G3 Fax.

6 Not Used (Service Rejected) .

7 STU-III.

through 255 Reserved. Treat reserved values the same as value 0, Analog Speech Only.

Data Rate (octet 2, bits A-D)


0 Not used.

1 Half-Rate Digital Traffic Channel .

2 Full-Rate Digital Traffic Channel .

3 Double Full-Rate Digital Traffic Channel .

4 Triple Full-Rate Digital Traffic Channel .

through 15 Reserved. If unknown, treat the same as value 2, Full-Rate Digital Traffic Channel.

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

Map Parameters138

6.5.2.cu ResumePIC(See IS-771, page 5-89)

The ResumePIC (RESUMEPIC) parameter identifies the point in call (PIC) at which call processingshould resume.

Notes:

a. Refer to TIA/EIA-41.7.


Identifier ResumePICIMPLICIT Unsigned Enumerated

M 6.5.1.2

Length one octet M 6.5.1.1

Contents


Point In Call 1 a

Point In Call (octet 1)


0 Not used.

1 Continue Call Processing .

2 Collect_Information PIC .

3 Analyze_Information PIC .

4 Select_Route PIC .

5 Authorize_Origination_Attempt PIC .

6 Authorize_Call_Setup PIC .

8 O_Alerting PIC .

9 O_Active PIC .

10 O_Suspended PIC .

11 O_Null PIC .

through 31 Reserved. Treat the same as value 1, Not used.

32 Select_Facility PIC .

33 Present_Call PIC .

34 Authorize_Termination_Attempt PIC .

35 T_Alerting PIC .

36 T_Active PIC .

37 Present_Call PIC .

38 T_Suspended PIC .

39 T_Null PIC .

through 223 Reserved. If unknown, ignore when received.

through 255 Reserved for TIA/EIA-41 protocol extension. If unknown, ignore when received.

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 triggersassociated with that address.

Notes:

a. This form of address is SS7 specific.

b. Include to specify additional trigger criteria for the associated list of WIN triggers.


Identifier TriggerListIMPLICIT SET

M 6.5.1.2


Contents

DestinationAddress M 6.5.2.ck a

WIN_TriggerList M 6.5.2.dk

TriggerCriteria O 6.5.2.hs b

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

Map Parameters140

6.5.2.dj WINOperationsCapability(See IS-848, page 5-46)

The WINOperationsCapability (WINOPCAP) parameter is used to specify the WINoperations and capabilities supported by the sending network element.

Notes:

a. Reserved bits shall be ignored on receipt and set to zero on sending.



Identifier WINOperationsCapabilityIMPLICIT OCTET STRING

M 6.5.1.2


Contents


Reserved CSD POS CCDIR CONN 1 a

• • • 2 b

Connect Resource (CONN) (octet 1, bit A)


0Sender is not capable of supporting the ConnectResource, DisconnectResource, ConnectionFailureReport and ResetTimer (SSFT timer) operations.

1Sender is capable of supporting the ConnectResource, DisconnectResource, ConnectionFailureReport and ResetTimer (SSFT timer) operations.

CallControlDirective (CCDIR) (octet 1, bit B)


0 Sender is not capable of supporting the CallControlDirective operation.

1 Sender is capable of supporting the CallControlDirective operation.

PositionRequest (POS) (octet 1, bit C)


0 Sender is not capable of supporting the PositionRequest operation.

1 Sender is capable of supporting the PositionRequest operation.

Circuit-Switched Data (CSD) (octet 1, bit D)


0 Sender is not capable of supporting WIN trigger-based circuit-switched data services.

1 Sender is capable of supporting WIN trigger-based circuit-switched data 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.5.2.hn SMS_BearerLength(New for TIA/EIA-41.5, Section 6.5.2)

The SMS_BearerLength (SMS_BRLEN) parameter specifies the length of the SMS BearerData.


Identifier SMS_BearerLengthIMPLICIT OCTET STRING

M 6.5.1.2

Length two octets M 6.5.1.1

Contents


MSBSMS Bearer Length

1

LSB 2

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

Map Parameters142

6.5.2.ho SMS_BillingID(New for TIA/EIA-41.5, Section 6.5.2)

The SMS_BillingID (SMS_BILLID) parameter is assigned by the subscriber’s Home MCwhen a short message is received for PPC SMS. The SMS_BillingID is used to correlateoperations and events related to a specific short message.

Notes:

a. Refer to the MSCID parameter (see 6.5.2.82) for the definition of this field.

b. MC number represents a particular MC associated with a common MarketID.

c. ID Number is a unique number assigned by the MC identified in the MarketID andMC Number fields.

d. Ignore extra octets, if received. Send only defined (or significant) octets.


Identifier SMS_BillingIDIMPLICIT OCTET STRING

M 6.5.1.2


Contents


MSBMarketID

1a

LSB 2

MC Number 3 b

MSB

ID Number

4

c5

LSB 6

• • • n d

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(New for TIA/EIA-41.5, Section 6.5.2)

The SMS_Event (SMS_EVENT) parameter identifies an individual SMS chargeable event.


Identifier SMS_EventIMPLICIT Unsigned Enumerated

M 6.5.1.2

Length 1 octet M 6.5.1.1

Contents


SMS Event 1

SMS Event (octet 1)


0 Unspecified.

1 MS-originated short message accepted by network .

2 MS-originated short message delivery attempt towards destination .

3 Successful MS-originated short message delivery towards destination .

4 Unsuccessful MS-originated short message delivery towards destination .

5 MS-originated short message purged by MC .

through 128 Reserved. Treat a reserved value the same as value 0, Unspecified.

129 MS-terminated short message accepted by network .

130 MS-terminated short message delivery attempt to MS-Based SME.

131 Successful MS-terminated short message delivery to MS-Based SME.

132 Unsuccessful MS-terminated short message delivery to MS-Based SME .

133 MS-terminated short message purged by MC .

through 223 Reserved. Treat a reserved value the same as value 0, Unspecified.

224 through 255 Reserved for TIA/EIA-41 protocol extension. If unknown, treat the same as value 0, Unspecified.

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

Map Parameters144

6.5.2.hq SMS_EventNotification(New for TIA/EIA-41.5, Section 6.5.2)

The SMS_EventNotification (SMS_EVENTNOT) parameter is used by an SCF to requestnotification of WIN SMS events at an MC for a short message. This request supersedes anypreviously requested notification of SMS events for the short message.

Notes:




Identifier SMS_EventNotificationIMPLICIT OCTET STRING

M 6.5.1.2


Contents


Reserved MO-P MO-UD MO-SD MO-DA MO-N 1 a

Reserved MT-P MT-UD MT-SD MT-DA MT-N 2 a

• • • n b

MS-Originated Short Message Network (MO-N) (octet 1, bit A)


0 No notification requested for MS-originated short message accepted by network event.

1 Notification is requested for MS-originated short message accepted by network event.

MS-Originated Short Message Delivery Attempt (MO-DA) (octet 1, bit B)


0 No notification requested for MS-originated short message delivery attempt towards destination event.

1 Notification is requested for MS-originated short message delivery attempt towards destination event.

Successful MS-Originated Short Message Delivery (MO-SD) (octet 1, bit C)


0 No notification requested for Successful MS-originated short message delivery towards destination event.

1 Notification is requested for Successful MS-originated short message delivery towards destination event.

Unsuccessful MS-Originated Short Message Delivery (MO-UD) (octet 1, bit D)


0 No notification requested for Unsuccessful MS-originated short message delivery towards destination event.

1 Notification is requested for Unsuccessful MS-originated short message delivery towards destination event.

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)


0 No notification requested for MS-originated short message purged by MC event.

1 Notification is requested for MS-originated short message purged by MC event.

MS-Terminated Short Message Network (MT-N) (octet 2, bit A)


0 No notification requested for MS-terminated short message accepted by network event.

1 Notification is requested for MS-terminated short message accepted by network event.

MS-Terminated Short Message Delivery Attempt (MT-DA) (octet 2, bit B)


0 No notification requested for MS-terminated short message delivery attempt to MS-based SME event.

1 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)


0 No notification requested for Successful MS-terminated short message delivery to MS-based SME event.

1 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)


0 No notification requested for Unsuccessful MS-terminated short message delivery to MS-based SME event.

1 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)


0 No notification requested for MS-terminated short message purged by MC event.

1 Notification is requested for MS-terminated short message purged by MC event.

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

Map Parameters146

6.5.2.hr SMS_PendingMessageCount(New for TIA/EIA-41.5, Section 6.5.2)

The SMS_PendingMessageCount (SMS_PMCNT) parameter is used to indicate thenumber of SMS messages pending delivery. The number of messages pending does notinclude SMS messages generated by the MC or by service logic, nor does the pendingmessage count include “free of charge” SMS messages1.

Notes:

a. A value of ‘0’ indicates no pending MS-originated short messages for the MS.

b. A value of ‘0’ indicates no pending MS-terminated short messages for the MS.


Identifier ActionCodeIMPLICIT OCTET STRING

M 6.5.1.2

Length four octets M 6.5.1.1

Contents


MSBMO-SMS Pending Message Count

1a

LSB 2

MSBMT-SMS Pending Message Count

3b

LSB 4

1. The ChargeIndicator parameter is used to determine that an SMS message is “free of charge.”

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(New for TIA/EIA-41.5, Section 6.5.2)

The TriggerCriteria parameter is used to identify the criteria for a WIN trigger list.

Notes:




Identifier TriggerCriteriaIMPLICIT OCTET STRING

M 6.5.1.2


Contents


Reserved CSD 1 a

• • • n b

Circuit-Switched Data (CSD) (octet 1, bit A)


0 Trigger list is not applicable for circuit-switched data calls.

1 Trigger list is applicable for circuit-switched data calls.

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

ANNEX A: ASN.1 NOTATION FOR WINPARAMETERS

148

A ANNEX A: ASN.1 NOTATION FOR WIN PARAMETERS

(See IS-771, page 5-111)

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 InterimStandard.

Table A-1 ASN.1 Notation for WIN Parameters

Parameter Acronym ASN.1 Notation

• • • • • • • • •

ResumePIC RESUMEPIC 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),...}

• • • • • • • • •

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

Intersystem Procedures IS-826 Chapter 6 Modifications149

IS-826 CHAPTER 6 MODIFICATIONSThis section provides additions and modifications to IS-826 Chapter 6, Modifications toTIA/EIA-41.6-D Signaling Procedures, required to support circuit-switched data and shortmessage services.

4 INTERSYSTEM PROCEDURES

4.14 Feature Request

4.14.1 MSC Detecting Feature Request(see IS-848, page 6-20)

When performing digit analysis of the dialed digits received from the MS, the MSC detectsthat the dialed digits are a feature control access. It shall perform the following:

1 Include the BillingID parameter set to identify the current call for billing andredirection purposes.

2 Include the Digits (Dialed) parameter set to the digits received from the MS.

3 Include the ElectronicSerialNumber parameter set to identify the MS.

4 Include the MobileIdentificationNumber parameter set to identify the MS.

5 Include the MSCID parameter set to the identity of the MSC.

6 IF any indicator is set in the OneTimeFeatureIndicator parameter:

6-1 Include the OneTimeFeatureIndicator parameter.

7 ENDIF.

8 Include SenderIdentificationNumber parameter set to the identification number of theMSC.

9 Include TransactionCapability parameter set appropriately.

10 IF the subscriber is involved in a conference call:

10-1 Include the ConferenceCallingIndicator parameter set to the number of confereescurrently in the call.

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 Stop timer (FRRT).

15-2 IF the message can be processed:

15-2-1 IF the MS is still connected:

15-2-1-1 IF the AnnouncementList parameter is received:

15-2-1-1-1 IF the PreferredLanguageIndicator parameter is received:

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

Feature Request150

15-2-1-1-1-1 Use the received Preferred Language value as the subscriber'spreferred language for playing this announcement list.

15-2-1-1-2 ENDIF.

15-2-1-1-3 Execute the “Play All Announcements in the AnnouncementList”task (see 3.2.5).

15-2-1-2 ELSEIF the FeatureResult parameter indicates Successful operation:

15-2-1-2-1 Provide a successful indication to the MS.

15-2-1-3 ELSE:

15-2-1-3-1 Provide an unsuccessful indication to the MS.

15-2-1-4 ENDIF.

15-2-1-5 IF the OneTimeFeatureIndicator parameter is received:

15-2-1-5-1 Store the received OneTimeFeatureIndicator parameter.

15-2-1-6 ENDIF.

15-2-1-7 IF the TriggerAddressList parameter is received:

15-2-1-7-1 IF the call is being redirected:

15-2-1-7-1-1 Arm the triggers indicated by the TriggerAddressList parameterfor the redirected call.

15-2-1-7-2 ELSE:

15-2-1-7-2-1 Disarm any previously armed subscribed WIN triggers for theremainder of the call in progress.

15-2-1-7-2-2 Arm the triggers indicated by the TriggerAddressList parameterfor the remainder of the call in progress.

15-2-1-7-3 ENDIF.

15-2-1-8 ENDIF.

15-2-1-9 IF the ConferenceCallingIndicator parameter is received:

15-2-1-9-1 Execute the “MSC CC Invocation” task (see 5.10.3).

15-2-1-10 ENDIF.

15-2-1-11 IF an ActionCode parameter is received:

15-2-1-11-1 Execute the “MSC ActionCode Processing” task (see 3.2.9)

15-2-1-12 ENDIF.

15-2-1-13 IF the MS is in a state capable of routing a call (e.g., after dialing a featurecode from an idle state or a call hold state).

15-2-1-13-1 IF the TerminationList parameter is received:

15-2-1-13-1-1 IF WIN triggers remain to be processed at theCollected_Information or the Analyzed_Information DP:

15-2-1-13-1-1-1 Return to the calling task.

15-2-1-13-1-2 ELSE:

15-2-1-13-1-2-1 Execute the “MSC Routing Points Of Return” task (see 3.2.6).

15-2-1-13-1-3 ENDIF.

15-2-1-13-2 ENDIF.

15-2-1-14 ENDIF.

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

Feature Request IS-826 Chapter 6 Modifications151

15-2-1-15 IF Digits (Dialed) parameter is received:

15-2-1-15-1 Set MS dialed digits to the received Digits (Dialed) parameter value.

15-2-1-15-2 IF the type of digits is unknown:

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

15-2-1-15-3 ENDIF.

15-2-1-15-4 IF WIN triggers remain to be processed at theCollected_Information or the Analyzed_Information DP:

15-2-1-15-4-1 Return to the calling task.

15-2-1-15-5 ENDIF.

15-2-1-16 ELSE:

15-2-1-16-1 Use Digits (Dialed) parameter included in the FeatureRequestINVOKE as MS dialed digits.

15-2-1-17 ENDIF.

15-2-1-18 GOTO AuthorizedSubscriberOrigination (see 3.2.3).

15-2-1-19 IF the ResumePIC parameter is received:

15-2-1-19-1 IF the value of the ResumePIC parameter is Continue Call Processing:


15-2-1-19-2 ELSEIF the value of the ResumePIC parameter is a valid transition:

15-2-1-19-2-1 GOTO the entry point indicated by the ResumePIC parameter.

15-2-1-19-3 ELSE:

15-2-1-19-3-1 Execute “Local Recovery Procedures” task (see 3.5.1).

15-2-1-19-3-2 Exit this task.

15-2-1-19-4 ENDIF.

15-2-1-20 ELSE:

15-2-1-20-1 GOTO AuthorizedSubscriberOrigination (see 3.2.3).

15-2-1-21 ENDIF.

15-2-2 ENDIF.

15-3 ELSE (the message cannot be processed):

15-3-1 Execute “Local Recovery Procedures” task (see 3.5.1).

15-3-2 IF the MS is still connected:

15-3-2-0-1 Provide an unsuccessful indication to the MS.

15-3-3 ENDIF.

15-4 ENDIF.

16 WHEN a RemoteUserInteractionDirective INVOKE is received:


16-2 Execute the “MSC Remote User Interaction” task (see 4.39.2).

16-3 Start the Feature Request Response Timer (FRRT).

16-4 Remain in this state.

17 WHEN a RETURN ERROR or REJECT is received:


17-2 Execute “Local Recovery Procedures” task (see 3.5.1).

17-3 IF the MS is still connected:

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

InterSystem Page152

17-3-1 Provide an unsuccessful indication to the MS.

17-4 ENDIF.

18 WHEN the MS disconnects:

18-1 Remain in this state (to handle possible call abandons).

19 WHEN timer (FRRT) expires:


19-2 IF the MS is still connected:

19-2-1 Provide an unsuccessful indication to the MS.

19-3 ENDIF.

20 ENDWAIT.

21 Exit this task.

4.25 InterSystem Page

4.25.2 MSC Receiving InterSystemPage INVOKE(See TIA/EIA-41.6-D, page 6-177)

When an MSC receives an InterSystemPage INVOKE, it shall perform the following:

1 IF the received message can be processed:

1-1 IF the MSC is currently executing the “MSC Detecting an Unsolicited PageResponse” procedure:

1-1-1 Exit this task.

1-2 ENDIF.

1-3 IF the MS is currently in a call or service process:

1-3-1 Include AccessDeniedReason parameter set to Busy1.

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


1-4 ELSEIF the indicated Service Type is not supported:

1-4-1 Include the AccessDeniedReason parameter set to Service Rejected bySystem.

1-4-2 Send a RETURN RESULT to the requesting MSC.


1-5 ELSEIF paging should be performed:

1-5-1 Determine the area to page base on the receive LocationAreaID parameter.2

1-5-2 Page the mobile.

1-6 ELSE:

1-6-1 Only listen for a page response.

1-7 ENDIF.

1. Handling of Call Waiting in this situation is for further study.

2. The paging area, identified by the location area ID, is defined per inter-system agreement.

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

InterSystem Page IS-826 Chapter 6 Modifications153

1-8 Start a page response timer.

1-9 WAIT for an MS response:

1-10 WHEN the page response is received:

1-10-1 Stop the page response timer.

1-10-2 IF the page response (e.g., TDMA Service Code or CDMA Service Optionparameters) indicates service rejected by the MS.

1-10-2-1 Include the AccessDeniedReason parameter set to Service Rejected byMS.

1-10-2-2 Send a RETURN RESULT.

1-10-2-3 Exit this task.

1-10-3 ELSEIF the system does not support the indicated Service Type (in the areawhere the MS is located):

1-10-3-1 Include the AccessDeniedReason parameter set to Service Rejected bySystem.



1-10-4 ENDIF

1-10-5 IF the Border MSC needs to retrieve the MS’s qualification information,optionally:

1-10-5-1 Execute “MSC Initiating a Qualification Request” task (see 4.33.1).

1-10-6 ENDIF.

1-10-7 Process the MS presence confirmation procedure.1

1-10-8 IF the MS presence confirmation fails:

1-10-8-1 Include the AccessDeniedReason parameter set to No Page Response.



1-10-9 ELSE (the presence confirmation is successful):

1-10-9-1 Execute “MSC Initiating an Authentication Request” task (see 4.4.1) toauthenticate the MS.

1-10-9-2 IF the MS is authentic:

1-10-9-2-1 IF a TLDN is available:

1-10-9-2-1-1 Assign a TLDN to the indicated MS.

1-10-9-2-1-2 Assign a billing identifier to the TLDN.

1-10-9-2-1-3 Store the Originating MSC ID information and informationrelated to the indicated MS with the assigned TLDN.

1-10-9-2-1-4 Include the MSCID parameter set to the identity of the MSC.

1-10-9-2-1-5 Include the Digits: (Destination); parameter set to the assignedTLDN.

1-10-9-2-1-6 Include the BillingID (Serving) parameter set to the TLDNbilling identifier.

1. MS presence confirmation consists of paging the MS and voice channel assignment with either SAT detectionor voice channel audit.

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

Origination Request154

1-10-9-2-1-7 IF the TriggerAddressList parameter was received:

1-10-9-2-1-7-1 Include the WINCapability parameter set to identify theMSC’s WIN capability.

1-10-9-2-1-8 ENDIF.

1-10-9-2-1-9 Send a RETURN RESULT.

1-10-9-2-1-10 Execute “MSC Initiating MS Registration” task (see 4.38.1) toproperly register the MS.

1-10-9-2-1-11 Execute the “Wait for TLDN Call” task (see 3.3.2).

1-10-9-2-2 ELSE (no TLDN is available):


1-10-9-2-2-2 Include the Error Code parameter set to ResourceShortage.

1-10-9-2-2-3 Send a RETURN ERROR.

1-10-9-2-3 ENDIF.

1-10-9-3 ELSE (MS is not authentic):

1-10-9-3-1 Execute “Local Recovery Procedures” task (see 3.5.1).

1-10-9-3-2 Exit this task.

1-10-9-4 ENDIF.

1-10-10 ENDIF.

1-11 WHEN the page response timer expires:

1-11-1 Include the AccessDeniedReason parameter set to No Page Response.

1-11-2 Send a RETURN RESULT.

1-12 ENDWAIT.

2 ELSE (the received message cannot be processed):


2-2 Send a RETURN ERROR with a proper Error Code value (see the followingtable).

3 ENDIF.

4 Exit this task.

4.31 Origination Request

4.31.1 MSC Initiating an Origination Request(see IS-848, page 6-30)

When the MSC determines that an active origination trigger has been encounteredrequiring call processing to be suspended while the HLR or another network entity mustperforms 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 Include the BillingID (Originating) parameter set to the billing identifier for the callassigned by the current Originating MSC.


3 Include the ElectronicSerialNumber parameter set to identify the originating MS.

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

Origination Request IS-826 Chapter 6 Modifications155

4 Include the MobileIdentificationNumber parameter set to identify the originating MS.

5 Include the MSCID parameter set to the identity of the Originating MSC.

6 Include the TransactionCapability parameter set to identify the current capabilities.

7 Include the WINCapability parameter set to identify the current TriggerCapability andthe current WINOperationsCapability.

8 IF the trigger that was encountered was armed by the TriggerAddressList parameter (aWIN trigger was encountered):

8-1 Include the TriggerType parameter set to identify the trigger that wasencountered.

8-2 Include the OriginationTriggers parameter set to indicate that no trigger wasencountered.

8-3 Include other applicable parameters.

8-4 Send an OriginationRequest INVOKE to the service logic host address obtainedfrom the TriggerAddressList for the trigger that was encountered.

9 ELSE (the trigger that was encountered was armed by the OriginationTriggersparameter):

9-1 Include the OriginationTriggers parameter set to identify the triggering event.

9-2 Include other applicable parameters.

9-3 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:


Origination Request RETURN RESULT Treatment:

13-1 Stop timer (ORT), if it is running.


13-2-1 IF the incoming call is still connected:


13-2-1-1-1 IF the PreferredLanguageIndicator parameter is received:

13-2-1-1-1-1 Use the received Preferred Language value as the subscriber'spreferred language for playing this announcement list.

13-2-1-1-2 ENDIF.


13-2-1-2 ENDIF.



13-2-1-3-1-1 Arm the triggers indicated by the received TriggerAddressListparameter for the redirected call.

13-2-1-3-2 ELSE:


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

Origination Request156

13-2-1-3-2-2 Arm the triggers indicated by the received TriggerAddressListparameter for the remainder of the call in progress.

13-2-1-3-3 ENDIF.

13-2-1-4 ENDIF.

13-2-1-5 IF the AccessDeniedReason parameter is received AND IF it can beacted upon:

13-2-1-5-1 IF the O_Called_Party_Busy trigger is armed for the subscriber:

13-2-1-5-1-1 Execute the “MSC Check of Serial Trigger Limit” task (see6.X).

13-2-1-5-1-2 Include the TriggerType parameter set to indicateO_Called_Party_Busy.

13-2-1-5-1-3 Include the FailureCause parameter set according to thereceived AccessDeniedReason parameter value.

13-2-1-5-1-4 Execute the “MSC Initiating an OCalledPartyBusy” task (see4.Z.1).

13-2-1-5-1-5 Return to the calling task with a successful indication.

13-2-1-5-2 ENDIF.

13-2-1-5-3 IF AnnouncementList parameter is not received:

13-2-1-5-3-1 Apply the default treatment appropriate for the receivedAccessDeniedReason value.


13-2-1-5-4 ENDIF.

13-2-1-6 ELSEIF the OriginationRequest INVOKE was sent after detecting a non-WIN trigger:

13-2-1-6-1 IF neither the TerminationList parameter nor ActionCode parameternor Digits (Dialed) parameter is received (an error condition?):

13-2-1-6-1-1 Execute the “Apply Access Denial Treatment” task (see 3.4.5).


13-2-1-6-2 ENDIF.

13-2-1-7 ENDIF.

13-2-1-8 IF the TerminationList parameter is received:



13-2-1-8-2 ENDIF.

13-2-1-8-3 Execute the “MSC Routing Points Of Return” task (see 3.2.6).

13-2-1-9 ENDIF.

13-2-1-10 IF the ActionCode parameter is received:

13-2-1-10-1 Execute the “MSC ActionCode Processing” task (see 3.2.9).

13-2-1-11 ENDIF.

13-2-1-12 IF the Digits (Dialed) parameter is received.

13-2-1-12-1 Set the MS dialed digits to the received Digits (Dialed) parametervalue.

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

Origination Request IS-826 Chapter 6 Modifications157


13-2-1-12-2-1 Process the dialed number locally to set the PointOfReturn (thismay include local feature code processing).

13-2-1-12-3 ENDIF.



13-2-1-12-5 ENDIF.

13-2-1-13 ELSE:

13-2-1-13-1 Use the Digits (Dialed) parameter included in theOriginationRequest INVOKE as MS dialed digits.

13-2-1-14 ENDIF.

13-2-1-15 GOTO AuthorizedSubscriberOrigination (see 3.2.3).






13-2-1-16-3 ELSE:

13-2-1-16-3-1 Execute the “Local Recovery Procedures” task (see 3.5.1).


13-2-1-16-4 ENDIF.

13-2-1-17 ELSE:

13-2-1-17-1 GOTO AuthorizedSubscriberOrigination (see 3.2.3).

13-2-1-18 ENDIF.

13-2-2 ELSE (call abandoned):

13-2-2-1 Execute the “Local Recovery Procedures” task (see 3.5.1).


13-2-3 ENDIF.




13-4 ENDIF.


14-1 Stop timer (ORT).

14-2 Execute the “MSC Remote User Interaction” task (see 4.39.2).

14-3 Start the Origination Request Timer (ORT).


15 WHEN a ConnectResource INVOKE is received:

15-1 Stop the timer (ORT).

15-2 Execute the “MSC Receiving ConnectResource INVOKE” task (see 4.B.3).

15-3 CASE MSC Connect Resource result OF:

15-4 Disconnect Resource received:

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

SMS Delivery Point-to-Point158

15-4-1 Start the timer (ORT).

15-4-2 Remain in this state.

15-5 OriginationRequest RETURN RESULT received:

15-5-1 GOTO OriginationRequest RETURN RESULT Treatment.

15-6 SSFT expiration:



15-7 call abandoned:

15-7-1 Execute the “Local Recovery Procedures” task (see 3.5.1).


15-8 resource disconnect:



15-9 failure at MSC:



15-10 message error:



15-11 ENDCASE.

16 WHEN the MS disconnects:

16-1 Remain in this state (to handle possible call abandons).


17-1 Stop timer (ORT).


17-3 Provide an unsuccessful indication to the MS.

17-4 Exit this task.

18 WHEN timer (ORT) expires:


18-2 Provide an unsuccessful indication to the MS.


19 ENDWAIT.

20 Return to the calling task.

4.46 SMS Delivery Point-to-Point

4.46.6 MC Receiving an SMSDeliveryPointToPoint INVOKE(See TIA/EIA-41.6-D, page 6-277)

Upon receipt of a SMSDeliveryPointToPoint INVOKE, the MC shall do the following:

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

SMS Delivery Point-to-Point IS-826 Chapter 6 Modifications159

1 IF the message can be processed:

1-1 IF the SMS_DestinationAddress parameter is received:

1-1-1 Set the destination address with the address in the receivedSMS_DestinationAddress parameter.

1-2 ELSEIF the MobileIdentificationNumber parameter is received:

1-2-1 Set the destination address to the MobileIdentificationNumber.

1-3 ELSEIF the underlying transport can carry the destination address:

1-3-1 Set the destination address with the destination address used by theunderlying transport mechanism.

1-4 ELSE:

1-4-1 Include the SMS_CauseCode parameter set to Missing Expected Parameter.



1-5 ENDIF.

1-6 IF the SMS_OriginalDestinationAddress parameter is received:

1-6-1 Set the original destination address with the address in the receivedSMS_OriginalDestinationAddress parameter.

1-7 ELSE:

1-7-1 Set the original destination address with the destination address.

1-8 ENDIF.

1-9 IF the SMS_OriginatingAddress parameter is received:

1-9-1 Set the originating address with received SMS_OriginatingAddress.

1-10 ELSEIF the underlying transport can carry the originating address:

1-10-1 Set the originating address with the originating address used by theunderlying transport mechanism.

1-11 ELSE:

1-11-1 Include the SMS_CauseCode parameter set to Missing Expected Parameter.



1-12 ENDIF.

1-13 IF the SMS_OriginalOriginatingAddress parameter is received:

1-13-1 Set the original originating address with the address in the receivedSMS_OriginalOriginatingAddress parameter.

1-14 ELSE:

1-14-1 Set the original originating address with the originating address.

1-15 ENDIF.

1-16 IF the original originating address is the same as the destination address(originating supplementary services may have been requested):

1-16-1 IF the original originating address is a SME homed to this MC, the destinationis a legitimate subscriber and the Teleservice is legitimate for the subscriber:

1-16-1-1 IF the SMS event MS-originated short message accepted by network isactive for the originating subscriber:

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-16-1-1-1 Execute the “MC Initiating a Short Message Analyzed” task(see 4.XX.1).

1-16-1-1-2 IF the request is refused:

1-16-1-1-2-1 Include the SMS_CauseCode parameter set to SMS originationdenied.



1-16-1-1-3 ELSEIF the request failed AND network operator policy dictatesthat short message processing shall not proceed upon operationfailure:

1-16-1-1-3-1 Include the SMS_CauseCode parameter set to SMS originationdenied.



1-16-1-1-4 ENDIF.

1-16-1-2 ENDIF.

1-16-1-3 Process the message with the indicated teleservice for immediateoriginating supplementary service processing (e.g., unacceptable bearerdata, canned responses for delivery schedules) indicated by the messageor the originating subscriber’s SMS profile information.

1-16-1-4 Send a RETURN RESULT message with parameters loaded accordingto the teleservice.

1-16-1-5 GOTO the “Originating MC Supplementary Services” task (see 4.46.7).

1-16-2 ELSE:

1-16-2-1 Include the SMS_CauseCode parameter indicating the proper value(e.g., SMS origination denied, Supplementary service not supported).


1-16-3 ENDIF.

1-17 ELSEIF the Original Destination Address is the same as the Destination Address(terminating supplementary services may have been requested):

1-17-1 IF the destination address is a SME homed to this MC, the destination is alegitimate subscriber and the Teleservice is legitimate for the subscriber:

1-17-1-1 IF the SMS event MS-terminated short message accepted by network isactive for the terminating subscriber:


1-17-1-1-2 IF the request is refused:

1-17-1-1-2-1 Include the SMS_CauseCode parameter set to SMS terminationdenied.



1-17-1-1-3 ELSEIF the request failed AND network operator policy dictatesthat short message processing shall not proceed upon operationfailure:

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 Include the SMS_CauseCode parameter set to SMS terminationdenied.



1-17-1-1-4 ENDIF.

1-17-1-2 ENDIF.

1-17-1-3 Process the message with the indicated teleservice for immediateterminating supplementary service processing (e.g., unacceptable bearerdata, canned responses for on vacation, travel schedules) indicated by themessage or the destination subscriber’s SMS profile information.

1-17-1-4 Send an SMSDeliveryPointToPoint RETURN RESULT message withparameters loaded according to the teleservice.

1-17-1-5 GOTO the “Terminating MC Supplementary Services” task (see 4.46.8).

1-17-2 ELSE:

1-17-2-1 Include the SMS_CauseCode parameter indicating the proper value(e.g., Address translation failure, Address vacant, Invalid TeleserviceID, SMS termination denied, Supplementary service not supported, SMSnot supported).


1-17-3 ENDIF.

1-18 ELSE (the message may have been misrouted to this MC):

1-18-1 Include the SMS_CauseCode parameter indicating the proper value.


1-19 ENDIF.

2 ELSE (the message cannot be processed):

2-1 Include the SMS_CauseCode parameter indicating the proper value.

2-2 Send a RETURN RESULT.

3 ENDIF.

4 Exit this task.

4.46.7 Originating MC Supplementary Services(See TIA/EIA-41.6-D, page 6-279)

When the Originating MC is ready to processes a pending SMSDeliveryPointToPointINVOKE, 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 originatingsubscriber’s SMS profile information.

2 WHILE originating supplementary service remains incomplete:

2-1 Schedule the message for delivery and, when ready, continue.

2-2 IF it becomes necessary for the MC to purge the short message (e.g., systemicmemory shortage) AND the SMS event MS-originated short message purged byMC is active for the originating subscriber:

2-2-1 Release storage for the message.

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


2-2-2 Execute the “MC Initiating a Short Message Analyzed” task (see 4.XX.1).


2-3 ENDIF.

2-4 IF the SMS event MS-originated short message delivery attempt towardsdestination is active for the originating subscriber:


2-4-2 IF the request is refused:

2-4-2-1 Release storage for the message.


2-4-3 ELSEIF the request failed AND network operator policy dictates that shortmessage processing shall not proceed upon operation failure:



2-4-4 ENDIF.

2-5 ENDIF.

2-6 Set the Destination Address to the Original Destination Address.

2-7 Include the SMS_BearerData parameter set by the SMS teleservice.

2-8 Include the SMS_TeleserviceIdentifier parameter set to identify the SMSteleservice.

2-9 Execute the “Initiating SMS Delivery Point-To-Point” task (see 4.46.2).1

2-10 IF the request is accepted:

2-10-1 IF the SMS event Successful MS-originated short message delivery towardsdestination is active for the originating subscriber:

2-10-1-1 Execute the “MC Initiating a Short Message Analyzed” task(see 4.XX.1).

2-10-2 ENDIF.

2-10-3 IF the supplementary service is complete:



2-10-4 ENDIF.

2-11 ELSE (the request is denied):

2-11-1 IF the SMS event Unsuccessful MS-originated short message deliverytowards destination is active for the originating subscriber:

2-11-1-1 Execute the “MC Initiating a Short Message Analyzed” task(see 4.XX.1).

2-11-2 ENDIF.


2-12 ENDIF.

3 ENDWHILE.

4 Exit this task.

1. This message may be internal to a single MC when the originating SME and destination SME are served bythe same MC.

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(See TIA/EIA-41.6-D, page 6-281)

Upon request to send a point-to-point SMS message to an MS-based SME, the MC shall dothe following:

1 IF notification is already pending for this MIN:

1-1 GOTO Wait for Notification.

2 ENDIF.

3 IF the address for the indicated MS is not current (as determined by internal algorithmsof the MC., e.g., any time between never to until revoked):

Get SMS Address:

3-1 IF notification of the presence of the MS is required:

3-1-1 Optionally, include the SMS_NotificationIndicator parameter set to Notifywhen available.

3-2 ELSE:

3-2-1 Include the SMS_NotificationIndicator parameter set to Do not notify whenavailable.

3-3 ENDIF.

3-4 Execute the “MC Initiating SMS Request” task (see 4.48.1).

3-5 IF the request was accepted:

3-5-1 Store the temporary routing address and the current time.

3-5-2 GOTO Send the message.

3-6 ELSEIF the request was denied or unavailable:



3-7 ELSE (the request was postponed which can only happen when notification isrequested):

Wait for Notification:

3-7-1 Queue the request.

3-7-2 WAIT for MS to become available to receive a short message:

3-7-3 WHEN SMSNotification is passed (see 4.47.3):

3-7-3-1 Remove the request from the queue.

3-7-3-2 Store the temporary routing address and the current time.

3-7-4 WHEN the validity of the message expires:

3-7-4-1 IF the SMS event MS-terminated short message purged by MC is activefor the terminating subscriber:


3-7-4-2 ENDIF.

3-7-4-3 Remove the request from the queue.


3-7-5 ENDWAIT.

3-8 ENDIF.

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 ENDIF.

Send the message:

5 IF the SMS event MS-terminated short message delivery attempt to MS-based SME isactive for the originating subscriber:

5-1 Execute the “MC Initiating a Short Message Analyzed” task (see 4.XX.1).

5-2 IF the request is refused:



5-3 ELSEIF the request failed AND network operator policy dictates that shortmessage processing shall not proceed upon operation failure:



5-4 ENDIF.

6 ENDIF.

7 IF notification of the presence of the MS is required:

7-1 Optionally, include the SMS_NotificationIndicator parameter set to Notify whenavailable.

7-2 Optionally, include the SMS_MessageCount parameter set to the number ofmessages pending delivery to this MS.

8 ELSE:

8-1 Include the SMS_NotificationIndicator parameter set to Do not notify whenavailable.

9 ENDIF.

10 Set the underlying transport destination address to the temporary routing address of theMS (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 destinationMS.

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 IF the SMS event Successful MS-terminated short message delivery to MS-basedSME is active for the terminating subscriber:


16-2 ENDIF.


17 ELSEIF the indication was postponed.

17-1 GOTO Wait for Notification.

18 ELSEIF the request resulted in a SMS_CauseCode value of Destination resourceshortage:

18-1 IF the SMS event Unsuccessful MS-terminated short message delivery to MS-based SME is active for the terminating subscriber:

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

Analyzed Information IS-826 Chapter 6 Modifications165


18-2 ENDIF.

18-3 Exit this task (the MC will get no further notification).

19 ELSE (the request was denied):

19-1 IF the SMS event Unsuccessful MS-terminated short message delivery to MS-based SME is active for the terminating subscriber:


19-2 ENDIF.


20 ENDIF.

21 Exit this task.

4.A Analyzed Information

4.A.1 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 beenencountered requiring call processing to be suspended while an SCF network entityexecutes service logic, and that trigger criteria have been met, the MSC shall perform thefollowing:

1 Include the BillingID parameter set to the billing identifier for the call assigned by thecurrent Originating MSC.


3 Include the MSCID parameter set to the identity of the Originating MSC.


5 5 Include the TriggerType parameter set to identify the trigger that wasencountered.

6 Include other applicable parameters.

7 Include the WINCapability parameter set to identify the current TriggerCapability andthe current WINOperationsCapability.

8 Send an AnalyzedInformation INVOKE to the SCF network entity address obtainedfrom the TriggerAddressList parameter for the trigger that was encountered.

9 Start the Analyzed Information Timer (ANZT).

10 WAIT for Analyzed Information response:


AnalyzedInformation RETURN RESULT Treatment:

11-1 Stop timer (ANZT) if it is running.




11-2-1-1-1 Execute “Play All Announcements in the AnnouncementList” task(see 3.2.5).

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

Analyzed Information166

11-2-1-2 ENDIF.


11-2-1-3-1 Execute the “Apply Access Denial Treatment” task (see 3.4.5).

11-2-1-3-2 Exit this task.

11-2-1-4 ENDIF



11-2-1-5-1-1 Arm the triggers indicated by the received TriggerAddressListparameter for the redirected call.

11-2-1-5-2 ELSE:


11-2-1-5-2-2 Arm the triggers indicated by the received TriggerAddressListparameter for the remainder of the call in progress.

11-2-1-5-3 ENDIF.

11-2-1-6 ENDIF.



11-2-1-8 ENDIF.

11-2-1-9 IF the AlertCode parameter is received:

11-2-1-9-1 Store the received AlertCode parameter value and discard anypreviously received value.

11-2-1-10 ENDIF.

11-2-1-11 IF the DisplayText parameter is received:

11-2-1-11-1 Store the received DisplayText parameter value and discard anypreviously received value.

11-2-1-12 ENDIF.


11-2-1-13-1 IF WIN triggers remain to be processed at theAnalyzed_Information DP:


11-2-1-13-2 ENDIF.

11-2-1-13-3 Execute the “MSC Routing Point Of Return” task (see 3.2.6).

11-2-1-14 ENDIF.

11-2-1-15 IF the Digits (Dialed) parameter is received:

11-2-1-15-1 Set the MS dialed digits to the received Digits (Dialed) parametervalue.


11-2-1-15-2-1 Process the dialed number locally to set the PointOfReturn.

11-2-1-15-3 ENDIF.

11-2-1-15-4 IF WIN triggers remain to be processed at theAnalyzed_Information DP:

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

Analyzed Information IS-826 Chapter 6 Modifications167


11-2-1-15-5 ENDIF.

11-2-1-16 ELSE:

11-2-1-16-1 Use the Digits (Dialed) parameter included in theAnalyzedInformation INVOKE as MS dialed digits.

11-2-1-17 ENDIF.






11-2-1-18-3 ELSE:



11-2-1-18-4 ENDIF.

11-2-1-19 ENDIF.




11-2-3 ENDIF.




11-4 ENDIF.


12-1 IF the call is still connected

12-1-1 Stop timer (ANZT).

12-1-2 Execute the “MSC Remote User Interaction” task (see 4.39.2).

12-1-3 Start the AnalyzedInformation Timer (ANZT).

12-2 ENDIF



13-1 Stop the timer (ANZT).




13-4-1 Start the timer (ANZT).


13-5 AnalyzedInformation RETURN RESULT received:

13-5-1 GOTO AnalyzedInformation RETURN RESULT Treatment.



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

Facility Selected And Available168














13-11 ENDCASE.

14 WHEN the incoming call disconnects:

14-1 Stop the timer (ANZT).

14-2 Execute the “Local Recovery Procedures” task (see 3.5.1).



15-1 Stop timer (ANZT).



16 WHEN timer (ANZT) expires:



17 ENDWAIT.


4.E Facility Selected And Available

4.E.1 MSC Initiating a Facility Selected And Available(see IS-848, page 6-44)

When the MSC determines that an active Terminating_Resource_Available trigger hasbeen encountered requiring call processing to be suspended while an SCF network entityexecutes service logic, and that trigger criteria have been met, it shall perform thefollowing:

1 Include the BillingID parameter set to the billing identifier for the call assigned by thecurrent Serving MSC.

2 Include the MSCID parameter set to the identity of the Serving MSC.


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

Facility Selected And Available IS-826 Chapter 6 Modifications169

4 Include the TriggerType parameter set to identify the trigger that was encountered.

5 Include the WINCapability parameter set to identify the current TriggerCapability andthe current WINOperationsCapability of the MSC.

6 IF the call leg was established with a PilotBillingID parameter:

6-1 Include the PilotBillingID parameter set to the same value as received.

7 ENDIF.


9 Send a FacilitySelectedAndAvailable INVOKE to the SCF network entity indicated bythe 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:


FacilitySelectedAndAvailable RETURN RESULT Treatment:

12-1 Stop the timer (FAVT), if the timer is still running.





12-2-1-1-2 Return to the calling task.

12-2-1-2 ENDIF


12-2-1-3-1 Disarm any previously armed subscribed WIN triggers for theremainder of the call in progress.

12-2-1-3-2 Arm the triggers indicated by the received TriggerAddressListparameter for the remainder of the call in progress.

12-2-1-4 ENDIF.

12-2-1-5 IF the AlertCode parameter is received:

12-2-1-5-1 Store the received AlertCode parameter value and discard anypreviously received value.

12-2-1-6 ENDIF.

12-2-1-7 IF the DisplayText parameter is received:

12-2-1-7-1 Store the received DisplayText parameter value and discard anypreviously received value.

12-2-1-8 ENDIF.



12-2-1-10 ENDIF.


12-2-1-11-1 IF the value of the ResumePIC parameter is Continue:




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

TBusy170

12-2-1-11-3 ELSE:



12-2-1-11-4 ENDIF.

12-2-1-12 ENDIF.




12-2-3 ENDIF.




12-4 ENDIF.





14-1 Stop timer (FAVT).



15 WHEN timer (FAVT) expires:



16 ENDWAIT


4.M TBusy

4.M.1 MSC Initiating a TBusy(see IS-848, page 6-46)

When the MSC determines that an active T_Busy trigger armed by a TriggerAddressListparameter has been encountered requiring call processing to be suspended while an SCFnetwork entity executes service logic, and that trigger criteria have been met, the MSC shallperform the following:


2 IF the MSC is the Originating MSC:

2-1 Include the Originating MSC’s call’s BillingID parameter to identify the call forsubsequent call redirection.

3 ELSEIF the MSC is the Serving MSC:

3-1 Include the Serving MSC’s BillingID parameter to identify the call for subsequentcall redirection.

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

TBusy IS-826 Chapter 6 Modifications171

4 ENDIF.



7 Include the WINCapability parameter set to identify the current TriggerCapability andthe current WIN Operations Capability.



9 ENDIF.


11 Send a TBusy INVOKE to the SCF network entity indicated by theTriggerAddressList parameter.

12 Start the TBusy Timer (TBT).

13 WAIT for a TBusy response:


TBusy RETURN RESULT Treatment:

14-1 Stop the timer (TBT), if it is running.





14-2-1-2 ENDIF.

14-2-1-3 IF AccessDeniedReason parameter is received:

14-2-1-3-1 Return to the calling task with an unsuccessful indication.

14-2-1-4 ENDIF.


14-2-1-5-1 Arm the triggers indicated by the received TriggerAddressListparameter for the redirected call.

14-2-1-6 ENDIF.



14-2-1-8 ENDIF.


14-2-1-9-1 Execute the “MSC Routing Points of Return” task (see 3.2.6).

14-2-1-10 ENDIF.


14-2-1-11-1 IF the value of ResumePIC parameter is Continue:


14-2-1-11-2 ELSEIF the transition indicated by the ResumePIC parameter is valid:


14-2-1-11-3 ELSE:

14-2-1-11-3-1 Return to the calling task with an unsuccessful indication.

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

TBusy172

14-2-1-11-4 ENDIF.

14-2-1-12 ENDIF.




14-2-3 ENDIF.


14-3-1 Return to the calling task with an unsuccessful indication.

14-4 ENDIF.


15-1 IF the call is still connected:

15-1-1 Stop the timer (TBT).


15-1-3 Start the TBusy Timer (TBT).

15-2 ENDIF



16-1 Stop the timer (TBT).




16-4-1 Start the timer (TBT).


16-5 TBusy RETURN RESULT received:

16-5-1 GOTO TBusy RETURN RESULT Treatment.
















16-11 ENDCASE.

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

TNoAnswer IS-826 Chapter 6 Modifications173





18-1 Stop the timer (TBT).

18-2 Return to the calling task with an unsuccessful indication.

19 WHEN the timer (TBT) expires:


20 ENDWAIT.


4.N TNoAnswer

4.N.1 MSC Initiating a TNoAnswer(see IS-848, page 6-48)

When the MSC determines that an active T_No_Answer trigger armed by aTriggerAddressList parameter has been encountered requiring call processing to besuspended while an SCF network entity executes service logic, and that trigger criteria havebeen met, the MSC shall perform the following:


2 IF the MSC is the Originating MSC:

2-1 Include the Originating MSC’s call’s BillingID parameter to identify the call forsubsequent call redirection.

3 ELSEIF the MSC is the Serving MSC:

3-1 Include the Serving MSC’s BillingID parameter to identify the call for subsequentcall redirection.

4 ENDIF.



7 Include the WINCapability parameter set to identify the current TriggerCapability andthe current WIN Operations Capability.



9 ENDIF.


11 Send a TNoAnswer INVOKE to the SCF network entity indicated by theTriggerAddressList parameter.

12 Start the TNoAnswer Timer (TNAT).

13 WAIT for a TNoAnswer response:


TNoAnswer RETURN RESULT Treatment:

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

TNoAnswer174

14-1 Stop the timer (TNAT), if it is running.





14-2-1-2 ENDIF.

14-2-1-3 IF AccessDeniedReason parameter is received:


14-2-1-3-2 Return to the calling task.

14-2-1-4 ENDIF.


14-2-1-5-1 Arm the triggers indicated by the received TriggerAddressListparameter for the redirected call.

14-2-1-6 ENDIF.



14-2-1-8 ENDIF.


14-2-1-9-1 Execute the “MSC Routing Points of Return” task (see 3.2.6).

14-2-1-10 ENDIF.


14-2-1-11-1 IF the value of ResumePIC parameter is Continue:


14-2-1-11-2 ELSEIF the transition indicated by the ResumePIC parameter is valid:


14-2-1-11-3 ELSE:

14-2-1-11-3-1 Return to the calling task with an unsuccessful indication.

14-2-1-11-4 ENDIF.

14-2-1-12 ENDIF.




14-2-3 ENDIF.


14-3-1 Return to the calling task with an unsuccessful indication.

14-4 ENDIF.


15-1 IF the call is still connected:

15-1-1 Stop the timer (TNAT).


15-1-3 Start the TBusy Timer (TNAT).

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

TNoAnswer IS-826 Chapter 6 Modifications175

15-2 ENDIF



16-1 Stop the timer (TNAT).




16-4-1 Start the timer (TNAT).


16-5 TNoAnswer RETURN RESULT received:

16-5-1 GOTO TNoAnswer RETURN RESULT Treatment.
















16-11 ENDCASE.





18-1 Stop the timer (TNAT).


19 WHEN the timer (TNAT) expires:


20 ENDWAIT.


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

OAnswer176

4.U OAnswer

4.U.1 MSC Initiating an OAnswer(see IS-826, page 6-68)

When the MSC determines that an active O_Answer trigger armed by a TriggerAddressListparameter has been encountered requiring call processing to notify the SCF network entity,and trigger criteria have been met, the MSC shall perform the following:

4.W TAnswer

4.W.1 MSC Initiating a TAnswer(see IS-826, page 6-72)

When the MSC determines that an active T_Answer trigger armed by a TriggerAddressListparameter has been encountered requiring call processing to notify the SCF network entityand trigger criteria have been met, the MSC shall perform the following:

4.Z OCalledPartyBusy

4.Z.1 MSC Initiating an OCalledPartyBusy(see IS-848, page 6-51)

When the MSC determines that an active O_Called_Party_Busy trigger armed by aTriggerAddressList parameter has been encountered requiring call processing to besuspended while an SCF network entity executes service logic, and trigger criteria havebeen met, the MSC shall perform the following:

4.AA ONoAnswer

4.AA.1 MSC Initiating an ONoAnswer(see IS-848, page 6-55)

When the MSC determines that an active O_No_Answer trigger armed by aTriggerAddressList parameter has been encountered requiring call processing to be




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

Short Message Analyzed IS-826 Chapter 6 Modifications177

suspended while an SCF network entity executes service logic, and trigger criteria havebeen met, the MSC shall perform the following:

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

4.XX.1 MC Initiating Short Message Analyzed

When the MC determines that an active SMS event has been encountered for this shortmessage that requires short message processing to be suspended while an SCF networkentity executes service logic, the MC shall perform the following:

1 Include the SMS_BearerLength parameter set to the length of the SMS bearer data forthe short message.

2 Include the SMS_BillingID parameter set to the billing identifier for the shortmessage.

3 Include the SMS_Event parameter set to identify the event that was encountered.

4 Include the SMS_TeleserviceID parameter set to the SMS teleservice identifier for theshort message.

5 If available, include the MobileDirectoryNumber parameter set to the MS-based SMEMobile Directory Number.

6 If available, include the MSID parameter set to the MS-based SME MSID.

7 Include other available parameters that are applicable.

8 Send an ShortMessageAnalyzed INVOKE to the SCF network entity address obtainedfrom the MS-Based SME subscriber’s profile for the event that was encountered.

9 Start the Short Message Analyzed Timer (SMAT).

10 WAIT for ShortMessageAnalyzed response:


11-1 Stop the timer (SMAT).


11-2-1 IF the SMS_CauseCode parameter is received:

11-2-1-1 Return to the calling task with all received parameters and a refusedindication.

11-2-2 ENDIF.

11-2-3 IF the SMS_EventNotification parameter is received:

11-2-3-1 Set the events indicated by the received SMS_EventNotificationparameter with the associated SMS message for further processing.

11-2-4 ENDIF.

11-2-5 Return to the calling task with all received parameters and an acceptedindication.




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

Short Message Analyzed178

11-4 ENDIF.


12-1 Stop the timer (SMAT).


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 shallperform the following:

1 IF the received message can be processed:

1-1 Execute “WIN Service Logic” task (see 6.Y).

1-2 Relay the parameters received from the service logic task.

1-3 Send a RETURN RESULT to the requesting MC.

2 ELSE (the received message cannot be processed):

2-1 Send a RETURN ERROR with the proper Error Code value (see the followingtable) to the requesting MC.

3 ENDIF.

4 Exit this task.

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

Short Message Analyzed IS-826 Chapter 6 Modifications179

Table 1 SCF ShortMessageAnalyzed Response

Problem Detection and Recommended Response from SCF

RETURN ERRORError Code

Problem Definition

MSID/HLRMismatchThe supplied MSID parameter is not in the network entity’s range of MSIDs (suspect routing error).

UnrecognizedMINThe network entity does not presently have a record for the supplied MobileIdentificationNumber parameter.

UnrecognizedESNThe network entity presently has a record for the supplied MSID parameter, but the supplied ElectronicSerialNumber parameter does not match the ESN in that record.

UnrecognizedIMSI The network entity does not presently have a record for the supplied IMSI parameter.

ResourceShortageA required resource (e.g., internal memory record, network entity is fully occupied) is temporarily not available (e.g., congestion).

OperationNotSupportedThe requested MAP operation is recognized, but not supported by the receiving network entity, or the requesting network entity is not authorized.

MissingParameterAn expected, or required, optional parameter was not received. Include the Parameter Identifier in question as the FaultyParameter parameter.

ParameterErrorA supplied parameter has an encoding problem. Include the Parameter Identifier in question as the FaultyParameter parameter.

SystemFailureA required resource (e.g., data base access, functional entity) is not presently accessible due to a failure. Human intervention may be required for resolution.

UnrecognizedParameterValueA supplied parameter value is unrecognized or has non-standard value. Include the Parameter Identifier in question as the FaultyParameter parameter.

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

Operation Timer Values180

7 OPERATION TIMER VALUES(See TIA/EIA-41.6-D, page 6-397)

The following table provides a summary of the timers used for MAP operations. The timervalues specified in this table are default values only and should be optimized for actualoperating environments. Some timers are locally defined 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 Default(sec.)

Start when Normally stopped when Action when timer expires

• • • • • • • • • • • • • • •

SMATShort Message Analyzed Timer

16 ShortMessageAnalyzed INVOKE is sent

ShortMessageAnalyzed RETURN RESULT or RETURN ERROR is received

Execute recovery procedures

• • • • • • • • • • • • • • •

X.S0010-A_v1.0_010504

Documents

Transcript of X.S0010-A_v1.0_010504