Network Mobility (NEMO)
▀ NEMO Overview
▄ Cisco ASR 5x00 Packet Data Network Gateway Administration Guide
204
LTE NEMO Call Flow
The following figure describes the call flow of the NEMOv4 solution.
Figure 18.
NEMOv4 Call Flow
1.
The Cisco MR eHWIC establishes first a connection to the IMS PDN to register to the LTE Network. The
eHWIC's User Id must be properly provisioned on the HSS/SPR to be successfully authenticated.
2.
After the Cisco MR eHWIC registers with the LTE network and establishes a connection to the IMS PDN, then
it connects to the appropriate Enterprise PDN based on the locally configured Enterprise APN.
During the PDN authorization procedure using S6b, the 3GPP AAA assigns a NEMO permission via
AVP. The AVP is also be available as an APN parameter on the E-PGW to allow NEMO service at
the PDN/Enterprise level.
E-PGW assigns the MR eHWIC an IPv4 address from the Enterprise IPv4 pool assigned during PDN
authentication.
E-PGW creates the proper flows internally to forward packets to the corresponding VRF external to the
E-PGW platform using the IPv4 pool configuration on the egress context.
The MR eHWIC passed on the assigned IPv4 address to the NEMO application (also called WAN-IPv4
address).
3.
The MR NEMO application initiates a Mobile IPv4 registration request (RRQ) using the following local
configuration and the IPv4 address assigned to the eHWIC during the Enterprise PDN attach procedure
