Cisco Cisco Packet Data Interworking Function (PDIF) Guía Para Resolver Problemas
GGSN Support in GPRS/UMTS Wireless Data Services
▀ Features and Functionality - Optional Enhanced Feature Software
▄ Cisco ASR 5000 Series Gateway GPRS Support Node Administration Guide
OL-22943-01
Higher bandwidth requirements of streaming audio and video delivery
Efficient broadcast and multicast mechanisms, to conserve resources in the RAN
MBMS represents the evolutionary approach to multicast and broadcast service delivery. MBMS uses spectrum
resources much more efficiently than Multicast-over-Unicast by optimizing packet replication across all critical
components in the bearer path. Thus, services requiring largely uni-directional multicast flows towards the UE are
particularly well suited to the MBMS approach. These would include news, event streaming, suitably
encoded/compressed cable/radio programs, video-on-demand, multi-chat / group-push-to-talk/video-conferencing
sessions with unicast uplink and multicast downlink connections, and other applications.
resources much more efficiently than Multicast-over-Unicast by optimizing packet replication across all critical
components in the bearer path. Thus, services requiring largely uni-directional multicast flows towards the UE are
particularly well suited to the MBMS approach. These would include news, event streaming, suitably
encoded/compressed cable/radio programs, video-on-demand, multi-chat / group-push-to-talk/video-conferencing
sessions with unicast uplink and multicast downlink connections, and other applications.
For MBMS functionality, the system supports the Gmb interface, which is used signal to the BM-SC
I
MPORTANT
:
For more information on this feature, refer Multicast Broadcast Service chapter in System Enhanced
Feature Configuration Guide.
Overcharging Protection on Loss of Coverage
This solution provides the ability to configure mobile carriers to maximize their network solutions and balancing the
requirements to accurately bill their customer.
requirements to accurately bill their customer.
Considerin a scenario where a mobile is streaming or downloading very large files from external sources and the mobile
goes out of radio coverage. If this download is happening on Background/Interactive traffic class then the GGSN is
unaware of such loss of connectivity as SGSN does not perform the Update PDP Context procedure to set QoS to 0kbps
(this is done when traffic class is either Streaming or Conversational only). The GGSN continues to forward the
downlink packets to SGSN. In the loss of radio coverage, the SGSN will do paging request and find out that the mobile
is not responding; SGSN will then drops the packets. In such cases, the G-CDR will have increased counts but S-CDR
will not. This means that when operators charge the subscribers based on G-CDR the subscribers may be overcharged.
This feature is implemented to avoid the overcharging in such cases.
goes out of radio coverage. If this download is happening on Background/Interactive traffic class then the GGSN is
unaware of such loss of connectivity as SGSN does not perform the Update PDP Context procedure to set QoS to 0kbps
(this is done when traffic class is either Streaming or Conversational only). The GGSN continues to forward the
downlink packets to SGSN. In the loss of radio coverage, the SGSN will do paging request and find out that the mobile
is not responding; SGSN will then drops the packets. In such cases, the G-CDR will have increased counts but S-CDR
will not. This means that when operators charge the subscribers based on G-CDR the subscribers may be overcharged.
This feature is implemented to avoid the overcharging in such cases.
This implementation is based on Cisco-specific private extension to GTP messages and/or any co-relation of G-CDRs
and S-CDRs. It also does not modify any RANAP messages.
and S-CDRs. It also does not modify any RANAP messages.
I
MPORTANT
:
For more information on this feature, refer Subscriber Overcharging Protection chapter in System
Enhanced Feature Configuration Guide.
Proxy Mobile IP
Mobility for subscriber sessions is provided through the Mobile IP protocol as defined in RFCs 2002-2005. However,
some older Mobile Nodes (MNs) do not support the Mobile IP protocol. The Proxy Mobile IP feature provides a
mobility solution for these MNs.
some older Mobile Nodes (MNs) do not support the Mobile IP protocol. The Proxy Mobile IP feature provides a
mobility solution for these MNs.
For IP PDP contexts using Proxy Mobile IP, the MN establishes a session with the GGSN as it normally would.
However, the GGSN/FA performs Mobile IP operations with an HA (identified by information stored in the subscriber's
profile) on behalf of the MN (i.e. the MN is only responsible for maintaining the IP PDP context with the GGSN, no
Agent Advertisement messages are communicated with the MN).
However, the GGSN/FA performs Mobile IP operations with an HA (identified by information stored in the subscriber's
profile) on behalf of the MN (i.e. the MN is only responsible for maintaining the IP PDP context with the GGSN, no
Agent Advertisement messages are communicated with the MN).