Nokia-specific information elements

A PFCP message may contain several IEs with support for TLV coded PFCP IEs and PFCP grouped IEs.

An IE has the following fields.

• Type

  This field is mandatory and indicates the type of the information element. IE type values within the range of 0 to 32767 are reserved for IEs defined by 3GPP. IE type values within the range of 32768 to 65535 are used for vendor-specific IEs. The vendor controls the value allocation of vendor-specific IEs.

• Length

  This field is mandatory and contains the length of the IE excluding the first four octets, which are common for all IEs (type and length). Bit 8 of the lowest numbered octet is the most significant bit and bit 1 of the highest numbered octet is the least significant bit.

• Enterprise ID

  This field is optional. If the IE type value is within the range of 32768 to 65535, this field contains the IANA-assigned SMI Network Management Private Enterprise Codes value of the vendor defining the IE.

The following table describes the format of a 3GPP-defined IE. The range of the IE type is 0 to 32767.

The following table describes the format of a vendor-specific IE. The range of the IE type is 32768 to 65535.

The BNG-UP sends this IE in response messages to the MAG-c when the Cause IE does not indicate success. The IE contains detailed error information in addition to the generic error indicated by the Cause IE.

The Detailed Error field is encoded as a printable ASCII string without zero-byte termination. The string length is derived from the IE length.

The MAG-c sends this IE to the BNG-UP to indicate a SAP template. The BNG-UP uses the SAP template to construct a new internal SAP structure for the creation of a forwarding state.

The SAP Template field is encoded as a printable ASCII string without zero-byte termination. The string length is derived from the IE length.

The MAG-c sends this IE to the BNG-UP to indicate the group interface template that needs to be used to create a forwarding state on the BNG-UP.

The Group Interface Template field is encoded as a printable ASCII string without zero-byte termination. The string length is derived from the IE length.

The QoS-Overrides field is encoded as described in the 7450 ESS, 7750 SR, and VSR RADIUS Attributes Reference Guide for the VSA Alc-Subscriber-QoS-Override.

If n = 3, the Filter Override field is not present. All filtering for the specified filter type is disabled.

If n > 3, the Filter Override field contains a filter name.

The type of the Filter Type field is the same enumeration as defined for the Nokia Create Filter Override IE.

This IE indicates that the filter override needs to be removed. The system falls back to the default filters configured for the session. This differs from an absent Filter Override field in the Nokia Create Filter Override IE (see Nokia Create Filter Override). The absent Filter Override field in the Nokia Create Filter Override IE explicitly disables all filtering, including the default filters.

The Intermediate Destination field is encoded as described in the 7450 ESS, 7750 SR, and VSR RADIUS Attributes Reference Guide for VSA Alc-Int-Dest-Id-Str.

This IE is an extension to the 3GPP Measurement Information IE. It defines how measurements are reported. The following additional bit is defined:

DET (7/1): includes detailed per queue and policer statistics in usage reports related to the URR for which this is signaled.

The BNG-UP sends this IE to indicate the support for vendor-specific functions that are not available on each version of the Nokia BNG-UP.

The following Nokia UP function features are defined.

• Bulk (7/1)

  The BNG-UP supports the bulk audit feature.

• NAT (7/2)

  The BNG-UP supports Nokia-specific extensions to subscriber-aware NAT.

• LAC (7/3)

  The BNG-UP supports the Nokia LAC implementation where the UP is responsible for L2TP control plane signaling.

• SSSG (7/3)

  The BNG-UP supports shared subscriber subnet signaling (SSSG) with each session to announce in routing.

The Abs flag field indicates that the modification is absolute and not relative. Any rules or traffic endpoints that were not explicitly created in this message must be deleted. This flag may only be set if the BNG-UP indicated support for the bulk audit feature.

The State field is an opaque value that is not interpreted by the BNG-UP but reflected as-is, in PFCP Session Modification Response and PFCP Session Report Request messages.

The BNG-UP sends this IE to indicate the number of ISA members in a NAT group. When not signaled, the Nokia MAG-c assumes the number to be 1.

To create BNG QoS profiles, Nokia formats the Activate Predefined Rules IE as follows:

qos_policy ::= (profile-name ':' value ';')+

