Overview

Contents
19.9.1 Overview

19.9.1 Overview
Definition

Benefits

Requirements

Impact on the System

Application Limitations

Usage Scenario

Implementation Principle

Charging and CDR

Solution Specifications

Standard Compliance

Release History

Related Topics

Definition

Internet Protocol version 6 (IPv6) is the most recent version of the Internet Protocol (IP). It is used to deal with
the long-lasting problem of IPv4 address exhaustion in the mobile broadband (MBB) field.

The Huawei IPv6 solution provides services to not only IPv4 UEs but also IPv6 and IPv4v6 (dual stack) UEs. To
provide services to IPv6 and IPv4v6 UEs, this solution uses the network elements (NEs) on GPRS/UMTS (GU)
and evolved packet core (EPC) networks to process the attach and activation procedures for these UE types and
transfer IPv6 packets generated on public data networks (PDNs).

Benefits
 For Benefits

Carriers IPv6 provides larger address space than IPv4, which helps address
IPv4 address exhaustion and enables carriers to:

Serve more subscribers.

Decrease the number of network address translation (NAT)

devices and reduce deployment and maintenance costs.

During the evolution from IPv4 to IPv6, IPv4 and IPv6 will coexist
for a long period of time. In the IPv6 solution, NEs support IPv4v6 dual
stack and provide services to IPv4, IPv6, and IPv4v6 UEs, ensuring the
smooth evolution of live networks.

Subscribers -

Requirements

NOTE:

Table 1 and Table 2 provide the earliest supporting versions of Huawei devices. If devices of other vendors are
used, confirm the supporting versions during deployment.
Table 1 NEs involved in implementing the IPv6 solution on GU networks

NE Function Earliest Version Requirement for

Requirement Supporting This the License
Solution

UE Supports IPv6 and - -

IPv4v6 Packet Data
Protocol (PDP)
contexts.

BSC Transparently transmits 13 -

IPv6 packets
(encapsulated in IPv4
packets) of IPv6 and
IPv4v6 subscribers on
GPRS networks.

RNC Transparently transmits 13 -

IPv6 packets
(encapsulated in IPv4
packets) of IPv6 and
IPv4v6 subscribers on
UMTS networks.

HLR Stores the subscription - -

information of IPv6
and IPv4v6 UEs.

AAA server Authenticates - -

IPv6 and IPv4v6
UEs.

Assigns IPv6
addresses to UEs on
live networks.

SGSN Supports IPv6 and SGSN9810 License for the function

IPv4v6 PDP contexts. V800R009C03 control item "IPv6 PDP
Context/Bearer
Table 1 NEs involved in implementing the IPv6 solution on GU networks

NE Function Earliest Version Requirement for

Requirement Supporting This the License
Solution

UE Supports IPv6 and - -

IPv4v6 Packet Data
Protocol (PDP)
contexts.

BSC Transparently transmits 13 -

IPv6 packets
(encapsulated in IPv4
packets) of IPv6 and
IPv4v6 subscribers on
GPRS networks.

Context"

GGSN Supports IPv6 UGW9811 License for controlling

and IPv4v6 PDP V900R009C01 the number of IPv6
contexts. PDP contexts. The
default number of IPv6
Assigns the PDP contexts
IPv6 addresses in configured in the
local address pools license is 10.
to UEs on live
networks.

CG Performs offline CG9812 -

charging on IPv6 and V500R006C01
IPv4v6 UEs.

OCS Performs online - -

charging on IPv6 and
IPv4v6 UEs.
Table 1 NEs involved in implementing the IPv6 solution on GU networks

NE Function Earliest Version Requirement for

Requirement Supporting This the License
Solution

UE Supports IPv6 and - -

IPv4v6 Packet Data
Protocol (PDP)
contexts.

BSC Transparently transmits 13 -

IPv6 packets
(encapsulated in IPv4
packets) of IPv6 and
IPv4v6 subscribers on
GPRS networks.

PCRF Delivers charging and UPCC V300R003C01 -

