IS826 NS0018Re

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
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
32
33
34
35
36
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
2
CHAPTER 2
3
FEATURE DESCRIPTION
4
5
6
7 CONTENTS
8
9
10
LIST OF TABLES ........................................................................................................................................... ii
11
12
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
32
33
34
35
36
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

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

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

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

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

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

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

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

PN-4287
1
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
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
32
33
34
35
36
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

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

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

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

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

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

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

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
32
33
34
35
36
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
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

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
24
26
27
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
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
DSTDGTS DestinationDigits. The network address of the R 51
destination. 52
53
CARDGTS CarrierDigits. Interexchange carrier for call O 54
55
ROUTDGTS RoutingDigits. Special routing instructions. O 56

58
f. The MSC sets up the call leg to the SN. 59
60

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
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
21
22 TOD TimeOfDay. The time of call answer (UTC). R
23
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
37
39
40
42
43
44 RELCAUSE Call release cause. R
45
46 TOD TimeOfDay. The time of call disconnect (UTC). R
47
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

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

3
4
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

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
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
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
45 r
46
answer
47 s
48
49 disconnect
50 t
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

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
7
8
10
11
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

26
TRANSCAP Serving MSC’s transaction capability. R 28

29
31
32
34
35
37
RoutingInfo: Call routing information:
38
destination. 40
41
setup. Include if applicable. 42
43
Include if applicable.
45

47
TDO TimeDateOffset. The time offset of local civil R 49
time. 50
51
52
53
54
55
56
57
58
59
60

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
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
23
DSTDGTS DestinationDigits. The network address of the R
24 destination.
25
26 CARDGTS CarrierDigits. Interexchange carrier for call O
27
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

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
5
6

8

11
13
TOD TimeOfDay. The time of call answer (UTC). R
14
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
27
29
30
32
33
35
RELCAUSE Call release cause. R
36
TOD TimeOfDay. The time of call disconnect (UTC). R 37

38
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

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
17
b
18
ORT
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
31 h
32
answer
33 i
34
35 disconnect
36 j
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

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
5
6

8

11
13
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
23
24
26
27
29
30

32

35
destination. 38
39
40
41
44
45
47
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

PN-4287
1
2 8.X.5 MS Call Origination: Called Party Disconnect
3
4
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

PN-4287
1
u. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT
2
3
5
6

8

11
13
14
16
17
19
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
35
36
destination.
37
40
ROUTDGTS RoutingDigits. Special routing instructions. O
41
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
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

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

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

3
4
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

PN-4287
1
o. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT
2
3
5
6
7 TRANSCAP Serving MSC’s transaction capability. R
8
9
WINCAP Serving MSC’s WIN capability. R
11
12 MDN Mobile directory number. Include if available. O
13
14
15 TRIGTYPE Indicates the trigger encountered. R
16
17
19
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
29
30 DSTDGTS DestinationDigits. The network address of the R
31 destination.
32
CARDGTS CarrierDigits. Interexchange carrier for call O
33
34
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

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
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
42
MSCID SCP MSCID. Include to identify the requesting R
43
network entity.
44
46
47

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

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

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
14
15
16

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

PN-4287
1
aa. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT
2
3
5
6
8
9
11
13
14
16
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

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

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

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

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
11
12
14
15
17
18
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
32
34
35
36 WINCAP Serving MSC’s WIN capability. R
37
39
40
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
50 [ROUTDGTS] RoutingDigits. Special routing instructions. O
52
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

PN-4287
1
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
16
17
19
20
22
23
with the call (e.g., Three-Way Calling).
24
TOD TimeOfDay. The time of call answer (UTC). R 25
26
27
time.
28
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
44
45
47
48
50
51
53
54

56
time.
58
59
60

PN-4287
1
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
13
15
16
18
19
21
23
TOD TimeOfDay. The time of call disconnect (UTC). R
24
25 TDO TimeDateOffset. The time offset of local civil R
26 time.
27
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

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
kk 22
SZRT ODT 23
seizeres [TLDN] 24
ll
25
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

PN-4287
1
jj. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT
2
3
5
6
8
9
WINCAP Serving MSC’s WIN capability. R
11
13
14
16
17
19
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
35
36
destination.
37
39 setup. Include if applicable.
40
41
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
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

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

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
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
43
44
46
47
49
50
52
53
55 time.
56
58 account balance for the call to the original called party.
59
60

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
8
10
11

13

16
RELCAUSE Call release cause. R 17
18
19
time. 21
22
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

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

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
5
6

8

11
13
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
27
28
30
31
33
34

36

destination. 39
40
41
42
45
46
FEATIND FeatureIndicator. Indicates the feature invoked R 47
with the call (e.g., Three-Way Calling). 48
49
50
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

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

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
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
jj
27
ODT
odisconnect [ ] 28
kk 29
END 30
ll 31
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
48
MSCID SCP MSCID. Include to identity the requesting R 49

network entity. 50
51
52

54
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

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
14
16
17
19
20
22
23
25
26
time.
27
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
36
38
39
41
42
44
46
47
49
50
time.
51
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

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
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
mm 34
35
ODT
odisconnect [ ] 36
nn
37
call-2 release 38
oo
39
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

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.
11
13
14
16
17
19
20
22
23
time.
24
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
35
36
38
39
41
43
44
46
47
time.
48
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

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
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
i 34
SZRT ANZT 35
seizeres [TLDN]
j 36
37
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

PN-4287
1
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
7
8
10
11
13
14
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
24
25
27
29
30
32
33
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
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
47
48
49 MSCID Requesting MSC MSCID. R
50
51
52 TOD TimeOfDay. The time of Service Invocation R
53 (UTC).
54
55
time.
56
57 f. SCP-1 sends a servreq to SCP-2.
58
59
60

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
10
11
13
14
16
17
19
20
destination. 22
23
24
25

29
31
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
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

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
5
6
destination.
7
10
11
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
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

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
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
36
37

39

42
44
45
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

PN-4287
1
y. The Serving MSC detects the O_Disconnect trigger and sends an ODISCONNECT
2
3
5
6
8
9
11
13
14
15 TOD TimeOfDay. The time of call Disconnection R
16 (UTC).
17
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

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
9
10
SCP-1 SCP-2 MSC 11
12
13
MS origination
14
a
15
b 17
ORT
c 19

d 21
22
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
33
ORREQ to SCP-1, the SCP associated with this trigger. 35
36

39
41
42
44
45
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

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
5
6
8
9
11
12 DGTSDIAL Digits entered by served MS. R
13
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
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
26
27
28 MSCID Requesting MSC MSCID. R
29
31
TOD TimeOfDay. The time of Service Invocation R
32 (UTC).
33
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

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
8
9
SCP-1 SCP-2 MSC 10
11
12
MS origination
13
a
14
b 16
ORT
c 18
ORREQ [MSCID, TRANSCAP, MSID, MDN, BILLID, DGTSDIAL, TRIGTYPE] 19

d 20
21
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

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
6
7
9
10
12
14
15
17
18 destination.
19
20
21
24
25
26 TOD TimeOfDay. The current time (UTC). R
27
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

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

PN-4287
1
2 8.X.20 Call Origination: Charge Rate Dependent on MS Location
3
4
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
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
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
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

PN-4287
1
d. The Serving MSC analyzes the dialed digits and prepares to route the call. The
2
3
4
6
7

9

12
14
15
17
destination. 18
19
[CARDGTS] CarrierDigits. Interexchange carrier for call O 20
21
24
25
27
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
37
38
destination.
39
42
43
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

PN-4287
1
l. The Serving MSC detects the O_Answer trigger and sends an OANSWER to the SN
2
3
5
6
8
9
11
13
14
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
31
33
34
36
37
39
40
42
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

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

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
7
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
18
19 MSCID Originating MSC MSCID. R
20
21
22 DGTSDIAL The called directory number. R
23
24 MSID Called MS MSID. R
25
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
37
38
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

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
6
MSCID Originating MSC MSCID. R
7

9

12
[DSTDGTS] DestinationDigits. The network address of the O 14
destination. 15
16
17
18
21
REDIND DMH_RedirectionIndicator. Reason for R
22
extending the incoming call.
23
25
26
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

38
40
41
43
44
46
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

PN-4287
1
n. The Originating MSC detects the T_Disconnect trigger and sends a TDISCONNECT
2
3
5
6
8
9
11
13
14
16
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

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
b 14
LRT 15
c
17
ANLYZD [MSCID, BILLID, DGTSDIAL, MSID, TRIGTYPE]
18
d
19
ANZT
e 21
f 23
24
ROUTREQ [MSCID, BILLID, MSID]
g 25
26
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

PN-4287
1
2
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
15
17
MIN Called MS MIN. R
18
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
27
28
30
31
DGTSDIAL The called directory number. R
33
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
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

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
5
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
19
20

22

25
destination. 28
29
30
31
34
35
36
38
39
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

PN-4287
1
p. The Serving MSC detects the T_Answer trigger and sends a TANSWER to the SCP
2
3
5
6
8
9
11
13
14
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
24
26
27
29
31
32
34
35
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

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
b 15
LRT 16
c
18
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
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

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
24 f
25 LRT
26 g
27
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
42 n
43
call forward setup
44 o
45
answer
46 p
47
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

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
9
10
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

21
23
24
26
27
destination. 29
30
31
32
35
37
39
40
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

PN-4287
1
q. The Originating MSC detects the O_Answer trigger and sends an OANSWER to the
2
3
5
6
8
9
11
13
14
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

PN-4287
1
Originating System 2
3
MSC HLR SCP 4
5
6
7
8
disconnect 9
s
10
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

27

30
32
33
35
36
38
39
time.
40
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

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
15 b
16 LRT
17
c
18
d
20
ANZT
22
e
24 f
25 LRT
26 g
27
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
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

PN-4287
1
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
7
8

10
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
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
31
33
34
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

PN-4287
1
n. The Originating MSC analyzes the dialed digits and prepares to route the call. The
2
3
4
6
7
9
10
12
14
15 destination.
16
17 [CARDGTS] CarrierDigits. Interexchange carrier for call O
18
21
22
23
25
26
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
41
43
44
46
47
49
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

PN-4287
1
Originating System CF PPC 2
3
MSC HLR SCP SCP 4
5
6
7
8
disconnect 9
t
10
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

27

30
32
33
35
36
38
39
time.
40
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

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
7
8
9
MSC HLR SCP VLR MSC
10
11 call origination
12 a
14 b
15 LRT
16
c
17
18
d
19
ANZT
21
e
23 f
24
25 g
26
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
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

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
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
16
18
19
21
22
REDIND DMH_RedirectionIndicator. Reason for extending R 23

the incoming call. 24
25
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

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
16
b
LRT
17 locreq [MSCID, MIN, IMSI, TRIGADDRLIST]
18 c
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
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

PN-4287
1
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
6
7

9
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
v 36
ANZT
w 38
39
call forward setup
x 40
41
answer
y 42
43
44
z
45
cut through 46
aa
47
48
disconnect 49
bb 50

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

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

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
b 14
LRT 15
c
17
d
19
ANZT
e 21
f 23
LRT 24
locreq [MSCID, MIN, IMSI, TERMLIST, REDIND, TRIGADDRLIST]
g 25
26
h 27
28
ANZT
i
30
call forward setup 31
j
32
answer 33
k 34
35
l 36
37
cut-through
m 38
39
disconnect 40
n 41

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

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
7
8
10
11
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

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
7
8
MSC HLR SCP SCP 9
10
11
call origination
a 12
b 14
LRT 15
c
17
d
19
ANZT
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
29
i
30
ANZT
j
32

k 34
35
answer
l 36
37
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

PN-4287
1
2
parameter set to indicate the Initial_Termination, Advanced_Termination, Location
3
and Called_Routing_Address_Available triggers shall be armed.
4
6
7
9
10
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
26
27
30
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

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
8
9
MSC HLR SCP SCP 10
11
12
call origination
a 13
14
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
28
h
29
ANZT
anlyzd [ ] 30
i
31

j 33
34
answer
k 35
36
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
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

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
10
12
13
15
16
19
20
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

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
8
9
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
18
s
19
LRT
t
21
u 23
ANZT 24
anlyzd [DMH_SVCID]
v 25
w 27
28
ROUTREQ [MSCID, BILLID, MSID] 29
x
30
y
32
LRT RRT RRT
routreq [TLDN] 33
z 34
routreq [TLDN] 35
aa 36
TLDNAT 37
bb 38
39
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

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
14
16
17
19
20
22
23
with the call (e.g., Call Waiting).
24
26
27
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

PN-4287
1
3
5
6
7
8
call-2 disconnect 9
jj
10
kk 12
TDT
tdisconnect [DMH_SVCID] 13
ll 14
call-1 cut through 15

mm 16
17
18
19
MS disconnect nn
20

oo 22
TDT 23
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
36
38
39

41

44
46
47
time. 49
50
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

PN-4287
1
oo. The Serving MSC detects the T_Disconnect trigger and sends a TDISCONNECT to
2
3
5
6
8
9
11
13
14
16
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

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
14
15
16
CCDIR [MSCID, MSID, MDN, BILLID] 17

t 18
CCDT 19
ccdir [ ]
u 20
21
MS disconnect v 22
23
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
35
t. The SCP sends a CCDIR to the Serving MSC. No action is requested. 36
37
38
MSCID SCP MSCID. Include to identity the requesting R 39
network entity. 40
41
42
44
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

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
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
41 m
42
BILLID2 LOCREQ [MSCID, BILLID, DGTSDIAL, TRIGTYPE, TRANSCAP, WINCAP]
43 n
44 LRT
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

PN-4287
1
a. MS-1 originates a call with dialed digits. The MS origination is received by the
2
Serving MSC.
3
ORREQ to the SN associated with this trigger. 5

6
8
9
11
12
14
15
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
to the SN associated with this trigger. 26

27
29
30
32
33
35
36

38
time.
40

42
43
destination.
44
[CARDGTS] CarrierDigits. Interexchange carrier for call O 45
47
[ROUTDGTS] RoutingDigits. Special routing instructions. O
49
51
52
53
54
55
56
57
58
59
60

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
5
6
destination.
7
10
11
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
35
36
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
48
50
51
53
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

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
8
9
11
12
14
REDIND DMH_RedirectionIndicator. Reason for O
15
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
22
23
25
26
28
29
[DSTDGTS] DestinationDigits. The network address of the O 30
destination. 31
32
34
36

39
40

42
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

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
22 z
23 ODT
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
44
45
47
48
50
52
53
55 time.
56
u. MS-1 is connected to MS-2.
57
58
59
60

PN-4287
1
v. The Serving MSC detects the O_Answer trigger for MS-1 and sends an OANSWER
2
3
5
6

8

11
13
time. 14
15
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
25

27

30
32
33
35
36
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

PN-4287
1
z. The MSC detects the O_Disconnect trigger for MS-1 and sends an ODISCONNECT
2
3
5
6
8
9
11
13
14 time.
15
17
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
25
26 DSTDGTS DestinationDigits. The network address of the R
27 destination.
28
CARDGTS CarrierDigits. Interexchange carrier for call O
29
30
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

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

PN-4287
1
3
4 MSC HLR SCP VLR MSC
5
6
7 call origination
8 a
10 b
11 LRT
12 c
13
14
d
15
ANZT
e
17
19 f
20
21 g
22
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
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

PN-4287
1
p. The Serving MSC detects the T_Answer trigger and sends a TANSWER to the SCP
2
3
5
6

8

11
13
14
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
30
32
33
35
36

38

41
time. 43
44
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

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

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
15
17
18
20
21

23

26
28
time. 29
30
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

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

PN-4287
1
3
5
6
call origination 7
a 8

b 10
LRT 11
c 12
13
14
d
15
ANZT
e
17
f 19
20
g 21
22
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
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
t 51
TDT 52
u 53
54
call release 55
v
56
Figure 8.X.36 Call Delivery: Serving MSC is Not WIN Capable 57

58
59
60

PN-4287
1
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
10
11
13
14
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
25
27
28
30
31
33
35
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
44
46
47
49
50
52
54
55
57
58
time.
59
60

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

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
Serving System
9
10
11
SN MSC MS
12
13
digits + SEND
14
a
15
17
b
ORT
19 c
20 ANLYZD [MSCID, TRANSCAP, WINCAP, MSID, MDN, BILLID,
21 DGTSDIAL, RoutingInfo, TRIGTYPE, TOD, TDO]
d
22
ANZT
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-1 setup
35
j
36 call-1 answer
37 k
38
39 l
40
answer
41 m
42
43 Figure 8.X.37-1 Three-Way Call to 9-1-1 (1 of 2)
44
45
46 a-m. Same as Section 8.X.2, Steps a-m.
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
1
Serving System 2
3
SN MSC MS 4
5
6
7
8
9-1-1 + SEND
9
n
10
11
call-1 hold o 12
13
9-1-1 call setup 14
p
15
9-1-1 call answer 16
q
17
answer 18
r 19
SEND 20
s 21
22
call-1 reconnect t 23
24
25
26
CCDIR [MSCID, MSID, MDN, BILLID, ANNLIST, ACTCODE] 27
u
28
CCDT
ccdir [CALLSTATUS] 29
v 30
31
32
END
33
w
34
9-1-1 call release 35
x 36

y 38
ODT 39
odisconnect [ ]
z 40
41
call-1 release
aa 42
43
Figure 8.X.37-2 Three-Way Call to 9-1-1 (2 of 2) 44

45
46
n. During the two-way conversation state, the subscriber enters the digits 9-1-1 and 47
presses the SEND key. 48
49
o. The original called party is put on hold. 50
51
p. The Serving MSC detects the locally allowed dialed number and sets up the 52
Emergency Services call. 53
54
q. The 9-1-1 call is answered.
55
r. The call is cut through and connected. 56

57
s. The subscriber presses the SEND key. 58
59
60

PN-4287
1
t. The held party is connected to the call (3-Way State).
2
3 u. The SN determines the call shall be disconnected (e.g., a PPC service logic program
4 instance timer expires). The SN sends a CCDIR to the Serving MSC. The
5 ANNLIST parameter indicates that the disconnect warning (i.e., tone or
6 announcement) shall be played to the MS. The ACTCODE parameter indicates the
7 call shall be disconnected.
8
9 v. Local Serving MSC procedures do not permit the call or any call leg related to the
10 locally allowed call to be released. The Serving MSC sends a ccdir to the SN
11 with the CALLSTATUS parameter set to indicate Locally Allowed Call - No Action.
12
13
w. The subscriber presses the END key.
14
15
x. The Serving MSC releases the 9-1-1 call.
16
y. The Serving MSC detects the O_Disconnect trigger for the call to the original called
17
party. The Serving MSC sends an ODISCONNECT to the SN associated with this
18
trigger.
19
21
22
24
25
27
28
30
32
33 time.
34
35 z. The SN sends an odisconnect to the Serving MSC.
36
37
aa. The Serving MSC releases the call to the original called party.
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
8.X.38 PPC Account Recovery After MSC Failure 2

3
4
This scenario describes PPC account recovery after a failure at an MSC. During a major
5
MSC failure, all calls are dropped. When the MSC recovers from the failure, it can
6
inform all SCPs that were controlling PPC calls of the time the failure occurred. This
7
information allows SCPs to update subscriber accounts based on the time a call was
8
ended because of MSC failure.
9
After a failure, the MSC can recover the addresses of SCPs controlling PPC calls at the 10
MSC, specifically SCPs associated with T_Disconnect and O_Disconnect triggers. 11
12
The amount of data stored by the MSC is a configurable size sliding window (e.g., 30 13
minutes). 14
15
16
MSC SCP 17
18
19
20
MSC Recovery a
21
22
BULKDISCONN [MSCID, MSCIN, TOD, TDO]
b 23
BDISCT 24
bulkdisconn [ ]
c 25
26
Figure 8.X.38 PPC Account Recovery After MSC Failure 27

28
29
a. The MSC recovers from a failure where all calls have been dropped. 30
31
b. The MSC sends a BULKDISCONN to the SCP indicating all calls have been 32
dropped. The TOD and TDO parameters indicate the time of failure to inform SCPs 33
associated with T_Disconnect and O_Disconnect triggers, that calls on this MSC 34
have been disconnected. The time of MSC failure is included in the message. 35
36
c. The SCP returns an empty bulkdisconn. The SCP updates PPC subscriber
37
accounts for calls that were active at the MSC at the time the failure occurred.
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
1
2 8.X.39 SCF Failure Recovery
3
4
This scenario describes intersystem operations needed to recover PPC call data after an
5
SCF network entity failure, SCF failure or network failure. During one of these failures,
6
PPC subscriber call data is not received from the MSC. The SCF may not receive
7
information about calls that ended during the failure period. To be able to adjust the
8
subscriber’s account, it is necessary for the SCF to obtain information on the calls that
9
ended during the failure.
10
11 The MSC may store data for calls for which it did not receive a response to a query for a
12 calling party or called party disconnect.
13
14 When the SCF recovers from a failure, it can request data from the MSC about the status
15 of calls that were being served at that MSC. The MSC returns a list of data for calls that
16 ended during the SCF failure.
17
After a failure, the SCF can recover data (stored at the SCF network entity) about calls
18
that were active at the time the failure occurred. This data includes:
19
20 • MSC where the call was active,
21
22 • call reference (Billing ID or subscriber information identifying the call),
23
24
• start time of 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

PN-4287
1
3
5
6
call origination
7
a
8
9
b
10
LRT
locreq [MSCID, MIN, IMSI, TRIGADDRLIST, CNID] 11
c 12
d 14
ANZT 15
anlyzd [DMH_SVCID]
e 16
17
f 18
19
g
21
h
23
LRT RRT RRT
routreq [TLDN] 24
i 25
26
routreq [TLDN]
j 27
TLDNAT 28
k 29
30
31
l
32
ANZT
anlyzd [ ] 33
m
34
call setup 35
n 36
37
MS answer o 38
39
TANSWER [MSCID, MSID, MDN, BILLID, TRIGTYPE, TOD, TDO] 40
p
41
cut through 42
q 43
44
Figure 8.X.39-1 SCF Failure Recovery (1 of 2) 45
46
47
48
49
b. The Originating MSC detects the Mobile_Termination trigger and sends a LOCREQ 50
to the HLR associated with the MS; this association is made through the dialed MS 51
address digits (which may not be the MSID). The TRANSCAP parameter is set to 52
indicate the MSC can process the TRIGADDRLIST parameter. The WINCAP 53
parameter indicates the triggers supported by the MSC. The TRIGTYPE parameter 54
is set to indicate the Mobile_Termination trigger was encountered. 55

56
c. The HLR sends the locreq to the Originating MSC with the TRIGADDRLIST 57
parameter set to indicate the Initial_Termination and Location and 58
Called_Routing_Address_Available triggers shall be armed. The CNID parameter 59
60

PN-4287
1
is set to the identifier associated with the SCF recovery operation in the event of an
2
SCF failure, SCF network entity failure or a network failure.
3
4 d. The Originating MSC detects the Initial_Termination trigger and sends an ANLYZD
5 to the SCP indicated in the TRIGADDRLIST parameter. The TRIGTYPE
6 parameter is set to indicate the Initial_Termination trigger was detected.
7
9
10
12
13
15
16
17 e. The SCP determines the called subscriber has PPC active and that the account
18 balance is above the threshold level. The SCP sends an anlyzd to the Originating
19 MSC. The DMH_SVCID parameter is set to indicate that PPC was invoked.
20
23
24
g. The HLR determines call processing shall continue and sends a ROUTREQ to the
25
VLR.
26
h. The VLR forwards the ROUTREQ to the Serving MSC.
27
28 i. The Serving MSC allocates a TLDN and returns it to the VLR in the routreq.
29
30 j. The VLR forwards the routreq to the HLR.
31
32
k. The HLR sends the locreq to the Originating MSC with instructions to set up the
33
call to the subscriber.
35
37
38
40
41
42
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
1
l. The Originating MSC prepares to route the call to the Serving MSC and detects the
2
Called_Routing_Address_Available trigger. The Originating MSC sends an
3
ANLYZD to the SCP associated with this trigger.
4
6
7

9

12
destination. 15
16
17
18
21
22
23
25
26
time. 28
29
m. The SCP sends an anlyzd to the MSC. 30
31
n. The Originating MSC sets up the call to the subscriber.
32
o. The MS answers the call. 33
34
p. The Serving MSC detects the T_Answer trigger and sends a TANSWER to the SCP 35
associated with the trigger. 36
37
38
40
41
43
44

46
time. 49
50
q. The calling party is connected to the MS. 51
52
53
54
55
56
57
58
59
60

PN-4287
1
3
4 MSC HLR SCP VLR MSC
5
6
7
8
SCP Failure r
9
10
MS disconnect s
11
12
13
t
14
TDT
15
16 timer expires u
17
call release
18 v
19
20
21 SCP Recovery w
22
23 UNRELCALLDATA [MSCID, CNID]
24
x
URCDT
25 CRREPORT [CRIDLIST]
26 y
27 CRRT
crreport [ ]
28 z
29 URCDT
unrelcalldata [ ]
30 aa
31
32 Figure 8.X.39-2 SCF Failure Recovery (2 of 2)
33
34
35 r. The SCP fails.
36
37
s. The MS ends the call.
38
t. The Serving MSC detects the T_Disconnect trigger and sends a TDISCONNECT to
39
40
42
43
45
46
48
50
51
53
54
time.
55
56 The SCP does not detect the message.
57
58 u. The Serving MSC does not receive a tdisconnect and an MSC timer expires.
59 The Serving MSC records data for the call with the MS’s CNID value.
60

PN-4287
1
v. The Serving MSC releases the call.
2
w. The SCP recovers from the failure. The SCF recovers data about MSCs handling 3
PPC calls for subscribers served by the SCF. The SCF also recovers data related to 4
PPC calls that started before the failure occurred. 5

6
x. The SCF sends an UNRELCALLDATA to the Serving MSC. The SCF’s CNID 7
parameter value is used to correlate the request to call data pertaining to recovery of 8
the SCF failure. 9
10
11
MSCID MSCID of the SCP. R 12
13
CNID ControlNetworkID for call data selection. R
14
15
y. The MSC compiles a list of stored call data that matches the received CNID value
16
and for which no response was received to a TDISCONNECT or ODISCONNECT
17
message. The MSC includes the time each of the calls ended. The MSC sends the
18
requested information to the SCF in the CRREPORT.
19
21
CRIDLIST CallRecoveryIDList. List of calls ended and not R
22
acknowledged at the MSC.
23
z. The SCF responds with a crreport. 24

25
The Serving MSC may delete the call data received by the SCF. If the scan is 26
incomplete, the MSC sends more call data. Steps y-z are repeated until all the call 27
data associated with the SCF is transmitted. 28
29
aa. The Serving MSC confirms that all the call data associated with the MSC has been 30
sent. The MSC sends an empty unrelcalldata to the SCF. 31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
1
2 8.X.40 Failure During SCF Failure Recovery
3
4
This scenario describes intersystem operations needed to recover PPC call data after an
5
SCP failure, SCF failure or network failure. During a failure, PPC subscriber call data is
6
not received from the MSC. The SCF may not receive information about calls that ended
7
during the failure period. To be able to adjust the subscriber’s account, it is necessary for
8
the SCF to obtain information on the calls that ended during the failure.
9
10
11
MSC SCP
12
13
14
15 SCP Recovery a
16
UNRELCALLDATA [MSCID, CNID]
17 b
18 URCDT
CRREPORT [CRIDLIST]
19 c
20
21
CRRT SCP Failure d
22
23
timer expires e
24
25
26
Figure 8.X.40 Failure During SCF Failure Recovery
27
28
29 a. The SCP recovers from a failure. The SCF recovers data about MSCs handling
30 PPC calls for subscribers served by the SCF. The SCF also recovers data related to
31 PPC calls that started before the failure occurred.
32
33 b. The SCF sends an UNRELCALLDATA to the Serving MSC. The SCF’s CNID
34 parameter value is used to correlate the request to call data pertaining to recovery of
35 the SCF failure.
36
37
38 MSCID MSCID of the SCP. R
39
40
CNID ControlNetworkID for call data selection. R
41
c. The MSC compiles a list of stored call data that matches the received CNID value
42
and for which no response was received to a TDISCONNECT or ODISCONNECT
43
message. The MSC includes the time each of the calls ended. The MSC sends the
44
requested information to the SCF in the CRREPORT.
45
47
CRIDLIST CallRecoveryIDList. List of calls ended and not R
48
acknowledged at the MSC.
49
50 d. Another failure occurs and the SCF does not respond to the MSC.
51
52 e. The MSC timer expires. The MSC executes local recovery procedures.
53
54
55
56
57
58
59
60

PN-4287
1
2
Annex Y (informative): PPC – Recovery From 3

4
Temporary Node Failures 5
6
(New Annex for TIA/EIA-41.3-D) 7
8
This annex is informative and is not considered part of this Standard. 9
10
This annex describes the actions the MSC and PPC service logic program (SLP) should 11
take to recover from temporary failures in order to provide reliable real-time charging for 12
PPC. 13
14
15
Y.1 Introduction 16
17
18
This annex describes the recommended actions and recovery actions that an MSC and 19
PPC SLP should take to recover from the following temporary failure types: 20
21
• a failure in the network between the MSC and the SCF network entity,
22
• an MSC failure, 23
24
• an SCF network entity failure. 25
26
When an MSC or SCF network entity experience a complete failure, the specific recovery 27
actions should be as described in the PPC information flows (see 8.X.38, 8.X.39, 8.X.40). 28
This annex describes the recommended high level actions that the PPC service logic 29
needs to be able to handle for network communication failures, remote node failures and 30
partial node failures. This annex is not intended to dictate the specific implementation 31
details of how these are to be performed (i.e., the internal PPC service logic algorithms). 32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Annex Y 4-114 TIA/EIA-41.3-D Modifications

PN-4287
1
2
Y.2 Underlying Principles
3
4
The underlying principles for recovery actions for temporary failures are:
5
1. Because PPC is a real-time charging service, the PPC service logic program
6
(SLP) must take actions to ensure charging reliability upon recovery from
7
failures rather than relying solely on post processing to sort out the charging.
8
9 2. The recovery measures described in this annex are intended to minimize the
10 impacts due to runaway calls (ongoing calls for which the PPC SLP is not
11 executing) or runaway charging (calls which have ended but for which the PPC
12 SLP has not received disconnect information).
13
14 3. Failure recovery in the nodes should be made as transparent to the end user as
15 possible. It is particularly important for the PPC SLP to provide the low balance
16 warning and zero balance notification to the subscriber upon recovery if these
17 thresholds have been reached during the failure. If both thresholds have been
18 reached during a failure, the SLP should provide the notifications in the normal
19 order for PPC calls, upon recovery.
20
21
4. PPC calls for which the a n l y z d has been received (for either the
22
Calling_Routing_Address_Available or Called_Routing_Address_Available
23
trigger) should continue to be processed normally by the MSC.
24
5. PPC calls for which the anlyzd has not been received (for either the
25
Calling_Routing_Address_Available or Called_Routing_Address_Available
26
trigger) should be released by the MSC.
27
28 6. Total network failures or prolonged partial network failures are not considered
29 in this annex.
30
31 7. This annex proposes the use of a sanity check procedure and the use of the
32 CallControlDirective operation by the PPC SLP as a heartbeat check of call
33 status at reasonable time intervals. This mechanism can be used to address
34 runaway calls, runaway charging, and to provide a limited retry mechanism for
35 sequencing notifications when the threshold has been reached during the
36 temporary failure. If used, the sanity check time interval should be configurable
37 and chosen to provide a suitable time interval for status checking and to avoid
38 overloading the network with heartbeat messages.
39
40
41 Y.3 PPC Failure Recovery Actions
42
43 This section describes the recommended recovery actions that the MSC or SCF network
44 entity should take when the node does not receive a message that would be reasonably
45 expected for the PPC call.
46
47
48
49
Y.3.1 Temporary Network Failure
50
51
For cases of temporary network failures, such as a signaling link outage, temporary
52
congestion in the SS7 network, poor response time from the receiving node or remote
53
node disturbances, it is possible that the local node will not receive an expected INVOKE
54
or RETURN RESULT operation for the PPC service. Since the failure has not occurred
55
at the local node, node recovery procedures are not normally initiated at the local node.
56
57 This section describes the actions that the local node (MSC or SCF network entity)
58 should take if a critical message is not received due to a temporary network failure. The
59 MSC should continue call processing based on available information. This may include
60
TIA/EIA-41.3-D Modifications 4-115 Annex Y

PN-4287
1
disallowing the call if no response is received for an ORREQ or ANLYZD, or storing call
2
data if no response is received for an ODISCONNECT or TDISCONNECT. It could also
3
include error handling for the MSC. The PPC SLP should attempt to recover missing
4
data from the MSC.
5
6
7
Y.3.1.1 MSC Failure Recovery Actions for Temporary Network Failures 8
9
For a temporary failure in the network, in a remote node, or even a partial failure at the 10
MSC, the MSC shall maintain PPC calls that are already in a talk state. Calls which are 11
not in a talk state cannot be maintained if it is not possible to communicate with the SCF 12
network entity. An appropriate notification should be provided to the calling party for 13
unsuccessful call attempts. 14
15
When the Origination Request Timer expires at the MSC, the MSC shall do the 16
following: 17
18
1. Execute "Local Recovery Procedures" task (TIA/EIA-41.6-D, Section 3.5.1). 19
20
2. Provide an unsuccessful indication to the PPC subscriber.
21
22
When the Analyzed Information Timer expires at the MSC, the MSC shall do the 23
following: 24
25
27
2. Provide an unsuccessful indication to the calling party.
28
29
When the ODisconnect or TDisconnect Timer expires at the MSC, the MSC shall do the 30
following: 31
32
34
2. If a ControlNetworkID has been received for the subscriber, the MSC shall log
35
relevant data (e.g., BillingID of the call, the time the call ended) for the call,
36
together with the received ControlNetworkID.
37
38
39
Y.3.1.2 PPC SLP Failure Recovery Actions for Temporary Network Failures
40
41
The PPC SLP should continue to provide PPC service for active calls during temporary
42
failures in the network, in a remote node, or even for partial failures at the SCF node
43
itself. The PPC SLP should also take reasonable measures to provide the normal
44
notifications to the PPC subscriber for low balance and “zero” balance, and in the correct
45
order after the network has recovered from a temporary failure.
46
47
A generic sanity check procedure is proposed to deal with various temporary failure 48
scenarios and to provide some measure of protection against runaway call and runaway 49
charging scenarios, rather than to introduce a number of special purpose timers to address 50
the failure scenarios separately. This sanity check procedure would be part of the PPC 51
SLP and would be performed at a configurable time interval. This time interval should be 52
defined to be longer than the average wireless call (e.g., set at twice the length of the 53
average wireless call). The interval for the sanity check represents the maximum amount 54
of time that the PPC SLP will permit the PPC call to continue without receiving some 55
positive communication from the MSC. Examples of positive communication from the 56
MSC are: ANLYZD received for call rating, TANSWER received, OANSWER received, a 57
response received to a CCDIR, TDISCONNECT received, or ODISCONNECT received. 58
The term last confirmed communication used in this annex refers to the last time that a 59
60

PN-4287
1
positive communication was received from the MSC or to the time the Call Control
2
Directive Timer expired. When the sanity check interval has been reached, the PPC SLP
3
will send a heartbeat CCDIR to the MSC to check on the call status. If no response to the
4
CCDIR is received, the PPC SLP may apply a partial credit to the PPC account and will
5
retry the heartbeat CCDIR at the end of the next sanity check interval. This process of
6
crediting and retrying is repeated for a limited number of times. A configurable
7
maximum number of times that the CCDIR will be sent without receiving a response
8
must be defined to eliminate flooding the network with CCDIRs.
9
10
11 The sanity check procedure permits the PPC SLP to determine if the PPC call is in an
12 unknown state and to take measures to provide the PPC subscriber with the expected
13 notifications upon recovery or to prevent total depletion of the PPC account during a
14 temporary failure. In order to do this, the PPC SLP must keep track of the key events
15 related to PPC charging and take actions to make adjustments to PPC charging whenever
16 the event does not occur. The PPC SLP may keep track of these events via time stamps,
17 timers or some other method. Details of exactly how this sanity check procedure is to be
18 implemented in the SCP are beyond the scope of this annex and shall be determined by
19 the individual PPC SLP vendors. The PPC SLP can be configured at the operator’s
20 discretion to provide some PPC account adjustments or credits during intervals when the
21 call is in an unknown state.
22
23
The ANSWER message (OANSWER, TANSWER) is critical for PPC charging. Since this
24
message does not have a RETURN RESULT, it is possible to have a runaway call
25
scenario if the MSC sets up the call and sends an ANSWER message but the PPC SLP
26
does not, for whatever reason, receive the ANSWER message. To address this issue of
27
runaway calls the PPC SLP shall do the following:
28
29 1. Decrement the PPC account based on a service provider defined interval against
30 the last confirmed communication.
31
32 2. If the last confirmed communication is before the ANSWER (i.e. ANLYZD), a
33 configurable pre-answer credit may be applied to the PPC account for the time
34 interval between the last confirmed communication and the ANSWER message.
35 This deals with the case where no ANSWER message is received at the SCF
36 network entity but a DISCONNECT message (ODISCONNECT,
37 TDISCONNECT) is received.
38
3. If the ANSWER message is received, then a credit may be given for the time
39
between the ANSWER and the last confirmed communication. Start
40
decrementing the PPC account from the time of answer. Now the ANSWER
41
message represents the last confirmed communication.
42
43 4. Stop decrementing the PPC account when a DISCONNECT message is received
44 at the SCF network entity.
45
46
47
The PPC SLP sends a CCDIR to order a low balance notification when it detects the low
48
balance threshold. When the timer for the CCDIR expires at the SCF network entity, the
49
PPC SLP shall do the following:
50
1. Credit the PPC account for the interval from the last confirmed communication.
51
52 2. Reset the interval for the low balance threshold.
53
54 3. Retry sending the CCDIR when the low balance threshold is again reached.
55
56
4. Repeat steps 1-to-3 as long as the maximum number of retries for
57
unacknowledged CCDIRs has not been reached. This provides the PPC SLP
58
with a means to give the normal notification if the system recovers from the
59
60

PN-4287
1
temporary failure. By crediting the PPC account during the unknown call state
2
the account does not become completely depleted during a temporary failure.
3
5. If the maximum number of retries for unacknowledged CCDIRs has been 4
reached, credit the PPC account for the interval from the last confirmed 5
communication and stop decrementing the PPC account. 6

7
8
The SCP sends a CCDIR if the time since the last confirmed communication has 9
exceeded the sanity check interval. This may occur, for example, if no DISCONNECT 10
(i.e., ODISCONNECT, TDISCONNECT) message has been received by the SCF network 11
entity for an active PPC call. When the timer for the CCDIR expires at the SCF network 12
entity, the PPC SLP shall do the following: 13
14
1. Credit the PPC account for the interval from the last confirmed communication.
15
2. The timer expiry for the CCDIR becomes the last confirmed communication. 16
17
3. Continue processing until the sanity check interval has been exceeded again. 18
19
4. Repeat steps 1-to-3 as long as the maximum number of retries for
20
unacknowledged CCDIRs has not been reached, or until the PPC SLP is notified
21
that the call has ended.
22
5. If the maximum number of retries for unacknowledged CCDIRs has been 23
reached, credit the PPC account for the interval from the last confirmed 24
communication and stop decrementing the PPC account. This will prevent the 25
total depletion of the PPC account during a failure. 26

27
28
29
Y.3.2 MSC Failure Recovery Actions 30
31
If the MSC experiences a complete failure, all calls at the MSC are released. The MSC 32
will initiate the Bulk Disconnection procedure, after it returns to a stable state. This 33
mechanism addresses the issue of runaway charging for calls which have ended but for 34
which the PPC SLP has not received disconnection information. The PPC SLP is notified 35
that the MSC has failed and the time the failure occurred. This enables the PPC SLP to 36
initiate internal algorithms to identify and adjust all PPC accounts for calls served by that 37
MSC, which were active at the time of the MSC failure. 38
39
40
Y.3.3 SCF Failure Recovery Actions 41
42
After an SCF network entity recovers from a complete failure, the PPC SLP will retrieve 43
basic data (e.g., BillingID or other information that identifies the call, start time for the 44
call) about PPC calls that had started before the failure occurred. The PPC SLP will 45
initiate the Unreliable Call Data procedure after the SCF network entity returns to a stable 46
state. This action addresses the issue of runaway charging for calls that ended during the 47
SCF network entity failure but for which the SLP is not aware of the call status. The PPC 48
SLP shall initiate internal algorithms to adjust PPC accounts with the received data about 49
calls that ended during the SCF failure. For PPC calls that are still active at the MSC, the 50
PPC SLP shall initiate internal algorithms to resume the normal processing for call 51
monitoring and playing of warning notifications. NOTE: This assumes that the SCF 52
network entity is capable of recovering sufficient data to be able to resume PPC service 53
for these calls. 54
55
56
If the SCF network entity experiences a failure, any calls ongoing at the time of failure
57
will not receive an indication of low balance, nor will the calls be disconnected when the
58
account balance reaches zero. An error in PPC accounts is possible in the case when an
59
60

PN-4287
1
account balance is depleted during SCF failure. The potential PPC account error occurs
2
from the time the balance is depleted until either the call is ended by one of the parties or
3
until the SCF network entity recovers.
4
5
6
7
Y.3.3.1 Identifying Call Data for SCF Failure Recovery
8
9
The ControlNetworkID (CNID) is used to associate call data with the SCF that has
10
experienced a failure. The CNID functions as a search key that is used by the MSC to
11
select call data for recovery of calls handled by the SCF. This key is associated with a
12
call when a particular SCF interaction failure occurs (e.g., there is no response to an
13
ODISCONNECT) and enables SCF call status recovery. When an SCF sends an
14
UNRELCALLDATA to an MSC, the MSC selects all call data matching the received CNID
15
value and sends the call data to the SCF in one or more CRREPORTs.
16
17 Guidelines for the use of the CNID in SCF call data recovery are:
18
19 1. The CNID is sent to the Serving MSC by the HLR upon MS registration (e.g.,
20 regnot) and is stored in the subscriber profile.
21
2. For calls destined for an MS, the HLR sends the CNID to the Originating MSC
22
in the locreq.
23
24 3. When an SCF recovers from a failure, it includes its CNID in the
25 UNRELCALLDATA sent to the MSC.
26
27
28
Y.3.3.2 SIM Failure Recovery
29
30
SIM failure and SIM failure recovery are not considered in this standard.
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
1
2
CHAPTER 5
3
MODIFICATIONS TO TIA/EIA-41.5-D SIGNALING PROTOCOLS
4
5
6
7 CONTENTS
8
9
10
LIST OF FIGURES ........................................................................................................................................ iii
11
12
LIST OF TABLES .......................................................................................................................................... iv
13
14
REVISION HISTORY..................................................................................................................................... v
15
16
17
5 DATA TRANSFER SERVICES....................................................................................................... 1
18 5.1 SS7-BASED DATA TRANSFER SERVICES .................................................................. 1
19 5.1.1 Message Transfer Part .......................................................................................... 1
20
21 6 APPLICATION SERVICES ............................................................................................................. 2
22
23
6.4 MAP OPERATIONS .......................................................................................................... 2
24 6.4.1 General ................................................................................................................. 2
25 6.4.1.2 Operation Specifiers........................................................................ 2
26 6.4.1.3 Mapping of Operations onto TCAP Package Types ....................... 3
27
6.4.2 Operation Definitions ........................................................................................... 4
28
6.4.2.27 LocationRequest ............................................................................. 5
29
30
6.4.2.30 OriginationRequest ......................................................................... 7
31 6.4.2.46 TransferToNumberRequest ........................................................... 11
32 6.4.2.h ServiceRequest.............................................................................. 15
33 6.4.2.i AnalyzedInformation .................................................................... 20
34
6.4.2.m FacilitySelectedAndAvailable ...................................................... 25
35
36
6.4.2.s SRFDirective................................................................................. 28
37 6.4.2.t TBusy ............................................................................................ 29
38 6.4.2.u TNoAnswer ................................................................................... 33
39 6.4.2.y BulkDisconnection........................................................................ 37
40
6.4.2.z CallControlDirective ..................................................................... 38
41
6.4.2.aa OAnswer ....................................................................................... 40
42
43
6.4.2.ab ODisconnect.................................................................................. 42
44 6.4.2.ac CallRecoveryReport...................................................................... 44
45 6.4.2.ad TAnswer........................................................................................ 45
46 6.4.2.ae TDisconnect .................................................................................. 47
47
6.4.2.af UnreliableCallData ....................................................................... 49
48
49 6.5 MAP PARAMETERS....................................................................................................... 50
50 6.5.1.2 Parameter Identifiers ..................................................................... 50
51 6.5.2 Parameter Definitions ......................................................................................... 51
52
6.5.2.2 ActionCode ................................................................................... 51
53
6.5.2.5 AnnouncementCode...................................................................... 52
54
55
6.5.2.97 Profile............................................................................................ 60
56 6.5.2.df TriggerCapability .......................................................................... 62
57 6.5.2.dh TriggerType .................................................................................. 66
58 6.5.2.dj WINOperationsCapability ............................................................ 68
59
60

PN-4287
1
6.5.2.eg CallRecoveryID ............................................................................. 69
2
6.5.2.eh CallRecoveryIDList....................................................................... 70 3
6.5.2.ei DMH_ServiceID ........................................................................... 71 4
6.5.2.ej FeatureIndicator............................................................................. 72 5
6.5.2.ek ControlNetworkID......................................................................... 73 6
7
6.5.2.el ReleaseCause ................................................................................. 74
8
6.5.2.em TimeOfDay.................................................................................... 75
9
6.5.2.en CallStatus....................................................................................... 76 10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
1
2
3
LIST OF FIGURES
4
5 Figure 9 ActionCode parameter ................................................................................. 51
6 Figure 12 AnnouncementCode parameter ................................................................... 52
7 Figure 105 Profile Macro ............................................................................................... 60
8
Figure df TriggerCapability parameter ....................................................................... 62
9
Figure dh TriggerType parameter................................................................................ 66
10
11
Figure dj WINOperationsCapability parameter.......................................................... 68
12 Figure eg CallRecoveryID parameter.......................................................................... 69
13 Figure eh CallRecoveryIDList parameter ................................................................... 70
14 Figure ei DMH_ServiceID parameter......................................................................... 71
15
Figure ej FeatureIndicator parameter ......................................................................... 72
16
17
Figure ek ControlNetworkID parameter ..................................................................... 73
18 Figure el ReleaseCause parameter.............................................................................. 74
19 Figure em TimeOfDay parameter ................................................................................. 75
20 Figure en CallStatus parameter ................................................................................... 76
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
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.5-D Modifications 5-iii List of Figures

PN-4287
LIST OF TABLES 2
3
4
Table 1 MTP Message Priority Values for TIA/EIA-41 Operations .......................... 1 5
Table 8 TIA/EIA-41 MAP Operation Specifiers ........................................................ 2 6
Table 9 Mapping of TIA/EIA-41 Operations onto TCAP Package Types ................. 3 7

8
Table 10 Summary of MAP Operations ....................................................................... 4
9
Table 64 LocationRequest RETURN RESULT Parameters......................................... 5
10
Table 68 OriginationRequest INVOKE Parameters ..................................................... 7 11
Table 69 OriginationRequest RETURN RESULT Parameters .................................... 9 12
Table 100 TransferToNumberRequest INVOKE Parameters ...................................... 11 13
Table 101 TransferToNumberRequest RETURN RESULT Parameters ..................... 13 14

15
Table h-1 ServiceRequest INVOKE Parameters ......................................................... 15
16
Table h-2 ServiceRequest RETURN RESULT Parameters ......................................... 18 17
Table i-1 AnalyzedInformation INVOKE Parameters ................................................ 21 18
Table i-2 AnalyzedInformation RETURN RESULT Parameters ............................... 23 19
Table m-1 FacilitySelectedAndAvailable INVOKE Parameters .................................. 25 20

21
Table m-2 FacilitySelectedAndAvailable RETURN RESULT Parameters ................. 27
22
Table s-1 SRFDirective INVOKE Parameters ............................................................ 28
23
Table t-1 TBusy INVOKE Parameters........................................................................ 29 24
Table t-2 TBusy RETURN RESULT Parameters ....................................................... 31 25
Table u-1 TNoAnswer INVOKE Parameters............................................................... 33 26
Table u-2 TNoAnswer RETURN RESULT Parameters.............................................. 35 27

28
Table y-1 BulkDisconnection INVOKE Parameters ................................................... 37
29
Table y-2 BulkDisconnection RETURN RESULT Parameters ................................... 37 30
Table z-1 CallControlDirective INVOKE Parameters................................................. 38 31
Table z-2 CallControlDirective RETURN RESULT Parameters................................ 39 32
Table aa-1 OAnswer INVOKE Parameters ................................................................... 41 33

34
Table ab-1 ODisconnect INVOKE Parameters ............................................................. 42
35
Table ab-2 ODisconnect RETURN RESULT Parameters ............................................. 43
36
Table ac-1 CallRecoveryReport INVOKE Parameters ................................................. 44 37
Table ac-2 CallRecoveryReport RETURN RESULT Parameters ................................. 44 38
Table ad-1 TAnswer INVOKE Parameters ................................................................... 46 39
Table ae-1 TDisconnect INVOKE Parameters .............................................................. 47 40

41
Table ae-2 TDisconnect RETURN RESULT Parameters ............................................. 48
42
Table af-1 UnreliableCallData INVOKE Parameters ................................................... 49 43
Table af-2 UnreliableCallData RETURN RESULT Parameters................................... 49 44
Table 112 TIA/EIA-41 MAP Parameter Identifiers ..................................................... 50 45
Table 114 ActionCode value......................................................................................... 51 46

47
Table 117 AnnouncementCode value ........................................................................... 53
48
Table df TriggerCapability value ............................................................................... 62
49
Table dh Trigger Type value....................................................................................... 66 50
Table dj WINOperationsCapability value ................................................................. 68 51
Table el Release Cause value..................................................................................... 74 52
Table en Call Status value .......................................................................................... 76 53

54
55
56
57
58
59
60
List of Tables 5-iv TIA/EIA-41.5-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.5-D Modifications 5-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
32
33
34
35
36
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 5-vi TIA/EIA-41.5-D Modifications

PN-4287
1
2
3
5 DATA TRANSFER SERVICES
4
5
6
7
8 5.1 SS7-BASED DATA TRANSFER SERVICES
9
10
11 5.1.1 Message Transfer Part
12
(TIA/EIA-41.5-D, page 5-6)
13
14
15
Table 1 MTP Message Priority Values for TIA/EIA-41 Operations
16 TIA/EIA-41 Operation MTP Message Priority
17
18 BulkDisconnection 0
19
CallControlDirective 0
20
21 OAnswer 0
22 ODisconnect 0
23
24
CallRecoveryReport 0
25 TAnswer 0
26
TDisconnect 0
27
28 UnreliableCallData 0
29
30
31
32
33
34
35
36
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.5-D Modifications 5-1 Data Transfer Services

PN-4287
6 APPLICATION SERVICES 2
3
4
5
6
6.4 MAP OPERATIONS 7

8
9
6.4.1 General 10
11
12
6.4.1.2 Operation Specifiers 13

14
15
16
Table 8 TIA/EIA-41 MAP Operation Specifiers 17
Operation Name Operation Specifier 18

19
H G F E D C B A Decimal 20
BulkDisconnection 0 1 0 1 0 0 0 0 80 21
22
CallControlDirective 0 1 0 1 0 0 0 1 81
23
OAnswer 0 1 0 1 0 0 1 0 82 24
25
ODisconnect 0 1 0 1 0 0 1 1 83
26
CallRecoveryReport 0 1 0 1 0 1 0 0 84 27
28
TAnswer 0 1 0 1 0 1 0 1 85
29
TDisconnect 0 1 0 1 0 1 1 0 86 30
31
UnreliableCallData 0 1 0 1 0 1 1 1 87
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
MAP Operations 5-2 TIA/EIA-41.5-D Modifications

PN-4287
1
6.4.1.3 Mapping of Operations onto TCAP Package Types
2
(TIA/EIA/IS-771, page 5-5)
3
4
5 Table 9 Mapping of TIA/EIA-41 Operations onto TCAP Package Types
6
Operation Name Component Type Package Type
7
8 ConnectionFailure- INVOKE (LAST) CONVERSATION WITH PERMISSION
9 Report RETURN ERROR CONVERSATION WITH PERMISSION
10 REJECT CONVERSATION WITH PERMISSION
11
ConnectResource INVOKE (LAST) CONVERSATION WITHOUT PERMISSION
12 RETURN ERROR CONVERSATION WITH PERMISSION
14
Disconnect- INVOKE (LAST) CONVERSATION WITHOUT PERMISSION
15
Resource RETURN ERROR CONVERSATION WITH PERMISSION
16
REJECT CONVERSATION WITH PERMISSION
17
18
FacilitiesDirective INVOKE (LAST) QUERY WITH PERMISSION
RETURN RESULT (LAST) CONVERSATION WITH PERMISSION
19
RETURN ERROR RESPONSE
20
REJECT RESPONSE
21
22 FacilitiesDirective2 INVOKE (LAST) QUERY WITH PERMISSION
23
24
REJECT RESPONSE
25
26 InstructionRequest INVOKE (LAST) CONVERSATION WITHOUT PERMISSION
27 RETURN RESULT (LAST) RESPONSE
28
REJECT RESPONSE
29
30 MobileOnChannel INVOKE (LAST) RESPONSE
31
OAnswer INVOKE (LAST) UNIDIRECTIONAL
32
33 TAnswer INVOKE (LAST) UNIDIRECTIONAL
34 RemoteUser- INVOKE (LAST) CONVERSATION WITHOUT PERMISSION
35 InteractionDirective RETURN RESULT (LAST) CONVERSATION WITH PERMISSION
36 RETURN ERROR CONVERSATION WITH PERMISSION
38
CallRecoveryReport INVOKE (LAST) CONVERSATION WITHOUT PERMISSION
39
40
RETURN ERROR CONVERSATION WITH PERMISSION
41
42
43 ResetTimer INVOKE (LAST) CONVERSATION WITHOUT PERMISSION
44
RETURN ERROR CONVERSATION WITH PERMISSION
45
46 SeizeResource INVOKE (LAST) QUERY WITH PERMISSION
47 RETURN RESULT (LAST) CONVERSATION WITHOUT PERMISSION
48 RETURN ERROR RESPONSE
49
REJECT RESPONSE
50 SRFDirective INVOKE (LAST) CONVERSATION WITHOUT PERMISSION
51 RETURN RESULT (LAST) CONVERSATION WITH PERMISSION
53 REJECT RESPONSE
54 All other operations INVOKE (LAST) QUERY WITH PERMISSION
55 RETURN RESULT (LAST) RESPONSE
57 REJECT RESPONSE
58
59
60
TIA/EIA-41.5-D Modifications 5-3 MAP Operations

PN-4287
6.4.2 Operation Definitions 2

3
4
5
Table 10 Summary of MAP Operations 6
7
Operation Reference
8
BulkDisconnection 6.4.2.y 9
10
CallControlDirective 6.4.2.z
11
OAnswer 6.4.2.aa 12
13
ODisconnect 6.4.2.ab
14
CallRecoveryReport 6.4.2.ac 15
16
TAnswer 6.4.2.ad
17
TDisconnect 6.4.2.ae 18
UnreliableCallData 6.4.2.af 19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Operation Definitions 5-4 TIA/EIA-41.5-D Modifications

PN-4287
1
2 6.4.2.27 LocationRequest
3
4
5 The LocationRequest operation success is reported with a TCAP RETURN RESULT
6 (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded
7 as follows:
8
9
Table 64 LocationRequest RETURN RESULT Parameters
10
11 LocationRequest RETURN RESULT Parameters
12
Field Value Type Reference Notes
13
14 Identifier SET [NATIONAL 18] M 6.3.2.2
15 Length variable octets M 6.3.2.2
16
Contents
17
18 ElectronicSerialNumber M 6.5.2.63 a
19
MobileIdentificationNumber M 6.5.2.81 a
20
21
MSCID (Serving MSC) M 6.5.2.82 b
22 AccessDeniedReason O 6.5.2.1 c
23
AnnouncementList O 6.5.2.6 d
24
25 CallingPartyNumberString1 O 6.5.2.23 e
27
ControlNetworkID O 6.5.2.ek s
28
29 Digits (Carrier) O 6.5.2.58 f
30
Digits (Destination) O 6.5.2.58 g, h
31
32
DisplayText O 6.5.2.bx e, p
33 DMH_AccountCodeDigits O 6.5.2.59 i
34
DMH_AlternateBillingDigits O 6.5.2.60 i
35
36 DMH_BillingDigits O 6.5.2.61 i
37 DMH_RedirectionIndicator O 6.5.2.62 j
38
DMH_ServiceID O 6.5.2.ei q
39
40 GroupInformation O 6.5.2.69 k
41
IMSI O 6.5.2.bu f
42
43
MobileDirectoryNumber O 6.5.2.80 i
44 NoAnswerTime O 6.5.2.87 l
45
OneTimeFeatureIndicator O 6.5.2.88 m
46
47 PC_SSN (Serving MSC or VLR) O 6.5.2.93 n
48 PreferredLanguageIndicator O 6.5.2.96 f, r
49
RedirectingNumberDigits O 6.5.2.107 j
50
51 RedirectingNumberString O 6.5.2.108 e
52
RedirectingSubaddress O 6.5.2.109 e, j
53
54
RoutingDigits O 6.5.2.114 f
55 TerminationList O 6.5.2.156 o
56
TerminationTriggers O 6.5.2.159 f
57
58 TriggerAddressList O 6.5.2.de f, t
59
60
TIA/EIA-41.5-D Modifications 5-5 LocationRequest

PN-4287
1
Notes:
2
a. Value is all zeroes, if unknown. 3
4
b. Value is MSCID (Originating), if access is denied or routing to a directory
5
number.
6
c. Include if access may be denied. 7

8
d. Include if one or more tones or announcements is to be applied to the calling 9
party. 10
11
e. Include for local termination (i.e., the LocalTermination parameter is included 12
within the TerminationList parameter) if a related feature is active. 13
14
f. Include if applicable.
15
g. Include if call is to be routed over a network. 16

17
h. Use only with system not capable of using the TerminationList parameter. 18
19
i. Include if available for recording purposes (see DMH). 20
21
j. Include if available and call redirection may apply.
22
k Include for multi-leg calls. 23
24
l. Include to request an override of the Originating MSC’s default No Answer Time 25
value. 26
27
m. Include if modification to normal feature processing is required for a call in
28
progress.
29
n. Use is for further study. 30

31
o. Include if call routing is required. 32
33
p. Refer to IS-764. 34
35
q. Include for recording purposes if a WIN service was invoked.
36
r. This parameter may only be included if the AnnouncementList parameter is 37

38
present.
39
s. Include to correlate call data for SCF data recovery. 40

41
t. Include to indicate address associated with active WIN triggers. 42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
LocationRequest 5-6 TIA/EIA-41.5-D Modifications

PN-4287
1
2 6.4.2.30 OriginationRequest
3
4
5 The OriginationRequest operation is used to request call origination treatment on behalf
6 of a registered MS.
7
8 The OriginationRequest operation is initiated with a TCAP INVOKE (LAST). This is
9 carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is
10 encoded as follows:
11
12 Table 68 OriginationRequest INVOKE Parameters
13
OriginationRequest INVOKE Parameters Timer: ORT
14
15 Field Value Type Reference Notes
16
Identifier SET [NATIONAL 18] M 6.3.2.1
17
19
Contents
20
21
BillingID (Originating) M 6.5.2.16
22 Digits (Dialed) M 6.5.2.58
23
ElectronicSerialNumber M 6.5.2.63
24
25 MSCID (Originating MSC) M 6.5.2.82
26 MSID M 6.5.2.bv k
27
OriginationTriggers M 6.5.2.90
28
29 TransactionCapability M 6.5.2.160
30 CallingPartyName O 6.5.2.bw g, i
31
CallingPartyNumberDigits1 O 6.5.2.21 a
32
33 CallingPartyNumberDigits2 O 6.5.2.22 a
34
CallingPartySubaddress O 6.5.2.25 a
35
36
LocationAreaID O 6.5.2.77 a, l
37 MobileDirectoryNumber O 6.5.2.80 b
38
FeatureIndicator O 6.5.2.ej m
39
40 MSCIdentificationNumber O 6.5.2.83 c
41
OneTimeFeatureIndicator O 6.5.2.88 d
42
43
PC_SSN (Originating MSC) O 6.5.2.93 e
44 PreferredLanguageIndicator O 6.5.2.96 j
45
SenderIdentificationNumber O 6.5.2.116 f
46
47 ServingCellID O 6.5.2.117 a, n
48 TriggerType O 6.5.2.dh h
49
WINCapability O 6.5.2.di o
50
51
52 Notes:
53 a. Include if applicable.
54
55 b. Include if available for recording purposes (see DMH).
56
57
c. Include to identify the MSC initiating the message.
58
d. Include if any OneTimeFeatureIndicator status bits are set (i.e., have value of 1).
59
60
TIA/EIA-41.5-D Modifications 5-7 OriginationRequest

PN-4287
1
e. Include if SS7 may be used for subsequent call redirection.
2
f. Include to identify intermediate message sender if different from the 3
MSCIdentificationNumber. 4
5
g. Include if calling party name information is known. 6
7
h. Include to identify the trigger encountered. 8
9
i. Refer to IS-764.
10
j. Include if available. 11
12
k. Include the identifier used by the MS to access the system. (If the identifier is a 13
MIN-based IMSI, the MobileIdentificationNumber derived from the IMSI is 14
included.) 15
16
l. Include if the current location area information is available.
17
18
m. Include to identify a feature invoked for the call (e.g., Three-Way Calling).
19
n. Include if the current serving cell identity is available. 20

21
o. Include to identify the WIN capabilities supported. 22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
OriginationRequest 5-8 TIA/EIA-41.5-D Modifications

PN-4287
1
The OriginationRequest operation success is reported with a TCAP RETURN RESULT
2
(LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded
3
as follows:
4
5
6
Table 69 OriginationRequest RETURN RESULT Parameters
7 OriginationRequest RETURN RESULT Parameters
8
11
Length variable octets M 6.3.2.2
12
13 Contents
14
AccessDeniedReason O 6.5.2.1 a
15
16
ActionCode O 6.5.2.2 b
17 AnnouncementList O 6.5.2.6 c
18
CallingPartyNumberString1 O 6.5.2.23 d, e
19
20 CallingPartyNumberString2 O 6.5.2.24 d, e
21 CallingPartySubaddress O 6.5.2.25 d, e, f
22
CarrierDigits O 6.5.2.28 g
23
24 Digits (Dialed) O 6.5.2.58 h
25 DisplayText O 6.5.2.bx d, e, r
26
DMH_AccountCodeDigits O 6.5.2.59 i
27
28 DMH_AlternateBillingDigits O 6.5.2.60 i
29
DMH_BillingDigits O 6.5.2.61 i
30
31
DMH_RedirectionIndicator O 6.5.2.62 i, j
32 DMH_ServiceID O 6.5.2.ei s
33
GroupInformation O 6.5.2.69 k
34
35 MobileDirectoryNumber O 6.5.2.80 i
36 NoAnswerTime O 6.5.2.87 l
37
OneTimeFeatureIndicator O 6.5.2.88 m
38
39 PilotNumber O 6.5.2.95 k
40
RedirectingNumberDigits O 6.5.2.107 f
41
42
RedirectingNumberString O 6.5.2.108 d
43 RedirectingSubaddress O 6.5.2.109 d, e
44
ResumePIC O 6.5.2.cu p
45
46 RoutingDigits O 6.5.2.114 g
47 TerminationList O 6.5.2.156 n
48
TerminationTriggers O 6.5.2.57 o
49
50 TriggerAddressList O 6.5.2.de q
51
52 Notes:
53
a. Include if access is denied. If included, no other optional parameters shall be
54
included (with the exception of the AnnouncementList parameter).
55
56 b. Include if action to be performed is not implied through presence of other
57 parameters.
58
59 c. Include if one or more tones or announcements are to be applied to the MS.
60
TIA/EIA-41.5-D Modifications 5-9 OriginationRequest

PN-4287
1
d. Include if a LocalTermination parameter is included in the TerminationList
2
parameter.
3
e. Include if the related feature is active. 4

5
f. Include if a PSTNTermination parameter or an IntersystemTermination 6
parameter is included within the TerminationList parameter. 7
8
g. Include if applicable. 9
10
h. Include if digits remain to be translated by the MSC.
11
13
j. Include if redirection may apply. 14
15
k. Include for multi-leg calls.
16
l. Include to request an override of the Serving MSC’s default No Answer Time 17
value. 18
19
m. Include if modification to normal feature processing is required for the call in 20
progress. 21
22
n. Include if call routing is required. 23
24
o. Include to indicate processing in the Originating MSC for failed call attempts.
25
p. Include to indicate the PIC where call processing is to resume. 26

27
q. Include to indicate address associated with active WIN triggers. 28
29
r. Refer to IS-764. 30
31
s. Include for recording purposes if a WIN service was invoked.
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
OriginationRequest 5-10 TIA/EIA-41.5-D Modifications

PN-4287
1
2 6.4.2.46 TransferToNumberRequest
3
(TIA/EIA-41.5-D, page 5-110)
4
5 The TransferToNumberRequest operation is used during feature processing to obtain an
6 MS’s forward-to number from the HLR.
7
8 The TransferToNumberRequest operation is initiated with a TCAP INVOKE (LAST).
9 This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is
11
12 Table 100 TransferToNumberRequest INVOKE Parameters
13
TransferToNumberRequest INVOKE Parameters Timer: TTNRT
14
16
17
19
Contents
20
21
ElectronicSerialNumber M 6.5.2.63
22 MSID M 6.5.2.bv h
23
RedirectionReason M 6.5.2.110
24
25 SystemMyTypeCode (MSC) M 6.5.2.147
26 BillingID (Originating) O 6.5.2.16 a
27
GroupInformation O 6.5.2.69 b
28
29 LegInformation O 6.5.2.75 c
30 MSCID (Originating) O 6.5.2.82 d
31
MSCIdentificationNumber O 6.5.2.83 e
32
33 PilotBillingID O 6.5.2.94 f
34
PilotNumber O 6.5.2.95 f
35
36
SenderIdentificationNumber O 6.5.2.116 g
37 TransactionCapability O 6.5.2.160 e
38
WINCapability O 6.5.2.di i
39
40
41
Notes:
42 a. Include to identify the Originating MSC and its BillingID for subsequent call
43 redirection.
44
45 b. Include if available (i.e., if provided in the associated RoutingRequest INVOKE
46 or LocationRequest RETURN RESULT) for the None Reachable termination
47 trigger.
48
c. Include if available (i.e., if provided in the associated RoutingRequest INVOKE
49
or LocationRequest RETURN RESULT) for any termination trigger except
50
None Reachable.
51
52 d. Include on TIA/EIA-41 or later.
53
54 e. Include on IS-41-C or later.
55
56
f. Include if available.
57
g. Include to identify the network entity sending the message.
58
59
60
TIA/EIA-41.5-D Modifications 5-11 TransferToNumberRequest

PN-4287
1
h. Use the MobileIdentificationNumber form of the MSID if the IMSI is known to
2
be a MIN-based IMSI.
3
i. Include to identify the WIN capabilities supported. 4

5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TransferToNumberRequest 5-12 TIA/EIA-41.5-D Modifications

PN-4287
1
The TransferToNumberRequest operation success is reported with a TCAP RETURN
2
RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is
3
encoded as follows:
4
5
6
Table 101 TransferToNumberRequest RETURN RESULT Parameters
7 TransferToNumberRequest RETURN RESULT Parameters
8
11
12
13 Contents
14
Digits (Destination) M 6.5.2.58 a
15
16
AccessDeniedReason O 6.5.2.1 b
17 ActionCode O 6.5.2.2 c
18
AnnouncementList O 6.5.2.6 d
19
22
CallingPartySubaddress O 6.5.2.25 e, f
23
24 Digits (Carrier) O 6.5.2.58 g
25 DMH_AccountCodeDigits O 6.5.2.59 h
26
DMH_AlternateBillingDigits O 6.5.2.60 h
27
28 DMH_BillingDigits O 6.5.2.61 h
29
DMH_RedirectionIndicator O 6.5.2.62 h
30
31
DMH_ServiceID O 6.5.2.ei k
32 GroupInformation O 6.5.2.69 i
33
MobileDirectoryNumber O 6.5.2.80 h
34
35 NoAnswerTime O 6.5.2.87 g, n
36
PreferredLanguageIndicator O 6.5.2.96 g, m
37
38 RedirectingNumberDigits O 6.5.2.107 f
39 RedirectingNumberString O 6.5.2.108 e
40
RedirectingSubaddress O 6.5.2.109 e, f
41
42 TerminationList O 6.5.2.156 j
43 TerminationTriggers O 6.5.2.159 g
44
TriggerAddressList O 6.5.2.de l
45
46
47 Notes:
48 a. This parameter is ignored if the TerminationList parameter is provided.
49
50 b. Include if access is denied. If included, no other optional parameters shall be
51 included (with the exception of the AnnouncementList).
52
53
c. Include if action to be performed is not implied through presence of other
54
parameters.
55
d. Include if one or more tones or announcements are to be applied to the MS.
56
57 e. Include if related feature is active and if a LocalTermination parameter is
58 included within the TerminationList parameter.
59
60
TIA/EIA-41.5-D Modifications 5-13 TransferToNumberRequest

PN-4287
1
f. Optionally include if a PSTNTermination parameter or an
2
IntersystemTermination parameter is included within the TerminationList
3
parameter.
4
g. Include if applicable. 5
6
h. Include if available for recording purposes (see DMH). 7
8
i. Include for multi-leg calls. 9
10
j. Include if call routing is required.
11
k. Include for recording purposes if a WIN service was invoked. 12
13
l. Include to identify WIN triggers for the redirected call. 14
15
m. This parameter may only be included if the AnnouncementList parameter is 16
present. 17
18
n. Include to request an override of the Originating MSC’s default No Answer Time 19
value. 20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TransferToNumberRequest 5-14 TIA/EIA-41.5-D Modifications

PN-4287
1
6.4.2.h ServiceRequest
2
3
4
The ServiceRequest (SERVREQ) operation is used by service logic to invoke specific
5
service logic execution on another network entity (NE) containing the service logic for
6
the requested services.
7
8 The ServiceRequest operation is initiated with a TCAP INVOKE (LAST). This is carried
9 by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as
10 follows:
11
12
Table h-1 ServiceRequest INVOKE Parameters
13
14 ServiceRequest INVOKE Parameters Timer: SVRT
15
16
19
Contents
20
21 ServiceID M 6.5.2.bz
22
AccessDeniedReason O 6.5.2.1 c, d
23
24
AvailabilityType O 6.5.2.15 c, e
25 BillingID O 6.5.2.16 a, f
26
CallingPartyName O 6.5.2.bw a
27
28 CallingPartyNumberDigits1 O 6.5.2.21 a
29 CallingPartyNumberDigits2 O 6.5.2.22 b
30
CallingPartySubaddress O 6.5.2.25 a
31
32 CarrierDigits O 6.5.2.28 p
33
ConditionallyDeniedReason O 6.5.2.48 c, d
34
35
DataAccessElementList O 6.5.2.cd c
36 DestinationDigits O 6.5.2.56 q
37
Digits (Dialed) O 6.5.2.58 a
38
39 DMH_RedirectionIndicator O 6.5.2.62 c
40
DMH_ServiceID O 6.5.2.ej c, r
41
42 ElectronicSerialNumber O 6.5.2.63 c, s
43 ExtendedMSCID O 6.5.2.64 c, t
44
45
FeatureIndicator O 6.5.2.ej c, u
46 GroupInformation O 6.5.2.69 c
47
LegInformation O 6.5.2.75 c
48
49 LocationAreaID O 6.5.2.77 c
50 MobileDirectoryNumber O 6.5.2.80 c, g
51
MSCID (Invoking) O 6.5.2.82 c, h
52
53 MSCIdentificationNumber (Invoking) O 6.5.2.82 c, i
54
MSID O 6.5.2.bv c, g
55
MSCIN (Invoking) O 6.5.2.83 c, i
56
57 PC_SSN O 6.5.2.93 i, j
58
59
60
TIA/EIA-41.5-D Modifications 5-15 ServiceRequest

PN-4287
1
Table h-1 ServiceRequest INVOKE Parameters (concluded) 2
3
Contents (continued)
4
PilotBillingID O 6.5.2.94 c 5
PilotNumber O 6.5.2.95 c 6
7
PreferredLanguageIndicator O 6.5.2.96 a
8
RedirectingPartyName O 6.5.2.by a 9
RedirectingNumberDigits O 6.5.2.107 a 10
11
RedirectingSubaddress O 6.5.2.109 a
12
RedirectionReason O 6.5.2.110 a, c 13
14
RoutingDigits O 6.5.2.114 v
15
SenderIdentificationNumber O 6.5.2.116 k 16
ServingCellID O 6.5.2.117 c 17
18
SystemMyTypeCode O 6.5.2.147 l
19
TerminationAccessType O 6.5.2.155 c 20
TimeDateOffset O 6.5.2.dd c, w 21
22
TimeOfDay O 6.5.2.em c, x 23
TransactionCapability O 6.5.2.160 m 24
25
TriggerType O 6.5.2.dh n
26
WINCapability O 6.5.2.di o 27
28
Notes: 29
30
a. Include if available.
31
b. Include if user provided, passed screening calling party number is available. 32

33
c. Include if applicable. 34
35
d. Include if a RoutingRequest operation was completed prior to the 36
ServiceRequest operation, and access was denied. 37
38
e. Include when MS is predictably unavailable for Call Delivery (e.g., slotted mode
39
or sleep mode).
40
f. Include to correlate service usage with call instance. 41
42
g. Include if the MSID is available and is not the same as the Digits (Dialed). 43
44
g. Include if MIN is available and is not the same as Digits (Dialed).
45
h. Include to identify invoking MSC. 46

47
i. Include if SS7 is used. 48
49
j. Not for international applications. 50
51
k. Include to identify invoking NE.
52
l. Include to indicate the vendor type of the invoking NE. 53

54
m. Include to indicate the capabilities of the MSC that the invoking NE (e.g., HLR, 55
SCP, SN) chooses to convey to the NE (e.g., SCP, SN) with the service logic for 56
the requested services. 57
58
n. Include to identify the trigger encountered by the MSC. 59
60
ServiceRequest 5-16 TIA/EIA-41.5-D Modifications

PN-4287
1
o. Include to indicate the WIN capabilities supported.
2
3 p. Include to identify the interexchange carrier for call routing.
4
5 q. Include to identify the network address of the called party for call routing.
6
7 r. Include to identify the Service Logic Program invoked on behalf of the MS.
8
9
s. Include to identify the MS.
10
t. Include to identify MSC serving the MS if not indicated by the MSCID
11
parameter.
12
13
u. Include to identify a feature invoked for the call (e.g., Three-Way Calling).
14
15 v. Include to identify special routing information for call routing.
16
17 w. Include to indicate the time offset of Local Civil Time with respect to
18 Coordinated Universal Time (UTC).
19
20 x. Include to indicate the time of day in UTC.
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
1
The ServiceRequest operation success is reported with a TCAP RETURN RESULT
2
3
as follows:
4
5
Table h-2 ServiceRequest RETURN RESULT Parameters 6
ServiceRequest RETURN RESULT Parameters 7

8
Field Value Type Reference Notes 9
Identifier SET [NATIONAL 18] M 6.3.2.2 10

11
12
Contents 13
14
AccessDeniedReason O 6.5.2.1 b
15
ActionCode O 6.5.2.2 c 16
AlertCode O 6.5.2.3 d 17
18
AnnouncementList O 6.5.2.6 e
19
CallingPartyName O 6.5.2.bw a 20
CallingPartyNumberString1 O 6.5.2.23 a 21
22
CallingPartyNumberString2 O 6.5.2.24 a
23
CallingPartySubaddress O 6.5.2.25 a 24
CarrierDigits O 6.5.2.28 a 25
26
Digits (Dialed) O 6.5.2.58 f
27
DisplayText O 6.5.2.bx a 28
29
DMH_AccountCodeDigits O 6.5.2.59 a
30
DMH_AlternateBillingDigits O 6.5.2.60 a 31
DMH_BillingDigits O 6.5.2.61 a 32
33
DMH_RedirectionIndicator O 6.5.2.62 a
34
DMH_ServiceID O 6.5.2.ei i 35
GroupInformation O 6.5.2.69 a 36
37
MobileDirectoryNumber O 6.5.2.80 a
38
NoAnswerTime O 6.5.2.87 a 39
40
RedirectingNumberDigits O 6.5.2.107 a
41
RedirectingNumberString O 6.5.2.108 a 42
RedirectingPartyName O 6.5.2.by a 43
44
RedirectingSubaddress O 6.5.2.109 a
45
ResumePIC O 6.5.2.cu g 46
RoutingDigits O 6.5.2.114 a 47
48
TerminationList O 6.5.2.156 h
49
TriggerAddressList O 6.5.2.de a, j 50
51
Notes: 52
53
a. Include if applicable.
54
b. Include if service logic determines access to the MS is denied. 55

56
c. Include if action to be performed is not implied through presence of other 57
parameters. 58
59
60
ServiceRequest 5-18 TIA/EIA-41.5-D Modifications

PN-4287
1
d. Include to specify special alerting treatment.
2
3 e. Include if one or more tones or announcements are to be applied to the MS.
4
5 f. Include if digits remain to be translated by the MSC.
6
7
g. Include to indicate the PIC where call processing is to resume.
8
h. Include if call routing is required.
9
10 i. Include for recording purposes if a WIN service was invoked.
11
12 j. Include to indicate address associated with active WIN triggers.
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
1
6.4.2.i AnalyzedInformation
2
3
4
The AnalyzedInformation (ANLYZD) operation is used by the MSC to provide
5
notification to a service logic network element (e.g., SCP, SN) that a trigger criteria at the
6
Analyzed_Information DP has been satisfied. Service logic may then invoke a service or
7
services.
8
The AnalyzedInformation operation is initiated with a TCAP INVOKE (LAST). This is 9
carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is 10
encoded as follows: 11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
AnalyzedInformation 5-20 TIA/EIA-41.5-D Modifications

PN-4287
1
Table i-1 AnalyzedInformation INVOKE Parameters
2
3 AnalyzedInformation INVOKE Parameters Timer: ANZT
4
5
7
8
9
Contents
10 BillingID (Originating) M 6.5.2.16 a
11
Digits (Dialed) M 6.5.2.58
12
13 MSCID (Originating) M 6.5.2.82 b
14 TransactionCapability M 6.5.2.160
15
TriggerType M 6.5.2.dh c
16
17 WINCapability M 6.5.2.di d
18 CallingPartyName O 6.5.2.bw e, m
19
CallingPartyNumberDigits1 O 6.5.2.21 e
20
21 CallingPartyNumberDigits2 O 6.5.2.22 e
22
CallingPartySubaddress O 6.5.2.25 e
23
24
CarrierDigits O 6.5.2.28 n, o
25 ConferenceCallingIndicator O 6.5.2.49 f
26
DestinationDigits O 6.5.2.56 n, p
27
28 DMH_RedirectionIndicator O 6.5.2.62 q
29
ElectronicSerialNumber O 6.5.2.63 g, r
30
31 FeatureIndicator O 6.5.2.ej s
32
LocationAreaID O 6.5.2.77 h, t
33
34 MobileDirectoryNumber O 6.5.2.80 i
35 MSCIdentificationNumber O 6.5.2.83 j
36
MSID O 6.5.2.bv g, r
37
38 OneTimeFeatureIndicator O 6.5.2.88 k
39
PreferredLanguageIndicator O 6.5.2.96
40
41
RedirectingNumberDigits O 6.5.2.107 e
42 RedirectingPartyName O 6.5.2.by b, m
43
RedirectingSubaddress O 6.5.2.109 e
44
45 RoutingDigits O 6.5.2.114 n, u
46 ServingCellID O 6.5.2.117 h, v
47
48
SystemMyTypeCode O 6.5.2.147
49 TerminationAccessType O 6.5.2.155 l
50
TimeDateOffset O 6.5.2.dd w
51
52 TimeOfDay O 6.5.2.em x
53
54 Notes:
55
a. Include to identify the call.
56
57 b. Include to identify the requesting MSC.
58
59 c. Include to identify the trigger encountered.
60
TIA/EIA-41.5-D Modifications 5-21 AnalyzedInformation

PN-4287
1
d. Include to identify the WIN capabilities supported.
2
e. Include if available (i.e., provided in call origination). 3

4
f. Include to indicate the number of conferees already in the call. 5
6
g. Include to identify the MS. 7
8
h. Include if available (information related to MS origination).
9
11
j. Include to identify the MSC initiating the message. 12
13
k. Include if any OneTimeFeatureIndicator status bits are set (i.e., have value of 1).
14
l. Include if call involves a special access situation (e.g., Roamer port access). 15
16
m. Refer to IS-764. 17
18
n. Include if applicable and a routing address is available. 19
20
o. Include to identify the interexchange carrier for call routing.
21
22
p. Include to identify the network address of the called party for call routing.
23
q. Include to identify the reason for extending the call. 24

25
r. Include if available. 26
27
s. Include to identify a feature invoked for the call (e.g., Three-Way Calling). 28
29
t. Include if the current location area information is available. 30
31
u. Include to identify special routing information for call routing.
32
v. Include if the current serving cell identity is available. 33

34
w. Include to indicate the time offset of Local Civil Time with respect to 35
Coordinated Universal Time (UTC). 36

37
x. Include to indicate the time of day in UTC. 38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
1
The AnalyzedInformation operation success is reported with a TCAP RETURN RESULT
2
3
as follows:
4
5
6
Table i-2 AnalyzedInformation RETURN RESULT Parameters
7 AnalyzedInformation RETURN RESULT Parameters
8
11
12
13 Contents
14
15
16
18
CarrierDigits O 6.5.2.28 d
19
20 ConferenceCallingIndicator O 6.5.2.49 e
21 Digits (Dialed) O 6.5.2.58 f
22
DisplayText O 6.5.2.bx d, m
23
24 DMH_AccountCodeDigits O 6.5.2.59 g
25 DMH_AlternateBillingDigits O 6.5.2.60 g
26
DMH_BillingDigits O 6.5.2.61 g
27
28 DMH_RedirectionIndicator O 6.5.2.62 g, h
29
DMH_ServiceID O 6.5.2.ei n
30
31 NoAnswerTime O 6.5.2.87 i
32 OneTimeFeatureIndicator O 6.5.2.88 j
33
RedirectingNumberDigits O 6.5.2.107 d
34
35 ResumePIC O 6.5.2.cu k
36 RoutingDigits O 6.5.2.114 d
37
TerminationList O 6.5.2.156 l
38
39 TerminationTriggers O 6.5.2.159 d
40
TriggerAddressList O 6.5.2.de d, o
41
42
43
Notes:
44 a. Include if access is denied. If included, no other optional parameters shall be
45 included (with the exception of the AnnouncementList parameter).
46
47
b. Include if action to be performed is not implied through presence of other
48
parameters.
49
c. Include if one or more tones or announcements are to be applied to the MS.
50
51 d. Include if applicable.
52
53 e. Include to direct that ongoing call be transformed into a Conference Call.
54
55
f. Include if digits remain to be translated by the MSC.
56
g. Include if available for recording purposes (see DMH).
57
58 h. Include if redirection may apply.
59
60
TIA/EIA-41.5-D Modifications 5-23 AnalyzedInformation

PN-4287
1
i. Include to request an override of the Serving MSC's default No Answer Time
2
value.
3
j. Include if modification to normal feature processing is required for the call in 4
progress. 5
6
k. Include to indicate the PIC where call processing is to resume. 7
8
l. Include if call routing is required. 9
10
m. Refer to IS-764.
11
n. Include for recording purposes if a WIN service was invoked. 12
13
o. Include to indicate address associated with active WIN triggers. 14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
1
2 6.4.2.m FacilitySelectedAndAvailable
3
4
5 The FacilitySelectedAndAvailable (FAVAIL) operation is used by an Serving MSC to
6 obtain call treatment instructions from an SCP or SN.
7
8 The FacilitySelectedAndAvailable operation is initiated with a TCAP INVOKE (LAST).
9 This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is
11
12 Table m-1 FacilitySelectedAndAvailable INVOKE Parameters
13
FacilitySelectedAndAvailable INVOKE Parameters Timer: FAVT
14
16
17
19
Contents
20
21
BillingID (Serving) M 6.5.2.16
22 MSCID (Serving) M 6.5.2.82
23
TransactionCapability M 6.5.2.160
24
25 TriggerType M 6.5.2.dh a
26 WINCapability M 6.5.2.di b
27
CallingPartyName O 6.5.2.bw c, i
28
29 CallingPartyNumberDigits1 O 6.5.2.21 c
30 CallingPartyNumberDigits2 O 6.5.2.22 c
31
CallingPartySubaddress O 6.5.2.25 c
32
33 ElectronicSerialNumber O 6.5.2.63
34
GroupInformation O 6.5.2.69 c
35
36
LegInformation O 6.5.2.75 c
37 LocationAreaID O 6.5.2.77 c
38
MobileDirectoryNumber O 6.5.2.80 d, e
39
MobileIdentificationNumber O 6.5.2.81 d
40
41 MSCIdentificationNumber O 6.5.2.83 f
42
MSID O 6.5.2.bv d, j
43
44 OneTimeFeatureIndicator O 6.5.2.88 g
45 PilotBillingID O 6.5.2.94 c
46
PilotNumber O 6.5.2.95 c
47
48 PreferredLanguageIndicator O 6.5.2.96 c
49 RedirectingNumberDigits O 6.5.2.107 c
50
RedirectingPartyName O 6.5.2.by c, i
51
52 RedirectingSubaddress O 6.5.2.109 c
53
ServingCellID O 6.5.2.117 c
54
55
56 TerminationAccessType O 6.5.2.155 h
57
58 Notes:
59
60
TIA/EIA-41.5-D Modifications 5-25 FacilitySelectedAndAvailable

PN-4287
1
a. Indicates the detected trigger.
2
b. Include to identify the WIN capabilities supported. 3

4
c. Include if available. 5
6
d. One must be present for use as service key. 7
8
e. Include if available for recording purposes (see DMH).
9
f. Include to identify the MSC sending the message. 10
11
g. Include if any OneTimeFeatureIndicator status bits are set (i.e., have value of 1). 12
13
h. Include if call involves a special access situation (e.g., Roamer port access).
14
i. Refer to IS-764. 15
16
j. Include to identify the MS. 17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
FacilitySelectedAndAvailable 5-26 TIA/EIA-41.5-D Modifications

PN-4287
1
The FacilitySelectedAndAvailable operation success is reported with a TCAP RETURN
2
RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set
3
is encoded as follows:
4
5
6
Table m-2 FacilitySelectedAndAvailable RETURN RESULT Parameters
7 FacilitySelectedAndAvailable RETURN RESULT Parameters
8
11
12
13 Contents
14
15
16
17 AlertCode O 6.5.2.3 c
18
DisplayText O 6.5.2.bx d, j
19
20 DMH_AccountCodeDigits O 6.5.2.59 e
21 DMH_AlternateBillingDigits O 6.5.2.60 e
22
DMH_BillingDigits O 6.5.2.61 e
23
24 DMH_RedirectionIndicator O 6.5.2.62 e, f
25 DMH_ServiceID O 6.5.2.ei k
26
27
NoAnswerTime O 6.5.2.87 g
28 OneTimeFeatureIndicator O 6.5.2.88 h
29
ResumePIC O 6.5.2.cu i
30
31 TerminationTriggers O 6.5.2.159 d
32 TriggerAddressList O 6.5.2.de d, l
33
34
Notes:
35
38
39
parameters.
40
41 c. Include to specify special alerting treatment.
42
43 d. Include if applicable.
44
45
e. Include if available for recording purposes (see DMH).
46
f. Include if redirection may apply.
47
48 g. Include to request an override of the Serving MSC's default No Answer Time
49 value.
50
51 h. Include if modification to normal feature processing is required for the call in
52 progress.
53
54
i. Include to indicate the PIC where call processing is to resume.
55
j. Refer to IS-764.
56
57 k. Include for recording purposes if a WIN service was invoked.
58
59 l. Include to indicate address associated with active WIN triggers.
60
TIA/EIA-41.5-D Modifications 5-27 FacilitySelectedAndAvailable

PN-4287
1
6.4.2.s SRFDirective
2
3
4
The SRFDirective (SRFDIR) operation is used by service control logic to direct the
5
operation of an IP (or other network entity) which provides user interaction.
6
The SRFDirective operation is initiated with a TCAP INVOKE (LAST). This is carried 7
by a TCAP CONVERSATION WITHOUT PERMISSION package. The Parameter Set 8
is encoded as follows: 9
10
11
Table s-1 SRFDirective INVOKE Parameters
12
SRFDirective INVOKE Parameters Timer: SRFDT 13
14
15
Length variable octets M 6.3.2.1 17

18
Contents
19
AnnouncementList O 6.5.2.6 a, d 20
21
DigitCollectionControl O 6.5.2.57 b
22
ExecuteScript O 6.5.2.cl c, d 23
MobileDirectoryNumber O 6.5.2.80 e 24
25
26
Notes:
27
a. When the AnnouncementList parameter is present, the ExecuteScript parameter 28
shall not be included. 29
30
b. This parameter may only be included if the AnnouncementList parameter is
31
present.
32
c. When the ExecuteScript parameter is present, the AnnouncementList and 33
DigitCollectionControl parameters shall not be included. 34

35
d. At least one of these parameters must be present. 36
37
e. Include if applicable. 38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
SRFDirective 5-28 TIA/EIA-41.5-D Modifications

PN-4287
1
2 6.4.2.t TBusy
3
4
5 The TBusy (TBUSY) operation is used by an MSC to obtain call treatment instructions
6 from an SCP or SN for the called party.
7
8 The TBusy operation is initiated with a TCAP INVOKE (LAST). This is carried by a
9 TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as
10 follows:
11
12 Table t-1 TBusy INVOKE Parameters
13
TBusy INVOKE Parameters Timer: TBT
14
16
17
19
Contents
20
21
BillingID (Invoking) M 6.5.2.16 a
22 MSCID M 6.5.2.82 b
23
24
25 TriggerType M 6.5.2.dh c
27
28
30 CallingPartySubaddress O 6.5.2.25 e
31
ElectronicSerialNumber O 6.5.2.63 f
32
33 GroupInformation O 6.5.2.69 f
34
LegInformation O 6.5.2.75 f
35
36
LocationAreaID O 6.5.2.77 g
37 MobileDirectoryNumber O 6.5.2.80 h, i
38 MobileIdentificationNumber O 6.5.2.81 h
39
MSCIdentificationNumber O 6.5.2.83 b
40
41 MSID O 6.5.2.bv h, k
42
OneTimeFeatureIndicator O 6.5.2.88 j
43
45 PilotNumber O 6.5.2.95 f
46
PreferredLanguageIndicator O 6.5.2.96 g
47
48 RedirectingNumberDigits O 6.5.2.107 e
49 RedirectingSubaddress O 6.5.2.109 e
50
RedirectionReason: TBusy O 6.5.2.110 f
51
52 ServingCellID O 6.5.2.117 g
53
54
55
TerminationAccessType O 6.5.2.155 f
56
57 Notes:
58 a. Include to identify the call at the invoking MSC
59
60
TIA/EIA-41.5-D Modifications 5-29 TBusy

PN-4287
1
b. Include to identify the invoking MSC.
2
c. Include to identify the trigger encountered. 3

4
d. Include to identify the WIN capabilities supported. 5
6
8
9
g. Include if available. (Note: this information element may not be available when 10
this operation is initiated by a non-Serving MSC.) 11
12
h. One must be present for use as a service key. 13
14
i. Include if available for recording purposes (see DMH).
15
j. Include if any OneTimeFeatureIndicator status bits are set (i.e., have value of 1). 16
17
k. Include to identify the MS. 18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TBusy 5-30 TIA/EIA-41.5-D Modifications

PN-4287
1
The operation success is reported with a TCAP RETURN RESULT (LAST). This is
2
carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
3
4
5
Table t-2 TBusy RETURN RESULT Parameters
6 TBusy RETURN RESULT Parameters
7
10
11
12 Contents
13
14
15
17
18
20 CarrierDigits O 6.5.2.28 l
21
DisplayText O 6.5.2.bx d, e, m
22
23 DMH_AccountCodeDigits O 6.5.2.59 f
24
DMH_AlternateBillingDigits O 6.5.2.60 f
25
26
DMH_BillingDigits O 6.5.2.61 f
27 DMH_RedirectionIndicator O 6.5.2.62 f
28
29
30 GroupInformation O 6.5.2.69 g
32
PilotNumber O 6.5.2.95 g
33
34 PreferredLanguageIndicator O 6.5.2.96 l, o
35
RedirectingNumberDigits O 6.5.2.107 i
36
37 ResumePIC O 6.5.2.cu j
38 RoutingDigits O 6.5.2.114 l
39
TerminationList O 6.5.2.156 k
40
41 TerminationTriggers O 6.5.2.159 l
42
TriggerAddressList O 6.5.2.de l, p
43
44
45
Notes:
48
49
50
parameters.
51
52
53 d. Include if a LocalTermination parameter is included in the TerminationList
54 parameter.
55
56 e. Include if the related feature is active.
57
58
f. Include if available for recording purposes (see DMH).
59
g. Include for multi-leg calls.
60
TIA/EIA-41.5-D Modifications 5-31 TBusy

PN-4287
1
h. Include if modification to normal feature processing is required for the call in
2
progress.
3
i. Include if call is being redirected. 4

5
j. Include to indicate the PIC where call processing is to resume. 6
7
k. Include if call routing is required. 8
9
l. Include if applicable.
10
12
n. Include for recording purposes if a WIN service was invoked. 13
14
o. This parameter may only be included if the AnnouncementList parameter is 15
present. 16
17
p. Include to indicate address associated with active WIN triggers.
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TBusy 5-32 TIA/EIA-41.5-D Modifications

PN-4287
1
2 6.4.2.u TNoAnswer
3
4
5 The TNoAnswer (TNOANS) operation is used by an MSC to obtain call treatment
6 instructions from an SCP or SN for the called party.
7
8 The TNoAnswer operation is initiated with a TCAP INVOKE (LAST). This is carried by
9 a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as
10 follows:
11
12 Table u-1 TNoAnswer INVOKE Parameters
13
TNoAnswer INVOKE Parameters Timer: TNAT
14
16
17
19
Contents
20
21
BillingID (Invoking) M 6.5.2.16 a
22 MSCID M 6.5.2.82 b
23
24
25 TriggerType M 6.5.2.dh c
27
28
30 CallingPartySubaddress O 6.5.2.25 e
31
ElectronicSerialNumber O 6.5.2.63 f
32
33 GroupInformation O 6.5.2.69 f
34
LegInformation O 6.5.2.75 f
35
36
LocationAreaID O 6.5.2.77 g
37 MobileDirectoryNumber O 6.5.2.80 h, i
38 MobileIdentificationNumber O 6.5.2.81 h
39
MSCIdentificationNumber O 6.5.2.83 b
40
41 MSID O 6.5.2.bv h, k
42
OneTimeFeatureIndicator O 6.5.2.88 j
43
45 PilotNumber O 6.5.2.95 f
46
PreferredLanguageIndicator O 6.5.2.96 g
47
48 RedirectingNumberDigits O 6.5.2.107 e
49 RedirectingSubaddress O 6.5.2.109 e
50
RedirectionReason: TNoAnswer O 6.5.2.110 f
51
52 ServingCellID O 6.5.2.117 g
53
54
55
TerminationAccessType O 6.5.2.155 f
56
57 Notes:
58 a. Include to identify the call at the invoking MSC
59
60
TIA/EIA-41.5-D Modifications 5-33 TNoAnswer

PN-4287
1
b. Include to identify the invoking MSC.
2
c. Include to identify the trigger encountered. 3

4
d. Include to identify the WIN capabilities supported. 5
6
8
9
g. Include if available. (Note: this information element may not be available when 10
this operation is initiated by a non-Serving MSC.) 11
12
h. One must be present for use as a service key. 13
14
i. Include if available for recording purposes (see DMH).
15
j. Include if any OneTimeFeatureIndicator status bits are set (i.e., have value of 1). 16
17
k. Include to identify the MS. 18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TNoAnswer 5-34 TIA/EIA-41.5-D Modifications

PN-4287
1
The TNoAnswer operation success is reported with a TCAP RETURN RESULT (LAST).
2
This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as
3
follows:
4
5
6
Table u-2 TNoAnswer RETURN RESULT Parameters
7 TNoAnswer RETURN RESULT Parameters
8
11
12
13 Contents
14
15
16
18
19
21 CarrierDigits O 6.5.2.28 l
22
DisplayText O 6.5.2.bx d, e, m
23
24 DMH_AccountCodeDigits O 6.5.2.59 f
25
DMH_AlternateBillingDigits O 6.5.2.60 f
26
27
DMH_BillingDigits O 6.5.2.61 f
28 DMH_RedirectionIndicator O 6.5.2.62 f
29
30
31 GroupInformation O 6.5.2.69 g
33
PilotNumber O 6.5.2.95 g
34
35 PreferredLanguageIndicator O 6.5.2.96 l, o
36
RedirectingNumberDigits O 6.5.2.107 i
37
38 ResumePIC O 6.5.2.cu j
39 RoutingDigits O 6.5.2.114 l
40
TerminationList O 6.5.2.156 k
41
42 TerminationTriggers O 6.5.2.159 l
43
TriggerAddressList O 6.5.2.de l, p
44
45
46
Notes:
49
50
51
parameters.
52
53
54 d. Include if a LocalTermination parameter is included in the TerminationList
55 parameter.
56
57 e. Include if the related feature is active.
58
59
f. Include if available for recording purposes (see DMH).
60
TIA/EIA-41.5-D Modifications 5-35 TNoAnswer

PN-4287
1
g. Include for multi-leg calls.
2
h. Include if modification to normal feature processing is required for the call in 3
progress. 4
5
i. Include if call is being redirected. 6
7
j. Include to indicate the PIC where call processing is to resume. 8
9
k. Include if call routing is required.
10
l. Include if applicable. 11
12
14
n. Include for recording purposes if a WIN service was invoked.
15
16
o. This parameter may only be included if the AnnouncementList parameter is
17
present.
18
p. Include to indicate address associated with active WIN triggers. 19

20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TNoAnswer 5-36 TIA/EIA-41.5-D Modifications

PN-4287
1
6.4.2.y BulkDisconnection
2
(New for TIA/EIA-41.5-D Section 6.4.2)
3
4
The BulkDisconnection (BULKDISCONN) operation is used by an MSC to notify a
5
service logic network entity that all calls associated with the service logic network entity
6
have been released due to an MSC failure.
7
8 The BulkDisconnection operation is initiated with a TCAP INVOKE (LAST). This is
11
12
Table y-1 BulkDisconnection INVOKE Parameters
13
14 BulkDisconnection INVOKE Parameters Timer: BDISCT
15
16
19
Contents
20
21 MSCID M 6.5.2.82
22
TimeDateOffset M 6.5.2.2 a
23
24
TimeOfDay M 6.5.2.em b
25 MSCIdentificationNumber O 6.5.2.83 c
26
SenderIdentificationNumber O 6.5.2.116 d
27
28
29
Notes:
30 a. Include to indicate the time offset of Local Civil Time with respect to
32
33
b. Include to indicate the time of day in UTC when the failure occurred.
34
c. Include to identify the MSC initiating the message.
35
36 d. Include to identify the network entity sending the message.
37
38
39
The BulkDisconnection operation success is reported with a TCAP RETURN RESULT
40
41
as follows:
42
43 Table y-2 BulkDisconnection RETURN RESULT Parameters
44
BulkDisconnection RETURN RESULT Parameters
45
47
48
49 Length zero octets M 6.3.2.2
50 Contents
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41.5-D Modifications 5-37 BulkDisconnection

PN-4287
1
6.4.2.z CallControlDirective
2
3
4
The CallControlDirective (CCDIR) operation is used during call processing to control
5
MSC operation for the indicated call.
6
The CallControlDirective operation is initiated with a TCAP INVOKE (LAST). This is 7
carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is 8
encoded as follows: 9
10
11
Table z-1 CallControlDirective INVOKE Parameters
12
CallControlDirective INVOKE Parameters Timer: CCDT 13
14
15

18
Contents
19
BillingID M 6.5.2.16 a 20
21
MSCID M 6.5.2.82 b
22
MSID M 6.5.2.bv c 23
ActionCode O 6.5.2.2 d 24
25
AnnouncementList O 6.5.2.6 e
26
DisplayText O 6.5.2.bx f 27
DMH_AccountCodeDigits O 6.5.2.59 g 28
29
DMH_AlternateBillingDigits O 6.5.2.60 g
30
DMH_BillingDigits O 6.5.2.61 g 31
DMH_RedirectionIndicator O 6.5.2.62 g, h 32
33
ElectronicSerialNumber O 6.5.2.63 i, j
34
MobileDirectoryNumber O 6.5.2.80 k 35
36
PreferredLanguageIndicator O 6.5.2.96 l, m
37
TerminationList O 6.5.2.156 n 38
TriggerAddressList O 6.5.2.de h 39
40
Notes: 41
42
a. Include to identify the call. 43
44
b. Include to identify the initiating network entity.
45
c. Include to identify the subscriber. 46
47
d. Include if action to be performed is not implied through presence of other 48
parameters. 49
50
e. Include if provision of one or more tones or announcements is required.
51
f. Include if display information is to be presented to the MS. 52

53
g. Include if applicable and for recording purposes (see DMH). 54
55
h. The use of this parameter is for further study. 56
57
i. Include if available.
58
j. Include to identify the MS. 59

60
CallControlDirective 5-38 TIA/EIA-41.5-D Modifications

PN-4287
1
k. Include if available for recording purposes (see DMH).
2
3 l. Include if applicable.
4
5 m. This parameter may only be included if the AnnouncementList parameter is
6 present.
7
8
n. Include if call routing is required.
9
10 The CallControlDirective operation success is reported with a TCAP RETURN RESULT
12 as follows:
13
14
Table z-2 CallControlDirective RETURN RESULT Parameters
15
16 CallControlDirective RETURN RESULT Parameters
17
18
21
Contents
22
23 CallStatus O 6.5.2.en a
24
25 Notes:
26
a. Include if applicable to report call status.
27
28
29
30
31
32
33
34
35
36
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.5-D Modifications 5-39 CallControlDirective

PN-4287
1
6.4.2.aa OAnswer
2
3
4
The OAnswer (OANSWER) operation is used by the MSC to provide notification to a
5
service logic network entity that a trigger criteria at the O_Answer DP has been satisfied.
6
Service logic may then invoke a service or services.
7
The OAnswer operation is initiated with a TCAP INVOKE (LAST). This is carried by a 8
TCAP UNIDIRECTIONAL package. The Parameter Set is encoded as follows: 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
OAnswer 5-40 TIA/EIA-41.5-D Modifications

PN-4287
1
Table aa-1 OAnswer INVOKE Parameters
2
3 OAnswer INVOKE Parameters
4
5
7
8
9
Contents
11
ElectronicSerialNumber M 6.5.2.63 b
12
13 MSCID (Originating) M 6.5.2.82 c
14 MSID M 6.5.2.bv d
15
TimeDateOffset M 6.5.2.dd e
16
17 TimeOfDay M 6.5.2.em f
18 TriggerType M 6.5.2.dh g
19
LocationAreaID O 6.5.2.77 h, i
20
21 MobileDirectoryNumber O 6.5.2.80 j
22
FeatureIndicator O 6.5.2.ej k
23
24
MSCIdentificationNumber O 6.5.2.83 l
25 ServingCellID O 6.5.2.117 h, m
26
27
28
29
Notes:
30 a. Include to identify the call.
31
32
b. Include to identify the subscriber.
33
c. Include to identify the requesting MSC.
34
35 d. Include to identify MS.
36
37 e. Include to indicate the time offset of Local Civil Time with respect to
39
40
f. Include to indicate the time of day in UTC.
41
g. Include to identify the trigger encountered.
42
43 h. Include if applicable.
44
45 i. Include if the current location area information is available.
46
j. Include if available for recording purposes (see DMH).
47
48 k. Include to identify a feature invoked for the call (e.g., Three-Way Calling).
49
50 l. Include to identify the MSC initiating the message.
51
52
m. Include if the current serving cell identity is available.
53
54
55
56
57
58
59
60
TIA/EIA-41.5-D Modifications 5-41 OAnswer

PN-4287
1
6.4.2.ab ODisconnect
2
3
4
The ODisconnect (ODISCONNECT) operation is used by the MSC to provide
5
notification to a service logic network entity that a trigger criteria at the O_Disconnect
6
DP has been satisfied. Service logic may then invoke a service or services.
7
The ODisconnect operation is initiated with a TCAP INVOKE (LAST). This is carried 8
by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as 9
follows: 10
11
12
Table ab-1 ODisconnect INVOKE Parameters
13
ODisconnect INVOKE Parameters Timer: ODT 14
15
16

19
Contents
20
BillingID (Originating) M 6.5.2.16 a 21
22
23
MSCID (Originating) M 6.5.2.82 c 24
MSID M 6.5.2.bv d 25
26
ReleaseCause M 6.5.2.el e
27
TimeDateOffset M 6.5.2.dd f 28
TimeOfDay M 6.5.2.em g 29
30
31
WINCapability M 6.5.2.di 32
TriggerType M 6.5.2.dh h 33
34
LocationAreaID O 6.5.2.77 i, j
35
MobileDirectoryNumber O 6.5.2.80 k 36
37
MSCIdentificationNumber O 6.5.2.83 l
38
ServingCellID O 6.5.2.117 i, m 39
SystemMyTypeCode O 6.5.2.147 40
41
Notes: 42
43
45
46
c. Include to identify the requesting MSC. 47
48
d. Include to identify MS. 49
50
e. Include to identify the call release cause.
51
f. Include to indicate the time offset of Local Civil Time with respect to 52

54
g. Include to indicate the time of day in UTC. 55
56
h. Include to identify the trigger encountered. 57
58
i. Include if applicable.
59
60
ODisconnect 5-42 TIA/EIA-41.5-D Modifications

PN-4287
1
j. Include if the current location area information is available.
2
3 k. Include if available for recording purposes (see DMH).
4
5 l. Include to identify the MSC initiating the message.
6
7
m. Include if the current serving cell identity is available.
8
9 The ODisconnect operation success is reported with a TCAP RETURN RESULT
11 as follows:
12
13
Table ab-2 ODisconnect RETURN RESULT Parameters
14
15 ODisconnect RETURN RESULT Parameters
16
17
20
Contents
21
22 AnnouncementList O 6.5.2.6 a
23
DMH_ServiceID O 6.5.2.ei b
24
25
Notes:
26
27 a. Include if one or more tones or announcements is to be applied to the calling
28 party.
29
30
b. Include for recording purposes if a WIN service was invoked.
31
32
33
34
35
36
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.5-D Modifications 5-43 ODisconnect

PN-4287
1
6.4.2.ac CallRecoveryReport
2
3
4
The CallRecoveryReport (CRREPORT) operation is used by an MSC to report the call
5
recovery data requested.
6
The CallRecoveryReport operation is initiated with a TCAP INVOKE (LAST). This is 7
carried by a TCAP CONVERSATION WITHOUT PERMISSION package. The 8
Parameter Set is encoded as follows: 9
10
11
Table ac-1 CallRecoveryReport INVOKE Parameters
12
CallRecoveryReport INVOKE Parameters Timer: RQDT 13
14
15

18
Contents
19
CallRecoveryIDList M 6.5.2.eh a 20
21
Notes: 22
23
a. Include to identify call data.
24
25
The CallRecoveryReport operation success is reported with a TCAP RETURN RESULT 26
(LAST). This is carried by a TCAP CONVERSATION WITH PERMISSION package. 27
The Parameter Set is encoded as follows: 28
29
Table ac-2 CallRecoveryReport RETURN RESULT Parameters 30

31
CallRecoveryReport RETURN RESULT Parameters 32
33
34

37
Contents
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
RequestedData 5-44 TIA/EIA-41.5-D Modifications

PN-4287
1
6.4.2.ad TAnswer
2
3
4
The TAnswer (TANSWER) operation is used by the MSC to provide notification to a
5
service logic network entity that a trigger criteria at the T_Answer DP has been satisfied.
6
Service logic may then invoke a service or services.
7
8 The TAnswer operation is initiated with a TCAP INVOKE (LAST). This is carried by a
9 TCAP UNIDIRECTIONAL package. The Parameter Set is encoded as follows:
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41.5-D Modifications 5-45 TAnswer

PN-4287
1
Table ad-1 TAnswer INVOKE Parameters
2
TAnswer INVOKE Parameters 3
4
5
7
8
Contents 9
BillingID (Originating) M 6.5.2.16 a 10
11
12
MSCID M 6.5.2.82 c 13
MSID M 6.5.2.bv b 14
15
TimeDateOffset M 6.5.2.dd d
16
TimeOfDay M 6.5.2.em e 17
TransactionCapability M 6.5.2.160 18
19
TriggerType M 6.5.2.dh f
20
WINCapability M 6.5.2.di 21
22
LocationAreaID O 6.5.2.77 g, h
23
MobileDirectoryNumber O 6.5.2.80 i 24
FeatureIndicator O 6.5.2.ej j 25
26
MSCIdentificationNumber O 6.5.2.83 k
27
ServingCellID O 6.5.2.117 g, l 28
SystemMyTypeCode O 6.5.2.147 29
30
TerminationAccessType O 6.5.2.155 m
31
32
Notes: 33
35
b. Include to identify MS. 36
37
38
d. Include to indicate the time offset of Local Civil Time with respect to 39

41
e. Include to indicate the time of day in UTC. 42
43
f. Include to identify the trigger encountered. 44
45
g. Include if applicable.
46
h. Include if the current location area information is available. 47

48
50
j. Include to identify a feature invoked for the call (e.g., Three-Way Calling). 51
52
k. Include to identify the MSC sending the message.
53
l. Include if the current serving cell identity is available. 54
55
m. Include if call involves a special access situation (e.g., Roamer port access). 56
57
58
59
60
TAnswer 5-46 TIA/EIA-41.5-D Modifications

PN-4287
1
6.4.2.ae TDisconnect
2
3
4
The TDisconnect (TDISCONNECT) operation is used by the MSC to provide
5
notification to a service logic network element that a trigger criteria at the T_Disconnect
6
DP has been satisfied. Service logic may then invoke a service or services.
7
8 The TDisconnect operation is initiated with a TCAP INVOKE (LAST). This is carried
9 by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as
10 follows:
11
12
Table ae-1 TDisconnect INVOKE Parameters
13
14 TDisconnect INVOKE Parameters Timer: TDT
15
16
19
Contents
20
22
23
24
MSCID M 6.5.2.82 c
25 MSID M 6.5.2.bv d
26
TimeDateOffset M 6.5.2.dd e
27
28 TimeOfDay M 6.5.2.em f
29 TriggerType M 6.5.2.dh g
30
LocationAreaID O 6.5.2.77 h, i
31
32 MobileDirectoryNumber O 6.5.2.80 j
33 MSCIdentificationNumber O 6.5.2.83 k
34
ReleaseCause O 6.5.2.el l
35
36 ServingCellID O 6.5.2.117 h, m
37
38
39
Notes:
40
41 a. Include to identify the call.
42
43
44
45
46 d. Include to identify MS.
47
48 e. Include to indicate the time offset of Local Civil Time with respect to
50
f. Include to indicate the time of day in UTC.
51
52 g. Include to identify the trigger encountered.
53
54 h. Include if applicable.
55
56
i. Include if the current location area information is available.
57
j. Include if available for recording purposes (see DMH).
58
59 k. Include to identify the MSC initiating the message.
60
TIA/EIA-41.5-D Modifications 5-47 TDisconnect

PN-4287
1
l. Include to identify the call release cause.
2
m. Include if the current serving cell identity is available. 3

4
5
The TDisconnect operation success is reported with a TCAP RETURN RESULT 6
(LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded 7
as follows: 8
9
Table ae-2 TDisconnect RETURN RESULT Parameters 10
11
TDisconnect RETURN RESULT Parameters
12
14
15
Contents 17
18
DMH_ServiceID O 6.5.2.ei a
19
20
Notes: 21
a Include for recording purposes if a WIN service was invoked. 22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TDisconnect 5-48 TIA/EIA-41.5-D Modifications

PN-4287
1
6.4.2.af UnreliableCallData
2
3
4
The UnreliableCallData (UNRELCALLDATA) operation is used to notify an MSC that
5
an SCF network entity has experienced a failure that has rendered its call data unreliable.
6
7 The UnreliableCallData operation is initiated with a TCAP INVOKE (LAST). This is
10
11
Table af-1 UnreliableCallData INVOKE Parameters
12
13 UnreliableCallData INVOKE Parameters Timer: URCDT
14
15
18
Contents
19
20 ControlNetworkID M 6.5.2.ek a
21
MSCID M 6.5.2.82 b
22
23
Notes:
24
25 a. Include to identify the SCF network entity that experienced the failure.
26
27
b. Include to identify the initiating SCF network entity.
28
29 The UnreliableCallData operation success is reported with a TCAP RETURN RESULT
31 as follows:
32
33
Table af-2 UnreliableCallData RETURN RESULT Parameters
34
35 UnreliableCallData RETURN RESULT Parameters
36
37
40
Contents
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41.5-D Modifications 5-49 UnreliableCallData

PN-4287
6.5 MAP PARAMETERS 2

3
4
5
6
7
6.5.1.2 Parameter Identifiers 8
(TIA/EIA-41.5-D, page 5-119) 9
10
Table 112 TIA/EIA-41 MAP Parameter Identifiers 11
12
Parameter Identifier Name Parameter Identifier Code Reference
13
H G F E D C B A
14
CallRecoveryID 1 0 1 1 1 1 1 1 6.5.2.eg 15
1 0 0 0 0 0 1 0 16
0 0 1 0 1 1 1 1 17
18
CallRecoveryIDList 1 0 1 1 1 1 1 1 6.5.2.eh
19
1 0 0 0 0 0 1 0
20
0 0 1 1 0 0 0 0
21
DMH_ServiceID 1 0 0 1 1 1 1 1 6.5.2.ei 22
1 0 0 0 0 0 1 0 23
0 0 1 1 0 0 0 1 24
25
FeatureIndicator 1 0 0 1 1 1 1 1 6.5.2.ej
26
1 0 0 0 0 0 1 0
27
0 0 1 1 0 0 1 0
28
ControlNetworkID 1 0 0 1 1 1 1 1 6.5.2.ek 29
1 0 0 0 0 0 1 0 30
0 0 1 1 0 0 1 1 31
ReleaseCause 1 0 0 1 1 1 1 1 6.5.2.el 32
1 0 0 0 0 0 1 0 33
0 0 1 1 0 1 0 0 34
35
TimeOfDay 1 0 0 1 1 1 1 1 6.5.2.em 36
1 0 0 0 0 0 1 0 37
0 0 1 1 0 1 0 1 38
CallStatus 1 0 0 1 1 1 1 1 6.5.2.en 39
1 0 0 0 0 0 1 0 40
0 0 1 1 0 1 1 0 41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Parameter Identifiers 5-50 TIA/EIA-41.5-D Modifications

PN-4287
1
2 6.5.2 Parameter Definitions
3
4
5
6
7 6.5.2.2 ActionCode
8 (TIA/EIA-41.5-D, page 5-129)
9
10
The ActionCode (ACTCODE) parameter specifies the nature of the action (e.g.,
11
disconnect the call) to be performed by the designated functional entity.
12
13
14 Identifier ActionCode M 6.5.1.2
15 IMPLICIT OCTET STRING
16
17
18 Contents
19 H G F E D C B A octet Notes
20
21
Action
22 ••• n a
23
24 Figure 9 ActionCode parameter
25
26 Notes:
27
a. Ignore extra octets, if received. Send only defined (or significant) octets.
28
29
30
Table 114 ActionCode value
31
32
33
Action (octet 1)
34 Bits H G F E D C B A Value Meaning
35
••••
36
0 0 0 1 0 1 0 0 20 Release leg and redirect subscriber.
37
38
0 0 0 1 0 1 0 1 21
39 Reserved. Treat the same as value 1, Continue
••• through processing.
40
0 1 0 1 1 1 1 1 95
41
42 0 1 1 0 0 0 0 0 96 Reserved for TIA/EIA-41 protocol extension. If
43 ••• through unknown, treat the same as value 1, Continue
44 0 1 1 1 1 1 1 1 127 processing.
45
46 1 0 0 0 0 0 0 0 128
Reserved. Treat the same as value 2, Disconnect
47 ••• through
call.
48 1 1 0 1 1 1 1 1 223
49
50 1 1 1 0 0 0 0 0 224 Reserved for TIA/EIA-41 protocol extension. If
51 ••• through unknown, treat the same as value 2, Disconnect
52 1 1 1 1 1 1 1 1 255 call.
53
54
55
56
57
58
59
60
TIA/EIA-41.5-D Modifications 5-51 ActionCode

PN-4287
1
6.5.2.5 AnnouncementCode 2
3
(TIA/EIA-41.5-D, page 5-133)
4
The AnnouncementCode (ANNCODE) parameter specifies the announcement or tone to 5
be given to a designated party. 6
7
9
Identifier AnnouncementCode M 6.5.1.2
10
IMPLICIT OCTET STRING
11
Length variable octets M 6.5.1.1 a 12
Contents 13
14
H G F E D C B A octet Notes
15
Tone 1 b, c 16
17
Reserved Class 2 d
18
Standard Announcement 3 19
Custom Announcement 4 e 20
21
••• n f
22
23
Figure 12 AnnouncementCode parameter
24
25
Notes: 26
a. The length is variable with more specific requests in the later octets. The 27
minimum length is one octet. 28
29
b. The tone is applied if an announcement is not specified or if the specified 30
announcement is not available. 31
32
c. This is based on the ANSI T1.607 (Q.931) Signal parameter and includes
33
“network specific values” [N-ISDN]. It should not be used for alerting purposes;
34
use the AlertCode instead.
35
d. Reserved bits shall be ignored on receipt and set to zero on sending. 36

37
e. The assignment of this octet is left to bilateral agreement. When a Custom 38
Announcement is specified it takes precedence over either the Standard 39
Announcement or Tone. 40
41
f. Ignore extra octets, if received. Send only defined (or significant) octets. 42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
AnnouncementCode 5-52 TIA/EIA-41.5-D Modifications

PN-4287
1
Table 117 AnnouncementCode value
2
3
4
Tone (octet 1)
6
0 0 0 0 0 0 0 0 0 DialTone. A continuous 350 Hz tone added to a
7
440 Hz tone.
8
0 0 0 0 0 0 0 1 1 RingBack or AudibleAlerting. A 440 Hz tone
9 added to a 480 Hz tone repeated in a 2s on 4s off
10 pattern.
11 0 0 0 0 0 0 1 0 2 InterceptTone or MobileReorder. Alternating
12 440 Hz and 620 Hz tones, each on for 250 ms.
13 0 0 0 0 0 0 1 1 3 CongestionTone or ReorderTone. A 480 Hz
14 tone added to a 620 Hz tone repeated in a 250
15
ms on, 250 ms off cycle.
0 0 0 0 0 1 0 0 4 BusyTone. A 480 Hz tone added to a 620 Hz
16
tone repeated in a 500 ms on, 500 ms off cycle.
17
0 0 0 0 0 1 0 1 5 ConfirmationTone. A 350 Hz tone added to a
18
440 Hz tone repeated 3 times in a 100 ms on,
19 100 ms off cycle.
20 0 0 0 0 0 1 1 0 6 AnswerTone. Answer tone is not presently used
21 in North American networks.
22 0 0 0 0 0 1 1 1 7 CallWaitingTone. A single 300 ms burst of
23 440 Hz tone.
24 0 0 0 0 1 0 0 0 8 OffHookTone. Off-hook warning tone on.
25
0 0 0 1 0 0 0 1 17 RecallDialTone. Three bursts (0.1 s on, 0.1s
off) then steady on of dial tone. [N-ISDN]
26
0 0 0 1 0 0 1 0 18 BargeInTone. No information available.
27
[N-ISDN]
28
0 0 0 1 0 1 0 0 20 PPCInsufficientTone. Three bursts (100 ms on,
29
100 ms off) of 480 Hz tone.
30
0 0 0 1 0 1 0 1 21 PPCWarningTone1. A single 200 ms burst of
31
480 Hz tone.
32
0 0 0 1 0 1 1 0 22 PPCWarningTone2. Two bursts (100 ms on,
33
34
0 0 0 1 0 1 1 1 23 PPCWarningTone3. Three bursts (100 ms on,
35
36
0 0 0 1 1 0 0 0 24 PPCDisconnectTone. A single 400 ms burst of
37
480 Hz tone.
38
0 0 0 1 1 0 0 1 25 PPCRedirectTone. Two bursts of (200 ms on,
39
40
0 0 1 1 1 1 1 1 63 TonesOff. All tones off.
41 1 1 0 0 0 0 0 0 192 PipTone. Four bursts of (0.1 s on, 0.1 s off) of
42 480 Hz tone, then off. [TIA/EIA-664]
43 1 1 0 0 0 0 0 1 193 AbbreviatedIntercept. 4 seconds of Intercept-
44 Tone. [CDMA]
45 1 1 0 0 0 0 1 0 194 AbbreviatedCongestion. 4 seconds of
46 CongestionTone. [CDMA]
47
1 1 0 0 0 0 1 1 195 WarningTone. A single 0.1 s burst of 480 Hz
tone. [TIA/EIA-664]
48
1 1 0 0 0 1 0 0 196 DenialToneBurst. A single 2.0 s burst of 480
49
Hz tone added to a 620 Hz tone. [TIA/EIA-664]
50
1 1 0 0 0 1 0 1 197 DialToneBurst. A single 2.0 s burst of
51 DialTone. [TIA/EIA-664]
52 1 1 1 1 1 0 1 0 250 IncomingAdditionalCallTone. No information
53 available. [N-ISDN]
54 1 1 1 1 1 0 1 1 251 PriorityAdditionalCallTone. No information
55 available. [N-ISDN]
56 X X X X X X X X Other values are reserved. Treat the same as
57
value 63, TonesOff.
58
59
60
TIA/EIA-41.5-D Modifications 5-53 AnnouncementCode

PN-4287
1
Table 117 (continued)
2
3
Class (octet 2, bits A-D) 4
Bits H G F E D C B A Value Meaning 5
6
0 0 0 0 0 Concurrent. Play announcements concurrently
7
with any call routing.
8
0 0 0 1 1 Sequential. Play all announcements before any
call termination or routing. 9
10
0 0 1 0 2 11
••• through Reserved. Treat the same as value 0, Concurrent. 12
0 1 1 1 7 13
14
1 0 0 0 8 15
••• through Reserved. Treat the same as value 1, Sequential. 16
1 1 1 1 15 17
18
Standard Announcement (octet 3) 19
21
0 0 0 0 0 0 0 0 0 None. No announcement is requested, just play 22
the tone.
23
0 0 0 0 0 0 0 1 1 UnauthorizedUser. (e.g., “Your cellular
24
telephone’s serial number has been restricted
25
from this service area. If you feel this is an error,
please contact your home cellular provider.”) 26
0 0 0 0 0 0 1 0 2 InvalidESN. (e.g., “You cannot make a call 27

because of conflicting serial number data. Please 28
call your customer service representative by 29
dialing (*) 611.”) 30
0 0 0 0 0 0 1 1 3 UnauthorizedMobile. An MS attempts to 31
originate a call for an unauthorized subscriber. 32
(e.g., “There is no service agreement between
33
the serving service provider and the home
34
service provider.”)
35
0 0 0 0 0 1 0 0 4 SuspendedOrigination. (e.g., “Your service has
been temporarily disconnected. For more 36
information, call your customer service 37

representative by dialing (*) 611.”) 38
0 0 0 0 0 1 0 1 5 OriginationDenied. The subscriber attempted 39
to originate a call that is denied by its service 40
profile. (e.g., “You cannot make a call from this 41
cellular telephone. You can only receive calls 42
with your type of service.”)
43
0 0 0 0 0 1 1 0 6 ServiceAreaDenial. The subscriber attempted a
44
call that is not permitted in the current service
45
area. (e.g., “You cannot make that call from this
service area. For more information, call your 46
customer service representative by dialing (*) 47

611.”) 48
0 0 0 1 0 0 0 0 16 PartialDial. The subscriber dialed insufficient 49
digits to complete routing. The Reorder SIT may 50
apply. Alternatively reorder tone may apply. 51
(e.g., “Your call cannot be completed as dialed. 52
Please try your call again.”) [NoLECN]
53
0 0 0 1 0 0 0 1 17 Require1Plus. The subscriber dialed a toll
54
network without dialing a ‘1’ digit prefix. (e.g.,
55
“It is necessary to first dial a one when calling
this number. Please try your call again.”) 56
57
58
59
60

PN-4287
1
2
3 0 0 0 1 0 0 1 0 18 Require1PlusNPA. A roaming subscriber
4
attempted to dial a seven-digit call that is likely
to be a toll call, but the call is not permitted.
5
(e.g., “It is necessary to dial a one plus the area
6
code and phone number of the party you are
7
calling when calling from this service area.
8 Please try your call again.”) [TIA/EIA-660]
9 0 0 0 1 0 0 1 1 19 Require0Plus. (e.g., “It is not possible to
10 provide toll service at this time. You may place
11 credit card, collect or third party long distance
12 calls by dialing “0”, area code and number.
13 Please try your call again.”)
14
0 0 0 1 0 1 0 0 20 Require0PlusNPA. (e.g., “It is necessary to first
dial a zero plus the area code and phone number
15
of the party you are calling to complete a long
16
distance call from this service area. Please try
17
your call again.”)
18 0 0 0 1 0 1 0 1 21 Deny1Plus. The subscriber dialed a local
19 number prefixed with a ‘1’ digit. (e.g., “It is not
20 necessary to dial a one when calling this
21 number. Please try your call again.”)
22 [TIA/EIA-660]
23 0 0 0 1 0 1 1 0 22 Unsupported10plus. (e.g., “Long distance
24
carrier access codes are not supported on this
system.”)
25
0 0 0 1 0 1 1 1 23 Deny10plus. (e.g., “You are not authorized to
26
dial long distance access codes.”) [TIA/EIA-660]
27
0 0 0 1 1 0 0 0 24 Unsupported10XXX. (e.g., “The long distance
28 access code you have dialed is not accessible on
29 this system. Please call your long distance
30 provider’s customer service number for
31 assistance.”) [TIA/EIA-660]
32 0 0 0 1 1 0 0 1 25 Deny10XXX. (e.g., “The long distance access
33 code you have dialed is not authorized on this
34
system.”) [TIA/EIA-660]
0 0 0 1 1 0 1 0 26 Deny10XXXLocally. (e.g., “A carrier access
35
code is not required for the number you have
36
dialed. Please try your call again without the
37
carrier access code.”)
38 0 0 0 1 1 0 1 1 27 Require10Plus. (e.g., “A carrier access code is
39 required for the number you have dialed. Please
40 dial the call again with the carrier access code.”)
41 [NoLECN]
42 0 0 0 1 1 1 0 0 28 RequireNPA. (e.g., “While roaming on this
43 system, you are required to include the area code
44
of the number you are calling to complete local
calls.”)
45
0 0 0 1 1 1 0 1 29 DenyTollOrigination. The subscriber attempted
46
a toll call that is not permitted by its service
47
profile. (e.g., “At the present time we are not
48 able to offer toll service to roamers.”)
49 [TIA/EIA-41]
50 0 0 0 1 1 1 1 0 30 DenyInternationalOrigination. The subscriber
51 attempted an international call that is not
52 permitted by its service profile. (e.g., “At the
53 present time we are not able to offer
54
international service to roamers. You may place
credit card calls by dialing “0” and the
55
appropriate access code and phone number.”)
56
[TIA/EIA-41]
57
58
59
60

PN-4287
1
2
0 0 0 1 1 1 1 1 31 Deny0Minus. The subscriber attempted to dial a 3
0- call that is not permitted by its service profile. 4
(e.g., “At the present time we are not able to
5
offer operator services.”)
6
0 0 1 1 0 0 0 0 48 DenyNumber. (e.g., “Your service does not
7
allow calls to the number you have dialed. For
more information please call your customer 8
service representative by dialing (*) 611.”) 9

[TIA/EIA-41] 10
0 0 1 1 0 0 0 1 49 AlternateOperatorServices. (e.g., “Your call is 11
being processed by a cellular operator service. 12
Use of a credit or calling card is required.”) 13
0 1 0 0 0 0 0 0 64 N o C i r c u i t or AllCircuitsBusy or 14
FacilityProblem. There are no available
15
outgoing trunks (or other facilities) for the
16
terminating route. The No Circuit SIT may
17
apply. Alternatively reorder tone may apply.
(e.g., All circuits are busy now. Please try again 18
later.”) 19
0 1 0 0 0 0 0 1 65 Overload. There are no available outgoing 20
trunks (or other facilities) for the terminating 21
route due to heavy calling. (e.g., “All circuits are 22
busy now due to heavy calling. Please try again 23
later. If your call is urgent, please try again 24
now.”) [T1.209]
25
0 1 0 0 0 0 1 0 66 InternalOfficeFailure. The Reorder SIT may
26
apply. Alternatively reorder tone may apply.
27
(e.g., “Your call did not go through. Please try
again later.”) [NoLECN] 28
0 1 0 0 0 0 1 1 67 NoWinkReceived. The Reorder SIT may apply. 29

Alternatively reorder tone may apply. (e.g., 30
“Your call did not go through. Please try again 31
later.”) [NoLECN] 32
0 1 0 0 0 1 0 0 68 InterofficeLinkFailure. The Reorder SIT may 33
apply. Alternatively reorder tone may apply. 34
(e.g., “Your call did not go through. Please try
35
again later.”) [NoLECN]
36
0 1 0 0 0 1 0 1 69 Vacant. The subscriber dialed an unassigned
37
area code, office code, X11 service code, out-of-
area call, or country code. The Vacant Code SIT 38
may apply. (e.g., “Your call cannot be 39

completed as dialed. Please check the number 40
and dial again.”) [NoLECN] 41
0 1 0 0 0 1 1 0 70 InvalidPrefix or InvalidAccessCode. The 42
Ineffective Order SIT may apply. (e.g., “Your 43
call cannot be completed as dialed. Please check 44
the number and dial again.”) [NoLECN]
45
0 1 0 0 0 1 1 1 71 OtherDialingIrregularity. The Ineffective
46
Order SIT may apply. (e.g., “Your call cannot be
47
completed as dialed. Please check the number
and dial again.”) [NoLECN] 48
0 1 0 1 0 0 0 0 80 VacantNumber or DisconnectedNumber. The 49

Intercept SIT may apply. (e.g., “You have 50
reached a number that has been disconnected or 51
is no longer in service. If you feel you have 52
reached this recording in error, please check the 53
number and try again.”) [NoLECN] 54
55
56
57
58
59
60

PN-4287
1
2
3 0 1 0 1 0 0 0 1 81 DenyTermination. The Intercept SIT may
4
apply. Calls to the dialed number are denied by
its service profile. (e.g., “The number you have
5
dialed does not accept incoming calls.”)
6
[TIA/EIA-41]
7
0 1 0 1 0 0 1 0 82 SuspendedTermination. The called party has
8 been temporarily disconnected. The Intercept
9 SIT may apply. (e.g., “The number you have
10 called has temporarily been disconnected.”)
11 [NoLECN]
12 0 1 0 1 0 0 1 1 83 ChangedNumber. The Intercept SIT may
13 apply. (e.g., “The number you have reached
14
(NPA) NXX-XXXX has been changed. The new
number is (NPA) NXX-XXXX. Please make
15
note of it.”) [NoLECN]
16
0 1 0 1 0 1 0 0 84 InaccessibleSubscriber. The Ineffective Order
17
SIT may apply. (e.g., “The customer you have
18 called is not accessible. Please try your call
19 again later.”) [TIA/EIA-41]
20 0 1 0 1 0 1 0 1 85 DenyIncomingToll. A call to an MS, involving
21 subscriber paid toll (e.g., Call Delivery, Call
22 Forwarding, etc.), is not permitted by its service
23 profile.) The Ineffective Order SIT may apply.
24
(e.g., “The customer you have called is not
accessible. Please try your call again later.”)
25
0 1 0 1 0 1 1 1 86 RoamerAccessScreening. The subscriber called
26
via a roamer port is either outside the roamer
27
port calling area or is forwarded to a number
28 outside the roamer port calling area. The
29 Ineffective Order SIT may apply. (e.g., “You
30 have reached a mobile subscriber that cannot be
31 reached through this roamer port. Please try to
32 dial the subscriber number directly.”)
33 0 1 0 1 0 1 1 1 87 RefuseCall. The calling party has been refused
34
by has permanent or temporary screening of
incoming calls. The Intercept SIT may apply.
35
(e.g., “The number you have dialed does not
36
accept incoming calls.”)
37
0 1 0 1 1 0 0 0 88 RedirectCall. (e.g., “Your call is being
38 forwarded. Please wait.”) [TIA/EIA-41]
39 0 1 0 1 1 0 0 1 89 NoPageResponse. (e.g., “Your call cannot be
40 completed at this time. Please try your call again
41 later.”) [TIA/EIA-41]
42 0 1 0 1 1 0 1 0 90 NoAnswer. The called subscriber has not
43 answered and the alerting has been discontinued.
44
(e.g., “The customer you have called does not
answer. Please try your call again later.”)
45
0 1 1 0 0 0 0 0 96 RoamerIntercept. A subscriber has roamed into
46
a service area requiring activation. (e.g., “If you
47
are interested in using cellular service, call #.”)
48 0 1 1 0 0 0 0 1 97 GeneralInformation. (e.g., “If you need
49 assistance using your service features please call
50 your service representative by dialing (*) 611.”)
51 0 1 1 1 0 0 0 0 112 UnrecognizedFeatureCode. The subscriber
52 dialed an unrecognized feature code. (e.g., “The
53 feature code you have dialed is not valid. Please
54
check the code and enter it again.”)
[TIA/EIA-664]
55
56
57
58
59
60

PN-4287
1
2
0 1 1 1 0 0 0 1 113 UnauthorizedFeatureCode. The subscriber 3
dialed a recognized, but unauthorized, feature 4
code. (e.g., “Your service does not include use
5
of this feature. For more information please call
6
your customer service representative by dialing
7
(*) 611.”) [TIA/EIA-664]
0 1 1 1 0 0 1 0 114 RestrictedFeatureCode. The subscriber dialed 8
a feature code which is not available in his or 9

her current service area. (e.g., “The feature code 10
you have dialed is not available in your service 11
area.”) 12
0 1 1 1 0 0 1 1 115 InvalidModifierDigits. The subscriber 13
attempted to activate a feature with invalid 14
modifier digits. (e.g., “The modifier digits you
15
have dialed is not valid. Please check the
16
number and try again.”)
17
0 1 1 1 0 1 0 0 116 SuccessfulFeatureRegistration. (e.g., “The
feature you have selected has been registered.”) 18
[TIA/EIA-664] 19
0 1 1 1 0 1 0 1 117 SuccessfulFeatureDeRegistration. (e.g., “The 20
feature you have selected has been de- 21
registered.”) [TIA/EIA-664] 22
0 1 1 1 0 1 1 0 118 SuccessfulFeatureActivation. (e.g., “The 23
feature you have selected has been activated.”) 24
[TIA/EIA-664]
25
0 1 1 1 0 1 1 1 119 SuccessfulFeatureDeActivation. (e.g., “The
26
feature you have selected has been de-
27
activated.”) [TIA/EIA-664]
0 1 1 1 1 0 0 0 120 InvalidForwardToNumber. (e.g., “The 28
telephone number you have entered is not valid. 29

Please try again.”) 30
0 1 1 1 1 0 0 1 121 CourtesyCallWarning. The subscriber has 31
dialed a feature code involving a courtesy call. 32
(e.g., “Please wait while your call is 33
forwarded.”) 34
1 0 0 0 0 0 0 0 128 EnterPINSendPrompt. (e.g., “Please enter
35
your PIN number and depress the SEND key.”)
36
[TIA/EIA-664]
37
1 0 0 0 0 0 0 1 129 EnterPINPrompt. (e.g., “Please enter your
PIN.”) [TIA/EIA-664] 38
1 0 0 0 0 0 1 0 130 ReEnterPINSendPrompt. (e.g., “Please re- 39

enter your PIN number and depress the SEND 40
key.”) [TIA/EIA-664] 41
1 0 0 0 0 0 1 1 131 ReEnterPINPrompt. (e.g., “Please re-enter 42
your PIN.”) [TIA/EIA-664] 43
1 0 0 0 0 1 0 0 132 EnterOldPINSendPrompt. (e.g., “Please enter 44
your old PIN number and depress the SEND
45
key.”) [TIA/EIA-664]
46
1 0 0 0 0 1 0 1 133 EnterOldPINPrompt. (e.g., “Please enter your
47
old PIN.”) [TIA/EIA-664]
1 0 0 0 0 1 1 0 134 EnterNewPINSendPrompt. (e.g., “Please enter 48
your new PIN number and depress the SEND 49

key.”) [TIA/EIA-664] 50
1 0 0 0 0 1 1 1 135 EnterNewPINPrompt. (e.g., “Please enter your 51
new PIN.”) [TIA/EIA-664] 52
1 0 0 0 1 0 0 0 136 ReEnterNewPINSendPrompt. (e.g., “Please 53
re-enter your new PIN number and depress the 54
SEND key.”) [TIA/EIA-664]
55
1 0 0 0 1 0 0 1 137 ReEnterNewPINPrompt. (e.g., “Please re-
56
enter your new PIN.”) [TIA/EIA-664]
57
58
59
60

PN-4287
1
Table 117 (concluded)
2
3 1 0 0 0 1 0 1 0 138 EnterPasswordPrompt. (e.g., “Please enter
4
your secret password number to access the
called party.”) [TIA/EIA-664]
5
1 0 0 0 1 0 1 1 139 EnterDirectoryNumberPrompt. (e.g., “Please
6
enter your directory number.”) [TIA/EIA-664]
7
1 0 0 0 1 1 0 0 140 ReEnterDirectoryNumberPrompt. (e.g.,
8 “Please re-enter your directory number.”)
9 [TIA/EIA-664]
10 1 0 0 0 1 1 0 1 141 EnterFeatureCodePrompt. (e.g., “Please enter
11 a feature code.”) [TIA/EIA-664]
12 1 0 0 1 1 0 0 0 152 PPCInsufficientAccountBalance. The
13 subscriber account balance is not sufficient to
14 complete this call (e.g., “Your Pre-paid balance
15 is too low to complete this call. Please replenish
16 your account.”)
17 1 0 0 1 1 0 0 1 153 PPCFiveMinuteWarning. The subscriber
18 account reaches a 5-minute low threshold
19 balance during the call (e.g., “You have five
20 minutes left in your account.”)
21 1 0 0 1 1 0 1 0 154 PPCThreeMinuteWarning. The subscriber
23 balance during the call (e.g., “You have three
25 1 0 0 1 1 0 1 1 155 PPCTwoMinuteWarning. The subscriber
27 balance during the call (e.g., “You have two
29 1 0 0 1 1 1 0 0 156 PPCOneMinuteWarning. The subscriber
31 balance during the call (e.g., “You have one
32 minute left in your account.”)
33 1 0 0 1 1 1 0 1 157 PPCDisconnect. This call will be disconnected.
34 (e.g., “This call will be disconnected. Please
35 replenish your account.”)
36 1 0 0 1 1 1 1 0 158 PPCRedirect. This call will be redirected. (e.g.,
37 “This call is being transferred to customer
38 service.”)
39 X X X X X X X X Other values are reserved. Treat the same as
40 value 0, None.
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
1
6.5.2.97 Profile 2
3
4
The Profile is a collection of the subscriber’s calling profile information. This 5
information is a list of optional parameters. The Profile macro has been defined solely for 6
editorial convenience, and does not affect the encoding in any way. 7
8
PROFILE 9
10
Type Reference Notes
11
Contents 12
13
AuthenticationCapability O 6.5.2.8 a
14
CallingFeaturesIndicator O 6.5.2.20 b 15
CarrierDigits O 6.5.2.28 c 16
17
ControlNetworkID O 6.5.2.ek u
18
DMH_AccountCodeDigits O 6.5.2.59 d 19
20
DMH_AlternateBillingDigits O 6.5.2.60 d
21
DMH_BillingDigits O 6.5.2.61 d 22
GeographicAuthorization O 6.5.2.68 e 23
24
MessageWaitingNotificationCount O 6.5.2.78 f
25
MessageWaitingNotificationType O 6.5.2.79 g 26
MobileDirectoryNumber O 6.5.2.80 d 27
28
OriginationIndicator O 6.5.2.89 h
29
OriginationTriggers O 6.5.2.90 i 30
PACAIndicator O 6.5.2.91 j 31
32
PreferredLanguageIndicator O 6.5.2.96 k
33
RestrictionDigits O 6.5.2.113 l 34
35
RoutingDigits O 6.5.2.114 m
36
SMS_OriginationRestrictions O 6.5.2.136 n 37
SMS_TerminationRestrictions O 6.5.2.138 o 38
39
SPINIPIN O 6.5.2.139 p
40
SPINITriggers O 6.5.2.140 q 41
TerminationRestrictionCode O 6.5.2.157 r 42
43
TerminationTriggers O 6.5.2.159 s
44
TriggerAddressList O 6.5.2.de t 45
46
Figure 105 Profile Macro 47
48
Notes: 49
a. Include on IS-41-C or later. 50

51
b. Include to identify feature authorization and activity. 52
53
c. Include if preferred carrier is applicable and TransactionCapability supported. 54
55
d. Include if available for recording purposes (see DMH).
56
e. Include if available for certain authorization restricted areas. 57

58
59
60
Profile 5-60 TIA/EIA-41.5-D Modifications

PN-4287
1
f. Include if MessageWaitingNotificationType is Message Waiting Indication and
2
number of messages waiting is authorized.
3
4 g. Include if Message Waiting Notification feature is active and a message is
5 waiting.
6
7 h. Include to indicate the type of calls allowed for origination service.
8
9
i. Include to indicate OriginationRequest triggers.
10
j. Include to identify the PACA feature.
11
12 k. Include to identify the Preferred Language feature.
13
14 l. Include if originations are restricted to NPA-NXX or NPA-NXX-XXXX and
15 TransactionCapability supported.
16
m. Include for special routing information.
17
18 n. Include for MS originated Short Message Service.
19
20 o. Include for MS terminated Short Message Service.
21
22
p. Include if local SPINI operation supported.
23
q. Include to indicate Subscriber PIN Intercept triggers.
24
25 r. Include to indicate the type of call termination service.
26
27 s. Include to indicate the RedirectionRequest or TransferToNumberRequest
28 triggers.
29
30
t. Include to indicate active WIN triggers and associated addresses for service
31
logic network elements.
32
u. Include to correlate call data for SCF data recovery.
33
34
35
36
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.5-D Modifications 5-61 Profile

PN-4287
1
6.5.2.df TriggerCapability 2
3
4
The TriggerCapability (TRIGCAP) parameter is used to specify the WIN Triggers of the 5
sending network element that can be armed by the TriggerAddressList parameter. 6
7
9
Identifier TriggerCapability M 6.5.1.2
10
11
Contents 13
14
15
Res’d. ODISC OANS OAA RvtC All K-digit INIT 1 a 16
17
Res’d. CdRAA IT CgRAA AT PA Unrec CT 2 a
18
Reserved TDISC TANS TNA TBusy TRA 3 a 19
20
••• n b
21
Figure df TriggerCapability parameter 22

23
24
Notes:
25
a. Reserved bits shall be ignored on receipt and set to zero on sending. 26
27
b. Ignore extra octets, if received. Send only defined (or significant) octets. 28
29
30
Table df TriggerCapability value 31
32
Introducing Star/Pound (INIT) (octet 1, bit A) 33
35
0 0 Introducing Star triggers and Introducing Pound 36
triggers cannot be armed by the
37
TriggerAddressList parameter.
38
1 1 Introducing Star triggers and Introducing Pound
39
triggers can be armed by the TriggerAddressList
parameter. 40
41
42
K-digit (K-digit) (octet 1, bit B) 43

45
0 0 K-digit triggers cannot be armed by the 46
TriggerAddressList parameter. 47
1 1 K - d i g i t triggers can be armed by the
48
49
50
All_Calls (All) (octet 1, bit C) 51

52
Bits H G F E D C B A Value Meaning
53
0 0 All_Calls trigger can not be armed by the 54
1 1 A l l _ C a l l s trigger can be armed by the 56
58
59
60
TriggerCapability 5-62 TIA/EIA-41.5-D Modifications

PN-4287
1
Table df TriggerCapability value (continued)
2
3
4
Revertive_Call (RvtC) (octet 1, bit D)
6
0 0 Revertive_Call trigger cannot be armed by the
7
8
1 1 Revertive_Call trigger can be armed by the
9 TriggerAddressList parameter.
10
11
12 Origination_Attempt_Authorized (OAA) (octet 1, bit E)
14
15 0 0 Origination_Attempt_Authorized trigger cannot
16 be armed by the TriggerAddressList parameter.
17 1 1 Origination_Attempt_Authorized trigger can be
18 armed by the TriggerAddressList parameter.
19
20
21 O_Answer (OANS) (octet 1, bit F)
23
24 0 0 O_Answer trigger cannot be armed by the
26 1 1 O_Answer trigger can be armed by the
28
29
30
O_Disconnect (ODISC) (octet 1, bit G)
32
33 0 0 O_Disconnect trigger cannot be armed by the
35 1 1 O_Disconnect trigger can be armed by the
37
38
39
Call Types (CT) (octet 2, bit A)
41
0 0 Call Type triggers cannot be armed by the
42
43
1 1 Call Type triggers can be armed by the
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41.5-D Modifications 5-63 TriggerCapability

PN-4287
1
Table df TriggerCapability value (continued)
2
3
Unrecognized_Number (Unrec) (octet 2, bit B) 4
6
0 0 Unrecognized_Number trigger cannot be armed
7
by the TriggerAddressList parameter.
8
1 1 Unrecognized_Number trigger can be armed by
the TriggerAddressList parameter. 9
10
11
Prior_Agreement (PA) (octet 2, bit C) 12

14
0 0 Prior_Agreement trigger cannot be armed by the 15
1 1 Prior_Agreement trigger can be armed by the
17
18
Advanced_Termination (AT) (octet 2, bit D) 19

20
21
0 0 Advanced_Termination trigger cannot be armed 22

by the TriggerAddressList parameter. 23
1 1 Advanced_Termination trigger can be armed by 24
the TriggerAddressList parameter. 25
26
27
Calling_Routing_Address_Available (CgRAA) (octet 2, bit E)
28
30
0 0 Calling_Routing_Address_Available trigger
31
cannot be armed by the TriggerAddressList
32
parameter.
33
1 1 Calling_Routing_Address_Available trigger can
34
be armed by the TriggerAddressList parameter.
35
36
37
Initial_Termination (IT) (octet 2, bit F)
38
40
0 0 Initial_Termination trigger cannot be armed by
41
the TriggerAddressList parameter.
42
1 1 Initial_Termination trigger can be armed by the
43
44
45
46
Called_Routing_Address_Available (CdRAA) (octet 2, bit G)
47
49
0 0 Called_Routing_Address_Available trigger
50
cannot be armed by the TriggerAddressList
51
parameter.
52
1 1 Called_Routing_Address_Available trigger can
53
54
55
56
57
58
59
60
TriggerCapability 5-64 TIA/EIA-41.5-D Modifications

PN-4287
1
Table df TriggerCapability value (concluded)
2
3
4
Terminating_Resource_Available (TRA) (octet 3, bit A)
6
0 0 Terminating_Resource_Available trigger cannot
7
8
1 1 Terminating_Resource_Available trigger can be
9 armed by the TriggerAddressList parameter.
10
11
12 T_Busy (TBusy) (octet 3, bit B)
14
15 0 0 T_Busy trigger cannot be armed by the
16
1 1 T_Busy trigger can be armed by the
17
18
19
20 T_No_Answer (TNA) (octet 3, bit C)
21
22
23 0 0 T_No_Answer trigger cannot be armed by the
25 1 1 T_No_Answer trigger can be armed by the
27
28
T_Answer (TANS) (octet 3, bit D)
29
31
0 0 T_Answer trigger cannot be armed by the
32
33
1 1 T _ A n s w e r trigger can be armed by the
34
35
36
37
T_Disconnect (TDISC) (octet 3, bit E)
38
39
40
0 0 T_Disconnect trigger cannot be armed by the
41
42
1 1 T_Disconnect trigger can be armed by the
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41.5-D Modifications 5-65 TriggerCapability

PN-4287
1
6.5.2.dh TriggerType 2
3
4
The TriggerType (TRIGTYPE) parameter identifies an individual trigger. 5
6
8
Identifier TriggerType M 6.5.1.2
9
IMPLICIT Unsigned Enumerated
10
Length 1 octet M 6.5.1.1 11
Contents 12
13
14
Trigger Type 1 15
16
Figure dh TriggerType parameter 17
18
Table dh Trigger Type value 19
20
Trigger Type (octet 1) 21

23
0 0 0 0 0 0 0 0 0 Unspecified 24
0 0 0 0 0 0 0 1 1 All_Calls.
25
0 0 0 0 0 0 1 0 2 Double_Introducing_Star.
26
0 0 0 0 0 0 1 1 3 Single_Introducing_Star.
27
0 0 0 0 0 1 0 0 4 Reserved [for Home_System_Feature_Code
(Note 1)] 28
0 0 0 0 0 1 0 1 5 Double_Introducing_Pound. 29
0 0 0 0 0 1 1 0 6 Single_Introducing_Pound. 30
0 0 0 0 0 1 1 1 7 Revertive_Call. 31
0 0 0 0 1 0 0 0 8 0_Digit. 32
0 0 0 0 1 0 0 1 9 1_Digit. 33
0 0 0 0 1 0 1 0 10 2_Digit. 34
0 0 0 0 1 0 1 1 11 3_Digit.
35
0 0 0 0 1 1 0 0 12 4_Digit.
36
0 0 0 0 1 1 0 1 13 5_Digit.
37
0 0 0 0 1 1 1 0 14 6_Digit.
0 0 0 0 1 1 1 1 15 7_Digit. 38
0 0 0 1 0 0 0 0 16 8_Digit. 39
0 0 0 1 0 0 0 1 17 9_Digit. 40
0 0 0 1 0 0 1 0 18 10_Digit. 41
0 0 0 1 0 0 1 1 19 11_Digit. 42
0 0 0 1 0 1 0 0 20 12_Digit. 43
0 0 0 1 0 1 0 1 21 13_Digit. 44
0 0 0 1 0 1 1 0 22 14_Digit.
45
0 0 0 1 0 1 1 1 23 15_Digit.
46
0 0 0 1 1 0 0 0 24 Local_Call.
47
0 0 0 1 1 0 0 1 25 Intra-LATA_Toll_Call.
0 0 0 1 1 0 1 0 26 Inter-LATA_Toll_Call. 48
0 0 0 1 1 0 1 1 27 World_Zone_Call. 49
0 0 0 1 1 1 0 0 28 International_Call. 50
0 0 0 1 1 1 0 1 29 Unrecognized_Number. 51
0 0 0 1 1 1 1 0 30 Prior_Agreement. 52
0 0 0 1 1 1 1 1 31 Specific_Called_Party_Digit_String (Note 2). 53
0 0 1 0 0 0 0 0 32 Mobile_Termination (Notes 2, 3). 54
0 0 1 0 0 0 0 1 33 Advanced_Termination (Note 2). 55
0 0 1 0 0 0 1 0 34 Location (Notes 2, 3).
56
57
58
59
60
TriggerType 5-66 TIA/EIA-41.5-D Modifications

PN-4287
1
Table dh Trigger Type value (concluded)
2
3
Trigger Type (octet 1)
4
5
6 0 0 1 0 0 0 1 1 35 Locally_Allowed_Specific_Digit_String (Note
7 2).
8 0 0 1 0 0 1 0 0 36 Origination_Attempt_Authorized.
9 0 0 1 0 0 1 0 1 37 Calling_Routing_Address_Available.
10 0 0 1 0 0 1 1 0 38 Initial_Termination (Note 2).
11 0 0 1 0 0 1 1 1 39 Called_Routing_Address_Available (Note 2).
12 0 0 1 0 1 0 0 0 40 O_Answer.
13 0 0 1 0 1 0 0 1 41 O_Disconnect.
14
0 0 1 0 1 0 1 0 42
15 Reserved. Treat a reserved value the same as
16 ••• through value 0, Unspecified.
17 0 0 1 1 1 1 1 1 63
18 0 1 0 0 0 0 0 0 64 Terminating_Resource_Available.
19 0 1 0 0 0 0 0 1 65 T_Busy.
20 0 1 0 0 0 0 1 0 66 T_No_Answer.
21 0 1 0 0 0 0 1 1 67 T_No_Page_Response.
22 0 1 0 0 0 1 0 0 68 T_Unroutable.
23 0 1 0 0 0 1 0 1 69 T_Answer.
24 0 1 0 0 0 1 1 0 70 T_Disconnect.
25 0 1 0 0 0 1 1 1 71
26 Reserved. Treat a reserved value the same as
••• through value 0, Unspecified.
27
1 1 0 1 1 0 1 1 219
28
29 1 1 0 1 1 1 0 0 220 Reserved for TDP-R DP Type value.
30 1 1 0 1 1 1 0 1 221 Reserved for TDP-N DP Type value.
31
1 1 0 1 1 1 1 0 222 Reserved for EDP-R DP Type value.
1 1 0 1 1 1 1 1 223 Reserved for EDP-N DP Type value.
32
33 1 1 1 0 0 0 0 0 224
Reserved for TIA/EIA-41 protocol extension. If
34 ••• through
unknown, treat the same as value 0, Unspecified.
35 1 1 1 1 1 1 1 1 255
36
37
38
Notes:
39 1. The Home_System_Feature_Code trigger type is mutually exclusive with the
40 Single_Introducing_Star trigger type. This trigger type is armed by default at
41 the serving system when the Single_Introducing_Star trigger is not armed.
42 When thus armed, the address associated with this trigger is the HLR for the
43 served subscriber.
44
45 2. These Trigger Type values are not intended for inclusion in the
46 TriggerAddressList parameter when this parameter is used for downloading a
47 subscriber’s trigger profile (e.g., regnot). The inclusion of these specific
48 Trigger Type values in a subscriber’s trigger profile is an error. If they are
49 received in a trigger profile, they shall be ignored.
50
3. The destination address associated with this trigger is always the address of the
51
52
HLR corresponding to the dialed MS address digits.
53
54
55
56
57
58
59
60
TIA/EIA-41.5-D Modifications 5-67 TriggerType

PN-4287
1
6.5.2.dj WINOperationsCapability 2
3
4
The WINOperationsCapability (WINOPCAP) parameter is used to specify the WIN 5
operations supported by the sending network element. 6
7
9
Identifier WINOperationsCapability M 6.5.1.2
10
11
Contents 13
14
15
Reserved CCDIR CONN 1 a 16
17
••• n b
18
19
Figure dj WINOperationsCapability parameter
20
21
Notes: 22
a. Reserved bits shall be ignored on receipt and set to zero on sending. 23
24
b. Ignore extra octets, if received. Send only defined (or significant) octets. 25
26
27
Table dj WINOperationsCapability value 28
29
ConnectResource (CONN) (octet 1, bit A) 30

32
0 0 Sender is not capable of supporting the 33
ConnectResource, DisconnectResource, 34
ConnectionFailureReport and ResetTimer
35
(SSFT timer) operations.
36
1 1 Sender is capable of supporting the
37
ConnectResource, DisconnectResource,
ConnectionFailureReport and ResetTimer 38
(SSFT timer) operations. 39

40
CallControlDirective (CCDIR) (octet 1, bit B) 41
0 0 Sender is not capable of supporting the 42
CallControlDirective operation. 43
1 1 Sender is capable of supporting the 44
CallControlDirective operation. 45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TriggerType 5-68 TIA/EIA-41.5-D Modifications

PN-4287
1
2 6.5.2.eg CallRecoveryID
3
4
5 The CallRecoveryID (CRID) parameter identifies a call for which no response was
6 received from the associated service logic for a TDisconnect or ODisconnect INVOKE.
7
9
Identifier CallRecoveryID M 6.5.1.2
10
IMPLICIT SET
11
13 Contents
14
BillingID M 6.5.2.16
15
16 TimeDateOffset M 6.5.2.dd a
17 TimeOfDay M 6.5.2.em b
18
19 Figure eg CallRecoveryID parameter
20
21 Notes:
22
23
a. Include to indicate the time offset of Local Civil Time with respect to
24
Coordinated Universal Time (UTC).
25
b. Include to indicate the time of day the call ended in UTC.
26
27
28
29
30
31
32
33
34
35
36
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.5-D Modifications 5-69 CallID

PN-4287
1
6.5.2.eh CallRecoveryIDList 2
3
4
The CallRecoveryIDList (CRIDLIST) parameter identifies a list of calls for which no 5
response was received from the associated service logic for a TDisconnect or 6
ODisconnect INVOKE. 7
8
10
Identifier CallRecoveryIDList M 6.5.1.2
11
IMPLICIT SET OF
12
Contents 14
15
CallRecoveryID M 6.5.2.eg
16
CallRecoveryID O 6.5.2.eg a 17
••• 18
19
Figure eh CallRecoveryIDList parameter 20
21
Notes: 22
23
a. Optionally include additional CallRecoveryID parameters. The maximum 24
number of CallRecoveryID parameters is dependent upon the two systems 25
involved in the transaction. 26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
CallIDList 5-70 TIA/EIA-41.5-D Modifications

PN-4287
1
2 6.5.2.ei DMH_ServiceID
3
4
5 The DMH_ServiceID (DMH_SVCID) parameter identifies the services (one or more)
6 that have been invoked.
7
9
Identifier DMH_ServiceID M 6.5.1.2
10
IMPLICIT Octet String
11
13 Contents
14
15
16 MSB 1
17 1st MarketID a, b
LSB 2
18
19 1st MarketSegmentID 3 b, c
20 MSB 4
21 1st DMH_ServiceID value d
LSB 5
22
23 MSB 6
2nd MarketID
24 LSB 7
25
2nd MarketSegmentID 8 e
26
27 MSB 9
28
2nd DMH_ServiceID value
LSB 10
29
30
••• n
31
Figure ei DMH_ServiceID parameter
32
33
34 Notes:
35 a. MarketID represents a unique market ID and is specified by the service provider
36 (e.g., FCC assigned SID, CIBERNET assigned BID—see TIA/EIA TSB29).
37
38 b. A MarketID plus MarketSegmentID uniquely identifies the SCF.
39
40
c. MarketSegmentID represents a unique identifier for a segment of a common
41
MarketID. The MarketSegmentID is specified by the service provider.
42
d. DMH_ServiceID values are determined by the service provider or bi-lateral
43
agreements.
44
45 e. Optionally include additional sets of five octets to identify the service invoked
46 and the associated SCF. The maximum number of services identified is
47 dependent upon the two systems involved in the transaction and the intervening
48 network.
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41.5-D Modifications 5-71 DMH_ServiceID

PN-4287
1
6.5.2.ej FeatureIndicator 2
3
4
The FeatureIndicator (FEATIND) parameter identifies a feature invoked for the call. 5
6
8
Identifier FeatureIndicator M 6.5.1.2
9
IMPLICIT Enumerated
10
Contents 12
13
14
Feature Indicator 1• •n b 15
16
Figure ej FeatureIndicator parameter 17
18
Notes: 19
20
a. Usually one octet.
21
b. See the DMH FeatureIndicator parameter for the values of this field. 22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
FeatureIndicator 5-72 TIA/EIA-41.5-D Modifications

PN-4287
1
2 6.5.2.ek ControlNetworkID
3
4
5 The ControlNetworkID (CNID) parameter indicates the MSCID of a specified SCF
6 network entity used to correlate MSC call data for SCF data recovery.
7
9
Identifier ControlNetworkID M 6.5.1.2
10
11
12 Length 3 octets M 6.5.1.1
13 Contents
14
15
16 MSB 1 a
17 MarketID
LSB 2
18
19 Switch Number (SWNO) 3 b
20
21
Figure ek ControlNetworkID parameter
22
23 Notes:
24 a. MarketID represent a unique market ID that is specified by the service provider
25 (e.g., FCC assigned SID, CIBERNET assigned BID—see TIA/EIA TSB29).
26
27 b. Switch Number represents a particular group of cell sites and switch resources
28 associated with a common MarketID.
29
30
31
32
33
34
35
36
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.5-D Modifications 5-73 ControlNetworkID

PN-4287
1
6.5.2.el ReleaseCause 2
3
4
The ReleaseCause (RELCAUSE) parameter identifies the call release cause. The release 5
cause applies to the call associated with a BillingID. 6
7
9
Identifier ReleaseCause M 6.5.1.2
10
IMPLICIT Unsigned Enumerated
11
Length 1 octet M 6.5.1.1 12
Contents 13
14
15
Release Cause 1 16
17
Figure el ReleaseCause parameter 18
19
Table el Release Cause value 20
21
Release Cause (octet 1) 22

24
0 0 0 0 0 0 0 0 0 Unspecified 25
0 0 0 0 0 0 0 1 1 Calling Party.
26
0 0 0 0 0 0 1 0 2 Called Party.
27
0 0 0 0 0 0 1 1 3 Commanded Disconnect.
28
0 0 0 0 0 1 0 0 4 29
Reserved. Treat a reserved value the same as
••• through 30
value 1, Calling Party.
0 0 0 1 0 1 1 1 23 31
32
0 0 0 1 1 0 0 0 24 Reserved for TIA/EIA-41 protocol extension. If
33
••• through unknown, treat the same as value 1, Calling
Party. 34
0 0 0 1 1 1 1 1 31
35
0 0 1 0 0 0 0 0 32 36
Reserved. Treat a reserved value the same as
••• through 37
value 2, Called Party.
0 0 1 1 0 1 1 1 55 38
39
0 0 1 1 1 0 0 0 56 Reserved for TIA/EIA-41 protocol extension. If 40
••• through unknown, treat the same as value 2, Called
41
0 0 1 1 1 1 1 1 63 Party.
42
43
0 1 0 0 0 0 0 0 64
Reserved. Treat a reserved value the same as 44
••• through
value 3, Commanded Disconnect. 45
0 1 0 1 0 1 1 1 87
46
0 1 0 1 1 0 0 0 88 Reserved for TIA/EIA-41 protocol extension. If 47
••• through unknown, treat the same as value 3, Commanded 48
0 1 0 1 1 1 1 1 95 Disconnect. 49
50
0 1 1 0 0 0 0 0 96
Reserved. Treat a reserved value the same as 51
••• through
value 0, Unspecified. 52
1 1 0 1 1 1 1 1 223 53
1 1 1 0 0 0 0 0 224 54
Reserved for TIA/EIA-41 protocol extension. If 55
••• through
unknown, treat the same as value 0, Unspecified. 56
1 1 1 1 1 1 1 1 255
57
58
59
60
ReleaseCause 5-74 TIA/EIA-41.5-D Modifications

PN-4287
1
2 6.5.2.em TimeOfDay
3
4
5 The TimeOfDay (TOD) parameter specifies time as a number of tenths of seconds past
6 midnight Coordinated Universal Time (UTC). The range of this parameter is 0 to
7 863,999 (24 hours times 60 minutes per hour times 60 seconds per minute times 10 tenths
8 per second - 1).
9
11
Identifier TimeOfDay IMPLICIT M 6.5.1.2
12
Unsigned Integer (0..863,999)
13
14 Length 3 octets M 6.5.1.1
15 Contents
16
17
18 MSB 1
19
Time of Day 2
20
21 LSB 3
22
23
Figure em TimeOfDay parameter
24
25
26
27
28
29
30
31
32
33
34
35
36
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.5-D Modifications 5-75 TimeOfDay

PN-4287
1
6.5.2.en CallStatus 2
3
4
The CallStatus (CALLSTATUS) parameter identifies the current status of a call. 5
6
8
Identifier CallStatus M 6.5.1.2
9
IMPLICIT Enumerated
10
Contents 12
13
14
Sign MSB 1 15
Call Status 16
LSB n
17
Figure en CallStatus parameter 18

19
20
Notes:
21
a. Usually one octet. 22
23
24
Table en Call Status value 25
26
Call Status 27
28
Decimal Value Meaning
29
0 Not used. 30
1 Call Setup in Progress. 31

32
2 Locally Allowed Call – No Action.
33
other positive values Reserved. Treat a reserved value the same as value 0, Not used. 34
negative values Reserved for bilateral agreements. If unknown, treat the same as value 35
0, Not used. 36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
CallStatus 5-76 TIA/EIA-41.5-D Modifications

PN-4287
1
2
CHAPTER 6
3
MODIFICATIONS TO TIA/EIA-41.6-D SIGNALING PROCEDURES
4
5
6
7
CONTENTS
8
9
10 LIST OF TABLES................................................................................................................... iii
11
12 REVISION HISTORY.............................................................................................................. iv
13
14 3 BASIC CALL PROCESSING......................................................................................... 1
15 3.1 Registration Call Tasks...................................................................................... 1
16 3.1.3 Loading of Profile Parameters................................................................. 1
17 3.2 Origination Call Tasks ....................................................................................... 4
18 3.2.3 MSC Analyze MS Dialed Number .......................................................... 4
19 3.2.5 Play All Announcements in the AnnouncementList.................................. 11
20 3.2.6 MSC Routing Points of Return............................................................ 12
21 3.2.9 MSC ActionCode Processing............................................................... 14
22 3.3 Terminating Call Tasks .................................................................................... 16
23 3.3.1 Incoming Call Attempt....................................................................... 16
24 3.3.5 MS Termination Alerting.................................................................... 18
25 3.3.8 MSC Route the Call Leg Externally...................................................... 25
26 3.4 Disconnect Call Tasks...................................................................................... 31
27 3.4.1 MS Disconnect.................................................................................. 31
28 3.4.2 Other Party Disconnect ....................................................................... 32
29 3.4.3 Commanded Disconnect ...................................................................... 33
30 4.14 Feature Request............................................................................................... 34
31 4.14.1 MSC Detecting Feature Request ........................................................... 34
32 4.24 Intersystem Answer ......................................................................................... 37
33 4.24.1 MSC Awaiting InterSystemAnswer....................................................... 37
34 4.28 Location Request............................................................................................. 38
35 4.28.1 MSC Initiating a Location Request ....................................................... 38
36 4.28.2 HLR Receiving LocationRequest INVOKE............................................. 42
37 4.31 Origination Request......................................................................................... 47
38 4.31.1 MSC Initiating an Origination Request.................................................. 47
39 4.49 Transfer-To-Number Request ............................................................................. 51
40 4.49.1 MSC Initiating a Transfer-To-Number Request........................................ 51
41 4.A Analyzed Information....................................................................................... 53
42 4.A.1 MSC Initiating an Analyzed Information ................................................ 53
43 4.E Facility Selected And Available.......................................................................... 56
44 4.E.1 MSC Initiating a Facility Selected And Available .................................... 56
45 4.M TBusy ........................................................................................................... 58
46 4.M.1 MSC Initiating a TBusy...................................................................... 58
47 4.N TNoAnswer.................................................................................................... 60
48 4.N.1 MSC Initiating a TNoAnswer .............................................................. 60
49 4.S Bulk Disconnection ......................................................................................... 63
50 4.S.1 MSC Initiating a Bulk Disconnection .................................................... 63
51 4.S.2 SCF Receiving BulkDisconnection INVOKE.......................................... 64
52 4.T Call Control Directive...................................................................................... 65
53 4.T.1 SCF Initiating a Call Control Directive ................................................. 65
54 4.T.2 MSC Receiving a CallControlDirective INVOKE .................................... 66
55 4.U OAnswer ....................................................................................................... 68
56 4.U.1 MSC Initiating an OAnswer ................................................................ 68
57 4.U.2 SCF Receiving an OAnswer INVOKE................................................... 69
58 4.V ODisconnect................................................................................................... 69
59 4.V.1 MSC Initiating an ODisconnect............................................................ 69
60

PN-4287
1
4.V.2 SCF Receiving an ODisconnect INVOKE .............................................. 71
2
4.W TAnswer........................................................................................................ 72
3
4.W.1 MSC Initiating a TAnswer .................................................................. 72
4
4.W.2 SCF Receiving a TAnswer INVOKE..................................................... 73
5
4.X TDisconnect................................................................................................... 73
6
4.X.1 MSC Initiating a TDisconnect.............................................................. 73
7
4.X.2 SCF Receiving a TDisconnect INVOKE ................................................ 74
8
4.Y Unreliable Call Data ........................................................................................ 75
9
4.Y.1 SCF Initiating an Unreliable Call Data .................................................. 76
10
4.Y.2 MSC Receiving UnreliableCallData INVOKE......................................... 77
11
4.Y.3 MSC Initiating a Call Recovery Report ................................................. 78
12
4.Y.4 SCF Receiving a CallRecoveryReport INVOKE ...................................... 79
13
14
6 COMMON VOICE FEATURE PROCEDURES .............................................................. 79
15
6.Y WIN Service Logic.......................................................................................... 79
16
17
7 OPERATION TIMER VALUES.................................................................................... 82 18
19
X Annex X: High level SDL Models for WIN...................................................................... 83 20
X.5.4 SDL Model of TriggerAddressList Processing.......................................... 83 21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
1
2
3
LIST OF TABLES
4
5 Table 4.S.2 SCF BulkDisconnection Response .................................................. 65
6 Table 4.T.2 MSC CallControlDirective Response .............................................. 68
7 Table 4.V.2 SCF ODisconnect Response .......................................................... 72
8
Table 4.X.2 SCF TDisconnect Response........................................................... 75
9
Table 4.Y.1 SCF CallRecoveryReport Response ................................................ 77
10
11
Table 4.Y.2 MSC UnreliableCallData Response ................................................. 78
12 Table 63 Operation Timer Values ................................................................ 82
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
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.6-D Modifications 6-iii List of Tables

PN-4287
REVISION HISTORY 2
3
4
5
6
Rev. Date Remarks 7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
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 6-iv TIA/EIA-41.6-D Modifications

PN-4287
1
2
3
3 BASIC CALL PROCESSING
4
5
6 3.1 REGISTRATION CALL TASKS
7
8
9
10
3 . 1 . 3 Loading of Profile Parameters
11 (TIA/EIA/IS-771, page 6-4)
12
13
Upon request, the HLR or VLR shall do the following:
14
1 Include the AuthenticationCapability parameter set appropriately.
15
16 2 Include the CallingFeaturesIndicator parameter set appropriately.
17 3 IF carrier selection digits are applicable:
18
3-1 IF the Profile is supported for this transaction:
19
20 3-1-1 Include the CarrierDigits parameter set to the carrier selection digits.
21 3-2 ELSE:
22
23
3-2-1 Include the Digits (Carrier) parameter set to the carrier selection digits.
24 3-3 ENDIF.
25
4 ENDIF.
26
27
5 IF default account code digits are applicable for calls by the subscriber:
28 5-1 IF the Profile is supported for this transaction:
29
5-1-1 Include the DMH_AccountCodeDigits parameter set to the appropriate
30
default account code digits.
31
32 5-2 ELSE:
33 5-2-1 (Consider restricting originations.)
34
5-3 ENDIF.
35
36 6 ENDIF.
37 7 IF billing digits are applicable for calls by the subscriber:
38
39
40 7-1-1 Include the DMH_BillingDigits parameter set to the appropriate alternate
41 billing digits.
42
7-2 ELSE:
43
44
7-2-1 (Consider restricting originations.)
45 7-3 ENDIF.
46
8 ELSEIF alternate billing digits are applicable for calls by the subscriber:
47
49 8-1-1 Include the DMH_AlternateBillingDigits parameter set to the appropriate
50 alternate billing digits.
51
8-2 ELSE:
52
53 8-2-1 (Consider restricting originations.)
54 8-3 ENDIF.
55
56
9 ENDIF.
57 10 IF the subscriber’s current privileges are geographically restricted:
58
59
60
TIA/EIA-41.6-D Modifications 6-1 3.1 Registration Call Tasks

PN-4287
1
10-1-1 Include the GeographicAuthorization parameter set appropriately.
2
10-2 ELSE: 3
10-2-1 (Consider restricting originations.) 4

5
10-3 ENDIF.
6
11 ENDIF. 7
12 IF the subscriber is authorized for message waiting notification: 8

9
12-1 IF the Profile is supported for this transaction: 10
12-1-1 Include the MessageWaitingNotificationCount parameter set appropriately. 11
12
12-1-2 Include the MessageWaitingNotificationType parameter set appropriately.
13
12-2 ENDIF. 14
13 ENDIF. 15
16
14 IF the MS is to be identified with a mobile directory number (other than its MIN):
17
14-1 IF the Profile is supported for this transaction: 18
14-1-1 Include the MobileDirectoryNumber parameter set to the subscriber’s current 19
directory number. 20
21
14-2 ELSE:
22
14-2-1 (Consider restricting originations and terminations or activating CNIR.) 23
14-3 ENDIF. 24
25
15 ENDIF. 26
16 Include the OriginationIndicator parameter set appropriately. 27
28
a IF WIN triggers can be processed by the requesting MSC (as indicated by the
29
TransactionCapability parameter):
30
a-1 IF there are WIN triggers or capabilities (e.g., support for CallControlDirective) 31
required for providing call origination or call termination services to the 32

33
subscriber:
34
a-1-1 IF the required set of triggers and capabilities is supported by the requesting 35
36
MSC (as indicated by the MSC’s WINCapability parameter):
37
a-1-1-1 Include the TriggerAddressList parameter set with the subset of the 38
subscriber’s triggers that are supported by the requesting MSC. 39

40
a-1-2 ELSE: 41
42
a-1-2-1 (Consider restricting originations or terminations.)
43
a-1-3 ENDIF. 44
45
a-1-4 IF the ControlNetworkID is applicable: 46
47
a-1-4-1 Include the ControlNetworkID parameter set appropriately.
48
a-1-5 ENDIF. 49
50
a-2 ELSE: 51
52
a-2-1 Include the TriggerAddressList parameter set with the subset of the
53
subscriber’s triggers that are supported by the requesting MSC. 54
a-3 ENDIF. 55
56
57
58
59
60
3.1 Registration Call Tasks 6-2 TIA/EIA-41.6-D Modifications

PN-4287
1 a-1 Include the TriggerAddressList1 parameter.

2
3 b ENDIF.
4 17 IF origination triggers are required:
5
6
7 17-1-1 Include the OriginationTriggers parameter set appropriately.
8
17-2 ELSE:
9
10
11 17-3 ENDIF.
12
18 ENDIF.
13
14 19 IF the subscriber is authorized for PACA:
16
19-1-1 Include the PACAIndicator parameter set appropriately.
17
18 19-2 ENDIF.
19 20 ENDIF.
20
21
21 IF the subscriber has a preferred language:
23
21-1-1 Include the PreferredLanguageIndicator parameter set appropriately.
24
25
21-2 ENDIF.
26 22 ENDIF.
27
23 IF restriction digits are required (as requested by the OriginationIndicator parameter):
28
30 23-1-1 Include the RestrictionDigits parameter set to the restriction digits.
31
23-2 ELSE:
32
33 23-2-1 Include the Digits (Destination) parameter set to the restriction digits.
34 23-3 ENDIF.
35
36
24 ENDIF.
37 25 IF routing digits are applicable for all calls by the subscriber:
38
39
40
25-1-1 Include the RoutingDigits parameter set to the appropriate routing digits.
41 25-2 ELSE:
42
43
44 25-3 ENDIF.
45 26 ENDIF.
46
27 IF the MS is registered to an SMS capable system:
47
49 27-1-1 Include the SMS_OriginationRestrictions parameter set appropriately.
50
51
27-1-2 Include the SMS_TerminationRestrictions parameter set appropriately.
52 27-2 ELSE:
53
54
55
56
57 1 A WIN trigger shall not be set in the TriggerAddressList parameter if the MSC’s
58 WINCapability parameter indicates the WIN trigger is not supported.
59
60
TIA/EIA-41.6-D Modifications 6-3 3.1 Registration Call Tasks

PN-4287
1
27-3 ENDIF.
2
28 ENDIF. 3
29 IF the current transaction supports local SPINI operation AND IF local SPINI 4
operation is desirable: 5
6
29-1 Include the SPINITriggers parameter set with the appropriate triggers for local
7
SPINI operation.
8
29-2 Include the SPINIPIN parameter set to the SPINI PIN. 9
30 ENDIF. 10
11
31 Include the TerminationRestrictionCode parameter set appropriately. 12
32 IF termination triggers are required: 13
14
15
32-1-1 Include the TerminationTriggers parameter set appropriately. 16
32-2 ELSE: 17
18
32-2-1 (Consider restricting terminations.)
19
32-3 ENDIF. 20
33 ENDIF. 21
22
34 Return to the calling task.
23
24
3.2 ORIGINATION CALL TASKS 25

26
27
28
3 . 2 . 3 MSC Analyze MS Dialed Number 29
(TIA/EIA/IS-771, page 6-7) 30
31
Upon demand the Anchor MSC shall do the following: 32
33
1 IF flash privileges are suspended (by the Flash Privileges in the OneTimeFeature-
34
Indicator parameter e.g., Call Transfer, Call Waiting, Three-Way Calling):
35
1-1 Include the TransactionCapability parameter with the number of multiple 36
terminations set to 0. 37
2 ELSEIF Call Transfer, Three-Way Calling OR or similar feature is being invoked: 38

39
2-1 Include the TransactionCapability parameter with the number of multiple 40
terminations set to 1. 41
3 ELSE: 42
43
3-1 Include the TransactionCapability parameter with the number of multiple
44
terminations set appropriately.
45
4 ENDIF. 46
Origination_Attempt_Authorized DP 47
48
a IF the MS dialed a locally allowed number (e.g., 9-1-1, *-9-1-1, N11, *N11)1 : 49
50
a-1 IF the MS dialed number is only routed locally, for instance, for numbers used
51
for access to local emergency service providers: 52
53
a-1-1 Process the dialed number locally routing the call with the
54
PreferredLanguageIndicator to set the PointOfReturn. 55
56
57
1 The MSC may also receive an air interface indication of an emergency call. 58
59
60
3.1 Registration Call Tasks 6-4 TIA/EIA-41.6-D Modifications

PN-4287
1
a-2 ELSEIF the Locally_Allowed_Specific_Digit_String trigger is armed AND IF
2
3
the dialed digits match the specific digit string:
4
a-2-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
5
6 a-2-2 Execute the “MSC Initiating an Origination Request” task (see 4.31.1) to
7 set the PointOfReturn.
8
9 a-3 ELSEIF the OriginationTriggers OR IF the TriggerAddressList WIN triggers
10 matches the *, # or the count of the dialed number digits:
11
12 a-3-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
13
a-3-2 Execute the “MSC Initiating an Origination Request” task (see 4.31.1) to
14
15
set the PointOfReturn.
16
a-4 ELSE:
17
18 a-4-1 Process the dialed number locally routing the call with the
19 PreferredLanguageIndicator to set the PointOfReturn.
20
21 a-5 ENDIF.
22
b ENDIF (locally allowed number).
23
24 c IF the Origination_Attempt_Authorized trigger is armed:
25
26 c-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
27
c-2 Include the TriggerType parameter set to indicate
28
29
Origination_Attempt_Authorized.
30
c-3 Execute the “MSC Initiating an Origination Request” task (see 4.31.1) to set the
31
32
PointOfReturn.
33 d ENDIF.
34
35 Collected_Information DP
36
Collect_Information PIC
37
38 5 IF the MS dialed a locally allowed number (e.g., 9-1-1, *-9-1-1, N11, *N11):
39 5-1 IF the MS dialed number is only routed locally, for instance, for numbers used for
40 access to local emergency service providers:
41 5-1-1 Process the dialed number locally routing the call with the
42 PreferredLanguageIndicator to set the PointOfReturn.
43
5-2 ELSEIF the OriginationTriggers OR the TriggerAddressList WIN triggers matches the
44
*, # or the count of the dialed number digits:
45
46
5-2-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
47 5-2-2 Execute the “MSC Initiating an Origination Request” task (see 4.31.1) to set the
48 PointOfReturn.
49
5-3 ELSE:
50
51
5-3-1 Process the dialed Service Code locally routing the call with the
PreferredLanguageIndicator to set the PointOfReturn.
52
53 5-4 ENDIF
54 6 ENDIF (locally allowed number).
55
56
7 IF the All_Calls trigger is set by the OriginationTriggers or the TriggerAddressList:
57 7-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
58
59
60
TIA/EIA-41.6-D Modifications 6-5 3.2 Origination Call Tasks

PN-4287
1
7-2 Execute the “MSC Initiating an Origination Request” task (see 4.31.1) to set the
2
PointOfReturn.
3
8 ENDIF (All trigger is set). 4
5
6 ELSEIF the OriginationTriggers All trigger is on:
6
7
PointOfReturn.
8
6-2 IF a Digits (Dialed) parameter is received: 9
6-2-1 IF the type of the Digits is unknown. 10
11
6-2-1-1 Process the dialed number locally to set the PointOfReturn.
12
6-2-2 ENDIF.
13
6-3 ENDIF. 14
9 IF ELSEIF the first digit is was a star (‘*’) digit: 15

16
9-1 IF the second digit is was a star (‘*’) digit: 17
9-1-1 IF the OriginationTriggers OR IF the TriggerAddressList is set for double 18
star codes: 19
20
9-1-1-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X). 21
9-1-1-2 Execute the “MSC Initiating an Origination Request” task (see 4.31.1) 22
to set the PointOfReturn. 23

24
7-1-1-2 IF a Digits (Dialed) parameter is received:
25
7-1-1-2-1 IF the type of the Digits is unknown: 26
7-1-1-2-1-1 Process the dialed number as a local feature code to set the 27
PointOfReturn. 28
7-1-1-2-2 ENDIF. 29
30
7-1-1-3 ENDIF.
31
9-1-2 ELSE (Double_Introducing_Star trigger is not set): 32
9-1-2-1 Process the dialed number as a local feature code or local service code to 33
34
set the PointOfReturn.
35
9-1-3 ENDIF. 36
9-2 ELSE (only a single star was dialed): 37

38
9-2-1 IF the OriginationTriggers OR IF the TriggerAddressList is set for single 39
star codes: 40
9-2-1-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X). 41
42
9-2-1-2 Execute the “MSC Initiating an Origination Request” task (see 4.31.1)
43
to set the PointOfReturn. 44
9-2-2 ELSE (Home_System_Feature_Code): 45
46
9-2-2-1 Execute a “MSC Detecting Feature Request” (see 4.14.1) to set the
47
PointOfReturn.
48
9-2-3 ENDIF. 49
7-2-4 IF a Digits (Dialed) parameter is received: 50

51
7-2-4-1 IF the type of the Digits is unknown.
52
7-2-4-1-1 Process the dialed number as a local feature code to set the 53
PointOfReturn. 54
7-2-4-2 ENDIF. 55
7-2-5 ENDIF. 56
57
9-3 ENDIF. 58
10 ENDIF (first digit is a star digit). 59
60
3.2 Origination Call Tasks 6-6 TIA/EIA-41.6-D Modifications

PN-4287
1
11 IF ELSEIF the first digit is was a pound (‘#’) digit:
2
3 11-1 IF the second digit is was a pound (‘#’) digit:
4
11-1-1 IF the OriginationTriggers OR IF the TriggerAddressList is set for double
5
pound codes:
6
7 11-1-1-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
8 11-1-1-2 Execute the “MSC Initiating an Origination Request” task (see 4.31.1)
9
to set the PointOfReturn.
10
8-1-1-2 IF a Digits (Dialed) parameter is received:
11
12 8-1-1-2-1 IF the type of the Digits is unknown.
13 8-1-1-2-1-1 Process the dialed number as a local feature code to set the
14 PointOfReturn.
15
8-1-1-2-2 ENDIF.
16
8-1-1-3 ENDIF.
17
18 11-1-2 ELSE (the double pound trigger is not set):
19
11-1-2-1 Process the dialed number as a local feature code to set the
20
PointOfReturn.
21
22 11-1-3 ENDIF.
23
11-2 ELSE (only a single pound was dialed):
24
25 11-2-1 IF the OriginationTriggers OR IF the TriggerAddressList is set for single
26 pound codes:
28
29
11-2-1-2 Execute the “MSC Initiating an Origination Request” task (see 4.31.1)
30 to set the PointOfReturn.
31 8-2-1-2 IF a Digits (Dialed) parameter is received:
32
8-2-1-2-1 IF the type of the Digits is unknown.
33
8-2-1-2-1-1 Process the dialed number as a local feature code to set the
34
PointOfReturn.
35
36 8-2-1-2-2 ENDIF.
37 8-2-1-3 ENDIF.
38
11-2-2 ELSE (the Single_Introducing_Pound pound trigger is not set):
39
40 11-2-2-1 Process the dialed number as a local feature code to set the
41 PointOfReturn.
42
11-2-3 ENDIF.
43
44 11-3 ENDIF.
45 12 ENDIF (first digit is a pound digit).
46
47
13 IF the OriginationTriggers or the TriggerAddressList is set for Revertive Call AND
48 IF the dialed number is the MS’s mobile directory number (or MIN if the mobile
49 directory number is not available):
50
13-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
51
52 13-2 Execute the “MSC Initiating an Origination Request” task (see 4.31.1) to set the
53 PointOfReturn.
54
14 ENDIF.
55
56
9 ELSEIF the OriginationTriggers Revertive Call trigger is on AND the dialed number is the
MS’s mobile directory number (or MIN if the mobile directory number is not available):
57
58 9-1 Execute the “MSC Initiating an Origination Request” task (see 4.31.1) to set the
59 PointOfReturn.
60

PN-4287

2
9-2-1 IF the type of the Digits is unknown.
3
9-2-1-1 Process the dialed number locally to set the PointOfReturn. 4
9-2-2 ENDIF. 5
6
9-3 ENDIF.
7
15 IF the OriginationTriggers OR IF the TriggerAddressList is set for Count AND IF 8
the number of digits dialed equals the corresponding count trigger: 9
10
15-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
11
15-2 Execute the “MSC Initiating an Origination Request” task (see 4.31.1) to set the 12
PointOfReturn. 13
14
16 ENDIF (Count triggers).
15
1 0 ELSEIF any of OriginationTriggers Count triggers are on AND the number of digits dialed 16
equals the corresponding count trigger:
17
10-1 Execute the “MSC Initiating an Origination Request” task (see 4.31.1) to set the 18
PointOfReturn. 19
21
10-2-1 IF the type of the Digits is unknown.
22
23
10-2-2 ENDIF. 24
10-3 ENDIF. 25
26
1 1 ELSEIF any of OriginationTriggers Local, ILATA, OLATA, Int’l, WZ, or Unrec, triggers
27
are on AND the call type matches the corresponding trigger:
28
29
PointOfReturn.
30
33
34
11-2-2 ENDIF.
35
11-3 ENDIF. 36
Analyzed_Information DP 37
38
Analyze_Information PIC 39
17 IF any of OriginationTriggers Local, ILATA, O L A T A , Int’l, W Z , Unrec or 40

41
TriggerAddressList Local, ILATA, OLATA, Int’l, WZ, Unrec triggers are set AND
42
IF the call type matches the corresponding trigger:
43
17-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X). 44
45
46
PointOfReturn.
47
18 ENDIF. 48
1 2 ELSEIF the any unknown OriginationTriggers are on (e.g., reserved bits set to 1 or extra 49
octets with any bit set to 1): 50

51
52
PointOfReturn.
53
12-2 IF a Digits (Dialed) parameter is received:
54
12-2-1-1 Process the dialed number locally to set the PointOfReturn. 56

57
12-2-2 ENDIF.
58
12-3 ENDIF. 59
60

PN-4287
1
19 IF the OriginationTriggers or the WIN trigger for Prior Agreement is set AND IF the
2
dialed digits are recognized for Prior Agreement:
3
5
6
PointOfReturn.
7
8 20 ENDIF.
9
21 IF the Specific_Called_Party_Digit_String trigger is armed AND IF the dialed digits
10
match the specific digit string:
11
13
21-2 Execute the “MSC Initiating an Analyzed Information” task (see 4.A.1) to set
14
the PointOfReturn.
15
16 22 ENDIF.
17
23 IF ELSEIF the call type matches an active trigger in the SPINITriggers parameter:
18
19 23-1 Execute the “MSC SPINI Originating Call Invocation” task (see 5.21.3) to set
20 the PointOfReturn.
21
24 ELSEIF the any unknown SPINITriggers are on (e.g., reserved bits set to 1 or extra
22
octets with any bit set to 1):
23
24 24-1 Execute the “MSC SPINI Originating Call Invocation” task (see 5.21.3) to set
25 the PointOfReturn.
26 25 ELSEIF the MS is permitted to dial only a specific 10-digit number in the service
27
profile (i.e., the MS has hot line activated):
28
29
25-1 Set the dialed number to the 10-digit number in the service profile.
30 25-2 Set the PointOfReturn to Directory Number.
31
32
26 ELSEIF the MS is restricted from originating any call:
33 26-1 Execute “Apply Access Denial Treatment” task (see 3.4.5).
34
26-2 Exit this task.
35
36 27 ELSEIF the subscriber shall be authorized on a per call basis OR IF authorization is
37 due:
38
27-1 Execute the “MSC Initiating a Qualification Request” task (see 4.33.1).
39
40 27-2 IF the call is not authorized (AuthorizationDenied or OriginationIndicator is
41 Origination denied):
42
27-2-1 Execute “Apply Access Denial Treatment” task (see 3.4.5).
43
44 27-2-2 Exit this task.
45 27-3 ENDIF
46
47
28 ELSE:
48 28-1 GOTO AuthorizedSubscriberOrigination.
49
50
29 ENDIF.
51 AuthorizedSubscriberOrigination:
52
30 IF the call is on hold and PointOfReturn is ToneTermination:
53
54 30-1 Reconnect the current call.
55
31 ENDIF.
56
57 c IF the Calling_Routing_Address_Available trigger is armed for the calling
58 subscriber:
59
60

PN-4287
1
c-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
2
c-2 Include the TriggerType parameter set to indicate 3
4
Calling_Routing_Address_Available.
5
c-3 Execute the “MSC Initiating an Analyzed Information” task (see 4.A.1). 6
7
d ENDIF. 8
32 IF the AnnouncementList parameter is received: 9

10
32-1 Execute the “Play All Announcements in the AnnouncementList” task (see 11
3.2.5). 12
33 ENDIF. 13
14
34 IF the dialed or destination number is a potential mobile directory number: 15
34-1 Include TerminationAccessType parameter set to indicate Mobile to 16
MobileDirectoryNumber. 17
18
34-2 Include the TriggerType parameter set to indicate Mobile_Termination.
19
34-3 Execute the “MSC Initiating a Location Request” task (see 4.28.1) to set the 20
PointOfReturn. 21
22
34-a IF the Initial_Termination trigger is armed:
23
34-a-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X). 24
25
34-a-2 Include the TriggerType parameter set to indicate Initial_Termination. 26
27
34-a-3 Execute the “MSC Initiating an Analyzed Information” task (see 4.A.1).
28
34-b ENDIF. 29
30
34-4 IF the Advanced_Termination trigger is armed for the called subscriber: 31
34-4-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X). 32
33
34-4-2 Include the TerminationAccessType parameter set to indicate Mobile to
34
MobileDirectoryNumber. 35
34-4-3 Include the TriggerType parameter set to indicate Advanced_Termination. 36
37
34-4-4 Execute the “MSC Initiating an Analyzed Information” task (see 4.A.1).
38
34-5 ENDIF. 39
40
34-6 IF the Location trigger is armed for the called subscriber:
41
43
34-6-2 Include TerminationAccessType parameter set to indicate Mobile to
44
MobileDirectoryNumber.
45
34-6-3 Include the TriggerType parameter set to indicate Location. 46
47
34-6-4 Execute the “MSC Initiating a Location Request” task (see 4.28.1).
48
34-7 ENDIF. 49
34-8 IF the Called_Routing_Address_Available trigger is armed: 50

51
53
34-8-2 I ncl ude the T ri ggerT ype param et er set to i ndi cat e
54
Called_Routing_Address_Available. 55
56
34-8-3 Execute the “MSC Initiating an Analyzed Information” task (see 4.A.1).
57
34-9 ENDIF. 58
59
60

PN-4287
1
34-10 IF the destination address is indicated by the Digits (Destination) parameter:
2
3 34-10-1 Execute the “MSC Route the Call Leg Externally” task (see 3.3.8).
4
5
34-11 ELSEIF the destination address is indicated by the TerminationList parameter:
6
34-11-1 Execute the “MSC Routing Points of Return” task (see 3.2.6).
7
8 34-12 ELSEIF the destination is an MS served by this MSC (i.e., this MSC is the
9 Serving MSC):
10
11 34-12-1 Execute the “Authorize MS Termination Attempt” task (see 3.3.4) for the
12 MS indicated by the MobileIdentificationNumber or IMSI parameter.
13
14 34-13 ENDIF.
15
35 ELSE:
16
17 35-1 Set the PointOfReturn to PSTNTermination.
18
36 ENDIF.
19
20 37 IF the AnnouncementList parameter is received:
21 37-1 Execute the “Play All Announcements in the AnnouncementList” task (see
22
3.2.5).
23
24
38 ENDIF.
25 39 Execute the “MSC Routing Points of Return” task (see 3.2.6) to process the
26 PointOfReturn.
27
28
29
30
3 . 2 . 5 Play All Announcements in the AnnouncementList
31
32
33
Upon request, the MSC shall do the following:
34
35 1 IF only one party exists in the call:
36
37 1-1 The announcement shall be played to this party.
38
2 ELSE (more than one party exists in the call):
39
40 2-1 IF the subscriber is engaged in the call:
41
42
2-1-1 The announcement shall be played to the subscriber.
43
2-2 ELSE:
44
45 2-2-1 The announcement shall be played to the party associated with the
46 subscriber (e.g., the called party when the call has been forwarded on behalf
47
of the subscriber).
48
49 2-3 ENDIF.
50
51 3 ENDIF.
52
53
54
Renumber the remaining steps.
55
56 1 FOR all AnnouncementCodes in the AnnouncementList parameter:
57 1-1 IF the custom AnnouncementCode specified is supported:
58
59
60

PN-4287
1
1-1-1 IF the custom announcement is available in the subscriber’s preferred
2
language:
3
1-1-1-1 Play the custom announcement in the subscriber’s preferred language. 4
1-1-2 ELSE: 5
6
1-1-2-1 Play the custom announcement in the system’s default language.
7
1-1-3 ENDIF. 8
1-2 ELSEIF the standard AnnouncementCode specified is supported: 9

10
1-2-1 IF the standard announcement is available in the subscriber’s preferred 11
language: 12
1-2-1-1 Play the standard announcement in the subscriber’s preferred language. 13
14
1-2-2 ELSE:
15
1-2-2-1 Play the standard announcement in the system’s default language. 16
1-2-3 ENDIF. 17
18
1-3 ELSEIF the standard tone specified is supported:
19
1-3-1 Play the indicated tone to the caller. 20
1-4 ELSE: 21
22
1-4-1 (Do nothing.)
23
1-5 ENDIF. 24
2 ENDFOR. 25
26
3 IF the announcements are in the sequential class: 27
3-1 WAIT for the End of announcement: 28
29
3-2 WHEN the announcement(s) is over:
30
3-2-1 Return to the calling task with a listened indication. 31
3-3 WHEN the subscriber abandons: 32
33
3-3-1 Return to the calling task with an abandoned indication.
34
3-4 ENDWAIT. 35
4 ELSE (the announcements are in the concurrent or reserved class): 36

37
4-1 Return to the calling task with a no wait indication .
38
5 ENDIF. 39
40
41
3 . 2 . 6 MSC Routing Points of Return 42
(TIA/EIA-41.6-D, page 6-20) 43
44
When an Originating MSC is requested to route a call or legs of a call, it shall do the 45
following: 46
47
1 (Subscriber parameters for this call are assumed from the stored profile.)
48
2 Override call parameters for this call only with parameters received with the 49
TerminationList parameter. 50
3 FOR all terminations in the TerminationList parameter: 51
52
3-1 Override call parameters for this call leg only with parameters received within the
53
particular termination parameter.
54
3-2 CASE termination OF: 55
3-3 LocalTermination (MSCID (Serving) is the same as this MSC’s ID): 56

57
3-3-1 IF the TerminationTreatment parameter is received:
58
3-3-1-1 CASE TerminationTreatment value OF: 59
60

PN-4287
1
3-3-1-2 MSTermination:
2
3 3-3-1-2-1 Execute the “Authorize MS Termination Attempt” task (see 3.3.4).
4 3-3-1-3 VoiceMailStorage:
5
3-3-1-3-1 IF the DestinationDigits parameter is received:
6
7 3-3-1-3-1-1 Select the voice mail system using the received
8 DestinationDigits parameter.
9 3-3-1-3-2 ELSE:
10
11
3-3-1-3-2-1 Select the voice mail system using a default voice mail system
12
identifier.
13 3-3-1-3-3 ENDIF.
14
3-3-1-3-4 IF the VoiceMailboxNumber parameter is received:
15
16
3-3-1-3-4-1 Select the voice mail box within the voice mail system using
17
the received VoiceMailboxNumber parameter.
18 3-3-1-3-5 ELSE:
19
3-3-1-3-5-1 Select the voice mail box within MIN.
20
21 3-3-1-3-6 ENDIF.
22 3-3-1-3-7 Connect the call to the selected voice mail box.
23
3-3-1-4 VoiceMailRetrieval:
24
25 3-3-1-4-1 IF the DestinationDigits parameter is received:
26 3-3-1-4-1-1 Select the voice mail system using the received
27 DestinationDigits parameter.
28
29
3-3-1-4-2 ELSE:
30 3-3-1-4-2-1 Select the voice mail system using a default voice mail system
31 identifier.
32
3-3-1-4-3 ENDIF.
33
34
3-3-1-4-4 IF the VoiceMailboxNumber parameter is received:
35 3-3-1-4-4-1 Select the voice mail box within the voice mail system using
36 the received VoiceMailboxNumber parameter.
37
3-3-1-4-5 ELSE:
38
39 3-3-1-4-5-1 Select the voice mail box within MIN.
40 3-3-1-4-6 ENDIF.
41
3-3-1-4-7 Connect the call to the selected voice mail box.
42
43 3-3-1-4-8 IF the VoiceMailboxPIN parameter is received:
44 3-3-1-4-8-1 Signal the PIN to the selected voice mail box.
45
46
3-3-1-4-9 ENDIF.
47 3-3-1-5 DialogueTermination:
48
3-3-1-5-1 Select the dialogue by analyzing the received DestinationDigits
49
parameter.
50
51
3-3-1-5-2 Play announcements in the Preferred Language, collect digits, and
52
perform other actions required by the locally defined dialog.
53 3-3-1-5-3 Communicate as required with the HLR in a proprietary manner.
54
3-3-1-6 DEFAULT:
55
56 3-3-1-6-1 Execute “Local Recovery Procedures” task (see 3.5.1).
57 3-3-1-7 ENDCASE.
58
3-3-2 ENDIF.
59
60

PN-4287
1
3-4 IntersystemTermination:
2
3-4-1 Execute the “MSC Route the Call Leg Externally” task (see 3.3.8). 3
3-5 PSTNTermination: 4
5
3-5-1 IF the TriggerAddressList parameter is received for the forwarded call leg:
6
3-5-1-1 Arm the triggers indicated by the TriggerAddressList parameter for the 7
8
redirected call.
9
3-5-1-2 Execute the “MSC Analyze MS Dialed Number” task (3.2.3). 10
11
3-5-2 ELSE: 12
13
3-5-2-1 Execute the “MSC Route the Call Leg Externally” task (see 3.3.8).
14
3-5-3 ENDIF. 15
16
3-5-1 Execute the “MSC Route the Call Leg Externally” task (see 3.3.8).
17
3-6 DEFAULT: 18
3-6-1 Execute “Local Recovery Procedures” task (see 3.5.1). 19

20
3-7 ENDCASE. 21
4 ENDFOR. 22
23
5 Exit this task.
24
25
3 . 2 . 9 MSC ActionCode Processing 26
27
28
1 CASE ActionCode parameter value OF: 29
30
2 Disconnect call:
31
2-1 Disconnect the call by executing the “Commanded Disconnect” task (see 3.4.3). 32
3 Disconnect call leg: 33

34
3-1 IF a LegInformation is received AND IF the received LegInformation matches an
35
outstanding leg for this call:
36
3-1-a IF the T_Disconnect trigger is armed for this leg: 37
38
3-1-a-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
39
3-1-a-2 Set the TriggerType parameter to indicate T_Disconnect. 40

41
3-1-a-3 Include the ReleaseCause parameter set to indicate Commanded 42
Disconnect. 43
44
3-1-a-4 Execute the “MSC Initiating a TDisconnect” task (see 4.X.1). 45
46
3-1-b ELSEIF the O_Disconnect trigger is armed for this leg:
47
3-1-b-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X). 48
49
3-1-b-2 Set the TriggerType parameter to indicate O_Disconnect. 50
3-1-b-3 Include the ReleaseCause parameter set to indicate Commanded 51

52
Disconnect.
53
3-1-b-4 Execute the “MSC Initiating an ODisconnect” task (see 4.V.1). 54

55
3-1-c ENDIF. 56
57
3-1-1 Disconnect the leg.
58
3-2 ELSE: 59
60

PN-4287
1
3-2-1 Disconnect the call by executing the “Commanded Disconnect” task (see
2
3.4.3).
3
4 3-3 ENDIF.
5 4 Conference calling drop last party:
6
4-1 IF the call is in the internal Conference Calling processing mode:.
7
8 4-1-1 IF there are at least two parties to the conference call:.
9
10 4-1-1-a IF the T_Disconnect trigger is armed for this leg:
11
4-1-1-a-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
12
13 4-1-1-a-2 Set the TriggerType parameter to indicate T_Disconnect.
14
15
4-1-1-a-3 Include the ReleaseCause parameter set to indicate Commanded
16 Disconnect.
17
18
4-1-1-a-4 Execute the “MSC Initiating a TDisconnect” task (see 4.X.1).
19 4-1-1-b ELSEIF the O_Disconnect trigger is armed for this leg:
20
21 4-1-1-b-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
22
4-1-1-b-2 Set the TriggerType parameter to indicate O_Disconnect.
23
24 4-1-1-b-3 Include the ReleaseCause parameter set to indicate Commanded
25
Disconnect.
26
27 4-1-1-b-4 Execute the “MSC Initiating an ODisconnect” task (see 4.V.1).
28
29
4-1-1-c ENDIF.
30
4-1-1-1 Disconnect the conference party that has been connected for the shortest
31
period of time.
32
33
4-1-2 ELSE:
34 4-1-2-1 Disconnect the call by executing the “Commanded Disconnect” task
35 (see 3.4.3).
36
4-1-3 ENDIF.
37
38 4-2 ENDIF.
39 5 Bridge leg(s) to conference call:
40
5-1 Extend the call leg with the routing instructions.
41
42 5-2 IF Conference Calling is invoked (i.e., a ConferenceCallingIndicator parameter is
43 received indicating more than 2 parties):
44 5-2-1 Add the leg to a conference circuit.
45
46
5-3 ELSEIF call is only a two-way call AND IF a three-way calling circuit is
47
available:
48 5-3-1 Bridge the leg to a three-way calling circuit.
49
5-4 ELSEIF the call is only a one-way call:
50
51
5-4-1 Connect the call leg to the calling subscriber.
52 5-5 ELSE (an error condition has occurred):
53
5-5-1 Drop the newly extended leg.
54
55 5-5-2 Play an appropriate announcement or tone.
56 5-6 ENDIF.
57
6 Drop leg on busy or routing failure:
58
59 6-1 Extend the call leg with the routing instructions.
60

PN-4287
1
6-2 Add the leg to a simultaneous alerting bridge and drop the leg automatically
2
should the leg not be routable or should the leg reach a busy party or should
3
another leg be answered or should the call be abandoned.
4
a Release leg and redirect subscriber: 5
6
a-1 Release all call legs except the subscriber call leg by executing the “Commanded
7
Disconnect” task (see 3.4.3). 8
9
b Disconnect all call legs:
10
b-1 Disconnect all call legs by executing the “Commanded Disconnect” task (see 11
3.4.3). 12
13
7 DEFAULT: 14
7-1 (ignore the action code.) 15

16
8 ENDCASE. 17
9 Return to the calling task. 18
19
20
3.3 TERMINATING CALL TASKS 21
22
23
3 . 3 . 1 Incoming Call Attempt 24

25
26
When an MSC receives a call, it shall do the following: 27

28
1 IF call is an RFC port: 29
30
1-1 Include TerminationAccessType parameter set to indicate a
31
RemoteFeatureControlPort.
32
PointOfReturn. 34
2 ELSEIF call is to a potential TLDN: 35
36
2-1 IF the call is to an assigned TLDN:
37
2-1-1 GOTO “TLDN Call Arrival” in the “Wait for TLDN Call” task (see 3.3.2). 38
2-2 ELSE (including the calls to an unassigned TLDN): 39

40
2-2-1 Execute “Apply Access Denial Treatment” task (see 3.4.5).
41
2-2-2 Exit this task. 42
2-3 ENDIF. 43
44
3 ELSEIF call is to a roamer port:
45
3-1 Include TerminationAccessType parameter set to indicate RoamerPort. 46
PointOfReturn. 48
3-3 IF the AnnouncementList parameter is received: 49

50
3-3-1 Execute the “Play All Announcements in the AnnouncementList” task (see
51
3.2.5).
52
3-4 ENDIF. 53
4 ELSE call is to a potential mobile directory number: 54
55
Analyzed_Information DP
56
4-1 IF the call is to a roamer port: 57
58
4-1-1 Set the TerminationAccessType parameter to indicate RoamerPort. 59
60

PN-4287
1
4-2 ELSE (call is to a potential mobile directory number):
2
3 4-2-1 Set the TerminationAccessType parameter to indicate Land to
4
MobileDirectoryNumber.
5
6 4-3 ENDIF.
7
8
4-4 Include the TerminationAccessType parameter.
9 4-1 Include TerminationAccessType parameter set to indicate Land to
10 MobileDirectoryNumber.
11
4-a Include the TriggerType parameter set to indicate Mobile_Termination.
12
13 4-w Execute the “MSC Initiating a Location Request” task (see 4.28.1) to set the
14 PointOfReturn.
15
4-x IF the Initial_Termination trigger is armed:
16
17 4-x-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
18
19 4-x-2 Include the TerminationAccessType parameter.
20
4-x-3 Include the TriggerType parameter set to indicate Initial_Termination.
21
22 4-x-4 Execute the “MSC Initiating an Analyzed Information” task (see 4.A.1).
23
24
4-y ENDIF.
25
4-b IF the Advanced_Termination trigger is armed:
26
27 4-b-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
28 4-b-2 Include the TerminationAccessType parameter.
29
30 4-b-3 Include the TriggerType parameter set to indicate Advanced_Termination.
31
4-b-4 Execute the “MSC Initiating Analyzed Information” task (see 4.A.1).
32
33 4-c ENDIF.
34
35
4-d IF the Location trigger is armed:
36 4-d-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
37
4-d-2 Include the TerminationAccessType parameter.
38
39 4-d-3 Include the TriggerType parameter set to indicate Location.
40
41 4-d-4 Execute the “MSC Initiating Location Request” task (see 4.28.1).
42
4-e ENDIF.
43
44 4-f IF the Called_Routing_Address_Available trigger is armed:
45
4-f-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
46
47 4-f-2 I ncl ude t he T ri ggerT ype param et er set to i nd ic a te
48
Called_Routing_Address_Available.
49
50 4-f-3 Execute the “MSC Initiating an Analyzed Information” task (see 4.A.1).
51
52
4-f-4 ENDIF.
53
4-g IF the destination address is indicated by the Digits (Destination) parameter:
54
55 4-g-1 Execute the “MSC Route the Call Leg Externally” task (see 3.3.8).
56
57
4-h ELSEIF the destination address is indicated by the TerminationList parameter:
58 4-h-1 Execute the “MSC Routing Points of Return” task (see 3.2.6).
59
60
TIA/EIA-41.6-D Modifications 6-17 3.3 Terminating Call Tasks

PN-4287
1
4-i ELSEIF the destination is an MS served by this MSC (i.e., this MSC is the
2
Serving MSC): 3
4
4-i-1 Execute the “Authorize MS Termination Attempt” task (see 3.3.4) for the
5
MS indicated by the MobileIdentificationNumber or IMSI parameter. 6
4-j ENDIF. 7
8
5 ENDIF. 9
6 Exit this task. 10

11
12
3 . 3 . 5 MS Termination Alerting 13
(TIA/EIA-41.6-D, page 6-29) 14

15
Upon request, the MSC shall perform the following: 16
17
1 IF the indicated MS is idle: 18
Select_Facility PIC 19
20
1-1 IF a channel has not been allocated for the MS (i.e., the MS has not been
21
paged):
22
1-1-1 IF an appropriate idle voice or traffic channel is available for the identified 23
air interface control channel: 24
1-1-1-1 Reserve the available voice or traffic channel. 25

26
1-1-1-2 Execute the “Page an MS Procedure” (see 3.3.3). 27
1-1-1-3 IF the paging was locally successful: 28
29
1-1-1-3-1 GOTO Network_Resource_Selection.
30
1-1-1-3-1 GOTO Await Answer. 31
1-1-1-4 ELSEIF the paging was successful on another system: 32
33
Facility Selected and Available DP
34
1-1-1-4-a IF the Terminating_Resource_Available trigger has been armed for 35
the MS: 36
37
1-1-1-4-a-1 Execute the “MSC Check of Serial Trigger Limit” task (see 38
6.X). 39
1-1-1-4-a-2 Execute the “MSC Initiating a Facility Selected And 40
Available” task (see 4.E.1). 41

42
1-1-1-4-b ENDIF. 43
1-1-1-4-c IF the DisplayText parameter is received: 44

45
1-1-1-4-c-1 Include the DisplayText parameter. 46
1-1-1-4-d ENDIF. 47
48
1-1-1-4-1 Execute the “MSC Initiation of an Intersystem Setup” task (see
49
4.27.1).
50
1-1-1-4-2 GOTO Await Answer. 51
1-1-1-5 ELSE (the paging was unsuccessful): 52

53
1-1-1-5-1 IF the MS has activated Call Forwarding—No Answer in the 54
CallingFeaturesIndicator OR or IF the MS has the No Page 55
Response termination trigger TerminatingTrigger active OR IF the 56
TriggerAddressList includes an address for the 57
T_No_Page_Response trigger: 58
59
60
3.3 Terminating Call Tasks 6-18 TIA/EIA-41.6-D Modifications

PN-4287
1
1-1-1-5-1-1 Include the RedirectionReason parameter set to No Page
2
Response.
3
4 1-1-1-5-1-2 IF this call has requested the None Reachable termination
5 trigger AND IF this is the last leg AND IF a
6 GroupInformation parameter was received:
7 1-1-1-5-1-2-1 Include the GroupInformation parameter.
8
1-1-1-5-1-3 ELSEIF the LegInformation parameter was received:
9
10 1-1-1-5-1-3-1 Include the LegInformation parameter.
11 1-1-1-5-1-4 ENDIF.
12
13
1-1-1-5-1-5 IF the MSC is the Originating MSC:
14 T Busy DP
15
16
1-1-1-5-1-5-1 IF the TriggerAddressList parameter includes an address for
17
the T_No_Page_Response trigger:
18 1-1-1-5-1-5-1-1 Execute the “MSC Check of Serial Trigger Limit”
19 task (see 6.X).
20
21
1-1-1-5-1-5-1-2 Execute the “MSC Initiating a TBusy” task (see
22 4.M.1).
23 1-1-1-5-1-5-2 ELSE:
24
25
1-1-1-5-1-5-2-1 Execute the “MSC Check of Serial Trigger Limit”
26 task (see 6.X).
27 1-1-1-5-1-5-2-2 Execute the “MSC Initiating a Transfer-To-Number
28
Request” task (see 4.49.1).
29
30 1-1-1-5-1-5-3 ENDIF.
31 1-1-1-5-1-5-1 Execute the “MSC Initiating a Transfer-To-Number Request”
32 task (see 4.49.1).
33
1-1-1-5-1-6 ELSEIF the Originating MSC is provisioned for call
34
redirection:
35
36 1-1-1-5-1-6-1 Execute the “MSC Initiating a Redirection Request” task
37 (see 4.36.1).
38 1-1-1-5-1-7 ELSE:
39
1-1-1-5-1-7-1 IF the TriggerAddressList parameter includes an address for
40
41
the T_No_Page_Response trigger:
42 1-1-1-5-1-7-1-1 Execute the “MSC Check of Serial Trigger Limit”
43 task (see 6.X).
44
45
46
4.M.1).
47 1-1-1-5-1-7-2 ELSE:
48
49
50
task (see 6.X).
51 1-1-1-5-1-7-2-2 Execute the “MSC Initiating a Transfer-To-Number
52 Request” task (see 4.49.1).
53
54
1-1-1-5-1-7-3 ENDIF.
55 1-1-1-5-1-7-1 Execute the “MSC Initiating a Transfer-To-Number Request”
56 task (see 4.49.1).
57
1-1-1-5-1-8 ENDIF.
58
59
1-1-1-5-2 ELSE:
60

PN-4287
1
1-1-1-5-2-1 Execute “Apply Access Denial Treatment” (see 3.4.5).
2
1-1-1-5-2-2 Exit this task. 3
1-1-1-5-3 ENDIF. 4
5
1-1-1-6 ENDIF.
6
1-1-2 ELSE (no idle voice channel available) 7
8
1-1-2-1 IF the T_Unroutable trigger has been armed for the MS:
9
1-1-2-1-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X). 10
1-1-2-1-2 Execute the “MSC Initiating a TBusy” task (see 4.M.1). 11

12
1-1-2-2 ENDIF. 13
1-1-3 ENDIF. 14
15
1-1-2 ENDIF.
16
1-2 ENDIF. 17
Network_Resource_Selection 18
19
1-3 IF the RoutingDigits parameter is received: 20
1-3-1 Analyze the routing digits to select an internal trunk group (such as, a 21
service monitor, scrambling device). 22
23
1-3-2 Execute the “MSC CNIP Terminating Call Invocation” task (see 5.8.4).
24
1-4 ENDIF. 25
1-5 Include the appropriate MS identifier (MobileIdentificationNumber or IMSI) in 26

27
the alerting command.
28
1-5 IF the MobileDirectoryNumber parameter is received: 29
1-5-1 Include the MobileDirectoryNumber parameter as the Called Number in the MS 30
alerting command. 31
32
1-6 ELSE:
33
1-6-1 Include the MobileIdentificationNumber parameter as the Called Number in the 34
MS alerting command.
35
1-7 ENDIF. 36
1-a IF the Terminating_Resource_Available trigger has been armed for the MS: 37
38
1-a-1 IF the trigger had not already been processed at this MSC: 39
1-a-1-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X). 40
41
1-a-1-2 Execute the “MSC Initiating a Facility Selected And Available” task 42
(see 4.E.1). 43
1-a-1-3 Execute the “MSC CNAP Terminating Call Invocation task (see 44
IS-764 page 137, Section 5.X.2). 45

46
1-a-2 ENDIF. 47
1-b ENDIF. 48
49
1-8 IF the AlertCode parameter received: 50
1-8-1 Include the AlertCode parameter in the MS alerting command to control the 51
pitch and cadence of the alerting. 52
53
1-9 ELSE:
54
1-9-1 Include the system default AlertCode parameter in the MS alerting command 55
to control the pitch and cadence of the alerting. 56
1-10 ENDIF. 57
58
Present_Call PIC
59
60

PN-4287
1
1-11 Order the MS to alert.
2
3 T_Alerting PIC
4 Await Answer (get here for normal and CW alerting, alerting has been applied, no
5 timers have been started):
6
7
1-12 IF the TerminationTriggers, the TriggerAddressList, or both are is received:
8 1-12-1 Store the TerminationTriggers parameter for the leg, if received, AND store
9 the TriggerAddressList parameter for this leg, if received.
10
11
1-12-2 IF the NoAnswer trigger is requested in the TerminationTriggers parameter
12
in the TriggerAddressList, or in both OR IF the MS has Call Forwarding—
13
No Answer activated in the CallingFeaturesIndicator parameter:
14 1-12-2-1 IF the NoAnswerTime parameter is received:
15
1-12-2-1-1 Start a no answer timer with the value in the received
16
NoAnswerTime parameter.
17
18 1-12-2-2 ELSE:
19 1-12-2-2-1 Start a no answer timer with a system default value.
20
1-12-2-3 ENDIF.
21
22 1-12-3 ENDIF.
23 1-13 ENDIF.
24
25
1-14 IF the LegInformation parameter is received:
26 1-14-1 Store the LegInformation to control subsequent redirections.
27
1-15 ENDIF.
28
29 1-16 Start the alerting timer1.
30 1-17 Apply ring back tone to the waiting call.
31
32
1-18 WAIT for the MS to answer:
33 1-19 WHEN the MS answers:
34
T_Answer DP
35
36 1-19-a IF the T_Answer trigger is armed:
37
38
39 1-19-a-2 Include the TriggerType parameter set to indicate T_Answer.
40
41 1-19-a-3 Execute the “MSC Initiating a TAnswer” task (see 4.W.1).
42
1-19-b ENDIF.
43
44 1-19-c IF the MSC is the Originating MSC:
45
46 O_Answer DP
47
1-19-c-1 IF the O_Answer trigger is armed for the calling subscriber:
48
49 1-19-c-1-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
50
51
1-19-c-1-2 Include the TriggerType parameter set to indicate O_Answer.
52
1-19-c-1-3 Execute the “MSC Initiating an OAnswer” task (see 4.U.1).
53
54 1-19-c-2 ENDIF.
55
56
57
58 1The Alerting Timer should be greater than the No Answer Timer.
59
60

PN-4287
1
1-19-d ENDIF.
2
1-19-1 Remove the ring back tone. 3
4
1-19-2 Connect the MS to the waiting call.
5
1-19-3 IF the OneTimeFeatureIndicator parameter was received and the Call Waiting 6
for future incoming calls field is not set to Ignore: 7
1-19-3-1 Set the Call Waiting for the existing call field in the 8
OneTimeFeatureIndicator parameter equal to the 9
OneTimeFeatureIndicator Call Waiting For Future Incoming Calls 10
field. 11
12
1-19-4 ELSE (the OneTimeFeatureIndicator parameter was not received or the Call
13
Waiting for Future Incoming Calls field is set to Ignore):
14
1-19-4-1 IF Call Waiting is active in the CallingFeaturesIndicator: 15
1-19-4-1-1 Set the Call Waiting for future incoming calls field in the 16
OneTimeFeatureIndicator parameter set to Normal CW. 17

18
1-19-4-2 ELSEIF Priority Call Waiting is active in the CallingFeaturesIndicator: 19
1-19-4-2-1 Set the Priority Call Waiting for future incoming calls field in the 20
OneTimeFeatureIndicator parameter set to Priority CW. 21
22
1-19-4-3 ELSE:
23
1-19-4-3-1 Set the Call Waiting for future incoming calls field in the 24
OneTimeFeatureIndicator parameter set to No CW. 25
1-19-4-4 ENDIF. 26
27
1-19-5 ENDIF:
28
1-20 WHEN the alerting timer expires: 29
1-20-1 Remove the ring back tone. 30

31
1-20-2 Connect the calling party to an announcement or tone to indicate that the
32
called party is not answering.
33
1-21 WHEN the no answer timer expires: 34
1-21-1 Include the RedirectionReason parameter set to No Answer. 35

36
1-21-2 IF this call has requested the None Reachable (NR) termination trigger AND 37
IF this is the last leg AND IF a GroupInformation parameter was received: 38
1-21-2-1 Include the GroupInformation parameter. 39
40
1-21-3 ELSEIF the LegInformation parameter was received:
41
1-21-3-1 Include the LegInformation parameter. 42
1-21-4 ENDIF. 43
44
1-21-5 IF the MSC is the Originating MSC:
45
T_No_Answer DP 46
47
T_Answer DP
48
1-21-5-1 IF the TriggerAddressList parameter includes an address for the 49
T_No_Answer trigger: 50
51
1-21-5-1-2 Execute the “MSC Initiating a TNoAnswer” task (see 4.N.1 53
54
4.M.1).
55
1-21-5-2 ELSE: 56
58
59
60

PN-4287
1
1-21-5-2-2 Execute the “MSC Initiating a Transfer-To-Number Request” task
2
(see 4.49.1).
3
4 1-21-5-3 ENDIF.
5
1-21-5-1 Execute the “MSC Initiating a Transfer-To-Number Request” task (see
6 4.49.1).
7
8
1-21-6 ELSEIF the Originating MSC is provisioned for call redirection:
9 1-21-6-1 Execute the “MSC Initiating a Redirection Request” task (see 4.36.1).
10
1-21-7 ELSE:
11
12
1-21-7-1 IF the TriggerAddressList parameter includes an address for the
13 T_No_Answer trigger:
14 1-21-7-1-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
15
16
1-21-7-1-2 Execute the “MSC Initiating a TNoAnswer” task (see 4.N.1
17 4.M.1).
18
1-21-7-2 ELSE:
19
20 1-21-7-2-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
21
1-21-7-2-2 Execute the “MSC Initiating a Transfer-To-Number Request” task
22
(see 4.49.1).
23
24 1-21-7-3 ENDIF.
25 1-21-7-1 Execute the “MSC Initiating a Transfer-To-Number Request” task (see
26 4.49.1).
27
1-21-8 ENDIF.
28
29 1-22 ENDWAIT.
30 2 ELSE (the indicated MS is busy):
31
32
2-1 IF Call Waiting is invoked (there is another call pending1 ) OR IF the MS is
33
otherwise unable to accept a call (e.g., the MS has invoked Priority Access and
34
Channel Assignment, Call Transfer, Conference Calling, Three-Way Calling or
35
the MS is not in a state where it can apply Call Waiting.):
36 2-1-1 GOTO Busy MS Detected.
37
2-2 ELSE (the MS may accept CW).
38
39 2-2-1 IF the RoutingDigits parameter is received:
40 2-2-1-1 Analyze the Routing digits to select an internal trunk group (such as, a
41 service monitor, scrambling device).
42
2-2-2 ENDIF.
43
44 2-2-3 Include the appropriate MS identifier (MobileIdentificationNumber or IMSI)
45 in the alerting command.
46
47
2-2-3 IF the MobileDirectoryNumber parameter is received:
48 2-2-3-1 Include the MobileDirectoryNumber parameter as the Called Number in the
49 MS alerting command.
50 2-2-4 ELSE:
51
2-2-4-1 Include the MobileIdentificationNumber parameter as the Called Number in
52
the MS alerting command.
53
54
55 1 MS busy or call pending can be defined as either a) actual calls in the MSC or b) a
56
combination of actual calls in the MSC or TLDNs assigned. Choice b) uses less of the
57
call redirection procedures and thereby routes calls faster. Choice a) handles abandoned
58
calls more properly.
59
60

PN-4287
2-2-5 ENDIF. 1
2
2-2-a IF the Terminating_Resource_Available trigger has been armed for the MS: 3
2-2-a-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X). 4
5
2-2-a-2 Execute the “MSC Initiating a Facility Selected And Available” task 6
(see 4.E.1). 7
2-2-b ENDIF. 8
9
2-2-6 Execute the “MSC CW Terminating Call Invocation” task (see 5.7.4). 10
2-2-7 IF Call Waiting is accepted: 11
12
2-2-7-1 GOTO Await Answer.
13
2-2-8 ELSE (Call Waiting was not accepted, the MS is busy): 14
Busy MS Detected: 15
16
T_Busy DP
17
2-2-8-1 IF a Trigger Address for the T_Busy trigger has been received for the 18
MS OR IF the MS has activated Call Forwarding—Busy or has the 19
Busy TerminationTriggers parameter set to launch a RedirectionRequest 20
or a TransferToNumberRequest or T_Busy: 21
22
2-2-8-1-1 Include the RedirectionReason parameter set to Busy. 23
2-2-8-1-2 IF this call has requested the None Reachable termination trigger 24
AND IF this is the last leg AND IF a GroupInformation parameter 25
was received: 26
27
2-2-8-1-2-1 Include the GroupInformation parameter.
28
2-2-8-1-3 ELSEIF the LegInformation parameter was received: 29
2-2-8-1-3-1 Include the LegInformation parameter. 30

31
2-2-8-1-4 ENDIF.
32
2-2-8-1-5 IF the call arrived via Call Delivery: 33
2-2-8-1-5-1 IF the Originating MSC is provisioned for call redirection: 34

35
2-2-8-1-5-1-1 Execute the “MSC Initiating a Redirection Request” task 36
(see 4.36.1). 37
2-2-8-1-5-2 ELSE: 38
39
2-2-8-1-5-2-1 IF the TriggerAddressList parameter includes a trigger
40
address for the T_Busy trigger:
41
2-2-8-1-5-2-1-1 Execute the “MSC Check of Serial Trigger Limit” 42
task (see 6.X). 43
44
45
4.M.1).
46
2-2-8-1-5-2-2 ELSE: 47
48
49
task (see 6.X).
50
2-2-8-1-5-2-2-2 Execute the “MSC Initiating a Transfer-To-Number 51
Request” task (see 4.49.1). 52
53
2-2-8-1-5-2-3 ENDIF.
54
2-2-8-1-5-2-1 Execute the “MSC Initiating a Transfer-To-Number Request” 55
task (see 4.49.1). 56
2-2-8-1-5-3 ENDIF. 57
58
2-2-8-1-6 ELSE (call did not arrive via Call Delivery):
59
60

PN-4287
1
2-2-8-1-6-1 IF the TriggerAddressList parameter includes a trigger address
2
for the T_Busy trigger:
3
4 2-2-8-1-6-1-1 Execute the “MSC Check of Serial Trigger Limit” task
5 (see 6.X).
6
2-2-8-1-6-1-2 Execute the “MSC Initiating a TBusy” task (see 4.M.1).
7
8 2-2-8-1-6-2 ELSE:
9
2-2-8-1-6-2-1 Execute the “MSC Check of Serial Trigger Limit” task
10
(see 6.X).
11
12 2-2-8-1-6-2-2 Execute the “MSC Initiating a Transfer-To-Number-
13 Request” task (see 4.49.1).
14
2-2-8-1-6-3 ENDIF.
15
16 2-2-8-1-6-1 Execute the “MSC Initiating a Transfer-To-Number Request” task
17 (see 4.49.1).
18 2-2-8-1-7 ENDIF.
19
2-2-8-2 ELSE (busy triggers do not apply):
20
21 2-2-8-2-1 Apply busy treatment to the waiting call (e.g., apply busy tone).
22 2-2-8-3 ENDIF.
23
24
2-2-9 ENDIF.
25 2-3 ENDIF.
26
3 ENDIF.
27
28
29
30
3 . 3 . 8 MSC Route the Call Leg Externally
31
32
33
Upon request, the MSC shall do the following:
34
35 1 Execute the “MSC Record the DMH Parameters” task (see 3.3.7).
36
2 IF the DMH_BillingDigits parameter is received:
37
38 2-1 Use the DMH_BillingDigits as the ISUP Charge Number or Automatic Number
39 Identification (ANI).
40 3 ELSEIF the MobileDirectoryNumber parameter is received:
41
42
3-1 Use the MobileDirectoryNumber as the ISUP Charge Number or Automatic
43
Number Identification (ANI).
44 4 ELSE:
45
4-1 Use the MobileIdentificationNumber as the ISUP Charge Number or Automatic
46
Number Identification (ANI).
47
48
5 ENDIF.
49 Select_Route PIC
50
6 IF the RoutingDigits parameter is received:
51
52 6-1 Analyze the routing digits to select an internal trunk group or an external
53 network address (such as, a roamer port, a private network hop-on point, virtual
54 private network hop-off point).
55 7 ENDIF.
56
57
8 IF the Digits (Carrier) parameter is received AND IF Carrier selection is appropriate:
58 8-1 Select the interexchange carrier based on the Digits (Carrier) digits.
59
9 ELSE:
60

PN-4287
1
9-1 Select the interexchange carrier based on internal algorithms.
2
10 ENDIF. 3
11 IF the ElectronicSerialNumber parameter is received within the 4
IntersystemTermination parameter. 5
6
11-1 Associate the ElectronicSerialNumber parameter with this call.
7
12 ENDIF. 8
13 IF the LegInformation parameter is received: 9

10
13-1 Store the LegInformation parameter to control subsequent redirections. 11
13-2 IF a BillingID parameter is received: 12
13
13-2-1 Associate the terminating BillingID parameter with this leg.
14
13-3 ENDIF. 15
14 ENDIF. 16
17
15 IF a PC_SSN parameter is received:
18
15-1 Store the PC_SSN for screening future call redirection attempts of this leg. 19
16 ENDIF. 20
21
17 IF an MSCID parameter is received:
22
17-1 Store the MSCID for screening future call redirection attempts of this leg. 23
18 ENDIF. 24
25
19 IF an MSCIdentificationNumber parameter is received: 26
19-1 Store the MSCIdentificationNumber for screening future call redirection attempts 27
of this leg. 28
29
20 ENDIF.
30
21 IF this is a call is originated by an MS at this MSC: 31
21-1 Execute the “MSC CNIP Originating Call Invocation” task (see 5.8.3). 32
33
22 ELSE (call must be being redirected at this MSC:
34
22-1 Execute the “MSC CNIP Redirecting Call Invocation” task (see 5.8.5). 35
23 ENDIF. 36
37
24 IF the TriggerAddressList parameter OR the TerminationTriggers parameter OR both
38
parameters are received: 39
24-1 IF the call is being redirected AND IF the TriggerAddressList parameter is 40
41
received:
42
24-1-1 Arm the triggers indicated by the received TriggerAddressList parameter for 43
the redirected call. Note: the TerminationTriggers parameter does not apply 44
45
for redirected calls.
46
24-2 ELSE: 47
48
24-2-1 IF the TerminationTriggers parameter is received: 49
50
24-2-1-1 Use these TerminationTriggers instead of the profile event triggers for
51
this call. 52
53
24-2-2 ENDIF.
54
24-2-3 IF the TriggerAddressList parameter is received: 55
56
24-2-3-1 Disarm any previously armed subscribed WIN triggers for the 57
remainder of the call in progress. 58
59
60

PN-4287
1
24-2-3-2 Arm the triggers indicated by the received TriggerAddressList
2
3
parameter for the remainder of the call in progress.
4
24-2-4 ENDIF.
5
6 24-3 ENDIF.
7
24-1 Use the received trigger arming and trigger address information instead of using the
8
event trigger information from the MS’s profile.
9
10 2 4 IF the TerminationTriggers parameter is received.
11 24-1 Use these TerminationTriggers instead of the profile event triggers for this call.
12
25 ENDIF.
13
14 26 IF a Digits (Destination) parameter is received:
15 26-1 Set destination to Digits (Destination).
16
17
27 ELSE IntersystemTermination parameter is received.
18 27-1 Set destination to the DestinationDigits parameter within the
19 IntersystemTermination parameter.
20
27-2 Set MSCID for this leg to the MSCID parameter within the
21
IntersystemTermination parameter.
22
23
27-3 IF the BillingID parameter is received within the IntersystemTermination
24
parameter.
25 27-3-1 Associate the terminating BillingID parameter with this call leg.
26
27-4 ENDIF.
27
28 27-5 IF the CarrierDigits parameter is received within the IntersystemTermination
29 parameter.
30 27-5-1 Use these carrier digits instead of other carrier digits.
31
27-6 ENDIF.
32
33 27-7 IF the ElectronicSerialNumber parameter is received within the
35 27-7-1 Associate the ElectronicSerialNumber parameter with this call leg.
36
37
27-8 ENDIF.
38 27-9 IF the LegInformation parameter is receive within the IntersystemTermination
39 parameter.
40
27-9-1 Associate the LegInformation parameter with this call leg.
41
42
27-10 ENDIF.
43 27-11 IF the MobileIdentificationNumber parameter is received within the
45
27-11-1 Associate the MobileIdentificationNumber parameter with this call leg.
46
47 27-12 ENDIF.
48 27-13 IF the MSCIdentificationNumber parameter is received within the
50
27-13-1 Associate the MSCIdentificationNumber with this call leg.
51
52 27-14 ENDIF.
53 27-15 IF the RoutingDigits parameter is received within the IntersystemTermination
54 parameter.
55
56
27-15-1 Use these routing digits instead of other routing digits for this call leg.
57 27-16 ENDIF.
58
27-17 IF the TerminationTriggers parameter is received within the
59
IntersystemTermination parameter.
60

PN-4287
1
27-17-1 Use these TerminationTriggers for this call leg, if received, instead of using
2
other event triggers trigger information for this call leg.
3
27-18 ENDIF. 4
5
28 ELSEIF PSTNTermination parameter is received.
6
28-1 Set destination to DestinationDigits within the PSTNTermination parameter. 7
28-2 IF the CarrierDigits parameter is received within the PSTNTermination 8
parameter. 9
10
28-2-1 Use these carrier digits instead of other carrier digits.
11
28-3 ENDIF. 12
28-4 IF the ElectronicSerialNumber parameter is received within the 13
PSTNTermination parameter. 14
15
28-4-1 Associate the ElectronicSerialNumber parameter with this call leg.
16
28-5 ENDIF. 17
28-6 IF the LegInformation parameter is received within the PSTNTermination 18
parameter. 19
20
28-6-1 Associate the LegInformation with this call leg. 21
28-7 ENDIF. 22
23
28-8 IF the MobileIdentificationNumber parameter is received within the
24
PSTNTermination parameter.
25
28-8-1 Associate the MobileIdentificationNumber parameter with this call leg. 26
28-9 ENDIF. 27
28
28-10 IF the RoutingDigits parameter is received within the PSTNTermination
29
parameter.
30
28-10-1 Use these routing digits instead of other routing digits for this call leg. 31
28-11 ENDIF. 32
33
28-12 IF the TerminationTriggers parameter is received within the PSTNTermination
34
parameter.
35
28-12-1 Use these TerminationTriggers for this call leg, if received, instead of using 36
other event triggers trigger information for this call leg. 37
38
28-13 ENDIF.
39
29 ELSE (Digits (Destination), IntersystemTermination, OR PSTNTermination 40
parameter not received): 41
29-1 Return to the calling task. 42

43
30 ENDIF.
44
Send_Call PIC 45
46
31 Process a call setup toward the destination via the route and selected carrier.
47
32 Cut through the voice path in the reverse direction (to allow the calling party to hear 48
call process tones). 49
O_Alerting PIC 50
51
33 Start an alerting timer.
52
34 IF the TriggerAddressList parameter OR the TerminationTriggers parameter OR both 53
parameters are received: 54
55
3 4 IF the TerminationTriggers parameter is received:
56
34-1 Store the TerminationTriggers parameter for this leg, if received, and store 57
theTriggerAddressList parameter for this leg, if received. 58
59
60

PN-4287
1
34-2 IF the NoAnswer trigger is requested in the TerminationTriggers parameter OR
2
3
IF the T_No_Answer trigger is armed by the TriggerAddressList parameter:
4
34-2-1 IF the NoAnswerTime parameter is received:
5
6
34-2-1-1 Start a no answer timer with the value in the received NoAnswerTime
7
parameter.
8 34-2-2 ELSE:
9
34-2-2-1 Start a no answer timer with a system default value.
10
11 34-2-3 ENDIF.
12 34-3 ENDIF.
13
35 ENDIF.
14
15 36 WAIT for the trunk to be answered.
16 37 WHEN a routing failure is detected:
17
18
37-1 IF the RoutingFailure termination trigger point is active:
19 37-1-1 Include the RedirectionReason parameter set to Unroutable.
20
37-1-2 IF this call has requested the None Reachable termination trigger AND IF
21
this is the last leg AND IF a GroupInformation parameter was received:
22
23
37-1-2-1 Include the GroupInformation parameter.
24 37-1-3 ELSEIF the LegInformation parameter was received:
25
37-1-3-1 Include the LegInformation parameter.
26
27 37-1-4 ENDIF.
28 37-1-5 IF a trigger address for the T_Unroutable trigger has been received:
29
30
37-1-5-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
31 37-1-5-2 Execute the “MSC Initiating a TBusy” task (see 4.M.1).
32
37-1-6 ELSE:
33
35
37-1-6-2 Execute the “MSC Initiating a Transfer-To-Number Request” task (see
36
4.49.1).
37
38 37-1-5 Execute the “MSC Initiating a Transfer-To-Number Request” task (see 4.49.1).
39 37-2 ELSE:
40
41
37-2-1 Remain in this state (to wait for the calling party to disconnect).
42 37-3 ENDIF.
43
38 WHEN a busy is detected:
44
45
T_Busy DP
46
38-1 IF the Busy termination trigger point is active:
47
48
38-1-1 Include the RedirectionReason parameter set to Busy.
49 38-1-2 IF this call has requested the None Reachable termination trigger AND IF
50 this is the last leg AND IF a GroupInformation parameter was received:
51
38-1-2-1 Include the GroupInformation parameter.
52
53 38-1-3 ELSEIF the LegInformation parameter was received:
54 38-1-3-1 Include the LegInformation parameter.
55
38-1-4 ENDIF.
56
57 38-1-5 IF a trigger address for the T_Busy trigger has been received:
58
59
60

PN-4287
1
38-1-5-2 Execute the “MSC Initiating a TBusy” task (see 4.M.1).
2
38-1-6 ELSE: 3
4
5
38-1-6-2 Execute the “MSC Initiating a Transfer-To-Number Request” task (see 6
4.49.1). 7
8
38-1-7 ENDIF.
9
38-1-5 Execute the “MSC Initiating a Transfer-To-Number Request” task (see 4.49.1). 10
38-2 ELSE: 11
12
38-2-1 Remain in this state (to wait for the calling party to disconnect).
13
38-2-2 ENDIF. 14
38-3 ENDIF. 15
16
T_No_Answer DP
17
a WHEN the no answer timer expires: 18

19
a-1 Include the RedirectionReason parameter set to indicate No Answer. 20
21
a-2 IF this call has requested the None Reachable termination trigger AND IF this is
22
the last leg AND IF a GroupInformation parameter was received: 23
24
a-2-1 Include the GroupInformation parameter.
25
a-3 ELSEIF the LegInformation parameter was received: 26
27
a-3-1 Include the LegInformation parameter. 28
a-4 ENDIF. 29
30
a-5 IF a trigger address for the T_No_Answer trigger has been received: 31
32
33
a-5-2 Execute the “MSC Initiating a TNoAnswer” task (see 4.N.1). 34

35
a-6 ELSE: 36
37
38
a-6-2 Execute the “MSC Initiating a Transfer-To-Number Request” task (see 39
40
4.49.1).
41
a-7 ENDIF. 42
43
39 WHEN the trunk is answered: 44
O_Answer DP 45
46
O_Active PIC
47
39-a IF the O_Answer trigger is armed: 48
49
39-a-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X). 50
39-a-2 Set the TriggerType parameter to indicate O_Answer. 51

52
39-a-3 Execute the “MSC Initiating an OAnswer” task (see 4.U.1) 53
54
39-b ENDIF.
55
T_Answer DP 56
57
39-c IF the T_Answer trigger is armed: 58
59
60

PN-4287
1
39-c-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
2
3 39-c-2 Set the TriggerType parameter to indicate T_Answer.
4
5
39-c-3 Execute the “MSC Initiating a TAnswer” task (see 4.W.1)
6
39-d ENDIF.
7
8 39-1 Cut through the voice path in the forward direction (to allow the calling party to
9 communicate with the called party).
10
40 WHEN the trunk disconnect is detected:
11
12
40-1 Release the trunk.
13 40-2 Execute the “Other Party Disconnect” task (see 3.4.2).
14
15
41 WHEN the alerting timer expires:
16 41-1 Connect the calling party to an announcement or tone to indicate that the called
17 party is not answering.
18
4 2 WHEN the no answer timer expires:
19
42-1 Include the RedirectionReason parameter set to No Answer.
20
21 42-2 IF this call has requested the None Reachable termination trigger AND IF this is the
22 last leg AND IF a GroupInformation parameter was received:
23 42-2-1 Include the GroupInformation parameter.
24
42-3 ELSEIF the LegInformation parameter was received:
25
42-3-1 Include the LegInformation parameter.
26
27 42-4 ENDIF.
28 42-5 IF a trigger address for the T_No_Answer trigger has been received:
29
30
31 42-5-2 Execute the “MSC Initiating a TNoAnswer Request” task (see 4.N.1).
32 42-6 ELSE:
33
34
35 42-6-2 Execute the “MSC Initiating a Transfer-To-Number Request” task (see 4.49.1).
36
42-7 ENDIF.
37
38
42-5 Execute the “MSC Initiating a Transfer-To-Number Request” task (see 4.49.1).
39 43 ENDWAIT.
40
44 Exit this task.
41
42
43 3.4 DISCONNECT CALL TASKS
44
45
46
47
3 . 4 . 1 MS Disconnect
48 (TIA/EIA-41.6-D, page 6-39)
49
50
1 IF the current system is the Anchor MSC:
51 1-1 IF this was not a simple feature code access:
52
1-1-1 Clear the OneTimeFeatureIndicator parameter.
53
54 1-1-2 Clear the Conference Calling internal processing mode.
55 1-2 ENDIF.
56
2 ENDIF.
57
58
59
60

PN-4287
1
3 FOR each leg of the call other than the subscriber leg (i.e., disconnecting MS call
2
leg) all of the other legs associated with this leg: 3
4
3-1 IF the T_Disconnect trigger is armed for this leg:
5
7
3-1-2 Set the TriggerType parameter to indicate T_Disconnect. 8
3-1-3 Include the ReleaseCause parameter set to indicate Called party. 9

10
3-1-4 Execute the “MSC Initiating a TDisconnect” task (see 4.X.1). 11
12
3-2 ELSEIF the O_Disconnect trigger is armed for this leg:
13
15
3-2-2 Set the TriggerType parameter to indicate O_Disconnect. 16
17
3-2-3 Include the ReleaseCause parameter set to indicate Calling party.
18
3-2-4 Execute the “MSC Initiating a ODisconnect” task (see 4.V.1). 19
20
3-3 ENDIF. 21
22
3-4 Disconnect leg.
23
3-1 Disconnect leg. 24
4 ENDFOR. 25
26
5 IF the current system is the serving system: 27
5-1 Release the voice channel to the MS. 28
29
6 ENDIF.
30
32
3 . 4 . 2 Other Party Disconnect 33

34
(TIA/EIA-41.6-D, page 6-39) 35
36
1 IF the other party was the only party in an active connection (i.e., not in a 3WC,
37
CC, or on hold):
38
1-1 IF this was not a simple feature code access: 39
1-1-1 Clear the OneTimeFeatureIndicator parameter. 40

41
1-1-2 Clear the Conference Calling internal processing mode.
42
1-2 ENDIF. 43
2 ENDIF. 44
45
a IF the T_Disconnect trigger is armed for the call leg to the other party: 46
a-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X). 47
48
a-2 Set the TriggerType parameter to indicate T_Disconnect. 49
50
a-3 Include the ReleaseCause parameter set to indicate Calling party.
51
a-4 Execute the “MSC Initiating an TDisconnect” task (see 4.V.1). 52

53
b ELSEIF the O_Disconnect trigger is armed for the call leg to the other party: 54
55
b-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
56
b-2 Set the TriggerType parameter to indicate O_Disconnect. 57
58
b-3 Include the ReleaseCause parameter set to indicate Called party. 59
60

PN-4287
1
b-4 Execute the “MSC Initiating an ODisconnect” task (see 4.X.1).
2
3 c ENDIF.
4
5
3 IF the MSC is the Serving MSC:
6 3-1 Release the voice channel to the MS.
7
4 ENDIF.
8
9 5 Exit this task.
10
11
12
3 . 4 . 3 Commanded Disconnect
13 (TIA/EIA-41.6-D, page 6-39)
14
1 IF the MSC is the Anchor MSC:
15
16 1-1 IF the other party was the only party in an active connection (i.e., not in a
17 3WC, CC, or on hold):
18 1-1-1 IF this was not a simple feature code access:
19
20
1-1-1-1 Clear the OneTimeFeatureIndicator parameter.
21 1-1-1-2 Clear the Conference Calling internal processing mode.
22
1-1-2 ENDIF.
23
24
1-2 ENDIF.
25 1-3 FOR each leg of the call other than the subscriber call leg all of the other legs
26
associated with this leg:
27
28
1-3-a IF the T_Disconnect trigger is armed for this leg:
29
30
31 1-3-a-2 Set the TriggerType parameter to indicate T_Disconnect.
32
33
1-3-a-3 Include the ReleaseCause parameter set to indicate Commanded
34 Disconnect.
35
1-3-a-4 Execute the “MSC Initiating a TDisconnect” task (see 4.X.1).
36
37 1-3-b ELSEIF the O_Disconnect trigger is armed for this leg:
38
39 1-3-b-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
40
1-3-b-2 Set the TriggerType parameter to indicate O_Disconnect.
41
42 1-3-b-3 Include the ReleaseCause parameter set to indicate Commanded
43
Disconnect.
44
45 1-3-b-4 Execute the “MSC Initiating an ODisconnect” task (see 4.V.1).
46
47
1-3-c ENDIF.
48 1-3-1 Disconnect leg.
49
50
1-4 ENDFOR.
51 2 ENDIF.
52
x IF the MSC is being directed to Release leg and redirect subscriber (i.e., ActionCode
53
54
parameter received with value of Release leg and redirect subscriber):
55 x-1 Return to the calling task.
56
57 y ENDIF.
58
3 IF the current system is the serving system:
59
60

PN-4287
1
3-1 Release the voice channel to the MS.
2
4 ELSE: 3
4-1 Release the handoff trunk toward the serving system. 4

5
5 ENDIF.
6
6 Exit this task. 7
8
9
4.14 FEATURE REQUEST 10
11
12
4.14.1 MSC Detecting Feature Request 13

14
15
When performing digit analysis of the dialed digits received from the MS, the MSC 16
detects that the dialed digits are a feature control access. It shall perform the following: 17
18
1 Include the BillingID parameter set to identify the current call for billing and 19
redirection purposes. 20
2 Include the Digits (Dialed) parameter set to the digits received from the MS. 21
22
3 Include the ElectronicSerialNumber parameter set to identify the MS. 23
4 Include the MobileIdentificationNumber parameter set to identify the MS. 24
25
5 Include the MSCID parameter set to the identity of the MSC.
26
6 IF any indicator is set in the OneTimeFeatureIndicator parameter: 27
6-1 Include the OneTimeFeatureIndicator parameter. 28
29
7 ENDIF.
30
8 Include SenderIdentificationNumber parameter set to the identification number of the 31
MSC. 32
9 Include TransactionCapability parameter set appropriately. 33

34
10 IF the subscriber is involved in a conference call:
35
10-1 Include the ConferenceCallingIndicator parameter set to the number of conferees 36
currently in the call. 37
11 ENDIF. 38
39
12 Send a FeatureRequest INVOKE to the HLR associated with the MS. 40
13 Start the Feature Request Response Timer (FRRT). 41
42
14 WAIT for Feature Request response:
43
15 WHEN a RETURN RESULT is received: 44
15-1 Stop timer (FRRT). 45
46
15-2 IF the message can be processed:
47
15-2-1 IF the MS is still connected: 48
15-2-1-1 IF the AnnouncementList parameter is received: 49

50
15-2-1-1-1 Execute the “Play All Announcements in the AnnouncementList”
51
task (see 3.2.5).
52
15-2-1-2 ELSEIF the FeatureResult parameter indicates Successful operation: 53
15-2-1-2-1 Provide a successful indication to the MS. 54

55
15-2-1-3 ELSE: 56
15-2-1-3-1 Provide an unsuccessful indication to the MS. 57
58
15-2-1-4 ENDIF.
59
60

PN-4287
1
15-2-1-5 IF the OneTimeFeatureIndicator parameter is received:
2
3 15-2-1-5-1 Store the received OneTimeFeatureIndicator parameter.
4 15-2-1-6 ENDIF.
5
15-2-1-a IF the TriggerAddressList parameter is received:
6
7 15-2-1-a-1 If the call is being redirected:
8
9 15-2-1-a-1-1 Arm the triggers indicated by the TriggerAddressList parameter
10 for the redirected call.
11
12
15-2-1-a-2 ELSE:
13
15-2-1-a-2-1 Disarm any previously armed subscribed WIN triggers for the
14
15
remainder of the call in progress.
16 15-2-1-a-2-2 Arm the triggers indicated by the TriggerAddressList parameter
17
for the remainder of the call in progress.
18
19 15-2-1-a-3 ENDIF.
20
21 15-2-1-b ENDIF.
22
15-2-1-7 IF the ConferenceCallingIndicator parameter is received:
23
24 15-2-1-7-1 Execute the “MSC CC Invocation” task (see 5.10.3).
25 15-2-1-8 ENDIF.
26
15-2-1-9 IF an ActionCode parameter is received:
27
28 15-2-1-9-1 Execute the “MSC ActionCode Processing” task (see 3.2.9)
29 15-2-1-10 ENDIF.
30
31
15-2-1-11 IF the MS is in a state capable of routing a call (e.g., after dialing a
32
feature code from an idle state or a call hold state).
33 15-2-1-11-1 IF the TerminationList parameter is received:
34
35
15-2-1-11-1-1 IF WIN triggers remain to be processed at the
36 Collected_Information or the Analyzed_Information DP:
37
15-2-1-11-1-1-1 Return to the calling task.
38
39 15-2-1-11-1-2 ELSE:
40
41 15-2-1-11-1-2-1 Execute the “MSC Routing Points Of Return” task (see
42 3.2.6).
43
44
15-2-1-11-1-3 ENDIF.
45 15-2-1-11-1-1 Execute the “MSC Routing Points Of Return” task (see 3.2.6).
46
47
15-2-1-11-2 ENDIF.
48 15-2-1-12 ENDIF.
49
15-2-1-13 IF Digits (Dialed) parameter is received:
50
51
15-2-1-13-1 Set MS dialed digits to the received Digits (Dialed) parameter
52 value.
53 15-2-1-13-2 IF the type of digits is unknown:
54
55
15-2-1-13-2-1 Process the dialed number locally to set the PointOfReturn.
56 15-2-1-13-3 ENDIF.
57
58
15-2-1-13-4 IF WIN triggers remain to be processed at the
59 Collected_Information or the Analyzed_Information DP:
60
TIA/EIA-41.6-D Modifications 6-35 4.14 Feature Request

PN-4287
1
15-2-1-13-4-1 Return to the calling task.
2
15-2-1-13-5 ENDIF. 3
4
15-2-1-14 ELSE: 5
15-2-1-14-1 Use Digits (Dialed) parameter included in the FeatureRequest 6
INVOKE as MS dialed digits. 7

8
15-2-1-15 ENDIF. 9
15-2-1-16 IF the ResumePIC parameter is received: 10

11
15-2-1-16-1 IF the value of the ResumePIC parameter is Continue Call 12
Processing: 13
15-2-1-16-1-1 Return to the calling task. 14

15
15-2-1-16-2 ELSEIF the value of the ResumePIC parameter is a valid 16
transition: 17
15-2-1-16-2-1 GOTO the entry point indicated by the ResumePIC parameter. 18

19
15-2-1-16-3 ELSE: 20
15-2-1-16-3-1 Execute “Local Recovery Procedures” task (see 3.5.1). 21
22
15-2-1-16-3-2 Exit this task.
23
15-2-1-16-4 ENDIF. 24
25
15-2-1-17 ELSE:
26
15-2-1-17-1 GOTO AuthorizedSubscriberOrigination (see 3.2.3). 27
28
15-2-1-18 ENDIF.
29
15-2-1-13-1 Execute the “MSC Analyze MS Dialed Number” task (see 3.2.3) 30
(without re-querying the HLR for the same digits).
31
15-2-1-14 ENDIF. 32
15-2-2 ENDIF. 33
34
15-3 ELSE (the message cannot be processed): 35
37
15-3-2 IF the MS is still connected:
38
15-3-2-1 Provide an unsuccessful indication to the MS. 39
15-3-3 ENDIF. 40
41
15-4 ENDIF.
42
16 WHEN a RemoteUserInteractionDirective INVOKE is received: 43

45
16-2 Execute the “MSC Remote User Interaction” task (see 4.39.2). 46
16-3 Start the Feature Request Response Timer (FRRT). 47
48
16-4 Remain in this state.
49
17 WHEN a RETURN ERROR or REJECT is received: 50
52
17-2 Execute “Local Recovery Procedures” task (see 3.5.1).
53
17-3 IF the MS is still connected: 54
17-3-1 Provide an unsuccessful indication to the MS. 55

56
17-4 ENDIF.
57
18 WHEN the MS disconnects: 58
18-1 Remain in this state (to handle possible call abandons). 59

60
4.14 Feature Request 6-36 TIA/EIA-41.6-D Modifications

PN-4287
1
19 WHEN timer (FRRT) expires:
2
3 19-1 Execute “Local Recovery Procedures” task (see 3.5.1).
4 19-2 IF the MS is still connected:
5
19-2-1 Provide an unsuccessful indication to the MS.
6
7 19-3 ENDIF.
8 20 ENDWAIT.
9
10
21 Exit this task.
11
12
13
4.24 INTERSYSTEM ANSWER
14
15
16 4.24.1 MSC Awaiting InterSystemAnswer
17 (TIA/EIA-41.6-D, page 6-173)
18
19 When the MSC determines that it should wait for an InterSystemAnswer message, it
20 shall do the following:
21
22
1 Start the InterSystemAnswer Response Timer (ISART).
23 2 WAIT for an InterSystemAnswer INVOKE:
24
3 WHEN an InterSystemAnswer INVOKE is received from the border system:
25
26
3-1 Stop the timer (ISART).
27 3-2 Send an InterSystemAnswer RETURN RESULT to the Border MSC.
28
3-a IF the T_Answer trigger is armed:
29
30 3-a-1 Execute the “MSC Check of Serial Trigger Limit” task (see 6.X).
31
32
3-a-2 Set the TriggerType parameter to indicate T_Answer.
33
3-a-3 Execute the “MSC Initiating a TAnswer” task (see 4.W.1).
34
35 3-b ENDIF.
36
37
3-3 Connect the call path.
38 NOTE: After the call has been established, a subsequent handoff to the visited
39 (Anchor) MSC should be treated as a Handoff Back.
40
4 WHEN a FacilitiesRelease INVOKE is received (see 4.13.2):
41
42
4-1 Stop the timer (ISART).
43 5 WHEN the (ISART) timer expires:
44
5-1 Include the ReleaseReason parameter indicating clear forward.
45
46 5-2 Execute the “Initiating MSC Initiating a Facilities Release” task (see 4.13.1).
48
6 ENDWAIT.
49
50 7 Exit this task.
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41.6-D Modifications 6-37 4.14 Feature Request

PN-4287
1
2
4.28 LOCATION REQUEST 3
4
5
4.28.1 MSC Initiating a Location Request 6

7
8
9
When an MSC receives a call destined toward an MS and the received Directory Number
10
(DN) is not a TLDN assigned by the MSC, it shall perform the following:
11
1 Include the MSCID (Originating) parameter set to the identity of the MSC. 12
13
2 Include the MSCIdentificationNumber parameter set to the identification number of
14
the MSC.
15
3 Include the TerminationAccessType parameter set to the source of the request (e.g., 16
PSTN, roamer port, private network trunk group). 17
4 Include the BillingID (Originating) parameter set to the billing identifier for the call 18
assigned by the current Originating MSC. 19

20
5 Include the Digits (Dialed) parameter set to the dialed or called digits used to access a
21
mobile subscriber. (This is the digits dialed after reaching a roamer port.)
22
6 Include the SystemMyTypeCode parameter set to the manufacturer of the Originating 23
MSC. 24
7 Include the TransactionCapability parameter indicating the MSC’s capability for this 25
transaction. 26
27
a IF the Location trigger was detected: 28
a-1 Set the Trigger Flag to Location. 29
30
b ELSE:
31
b-1 Set the Trigger Flag to Mobile Termination. 32
33
c ENDIF.
34
d Include the WINCapability parameter indicating the MSC’s WIN capability for this 35
transaction. 36
37
e Include the TriggerType parameter to indicate the trigger encountered.
38
8 IF the network validated calling party number is known: 39
8-1 Include the CallingPartyNumberDigits1 parameter. 40

41
9 ENDIF. 42
10 IF the user provided calling party number is known: 43
44
10-1 Include the CallingPartyNumberDigits2 parameter.
45
11 ENDIF. 46
12 IF the calling party subaddress is known: 47
48
12-1 Include the CallingPartySubaddress parameter.
49
13 ENDIF. 50
a IF the calling name information is known: 51

52
a-1 Include the CallingPartyName parameter. 53
b ENDIF. 54
55
14 IF the message is to be launched on an SS7 network:
56
14-1 IF the MSC is the home MSC for the indicated directory number: 57
14-1-1 Include the PC_SSN parameter with the Type set to Home MSC and the 58
PC and SSN fields set to the MSC’s point code and subsystem number. 59
60
4.28 Location Request 6-38 TIA/EIA-41.6-D Modifications

PN-4287
1
14-2 ELSE:
2
3 14-2-1 Include the PC_SSN parameter with the Type set to Originating MSC and
4 the PC and SSN fields set to the MSC’s point code and subsystem number.
5 14-3 ENDIF.
6
15 ENDIF.
7
8 16 IF the received call was redirected (before arrival to the Originating MSC):
9 16-1 IF the redirecting number is known:
10
11
16-1-1 Include the RedirectingNumberDigits parameter.
12 16-2 ENDIF.
13
16-3 IF the redirecting subaddress is known:
14
15
16-3-1 Include the RedirectingSubaddress parameter.
16 16-4 ENDIF.
17
16-5 IF the redirecting name information is known:
18
19 16-5-1 Include the RedirectingPartyName parameter.
20
16-6 ENDIF.
21
22 17 ENDIF.
23 18 Optionally provide call progress tone or announcement to the caller.
24
19 Send a LocationRequest INVOKE to the indicated MS’s HLR.
25
26 20 Start the Location Request Timer (LRT).
27 21 WAIT for a Location Request response:
28
29
22 WHEN a RETURN RESULT is received:
30 Location Request RETURN RESULT Treatment:
31
22-1 Stop the timer (LRT), if the timer is still running.
32
33 22-2 IF the message can be processed:
34 22-2-1 IF the incoming call is still connected:
35
36
22-2-1-1 IF the OneTimeFeatureIndicator parameter is received:
37 22-2-1-1-1 Store the OneTimeFeatureIndicator parameter to modify subsequent
38 call processing actions for this call.
39
22-2-1-2 ENDIF.
40
41
22-2-1-x IF the ControlNetworkID parameter is received:
42
22-2-1-x-1 Store the parameter value to correlate potential UnreliableCallData
43
44
operations.
45 22-2-1-y ENDIF.
46
47 22-2-1-3 IF the AccessDeniedReason parameter is received:
48 22-2-1-3-1 IF the AccessDeniedReason parameter can be acted upon:
49
50
22-2-1-3-1-1 IF the AnnouncementList parameter is received:
51 22-2-1-3-1-1-1 Execute the “Play All Announcements in the
52 AnnouncementList” task (see 3.2.5).
53
22-2-1-3-1-1-2 Optionally provide the treatment indicated in the
54
AccessDeniedReason parameter.
55
56
22-2-1-3-1-2 ELSE:
57 22-2-1-3-1-2-1 Provide the treatment indicated in the AccessDeniedReason
58 parameter.
59
60
TIA/EIA-41.6-D Modifications 6-39 4.28 Location Request

PN-4287
1
22-2-1-3-1-3 ENDIF.
2

5
22-2-1-3-1-4 ENDIF.
6
22-2-1-3-2 ENDIF. 7
22-2-1-4 ENDIF. 8
9
22-2-1-a IF the TriggerAddressList parameter is received: 10
22-2-1-a-1 If the call is being redirected: 11
12
22-2-1-a-1-1 Arm the triggers indicated by the received TriggerAddressList 13
parameter for the redirected call. 14
15
22-2-1-a-2 ELSE: 16
22-2-1-a-2-1 Disarm any previously armed subscribed WIN triggers for the 17
18
19

21
22
22-2-1-a-3 ENDIF. 23
24
22-2-1-a-1 Arm the indicated triggers.
25
22-2-1-b ENDIF. 26
27
22-2-1-5 IF the Digits (Destination) parameter is included:
28
22-2-1-5-1 IF the AnnouncementList parameter is received: 29
22-2-1-5-1-1 Execute the “Play All Announcements in the 30
AnnouncementList” task (see 3.2.5). 31

32
22-2-1-5-2 ELSE: 33
22-2-1-5-2-1 Optionally provide call progress tones or announcements to 34
the calling party. 35
36
22-2-1-5-3 ENDIF.
37
22-2-1-5-a IF WIN triggers remain to be processed at the 38
Analyzed_Information DP: 39
40
22-2-1-5-a-1 Return to the calling task. 41
22-2-1-5-b ENDIF. 42
43
22-2-1-5-4 Execute the “MSC Route the Call Leg Externally” task (see 3.3.8). 44
22-2-1-6 ELSEIF the TerminationList parameter is included: 45

46
22-2-1-6-1 IF the AnnouncementList parameter is received: 47
22-2-1-6-1-1 Execute the “Play All Announcements in the 48
AnnouncementList” task (see 3.2.5). 49
50
22-2-1-6-2 ELSE:
51
22-2-1-6-2-1 Optionally provide call progress tones or announcements to 52
the calling party. 53
22-2-1-6-3 ENDIF. 54
55
22-2-1-6-a IF WIN triggers remain to be processed at the
56
58
22-2-1-6-a-1 Return to the calling task.
59
60

PN-4287
1
22-2-1-6-b ENDIF.
2
3 22-2-1-6-4 Execute the “MSC Routing Points of Return” task (see 3.2.6).
4
22-2-1-7 ELSEIF the received MSCID parameter is the same as this MSC’s ID:
5
6 22-2-1-7-1 IF the AnnouncementList parameter is received:
7 22-2-1-7-1-1 Execute the “Play All Announcements in the
8 AnnouncementList” task (see 3.2.5).
9
22-2-1-7-2 ELSE:
10
11 22-2-1-7-2-1 Optionally provide call progress tones or announcements to
12 the calling party.
13 22-2-1-7-3 ENDIF.
14
15
22-2-1-7-4 Execute the “Authorize MS Termination Attempt” task for the MS
16
identified by the received MobileIdentificationNumber or IMSI
17 parameter (see 3.3.4).
18 22-2-1-8 ELSE (There is insufficient information to route the call.):
19
20
22-2-1-8-1 IF the Trigger Flag is set to Mobile Termination AND IF WIN
21 triggers that precede the Location trigger are armed for the
22 subscriber:
23
24
22-2-1-8-1 IF the Trigger Flag is set to Mobile Termination AND IF the
25
Advanced_Termination trigger is armed:
26 22-2-1-8-1-1 Return to the calling task.
27
28
22-2-1-8-2 ELSE:
29 22-2-1-8-2-1 Execute the “Local Recovery Procedures” task (see 3.5.1).
30
31
32 22-2-1-8-3 ENDIF.
33
22-2-1-8-1 Execute “Local Recovery Procedures” task (see 3.5.1).
34
35
22-2-1-9 ENDIF.
36 22-2-2 ELSE (the call is disconnected):
37
22-2-2-1 Execute “Local Recovery Procedures” task (see 3.5.1).
38
39 22-2-2-2 Exit this task.
40 22-2-3 ENDIF.
41
22-3 ELSE (the message cannot be processed):
42
43 22-3-1 Execute “Local Recovery Procedures” task (see 3.5.1).
45
46
22-4 ENDIF.
47 23 WHEN a RemoteUserInteractionDirective INVOKE is received:
48
23-1 Stop timer (LRT).
49
50
23-2 Execute the “MSC Remote User Interaction” task (see 4.39.2).
51 23-3 Start the Location Request Timer (LRT).
52
23-4 Remain in this state (to get further routing instructions).
53
54 a WHEN a ConnectResource INVOKE is received:
55 a-1 Stop the timer (LRT).
56
57
a-2 Execute the “MSC Receiving ConnectResource INVOKE” task (see 4.B.3).
58 a-3 CASE MSC Connect Resource result OF:
59
60

PN-4287
1
a-4 Disconnect Resource received:
2
a-4-1 Start the timer (LRT). 3
4
a-4-2 Remain in this state.
5
a-5 LocationRequest RETURN RESULT received: 6
a-5-1 GOTO LocationRequest RETURN RESULT Treatment. 7

8
a-6 SSFT expiration: 9

11
a-6-2 Remain in this state. 12
a-7 call abandoned: 13
14
a-7-1 Execute the “Local Recovery Procedures” task (see 3.5.1).
15
a-8 resource disconnect: 16
17
a-8-1 Start the timer (LRT).
18
20
a-9 failure at MSC:
21

24
a-10 message error: 25

27
a-11 ENDCASE. 29
30
24 WHEN the incoming call disconnects:
31

34
25-1 Stop timer (LRT). 35
25-2 Execute “Local Recovery Procedures” task (see 3.5.1). 36
37
26 WHEN timer (LRT) expires:
38
27 ENDWAIT. 40
41
28 Exit this task.
42
43
4.28.2 HLR Receiving LocationRequest INVOKE 44

45
46
When an HLR receives a LocationRequest INVOKE, it shall perform the following:1 47

48
1 IF the received message can be processed: 49
1-a IF the received TriggerType parameter indicates the Mobile_Termination trigger 50

51
has been encountered AND IF there are WIN triggers required for providing
52
services to the subscriber AND IF the received WINCapability parameter 53
indicates the triggers are supported: 54
55
56
1Note that the feature interaction is per TIA/EIA-664 IS-53 and may be different in actual 57
58
implementations.
59
60

PN-4287
1 1-a IF the subscriber record indicates the Advanced_Termination trigger is active AND IF
2
the received TriggerType parameter indicates the Mobile_Termination trigger has
3
been encountered AND IF the received WINCapability parameter indicates the
4
Advanced_Termination trigger is supported (SCP-based SIM):
5
6 1-a-1 Include the TriggerAddressList parameter set to indicate active triggers for
7 the requesting MSC.
8
1-a-2 Include all pertinent parameters.
9
10 1-a-3 Send a RETURN RESULT to the requesting MSC.
11 1-a-4 Exit this task.
12
1-b ELSEIF the subscriber has WIN services controlled by the HLR at the
13
Mobile_Termination trigger (HLR-based SIM):
14
15 1-b-1 Execute “WIN Service Logic” task (see 6.Y).
16
1-b-2 Include parameters received from the service logic task.
17
18
1-b-3 IF a PointOfReturn shall be set:
19 1-b-3-1 Set the PointOfReturn.
20
1-b-4 ENDIF.
21
22 1-1 ELSE (Execute feature incoming call tasks to determine the feature processing
23 and PointOfReturn):
24
1-1 (Execute feature incoming call tasks to determine the feature processing and
25 PointOfReturn.)
26
27
a-1-1 IF WIN services are required1 :
28
a-1-1-1 Execute the “WIN Service Logic” task (see 6.Y.), as needed.
29
30 a-1-1-2 Include parameters received from the service logic task.
31
32
a-1-1-3 IF a PointOfReturn shall be set:
33 a-1-1-3-1 Set the PointOfReturn.
34
35 a-1-1-4 ENDIF.
36
a-1-2 ENDIF.
37
38 1-1-1 IF the CallingPartyNumberDigits1 parameter was received:
39
40
1-1-1-1 IF the received Digits (Dialed) equal the CallingPartyNumberDigits1
41
(an MS dialed its own directory number):
42 1-1-1-1-1 CASE revertive treatment OF:
43
1-1-1-1-2 VMR:
44
45 1-1-1-1-2-1 Execute “HLR VMR Revertive Call Invocation” task (see
46 5.23.3).
47
1-1-1-1-3 FA:
48
49 1-1-1-1-3-1 Execute “HLR FA Revertive Call Invocation” task (see
50 5.12.4).
51
1-1-1-1-4 MAH:
52
53 1-1-1-1-4-1 Execute “HLR MAH Revertive Call Invocation” task (see
54 5.14.5).
55
56
1 WIN services can be invoked at any point in HLR feature processing before the
57
58 Location Request RETURN RESULT is sent.
59
60

PN-4287
1
1-1-1-1-5 DEFAULT:
2
1-1-1-1-5-1 Include the AnnouncementCode parameter within the 3
AnnouncementList set to an accessed denied announcement. 4
5
1-1-1-1-5-2 Set the PointOfReturn to ToneTermination.
6
1-1-1-1-6 ENDCASE. 7
1-1-1-1-7 Send a RETURN RESULT to the requesting MSC. 8

9
1-1-1-1-8 Exit this task. 10
1-1-1-2 ENDIF. 11
12
1-1-2 ENDIF. 13
1-1-3 Set the called or dialed party equal to the received Digits (Dialed) parameter. 14
15
1-1-4 Execute the “HLR FA Incoming Call Invocation” task (see 5.12.3).
16
1-1-5 IF the PointOfReturn is indicated: 17
18
1-1-5-1 GOTO LocReqPointOfReturn.
19
1-1-6 ENDIF. 20
21
1-1-7 Execute the “HLR MAH Incoming Call Invocation” task (see 5.14.4).
22
1-1-8-1 GOTO LocReqPointOfReturn. 24

25
1-1-9 ENDIF. 26
(At this point it can be assumed that a mobile directory number was dialed.) 27
28
1-1-10 Execute the “HLR CFU Incoming Call Invocation” task (see 5.5.5).
29
31
1-1-11-1 GOTO LocReqPointOfReturn.
32
1-1-12 ENDIF. 33
34
1-1-13 Execute the “HLR SCA Incoming Call Invocation” task (see 5.19.7).
35
1-1-14-1 IF the PointOfReturn is Accepted: 37

38
1-1-14-1-1 GOTO Call Accepted. 39
1-1-14-2 ELSE: 40
41
1-1-14-2-1 GOTO LocReqPointOfReturn. 42
1-1-14-3 ENDIF. 43
44
1-1-15 ENDIF.
45
1-1-16 Execute the “HLR PCA Incoming Call Invocation” task (see 5.15.7). 46
47
1-1-17 IF the PointOfReturn is indicated:
48
1-1-17-1 IF the PointOfReturn is Accepted: 49
50
1-1-17-1-1 GOTO Call Accepted.
51
1-1-17-2 ELSE: 52
1-1-17-2-1 GOTO LocReqPointOfReturn. 53

54
1-1-17-3 ENDIF. 55
1-1-18 ENDIF. 56
57
1-c ENDIF. 58
Call Accepted: 59
60

PN-4287
1
1-20 Execute the “HLR CFNA Incoming Call Invocation” task (see 5.4.5).
2
3 1-21 IF the PointOfReturn is indicated:
4 1-21-1 GOTO LocReqPointOfReturn.
5
1-22 ENDIF.
6
7 1-23 Execute the “HLR CFD Incoming Call Invocation” task (see 5.3.5).
8 1-24 IF the PointOfReturn is indicated:
9
10
1-24-1 GOTO LocReqPointOfReturn.
11 1-25 ENDIF.
12
1-26 Execute the “HLR DND Incoming Call Invocation” task (see 5.11.3).
13
14
1-27 IF the PointOfReturn is indicated:
15 1-27-1 GOTO LocReqPointOfReturn.
16
1-28 ENDIF.
17
18 (HLR-based features are complete at this point.)
19 1-29 IF termination to the MS is authorized:
20
1-29-1 Execute the “HLR CD Incoming Call Invocation” task (see 5.1.3).
21
22 1-29-2 IF the PointOfReturn is not indicated:
23 1-29-2-1 (This is the default treatment for LocationRequests.)
24
25
1-29-2-2 Include the AnnouncementCode parameter within the
26
AnnouncementList parameter set to Reorder or other appropriate
27
announcement.
28 1-29-2-3 Set the PointOfReturn to ToneTermination (this is the default
29 treatment).
30
1-29-3 ENDIF.
31
32
1-30 ELSE (termination to the MS is not authorized:
33 1-30-1 Include the AnnouncementCode parameter in the AnnouncementList
34 parameter set to an appropriate announcement.
35
1-30-2 Set the PointOfReturn to ToneTermination.
36
37 1-31 ENDIF.
38 LocReqPointOfReturn (parameters may be included already and the PointOfReturn
39 should be selected by the feature processing tasks):
40
1-32 CASE PointOfReturn OF:
41
42 1-33 ToneTermination:
43 1-33-1 Include the AccessDeniedReason parameter set to the proper value (see the
44 following table).
45
46
1-33-2 Include the MSCID parameter set to the identity of the Originating MSC.
47 1-34 LocalTermination:
48
1-34-1 Include the MSCID parameter set to the identity of the Serving MSC.
49
50
1-34-2 Execute the “HLR CNIP Terminating Call Invocation” task (see 5.8.1).
51 1-34-3 IF the a preferred interexchange carrier is applicable:
52
1-34-3-1 Include the Digits (Carrier) parameter set to the MS’s preferred
53
interexchange carrier.
54
55 1-34-4 ENDIF.
56 1-35 IntersystemTermination:
57
1-35-1 Include the MSCID parameter set to the identity of the Serving MSC.
58
59 1-35-2 IF the PC_SSN of the Serving MSC is known:
60

PN-4287
1
1-35-2-1 Include the PC_SSN parameter as received.
2
1-35-3 ENDIF. 3
1-35-4 Execute the “HLR CNIP Redirecting Call Invocation” task (see 5.8.2). 4
5
1-35-5 IF the a preferred interexchange carrier is applicable:
6
1-35-5-1 Include the Digits (Carrier) parameter set to the MS’s preferred 7
interexchange carrier. 8
1-35-6 ENDIF. 9
10
1-36 PSTNTermination: 11
1-36-1 Include the MSCID parameter set to the identity of the Originating MSC. 12
13
1-36-2 IF selection of interexchange carrier is applicable:
14
1-36-3 ENDIF. 17
18
1-36-4 Execute the “HLR CNIP Redirecting Call Invocation” task (see 5.8.2).
19
1-36-5 IF the a preferred interexchange carrier is applicable: 20
23
1-36-6 ENDIF.
24
1-37 MultipleTermination: 25
1-37-1 IF at least one of the routes on the list is for a LocalTermination: 26

27
1-37-1-1 Execute the “HLR CNIP Terminating Call Invocation” task (see 5.8.1). 28
1-37-2 ENDIF. 29
30
1-37-3 IF at least one of the routes on the list is for a IntersystemTermination or a
31
PSTNTermination:
32
1-37-3-1 Execute the “HLR CNIP Redirecting Call Invocation” task (see 5.8.2). 33
1-37-4 ENDIF. 34
35
1-37-5 IF the a preferred interexchange carrier is applicable:
36
1-37-6 ENDIF. 39
40
1-38 DEFAULT:
41
1-38-1 Send a RETURN ERROR with Error Code SystemFailure. 42

44
1-39 ENDCASE. 45
1-40 Send a RETURN RESULT to the requesting MSC. 46
47
2 ELSE (the received message cannot be processed):
48
2-1 Send a RETURN ERROR with a proper Error Code value (see the following 49
table) to the requesting MSC. 50
3 ENDIF. 51
52
4 Exit this task.
53
54
55
56
57
58
59
60

PN-4287
1
2
3 4.31 ORIGINATION REQUEST
4
5
6
4.31.1 MSC Initiating an Origination Request
7
8
9
When the MSC determines that an active origination trigger has been encountered
10
requiring call processing to be suspended while the HLR or another network entity must
11
performs digit analysis (for other than a feature code) or otherwise executes service logic,
12
13
it shall perform the following:
14
1 Include the BillingID (Originating) parameter set to the billing identifier for the call
15
assigned by the current Originating MSC.
16
17
2 Include the Digits (Dialed) parameter set to the digits received from the MS.
18 3 Include the ElectronicSerialNumber parameter set to identify the originating MS.
19
4 Include the MobileIdentificationNumber parameter set to identify the originating MS.
20
21 5 Include the MSCID parameter set to the identity of the Originating MSC.
22 m IF a WIN Trigger was encountered:
23
24 m-1 Include the TriggerType parameter set to identify the trigger encountered.
25
n ENDIF.
26
27 6 Include the OriginationTriggers parameter set to identify the triggering event.
28
7 Include the TransactionCapability parameter set to identify the current capabilities.
29
30 a Include the WINCapability parameter set to identify the current TriggerCapability and
31 the current WINOperationsCapability.
32
b Include other applicable parameters.
33
34 b Include the TriggerType parameter set to identify the trigger that was encountered.
35
c IF the trigger that was encountered was armed by the TriggerAddressList parameter:
36
37 c-1 Send an OriginationRequest INVOKE to the service logic host address obtained
38 from the TriggerAddressList for the trigger that was encountered.
39
d ELSE:
40
41 d-1 Send an OriginationRequest INVOKE to the MS’s associated HLR.
42 e ENDIF.
43
8 Send a OriginationRequest INVOKE to the MS’s associated HLR.
44
45 9 Start the Origination Request Timer (ORT).
46
10 WAIT for Origination Request response:
47
48
49 Origination Request RETURN RESULT Treatment:
50
11-1 Stop timer (ORT), if it is running.
51
53
11-2-1 IF the incoming call is still connected:
54
55
11-2-1-1 IF the AnnouncementList parameter is received:
56 11-2-1-1-1 Execute the “Play All Announcements in the AnnouncementList”
57 task (see 3.2.5).
58
11-2-1-2 ENDIF.
59
60
TIA/EIA-41.6-D Modifications 6-47 4.31 Origination Request

PN-4287
1
2
11-2-1-a-1 If the call is being redirected: 3
4
7
11-2-1-a-2 ELSE: 8
10
11

13
14
11-2-1-a-3 ENDIF. 15
16
11-2-1-b ENDIF. 17
18
11-2-1-3 IF the AccessDeniedReason parameter is received AND IF it can be
19
acted upon:
20
11-2-1-3-1 IF AnnouncementList parameter is not received: 21
11-2-1-3-1-1 Apply the default treatment appropriate for the received 22

23
AccessDeniedReason value.
24
11-2-1-3-1-1 Apply the treatment appropriate to the returned 25
AccessDeniedReason value. 26

28
11-2-1-3-2 ENDIF. 29
11-2-1-4 ELSEIF the OriginationRequest INVOKE was sent after detecting a 30
non-WIN trigger: 31
32
11-2-1-4-1 IF neither the TerminationList parameter nor ActionCode 33
parameter nor Digits (Dialed) parameter is received (an error 34

35
condition?):
36
11-2-1-4-1-1 Execute the “Apply Access Denial Treatment” task (see 3.4.5). 37
38
40
11-2-1-4-2 ENDIF.
41
11-2-1-4 ELSEIF neither the no TerminationList parameter nor ActionCode parameter 42
nor Digits (Dialed) parameter nor ResumePIC parameter is received (an error 43
condition?): 44
11-2-1-4-1 Execute the “Apply Access Denial Treatment” task (see 3.4.5). 45
46
11-2-1-4-2 Return to the calling task.
47
11-2-1-5 ENDIF. 48
11-2-1-6 IF the TerminationList parameter is received: 49

50
51
Collected_Information or the Analyzed_Information DP: 52
53
54
11-2-1-6-b ENDIF. 55
56
11-2-1-6-1 Execute the “MSC Routing Points Of Return” task (see 3.2.6). 57
11-2-1-7 ENDIF. 58
59
60
4.31 Origination Request 6-48 TIA/EIA-41.6-D Modifications

PN-4287
1
11-2-1-8 IF the ActionCode parameter is received:
2
3 11-2-1-8-1 Execute the “MSC ActionCode Processing” task (see 3.2.9).
4 11-2-1-9 ENDIF.
5
11-2-1-10 IF the Digits (Dialed) parameter is received.
6
7 11-2-1-10-1 Set the MS dialed digits to the received Digits (Dialed) parameter
8 value.
9
11-2-1-10-2 IF the type of digits is unknown:
10
11 11-2-1-10-2-1 Process the dialed number locally to set the PointOfReturn
12 (this may include local feature code processing).
13
14
11-2-1-10-3 ENDIF:
15 11-2-1-10-a IF WIN triggers remain to be processed at the
16
Collected_Information or the Analyzed_Information DP:
17
18 11-2-1-10-a-1 Return to the calling task.
19
20
11-2-1-10-b ENDIF.
21
11-2-1-11 ELSE:
22
23 11-2-1-11-1 Use the Digits (Dialed) parameter included in the
24 OriginationRequest INVOKE as MS dialed digits.
25
11-2-1-12 ENDIF.
26
27 11-2-1-13 IF the ResumePIC parameter is received:
28 11-2-1-13-1 IF the value of the ResumePIC parameter is Continue Call
29
Processing:
30
32 11-2-1-13-2 ELSEIF the value of the ResumePIC parameter is a valid
33
transition:
34
35 11-2-1-13-2-1 GOTO the entry point indicated by the ResumePIC parameter.
36 11-2-1-13-3 ELSE:
37
38
11-2-1-13-3-1 Execute the “Local Recovery Procedures” task (see 3.5.1).
39 11-2-1-13-3-2 Exit this task.
40
41
11-2-1-13-4 ENDIF.
42 11-2-1-14 ELSE:
43
11-2-1-14-1 GOTO AuthorizedSubscriberOrigination (see 3.2.3).
44
45 11-2-1-15 ENDIF.
46
11-2-2 ELSE (call abandoned):
47
48 11-2-2-1 Execute the “Local Recovery Procedures” task (see 3.5.1).
49
11-2-2-2 Exit this task.
50
51 11-2-3 ENDIF.
52 11-3 ELSE (the message cannot be processed):
53
54
11-3-1 Execute “Local Recovery Procedures” task (see 3.5.1).
56
11-4 ENDIF.
57
59 12-1 Stop timer (ORT).
60
TIA/EIA-41.6-D Modifications 6-49 4.31 Origination Request

PN-4287
1
2
12-3 Start the Origination Request Timer (ORT). 3
12-4 Remain in this state. 4

5
a WHEN a ConnectResource INVOKE is received:
6
a-1 Stop the timer (ORT). 7
8
a-2 Execute the “MSC Receiving ConnectResource INVOKE” task (see 4.B.3).
9
a-3 CASE MSC Connect Resource result OF: 10
11
a-4 Disconnect Resource received:
12
a-4-1 Start the timer (ORT). 13

15
a-5 OriginationRequest RETURN RESULT received: 16
a-5-1 GOTO OriginationRequest RETURN RESULT Treatment. 17

18
a-6 SSFT expiration: 19
21
a-6-2 Remain in this state.
22
a-7 call abandoned: 23
24
a-7-1 Execute the “Local Recovery Procedures” task (see 3.5.1).
25
a-7-2 Exit this task. 26
27
a-8 resource disconnect:
28

31
a-9 failure at MSC: 32

34
a-10 message error: 36
37
a-10-1 Start the timer (ORT).
38
40
a-11 ENDCASE.
41
13 WHEN the MS disconnects: 42

44
14-1 Stop timer (ORT). 46
47
48
14-3 Provide an unsuccessful indication to the MS. 49
14-4 Exit this task. 50
51
15 WHEN timer (ORT) expires:
52
15-2 Provide an unsuccessful indication to the MS. 54

55
16 ENDWAIT. 57
58
59
60
4.31 Origination Request 6-50 TIA/EIA-41.6-D Modifications

PN-4287
1
2
3 4.49 TRANSFER-TO-NUMBER REQUEST
4
5
6
4.49.1 MSC Initiating a Transfer-To-Number Request
7
(TIA/EIA-41.6-D, page 6-296)
8
9
10
When an MSC detects that it needs to request the transfer-to-number associated with an
11
MS, it shall perform the following:
12
1 Relay the RedirectionReason parameter set by the calling task.
13
14 2 Include the CallingPartyNumberDigits1 parameter.
15 3 Include the CallingPartySubaddress parameter.
16
4 Include the MS’s ElectronicSerialNumber parameter.
17
18 5 Include the MS’s MobileIdentificationNumber parameter.
19 6 Include the MSC’s MSCIdentificationNumber.
20
21
7 Include the MSC’s SystemMyTypeCode parameter.
22 8 Include the TransactionCapability parameter set according to the capabilities of the
23 system and the current call state.
24
9 IF the MSC is the Originating MSC:
25
26
9-1 Include the Originating MSC’s call’s BillingID parameter to identify the call for
27
subsequent call redirection.
28 10 ELSEIF the MSC is the Serving MSC:
29
10-1 Include the Serving MSC’s BillingID parameter to identify the call for
30
subsequent call redirection.
31
32 11 ENDIF.
33 12 IF the leg was established with a PilotBillingID parameter:
34
12-1 Include the PilotBillingID parameter set to the same value as received.
35
36 13 ENDIF.
37 14 Send a TransferToNumberRequest INVOKE to the MS’s HLR.
38
39
15 Start the Transfer-To-Number Request Timer (TTNRT).
40 16 WAIT for a Transfer to Number Request response:
41
42
43
17-1 Stop timer (TTNRT).
45
17-2-1 IF the AnnouncementList parameter is received:
46
47 17-2-1-1 Execute the “Play All Announcements in the AnnouncementList” task
48 (see 3.2.5).
49 17-2-2 ENDIF.
50
17-2-a IF the TriggerAddressList parameter is received:
51
52 17-2-a-1 Arm the triggers indicated by the received TriggerAddressList parameter
53
for the redirected call.
54
55 17-2-b ENDIF.
56
57
17-2-3 IF an ActionCode parameter is received:
58 17-2-3-1 Execute the “MSC ActionCode Processing” task (see 3.2.9).
59
60
TIA/EIA-41.6-D Modifications 6-51 4.49 Transfer-To-Number Request

PN-4287
1
17-2-4 ENDIF.
2
17-2-5 IF the AccessDeniedReason parameter is received: 3
17-2-5-1 IF AnnouncementList parameter was not received: 4

5
17-2-5-1-1 Apply the treatment appropriate to the returned
6
AccessDeniedReason value.
7
17-2-5-2 ENDIF. 8
17-2-5-3 Return to the calling task with a successful indication. 9

10
17-2-6 ENDIF. 11
17-2-7 IF the TerminationList parameter is received: 12
13
17-2-7-1 Execute the “MSC Routing Points Of Return” task (see 3.2.6).
14
17-2-8 ELSEIF the Digits (Destination) parameter is received: 16
17
17-2-8-1 Release all extended facilities associated with the indicated call.
18
20
17-2-8-a-1 Execute the “MSC Analyze MS Dialed Number” task (see 3.2.3).
21
17-2-8-b ELSE: 22
23
17-2-8-b-1 Execute the “MSC Route the Call Leg Externally” task (see 3.3.8). 24
25
17-2-8-b-2 Return to the calling task with a successful indication.
26
17-2-8-c ENDIF. 27
28
17-2-8-2 Execute the “MSC Route the Call Leg Externally” task (see 3.3.8).
29
17-2-9 ELSE: 31
32
33
17-2-9-2 Return to the calling task with an unsuccessful indication. 34
17-2-10 ENDIF. 35
36
39
17-3-2 Return to the calling task with an unsuccessful indication.
40
17-4 ENDIF. 41
43
18-1 Stop timer (TTNRT).
44
18-2 Execute the “MSC Remote User Interaction” task (see 4.39.2). 45
18-3 Start the Transfer-To-Number Timer (TTNRT). 46

47
48
19 WHEN the incoming call disconnects: 49

51
20-1 Stop timer (TTNRT). 53
54
55
20-3 Return to the calling task with an unsuccessful indication. 56
21 WHEN timer (RDRT) expires: 57
58
59
60
4.49 Transfer-To-Number Request 6-52 TIA/EIA-41.6-D Modifications

PN-4287
1
21-2 Return to the calling task with an unsuccessful indication.
2
3 22 ENDWAIT.
4
5
6
4.A ANALYZED INFORMATION
7
8
9 4.A.1 MSC Initiating an Analyzed Information
10
11
12
When the MSC determines that an active A d v a n c e d _ T e r m i n a t i o n trigger or
13
Specific_Called_Party_Digit_String trigger at the Analyzed_Information DP has been
14
15
encountered requiring call processing to be suspended while an SCF network entity
16
executes service logic, the MSC shall perform the following:
17
1 Include the BillingID parameter set to the billing identifier for the call assigned by
18
the current Originating MSC.
19
20 2 Include the Digits (Dialed) parameter set to the digits received from the MS.
21 3 Include the MSCID parameter set to the identity of the Originating MSC.
22
4 Include the TransactionCapability parameter set to identify the current capabilities.
23
24 5 Include the TriggerType parameter set to identify the trigger that was encountered.
25 a Include other applicable parameters.
26
27 6 Include the WINCapability parameter set to identify the current TriggerCapability and
28 the current WINOperationsCapability.
29 7 Send an AnalyzedInformation INVOKE to the SCF network entity address obtained
30 from the TriggerAddressList parameter for the trigger that was encountered.
31
32
8 Start the Analyzed Information Timer (ANZT).
33 9 WAIT for Analyzed Information response:
34
35
36
AnalyzedInformation RETURN RESULT Treatment:
37
10-1 Stop timer (ANZT) if it is running.
38
39 AnalyzedInformation RETURN RESULT Treatment:
41
42
43 10-2-1-1 IF the AnnouncementList parameter is received:
44
10-2-1-1-1 Execute “Play All Announcements in the AnnouncementList” task
45
(see 3.2.5).
46
47
10-2-1-2 ENDIF.
48 10-2-1-3 IF the AccessDeniedReason parameter is received AND IF it can be
49 acted upon:
50
10-2-1-3-1 Execute the “Apply Access Denial Treatment” task (see 3.4.5).
51
52 10-2-1-3-2 Exit this task.
53 10-2-1-4 ENDIF
54
55
56 10-2-1-a-1 If the call is being redirected:
57
58 10-2-1-a-1-1 Arm the triggers indicated by the received TriggerAddressList
59 parameter for the redirected call.
60
TIA/EIA-41.6-D Modifications 6-53 4.49 Transfer-To-Number Request

PN-4287
1
10-2-1-a-2 ELSE:
2
4
5
parameter for the remainder of the call in progress. 7

8
10-2-1-a-3 ENDIF. 9
10
10-2-1-b ENDIF.
11
10-2-1-5 IF the ActionCode parameter is received: 12

13
10-2-1-5-1 Execute the “MSC ActionCode Processing” task (see 3.2.9).
14
10-2-1-6 ENDIF. 15
10-2-1-7 IF the TerminationList parameter is received: 16

17
10-2-1-7-a IF WIN triggers remain to be processed at the 18
20
21
10-2-1-7-b ENDIF. 22
23
10-2-1-7-1 Execute the “MSC Routing Point Of Return” task (see 3.2.6). 24
10-2-1-8 ENDIF. 25
26
10-2-1-9 IF the Digits (Dialed) parameter is received:
27
10-2-1-9-1 Set the MS dialed digits to the received Digits (Dialed) parameter 28
value. 29
10-2-1-9-2 IF the type of digits is unknown: 30

31
10-2-1-9-2-1 Process the dialed number locally to set the PointOfReturn. 32
10-2-1-9-3 ENDIF. 33
34
35
10-2-1-9-a-1 Return to the calling task. 37

38
10-2-1-9-b ENDIF. 39
40
10-2-1-10 ELSE:
41
10-2-1-10-1 Use the Digits (Dialed) parameter included in the 42
AnalyzedInformation INVOKE as MS dialed digits. 43
10-2-1-11 ENDIF. 44
45
10-2-1-12 IF the ResumePIC parameter is received: 46
10-2-1-12-1 IF the value of the ResumePIC parameter is Continue Call 47
Processing: 48
49
50
10-2-1-12-2 ELSEIF the value of the ResumePIC parameter is a valid 51
transition: 52
10-2-1-12-2-1 GOTO the entry point indicated by the ResumePIC parameter. 53
54
10-2-1-12-3 ELSE:
55
10-2-1-12-3-1 Execute “Local Recovery Procedures” task (see 3.5.1). 56
10-2-1-12-3-2 Exit this task. 57

58
10-2-1-12-4 ENDIF.
59
60
4.A Analyzed Information 6-54 TIA/EIA-41.6-D Modifications

PN-4287
1
10-2-1-13 ENDIF.
2
3 10-2-2 ELSE (call abandoned):
5
6
7 10-2-3 ENDIF.
8 10-3 ELSE (the message cannot be processed):
9
10
12
10-4 ENDIF.
13
14
11 WHEN a RemoteUserInteractionDirective INVOKE is received:
15 11-1 IF the call is still connected
16
11-1-1 Stop timer (ANZT).
17
18 11-1-2 Execute the “MSC Remote User Interaction” task (see 4.39.2).
19 11-1-3 Start the AnalyzedInformation Timer (ANZT).
20
11-2 ENDIF
21
22 11-3 Remain in this state.
23 12 WHEN a ConnectResource INVOKE is received:
24
25
12-1 Stop the timer (ANZT).
26 12-2 Execute the “MSC Receiving ConnectResource INVOKE” task (see 4.B.3).
27
12-3 CASE MSC Connect Resource result OF:
28
29
12-4 Disconnect Resource received:
30 12-4-1 Start the timer (ANZT).
31
12-4-2 Remain in this state.
32
33 12-5 AnalyzedInformation RETURN RESULT received:
34 12-5-1 GOTO AnalyzedInformation RETURN RESULT Treatment.
35
12-6 SSFT expiration:
36
38 12-6-2 Remain in this state.
39
40
12-7 call abandoned:
41 12-7-1 Execute the “Local Recovery Procedures” task (see 3.5.1).
42
12-7-2 Exit this task.
43
44
12-8 resource disconnect:
46
47
48 12-9 failure at MSC:
50
51
52 12-10 message error:
54
55
56 12-11 ENDCASE.
57
13 WHEN the incoming call disconnects:
58
59
13-1 Stop the timer (ANZT).
60
TIA/EIA-41.6-D Modifications 6-55 4.A Analyzed Information

PN-4287
1
13-2 Execute the “Local Recovery Procedures” task (see 3.5.1).
2

5
14-1 Stop timer (ANZT).
6

9
15 WHEN timer (ANZT) expires: 10
12
13
16 ENDWAIT. 14
16
17
4.E FACILITY SELECTED AND AVAILABLE 18
19
20
4 . E . 1 MSC Initiating a Facility Selected And Available 21

22
23
24
When the MSC determines that an active Terminating_Resource_Available trigger has 25
been encountered requiring call processing to be suspended while an SCF network entity 26
executes service logic, it shall perform the following: 27
28
1 Include the BillingID parameter set to the billing identifier for the call assigned by
29
the current Serving MSC.
30
2 Include the MSCID parameter set to the identity of the Serving MSC. 31
3 Include the TransactionCapability parameter set to identify the current capabilities. 32

33
4 Include the TriggerType parameter set to identify the trigger that was encountered.
34
5 Include the WINCapability parameter set to identify the current TriggerCapability and 35
the current WINOperationsCapability of the MSC. 36
6 IF the call leg was established with a PilotBillingID parameter: 37

38
6-1 Include the PilotBillingID parameter set to the same value as received. 39
7 ENDIF. 40
41
8 Send a FacilitySelectedAndAvailable INVOKE to the SCF network entity indicated
42
by the TriggerAddressList parameter for the trigger that was encountered.
43
9 Start the Facility Selected And Available Timer (FAVT). 44
10 WAIT for Facility Selected And Available response: 45
46
47
FacilitySelectedAndAvailable RETURN RESULT Treatment: 48
11-1 Stop the timer (FAVT), if the timer is still running. 49

50
51
11-2-1 IF the incoming call is still connected: 52
11-2-1-2 IF the AccessDeniedReason parameter is received AND IF it can be 53
acted upon: 54
55
11-2-1-2-2 Return to the calling task. 57
58
11-2-1-3 ENDIF
59
60
4.A Analyzed Information 6-56 TIA/EIA-41.6-D Modifications

PN-4287
1
2
3 11-2-1-a-1 Disarm any previously armed subscribed WIN triggers for the
4
5
6 11-2-1-a-2 Arm the triggers indicated by the received TriggerAddressList
7 parameter for the remainder of the call in progress.
8
9 11-2-1-b ENDIF.
10
11
13 11-2-1-5 ENDIF.
14
15
11-2-1-6 IF the ResumePIC parameter is received:
16 11-2-1-6-1 IF the value of the ResumePIC parameter is Continue:
17
18
19
11-2-1-6-2 ELSEIF the value of the ResumePIC parameter is a valid
20
transition:
22
11-2-1-6-3 ELSE:
23
24 11-2-1-6-3-1 Execute “Local Recovery Procedures” task (see 3.5.1).
25 11-2-1-6-3-2 Exit this task.
26
11-2-1-6-4 ENDIF.
27
28 11-2-1-7 ENDIF.
30
31
11-2-2-1 Execute the “Local Recovery Procedures” task (see 3.5.1).
33
11-2-3 ENDIF.
34
35
37
38
39 11-4 ENDIF.
40 12 WHEN the incoming call disconnects:
41
42
43 12-2 Exit this task.
44 13 WHEN a RETURN ERROR or REJECT is received:
45
46
13-1 Stop timer (FAVT).
48
49
50
14 WHEN timer (FAVT) expires:
52
53
54 15 ENDWAIT
55 16 Return to the calling task.
56
57
58
59
60
TIA/EIA-41.6-D Modifications 6-57 4.E Facility Selected And Available

PN-4287
1
2
4.M TBUSY 3
4
5
4 . M . 1 MSC Initiating a TBusy 6

7
8
9
When the MSC determines that an active T_Busy trigger armed by a TriggerAddressList 10
parameter has been encountered requiring call processing to be suspended while an SCF 11
network entity executes service logic, the MSC shall perform the following: 12
13
14
2 IF the MSC is the Originating MSC: 15
2-1 Include the Originating MSC’s call’s BillingID parameter to identify the call for 16
subsequent call redirection. 17

18
3 ELSEIF the MSC is the Serving MSC:
19
3-1 Include the Serving MSC’s BillingID parameter to identify the call for 20
4 ENDIF. 22
23
5 Include the TransactionCapability parameter set to identify the current capabilities. 24
6 Include the TriggerType parameter set to identify the trigger that was encountered. 25
26
7 Include the WINCapability parameter set to identify the current TriggerCapability and
27
the current WIN Operations Capability.
28
8 IF the call leg was established with a PilotBillingID parameter: 29
8-1 Include the PilotBillingID parameter set to the same value as received. 30
31
9 ENDIF.
32
10 Send a TBusy INVOKE to the SCF network entity indicated by the 33
11 Start the TBusy Timer (TBT). 35

36
12 WAIT for a TBusy response:
37
TBusy RETURN RESULT Treatment: 39

40
13-1 Stop the timer (TBT), if it is running. 41
13-2 IF the message can be processed: 42
43
44
13-2-1-1 IF the AnnouncementList parameter is received: 45
13-2-1-1-1 Execute the “Play All Announcements in the AnnouncementList” 46
task (see 3.2.5). 47
48
13-2-1-2 ENDIF.
49
13-2-1-3 IF AccessDeniedReason parameter is received: 50
52
53
13-2-1-4 ENDIF. 54

56
13-2-1-a-1 Arm the triggers indicated by the received TriggerAddressList 57

59
60
4.N TNoAnswer 6-58 TIA/EIA-41.6-D Modifications

PN-4287
1
13-2-1-b ENDIF.
2
3 13-2-1-5 IF the ActionCode parameter is received:
4
13-2-1-5-1 Execute the “MSC ActionCode Processing” task (see 3.2.9).
5
6 13-2-1-6 ENDIF.
7 13-2-1-7 IF the TerminationList parameter is received:
8
13-2-1-7-1 Execute the “MSC Routing Points of Return” task (see 3.2.6).
9
10 13-2-1-8 ENDIF.
12
13
13-2-1-9-1 IF the value of ResumePIC parameter is Continue:
15
13-2-1-9-2 ELSEIF the transition indicated by the ResumePIC parameter is
16
valid:
17
18
13-2-1-9-2-1 GOTO the entry point indicated by the ResumePIC parameter.
19 13-2-1-9-3 ELSE:
20
13-2-1-9-3-1 Execute the “Local Recovery Procedures” task (see 3.5.1).
21
22 13-2-1-9-3-2 Exit this task.
23 13-2-1-9-4 ENDIF.
24
13-2-1-10 ENDIF.
25
28
29
30 13-2-3 ENDIF.
31
32
33
35
13-4 ENDIF.
36
38 14-1 IF the call is still connected:
39
14-1-1 Stop the timer (TBT).
40
41 14-1-2 Execute the “MSC Remote User Interaction” task (see 4.39.2).
42 14-1-3 Start the TBusy Timer (TBT).
43
44
14-2 ENDIF
46
15 WHEN a ConnectResource INVOKE is received:
47
48
15-1 Stop the timer (TBT).
49 15-2 Execute the “MSC Receiving ConnectResource INVOKE” task (see 4.B.3).
50
15-3 CASE MSC Connect Resource result OF:
51
52 15-4 Disconnect Resource received:
53 15-4-1 Start the timer (TBT).
54
55
56 15-5 TBusy RETURN RESULT received:
57 15-5-1 GOTO TBusy RETURN RESULT Treatment.
58
59
15-6 SSFT expiration:
60
TIA/EIA-41.6-D Modifications 6-59 4.N TNoAnswer

PN-4287
1
15-6-1 Start the timer (TBT).
2
15-6-2 Remain in this state. 3
15-7 call abandoned: 4

5
15-7-1 Execute the “Local Recovery Procedures” task (see 3.5.1).
6
15-8 resource disconnect: 8

9
15-8-1 Start the timer (TBT). 10
12
15-9 failure at MSC:
13
16
15-10 message error:
17

20
15-11 ENDCASE.
21
16-1 Execute the “Local Recovery Procedures” task (see 3.5.1). 23

24
27
17-1 Stop the timer (TBT).
28
31
18 WHEN the timer (TBT) expires:
32

35
19 ENDWAIT.
36
38
39
4.N TNOANSWER 40
41
42
4 . N . 1 MSC Initiating a TNoAnswer 43

44
45
46
When the MSC determines that an active T _ N o _ A n s w e r trigger armed by a
47
TriggerAddressList parameter has been encountered requiring call processing to be
48
suspended while an SCF network entity executes service logic, the MSC shall perform
49
the following:
50
1 Include the MSCID parameter set to the identity of the MSC. 51

52
2 IF the MSC is the Originating MSC: 53
2-1 Include the Originating MSC’s call’s BillingID parameter to identify the call for 54
56
3 ELSEIF the MSC is the Serving MSC:
57
3-1 Include the Serving MSC’s BillingID parameter to identify the call for 58
60
4.N TNoAnswer 6-60 TIA/EIA-41.6-D Modifications

PN-4287
1
4 ENDIF.
2
3 5 Include the TransactionCapability parameter set to identify the current capabilities.
4 6 Include the TriggerType parameter set to identify the trigger that was encountered.
5
7 Include the WINCapability parameter set to identify the current TriggerCapability and
6
the current WINOperationsCapability.
7
8 8 IF the call leg was established with a PilotBillingID parameter:
9 8-1 Include the PilotBillingID parameter set to the same value as received.
10
11
9 ENDIF.
12 10 Send a TNoAnswer INVOKE to the SCF network entity indicated by the
14
11 Start the TNoAnswer Timer (TNAT).
15
16
12 WAIT for a TNoAnswer response:
17 13 WHEN a RETURN RESULT is received:
18
TNoAnswer RETURN RESULT Treatment:
19
20 13-1 Stop the timer (TNAT), if it is running.
22
23
24 13-2-1-1 IF the AnnouncementList parameter is received:
25 13-2-1-1-1 Execute “Play All Announcements in the AnnoucementList” task
26 (See 3.2.5).
27
28
13-2-1-2 ENDIF
29 13-2-1-3 IF the AccessDeniedReason parameter is received:
30
13-2-1-3-1 Execute the “Apply Access Denial Treatment” task (see 3.4.5).
31
32
33 13-2-1-4 ENDIF.
34
35
36 13-2-1-a-1 Arm the triggers indicated by the received TriggerAddressList
37
parameter for the redirected call.
38
39 13-2-1-b ENDIF.
40
41
43
13-2-1-6 ENDIF.
44
45
13-2-1-7 IF the TerminationList parameter is received:
46 13-2-1-7-1 Execute the “MSC Routing Points of Return” task (see 3.2.6).
47
13-2-1-8 ENDIF.
48
50 13-2-1-9-1 IF the value of ResumePIC parameter is Continue:
51
52
53 13-2-1-9-2 ELSEIF the transition indicated by the ResumePIC parameter is
54 valid:
56
57
13-2-1-9-3 ELSE:
58 13-2-1-9-3-1 Execute the “Local Recovery Procedures” task (see 3.5.1).
59
60
TIA/EIA-41.6-D Modifications 6-61 4.M TBusy

PN-4287
1
13-2-1-9-4 ENDIF.
2
13-2-1-10 ENDIF. 3
13-2-2 ELSE (call abandoned): 4

5
13-2-2-1 Execute the “Local Recovery Procedures” task (see 3.5.1).
6
13-2-2-2 Exit this task. 7
13-2-3 ENDIF. 8
9
13-3-1 Execute the “Local Recovery Procedures” task (see 3.5.1). 11
12
13
13-4 ENDIF. 14
16
14-1 IF the call is still connected
17
14-1-1 Stop the timer (TNAT). 18
14-1-2 Execute the “MSC Remote User Interaction” task (see 4.39.2). 19
20
14-1-3 Start the TNoAnswer Timer (TNAT).
21
14-2 ENDIF 22

24
15 WHEN a ConnectResource INVOKE is received: 25
15-1 Stop the timer (TNAT). 26
27
15-2 Execute the “MSC Receiving Connect Resource INVOKE” task (see 4.B.3).
28
15-3 CASE MSC Connect Resource result OF: 29
15-4 Disconnect Resource received: 30
31
15-4-1 Start the timer (TNAT).
32
15-5 TNoAnswer RETURN RESULT received: 34

35
15-5-1 GOTO TNoAnswer RETURN RESULT Treatment.
36
15-6 SSFT expiration: 37
15-6-1 Start the timer (TNAT). 38

39
42
15-7-1 Execute the “Local Recovery Procedures” task (see 3.5.1).
43
46
47
15-9 failure at MSC: 49

50
51
15-10 message error: 53

54
15-10-1 Start the timer (TNAT). 55
57
15-11 ENDCASE.
58
60
4.M TBusy 6-62 TIA/EIA-41.6-D Modifications

PN-4287
1
2
4 17 WHEN a RETURN ERROR or REJECT is received:
5
17-1 Stop the timer (TNAT).
6
7 17-2 Execute the “Local Recovery Procedures” task (see 3.5.1).
9
10
18 WHEN the timer (TNAT) expires:
12
13
14
19 ENDWAIT.
16
17
18 4.S BULK DISCONNECTION
19 (New for TIA/EIA-41.6-D Section 4)
20
21
22
23
4 . S . 1 MSC Initiating a Bulk Disconnection
24
25
When an MSC has recovered from a failure where all calls served by that MSC have been
26
released, the MSC shall perform the following:
27
1 FOR each SCF network entity that is associated with armed T_Disconnect or
28
O_Disconnect triggers:
29
30 1-1 Include the MSCID parameter set to the identity of the MSC.
31 1-2 Include the TimeOfDay parameter set to local time (UTC) when the MSC failure
32 occurred.
33
1-3 Include the TimeDateOffset parameter set to the offset for local time.
34
35 1-4 Include other applicable parameters.
36 1-5 Send a BulkDisconnection INVOKE to the SCF network entity.
37
38
1-6 Start the Bulk Disconnection Timer (BDISCT).
39 1-7 WAIT for a Bulk Disconnection response:
40
1-8 WHEN a RETURN RESULT is received:
41
42
1-8-1 Stop timer (BDISCT).
43 1-8-2 IF the message cannot be processed:
44
45
47 1-8-3 ENDIF.
48
1-9 WHEN a RETURN ERROR or REJECT is received:
49
50 1-9-1 Stop timer (BDISCT).
52
53
54 1-10 WHEN timer (BDISCT) expires:
55
56
57
58 1-11 ENDWAIT.
59
60
TIA/EIA-41.6-D Modifications 6-63 4.M TBusy

PN-4287
1
2 ENDFOR.
2
3 Exit this task. 3
4
5
4 . S . 2 SCF Receiving BulkDisconnection INVOKE 6
7
When an SCF network entity receives a BulkDisconnection INVOKE, it shall perform 8
the following: 9
10
1 IF the received message can be processed:
11
1-2 IF service information for subscribers that were being served by the MSC that 13
experienced the failure has not been updated: 14
15
1-2-1 Update service information for subscribers that were being served by the
16
MSC that experienced the failure.
17
1-3 ENDIF. 18
1-4 Execute Service Interactions Manager service logic, if required. 19

20
1-5 FOR each remote SCF network entity requiring notification of the MSC failure
21
recovery:
22
1-5-1 Relay all received parameters. 23
1-5-2 Include the SenderIdentificationNumber parameter set to the identification 24
number of this SCF network entity. 25

26
1-5-3 Send a BulkDisconnection INVOKE to the service logic network entity. 27
1-5-4 Start the Bulk Disconnection Timer (BDISCT). 28
29
1-5-5 WAIT for a Bulk Disconnection response:
30
1-5-6 WHEN a RETURN RESULT is received: 31
1-5-6-1 Stop timer (BDISCT). 32
33
1-5-6-2 IF the message cannot be processed:
34
1-5-6-2-1 Execute “Local Recovery Procedures” task (see 3.5.1). 35
1-5-6-3 ENDIF. 36
37
1-5-7 WHEN a RETURN ERROR or REJECT is received:
38
1-5-7-1 Stop timer (BDISCT). 39
1-5-7-2 Execute “Local Recovery Procedures” task (see 3.5.1). 40

41
1-5-8 WHEN the timer (BDISCT) expires: 42
1-5-8-1 Execute “Local Recovery Procedures” task (see 3.5.1). 43
44
1-5-9 ENDWAIT.
45
1-6 ENDFOR. 46
2 ELSE (the received message cannot be processed): 47
48
2-1 Send a RETURN ERROR with a proper Error Code value (see the following
49
table) to the requesting MSC.
50
3 ENDIF. 51

53
54
55
56
57
58
59
60
4.S BulkDisconnect 6-64 TIA/EIA-41.6-D Modifications

PN-4287
1
T a b l e 4 . S . 2 SCF BulkDisconnection Response
2
3 Problem Detection and Recommended Response from
4 SCF
5
PROBLEM DEFINITION 1 2 3 4 5 Notes
6
7 RETURN ERROR
8 Error Code
9 UnrecognizedIMSI a
10 UnrecognizedMIN a
11 UnrecognizedESN a
12 MSID/HLRMismatch a
13 OperationSequenceProblem a
14 ResourceShortage X
15 OperationNotSupported X b
16 TrunkUnavailable a
17 ParameterError X c
18 SystemFailure X
19 UnrecognizedParameterValue X c
20 FeatureInactive a
21 MissingParameter c
22
23 Problem Detections:
24
1. The requested MAP operation is recognized, but not supported by the receiving SCF network
25
entity, or the requesting network entity is not authorized.
26
27
2. A required SCF resource is temporarily not available (e.g., congestion).
28 3. A required resource (e.g., data base access, functional entity) is not presently accessible due to a
29 failure. Human intervention may be required for resolution.
30 4. A supplied parameter value is unrecognized or has non-standard values.
31 5. A supplied parameter value has an encoding problem.
32
33 Notes:
34 a. This Error Code is not an appropriate SCF response to an BulkDisconnection transaction.
35
b. It is recommended that an SCF network entity support BulkDisconnection transactions.
36
37
c. Include the Parameter Identifier in question as the FaultyParameter parameter.
38
39
4.T CALL CONTROL DIRECTIVE
40
(New for TIA/EIA-41.6-D Section 4)
41
42
43
44 4.T.1 SCF Initiating a Call Control Directive
45
46 When the SCF network entity determines that call processing actions are required for a
47 call being processed by an MSC, it shall perform the following:
48
49 1 Include the BillingID parameter set to identify the call.
50 2 Include the MSCID parameter set to the identity of the SCF network entity.
51
52
3 Include the MSID parameter set to identify the subscriber.
53 4 Include the ElectronicSerialNumber parameter.
54
5 IF a tone or announcement is to be played to the MS or to the party associated with
55
the MS (e.g., the called party when the call is forwarded on behalf of the subscriber):
56
57
5-1 Include the AnnouncementList parameter set to indicate the tone or
58
announcement.
59 6 ENDIF.
60
TIA/EIA-41.6-D Modifications 6-65 4.S BulkDisconnect

PN-4287
1
7 IF specific MSC call processing action is required:
2
7-1 Include the ActionCode parameter set appropriately. 3
8 ENDIF. 4
5
9 IF the MS call shall be redirected:
6
9-1 Include the TerminationList parameter set appropriately. 7
10 ENDIF. 8
9
11 Include other applicable parameters. 10
12 Send a CallControlDirective to the MSC associated with this call. 11
12
13 Start the Call Control Directive Timer (CCDT).
13
14 WAIT for a Call Control Directive response. 14
16
15-1 Stop the timer (CCDT).
17
15-2-1 IF the requested actions were completed: 19

20
15-2-1-1 Return to the calling task with a successful indication.
21
15-2-2 ELSE: 22
15-2-2-1 Return to the calling task with an unsuccessful indication and the 23
received parameters. 24
25
15-2-3 ENDIF. 26
15-3 ELSE: 27
28
29
15-3-2 Return to the calling task with an unsuccessful indication. 30
15-4 ENDIF. 31
32
16 WHEN a RETURN ERROR is received:
33
16-1 Stop the timer (CCDT). 34

36
16-3 Return to the calling task with an unsuccessful indication.
37
17 WHEN a REJECT is received: 38
17-1 Stop the timer (CCDT). 39

40
43
18 WHEN the timer (CCDT) expires:
44
47
19 ENDWAIT.
48
49
4.T.2 MSC Receiving a CallControlDirective INVOKE 50

51
Upon receipt of a CallControlDirective INVOKE, the MSC shall perform the following: 52
53
55
1-1 IF call setup is in progress for the call associated with the received BillingID
56
parameter value:
57
1-1-1 Include the CallStatus parameter set to indicate Call Setup in Progress. 58
1-1-2 Send a RETURN RESULT. 59
60
4.T CallControlDirective 6-66 TIA/EIA-41.6-D Modifications

PN-4287
1
2
3 1-2 ENDIF.
4 1-3 IF the subscriber indicated by the received MSID parameter is engaged in a
5 locally allowed call:
6
1-3-1 Include the CallStatus parameter set to indicate Locally Allowed Call – No
7
Action.
8
9 1-3-2 Send a RETURN RESULT.
11
12
1-4 ENDIF.
13 1-5 IF the AnnouncementList parameter is received:
14
1-5-1 Execute the “Play All Announcements in the AnnouncementList” task (see
15
3.2.5).
16
17
1-6 ENDIF.
18 1-7 Send an empty RETURN RESULT.
19
1-8 IF the ActionCode parameter is received:
20
21 1-8-1 Execute the “MSC ActionCode Processing” task (see 3.2.9).
22 1-8-2 IF the received ActionCode parameter value indicates Release leg and redirect
23 subscriber:
24
1-8-2-1 IF the TerminationList parameter is received:
25
26 1-8-2-1-1 Execute the “MSC Route the Call Leg Externally” task (see
27 3.3.8)1.
28
1-8-2-2 ELSE:
29
30
1-8-2-2-1 Execute “Local Recovery Procedures” task (see 3.5.1).
31 1-8-2-2-2 Exit this task.
32
1-8-2-3 ENDIF.
33
34 1-9 ENDIF.
35 2 ELSE (the received message cannot be processed).
36
37
38 2-2 Send a RETURN ERROR with the proper Error Code value (see the following
39 table).
40 3 ENDIF.
41
42
4 Exit this task.
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57 1 The processing of WIN triggers for the call leg identified by the received BillingID
58 parameter is for further study.
59
60
TIA/EIA-41.6-D Modifications 6-67 4.T CallControlDirective

PN-4287
1
T a b l e 4 . T . 2 MSC CallControlDirective Response
2
Problem Detection and Recommended Response from MSC 3
4
PROBLEM DEFINITION 1 2 3 4 5 6 7 Notes
5
RETURN ERROR 6
Error Code 7
UnrecognizedMIN X 8
UnrecognizedIMSI X 9
UnrecognizedESN a 10
MSID/HLRMismatch a 11
OperationSequenceProblem X 12
ResourceShortage X 13
OperationNotSupported X b 14
TrunkUnavailable a 15
ParameterError X c 16
SystemFailure X 17
UnrecognizedParameterValue X c 18
FeatureInactive a 19
MissingParameter a 20
21
Problem Detections: 22
23
1. The requested MAP operation is recognized, but not supported, by the receiving MSC, or the
24
requesting network entity is not authorized.
25
2. A required MSC resource is temporarily not available (e.g., congestion). 26
3. A required resource (e.g., data base access, functional entity) is not presently accessible due to a 27
failure. Human intervention may be required for resolution. 28
4. A supplied parameter value has an encoding problem (e.g., The supplied MSID parameter digit 29
values do not meet the BCD specification). 30
5. A supplied parameter value is unrecognized or has nonstandard values (e.g., Not used). 31
32
6. There is no call or call leg associated with the supplied BillingID parameter.
33
7. There is no record of the supplied MSID parameter for the supplied BillingID parameter.
34
35
Notes:
36
a. This Error Code is not an appropriate response to an CallControlDirective transaction. 37
b. It is recommended that an MSC support CallControlDirective transactions. 38
c. Include the Parameter Identifier in question as the FaultyParameter parameter. 39
40
41
4.U OANSWER 42
(New for TIA/EIA-41.6-D Section 4) 43
44
45
4 . U . 1 MSC Initiating an OAnswer 46

47
48
When the MSC determines that an active O _ A n s w e r trigger armed by a
49
TriggerAddressList parameter has been encountered requiring call processing to notify the
50
SCF network entity, the MSC shall perform the following:
51
1 Include the BillingID parameter set to the billing identifier for the call assigned by 52
the current MSC. 53

54
2 Include the MSCID parameter set to the identity of the MSC. 55
3 Include the MSID parameter set to identify the MS. 56
57
4 Include the ElectronicSerialNumber parameter.
58
5 Include the TimeDateOffset parameter. 59
60
4.T CallControlDirective 6-68 TIA/EIA-41.6-D Modifications

PN-4287
1
6 Include the TimeOfDay parameter.
2
3 7 Include the TriggerType parameter set to indicate O_Answer.
4 8 Include other applicable parameters.
5
9 Send an OAnswer INVOKE to the SCF network entity indicated by the
6
7
9
10
11
4 . U . 2 SCF Receiving an OAnswer INVOKE
12
13
When an SCF network entity receives an OAnswer INVOKE, it shall perform the
14
following:
15
16
17 1-1 Execute “WIN Service Logic” task (see 6.Y).
18 2 ENDIF.
19
3 Exit this task.
20
21
22
23
4.V ODISCONNECT
24
25
26
27 4 . V . 1 MSC Initiating an ODisconnect
28
29 When the MSC determines that an active O_Disconnect trigger armed by a
30 TriggerAddressList parameter has been encountered requiring call processing to be
31 suspended while an SCF network entity executes service logic, the MSC shall perform
32 the following:
33
34 1 Include the BillingID parameter set to the billing identifier for the call assigned by
35 the current MSC.
36
37
38
a Include the TransactionCapability parameter indicating the MSC’s capability for this
39
transaction.
40 b Include the WINCapability parameter indicating the MSC’s WIN capability for this
41 transaction.
42
3 Include the MSID parameter set to identify the MS.
43
45 5 Include the TimeDateOffset parameter.
46
6 Include the TimeOfDay parameter.
47
48 7 Include the TriggerType parameter.
49 8 Include other applicable parameters.
50
51
9 Send an ODisconnect INVOKE to the SCF network entity indicated by the
52
53 10 Start the ODisconnect Timer (ODT).
54
11 WAIT for an ODisconnect response:
55
56
57 ODisconnect RETURN RESULT Treatment:
58
12-1 Stop the timer (ODT), if it is running.
59
60
TIA/EIA-41.6-D Modifications 6-69 4.U OAnswer

PN-4287
1
2
12-2-1 IF the AnnouncementList parameter is received: 3
12-2-1-1 Execute the “Play All Announcements in the AnnouncementList” task 4
(see 3.2.5). 5
6
12-2-2 ENDIF.
7
12-2-3 Return to the calling task. 8

10
13
12-4 ENDIF.
14
13-1 Stop timer (ODT). 16
17
18
13-3 Start the ODisconnect Timer (ODT). 19

21
14 WHEN a ConnectResource INVOKE is received:
22
14-1 Stop the timer (ODT). 23
14-2 Execute the “MSC Receiving ConnectResource INVOKE” task (see 4.B.3). 24
25
14-3 CASE MSC Connect Resource result OF: 26
14-4 Disconnect Resource received: 27
28
14-4-1 Start the timer (ODT).
29
14-5 ODisconnect RETURN RESULT received: 31
32
14-5-1 GOTO ODisconnect RETURN RESULT Treatment.
33
14-6 SSFT expiration: 34
14-6-1 Start the timer (ODT). 35

36
37

40
43
44
14-9 failure at MSC: 46
47
48
14-10 message error: 50

51
52
14-11 ENDCASE. 54
55
15 WHEN the call disconnects: 56
58
59
60
4.V ODisconnect 6-70 TIA/EIA-41.6-D Modifications

PN-4287
1
16 WHEN a REJECT is received:
2
3 16-1 Stop the timer (ODT).
4 16-2 IF the ControlNetworkID parameter has been received for the subscriber:
5
16-2-1 Store the call data with the ControlNetworkID value for this call.
6
7 16-3 ENDIF.
9
10
11 17 WHEN a RETURN ERROR is received:
12
17-1 Stop the timer (ODT).
13
14
17-2 IF the Error Code indicates SystemFailure or ResourceShortage:
15 17-2-1 IF the ControlNetworkID parameter has been received for the subscriber:
16
17-2-1-1 Store the call data with the ControlNetworkID value for this call.
17
18 17-2-2 ENDIF.
19 17-3 ENDIF.
20
21
23 18 WHEN the timer (ODT) expires:
24
25
18-1 IF the ControlNetworkID parameter has been received for the subscriber:
26 18-1-1 Store the call data with the ControlNetworkID value for this call.
27
18-2 ENDIF.
28
29
31
19 ENDWAIT.
32
33
34 4 . V . 2 SCF Receiving an ODisconnect INVOKE
35
36 When an SCF network entity receives an ODisconnect INVOKE, it shall perform the
37 following:
38
39 1 IF the received message can be processed:
40
1-1 Execute “WIN Service Logic” task (see 6.Y).
41
42
1-2 Relay parameters from the service logic task.
43 1-3 Send a RETURN RESULT to the requesting MSC.
44
45
46 2-1 Send a RETURN ERROR with a proper Error Code value (see the following
47 table) to the requesting MSC.
48 3 ENDIF.
49
4 Exit this task.
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA-41.6-D Modifications 6-71 4.V ODisconnect

PN-4287
1
T a b l e 4 . V . 2 SCF ODisconnect Response
2
Problem Detection and Recommended Response from SCF 3
4
PROBLEM DEFINITION 1 2 3 4 5 6 7 8 9 Notes
5
RETURN ERROR 6
Error Code 7
UnrecognizedIMSI X 8
UnrecognizedMIN X 9
UnrecognizedESN X 10
MSID/HLRMismatch X 11
OperationSequenceProblem a 12
SystemFailure X 17
MissingParameter X c 20
21
23
1. The requested MAP operation is recognized, but not supported, by the receiving SCF network
24
25
2. A required resource (e.g., internal memory record, SCF is fully occupied) is temporarily not 26
available (e.g., congestion). 27
4. A supplied parameter value has an encoding problem (e.g., The supplied MSID parameter digit 30
values do not meet the BCD specification). 31
5. A supplied parameter value is unrecognized or has nonstandard values (e.g., Not used). 32
33
6. An expected, or required, optional parameter (e.g., MSID) was not received.
34
7. The supplied MSID parameter is not in the network entity’s range of MSIDs (suspect routing
35
error).
36
8. No record of the supplied MSID parameter exists for the supplied BillingID parameter. 37
9. The supplied MSID parameter is within the range of the network entity, but the supplied 38
ElectronicSerialNumber parameter is not valid for the MSID’s record. 39
40
Notes: 41
a. This Error Code is not an appropriate response to an ODisconnect transaction. 42
b. It is recommended that an SCF network entity supports ODisconnect transactions. 43

44
45
46
4.W TANSWER 47
48
49
50
51
4.W.1 MSC Initiating a TAnswer 52
53
When the MSC determines that an active T _ A n s w e r trigger armed by a 54
TriggerAddressList parameter has been encountered requiring call processing to notify the 55
SCF network entity, the MSC shall perform the following: 56
57
1 Include the BillingID parameter set to the billing identifier for the call assigned by 58
the Originating MSC. 59
60
4.V ODisconnect 6-72 TIA/EIA-41.6-D Modifications

PN-4287
1
2
3 3 Include the MSID parameter.
5
5 Include the TimeDateOffset parameter.
6
7 6 Include the TimeOfDay parameter.
8 7 Include the TriggerType parameter set to indicate T_Answer.
9
10
8 Include the TransactionCapability parameter.
11 9 Include the WINCapability parameter.
12
10 Include other applicable parameters.
13
14
11 Send a TAnswer INVOKE to the SCF network entity indicated by the
15
17
18
19 4.W.2 SCF Receiving a TAnswer INVOKE
20
21 When an SCF network entity receives a TAnswer INVOKE, it shall perform the
22 following:
23
24
25 1-1 Execute the “WIN Service Logic” task (see 6.Y).
26
2 ENDIF.
27
28
3 Exit this task.
29
30
31
4.X TDISCONNECT
32 (New for TIA/EIA-41.6-D Section 4)
33
34
35
4 . X . 1 MSC Initiating a TDisconnect
36
37
When the MSC determines that an active T_Disconnect trigger armed by a
38
TriggerAddressList parameter has been encountered requiring call processing to be
39
suspended while an SCF network entity executes service logic, the MSC shall perform
40
the following:
41
42 1 Include the BillingID parameter set to the billing identifier for the call assigned by
43 the Originating MSC.
44
45
46 3 Include the MSID parameter.
48
49
5 Include the TimeDateOffset parameter.
50 6 Include the TimeOfDay parameter.
51
7 Include the TriggerType parameter.
52
53
8 Include other applicable parameters.
54 9 Send a TDisconnect INVOKE to the SCF network entity indicated by the
56
10 Start the TDisconnect Timer (TDT).
57
58 11 WAIT for an TDisconnect response:
59 12 WHEN a RETURN RESULT is received:
60
TIA/EIA-41.6-D Modifications 6-73 4.X TAnswer

PN-4287
1
12-1 Stop the timer (TDT), if it is running.
2

5
6

9
12-4 ENDIF. 10
13 WHEN a REJECT is received: 11
12
13-1 Stop the timer (TDT).
13
13-2 IF the ControlNetworkID parameter has been received for the subscriber: 14
13-2-1 Store the call data with the ControlNetworkID value for this call. 15
16
13-3 ENDIF.
17

20
14 WHEN a RETURN ERROR is received:
21
14-1 Stop the timer (TDT). 22
14-2 IF the Error Code indicates SystemFailure or ResourceShortage: 23

24
14-2-1 IF the ControlNetworkID parameter has been received for the subscriber: 25
14-2-1-1 Store the call data with the ControlNetworkID value for this call. 26
27
14-2-2 ENDIF.
28
14-3 ENDIF. 29
31
32
15 WHEN the timer (TDT) expires: 33
15-1 IF the ControlNetworkID parameter has been received for the subscriber: 34
35
15-1-1 Store the call data with the ControlNetworkID value for this call.
36
15-2 ENDIF. 37

39
16 ENDWAIT. 41
42
43
44
4 . X . 2 SCF Receiving a TDisconnect INVOKE 45
46
When an SCF network entity receives a TDisconnect INVOKE, it shall perform the 47
following: 48
49
1-1 Execute the “WIN Service Logic” task (see 6.Y). 51

52
1-2 Relay parameters from the service logic task. 53
55
56
2-1 Send a RETURN ERROR with a proper Error Code value (see the following 57
table) to the requesting MSC. 58
3 ENDIF. 59
60
4.Y TDisconnect 6-74 TIA/EIA-41.6-D Modifications

PN-4287
1
4 Exit this task.
2
3
T a b l e 4 . X . 2 SCF TDisconnect Response
4
5 Problem Detection and Recommended Response from SCF
6
7
PROBLEM DEFINITION 1 2 3 4 5 6 7 8 9 Notes
8 RETURN ERROR
9 Error Code
10 UnrecognizedIMSI X
11 UnrecognizedMIN X
12 UnrecognizedESN X
13 MSID/HLRMismatch X
14 OperationSequenceProblem a
19 SystemFailure X
22 MissingParameter X c
23
24
Problem Detections:
25
1. The requested MAP operation is recognized, but not supported, by the receiving SCF network
26
27
28
2. A required resource (e.g., internal memory record, SCF is fully occupied) is temporarily not
29
available (e.g., congestion).
30 3. A required resource (e.g., data base access, functional entity) is not presently accessible due to a
31 failure. Human intervention may be required for resolution.
32 4. A supplied parameter value has an encoding problem (e.g., The supplied MSID parameter digit
33 values do not meet the BCD specification).
34 5. A supplied parameter value is unrecognized or has nonstandard values (e.g., Not used).
35
6. An expected, or required, optional parameter (e.g., MSID) was not received.
36
37
7. The supplied MSID parameter is not in the network entity’s range of MSIDs (suspect routing
38
error).
39 8. No record of the supplied MSID parameter exists for the supplied BillingID parameter.
40 9. The supplied MSID parameter is within the range of the network entity, but the supplied
41 ElectronicSerialNumber parameter is not valid for the MSID’s record.
42
43 Notes:
44 a. This Error Code is not an appropriate response to an TDisconnect transaction.
45 b. It is recommended that an SCF network entity supports TDisconnect transactions.
46
47
48
49 4.Y UNRELIABLE CALL DATA
50
51
52
This section describes procedures at an SCF network entity and an MSC when the SCF
53
network entity determines call data recovery is needed.
54
55
56
57
58
59
60
TIA/EIA-41.6-D Modifications 6-75 4.Y TDisconnect

PN-4287
1
4 . Y . 1 SCF Initiating an Unreliable Call Data 2
3
When an SCF network entity determines call data recovery is needed, it shall perform the 4
following: 5
6
1 Recover data about which MSCs were handling calls for subscribers served by this
7
SCF.
8
2 Recover data related to all calls that were in progress when the failure occurred. 9
3 FOR each MSC that is handling calls served by this SCF network entity: 10
11
3-1 Include the MSCID parameter set to the identity of this SCF network entity.
12
3-2 Include the ControlNetworkID parameter set to the identity of this SCF network 13
entity. 14
3-3 Send an UnreliableCallData INVOKE to the MSC. 15

16
3-4 Start the Unreliable Call Data Timer (URCDT).
17
3-5 WAIT for an Unreliable Call Data response: 18
3-6 WHEN a CallRecoveryReport INVOKE is received: 19

20
3-6-1 Stop timer (URCDT). 21
3-6-2 IF the received message can be processed: 22
23
3-6-2-1 Execute the “SCF Receiving CallRecoveryReport INVOKE” task (see
24
4.Y.4).
25
3-6-2-2 Start the Unreliable Call Data timer (URCDT). 26
3-6-2-3 Remain in this state. 27
28
3-6-3 ELSE (the received message cannot be processed):
29
3-6-3-1 Send a RETURN ERROR with a proper Error Code value (see the 30
following table) to the MSC. 31
3-6-3-2 Start the Unreliable Call Data timer (URCDT). 32

33
3-6-3-3 Remain in this state.
34
3-6-4 ENDIF. 35
3-7 WHEN a RETURN RESULT is received: 36

37
3-7-2 IF the message cannot be processed: 39
40
41
3-7-2-2 Exit this task. 42
3-7-3 ENDIF. 43
44
45

48
49
3-9 WHEN timer (URCDT) expires: 50

52
3-10 ENDWAIT. 54
55
4 ENDFOR.
56
58
59
60
4.Y Unreliable Call Data 6-76 TIA/EIA-41.6-D Modifications

PN-4287
1
T a b l e 4 . Y . 1 SCF CallRecoveryReport Response
2
3 Problem Detection and Recommended Response from SCF
4
PROBLEM DEFINITION 1 2 3 4 5 6 Notes
5
6 RETURN ERROR
7 Error Code
8 UnrecognizedIMSI a
9 UnrecognizedMIN a
10 UnrecognizedESN a
11 MSID/HLRMismatch a
12 OperationSequenceProblem X
17 SystemFailure X
20 MissingParameter a
21
22 Problem Detections:
23
1. The requested MAP operation is recognized, but not supported by the receiving network entity, or
24
the requesting network entity is not authorized.
25
2. A required receiving network entity resource is temporarily not available (e.g., congestion).
26
27
3. A required resource (e.g., data base access, functional entity) is not presently accessible due to a
28
failure. Human intervention may be required for resolution.
29 4. A supplied parameter value is unrecognized or has non-standard values (e.g., CallRecoveryIDList).
30 5. The received message cannot be correlated with a transaction.
31 6. A supplied parameter value has an encoding problem (e.g., CallRecoveryIDList).
32
33 Notes:
34
a. This Error Code is not an appropriate SCF response to a CallRecoveryReport transaction.
35
b. It is recommended that an SCF support CallRecoveryReport transactions.
36
37
38
39 4 . Y . 2 MSC Receiving UnreliableCallData INVOKE
40
41
When a MSC receives a UnreliableCallData INVOKE, it shall perform the following:
42
43 1 IF the received message can be processed:
44
1-1 Execute “MSC Initiating a Call Recovery Report” task (see 4.Y.3).
45
46 1-2 Send a RETURN RESULT to the requesting SCF network entity.
47 2 ELSE (the received message cannot be processed):
48
2-1 Send a RETURN ERROR with a proper Error Code value (see the following
49
table) to the requesting SCF network entity.
50
51 3 ENDIF.
52 4 Exit this task.
53
54
55
56
57
58
59
60
TIA/EIA-41.6-D Modifications 6-77 4.Y Unreliable Call Data

PN-4287
1
T a b l e 4 . Y . 2 MSC UnreliableCallData Response
2
Problem Detection and Recommended Response 3
from MSC to SCF 4
5
PROBLEM DEFINITION 1 2 3 4 5 6 Notes
6
RETURN ERROR 7
Error Code 8
UnrecognizedIMSI a 9
UnrecognizedMIN a 10
UnrecognizedESN a 11
MSID/HLRMismatch a 12
OperationSequenceProblem a 13
SystemFailure X 18
MissingParameter X c 21
22
24
1. The requested MAP operation is recognized, but not supported by the receiving MSC, or the
25
requesting network entity is not authorized.
26
2. A required MSC resource is temporarily not available (e.g., congestion). 27
4. A supplied parameter value is unrecognized or has non-standard values (e.g., 30
SenderIdentificationNumber). 31
5. An optional parameter required for this operation is missing (e.g., ControlNetworkID). 32

33
6. A supplied parameter value has an encoding problem (e.g., The supplied
34
SenderIdentificationNumber parameter digit values do not meet the BCD specification).
35
Notes: 36
37
a. This Error Code is not an appropriate MSC response to an UnreliableCallData transaction.
38
b. It is recommended that an MSC support UnreliableCallData transactions. 39
c. Include the Parameter Identifier in question as the FaultyParameter parameter. 40
41
4 . Y . 3 MSC Initiating a Call Recovery Report 42

43
44
Upon request, the MSC shall perform the following:
45
1 The MSC compiles a list of CallRecoveryID parameters for all calls matching the 46
received ControlNetworkID value. 47

48
2 WHILE the MSC has call data to convey to the SCF:
49
2-1 Include the CallRecoveryIDList parameter set to the Billing IDs used to identify 50
calls served at the MSC which have ended and have not been acknowledged by 51
the SCF, the TimeOfDay set to the time of day (UTC) the calls ended, and the 52
TimeDateOffset set to the offset of the local time that the calls ended at the 53
MSC. 54
2-2 Send a CallRecoveryReport INVOKE to the requesting SCF. 55

56
2-3 Start the Call Recovery Report Timer (CRRT). 57
2-4 WAIT for a CallRecoveryReport response: 58
59
2-5 WHEN a RETURN RESULT is received:
60
4.Y Unreliable Call Data 6-78 TIA/EIA-41.6-D Modifications

PN-4287
1
2-5-1 Stop timer (CRRT).
2
3 2-5-2 IF the message cannot be processed:
4 2-5-2-1 Execute “Local Recovery Procedures” task (see 3.5.1).
5
6
7 2-5-3 ENDIF.
8 2-5-4 CallRecoveryIDs associated with this RETURN RESULT may be removed
9 from MSC storage.
10
11
12 2-6-1 Stop timer (CRRT).
13
14
15
16 2-7 WHEN timer (CRRT) expires:
17
18
20 2-8 ENDWAIT.
21
3 ENDWHILE.
22
24
25
26
4 . Y . 4 SCF Receiving a CallRecoveryReport INVOKE
27
28
When an SCF receives a CallRecoveryReport INVOKE, it shall perform the following:
29
1 Update the SCF data with the received information.
30
31 2 Send a RETURN RESULT to the invoking MSC.
33
34
35 6 COMMON VOICE FEATURE PROCEDURES
36
37
38
39
6.Y WIN SERVICE LOGIC
40
(TIA/EIA-771 page 128, Section 6)
41
42 When WIN service logic is invoked, the SCF network entity shall perform the
43 following1:
44
45
1 Execute the WIN service logic program.
46 2 WAIT for completion of WIN service logic execution.
47
3 WHEN execution of WIN service logic is complete:
48
49
3-1 Include applicable parameters.
50 3-2 Return to the calling task.
51
4 WHEN data is to be retrieved from an SDF network entity:
52
53 4-1 Execute the “SCF Initiating a Search task (see 4.I.1).
55
56
57 1This procedure identifies interactions with other procedures and may be different than
58 actual implementations.
59
60
TIA/EIA-41.6-D Modifications 6-79 4.Y Unreliable Call Data

PN-4287
1
5 WHEN data is to be updated in an SDF network entity:
2
5-1 Execute the “SCF Initiating a Modify task (see 4.G.1). 3

5
6 WHEN user interaction is required:
6
User interaction required: 7
6-1 IF an SRF network entity external to the MSC is indicated: 8

9
6-1-1 Execute “SCF Initiating a Seize Resource” task (see 4.J.1). 10
6-1-2 IF the task was unsuccessful: 11
12
6-1-2-1 Include parameters for default treatment.
13
6-1-2-2 Return to the calling task. 14
6-1-3 ELSE (the task was successful): 15
16
6-1-3-1 Execute the ”SCF Initiating Connect Resource” task (see 4.B.1).
17
6-1-3-2 IF the task was unsuccessful: 18
6-1-3-2-1 Include parameters for default treatment. 19

20
21
6-1-3-3 ENDIF. 22
6-1-3-4 IF further user interaction is required: 23

24
6-1-3-4-1 Execute the “SCF Initiating Disconnect Resource” task (see 25
4.D.1). 26
6-1-3-4-2 GOTO User Interaction Required. 27
28
6-1-3-5 ELSEIF immediate disconnection of the MSC to the SRF network
29
entity is required:
30
6-1-3-5-1 Execute the “SCF Initiating Disconnect Resource” task (see 31
4.D.1). 32
6-1-3-6 ENDIF. 33
34
6-1-4 ENDIF.
35
6-2 ELSE (an SRF network entity external to the MSC is not indicated): 36
6-2-1 Execute “Initiation of Remote User Interaction Directive” task (see 4.39.1). 37
38
6-3 ENDIF.
39
7 WHEN remote service logic execution is required1: 41

42
7-1 Execute “SCF Initiating Service Request” task (see 4.K.1). 43
7-2 IF the remote service logic execution is unsuccessful: 44
45
7-2-1 Include parameters for default treatment.
46
7-3 ENDIF. 48
49
50
8 WHEN call control intervention is required: 51
52
53
1If there is an interaction between the requesting MSC and an SRF network entity that 54
may interfere with the remote service logic execution, the SCF network entity may have 55
to disconnect the MSC from the SRF network entity prior to invocation of remote 56
service logic. This potential interaction should be identified in agreements between the 57
requesting and serving network entities. 58

59
60
6 Common Voice Feature Procedures 6-80 TIA/EIA-41.6-D Modifications

PN-4287
1
8-1 Execute the “SCF Initiating a Call Control Directive” task (see 4.T.1)
2
4
5
9 ENDWAIT.
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
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.6-D Modifications 6-81 6 Common Voice Feature Procedures

PN-4287
1
7 OPERATION TIMER VALUES 2
(TIA/EIA-41.6-D, page 6-400) 3

4
The following table provides a summary of the timers used for MAP operations. The 5
timer values specified in this table are default values only and should be optimized for 6
actual operating environments. Some timers are locally defined and are not in this table 7
(e.g., alerting timer, no answer timer, page response timer, maximum interaction timer, 8
interdigit timer). 9
10
11
T a b l e 6 3 Operation Timer Values
12
Timer Default Started when Normally stopped when Action when 13
(sec.) timer expires 14
15
BDISCT 6 BulkDisconnection BulkDisconnection Execute 16
INVOKE is sent. RETURN RESULT or recovery 17
Bulk RETURN ERROR is procedures. 18
Disconnection received. 19
20
Timer
21
CCDT 6 CallControlDirective CallControlDirective Execute 22
Call Control RETURN ERROR is procedures.

24
25
Directive Timer received. 26
27
ODT 16 ODisconnect INVOKE ODisconnect RETURN Execute
28
(or a subsequent RESULT or RETURN recovery 29
ODisconnect RemoteUser- ERROR is received, procedures. 30
Timer InteractionDirective RemoteUserInteraction- 31
32
RETURN RESULT) is Directive INVOKE is
33
sent, or a subsequent received, or Connect- 34
DisconnectResource Resource INVOKE is 35
INVOKE is received. received. 36

37
CRRT 6 CallRecoveryReport CallRecoveryReport Execute 38
Call Recovery RETURN ERROR is procedures. 40
41
Report Timer received. 42
TDT 16 TDisconnect INVOKE TDisconnect RETURN Execute 43

44
is sent. RESULT or RETURN recovery
45
TDisconnect ERROR is received. procedures. 46
Timer 47
URCDT 10 UnreliableCallData UnreliableCallData Execute 48

49
INVOKE is sent or RETURN RESULT or recovery
50
Unreliable Call subsequent Call- CallRecoveryReport procedures. 51
Data Timer RecoveryReport INVOKE or RETURN 52
53
RETURN RESULT is ERROR is received.
54
sent. 55
56
57
58
59
60
7 Operation Timer Values 6-82 TIA/EIA-41.6-D Modifications

PN-4287
1
2
3
X ANNEX X: HIGH LEVEL SDL MODELS FOR
4
5
WIN
(TIA/EIA/IS-771.6, Page 6-134)
6
7
8
9 X . 5 . 4 SDL Model of TriggerAddressList Processing
10
11
SDL modeling of TriggerAddressList processing is illustrated in Figure X-25. This
12
13
modeling is intended to describe the relationship of the TriggerAddressList stored in a
14 subscriber profile and a TriggerAddressList received during call processing (i.e., dynamic
15 trigger arming). When a TriggerAddressList is received during call processing, the new
16
trigger arming information is used to process that call leg and does not alter the
17
18
TriggerAddressList stored in the subscriber profile.
19
20
Begin call
21 processing
22
23
Arm WIN triggers
24 from
25 TriggerAddressList
in subscriber profile
26
27
28
Start trigger processing
29
30
31
Information flow
32 from SCF
33
34
35
YES TriggerAddressList NO
36
received* ?
37
38 Complete trigger
processing
39
YES TriggerAddressList NO
40 for call forwarding
41 leg?
Process the Disarm all subscribed
42 call forwarding leg WIN triggers
43 using the WIN triggers
received in the
44 TriggerAddressList**
45 Arm WIN triggers in
received
46 TriggerAddressList
47
48
49 Complete trigger
processing
50
51
52
53
54 * One or more TriggerAddressList parameters may be received during call processing.
55 ** Triggers for the call leg prior to forwarding are no longer applicable.
56
57
Figure X-25 SDL Model of TriggerAddressList Processing
58
59
60
TIA/EIA-41.6-D Modifications 6-83 7 Operation Timer Values

PN-4287
1
When a TriggerAddressList parameter is received for a call forwarding leg, the new
2
TriggerAddressList is used to process the call forwarding leg and will not be used for 3
subsequent call originations or terminations. Any previously armed triggers are not 4
applicable for processing the call forwarding leg. 5

6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
7 Operation Timer Values 6-84 TIA/EIA-41.6-D Modifications

PN-4287
1
2
3
CHAPTER 7
4
MODIFICATIONS TO TIA/EIA/IS-771.7 DISTRIBUTED FUNCTIONAL PLANE
5
6
7
8
CONTENTS
9
10
LIST OF FIGURES .................................................................................................................. ii
11
12
13
LIST OF TABLES................................................................................................................... iii
14
15
REVISION HISTORY.............................................................................................................. iv
16
17 5 SSF/CCF CALL AND SERVICE LOGIC MODEL............................................................ 1
18 5.1 General............................................................................................................ 1
19
5.1.3 Service Interactions Manager (SIM) - SCF................................................. 1
20
21
5.2 SSF/CCF Model............................................................................................... 3
22 5.2.2.1 Originating BCSM.............................................................. 3
23 5.2.2.2 Terminating BCSM ........................................................... 13
24 5.2.2.3 BCSM Transitions ............................................................ 20
25
5.2.3 BCSM Detection Points ....................................................................... 24
26
27
5.2.3.4 Trigger Types and Trigger Precedence.................................... 24
28
29
Annex D (informative) Notes on Trigger Concepts and Usage ......................................................... 43
30 Dynamic Trigger Arming Mechanism ............................................................................. 43
31
32
33
34
35
36
37
38
39
40
4
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA/IS-771.7 Modifications 7-i Contents

PN-4287
LIST OF FIGURES 1
2
3
Figure 5 Service Interactions Manager at the SCF.............................................. 1 4

5
Figure 8 Originating Call Model .................................................................... 4
6
Figure 9 Terminating Call Model ................................................................. 13 7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
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 7-ii TIA/EIA/IS-771.7 Modifications

PN-4287
1
2
3 LIST OF TABLES
4
5 Table 1 Originating BCSM Transitions ........................................................ 20
6
Table 2 Terminating BCSM Transitions....................................................... 22
7
8 Table 4 WIN Trigger Precedence for Originating BCSM .................................. 25
9 Table 5 WIN Trigger Precedence for Terminating BCSM ................................. 26
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
4
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA/IS-771.7 Modifications 7-iii List of Tables

PN-4287
REVISION HISTORY 1
2
3
4
5
Rev. Date Remarks 6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
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 7-iv TIA/EIA/IS-771.7 Modifications

PN-4287
1
2
3 5 SSF/CCF CALL AND SERVICE LOGIC
4
5
MODEL
6
7
8
9 5.1 General
10
11
12
13
14 5.1.3 Service Interactions Manager (SIM) - SCF
16
17 The service interactions manager (SIM) at the SCF coordinates the invocation of features
18 applicable for a subscriber at a given trigger at a Detection Point (DP). The SIM has
19 knowledge of the relevant SCF-executed features resident on the same SCF and an
20 indication when another feature on a separate SCF requires interaction at certain points in
21 the SIM logic flow. When service logic is distributed across multiple SCFs, the SIM is
22 also distributed. The first SIM invoked by the trigger must coordinate the precedence and
23 data changes that affect call processing within the SCF and between SCFs. This is
24 illustrated in Figure 5.
25
26
27 SCF SCF
28
29
30 FSLP i FSLP j FSLP x FSLP y
31 FSLP k FSLP z
32
33
SIM SIM
34
35
36
37
38
39
40
4
42
SSF/CCF
43
44
Legend
45
46
CCF Call Control Function
47 FSLP Feature Service Logic Program
48 SCF Service Control Function
49 SIM Service Interactions Manager
50
SSF Service Switching Function
51
52
Figure 5 Service Interactions Manager at the SCF
53
54
55
56
57
58
59
60
TIA/EIA/IS-771.7 Modifications 7-1 Originating BCSM

PN-4287
Basic rules include: 1

2
a. Once an SCF-executed feature is given control, it must complete its task before
3
returning control to the SIM. The setting of Event Detection Point - Response
4
(EDP-Rs) indicates the need for the feature to regain control at a future DP, but
5
yields current control of service logic to other features.
6
b. SIM rules include the actions to be taken based on the response of the feature’s 7
invocation. Additional features in this SCF may be invoked or a response may 8
be prepared for the entity (another SIM or BCM) which had invoked the SIM 9
processing. 10
11
c. The SIM coordinates the response to the invoking entity (SSF or CCF). The 12
response is based on the responses of all features invoked. A single response is 13
sent to the invoking entity regardless of the number of features invoked. 14
15
Coordination of EDP-N, EDP-R, TDP-N and TDP-R events and triggers is done
16
by the SIM. Thus, the response to the invoking entity may contain information
17
that would not be in a single feature’s response, but represents a synthesis of all
18
of the features that were invoked.
19
d. The SIM determines if dynamically armed triggers are required after service logic 20
21
execution is completed. If the call is not being redirected by service logic,
22
dynamically arming triggers will result in any previously armed triggers for the
23
call being disarmed. The dynamically armed triggers will be armed for the
24
remainder of the call in progress (or until a subsequent TriggerAddressList is 25
received). If the call is being redirected by service logic, dynamically armed 26
triggers will be applied to the redirected call leg. 27
28
29
As part of managing service execution interactions, the SIM is responsible for handling
30
WIN Feature Code processing. For example, a SIM associated with the
31
Single_Introducing_Star and Home_System_Feature_Code triggers, receives WIN feature
32
codes entered by a subscriber. This SIM will determine where feature codes are to be
33
processed and, if necessary, to forward feature codes to another physical platform for
34
processing.
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Originating BCSM 7-2 TIA/EIA/IS-771.7 Modifications

PN-4287
1
2
3
5.2 SSF/CCF Model
4
5
6
7 5.2.2.1 Originating BCSM
9
10 The originating half of the BCSM corresponds to that portion of the BCSM associated
11 with the originating party (see Figure 8). The descriptions for each of the PICs in the
12 originating half of the BCSM are described below:
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
4
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
1
O_Null O_Exception
2
3
O_Abandon DP 4
Origination_Attempt_DP 5
6
origination_denied
Authorize_Origination_Attempt 7
8
9
10
Origination_Attempt_Authorized DP 11
12
collect_failure
Collect_Information 13
14
15
16
Collected_Information DP
17
invalid_information 18
Analyze_Information
19
20
21
route_busy
Analyzed_Information DP 22
23
24
Select_Route
25
Route_Select_Failure DP 26
route_failure 27
authorization_route_failure 28
Authorize_Call_Setup
29
30
O_Called_Party_Busy DP 31
32
Send_Call
33
O_Mid_Call DP 34
35
O_Term_Seized DP 36
37
O_Alerting 38
39
O_Mid_Call DP O_No_Answer DP
40
41
O_Answer DP 42
43
O_active_failure
O_Active 44
45
O_Mid_Call DP
O_Re-answer DP 46
47
O_Suspend DP reconnect 48
O_suspend_failure 49
O_Suspended 50
O_Disconnect DP
51
52
O_Mid_Call DP
53
54
No WIN triggers defined for the DP in this standard 55
56
Figure 8 Originating Call Model 57
58
59
60

PN-4287
1
2
O_Null
3
4
Entry Event:
5
– Disconnect and clearing of a previous call. (DPs: O_Disconnect and
6
O_Abandon).
7
8 – Default handling of exceptions by SSF/CCF completed (Transition from
9 O_Exception PIC).
10
11
Functions:
12
13 – Clear any resources allocated to the originating party (no call exists, no call
14 reference exists, no radio channel allocated for call, etc.).
15
16
17
Exit Event:
18
– Indication of a desire to place an outgoing call (e.g., an indication is received
19
from the RACF of an origination attempt by an MS user).
20
(DP: Origination_Attempt).
21
22 – Other indication from an originating party of a desire to place a call (e.g., ISDN-
23 UP IAM message). (DP: Origination_Attempt).
24
25 – The following exception exit event is applicable to the O_Null PIC. For this
26 PIC, if the call encounters this exception during O_Null PIC processing, the
27 exception event is not visible because there is no corresponding DP.
28
29
i) The O_Abandon occurs when the calling party disconnects.
30
31
32
33 Authorize_Origination_Attempt
34
35 Entry Event:
36
– An indication is available that the originating MS needs to be authorized.
37
(DP: Origination_Attempt).
38
39
40 Functions:
4
42
– Collects the information required to authorize the call for MS origination.
43
– The originating MS rights are checked using the MS identity and service profile.
44
The right of the MS to place the call with given properties (e.g., bearer
45
capability, subscriber profile restrictions) is verified.
46
47 – For MS origination, sends an indication to the RACF to select a radio channel
48 (i.e., select RCF) for MS origination and order the MS to use the channel. If no
49 channel is immediately available, the RACF may invoke Priority Access and
50 Channel Assignment (PACA) to wait for a channel to become available.
51
52
53
Exit Event:
54
– Authority/ability to place outgoing call verified. For MS origination, radio
55
channel is available and assigned to the MS.
56
(DP: Origination_Attempt_Authorized).
57
58 – Authority/ability to originate call is denied. This event causes a transition to the
59 O_Exception PIC.
60

PN-4287
– Failure to select a radio channel for the MS. This event causes a transition to 1
the O_Exception PIC. 2
3
– A disconnection indication is received from the originating party.
4
(DP: O_Abandon).
5
6
7
Collect_Information
8
9
Entry Event:
10
– Authority/ability to place outgoing call verified. For MS origination, radio 11
channel available and assigned to the MS. 12
(DP: Origination_Attempt_Authorized). 13
14
15
Functions: 16
17
– Initial information package/dialing string (e.g., service codes, prefixes, dialed
18
address digits) being collected from originating party. Information being
19
examined according to dialing plan to determine end of collection. No further
20
action may be required if an en bloc signaling method is in use (e.g., an
21
incoming SS7 trunk).
22
– Subsequent digit collection according to the subscriber profile (e.g., for PIN 23
collection). After digit collection is completed, the SSF/CCF should be able to 24
verify that the MS is authorized for the outgoing call. 25

26
27
Exit Event: 28
29
– Availability of complete initial information package/dialing string from
30
originating party. (This event may have already occurred in the case of en bloc
31
signaling, in which case the duration of this PIC is zero).
32
(DP: Collected_Information).
33
– Originating party abandons call. (DP: O_Abandon). 34
35
– After digit collection is complete, authority to originate call is denied. This 36
event causes a transition to the O_Exception PIC. 37
38
– Information collection error has occurred (e.g., invalid dial string format, digit
39
collection timeout). This event causes a transition to the O_Exception PIC.
40
41
Comment: Some digit analysis is required to determine the end of dialing. However, it 42
is assumed that this analysis may be modeled as separable from the rest of digit analysis, 43
which occurs in the Analyze_Information PIC. There is no intention to specify an 44
implementation. However, an MSC should externally present the separable views 45
described1. 46
47
48
49
50
51
52
53
54
1 The separable views are provided by supporting distinct DPs for Collected_Information and
55
Analyzed_Information and by populating information flows accordingly for corresponding
56
TDP and EDP information flows to the SCF.
57
58
59
60

PN-4287
1
2
Analyze_Information
3
4
Entry Event:
5
– Availability of complete initial information package/dialing string from
6
originating party. (DP: Collected_Information).
7
8
9 Functions:
10
– Information being analyzed and/or translated according to dialing plan to
11
determine routing address and call type (e.g., termination to MS, local exchange
12
call, transit exchange call, international exchange call).
13
14
15 Exit Event:
16
17
– Availability of routing address and call type. (DP: Analyzed_Information).
18
– The invalid information event (e.g., invalid dialed digits). This event causes a
19
transition to the O_Exception PIC.
20
21 – Originating party abandons the call. (DP: O_Abandon).
22
23
24
Comment: Note that routing address does not necessarily mean that the final physical
25
route has been determined (e.g., route list has not been searched, hunt groups have not
26
been searched, directory number has not yet been translated to a physical port address),
27
though this may be the case (e.g., when routing to a special private facility).
28
29
30 Select_Route
31
32 Entry Event:
33
– Availability of routing address and call type. (DP: Analyzed_Information).
34
35 – Route failure reported from the Send_Call PIC or O_Alerting PIC.
36
37
38
Functions:
39
– Routing address and call type being interpreted. The next route is being selected.
40
This may involve sequentially searching a route list, translating a directory
4
number into a physical port address, etc. The individual destination resource out
42
of a resource group (e.g., a multi-line hunt group, a trunk group) is not selected.
43
44
45 Exit Event:
46
47
– Unable to select a route (e.g., unable to determine a correct route, no more routes
48
on the route list). (DP: Route_Select_Failure).
49
– The route_busy event leading to the Analyze_Information PIC. Route_busy is a
50
non-WIN transition which is part of a basic call. If the trunk group selected for
51
the call is busy at this switch, the SSF/CCF attempts to route the call on the
52
next trunk group that has been specified for the call. Call processing moves to
53
the Analyze_Information PIC when routing to a particular intra-network or inter-
54
network carrier has been tried and an alternate carrier is allowed.
55
56 – Terminating resource (group) to which call should be routed has been identified.
57 This event causes call processing to move to the Authorize_Call_Setup PIC.
58
59 – Originating party abandons the call. (DP: O_Abandon).
60

PN-4287
Authorize_Call_Setup 1
2
Entry Event: 3
4
– Terminating resource (group) to which call should be routed has been identified.
5
6
Functions: 7
8
– The authority of the calling party to place this particular call is verified.
9
10
Exit Event: 11
12
– Authority of originating party to place this call is denied (e.g., business group 13
restriction mismatch, toll restricted calling line). This event causes a transition 14
to the O_Exception PIC. 15
16
– Authority of originating party to place this call is verified. This event causes
17
call processing to move to the Send_Call PIC.
18
– Originating party abandons the call. (DP: O_Abandon). 19

20
21
22
Send_Call
23
24
Entry Event:
25
– Authority of originating party to place this call is verified. 26
27
28
Functions:
29
– The originating half BCSM sends an indication to the terminating half BCSM of 30
the desire to set up a call to the specified called party. Continued processing of 31
call setup (e.g., ringing, audible ring indication) is taking place. The originating 32
half BCSM waits for the indication that the call has been answered by the 33
terminating party. 34
35
36
Exit Event: 37
38
– An indication is received from the terminating half BCSM that the terminating
39
party is busy. (DP: O_Called_Party_Busy).
40
In addition to terminating party busy events, the following call_rejected 41
conditions are also treated as O_Called_Party_Busy events: 42

43
i) a termination_denied indication is received from the terminating half BCSM 44
(Authorize_Termination_Attempt PIC); or, 45
46
ii) a call_rejected indication is received from the terminating half BCSM 47
(T_Alerting PIC) that does not specify busy. 48
49
– An indication is received from the terminating half BCSM that the terminating
50
party does not answer. (DP: O_No_Answer).
51
– An indication is received from the terminating half BCSM that the terminating 52
party is being alerted. (DP: O_Term_Seized). 53
54
– An indication is received from the terminating half BCSM that the call is 55
accepted and answered by the terminating party. (DP: O_Answer DP). 56
57
– A route_failure event is detected when:
58
59
60

PN-4287
1
2
i) an indication of a T_Busy event specifying route busy; is received from the
3
terminating half BCSM, or
4
ii) an indication of a call_rejected event specifying route busy (received when
5
the route is found to be busy at a switch other than the local switch) is
6
received from the terminating half BCSM (T_Alerting PIC).
7
8 iii) an indication of a presentation_failure event specifying route busy is
9 received from the terminating half BCSM (Present_Call PIC).
10
11 In all these cases, the originating half BCSM returns to the Select_Route PIC.
12 This event is not detected at a DP.
13
Note: The route_failure event takes precedence over the O_Called_Party_Busy
14
and O_No_Answer events.
15
16 – An indication is received from the RCF of a service feature request by the
17 originating MS. (DP: O_Mid_Call).
18
19 – For SS7-supported trunk interface, the authorization_route_failure event occurs
20 when the continuity check procedure results in failure. This event causes a
21 transition to the O_Exception PIC.
22
23
– Originating party abandons the call. (DP: O_Abandon).
24
25
26 O_Alerting
27
28 Entry Event:
29
30
– An indication is received from terminating half BCSM that the terminating party
31
is being alerted. (DP: O_Term_Seized).
32
33 Functions:
34
35 – Continue processing of call setup.
36
– Waiting for indication from the terminating half BCSM that the call has been
37
answered by the terminating party.
38
39
40 Exit Event:
4
42
– A route failure event is detected when all of the following conditions are met:
43
i) the O_Called_Party_Busy event or O_No_Answer event occurs as specified
44
below,
45
46 ii) call forwarding applies,
47
48 iii) there are more called party numbers left to try.
49
50
Note: the Route_Failure event takes precedence over the O_Called_Party_Busy
51
and O_No_Answer events.
52
In this case the originating call portion returns to the Select_Route PIC. This
53
event is not detected at a DP in WIN.
54
55 – An indication is received from the terminating half BCSM that the terminating
56 party does not answer within a specified time period. (DP: O_No_Answer).
57
58 – An indication is received from the terminating half BCSM that the call is
59 accepted and answered by the terminating party. (DP: O_Answer).
60

PN-4287
– From this PIC, the O_Called_Party_Busy event occurs either when: 1

2
i) an indication of a call_rejected event specifying user busy is received from
3
the terminating half BCSM (T_Alerting PIC), or
4
ii) an indication of a call_rejected event not specifying user busy is received 5
from the terminating half BCSM (T_Alerting PIC). For example, the 6
terminating party may reject the call. 7
8
The originating half BCSM moves to the O_Called_Party_Busy DP. 9
10
– An indication is received from the RCF of a service feature request by the
11
originating MS. (DP: O_Mid_Call).
12
– Originating party abandons the call. (DP: O_Abandon) 13

14
15
16
O_Active
17
18
Entry Event:
19
– An indication is received from the terminating half BCSM that the call is 20
accepted and answered by the terminating party. (DP: O_Answer). 21

22
23
Functions: 24
25
– Connection established between originating and terminating party. Message
26
accounting/charging data may be collected. Call supervision is being provided.
27
28
Exit Event: 29
30
31
32
– A disconnect indication is received from the originating party. 33
(DP: O_Disconnect). 34
35
– A disconnect indication is received from the terminating party via the 36
terminating half BCSM. (DP: O_Disconnect). 37
38
– A suspend disconnect indication is received from the terminating party via the 39
terminating half BCSM. (DP: O_Suspend). 40
41
– A connection failure occurs. This event causes a transition to the O_Exception 42
PIC. 43
44
45
O_Suspended 46
47
Entry Event: 48
49
– A suspend disconnect indication is received from the terminating party via the 50
terminating half BCSM. (DP: O_Suspend). 51
52
Functions (the function of this PIC is not currently supported for MS originated calls): 53
54
– The connection with the originating party is maintained and depending on the 55
incoming access connection, appropriate signaling takes place. 56
57
58
59
60

PN-4287
1
2
i) In case that a disconnect indication is received from the terminating half
3
BCSM, this PIC is immediately exited to the O_Disconnect DP without
4
any action. As an option for MS originated calls, the call can be continued
5
for an appropriate period in order to offer follow-on initiated by
6
O_Mid_Call.
7
ii) If the re-answer indication from the terminating half BCSM is received, the
8
originating and terminating parties are reconnected.
9
10 iii) Other features may be required during this PIC (for further study).
11
12
13
Exit Event:
14
15 – Connection to the terminating party is resumed. The originating half BCSM
16 returns to the O_Active PIC. (DP: O_Re-answer).
17
18 Note: This transition to the O_Active PIC is not applicable for wireless calls.
19
20
21
22
– A disconnection indication is received from the originating party.
23
(DP: O_Disconnect).
24
25 – A disconnection indication is received from the terminating party.
26 (DP: O_Disconnect).
27
28 – An exception event is encountered. This event causes a transition to the
29 O_Exception PIC.
30
31
– An indication of expiration of the timer waiting for re-answer request is received
32
from the terminating half BCSM. (DP: O_Disconnect).
33
– A trigger at O_Mid_Call is not initiated during an appropriate period.
34
(DP: O_Disconnect).
35
36
37
O_Exception
38
39
Entry Event:
40
4 – An exception event is encountered as described above for each PIC.
42
43
44
Functions:
45
– Default handling of the exception condition is being provided. This includes
46
general actions necessary to ensure no resources remain inappropriately allocated,
47
such as:
48
49 i) If any relationships exist between the SSF and SCF(s), send an error
50 information flow to the SCF(s) closing the relationships and indicating that
51 any outstanding call handling instructions will not run to completion.
52
53 ii) The SSF/CCF should make use of vendor-specific procedures to ensure
54 release of resources so that radio, trunk, and other resources are made
55 available for new calls.
56
57
58
59
60

PN-4287
Exit Event: 1
2
– Default handling of the exception condition by SSF/CCF completed.
3
(Transition to O_Null PIC)
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
1
2
5.2.2.2 Terminating BCSM
3
4
5 The terminating half of the BCSM corresponds to that portion of the BCSM associated
6 with the terminating party (see Figure 9). The description for each of the PICs in the
7 terminating half of the BCSM are described below:
8
9
10 T_Null T_Exception
11
12
T_Abandon DP
13
Termination_Attempt_DP
14
15 termination_denied
Authorize_Termination_Attempt
16
17
18
19 Termination_Attempt_Authorized DP
20 T_Busy DP
21 Select_Facility
22
23
24
SS7_failure
25 Facility_Selected_and_Available DP
26
presentation_failure
27 Present_Call
28
29
30
Call_Accepted DP
31
32
33
T_Alerting
34 T_No_Answer DP
35
call_rejected
36 T_Answer DP
37
38 T_active_failure
T_Active
39
40 T_Mid_Call DP
4
T_Re-answer DP
42 T_Suspend DP
reconnect
43
T_suspend_failure
44 T_Suspended
45
T_Disconnect DP
46
47
48
49 No WIN triggers defined for the DP in this standard
50
51 Figure 9 Terminating Call Model
52
53
54
55
56
57
58
59
60
TIA/EIA/IS-771.7 Modifications 7-13 Terminating BCSM

PN-4287
1
T_Null
2
3
Entry Event:
4
– Disconnect and clearing of a previous call (DPs: T_Disconnect or T_Abandon) 5
6
– Default handling of the exception condition by SSF/CCF completed. 7
(Transition from T_Exception PIC). 8
9
Functions: 10
11
– Clear any resources allocated to the terminating MS. 12
13
14
Exit Event:
15
– An indication of incoming call is received from the originating half BCSM. 16
(DP: Termination_Attempt). 17
18
– The following exception exit event is applicable to this PIC: T_Abandon. 19
20
i) The T_Abandon occurs when an indication of call disconnection is received 21
from the originating half BCSM. If the call encounters T_Abandon during 22
PIC processing, the exception event is not visible because there is no 23
corresponding DP. 24
25
26
27
Authorize_Termination_Attempt 28
29
Entry Event: 30
31
– Indication of incoming call received from the originating half BCSM.
32
(DP: Termination_Attempt)
33
34
Functions: 35
36
– Authority to route the call to the terminating access (e.g., MS or trunk group) is 37
being verified, e.g., check business group restrictions, restricted incoming access 38
to line, or bearer capability compatibility. 39
40
Exit Event: 41
42
– Termination_Attempt_Authorized event. This event occurs when the MSC has 43
verified the authority to terminate the call to the terminating access. 44
(DP: Termination_Attempt_Authorized). 45
46
– The Termination Denied event occurs when the authority to route these call to 47
the terminating user is denied. (This causes a transition to the T_Exception 48
PIC). 49
50
– The T_Abandon event occurs when an indication of clearing is received from the
51
originating half BCSM. (DP: T_Abandon).
52
53
54
55
56
57
58
59
60
Terminating BCSM 7-14 TIA/EIA/IS-771.7 Modifications

PN-4287
1
2
Select_Facility
3
4
Entry Event:
5
– Termination_Attempt_Authorized event. This event occurs when the MSC has
6
verified the authority to terminate the call to the terminating access.
7
(DP: Termination_Attempt_Authorized).
8
9 – An SS7 failure occurs causing a re-attempt. The SS7 failure in the Present_Call
10 PIC can be caused by a timer expiry upon sending the first Circuit Reservation
11 Message (CRM) or a continuity check failure.
12
13
Functions:
14
15 – A particular network resource is being selected. It is possible that all resources
16 in the group could be busy or unavailable. A single resource is considered a
17 group of one.
18
19 – For MS termination, the terminating half BCSM sends an indication to the
20 RACF to select facilities (e.g., page the MS, MS page response, trunk to cell,
21 radio channel within cell) for the call. The MS is assigned to the radio channel.1
22
23
– The busy/idle status of the terminating access is determined.
24
i) For termination to an MS, the MS is treated as user busy if it is already
25
involved in an existing call and cannot receive another call (e.g., call
26
waiting is not active).
27
28 ii) For termination to an MS, the MS is treated as network busy if no radio
29 channels are available or a routing failure occurs while attempting to
30 complete the call.
31
32 iii) For termination to an MS, the MS is treated as unavailable if it is not
33 available for call termination, an indication that the MS does not respond to
34 a page is received from the RACF2, or an indication of a failure to assign
35 the MS to a radio channel is received from the RACF.
36
37
iv) For calls routed out of this SSF/CCF, network-determined user busy is the
38
detection of terminating party busy.
39
v) For calls routed out of this SSF/CCF, network busy is when all trunks
40
within the selected trunk group are busy.
4
42 For call arrival with TLDN, if the MS status is busy (user or network) or
43 unavailable and the subscriber profile indicates call redirection on Busy, No Page
44 Response, No Answer or Routing Failure, a RedirectionRequest INVOKE3 is
45 sent to the Originating MSC with the RedirectionReason parameter set to
46 indicate the reason for redirection. The response determines the exit event.
47
48
49
50
51
52
1 If the MS is already assigned to a radio channel, only the selection of a trunk to the serving
53
54
cell may be required.
55 2The MS is treated as unavailable if it fails authentication when it responds to the page.
56
3The REDREQ will not be sent if office provisioning indicates that call redirection will be done
57
by the Serving MSC.
58
59
60

PN-4287
Exit Event: 1
2
– Terminating access is not busy, available terminating resources available and
3
facilities selected. (DP: Facility_Selected_and_Available).
4
– For call arrival with TLDN, the MS status is busy or unavailable, and the 5
response to the RedirectionRequest INVOKE indicates success. 6
(DP: T_Abandon). 7
8
– A T_Busy event occurs when the terminating access is busy or unavailable (as 9
defined above) and there is no call redirection (i.e., local termination, TLDN call 10
arrival with call redirection not applicable, TLDN call arrival with response to 11
RedirectionRequest INVOKE indicating failure). (DP: T_Busy). 12
13
After detecting T_Busy, if WIN service logic is not needed on the call and no
14
switch-based features apply, an indication of the T_Busy event describing the
15
type of busy (e.g., user or network) is passed to the originating half BCSM
16
(Send_Call PIC). If a terminating feature acts on the T_Busy event and changes
17
the event [e.g., as in the Call Waiting feature], the event is not passed to the
18
originating half BCSM.
19
– The T_Abandon event occurs when an indication of clearing is received from the 20
originating half BCSM. (DP: T_Abandon). 21

22
23
24
Present_Call
25
26
Entry Event:
27
– Available terminating resource identified and facilities selected. 28
(DP: Facility_Selected_and_Available). 29
30
31
Functions: 32
33
– Terminating resource informed of incoming call (e.g., indication sent to RCF
34
about the call).
35
36
Exit Event: 37
38
– Terminating party is being alerted (e.g., indication from RCF that ringing is
39
being applied, ringing being applied, ISDN-UP ACM message).
40
(DP: Call_Accepted).
41
– Call is accepted and answered by terminating party (e.g., indication from RCF of 42
call answer by MS, terminating party goes off hook, ISDN-UP answer message 43
received). (DP: T_Answer). 44

45
– For call routed out of this SSF/CCF to an MS, RedirectionRequest INVOKE 46
received with the RedirectionReason parameter indicating Busy, No Page 47
Response, Unavailable or Unroutable. (DP: T_Busy). 48
49
After detecting T_Busy, if WIN service logic is not needed on the call, an 50
indication of the T_Busy event is passed to the originating half BCSM 51
(Send_Call PIC). If a terminating feature acts on the T_Busy event and changes 52
the event [e.g., as in the Call Forwarding feature], the event is not passed to the 53
originating half BCSM. 54
55
– For call routed out of this SSF/CCF to an MS, RedirectionRequest INVOKE
56
message received with the RedirectionReason parameter indicating No Answer or
57
Call Refused. (DP: T_No_Answer).
58
59
60

PN-4287
1
2
After detecting T_No_Answer, if WIN service logic is not needed on the call, an
3
indication of the T_No_Answer event is passed to the originating half BCSM
4
(Send_Call PIC). If a terminating feature acts on the T_No_Answer event and
5
changes the event [e.g., as in the Call Forwarding feature], the event is not
6
passed to the originating half BCSM.
7
– A timer expiry upon sending the first Circuit Reservation Message (CRM) or a
8
continuity check failure. (SS7 failure). This event causes call processing to
9
move to the Select_Facility PIC.
10
11 – Presentation Failure: For call routed out of this SSF/CCF, the call cannot be
12 presented, (e.g., ISDN user determined busy, ISDN-UP release message with
13 busy cause). This event causes the terminating half BCSM to move to the
14 T_Exception PIC and an indication sent to the originating half BCSM
15 (Send_Call PIC).
16
17 – An indication of originating party abandon is received from originating half
18 BCSM. (DP: T_Abandon).
19
20
21 T_Alerting
22
23 Entry Event:
24
25
– Terminating party is being alerted of incoming call (DP: Call_Accepted).
26
27 Functions:
28
29 – An indication is sent to the originating half BCSM that the terminating party is
30 being alerted. Continued processing of call setup (e.g., ringing, audible ring
31 indication) is taking place. Waiting for the call to be answered by the
32 terminating party.
33
34
– For call arrival with TLDN, if the MS does not answer the alert and the
35
subscriber profile indicates call redirection on a “no answer” condition 1 , a
36
RedirectionRequest INVOKE is sent to the Originating MSC with the
37
RedirectionReason parameter indicating No Answer or Call Refused, as
38
appropriate. The response determines the exit event.
39
40 Exit Event:
4
42 – Call is accepted and answered by terminating party (e.g., indication from RCF of
43 call answer by MS, terminating party goes off hook, ISDN-UP answer message
44 received). (DP: T_Answer).
45
– For call arrival with TLDN, the MS does not answer the alert and the response
46
to the RedirectionRequest INVOKE indicates success. (DP: T_Exception).
47
48 – Terminating party does not answer before the MSC-based ringing timer expires.
49 For call arrival with TLDN, the MS does not answer the alert and the response
50 to the RedirectionRequest INVOKE indicates failure. For MS termination, loss
51 of radio contact with MS. For call routed out of this SSF/CCF to an MS,
52 RedirectionRequest INVOKE received with the RedirectionReason parameter
53 indicating No Answer or Call Refused. (DP: T_No_Answer).
54
55
56
1The REDREQ will not be sent if office provisioning indicates that call redirection will be done
57
by the Serving MSC.
58
59
60

PN-4287
After detecting T_No_Answer, if WIN service logic is not needed on the call, an 1
indication of the T_No_Answer event is passed to the originating half BCSM 2
(Send_Call PIC). If a terminating feature acts on the T_No_Answer event and 3
changes the event [e.g., as in the Call Forwarding feature], the event is not 4
passed to the originating half BCSM. 5
6
– Call_rejected exception event may happen when a user rejects a call while being
7
alerted. This event causes the terminating half BCSM to move to the
8
T_Exception PIC and an indication sent to the originating half BCSM
9
(Send_Call PIC).
10
– Indication of originating party abandon received from the originating half 11
BCSM. (DP T_Abandon) 12
13
14
T_Active 15
16
Entry Event: 17
18
– Call is accepted and answered by terminating party. (DP: T_Answer). 19
20
21
Functions:
22
– An indication is sent to the origination half BCSM that the terminating party 23
has accepted and answered the call. Connection established between originating 24
and terminating party. Call supervision is being provided. 25

26
27
Exit Event: 28
29
30
terminating MS. (DP: T_Mid_Call).
31
– A suspend disconnect indication is received from the terminating party. 32
(DP: T_Suspend). 33
34
– A disconnect indication is received from the terminating party. 35
(DP: T_Disconnect). 36
37
– A disconnect indication is received from the originating party via the originating 38
half BCSM. (DP: T_Disconnect). 39
40
– A connection failure occurs or loss of radio contact with MS. This event causes
41
the terminating half BCSM to move to the T_Exception PIC and an indication
42
sent to the originating half BCSM.
43
44
45
T_Suspended 46
47
Entry Event: 48
49
– A suspend disconnect indication is received from the terminating party.
50
(DP: T_Suspend).
51
52
Functions: 53
54
– The physical resources associated with the call remain connected. 55
56
– A suspend indication is sent to the originating half BCSM.
57
58
59
60

PN-4287
1
2
– A disconnect indication (e.g., Q.931 disconnect message, SS7 release message)
3
is received from the terminating party, this PIC is immediately exited to the
4
T_Disconnect DP without any action.
5
– For an SS7 supported trunk, when the receiving network initiates a suspend
6
message, a timer is started and the call processing waits for re-answer request
7
from the terminating party. If re-answer request (e.g., off-hook, SS7 resume
8
message) is received from the terminating party before the timer expires, the
9
originating and terminating parties are reconnected.
10
11 Note: Both a Call Resume timer and a Call Retention timer may exist in this
12 PIC. WIN implementations may use a single timer for both conditions.
13
14
Exit Event:
15
16 – The terminating party re-answers or a resume message is received before the
17 timer expires. The T_BCSM returns to the T_Active PIC. (DP: T_Re-answer).
18
19 Note: This transition to the T_Active PIC is not applicable for wireless calls.
20
21
– The expiration of the timer waiting for re-answer from the terminating party.
22
(DP: T_Disconnect).
23
– A disconnection indication is received from the terminating party
24
(DP: T_Disconnect).
25
26 – A disconnection indication is received from the originating party via the
27 originating half BCSM. (DP: T_Disconnect).
28
29 – An exception event is encountered. This event causes a transition to the
30 T_Exception PIC.
31
32
33 T_Exception
34
35 Entry Event:
36
37 – An exception event is encountered as described above for each PIC.
38
39 Functions:
40
4 – An indication of the exception condition is sent to the originating half BCSM.
42 Default handling of the exception condition is being provided. This includes
43 general actions necessary to ensure no resources remain inappropriately allocated,
44 such as:
45
46
i) If any relationships exist between the SSF and SCF(s), send an error
47
information flow to the SCF(s) closing the relationships and indicating that
48
any outstanding call handling instructions will not run to completion.
49
ii) The SSF/CCF should make use of vendor-specific procedures to ensure
50
release of resources so that radio, trunk, and other resources are made
51
available for new calls.
52
53
54
55 Exit Event:
56
57
– Default handling of the exception condition by SSF/CCF completed.
58
(Transition to O_Null PIC)
59
60

PN-4287
1
5.2.2.3 BCSM Transitions
2
3
The complete set of transitions for the Originating BCSM are shown in Table 1 below. 4
The shaded DPs do not have triggers defined in this standard. The Nature of BCSM 5
Transition indicates whether the transition is Basic or Extended. 6

7
• Basic: call processing resumes in sequence (i.e., continue) 8
9
• Extended: the next step in call processing is specified by SCF 10
11
Table 1 Originating BCSM Transitions 12

13
From To Nature of BCSM 14
Transition
15
Origination_Attempt DP Authorize_Orig._Attempt PIC 16
17
Orig._Attempt_Authorized DP Collect_Information PIC Basic
18
Collected_Information DP Collect_Information PIC Extended 19
Analyze_Information PIC Basic 20

21
Select_Route PIC Extended
22
Analyzed_Information DP Collect_Information PIC Extended 23
24
Analyze_Information PIC Extended
25
Select_Route PIC Basic 26
O_Term_Seized DP O_Alerting PIC 27
28
Route_Select_Failure DP O_Exception
29
O_Called_Party_Busy DP O_Exception 30
O_No_Answer DP O_Exception 31
32
O_Answer DP O_Active PIC Basic
33
O_Suspend DP O_Suspended PIC 34
35
O_Re-Answer DP O_Active PIC
36
O_Mid_Call DP Send_Call PIC 37
O_Mid_Call DP O_Alerting PIC 38

39
O_Mid_Call DP O_Active PIC
40
O_Mid_Call DP O_Suspended PIC 41
42
O_Disconnect DP O_Null PIC Basic
43
O_Abandon DP O_Null PIC 44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
BCSM Transitions 7-20 TIA/EIA/IS-771.7 Modifications

PN-4287
1
2
Table 1 Originating BCSM Transitions (concluded)
3 From To Nature of BCSM
4 Transition
5
O_Null PIC Origination_Attempt DP
6
7 Auth._Orig._Attempt PIC Orig._Attempt_Auth. DP Basic
8
O_Abandon DP
9
10
O_Exception Basic
11 Collect_Information PIC Collected_Information DP Basic
12
O_Abandon DP
13
14 O_Exception Basic
15 Analyze_Information PIC Analyzed_Information DP Basic
16
O_Abandon DP
17
19 Select_Route PIC Analyze_Information PIC Basic
20
Authorize_Call_Setup PIC Basic
21
22 Route_Select_Failure DP
23 O_Abandon DP
24
Authorize_Call_Setup PIC Send_Call PIC Basic
25
26 O_Abandon DP
27
O_Exception Basic
28
29
Send_Call PIC O_Term_Seized DP
30 O_Mid_Call DP
31 O_Called_Party_Busy DP
32
O_Answer DP Basic
33
34 O_No_Answer DP
35
Select_Route PIC Basic
36
37 O_Abandon DP
39
O_Alerting PIC Select_Route PIC Basic
40
4 O_Mid_Call DP
42 O_Answer DP Basic
43
44
O_No_Answer DP
45 O_Called_Party_Busy DP
46 O_Abandon DP
47
O_Active PIC O_Mid_Call DP
48
49 O_Disconnect DP Basic
50
O_Suspend DP
51
53 O_Suspended PIC O_Re-Answer DP
54
O_Mid_Call DP
55
56 O_Disconnect DP Basic
58
O_Exception O_Null PIC Basic
59
60
TIA/EIA/IS-771.7 Modifications 7-21 BCSM Transitions

PN-4287
The complete set of transitions for the Terminating BCSM are shown in Table 2 below. 1
The shaded DPs do not have triggers defined in this standard. 2
3
Table 2 Terminating BCSM Transitions
4
From To Nature of BCSM 5
Transition 6
7
Termination_Attempt DP Auth._Term._Attempt PIC
8
Term._Attempt_Auth. DP Select_Facility PIC 9
10
Facility_Sel._And_Avail. DP Present_Call PIC Basic
11
Call_Accepted DP T_Alerting PIC 12
13
T_Busy DP Select_Facility PIC Extended
14
Present_Call PIC Extended 15
16
T_Exception Basic
17
T_No_Answer DP Select_Facility PIC Extended 18

19
T_Exception Basic 20
T_Answer DP T_Active PIC Basic 21

22
T_Suspend DP T_Suspended PIC 23
24
T_Re-Answer DP T_Active PIC
25
T_Mid_Call DP T_Active PIC 26
27
T_Disconnect DP T_Null PIC Basic
28
T_Abandon DP T_Null PIC 29

30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
1
2
Table 2 Terminating BCSM Transitions (concluded)
3 From To Nature of BCSM
4 Transition
5
T_Null PIC Termination_Attempt DP
6
7 Auth._Term._Attempt PIC T_Exception Basic
8 T_Abandon DP
9
Term._Attempt_Auth. DP
10
11 Select_Facility PIC Facility_Selected_And_Avail. Basic
12 DP
13 T_Busy DP Basic
14
T_Abandon DP
15
16 Present_Call PIC Select_Facility PIC Basic
17 T_Abandon DP
18
T_Busy DP Basic
19
20 T_No_Answer DP Basic
21
T_Exception Basic
22
23
Call_Accepted DP
24 T_Answer DP Basic
25
T_Alerting PIC T_Answer DP Basic
26
27 T_Abandon DP
28
T_Exception Basic
29
30
T_No_Answer DP Basic
31 T_Active PIC T_Exception Basic
32
T_Mid_Call DP
33
34 T_Disconnect DP Basic
35
T_Suspend DP
36
37
T_Suspended PIC T_Disconnect DP Basic
38 T_Re-Answer DP
39
T_Exception Basic
40
4 T_Exception T_Null PIC Basic
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
5.2.3 BCSM Detection Points 1

2
3
4
5
6
5.2.3.4 Trigger Types and Trigger Precedence 7
(TIA/EIA/IS-771, page 7-52) 8
9
Trigger types denote classes of events of interest. They are used to establish trigger 10
precedence rules at TDPs and to indicate to the SCF the service logic to be invoked. A 11
non-exhaustive list of trigger types are defined. Definition of future trigger types is for 12
further study. 13
14
The trigger types are described in terms of: 15
16
1. TDP - the DP at which the trigger can be detected. 17
18
2. DP Criteria - the conditions needed to trigger. Criteria may be conditional -
19
effective only when the trigger is active and the criteria is satisfied, or
20
unconditional - always effective when the trigger is active.
21
3. Category - office, group, or subscribed (subscriber based). 22

23
4. Interface - type of interface to which it can be assigned (e.g., inter-office trunk, 24
mobile origination, mobile termination). 25
26
5. Trigger Type - the value that identifies the type of criteria that caused the 27
SSF/CCF to detect a valid trigger condition at this TDP. 28
29
6. Fault Handling - defines fault handling procedures for the case when the SCF
30
does not respond to the SSF/CCF message. Details on possibilities for fault
31
handling are for further study.
32
7. TIA/EIA-41 operation - identifies the TIA/EIA-41 operation used to query WIN 33
service logic (e.g., SCP). 34

35
8. Arming Mechanism - identifies the possible mechanisms by which the trigger is 36
armed. Subscribed triggers may be armed by parameters received by the MSC 37
(e.g., in a regnot, qualreq or QUALDIR). Triggers may be dynamically 38
armed on a per call basis by parameters within call related operations (e.g., 39
orreq, featreq, locreq, ROUTREQ) Office based triggers are armed in the 40
provisioning process by separate service management systems that are beyond 41
the scope of this standard. 42
43
44
Since multiple triggers may be armed as TDP-Rs at a DP, precedence rules for trigger
45
processing are specified as:
46
Since the same DP may be armed multiple times as a TDP-R, precedence rules for trigger 47
processing are specified as: 48

49
1. subscribed triggers have precedence over group triggers 50
51
2. group triggers have precedence over office triggers 52
53
3. more specific triggers take precedence over less specific triggers (e.g., a 6-digit
54
trigger takes precedence over a 3-digit trigger)
55
56
57
58
59
60

PN-4287
1
2
The sequence for processing WIN triggers should be as detailed in Tables 4 and 5 below.
3
Table 4 WIN Trigger Precedence for Originating BCSM
4
5 Trigger Detection Point Trigger Type Reference
6
Origination_Attempt_Authorized Locally_Allowed_Specific_Digit_String 5.2.3.4.33
7
8 Origination_Attempt_Authorized 5.2.3.4.25
9
10 Collected_Information All_Calls 5.2.3.4.1
11
Double_Introducing_Star 5.2.3.4.2
12
13 Single_Introducing_Star 5.2.3.4.3
14
15 Home_System_Feature_Code 5.2.3.4.4
16
Double_Introducing_Pound 5.2.3.4.5
17
18 Single_Introducing_Pound 5.2.3.4.6
19
20 Revertive_Call 5.2.3.4.7
21
K-Digit 5.2.3.4.8
22
23 Analyzed_Information Local_Call 5.2.3.4.9
24
25
Intra_LATA_Toll_Call 5.2.3.4.10
26
Inter_LATA_Toll_Call 5.2.3.4.11
27
28 World_Zone_Call 5.2.3.4.12
29
International_Call 5.2.3.4.13
30
31 Unrecognized_Number 5.2.3.4.14
32
33 Prior_Agreement 5.2.3.4.15
34
Specific_Called_Party_Digit_String 5.2.3.4.16
35
36 Calling_Routing_Address_Available 5.2.3.4.27
37
38 Mobile_Termination 5.2.3.4.17
39
Initial_Termination 5.2.3.4.26
40
4 Advanced_Termination 5.2.3.4.18
42
43
Location 5.2.3.4.19
44
Called_Routing_Address_Available 5.2.3.4.28
45
46 O_Answer O_Answer 5.2.3.4.29
47
O_Disconnect O_Disconnect 5.2.3.4.30
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
Table 5 WIN Trigger Precedence for Terminating BCSM 1

Trigger Detection Point Trigger Type Reference 2
3
Facility_Selected_and_Available Terminating_Resource_Available 5.2.3.4.20 4
5
T_Busy T_Busy 5.2.3.4.21
6
T_No_Page_Response 5.2.3.4.22 7
8
T_Unroutable 5.2.3.4.23
9
T_No_Answer T_No_Answer 5.2.3.4.24 10

11
T_Answer T_Answer 5.2.3.4.31 12
13
T_Disconnect T_Disconnect 5.2.3.4.32
14
15
16
Locally allowed numbers escape the subscribed triggers at the Collected_Information and 17
Analyzed_Information Detection Points. However these subscribed triggers at the 18
Collected_Information and Analyzed_Information Detection Points do take precedence 19
over “hot line.” 20
21
22
5.2.3.4.1 All_Calls 23
24
The All_Calls trigger is detected for all MS originated calls. 25
26
1. TDP - Collected_Information 27
28
2. DP Criteria - UnconditionalTrigger assigned (unconditional)
29
3. Category - Subscribed 30
31
4. Interface - mobile origination 32
33
5. Trigger Type - All_Calls 34
35
6. Fault Handling - Final treatment (other treatments such as Default Routing or
36
Continue Call Processing are for further study).
37
7. TIA/EIA-41 operation - OriginationRequest INVOKE 38
39
8. Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or 40
dynamically for a single call (e.g., orreq) 41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
1
2
5.2.3.4.2 Double_Introducing_Star
3
4
The Double_Introducing_Star trigger is detected for MS originated calls having ‘**’ as the
5
first two dialed digits.
6
1. TDP - Collected_Information
7
8 2. DP Criteria - Conditional
9
10 3. Category - Subscribed
11
4. Interface - mobile origination
12
13 5. Trigger Type - Double_Introducing_Star
14
15 6. Fault Handling - Final treatment (other treatments such as Default Routing or
16 Continue Call Processing are for further study).
17
18
7. TIA/EIA-41 operation - OriginationRequest INVOKE
19
8. Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot)
20
or dynamically for a single call (e.g., orreq)
21
22
23
24
5.2.3.4.3 Single_Introducing_Star
25
26
The Single_Introducing_Star trigger is detected for MS originated calls with ‘*’ as the
27
first dialed digit but not as the second dialed digit.
28
29
31
33
34
35
5. Trigger Type - Single_Introducing_Star
36
39
40 7. TIA/EIA-41 operation - OriginationRequest INVOKE
4
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
5.2.3.4.4 Home_System_Feature_Code 1
2
The Home_System_Feature_Code trigger is detected for MS originated calls with ‘*’ as 3
the first dialed digit but not as the second dialed digit. 4
5
6
2. DP Criteria - Conditional 7
8
10
11
5. Trigger Type - Home_System_Feature_Code 12

13
6. Fault Handling - Final treatment (other treatments such as Default Routing or 14
Continue Call Processing are for further study). 15
16
7. TIA/EIA-41 operation - FeatureRequest INVOKE 17
18
8. Arming Mechanism - (Note)
19
Note: This trigger type is armed as a TDP-R at the Serving MSC when the 20
Single_Introducing_Star trigger type is not armed. The Home_System_Feature_Code 21
trigger type is mutually exclusive with the Single_Introducing_Star trigger type. When 22
the Home_System_Feature_Code trigger type is armed, the address associated with this 23
trigger type is the address of the HLR for the served subscriber. 24
25
26
5.2.3.4.5 Double_Introducing_Pound 27
28
The Double_Introducing_Pound trigger is detected for MS originated calls having ‘##’ as 29
the first two dialed digits. 30
31
32
34
36
38
5. Trigger Type - Double_Introducing_Pound
39
42
44
45
or dynamically for a single call (e.g., orreq) 46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
1
2
5.2.3.4.6 Single_Introducing_Pound
3
4
The Single_Introducing_Pound trigger is detected for MS originated calls having ‘#’ as
5
the first dialed digit but not as the second dialed digit.
6
7
9
11
12
13 5. Trigger Type - Single_Introducing_Pound
14
17
18
19
20
21
22
23
24
5.2.3.4.7 Revertive_Call
25
26
The Revertive_Call trigger is detected when the dialed digits are equal to the MS’s mobile
27
directory number (or MIN if the MDN is not available).
28
29
31
33
34
35
5. Trigger Type - Revertive_Call
36
39
4
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
5.2.3.4.8 K_Digit 1 1
2
Sixteen distinct and independent K_Digit triggers are defined for values of K from 0 to 15. 3
For values of K from 0 to 14, the associated K_Digit trigger is detected if the MS dialed 4
digits are precisely K digits in length. The 15-Digit K_Digit trigger is detected if the MS 5
dialed digits are at least 15 digits in length. 6
7
8
10
12
13
5. Trigger Type - K_Digit 14

15
18
20
21
22
23
24
5.2.3.4.9 Local_Call 25
26
The Local_Call trigger is detected when the digits dialed are recognized as a local call 27
according to the dialing plan in use. 28
29
1. TDP - Analyzed_Information
30
32
34
36
5. Trigger Type - Local_Call
37
40
42
43
45
46
47
48
49
50
51
52
53
54
55
1All digits (e.g., *,#) are counted in determining whether the K_Digit trigger criterion is met. 56
57
58
59
60

PN-4287
1
2
5.2.3.4.10 Intra_LATA_Toll_Call
3
4
The Intra_LATA_Toll_Call trigger is detected when the digits dialed are recognized as an
5
intra-LATA toll call according to the dialing plan in use.
6
7
9
11
12
13 5. Trigger Type - Intra_LATA_Toll_Call
14
17
18
19
20
21
22
23
24
5.2.3.4.11 Inter_LATA_Toll_Call
25
26
The Inter_LATA_Toll_Call trigger is detected when the digits dialed are recognized as an
27
inter-LATA toll call according to the dialing plan in use.
28
29
31
33
34
35
5. Trigger Type - Inter_LATA_Toll_Call
36
39
4
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
5.2.3.4.12 World_Zone_Call 1
2
The World_Zone_Call trigger is detected when the digits dialed are recognized as a call to 3
a World Zone different from the World Zone in which the call has originated (as defined in 4
ITU-T Rec. E.164) according to the dialing plan in use. 5
6
7
9
11
12
5. Trigger Type - World_Zone_Call 13

14
17
19
20
21
22
23
5.2.3.4.13 International_Call 24
25
The International_Call trigger is detected when the digits dialed are recognized as an 26
international call according to the dialing plan in use. 27
28
29
31
33
35
5. Trigger Type - International_Call
36
39
41
42
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
1
2
5.2.3.4.14 Unrecognized_Number
3
4
The Unrecognized_Number trigger is detected when the digits dialed are not recognized as
5
a valid call type.
6
7
9
11
12
13 5. Trigger Type - Unrecognized_Number
14
17
18
19
20
21
22
23
24
5.2.3.4.15 Prior_Agreement
25
26
The Prior_Agreement trigger is detected when the digits dialed match the criteria of a prior
27
agreement.
28
29
31
33
34
35
5. Trigger Type - Prior_Agreement
36
39
4
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
5.2.3.4.16 Specific_Called_Party_Digit_String 1 1
2
The Specific_Called_Party_Digit_String trigger is detected when the appropriate sequence 3
of digits is dialed according to the dialing plan in use. For example, a 3, 6, or 10 digit 4
sequence of digits can be provisioned as the trigger. Trigger provisioning specifies 5
whether the MSC performs some manipulation of the dialed digits (e.g., digit insertion, 6
deletion, or translation to public numbers), or queries the SCF with the digits as dialed. 7
The numbering plan in force should ensure that emergency service numbers are distinct 8
from provisionable specific digit strings. 9
10
11
13
2. DP Criteria -Trigger assigned (conditional). Specific called party number string. 14
15
3. Category - Office-based
16
4. Interface - mobile origination or interoffice trunk 17

18
5. Trigger Type - Specific_Called_Party_Digit_String 19
20
23
7. TIA/EIA-41 operation - AnalyzedInformation INVOKE
24
8. Arming Mechanism - armed as a TDP-R via office provisioning 25

26
27
28
5.2.3.4.17 Mobile_Termination
29
30
The Mobile_Termination trigger is detected when the dialed digits are called party number
31
is determined to be a mobile directory number.
32
1. TDP - Analyzed_Information 33
34
36
2. DP Criteria -Trigger assigned (conditional), called party number identified as a mobile 37
directory number.
38
39
40
42
5. Trigger Type - Mobile_Termination 43
44
45
46
7. TIA/EIA-41 operation - LocationRequest INVOKE with the TRIGTYPE 47
parameter set to indicate the Mobile_Termination trigger was encountered 48

49
8. Arming Mechanism - armed as a TDP-R via office provisioning 50
51
52
53
54
55
1Known as Specific_Digit_String in ITU-T Q.1224. 56

57
58
59
60

PN-4287
1
2
5.2.3.4.18 Advanced_Termination
3
4
The Advanced_Termination trigger is detected when it has been armed by the
5
TriggerAddressList parameter received in the locreq response to a LOCREQ sent upon
6
detection of the Mobile_Termination trigger.
7
8
9 2. DP Criteria - Unconditional
10
11 2. DP Criteria -Trigger assigned (unconditional)
12
3. Category - Subscribed
13
14 4. Interface - mobile origination or interoffice trunk
15
16 5. Trigger Type - Advanced_Termination
17
18
19
20
21
22 8. Arming Mechanism - armed as a TDP-R via TriggerAddressList parameter in the
23 locreq
24
25
26
5.2.3.4.19 Location
27
28
The Location trigger is armed by the TriggerAddressList parameter received in the
29
locreq response to a LOCREQ sent upon detection of the Mobile_Termination trigger.
30
The Location trigger is detected when the dialed digits are called party number is determined
31
to be a mobile directory number and no routing information1 is available.
32
33 1. TDP - Analyzed_Information
34
36
37
2. DP Criteria -Trigger assigned (conditional – called party is determined to be a mobile
directory number and no routing information is available)
38
39
40
42
43 5. Trigger Type - Location
44
45
46
47 7. TIA/EIA-41 operation - LocationRequest INVOKE with TRIGTYPE parameter
48 set to indicate the Location trigger was encountered2
49
50 8. Arming Mechanism - armed as a TDP-R via TriggerAddressList parameter in the
51 locreq
52
53
54
1 Routing information can specify Intersystem Termination, Local Termination or PSTN
55
56 Termination.
57
58
59
60

PN-4287
5.2.3.4.20 Terminating_Resource_Available 1
2
The Terminating_Resource_Available trigger is detected by the Serving MSC when the 3
MS has been paged and responded, and the alerting information is being prepared for 4
transmission to the MS. 5
6
1. TDP - Facility_Selected_and_Available
7
9
2. DP Criteria - Trigger assigned (conditional) 10
11
12
4. Interface - mobile termination 13

14
5. Trigger Type - Terminating_Resource_Available 15
16
19
7. TIA/EIA-41 operation - FacilitySelectedAndAvailable INVOKE
20
8. Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) 21
or dynamically for a single call (e.g., ROUTREQ) 22

23
24
25
5.2.3.4.21 T_Busy
26
27
The T_Busy trigger is detected when the terminating access is determined to be busy (i.e.,
28
network determined user-busy). This trigger may be detected either at the Serving MSC
29
when the calling party connection has been made and busy is detected, or at the
30
Originating MSC when, for instance, a busy indication is received in the LocationRequest
31
RETURN RESULT or RedirectionRequest INVOKE.
32
1. TDP - T_Busy 33
34
36
2. DP Criteria - Trigger assigned (conditional)
37
38
39
41
5. Trigger Type - T_Busy 42
43
6. Fault Handling - Continue call processing (other treatments such as Default
44
Routing or Final Treatment are for further study)
45
7. TIA/EIA-41 operation - TransferToNumberRequest INVOKE (trigger is armed by 46
mechanism other than the TriggerAddressList parameter), TBusy INVOKE 47
(trigger is armed by the TriggerAddressList parameter) 48

49
52
53
54
2The destination address for this query is the address of the HLR associated with the dialed MS 55
56
address digits.
57
58
59
60

PN-4287
1
2
5.2.3.4.22 T_No_Page_Response
3
4
The T_No_Page_Response trigger is detected when a called mobile station does not
5
respond to a page. This trigger may be detected either at the Serving MSC when the
6
mobile station does not respond to a page, or at the Originating MSC when, for instance,
7
a No page response indication is received in the LocationRequest RETURN RESULT or
8
RedirectionRequest INVOKE.
9
1. TDP - T_Busy
10
12
13 2. DP Criteria - Trigger assigned (conditional)
14
15
16 4. Interface - mobile termination
17
18 5. Trigger Type - T_No_Page_Response
19
20
21
22
7. TIA/EIA-41 operation - TransferToNumberRequest INVOKE (trigger is armed by
23
mechanism other than the TriggerAddressList parameter), TBusy INVOKE
24
(trigger is armed by the TriggerAddressList parameter)
25
26 8. Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot)
27 or dynamically for a single call (e.g., ROUTREQ)
28
29
30
5.2.3.4.23 T_Unroutable
31
32
The T_Unroutable trigger is detected when a routing failure occurs when attempting to
33
complete a call. This trigger may be detected either at the Serving MSC or at the
34
Originating MSC when, for instance, an Unroutable indication is received in the
35
RedirectionRequest INVOKE.
36
37 1. TDP - T_Busy
38
40
2. DP Criteria - Trigger assigned (conditional)
4
42
43
44 4. Interface - mobile termination
45
46 5. Trigger Type - T_Unroutable
47
48
49
50 7. TIA/EIA-41 operation - TransferToNumberRequest INVOKE (trigger is armed by
51 mechanism other than the TriggerAddressList parameter), TBusy INVOKE
52 (trigger is armed by the TriggerAddressList parameter)
53
54 8. Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot)
55 or dynamically for a single call (e.g., ROUTREQ)
56
57
58
59
60

PN-4287
5.2.3.4.24 T_No_Answer 1
2
The T_No_Answer trigger is detected when the no-answer timer associated with the 3
terminating access expires. This trigger may be detected at the Serving MSC when the 4
calling party connection has been made and the no answer timer expires, or at the 5
Originating MSC when, for instance, a no answer indication is received in the 6
RedirectionRequest INVOKE. 7
8
1. TDP - T_No_Answer
9
11
2. DP Criteria - Trigger assigned (conditional) 12
13
14

16
5. Trigger Type - T_No_Answer 17
18
6. Fault Handling - Continue call processing (other treatments such as Default 19
Routing or Final Treatment are for further study) 20
21
7. TIA/EIA-41 operation - TransferToNumberRequest INVOKE (trigger is armed by
22
mechanism other than the TriggerAddressList parameter), TNoAnswer INVOKE
23
(trigger is armed by the TriggerAddressList parameter)
24

27
28
29
5.2.3.4.25 Origination_Attempt_Authorized
30
31
The Origination_Attempt_Authorized trigger is detected when an MS origination
32
indication is received and authorization is completed. 33
34
1. TDP - Origination_Attempt_Authorized
35
2. DP Criteria - Unconditional 36
37
39
41
5. Trigger Type - Origination_Attempt_Authorized 42
43
44
46
47

49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
1
2
5.2.3.4.26 Initial_Termination
3
4
The Initial_Termination trigger is detected when it has been armed by the
5 TriggerAddressList parameter received in the locreq response to a LOCREQ sent upon
6 detection of the Mobile_Termination trigger.
7
8
9
2. DP Criteria - Unconditional
10
11
12
14
15 5. Trigger Type - Initial_Termination
16
19
20
21
8. Arming Mechanism - armed as a TDP-R via TriggerAddressList parameter in the
22
23
locreq
24
25
26 5.2.3.4.27 Calling_Routing_Address_Available
27
28 The Calling Routing_Address_Available trigger is detected when a routing address and call
29 type have been determined for an outgoing call.
30
32
33
34
35
36
37
38 5. Trigger Type - Calling_Routing_Address_Available
39
42
43 7. TIA/EIA-41 operation - AnalyzedInformation INVOKE
44
45
46 or dynamically for a single call (e.g., locreq)
47
48
49 5.2.3.4.28 Called_Routing_Address_Available
50
51 The Called_Routing_Address_Available trigger is detected when a routing address and call
52 type have been determined for an incoming call
53
55
56 2. DP Criteria - Unconditional
57
58
59
60

PN-4287

2
5. Trigger Type - Called_Routing_Address_Available
3
6 Fault Handling - Final treatment (other treatments such as Default Routing or 4

5
6
7. TIA/EIA Operation - AnalyzedInformation INVOKE 7

8
8. Arming Mechanism - armed as a TDP-R via TriggerAddressList parameter in the 9
locreq 10
11
12
13
5.2.3.4.29 O_Answer
14
15
The O_Answer trigger is detected when an answer indication is received via the
16
terminating BCSM.
17
18
1. TDP - O_Answer
19
21
23
25
5. Trigger Type - O_Answer 26
27
28
29
30
7. TIA/EIA-41 operation - O_Answer INVOKE
31
8. Arming Mechanism - armed as a TDP-N via subscriber profile (e.g., regnot) 32
or dynamically for a single call (e.g., locreq) 33

34
35
36
5.2.3.4.30 O_Disconnect
37
38
The O_Disconnect trigger is detected when either the call is cleared from the terminating
39
BCSM or the originating facility disconnects, or the MSC releases the call leg. 40
41
1. TDP - O_Disconnect
42
44
46
48
5. Trigger Type - O_Disconnect 49
50
51
Routing or Final Treatment are for further study) 52
53
7. TIA/EIA-41 operation - O_Disconnect INVOKE
54

56
or dynamically for a single call (e.g., locreq)
57
58
59
60

PN-4287
1
2
5.2.3.4.31 T_Answer
3
4
The T_Answer trigger is detected when an answer indication is received from the
5 terminating facility.
6
7
1. TDP - T_Answer
8
9
11
12 4. Interface - mobile termination or interoffice trunk
13
14 5. Trigger Type - T_Answer
15
16
17 Routing or Final Treatment are for further study)
18
19
7. TIA/EIA-41 operation - T_Answer INVOKE
20
8. Arming Mechanism - armed as a TDP-N via subscriber profile (e.g., regnot)
21
22
23
24
25 5.2.3.4.32 T_Disconnect
26
27 The T_Disconnect trigger is detected when either the call is cleared from the originating
28 BCSM or the terminating facility disconnects, or the MSC releases the call leg.
29
30 1. TDP - T_Disconnect
31
32
33
34
35 4. Interface - mobile termination or interoffice trunk
36
37 5. Trigger Type - T_Disconnect
38
39 6. Fault Handling - Continue call processing (other treatments such as Default
40 Routing or Final Treatment are for further study)
4
42 7. TIA/EIA-41 operation - T_Disconnect INVOKE
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
5.2.3.4.33 Locally_Allowed_Specific_Digit_String 1
2
The Locally_Allowed_Specific_Digit_String trigger is detected when the appropriate 3
sequence of digits is dialed according to the dialing plan in use, and the dialed digit string 4
is a locally allowed number. 5
6
1. TDP - Origination_Attempt_Authorized 7
8
2. DP Criteria - Conditional
9
10
11

13
5. Trigger Type - Locally_Allowed_Specific_Digit_String 14
15
18
20
8. Arming Mechanism - armed as a TDP-R via office provisioning
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

PN-4287
1
2
3
4
Annex D (informative) Notes on Trigger Concepts
5
6
and Usage
7
8 This annex is informative and is not considered part of this Interim Standard.
9
10
11
Dynamic Trigger Arming Mechanism
12
13
14
A subscriber’s trigger profile is stored in the HLR. This profile is considered to be
15
“static” because it changes “slowly” if at all. The subscriber’s trigger profile remains the
16
same unless the subscription options change so that a new trigger is required or an
17
existing trigger is no longer required. That is, it remains the same unless the subscriber adds
18
or deletes a triggered service from the profile, or turns on or off one of the services that are
19
subscribed to. It is this “static” profile that is dynamically geographically placed as the
20
subscriber roams and is served by different MSCs.
21
22 Subscribed triggers may be dynamically armed by service logic for the call leg. When
23
dynamic trigger arming is used, any previously armed triggers are disarmed before the new
24
triggers are armed. These new triggers apply only for the remainder of the call in progress
25
or until a subsequent dynamic trigger arming event occurs. A subscriber’s trigger profile
26
may be modified for a given call instance without affecting the “static” profile. These
27
modifications to the profile do not survive after the current call. On release of the call, all such
28
modifications disappear. This is called “dynamic” trigger arming. This may be done in two
29
ways. In pre-WIN systems, it is done using the OriginationTriggers ORIGTRIG and
30
TerminationTriggers TERMTRIG parameters. In WIN-capable systems, it may also be
31
32
done using the TriggerAddressList TRIGADDRLIST parameter.
33
The TriggerAddressList parameter may also be used to dynamically arm triggers when the
34
subscriber profile is not available or is not applicable. For example, the
35
36
Initial_Termination and Advanced_Termination triggers are not included in the subscriber
37
profile; they can only be armed dynamically via the TriggerAddressList parameter.
38 Triggers armed on the Originating MSC for a roaming subscriber when the Serving
39 System is not WIN-capable can only be armed dynamically by the TriggerAddressList
40 parameter. Profile triggers are not applicable to forwarded calls; WIN triggers for
4 forwarded call legs can be armed by the TriggerAddressList.
42
43 Subscribed WIN Triggers may be explicitly disarmed by service logic via the
44 TriggerAddressList parameter. Upon receipt of this parameter, all previously armed
45 subscribed WIN triggers for that call leg will be disarmed for the remainder of the call in
46 progress. Use of this parameter does not affect the subscriber's profile. The subscriber's
47 profile triggers are used for the next new call origination or termination.
48
49
50
51
52
53
54
55
56
57
58
59
60
TIA/EIA/IS-771.7 Modifications 7-43 Annex D: Notes on Trigger Concepts and Usage

IS826 NS0018Re

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

IS826 NS0018Re

Загружено:

Авторское право:

Доступные форматы

3GPP2 N.

TIA/EIA-41-D Pre-Paid Charging

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

Association; June 1996 10

1-iii Revision History

Revision History 1-iv

• cross out: deletions 8

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

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

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

scenarios in this standard. 11

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

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

PPC Feature Description 2-i Contents

List of Tables 2-ii PPC Feature Description

PPC Feature Description 2-iii Revision History

Revision History 2-iv PPC Feature Description

PPC Feature Description 2-1 Definitions and Concepts

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

of voice telecommunications services may be de-authorized. 13

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

35 FC + # + termination address + SEND , or

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

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

• The calls continue without interruption. 43

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

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

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

shall be presented to the subscriber. 58

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

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

Call Forwarding—Default (CFD) 26

PPC is invoked before CFD. 28

Calling Name Presentation (CNAP) 52

PPC is invoked before CNAP. 54

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

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

Preferred Language (PL) 22

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

Subscriber Confidentiality (SC) 54

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

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

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

List of Figures 3-ii TIA/EIA-41.1-D Modifications

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

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

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

Originating System Serving System 12

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

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

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

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

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

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

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

• Q+P Query with Permission 3

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