Preview Tool

Cisco Bug: CSCvu17196 - NRSRNA and USSRNA should always present in MM context

Last Modified

Oct 01, 2020

Products (1)

  • Cisco ASR 5000 Series

Known Affected Releases

Description (partial)

As per TS 29.274 V15.2.0, NRSRNA and USSRNA should always present as part of the Extended Access Restriction Data in MM context regardless of its value. But MME omits to include the flags in MM context when the value of NRSRNA and USSRNA is zero.

During handovers, the target MME performs gateway selection before getting the subscription information from the HSS and hence MME may select the NR capable S-GW for DCNR restricted UE. To prevent this, the peer SGSN will notify the Restriction information (NRSRNA) through the GTP MM context in Identification-Response/Context-Response/Forward-Relocation-Request message to MME. The S3-DCNR support includes both GTPv2 and GTPv1 protocol for S4-SGSN and Gn-SGSN respectively.

- NRSRNA and USSRNA are set as 0 in MM context in the below messages
- FORWARD_RELOCATION_REQUEST and Context Response on S10 interfac
Bug details contain sensitive information and therefore require a 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.