Owb091500 (Slide) Usn9810 v900r015c10 (Mme) Data Configuration Issue1.01

USN9810 MME Data Configuration
Confidential Information of Huawei. No Spreading Without Permission









 Important Parameters:
 System Function: This parameter specifies the NE type that the USN9810 functions as.
 SGSN(SGSN): indicates that the USN9810 functions as an SGSN.
 MME(MME): indicates that the USN9810 functions as an MME.
 MME+SGSN(MME+SGSN): indicates that the USN9810 functions as a combined
MME/SGSN
 Protocol version: This parameter specifies the protocol version used by the USN9810.
 Some procedure will different according to the requirement of R99 or R4. For example
in R99 the RAB message will happen before the create PDP context response
message.
 The extension headers included in the Supported Extension Headers Notification
message vary with the protocol version of the USN9810. If the protocol version is R99,
the USN9810 can include only the PDCP PDU Number extension header in the
message. If the protocol version is R4, the USN9810 can include the PDCP PDU
Number, Suspend Request, and Suspend Response extension headers in the
message.
 CNID: specifies the identifier of the core network. This parameter together with Mobile Country
Code and Mobile Network Code composes a global CN ID, which is sent to the radio access
network (RAN) during procedures such as the paging procedure. When the Iu-flex function is
used, the value of this parameter must be unique in an SGSN pool. Iu-flex is a function that
enables a RAN node in a circuited-switched (CS) or packet-switched (PS) domain to connect to
multiple CN nodes. The Core network identifier parameter must be planned with both the CS
and PS domains considered to prevent core network identifier conflicts.
 Capability: This parameter specifies the relative weight of the MME capacity in an MME pool.


 ADD MMEID command is used to add an MME ID record identifying a unique MME in a public land
mobile network (PLMN).
 Application scenario
 When the MME allocates a GUTI to a UE, it generates the GUTI according to the value
of MME Code(Begin) in this command. When a UE attaches to the network, the MME
compares the mobile country code (MCC), mobile network code (MNC), mobility
management entity group identifier (MMEGI), and mobility management entity code
(MMEC) carried in the GUTI with those in the MME ID. If the information in the GUTI is
different from that in the MME ID, the MME considers the attach procedure as an inter-
USN9810 attach procedure.
 This command is used to set the device capability value of the MME in the Pool in case of
establishing the MME Pool.
 When the MME ID is distributed on the network, the following configuration rules must be followed:
 The MME group identity is unique under the same PLMN. Multiple PLMNs may use the same
MME group identity.
 The same MME cannot exist in multiple MME groups.
 MCC
 MNC
 MMEGI: a code in hexadecimal format and four bits fixed.
 MMEC: a code in hexadecimal format and two bits fixed. Enter 0 at the most significant
bit in case of less than two bits.


 Time zone: This parameter specifies the time zone of the area where the
equipment resides.
 Daylight saving time flag: This parameter specifies whether to enable the
DST
 Start date mode: This parameter specifies the format of the start time of the
DST. The parameter is valid only when Daylight saving time flag is set to
YES(Yes).
 End date mode: This parameter specifies the format of the end time of the
YES(Yes).

 Time zone: This parameter specifies the time zone of the area where the
equipment resides.
 Daylight saving time flag: This parameter specifies whether to enable the
DST
 Start date mode: This parameter specifies the format of the start time of the
YES(Yes).
 End date mode: This parameter specifies the format of the end time of the
YES(Yes).


 These MML commands must run in the MML Command - USN window.

 These MML commands must run in the MML Command - USN window.

 These MML commands must run in the MML Command - CGP window.






 An MME can use S1-MME interfaces to provide the following functions for UEs:
 Session management
 Mobility management
 Security management
 S1-MME interfaces provide the functions of wireless management and paging.

 SCTP: is a reliable datagram transmission protocol based on a protocol (such as the

IP protocol) that supports unreliable transmission services. SCTP is a connection-
oriented protocol that provides acknowledged, accurate, and non-repeated datagram
transmission.
 S1-Application Protocol (AP): is an application-layer protocol configured on S1-
MME interfaces. It is used to transmit signaling control messages between an MME
and an eNodeB.

 S1 interface management: establishes and resets a connection between S1

interfaces, and updates configurations between an eNodeB and an MME.
 NAS signaling transmission: transparently transmits NAS signaling (such as attach
and authentication information) between a UE and an MME.
 UE context management: manages the processes of modifying UE contexts and
releasing UEs.
 Paging: enables an EPC to page a UE.
 E-RAB management: creates, modifies, and releases E-RAB information. These
processes are triggered by an MME. The E-RAB release process can also be
triggered by an eNodeB.
 Handover signaling processing: provides the mobility management function on UEs
in the LTE_ACTIVE state, for example, the TAU process and the handover between
3G and 4G systems.
 UE capability indication: informs an MME of UE capabilities.
 RIM: uses an MME to send Radio Access Network (RAN) requests and transmit RAN
system information between two RANs.

 SCTP multi-homing: indicates that an SCTP endpoint can provide multiple IP

addresses and SCTP port numbers.
 SCTP multi-homing + dual master interfaces: indicates that an MME and eNodeB
both provide multiple IP addresses and SCTP port numbers to establish SCTP
connections and two ports are configured on the MME as two master interfaces for
load sharing.
 SCTP non-multi-homing + master/slave interfaces + ARP probe: indicates that an
MME and eNodeB each provide one IP address and one SCTP port number to
establish an SCTP connection, two ports are configured on the MME to work in
master/slave mode, and ARP probe is used to ensure a master/slave switchover is
performed immediately after the master interface is faulty.

 The networking has the following characteristics:

 Two physical links are configured to work in dual master mode to implement
load sharing, ensuring link reliability.
 S1-AP signaling links are multi-homed to the eNodeB based on SCTP to
transmit signaling packets, enhancing the reliability of signaling links.

 The eNodeB does not support multi-homing. Therefore, the networking of non-multi-
homing + master/slave interfaces + ARP probe is recommended for MMEs.
 The networking has the following characteristic:
 Two physical links are configured to work in master/slave mode to ensure link
reliability.

 ECUs are used to parse signaling packets, including those of SCTP and S1-AP
protocol stacks on S1-MME interfaces.
 EPUs or PFIs are used to forward packets, including those of IP, L2, and L1 protocol
stacks.







 The MML Command – CGP window is used to run hardware-related man-machine

language (MML) commands.

 This command is used to modify the attributes of ports (including Electric ethernet,
Fiber ethernet, 10 gigabit fiber ethernet, and ATM) of a back board only.
 By default, the work mode and OAM state of the EETH ports of the USI, ETI, and SSI
boards are preset to Auto and Inactive when the system is initialized.
 By default, the work mode of the FETH ports of the USI boards are preset to Full-
duplex, 1000M/s when the system is initialized.
 By default, the work mode of the XFETH ports of the USI boards are preset to Full-
duplex, 10000M/s when the system is initialized.
 The port working modes at the local and peer ends must be the same.
 SRN, SN: indicates the subrack number and slot number.
 PORTTYPE: indicates the port type.
 PORTNAME: indicates the port name.
 PEERSN: indicates the slot number of a slave port
 PEERNAME: indicates the name of a slave port.
 MTU: indicates the maximum transmission unit. The value ranges from 1280 to
1600. The default value is 1500.
 WORKMODE: indicates the port working mode. Note that the initial value is
AUTO (auto-negotiation) for electrical ports and is FTH (1000 Mbit/s, full
duplex) for optical ports.

 The MML Command - USN 9810 window is used to run service-related MML
commands.

 The ADD BRDIP command is used to add IP addresses to the IP address pool of an
EPU/ESU/ESUB.
 A maximum of 48 IPv4 addresses and 48 IPv6 addresses can be configured for a pair
of active and standby EPUs/EPUBs/ESUs/ESUBs using this command.
 SRN: indicates the subrack number
 SN: indicates the slot number
 IPT: indicates the IP address type.
 IPV4: indicates an IPv4 address.
 IPV6: indicates an IPv6 address.
 IPV4: specifies IPV4 address of the board
 DESC: indicates the description option.

 The IP addresses of different PFU’s interfaces cannot be on the same network

segment even if these interfaces belong to the same PFI.
 If multiple EPUs on a USN9810 are activated, data packets may pass EPUs before
being sending out. Therefore, EPUs must be able to:
 1. provide high throughput;
 2. consume the bandwidth of the board bus.

 USN9810s support public network segments and allow interfaces on different PFIs to
use IP addresses in the same network segment.
 The working procedure of setting a public network segment is as follows:
 1. Define an IP network segment (such as 10.1.1.0/24) as a public network
