для Cisco Cisco Packet Data Gateway (PDG)
Evolved Packet Data Gateway Engineering Rules
▀ GTPv2 Restrictions
▄ ePDG Administration Guide, StarOS Release 17
108
GTPv2 Restrictions
The following are known restrictions for the creation and use of GTPv2:
The ePDG does not send the Modify Bearer Command towards PGW for the modification of QoS or APN
AMBR for the default bearer when triggered by HSS to ePDG and then to PGW.
The ePDG does not have the partial failure (FQ-CSID failure) handling.
The ePDG does not support allowing the UE to have more than one PDN connection with one APN.
The ePDG does not supports "Subscriber Tracing" per 3GPP standards.
The ePDG does not have any policy (QoS) enforcement mechanism. However ePDG does communicates the
subscribed QoS profile, APN-AMBR as received from AAA to the PGW. Also ePDG does keeps the QCI to
DSCP mapping and negotiated QCI, which it uses for DSCP and 802.1p marking for the UL traffic. Downlink
traffic marking will be done at PGW and ePDG shall be copying the DSCP marking from inner IP packet to
outer ESP packet header when sending to UE. ePDG will not uses the configured DSCP to QCI mapping for
the downlink direction.
DSCP mapping and negotiated QCI, which it uses for DSCP and 802.1p marking for the UL traffic. Downlink
traffic marking will be done at PGW and ePDG shall be copying the DSCP marking from inner IP packet to
outer ESP packet header when sending to UE. ePDG will not uses the configured DSCP to QCI mapping for
the downlink direction.
The ePDG does not have any CAC/Admission control functionality.
The ePDG does not supports handling the piggy backed message as per 3GPP spec, its not clearly mentioned to
use the same for the ePDG. ePDG does expects the separate create bearer request message post handling of
create session request and response for the creation of dedicated bearer.
create session request and response for the creation of dedicated bearer.