Sie sind auf Seite 1von 383

3GPP2 N.

S0018
Version 1.0.0
Version Date: July 14, 2000

TIA/EIA-41-D Pre-Paid Charging

Revision: 1

COPYRIGHT
3GPP2 and its Organizational Partners claim copyright in this document and individual
Organizational Partners may copyright and issue documents or standards publications in
individual Organizational Partner’s name based on this document. Requests for reproduction
of this document should be directed to the 3GPP2 Secretariat at secretariat@3gpp2.org.
Requests to reproduce individual Organizational Partner’s documents should be directed to
that Organizational Partner. See www.3gpp2.org for more information.

1
Revision History

Revision Date
Rev. 0 Initial Publication July 2000
Ballot comment resolution

Note
This specification is an extract of the post-ballot version of TIA PN-4287.

2
PN-4287

1
WIRELESS INTELLIGENT NETWORK CAPABILITIES FOR PRE-PAID CHARGING
2
3
4
5
6
7
8
9
10
11
12
CONTENTS
13
14
CHAPTER 1: OVERVIEW .......................................................................................................................... 1-1
15
16
17
CHAPTER 2: MODIFICATIONS TO TIA/EIA-664 ................................................................................... 2-1
18
19
CHAPTER 3: MODIFICATIONS TO TIA/EIA-41.1-D FUNCTIONAL OVERVIEW............................. 3-1
20
21 CHAPTER 4: MODIFICATIONS TO TIA/EIA-41.3-D AUTOMATIC ROAMING INFORMATION
22 FLOWS ........................................................................................................................................... 4-1
23
24 CHAPTER 5: MODIFICATIONS TO TIA/EIA-41.5-D SIGNALING PROTOCOLS .............................. 5-1
25
26 CHAPTER 6: MODIFICATIONS TO TIA/EIA-41.6-D SIGNALING PROCEDURES............................ 6-1
27
28 CHAPTER 7: MODIFICATIONS TO TIA/EIA/IS-771 DISTRIBUTED FUNCTIONAL PLANE .......... 7-1
29
30 (NOTE: Each chapter has its own detailed Contents.)
31
32
33
34
35
36
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 Contents
PN-4287

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
(This page intentionally left blank.) 31
32
33
34
35
36
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 ii
PN-4287

1
WIRELESS INTELLIGENT NETWORK CAPABILITIES FOR PRE-PAID CHARGING
2
CHAPTER 1
3
OVERVIEW
4
5
6
7 CONTENTS
8
9
10
FOREWORD ................................................................................................................................................... ii
11
12
REVISION HISTORY.................................................................................................................................... iii
13
14
1 INTRODUCTION ............................................................................................................................. 1
15
16 1.1 GENERAL .......................................................................................................................... 1
17 1.2 OBJECTIVE........................................................................................................................ 1
18
19
1.3 ORGANIZATION .............................................................................................................. 1
20 1.4 EDITORIAL CONVENTIONS .......................................................................................... 2
21
1.5 ASSUMPTIONS ................................................................................................................. 2
22
23
1.6 DISTRIBUTED FUNCTIONAL PLANE IMPACTS ........................................................ 4
24
25
26
27
28
29
30
31
32
33
34
35
36
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-i Contents
PN-4287

FOREWORD 2
3
4
This Interim Standard presents a recommended plan for the implementation of Pre-Paid 5
Charging (PPC) for use in the Wireless Radiotelephone Service. 6
7
This Interim Standard builds on the following standards:
8

• ANSI/TIA/EIA-664, Cellular Features Description; Telecommunications Industry 9

Association; June 1996 10


11
• ANSI/TIA/EIA-41-D, Cellular Radiotelecommunications Intersystem Operations; 12
Telecommunications Industry Association; 1997 13
14
• TIA/EIA/IS-751, TIA/EIA-41-D Modifications to Support IMSI; 15
Telecommunications Industry Association; February 1998 16
17
• TIA/EIA/IS-771, Wireless Intelligent Network; Telecommunications Industry
18
Association; December 1998
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Foreword 1-ii
PN-4287

1
2
3
REVISION HISTORY
4
5
6
7 Rev. Date Remarks
8
0 May 2000 Approved For Publication
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
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-iii Revision History


PN-4287

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
(This page intentionally left blank.) 31
32
33
34
35
36
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 1-iv


PN-4287

1
2
3
1 INTRODUCTION
4
5 Pre-Paid Charging (PPC) allows the subscriber to pay for voice telecommunication
6 services prior to usage. This document presents a recommended plan for the
7 implementation of Wireless Intelligent Network (WIN) capabilities that support PPC.
8 The WIN capabilities that support PPC are for use in the Wireless Radiotelephone
9 Service.
10
11
12 1.1 GENERAL
13
14 This document describes the WIN capabilities needed for PPC and the intersystem
15 operations to enable a wireless subscriber to use the intelligent network capabilities in
16 systems into which the subscriber roams.
17
18
19
20
1.2 OBJECTIVE
21
22
The purpose of this document is to describe the WIN capabilities needed for PPC and to
23
specify the WIN operation so that a roaming wireless subscriber can access the intelligent
24
network capabilities in a seamless manner.
25
The purpose of this document is also to describe the modifications to WIN operations
26
(including the WIN operations initially specified in TIA/EIA/IS-771) needed to support
27
IMSI.
28
29
30
31 1.3 ORGANIZATION
32
33 This document is organized as follows:
34
35
• Chapter 2 provides Stage 1 feature descriptions for PPC according to the
36
structure of TIA/EIA-664.
37
• Chapter 3 provides the modifications and additions to TIA/EIA-41-D Chapter 1
38
“Functional Overview” for PPC.
39
40 • Chapter 4 provides the modifications and additions to TIA/EIA-41-D Chapter 3
41 “Automatic Roaming Information Flows” for PPC.
42
43 • Chapter 5 provides the modifications and additions to TIA/EIA-41-D Chapter 5
44 “Signaling Protocol” for PPC.
45
• Chapter 6 provides the modifications and additions to TIA/EIA-41-D Chapter 6
46
“Signaling Procedures” for PPC.
47
48 • Chapter 7 provides the modifications and additions to TIA/EIA/IS-771 Chapter 7
49 “Distributed Functional Plane” for PPC.
50
51
52
53
54
55
56
57
58
59
60

1-1 Introduction
PN-4287

1
1.4 EDITORIAL CONVENTIONS 2
3
The following editorial conventions are used in this Interim Standard for Chapters 1, 2, 3, 4
4, 5 and 7: 5
6
• underline: additions
7

• cross out: deletions 8


9
• single vertical change bar: indicates additions or deletions 10
11
• new sub-sections are identified in the sub-section heading 12
13
• for clarity, new sub-sections are shown with single vertical change bars but are
14
not underlined
15
16
The following editorial conventions are used in this Interim Standard for Chapter 6: 17
18
• underline: TIA/EIA/IS-771 additions 19
20
• double underline: additions for this Interim Standard
21
22
• cross out: deletions
23

• single vertical change bar: indicates TIA/EIA/IS-771 additions or deletions 24


25
• double vertical change bar: indicates additions or deletions for this Interim 26
Standard 27
28
• new sub-sections are identified in the sub-section heading 29
30
• for clarity, new sub-sections are shown with double vertical change bars but are
31
not underlined
32
33
34
1.5 ASSUMPTIONS 35
36
The following assumptions were used in the development of this standard: 37
38
1. Pre-Paid Charging (PPC) is invoked before any other services are invoked to
39
verify a positive account balance. If the subscriber’s account balance is at or
40
below threshold, all services may be blocked.
41

A PPC subscriber with a balance at or below threshold, may be connected to a 42

customer service representative automatically when attempting to originate any 43

call so that the account can be refilled. 44


45
2. An announcement may be played when an MS originates a call to inform the 46
subscriber of his or her account balance. The account balance may be presented 47
to the subscriber as the amount of time remaining in the account. The call 48
routing information needed to rate the call must be available to PPC service 49
logic before the announcement can be played. 50
51
3. A subscriber (or surrogate) is notified of a low account balance by a “low 52
balance” tone or optionally a switch-based announcement being played during a 53
call. The subscriber is expected to end the current call in a timely fashion and to 54
refill the PPC account. 55
56
4. End-of-Call announcements are not provided to the PPC subscriber at the end of
57
an incoming call.
58
59
60

Introduction 1-2
PN-4287

1
5. PPC service logic may end the current subscriber call (or calls). A “disconnect
2
warning” tone or announcement is played to the subscriber (or surrogate) before
3
the call is disconnected.
4
5 6. The charges for a call may start when the call is answered or as determined by
6 the service provider.
7
8 7. The charges for a call may stop when the call is disconnected.
9
10
8. The PPC service logic has access to all the subscriber profile information needed
11
to provide the service (e.g., subscriber’s preferred language).
12
9. A subscriber’s PPC account is identified by the subscriber’s MSID or MDN or
13
both.
14
15 10. Call rating for call delivery involves the time of day in both the originating and
16 the serving systems. Long distance charges are based on home system time.
17 Local and air time charges are based on serving system time. The time of day of
18 the Originating MSC is included in the query message sent to the PPC service
19 logic program instance (SLPI) when a routing address is available (i.e., at the
20 Analyzed_Information DP). This information is used by the SLPI to calculate
21 an approximate rate for the call using “nominal” local charges at the Serving
22 MSC. When the call is answered by the mobile subscriber, the query message to
23 the PPC SLPI includes the time of day at the Serving MSC enabling the PPC
24 SLPI to have the accurate local charge information needed to rate the call.
25
26 Call rating for mobile originated calls involves the time of day in the serving
27 system.
28
11. Some calls may be free (e.g., calls to customer service).
29
30 12. Only voice telecommunications services are considered.
31
32 13. The interaction of the Call Transfer service and the PPC service is not
33 considered.
34
35
14. The interaction of the Conference Calling service and the PPC service is not
36
considered.
37
15. Impacts of Wireless Number Portability Phase II (TIA/EIA/IS-756-A) have not
38
been considered (e.g., signaling procedures).
39
40 16. PPC information may be sent to an MS for display. This information is
41 conveyed in the DisplayText parameter using the Text [e.g., ASCII] Display Tag
42 value (see ANSI T1.610).
43
44 17. When the subscriber is engaged in a three-way call with one leg of the call to a
45 locally allowed number (e.g., 9-1-1) which the PPC SCF may not be aware of,
46 the MSC ignores any ActionCode parameter value received from the SCF in a
47 CallControlDirective INVOKE. The MSC indicates that no action was taken
48 due to the locally allowed call to the SCF in the CallControlDirective RETURN
49 RESULT.
50
51
18. SIM relay of a CallControlDirective INVOKE is not considered in this standard.
52
19. SIM relay of an UnreliableCallData INVOKE is not considered in this standard.
53
54
55
56
57
58
59
60

1-3 Introduction
PN-4287

1
1.6 DFP IMPACTS 2
3
The following WIN DFP modifications are described in this standard: 4
5
a. The Origination_Attempt_Authorized trigger has been defined for the
6
Origination_Attempt_Authorized DP. This trigger can be used to invoke PPC
7
for an MS originated call after the MSC authorizes the MS origination and
8
determines that the call is not to a locally allowed number (e.g., 9-1-1).
9

The Origination_Attempt_Authorized trigger is armed as a TDP-R for the 10

scenarios in this standard. 11


12
The OriginationRequest operation is used to query service logic when the 13
Origination_Attempt_Authorized trigger is encountered. The TriggerType 14
parameter is set to indicate the trigger was encountered. 15
16
b. The Initial_Termination trigger has been defined for the Analyzed_Information 17
DP. This trigger is armed for the called subscriber by the TriggerAddressList 18
parameter received in the l o c r e q returned to the MSC after the 19
Mobile_Termination trigger was encountered. 20
21
The Initial_Termination trigger is armed as a TDP-R for the scenarios in this
22
standard.
23
The AnalyzedInformation operation is used to notify the SLPI that a call is 24
requested to be delivered to a pre-paid subscriber. The TriggerType parameter 25
is set to indicate this trigger was encountered. 26
27
c. The Calling_Routing_Address_Available trigger has been defined for the 28
Analyzed_Information DP. This trigger is armed for the calling PPC subscriber. 29
It is used to convey a routing address and call type to the SLPI. 30
31
The Calling_Routing_Address_Available trigger is armed as a TDP-R for the
32
scenarios in this standard.
33

The AnalyzedInformation operation is used to notify service logic of the 34

availability of a routing address. The TriggerType parameter is set to indicate 35

this trigger was encountered. 36


37
d. The Called_Routing_Address_Available trigger has been defined for the 38
Analyzed_Information DP. This trigger is armed for the called pre-paid 39
subscriber. It is used to convey a routing address and call type to the SLPI. 40
41
The Called_Routing_Address_Available trigger is armed as a TDP-R for the 42
scenarios in this standard. 43
44
The AnalyzedInformation operation is used to notify service logic of the
45
availability of a routing address. The TriggerType parameter is set to indicate
46
this trigger was encountered.
47

e. The O_Answer trigger has been defined for the O_Answer DP. This trigger (an 48

existing CS-2 trigger) can be used to notify the SLPI of call answer for a call 49

originated at an MSC (e.g., MS origination) or for a call forwarded by the MSC. 50


51
The O_Answer trigger is armed as a TDP-N for the calling PPC subscriber for 52
scenarios illustrated in this standard. 53
54
The new OAnswer operation is used to notify the SLPI of the call answer. 55
56
f. The T_Answer trigger has been defined for the T_Answer DP. This trigger (an
57
existing CS-2 trigger) can be used to notify service logic of call answer for a call
58
terminated at an MSC (e.g., MS terminated call).
59
60

Introduction 1-4
PN-4287

1
The T_Answer trigger is armed as a TDP-N for the PPC scenarios illustrated in
2
this standard.
3
4 The new TAnswer operation is used to notify service logic for the call answer by
5 a called PPC subscriber.
6
7 g. The O_Disconnect trigger has been defined for the O_Disconnect DP. This
8 trigger (an existing CS-2 trigger) can be used to notify the SLPI of call
9 disconnect for a call originated at an MSC (e.g., MS origination) or for a call
10 forwarded by the MSC.
11
12
The O_Disconnect trigger is armed as a TDP-R for a calling subscriber for the
13
PPC scenarios illustrated in this standard.
14
The new ODisconnect operation is used to query the SLPI upon call disconnect.
15
16 h. The T_Disconnect trigger has been defined for the T_Disconnect DP. This
17 trigger (an existing CS-2 trigger) can be used to notify the SLPI of call
18 disconnect for a call terminated at an MSC (e.g., MS terminated call).
19
20 The T_Disconnect trigger is armed as a TDP-R for the called subscriber for the
21 PPC scenarios illustrated in this standard.
22
The new TDisconnect operation is used to query the SLPI upon call disconnect.
23
24
25 i. The Locally_Allowed_Specific_Digit_String trigger has been defined for the
26 Origination_Attempt_Authorized DP. This Office-based trigger can be used to
27 invoke service logic for a locally allowed dialed digits string1.
28
29 The Locally_Allowed_Specific_Digit_String trigger is armed as a TDP-R.
30
The OriginationRequest operation is used to query service logic when the
31
Locally_Allowed_Specific_Digit_String trigger is encountered. The
32
TriggerType parameter is set to indicate the trigger was encountered.
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
1 The Locally_Allowed_Specific_Digit_String trigger enables processing of locally
56
57 allowed digit strings by a WIN Service Logic Program. Locally allowed dialed digit
58 strings can be processed by other methods (e.g., MSC local routing of call).
59
60

1-5 Introduction
PN-4287

1
WIRELESS INTELLIGENT NETWORK CAPABILITIES FOR PRE-PAID CHARGING
2
CHAPTER 2
3
FEATURE DESCRIPTION
4
5
6
7 CONTENTS
8
9
10
LIST OF TABLES ........................................................................................................................................... ii
11
12
REVISION HISTORY.................................................................................................................................... iii
13
14
3 Definitions and Concepts .................................................................................................................. 1
15
16 3.1 Definitions ........................................................................................................................... 1
17 5.A Pre-Paid Charging (PPC) .................................................................................................... 2
18
5.A.1 Normal Procedures With Successful Outcome..................................................... 2
19
20
5.A.2 Exception Procedures or Unsuccessful Outcome ................................................. 6
21 5.A.3 Alternative Procedures ......................................................................................... 8
22 5.A.4 Interactions With Other Wireless Services ........................................................... 8
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PPC Feature Description 2-i Contents


PN-4287

LIST OF TABLES 2
3
4
Table A: PPC Subscription Options............................................................................ 2 5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

List of Tables 2-ii PPC Feature Description


PN-4287

1
2
3
REVISION HISTORY
4
5
6
Rev. Date Remarks
7
8 0 May 2000 Approved For Publication
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PPC Feature Description 2-iii Revision History


PN-4287

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
(This page intentionally left blank.) 31
32
33
34
35
36
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 2-iv PPC Feature Description


PN-4287

1
2
3
3 Definitions and Concepts
4
5
6
3.1 Definitions
7
8
Chargeable Event
9
10
11
A chargeable event is any event initiated either by the subscriber or by the network that
12
may result in a decrease of the subscriber’s PPC account balance. A chargeable event
13 may occur during a voice telecommunications service. A chargeable event has a
14 beginning and an end, which are used to start and stop the corresponding PPC invocation.
15
16
17 PPC Pre-Paid Charging
18
19 See 5.A
20
21
22
Post Usage Billing (PUB)
23
24
25
PUB allows the subscriber with proper credit to pay for telecommunications services after
26
usage.
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PPC Feature Description 2-1 Definitions and Concepts


PN-4287

1
5.A Pre-Paid Charging (PPC) 2
3
PPC allows the subscriber to pay for voice telecommunication services prior to usage. 4
5

A PPC subscriber establishes an account with the service provider to access voice 6

telecommunications services in home and roaming networks. Charges for voice 7

telecommunication services are applied to the PPC account by decrementing the account 8

in real time. The PPC subscriber may be notified about the account information at the 9

beginning, during, or at the end of the voice telecommunications service. When the 10

account balance is low, the subscriber may be notified so that the subscriber may refill the 11

account. When the account balance is below a pre-defined threshold, the subscriber’s use 12

of voice telecommunications services may be de-authorized. 13


14
15
PPC may be activated for all calls or on a single call basis. For “All-Calls” activation, 16
charges for all voice telecommunications services invoked are applied to the PPC 17
account. For “Single-Call” activation, only charges for voice telecommunications 18
services invoked in association with the call origination are applied to the PPC account. 19
20
21
Applicability to Telecommunications Services 22
23
PPC is applicable to voice telecommunications services. In the future, PPC may apply to 24
other telecommunications services. 25
26

In this document, the usual billing practice is referred to as post-usage billing (PUB). 27
28
29
30
5.A.1 Normal Procedures With Successful Outcome 31
32
33
Authorization
34
35
PPC is provided after pre-arrangement with the service provider.
36
37
The authorization may have the following subscription options: 38
39
Subscription Options Values 40
41
Single-Call Activation Demand. The subscriber is 42
authorized to activate PPC for a 43
single call origination. 44
45
Permanent. PPC may not be
46
activated for single call
47
originations.
48
All-Calls Activation Demand. The subscriber is 49
authorized to control the activation 50
and de-activation of PPC for all 51
calls. 52
53
Permanent. PPC is active for all 54
calls while authorized. 55
56
Table A: PPC Subscription Options
57
58
59
60

Pre-Paid Charging (PPC) 2-2 PPC Feature Description


PN-4287

1
De-Authorization
2
3
PPC may be withdrawn at the subscriber’s request or for administrative reasons.
4
5
6
7
Registration
8
9
PPC has no registration.
10
11
12 De-Registration
13
14 PPC has no de-registration.
15
16
17 Activation
18
19 If the subscriber is authorized for Permanent “All-Calls” Activation, PPC is activated
20 upon authorization.
21
22
PPC may be activated by a Demand “All-Calls” Activation authorized subscriber by
23
specifying a feature code, as in:
24
25
*

26
FC + SEND .
27
28
If the activation is accepted, the system shall indicate success with feature confirmation
29
treatment. If PPC is activated while a call is in progress, the activation shall not affect the
30
call in progress.
31
32 PPC may be activated by a Demand “Single-Call” Activation authorized subscriber by
33 specifying a feature code and a termination address:
34
*

35 FC + # + termination address + SEND , or


36
37
*

38
FC + termination address + SEND .
39
40
If the activation is accepted, the system shall indicate success with feature confirmation
41
treatment. In this case PPC applies only to charges for voice telecommunication services
42
associated with the call origination attempt.
43
44
45 De-Activation
46
47 PPC shall be de-activated upon de-authorization.
48
49
PPC may be de-activated by a Demand “All-Calls” Activation authorized subscriber by
50
specifying a feature code, as in:
51
52
*

FC0 + SEND .
53
54
If the de-activation is accepted, the system shall indicate success with feature
55
confirmation treatment. If PPC is de-activated while a call is in progress, the
56
de-activation shall not affect the call in progress.
57
58
59
60

PPC Feature Description 2-3 Pre-Paid Charging (PPC)


PN-4287

1
For a “Single-Call” activation, PPC is automatically de-activated after the single call
2
attempt is cleared.
3
4
5
Invocation 6
7
PPC is invoked when a chargeable event begins and PPC is active. 8
9
10
Normal Operation With Successful Outcome 11
12
PPC subscribers may have a “normal” PUB account. For those subscribers, the PPC and 13
PUB service profiles do not have to be identical. For a subscriber who has both PPC and 14
PUB profiles, the “Single-Call” PPC profile has precedence over the “All-Calls” profile. 15
16

A PPC subscriber may request the notification of current PPC account information at any 17

time from the Pre-Paid Charging system, while not in an active call. 18
19
20
Normal operation with account balance above threshold
21

PPC subscribers can use all subscribed voice telecommunication services in a normal 22

manner when their account balance is above a threshold level. When PPC is invoked, the 23

PPC account is decremented in real time. Voice telecommunication services may be 24

charged to the PPC account at a flat rate, on invocation, or according to usage duration. 25
26
27
The PPC subscriber may be notified about the account information and charges 28
associated with voice telecommunication services at the beginning, during and/or at the 29
end of the voice telecommunication services. 30
31
If PPC is active, the PPC account balance is above a threshold level, and Call Delivery is 32
provisioned, Call Delivery shall be supported. 33
34
35
Final routing information is required by the PPC system before accurate charging can be
36
applied against the PPC account.
37
38
Normal operation when a threshold condition is reached during a voice call 39
40
If the PPC account balance reaches a threshold level while one or more voice calls are in
41
progress, one of the following procedures can be used:
42

• The calls continue without interruption. 43


44
• If the PPC subscriber is engaged in one of the calls, the subscriber is notified. If 45
the subscriber is not engaged in one of the calls, the subscriber or the 46
subscriber’s proxy (e.g., voice mail system, assistant, etc.) may be notified. The 47
calls continue without interruption. 48
49
• If the PPC subscriber is engaged in one of the calls, the subscriber is notified 50
during the call. If the subscriber is not engaged in one of the calls, the 51
subscriber or the subscriber’s proxy may be notified. Every call that is not 52
ended in a timely manner is dropped. 53
54
If the PPC subscriber does not disconnect at the end of a call, the subscriber may be
55
connected to customer service or to an automatic system to enable the subscriber to refill
56
the account.
57
58
59
60

Pre-Paid Charging (PPC) 2-4 PPC Feature Description


PN-4287

1
If the PPC account balance reaches a threshold level, the invocation of another chargeable
2
service may be denied.
3
4
5 Notification may be provided by tone, announcement, voice mail, SMS, etc.
6 Notifications are played only to the PPC subscriber or to the subscriber’s proxy (e.g.
7 voice mail system), not to the other parties on the calls.
8
9 Normal operation with insufficient balance
10
11 If the PPC account balance is below a pre-set threshold, a notification shall be provided to
12 the subscriber. If the subscriber originates a call, the network may route the call to
13 customer service to help the subscriber to refill the account. Incoming calls may be given
14 the subscriber inaccessible treatment.
15
Some call cases may be allowed to proceed normally such as:
16
17 • Calls to emergency services
18
19 • Calls to and from customer service
20
21
Chargeable Events
22
23 The chargeable events for “All-Call” activation subscribers:
24
25
1. Voice call termination to a PPC subscriber
26
– beginning: alerting, or called party answers,
27
28 – end: disconnect (network- or user-initiated), or connection failure (radio or
29 network), or abandon, or reject, or no answer
30
31 2. Voice call origination by a PPC subscriber
32
– beginning: voice channel seizure, or ring back, or called party answers,
33
34 – end : busy, or disconnect (network- or user-initiated), or connection failure
35 (radio or network), or abandon, or no answer
36
37 3. Wireless services invoked on behalf of the PPC subscriber during a voice call:
38
39
– In cases where the invocation of services causes calls to be placed, these
40
calls are chargeable events with the same beginning and end conditions as
41
described above. Additionally, the activation or the invocation of services
42
may be chargeable events.
43
4. Wireless Services invoked on behalf of the PPC subscriber outside a voice call
44
45 – In cases where the invocation of wireless services causes calls to be placed,
46 these calls are chargeable events subject to the same beginning and end
47 conditions as described above. Additionally, the activation or the
48 invocation of wireless services may themselves be chargeable events.
49
50 5. Other charges associated with the PPC account (e.g. monthly fees.)
51
52
The chargeable events for “Single-Call” activation subscribers:
53
54 1. Voice call origination
55
56 – Same as “All-Calls chargeable events”
57
2. Services invoked on behalf of the PPC subscriber associated with the voice call
58
origination
59
60

PPC Feature Description 2-5 Pre-Paid Charging (PPC)


PN-4287

1
– In cases where the invocation of wireless services causes calls to be placed,
2
these calls are chargeable events subject to the same beginning and end
3
conditions as those described above. Additionally, the activation or the
4
invocation of wireless services may themselves be chargeable events.
5

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


7
8
9
Call Detail Record
10
11
The system should record call detail information for the following:
12
a. PPC activation 13
14
b. PPC de-activation 15
16
c. PPC invocation
17

See TIA/EIA-124 for the specific information to be included for each element. 18
19
20
21
5.A.2 Exception Procedures or Unsuccessful Outcome 22
23
24
Registration
25
26
None identified.
27
28
29
De-Registration
30
31
None identified.
32
33
34
Activation 35
36
Permanent Activation
37

If the subscriber is not authorized for a request, the system shall apply feature denial 38

treatment. 39
40
41
Demand Activation
42
If the subscriber is not authorized for the request, the system shall apply feature denial 43
treatment when activation is attempted. 44
45
46
If PPC cannot be activated, an indication shall be provided to the subscriber that PPC is
47
not available. If the subscriber is authorized for PUB, then PUB shall remain active and a
48
notice to this effect may also be presented to the subscriber.
49
50
51
De-Activation 52
53
If the subscriber is not authorized for a request, the system shall apply feature denial 54
treatment. 55
56

