03 - CN37403EN92GLA0 - HSS-FE S6 Specific Functions and Interfaces

HSS-FE S6 Specific Functions and Interfaces
HSS-FE S6 Specific Functions and

Interfaces
Contents
1
Introduction
1.1
HSS-FE Specific Interfaces
2
HSS-FE Specific Procedures
2.1
Authentication and Key Management
2.2
Update Location
2.3
Cancel Location
2.4
Purge UE
2.5
Insert Subscriber Data
2.6
Delete Subscriber Data
2.7
Reset
2.8
Notify
CN37403EN92GLA0
2013 Nokia Siemens Networks
1
3
6
11
12
16
18
20
22
24
26
28
CN37403EN92GLA0
Introduction
Fig. 1 Introduction
Nowadays, 2G/2.5G (GSM/GPRS) and 3G (UMTS) domains are supported by HLRoriented equipments which connect the necessary core network backbone for the
todays telecommunication networks.
With the upcoming of the new 3GPP Release 8 radio technology (LTE), the HSS-will
be greatly involved in the supporting of the core network functionality that will bring
new services and rich end user experience in terms of service quality and costs.
LTE/SAE provides
High data rates and spectral efficiency

Supports peak data rates of up to 173Mbps
Low latency (round trip delays of 10-20 ms)
Cost-efficient handling of increased data traffic
CN37403EN92GLA0
Scalable bandwidth from 1.4 up to 20 MHz and flexible spectrum allocation.

The standards define the HSS as both the logic and repository parts for subscriber
management. Obviously, in the case of the NSN solution embedding a multi-service
database, we will be referring to HSS as a combination of the HSS-FE and One-NDS
database parts.
CN37403EN92GLA0
The following picture shows the evolution steps from GSM/UMTS towards LTE/SAE,
with the HSS-FE (HSS) as a central component in the control network.
Access
Core
Control
GSM/EDGE/
MSC
MGW
BTS
UMTS/HSPA
Shift of
functionality
BSC
RNC
Node B
SGSN
GGSN
LTE / SAE
PDN
MME
HSS
SAE-GW
eNodeB
EPC
LTE: Long Term Evolution

SAE: System Architecture Evolution
EPC: Evolved Packet Core
MME: Mobility Management Entity
HSS: Home Subscriber Server
eNodeB: evolved Node B
PDN: Packet Data Network
BSC: Base Station Controller

RNC: Radio Network Controller
MGW: Media Gateway
MSC: Mobile Switching Center
SGSN: Serving GPRS Support Node
GGSN: Gateway GPRS Support Node
Nokia Siemens Networks
Fig. 2 Network evolution
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
CN37403EN92GLA0
. Nokia
. .Siemens
. .Networks
. .
2013
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1.1
HSS-FE Specific Interfaces
Currently, the HSS-FE is meant for IMS systems and therefore natively support
Diameter based interfaces like Cx/Sh/Wx/SWx/Zh and so on, mostly used for the
interfacing with the CSCF.
Nowadays, the S6a/d Diameter interfacing will be used following the enhancement of
the Packet Switch network domain (EPS) by the LTE access, according to 3GPP
Release 8.
The S6a Diameter interface runs towards the MME while the S6d runs towards the
Release 8 SGSN, as described in the relevant 3GPP standard (3GPP TS 29.2728.1.1, Release 8). This new purpose for the Diameter interface will provide a mean to
handle the necessary traffic load sharing with the different HSS-FEs.
Focusing on the LTE implementation of the HSS-FE narrows down the relevant
interfaces to S6a (connectivity with MME) and LDAP (connectivity to One-NDS) as
well as the S6d (connectivity with Rel 8 SGSN) and LDAP (connectivity to One-NDS).
Since we are already familiar with LDAP, we will focus on the S6 interface.
TIP
The S6 Diameter interface is based on IP, with SCTP being used as transport
protocol.
The picture below depicts the components of the HSS-FE involved in this interfacing.
Fig. 3 HSS-FE Architecture and Interfacing
CN37403EN92GLA0
In an LTE-only scenario, the messages shared between the corresponding entities is

depicted on the following figure, with the focus on the S6 interface:
HSS-FE (with LDAP

to One-NDS)
MME
S6a
R8-SGSN
eNodeB
S6d
RNC
S4
S11
UE
NodeB
SAE-GW
PCRF
PCEF
PDN
GW
Serving
GW
BSC
PDN
BTS
S6 Interface based on Diameter
PDN: Packet Data Network
MME: Mobility Management Entity
PCRF: Policy and Charging Rules Function
HSS: Home Subscriber Server
PCEF: Policy and Charging Enforcement Function
UE: User Equipment
eNodeB: evolved Node B
Fig. 4 HSS-FE S6 interface
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
CN37403EN92GLA0
. . . . . . .
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1.1.1
S6 Diameter Interface
In order to support the S6 interface, the HSS-FE uses the Diameter stack which
provides the following functions:
Identification of incoming messages

Identification of outgoing messages
Identification of the relevant AVPs (Attribute Value Pairs)
The message types that are expected on this S6 interface are:
ULR Update Location Request (I)
ULA Update Location Answer (O)
AIR Authentication Information Request (I)
AIA Authentication Information Answer (O)
CLR Cancel Location Request (O)
CLA Cancel Location Answer (I)
PUR Purge UE Request (I)
PUA Purge UE Answer (O)
IDR Insert Subscriber Data Request (O)
IDA Insert Subscriber Data Answer (I)
DSR Delete Subscriber Data Request (O)
DSA Delete Subscriber Data Answer (I)
NOR Notify Request (I)
NOA Notify Answer (O)
RSR RESET Request (O)
RSA RESET Answer (I)
TIP
The direction of each message is in brackets.
(I) means Incoming, (O) means Outgoing - from the HSS-FE perspective.
1.1.2
Diameter Interface - Automatic Connection Closure
In case of critical errors in the HSS-FE/SGSN, there is a provision to automatically

set an inaccessible flag on the S6 (Diameter) interface. The following errors can
trigger an automatic interrupt on the S6 call flow:
a) FE-DSA unavailability (One NDS database)
b) HSM unavailability
c) Unavailability of the main Diameter process itself
CN37403EN92GLA0
Here is a wrap-up of the most important S6 Diameter messages that we will study in
more details throughout the training:
ULR Update Location Request (I)
ULA Update Location Answer (O)
AIR Authentication Information Request (I)
AIA Authentication Information Answer (O)
CLR Cancel Location Request (O)
CLA Cancel Location Answer (I)
PUR Purge UE Request (I)
PUA Purge UE Answer (O)
IDR Insert Subscriber Data Request (O)
IDA Insert Subscriber Data Answer (I)
DSR Delete Subscriber Data Request (O)
DSA Delete Subscriber Data Answer (I)
NOR Notify Request (I)
NOA Notify Answer (O)
RSR RESET Request (O)
RSA RESET Answer (I)
Fig. 5 S6 Diameter message types
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
CN37403EN92GLA0
. . . . . . .
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
10
CN37403EN92GLA0
HSS-FE Specific Procedures
Fig. 6 HSS-FE Specific Procedures
CN37403EN92GLA0
11
2.1
Authentication and Key Management
LTE/SAE security handling uses the EPS Authentication and Key Agreement (EPS
AKA) procedure. EPS AKA is based on the UMTS AKA procedure.
With the introduction of the new LTE/SAE flat network architecture, some additional
security enhancements were defined in comparison with the UMTS security handling:
New key hierarchy

Termination of encryption at network edge
New protocols to be secured
More demanding security requirements from 3GPP
The following keys are shared between UE and HSS:
K
is the permanent key stored on the USIM and in the

