subscription-id-data-include (PCRF Partition)

Use the specified physical or underlying interface name. If both the underlying interface and the client application perform authentication, authorization, and provisioning, the identification attributes in the server requests enable the AAA or PCRF server to make an association between the two entities.

Use the specified character used as the delimiter between the concatenated components of the subscription-id-data-include. You cannot use the semicolon (;) as a delimiter.

• Default: @

Use the specified domain name that is concatenated with the subscription-id-data-include during the subscriber identification process.

Use the specified interface name that is concatenated with the subscription-id-data-include during the subscriber identification process; for example, demux0.

Use the specified client hardware address (chaddr) from the incoming packet that is concatenated with the subscription-id-data-include during the subscriber identification process.

Use the specified NAS-Port-ID (RADIUS attribute 87), which identifies the physical interface that subscriber management uses to identify subscribers that is concatenated with the subscription-id-data-include during the subscriber identification process. By default, the NAS-Port-ID includes the interface-description value that describes the physical interface.

Use the specified name of the host that originates the Diameter message that is concatenated with the subscription-id-data-include during the subscriber identification process. Supplied as the value of Origin-Host AVP for all messages sent by the Diameter master instance.

Use the specified realm of the host that originates the Diameter message that is concatenated with the subscription-id-data-include during the subscriber identification process. Supplied as the value of Origin-Realm AVP for all messages sent by the Diameter master instance.

Use the specified subscriber username that is concatenated with the subscription-id-data-include during the subscriber identification process.

Use the specified user prefix that is concatenated with the subscription-id-data-include during the subscriber identification process.

Include the subscriber session VLAN tags in the subscription ID. Both single-tagged and double-tagged VLANs are supported: The tags are added in the format outer-vlan-tag-inner-vlan-tag. The outer tag is always included; the inner tag is included for double-tagged VLANs.

Use this option instead of the interface-name option when you the outer VLAN tag is unique across the system and you do not need the underlying physical interface name to be part of the format.