If PPC cannot be de-activated, a notification (e.g., SMS or tone) that PPC is still active 57

shall be presented to the subscriber. 58


59
60

Pre-Paid Charging (PPC) 2-6 PPC Feature Description


PN-4287

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

PPC Feature Description 2-7 Pre-Paid Charging (PPC)


PN-4287

1
5.A.3 Alternative Procedures 2
3
If the subscriber’s account balance is below the threshold, the subscriber may activate a 4
PUB account to obtain service. 5
6
7
5.A.4 Interactions With Other Wireless Services 8
9
10
Asynchronous Data Service (ADS) 11
12
Not applicable. 13
14
15
Call Delivery (CD) 16
17
PPC is invoked before CD. 18
19
20
Call Forwarding—Busy (CFB) 21
22
PPC is invoked before CFB. 23
24
25

Call Forwarding—Default (CFD) 26


27

PPC is invoked before CFD. 28


29
30
31
Call Forwarding—No Answer (CFNA)
32
33
PPC is invoked before CFNA.
34
35
36
Call Forwarding—Unconditional (CFU) 37
38
PPC is invoked before CFU. 39
40
41
Call Transfer (CT) 42
43
Interaction between PPC and CT is beyond the scope of this standard. 44
45
46
Call Waiting (CW) 47
48
PPC is invoked before CW. 49
50
51

Calling Name Presentation (CNAP) 52


53

PPC is invoked before CNAP. 54


55
56
57
Calling Name Restriction (CNAR)
58
59
None identified.
60

Pre-Paid Charging (PPC) 2-8 PPC Feature Description


PN-4287

1
Calling Number Identification Presentation (CNIP)
2
3
PPC is invoked before CNIP.
4
5
6
7
Calling Number Identification Restriction (CNIR)
8
9
None identified.
10
11
12 Conference Calling (CC)
13
14 Interaction between PPC and CC is beyond the scope of this standard.
15
16
17 Data Privacy (DP)
18
19 Not applicable.
20
21
22 Do Not Disturb (DND)
23
24 PPC is invoked before DND.
25
26
27
Emergency Services (9-1-1)
28
29
Emergency Services takes precedence over PPC.
30
31
32
Flexible Alerting (FA)
33
34
Interaction between PPC and FA is beyond the scope of this standard.
35
36
37
38
Group 3 Facsimile (G3 Fax)
39
40
Not applicable.
41
42
43 Incoming Call Screening (ICS)
44
45 PPC is invoked before ICS.
46
47
48 Message Waiting Notification (MWN)
49
50 PPC is invoked before MWN.
51
52
53 Mobile Access Hunting (MAH)
54
55 Interaction between PPC and MAH is beyond the scope of this standard.
56
57
58
59
60

PPC Feature Description 2-9 Pre-Paid Charging (PPC)


PN-4287

1
Network Directed System Selection (NDSS)
2
3
None identified.
4
5
6
Non-Public Mode Service (NP) 7
8
PPC interaction with NP is for further study. 9
10
11
Over-the-Air Service Provisioning (OTASP) 12
13
None identified. 14
15
16
Password Call Acceptance (PCA) 17
18
PPC is invoked before PCA. 19
20
21

Preferred Language (PL) 22


23

Announcements related to PPC should be presented to the PPC subscriber in subscriber’s 24

preferred language. 25
26
27
28
Pre-Paid Charging (PPC)
29
30
Not applicable.
31
32
33
Priority Access and Channel Assignment (PACA)
34
35
PPC is invoked before PACA.
36
37
38
Remote Feature Control (RFC) 39
40
Interaction between PPC and RFC is beyond the scope of this standard. 41
42
43
Selective Call Acceptance (SCA) 44
45
PPC is invoked before SCA. 46
47
48
Short Message Services (SMS) 49
50
Not applicable. 51
52
53

Subscriber Confidentiality (SC) 54


55

None identified. 56
57
58
59
60

Pre-Paid Charging (PPC) 2-10 PPC Feature Description


PN-4287

1
Subscriber PIN Access (SPINA)
2
3
PPC interaction with SPINA is for further study.
4
5
6
7
Subscriber PIN Intercept (SPINI)
8
9
PPC interaction with SPINI is for further study.
10
11
12 Three-Way Calling (3WC)
13
14 PPC is invoked before 3WC.
15
16
17 User Group ID (UGID)
18
19 PPC interaction with UGID is for further study.
20
21
22 Voice Message Retrieval (VMR)
23
24 PPC is invoked before VMR.
25
26
27
Voice Privacy (VP)
28
29
PPC is invoked before VP.
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PPC Feature Description 2-11 Pre-Paid Charging (PPC)


PN-4287

1
WIRELESS INTELLIGENT NETWORK CAPABILITIES FOR PRE-PAID CHARGING
2
CHAPTER 3
3
MODIFICATIONS TO TIA/EIA-41.1-D FUNCTIONAL OVERVIEW
4
5
6
7 CONTENTS
8
9
10
LIST OF FIGURES ......................................................................................................................................... ii
11
12
REVISION HISTORY.................................................................................................................................... iii
13
14
3 DEFINITIONS and DOCUMENTATION CONVENTIONS .......................................................... 1
15
16 3.2 DOCUMENTATION CONVENTIONS ............................................................................ 1
17 3.2.1 Scenario Diagram Conventions ............................................................................ 2
18 3.2.1.1 TCAP Package Type Diagram Conventions ................................... 5
19
3.2.1.2 BillingID Diagram Conventions ..................................................... 7
20
21
4 SYMBOLS AND ABBREVIATIONS.............................................................................................. 9
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.1-D Modifications 3-i Contents


PN-4287

LIST OF FIGURES 2
3
4
Figure 1 Diagrammatic Conventions ........................................................................... 3 5
Figure X TCAP Package Type Diagram Conventions ................................................. 5 6
Figure Y BillingID Diagram Conventions .................................................................... 7 7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
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 3-ii TIA/EIA-41.1-D Modifications


PN-4287

1
2
3
REVISION HISTORY
4
5
6
7 Rev. Date Remarks
8
0 May 2000 Approved For Publication
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.1-D Modifications 3-iii Revision History


PN-4287

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
(This page intentionally left blank.) 31
32
33
34
35
36
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 3-iv TIA/EIA-41.1-D Modifications


PN-4287

1
2
3
3 DEFINITIONS and DOCUMENTATION
4
5
CONVENTIONS
6
7
8
9
10 3.2 DOCUMENTATION CONVENTIONS
11 (TIA/EIA-41.1-D, page 1-11)
12
13 Each scenario description has two components:
14
• a scenario diagram, followed by
15
16 • a description of each step in the scenario diagram.
17
18 Each of these two components employs a set of documentation conventions, described in
19 Sections 3.2.1 and 3.2.2.
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.1-D Modifications 3-1 Documentation Conventions


PN-4287

1
3.2.1 Scenario Diagram Conventions 2
(TIA/EIA-41.1-D, page 1-11) 3
4
The scenarios presented in this document use the following diagrammatic conventions to
5
illustrate the information exchange between network entities:
6
7
Network Network Network 8
entity entity name entity role
Time 9
10
11

Originating System Serving System 12


13
non-TIA/EIA-41 MSC HLR VLR MSC 14
information flow
15
description
event 16
non-TIA/EIA-41 call origination identifier
a 17
information flow
18
from external LOCREQ event timing
b 19
source gridline
ROUTREQ 20
TIA/EIA-41 c 21
information flow:
ROUTREQ 22
invoke d extension of
message name 23
network entity
RRT 24
LRT RRT
25
TIA/EIA-41 QUALREQ optional 26
information flow e
(in this scenario)
qualreq QRT 27
TIA/EIA-41
Timer and f procedure 28
timer name routreq[TLDN] 29
g 30
TIA/EIA-41
TIA/EIA-41
routreq[TLDN] information flow: 31
information flow: h
parameter name or 32
response TLDNAT
locreq[TLDN] reference
message name i 33
34
call setup local event at
j network entity 35
non-TIA/EIA-41 36
information flow page or answer k 37
to external timeout
38
destination call release
l
39
call release non-TIA/EIA-41
Indefinite break 40
m information flow
in time 41
between
network entities 42
43
call origination
n 44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Documentation Conventions 3-2 TIA/EIA-41.1-D Modifications


PN-4287

1
Network Network Network
2
functional functional functional
3 entity entity name entity role Time
4
5
6 Originating System Serving System
7
8
non-IS-41 MSC HLR VLR MSC
information flow
9
description
10 event
non-IS-41 call origination identifier
11 information flow a
12 from external LOCREQ
b event timing
13 source
gridline
14 ROUTREQ
IS-41 c
15
information flow:
16
ROUTREQ extension of
invoke d network
17 message name
RRT functional entity
18 LRT RRT
19 IS-41 QUALREQ optional
20 information flow e
(in this scenario)
21 qualreq QRT IS-41 procedure
Timer and f
22
timer name routreq[TLDN]
23
g
24
IS-41
IS-41 routreq[TLDN] information flow:
25 information flow: h parameter name or
26 response TLDNAT
locreq[TLDN] reference
message name i
27 local event at
28 call setup network
j functional entity
29
non-IS-41
30 information flow page or answer k
31 to external timeout
destination call release
32 l
33 call release non-IS-41
Indefinite break
34 m information flow
in time
35 between network
functional entities
36
37
call origination
n
38
39
40
Figure 1 Diagrammatic Conventions
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.1-D Modifications 3-3 Documentation Conventions


PN-4287

1
The following items should be noted in figure 1:
2

1. Every event identifier must have an associated information flow. 3


4
2. Information flows are classified as either TIA/EIA-41 or non-TIA/EIA-41; the 5
former are subject to standardization in this document, while the latter are not. 6
7
3. Only network functional entities which are involved in an information flow (i.e., 8
source, destination, or tandem) are shown. 9
10
4. Use of parameter references, rather than the parameter names themselves, is
11
permitted (e.g., TLDN rather than Digits (Destination)) where this is deemed to
12
improve readability. However, the mapping of references to actual parameters
13
must be provided.
14

5. An TIA/EIA-41 operation’s INVOKE component is designated by an upper-case 15

acronym (e.g., LOCREQ); its RETURN RESULT is designated by a lower-case 16

acronym (e.g., locreq); its RETURN ERROR is designated by the full name 17

(e.g., LocationRequest RETURN ERROR). 18


19
6. Optional TIA/EIA-41 operations are enclosed by shaded areas. See events "e" 20
and "f". 21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Documentation Conventions 3-4 TIA/EIA-41.1-D Modifications


PN-4287

1
3.2.1.1 TCAP Package Type Diagram Conventions
2
(TIA/EIA/IS-771.3, page 3-5)
3
4
The following figure illustrates the diagrammatic conventions used to identify TCAP
5
package types for the information exchange between network entities.
6
7
Serving System Home System
8
9
10
MSC VLR HLR SCP
11
12
13 REGNOT [TRANSCAP]
a
14
15 REGNOT [TRANSCAP]
16
b
RNT RNT
17 regnot [ORIGTRIG]
18 c
19
regnot [ORIGTRIG]
20 d
21
22 call origination
23 e
24
Q+P 1 ORREQ [ORIGTRIG, DGTSDIAL, TRANSCAP]
25 f
26
Q+P 2 ORREQ [ORIGTRIG, DGTSDIAL, TRANSCAP]
27 g
TCAP
28 ORT
package C-P 2 RUIDIR [ANNLIST, DGTCC] ORT
29
type h
30
31 C-P 1 RUIDIR [ANNLIST, DGTCC]
i
32
33 prompt for digits
34
j
35 requested digits RUDT RUDT
36 k
37
Messages
within a single C+P 1 ruidir [DGTSDIAL]
38 l
39
TCAP
transaction C+P 2 ruidir [DGTSDIAL]
40 m
41
have the same
number ORT ORT
42 RES 2 orreq [TERMLIST]
designation n
43
44 RES 1 orreq [TERMLIST]
o
45
46 call setup
47 p
48
TCAP answer
49
package q
50
type U OANSWER [MSCID, MSID, BILLID, TOD, TDO]
51 r
52
53 Figure X TCAP Package Type Diagram Conventions
54
55
56 The following items should be noted in figure X:
57
58 1. TCAP package types are only shown for complex TCAP transactions (i.e., more
59 than two messages within the same TCAP transaction).
60

TIA/EIA-41.1-D Modifications 3-5 Documentation Conventions


PN-4287

1
2. The valid TCAP package types for complex TCAP transactions are:
2

• Q+P Query with Permission 3


4
• Q-P Query without Permission 5
6
• C+P Conversation with Permission 7
8
• C-P Conversation without Permission
9
• RES Response 10
11
• U Unidirectional 12
13
3. The number following the TCAP package type will be the same for all messages 14
within a single TCAP transaction. By definition, a TCAP transaction involves 15
only two network entities. The numbering begins at 1 in each figure and is 16
incremented for each complex TCAP transaction. 17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Documentation Conventions 3-6 TIA/EIA-41.1-D Modifications


PN-4287

1
3.2.1.2 BillingID Diagram Conventions
2
(New Section for TIA/EIA-41.D-1, Section 3.2.1)
3
4
The following figure illustrates the diagrammatic conventions used to identify BillingID
5
parameter values for the information exchange between network entities.
6
7
Serving System
8
9
10
SN VLR MSC
11
12
digits + SEND
13
a
14
15 BILLID1 ORREQ [MSCID, MSID, BILLID, DGTSDIAL, TRIGTYPE]
16
b
ORT
17 orreq [DMH_SVCID]
18 c
19
BILLID1 ANLYZD [MSCID, MSID, BILLID, DGTSDIAL, RoutingInfo, TRIGTYPE, TOD, TDO]
20 d
21 ANZT
anlyzd [ ]
22 e
23
24 call-1 setup
f
25
26 call-1 answer
g
27
28 BILLID1 OANSWER [MSCID, MSID, BILLID, TRIGTYPE, TOD, TDO]
29 h
30
answer
31 i
32
BillingID
33
value digits + SEND
34
35 j
36
37 call-1 hold k
38
39 BILLID2 ORREQ [MSCID, MSID, BILLID, DGTSDIAL, TRIGTYPE, FEATIND]
40
l
ORT
41 A call leg orreq [DMH_SVCID]
42 has one m
43 BillingID call-2 setup
44 value n
45
call-2 answer
46 o
47
48 BILLID2 OANSWER [MSCID, MSID, BILLID, FEATIND, TRIGTYPE, TOD, TDO]
p
49
50 answer
q
51
52 SEND
53 r
54
55 call-1 reconnect s
56
57
58
Figure Y BillingID Diagram Conventions
59 The following items should be noted in figure Y:
60

TIA/EIA-41.1-D Modifications 3-7 Documentation Conventions


PN-4287

1
1. BillingID values are only shown for multiple call leg scenarios.
2

2. The BillingID value (e.g., BILLID1) will be the same for a single call leg. 3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Documentation Conventions 3-8 TIA/EIA-41.1-D Modifications


PN-4287

1
2
3
4 SYMBOLS AND ABBREVIATIONS
4 (TIA/EIA-41.1-D, page 1-14)
5
6
AD Abbreviated Dialing
7 BDISCT Bulk Disconnection Timer
8 BULKDISCONN BulkDisconnection INVOKE
9
bulkdisconn BulkDisconnection RETURN RESULT
10
11 CALLSTATUS CallStatus parameter
12 CRREPORT CallRecoveryReport INVOKE
13
crreport CallRecoveryReport RETURN RESULT
14
15
CCDIR CallControlDirective INVOKE
16 ccdir CallControlDirective RETURN RESULT
17 CCDT Call Control Directive Timer
18
CNID ControlNetworkID parameter
19
20
CRID CallRecoveryID parameter
21 CRIDLIST CallRecoveryIDList parameter
22 CRRT Call Recovery Report Timer
23
DMH_SVCID DMH_ServiceID parameter
24
25 FEATIND FeatureIndicator parameter
26 OANSWER OAnswer INVOKE
27
ODISCONNECT ODisconnect INVOKE
28
29
odisconnect ODisconnect RETURN RESULT
30 ODT ODisconnect Timer
31 PPC Pre-Paid Charging
32
RELCAUSE ReleaseCause parameter
33
34
TANSWER TAnswer INVOKE
35 TDISCONNECT TDisconnect INVOKE
36 tdisconnect TDisconnect RETURN RESULT
37
TDO TimeDateOffset parameter
38
39 TDT TDisconnect Timer
40 TOD TimeOfDay parameter
41
UNRELCALLDATA UnreliableCallData INVOKE
42
43
unrelcalldata UnreliableCallData RETURN RESULT
44 URCDT Unreliable Call Data Timer
45 UCT Universal Coordinated Time
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.1-D Modifications 3-9 Symbols and Abbreviations


PN-4287

1
WIRELESS INTELLIGENT NETWORK CAPABILITIES FOR PRE-PAID CHARGING
2
CHAPTER 4
3
MODIFICATIONS TO TIA/EIA-41.3-D AUTOMATIC ROAMING INFORMATION FLOWS
4
5
6
7 CONTENTS
8
9
10
LIST OF FIGURES ........................................................................................................................................ iii
11
12
REVISION HISTORY..................................................................................................................................... v
13
14
8 WIRELESS INTELLIGENT NETWORK (WIN) SCENARIOS..................................................... 1
15
16 8.X WIN Pre-Paid Charging Scenarios ..................................................................................... 1
17 8.X.1 MS Registration .................................................................................................... 2
18 8.X.2 MS Call Origination: Calling Party Disconnect (SN Based) ............................... 3
19
8.X.3 MS Call Origination: Calling Party Disconnect ................................................... 6
20
21
8.X.4 MS Call Origination: Calling Party Disconnect - No Pre-Call
22
Announcement.................................................................................................... 11
23 8.X.5 MS Call Origination: Called Party Disconnect .................................................. 13
24 8.X.6 MS Call Origination: Called Party Disconnect (SN Based) ............................... 16
25 8.X.7 MS Call Origination with Mid-Call Indication of Low Balance........................ 18
26
8.X.8 MS Call Origination with Service Logic Directed Call Release ........................ 20
27
8.X.9 MS Call Origination with Insufficient Balance for Call Requested ................... 22
28
29
8.X.10 Three-Way Calling: Calling Party Disconnect ................................................... 23
30 8.X.11 Three-Way Calling: Called Party Disconnect .................................................... 29
31 8.X.12 Three-Way Calling: Loss of Radio Contact ....................................................... 32
32 8.X.13 Three-Way Calling: Insufficient Balance for Third-Party Call.......................... 34
33
8.X.14 Three-Way Calling: Mid-Call Low Balance Indication ..................................... 37
34
35
8.X.15 Three-Way Calling: Service Logic Directed Call Release ................................. 39
36 8.X.16 MS Call Origination with Abbreviated Dialing ................................................. 41
37 8.X.17 Abbreviated Dialing: Insufficient Balance for Service Invocation .................... 47
38 8.X.18 Abbreviated Dialing: Insufficient Balance for Call............................................ 49
39
8.X.19 Call Origination with Call Abandon ................................................................... 51
40
8.X.20 Call Origination: Charge Rate Dependent on MS Location ............................... 52
41
42
8.X.21 Call Delivery: Local Termination at Originating MSC...................................... 55
43 8.X.22 Call Delivery: Intersystem Termination ............................................................. 59
44 8.X.23 Call Delivery: Insufficient Account Balance ..................................................... 63
45 8.X.24 HLR-Based Call Forwarding No Answer........................................................... 64
46
8.X.25 SCP-Based Call Forwarding No Answer ........................................................... 68
47
48
8.X.26 HLR-Based Call Forwarding Busy..................................................................... 72
49 8.X.27 SCP-Based Call Forwarding Busy Invocation with Call Collision .................... 74
50 8.X.28 HLR-Based Call Forwarding Unconditional ...................................................... 77
51 8.X.29 SCP-Based Call Forwarding Unconditional ....................................................... 79
52
8.X.30 Call Forwarding Unconditional: Location Trigger Not Required for PPC ........ 81
53
8.X.31 Call Delivery with Call Waiting ......................................................................... 83
54
55
8.X.32 Mid-Call Verification of Call Status................................................................... 87
56 8.X.33 MS-to-MS Call: SN Based ................................................................................. 88
57 8.X.34 Call Delivery: Charge Rate Dependent on MS Location ................................... 95
58 8.X.35 MS Call Origination with Service Logic Directed Call to Customer
59 Service Center..................................................................................................... 98
60

TIA/EIA-41.3-D Modifications 4-i Contents


PN-4287

1
8.X.36 Call Delivery: Serving MSC is Not WIN Capable ........................................... 100
2
8.X.37 Three-Way Call to 9-1-1....................................................................................104 3
8.X.38 PPC Account Recovery After MSC Failure ..................................................... 107 4
8.X.39 SCF Failure Recovery....................................................................................... 108 5

8.X.40 Failure During SCF Failure Recovery.............................................................. 114 6


7

Annex Y (informative): PPC – Recovery From Temporary Node Failures .............................................. 115 8
9
Y.1 Introduction ..................................................................................................................... 115 10
Y.2 Underlying Principles ..................................................................................................... 116 11
12
Y.3 PPC Failure Recovery Actions ....................................................................................... 116
13
Y.3.1 Temporary Network Failure ............................................................................. 116
14
Y.3.1.1 MSC Failure Recovery Actions for Temporary Network 15
Failures........................................................................................ 117 16
Y.3.1.2 PPC SLP Failure Recovery Actions for Temporary Network 17
Failures........................................................................................ 117 18
Y.3.2 MSC Failure Recovery Actions........................................................................ 119 19

Y.3.3 SCF Failure Recovery Actions ......................................................................... 119 20


21
Y.3.3.1 Identifying Call Data for SCF Failure Recovery ........................ 120
22
Y.3.3.2 SIM Failure Recovery ................................................................. 120 23
24
25
26
27
28
29
30
31
32
33
34
35
36
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 4-ii TIA/EIA-41.3-D Modifications


PN-4287

1
2
3
LIST OF FIGURES
4
5 Figure 8.X.1 MS Registration ..................................................................................... 2
6
Figure 8.X.2 MS Call Origination: Calling Party Disconnect (SN Based) ................. 3
7
8
Figure 8.X.3 MS Call Origination: Calling Party Disconnect..................................... 7
9 Figure 8.X.4 MS Call Origination: Calling Party Disconnect - No Pre-Call
10 Announcement ..................................................................................... 11
11
Figure 8.X.5 MS Call Origination: Called Party Disconnect .................................... 13
12
13 Figure 8.X.6 MS Call Origination: Called Party Disconnect (SN Based) ................ 16
14 Figure 8.X.7 MS Call Origination with Mid-Call Indication of Low Balance ......... 18
15
Figure 8.X.8 MS Call Origination with Service Logic Directed Call Release.......... 20
16
17 Figure 8.X.9 MS Call Origination with Insufficient Balance for Call
18 Requested ............................................................................................. 22
19 Figure 8.X.10-1 Three-Way Calling: Calling Party Disconnect (1 of 2) ....................... 23
20
21
Figure 8.X.10-2 Three-Way Calling: Calling Party Disconnect (2 of 2) ....................... 24
22 Figure 8.X.11 Three-Way Calling: Called Party Disconnect ...................................... 29
23
Figure 8.X.12 Three-Way Calling: Loss of Radio Contact ......................................... 32
24
25
Figure 8.X.13 Three-Way Calling: Insufficient Balance for Third-Party Call ........... 34
26 Figure 8.X.14 Three-Way Calling: Mid-Call Low Balance Indication....................... 37
27
Figure 8.X.15 Three-Way Calling: Service Logic Directed Call Release................... 39
28
29 Figure 8.X.16-1 Call Origination with WIN-based Abbreviated Dialing (1 of 2) ......... 41
30 Figure 8.X.16-2 Call Origination with WIN-based Abbreviated Dialing (2 of 2) ......... 45
31
Figure 8.X.17 Abbreviated Dialing: Insufficient Balance for Service
32
Invocation ............................................................................................. 47
33
34 Figure 8.X.18 Abbreviated Dialing: Insufficient Balance for Call ............................. 49
35 Figure 8.X.19 Call Origination with Call Abandon .................................................... 51
36
37
Figure 8.X.20 MS Call Origination: Charge Rate Dependent on MS Location.......... 52
38 Figure 8.X.21 Call Delivery: Local Termination at Originating MSC ....................... 55
39
Figure 8.X.22 Call Delivery: Intersystem Termination............................................... 59
40
41
Figure 8.X.23 Call Delivery: Insufficient Account Balance ....................................... 63
42 Figure 8.X.24-1 HLR-Based Call Forwarding No Answer (1 of 2) ............................... 64
43
Figure 8.X.24-2 HLR-Based Call Forwarding No Answer (2 of 2) ............................... 67
44
45 Figure 8.X.25-1 SCP-Based Call Forwarding No Answer (1 of 2) ................................ 68
46 Figure 8.X.25-2 SCP-Based Call Forwarding No Answer (2 of 2) ................................ 71
47
Figure 8.X.26 HLR-Based Call Forwarding Busy ...................................................... 72
48
49 Figure 8.X.27-1 SCP-Based Call Forwarding Busy Invocation with Call Collision
50 (1 of 2) .................................................................................................. 74
51 Figure 8.X.27-2 SCP-Based Call Forwarding Busy Invocation with Call Collision
52 (2 of 2) .................................................................................................. 75
53
54
Figure 8.X.28 HLR-Based Call Forwarding Unconditional ....................................... 77
55 Figure 8.X.29 SCP-Based Call Forwarding Unconditional ........................................ 79
56
Figure 8.X.30 Call Forwarding Unconditional: Location Trigger Not Required
57
for PPC ................................................................................................. 81
58
59
Figure 8.X.31-1 Call Delivery with Call Waiting (1 of 2) ............................................. 83
60

TIA/EIA-41.3-D Modifications 4-iii List of Figures


PN-4287

1
Figure 8.X.31-2 Call Delivery with Call Waiting (2 of 2) ............................................. 85
2
Figure 8.X.32 Mid-Call Verification of Call Status ................................................... 87 3

Figure 8.X.33-1 MS-to-MS Call: SN Based (1 of 2)...................................................... 88 4


5
Figure 8.X.33-2 MS-to-MS Call: SN Based (2 of 2)...................................................... 92
6
Figure 8.X.34 Call Delivery: Charge Rate Dependent on MS Location ..................... 96 7

Figure 8.X.35 MS Call Origination with Service Logic Directed Call to 8

Customer Service Center ..................................................................... 98 9


