SIST ES 283 034 V2.2.0:2009

ETSI ES 283 034 V2.2.0 (2008-07)
ETSI Standard
Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Network Attachment Sub-System (NASS);
e4 interface based on the DIAMETER protocol

2 ETSI ES 283 034 V2.2.0 (2008-07)

Reference
RES/TISPAN-03139-NGN-R2
Keywords
interface, network, system
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI ES 283 034 V2.2.0 (2008-07)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.6
2 References.6
2.1 Normative references.6
2.2 Informative references.7
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.7
4 Overview.8
5 Procedure descriptions .9
5.1 General.9
5.1.1 Information elements.9
5.1.2 NASS User profile.9
5.2 Procedures on the CLF - A-RACF interface .10
5.2.1 Access profile push.10
5.2.1.1 Overview.10
5.2.1.2 Procedure at the CLF side .11
5.2.1.3 Procedure at the A-RACF side.11
5.2.2 Access Profile Pull.12
5.2.2.1 Overview.12
5.2.2.2 Procedure at the A-RACF side.13
5.2.2.3 Procedure at the CLF side .13
5.2.3 IP connectivity release indication .14
5.2.3.1 Overview.14
5.2.3.2 Procedure at the CLF side .14
5.2.3.3 Procedure at the A-RACF side.15
6 Use of the Diameter base protocol .15
6.1 Securing Diameter messages.15
6.2 Accounting functionality.15
6.3 Use of sessions .15
6.4 Transport protocol.15
6.5 Routing considerations.16
6.6 Advertising application support .16
7 DIAMETER application.16
7.1 Commands.16
7.1.1 User-Data-Request command.17
7.1.2 User-Data-Answer command.17
7.1.3 Push-Notification-Request command.18
7.1.4 Push-Notification-Answer command.18
7.2 Result-Code AVP values.18
7.2.1 Success.19
7.2.2 Permanent failures.19
7.2.3 Transient failures.19
7.3 AVPs.19
7.3.1 Globally-Unique-Address AVP.21
7.3.2 Address-Realm AVP.21
7.3.3 Logical-Access-ID AVP.21
7.3.4 Initial-Gate-Setting-Description AVP.21
7.3.5 QoS-Profile-Description AVP.21
7.3.6 IP-Connectivity-Status AVP.22
7.3.7 Access-Network-Type AVP.22
ETSI
4 ETSI ES 283 034 V2.2.0 (2008-07)
7.3.8 Aggregation-Network-Type AVP.22
7.3.9 Maximum-Allowed-Bandwidth-UL AVP.22
7.3.10 Maximum-Allowed-Bandwidth-DL AVP.22
7.3.11 Reservation-Priority.22
7.3.12 Transport-Class.23
7.3.13 Application-Class-ID.23
7.3.14 Physical-Access-ID.23
7.3.15 NAS-Port-Type AVP.23
7.3.16 NAS-Filter-Rule AVP.23
7.3.17 Framed-IP-Address AVP.24
7.3.18 Framed-IP-Prefix AVP.24
7.3.19 Origin-Host AVP.24
7.3.20 AF-Application-Identifier AVP.24
7.3.21 Media-Type AVP.24
7.3.22 Initial-Gate-Setting-ID AVP.24
7.3.23 QoS-Profile-ID AVP.24
7.4 Use of namespaces .24
7.4.1 AVP codes.24
7.4.2 Experimental-Result-Code AVP values.24
7.4.3 Command Code values .24
7.4.4 Application-ID value.25
Annex A (informative): Mapping of e4 operations and terminology to Diameter.26
History .27

ETSI
5 ETSI ES 283 034 V2.2.0 (2008-07)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN).
ETSI
6 ETSI ES 283 034 V2.2.0 (2008-07)
1 Scope
The present document defines a protocol for use between the TISPAN NGN Network Attachment Sub-System (NASS)
and the Resource and Admission Control Subsystem (RACS), based on Diameter.
The present document is applicable to the e4 interface between the Connectivity Session Location and Repository
Function (CLF) and the RACS.
Whenever it is possible the present document specifies the requirements for this protocol by reference to specifications
produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined
within the present document.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ETSI ES 282 004: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment
Sub-System (NASS)".
[2] ETSI ES 282 003: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Resource and Admission Control Sub-system (RACS);
Functional Architecture".
[3] ETSI TS 129 229: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Cx and Dx interfaces based on the Diameter protocol;
Protocol details (3GPP TS 29.229)".
[4] ETSI TS 129 329: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Sh interface based on the Diameter protocol; Protocol
details (3GPP TS 29.329)".
ETSI
7 ETSI ES 283 034 V2.2.0 (2008-07)
[5] ETSI TS 129 209: "Universal Mobile Telecommunications System (UMTS); Policy control over
Gq interface (3GPP TS 29.209)".
[6] IETF RFC 2960: "Stream Control Transmission Protocol".
[7] IETF RFC 3588: "Diameter base protocol".
[8] IETF RFC 3309: "Stream Control Transmission Protocol (SCTP) Checksum Change".
[9] IETF RFC 4005: "Diameter Network Access Server application".
[10] IETF RFC 3554: "On the use of Stream Control Transmission Protocol (SCTP) with IPsec".
[11] IETF RFC 3046: "DHCP Relay Agent Information Option".
[12] ETSI TS 183 017: "Telecommunications and Internet Converged Services and Protocols for
Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER protocol for
session based policy set up information exchange between the Application Function (AF) and the
Service Policy Decision Function (SPDF); Protocol specification".
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
Not applicable.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Application Function (AF): element of the service layer architecture offering applications that require information
about the characteristics of the IP-connectivity session used to access such applications
Attribute-Value Pair (AVP): corresponds to an information element in a Diameter message
NOTE: See RFC 3588 [7].
NASS User: See definition in [1].
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ABNF Augmented Backus-Naur Form
AF Application Function
A-RACF Access-Resource and Admission Control Function
ATM Asynchronous Transfer Mode
AVP Attribute-Value Pair
CLF Connectivity session Location and repository Function
DHCP Dynamic Host Configuration Protocol
FQDN Fully Qualified Domain Name
IANA Internet Assigned Numbers Authority
ID IDentifier
IETF Internet Engineering Task Force
IPSec IP Security
NAS Network Access Server
ETSI
8 ETSI ES 283 034 V2.2.0 (2008-07)
NASS Network Attachment Sub-System
PDBF Profile Data Base Function
PNA Push-Notification-Answer
PNR Push-Notification-Request
QoS Quality of Service
RACF Resource and Admission Control Function
RACS Resource and Admission Control Subsystem
RCEF Resource Control Enforcement Function
RFC Request For Comments
SCTP Stream Control Transport Protocol
SPDF Service-based Policy Decision Function
UAAF User Authentication and Authorization Function
UDA User-Data-Answer
UDR User-Data-Request
VC Virtual Channel
VP Virtual Path
4 Overview
The Network Attachment Sub-System (NASS), defined in ES 282 004 [1], maintains information about IP-connectivity
associated with uNASS Users connected to TISPAN networks. This information is stored in the Connectivity session
Location and repository Function (CLF) and made accessible to other subsystems and applications through the
following two interfaces (see figure 1):
• The e2 interface enables Application Functions (AF) to retrieve IP-connectivity related session data.
• The e4 interface enables the IP-connectivity related session data to be exchanged between the NASS and the
Resource and Admission Control Subsystem (RACS) defined in ES 282 003 [2].
The present document specifies the protocol for the e4 interface.
Service Control
Subsystems and
Applications
AF
e2
CLF
NASS
e4
Scope of the present
A-RACF
document
RACS
Transfer Functions
Figure 1: NASS external interfaces
ETSI
9 ETSI ES 283 034 V2.2.0 (2008-07)
5 Procedure descriptions
5.1 General
5.1.1 Information elements
The following clauses describe the realization of the functional procedures defined in the NASS (ES 282 004) [1] and
RACS specifications (ES 282 003 [2]) using Diameter commands described in clause 7. This involves describing a
mapping between the information elements defined in the NASS specification (ES 282 004 [1]) and Diameter AVPs.
In the tables that describe this mapping, each information element is marked as (M) Mandatory, (C) Conditional or (O)
Optional:
• A mandatory information element (marked as (M) in tables 1 to 8) shall always be present in the command. If
this information element is absent, an application error occurs at the receiver and an answer message shall be
sent back to the originator of the request with the Result-Code set to DIAMETER_MISSING_AVP. This
message shall also include a Failed-AVP AVP containing the missing information element i.e. the
corresponding Diameter AVP defined by the AVP Code and the other fields set as expected for this
information element.
• A conditional information element (marked as (C) in tables 1 to 8) shall be present in the command if certain
conditions are fulfilled:
- If the receiver detects that those conditions are fulfilled and the information element is absent, an
application error occurs and an answer message shall be sent back to the originator of the request with
the Result-Code set to DIAMETER_MISSING_AVP. This message shall also include a Failed-AVP
AVP containing the missing information element i.e. the corresponding Diameter AVP defined by the
AVP Code and the other fields set as expected for this information element. If multiple information
elements are missing, all corresponding AVP codes shall be included in the Failed-AVP AVP.
- If those conditions are not fulfilled, the information element shall be absent. If however this information
element appears in the message, it shall not cause an application error and it may be ignored by the
receiver if this is not explicitly defined as an error case. Otherwise, an application error occurs at the
receiver and an answer message with the Result-Code set to DIAMETER_AVP_NOT_ALLOWED shall
be sent back to the originator of the request. A Failed-AVP AVP containing a copy of the corresponding
Diameter AVP shall be included in this message.
• An optional information element (marked as (O) in tables 1 to 8) may be present or absent in the command, at
the discretion of the application at the sending entity. Absence or presence of this information element shall
not cause an application error and may be ignored by the receiver.
5.1.2 NASS User profile
NASS User profile information sent over the e4 interface comprises QoS profile information and initial gate setting
information. Each of these pieces of information may be sent in the form of an identifier using the QoS-Profile-ID and
Initial-Gate-Setting-ID AVPs or in the form of an explicit description using the QoS-Profile-Description and Initial-
Gate-Setting-Description AVPs.
Tables 1 and 2 detail the information elements involved in the second case as defined in the NASS specification
ES 282 004 [1] and their mapping to DIAMETER AVPs.
ETSI
10 ETSI ES 283 034 V2.2.0 (2008-07)
Table 1: Initial gate setting description
Information Mapping to Cat. Description
element name Diameter AVP
List of allowed NAS-Filter-Rule O In case of unicast data, the list of default destination IP addresses
destinations as ports, prefixes and port ranges to which traffic can be sent. In case of
well as multicast, the list of IP-Multicast group addresses and/or the list of
multicast flows (Source IP address, IP-Multicast group address) pairs which traffic can
be received from by the attached NASS User.
List of denied NAS-Filter-Rule O In case of unicast, the list of default destination IP addresses ports,
destinations as prefixes and port ranges to which traffic is denied. In case of multicast,
well as the list of IP-Multicast group addresses and/or the list of (Source IP
multicast flows address, IP-Multicast group address) pairs for which traffic towards the
attached NASS User must be denied.
UL Subscribed Maximum-Allowed- O The maximum amount of bandwidth that can be used without explicit
Bandwidth Bandwidth-UL authorization in the uplink direction.
DL Subscribed Maximum-Allowed- O The maximum amount of bandwidth that can be used without explicit
Bandwidth Bandwidth-DL authorization in the downlink direction.

Table 2: QoS profile description
Information Mapping to Cat. Description
element name Diameter AVP
Transport Transport-Class O The transport class applicable to the QoS Profile Information.
service class
Media-Type Media-Type O The media type applicable to the QoS Profile information.
UL Subscribed Maximum-Allowed- O The maximum amount of bandwidth subscribed by the attached NASS
Bandwidth Bandwidth-UL User in the uplink direction.
DL Subscribed Maximum-Allowed- O The maximum amount of bandwidth subscribed by the attached NASS
Bandwidth Bandwidth-DL User in the downlink direction.
Maximum Reservation-Priority O The maximum priority allowed for any reservation request.
Priority
Requestor Application Class ID O Identifies the application class(es) that are allowed to request
Name resources for the QoS profile.

5.2 Procedures on the CLF - A-RACF interface
5.2.1 Access profile push
5.2.1.1 Overview
This procedure is used to push session-related information from the CLF to the A-RACF. This information flow occurs
when an IP address has been allocated to a NASS User or in case a modification occurs on a profile that has already
been pushed to the RACS.
The CLF should push session-related-information to the A-RACF as soon as it is available to the CLF. This may require
the CLF to pull part of the information from other components of the NASS.
For the same NASS User, the CLF may push several independent session records with different IP addresses, with or
without the same logical access identifier.
This procedure is mapped to the commands Push-Notification-Request/Answer in the Diameter application specified in
clause 7. Tables 3 and 4 detail the involved information elements as defined in the NASS specification ES 282 004 [1]
and their mapping to Diameter AVPs.
ETSI
11 ETSI ES 283 034 V2.2.0 (2008-07)
Table 3: Access profile push
Information Mapping to Diameter Cat. Description
element name AVP
Globally Unique Globally-Unique-Address M This information element contains:
IP Address - The IP address of the NASS User for which profile
information is being pushed.
- The addressing domain in which the IP address is
significant.
Logical Access Logical-Access-Id M The identity of the logical access to which the user equipment is
ID connected.
Access Access-Network-Type O The type of access network over which IP connectivity is provided
Network Type to the user equipment.
NASS User ID User-Name C The NASS User that is attached to the network (see note).
Physical Physical-Access-Id O The identity of the physical access to which the user equipment is
Access ID connected.
Initial Gate Initial-Gate-Setting or O See clause 5.1, table 1.
Setting Initial-Gate-Setting-ID
QoS Profile QoS-Profile or QoS- O See clause 5.1, table 2.
Profile-ID
NOTE: The NASS User ID shall be included if available in the CLF.

