TIF Features

3 TIF Features

This chapter describes the EAGLE 5 features that use the Triggerless ISUP Framework (TIF) and the Numbering Plan Processor (NPP) to process ISUP messages:

TIF Number Portability (TIF NP)
TIF SCS Forwarding (TIF SCS)
TIF Number Substitution (TIF NS)
TIF Simple Number Substitution (TIF SNS)
TIF Additional Subscriber Data (TIF ASD)
TIF Generic Routing Number (TIF GRN)
TIF Blacklist Features
- TIF Subscriber CgPN Blacklist (TIF Subscr CgPN Blacklist)
- TIF Range CgPN Blacklist
- TIF Selective Screening
- TIF Redirecting Number Based Blacklisting
- TIF Generic Name Based Screening
- TIF Linkset Based Blacklisting

TIF Number Portability Feature

The TIF Number Portability (TIF NP) feature, along with the Numbering Plan Processor (NPP) the Service Portability feature, and the Triggerless ISUP Framework (TIF), provide the following capabilities:

Complex prefix usage, where prefixes can be used to customize actions
Non-NAI-compliant digit handling
Complex outgoing digit formats
Calling number portability
Concurrent Release and Relay support
Circular route prevention (CRP)
IAM/SAM splitting
Service Portability (S-Port)

The TIF NP feature is built upon the services provided by TIF and NPP to support ISUP messages.

TIF NP provides the following functions:

Definition of feature-specific pre-NPP processing to be performed by TIF
Service Action specification (including Service Action names and precedence)
Service Action Handlers
Feature-specific post-NPP processing, if needed

TIF NP Message Flows

The following figure shows basic TIF NP CdPN Relay use cases.

Figure 3-1 ISUP Message Flows for TIF NP CdPN Relay

The following figure shows TIF NP Relay cases where NM bits are used in the ISUP IAM message. In the sequence diagrams, the NM bits are shown as binary values. Refer to Use of NM Bits for details on the use of NM bits.

Note:

Use of NM bits in the IAM message is an optional part of TIF NP.

Figure 3-2 ISUP Message Flows for TIF NP CdPN Relay, with Optional NM Bits

The following figure shows basic TIF NP CgPN portability use cases.

Figure 3-3 ISUP Message Flows for TIF NP CgPN Portability

A TIF NP CgPN use case is shown in the following figure for a TIFCGPN, TIFCGPN2, or TIFCGPN3 NPP service when NPRELAY (in TIF, TIF2, or TIF3) and CGPNNP (in TIFCGPN, TIFCGPN2, or TIFCGPN3) Service Actions are provisioned and RTDB lookup is performed on both CdPN and CgPN. A TIFCGPN, TIFCGPN2, and TIFCGPN3 NPP service is invoked by the corresponding TIF, TIF2, or TIF3 NPP Service.

Figure 3-4 ISUP Message Flows for TIF NP CgPN with NPRELAY and CGPNNP

The following figure shows basic TIF NP Release use cases.

Figure 3-5 ISUP Message Flows for TIF NP Release

The following figure shows TIF NP Release use cases, with use of NM bits. See Use of NM Bits for details on the use of NM bits.

Figure 3-6 ISUP Message Flows for TIF NP Release, with Optional NM bits

The following figure shows Circular Route Prevention use cases. In these cases, subscriber X is ported from network A to network B. Network A’s NP database has the correct entry indicating that subscriber X is ported, but network B has incorrect routing information, indicating that subscriber B still belongs to network A. Subscriber Y belongs to network A. In the use case, subscriber Y calls subscriber X.

Figure 3-7 ISUP Message Flows for TIF CRP

A basic Service Portability use case is shown in the following figure. In this example, the Service Portability feature is turned on and the TIFOPTS SPORTRELAY option has been configured for Service Portability. If the subscriber is an own-network GSM or IS41 subscriber, then the RTDB GRN is used for the RN.

Figure 3-8 ISUP Message Flows for Service Portability

A use case using both the NPRLS and NPRELAY Service Actions is shown in the following figure. In this example, only OLO subscribers are released; own-network subscribers are relayed. The Service Actions would be set to NPRLS and NPRELAY. The NPTYPERLS configuration option is set to RN and the NPTYPERLY configuration option is set to SP.

TIF NP Configuration Options

TIF Configuration Options indicates the TIF configuration options that can be used specifically by TIF NP. TIF NP can also use other options that are available to any TIF feature.

TIF NP Protocol Handling

TIF NP protocol handling provides the following functions:

TIF NP-specific pre-NPP processing
TIF NP Service Action Handlers
Post NPP-processing

TIF Pre-NPP Processing for TIF NP

TIF decodes the incoming MSU and passes the following information to NPP:

Conditioned CgPN
Number of Country Code digits in CgPN
Incoming NM bits

TIF NP Service Action Handlers

TIF NP provides Service Action Handlers for the NPP Service Actions that are specific to TIF NP. TIF and NPP perform the following functions for the TIF NP feature:

RTDB lookup
Interpretation of results from RTDB lookups
NPP processing of Service Actions that are used for TIF NP

Table 3-1 provides a summary of the Service Actions used for TIF NP.

Table 3-1 Summary of TIF NP Service Actions

Service Action	Description	Function	Precedence
CRP	Circular Route Prevention	Performs an RTDB lookup on the CdPN and attempts to detect a circular route.	92
NPNRLS	Number Portability Release on No Match	Performs an RTDB lookup on the CdPN and indicates release behavior on an unsuccessful lookup.	91
NPRELAY	Number Portability Relay	Performs an RTDB lookup on the CdPN and indicates relay behavior.	80
NPRLS	Number Portability Release on Match	Performs an RTDB lookup on the CdPN and indicates release behavior on a successful lookup.	80
CgPNSvcRqd CgPNNPRqd	Calling Number Lookup	Performs an RTDB lookup on the CgPN.	80

Relationships Between TIF NP Service Actions

The following figure shows the relationships between NP Service Actions. The figure shows the precedence values (p) and shows which Service Actions are mutually exclusive in terms of Action Set configuration. In the diagram, Service Actions that are connected by lines are mutually exclusive. Service Actions that can be terminating actions are marked with asterisks.

Figure 3-9 NP Service Action Precedence

The mutual exclusion relationships can be explained as follows:

NPRELAY and NPRLS – For the successful NP lookup case, must choose between Relay or Release
CgPNSvcRqdCgpnNPRqd and NPRLS – CgPNNPRqdCgPNSvcRqd implies Relay behavior.

The precedence relationships can be explained as follows:

CRP – CRP should be first since it is a special case and a terminating action.
NPNRLS – NPNRLS is a special condition and a terminating action.
NPRLS – Normal Release case; can be same precedence as normal Relay cases since they are mutually exclusive and cannot appear in the same action set with CgpnSvcRqd.
NPRLS – NPRELAY can be the same precedence. The NP lookup status determines whether or not the second Service Action needs to be executed.
CgPNSvcRqd, NPRELAY – normal relay case

The following principles apply to precedence relationships:

Special NP Release cases are given higher precedence.
Handlers that need to override conditions set by other handlers must be given lower precedence

The mutual exclusion relationships are enforced during EAGLE configuration for TIF NP.

RN, SP, and DFLTRN Handling

The RN and SP values are set depending on the entity type retrieved from the RTDB and the values of the NPTYPE configuration options for NP type (NPTYPERLY, NPTYPERLS and NPTYPECGPN) and the SPFILL and DFLTRN configuration options. The NPTYPE option isoptions for NP type are used as part of the matching criteria to determine when the RTDB search is considered a success.

If a match is found and the Entity Type is RN, then RN digits are inserted into the outbound field.

If a match is found and the Entity Type is SP, then SP digits are inserted into the outbound field or the DFLTRN option digit string can be used instead of actual SP digits.

The DFLTRN and SPFILL configuration option allowsoptions allow a single digit string to be inserted instead of the actual SP digits to identify ‘in-network subscribers’. There may be different SPs in the RTDB for use by G-Port or other EAGLE features, but a single digit string is needed for TIF. The DFLTRN string is considered ‘routing digits’. When a DFLTRN string is provisioned, the RN Formatting Action is used to encode ‘routing digits’ (RN or DFLTRN) in the outbound digits. The SPFILL option is used to indicate how the SP is populated when DFLTRN is used for the RN. If the SPFILL option value is ON, RTDB network entity digits are used for the SP. If the SPFILL option value is OFF, the SP is not populated.

The RN Formatting Action inserts the ’routing digits” into the outbound digits (either be the actual RN or the DFLTRN string).

The SP Formatting Action inserts the SP digits into the outbound digits.

Note:

If the IGM Feature is turned on, or the Service Portability feature is enabled, Entity Type is RN, and portability type (PT) is zero, then the Entity Type is treated as SP (in-network subscriber).

Table 3-2 summarizes the rules for determining the outbound RN and SP.

Table 3-2 Rules for Determining Outbound RN and SP

Case	NPTYPE	RTDB Entity Type	DFLTRN	SPFILL	RN	SP
1	RN, RNSP, RNSPDN, ANY, ALL	RN	N/A	N/A	Entity data digits from the RTDB	No data
2	SP	RN	N/A	N/A	No data	No data
3	RN	SP	N/A	N/A	No data	No data
4	SP, RNSP, RNSPDN, ANY, ALL	SP	Null	N/A	No data	Entity data digits from the RTDB
5	SP, RNSP, RNSPDN, ANY, ALL	SP	Not Null	ON	DFLTRN	Entity data digits from the RTDB
6	SP, RNSP, RNSPDN, ANY, ALL	SP	Not Null	OFF	DFLTRN	No data
6 7	SP, RN, RNSP, RNSPDN, ANY, ALL	Not RN, Not SP	N/A	N/A	No data	No data

Use of NM Bits

The Number Portability Forward Call Indicator NM bit values shown in Table 3-3 are used in ISUP IAM messages to indicate CdPN portability status.

Table 3-3 NM Bits Values

NM Bits Value	Meaning
00	"Without indication" - DPC is out-of-network, or no RTDB lookup performed
01	"Query not performed" - DPC is in-network, RTDB lookup was not performed
10	"Query performed, not ported" - DPC is in-network, unsuccessful RTDB lookup
11	"Query performed, ported" - DPC is in-network, successful RTDB lookup

Use of NM Bits is optional, and is controlled by the TIFOPTS NPFLAG configuration option and by the destination-based NPRST configuration option for the DPC of the incoming message.

TIF determines the value of the NM Bits in the incoming message. The following CdPN-based Service Action Handlers inspect the incoming NM Bits value: NPRELAY, NPRLS, NPNRLS, and CRP.

If TIFOPTS NPFLAG=NM and the incoming NM Bits value is 10 or 11, the Service Action Handler ends processing immediately.
If TIFOPTS NPFLAG=NM and the NPRELAY Service Action Handler performs an RTDB lookup on the CdPN, TIF uses the NM Bits value indicated by the NPRELAY processing to determine if the NM Bits value needs to be updated in the outgoing IAM message.
If TIFOPTS NPFLAG=NM, the incoming NM Bits value is 01, the NPRLS Service Action Handler performs an RTDB lookup on the CdPN, and no match is found, the NPRLS Service Action Handler sends a RELEASE message with no Redirection Number and the Release Cause set to the value of the TIFOPTS RCAUSENP option.

Note:

The configuration options and the NM Bits apply only to the CdPN, not to the CgPN. Therefore, the CgPNSVCRQD Service Action Handler does notCgPNSVCRQD and CGPNNP Service Action Handlers do not look at the NM bits. The NM Bits apply only for ITU ISUP messages when TIFOPTS NPFLAG=NM.

If the TIFOPTS NPFLAG configuration option is set to NM and the outgoing message NM bits are not 00, the Destination table is searched for the DPC from the IAM message.

If the NPRST option valued in the Destination table entry is ON, the NM bits in the outgoing message are set to 00 ("without indication").

If the NPRST option valued in the Destination table entry is OFF, the NM bits in the outgoing message are not set to 00.

Service Portability for TIF NP

With the Service Portability feature, the subscriber has ported to a different network technology with the same service provider. The Service Portability use case is very similar to number portability with the exception of what is used as the prefix for the Called Party digits. Service Portability is applicable to TIF Number Portability Relay and TIF Number Portability Release, and is handled by the NPRELAY and the NPRLS Service Actions.

Service Portability is controlled by the Service Portability feature P/N 893-0343-01. The SPORTRELAY and SPORTRLS options in the TIFOPTS table control the mode of the Service Portability for NP Relay and NP Release. These options have the following values:

NONE - Apply standard NP processing for own-network GSM and IS41 subscribers.
GSM - Use the GSM Service Portability prefix for GSM own-network subscribers, and apply standard NP processing for own-network IS41 and OLO subscribers.
IS41 - Use the IS41 Service Portability prefix for Is41 own-network subscribers, and apply standard NP processing for own-network GSM and OLO subscribers.
ALL - Use the GSM Service Portability prefix for GSM own-network subscribers, use the IS41 Service Portability prefix for IS41 own-network subscribers, and apply standard NP processing for OLO subscribers.

The determination of whether or not to invoke Service Portability depends on the subscriber’s Entity type and the Portability Type. The subscriber is considered as an own-network IS41 subscriber if the Entity type is RN and the Portability Type is 0 (RN/PT=0). The subscriber is considered as an own-network GSM subscriber if the Entity type is SP with any Portability Type. In the case of RN/PT=0, the RN for this subscriber is actually considered to be the SP (the IS-41 HLR address).

After the Service Portability feature is considered to be applicable, the Service Action attempts to use the subscriber GRN data in the RTDB as the Service Portability prefix. This GRN is populated in the RN Formatting Action value as the Service Portability prefix. The TIFOPTS SPFILL option value determines the content of the SP. If the SPFILL option value is ON, then the RTDB Network Entity digits are used for the .SP. If the SPFILL option value is OFF, then the SP value is null. Table 3-4 shows how the RN and SP are set according to the various scenarios. In all the cases, it is assumed that the Service Portability feature (893-0343-01) is ON.

Table 3-4 TIF NP Service Portability Digit Formatting Scenarios

		Subscriber Type Returned form RTDB
		Own IS41	OLO	Own GSM
TIFOPTS Service Portability Option Value	NONE	No changes from default TIF-NP behavior	No changes from default TIF-NP behavior	No changes from default TIF-NP behavior
	GSM	No changes from current behavior	No changes from default TIF-NP behavior	RN=GRN
	IS41	RN=GRN	No changes from default TIF-NP behavior	No changes from default TIF-NP behavior
	ALL	RN=GRN	No changes from v behavior	RN=GRN

If the GRN is not present in the RTDB, then UIM 1426, “S-Port: Missing GRN for srvc prtd subs” is generated indicating that Service Portability could not be applied due to missing Service Portability data. The behavior of the Service Action is as follows for the case that S-Port applies and the GRN does not exist in the RTDB:

For the NPRELAY Service Action, the IAM message is routed with the CdPN unmodified, unless CDIAL is indicated to cause Formatting Action execution.
For the NPRLS Service Action with NP type of RN, SP, RNSP, or RNSPDN, the IAM message is routed with the CdPN unmodified, unless CDIAL is indicated to cause Formatting Action execution.
For the NPRLS Service Action with NP type of ALL or ANY, a REL message is sent with no redirection number.

Using NPRELAY and NPRLS in One Service Action Set

In a Service Action set containing both the NPRELAY and NPRLS Service Actions, TIF will perform Service Action processing in the order in which the Service Actions are provisioned (the lower-numbered sax configuration parameter specifies the first Service Action to be executed). If the first Service Action (NPRELAY or NPRLS) has a successful database match, then the second Service Action (NPRLS or NPRELAY) will not be executed. If the first Service Action (NPRELAY or NPRLS) does not have a successful database match, then the second Service Action (NPRLS or NPRELAY) is executed.

The TIFOPTS NPTYPERLY option will determine the Network Entity type behavior for the NPRELAY Service Action, and the The TIFOPTS NPTYPERLS option will determine the Network Entity type behavior for the NPRLS Service Action. This s allows the NPRELAY and NPRLS Service Actions to be configured for non-ported subscribers and ported subscribers independently. See the use case in Table 3-5. The following table has a list of possible combined Service Actions scenarios for NPRELAY and NPRLS. Scenarios 1 and 4 have the same behavior, and scenarios 2 and 3 have the same behavior. If the NP type is the same for both Service Actions, the second Service Action will never get executed.

Table 3-5 Scenarios for Combining the NPRELAY and NPRLS Service Actions

Scenario	First Service Action	Second Service Action	Result
1	NPRELAY, NPTYPERLY=SP	NPRLS, NPTYPERLS=RN	NP Relay an own-network subscriber; NP Release a foreign subscriber
2	NPRELAY, NPTYPERLY=RN	NPRLS, NPTYPERLS=SP	NP Relay foreign subscriber; NP Release an own-network subscriber
3	NPRLS, NPTYPERLS=SP	NPRELAY, NPTYPERLY=RN	NP Release an own-network subscriber; NP Relay a ported subscriber
4	NPRLS, NPTYPERLS=RN	NPRELAY, NPTYPERLY=SP	NP Release a foreign subscriber; NP Relay an own-network subscriber

NPRELAY Service Action Handler

The NPRELAY Service Action Handler performs an RTDB lookup on the conditioned CdPN digit string and indicates Relay behavior.

The NPRELAY and NPRLS Service Actions are mutually exclusive in an Action Set.

Configuration Options Used

The TIFOPTS NPTYPERLYNPTYPE configuration option indicates the conditions that are used for a successful RTDB match.

The destination-based NPRST configuration option and the TIFOPTS NPFLAG configuration option indicate when and how the NM bits should be processed.

The value of the TIFOPTS DFLTRN option, if provisioned, is used to populate the RN on a successful match on SP.

The TIFOPTS SPFILL option indicates whether SP should be populated when the DFLTRN value or the GRN data is used for the RN value.

The TIFOPTS SPORTRELAY option indicates the Service Portability processing for the NPRELAY Service Action (none, GSM, IS41, all).

Action Performed

If the NPRLS Service Action has already been executed with a successful match, no NPRELAY processing is performed.

This Service Action Handler uses the incoming NM bits to determine if a lookup has already been performed. See Use of NM Bits.

If the TIFOPTS NPFLAG option is set to NM and the NM bits indicate that a lookup has already been performed, then the Service Action Handler returns immediately.

If a lookup has not already been performed, the NPRELAY Service Action Handler performs an RTDB lookup on the CdPN digit string. RN and SP can be found as a successful match. RN and SP entities are processed as described in RN, SP, and DFLTRN Handling.

Interpretation of lookup results is described in Interpreting Results of an RTDB Lookup.

Depending on the Formatting Action configuration for the selected rule, the updated RN or SP can be used during CdPN formatting by NPP.

Service portability processing is applied as described in Service Portability for TIF NP when the Service Portability feature is ON, and:

Network Entity type is RN/PT=0 and the SPORTRELAY option value is IS41 or ALL
Network Entity type is SP and the SPORTRELAY option value is GSM or ALL

If the NPTYPERLY configuration option is RNSPDN, ANY, or ALL and a match is found on a non-RN/SP condition, then the RN or SP entities are not used. The end result is that NPP performs formatting of the outgoing CdPN.

The NPP Formatting Action processing will be skipped on an unsuccessful lookup. One way to force formatting of the outgoing CdPN, even after an unsuccessful lookup, is to configure the CDIAL Service Action.

On a successful lookup, where DN and entity data was found, the CdPN message parameter is changed to the ported number and the message is relayed to the recipient network.

On a successful lookup, where DN was found but entity data was not found (NPTYPERLY=ALL), the CdPN is unchanged and the message is relayed to the original destination.

The decoded NM result is used to determine if the NM bits need to be set in the outgoing IAM message.

Terminating Action?

This is not a terminating action.

NPRLS Service Action Handler

The NPRLS Service Action Handler performs a lookup on the conditioned CdPN digit string and indicates Release behavior on a successful lookup.

This Service Action should be used after the CRP Service Action.

The NPRELAY and NPRLS Service Actions are mutually exclusive in an Action Set.

Configuration Options Used

The TIFOPTS NPTYPERLSNPTYPE configuration option indicates the conditions used for a successful match.

The TIFOPTS RNRQD configuration option indicates if a Redirection Number should be included in the Release message.

The TIFOPTS RLCOPC option indicates whether the destination-based RCAUSE configuration option value or the TIFOPTS RCAUSENP configuration option value is used as the Release Cause to be included in the Release message.

The RCAUSENP configuration option indicates the Release Cause to be included in the Release message.

The value of the TIFOPTS DFLTRN option, if provisioned, is used to populate the RN on a successful match on SP.

The destination-based NPRST configuration option and the TIFOPTS NPFLAG configuration option indicates if the NM bits should be processed, and if a Release message should be generated if a DN is-not-found.

The TIFOPTS SPORTRLS option indicates the Service Portability processing for the NPRLS Service Action (none, GSM, IS41, all).

The TIFOPTS SPFILL option indicates whether SP should be populated when the DFLTRN value or the GRN data is used for the RN value.

Action Performed

If the NPRELAY Service Action has already been executed with a successful match, no NPRLS processing is performed.

This Service Action Handler uses the incoming NM bits to determine whether a lookup has already been performed. See Use of NM Bits.

If the NPFLAG configuration option is set to NM and the NM bits indicate that a lookup has already been performed, then the Service Action Handler returns immediately.

If the NM bits indicate that a lookup has not already been performed, the Service Action Handler performs an RTDB lookup on the conditioned CdPN digit string. RN or SP can be found as successful match. The RN and SP values are processed as described in RN, SP, and DFLTRN Handling.

Interpretation of lookup results is described in Interpreting Results of an RTDB Lookup.

On a match, the RNRQD option indicates whether or not a Redirection Number is included in the Release message, and the RCAUSE option or the RCAUSENP option indicates the Release Cause to be included in the Release message.

On a successful lookup, where DN and entity data was found, a Release message is sent. If the Redirection Number configuration option (RNRQD) is set to YES, then the ported number is included in the ISUP Release message.
On a successful lookup, where DN was found but entity data was not found (NPTYPERLS=ALL), a Release message is sent. If the Redirection Number configuration option (RNRQD) is set to YES, then the original CdPN is included in the ISUP Release message.

Depending on the Formatting Action configuration for the selected rule, the updated RN or SP can be used during CdPN formatting by NPP.

Service portability processing is applied as described in Service Portability for TIF NP when the Service Portability feature is ON, and:

Network Entity type is RN/PT=0 and the SPORTRLS option value is IS41 or ALL
Network Entity type is SP and the SPORTRLS option value is GSM or ALL

The Formatting Action processing will be skipped on an unsuccessful lookup. The original message is relayed using the original CdPN, unless NPFLAG=NM and a Release message is to be generated. If TIFOPTS NPFLAG=NM, the incoming NM Bits value is 01, and no match is found in the RTDB lookup on the CdPN, then the NPRLS Service Action Handler sends a Release message with no Redirection Number and the Release Cause set to the value of the TIFOPTS RCAUSENP option.

Terminating Action?

This is a terminating action in either of the following two conditions:

The NPFLAG is set to NM, lookup is not successful, and the NM bits indicate “query not performed” (binary value 01).
The lookup is successful.

NPNRLS Service Action Handler

The NPNRLS Service Action Handler performs a lookup on the conditioned CdPN digit string and indicates Release behavior on an unsuccessful lookup.

Configuration Options Used

The TIFOPTS NPTYPERLS configuration option indicates the conditions used for a successful match.

The destination-based NPRST configuration option and the TIFOPTS NPFLAG configuration option indicates when and how the NM bits should be processed.

The RCAUSEPFX configuration option indicates the Reason Cause Value to be included in a Release message.

Action Performed

This Service Action Handler uses the incoming NM bit decode result to determine if a lookup has already been performed.

If the TIFOPTS NPFLAG configuration option is set to NM and the NM bits indicate that a lookup has already been performed, then the Service Action Handler returns immediately.

If the NM bits indicate that a lookup has not already been performed, the RTDB lookup is performed and does not return a match.

In this no-match case, a Release message will be sent with a Release Cause specified in the RCAUSE option or the RCAUSEPFX option. The Redirection Number is not included in the Release message.

This Service Action Handler provides no inputs to Formatting Actions.

The post-NPP processing sends a Release message with a Release Cause that is configured in the RCAUSE option or the RCAUSEPFX option. The Redirection Number is not included in the Release message.

Terminating Action?

In the no-match case, this is a terminating action.

CGPNNP Service Action Handler

The CGPNNP Service Action Handler performs an RTDB lookup on the CgPN digits from the ISUP IAM message.

The CGPNNP Service Action Handler is supported for the TIFCGPN, TIFCGPN2, and TIFCGPN3 services, which are invoked only if the INVKSERV parameter value is not NONE for the corresponding TIF, TIF2, or TIF3 service.

The CGPNNP Service Action can be provisioned with any of the other Service Actions supported by the TIFCGPN, TIFCGPN2, and TIFCGPN3 services except for FPFXRLS.

Configuration Options Used

The TIFOPTS NPTYPECGPN option indicates the conditions used for a successful match.

The value of the TIFOPTS DFLTRN option, if set, is used to populate the RN on a successful DN match and the effective entity type is SP.

The TIFOPTS SPFILL option indicates whether SP should be populated when the DFLTRN value is used for the RN value.

Action Performed

RTDB lookup is performed on the conditioned digit string in international format. The result is determined based on the TIFOPTS NPTYPECGPN option value.

On a lookup where an RN or SP entity was found

The SRFIMSI digits assigned to the entity are used to populate the SRFIMSI Formatting Action value.
If the IGM feature is turned on, Entity Type is RN, and PT=0, then the Entity Type is treated as SP (in-network subscriber).

If a match is found and the Entity Type is RN, then RN digits are inserted into the outgoing field.

If a match is found and the effective Entity Type is SP, then SP digits are inserted into the outgoing field or the DFLTRN option digit string can be used to populate the RN Formatting Action value instead of actual SP digits.

If a match is found and the Entity Type is SP, then SPFILL=ON causes the SP digits to populate the SP Formatting Action value when the DFLTRN value is used to populate the RN Formatting Action value.

On a lookup where an entry was found, but entity data was not found (NPTYPECGPN=ALL), the CgPN is unchanged, if the Formatting Actions do not modify the digits in some other manner.

Formatting Action processing is skipped on an unsuccessful lookup. Depending on the Formatting Action configuration for the selected rule, the updated RN, SP or SRFIMSI can be used during CgPN formatting by NPP.

Terminating Action?

This is not a terminating action.

CgPNSvcRqd Service Action Handler

The CgPNSvcRqd Service Action Handler performs an RTDB lookup on the conditioned CgPN digit string.

The CgPNSvcRqd and NPRLS Service Actions are mutually exclusive in an Action Set.

Configuration Options Used

The NPTYPECGPN option indicates the conditions used for a successful match.

The IAMCGPN option value (DN, RN, RNDN) indicates the format of outgoing CgPN string. For the IAMCGPN configuration option, RN implies either RN or SP.

The value of the DFLTRN option, if set, is used to populate the RN on a successful match on SP.

Action Performed

On a lookup where entity data was found, the CgPN is changed according to the IAMCGPN configuration option. TIF will use the updated CgPN string to set the CgPN in the outgoing message.

On a lookup where an entry was found, but entity data was not found (NPTYPE=ALL), the CgPN is unchanged. The outgoing CgPN string is empty.

The length of the provisioned STPOPTS Default Country Code (DEFCC) parameter value provides the number of Country Code (CC) digits that are at the front of the conditioned CgPN.

On a successful lookup, where the outgoing format includes the DN (IAMCGPN=DN or RNDN) and the Country Code (CC) was added to the conditioned CgPN, the CC will be removed from the conditioned CgPN before copying the DN to the outgoing CgPN digit sting.

For example,

On entry to the Service Action Handler:
- The conditioned CgPN is CCC1234567.
- The number of CC digits is 3.
- The IAMCGPN option values is RNDN.
The lookup is successful.
- The value of RN is AAA.
- The resulting outgoing CgPN digit string is AAA1234567.

If a match is found and the Entity Type is RN, then RN digits are inserted into the outgoing field.

If a match is found and the Entity Type is SP, then SP digits are inserted into the outgoing field or the DFLTRN option digit string can be used instead of actual SP digits.

Note:

If the IGM feature is turned on, Entity Type is RN, and PT=0, then the Entity Type is treated as SP (in-network subscriber).

Terminating Action?

This is not a terminating action.

CRP Service Action Handler

The Circular Route Prevention (CRP) Service Action Handler attempts to detect a circular route.

The CRP Service Action must have a higher precedence that the NPRLS Service Action, which is a terminating action.

Configuration Options Used

The TIFOPTS NPFLAG configuration option indicates when and how the NM bits should be processed.

The TIFOPTS CRPREL configuration option indicates the Release Cause code to be included in the Release message.

Actions Performed

If the TIFOPTS NPFLAG configuration option is set to NM and the NM bits indicate that a lookup has already been performed, then the Service Action Handler returns immediately. (NM bits are used in-network only. If the NM bits have been set, then portability has already been checked in the network. Another CRP check is not needed.)

If the NM bits indicate that a lookup has not already been performed, the RTDB lookup is performed. If an RN is returned, then it is assumed that the number was ported and that a circular route is detected.

A Release Cause code will be included, and a Redirection Number will not be included, in the outgoing Release message.

The NPP Formatting Action processing will be skipped when a circular route is detected. One way to force formatting of the outgoing CdPN is to configure the CDIAL Service Action.

Terminating Action?

If a circular route is detected, then this is a terminating action.

TIF Post-NPP Processing for TIF NP

TIF post-NPP processing performs all actions required for NP Release and most actions required for NP Relay. The only extra NP-specific logic in TIF post-NPP processing is a Result Handler that performs the following functions:

If the NPFLAG option value is NM, and the NPRST parameter value is ON for the Destination Point Code in the DestinationCommon Screening List (CSL) table, then the NM bits will be set to 00 (meaning “without indication”).
If the NPFLAG option value is NM, and the NPRST parameter value is OFF for the Destination Point Code in the DestinationCSL table, and if.the incoming NM bits are not equal to the outgoing NM bits, then the outgoing NM bits are written to the outgoing ISUP IAM message (see NPRELAY Service Action Handler for details).
If the Destination Point Code is not found in the Destination table, then the message is discarded and a UIM is generated.

TIF Number Substitution Feature

Number substitution of both the Calling and Called Party provides customers the ability of supporting numbers outside their normal number range without having to upgrade all the nodes in the network. The TIF Number Substitution (TIF NS) feature, along with the Numbering Plan Processor (NPP) and the Triggerless ISUP Framework (TIF), provide the following capabilities:

Called number substitution to change a Public DN into a Private DN
Calling number substitution to change a Private DN into a Public DN

The TIF NS feature is built upon the services provided by TIF and NPP to support RTDB lookup of both Calling Party and Called Party numbers for substitution.

TIF NS provides the following functions:

Definition of feature-specific pre-NPP processing to be performed by TIF
Service Action specification (including Service Action names and precedence)
Service Action Handlers
Feature-specific post-NPP processing, if needed

TIF NS Message Flows

The following figure shows CgPN and CdPN substitution in an ISUP IAM Relay call flow.

Figure 3-10 ISUP RELAY with TIF NS

The following figure shows the ISUP IAM Relay call flow where CdPN is substituted and CgPN is not substituted.

Figure 3-11 ISUP RELAY with TIF NS - No CgPN Substitution

The following figure shows the ISUP IAM Relay call flow where CgPN is substituted and CdPN is not substituted.

Figure 3-12 ISUP RELAY with TIF NS - No CdPN Substitution

TIF NS Basic Use Cases

This section describes two basic use cases for TIF NS:

TIF NS use case for TIF CdPN Service
TIF NS use case for TIF CgPN Service

TIF NS Use Case for TIF CdPN Service

The following figure shows the steps involved in a basic TIF NS use case for CdPN service.

Figure 3-13 TIF NS Basic Operation for TIF CdPN Service

This case uses the following Service Rule and configuration options:

Filter FPFX=123
Filter FDL=13
Conditioning Actions=CC3+AC3+SN7
Service Actions=NSCgPN, NSCdPN
Formatting Actions=CC+AC+SN
TIFOPTS options NSADDLDATA=yes, NSPUBLIC=5

TIF NS Use Case for TIF CgPN Service

The following figure shows the steps involved in a basic TIF NS use case for CgPN service.

Figure 3-14 TIF NS Basic Operation for TIF CgPN Service

This case uses the following Service Rule and configuration options:

Filter FPFX-123
Filter FDL=13
Conditioning Actions=CC3+AC3+SN7
Service Action=NSCgPN
Formatting Actions=CC+AC+SN
TIFOPTS options NSADDLDATA=yes, NSPUBLIC=5

TIF NS Configuration Options

TIF Configuration Options indicates the TIF configuration options that can be used specifically by TIF NS. TIF NS can also use other options that are available to any TIF feature.

TIF NS Handling of IAM Message

When an IAM message is received and successfully decoded, an RTDB lookup is performed on the CdPN, the CgPN, or both.

For the CdPN, upon successful retrieval of the Called Party DN (Private), the CdPN is substituted in the outgoing IAM message.

For the CgPN, upon successful retrieval of the Calling Party DN (Public), the CgPN is substituted in the outgoing IAM message. If the Calling Party's Category is not the same as the value for the TIFOPTS nspublic configuration option and the lookup was successful, the Calling Party's Category is changed to the nspublic option value in the outgoing IAM message. The outgoing IAM message is then relayed.

TIF NS Protocol Handling