segment.
 2. Configure interfaces on different PFIs to use IP addresses of the public
network segment. For example, you can set the IP address of port 0 on the
EPU/PFI in slot 10 to 10.1.1.1, and the IP address of port 0 on the EPU/PFI in
slot 11 to 10.1.1.2. Then the EPUs/PFIs in slots 10 and 11 can use their own
PFI interfaces to separately communicate with remote devices
 Notes: IP addresses in the same network segment are not configured for different
interfaces of one PFI. This is because such configuration cannot prevent IP packets
from being forwarded between EPUs.


 The ADD IFIP command is used to set IP addresses for PFI’s main interfaces and
sub-interfaces.
 A maximum of 48 IP addresses can be configured for a main interface, including a
primary IP address and 47 secondary IP addresses. The primary IP address must be
configured before any slave one is configured.
 A maximum of four IP addresses can configured for a sub-interface, including a
primary IP address and three secondary IP addresses.
 SRN, SN: indicates a subrack number and slot number.
 PN: indicates a port number. Notes: The port numbers of an EPU start from 0
and increase from top to bottom. The value ranges from 0 to 7.
 IFTP: indicates an interface type. The value can be Physical(Physical)
,Trunk(Trunk), GlobalTrunk(GlobalTrunk)
 SIF: indicates a sub-interface number, which ranges from 1 to 16. If this
parameter is not specified, running this command will set an IP address for the
main interface. Before using this parameter, you must run the ADD SUBIF
command to add sub-interfaces.
 IPT: indicates an IP address type, which can be PRI (primary IP address) or
SECONDARY (secondary IP address).
 IP: indicates an IPv4 address.
 MSK: indicates a mask.

 The ADD IPRT command is used to configure a static route to a destination IP

address.
 The destination IP address and the local port IP address must be in different network
segments. A gateway IP address and a service or port IP address must belong to
different network segments. If the connection between two sites does not pass a
gateway, for example, a USN9810 is connected to the peer end directly or through a
LAN switch, routes are not used.
 The smaller the route priority value is, the higher the route priority is. If multiple routes
are destined to the same destination address through different gateways, a USN9810
preferentially selects the route with the highest priority.
 A maximum of 15 routes can be destined to the same address
 If there is more than one route of the highest priority to the same destination IP
address, the USN9810 selects up to 8 routes to share the load.
 IP: indicates a destination IP address or IP network segment.
 MSK: indicates the mask of a destination address. If the destination address is
an IP address but not an IP network segment, the mask is 255.255.255.255.
 GATE: indicates a gateway IP address. The gateway address and the IP port
address of the interconnected USN9810 must be in the same network
segment.
 PRE: indicates the route priority. IP packets are sent preferentially using a
route with high priority. If congestion or a fault occurs, IP packets are sent
using a route with low priority. Note that the smaller the route priority value is,
the higher the route priority is.
 VRFNAME: indicates the name of a virtual route forwarding (VRF) table.

 The ADD SCTPPARA command is used to define SCTP parameters, which will also
be used by Diameter links.
 This command can be used to set different SCTP parameters that can be identified
uniquely using SCTPPARAINDEX. You can specify different SCTP parameters for
diameter or S1-MME links on different interfaces.

 The ADD S1APLE command is used to add a local S1-AP link entity.
 When an S1-MME interface is configured, only local information needs to be
configured on the MME, but the IP address and port number of the MME need to be
configured on the eNodeB. After the S1AP local entity is configured, the eNodeB must
initiate a link setup process to complete the setup of the S1 link.
 Local S1-AP entities are identified using the local IP address and ports.
 LLEINDEX: indicates the number of a local S1-AP link entity.
 IPTYPE: indicates the IP address type of a local S1-AP link entity.
 LOCALIPV4_1: indicates the first IP address of an S1-AP link on the MME
side.
 LOCALIPV4_1:This parameter specifies the second local IP address of the
S1AP link on the MME side. When the communication fails using Local IPv4
address 1, the system automatically switches to Local IPv4 Address 2 for the
communication with the peer NE.
 LOCALPORT: indicates the SCTP port number of an S1-AP link on the MME
side.
 CROSSIPFLAG: indicates whether an SCTP dual-homing cross path is
available. Cross paths are not recommended because they will increase
networking complexity.
 SCTPINDEX: indicates the index of the SCTP parameter used by S1-AP links.
 LLNAME: indicates the name of a local S1-AP link entity.




 This example uses an active and a standby EPU.

 0/11 indicates the EPU in slot 11 of subrack 0.




 Add a local entity for an S1AP link:

 The value of CROSSIPFLAG must be the same as the value of
CROSSIPFLAG on the peer eNodeB. It is recommended that CROSSIPFLAG
be set to NO. The values of LOCALIPV4_1 and LOCALIPV4_2 are the
service IP addresses of S1-MME interfaces.




 NOTE: A static route to the user plane of the MME should also be configured on the
eNodeB with the next hop being the port IP address of the router connected to the
eNodeB.

 Add a local entity for an S1AP link.

 The value of CROSSIPFLAG must be the same as the value of
CROSSIPFLAG on the peer eNodeB. It is recommended that CROSSIPFLAG
be set to NO. The value of LOCALIPV4_1 is the service IP address of the S1-
MME interface.



 As shown in Figure above, the MME interworks with the eNodeBs through routers A and B
over the IP backbone network. The MME connects to routers A and B using two pairs of PFIs.
Ports 0/10/4 and 1/11/4 connect to router A, and these two ports bound as a global Eth-Trunk
interface. Ports 0/12/4 and 1/13/4 connect to router B, and these two ports bound as another
global Eth-Trunk interface. (Note that x/y/z indicates subrack number, slot number, and port
number, respectively.)
 This networking mode has the following characteristics:
 The MME interworks with all eNodeBs using system-level logical IP addresses, which
are referred to as global service IP addresses.
 Ports on different interface boards on the MME are bound to form a global Eth-Trunk
interface so that the traffic transmitted between the eNodeBs and MME can be shared
among these interface boards.
 Two global Eth-Trunk interfaces are deployed, and both work in active mode to
implement load sharing. This ensures the reliability of the S1 interface.
 Two routers connect to each other so that data can be transmitted to the MME using
another router when one router is faulty.
 With global Eth-Trunk interfaces, multiple pairs of independent EPUs share load and resources.
 With global Eth-Trunk interfaces, if the forwarding resources are insufficient on EPUs, you only
need to add the physical ports on other EPUs as member interfaces of the global Eth-Trunk
interfaces to perform capacity expansion.
 The global Eth-Trunk interfaces working in dual active mode can implement load sharing or be
configured with different priorities to ensure the link reliability.









 The MML Command – CGP window is used to run hardware-related MML

commands.

 The MOD PORT command is used to modify or adjust some port parameters, such as
MTU and Work mode.
 The port working modes at the local and peer ends must be the same.
 By default, MTU and Work mode of the EETH ports on a PFI are set to 1500
and auto-negotiation during system initialization.
 By default, MTU of the FETH ports on a PFI is set to 1500 during system
initialization.
 SRN, SN: indicates the subrack number and slot number.
 PORTTYPE: indicates the port type.
The values are as follows:
 PORTNAME: indicates the port name.
 PEERSN: indicates the slot number of a standby port.
 PEERNAME: indicates the name of a standby port.
 MTU: indicates the maximum transmission unit. The value ranges from 1280 to
1600. The default value is 1500.
 WORKMODE: indicates the port working mode. Note that the initial value is
AUTO (auto-negotiation) for electrical ports and is FTH (1000 Mbit/s, full
duplex) for optical ports.

 The MML Command - USN9810 window is used to run service-related MML

commands.

 This command is used to add a virtual routing and forwarding (VRF). VRF is a
technology used for routers in IP networks. It allows multiple instances in a routing
table to work at the same time in a router.
 Run this command when multiple interfaces on the IP bearer need to be separated at
the network layer.
 A maximum of 16 records can be added
 VRFNAME: This parameter specifies the VRF name.
 VRFID: This parameter specifies the global index of the VRF. VRF global index
uniquely identifies a VRF in the system.

 The Single IP for S1-MME feature allows the MME to be configured with a few IP
addresses (at least one) for the S1-MME interfaces between the MME and all
connected eNodeBs. This feature requires that a global service IP address be
configured as a logical IP address for the entire MME so that the eNodeBs considers
the MME as one node.
 This global service IP address can be referenced only by the S1-MME interface.
 A maximum of 48 global service IPv4 addresses can be configured for a USN9810.
 The global service IP address added by running this command must be bound to an