10
Figure 8.X.36 Call Delivery: Serving MSC is Not WIN Capable ............................ 101 11
Figure 8.X.37-1 Three-Way Call to 9-1-1 (1 of 2) ........................................................104 12
13
Figure 8.X.37-2 Three-Way Call to 9-1-1 (2 of 2) ........................................................105
14
Figure 8.X.38 PPC Account Recovery After MSC Failure....................................... 107 15
Figure 8.X.39-1 SCF Failure Recovery (1 of 2) ........................................................... 109 16
17
Figure 8.X.39-2 SCF Failure Recovery (2 of 2) ........................................................... 112
18
Figure 8.X.40 Failure During SCF Failure Recovery ............................................... 114 19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
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 4-iv TIA/EIA-41.3-D Modifications


PN-4287

1
2
3
REVISION HISTORY
4
5
6 Rev. Date Remarks
7
0 May 2000 Approved for Publication
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-v Revision History


PN-4287

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
(This page intentionally left blank.) 31
32
33
34
35
36
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 4-vi TIA/EIA-41.3-D Modifications


PN-4287

1
2
3
8 WIRELESS INTELLIGENT NETWORK (WIN)
4
5
SCENARIOS
6
7
8
9 8.X WIN Pre-Paid Charging Scenarios
10
(New Section for TIA/EIA-41.3-D)
11
12 This section depicts the interactions between network entities in various situations related
13 to automatic roaming and Pre-Paid Charging (PPC) for WIN applications. These
14 scenarios are for illustrative purposes only.
15
16 Unless otherwise noted, the scenarios in this section depict features operating individually
17 (i.e., feature interactions are not considered unless specifically noted).
18
The scenarios in this section do not include a complete listing of operation parameters,
19
either in the figures or in the accompanying text descriptions. Parameters are included
20
where they are deemed necessary to improve the understanding of the scenario. For a
21
complete description of the parameters associated with each operation, refer to Chapter 5.
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-1 Pre-Paid Charging


PN-4287

8.X.1 MS Registration 2
3
4
This scenario describes MS registration in a new serving system by a PPC subscriber with
5
PPC active and an account balance above threshold.
6
7
Serving System
8
9
HLR VLR MSC 10
11
12
REGNOT [MSCID, MSID, ESN, TRANSCAP, WINCAP, QUALCODE]
13
a
14
REGNOT [MSCID, MSID, ESN, TRANSCAP, WINCAP, QUALCODE] 15
b 16
RNT RNT
regnot [Profile {TRIGADDRLIST}] 17
c 18
19
regnot [Profile {TRIGADDRLIST}]
d 20
21
Figure 8.X.1 MS Registration 22
23
24
a. The Serving MSC determines that a roaming MS is within its service area. The 25
Serving MSC sends a REGNOT to its VLR requesting subscriber profile and 26
authorization information. The TRANSCAP parameter is set to indicate the Serving 27
MSC can process the TRIGADDRLIST parameter. The WINCAP parameter is set 28
to indicate the WIN capabilities of the Serving MSC. 29
30
Parameters Usage Type
31
MSCID Serving MSC MSCID. R 32
33
MSID Served MS MSID. R
34
ESN Served MS ESN. R 35
36
TRANSCAP Serving MSC’s transaction capability. R
37

WINCAP Serving MSC’s WIN capability. R 38


39
QUALCODE Type of qualification information required. R 40
41
b. The Serving VLR determines the MS is not known to the VLR. The Serving VLR
42
forwards the REGNOT to the HLR associated with the MS.
43

c. The HLR determines that authorization can be granted to the MS. It returns the 44

requested information to the Serving VLR in the regnot. The TRIGADDRLIST 45

parameter is set to indicate the Origination_Attempt_Authorized, 46

Calling_Routing_Address_Available, O_Answer, O_Disconnect, T_Answer, and 47

T_Disconnect triggers are active and to specify routing to the network entity (e.g., 48

SCP, SN) that contains the PPC service logic program. 49


50
Note: the TRIGADDRLIST parameter may also arm triggers for other WIN 51
services. 52
53
d. The VLR forwards the regnot to the Serving MSC. 54
55
56
57
58
59
60

Pre-Paid Charging 4-2 TIA/EIA-41.3-D Modifications


PN-4287

1
2 8.X.2 MS Call Origination: Calling Party Disconnect (SN Based)
3
4
This scenario describes PPC invocation upon call origination by a PPC subscriber with
5
PPC active and an account balance above threshold. The calling MS disconnects first and
6
no end of call announcement is provided to the subscriber.
7
8
Serving System
9
10
11
SN MSC
12
13
MS origination
14
a
15
16 ORREQ [MSCID, MSID, MDN, BILLID, DGTSDIAL, TRIGTYPE]
17
b
ORT
18 orreq [DMH_SVCID]
19 c
20 ANLYZD [MSCID, MSID, MDN, BILLID, DGTSDIAL, RoutingInfo, TRIGTYPE, TOD, TDO]
21 d
22 ANZT
CONNRES [DSTDGTS, CARDGTS, ROUTDGTS]
23 e
24
TLDNAT
25 call setup
f
26
SSFT
27 announcement
g
28
29 anlyzd [ ]
30 h
31
call release
32 i
33
call setup
34 j
35
36
answer
k
37
38 OANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO]
l
39
40 answer
41
m
42
43
disconnect
44 n
45 ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]
46 o
47 ODT
48
odisconnect [ ]
p
49
50 call release
q
51
52
Figure 8.X.2 MS Call Origination: Calling Party Disconnect (SN Based)
53
54
55 a. An MS call origination with dialed digits is received by the Serving MSC.
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-3 Pre-Paid Charging


PN-4287

1
b. The Serving MSC detects the Origination_Attempt_Authorized trigger and sends an
2
ORREQ to the SN associated with this trigger.
3
Parameters Usage Type 4
5
MSCID Serving MSC MSCID. R
6

MSID Served MS MSID. R 7


8
MDN Mobile directory number. Include if available. O 9

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


11
DGTSDIAL Digits entered by served MS. R 12
13
TRIGTYPE Indicates the trigger encountered. R
14
c. The SN determines the subscriber has PPC active and the subscriber’s account 15
balance is above the threshold level. The SN sends an orreq to the Serving MSC 16
to indicate call processing shall continue. The DMH_SVCID parameter is set to 17
indicate that PPC was invoked. 18
19
d. The Serving MSC analyzes the dialed digits and prepares to route the call. The 20
MSC detects the Calling_Routing_Address_Available trigger and sends an ANLYZD 21
to the SN associated with this trigger. 22
23
Parameters Usage Type
24
MSCID Serving MSC MSCID. R 25
26
MSID Served MS MSID. R
27
MDN Mobile directory number. Include if available. O 28
29
BILLID BillingID. Used to relate queries for this call. R
30

DGTSDIAL Digits entered by served MS. O 31


32
RoutingInfo: Call routing information: 33

[DSTDGTS] DestinationDigits. The network address of the R 34


destination. 35
36
[CARDGTS] CarrierDigits. Interexchange carrier for call O
37
setup. Include if applicable.
38
[ROUTDGTS] RoutingDigits. Special routing instructions. O 39
Include if applicable. 40
41
TRIGTYPE Indicates the trigger encountered. R
42
TOD TimeOfDay. The current time (UTC). R 43
44
TDO TimeDateOffset. The time offset of local civil R
45
time.
46
e. The SN sends a CONNRES to the Serving MSC with instructions to set up a call leg 47
to the SN. 48
49
Parameters Usage Type 50

DSTDGTS DestinationDigits. The network address of the R 51

destination. 52
53
CARDGTS CarrierDigits. Interexchange carrier for call O 54
setup. Include if applicable.
55

ROUTDGTS RoutingDigits. Special routing instructions. O 56


Include if applicable. 57
58
f. The MSC sets up the call leg to the SN. 59
60

Pre-Paid Charging 4-4 TIA/EIA-41.3-D Modifications


PN-4287

1
g. The SN plays an announcement to the MS indicating the current account balance.
2
3 h. The SN sends an anlyzd to the MSC.
4
5 i. The Serving MSC releases the call leg to the SN.
6
7
j. The MSC extends the MS originated call.
8
k. The call is answered by the called party.
9
10 l. The Serving MSC detects the O_Answer trigger and sends an OANSWER to the SN
11 associated with this trigger.
12
13
Parameters Usage Type
14 MSCID Serving MSC MSCID. R
15
16 MSID Served MS MSID. R
17
MDN Mobile directory number. Include if available. O
18
19 BILLID BillingID. Used to relate queries for this call. R
20
TRIGTYPE Indicates the trigger encountered. R
21
22 TOD TimeOfDay. The time of call answer (UTC). R
23
TDO TimeDateOffset. The time offset of local civil R
24
time.
25
26 Upon receipt of the OANSWER, the SN begins decrementing the subscriber’s
27 account balance.
28
29 m. The call is cut through and connected.
30
31
n. The MS ends the call.
32
o. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT
33
to the SN associated with this trigger.
34
35 Parameters Usage Type
36
MSCID Serving MSC MSCID. R
37
38 MSID Served MS MSID. R
39
MDN Mobile directory number. Include if available. O
40
41 BILLID BillingID. Used to relate queries for this call. R
42
43
TRIGTYPE Indicates the trigger encountered. R
44 RELCAUSE Call release cause. R
45
46 TOD TimeOfDay. The time of call disconnect (UTC). R
47
TDO TimeDateOffset. The time offset of local civil R
48 time.
49
50 Upon receipt of the ODISCONNECT, the SN stops decrementing the subscriber’s
51 account balance.
52
53
p. The SN sends an empty odisconnect to the Serving MSC.
54
q. The Serving MSC releases the call.
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-5 Pre-Paid Charging


PN-4287

8.X.3 MS Call Origination: Calling Party Disconnect 2


3
4
This scenario describes PPC invocation upon call origination by a PPC subscriber with
5
PPC active and an account balance above threshold. The calling party disconnects first,
6
hence no end of call announcement is provided.
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
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 4-6 TIA/EIA-41.3-D Modifications


PN-4287

1
2 Serving System
3
4 IP SCP MSC
5
6
7
MS origination
a
8
ORREQ [MSCID, MSID, MDN, BILLID, DGTSDIAL, TRIGTYPE]
9
b
10
ORT
11 orreq [DMH_SVCID]
12
c
13
ANLYZD [MSCID, TRANSCAP, WINCAP, MSID, MDN, BILLID,
14
DGTSDIAL, RoutingInfo, TRIGTYPE, TOD, TDO]
d
15
16 SEIZERES [SRFCapability, PLIND]
e
17
SZRT ANZT
18 seizeres [TLDN]
19 f
20
CONNRES [DSTDGTS, CARDGTS, ROUTDGTS]
21 TLDNAT g
22 WINRT
call setup
23 h
24
25
INSTREQ
i
26
IRT
27 SRFDIR [ANNLIST]
SSFT j
28
SRFDT
29 announcement
30
k
31 srfdir [ ]
32 l
33
anlyzd [ ]
34 m
35 IRT
call release
36 n
37
38 instreq
o
39
40 call setup
p
41
42 answer
43 q
44 OANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO]
45 r
46
answer
47 s
48
49 disconnect
50 t
51 ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]
52 u
53 ODT
odisconnect [ ]
54 v
55
56 call release
w
57
58
Figure 8.X.3 MS Call Origination: Calling Party Disconnect
59
60

TIA/EIA-41.3-D Modifications 4-7 Pre-Paid Charging


PN-4287

1
a. An MS call origination with dialed digits is received by the Serving MSC.
2

b. The Serving MSC detects the Origination_Attempt_Authorized trigger and sends an 3

ORREQ to the SCP associated with this trigger. 4


5
Parameters Usage Type 6
7
MSCID Serving MSC MSCID. R
8
MSID Served MS MSID. R 9
10
MDN Mobile directory number. Include if available. O
11
BILLID BillingID. Used to relate queries for this call. R 12
13
DGTSDIAL Digits entered by served MS. R
14
TRIGTYPE Indicates the trigger encountered. R 15
16
c. The SCP determines the subscriber has PPC active and the subscriber’s account 17
balance is above the threshold level. The SCP sends an orreq to the Serving MSC 18
to indicate that call processing shall continue. The DMH_SVCID parameter is set 19
to indicate that PPC was invoked. 20
21
d. The Serving MSC analyzes the dialed digits and prepares to route the call. The
22
MSC detects the Calling_Routing_Address_Available trigger and sends an ANLYZD
23
to the SCP associated with this trigger.
24

Parameters Usage Type 25


26
MSCID Serving MSC MSCID. R 27

TRANSCAP Serving MSC’s transaction capability. R 28


29
WINCAP Serving MSC’s WIN capability. R 30
31
MSID Served MS MSID. R
32
MDN Mobile directory number. Include if available. O 33
34
BILLID BillingID. Used to relate queries for this call. R
35
DGTSDIAL Digits entered by served MS. O 36
37
RoutingInfo: Call routing information:
38
[DSTDGTS] DestinationDigits. The network address of the R 39
destination. 40
41
[CARDGTS] CarrierDigits. Interexchange carrier for call O
setup. Include if applicable. 42
43
[ROUTDGTS] RoutingDigits. Special routing instructions. O 44
Include if applicable.
45

TRIGTYPE Indicates the trigger encountered. R 46


47
TOD TimeOfDay. The current time (UTC). R 48

TDO TimeDateOffset. The time offset of local civil R 49

time. 50
51
52
53
54
55
56
57
58
59
60

Pre-Paid Charging 4-8 TIA/EIA-41.3-D Modifications


PN-4287

1
e. The SCP determines that an IP is required to play an announcement to the MS with
2
the subscriber’s current account balance. The SCP sends a SEIZERES to an IP
3
requesting the resource.
4
5 Parameters Usage Type
6
SRFCapability: Specifies the specialized resource capabilities R
7
requested:
8
9 [SpecializedResource] Indicates the type of standard specialized O
10 resource requested.
11
[PrivateSpecializedResource] Indicates the type of private specialized O
12 resource requested.
13
14 PLIND PreferredLanguageIndicator. Indicates the O
15
preferred language.
16
f. When the IP receives the SEIZERES, it allocates a TLDN to the appropriate
17
resource. The TLDN is returned to the SCP in the seizeres.
18
19 g. The SCP sends a CONNRES to the Serving MSC with instructions to set up a call
20 leg to the IP.
21
22 Parameters Usage Type
23
DSTDGTS DestinationDigits. The network address of the R
24 destination.
25
26 CARDGTS CarrierDigits. Interexchange carrier for call O
27
setup. Include if applicable.
28 ROUTDGTS RoutingDigits. Special routing instructions. O
29 Include if applicable.
30
31 h. The Serving MSC sets up the call leg to the IP.
32
33
i. When the call is detected at the IP, the IP sends an INSTREQ to the SCP requesting
34
call processing instructions.
35
j. The SCP sends an SRFDIR to the IP with the ANNLIST parameter indicating the
36
announcement to play.
37
38 k. The IP plays the announcement indicated by the ANNLIST parameter.
39
40 l. The IP sends an empty srfdir to the SCP.
41
m. The SCP sends an anlyzd to the Serving MSC.
42
43 n. The Serving MSC releases the call leg to the IP.
44
45 o. The SCP sends an instreq to the IP to conclude the SCP-IP conversation.
46
47
Note: the SCP may send the instreq to the IP at any time after Step-l.
48
p. The Serving MSC extends the MS originated call.
49
50 q. The call is answered by the called party.
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-9 Pre-Paid Charging


PN-4287

1
r. The Serving MSC detects the O_Answer trigger and sends an OANSWER to the SCP
2
associated with this trigger.
3
Parameters Usage Type 4
5
MSCID Serving MSC MSCID. R
6

MSID Served MS MSID. R 7


8
MDN Mobile directory number. Include if available. O 9

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


11
TRIGTYPE Indicates the trigger encountered. R 12
13
TOD TimeOfDay. The time of call answer (UTC). R
14
TDO TimeDateOffset. The time offset of local civil R 15
time. 16
17
Upon receipt of the OANSWER, the SCP begins decrementing the subscriber’s
18
account balance.
19

s. The call is cut through and connected. 20


21
t. The (calling) MS ends the call. 22
23
u. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT 24
to the SCP associated with this trigger. 25
26
Parameters Usage Type
27
MSCID Serving MSC MSCID. R 28
29
MSID Served MS MSID. R
30
MDN Mobile directory number. Include if available. O 31
32
BILLID BillingID. Used to relate queries for this call. R
33
TRIGTYPE Indicates the trigger encountered. R 34
35
RELCAUSE Call release cause. R
36

TOD TimeOfDay. The time of call disconnect (UTC). R 37


38
TDO TimeDateOffset. The time offset of local civil R 39
time.
40
41
Upon receipt of the ODISCONNECT, the SCP stops decrementing the subscriber’s
42
account balance.
43
v. The SCP sends an odisconnect to the Serving MSC. 44
45
w. The Serving MSC releases the call. 46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Pre-Paid Charging 4-10 TIA/EIA-41.3-D Modifications


PN-4287

1
2 8.X.4 MS Call Origination: Calling Party Disconnect - No Pre-Call
3
Announcement
4
5
This scenario differs from the previous scenario in that no announcement is played when
6
an MS originates the call to inform the subscriber of their current account balance. The
7
calling party disconnects first and there is no end of call announcement.
8
9
Serving System
10
11
12 IP SCP MSC
13
14
MS origination
15 a
16
ORREQ [MSCID, MSID, MDN, BILLID, DGTSDIAL, TRIGTYPE]
17
b
18
ORT
19 orreq [DMH_SVCID]
c
20
ANLYZD [MSCID, TRANSCAP, WINCAP, MSID, MDN, BILLID,
21
DGTSDIAL, RoutingInfo, TRIGTYPE, TOD, TDO]
22 d
23
ANZT
24 anlyzd [ ]
e
25
26 call setup
f
27
28 answer
29 g
30 OANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO]
31 h
32
answer
33 i
34
35 disconnect
36 j
37 ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]
38 k
39 ODT
odisconnect [ ]
40 l
41
42 call release
m
43
44
Figure 8.X.4 MS Call Origination: Calling Party Disconnect - No Pre-Call Announcement
45
46
47 a. An MS call origination with dialed digits is received by the Serving MSC.
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-11 Pre-Paid Charging


PN-4287

1
b. The Serving MSC detects the Origination_Attempt_Authorized trigger and sends an
2
ORREQ to the SCP associated with this trigger.
3
Parameters Usage Type 4
5
MSCID Serving MSC MSCID. R
6

MSID Served MS MSID. R 7


8
MDN Mobile directory number. Include if available. O 9

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


11
DGTSDIAL Digits entered by served MS. R 12
13
TRIGTYPE Indicates the trigger encountered. R
14
c. The SCP determines the subscriber has PPC active and the subscriber’s account 15
balance is above the threshold level. The SCP sends an orreq to the Serving MSC 16
to indicate that call processing shall continue. The DMH_SVCID parameter is set 17
to indicate that PPC was invoked. 18
19
d. The Serving MSC analyzes the dialed digits and prepares to route the call. The 20
MSC detects the Calling_Routing_Address_Available trigger and sends an ANLYZD 21
to the SCP associated with this trigger. 22
23
Parameters Usage Type
24
MSCID Serving MSC MSCID. R 25
26
TRANSCAP Serving MSC’s transaction capability. R
27
WINCAP Serving MSC’s WIN capability. R 28
29
MSID Served MS MSID. R
30

MDN Mobile directory number. Include if available. O 31


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

DGTSDIAL Digits entered by served MS. O 34


35
RoutingInfo: Call routing information: 36

[DSTDGTS] DestinationDigits. The network address of the R 37

destination. 38
39
[CARDGTS] CarrierDigits. Interexchange carrier for call O
40
setup. Include if applicable.
41
[ROUTDGTS] RoutingDigits. Special routing instructions. O 42
Include if applicable. 43
44
TRIGTYPE Indicates the trigger encountered. R
45
TOD TimeOfDay. The current time (UTC). R 46
47
TDO TimeDateOffset. The time offset of local civil R
48
time.
49

e. The SCP determines that call processing shall continue and that the MS does not 50

have to be informed of the subscriber’s account balance at this time. The SCP sends 51

an anlyzd to the Serving MSC. 52


53
f-m. Same as Section 8.X.3, Steps p-w. 54
55
56
57
58
59
60

Pre-Paid Charging 4-12 TIA/EIA-41.3-D Modifications


PN-4287

1
2 8.X.5 MS Call Origination: Called Party Disconnect
3
4
This scenario describes PPC invocation upon call origination by a PPC subscriber with
5
PPC active and an account balance above threshold. The called party ends the call first
6
and the O_Disconnect trigger is detected. In this scenario, the updated account balance is
7
provided to the subscriber at the end of the call.
8
9
Serving System
10
11
12
IP SCP MSC
13
14
15
MS Call Origination: Same as Section 8.X.3, Steps a-s
16
17
18
19 disconnect
20 t
21 ODISCONNECT [MSCID, TRANSCAP, WINCAP, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]
22 u
23
SEIZERES [SRFCapability, PLIND]
24 v
25
SZRT ODT
26 seizeres [TLDN]
w
27
28 CONNRES [DSTDGTS, CARDGTS, ROUTDGTS]
TLDNAT x
29
WINRT
30 call setup
31 y
32
INSTREQ
33 z
34 IRT
SRFDIR [EXESCR]
35 SSFT aa
36 SRFDT
37
announcement
bb
38
39 srfdir [SCRRESULT ]
cc
40
41 odisconnect [ ]
42
dd
IRT
43 call release
44 ee
45
instreq
46 ff
47
release
48 gg
49
50 Figure 8.X.5 MS Call Origination: Called Party Disconnect
51
52
53 a-s. Same as Section 8.X.3, Steps a-s.
54
55
t. The MSC receives a called party disconnect indication. The MSC releases the call
56
leg toward the called party.
57
58
59
60

TIA/EIA-41.3-D Modifications 4-13 Pre-Paid Charging


PN-4287

1
u. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT
2
to the SCP associated with this trigger.
3
Parameters Usage Type 4
5
MSCID Serving MSC MSCID. R
6

TRANSCAP Serving MSC’s transaction capability. R 7


8
WINCAP Serving MSC’s WIN capability. R 9

MSID Served MS MSID. R 10


11
MDN Mobile directory number. Include if available. O 12
13
BILLID BillingID. Used to relate queries for this call. R
14
TRIGTYPE Indicates the trigger encountered. R 15
16
RELCAUSE Call release cause. R
17
TOD TimeOfDay. The time of call disconnect (UTC). R 18
19
TDO TimeDateOffset. The time offset of local civil R
20
time.
21

Upon receipt of the ODISCONNECT, the SCP stops decrementing the subscriber’s 22

account balance. 23
24
v. The SCP determines that an IP is required to play an announcement to the MS with 25
the subscriber’s new account balance. The SCP sends a SEIZERES to an IP 26
requesting the necessary resource. 27
28
w. When the IP receives the SEIZERES, it allocates a TLDN to the appropriate 29
resource. The TLDN is returned to the SCP in the seizeres. 30
31
x. The SCP sends a CONNRES to the Serving MSC with instructions to set up a call
32
leg to the IP.
33
Parameters Usage Type 34
35
DSTDGTS DestinationDigits. The network address of the R
36
destination.
37
CARDGTS CarrierDigits. Interexchange carrier for call O 38
setup. Include if applicable. 39
40
ROUTDGTS RoutingDigits. Special routing instructions. O
41
Include if applicable.
42
y. The Serving MSC sets up the call leg to the IP. 43
44
z. When the call is detected at the IP, the IP sends an INSTREQ to the SCP requesting 45
call processing instructions. 46
47
aa. The SCP sends an SRFDIR to the IP with the EXESCR parameter indicating the
48
announcement to play.
49

Note: The SCP may include the ANNLIST parameter instead of the EXESCR 50

parameter to indicate the announcement to play. 51


52
bb. The IP plays the announcement indicated by the EXESCR parameter to the MS. 53
The announcement indicates the updated account balance. 54
55
cc. The IP sends an srfdir to the SCP. The SCRRESULT parameter indicates the 56
announcement was played. 57
58
dd. The SCP sends an odisconnect to the Serving MSC.
59
60

Pre-Paid Charging 4-14 TIA/EIA-41.3-D Modifications


PN-4287

1
ee. The Serving MSC releases the call leg to the IP.
2
3 ff. The SCP sends an instreq to the IP to conclude the SCP-IP transaction.
4
5 gg. The Serving MSC releases the MS.
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-15 Pre-Paid Charging


PN-4287

8.X.6 MS Call Origination: Called Party Disconnect (SN Based) 2


3
4
This scenario describes PPC invocation upon call origination by a PPC subscriber with
5
PPC active and an account balance above threshold. The called party ends the call and
6
the O_Disconnect trigger is detected. The updated account balance may be provided to
7
the subscriber at the end of the call. An SN provides the service control function and
8
specialized resource function.
9
10
Serving System
11
12
SN MSC 13
14
15
16
MS Call Origination: Same as Section 8.X.2, Steps a-m
17
18
19

disconnect 20
n 21

ODISCONNECT [MSCID, TRANSCAP, WINCAP, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO] 22
o 23

ODT 24
25
CONNRES [DSTDGTS, CARDGTS, ROUTDGTS] 26
p
27
TLDNAT
call setup 28
q
29
SSFT
announcement 30
r 31

DISCONNRES [ ] 32
s 33
ODT 34
call release
t 35
36
odisconnect [ ]
u 37
38
release 39
v
40
41
Figure 8.X.6 MS Call Origination: Called Party Disconnect (SN Based)
42
43

a-m. Same as Section 8.X.2, Steps a-m. 44


45
n. The MSC receives a called party disconnect indication. The MSC releases the call 46
leg toward the called party. 47
48
49
50
51
52
53
54
55
56
57
58
59
60

Pre-Paid Charging 4-16 TIA/EIA-41.3-D Modifications


PN-4287

1
o. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT
2
to the SN associated with this trigger.
3
4 Parameters Usage Type
5
MSCID Serving MSC MSCID. R
6
7 TRANSCAP Serving MSC’s transaction capability. R
8
9
WINCAP Serving MSC’s WIN capability. R
10 MSID Served MS MSID. R
11
12 MDN Mobile directory number. Include if available. O
13
BILLID BillingID. Used to relate queries for this call. R
14
15 TRIGTYPE Indicates the trigger encountered. R
16
RELCAUSE Call release cause. R
17
18 TOD TimeOfDay. The time of call disconnect (UTC). R
19
TDO TimeDateOffset. The time offset of local civil R
20
time.
21
22 Upon receipt of the ODISCONNECT, the SN stops decrementing the subscriber’s
23 account balance.
24
25 p. If the SN determines that an announcement shall be played to the MS with the
26 subscriber’s new account balance, it sends a CONNRES to the Serving MSC with
27 instructions to set up a call leg to the SN.
28
Parameters Usage Type
29
30 DSTDGTS DestinationDigits. The network address of the R
31 destination.
32
CARDGTS CarrierDigits. Interexchange carrier for call O
33
setup. Include if applicable.
34
35 ROUTDGTS RoutingDigits. Special routing instructions. O
36 Include if applicable.
37
38
q. The Serving MSC sets up the call leg to the SN.
39
r. The SN plays an announcement to the MS indicating the updated account balance.
40
41 s. The SN sends a DISCONNRES to the Serving MSC indicating the call leg to the SN
42 shall be released.
43
44 t. The Serving MSC releases the call leg to the SN.
45
u. The SN sends an odisconnect to the Serving MSC.
46
47 v. The Serving MSC releases the MS.
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-17 Pre-Paid Charging


