SIST ES 283 035 V2.5.1:2009

ETSI Standard
Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Network Attachment Sub-System (NASS);
e2 interface based on the DIAMETER protocol

2 ETSI ES 283 035 V2.5.1 (2008-08)

Reference
RES/TISPAN-03116-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 035 V2.5.1 (2008-08)
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.8
4 Overview.8
5 Procedure descriptions .9
5.1 General.9
5.2 Procedures on the CLF - AF interface.10
5.2.1 Information query.10
5.2.1.1 Overview.10
5.2.1.2 Procedure at the AF side .11
5.2.1.3 Procedure at the CLF side .11
5.2.2 Event Registration/Deregistration.12
5.2.2.1 Overview.12
5.2.2.2 Procedure at the AF side .13
5.2.2.3 Procedure at the CLF side .13
5.2.3 Notification Events .14
5.2.3.1 Overview.14
5.2.3.2 Procedure at the CLF side .15
5.2.3.3 Procedure at the AF side .15
6 Use of the Diameter base protocol .16
6.1 Securing Diameter messages.16
6.2 Accounting functionality.16
6.3 Use of sessions .16
6.4 Transport protocol.16
6.5 Routing considerations.16
6.6 Advertising application support .17
7 DIAMETER application.17
7.1 Commands.17
7.1.1 User-Data-Request command.18
7.1.2 User-Data-Answer command.18
7.1.3 Subscribe-Notifications-Request (SNR) Command .19
7.1.4 Subscribe-Notifications-Answer (SNA) Command.19
7.1.5 Push-Notification-Request (PNR) Command.19
7.1.6 Push-Notifications-Answer (PNA) Command.20
7.2 Result-Code AVP values.20
7.2.1 Success.20
7.2.2 Permanent failures.21
7.2.3 Transient failures.21
7.3 AVPs.21
7.3.1 Location-Information AVP.22
7.3.1A Civic-Location AVP.22
7.3.1B Geospatial-Location AVP.23
7.3.2 RACS-Contact-Point AVP.23
7.3.3 Terminal-Type AVP.23
7.3.4 Requested-Information AVP.23
7.3.5 Line-Identifier AVP.23
ETSI
4 ETSI ES 283 035 V2.5.1 (2008-08)
7.3.6 Event-Type AVP.24
7.4 Use of namespaces .24
7.4.1 AVP codes.24
7.4.2 Experimental-Result-Code AVP values.25
7.4.3 Command Code values .25
7.4.4 Application-ID value.25
Annex A (informative): Mapping of e2 operations and terminology to Diameter.26
Annex B (informative): Change history .27
History .28