existing VRF, which can be queried by running LST VRF.
 The global service IP address added by running this command is visible to all
EPU/EPUB/ESU/ESUB of the USN9810.
 An IP address bound to a VRF functions as either a global service IP address or a
board IP address. It cannot function as both.
 The IPv6 configurations are currently not supported.

 This command is used to add an Eth-Trunk interface. Eth-Trunk is a bundling technology. A group of physical
Ethernet ports can be bundled together as a logical interface that is known as an Eth-Trunk interface. Route protocols
and other services are implemented on the Eth-Trunk interface. The Eth-Trunk interface helps improve link reliability,
share the load, and increase the bandwidth. At the same time, USN9810 networking is simplified, the number of IP
addresses is decreased, and the number of routes is reduced.
 A maximum of 200 records can be added for an intra-board Eth-Trunk interface. A maximum of 8 records can be
added for each pair of EPU/EPUB/ESU/ESUB/EVU or the single active EVU boards.
 A maximum of 8 records can be added for a global Eth-Trunk interface.
 Eth-Trunk interfaces cannot work in active/standby mode.
 Only the S1-MME interface can function as a global Eth-Trunk interface.
 PN: This parameter specifies the Eth-Trunk interface number.
 0-7: value range for intra-board Eth-Trunk interfaces
 100-107: value range for global Eth-Trunk interfaces
 LLINK: This parameter specifies the lower limit for the member interfaces of the Eth-Trunk interface. If the
number of member interfaces in the Up state is lower than the value of this parameter, the Eth-Trunk
interface enters the Down state. If the number of member interfaces in the Up state is larger than the value
of this parameter, the Eth-Trunk interface enters the Up state. This parameter cannot be set to a value
larger than the total number of member interfaces.
 LACP: This parameter specifies whether Link Aggregation Control Protocol (LACP) is enabled. LACP
provides a standard negotiation method for devices that exchange data. LACP enables the system to
automatically aggregate a group of links to an aggregated link based on the system configurations and to
receive and transmit data using the aggregated link. After the aggregated link is formed, LACP maintains
the status of the link in real time. If LACP detects that the link is faulty on the reception or transmission
direction, LACP adjusts the aggregated link automatically.
 LACPPERIOD: This parameter specifies the period mode that the Eth-Trunk interface receives LACP
packets in the LACP mode.
 FAST(Fast): indicates that the timeout for receiving LACP packets is 3s.
 SLOW(Slow): indicates that the timeout for receiving LACP packets is 90s.

 This command is used to bind an interface to a virtual routing and forwarding (VRF)
so that the interface is separated from the public network.
 The VRF bound to the global Eth-Trunk interface must be the same as that bound to
the global service IP address.

 This command is used to add a member interface of the Eth-Trunk interface. Eth-
Trunk is a bundling technology. A group of physical Ethernet ports can be bundled
together as a logical interface that is known as an Eth-Trunk interface. Physical ports
that are bundled together are called member interfaces.
 ETHTRKMPORTPRI: This parameter specifies the member interface priority.
The member interface priority is used to choose the active port. A smaller
value indicates a higher priority. Value range are 0-65535

 This command is used to add an IP address of an interface on an EPU/EPUB/ESU/ESUB/EVU

and a global Eth-Trunk interface, including the IP address of the active interface and
subinterface. A subinterface is a logical interface subordinate to an active interface. They share
the same physical port but are logically independent from each other.
 Interface IP addresses cannot be in the same subnet used by inter-board routes (the default
network segment is 192.168.0.0/20) within the USN9810. You can query the information about
subnets used by inter-board routes by running LST IPCBASEIP.
 The global Eth-Trunk interface does not support IPv6 addresses.
 Interface IP addresses can be set for a global Eth-Trunk interface only when the global Eth-
Trunk interface is bound to a VRF.
 The IP address of the global Eth-Trunk interface cannot be on the same network segment as a
public network segment. Nor can the two network segments be a subnet of each other. The IP
address of the global Eth-Trunk interface cannot be on the same network segment as the IP
addresses of other interfaces.
 IFTP: indicates the interface type. The value can be Physical(Physical), Trunk(Trunk), or
GlobalTrunk(GlobalTrunk). The default value is Physical(Physical).
 PN: indicates a port number. Note: The port number of a global Eth-Trunk interface ranges from
100 to 107.
 IPT: indicates an IP address type, which can be PRI(Primary IP address) or
SECONDARY(Secondary IP address).
 MSK: indicates the subnet mask of an IP address.

 In live network, configure two default routes and bind them to the VRF. Configure
different gateway IP addresses and a same route priority for the default routes so that
the data streams can be shared between the two global Eth-Trunk interfaces.

 This command is used to add protocol parameters for IP-based broadband signaling
SCTP associations. SCTP is short for Stream Control Transmission Protocol. An
association is a logical relationship (or channel) for data transmission, which is set up
by two SCTP end points using four-step handshake mechanism defined in the SCTP
protocols.
 This command can be used to set different SCTP link parameters that can be
identified uniquely using SCTPPARAINDEX. You can specify different SCTP link
parameters for Diameter or S-MME links on different interfaces.
 SCTP protocol parameters must be negotiated with the peer NE based on the status
and interface type of the live network.
 Two sets of recommended values are provided in this command for different
interfaces.
 For S6a, S6d, SGs, Gr, and Iu interfaces and the S1-MME interface adopting
the double-active-port mode, the recommended values are the same as the
default values, which are listed as follows:

 The ADD S1APLE command is used to add a local S1AP link entity.
 When an S1-MME interface is configured, only local information needs to be
configured on the MME, but the IP address and port number of the MME need to be
configured on the eNodeB. After the system is started, the eNodeB will initiate the
process of establishing an S1 connection.
 Local S1AP entities are identified using the local IP address and ports.
 LLEINDEX: indicates the number of a local S1AP link entity.
 IPTYPE: indicates the IP address type of a local S1AP link entity.
 LOCALIPV4_1: indicates the first IP address of an S1AP link on the MME side.
 LOCALPORT: indicates the SCTP port number of an S1AP link on the MME
side.
 CROSSIPFLAG: indicates whether an SCTP dual-homing cross path is
available. Cross paths are not recommended because they will increase
networking complexity.
 SCTPINDEX: indicates the index of the SCTP parameter used by S1AP links.
 LLNAME: indicates the name of a local S1AP link entity.

 This command is used to enable or disable the bidirectional forwarding detection

(BFD) function. BFD can rapidly detect communication faults between systems and
report to upper applications.
 To enable the preceding feature, the associated license must be purchased and
activated, and the parameters must be set as required. Before setting parameters, you
can run DSP LICENSE to check whether the license is available, and then run LST
LICCTRL to check whether the associated license control item is enabled. LST
LICCTRL: PN="82203861";
 BFD configuration information is not affected after the BFD function is disabled.

 This command is used to add a BFD session. Acting as a path probe on a layer 3
network, the BFD session reports the link status in real time. The BFD session adopts
two detection modes: single-hop and multi-hop. Single-hop detection is relevant to the
egress from which packets are sent and is used to detect the peer end through only a
single hop. Multi-hop detection is irrelevant to the egress from which packets are sent
and is used to detect the peer end through multiple hops.
 A BFD session is mainly bound to a static route for checking the validity of the static
route based on real-time link status. For details, see ADD IPRTBFDBD and ADD
DFTRTBFDBD.

 This command is used to configure the binding between default routes and
Bidirectional Forwarding Detection (BFD) sessions. Default routes are those whose
destination IP address and subnet mask are both 0.0.0.0. If there is no mapped route,
a router forwards packets based on the default routes. BFD can rapidly detect
communication faults between systems and report to upper applications. In this
manner, the BFD sessions can be used to detect the link status of default routes.
 When Application Scope is set to Global(Global), this command does not apply to
IPv6 configurations.



 BFD Session indicates the real-time status of the BFD session.

 Value of BFD Session State by running command DSP BFDSESSION:
 Admin Down: indicates that the session is in Admin Down state.
 Down: indicates that the session is in Down state.
 Init: indicates that the session is in Init state.
 Up: indicates that the session is in Up state.


 In this example, a pair of active/standby ESUs are used. 0/11 indicates slot 11 of
subrack 0. 0/11/4 indicates port 4 in slot 11 of subrack 0.










 The MME interworks with the HSS using the S6a interface that applies the Diameter
protocol.
 EPC: Evolved Packet Core
 MME: Mobility Management Entity
 HSS: Home Subscriber Server

 The protocols included in the S6a interface protocol stack are described as follows:
 Diameter: transfers subscription and authentication data between the MME and the
