ng_dnas_app_ifd

7/27/2019 ng_dnas_app_ifd

http://slidepdf.com/reader/full/ngdnasappifd 1/23



2 Interface Description

DN09106383 Issue 1-1

Diameter Network Access Server Application

Id:0900d8058093045d

The information in this document is subject to change without notice and describes only the

product defined in the introduction of this documentation. This documentation is intended for the

use of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted

in any form or means without the prior written permission of Nokia Siemens Networks. The

documentation has been prepared to be used by professional and properly trained personnel,

and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes

customer comments as part of the process of continuous development and improvement of the

documentation.

The information or statements given in this documentation concerning the suitability, capacity,

or performance of the mentioned hardware or software products are given "as is" and all liability

arising in connection with such hardware or software products shall be defined conclusively and

finally in a separate agreement between Nokia Siemens Networks and the customer. However,

Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions

contained in the document are adequate and free of material errors and omissions. Nokia

Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which

may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO

EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-

TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-

RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED

TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY

OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION

IN IT.

This documentation and the product it describes are considered protected by copyrights and

other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark

of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respectiveowners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2013/8/21. All rights reserved

f Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sources

of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle

this product and only after having carefully read the safety information applicable to this

product.

The safety information is provided in the Safety Information section in the “Legal, Safety

and Environmental Information” part of this document or documentation set.

The same text in German:

f Wichtiger Hinweis zur ProduktsicherheitVon diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder

andere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch

geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-

anforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal,

Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-

satzes.



Interface Description

DN09106383 Issue 1-1

3


Id:0900d8058093045d

Table of ContentsThis document has 23 pages.

1 Changes in Flexi NG Diameter Network Access Server Application. . . . 71.1 Changes between release 2.0 and release 2.1 . . . . . . . . . . . . . . . . . . . . 7

2 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.1 Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.2 Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3 Overview of S6b interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

4 Message flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

5 S6b AVPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

5.1 Authentication-Authorization-Request . . . . . . . . . . . . . . . . . . . . . . . . . . 13

5.2 Authentication-Authorization-Answer. . . . . . . . . . . . . . . . . . . . . . . . . . . 15

5.3 Session-Termination-Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

5.4 Session-Termination-Answer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

5.5 Abort-Session-Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

5.6 Abort-Session-Answer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

6 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

7 Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23




DN09106383 Issue 1-1


Id:0900d8058093045d

List of FiguresFigure 1 Authentication through AAA message . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Figure 2 P-GW initiated session termination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Figure 3 3GPP AAA server initiated session termination . . . . . . . . . . . . . . . . . . . 11




DN09106383 Issue 1-1

5


Id:0900d8058093045d

List of TablesTable 1 Message headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Table 2 Description of columns in AVP tables . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Table 3 Authentication-Authorization-Request sent by Flexi NG . . . . . . . . . . . . 13

Table 4 Authentication-Authorization-Answer received by Flexi NG . . . . . . . . . 15

Table 5 Session-Termination-Request sent by Flexi NG . . . . . . . . . . . . . . . . . . 17

Table 6 Session-Termination-Answer received by Flexi NG . . . . . . . . . . . . . . . 19

Table 7 Abort-Session-Request received by Flexi NG . . . . . . . . . . . . . . . . . . . 19

Table 8 Abort-Session-Answer sent by Flexi NG . . . . . . . . . . . . . . . . . . . . . . . . 20




DN09106383 Issue 1-1


Id:0900d8058093045d




DN09106383 Issue 1-1

7

Diameter Network Access Server Application Changes in Flexi NG Diameter Network Access Server Application

Id:0900d805809305ae

1 Changes in Flexi NG Diameter Network

Access Server Application

1.1 Changes between release 2.0 and release 2.1

Changes between issues 1-0 and 1-1

Chapter Overview of S6b interface:

• removed reference about mobility-related authentication

• removed reference about retrieval of specific subscription-related parameters