service control policies
for IPv6 and IPv4v6
UEs.

DNS Records the mappings DNS9816 -

between uniform V100R005C00
resource locators
(URLs) and IPv6
addresses.

Router/LAN Switch Forwards IPv6 packets. - -

The router/LAN Switch
is located between the
GGSN and the IPv6
server.

Table 2 NEs involved in implementing the IPv6 solution on EPC networks

NE Function Earliest Version Requirement for

Table 1 NEs involved in implementing the IPv6 solution on GU networks

NE Function Earliest Version Requirement for

Requirement Supporting This the License
Solution

UE Supports IPv6 and - -

IPv4v6 Packet Data
Protocol (PDP)
contexts.

BSC Transparently transmits 13 -

IPv6 packets
(encapsulated in IPv4
packets) of IPv6 and
IPv4v6 subscribers on
GPRS networks.

Requirement Supporting This the License

Solution

UE Supports IPv6 and - -

IPv4v6 evolved packet
system (EPS) bearers.

eRAN Handles the radio 2.2 -

access of IPv6 and
IPv4v6 UEs to EPC
networks.

MME Supports IPv6 and USN9810 License for the function

IPv4v6 EPS bearers. V900R011C01 control item "IPv6 PDP
Context/Bearer
Context"
Table 1 NEs involved in implementing the IPv6 solution on GU networks

NE Function Earliest Version Requirement for

Requirement Supporting This the License
Solution

UE Supports IPv6 and - -

IPv4v6 Packet Data
Protocol (PDP)
contexts.

BSC Transparently transmits 13 -

IPv6 packets
(encapsulated in IPv4
packets) of IPv6 and
IPv4v6 subscribers on
GPRS networks.

HSS Stores the subscription SAE-HSS -

information of IPv6 V900R006C031
and IPv4v6 UEs.

AAA server Authenticates - -

IPv6 and IPv4v6
UEs.

Assigns IPv6
addresses to UEs on
live networks.

S-GW Supports IPv6 UGW9811 License for controlling

and IPv4v6 EPS V900R009C01 the number of IPv6
bearer contexts. PDP contexts. The
default number of IPv6
P-GW Assigns the PDP contexts
IPv6 addresses in configured in the
local address pools license is 10.
to UEs on live
networks.
Table 1 NEs involved in implementing the IPv6 solution on GU networks

NE Function Earliest Version Requirement for

Requirement Supporting This the License
Solution

UE Supports IPv6 and - -

IPv4v6 Packet Data
Protocol (PDP)
contexts.

BSC Transparently transmits 13 -

IPv6 packets
(encapsulated in IPv4
packets) of IPv6 and
IPv4v6 subscribers on
GPRS networks.

CG Performs offline CG9812 -

charging on IPv6 and V500R006C01
IPv4v6 UEs.

OCS Performs online - -

charging on IPv6 and
IPv4v6 UEs.

PCRF Delivers charging and UPCC V300R003C01 -

service control policies
for IPv6 and IPv4v6
UEs.

DNS Records the mappings DNS9816 -

between URLs and V100R005C00
IPv6 addresses.

Router/LAN Switch Forwards IPv6 packets. - -

The router/LAN Switch
is located between the
 Table 1 NEs involved in implementing the IPv6 solution on GU networks

NE Function Earliest Version Requirement for

Requirement Supporting This the License
Solution

UE Supports IPv6 and - -

IPv4v6 Packet Data
Protocol (PDP)
contexts.

BSC Transparently transmits 13 -

IPv6 packets
(encapsulated in IPv4
packets) of IPv6 and
IPv4v6 subscribers on
GPRS networks.

PDN gateway (P-GW)

and the IPv6 server.

Impact on the System

The packet forwarding performance of a system deployed with the IPv6 solution is 70% of that of a system
deployed with the IPv4 solution.

Application Limitations

There is no limitation on the use of this feature.

Usage Scenario