HSS and authorizes users to access the EPS network. It is defined in RFC 3588 [31].
 SCTP: is carried over an IP network and transfers data and signaling reliably between
the MME and the HSS.
 SCTP: Stream Control Transmission Protocol
 IP: Internet Protocol
 MME: mobility management entity
 HSS: home subscriber server
 EPS: evolved packet system

 The S6a interface and the Gr interface between the HLR and the SGSN are similar in
aspects of the location and function on the network. Even though the Gr interface
uses the MAP protocol and the S6a interface uses the Diameter protocol, their major
message flows are similar.
 As shown in the preceding figure, the S6a interface protocol stack is simpler than the
Gr interface protocol stack. Therefore, the S6a interface is easier to implement and
maintain.
 In compliance with SS7, the Gr interface is mandatory between the SGSN and the
HLR on a GSM or UMTS network. In addition, Gr over TDM and Gr over IP have
different protocol stacks.
 MAP: Mobile Application Part
 TCAP: Transaction Capability Application Part
 SCCP: Signaling Connection Control Part
 MTP3: Message Transfer Part Layer 3
 M3UA: MTP3-User Adaptation Layer

 SCTP Multi-Homing + Dual Active Ports

 The MME communicates with the HSS using Router A and Router B over the IP
backbone network. In addition, the MME connects to the two routers with two PFIs
respectively and the IP addresses of a router and its connected PFI port are in one
network segment.
 ECU: enhanced control plane unit
 EPU: enhanced packet forward unit
 PFI: packet forward interface

 SCTP Non-Multi-Homing + Active/Standby Port + ARP Detection

 The MME communicates with the HSS using Router A and Router B over the IP
backbone network. In addition, the MME connects to the two routers with two PFIs
(active and standby) respectively and the IP addresses of the two PFI ports are in one
network segment.
 The ARP detection is used to detect port faults. Once a port fault is detected, a
active/standby switchover occurs to the two ports.
 ARP: Address Resolution Protocol


 E2E: End to End


 Diameter client: sends request messages.

 Diameter server: receives and processes request messages.
 Diameter proxy: forwards the received Diameter messages.
 The Diameter server and client are logically separated and the USN9810 can serve
as a Diameter server or a Diameter client.
 A Diameter entity is identified by the host name comprising the host ID and realm
name. For example, hss1.huawei.com.cn, where Hss1 is the host ID and
huawei.com.cn is the realm name.




 Diameter connection setup: negotiate and setup by Capabilities-Exchange-Request,

Capabilities-Exchange-Answer message.
 Establishing connection: Before a connection is established, any Diameter peer can serve as
an SCTP client or an SCTP server. The final connection state is determined by the dynamic
connection negotiation procedure.
 Exchanging capability data: the capability data includes applications and vendor types
supported by the two peers.
 You can configure certain important data on the Diameter peer in advance to reject illegal or
irrelevant connection in the procedure.
 Diameter connection detection: detect by Device-Watchdog-Request, Device-Watchdog-
Answer message.
 Various messages can be transmitted through normal peer connection. If no message is sent
or received through the connection for a long period, the two nodes send and receive detection
messages, DWR and DWA, as shown in Figure 1-9. If the DWR or DWA message cannot be
sent or received, the Diameter node infers that the connection is faulty. In this case, the node
tries to re-establish the connection or switch to the standby peer connection.
 Diameter connection release: release by Disconnect-Peer-Request, Disconnect-Peer-Answer
message.
 The peer connection can be normally disconnected. To disconnect a connection, a Diameter
node sends a DPR message to the peer Diameter node. After receiving the message, the peer
Diameter node returns a DPA message and disconnects the lower-layer connection first. If the
connection is interrupted, for example, caused by network and system faults, the peer that
detects the disconnection repeatedly tries to restore the connection based on the configuration
of the timer.

 The Diameter client searches the locally configured Diameter routing table for links to
the peer entity. The links and link sets are configured and stored in the system and
they can be obtained using the destination realm name from the routing table.

 The USN9810 first obtains user IMSIs and searches the IMSIHSS table for IMSI
prefixes based on the obtained IMSIs using the longest match rule. If no IMSI prefix is
obtained, the USN9810 will construct a default realm name. If the required IMSI prefix
is obtained, it will obtain the peer realm name.
 IMSI: international mobile station identity

 The following information need to be configured:

 Local entity: Configure information about the local entity at the Diameter layer,
including the host name and domain name of the local entity. When configuring a
local entity, you must specify the local entity index as its internal identifier on the
MME.
 Peer entity: Configure information about a peer Diameter entity connected to the
MME, including the host name of the peer entity. When configuring a peer entity,
you must specify a peer entity index as its internal identifier on the MME.
 Diameter route group: Configure the method of selecting routes from the local
entity to a peer entity. A Diameter route group consists of Diameter domain
routes and host routes.
 Diameter host route: Configure the route from a local entity to the peer entity host.
 Diameter domain route: Configure the route from a local entity to the peer entity
domain.
 Diameter link set: Configure a link set from a specified local entity to a specified
peer entity. A link set index identifies a link set. Links can be selected in load
sharing, active/standby, round-robin, or activation mode.
 Diameter link: To add a link from a local entity to a peer entity, configure the IP
addresses and port numbers of these entities.
 IMSI-HSS mapping table: Query the domain name and route group based on the UE
IMSI.

 If no record is found in the IMSI-HSS mapping table, the MME automatically assembles a
domain name.
 If no Diameter route group index is found in the IMSI-HSS mapping table, the MME
automatically queries the Diameter domain route table based on the domain name.
 The MME obtains the HSS domain name and the Diameter route group index from the
IMSHSS table based on the UE IMSI. If they cannot be found in the IMSIHSS table, the MME
assembles a domain name in the epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org format based
on 3GPP specifications.
 2. If the Diameter route group table is configured, the MME selects host routes or domain
routes based on the route selection mode specified in the table. If the table contains only host
routes, the MME obtains the HSS host name based on a host route. (In this case, the domain
name is also obtained.) If the table contains only domain routes, the MME obtains the index of
the next hop based on a domain route. (In this case, it is recommended the Diameter route
group table not be configured so that the MME automatically obtains the index of the next hop
based on the domain route table.) If the table contains both host routes and domain routes, the
MME selects host routes or domain routes based on the route selection mode specified in the
table.
 3. The MME obtains the index of the next hop peer entity from the Diameter host or domain
route table based on the HSS domain name. If the MME has obtained the HSS host name, it
queries the peer entity index from the peer entity table.
 4. The MME obtains a link set from the Diameter link set table based on the local entity index
and peer entity index, and selects a link based on the link selection mode specified in the table.
 5. The MME obtains the IP addresses and port numbers of the local entity and peer entity
based on the link index, and sends packets to the corresponding HSS at the SCTP or IP layer.


 The SCTP is the reliable datagram transmission protocol based on unreliable

transmission service protocols, such as the IP.
 The SCTP improves on the TCP defects and enhances the reliability for signaling
transmission. The improvement includes:
 Proper congestion control
 Flooding and spoof attack protection
 More reliable real-time performance
 Multi-homing

 TCP: Transmission Control Protocol
 IUA: ISDN Q.921-User Adaptation Layer

 Transmission address
 The SCTP transmission address is composed of an IP address and an SCTP port
number. The SCTP port number is used by the SCTP to identify users of the same
address. It means the same as the TCP port number. For example, the IP address
10.105.28.92 and the SCTP port number 1024 define together a transmission address,
and 10.105.28.93 and 1024 define another transmission address. Similarly,
10.105.28.92 and 1023 define a different transmission address.

 A host is configured with one or multiple IP addresses. It is a typical physical entity.

 SCTP Endpoint is one of basic concepts of SCTP. An endpoint is the logical
sender/receiver of SCTP packets. It is a typical logical entity.
 Host and end point
 A host is a computer configured with one or more IP addresses. It is a physical entity.
 An end point is a logical SCTP concept. It is the logical sender and receiver of
datagrams. It is a logical entity.
 According to the SCTP protocol, there is only one association between two end points
and one host can correspond to multiple end points.



 The workflow of the MME serving as the sending end is as follows:

1.The Diameter protocol application sends a message such as an update location
message, to the HSS to which a specified IMSI belongs.
2.Based on the mapping between the IMSI and the HSS, the MME uses the HSS
host name such as hss.huawei.com, as the peer host ID in the Diameter
message.
3.The MME searches the Diameter peer entity table for the peer entity index
(peeridx) based on the HSS host name (hss.huawei.com).
4.The MME obtains the required Diameter link set and links to the peer entity
based on the peer entity index and local entity index.
5.The MME obtains the IP address and port number of the HSS based on the
configured link information.
6.The MME queries the Ethernet port number and next-hop address in the IP
routing table and sends the message to the HSS over IP.
 The workflow of the HSS serving as the receiving end is as follows:
1.Upon receiving a data packet from the Ethernet port, the HSS uncompressed,
processes, and constructs a Diameter message.
2.The HSS checks whether its host ID is carried in the Diameter message. If the
HSS host ID is carried in the message, it will forward this message to the
Diameter application layer for further processing.

 Processing in sending side MME:

 1. Diameter application decide to send a message ( for example, update location ) to the home HSS of
specific IMSI.
 2. According to the mapping of IMSI and HSS host identity ( ADD IMSIHSS), the MME use the home
HSS identity of that IMSI ( for example, hss.huawei.com ) as the destination host identity of Diameter
message.
 3. MME use the realm name of HSS host identity ( huawei.com) to check the Diameter routing table, and
find the peer entity index , which is the index of agent in this case.
 4. MME find the corresponding diameter link set and link of that peer entity.
 5. MME find the agent IP address according to the SCTP association of the diameter link.
 6. MME check the IP routing table, find the Ethernet port and the next hop, then forward the message to
agent via the IP network.
 Processing in the agent:
 1. Receive the packet from the Ethernet port, decapsulate and processing, up to the diameter layer
message.
 2. Agent check the destination host identity of diameter message, find out that is not himself, but for a
direct connect peer entity, so the agent check the link set table and forward. If the destination host
identity is not a direct connect entity of local realm, the agent will check the DMRT routing table to find a
direct connect peer entity, then forward the message to that entity for further forwarding.
 Processing in the receiving side HSS:
message.
 2. HSS check the destination host identity of diameter message, find out that is himself, then forward the
message to diameter application layer for further processing.

 Processing in sending side MME:

 1. Diameter application decide to send a message ( for example, update location ) to the home HSS of
specific IMSI.
 2. If the MME does not know the IMSI and it's corresponding HSS host ID, MME will select a Diameter
agent as next hop.
 3. The MME queries the peer entity index from the Diameter routing table based on the HSS domain
name (in the epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org format). In this case, the peer entity index is
also the index of the DRA.
 4. The MME finds the corresponding diameter link set and link of that peer entity.
 5. The MME finds the agent IP address according to the SCTP association of the diameter link.
 6. The MME checks the IP routing table, finds the Ethernet port and the next hop, then forwards the
message to agent via the IP network.
 Processing in the agent:
message.
 2. The Diameter agent needs to map the IMSI to a destination HSS host ID. If the realm of HSS is a
direct connect peer entity, the agent check the link set table and forward. If the destination host identity is
not a direct connect entity of local realm, the agent will check the DMRT routing table to find a direct
connect peer entity, then forward the message to that entity for further forwarding.
 Processing in the receiving side HSS:
message.
 2. HSS check the destination host identity of diameter message, find out that is himself, then forward the
message to diameter application layer for further processing.


 FE: front end, a signaling access and service logic processing component on the HSS
 DRA: diameter routing agent



 ECUs are used to parse signaling packets

 EPUs or PFIs are used to forward packets


 Data provided in this document is used only as an example. You can configure a site
based on the site's network plan and system configuration.
 IMSI: international mobile station identity






 The CGP MML panel is used to execute the hardware related MML command.

 MOD PORT is used to modify some parameters related to the PFI port, such as MTU
and WORKMODE.
 The working mode configured for this port must be the same as that of the peer port.
 By default, MTU is set to 1500 and WORKMODE to AUTO for the Ethernet port on
the PFI during system initialization.

 The USN9810 MML panel is used to execute the service related MML command.

 This command is used to add an IP address to the service IP address pool of the
EPU/EPUB/ESU/ESUB/EVU.
 Note:
 The board identified by the Subrack No. and the Slot No. is configured on the slot
description list. The board type is active EPU.
 Important Parameter:
 SRN,SN: subrack number, slot number.
 IPT: IP address type
 IPV4: IP address
 DESC: Description

 The ADD IFIP command is used to set IP addresses for PFI’s main interfaces and sub-
interfaces.
 A maximum of 48 IP addresses can be configured for a main interface, including a primary IP
address and 47 secondary IP addresses. The primary IP address must be configured before
any slave one is configured.
 A maximum of four IP addresses can configured for a sub-interface, including a primary IP
address and three secondary IP addresses.
 SRN, SN: indicates a subrack number and slot number.
 PN: indicates a port number. Notes: The port numbers of an EPU start from 0 and
increase from top to bottom. The value ranges from 0 to 7.
 IFTP: indicates an interface type. The value can be Physical(Physical)
,Trunk(Trunk), GlobalTrunk(GlobalTrunk)
 SIF: indicates a sub-interface number, which ranges from 1 to 16. If this parameter is
not specified, running this command will set an IP address for the main interface.
Before using this parameter, you must run the ADD SUBIF command to add sub-
interfaces.
 IPT: indicates an IP address type, which can be PRI (primary IP address) or
SECONDARY (secondary IP address).
 MSK: indicates a mask.

 Command ADD IPRT is used to configure the static IP route to the destination IP
address.
 IP: The destination IP address or network segment of the IP route
 MSK: Mask. If the destination address is an IP address rather than an IP
network segment, the mask is 255.255.255.255.
 GATE: Gateway. The IP address of the gateway and the IP address of the port
connected with the USN9810 must be within the same network segment.
 PRE: Route priority. The route with higher priority is chosen to send the IP
messages. The route with lower priority is chosen in case the high priority
route is in congestion or fault. Note: represents the highest priority. The bigger
the number, the lower the priority.
 DESC: Description
 VRFNAME: VRF name. This parameter specifies the VRF to which the route
belongs.

 Command ADD SCTPPARA is used to define some SCTP protocol parameter table,
which will be used when configuring the Diameter link.
 We can define different SCTP parameter table, identified by different
SCTPPARAINDEX value. We can use these different SCTP parameter table when
configuring the diameter link of different interface.

 Command ADD DMLE is used to configure the local entity information.

 LOINDEX: Local entity index
 LOHSTNAME: Local entity host name
 LORLMNAME: Local entity realm name
 PDTNAME: Product name

 Command ADD DMPE is used to configure the direct connected peer entity.
 The indirect connected peer entity is not needed to be configured.
 PEERIDX: Peer entity index. The index and host name uniquely identify an
entity. The index must be unique and need not be added in sequence.
 PEERHTNAM: Peer entity host name
 PEERNAM: Peer entity name

 Command ADD DMLKS is used to configure the diameter link set of direct connected peer entity.
 Parameter:
 LINKSIDX: Local entity index
 LOCALIDX: Local entity index
 PEERIDX: Peer entity index
 LSSELMODE: link set selection Mode. This parameter specifies how the USN9810 selects a
Diameter link from a Diameter link set for service provision.
 Value range: SELMODE_ROUND_ROBIN, SELMODE_LOAD_BALAN,
SELMODE_MASTER_SLAVE, or SELMODE_ACTIVE
 Default value: SELMODE_LOAD_BALAN
 SELMODE_ROUND_ROBIN: The USN9810 selects links from the link set in the
sequence of the link number.
SELMODE_LOAD_BALAN: The USN9810 selects an active link from the link

set so that loads are balanced among all activate links in the link set.
SELMODE_MASTER_SLAVE: Links in the link set work in 1+N backup mode.

In this mode, services are transmitted over only the master link and the
USN9810 always selects the master link. The other links work in slave mode.
SELMODE_ACTIVE: The USN9810 selects the link used the last time from the
link set.
 LINKSNAM: Link set name



 ADD DMHOSTRT is used to add a Diameter host route. A Diameter host route indicates that a peer
entity is selected based on the host name. This command is used when the MME connects directly to a
peer entity over the Diameter protocol.
 The ADD DMRTGRP command can be used to classify the host routes into different Diameter route
groups by route selection mode. The MME selects routes based on the route group configurations.
 Parameter Description
 Route Index: This parameter specifies the index of the Diameter host route under an MME.
 Application Name: This parameter specifies the interface type for the Diameter host route.
 Value: S6A/S6D(S6a/S6d)
 Route Select Mode: This parameter specifies the mode used by the USN9810 to select a peer
entity based on a specified Diameter host route.
 Values: SELMODE_ROUND_ROBIN, SELMODE_MASTER_SLAVE, and
SELMODE_PRIORITY_WEIGHT
 Destination Entity Select Mode: This parameter specifies the method of selecting a peer entity.
