Product Description
Licenses
Summary of Mobile Video Gateway Features and Functions
Network Deployments and Interfaces
The Mobile Video Gateway in an E-UTRAN/EPC Network
The Mobile Video Gateway in a GPRS/UMTS Network
The Mobile Video Gateway in a CDMA2000 Network
Mobile Video Gateway Logical Network Interfaces
| Interface | Description |
|---|---|
|
PCRF Interface
|
The Mobile Video Gateway
can use the Gx interface to connect to a PCRF (Policy and Charging
Rules Function) server to receive subscriber policy information and
charging rules.
|
|
RADIUS Interface
|
The Mobile Video Gateway
uses a RADIUS interface to exchange signaling messages with the
external RADIUS server.
|
|
Video Origin Server Interface
|
The Mobile Video Gateway
uses the Gi or SGi interface to connect to the video origin servers
in the network. The Mobile Video Gateway also uses the Gi or SGi interface
to connect to non-video origin servers.
|
|
CAE Interface
|
The Mobile Video Gateway
uses a Cisco-enhanced HTTP interface called the Ua interface to
connect to the Cisco CAE. The Cisco CAE is an optional component of
the Cisco Mobile Videoscape.
|
Features and Functionality
Deep Packet Inspection
CAE Video Re-addressing
IMPORTANT:
Platform Requirements
License Requirements
HTTP X-Header Use in CAE Video Re-addressing
Mobile Video Gateway to the CAE
CAE Video Re-adressing Call Flows
Video Request Re-addressing
|
Step
|
Description
|
|---|---|
|
1—3
|
UE sets up a TCP connection
with Origin Server by sending SYN. The TCP three-way handshake takes
place between UE and the Origin Server.
|
|
4
|
UE sends a HTTP request
to the OS for “video_url” which passes
through the MVG. This request could take the form of an HTTP GET.
|
|
5—8
|
MVG recognizes that
the request is for video content. MVG breaks/ closes the
existing TCP connection with OS and establishes a new connection
with CAE.
|
|
9
|
MVG now proxies the
request with additional information like the congestion information
etc. (x-headers) to the CAE that is configured to provide optimized
video.
CAE can then either
send its stored copy of response or fetch it from OS (in case the response
is not cached before or is cached but is stale).
|
|
10
|
CAE processes, optimizes,
and streams the video in real time back to the MVG.
|
|
11
|
MVG proxies the content
back to the UE.
|
|
12
|
UE closes the TCP connection.
|
|
13
|
MVG closes the connection
with CAE.
|
Video Response Re-addressing
|
Step
|
Description
|
|---|---|
|
1—3
|
UE sets up a TCP connection
with Origin Server by sending SYN. The TCP three-way handshake takes
place between UE and the Origin Server.
|
|
4
|
UE sends a HTTP request
to the OS for “video_url” which passes
through the MVG. This request could take the form of an HTTP GET.
|
|
5
|
MVG sends the request
to the origin server.
|
|
6—11
|
MVG analyzes the response
and checks the response for video content.
If the response contains
video content, the MVG breaks/closes the existing connection with
OS and establishes a new connection with CAE. The request with additional
information like the congestion information etc. (x-headers) is
then steered to one of the CAE servers configured on the system.
The CAE can either send
its stored copy of response or fetch it from OS (in case the response
is not cached before or is cached but is stale).
|
|
12
|
CAE processes, optimizes,
and streams the video in real time back to the MVG.
|
|
13
|
MVG proxies the content
back to the UE.
|
|
14
|
UE closes the TCP connection.
|
|
15
|
MVG closes the connection
with CAE.
|
Bulkstatistics Support
CAE Load Balancing
CAE Load Balancer Function
CAE Health-Check Monitoring Function
Video Optimization Policy Control
Functional Overview
Video White-listing
Video Pacing
Platform Requirements
Video Pacing Operation
Video Pacing Functions
Video Pacing Call Flows
Interactions with Related Functions
Supported Video Container File Formats
TCP Link Monitoring
TCP Link Monitoring System Flow
Functional Overview
Bandwidth Estimation
Statistical Logging
Dynamically-enabled TCP Proxy
N+1 Stateful Redundancy
Mobile Video Statistics
Bulk Statistics for Mobile Video
How the Mobile Video Gateway Works
Mobile Video Gateway with the Content Adaptation Engine
DPI of HTTP GET Request Identifying a Non-Video Request (MVG with the CAE)
| Step | Description |
|---|---|
|
1.
|
The UE creates a TCP
connection with the OS.
|
|
2.
|
The Mobile Video Gateway
receives an HTPP GET request from the UE. The Mobile Video Gateway
performs DPI and identifies it as a non-video request (the DPI on
GET/POST fails).
|
|
3.
|
The Mobile Video Gateway
forwards the HTTP request to the OS transparently, using the URL
source IP address as the client address and the destination IP address
as the OS address.
|
|
4.
|
The OS responds with
an HTTP 200 OK, including the content of the page.
|
|
5.
|
The Mobile Video Gateway
forwards the HTTP 200 OK to the UE transparently. The connection
is not proxied, and the TCP flow continues to the UE.
|
DPI of HTTP RESPONSE Identifying a Non-Video Request (MVG with the CAE)
| Step | Description |
|---|---|
|
1.
|
The UE creates a TCP
connection with the OS.
|
|
2.
|
The Mobile Video Gateway
receives an HTPP GET request from the UE. The Mobile Video Gateway
performs DPI and cannot determine whether it is a video request.
|
|
3.
|
The Mobile Video Gateway
forwards the HTTP request to the OS transparently, using the URL
source IP address as the client address and the destination IP address
as the OS address.
|
|
4.
|
The OS responds with
an HTTP 200 OK, including the content of the page. The Mobile Video
Gateway performs DPI again and identifies it as a response to a
non-video request (the DPI on the RESPONSE headers fails).
|
|
5.
|
The Mobile Video Gateway
forwards the HTTP 200 OK to the UE transparently. The connection
is not proxied, and the TCP flow continues to the UE.
|
DPI of HTTP GET Request Identifying a Video Request (MVG with the CAE)
| Step | Description |
|---|---|
|
1.
|
The UE creates a TCP
connection with the OS.
|
|
2.
|
The Mobile Video Gateway
receives an HTPP GET request from the UE. The Mobile Video Gateway
performs DPI and identifies it as a video request (the DPI on GET/POST succeeds).
|
|
3.
|
The TCP connection gets
proxied. The Mobile Video Gateway closes the TCP connection with
the OS and opens a new one with the CAE.
|
|
4.
|
The Mobile Video Gateway
sends the original HTTP GET request to the CAE with x-headers for
transport, quality, and UE identity.
|
|
5.
|
The CAE creates a TCP
proxy connection with the OS.
|
|
6.
|
The CAE sends the original
HTTP GET request from the UE to the OS.
|
|
7.
|
The CAE processes the
HTTP RESPONSE packets from the OS and performs video optimization.
|
|
8.
|
The Mobile Video Gateway
performs additional video optimization and sends the optimized packets
to the UE.
|
DPI of HTTP RESPONSE Identifying a Video Request (MVG with the CAE)
| Step | Description |
|---|---|
|
1.
|
The UE creates a TCP
connection with the OS.
|
|
2.
|
The Mobile Video Gateway
receives an HTPP GET request from the UE. The Mobile Video Gateway
performs DPI and cannot determine whether it is a video request.
|
|
3.
|
The Mobile Video Gateway
forwards the HTTP request to the OS transparently, using the URL
source IP address as the client address and the destination IP address
as the OS address.
|
|
4.
|
The OS responds with
an HTTP 200 OK. The Mobile Video Gateway performs DPI again and
identifies it as a response to a video request (the DPI on the RESPONSE
headers succeeds).
|
|
5.
|
The TCP connection gets
proxied. The Mobile Video Gateway closes the TCP connection with
the OS and opens a new one with the CAE.
|
|
6.
|
The Mobile Video Gateway
sends the original HTTP GET request to the CAE with x-headers for
transport, quality, and UE identity.
|
|
7.
|
The CAE creates a TCP
proxy connection with the OS.
|
|
8.
|
The CAE sends the original
HTTP GET request from the UE to the OS.
|
|
9.
|
The CAE processes the
HTTP RESPONSE packets from the OS and performs video optimization.
|
|
10.
|
The Mobile Video Gateway
performs additional video optimization and sends the optimized packets
to the UE.
|
Mobile Video Gateway without the Content Adaptation Engine
DPI of HTTP GET Request Identifying a Non-Video Request (MVG without the CAE)
| Step | Description |
|---|---|
|
1.
|
The UE creates a TCP
connection with the OS.
|
|
2.
|
The Mobile Video Gateway
receives an HTPP GET request from the UE. The Mobile Video Gateway
performs DPI and identifies it as a non-video request (the DPI on
GET/POST fails).
|
|
3.
|
The Mobile Video Gateway
forwards the HTTP request to the OS transparently, using the URL
source IP address as the client address and the destination IP address
as the OS address.
|
|
4.
|
The OS responds with
an HTTP 200 OK, including the content of the page.
|
|
5.
|
The Mobile Video Gateway
forwards the HTTP 200 OK to the UE transparently. The connection
is not proxied, and the TCP flow continues to the UE.
|
DPI of HTTP RESPONSE Identifying a Non-Video Request (MVG without the CAE)
| Step | Description |
|---|---|
|
1.
|
The UE creates a TCP
connection with the OS.
|
|
2.
|
The Mobile Video Gateway
receives an HTPP GET request from the UE. The Mobile Video Gateway
performs DPI and cannot determine whether it is a video request.
|
|
3.
|
The Mobile Video Gateway
forwards the HTTP request to the OS transparently, using the URL
source IP address as the client address and the destination IP address
as the OS address.
|
|
4.
|
The OS responds with
an HTTP 200 OK, including the content of the page. The Mobile Video
Gateway performs DPI again and identifies it as a response to a
non-video request (the DPI on the RESPONSE headers fails).
|
|
5.
|
The Mobile Video Gateway
forwards the HTTP 200 OK to the UE transparently. The connection
is not proxied, and the TCP flow continues to the UE.
|
DPI of HTTP GET Request Identifying a Video Request (MVG without the CAE)
| Step | Description |
|---|---|
|
1.
|
The UE creates a TCP
connection with the OS.
|
|
2.
|
The Mobile Video Gateway
receives an HTPP GET request from the UE. The Mobile Video Gateway
performs DPI and identifies it as a video request (the DPI on GET/POST succeeds).
|
|
3.
|
The Mobile Video Gateway
forwards the HTTP request to the OS transparently, using the URL
source IP address as the client address and the destination IP address
as the OS address.
|
|
4.
|
The OS responds with
an HTTP 200 OK.
The Mobile Video Gateway
proxies the TCP connection and the HTTP RESPONSE packets are processed
through the video optimization features.
|
|
5.
|
The Mobile Video Gateway
forwards the HTTP 200 OK to the UE.
|
|
6.
|
The optimized TCP video
flow continues to the UE.
|
DPI of HTTP RESPONSE Identifying a Video Request (MVG without the CAE)
| Step | Description |
|---|---|
|
1.
|
The UE creates a TCP
connection with the OS.
|
|
2.
|
The Mobile Video Gateway
receives an HTPP GET request from the UE. The Mobile Video Gateway
performs DPI and cannot determine whether it is a video request.
|
|
3.
|
The Mobile Video Gateway
forwards the HTTP request to the OS transparently, using the URL
source IP address as the client address and the destination IP address
as the OS address.
|
|
4.
|
The OS responds with
an HTTP 200 OK. The Mobile Video Gateway performs DPI again and
identifies this as a response to a video request (the DPI on the
RESPONSE headers succeeds).
The Mobile Video Gateway
proxies the TCP connection and the HTTP RESPONSE packets are processed
through the video optimization features.
|
|
5.
|
The Mobile Video Gateway
forwards the HTTP 200 OK to the UE.
|
|
6.
|
The optimized TCP video
flow continues to the UE.
|