MBC Success Handling Call Flow
This section describes the MBC Success Handling call flow.
|
Step |
Description |
|---|---|
|
1 |
The MME sends the Modify Bearer Command to the S11-UDP-Proxy. |
|
2 |
The S11-UDP-Proxy forwards the Modify Bearer Command to the S11-GTP-EP pod. |
|
3 |
The S11-GTP-EP pod sends the ASYNC Modify Bearer Command to the SGW-SVC pod. The SGW-SVC pod forwards the Modify Bearer Command to the PGW. Save MBC_info in PDN for response. |
|
4 |
The S11-GTP-EP pod performs the retransmission. If there is no response, the pod sends the Modify Bearer Command Failure Indication (MBCFI) to the S5-GTP-EP pod. |
|
5 |
The S5-GTP-EP sends the Modify Bearer Command to the S5-UDP-Proxy. |
|
6 |
The S5-UDP-Proxy forwards the Modify Bearer Command to the PGW. |
|
7 |
The PGW sends the Update Bearer Request to the S5-UDP-Proxy. |
|
8 |
The S5-UDP-Proxy sends the Update Bearer Request (src: 2123, dest: 30016) to the S5-GTP-EP. |
|
9 |
The S5-GTP-EP pod sends MBCmd-FailureIndication to SGW-SVC pod to end the transaction. Post internal transaction, the GRPC Update Bearer Request is sent to the SGW-SVC pod. |
|
10 |
The S5-GTP-EP starts the ET2. |
|
11 |
The S5-GTP-EP sends the GRPC Update Bearer Request to SGW-SVC pod. |
|
12 |
The SGW-SVC pod processes the Update Bearer Request and consumes the saved MBC_Info to send Update Bearer Request to the S11-GTP-EP. |
|
13 |
The S11-GTP-EP sends the Update Bearer Request to the S11-UDP-Proxy. |
|
14 |
The S11-UDP-Proxy forwards the Update Bearer Request to the MME. |
|
15 |
The MME sends Update Bearer Response to the SGW-SVC pod. |
|
16 |
The S11-UDP-Proxy processes and sends the Update Bearer Response to the SGW-SVC pod. |
|
17 |
The SGW-SVC pods forward the Update Bearer Response to the S5-GTP-EP pod. |
|
18 |
The S5-GTP-EP pod sends the Update Bearer Response to the S5-UDP-Proxy. |
|
19 |
The S5-UDP-Proxy sends the Update Bearer Response to the PGW. |