The IPv6 solution can be deployed on live GU or EPC networks with IPv4 bearers. Figure 1 and Figure 2 show
the recommended networking of the IPv6 solution deployed on a GPRS/UMTS network and on an EPC network
respectively.

Figure 1 Networking of the IPv6 solution deployed on a GPRS/UMTS network

Figure 2 Networking of the IPv6 solution deployed on an EPC network

In Figure 1 and Figure 2, the GGSN and UGW9811 support the IPv4v6 dual stack on interfaces, through which
the GGSN and UGW9811 connect to the PDNs. The GGSN and UGW9811 both forward IPv6 packets directly
to IPv6 networks.

On GPRS/UMTS or EPC networks, the IPv6 solution is deployed in the following models based on the original
and terminal locations of service packets:

IPv4v6 UEs accessing IPv4 and IPv6 services

IPv6 UEs accessing IPv4 services

The IPv6 networks shown in Figure 1 and Figure 2 must have DNS64s and NAT64s deployed.

The GGSN or UGW9811 queries the DNS64 to obtain an IPv6 address based on the URL carried in an IPv6
packet. Then the GGSN or UGW9811 sends the IPv6 packet with the IPv6 address to the NAT64. The
NAT64 then derives an IPv4 address from the IPv6 address and forwards the IPv6 packet to an IPv4 WAP
gateway.
 IPv6 UEs accessing IPv6 services

NOTE:

The current application model in which IPv4 UEs access IPv4 services does not belong to the IPv6 solution. The
application model in which IPv4 UEs access IPv6 services can be implemented only after the IPv6 solution is
mature. These two application models are not described in this document.

Implementation Principle

Table 3 describes the IPv6 support by the UGW9811.

Table 3 IPv6 support

Item IPv6 Support

Physical interfaces The UGW9811 allows for configuration of IPv6 addresses for the
following types of interfaces: GE and Eth-trunk (including
subinterfaces), tunnel, and loopback. A maximum of 10 IPv6 addresses
can be configured for each interface.

Feature GWFD-110401 This feature enables the UGW9811 to activate, deactivate, and update
IPv6 PDP/Bearer the IPv6 PDP context/EPS bearers provided by the IPv4 backbone
Context network.

GWFD-110402 This feature enables the UGW9811 to support networking based on the
IPv6 Networking IPv6 technology on the packet data network (PDN) side. The
on Gi/SGi UGW9811 can connect to a PDN using physical interfaces configured
with IPv6 addresses. In addition, the UGW9811 supports path
maximum transmission unit (PMTU) discovery, IPv6 static routes, and
IPv6 dynamic routing protocols. IPv6 dynamic routing protocols
include the Routing Information Protocol next generation (RIPng),
Open Shortest Path First version 3 (OSPFv3), Intermediate System-to-
Intermediate System (IS-IS) IPv6, and Border Gateway Protocol 4+
(BGP4+).

GWFD-110403 This feature allows the UGW9811 to perform SA for IPv6 subscribers'
IPv6 SA uplink and downlink packets, identify requested IPv6 services and
contents, and perform varied charging and control policies for different
IPv6 services and contents accordingly. IPv6 SA is applicable to the
following services:
Table 3 IPv6 support

Item IPv6 Support

IPv6 content-based charging

IPv6 URL redirection

IPv6 web proxy

IPv6 captive portal

IPv6 P2P traffic control

GWFD-110404 This feature enables the UGW9811 to perform content-based charging

IPv6 Online and non-content-based charging for IPv6 data flows.
Charging

GWFD-110405 This feature enables the UGW9811 to use IPv4 and IPv6 addresses to
IPv4v6 Dual provide UEs with services, including data transmission.
Stack Access

GWFD-110406 This feature allows IPv6 MSs/UEs to function as wireless mobile

IPv6 Prefix routers, which enables family subscribers or small-enterprise
Delegation subscribers to use mobile access services.

