Table of Contents
Advertisement
Network Mobility (NEMO)
(referred to as WAN-IP). The NEMO MIPv4 RRQ will be carried as a regular user packet over the mobility
connection, either GTP in LTE and PPP/PMIPv6 in eHRPD. The NEMO MIPv4 RRQ includes the following
key parameters:
CCOA - IPv4 address assigned to the eHWIC modem during the Enterprise PDN connection setup
MR-HADDR - Mandatory IPv4 address preconfigured in the MR NEMO application. MR-HADDR is
Home Agent Address - Preconfigured IPv4 address that the MR NEMO application uses as the
Explicit LAN Prefixes - Locally attached IPv4 networks preconfigured on the MR NEMO application.
N-MHAE - Mandatory NEMO MN-HA Authentication Extension that includes the SPI and the
NEMO-Tunnel flags such as, but not limited to, "Reverse Tunnel," "Direct Termination," "Tunnel
4. NEMO4G-HA sends a MIP registration response (RRP) back to the MR after it performs the following tasks:
Authenticate the RRQ using the N-MHAE information included in the RRQ.
Authorize the NEMO service based on the NEMO permission attribute assigned to the associated
Accept the prefixes advertised in the Cisco NVSE extension included in the NEMO MIPv4 RRQ.
5. Upon receiving the NEMO MIP RRP, the MR will install a default route (0.0.0.0/0) in its routing table to route
all traffic through the LTE connection.
Outbound packets are encapsulated over GRE using the CCOA/WAN-IP address as the source and the
Inbound packets are encapsulated over GRE as well from the NEMO4G-HA to the MR NEMO
(WAN-IP). The MR NEMO application will use the CCOA/WAN-IP address as the source of all
NEMO packets sent to NEMO4G-HA (control and tunneled user traffic).
normally used as the source of all NEMO control packets sent to the NEMO4G-HA. However, the
MR NEMO application will use the CCOA as the source for all NEMO packets (control and tunneled
user traffic). Therefore, NEMO4G-HA will ignore the preconfigured MR-HADDR included in the
RRQ, but it will still include it in the NEMO MIPv4 RRP.
destination for all NEMO control and GRE tunneled user data (NEMO4G-HA's IPv4 Address).
LAN prefixes will be encoded in the same Cisco NVSE extension currently used in the NEMO
solution for 3G. The Cisco NVSE included in the NEMOv4 MIP RRQ is in the form of a TLV.
authenticator computed using a pre-shared Key. Both SPI and Key are preconfigured in the MR
NEMO application as well.
Encapsulation" = GRE.
Enterprise PDN connection.
The learned prefixes will have to adhere to the current rules of valid pool routes. The minimum
valid mask length is /13 and pool routes can not include 0.0.0.0 or 255.255.255.255.
NEMO4G-HA will accept a minimum of 0 prefixes and a maximum of 8 prefixes. Anything
beyond 8 prefixes will be silently discarded.
NEMO4G-HA will also check that the new resultant enterprise route count (total number of
VRF routes) do not exceed the route limit potentially configured for the given enterprise. If
the preconfigured route limit is exceeded, then NEMO4G-HA will reject the NEMO MIP
RRQ. Otherwise, NEMO4G-HA will install the accepted prefixes in the internal VRF
associated with the Enterprise PDN.
eBGP would then propagate the new NEMO routes to the external VRF as part of the next
BGP update.
NEMO4G-HA-Service IPv4 address as the destination of the tunnel.
application. The source of the GRE tunnel is the NEMO4G-HA-Service IPv4 address and the
destination is the CCOA/WAN-IP address.
Cisco ASR 5x00 Packet Data Network Gateway Administration Guide ▄
NEMO Overview ▀
205
Advertisement
Table of Contents
