Url-Based Re-Addressing - Cisco ASR 5000 Series Administration Manual

Enhanced Charging Service Overview
In case of IP fragmentation, packets with successful IP re-assembly will be re-addressed. However, IP fragmentation
failure packets will not be re-addressed.
New hierachy approach has also been provided for selecting the server in case of server list configured under charging-
action. This helps the operator to specify list of DNS servers in the order of preference. In hierarchy based approach,
queries are redirected as per primary, secondary, and tertiary selection. Both round-robin and hierarchy based server
selection approaches would be applicable for both IPv4 and IPv6 based servers. An additional CLI is provided that
enables you to select from hierarchy or round-robin approach for server selection. See the Configuring IP Readdressing
for more information.

URL-based Re-addressing

URL-based re-addressing feature is applied based on L7 rule matching for HTTP URLs in addition to re-addressing
charging action based on L3/L4 rule matching. HTTP request with specific token or complete URL must be redirected
to a separate server and must be transparent to the UE.
Flow-based re-addressed connection
Flow-based re-addressed connection is the default behavior of this feature. In this type, after a HTTP connection is setup
with Original Server, all subsequent requests will be sent to it until the URL-based re-addressing rule matches. This
behavior holds true even for multiple concatenated HTTP requests in one packet.
The following call flow explains the URL HTTP Request Re-addressing feature.
Figure 8. URL HTTP Request Re-addressing
Cisco ASR 5x00 Enhanced Charging Services Administration Guide ▄
Enhanced Features and Functionality ▀
43