Table 4: Access profile push response
Information Mapping to Diameter AVP Cat. Description
element name
Result Result-Code / Experimental_ M Result of the request.
Result Result-Code AVP shall be used for errors defined in the
Diameter base protocol.
Experimental-Result AVP shall be used for other errors. This
is a grouped AVP which contains a Vendor-Id AVP, and the
error code in the Experimental-Result-Code AVP.

5.2.1.2 Procedure at the CLF side
The CLF knows the address of the A-RACF entity where the information should be pushed, either from configuration
data or from the NASS User profile (i.e. received from the UAAF/PDBF).
The CLF shall populate the Access Profile Push as follows:
• The Globally-Unique-Address AVP shall contain a Frame-IP-Address or Frame-IPv6-Prefix AVP value, and
an Address-Realm AVP.
• The Logical-Access-ID AVP shall be present.
The presence of the other AVPs depends on the NASS User profile and local policy rules.
5.2.1.3 Procedure at the A-RACF side
If the Logical Access ID is not included or is invalid, the A-RACF shall return an Access Profile Push response with a
Result-Code AVP value set to DIAMETER_INVALID_AVP_VALUE.
If the globally unique identifier contained in the Globally-Unique-Address AVP is not known, the A-RACF shall:
• Create an internal record to store the received information for future use (i.e. for processing resource
reservation requests received from the SPDF).
• Derive the following information from the Logical Access ID:
- The identification and bandwidth capacity of the layer 2 resources over which the NASS user traffic is to
be carried.
- The address of the transport network node(s) implementing an RCEF.
ETSI
12 ETSI ES 283 034 V2.2.0 (2008-07)
• If the received information contains an Initial-Gate-Setting-Description or Initial-Gate-Setting-ID AVP,
perform any appropriate actions to enforce the policy information. This involves interacting with one or more
RCEFs through the Re interface.
If the globally unique identifier contained in the Globally-Unique-Address AVP is already known, the A-RACF shall:
• Replace the entire content of the internal record with the received information for future use.
• If the received information contains an Initial-Gate-Setting-Description or Initial-Gate-Setting-ID, perform any
appropriate actions to enforce the new policy information. This may involve interacting with the RCEF
through the Re interface.
When an Initial-Gate-Setting-ID is received, the A-RACF shall derive a set of associated traffic filter rules before
interacting with an RCEF or a subordinated x-RACF. If the value of the Initial-Gate-Setting-ID is unknown, the A-
RACF shall return an Access Profile Push response with a Result-Code AVP value set to
DIAMETER_INVALID_AVP_VALUE.
Such an update shall not have any impact on ongoing application sessions for which an authorization has already been
provided by the A-RACF.
If the contents of the request are invalid the A-RACF shall return an Access Profile Push response with a Result-Code
AVP value set to the appropriate value as described in clause 5.1.
If the creation or modification of the session record is successful but a failure occurs during the processing of the Initial
Gate Settings (e.g. due to a failure in the interaction with the RCEF), the A-RACF shall return an Access Profile Push
response with a Result-Code AVP value set to DIAMETER_LIMITED_SUCCESS.
If the A-RACF cannot fulfil the received request for reasons not stated in the above steps, e.g. due to database error, it
shall stop processing the request and return an Access Profile Push response with a Result-Code AVP value set to
DIAMETER_UNABLE_TO_COMPLY or an Experimental-Result-Code AVP set to
DIAMETER_SYSTEM_UNAVAILABLE. In the later case, the CLF is expected to retry after a provisioned time
period.
Otherwise, the requested operation shall take place and the A-RACF shall return the Result-Code AVP set to
DIAMETER_SUCCESS in the Access Profile Push response.
5.2.2 Access Profile Pull
5.2.2.1 Overview
This procedure is used by the RACS to request the Access Profile information from the CLF, in the context of recovery
procedures.
This procedure is mapped to the commands User-Data-Request/Answer in the Diameter application specified in
clause 7. Tables 5 and 6 detail the involved information elements as defined in the NASS specification ES 282 004 [1]
and their mapping to Diameter AVPs.
Table 5: Access Profile Pull request
Information Mapping to Cat. Description
element name Diameter AVP
Globally unique Globally-Unique- C This information element contains:
IP Address Address - The IP address of the NASS User for which profile information
is being pushed.
- The addressing domain in which the IP address is significant.
NASS User ID User-Name C The NASS User that is attached to the network.
RACS-Id AF-Application- M Identifies the A-RACF function requesting profile information.
Identifier
ETSI
13 ETSI ES 283 034 V2.2.0 (2008-07)
Table 6: Access Profile Pull response
Information Mapping to Diameter Cat. Description
element name AVP
Globally unique Globally-Unique- C This information element contains:
IP Address Address - The IP address of the NASS User for which profile
information is being pushed.
- The addressing domain in which the IP address is
significant.
Logical Access Logical-Access-Id M The identity of the logical access to which the user equipment is
ID connected.
Access Access-Network-Type O The type of access network over which IP connectivity is provided to
Network Type the user equipment.
NASS User ID User-Name C The identity of the NASS User that is attached to the network.
Physical Physical-Access-Id O The identity of the physical access to which the user equipment is
Access ID connected.
Initial Gate Initial-Gate-Setting- O See clause 5.1
Settings Description or Initial-
Gate-Setting-ID
QoS Profile QoS-Profile- O See clause 5.1
Description or Initial-
QoS-Profile-ID
5.2.2.2 Procedure at the A-RACF side
The A-RACF may use this procedure after a restart, upon reception of the resource reservation request associated with
an IP-Address for which no record is stored.
The A-RACF shall populate the Access Profile Pull request as follows:
1) The User-Name AVP or the Globally-Unique-Address AVP shall be included. The Globally-Unique-Address
AVP shall be included in configurations where more than one IP address may be assigned per NASS User ID .
2) If present, the Globally-Unique-Address AVP shall contain a Frame-IP-Address or Frame-IPv6-Prefix AVP
value, and an Address-Realm AVP. The Address-Realm AVP shall be included and set either using
configuration data (in which case all terminal equipment served by the A-RACF belong to the same addressing
domain) or from the physical or logical interface over which was received the resource request that triggered
the pull procedure.
3) The AF-Application-Identifier AVP shall be present and set to the A-RACF Identity.
5.2.2.3 Procedure at the CLF side
Upon reception of the Access Profile Pull request, the CLF shall, in the following order:
1) If the Globally-Unique-Address AVP is present, use this information as a key to retrieve the requested session
information.
2) If the Globally-Unique-Address AVP is absent but the User-Name AVP is present, use the latter information
as a key to retrieve the requested session information.
3) If both the Globally-Unique-Address AVP and the User-Name AVP are absent, return an Access Pull Profile
response with Result-Code set to DIAMETER_MISSING_AVP.
4) If more than one record include the same NASS User ID matching the value of the User-Name AVP and no
Globally-Unique-Address AVP is included, return an Access Pull Profile response with Result-Code set to
DIAMETER_UNABLE_TO_COMPLY.
5) If no session record is stored for the Globally-Unique-Address AVP or the User-Name AVP, return an Access
Pull Profile with the Experimental-Result-Code AVP shall be set to
DIAMETER_ERROR_USER_UNKNOWN.
ETSI
14 ETSI ES 283 034 V2.2.0 (2008-07)
If a unique NASS User record car be retrieved, the CLF shall:
1) Check which session data can be returned to the A-RACF, based on local policy rules and per-NASS User
privacy information stored in the CLF.
2) Check whether the session data to be retrieved is currently being updated by another entity. If there is an
update of the data in progress, the CLF may delay the response message until the update has been completed
and shall include in the response message the updated data requested. The CLF shall ensure that the data
returned is not corrupted by this conflict.
If the CLF cannot fulfil the received request for reasons not stated in the above steps, e.g. due to database error, it shall
stop processing the request and set Result-Code to DIAMETER_UNABLE_TO_COMPLY or an
Experimental-Result-Code AVP set to DIAMETER_USER_DATA_NOT_AVAILABLE.
Otherwise, the requested operation shall take place and the CLF shall return the Result-Code AVP set to
DIAMETER_SUCCESS and the session data in the Access Profile Pull response.
5.2.3 IP connectivity release indication
5.2.3.1 Overview
This procedure is used by the CLF to report loss of IP connectivity. This enables the RACS to remove the access profile
from its internal data base. This event occurs in case the allocated IP address is released (e.g. DHCP leased timer
expiry) or due to a release of the underlying layer 2 resources.
This procedure is mapped to the commands Push-Notification-Request/Answer in the Diameter application specified in
clause 7. Tables 7 and 8 detail the involved information elements as defined in the NASS specification ES 282 004 [1]
and their mapping to Diameter AVPs.
Table 7: IP connectivity release indication
Information Mapping to Cat. Description
element name Diameter AVP
Globally unique Globally-Unique- M This information element contains:
IP Address Address - The IP address of the NASS User for which profile information
is being pushed.
- The addressing domain in which the IP address is significant.
NASS User ID User-Name O The identity of the NASS User that is attached to the network.
IP-Connectivity IP-Connectivity- M Whether IP connectivity to/from the NASS Usert is currently available.
Status Status
Table 8: IP connectivity release indication response
Information Mapping to Cat. Description
element name Diameter AVP
Result Result-Code / M Result of the request.
Experimental_ Result-Code AVP shall be used for errors defined in the Diameter base
Result protocol.
Experimental-Result AVP shall be used for other errors. This is a grouped
AVP which contains a Vendor-Id AVP, and the error code in the
Experimental-Result-Code AVP.
5.2.3.2 Procedure at the CLF side
On receipt of an external event indicating that the allocated IP address has been released or the underlying layer 2
connection has been lost, the CLF shall clear all information stored against the IP address and issue a
Push-Notification-Request representing an IP-Connectivity-Release-Indication with the IP-Connectivity-Status AVP set
to the value IP-CONNECTIVITY-LOST.
NOTE: Receipt of an indication that a layer 2 connection has been lost may lead the CLF to issue several
notifications, in case multiple access sessions where associated with this connection.
ETSI
15 ETSI ES 283 034 V2.2.0 (2008-07)
5.2.3.3 Procedure at the A-RACF side
If the globally unique identifier contained in the Globally-Unique-Address AVP is not known, the A-RACF shall stop
processing the request and set the Experimental-Result-Code to DIAMETER_ERROR_USER_UNKNOWN in the IP
Connectivity Release Indication Response.
If the globally unique identifier contained in the Globally-Unique-Address AVP is already known, the A-RACF shall:
• remove the existing session record;
• interact with transfer layer entities (i.e. RCEF) to remove transport policies associated with the session and
clear associated resources;
• notify the SPDF.
If the A-RACF cannot fulfil the received request for reasons not stated in the above steps, e.g. due to database error, it
shall stop processing the request and set Result-Code to DIAMETER_UNABLE_TO_COMPLY or an
Experimental-Result-Code set to DIAMETER_SYSTEM_UNAVAILABLE. In the later case, the CLF is expected to
retry after a provisioned time period.
Otherwise, the requested operation shall take place and the A-RACF shall return an IP-Connectivity-Release-Indication
response with the Result-Code AVP set to DIAMETER_SUCCESS.
6 Use of the Diameter base protocol
With the clarifications listed in the following clauses the Diameter base protocol defined by RFC 3588 [7] shall apply.
6.1 Securing Diameter messages
For secure transport of Diameter messages, IPSec may be used. Guidelines on the use of SCTP with IPSec can be found
in RFC 3554 [10].
6.2 Accounting functionality
Accounting functionality (accounting session state machine, related command codes and AVPs) is not used on the e4
interface.
6.3 Use of sessions
Diameter sessions are implicitly terminated. An implicitly terminated session is one for which the server does not
maintain state information. The client does not need to send any re-authorization or session termination requests to the
server.
The Diameter base protocol includes the Auth-Session-State AVP as the mechanism for the implementation of
implicitly terminated sessions.
The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value
NO_STATE_MAINTAINED (1), as described in RFC 3588 [7]. As a consequence, the server does not maintain any
state information about this session and the client does not need to send any session termination request. Neither the
Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses.
6.4 Transport protocol
Diameter messages over the e4 interface shall make use of SCTP RFC 2960 [6] and shall utilize the new SCTP
checksum method specified in RFC 3309 [8].
ETSI
16 ETSI ES 283 034 V2.2.0 (2008-07)
6.5 Routing considerations
This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host.
Requests initiated by the CLF towards the RACS shall include both Destination-Host and Destination-Realm AVPs.
The CLF obtains the Destination-Host AVP to use in requests towards an A-RACF, from configuration data and/or the
NASS User profile. Consequently, the Destination-Host AVP is declared as mandatory in the ABNF for all requests
initiated by the CLF.
Requests initiated by the A-RACF towards the CLF shall include both Destination-Host and Destination-Realm AVPs.
The A-RACF obtains the Destinati
...