GWFD-110407 This feature enables the UGW9811 to allocate IPv6 addresses to both
DHCPv6 Address IPv6 and IPv4v6 subscribers. During the PDP context or EPS bearer
Allocation activation procedure, the UGW9811 functions as a DHCPv6 client to
obtain IPv6 addresses and DNS configurations from the address pool
on an external DHCPv6 server. The UGW9811 then sends the IPv6
addresses and DNS configurations to IPv6 or IPv4v6 subscribers. Note
that the DHCPv6 server may be located on an intranet or
independently maintained by a carrier.
Table 3 IPv6 support

Item IPv6 Support

GWFD-110409 This feature enables the logical interfaces of the UGW9811 to support
IPv6 Networking IPv6-based networking. IPv6 addresses can be configured for
on Logic interfaces connecting to neighboring NEs. These interfaces include Gi,
Interface Gn, S11, S4, S12, S1-U, S2a, S2b, S5, S8, S6b, Ga, Gy, Gxc, and Gx.

Implementation of the IPv6 solution involves the following:

Activating PDP or bearer contexts for IPv6 and IPv4v6 UEs on the GGSN/P-GW on GPRS/UMTS or
EPC Networks

GGSN/P-GW Transmitting IPv6 Packets Generated on PDNs

When IPv6 and IPv4v6 UEs are accessing network services, the UGW9811 can perform the following operations
on these UEs:

Security control

QoS

Service resolution and control

Charging

For details, see the "GWFD-011200 Security", "GWFD-010600 QoS and Traffic Management", "Service
Awareness (SA)", "GWFD-010500 Charging Mode", and "Charging Function" chapters in the UGW9811
product manual.

Activating PDP or bearer contexts for IPv6 and IPv4v6 UEs on the GGSN/P-GW on GPRS/UMTS or EPC
Networks

The activation procedure for IPv6 UEs is slightly different from that for IPv4v6 UEs. The following describes
the activation procedure for IPv4v6 UEs on GPRS/UMTS or EPC networks and lists the differences in the
activation procedure between an IPv6 UE and an IPv4v6 UE.

When an IPv4v6 UE initiates the PDP context activation procedure on a GPRS/UMTS network, one of the
following three situations occurs, depending on the configurations on the SGSN:

One PDP context is created, which contains both an IPv4 address and an IPv6 address.

Two PDP contexts are created, which contain an IPv4 address and an IPv6 address respectively. The
SGSN preferentially sends the GGSN a Create PDP Context Request message for creating a PDP context that
contains an IPv6 address.

Two PDP contexts are created, which contain an IPv4 address and an IPv6 address respectively. The
 SGSN preferentially sends the GGSN a Create PDP Context Request message for creating a PDP context that
contains an IPv4 address.

Figure 3 uses an example to describe the PDP context activation procedure for an IPv4v6 UE on a GPRS/UMTS
network. In this example, one PDP context is created containing both an IPv4 address and an IPv6 address.

Figure 3 Attach and PDP context activation procedure for an IPv4v6 UE on a GPRS/UMTS network

1. The IPv4v6 UE sends an Attach Request message to the SGSN.

The message contains an international mobile subscriber identifier (IMSI) or packet temporary mobile
subscriber identity (P-TMSI). The IMSI will be included if the UE does not have a valid P-TMSI available.
If the UE has a valid P-TMSI, the P-TMSI and the routing area identifier (RAI) associated with the P-TMSI
will be included.

2. The SGSN sends an Authentication Request message to the HLR.

3. If the subscription information of this IPv4v6 UE is available on the HLR, the HLR sends an
Authentication Response message to the SGSN.

4. The SGSN sends an Attach Complete message to the IPv4v6 UE.

5. The IPv4v6 UE sends an Activate PDP Context Request message to the SGSN.

The message contains the APN, PDP Type, Network Service Access Point Identifier (NSAPI), and Protocol
Configuration Option (PCO), where the PDP Type is IPv4v6.

6. The SGSN sends a Create PDP Context Request message to the GGSN.

The message contains the APN, PDP Type, Tunnel Endpoint Identifier (TEID), and PCO, where the PDP
Type is IPv4v6.

