Collision Between Original QCI and Remapped QCI

If there is a collision between existing bearer with new bearer with the same QCI or mapped QCI, SMF rejects some QoS flow configurations based on the following conditions:

  • If the PCF sends a QCI, which gets remapped to an existing QCI associated with a flow or bearer, the SMF rejects the creation of the bearer or any QCI upgrade or downgrade request.

  • If the PCF sends a QCI for the creation of a new bearer/flow, and there is already an existing flow/bearer with the same remapped QCI, the SMF rejects the PCF's request for creating the new bearer.

  • Given that the SMF is configured to remap QCI=x to QCI=y and QCI=z to QCI=y, if the PCF sends a rule with QCI=x, resulting in the creation of a flow/bearer, any subsequent request from the PCF with QCI=z is rejected by the SMF.

Example: The following remapping configuration is not allowed/accepted by the system:
  • profile qos qosp-ims
       qosflow qi5 131 nas-remap 131
  • profile qos qosp-ims
       qosflow qi5 131 nas-remap 132
       qosflow qi5 132 nas-remap 131
  • profile qos qosp-ims
       qosflow qi5 131 nas-remap 132
       qosflow qi5 132 nas-remap 133

For more information, see the Remapping Nonstandard QCI to Standard QCI.