Cisco Cisco Packet Data Gateway (PDG) Nota Di Rilascio
MME Changes in Release 15.0
MME Enhancements for 15.0 MR6 ▀
Cisco ASR 5x00 Release Change Reference ▄
287
CSCur38243 - MME discards
EGTP_CREATE_INDIRECT_DATA_FORWARDING_TUNNEL_RSP
Feature Changes
Extended Validation Options for UL F-TEID during HO
Up Link - Fully qualified Tunnel End Point Identifier
Previous Behavior:
The MME did not accept ‘up link fully qualified tunnel end point identifier’ (UL F-TEID) in a Create Indirect
Data Forwarding Response and response was dropped).
The MME would only accept a UL F-TEID in a Create Indirect Data Forwarding Response from the S-GW if the
IE instance was 4 and the interface type was set at 28 (SGW GTP-U interface for UL data forwarding).
New Behavior: The validation process has been modified so that the MME now accepts UL F-TEID in a Create
Indirect Data Forwarding Response during intra-EUTRAN handover. So, the MME does not drop the response if the IE
of the UL F-TEID instance is 4 and the interface type is set to either 28 (SGW GTP-U interface for UL data forwarding)
or 1 (S1-U SGW GTP-U interface).
Indirect Data Forwarding Response during intra-EUTRAN handover. So, the MME does not drop the response if the IE
of the UL F-TEID instance is 4 and the interface type is set to either 28 (SGW GTP-U interface for UL data forwarding)
or 1 (S1-U SGW GTP-U interface).
Customer Impact: The MME will accept a broader range of responses from the S-GW.
CSCur50736 - PDN Connectivity Reject : Incorrect ESM cause#27
Feature Changes
Configuring ESM Cause Code #27
In general, much of the UE behavior depends on factory configuration; for example, some operator-tied phones consider
APN subscriptions as RAT specific. But many operators have configured APN as RAT agnostic. This behavior changes
allows some operator flexibility to handle either type of UE configuration.
APN subscriptions as RAT specific. But many operators have configured APN as RAT agnostic. This behavior changes
allows some operator flexibility to handle either type of UE configuration.
Previous Behavior: By default, the MME sent cause code value #27 (Unknown or Missing APN) in standalone PDN
Connectivity Reject messages when the UE requested APN was not subscribed for that subscriber.
Connectivity Reject messages when the UE requested APN was not subscribed for that subscriber.
New Behavior: As part of the MME’s local cause code mapping, a new cause code option can be configured -
"Requested-Option-Not-Subscribed" cause code value #33. When the new option is configured, then the MME sends
cause code #33 (Requested Service Option Not Subscribed) in the standalone PDN Connectivity Reject message
whenever the UE-requested APN is not subscribed. If the option is not configured, then by default the MME uses the
cause code value #27 (Unknown or Missing APN) in standalone PDN Connectivity Reject message when the UE-
requested APN is not subscribed.
"Requested-Option-Not-Subscribed" cause code value #33. When the new option is configured, then the MME sends
cause code #33 (Requested Service Option Not Subscribed) in the standalone PDN Connectivity Reject message
whenever the UE-requested APN is not subscribed. If the option is not configured, then by default the MME uses the
cause code value #27 (Unknown or Missing APN) in standalone PDN Connectivity Reject message when the UE-
requested APN is not subscribed.
Command Changes
local-cause-code-mapping
The new keyword
apn-not-subscribed
is added to specify the local cause-code mapping when the UE-requested
APN is not subscribed for that subscriber. If cause code mapping for
apn-not-subscribed
is explicitly configured
with requested-service-option-not-subscribed in either the Call-Control-Profile or MME-Service configuration mode,