You are on page 1of 48

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

WIRELESS INTELLIGENT NETWORK CAPABILITIES FOR PRE-PAID CHARGING CHAPTER 7 MODIFICATIONS TO TIA/EIA/IS-771.7 DISTRIBUTED FUNCTIONAL PLANE

CONTENTS
LIST OF FIGURES .................................................................................................................. ii LIST OF TABLES................................................................................................................... iii REVISION HISTORY.............................................................................................................. iv 5 SSF/CCF CALL AND SERVICE LOGIC MODEL............................................................ 1 5.1 General............................................................................................................ 1 5.1.3 Service Interactions Manager (SIM) - SCF................................................. 1 5.2 SSF/CCF Model............................................................................................... 3 5.2.2.1 Originating BCSM.............................................................. 3 5.2.2.2 Terminating BCSM ............................................................. 6 5.2.2.3 BCSM Transitions .............................................................. 7 5.2.3 BCSM Detection Points ....................................................................... 11 5.2.3.4 Trigger Types and Trigger Precedence.................................... 11

Annex D (informative) Notes on Trigger Concepts and Usage ......................................................... 30 Dynamic Trigger Arming Mechanism ............................................................................. 30

PPC TIA/EIA/IS-771.7 Modifications

7-i

Contents

TIA/EIA/IS-826

LIST OF FIGURES
Figure 5 Figure 8 Figure 9 Service Interactions Manager at the SCF.............................................. 1 Originating Call Model .................................................................... 4 Terminating Call Model ................................................................... 6

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

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

LIST OF TABLES
Table 1 Table 2 Table 4 Table 5 Originating BCSM Transitions .......................................................... 7 Terminating BCSM Transitions......................................................... 9 WIN Trigger Precedence for Originating BCSM .................................. 12 WIN Trigger Precedence for Terminating BCSM ................................. 13

PPC TIA/EIA/IS-771.7 Modifications

7-iii

List of Tables

TIA/EIA/IS-826

REVISION HISTORY
Rev. 0 Date May 2000 Remarks Ballot Version

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

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

5

SSF/CCF CALL AND SERVICE LOGIC MODEL
General

5.1

5.1.3

Service Interactions Manager (SIM) - SCF
(TIA/EIA/IS-771, page 7-20)

The service interactions manager (SIM) at the SCF coordinates the invocation of features applicable for a subscriber at a given trigger at a Detection Point (DP). The SIM has knowledge of the relevant SCF-executed features resident on the same SCF and an indication when another feature on a separate SCF requires interaction at certain points in the SIM logic flow. When service logic is distributed across multiple SCFs, the SIM is also distributed. The first SIM invoked by the trigger must coordinate the precedence and data changes that affect call processing within the SCF and between SCFs. This is illustrated in Figure 5.

SCF
FSLP i FSLP j FSLP k SIM FSLP x

SCF
FSLP y FSLP z SIM

SSF/CCF
Legend Call Control Function Feature Service Logic Program Service Control Function Service Interactions Manager Service Switching Function

CCF FSLP SCF SIM SSF

Figure 5

Service Interactions Manager at the SCF

PPC TIA/EIA/IS-771.7 Modifications

7-1

Originating BCSM

TIA/EIA/IS-826

Basic rules include: a. Once an SCF-executed feature is given control, it must complete its task before returning control to the SIM. The setting of Event Detection Point - Response (EDP-Rs) indicates the need for the feature to regain control at a future DP, but yields current control of service logic to other features. SIM rules include the actions to be taken based on the response of the feature’s invocation. Additional features in this SCF may be invoked or a response may be prepared for the entity (another SIM or BCM) which had invoked the SIM processing. The SIM coordinates the response to the invoking entity (SSF or CCF). The response is based on the responses of all features invoked. A single response is sent to the invoking entity regardless of the number of features invoked. Coordination of EDP-N, EDP-R, TDP-N and TDP-R events and triggers is done by the SIM. Thus, the response to the invoking entity may contain information that would not be in a single feature’s response, but represents a synthesis of all of the features that were invoked. d. The SIM determines if dynamically armed triggers are required after service logic execution is complete. If the call is not being redirected by service logic, dynamically arming triggers will result in any previously armed triggers for the call being disarmed. The dynamically armed triggers will be armed for the remainder of the call in progress (or until a subsequent TriggerAddressList is received). If the call is being by service logic, dynamically armed triggers will be applied to the redirected call leg.
The SIM determines which triggers should be dynamically armed subsequent to execution of service logic. Such dynamically armed triggers overwrite previously armed triggers for call leg duration.

1 2 3 4 5 6

b.

7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

c.

d.

30 31 32 33 34

As part of managing service execution interactions, the SIM is responsible for handling WIN Feature Code processing. For example, a SIM associated with the Single_Introducing_Star and Home_System_Feature_Code triggers, receives WIN feature codes entered by a subscriber. This SIM will determine where feature codes are to be processed and, if necessary, to forward feature codes to another physical platform for 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

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

5.2

SSF/CCF Model

5.2.2.1

Originating BCSM
(TIA/EIA/IS-771, page 7-25)

The originating half of the BCSM corresponds to that portion of the BCSM associated with the originating party (see Figure 8). The descriptions for each of the PICs in the originating half of the BCSM are described below:

PPC TIA/EIA/IS-771.7 Modifications

7-3

Originating BCSM

TIA/EIA/IS-826

O_Null

O_Exception

1 2 3

O_Abandon DP Origination_Attempt_DP Authorize_Origination_Attempt origination_denied

4 5 6 7 8 9 10

Origination_Attempt_Authorized DP Collect_Information collect_failure

11 12 13 14 15

Collected_Information DP Analyze_Information invalid_information

16 17 18 19 20

route_busy

21

Analyzed_Information DP Select_Route Route_Select_Failure DP

22 23 24 25 26 27

route_failure authorization_route_failure Authorize_Call_Setup

28 29 30

O_Called_Party_Busy DP Send_Call O_Mid_Call DP O_Term_Seized DP O_Alerting O_Mid_Call DP O_Answer DP O_Active O_Mid_Call DP O_Re-answer DP O_Suspend DP O_Suspended O_Disconnect DP O_Mid_Call DP No WIN triggers defined for the DP in this standard reconnect O_suspend_failure O_active_failure O_No_Answer DP

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

Figure 8

Originating Call Model

57 58 59 60

Originating BCSM

7-4

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

O_Null Entry Event: – – Disconnect and clearing of a previous call. O_Abandon). (DPs: O_Disconnect and

Default handling of exceptions by SSF/CCF completed (Transition from O_Exception PIC).

Functions: – Clear any resources allocated to the originating party (no call exists, no call reference exists, no radio channel allocated for call, etc.).

Exit Event: – Indication of a desire to place an outgoing call (e.g., an indication is received from the RACF of an origination attempt by an MS user). (DP: Origination_Attempt). Other indication from an originating party of a desire to place a call (e.g., ISDNUP IAM message). (DP: Origination_Attempt). The following exception exit event is applicable to the O_Null PIC. For this PIC, if the call encounters this exception during O_Null PIC processing, the exception event is not visible because there is no corresponding DP. i) The O_Abandon occurs when the calling party disconnects.

– –

Authorize_Origination_Attempt Entry Event: – An indication is available that the originating MS needs to be authorized. (DP: Origination_Attempt).

Functions: – – Collects the information required to authorize the call for MS origination. The originating MS rights are checked using the MS identity and service profile. The right of the MS to place the call with given properties (e.g., bearer capability, subscriber profile restrictions) is verified. For MS origination, sends an indication to the RACF to select a radio channel (i.e., select RCF) for MS origination and order the MS to use the channel. If no channel is immediately available, the RACF may invoke Priority Access and Channel Assignment (PACA) to wait for a channel to become available.

Exit Event: – Authority/ability to place outgoing call verified. For MS origination, radio channel is available and assigned to the MS. (DP: Origination_Attempt_Authorized). Authority/ability to originate call is denied. This event causes a transition to the O_Exception PIC.

PPC TIA/EIA/IS-771.7 Modifications

7-5

Originating BCSM

TIA/EIA/IS-826

– –

Failure to select a radio channel for the MS. This event causes a transition to the O_Exception PIC. A disconnection indication is received from the originating party. (DP: O_Abandon).

1 2 3 4 5 6

Collect_Information Entry Event: – Authority/ability to place outgoing call verified. For MS origination, radio channel available and assigned to the MS. (DP: Origination_Attempt_Authorized).

7 8 9 10 11 12 13 14

Functions: – Initial information package/dialing string (e.g., service codes, prefixes, dialed address digits) being collected from originating party. Information being examined according to dialing plan to determine end of collection. No further action may be required if an en bloc signaling method is in use (e.g., an incoming SS7 trunk). Subsequent digit collection according to the subscriber profile (e.g., for PIN collection). After digit collection is completed, the SSF/CCF should be able to verify that the MS is authorized for the outgoing call.

15 16 17 18 19 20 21 22

23 24 25 26

Exit Event: – Availability of complete initial information package/dialing string from originating party. (This event may have already occurred in the case of en bloc signaling, in which case the duration of this PIC is zero). (DP: Collected_Information). Originating party abandons call. (DP: O_Abandon). After digit collection is complete, authority to originate call is denied. This event causes a transition to the O_Exception PIC. Information collection error has occurred (e.g., invalid dial string format, digit collection timeout). This event causes a transition to the O_Exception PIC.

27 28 29 30 31 32 33

– – –

34 35 36 37 38 39 40 41

Comment: Some digit analysis is required to determine the end of dialing. However, it is assumed that this analysis may be modeled as separable from the rest of digit analysis, which occurs in the Analyze_Information PIC. There is no intention to specify an implementation. However, an MSC should externally present the separable views described1.

42 43 44 45 46 47 48 49 50 51 52 53

1 The separable views are provided by supporting distinct DPs for Collected_Information and

54 55 56 57 58 59 60

Analyzed_Information and by populating information flows accordingly for corresponding TDP and EDP information flows to the SCF.

Originating BCSM

7-6

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

Analyze_Information Entry Event: – Availability of complete initial information package/dialing string from originating party. (DP: Collected_Information).

Functions: – Information being analyzed and/or translated according to dialing plan to determine routing address and call type (e.g., termination to MS, local exchange call, transit exchange call, international exchange call).

Exit Event: – – – Availability of routing address and call type. (DP: Analyzed_Information). The invalid information event (e.g., invalid dialed digits). This event causes a transition to the O_Exception PIC. Originating party abandons the call. (DP: O_Abandon).

Comment: Note that routing address does not necessarily mean that the final physical route has been determined (e.g., route list has not been searched, hunt groups have not been searched, directory number has not yet been translated to a physical port address), though this may be the case (e.g., when routing to a special private facility).

Select_Route Entry Event: – – Availability of routing address and call type. (DP: Analyzed_Information). Route failure reported from the Send_Call PIC or O_Alerting PIC.

Functions: – Routing address and call type being interpreted. The next route is being selected. This may involve sequentially searching a route list, translating a directory number into a physical port address, etc. The individual destination resource out of a resource group (e.g., a multi-line hunt group, a trunk group) is not selected.

Exit Event: – – Unable to select a route (e.g., unable to determine a correct route, no more routes on the route list). (DP: Route_Select_Failure). The route_busy event leading to the Analyze_Information PIC. Route_busy is a non-WIN transition which is part of a basic call. If the trunk group selected for the call is busy at this switch, the SSF/CCF attempts to route the call on the next trunk group that has been specified for the call. Call processing moves to the Analyze_Information PIC when routing to a particular intra-network or internetwork carrier has been tried and an alternate carrier is allowed. Terminating resource (group) to which call should be routed has been identified. This event causes call processing to move to the Authorize_Call_Setup PIC. Originating party abandons the call. (DP: O_Abandon).

– –

PPC TIA/EIA/IS-771.7 Modifications

7-7

Originating BCSM

TIA/EIA/IS-826

Authorize_Call_Setup Entry Event: – Terminating resource (group) to which call should be routed has been identified.

1 2 3 4 5

Functions: – The authority of the calling party to place this particular call is verified.

6 7 8 9 10

Exit Event: – Authority of originating party to place this call is denied (e.g., business group restriction mismatch, toll restricted calling line). This event causes a transition to the O_Exception PIC. Authority of originating party to place this call is verified. This event causes call processing to move to the Send_Call PIC. Originating party abandons the call. (DP: O_Abandon).

11 12 13 14 15 16 17 18

– –

19 20 21

Send_Call Entry Event: – Authority of originating party to place this call is verified.

22 23 24 25 26 27

Functions: – The originating half BCSM sends an indication to the terminating half BCSM of the desire to set up a call to the specified called party. Continued processing of call setup (e.g., ringing, audible ring indication) is taking place. The originating half BCSM waits for the indication that the call has been answered by the terminating party.

28 29 30 31 32 33 34 35

Exit Event: – An indication is received from the terminating half BCSM that the terminating party is busy. (DP: O_Called_Party_Busy). In addition to terminating party busy events, the following call_rejected conditions are also treated as O_Called_Party_Busy events: i) a termination_denied indication is received from the terminating half BCSM (Authorize_Termination_Attempt PIC); or,

36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51

ii) a call_rejected indication is received from the terminating half BCSM (T_Alerting PIC) that does not specify busy. – – – – An indication is received from the terminating half BCSM that the terminating party does not answer. (DP: O_No_Answer). An indication is received from the terminating half BCSM that the terminating party is being alerted. (DP: O_Term_Seized). An indication is received from the terminating half BCSM that the call is accepted and answered by the terminating party. (DP: O_Answer DP). A route_failure event is detected when:

52 53 54 55 56 57 58 59 60

Originating BCSM

7-8

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

i)

an indication of a T_Busy event specifying route busy; is received from the terminating half BCSM, or

ii) an indication of a call_rejected event specifying route busy (received when the route is found to be busy at a switch other than the local switch) is received from the terminating half BCSM (T_Alerting PIC). iii) an indication of a presentation_failure event specifying route busy is received from the terminating half BCSM (Present_Call PIC). In all these cases, the originating half BCSM returns to the Select_Route PIC. This event is not detected at a DP. Note: The route_failure event takes precedence over the O_Called_Party_Busy and O_No_Answer events. – – An indication is received from the RCF of a service feature request by the originating MS. (DP: O_Mid_Call). For SS7-supported trunk interface, the authorization_route_failure event occurs when the continuity check procedure results in failure. This event causes a transition to the O_Exception PIC. Originating party abandons the call. (DP: O_Abandon).

O_Alerting Entry Event: – An indication is received from terminating half BCSM that the terminating party is being alerted. (DP: O_Term_Seized).

Functions: – – Continue processing of call setup. Waiting for indication from the terminating half BCSM that the call has been answered by the terminating party.

Exit Event: – A route failure event is detected when all of the following conditions are met: i) the O_Called_Party_Busy event or O_No_Answer event occurs as specified below,

ii) call forwarding applies, iii) there are more called party numbers left to try. Note: the Route_Failure event takes precedence over the O_Called_Party_Busy and O_No_Answer events. In this case the originating call portion returns to the Select_Route PIC. This event is not detected at a DP in WIN. – – An indication is received from the terminating half BCSM that the terminating party does not answer within a specified time period. (DP: O_No_Answer). An indication is received from the terminating half BCSM that the call is accepted and answered by the terminating party. (DP: O_Answer).

PPC TIA/EIA/IS-771.7 Modifications

7-9

Originating BCSM

TIA/EIA/IS-826

From this PIC, the O_Called_Party_Busy event occurs either when: i) an indication of a call_rejected event specifying user busy is received from the terminating half BCSM (T_Alerting PIC), or

1 2 3 4

ii) an indication of a call_rejected event not specifying user busy is received from the terminating half BCSM (T_Alerting PIC). For example, the terminating party may reject the call. The originating half BCSM moves to the O_Called_Party_Busy DP. – – An indication is received from the RCF of a service feature request by the originating MS. (DP: O_Mid_Call). Originating party abandons the call. (DP: O_Abandon)

5 6 7 8 9 10 11 12 13 14 15

O_Active Entry Event: – An indication is received from the terminating half BCSM that the call is accepted and answered by the terminating party. (DP: O_Answer).

16 17 18 19 20 21 22

Functions: – Connection established between originating and terminating party. Message accounting/charging data may be collected. Call supervision is being provided.

23 24 25 26 27

