To enable the URL blacklisting feature on User Plane (UP), URL blacklisting database should be present with a name “optblk.bin” under flash, or SFTP or under its sub-directory. This database directory
path needs to be configured on user-plane, after user-plane services are brought up.
HTTP Analyzer must be enabled for URL blacklisting. The HTTP analyzer extracts URL information from the incoming HTTP request data packet. Extracted URL content is compared
with the URL Blacklisting database. Once the incoming HTTP data packet’s URL matches with the database URL entry, that URL is treated as blacklisted URL and one of the following actions takes place on that HTTP packet.
-
Termination of flow
-
Packet is discarded
The URL blacklisting configurations must be configured on Control Plane (CP), Rulebase configuration under Active Charging Service. Additionally,
two URL blacklisting methods – Exact and Generic, are supported at Active Charging Service-level configuration, on CP. These CLI configurations
are pushed to UP through PFD mechanism, during Sx association procedure, to the CP.
Important |
Blacklisting database(s) are provided by – IWF (Internet Watch Foundation) and NCMEC (National Center for Missing and Exploited Children).
The ASR5500, CUPS UP always receives the blacklisting DB in Optimized Format (optimized blacklisting DB format).
|
URL Blacklisting Database Upgrade
URL database upgrade is supported in 2 ways:
Timer-based or Auto-upgrade
After the database is loaded on the chassis for the first time, a timer, for a duration of 5 minutes, is started. This process
is started to auto upgrade the database.
If at the expiry of the timer, a valid database with higher version is available at the directory path, then database upgrade
procedure is initiated, and a newer version of the database is loaded on the UP chassis.
To upgrade a URL blacklisting database, a higher version of valid URL Blacklisting database with name “optblk_f.bin” should be present at same directory as that of current database “optblk.bin”.
After the database is upgraded successfully, the earlier “optblk.bin” file gets renamed as “optblk_0.bin” and “optblk_f.bin”
file gets renamed as “optblk.bin”. Here, “optblk_0.bin” file is treated as a backup file of older database.
If one more upgrade is performed, then “optblk_0.bin” file will be renamed as “optblk_1.bin” file and current “optblk.bin”
will get renamed as “optblk_0.bin”, and so on.
The number of backup files to be stored in the database can be configured using the max-versions CLI on UP.
CLI-based or Manual Upgrade
In this upgrade method, the CLI command - upgrade url-blacklisting database , upgrades the current database to a newer version.