To ensure compatibility with earlier versions, a peer entity can be identified by the index or host
name.
 Peer entity index: This parameter specifies the index of a peer entity.
 Peer Entity Host Name: This parameter specifies the host name of a peer entity.
 Route Name: This parameter specifies the name of a Diameter host route.
 Priority: This parameter specifies the priority of the peer entity in a Diameter host route.
 Weight: This parameter specifies the weight of the peer entity in a Diameter host route.

 ADD DMRTGRP is used to add a Diameter route group. A Diameter route group consists of Diameter domain routes and host routes.
You can use ADD DMRT and ADD DMHOSTRT to configure Diameter domain routes and host routes, respectively. When connecting
to a peer entity over the Diameter protocol, the MME selects the route selection mode based on the route group information configured
by running ADD IMSIHSS .
 Route Group Index: This parameter specifies the index of a Diameter route group under an MME.
 Route Mode: This parameter specifies the route mode in a Diameter route group.
 Values: REALM_ROUTE and HOST_ROUTE.
 Configuration notes:
When the MME connects to a peer entity through a DRA or the mapping between the IMSI and the host
name is not specified, set this parameter to REALM_ROUTE.
When the MME connects directly to a peer entity, set this parameter to HOST_ROUTE.
 Route Index: This parameter specifies the index of a route.
If Route Mode is set to REALM_ROUTE, the value of Route Index must be the same as the route
index configured by running ADD DMRT. Under the same route group index, only one or no route index
can be configured.
If Route Mode is set to HOST_ROUTE, the value of Route Index must be the same as the route index
configured by running ADD DMHOSTRT. A maximum of 16 route indexes can be configured under the
same route group index and the route selection modes of the routes must be the same.
 Peer Entity Index: This parameter specifies the index of a peer entity.
The value of this parameter must be the same as the peer entity index configured by running ADD
DMRT.
If Route Mode is set to REALM_ROUTE and the Mode parameter in ADD DMRT is set to
SELMODE_IMSI_PRIORITY, you must set the Peer Entity Index parameter.
If Route Mode is set to REALM_ROUTE and the Mode parameter in ADD DMRT is not set to
SELMODE_IMSI_PRIORITY, do not set the Peer Entity Index parameter.
 Route Group Name: This parameter specifies the name of a Diameter route group.
 Routes under the same route group index must have the same Route Prefer Select Mode and Route Group Name values.

 ADD IMSIHSS is used to configure the mapping between the IMSI and the HSS.The
MME can select the HSS to which an IMSI belongs based on the mapping between
the IMSI and the HSS.
 IMSIPRE: IMSI prefix. You can obtain it based on the user IMSI using the
longest match rule. It is used to obtain the HSS realm name.
 HSSRLM: HSS realm name. If the HSS host name is not configured, the MME
can select the HSS using the HSS realm name.
 GRPIDX: This parameter specifies the index of a Diameter route group under
an MME. A Diameter route group consists of Diameter domain routes and host
routes.
 MNNAME: Description information.




 This slide describes only how to configure Diameter routes and the mapping between
IMSIs and HSSs. The configuration of the IP layer is omitted.






 A Diameter route group is optional. If a Diameter route group is not configured, the
MME automatically searches for a domain route based on the domain name obtained
from the mapping between IMSIs and HSSs.










 The protocol stack of both the S10 interface and S11 interface consists of IP, UDP,
and GTPC protocols of an IP network.
 The GPRS Tunnelling Protocol-Control Plane (GTPC) provides tunneling of signaling
messages not only between MMEs but also between the MME and SGW.


 Dual active interface + OSPF dynamic route networking: The dual active interfaces
are configured on a pair of EPU boards for interconnection with two PE devices or L3
switches separately. The OSPF dynamic routing protocol is configured for link route
detection in load sharing mode. The OSPF can detect physical faults of links rapidly.
For logical faults, the detection time is based on the timeout of the HELLO detection.

 The active and standby interfaces are configured on a pair of EPU boards for
interconnection with two PE devices separately. The active and standby interfaces are
in L2 bearer link backup mode, that is, only one interface IP address is configured for
two physical links. The peer PEs or L3 switches are configured with the VRRP to have
one virtual interface IP address. To ensure that faults of the peer device are detected
on USN side for active/standby interface switchover, the ARP detection must be
supported (L2 link detection). The ARP detection is a mandatory mode for L2
reliability detection in the networking scheme.


 The transport layer protocol of GTPC is the User Datagram Protocol (UDP). The UDP
is a connectionless protocol. The GTPC path is a logical concept. The connection of
the path is ensured by means of GTPC path detection.

 When a GTPC message such as a GTPC request messages or a three-way

handshake response messages is sent, the local end caches this message to ensure
retransmission of the message in the case of timeout without response. In this case, a
GTPC path is created if no GTPC path to the peer end exists. For example, when the
Create PDP Context Request message is sent, a GTPC path is created if no path
from GTPC1 to GTPC2 exists.

 The GTPC path is detected by using the Echo message. The GTPC protocol entity
periodically sends an Echo Request message to the peer end and meanwhile starts
the T3 timer used for waiting an Echo Response message. If the GTPC path does not
receive the response message after timeout of the T3 timer, the GTPC retransmits the
Echo Request message. The maximum number of retransmissions is N3. If timeout
still occurs, the GTPC path is disconnected. If the response message is received in
T3 x N3s, the GTPC path is normal.
 GTPC path detection includes normal path detection and fault detection.
 Detection interval of normal paths is configured by using SET GTPPUB command.
The minimum interval of fault path detection is 60s and the maximum is 2 x T3 x N3s
(in the case of 2 x T3 x N3 > 60).
 The T3 timing length and number of N3 are configured by using SET T3N3 command.

 Each GTPC path has an aging timer to scan the path periodically. The aging counter
increases by one for each path scanning. If a signaling message is sent in the path
(except Echo detection messages), the aging counter is cleared. If the count of the
aging counter is larger than the aging threshold, the GTPC path is deleted because
no signaling message is sent in the path for a long time.
 You can run the SET UGTP command to configure the idle scanning duration and
aging threshold.









 Command MOD PORT is used to set the PFI port attribute, such as MTU (octet) and
Work mode
 The work mode must be set to the same value as that of the peer communication port.
 By default, the maximum transmission unit and work mode of the EETH port of the
PFI board are preset to 1500 and Auto when the system is initialized.
 By default, the maximum transmission unit of the FETH port of the PFI board is preset
to 1500 when the system is initialized.
 SRN, SN, PORTID: subrack number, slot number and port number.
 PORTTYPE: port type. Value: electric Ethernet, Fiber Ethernet, ATM
 PEERSN: peer slot number
 PEERPID: peer port ID
 MTU: MTU (octet). Value: 1280-1600. Default value: 1500
 WORKMODE: Work mode. Note: initial value of electrical Ethernet port Auto,
initial value of optical Ethernet port Full-duplex, 1000 M/s.


 The USN9810 MML panel is used to run the service related MML command.

 This command is used to add an IP address to the service IP address pool of the
EPU/EPUB/ESU/ESUB/EVU.
 SRN, SN: subrack number, slot number.
 IPV4: IP address
 DESC: description

 Command ADD BINDGTPCIP is used to set an EPU logical IP address as a GTPC IP

address.
 IPV4: IPv4 address
 IPV6: IPv6

 Command ADD IFIP is used to configure the interface IP address of PFI interface (active
interface and sub-interface).
 A maximum of forty-eight IP addresses can be configured for each active interface, that is, 1
primary IP address and 47 secondary IP addresses. The primary IP address is configured
before secondary IP addresses.
 Four IP addresses can be configured for each sub-interface maximumly, that is, 1 primary IP
address and 3 secondary IP addresses.
 Parameter:
 SRN, SN: subrack number, slot number.
 PN: port number. Note: On EPU backplane, the port number starts with 0, from up to
down. Value range: 0–7.
 IFTP: interface type. Value range: Physical (physical interface) or Trunk (Trunk).
Default value: Physical (physical interface).
 SIF: sub-interface number. If the sub-interface number is not designated, this
command is used to set the IP address of the active interface. You are required to add
a sub-interface by using the ADD SUBIF command before typing the parameter. Value
range: 1–16.
 IPT: IP address type. Value: PRI (primary IP address), SECONDARY (secondary IP
address).
 IP: IPv4 address
 MSK: mask

 Command ADD IPRT is used to configure the static IP route to the destination IP address.
 The IP address of the destination must be in a different network segment of the port IP
