1. Diameter Common User Guide
  2. Diameter Common on the NOAM
  3. MCCMNC Mapping Configuration

MCCMNC Mapping Configuration

The Diameter Common, and then Network Identifiers, and then MCCMNC Mapping pages are used to configure mapping of MCC+MNC combinations to Diameter Realms, MSIN prefix digits, and CC+NDC combinations.

The MCC+MNC combinations must first be configured using the Diameter Common, and then Network Identifiers, and then MCCMNC pages (see MCCMNC Configuration) before the MCCMNC Mapping configuration is performed.

MCCMNC combinations and MCCMNC Mapping are used by:
  • The MAP-Diameter Interworking Function to translate:
    • A Diameter Request message to a MAP Request message (ITU)

      If a Diameter Request message does not contain a Destination Host AVP, but does contain IMSI digits in a User-Name AVP, the MCCMNC Mapping configuration is used to translate the MCC and MNC in the IMSI to the CC and NDC that are populated in the SCCP Called Party Address (CdPA) of the MAP Request. A longest prefix match of IMSI digits (MCC+MNC+prefix digits) is performed.

    • A MAP Request message to a Diameter Request message

      If the GTA digits are in IMSI format (for ANSI this occurs if the SCCP CdPA Translation Type is 9, and for ITU this occurs if the SCCP CdPA Numbering Plan is E.212), then the MCCMNC Mapping configuration is used to translate the MCC and MNC in the IMSI to a Diameter Realm.

      The Diameter Realm is populated into the Destination-Realm AVP of the Diameter Request message.

  • Diameter Mediation to populate the Destination-Realm AVP based on the IMSI value present in a Request message.
    Mediation retrieves the IMSI value from one of the following AVPs in the Request:
    1. Subscription-ID (Subscription-ID-Type=1)
    2. User-Name
    • The first instance of an AVP that contains an IMSI is used.
    • The Mediation Set Diameter Realm Action extracts the MCC and MNC values from the IMSI by prefix matching against the MCCMNC combinations configured on the Diameter Common, and then Network Identifiers, and then MCCMNC page. The MCC and MNC cannot be extracted from the IMSI if there is no match found on this page.
    • The Destination-Realm AVP is added or populated with the Realm that corresponds to the MCCMNC combination configured on the Diameter Common, and then Network Identifiers, and then MCCMNC Mapping page.
    • If no Realm is specified for the MCCMNC combination, the Destination-Realm is populated in 3GPP format "epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org", where <MNC> and <MCC> fields correspond to the MNC and MCC values extracted from the AVP containing the IMSI present in the Request.
    • If the Destination-Realm AVP is not present in the message, the Action adds it.
On the Diameter Common, and then Network Identifiers, and then MCCMNC Mapping page, you can perform the following actions:
  • Filter the list of entries, to display only the desired entries.
  • Sort the list entries in ascending or descending order by clicking the column heading. By default, the list is sorted by MCC and MNC in ascending ASCII order.

  • Click Insert.

    The Diameter Common, and then Network Identifiers, and then MCCMNC Mapping [Insert] page opens. You can add new MCCMNC Mapping entries. If the maximum number of MCCMNC Mapping entries (2500) already exists in the system, the Diameter Common, and then Network Identifiers, and then MCCMNC Mapping [Insert] page will not open, and an error message is displayed.

  • Select an MCCMNC Mapping entry in the list, and click Edit.

    The Diameter Common, and then Network Identifiers, and then MCCMNC Mapping [Edit] page opens. The selected MCCMNC Mapping entry can be edited.

  • Select an MCCMNC Mapping entry in the list, and click Delete to remove the selected entry.