SIST ES 283 035 V2.7.1:2016

Network Technologies (NTECH) - Network Attachment - e2 interface based on the DIAMETER protocol

The present document specifies a Diameter application for use between a Connectivity session Location and repository
Function (CLF) and an Application Function (AF).

Omrežne tehnologije (NTECH) - Omrežne priključitve - Vmesnik e2 na podlagi protokola DIAMETER

Ta dokument določa uporabo protokola Diameter za uporabo med funkcijo za lokacijo naročnikov (CLF) in funkcijo aplikacije (AF).

General Information

• Status: Published
• Publication Date: 01-Jun-2016
• ICS: 33.040.01 - Telecommunication systems in general
• ICS: 35.200 - Interface and interconnection equipment
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 17-May-2016
• Due Date: 22-Jul-2016
• Completion Date: 02-Jun-2016
• Ref Project: ETSI ES 283 035 V2.7.1 (2014-07) - Network Technologies (NTECH); Network Attachment; e2 interface based on the DIAMETER protocol

Standards Content (Sample)

ETSI ES 283 035 V2.7.1 (2014-07)






ETSI STANDARD
Network Technologies (NTECH);
Network Attachment;
e2 interface based on the DIAMETER protocol

---------------------- Page: 1 ----------------------
2 ETSI ES 283 035 V2.7.1 (2014-07)