Authentication Centre (AuC).
CK, IK
is the pair of keys derived in the AuC and on the USIM during
an AKA run
TIP
EPS AKA is specified in [TS33.401], which defines a rel-99 or later USIM application
on an UICC for accessing E-UTRAN.
EPS AKA differs from UMTS AKA in the use of the AMF separation bit and the key
hierarchy. As a result of the authentication and key agreement, an intermediate key
KASME is generated using the CK, IK and serving network ID.
E-UTRAN keys are then derived from the KASME.
For further details refer to 3GPP TS 33.401 SAE: Security Architecture.
12
CN37403EN92GLA0
In order to perform user specific access authentication the MME receives from the
HSS-FE one or more EPS authentication vectors (RAND, AUTN, XRES and
KASME). The MME indicates in the request how many vectors it is prepared to
receive. The HSS-FE (through HSM box) responds accordingly, providing this is in
harmony with the locally configured maximum number of permitted vectors (1 to 5).
The transfer of these authenticating/authorizing relevant data is performed via the S6
interface by using the Authentication Information Retrieval Procedure.
WARNING
There are two possibilities regarding the Authentication Center in our case. We
can indeed have a SoftAC (which is a Crypto-Module embedded on the HSSFE) or a connection to a HSM box (more secure). To avoid confusion, we will
simply refer to AuC as the entity providing the Authentication data.
An ME accessing E-UTRAN shall check during

authentication that the "separation bit" in the
AMF field of AUTN is set to 1 and reject
authentication otherwise with a CAUSE value
If the "separation bit" is

set to 1, the
authentication vector is
only usable for AKA in
an EPS context
The "separation bit" in the AMF field (bit 0) is set to 1.

