Summary Data

Revision History

Note	This is a customer-specific feature. For details, contact your Cisco Account representative.

When a User Location Information (ULI) IE is received, the P-GW stores the information in the P-GW Charging Data Record (CDR). When the ULI IE is updated, the ULI field of the P-GW CDR gets reflected.

However, there are instances where after receiving the initial ULI with TAI + ECGI, the subsequent ULIs receive only ECGI. With this feature, P-GW saves the latest TAC and appends it to the main level ULI field in the P-GW CDR along with ECGI, if TAC is not received.

Examples of ULI customization:

1. Initial ULI received in Create Session Request:TAI + ECGI.

   • TAI > MCC: 214, MNC: 365, TAC: 0x6789

   • ECGI > MCC: 214, MNC: 365, ECI: 0x0001234

   TAC: 0x6789 is saved by P-GW.

2. ULI is modified to ECGI only.

   • ECGI > MCC: 214, MNC: 365, ECI: 0x0003333

   • Whenever ULI is written to P-GW CDR, saved TAC is used

   • ULI in P-GW CDR contains the following:

     1. TAI > MCC: 214, MNC: 365, TAC: 0x6789

     2. ECGI > MCC: 214, MNC: 365, ECI: 0x0003333

Note	As LAC is not a separate element in ULI, in case of CGI, RAI or SAI, LAC is expected to be received always.

Use the following configuration to customize TAC:

configure 
   context context_name 
      gtpp group gtpp_group_name 
         [ no | default ] gttp attribute tac-always-in-uli 
         end 

NOTES:

• gtpp group gtpp_group_name : Configures GTPP related parameters for the system to handle a GTPP attribute that does not indicate direction.

• no | default : Disables the addition of saved TAC to ULI.

• gttp attribute tac-always-in-uli : Specifies the "TAI Location Type" option always in the ULI CDR field.

This section provides information to monitor and troubleshoot this feature.