Standard diameter AVPs

Applications for which the described AVPs apply:

  • Gx-PM-ESM—Policy Management for Enhanced Subscriber Management
  • Gx-UM-ESM—Usage Monitoring for Enhanced Subscriber Management
  • Gx-PM-AA—Policy Management for Application Assurance
  • Gx-UM-AA—Usage Monitoring Application Assurance

The AVPs listed in Standard diameter AVPs (description) that do not have an associated application are AVPs that are used for generic purposes and their use can extend through all applications.

Table 1. Standard diameter AVPs (description)
AVP ID AVP name Section defined Application Description

5

NAS-Port

RFC 2865 / §5.5 RFC 4005 / §4.2

—

See the 7450 ESS, 7750 SR, and VSR RADIUS Attributes Reference Guide.

8

Framed-IP-Address

RFC 4005 /§6.11.1

—

This AVP specifies the IPv4 address of the subscriber host. The IPv4 address is obtained before Gx session establishment. The IPv4 address cannot be assigned to the subscriber host by PCRF via Gx but is instead used only for reporting.

18

3GPP-SGNS-MCC-MNC

29.061

—

GTP S11 Access uses the value configured with the following command: 
configure subscriber-mgmt gtp serving-network

22

3GPP-User-Location-Info

29.061

—

In CCR-I, this contains the User Location Information as signaled in the incoming GTP-C message for GTP Access hosts.

For a CCR-U triggered by either USER_LOCATION_CHANGE (ULC), ECGI_CHANGE, or TAI_CHANGE will include ULI values as follows:

  • If the trigger was ULC and the ULI contains anything other than ECGI or TAI, the ULI is signaled as received in GTP.

  • If the trigger was ULC and either TAI or ECGI changed from its last known value, both TAI and ECGI will be included.

  • If the trigger was ECGI_CHANGE and ECGI changed from its last known value, ECGI is included.

  • If the trigger was TAI_CHANGE and TAI change from its last known value, TAI is included.

25

Class

RFC 2865 / §5.25

—

This attribute is available to be sent by the PCRF to the 7750 SR and is echoed unmodified by the 7750 SR to the PCRF. The 7750 SR does not interpret this attribute locally.

30

Called-Station-Id

RFC 2865 / §5.30 RFC 4005 / §4.5

—

See the7450 ESS, 7750 SR, and VSR RADIUS Attributes Reference Guide.

31

Calling-Station-ID

RFC 4005 / §4.6

—

See the 7450 ESS, 7750 SR, and VSR RADIUS Attributes Reference Guide.

55

Event-Timestamp

RFC 6733 / §8.21

—

This AVP records the time that this event occurred on the 7750 SR, in seconds since January 1, 1900 00:00 UTC.

61

NAS-Port-Type

RFC 2865 / §5.41

RFC 4005 / §4.4

RFC 4603

—

See the7450 ESS, 7750 SR, and VSR RADIUS Attributes Reference Guide.

87

NAS-Port-Id

RFC 2869 / §5.17

RFC 4005 / §4.3

—

See the7450 ESS, 7750 SR, and VSR RADIUS Attributes Reference Guide.

92

NAS-Filter-Rule

RFC 4849

Gx-PM-ESM

See the 7450 ESS, 7750 SR, and VSR RADIUS Attributes Reference Guide.

This AVP is nested within the Charging-Rule-Definition AVP.

97

Framed-IPv6-Prefix

RFC 4005 /§6.11.6

—

This AVP specifies the IPv6-prefix and prefix-length that is assigned to the host via SLAAC (Router Advertisement) to the WAN side of the user. The IPv6-prefix and prefix-length is obtained before Gx session establishment. The facilities to provide the IPv6-prefix and prefix-length to the subscriber-host are DHCP server/local pools, RADIUS or LUDB. The IPv6-prefix/prefix-length cannot be assigned to the subscriber host by PCRF via Gx. Instead the IPv6-prefix and prefix-length is the one being reported to the PCRF during the host instantiation phase.

123

Delegated-IPv6-Prefix

RFC 4818

—

This attribute carries the Prefix (ipv6-prefix/prefix-length) assigned to the host via DHCPv6 (IA-PD) for the LAN side of the user (IPoE, PPPoE). The IPv6-prefix/prefix-length is obtained before Gx session establishment. The facilities to provide the IPv6-prefix/prefix-length to the subscriber-host are DHCP server/local pools, RADIUS or LUDB. The IPv6-prefix/prefix-length cannot be assigned to the subscriber host by PCRF via Gx. Instead the IPv6-prefix/prefix-length is the one being reported to the PCRF during the host instantiation phase.

257

Host-IP-Address

RFC 6733 / §5.3.5

—

This AVP is used to inform a Diameter peer of the sender's IP address.

The IPv4 address used is the one configured in the diameter-peer-policy. If none is configured, then the system IP address is used.

258

Auth-Application-Id

RFC 6733 / §6.8

—

This AVP indicates supported Diameter applications. The application support is exchanged in CER/CEA when the peering sessions is established.

The diameter base protocol does not require application ID because its support is mandatory.

The Gx application ID value is 16777238 and it is advertised in Auth-Application-Id AVP within the grouped Vendor-Specific-Application-Id AVP in CER message.

In addition, each Gx specific message carries Auth-Application-Id AVP with the value of 16777238.

260

Vendor-Specific-Application-Id

RFC 6733 / §6.11

—

This is a Grouped AVP that is used to advertise support of a vendor-specific Diameter application in CER/CEA messages. Gx is one such application. This AVP contains the Vendor-Id AVP of the application and the auth-application-id AVP.

263

Session-id

RFC 6733 / §8.8

—

This AVP must be present in all messages and it is used to identify a specific IP-Can session. IP-Can session corresponds to a subscriber host, which can be DHCPv4/v6, PPPoX or ARP host. Session-id AVP is unique per host.

Dual stack host (IPoE or PPPoX) share a single session-id.

264

Origin-Host

RFC 6733 / §6.3

—

This AVP must be present in all messages and it is used to identify the endpoint (Diameter peer) that originated the message.

265

Supported-Vendor-Id

RFC 6733 / §5.3.6

—

This AVP is used in CER/CEA messages to inform the peer that the sender supports a subset of) the vendor-specific AVPs defined by the vendor identified in this AVP.

Supported vendors in the 7750 SR are:

3GPP — 10415

ETSI — 13019

NOKIA — 6527

BBF — 3561

266

Vendor-Id

RFC 6733 / §5.3.3

—

The value of this AVP is the IANA assigned code to a specific vendor.

This AVP may be part of the Vendor-Specific-Application-Id AVP, Failed-AVP AVP, Experimental-Result AVP to identify the vendor associated with the relevant message/AVP.

In case of a standalone Vendor-Id AVP (outside of any grouped AVP) that is conveyed in CER/CEA messages, it is envisioned that this AVP along with the Product-Name AVP and the Firmware-Revision AVP may provide useful debugging information.

Supported Vendor-Id AVPs in the 7750 SR are:

3GPP — 10415

ETSI — 13019

NOKIA — 6527

267

Firmware-Revision

RFC 6733 / §5.3.4

—

The SR OS version is reported.

268

Result-Code

RFC 6733 / §7.1

—

This AVP indicates whether a particular request was completed successfully or an error occurred.

All answer messages in Diameter/Gx must include one Result-Code AVP or Experimental-Result AVP.

For the list of supported error codes see Result codes (Result-Code AVP).

269

Product-Name

RFC 6733 / §5.3.7

—

This AVP specifies the vendor-assigned name.

278

Origin-State-Id

RFC 6733 / §8.16

—

This AVP is used to inform the PCRF of the loss of the state on the 7750 SR side. Its value monotonically increases each time the PCRF is rebooted with the loss of the previous state.

Because Gx sessions are not persistent in the 7750 SR, Origin-State-Id increases each time the 7750 SR is rebooted.

