07 TM32047EN04GLA0 E2 E4 Diameter Prot

e2/e4 Interface - DIAMETER Protocol
Content
1
1.1
1.2
2
2.1
2.2
3
4
Diameter Protocol Functions and Tasks on the e2 Interface

Overview on e2 Interface
e2 Diameter Application specific Procedures
Diameter Protocol Functions and Tasks on the e4 Interface
Exercise
Solution
TM32047EN04GLA0
2011 Nokia Siemens Networks
3
4
6
15
16
18
29
31
TM32047EN04GLA0
Diameter Protocol Functions and Tasks on

the e2 Interface
TM32047EN04GLA0
1.1
The Network Attachment Sub-System (NASS) maintains information about IPconnectivity access sessions, e.g. network location information, associated with user
equipment which is connected to the TISPAN network. This information is stored in
the Connectivity Session Location and Repository Function (CLF) and made
accessible to other subsystems and applications through the e2 interface. The
primary parameter to retrieve the location information is the assigned IP address
allocated to the UE. The form of network location information that is provided by the
CLF depends on the requestor.
Note: The e2 interface is not required when connected to a 3GPP IP-CAN.
The Application Function (AF) is a generic term representing any element of the
service layer architecture offering applications that require information about the
characteristics of the IP-connectivity session used to access such applications, e.g.
the P-CSCF in the IMS or the IBCF.
The Connectivity session Location and repository Function (CLF) holds a
number of records representing active sessions. These records contain information
received from the NACF and the UAAF, and additional statically configured data. The
CLF registers:
association between the IP address allocated to the UE and related network

location information provided by the NACF, i.e. access transport equipment
characteristics, line identifier (Logical Access ID), IP Edge identity, etc. The IP
edge is where the end-user session is terminated, and provides the first policy
enforcement point at the IP layer, e.g. a B-RAS in the DSL environment.
network location information received from the NACF and geographical location
information.
may store the identity of the user/UE to which the IP address has been allocated
(information received from the UAAF).
may store the user network QoS profile and user preferences regarding the
privacy of location information.
The actual information delivered by the CLF may take various forms (e.g. network
location, geographical coordinates, post mail address etc.), depending on
agreements with the requestor and on user preferences regarding the privacy of its
location.
The CLF registers also user network profile information (received from the UAAF at
authentication) to make this profile information available to the RACS at
authentication of the UE.
TM32047EN04GLA0
Service Control
Subsystems and
Applications
AF
e2
CLF
e4
NASS
A-RACF
RACS
Transfer Functions
Fig. 1 Location of e2 Interface.
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
TM32047EN04GLA0
2011
. Nokia
. .Siemens
. .Networks
. .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1.2
The e2 interface protocol is defined as an ETSI TISPAN vendor specific Diameter

application, where the vendor is ETSI. The vendor identifier assigned by IANA to
ETSI is 13019. The Diameter application identifier assigned to the e2 interface
application is 16777231 (allocated by IANA).
On the e2 interface between CLF and AF the e2 Diameter Application is used. This
application provides currently the following functions:
Information Query The Information Query procedure is used by an AF to retrieve
from the CLF location information and other data related to an
access session.
Event
Registration/Dere
gistration
The Event Registration/Deregistration procedure is used by an

AF to subscribe with the CLF to a particular event.
Notification
Events
The Notification Events procedure is used by a CLF to notify the

AF of the occurrence of a particular event.
TM32047EN04GLA0
e2 Diameter Application Functions

Information Query
Event Registration/Deregistration
Notification Events
e2 Diameter Application
Diameter (Base)
SCTP
IP
AF
CLF
e2
Fig. 2 e2 Diameter Application Functions
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
TM32047EN04GLA0
2011
. Nokia
. .Siemens
. .Networks
. .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1.2.1
Information Query Procedure
The Information Query Procedure is used by an AF to retrieve from the CLF

network location information and other data related to an access session. Due to
operator's policies and subscriber privacy rules, the session data returned may be a
subset of the requested session data.
This procedure is mapped to the commands User-Data-Request/Answer in the
Diameter application specified in TS 129 329 (Sh Interface).
The Information Query Request message contains the following parameters:
Either the Globally-Unique-Address, e.g. IP address and addressing domain of the

user equipment used by the subscriber for which the profile info is requested or
the User-Name of the user that is attached to the network.

