Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2151950.1
Update Date:2016-06-22
Keywords:

Solution Type  Problem Resolution Sure

Solution  2151950.1 :   GPRS Gn xDR Builder Low Rate of IMSI Enrichment  


Related Items
  • Oracle Communications Performance Intelligence Center (PIC) Software
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec PIC
  •  


Dynamic enrichment does not work in all cases, with around only 50% of enriched  xDRs

In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-11938260468>

Applies to:

Oracle Communications Performance Intelligence Center (PIC) Software - Version 9.0.3 and later
Information in this document applies to any platform.

Symptoms

IMSI Enrichment in Gn GPRS session does not work correctly in up to 80% of cases (no IMSI value populated).

Cause

Possible causes:

  1. The IMSI enrichment prerequisite is a good reconstitution rate. It means that in case of bad reconstitution, there will be loss of information such as IMSI, which is essential to manage a correct enrichment. xDRs for Gn operations "Create PdP Context" are essential because they manage the TEID CP1 and TEID CP2 values. They are key with the IMSI to perform a good IMSI enrichment. The reconstitution status (rate) must be verified to ensure whether it is the origin of the bad enrichment rate.
    If it is confirmed that reconstitution rate is poor, the throughput must be verified.
  2. The throughput of traffic to be enriched must respect the recommended values of the system. Otherwise, if the system is overloaded, there will be reconstitution issues.
    From the CCM, in "Settings" of the PMF verify the value of parameter "ThresholdKbps" and check "mfDisp" on the PMF console (as cfguser). If the value increase, reach a max and decrease, it means that the throughput is over the limit.
  3. The values of parameters for "Mobile Database" ("Garbage time of Context " and "Association Table size") must be set according to network specificity.
    Indeed, these 2 values depends directly on the customers behavior and network usage: if GTP sessions are long (more than half a day) and if the number of customers on the network is high (several millions) it can occur a bad IMSI enrichment thru Mobile Database.

The values of the DFP for Gn sessions are low: half a day for ("Garbage time of Context" and 100000 for "Association Table size". These are low values, especially because of "sessions" duration are generally long on the networks (time between a "Create PDP Context" and a "Delete PDP Context".
With such values there may be problems for the system to manage all GTP sessions "contexts" opened on the system.

On PMF, CCM shows in "Settings" of the PMF that the parameter "ThresholdKbps" is set to 800000. By checking on the PMF, the mfDisp shows that the input traffic increases over 900000 and then decrease and so on. The traffic throughput is to high. Moreover, the linkDisp command on the same PMF shows that there is a "bypass" filter (named in fact "bypqss") and this filter makes that the traffic is too high in input. The configuration should be updated with lower input traffic, because current settings are over the recommendations, making that the system is unstable and reconstitution rate is poor. This occurs the poor IMSI enrichment.. 

Solution

  1. The input traffic throughput must be managed in order to respect the max recommendations and guarantee a better reliability of enrichment
  2. The values of parameters for "Mobile Database" ("Garbage time of Context " and "Association Table size") must be verified as they must be set according to network specificity.
    For example, to cover a day, the 1st parameter can be set to 86400. To be able to manage a huge number of customers, the 2nd parameter should be set to 1 million (which is the max value that can be set from the GUI for this parameter).

References

<NOTE:1949059.1> - Gn/Gp Builder Restarts Continuously when GTP Association Table Size is too Small

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback