2.2.1 SDS Components
SDS
The SDS has one active and one standby server running the SDS application and operating in a high availability configuration. It accepts subscriber data provisioned by the customer over SOAP or XML and replicates it to the DR SDS, the Query server, and all underlying servers. It also provides a GUI, which is used for configuration, user administration, and viewing alarms and measurements.
SDS distributes all successful incoming subscriber provisioning data, independent of source, to all downstream Network Elements (NEs) and to the DR SDS at a rate of up to 200 provisioning database updates per second. To ensure the database levels of the NEs are less than the database levels of the SDS and DR SDS, the active provisioning site SDS provisions the DR SDS before updating the NEs.
DR SDS
The DR SDS is a geographically independent SDS component. The DR SDS has the same hardware configuration and network accessibility as the primary SDS.
The DR SDS's databases are kept updated through real-time replication of subscriber and application data from the active primary SDS. Under normal operating conditions, the DR SDS does not provision any downstream systems, but if made active, it takes over all the functions of the active SDS including the provisioning and database replication to underlying DP SOAMs.
DP SOAM
The DP SOAM is the combination of an active and a standby application server running the DP SOAM application and operating in a high availability configuration. It accepts subscriber data replicated from the active primary SDS and in turn replicates it to all underlying DPs located in the same physical site. DP SOAM also provides a GUI used for viewing alarms and measurements details specific to components located within the site (DP SOAM, DP).
The DP SOAM supports up to 10 DPs.
Query Server
The Query server is an independent application server containing a replicated version of the provisioning database. It accepts replicated subscriber data from the active primary SDS and stores it in a customer accessible SQL interface. A Query server is located in the same physical site as each SDS component (SDS/DR SDS).
Network Element
- SDS: such as the SDS and the DR SDS
- DP SOAM: contains a pair of DP SOAM servers and one or more DP servers
The system can support two SDS NEs and up to 32 DP SOAM NEs.
DPs
The Data Processors (DPs) are servers with the SDS application installed that are configured for DP functionality. They accept replicated subscriber data from the local DP SOAM and store it in a subscriber database.
The DPs are used for processing queries from the Message Processor (MP) for destination address resolution. DP receives database queries that include user identities such as MSISDN, IMSI, URI, or External Identifiers, and destination types and return the resolved destination’s address FQDN and/or realm values.
Each Signaling Site can support multiple DP servers deployed at a single site to scale query capacity (by increments of 140,000 QPS per DP). Each Signaling Site can support up to 10 DPs.
The DP servers all contain a copy of the same SDS data. They are configured in an active/active mode. The MP is responsible for load-balancing requests across DP servers.