7. The GGSN sends a Create PDP Context Response message to the SGSN.
 The message contains the PCO, Cause, IPv4 address assigned to the IPv4v6 UE, IPv6 address prefix,
interface ID, and DNS server IP address.

8. The SGSN sends an Activate PDP Context Accept message to the IPv4v6 UE.

The message contains the PCO, Cause, and Link-local address mapped from the interface ID.

9. The IPv4v6 UE sends a Router Solicitation message to the GGSN, requesting an IPv6 prefix.

10. The GGSN sends a Router Advertisement message to the IPv4v6 UE.

The message contains the same IPv6 prefix as that in 7.

NOTE:

The activation procedure for an IPv6 UE is similar to that for an IPv4v6 UE. The only difference is that IPv6
information is carried in the messages mentioned in steps 5 through 7.

When an IPv4v6 UE initiates an attach procedure on an EPC network, one of the following three situations
occurs, depending on the configuration on the MME:

One default EPS bearer is created, which contains both an IPv4 address and an IPv6 address.

Two default EPS bearers are created, which contain an IPv4 address and an IPv6 address respectively.
The MME preferentially sends the S-GW a Create Session Request message for creating a default EPS bearer
that contains an IPv6 address.

Two default EPS bearers are created, which contain an IPv4 address and an IPv6 address respectively.
The MME preferentially sends the S-GW a Create Session Request message for creating a default EPS bearer
that contains an IPv4 address.

Figure 4 uses an example to describe the attach procedure for an IPv4v6 UE on an EPC network. In this
example, one default EPS bearer is created containing both IPv4 and IPv6 addresses.

Figure 4 Attach procedure for an IPv4v6 UE on an EPC network

1. The IPv4v6 UE sends an Attach Request message to the eNodeB.

The message contains the IMSI or old GUTI, last visited TAI (if available), UE Core Network Capability,
Attach Type, ESM message container (including Request Type, PDN Type, PCO, and Ciphered Options
Transfer Flag IEs).

2. The eNodeB forwards the Attach Request message to the MME.

3. If the subscription information of the IPv4v6 UE is available on the home subscriber server (HSS), the
MME interacts with the IPv4v6 UE and the HSS to perform mutual authentication.

4. The MME sends an Update location Request message to the HSS.

The message contains the MME Identity, IMSI, ME Identity, and MME Capabilities.

5. The HSS sends an Update location Response message to the MME.

6. The MME sends the S-GW a Create Session Request message, where the PDN Type is IPv4v6.

7. The S-GW forwards the P-GW the Create Session Request message, where the PDN Type is IPv4v6.

8. The P-GW sends a Create Session Response message to the S-GW.

The message contains an IPv4 address assigned to the IPv4v6 UE, IPv6 address prefix, interface ID, and
DNS server IP address.
 9. The S-GW forwards the Create Session Response message to the MME.

10. The MME sends an Attach Accept message to the eNodeB.

The message contains the IPv4 address and Link-local address mapped from the interface ID.

11. The eNodeB forwards the Attach Accept message to the IPv4v6 UE.

12. The IPv4v6 UE sends a Router Solicitation message to the P-GW, requesting an IPv6 prefix.

13. The P-GW sends a Router Advertisement message to the IPv4v6 UE.

The message contains the Global Address mapped from a same IPv6 prefix as that in 8.

NOTE:

The activation procedure for an IPv6 UE is similar to that for an IPv4v6 UE. The only difference is that IPv6
information is carried in the messages mentioned in steps 6 through 11.

The IPv6 solution supports the UE handover from a long term evolution (LTE) network to a GPRS/UMTS
network. The handover is classified, based on the UE state, as follows:

Handover

RAU

For details, see the following sections.

Figure 5 shows the signaling procedure for the handover of a UE in connected mode from an LTE network to a
GPRS/UMTS network.

Figure 5 Signaling procedure for the UE handover from an LTE network to a GPRS/UMTS network
1. The source eNodeB sends a Handover Request message to the old MME.

