Limitations

The Dynamic QoS Flow Based Application Detection and Control feature has the following limitations:

  • In case both ADC start or stop and non-ADC Usage-report(vol/time threshold) come from UPF in same session-report, it is not deterministic weather first ADC report or Non-ADC report is processed. When both ADC and non-ADC report come in a session-report, smf-service pod posts two internal events ADC event and non-ADC usage-report event. Infra creates two separate go-routines to process both events. But it is not deterministic which go-routine is going to be scheduled first, because of this limitation, some times Non-ADC usage-report is processed before ADC report or the other way around.

  • When APP-Start and App-Stop event for two separate App-Id's are received from UPF in same session-report request, SMF informs both(Start and Stop) events in same SmPolicyUpdateReq to PCF. APP_STA and APP_STO are sent in repPolicyCtrlReqTriggers IE.\, this is a global IE. Since PCF has history of receiving APP_STA and APP_STO, it can link the APP_STO to the appId for which an APP_STA already received. APP_STA trigger is applicable to the appId for which PCF has not received a start indication.