The following session
interaction scenarios are supported between NEMO and the underlying
PDN connection made over CDMA MIP or eHRPD or LTE access.
The mobile router on
receiving a packet to from the tunnel shall use the GRE key to identify the
tunnel instance. After decap, the packet shall be forwarded towards
the mobile networks, based on the route lookup in the specific VRF
On receiving a packet
from the mobile network, the default-route in the specific VRF context
(associated with that input interface) shall be used and the packet
encap shall get the correct GRE key.
In the following circumstances,
NEMO4G-HA shall withdraw the associated prefix routes from the Enterprise
VRF routing table, update the eBGP neighbors and free up all internal resources
allocated for the underlying PDN connection and NEMO session:
When the eHRPD terminates
the underlying PDN connection (PPP-VSNCP-Term-Req sent to MR and
PMIP-BU with lifetime = 0 sent to HA/PGW/GGSN).
When the MR terminates
the PPP/PDN connection when accessing the network via eHRPD.
After an eUTRAN (LTE)
detach procedure initiated by the MR or MME.
NEMO4G-HA shall not
be able to process any NEMO MIPv4 RRQs if there's no underlying PDN
connection associated to those RRQs (PMIPv6 or GTP). In other words,
NEMO MIPv4 RRQs can be accepted and processed only if an Enterprise
PDN connection has been established with HA/PGW/GGSN
by the mobile router.
NEMO4G-HA shall silently
ignore NEMO MIPv4 RRQs if the underlying PDN connection associated
to each of those RRQs does not have the NEMO permission indication.
This applies to CDMA, eHRPD and LTE access.
NEMO4G-HA shall forward
(not drop) user data using MIP or GRE tunneling (UDP/434
or IP Protocol/47, respectively) to the external enterprise
VRF if such data is not destined to the NEMO4G-HA IP address. This
applies to PDN connections that have or do not have the NEMO Permission
indication. This shall also apply to both eHRPD and LTE access.
Any failure on either
the authentication or authorize of a NEMO MIPv4 session shall not affect
the underlying PDN connection established between the mobile router
and the HA/PGW/GGSN via eHRPD or LTE. For example,
if the security credentials do not match between the MR NEMO client
and NEMO4G-HA, NEMO4G-HA can reject the NEMO MIPv4 RRQ, but the associated
PDN connection shall not be terminated.