The message contains the following IEs: S1AP Cause, Target RNC Identifier, CSG ID, CSG access mode,
Source eNodeB Identifier, and Source to Target Transparent Container.

2. The old MME converts the EPS bearer context to the UMTS terrestrial radio access network (UTRAN)
mobility management (MM) context and the PDP context, and sends a Forward Relocation Request
message to the new SGSN.

The message contains IMSI, MM Context, PDP context (including the NSAPI and QoS), UE IP address, IP
addresses of the GGSN control plane and user plane, APN, IP address of the SGSN control plane, target
RNC, and RAC.

3. The new SGSN sends a Relocation Request message to the target RNC.

The message contains the IMSI, Cause, authentication encryption algorithm, integrity algorithm, and IP
addresses of the GGSN user plane.

4. The new RNC sends a Relocation Request ACK message to the new SGSN.

The message contains the radio access bearer (RAB) ID, user-plane TEID, GGSN IP address, and integrity
algorithm.

5. The new SGSN sends a Forward Relocation Response message to the old MME.

The message contains the control-plane TEID and the IP address of the new SGSN.
6. The old MME sends a Handover Command message to the source eNodeB.

The message contains the bearer ID, uplink and downlink GTP TEIDs, and the downlink GGSN IP address.

7. The target RNC sends a Relocation Detect message to the new SGSN.

8. The target RNC sends a Relocation Complete message to the new SGSN.

9. The new SGSN sends a Forward Relocation Complete message to the old MME.

The message contains the IP address, port number, and TEID of the GTP tunnel between the old MME and
the new SGSN.

10. The old MME sends a Forward Relocation Complete ACK message to the new SGSN.

The message contains the IP address, port number, and TEID of the GTP tunnel between the old MME and
the new SGSN, and Cause.

11. The new SGSN sends an Update PDP Context Request message to the UGW9811/GGSN.

The message contains the IMSI, the user-plane and control-plane TEIDs, NSAPI, the IP addresses of the
SGSN and GGSN control planes and user planes, QoS, RAT Type, and DT flag.

12. The UGW/GGSN sends an Update PDP Context Response message to the new SGSN.

The message contains the IP addresses and TEIDs of the GGSN control plane and user plane, and QoS.

If a UE in idle mode is handed over from an LTE network to a GPRS/UMTS network, an RAU procedure is
initiated. See Figure 6.

Figure 6 RAU procedure

1. The UE selects a UTRAN cell, the routing area of which is not registered on the network.

2. The UE sends an RAU Request message to the new SGSN.

The message contains the old TMSI, old RAI, old P-TMSI Signature, and Update Type.

3. The new SGSN interacts with the old MME to obtain the SGSN context.

a. The new SGSN sends a Context Request message to the old MME to obtain the MM context
and PDP context for the UE.

The message contains the P-TMSI, old RAI, IP address of the new SGSN, and P-TMSI Signature.

b. The old MME maps the EPS bearer to the PDP context, and the EPS bearer QoS parameters to
pre-Rel-8 QoS parameters. The old MME then returns a Context Response message, which contains
the MM context and PDP context to the new SGSN. At the same time, the old MME starts the timer
for deletion of the bearer at a later stage.
 The message contains the IMSI, ME Identity (if available), and MSISDN.

4. If the PDP context sent by the old MME does not contain security parameters, the operations in security
mode are performed.

5. The new SGSN sends a Context ACK message to the old MME, indicating that the new SGSN has
received the SGSN context.

6. The P-GW updates information about the PDP context.

a. The new SGSN sends an Update PDP Context Request message to the P-GW.

b. The P-GW sends an Update PDP Context Response message to the new SGSN after updating
PDP context related information.

7. The new SGSN sends an Update Location Request message to the HSS.

8. The HSS cancels the location information on the old MME before updating the location information on
the HSS.

a. The HSS sends a Cancel Location Request message to the old MME.

b. The old MME sends a Cancel Location ACK message to the HSS after the location
information on the old MME is canceled.

