Data Path Enforcement

The following is the sequence for the data traffic enforcement performed at UPF.

  1. Verify whether the incoming data traffic matches the http ruledef.

  2. Check if there is a QGR with the matched ruledef or group of ruledefs. If a match is found, the highest priority QGR is returned.

    Note

    The ruledef or group of ruledefs can be either static or predefined.

  3. If the QGR matches, then Flow-Action enforcement is first performed at Charging-Action level and then at QGR level assuming Charging-Action has allowed the packet. If the packet is dropped, then QGR-level Flow-Action enforcement is skipped.

  4. If Flow-Action at QGR allows the packet to pass, then the Bandwidth Limiting or QoS Enforcement Rule (QER) Limiting is enforced on the data packet. If it is dropped at QGR, QER Limiting is skipped.

  5. Unlike the Flow-Action enforcement, the QER Limiting is also performed first at Charging-Action Level and then at the QGR subject to packet being allowed at Charging-Action.