Exit Event: – – – – – An indication is received from the RCF of a service feature request by the originating MS. (DP: O_Mid_Call). A disconnect indication is received from the originating party. (DP: O_Disconnect). A disconnect indication is received from the terminating party via the terminating half BCSM. (DP: O_Disconnect). A suspend disconnect indication is received from the terminating party via the terminating half BCSM. (DP: O_Suspend). A connection failure occurs. This event causes a transition to the O_Exception PIC.

28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45

O_Suspended Entry Event: – A suspend disconnect indication is received from the terminating party via the terminating half BCSM. (DP: O_Suspend).

46 47 48 49 50 51 52

Functions (the function of this PIC is not currently supported for MS originated calls): – The connection with the originating party is maintained and depending on the incoming access connection, appropriate signaling takes place.

53 54 55 56 57 58 59 60

Originating BCSM

7-10

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

i)

In case that a disconnect indication is received from the terminating half BCSM, this PIC is immediately exited to the O_Disconnect DP without any action. As an option for MS originated calls, the call can be continued for an appropriate period in order to offer follow-on initiated by O_Mid_Call.

ii) If the re-answer indication from the terminating half BCSM is received, the originating and terminating parties are reconnected. iii) Other features may be required during this PIC (for further study).

Exit Event: – Connection to the terminating party is resumed. The originating half BCSM returns to the O_Active PIC. (DP: O_Re-answer). Note: This transition to the O_Active PIC is not applicable for wireless calls. – – – – – – An indication is received from the RCF of a service feature request by the originating MS. (DP: O_Mid_Call). A disconnection indication is received from the originating party. (DP: O_Disconnect). A disconnection indication is received from the terminating party. (DP: O_Disconnect). An exception event is encountered. This event causes a transition to the O_Exception PIC. An indication of expiration of the timer waiting for re-answer request is received from the terminating half BCSM. (DP: O_Disconnect). A trigger at O_Mid_Call is not initiated during an appropriate period. (DP: O_Disconnect).

O_Exception Entry Event: – An exception event is encountered as described above for each PIC.

Functions: – Default handling of the exception condition is being provided. This includes general actions necessary to ensure no resources remain inappropriately allocated, such as: i) If any relationships exist between the SSF and SCF(s), send an error information flow to the SCF(s) closing the relationships and indicating that any outstanding call handling instructions will not run to completion.

ii) The SSF/CCF should make use of vendor-specific procedures to ensure release of resources so that radio, trunk, and other resources are made available for new calls.

PPC TIA/EIA/IS-771.7 Modifications

7-11

Originating BCSM

TIA/EIA/IS-826

Exit Event: – Default handling of the exception condition by SSF/CCF completed. (Transition to O_Null PIC)

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

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

5.2.2.2

Terminating BCSM
(TIA/EIA/IS-771, page 7-35)

The terminating half of the BCSM corresponds to that portion of the BCSM associated with the terminating party (see Figure 9). The description for each of the PICs in the terminating half of the BCSM are described below:
T_Null T_Exception

T_Abandon DP Termination_Attempt_DP Authorize_Termination_Attempt termination_denied

Termination_Attempt_Authorized DP T_Busy DP Select_Facility

Facility_Selected_and_Available DP Present_Call

SS7_failure presentation_failure

Call_Accepted DP T_Alerting T_No_Answer DP call_rejected T_Answer DP T_Active T_Mid_Call DP T_Re-answer DP T_Suspend DP T_Suspended T_Disconnect DP reconnect T_suspend_failure T_active_failure

No WIN triggers defined for the DP in this standard

Figure 9

Terminating Call Model

PPC TIA/EIA/IS-771.7 Modifications

7-13

Terminating BCSM

TIA/EIA/IS-826

T_Null Entry Event: – – Disconnect and clearing of a previous call (DPs: T_Disconnect or T_Abandon) Default handling of the exception condition by SSF/CCF completed. (Transition from T_Exception PIC).

1 2 3 4 5 6 7 8 9

Functions: – Clear any resources allocated to the terminating MS.

10 11 12 13

Exit Event: – – An indication of incoming call is received from the originating half BCSM. (DP: Termination_Attempt). The following exception exit event is applicable to this PIC: T_Abandon. i) The T_Abandon occurs when an indication of call disconnection is received from the originating half BCSM. If the call encounters T_Abandon during PIC processing, the exception event is not visible because there is no corresponding DP.

14 15 16 17 18 19 20 21 22 23 24 25 26

Authorize_Termination_Attempt Entry Event: – Indication of incoming call received from the originating half BCSM. (DP: Termination_Attempt)

27 28 29 30 31 32 33 34

Functions: – Authority to route the call to the terminating access (e.g., MS or trunk group) is being verified, e.g., check business group restrictions, restricted incoming access to line, or bearer capability compatibility.

35 36 37 38 39 40

Exit Event: – Termination_Attempt_Authorized event. This event occurs when the MSC has verified the authority to terminate the call to the terminating access. (DP: Termination_Attempt_Authorized). The Termination Denied event occurs when the authority to route these call to the terminating user is denied. (This causes a transition to the T_Exception PIC). The T_Abandon event occurs when an indication of clearing is received from the originating half BCSM. (DP: T_Abandon).

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

Terminating BCSM

7-14

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

Select_Facility Entry Event: – Termination_Attempt_Authorized event. This event occurs when the MSC has verified the authority to terminate the call to the terminating access. (DP: Termination_Attempt_Authorized). An SS7 failure occurs causing a re-attempt. The SS7 failure in the Present_Call PIC can be caused by a timer expiry upon sending the first Circuit Reservation Message (CRM) or a continuity check failure.

Functions: – A particular network resource is being selected. It is possible that all resources in the group could be busy or unavailable. A single resource is considered a group of one. For MS termination, the terminating half BCSM sends an indication to the RACF to select facilities (e.g., page the MS, MS page response, trunk to cell, radio channel within cell) for the call. The MS is assigned to the radio channel.1 The busy/idle status of the terminating access is determined. i) For termination to an MS, the MS is treated as user busy if it is already involved in an existing call and cannot receive another call (e.g., call waiting is not active).

ii) For termination to an MS, the MS is treated as network busy if no radio channels are available or a routing failure occurs while attempting to complete the call. iii) For termination to an MS, the MS is treated as unavailable if it is not available for call termination, an indication that the MS does not respond to a page is received from the RACF2, or an indication of a failure to assign the MS to a radio channel is received from the RACF. iv) For calls routed out of this SSF/CCF, network-determined user busy is the detection of terminating party busy. v) For calls routed out of this SSF/CCF, network busy is when all trunks within the selected trunk group are busy.

For call arrival with TLDN, if the MS status is busy (user or network) or unavailable and the subscriber profile indicates call redirection on Busy, No Page Response, No Answer or Routing Failure, a RedirectionRequest INVOKE3 is sent to the Originating MSC with the RedirectionReason parameter set to indicate the reason for redirection. The response determines the exit event.

1 If the MS is already assigned to a radio channel, only the selection of a trunk to the serving

cell may be required.
2The MS is treated as unavailable if it fails authentication when it responds to the page. 3The REDREQ will not be sent if office provisioning indicates that call redirection will be done

by the Serving MSC.

PPC TIA/EIA/IS-771.7 Modifications

7-15

Terminating BCSM

TIA/EIA/IS-826

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

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

Present_Call Entry Event: – Available terminating resource identified and facilities selected. (DP: Facility_Selected_and_Available).

24 25 26 27 28 29 30

Functions: – Terminating resource informed of incoming call (e.g., indication sent to RCF about the call).

31 32 33 34 35

Exit Event: – Terminating party is being alerted (e.g., indication from RCF that ringing is being applied, ringing being applied, ISDN-UP ACM message). (DP: Call_Accepted). Call is accepted and answered by terminating party (e.g., indication from RCF of call answer by MS, terminating party goes off hook, ISDN-UP answer message received). (DP: T_Answer). For call routed out of this SSF/CCF to an MS, RedirectionRequest INVOKE received with the RedirectionReason parameter indicating Busy, No Page Response, Unavailable or Unroutable. (DP: T_Busy). After detecting T_Busy, if WIN service logic is not needed on the call, an indication of the T_Busy event is passed to the originating half BCSM (Send_Call PIC). If a terminating feature acts on the T_Busy event and changes the event [e.g., as in the Call Forwarding feature], the event is not passed to the originating half BCSM. – For call routed out of this SSF/CCF to an MS, RedirectionRequest INVOKE message received with the RedirectionReason parameter indicating No Answer or Call Refused. (DP: T_No_Answer).

