Release Note для Cisco Cisco Packet Data Gateway (PDG)
S-GW Changes in Release 15.0
▀ S-GW Enhancements for September 30, 2013
▄ Cisco ASR 5x00 Release Change Reference
556
UDP Port Extension header helps in handling the Error-Indication message efficiently. If any GTP-U peer supports this
extension header, then sending this extension header in Error-Indication message will help in processing the Error-
Indication message.
extension header, then sending this extension header in Error-Indication message will help in processing the Error-
Indication message.
Support for Supported Extension Headers Notification message helps notify the GTP-U peer about the GT-U
capabilities of the node. This message is sent only in case the node was required to interpret a mandatory extension
header (by setting the comprehension required in extension header), but the node was not yet upgraded to support that
extension header.
capabilities of the node. This message is sent only in case the node was required to interpret a mandatory extension
header (by setting the comprehension required in extension header), but the node was not yet upgraded to support that
extension header.
Bearer Context to be Modified IE in MBR Message
The Modify Bearer Request message can be triggered by the UE time zone, ULI and/or RAT Type in the
TAU/RAU/Handover without S-GW change procedure. In these procedures, there is no need to include the Bearer
Context to be Modified IE.
TAU/RAU/Handover without S-GW change procedure. In these procedures, there is no need to include the Bearer
Context to be Modified IE.
Previous Behavior: The S-GW included the MBR message without change procedure.
New Behavior: The Bearer Context to be Modified IE is not included in the MBR message over the S5/S8 interfaces for
a TAU/RAU/HO without S-GW change procedure.
a TAU/RAU/HO without S-GW change procedure.
Create Indirect Data Forwarding Tunnel Response Change
The Create Indirect Data Forwarding Tunnel Response message can now have cause value set to “Request accepted
partially”.
partially”.
EPS Bearer ID and ARP Support in DDN
This feature allows support for Priority Paging support in the network. This is mainly needed for MPS subscriber
support. The paging priority in the paging message is set by MME based on ARP received in Downlink Data
Notification message.
support. The paging priority in the paging message is set by MME based on ARP received in Downlink Data
Notification message.
In order to support MPS requirement for Priority Paging in the network for MPS subscriber, DDN message has been
enhanced to support passing ARP and EBI information. When the S-GW sends a Downlink Data Notification message,
it shall include both EPS Bearer ID and ARP. If the Downlink Data Notification is triggered by the arrival of downlink
data packets at the S-GW, the S-GW shall include the EPS Bearer ID and ARP associated with the bearer on which the
downlink data packet was received. If the Downlink Data Notification is triggered by the arrival of control signaling, the
S-GW shall include the EPS Bearer ID and ARP, if present in the control signaling. If the ARP is not present in the
control signaling, the S-GW shall include the ARP in the stored EPS bearer context. If multiple EPS Bearers IDs are
reported in the Downlink Data Notification message, the S-GW shall include all the EBI values and the ARP associated
with the bearer with the highest priority (lowest ARP value). For more information, see TS 23.401 (section 5.3.4.3) and
29.274 (section 7.2.11). Details are discussed in CR-859 of 3GPP specifications.
enhanced to support passing ARP and EBI information. When the S-GW sends a Downlink Data Notification message,
it shall include both EPS Bearer ID and ARP. If the Downlink Data Notification is triggered by the arrival of downlink
data packets at the S-GW, the S-GW shall include the EPS Bearer ID and ARP associated with the bearer on which the
downlink data packet was received. If the Downlink Data Notification is triggered by the arrival of control signaling, the
S-GW shall include the EPS Bearer ID and ARP, if present in the control signaling. If the ARP is not present in the
control signaling, the S-GW shall include the ARP in the stored EPS bearer context. If multiple EPS Bearers IDs are
reported in the Downlink Data Notification message, the S-GW shall include all the EBI values and the ARP associated
with the bearer with the highest priority (lowest ARP value). For more information, see TS 23.401 (section 5.3.4.3) and
29.274 (section 7.2.11). Details are discussed in CR-859 of 3GPP specifications.
GTPv2 Cause IMSI Not Known Changed to IMSI/IMEI Not Known
When the UE is UICC-less and emergency attached, there is no valid IMSI. So it is not possible to provide the IMSI in
the related messages like Change Notification Requests. In this case, the IMEI is included in these messages. If the
IMEI is not known in the target side, the correct cause should be returned to the source side.
the related messages like Change Notification Requests. In this case, the IMEI is included in these messages. If the
IMEI is not known in the target side, the correct cause should be returned to the source side.
Previous Behavior: GTPv2 cause was previously 'IMSI not known'
New Behavior: The cause “IMSI not known” is changed to “IMSI/IMEI not known” and changed in the related
response messages.
response messages.
Higher Bitrates Than 16 Mbps Flag