Content Aware Edge (CAE)
Native Subscriber and Radio Access Network (RAN) Awareness
The Movik Content Aware Edge (CAE) leverages its network location between the RAN and packet core to gain intelligence in real time from the network and subscribers, including the following attributes:
- Device/User Equipment
- Radio network condition detection
- Session/Mobility information
- Content/Application being accessed by subscribers
With this information, the CAE is able to make traffic and content decisions without requiring integration with other network elements over proprietary interfaces. By reusing standards-based interfaces to gather subscriber and network information, the CAE enables operators to manage traffic at the network entry point, improving the subscriber’s quality of experience (QoE) and best leveraging their network assets.
Content and Application Scheduling
The CAE incorporates a sophisticated content and application scheduling engine to ensure that the requested content is delivered to the subscriber over the RAN in the most efficient manner. This occurs by taking into account the dynamic and varying nature of the RAN conditions and devices in a mobile network.
The capabilities of the CAE include:
- Transparent application proxy/gateway
- Adaptive video pacing
- Patent-pending network aware content scheduling and rate control
- Streaming proxy
Movik’s patent-pending RAN-aware content scheduling increases RAN utilization and throughput, while improving the quality and consistency of the subscriber experience.
Intelligent Traffic Management and Steering
The CAE enables an operator to intelligently manage and steer traffic at the edge of the mobile network. By leveraging the real-time subscriber, content, and RAN awareness capabilities of the CAE, operators can set up precise policies to pick the optimal path for different types of traffic before it enters the packet core.
For example, content may be served from a local cache, offloaded to the Internet, or directed to the service plane by bypassing the packet core. Traffic management and steering policies may be defined along multiple dimensions, including type of content, URL, type of application, subscriber class, device type, etc.