The AF Identity that identifies the AF originating the request.
Requested-Information which is the list of information requested by the AF, e.g.
User name, Location-Information, RACS-Contact-Point, Access-Network-Type,
Terminal-Type.
The Requested-Information parameter has to be present only if specific information is
requested and is absent if all available information is requested.
The Information Query Response message contains the following:
The Result Code.

optional the User-Name of the user that is attached to the network.
optional the Location information (or a pointer to such information) in a form that is
suitable for the requesting application.
optional RACS contact point which is the FQDN or the IP address of the RACS
entity where the resource request is sent (i.e. SPDF address).
optional the type of access network over which IP connectivity is provided to the
user equipment.
optional the type of user equipment to which the IP address was allocated.
If both the Globally-Unique-Address and the User-Name are absent, an Information
Query response with Result-Code set to Diameter_Missing_AVP is returned.
If more than one record include the same subscriber identity matching the value of
the User-Name and no Globally-Unique-Address is included, an Information Query
response with Result-Code set to Diameter_Unable_To_Comply is returned.
If no session record is stored for the Globally-Unique-Address or the User-Name, an
Information Query response with the Experimental-Result-Code set to
Diameter_Error_User_Unknown is returned.
TM32047EN04GLA0
Under temporary overload conditions, the CLF stops processing the request and
return an Information Query response with the Experimental-Result-Code set to
Diameter_User_Data_Not_Available.
If the CLF cannot fulfill the received request for reasons not stated in the above
steps, e.g. due to database error, it stops processing the request and set the ResultCode to Diameter_Unable_To_Comply.
Otherwise, the requested operation takes place and the CLF returns the Result-Code
set to Diameter_Success and the session data in the Information Query response.
AF
CLF
Information-Query-Request
(globally unique address or user name, AF Id, requested information )
Information-Query-Response
(result code, requested information: user name, access network type, location info,
RACS contact point, terminal type)
Fig. 3 Information Query Procedure
TM32047EN04GLA0
1.2.2
Event Registration/Deregistration
The Event Registration/Deregistration procedure is used by an AF to subscribe

with the CLF to a particular event related to access sessions.
This procedure is mapped to the commands Subscribe-Notifications-Request/Answer
defined in the Diameter application specified in TS 129 329 (Sh interface).
Subscription to an event terminates when one of the following conditions is met:
Expiry of the subscription duration.

Removal of the session record from the CLF.
Receipt of an explicit request to unsubscribe.
The Event Registration/Deregistration Request contains the following:
Subs-Req-Type AVP indicating whether to subscribe or unsubscribe to the

notification of events.
Either the User Name or a Globally-Unique-Address (IP address + realm).

The AF-Application-Identifier to identify the AF originating the request.
At least one occurrence of the type of event to be monitored.
Optionally the requested Subscription Expiration Time.
The Event Registration/Deregistration Response contains the following:
Result Code
Optionally the Expiry Time which acknowledges the absolute time at which the
subscription expires. No Expiry time indicates an unlimited subscription and no
notification is sent to the AF after the expiration time.
Based on the contents of the AF-Application-Id the CLF checks whether the AF is
allowed to request monitoring of events. If not, it returns an Event Registration
Response with Result-Code "DIAMETER_ERROR_OPERATION_NOT_ALLOWED".
If neither the Globally-Unique-Address nor the User Name is present the CLF returns
an Registration Response with Result-Code "DIAMETER_MISSING_AVP".
If no stored session record matches the Globally-Unique-Address or the User name
the CLF returns an Event Registration Response with the Result-Code set to
"DIAMETER_ERROR_USER_UNKNOWN."
If the Subs-Req-Type indicates that it is a request to subscribe to the notification of
events, the CLF checks whether the requested event can be reported to the AF,
based on local policy rules and per-NASS User privacy information received from the
UAAF. If the AF is not allowed to request monitoring of the event, it returns an Event
Registration Response with Result-Code "DIAMETER_ERROR_OPERATION_NOT_
ALLOWED".
If the AF is allowed to request monitoring of the event, the CLF returns an Event
Registration Response with Result Code " DIAMETER_SUCCESS".
10
TM32047EN04GLA0
If the Subs-Req-Type indicates that it is a request to unsubscribe to the notification of

events, the CLF removes the association of the AF-Identifier of its internal list. If the
Event-Type is absent, the CLF assumes that the AF is wants to unsubscribe to all
events associated with the User. The CLF returns an Event Deregistration Response
with Result-Code "DIAMETER_SUCCESS ".
If a subsequent request is received by the CLF where the Expiry Time is present but
different from what the CLF has previously stored, the CLF replaces the stored
expiration time with what was received in the request.
If the CLF cannot fulfill the received request for reasons not stated in the above, e.g.
due to database error, it stops processing the request and returns an Event
Registration Response with Result-Code " DIAMETER_UNABLE_TO_COMPLY".
AF
CLF
Event-Registration/Deregistration-Request
(globally unique address or user name, subs-req-type, AF Id, event-type(s),
opt. expiry timer)
Event-Registration/Deregistration-Response
(result code, opt. expiry timer)
Fig. 4 Event Registration/Deregistration
TM32047EN04GLA0
11
1.2.3
Notification Events
The Notification Events procedure is used by a CLF to notify the AF of the

occurrence of a particular event.
This procedure is mapped to the commands Push-Notifications-Request/Answer in
the Diameter application specified in TS 129 329 (Sh interface).
The Notification Event Request contains the following:
Either the User Name or a Globally-Unique-Address (IP address + realm).

The AF-Application-Identifier to identify the AF having registered to the request.
The type of event(s) which occurred.
Optionally AVPs carrying CLF information associated to the reported event.
The Notification Event Response contains the following:
Result Code
When a monitored event is detected on a particular access session, the CLF issues a
Notification Event Request to each of the application functions having registered to
this event. Based on local policy rules and per-NASS User privacy information
previously received from the UAAF, the CLF may also include additional information
in the Notification Event Request.
If neither the Globally-Unique-Address nor the User-Name received in the Notification
Event Request are known, the AF returns a Notification Event Response with ResultCode "DIAMETER_ERROR_USER_UNKNOWN".
If the event type is not known, the AF returns a Notification Event Response with
Result-Code "DIAMETER_INVALID_AVP_VALUE".
If the event type is known but was not expected, the AF returns a Notification Event
Response with Result-Code "DIAMETER_ERROR_NO_SUBSCRIPTION_TO_
DATA.
If the AF cannot process the event for reasons not stated in the above the AF returns
a Notification Event Response with Result-Code "DIAMETER_UNABLE_TO_
COMPLY" or "DIAMETER_SYSTEM_UNAVAILABLE". In the later case, the CLF is
expected to retry after a provisioned time period. After a provisioned number of
unsuccessful retries, the CLF is expected to delete the AF-Identity from the list of
application functions registered to the event. Otherwise, if the event can be
processed by the AF the AF returns the Result-Code "DIAMETER_SUCCESS" in the
Notification Event Response.
12
TM32047EN04GLA0
AF
CLF
Notification-Event-Request
(globally unique address or user name, AF Id, event-type(s),
opt. information associated to the reported event )
Notification-Event-Response
(result code)
Fig. 5 Event Notification Procedure
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
TM32047EN04GLA0
. . . . . . .
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
13
14
TM32047EN04GLA0
Diameter Protocol Functions and Tasks on

the e4 Interface
TM32047EN04GLA0
15
2.1
The Network Attachment Sub-System (NASS) maintains information about IPconnectivity access sessions associated with user equipment which is connected to
the TISPAN network. This information is stored in the Connectivity Session Location
and Repository Function (CLF) and made accessible to other subsystems and
applications through the e4 interface.
The e4 interface allows the RACS to retrieve network location information from the
CLF (e.g. the address of the physical node through which the user can be reached) in
order to determine the amount of available network resources. The e4 interface also
allows the RACS to retrieve user network profile information from the CLF in order to
take them into account when processing resource allocation requests:
The CLF informs the Access-Resource and Admission Control Function (ARACF) via the e4 interface when a subscriber attaches to the network. The CLF
sends network attachment information and the subscriber access profile information
to the A-RACF. The A-RACF also interfaces with the SPDF (Rq interface). Based on
the SPDF requests and policy information stored in the A-RACF, the A-RACF may
accept or reject the requests for the transport resources. When a resource request is
received from the SPDF, based on the Subscriber Id and/or the IP address, the ARACF identifies the subscriber access profile previously received from the NASS.
The subscriber access profile received from the CLF consist of:
Subscriber attachment info: Subscriber ID, Physical Access ID, Logical Access ID,
Access Network Type and
Globally Unique IP Address;

QoS Profile Information (optional): Transport Service Class, UL Subscribed
Bandwidth, DL Subscribed
Bandwidth, Maximum Priority, Media Type and Requestor Name. The QoS Profile
may contain one or more sets of information elements;
Initial Gate Setting (optional): List of Allowed Destinations, UL Default Bandwidth,

DL Default Bandwidth.
On the other hand, the SPDF provides the following information that is relevant to ARACF procedures when it receives a request:
Subscriber Id or IP address;
Requestor Name/Service Class;
Media Description;
Service Priority.
The Physical Access ID, Logical Access ID and Access Network Type allows ARACF to bind the Subscriber Id and/or its IP address to the topology information of
the access and aggregation networks hosted in A-RACF.
16
TM32047EN04GLA0
Service Control
Subsystems and
Applications
AF
e2
CLF
Gq
e4
NASS
SPDF
Rq
A-RACF
RACS
Transfer Functions
Fig. 6 Location of e4 Interface.
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
TM32047EN04GLA0
. . . . . . .
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
17
2.2
The e4 interface protocol is defined as an ETSI TISPAN vendor specific Diameter

application, where the vendor is ETSI. The vendor identifier assigned by IANA to
ETSI is 13019. The Diameter application identifier assigned to the e4 interface
application is 16777231 (allocated by IANA).
On the e4 interface between CLF and AF the e4 Diameter Application is used. This
application provides currently the following functions:
Access Profile
Push
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.
Access Profile
Pull
The Access Profile Pull procedure is used by the RACS to

request the Access Profile information from the RACS (e.g. in
the context of recovery procedures).
The IP Connectivity Release Indication procedure is used by

IP Connectivity
Release Indication the NASS to report loss of IP connectivity. This enables the
RACS to remove the access profile from its internal data base.
18
TM32047EN04GLA0
e4 Diameter Application Functions

Access Profile Push
Access Profile Pull
IP Connectivity Release Indication
e4 Diameter Application
Diameter (Base)
SCTP
IP
CLF
A-RACF
e4
Fig. 7 e4 Diameter Application Functions
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
TM32047EN04GLA0
. . . . . . .
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
19
2.2.1
Subscriber Profile exchanged on e4
The Subscriber Profile Information sent over the e4 interface is structured into two
groups:
the QoS Profile Information and

the Initial Gate Setting.
20
TM32047EN04GLA0
QoS Profile Information
Initial Gate Setting
Fig. 8 Subscriber Profile Information exchanged on e4
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
TM32047EN04GLA0
2011
. Nokia
. .Siemens
. .Networks
. .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
21
2.2.2
Access Profile Push Procedure
The Access Profile Push procedure is used to push session-related information from
the CLF to the A-RACF in case 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.
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
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 Access Profile Push contains the Globally-Unique-Address AVP,
i.e. the IP-Address with an Address-Realm AVP and also the Logical-Access-ID AVP.
The presence of the other AVPs depends on the user profile and local policy rules.
At the A-RACF if the Logical Access ID is not included or is invalid, the A-RACF
returns an Access Profile Push response with a Result-Code AVP value set to
Diameter_Invalid_AVP_Value.
If the Globally-Unique-Address in the Access Profile Push Request is not known, the
A-RACF will:
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
carried and the address of the physical node(s) implementing the BGF, L2TF and
RCEF.
enforce the policy information if received in the Initial Gate Settings AVP which
may involve interacting with the RCEF through the Re interface.
If the Globally-Unique-Address in the Access Profile Push Request is already known,
the A-RACF will:
Replace the entire content of the internal record with the received information for
future use.
Enforce the new policy information if received in the Initial Gate Settings AVP
which may involve interacting with the RCEF through the Re interface. Such an
update shall not have any impact on ongoing application sessions for which an
authorization has already been provided by the A-RACF.
If the creation or modification of the session record is successful but a failure occurs
during the processing of the Initial Gate Settings (e.g. due to a failure in the
interaction with the RCEF), the A-RACF returns an Access Profile Push response
with a Result-Code AVP value set to Diameter_Limited_Success.
If the A-RACF cannot fulfill the received request for any other reasons, e.g. due to
database error, it stops processing the request and return an Access Profile Push
response with a Result-Code AVP value set to Diameter_unable_To_Comply or
Diameter_System_Unavailable. In the later case, the CLF is expected to retry after a
provisioned time period.
22
TM32047EN04GLA0
A-RACF
CLF
Access-Profile-Push-Request
(globally unique ip address or user name, logical access id, access-network-type, initialgate-setting, QoS profile )
Access-Profile-Push-Response
(result code)
Fig. 9 Access Profile Push Procedure
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
TM32047EN04GLA0
. . . . . . .
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
23
2.2.3
Access Profile Pull Procedure
The Access Profile Pull procedure is used by the RACS to request the Access Profile
information from the CLF in case of recovery situations, i.e. the procedure is used
after a restart, upon reception of the resource reservation request associated with an
IP-Address for which no record is stored.
This procedure is mapped to the commands User-Data-Request/Answer in the
The Access Profile Pull Request contains the User-Name AVP or the GloballyUnique-Address AVP. The Globally-Unique-Address has to be included in
configurations where more than one IP address may be assigned per subscriber
identifier. The Globally-Unique-Address AVP contains an IP-Address AVP and an
Address-Realm AVP.
Upon reception of the Access Profile Pull request, the CLF will do the following:
If present, use the Globally-Unique-Address AVP, else use the User-Name AVP as
a key to retrieve the requested session information.
If both the Globally-Unique-Address AVP and the User-Name AVP are absent,
return an Access Pull Profile Rsp. with Result-Code set to Diameter_Missing_AVP.
If more than one record include the same subscriber identity matching the value of
the User-Name AVP and no Globally-Unique-Address AVP is included, return an
Access Pull Profile Rsp. with Result-Code set to Diameter_Unable_To_Comply.
If no session record is stored for the Globally-Unique-Address AVP or the UserName AVP, return an Access Pull Profile Rsp. with Result-Code set to
Diameter_Error_User_Unknown.
If a unique subscriber record can be retrieved, the CLF checks:
which session data can be returned to the A-RACF, based on local policy rules
and per-subscriber privacy information stored in the CLF.
whether the session data to be retrieved is currently being updated by another

