4.1.1 SDS functionality

Subscriber Database Server (SDS) provides the central provisioning of the Full-Address Based Resolution (FABR) data. The SDS, which is deployed geo-redundantly at a Primary and Disaster recovery site, connects with the Query Server and the Data Processor Site Operation Administration and Maintenance (DP SOAM) servers at each Diameter Signaling Router (DSR) site or a standalone DP site to replicate and recover provisioned data to the associated components.

SDS provides the following functionality:

• SDS Database – Stores subscriber data needed by the FABR application
• GUI-based provisioning
• Control the Diameter Internet Engineering Task Force (IETF) specification called Diameter Routing Message Priority (DRMP) to establish relative message priorities
• Enhanced Subscriber Table add functionality
• Support SOAP over HTTP and XML over TCP as provisioning interfaces
• SQL Interface – At query server for query only
• CSV and/or XML-formatted export and import of database contents
• Real Time replication to:
  • Local standby server at Primary site
  • Local query server at Primary site
  • Each server at Disaster Recovery site
  • Each DP SOAM and DP at up to 32 sites
• DP - DB Processor – A server that has a replica of the SDS database and is available for query by FABR applications
• Automatic scheduled NPA Split processing
• Provisioning Measurements and KPIs
• Alarms, Events and Logs for all interfaces
• DB Audit - Replication audit within replicas and Active SDS, and remote audit between SDS and HLR Router
• Query server
• Backup and Restore of SDS database components
• Disaster Recovery SDS – Geo-diverse site
• Automated Performance Data Export (APDE)
• Manage and associate routing destinations for routing entities that represent Subscriber identities
• Monitor exceptions
• Subscriber identity grouping
• Blacklist support
• Address resolution – Full address, as well as prefix address support