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

The present document defines a protocol for use between the TISPAN NGN Network Attachment Sub-System (NASS) and the Resource and Admission Control Subsystem (RACS), based on Diameter. The present document is applicable to the e4 interface between the Connectivity Session Location and Repository Function (CLF) and the RACS. Whenever it is possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within the present document.

Zlite telekomunikacijske in internetne storitve ter protokoli za napredno omreženje (TISPAN) - Podsistem omrežne priključitve (NASS) - Vmesnik e4 na podlagi protokola DIAMETER

General Information

Status
Published
Publication Date
01-Jun-2008
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
23-Apr-2008
Due Date
28-Jun-2008
Completion Date
02-Jun-2008

Buy Standard

Standard
ETSI ES 283 034 V1.5.0 (2008-04) - Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Network Attachment Sub-System (NASS); e4 interface based on the DIAMETER protocol
English language
27 pages
sale 15% off
Preview
sale 15% off
Preview
Standard
ETSI ES 283 034 V1.5.0 (2008-01) - Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Network Attachment Sub-System (NASS); e4 interface based on the DIAMETER protocol
English language
26 pages
sale 15% off
Preview
sale 15% off
Preview
Standardization document
SIST ES 283 034 V1.5.0:2008
English language
27 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day

Standards Content (sample)

ETSI ES 283 034 V1.5.0 (2008-04)
ETSI Standard
Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Network Attachment Sub-System (NASS);
e4 interface based on the DIAMETER protocol
---------------------- Page: 1 ----------------------
2 ETSI ES 283 034 V1.5.0 (2008-04)
Reference
RES/TISPAN-03124-NGN-R1
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.

3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.

ETSI
---------------------- Page: 2 ----------------------
3 ETSI ES 283 034 V1.5.0 (2008-04)
Contents

Intellectual Property Rights................................................................................................................................5

Foreword.............................................................................................................................................................5

1 Scope........................................................................................................................................................6

2 References................................................................................................................................................6

2.1 Normative references.........................................................................................................................................6

2.2 Informative references........................................................................................................................................7

3 Definitions and abbreviations...................................................................................................................7

3.1 Definitions..........................................................................................................................................................7

3.2 Abbreviations.....................................................................................................................................................7

4 Overview..................................................................................................................................................8

5 Procedure descriptions .............................................................................................................................9

5.1 General...............................................................................................................................................................9

5.1.1 Information elements....................................................................................................................................9

5.1.2 Subscriber profile..........................................................................................................................................9

5.2 Procedures on the CLF - A-RACF interface ....................................................................................................10

5.2.1 Access profile push.....................................................................................................................................10

5.2.1.1 Overview...............................................................................................................................................10

5.2.1.2 Procedure at the CLF side .....................................................................................................................11

5.2.1.3 Procedure at the A-RACF side..............................................................................................................11

5.2.2 Access profile pull ......................................................................................................................................12

5.2.2.1 Overview...............................................................................................................................................12

5.2.2.2 Procedure at the A-RACF side..............................................................................................................13

5.2.2.3 Procedure at the CLF side .....................................................................................................................13

5.2.3 IP connectivity release indication ...............................................................................................................14

5.2.3.1 Overview...............................................................................................................................................14

5.2.3.2 Procedure at the CLF side .....................................................................................................................14

5.2.3.3 Procedure at the A-RACF side..............................................................................................................15

6 Use of the Diameter base protocol .........................................................................................................15

6.1 Securing Diameter messages............................................................................................................................15

6.2 Accounting functionality..................................................................................................................................15

6.3 Use of sessions .................................................................................................................................................15

6.4 Transport protocol............................................................................................................................................15

6.5 Routing considerations.....................................................................................................................................16

6.6 Advertising application support .......................................................................................................................16

7 DIAMETER application.........................................................................................................................16

7.1 Commands........................................................................................................................................................16

7.1.1 User-Data-Request command.....................................................................................................................17

7.1.2 User-Data-Answer command......................................................................................................................17

7.1.3 Push-Notification-Request command.........................................................................................................18

7.1.4 Push-Notification-Answer command..........................................................................................................18

7.2 Result-Code AVP values..................................................................................................................................18

7.2.1 Success........................................................................................................................................................19

7.2.2 Permanent failures......................................................................................................................................19

7.2.3 Transient failures........................................................................................................................................19

7.3 AVPs................................................................................................................................................................20

7.3.1 Globally-Unique-Address AVP..................................................................................................................21

7.3.2 Address-Realm AVP...................................................................................................................................21

7.3.3 Logical-Access-ID AVP.............................................................................................................................21

7.3.4 Initial-Gate-Setting AVP............................................................................................................................22

7.3.5 QoS-Profile AVP........................................................................................................................................22

7.3.6 IP-Connectivity-Status AVP.......................................................................................................................22

7.3.7 Access-Network-Type AVP.......................................................................................................................22

ETSI
---------------------- Page: 3 ----------------------
4 ETSI ES 283 034 V1.5.0 (2008-04)

7.3.8 Aggregation-Network-Type AVP...............................................................................................................23

7.3.9 Maximum-Allowed-Bandwidth-UL AVP..................................................................................................23

7.3.10 Maximum-Allowed-Bandwidth-DL AVP..................................................................................................23

7.3.11 Reservation-Priority....................................................................................................................................23

7.3.12 Transport-Class...........................................................................................................................................23

7.3.13 Application-Class-ID..................................................................................................................................23

7.3.14 Physical-Access-ID.....................................................................................................................................24

7.3.15 NAS-Port-Type AVP..................................................................................................................................24

7.3.16 NAS-Filter-Rule AVP.................................................................................................................................24

7.3.17 Framed-IP-Address AVP............................................................................................................................24

7.3.18 Framed-IP-Prefix AVP...............................................................................................................................24

7.3.19 Origin-Host AVP........................................................................................................................................24

7.3.20 AF-Application-Identifier AVP..................................................................................................................24

7.3.21 Media-Type AVP........................................................................................................................................24

7.4 Use of namespaces ...........................................................................................................................................24

7.4.1 AVP codes..................................................................................................................................................24

7.4.2 Experimental-Result-Code AVP values......................................................................................................24

7.4.3 Command Code values ...............................................................................................................................24

7.4.4 Application-ID value..................................................................................................................................25

Annex A (informative): Mapping of e4 operations and terminology to Diameter............................26

History ..............................................................................................................................................................27

