| 摘要 |
The application relates to IP address allocation in the context of a user equipment UE connecting to the Evolved Packet Core as standardised by 3GPP, in particular over the S2a interface, where there is a GPRS Tunneling Protocol (GTP) or Proxy Mobile IP (PMIP) tunnel for each PDN connection between the BBF BNG and the 3GPP PGW(s). At the setup of the GTPv2/PMIPv6 tunnel to the PGW, the BNG indicates the PDN type: IPv4-only, IPv6 only, or IPv4v6. The UE is not able or willing to indicate the IP capability it has. Therefore the BNG has to assume either a single IP type PDN connection type (e.g. Pv4ony or Pv6ony) or a dual IP type PDN connection type (i.e. IPv4v6) at tunnel establishment. If there is a mismatch between the UE IP capability and the network assumption, extra resources may be allocated unnecessary. This problem is solved in that the non-3GPP gateway node, e.g. the BNG, sends a message ((b)-(A)) to the 3GPP gateway node, e.g. the PGW, including an indication that the PDN connection is to support the first and a second version of the Internet Protocol, e.g. PDN type “IPv4v6”, with allocation ((C)) initially by the 3GPP gateway node of an IP address for the PDN connection of the first version but not the second version. Following establishment of the PDN connection, when the non-3GPP gateway node receives a second trigger message ((e)) relating to the PDN to trigger allocation of an IP address for the PDN connection of the second version, the non-3GPP gateway node sends a message ((f)-(E)) to the 3GPP gateway node to request the allocation of an IP address for the PDN connection of the second version and, if necessary, the updating of the existing PDN connection. The non-3GPP gateway node receives from the 3GPP gateway node the second version IP address ((H)-(g)) allocated by the 3GPP gateway node for the PDN connection. |