36 37 38 39 40 41 42 43 44 45

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

Terminating BCSM

7-16

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

After detecting T_No_Answer, if WIN service logic is not needed on the call, an indication of the T_No_Answer event is passed to the originating half BCSM (Send_Call PIC). If a terminating feature acts on the T_No_Answer event and changes the event [e.g., as in the Call Forwarding feature], the event is not passed to the originating half BCSM. – A timer expiry upon sending the first Circuit Reservation Message (CRM) or a continuity check failure. (SS7 failure). This event causes call processing to move to the Select_Facility PIC. Presentation Failure: For call routed out of this SSF/CCF, the call cannot be presented, (e.g., ISDN user determined busy, ISDN-UP release message with busy cause). This event causes the terminating half BCSM to move to the T_Exception PIC and an indication sent to the originating half BCSM (Send_Call PIC). An indication of originating party abandon is received from originating half BCSM. (DP: T_Abandon).

T_Alerting Entry Event: – Terminating party is being alerted of incoming call (DP: Call_Accepted).

Functions: – An indication is sent to the originating half BCSM that the terminating party is being alerted. Continued processing of call setup (e.g., ringing, audible ring indication) is taking place. Waiting for the call to be answered by the terminating party. For call arrival with TLDN, if the MS does not answer the alert and the subscriber profile indicates call redirection on a “no answer” condition 1 , a RedirectionRequest INVOKE is sent to the Originating MSC with the RedirectionReason parameter indicating No Answer or Call Refused, as appropriate. The response determines the exit event.

Exit Event: – Call is accepted and answered by terminating party (e.g., indication from RCF of call answer by MS, terminating party goes off hook, ISDN-UP answer message received). (DP: T_Answer). For call arrival with TLDN, the MS does not answer the alert and the response to the RedirectionRequest INVOKE indicates success. (DP: T_Exception). Terminating party does not answer before the MSC-based ringing timer expires. For call arrival with TLDN, the MS does not answer the alert and the response to the RedirectionRequest INVOKE indicates failure. For MS termination, loss of radio contact with MS. For call routed out of this SSF/CCF to an MS, RedirectionRequest INVOKE received with the RedirectionReason parameter indicating No Answer or Call Refused. (DP: T_No_Answer).

– –

1The REDREQ will not be sent if office provisioning indicates that call redirection will be done

by the Serving MSC.

PPC TIA/EIA/IS-771.7 Modifications

7-17

Terminating BCSM

TIA/EIA/IS-826

After detecting T_No_Answer, if WIN service logic is not needed on the call, an indication of the T_No_Answer event is passed to the originating half BCSM (Send_Call PIC). If a terminating feature acts on the T_No_Answer event and changes the event [e.g., as in the Call Forwarding feature], the event is not passed to the originating half BCSM. – Call_rejected exception event may happen when a user rejects a call while being alerted. This event causes the terminating half BCSM to move to the T_Exception PIC and an indication sent to the originating half BCSM (Send_Call PIC). Indication of originating party abandon received from the originating half BCSM. (DP T_Abandon)

1 2 3 4 5 6 7 8 9 10

11 12 13 14

T_Active Entry Event: – Call is accepted and answered by terminating party. (DP: T_Answer).

15 16 17 18 19 20

Functions: – An indication is sent to the origination half BCSM that the terminating party has accepted and answered the call. Connection established between originating and terminating party. Call supervision is being provided.

21 22 23 24 25 26

Exit Event: – – – – – An indication is received from the RCF of a service feature request by the terminating MS. (DP: T_Mid_Call). A suspend disconnect indication is received from the terminating party. (DP: T_Suspend). A disconnect indication is received from the terminating party. (DP: T_Disconnect). A disconnect indication is received from the originating party via the originating half BCSM. (DP: T_Disconnect). A connection failure occurs or loss of radio contact with MS. This event causes the terminating half BCSM to move to the T_Exception PIC and an indication sent to the originating half BCSM.

27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44

T_Suspended Entry Event: – A suspend disconnect indication is received from the terminating party. (DP: T_Suspend).

45 46 47 48 49 50 51 52

Functions: – – The physical resources associated with the call remain connected. A suspend indication is sent to the originating half BCSM.

53 54 55 56 57 58 59 60

Terminating BCSM

7-18

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

A disconnect indication (e.g., Q.931 disconnect message, SS7 release message) is received from the terminating party, this PIC is immediately exited to the T_Disconnect DP without any action. For an SS7 supported trunk, when the receiving network initiates a suspend message, a timer is started and the call processing waits for re-answer request from the terminating party. If re-answer request (e.g., off-hook, SS7 resume message) is received from the terminating party before the timer expires, the originating and terminating parties are reconnected. Note: Both a Call Resume timer and a Call Retention timer may exist in this PIC. WIN implementations may use a single timer for both conditions.

Exit Event: – The terminating party re-answers or a resume message is received before the timer expires. The T_BCSM returns to the T_Active PIC. (DP: T_Re-answer). Note: This transition to the T_Active PIC is not applicable for wireless calls. – – – – The expiration of the timer waiting for re-answer from the terminating party. (DP: T_Disconnect). A disconnection indication is received from the terminating party (DP: T_Disconnect). A disconnection indication is received from the originating party via the originating half BCSM. (DP: T_Disconnect). An exception event is encountered. This event causes a transition to the T_Exception PIC.

T_Exception Entry Event: – An exception event is encountered as described above for each PIC.

Functions: – An indication of the exception condition is sent to the originating half BCSM. Default handling of the exception condition is being provided. This includes general actions necessary to ensure no resources remain inappropriately allocated, such as: i) If any relationships exist between the SSF and SCF(s), send an error information flow to the SCF(s) closing the relationships and indicating that any outstanding call handling instructions will not run to completion.

ii) The SSF/CCF should make use of vendor-specific procedures to ensure release of resources so that radio, trunk, and other resources are made available for new calls.

Exit Event: – Default handling of the exception condition by SSF/CCF completed. (Transition to O_Null PIC)

PPC TIA/EIA/IS-771.7 Modifications

7-19

Terminating BCSM

TIA/EIA/IS-826

5.2.2.3

BCSM Transitions
(TIA/EIA/IS-771, page 7-42)

1 2 3 4 5 6 7

The complete set of transitions for the Originating BCSM are shown in Table 1 below. The shaded DPs do not have triggers defined in this standard. The Nature of BCSM Transition indicates whether the transition is Basic or Extended. • • Basic: call processing resumes in sequence (i.e., continue) Extended: the next step in call processing is specified by SCF Table 1
From Origination_Attempt DP Orig._Attempt_Authorized DP Collected_Information DP

8 9 10 11

Originating BCSM Transitions
To Authorize_Orig._Attempt PIC Collect_Information PIC Collect_Information PIC Analyze_Information PIC Select_Route PIC Basic Extended Basic Extended Extended Extended Basic Nature of BCSM Transition

12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

Analyzed_Information DP

Collect_Information PIC Analyze_Information PIC Select_Route PIC

O_Term_Seized DP Route_Select_Failure DP O_Called_Party_Busy DP O_No_Answer DP O_Answer DP O_Suspend DP O_Re-Answer DP O_Mid_Call DP O_Mid_Call DP O_Mid_Call DP O_Mid_Call DP O_Disconnect DP O_Abandon DP

O_Alerting PIC O_Exception O_Exception O_Exception O_Active PIC O_Suspended PIC O_Active PIC Send_Call PIC O_Alerting PIC O_Active PIC O_Suspended PIC O_Null PIC O_Null PIC Basic Basic

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

BCSM Transitions

7-20

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

Table 1
From O_Null PIC Auth._Orig._Attempt PIC

Originating BCSM Transitions (concluded)
To Origination_Attempt DP Orig._Attempt_Auth. DP O_Abandon DP O_Exception Basic Basic Basic Basic Basic Basic Basic Basic Nature of BCSM Transition

Collect_Information PIC

Collected_Information DP O_Abandon DP O_Exception

Analyze_Information PIC

Analyzed_Information DP O_Abandon DP O_Exception

Select_Route PIC

Analyze_Information PIC Authorize_Call_Setup PIC Route_Select_Failure DP O_Abandon DP

