ing to PDCP PDU types could look like. We would map the link-layer address into an EUI-64 address. The Organizationally Unique Identifier (OUI) 'aa:bb:cc' is fictional in our example. Requiring a PGW router to adhere the proposed EUI-64 can be loosened, as the PGW is not required to follow the new PDCP-based EUI-64 scheme. After all, the evolved bearer has no impact on the PGW. The evolved bearer will still be modeled as an isolated per UE link; that is, there can be only one end host attached to the evolved link in addition to routers. Figure 6.3 illustrates Future of IPv6 in 3GPP Networks Table 6.1 PDCP PDU type mapping to a EUI-64 identifier PDU Type EUI-64 Identifier Remarks Existing type for control PDUs. aa:bb:cc:01:00:xx:xx:xx PGW terminated traffic using existing PDU type space. aa:bb:cc:02:00:xx:xx:xx eNodeB terminated traffic, new PDU type value 2. aa:bb:cc:03:00:xx:xx:xx SGW terminated traffic, new PDU type value 3. aa:bb:cc:33:xx:xx:xx:xx Uplink multicast traffic, will reach eNodeB, SGW, and PGW, new PDU type 4. S1-MME Combined gateway 1x RAB Mobile device eNodeB PDU type 1 S1-U bearer 1 S5/S8 bearer LLA_1 PDU type 3 LLA_3 S1-U bearer 2 Prefix C LLA_2 Prefix B Prefix A breakout breakout Any network Any network Figure 6.3 Mapping of PDCP PDU types and different 3GPP bearers within the evolved bearer. how the evolved bearer looks like, and shows the mapping of PDU types, different bearers, and conceptual link-layer addresses. The IPv6 prefix provided via the 'SGW router' or 'eNodeB router' does not provide mobility or any other advanced features such as Policy and Charging Control (PCC) [14] that are typically associated with 3GPP PDN Connections and EPS Bearers; the IPv6 prefix is just for plain simple-IP use. It should be noted that the handling of IPv6 prefixes that are terminated at the eNodeB do not need to be communicated with the Mobile Management Entity (MME) for their evolved bearer handling. The IPv6 prefixes are entirely local to the eNodeB. During handovers or SGW relocations, only the PGW a