Got it

How eCNS280 roaming with another eCNS280 each uder different PLMN

Created: Feb 16, 2020 16:42:10Latest reply: Feb 16, 2020 17:55:04 432 1 0 0 0
  Rewarded HiCoins: 0 (problem resolved)

PLMN A with eCNS280 A need to provide roaming to another eCNS280 B with PLMN B, ho wthe interworking and using which interface.

Featured Answers

Recommended answer

wissal
MVE Created Feb 16, 2020 17:55:04

Hello,
Below the initial configuration of Inter-eCNS280 Roaming in new deployment scenarios.

eCNS280 roaming with another eCNS280 each uder different PLMN

  1. Configure core network A (eCNS280A).

    1. Add an APN.

      In the MML Command - ugw window of the vUGW, run the following command to add an APN:

      ADD APN:APN=APN of eCNS280B;

      SET APNDNS: APN=APN of eCNS280B, MDNSSERVERV4=Primary DNS server IPv4 address, BDNSSERVERV4=Secondary DNS server IPv4 address;

      SET APNREPORTATTR: APN=APN of eCNS280B;

    2. Add IP address pool configurations.

      In the MML Command - ugw window of the vUGW, run the following command to add IP address pool configurations:

      ADD POOL: POOLNAME=IP address pool of eCNS280A;

      ADD POOLBINDAPN: APN=APN of eCNS280B, POOLNAME=IP address pool name of eCNS280A;

      ADD SECTION: POOLNAME=IP address pool name of eCNS280A, SECTIONNUM=IP address segment number, IPVERSION=IP address type, V4STARTIP=Starting IPv4 address of eCNS280A's address segment, and V4ENDIP=Ending IPv4 address of eCNS280A's address segment;

    3. In the MML Command - omo window of the vUSN, run the following command to configure DNS data for the APN of the roaming user:

      ADD IPV4DNSH:HSINDEX=Host name index, HOSTNAME=Host name, ADDRSECTION=IP address segment, IPV4ADDR1=IP address of the S5/S8 interface of the PGW on eCNS280A

      note_3.0-en-us.png

      HSINDEX in ADD IPV4DNSH corresponds to HSINDEX in ADD DNSN.

      ADD DNSN:FQDN=FQDN,HSINDEX=Host name index, ENTITY=NE type, INTYPE=Interface type, S5PROTOCOL=S5 interface protocol type;
      • Set ENTITY to PGW.
      • If the core network B and core network A are in different PLMNs, set the INTYPE to S8 in ADD DNSN.
      • If the core network B and core network A are in the same PLMN, set the INTYPE to S5 in ADD DNSN.
      • FQDN specifies an NE's fully qualified domain name, which is composed of RAI, TAI, APN, and MME ID. The FQDN is used to query NEs such as the SGSN, MME, S-GW, P-GW, or IWS. An FQDN is composed of the following IEs: P-GW(APN): <APNNI>.APN.EPC.MNC<MNC>.MCC<MCC>.3GPPNETWORK.ORG

        Example: COMPANY1.COM.APN.EPC.MNC001.MCC308.3GPPNETWORK.ORG

        note_3.0-en-us.png
        • This parameter can contain only letters, digits, periods (.), and hyphens (-).
        • <MNC> and <MCC> are both a 3-digit decimal number and <CELL ID> is a 4-digit decimal number.
        • The number in each <> field except that in <APNNI> must meet the specified number of digits. If there are less digits in each field, 0s must be added in the front until the required number of digits is met.
        • The FQDN cannot start or end with a period (.).
    4. Configure S6a interface data.
      1. Configure S6a interface basic data.

        In the MML Command - vnrs window of the vUSN, run the following command:

        SET BFD: BFDENABLE=TRUE;

        SET AUTOCONFIG:SWITCHFLAG=FALSE;

        ADD AUTOSCALINGSERVICE:SERVICENAME=Service name,AFTYPE=IPv4,IPALLOCTYPE4=USER_CONFIG,VNICID=VNIC ID,VLANID=VLAN ID,BEGINADDR4=Begin address,ENDADDR4=End address;

        ADD AUTOSCALINGSRBFD: SERVICENAME=Service name;

        ADD AUTOSCALINGSRROUTE: SERVICENAME=Service name, IPVERSION=IPv4, PREFIX4=Route prefix IPv4, MASKLENGTH=32, NEXTHOPALLOCTYPE4=CONFIG, NEXTHOP4=Route next hop IPv4, BFDENABLE=TRUE;

        SET AUTOCONFIG:SWITCHFLAG=TRUE;

      2. Configure parameters related to the service IP address.

        In the MML Command - omo window of the vUSN, run the following command:

        ADD SERVICEIP:IPVERSION=IPv4, SERVICEIPV4=Service IPv4 address of eCNS280A;

      3. Configure SCTP link parameters.
        note_3.0-en-us.png

        Run LST SCTPPARA to check whether SCTP protocol parameters exist.Skip this step if these parameters have already been configured.

        In the MML Command - omo window, run the following command:

        ADD SCTPPARA:SCTPPARAINDEX=SCTP protocol parameter index;

      4. Set S6a parameters with NETYPE of MME on the local end.Configure this parameter when eCNS280B users need to roam to eCNS280A.
        1. Configure local Diameter information.
          note_3.0-en-us.png

          Run LST DMLE to check whether the local Diameter entity exists. If yes, use the existing local Diameter entity information and skip this step.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMLE: LOINDEX=Local entity index, LOHSTNAME=Local entity host name, LORLMNAME=Local entity realm name, NETYPE=MME, LOINFONAME=Local entity name;

        2. Configure the peer Diameter information.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMPE: PEERIDX=Peer entity index, PEERHTNAM=Peer host name, PEERNAM=Peer entity name;

        3. Configure the Diameter link set.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMLKS: LINKSIDX=Link set index, LOCALIDX=Local entity index, PEERIDX=Peer entity index, LSSELMODE=Route selection mode, LINKSNAM=Link set name;

        4. Configure the Diameter link.

          In the MML Command - omo window of the vUSN, run the following command:

          note_3.0-en-us.png
          • One end of the link must function as the server and the other end as the client.
          • Port numbers of two same Diameter links must be different.

          ADD DMLNK: LINKIDX=Link index, IPTYPE=IP address type, PROTOTYPE=Protocol type, LOCALIPV4_1=Local IPv4 address 1, LOCALPORT=Local port number, PEERIPV4_1=Peer IPv4 address 1, PEERPORT=Peer port number, CLIORSER=DIAM_CONN_SERVER, LINKSIDX=Diameter link set index, SCTPINDX=SCTPPARAINDEX in ADD SCTPPARA, LINKNAM=Link name;

        5. Configure a Diameter host route and add the host route to the route group.
          1. Configure a Diameter host route.

            In the MML Command - omo window of the vUSN, run the following command:

            ADD DMHOSTRT: ROUTEIDX=Route index, APPNAM=Application name, RSELMODE=Route selection mode, PEERSEL=PEER_INDEX,PEERIDX=Peer entity index;

          2. Configure a Diameter route group.

            In the MML Command - omo window of the vUSN, run the following command:

            ADD DMRTGRP: GRPIDX=Route group index, RTMODE=HOST_NAME_ROUTE, RTPRIMODE=HOST_NAME_ROUTE_PREFER, ROUTEIDX=Route index, ROUTEGRPNAM=Route group name;

      5. Set S6a parameters with NETYPE of HSS on the local end.Configure this parameter when eCNS280A users need to roam to eCNS280B.
        1. Configure local Diameter information.
          note_3.0-en-us.png

          Run LST DMLE to check whether the local Diameter entity exists. If yes, use the existing local Diameter entity information and skip this step.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMLE: LOINDEX=Local entity index, LOHSTNAME=Local entity host name, LORLMNAME=Local entity realm name, NETYPE=HSS, LOINFONAME=Local entity name;

        2. Configure the peer Diameter information.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMPE: PEERIDX=Peer entity index, PEERHTNAM=Peer host name, PEERNAM=Peer entity name;

        3. Configure the Diameter link set.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMLKS: LINKSIDX=Link set index, LOCALIDX=Local entity index, PEERIDX=Peer entity index, LSSELMODE=Route selection mode, LINKSNAM=Link set name;

        4. Configure the Diameter link.

          In the MML Command - omo window of the vUSN, run the following command:

          note_3.0-en-us.png
          • One end of the link must function as the server and the other end as the client.
          • Port numbers of two same Diameter links must be different.

          ADD DMLNK: LINKIDX=Link index, IPTYPE=IP address type, LOCALIPV4_1=Local IPv4 address 1, LOCALPORT=Local port number, PEERIPV4_1=Peer IPv4 address 1, PEERPORT=Peer port number, CLIORSER=DIAM_CONN_CLIENT, LINKSIDX=Diameter link set index, SCTPINDX=SCTPPARAINDEX in ADD SCTPPARA, LINKNAM=Link name;

        5. Configure a Diameter host route and add the host route to the route group.
          1. Configure a Diameter host route.

            In the MML Command - omo window of the vUSN, run the following command:

            ADD DMHOSTRT: ROUTEIDX=Route index, APPNAM=Application name, RSELMODE=Route selection mode, PEERSEL=PEER_INDEX,PEERIDX=Peer entity index;

          2. Configure a Diameter route group.

            In the MML Command - omo window of the vUSN, run the following command:

            ADD DMRTGRP: GRPIDX=Route group index, RTMODE=HOST_NAME_ROUTE, RTPRIMODE=HOST_NAME_ROUTE_PREFER, ROUTEIDX=Route index, ROUTEGRPNAM=Route group name;

    5. Configure the mapping between the IMSI and HSS.

      The user can find the HSS to which the IMSI belongs based on the mapping.

      note_3.0-en-us.png
      • It is recommended that the IMSI number segment configured in this step do not overlap with that in the LocalSub feature (The IMSI number segment can be queried by running LST HIMSISEG).
      • If they are overlapped, the system selects the HSS based on the priority configured in the IMSI segment of the LocalSub feature. Modify the priority based on the site requirements.
      • Ensure that the user registration information is available in the preferred HSS (external HSS or embedded HSS).
      • The number segments of roaming users cannot be included in those of local users.
      • The parameter IMSIPRE matches the IMSI of users to distinguish different user groups. You need to determine the HSS onto which an IMSI prefix is mapped based on the maximum matching principle.

      In the MML Command - omo window of the vUSN, run the following command:

      ADD IMSIHSS:IMSIPRE=IMSI number segment of eCNS280B users, HSSRLM=HSS domain name, GRPIDX=GRPIDX configured in ADD DMRTGRP;

    6. Optional: Configuring an interworking PLMN.

      If the core network B and core network A are in different PLMNs, an interworking PLMN must be configured in the core network A.

      Roaming users can access the eCN only when their VPLMNs are in the interworking PLMN table.

      In the MML Command - omo window of the vUSN, run the following command:

      ADD CONNECTPLMN: MCC=Mobile country code, MNC=Mobile network code, MATCHIMSI=Matched IMSI, CC=Country code, COUNTRYORAREANAME=Operator name;

      Configure these parameters as follows:

      • MCC: Set this parameter to the mobile country code of the core network B PLMN.
      • MNC: Set this parameter to the mobile network code of the core network B PLMN.
      • MATCHIMSI: Set this parameter to the part except the MCC and MNC in the IMSI field.
      note_3.0-en-us.png

      After the PLMNs are matched based on the MCC and the MNC, this parameter is used to match a record based on the forward maximum rule.

      • CC: Set this parameter to the country code (CC) of the core network B PLMN.
      • COUNTRYORAREANAME: Set this parameter to name of the core network B PLMN operator.

  2. Configure core network B (eCNS280B).

    1. Add an APN.

      In the MML Command - ugw window of the vUGW, run the following command to add an APN:

      ADD APN:APN=APN of eCNS280A;

      SET APNDNS: APN=APN of eCNS280A, MDNSSERVERV4=Primary DNS server IPv4 address, BDNSSERVERV4=Secondary DNS server IPv4 address;

      SET APNREPORTATTR: APN=APN of eCNS280A;

    2. Add IP address pool configurations.

      In the MML Command - ugw window of the vUGW, run the following command to add IP address pool configurations:

      ADD POOL: POOLNAME=IP address pool of eCNS280B;

      ADD POOLBINDAPN: APN=APN of eCNS280A, POOLNAME=IP address pool name of eCNS280B;

      ADD SECTION: POOLNAME=IP address pool name of eCNS280B, SECTIONNUM=IP address segment number, IPVERSION=IP address type, V4STARTIP=Starting IPv4 address of eCNS280B's address segment, and V4ENDIP=Ending IPv4 address of eCNS280B's address segment;

    3. In the MML Command - omo window of the vUSN, run the following command to configure DNS data for the APN of the roaming user:
      • HSINDEX in ADD IPV4DNSH corresponds to HSINDEX in ADD DNSN.
      • If the core network B and core network A are in different PLMNs, set the INTYPE to S8 in ADD DNSN.
      • If the core network B and core network A are in the same PLMN, set the INTYPE to S5 in ADD DNSN.

      ADD IPV4DNSH:HSINDEX=Host name index, HOSTNAME=Host name, ADDRSECTION=IP address segment, IPV4ADDR1=IP address of the S5/S8 interface of the PGW on eCNS280B

      ADD DNSN:FQDN=FQDN,HSINDEX=Host name index, ENTITY=NE type, INTYPE=Interface type, S5PROTOCOL=S5 interface protocol type;

    4. Configure S6a interface data.
      1. Configure S6a interface basic data.

        In the MML Command - vnrs window of the vUSN, run the following command:

        SET BFD: BFDENABLE=TRUE;

        SET AUTOCONFIG:SWITCHFLAG=FALSE;

        ADD AUTOSCALINGSERVICE:SERVICENAME=Service name,AFTYPE=IPv4,IPALLOCTYPE4=USER_CONFIG,VNICID=VNIC ID,VLANID=VLAN ID,BEGINADDR4=Begin address,ENDADDR4=End address;

        ADD AUTOSCALINGSRBFD: SERVICENAME=Service name;

        ADD AUTOSCALINGSRROUTE: SERVICENAME=Service name, IPVERSION=IPv4, PREFIX4=Route prefix IPv4, MASKLENGTH=32, NEXTHOPALLOCTYPE4=CONFIG, NEXTHOP4=Route next hop IPv4, BFDENABLE=TRUE;

        SET AUTOCONFIG:SWITCHFLAG=TRUE;

      2. Configure parameters related to the service IP address.

        In the MML Command - omo window of the vUSN, run the following command:

        ADD SERVICEIP:IPVERSION=IPv4, SERVICEIPV4=Service IPv4 address of eCNS280B;

      3. Configure SCTP link parameters.
        note_3.0-en-us.png

        Run LST SCTPPARA to check whether SCTP protocol parameters exist.Skip this step if these parameters have already been configured.

        In the MML Command - omo window, run the following command:

        ADD SCTPPARA:SCTPPARAINDEX=SCTP protocol parameter index;

      4. Set S6a parameters with NETYPE of HSS on the local end.Configure this parameter when eCNS280B users need to roam to eCNS280A.
        1. Configure local Diameter information.
          note_3.0-en-us.png

          Run LST DMLE to check whether the local Diameter entity exists. If yes, use the existing local Diameter entity information and skip this step.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMLE: LOINDEX=Local entity index, LOHSTNAME=Local entity host name, LORLMNAME=Local entity realm name, NETYPE=HSS, LOINFONAME=Local entity name;

        2. Configure the peer Diameter information.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMPE: PEERIDX=Peer entity index, PEERHTNAM=Peer host name, PEERNAM=Peer entity name;

        3. Configure the Diameter link set.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMLKS: LINKSIDX=Link set index, LOCALIDX=Local entity index, PEERIDX=Peer entity index, LSSELMODE=Route selection mode, LINKSNAM=Link set name;

        4. Configure the Diameter link.

          In the MML Command - omo window of the vUSN, run the following command:

          note_3.0-en-us.png
          • One end of the link must function as the server and the other end as the client.
          • Port numbers of two same Diameter links must be different.

          ADD DMLNK: LINKIDX=Link index, IPTYPE=IP address type, PROTOTYPE=Protocol type, LOCALIPV4_1=Local IPv4 address 1, LOCALPORT=Local port number, PEERIPV4_1=Peer IPv4 address 1, PEERPORT=Peer port number, CLIORSER=DIAM_CONN_CLIENT, LINKSIDX=Diameter link set index, SCTPINDX=SCTPPARAINDEX in ADD SCTPPARA, LINKNAM=Link name;

        5. Configure a Diameter host route and add the host route to the route group.
          1. Configure a Diameter host route.

            In the MML Command - omo window of the vUSN, run the following command:

            ADD DMHOSTRT: ROUTEIDX=Route index, APPNAM=Application name, RSELMODE=Route selection mode, PEERSEL=PEER_INDEX,PEERIDX=Peer entity index;

          2. Configure a Diameter route group.

            In the MML Command - omo window of the vUSN, run the following command:

            ADD DMRTGRP: GRPIDX=Route group index, RTMODE=HOST_NAME_ROUTE, RTPRIMODE=HOST_NAME_ROUTE_PREFER, ROUTEIDX=Route index, ROUTEGRPNAM=Route group name;

      5. Set S6a parameters with NETYPE of MME on the local end.Configure this parameter when eCNS280A users need to roam to eCNS280B.
        1. Configure local Diameter information.
          note_3.0-en-us.png

          Run LST DMLE to check whether the local Diameter entity exists. If yes, use the existing local Diameter entity information and skip this step.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMLE: LOINDEX=Local entity index, LOHSTNAME=Local entity host name, LORLMNAME=Local entity realm name, NETYPE=MME, LOINFONAME=Local entity name;

        2. Configure the peer Diameter information.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMPE: PEERIDX=Peer entity index, PEERHTNAM=Peer host name, PEERNAM=Peer entity name;

        3. Configure the Diameter link set.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMLKS: LINKSIDX=Link set index, LOCALIDX=Local entity index, PEERIDX=Peer entity index, LSSELMODE=Route selection mode, LINKSNAM=Link set name;

        4. Configure the Diameter link.

          In the MML Command - omo window of the vUSN, run the following command:

          note_3.0-en-us.png
          • One end of the link must function as the server and the other end as the client.
          • Port numbers of two same Diameter links must be different.

          ADD DMLNK: LINKIDX=Link index, IPTYPE=IP address type, LOCALIPV4_1=Local IPv4 address 1, LOCALPORT=Local port number, PEERIPV4_1=Peer IPv4 address 1, PEERPORT=Peer port number, CLIORSER=DIAM_CONN_SERVER, LINKSIDX=Diameter link set index, SCTPINDX=SCTPPARAINDEX in ADD SCTPPARA, LINKNAM=Link name;

        5. Configure a Diameter host route and add the host route to the route group.
          1. Configure a Diameter host route.

            In the MML Command - omo window of the vUSN, run the following command:

            ADD DMHOSTRT: ROUTEIDX=Route index, APPNAM=Application name, RSELMODE=Route selection mode, PEERSEL=PEER_INDEX,PEERIDX=Peer entity index;

          2. Configure a Diameter route group.

            In the MML Command - omo window of the vUSN, run the following command:

            ADD DMRTGRP: GRPIDX=Route group index, RTMODE=HOST_NAME_ROUTE, RTPRIMODE=HOST_NAME_ROUTE_PREFER, ROUTEIDX=Route index, ROUTEGRPNAM=Route group name;

    5. Configure the mapping between the IMSI and HSS.

      The user can find the HSS to which the IMSI belongs based on the mapping.

      note_3.0-en-us.png
      • It is recommended that the IMSI number segment configured in this step do not overlap with that in the LocalSub feature (The IMSI number segment can be queried by running LST HIMSISEG).
      • If they are overlapped, the system selects the HSS based on the priority configured in the IMSI segment of the LocalSub feature. Modify the priority based on the site requirements.
      • Ensure that the user registration information is available in the preferred HSS (external HSS or embedded HSS).
      • The number segments of roaming users cannot be included in those of local users.
      • The parameter IMSIPRE matches the IMSI of users to distinguish different user groups. You need to determine the HSS onto which an IMSI prefix is mapped based on the maximum matching principle.

      In the MML Command - omo window of the vUSN, run the following command:

      ADD IMSIHSS:IMSIPRE=IMSI number segment of eCNS280A users, HSSRLM=HSS domain name, GRPIDX=GRPIDX configured in ADD DMRTGRP;

    6. Optional: Configuring an interworking PLMN.

      If the core network A and core network B are in different PLMNs, an interworking PLMN must be configured in the core network B.

      Roaming users can access the eCN only when their VPLMNs are in the interworking PLMN table.

      In the MML Command - omo window of the vUSN, run the following command:

      ADD CONNECTPLMN: MCC=Mobile country code, MNC=Mobile network code, MATCHIMSI=Matched IMSI, CC=Country code, COUNTRYORAREANAME=Operator name;

      Configure these parameters as follows:

      • MCC: Set this parameter to the mobile country code of the core network A PLMN.
      • MNC: Set this parameter to the mobile network code of the core network A PLMN.
      • MATCHIMSI: Set this parameter to the part except the MCC and MNC in the IMSI field.
      note_3.0-en-us.png

      After the PLMNs are matched based on the MCC and the MNC, this parameter is used to match a record based on the forward maximum rule.

      • CC: Set this parameter to the country code (CC) of the core network A PLMN.
      • COUNTRYORAREANAME: Set this parameter to name of the core network A PLMN operator.
