udc overview

USER DATA Consolidation

Beijing, February 2012JOSE ANTONIO DIAZUDM Services Engineer

Slide title minimum 32 pt

(32 pt makes 2 rows

Text and bullet level 1 minimum 24 pt

Bullets level 2-5minimum 20 pt

!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵŶŷŸŹźŻżŽžƒȘșˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–—‘’‚“”„†‡•…‰‹›⁄€™−≤≥fifl

ĀĀĂĂĄĄĆĆĊĊČČĎĎĐĐĒĒĖĖĘĘĚĚĞĞĠĠĢĢĪĪĮĮİĶĶĹĹĻĻĽĽŃŃŅŅŇŇŌŌŐŐŔŔŖŖŘŘŚŚŞŞŢŢŤŤŪŪŮŮŰŰŲŲŴŴŶŶŹŹŻŻȘș

ΆΈΉΊΌΎΏΐΑΒΓΕΖΗΘΙΚΛΜΝΞΟΠΡΣΤΥΦΧΨΪΫΆΈΉΊΰαβγδεζηθικλνξορςΣΤΥΦΧΨΩΪΫΌΎΏ

ЁЂЃЄЅІЇЈЉЊЋЌЎЏАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯЁЂЃЄЅІЇЈЉЊЋЌЎЏѢѢѲѲѴѴҐҐәǽẀẁẂẃẄẅỲỳ№

Do not add objects or text in the footer area

Ericsson Internal | 2011-02-02 |

Agenda

› User Data CONSOLIDATION values› UDC Functional View› UDC Interfaces› UDC Product View› UDC Hardware Overview› Redundancy in UDC› UDC Data Model› UDC Traffic Use Cases› UDC Provisioning Use Cases


(32 pt makes 2 rows









Clients

Subscriber Database Evolution

HLRHLR

HLR

EIRAuC

PresenceAAA Location

MMS

Device MgtStreaming

PoCAS

Core Networkdomain

Servicedomain

Provisioning

CommonSubscriber

DB

interworking

interworking

HSSHSS SLF

Radio Accessdomain

Centralizationprovides flexibility reduces complexity

MNP

BSC RNC

PresenceAAA Location

MMS

Device MgtStreaming

PoCAS


(32 pt makes 2 rows









UDC values› User Data Consolidation (UDC) is a real time telecommunication

system product supporting the following technologies: GSM, GPRS, WCDMA, LTE/eUTRAN, WLAN or any type of wireline.

› UDC implements the 3GPP providing the capability of managing CS, PS, IMS, LTE/EPC and non 3GPP WLAN networks domain.

› UDC supports a layered architecture, separating the data from the application logic, so that user data is stored in a logically unique repository allowing access from core and service layer entities, named application front-ends.

› CUDB is the data repository and HLR/AuC Server and HSS-FE are the application FEs -> UDC Layered ConfigurationUDC Layered Configuration includes deployments of CUDB, PG, HLR/AuC Server and HSS/SLF FE

› UDC also supports the combination with classic FNR, HLR and HSS nodes in a non layered architecture -> UDC Classic Configuration


(32 pt makes 2 rows









HLR/AuC Evolution

DB

Ericsson evolved HLR

Classic HLR/AuC node

HLR FE

HLR/AuC

OA

M

PROTOCOLS

LOGIC

DB

HL

R n

od

e

OA

M

PROTOCOLS

LOGIC

HL

R A

pp

lica

tion

Signalling &

application logic

DBHLR DB

CU

DB

From Monolithic to UDC


(32 pt makes 2 rows









Data Layered Architecture valuescustomer Perception

Centralized storage•Storage administration effectiveness•Optimized storage upgrade e.g. version control, change control•Improved data availability•Lower SW and HW maintenance cost•Backup improvement

Simplified user &service provisioning Easy access to end-user data

OPEX

Optimized use of the network resources•Independent scalability of data storage and traffic

Low price HWCAPEX

Easy integration of new applications and services•Simplified user & service provisioning•Easy access to end-user data

TTM

Data mining

Enhanced monitoring of subscriber behavior•To customize and push services to the end users base on usage,

habits,.


(32 pt makes 2 rows









Agenda

› User Data CONSOLIDATION values› UDC Functional View› UDC Interfaces› UDC Product View› UDC Hardware Overview› Redundancy in UDC› UDC Data Model› UDC Traffic Use Cases› UDC Provisioning Use Cases


(32 pt makes 2 rows









UDC LAYEREDFunctional Architecture

Circuit Switch& Packet Switch

Core Network(MSC, IN, GGSN, SGSN, etc.)

IMSCore Network

and Service Layer(CSCF, AS, etc.)

Load Distributor

Front End Cluster

Partitioning Layer

Data Storage

Pro

cess

ing

Lay

erD

ata

Lay

er


(32 pt makes 2 rows









SS,PD

Partitioning Function

Data Store Data Store

UDC Layered Architecture

Data StorageLayer

Circuit Switch & Packet SwitchCore Network

(MSC, IN, GGSN, SGSN, etc.)

Partitioninglayer

OperationalSupportSystem(OSS)

Distributionlayer

LD HLR

Applicationlayer

NetworkapplicationsHLR/AuC-

FEPS HSS FEMNP

SLF

IMSCore Network


CAS /Mediation System


(32 pt makes 2 rows









UDC LayeredLoad Distributor for HLR-FE


Core Network(MSC, IN, GGSN,

SGSN, etc.)

Signalling Distribution LD HLR

Network applications

HLR/AuC FEProvisioning server



Load Distributor

• Entry point for Core Network incoming traffic

• Distributes Core Network transactions to available HLR/AuC FEs

• Any traffic request for any subscriber can be distributed to any HLR/AuC FE

• Enables scalability and redundancy of the HLR/AuC FE pool.

• Subscriber agnostic. Not impacted when adding new subscribers

• N+Red mechnicas

IMSCore Network


SLF

HSS-FE


(32 pt makes 2 rows









UDC LayeredHLR/AuC Front Ends

HLR/AuC Front Ends

• Provide HLR/AuC Business Logic

• Stateless (any front end can serve any request, user data are not retained)

• Serves single transaction

• FE redundancy and scalability handled by additional FEs (viewed as adding FE capacity)

• Implements the HLR/AuC provisioning validation logic.

• Implements network notification function due to provisioning



SGSN, etc.)

Signalling Distribution

LD HLR


HLR/AuC FEProvisioning

Server



IMSCore Network


SLF

HSS-FE


(32 pt makes 2 rows









UDC LayeredProvisioning server

ProvisioningServer

• Single point of provisioning for UDC

• Terminates the provisioning protocol from CAS/Mediation System

• Controls the validation for the provisioning requests

• Stores data in Data Layer

• Notifies HLR/AuC FE regarding changes once they are consolidated in the Data Layer

• HSS Validator plugin

• Judgement&Notification node (for HLR/HSS)



SGSN, etc.)




Server



HSS

SLF

IMSCore Network


HSSHSS

SLF

HSS

SLF

HSS

IMSCore Network


SLF

HSS-FE


(32 pt makes 2 rows









UDC LayeredPartitioning Function


• Implements Access Point for all subscribers

• Hides the structure of the data storage layer

• Locates appropriate data store for the subscriber data request

• Provide protocol translation if needed.

• Register msisdn,imsi.and use it (Have a index) to find out PD in Data store.



SGSN, etc.)




Server



IMSCore Network


SLF

HSS-FE


(32 pt makes 2 rows









UDC layeredData Storage Layer

Data Storage Layer

• Contains the entire Subscriber Database

• Based on Commercial component (MySQL Cluster Grade Edition)

• Reliable data storage (ACID assurance)

• Real time data hosting

• Provides High availability, high scalability and geographic replication



SGSN, etc.)




Server



IMSCore Network


SLF

HSS-FE


(32 pt makes 2 rows









Agenda

› User Data Register values› UDC Functional View› UDC Interfaces› UDC Product View› UDC Hardware Overview› Redundancy in UDC› UDC Data Model› UDC Traffic Use Cases› UDC Provisioning Use Cases


(32 pt makes 2 rows











UDC Interfaces and protocols

Datastore



SGSN, etc.)

Partitioninglayer

CAS

OperationalSupportSystem(OSS)

Distributionlayer

DistributionFunction

SD

Applicationlayer

Networkapplications


Server

MAP

1

MAP2

4

3

MML

5

LDAP

6

7

SNMPTelnet

ftp,SSH,

MMLLDAP

CAI3G, CLI, MML

HSS-FE

EPC/LTE(MME)

LDAP

Diameters6a

LDAP

3

9

IMS / WLAN

10

DiameterCx/

Radius

8

SOAPSOAP

SLF


(32 pt makes 2 rows









UDC interfaces and protocols

1. CN nodes - LD: MAPUsed by CN nodes (MSC, GSN, SMS-C, …) to access the HLR

2. LD – HLR/AuC FE: MAPUsed by the LD to deliver the request to the selected FE

3. HLR/AUC and HSS FE – CUDB: LDAPUsed by the HLR/AuC FEs to access the data layer

4. CAS – Provisioning Server: CAI3G, CLI, MMLFor the provision commands for the data layered architecture

5. Provisioning Server – HLR/AuC FE: MML

Used by the PG/PS for validation and notification request to the HLR/AuC FEs

6. Provisioning Server – CUDB: LDAP

Used for accessing application data stored in CUDB to create, read, modify and delete user data

CUDB – PG/PS notifications: RMI

Used to inform PG/PS that a backup procedure in CUDB is going to start

7. OSS – UDC components: SNMP, Telnet, sftp, SSH

Used for O&M purposes: FM, CM, PM, SM


(32 pt makes 2 rows









UDC interfaces and protocols

8. PG - HSS : SOAP

Used for notification of data changes towards HSS-FE

8. CUDB - HLR : SOAP

Used for notification messages due to SAE Mobility Management function

9. HSS – LTE/EPC: S6a Diameter

Used for generation and provision of user authentication, integrity and ciphering data and to update user location information

10. IMS CN (CSCF or MTAS) - HSS: Cx/Sh Diameter

Used for network (de)registration, location information retrieval, Security Information exchange, User Profile information exchange for authorization

10. WLAN - HSS: RADIUS

Used for Access authentication to the WLAN network.


(32 pt makes 2 rows









Agenda



(32 pt makes 2 rows









Load Distribution for HLR-FE (I)› Load Distribution in UDC for the pool of HLR/AuC FE is a functionality

implemented on signalling network level (i.e. using signalling routing mechanisms).

› The implementation of the LD functionality depends on the customer’s specific signalling strategy and the signalling capabilities of the nodes interworking UDC.

› Load Distribution might not require any additional node in the customer’s network depending on the present routing capabilities

› In case that customer’s network does not provide the needed routing capabilities for UDC, Ericsson could provide a Load Distribution solution based on STP (AXE based)

› STP will be enhanced with an extension of current M3UA signalling capabilities (extension to 16 M3UA routes in load sharing mode)

› Enhanced STP is delivered within R13.2 release (CN-I)

› Two main scenarios are identified:

– Scenario A: STP based signalling hierarchy towards UDC– Scenario B: All-IP based signalling towards UDC


(32 pt makes 2 rows









Load Distribution (II)Scenario A. stp based

SGSN

STP

MSC GMLC

STP

HLR FE HLR FE HLR FE HLR FE HLR FE HLR FE HLR FE HLR FE

MSC

STPSTP

GMSC SMS

› All traffic towards UDC will be routed through the STPs

› The STPs will distribute messages corresponding to new transactions towards an available HLR/AuC FE

› Subsequent messages within one transaction will be sent directly to the selected HLR/AuC FE


(32 pt makes 2 rows









Load Distribution (IV)Scenario A. STP based

MSC/SGSN

LD(STP)HLR/AuC

FE 1

New MAP operation

HLR/AuC FE 2

HLR/AuC FE N

FE selectionRound Robin based

HLR/AuC FE 2selected

New MAP operation

…

IMSIMISDNHLR number

MAP operation Response

MAP operation Continuation

MAP operation Termination

- A new transaction (MAP operation) can be served by any HLR/AuC FE.

- A single transaction is served by one and the same HLR/AuC FE

HLR/AuC FE2 SCCP Address included in Calling Party Address


(32 pt makes 2 rows









Load Distribution (IV)Scenario B. All-IP

SG SNMSC GMLC

HLR F E HLR F E HLR F E HLR F E

MSC GM SC SM S

Tra ffic Handlin gSignalin g

IP Backbo ne

› All traffic towards UDC will be routed directly in the originating nodes towards the HLR/AuC FE pool.

› Originating nodes shall be capable to distribute messages corresponding to new transactions towards an available HLR/AuC FE in load sharing mode.

› Subsequent messages within one transaction will be sent directly to the already selected HLR/AuC FE


(32 pt makes 2 rows









HLR/AuC FE (AXE)

Adm

inistration

HLR/AuC FE

IO S

ystem

AP

G/IO

G

CPAPZ 212 3x, 40, 50, 55, 60

RP

A

uC

RP

A

uC

RP

S

ig

RP

S

ig

……

GA

RP

2 L

DA

P

GA

RP

2 L

DA

P

GA

RP

2 L

DA

P

GA

RP

2 L

DA

P

…

LDAP

SS7

MML

HLR/AuC FE can be AXE based

Running on APZ 212 30, 33, 33c, 40, 50,55 and 60

GARP2 boards are needed to implement LDAP i/f

HLR/AuC FE is delivered within 11B release


(32 pt makes 2 rows









HLR/AuC FE (BLADE SERVER)

HLR/AuC FE can be EBS based

Running on IS and AXE (APG)

HLR/AuC FE is delivered within 11B release


(32 pt makes 2 rows









Provisioning SERVER (I)

Load Balancers + Switches (optional)

Expansion

Servers(SB6000)

PS functionality in UDC is implemented in a feature in the EMA product family, called Provisioning Gateway (PG)

PG feature can be deployed as an optional feature in CUDB or together with Classic EMA.

PG runs in different platforms:

- PG can run on OEM platform HW (Sun Blade X6270m2), with LOTC as Operating System.

- PG can run on EBS platform HW, with LOTC as Operating System. Same platform as CUDB 11B.

NWIs + SCXB2

Expansion

Servers(GEP3)

OEM

EBS


(32 pt makes 2 rows









Provisioning SERVER (II)Interfaces

HLR/AuC FE

CUDB

MML

LDAP

CAS /Mediation System

CAI3G/MML

ProvisioningServer

CLI

OSS

SNMP/GUI/CLI

EMAEMA

CAI3G

CAI

GUI

HSS FE

LDAPMML


(32 pt makes 2 rows









CUDB – DATA LAYER

› Partitioning Function and Data Storage Layers in UDC/UDC are implemented by the Centralized User DataBase (CUDB) system.

› CUDB is an extensible, networked high-performance, distributed database.

› CUDB system is made up of a set of ”CUDB nodes”

Each CUDB node provides an Single Point of Access (SPoA). That means that a client accessing a CUDB node (e.g. HLR/AuC FE, HSS-FE, PG) can access any subscriber stored in the CUDB system.

CUDB (System)

CUDBnode

CUDBnode

CUDBnode

IPnetwork

LDAP

LDAPLDAP

LDAPclients

LDAPclients

LDAPclients

LDAPLDAP

LDAP

SPoASPoA

SPoA


(32 pt makes 2 rows









Agenda



(32 pt makes 2 rows









Ericsson blade server (EBS)from 11B release

EGEM2 subrack-0

EGEM2 subrack-1

Components› 1 Ericsson BYB 501

cabinet› 1-3 subracks EGEM2

including Power and Fan Modules (PFM)

› 8-34 GEP3 blade servers › 2-6 SCXB2 boards (2 per

subrack) › 2 NWI-E switches with

Summit X450a Core License for routing


(32 pt makes 2 rows









HLR/AUC FE – hardware view (AXE)

Cabinet layout for APZ 212 55/60

› HLR/AuC FE can be AXE based› The GEM-0 subrack is equipped with 2+1

GARP-2 for LDAP. The GEM can also additionally be equipped with up to 21 GARP boards used for additional support of LDAP, Signaling over IP or AUC.

› GEM-1 is optional and can be used for TDM signaling supporting up to 2+2 STM-1/OC-3, 1024 C7/S7 or 48 HSL.

Fan

Fan

GEM 0

Fan

APZ 212 55/60 APG43

Fan

Fan

GEM 1

Fan


(32 pt makes 2 rows









HLR/AUC FE - HARDWARE VIEW (EBS)

› All HW is housed in one BYB 501 cabinet. The cabinet dimensions is 1800x600x400 mm

› HLR-BS will use platform releases APZ 17 and IS3.1. APG43 not integrated in IS:

› Therefore, the cabinet will be composed of:–AXE subrack (on EGEM) for SPX/APG– IS subrack (on EGEM2 (BFD 538))Doesn’t support TDM based Signaling


(32 pt makes 2 rows









Agenda



(32 pt makes 2 rows









Circuit Switch & Packet Switch Core Network(MSC, IN, GGSN, SGSN, etc.)

Multiple Site HLR/AUC-FEs to minimize site failures effects.

HLR/AUC-FE N+K Redundancy

CUDB assures Data consistency.

1+1 or 1+1+1 Redundancy

1+1 Signalling Redundancy

Site #1

DS-cluster

DS-cluster

PL-cluster

Site #2

DS-cluster

PL-cluster

Site #3

DS-cluster

DS-cluster

PL-cluster

Site #4

DS-cluster

PL-cluster

DS-cluster DS-clusterDS-cluster

DS-cluster DS-cluster DS-cluster

replication

replication

replication

replication

replication

replication

replication

replication

replication replication

replication

HLR/AUC FEHLR/AUC

FEHLR/AUC

FE

HLR/AUC FEHLR/AUC

FEHLR/AUC

FE

STP

STP

STP

STP

This solution provides high disaster resilience

Redundancy in UDC (CS & PS CN)


(32 pt makes 2 rows









Agenda



(32 pt makes 2 rows









UDC Data Model

Directory Information Tree


(32 pt makes 2 rows









Agenda



(32 pt makes 2 rows









Traffic Case – HLR-FENo subscriber data updates

Send Routing Information

GMSC LD HLRHLR FE

CUDB

SRI

LDAP Search (IMSI)

LDAP Search Result

PRN

PRN rsp

SRI rsp

VLR

SRI


(32 pt makes 2 rows









Traffic Case – HLR-FESubscriber data updated

UEMSC(new)

LD HLRHLR/ FE

CUDBMSC(old)

LU request LU request LU requestLDAP Search (IMSI)

LDAP Search Result

Cancel LocCancel Loc

Cancel Loc rspCancel Loc rsp

ISD

ISD Rsp

LDAP Modify (MSISDN)

LDAP Modify ResultLU rsp

LU rspLU rsp

Location Update


(32 pt makes 2 rows









Traffic case HSS (IMS):initial registration

UE CSCF HSS-FE1 CUDBSLF HSS-FE2SIP register

Cx UAR SLF acts as LB and sends operation to HSS-FE2

Cx UAR LDAP searches

LDAP srchs resultUser data is fetchedCx UAA

Cx UAA

Cx SAR

Cx SAA

SIP register OK

Cx SAR

LDAP modify

LDAP mod result Modification of IMPU state

Cx SAA

Cx MAR

LDAP modify

LDAP mod result Authentication and CSCF id inserted

Cx MAACx MAA

Cx MAR


(32 pt makes 2 rows









Agenda



(32 pt makes 2 rows









ProvisioningSET Use Case (HLR)

EMA/MS PGHLR/

AuCFECUDB

FE selectionRound Robin

based

CAI3G

Validation ReqMML

Validation AckPrintout_MML

HLR/AuCFE

LDAP Search

LDAP Search_Rsp

LDAP Modify

LDAP Modify_Rsp

….

Notification ReqMML (HEPPE)

NetworkNotificationNotification Ack

CAI3G resp

CAS

...

CAI

CAI resp


(32 pt makes 2 rows









ProvisioningGET Use Case (HLR)

EMA/MS PGHLR/

AuCFECUDB

CAI3G

HLR/AuCFE

LDAP Search

LDAP Search_Rsp

….

CAI3G resp

CAS

...

CAI

CAI resp


(32 pt makes 2 rows









ProvisioningMassive Search (HLR)

PGHLR/

AuCFECUDB

LDAP Search (Filters)

LDAP Search_Rsp

CAS

CMD_MassiveSearchFiltering_Criteria

[CLI]

LDAP Search_Rsp

LDAP Search_Rsp

......

One Search response per

subscriber fulfilling the entry criteria

Results are compiled in file

Process completed

Example: Get the list of subscribers with CFU


(32 pt makes 2 rows









ProvisioningMassive Updates (HLR)

PG HLR/AuCFE

CUDB

LDAP Update (Filters)

LDAP Update_Rsp

CAS

CMD_MassiveUpdatesFilteringCriteria

[CLI]

LDAP Update_Rsp

LDAP Update_Rsp

......

One Update response per

subscriber fulfilling the entry criteria

Results are compiled in file

Process completed

Trigger an individual provisioning process for each of the subscribers compiled in the obtained file

One search is raised with subscriber pattern criteria

One search is raised with subscriber pattern criteria

udc overview

Documents