eHRPD Network Summary
eHRPD Network Components
Evolved Packet Control Function (ePCF)
HRPD Serving Gateway (HSGW)
SAE Network Summary
E-UTRAN EPC Network Components
eNodeB
Mobility Management Entity (MME)
Serving Gateway (S-GW)
PDN Gateway (P-GW)
Product Description
Product Specifications
Licenses
Hardware Requirements
Components
Network Deployment(s)
PDN Gateway Supporting eHRPD to E-UTRAN/EPC Connectivity
Supported Logical Network Interfaces (Reference Points)
S5/S8 Interface
S6b Interface
SGi Interface
Features and Functionality - Base Software
Subscriber Session Management Features
IPv6 Capabilities
Benefit(s)
Description
Native IPv6 and IPv6 transport
IPv6 Connections to Attached Elements
Source IP Address Validation
Benefit(s)
Description
Default & Dedicated EPC Bearers
Benefit(s)
Description
Lawful Intercept
Benefit(s)
Description
Local Break-Out
Benefit(s)
Description
Subscriber Level Trace
Description
Proxy Mobile IPv6 (S2a)
Benefit(s)
Description
Mobile IP Registration Revocation
Description
Session Recovery Support
Benefits
Description
IMPORTANT:
Network Access and Charging Management Features
Enhanced Charging Service (ECS)
Benefits
Description
Mediation and Charging Methods
Content Analysis Support
Benefit
Description
Content Service Steering
IMPORTANT:
IMPORTANT:
Support for Multiple Detail Record Types
Description
Diameter Credit Control Application
Benefit
Description
Accept TCP Connections from DCCA Server
Benefits
Gy Interface Support
Benefits
Description
Online/Offline Charging
Online Charging
Gy/Ro Reference Interface:
Offline Charging
Ga/Gz Reference Interfaces:
Rf Reference Interface:
AAA Server Groups
Benefit(s)
Description
Dynamic Policy Charging Control (Gx Reference Interface)
Benefit(s)
Description
Network Operation Management Functions
Support Interfaces (Reference Points)
S5/S8 GTP (E-UTRAN EPC)
S6b (E-UTRAN EPC)
SGi
S2a (eHRPD)
Multiple PDN Support
Benefit(s)
Description
Congestion Control
Benefit(s)
Description
IP Access Control Lists
Benefit(s)
Description
System Management Features
Management System Overview
Benefits
Description
IMPORTANT:
IMPORTANT:
Bulk Statistics Support
Benefits
Description
IMPORTANT:
Threshold Crossing Alerts (TCA) Support
Benefits
Description
ANSI T1.276 Compliance
Benefits
Description
Features and Functionality - Inline Service Support
Content Filtering
Integrated Adult Content Filter
Benefit(s)
Description
ICAP Interface
Benefit(s)
Description
Peer-to-Peer Detection
Benefit(s)
Description
Features and Functionality - External Application Support
Web Element Management System
Benefits
Description
Features and Functionality - Optional Enhanced Feature Software
Inter-Chassis Session Recovery (future release)
Benefits
Description
IP Security (IPSec) Encryption
Benefits
Description
Traffic Policing and Shaping
Benefit(s)
Description
Native IPv6 and IPv6 transport
IPv6 Connections to Attached Elements
Traffic Policing
Traffic Shaping
How the PDN Gateway Works
PMIPv6 PDN Gateway Call/Session Procedures in an eHRPD Network
Initial Attach with IPv6/IPv4 Access
Step | Description |
---|---|
1 | The subscriber (UE) attaches to the eHRPD network. |
2a | The eAN/PCF sends an A11 RRQ to the HSGW. The eAN/PCF includes the true IMSI of the UE in the A11 RRQ. |
2b | The HSGW establishes A10s and respond back to the eAN/PCF with an A11 RRP. |
3a | The UE performs LCP negotiation with the HSGW over the established main A10. |
3b | The UE performs EAP over PPP. |
3c | EAP authentication is completed between the UE and the 3GPP AAA. During this transaction, the HSGW receives the subscriber profile from the AAA server. |
4a | After receiving the subscriber profile, the HSGW sends the QoS profile in A11 Session Update Message to the eAN/PCF. |
4b | The eAN/PCF responds with an A11 Session Update Acknowledgement (SUA). |
5a | The UE initiates a PDN connection by sending a PPP-VSNCP-Conf-Req message to the HSGW. The message includes the PDNID of the PDN, APN, PDN-Type=IPv6/[IPv4], PDSN-Address and, optionally, PCO options the UE is expecting from the network. |
5b | The HSGW sends a PBU to the P-GW. |
5c | The P-GW processes the PBU from the HSGW, assigns an HNP for the connection and responds back to the HSGW with PBA. |
5d | The HSGW responds to the VSNCP Conf Req with a VSNCP Conf Ack. |
5e | The HSGW sends a PPP-VSNCP-Conf-Req to the UE to complete PPP VSNCP negotiation. |
5f | The UE completes VSNCP negotiation by returning a PPP-VSNCP-Conf-Ack. |
6 | The UE optionally sends a Router Solicitation (RS) message. |
7 | The HSGW sends a Router Advertisement (RA) message with the assigned Prefix. |
PMIPv6 Lifetime Extension without Handover
Step | Description |
---|---|
1 | The UE is attached to the EPC and has a PDN connection with the P-GW where PDNID=x and an APN with assigned HNP. |
2 | The HSGW MAG service registration lifetime nears expiration and triggers a renewal request for the LMA. |
3 | The MAG service sends a Proxy Binding Update (PBU) to the P-GW LMA service with the following attributes: Lifetime, MNID, APN, ATT=HRPD, HNP. |
4 | The P-GW LMA service updates the Binding Cache Entry (BCE) with the new granted lifetime. |
5 | The P-GW responds with a Proxy Binding Acknowledgement (PBA) with the following attributes: Lifetime, MNID, APN. |
PDN Connection Release Initiated by UE
Step | Description |
---|---|
1 | The UE is attached to the EPC and has a PDN connection with the P-GW for PDN-ID=x and APN with assigned HNP. |
2 | The UE decides to disconnect from the PDN and sends a PPP VSNCP-Term-Req with PDNID=x. |
3 | The HSGW starts disconnecting the PDN connection and sends a PPP-VSNCP-Term-Ack to the UE (also with PDNID=x). |
4 | The HSGW begins the tear down of the PMIP session by sending a PBU Deregistration to the P-GW with the following attributes: Lifetime=0, MNID, APN, ATT=HRPD, HNP. The PBU Deregistration message should contain all the mobility options that were present in the initial PBU that created the binding. |
5 | The P-GW looks up the Binding Cache Entry (BCE) based on the HNP, deletes the binding, and responds to the HSGW with a Deregistration PBA with the same attributes (Lifetime=0, MNID, APN, ATT=HRPD, HNP). |
6 | The HSGW optionally sends a Router Advertisement (RA) with assigned HNP and prefix lifetime=0. |
PDN Connection Release Initiated by HSGW
Step | Description |
---|---|
1 | The UE is attached to the EPC and has a PDN connection with the P-GW for PDN-ID=x and APN with assigned HNP. |
2 | The HSGW MAG service triggers a disconnect of the PDN connection for PDNID=x. |
3 | The HSGW sends a PPP VSNCP-Term-Req with PDNID=x to the UE. |
4 | The UE acknowledges the receipt of the request with a VSNCP-Term-Ack (PDNID=x). |
5 | The HSGW begins the tear down of the PMIP session by sending a PBU Deregistration to the P-GW with the following attributes: Lifetime=0, MNID, APN, HNP. The PBU Deregistration message should contain all the mobility options that were present in the initial PBU that created the binding. |
6 | The P-GW looks up the BCE based on the HNP, deletes the binding, and responds to the HSGW with a Deregistration PBA with the same attributes (Lifetime=0, MNID, APN, ATT=HRPD, HNP). |
7 | The HSGW optionally sends a Router Advertisement (RA) with assigned HNP and prefix lifetime=0. |
PDN Connection Release Initiated by P-GW
Step | Description |
---|---|
1 | The UE is attached to the EPC and has a PDN connection with the P-GW for PDN-ID=x and APN with assigned HNP. |
2 | A PGW trigger causes a disconnect of the PDN connection for PDNID=x and the PGW sends a Binding Revocation Indication (BRI) message to the HSGW with the following attributes: MNID, APN, HNP. |
3 | The HSGW responds to the BRI message with a Binding Revocation Acknowledgement (BRA) message with the sane attributes (MNID, APN, HNP). |
4 | The HSGW MAG service triggers a disconnect of the UE PDN connection for PDNID=x. |
5 | The HSGW sends a PPP VSNCP-Term-Req with PDNID=x to the UE. |
6 | The UE acknowledges the receipt of the request with a VSNCP-Term-Ack (PDNID=x). |
7 | The HSGW optionally sends a Router Advertisement (RA) with assigned HNP and prefix lifetime=0. |
PMIPv6 PDN Gateway Call/Session Procedures in an LTE-SAE Network
GTP PDN Gateway Call/Session Procedures in an LTE-SAE Network
Subscriber-initiated Attach (initial)
Step | Description |
---|---|
1 | The UE initiates the Attach procedure by the transmission of an Attach Request (IMSI or old GUTI, last visited TAI (if available), UE Network Capability, PDN Address Allocation, Protocol Configuration Options, Attach Type) message together with an indication of the Selected Network to the eNodeB. IMSI is included if the UE does not have a valid GUTI available. If the UE has a valid GUTI, it is included. |
2 | The eNodeB derives the MME from the GUTI and from the indicated Selected Network. If that MME is not associated with the eNodeB, the eNodeB selects an MME using an “MME selection function”. The eNodeB forwards the Attach Request message to the new MME contained in a S1-MME control message (Initial UE message) together with the Selected Network and an indication of the E-UTRAN Area identity, a globally unique E-UTRAN ID of the cell from where it received the message to the new MME. |
3 | If the UE is unknown in the MME, the MME sends an Identity Request to the UE to request the IMSI. |
4 | The UE responds with Identity Response (IMSI). |
5 | If no UE context for the UE exists anywhere in the network, authentication is mandatory. Otherwise this step is optional. However, at least integrity checking is started and the ME Identity is retrieved from the UE at Initial Attach. The authentication functions, if performed this step, involves AKA authentication and establishment of a NAS level security association with the UE in order to protect further NAS protocol messages. |
6 | The MME sends an Update Location (MME Identity, IMSI, ME Identity) to the HSS. |
7 | The HSS sends Insert Subscriber Data (IMSI, Subscription Data) message to the MME. The Subscription Data contains the list of all APNs that the UE is permitted to access, an indication about which of those APNs is the Default APN, and the 'EPS subscribed QoS profile' for each permitted APN. |
8 | The MME validates the UE's presence in the (new) TA. If due to regional subscription restrictions or access restrictions the UE is not allowed to attach in the TA, the MME rejects the Attach Request with an appropriate cause, and may return an Insert Subscriber Data Ack message to the HSS. If subscription checking fails for other reasons, the MME rejects the Attach Request with an appropriate cause and returns an Insert Subscriber Data Ack message to the HSS including an error cause. If all checks are successful then the MME constructs a context for the UE and returns an Insert Subscriber Data Ack message to the HSS. The Default APN shall be used for the remainder of this procedure. |
9 | The HSS acknowledges the Update Location message by sending an Update Location Ack to the MME. If the Update Location is rejected by the HSS; the MME rejects the Attach Request from the UE with an appropriate cause. |
10 | The MME selects an S-GW using “Serving GW selection function” and allocates an EPS Bearer Identity for the Default Bearer associated with the UE. If the PDN subscription context contains no P-GW address the MME selects a P-GW as described in clause “PDN GW selection function”. Then it sends a Create Default Bearer Request (IMSI, MME Context ID, APN, RAT type, Default Bearer QoS, PDN Address Allocation, AMBR, EPS Bearer Identity, Protocol Configuration Options, ME Identity, User Location Information) message to the selected S-GW. |
11 | The S-GW creates a new entry in its EPS Bearer table and sends a Create Default Bearer Request (IMSI, APN, S-GW Address for the user plane, S-GW TEID of the user plane, S-GW TEID of the control plane, RAT type, Default Bearer QoS, PDN Address Allocation, AMBR, EPS Bearer Identity, Protocol Configuration Options, ME Identity, User Location Information) message to the P-GW. |
12 | If dynamic PCC is deployed, the P-GW interacts with the PCRF to get the default PCC rules for the UE. The IMSI, UE IP address, User Location Information, RAT type, AMBR are provided to the PCRF by the P-GW if received by the previous message. |
13 | The P-GW returns a Create Default Bearer Response (P-GW Address for the user plane, P-GW TEID of the user plane, P-GW TEID of the control plane, PDN Address Information, EPS Bearer Identity, Protocol Configuration Options) message to the S-GW. PDN Address Information is included if the P-GW allocated a PDN address Based on PDN Address Allocation received in the Create Default Bearer Request. PDN Address Information contains an IPv4 address for IPv4 and/or an IPv6 prefix and an Interface Identifier for IPv6. The P-GW takes into account the UE IP version capability indicated in the PDN Address Allocation and the policies of operator when the P-GW allocates the PDN Address Information. Whether the IP address is negotiated by the UE after completion of the Attach procedure, this is indicated in the Create Default Bearer Response. |
14 | The Downlink (DL) Data can start flowing towards S-GW. The S-GW buffers the data. |
15 | The S-GW returns a Create Default Bearer Response (PDN Address Information, S-GW address for User Plane, S-GW TEID for User Plane, S-GW Context ID, EPS Bearer Identity, Protocol Configuration Options) message to the new MME. PDN Address Information is included if it was provided by the P-GW. |
16 | The new MME sends an Attach Accept (APN, GUTI, PDN Address Information, TAI List, EPS Bearer Identity, Session Management Configuration IE, Protocol Configuration Options) message to the eNodeB. |
17 | The eNodeB sends Radio Bearer Establishment Request including the EPS Radio Bearer Identity to the UE. The Attach Accept message is also sent along to the UE. |
18 | The UE sends the Radio Bearer Establishment Response to the eNodeB. In this message, the Attach Complete message (EPS Bearer Identity) is included. |
19 | The eNodeB forwards the Attach Complete (EPS Bearer Identity) message to the MME. |
20 | The Attach is complete and UE sends data over the default bearer. At this time the UE can send uplink packets towards the eNodeB which are then tunnelled to the S-GW and P-GW. |
21 | The MME sends an Update Bearer Request (eNodeB address, eNodeB TEID) message to the S-GW. |
22 | The S-GW acknowledges by sending Update Bearer Response (EPS Bearer Identity) message to the MME. |
23 | The S-GW sends its buffered downlink packets. |
24 | After the MME receives Update Bearer Response (EPS Bearer Identity) message, if an EPS bearer was established and the subscription data indicates that the user is allowed to perform handover to non-3GPP accesses, and if the MME selected a P-GW that is different from the P-GW address which was indicated by the HSS in the PDN subscription context, the MME sends an Update Location Request including the APN and P-GW address to the HSS for mobility with non-3GPP accesses. |
25 | The HSS stores the APN and P-GW address pair and sends an Update Location Response to the MME. |
26 | Bidirectional data is passed between the UE and PDN. |
Subscriber-initiated Detach
Step | Description |
---|---|
1 | The UE sends NAS message Detach Request (GUTI, Switch Off) to the MME. Switch Off indicates whether detach is due to a switch off situation or not. |
2 | The active EPS Bearers in the S-GW regarding this particular UE are deactivated by the MME sending a Delete Bearer Request (TEID) message to the S-GW. |
3 | The S-GW sends a Delete Bearer Request (TEID) message to the P-GW. |
4 | The P-GW acknowledges with a Delete Bearer Response (TEID) message. |
5 | The P-GW may interact with the PCRF to indicate to the PCRF that EPS Bearer is released if PCRF is applied in the network. |
6 | The S-GW acknowledges with a Delete Bearer Response (TEID) message. |
7 | If Switch Off indicates that the detach is not due to a switch off situation, the MME sends a Detach Accept message to the UE. |
8 | The MME releases the S1-MME signalling connection for the UE by sending an S1 Release command to the eNodeB with Cause = Detach. |
Supported Standards
3GPP References
IETF References