A Telco-grade database to store all users & IoT subscription data, with real-time characteristics, data consistency and high capacity with optimal footprint.
Laying in the heart of Ericsson’s Data Management solution, the Centralized User Database (CUDB) is a flexible high-capacity, highly robust and high-performance database that consolidates subscriber profile data from all users and IoT devices in the network.
Being able to store profile data for 2G, 3G, 4G, IMS, VoLTE, Wi-Fi, Fixed and IoT as well policing and charging data between others, the CUDB is a very flexible and scalable distributed database system that offers excellent TCO figures and that can boost the Time-to-Market (TTM) for new services launch in your network.
CUDB is fully aligned to 3GPP User Data Convergence TS 23.335 standard and communicates with all application front ends through standard LDAP (Lightweight Directory Access Protocol) and SOAP (Simple Object Access Protocol). Its data model comes ready to support the most common subscription and device management applications like HLR, HSS, AuC, MNP, AAA, ENUM, PCRF and EIR. Also, thanks to its extendibility new applications front ends can be easily integrated to the database making it a very flexible and cost efficient solution to support new network’s needs.
Data consistency and durability are critical in distributed subscription management database systems. With operators concerns in mind, Ericsson has implemented the most advanced replication mechanisms to secure that data is trustable at all times in a CUDB system no matter from which node in a CUDB system an application front end fetches data. Moreover Ericsson has gone one step further to provide additional mechanisms to ensure data consistency in specific failure situations by checking and restoring the consistency of replicas automatically if necessary after network isolation situations.
Equipped with a common provisioning interface, all data is provisioned to the system in a secure way so it is validated and synchronized between the application front ends and the database and thanks to the Ericsson’s unique flexible and highly configurable Notifications Framework, the CUDB can inform the application front ends about certain data updates, for them to take proper action towards the network.
As being the heart of the subscription management system in telecommunication networks and responsible to provide user’s and M2M/IoT devices access to the different network services, the centralized database availability is of vital importance. The Ericsson CUDB implements not just the most advanced mechanisms for resilience and redundancy following telecom market standards but Ericsson has gone the extra mile to provide a unique state-of-art overload protection and load regulation mechanism in its centralized data management system, so called Ericsson User Data Consolidation (UDC) where CUDB plays a central role. This allows an e2e congestion control by means of a real-time cooperation mechanism between the CUDB and the Ericsson application front ends to maximize the database performance under signaling storms. Read more about this unique Ericsson functionality. (add hyperlink to the brochure).
No network is unique and each operator has different deployment requirements and needs. To cope with that CUDB offering is highly flexible in terms of sites & subscribers distribution and redundancy level. Moreover, CUDB can be deployed as a native stand-alone application, native co-located with other Ericsson applications or as a virtualized network function. This makes Ericsson CUDB a unique product in its market category.
Contact your local Ericsson sales representative for more information.
The Ericsson Unified Data Management solutions help network operators to address the IoT challenges on connectivity, security, adaptability and analytics to implement a profitable IoT strategy. Check out this new brochure.
Imagine what you could do with a full multi-access data management solution that can also provide you a 360 degrees view of your user’s data assets - all in just one “box”?