Authorize_Call_Setup PIC

Send_Call PIC O_Abandon DP O_Exception

Basic Basic

Send_Call PIC

O_Term_Seized DP O_Mid_Call DP O_Called_Party_Busy DP O_Answer DP O_No_Answer DP Select_Route PIC O_Abandon DP O_Exception Basic Basic Basic Basic Basic

O_Alerting PIC

Select_Route PIC O_Mid_Call DP O_Answer DP O_No_Answer DP O_Called_Party_Busy DP O_Abandon DP

O_Active PIC

O_Mid_Call DP O_Disconnect DP O_Suspend DP O_Exception Basic Basic

O_Suspended PIC

O_Re-Answer DP O_Mid_Call DP O_Disconnect DP O_Exception Basic Basic Basic

O_Exception

O_Null PIC

PPC TIA/EIA/IS-771.7 Modifications

7-21

BCSM Transitions

TIA/EIA/IS-826

The complete set of transitions for the Terminating BCSM are shown in Table 2 below. The shaded DPs do not have triggers defined in this standard. Table 2
From Termination_Attempt DP Term._Attempt_Auth. DP Facility_Sel._And_Avail. DP Call_Accepted DP T_Busy DP

1 2 3 4

Terminating BCSM Transitions
To Auth._Term._Attempt PIC Select_Facility PIC Present_Call PIC T_Alerting PIC Select_Facility PIC Present_Call PIC T_Exception Extended Extended Basic Extended Basic Basic Basic Nature of BCSM Transition

5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

T_No_Answer DP

Select_Facility PIC T_Exception

T_Answer DP T_Suspend DP T_Re-Answer DP T_Mid_Call DP T_Disconnect DP T_Abandon DP

T_Active PIC T_Suspended PIC T_Active PIC T_Active PIC T_Null PIC T_Null PIC

23 24 25 26

Basic

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

BCSM Transitions

7-22

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

Table 2
From T_Null PIC

Terminating BCSM Transitions (concluded)
To Termination_Attempt DP T_Exception T_Abandon DP Term._Attempt_Auth. DP Basic Nature of BCSM Transition

Auth._Term._Attempt PIC

Select_Facility PIC

Facility_Selected_And_Avail. DP T_Busy DP T_Abandon DP

Basic Basic Basic Basic Basic Basic Basic Basic

Present_Call PIC

Select_Facility PIC T_Abandon DP T_Busy DP T_No_Answer DP T_Exception Call_Accepted DP T_Answer DP

T_Alerting PIC

T_Answer DP T_Abandon DP T_Exception T_No_Answer DP

Basic Basic Basic Basic

T_Active PIC

T_Exception T_Mid_Call DP T_Disconnect DP T_Suspend DP

T_Suspended PIC

T_Disconnect DP T_Re-Answer DP T_Exception

Basic

Basic Basic

T_Exception

T_Null PIC

PPC TIA/EIA/IS-771.7 Modifications

7-23

BCSM Transitions

TIA/EIA/IS-826

5.2.3

BCSM Detection Points

1 2 3 4 5

5.2.3.4

Trigger Types and Trigger Precedence
(TIA/EIA/IS-771, page 7-52)

6 7 8 9 10 11 12 13 14

Trigger types denote classes of events of interest. They are used to establish trigger precedence rules at TDPs and to indicate to the SCF the service logic to be invoked. A non-exhaustive list of trigger types are defined. Definition of future trigger types is for further study. The trigger types are described in terms of: 1. 2. TDP - the DP at which the trigger can be detected. DP Criteria - the conditions needed to trigger. Criteria may be conditional effective only when the trigger is active and the criteria is satisfied, or unconditional - always effective when the trigger is active. Category - office, group, or subscribed (subscriber based). Interface - type of interface to which it can be assigned (e.g., inter-office trunk, mobile origination, mobile termination). Trigger Type - the value that identifies the type of criteria that caused the SSF/CCF to detect a valid trigger condition at this TDP. Fault Handling - defines fault handling procedures for the case when the SCF does not respond to the SSF/CCF message. Details on possibilities for fault handling are for further study. TIA/EIA-41 operation - identifies the TIA/EIA-41 operation used to query WIN service logic (e.g., SCP). Arming Mechanism - identifies the possible mechanisms by which the trigger is armed. Subscribed triggers may be armed by parameters received by the MSC (e.g., in a regnot, qualreq or QUALDIR). Triggers may be dynamically armed on a per call basis by parameters within call related operations (e.g., orreq, featreq, locreq, ROUTREQ) Office based triggers are armed in the provisioning process by separate service management systems that are beyond the scope of this standard.

15 16 17 18 19 20 21 22 23

3. 4. 5. 6.

24 25 26 27 28 29 30 31 32

7. 8.

33 34 35 36 37 38 39 40 41 42 43 44 45

Editor’s note; the following terminology is not correct per the DFP and ITU-T DFP. The original text is more correct. Triggers are armed at a DP, not contained within a DP!
Since the same DP may contain multiple triggers which may be armed multiple times as a TDP-Rs, precedence rules for trigger processing are specified as: 1. 2. 3. subscribed triggers have precedence over group triggers group triggers have precedence over office triggers more specific triggers take precedence over less specific triggers (e.g., a 6-digit trigger takes precedence over a 3-digit trigger)

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

BCSM Transitions

7-24

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

The sequence for processing WIN triggers should be as detailed in Tables 4 and 5 below. Table 4 WIN Trigger Precedence for Originating BCSM
Trigger Type Locally_Allowed_Specific_Digit_String Origination_Attempt_Authorized Collected_Information All_Calls Double_Introducing_Star Single_Introducing_Star Home_System_Feature_Code Double_Introducing_Pound Single_Introducing_Pound Revertive_Call K-Digit Analyzed_Information Local_Call Intra_LATA_Toll_Call Inter_LATA_Toll_Call World_Zone_Call International_Call Unrecognized_Number Prior_Agreement Specific_Called_Party_Digit_String Calling_Routing_Address_Available Mobile_Termination Initial_Termination Advanced_Termination Location Called_Routing_Address_Available O_Answer O_Disconnect O_Answer O_Disconnect Reference 5.2.3.4.33 5.2.3.4.25 5.2.3.4.1 5.2.3.4.2 5.2.3.4.3 5.2.3.4.4 5.2.3.4.5 5.2.3.4.6 5.2.3.4.7 5.2.3.4.8 5.2.3.4.9 5.2.3.4.10 5.2.3.4.11 5.2.3.4.12 5.2.3.4.13 5.2.3.4.14 5.2.3.4.15 5.2.3.4.16 5.2.3.4.27 5.2.3.4.17 5.2.3.4.26 5.2.3.4.18 5.2.3.4.19 5.2.3.4.28 5.2.3.4.29 5.2.3.4.30

Trigger Detection Point Origination_Attempt_Authorized

PPC TIA/EIA/IS-771.7 Modifications

7-25

BCSM Transitions

TIA/EIA/IS-826

Table 5

WIN Trigger Precedence for Terminating BCSM
Trigger Type Terminating_Resource_Available T_Busy T_No_Page_Response T_Unroutable Reference 5.2.3.4.20 5.2.3.4.21 5.2.3.4.22 5.2.3.4.23 5.2.3.4.24 5.2.3.4.31 5.2.3.4.32

1 2 3 4 5 6 7 8 9 10

Trigger Detection Point Facility_Selected_and_Available T_Busy

T_No_Answer T_Answer T_Disconnect

T_No_Answer T_Answer T_Disconnect

11 12 13 14 15 16 17

Locally allowed numbers escape the subscribed triggers at the Collected_Information and Analyzed_Information Detection Points. However these subscribed triggers at the Collected_Information and Analyzed_Information Detection Points do take precedence over “hot line.”

18 19 20 21 22 23

5.2.3.4.1

All_Calls

24 25

The All_Calls trigger is detected for all MS originated calls. 1. 2. 3. 4. 5. 6. 7. 8. TDP - Collected_Information DP Criteria - UnconditionalTrigger assigned (unconditional) Category - Subscribed Interface - mobile origination Trigger Type - All_Calls Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - OriginationRequest INVOKE Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., orreq)

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

BCSM Transitions

7-26

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

5.2.3.4.2

Double_Introducing_Star

