In 21.19.1 and later releases, the following three new parameters are added in large TODR:

1. International Mobile Subscriber Identity (IMSI)

2. Flow-ID and Flow-ID list

3. User Location Information (ULI)

   The Flow-ID is used to correlate the ACS Flow ID that is visible in End Point Detection and Response ("sn-flow-id" attribute) and then the ULI is correlated with RAN counters.

Note	These new fields are only available in Large TODRs generated on non-VPP based P-GW and SAEGW.

All TODR attributes of traffic optimization is enabled by a single CLI command. The output is always comma separated, and in a rigid format.

Standard TODR

The following is the format of a Standard TODR:

instance_id,flow_type,srcIP,dstIP,policy_id, proto_type, dscp,
flow_first_pkt_rx_time_ms,flow_last_pkt_rx_time_ms,flow_cumulative_rx_bytes 

Example:

1,0,173.39.13.38,192.168.3.106,0,1,0,
 1489131332693,1489131335924,342292 

Where:

• instance_id : Instance ID.

• flow_type : Standard flow (0)

• srcIP : Indicates the source IP address.

• dstIP : Indicates the destination IP address.

• policy_id : Indicates the traffic optimization policy ID.

• proto_type: Indicates the IP protocol being used. The IP protocols are: TCP and UDP.

• dscp : Indicates the DSCP code for upstream packets.

• flow_first_pkt_rx_time_ms : Indicates the timestamp when the first packet was detected during traffic optimization.

• flow_last_pkt_rx_time_ms : Indicates the timestamp when the last packet was detected during traffic optimization.

• flow_cumulative_rx_bytes : Indicates the number of bytes transferred by this flow.

Large TODR

The following is a sample output of a Large TODR.

19,1,404005123456789,22.22.0.1,1.1.1.8,custom1,2,0,1588858362158,1588858952986,16420806,1588858364162,419,351,7000,0,0,1,
19:2:15,2,0,0,2,1,1,16:0x12546300012345,
1588858364162,80396,1472,0,0,0,2,1,16:0x12546300012345,1588858366171,146942,1937,7000,0,0,2 

Where:

• instance_id : Instance ID.

• flow_type : Large flow (1)

• imsi_id : Indicates the International Mobile Subscriber Identity.

• srcIP : Indicates the source IP address.

• dstIP : Indicates the destination IP address.

• policy_name : Identifies the name of the configured traffic optimization policy.

• policy_id : Indicates the traffic optimization policy ID.

• proto_type : Indicates the IP protocol being used. The IP protocols are: TCP and UDP.

• dscp : Indicates the DSCP code for upstream packets.

• flow_first_pkt_rx_time_ms : Indicates the timestamp when the first packet was detected during traffic optimization.

• flow_last_pkt_rx_time_ms : Indicates the timestamp when the last packet was detected during traffic optimization.

• flow_cumulative_rx_bytes : Indicates the number of bytes transferred by this flow.

• large_detection_time_ms : Indicates the timestamp when the flow was detected as Large.

• avg_burst_rate_kbps : Indicates the average rate in Kbps of all the measured bursts.

• avg_eff_rate_kbps : Indicates the average effective rate in Kbps.

• final_link_peak_kbps : Indicates the highest detected link peak over the life of the Large flow.

• recovered_capacity_bytes : Indicates the recovered capacity in Kbps for this Large flow.

• recovered_capacity_ms : Indicates the timestamp of recovered capacity for this Large flow.

• acs_flow_id_count : Indicates the number of ACS Flow IDs present in this TODR. A maximum of 20 ACS Flow IDs is present.

• acs_flow_id_list : Indicates the list of individual ACS Flow IDs. For example, acs_flow_id1, acs_flow_id2, and so on.

• phase_count : Indicates the Large flow phase count.

• min_gbr_kbps : Indicates the Minimum Guaranteed Bit Rate (GBR) in Kbps.

• max_gbr_kbps : Indicates the Maximum Guaranteed Bit Rate (MBR) in Kbps.

• phase_count_record : Indicates the number of phases present in this record.

• end_of_phases : 0 (not end of phases) or 1 (end of phases).

• Large flow phase attributes:

  • phase_type : Indicates the type of the phase. This field represents that the flow was in one of the following three possible states where each state is represented by a numeric value:

    • 0 - Ramp-up Phase (if the Flow was previously idle)

    • 1 - Measurement Phase (required)

    • 2 - Flow Control Phase (if congestion detected during Measurement Phase)

  • uli_type : Indicates the type of ULI.

  • phase_start_time_ms : Indicates the timestamp for the start time of the phase.

  • burst_bytes : Indicates the burst size in bytes.

  • burst_duration_ms : Indicates the burst duration in milliseconds.

  • link_peak_kbps : Indicates the peak rate for the flow during its life.

  • flow_control_rate_kbps : Indicates the rate at which flow control was attempted (or 0 if non-flow control phase). This field is valid only when flow is in ‘Flow Control Phase’.

  • max_num_queued_packets : Identifies the maximum number of packets queued.

  • policy_id : Identifies the traffic optimization policy ID.