SLOVENSKI STANDARD
01-marec-2009
=OLWHWHOHNRPXQLNDFLMVNHLQLQWHUQHWQHVWRULWYHWHUSURWRNROL]DQDSUHGQRRPUHåHQMH
7,63$13RGVLVWHPRPUHåQHSULNOMXþLWYH1$669PHVQLNHQDSRGODJL
SURWRNROD',$0(7(5
Telecommunications and Internet converged Services and Protocols for Advanced
Networking (TISPAN) - Network Attachment Sub-System (NASS) - e4 interface based on
the DIAMETER protocol
Ta slovenski standard je istoveten z: ES 283 034 Version 2.2.0
ICS:
33.040.01 Telekomunikacijski sistemi Telecommunication systems
na splošno in general
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

ETSI ES 283 034 V2.2.0 (2008-07)
ETSI Standard
Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Network Attachment Sub-System (NASS);
e4 interface based on the DIAMETER protocol

2 ETSI ES 283 034 V2.2.0 (2008-07)

Reference
RES/TISPAN-03139-NGN-R2
Keywords
interface, network, system
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI ES 283 034 V2.2.0 (2008-07)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.6
2 References.6
2.1 Normative references.6
2.2 Informative references.7
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.7
4 Overview.8
5 Procedure descriptions .9
5.1 General.9
5.1.1 Information elements.9
5.1.2 NASS User profile.9
5.2 Procedures on the CLF - A-RACF interface .10
5.2.1 Access profile push.10
5.2.1.1 Overview.10
5.2.1.2 Procedure at the CLF side .11
5.2.1.3 Procedure at the A-RACF side.11
5.2.2 Access Profile Pull.12
5.2.2.1 Overview.12
5.2.2.2 Procedure at the A-RACF side.13
5.2.2.3 Procedure at the CLF side .13
5.2.3 IP connectivity release indication .14
5.2.3.1 Overview.14
5.2.3.2 Procedure at the CLF side .14
5.2.3.3 Procedure at the A-RACF side.15
6 Use of the Diameter base protocol .15
6.1 Securing Diameter messages.15
6.2 Accounting functionality.15
6.3 Use of sessions .15
6.4 Transport protocol.15
6.5 Routing considerations.16
6.6 Advertising application support .16
7 DIAMETER application.16
7.1 Commands.16
7.1.1 User-Data-Request command.17
7.1.2 User-Data-Answer command.17
7.1.3 Push-Notification-Request command.18
7.1.4 Push-Notification-Answer command.18
7.2 Result-Code AVP values.18
7.2.1 Success.19
7.2.2 Permanent failures.19
7.2.3 Transient failures.19
7.3 AVPs.19
7.3.1 Globally-Unique-Address AVP.21
7.3.2 Address-Realm AVP.21
7.3.3 Logical-Access-ID AVP.21
7.3.4 Initial-Gate-Setting-Description AVP.21
7.3.5 QoS-Profile-Description AVP.21
7.3.6 IP-Connectivity-Status AVP.22
7.3.7 Access-Network-Type AVP.22
ETSI
4 ETSI ES 283 034 V2.2.0 (2008-07)
7.3.8 Aggregation-Network-Type AVP.22
7.3.9 Maximum-Allowed-Bandwidth-UL AVP.22
7.3.10 Maximum-Allowed-Bandwidth-DL AVP.22
7.3.11 Reservation-Priority.22
7.3.12 Transport-Class.23
7.3.13 Application-Class-ID.23
7.3.14 Physical-Access-ID.23
7.3.15 NAS-Port-Type AVP.23
7.3.16 NAS-Filter-Rule AVP.23
7.3.17 Framed-IP-Address AVP.24
7.3.18 Framed-IP-Prefix AVP.24
7.3.19 Origin-Host AVP.24
7.3.20 AF-Application-Identifier AVP.24
7.3.21 Media-Type AVP.24
7.3.22 Initial-Gate-Setting-ID AVP.24
7.3.23 QoS-Profile-ID AVP.24
7.4 Use of namespaces .24
7.4.1 AVP codes.24
7.4.2 Experimental-Result-Code AVP values.24
7.4.3 Command Code values .24
7.4.4 Application-ID value.25
Annex A (informative): Mapping of e4 operations and terminology to Diameter.26
History .27

