Cisco Cisco Packet Data Gateway (PDG)
P-GW CDR Field Descriptions
▀ CDR Fields
▄ GTPP Interface Administration and Reference, StarOS Release 18
262
Format Variable Meaning
Encoding Format
YY
Year 00 to 99
BCD encoded
MM
Month 01 to 12
BCD encoded
DD
Day 01 to 31
BCD encoded
hh
Hour 00 to 23
BCD encoded
mm
Minute 00 to 59
BCD encoded
ss
Second 00 to 59
BCD encoded
S
Sign 0 = “+”, “-” ASCII encoded
hh
Hour 00 to 23
BCD encoded
mm
Minute 00 to 59
BCD encoded
Format
BCD encoded octet string
Length
9 bytes
TWAN ULI
This field contains the location information of UE in a Trusted WLAN Access Network (TWAN).
Format
Octet string
Length
38 bytes
User Location Information
This field contains the User Location Information of the MS as defined in TS 29.060 for GPRS case, and in TS 29.274 for
EPC case (e.g. CGI, SAI, RAI TAI and ECGI), if available.
EPC case (e.g. CGI, SAI, RAI TAI and ECGI), if available.
This field is provided by the SGSN/MME and transferred to the S-GW/P-GW during the IP-CAN bearer
activation/modification.
activation/modification.
User Location Information contains the location (e.g. CGI/SAI, ECGI/TAI or RAI) where the UE is located and used
during the transfer of the data volume captured by the container (applicable only to the SGW-CDR). This is included
in the Traffic data container only if previous container's change condition is “user location change”. Note the user
location information in SGW-CDR main level contains the location where the UE was when PGW-CDR was opened.
during the transfer of the data volume captured by the container (applicable only to the SGW-CDR). This is included
in the Traffic data container only if previous container's change condition is “user location change”. Note the user
location information in SGW-CDR main level contains the location where the UE was when PGW-CDR was opened.
The flags ECGI, TAI, RAI, SAI and CGI in octet 5 indicate if the corresponding fields are present in the IE or not. If
one of these flags is set to “0”, the corresponding field is not present at all. The respective identities are defined in
3GPP TS 23.003.
one of these flags is set to “0”, the corresponding field is not present at all. The respective identities are defined in
3GPP TS 23.003.
The following subclauses specify the coding of the different identities. For each identity, if an Administration decides
to include only two digits in the MNC, then bits 5 to 8 of octet 7 are coded as “1111”.
to include only two digits in the MNC, then bits 5 to 8 of octet 7 are coded as “1111”.