Guest

Preview Tool

Cisco Bug: CSCuj16864 - PGW EGCDR: Incorrect QoS after 4G to 3G HO if QoS in UPCReq is different

Last Modified

Feb 05, 2017

Products (1)

  • Cisco ASR 5000 Series

Known Affected Releases

15.0(1)

Description (partial)

Symptom:
If different QoS is sent in UPCReq during 4G to 3G HO then correct QoS (QoS before HO) is reported  in CDR generated due to HO, however in the next CDR generated on call clear/ or Interim after HO contains the same QoS ( QoS before HO), it should contain the changed QoS.

Conditions:
1. Bring up an LTE call with one default and one dedicated bearer( MBR/ GBR [UL/DL]= 10kbps ).
2. Send some data over both bearers.
3. Change QoS of the rule on dedicated bearer by sending RAR( MBR/ GBR [UL/DL]= 1kbps ), one CDR is released for dedicated bearer with QoS change and QoS= 10kbps as expected.
4. At this point in "show sub pgw-only full all", the new QoS i.e. 1 kbps is seen as expected.
5. Again send data hitting the rule on dedicated bearer.
5. 4G to 3G HO.
6. Say during HO, in GTP_UPDATE_PDP_CONTEXT_REQ_MSG the QoS=( MBR/ GBR [UL/DL]= 10kbps ) is sent and same is positively responed in GTP_UPDATE_PDP_CONTEXT_RES_MSG.
7. One CDR is released with correct QoS (QoS before HO).
8. After HO in "show sub ggsn-only full all" the QoS sent in UPC_Req is seen.
  Negotiated MBR for up (bps): 10000       Negotiated MBR for down (bps): 10000 

9. Send some more data and perform HO back to 4G or clear the call in 3G itself.
10. In the released CDR the oldQoS i.e. ( MBR/ GBR [UL/DL]= 1kbps ) is shown
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.