Cisco Cisco Packet Data Interworking Function (PDIF)
MME Changes in Release 17
▀ MME Enhancements for 17.4
▄ Release Change Reference, StarOS Release 17
256
PDN Connectivity Reject: 3
PTI Already in Use: 1 Unknown or Missing APN: 0
Unknown PDN Type: 0 Invalid Bearer Id: 0
Invalid PTI: 0 Rejected By PGW/SGW: 0
Authentication Failed: 0 Svc Opt Not Supported: 0
Svc Opt Not Subscribed: 0 Opr Determined Barring: 0
Insufficient Resource: 0 Activation Rejected: 0
Svc Opt Tmp OutOfOrder: 0 Protocol Errors: 0
APN Restrict Incomt: 0 Multiple PDN conn not allowed: 1
Other Reasons: 1
CSCuu48619 - MME Rejects UBR During a Handover Collision between S10-HO
and X2-HO
Feature Changes
Enable TAU to Continue on Receiving X2 HO
Scenario:
After SRNS handover from 3G, the MME rejects a received Update Bearer Request with the following failure
cause: EGTP_CAUSE_TEMP_REJECTED_DUE_TO_HANDOVER_IN_PROGRESS.
Then the QoS from the HSS is not applied to the subscriber.
After the SRNS handover from 3G is performed, when the UE does a TAU, the MME waits to receive a TAU
Complete message from the UE. But the MME only receives an X2/S1 HO.
Previous Behavior: If the MME received X2 HO /S1 HO while TAU Accept was being retried, then after completion
of inbound MME relocation the TAU Accept retries were aborted and not retried after X2 HO/ S1 HO. Also, if X2/S1
HO occurred before TAU Complete was received then the HSS-provided subscribed QoS is not applied.
of inbound MME relocation the TAU Accept retries were aborted and not retried after X2 HO/ S1 HO. Also, if X2/S1
HO occurred before TAU Complete was received then the HSS-provided subscribed QoS is not applied.
New Behavior: If the MME receives X2 HO /S1 HO while TAU Accept is being retried, then after completion of
inbound MME relocation the TAU Accept retries will proceed after completion of S1 HO / X2 HO provided the HO
happens from the same TAI as the TAU. Also, if X2/S1 HO occurred before TAU Complete was received then the
HSS-provided subscribed QoS are applied.
inbound MME relocation the TAU Accept retries will proceed after completion of S1 HO / X2 HO provided the HO
happens from the same TAI as the TAU. Also, if X2/S1 HO occurred before TAU Complete was received then the
HSS-provided subscribed QoS are applied.
CSCuu51391 - Scaling support for Cell Tracing
Feature Changes
Cell Traffic Trace