In this section:

One to one public topology mapping and one to N public topology mapping are supported for the Ribbon DSC. These topology mapping scenarios apply to both request and answer Diameter messages. Changes are applied to the host part of the Diameter ID. 

Topology One to One Public Mapping

Configuring a one to one Topology Mapping Record allows replacement of the DID Host Name, the Realm Name, or both of them with an Alias. The Public DID (Public DID Host + Public Realm) replaces the Private DID (Private DID Host + Private Realm) when this message leaves the Realm and vice versa when the message enters the Real.

Topology One to N Public Mapping

For Mobility Management Entity/Home Subscriber Server (MME/HSS) S6a/S6d and MME/Equipment Identity Register (EIR) S13/S13 message flows, one private to N public obfuscation is supported. In this topology mapping scenario, the Public DID Host Name is a combination of a base value and a numeric suffix. The base value can be shared among multiple rows (records) in the Topology Mapping Table, but the suffix must be unique. The base value must also not end with a digit.

For example, protected Realm “A” contains three Mobile Management Entities (MMEs) each with the same base value “mme” but suffix values “1-5”, “6-10”, “11-15”. Outside Diameter Nodes see the protected DSC Nodes as “mme1” to “mme15”.

Note

Topology Hiding is a resource-intensive feature and, therefore, using this feature may impact system performance.

To create a Topology Mapping Table

Click to read more...

To view a Topology Mapping Table

Click to read more...

To create a One to One Public Mapping (Record)

Click to read more...

To create a One to N Public Mapping (Record)

Click to read more...

To configure a One to One Public Mapping (Record)

Click to read more...


To configure a One to N Public Mapping (Record)

Click to read more...