Content Filtering is an in-line service available for 3GPP and 3GPP2 networks to filter HTTP
requests from mobile subscribers based on the URLs in the requests. This enables
operators to filter and control the content that an individual subscriber can access, so
that subscribers are inadvertently not exposed to universally unacceptable content
and/or content inappropriate as per the subscribers’ preferences.
The Content Filtering functionality remains the same as implemented in the non-CUPS architecture. For more information, refer
to Content Filtering Support Overview chapter in the CF Administration Guide.
Configuring the Content Filtering
Use the following additional configuration to enable the content filtering:
configure
require user-plane content-filtering
content-filtering category database directory path path_address
content-filtering category database max-version version_number
end
Note
|
The above configuration must be configured on the User Plane, during boot time, to enable Content Filtering. Defining the
above configuration post the User Plane configuration will lead to errors and inconsistencies.
|
Note
|
To enable the feature, license for User Plane as well as existing content filtering license is required on Uplane.
|
Note
|
For ICSR User Plane 1:1, the database is loaded pn both the UP's, separately. The rest of the Content Filtering configurations
on Control Plane remains the same. The Content Filtering configuration is pushed from Control Plane to active the User Plane
and then to standby User Plane.
|
Configuration on Control Plane
The following sample configuration demonstrates changes required on Control Plane for Content Filtering:
config
active-charging-service ACS
content-filtering category policy-id 1
analyze priority 1 category ABOR
analyze priority 2 category ADVERT action allow
analyze priority 2 category ADVERT action allow action content-insert "Content Restricted : The Web Guard feature has been enabled on your line. Web Guard has restricted your access to this content. The person on your Wireless account who is designated as the Primary Account Holder can disable this restriction through the account management website"
exit
rulebase cisco
content-filtering mode category static-only
content-filtering flow-any-error permit
content-filtering category policy-id 5
The configuration on the Control Plane is pushed to User Plane using the PFD mechanism.
Use the following show commands to validate the content filtering configuration on User Plane:
Use the following show commands to check the CFDB spawning on User Plane:
-
show content-filtering category database facility srdbmgr
-
show content-filtering category database verbose debug-only
-
show content-filtering category database verbose
-
show content-filtering category database url
-
show content-filtering category url
The Content Filtering policy ID received from PCRF for a particular subscriber is sent to User Plane during call establishment.
The PFCP messages Sx establishment request/Sx modify request contains the CF Policy ID.
Use the following command to check the CF Policy Id on User Plane:
show subscribers user-plane-only callid full all
The following filed is displayed in support of Content Filtering in CUPS:
Use the following show commands to monitor the SRDB Request/Response/CF Polict actions:
-
show user-plane-service inline-services content-filtering category statistics
-
show user-plane-service inline-services content-filtering category statistics rulebase name
-
show content-filtering category statistics
-
show content-filtering category statistics facility srdbmgr instance 1
-
show content-filtering category statistics volume all
Note
|
All existing bulk statistics defined for Content Filtering in the non-CUPS architecture is also applicable in CUPS.
|
Feedback