279

Failed-AVP

RFC 6733 / §7.5

—

This is a Grouped AVP that provides debugging information in cases where a request is rejected or not fully processed because of the erroneous information in specific AVP. The value of the Result-Code AVP will provide information about the reason for the Failed-AVP AVP.

The Failed-AVP AVP contains the entire AVP that could not be processed successfully.

281

Error-Message

RFC 6733 / §7.3

—

This AVP provides more information of the failure that is indicated in the Result-Code AVP.

282

Route Record

RFC 6733 / §6.7.1

This AVP identifies the peer from which the request is received and is used for routing loop detection. An SR node inserts the origin-host of the peer in the Route-Record AVP of all transit request messages.

283

Destination-Realm

RFC 6733 / §6.6

—

This AVP represents the realm to which this message is to be routed. The value of this AVP is either explicitly configured in the 7750 SR.

285

Re-Auth-Request-Type

RFC 6733 / §8.12

—

This AVP is mandatory in RAR requests. The content of this AVP is ignored by the 7750 SR.

293

Destination-Host

RFC 6733 / §6.5

—

This AVP represents the host to which this message is to be sent. The value of this AVP can be explicitly configured.

In case that it is omitted, the DRA (Diameter relay-agent) that receives the message selects the destination host to which the message is sent.

295

Termination-Cause

RFC 6733 / §8.15

—

This AVP is used to indicate the reason why a session was terminated on the 7750 SR.

The supported termination causes in the 7750 SR are specified in Termination causes (Termination-Cause AVP) .

296

Origin-Realm

RFC 6733 / §6.4

—

This AVP contains the realm of the originator of message. In the 7750 SR, the Origin-Realm is explicitly configured per Diameter peer.

297

Experimental-Result

RFC 6733 / §7.6

—

This is a Grouped AVP that indicates whether a particular vendor-specific request completed successfully or whether an error occurred. It contains a vendor-assigned value representing the result of processing a request.

The result-code AVP values defined in Diameter Base RFC (6733, §7.1) are also applicable to Experimental-Result AVP.

For a list of Gx-specific Experimental-Result-Code values supported in the 7750 SR, see Result codes (Result-Code AVP). For Gx application, the Vendor-Id AVP is set to 10415 (3GPP).

All answer messages defined in vendor-specific application must include either one Result-Code AVP or one Experimental-Result AVP.

298

Experimental-Result-Code

RFC 6733 / §7.7

29.214 / §5.5

—

This AVP specifies vendor-assigned (3GPP — Gx) values representing the result of processing the request.

For a list of the 7750 SR supported values for Gx see Result codes (Result-Code AVP).

302

Logical-Access-Id

ETSI TS 283 034 / §7.3.3

BBF TR-134 (§7.1.4.1)

—

This AVP contains information describing the subscriber agent circuit identifier corresponding to the logical access loop port of the Access Node from which the subscriber's requests are initiated, namely:

  • circuit-id from DHCPv4 Option (82,1)

  • circuit-id from PPPoE tag (0x105, 0x00000de9 [dsl forum], 0x01 — DSL Forum TR-101)

  • interface-id from DHCPv6 option 18.

The Vendor-Id in CER is set to ETSI (13019).

313

Physical-Access-Id

ETSI TS283 034 / §7.3.14

BBF TR-134 (§7.1.4.1)

—

This AVP contains information about the identity of the physical access to which the user device is connected, namely:

  • remote-id from DHCPv4 Option (82,2)

  • remote-id from PPPoE tag (0x105, 0x00000de9 [dsl forum], 0x02 — DSL Forum TR-101)

  • remote-id from DHCPv6 option 37.

The Vendor-Id in CER is set to ETSI (13019).

412

CC-Input-Octets

RFC 4006 / §8.24

Gx-UM-ESM

Gx-UM-AA

This AVP contains the number of requested, granted or used octets from the user.

414

CC-Output-Octets

RFC 4006 / §8.25

Gx-UM-ESM

Gx-UM-AA

This AVP contains the number of requested, granted or used octets toward the user.

415

CC-Request-Number

RFC 4006 / §8.2

—

This AVP identifies each request within one session. Each request within a session has a unique CC-Request-Number that is used for matching requests with answers.

416

CC-Request-Type

RFC 4006 / §8.3

—

This AVP identifies the request type:

INITIAL_REQUEST (CCR-I)

UPDATE_REQUEST (CCR-U)

TERMINATION_REQUEST (CCR-T)

418

CC-Session-Failover

RFC 4006 / §8.4

—

This AVP controls whether the secondary peer will be used in case that the primary peer is unresponsive (peer failover behavior). The unresponsiveness is determined by the timeout of the previously sent message.

If this AVP is not supplied via PCRF, the locally configured options in the 7750 SR will determine the peer failover behavior. For further details on the peer failover behavior, see ‟Gx Fallback Function” section in the Gx Configuration Guide.

421

CC-Total-Octets

RFC 4006 / §8.23

Gx-UM-ESM Gx-UM-AA

This AVP contains the number of requested, granted or used octets regardless of the direction (sent or received).

427

Credit-Control-Failure-Handling

RFC 4006 / §8.14

—

This AVP controls whether the subscriber is terminated or instantiated with default parameters in case that the PCRF is unresponsive. The unresponsiveness is determined by the timeout of the previously sent message.

If this AVP is not supplied via PCRF, the locally configured options in the 7750 SR determines the behavior. For further details, see the ‟Gx Fallback Function” section in the Gx Configuration Guide.

431

Granted-Service-Unit

RFC 4006 / §8.17

Gx-UM-ESM

Gx-UM-AA

This grouped AVP is sent by PCRF to the 7750 SR for usage monitoring purposes. When the granted amount of units is consumed by the user, a report is sent from the 7750 SR to the PCRF.

The amount of consumed units can be measured on three different levels:

  • Session level (host level)

  • PCC rule level (credit category in the 7750 SR)

  • ADC rule level (AA level in the 7750 SR)

433

Redirect-Address-Type

RFC 4006 / §8.38

Gx-PM-ESM

This AVP specifies the address type of the HTTP redirect server.

URL (2) type is the only address type supported in the 7750 SR.

435

Redirect-Server-Address

RFC 4006 / §8.39

Gx-PM-ESM

This AVP specifies the URL string of the redirect server.

443

Subscription-Id

RFC 4006 / §8.46

—

This AVP is of type Grouped and is used to identify the subscriber host in the 7750 SR. The nested AVPs are subscription-id-data and subscription-id-type.

444

Subscription-Id-Data

RFC 4006 / §8.48

—

This AVP is part of the subscription-id AVP and is used to identify the host by:

  • Circuit-id

  • Dual-stack-remote-id

  • Imei

  • Imsi

  • Mac of the host

  • Msisdn

  • Subscriber-id

  • Username (ppp-username or a string returned in the Username attribute via RADIUS or NASREQ)

Subscription type (subscription-id-type AVP) has to be explicitly set via CLI. The data is formatted according to the type set.

For GTP S11 access, the value configured with the following command is ignored and the session always includes two subscription-Id AVPs for both IMSI and MSISDN.

  • MD-CLI

    configure subscriber-mgmt diameter-gx-policy gx avp-subscription-id

  • classic CLI

    configure subscriber-mgmt diameter-application-policy gx avp-subscription-id

446

Used-Service-Unit

RFC 4006 / §8.19

Gx-UM-ESM

Gx-UM-AA

This AVP is of type Grouped and it represents the measured volume threshold for usage monitoring control purposes.

It is sent in the Usage-Monitoring-Report AVP from the 7750 SR to the PCRF when the granted unit threshold is reached or in response to a usage-report request from the PCRF.

450

Subscription-Id-Type

RFC 4006 / §8.47

—

This AVP is used to determine which type of identifier is carried by the subscription-id AVP. The following formats (types) are supported in the 7750 SR:

  • E.164 format (ITU-T E.164)

  • IMSI format (ITU-T E.212)

  • NAI format (RFC 2486)

  • Private format

458

User-Equipment-Info

RFC 4006 / §8.49

—

This is a Grouped AVP that carries information about the identity and the capabilities of the host.

459

User-Equipment-Info-Type

RFC 4006 / §8.50

—

This AVP is nested within the User-Equipment-Info AVP. The following types are supported in the 7750 SR:

  • IMEISV – contains the IMEI and software version according to 3GPP TS 23.003 document.

  • MAC address

  • Eui64 based on 48-bit MAC address with 0xfffe inserted in the middle.

  • Modified_eui64 — similar to eui64 but with inverted ‛u’ bit as defined in: http://standards.ieee.org/develop/regauth/tut/eui64.pdf and RFC 4291.

The equipment type must be explicitly set through the CLI. For GTP S11 access, the configuration is ignored and always uses IMEISV.

460

User-Equipment-Info-Value

RFC 4006 / §8.51

—

This AVP carries the value that is defined by the User-Equipment-Info-Type AVP.

507

Flow-Description

29.214 / §5.3.8

Gx-PM-ESM

This AVP is nested within Flow-Information AVP. It identifies traffic within the PCC rule based on the 5 tuple.

511

Flow-Status

29.214 / §5.3.11

Gx-PM-ESM

This AVP is used to set the service gating action for the service represented by the PCC rule. It is nested inside of Charging-Rule-Definition AVP.

Supported values are:

  • ENABLED (2)

  • DISABLED (3)

The service identified by PCC rule is by default enabled (Flow-Status = ENABLED). If explicitly configured within the PCC rule, it must be accompanied with one or more additional actions. Otherwise, the entire PCC rule instantiation fails.

Flow-Status = DISABLED can be the sole action within the PCC rule. Traffic associated with this action, is dropped.

515

Max-Requested-Bandwidth-DL

29.214 / §5.3.14

Gx-PM-ESM

Depending on the context in which it is configured (nested), this AVP represents the egress PIR of a queue or a policer.

516

Max-Requested-Bandwidth-UL

29.214 / §5.3.15

Gx-PM-ESM

Depending on the context in which it is configured (nested), this AVP represents the ingress PIR of a queue or a policer.

554

Extended-Max-Requested-BW-DL

29.214 / §5.3.52

Gx-PM-ESM

For higher rate requirements, this AVP can be used in place of the Max-Requested-Bandwidth-DL AVP.

555

Extended-Max-Requested-BW-UL

29.214 / §5.3.52

Gx-PM-ESM

For higher rate requirements, this AVP can be used in place of the Max-Requested-Bandwidth-UL AVP.

628

Supported-Features

29.229 / §6.3.29

29.212 / §5.4.1

—

This is a Grouped AVP that is used during Gx session establishment to inform the destination host about the required and optional features that the origin-host supports. One instance of Supported-Features AVP is needed per Feature-List-id.

The 7750 SR supports the following features from 3GPP document 29.212, section §5.4.1:

  • Gx Rel 8, 9, 10

  • ADC

  • Extended-BW-NR (optional)

The Vendor-Id AVP in Supported-Features AVP is set to 10415 (3GPP).

629

Feature-List-Id

29.229 / §6.3.30

—

This AVP contains the identity of a feature list. This AVP allows differentiation between multiple feature lists in case that an application has multiple feature lists defined.

Gx reference point and ADC are advertised in Feature-List-Id=1 and Extended-BW-NR is advertised in Feature-List-Id=2.

630

Feature-List

29.229 / §6.3.31

—

This AVP contains a bitmask indicating the supported feature in Gx.

The Gx features in the Feature-List AVP are defined in 3GPP TS 29.212, §5.4.1.

909

RAI

29.061

—

For GTP S11 access this contains the RAI if it was signaled in GTP.

1001

Charging-Rule-Install

29.212 / §5.3.2

—

This AVP is of type Grouped and is used to enforce overrides, install NAS filter inserts and install or modify PCC rules in the node as instructed by PCRF.

Each override, NAS filter insert or a PCC rule that is to be instantiated is identified by the charging-rule-name AVP.

1002

Charging-Rule-Remove

29.212 / §5.3.3

—

This AVP is of type Grouped and is used to remove PCC rules from an IP CAN session.

Be aware that Gx overrides (ESM string overrides, updates of queue and policer rates, filter overrides, category-map overrides), cannot be removed. For those cases, the Charging-Rule-Remove AVP is ignored, even if the M-bit in the AVP is set.

1003

Charging-Rule-Definition

29.212 / §5.3.4

—

This AVP is of type Grouped and is used for rule overrides, NAS filter inserts or PCC rules installation. It contains nested AVPs that define the overrides (rate changes of a subscriber, a queue or a policer, and so on), NAS filter insert or a completely new PCC rule definition.

The override/PCC rule (defined by the Charging-Rule-Definition) is instantiated via Charging-Rule-Install AVP.

1005

Charging-Rule-Name

29.212 / §5.3.6

—

This AVP is used to:

  • Reference a predefined rule in the node. This predefined rule represents an override of an existing rule. The override is activated by including Charging-Rule-Name AVP nested within the Charging-Rule-Install AVP sent from the PCRF to the 7750 SR.

  • Name the PCC rule which is defined through Charging-Rule-Definition AVP. When the PCC rule is installed, it can be removed by referencing the PCC rule name.

  • Report rule/override status in case of a rule/override activation failure. The status is reported within Charging-Rule-Report AVP sent from the node to the PCRF.

1006

Event-Trigger

29.212 / §5.3.7

—

This AVP can be sent from the PCRF to subscribe to a particular event in the 7750 SR.

When specific events occur on the 7750 SR, they are reported to the PCRF in the related AVP along with the event trigger indication.

The supported events are listed in Event triggers (Event-Trigger AVP).

1010

Precedence

29.212 / §5.3.11

Gx-PM-ESM

This AVP is carried within a PCC rule definition (Charging-Rule-Definition) and it determines the order in which PCC rules are installed for the subscriber-host. PCC rules with lower values are evaluated before PCC rules with higher values.

PCC rules without the Precedence value will be automatically ordered by the system to optimize the use of system resource.

In case that there is a mix of PCC rules with and without the Precedence value, PCC rules without the explicit Precedence value are ordered after the PCC rules with the explicitly set Precedence value.

1014

ToS-Traffic-Class

29.212 / §5.3.15

Gx-PM-ESM

This AVP is nested within Flow-Information AVP. It identifies traffic within the PCC rule based on DSCP bits. The only supported mask in this AVP is 11111100 (6 bits denoting DSCP field).

1016

QoS-Information

29.212 / §5.3.16

Gx-PM-ESM

This AVP has a multi-faceted function:

  • As part of PCC rule definition in CCA or RAR, this AVP is used to rate-limit a flow.

  • The AVP defines QoS overrides that can be submitted from PCRF to the SR OS router in a CCA or RAR message. The overrides are nested in Charging-Rule-Definition AVP and are activated in SR OS through the Charging-Rule-Install AVP.

The supported QoS overrides are:

  • Queue rates, bursts sizes, and weights

  • Policer rates and burst sizes

  • Subscriber egress aggregate rate limit

  • Arbiter rates

The AVP defines APN Uplink and Downlink Aggregate Maximum Bitrate (AMBR) in a CCA or RAR message. In this case, the AVP is included on the message level. The SR OS can map the AMBR on QoS overrides using the following commands.

  • MD-CLI 
    configure groups group subscriber-mgmt diameter-gx-policy gx three-gpp-qos-mapping
  • classic CLI 
    configure subscriber-mgmt diameter-application-policy gx 3gpp-qos-mapping

For GTP S11 access, the AVP can also be used to signal the APN AMBR value received in GTP in a CCR message. In this case the AVP is included on message level.

1018

Charging-Rule-Report

29.212 / §5.3.18

—

This AVP is of type Grouped and is used to report the status of PCC rules in the 7750 SR.

Failure to install or activate one or more policy rules is always reported in CCR-u messages. One or more Charging-Rule-Report AVPs in CCR-u command is included, indicating the failed rules.

The report about successful rule activation or rule resource allocation is not sent to the PCRF even in the cases when the PCRF specifically demands such reports from the 7750 SR.

1019

PCC-Rule-Status

29.212 / §5.3.19

—

This AVP describes the status of the rules as active or inactive and is nested within the Charging-Rule-Report AVP.

1025

Guaranteed-Bitrate-DL

29.212 / §5.3.25

Gx-PM-ESM

Depending on the context in which it is configured (nested), this AVP represents the egress CIR of a queue or a policer.

1026

Guaranteed-Bitrate-UL

29.212 / §5.3.26

Gx-PM-ESM

Depending on the context in which it is configured (nested), this AVP represents the ingress CIR of a queue or a policer.

1027

IP-CAN-Type

29.212 / §5.3.27

—

This AVP indicates the type of Connectivity Access Network in which the user is connected.

For GTP S11 access, the AVP value is set to 3GPP-EPS (code 5). For any other access type the AVP value is set to xDSL (code 2).

1028

QoS-Class-Identifier

29.212 / §5.3.17

—

This AVP identifies a QoS forwarding class within the router. Mapping between QCIs and forwarding classes in the 7750 SR is the following:

  • QCI 1 — FC H1

  • QCI 2 — FC H2

  • QCI 3 — FC EF

  • QCI 4 — FC L1

  • QCI 5 — FC NC

  • QCI 6 — FC AF

  • QCI 7 — FC L2

  • QCI 8 — FC BE

1031

Rule-Failure-Code

29.212 / §5.3.38

—

This AVP is sent from the router to the PCRF within a Charging-Rule-Report or ADC-Rule-Report AVP to identify the reason a rule is being reported. For the list of supported failure codes in the 7750 SR, see Rule failure codes (Rule-Failure-Code AVP).

1032

RAT-Type

29.212 / §5.3.31

—

This AVP identifies the radio access technology used for this connection.

For WLAN-GW UEs, the AVP value is fixed and set to WLAN(0).

For GTP S11 access, the AVP value is set to the value signaled in GTP.

1040

APN-Aggregate-Max-Bitrate-DL

29.212

—

When received in an RAR or CCA, this value can be mapped to a local egress QoS override with the following commands.

  • MD-CLI 
    configure groups group  subscriber-mgmt diameter-gx-policy gx three-gpp-qos-mapping apn-ambr-dl
  • classic CLI
    configure subscriber-mgmt diameter-application-policy gx 3gpp-qos-mapping apn-amb-dl

The AVP can be configured to override an egress policer PIR rate, an egress queue PIR rate, an egress arbiter rate, an egress user scheduler rate, an egress aggregate rate, an egress high-scale SLA aggregate rate, or to ignore the override.

This uses the generic ESM override mechanism and any override received from another source (such as RADIUS or Alc-Queue AVP) can remove or change this value.

For GTP S11 access, the value received in GTP is also reflected in a CCR.

1041

APN-Aggregate-Max-Bitrate-UL

29.212

—

When received in an RAR or CCA, this value can be mapped to a local ingress qos override with the following commands.

  • MD-CLI
    configure groups group subscriber-mgmt diameter-gx-policy gx three-gpp-qos-mapping apn-ambr-ul
  • classic CLI
    configure subscriber-mgmt diameter-application-policy gx 3gpp-qos-mapping apn-amb-ul

The AVP can be configured to override an ingress policer PIR rate, an ingress queue PIR rate, an ingress arbiter rate, an ingress user scheduler rate, or to ignore the override.

This uses the generic ESM override mechanism and any override received from another source (such as RADIUS or Alc-Queue AVP) can remove or change this value.

For GTP S11, the access value received in GTP also reflected in a CCR.

1045

Session-Release-Cause

29.212 / §5.3.33

Gx-PM-ESM

Gx-PM-AA

This AVP terminates the Gx session from the PCRF side. The reason for session termination is included in this AVP. The reason for the session termination is ignored by the router.

1050

AN-GW-Address

29.212 / § 5.3.49

—

This AVP is the system IPv4 address of the 7750 SR.

1058

Flow-Information

29.212 / §5.3.53

Gm-PM-ESM

This is a Grouped AVP carrying information about traffic identification with the PCC rule. This AVP is nested within Charging-Rule-Definition AVP.

Possible traffic identifiers within this AVP are:

  • Flow-Description AVP — 5 tuple information
  • ToS-Traffic-Class AVP — DSCP bits
  • Flow-Direction AVP — ingress or egress direction of the traffic

1065

PDN-Connection-ID

29.212

—

For GTP S11, the access value contains the APN as received in GTP.

1066

Monitoring-Key

29.212 / §5.3.59

Gx-UM-ESM

Gx-UM-AA

This AVP is used for usage monitoring, as an identifier for a usage monitoring control instance.

This AVP can be nested within:

  • Charging-Rule-Definition AVP

    In this case, the Monitoring-Key AVP is used to represent the PCC rule for which usage monitoring may be needed.

  • Usage-Monitoring-Information AVP

    In this case, the Monitoring-Key AVP is used to trigger or report the usage monitoring action for the entity represented by the Monitoring-Key AVP.

The usage monitoring can be performed on multiple levels as requested by the Usage-Monitoring-Level AVP nested within the Usage-Monitoring-Information AVP:

  • If the level is IP-CAN session, then the monitoring-key is an arbitrary octet string set by the PCRF – usage monitoring is performed for the entire IP-CAN session (which represent a host/sla-profile instance)

  • If the level is pcc rule, then the Monitoring-Key refers to either the predefined category (name) in the 7750 SR, or the PCC rule represented by the Monitoring-Key AVP as defined in the Charging-Rule-Definition AVP.

  • If the level is adc rule, then the monitoring-key is an arbitrary unique name that refers to a unique Tdf-App-Id defined in an Adc-Rule.

There can be up to three monitoring-keys in a single Gx messages.

1067

Usage-Monitoring-Information

29.212/ §5.3.60

Gx-UM-ESM

Gx-UM-AA

This AVP is of type Grouped and it contains the usage monitoring control information. It is used to activate usage monitoring and grant service units when it is sent from the PCRF toward the 7750 SR.

The 7750 SR uses this AVP to report usage monitoring to the PCRF.

1068

Usage-Monitoring-Level

29.212 / §5.3.61

Gx-UM-ESM

Gx-UM-AA

This AVP is sent by PCRF to indicate the level on which usage monitoring is performed in the 7750 SR:

  • IP-CAN session level

  • PCC rule level

  • ADC rule level

If usage-monitoring-level AVP is not provided, its absence indicates the pcc rule level usage monitoring.

1069

Usage-Monitoring-Report

29.212 / §5.3.62

Gx-UM-ESM

Gx-UM-AA

This AVP is sent by the PCRF to indicate that the accumulated usage monitoring is to be reported by the 7750 SR regardless of whether a usage monitoring threshold is reached. In other words, this AVP indicated immediate request for a usage monitoring report.

A single value for this AVP is defined:

0 — usage_monitoring_report_required

1070

Usage-Monitoring-Support

29.212 / §5.3.63

Gx-UM-ESM

Gx-UM-AA

This AVP is sent by the PCRF to indicate whether the usage monitoring is disabled for specific monitoring key.

The following value is defined:

0 — usage_monitoring_disabled

When usage-monitoring is disabled for a specific monitoring-key in this fashion, the 7750 SR generates a new CCR-u with the event-trigger AVP set to ‛usage_report’ to report the accumulated usage for the disabled usage monitoring entities.

1080

Flow-Direction

29.212 / §5.3.65

Gx-PM-ESM

This AVP is nested within the Flow-Information AVP. It identifies the direction in which the PCC rule is applied (ingress or egress).

Supported values are:

  • DOWNLINK (1) for egress direction
  • UPLINK (2) for ingress direction

The direction to which the PCC rule is applied can come from the following two sources, in the order of preference:

  • Flow-Direction AVP inside of the Flow-Information AVP.

  • Inside of the Flow-Description AVP as part of IPFilterRule type (direction field).

1085

Redirect-Information

29.212/§5.3.82

Gx-PM-ESM

This is a Grouped AVP that contains HTTP redirect information. This can be used in:

  • PCC rules to HTTP redirect a flow or a group of flows.

  • HTTP redirect overrides to override currently applied URL within the subscriber filter.

1086

Redirect-Support

29.212/§5.3.83

Gx-PM-ESM

This AVP is nested inside of Redirect-Information AVP.

The values of this AVPs are:

  • REDIRECTION_DISABLED (0)

  • REDIRECTION-ENABLED (1)

The behavior for Redirect-Support in the 7750 SR is the following:

  • If the AVP value is REDIRECTION_ENABLED, the 7750 SR accepts it and HTTP redirect is in effect.

  • If the AVP value is different from REDIRECTION_ENABLED and M-bit is set (or inherited from parent AVP), the 7750 SR rejects it and the rule fails.

  • If the AVP value is different from REDIRECTION_ENABLED and M-bit is not set in this AVP or any of parent AVPs, the 7750 SR ignores it and the HTTP redirect is not explicitly disabled.

Not receiving this AVP has the same effect as it was received with value REDIRECTION_ENABLED.

1088

TDF-Application-Identifier

29.212/§5.3.77

Gx-UM-AA

This AVP is of type OctetString.

This AVP can be used in both PCC and ADC rules.

For AA, this identifier is a reference to a preconfigured charging-group, app-group or application.

1092

ADC-Rule-Install

29.212 / §5.3.85

Gx-PM-AA

Gx-UM-AA

This AVP is of type Grouped and is used to install or modify ADC (AA) rules in the 7750 SR as instructed by the PCRF.

1093

ADC-Rule-Remove

29.212/§5.3.86

Gx-PM-AA

Gx-UM-AA

This AVP is of type Grouped, and it is used to deactivate or remove ADC rules in the 7750 SR as instructed from the PCRF.

1094

ADC-Rule-Definition

29.212 / §5.3.87

Gx-PM-AA

Gx-UM-AA

This AVP is of type Grouped and it contains the rules that are to be activated.

AA rules that can be applied to a subscriber via Gx are:

  • Application-profile activation/override. A preexisting application-profile must be defined in the 7750 SR.

  • Application characteristic overrides.

  • Monitoring Key and a TDF-Application-Identifier. This installation of this rule has the effect of creating a usage monitoring instance for the subscriber for the specified TDF-Application-Identifier.

1096

ADC-Rule-Name

29.212 / §5.3.89

Gx-PM-AA

Gx-UM-AA

This AVP specifies the name of the ADC rule that is applied. This is an arbitrary string assigned by the PCRF and is used by the 7750 SR to report the rule status. In case that AA-Functions AVP is used (app-profile and ASO assignment/modification), this arbitrary name string must be prepended with a 7750 SR reserved keyword ‟AA-Functions:”.

1097

ADC-Rule-Report

29.212 / §5.3.90

Gx-PM-AA

Gx-UM-AA

This AVP is of type Grouped and is used to report the status of ADC rules which cannot be activated or enforced in the 7750 SR.

2848

Extended-APN-AMBR-DL

29.212 / §5.3.134

For higher rate requirements, this AVP can be used in place of the APN-Aggregate-Max-Bitrate-DL AVP.

2849

Extended-APN-AMBR-UL

29.212 / §5.3.135

For higher rate requirements, this AVP can be used in place of the APN-Aggregate-Max-Bitrate-UL AVP.

2850

Extended-GBR-DL

29.212 / §5.3.136

Gx-PM-ESM

For higher rate requirements, this AVP can be used in place of the Guaranteed-Bitrate-DL AVP.

2851

Extended-GBR-UL

29.212 / §5.3.137

Gx-PM-ESM

For higher rate requirements, this AVP can be used in place of the Guaranteed-Bitrate-UL AVP.

Standard diameter AVPs (format)

Standard diameter AVPs (format) lists standard diameter AVPs.

Incl/Excl – The attribute can be suppressed via CLI.

Flags (as set by the 7750 SR when the AVP is constructed):

  • V indicates Vendor specific bit.

  • M indicates Mandatory bit.

Note: The P flag bit is always set to 0.

UTF8String is a human-readable string using UTF-8 transformation format (which is for 7-bit encoding the same as US-ASCII).

OctetString is a basic data type which contains an arbitrary data. For example, Charging-Rule-Name AVP is OctetString according to RFC 6733 but in the 7750 SR it is displayed as readable string (UTF8String).

Flags for Gx specific AVPs are defined in RFC 6733, §4.5; 29.212, §5.3.

Flags for the Gx re-used AVPs are set as described in RFC 6733, §4.5 and in 3GPP 29.219, §5.4 — ‟The AVPs from Diameter base protocol are not included in Table 5.4, but they are re-used for the Gx reference point. Unless otherwise stated, re-used AVPs shall maintain their 'M', 'P' and 'V' flag settings. Where 3GPP RADIUS AVPs are re-used, unless otherwise stated, they shall be translated to Diameter AVPs as described in RFC 4005 [12] with the exception that the 'M' flag shall be set and the 'P' flag may be set”.

The NOKIA-specific AVPs will have the M-bit cleared.

NA — This keyword (Not Advertised) denotes that the AVP is not originated by the 7750 SR and therefore the 7750 SR does not set the flag bits. However, the 7750 SR recognizes the AVPs and corresponding values listed in the table, regardless of the M-bit flags set by PCRF. However, if the V-bit is present in the received AVP, then the Vendor-Id filed in the AVP layout also must be present and set to the correct value because the AVP with V-bit set is identified by the <avp-id, vendor-id> pair.

Table 2. Standard diameter AVPs (format)
AVP ID AVP name Incl/ Excl Type Flags Limits Format

5

NAS-Port

Yes

Unsigned32

M

4 octets

See the 7450 ESS, 7750 SR, and VSR RADIUS Attributes Reference Guide.

8

Framed-IP-Address

No

OctetString

M

4 octets

Example:

ip-address 10.11.12.13

Framed-IP-Address = 0a0b0c0d

As defined in RFC 4005, §6.11.1.

22

3GPP-User-Location-Info

Yes

Octetstring

V

—

Vendor-Id = 10415 (3GPP)

See 3GPP TS 29.061 for encoding details.

For example:

3GPP-User-Location-Info = 130 (TAI and ECGI), MNC 001, MCC 001, ECI 1, TAC 1

30

Called-Station-Id

Yes

UTF8String

M

64 chars

Example: Called-Station-Id = mac:ssid or mac only if ssid is not available.

31

Calling-Station-ID

Yes

UTF8String

M

64 chars

llid | mac | remote-id | sap-id | sap-string (a 64 character string configured at the SAP level)

Example: include-avp calling-station-id sap-id

  • MD-CLI
    configure subscriber-mgmt diameter-gx-policy gx include-avp calling-station-id type sap-id
  • classic CLI
    configure subscriber-mgmt diameter-application-policy gx include-avp calling-station-id sap-id

Calling-Station-Id = 1/1/2:1.1

55

Event-Time stamp

No

Time

M

4 octets

See the 7450 ESS, 7750 SR, and VSR RADIUS Attributes Reference Guide.

61

NAS-Port-Type

Yes

Enumerated

M

4 octets