ETSI
5 ETSI ES 283 035 V2.5.1 (2008-08)
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 035 V2.5.1 (2008-08)
1 Scope
The present document defines a protocol for use between the TISPAN NGN Network Attachment Sub-System (NASS)
and service control subsystems or applications of the TISPAN NGN architecture, based on Diameter.
The present document is applicable to the e2 interface between the Connectivity session Location and repository
Function (CLF) and an Application Function (AF).
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 001: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Functional Architecture Release 2".
[2] ETSI ES 282 004: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment
Sub-System (NASS)".
[3] ETSI ES 282 003: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Resource and Admission Control Sub-System (RACS);
Functional Architecture".
[4] ETSI ES 282 007: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture".
ETSI
7 ETSI ES 283 035 V2.5.1 (2008-08)
[5] ETSI ES 283 034: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Network Attachment Sub-System (NASS); e4 interface based
on the DIAMETER protocol".
[6] 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)".
[7] 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)".
[8] ETSI TS 129 209: "Universal Mobile Telecommunications System (UMTS); Policy control over
Gq interface (3GPP TS 29.209)".
[9] IETF RFC 2960: "Stream Control Transmission Protocol".
[10] IETF RFC 3588: "Diameter Base Protocol".
[11] IETF RFC 3309: "Stream Control Transmission Protocol (SCTP) Checksum Change".
[12] IETF RFC 3554: "On the use of Stream Control Transmission Protocol (SCTP) with IPSec".
[13] ETSI TS 182 008: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Presence Service; Architecture and functional description
(Endorsement of 3GPP TS 23.141 and OMA-AD-Presence-SIMPLE-V1-0)".
[14] Void.
[15] IETF RFC 4776: "Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for
Civic Addresses Configuration Information" .
[16] IETF RFC 3825: "Dynamic Host Configuration Protocol Option for Coordinate-based Location
Configuration Information".
[17] IETF RFC 4234: "Augmented BNF for Syntax Specifications: ABNF".
[18] ITU-T Recommendation M.1400: "Designations for interconnections among operators' networks".
[19] ISO 3166-1: "Codes for the representation of names of countries and their subdivisions - Part 1:
Country codes".
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:
access record: the set of information stored in the CLF in relation to an IP address
Application Function (AF): element of the network architecture offering - or providing access to - applications that
require information about the characteristics of the IP-connectivity session used to access such applications
ETSI
8 ETSI ES 283 035 V2.5.1 (2008-08)
Attribute-Value Pair (AVP): corresponds to an Information Element in a Diameter message
NOTE: See RFC 3588 [10].
NASS User: See definition in [2].
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
ASF Application Server Function
AVP Attribute-Value Pair
CLF Connectivity session Location and repository Function
CSCF Call Session Control Function
DHCP Dynamic Host Configuration Protocol
IANA Internet Assigned Numbers Authority
IBCF Interconnection Border Control Function
ICC ITU Carrier Code
IETF Internet Engineering Task Force
IMS IP Multimedia Subsystem
IP Internet Protocol
LAC Location-Area-Code
LCI Location Configuration Information
NASS Network Attachment Sub-System
NOC Network-Operator-Code
P-CSCF Proxy Call Session Control Function
PDBF Profile Data Base Function
PNA Presence Network Agent
PNR Push-Notification-Request
RACF Resource and Admission Control Function
RACS Resource and Admission Control Subsystem
RFC Request For Comments
SCTP Stream Control Transport Protocol
SNA Subscribe-Notifications-Answer
SNR Subscribe-Notifications-Request
SPDF Service-based Policy Decision Function
UAAF User Authentication and Authorization Function
UDA User-Data-Answer
UDR User-Data-Request
4 Overview
The Network Attachment Sub-System (NASS) defined in ES 282 004 [2] maintains information about IP-connectivity
access sessions associated with NASS Users connected to the TISPAN network. This information is stored in the
Connectivity session Location and repository Function (CLF) in the form of access records 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 [3].
The present document specifies the protocol for the e2 interface.
ETSI
9 ETSI ES 283 035 V2.5.1 (2008-08)
In the context of the present document, an Application Function (AF) is a generic term representing any element of the
network architecture offering - or providing access to - applications that require information about the characteristics of
the IP-connectivity session used to access such applications. Examples of such Application Functions are the P-CSCF
and the IBCF in the IMS (ES 282 007 [4]), certain categories of Application Server Functions (ASF) (ES 282 001 [1])
or a Presence Network Agent (PNA) as defined in TS 182 008 [13]. In the later case, the Pn reference point of the
presence architecture is mapped to the e2 interface.
Scope of the present
document
Service Control
Subsystems and
Applications
AF
e2
CLF
NASS
e4
A-RACF
RACS
Transfer Functions
Figure 1: NASS external interfaces
5 Procedure descriptions
5.1 General
The following clauses describe the realization of the functional procedures defined in the NASS (ES 282 004 [2]) and
RACS specifications (ES 282 003 [3]) using Diameter commands described in clause 7. This involves describing a
mapping between the Information Elements defined in the NASS specification (ES 282 004 [2]) 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 the table) 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 and 2) 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.
ETSI
10 ETSI ES 283 035 V2.5.1 (2008-08)
- 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 and 2) 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.2 Procedures on the CLF - AF interface
5.2.1 Information query
5.2.1.1 Overview
This procedure is used by an AF to retrieve from the CLF location information and other data related to an access
session.
This procedure is mapped to the commands User-Data-Request/Answer in the Diameter application specified in
TS 129 329 [7].
Tables 1 and 2 detail the involved information elements as defined in the NASS specification ES 282 004 [2] and their
mapping to Diameter AVPs.
Table 1: Information query request
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.
NASS User ID User-Name C The identity of the NASS User that is attached to the network.
AF Identity AF-Application-Identifier M Identifies the AF originating the request.
Requested-Items Requested-Information O The list of items requested by the AF.
NOTE: Either the Globally-Unique-IP-Address or the NASS User ID shall be included.

ETSI
11 ETSI ES 283 035 V2.5.1 (2008-08)
Table 2: Information query response
Information Mapping to diameter Cat. Description
element name AVP
Result Result-Code / M Result of the request.
Experimental_
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 the 3GPP Vendor ID in the Vendor-Id
AVP, and the error code in the Experimental-Result-Code AVP.
NASS User ID User-Name O The identity of the NASS User that is attached to the network.
Location Location-Information O Location information (or a pointer to such information) in a form that
Information is suitable for the requesting application.
RACS contact RACS-Contact- O The FQDN or IP address of the RACS entity where resource request
point Point shall be sent (i.e. SPDF address).
Access Network Access-Network- O The type of access network over which IP connectivity is provided to
Type Type the user equipment.
Terminal Type Terminal-Type O The type of user equipment to which the IP address was allocated.
Logical Access ID Logical-Access-Id O The identity of the logical access where the user equipment is
connected.
Physical Access ID Physical-Access-Id O The identity of the physical access where the user equipment is
connected.
5.2.1.2 Procedure at the AF side
The AF shall populate the Information Query as follows:
1) Insert either a Globally-Unique-Address or a User-Name AVP. 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 AF 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.
2) The AF-Application-Identifier AVP shall be present.
3) The Requested-Information AVP shall be present if specific information is requested and shall be absent if all
available information is requested.
5.2.1.3 Procedure at the CLF side
Upon reception of the Information Query, 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 Information Query
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 Information Query 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
Information Query with the Experimental-Result-Code AVP shall be set to
DIAMETER_ERROR_USER_UNKNOWN.
ETSI
12 ETSI ES 283 035 V2.5.1 (2008-08)
If a unique NASS user record can be retrieved, the CLF shall:
1) Check which session data can be returned to the AF, based on the contents of the Requested-Information AVP,
local policy rules and per-NASS user privacy information previously received from the UAAF/PDBF and
stored in the CLF.
NOTE 1: If the Requested-Information AVP is not received, the list of requested information is inferred from the
AF identity.
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.
Under temporary overload conditions, the CLF shall stop processing the request and return an Information Query
response with the Result-Code set to DIAMETER_TOO_BUSY. The AF may retry retrieving the required information
at a later stage.
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 the 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 Information Query response.
NOTE 2: Due to the application of operator's policies and NASS User privacy rules, the session data returned in the
message may be a subset of the explicitly or implicitly requested session data.
5.2.2 Event Registration/Deregistration
5.2.2.1 Overview
This procedure is used by an AF to subscribe with the CLF to a particular event.
This procedure is mapped to the commands Subscribe-Notifications-Request/Answer defined in the Diameter
application specified in TS 129 329 [7].
Tables 2a and 2b detail the involved information elements as identified in the NASS specification ES 282 004 [2] and
their mapping to Diameter AVPs.
Table 2a: Event Registration/Deregistration Request
Information Mapping to Diameter Cat. Description
element name AVP
Subs-Req-Type M Indicates whether the AF is willing to subscribe or unsubscribe to the
notification of the event.
NASS User ID User-Name C The identity of the NASS User on behalf of which the event is to be
reported.
Globally unique Globally Unique C This information element contains the IP address of the NASS User
IP Address Address on behalf of which the event is to be reported, together with the
addressing domain in which the IP address is significant.
Subscription Expiry-Time O Moment of expiration of the subscription to the event.
Expiration
Event Event-Type M The type of event to be monitored.
AF Identity AF-Application-Identifier M Identifies the AF originating the request.

