Configuring a Set of IP-Based TDF Subscriber Properties with a TDF Domain

You define a set of properties for processing IP-based subscriber traffic and for setting up the subscriber session by configuring a TDF domain. You can create multiple TDF domains.

A potential IP-based subscriber is assigned to a TDF domain through a TDF domain-selection process that you configure in another topic.

Before you begin to create a TDF domain for IP-based subscribers, make sure that you have done the following:

Configured the TDF interface (mif-) that the TDF domain uses.
Configured the access-facing interfaces that the TDF domain uses.
Configured a VRF routing instance that includes the TDF interface and the access-facing interfaces.
Configured the PCEF profile if the TDF domain specifies one.
Configured the address pool that contains source IP addresses of packets that are excluded from TDF processing for the TDF domain.

To configure a TDF domain for IP-based subscribers:

Configuring the TDF Domain Name and AAA Parameters

To configure the TDF domain name and the AAA parameters that are used by the TDF domain to create TDF IP-based subscriber sessions:

Specify a name for the TDF domain. The name can be from 1 through 50 characters long.

(Optional) Configure the TDF domain for IP-based subscribers.
You may omit this step because the default subscriber-type for TDF domains is ip.

Specify one or more methods for constructing the Subscription-Id for the Diameter credit control request (CCR) message that is sent from the TDF to the PCRF for subscribers belonging to the TDF domain.

Specify the type of information to use for the Subscription-Id.

You can specify multiple types, and the order of preference matches the order in which you enter the types. Table 1 describes the types.
You can specify multiple methods by including the entry-name variable multiple times.
If you selected use-class in Step a, you can also configure a regular expression to parse the Class attribute contents, specify characters to insert between the resulting regular expression groups, and specify the subscription ID type.
where value is a regular expression and pattern indicates the characters to insert between regular expression groups, which are identified with \n for a group number.

For example, the following configuration generates " 000118191129|ALICE:DRAV3:" out of " 000118191129#000118191129#ALICE:DRAV3:#7168#nflat#ADSL##" and sets the type to IMSI:
Specify a constant string for the Subscription-Id-Data value.

This constant value is used if none of the subscription-id-options methods can be used. In such a case, the Subscription-Id-Type is END_USER_PRIVATE.

Table 1: Options for id-components of Subscription-Id
Option	Subscription-Id Type	Subscription-Id Data
use-class	Configurable	Entire Class attribute by default. Class attribute value can be parsed with `regex` option under the `[edit unified-edge gateways tdf gateway-name domains domain-name subscription-id use-class]` hierarchy.
use-imsi	END_USER_IMSI	3GPP-IMSI
use-msisdn	END_USER_E164	Calling-Station-Id
use-nai	END_USER_NAI	User-Name
use-nas-port	END_USER_PRIVATE	NAS-Port
use-nas-port-id	END_USER_PRIVATE	NAS-Port-Id
use-realm	END_USER_PRIVATE	Realm portion of the User-Name in NAI format
use-username	END_USER_PRIVATE	Username portion of the User-Name in NAI format

(Not applicable to snooped messages) Enable or disable the sending of an immediate RADIUS response message to the accounting start message received from a gateway GPRS support node (GGSN), Packet Data Network Gateway (PGW), or broadband network gateway (BNG) RADIUS client (disabled is the default).
If the option is disabled, the response is sent after the TDF subscriber session creation is complete.

Configuring Address Filtering

To restrict the traffic that undergoes TDF processing for the TDF domain by identifying source IP addresses for uplink traffic and destination IP addresses for downlink traffic:

Identify the network prefix of source and destination IP addresses for packets that do not undergo TDF processing. Specify inet for IPv4 prefixes and inet6 for IPv6 prefixes.
Identify the address pool that contains source and destination IP addresses of packets that undergo TDF processing. Specify inet for IPv4 prefixes and inet6 for IPv6 prefixes.
Note:
The address pool must be configured at the [edit access address-assignment] hierarchy level.

Configuring Subscriber Services and Policies

To configure the services and policies for IP-based subscribers that belong to the TDF domain:

Identify the TDF interface for the TDF domain.
The TDF domain uses the service set that is applied to this TDF interface.
Note:
The TDF interface (mif) must have been previously configured at the [edit interfaces] hierarchy level.
(Optional) Identify the PCEF profile that the TDF domain uses to apply policies.
If you do not identify a PCEF profile, then the PCEF profile must be assigned under the [edit unified-edge gateways tdf gateway-name domain-selection term] hierarchy.
Note:
The PCEF profile must have been previously configured at the [unified-edge pcef] hierarchy level.

Configuring Access Interfaces

To configure the interfaces that face the access network and carry traffic to and from the IP-based subscribers that belong to the TDF domain:

Specify at least one interface. You can specify multiple interfaces.

Configuring Session Controls

To configure the TDF session controls for subscribers that belong to the TDF domain:

Configure the idle timeout (in minutes) for the TDF subscriber session. The range is 0 through 300.

Configure the default TDF subscriber maximum bit rate (MBR) for uplink and downlink traffic.
Uplink traffic originates from the subscriber towards the public data network (PDN), and downlink traffic comes from the PDN and is destined for the subscriber. The range is 0 through 6,144,000 Kbps.
Configure the default TDF subscriber allowed burst size for uplink and downlink traffic.
Uplink traffic originates from the subscriber towards the public data network (PDN), and downlink traffic comes from the PDN and is destined for the subscriber. The range is 1500 through 1,500,000,000 bytes.
Configure the maximum number of subscriber sessions allowed (in thousands) for the TDF domain. The range is 100 thousands through 5000 thousands.

Configuring Default Policy

To configure the default local policy for handling subscriber traffic entering the access interface of the TDF domain if a TDF subscriber session does not exist:

Configure the flow action to take on the subscriber’s traffic.

Configure the maximum bit rate for the subscriber’s traffic.
Uplink traffic originates from the subscriber towards the public data network (PDN); downlink traffic comes from the PDN and is destined for the subscriber. The range is 0 through 6144000 Kbps.
Configure the allowed burst size for the subscriber’s traffic.
Uplink traffic originates from the subscriber towards the public data network (PDN); downlink traffic comes from the PDN and is destined for the subscriber. The range is 1500 through 1,500,000,000 bytes.

ON THIS PAGE