The Anti Fraud Prevention feature, using the CFU & ECT prevention feature.
|
This feature applies to the HLR & MSOFTX (V100R008C03 & later versions) This feature is applicable to the GSM and UMTS R99/R4 networks and can be used in the scenario where the MSOFTX3000 is required to restrict CF/ECT times. The Fraud Prevention feature allows carriers to monitor subscriber activities such as authentication, location update, forwarded-to number (FTN) registration, and international FTN registration. If a subscriber performs these activities frequently, the system considers that the SIM card of the subscriber may be cloned and then reports the abnormality. If subscriber B has subscribed to the call forwarding (CF) or explicit call transfer (ECT) service, the call from A to B can be forwarded by B to C, during which there can be no connection between A and B as well as between B and C. In this way, B can set up multiple connections between An to Cn ("n" here means an indefinite number of A and C), but these calls might not be charged. This is a kind of charge fraud for carriers. To prevent such fraud, the MSOFTX3000 supports the Anti-Fraud feature which can restrict the number of simultaneous forwarded/ECT calls of subscribers. Solution Implementation Principle: The Anti-Fraud feature involves the following two flows: CFU & ECT as shown below. Anti-Fraud prevention with CFU scenario (call Flow): The flow is as follows: 1. When an incoming or outgoing call is originated, the local MSC server sends an SRI request to the HLR. 2. After finding that the called subscriber has subscribed to the CFU service, the HLR returns the forwarded-to number in the SRI_ack message. 3. If the Anti-Fraud function is enabled, after detecting that the call is being forwarded, the local MSC server checks whether the total times of CF that was triggered by the subscriber in the local office has reached the preset threshold. If the CF times has reached the threshold, this CF request is rejected; otherwise, the CF request is allowed. Anti-Fraud prevention with ECT prevention scenario (call Flow): The flow is as follows for ECT request threshold exceed check on MSC: 1. Subscriber a calls subscriber b. The call is connected. 2. Subscriber a holds the call. 3. Subscriber a calls subscriber c. The call is connected. 4. Subscriber a sends an ECT request. If the Anti-Fraud function is enabled, after detecting the request, the local MSC server checks whether the total times of ECT that was triggered by the subscriber in the local office has reached the preset threshold. If the ECT times has reached the threshold, this ECT request is rejected; otherwise, the ECT request is allowed. Benefit of solution to Carriers: |

Favorite (0)