PN-4287

8.X.7 MS Call Origination with Mid-Call Indication of Low Balance 2


3
4
This scenario describes PPC invocation upon call origination with the “mid-call”
5
indication of low balance.
6
7
Serving System
8
9
IP SCP MSC 10
11
12
13
MS Call Origination: Same as Section 8.X.3, Steps a-s
14
15
16

CCDIR [MSCID, MSID, MDN, BILLID, ANNLIST] 17


t 18
19
low balance warning
CCDT u 20
21
ccdir [ ]
v 22
23
disconnect 24
w
25
ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO] 26
x
27
ODT
odisconnect [ ] 28
y 29
30
call release
z 31
32
Figure 8.X.7 MS Call Origination with Mid-Call Indication of Low Balance 33
34
35
a-s. Same as Section 8.X.3, Steps a-s. 36
37
t. The subscriber’s account balance reaches a threshold level and the SCP sends a
38
CCDIR to the Serving MSC with the ANNLIST parameter indicating that a low
39
balance warning (i.e., tone or announcement) be played to the MS.
40
Parameters Usage Type 41
42
MSCID SCP MSCID. Include to identify the requesting R
43
network entity.
44
MSID Served MS MSID. R 45
46
MDN Mobile directory number. Include if available. O
47

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


49
ANNLIST List of tones or announcements to play. R 50
51
u. The Serving MSC applies the low balance warning to the MS. The low balance
52
warning is only applied to the calling MS (i.e., the called party does not hear the
53
warning).
54

v. The Serving MSC sends a ccdir to the SCP indicating the requested action was 55

completed. 56
57
w. The MS ends the call. 58
59
60

Pre-Paid Charging 4-18 TIA/EIA-41.3-D Modifications


PN-4287

1
x-z. Same as Section 8.X.3, Steps u-w.
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-19 Pre-Paid Charging


PN-4287

8.X.8 MS Call Origination with Service Logic Directed Call Release 2


3
4
This scenario describes PPC invocation upon call origination with service logic directed
5
call release.
6
7
Serving System
8
9
IP SCP MSC 10
11
12
13
MS Call Origination: Same as Section 8.X.3, Steps a-s
14
15
16

CCDIR [MSCID, MSID, MDN, BILLID, ANNLIST] 17


t 18
19
low balance warning
CCDT u 20
21
ccdir [ ]
v 22
23
24
25
CCDIR [MSCID, MSID, MDN, BILLID, ANNLIST, ACTCODE]
w 26
27
disconnect warning
x 28
29
CCDT
call release 30
y
31
ccdir [ ] 32
z
33
ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO] 34
aa 35
ODT 36
odisconnect [ ]
bb 37
38
release
cc 39
40
Figure 8.X.8 MS Call Origination with Service Logic Directed Call Release 41
42
43
a-s. Same as Section 8.X.3, Steps a-s. 44
45
t-v. Same as Section 8.X.7, Steps t-v. 46
47
w. The SCP determines the call shall be disconnected (e.g., a PPC service logic
48
program instance timer expires). The SCP sends a CCDIR to the Serving MSC.
49
The ANNLIST parameter indicates that the disconnect warning (i.e., tone or
50
announcement) shall be played to the MS. The ACTCODE parameter indicates the
51
call shall be disconnected.
52
x. The Serving MSC plays the disconnect warning. The disconnect warning is only 53
applied to the calling MS (i.e., the called party does not hear the warning). 54
55
y. The Serving MSC releases the call leg to the called party. 56
57
z. The Serving MSC sends a ccdir to the SCP reporting the action was completed.
58
59
60

Pre-Paid Charging 4-20 TIA/EIA-41.3-D Modifications


PN-4287

1
aa. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT
2
to the SCP associated with this trigger.
3
4 Parameters Usage Type
5
MSCID Serving MSC MSCID. R
6
7 MSID Served MS MSID. R
8
9
MDN Mobile directory number. Include if available. O
10 BILLID BillingID. Used to relate queries for this call. R
11
12 TRIGTYPE Indicates the trigger encountered. R
13
RELCAUSE Call release cause. R
14
15 TOD TimeOfDay. The time of call disconnect (UTC). R
16
TDO TimeDateOffset. The time offset of local civil R
17
time.
18
19 bb. The SCP sends an empty odisconnect to the Serving MSC.
20
21 cc. The Serving MSC releases the MS.
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-21 Pre-Paid Charging


PN-4287

8.X.9 MS Call Origination with Insufficient Balance for Call Requested 2


3
4
This scenario describes PPC invocation upon call origination with insufficient balance for
5
the call requested.
6
7
Serving System
8
9
SCP MSC 10
11
12
MS origination
a 13
14
ORREQ [MSCID, MSID, MDN, BILLID, DGTSDIAL, TRIGTYPE]
b 15

ORT 16
orreq [DMH_SVCID] 17
c
18
ANLYZD [MSCID, TRANSCAP, MSID, MDN, BILLID, DGTSDIAL, RoutingInfo, TRIGTYPE, TOD, TDO] 19
d
20
ANZT
anlyzd [ANNLIST, ACCDEN] 21
e 22

announcement 23
f 24
25
release
g 26
27
Figure 8.X.9 MS Call Origination with Insufficient Balance for Call Requested 28
29
30
a-d. Same as Section 8.X.3, Steps a-d. 31
32
e. The subscriber’s account balance is not sufficient for the call origination requested.
33
The SCP sends an anlyzd to the MSC. The ANNLIST parameter indicates the
34
announcement to play. The ACCDEN parameter indicates service denial.
35

f. The MSC plays the indicated announcement to the MS. 36


37
g. The Serving MSC releases the MS. 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 4-22 TIA/EIA-41.3-D Modifications


PN-4287

1
2 8.X.10 Three-Way Calling: Calling Party Disconnect
3
4
This scenario describes PPC invocation for a Three-Way call. The calling party
5
disconnects before the last party on the call and no end of call announcement is provided.
6
7
Serving System
8
9
10
IP SCP MSC MS
11
12
digits + SEND
13
a
14
15 BILLID1 ORREQ [MSCID, MSID, MDN, BILLID, DGTSDIAL, TRIGTYPE]
16
b
ORT
17 orreq [DMH_SVCID]
18 c
19 ANLYZD [MSCID, TRANSCAP, WINCAP, MSID, MDN, BILLID,
20 BILLID1 DGTSDIAL, RoutingInfo, TRIGTYPE, TOD, TDO]
d
21
22 SEIZERES [SRFCapability, PLIND]
23 e
24 SZRT ANZT
seizeres [TLDN]
25 f
26
CONNRES [DSTDGTS, CARDGTS, ROUTDGTS]
27 TLDNAT g
28 WINRT
29
call setup
h
30
31 INSTREQ
i
32
IRT
33 SRFDIR [EXESCR]
34
SSFT j
SRFDT
35 announcement
36 k
37
srfdir [SCRRESULT ]
38 l
39
anlyzd [ ]
40 m
41
IRT
42 call release
n
43
44 instreq
o
45
46 call-1 setup
47 p
48
call-1 answer
49 q
50
BILLID1 OANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO]
51 r
52
53
answer
s
54
55 Figure 8.X.10-1 Three-Way Calling: Calling Party Disconnect (1 of 2)
56
57
58 a-s. Same as Section 8.X.3, Steps a -s.
59
60

TIA/EIA-41.3-D Modifications 4-23 Pre-Paid Charging


PN-4287

1
Serving System 2
3
IP SCP MSC MS 4
5
6
7
8
digits + SEND
9
t
10
11
call-1 hold u 12
13
BILLID2 ORREQ [MSCID, MSID, MDN, BILLID, DGTSDIAL, TRIGTYPE, FEATIND]
14
v
15
ORT
orreq [DMH_SVCID] 16
w
17
ANLYZD [MSCID, TRANSCAP, WINCAP, MSID, MDN, BILLID, 18
BILLID2 DGTSDIAL, RoutingInfo, TRIGTYPE, FEATIND, TOD, TDO] 19
x
20
ANZT
21
22
Announcement as described in Steps e-l can optionally be repeated here
23
24
anlyzd [ ] 25
y
26
call-2 setup 27
z
28
call-2 answer 29
aa 30

BILLID2 OANSWER [MSCID, MSID, MDN, BILLID, FEATIND, TRIGTYPE, TOD, TDO] 31
bb 32
33
answer
cc 34
35
SEND
dd 36
37
38
call-1 reconnect ee
39
40
41
call-1 disconnect
ff 42
43
BILLID1 ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]
44
gg
45
ODT
odisconnect [ ] 46
hh
47
END 48
ii 49

BILLID2 ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO] 50
jj 51
ODT 52
odisconnect [ ]
kk 53
54
call release 55
ll
56

Figure 8.X.10-2 Three-Way Calling: Calling Party Disconnect (2 of 2) 57


58
59
60

Pre-Paid Charging 4-24 TIA/EIA-41.3-D Modifications


PN-4287

1
t. During the two-way conversation state, the subscriber enters digits and presses the
2
SEND key.
3
4
u. The original called party is put on hold and the Serving MSC will attempt to
5
establish a connection to the third party specified by the digits received.
6
7 v. The Serving MSC detects the Origination_Attempt_Authorized trigger and sends an
8 ORREQ to the SCP associated with this trigger.
9
10 Parameters Usage Type
11
MSCID Serving MSC MSCID. R
12
13 MSID Served MS MSID. R
14
MDN Mobile directory number. Include if available. O
15
16 BILLID BillingID. Used to relate queries for this call. R
17
DGTSDIAL Digits entered by served MS. R
18
19 TRIGTYPE Indicates the trigger encountered. R
20
FEATIND FeatureIndicator. Indicates the feature invoked R
21
with the call (e.g., Three-Way Calling).
22
23 w. The SCP determines the subscriber has PPC active, another subscriber call is in
24 progress, and the subscriber’s account balance is above the threshold level. The
25 SCP sends an orreq to the Serving MSC to indicate call processing shall continue.
26 The DMH_SVCID parameter is set to indicate the PPC service was invoked.
27
28 x. The Serving MSC analyzes the dialed digits and prepares to route the call to the
29 third party. The MSC detects the Calling_Routing_Address_Available trigger and
30 sends an ANLYZD to the SCP associated with this trigger.
31
Parameters Usage Type
32
33 MSCID Serving MSC MSCID. R
34
35
TRANSCAP Serving MSC’s transaction capability. R
36 WINCAP Serving MSC’s WIN capability. R
37
38 MSID Served MS MSID. R
39
MDN Mobile directory number. Include if available. O
40
41 BILLID BillingID. Used to relate queries for this call. R
42
DGTSDIAL Digits entered by served MS. O
43
44 RoutingInfo: Call routing information:
45
[DSTDGTS] DestinationDigits. The network address of the R
46
destination.
47
48 [CARDGTS] CarrierDigits. Interexchange carrier for call O
49
setup. Include if applicable.
50 [ROUTDGTS] RoutingDigits. Special routing instructions. O
51 Include if applicable.
52
TRIGTYPE Indicates the trigger encountered. R
53
54 FEATIND FeatureIndicator. Indicates the feature invoked R
55 with the call (e.g., Three-Way Calling).
56
TOD TimeOfDay. The current time (UTC). R
57
58
59
60

TIA/EIA-41.3-D Modifications 4-25 Pre-Paid Charging


PN-4287

1
TDO TimeDateOffset. The time offset of local civil R 2
time.
3
4
The SCP can optionally play an announcement to the subscriber to indicate the
5
current account balance.
6
y. The SCP sends an anlyzd to the MSC. 7
8
z. The MSC extends the call to the third party. 9
10
aa. The call is answered by the called party.
11

bb. The Serving MSC detects the O_Answer trigger and sends an OANSWER to the SCP 12

associated with this trigger. 13


14
Parameters Usage Type 15
16
MSCID Serving MSC MSCID. R
17
MSID Served MS MSID. R 18
19
MDN Mobile directory number. Include if available. O
20
BILLID BillingID. Used to relate queries for this call. R 21
22
FEATIND FeatureIndicator. Indicates the feature invoked R
23
with the call (e.g., Three-Way Calling).
24
TOD TimeOfDay. The time of call answer (UTC). R 25
26
TDO TimeDateOffset. The time offset of local civil R
27
time.
28
TRIGTYPE Indicates the trigger encountered. R 29
30
Upon receipt of the OANSWER, the SCP begins decrementing the subscriber’s 31
account balance for the call to the third party. 32
33
cc. The call is cut through and connected.
34

dd. The subscriber presses the SEND key. 35


36

ee. The held party is connected to the call (3-Way State). 37


38
ff. The MSC receives a disconnect indication for the original called party. The MSC 39
releases the call leg toward the original called party. 40
41
gg. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT 42
to the SCP associated with this trigger. 43
44
Parameters Usage Type
45
MSCID Serving MSC MSCID. R 46
47
MSID Served MS MSID. R
48
MDN Mobile directory number. Include if available. O 49
50
BILLID BillingID. Used to relate queries for this call. R
51
TRIGTYPE Indicates the trigger encountered. R 52
53
RELCAUSE Call release cause. R
54

TOD TimeOfDay. The time of call disconnect (UTC). R 55


56
TDO TimeDateOffset. The time offset of local civil R 57
time.
58
59
60

Pre-Paid Charging 4-26 TIA/EIA-41.3-D Modifications


PN-4287

1
Upon receipt of the ODISCONNECT, the SCP stops decrementing the subscriber’s
2
account balance for the call to the original called party.
3
4 hh. The SCP determines that there are still two parties on the call and does not play an
5 end of call announcement. The SCP sends an odisconnect to the Serving
6 MSC.
7
8 ii. The subscriber presses the END key.
9
10 jj. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT
11 to the SCP associated with this trigger.
12
Parameters Usage Type
13
14 MSCID Serving MSC MSCID. R
15
MSID Served MS MSID. R
16
17 MDN Mobile directory number. Include if available. O
18
19
BILLID BillingID. Used to relate queries for this call. R
20 TRIGTYPE Indicates the trigger encountered. R
21
22 RELCAUSE Call release cause. R
23
TOD TimeOfDay. The time of call disconnect (UTC). R
24
25 TDO TimeDateOffset. The time offset of local civil R
26 time.
27
Upon receipt of the ODISCONNECT, the SCP stops decrementing the subscriber’s
28
account balance for the call to the third party.
29
30 kk. The SCP sends an odisconnect to the Serving MSC.
31
32 ll. The Serving MSC releases the call.
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-27 Pre-Paid Charging


PN-4287

8.X.11 Three-Way Calling: Called Party Disconnect 2


3
4
This scenario describes PPC invocation for a Three-Way call. The called parties end the
5
call first. In this scenario, the updated account balance is provided to the subscriber at the
6
end of the call.
7
8
Serving System
9
10
IP SCP MSC MS 11
12
13
14
Same as MS Call Origination with 3-Way Call Invocation, Section 8.X.10, Steps a-hh
15
16
call-2 disconnect
ii 17
18
ODISCONNECT [MSCID, TRANSCAP, WINCAP, MSID, MDN,
19
BILLID2 BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]
jj 20
21
SEIZERES [SRFCapability, PLIND]
kk 22

SZRT ODT 23
seizeres [TLDN] 24
ll
25
CONNRES [DSTDGTS, CARDGTS, ROUTDGTS] 26
TLDNAT mm
27
WINRT
call setup 28
nn 29

INSTREQ 30
oo 31
IRT SSFT 32
SRFDIR [EXESCR]
pp 33

SRFDT 34
announcement
qq 35
36
srfdir [SCRRESULT ] 37
rr
38
odisconnect [ ] 39
ss
40
IRT
call release 41
tt 42
43
instreq
uu 44
45
release
vv 46
47
Figure 8.X.11 Three-Way Calling: Called Party Disconnect 48
49
50
a-hh. Same as Section 8.X.10, Steps a-hh. 51
52
ii. The MSC receives a disconnect indication for the second called party. The MSC 53
releases the call leg toward the second called party. 54
55
56
57
58
59
60

Pre-Paid Charging 4-28 TIA/EIA-41.3-D Modifications


PN-4287

1
jj. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT
2
to the SCP associated with this trigger.
3
4 Parameters Usage Type
5
MSCID Serving MSC MSCID. R
6
7 TRANSCAP Serving MSC’s transaction capability. R
8
9
WINCAP Serving MSC’s WIN capability. R
10 MSID Served MS MSID. R
11
12 MDN Mobile directory number. Include if available. O
13
BILLID BillingID. Used to relate queries for this call. R
14
15 TRIGTYPE Indicates the trigger encountered. R
16
RELCAUSE Call release cause. R
17
18 TOD TimeOfDay. The time of call disconnect (UTC). R
19
TDO TimeDateOffset. The time offset of local civil R
20
time.
21
22 Upon receipt of the ODISCONNECT, the SCP stops decrementing the subscriber’s
23 account balance.
24
25 kk. The SCP determines that an IP is required to play an announcement to the MS with
26 the subscriber’s new account balance. The SCP sends a SEIZERES to an IP
27 requesting routing instructions.
28
29
ll. When the IP receives the SEIZERES, it allocates a TLDN to the appropriate
30
resource. The TLDN is returned to the SCP in the seizeres.
31
mm. The SCP sends a CONNRES to the Serving MSC with instructions to set up a call
32
leg to the IP.
33
34 Parameters Usage Type
35
DSTDGTS DestinationDigits. The network address of the R
36
destination.
37
38 CARDGTS CarrierDigits. Interexchange carrier for call O
39 setup. Include if applicable.
40
ROUTDGTS RoutingDigits. Special routing instructions. O
41
Include if applicable.
42
43 nn. The Serving MSC sets up the call leg to the IP.
44
45 oo. When the call is detected at the IP, the IP sends an INSTREQ to the SCP requesting
46 instructions.
47
pp. The SCP sends an SRFDIR to the IP with the EXESCR parameter indicating the
48
announcement to play.
49
50 Note: The SCP may include the ANNLIST parameter instead of the EXESCR
51 parameter to indicate the announcement to play.
52
53 qq. The IP plays the announcement indicated by the EXESCR parameter to the MS.
54 The announcement indicates the updated account balance.
55
56
rr. The IP sends an srfdir to the SCP. The SCRRESULT parameter indicates the
57
announcement was played.
58
ss. The SCP sends an odisconnect to the Serving MSC.
59
60

TIA/EIA-41.3-D Modifications 4-29 Pre-Paid Charging


PN-4287

1
tt. The Serving MSC releases the call leg to the IP.
2

uu. The SCP sends an instreq to the IP to conclude the SCP-IP transaction. 3
4
vv. The Serving MSC releases the MS. 5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
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 4-30 TIA/EIA-41.3-D Modifications


PN-4287

1
2 8.X.12 Three-Way Calling: Loss of Radio Contact
3
4
This scenario describes PPC invocation for a Three-Way call with loss of radio contact
5
after all call legs are active.
6
7
Serving System
8
9
10
IP SCP MSC MS
11
12
13
Same as MS Call Origination with 3-Way Call Invocation, Section 8.X.10, Steps a-ee
14
15
16
17 loss of radio contact
18 ff
19
BILLID1 ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]
20 gg
21 ODT
odisconnect [ ]
22 hh
23
24 call-1 release
ii
25
26 BILLID2 ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]
jj
27
ODT
28 odisconnect [ ]
29 kk
30
call-2 release
31 ll
32
33 Figure 8.X.12 Three-Way Calling: Loss of Radio Contact
34
35
36
a-ee. Same as Section 8.X.10, Steps a-ee.
37
ff. Radio contact with the MS is lost.
38
39 gg. The Serving MSC detects the O_Disconnect trigger for the call to the original called
40 party. The MSC sends an ODISCONNECT to the SCP associated with this trigger.
41
42 Parameters Usage Type
43
MSCID Serving MSC MSCID. R
44
45 MSID Served MS MSID. R
46
MDN Mobile directory number. Include if available. O
47
48 BILLID BillingID. Used to relate queries for this call. R
49
TRIGTYPE Indicates the trigger encountered. R
50
51 RELCAUSE Call release cause. R
52
TOD TimeOfDay. The time of call disconnect (UTC). R
53
54 TDO TimeDateOffset. The time offset of local civil R
55 time.
56
57 Upon receipt of the ODISCONNECT, the SCP stops decrementing the subscriber’s
58 account balance for the call to the original called party.
59
60

TIA/EIA-41.3-D Modifications 4-31 Pre-Paid Charging


PN-4287

1
hh. The SCP sends an odisconnect to the Serving MSC.
2

ii. The Serving MSC releases the call to the original called party. 3
4
jj. The Serving MSC detects the O_Disconnect trigger for the call to the third party. 5
The MSC sends an ODISCONNECT to the SCP associated with this trigger. 6
7
Parameters Usage Type
8
MSCID Serving MSC MSCID. R 9
10
MSID Served MS MSID. R
11

MDN Mobile directory number. Include if available. O 12


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

TRIGTYPE Indicates the trigger encountered. R 15


16
RELCAUSE Call release cause. R 17
18
TOD TimeOfDay. The time of call disconnect (UTC). R
19
TDO TimeDateOffset. The time offset of local civil R 20
time. 21
22
Upon receipt of the ODISCONNECT, the SCP stops decrementing the subscriber’s
23
account balance for the call to the third party.
24

kk. The SCP sends an odisconnect to the Serving MSC. 25


26
ll. The Serving MSC releases the call to the third party. 27
28
29
30
31
32
33
34
35
36
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 4-32 TIA/EIA-41.3-D Modifications


PN-4287

1
2 8.X.13 Three-Way Calling: Insufficient Balance for Third-Party Call
3
4
This scenario describes PPC invocation for a Three-Way call with an insufficient balance
5
for the third-party call.
6
7
Serving System
8
9
10
IP SCP MSC MS
11
12
13
Same as MS Call Origination with 3-Way Call Invocation, Section 8.X.10, Steps a-s
14
15
16
17 digits + SEND
18 t
19
20 call-1 hold u
21
22 BILLID2 ORREQ [MSCID, MSID, MDN, BILLID, DGTSDIAL, TRIGTYPE, FEATIND]
23 v
24 ORT
orreq [DMH_SVCID]
25 w
26 ANLYZD [MSCID, TRANSCAP, MSID, MDN, BILLID, DGTSDIAL,
27 BILLID2 RoutingInfo, TRIGTYPE, FEATIND, TOD, TDO]
28
x
ANZT
29 anlyzd [ANNLIST, ACCDEN]
30 y
31
announcement
32 z
33
34 call-1 reconnect aa
35
36
37 Figure 8.X.13 Three-Way Calling: Insufficient Balance for Third-Party Call
38
39
40 a-s. Same as Section 8.X.10, Steps a-s.
41
42
t. During the two-way conversation state, the subscriber enters digits and presses the
SEND key.
43
44
45
u. The other party is put on hold and the Serving MSC will attempt to establish a
46
connection to the party specified by the digits received.
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-33 Pre-Paid Charging


PN-4287

1
v. The Serving MSC detects the Origination_Attempt_Authorized trigger and sends an
2
ORREQ to the SCP associated with this trigger.
3
Parameters Usage Type 4
5
MSCID Serving MSC MSCID. R
6

MSID Served MS MSID. R 7


8
MDN Mobile directory number. Include if available. O 9

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


11
DGTSDIAL Digits entered by served MS. R 12
13
TRIGTYPE Indicates the trigger encountered. R
14
FEATIND FeatureIndicator. Indicates the feature invoked R 15
with the call (e.g., Three-Way Calling). 16
17
w. The SCP determines the subscriber has PPC active, that another subscriber call is in
18
progress, and the account balance is above the threshold level. The SCP sends an
19
orreq to the Serving MSC. The DMH_SVCID parameter is set to indicate the
20
PPC service was invoked.
21

x. The Serving MSC analyzes the dialed digits and prepares to route the call to the 22

third party. The MSC detects the Calling_Routing_Address_Available trigger and 23

sends an ANLYZD to the SCP associated with this trigger. 24


25
Parameters Usage Type 26
27
MSCID Serving MSC MSCID. R
28
TRANSCAP Serving MSC’s transaction capability. R 29
30
MSID Served MS MSID. R
31
MDN Mobile directory number. Include if available. O 32
33
BILLID BillingID. Used to relate queries for this call. R
34

DGTSDIAL Digits entered by served MS. O 35


36
RoutingInfo: Call routing information: 37

[DSTDGTS] DestinationDigits. The network address of the R 38


destination. 39
40
[CARDGTS] CarrierDigits. Interexchange carrier for call O
41
setup. Include if applicable.
42
[ROUTDGTS] RoutingDigits. Special routing instructions. O 43
Include if applicable. 44
45
TRIGTYPE Indicates the trigger encountered. R
46
FEATIND FeatureIndicator. Indicates the feature invoked R 47
with the call (e.g., Three-Way Calling). 48
49
TOD TimeOfDay. The current time (UTC). R
50
TDO TimeDateOffset. The time offset of local civil R 51
time. 52
53
y. The subscriber account balance is too low for the call origination indicated (Note:
54
another call origination attempt may have been permitted). The SCP sends an
55
anlyzd to the MSC. The ANNLIST parameter specifies the announcement to be
56
played to the MS. The ACCDEN parameter indicates denial of this service request.
57

z. The MSC plays an announcement to the MS indicating the account balance is too 58

low for the call origination attempt. 59


60

Pre-Paid Charging 4-34 TIA/EIA-41.3-D Modifications


PN-4287

1
aa. The MSC reconnects the MS to the original called party.
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-35 Pre-Paid Charging


PN-4287

8.X.14 Three-Way Calling: Mid-Call Low Balance Indication 2


3
4
This scenario describes PPC invocation for a Three-Way call with a mid-call indication
5
of low balance provided to the MS.
6
7
Serving System
8
9
IP SCP MSC MS 10
11
12
13
Same as MS Call Origination with 3-Way Call Invocation, Section 8.X.10, Steps a-ee
14
15
16

BILLID2 CCDIR [MSCID, MSID, MDN, BILLID, ANNLIST] 17


ff 18
19
low balance warning
CCDT gg 20
21
ccdir [ ]
hh 22
23
call-1 disconnect 24
ii
25
BILLID1 ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO] 26
jj
27
ODT
odisconnect [ ] 28
kk 29
END 30
ll 31

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

