laforge has submitted this change. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/41489?usp=email ) Change subject: s1gw: correct handling of UE CONTEXT RELEASE REQUEST ...................................................................... s1gw: correct handling of UE CONTEXT RELEASE REQUEST By sending a UE CONTEXT RELEASE REQUEST, the eNB is requesting the MME to terminate the UE context. This procedure itself does not terminate the UE context nor the associated E-RABs. Therefore, the S1GW should not terminate E-RAB FSMs upon receiving this PDU. This means that we should not be expecting PFCP sesstion(s) to be deleted in S1GW_ConnHdlr.f_ConnHdlr_ue_ctx_release_req(). Change-Id: Ibbb6da1f2888995608b980e7479758000e94864e Related: osmo-s1gw.git If467162e871b7989f0578be30c04d1c32c263c99 Related: SYS#7738, SYS#7599 --- M s1gw/S1GW_ConnHdlr.ttcn 1 file changed, 0 insertions(+), 1 deletion(-) Approvals: laforge: Looks good to me, approved pespin: Looks good to me, approved Jenkins Builder: Verified diff --git a/s1gw/S1GW_ConnHdlr.ttcn b/s1gw/S1GW_ConnHdlr.ttcn index 013d7bf..b850f55 100644 --- a/s1gw/S1GW_ConnHdlr.ttcn +++ b/s1gw/S1GW_ConnHdlr.ttcn @@ -1662,7 +1662,6 @@ log("[eNB -> S1GW] -> MME: UE CONTEXT RELEASE REQUEST"); f_ConnHdlr_tx_s1ap_from_enb(ts_S1AP_UeContextReleaseReq(mme_ue_id, enb_ue_id, cause)); - f_ConnHdlr_session_delete(erabs); log("eNB -> [S1GW -> MME]: UE CONTEXT RELEASE REQUEST"); f_ConnHdlr_rx_s1ap_from_enb(pdu, tr_S1AP_UeContextReleaseReq(mme_ue_id, enb_ue_id, cause)); } -- To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/41489?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: merged Gerrit-Project: osmo-ttcn3-hacks Gerrit-Branch: master Gerrit-Change-Id: Ibbb6da1f2888995608b980e7479758000e94864e Gerrit-Change-Number: 41489 Gerrit-PatchSet: 2 Gerrit-Owner: fixeria <vyanitskiy@sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge@osmocom.org> Gerrit-Reviewer: pespin <pespin@sysmocom.de>