The Double_Introducing_Star trigger is detected for MS originated calls having ‘**’ as the first two dialed digits. 1. 2. 3. 4. 5. 6. 7. 8. TDP - Collected_Information DP Criteria - Conditional Category - Subscribed Interface - mobile origination Trigger Type - Double_Introducing_Star Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - OriginationRequest INVOKE Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., orreq)

5.2.3.4.3

Single_Introducing_Star

The Single_Introducing_Star trigger is detected for MS originated calls with ‘*’ as the first dialed digit but not as the second dialed digit. 1. 2. 3. 4. 5. 6. 7. 8. TDP - Collected_Information DP Criteria - Conditional Category - Subscribed Interface - mobile origination Trigger Type - Single_Introducing_Star Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - OriginationRequest INVOKE Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., orreq)

PPC TIA/EIA/IS-771.7 Modifications

7-27

BCSM Transitions

TIA/EIA/IS-826

5.2.3.4.4

Home_System_Feature_Code

1 2 3 4 5 6

The Home_System_Feature_Code trigger is detected for MS originated calls with ‘*’ as the first dialed digit but not as the second dialed digit. 1. 2. 3. 4. 5. 6. 7. 8. TDP - Collected_Information DP Criteria - Conditional Category - Subscribed Interface - mobile origination Trigger Type - Home_System_Feature_Code Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - FeatureRequest INVOKE Arming Mechanism - (Note)

7 8 9 10 11 12 13 14 15 16 17 18 19

Note: This trigger type is armed as a TDP-R at the Serving MSC when the Single_Introducing_Star trigger type is not armed. The Home_System_Feature_Code trigger type is mutually exclusive with the Single_Introducing_Star trigger type. When the Home_System_Feature_Code trigger type is armed, the address associated with this trigger type is the address of the HLR for the served subscriber. 5.2.3.4.5 Double_Introducing_Pound

20 21 22 23 24 25 26 27 28 29 30 31 32

The Double_Introducing_Pound trigger is detected for MS originated calls having ‘##’ as the first two dialed digits. 1. 2. 3. 4. 5. 6. 7. 8. TDP - Collected_Information DP Criteria - Conditional Category - Subscribed Interface - mobile origination Trigger Type - Double_Introducing_Pound Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - OriginationRequest INVOKE Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., orreq)

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

BCSM Transitions

7-28

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

5.2.3.4.6

Single_Introducing_Pound

The Single_Introducing_Pound trigger is detected for MS originated calls having ‘#’ as the first dialed digit but not as the second dialed digit. 1. 2. 3. 4. 5. 6. 7. 8. TDP - Collected_Information DP Criteria - Conditional Category - Subscribed Interface - mobile origination Trigger Type - Single_Introducing_Pound Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - OriginationRequest INVOKE Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., orreq)

5.2.3.4.7

Revertive_Call

The Revertive_Call trigger is detected when the dialed digits are equal to the MS’s mobile directory number (or MIN if the MDN is not available). 1. 2. 3. 4. 5. 6. 7. 8. TDP - Collected_Information DP Criteria - Conditional Category - Subscribed Interface - mobile origination Trigger Type - Revertive_Call Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - OriginationRequest INVOKE Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., orreq)

PPC TIA/EIA/IS-771.7 Modifications

7-29

BCSM Transitions

TIA/EIA/IS-826

5.2.3.4.8

K_Digit 1

1 2 3 4 5 6 7 8

Sixteen distinct and independent K_Digit triggers are defined for values of K from 0 to 15. For values of K from 0 to 14, the associated K_Digit trigger is detected if the MS dialed digits are precisely K digits in length. The 15-Digit K_Digit trigger is detected if the MS dialed digits are at least 15 digits in length. 1. 2. 3. 4. 5. 6. 7. 8. TDP - Collected_Information DP Criteria - Conditional Category - Subscribed Interface - mobile origination Trigger Type - K_Digit Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - OriginationRequest INVOKE Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., orreq)

9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

5.2.3.4.9

Local_Call

24 25 26 27 28 29 30

The Local_Call trigger is detected when the digits dialed are recognized as a local call according to the dialing plan in use. 1. 2. 3. 4. 5. 6. 7. 8. TDP - Analyzed_Information DP Criteria - Conditional Category - Subscribed Interface - mobile origination Trigger Type - Local_Call Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - OriginationRequest INVOKE Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., orreq)

31 32 33 34 35 36 37 38 39 40 41 42 43 44 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

BCSM Transitions

7-30

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

5.2.3.4.10

Intra_LATA_Toll_Call

The Intra_LATA_Toll_Call trigger is detected when the digits dialed are recognized as an intra-LATA toll call according to the dialing plan in use. 1. 2. 3. 4. 5. 6. 7. 8. TDP - Analyzed_Information DP Criteria - Conditional Category - Subscribed Interface - mobile origination Trigger Type - Intra_LATA_Toll_Call Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - OriginationRequest INVOKE Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., orreq)

5.2.3.4.11

Inter_LATA_Toll_Call

The Inter_LATA_Toll_Call trigger is detected when the digits dialed are recognized as an inter-LATA toll call according to the dialing plan in use. 1. 2. 3. 4. 5. 6. 7. 8. TDP - Analyzed_Information DP Criteria - Conditional Category - Subscribed Interface - mobile origination Trigger Type - Inter_LATA_Toll_Call Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - OriginationRequest INVOKE Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., orreq)

PPC TIA/EIA/IS-771.7 Modifications

7-31

BCSM Transitions

TIA/EIA/IS-826

5.2.3.4.12

World_Zone_Call

1 2 3 4 5 6 7

The World_Zone_Call trigger is detected when the digits dialed are recognized as a call to a World Zone different from the World Zone in which the call has originated (as defined in ITU-T Rec. E.164) according to the dialing plan in use. 1. 2. 3. 4. 5. 6. 7. 8. TDP - Analyzed_Information DP Criteria - Conditional Category - Subscribed Interface - mobile origination Trigger Type - World_Zone_Call Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - OriginationRequest INVOKE Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., orreq)

8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

5.2.3.4.13

International_Call

23 24 25 26 27 28 29

The International_Call trigger is detected when the digits dialed are recognized as an international call according to the dialing plan in use. 1. 2. 3. 4. 5. 6. 7. 8. TDP - Analyzed_Information DP Criteria - Conditional Category - Subscribed Interface - mobile origination Trigger Type - International_Call Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - OriginationRequest INVOKE Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., orreq)

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

BCSM Transitions

7-32

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

5.2.3.4.14

Unrecognized_Number

The Unrecognized_Number trigger is detected when the digits dialed are not recognized as a valid call type. 1. 2. 3. 4. 5. 6. 7. 8. TDP - Analyzed_Information DP Criteria - Conditional Category - Subscribed Interface - mobile origination Trigger Type - Unrecognized_Number Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - OriginationRequest INVOKE Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., orreq)

5.2.3.4.15

Prior_Agreement

The Prior_Agreement trigger is detected when the digits dialed match the criteria of a prior agreement. 1. 2. 3. 4. 5. 6. 7. 8. TDP - Analyzed_Information DP Criteria - Conditional Category - Subscribed Interface - mobile origination Trigger Type - Prior_Agreement Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - OriginationRequest INVOKE Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., orreq)

PPC TIA/EIA/IS-771.7 Modifications

7-33

BCSM Transitions

TIA/EIA/IS-826

5.2.3.4.16

Specific_Called_Party_Digit_String 1

1 2 3 4 5 6 7 8 9 10 11

The Specific_Called_Party_Digit_String trigger is detected when the appropriate sequence of digits is dialed according to the dialing plan in use. For example, a 3, 6, or 10 digit sequence of digits can be provisioned as the trigger. Trigger provisioning specifies whether the MSC performs some manipulation of the dialed digits (e.g., digit insertion, deletion, or translation to public numbers), or queries the SCF with the digits as dialed. The numbering plan in force should ensure that emergency service numbers are distinct from provisionable specific digit strings. 1. 2.
2.

TDP - Analyzed_Information DP Criteria - Conditional
DP Criteria -Trigger assigned (conditional). Specific called party number string.

12 13 14 15 16 17 18

3. 4. 5. 6. 7. 8.

Category - Office-based Interface - mobile origination or interoffice trunk Trigger Type - Specific_Called_Party_Digit_String Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - AnalyzedInformation INVOKE Arming Mechanism - armed as a TDP-R via office provisioning

19 20 21 22 23 24 25 26 27

5.2.3.4.17