mm 33

ODT 34
odisconnect [ ] 35
nn
36
call release 37
oo
38
39
Figure 8.X.14 Three-Way Calling: Mid-Call Low Balance Indication
40
41

a-ee. Same as Section 8.X.10, Steps a-ee. 42


43
ff. The subscriber’s account balance reaches a threshold level and the SCP sends a 44
CCDIR to the Serving MSC with the ANNLIST parameter indicating that a low 45
balance warning (i.e., tone or announcement) be played to the MS. 46
47
Parameters Usage Type
48

MSCID SCP MSCID. Include to identity the requesting R 49


network entity. 50
51
MSID Served MS MSID. R
52

MDN Mobile directory number. Include if available. O 53


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

ANNLIST List of tones or announcements to play. R 56


57
Note: the value of the BILLID parameter may be the value for the call to the first 58
called party or the value for the call to the third party. 59
60

Pre-Paid Charging 4-36 TIA/EIA-41.3-D Modifications


PN-4287

1
gg. The Serving MSC applies the low balance warning to the MS. The low balance
2
warning is only applied to the calling MS (i.e., the called parties do not hear the
3
warning).
4
5 hh. The Serving MSC sends a ccdir to the SCP indicating the requested action was
6 completed.
7
8 ii. The MSC receives a disconnect indication for the original called party. The MSC
9 releases the call leg toward the original called party.
10
11
jj. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT
12
to the SCP associated with this trigger.
13 Parameters Usage Type
14
15 MSCID Serving MSC MSCID. R
16
MSID Served MS MSID. R
17
18 MDN Mobile directory number. Include if available. O
19
BILLID BillingID. Used to relate queries for this call. R
20
21 TRIGTYPE Indicates the trigger encountered. R
22
RELCAUSE Call release cause. R
23
24 TOD TimeOfDay. The time of call disconnect (UTC). R
25
TDO TimeDateOffset. The time offset of local civil R
26
time.
27
28 Upon receipt of the ODISCONNECT, the SCP stops decrementing the subscriber’s
29 account balance for the call to the original called party.
30
31 kk. The SCP sends an odisconnect to the Serving MSC.
32
33
ll. The MS ends the call.
34
mm. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT
35
to the SCP associated with this trigger.
36
37 Parameters Usage Type
38
MSCID Serving MSC MSCID. R
39
40 MSID Served MS MSID. R
41
42
MDN Mobile directory number. Include if available. O
43 BILLID BillingID. Used to relate queries for this call. R
44
45 TRIGTYPE Indicates the trigger encountered. R
46
RELCAUSE Call release cause. R
47
48 TOD TimeOfDay. The time of call disconnect (UTC). R
49
TDO TimeDateOffset. The time offset of local civil R
50
time.
51
52 Upon receipt of the ODISCONNECT, the SCP stops decrementing the subscriber’s
53 account balance for the call to the third party.
54
55 nn. The SCP sends an odisconnect to the Serving MSC.
56
oo. The Serving MSC releases the call to the third party.
57
58
59
60

TIA/EIA-41.3-D Modifications 4-37 Pre-Paid Charging


PN-4287

8.X.15 Three-Way Calling: Service Logic Directed Call Release 2


3
4
This scenario describes PPC invocation for a Three-Way call with a service logic directed
5
call release.
6
7
Serving System
8
9
IP SCP MSC MS 10
11
12
13
Same as MS Call Origination with 3-Way Call Invocation, Section 8.X.10, Steps a-ee
14
15
16

BILLID2 CCDIR [MSCID, MSID, MDN, BILLID, ANNLIST] 17


ff 18
19
low balance warning
CCDT gg 20
21
ccdir [ ]
hh 22
23
24
BILLID1 CCDIR [MSCID, MSID, MDN, BILLID, ANNLIST, ACTCODE] 25
ii
26
disconnect warning 27
jj 28
CCDT
call-1 release 29
kk 30
31
ccdir [ ]
ll 32
33
BILLID1 ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]
mm 34
35
ODT
odisconnect [ ] 36
nn
37
call-2 release 38
oo
39

BILLID2 ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO] 40
pp 41
ODT 42
odisconnect [ ]
qq 43
44
call release
rr 45
46
Figure 8.X.15 Three-Way Calling: Service Logic Directed Call Release 47
48
49
a-ee. Same as Section 8.X.10, Steps a-ee. 50
51
ff-hh. Same as Section 8.X.14, Steps ff-hh. 52
53
ii. The SCP determines the three-way call shall be disconnected (e.g., a PPC service
54
logic program instance timer expires). The SCP sends a CCDIR to the Serving
55
MSC. The ANNLIST parameter indicates that the disconnect warning (i.e., tone
56
or announcement) shall be played to the MS. The ACTCODE parameter indicates
57
the MS shall be released.
58
59
60

Pre-Paid Charging 4-38 TIA/EIA-41.3-D Modifications


PN-4287

1
jj. The Serving MSC plays the disconnect warning. The disconnect warning is only
2
applied to the calling MS (i.e., the called parties do not hear the warning).
3
4 kk. The call to the first called party is released.
5
6 ll. The Serving MSC sends a ccdir to the SCP reporting the action was completed.
7
8
mm. The Serving MSC detects the O_Disconnect trigger for the call to the first called
9
party and sends an ODISCONNECT to the SCP associated with this trigger.
10 Parameters Usage Type
11
12 MSCID Serving MSC MSCID. R
13
MSID Served MS MSID. R
14
15 MDN Mobile directory number. Include if available. O
16
BILLID BillingID. Used to relate queries for this call. R
17
18 TRIGTYPE Indicates the trigger encountered. R
19
RELCAUSE Call release cause. R
20
21 TOD TimeOfDay. The time of call disconnect (UTC). R
22
TDO TimeDateOffset. The time offset of local civil R
23
time.
24
25 Upon receipt of the ODISCONNECT, the SCP stops decrementing the subscriber’s
26 account balance for the call to the first called party.
27
28 nn. The SCP sends an empty odisconnect to the Serving MSC.
29
30
oo. The call to the second called party is released.
31
pp. The Serving MSC detects the O_Disconnect trigger for the call to the second called
32
party and sends an ODISCONNECT to the SCP associated with this trigger.
33
34 Parameters Usage Type
35
MSCID Serving MSC MSCID. R
36
37 MSID Served MS MSID. R
38
39
MDN Mobile directory number. Include if available. O
40 BILLID BillingID. Used to relate queries for this call. R
41
42 TRIGTYPE Indicates the trigger encountered. R
43
RELCAUSE Call release cause. R
44
45 TOD TimeOfDay. The time of call disconnect (UTC). R
46
TDO TimeDateOffset. The time offset of local civil R
47
time.
48
49 Upon receipt of the ODISCONNECT, the SCP stops decrementing the subscriber’s
50 account balance for the call to the second called party.
51
52 qq. The SCP sends an empty odisconnect to the Serving MSC.
53
rr. The Serving MSC releases the MS.
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-39 Pre-Paid Charging


PN-4287

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


3
4
This scenario describes PPC invocation for an MS call origination with a WIN-based
5
abbreviated dialing service. The subscriber enters # and the abbreviated dialing number
6
as in:
7
# + digits + SEND . 8
9
10
PPC AD Serving System
11
12
IP SCP-1 SCP-2 MSC 13
14
15
MS origination
16
a
17
ORREQ [MSCID, MSID, MDN, BILLID, DGTSDIAL, TRIGTYPE] 18
b 19
ORT
orreq [DMH_SVCID] 20
c 21

ORREQ [MSCID, TRANSCAP, MSID, MDN, BILLID, DGTSDIAL, TRIGTYPE] 22


d 23
24
SERVREQ [SRVID, DMH_SVCID, MSID, MDN, MSCID, BILLID, TOD, TDO]
e 25
26
SVRT ORT
servreq [ ] 27
f
28
orreq [TERMLIST] 29
g
30
ANLYZD [MSCID, WINCAP, MSID, MDN, BILLID, DGTSDIAL, RoutingInfo, TRIGTYPE, TOD, TDO] 31
h 32
33
SEIZERES [SRFCapability, PLIND]
i 34
SZRT ANZT 35
seizeres [TLDN]
j 36
37
CONNRES [DSTDGTS, CARDGTS, ROUTDGTS] 38
TLDNAT k
39
WINRT
call setup 40
l
41
INSTREQ 42
m 43
IRT
SRFDIR [EXESCR] 44
SSFT n 45
SRFDT 46
announcement
o 47
48
srfdir [SCRRESULT ]
p 49
50
anlyzd [ ] 51
q
52
IRT
call release 53
r
54

instreq 55
s 56
57
Figure 8.X.16-1 Call Origination with WIN-based Abbreviated Dialing (1 of 2) 58
59
60

Pre-Paid Charging 4-40 TIA/EIA-41.3-D Modifications


PN-4287

1
a. An MS call origination with dialed digits is received by the Serving MSC.
2
3 b. The Serving MSC detects the Origination_Attempt_Authorized trigger and sends an
4 ORREQ to SCP-1, the SCP associated with this trigger.
5
6 Parameters Usage Type
7
MSCID Serving MSC MSCID. R
8
9 MSID Served MS MSID. R
10
MDN Mobile directory number. Include if available. O
11
12 BILLID BillingID. Used to relate queries for this call. R
13
DGTSDIAL Digits entered by served MS. R
14
15 TRIGTYPE Indicates the trigger encountered. R
16
17 c. SCP-1 determines the subscriber has PPC active and the subscriber’s account
18 balance is above the threshold level. The SCP sends an orreq to the Serving
19 MSC. The DMH_SVCID parameter is set to indicate the PPC service was invoked.
20
d. The Serving MSC detects the Single_Introducing_Pound trigger and sends an
21
ORREQ to SCP-2, the SCP associated with this trigger.
22
23 Parameters Usage Type
24
25
MSCID Serving MSC MSCID. R
26 TRANSCAP Serving MSC’s transaction capability. R
27
28 MSID Served MS MSID. R
29
MDN Mobile directory number. Include if available. O
30
31 BILLID BillingID. Used to relate queries for this call. R
32
DGTSDIAL Digits entered by served MS. R
33
34 TRIGTYPE Indicates the trigger encountered. R
35
36
e. Based on the SIM (Service Interaction Manager) in SCP-2, SCP-2 may optionally
37
send a SERVREQ to SCP-1 to invoke a PPC service for charging the indicated
38
subscriber for the abbreviated dialing service invocation.
39
Parameters Usage Type
40
41 SRVID ID of the Service Logic Program to execute. R
42 (SRVID = PPC).
43
DMH_SVCID ID of the Service Logic Program invoked on R
44 behalf of the MS (DMH_SVCID=AD).
45
46 MSID Served MS MSID. R
47
MDN Mobile directory number. Include if available. O
48
49 MSCID Requesting MSC MSCID. R
50
BILLID BillingID. Used to relate queries for this call. R
51
52 TOD TimeOfDay. The time of Service Invocation R
53 (UTC).
54
TDO TimeDateOffset. The time offset of local civil R
55
time.
56
57 f. SCP-1 sends a servreq to SCP-2.
58
59
60

TIA/EIA-41.3-D Modifications 4-41 Pre-Paid Charging


PN-4287

1
g. SCP-2 translates the abbreviated dialing string into a network address. SCP-2 sends
2
an orreq to the Serving MSC. The TERMLIST parameter indicates the routing
3
for the call.
4

h. The Serving MSC prepares to route the call. The MSC detects the 5

Calling_Routing_Address_Available trigger and sends an ANLYZD to SCP-1, the 6

SCP associated with this trigger. 7


8
Parameters Usage Type 9
10
MSCID Serving MSC MSCID. R
11
WINCAP Serving MSC’s WIN capability. R 12
13
MSID Served MS MSID. R
14
MDN Mobile directory number. Include if available. O 15
16
BILLID BillingID. Used to relate queries for this call. R
17
DGTSDIAL Digits entered by served MS. O 18
19
RoutingInfo: Call routing information:
20
[DSTDGTS] DestinationDigits. The network address of the R 21
destination. 22
23
[CARDGTS] CarrierDigits. Interexchange carrier for call O
24
setup. Include if applicable.
25
[ROUTDGTS] RoutingDigits. Special routing instructions. O 26
Include if applicable. 27

TRIGTYPE Indicates the trigger encountered. R 28


29
TOD TimeOfDay. The current time (UTC). R 30
31
TDO TimeDateOffset. The time offset of local civil R
time. 32
33
i. SCP-1 determines that an IP is required to play an announcement to the MS with the 34
subscriber’s current account balance. SCP-1 sends a S E I Z E R E S to an IP 35
requesting the resource. 36
37
Parameters Usage Type
38

SRFCapability: Specifies the specialized resource capabilities R 39


requested: 40
41
[SpecializedResource] Indicates the type of standard specialized O
42
resource requested.
43
[PrivateSpecializedResource] Indicates the type of private specialized O 44
resource requested. 45
46
PLIND PreferredLanguageIndicator. Indicates the O
preferred language. 47
48
j. When the IP receives the SEIZERES, it allocates a TLDN to the appropriate 49
resource. The TLDN is returned to SCP-1 in the seizeres. 50
51
52
53
54
55
56
57
58
59
60

Pre-Paid Charging 4-42 TIA/EIA-41.3-D Modifications


PN-4287

1
k. SCP-1 sends a CONNRES to the Serving MSC with instructions to set up a call leg
2
to the IP.
3
4 Parameters Usage Type
5
DSTDGTS DestinationDigits. The network address of the R
6
destination.
7
8 CARDGTS CarrierDigits. Interexchange carrier for call O
9 setup. Include if applicable.
10
ROUTDGTS RoutingDigits. Special routing instructions. O
11
Include if applicable.
12
13 l. The MSC sets up the call leg to the IP.
14
15 m. When the call is detected at the IP, the IP sends an INSTREQ to SCP-1 requesting
16 call processing instructions.
17
18
n. SCP-1 sends an SRFDIR to the IP with the EXESCR parameter indicating the
19
announcement to play.
20
Note: SCP-1 may include the ANNLIST parameter instead of the EXESCR
21
parameter to indicate the announcement to play.
22
23 o. The IP plays the announcement indicated by the EXESCR parameter.
24
25 p. The IP sends an srfdir to SCP-1. The SCRRESULT parameter indicates the
26 announcement was played.
27
q. SCP-1 sends an anlyzd to the MSC.
28
29 r. The Serving MSC releases the call leg to the IP.
30
31 s. SCP-1 sends an instreq to the IP to conclude the SCP-IP conversation.
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-43 Pre-Paid Charging


PN-4287

1
PPC AD Serving System 2
3
IP SCP-1 SCP-2 MSC 4
5
6

call setup 7
t 8
9
answer
u 10
11
OANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO]
v 12
13
answer 14
w
15
16
disconnect 17
x 18
ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO] 19
y 20
ODT 21
odisconnect [ ]
z 22
23
call release
aa 24
25

Figure 8.X.16-2 Call Origination with WIN-based Abbreviated Dialing (2 of 2) 26


27
28
t. The MSC extends the MS originated call. 29
30
u. The call is answered by the called party. 31
32
v. The Serving MSC detects the O_Answer trigger and sends an OANSWER to SCP-1,
33
the SCP associated with this trigger.
34
Parameters Usage Type 35
36
MSCID Serving MSC MSCID. R
37

MSID Served MS MSID. R 38


39
MDN Mobile directory number. Include if available. O 40

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


42
TRIGTYPE Indicates the trigger encountered. R 43
44
TOD TimeOfDay. The time of call answer (UTC). R
45
TDO TimeDateOffset. The time offset of local civil R 46
time. 47
48
Upon receipt of the OANSWER, SCP-1 begins decrementing the subscriber’s account
49
balance.
50

w. The call is cut through and connected. 51


52
x. The MS ends the call. 53
54
55
56
57
58
59
60

Pre-Paid Charging 4-44 TIA/EIA-41.3-D Modifications


PN-4287

1
y. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT
2
to the SCP associated with this trigger.
3
4 Parameters Usage Type
5
MSCID Serving MSC MSCID. R
6
7 MSID Served MS MSID. R
8
9
MDN Mobile directory number. Include if available. O
10 BILLID BillingID. Used to relate queries for this call. R
11
12 TRIGTYPE Indicates the trigger encountered. R
13
RELCAUSE Call release cause. R
14
15 TOD TimeOfDay. The time of call Disconnection R
16 (UTC).
17
TDO TimeDateOffset. The time offset of local civil R
18 time.
19
20 Upon receipt of the ODISCONNECT, SCP-1 stops decrementing the subscriber’s
21 account balance.
22
23
z. SCP-1 sends an odisconnect to the Serving MSC.
24
aa. The Serving MSC releases the call.
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-45 Pre-Paid Charging


PN-4287

8.X.17 Abbreviated Dialing: Insufficient Balance for Service Invocation 2


3
4
This scenario describes PPC invocation upon MS call origination with a WIN-based
5
abbreviated dialing service. Due to an insufficient balance for the invoked service, the
6
call is disconnected.
7
8
PPC AD Serving System
9
10
SCP-1 SCP-2 MSC 11
12
13
MS origination
14
a
15
ORREQ [MSCID, MSID, MDN, BILLID, DGTSDIAL, TRIGTYPE] 16
b 17
ORT
orreq [DMH_SVCID] 18
c 19

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


d 21
22
SERVREQ [SRVID, DMH_SVCID, MSID, MDN, MSCID, BILLID, TOD, TDO]
e 23
24
SVRT ORT
servreq [ACCDEN] 25
f
26
orreq [ACCDEN] 27
g
28
29
Figure 8.X.17 Abbreviated Dialing: Insufficient Balance for Service Invocation
30
31
32
a. An MS call origination with dialed digits is received by the Serving MSC.
33
b. The Serving MSC detects the Origination_Attempt_Authorized trigger and sends an 34
ORREQ to SCP-1, the SCP associated with this trigger. 35
36
Parameters Usage Type 37

MSCID Serving MSC MSCID. R 38


39
MSID Served MS MSID. R 40
41
MDN Mobile directory number. Include if available. O
42
BILLID BillingID. Used to relate queries for this call. R 43
44
DGTSDIAL Digits entered by served MS. R
45
TRIGTYPE Indicates the trigger encountered. R 46
47
c. SCP-1 determines the subscriber has PPC active and the subscriber’s account 48
balance is above the threshold level. The SCP sends an orreq to the Serving 49
MSC. The DMH_SVCID parameter is set to indicate the PPC service was invoked. 50
51
52
53
54
55
56
57
58
59
60

Pre-Paid Charging 4-46 TIA/EIA-41.3-D Modifications


PN-4287

1
d. The Serving MSC detects the Single_Introducing_Pound trigger and sends an
2
ORREQ to SCP-2, the SCP associated with this trigger.
3
4 Parameters Usage Type
5
MSCID Serving MSC MSCID. R
6
7 MSID Served MS MSID. R
8
9
MDN Mobile directory number. Include if available. O
10 BILLID BillingID. Used to relate queries for this call. R
11
12 DGTSDIAL Digits entered by served MS. R
13
TRIGTYPE Indicates the trigger encountered. R
14
15 e. Based on the SIM (Service Interaction Manager) in SCP-2, SCP-2 sends a
16 SERVREQ to SCP-1 to invoke a PPC service for charging the indicated subscriber
17 for the abbreviated dialing service invocation.
18
19
Parameters Usage Type
20 SRVID ID of the Service Logic Program to execute. R
21 (SRVID = PPC).
22
23
DMH_SVCID ID of the Service Logic Program invoked on R
behalf of the MS.
24
25 MSID Served MS MSID. R
26
27
MDN Mobile directory number. Include if available. O
28 MSCID Requesting MSC MSCID. R
29
30 BILLID BillingID. Used to relate queries for this call. R
31
TOD TimeOfDay. The time of Service Invocation R
32 (UTC).
33
34 TDO TimeDateOffset. The time offset of local civil R
35
time.
36
f. SCP-1 determines that the subscriber does not have sufficient balance for the call
37
and sends a servreq that includes the ACCDEN parameter to SCP-2.
38
39 g. SCP-2 sends an orreq that includes the ACCDEN parameter to the Serving MSC.
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-47 Pre-Paid Charging


PN-4287

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


3
4
This scenario describes PPC invocation for an MS call origination with a WIN-based
5
abbreviated dialing service. Due to an insufficient balance, the call is disconnected.
6
7
PPC AD Serving System
8
9
SCP-1 SCP-2 MSC 10
11
12
MS origination
13
a
14
ORREQ [MSCID, MSID, MDN, BILLID, DGTSDIAL, TRIGTYPE] 15
b 16
ORT
orreq [DMH_SVCID] 17
c 18

ORREQ [MSCID, TRANSCAP, MSID, MDN, BILLID, DGTSDIAL, TRIGTYPE] 19


d 20
21
SERVREQ [SRVID, DMH_SVCID, MSID, MDN, MSCID, BILLID, TOD, TDO]
e 22
23
SVRT ORT
servreq [ ] 24
f
25
orreq [TERMLIST] 26
g
27
ANLYZD [MSCID, TRANSCAP, MSID, MDN, BILLID, DGTSDIAL, RoutingInfo, TRIGTYPE, TOD, TDO] 28
h 29
ANZT 30
anlyzd [ANNLIST, ACCDEN]
i 31
32
announcement
j 33
34
release 35
k
36

Figure 8.X.18 Abbreviated Dialing: Insufficient Balance for Call 37


38
39
a-g. Same as Section 8.X.16, Steps a-g. 40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Pre-Paid Charging 4-48 TIA/EIA-41.3-D Modifications


PN-4287

1
h. The Serving MSC prepares to route the call. The MSC detects the
2
Calling_Routing_Address_Available trigger and sends an ANLYZD to SCP-1, the
3
SCP associated with this trigger.
4
5 Parameters Usage Type
6
MSCID Serving MSC MSCID. R
7
8 TRANSCAP Serving MSC’s transaction capability. R
9
10
MSID Served MS MSID. R
11 MDN Mobile directory number. Include if available. O
12
13 BILLID BillingID. Used to relate queries for this call. R
14
DGTSDIAL Digits entered by served MS. O
15
16 RoutingInfo: Call routing information:
17
[DSTDGTS] DestinationDigits. The network address of the R
18 destination.
19
20
[CARDGTS] CarrierDigits. Interexchange carrier for call O
setup. Include if applicable.
21
22 [ROUTDGTS] RoutingDigits. Special routing instructions. O
23 Include if applicable.
24
TRIGTYPE Indicates the trigger encountered. R
25
26 TOD TimeOfDay. The current time (UTC). R
27
TDO TimeDateOffset. The time offset of local civil R
28
time.
29
30 i. The subscriber account balance is too low for the call origination indicated. (Note:
31 another call origination attempt may have been permitted). SCP-1 sends an
32 anlyzd to the requesting MSC. The ANNLIST parameter specifies the
33 announcement to be played to the MS. The ACCDEN parameter indicates denial of
34 this service request.
35
36 j. The Serving MSC plays an announcement to the MS indicating the account balance
37 is too low for the call origination attempt.
38
39
k. The Serving MSC releases the MS.
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-49 Pre-Paid Charging


PN-4287

8.X.19 Call Origination with Call Abandon 2


3
4
This scenario describes PPC invocation upon call origination. The MS abandons the call
5
before the call is answered.
6
7
Serving System
8
9
IP SCP MSC 10
11
12
13
MS Call Origination: Same as Section 8.X.3, Steps a-p
14
15
call abandon
q 16
17
call release 18
r
19
20
CCDIR [MSCID, MSID, MDN, BILLID, ANNLIST] 21
s 22
CCDT
RETURN ERROR 23
t 24
25
Figure 8.X.19 Call Origination with Call Abandon 26
27
28
a-p. Same as Section 8.X.3, Steps a-p. 29
30
q. The MS abandons the call.
31
r. The Serving MSC releases the call. 32
33
s. The SCP determines the status of the call shall be checked (e.g., a PPC SLPI timer 34
expires). The SCP sends a CCDIR to the MSC. The BILLID parameter identifies 35
the call. 36
37
t. The Serving MSC does not have a call that is associated with the received BILLID.
38
The Serving MSC sends a RETURN ERROR to the SCP.
39

The SCP releases all resources associated with the call, and may adjust the 40

subscriber's account balance. 41


42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Pre-Paid Charging 4-50 TIA/EIA-41.3-D Modifications


PN-4287

1
2 8.X.20 Call Origination: Charge Rate Dependent on MS Location
3
4
This scenario describes PPC invocation upon call origination by a PPC subscriber with
5
PPC active and an account balance above threshold. The rate of charging for the call is
6
dependent on the location of the MS.
7
8
Serving System
9
10
11
SN MSC
12
13
MS origination
14
a
15
16 ORREQ [MSCID, MSID, MDN, BILLID, DGTSDIAL, TRIGTYPE]
17
b
ORT
18 orreq [DMH_SCVID]
19 c
20 ANLYZD [MSCID, WINCAP, MSID, MDN, BILLID, DGTSDIAL,
21 RoutingInfo, TRIGTYPE, TOD, TDO, SCELLID, LOCID]
d
22
ANZT
23 CONNRES [DSTDGTS, CARDGTS, ROUTDGTS]
24 e
25 TLDNAT
call setup
26 f
27 SSFT
announcement
28 g
29
30
anlyzd [ ]
h
31
32 call release
i
33
34 call setup
35
j
36 answer
37 k
38 OANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO, SCELLID, LOCID]
39 l
40
answer
41 m
42
43
44 disconnect
n
45
46 ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]
47
o
ODT
48 odisconnect [ ]
49 p
50
call release
51 q
52
53 Figure 8.X.20 MS Call Origination: Charge Rate Dependent on MS Location
54
55
56 a-c. Same as Section 8.X.2, Steps a-c.
57
58
59
60

TIA/EIA-41.3-D Modifications 4-51 Pre-Paid Charging


PN-4287

1
d. The Serving MSC analyzes the dialed digits and prepares to route the call. The
2
MSC detects the Calling_Routing_Address_Available trigger and sends an ANLYZD
3
to the SN associated with this trigger.
4
Parameters Usage Type 5
6
MSCID Serving MSC MSCID. R
7

WINCAP Serving MSC’s WIN capability. R 8


9
MSID Served MS MSID. R 10

MDN Mobile directory number. Include if available. O 11