ETSI
---------------------- Page: 4 ----------------------
5 ETSI ES 283 034 V1.5.0 (2008-04)
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
---------------------- Page: 5 ----------------------
6 ETSI ES 283 034 V1.5.0 (2008-04)
1 Scope

The present document defines a protocol for use between the TISPAN NGN Network Attachment Sub-System (NASS)

and the Resource and Admission Control Subsystem (RACS), based on Diameter.

The present document is applicable to the e4 interface between the Connectivity Session Location and Repository

Function (CLF) and the RACS.

Whenever it is possible the present document specifies the requirements for this protocol by reference to specifications

produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined

within the present document.
2 References

References are either specific (identified by date of publication and/or edition number or version number) or

non-specific.
• For a specific reference, subsequent revisions do not apply.

• Non-specific reference may be made only to a complete document or a part thereof and only in the following

cases:

- if it is accepted that it will be possible to use all future changes of the referenced document for the

purposes of the referring document;
- for informative references.

Referenced documents which are not found to be publicly available in the expected location might be found at

http://docbox.etsi.org/Reference.

For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,

the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the

reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the

method of access to the referenced document and the full network address, with the same punctuation and use of upper

case and lower case letters.

NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee

their long term validity.
2.1 Normative references

The following referenced documents are indispensable for the application of the present document. For dated

references, only the edition cited applies. For non-specific references, the latest edition of the referenced document

(including any amendments) applies.

[1] ETSI ES 282 004: "Telecommunications and Internet converged Services and Protocols for

Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment
Sub-System (NASS)".

[2] ETSI ES 282 003: "Telecommunications and Internet converged Services and Protocols for

Advanced Networking (TISPAN); Resource and Admission Control Sub-system (RACS);
Functional Architecture".

[3] ETSI TS 129 229: "Digital cellular telecommunications system (Phase 2+); Universal Mobile

Telecommunications System (UMTS); Cx and Dx interfaces based on the Diameter protocol;

Protocol details (3GPP TS 29.229)".

[4] ETSI TS 129 329: "Digital cellular telecommunications system (Phase 2+); Universal Mobile

Telecommunications System (UMTS); Sh interface based on the Diameter protocol; Protocol

details (3GPP TS 29.329)".
ETSI
---------------------- Page: 6 ----------------------
7 ETSI ES 283 034 V1.5.0 (2008-04)

[5] ETSI TS 129 209: "Universal Mobile Telecommunications System (UMTS); Policy control over

Gq interface (3GPP TS 29.209)".
[6] IETF RFC 2960: "Stream Control Transmission Protocol".
[7] IETF RFC 3588: "Diameter Base Protocol".

[8] IETF RFC 3309: "Stream Control Transmission Protocol (SCTP) Checksum Change".

[9] IETF RFC 4005: "Diameter Network Access Server application".

[10] IETF RFC 3554: "On the use of Stream Control Transmission Protocol (SCTP) with IPsec".

[11] IETF RFC 3046: "DHCP Relay Agent Information Option".

[12] ETSI TS 183 017: "Telecommunications and Internet Converged Services and Protocols for

Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER protocol for

session based policy set up information exchange between the Application Function (AF) and the

Service Policy Decision Function (SPDF); Protocol specification".
2.2 Informative references
Not applicable.
3 Definitions and abbreviations
3.1 Definitions

For the purposes of the present document, the following terms and definitions apply:

Application Function (AF): element of the service layer architecture offering applications that require information

about the characteristics of the IP-connectivity session used to access such applications

Attribute-Value Pair (AVP): corresponds to an Information Element in a Diameter message

NOTE: See RFC 3588 [7].
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ABNF Augmented Backus-Naur Form
AF Application Function
A-RACF Access-Resource and Admission Control Function
ATM Asynchronous Transfer Mode
AVP Attribute-Value Pair
BGF Border Gateway Function
CLF Connectivity session Location and repository Function
FQDN Fully Qualified Domain Name
IANA Internet Assigned Numbers Authority
ID IDentifier
IETF Internet Engineering Task Force
IPSec IP Security
L2TF Layer 2 Termination Function
NAS Network Access Server
NASS Network Attachment Sub-System
PDBF Profile Data Base Function
PNA Push-Notification-Answer
PNR Push-Notification-Request
ETSI
---------------------- Page: 7 ----------------------
8 ETSI ES 283 034 V1.5.0 (2008-04)
RACF Resource and Admission Control Function
RACS Resource and Admission Control Subsystem
RCEF Resource Control Enforcement Function
RFC Request For Comments
SCTP Stream Control Transport Protocol
SPDF Service-based Policy Decision Function
UAAF User Authentication and Authorization Function
UCS Universal Character Set
UDA User-Data-Answer
UDR User-Data-Request
VC Virtual Channel
VP Virtual Path
4 Overview

The Network Attachment Sub-System (NASS), defined in ES 282 004 [1], maintains information about IP-connectivity

associated with user equipment connected to TISPAN networks. This information is stored in the Connectivity Session

Location and Repository Function (CLF) and made accessible to other subsystems and applications through the

following two interfaces (see figure 1):

• The e2 interface enables Application Functions (AF) to retrieve IP-connectivity related session data.

• The e4 interface enables the IP-connectivity related session data to be exchanged between the NASS and the

Resource and Admission Control Subsystem (RACS) defined in ES 282 003 [2].
The present document specifies the protocol for the e4 interface.
Service Control
Subsystems and
Applications
CLF
NASS
Scope of the present
A-RACF
document
RACS
Transfer Functions
Figure 1: NASS external interfaces
ETSI
---------------------- Page: 8 ----------------------
9 ETSI ES 283 034 V1.5.0 (2008-04)
5 Procedure descriptions
5.1 General
5.1.1 Information elements

The following clauses describe the realization of the functional procedures defined in the NASS (ES 282 004) [1] and

RACS specifications (ES 282 003 [2]) using Diameter commands described in clause 7. This involves describing a

mapping between the Information Elements defined in the NASS specification (ES 282 004 [1]) and Diameter AVPs.

In the tables that describe this mapping, each Information Element is marked as (M) Mandatory, (C) Conditional or (O)

Optional:

• A mandatory Information Element (marked as (M) in 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 the table) 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 the table) may be present or absent in the command, at the

discretion of the application at the sending entity. Absence or presence of this Information Element shall not

