Inter-MME Handover with Bearer Context Marked for Removal Call Flow
This section describes the Inter-MME Handover with Bearer Context Marked for Removal call flow.

Step |
Description |
---|---|
1, 2 |
Received Modify Bearer request at SGW-Service POD with new MME control F-TEID, bearer-context-1 to be created with EBI:5, eNodeB data TEID, bearer-context-2 to be removed with EBI:6.
|
3, 4 |
Received Sx Modification request from SGW-Service POD to PFCP-EP POD for:
Sx Modification request is forwarded to UP. |
5, 6 |
Received Sx Modification response from UP > PFCP-EP POD. Sx Modification response is received at SGW-Service POD. |
7 |
SGW-Service POD forwards Modify Bearer response to GTPC-EP POD ingress with bearer context to be modified (EBI:5, cause as ACCEPTED) and bearer context to be removed (EBI:6, cause as ACCEPTED). |
8, 9 |
Session updated at CDL. GTPC-EP POD forwards Modify Bearer response to MME. |
10, 11 |
Received delete bearer command at SGW-Service POD with EBI:6. |
12, 13 |
SGW-Service POD forwards delete bearer command to S5 GTPC-EP POD. Delete bearer command received at PGW. |
14, 15 |
Received Delete Bearer request from PGW > S5 GTPC-EP POD. Delete Bearer request received at SGW-Service POD. |
16, 17 |
SGW-Service POD processes Delete Bearer request and forwards it to GTPC-EP POD ingress. |
18, 19 |
Delete Bearer response received at SGW-Service POD and processed. |
20, 21 |
Delete Bearer response received at S5 GTPC-EP POD. Delete Bearer response is received at PGW. |