12
BILLID BillingID. Used to relate queries for this call. R 13
14
DGTSDIAL Digits entered by served MS. O
15
RoutingInfo: Call routing information: 16
17
[DSTDGTS] DestinationDigits. The network address of the R
destination. 18
19
[CARDGTS] CarrierDigits. Interexchange carrier for call O 20
setup. Include if applicable.
21
[ROUTDGTS] RoutingDigits. Special routing instructions. O 22
Include if applicable. 23
24
TRIGTYPE Indicates the trigger encountered. R
25
TOD TimeOfDay. The current time (UTC). R 26
27
TDO TimeDateOffset. The time offset of local civil R
28
time.
29
SCELLID ID of the cell serving the MS. R 30
31
LOCID Location Area ID. Include if available. O
32
33
e. The SN sends a CONNRES to the Serving MSC with instructions to set up a call leg
34
to the SN.
35
Parameters Usage Type 36
37
DSTDGTS DestinationDigits. The network address of the R
38
destination.
39
CARDGTS CarrierDigits. Interexchange carrier for call O 40
setup. Include if applicable. 41
42
ROUTDGTS RoutingDigits. Special routing instructions. O
43
Include if applicable.
44
f. The MSC sets up the call leg to the SN. 45
46
g. The SN plays an announcement to the MS indicating the current account balance. 47
The amount of time available for the call is dependent upon the MS location. 48
49
h. The SN sends an anlyzd to the MSC.
50

i. The Serving MSC releases the call leg to the SN. 51


52
j. The MSC extends the MS originated call. 53
54
k. The call is answered by the called party. 55
56
57
58
59
60

Pre-Paid Charging 4-52 TIA/EIA-41.3-D Modifications


PN-4287

1
l. The Serving MSC detects the O_Answer trigger and sends an OANSWER to the SN
2
associated with this trigger.
3
4 Parameters Usage Type
5
MSCID Serving MSC MSCID. R
6
7 MSID Served MS MSID. R
8
9
MDN Mobile directory number. Include if available. O
10 BILLID BillingID. Used to relate queries for this call. R
11
12 TRIGTYPE Indicates the trigger encountered. R
13
TOD TimeOfDay. The time of call answer (UTC). R
14
15 TDO TimeDateOffset. The time offset of local civil R
16 time.
17
SCELLID ID of the cell serving the MS. R
18
19 LOCID Location Area ID. Include if available. O
20
21
Upon receipt of the OANSWER, the SN begins decrementing the subscriber’s
22
account balance. The rate of charging for the call is dependent upon the MS
23
location.
24
m. The call is cut through and connected.
25
26 n. The MS ends the call.
27
28 o. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT
29 to the SN associated with this trigger.
30
Parameters Usage Type
31
32 MSCID Serving MSC MSCID. R
33
MSID Served MS MSID. R
34
35 MDN Mobile directory number. Include if available. O
36
BILLID BillingID. Used to relate queries for this call. R
37
38 TRIGTYPE Indicates the trigger encountered. R
39
40
RELCAUSE Call release cause. R
41 TOD TimeOfDay. The time of call disconnect (UTC). R
42
43 TDO TimeDateOffset. The time offset of local civil R
44
time.
45
Upon receipt of the ODISCONNECT, the SN stops decrementing the subscriber’s
46
account balance.
47
48 p. The SN sends an empty odisconnect to the Serving MSC.
49
50 q. The Serving MSC releases the call.
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-53 Pre-Paid Charging


PN-4287

8.X.21 Call Delivery: Local Termination at Originating MSC 2


3
4
This scenario describes PPC invocation upon Call Delivery. The call is terminated at the
5
Originating MSC.
6
7
Originating System
8
9
MSC HLR SCP 10
11
12
call origination
a 13

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

b 15

LRT 16
locreq [MSCID, MIN, IMSI, TRIGADDRLIST] 17
c
18
ANLYZD [MSCID, BILLID, DGTSDIAL, MSID, TRIGTYPE] 19
d
20
ANZT
anlyzd [DMH_SVCID] 21
e 22
LOCREQ [MSCID, BILLID, DGTSDIAL, TRIGTYPE, TRANSCAP, WINCAP] 23
f 24
LRT 25
locreq [MSCID, MIN, IMSI, TERMLIST, REDIND]
g 26
27
ANLYZD [MSCID, BILLID, MSID, MDN, RoutingInfo, REDIND, TRIGTYPE, TOD, TDO]
h 28
29
ANZT
anlyzd [ ] 30
i
31
32
MS answer j
33

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


k 35
36
cut through
l 37
38
39
MS disconnect m 40
41
TDISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]
42
n
43
TDT
tdisconnect [ ] 44
o
45

call release 46
p 47
48
Figure 8.X.21 Call Delivery: Local Termination at Originating MSC 49
50
51
a. A call origination and the dialed MS address digits (i.e., directory number) are
52
received by the Originating MSC.
53

b. The Originating MSC detects the Mobile_Termination trigger and sends a LOCREQ 54

to the HLR associated with the MS; this association is made through the dialed MS 55

address digits (which may not be the MSID). The TRANSCAP parameter is set to 56

indicate the MSC can process the TRIGADDRLIST parameter. The WINCAP 57

parameter indicates the triggers supported by the MSC. The TRIGTYPE parameter 58

is set to indicate the Mobile_Termination trigger was encountered. 59


60

Pre-Paid Charging 4-54 TIA/EIA-41.3-D Modifications


PN-4287

1
c. The HLR sends the locreq to the Originating MSC with the TRIGADDRLIST
2
parameter set to indicate t h e Initial_Termination, Location,
3
Called_Routing_Address_Available, T_Answer and T_Disconnect triggers shall be
4
armed.
5
6 Parameters Usage Type
7
MSCID Serving MSC MSCID. R
8
9 MIN Called MS MIN. R
10
11
IMSI Called MS IMSI. Include if available. O
12 TRIGADDRLIST WIN Triggers to arm for this call leg. R
13
14 d. The Originating MSC detects the Initial_Termination trigger and sends an ANLYZD
15 to the SCP indicated in the TRIGADDRLIST parameter. The TRIGTYPE
16 parameter is set to indicate the Initial_Termination trigger was detected.
17
Parameters Usage Type
18
19 MSCID Originating MSC MSCID. R
20
21
BILLID BillingID. Used to relate queries for this call. R
22 DGTSDIAL The called directory number. R
23
24 MSID Called MS MSID. R
25
TRIGTYPE Indicates the trigger encountered. R
26
27 e. The SCP determines the called subscriber has PPC active and that the account
28 balance is above the threshold level. The SCP sends an anlyzd to the Originating
29 MSC. The DMH_SVCID parameter is set to indicate that PPC was invoked.
30
31 f. The Originating MSC detects the Location trigger and sends a LOCREQ to the HLR.
32 The TRIGTYPE parameter is set to indicate the Location trigger was encountered.
33
g. The HLR determines the MS is served by the Originating MSC and returns a
34
locreq indicating a local termination.
35
36 Parameters Usage Type
37
38
MSCID Serving MSC MSCID. R
39 MIN Called MS MIN. R
40
41 IMSI Called MS IMSI. Include if available. O
42
TERMLIST Call termination information. R
43
44 REDIND DMH_RedirectionIndicator. Reason for R
45 extending the incoming call.
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-55 Pre-Paid Charging


PN-4287

1
h. The Originating MSC prepares to terminate the call. The MSC detects the
2
Called_Routing_Address_Available trigger and sends an ANLYZD to the SCP
3
associated with this trigger. The REDIND parameter is set to indicate CD Local.
4
Parameters Usage Type 5
6
MSCID Originating MSC MSCID. R
7

MSID Served MS MSID. R 8


9
MDN Mobile directory number. Include if available. O 10

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


12
RoutingInfo: Call routing information: 13

[DSTDGTS] DestinationDigits. The network address of the O 14

destination. 15
16
[CARDGTS] CarrierDigits. Interexchange carrier for call O
17
setup. Include if applicable.
18
[ROUTDGTS] RoutingDigits. Special routing instructions. O 19
Include if applicable. 20
21
REDIND DMH_RedirectionIndicator. Reason for R
22
extending the incoming call.
23
TRIGTYPE Indicates the trigger encountered. R 24
25
TOD TimeOfDay. The current time (UTC). R
26
TDO TimeDateOffset. The time offset of local civil R 27
time. 28
29
i. The SCP sends an anlyzd to the Originating MSC. 30
31
j. The Originating MSC pages and alerts the MS. The MS answers.
32
k. The MSC detects the T_Answer trigger. The MSC sends a TANSWER to the SCP 33
associated with this trigger. 34
35
Parameters Usage Type 36

MSCID Serving MSC MSCID. R 37


38
MSID Served MS MSID. R 39
40
MDN Mobile directory number. Include if available. O
41
BILLID BillingID. Used to relate queries for this call. R 42
43
TRIGTYPE Indicates the trigger encountered. R
44
TOD TimeOfDay. The time of call answer (UTC). R 45
46
TDO TimeDateOffset. The time offset of local civil R
47
time.
48

l. The calling party is connected to the MS. 49


50
m. The MS ends the call. 51
52
53
54
55
56
57
58
59
60

Pre-Paid Charging 4-56 TIA/EIA-41.3-D Modifications


PN-4287

1
n. The Originating MSC detects the T_Disconnect trigger and sends a TDISCONNECT
2
to the SCP associated with this trigger.
3
4 Parameters Usage Type
5
MSCID Serving MSC MSCID. R
6
7 MSID Served MS MSID. R
8
9
MDN Mobile directory number. Include if available. O
10 BILLID BillingID. Used to relate queries for this call. R
11
12 TRIGTYPE Indicates the trigger encountered. R
13
RELCAUSE Call release cause. R
14
15 TOD TimeOfDay. The time of call disconnect (UTC). R
16
TDO TimeDateOffset. The time offset of local civil R
17
time.
18
19 Upon receipt of the TDISCONNECT, the SCP stops decrementing the subscriber’s
20 account balance.
21
22 o. The SCP sends a tdisconnect to the Originating MSC.
23
p. The MSC releases the call.
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-57 Pre-Paid Charging


PN-4287

8.X.22 Call Delivery: Intersystem Termination 2


3
4
This scenario describes PPC invocation upon Call Delivery with intersystem termination.
5
6
Originating System Serving System
7
8
MSC HLR SCP VLR MSC 9
10

call origination 11
a 12

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

b 14

LRT 15
locreq [MSCID, MIN, IMSI, TRIGADDRLIST] 16
c
17
ANLYZD [MSCID, BILLID, DGTSDIAL, MSID, TRIGTYPE]
18
d
19
ANZT
anlyzd [DMH_SVCID] 20
e 21
LOCREQ [MSCID, BILLID, DGTSDIAL, TRIGTYPE, TRANSCAP, WINCAP] 22
f 23
24
ROUTREQ [MSCID, BILLID, MSID]
g 25
26
ROUTREQ [MSCID, BILLID, MSID]
h 27
28
LRT RRT RRT
routreq [TLDN] 29
i
30
routreq [TLDN] 31
j
32
TLDNAT
locreq [MSCID, MIN, IMSI, TERMLIST, REDIND] 33
k 34
ANLYZD [MSCID, MSID, MDN, BILLID, RoutingInfo, REDIND, TRIGTYPE, TOD, TDO] 35
l 36
ANZT 37
anlyzd [ ]
m 38
39
call setup 40
n
41
42
MS answer o
43
44
TANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO]
p 45
46
cut through
47
q
48
49

MS disconnect r 50
51
TDISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO] 52
s 53
TDT 54
tdisconnect [DMH_SVCID]
t 55
56
call release
u 57
58

Figure 8.X.22 Call Delivery: Intersystem Termination 59


60

Pre-Paid Charging 4-58 TIA/EIA-41.3-D Modifications


PN-4287

1
a. A call origination and the dialed MS address digits (i.e., directory number) are
2
received by the Originating MSC.
3
4 b. The Originating MSC detects the Mobile_Termination trigger and sends a LOCREQ
5 to the HLR associated with the MS; this association is made through the dialed MS
6 address digits (which may not be the MSID). The TRANSCAP parameter is set to
7 indicate the MSC can process the TRIGADDRLIST parameter. The WINCAP
8 parameter indicates the triggers supported by the MSC. The TRIGTYPE parameter
9 is set to indicate the Mobile_Termination trigger was encountered.
10
11 c. The HLR sends the locreq to the Originating MSC with the TRIGADDRLIST
12 parameter set to indicate the Initial_Termination, Location and
13 Called_Routing_Address_Available triggers shall be armed.
14
Parameters Usage Type
15
16 MSCID Serving MSC MSCID. R
17
MIN Called MS MIN. R
18
19 IMSI Called MS IMSI. Include if available. O
20
21
TRIGADDRLIST WIN Triggers to arm for this call leg. R
22
d. The Originating MSC detects the Initial_Termination trigger and sends an ANLYZD
23
to the SCP indicated in the TRIGADDRLIST parameter. The TRIGTYPE
24
parameter is set to indicate the Initial_Termination trigger was detected.
25
26 Parameters Usage Type
27
MSCID Originating MSC MSCID. R
28
29 BILLID BillingID. Used to relate queries for this call. R
30
31
DGTSDIAL The called directory number. R
32 MSID Called MS MSID. R
33
34 TRIGTYPE Indicates the trigger encountered. R
35
e. The SCP determines the called subscriber has PPC active and that the account
36
balance is above the threshold level. The SCP sends an anlyzd to the Originating
37
MSC. The DMH_SVCID parameter is set to indicate that PPC was invoked.
38
39 f. The Originating MSC detects the Location trigger and sends a LOCREQ to the HLR.
40 The TRIGTYPE parameter is set to indicate the Location trigger was encountered.
41
42 g. The HLR determines call processing shall continue and sends a ROUTREQ to the
43 VLR.
44
45
h. The VLR forwards the ROUTREQ to the Serving MSC.
46
i. The Serving MSC allocates a TLDN and returns it to the VLR in the routreq.
47
48 j. The VLR forwards the routreq to the HLR.
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-59 Pre-Paid Charging


PN-4287

1
k. The HLR sends the locreq to the Originating MSC with instructions to set up the
2
call to the subscriber.
3
Parameters Usage Type 4
5
MSCID Serving MSC MSCID. R
6

MIN Called MS MIN. R 7


8
IMSI Called MS IMSI. Include if available. O 9

REDIND DMH_RedirectionIndicator. Reason for R 10

extending the incoming call. 11


12
TERMLIST Call termination information. R 13
14
l. The Originating MSC prepares to setup the call to the Serving MSC and detects the
15
Called_Routing_Address_Available trigger. The Originating MSC sends an
16
ANLYZD to the SCP associated with this trigger.
17
Parameters Usage Type 18
19
MSCID Originating MSC MSCID. R
20

MSID Served MS MSID. R 21


22
MDN Mobile directory number. Include if available. O 23

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


25
RoutingInfo: Call routing information: 26

[DSTDGTS] DestinationDigits. The network address of the R 27

destination. 28
29
[CARDGTS] CarrierDigits. Interexchange carrier for call O
30
setup. Include if applicable.
31
[ROUTDGTS] RoutingDigits. Special routing instructions. O 32
Include if applicable. 33
34
REDIND DMH_RedirectionIndicator. Reason for R
35
extending the incoming call.
36
TRIGTYPE Indicates the trigger encountered. R 37
38
TOD TimeOfDay. The current time (UTC). R
39
TDO TimeDateOffset. The time offset of local civil R 40
time. 41
42
m. The SCP sends an anlyzd to the MSC. 43
44
n. The Originating MSC sets up the call to the subscriber.
45
o. The MS answers the call. 46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Pre-Paid Charging 4-60 TIA/EIA-41.3-D Modifications


PN-4287

1
p. The Serving MSC detects the T_Answer trigger and sends a TANSWER to the SCP
2
associated with this trigger.
3
4 Parameters Usage Type
5
MSCID Serving MSC MSCID. R
6
7 MSID Served MS MSID. R
8
9
MDN Mobile directory number. Include if available. O
10 BILLID BillingID. Used to relate queries for this call. R
11
12 TRIGTYPE Indicates the trigger encountered. R
13
TOD TimeOfDay. The time of call answer (UTC). R
14
15 TDO TimeDateOffset. The time offset of local civil R
16 time.
17
q. The calling party is connected to the MS.
18
19 r. The MS ends the call.
20
21 s. The Serving MSC detects the T_Disconnect trigger and sends a TDISCONNECT to
22 the SCP associated with this trigger.
23
Parameters Usage Type
24
25 MSCID Serving MSC MSCID. R
26
27
MSID Served MS MSID. R
28 MDN Mobile directory number. Include if available. O
29
30 BILLID BillingID. Used to relate queries for this call. R
31
TRIGTYPE Indicates the trigger encountered. R
32
33 RELCAUSE Call release cause. R
34
TOD TimeOfDay. The time of call disconnect (UTC). R
35
36 TDO TimeDateOffset. The time offset of local civil R
37 time.
38
39
Upon receipt of the TDISCONNECT, the SCP stops decrementing the subscriber’s
40
account balance.
41
t. The SCP sends a tdisconnect to the Serving MSC. The DMH_SVCID
42
parameter is set to indicate PPC was invoked.
43
44 u. The Serving MSC releases the call.
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-61 Pre-Paid Charging


PN-4287

8.X.23 Call Delivery: Insufficient Account Balance 2


3
4
This scenario describes PPC invocation upon Call Delivery when the subscriber’s
5
account balance is below threshold.
6
7
Originating System
8
9
MSC HLR SCP 10
11
12
call origination
a 13

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

b 15

LRT 16
locreq [MSCID, MIN, IMSI, TRIGADDRLIST] 17
c
18
ANLYZD [MSCID, BILLID, DGTSDIAL, MSID, TRIGTYPE] 19
d
20
ANZT
anlyzd [ACCDEN, ANNLIST] 21
e 22

denial treatment 23
f 24
25
Figure 8.X.23 Call Delivery: Insufficient Account Balance 26
27
28
a-d. Same as Section 8.X.22, Steps a-d. 29
30
e. The subscriber’s account balance is at or below threshold. The SCP sends an
31
anlyzd to the Originating MSC.
32
Parameters Usage Type 33
34
ACCDEN Reason for denying access. R
35
ANNLIST List of tones or announcements to play. If not O 36
included, the announcement is based on the 37
ACCDEN value. 38
39
f. The Originating MSC provides denial treatment. 40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Pre-Paid Charging 4-62 TIA/EIA-41.3-D Modifications


PN-4287

1
2 8.X.24 HLR-Based Call Forwarding No Answer
3
4
This scenario describes PPC invocation upon Call Forwarding No Answer (CFNA). The
5
call is forwarded by the Originating MSC.
6
7
Originating System
8
9
10
MSC HLR SCP
11
12
call origination
13 a
14 LOCREQ [MSCID, BILLID, DGTSDIAL, TRIGTYPE, TRANSCAP, WINCAP]
15 b
16 LRT
17
locreq [MSCID, MIN, IMSI, TRIGADDRLIST]
c
18
19 ANLYZD [MSCID, BILLID, DGTSDIAL, MSID, TRIGTYPE]
d
20
ANZT
21 anlyzd [DMH_SVCID]
22
e
23 LOCREQ [MSCID, BILLID, DGTSDIAL, TRIGTYPE, TRANSCAP, WINCAP]
24 f
25 LRT
locreq [MSCID, MIN, IMSI, TERMLIST, REDIND]
26 g
27
ANLYZD [MSCID, BILLID, MSID, MDN, RoutingInfo, REDIND, TRIGTYPE, TOD, TDO]
28 h
29
ANZT
30 anlyzd [ ]
i
31
32
no answer timeout j
33
34
TRANUMREQ [MSCID, MSID, BILLID, REDREASON, TRANSCAP, WINCAP]
35
k
36
TTNRT
37 tranumreq [TERMLIST, REDIND, TRIGADDRLIST]
l
38
39 ANLYZD [MSCID, BILLID, MSID, MDN, RoutingInfo, REDIND, TRIGTYPE, TOD, TDO]
40
m
ANZT
41 anlyzd [DMH_SVCID]
42 n
43
call forward setup
44 o
45
answer
46 p
47
48 OANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO]
q
49
50 cut-through
r
51
52
Figure 8.X.24-1 HLR-Based Call Forwarding No Answer (1 of 2)
53
54
55
a-i. Same as Section 8.X.21, Steps a-i.
56
57 j. The Originating MSC pages and alerts the MS. The MS does not answer. The
58 MSC’s no answer timer expires.
59
60

TIA/EIA-41.3-D Modifications 4-63 Pre-Paid Charging


PN-4287

1
k. The Originating MSC sends a TRANUMREQ to the HLR
2

l. The subscriber has CFNA active. The HLR sends a tranumreq to the MSC. The 3

TERMLIST parameter indicates call forwarding to the PSTN. The 4

TRIGADDRLIST parameter is included to arm triggers for the forwarded call (e.g., 5

Calling_Routing_Address_Available, O_Answer, O_Disconnect). 6


7
Parameters Usage Type 8
9
TERMLIST Call termination information. R
10
REDIND DMH_RedirectionIndicator. Reason for R 11
extending the incoming call. 12
13
TRIGADDRLIST Indicates WIN triggers for the forwarded call leg. R
14
m. The Serving MSC analyzes the routing information and prepares to route the call. 15
The MSC detects the Calling_Routing_Address_Available trigger and sends an 16
ANLYZD to the SCP associated with this trigger. 17
18
Parameters Usage Type 19

MSCID Serving MSC MSCID. R 20


21
MSID Served MS MSID. R 22
23
MDN Mobile directory number. Include if available. O
24
BILLID BillingID. Used to relate queries for this call. R 25
26
RoutingInfo: Call routing information:
27
[DSTDGTS] DestinationDigits. The network address of the R 28
destination. 29
30
[CARDGTS] CarrierDigits. Interexchange carrier for call O
31
setup. Include if applicable.
32
[ROUTDGTS] RoutingDigits. Special routing instructions. O 33
Include if applicable. 34
35
REDIND DMH_RedirectionIndicator. Reason for R
extending the incoming call. 36
37
TRIGTYPE Indicates the trigger encountered. R 38
39
TOD TimeOfDay. The current time (UTC). R
40
TDO TimeDateOffset. The time offset of local civil R 41
time. 42
43
n. The SCP sends an anlyzd to the MSC. The DMH_SVCID parameter is set to
44
indicate PPC was invoked.
45

o. The Originating MSC forwards the call. 46


47
p. The call is answered. 48
49
50
51
52
53
54
55
56
57
58
59
60

Pre-Paid Charging 4-64 TIA/EIA-41.3-D Modifications


PN-4287

1
q. The Originating MSC detects the O_Answer trigger and sends an OANSWER to the
2
SCP associated with this trigger.
3
4 Parameters Usage Type
5
MSCID Serving MSC MSCID. R
6
7 MSID Served MS MSID. R
8
9
MDN Mobile directory number. Include if available. O
10 BILLID BillingID. Used to relate queries for this call. R
11
12 TRIGTYPE Indicates the trigger encountered. R
13
TOD TimeOfDay. The time of call answer (UTC). R
14
15 TDO TimeDateOffset. The time offset of local civil R
16 time.
17
Upon receipt of the OANSWER, the SCP begins decrementing the subscriber’s
18
account balance.
19
20 r. The call is cut through and connected.
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-65 Pre-Paid Charging


PN-4287

1
Originating System 2
3
MSC HLR SCP 4
5
6
7
8
disconnect 9
s
10
ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO] 11
t 12
ODT
odisconnect [ ] 13
u 14
15
call release
v 16
17
Figure 8.X.24-2 HLR-Based Call Forwarding No Answer (2 of 2) 18
19
20
s. The MSC receives a disconnect indication for the terminating party. The MSC 21
releases the call leg toward the terminating party. 22
23
t. The Originating MSC detects the O_Disconnect trigger and sends an
24
ODISCONNECT to the SCP associated with this trigger.
25

Parameters Usage Type 26


27
MSCID Serving MSC MSCID. R 28

MSID Served MS MSID. R 29


30
MDN Mobile directory number. Include if available. O 31
32
BILLID BillingID. Used to relate queries for this call. R
33
TRIGTYPE Indicates the trigger encountered. R 34
35
RELCAUSE Call release cause. R
36
TOD TimeOfDay. The time of call disconnect (UTC). R 37
38
TDO TimeDateOffset. The time offset of local civil R
39
time.
40

Upon receipt of the ODISCONNECT, the SCP stops decrementing the subscriber’s 41

account balance. 42
43
u. The SCP sends an empty odisconnect to the Originating MSC. 44
45
v. The MSC releases the call leg to the calling party. 46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Pre-Paid Charging 4-66 TIA/EIA-41.3-D Modifications


PN-4287

1
2 8.X.25 SCP-Based Call Forwarding No Answer
3
4
This scenario describes PPC invocation after SCP-based call forwarding is invoked based
5
on a no answer event. The call is forwarded by the Originating MSC.
6
7
Originating System CF PPC
8
9
10
MSC HLR SCP SCP
11
12
call origination
13 a
14 LOCREQ [MSCID, BILLID, DGTSDIAL, TRIGTYPE, TRANSCAP, WINCAP]
15 b
16 LRT
17
locreq [MSCID, MIN, IMSI, TRIGADDRLIST]
c
18
19 ANLYZD [MSCID, BILLID, DGTSDIAL, MSID, TRIGTYPE]
d
20
ANZT
21 anlyzd [DMH_SVCID]
22
e
23 LOCREQ [MSCID, BILLID, DGTSDIAL, TRIGTYPE, TRANSCAP, WINCAP]
24 f
25 LRT
locreq [MSCID, MIN, IMSI, TERMLIST, REDIND]
26 g
27
ANLYZD [MSCID, BILLID, MSID, MDN, RoutingInfo, REDIND, TRIGTYPE, TOD, TDO]
28 h
29
ANZT
30 anlyzd [ ]
i
31
32
no answer timeout j
33
34
TNOANS [MSCID, TRANSCAP, WINCAP, MSID, BILLID, TRIGTYPE
35
k
36
37
TNAT SIM Interaction l
38
39 tnoans [TERMLIST, REDIND, TRIGADDRLIST]
40
m
41 ANLYZD [MSCID, BILLID, MSID, MDN, RoutingInfo, REDIND, TRIGTYPE, TOD, TDO]
42 n
43 ANZT
anlyzd [DMH_SVCID]
44 o
45
call forward setup
46 p
47
48 answer
q
49
50 OANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO]
r
51
52 cut-through
53 s
54
55
Figure 8.X.25-1 SCP-Based Call Forwarding No Answer (1 of 2)
56
57
a-b. Same as Section 8.X.21, steps a-b.
58
59
60

TIA/EIA-41.3-D Modifications 4-67 Pre-Paid Charging


PN-4287

1
c. The HLR sends the locreq to the Originating MSC with the TRIGADDRLIST
2
parameter set to indicate t h e Initial_Termination, Location,
3
Called_Routing_Address_Available, T_Answer, T_No_Answer and T_Disconnect
4
triggers shall be armed.
5
Parameters Usage Type 6
7
MSCID Serving MSC MSCID. R
8

MIN Called MS MIN. R 9


10
IMSI Called MS IMSI. Include if available. O 11

TRIGADDRLIST WIN Triggers to arm for this call leg. R 12