ETSI
13 ETSI ES 283 035 V2.5.1 (2008-08)
Table 2b: Event Registration/Deregistration Response
Information Mapping to Cat. Description
element name Diameter AVP
Result Result-Code / M Result of the request.
Experimental_
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 the 3GPP Vendor ID in the Vendor-Id
AVP, and the error code in the Experimental-Result-Code AVP.
Expiry-Time O Acknowledges the absolute time at which the subscription expires.

The CLF monitors events related to access sessions. Monitoring of a particular event on a particular session is activated
when at least one Application Function has subscribed to be notified of the occurrence of the event.
Subscription to an event may be done implicitly (i.e. through management operations) or explicitly using the Event
Registration/Deregistration request. Subscription to an event ceases when one of the following conditions is met:
• Expiry of the subscription duration.
• Removal of the session record from the CLF.
• Receipt of an explicit request to unsubscribe.
5.2.2.2 Procedure at the AF side
The AF shall populate the Event Registration/Deregistration Request as follows:
Insert a Subs-Req-Type AVP indicating whether it is willing to subscribe or unsubscribe to the notification of events.
1) Insert either a Globally-Unique-Address or a User-Name AVP. 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 NASS Users
served by the AF is assumed to belong to the same addressing domain) or from the physical or logical interface
over which was received a related service request.
2) The AF-Application-Identifier AVP shall be present.
3) At least one occurrence of the Event-Type AVP shall be present.
4) The Expiry-Time AVP may be present.
5.2.2.3 Procedure at the CLF side
Upon reception of an Event Registration/Deregistration Request, the CLF shall, in the following order:
1) Based on the contents of the AF-Application-Identifier AVP, check whether the AF is allowed to request
monitoring of events. If not, return an Event Registration Response with Result-Code set to
DIAMETER_ERROR_OPERATION_NOT_ALLOWED.
2) If the Globally-Unique-Address AVP is present, use this information as a key to identify the session for which
event monitoring is being requested.
3) If the Globally-Unique-Address AVP is absent but the User-Name AVP is present, use the latter information as
a key to the session(s) for which event monitoring is being requested.
4) If both the Globally-Unique-Address AVP and the User-Name AVP are absent, return an Event
Registration/Deregistration Response with the Result-Code AVP set to DIAMETER_MISSING_AVP.
5) If no stored session record matches the Globally-Unique-Address AVP or the User-Name AVP and the
requested Event differs from USER-LOGON, return an Event Registration Response with the
Experimental-Result-Code AVP set to DIAMETER_ERROR_USER_UNKNOWN.
ETSI
14 ETSI ES 283 035 V2.5.1 (2008-08)
If the Subs-Req-Type AVP indicates that this is a request to subscribe to the notification of events, the CLF shall check
whether the requested event can be reported to the AF, based on local policy rules and per-NASS User privacy
information received from the UAAF. If the AF is not allowed to request monitoring of the event, return an Event
Registration/Deregistration Response with Result-Code set to
DIAMETER_ERROR_OPERATION_NOT_ALLOWED. If the AF is allowed to request monitoring of the event, the
CLF shall:
6) For all session records matching the request, associate the AF-Application-Identifier with the list of entities that
need to be notified when the event identified by the request occurs. The association lasts until the moment
indicated by the value of the Expiry-Time AVP as returned to the AF. If no Expiry-Time AVP is supplied, the
CLF should treat it as a request for an unlimited subscription.
7) Include in the Event Registration Response an Expiry Time AVP with the absolute time at which the
subscription expires in the case of a successful subscription. This time may be earlier than the requested expiry
time. If the CLF includes this AVP, then no notification shall be sent to the AF after the expiration time. If the
CLF does not include this AVP, that indicates an unlimited subscription.
8) Set the Result-Code to DIAMETER_SUCCESS and return an Event Registration/Deregistration Response.
If the Subs-Req-Type AVP indicates that this is a request to unsubscribe to the notification of events, the CLF shall
remove the association of the AF-Identifier with the same list. The Result-Code shall be set to DIAMETER_SUCCESS
if the operation is successful or if the AF-Identifier was not present in the list. If the Event-Type AVP is absent, the
CLF assumes that the AF is willing to unsubscribe to all events associated with the
User-Name or Globally-Unique-Address AVP.
If a subsequent request is received by the CLF where the Expiry Time AVP is present but different from what the CLF
has previously stored, the CLF should replace the stored expiration time with what was received in the request.
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 the Result-Code to DIAMETER_UNABLE_TO_COMPLY.
5.2.3 Notification Events
5.2.3.1 Overview
This procedure is used by a CLF to notify the AF of the occurrence of a particular event.
This procedure is mapped to the commands Push-Notifications-Request/Answer in the Diameter application specified in
TS 129 329 [7].
Tables 2c and 2d detail the involved information elements as defined in the NASS specification ES 282 004 [2] and
their mapping to Diameter AVPs.
Table 2c: Notification Event Request
Information Mapping to Diameter Cat. Description
element name AVP
NASS User ID User-Name C The identity of the NASS User on behalf of which the event is to be
reported.
Globally unique Globally Unique C This information element contains:
IP Address Address - The IP address of the NASS User on behalf of which the event is
to be reported.
- The addressing domain in which the IP address is significant.
AF Identity AF-Application-Identifier M Identifies the AF having registered to the request.
Event Event-Type M The type of event to be monitored.
[AVP] O AVPs carrying CLF information associated to the reported event.