TIF NS protocol handling provides the following functions:

TIF NS-specific pre-NPP processing
TIF NS Service Action Handlers
Post NPP-processing

TIF Pre-NPP Processing for TIF NS

TIF decodes the incoming MSU and passes either the conditioned CdPN or the conditioned CgPN to NPP.

For the conditioned CgPN, the country code provisioned in the STPOPTS DefCC parameter value will be prepended to the conditioned CgPN if the TIFOPTS condcgpn parameter value is set to addcc.

TIF NS Service Action Handlers

TIF NS provides Service Action Handlers for the NPP Service Actions that are specific to TIF NS. TIF and NPP perform the following functions for the TIF NS feature:

RTDB lookup
Interpretation of results from RTDB lookups
NPP processing of Service Actions that are used for TIF NS

Table 3-6 provides a summary of the Service Actions used specifically for TIF NS.

Table 3-6 Summary of TIF NS Service Actions

Service Action	Description	Function	Precedence
NSCdPN	Called Number Substitution	Performs an RTDB lookup on the CdPN; if the lookup is successful, replaces the outgoing CdPN.	80
NSCgPN	Calling Number Substitution	Performs an RTDB lookup on the CgPN. if the lookup is successful, replaces the outgoing CgPN.	75

NSCdPN Service Action Handler

The TIF NSCdPN Service Action Handler executes the NSCdPN Service Action when NSCdPN is associated in a Service Rule Set with a CdPN service (TIF, TIF2, TIF3).

There are no mutually exclusive relationships with other NS Service Actions.

Configuration Options Used

None.

Action Performed

The NSCdPN Service Action Handler performs an RTDB lookup on the conditioned CdPN digit string. On a successful lookup it replaces the outgoing CdPN. A successful lookup is one in which the subscriber type is Public and there is a pointer to an associated Private DN. The subscriber can come from either the individual or range data.

This Service Action Handler copies digits from the Private DN found in the successful RTDB lookup, and populates one of the following sets of Formatting Action values:

ZN
CC+DN
CC+AC+SN

This Service Action assumes that Formatting Action execution will occur. If another Service Action determines that Formatting Action execution will not occur, the CDIAL Service Action must be used to force Formatting Action execution to occur.

The post-NPP processing replaces the CdPN in the outgoing message.

Terminating Action?

This is not a terminating action.

TIF CdPN NSCgPN Service Action Handler

The TIF CdPN NSCgPN Service Action Handler executes the NSCgPN Service Action when NSCgPN is associated in a Service Rule Set with a CdPN service (TIF, TIF2, TIF3).

The SNSCgPN Service Action and the NSCgPN Service Action are mutually exclusive in the same Action Set.

NSCgPN for a TIF CdPN service cannot be specified if a TIF CgPN is configured to be invoked (INVKSERV parameter not NONE in CdPN Service Rule).

Configuration Options Used

The nsaddldata configuration option indicates whether to compare the incoming Calling Party's Category to the nspublic configuration option value before the RTDB lookup.

The nspublic configuration option indicates the value for the Calling Party's Category in a Public DN for the network.

Formatting of the outgoing CgPN string is based on the value of the iamcgpn configuration option.

Action Performed

The NSCgPN Service Action Handler performs an RTDB lookup on the conditioned CgPN digit string. On a successful lookup it replaces the outgoing CgPN. A successful lookup is one in which the subscriber type is Private and there is an associated Public DN.

The Calling Party Category can be:

Used to determine if the incoming CgPN is Public or Private
Replaced in the outgoing message with a "Public" value

This Service Action Handler uses the nsaddldata configuration option to determine whether to check the Calling Party Category for "Public" or "Private", and the nspublic configuration option value to replace the Calling Party Category in the outgoing message.

If a country code was prepended to the original CgPN by the TIF pre-NPP processing, the Public DN from the RTDB is assumed to begin with a country code. The STPOPTS default country code ( DefCC) value is compared with the country code digits in the DN retrieved from the RTDB.

If the two sets of digits match, the country code digits are removed from the retrieved DN.
If the two sets of digits do not match, a UIM is generated and the Service Action returns normally.

The following actions are taken depending on the value of the iamcgpn configuration option:

If iamcgpn=dn, all digits in the outgoing CgPN are substituted.
If iamcgpn=rndn, the RN will contain the maximum number of digits allowed in the CgPN, and the digits following the RN are replaced with the substituted DN.

This Service Action Handler provides no inputs to Formatting Actions. Formatting of the outgoing CgPN digit string is completed in the Service Action Handler.

The post-NPP processing replaces the Calling Party'Category and the CgPN (only the digit string and the odd/even indicator bits, not the NAI) as NPP processing indicates.

Terminating Action?

This is not a terminating action.

TIF CgPN NSCgPN Service Action Handler

The TIF CgPN NSCgPN Service Action Handler executes the NSCgPN Service Action when NSCgPN is associated in a Service Rule Set with a CgPN service (TIFCGPN, TIFCGPN2, TIFCGPN3).

The SNSCgPN Service Action and the NSCgPN Service Action are mutually exclusive in the same Action Set.

Configuration Options Used

The nsaddldata configuration option indicates whether to compare the incoming Calling Party's Category to the nspublic configuration option value before the RTDB lookup.

The nspublic configuration option indicates the value for the Calling Party's Category in a Public DN for the network.

Action Performed

The Calling Party Category can be:

Used to determine if the incoming CgPN is Public or Private
Replaced in the outgoing message with a "Public" value

This Service Action Handler uses the nsaddldata configuration option to determine whether to check the Calling Party Category for "Public" or "Private", and the nspublic configuration option value to replace the Calling Party Category in the outgoing message.

This Service Action Handler populates the ZN, CC+DN. or CC+AC+SN Formatting Action values that correspond to the provisioned Conditioning Actions.

The TIF post-NPP processing replaces the Calling Party Category and the CgPN (only the digit string and the odd/even indicator bits, not the NAI) as NPP processing indicates. Formatting Action execution uses the populated values to generate the outgoing CgPN digit string.

Terminating Action?

This is not a terminating action.

TIF Post-NPP Processing for TIF NS

TIF post-NPP processing performs all actions required for NS functions. TIF performs the following processing for TIF NS:

Calling Party's Category replacement
CgPN replacement
CdPN replacement

TIF Simple Number Substitution Feature

The TIF Simple Number Substitution (TIF SNS) feature allows the Calling Party number in the ISUP IAM message to be substituted with a single Calling Party number that is provisioned in a TIF configuration option. The RTDB is not used in this case.

The TIF SNS feature uses services provided by the Triggerless ISUP Framework (TIF), and provides the following functions:

Feature-specific pre-NPP processing
Service Action specification (including Service Action names and precedence)
Service Action Handlers
Feature-specific post-NPP processing

TIF SNS Message Flows

The following figure shows TIF SNS use cases.

Figure 3-15 ISUP Message Flows for TIF SNS

TIF SNS Basic Use Cases

This section describes two basic use cases for TIF SNS:

TIF SNS use case for TIF CdPN Service
TIF SNS use case for TIF CgPN Service

TIF SNS Use Case for TIF CdPN Service

The following figure shows the steps involved in a basic TIF SNS use case for CdPN service:

Figure 3-16 TIF SNS Basic Operation for TIF CdPN Service

This case uses the following Service Rule and configuration options:

Filter FPFX=123
Filter FDL=13
Conditioning Actions=CC3+AC3+SN7
Service Action=SNSCgPN
Formatting Actions=CC+AC+SN
TIFOPTS option SNSCGPNDFLT=none

TIF SNS Use Case for TIF CgPN Service

The following figure shows the steps involved in a basic TIF SNS use case for CgPN service:

Figure 3-17 TIF SNS Basic Operation for TIF CgPN Service

This case uses the following Service Rule and configuration options:

Filter FPFX-123
Filter FDL=13
Conditioning Actions=CC3+AC3+SN7
Service Action=SNSCgPN
Formatting Actions=CC+AC+SN
TIFOPTS option SNSCgPNDFLT=123777888999

TIF SNS Configuration Option

The SNSCgPNDflt configuration option is used by TIF SNS. The provisioned option value indicates the number to be used to replace the CgPN during simple number substitution. A value of none indicates that the CgPN will be removed from the outgoing message.

The TIF SNS feature can use other TIF configuration options that are available to any TIF feature. See TIF Configuration Options.

TIF SNS Protocol Handling

TIF SNS protocol handling consists of the following functions:

TIF SNS-specific pre-NPP Processing
- TIF sends the conditioned CgPN to NPP.
SNSCgPN Service Action Handler
TIF SNS-specific post NPP-Processing

TIF SNS Service Action Handlers

The SNSCgPN Service Action can be associated with a TIF CdPN service (TIF, TIF2, TIF3) or a TIF CgPN service (TIFCGPN, TIFCGPN2, TIFCGPN3) in a Service Rule Set. Two SNSCgPN Service Action Handlers indicate how to update the outgoing CgPN based on the value of the SNSCgPNDflt configuration option:

TIF CdPN SNSCgPN Service Action Handler

The TIF CdPN SNSCgPN Service Action Handler indicates how to update the outgoing CgPN based on the value of the SNSCgPNDflt configuration option.

SNSCgPN for a TIF CdPN service cannot be specified if a TIF CgPN service is invoked using the INVKSERV parameter in the CdPN Service Rule.

See Table 2-10 for Service Actions that are mutually exclusive with SNSCgPN.

Configuration Options Used

The SNSCgPNDflt option indicates the number used to replace the CgPN, or a value of NONE if the CgPN should be removed.

Actions Performed

If the CgPN parameter is not included in the IAM message or the CgPN digits are empty in the CgPN parameter, then the TIF CgPN SNSCgPN Service Action will not be invoked.

If the SNSCgPNDflt option value is not NONE, the SNSCgPN Service Action Handler indicates that the CgPN is to be replaced with the specified SNSCgPNDflt option value.

If the SNSCgPNDflt option value is NONE, then the SNSCgPN Service Action Handler indicates that the CgPN will be removed from the message.

This Service Action Handler provides no input to NPP Formatting Actions.

Note:

Formatting of the outgoing CgPN string is not based on the value of the IAMCGPN configuration option.

NPP Post-Processing

TIF post-NPP processing performs all actions required for SNS-related updates to the outgoing message:

If the value of the SNSCgPNDflt option is NONE, then TIF removes the CgPN.
If the value of the SNSCgPNDflt option is not NONE, then TIF replaces the CgPN in the outgoing message with the SNSCgPNDflt value. The CgPN NAI is not changed.

Terminating Action?

This is not a terminating action.

TIF CgPN SNSCgPN Service Action Handler

The SNSCgPN Service Action Handler indicates how to update the outgoing CgPN based on the value of the SNSCgPNDefault configuration option.

Configuration Options Used

The SNSCgPNDefault option indicates the number used to replace the CgPN, or a value of NONE if the CgPN should be removed.

Actions Performed

If the SNSCgPNDefault option value is the number used to replace the CgPN, the SNSCgPN Service Action Handler indicates that the CgPN is to be replaced.

If the SNSCgPNDefault option value is NONE, then the SNSCgPN Service Action Handler indicates that the CgPN should be removed from the message.

This Service Action Handler provides no input to NPP Formatting Actions.

Note:

Formatting of the outgoing CgPN string is not based on the value of the IAMCGPN configuration option.

NPP Post-Processing

