3 IDP A-Party Blacklist Feature
The IDP A-Party Blacklist feature enhances the Prepaid IDP Query Relay feature to provide a generic framework to support subscriber blacklisting capability with a query-based or relay-based method. The feature supports the blacklist check on Calling Party (A-Party or CgPN) number in the IDP CAMEL or INAP message.
Feature Description
The IDP A-Party Blacklist feature provides subscriber blacklisting capability on the Calling Party (A-Party or CgPN) number in the IDP CAMEL message. (The feature is not supported for IDPSMS messages.) The blacklisting function is achieved using either a query-based mode, or a relay-based mode in conjunction with IDP Relay feature processing.
EAGLE receives an IDP query message destined to the EAGLE PC, or a prepaid IDP message sent to the EAGLE PC for translation to a prepaid SCP. MSCs are configured with a trigger point to send an IDP message for just post-paid, or prepaid, or all subscribers in the network, depending on the use case for a particular operator.
The necessary discrimination and pre-processing are performed by the prepaid IDP Relay functions (SCCP CdPA check, CgPA check and SKBCSM Common Screening List). The Calling Party Number (from the CgPN parameter in the message) is decoded. If the subscriber number is blacklisted, the number in the EPAP RTDB has a blacklist flag and any Routing Number information that is needed to re-route the call. If a blacklist match is found, a Connect message is returned with Routing Number (if provisioned). This Routing Number could be a service center number that receives the re-routed call and provides the necessary assistance. If the subscriber is not blacklisted, the IDP message continues normal processing for IDP A-Party Blacklist Relay, or a CONTINUE response is generated for IDP A-Party Blacklist Query.
- IDP A-Party Blacklist Query mode is provided by the BLKLSTQRY NPP Service Action, which is used when a query/response mode is desired for both blacklist-match and blacklist-no-match cases.
- IDP A-Party Blacklist Relay mode is provided by BLKLSTRLY NPP Service Action, which is used when a query/response mode is desired only for the blacklist-match case. In the blacklist-no-match case, the message is subject to other new or existing provisioned features, their status, and the results of any other Service Action Handler execution.
IDP A-Party Blacklist Query
IDP A-Party Blacklist Query mode is provided by the BLKLSTQRY NPP Service Action, which is used when a query/response mode is desired for both the blacklist-match and blacklist-no-match cases.
The BLKLSTQRY Service Action is used only by the IDP Relay IDPRCgPN NPP service, and is mutually exclusive with the BLKSTRLY Service Action in the same rule.
BLKLSTQRY is an IDPRCgPN terminating Service Action for the blacklist-match case.
-
In the blacklist-match case, the CgPN lookup on the RTDB results in an entry in which the blacklist flag is on and GRN data is present.
A Connect response is encoded and sent back to originator of the IDP message using the existing routing mechanism.
The DRA parameter in the response is encoded using GRN entity digits from the RTDB and the TTROPTS DRAFRMT and DRANAI option value.
The TTROPTS DRANAI option value is used to encode the DRA NAI component of the DRAFRMT option format. If the NAI is International, the format must contain the Country Code (CC), If the NAI is National or Subscriber, the format does not contain the Country Code (CC).
The DRA NP value is always encoded as “e.164”, and the DRA NAI will be encoded based on the TTROPTS DRANAI option value.Figure 3-1 IDP A-Party Blacklist Query Response - Connect
-
In the blacklist-no-match case, an RTDB entry is not found for the CgPN, or an entry is found but the blacklist flag is off or GRN data is not present.
A Continue response is encoded and sent back to the originator of the IDP message using the existing routing mechanism.Figure 3-2 IDP A-Party Blacklist Query Response - Continue
The IDP Relay feature post-NPP processing function handles IDP A-Party Blacklist post-NPP processing. Based on the IDP Relay feature status and the possible BLKLSTQRY Service Action Handler execution results, post-processing encodes the Connect or Continue response. See Table 2-6.
On completion of feature specific handling, a generic translation can be applied to map success/failure results into required measurements pegs and rept-stat-sccp statistics.
In the post-processing handler for IDP A-Party Blacklist Query, network conversion is not allowed while sending the response. If the resulting PC is of a different network domain, or the Connect or Continue results in any encoding or decoding failures, then the IDP A-Party Blacklist Query processing is considered to be a failure. Based on the “return-on-error” flag in the incoming IDP message, either the UDTS will be sent back to the originator or the message is discarded if the failure was due to GTT on the CgPA.
In case of any failures in message processing, feature specific post-processing will also set unique execution error codes that can be used to identify the processing applied to the IDP message.
IDP A-Party Blacklist Relay
IDP A-Party Blacklist Relay mode is provided by the BLKLSTRLY NPP Service Action, which is used when a query/response mode is desired only for the blacklist-match case.
The BLKLSTRLY Service Action is used only by the IDP Relay IDPRCgPN NPP service; it has the highest precedence and is mutually exclusive with the BLKLSTQRY SA in the same rule.
BLKLSTRLY is a terminating Service Action on a blacklist match.
-
In the blacklist-match case, the CgPN lookup on the RTDB results in an entry in which the blacklist flag is on and GRN data is present.
A Connect response is encoded and sent back to originator of the IDP message (see part 1 on the left side of Figure 3-3).
The DRA parameter in the associated GRN entity digits are used to encode the DRA digits according to the TTROPTS DRAFRMT option value.
The TTROPTS DRANAI option value is used to encode the DRA NAI component of the DRAFRMT option format. If the NAI is International, the format must contain the Country Code (CC), If the NAI is National or Subscriber, the format does not contain the Country Code (CC).
The DRA NP value is always encoded as “e.164”, and the DRA NAI will be encoded based on the TTROPTS DRANAI option value. All other Service Action processing is ignored.
-
In the blacklist-no-match case, the message is serviced through other applicable IDP Relay Service Actions, or falls through to GTT processing if there are no subsequent applicable Service Actions. (See part 2 on the right side of Figure 3-3.)
Figure 3-3 IDP A-Party Blacklist Relay
In the post-NPP processing handler for IDP A-Party Blacklist Relay, network conversion is not allowed while sending the response. If the resulting PC is of different network type or the Connect results in any encoding failures, the IDP A-Party Blacklist Relay processing is considered to be a failure. Based on the “return-on-error” flag in the incoming IDP message, either the UDTS will be sent back to the originator or the message is discarded.
IDP A-Party Blacklist Service Action Handlers
- RTDB lookup
- Interpretation of results from RTDB lookups
- NPP processing of Service Actions that are used for IDP A-Party Blacklist
Table 3-1 provides a summary of the Service Actions used for IDP A-Party Blacklist.
Table 3-1 Summary of IDP A-Party Blacklist Service Actions
| Service Action | Description | Function | Precedence |
|---|---|---|---|
| BLKLSTQRY | Blacklist Query | Provides query response mode handling for selected incoming IDP Query messages. | 90 |
| BLKLSTRLY | Blacklist Relay | Provides relay mode handling for selected incoming IDP Query messages. | 90 |
| CgPNSvcRqd | Calling Number Lookup | Sets a flag to cause the IDPRCgPN service to be invoked for the message. | 60 |
BLKLSTQRY Service Action Handler
The BLKLSTQRY Service Action Handler performs an RTDB lookup on the conditioned CgPN digit string and indicates whether a Connect or Continue message should be sent to the originating SSP.
The BLKLSTQRY Service Action is mutually exclusive with all other IDPRCGPN Service Actions in an Action Set.
Configuration Options Used
None.
Action Performed
If the CgPN is found in the RTDB lookup, and the subscriber is blacklisted, and GRN data is present, a Connect message will be sent.
If the CgPN is not found in the RTDB lookup, or the subscriber is not blacklisted, or GRN data is not present, a Continue message will be sent.
The NPP Formatting Action processing will be skipped. One way to force formatting is to configure the CDIAL Service Action.
Terminating Action?
This is a terminating action.
BLKLSTRLY Service Action Handler
The BLKLSTRLY Service Action Handler performs an RTDB lookup on the conditioned CgPN digit string and indicates whether a Connect message will be sent to the originator, or the IDP query will be relayed to the SCP.
The BLKLSTRLY and BLKLSTQRY Service Actions are mutually exclusive in an Action Set.
Configuration Options Used
None
Action Performed
If the CgPN is found in the RTDB lookup, the subscriber is blacklisted, and GRN data is present, a Connect message will be sent.
If the CgPN is not found in the RTDB lookup, the subscriber is not blacklisted, and GRN data is not present, the IDP query will be relayed to the SCP.
The NPP Formatting Action processing will be skipped. One way to force formatting is to configure the CDIAL Service Action.
Terminating Action?
This is a terminating action only on a blacklist match.
EAGLE Commands
EAGLE Commands describes commands that can be used for the configuration of the IDP A-Party Blacklist feature.
Refer to Commands User's Guide for complete descriptions of the commands, including parameter names, valid values, and output examples for the commands.