Cisco Ultra Traffic Optimization algorithm monitors the traffic and automatically transitions between Base and Extended policy parameters based on the following logic:

1. Start with base policy.

2. If measurement phase burst rate > extended link profile initial-rate then move to the extended policy.

3. If measurement phase burst rate < base link profile max-rate then move to the base policy.

4. Repeat steps 2,3 for every measurement phase.

   .

Policy Selection

Cisco’s Ultra Traffic Optimization engine provides two default policies – Managed and Unmanaged. When Unmanaged policy is selected, traffic optimization is not performed.

When Managed policy is selected, traffic optimization is performed using default parameters. Managed policy is applied when a policy is not specified in a Trigger Action where traffic optimization is enabled without specifying a policy.

When Managed policy is selected, traffic optimization is performed using default parameters. Managed policy is applied when a policy is not specified in a Trigger Action where traffic optimization is enabled without specifying a policy.

• Session Setup Trigger – If a Trigger Action is applied only for a Session Setup in a Service-Schema, then the trigger action is only applied to new sessions only.

• Bearer Setup Trigger – If a trigger action is applied only for a Bearer Setup, changes in the trigger action will be applicable to newly created bearers and its flows.

• Flow Creation Trigger – Under a trigger condition corresponding to a flow create, conditions can be added based on a rule-name, local-policy-rule or an IP protocol in addition to the trigger condition: any-match.

When traffic optimization on existing flows is disabled because of a trigger condition, then the traffic optimization engine will apply the default Unmanaged policy on them.

Deleting a Policy

Before deleting a Policy profile, all association to a traffic optimization policy should be removed.

For more information on deletion of a policy, refer to the Traffic Optimization Policy Configuration section.

The following sections describes the required configurations to support the Multi-Policy Support.

In this StarOS 21.23 release, the following show commands and bulk statistics schema counters are enhanced to show Rx/Tx packet statistics for Uplink and Downlink for UDP and TCP split in Cisco Ultra Traffic Optimization solution.

• show active-charging traffic-optimization counters sessmgr all

• show active-charging traffic-optimization counters tcp sessmgr all

• show active-charging traffic-optimization counters udp sessmgr all

The any-match = TRUE , a wildcard configuration, is the only supported condition for this trigger and so this is applicable to all the flows of the subscriber.

Following is a sample configuration:

configure 
    active-charging service service_name 
       service-scheme service_scheme_name 
            trigger sess-setup 
                priority priority_value trigger-condition trigger_condition_name1 trigger-action trigger_action_name 
                exit 
            trigger-condition trigger_condition_name1 
                any-match = TRUE 
                exit 
            trigger-action sess-setup 
            traffic-optimization policy sess-setup 
                exit 

The trigger conditions related to QCI can be used for this trigger, and so this is applicable to all the flows of specific bearers.

The following is a sample configuration:

configure 
    active-charging service service_name 
        trigger-action trigger_action_name 
            traffic-optimization 
            exit 
        trigger-condition trigger_condition_name1 
            any-match = TRUE 
            exit 
        trigger-condition trigger_condition_name2 
            qci = qci_value 
            exit 
        service-scheme service_scheme_name 
            trigger bearer-creation 
                priority priority_value trigger-condition trigger_condition_name2 trigger-action trigger_action_name 
                exit 
            exit 
        subs-class sub_class_name 
            apn = apn_name 
            exit 
        subscriber-base subscriber_base_name 
            priority priority_value subs-class sub_class_name bind service-scheme service_scheme_name 
            end 

The trigger conditions related to rule-name and QCI can be used here, and so this is related to specific flow.

The following is a sample configuration:

configure 
    active-charging service service_name 
        trigger-action trigger_action_name 
            traffic-optimization 
            exit 
        trigger-condition trigger_condition_name1 
            any-match = TRUE 
            exit 
        trigger-condition trigger_condition_name2 
            qci = qci_value 
            exit 
        trigger-condition trigger_condition_name3 
            rule-name = rule_name 
            exit 
        service-scheme service_scheme_name 
            trigger bearer-creation 
                priority priority_value trigger-condition trigger_condition_name3 trigger-action trigger_action_name 
                exit 
            exit 
        subs-class sub_class_name 
            apn = apn_name 
            exit 
        subscriber-base subscriber_base_name 
            priority priority_value subs-class sub_class_name bind service-scheme service_scheme_name 
            end 

Notes:

• trigger_condition_name3 can have only rules, only QCI, both rule and QCI, or either of rule and QCI.

The following table illustrates the different levels of Traffic Optimization and their corresponding Subscriber Class configuration and Triggers.

subs-class sc1 
    any-match = TRUE 
    exit 

subs-class sc1 
    rulebase = prepaid 
    exit 

subs-class sc1 
    apn = cisco.com 
    exit 

trigger-condition TC1 
    qci = 1 
    exit 

trigger-condition TC1 
    qci = 1 
    rule-name = tcp 
    multi-line-or all-lines 
    exit 

Important

In case of LTE to eHRPD handover, since QCI is not valid for eHRPD, it is recommended to configure rule-name as the trigger-condition under service-scheme.