TIF post-NPP processing performs all actions required for SNS-related updates to the outgoing message:

If the value of the SNSCgPNDefault option is NONE, then TIF removes the CgPN.
If the value of the SNSCgPNDefault option is not NONE, then TIF replaces the CgPN with the SNSCgPNDefault value in the outgoing message. The CgPN NAI is not changed.

TIF SCS Forwarding Feature

The TIF SCS Forwarding feature provides the ability to forward messages to the SCS for additional processing after TIF processing is complete.

The only modifications made to the message by TIF are:

Re-encode a modified CdPN
Forward message to SCS, using DTA

The TIF SCS Forwarding feature provides the Service Action Handler for the FWDSCS Service Action that is provided by TIF to NPP. Before an NPP Rule can be provisioned with the FWDSCS Service Action in the Action Set, the TIF SCS Forwarding feature must be enabled in the system.

The feature does not require EPAP and RTDB lookup, but can operate with EPAP or ELAP subsystems.

FWDSCS Service Action Handler

The FWDSCS Service Action indicates that any relayed IAM and SAM messages require processing by the Database Transport Access (DTA; also called Redirect), a feature that encapsulates an MSU in an SCCP header and forwards it to a destination (the DTA DPC, usually an SCS). Refer to Database Administration - Features User's Guide for more information about DTA, including message size limits for encapsulation.

DTA might not be able to forward a message for the following reasons:

The message is too large for DTA to process.
The DTA DPC is prohibited or congested (through TFC, local link congestion is not considered).

The DTA node is disabled.

If DTA encapsulation is requested but cannot be performed, the message is relayed without additional modification.

TIF Additional Subscriber Data Feature

The TIF Additional Subscriber Data (TIF ASD) feature allows for the insertion of Additional Subscriber Data (ASD) into the CdPN or CgPN of an outgoing IAM or Redirection Number of a REL ISUP message.

The ASD is obtained from the RTDB lookup of the CdPN and CgPN digits.

TIF ASD provides Service Action Handlers for the ASDLKUP and CgPNASDRqd Service Actions associated with TIF CdPN services TIF, TIF2, and TIF3 in NPP. The ASDLKUP Service Action allows retrieval of ASD from the matched incoming CdPN to be inserted into the outgoing CdPN digits. The CgPNASDRqd Service Action allows retrieval of ASD from the matched incoming CgPN to be inserted into the outgoing CdPN digits.

TIF ASD provides a Service Action Handler for the ASDLKUP Service Action associated with TIF CgPN services TIFCGPN, TIFCGPN2, and TIFCGPN3 in NPP. The ASDLKUP Service Action allows retrieval of ASD from the matched incoming CgPN to be inserted into the outgoing CgPN digits.

A TIF CgPN service is invoked by the corresponding TIF CdPN service by setting the INVKSERV parameter value to the TIF CgPN service name in the Service Rule for the TIF CdPN service.

The NPP ASD Formatting Action is used for TIF ASD. The ASD Formatting Action is used to process the ASD that is retrieved by TIF ASD Service Actions.

The NPP ASD and ASDOTHER Formatting Actions are used for TIF ASD:

The ASD Formatting Action is used to process the ASD that is retrieved by TIF ASD Service Actions.
The ASDOTHER Formatting Action allows the ASD returned from a RTDB search by the ASDLKUP Service Action for a TIF CgPN service to be used in CdPN formatting.

Basic TIF ASD Use Case for TIF CdPN Service

In the use case described in this section, the incoming IAM message contains CdPN=1238882223333 and CgPN=1239995556666.

The following Filter and Action Set components are used for the example:

Filter Prefix (FPFX) = 123
Filter Digit Length (FDL) = 13
Conditioning Actions = CC3 + AC3 + SN7
Service Action = CgPNASDRqd
Formatting Actions = CC + ASD + AC + SN

The CgPNASDRqd Service Action Handler performs an RTDB DN lookup on the CgPN, finds the CgPN entry with ASD value a5d, and populates the ASD Formatting Action value with the ASD value.

NPP Formatting Action execution uses the extracted CdPN information and the ASD to construct the outgoing CdPN digit string as CC + ASD + AC + SN = 123a5d8882223333.

TIF inserts the outgoing CdPN digit into the outgoing IAM message. The CgPN is not changed. The IAM message is relayed.

Basic TIF ASD Use Case for TIF CgPN Service

In the use case described in this section, the incoming IAM message contains CdPN=1238882223333 and CgPN=1239995556666.

The following Filter and Action Set components are used for the example:

Filter Prefix (FPFX) = 123
Filter Digit Length (FDL) = 13
Conditioning Actions = CC3 + AC3 + SN7
Service Action = ASDLKUP
Formatting Actions = CC + ASD + AC + SN

The ASDLKUP Service Action Handler performs an RTDB lookup for the DN in the CgPN, finds the CgPN entry with ASD value a5d, and populates the ASD Formatting Action value with the ASD value.

NPP Formatting Action execution uses the extracted information and the ASD to construct the outgoing CgPN digit string as CC + ASD + AC + SN = 123a5d9995556666.

TIF inserts the outgoing CgPN digit string into the outgoing IAM message. The CdPN is not changed. The IAM message is relayed.

TIF ASD Use Case for TIF CgPN Service using ASDOTHER

In the use case described in this section, the incoming IAM message contains CdPN=4568882223333 and CgPN=1239995556666.

The following TIF Filter and Action Set components are used for the example:

Filter Prefix (FPFX) = 456
Filter Digit Length (FDL) = 13
INVKSERV=TIFCGPN
Conditioning Actions = CC3 + AC3 + SN7
Service Action = CDIAL
Formatting Actions = CC + ASDOTHER + AC + SN

The following TIFCGPN Filter and Action Set components are used for the example:

Filter Prefix (FPFX) = 123
Filter Digit Length (FDL) = 13
Conditioning Actions = CC3 + AC3 + SN7
Service Action = ASDLKUP
Formatting Actions = CC + AC + SN

The ASDLKUP Service Action Handler performs an RTDB lookup for the DN in the CgPN, finds the CgPN entry with ASD value a5d, and populates the CgPN ASD Formatting Action value with the ASD value.

NPP Formatting Action execution uses the extracted information to construct the outgoing CgPN digit string as CC + AC + SN = 1239995556666.

TIF populates the CdPN ASDOTHER Formatting Action value from the CgPN ASD Formatting Action value.

NPP Formatting Action execution uses the extracted information and the CdPN ASDOTHER value to construct the outgoing CdPN digit string as CC + ASDOTHER + AC + SN = 456a5d8882223333.

TIF inserts the outgoing CdPN and CgPN into the outgoing IAM message. The IAM message is relayed.

TIF ASD Message Flows

The following figure shows TIF ASD use cases for ISUP IAM messages, with TIF CdPN service..

Figure 3-18 ISUP IAM Message Flows for TIF ASD for TIF CdPN Service

The following figure shows TIF ASD use cases with the NPRLS and NPNRLS Service Actions.

Figure 3-19 ISUP REL Message Flow for TIF ASD for TIF CdPN Service with NPRLS and NPNRLS SAs

The following fiure shows TIF ASD use cases for TIF CgPN service.

Figure 3-20 ISUP IAM Message Flow for TIF ASD for CgPN Service

TIF ASD Service Action Handlers

TIF ASD provides Service Action Handlers for the NPP Service Actions shown in Table 3-7:

Table 3-7 NPP Service Actions used by TIF ASD

TIF Services	Service Action	Description
TIF, TIF2, TIF3	ASDLKUP	Performs an individual or range RTDB lookup on the CdPN to find an entry containing an ASD digit string.
TIF, TIF2, TIF3	CgPNASDRqd	Performs an individual or range RTDB lookup on the CgPN to find an entry containing an ASD digit string.
TIFCGPN, TIFCGPN2, TIFCGPN3	ASDLKUP	Performs an individual or range RTDB lookup on the CgPN to find an entry containing an ASD digit string.

TIF CdPN ASDLKUP Service Action Handler

The ASDLKUP Service Action Handler executes the ASDLKUP Service Action associated with a TIF CdPN service (TIF, TIF2, TIF3) to find a CdPN entry containing an ASD digit string.

The TIF CdPN ASDLKUP Service Action and the CgPNASDRqd Service Action are mutually exclusive in the same Action Set. The CgPNASDRqd Service Action cannot be specified if a TIF CgPN service is invoked.

Configuration Options Used

None.

Action Performed

The TIF CdPN ASDLKUP Service Action Handler performs an individual or range RTDB lookup on the conditioned CdPN, to find an entry containing an ASD digit string.

ASDLKUP populates the ASD Formatting Action value with the ASD digit string.

Depending on the Formatting Action configuration for the selected NPP Service Rule, the ASD digit string can be used during CdPN formatting by NPP.

TIF uses the formatted CdPN in the outgoing IAM or the Redirection Number in the outgoing REL message.

If the TIF ASD feature is turned off in the system, the ASDLKUP Service Action Handler returns immediately.

Terminating Action?

This is not a terminating action.

TIF ASD CgPNASDRqd Service Action Handler

The CgPNASDRqd Service Action Handler executes the CgPNASDRqd Service Action associated with a TIF CdPN service (TIF, TIF2, TIF3) to find a CgPN entry containing an ASD digit string.

Configuration Options Used

None.

Action Performed

The CgPNASDRqd Service Action Handler performs an individual or range RTDB lookup on the conditioned CgPN, to find an entry containing an ASD digit string.

CgPNASDRqd populates the ASD Formatting Action value with the ASD digit string.

Depending on the Formatting Action configuration for the selected NPP Service Rule, the ASD digit string can be used during CdPN formatting by NPP.

TIF uses the formatted CdPN in the outgoing IAM or the Redirection Number in the outgoing REL message.

If the TIF ASD feature is turned off in the system, the CgPNASDRqd Service Action Handler returns immediately.

Terminating Action?

This is not a terminating action.

TIF CgPN ASDLKUP Service Action Handler

The ASDLKUP Service Action Handler executes the ASDLKUP Service Action associated with a TIF CgPN service (TIFCGPN, TIFCGPN2, TIFCGPN3) to find a CgPN entry containing an ASD digit string.

Configuration Options Used

None.

Action Performed

The TIF CgPN ASDLKUP Service Action Handler performs an individual or range RTDB lookup on the conditioned CgPN, to find an entry containing an ASD digit string.

ASDLKUP populates the TIF CgPN ASD Formatting Action value with the ASD digit string.

Depending on the Formatting Action configuration for the selected NPP Service Rule, the ASD digit string can be used during CgPN formatting by NPP.

If the TIF ASDOTHER Formatting Action is provisioned for the TIF CdPN service that invoked the TIF CgPN service, TIF copies the TIF CgPN ASD Formatting Action value to the TIF CdPN ASDOTHER Formatting Action value for use in CdPN formatting. TIF uses the formatted CgPN in the outgoing IAM or the Redirection Number in the outgoing REL message.

If the TIF ASD feature is turned off in the system, the TIF CgPN ASDLKUP Service Action Handler returns immediately.

Terminating Action?

This is not a terminating action.

TIF Generic Routing Number Feature

The TIF Generic Routing Number (TIF GRN) feature allows for the insertion of a Generic Routing Number (GRN) digit string into the CdPN or CgPN of an outgoing IAM or Redirection Number of a REL ISUP message.