The values for this attribute are defined in the RFC 2865, 4005 and 4603.

See the 7450 ESS, 7750 SR, and VSR RADIUS Attributes Reference Guide.

87

NAS-Port-Id

Yes

UTF8String

M

253 octets

See the 7450 ESS, 7750 SR, and VSR RADIUS Attributes Reference Guide.

92

NAS-Filter-Rule

NA

UTF8String

NA

Max 10 attributes per message or max 10 filter entries per message.

See the 7450 ESS, 7750 SR, and VSR RADIUS Attributes Reference Guide.

97

Framed-IPv6-Prefix

No

OctetString

M

—

SLAAC wan-host

<ipv6-prefix/prefix-length> with prefix-length 64

The AVP layout is:

<1 octet Reserved> <1 octet Length> <max 16 octets for Prefix>

123

Delegated-IPv6-Prefix

No

OctetString

M

—

<ipv6-prefix/prefix-length> with prefix-length [48 to 64]

The AVP layout is:

<1 octet Reserved> <1 octet Length> <max 16 octets for Prefix>

257

Host-IP-Address

No

Address

M

—

IPv4 Address

258

Auth-Application-Id

No

Unsigned32

M

—

Example:

Gx Auth-Application-Id = 16777238

260

Vendor-Specific-Application-Id

No

Grouped

M

—

This AVP contains the Vendor-Id AVP and Auth-Application-Id AVP.

For Gx, the Vendor-Id = 10415 (3GPP) and the Auth-Application-Id = 16777238.

263

Session-id

No

UTF8String

M

102 bytes

The session-id must be globally and eternally unique. The format of the session-id is the following:

<DiameterIdentity>;<high 32 bits>;<low 32 bits>

In the 7750 SR the session-id is defined as:

diameter-identity;boxuptime; seq-number

Example:

router.workstation.be;1391362206;1

264

Origin-Host

No

DiameterIdentity

M

80 bytes

Example:

Origin-Host = host-name-1@domain-name-1

265

Supported-Vendor-Id

No

Unsigned32

M

—

IANA assigned vendor number:

3GPP — 10415

ETSI — 13019

NOKIA — 6527

266

Vendor-Id

No

Unsigned32

M

—

IANA assigned vendor number:

3GPP — 10415

ETSI — 13019

NOKIA — 6527

BBF — 3561

267

Firmware-Revision

No

Unsigned32

—

—

Reference to the major/minor release version.

Example:

805 — Release 8R5

268

Result-Code

No

Unsigned32

M

—

See Result codes (Result-Code AVP) for Error Codes.

269

Product-Name

No

UTF8String

—

—

Vendor-assigned name for the product.

Example:

‟SR OS”

278

Origin-State-Id

No

Unsigned32

M

—

Example:

Origin-State-Id = 10

279

Failed-AVP

No

Grouped

M

—

This AVP contains the AVP that could not be processed successfully.

281

Error-Message

No

UTF8String

—

—

String describing the cause of the failure.

282

Route-Record

No

DiameterIdentity

M

80 bytes

Example:

Route-Record: host-1

283

Destination-Realm

No

DiameterIdentity

M

80 bytes

Example:

Destination-Realm = domain.com

285

Re-Auth-Request-Type

No

Enumerated

NA

—

This AVP is always received in RAR message and it is never sent by the 7750 SR.

0 — AUTHORIZE_ONLY

1 — AUTHORIZE_AUTHENTICATE

Example:

Re-Auth-Request-Type = 0

293

Destination-Host

No

DiameterIdentity

M

80 bytes

Operator configurable.

295

Termination-Cause

No

Enumerated

M

—

For a list of the 7750 SR supported values for Gx see Termination causes (Termination-Cause AVP) .

296

Origin-Realm

No

DiameterIdentity

M

80 bytes

Example:

Origin-Realm = origin-domain.com

297

Experimental-Result

No

Grouped

M

—

A grouped AVP containing:

  • Vendor-Id AVP

  • Experimental-Result-Code AVP

Example:

Experimental-Result = {Vendor-Id = 10415 (3GPP)

Experimental-Result-Code = DIAMETER_PCC_RULE_EVENT (5142)}

298

Experimental-Result-Code

No

Unsigned32

M

—

For a list of the 7750 SR supported values for Gx see Result codes (Result-Code AVP).

302

Logical-Access-Id

Yes

OctetString

V

—

Vendor ID = 13019 (ETSI)

313

Physical-Access-Id

Yes

UTF8String

V

—

Vendor ID = 13019 (ETSI)

412

CC-Input-Octets

No

Unsigned64

M

—

Example:

CC-Input-Octets = 1000000

414

CC-Output-Octets

No

Unsigned64

M

—

Example:

CC-Output-Octets = 1000000

415

CC-Request-Number

No

Unsigned32

M

—

Monotonically increasing from 0 for all requests within one session.

416

CC-Request-Type

No

Enumerated

M

—

Example:

CC-Request-Type = 1 (CCR-i)

3. CC-Request-Type = 2 (CCR-u)

CC-Request-Type = 3 (CCR-t)

418

CC-Session-Failover

No

Enumerated

M

—

FAILOVER_NOT_SUPPORTED (0)

FAILOVER_SUPPORTED (1)

Example:

CC-Session-Failover = 1

421

CC-Total-Octets

No

Unsigned64

M

—

Example:

CC-Total-Octets = 2000000

427

Credit-Control-Failure-Handling

No

Enumerated

M

—

TERMINATE (0)

CONTINUE (1)

RETRY_AND_TERMINATE (2)

Example:

Credit-Control-Failure-Handling = 1

431

Granted-Service-Unit

No

Grouped

M

—

This AVP can contain the following AVPs:

  • CC-Total-Octets

  • CC-Input-Octets

  • CC-Output-Octets

433

Redirect-Address-Type

No

Enumerated

M

—

Example:

Redirect-Address-Type = 2

(URL type)

435

Redirect-Server-Address

No

UTF8String

M

255 chars

Example:

Redirect-Server-Address = http://www.operator.com/portal.php&

443

Subscription-Id

Yes

Grouped

M

—

This AVP contains the following AVPs:

  • Subscription-Id-Type

  • Subscription-Id-Data

444

Subscription-Id-Data

Yes

UTF8String

M

—

Example:

Username — Subscription-Id-Data = user1@domain.com

Mac — Subscription-Id-Data = 11:22:33:44:55:66

Circuit-id — Subscription-Id-Data = dslam1 eth 2/1:100

Dual-stack-remote-id — Subscription-Id-Data = myRemoteId

Subscriber-id — Subscription-Id-Data = sub-id-1

Imsi Subscription-Id-Data = 204047910000598

Msisdn Subscription-Id-Data = 13109976224

Imei — Subscription-Id-Data = 356938035643809

446

Used-Service-Unit

No

Grouped

M

—

This AVP contains the following AVPs:

  • CC-Total-Octets

  • CC-Input-Octets

  • CC-Output-Octets

450

Subscription-Id-Type

Yes

Enumerated

M

—

Example:

Subscription-Id-Type = 0 (end_user_e164)

Subscription-Id-Type = 1 (end_user_imsi)

Subscription-Id-Type = 3 (end_user_nai)

Subscription-Id-Type = 4 (end_user_private)

458

User-Equipment-Info

Yes

Grouped

M

—

This AVP contains the following AVPs:

  • User-Equipment-Info-Type

  • User-Equipment-Info-Value

459

User-Equipment-Info-Type

Yes

Enumerated

—

—

Example:

User-Equipment-Info-Type = 0 (emissive)

User-Equipment-Info-Type =1 (mac)

User-Equipment-Info-Type = 2 (eui64)

User-Equipment-Info-Type = 3 (modified_eui64)

460

User-Equipment-Info-Value

Yes

OctetString

—

—

—

507

Flow-Description

No

IPFilterRule (RFC6733, §4.3.1)

