Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Configuring HTTP Header Enrichment Overview

You configure HTTP header enrichment by configuring tag rules and an HCM profile that points to specific tag rules. Tag rules identify the HTTP enrichment actions to take when the conditions in the tag rule are matched. For subscriber traffic under static policy control, a tag rule is used if it is included in the HCM profile specified in a PCC rule that the traffic matches. For subscribers under dynamic policy control, a message from the PCRF identifies the configured HCM profile to use for HTTP header enrichment.

Support added in Junos OS Release 20.2R1 for only the insertion of IPv4 or IPv6 tags user addresses in an HTTP headers. No other tags are supported in this release for Next Gen Services.

If you change the configuration of tag rules during an existing subscriber data session, the changes do not impact the existing session. The configuration changes are used by any new subscriber data sessions.

To configure HTTP header enrichment for a subscriber:

  1. Configure one or more tag rules to specify the HTTP header enrichment actions.

    See Configuring Tag Rules.

  2. Configure an HCM profile and assign tag rules to it.

    See Configuring HCM Profiles and Assigning Tag Rules.

  3. (For subscribers under static policy control) Assign the HCM profile to a PCC action profile.

    See Configuring Policy and Charging Control Action Profiles For Junos OS Subscriber Aware.

  4. (For subscribers under static policy control) Configure a PCC rule that includes the PCC action profile.

    See Configuring Policy and Charging Control Rules.

  5. Enable HTTP enrichment for a subscriber’s service set.

    See Applying Services to Subscriber-Aware Traffic with a Service Set.

Related Documentation

Release History Table
Release
Description
20.2R1
Support added in Junos OS Release 20.2R1 for only the insertion of IPv4 or IPv6 tags user addresses in an HTTP headers. No other tags are supported in this release for Next Gen Services.