13
d-i. Same as Section 8.X.21, steps d-i. 14
15
j. The Originating MSC pages and alerts the MS. The MS does not answer. The 16
MSC’s no answer timer expires. 17
18
k. The Originating MSC detects the T_No_Answer trigger and sends a TNOANS to the
19
SCP associated with this trigger.
20

l. The SCP may send a query (e.g., SERVREQ, SEARCH) to a Service Interaction 21

Manager (SIM) on another service logic network entity to determine which, if any, 22

triggers should be armed for the forwarded call. 23


24
m. The service logic program determines the call should be forwarded. The SCP sends 25
a tnoans to the MSC. The TERMLIST parameter indicates call forwarding to the 26
PSTN. The TRIGADDRLIST parameter is included to arm triggers for the 27
forwarded call (e.g., C a l l i n g _ R o u t i n g _ A d d r e s s _ A v a i l a b l e, O_Answer, 28
O_Disconnect). 29
30
Parameters Usage Type
31
TERMLIST Call termination information. R 32
33
REDIND DMH_RedirectionIndicator. Reason for R
34
extending the incoming call.
35
TRIGADDRLIST Indicates WIN triggers for the forwarded call leg. R 36
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 4-68 TIA/EIA-41.3-D Modifications


PN-4287

1
n. The Originating MSC analyzes the dialed digits and prepares to route the call. The
2
MSC detects the Calling_Routing_Address_Available trigger and sends an ANLYZD
3
to the SCP associated with this trigger.
4
5 Parameters Usage Type
6
MSCID Serving MSC MSCID. R
7
8 MSID Served MS MSID. R
9
10
MDN Mobile directory number. Include if available. O
11 BILLID BillingID. Used to relate queries for this call. R
12
13 RoutingInfo: Call routing information:
14
[DSTDGTS] DestinationDigits. The network address of the R
15 destination.
16
17 [CARDGTS] CarrierDigits. Interexchange carrier for call O
18
setup. Include if applicable.
19 [ROUTDGTS] RoutingDigits. Special routing instructions. O
20 Include if applicable.
21
22
REDIND DMH_RedirectionIndicator. Reason for R
extending the incoming call.
23
24 TRIGTYPE Indicates the trigger encountered. R
25
26
TOD TimeOfDay. The current time (UTC). R
27 TDO TimeDateOffset. The time offset of local civil R
28 time.
29
30 o. The SCP sends an anlyzd to the MSC. The DMH_SVCID parameter is set to
31 indicate PPC was invoked.
32
33
p. The Originating MSC forwards the call.
34
q. The call is answered.
35
36 r. The Originating MSC detects the O_Answer trigger and sends an OANSWER to the
37 SCP associated with this trigger.
38
39
Parameters Usage Type
40 MSCID Serving MSC MSCID. R
41
42 MSID Served MS MSID. R
43
MDN Mobile directory number. Include if available. O
44
45 BILLID BillingID. Used to relate queries for this call. R
46
TRIGTYPE Indicates the trigger encountered. R
47
48 TOD TimeOfDay. The time of call answer (UTC). R
49
TDO TimeDateOffset. The time offset of local civil R
50
time.
51
52 Upon receipt of the OANSWER, the SCP begins decrementing the subscriber’s
53 account balance.
54
55 s. The call is cut through and connected.
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-69 Pre-Paid Charging


PN-4287

1
Originating System CF PPC 2
3
MSC HLR SCP SCP 4
5
6
7
8
disconnect 9
t
10
ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO] 11
u 12
ODT
odisconnect [ ] 13
v 14
15
call release
w 16
17
Figure 8.X.25-2 SCP-Based Call Forwarding No Answer (2 of 2) 18
19
20
t. The MSC receives a disconnect indication for the terminating party. The MSC 21
releases the call leg toward the terminating party. 22
23
u. The Originating MSC detects the O_Disconnect trigger and sends an
24
ODISCONNECT to the SCP associated with this trigger.
25

Parameters Usage Type 26


27
MSCID Serving MSC MSCID. R 28

MSID Served MS MSID. R 29


30
MDN Mobile directory number. Include if available. O 31
32
BILLID BillingID. Used to relate queries for this call. R
33
TRIGTYPE Indicates the trigger encountered. R 34
35
RELCAUSE Call release cause. R
36
TOD TimeOfDay. The time of call disconnect (UTC). R 37
38
TDO TimeDateOffset. The time offset of local civil R
39
time.
40

Upon receipt of the ODISCONNECT, the SCP stops decrementing the subscriber’s 41

account balance. 42
43
v. The SCP sends an empty odisconnect to the Originating MSC. 44
45
w. The Originating MSC releases the call leg to the calling party. 46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Pre-Paid Charging 4-70 TIA/EIA-41.3-D Modifications


PN-4287

1
2 8.X.26 HLR-Based Call Forwarding Busy
3
4
This scenario describes PPC invocation upon Call Forwarding Busy (CFB).
5
6
Originating System Serving System
7
8
9
MSC HLR SCP VLR MSC
10
11 call origination
12 a
13 LOCREQ [MSCID, BILLID, DGTSDIAL, TRIGTYPE, TRANSCAP, WINCAP]
14 b
15 LRT
16
locreq [MSCID, MIN, IMSI, TRIGADDRLIST]
c
17
ANLYZD [MSCID, BILLID, DGTSDIAL, MSID, TRIGTYPE]
18
d
19
ANZT
20 anlyzd [DMH_SVCID]
21
e
22 LOCREQ [MSCID, BILLID, DGTSDIAL, TRIGTYPE, TRANSCAP, WINCAP]
23 f
24
ROUTREQ [MSCID, BILLID, MSID]
25 g
26
ROUTREQ [MSCID, BILLID, MSID]
27 h
28
LRT RRT RRT
29 routreq [ACCDEN]
i
30
31 routreq [ACCDEN]
j
32
33 locreq [MSCID, MIN, IMSI, TERMLIST, REDIND, TRIGADDRLIST]
34 k
35 ANLYZD [MSCID, MSID, MDN, BILLID, RoutingInfo, REDIND, TRIGTYPE, TOD, TDO]
36 l
37 ANZT
anlyzd [DMH_SVCID]
38 m
39
40
call forward setup
n
41
42
answer
o
43
44
OANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO]
45 p
46
cut through
47
q
48
49
50 disconnect
51
r
52 ODISCONNECT [MSCID, TRANSCAP, WINCAP, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]
53 s
54 ODT
odisconnect [ ]
55 t
56
call release
57 u
58
59 Figure 8.X.26 HLR-Based Call Forwarding Busy
60

TIA/EIA-41.3-D Modifications 4-71 Pre-Paid Charging


PN-4287

1
a-h. Same as Section 8.X.22, Steps a-h.
2

i. The MS is engaged in a call and Call Waiting is not applicable. The Serving MSC 3

sends a routreq to the VLR. 4


5
Parameters Usage Type 6
7
ACCDEN Reason for denying access. R
8
j. The VLR forwards the routreq to the HLR. 9
10
k. The subscriber has CFB active. The HLR sends a locreq to the MSC. The 11
TERMLIST parameter indicates call forwarding to the PSTN. The 12
TRIGADDRLIST parameter is included to arm triggers for the forwarded call (e.g., 13
Calling_Routing_Address_Available, O_Answer, O_Disconnect). 14
15
Parameters Usage Type
16
MSCID Serving MSC MSCID. R 17
18
MIN Called MS MIN. R
19
IMSI Called MS IMSI. Include if available. O 20
21
TERMLIST Call termination information. R
22

REDIND DMH_RedirectionIndicator. Reason for extending R 23


the incoming call. 24
25
TRIGADDRLIST Indicates WIN triggers for the forwarded call leg. R
26
27
l-u. Same as Section 8.X.24, Steps m-v.
28
29
30
31
32
33
34
35
36
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 4-72 TIA/EIA-41.3-D Modifications


PN-4287

1
2 8.X.27 SCP-Based Call Forwarding Busy Invocation with Call Collision
3
4
This scenario describes PPC interaction with SCP-based call forwarding on a busy
5
condition encountered after call delivery.
6
7
Originating System CF PPC Serving System
8
9
10
MSC HLR SCP SCP VLR MSC
11
12
13
call origination
a
14
15 LOCREQ [MSCID, BILLID, DGTSDIAL, TRIGTYPE, TRANSCAP, WINCAP]
16
b
LRT
17 locreq [MSCID, MIN, IMSI, TRIGADDRLIST]
18 c
19 ANLYZD [MSCID, BILLID, DGTSDIAL, MSID, TRIGTYPE]
20 d
21 ANZT
anlyzd [DMH_SVCID]
22 e
23
LOCREQ [MSCID, BILLID, DGTSDIAL, TRIGTYPE, TRANSCAP, WINCAP]
24
f
25
26 ROUTREQ [MSCID, BILLID, MSID]
g
27
28 ROUTREQ [MSCID, BILLID, MSID]
29 h
30 LRT RRT RRT
routreq [TLDN]
31 i
32
routreq [TLDN]
33 j
34 TLDNAT
35
locreq [MSCID, MIN, IMSI, TERMLIST, REDIND]
k
36
ANLYZD [MSCID, MSID, MDN, BILLID, RoutingInfo, REDIND, TRIGTYPE, TOD, TDO]
37
l
38
ANZT
39 anlyzd [ ]
40
m
41 call setup
42 n
43
44 MS busy o
45
REDREQ [REDREASON]
46 p
47
RDRT
48 redreq [ ]
q
49
50
Figure 8.X.27-1 SCP-Based Call Forwarding Busy Invocation with Call Collision (1 of 2)
51
52
53 a-b. Same as Section 8.X.22, Steps a-b.
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-73 Pre-Paid Charging


PN-4287

1
c. The HLR sends the locreq to the Originating MSC with the TRIGADDRLIST
2
parameter set to indicate the Initial_Termination, Location, T _ B u s y and
3
Called_Routing_Address_Available triggers shall be armed.
4
Parameters Usage Type 5
6
MSCID Serving MSC MSCID. R
7

MIN Called MS MIN. R 8


9
IMSI Called MS IMSI. Include if available. O 10

TRIGADDRLIST WIN Triggers to arm for this call leg. R 11


12
d-n. Same as Section 8.X.22, Steps d-n. 13
14
o. The MS is engaged in a call and Call Waiting is not applicable. 15
16
p. The Serving MSC sends a REDREQ to the Originating MSC indicating the MS is
17
busy.
18

q. The Originating MSC responds with a redreq. 19


20
Originating System CF PPC Serving System 21
22

MSC HLR SCP SCP VLR MSC 23


24
25
26
call release
r 27

TBUSY [MSCID, MSID, BILLID, TRIGTYPE] 28

s 29
30
31
TBT SIM Interaction t
32
tbusy [REDIND, TERMLIST, TRIGADDRLIST] 33
u
34
ANLYZD [MSCID, MSID, MDN, BILLID, RoutingInfo, REDIND, TRIGTYPE, TOD, TDO] 35
v 36
ANZT
anlyzd [DMH_SVCID] 37
w 38
39
call forward setup
x 40
41
answer
y 42
43
OANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO]
44
z
45
cut through 46
aa
47
48
disconnect 49
bb 50

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


cc 52

ODT 53
odisconnect [ ]
dd 54
55
call release 56
ee
57
58
Figure 8.X.27-2 SCP-Based Call Forwarding Busy Invocation with Call Collision (2 of 2)
59
60

Pre-Paid Charging 4-74 TIA/EIA-41.3-D Modifications


PN-4287

1
r. The Originating MSC releases the call leg to the Serving MSC.
2
3 s. The Originating MSC detects the T_Busy trigger and sends a TBUSY to the SCP
4 associated with this trigger.
5
6 t. The SCP may send a query (e.g., SERVREQ, SEARCH) to a SIM on another service
7 logic network entity to determine which, if any, triggers should be armed for the
8 forwarded call.
9
10
u. The service logic determines the call should be forwarded and the SCP sends a
11
tbusy to the MSC. The TERMLIST parameter indicates call forwarding to the
12
PSTN. The TRIGADDRLIST parameter is included to arm triggers for the
13
forwarded call (e.g., C a l l i n g _ R o u t i n g _ A d d r e s s _ A v a i l a b l e, O_Answer,
14
O_Disconnect).
15 Parameters Usage Type
16
17 TERMLIST Call termination information. R
18
REDIND DMH_RedirectionIndicator. Reason for extending R
19 the incoming call.
20
21 TRIGADDRLIST Indicates WIN triggers for the forwarded call leg. R
22
v-ee. Same as Section 8.X.24, Steps m-v.
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-75 Pre-Paid Charging


PN-4287

8.X.28 HLR-Based Call Forwarding Unconditional 2


3
4
This scenario describes PPC invocation upon Call Forwarding Unconditional (CFU).
5
6
Originating System
7
8
MSC HLR SCP 9
10
11
call origination
a 12

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

b 14

LRT 15
locreq [MSCID, MIN, IMSI, TRIGADDRLIST] 16
c
17
ANLYZD [MSCID, BILLID, DGTSDIAL, MSID, TRIGTYPE] 18
d
19
ANZT
anlyzd [DMH_SVCID] 20
e 21
LOCREQ [MSCID, BILLID, DGTSDIAL, TRIGTYPE, TRANSCAP, WINCAP] 22
f 23
LRT 24
locreq [MSCID, MIN, IMSI, TERMLIST, REDIND, TRIGADDRLIST]
g 25
26
ANLYZD [MSCID, BILLID, MSID, MDN, RoutingInfo, REDIND, TRIGTYPE, TOD, TDO]
h 27
28
ANZT
anlyzd [DMH_SVCID] 29
i
30
call forward setup 31
j
32

answer 33
k 34
35
OANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO]
l 36
37
cut-through
m 38
39

disconnect 40
n 41

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


o 43

ODT 44
odisconnect [ ]
p 45
46
call release 47
q
48
49
Figure 8.X.28 HLR-Based Call Forwarding Unconditional
50
51

a-f. Same as Section 8.X.22, Steps a-f. 52


53
54
55
56
57
58
59
60

Pre-Paid Charging 4-76 TIA/EIA-41.3-D Modifications


PN-4287

1
g. The subscriber has CFU active. The HLR sends a locreq to the MSC with
2
instructions to forward the call to the PSTN. The TRIGADDRLIST parameter is
3
included to arm triggers for the forwarded call (e.g.,
4
Calling_Routing_Address_Available, O_Answer, O_Disconnect).
5
6 Parameters Usage Type
7
MSCID Serving MSC MSCID. R
8
9 MIN Called MS MIN. R
10
11
IMSI Called MS IMSI. Include if available. O
12 TERMLIST Call termination information. R
13
14 REDIND DMH_RedirectionIndicator. Reason for extending R
15
the incoming call.
16 TRIGADDRLIST Indicates WIN triggers for the forwarded call leg. R
17
18 h-q. Same as Section 8.X.24, Steps m-v.
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-77 Pre-Paid Charging


PN-4287

8.X.29 SCP-Based Call Forwarding Unconditional 2


3
4
This scenario describes PPC invocation for SCP-based unconditional call forwarding.
5
6
Originating System CF PPC
7
8
MSC HLR SCP SCP 9
10
11
call origination
a 12

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

b 14

LRT 15
locreq [MSCID, MIN, IMSI, TRIGADDRLIST] 16
c
17
ANLYZD [MSCID, BILLID, DGTSDIAL, MSID, TRIGTYPE] 18
d
19
ANZT
anlyzd [DMH_SVCID] 20
e 21
ANLYZD [MSCID, TRANSCAP, WINCAP, BILLID, DGTSDIAL, MSID, TRIGTYPE] 22
f 23
24
ANZT SIM Interaction g 25
26
anlyzd [TERMLIST, REDIND, TRIGADDRLIST]
h 27
28
ANLYZD [MSCID, BILLID, MSID, MDN, RoutingInfo, REDIND, TRIGTYPE, TOD, TDO]
29
i
30
ANZT
anlyzd [DMH_SVCID] 31
j
32

call forward setup 33


k 34
35
answer
l 36
37
OANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO]
m 38
39
cut-through 40
n
41
42
disconnect
o 43
44
ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]
p 45
46
ODT
odisconnect [ ] 47
q
48
call release 49
r
50
51
Figure 8.X.29 SCP-Based Call Forwarding Unconditional
52
53
54
a-b. Same as Section 8.X.22, Steps a-b.
55
56
57
58
59
60

Pre-Paid Charging 4-78 TIA/EIA-41.3-D Modifications


PN-4287

1
c. The HLR sends the locreq to the Originating MSC with the TRIGADDRLIST
2
parameter set to indicate the Initial_Termination, Advanced_Termination, Location
3
and Called_Routing_Address_Available triggers shall be armed.
4
5 Parameters Usage Type
6
MSCID Serving MSC MSCID. R
7
8 MIN Called MS MIN. R
9
10
IMSI Called MS IMSI. Include if available. O
11 TRIGADDRLIST WIN Triggers to arm for this call leg. R
12
13 d-e. Same as Section 8.X.22, Steps d-e.
14
15
f. The Originating MSC detects the Advanced_Termination trigger and sends an
16
ANLYZD to the associated SCP.
17
g. The SCP may send a query (e.g., SERVREQ, SEARCH) to a SIM on another
18
platform to determine which, if any, triggers should be armed for the forwarded call.
19
20 h. The subscriber has an unconditional call forwarding service. The SCP sends the
21 anlyzd to the MSC with instructions to forward the call to the PSTN. The
22 TRIGADDRLIST parameter is included to arm triggers for the forwarded call (e.g.,
23 Calling_Routing_Address_Available, O_Answer, O_Disconnect).
24
25 Parameters Usage Type
26
TERMLIST Call termination information. R
27
28 REDIND DMH_RedirectionIndicator. Reason for extending R
29 the incoming call.
30
TRIGADDRLIST Indicates WIN triggers for the forwarded call leg. R
31
32 i-r. Same as Section 8.X.24, Steps m-v.
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-79 Pre-Paid Charging


PN-4287

8.X.30 Call Forwarding Unconditional: Location Trigger Not Required for 2

PPC 3
4
5
This scenario describes PPC invocation when the Location trigger is not required.
6
7
Originating System CF PPC
8
9
MSC HLR SCP SCP 10
11
12
call origination
a 13
14
LOCREQ [MSCID, BILLID, DGTSDIAL, TRIGTYPE, TRANSCAP, WINCAP]
15
b
16
SERVREQ [SRVID, MSCID, BILLID, DGTSDIAL, MSID, TRIGTYPE] 17
c
18
SVRT
servreq [DMH_SVCID] 19
d 20
LRT
SERVREQ [SRVID, MDN] 21
e 22
SVRT 23
servreq [REDIND, TERMLIST]
f 24
25
locreq [MSCID, MIN, IMSI, TERMLIST, REDIND, TRIGADDRLIST, DMH_SVCID]
g 26
27
ANLYZD [MSCID, BILLID, MSID, MDN, RoutingInfo, REDIND, TRIGTYPE, TOD, TDO]
28
h
29
ANZT
anlyzd [ ] 30
i
31

call forward setup 32


j 33
34
answer
k 35
36
OANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO]
l 37
38
cut-through 39
m
40
41
disconnect
n 42
43
ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]
o 44
45
ODT
odisconnect [ ] 46
p
47
call release 48
q
49
50
Figure 8.X.30 Call Forwarding Unconditional: Location Trigger Not Required for PPC
51
52
53
a-b. Same as Section 8.X.22, Steps a-b.
54
c. The HLR determines PPC is active and sends a SERVREQ to the PPC SCP. 55
56
d. The PPC SCP determines that the called subscriber’s account balance is above the 57
threshold level and returns the servreq to the HLR. The DMH_SVCID is set to 58
indicate PPC was invoked. 59
60

Pre-Paid Charging 4-80 TIA/EIA-41.3-D Modifications


PN-4287

1
e. The HLR determines that CFU is active and sends a SERVREQ to the CFU SCP.
2
3 f. The CFU SCP returns the servreq to the HLR with call forwarding instructions.
4
5 g. The HLR sends a locreq to the MSC with instructions to forward the call to the
6 PSTN. In addition, the TRIGADDRLIST parameter is included to arm triggers for
7 the forwarded call (e.g., Calling_Routing_Address_Available, O_Answer,
8 O_Disconnect).
9
Parameters Usage Type
10
11 MSCID Serving MSC MSCID. R
12
MIN Called MS MIN. R
13
14 IMSI Called MS IMSI. Include if available. O
15
16
TERMLIST Call termination information. R
17 REDIND DMH_RedirectionIndicator. Reason for extending R
18 the incoming call.
19
20
TRIGADDRLIST Indicates WIN triggers for the forwarded call leg. R
21 DMH_SVCID ID of the Service Logic Program invoked on behalf R
22 of the MS (DMH_SVCID=PPC).
23
24 h-q. Same as Section 8.X.22, Steps m-v.
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-81 Pre-Paid Charging


PN-4287

8.X.31 Call Delivery with Call Waiting 2


3
4
This scenario describes PPC invocation for Call Delivery and Call Delivery with Call
5
Waiting.
6
7
Originating System Serving System
8
9
MSC HLR SCP VLR MSC 10
11
12
13
Same as Call Delivery with Intersystem Termination, Section 8.X.22, Steps a-q
14
15
call-2 origination
r 16
17
LOCREQ [MSCID, BILLID, DGTSDIAL, TRIGTYPE, TRANSCAP, WINCAP]
18
s
19
LRT
locreq [MSCID, MIN, IMSI, TRIGADDRLIST] 20
t
21
ANLYZD [MSCID, BILLID, DGTSDIAL, MSID, TRIGTYPE] 22
u 23
ANZT 24
anlyzd [DMH_SVCID]
v 25

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

w 27
28
ROUTREQ [MSCID, BILLID, MSID] 29
x
30
ROUTREQ [MSCID, BILLID, MSID] 31
y
32
LRT RRT RRT
routreq [TLDN] 33
z 34

routreq [TLDN] 35
aa 36
TLDNAT 37
locreq [MSCID, MIN, IMSI, TERMLIST, REDIND]
bb 38
39
ANLYZD [MSCID, MSID, MDN, BILLID, RoutingInfo, REDIND, TRIGTYPE, TOD, TDO]
cc 40
41
ANZT
anlyzd [ ] 42
dd
43
call-2 setup 44
ee
45

call waiting alert 46


ff 47
48
MS answer gg 49
50
TANSWER [MSCID, MSID, MDN, BILLID, FEATIND, TRIGTYPE, TOD, TDO] 51
hh 52
call-2 cut through 53
ii 54
55
Figure 8.X.31-1 Call Delivery with Call Waiting (1 of 2) 56
57
58
a-q. Same as Section 8.X.22, Steps a-q. 59
60

Pre-Paid Charging 4-82 TIA/EIA-41.3-D Modifications


PN-4287

1
r. Another call origination and the dialed MS address digits (i.e., directory number)
2
are received by the Originating MSC.
3
4 s-dd. Same as Section 8.X.22, Steps b-m.
5
6 ee. The Originating MSC sets up the second call to the subscriber.
7
8
ff. When the (second) inter-MSC call is received at the Serving MSC, the MS receives
9
normal call waiting treatment.
10
gg. The MS answers the second call (i.e., the subscriber presses the SEND key).
11
12
hh. The Serving MSC detects the T_Answer trigger and sends a TANSWER to the SCP
13
associated with this trigger.
14
15 Parameters Usage Type
16
MSCID Serving MSC MSCID. R
17
18 MSID Served MS MSID. R
19
MDN Mobile directory number. Include if available. O
20
21 BILLID BillingID. Used to relate queries for this call. R
22
23
FEATIND FeatureIndicator. Indicates the feature invoked R
with the call (e.g., Call Waiting).
24
25 TRIGTYPE Indicates the trigger encountered. R
26
27
TOD TimeOfDay. The time of call answer (UTC). R
28 TDO TimeDateOffset. The time offset of local civil R
29 time.
30
31 ii. The first calling party is put on hold and the second calling party is connected to the
32 MS.
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-83 Pre-Paid Charging


PN-4287

1
Originating System Serving System 2
3
MSC HLR SCP VLR MSC 4
5
6
7
8
call-2 disconnect 9
jj
10
TDISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO] 11
kk 12
TDT
tdisconnect [DMH_SVCID] 13
ll 14

call-1 cut through 15


mm 16
17
18
19
MS disconnect nn
20

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


oo 22

TDT 23
tdisconnect [DMH_SVCID]
pp 24
25
call-1 release 26
qq
27
28
Figure 8.X.31-2 Call Delivery with Call Waiting (2 of 2)
29
30

jj. The second calling party disconnects. 31


32
kk. The Serving MSC detects the T_Disconnect trigger and sends a TDISCONNECT to 33
the SCP associated with this trigger. 34
35
Parameters Usage Type
36
MSCID Serving MSC MSCID. R 37
38
MSID Served MS MSID. R
39

MDN Mobile directory number. Include if available. O 40


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

TRIGTYPE Indicates the trigger encountered. R 43


44
RELCAUSE Call release cause. R 45
46
TOD TimeOfDay. The time of call disconnect (UTC). R
47
TDO TimeDateOffset. The time offset of local civil R 48
time. 49
50
Upon receipt of the TDISCONNECT, the SCP stops decrementing the subscriber’s
51
account balance for the second call.
52

ll. The SCP sends a tdisconnect to the Serving MSC. The DMH_SVCID 53

parameter is set to indicate PPC was invoked. 54


55
mm. The subscriber is connected to the party on hold. 56
57
nn. The subscriber ends the call. 58
59
60

Pre-Paid Charging 4-84 TIA/EIA-41.3-D Modifications


PN-4287

1
oo. The Serving MSC detects the T_Disconnect trigger and sends a TDISCONNECT to
2
the SCP associated with this trigger.
3
4 Parameters Usage Type
5
MSCID Serving MSC MSCID. R
6
7 MSID Served MS MSID. R
8
9
MDN Mobile directory number. Include if available. O
10 BILLID BillingID. Used to relate queries for this call. R
11
12 TRIGTYPE Indicates the trigger encountered. R
13
RELCAUSE Call release cause. R
14
15 TOD TimeOfDay. The time of call disconnect (UTC). R
16
TDO TimeDateOffset. The time offset of local civil R
17
time.
18
19 Upon receipt of the TDISCONNECT, the SCP stops decrementing the subscriber’s
20 account balance for the first call.
21
22 pp. The SCP sends a tdisconnect to the Serving MSC. The DMH_SVCID
23 parameter is set to indicate PPC was invoked.
24
qq. The Serving MSC releases the call to the first called party.
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-85 Pre-Paid Charging


PN-4287

8.X.32 Mid-Call Verification of Call Status 2


3
4
This scenario describes an MS call origination with a mid-call verification by PPC
5
service logic of call status.
6
7
Serving System
8
9
IP SCP MSC 10
11
12
13
MS Call Origination: Same as Section 8.X.3, Steps a-s
14
15
16

