Udc technical course

introduction
Scope and Objectives
Scope

› Describe the purpose and main characteristics of the UDC

(Ericsson User Data Consolidation) solution
› UDC Architecture description
› Describe the different nodes that are part of the UDC solution
› Understand the migration procedure

Objectives
› At the end of this course, the participants
will have a general understanding of the
UDC solution and Ericsson’s UDC offerings
Agenda

› UDC Overview
› UDC Solution Architecture
› UDC Components
› Traffic Cases
Udc overview
FROM classic to layered architecture
Architecture
HLR & HSS UDC

HLR/HSS Front End

Front
End

Classic HLR or HSS node Application logic Logic

HLR or & Signalling
HSS
Protocols

OAM
Protocol
OAM

Logic Ericsson Back End

CUDB

PG
Data Storage

Processing Layer
Database
Data Storage
 UDC x DLA
› A Solution is the answer to a Customer’s business needs
enabling him to exploit his opportunities
› UDC stands for User Data Consolidation
› UDC is a layered solution for user data storage

INDUSTRY DLA: Data Layered Architecture

ERICSSON UDC: User Data Consolidation

User Data CONSOLIDATION
Customer E2E SOLUTION
NEW Application integration

OSS 
PG 

HLR-FE NEW


HLR-FE APP



DATA MIGRATION
CAS

DME CUDB
Servic CUDB
CUDB
e CUDB
Udc architecture
UDC components
Functional Architecture
udc external interfaces
UDc Core network
UDC internal Interfaces
Circuit Switch
IMS
& Packet Switch
Core Network SNMP,
Core Network
(MSC, IN, GGSN, and LTE Telnet,
SGSN, etc.) (CSCF, AS, etc.) ftp,SSH
,
Radius
SOAP Diameter
MAP Operational
1
Support
Application 7 6
4 System
layer 3 Provisioning HLR-FE HSS/SLF-FE (OSS)

CAS Gateway
5 8
2 2
LDAP
Partitioning Partitioning Function
layer
CAI3G, CLI,
MML*
CUDB
Data Notifications
Data Store MML Data Store
store LDAP SOAP
Signaling Impact
New Protocol in CN: LDAP

› What is LDAP?
– Lightweight Directory Access Protocol.
– The LDAP hierarchy has a tree structure.
– LDAP is a client-server based directory access protocol that provides
both read and update access.

› Characteristics of LDAP
– Uses TCP/IP
– Open standard by the Internet Engineering Task Force (IETF)
– OpenLDAP Software is an open source implementation of the
Lightweight Directory Access Protocol
– Allow the management of users and access privileges
LDAP Server Configuration

LDAP Operations

LDAP TCP/IP LDAP

Client Server

HLR/AUC-S CUDB Directory

Signaling Impact
New Protocol in CN: SOAP

› What is SOAP?
– Simple Object Access Protocol
– Specification for exchanging structured information
– XML based protocol

› Characteristics of SOAP
– Extensibility: security and routing are among the extensions under
development
– Neutrality: SOAP can be used over any transport protocol
– Independence: SOAP allows for any programming model
Udc components
HLR/AuC/MNP/m2m front end
HLR-FE process handling
HLR-FE is able to receive requests:

1. MAP/INAP signalling traffic messages for a subscription from other GSM/WCDMA

applications (e.g. VLR, SGSN, GMSC, etc.)
• HLR-FE also solves the Mobile Number Portability

2. Validation orders when initiating/changing/ending subscription data from Provisioning

Gateway for a subscription

3. HLR/AuC-FE axe based Administrative orders for initiating/changing/ending/printing

HLR-FE application data (e.g. configuration data, alarms, etc.) from OSS

HLR/AUC/
MNP-FE
HSS Front end
Centralized User DataBase
Circuit Switch
IMS
& Packet Switch
Core Network Core Network
(MSC, IN, GGSN, and LTE
SGSN, etc.) (CSCF, AS, etc.)

Signaling SD SLF
Distribution

Network applications
HLR/AuC-FE HSS-FE
Centralized User Provisioning
Gateway
DataBase
• extensible, networked
high-performance,
distributed database

• CUDB system = set of CUDB

”CUDB nodes”
 CUDB Function
› CUDB role:
– Centralized subscription database in the network for
storing and managing subscriber data
› CUDB is:
– In-memory
– Highly Scalable
– Highly Available
– Geographically Distributed and Replicated
– Extensible Data Model
– Perceived by applications as one logical distributed
LDAP v3 directory
CUDB
Provisioning Gateway
Single point of provisioning
› PG implements the single point of provisioning for UDC
solution. Provisioning for HLR, AuC, MNP, HSS (EPS, IMS
and AVG) and EIR applications within UDC

› PG offers the following interfaces for provisioning from the

CAS or Mediation System:
– CAI3G is a SOAP-based interface for provisioning of HLR, AuC, MNP, EIR
and HSS data and profiles
– Man Machine Language (MML) is a proprietary protocol for the provisioning
of HLR, AuC and MNP data
– The PG Command Line Interface (CLI) is an interface to execute a
proprietary Ericsson presentation and session layer
 UPG node
› Ericsson implementation of
3GPP Generic User Profile
(GUP)
– Exposes consolidated virtual user
profile
– Hides underlying network complexity
– Isolates applications from changes
– Offers a single point of access for
applications towards multiple data
sources
– Aggregates data and transforms them
into suitable data views for
applications
– Offers an unified way of accessing,
managing and transfer static and
dynamic user data
SAPC-FE Node
SAPC in UDC
SOLUTION • Ericsson Service-Aware Policy Controller
(SAPC)

• Central policy node in the operator’s

network
CUDB
• SAPC includes the functionality defined in
the Policy and Charging Rules Function

SAPC • SAPC enables the applicability of

FE subscriber and service centric Policy
Control. The main enabled policy types are
related to service access control, Quality of
Service Control and charging control.
GGSN MSER
/SASN
 EIR-FE NODE
› EIR is a 3PP product

› EIR-FE is the component in

SAPC-
UDC that allows a network EIR-FE FE

operator to control and restrict

access to their CUDB
GSM/WCDMA/LTE network M2M-FE AUC-FE
for specific User Equipment.
IPWorks-FE node - AAA module
Redundancy in All Layers
Traffic cases
Location Update
How to update MS location
6 3 4

HLR- 1. Do a Location update (LU) of MS

CUDB CUDB 5 FE
(i.e. switch on the mobile phone)
2 7 2. LU is distributed to an HLR-S
3. HLR-S requests and downloads the
Subscriber data from CUDB
4. HLR-S processes the LU
MSC
5. HLR-S stores the new Location data
(VLR address) in the CUDB
6. Subscriber data change is replicated to
other CUDB nodes
7. HLR-S sends Insert Subscriber Data
MS BSC
(ISD) message to the VLR and
1 terminates the location update
operation
Call Establishment
Establish a call between two MS
3
located in different MSC/VLR
1. MS1 calls MS2
HLR-
CUDB FE 2. MSC1 sends SendRoutingInfo (SRI) to
2 5
HLR-S
6 4
3. HLR-S requests and downloads the B-
7
subscriber data from CUDB by a
LDAPsearch message.
MSC1 MSC2 4. HLR-S processes the received data
and sends a ProvideRoamingNumber
(PRN) to VLR where MS2 is located
(MSC2)
5. VLR sends the PRN response with the
BSC1 BSC2 Roaming number.
MS1 MS2
1 6. HLR sends SRIres with the Roaming
Number to MSC1.
7. Call is established.
Short messages
Send an SMS between two MS
5 located in different MSC/VLR
HLR- 1. Send an SMS from MS1 to MS2.
CUDB FE
2. SMS center receives the SMS and
4
6 queues it
3. SMSC forwards terminated SMS
2 7
SMS to MSC
center
4. Send Routing Info (SRI) for SMS
3 MSC1 MSC2
5. HLR-S requests and downloads
the Subscriber data from CUDB
6. Forward information (located in
MSC2)
BSC1 BSC2
7. Forward SMS
MS1 MS2
1 8 8. MS2 receives the SMS
Authentication process
Send Authentication Information
1. Send Authentication Information
CUDB
(SAI) message to HLR-FE
2 4 2. HLR -FE by LDAP search
message fetch the correct
subscriber
3
3. HLR ask AuC to Generate the
HLR- AuC- Authentication Vectors
5
FE FE 4. AuC Subscriber Profile is
downloaded from the CUDB
6 1
5. Decryption of eKi and
generation of Authentication
Vectors
GMSC/ MSC/ 6. HLR-FE sends the SAI
SGSN response with the
VLR VLR
Authentication Vectors
Link failure between
HLR-FE and primary CUDB
Support HLR-FE to CUDB primary link failure

CUDB
21
HLR-
FE MSC1

CUDB
22

MS1 BSC1 MS2

› If the HLR-FE - CUDB primary link is down, the secondary link is activated

› When the link is recovered the status of the links is not changed
CUDB SPLIT BRAIN Management
Majority / minority
CUDB SYSTEM

SYSTEM IN MAJORITY
CUDB #1
Site 1

IP Backbone
CUDB #3

Site 3
MINORITY

CUDB #2
Site 2
CUDB SPLIT BRAIN Management
EVEN SPLIT
CUDB SYSTEM

EVEN SPLIT
SITUATION
CUDB #1
Site 1
CUDB #3

IP Backbone Site 3

CUDB #4
CUDB #2
Site 2 Site 4
CUDB SPLIT BRAIN Management
EVEN SPLIT: IP Backbone reliability

› Three split brain situations can occur:

– The CUDB Nodes belonging to the Majority group take
all masters
– The CUDB Nodes belonging to a Minority group release
all masters
– The CUDB Node is in Even Split. Then the IP Backbone
reliability (IPBBR) is evaluated.
› If = True it is assumed that the non-reachable nodes
are really down. The CUDB takes all the masters.
Provisioning is locked
› If = False: Network communication problem. Unknown
situation of the non-reachable nodes. No changes in
master assignment
> SummaRY
Summary
 Ericsson Data Layer Architecture is the UDC solution
 New protocols, LDAP and SOAP are introduced in Core
Network for this solution
 The cornerstone component of UDC is the Centralized User
Database (CUDB)
 Provisioning Gateway node will be the single point of
provisioning for this solution
 The Front End nodes for this solution are HLR –FE, AUC –
FE, MNP –FE, M2M –FE, HSS –FE, SLF –FE, SAPC-FE,
IPWorks-FE and EIR-FE
 This is a redundant solution at all the levels
 Some traffic cases reviewed, including the CUDB even split
handling
 More Information
› Check the Nodes specific Trainings in Ericsson Academy:
– CUDB Technical Course
– CUDB Operation and Maintenance Course
– CUDB Installation Course
– HLR Technical Course
– HSS Technical Course
– PG Technical Course
....and many more!