ETSI
15 ETSI ES 283 035 V2.5.1 (2008-08)
Table 2d: Notification Event 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 the 3GPP Vendor ID in the Vendor-Id
AVP, and the error code in the Experimental-Result-Code AVP.

5.2.3.2 Procedure at the CLF side
When a monitored event is detected on a particular access session, the CLF issues a Notification Event Request to each
of the application functions having registered to this event.
The Notification Event Request is populated as follows:
1) A least a Globally-Unique-Address or a User-Name AVP shall be included. 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 AF belong to the same addressing domain) or from the physical or logical interface
over which was received a related service request.
2) The AF-Application-Identifier AVP shall be present.
3) One or more occurrence of the Event-Type AVP indicating the type of events being notified.
Based on local policy rules and per-NASS User privacy information previously received from the UAAF, the CLF may
also include additional information in the Event Registration/Deregistration Request. Table 2e provides an indication of
the AVPs that may be returned for each event.
Table 2e: Request-Information to AVP mapping
Event AVP
USER-LOGON IP-Connectivity-Status
LOCATION-INFORMATION-CHANGED Location-Information
RACS-CONTACT-POINT-CHANGED RACS-Contact-Point
ACCESS-NETWORK-TYPE -CHANGED Access-Network-Type
TERMINAL-TYPE -CHANGED Terminal-Type
LOGICAL-ACCESS-ID-CHANGED Logical-Access-Id
PHYSICAL-ACCESS-ID-CHANGED Physical Access-Id
INITIAL-GATE-SETTING-CHANGED Initial-Gate-Setting
QOS-PROFILE-CHANGED. QoS-Profile
IP-ADDRESS-CHANGED Globally-Unique-Address
USER-LOGOFF IP-Connectivity-Status

5.2.3.3 Procedure at the AF side
Upon reception of a Notification Event Request, the AF shall:
1) If neither the globally unique identifier contained in the Globally-Unique-Address AVP nor the NASS User ID
contained in the User-Name AVP are known, return a Notification Event Response with a Result-Code AVP
value set to DIAMETER_ERROR_USER_UNKNOWN.
2) If the event type contained in the Event-Type AVP is not known, return a Notification Event Response with a
Result-Code AVP value set to DIAMETER_INVALID_AVP_VALUE.
3) If the event type contained in the Event-Type AVP is known but was not expected, return a Notification Event
Response with a Result-Code AVP value set to DIAMETER_ERROR_NO_SUBSCRIPTION_TO_DATA.
ETSI
16 ETSI ES 283 035 V2.5.1 (2008-08)
If the AF cannot process the event for reasons not stated in the above steps return a Notification Event 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. After a provisioned number of unsuccessful retries, the CLF is expected to delete the AF-Identity from the list of
application functions registered to the event.
Otherwise, the event shall be processed and the AF shall return the Result-Code AVP set to DIAMETER_SUCCESS in
the Notification Event Response.
6 Use of the Diameter base protocol
With the clarifications listed in the following clauses the Diameter Base Protocol defined by RFC 3588 [10] 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 [12].
6.2 Accounting functionality
Accounting functionality (Accounting Session State Machine, related command codes and AVPs) is not used on the
e2 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 [10]. 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 e2 interface shall make use of SCTP RFC 2960 [9] and shall utilize the new SCTP
checksum method specified in RFC 3309 [11].
6.5 Routing considerations
This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host.
If an AF knows the address/name of the CLF for a certain NASS User/session, both the Destination-Realm and
Destination-Host AVPs shall be present in the request. Otherwise, only the Destination-Realm AVP shall be present and
the command shall be routed to a DIAMETER agent, based on the Diameter routing table in the client. The
DIAMETER Agent plays the role of the "CLF Proxy" described in clause 7.1 of ES 282 0004 [2]. The DIAMETER
agent shall act as a DIAMETER relay or proxy as described in RFC 3588 [10].
ETSI
17 ETSI ES 283 035 V
...

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) - e2 interface based on
the DIAMETER protocol
Ta slovenski standard je istoveten z: ES 283 035 Version 2.5.1
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 Standard
Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Network Attachment Sub-System (NASS);
e2 interface based on the DIAMETER protocol

