VAS Cloud Protocol Module

1. Storage of Cloud Protocol Base
2. Obtaining cloud protocol updates from the Cloud Protocol Preparation and Update Service, followed by updating the Cloud Protocol Base.
3. Storage of protocol databases of all operators for which there is customization (cloud + customy protocols).
4. Updating protocol databases on DPI operators through the Protocol Download Service.

Cloud protocols are created and updated in VAS Experts Lab, the current database is available to all customers with technical support. Periodic updates require settings on the DPI to access the VAS Cloud Protocol Module. Update occurs 1 time per day, or more often in accordance with the Agreement. List of protocols.

Custom protocols are created by the client’s administrator or VAS Experts engineers in agreement with the client in the client’s GUI. With the help of custom protocols, flexibility, efficiency and accuracy of settings are achieved, as well as they serve to implement the operator’s business cases. Traffic management using custom protocols is implemented to unify settings in the interface and improve DPI performance. Custom protocol is currently defined by IP+port (CIDR), SNI and ASN. The architecture of SSG DPI allows you to supplement these parameters at the request of the customer. Instructions for creating custom protocols with examples.
When creating custom protocols, the Protocol Base for this operator is allocated to a separate storage, since the creation of custom protocols can affect the composition of cloud protocols for correct operation.

1. Custom protocol takes precedence over other protocol types.
2. When you add a list of resources for the custom protocol on the VAS Cloud side, the availability of these resources in existing protocols is checked. In the presence of intersections, notification occurs, which must be analyzed to avoid collisions between polysing and statistics, since when applying settings, resources will subsequently be determined under the new custom protocol and will not fall under the influence of those protocols where they were previously located. For example:
   
3. The creation time of the custom protocol on the DPI after sending from the GUI is about 15 minutes, readiness can be tracked by process statuses (see instructions). Time is driven by processes:
   1. By preparing a new protocol tree for the client, a customized version of cloud protocols is created, the resources of which are transferred to custom protocols.
   2. Create binary files Protocol databases for download to DPI (5 files with lists: IP, SNI, ASN, protocol name, legitimate resources)
   3. Upload time of files about 100 MB to DPI from VAS Cloud.