C.1 Introduction
C.2 BCSM TDPs and TDP criteria
C.2.1 Unconditional TDPs
C.2.2 Conditional TDPs
C.2.3 Trigger criteria combinations
C.2.4 Trigger criteria priorities

Annex C (informative): Trigger Detection Points (TDPs) and trigger criteria for the CS1 core INAP

C.1 Introduction

This annex provides for the Core INAP information on the applicability of the CS1 Detection Points (DPs) as Trigger Detection Points (TDPs) and on the applicability of trigger criteria that are listed and clarified in Recommendation Q.1219, � 6.3.3.3.
This annex has no intention to be restrictive on the use of the EventTypeBCSM parameter in the InitialDP operation. All values of the EventTypeBCSM are possible.
In addition the indicated applicability of trigger criteria to the TDPs are considered as being useful in the context of Core INAP and it is not intended to be restrictive.
Note, however, that the assignment of DP to a TDP on either a customer/trunkgroup, private facility or office basis may have an impact on the memory and real time performance requirements of the CCF/SSF.
Note further that the applicability of DP criteria at a given DP depends on when call processing is available and how long it is retained. The IN Core INAP places no requirements on equipment suppliers in this area. If network and service providers plan to implement IN CS1 services in a multi-supplier environment, they should consider formulating such requirements to ensure consistent implementations across supplier equipments. Such requirements should be considered carefully so as not to adversely impact memory and real-time performance of CCF/SSF processing.
Finally note that the relationship between DP criteria and minimum parameter population rules is not defined in this version of the ETS.

C.2 BCSM TDPs and TDP criteria

The following classification is used.

C.2.1 Unconditional TDPs

The unconditional TDPs can be used by itself, related to DPs of the BCSM without any other criterion to be satisfied at the TDP before informing the SCF that the TDP was encountered.
The unconditional TDPs can be:

customer based;
trunkgroup based;
private facility (e.g. Centrex) based.

The unconditional TDPs are listed in table C.1.
Table C.1

A "X" for the selected DPs means really the point in call when the BCSM should be suspended. E.g. for DP3 the information should only be analyzed whereafter, irrespective the value of the analyzed information the BCSM should be suspended.

C.2.2 Conditional TDPs

Related to DPs with additional trigger criteria as listed in the table C.2.
The entries in the table can be:

Customer Based;
Trunkgroup Based;
Private Facility Based;
Office Based.

Table C.2

If a criteria is marked with an "X" for a DP, then this means that a conditional TDP which is armed at the DP may require the criteria as listed in the table to be satisfied before informing the SCF that the TDP was encountered. E.g. a conditional TDP at DP1 may require the class of service criteria to be satisfied before the SCF is informed that the TDP was encountered.
If a criteria is marked with an "O" for a DP, then this means that it is implementation dependent if the criteria specific information is still present at that DP because not all suppliers may retain this information for the duration of the call/attempt. If the information is still present, the treatment is the same as a criteria marked with a "X".
Concerning impact on memory and real time performance, see the notes in the introduction.
DP of the OBCSM and TBCSM

DP1	OriginatingAttemptAuthorized

DP2	CollectedInfo

DP3	AnalyzedInformation

DP4	RouteSelectFailure

DP5	OCalledPartyBusy

DP6	ONoAnswer

DP7	OAnswer

DP8	OMidCall

DP9	ODisconnect

DP10	OAbandon

DP11	Reserved

DP12	TerminatingAttemptAuthorized

DP13	TCalledPartyBusy

DP14	TNoAnswer

DP15	TAnswer

DP16	TMidCall

DP17	TDisconnect

DP18	TAbandon

C.2.3 Trigger criteria combinations

A particular conditional TDP may require a combination of the applicable criteria to be checked before informing the SCF that the TDP was encountered.
Criteria may be combined using the:

AND function (e.g. at DP3, initiate an SCF enquiry if "Class of Service" = international call barred AND "Nature of Address" = international);
OR function (e.g. at DP3, initiate an SCF enquiry if "Called Party Number" = 831 or "Called Party Number" = 836);
NOT function (e.g. at DP3, initiate an SCF enquiry if "Called Party Number" is NOT = 831).

The criteria combinations to be checked for a particular TDP is to be specified by means of management procedures applicable for the CCF/SSF.

C.2.4 Trigger criteria priorities

Multiple TDP-Rs may be armed at the same DP, each TDP-R being either an unconditional or a conditional TDP. Each TDP-R will have an associated set of criteria (i.e. conditions specific to the particular TDP-R that shall be met before the SCF is informed that the TDP is encountered). The priority of the TDP-Rs at a DP is to be specified by means of management procedures applicable for the CCF/SSF.
During the processing of TDP-Rs at a DP, the SSF has to check the set of criteria associated with each TDP-R in descending order of priority until either the set of criteria for a particular TDP-R are met (resulting in informing the SCF) or all sets of criteria have been checked and none have been met.

INAP Contents Page