Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Guidelines for Working with TDF


Keep the following points in mind while configuring TDF characteristics:

  • Downlink packet that requires TDF processing undergoes two passes through forwarding topology; therefore, the total bandwidth needed by the egress Packet Forwarding Engine is double the actual bandwidth.

  • Graceful Routing engine switchover (GRES) is not supported on the Services Control Gateway.

  • Interface style services on subscriber edge network element facing interface (also called as access interface of TDF domain) are not supported; only next-hop style services are supported On the TDF mobile interface (mif-), no interface style services other than the TDF service are supported.

  • Multicast with TDF is not supported.

  • Multiple TDF gateways on a single chassis is not supported.

  • To apply the TDF services for uplink and downlink subscriber traffic, it is expected that both uplink and downlink traffic flows through the same chassis.

  • 3GPP standard-compliant TDF for Sd interfaces to operate with PCC and ADC rules is not supported.

  • Online charging is not supported

  • Anchor Packet Forwarding Engine support is not available.

  • Packet-triggered and PCRF (Sd) triggered subscriber creations are not supported.

  • QOSMOS (Quality of Service and MObility driven cognitive radio Systems) integration with XLP service PIC DPI engine is supported.

  • RADIUS triggered subscriber creation and PCRF triggered session update are supported. RADIUS and PCRF-triggered subscriber deletion are supported. TDF initiated subscriber deletion (idle timeout) is also supported.

  • You can enable intrachassis redundancy (1:1 GRES, 1:1 session PIC, and N:1 service PIC).

  • Service chaining is supported with both virtual and physical services, both within the box and outside the box.

  • Subscriber-aware services and other existing Infrastructure cannot run on same the service PIC.

  • Dynamic policy support for AVPs within PCC rules (ePCC rules), Layer 7 traffic classification, and HTTP enforcement (header enrichment and URL steering).

  • TDF subscriber-aware services are supported only on XLP based line cards. All other services configured as part of next-hop style services can be either on XLR/XLP/Trio (inline). Interface style service on the access interface is not supported.