ETSI
5 ETSI ES 283 034 V2.2.0 (2008-07)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN).
ETSI
6 ETSI ES 283 034 V2.2.0 (2008-07)
1 Scope
The present document defines a protocol for use between the TISPAN NGN Network Attachment Sub-System (NASS)
and the Resource and Admission Control Subsystem (RACS), based on Diameter.
The present document is applicable to the e4 interface between the Connectivity Session Location and Repository
Function (CLF) and the RACS.
Whenever it is possible the present document specifies the requirements for this protocol by reference to specifications
produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined
within the present document.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ETSI ES 282 004: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment
Sub-System (NASS)".
[2] ETSI ES 282 003: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Resource and Admission Control Sub-system (RACS);
Functional Architecture".
[3] ETSI TS 129 229: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Cx and Dx interfaces based on the Diameter protocol;
Protocol details (3GPP TS 29.229)".
[4] ETSI TS 129 329: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Sh interface based on the Diameter protocol; Protocol
details (3GPP TS 29.329)".
ETSI
7 ETSI ES 283 034 V2.2.0 (2008-07)
[5] ETSI TS 129 209: "Universal Mobile Telecommunications System (UMTS); Policy control over
Gq interface (3GPP TS 29.209)".
[6] IETF RFC 2960: "Stream Control Transmission Protocol".
[7] IETF RFC 3588: "Diameter base protocol".
[8] IETF RFC 3309: "Stream Control Transmission Protocol (SCTP) Checksum Change".
[9] IETF RFC 4005: "Diameter Network Access Server application".
[10] IETF RFC 3554: "On the use of Stream Control Transmission Protocol (SCTP) with IPsec".
[11] IETF RFC 3046: "DHCP Relay Agent Information Option".
[12] ETSI TS 183 017: "Telecommunications and Internet Converged Services and Protocols for
Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER protocol for
session based policy set up information exchange between the Application Function (AF) and the
Service Policy Decision Function (SPDF); Protocol specification".
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
Not applicable.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Application Function (AF): element of the service layer architecture offering applications that require information
about the characteristics of the IP-connectivity session used to access such applications
Attribute-Value Pair (AVP): corresponds to an information element in a Diameter message
NOTE: See RFC 3588 [7].
NASS User: See definition in [1].
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ABNF Augmented Backus-Naur Form
AF Application Function
A-RACF Access-Resource and Admission Control Function
ATM Asynchronous Transfer Mode
AVP Attribute-Value Pair
CLF Connectivity session Location and repository Function
DHCP Dynamic Host Configuration Protocol
FQDN Fully Qualified Domain Name
IANA Internet Assigned Numbers Authority
ID IDentifier
IETF Internet Engineering Task Force
IPSec IP Security
NAS Network Access Server
ETSI
8 ETSI ES 283 034 V2.2.0 (2008-07)
NASS Network Attachment Sub-System
PDBF Profile Data Base Function
PNA Push-Notification-Answer
PNR Push-Notification-Request
QoS Quality of Service
RACF Resource and Admission Control Function
RACS Resource and Admission Control Subsystem
RCEF Resource Control Enforcement Function
RFC Request For Comments
SCTP Stream Control Transport Protocol
SPDF Service-based Policy Decision Function
UAAF User Authentication and Authorization Function
UDA User-Data-Answer
UDR User-Data-Request
VC Virtual Channel
VP Virtual Path
4 Overview
The Network Attachment Sub-System (NASS), defined in ES 282 004 [1], maintains information about IP-connectivity
associated with uNASS Users connected to TISPAN networks. This information is stored in the Connectivity session
Location and repository Function (CLF) and made accessible to other subsystems and applications through the
following two interfaces (see figure 1):
• The e2 interface enables Application Functions (AF) to retrieve IP-connectivity related session data.
• The e4 interface enables the IP-connectivity related session data to be exchanged between the NASS and the
Resource and Admission Control Subsystem (RACS) defined in ES 282 003 [2].
The present document specifies the protocol for the e4 interface.
Service Control
Subsystems and
Applications
AF
e2
CLF
NASS
e4
Scope of the present
A-RACF
document
RACS
Transfer Functions
Figure 1: NASS external interfaces
ETSI
9 ETSI ES 283 034 V2.2.0 (2008-07)
5 Procedure descriptions
5.1 General
5.1.1 Information elements
The following clauses describe the realization of the functional procedures defined in the NASS (ES 282 004) [1] and
RACS specifications (ES 282 003 [2]) using Diameter commands described in clause 7. This involves describing a
mapping between the information elements defined in the NASS specification (ES 282 004 [1]) and Diameter AVPs.
In the tables that describe this mapping, each information element is marked as (M) Mandatory, (C) Conditional or (O)
Optional:
• A mandatory information element (marked as (M) in tables 1 to 8) shall always be present in the command. If
this information element is absent, an application error occurs at the receiver and an answer message shall be
sent back to the originator of the request with the Result-Code set to DIAMETER_MISSING_AVP. This
message shall also include a Failed-AVP AVP containing the missing information element i.e. the
corresponding Diameter AVP defined by the AVP Code and the other fields set as expected for this
information element.
• A conditional information element (marked as (C) in tables 1 to 8) shall be present in the command if certain
conditions are fulfilled:
- If the receiver detects that those conditions are fulfilled and the information element is absent, an
application error occurs and an answer message shall be sent back to the originator of the request with
the Result-Code set to DIAMETER_MISSING_AVP. This message shall also include a Failed-AVP
AVP containing the missing information element i.e. the corresponding Diameter AVP defined by the
AVP Code and the other fields set as expected for this information element. If multiple information
elements are missing, all corresponding AVP codes shall be included in the Failed-AVP AVP.
- If those conditions are not fulfilled, the information element shall be absent. If however this information
element appears in the message, it shall not cause an application error and it may be ignored by the
receiver if this is not explicitly defined as an error case. Otherwise, an application error occurs at the
receiver and an answer message with the Result-Code set to DIAMETER_AVP_NOT_ALLOWED shall
be sent back to the originator of the request. A Failed-AVP AVP containing a copy of the corresponding
Diameter AVP shall be included in this message.
• An optional information element (marked as (O) in tables 1 to 8) may be present or absent in the command, at
the discretion of the application at the sending entity. Absence or presence of this information element shall
not cause an application error and may be ignored by the receiver.
5.1.2 NASS User profile
NASS User profile information sent over the e4 interface comprises QoS profile information and initial gate setting
information. Each of these pieces of information may be sent in the form of an identifier using the QoS-Profile-ID and
Initial-Gate-Setting-ID AVPs or in the form of an explicit description using the QoS-Profile-Description and Initial-
Gate-Setting-Description AVPs.
Tables 1 and 2 detail the information elements involved in the second case as defined in the NASS specification
ES 282 004 [1] and their mapping to DIAMETER AVPs.
ETSI
10 ETSI ES 283 034 V2.2.0 (2008-07)
Table 1: Initial gate setting description
Information Mapping to Cat. Description
element name Diameter AVP
List of allowed NAS-Filter-Rule O In case of unicast data, the list of default destination IP addresses
destinations as ports, prefixes and port ranges to which traffic can be sent. In case of
well as multicast, the list of IP-Multicast group addresses and/or the list of
multicast flows (Source IP address, IP-Multicast group address) pairs which traffic can
be received from by the attached NASS User.
List of denied NAS-Filter-Rule O In case of unicast, the list of default destination IP addresses ports,
destinations as prefixes and port ranges to which traffic is denied. In case of multicast,
well as the list of IP-Multicast group addresses and/or the list of (Source IP
multicast flows address, IP-Multicast group address) pairs for which traffic towards the
attached NASS User must be denied.
UL Subscribed Maximum-Allowed- O The maximum amount of bandwidth that can be used without explicit
Bandwidth Bandwidth-UL authorization in the uplink direction.
DL Subscribed Maximum-Allowed- O The maximum amount of bandwidth that can be used without explicit
Bandwidth Bandwidth-DL authorization in the downlink direction.

