Cisco Cisco Packet Data Gateway (PDG) Veröffentlichungshinweis
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
MVG Changes in Release 15.0
▀ MVG Enhancements for September 30, 2013
▄ Cisco ASR 5x00 Release Change Reference
352
MVG Enhancements for September 30, 2013
MVG Feature Changes as of September 30, 2013
This section provides information on MVG feature changes in release 15.0.
Important:
For more information regarding features in this section, refer to the MVG Administration Guide for
this release.
New MVG Features
This section identifies new MVG features available in release 15.0.
MVG CAE Video Re-addressing Without Full TCP Proxy
With this release, the MVG video re-addressing feature does not require a TCP proxy connection for the entire duration
of the flow. The video re-addressing functionality towards CAE is invoked only on the first HTTP video request, and
response. Thereafter, the rest of the packets do not need the proxy functionality, and TCP proxy is dynamically disabled
as soon as a response packet is received from the CAE.
of the flow. The video re-addressing functionality towards CAE is invoked only on the first HTTP video request, and
response. Thereafter, the rest of the packets do not need the proxy functionality, and TCP proxy is dynamically disabled
as soon as a response packet is received from the CAE.
Once connection is setup with CAE and proxy is disabled, MVG still keeps monitoring all requests and inserts MVG x-
headers to all requests (both video and non-video) being forwarded to CAE. X-headers are required for CAE to access
the requested content from the Origin server (OS) if needed. MVG x-headers will be added to both pipelined and non-
pipelined (both video and non-video) requests once connection is setup with CAE and proxy is disabled.
headers to all requests (both video and non-video) being forwarded to CAE. X-headers are required for CAE to access
the requested content from the Origin server (OS) if needed. MVG x-headers will be added to both pipelined and non-
pipelined (both video and non-video) requests once connection is setup with CAE and proxy is disabled.
MVG Platform Support
The following are the platform support for the MVG CAE video re-addressing, and the MVG video pacing features:
CAE Video Re-addressing: This feature is now qualified to run on the Cisco ASR 5000 chassis for PSC2 and
PSC3 integrated with GGSN, P-GW, and SAE-GW (if MVG is running on P-GW) products. To use this
feature in a combination of GGSN, P-GW, and HA products, MVG should run on GGSN or P-GW.
feature in a combination of GGSN, P-GW, and HA products, MVG should run on GGSN or P-GW.
Video Pacing: This feature is now qualified to run on ASR 5000 and ASR 5500 chassis integrated with GGSN,
P-GW, SAE-GW (if MVG is running on P-GW), HA, and IPSG (ASR 5000 only) products. To use this feature
in a combination of GGSN, P-GW, and HA products, MVG should run on GGSN or P-GW.
in a combination of GGSN, P-GW, and HA products, MVG should run on GGSN or P-GW.
MVG Interworking With Cisco Inlet CAE
With this release, the Mobile Video Gateway Inline service is fully qualified to interwork with the Cisco Inlet Content
Adaptation Engine (CAE) for video optimization and re-addressing.
Adaptation Engine (CAE) for video optimization and re-addressing.
Dynamic Disabling of TCP Proxy
With this release, TCP proxy can be disabled during the middle of the HTTP flow for the MVG CAE video re-
addressing feature. The video re-addressing functionality towards CAE is invoked only on the first HTTP video request
(connection establishment and x-header insertion), and response. As the rest of the flow to the CAE does not require a
TCP proxy, it is disabled. This leads to the overall improvement of the system performance.
addressing feature. The video re-addressing functionality towards CAE is invoked only on the first HTTP video request
(connection establishment and x-header insertion), and response. As the rest of the flow to the CAE does not require a
TCP proxy, it is disabled. This leads to the overall improvement of the system performance.