• removed reference of DSMIPv6 based on S2c

• removed reference about retrieval and update of mobility-related parameters

Chapter Meesage flows: updated 3GPP AAA server initiated session termination figure.

Chapter S6b AVPs: new tables introduced, based on the "per-msg restructuring" logic

for the supported AVPs.

Chapter References: updated link for “3GPP TS29.273” specification.

Changes in issue 1-0

This is the first issue of the document.




DN09106383 Issue 1-1


Id:0900d805809014ab

About this document

2 About this documentThis document provides information on the S6b interface in Nokia Siemens Networks

Flexi Network Gateway (Flexi NG).

S6b implementation of Flexi NG is mostly based on 3GPP TS 29.273 [1] and the

relevant IETF RFCs (RFC 4005 [2] and RFC 5447 [3]).

2.1 Scope

This document includes the S6b reference point related functionalities supported by

Flexi NG, the description of the supported messages and the list of AVPs included in

each message. Functionalities that are described in 3GPP specifications, are only

briefly mentioned in this document.

2.2 AudienceThis document is aimed at operators and administrators working with S6b interface of

Flexi NG. The reader should have basic knowledge of Flexi NG, EPS architecture,

internet networks, and Diameter protocol.




DN09106383 Issue 1-1

9

Diameter Network Access Server Application Overview of S6b interface

Id:0900d8058093045e

3 Overview of S6b interfaceThe S6b reference point is located between the P-GW and the 3GPP AAA server (3GPP

authentication, authorization and accounting server) or between the P-GW and the

3GPP AAA proxy server (for roaming cases with P-GW in the visited network).

The S6b interface is used when the UE attaches over a trusted or un-trusted non-3GPP

access, for example, CDMA.

The S6b interface informs the 3GPP AAA server either about the current P-GW identity

and the APN being used by a given UE, or that a specific P-GW and APN pair is no

longer used (for example, when the P-GW connection is established or closed).

The above functionality is common for all mobility protocols that can be used when the

UE attaches through a non-3GPP access (for example, PMIPv6 based on S2a or S2b,

Mobile IPv4 based on S2a).

When the UE attaches to the EPC using the S2a reference point in the PMIPv6 mode,

the S6b reference point is used to update the 3GPP AAA server or the 3GPP AAA proxy

with the P-GW address information.

In Flexi NG, the S6b interface is used during the PDN connection establishment proce-

dure in order to authenticate and authorize a UE that requests such a connection

through the S2a/S2b interface between the P-GW and a non-3GPP IP access.

Flexi NG can communicate through S6b interface only when it is in either P-GW or

combined S-GW/P-GW mode.




DN09106383 Issue 1-1


Id:0900d805809305ad

Message flows

4 Message flowsAAR/AAA

The S6b application in Flexi NG uses an Authentication Authorization Request (AAR)message to create a session towards the 3GPP AAA server, to request authentication

and authorization information and to transfer mobility-related information.

The AAR message carries information regarding the mobile user identity and the P-GW

identity and capabilities. The 3GPP AAA server replies using an Authentication Autho-

rization Answer (AAA) message, indicating the authentication and/or authorization

result.

Figure 1 Authentication through AAA message

STR/STA

The S6b reference point allows the P-GW to inform the 3GPP AAA server that the UE

disconnected a PDN connection associated to an APN and therefore the mobilitysession established for this PDN connection is to be removed.

P-GW initiates the procedure by sending a Session Termination Request (STR)

message towards the 3GPP AAA server. Each PDN connection is identified by the

Diameter Session-Id parameter.

When 3GPP AAA server sends Session Termination Answer (STA) message to P-GW,

the P-GW (regardless of the Result Code AVP) releases the context associated to the

active session identified by the Session-Id parameter used in the initial authorization

exchange.

Figure 2 P-GW initiated session termination




DN09106383 Issue 1-1

11

Diameter Network Access Server Application Message flows

Id:0900d805809305ad

ASR/ASA

The 3GPP AAA server can request the termination of a session by sending an Abort

Session Request (ASR) message to P-GW.

The P-GW responds to the 3GPP AAA server with an Abort Session Answer (ASA)message, including the result code corresponding to the requested action.

Figure 3 3GPP AAA server initiated session termination




DN09106383 Issue 1-1


Id:0900d80580930537

S6b AVPs

5 S6b AVPsThis chapter shows the AVPs that are supported by the S6b application of Flexi NG. The

AVPs, their data types and the handling of unknown AVPs are implemented as specified

in the 3GPP specification TS 29.273 [1].

The attributes defined in this chapter comply with the attribute formats and message

structures given in 3GPP TS 29.273 [1].

Flags R(equest), P(roxiable)

Code 265

Application-ID 3GPP S6b (16777272)

Table 1 Message headers

Column Meaning

AVP (code) Contains the AVP name, and in parenthesis the AVP

code or vendor/code, as well as bits and flag informa-

tion. The following flags are possible:

• M (Mandatory)

• V (Vendor)

Type and content Contains the AVP type and description.

Table 2 Description of columns in AVP tables




DN09106383 Issue 1-1

13

Diameter Network Access Server Application S6b AVPs

Id:0900d80580930537

5.1 Authentication-Authorization-Request

AVP (code) Type and content

Session-Id (263M) UTF8String. Session-Id in string format:

<host>;<session creation time>;<internal session

sequence number>. For example: gatewayservice7-10-

0.NG1.nokiasiemensnetworks.com;84734828 3;1.

The <host> is 16 to 256 characters, for example

'nodeID.hostname '. The minimum value is 16 because of the

recovery group prefix ('gatewayserviceX-Y ').

The <session creation time> specifies the DIAMETER

session creation time in seconds from epoch (1 Jan 1970). It is

always 10 digits assuming the system clock has the correct time.

The <internal session sequence number> is 1 to 10digits.

When the field separators (';') are included in the count, the the-

oretical minimum size is 16 bytes, and the theoretical maximum

size is 278.

Note that the above description is provided for operator informa-

tion and represents the current situation only. The content and

format of the Session-Id AVP may be changed in later releases

or change deliveries without warning, therefore servers are

instructed not to extract parts or otherwise parse the content of

this AVP in order to retain future compatibility.

Auth-Application-

Id (258M)

Unsigned32. Contains the value 16777272 to indicate that 3GPP

S6b is used.

Table 3 Authentication-Authorization-Request sent by Flexi NG




DN09106383 Issue 1-1


Id:0900d80580930537

S6b AVPs

Origin-Host

(264M)

DiameterIdentity. The host name of the 3GPP S6b node in Flexi

NG where the request originated, as seen by AAA server.

A different value can be configured for every diameter server.

The origin host name is constructed by prefixing the configured

host name with the name of the node.

The host name is configured as part of diameter profile.

Example:

my.configuration.in.dia.server.com

The node name is not configurable, and it corresponds to the

Flexi NG recovery group that originated the message.

Example:

gatewayservice7-10-0 : corresponds to recovery groupgateway service with nodes 7-0 and 10-0 working in active-

standby mode. For more information, see Recovery group roles

and naming in Flexi NG User Guide.

Flexi NG has 2 independent nodes per service blade (0 and 1).

Example:

gatewayservice7-10-

1.my.configuration.in.dia.server.com

Origin-Realm

(296M)

DiameterIdentity. A different value can be configured for every

diameter server.

Example:

nokiasiemensnetworks.com

If the Flexi NG host name is configured to contain only a single

word without any dots, this AVP is left empty.

Destination-

Realm (283M)

DiameterIdentity. Contains the destination realm name config-

ured for the server.

Auth-Request-

Type (274M)

Enumerated. Indicates application-specific authorization request

types towards the Diameter server and also the authorization

