Downlink Data Notification for PGW-initiated procedure with Cloud Native Call Flow

This section describes the DDN for the PGW-initiated procedure with Cloud Native call flow.

Downlink Data Notification for PGW initiated Procedure with Cloud Native Call Flow
Downlink Data Notification for PGW initiated procedure (CBR) with Cloud Native Call Flow Description

Step

Description

1, 2

Enabled trigger-on-pgw-initiated-proc CLI and state of the UE is in IDLE mode.

S5-GTP-EP receives the CBR from the PGW and forwards it to the SGW-service pod.

SGW-service pod starts a new S-T2 transaction.

SGW-service pod sends failure response to the S5-GTP-EP with cause code 110.

3

The T2 transaction which started in step two is completed.

A new S-T3 transaction is started for the UE for which DDN is not triggered.

SGW-service pod initiates the DDN Request to the theS11-GTP-EP.

4

A new E-T4 transaction is started.

S11-GTP-EP forwards the DDN Request to the MME.

5

S11-GTP-EP receives the DDN Response success from the MME.

6

Transaction E-T4 which started in step four is completed.

S11-GTP-EP sends the DDN Response success to the SGW-service pod.

7

Transaction T1 which is started in step three is completed.

SGW-service pod updates the session to CDL.