2 Diameter Gy Interface Specification
2 Diameter Gy Interface Specification
RELEASE 16.0.R4
*[ Multiple-Services-Credit-Control ]
*[ Service-Parameter-Info ]
[ CC-Correlation-Id ]
[ User-Equipment-Info ]
*[ Proxy-Info ]
*[ Route-Record ]
*[ AVP ]
[ Framed-IP-Address ]
[ Called-Station-Id ]
[ Framed-IPv6-Prefix ]
[ Delegated-IPv6-Prefix ]
[ Alc-IPv6-Address ]
[ 3GPP-IMSI ]
[ 3GPP-Charging-Id ]
[ 3GPP-GPRS-QoS-Negotiated-Profile ]
[ 3GPP-GGSN-Address ]
[ 3GPP-NSAPI ]
[ 3GPP-Session-Stop-Indicator ]
[ 3GPP-Selection-Mode ]
[ 3GPP-Charging-Characteristics ]
[ 3GPP-GGSN-v6-Address ]
[ 3GPP-RAT-Type ]
[ 3GPP-User-Location-Info ]
[ GGSN-Address ]
[ Service-Information ]
[ Charging-Rule-Base-Name ]
[ PDP-Context-Type ]
8 Framed-IP-Address The IP address of the IPv4 subscriber host that triggered the
creation of the Diameter Gy session.
AVP included if configured in the diameter application policy:
configure subscriber-mgmt diameter-application-policy
application-policy-name gy include-avp address-avp
Included at command level or embedded within [3GPP – 873]
Service-Information / [3GPP – 874] PS-Information grouped
AVPs when configured (gy include-avp ps-information).
default: included
30 Called-Station-Id AVP included if configured in the diameter application policy:
configure subscriber-mgmt diameter-application-policy
application-policy-name gy include-avp called-station-id string
Included at command level or embedded within [3GPP – 873]
Service-Information / [3GPP – 874] PS-Information grouped
AVPs when configured (gy include-avp ps-information).
value: string of max. 64 characters
default: no called-station-id
123 Delegated-IPv6-Prefix The IPv6 prefix of the DHCPv6 IA-PD subscriber host that
triggered the creation of the Diameter Gy session.
AVP included if configured in the diameter application policy:
configure subscriber-mgmt diameter-application-policy
application-policy-name gy include-avp address-avp
Included at command level or embedded within [3GPP – 873]
Service-Information / [3GPP – 874] PS-Information grouped
AVPs when configured (gy include-avp ps-information).
default: included
263 Session-Id A session is a logical concept at the application layer that exists
between the Diameter client and the Diameter server; it is
identified via the Session-Id AVP.
Format:
<DiameterIdentity>; <high 32 bits>; <low 32 bits>
• <DiameterIdentity> is the configured origin host
• <high 32 bits> are encoded as the Diameter initialization
time (number of seconds since 1 January, 1970)
• <low 32 bits> are encoded as a sequentially increasing
number starting at 1
Example: bng.nokia.com;1326398325;1
NOKIA – 99 Alc-IPv6-Address The IPv6 address of the DHCPv6 IA-NA subscriber host that
triggered the creation of the Diameter Gy session.
AVP included if configured in the diameter application policy:
configure subscriber-mgmt diameter-application-policy
application-policy-name gy include-avp address-avp
Included at command level or embedded within [3GPP – 873]
Service-Information / [3GPP – 874] PS-Information grouped
AVPs when configured (gy include-avp ps-information).
default: included
3GPP – 1 3GPP-IMSI AVP included if configured in the diameter application policy:
configure subscriber-mgmt diameter-application-policy
application-policy-name gy include-avp 3gpp-imsi {circuit-id |
imsi | subscriber-id}
Included at command level or embedded within [3GPP – 873]
Service-Information / [3GPP – 874] PS-Information grouped
AVPs when configured (gy include-avp ps-information).
values:
• circuit-id
• imsi
• subscriber-id
default: included with value subscriber-id
3GPP – 16 3GPP-GGSN-v6-Address The local IPv6 address used to setup the diameter peer. AVP
included if configured in the diameter application policy:
configure subscriber-mgmt diameter-application-policy
application-policy-name gy include-avp 3gpp-ggsn-ipv6-
address
Included at command level or embedded within [3GPP – 873]
Service-Information / [3GPP – 874] PS-Information grouped
AVPs when configured (gy include-avp ps-information).
value:
1. Use the configured IPv6 source address:
configure aaa diameter-peer-policy peer-policy-name
ipv6-source-address ipv6-address
2. If router = base or vprn service id: use the system interface
IPv6 address
else if router = management: use the active management
port IP address configured in the BOF
default: not included
3GPP – 847 GGSN-Address The local address used to setup the diameter peer.
AVP included if configured in the diameter application policy:
configure subscriber-mgmt diameter-application-policy
application-policy-name gy include-avp ggsn-address {ipv4 |
ipv6}
Either IPv4 or IPv6 address can be included.
Included at command level or embedded within [3GPP – 873]
Service-Information / [3GPP – 874] PS-Information grouped
AVPs when configured (gy include-avp ps-information).
value:
1. Use the configured IP source address:
configure aaa diameter-peer-policy peer-policy-name
ipv6-source-address ipv6-address | source-address ip-
address
2. If router = base or vprn service id: use the system interface
IP address
else if router = management: use the active management
port IP address configured in the BOF
default: not included
3GPP – 873 Service-Information Grouped AVP containing the [3GPP – 874] PS-Information
↳ (grouped AVP) grouped AVP and embedding following AVPs:
• [8] Framed-IP-Address
• [30] Called-Station-Id
• [97] Framed-IPv6-Prefix
• [123] Delegated-IPv6-Prefix
• [NOKIA – 99] Alc-IPv6-Address
• [3GPP – 1] 3GPP-IMSI
• [3GPP – 2] 3GPP-Charging-Id
• [3GPP – 5] 3GPP-GPRS-Negotiated-QoS-profile
• [3GPP – 7] 3GPP-GGSN-Address
• [3GPP – 10] GGSN-NSAPI
• [3GPP – 11] 3GPP-Session-Stop-Indicator
• [3GPP – 12] 3GPP-Selection-Mode
• [3GPP – 13] 3GPP-Charging-Characteristics
• [3GPP – 16] 3GPP-GGSN-IPv6-Address
• [3GPP – 21] 3GPP-RAT-Type
• [3GPP – 847] GGSN-Address
• [3GPP – 1004] Charging-Rule-Base-Name
• [3GPP – 1247] PDP-Context-Type
AVP included if configured in the diameter application policy:
configure subscriber-mgmt diameter-application-policy
application-policy-name gy include-avp ps-information
When not configured the above listed AVPs are included at
command level.
default: no ps-information
3GPP – 1004 Charging-Rule-Base-Name AVP included if configured in the diameter application policy:
configure subscriber-mgmt diameter-application-policy
application-policy-name gy include-avp charging-rule-base-
name {category-map-name | string}
Included at command level or embedded within [3GPP – 873]
Service-Information / [3GPP – 874] PS-Information grouped
AVPs when configured (gy include-avp ps-information).
value:
• category-map-name: the name of the category-map in use
for this session
• string: a string of max. 64 characters.
default: charging-rule-base-name category-map-name
Grouped AVP format as defined in RFC 4006. Strikethrough formatted AVPs are not
included in CCR. Italic formatted AVPs listed after [AVP] are not defined in RFC
4006.
432 Rating-Group Rating group for which the quota is requested and/or
reported. Corresponds with a category within a
category-map defining the queues/policers and
direction to monitor.
configure subscriber-mgmt category-map
category-map-name category category-name rating-
group rating-group-id
3GPP – 872 Reporting-Reason Specifies the reason for which the Used-Service-Units
are reported. CCR-U and CCR-T only.
Values
• 0 (Threshold) – used quota reached time or
volume threshold value (threshold value different
from zero)
• 1 (Quota Holding Time) – expiration of the Quota
Holding Time
• 2 (Final) – Diameter session termination; can be
client or server initiated.
• 3 (Quota Exhausted) – no threshold or threshold
is zero and quota exhausted
• 4 (Validity Time) – expiration of the Validity Time
• 5 (Other Quota Type) – not supported
• 6 (Rating Condition Change) – not supported
• 7 (Forced Reauthorisation) – Reception of a RAR
message
• 8 (Pool Exhausted) – not supported
Grouped AVP format as defined in RFC 4006. Strikethrough formatted AVPs are not
included in CCR.
[ CC-Total-Octets ]
[ CC-Input-Octets ]
[ CC-Output-Octets ]
[ CC-Service-Specific-Units ]
*[ AVP ]
The Requested-Service-Unit AVP has an empty data field in all CCR Initial/Update
messages and is not present in a CCR Terminate message.
Grouped AVP format as defined in RFC 4006. Strikethough formatted AVPs are not
included in CCR.
Grouped AVP format as defined in TS 32.29. Strikethrough formatted AVPs are not
included in CCR.
Strikethrough formatted AVPs are not included in CCR. Italic formatted AVPs listed
at the end are not defined in TS 32.299.
For a description and format of the AVPs embedded in the grouped PS-Information
AVP, refer to Table 2 and Table 3.
[ Terminal-Information ]
[ Start-Time ]
[ Stop-Time ]
[ Change-Condition ]
[ Diagnostics ]
[ Framed-IP-Address ]
[ Framed-IPv6-Prefix ]
[ Delegated-IPv6-Prefix ]
[ Alc-IPv6-Address ]
[ 3GPP-IMSI ]
[ 3GPP-GPRS-Negotiated-QoS-profile ]
[ 3GPP-GGSN-Address ]
[ 3GPP-GGSN-IPv6-Address ]
427 Credit-Control-Failure- Action to take when the Credit Control client does not
Handling receive a valid CCA message within the interval
specified with tx-timer (default 10s).
Overrides the configured failure handling: configure
subscriber-mgmt diameter-application-policy
application-policy-name on-failure [failover {enabled |
disabled}] [handling {continue | retry-and-terminate
| terminate}]
Values:
0 = Terminate
1 = Continue
2 = Retry and terminate
The failed-AVP AVP contains the entire AVP that could not be processed
successfully.
Grouped AVP format as defined in RFC 4006: Strikethrough formatted AVPs should
not appear or are ignored in CCA. Italic formatted AVPs listed after [AVP] are not
defined in RFC 4006.
430 Final-Unit-Indication This AVP indicates that the Granted-Service-Unit contains the
↳ (grouped AVP) final units for the service. When this quota is consumed, a final
reporting is started (CCR-U or CCR-T) with reporting reason
“Final”. The final reporting can be disabled with configure
subscriber-mgmt diameter-application-policy application-
policy-name
gy out-of-credit-reporting quota-exhausted
431 Granted-Service-Unit Amount of service units that the Diameter credit control client can
↳ (grouped AVP) provide to the end user until the service must be released or a
new CCR message must be sent.
432 Rating-Group Rating group for which the quota is allocated. Corresponds with
a category within a category-map defining the queues/policers
and direction to monitor.
configure subscriber-mgmt category-map category-map-
name category category-name rating-group rating-group-id
448 Validity-Time If the granted service units have not been consumed within the
validity time, a CCR-U is triggered with Reporting Reason AVP
set to 4 (Validity Time).
Value in seconds
3GPP – 868 Time-Quota-Threshold Threshold preventing time quota exhaustion prior to refreshing.
When the used time quota exceeds the threshold, a CCR-U is
triggered with Reporting Reason AVP set to 0 (Threshold).
Value in seconds
3GPP – 871 Quota-Holding-Time Specifies an idle-timeout associated with the granted service
units. If no traffic associated with the quota is observed for the
time specified by the quota holding time, then a CCR-U is
triggered with Reporting Reason AVP set to 1 (Quota Holding
Time). The idle time is measured per sampling period.
Value in seconds
Grouped AVP format as defined in RFC 4006: Strikethrough formatted AVPs should
not appear or are ignored in CCA.
Grouped AVP format as defined in RFC 4006. Strikethrough formatted AVPs should
not appear or are ignored in CCA.
For a single rating group (category), either Volume or Time quota can be granted.
Granting both time and volume quota for a single rating group is not supported and
results in a Diameter Session Failure and the execution of the Credit Control Failure
Handling action.