9. The HSS inserts information about the UE to the new SGSN before updating the location information
on the HSS.

a. The HSS sends an Insert Subscriber Data Request message to the new SGSN.

b. The new SGSN sends an Insert Subscriber Data ACK message to the HSS upon receiving UE
information.

10. After updating location information, the HSS sends an Update Location ACK to the new SGSN.

11. The UE performs the routing area update (RAU) procedure.

a. The new SGSN obtains the SGSN context and subscriber data, updates the location
information, and then sends an RAU Accept message to the UE.

b. The UE returns an RAU Complete message to the new SGSN upon completion of the RAU
procedure.

12. The MME requests to delete the original bearer when the timer set in 3b expires.

a. The old MME sends a Delete Session Request message to the S-GW.

b. The S-GW deletes the original bearer and sends a Delete Session Response message to the old
MME.

c. If the S1 connection on the user plane has been established before the RAU procedure, the old
MME must instruct the eNodeB to release the S1 connection. The eNodeB returns a response message
to the old MME upon releasing the S1 connection.

GGSN/P-GW Transmitting IPv6 Packets Generated on PDNs

Networks for transmitting IPv6 packets between the GGSN/P-GW and the IPv6 server can be deployed based on
any of the networking schemes in Table 4.

Table 4 Networking scheme for a network between a GGSN/P-GW and a PDN

Conditions of Category Networking Scheme Description

Live Networks

The live network (Recommended) (Primary) combination of the The routes between the
has a complex IPv6 networking dual active interface, load- GGSN/UGW9811 and the
topology, with sharing mode, Eth-trunk IPv6 server support
many IPv6- interface, and OSPFv3 forwarding IPv6 packets.
supporting routing
devices deployed.

The live network (Secondary) combination of

has a simple and active/standby interface
stable topology, mode, VRRP, and static
and all the routing
devices on it
support IPv6.

Devices on the (Optional) IPv6 IPv6 over IPv4 GRE tunnel The GRE tunnel is
live network over IPv4 established between the
support only tunneling GGSN/UGW9811 and the
IPv4. IPv6 network for transmitting
encapsulated IPv6 packets.

IPv6 over IPv4 manual The IPv4 network is

tunnel established between the
GGSN/UGW9811 and the
IPv6 network for transmitting
encapsulated IPv6 packets.

6to4 tunnel The 6to4 tunnel is established

between the
GGSN/UGW9811 and the
IPv6 network for transmitting
encapsulated IPv6 packets.
 Table 4 Networking scheme for a network between a GGSN/P-GW and a PDN

Conditions of Category Networking Scheme Description

Live Networks

The live network (Others) IPv6 over MPLS tunnel The MPLS network is
is a multiprotocol 6PE&6vPE established between the
label switching GGSN/UGW9811 and the
(MPLS) network. IPv6 network for transmitting
encapsulated IPv6 packets.

Charging and CDR

The GGSN/P-GW can be deployed together with the CG and OCS to perform online and offline charging on
IPv6 and IPv4v6 UEs. Charging principles for IPv6 and IPv4v6 UEs are the same as those for IPv4 UEs.
However, in the case of quota and call data records (CDRs) for IPv6 and IPv4v6 UEs, the address type is IPv6.

Solution Specifications

No specifications are involved.

Standard Compliance

Category Name

3GPP 3GPP TS 23.060, V9.7.0 "General Packet Radio Service (GPRS) Service
description Stage 2"

3GPP TS 23.401, V9.6.0 "General Packet Radio Service (GPRS)

enhancements for Evolved Universal Terrestrial Radio Access Network (E-
UTRAN) access"

3GPP TS 23975-100 IPv6 Migration Guidelines

3GPP TS 32.215 Charging data description for the Packet Switched (PS)
domain
 Category Name

3GPP TS 32.240 Charging architecture and principles

3GPP TS 32.251 Packet Switched (PS) domain charging

3GPP TS 32.295 Charging Data Record (CDR) transfer

3GPP TS 32.296 Online Charging System (OCS): Applications and interfaces

