UPF blocks all traffic if QER doesn't contain MBR

[pirog-spb]

Describe the bug After upgrate free5gc SMF sends two QER per PDR. eUPF ignores second QER and applies only first. First QER has no MBR param. That's why UPF decides to drop all traffic in this PDR.

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior

• [ ] eUPF does't block traffic if QER have no MBR param
• [ ] eUPF prints corrent Session Establish Request params in logs

Screenshots If applicable, add screenshots to help explain your problem.

Logs

upf  | Session Establishment Request:
upf  |   CreatePDR ID: 1 
upf  |     Outer Header Removal: 0 
upf  |     FAR ID: 1 
upf  |     QER ID: 2 
upf  |     Source Interface: 0 
upf  |     TEID: 1 
upf  |     Ipv4: 10.100.200.14 
upf  |     Ipv6: <nil> 
upf  |   CreatePDR ID: 2 
upf  |     FAR ID: 2 
upf  |     QER ID: 2 
upf  |     Source Interface: 1 
upf  |     UE IPv4 Address: 10.60.0.1 
upf  |   CreateFAR ID: 1 
upf  |     Apply Action: [2] 
upf  |     Forwarding Parameters:
upf  |       Network Instance: internet 
upf  |   CreateFAR ID: 2 
upf  |     Apply Action: [2] 
upf  |     Forwarding Parameters:
upf  |   CreateQER ID: 1 
upf  |     Gate Status DL: 0 
upf  |     Gate Status UL: 0 
upf  |     Max Bitrate DL: 100000 
upf  |     Max Bitrate UL: 200000 
upf  |     QFI: 0 
upf  |   CreateQER ID: 2 
upf  |     Gate Status DL: 0 
upf  |     Gate Status UL: 0 
upf  |     QFI: 1 

Environment (please complete the following information):

• 5GC kind and version: free5gc smf:v3.3.0
• UPF version: v0.3.2

Additional context PFCP dump: dump.zip

[pirog-spb]

According to PFCP spec it's possible to have several QER ID in PDR:

This IE shall be present if a QoS enforcement or QoS marking action shall be applied to packets matching this PDR.
When present, this IE shall contain the QER IDs to be associated to the PDR. Several IEs within the same IE type may be present to represent a list of QERs to be associated to the PDR.