IP address allocation in other accesses

The way by which IPv4 addresses and/or IPv6 prefixes are assigned in other
accesses differs depending on what access is used and what mobility protocol
(PMIPv6, MIPv4 or DSMIPv6) is used.
When the terminal attaches from a trusted non-3GPP access and PMIPv6 is
used on the S2a interface, the address allocation is quite similar to how it wor
ks
in 3GPP accesses. An access may, for example, have access specific means to
deliver IPv4 address to the UE, or DHCPv4 may be used. For IPv6, stateless
IPv6 address auto configuration is typically supported. The IP layers are illust
rated
in Figure 6.1.1.4.1.
When the terminal attaches in an untrusted access and PMIPv6 is used on S2b
interface, the terminal receives the IP address from the PDN during the IKEv2based authentication with the ePDG. It can be noted that before IKEv2 is perform
ed
and the IPSec tunnel is setup, an additional IP address is involved. The
reason is that the terminal needs local IP connectivity from the untrusted non3GPP access in order to communicate with the ePDG. This local IP address does,
PDN connection
layer
Application layer Application layer
UE IP connection
Layer 1
Layer 2
IP
Non3GPP
access GW
Transport layer
Layer 1
Router
Layer 2
IP
Layer 1
Layer 2
IP
PDN
GW
UE
PDN
IP IP
Figure 6.1.1.4.1 Schematic view of application, PDN connection and transport lay
ers for
trusted non-3GPP accesses when PMIP is used on S2a.
108 SAE and the Evolved Packet Core: Driving The Mobile Broadband Revolution
however, not come from a PDN but is only used to setup the IPSec tunnel. This is
illustrated in Figure 6.1.1.4.2. For more details, see [Ch 12.1].
From an IP address allocation point of view, the situation is rather similar whe
n