Table 2: QoS profile description
Information Mapping to Cat. Description
element name Diameter AVP
Transport Transport-Class O The transport class applicable to the QoS Profile Information.
service class
Media-Type Media-Type O The media type applicable to the QoS Profile information.
UL Subscribed Maximum-Allowed- O The maximum amount of bandwidth subscribed by the attached NASS
Bandwidth Bandwidth-UL User in the uplink direction.
DL Subscribed Maximum-Allowed- O The maximum amount of bandwidth subscribed by the attached NASS
Bandwidth Bandwidth-DL User in the downlink direction.
Maximum Reservation-Priority O The maximum priority allowed for any reservation request.
Priority
Requestor Application Class ID O Identifies the application class(es) that are allowed to request
Name resources for the QoS profile.

5.2 Procedures on the CLF - A-RACF interface
5.2.1 Access profile push
5.2.1.1 Overview
This procedure is used to push session-related information from the CLF to the A-RACF. This information flow occurs
when an IP address has been allocated to a NASS User or in case a modification occurs on a profile that has already
been pushed to the RACS.
The CLF should push session-related-information to the A-RACF as soon as it is available to the CLF. This may require
the CLF to pull part of the information from other components of the NASS.
For the same NASS User, the CLF may push several independent session records with different IP addresses, with or
without the same logical access identifier.
This procedure is mapped to the commands Push-Notification-Request/Answer in the Diameter application specified in
clause 7. Tables 3 and 4 detail the involved information elements as defined in the NASS specification ES 282 004 [1]
and their mapping to Diameter AVPs.
ETSI
11 ETSI ES 283 034 V2.2.0 (2008-07)
Table 3: Access profile push
Information Mapping to Diameter Cat. Description
element name AVP
Globally Unique Globally-Unique-Address M This information element contains:
IP Address - The IP address of the NASS User for which profile
information is being pushed.
- The addressing domain in which the IP address is
significant.
Logical Access Logical-Access-Id M The identity of the logical access to which the user equipment is
ID connected.
Access Access-Network-Type O The type of access network over which IP connectivity is provided
Network Type to the user equipment.
NASS User ID User-Name C The NASS User that is attached to the network (see note).
Physical Physical-Access-Id O The identity of the physical access to which the user equipment is
Access ID connected.
Initial Gate Initial-Gate-Setting or O See clause 5.1, table 1.
Setting Initial-Gate-Setting-ID
QoS Profile QoS-Profile or QoS- O See clause 5.1, table 2.
Profile-ID
NOTE: The NASS User ID shall be included if available in the CLF.