NA,M

—

The IPFilterRule format within PCC rule in the 7750 SR has the following syntax:

action dir proto from src to dst

action — permit

dir — direction: in or out

proto — an IP protocol specified by number. The ip keyword means any protocol matches.

src and dest — <address/mask> and ports (including port ranges)

Example:

Flow-Description = allow in 6 from 192.168.7.0/24 3000-40000 to 172.16.10.0/26 10000-20000

511

Flow-Status

No

Enumerated

NA,M

—

Example:

Flow-Status = 3 — matched traffic inside of the PCC rule is dropped.

515

Max-Requested-Bandwidth-DL

No

Unsigned32

NA, V

—

The units of this parameter are kb/s for overrides and b/s when used within PCC rules.

The rate accounts for the IP header and above (no L2 header).

Vendor-Id = 10415 (3GPP)

Example:

Max-Requested-Bandwidth-DL = 1000 — 1 Mb/s in overrides

Max-Requested-Bandwidth-DL = 1000000 — 1 Mb/s in PCC rules

516

Max-Requested-Bandwidth-UL

No

Unsigned32

NA, V

—

The units of this parameter are kb/s for overrides and b/s when used within PCC rules.

The rate accounts for the IP header and above (no Layer 2 header).

Vendor-Id = 10415 (3GPP)

Example:

Max-Requested-Bandwidth-UL = 1000 — 1 Mb/s for overrides

Max-Requested-Bandwidth-UL = 1000000 — 1 Mb/s in PCC rules

554

Extended-Max-Requested-BW-DL

NA

Unsigned32

NA, V

—

The units of this parameter are kb/s.

Vendor-Id = 10415 (3GPP)

Example:

Extended-Max-Requested-BW-DL = 1000 — 1 Mb/s

555

Extended-Max-Requested-BW-UL

NA

Unsigned32

NA, V

—

The units of this parameter are kb/s.

Vendor-Id = 10415 (3GPP)

Example:

Extended-Max-Requested-BW-UL = 1000 — 1 Mb/s

628

Supported-Features

No

Grouped

V

—

This AVP contains the following AVPs:

  • Vendor-Id

  • Feature-List-Id

  • Feature-List

Vendor-Id = 10415 (3GPP)

Example for Extended-BW-NR:

Supported-Features

  • Vendor-Id = 10415 3GPP

  • Feature-List-Id = 2

  • Feature-List = 128

629

Feature-List-Id

No

Unsigned32

V

—

Vendor-Id = 10415 (3GPP)

Example:

Feature-List-Id = 2

630

Feature-List

No

Unsigned32

V

—

Vendor-Id = 10415 (3GPP)

Example:

Feature-List = 128

909

RAI

Yes

Octetstring

V

12 octets

Vendor-Id = 10415 (3GPP)

See 3GPP TS 29.061 for encoding details.

For example:

RAI = MCC 001, MNC 001, LAC 0xA2C1, RAC 0x0A

1001

Charging-Rule-Install

No

Grouped

NA, V

—

Vendor-Id = 10415 (3GPP)

This AVP contains the following AVPs:

  • Charging-Rule-Definition

  • Charging-Rule-Name

1002

Charging-Rule-Remove

No

Grouped

NA, V

—

Vendor-Id = 10415 (3GPP)

This AVP contains the following AVP:

Charging-Rule-Name

1003

Charging-Rule-Definition

No

Grouped

NA, V

—

Vendor-Id = 10415 (3GPP)

This AVP contains the following nested AVPs:

  • Charging-Rule-Name (provides the name to the overrides so that they can be referred in the Charging-Rule-Report – successful or failed rule instantiation)

  • QoS-Information (defines Qos overrides)

  • NAS-Filter-Rule

  • Alc-NAS-Filter-Rule-Shared

  • AA-Functions

1005

Charging-Rule-Name

No

OctetString

V,M

100 chars for PCC rules (defined via Charging-Rule-Definition AVP)

128 chars for overrides.

Vendor-Id = 10415 (3GPP)

This is an arbitrary rule name for PCC rules or a predefined string representing the overrides in the 7750 SR. Syntax for predefined names used in overrides are:

Filters:

  • Ingr-v4:<id>

  • Ingr-v6:<id>

  • Egr-v4:<id>

  • Egr-v6:<id>

  • In-Othr-v4:<id> (one-time-http-redirect)

ESM Strings:

  • Sub-Id: (64 Byte)

  • Sla-Profile:sla-profile-string (16 Byte)

  • Sub-Profile:sub-profile-string (16 Byte)

  • Inter-Dest:Inter-Dest-String to associate subscriber with Vport

HTTP Redirect Override

  • V4-http-url:url-string

  • V6-http-url:url-string

Category-Map (for usage monitoring):

Cat-Map:category-map-name

HTTP Redirect Override:

  • V4-http-url:url-string

  • V6-http-url:url-string

AA Strings:

  • AA-Functions: <name-string>

    This prefix indicates that the rule contains aa-specific information.

  • AA-UM: <name-string>

    This prefix indicates that the rule contains aa-specific usage-monitoring information, or points to a predefined aa-specific usage-monitoring rule.

Example:

Charging-Rule-Name = ingr-v4:5 ̶ reference to the predefined ingress IPv4 filter in 7450 ESS, 7750 SR, 7950 XRS, and VSR. The filter ID is 5.

Charging-Rule-Name =sla-profile:my-premium-sla ̶ reference to the predefined sla-profile in 7450 ESS, 7750 SR, 7950 XRS, and VSR. The sla-profile name is ‛my-premium-sla’.

1006

Event-Trigger

No

Enumerated

V

—

Vendor-Id = 10415 (3GPP)

For the list of supported event-triggers in the 7750 SR, see Event triggers (Event-Trigger AVP).

1010

Precedence

No

Unsigned32

NA, M

0 to 65535

Vendor-Id = 10415 (3GPP)

Example:

Precedence = 100

1014

Tos-Traffic-Class

No

OctetString

NA, M

—

Encoded as two octets. The first octet contains the IPv4 Type-of-Service or the IPv6 Traffic-Class field and the second octet contains the ToS/Traffic Class mask field. The only supported mask is 11111100 (6 bits denoting DSCP support).

Example:

ToS-Traffic-Class = 00101000 11111100 — DSCP AF11

1016

QoS-Information

NA

Grouped

NA, V

—

Vendor-Id 10415 (3GPP)

When used to signal a flow rate limiter in a PCC rule, this AVP contains the following nested AVPs:

  • Max-Requested-Bandwidth-UL

  • Max-Requested-Bandwidth-DL

  • Guaranteed-Bitrate-UL

  • Guaranteed-Bitrate-DL

1018

Charging-Rule-Report

No

Grouped

V,M

—

Vendor-Id = 10415 (3GPP)

This AVP contains the following nested AVPs:

  • Charging-Rule-Name

  • PCC-Rule-Status

  • Rule-Failure-Code

Example: Charging-Rule-Report {

Charging-Rule-Name = sla-profile:failed-profile

PCC-Rule-Status = 1 (inactive)

Rule-Failure-Code = 4 (GW/7750 SR_MALFUNCTION)

}

1019

PCC-Rule-Status

No

Enumerated

V,M

—

Vendor-Id = 10415 (3GPP)

Supported values in the 7750 SR:

1 – inactive

Example:

PCC-Rule-Status = 0 — rule is active

1025

Guaranteed-Bitrate-DL

NA

Unsigned32

NA,V

—

The units of this parameter are kb/s for overrides and b/s when used within PCC rules.

The rate accounts for the IP header and above (no Layer 2 header).

Vendor-Id = 10415 (3GPP)

Example:

Guaranteed-Bandwidth-DL = 1000 — 1 Mb/s in overrides

Guaranteed-Bandwidth-DL = 1000000 — 1 Mb/s in PCC rules

1026

Guaranteed-Bitrate-UL