The secret keys CK
and IK generated
during this AKA shall
never leave the HSS
AUTN := SQN AK ||AMF|| MAC
Pre
Pre-EPS authentication vector (RAND,
AUTN
AUTN,
, XRES,
XRES, CK, IK)
IK)
SN -ID = MCC+MNC
KASME:= KDF
KDF( CK, IK,, SN --ID, SQN AK)
EPS
EPSauthentication
authenticationvector
vector(RAND,
(RAND,AUTN, XRES, KASME)
Fig. 7 EPS Authentication handling
TIP
EPS AKA at the HSS-FE is supported on the basis that the AuC is co-located. Should
all HSM-Boxes be unavailable, the S6a connections will be closed and new
connections only accepted when at least one HSM-Box is available again.
CN37403EN92GLA0
13
2.1.1
Authentication Information Request Procedure
The MME/SGSN uses the Authentication Information Retrieval Procedure to request

authentication information from the HSS-FE.
The generation of keys is triggered by Authentication and Key Agreement (AKA)
procedures. In LTE/SAE the MME acts as the Access Security Management Entity
(ASME). This is the access network entity that receives top level keys from the HSSFE.
UMTS AKA is capable of agreeing two keys, CK and IK, both co-located in the USIM
and in the AuC. For LTE these keys never leave the HSS-FE AuC. Instead, they are
used to derive KASME, which is transferred from the HSS-FE to the MME as part of
the Authentication Vector (AV).
Upon receiving an Authentication Information Request command from the MME, the
HSS-FE checks whether the IMSI is already known in the database. If true, the HSSFE requests the AuC to generate the corresponding authentication vectors.
By receiving the AVs from the AuC, the HSS-FE generates the authentication
parameter KASME before sending the response to the MME. After this, the HSS-FE
returns to the MME the result code Diameter_Success and the generated
Authentication Vectors.
The most important information elements contained in the corresponding messages
are given below:
14
Command
Authentication Information Request
User Name
IMSI (i.e., identity of the user)
Visited PLMN ID
MCC-MNC of visited PLMN
Requesting Node Type
3 (requesting node is MME/SGSN combined)
Command
Authentication Information Answer
User Name
Result
Indicates the result of the operation (i.e., success/error)
RAND
Random Value
KASME
Authentication Parameter used for Network

Authentication
XRES
UE Expected Result of the Authentication Computation
CN37403EN92GLA0
2.1.2
Message flow
UE
eNodeB/RNC/BSC
HSS-FE
MME/SGSN
One NDS
S6 (Diameter)
LDAP
NAS: attach Request

(User ID, UE Capabilities,)
Authentication Information Request

LDAP Search
(AVP: User-Name, Requested E-UTAN
or UTRAN/GERAN Auth Info,
Visited-PLMN-ID)
(IMSI)
LDAP Response
. Check Username
. Check EPS
. Check RAT
. Check Roaming
UE derives and
uses KASME to
verify the
network
(AC Credentials, EPS Profile Data)
AuC
Authentication Information Answer
E-UTRAN = (AV: RAND(i), AUTN(i) KASME(i), XRES(i))
UTRAN = (AV: RAND(i), AUTN(i) KASME(i), CK(i), IK(i))
NAS: User Authentication Request

(RAND(i), AUTN(i))
if RES(i) = XRES(i)
NAS: User Authentication Response

(RES(i))
authentication successful
Fig. 8 Authentication Procedure
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
CN37403EN92GLA0
. . . . . . .
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
15
2.2
Update Location
The Update Location procedure is used between the MME/SGSN and the HSS-FE to
update location information of the subscriber in the One-NDS, and to download the
user subscription data towards the MME/SGSN.
This procedure is invoked by the MME/SGSN and may be optionally used to provide
the HSS-FE with other user data, such as Terminal Information.
The Update Location procedure is mapped to the commands Update Location
Request (ULR) and Update Location Answer (ULA). The most important information
elements contained in these messages are shown in the table below:
Command
Update Location Request
User Name
ULR Flags
Bit 2 (Skip Subscriber Data)
Visited PLMN ID
Contains MCC and MNC. May be used to apply roaming based

features
RAT Type
Contains the Radio Access Type the UE is using
Command
Update Location Answer
Result Code
Indicates result of the operation (e.g., Roaming Not Allowed)
ULA Flags
Bit 0 (not used)
2.2.1
Update Location Procedure
Upon receiving an Update Location Request, the HSS-FE performs IMSI, EPS
subscription and roaming checks. Depending on specific conditions, different result
codes are determined and send back to the MME/SGSN.
16
CN37403EN92GLA0
2.2.2
Message Flow
MME/SGSN
HSS-FE
One NDS
S6 (Diameter)
LDAP

(AVP: User-Name)
LDAP Search
. Check Username
. Check EPS
. Check RAT
. Check Roaming
(IMSI)
LDAP Response

(DIAMETER_SUCCESS)
LDAP Modify
(MME/SGSN Identity)
LDAP Response
Fig. 9 Update Location Procedure
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
CN37403EN92GLA0
. . . . . . .
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
17
2.3
Cancel Location
The Cancel Location procedure is used between the HSS-FE and the MME/SGSN to
delete a subscriber record from the MME/SGSN.
This procedure will be invoked by the HSS-FE and represents the following
conditions:
HSS-FE informs the MME/SGSN about the subscriber's subscription withdrawal

HSS-FE informs the MME/SGSN about an ongoing update procedure, i.e. by
changing of MME/SGSN.
The Cancel Location procedure is mapped to the commands Cancel Location
Request (CLR) and Cancel Location Answer (CLA).
The most important information elements contained in these messages are shown in
the table below:
Command
Cancel Location Request
User Name
Cancellation Type
Defines the type of cancellation (e.g. MME/SGSN-Update

Procedure, Subscription Withdrawal, )
Command
Cancel Location Answer
Result
Indicates the result of the operation (i.e., success or error)
2.3.1
Cancel Location Procedure
The Cancel Location procedure is triggered over the provisioning interface of the
One-NDS, or as part of an Update Location Request sent by the MME/SGSN.
Different types of cancellation procedures are defined, as explained below:
Subscription Withdrawal
The HSS-FE will include a cancellation type "Subscription Withdrawal" if the
subscriber's subscription is barred or deleted by the operator.
MME/SGSN Update Procedure

This will occur when the UE moves to a new MME/SGSN area.
18
CN37403EN92GLA0
2.3.2
Message Flow: Subscription Withdrawal
MME/SGSN
HSS-FE
NTF
S6 (Diameter)
SOAP
sendSOAPTrigger
sendSOAPResponse

(Cancellation-Type: Subscription Withdrawal)
(DIAMETER_SUCCESS)
Fig. 10 Cancel Location Procedure - Subscription withdrawal
2.3.3
Message Flow: MME/SGSN Update

MME/SGSN 2
MME/SGSN 1
HSS-FE
S6 (Diameter)
One NDS
LDAP

LDAP Search
(AVP: User-Name)
(IMSI)
. Check Username
. Check EPS
. Check RAT
. Check Roaming
LDAP Response

(Cancellation-Type: MME/SGSN-Update Procedure)
(DIAMETER_SUCCESS)
(DIAMETER_SUCCESS)
LDAP Modify
(MME/SGSN Identity)
LDAP Response
Fig. 11 Cancel Location Procedure - MME/SGSN Update

CN37403EN92GLA0
19
2.4
Purge UE
The Purge UE procedure is used between the HSS-FE and the MME/SGSN, and
between the HSS-FE and the SGSN, to indicate that the subscriber profile has been
deleted from the MME/SGSN either by an MMI interaction or automatically, e.g.
because the UE has been inactive for several days.
The Purge UE procedure is mapped to the commands Purge UE Request (PUR) and
Purge UE Answer (PUA).
the table below:
Command
Purge UE Request
User Name
Command
Purge UE Answer
Result
indicates the result of the operation, (i.e., success/error)
PUA Flags
Bit mask 0: (Freeze M-TMSI)
2.4.1
Purge UE Procedure
When receiving a Purge UE request, the HSS-FE checks whether the IMSI is known.
Afterwards, it compares the Source Node Identity with the stored MME/SGSN ID. If
they are identical, the HSS-FE sets the PUA Flag "Freeze M-TMSI" (for MME) or the
Freeze P-TMSI (for SGSN), and finally sets internally the flag "UE Purged in
MME/SGSN", as described in the figure 12.
In case the IMSI is not known in the One-NDS, an error is returned to the
MME/SGSN with the corresponding result code, see figure 13.
20
CN37403EN92GLA0
2.4.2
Message Flow: IMSI Known
Message Flow: IMSI Known
MME/SGSN
HSS-FE
One NDS
S6 (Diameter)
LDAP
Purge UE Request
(AVP: User-Name)
LDAP Search
(IMSI)
Compare MME/SGSN ID
LDAP Response
Purge UE Answer
(DIAMETER_SUCCESS)
LDAP Modify
(UE Purged in MME/SGSN)
LDAP Response
Fig. 12 Purge UE IMSI Known
2.4.3
Message Flow: IMSI Unknown

MME/SGSN
HSS-FE
S6 (Diameter)
One NDS
LDAP
Purge UE Request
(AVP: User-Name)
LDAP Search
(IMSI)
LDAP Response
(LDAP_NO_SUCH_OBJECT)
Purge UE Answer
(DIAMETER_ERROR_USER_UNKNOWN)
Fig. 13 Purge UE IMSI Unknown

CN37403EN92GLA0
21
2.5
Insert Subscriber Data
The Insert Subscriber Data procedure is used between the HSS-FE and the
MME/SGSN for updating certain user data in the MME/SGSN.
Following situations can be considered:
Administrative changes of the user data in the One-NDS, while roaming in one
MME/SGSN (i.e., subscription changes)
The feature ODB (Operator Determined Barring) has been applied, changed or
removed for that user
After activation of subscriber tracing in MME/SGSN

The Insert Subscriber Data procedure is mapped to the commands Insert Subscriber
Data Request (IDR) and Insert Subscriber Data Answer (IDA).
the table below:
Command
Insert Subscriber Data Request
User Name
Subscription Data
modifications (add/replace) to the subscription profile stored

in the MME/SGSN
Command
Insert Subscriber Data Answer
Result
2.5.1
Insert Subscriber Data Procedure
The HSS-FE (on behalf of the One-NDS) uses this procedure to replace a specific
part of the user data stored in the MME/SGSN, or just to add a specific part on that
user data.
This procedure is triggered over the provisioning interface of the One-NDS.
22
CN37403EN92GLA0
2.5.2
Message Flow
MME/SGSN
HSS-FE
NTF
S6 (Diameter)
SOAP
sendSOAPTrigger
sendSOAPResponse
Insert Subscriber Data Request

(AVP: Subscription-Data)
Insert Subscriber Data Answer
(DIAMETER_SUCCESS)
Fig. 14 Insert Subscriber Data
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
CN37403EN92GLA0
. . . . . . .
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
23
2.6
The Delete Subscriber Data procedure is used between the MME/SGSN and the
HSS-FE to remove partial or the complete user profile data stored in the MME/SGSN.
This procedure is invoked by the HSS-FE and will be used in the following situations:
To remove all or a subset of the subscriber EPS Subscription Data (APN

Configuration Profile) from the MME/SGSN
To remove the regional subscription

To remove the subscribed Charging Characteristics
To remove the Session Transfer Number for SRVCC
To remove the user Trace Data
The Delete Subscriber Data procedure is mapped to the commands Delete
Subscriber Data Request (DSR) and Delete Subscriber Data Answer (DSA).
The following table provides an overview of the most important information elements
contained in these messages:
Command
User Name
DSR Flags
Bit Mask (e.g., Bit 1 = Complete APN Configuration Profile

Withdrawal)
Command
Delete Subscriber Answer
Result
2.6.1
Delete Subscriber Data Procedure
The HSS-FE uses this procedure to remove from the MME/SGSN the user
subscription data taken from the One-NDS.
This procedure is triggered over the provisioning interface of the One-NDS.
24
CN37403EN92GLA0
2.6.2
Message Flow
MME/SGSN
HSS-FE
NTF
S6 (Diameter)
SOAP
sendSOAPTrigger
sendSOAPResponse
Delete Subscriber Data Request
(AVP: User-Name, DSR Flags)
Delete Subscriber Data Answer
(DIAMETER_SUCCESS)
Fig. 15 Delete Subscriber Data
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
CN37403EN92GLA0
. . . . . . .
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
25
2.7
Reset
The Reset Procedure shall be used by the HSS, after a restart, to indicate to the
MME (and, if applicable, to the SGSN) that a failure has occurred.
This procedure is mapped to the commands Reset Request (RSR) and Reset
Answer (RSA).
Command
Reset Request
User ID List (O)
list of User IDs (MCC, MNC)
Command
Reset Answer
Result
2.7.1
Reset Procedure
The HSS-FE makes use of this procedure in order to indicate the MME/SGSN that
the One-NDS nodes holding the MME/SGSN Identity of some subscribers currently
roaming in that MME/SGSN Area have restarted and may have lost this data.
This action is necessary for the HSS-FE in order to provide future Cancel Location
messages as well as to be able to start Insert/Delete Subscriber Data procedures,
when needed.
The Reset procedure is triggered by the operator over the One-NDS Administrator
GUI.
26
CN37403EN92GLA0
2.7.2
Message Flow
MME/SGSN
NTF
HSS-FE
S6 (Diameter)
ADM
One NDS
SOAP
SOAP
LDAP
LDAP Search
(DSA ID)
LDAP Response
(User-IDs)
LDAP Modify
(Send-RESET)
LDAP Response
sendSOAPTrigger
sendSOAPResponse
sendSOAPTrigger
sendSOAPResponse
Reset Request
(Opt-AVP: User-ID)
Reset Answer
(DIAMETER_SUCCESS)
Fig. 16 Reset
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
CN37403EN92GLA0
. . . . . . .
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
27
2.8
Notify
The Notification Procedure shall be used between the MME/SGSN and the HSS and
between the SGSN and the HSS when an inter MME/SGSN or SGSN location
update does not occur but the HSS needs to be notified about:
An update of terminal information

An update of the UE SRVCC capability
Also and more generally if the HSS needs to be notified about:
An assignment/change of a dynamically allocated PDN GW for an APN, if such a

notification is needed taking into account the access restrictions
The UE has become reachable again

This procedure is mapped to the commands Notify Request (NOR) and Notify
Answer (NOA).
Command
Notify Request
User-Name
IMSI
Command
Notify Answer
Result
2.8.1
Notify Procedure
The MME/SGSN makes use of this procedure in order to indicate the HSS that the
User Equipment information for a specific subscriber have to be updated, new PDN
GW Identity has to be verified for handover allocation or that user has become
reachable again.
The message flow for this procedure is detailed on the figure on the right-hand side.
28
CN37403EN92GLA0
2.8.2
Message Flow
MME/SGSN
NTF
HSS-FE
S6 (Diameter)
ADM
One NDS
SOAP
SOAP
LDAP
LDAP Search
(DSA ID)
LDAP Response
(User-IDs)
LDAP Modify
(Send-RESET)
LDAP Response
sendSOAPTrigger
sendSOAPResponse
sendSOAPTrigger
sendSOAPResponse
Reset Request
(Opt-AVP: User-ID)
Reset Answer
(DIAMETER_SUCCESS)
Fig. 17 Notify
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
CN37403EN92GLA0
. . . . . . .
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
29
30
CN37403EN92GLA0

03 - CN37403EN92GLA0 - HSS-FE S6 Specific Functions and Interfaces

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

03 - CN37403EN92GLA0 - HSS-FE S6 Specific Functions and Interfaces

Hochgeladen von

Copyright:

Verfügbare Formate

HSS-FE S6 Specific Functions and Interfaces

HSS-FE S6 Specific Functions and

HSS-FE S6 Specific Functions and Interfaces

HSS-FE S6 Specific Functions and Interfaces

High data rates and spectral efficiency

HSS-FE S6 Specific Functions and Interfaces

Scalable bandwidth from 1.4 up to 20 MHz and flexible spectrum allocation.

HSS-FE S6 Specific Functions and Interfaces

LTE: Long Term Evolution

BSC: Base Station Controller

Nokia Siemens Networks

Fig. 2 Network evolution

HSS-FE S6 Specific Functions and Interfaces

HSS-FE Specific Interfaces

Fig. 3 HSS-FE Architecture and Interfacing

HSS-FE S6 Specific Functions and Interfaces

In an LTE-only scenario, the messages shared between the corresponding entities is

HSS-FE (with LDAP

S6 Interface based on Diameter

PDN: Packet Data Network

MME: Mobility Management Entity

PCRF: Policy and Charging Rules Function

HSS: Home Subscriber Server

PCEF: Policy and Charging Enforcement Function

UE: User Equipment

eNodeB: evolved Node B

Nokia Siemens Networks

Fig. 4 HSS-FE S6 interface

HSS-FE S6 Specific Functions and Interfaces

Identification of incoming messages

ULA Update Location Answer (O)

AIR Authentication Information Request (I)

AIA Authentication Information Answer (O)

CLR Cancel Location Request (O)

CLA Cancel Location Answer (I)

PUR Purge UE Request (I)

PUA Purge UE Answer (O)

IDR Insert Subscriber Data Request (O)

IDA Insert Subscriber Data Answer (I)

DSR Delete Subscriber Data Request (O)

DSA Delete Subscriber Data Answer (I)

NOR Notify Request (I)

NOA Notify Answer (O)

RSR RESET Request (O)

RSA RESET Answer (I)

Diameter Interface - Automatic Connection Closure

In case of critical errors in the HSS-FE/SGSN, there is a provision to automatically

HSS-FE S6 Specific Functions and Interfaces

ULR Update Location Request (I)

ULA Update Location Answer (O)

AIR Authentication Information Request (I)

AIA Authentication Information Answer (O)

CLR Cancel Location Request (O)

CLA Cancel Location Answer (I)

PUR Purge UE Request (I)

PUA Purge UE Answer (O)

IDR Insert Subscriber Data Request (O)

IDA Insert Subscriber Data Answer (I)

DSR Delete Subscriber Data Request (O)

DSA Delete Subscriber Data Answer (I)

NOR Notify Request (I)

NOA Notify Answer (O)