Table 4: Access profile push response
Information Mapping to Diameter AVP Cat. Description
element name
Result Result-Code / Experimental_ M Result of the request.
Result Result-Code AVP shall be used for errors defined in the
Diameter base protocol.
Experimental-Result AVP shall be used for other errors. This
is a grouped AVP which contains a Vendor-Id AVP, and the
error code in the Experimental-Result-Code AVP.

5.2.1.2 Procedure at the CLF side
The CLF knows the address of the A-RACF entity where the information should be pushed, either from configuration
data or from the NASS User profile (i.e. received from the UAAF/PDBF).
The CLF shall populate the Access Profile Push as follows:
• The Globally-Unique-Address AVP shall contain a Frame-IP-Address or Frame-IPv6-Prefix AVP value, and
an Address-Realm AVP.
• The Logical-Access-ID AVP shall be present.
The presence of the other AVPs depends on the NASS User profile and local policy rules.
5.2.1.3 Procedure at the A-RACF side
If the Logical Access ID is not included or is invalid, the A-RACF shall return an Access Profile Push response with a
Result-Code AVP value set to DIAMETER_INVALID_AVP_VALUE.
If the globally unique identifier contained in the Globally-Unique-Address AVP is not known, the A-RACF shall:
• Create an internal record to store the received information for future use (i.e. for processing resource
reservation requests received from the SPDF).
• Derive the following information from the Logical Access ID:
- The identification and bandwidth capacity of the layer 2 resources over which the NASS user traffic is to
be carried.
- The address of the transport network node(s) implementing an RCEF.
ETSI
12 ETSI ES 283 034 V2.2.0 (2008-07)
• If the received information contains an Initial-Gate-Setting-Description or Initial-Gate-Setting-ID AVP,
perform any appropriate actions to enforce the policy information. This involves interacting with one or more
RCEFs through the Re interface.
If the globally unique identifier contained in the Globally-Unique-Address AVP is already known, the A-RACF shall:
• Replace the entire content of the internal record with the received information for future use.
• If the received information contains an Initial-Gate-Setting-Description or Initial-Gate-Setting-ID, perform any
appropriate actions to enforce the new policy information. This may involve interacting with the RCEF
through the Re interface.
When an Initial-Gate-Setting-ID is received, the A-RACF shall derive a set of associated traffic filter rules before
interacting with an RCEF or a subordinated x-RACF. If the value of the Initial-Gate-Setting-ID is unknown, the A-
RACF shall return an Access Profile Push response with a Result-Code AVP value set to
DIAMETER_INVALID_AVP_VALUE.
Such an update shall not have any impact on ongoing application sessions for which an authorization has already been
provided by the A-RACF.
If the contents of the request are invalid the A-RACF shall return an Access Profile Push response with a Result-Code
AVP value set to the appropriate value as described in clause 5.1.
If the creation or modification of the session record is successful but a failure occurs during the processing of the Initial
Gate Settings (e.g. due to a failure in the interaction with the RCEF), the A-RACF shall return an Access Profile Push
response with a Result-Code AVP value set to DIAMETER_LIMITED_SUCCESS.
If the A-RACF cannot fulfil the received request for reasons not stated in the above steps, e.g. due to database error, it
shall stop processing the request and return an Access Profile Push response with a Result-Code AVP value set to
DIAMETER_UNABLE_TO_COMPLY or an Experimental-Result-Code AVP set to
DIAMETER_SYSTEM_UNAVAILABLE. In the later case, the CLF is expected to retry after a provisioned time
period.
Otherwise, the requested operation shall take place and the A-RACF shall return the Result-Code AVP set to
DIAMETER_SUCCESS in the Access Profile Push response.
5.2.2 Access Profile Pull
5.2.2.1 Overview
This procedure is used by the RACS to request the Access Profile information from the CLF, in the context of recovery
procedures.
This procedure is mapped to the commands User-Data-Request/Answer in the Diameter application specified in
clause 7. Tables 5 and 6 detail the involved information elements as defined in the NASS specification ES 282 004 [1]
and their mapping to Diameter AVPs.
Table 5: Access Profile Pull request
Information Mapping to Cat. Description
element name Diameter AVP
Globally unique Globally-Unique- C This information element contains:
IP Address Address - The IP address of the NASS User for which profile information
is being pushed.
- The addressing domain in which the IP address is significant.
NASS User ID User-Name C The NASS User that is attached to the network.
RACS-Id AF-Application- M Identifies the A-RACF function requesting profile information.
Identifier
ETSI
13 ETSI ES 283 034 V2.2.0 (2008-07)
Table 6: Access Profile Pull response
Information Mapping to Diameter Cat. Description
element name AVP
Globally unique Globally-Unique- C This information element contains:
IP Address Address - The IP address of the NASS User for which profile
information is being pushed.
- The addressing domain in which the IP address is
significant.
Logical Access Logical-Access-Id M The identity of the logical access to which the user equipment is
ID connected.
Access Access-Network-Type O The type of access network over which IP connectivity is provided to
Network Type the user equipment.
NASS User ID User-Name C The identity of the NASS User that is attached to the network.
Physical Physical-Access-Id O The identity of the physical access to which the user equipment is
Access ID connected.
Initial Gate Initial-Gate-Setting- O See clause 5.1
Settings Description or Initial-
Gate-Setting-ID
QoS Profile QoS-Profile- O See clause 5.1
Description or Initial-
QoS-Profile-ID
5.2.2.2 Procedure at the A-RACF side
The A-RACF may use this procedure after a restart, upon reception of the resource reservation request associated with
an IP-Address for which no record is stored.
The A-RACF shall populate the Access Profile Pull request as follows:
1) The User-Name AVP or the Globally-Unique-Address AVP shall be included. The Globally-Unique-Address
AVP shall be included in configurations where more than one IP address may be assigned per NASS User ID .
2) If present, the Globally-Unique-Address AVP shall contain a Frame-IP-Address or Frame-IPv6-Prefix AVP
value, and an Address-Realm AVP. The Address-Realm AVP shall be included and set either using
configuration data (in which case all terminal equipment served by the A-RACF belong to the same addressing
domain) or from the physical or logical interface over which was received the resource request that triggered
the pull procedure.
3) The AF-Application-Identifier AVP shall be present and set to the A-RACF Identity.
5.2.2.3 Procedure at the CLF side
Upon reception of the Access Profile Pull request, the CLF shall, in the following order:
1) If the Globally-Unique-Address AVP is present, use this information as a key to retrieve the requested session
information.
2) If the Globally-Unique-Address AVP is absent but the User-Name AVP is present, use the latter information
as a key to retrieve the requested session information.
3) If both the Globally-Unique-Address AVP and the User-Name AVP are absent, return an Access Pull Profile
response with Result-Code set to DIAMETER_MISSING_AVP.
4) If more than one record include the same NASS User ID matching the value of the User-Name AVP and no
Globally-Unique-Address AVP is included, return an Access Pull Profile response with Result-Code set to
DIAMETER_UNABLE_TO_COMPLY.
5) If no session record is stored for the Globally-Unique-Address AVP or the User-Name AVP, return an Access
Pull Profile with the Experimental-Result-Code AVP shall be set to
DIAMETER_ERROR_USER_UNKNOWN.
ETSI
14 ETSI ES 283 034 V2.2.0 (2008-07)
If a unique NASS User record car be retrieved, the CLF shall:
1) Check which session data can be returned to the A-RACF, based on local policy rules and per-NASS User
privacy information stored in the CLF.
2) Check whether the session data to be retrieved is currently being updated by another entity. If there is an
update of the data in progress, the CLF may delay the response message until the update has been completed
and shall include in the response message the updated data requested. The CLF shall ensure that the data
returned is not corrupted by this conflict.
If the CLF cannot fulfil the received request for reasons not stated in the above steps, e.g. due to database error, it shall
stop processing the request and set Result-Code to DIAMETER_UNABLE_TO_COMPLY or an
Experimental-Result-Code AVP set to DIAMETER_USER_DATA_NOT_AVAILABLE.
Otherwise, the requested operation shall take place and the CLF shall return the Result-Code AVP set to
DIAMETER_SUCCESS and the session data in the Access Profile Pull response.
5.2.3 IP connectivity release indication
5.2.3.1 Overview
This procedure is used by the CLF to report loss of IP connectivity. This enables the RACS to remove the access profile
from its internal data base. This event occurs in case the allocated IP address is released (e.g. DHCP leased timer
expiry) or due to a release of the underlying layer 2 resources.
This procedure is mapped to the commands Push-Notification-Request/Answer in the Diameter application specified in
clause 7. Tables 7 and 8 detail the involved information elements as defined in the NASS specification ES 282 004 [1]
and their mapping to Diameter AVPs.
Table 7: IP connectivity release indication
Information Mapping to Cat. Description
element name Diameter AVP
Globally unique Globally-Unique- M This information element contains:
IP Address Address - The IP address of the NASS User for which profile information
is being pushed.
- The addressing domain in which the IP address is significant.
NASS User ID User-Name O The identity of the NASS User that is attached to the network.
IP-Connectivity IP-Connectivity- M Whether IP connectivity to/from the NASS Usert is currently available.
Status Status
Table 8: IP connectivity release indication response
Information Mapping to Cat. Description
element name Diameter AVP
Result Result-Code / M Result of the request.
Experimental_ Result-Code AVP shall be used for errors defined in the Diameter base
Result protocol.
Experimental-Result AVP shall be used for other errors. This is a grouped
AVP which contains a Vendor-Id AVP, and the error code in the
Experimental-Result-Code AVP.
5.2.3.2 Procedure at the CLF side
On receipt of an external event indicating that the allocated IP address has been released or the underlying layer 2
connection has been lost, the CLF shall clear all information stored against the IP address and issue a
Push-Notification-Request representing an IP-Connectivity-Release-Indication with the IP-Connectivity-Status AVP set
to the value IP-CONNECTIVITY-LOST.
NOTE: Receipt of an indication that a layer 2 connection has been lost may lead the CLF to issue several
notifications, in case multiple access sessions where associated with this connection.
ETSI
15 ETSI ES 283 034 V2.2.0 (2008-07)
5.2.3.3 Procedure at the A-RACF side
If the globally unique identifier contained in the Globally-Unique-Address AVP is not known, the A-RACF shall stop
processing the request and set the Experimental-Result-Code to DIAMETER_ERROR_USER_UNKNOWN in the IP
Connectivity Release Indication Response.
If the globally unique identifier contained in the Globally-Unique-Address AVP is already known, the A-RACF shall:
• remove the existing session record;
• interact with transfer layer entities (i.e. RCEF) to remove transport policies associated with the session and
clear associated resources;
• notify the SPDF.
If the A-RACF cannot fulfil the received request for reasons not stated in the above steps, e.g. due to database error, it
shall stop processing the request and set Result-Code to DIAMETER_UNABLE_TO_COMPLY or an
Experimental-Result-Code set to DIAMETER_SYSTEM_UNAVAILABLE. In the later case, the CLF is expected to
retry after a provisioned time period.
Otherwise, the requested operation shall take place and the A-RACF shall return an IP-Connectivity-Release-Indication
response with the Result-Code AVP set to DIAMETER_SUCCESS.
6 Use of the Diameter base protocol
With the clarifications listed in the following clauses the Diameter base protocol defined by RFC 3588 [7] shall apply.
6.1 Securing Diameter messages
For secure transport of Diameter messages, IPSec may be used. Guidelines on the use of SCTP with IPSec can be found
in RFC 3554 [10].
6.2 Accounting functionality
Accounting functionality (accounting session state machine, related command codes and AVPs) is not used on the e4
interface.
6.3 Use of sessions
Diameter sessions are implicitly terminated. An implicitly terminated session is one for which the server does not
maintain state information. The client does not need to send any re-authorization or session termination requests to the
server.
The Diameter base protocol includes the A
...