2 ETSI ES 283 035 V2.5.1 (2008-08)

Reference
RES/TISPAN-03116-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 035 V2.5.1 (2008-08)
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.8
4 Overview.8
5 Procedure descriptions .9
5.1 General.9
5.2 Procedures on the CLF - AF interface.10
5.2.1 Information query.10
5.2.1.1 Overview.10
5.2.1.2 Procedure at the AF side .11
5.2.1.3 Procedure at the CLF side .11
5.2.2 Event Registration/Deregistration.12
5.2.2.1 Overview.12
5.2.2.2 Procedure at the AF side .13
5.2.2.3 Procedure at the CLF side .13
5.2.3 Notification Events .14
5.2.3.1 Overview.14
5.2.3.2 Procedure at the CLF side .15
5.2.3.3 Procedure at the AF side .15
6 Use of the Diameter base protocol .16
6.1 Securing Diameter messages.16
6.2 Accounting functionality.16
6.3 Use of sessions .16
6.4 Transport protocol.16
6.5 Routing considerations.16
6.6 Advertising application support .17
7 DIAMETER application.17
7.1 Commands.17
7.1.1 User-Data-Request command.18
7.1.2 User-Data-Answer command.18
7.1.3 Subscribe-Notifications-Request (SNR) Command .19
7.1.4 Subscribe-Notifications-Answer (SNA) Command.19
7.1.5 Push-Notification-Request (PNR) Command.19
7.1.6 Push-Notifications-Answer (PNA) Command.20
7.2 Result-Code AVP values.20
7.2.1 Success.20
7.2.2 Permanent failures.21
7.2.3 Transient failures.21
7.3 AVPs.21
7.3.1 Location-Information AVP.22
7.3.1A Civic-Location AVP.22
7.3.1B Geospatial-Location AVP.23
7.3.2 RACS-Contact-Point AVP.23
7.3.3 Terminal-Type AVP.23
7.3.4 Requested-Information AVP.23
7.3.5 Line-Identifier AVP.23
ETSI
4 ETSI ES 283 035 V2.5.1 (2008-08)
7.3.6 Event-Type AVP.24
7.4 Use of namespaces .24
7.4.1 AVP codes.24
7.4.2 Experimental-Result-Code AVP values.25
7.4.3 Command Code values .25
7.4.4 Application-ID value.25
Annex A (informative): Mapping of e2 operations and terminology to Diameter.26
Annex B (informative): Change history .27
History .28

