Section: 5.3.1 IP address allocation 5.3.1.1 General
Content: The procedures of clause 5.3.1 apply to UEs activating a PDN connection of PDN Type IPv4, IPv6 or IPv4v6. Part of it also applies for PDN Type Non-IP when SGi PtP Tunnelling based on UDP/IP, see clause 4.3.17.8, is used. The procedures of clause 5.3.1 do not apply to UEs activating a PDN connection of PDN Type Ethernet. A UE shall perform the address allocation procedures for at least one IP address (either IPv4 address or IPv6 prefix) after the default bearer activation if no IPv4 address is allocated during the default bearer activation. One of the following ways shall be used to allocate IP addresses for the UE: a) The HPLMN allocates the IP address to the UE when the default bearer is activated (dynamic or static HPLMN address); b) The VPLMN allocates the IP address to the UE when the default bearer is activated (dynamic VPLMN address); or c) The PDN operator or administrator allocates an (dynamic or static) IP address to the UE when the default bearer is activated (External PDN Address Allocation). The IP address allocated for the default bearer shall also be used for the dedicated bearers within the same PDN connection. IP address allocation for PDN connections, which are activated by the UE requested PDN connectivity procedure, is handled with the same set of mechanisms as those used within the Attach procedure. PDN types IPv4, IPv6 and IPv4v6 are supported. An EPS Bearer of PDN type IPv4v6 may be associated with one IPv6 prefix only or with both one IPv4 address and one IPv6 prefix. PDN type IPv4 is associated with an IPv4 address. PDN type IPv6 is associated with an IPv6 prefix. PDN types IPv4 and IPv6 are utilised for the UE and/or the PDN GW support IPv4 addressing only or IPv6 prefix only; or operator preferences dictate the use of a single IP version only, or the subscription is limited to IPv4 only or IPv6 only for this APN. In addition, PDN type IPv4 and IPv6 are utilised for interworking with nodes of earlier releases. The way that the UE sets the requested PDN type may be pre-configured in the device per APN. Unless otherwise configured (including when the UE does not send any APN), the UE sets the PDN type during the Attach or PDN Connectivity procedures based on its IP stack configuration as follows: - A UE which is IPv6 and IPv4 capable shall request for PDN type IPv4v6. - A UE which is only IPv4 capable shall request for PDN type IPv4. - A UE which is only IPv6 capable shall request for PDN type IPv6. - When the IP version capability of the UE is unknown in the UE (as in the case when the MT and TE are separated and the capability of the TE is not known in the MT), the UE shall request for PDN type IPv4v6. NOTE 1: At intersystem changes between GERAN/UTRAN and E-UTRAN there is a 1-to-1 mapping between PDP type IPv4v6 and PDN type IPv4v6 without re-negotiation of the PDP/PDN type used for a PDN connection. The HSS stores one PDN type per APN in the subscription data. During the Attach or UE requested PDN connectivity procedure the MME compares the requested PDN type to the PDN type in the subscription records for the given APN and sets the PDN type as follows: - If the requested PDN type is allowed by subscription, the MME sets the PDN type as requested. - If the requested PDN type is IPv4v6 and subscription data only allows PDN type IPv4 or only allows PDN type IPv6, the MME sets the PDN type according to the subscribed value. A reason cause shall be returned to the UE indicating that only the assigned PDN type is allowed. In this case the UE shall not request another PDN connection to the same APN for the other IP version during the existence of the PDN connection. - If the requested PDN type is IPv4 or IPv6, and either the requested PDN type or PDN type IPv4v6 are subscribed, the MME sets the PDN type as requested. Otherwise the PDN connection request is rejected. - If the requested PDN type is IPv4v6, and both IPv4 and IPv6 PDN types are allowed by subscription but not IPv4v6, the MME shall set the PDN type to IPv4 or IPv6 where the selection between IPv4 and IPv6 is implementation specific. The UE should then initiate the UE requested PDN connectivity procedure to this APN in order to activate a second PDN connection with the other single address PDN type which was not allocated by the network. NOTE 2: If the MT and TE are separated, the UE might not be able to use reason cause "single address bearers only" as a trigger for activating a second single-stack EPS bearer. The PDN GW may restrict the usage of a PDN type IPv4v6 as follows. - If the PDN GW receives a request for PDN type IPv4v6, but the PDN GW operator preferences dictate the use of IPv4 addressing only or IPv6 prefix only for this APN, the PDN type shall be changed to a single address PDN type (IPv4 or IPv6) and a reason cause shall be returned to the UE indicating that only the assigned PDN type is allowed. In this case the UE shall not request another PDN connection to the same APN for the other IP version during the existence of the PDN connection. - If the PDN GW receives a request for PDN type IPv4v6, but the MME does not set the Dual Address Bearer Flag due to the MME operator using single addressing per bearer to support interworking with nodes of earlier releases the PDN type shall be changed to a single IP version only and a reason cause shall be returned to the UE indicating that only single IP version per PDN connection is allowed. In this case the UE should request another PDN connection for the other IP version using the UE requested PDN connectivity procedure to the same APN with a single address PDN type (IPv4 or IPv6) other than the one already activated. During inter-RAT mobility between E-UTRAN and UTRAN/GERAN, an EPS bearer with PDN type IPv4v6 shall be mapped one-to-one to PDP type IPv4v6. During inter-RAT mobility between E-UTRAN and UTRAN/GERAN, an EPS bearer with PDN type IPv4 shall be mapped one-to-one to a PDP context of PDP type IPv4. An EPS bearer with PDN type IPv6 shall be mapped one-to-one to a PDP context of PDP type IPv6. It is the HPLMN operator that shall define in the subscription whether a dynamic HPLMN or VPLMN address may be used. The EPS UE may indicate to the network within the Protocol Configuration Options element that the UE wants to obtain the IPv4 address with DHCPv4, which is a deferred IPv4 address allocation option, or during the default bearer activation procedure. This implies the following behaviour both for static and dynamic address allocation: - the UE may indicate that it prefers to obtain an IPv4 address as part of the default bearer activation procedure. In such a case, the UE relies on the EPS network to provide IPv4 address to the UE as part of the default bearer activation procedure. - the UE may indicate that it prefers to obtain the IPv4 address after the default bearer setup by DHCPv4. That is, when the EPS network supports DHCPv4 and allows that, it does not provide the IPv4 address for the UE as part of the default bearer activation procedures. The network may respond to the UE by setting the PDN Address to 0.0.0.0. After the default bearer establishment procedure is completed, the UE uses the connectivity with the EPS and initiates the IPv4 address allocation on its own using DHCPv4. However, if the EPS network provides IPv4 address to the UE as part of the default bearer activation procedure, the UE should accept the IPv4 address indicated in the default bearer activation procedure. - if the UE sends no Address Allocation Preference, the PDN GW determines whether DHCPv4 is used between the UE and the PDN GW (for the deferred IPv4 address allocation) or not, based on per APN configuration Both EPS network elements and UE shall support the following mechanisms: a. IPv4 address allocation via default bearer activation, if IPv4 is supported. b. /64 IPv6 prefix allocation via IPv6 Stateless Address autoconfiguration according to RFC 4862 [18], if IPv6 is supported; Furthermore, the Protocol Configuration Options may be used during bearer activation to configure parameters which are needed for IP address allocation. Both EPS network elements and UE may support the following mechanisms: a. IPv4 address allocation and IPv4 parameter configuration after the attach procedure via DHCPv4 according to RFC 2131 [19] and RFC 4039 [25]; b. IPv6 parameter configuration via Stateless DHCPv6 according to RFC 8415 [94]. c. Allocation of IPv6 prefixes using DHCPv6 according to RFC 8415 [94]. EPS network elements may support the following mechanism: a. Allocation of a static IPv4 address and/or a static IPv6 prefix based on subscription data in the HSS. If the static IP address/prefix is not stored in the HSS subscription record, it may be configured on a per-user per-APN basis in the DHCP/Radius/Diameter server and the PDN GW retrieves the IP address/prefix for the UE from the DHCP/Radius/Diameter server. In this case, static IP address/prefix is allocated by the same procedures as the dynamic IP address/prefix allocation (i.e. in such cases it is transparent to the PDN GW if the IP address is static or dynamic). If the static IP address/prefix is stored in the HSS subscription record, during the default bearer establishment the PDN GW receives this static IP address/prefix from Serving GW. In this case the PDN GW shall deliver the received address/prefix to the UE. The static IP address/prefix is delivered to the UE in the same way as a dynamic IP address/prefix. Thus it is transparent to the UE whether the PLMN or the external PDN allocates the IP address and whether the IP address is static or dynamic. The following clauses describe how the above listed IP address allocation mechanisms work when GTP based S5/S8 is used. The way of working of the IP address allocation mechanisms for PMIP based S5/S8 can be found in TS 23.402[ Architecture enhancements for non-3GPP accesses ]  [2].The procedures can be used both for PLMN (VPLMN/HPLMN) or external PDN based IP address allocation. In order to support DHCP based IP address configuration, the PDN GW shall act as the DHCP server towards the UE for both HPLMN assigned dynamic and static IP addressing and for VPLMN assigned dynamic IP addressing. When DHCP is used for external PDN assigned addressing and parameter configuration, the PDN GW shall act as the DHCP server towards the UE and it shall act as the DHCP client towards the external DHCP server. The Serving GW does not have any DHCP functionality. It forwards packets, including DHCP packets, between the UE and the PDN GW. IPv6 Stateless Address autoconfiguration specified in RFC 4862 [18] is the basic mechanism to allocate /64 IPv6 prefix to the UE. During default bearer establishment, the PDN GW sends the IPv6 prefix and Interface Identifier to the S-GW, and then the S-GW forwards the IPv6 prefix and Interface Identifier to the MME or to the SGSN. The MME or the SGSN forwards the IPv6 Interface Identifier to the UE. The MME does not forward the IPv6 prefix to the UE. If the UE receives the IPv6 prefix from the SGSN during PDP Context Activation procedure, it shall ignore it.