Mobile_Termination

28 29 30 31 32 33 34 35 36

The Mobile_Termination trigger is detected when the dialed digits are called party number is determined to be a mobile directory number. 1. 2.
2.

TDP - Analyzed_Information DP Criteria - Conditional
DP Criteria -Trigger assigned (conditional), called party number identified as a mobile directory number.

37 38 39

3. 4.

Category - Office-based Interface - mobile origination or interoffice trunk

40 41 42 43 44

5. Trigger Type - Mobile_Termination 6. 7. 8. Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - LocationRequest INVOKE with the TRIGTYPE parameter set to indicate the Mobile_Termination trigger was encountered Arming Mechanism - armed as a TDP-R via office provisioning

45 46 47 48 49 50 51 52 53 54 55

1Known as Specific_Digit_String in ITU-T Q.1224.

56 57 58 59 60

BCSM Transitions

7-34

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

5.2.3.4.18

Advanced_Termination

The Advanced_Termination trigger is detected when it has been armed by the TriggerAddressList parameter received in the locreq response to a LOCREQ sent upon detection of the Mobile_Termination trigger. 1. 2.
2.

TDP - Analyzed_Information DP Criteria - Unconditional
DP Criteria -Trigger assigned (unconditional)

3. 4. 5. 6. 7. 8.

Category - Subscribed Interface - mobile origination or interoffice trunk Trigger Type - Advanced_Termination Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - AnalyzedInformation INVOKE Arming Mechanism - armed as a TDP-R via TriggerAddressList parameter in the locreq

PPC TIA/EIA/IS-771.7 Modifications

7-35

BCSM Transitions

TIA/EIA/IS-826

5.2.3.4.19

Location

1 2 3 4 5 6 7 8 9 10

The Location trigger is armed by the TriggerAddressList parameter received in the locreq response to a LOCREQ sent upon detection of the Mobile_Termination trigger. The Location trigger is detected when the dialed digits are called party number is determined to be a mobile directory number and no routing information1 is available. 1. 2.
2.

TDP - Analyzed_Information DP Criteria - Conditional
DP Criteria -Trigger assigned (conditional – called party is determined to be a mobile directory number and no routing information is available)

11 12 13

3. 4. 5. 6. 7. 8.

Category - Subscribed Interface - mobile origination or interoffice trunk Trigger Type - Location Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - LocationRequest INVOKE with TRIGTYPE parameter set to indicate the Location trigger was encountered2 Arming Mechanism - armed as a TDP-R via TriggerAddressList parameter in the locreq

14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51

1 Routing information can specify Intersystem Termination, Local Termination or PSTN

52 53 54 55 56 57 58 59 60

Termination.
2The destination address for this query is the address of the HLR associated with the dialed MS

address digits.

BCSM Transitions

7-36

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

5.2.3.4.20

Terminating_Resource_Available

The Terminating_Resource_Available trigger is detected by the Serving MSC when the MS has been paged and responded, and the alerting information is being prepared for transmission to the MS. 1. 2.
2.

TDP - Facility_Selected_and_Available DP Criteria - Conditional
DP Criteria - Trigger assigned (conditional)

3. 4. 5. 6. 7. 8.

Category - Subscribed Interface - mobile termination Trigger Type - Terminating_Resource_Available Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - FacilitySelectedAndAvailable INVOKE Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., ROUTREQ)

5.2.3.4.21

T_Busy

The T_Busy trigger is detected when the terminating access is determined to be busy (i.e., network determined user-busy). This trigger may be detected either at the Serving MSC when the calling party connection has been made and busy is detected, or at the Originating MSC when, for instance, a busy indication is received in the LocationRequest RETURN RESULT or RedirectionRequest INVOKE. 1. 2.
2.

TDP - T_Busy DP Criteria - Conditional
DP Criteria - Trigger assigned (conditional)

3. 4. 5. 6. 7.

Category - Subscribed Interface - mobile termination Trigger Type - T_Busy Fault Handling - Continue call processing (other treatments such as Default Routing or Final Treatment are for further study) TIA/EIA-41 operation - TransferToNumberRequest INVOKE (trigger is armed by mechanism other than the TriggerAddressList parameter), TBusy INVOKE (trigger is armed by the TriggerAddressList parameter) Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., ROUTREQ)

8.

PPC TIA/EIA/IS-771.7 Modifications

7-37

BCSM Transitions

TIA/EIA/IS-826

5.2.3.4.22

T_No_Page_Response

1 2 3 4 5 6 7 8 9

The T_No_Page_Response trigger is detected when a called mobile station does not respond to a page. This trigger may be detected either at the Serving MSC when the mobile station does not respond to a page, or at the Originating MSC when, for instance, a No page response indication is received in the LocationRequest RETURN RESULT or RedirectionRequest INVOKE. 1. 2.
2.

TDP - T_Busy DP Criteria - Conditional
DP Criteria - Trigger assigned (conditional)

10 11 12 13 14 15 16

3. 4. 5. 6. 7.

Category - Subscribed Interface - mobile termination Trigger Type - T_No_Page_Response Fault Handling - Continue call processing (other treatments such as Default Routing or Final Treatment are for further study) TIA/EIA-41 operation - TransferToNumberRequest INVOKE (trigger is armed by mechanism other than the TriggerAddressList parameter), TBusy INVOKE (trigger is armed by the TriggerAddressList parameter) Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., ROUTREQ)

17 18 19 20 21 22 23 24 25 26 27 28

8.

5.2.3.4.23

T_Unroutable

29 30 31 32 33 34 35 36 37

The T_Unroutable trigger is detected when a routing failure occurs when attempting to complete a call. This trigger may be detected either at the Serving MSC or at the Originating MSC when, for instance, an Unroutable indication is received in the RedirectionRequest INVOKE. 1. 2.
2.

TDP - T_Busy DP Criteria - Conditional
DP Criteria - Trigger assigned (conditional)

38 39 40 41 42 43 44

3. 4. 5. 6. 7.

Category - Subscribed Interface - mobile termination Trigger Type - T_Unroutable Fault Handling - Continue call processing (other treatments such as Default Routing or Final Treatment are for further study) TIA/EIA-41 operation - TransferToNumberRequest INVOKE (trigger is armed by mechanism other than the TriggerAddressList parameter), TBusy INVOKE (trigger is armed by the TriggerAddressList parameter) Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., ROUTREQ)

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

8.

BCSM Transitions

7-38

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

5.2.3.4.24

T_No_Answer the the the the

The T_No_Answer trigger is detected when the no-answer timer associated with terminating access expires. This trigger may be detected at the Serving MSC when calling party connection has been made and the no answer timer expires, or at Originating MSC when, for instance, a no answer indication is received in RedirectionRequest INVOKE. 1. 2.
2.

TDP - T_No_Answer DP Criteria - Conditional
DP Criteria - Trigger assigned (conditional)

3. 4. 5. 6. 7.

Category - Subscribed Interface - mobile termination Trigger Type - T_No_Answer Fault Handling - Continue call processing (other treatments such as Default Routing or Final Treatment are for further study) TIA/EIA-41 operation - TransferToNumberRequest INVOKE (trigger is armed by mechanism other than the TriggerAddressList parameter), TNoAnswer INVOKE (trigger is armed by the TriggerAddressList parameter) Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., ROUTREQ)

8.

5.2.3.4.25

Origination_Attempt_Authorized

The Origination_Attempt_Authorized trigger is detected when an MS origination indication is received and authorization is completed. 1. 2.
2.

TDP - Origination_Attempt_Authorized DP Criteria - Unconditional
DP Criteria - Trigger assigned (unconditional)

3. 4. 5. 6. 7. 8.

Category - Subscribed Interface - mobile origination Trigger Type - Origination_Attempt_Authorized Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - OriginationRequest INVOKE Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot)

PPC TIA/EIA/IS-771.7 Modifications

7-39

BCSM Transitions

TIA/EIA/IS-826

5.2.3.4.26

Initial_Termination

1 2 3 4 5 6 7 8 9 10 11

The Initial_Termination trigger is detected when it has been armed by the TriggerAddressList parameter received in the locreq response to a LOCREQ sent upon detection of the Mobile_Termination trigger. 1. 2.
2.

TDP - Analyzed_Information DP Criteria - Unconditional
DP Criteria - Trigger assigned (unconditional)

3. 4. 5. 6. 7. 8.