ETSI
5 ETSI ES 283 035 V2.5.1 (2008-08)
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 035 V2.5.1 (2008-08)
1 Scope
The present document defines a protocol for use between the TISPAN NGN Network Attachment Sub-System (NASS)
and service control subsystems or applications of the TISPAN NGN architecture, based on Diameter.
The present document is applicable to the e2 interface between the Connectivity session Location and repository
Function (CLF) and an Application Function (AF).
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 001: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Functional Architecture Release 2".
[2] ETSI ES 282 004: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment
Sub-System (NASS)".
[3] ETSI ES 282 003: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Resource and Admission Control Sub-System (RACS);
Functional Architecture".
[4] ETSI ES 282 007: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture".
ETSI
7 ETSI ES 283 035 V2.5.1 (2008-08)
[5] ETSI ES 283 034: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Network Attachment Sub-System (NASS); e4 interface based
on the DIAMETER protocol".
[6] 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)".
[7] 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)".
[8] ETSI TS 129 209: "Universal Mobile Telecommunications System (UMTS); Policy control over
Gq interface (3GPP TS 29.209)".
[9] IETF RFC 2960: "Stream Control Transmission Protocol".
[10] IETF RFC 3588: "Diameter Base Protocol".
[11] IETF RFC 3309: "Stream Control Transmission Protocol (SCTP) Checksum Change".
[12] IETF RFC 3554: "On the use of Stream Control Transmission Protocol (SCTP) with IPSec".
[13] ETSI TS 182 008: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Presence Service; Architecture and functional description
(Endorsement of 3GPP TS 23.141 and OMA-AD-Presence-SIMPLE-V1-0)".
[14] Void.
[15] IETF RFC 4776: "Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for
Civic Addresses Configuration Information" .
[16] IETF RFC 3825: "Dynamic Host Configuration Protocol Option for Coordinate-based Location
Configuration Information".
[17] IETF RFC 4234: "Augmented BNF for Syntax Specifications: ABNF".
[18] ITU-T Recommendation M.1400: "Designations for interconnections among operators' networks".
[19] ISO 3166-1: "Codes for the representation of names of countries and their subdivisions - Part 1:
Country codes".
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:
access record: the set of information stored in the CLF in relation to an IP address
Application Function (AF): element of the network architecture offering - or providing access to - applications that
require information about the characteristics of the IP-connectivity session used to access such applications
ETSI
8 ETSI ES 283 035 V2.5.1 (2008-08)
Attribute-Value Pair (AVP): corresponds to an Information Element in a Diameter message
NOTE: See RFC 3588 [10].
NASS User: See definition in [2].
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
ASF Application Server Function
AVP Attribute-Value Pair
CLF Connectivity session Location and repository Function
CSCF Call Session Control Function
DHCP Dynamic Host Configuration Protocol
IANA Internet Assigned Numbers Authority
IBCF Interconnection Border Control Function
ICC ITU Carrier Code
IETF Internet Engineering Task Force
IMS IP Multimedia Subsystem
IP Internet Protocol
LAC Location-Area-Code
LCI Location Configuration Information
NASS Network Attachment Sub-System
NOC Network-Operator-Code
P-CSCF Proxy Call Session Control Function
PDBF Profile Data Base Function
PNA Presence Network Agent
PNR Push-Notification-Request
RACF Resource and Admission Control Function
RACS Resource and Admission Control Subsystem
RFC Request For Comments
SCTP Stream Control Transport Protocol
SNA Subscribe-Notifications-Answer
SNR Subscribe-Notifications-Request
SPDF Service-based Policy Decision Function
UAAF User Authentication and Authorization Function
UDA User-Data-Answer
UDR User-Data-Request
4 Overview
The Network Attachment Sub-System (NASS) defined in ES 282 004 [2] maintains information about IP-connectivity
access sessions associated with NASS Users connected to the TISPAN network. This information is stored in the
Connectivity session Location and repository Function (CLF) in the form of access records 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 [3].
The present document specifies the protocol for the e2 interface.
ETSI
9 ETSI ES 283 035 V2.5.1 (2008-08)
In the context of the present document, an Application Function (AF) is a generic term representing any element of the
network architecture offering - or providing access to - applications that require information about the characteristics of
the IP-connectivity session used to access such applications. Examples of such Application Functions are the P-CSCF
and the IBCF in the IMS (ES 282 007 [4]), certain categories of Application Server Functions (ASF) (ES 282 001 [1])
or a Presence Network Agent (PNA) as defined in TS 182 008 [13]. In the later case, the Pn reference point of the
presence architecture is mapped to the e2 interface.
Scope of the present
document
Service Control
Subsystems and
Applications
AF
e2
CLF
NASS
e4
A-RACF
RACS
Transfer Functions
Figure 1: NASS external interfaces
5 Procedure descriptions
5.1 General
The following clauses describe the realization of the functional procedures defined in the NASS (ES 282 004 [2]) and
RACS specifications (ES 282 003 [3]) using Diameter commands described in clause 7. This involves describing a
mapping between the Information Elements defined in the NASS specification (ES 282 004 [2]) 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 the table) 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 and 2) 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.
ETSI
10 ETSI ES 283 035 V2.5.1 (2008-08)
- 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 and 2) 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.2 Procedures on the CLF - AF interface
5.2.1 Information query
5.2.1.1 Overview
This procedure is used by an AF to retrieve from the CLF location information and other data related to an access
session.
This procedure is mapped to the commands User-Data-Request/Answer in the Diameter application specified in
TS 129 329 [7].
Tables 1 and 2 detail the involved information elements as defined in the NASS specification ES 282 004 [2] and their
mapping to Diameter AVPs.
Table 1: Information query request
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.
NASS User ID User-Name C The identity of the NASS User that is attached to the network.
AF Identity AF-Application-Identifier M Identifies the AF originating the request.
Requested-Items Requested-Information O The list of items requested by the AF.
NOTE: Either the Globally-Unique-IP-Address or the NASS User ID shall be included.