address.
 The IP address of gateway must be different from the board IP address or the port IP address.
 If there is no gateway between the sites, for example, the USN9810 is connected to the
destination directly or through a LanSwitch, do not set this parameter.
 The smaller the number, the higher the priority of the route. More than one route can be added
to connect one destination through various gateways. SGSN chooses the route with higher
priority.
 You are allowed to configure at most 15 routes to the same destination address. If there is
more than one route with the highest priority to the destination, SGSN chooses up to three
routes to share the load.
 IP: the destination IP address or network segment of the IP route
 MSK: mask. If the destination address is an IP address rather than an IP network
segment, the mask is 255.255.255.255.
 GATE: gateway. The IP address of the gateway and the IP address of the port
connected with the USN9810 must be within the same network segment.
 PRE: route priority. The route with higher priority is chosen to send the IP messages.
The route with lower priority is chosen in case the high priority route is in congestion or
fault. Note: represents the highest priority. The bigger the number, the lower the
priority.

 Command SET UGTP is used to set the scanning parameters of a GTPC path, that is,
aging and version detection.
 Idle Counter Interval: This parameter specifies the scanning interval of the
idle counter in the GTP path. In the case of expiry, the aging count increases
by one.
 SM Path Idle Count: This parameter specifies the upper limit for the aging
count of the GTP path (SM attribute). When the upper limit is reached, the SM
attribute of this path is cleared.
 MM Path Idle Count: This parameter specifies the upper limit for the aging
count of the GTP path (MM attribute). When the upper limit is reached, the MM
attribute of this path is cleared.
 GTPMAP Path Idle Count: This parameter specifies the upper limit for the
aging count of the GTP path (LM attribute). When the upper limit is reached,
the GTPMAP attribute of this path is cleared.
 Path Version Check Interval: This parameter specifies the detection period of
the path version. The detection is used to upgrade an earlier version into a
later version.

 ECHOSIG: This parameter specifies whether to send GTPC ECHO signaling. The default value is ON.
 EI: This parameter specifies the interval of sending Echo Request in the GTPC path. The default value is