answers to inform the client about the action expected upon expi-

ration of the authorization lifetime. Defines whether the UE is to

be authenticated only, authorized only or both.

Only one value is supported:

AUTHORIZE_ONLY (2).

Destination-Host

(293M)

DiameterIdentity. Contains the destination host name configured

for the server. If the destination host is omitted from the configu-

ration, Destination-Host AVP is not sent in any outgoing Diameter

message.


Table 3 Authentication-Authorization-Request sent by Flexi NG (Cont.)




DN09106383 Issue 1-1

15


Id:0900d80580930537

5.2 Authentication-Authorization-Answer

User-Name (1M) UTF8String. If the user equipment has provided a user name in

the protocol configuration options GTP information element, then

it is used here. Otherwise, this AVP is not included.

MIP6-Agent-Info

(486M)

Grouped. Indicates the identity of the selected PGW for the UE

and the corresponding PDN connection.

Contains the necessary information to assign a Home Agent (HA)

to the Mobile Node (MN).

MIP-Home-

Agent-

Address

(334M)

Address. Indicates the address and/or host name of the home

agent.

Contains the IPV6 or IPv4 address of the MIPv6 HA.

MIP6-Feature-

Vector (124M)

Unsigned64. Indicates the supported mobile IP capabilities of the

non-3GPP GW (when used in the request commands) and themobile IP capabilities of the 3GPP AAA server (when used in the

answer commands).

Contains a 64-bit flags field of supported capabilities of the

NAS/ASP. The following capabilities are sup-

ported:PMIP6_SUPPORTED

(0x0000010000000000)IP4_HOA_SUPPORTED

(0x0000020000000000).

Visited-Network-

Identifier

(3GPP/600M)

OctetString. Allows the home network to identify the Visited

Network.

Contains the PLMN ID of the PGW in the form:mnc<MNC>.mcc<MCC>.3gppnetwork.org

Service-Selection

(493M)

UTF8String. Indicates the name of the service or the external

network with which the mobility service should be associated.

Contains the APN-NI that contains one or more labels according

to DNS naming conventions describing the access point to the

packet data network. The contents are formatted as a character

string composed of one or more labels separated by dots (".").


Table 3 Authentication-Authorization-Request sent by Flexi NG (Cont.)


Session-Id (263M) UTF8String. Flexi NG uses the end-to-end identifier in the

message header to locate the session that is associated with the

AAA message.

Auth-Application-

Id (258M)


S6b is used.

Table 4 Authentication-Authorization-Answer received by Flexi NG




DN09106383 Issue 1-1


Id:0900d80580930537

S6b AVPs

Origin-Host

(264M)

DiameterIdentity. Ignored if received. The value of this AVP is

trusted to be correct.

Origin-Realm

(296M)



Auth-Request-

Type (274M)

Enumerated. Indicates application-specific authorization request

types towards the Diameter server and also the authorization

answers to inform the client about the action expected upon expi-

ration of the authorization lifetime. Defines whether the UE is to

be authenticated only, authorized only or both.

Only one value is supported:

AUTHORIZE_ONLY (2).

MIP6-Feature-

Vector (124M)

Unsigned64. Ignored if received. Not supported in the current

release.

Session-Timeout

(27M)

Unsigned32. Ignored if received. Not supported in the current

release.

Result-Code

(268M)

Unsigned32. Indicates the result of the request.


Table 4 Authentication-Authorization-Answer received by Flexi NG (Cont.)




DN09106383 Issue 1-1

17


Id:0900d80580930537

5.3 Session-Termination-Request













When the field separators (';') are included in the count, the theo-

retical minimum size is 16 bytes, and the theoretical maximum

size is 278.







Auth-Application-

Id (258M)


S6b is used.

Table 5 Session-Termination-Request sent by Flexi NG




DN09106383 Issue 1-1


Id:0900d80580930537

S6b AVPs

Origin-Host

(264M)