Reference
RES/NTECH-0023
Keywords
interface, network, system
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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
The present document can be downloaded from:
http://www.etsi.org
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (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 or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2014.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI ES 283 035 V2.7.1 (2014-07)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 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.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 . 14
5.2.3.3 Procedure at the AF 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 . 16
6.4 Transport protocol . 16
6.5 Routing considerations . 16
6.6 Advertising application support . 16
7 DIAMETER application. 17
7.1 Commands . 17
7.1.1 User-Data-Request command . 17
7.1.2 User-Data-Answer command. 18
7.1.3 Subscribe-Notifications-Request (SNR) Command . 18
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 . 19
7.2 Result-Code AVP values . 20
7.2.1 Success . 20
7.2.2 Permanent failures . 20
7.2.3 Transient failures . 20
7.3 AVPs . 20
7.3.1 Location-Information AVP . 22
7.3.1A Civic-Location AVP . 22
7.3.1B Geospatial-Location AVP . 22
7.3.2 Policy-Control-Contact-Point AVP . 22
7.3.3 Terminal-Type AVP . 22
ETSI

---------------------- Page: 3 ----------------------
4 ETSI ES 283 035 V2.7.1 (2014-07)
7.3.4 Requested-Information AVP . 22
7.3.5 Line-Identifier AVP . 23
7.3.6 Event-Type AVP . 23
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 . 24
Annex A (informative): Application to NGN Architectures . 25
A.1 Overview . 25
A.2 Mapping of e2 operations and terminology to Diameter . 26
Annex B (informative): Change history . 27
History . 28

ETSI

---------------------- Page: 4 ----------------------
5 ETSI ES 283 035 V2.7.1 (2014-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://ipr.etsi.org).
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 Network Technologies (NTECH).
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "may not", "need", "need not", "will",
"will not", "can" and "cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms
for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI

---------------------- Page: 5 ----------------------
6 ETSI ES 283 035 V2.7.1 (2014-07)
1 Scope
The present document specifies a Diameter application for use between a Connectivity session Location and repository
Function (CLF) and an Application Function (AF).
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
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 necessary for the application of the present document.
[1] Void.
[2] Void.
[3] Void.
[4] Void.
[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); LTE; 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); LTE; 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".
ETSI

---------------------- Page: 6 ----------------------
7 ETSI ES 283 035 V2.7.1 (2014-07)
[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] Recommendation ITU-T 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 necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Functional Architecture Release 2".
[i.2] ETSI ES 282 004: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment
Sub-System (NASS)".
[i.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".
[i.4] ETSI ES 282 007: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
access network: collection of network entities and interfaces that provide the underlying IP transport connectivity
between end user devices and other networks
access record: 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
Attribute-Value Pair (AVP): Information Element in a Diameter message
NOTE: See RFC 3588 [10].
IP connectivity user: entity requesting IP connectivity from an access network
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ABNF Augmented Backus-Naur Form
AF Application Function
ASCII American Standard Code for Information Interchange
ASF Application Server Function
AVP Attribute-Value Pair
CLF Connectivity session Location and repository Function
CSCF Call Session Control Function
ETSI

---------------------- Page: 7 ----------------------
8 ETSI ES 283 035 V2.7.1 (2014-07)
DHCP Dynamic Host Configuration Protocol
FQDN Fully Qualified Domain Name
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
NGN Next Generation Network
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
UAAF User Authentication and Authorization Function
UDA User-Data-Answer
UDR User-Data-Request
UE User Equipment
4 Overview
The present document specifies a Diameter application for use between a Connectivity session Location and repository
Function (CLF) and an Application Function (AF). The interface between the CLF and the AF is known as the e2
interface (figure 1).
A Connectivity session Location and repository Function (CLF) is a data base in an access network that maintains a
mapping between IP addresses allocated to IP connectivity users and the corresponding network location. A CLF may
also store additional information related to IP connectivity sessions. How a CLF obtains this information is outside the
scope of the present document.
In the context of the present document, an Application Function (AF) represents any network element offering - or
providing access to - applications that require information about the characteristics of the IP-connectivity session used
to access such applications.
In an NGN architecture (ES 282 001 [i.1]), a CLF is a functional entity of the Network Attachment Sub-System (NASS)
defined in ES 282 004 [i.2]. Annex A provides further information on the use of a CLF in NGN architectures.
ETSI

---------------------- Page: 8 ----------------------
9 ETSI ES 283 035 V2.7.1 (2014-07)
AF
Scope of
this document
e2
CLF
UE Access Network Resources

Figure 1: e2 interface
5 Procedure descriptions
5.1 General
The following clauses describe the procedures for supporting interactions between an AF and a CLF.
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.
- 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.
ETSI

---------------------- Page: 9 ----------------------
10 ETSI ES 283 035 V2.7.1 (2014-07)
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 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 UE for which profile information is being
pushed.
- The addressing domain in which the IP address is significant.
IP connectivity User-Name C The identity of the IP connectivity user that is attached to the
user ID 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 IP connectivity user ID shall be included.

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.
IP connectivity User-Name O The identity of the IP connectivity user that is attached to the
user ID network.
Location Location-Information O Location information (or a pointer to such information) in a form that
Information is suitable for the requesting application.
Policy Control Policy-Control- O The FQDN or IP address of a policy control entity where resource
contact point Contact- request shall be sent.
Point
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.

ETSI

---------------------- Page: 10 ----------------------
11 ETSI ES 283 035 V2.7.1 (2014-07)
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 IP connectivity 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.
If a unique IP connectivity 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-IP connectivity 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
...

Final draft ETSI ES 283 035 V2.6.2 (2014-05)






ETSI Standard
Network Technologies (NTECH);
Network Attachment;
e2 interface based on the DIAMETER protocol

---------------------- Page: 1 ----------------------
2 Final draft ETSI ES 283 035 V2.6.2 (2014-05)



Reference
RES/NTECH-0023
Keywords
interface, network, system
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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
The present document can be downloaded from:
http://www.etsi.org
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (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 or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2014.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 Final draft ETSI ES 283 035 V2.6.2 (2014-05)
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.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 . 14
5.2.3.3 Procedure at the AF 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 . 16
6.4 Transport protocol . 16
6.5 Routing considerations . 16
6.6 Advertising application support . 16
7 DIAMETER application. 17
7.1 Commands . 17
7.1.1 User-Data-Request command . 17
7.1.2 User-Data-Answer command. 18
7.1.3 Subscribe-Notifications-Request (SNR) Command . 18
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 . 19
7.2 Result-Code AVP values . 20
7.2.1 Success . 20
7.2.2 Permanent failures . 20
7.2.3 Transient failures . 20
7.3 AVPs . 20
7.3.1 Location-Information AVP . 22
7.3.1A Civic-Location AVP . 22
7.3.1B Geospatial-Location AVP . 22
7.3.2 Policy-Control-Contact-Point AVP . 22
7.3.3 Terminal-Type AVP . 22
7.3.4 Requested-Information AVP . 22
7.3.5 Line-Identifier AVP . 23
ETSI

---------------------- Page: 3 ----------------------
4 Final draft ETSI ES 283 035 V2.6.2 (2014-05)
7.3.6 Event-Type AVP . 23
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 . 24
Annex A (informative): Application to NGN Architectures . 25
A.1 Overview . 25
A.2 Mapping of e2 operations and terminology to Diameter . 26
Annex B (informative): Change history . 27
History . 28

ETSI

---------------------- Page: 4 ----------------------
5 Final draft ETSI ES 283 035 V2.6.2 (2014-05)
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://ipr.etsi.org).
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 final draft ETSI Standard (ES) has been produced by ETSI Technical Committee Network Technologies
(NTECH), and is now submitted for the ETSI standards Membership Approval Procedure.
ETSI

---------------------- Page: 5 ----------------------
6 Final draft ETSI ES 283 035 V2.6.2 (2014-05)
1 Scope
The present document specifies a Diameter application for use between a Connectivity session Location and repository
Function (CLF) and an Application Function (AF).
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
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 necessary for the application of the present document.
[1] Void.
[2] Void.
[3] Void.
[4] Void.
[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); LTE; 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); LTE; 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".
ETSI

---------------------- Page: 6 ----------------------
7 Final draft ETSI ES 283 035 V2.6.2 (2014-05)
[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] Recommendation ITU-T 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 necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Functional Architecture Release 2".
[i.2] ETSI ES 282 004: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-
System (NASS)".
[i.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".
[i.4] ETSI ES 282 007: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
access network: collection of network entities and interfaces that provide the underlying IP transport connectivity
between end user devices and other networks
access record: 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
Attribute-Value Pair (AVP): Information Element in a Diameter message
NOTE: See RFC 3588 [10].
IP connectivity user: entity requesting IP connectivity from an access network
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ABNF Augmented Backus-Naur Form
AF Application Function
ASCII American Standard Code for Information Interchange
ASF Application Server Function
AVP Attribute-Value Pair
CLF Connectivity session Location and repository Function
CSCF Call Session Control Function
ETSI

---------------------- Page: 7 ----------------------
8 Final draft ETSI ES 283 035 V2.6.2 (2014-05)
DHCP Dynamic Host Configuration Protocol
FQDN Fully Qualified Domain Name
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
NGN Next Generation Network
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
UAAF User Authentication and Authorization Function
UDA User-Data-Answer
UDR User-Data-Request
UE User Equipment
4 Overview
The present document specifies a Diameter application for use between a Connectivity session Location and repository
Function (CLF) and an Application Function (AF). The interface between the CLF and the AF is known as the e2
interface (figure 1).
A Connectivity session Location and repository Function (CLF) is a data base in an access network that maintains a
mapping between IP addresses allocated to IP connectivity users and the corresponding network location. A CLF may
also store additional information related to IP connectivity sessions. How a CLF obtains this information is outside the
scope of the present document.
In the context of the present document, an Application Function (AF) represents any network element offering - or
providing access to - applications that require information about the characteristics of the IP-connectivity session used
to access such applications.
In an NGN architecture (ES 282 001 [i.1]), a CLF is a functional entity of the Network Attachment Sub-System (NASS)
defined in ES 282 004 [i.2]. Annex A provides further information on the use of a CLF in NGN architectures.
ETSI

---------------------- Page: 8 ----------------------
9 Final draft ETSI ES 283 035 V2.6.2 (2014-05)
AF
Scope of
this document
e2
CLF
UE Access Network Resources

Figure 1: e2 interface
5 Procedure descriptions
5.1 General
The following clauses describe the procedures for supporting interactions between an AF and a CLF.
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.
- 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.
ETSI

---------------------- Page: 9 ----------------------
10 Final draft ETSI ES 283 035 V2.6.2 (2014-05)
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 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 UE for which profile information is being
pushed.
- The addressing domain in which the IP address is significant.
IP connectivity User-Name C The identity of the IP connectivity user that is attached to the
user ID 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 IP connectivity user ID shall be included.

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.
IP connectivity User-Name O The identity of the IP connectivity user that is attached to the
user ID network.
Location Location-Information O Location information (or a pointer to such information) in a form that
Information is suitable for the requesting application.
Policy Control Policy-Control- O The FQDN or IP address of a policy control entity where resource
contact point Contact- request shall be sent.
Point
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.

ETSI

---------------------- Page: 10 ----------------------
11 Final draft ETSI ES 283 035 V2.6.2 (2014-05)
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 IP connectivity 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.
If a unique IP connectivity 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-IP connectivity 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 IP connectivity user privacy rules, the session data
returned in the message may be a subset of the explicitly or implicitly requested session data.
ETSI

---------------------- Page: 11 ----------------------
12 Final draft ETSI ES 283 035 V2.6.2 (2014-
...

SLOVENSKI STANDARD
SIST ES 283 035 V2.7.1:2016
01-julij-2016
2PUHåQHWHKQRORJLMH17(&+2PUHåQHSULNOMXþLWYH9PHVQLNHQDSRGODJL
SURWRNROD',$0(7(5
Network Technologies (NTECH) - Network Attachment - e2 interface based on the
DIAMETER protocol
Ta slovenski standard je istoveten z: ETSI ES 283 035 V2.7.1 (2014-07)
ICS:
33.040.01 Telekomunikacijski sistemi Telecommunication systems
na splošno in general
35.200 Vmesniška in povezovalna Interface and interconnection
oprema equipment
SIST ES 283 035 V2.7.1:2016 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ES 283 035 V2.7.1:2016

---------------------- Page: 2 ----------------------

SIST ES 283 035 V2.7.1:2016

---------------------- Page: 3 ----------------------

SIST ES 283 035 V2.7.1:2016

---------------------- Page: 4 ----------------------

SIST ES 283 035 V2.7.1:2016

---------------------- Page: 5 ----------------------

SIST ES 283 035 V2.7.1:2016

---------------------- Page: 6 ----------------------

SIST ES 283 035 V2.7.1:2016

---------------------- Page: 7 ----------------------

SIST ES 283 035 V2.7.1:2016

---------------------- Page: 8 ----------------------

SIST ES 283 035 V2.7.1:2016

---------------------- Page: 9 ----------------------

SIST ES 283 035 V2.7.1:2016

---------------------- Page: 10 ----------------------

SIST ES 283 035 V2.7.1:2016

---------------------- Page: 11 ----------------------

SIST ES 283 035 V2.7.1:2016

---------------------- Pag
...