NA

Unsigned32

V

—

The units of this parameter are kb/s for overrides and b/s when used within PCC rules.

The rate accounts for the IP header and above (no Layer 2 header).

Vendor-Id = 10415 (3GPP)

Example:

Guaranteed-Bandwidth-UL = 1000 — 1 Mb/s in overrides

Guaranteed-Bandwidth-UL = 1000000 — 1 Mb/s in PCC rules

1027

IP-CAN-Type

Yes

Enumerated

V

—

Vendor-Id = 10415 (3GPP)

Example:

IP-CAN-Type = 2 — xDSL

IP-CAN-Type = 5 — 3GPP-EPS

1028

QoS-Class-Identifier

NA

Enumerated

NA,M

—

Vendor-Id = 10415 (3GPP)

Example:

QoS-Class-Identifier = 3 — maps to FC EF.

1031

Rule-Failure-Code

No

Enumerated

V,M

—

Vendor-Id = 10415 (3GPP)

Example:

Rule-Failure-Code = 1 — UNKNOWN_RULE_NAME

1032

RAT-Type

Yes

Enumerated

V

—

Vendor-Id = 10415 (3GPP)

Example:

RAT-Type = 0 — WLAN

RAT-Type = 1004 — EUTRAN

1040

APN-Aggregate-Max-Bitrate-DL

Yes

Unsigned32

V

2^32-1 b/s

Vendor-Id = 10415 (3GPP)

Rate in bits per second (b/s)

For example:

APN-Aggregate-Max-Bitrate-DL = 100000000 (100 Mb/s)

1041

APN-Aggregate-Max-Bitrate-UL

Yes

Unsigned32

V

2^32-1 b/s

Vendor-Id = 10415 (3GPP)

Rate in bits per second (b/s)

For example:

APN-Aggregate-Max-Bitrate-UL = 10000000 (10 Mb/s)

1045

Session-Release-Cause

NA

Enumerated

V,M

—

Vendor-Id = 10415 (3GPP)

This AVP is only received by the 7750 SR and it is never sent by the 7750 SR.

0 — UNSPECIFIED-REASON

1 — UE_SUBSCRIPTION_REASON

This value is used to indicate that the subscription of UE has changed (for example, removed) and the session needs to be terminated.

2 — INSUFFICIENT_SERVER_ RESOURCES

This value is used to indicate that the server is overloaded and needs to abort the session.

Example:

Session-Release-Cause = 0

1050

AN-GW-Address

Yes

IPv4Address

V

—

Vendor-Id = 10415 (3GPP)

Example:

AN-GW-Address = 10.10.10.10

1058

Flow-Information

No

Grouped

V

—

Vendor-Id = 10415 (3GPP)

The following AVPs can be nested inside:

  • Flow-Description

  • ToS-Traffic-Class

  • Flow-Direction

1065

PDN-Connection-ID

Yes

UTF8String

V

100 chars

Vendor-Id = 10415 (3GPP)

For example:

PDN-Connection-ID = example-apn.mnc001.mcc001.gprs

1066

Monitoring-Key

No

OctetString

NA,V

32 bytes

Vendor-Id = 10415 (3GPP)

Category name configured in the 7750 SR, a string used for session monitoring or a Monitoring-Key AVP set in PCC rule definition with the Charging-Rule-Definition AVP.

Example:

Monitoring-Key = monitor-pcc-rule-1

1067

Usage-Monitoring-Information

No

Grouped

V

—

Vendor-Id = 10415 (3GPP)

This AVP contains the following nested AVPs:

  • Monitoring-Key

  • Granted-Service-Unit

  • Used-Service-Unit

  • Usage-Monitoring-Level

  • Usage-Monitoring-Report

  • Usage-Monitoring-Support

1068

Usage-Monitoring-Level

No

Enumerated

V

—

Vendor-Id = 10415 (3GPP)

The following values are defined:

0 – session_level

1 – pcc_rule_level

2 – adc_rule_level

Example:

Usage-Monitoring-Level = 0 — usage monitoring is performed based on sla-profile (IP-CAN session level) of the host.

Usage-Monitoring-Level = 1 — usage monitoring is performed based on predefined category as indicated by the monitoring-key AVP

Usage-Monitoring-Level = 2 — usage monitoring is performed based on ADC rule, as indicated by the monitoring-key AVP

1069

Usage-Monitoring-Report

No

Enumerated

V

—

Vendor-Id = 10415 (3GPP)

Example:

Usage-Monitoring-Report = 0

(usage_monitoring_report_required)

1070

Usage-Monitoring-Support

No

Enumerated

NA,V

—

Vendor-Id = 10415 (3GPP)

Example:

Usage-Monitoring-Support = 0 — usage_ monitoring_disabled

1080

Flow-Direction

No

Enumerated

NA,M

—

Vendor-Id = 10415 (3GPP)

Example:

Flow-Direction = 1 — egress

Flow-Direction = 2 — ingress

1085

Redirect-Information

No

Grouped

NA,V

—

Vendor-Id = 10415 (3GPP)

This AVP can contain the following AVPs:

  • Redirect-Support

  • Redirect-Address-Type

  • Redirect-Server-Address

1086

Redirect-Support

No

Enumerated

NA,V

—

Vendor-Id = 10415 (3GPP)

Example:

Redirect-Support = 1 — redirection is enabled

1088

TDF-Application-Identifier

OctetString

NA,V

32 chars long

Vendor-Id = 10415 (3GPP)

Example: 0_rated, BitTorrent

1092

ADC-Rule-Install

No

Grouped

NA,V

—

Vendor-Id = 10415 (3GPP)

This AVP contains the following nested AVPs:

ADC-Rule-Definition

1093

ADC-Rule-Remove

Grouped

NA,V

—

Vendor-Id = 10415 (3GPP)

This AVP contains the following nested AVPs:

ADC-Rule-Name

1094

ADC-Rule-Definition

No

Grouped

NA,V

—

Vendor-Id = 10415 (3GPP)

This AVP contains the following nested AVPs:

  • ADC-Rule-Name

  • MonitoringKey

  • TDF-Application-Id

  • AA-Functions {

    • AA profile

    • AA-App-Service-Options {

    • AA-App-Service-Options-Name

    • AA-App-Service-Options-Value

}

}

1096

ADC-Rule-Name

No

OctetString

V

17 chars for prefix/separator (optional) plus 32 chars for name

Vendor-Id = 10415 (3GPP)

Example:

For app-profile and ASO changes:

ADC-Rule-Name = ‟AA-Functions: AdcRuleWithAAFtn”

For usage monitoring:

ADC-Rule-Name = "AdcRuleWithoutAAFtn"

1097

ADC-Rule-Report

No

Grouped

V

—

Vendor-Id = 10415 (3GPP)

This AVP contains the following nested AVPs:

  • ADC-Rule-Name

  • PCC-Rule-Status

  • Rule-Failure-Code

2848

Extended-APN-AMBR-DL

NA

Unsigned32

NA, V

—

The units of this parameter are kb/s.

Vendor-Id = 10415 (3GPP)

Example:

Extended-APN-AMBR-DL = 1000 — 1 Mb/s

2849

Extended-APN-AMBR-UL

NA

Unsigned32

NA, V

—

The units of this parameter are kb/s.

Vendor-Id = 10415 (3GPP)

Example:

Extended-APN-AMBR-UL = 1000 — 1 Mb/s

2850

Extended-GBR-DL

NA

Unsigned32

NA, V

—

The units of this parameter are kb/s.

Vendor-Id = 10415 (3GPP)

Example:

Extended-GBR-DL = 1000 — 1 Mb/s

2851

Extended-GBR-UL

NA

Unsigned32

NA, V

—

The units of this parameter are kb/s.

Vendor-Id = 10415 (3GPP)

Example:

Extended-GBR-UL = 1000 — 1 Mb/s