DiameterIdentity. The host name of the DIAMETER node in Flexi






Example:




Example:





Example:

gatewayservice7-10-


Origin-Realm

(296M)


diameter server.

Example:




Destination-

Realm (283M)

DiameterIdentity. Contains the destination realm name config-

ured for the server.

Termination-

Cause (295M)

Enumerated. Identifies the reason for session termination.

Supported values:

DIAMETER_LOGOUT (1),

DIAMETER_SERVICE_NOT_PROVIDED (2),DIAMETER_BAD_ANSWER (3),

DIAMETER_ADMINISTRATIVE (4),

DIAMETER_LINK_BROKEN (5),

DIAMETER_AUTH_EXPIRED (6),

DIAMETER_USER_MOVED (7),

DIAMETER_SESSION_TIMEOUT (8)

User-Name (1M) UTF8String. If the user equipment has provided a user name in

the protocol configuration options GTP information element, then

it is used here. Otherwise, this AVP is not included.


Table 5 Session-Termination-Request sent by Flexi NG (Cont.)




DN09106383 Issue 1-1

19


Id:0900d80580930537

5.4 Session-Termination-Answer

5.5 Abort-Session-Request




STA message.

Origin-Host

(264M)



Origin-Realm

(296M)



Result-Code

(268M)


Table 6 Session-Termination-Answer received by Flexi NG




ASR message.

Auth-Application-

Id (258M)

Unsigned32. Contains value 16777272 to indicate that 3GPP

S6b is used.

Origin-Host

(264M)



Origin-Realm

(296M)



Destination-

Realm (283M)



User-Name (1M) UTF8String. Ignored if received.

Auth-Session-

State (277M)

Enumerated. Specifies whether state is maintained for a particu-

lar session or not.

Supported values:

STATE_MAINTAINED (0),

NO_STATE_MAINTAINED (1)

Table 7 Abort-Session-Request received by Flexi NG




DN09106383 Issue 1-1


Id:0900d80580930537

S6b AVPs

5.6 Abort-Session-Answer













When the field separators (';') are included in the count, the the-

oretical minimum size is 16 bytes, and the theoretical maximum

size is 278.







Table 8 Abort-Session-Answer sent by Flexi NG




DN09106383 Issue 1-1

21


Id:0900d80580930537

Origin-Host

(264M)

DiameterIdentity. The host name of the DIAMETER node in Flexi






Example:




Example:





Example:

gatewayservice7-10-


Origin-Realm

(296M)


diameter server.

Example:




Result-Code

(268M)



Table 8 Abort-Session-Answer sent by Flexi NG (Cont.)




DN09106383 Issue 1-1


Id:0900d805809304ab

References

6 References

1. 3GPP TS29.273, “Evolved Packet System (EPS); 3GPP EPS AAA interfaces".

http://www.3gpp.org/ftp/Specs/html-info/29273.htm

2. RFC 4005 Diameter Network Access Server Application, Calhoun P. et al.

http://www.ietf.org/rfc/rfc4005.txt

3. RFC 5447 Diameter Mobile IPv6: Support for Network Access Server to Diameter

Server Interaction, J. Korhonen et al.

http://www.ietf.org/rfc/rfc5447.txt



Diameter Network Access Server Application Glossary

7 Glossary

Term Definition

AAA server authentication authorization and accounting server

AAA authentication authorization answer

AAR authentication authorization request

APN-NI APN network identifier

ASA abort session answer

ASR abort session request

AVP attribute value pair

DSMIP Dual Stack Mobile IP

EPC evolved packet core

FQDN fully qualified domain name

HA home agent

HSGW high rate packet data serving gateway

HSS home subscriber server

MIP Mobile IP

PDN packet data network

P-GW or

PDN-GW

packet data network gateway

PMIP Proxy Mobile IP

STA session termination answer

STR session termination request

UE user equipment

ng_dnas_app_ifd

Documents