entity. If there is an update in progress, the CLF delays the response message
until the update has been completed and includes the updated data.
If the CLF cannot fulfill the received Access Profile Pull request for any other
reasons, e.g. due to database error, it stops processing the request and set ResultCode to Diameter_Unable_To_Comply or to Diameter_User_Data_Not_Available.
24
TM32047EN04GLA0
A-RACF
CLF
Access-Profile-Pull-Request
(globally unique ip address or user name, A-RACF-id)
Access-Profile-Pull-Response
(globally unique ip address, logical access id, access-network-type, initial-gate-setting,
QoS profile )
Fig. 10 Access Profile Pull Procedure
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
TM32047EN04GLA0
. . . . . . .
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
25
2.2.4
IP Connectivity Release Indication Procedure
The IP Connectivity Release Indication Procedure is used by the CLF to report loss
of IP connectivity. This enables the A-RACF to remove the access profile from its
internal data base. Loss of IP connectivity occurs in case the allocated IP address is
released (e.g. DHCP leased timer expiry) or due to a release of the underlying layer 2
resources.
The IP Connectivity Release Indication Procedure is mapped to the commands PushNotification-Request/Answer in the Diameter application specified in TS 129 329 (Sh
Interface).
On receipt of an external event indicating that the allocated IP address has been
released or the underlying layer 2 connection has been lost, the CLF clears all
information stored against the IP address and issues a Push-Notification-Request
representing an IP-Connectivity-Release-Indication with the IP-Connectivity-Status
AVP set to the value IP-CONNECTIVITY-LOST.
NOTE: Receipt of an indication that a layer 2 connection has been lost may lead the
CLF to issue several notifications, in case multiple access sessions where associated
with this connection.
If the identifier contained in the Globally-Unique-Address AVP is not yet known, the
A-RACF stops processing the request and sets the Result-Code to
Diameter_Error_User_unknown in the IP Connectivity Release Indication Response.
If the identifier contained in the Globally-Unique-Address AVP is already known, the
A-RACF does the following:
remove the existing session record;

interact with transfer layer entities (i.e. RCEF) to remove transport policies
associated with the session and
clear associated resources;

