Throughput Limiting

If you have configured a secondary authentication on the SMF, then the SMF sends the RADIUS access request to ISE based on the configured RADIUS server address. SMF includes PEI in the access request, if available. The configured IMEI-based ISE includes the name of the rule that is to be applied on the private 5G network to achieve the throughput limiting.

Note

Throughput limiting can use either IMEI or IMSI.

ISE populates the rule name in the 3GPP-Policy-Reference attribute in the access accept request. You can configure this rulebase in SMF. SMF derives the ASCII value from the octet string included in the 3GPP-Policy-Reference attribute. Then, SMF matches this value with the configured rulebase.

Following table lists the octet values for the 3GPP-Policy-Reference AVP.

3GPP-Policy-Reference AVP

Bits

Octets

8

7

6

5

4

3

2

1

1

3GPP Type = 113

2

3GPP Length = m

3-m

Policy Data Reference (octet string)

Note
DN AAA sends the policy data reference value. SMF uses this value to retrieve the SM and QoS policy data in the PCF.

The ISE sends the rulebase to SMF. If the SMF receives the rulebase that is not configured, then the SMF ignores it. If you have not configured the default bandwidth policy on SMF, then the bandwidth policy is ignored.

You can configure the bandwidth limit on SMF when a UE attaches through the 4G RAT or 5G RAT. Based on the bandwidth limit configured through the 4G RAT, the SMF populates the BearerQoS value in the Create Session response. Based on the bandwidth limit configured through the 5G RAT, the SMF populates the QosFlowDescription value in the N1 PDU Establishment Accept request.

Bandwidth limiting is configured locally on UPF based on the predefined rule that SMF sends.