The show active-charging traffic-optimization counters sessmgr { all | instance number } CLI command is introduced where:

• counters – Displays aggregate flow counters/statistics from Cisco Ultra Traffic Optimization engine.

Important

This CLI command is license dependent and visible only if the license is loaded.

Following are the new field/counters:

• Traffic Optimization Flows:

  • Active Normal Flow Count

  • Active Large Flow Count

  • Active Managed Large Flow Count

  • Active Unmanaged Large Flow Count

  • Base Policy:

    • Active Large Flow Count

    • Active Managed Large Flow Count

    • Active Unmanaged Large Flow Count

  • Extended Policy:

    • Active Large Flow Count

    • Active Managed Large Flow Count

    • Active Unmanaged Large Flow Count

  • Total Normal Flow Count

  • Total Large Flow Count

  • Total Managed Large Flow Count

  • Total Unmanaged Large Flow Count

  • Base Policy:

    • Total Large Flow Count

    • Total Managed Large Flow Count

    • Total Unmanaged Large Flow Count

  • Extended Policy:

    • Total Large Flow Count

    • Total Managed Large Flow Count

    • Total Unmanaged Large Flow Count

  • Total IO Bytes

  • Total Large Flow Bytes

  • Total Recovered Capacity Bytes

  • Total Recovered Capacity ms

On executing the above command, the following new fields are displayed for the Multi-Policy Support feature:

Important

This CLI command is license dependent and visible only if the license is loaded.

• TCP Traffic Optimization Flows:

  • Active Normal Flow Count

  • Active Large Flow Count

  • Active Managed Large Flow Count

  • Active Unmanaged Large Flow Count

  • Base Policy:

    • Active Large Flow Count

    • Active Managed Large Flow Count

    • Active Unmanaged Large Flow Count

  • Extended Policy:

    • Active Large Flow Count

    • Active Managed Large Flow Count

    • Active Unmanaged Large Flow Count

  • Total Normal Flow Count

  • Total Large Flow Count

  • Total Managed Large Flow Count

  • Total Unmanaged Large Flow Count

  • Base Policy:

    • Total Large Flow Count

    • Total Managed Large Flow Count

    • Total Unmanaged Large Flow Count

  • Extended Policy:

    • Total Large Flow Count

    • Total Managed Large Flow Count

    • Total Unmanaged Large Flow Count

  • Total IO Bytes

  • Total Large Flow Bytes

  • Total Recovered Capacity Bytes

  • Total Recovered Capacity ms

• UDP Traffic Optimization Flows:

  • Active Normal Flow Count

  • Active Large Flow Count

  • Active Managed Large Flow Count

  • Active Unmanaged Large Flow Count

  • Base Policy:

    • Active Large Flow Count

    • Active Managed Large Flow Count

    • Active Unmanaged Large Flow Count

  • Extended Policy:

    • Active Large Flow Count

    • Active Managed Large Flow Count

    • Active Unmanaged Large Flow Count

• • Total Normal Flow Count

  • Total Large Flow Count

  • Total Managed Large Flow Count

  • Total Unmanaged Large Flow Count

  • Base Policy:

    • Total Large Flow Count

    • Total Managed Large Flow Count

    • Total Unmanaged Large Flow Count

  • Extended Policy:

    • Total Large Flow Count

    • Total Managed Large Flow Count

    • Total Unmanaged Large Flow Count

  • Total IO Bytes:

  • Total Large Flow Bytes

  • Total Recovered Capacity Bytes

  • Total Recovered Capacity ms

This show command has been introduced in Exec Mode, where:

• traffic-optimization – Displays all traffic optimization options.

• info – Displays Cisco Ultra Traffic Optimization engine information.

The output of this CLI command displays the version, mode, and configuration values.

Following are the new fields/counters:

• Version:

• Mode:

• Configuration:

  • Data Records (TODR)

  • Statistics Options

  • EFD Flow Cleanup Interval

  • Statistics Interval

On executing the above command, the following new fields are displayed for the Multi-Policy Support feature:

• Policy Name

• Policy-Id

• Bandwidth-Mgmt

  • Backoff-Profile

  • Min-Effective-Rate

  • Min-Flow-Control-Rate

• Extended-Bandwidth-Mgmt

  • Backoff-Profile

  • Min-Effective-Rate

  • Min-Flow-Control-Rate

• Curbing-Control

  • Time

  • Rate

  • Max-phases

  • Threshold-Rate

• Extended-Curbing-Control

  • Time

  • Rate

  • Max-phases

  • Threshold-Rate

• Heavy-Session

  • Threshold

  • Standard-Flow-Timeout

• Extended-Heavy-Session

  • Threshold

  • Standard-Flow-Timeout

• Link-Profile

  • Initial-Rate

  • Max-Rate

  • Peak-Lock

• Extended-Link-Profile

  • Initial-Rate

  • Max-Rate

  • Peak-Lock

• Session-Params

  • Tcp-Ramp-Up

  • Udp-Ramp-Up

• Extended-Session-Params

  • Tcp-Ramp-Up

  • Udp-Ramp-Up