The DSC provides for the needs of hub providers and wholesale interconnect operators. Individual clients of the hub provider are managed with individual routing table and configuration databases. Within these databases, the DSC allows for up to 32 independent Diameter nodes, each with its own Diameter IDs and IP addresses. 

In the example shown in the following figure, there are two DSC instances running on each Routing CPU or Routing VM. Within Instance – A, there are two Diameter nodes running. One acts as a DEA and one acts as a DRA. These entities have their own Diameter ID and separately provisioned Adjacent Diameter Nodes (ADNs), which both share a routing table database. The routing can be distinct in this case because the routing table tree can start with a search for the given incoming Diameter ID. 

The second instance, DSC Instance – B, has its own routing tables as well as separate statistics and peg counters. In this case, the user elects to run the DEA function and the DRA function as one node under the same Diameter ID.

Example of Three Diameter Nodes Across two DSC Instances

It is expected that in a hub provider environment, one instance is dedicated to each carrier customer to act as a Diameter Edge for this customer. One central instance for the hub provider joins these together. 

Diameter messages can be copied through the XML interface(s) for billing purposes. For more information about the XML interface, refer to the XML Application Programming Interface User Guide.

The Diameter Roaming Hub has connections to other carriers and other hub providers. In its routing and configuration tables, it can do the following:

  • Sets rules that define which carriers can roam and with whom.

  • Each DSC instance can create separate statistics and peg counters on 1000s of different combinations of the messages (for example, counting messages between two carriers).

  • Throttle messages coming from or to specific carriers.

  • Copy messages to external systems for downstream billing creation.

Up to 32 independent Diameter nodes can exist in each DSC instance. Each routing node is a separate entity but runs in the same software process. This same process is replicated on each CPU (DSC 8000) or VM (DSC SWe). The processes discover their corresponding peers on other CPUs or VMs to exchange information concerning configurations, states, and message routing between them.

 

  • No labels