3GPP TS 32.297 Charging Data Record (CDR) file format and transfer

3GPP TS 32.298 Charging Data Record (CDR) parameter description

3GPP TS 32.299 Diameter charging applications.

3GPP TS 23203 Policy and charging control architecture

3GPP TS 29.212 Policy and Charging Control over Gx reference point

3GPP TS 29.214 Policy and Charging Control over Rx reference point

IETF RFC 2460 Internet Protocol, Version 6 (IPv6) Specification

RFC 1700 Assigned Numbers

RFC 1885 Internet Control Message Protocol (ICMPv6) for the Internet
Category Name

Protocol Version 6 (IPv6)

RFC 2463 Internet Control Message Protocol (ICMPv6) for the Internet
Protocol Version 6 (IPv6) Specification

IETF RFC 4443 Internet Control Message Protocol (ICMPv6) for the Internet
Protocol Version 6 (IPv6) Specification

RFC 3986 Uniform Resource Identifier (URI): Generic Syntax

RFC 4291 IP Version 6 Addressing Architecture

RFC 2673 Binary Labels in the Domain Name System

IETF RFC 1886 DNS Extensions to support IP version 6

RFC 2874 DNS Extensions to Support IPv6 Address Aggregation and

Renumbering

RFC 2916 E.164 number and DNS

RFC 3152 Delegation of IP6.ARPA

RFC 3226 DNSSEC and IPv6 A6 aware server/resolver message size

requirements

RFC 3596 DNS Extensions to Support IP Version 6

Category Name

RFC 1809 Using the Flow Label Field in IPv6

RFC 3595 Textual Conventions for IPv6 Flow Label

RFC 3697 IPv6 Flow Label Specification

RFC 959 FILE TRANSFER PROTOCOL (FTP)

RFC 1639 FTP Operation Over Big Address Records (FOOBAR)

RFC 2428 FTP Extensions for IPv6 and NATs

RFC 1945 Hypertext Transfer Protocol -- HTTP/1.0

RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1

RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1

RFC 1191 Path MTU Discovery

RFC 1981 Path MTU Discovery for IP version 6

RFC 3775 Mobility Support in IPv6

RFC 5095 Deprecation of Type 0 Routing Headers in IPv6

Category Name

IETF draft-hui-6man-rpl-routing-header-02 An IPv6 Routing Header for

Source Routes with RPL

IETF draft-manral-ipv6-rh4-00 New IPv6 Type 4 Routing Header

RFC 783 THE TFTP PROTOCOL (REVISION 2)

RFC 1350 THE TFTP PROTOCOL (REVISION 2)

RFC 3617 Uniform Resource Identifier (URI) Scheme and Applicability

Statement for the Trivial File Transfer Protocol (TFTP)

RFC 3718 Uniform Resource Locators (URL)

RFC 1808 Relative Uniform Resource Locators

RFC 2396 Uniform Resource Identifiers (URI): Generic Syntax

RFC 2732 Format for Literal IPv6 Addresses in URL's

RFC 5952 A Recommendation for IPv6 Address Text Representation

RFC 5954 Essential Correction for IPv6 ABNF and URI Comparison in RFC
3261

RFC 2401 Security Architecture for the Internet Protocol

 Category Name

MICORSOFT Microsoft Media Server (MMS) Protocol Specification

Release History

Feature Version Product Version Details Release Plan

01 BSC 13 This solution is -

released for the first
time.

RNC 13 -

eRAN 2.2 -

SGSN9810 -
V900R010C02

USN9810 -
V900R011C01

UGW9811 -
V900R009C01

SAE-HSS -
V900R006C031

CG9812 -
V500R006C01

UPCC V300R003C01 -
 Feature Version Product Version Details Release Plan

DNS9816 -
V100R005C00

Related Topics

IPv4v6 Dual-Stack UEs Accessing IPv4 and IPv6 Services

IPv6 UEs Accessing IPv4 Services

IPv6 UEs Accessing IPv6 Services

Parent topic: IPv6