Dedicated Bearer with s5u as local-purge/signal-peer Call Flow

This section describes Dedicated Bearer with s5u as local-purge/signal-peer call flow.

Dedicated Bearer with s5u as local-purge/signal-peer Call Flow
Dedicated Bearer with s5u as local-purge/signal-peer Call Flow Description

Step

Description

1, 2

Initial attach complete.

3, 4, 5

GTPU Error detected on UPF.

  • Sx_Session_Report_Request sent to cnSGW-C.

  • cnSGW-C responds with Sx_Session_Report_Response.

6, 7, 8, 9

cnSGW-C processes Session Report Request (ERIR). If TEID is received for dedicated bearer (s5u), submit internal transaction to clean up bearer.

CLI: sgw-profile config

If gtpuErrorInd:

s5u: signal-peer

  • Send Delete Bearer Req to MME.

  • Send Delete Bearer Command to PGW.

10

Send Sx_Session_Modification_Request (Remove Traffic Endpoint) to UPF.

11

UPF responds with Sx_Session_Modification_Response.