CCDIR [MSCID, MSID, MDN, BILLID] 17


t 18
CCDT 19
ccdir [ ]
u 20
21

MS disconnect v 22
23
ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO] 24
w 25
ODT 26
odisconnect [ ]
x 27
28
call release 29
y
30

Figure 8.X.32 Mid-Call Verification of Call Status 31


32
33
a-s. Same as Section 8.X.3, Steps a-s. 34
35
t. The SCP sends a CCDIR to the Serving MSC. No action is requested. 36
37
Parameters Usage Type
38
MSCID SCP MSCID. Include to identity the requesting R 39
network entity. 40
41
MSID Served MS MSID. R
42
MDN Mobile directory number. Include if available. O 43
44
BILLID BillingID. Used to relate queries for this call. R
45

u. The Serving MSC sends a ccdir to the SCP for the active call. (Note: the Serving 46

MSC sends a RETURN ERROR in response to the CCDIR if the call indicated by 47

the received BILLID parameter is not active.) 48


49
v-y. Same as Section 8.X.3, Steps t-w. 50
51
52
53
54
55
56
57
58
59
60

Pre-Paid Charging 4-86 TIA/EIA-41.3-D Modifications


PN-4287

1
2 8.X.33 MS-to-MS Call: SN Based
3
4
This scenario describes an MS-to-MS call. Both users are PPC subscribers of the same
5
system. Both subscribers are currently in the home service area.
6
7
Home System
8
9
10
MS-1 MS-2 MSC HLR SN
11
12
13 MS-1 origination
a
14
15 BILLID1 ORREQ [MSCID, MSID, MDN, BILLID, DGTSDIAL, TRIGTYPE]
16
b
ORT
17 orreq [DMH_SVCID]
18 c
19 ANLYZD [MSCID, WINCAP, MSID, MDN, BILLID, DGTSDIAL,
20 BILLID1 RoutingInfo, TRIGTYPE, TOD, TDO]
d
21
22
ANZT
23
CONNRES [DSTDGTS, CARDGTS, ROUTDGTS] e
24
TLDNAT
25 call setup
f
26
SSFT
27 announcement
28
g
29 anlyzd [ ]
30 h
31
call release
32 i
33
BILLID2 LOCREQ [MSCID, BILLID, DGTSDIAL, TRIGTYPE, TRANSCAP, WINCAP]
34 j
35
LRT
36 locreq [MSCID, MIN, IMSI, TRIGADDRLIST]
k
37
38 BILLID2 ANLYZD [MSCID, BILLID, DGTSDIAL, MSID, TRIGTYPE]
l
39
ANZT
40 anlyzd [DMH_SVCID]
41 m
42
BILLID2 LOCREQ [MSCID, BILLID, DGTSDIAL, TRIGTYPE, TRANSCAP, WINCAP]
43 n
44 LRT
locreq [MSCID, MIN, IMSI, TERMLIST, REDIND]
45 o
46
BILLID2 ANLYZD [MSCID, MSID, MDN, BILLID, RoutingInfo, REDIND, TRIGTYPE, TOD, TDO]
47
p
48
ANZT
49 anlyzd [ ]
q
50
51 alert
52
r
53 MS-2 answer
54 s
55
56 Figure 8.X.33-1 MS-to-MS Call: SN Based (1 of 2)
57
58
59
60

TIA/EIA-41.3-D Modifications 4-87 Pre-Paid Charging


PN-4287

1
a. MS-1 originates a call with dialed digits. The MS origination is received by the
2
Serving MSC.
3

b. The Serving MSC detects the Origination_Attempt_Authorized trigger and sends an 4

ORREQ to the SN associated with this trigger. 5


6
Parameters Usage Type 7
8
MSCID Serving MSC MSCID. R
9
MSID Served MS MSID. R 10
11
MDN Mobile directory number. Include if available. O
12
BILLID BillingID. Used to relate queries for this call. R 13
14
DGTSDIAL Digits entered by served MS. R
15
TRIGTYPE Indicates the trigger encountered. R 16
17
The BILLID parameter is assigned by the Serving MSC for the call origination. 18
19
c. The SN determines that MS-1 has PPC active and the subscriber’s account balance
20
is above the threshold level. The SN sends an orreq to the Serving MSC to
21
indicate call processing shall continue. The DMH_SVCID parameter is set to
22
indicate PPC was invoked for the call origination.
23

d. The Serving MSC analyzes the dialed digits and prepares to route the call. The 24

MSC detects the Calling_Routing_Address_Available trigger and sends an ANLYZD 25

to the SN associated with this trigger. 26


27
Parameters Usage Type 28
29
MSCID Serving MSC MSCID. R
30
WINCAP Serving MSC’s WIN capability. R 31
32
MSID Served MS MSID. R
33
MDN Mobile directory number. Include if available. O 34
35
BILLID BillingID. Used to relate queries for this call. R
36

TOD TimeOfDay. The current time (UTC). R 37


38
TDO TimeDateOffset. The time offset of local civil R 39
time.
40

RoutingInfo: Call routing information: 41


42
[DSTDGTS] DestinationDigits. The network address of the R
43
destination.
44
[CARDGTS] CarrierDigits. Interexchange carrier for call O 45
setup. Include if applicable. 46
47
[ROUTDGTS] RoutingDigits. Special routing instructions. O
Include if applicable. 48
49
DGTSDIAL Digits entered by served MS. O 50
51
TRIGTYPE Indicates the trigger encountered. R
52
53
54
55
56
57
58
59
60

Pre-Paid Charging 4-88 TIA/EIA-41.3-D Modifications


PN-4287

1
e. The SN sends a CONNRES to the Serving MSC with instructions to set up a call leg
2
to the SN.
3
4 Parameters Usage Type
5
DSTDGTS DestinationDigits. The network address of the R
6
destination.
7
8 CARDGTS CarrierDigits. Interexchange carrier for call O
9 setup. Include if applicable.
10
ROUTDGTS RoutingDigits. Special routing instructions. O
11
Include if applicable.
12
13 f. The MSC sets up the call leg to the SN.
14
15 g. The SN plays an announcement to MS-1 indicating the current account balance.
16
17
h. The SN sends an anlyzd to the MSC.
18
i. The Serving MSC releases the call leg to the SN.
19
20 j. The MSC determines the called party number is the directory number of an MS and
21 detects the Mobile_Termination trigger. The Originating MSC sends a LOCREQ to
22 the HLR associated with the MS; this association is made through the dialed MS
23 address digits (which may not be the MIN). The TRANSCAP parameter is set to
24 indicate the MSC can process the TRIGADDRLIST parameter. The WINCAP
25 parameter indicates the MSC supports the Location trigger. The TRIGTYPE
26 parameter is set to indicate the Mobile_Termination trigger was encountered. The
27 BILLID parameter is set by the MSC for the call termination to MS-2.
28
29 Note: the MSC may assign the same value to BILLID1 and BILLID2.
30
k. The HLR sends the locreq to the Originating MSC with the TRIGADDRLIST
31
parameter set to indicate the Initial_Termination, Location, T_A nsw e r,
32
T_Disconnect and Called_Routing_Address_Available triggers shall be armed.
33
34 Parameters Usage Type
35
36
MSCID Serving MSC MSCID. R
37 MIN Called MS (MS-2) MIN. R
38
39 IMSI Called MS (MS-2) IMSI. Include if available. O
40
TRIGADDRLIST Indicates WIN triggers for the call leg to MS-2. R
41
42 l. The MSC detects the Initial_Termination trigger and sends an ANLYZD to the SN
43 indicated in the TRIGADDRLIST parameter. The TRIGTYPE parameter indicates
44 the Initial_Termination trigger was detected.
45
46
Parameters Usage Type
47 MSCID Originating MSC MSCID. R
48
49 BILLID BillingID. Used to relate queries for this call. R
50
DGTSDIAL The called directory number. R
51
52 MSID Called MS MSID. R
53
TRIGTYPE Indicates the trigger encountered. R
54
55 m. The SN determines MS-2 has PPC active and that the subscriber’s account balance
56 is above the threshold level. The SN sends an anlyzd to the MSC to indicate call
57 processing shall continue. The DMH_SVCID parameter is set to indicate PPC was
58 invoked for the call delivery to MS-2.
59
60

TIA/EIA-41.3-D Modifications 4-89 Pre-Paid Charging


PN-4287

1
n. The MSC detects the Location trigger and sends another LOCREQ to the HLR. The
2
TRIGTYPE parameter indicates the Location trigger was encountered.
3

o. The HLR determines MS-2 is served by the MSC and returns a locreq indicating 4

a local termination to MS-2. 5


6
Parameters Usage Type 7
8
MSCID Serving MSC MSCID. R
9
MIN Called MS MIN. R 10
11
IMSI Called MS IMSI. Include if available. O
12
TERMLIST Call termination information. R 13
14
REDIND DMH_RedirectionIndicator. Reason for O
15
extending the incoming call.
16

p. The MSC prepares to terminate the call to MS-2. The MSC detects the 17

Called_Routing_Address_Available trigger and sends an A N L Y Z D to the SN 18

associated with this trigger. The REDIND parameter is set to indicate CD Local. 19
20
Parameters Usage Type 21
22
MSCID Originating MSC MSCID. R
23
MSID Served MS MSID. R 24
25
MDN Mobile directory number. Include if available. O
26
BILLID BillingID. Used to relate queries for this call. R 27
28
RoutingInfo: Call routing information:
29
[DSTDGTS] DestinationDigits. The network address of the O 30
destination. 31
32
[CARDGTS] CarrierDigits. Interexchange carrier for call O
setup. Include if applicable. 33
34
[ROUTDGTS] RoutingDigits. Special routing instructions. O 35
Include if applicable.
36

REDIND DMH_RedirectionIndicator. Reason for R 37


extending the incoming call. 38
39
TRIGTYPE Indicates the trigger encountered. R
40

TOD TimeOfDay. The current time (UTC). R 41


42
TDO TimeDateOffset. The time offset of local civil R 43
time.
44
45
q. The SN sends an anlyzd to the MSC.
46
r. The Originating MSC pages and alerts MS-2. 47
48
s. MS-2 answers. 49
50
51
52
53
54
55
56
57
58
59
60

Pre-Paid Charging 4-90 TIA/EIA-41.3-D Modifications


PN-4287

1
2 Home System
3
4 MS-1 MS-2 MSC HLR SN
5
6
7 BILLID2 TANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO]
8 t
9
cut through
10 u
11
BILLID1 OANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO]
12 v
13
14
15 MS-2 disconnect
w
16
17 BILLID2 TDISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]
18
x
TDT
19 tdisconnect [DMH_SVCID]
20 y
21
BILLID1 ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]
22 z
23 ODT
24 CONNRES [DSTDGTS, CARDGTS, ROUTDGTS]
25 aa
26 TLDNAT
call setup
27 bb
28 SSFT
announcement
29 cc
30
31
odisconnect [ ]
dd
32
33 call release
ee
34
35 MS-1 release
36
ff
37
38
Figure 8.X.33-2 MS-to-MS Call: SN Based (2 of 2)
39
40
t. The MSC detects the T_Answer trigger for the call termination to MS-2. The MSC
41
sends a TANSWER to the SN associated with this trigger.
42
43 Parameters Usage Type
44
MSCID Serving MSC MSCID. R
45
46 MSID Served MS MSID. R
47
48
MDN Mobile directory number. Include if available. O
49 BILLID BillingID. Used to relate queries for this call. R
50
51 TRIGTYPE Indicates the trigger encountered. R
52
TOD TimeOfDay. The time of call answer (UTC). R
53
54 TDO TimeDateOffset. The time offset of local civil R
55 time.
56
u. MS-1 is connected to MS-2.
57
58
59
60

TIA/EIA-41.3-D Modifications 4-91 Pre-Paid Charging


PN-4287

1
v. The Serving MSC detects the O_Answer trigger for MS-1 and sends an OANSWER
2
to the SN associated with this trigger.
3
Parameters Usage Type 4
5
MSCID Serving MSC MSCID. R
6

MSID Served MS MSID. R 7


8
MDN Mobile directory number. Include if available. O 9

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


11
TOD TimeOfDay. The time of call answer (UTC). R 12
13
TDO TimeDateOffset. The time offset of local civil R
time. 14
15
TRIGTYPE Indicates the trigger encountered. R 16
17
Upon receipt of the OANSWER, the SN begins decrementing MS-1’s account
18
balance.
19

w. MS-2 disconnects. 20
21
x. The MSC detects the T_Disconnect trigger for MS-2 and sends a TDISCONNECT to 22
the SN associated with this trigger. 23
24
Parameters Usage Type
25

MSCID Serving MSC MSCID. R 26


27
MSID Served MS MSID. R 28

MDN Mobile directory number. Include if available. O 29


30
BILLID BillingID. Used to relate queries for this call. R 31
32
TRIGTYPE Indicates the trigger encountered. R
33
RELCAUSE Call release cause. R 34
35
TOD TimeOfDay. The time of call disconnect (UTC). R
36
TDO TimeDateOffset. The time offset of local civil R 37
time. 38
39
Upon receipt of the TDISCONNECT, the SN stops decrementing MS-2’s account 40
balance. 41
42
y. The SN sends a tdisconnect to the MSC. The DMH_SVCID parameter is set
43
to indicate PPC was invoked.
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Pre-Paid Charging 4-92 TIA/EIA-41.3-D Modifications


PN-4287

1
z. The MSC detects the O_Disconnect trigger for MS-1 and sends an ODISCONNECT
2
to the SN associated with this trigger.
3
4 Parameters Usage Type
5
MSCID Serving MSC MSCID. R
6
7 MSID Served MS MSID. R
8
9
MDN Mobile directory number. Include if available. O
10 BILLID BillingID. Used to relate queries for this call. R
11
12 TOD TimeOfDay. The time of call disconnect (UTC). R
13
TDO TimeDateOffset. The time offset of local civil R
14 time.
15
16 RELCAUSE Call release cause. R
17
TRIGTYPE Indicates the trigger encountered. R
18
19 Upon receipt of the ODISCONNECT, the SN stops decrementing MS-1’s account
20 balance.
21
22 aa. The SN sends a CONNRES to the MSC with instructions to set up a call leg to the
23 SN.
24
Parameters Usage Type
25
26 DSTDGTS DestinationDigits. The network address of the R
27 destination.
28
CARDGTS CarrierDigits. Interexchange carrier for call O
29
setup. Include if applicable.
30
31 ROUTDGTS RoutingDigits. Special routing instructions. O
32 Include if applicable.
33
bb. The MSC sets up the call leg to the SN.
34
35 cc. The SN plays an announcement to MS-1 indicating the updated account balance.
36
37 dd. The SN sends an odisconnect to the MSC.
38
39
ee. The MSC releases the call leg to the SN.
40
ff. The MSC releases MS-1.
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-93 Pre-Paid Charging


PN-4287

8.X.34 Call Delivery: Charge Rate Dependent on MS Location 2


3
4
This scenario describes PPC invocation upon Call Delivery with intersystem termination.
5
The rate of charging for the call is dependent on the location of the MS.
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
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 4-94 TIA/EIA-41.3-D Modifications


PN-4287

1
2 Originating System Serving System
3
4 MSC HLR SCP VLR MSC
5
6
7 call origination
8 a
9 LOCREQ [MSCID, BILLID, DGTSDIAL, TRIGTYPE, TRANSCAP, WINCAP]
10 b
11 LRT
locreq [MSCID, MIN, IMSI, TRIGADDRLIST]
12 c
13
ANLYZD [MSCID, BILLID, DGTSDIAL, MSID, TRIGTYPE]
14
d
15
ANZT
16 anlyzd [DMH_SVCID]
e
17
18 LOCREQ [MSCID, BILLID, DGTSDIAL, TRIGTYPE, TRANSCAP, WINCAP]
19 f
20
ROUTREQ [MSCID, BILLID, MSID]
21 g
22
ROUTREQ [MSCID, BILLID, MSID]
23 h
24 LRT RRT RRT
25
routreq [TLDN]
i
26
27 routreq [TLDN]
j
28
TLDNAT
29 locreq [MSCID, MIN, IMSI, TERMLIST, REDIND]
30
k
31 ANLYZD [MSCID, MSID, MDN, BILLID, RoutingInfo, REDIND, TRIGTYPE, TOD, TDO]
32 l
33 ANZT
anlyzd [ ]
34 m
35
call setup
36 n
37
38
MS answer o
39
40 TANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO, SCELLID, LOCID]
41 p
42
cut through
43
q
44
45
46
MS disconnect r
47
48
TDISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]
49
s
50
TDT
51 tdisconnect [DMH_SVCID]
t
52
53 call release
54
u
55
56
Figure 8.X.34 Call Delivery: Charge Rate Dependent on MS Location
57
58
a-o. Same as Section 8.X.22, Steps a-o.
59
60

TIA/EIA-41.3-D Modifications 4-95 Pre-Paid Charging


PN-4287

1
p. The Serving MSC detects the T_Answer trigger and sends a TANSWER to the SCP
2
associated with this trigger.
3
Parameters Usage Type 4
5
MSCID Serving MSC MSCID. R
6

MSID Served MS MSID. R 7


8
MDN Mobile directory number. Include if available. O 9

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


11
TRIGTYPE Indicates the trigger encountered. R 12
13
TOD TimeOfDay. The time of call answer (UTC). R
14
TDO TimeDateOffset. The time offset of local civil R 15
time. 16
17
SCELLID ID of the cell serving the MS. R
18
LOCID Location Area ID. Include if available. O 19
20
Upon receipt of the TANSWER, the SCP begins decrementing the subscriber’s 21
account balance. The charging rate for the call is dependent upon the MS location. 22
23
q. The calling party is connected to the MS.
24
r. The MS ends the call. 25
26
s. The Serving MSC detects the T_Disconnect trigger and sends a TDISCONNECT to 27
the SCP associated with this trigger. 28
29
Parameters Usage Type
30
MSCID Serving MSC MSCID. R 31
32
MSID Served MS MSID. R
33
MDN Mobile directory number. Include if available. O 34
35
BILLID BillingID. Used to relate queries for this call. R
36

TRIGTYPE Indicates the trigger encountered. R 37


38
RELCAUSE Call release cause. R 39

TOD TimeOfDay. The time of call disconnect (UTC). R 40


41
TDO TimeDateOffset. The time offset of local civil R 42
time. 43
44
Upon receipt of the TDISCONNECT, the SCP stops decrementing the subscriber’s
45
account balance.
46

t. The SCP sends a tdisconnect to the Serving MSC. The DMH_SVCID 47

parameter is set to indicate that PPC was invoked. 48


49
u. The Serving MSC releases the call. 50
51
52
53
54
55
56
57
58
59
60

Pre-Paid Charging 4-96 TIA/EIA-41.3-D Modifications


PN-4287

1
2 8.X.35 MS Call Origination with Service Logic Directed Call to Customer
3
Service Center
4
5
This scenario describes PPC invocation upon call origination with service logic directed
6
call to a Customer Service Center.
7
8
Serving System
9
10
11 IP SCP MSC
12
13
14
15
MS Call Origination: Same as Section 8.X.3, Steps a-s
16
17
18
CCDIR [MSCID, MSID, MDN, BILLID, ANNLIST]
19 t
20
low balance warning
21 CCDT u
22
23 ccdir [ ]
v
24
25
26
CCDIR [MSCID, MSID, MDN, BILLID, ANNLIST, ACTCODE, TERMLIST]
27 w
28
29 redirection warning
x
30
CCDT
31 release called party
y
32
33 ccdir [ ]
34
z
35 ODISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO]
36 aa
37 ODT
odisconnect [ ]
38 bb
39
call setup
40 cc
41
42 answer
dd
43
44
45
disconnect
46 ee
47
48 call release
ff
49
50
Figure 8.X.35 MS Call Origination with Service Logic Directed Call to Customer Service
51
Center
52
53
54 a-s. Same as Section 8.X.3, Steps a-s.
55
56 t-v. Same as Section 8.X.7, Steps t-v.
57
58
w. The SCP determines the call shall be redirected to a Customer Service Center (e.g.,
59
a PPC service logic program instance timer expires). The SCP sends a CCDIR to
60

TIA/EIA-41.3-D Modifications 4-97 Pre-Paid Charging


PN-4287

1
the Serving MSC. The ANNLIST parameter is set to indicate that a redirection
2
warning (i.e., tone or announcement) shall be played to the MS. The ACTCODE
3
parameter is set to indicate the call leg to the called party be released and the MS be
4
maintained on the traffic channel. The TERMLIST parameter provides the routing
5
information for the call to the Customer Service Center.
6

x. The Serving MSC plays the redirection warning. The redirection warning is only 7

applied to the calling MS (i.e., the called party does not hear the warning). 8
9
y. The Serving MSC releases the called party. 10
11
z. The Serving MSC sends a ccdir to the SCP. 12
13
aa. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT
14
to the SCP associated with this trigger.
15
Parameters Usage Type 16
17
MSCID Serving MSC MSCID. R
18
MSID Served MS MSID. R 19
20
MDN Mobile directory number. Include if available. O
21

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


23
TRIGTYPE Indicates the trigger encountered. R 24

RELCAUSE Call release cause. R 25


26
TOD TimeOfDay. The time of call disconnect (UTC). R 27
28
TDO TimeDateOffset. The time offset of local civil R
time. 29
30
Upon receipt of the ODISCONNECT, the SCP stops decrementing the subscriber’s 31
account balance. 32
33
bb. The SCP sends an empty odisconnect to the Serving MSC. 34
35
cc. The Serving MSC sets up the call to the Customer Service Center.
36

dd. The call is answered. 37


38
ee. The subscriber disconnects. 39
40
ff. The Serving MSC releases the call. 41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Pre-Paid Charging 4-98 TIA/EIA-41.3-D Modifications


PN-4287

1
2 8.X.36 Call Delivery: Serving MSC is Not WIN Capable
3
4
This scenario describes PPC invocation upon call delivery with intersystem termination.
5
The Serving MSC is not WIN capable.
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

TIA/EIA-41.3-D Modifications 4-99 Pre-Paid Charging


PN-4287

1
Originating System Serving System 2
3
MSC HLR SCP VLR MSC 4
5
6
call origination 7
a 8

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


b 10

LRT 11
locreq [MSCID, MIN, IMSI, TRIGADDRLIST]
c 12
13
ANLYZD [MSCID, BILLID, DGTSDIAL, MSID, TRIGTYPE]
14
d
15
ANZT
anlyzd [DMH_SVCID] 16
e
17
LOCREQ [MSCID, BILLID, DGTSDIAL, TRIGTYPE, TRANSCAP, WINCAP] 18
f 19
20
ROUTREQ [MSCID, BILLID, MSID]
g 21
22
ROUTREQ [MSCID, BILLID, MSID]
h 23

LRT RRT RRT 24


routreq [TLDN] 25
i
26
routreq [TLDN] 27
j
28
TLDNAT
locreq [MSCID, MIN, IMSI, TERMLIST, REDIND] 29
k 30
ANLYZD [MSCID, MSID, MDN, BILLID, RoutingInfo, REDIND, TRIGTYPE, TOD, TDO] 31
l 32
ANZT 33
anlyzd [ ]
m 34
35
call setup
n 36
37
38
MS answer o
39
40
answer
p 41
42
cut through
43
q
44
TANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO]
45
r
46
47
48
MS disconnect s 49
TDISCONNECT [MSCID, MSID, MDN, BILLID, TRIGTYPE, RELCAUSE, TOD, TDO] 50
t 51
TDT 52
tdisconnect [DMH_SVCID]
u 53
54
call release 55
v
56

Figure 8.X.36 Call Delivery: Serving MSC is Not WIN Capable 57


58
59
60

Pre-Paid Charging 4-100 TIA/EIA-41.3-D Modifications


PN-4287

1
a-b. Same as Section 8.X.22, Steps a-b.
2
3 c. The HLR sends a locreq to the Originating MSC with the TRIGADDRLIST
4 parameter set to indicate t h e Initial_Termination, Location,
5 Called_Routing_Address_Available, T_Answer, and T_Disconnect triggers shall be
6 armed. The T_Answer and T_Disconnect triggers are armed for call delivery
7 because the Serving MSC is not WIN capable.
8
9 Parameters Usage Type
10
MSCID Serving MSC MSCID. R
11
12 MIN Called MS MIN. R
13
IMSI Called MS IMSI. Include if available. O
14
15 TRIGADDRLIST WIN Triggers to arm for this call leg. R
16
17
d-o. Same as Section 8.X.22, Steps d-o.
18
p. The Serving MSC provides an answer indication.
19
20 q. The calling party is connected to the MS.
21
22 r. The Originating MSC detects the T_Answer trigger and sends a TANSWER to the
23 SCP associated with this trigger.
24
Parameters Usage Type
25
26 MSCID Originating MSC MSCID. R
27
MSID Served MS MSID. R
28
29 MDN Mobile directory number. Include if available. O
30
31
BILLID BillingID. Used to relate queries for this call. R
32 TRIGTYPE Indicates the trigger encountered. R
33
34 TOD TimeOfDay. The time of call answer (UTC). R
35
TDO TimeDateOffset. The time offset of local civil R
36 time.
37
38 Note: the TOD and TDO values are Originating MSC times and the PPC service
39 logic program may need to adjust these value to reflect Serving MSC local time.
40
41
s. The MS ends the call.
42
t. The Originating MSC detects the T_Disconnect trigger and sends a TDISCONNECT
43
to the SCP associated with this trigger.
44
45 Parameters Usage Type
46
MSCID Originating MSC MSCID. R
47
48 MSID Served MS MSID. R
49
50
MDN Mobile directory number. Include if available. O
51 BILLID BillingID. Used to relate queries for this call. R
52
53 TRIGTYPE Indicates the trigger encountered. R
54
RELCAUSE Call release cause. R
55
56 TOD TimeOfDay. The time of call disconnect (UTC). R
57
TDO TimeDateOffset. The time offset of local civil R
58
time.
59
60

TIA/EIA-41.3-D Modifications 4-101 Pre-Paid Charging


PN-4287

1
Note: the TOD and TDO values are Originating MSC times and the PPC service
2
logic program may need to adjust these value to reflect Serving MSC local time.
3

u. The SCP sends a tdisconnect to the Originating MSC. The DMH_SVCID 4

parameter is set to indicate that PPC was invoked. 5


6
v. The Serving MSC releases the call. 7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
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 4-102 TIA/EIA-41.3-D Modifications


PN-4287

1
2 8.X.37 Three-Way Call to 9-1-1
3
4
This scenario describes a PPC subscriber invoking a Three-Way call to 9-1-1. The PPC
5
account is depleted during the Three-Way call and the MSC does not release the call
6
because of the locally allowed 9-1-1 call leg.
7
8