Failure Handling
cnSGW-C supports failure handling for creating or deleting IDFT request procedure.
Following are the failure types that can occur during message processing:
-
Advance validation failure on request and response
-
Retransmissions timeout
-
Transaction SLA
-
Failure reported from peer (UP/PGW/MME), depending on the stage of message processing.
The following table depicts the behavior of cnSGW-C during different failure scenarios in call processing.
Failure Scenario |
SGW-SVC behavior |
Signaling (S11) |
---|---|---|
|
Sends failure or No signaling over Sx. |
Negative Create IDFT response. |
Single PDN
|
Sends failure. Sends Context not found of nonexisting EBI. Clear the PDN if sxCause = Context Not Found. |
Negative Create IDFT response. DBR and DSR over S11 and S5 when sxCause = Context Not Found. |
Multi PDN (Partial Failure)
|
Send Context Not Found for nonexisting PDNs. Send failure in Bearer Context for PDNs for which Sx Modification Request fails. |
Partially Accepted Create IDFT Response. DBR and DSR over S11 and S5 for the PDN for which sxCause = Context Not Found. |
Multi PDN (Complete Failure):
|
Send Context Not Found for nonexisting PDNs. Send failure in Bearer Context for PDNs which has Sx Modification Request fails. |
Negative Create IDFT Response. DBR and DSR over S11 and S5 for the PDN for which sxCause = Context Not Found. |
Delete IDFT Request Advance validation failure. |
Send failure or No signaling over Sx. |
Negative Delete IDFT response. |
|
Ignore Failure. |
Positive Delete IDFT Response. DBR and DSR over S11 and S5 for the PDN for which sxCause = Context Not Found. |