The GRN is obtained from the RTDB lookup of the CdPN and CgPN digits.

TIF GRN provides Service Action Handlers for the GRNLKUP and CgPNGRNRqd Service Actions associated with TIF CdPN services TIF, TIF2, and TIF3 in NPP. The GRNLKUP Service Action allows retrieval of the GRN from the matched incoming CdPN to be inserted into the outgoing CdPN digits. The CgPNGRNRqd Service Action allows retrieval of GRN from the matched incoming CgPN to be inserted into the outgoing CdPN digits.

TIF GRN provides a Service Action Handler for the GRNLKUP Service Actions associated with TIF CgPN services TIFCGPN, TIFCGPN2, and TIFCGPN3 in NPP. The GRNLKUP Service Action allows retrieval of the GRN from the matched incoming CgPN to be inserted into the outgoing CgPN digits.

A TIF CgPN service is invoked by the corresponding TIF CdPN service by setting the INVKSERV parameter value to the TIF CgPN service name in the Service Rule for the TIF CdPN service.

The NPP GRN Formatting Action is used to process the GRN that is retrieved by TIF GRN Service Actions.

The NPP GRN Formatting Action is used for TIF GRN. The GRN Formatting Action is used to process the GRN that is retrieved by TIF GRN Service Actions.

The NPP GRN and GRNOTHER Formatting Actions are used for TIF GRN:

The GRN Formatting Action is used to process the GRN that is retrieved by TIF GRN Service Actions.
The GRNOTHER Formatting Action allows the GRN returned from a RTDB search by the GRNLKUP Service Action for a TIF CgPN service to be used in CdPN formatting.

Basic TIF GRN Use Case for TIF CdPN Service

In the use case described in this section, the incoming IAM message contains CdPN=1238882223333 and CgPN=1239995556666.

The following Filter and Action Set components are used for the example:

Filter Prefix (FPFX) = 123
Filter Digit Length (FDL) = 13
Conditioning Actions = CC3 + AC3 + SN7
Service Action = CgPNGRNRqd
Formatting Actions = CC + GRN + AC + SN

The CgPNGRNRqd Service Action Handler performs an RTDB DN lookup on the CgPN, finds the CgPN entry with GRN value a5d, and populates the GRN Formatting Action value with the GRN value.

NPP Formatting Action execution uses the extracted CdPN information and the GRN to construct the outgoing CdPN digit string as CC + GRN + AC + SN = 123a5d8882223333.

TIF inserts the outgoing CdPN digit into the outgoing IAM message. The CgPN is not changed. The IAM message is relayed.

Basic TIF GRN Use Case for TIF CgPN Service

In the use case described in this section, the incoming IAM message contains CdPN=1238882223333 and CgPN=1239995556666.

The following Filter and Action Set components are used for the example:

Filter Prefix (FPFX) = 123
Filter Digit Length (FDL) = 13
Conditioning Actions = CC3 + AC3 + SN7
Service Action = GRNLKUP
Formatting Actions = CC + GRN + AC + SN

The GRNLKUP Service Action Handler performs an RTDB lookup for the DN in the CgPN, finds the CgPN entry with GRN value a5d, and populates the GRN Formatting Action value with the GRN value.

NPP Formatting Action execution uses the extracted information and the GRN to construct the outgoing CgPN digit string as CC + GRN + AC + DN = 123a5d9995556666.

TIF inserts the outgoing CgPN digit into the outgoing IAM message. The CdPN is not changed. The IAM message is relayed.

TIF GRN Use Case for TIF CgPN Service using GRNOTHER

In the use case described in this section, the incoming IAM message contains CdPN=4568882223333 and CgPN=1239995556666.

The following TIF Filter and Action Set components are used for the example:

Filter Prefix (FPFX) = 456
Filter Digit Length (FDL) = 13
INVKSERV=TIFCGPN
Conditioning Actions = CC3 + AC3 + SN7
Service Action = CDIAL
Formatting Actions = CC + GRNOTHER + AC + SN

The following TIFCGPN Filter and Action Set components are used for the example:

Filter Prefix (FPFX) = 123
Filter Digit Length (FDL) = 13
Conditioning Actions = CC3 + AC3 + SN7
Service Action = GRNLKUP
Formatting Actions = CC + AC + SN

The GRNLKUP Service Action Handler performs an RTDB lookup for the DN in the CgPN, finds the CgPN entry with GRN value a5d, and populates the CgPN GRN Formatting Action value with the GRN value.

NPP Formatting Action execution uses the extracted information to construct the outgoing CgPN digit string as CC + AC + SN = 1239995556666.

TIF populates the CdPN GRNOTHER Formatting Action value from the CgPN GRN Formatting Action value.

NPP Formatting Action execution uses the extracted information and the CdPN GRNOTHER value to construct the outgoing CdPN digit string as CC + GRNOTHER + AC + SN = 456a5d8882223333.

TIF inserts the CdPN and CgPN in the outgoing IAM message. The outgoing message is relayed.

TIF GRN Message Flows

The following figure shows TIF GRN use cases for TIF CdPN Service.

Figure 3-21 ISUP IAM Message Flows for TIF GRN for TIF CdPN Service

The following figure shows TIF GRN use cases with NPRLS and NPNRLS for TIF CdPN service.

Figure 3-22 ISUP REL Message Flow for TIF GRN for TIF CdPN Service with NPRSL and NPNRLS

The following figure shows TIF GRN use cases for TIF CgPN service.

Figure 3-23 ISUP IAM Message Flows for TIF GRN for TIF CgPN Service

TIF GRN Service Action Handlers

TIF GRN provides Service Action Handlers for the NPP Service Actions shown in Table 3-8:

Table 3-8 NPP Service Actions used by TIF GRN

TIF Services	Service Action	Description
TIF, TIF2, TIF3	GRNLKUP	Performs an individual or range RTDB lookup on the CdPN to find an entry containing a GRN digit string.
TIF, TIF2, TIF3	CgPNGRNRqd	Performs an individual or range RTDB lookup on the CgPN to find an entry containing a GRN digit string.
TIFCGPN, TIFCGPN2, TIFCGPN3	GRNLKUP	Performs an individual or range RTDB lookup on the CgPN to find an entry containing a GRN digit string.

TIF CdPN GRNLKUP Service Action Handler

The GRNLKUP Service Action Handler executes the GRNLKUP Service Action associated with a TIF CdPN service (TIF, TIF2, TIF3) to find a CdPN entry containing a GRN digit string.

The TIF CdPN GRNLKUP Service Action and the CgPNGRNRqd Service Action are mutually exclusive in the same Action Set. The CgPNGRNRqd Service Action cannot be specified if a TIF CgPN service is invoked.

Configuration Options Used

None.

Action Performed

The TIF CdPN GRNLKUP Service Action Handler performs an individual or range RTDB lookup on the conditioned CdPN, to find an entry containing an GRN digit string.

GRNLKUP populates the GRN Formatting Action value with the GRN digit string.

Depending on the Formatting Action configuration for the selected NPP Service Rule, the GRN digit string can be used during CdPN formatting by NPP.

TIF uses the formatted CdPN in the outgoing IAM or the Redirection Number in the outgoing REL message.

If the TIF GRN feature is turned off in the system, the GRNLKUP Service Action Handler returns immediately.

Terminating Action?

This is not a terminating action.

TIF GRN CgPNGRNRqd Service Action Handler

The CgPNGRNRqd Service Action Handler executes the CgPNGRNRqd Service Action associated with a TIF CdPN service (TIF, TIF2, TIF3) to find a CgPN entry containing a GRN digit string.

Configuration Options Used

None.

Action Performed

The CgPNGRNRqd Service Action Handler performs an individual or range RTDB lookup on the conditioned CgPN, to find an entry containing a GRN digit string.

CgPNGRNRqd populates the GRN Formatting Action value with the GRN digit string.

Depending on the Formatting Action configuration for the selected NPP Service Rule, the GRN digit string can be used during CdPN formatting by NPP.

TIF uses the formatted CdPN in the outgoing IAM or the Redirection Number in the outgoing REL message.

If the TIF GRN feature is turned off in the system, the CgPNGRNRqd Service Action Handler returns immediately.

Terminating Action?

This is not a terminating action.

TIF CgPN GRNLKUP Service Action Handler

The GRNLKUP Service Action Handler executes the GRNLKUP Service Action associated with a TIF CgPN service (TIFCGPN, TIFCGPN2, TIFCGPN3) to find a CgPN entry containing a GRN digit string.

Configuration Options Used

None.

Action Performed

The TIF CgPN GRNLKUP Service Action Handler performs an individual or range RTDB lookup on the conditioned CgPN, to find an entry containing an GRN digit string.

GRNLKUP populates the TIF CgPN GRN Formatting Action value with the GRN digit string.

Depending on the Formatting Action configuration for the selected NPP Service Rule, the GRN digit string can be used during CgPN formatting by NPP.

If the TIF GRNOTHER Formatting Action is provisioned for the TIF CdPN service that invoked the TIF CgPN service, TIF copies the TIF CgPN GRN Formatting Action value to the TIF CdPN GRNOTHER Formatting Action value for use in CdPN formatting. TIF uses the formatted CgPN in the outgoing IAM or the Redirection Number in the outgoing REL message.

If the TIF GRN feature is turned off in the system, the TIF CgPN GRNLKUP Service Action Handler returns immediately.

Terminating Action?

This is not a terminating action.

TIF Blacklist Features

The TIF Subscriber CgPN Blacklist, TIF Range CgPN Blacklist, and TIF Selective Screening features provide TIF blacklist capabilities, which help Network Operators reduce significantly or completely prevent spoofing their networks with illegal messages.

The TIF CgPN Blacklist functionality is controlled by the TIF Subscriber CgPN Blacklist feature. The TIF Subscriber CgPN Blacklist (TIF Subscr CgPN Blacklist) feature generates an ISUP Release (REL) message back to the originator of a processed ISUP IAM, based on the Calling Party Number (CgPN), if either of the following scenarios occur:

The CgPN that is found in the RTDB is blacklisted; the CgPN has CgBL flag=YES.
The CgPN is not found in the RTDB.

The TIF Range CgPN Blacklist feature generates an ISUP Release (REL) message back to the originator of a processed ISUP IAM, based on the CgPN, if either of the following scenarios occur:

The CgPN begins with a specific prefix.
The Calling Party parameter is not present in the IAM or it is present with no digits in it.

The TIF CdPN Blacklist functionality is controlled by the TIF Selective Screening feature. The TIF Selective Screening feature generates an ISUP Release (REL) message back to the originator of a processed ISUP IAM, based on the Called Party Number (CdPN), if any of the following scenarios occur:

The CdPN that is found in the RTDB is blacklisted; the CdPN has CdBL flag = YES.
The CdPN is not found in RTDB.
The CdPN begins with a specific prefix.
The Called Party is screened by TIF Selective Screening and the Release cause is not NONE.

The TIF Redirecting Number Based Blacklisting allows modifying CdPN based on the redirecting number, if present in the incoming message.

The TIF Linkset based Blacklisting screens any message arriving on EAGLE with the combination of blacklisted SetID referred in incoming linkset with the blacklisted SetID configured in RTDB the number. This enables a misused user to make legitimate calls in case it is blocked on a particular linkset.

The TIF Generic Name Based screening functionality screens the message arriving on EAGLE with the combination of name and linkset from which it is arriving. Therefore, enabling users to block any spam calls.

