Improved Automatic Congestion Management.
Support for policy selection through Radius Class AVP
Support for IPv6 subscriber addresses in REST interface
New subscriber monitoring page in Status->Subscribers (Statistics->Subscribers->Metrics deprecated).
DPI statistics of up to one month.
New Powercode integration with better performance.
Integration with Sonar billing system (v2)
Subscriber ID searchable in GUI
Integration with Splynx billing system
Subscriber dashboard window
TCPO Acceleration metrics per service/application
DNS for Powercode & Azotel integration
New Bequant logo in GUI
Azotel: block subscribers without a valid subscription (from 4.6.3).
Faster TCPO metrics (from 4.6.3).
Improved shaping, including improved FQ-CODEL (from 4.6.3).
Azotel billing integration.
Histograms with main client/server IP addresses per service.
Modal charts in Subscriber metrics.
Multiple Powercode equipment categories (from 4.5.2).
ACM enabled for billing dynamic policies (from 4.5.2).
XBox software update DPI signature (from 4.5.2).
New Automatic Congestion Management, based on advanced machine-learning algorithms, to automatically detect congestion situations and, in those case, apply a dynamic limit to mitigate the latency and packet losses caused by the congestion.
New Time Profiles, to allow specifying subscriber flow and rate policies as a function of the day-of-week and the time-of-day
Integration with Powercode billing systems
Integration with Cisco qos-policy RADIUS AVPs
Shaping policies per flow: it is now possible to set a limit per flow, in addition to existing combined limit to all flows of the same subscriber. Applicable to scenarios with NAT.
Sortable data tables more scalable.
In DPI Service Analysis, possibility to exclude DPI samples generated by monitoring policies (to eliminate biases caused by those policies, for example, because of full DPI of specific IPs).
Fixes the issue of slow speeds when doing shaping or rate-limiting when turning off overall TCPO.
Sortable data tables in:
- Status->Flows->Per Subscriber
- Host name
- IPv6 prefix for subscribers
- UDR production rate
Speedtest DPI identification.
Latency per service charts.
Automatic UDR rate production.
Subscriber metrics available via REST API.
Rate-policy profile, to define policy flow rules based on the name of the policy rate of the subscriber.
RADIUS Ascend AVPs supported (data-rate and xmit-rate).
In policy flows, drop rules for Internet-incoming SYN, UDP and IP other flows.
Up to 3 months of Subscriber metrics (usage, latency,retransmission, max speed, flows).
Dynamic policy rate creation from RADIUS.
Overall retransmission metrics.
PPS in Dashboard.
Support of 25 Gbps and 100Gbps with Intel E810 network interfaces.
Better management of REST/API policies and subscribers.
Access to subscriber status and usage from subscriber tables.
DPI for QUIC-IETF and QUIC-vQ050.
DPI for Bittorrent.
Load a policy configuration respecting the server specific configuration (to load the same policies to several BQN servers).
RADIUS client description field.
Automatic Congestion Detection (ML).
Show API policies in GUI.
Show subscriber API policy assignments in GUI.
More graphical dashboard.
Subscriber usage of up to three months.
Status Flow per Subscriber introduced.
Status Subscribers much improved.
Traffic counter improvements.
Burst transition duration.
New Dashboard, with more information and more frequent updates.
REST API includes subscriber and policy IDs.
More IPs in OAM firewall.
Renovated system alarms.
Clearer DoS over time chart.
API Rest can specify rate policy parameters.
Centralized DoS thresholds.
UDR generation in Subscriber monitor policy.
Tracking flows can be subject to shaping.
Subscribers and flows per Policy (Status->Policies).
Subscribers per Policy over time(Status->Subscribers->Per Policy).
Flows per policy over time (Statistics->Flows->Per Policy).
Release Naming Conventions
BQN software release is identified by three digits (e.g., R4.1.1):
- The first digit indicates a mayor release (e.g., Release 4). A major release requires new platform packages (normally it is not compatible with platform packages from previous major releases).
- The second digit indicates a minor release within the major release (e.g., Release 4.1). Contains new functionality and it is compatible with the platform packages of its major release. Simply involves the installation of a BQN package.
- The third digit is a patch number, delivering corrections of the minor release. This is the convention from R4.1 onwards (R4.0 was delivering also functionality using the third digit).