How It Works
Following are the steps that describe the DSCP markings for the collapse calls.
-
In case of Collapse call:
-
For ACCESS side, QCI-QOS mapping table associated with SGW-service is used.
-
For CORE side, QCI-QOS mapping table associated with PGW-service is used.
-
-
The preceding conditions apply once you enable the feature, otherwise QCI-QOS mapping table associated with PGW-service is applicable for both sides.
-
APN associated QCI-QOS mapping table is preferred over the P-GW service QCI-QOS mapping table.
-
APN-Profile associated QCI-QOS mapping table is preferred over SGW-Service QCI-QOS mapping table for ACCESS side DSCP markings.
-
In case, only P-GW service has QCI-QOS mapping table configuration, then these DSCP markings is applicable on both ACCESS & CORE side for collapse call.
-
In case only S-GW service has QCI-QOS mapping table configuration then these DSCP markings is applicable on ACCESS side for collapse call.
-
There’s a new configurable parameter inside the SAEGW service which indicates whether the feature is enabled or disable.
-
For Pure-P to Collapse HO and conversely, transport layer markings are updated in FAR as a part of Sx Modify request.
-
Layer2 markings are also modified based on QCI-QOS mapping table picked for ACCESS and CORE side.
-
DSCP markings continue to apply on existing bearers post session recovery.
-
DSCP markings continue for the bearers on standby chassis once it switches to active mode.