More details : 
https://support.huawei.com/hedex/hdx.do?lib=EDOC1100072187WEH0912B&docid=EDOC1100072187&lang ... &ui=3&keyword=eCNS280%2Broaming%2B%2B%2Bplmn
I hope my answer can help you!
Thanks
View more
  • x
  • convention:

All Answers
Hello,
Below the initial configuration of Inter-eCNS280 Roaming in new deployment scenarios.

eCNS280 roaming with another eCNS280 each uder different PLMN

  1. Configure core network A (eCNS280A).

    1. Add an APN.

      In the MML Command - ugw window of the vUGW, run the following command to add an APN:

      ADD APN:APN=APN of eCNS280B;

      SET APNDNS: APN=APN of eCNS280B, MDNSSERVERV4=Primary DNS server IPv4 address, BDNSSERVERV4=Secondary DNS server IPv4 address;

      SET APNREPORTATTR: APN=APN of eCNS280B;

    2. Add IP address pool configurations.

      In the MML Command - ugw window of the vUGW, run the following command to add IP address pool configurations:

      ADD POOL: POOLNAME=IP address pool of eCNS280A;

      ADD POOLBINDAPN: APN=APN of eCNS280B, POOLNAME=IP address pool name of eCNS280A;

      ADD SECTION: POOLNAME=IP address pool name of eCNS280A, SECTIONNUM=IP address segment number, IPVERSION=IP address type, V4STARTIP=Starting IPv4 address of eCNS280A's address segment, and V4ENDIP=Ending IPv4 address of eCNS280A's address segment;

    3. In the MML Command - omo window of the vUSN, run the following command to configure DNS data for the APN of the roaming user:

      ADD IPV4DNSH:HSINDEX=Host name index, HOSTNAME=Host name, ADDRSECTION=IP address segment, IPV4ADDR1=IP address of the S5/S8 interface of the PGW on eCNS280A

      note_3.0-en-us.png

      HSINDEX in ADD IPV4DNSH corresponds to HSINDEX in ADD DNSN.

      ADD DNSN:FQDN=FQDN,HSINDEX=Host name index, ENTITY=NE type, INTYPE=Interface type, S5PROTOCOL=S5 interface protocol type;
      • Set ENTITY to PGW.
      • If the core network B and core network A are in different PLMNs, set the INTYPE to S8 in ADD DNSN.
      • If the core network B and core network A are in the same PLMN, set the INTYPE to S5 in ADD DNSN.
      • FQDN specifies an NE's fully qualified domain name, which is composed of RAI, TAI, APN, and MME ID. The FQDN is used to query NEs such as the SGSN, MME, S-GW, P-GW, or IWS. An FQDN is composed of the following IEs: P-GW(APN): <APNNI>.APN.EPC.MNC<MNC>.MCC<MCC>.3GPPNETWORK.ORG

        Example: COMPANY1.COM.APN.EPC.MNC001.MCC308.3GPPNETWORK.ORG

        note_3.0-en-us.png
        • This parameter can contain only letters, digits, periods (.), and hyphens (-).
        • <MNC> and <MCC> are both a 3-digit decimal number and <CELL ID> is a 4-digit decimal number.
        • The number in each <> field except that in <APNNI> must meet the specified number of digits. If there are less digits in each field, 0s must be added in the front until the required number of digits is met.
        • The FQDN cannot start or end with a period (.).
    4. Configure S6a interface data.
      1. Configure S6a interface basic data.

        In the MML Command - vnrs window of the vUSN, run the following command:

        SET BFD: BFDENABLE=TRUE;

        SET AUTOCONFIG:SWITCHFLAG=FALSE;

        ADD AUTOSCALINGSERVICE:SERVICENAME=Service name,AFTYPE=IPv4,IPALLOCTYPE4=USER_CONFIG,VNICID=VNIC ID,VLANID=VLAN ID,BEGINADDR4=Begin address,ENDADDR4=End address;

        ADD AUTOSCALINGSRBFD: SERVICENAME=Service name;

        ADD AUTOSCALINGSRROUTE: SERVICENAME=Service name, IPVERSION=IPv4, PREFIX4=Route prefix IPv4, MASKLENGTH=32, NEXTHOPALLOCTYPE4=CONFIG, NEXTHOP4=Route next hop IPv4, BFDENABLE=TRUE;

        SET AUTOCONFIG:SWITCHFLAG=TRUE;

      2. Configure parameters related to the service IP address.

        In the MML Command - omo window of the vUSN, run the following command:

        ADD SERVICEIP:IPVERSION=IPv4, SERVICEIPV4=Service IPv4 address of eCNS280A;

      3. Configure SCTP link parameters.
        note_3.0-en-us.png

        Run LST SCTPPARA to check whether SCTP protocol parameters exist.Skip this step if these parameters have already been configured.

        In the MML Command - omo window, run the following command:

        ADD SCTPPARA:SCTPPARAINDEX=SCTP protocol parameter index;

      4. Set S6a parameters with NETYPE of MME on the local end.Configure this parameter when eCNS280B users need to roam to eCNS280A.
        1. Configure local Diameter information.
          note_3.0-en-us.png

          Run LST DMLE to check whether the local Diameter entity exists. If yes, use the existing local Diameter entity information and skip this step.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMLE: LOINDEX=Local entity index, LOHSTNAME=Local entity host name, LORLMNAME=Local entity realm name, NETYPE=MME, LOINFONAME=Local entity name;

        2. Configure the peer Diameter information.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMPE: PEERIDX=Peer entity index, PEERHTNAM=Peer host name, PEERNAM=Peer entity name;

        3. Configure the Diameter link set.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMLKS: LINKSIDX=Link set index, LOCALIDX=Local entity index, PEERIDX=Peer entity index, LSSELMODE=Route selection mode, LINKSNAM=Link set name;

        4. Configure the Diameter link.

          In the MML Command - omo window of the vUSN, run the following command:

          note_3.0-en-us.png
          • One end of the link must function as the server and the other end as the client.
          • Port numbers of two same Diameter links must be different.

          ADD DMLNK: LINKIDX=Link index, IPTYPE=IP address type, PROTOTYPE=Protocol type, LOCALIPV4_1=Local IPv4 address 1, LOCALPORT=Local port number, PEERIPV4_1=Peer IPv4 address 1, PEERPORT=Peer port number, CLIORSER=DIAM_CONN_SERVER, LINKSIDX=Diameter link set index, SCTPINDX=SCTPPARAINDEX in ADD SCTPPARA, LINKNAM=Link name;

        5. Configure a Diameter host route and add the host route to the route group.
          1. Configure a Diameter host route.

            In the MML Command - omo window of the vUSN, run the following command:

            ADD DMHOSTRT: ROUTEIDX=Route index, APPNAM=Application name, RSELMODE=Route selection mode, PEERSEL=PEER_INDEX,PEERIDX=Peer entity index;

          2. Configure a Diameter route group.

            In the MML Command - omo window of the vUSN, run the following command:

            ADD DMRTGRP: GRPIDX=Route group index, RTMODE=HOST_NAME_ROUTE, RTPRIMODE=HOST_NAME_ROUTE_PREFER, ROUTEIDX=Route index, ROUTEGRPNAM=Route group name;

      5. Set S6a parameters with NETYPE of HSS on the local end.Configure this parameter when eCNS280A users need to roam to eCNS280B.
        1. Configure local Diameter information.
          note_3.0-en-us.png

          Run LST DMLE to check whether the local Diameter entity exists. If yes, use the existing local Diameter entity information and skip this step.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMLE: LOINDEX=Local entity index, LOHSTNAME=Local entity host name, LORLMNAME=Local entity realm name, NETYPE=HSS, LOINFONAME=Local entity name;

        2. Configure the peer Diameter information.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMPE: PEERIDX=Peer entity index, PEERHTNAM=Peer host name, PEERNAM=Peer entity name;

        3. Configure the Diameter link set.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMLKS: LINKSIDX=Link set index, LOCALIDX=Local entity index, PEERIDX=Peer entity index, LSSELMODE=Route selection mode, LINKSNAM=Link set name;

        4. Configure the Diameter link.

          In the MML Command - omo window of the vUSN, run the following command:

          note_3.0-en-us.png
          • One end of the link must function as the server and the other end as the client.
          • Port numbers of two same Diameter links must be different.

          ADD DMLNK: LINKIDX=Link index, IPTYPE=IP address type, LOCALIPV4_1=Local IPv4 address 1, LOCALPORT=Local port number, PEERIPV4_1=Peer IPv4 address 1, PEERPORT=Peer port number, CLIORSER=DIAM_CONN_CLIENT, LINKSIDX=Diameter link set index, SCTPINDX=SCTPPARAINDEX in ADD SCTPPARA, LINKNAM=Link name;

        5. Configure a Diameter host route and add the host route to the route group.
          1. Configure a Diameter host route.

            In the MML Command - omo window of the vUSN, run the following command:

            ADD DMHOSTRT: ROUTEIDX=Route index, APPNAM=Application name, RSELMODE=Route selection mode, PEERSEL=PEER_INDEX,PEERIDX=Peer entity index;

          2. Configure a Diameter route group.

            In the MML Command - omo window of the vUSN, run the following command:

            ADD DMRTGRP: GRPIDX=Route group index, RTMODE=HOST_NAME_ROUTE, RTPRIMODE=HOST_NAME_ROUTE_PREFER, ROUTEIDX=Route index, ROUTEGRPNAM=Route group name;

    5. Configure the mapping between the IMSI and HSS.

      The user can find the HSS to which the IMSI belongs based on the mapping.

      note_3.0-en-us.png
      • It is recommended that the IMSI number segment configured in this step do not overlap with that in the LocalSub feature (The IMSI number segment can be queried by running LST HIMSISEG).
      • If they are overlapped, the system selects the HSS based on the priority configured in the IMSI segment of the LocalSub feature. Modify the priority based on the site requirements.
      • Ensure that the user registration information is available in the preferred HSS (external HSS or embedded HSS).
      • The number segments of roaming users cannot be included in those of local users.
      • The parameter IMSIPRE matches the IMSI of users to distinguish different user groups. You need to determine the HSS onto which an IMSI prefix is mapped based on the maximum matching principle.

      In the MML Command - omo window of the vUSN, run the following command:

      ADD IMSIHSS:IMSIPRE=IMSI number segment of eCNS280B users, HSSRLM=HSS domain name, GRPIDX=GRPIDX configured in ADD DMRTGRP;

    6. Optional: Configuring an interworking PLMN.

      If the core network B and core network A are in different PLMNs, an interworking PLMN must be configured in the core network A.

      Roaming users can access the eCN only when their VPLMNs are in the interworking PLMN table.

      In the MML Command - omo window of the vUSN, run the following command:

      ADD CONNECTPLMN: MCC=Mobile country code, MNC=Mobile network code, MATCHIMSI=Matched IMSI, CC=Country code, COUNTRYORAREANAME=Operator name;

      Configure these parameters as follows:

      • MCC: Set this parameter to the mobile country code of the core network B PLMN.
      • MNC: Set this parameter to the mobile network code of the core network B PLMN.
      • MATCHIMSI: Set this parameter to the part except the MCC and MNC in the IMSI field.
      note_3.0-en-us.png

      After the PLMNs are matched based on the MCC and the MNC, this parameter is used to match a record based on the forward maximum rule.

      • CC: Set this parameter to the country code (CC) of the core network B PLMN.
      • COUNTRYORAREANAME: Set this parameter to name of the core network B PLMN operator.

  2. Configure core network B (eCNS280B).

    1. Add an APN.

      In the MML Command - ugw window of the vUGW, run the following command to add an APN:

      ADD APN:APN=APN of eCNS280A;

      SET APNDNS: APN=APN of eCNS280A, MDNSSERVERV4=Primary DNS server IPv4 address, BDNSSERVERV4=Secondary DNS server IPv4 address;

      SET APNREPORTATTR: APN=APN of eCNS280A;

    2. Add IP address pool configurations.

      In the MML Command - ugw window of the vUGW, run the following command to add IP address pool configurations:

      ADD POOL: POOLNAME=IP address pool of eCNS280B;

      ADD POOLBINDAPN: APN=APN of eCNS280A, POOLNAME=IP address pool name of eCNS280B;

      ADD SECTION: POOLNAME=IP address pool name of eCNS280B, SECTIONNUM=IP address segment number, IPVERSION=IP address type, V4STARTIP=Starting IPv4 address of eCNS280B's address segment, and V4ENDIP=Ending IPv4 address of eCNS280B's address segment;

    3. In the MML Command - omo window of the vUSN, run the following command to configure DNS data for the APN of the roaming user:
      • HSINDEX in ADD IPV4DNSH corresponds to HSINDEX in ADD DNSN.
      • If the core network B and core network A are in different PLMNs, set the INTYPE to S8 in ADD DNSN.
      • If the core network B and core network A are in the same PLMN, set the INTYPE to S5 in ADD DNSN.

      ADD IPV4DNSH:HSINDEX=Host name index, HOSTNAME=Host name, ADDRSECTION=IP address segment, IPV4ADDR1=IP address of the S5/S8 interface of the PGW on eCNS280B

      ADD DNSN:FQDN=FQDN,HSINDEX=Host name index, ENTITY=NE type, INTYPE=Interface type, S5PROTOCOL=S5 interface protocol type;

    4. Configure S6a interface data.
      1. Configure S6a interface basic data.

        In the MML Command - vnrs window of the vUSN, run the following command:

        SET BFD: BFDENABLE=TRUE;

        SET AUTOCONFIG:SWITCHFLAG=FALSE;

        ADD AUTOSCALINGSERVICE:SERVICENAME=Service name,AFTYPE=IPv4,IPALLOCTYPE4=USER_CONFIG,VNICID=VNIC ID,VLANID=VLAN ID,BEGINADDR4=Begin address,ENDADDR4=End address;

        ADD AUTOSCALINGSRBFD: SERVICENAME=Service name;

        ADD AUTOSCALINGSRROUTE: SERVICENAME=Service name, IPVERSION=IPv4, PREFIX4=Route prefix IPv4, MASKLENGTH=32, NEXTHOPALLOCTYPE4=CONFIG, NEXTHOP4=Route next hop IPv4, BFDENABLE=TRUE;

        SET AUTOCONFIG:SWITCHFLAG=TRUE;

      2. Configure parameters related to the service IP address.

        In the MML Command - omo window of the vUSN, run the following command:

        ADD SERVICEIP:IPVERSION=IPv4, SERVICEIPV4=Service IPv4 address of eCNS280B;

      3. Configure SCTP link parameters.
        note_3.0-en-us.png

        Run LST SCTPPARA to check whether SCTP protocol parameters exist.Skip this step if these parameters have already been configured.

        In the MML Command - omo window, run the following command:

        ADD SCTPPARA:SCTPPARAINDEX=SCTP protocol parameter index;

      4. Set S6a parameters with NETYPE of HSS on the local end.Configure this parameter when eCNS280B users need to roam to eCNS280A.
        1. Configure local Diameter information.
          note_3.0-en-us.png

          Run LST DMLE to check whether the local Diameter entity exists. If yes, use the existing local Diameter entity information and skip this step.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMLE: LOINDEX=Local entity index, LOHSTNAME=Local entity host name, LORLMNAME=Local entity realm name, NETYPE=HSS, LOINFONAME=Local entity name;

        2. Configure the peer Diameter information.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMPE: PEERIDX=Peer entity index, PEERHTNAM=Peer host name, PEERNAM=Peer entity name;

        3. Configure the Diameter link set.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMLKS: LINKSIDX=Link set index, LOCALIDX=Local entity index, PEERIDX=Peer entity index, LSSELMODE=Route selection mode, LINKSNAM=Link set name;

        4. Configure the Diameter link.

          In the MML Command - omo window of the vUSN, run the following command:

          note_3.0-en-us.png
          • One end of the link must function as the server and the other end as the client.
          • Port numbers of two same Diameter links must be different.

          ADD DMLNK: LINKIDX=Link index, IPTYPE=IP address type, PROTOTYPE=Protocol type, LOCALIPV4_1=Local IPv4 address 1, LOCALPORT=Local port number, PEERIPV4_1=Peer IPv4 address 1, PEERPORT=Peer port number, CLIORSER=DIAM_CONN_CLIENT, LINKSIDX=Diameter link set index, SCTPINDX=SCTPPARAINDEX in ADD SCTPPARA, LINKNAM=Link name;

        5. Configure a Diameter host route and add the host route to the route group.
          1. Configure a Diameter host route.

            In the MML Command - omo window of the vUSN, run the following command:

            ADD DMHOSTRT: ROUTEIDX=Route index, APPNAM=Application name, RSELMODE=Route selection mode, PEERSEL=PEER_INDEX,PEERIDX=Peer entity index;

          2. Configure a Diameter route group.

            In the MML Command - omo window of the vUSN, run the following command:

            ADD DMRTGRP: GRPIDX=Route group index, RTMODE=HOST_NAME_ROUTE, RTPRIMODE=HOST_NAME_ROUTE_PREFER, ROUTEIDX=Route index, ROUTEGRPNAM=Route group name;

      5. Set S6a parameters with NETYPE of MME on the local end.Configure this parameter when eCNS280A users need to roam to eCNS280B.
        1. Configure local Diameter information.
          note_3.0-en-us.png

          Run LST DMLE to check whether the local Diameter entity exists. If yes, use the existing local Diameter entity information and skip this step.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMLE: LOINDEX=Local entity index, LOHSTNAME=Local entity host name, LORLMNAME=Local entity realm name, NETYPE=MME, LOINFONAME=Local entity name;

        2. Configure the peer Diameter information.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMPE: PEERIDX=Peer entity index, PEERHTNAM=Peer host name, PEERNAM=Peer entity name;

        3. Configure the Diameter link set.

          In the MML Command - omo window of the vUSN, run the following command:

          ADD DMLKS: LINKSIDX=Link set index, LOCALIDX=Local entity index, PEERIDX=Peer entity index, LSSELMODE=Route selection mode, LINKSNAM=Link set name;

        4. Configure the Diameter link.

          In the MML Command - omo window of the vUSN, run the following command:

          note_3.0-en-us.png
          • One end of the link must function as the server and the other end as the client.
          • Port numbers of two same Diameter links must be different.

          ADD DMLNK: LINKIDX=Link index, IPTYPE=IP address type, LOCALIPV4_1=Local IPv4 address 1, LOCALPORT=Local port number, PEERIPV4_1=Peer IPv4 address 1, PEERPORT=Peer port number, CLIORSER=DIAM_CONN_SERVER, LINKSIDX=Diameter link set index, SCTPINDX=SCTPPARAINDEX in ADD SCTPPARA, LINKNAM=Link name;

        5. Configure a Diameter host route and add the host route to the route group.
          1. Configure a Diameter host route.

            In the MML Command - omo window of the vUSN, run the following command:

            ADD DMHOSTRT: ROUTEIDX=Route index, APPNAM=Application name, RSELMODE=Route selection mode, PEERSEL=PEER_INDEX,PEERIDX=Peer entity index;

          2. Configure a Diameter route group.

            In the MML Command - omo window of the vUSN, run the following command:

            ADD DMRTGRP: GRPIDX=Route group index, RTMODE=HOST_NAME_ROUTE, RTPRIMODE=HOST_NAME_ROUTE_PREFER, ROUTEIDX=Route index, ROUTEGRPNAM=Route group name;

    5. Configure the mapping between the IMSI and HSS.

      The user can find the HSS to which the IMSI belongs based on the mapping.

      note_3.0-en-us.png
      • It is recommended that the IMSI number segment configured in this step do not overlap with that in the LocalSub feature (The IMSI number segment can be queried by running LST HIMSISEG).
      • If they are overlapped, the system selects the HSS based on the priority configured in the IMSI segment of the LocalSub feature. Modify the priority based on the site requirements.
      • Ensure that the user registration information is available in the preferred HSS (external HSS or embedded HSS).
      • The number segments of roaming users cannot be included in those of local users.
      • The parameter IMSIPRE matches the IMSI of users to distinguish different user groups. You need to determine the HSS onto which an IMSI prefix is mapped based on the maximum matching principle.

      In the MML Command - omo window of the vUSN, run the following command:

      ADD IMSIHSS:IMSIPRE=IMSI number segment of eCNS280A users, HSSRLM=HSS domain name, GRPIDX=GRPIDX configured in ADD DMRTGRP;

    6. Optional: Configuring an interworking PLMN.

      If the core network A and core network B are in different PLMNs, an interworking PLMN must be configured in the core network B.

      Roaming users can access the eCN only when their VPLMNs are in the interworking PLMN table.

      In the MML Command - omo window of the vUSN, run the following command:

      ADD CONNECTPLMN: MCC=Mobile country code, MNC=Mobile network code, MATCHIMSI=Matched IMSI, CC=Country code, COUNTRYORAREANAME=Operator name;

      Configure these parameters as follows:

      • MCC: Set this parameter to the mobile country code of the core network A PLMN.
      • MNC: Set this parameter to the mobile network code of the core network A PLMN.
      • MATCHIMSI: Set this parameter to the part except the MCC and MNC in the IMSI field.
      note_3.0-en-us.png

      After the PLMNs are matched based on the MCC and the MNC, this parameter is used to match a record based on the forward maximum rule.

      • CC: Set this parameter to the country code (CC) of the core network A PLMN.
      • COUNTRYORAREANAME: Set this parameter to name of the core network A PLMN operator.
More details : 
https://support.huawei.com/hedex/hdx.do?lib=EDOC1100072187WEH0912B&docid=EDOC1100072187&lang ... &ui=3&keyword=eCNS280%2Broaming%2B%2B%2Bplmn
I hope my answer can help you!
Thanks
View more
  • x
  • convention:

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.