cause an application error and may be ignored by the receiver.
5.1.2 Subscriber profile

Subscriber profile information sent over the e4 interface is structured into two groups: the QoS Profile Information and

the initial gate setting.

Tables 1 and 2 detail the involved information elements as defined in the NASS specification ES 282 004 [1] and their

mapping to DIAMETER AVPs.
Table 1: Initial gate setting
Information Mapping to Category Description
element name Diameter AVP

List of allowed NAS-Filter-Rule O The list of default destination IP addresses, ports, prefixes and

destinations port ranges to which traffic can be sent.

UL Subscribed Maximum-Allowed- O The maximum amount of bandwidth that can be used without

Bandwidth Bandwidth-UL explicit authorization in the uplink direction.

DL Subscribed Maximum-Allowed- O The maximum amount of bandwidth that can be used without

Bandwidth Bandwidth-DL explicit authorization in the downlink direction.
ETSI
---------------------- Page: 9 ----------------------
10 ETSI ES 283 034 V1.5.0 (2008-04)
Table 2: QoS profile information
Information Mapping to Category Description
element name Diameter AVP

Transport Transport-Class O The transport class applicable to the QoS Profile Information.

service class

Media-Type Media-Type O The media type applicable to the QoS Profile information.

UL Subscribed Maximum-Allowed- O The maximum amount of bandwidth subscribed by the attached

Bandwidth Bandwidth-UL user in the uplink direction.

DL Subscribed Maximum-Allowed- O The maximum amount of bandwidth subscribed by the attached

Bandwidth Bandwidth-DL user in the downlink direction.

Maximum Reservation-Priority O The maximum priority allowed for any reservation request.

Priority

Requestor Application Class ID O Identifies the application class(es) that are allowed to request

Name resources for the QoS profile.
5.2 Procedures on the CLF - A-RACF interface
5.2.1 Access profile push
5.2.1.1 Overview

This procedure is used to push session-related information from the CLF to the A-RACF. This information flow occurs

when an IP address has been allocated to a subscriber or in case a modification occurs on a profile that has already been

pushed to the RACS.

The CLF should push session-related-information to the A-RACF as soon as it is available to the CLF. This may require

the CLF to pull part of the information from other components of the NASS.

For the same subscriber, the CLF may push several independent session records with different IP addresses, with or

without the same logical access identifier.

This procedure is mapped to the commands Push-Notification-Request/Answer in the Diameter application specified in

clause 7. Tables 3 and 4 detail the involved information elements as defined in the NASS specification ES 282 004 [1]

and their mapping to Diameter AVPs.
Table 3: Access profile push
Information Mapping to Diameter Category Description
element name AVP
Globally Unique Globally-Unique-Address M This information element contains:
IP Address - The IP address of the user equipment used by the
subscriber for which profile information is being
pushed.
- The addressing domain in which the IP address is
significant.

Logical Access Logical-Access-Id M The identity of the logical access to which the user

ID equipment is connected.

Access Access-Network-Type O The type of access network over which IP connectivity is

Network Type provided to the user equipment.
Subscriber ID User-Name C The user that is attached to the network (see note).

Physical Physical-Access-Id O The identity of the physical access to which the user

Access ID equipment is connected.
Initial Gate Initial-Gate-Setting O See clause 5.1, table 1.
Setting
QoS Profile QoS-Profile O See clause 5.1, table 2.
NOTE: The Subscriber ID shall be included if available in the CLF.
ETSI
---------------------- Page: 10 ----------------------
11 ETSI ES 283 034 V1.5.0 (2008-04)
Table 4: Access profile push response
Information Mapping to Diameter AVP Category Description
element name
Result Result-Code / Experimental_ M Result of the request.
Result
Result-Code AVP shall be used for errors defined in the
Diameter Base Protocol.
Experimental-Result AVP shall be used for other errors.
This is a grouped AVP which contains a Vendor-Id AVP,
and the error code in the Experimental-Result-Code
AVP.
5.2.1.2 Procedure at the CLF side

The CLF knows the address of the A-RACF entity where the information should be pushed, either from configuration

data or from the user profile (i.e. received from the UAAF/PDBF).
The CLF shall populate the Access Profile Push as follows:

• The Globally-Unique-Address AVP shall contain a Frame-IP-Address or Frame-IPv6-Prefix AVP value, and

an Address-Realm AVP.
• The Logical-Access-ID AVP shall be present.

The presence of the other AVPs depends on the user profile and local policy rules.

5.2.1.3 Procedure at the A-RACF side

If the Logical Access ID is not included or is invalid, the A-RACF shall return an Access Profile Push response with a

Result-Code AVP value set to DIAMETER_INVALID_AVP_VALUE.

If the globally unique identifier contained in the Globally-Unique-Address AVP is not known, the A-RACF shall:

• Create an internal record to store the received information for future use (i.e. for processing resource

reservation requests received from the SPDF).
• Derive the following information from the Logical Access ID:

- The identification and bandwidth capacity of the layer 2 resources over which the subscriber traffic is

...

Final draft ETSI ES 283 034 V1.5.0 (2008-01)
ETSI Standard
Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Network Attachment Sub-System (NASS);
e4 interface based on the DIAMETER protocol
---------------------- Page: 1 ----------------------
2 Final draft ETSI ES 283 034 V1.5.0 (2008-01)
Reference
RES/TISPAN-03124-NGN-R1
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.

3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.

ETSI
---------------------- Page: 2 ----------------------
3 Final draft ETSI ES 283 034 V1.5.0 (2008-01)
Contents

Intellectual Property Rights................................................................................................................................5

Foreword.............................................................................................................................................................5

1 Scope........................................................................................................................................................6

2 References................................................................................................................................................6

2.1 Normative references.........................................................................................................................................6

3 Definitions and abbreviations...................................................................................................................7

3.1 Definitions..........................................................................................................................................................7

3.2 Abbreviations.....................................................................................................................................................7

4 Overview..................................................................................................................................................8

5 Procedure descriptions .............................................................................................................................9

5.1 General...............................................................................................................................................................9

5.1.1 Information elements....................................................................................................................................9

5.1.2 Subscriber profile..........................................................................................................................................9

5.2 Procedures on the CLF - A-RACF interface ....................................................................................................10

5.2.1 Access profile push.....................................................................................................................................10

5.2.1.1 Overview...............................................................................................................................................10

5.2.1.2 Procedure at the CLF side .....................................................................................................................11

