ESM QoS using subscriber and SLA profiles also applies to GTP hosts. SR OS provides various methods to align internal QoS objects with 3GPP signaling of UL/DL APN-AMBR values:
The incoming APN-AMBR from GTP can be reflected in RADIUS and Diameter. Additionally, this can be mapped to an SR OS QoS override using the command configure subscriber-mgmt gtp apn-policy apn ambr-qos-mapping. This uses generic QoS overrides, meaning that a subsequent QoS-override from AAA, for example, removes this mapping again.
The APN-AMBR IE signaled in Gx can similarly be mapped to QoS overrides using the command configure subscriber-mgmt diameter-application-policy gx 3gpp-qos-mapping. This has precedence over the similar GTP command.
The APN-AMBR IE signaled in outgoing GTP messages is derived from either local QoS objects, a Gx/radius signaled value, the incoming GTP APN-AMBR, or default values under configure subscriber-mgmt gtp peer-profile mme qos ambr, in that priority order. The mapping of local QoS objects to APN-AMBR is done with the command configure subscriber-mgmt sla-profile egress/ingress report-rate.
Values for QCI and ARP can be reflected from AAA or default values can be configured under configure subscriber-mgmt gtp peer-profile mme qos arp/qci. There is no interaction with local QoS objects.
SR OS maintains the FC classification and in- and out-of-profile markings consistent over the two dataplane passes. The egress and ingress QoS policies in the SLA profile should be configured with the following considerations.
Enable de-mark for access egress and map each FC to the dot1p as defined in Table: FC to dot1p mapping, therefore ensuring that the GTP-U encapsulated packet uses the same classification as the ESM context.
Perform classification for access ingress based on dot1p as defined in Table: FC to dot1p mapping and enable in-profile and de-1-out-of-profile for each FC, therefore ensuring that the ESM context uses the same classification as determined for the GTP-U packet. However, a different classification scheme can be used, if required; for example, based on DSCP or IP criteria.
| FC | dot1p |
|---|---|
be |
0 |
l2 |
1 |
af |
2 |
l1 |
3 |
h2 |
4 |
ef |
5 |
h1 |
6 |
nc |
7 |