ETSI
11 ETSI ES 283 035 V2.5.1 (2008-08)
Table 2: Information query response
Information Mapping to diameter Cat. Description
element name AVP
Result Result-Code / M Result of the request.
Experimental_
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 the 3GPP Vendor ID in the Vendor-Id
AVP, and the error code in the Experimental-Result-Code AVP.
NASS User ID User-Name O The identity of the NASS User that is attached to the network.
Location Location-Information O Location information (or a pointer to such information) in a form that
Information is suitable for the requesting application.
RACS contact RACS-Contact- O The FQDN or IP address of the RACS entity where resource request
point Point shall be sent (i.e. SPDF address).
Access Network Access-Network- O The type of access network over which IP connectivity is provided to
Type Type the user equipment.
Terminal Type Terminal-Type O The type of user equipment to which the IP address was allocated.
Logical Access ID Logical-Access-Id O The identity of the logical access where the user equipment is
connected.
Physical Access ID Physical-Access-Id O The identity of the physical access where the user equipment is
connected.
5.2.1.2 Procedure at the AF side
The AF shall populate the Information Query as follows:
1) Insert either a Globally-Unique-Address or a User-Name AVP. 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 AF 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.
2) The AF-Application-Identifier AVP shall be present.
3) The Requested-Information AVP shall be present if specific information is requested and shall be absent if all
available information is requested.
5.2.1.3 Procedure at the CLF side
Upon reception of the Information Query, 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 Information Query
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 Information Query 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
Information Query with the Experimental-Result-Code AVP shall be set to
DIAMETER_ERROR_USER_UNKNOWN.
ETSI
12 ETSI ES 283 035 V2.5.1 (2008-08)
If a unique NASS user record can be retrieved, the CLF shall:
1) Check which session data can be returned to the AF, based on the contents of the Requested-Information AVP,
local policy rules and per-NASS user privacy information previously received from the UAAF/PDBF and
stored in the CLF.
NOTE 1: If the Requested-Information AVP is not received, the list of requested information is inferred from the
AF identity.
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.
Under temporary overload conditions, the CLF shall stop processing the request and return an Information Query
response with the Result-Code set to DIAMETER_TOO_BUSY. The AF may retry retrieving the required information
at a later stage.
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 the 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 Information Query response.
NOTE 2: Due to the application of operator's policies and NASS User privacy rules, the session data returned in the
message may be a subset of the explicitly or implicitly requested session data.
5.2.2 Event Registration/Deregistration
5.2.2.1 Overview
This procedure is used by an AF to subscribe with the CLF to a particular event.
This procedure is mapped to the commands Subscribe-Notifications-Request/Answer defined in the Diameter
application specified in TS 129 329 [7].
Tables 2a and 2b detail the involved information elements as identified in the NASS specification ES 282 004 [2] and
their mapping to Diameter AVPs.
Table 2a: Event Registration/Deregistration Request
Information Mapping to Diameter Cat. Description
element name AVP
Subs-Req-Type M Indicates whether the AF is willing to subscribe or unsubscribe to the
notification of the event.
NASS User ID User-Name C The identity of the NASS User on behalf of which the event is to be
reported.
Globally unique Globally Unique C This information element contains the IP address of the NASS User
IP Address Address on behalf of which the event is to be reported, together with the
addressing domain in which the IP address is significant.
Subscription Expiry-Time O Moment of expiration of the subscription to the event.
Expiration
Event Event-Type M The type of event to be monitored.
AF Identity AF-Application-Identifier M Identifies the AF originating the request.

ETSI
13 ETSI ES 283 035 V2.5.1 (2008-08)
Table 2b: Event Registration/Deregistration Response
Information Mapping to Cat. Description
element name Diameter AVP
Result Result-Code / M Result of the request.
Experimental_
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 the 3GPP Vendor ID in the Vendor-Id
AVP, and the error code in the Experimental-Result-Code AVP.
Expiry-Time O Acknowledges the absolute time at which the subscription expires.

The CLF monitors events related to access sessions. Monitoring of a particular event on a particular session is activated
when at least one Application Function has subscribed to be notified of the occurrence of the event.
Subscription to an event may be done implicitly (i.e. through management operations) or explicitly using the Event
Registration/Deregistration request. Subscription to an event ceases when one of the following conditions is met:
• Expiry of the subscription duration.
• Removal of the session record from the CLF.
• Receipt of an explicit request to unsubscribe.
5.2.2.2 Procedure at the AF side
The AF shall populate the Event Registration/Deregistration Request as follows:
Insert a Subs-Req-Type AVP indicating whether it is willing to subscribe or unsubscribe to the notification of events.
1) Insert either a Globally-Unique-Address or a User-Name AVP. 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 NASS Users
served by the AF is assumed to belong to the same addressing domain) or from the physical or logical interface
over which was received a related service request.
2) The AF-Application-Identifier AVP shall be present.
3) At least one occurrence of the Event-Type AVP shall be present.
4) The Expiry-Time AVP may be present.
5.2.2.3 Procedure at the CLF side
Upon reception of an Event Registration/Deregistration Request, the CLF shall, in the following order:
1) Based on the contents of the AF-Application-Identifier AVP, check whether the AF is allowed to request
monitoring of events. If not, return an Event Registration Response with Result-Code set to
DIAMETER_ERROR_OPERATION_NOT_ALLOWED.
2) If the Globally-Unique-Address AVP is present, use this information as a key to identify the session for which
event monitoring is being requested.
3) If the Globally-Unique-Address AVP is absent but the User-Name AVP is present, use the latter information as
a key to the session(s) for which event monitoring is being requested.
4) If both the Globally-Unique-Address AVP and the User-Name AVP are absent, return an Event
Registration/Deregistration Response with the Result-Code AVP set to DIAMETER_MISSING_AVP.
5) If no stored session record matches the Globally-Unique-Address AVP or the User-Name AVP and the
requested Event differs from USER-LOGON, return an Event Registration Response with the
Experimental-Result-Code AVP set to DIAMETER_ERROR_USER_UNKNOWN.
ETSI
14 ETSI ES 283 035 V2.5.1 (2008-08)
If the Subs-Req-Type AVP indicates that this is a request to subscribe to the notification of events, the CLF shall check
whether the requested event can be reported to the AF, based on local policy rules and per-NASS User privacy
information received from the UAAF. If the AF is not allowed to request monitoring of the event, return an Event
Registration/Deregistration Response with Result-Code set to
DIAMETER_ERROR_OPERATION_NOT_ALLOWED. If the AF is allowed to request monitoring of the event, the
CLF shall:
6) For all session records matching the request, associate the AF-Application-Identifier with the list of entities that
need to be notified when the event identified by the request occurs. The association lasts until the moment
indicated by the value of the Expiry-Time AVP as returned to the AF. If no Expiry-Time AVP is supplied, the
CLF should treat it as a request for an unlimited subscription.
7) Include in the Event Registration Response an Expiry Time AVP with the absolute time at which the
subscription expires in the case of a successful subscription. This time may be earlier than the requested expiry
time. If the CLF includes this AVP, then no notification shall be sent to the AF after the expiration time. If the
CLF does not include this AVP, that indicates an unlimited subscription.
8) Set the Result-Code to DIAMETER_SUCCESS and return an Event Registration/Deregistration Response.
If the Subs-Req-Type AVP indicates that this is a request to unsubscribe to the notification of events, the CLF shall
remove the association of the AF-Identifier with the same list. The Result-Code shall be set to DIAMETER_SUCCESS
if the operation is successful or if the AF-Identifier was not present in the list. If the Event-Type AVP is absent, the
CLF assumes that the AF is willing to unsubscribe to all events associated with the
User-Name or Globally-Unique-Address AVP.
If a subsequent request is received by the CLF where the Expiry Time AVP is present but different from what the CLF
has previously stored, the CLF should replace the stored expiration time with what was received in the request.
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 the Result-Code to DIAMETER_UNABLE_TO_COMPLY.
5.2.3 Notification Events
5.2.3.1 Overview
This procedure is used by a CLF to notify the AF of the occurrence of a particular event.
This procedure is mapped to the commands Push-Notifications-Request/Answer in the Diameter application specified in
TS 129 329 [7].
Tables 2c and 2d detail the involved information elements as defined in the NASS specification ES 282 004 [2] and
their mapping to Diameter AVPs.
Table 2c: Notification Event Request
Information Mapping to Diameter Cat. Description
element name AVP
NASS User ID User-Name C The identity of the NASS User on behalf of which the event is to be
reported.
Globally unique Globally Unique C This information element contains:
IP Address Address - The IP address of the NASS User on behalf of which the event is
to be reported.
- The addressing domain in which the IP address is significant.
AF Identity AF-Application-Identifier M Identifies the AF having registered to the request.
Event Event-Type M The type of event to be monitored.
[AVP] O AVPs carrying CLF information associated to the reported event.

