Evanti CAS service is designed to deploy collective WEB-access spots at 64-bit IBM-PC-compatible server platforms. The service allows several subscribers to surf the Web using one satellite equipment kit.
CAS is enabled through close interaction with Evanti’s comprehensive QoS Server solution, the interaction pattern is illustrated below.
VSAT equipment kit
Application server (optional)
Local network users
CAS-to-QoS interaction implies the following sharing of functions:
Subscriber authentication and authorization
Shaping (downlink/uplink management1)
Support of subscriber and CAS operator accounts and balance details
Shaping (downlink/uplink management)
Note that CAS is designed to operate only in bi-directional integration with Evanti QoS Server.
Personal QoS Server account enabling subscriber management and traffic/activity monitoring.
Balance support with automated visualization of results of CAS operator financial transactions.
Bi-directional satellite access to the Internet from any device connectable to LAN or Wi-Fi
Direct registration of new subscribers.
Support of subscriber authorization by network equipment (switch) port or by MAC-address.
Access to personal account web-interface allowing subscribers to select service plans and flexibly configure/manage their services
Balance management interface supporting recharge via electronic payment systems
CAS Server & Network equipment
Equipment requirements are defined for each particular project.
VSAT Equipment Kit Requirements
Requirements to subscriber equipment set for bidirectional connection are determined by the CAS operator.
CAS installation set includes:
Electronic media (CD/DVD/USB) with a distribution package
HASP-key (when installed with Evanti QoS Server)
CAS deployment and configuration are supposed to be carried out by operator staff according to the guide. Configurable parameters are:
External network IP-address on the subscriber side of the bi-directional satellite connection channel (to be agreed upon with the operator)
Internal network IP-address to the switch (assigned by the operator)
Authorization method: IPoE or MAC address
Using Evanti QoS Server or not (if supplied)
Operator can edit the above settings whenever they want in the course of CAS operation. Local network and network equipment configuration are carried out by the CAS operator in compliance with the existing requirements and hardware documentation.
When deployed in compliance with the above, CAS has the following operating parameters:
Centralized satellite earth stations compatible with CAS (by vendor):
Number of supported CAS operators: 1
Estimated subscriber number: up to 50
Subscriber authorization by IPoE or MAC-address, depending on equipment and CAS settings
Downlink MIR unlimited
Uplink MIR up to 50 Mbps
Figures in 3 and 6 above can be increased through enhancing performance of the CAS server.
To enhance performance of a CAS unit, operator may deploy Evanti PEP (performance enhancement proxy). Evanti PEP relies on proprietary approach to user traffic encapsulation. The standard implementation is based on the UDP protocol, but, if necessary (and possible), any other message-based, message/datagram-based, or even a stream-based protocol without mandatory requirements to data delivery guarantees can be used.
We offer a tool that can handle congested channels, minimize QoE (Quality of Experience) impairment caused by long delays and by various network issues that hinder user traffic stream. This solution is complemented by an efficient shaping system that ensures flexible management of bandwidth available to user without applying standard shaping methods that involve packet dropping; thus subscriber experience is not impaired even in environments with limited and fluctuating bandwidth.
Note that Evanti PEP is best used with Evanti QoS Server that implements the traffic shaping functionality. The shaping QoS module instructs the PEP how much data it is capable to accommodate for each user and the PEP applies relevant measures.
The solution includes a server side and a client side. The server side is deployed at the server and can manage multiple simultaneous sessions. The client side is deployed at subscriber terminal and manages session of a specific user.
1Optional, if Evanti QoS Server license is purchased