notify the SPDF.
If the A-RACF cannot fulfill the received request for any other reasons, e.g. due to
database error, it stops processing the request and returns an IP-ConnectivityRelease Response with a Result-Code AVP value set to
Diameter_unable_To_Comply or Diameter_System_Unavailable. In the later case,
the CLF is expected to retry after a provisioned time period.
26
TM32047EN04GLA0
A-RACF
CLF
IP-Connectivity-Release-Indication
(globally unique ip address, opt. user name, IP-Connectivity
Status)
IP-Connectivity-Release-Response
(result code)
Fig. 11 IP Connectivity Release Indication Procedure
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
TM32047EN04GLA0
. . . . . . .
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
27
28
TM32047EN04GLA0
Exercise
Exercise
Title:
DIAMETER on e2 and e4 Interfaces.
Query
1. Between which NGN architecture entities is the e2 interface located?
3. What are the main tasks of the e2 interface?
TM32047EN04GLA0
29
30
TM32047EN04GLA0
Solution
Solution
Title:
DIAMETER on e2 and e4 Interfaces.
Query
Between AF und CLF:
Between CLF and A-RACF.
The e2 interface is used by an AF to retrieve from the CLF network location
information and other data related to an access session..
The e4 interface allows the RACS to retrieve network location information from the
CLF (e.g. the address of the physical node through which the user can be
reached) in order to determine the amount of available network resources. The e4
interface also allows the RACS to retrieve user network profile information from the
CLF in order to take them into account when processing resource allocation
requests.
TM32047EN04GLA0
31
32
TM32047EN04GLA0

07 TM32047EN04GLA0 E2 E4 Diameter Prot

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

07 TM32047EN04GLA0 E2 E4 Diameter Prot

Uploaded by

Copyright:

Available Formats

e2/e4 Interface - DIAMETER Protocol

e2/e4 Interface - DIAMETER Protocol

Diameter Protocol Functions and Tasks on the e2 Interface

e2/e4 Interface - DIAMETER Protocol

e2/e4 Interface - DIAMETER Protocol

Diameter Protocol Functions and Tasks on

e2/e4 Interface - DIAMETER Protocol

association between the IP address allocated to the UE and related network

e2/e4 Interface - DIAMETER Protocol

Fig. 1 Location of e2 Interface.

e2/e4 Interface - DIAMETER Protocol

e2 Diameter Application specific Procedures

The e2 interface protocol is defined as an ETSI TISPAN vendor specific Diameter

The Event Registration/Deregistration procedure is used by an

The Notification Events procedure is used by a CLF to notify the

e2/e4 Interface - DIAMETER Protocol

e2 Diameter Application Functions

Fig. 2 e2 Diameter Application Functions

e2/e4 Interface - DIAMETER Protocol

Information Query Procedure

The Information Query Procedure is used by an AF to retrieve from the CLF

Either the Globally-Unique-Address, e.g. IP address and addressing domain of the

the User-Name of the user that is attached to the network.

The Result Code.

e2/e4 Interface - DIAMETER Protocol

Fig. 3 Information Query Procedure

e2/e4 Interface - DIAMETER Protocol

The Event Registration/Deregistration procedure is used by an AF to subscribe

Expiry of the subscription duration.

Subs-Req-Type AVP indicating whether to subscribe or unsubscribe to the

Either the User Name or a Globally-Unique-Address (IP address + realm).

The Event Registration/Deregistration Response contains the following:

e2/e4 Interface - DIAMETER Protocol

If the Subs-Req-Type indicates that it is a request to unsubscribe to the notification of

Fig. 4 Event Registration/Deregistration

e2/e4 Interface - DIAMETER Protocol

The Notification Events procedure is used by a CLF to notify the AF of the

Either the User Name or a Globally-Unique-Address (IP address + realm).

The Notification Event Response contains the following:

e2/e4 Interface - DIAMETER Protocol

Fig. 5 Event Notification Procedure

e2/e4 Interface - DIAMETER Protocol

e2/e4 Interface - DIAMETER Protocol

Diameter Protocol Functions and Tasks on

e2/e4 Interface - DIAMETER Protocol

Globally Unique IP Address;

Initial Gate Setting (optional): List of Allowed Destinations, UL Default Bandwidth,

e2/e4 Interface - DIAMETER Protocol

Fig. 6 Location of e4 Interface.

e2/e4 Interface - DIAMETER Protocol

e4 Diameter Application specific Procedures

The e4 interface protocol is defined as an ETSI TISPAN vendor specific Diameter

This procedure is used to push session-related information from

The Access Profile Pull procedure is used by the RACS to

The IP Connectivity Release Indication procedure is used by

e2/e4 Interface - DIAMETER Protocol

e4 Diameter Application Functions

Fig. 7 e4 Diameter Application Functions

e2/e4 Interface - DIAMETER Protocol

Subscriber Profile exchanged on e4

the QoS Profile Information and

e2/e4 Interface - DIAMETER Protocol

QoS Profile Information