5.2.1.3 Procedure at the A-RACF side..............................................................................................................11

5.2.2 Access profile pull ......................................................................................................................................12

5.2.2.1 Overview...............................................................................................................................................12

5.2.2.2 Procedure at the A-RACF side..............................................................................................................12

5.2.2.3 Procedure at the CLF side .....................................................................................................................13

5.2.3 IP connectivity release indication ...............................................................................................................13

5.2.3.1 Overview...............................................................................................................................................13

5.2.3.2 Procedure at the CLF side .....................................................................................................................14

5.2.3.3 Procedure at the A-RACF side..............................................................................................................14

6 Use of the Diameter base protocol .........................................................................................................15

6.1 Securing Diameter messages............................................................................................................................15

6.2 Accounting functionality..................................................................................................................................15

6.3 Use of sessions .................................................................................................................................................15

6.4 Transport protocol............................................................................................................................................15

6.5 Routing considerations.....................................................................................................................................15

6.6 Advertising application support .......................................................................................................................15

7 DIAMETER application.........................................................................................................................16

7.1 Commands........................................................................................................................................................16

7.1.1 User-Data-Request command.....................................................................................................................16

7.1.2 User-Data-Answer command......................................................................................................................17

7.1.3 Push-Notification-Request command.........................................................................................................17

7.1.4 Push-Notification-Answer command..........................................................................................................18

7.2 Result-Code AVP values..................................................................................................................................18

7.2.1 Success........................................................................................................................................................18

7.2.2 Permanent failures......................................................................................................................................19

7.2.3 Transient failures........................................................................................................................................19

7.3 AVPs................................................................................................................................................................19

7.3.1 Globally-Unique-Address AVP..................................................................................................................21

7.3.2 Address-Realm AVP...................................................................................................................................21

7.3.3 Logical-Access-ID AVP.............................................................................................................................21

7.3.4 Initial-Gate-Setting AVP............................................................................................................................21

7.3.5 QoS-Profile AVP........................................................................................................................................21

7.3.6 IP-Connectivity-Status AVP.......................................................................................................................22

7.3.7 Access-Network-Type AVP.......................................................................................................................22

7.3.8 Aggregation-Network-Type AVP...............................................................................................................22

ETSI
---------------------- Page: 3 ----------------------
4 Final draft ETSI ES 283 034 V1.5.0 (2008-01)

7.3.9 Maximum-Allowed-Bandwidth-UL AVP..................................................................................................22

7.3.10 Maximum-Allowed-Bandwidth-DL AVP..................................................................................................22

7.3.11 Reservation-Priority....................................................................................................................................22

7.3.12 Transport-Class...........................................................................................................................................23

7.3.13 Application-Class-ID..................................................................................................................................23

7.3.14 Physical-Access-ID.....................................................................................................................................23

7.3.15 NAS-Port-Type AVP..................................................................................................................................23

7.3.16 NAS-Filter-Rule AVP.................................................................................................................................23

7.3.17 Framed-IP-Address AVP............................................................................................................................23

7.3.18 Framed-IP-Prefix AVP...............................................................................................................................23

7.3.19 Origin-Host AVP........................................................................................................................................23

7.3.20 AF-Application-Identifier AVP..................................................................................................................23

7.3.21 Media-Type AVP........................................................................................................................................24

7.4 Use of namespaces ...........................................................................................................................................24

7.4.1 AVP codes..................................................................................................................................................24

7.4.2 Experimental-Result-Code AVP values......................................................................................................24

7.4.3 Command Code values ...............................................................................................................................24

7.4.4 Application-ID value..................................................................................................................................24

Annex A (informative): Mapping of e4 operations and terminology to Diameter............................25

History ..............................................................................................................................................................26

ETSI
---------------------- Page: 4 ----------------------
5 Final draft ETSI ES 283 034 V1.5.0 (2008-01)
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), and is now submitted for the ETSI standards

Membership Approval Procedure.
ETSI
---------------------- Page: 5 ----------------------
6 Final draft ETSI ES 283 034 V1.5.0 (2008-01)
1 Scope

The present document defines a protocol for use between the TISPAN NGN Network Attachment Sub-System (NASS)

and the Resource and Admission Control Subsystem (RACS), based on Diameter.

The present document is applicable to the e4 interface between the Connectivity Session Location and Repository

Function (CLF) and the RACS.

Whenever it is possible the present document specifies the requirements for this protocol by reference to specifications

produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined

within the present document.
2 References

References are either specific (identified by date of publication and/or edition number or version number) or

non-specific.
• For a specific reference, subsequent revisions do not apply.

• Non-specific reference may be made only to a complete document or a part thereof and only in the following

cases:

- if it is accepted that it will be possible to use all future changes of the referenced document for the

purposes of the referring document;
- for informative references.

Referenced documents which are not found to be publicly available in the expected location might be found at

http://docbox.etsi.org/Reference.

For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,

the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the

reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the

method of access to the referenced document and the full network address, with the same punctuation and use of upper

case and lower case letters.

NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee

their long term validity.
2.1 Normative references

The following referenced documents are indispensable for the application of the present document. For dated

references, only the edition cited applies. For non-specific references, the latest edition of the referenced document

(including any amendments) applies.

[1] ETSI ES 282 004: "Telecommunications and Internet converged Services and Protocols for

Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment
Sub-System (NASS)".

[2] ETSI ES 282 003: "Telecommunications and Internet converged Services and Protocols for

Advanced Networking (TISPAN); Resource and Admission Control Sub-system (RACS);
Functional Architecture".

[3] ETSI TS 129 229: "Digital cellular telecommunications system (Phase 2+); Universal Mobile

Telecommunications System (UMTS); Cx and Dx interfaces based on the Diameter protocol;

Protocol details (3GPP TS 29.229)".

[4] ETSI TS 129 329: "Digital cellular telecommunications system (Phase 2+); Universal Mobile

Telecommunications System (UMTS); Sh interface based on the Diameter protocol; Protocol

details (3GPP TS 29.329)".
ETSI
---------------------- Page: 6 ----------------------
7 Final draft ETSI ES 283 034 V1.5.0 (2008-01)

[5] ETSI TS 129 209: "Universal Mobile Telecommunications System (UMTS); Policy control over

Gq interface (3GPP TS 29.209)".
[6] IETF RFC 2960: "Stream Control Transmission Protocol".
[7] IETF RFC 3588: "Diameter Base Protocol".

[8] IETF RFC 3309: "Stream Control Transmission Protocol (SCTP) Checksum Change".

[9] IETF RFC 4005: "Diameter Network Access Server application".

[10] IETF RFC 3554: "On the use of Stream Control Transmission Protocol (SCTP) with IPsec".

[11] IETF RFC 3046: "DHCP Relay Agent Information Option".

[12] ETSI TS 183 017: "Telecommunications and Internet Converged Services and Protocols for

Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER protocol for

session based policy set up information exchange between the Application Function (AF) and the

Service Policy Decision Function (SPDF); Protocol specification".
3 Definitions and abbreviations
3.1 Definitions

For the purposes of the present document, the following terms and definitions apply:

Application Function (AF): element of the service layer architecture offering applications that require information

about the characteristics of the IP-connectivity session used to access such applications

Attribute-Value Pair (AVP): corresponds to an Information Element in a Diameter message

NOTE: See RFC 3588 [7].
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ABNF Augmented Backus-Naur Form
AF Application Function
A-RACF Access-Resource and Admission Control Function
ATM Asynchronous Transfer Mode
AVP Attribute-Value Pair
BGF Border Gateway Function
CLF Connectivity session Location and repository Function
FQDN Fully Qualified Domain Name
IANA Internet Assigned Numbers Authority
ID IDentifier
IETF Internet Engineering Task Force
IPSec IP Security
L2TF Layer 2 Termination Function
NAS Network Access Server
NASS Network Attachment Sub-System
PDBF Profile Data Base Function
PNA Push-Notification-Answer
PNR Push-Notification-Request
RACF Resource and Admission Control Function
RACS Resource and Admission Control Subsystem
RCEF Resource Control Enforcement Function
RFC Request For Comments
SCTP Stream Control Transport Protocol
ETSI
---------------------- Page: 7 ----------------------
8 Final draft ETSI ES 283 034 V1.5.0 (2008-01)
SPDF Service-based Policy Decision Function
UAAF User Authentication and Authorization Function
UCS Universal Character Set
UDA User-Data-Answer
UDR User-Data-Request
VC Virtual Channel
VP Virtual Path
4 Overview

The Network Attachment Sub-System (NASS), defined in ES 282 004 [1], maintains information about IP-connectivity

associated with user equipment connected to TISPAN networks. This information is stored in the Connectivity Session

Location and Repository Function (CLF) and made accessible to other subsystems and applications through the

following two interfaces (see figure 1):

• The e2 interface enables Application Functions (AF) to retrieve IP-connectivity related session data.

• The e4 interface enables the IP-connectivity related session data to be exchanged between the NASS and the

Resource and Admission Control Subsystem (RACS) defined in ES 282 003 [2].
The present document specifies the protocol for the e4 interface.
Service Control
Subsystems and
AF Applications
CLF
NASS
Scope of the present
document A-RACF
RACS
Transfer Functions
Figure 1: NASS external interfaces
ETSI
---------------------- Page: 8 ----------------------
9 Final draft ETSI ES 283 034 V1.5.0 (2008-01)
5 Procedure descriptions
5.1 General
5.1.1 Information elements

The following clauses describe the realization of the functional procedures defined in the NASS (ES 282 004) [1] and

RACS specifications (ES 282 003 [2]) using Diameter commands described in clause 7. This involves describing a

mapping between the Information Elements defined in the NASS specification (ES 282 004 [1]) and Diameter AVPs.

In the tables that describe this mapping, each Information Element is marked as (M) Mandatory, (C) Conditional or (O)

Optional:

• A mandatory Information Element (marked as (M) in 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 the table) 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 the table) may be present or absent in the command, at the

discretion of the application at the sending entity. Absence or presence of this Information Element shall not

cause an application error and may be ignored by the receiver.
5.1.2 Subscriber profile

Subscriber profile information sent over the e4 interface is structured into two groups: the QoS Profile Information and

the initial gate setting.

Tables 1 and 2 detail the involved information elements as defined in the NASS specification ES 282 004 [1] and their

mapping to DIAMETER AVPs.
Table 1: Initial gate setting
Information Mapping to Category Description
element name Diameter AVP

List of allowed NAS-Filter-Rule O The list of default destination IP addresses, ports, prefixes and

destinations port ranges to which traffic can be sent.

UL Subscribed Maximum-Allowed- O The maximum amount of bandwidth that can be used without

Bandwidth Bandwidth-UL explicit authorization in the uplink direction.

DL Subscribed Maximum-Allowed- O The maximum amount of bandwidth that can be used without

Bandwidth Bandwidth-DL explicit authorization in the downlink direction.
ETSI
---------------------- Page: 9 ----------------------
10 Final draft ETSI ES 283 034 V1.5.0 (2008-01)
Table 2: QoS profile information
Information Mapping to Category Description
element name Diameter AVP

Transport Transport-Class O The transport class applicable to the QoS Profile Information.

service class

Media-Type Media-Type O The media type applicable to the QoS Profile information.

UL Subscribed Maximum-Allowed- O The maximum amount of bandwidth subscribed by the attached

Bandwidth Bandwidth-UL user in the uplink direction.

DL Subscribed Maximum-Allowed- O The maximum amount of bandwidth subscribed by the attached

Bandwidth Bandwidth-DL user in the downlink direction.

Maximum Reservation-Priority O The maximum priority allowed for any reservation request.

Priority

Requestor Application Class ID O Identifies the application class(es) that are allowed to request

Name resources for the QoS profile.
5.2 Procedures on the CLF - A-RACF interface
5.2.1 Access profile push
5.2.1.1 Overview

This procedure is used to push session-related information from the CLF to the A-RACF. This information flow occurs

when an IP address has been allocated to a subscriber or in case a modification occurs on a profile that has already been

pushed to the RACS.

The CLF should push session-related-information to the A-RACF as soon as it is available to the CLF. This may require

the CLF to pull part of the information from other components of the NASS.

For the same subscriber, the CLF may push several independent session records with different IP addresses, with or

without the same logical access identifier.

This procedure is mapped to the commands Push-Notification-Request/Answer in the Diameter application specified in

clause 7. Tables 3 and 4 detail the involved information elements as defined in the NASS specification ES 282 004 [1]

and their mapping to Diameter AVPs.
Table 3: Access profile push
Information Mapping to Diameter Category Description
element name AVP
Globally Unique Globally-Unique-Address M This information element contains:
IP Address - The IP address of the user equipment used by the
subscriber for which profile information is being
pushed.
- The addressing domain in which the IP address is
significant.

Logical Access Logical-Access-Id M The identity of the logical access to which the user

ID equipment is connected.

Access Access-Network-Type O The type of access network over which IP connectivity is

Network Type provided to the user equipment.
Subscriber ID User-Name C The user that is attached to the network (see note).

Physical Physical-Access-Id O The identity of the physical access to which the user

Access ID equipment is connected.
Initial Gate Initial-Gate-Setting O See clause 5.1, table 1.
Setting
QoS Profile QoS-Profile O See clause 5.1, table 2.
NOTE: The Subscriber ID shall be included if available in the CLF.
ETSI
---------------------- Page: 10 ----------------------
11 Final draft ETSI ES 283 034 V1.5.0 (2008-01)
Table 4: Access profile push response
Information Mapping to Diameter AVP Category Description
element name
Result Result-Code / Experimental_ M Result of the request.
Result
Result-Code AVP shall be used for errors defined in the
Diameter Base Protocol.
Experimental-Result AVP shall be used for other errors.
This is a grouped AVP which contains a Vendor-Id AVP,
and the error code in the Experimental-Result-Code
AVP.
5.2.1.2 Procedure at the CLF side

The CLF knows the address of the A-RACF entity where the information should be pushed, either from configuration

data or from the user profile (i.e. received from the UAAF/PDBF).
The CLF shall populate the Access Profile Push as follows:

• The Globally-Unique-Address AVP shall contain a Frame-IP-Address or Frame-IPv6-Prefix AVP value, and

an Address-Realm AVP.
• The Logical-Access-ID AVP shall be present.

The presence of the other AVPs depends on the user profile and local policy rules.

5.2.1.3 Procedure at the A-RACF side

If the Logical Access ID is not included or is invalid, the A-RACF shall return an Access Profile Push response with a

Result-Code AVP value set to DIAMETER_INVALID_AVP_VALUE.

If the globally unique identifier contained in the Globally-Unique-Address AVP is not known, the A-RACF shall:

• Create an internal record to store the received information for future use (i.e. for processing resource

reservation requests received from the SPDF).
• Derive the following information from the Logical Access ID:

- The identification and bandwidth capacity of the layer 2 resources over which the subscriber traffic is

car
...

SLOVENSKI STANDARD
SIST ES 283 034 V1.5.0:2008
01-julij-2008

=OLWHWHOHNRPXQLNDFLMVNHLQLQWHUQHWQHVWRULWYHWHUSURWRNROL]DQDSUHGQRRPUHåHQMH

7,63$1 3RGVLVWHPRPUHåQHSULNOMXþLWYH 1$66 9PHVQLNHQDSRGODJL
SURWRNROD',$0(7(5
Telecommunications and Internet converged Services and Protocols for Advanced

Networking (TISPAN) - Network Attachment Sub-System (NASS) - e4 interface based on

the DIAMETER protocol
Ta slovenski standard je istoveten z: ES 283 034 Version 1.5.0
ICS:
33.040.01 Telekomunikacijski sistemi Telecommunication systems
na splošno in general
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
SIST ES 283 034 V1.5.0:2008 en

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST ES 283 034 V1.5.0:2008
---------------------- Page: 2 ----------------------
SIST ES 283 034 V1.5.0:2008
ETSI ES 283 034 V1.5.0 (2008-04)
ETSI Standard
Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Network Attachment Sub-System (NASS);
e4 interface based on the DIAMETER protocol
---------------------- Page: 3 ----------------------
SIST ES 283 034 V1.5.0:2008
2 ETSI ES 283 034 V1.5.0 (2008-04)
Reference
RES/TISPAN-03124-NGN-R1
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.

3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.

ETSI
---------------------- Page: 4 ----------------------
SIST ES 283 034 V1.5.0:2008
3 ETSI ES 283 034 V1.5.0 (2008-04)
Contents

Intellectual Property Rights................................................................................................................................5

Foreword.............................................................................................................................................................5

1 Scope........................................................................................................................................................6

2 References................................................................................................................................................6

2.1 Normative references.........................................................................................................................................6

2.2 Informative references........................................................................................................................................7

3 Definitions and abbreviations...................................................................................................................7

3.1 Definitions..........................................................................................................................................................7

3.2 Abbreviations.....................................................................................................................................................7

4 Overview..................................................................................................................................................8

5 Procedure descriptions .............................................................................................................................9

5.1 General...............................................................................................................................................................9

5.1.1 Information elements....................................................................................................................................9

5.1.2 Subscriber profile..........................................................................................................................................9

5.2 Procedures on the CLF - A-RACF interface ....................................................................................................10

5.2.1 Access profile push.....................................................................................................................................10

5.2.1.1 Overview...............................................................................................................................................10

5.2.1.2 Procedure at the CLF side .....................................................................................................................11

5.2.1.3 Procedure at the A-RACF side..............................................................................................................11

5.2.2 Access profile pull ......................................................................................................................................12

5.2.2.1 Overview...............................................................................................................................................12

5.2.2.2 Procedure at the A-RACF side..............................................................................................................13

5.2.2.3 Procedure at the CLF side .....................................................................................................................13

5.2.3 IP connectivity release indication ...............................................................................................................14

5.2.3.1 Overview...............................................................................................................................................14

5.2.3.2 Procedure at the CLF side .....................................................................................................................14

5.2.3.3 Procedure at the A-RACF side..............................................................................................................15

6 Use of the Diameter base protocol .........................................................................................................15

6.1 Securing Diameter messages............................................................................................................................15

6.2 Accounting functionality..................................................................................................................................15

6.3 Use of sessions .................................................................................................................................................15

6.4 Transport protocol............................................................................................................................................15

6.5 Routing considerations.....................................................................................................................................16

6.6 Advertising application support .......................................................................................................................16

7 DIAMETER application.........................................................................................................................16

7.1 Commands........................................................................................................................................................16

7.1.1 User-Data-Request command.....................................................................................................................17

7.1.2 User-Data-Answer command......................................................................................................................17

7.1.3 Push-Notification-Request command.........................................................................................................18

7.1.4 Push-Notification-Answer command..........................................................................................................18

7.2 Result-Code AVP values..................................................................................................................................18

7.2.1 Success........................................................................................................................................................19

7.2.2 Permanent failures......................................................................................................................................19

7.2.3 Transient failures........................................................................................................................................19

7.3 AVPs................................................................................................................................................................20

7.3.1 Globally-Unique-Address AVP..................................................................................................................21

7.3.2 Address-Realm AVP...................................................................................................................................21

7.3.3 Logical-Access-ID AVP.............................................................................................................................21

7.3.4 Initial-Gate-Setting AVP............................................................................................................................22

7.3.5 QoS-Profile AVP........................................................................................................................................22

7.3.6 IP-Connectivity-Status AVP.......................................................................................................................22

7.3.7 Access-Network-Type AVP.......................................................................................................................22

ETSI
---------------------- Page: 5 ----------------------
SIST ES 283 034 V1.5.0:2008
4 ETSI ES 283 034 V1.5.0 (2008-04)

7.3.8 Aggregation-Network-Type AVP...............................................................................................................23

7.3.9 Maximum-Allowed-Bandwidth-UL AVP..................................................................................................23

7.3.10 Maximum-Allowed-Bandwidth-DL AVP..................................................................................................23

7.3.11 Reservation-Priority....................................................................................................................................23

7.3.12 Transport-Class...........................................................................................................................................23

7.3.13 Application-Class-ID..................................................................................................................................23

7.3.14 Physical-Access-ID.....................................................................................................................................24

7.3.15 NAS-Port-Type AVP..................................................................................................................................24

7.3.16 NAS-Filter-Rule AVP.................................................................................................................................24

7.3.17 Framed-IP-Address AVP............................................................................................................................24

7.3.18 Framed-IP-Prefix AVP...............................................................................................................................24

7.3.19 Origin-Host AVP........................................................................................................................................24

7.3.20 AF-Application-Identifier AVP..................................................................................................................24

7.3.21 Media-Type AVP........................................................................................................................................24

7.4 Use of namespaces ...........................................................................................................................................24

7.4.1 AVP codes..................................................................................................................................................24

7.4.2 Experimental-Result-Code AVP values......................................................................................................24

7.4.3 Command Code values ...............................................................................................................................24

7.4.4 Application-ID value..................................................................................................................................25

Annex A (informative): Mapping of e4 operations and terminology to Diameter............................26

History ..............................................................................................................................................................27

ETSI
---------------------- Page: 6 ----------------------
SIST ES 283 034 V1.5.0:2008
5 ETSI ES 283 034 V1.5.0 (2008-04)
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
---------------------- Page: 7 ----------------------
SIST ES 283 034 V1.5.0:2008
6 ETSI ES 283 034 V1.5.0 (2008-04)
1 Scope

The present document defines a protocol for use between the TISPAN NGN Network Attachment Sub-System (NASS)

and the Resource and Admission Control Subsystem (RACS), based on Diameter.

The present document is applicable to the e4 interface between the Connectivity Session Location and Repository

Function (CLF) and the RACS.

Whenever it is possible the present document specifies the requirements for this protocol by reference to specifications

produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined

within the present document.
2 References

References are either specific (identified by date of publication and/or edition number or version number) or

non-specific.
• For a specific reference, subsequent revisions do not apply.

• Non-specific reference may be made only to a complete document or a part thereof and only in the following

cases:

- if it is accepted that it will be possible to use all future changes of the referenced document for the

purposes of the referring document;
- for informative references.

Referenced documents which are not found to be publicly available in the expected location might be found at

http://docbox.etsi.org/Reference.

For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,

the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the

reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the

method of access to the referenced document and the full network address, with the same punctuation and use of upper

case and lower case letters.

NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee

their long term validity.
2.1 Normative references

The following referenced documents are indispensable for the application of the present document. For dated

references, only the edition cited applies. For non-specific references, the latest edition of the referenced document

(including any amendments) applies.

[1] ETSI ES 282 004: "Telecommunications and Internet converged Services and Protocols for

Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment
Sub-System (NASS)".

[2] ETSI ES 282 003: "Telecommunications and Internet converged Services and Protocols for

Advanced Networking (TISPAN); Resource and Admission Control Sub-system (RACS);
Functional Architecture".

[3] ETSI TS 129 229: "Digital cellular telecommunications system (Phase 2+); Universal Mobile

Telecommunications System (UMTS); Cx and Dx interfaces based on the Diameter protocol;

Protocol details (3GPP TS 29.229)".

[4] ETSI TS 129 329: "Digital cellular telecommunications system (Phase 2+); Universal Mobile

Telecommunications System (UMTS); Sh interface based on the Diameter protocol; Protocol

details (3GPP TS 29.329)".
ETSI
---------------------- Page: 8 ----------------------
SIST ES 283 034 V1.5.0:2008
7 ETSI ES 283 034 V1.5.0 (2008-04)

[5] ETSI TS 129 209: "Universal Mobile Telecommunications System (UMTS); Policy control over

Gq interface (3GPP TS 29.209)".
[6] IETF RFC 2960: "Stream Control Transmission Protocol".
[7] IETF RFC 3588: "Diameter Base Protocol".

[8] IETF RFC 3309: "Stream Control Transmission Protocol (SCTP) Checksum Change".

[9] IETF RFC 4005: "Diameter Network Access Server application".

[10] IETF RFC 3554: "On the use of Stream Control Transmission Protocol (SCTP) with IPsec".

[11] IETF RFC 3046: "DHCP Relay Agent Information Option".

[12] ETSI TS 183 017: "Telecommunications and Internet Converged Services and Protocols for

Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER protocol for

session based policy set up information exchange between the Application Function (AF) and the

Service Policy Decision Function (SPDF); Protocol specification".
2.2 Informative references
Not applicable.
3 Definitions and abbreviations
3.1 Definitions

For the purposes of the present document, the following terms and definitions apply:

Application Function (AF): element of the service layer architecture offering applications that require information

about the characteristics of the IP-connectivity session used to access such applications

Attribute-Value Pair (AVP): corresponds to an Information Element in a Diameter message

NOTE: See RFC 3588 [7].
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ABNF Augmented Backus-Naur Form
AF Application Function
A-RACF Access-Resource and Admission Control Function
ATM Asynchronous Transfer Mode
AVP Attribute-Value Pair
BGF Border Gateway Function
CLF Connectivity session Location and repository Function
FQDN Fully Qualified Domain Name
IANA Internet Assigned Numbers Authority
ID IDentifier
IETF Internet Engineering Task Force
IPSec IP Security
L2TF Layer 2 Termination Function
NAS Network Access Server
NASS Network Attachment Sub-System
PDBF Profile Data Base Function
PNA Push-Notification-Answer
PNR Push-Notification-Request
ETSI
---------------------- Page: 9 ----------------------
SIST ES 283 034 V1.5.0:2008
8 ETSI ES 283 034 V1.5.0 (2008-04)
RACF Resource and Admission Control Function
RACS Resource and Admission Control Subsystem
RCEF Resource Control Enforcement Function
RFC Request For Comments
SCTP Stream Control Transport Protocol
SPDF Service-based Policy Decision Function
UAAF User Authentication and Authorization Function
UCS Universal Character Set
UDA User-Data-Answer
UDR User-Data-Request
VC Virtual Channel
VP Virtual Path
4 Overview

The Network Attachment Sub-System (NASS), defined in ES 282 004 [1], maintains information about IP-connectivity

associated with user equipment connected to TISPAN networks. This information is stored in the Connectivity Session

Location and Repository Function (CLF) and made accessible to other subsystems and applications through the

following two interfaces (see figure 1):

• The e2 interface enables Application Functions (AF) to retrieve IP-connectivity related session data.

• The e4 interface enables the IP-connectivity related session data to be exchanged between the NASS and the

Resource and Admission Control Subsystem (RACS) defined in ES 282 003 [2].
The present document specifies the protocol for the e4 interface.
Service Control
Subsystems and
Applications
CLF
NASS
Scope of the present
A-RACF
document
RACS
Transfer Functions
Figure 1: NASS external interfaces
ETSI
---------------------- Page: 10 ----------------------
SIST ES 283 034 V1.5.0:2008
9 ETSI ES 283 034 V1.5.0 (2008-04)
5 Procedure descriptions
5.1 General
5.1.1 Information elements

The following clauses describe the realization of the functional procedures defined in the NASS (ES 282 004) [1] and

RACS specifications (ES 282 003 [2]) using Diameter commands described in clause 7. This involves describing a

mapping between the Information Elements defined in the NASS specification (ES 282 004 [1]) and Diameter AVPs.

In the tables that describe this mapping, each Information Element is marked as (M) Mandatory, (C) Conditional or (O)

Optional:

• A mandatory Information Element (marked as (M) in 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 the table) 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 the table) may be present or absent in the command, at the

discretion of the application at the sending entity. Absence or presence of this Information Element shall not

cause an application error and may be ignored by the receiver.
5.1.2 Subscriber profile

Subscriber profile information sent over the e4 interface is structured into two groups: the QoS Profile Information and

the initial gate setting.

Tables 1 and 2 detail the involved information elements as defined in the NASS specification ES 282 004 [1] and their

mapping to DIAMETER AVPs.
Table 1: Initial gate setting
Information Mapping to Category Description
element name Diameter AVP

List of allowed NAS-Filter-Rule O The list of default destination IP addresses, ports, prefixes and

destinations port ranges to which traffic can be sent.

UL Subscribed Maximum-Allowed- O The maximum amount of bandwidth that can be used without

Bandwidth Bandwidth-UL explicit authorization in the uplink direction.

DL Subscribed Maximum-Allowed- O The maximum amount of bandwidth that can be used without

Bandwidth Bandwidth-DL explicit authorization in the downlink direction.
ETSI
---------------------- Page: 11 ----------------------
SIST ES 283 034 V1.5.0:2008
10 ETSI ES 283 034 V1.5.0 (2008-04)
Table 2: QoS profile information
Information Mapping to Category Description
element name Diameter AVP

Transport Transport-Class O The transport class applicable to the QoS Profile Information.

service class

Media-Type Media-Type O The media type applicable to the QoS Profile information.

UL Subscribed Maximum-Allowed- O The maximum amount of bandwidth subscribed by the attached

Bandwidth Bandwidth-UL user in the uplink direction.

DL Subscribed Maximum-Allowed- O The maximum amount of bandwidth subscribed by the attached

Bandwidth Bandwidth-DL user in the downlink direction.

Maximum Reservation-Priority O The maximum priority allowed for any reservation request.

Priority

Requestor Application Class ID O Identifies the application class(es) that are allowed to request

Name resources for the QoS profile.
5.2 Procedures on the CLF - A-RACF interface
5.2.1 Access profile push
5.2.1.1 Overview

This procedure is used to push session-related information from the CLF to the A-RACF. This information flow occurs

when an IP address has been allocated to a subscriber or in case a modification occurs on a profile that has already been

pushed to the RACS.

The CLF should push session-related-information to the A-RACF as soon as it is available to the CLF. This may require

the CLF to pull part of the information from other components of the NASS.

For the same subscriber, the CLF may push several independent session records with different IP addresses, with or

without the same logical access identifier.

This procedure is mapped to the commands Push-Notification-Request/Answer in the Diameter application specified in

clause 7. Tables 3 and 4 detail the involved information elements as defined in the NASS specification ES 282 004 [1]

and their mapping to Diameter AVPs.
Table 3: Access profile push
Information Mapping to Diameter Category Description
element name AVP
Globally Unique Globally-Unique-Address M This information element contains:
IP Address - The IP address of the user equipment used by the
subscriber for which profile information is being
pushed.
- The addressing domain in which the IP address is
significant.

Logical Access Logical-Access-Id M The identity of the logical access to which the user

ID equipment is connected.

Access Access-Network-Type O The type of access network over which IP connectivity is

Network Type provided to the user equipment.
Subscriber ID User-Name C The user that is attached to the network (see note).

Physical Physical-Access-Id O The identity of the physical access to which the user

Access ID equipment is connected.
Initial Gate Initial-Gate-Setting O See clause 5.1, table 1.
Setting
QoS Profile QoS-Profile O See clause 5.1, table 2.
NOTE: The Subscriber ID shall be included if available in the CLF.
ETSI
---------------------- Page: 12 ----------------------
SIST ES 283 034 V1.5.0:2008
11 ETSI ES 283 034 V1.5.0 (2008-04)
Table 4: Access profile push response
Information Mapping to Diameter AVP Category Description
element name
Result Result-Code / Experimental_ M Result of the request.
Result
Result-Code AVP shall be used for errors defined in the
Diameter Base Protocol.
Experimental-Result AVP shall be used for
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.