ASR5x00: Grupo de Classificação = '0' refletindo em GGSN CDRs

Introduction

Este documento descreve os cenários de cobrança relacionados ao Grupo de Classificação (RG - Rating Group) 0 no GPRS Support Node (GGSN - Gateway GPRS Support Node).

Descrição do problema

Grupo de Classificação = '0' refletindo em CDRs (Call Data Records, registros de dados de chamada) GSN. Além disso, o volume que relata no GGSN no grupo de Classificação = ‘0’ não relata ao OCS (Online Charging Server, servidor de cobrança online).

CDR ELEMENTS FOLLOW
recordType EGSNPDPRECORD
servedIMSI 11122233334444
ggsnAddress 192.224.40.131
chargingID 464620230
sgsnAddress 192.224.40.136
accessPointNameNI xxxxx.com
pdpType IPV4
servedPDPAddress 192.72.21.107
dynamicAddressFlag TRUE
recordOpeningTime 160905195241+0530
duration 109
causeForRecClosing Normal Release
recordSequenceNumber 1
nodeID DELGW02
localSequenceNumber 384391885
apnSelectionMode MS or Network Provided and Subscription Verified
servedMSISDN 918009435175
chargingCharacteristics Prepaid
chargingCharSelMode SGSN Supplied
sgsnPLMNIdentifier 405, 54
imei-sv 3008280525536203
RATType GERAN
MSTimeZone +05:30
userLocationInformation 405-54-3105-8122
ratingGroup 0 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Troubleshoot

De acordo com o plano de redirecionamento pós-pago, eles ligam com o RG 431 ruledef que não está configurado com qualquer ID de conteúdo. Devido a isso, todos os usuários de redirecionamento pós-pagos obtêm um grupo de classificação zero no registro de dados de chamada (CDR).

De acordo com o teste de caso múltiplo, ele é identificado somente com determinados equipamentos do usuário (UEs).

1. Os números pagos antecipadamente parecem ter um problema. Os que pertencem ao plano de redirecionamento de perfil de usuário único.
2. Se o usuário tentar acessar qualquer página, ela será redirecionada com a página Cliente com base no agente de usuário. Na extremidade GGSN, há uma ação de cobrança para esta tarefa de redirecionamento e ela não está associada a nenhum Grupo de Classificação. Nesse caso, o uso do usuário também contém o grupo de classificação "0".

Esta é a configuração ausente:

charging-action 431_url_redirect
flow idle-timeout 300
no video cae-readdressing
flow idle-timeout flow-mapping 300
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>content-id 431 its missing which is trigger for the RG 0 in CDR. add this one
no service-identifier
retransmissions-counted
xheader-insert xheader-format msisdn_rat 
billing-action egcdr
no cca charging
content-filtering processing server-group
no qos-class-identifier
no ip tos
no ip tos
no qos-renegotiate traffic-class
flow action redirect-url http://one.airtel.in/net
no flow limit-for-flow-type
no flow limit-for-bandwidth direction downlink
no flow limit-for-bandwidth direction uplink
charge-volume ip bytes 
no nexthop-forwarding-address
no ip vlan
tft-notify-ue
no service-detection session-update


rulebase REDIRECT_PLAN
description ""
#exit
timestamp rounding edr round-off
no ran bandwidth optimize
dynamic-rule order always-first
ip reassembly-timeout 5000
no active-charging rf rating-group-override
no active-charging rf service-id-override
icmp req-threshold 20
no ip reset-tos
no tethering-detection
tcp packets-out-of-order timeout 30000
retransmissions-counted
tcp 2msl-timeout 2
tcp packets-out-of-order transmit immediately
no tcp mss
no tcp proxy-mode
http header-parse-limit 12000
rtsp initial-bytes-limit 6000
no video optimization-preprocessing
wtp packets-out-of-order transmit immediately
wtp out-of-order-timeout 5000
tcp check-window-size
post-processing policy not-for-dynamic-discard
no xheader-encryption certificate-name
no xheader-encryption re-encryption
timestamp rounding egcdr round-off
flow end-condition timeout normal-end-signaling session-end charging-edr edr-flow-format
billing-records egcdr
action priority 3 ruledef 426_1_redirect charging-action 426_charged_with_Gy monitoring-key 2
action priority 4 ruledef 403_1_redirect charging-action 410_charged_with_Gy monitoring-key 2
action priority 5 ruledef 410_1_redirect charging-action 431_charged_with_Gy monitoring-key 2
action priority 7 ruledef 431_1 charging-action 431_charged_with_Gy
action priority 15 ruledef httpua charging-action 431_url_redirect