239.
 V2EI: Interval of send GTPv2 ECHO(s
 POOLSRCPORTSW: This parameter specifies whether the default SGSN transparently transmits the
source port number in the Identification/SGSN Context Request message sent by the source SGSN to the
destination SGSN in Pool networking mode. When this function is enabled, the local SGSN transmits the
source port number transparently. When this function is disabled, the local SGSN allocates the source port
number. The default value is ON.
 PEERRECOVERYSW: This parameter specifies whether to deactivate subscribers when the Recovery
value of the peer end changes. When this function is enabled, subscribers are deactivated when the
Recovery value of the peer end changes. When this function is disabled, subscribers are not deactivated
when the Recovery value of the peer end changes. The default value is OFF.
 PATHDOWNDEASW GTPC: This parameter specifies whether to deactivate subscribers when the GTPC
path is disconnected. When this function is enabled, subscribers are deactivated. When this function is
disabled, subscribers are not deactivated. The default is OFF.
 PATHVERDETECTSW: This parameter specifies whether to detect the GTPC path of the V0 version by
using Echo messages of the V1 version. If the detection is successful, the GTPC path is upgraded to the
version V1. Otherwise, the version of the GTPC path keeps unchanged. When this function is enabled,
Echo messages of the V1 version are used to detect the GTPC path of the version V0. If this function is
disabled, Echo messages are not used to detect the GTPC path of the version V0. The default value is ON.
 DNSGTPCPATHFILTERSW: This parameter is used to specify whether the faulty peer IP address is
filtered in the IP address list resolved by the DNS according to the GTPC path status. If the GTPC path
does not exist, the GTPC path is normal. When the function is enabled, only the IP address list of the
normal GTPC paths is used in the DNS resolution result. When this function is disabled, the GTPC path
status is not determined. The default value is ON.
 LOCRECOVERYSW: This parameter specifies whether to update the Recovery value on the local end.
When this function is disabled, the Recovery value at the local end keeps unchanged after restart of all
SPP processes. Otherwise, the Recovery value increases by one. When the Recovery value is set to 255,
the value increases by one and then changes to 0. The default value is OFF.

 Command SET T3N3 is used to configure T3 and N3 according to GTPC versions

and message types.
 T3 specifies the maximum time to wait for a response to a path detection message.
N3 specifies the maximum number of attempts to send a path detection message.










 In this example, the S10 and S11 interfaces share the same EPU logical IP and the
same PFI interface IP. Therefore, you only need to add a static route in step 8.










 A GUTI is a globally unique identifier that an MME provides for a UE. It consists of the
following information:
 GUMMEI: indicates an identifier in the format of mobile country code (MCC) + mobile
network code (MNC) + MME identifier.
 M-TMSI: indicates a unique 32-bit identifier of a UE in an MME.
 An MME provides GUTIs implicitly in the attach or TAU procedure or explicitly in the
GUTI reallocation procedure. The GUTI reallocation procedure is triggered only when
an MME is in the EMM-REGISTERED status.
 A TAI is in the format of MMC + MNC + tracking area code (TAC).
 A UE does not need to request TAU when moving between the TAs on the TA list.
 A network pages a UE in all TAs on the TA list.
 An MME sends the TA list to a UE through the Attach Accept, TAU Accept, or GUTI
Reallocation Command message.

 An MME provides a GUTI for a UE based on the MME identifier. The MME compares
the MCC, MNC, MME group identifier, and MME code in the GUTI with those in the
MME identifier in the attach procedure. If they are different, the attach is an inter-MME
attach.
 Set consecutive MME codes when setting up a serving GPRS support node (SGSN)
pool if the network resource identifier (NRI) of the SGSN contains less than eight bits.

 T3412(min): indicates the time duration of timer T3412 in the unit of minute. This parameter specifies the time duration for UEs to initiate periodic TAU. The
T3412 is started if the UE status changes from ECM-CONNECTED to ECM-IDLE. When the timer expires, a UE initiates TAU.
 T3402(min): indicates the time duration of timer T3402 in the unit of minute. The parameter value is sent to an UE through the Attach Accept or TAU Accept
message. The T3402 is started if an MME sends the Attach Accept or TAU Accept message more than five times. When the timer expires, the MME resends
the Attach Accept or TAU Accept message.
 T3413(s): indicates the time duration of timer T3413 in the unit of second. The T3413 is started when an MME sends a paging request and is stopped when
the MME receives a service request. When the timer expires, the MME resends a paging request.
 N3413(times): indicates the times for resending paging requests.
 Repaging delta increased(s): indicates the increase of the time interval for resending paging requests before receiving a service request. (Unit: second)
 Mobile reachable timer(min): indicates the time duration of the mobile reachable timer in the unit of minute. The mobile reachable timer monitors whether an
UE initiates periodic TAU. If a UE does not initiate periodic TAC when the timer expires, the MME implicitly separates the UE. The timer is started when the
NAS signaling link is released and is stopped when the NAS link is established.
 GUTI reallocation timer(h): indicates the time duration of the GUTI reallocation timer in the unit of hour. An MME starts the GUTI reallocation timer when a UE
is in the ECM-CONNECTED status. When the timer expires, the MME initiates a GUTI reallocation procedure.
 GUTI reallocation in attach or TAU: indicates whether an MME reallocates a GUTI in the attach or TAU procedure.
 Handover preparation timer(s): indicates the time duration of the handover preparation timer in the unit of second.
 Handover complete timer in source MME(s): indicates the time duration of the source handover preparation timer in the unit of second. The source handover
preparation timer is started when a source MME sends the Handover Command message to the source eNodeB and is stopped when the source MME
receives the Forward Relocation Complete message from the target MME. When the timer expires, the source MME releases UE data.
 Handover complete timer in target MME(s): indicates the time duration of the target handover preparation timer in the unit of second. The target handover
preparation timer is started when a target MME sends the Forward Relocation Response message to the source MME and is stopped when the target MME
receives the Handover Notify message from the target eNodeB. When the timer expires, the target MME releases UE data.
 T3 timer(s): indicates the time duration of timer T3 in the unit of second. The T3 is triggered in the following scenarios: The source MME receives the Forward
Relocation Complete message in the inter-HO procedure.
 The source MME sends the Context Response message to the target MME in the inter-TAU procedure.
 The target MME receives the Forward Relocation Complete ACK message form the source MME in the inter-HO procedure and indirect bearers have been
established on the target serving gateway (SGW).
 An MME receives the Handover Notify message in the intra-HO procedure.
 An MME receives the Create Session Response message from the MME if the SGW is changed in the X2-based HO procedure. When the T3 expires, the
source MME deletes data and bearers.


 Parameters:
 TALISTID: indicates the identifier of a TA list.
 TAI: indicates the identifier of a TA, which is in the format of MCC + MNC +
TAC.
 Notes:
 1. For details about the TAI, see Table 9.9.3.33.1 in 3GPP TS 24.301.
 2. The MCC contains three binary coded decimal (BCD) digits. The MNC contains two
or three BCD digits.
 3. The TAC code is a 4-digit hexadecimal number. Prefix zeros (0s) if the TAC
contains less than four digits.

 USRRANGE: indicates the UE range. For UEs in a number segment, values are
SPECIAL (indicating UEs with the specified IMSI prefix) and IMSI_RANGE (indicating
UEs in the specified IMSI range).
 SECPLC: Select the value AUTHANDPROTECTED on the live network. The other
values cannot ensure proper attach.
 SUPTINTAGTH: indicates the integrity algorithm supported by an MME. Select all
values in normal cases. The USN9810 determines the maximum algorithm supported
by a UE and selects the maximum algorithm supported by the MME and UE.
 SUPTCIPHAGTH: indicates the encryption algorithm supported by an MME. All values
are selected in normal cases. The USN9810 determines an encryption algorithm based
on the UE capability.
 IMEIOPTION: Set this parameter to NO(NO) unless the carrier has special
requirements, for example, when the carrier needs to test the UE validity.
 Authentication Event: indicates which procedures are flexible authentication events.
This parameter is under license control. The parameter is valid only when the involved
license item (Flexible Authentication Based on Subscriber Group Function) is enabled.
 Authentication Period: If the period of the UE registration reaches the value of this
parameter, authentication is performed in the basic procedures (Attach, TAU, Detach,
and Service Request). Disable the period authentication function in normal cases to
ensure that UEs are authenticated in each procedure.

 1. The USN9810 checks whether the UE IMSI matches with any configured IMSI prefix
when a UE initiates attach or TAU.
 If yes, go to step 2.
 If no, the access is allowed.
 2. The USN9810 checks whether the UE matches any access restriction configuration
record.
 If no, go to step 4.
 3. The USN9810 checks whether at least one of the UE attributes (including the
subscribed ARD and APN) matches the configured attributes based on the subscribed
ARD/APN.
 If no, go to step 5.
 4. The USN9810 implements the configured access restriction policy.
 5. The USN9810 implements the access restriction policy reverse to the configured one.
 6. The USN9810 checks the setting of Control Type.
 If Control Type is set to REJECT(REJECT), the access is rejected.



 The default EPS bearer is set up when a UE sets up a PDN connection and is not
released during the PDN connection. All other EPS bearers are dedicated bearers.
 Activate dedicated bearers to set up bearers using a certain QoS and traffic flow
template (TFT) between a UE and the EPC. The activation of dedicated bearers is
triggered on the network side, or is triggered as a part of the bearer
allocation/modification procedure requested by a UE.
 Activate the default bearer to create a default EPS bearer context between a UE and
the EPC. The activation of the default bearer is a part of the attach procedure. If the
attach fails, the default bearer cannot be activated.

 SET ESM
 T3485(s): indicates the time duration of timer T3485 in the unit of second. The T3485 is started when an
MME sends the ACTIVATE DEFAULT/DEDICATED EPS BEARER CONTEXT REQUEST message to a
UE. It is stopped when the MME receives ACTIVATE DEFAULT EPS BEARER ACCEPT/REJECT or
ACTIVATE DEDICATED EPS BEARER ACCEPT/REJECT message from the UE. When the timer expires,
the MME resends the ACTIVATE DEFAULT/DEDICATED EPS BEARER CONTEXT REQUEST message
to the UE.
 N3485(times): indicates the times for resending the ACTIVATE DEFAULT/DEDICATED EPS BEARER
CONTEXT REQUEST message.
 T3486(s): indicates the time duration of timer T3485 in the unit of second. The T3486 is started when an
MME sends the MODIFY EPS BEARER CONTEXT REQUEST message to a UE and is stopped when the
MME receives the MODIFY EPS BEARER CONTEXT ACCEPT/REJECT message from the UE.
 N3486(times): indicates the times for resending the MODIFY EPS BEARER CONTEXT REQUEST
message.
 T3489(s): Timer T3489 is started when an MME sends the ESM INFORMATION REQUEST message to a
UE and is stopped when the MME receives the ESM INFORMATION RESPONSE message from the UE.
When the timer expires, the MME resends the ESM INFORMATION REQUEST message and the T3489 is
restarted. If the MME does not receive a response from the UE when the resending times exceed the upper
limit, the MME releases certain resources.
 N3489(times): indicates the times for resending the ESM INFORMATION REQUEST message.
 T3495(s): Timer T3495 is started when an MME sends the DEACTIVATE EPS BEARER CONTEXT
REQUEST message to a UE and is stopped when the MME receives the DEACTIVATE EPS BEARER
CONTEXT ACCEPT message from the UE. If the MME does not receive a response from the UE when the
resending times exceed the upper limit, the MME deactivates EPS bearer contexts.
 N3495(times): indicates the times for resending the DEACTIVATE EPS BEARER CONTEXT REQUEST
message.

 SET SMFUNC
 DUALFLAG: indicates whether the MME or SGSN to which UEs are handed over
supports IPv4 and IPv6 addresses. If a UE sets this parameter to YES during the
bearer context activation procedure, the PGW assigns an IPv4 address and an IPv6
address to the UE. If the MME or SGSN does not support dual stack, the bearer
context activation or handover procedure fails.
 INDFWD: During a handover from the UTRAN/GERAN (Gn/Gp SGSN) to the E-
UTRAN, an MME (on the E-UTRAN) sets up an indirect forwarding tunnel between the
SGW and eNodeB to forward UE data received from the UTRAN/GERAN (Gn/Gp
SGSN). During a handover from an E-UTRAN to another one, a source MME can send
a GTPV2 message to ask whether the target MME sets an indirect forwarding tunnel.
In direct forwarding mode, UE data is directly forwarded between the source eNodeB
and target eNodeB.
 ISNAPTRMOD: indicates whether an MME is allowed to query naming authority
pointer resource records (NAPTRs). Enable the function for querying NAPTR before
setting the PGW shielding duration and topology. An MME generates a fully qualified
domain name (FQDN) using a TAI and queries the NAPTR list based on the FQDN to
obtain the host name list of the PGW in the attach or handover procedure. You can
select the latest SGW and PGW based on the host name suffix to shorten the signaling
delay. For example, you have obtained three host names:
topon.s5.pgw1.california.west.example.com,
topon.s11.sgw.california.west.example.com, and
topon.s5.pgw2.oregon.west.example.com. The same information between the first two
host names is california.west.example.com and that between the latter two host names
is west.example.com. Longer same information between host names indicates nearer
topology distance between the hosts. In this example, the topology distance between
the first two hosts is nearer than that between the latter two hosts.
 APNRES: If this parameter is disabled, the ESM sends the gateway GPRS support
node (GGSN) the Create PDP Context message carrying no Maximum APN
Restriction information element (IE), and ignores APN Restriction IEs in all messages
sent by the GGSN to the SGSN.
 PDPRMD: Select a deactivation mode for PDP deactivation if the APN restriction
function is enabled.
 PDPTYPE: indicates the PDP/PDN type. If dual-stack contexts are not allowed, select
the single-stack PDP type first.

 The GGSN/PGW provides an APN restriction value for each APN. This value
indicates whether the UE can create the PDP contexts of other APNs.
 The SGSN/MME maintains and stores the maximum APN restriction value among all
activated PDP contexts of a UE.




Owb091500 (Slide) Usn9810 v900r015c10 (Mme) Data Configuration Issue1.01

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Owb091500 (Slide) Usn9810 v900r015c10 (Mme) Data Configuration Issue1.01

Uploaded by

Copyright:

Available Formats

USN9810 MME Data Configuration

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 SCTP: is a reliable datagram transmission protocol based on a protocol (such as the

Confidential Information of Huawei. No Spreading Without Permission

 S1 interface management: establishes and resets a connection between S1

Confidential Information of Huawei. No Spreading Without Permission

 SCTP multi-homing: indicates that an SCTP endpoint can provide multiple IP

Confidential Information of Huawei. No Spreading Without Permission

 The networking has the following characteristics:

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 The MML Command – CGP window is used to run hardware-related man-machine

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 The IP addresses of different PFU’s interfaces cannot be on the same network

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 The ADD IPRT command is used to configure a static route to a destination IP

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 This example uses an active and a standby EPU.

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission