name: P-GW
full_form: Packet Data Network Gateway
context: In this case, the P-GW provides the UE with an IPv6 Prefix belonging to the Intranet/ISP addressing space. A dynamic IPv6 address is given using stateless address autoconfiguration. This IPv6 address is used for packet forwarding within the packet domain and for packet forwarding on the Intranet/ISP. When a P-GW receives an initial access request (e.g. Create Session Request or Proxy Binding Update) message, the P-GW deduces from local configuration data associated with the APN: - The source of IPv6 Prefixes (P-GW internal prefix pool, or external address allocation server); - Any server(s) to be used for address allocation, authentication and/or protocol configuration options retrieval (e.g. IMS related configuration, see 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ]  [47]); - The protocol, i.e. RADIUS, Diameter or DHCPv6, to be used with the server(s); - The communication and security feature needed to communicate with the server(s); As an example the P-GW may use one of the following options: - P-GW internal Prefix pool for IPv6 prefixes allocation and no authentication; - P-GW internal Prefix pool for IPv6 prefixes allocation and RADIUS for authentication. The AAA server responds with either an Access-Accept or an Access-Reject to the RADIUS client in the P-GW; - RADIUS for authentication and IPv6 prefix allocation. The AAA server responds with either an Access-Accept or an Access-Reject to the RADIUS client in the P-GW; The P-GW includes the PDP Address IE in the the initial access response (e.g. Create Session Response or Proxy Binding Acknowledgement) and return an IPv6 address composed of a Prefix and an Interface-Identifier. The Interface-Identifier may have any value and it does not need to be unique within or across APNs. It shall however not conflict with the Interface-Identifier that the P-GW has selected for its own side of the UE-P-GW link. The Prefix assigned by the P-GW or the external AAA server shall be globally or site-local unique (see the Note in subclause 11.3 of this document regarding the usage of site-local addresses). Table 0.a summarizes the IPv6 prefix allocation and parameter configuration use cases between the UE and the P-GW that may lead the P-GW to interwork with the external RADIUS AAA, Diameter AAA and DHCPv6 servers over Sgi reference point. For detailed description of the signalling flows between the UE and the P-GW, see the references in the table. The detailed description of the signalling use cases that may be triggered between the P-GW and the external servers are specified in this document, as referenced in the table. Table 0.a : IPv6 prefix allocation and parameter configuration use cases
description: The Packet Data Network Gateway (P-GW) is a critical network function within the Evolved Packet Core (EPC) architecture, responsible for providing UE with an IPv6 Prefix belonging to the Intranet/ISP addressing space. It plays a key role in managing packet forwarding within the packet domain and on the Intranet/ISP. The P-GW interacts with external servers such as AAA servers using protocols like RADIUS or Diameter for authentication and IPv6 prefix allocation, ensuring secure and efficient communication.
explanation: P-GW is classified as a Network Function because it serves as an essential component in managing packet data networks, handling tasks such as IPv6 prefix allocation, authentication, and packet forwarding. Its interactions with external servers and its role in providing UE with IPv6 addresses align with the 3GPP's specifications for efficient network operations.
section_title: 11.2.1.3.1a IPv6 EPC based Bearer Activation
biotag_Context: O,O,O,O,B-Network Function,O,O,B-Device,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,B-Organization,B-Specification,O,B-Protocol,O,O,O,O,O,O,B-Protocol,I-Protocol,I-Protocol,O,O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,B-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,B-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Network Function,O,O,B-Protocol,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,O,O,B-Protocol,O,O,B-Service,O,B-Protocol,O,O,B-Interface,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,B-Network,I-Network,I-Network,O,O,O,O,O,B-Device,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Service,O,O,O,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O