Cisco Cisco ASR 5500
Mobile Video Gateway Overview
Features and Functionality ▀
MVG Administration Guide, StarOS Release 17 ▄
17
The CAE video re-addressing feature works in conjunction with the dynamic TCP proxy feature to send video requests
to the CAE cluster without using HTTP redirection, so that the re-addressing to the CAEs remains transparent to the
video clients on the subscriber UEs.
to the CAE cluster without using HTTP redirection, so that the re-addressing to the CAEs remains transparent to the
video clients on the subscriber UEs.
The TCP proxy is used only for connection initiation. The CAE re-addressing functionality is invoked only on the first
HTTP video request and response, after which 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.
HTTP video request and response, after which 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.
For persistent connections with continuous requests from the UE, once a connection is established with the CAE for
processing the first video request, TCP proxy is disabled and the connection with the CAE is kept active until the end of
the flow. Both video and non-video requests are processed by a CAE that is capable of processing both types of
requests.
processing the first video request, TCP proxy is disabled and the connection with the CAE is kept active until the end of
the flow. Both video and non-video requests are processed by a CAE that is capable of processing both types of
requests.
Platform Requirements
In 12.3 and 14.0 releases, the CAE Video Re-addressing feature is supported on GGSN, P-GW, HA, and IPSG products
as a lab demo/ lab trial feature only. This feature is not fully qualified and is not supported for field deployment.
as a lab demo/ lab trial feature only. This feature is not fully qualified and is not supported for field deployment.
In 15.0 and later releases, the MVG CAE Video Re-addressing feature is 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.
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.
License Requirements
CAE Video Re-addressing is a licensed Cisco feature. It requires the Video Optimization license or the ECS Header
Enrichment license to insert specific x-headers in the HTTP message before forwarding the request to the CAE. Contact
your Cisco account representative for detailed information on specific licensing requirements. For information on
installing and verifying licenses, refer to the Managing License Keys section of the Software Management Operations
chapter in the System Administration Guide.
Enrichment license to insert specific x-headers in the HTTP message before forwarding the request to the CAE. Contact
your Cisco account representative for detailed information on specific licensing requirements. For information on
installing and verifying licenses, refer to the Managing License Keys section of the Software Management Operations
chapter in the System Administration Guide.
HTTP X-Header Use in CAE Video Re-addressing
To enable the CAE to reach an OS to retrieve selected video clips for adaptation, the Mobile Video Gateway inserts the
Layer 3 destination IP address and Layer 4 destination port number of the OS in a proprietary HTTP x-header in the
HTTP video request to the CAE. The CAE uses the information to recreate the Layer 3 and 4 headers to connect to the
OS.
Layer 3 destination IP address and Layer 4 destination port number of the OS in a proprietary HTTP x-header in the
HTTP video request to the CAE. The CAE uses the information to recreate the Layer 3 and 4 headers to connect to the
OS.
The following figure shows how the HTTP x-header is used in CAE video re-addressing to the CAE. In this example, in
the original HTTP request from the subscriber UE, the source IP address is 10.1.1.233 and the destination IP address is
200.2.3.4. The destination TCP port is 8080.
the original HTTP request from the subscriber UE, the source IP address is 10.1.1.233 and the destination IP address is
200.2.3.4. The destination TCP port is 8080.