Seguem-se os elementos CDR:

recordType EGSNPDPRECORD
servedIMSI 405540128802801
ggsnAddress 192.224.40.131
chargingID 157136633
sgsnAddress 192.224.40.136
accessPointNameNI xxxxxgprs.com
pdpType IPV4
servedPDPAddress 10.66.181.167
dynamicAddressFlag TRUE
recordOpeningTime 160906192638+0530
duration 130
causeForRecClosing Management Intervention
recordSequenceNumber 1
nodeID DELGW02
localSequenceNumber 524874817
apnSelectionMode MS or Network Provided and Subscription Verified
servedMSISDN 918933043178
chargingCharacteristics Prepaid
chargingCharSelMode SGSN Supplied
sgsnPLMNIdentifier 405, 54
imei-sv 3562370491918918
RATType GERAN
MSTimeZone +05:30
userLocationInformation 422-54-15-25111

ratingGroup 0
localSequenceNumber 87586425
timeOfFirstUsage 160906192838+0530
timeOfLastUsage 160906192838+0530
timeUsage 0
serviceConditionChange PDP context release
qoSInformationNeg 01 0b 61 1f 73 96 68 68 74 05 ff ff 00 
sgsn-Address 192.224.20.136
sGSNPLMNIdentifier 405, 54
datavolumeFBCUplink 327
datavolumeFBCDownlink 112
timeOfReport 160906192848+0530
rATType GERAN

CDR ELEMENTS FOLLOW
recordType EGSNPDPRECORD
servedIMSI 405540128802801
ggsnAddress 192.234.40.131
chargingID 157136633
sgsnAddress 223.224.40.136
accessPointNameNI xxxxgprs.com
pdpType IPV4
servedPDPAddress 192.66.181.167
dynamicAddressFlag TRUE
recordOpeningTime 160906192848+0530
duration 0
causeForRecClosing Management Intervention
recordSequenceNumber 2
nodeID DELGW02
localSequenceNumber 524874818
apnSelectionMode MS or Network Provided and Subscription Verified
servedMSISDN 918933043178
chargingCharacteristics Prepaid
chargingCharSelMode SGSN Supplied
sgsnPLMNIdentifier 405, 54
imei-sv 3562370491918918
RATType GERAN
MSTimeZone +05:30
userLocationInformation 405-54-15-25111

ratingGroup 800
resultCode 2001
localSequenceNumber 87586426
timeOfFirstUsage 160906192711+0530
timeOfLastUsage 160906192724+0530
timeUsage 13
serviceConditionChange PDP context release
qoSInformationNeg 01 0b 61 1f 73 96 68 68 74 05 ff ff 00 
sgsn-Address 192.124.40.136
sGSNPLMNIdentifier 405, 54
datavolumeFBCUplink 124
datavolumeFBCDownlink 0
timeOfReport 160906192848+0530
rATType GERAN


HEXDUMP-START
00 00 00 01 ....
[V] [M] Charging-Rule-Install 
Code: 0x000003e9 (1001) Charging-Rule-Install
Flags: 0xc0 (192) [V] [M] 
Length: 0x00003c (60)
Vendor-Id: 0x000028af (10415) 3GPP
[V] [M] Charging-Rule-Base-Name 
Code: 0x000003ec (1004) Charging-Rule-Base-Name
Flags: 0xc0 (192) [V] [M] 
Length: 0x000020 (32)
Vendor-Id: 0x000028af (10415) 3GPP
Data: REDIRECT_PLAN

Conclusão

Se em um egcdr de ação de cobrança estiver configurado, mas o ID de conteúdo não estiver, o tráfego de dados será cobrado contra essa ação de cobrança e será relatado em CDRs com grupo de classificação "0".