The Transactional Rule Matching (TRM) feature is enhanced to support response-based TRM for HTTP protocol. This feature is applicable to all HTTP transactions of a method type for the subscriber, when an HTTP method is configured for response-based TRM. A configurable option is provided to limit the behavior to HTTP methods configured for response-based TRM.

TRM gets engaged on the HTTP request packet and all further packets in the HTTP transaction bypass rule matching. The same rule is matched and charging-action is applied as that of the HTTP request.

With this release, a new variant of TRM is introduced, where engagement of TRM can be delayed till HTTP response is received. When response-based TRM is configured for a subscriber, TRM gets engaged on the first complete HTTP response packet. The same rule and charging action is applied to all further packets in the HTTP transaction.

• Response-based TRM is supported only for the HTTP protocol. There is no capability to selectively enable response-based TRM for some HTTP transactions of a particular HTTP method type and not to other transactions of the same method for a subscriber.

• Response-based TRM will support pipelined HTTP requests (both concatenated and non-concatenated). This will also support persistent HTTP connections. For pipelined HTTP requests of different HTTP methods, this feature will be applied only to those HTTP methods for which it is configured.

• Response-based TRM can be enabled for subscribers classified according to the APN, Virtual-APN, Rulebase, or a combination of these.

• The transactional-rule-matching response command is added in the ACS Trigger Action configuration mode to delay engagement of TRM for the flow.

• The show active-charging analyzer statistics name http command displays the count if the feature has been applied to the different HTTP transactions based on HTTP request methods.

The service-scheme framework configuration is required to configure and enable the Response-based Charging feature for a subscriber. This framework is introduced to disassociate the dependency with rulebase/PCRF and update the policies specific to subscribers based on pre-configured events. For more information on the service-scheme framework, see the ECS Administration Guide.

This section describes the Response-based TRM configuration. The Service Scheme framework configuration is required to configure and enable this feature for a subscriber.

Use the sample configuration to enable the response-based TRM feature for a subscriber on a particular rulebase.

configure
   active-charging service s1
      trigger-action ta1
         transactional-rule-matching response http all
      #exit
      trigger-condition tc1
         any-match = TRUE
      #exit
      service-scheme ss1
         trigger sess-setup
            priority 1 trigger-condition tc1 trigger-action ta1
         #exit
      #exit
      subs-class sc1
         rulebase = rb1
      #exit
      subscriber-base sb1
         priority 1 subs-class sc1 bind service-scheme ss1
      #exit

Notes:

• The transactional-rule-matching command configured in the rulebase that handles the subscriber for response-based TRM must be functional.

• If the transactional-rule-matching command is not configured in the rulebase for a subscriber, response-based TRM will not be applicable to the subscriber.

Use the following configuration in the ACS Trigger Action Configuration mode to delay engagement of TRM for the flow.

configure
   active-charging service service_name
      trigger-action trigger_action_name
         [ no ] transactional-rule-matching response http { all | connect | delete | get | head | options | post | put | trace }
         exit

• To disable the feature for the subscriber, configure the following command:

  no transactional-rule-matching response http all

• The response-based TRM feature applies to the following HTTP methods:

  • all - Applies to all HTTP methods

  • connect - HTTP Connect method

  • delete - HTTP Delete method

  • get - HTTP Get method

  • head - HTTP Head method

  • options - HTTP Options method

  • post - HTTP Post method

  • put - HTTP Put method

  • trace - HTTP Trace method

This section provides information on the show commands available to support this feature.