where profile-name is slaprof or subprof. Each profile-name can occur at most one time.

• slaprof

  This is an SLA profile as directly defined on the BNG-UP. No string-to-profile mappings are used.

• subprof

  This is a subscriber profile as directly defined on the BNG-UP. No string-to-profile mappings are used.

This IE includes the first LCP Configure Request Message received by a LAC MAG-c. It is used to proxy to an LNS.

This IE is used to proxy PPP setup parameters from a LAC MAG-c to an LNS. For more details, see RFC 1661, section 4.4.5.

This IE includes the last LCP Configure Request Message received by a LAC MAG-c. It is used to proxy to an LNS.

This IE is used to proxy PPP setup parameters from a LAC MAG-c to an LNS. For more details, see RFC 1661, section 4.4.5.

This IE includes the last LCP Configure Request Message received by a LAC MAG-c. It is used to proxy to an LNS.

This IE is used to proxy PPP setup parameters from a LAC MAG-c to an LNS. For more details, see RFC 1661, section 4.4.5.

This IE indicates which authentication method was used between the LAC MAG-c and the PPPoE client. The type of the Authentication Type field is an enumeration of the following values:

• 0: CHAP
• 1: PAP

This IE is used to proxy PPP setup parameters from a LAC MAG-c to an LNS. For more details, see RFC 1661, section 4.4.5.

This IE includes the username used during authentication between the LAC MAG-c and the PPPoE Client.

This IE is used to proxy PPP setup parameters from a LAC MAG-c to an LNS. For more details, see RFC 1661, section 4.4.5.

This IE includes the ID used during authentication between the LAC MAG-c and the PPPoE client.

This IE is used to proxy PPP setup parameters from a LAC MAG-c to an LNS. For more details, see RFC 1661, section 4.4.5.

This IE includes the challenge used during CHAP authentication between the LAC MAG-c and the PPPoE Client.

This IE is used to proxy PPP setup parameters from a LAC MAG-c to an LNS. For more details, see RFC 1661, section 4.4.5.

This IE includes the challenge response or password used during the authentication between the LAC MAG-c and the PPPoE Client.

This IE is used to proxy PPP setup parameters from a LAC MAG-c to an LNS. For more details, see RFC 1661, section 4.4.5.

The LAC BNG-UP uses the IP address in this IE to set up an L2TP tunnel.

The LAC BNG-UP sets up an L2TP tunnel toward the IP address in this IE.

The Name field in this ID identifies the hostname of the LAC.

The Name field in this ID identifies the hostname of the LNS.

This IE includes the password used for tunnel authentication.

This IE includes a name for a tunnel or a group of tunnels.

An LNS can use the Group ID in this IE to correlate a group of customers.

This IE contains a set of fixed-width parameters that influence tunnel set up. The Parameter Inclusion Flags field contains a list of flags that indicates whether a specific parameter is present or not.

The following table lists for all supported parameters the name, the description, the flag number (1 to 32), and the number of bytes used by the parameter. The flag number correlates to a bit in the Parameter Inclusion Flags field, that is, flag 1 corresponds with 0x00000001 and flag 32 with 0x80000000. The parameters that are flagged for inclusion are included in the Parameters field in order of flag number.

This IE contains a set of fixed-width access line parameters; for example, the access line characteristics as defined in BBF TR-101 and signaled in DHCP, DHCPv6 or PPPoE discovery. The Parameter Inclusion Flags field contains a list of flags that indicates whether a specific parameter is present or not. These values are signaled to be reflected in other BNG-UP specific protocols such as L2TP.

The following table lists for all supported parameters the name, the description, the flag number (1 to 32), and the number of bytes used by the parameter. The flag number correlates to a bit in the Parameter Inclusion Flags field, that is, flag 1 corresponds with 0x00000001 and flag 32 with 0x80000000. The parameters that are flagged for inclusion are included in the Parameters field in order of flag number.

This IE contains identifiers that are negotiated during L2TP setup.

This IE includes the circuit ID as learned from the access connection protocols such as DHCP, PPPoE discovery, and DHCPv6.

This IE includes the remote ID as learned from the access connection protocols such as DHCP, PPPoE discovery, and DHCPv6.