NPP Service Action Data

An NPP Action Set can have optional Service Action Data (SA Data) for one or more Service Actions (SAs) in the Action Set. Not all NPP Service/Service Action combinations support SA Data. The SA Data contains two numerical values: SAxVAL configuration parameter values, where x is the same number as the associated Service Action parameter.

Table 3-9 lists the TIF CdPN and TIF CgPN NPP services and Service Actions that support SA Data.

Table 3-9 NPP Service Actions that Support SA Data

NPP Service	Service Action	SA Values (SAxVAL)
TIFCGPN, TIFCGPN2, TIFCGPN3 TIF, TIF2, TIF3	FPFXRLS	Require 2 numerical values for an SAxVAL parameter, one value for ANSI and one value for ITU release causes, respectively. Both values have range 0-127.
TIFCGPN, TIFCGPN2, TIFCGPN3 TIF, TIF2, TIF3	BLRLS	Require 2 numerical values for an SAxVAL parameter, one value for ANSI and one value for ITU release causes, respectively. Both values have range 0-127.
TIFCGPN, TIFCGPN2, TIFCGPN3 TIF, TIF2, TIF3	BLNFNDRLS	Require 2 numerical values for an SAxVAL parameter, one value for ANSI and one value for ITU release causes, respectively. Both values have range 0-127.
TIF, TIF2, TIF3	NOCGPNRLS	Require 2 numerical values for an SAxVAL parameter, one value for ANSI and one value for ITU release causes, respectively. Both values have range 0-127.
TIF, TIF2, TIF3	SELSCR	Require 2 numerical values for an SAxVAL parameter, one value for ANSI and one value for ITU release causes, respectively. Both values have range 0-127. Additionally supports SAxDGTS (range 0-FF) to provision Call Types for CdPN.

TIF Blacklist Message Flow

Figure 3-24 shows the basic TIF Blacklist message flow.

Figure 3-24 TIF Blacklist Basic Message Flow

TIF Blacklist Post-NPP Processing

After NPP processing is complete, the TIF post-NPP Results Handler performs the following functions for the TIF Blacklist features:

If the IAM MSU is marked as blacklisted, TIF generates a RELease MSU with the Release Cause value obtained by a Service Action that identified this MSU as blacklisted, and sends the RELease MSU to the originator of the incoming IAM.
If the IAM MSU is not marked as blacklisted, the IAM message is relayed intact.

TIF Subscr CgPN Blacklist Feature

The TIF Subscr CgPN Blacklist feature generates an ISUP Release (REL) message back to the originator of a processed ISUP IAM, based on the Calling Party Number (CgPN), if the following EPAP-based scenarios occur:

The Calling Party is found in the RTDB and the CgPN is marked as blacklisted; the CgPN has CgBL flag=YES.
The CgPN is not found in the RTDB.

Two Service Action Data (SA Data) values can be associated with provisioned TIF CgPN Blacklist Service Actions to provide configurable Release Cause values for the blacklist scenarios. One value is used for ANSI ISUP and the other value is used for ITU ISUP.

TIF Subscr CgPN Blacklist provides the following functions:

Definition of feature-specific pre-NPP processing to be performed by TIF
Service Action specification (including Service Action names and precedence)
Service Action Handlers
Feature-specific post-NPP processing, if needed

TIF Subscr CgPN Blacklist Service Action Handlers

The TIF Subscr CgPN Blacklist feature provides feature-specific Service Action Handlers for NPP Service Actions. TIF and NPP perform the following functions for the TIF Subscr CgPN Blacklist feature:

RTDB lookup
Interpretation of results from RTDB lookups
NPP processing of Service Actions that are used for TIF Subscr CgPN Blacklist
Post-NPP processing of the outgoing message

Table 3-10 provides a summary of the Service Actions used specifically for TIF Subscr CgPN Blacklist.

Table 3-10 Summary of TIF Subscr CgPN Blacklist Service Actions

Service Action	Description	Function	Precedence
BLRLS	TIF CgPN Blacklist in EPAP Release	Indicates that a Release (REL) will be generated if the Calling Party is found in the RTDB and the CgPN contains the CgBL flag=YES.	91
BLNFNDRLS	TIF CgPN not-in-EPAP Release	Indicates that a Release (REL) will be generated if the CgPN digits are not found in the RTDB and finds the CgPN digits.	91

BLRLS Service Action Handler for TIF CgPN EPAP-based RELEASE

The BLRLS Service Action Handler indicates that an REL will be sent if Calling Party digits are found in the RTDB with CgBL=YES.

Configuration Options Used

The provisioned SAxVAL[1] value contains the Release Cause value used in the REL for an IAM ISUP ANSI message; the provisioned SAxVAL[2] value contains the Release Cause value used in the REL for an IAM ISUP ITU message.

Action Performed

The BLRLS Service Action Handler performs an RTDB lookup and finds the CgPN digits in the RTDB. If the Calling Party digits in the RTDB have CgBL=YES, the Service Action Handler indicates that an REL will be sent to the originator of the IAM during post-NPP processing. The REL will contain the provisioned SAxVAL[1] value for the Release Cause if ANSI ISUP, or the provisioned SAxVAL[2] value for the Release Cause if ITU ISUP. The REL will not include a Redirection Number. The original MSU is discarded.

If the TIF Subscr CgPN Blacklist feature is not turned ON or the CgPN is not found in the RTDB, or if the CgPN is found but is not marked as blacklisted, the Service Action Handler completes without any changes.

No Formatting Actions are populated.

Terminating Action?

Yes when the subscriber is blacklisted.

BLNFNDRLS Service Action Handler for TIF CgPN not-in-EPAP RELEASE

The BLNFNDRLS Service Action Handler performs an RTDB lookup and does not find the CgPN digits in the RTDB.

Configuration Options Used

Action Performed

If CgPN digits are not found in the RTDB, the Service Action Handler indicates that an REL will be sent to the originator of the IAM during post-NPP processing. The REL will contain the provisioned SAxVAL[1] value for the Release Cause if ANSI ISUP, or with the provisioned SAxVAL[2] value for the Release Cause if ITU ISUP. The REL will not include a Redirection Number. The original MSU Is discarded.

If the TIF Subscr CgPN Blacklist feature is not turned ON or if the CgPN is found in the RTDB, the Service Action Handler completes without any changes.

No Formatting Actions are populated.

Terminating Action?

Yes

TIF Range CgPN Blacklist Feature

The TIF Range CgPN Blacklist feature generates an ISUP Release (REL) message back to the originator of a processed ISUP IAM, based on the Calling Party Number (CgPN), if the following non-EPAP-based scenarios occur:

The CgPN begins with a specific prefix.
The Calling Party parameter is not present in the IAM or it is present with no digits in it.

Two Service Action Data (SA Data) values can be associated with provisioned TIF CgPN Blacklist Service Actions to provide configurable Release Cause values for the blacklist scenarios. The SAxVAL[1] value is used for ANSI ISUP and the SAxVAL[2] value is used for ITU ISUP.

TIF Range CgPN Blacklist provides the following functions:

Definition of feature-specific pre-NPP processing to be performed by TIF
Service Action specification (including Service Action names and precedence)
Service Action Handlers
Feature-specific post-NPP processing, if needed

TIF Range CgPN Blacklist Service Action Handlers

The TIF Range CgPN Blacklist feature provides feature-specific Service Action Handlers for NPP Service Actions. TIF and NPP perform NPP processing of Service Actions that are used for TIF Range CgPN Blacklist and post-NPP processing of the outgoing message.

Table 3-11 provides a summary of the Service Actions used specifically for TIF Range CgPN Blacklist.

Table 3-11 Summary of TIF Range CgPN Blacklist Service Actions

Service Action	Description	Function	Precedence
FPFXRLS	TIF CgPN Blacklist non-EPAP Release	Indicates that a Release (REL) will be generated if a matching Calling Party Rule is found in NPP.	92
NOCGPNRLS	TIF CgPN Empty Release	Indicates that a Release (REL) will be generated if the Calling Party parameter is not present in the ISUP IAM or it is present with no digits in it.	80

FPFXRLS Service Action Handler for TIF Prefix CgPN non-EPAP-based RELEASE

The FPFXRLS Service Action Handler indicates that an REL will be sent to the originator of the IAM if a matching Calling Party Rule is found by NPP.

The FPFXRLS Service Action is mutually exclusive with all other Service Actions in the same Action Set.

Configuration Options Used

Action Performed

If the Calling Party prefix is found by NPP, the Service Action Handler indicates that an REL will be sent to the originator of the IAM during post-NPP processing. If the subscriber is marked as blacklisted, the REL will contain the provisioned SAxVAL[1] value for the Release Cause if ANSI ISUP, or with the provisioned SAxVAL[2] value for the Release Cause if ITU ISUP. The REL will not include a Redirection Number. The original MSU is discarded.

If the TIF Range CgPN Blacklist feature is not turned ON , the Service Action Handler completes without any changes.

No Formatting Actions are populated.

Terminating Action?

Yes

NOCGPNRLS Service Action Handler for TIF Empty CgPN non-EPAP-based RELEASE

The NOCGPNRLS Service Action Handler indicates that an REL will be sent to the originator of the IAM if the CgPN is not present in the IAM or the CgPN is present but has no digits in it.

Configuration Options Used

Action Performed

If CgPN digits are not present in the MSU, the Service Action Handler indicates that an REL will be sent to the originator of the IAM during post-NPP processing. If the subscriber is marked as blacklisted, the REL will contain the provisioned SAxVAL[1] value for the Release Cause if ANSI ISUP, or with the provisioned SAx)AL[2] value for the Release Cause if ITU ISUP. The REL will not include a Redirection Number. The original MSU Is discarded.

If the TIF Range CgPN Blacklist feature is not turned ON or if the CgPN in the processed MSU contains digits, the Service Action Handler completes without any changes.

No Formatting Actions are populated.

Terminating Action?

Yes when the subscriber is blacklisted.

TIF Selective Screening Feature

The TIF CdPN blacklist functionality is controlled by the TIF Selective Screening feature. The TIF Selective Screening feature generates an ISUP Release (REL) message back to the originator of a processed ISUP IAM, based on the Called Party Number (CdPN), if the following scenarios occur:

The CdPN that is found in the RTDB is blacklisted; the CdPN has CdBL flag = YES.
The CdPN is not found in RTDB.
The CdPN begins with a specific prefix.
The Called Party is screened by TIF Selective Screening and the Release cause is not NONE.

Three Service Action Data (SA Data) values can be associated with provisioned TIF Selective Screening Service Actions to provide configurable Release Cause values for the blacklist scenarios. The SAxVAL[1] value is used to indicate the Release Cause for ANSI ISUP; the SAxVAL[2] value is used to indicate the Release Cause for ITU ISUP. The SAxDGTS parameter indicates the Call Type for CdPNs that match the associated NPP Rule.

TIF Selective Screening provides the following functions:

Definition of feature-specific pre-NPP processing to be performed by TIF
Service Action specification (including Service Action names and precedence)
Service Action Handlers
Feature-specific post-NPP processing, if needed

TIF Selective Screening Service Action Handlers

The TIF Selective Screening feature provides feature-specific Service Action Handlers for NPP Service Actions. TIF and NPP perform the following functions for the TIF Selective Screening feature:

RTDB lookup
Interpretation of results from RTDB lookups
NPP processing of Service Actions that are used for TIF Selective Screening
Post-NPP processing of the outgoing message

Table 3-12 provides a summary of the Service Actions used for TIF Selective Screening.

Table 3-12 Summary of TIF Selective Screening Service Actions

Service Action	Description	Function	Precedence
BLRLS	TIF CdPN Blacklist in EPAP-based Release	Indicates that a Release (REL) message will be generated if the Called Party is found in the RTDB and the CdPN contains the CdBL flag=YES	91
BLNFNDRLS	TIF CdPN not-in-EPAP Release	Indicates that a Release (REL) message will be generated if a matching Called Party number is not found in the RTDB	91
FPFXRLS	TIF Pfx CdPN Release (non-EPAP based)	Indicates that a Release (REL) message will be generated if a matching Called Party rule is found by NPP	92
SELSCR	TIF CdPN EPAP-based Selective Screening	Indicates that the message is selectively screened based on CdPN and CgPN Call Types	91

BLRLS Service Action Handler for TIF Selective Screening (CdPN) EPAP-based RELEASE

The BLRLS Service Action Handler indicates that a Release (REL) message will be sent if Called Party digits are found in the RTDB with CdBL=YES.

Configuration Options Used

TIFOPTS options SAxVAL[1] and SAxVAL[2] contain the Release Cause value used in the Release (REL) message for an IAM ISUP ANSI message and an IAM ISUP ITU message.

Action Performed

The BLRLS Service Action Handler performs an RTDB lookup and finds the CdPN digits in the RTDB. If the Called Party digits in the RTDB have CdBL=YES, the Service Action Handler indicates that a Release (REL) message will be sent to the originator of the IAM during post-NPP processing. The Release (REL) message will contain the provisioned SAxVAL[1] value for the Release Cause if ANSI ISUP, or the provisioned SAxVAL[2] value for the Release Cause if ITU ISUP. The REL will not include a Redirection Number. The original MSU is discarded.

If the TIF Selective Screening feature is not turned on, the CdPN is not found in the RTDB, or the CdPN is found but is not marked as blacklisted, the Service Action Handler completes without any changes.

No Formatting Actions are populated.

Terminating Action?

Yes, when the subscriber is marked as blacklisted.

BLNFNDRLS Service Action Handler for TIF Selective Screening (CdPN) not-in-EPAP RELEASE

The BLNFNDRLS Service Action Handler performs an RTDB lookup and does not find the CdPN digits in the RTDB.

Configuration Options Used

TIFOPTS options SAxVAL[1] and SAxVAL[2] contain the Release Cause value used in the Release (REL) message for an IAM ISUP ANSI message and an IAM ISUP ITU message.

Action Performed

If CdPN digits are not found in the RTDB, the Service Action Handler indicates that a Release (REL) message will be sent to the originator of the IAM during post-NPP processing. The Release (REL) message will contain the provisioned SAxVAL[1] value for the Release Cause if ANSI ISUP, or the provisioned SAxVAL[2] value for the Release Cause if ITU ISUP. The REL will not include a Redirection Number. The original MSU is discarded.

No Formatting Actions are populated.

Terminating Action?

Yes.

FPFXRLS Service Action Handler for TIF Prefix CdPN non-EPAP-based RELEASE

The FPFXRLS Service Action Handler indicates that a Release (REL) message will be sent to the originator of the IAM if a matching Called Party Rule is found by NPP.

The FPFXRLS Service Action is mutually exclusive with all other Service Actions in the same Action Set.

Configuration Options Used

TIFOPTS options SAxVAL[1] and SAxVAL[2] contain the Release Cause value used in the Release (REL) message for an IAM ISUP ANSI message and an IAM ISUP ITU message.

Action Performed

If the Called Party prefix is found by NPP, the Service Action Handler indicates that a Release (REL) message will be sent to the originator of the IAM during post-NPP processing. If the subscriber is marked as blacklisted, the Release (REL) message will contain the provisioned SAxVAL[1] value for the Release Cause if ANSI ISUP, or with the provisioned SAxVAL[2] value for the Release Cause if ITU ISUP. The Release (REL) message will not include a Redirection Number. The original MSU is discarded.

If the TIF Range CdPN Blacklist feature is not turned ON , the Service Action Handler completes without any changes.

No Formatting Actions are populated.

Terminating Action?

Yes.

SELSCR Service Action Handler for TIF CdPN EPAP-based Selective Screening

The SELSCR Service Action Handler Indicates that the message is selectively screened based on CdPN and CgPN Call Types.

Configuration Options Used

TIFOPTS options SAxVAL[1] and SAxVAL[2] contain the Release Cause value used in the Release (REL) message for an IAM ISUP ANSI message and an IAM ISUP ITU message. TIFOPTS options SAxDGTS indicate the Call Type for CdPNs that match the associated NPP Rule.

Action Performed

If the CdPN is screened by the TIF selective screening process, the TIF selective screening post-processing checks whether the SAxVAL values are provisioned with SELSCR Service Action in the TIF NPP Service. If the SAxVAL is provisioned for the incoming ISUP message type, then the ISUP RELease (REL) message is generated with the RELease cause provisioned in SAxVAL.

If the SAxVAL is not provisioned (None) for the incoming ISUP message type, then the ISUP message is relayed to the destination point code in the incoming message (original DPC). The CdPN and CgPN parameters in the ISUP message are formatted based on the respective FASCRCD and FASCRCG formatting list values provisioned in the NPP Action Set associated with TIF NPP Service.

Terminating Action?

TIF Selective Screening Call Types

The TIF Selective Screening process is based on Call Types configured for a DN in the RTDB. The Call Types of a DN are a list of numerical values in the range of 1-254, 255 , and 0. The zero (0) value indicates that the specific Call Type is not provisioned. The 255 value (hexadecimal 0xFF) of the first Call Type, which is the first byte of the digit string, indicates a wild card (any/*). Only the first number in the set of eight numbers can be provisioned with this wild card value of 255 (any/*) because the following seven numbers will be ignored. Any other Call Type except the first Call Type provisioned as 255 (0xFF/any/*) will be treated as not provisioned.

The Call Types for a DN are stored in the Number Substitution DN field. The Number Substitution DN field for the DN is stored in the RTDB. The Number Substitution DN field is a 15-digit digit string, with two digits stored per byte for a total of eight bytes). This allows provisioning seven 1-byte Call Types and one 4-bit Call Type for a total of eight possible Call Types per DN. The first seven Call Types a range from 1 till 254, and the eighth Call Type can have a value between 1 and 15. The Call Types are provisioned as hexadecimal digits: the first 7 Call Types are one-byte-long Call Types - as a pair of hexadecimal digits, and the last - eighth Call Type - as a single hexadecimal digit.

The Call Type for CdPN can also be configured with NPP rules for TIF NPP Service. The SELSCR Service Action is associatd with the configurable SAxDGTS parameter. A single Call Type (0x0 - 0xFF) can be configured in the SAxDGTS field corresponding to the SELSCR Service Action in the NPP Action Set.

The Call Types configured in the SAxDGTS parameter take precedence over the Call Types configured in the Number Substitution DN field. If the Call Type for the CdPN is configured in the SAxDGTS field, then the Call Types configured in the RTDB are not considered for the CdPN. The Call Types for CgPN are always fetched from RTDB.

Only the first Call Type configured for the CdPN in RTDB is considered for Selective Screening. If more than one Call Type is configured for the CdPN in RTDB, then the rest of the Call Types after the first Call Type are ignored.

TIF Redirecting-Number Based Blacklist Feature

The TIF Redirecting-Number Based Blacklisting Feature allows modifying CdPN based on the redirecting number, if present in the incoming message.

If the redirecting number is found in the incoming message, then it is decoded. RTDB lookup is executed to check the presence of ASD with RDN as a key. If the SUBCDPN parameter is configured, the number substitutes the CdPN digits instead of ASD.

The following table provides a summary of the Service Action used specifically for TIF Redirecting-Number Based Blacklist.

Table 3-13 Summary of TIF Redirecting-Number Based Blacklist Service Action

Service Action	Description	Function	Precedence
TIFRDNBL	CdPN Service Action	Sets the NPPSTATE.ASD field if an individual or range lookup on the Redirecting Number or CgPN leads to an entry containing a non-empty ASD digit string. And substitutes SUBCDPN digits instead of ASD digits in-case the lookup was performed on Redirecting-Number.	90

Configuration Options Used

No specific configuration options are used.

Action Performed

The redirecting number is decoded from the IAM message received. If redirecting number is present in IAM and the applied Service Action is TIFRDNBL, RTDB is queried with the redirecting number as a key. However, if redirecting number is not present in IAM, RTDB is queried using the original CgPN digits as a key.

If ASD is returned from RTDB, it is stored in NPPSTATE.ASD, which is used during the processing of FA, when FA is equal to ASD. If ASD is found corresponding to CgPN in RTDB, ASD digits are used to replace CdPN in outgoing digits. However, if ASD is found corresponding to RDN in RTDB, SUBCDPN digits are used to replace CdPN in outgoing digits.

If there is no redirecting number available in IAM or any of the criteria for RDN is not met, then the functionality remains same as CgPNASDRqd.

Terminating Action

Yes

TIF Generic Name Based Screening Feature

The TIF Generic Name Based Screening functionality stores the blacklisted information for a particular name arriving from a specific linkset (National or International) on EAGLE. Therefore, any message arriving on EAGLE are screened with the combination of name and linkset from which it is arriving. This enables users to block any span calls with different names.

The following table provides a summary of the Service Action used specifically for TIF Generic Name Based Screening.

Table 3-14 Summary of TIF Generic Name Based Screening Service Actions

Service Action	Description	Function	Precedence
TIFGNBL	CgPN Service Action	Indicates that a Release should be generated if the generic name present in IAM message is available in the Generic name table with a certain combination of linkset type.	90

Configuration Options Used

No specific configuration options are used.

Action Performed

Indicate that a Release for TIFGNBL should be sent when a similar Generic name is found in the Generic Name table with the same combination of the following parameters:

The settype parameter in Generic name table
The gnameset parameter in linkset table

Terminating Action

Yes

TIF Linkset Based Blacklist Feature

The TIF Linkset Based Blacklist functionality enables a misused user to still make legitimate calls in case it is blocked on a particular linkset. The blacklisted information for each number includes the blacklisted SetID. Therefore, all the messages arriving on EAGLE are screened with the following combination:

The Blacklisted SetID referred in incoming linkset
The Blacklisted SetID configured in RTDB

This functionality enables a misused user to still make legitimate calls in case it is blocked on a particular linkset.

The following table provides a summary of the Service Action used specifically for TIF Linkset Based Blacklist:

Table 3-15 Summary of TIF Linkset Based Blacklist Service Actions

Service Action	Description	Function	Precedence
TIFLSBL	CgPN Service Action	Indicates that a Release should be generated if the blacklisted SetID (CgPNBLSet) configured with the incoming linkset matches with the blacklisted SetID configured against the DN in the RTDB	90

Configuration Options Used

No specific configuration options are used.

Action Performed

Indicates that a Release should be generated if:

The blacklisted SetID (CgPNBLSet) configured with the incoming linkset matches with the blacklisted SetID configured against the DN in the RTDB.
No Number Substitution CgPN Service Action is configured after TIFLSBL.

Terminating Action

Yes