ETSI
15 ETSI ES 283 035 V2.5.1 (2008-08)
Table 2d: Notification Event 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 the 3GPP Vendor ID in the Vendor-Id
AVP, and the error code in the Experimental-Result-Code AVP.

5.2.3.2 Procedure at the CLF side
When a monitored event is detected on a particular access session, the CLF issues a Notification Event Request to each
of the application functions having registered to this event.
The Notification Event Request is populated as follows:
1) A least a Globally-Unique-Address or a User-Name AVP shall be included. 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 AF belong to the same addressing domain) or from the physical or logical interface
over which was received a related service request.
2) The AF-Application-Identifier AVP shall be present.
3) One or more occurrence of the Event-Type AVP indicating the type of events being notified.
Based on local policy rules and per-NASS User privacy information previously received from the UAAF, the CLF may
also include additional information in the Event Registration/Deregistration Request. Table 2e provides an indication of
the AVPs that may be returned for each event.
Table 2e: Request-Information to AVP mapping
Event AVP
USER-LOGON IP-Connectivity-Status
LOCATION-INFORMATION-CHANGED Location-Information
RACS-CONTACT-POINT-CHANGED RACS-Contact-Point
ACCESS-NETWORK-TYPE -CHANGED Access-Network-Type
TERMINAL-TYPE -CHANGED Terminal-Type
LOGICAL-ACCESS-ID-CHANGED Logical-Access-Id
PHYSICAL-ACCESS-ID-CHANGED Physical Access-Id
INITIAL-GATE-SETTING-CHANGED Initial-Gate-Setting
QOS-PROFILE-CHANGED. QoS-Profile
IP-ADDRESS-CHANGED Globally-Unique-Address
USER-LOGOFF IP-Connectivity-Status

5.2.3.3 Procedure at the AF side
Upon reception of a Notification Event Request, the AF shall:
1) If neither the globally unique identifier contained in the Globally-Unique-Address AVP nor the NASS User ID
contained in the User-Name AVP are known, return a Notification Event Response with a Result-Code AVP
value set to DIAMETER_ERROR_USER_UNKNOWN.
2) If the event type contained in the Event-Type AVP is not known, return a Notification Event Response with a
Result-Code AVP value set to DIAMETER_INVALID_AVP_VALUE.
3) If the event type contained in the Event-Type AVP is known but was not expected, return a Notification Event
Response with a Result-Code AVP value set to DIAMETER_ERROR_NO_SUBSCRIPTION_TO_DATA.
ETSI
16 ETSI ES 283 035 V2.5.1 (2008-08)
If the AF cannot process the event for reasons not stated in the above steps return a Notification Event 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. After a provisioned number of unsuccessful retries, the CLF is expected to delete the AF-Identity from the list of
application functions registered to the event.
Otherwise, the event shall be processed and the AF shall return the Result-Code AVP set to DIAMETER_SUCCESS in
the Notification Event Response.
6 Use of the Diameter base protocol
With the clarifications listed in the following clauses the Diameter Base Protocol defined by RFC 3588 [10] 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 [12].
6.2 Accounting functionality
Accounting functionality (Accounting Session State Machine, related command codes and AVPs) is not used on the
e2 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.
T
...