Category - Subscribed Interface - mobile origination or interoffice trunk Trigger Type - Initial_Termination Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - AnalyzedInformation INVOKE Arming Mechanism - armed as a TDP-R via TriggerAddressList parameter in the locreq

12 13 14 15 16 17 18 19 20 21 22 23 24 25

5.2.3.4.27

Calling_Routing_Address_Available

26 27 28

The Calling Routing_Address_Available trigger is detected when a routing address and call type have been determined for an outgoing call. 1. 2.
2.

29 30 31 32 33 34 35 36 37 38

TDP - Analyzed_Information DP Criteria - Unconditional
DP Criteria - Trigger assigned (unconditional)

3. 4. 5. 6. 7. 8.

Category - Subscribed Interface - mobile origination Trigger Type - Calling_Routing_Address_Available Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - AnalyzedInformation INVOKE Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., locreq)

39 40 41 42 43 44 45 46 47 48 49 50 51

5.2.3.4.28

Called_Routing_Address_Available

52 53

The Called_Routing_Address_Available trigger is detected when a routing address and call type have been determined for an incoming call 1. TDP - Analyzed_Information

54 55 56 57 58 59 60

BCSM Transitions

7-40

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

2.
2.

DP Criteria - Unconditional
DP Criteria - Trigger assigned (unconditional)

3. 4. 5. 6 7. 8.

Category - Subscribed Interface - mobile origination or interoffice trunk Trigger Type - Called_Routing_Address_Available Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA Operation - AnalyzedInformation INVOKE Arming Mechanism - armed as a TDP-R via TriggerAddressList parameter in the locreq

5.2.3.4.29

O_Answer

The O_Answer trigger is detected when an answer indication is received via the terminating BCSM. 1. 2.
2.

TDP - O_Answer DP Criteria - Unconditional
DP Criteria - Trigger assigned (unconditional)

3. 4. 5. 6. 7. 8.

Category - Subscribed Interface - mobile origination or interoffice trunk Trigger Type - O_Answer Fault Handling - Continue call processing (other treatments such as Default Routing or Final Treatment are for further study) TIA/EIA-41 operation - O_Answer INVOKE Arming Mechanism - armed as a TDP-N via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., locreq)

PPC TIA/EIA/IS-771.7 Modifications

7-41

BCSM Transitions

TIA/EIA/IS-826

5.2.3.4.30

O_Disconnect

1 2 3 4 5 6 7 8

The O_Disconnect trigger is detected when either the call is cleared from the terminating BCSM or the originating facility disconnects, or the MSC releases the call leg. 1. 2.
2.

TDP - O_Disconnect DP Criteria - Unconditional
DP Criteria - Trigger assigned (unconditional)

9 10

3. 4. 5. 6. 7. 8.

Category - Subscribed Interface - mobile origination or interoffice trunk Trigger Type - O_Disconnect Fault Handling - Continue call processing (other treatments such as Default Routing or Final Treatment are for further study) TIA/EIA-41 operation - O_Disconnect INVOKE Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., locreq)

11 12 13 14 15 16 17 18 19 20 21 22 23 24

5.2.3.4.31

T_Answer

25 26 27 28 29 30 31 32 33

The T_Answer trigger is detected when an answer indication is received from the terminating facility. 1. 2.
2.

TDP - T_Answer DP Criteria - Unconditional
DP Criteria - Trigger assigned (unconditional)

34 35

3. 4. 5. 6. 7. 8.

Category - Subscribed Interface - mobile termination or interoffice trunk Trigger Type - T_Answer Fault Handling - Continue call processing (other treatments such as Default Routing or Final Treatment are for further study) TIA/EIA-41 operation - T_Answer INVOKE Arming Mechanism - armed as a TDP-N via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., locreq)

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

BCSM Transitions

7-42

PPC TIA/EIA/IS-771.7 Modifications

TIA/EIA/IS-826

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 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

5.2.3.4.32

T_Disconnect

The T_Disconnect trigger is detected when either the call is cleared from the originating BCSM or the terminating facility disconnects, or the MSC releases the call leg. 1. 2.
2.

TDP - T_Disconnect DP Criteria - Unconditional
DP Criteria - Trigger assigned (unconditional)

3. 4. 5. 6. 7. 8.

Category - Subscribed Interface - mobile termination or interoffice trunk Trigger Type - T_Disconnect Fault Handling - Continue call processing (other treatments such as Default Routing or Final Treatment are for further study) TIA/EIA-41 operation - T_Disconnect INVOKE Arming Mechanism - armed as a TDP-R via subscriber profile (e.g., regnot) or dynamically for a single call (e.g., locreq)

5.2.3.4.33

Locally_Allowed_Specific_Digit_String

The Locally_Allowed_Specific_Digit_String trigger is detected when the appropriate sequence of digits is dialed according to the dialing plan in use, and the dialed digit string is a locally allowed number. 1. 2.
2.

TDP - Origination_Attempt_Authorized DP Criteria - Conditional
DP Criteria - Trigger assigned (conditional). Specific dialed digit string is a locally allowed number.

3. 4. 5. 6. 7. 8.

Category - Office-based Interface - mobile origination Trigger Type - Locally_Allowed_Specific_Digit_String Fault Handling - Final treatment (other treatments such as Default Routing or Continue Call Processing are for further study). TIA/EIA-41 operation - OriginationRequest INVOKE Arming Mechanism - armed as a TDP-R via office provisioning

PPC TIA/EIA/IS-771.7 Modifications

7-43

BCSM Transitions

TIA/EIA/IS-826

1

Annex D

(informative)

Notes on Trigger Concepts and Usage

2 3 4 5 6

This annex is informative and is not considered part of this Interim Standard.

7 8 9

Dynamic Trigger Arming Mechanism
(TIA/EIA/IS-771, page 7-123)

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33

A subscriber’s trigger profile is stored in the HLR. This profile is considered to be “static” because it changes “slowly” if at all. The subscriber’s trigger profile remains the same unless the subscription options change so that a new trigger is required or an existing trigger is no longer required. That is, it remains the same unless the subscriber adds
or deletes a triggered service from the profile, or turns on or off one of the services that are subscribed to. It is this “static” profile that is dynamically geographically placed as the

subscriber roams and is served by different MSCs. Subscribed triggers may be dynamically armed by service logic for the call leg. When dynamic trigger arming is used, any previously armed triggers are disarmed before the new triggers are armed. These new triggers apply only for the remainder of the call in progress or until a subsequent dynamic trigger arming event occurs. A subscriber’s trigger profile
may be modified for a given call instance without affecting the “static” profile. These modifications to the profile do not survive after the current call. On release of the call, all such modifications disappear. This is called “dynamic” trigger arming. This may be done in two ways. In pre-WIN systems, it is done using the OriginationTriggers ORIGTRIG and

TerminationTriggers TERMTRIG parameters. In WIN-capable systems, it may also be done using the TriggerAddressList TRIGADDRLIST parameter. The TriggerAddressList parameter may also be used to dynamically arm triggers when the subscriber profile is not available or is not applicable. For example, the Initial_Termination and Advanced_Termination triggers are not included in the subscriber profile, they can only be armed dynamically via the TriggerAddressList parameter. Triggers armed on the Originating MSC for a roaming subscriber when the Serving System is not WIN-capable can only be armed dynamically by the TriggerAddressList parameter. Profile triggers are not applicable to forwarded calls; WIN triggers for forwarded call legs can be armed by the TriggerAddressList. Subscribed WIN Triggers may be explicitly disarmed by service logic via the TriggerAddressList parameter. Upon receipt of this parameter, all previously armed subscribed WIN triggers for that call leg will be disarmed for the remainder of the call in progress. Use of this parameter does not affect the subscriber's profile. The subscriber's profile triggers are used for the next new call origination or termination.
When the TriggerAddressList parameter is utilized to dynamically arm triggers (e.g. triggers armed for call forwarding), such triggers overwrite previously armed triggers. Thus, only these triggers apply for the remainder of the call leg instance. This approach is consistent with the treatment of IN dynamically armed EDPs (i.e. when new EDPs are armed dynamically, any previously armed EDPs are disarmed). This approach is also consistent with the treatment of origination and termination triggers in pre-WIN systems.

34 35 36 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 D: Notes on Trigger Concepts and Usage

7-44

PPC TIA/EIA/IS-771.7 Modifications