From e90baa384d029bb8da34f467c3d4af776b51eb63 Mon Sep 17 00:00:00 2001 From: Neels Hofmeyr Date: Tue, 11 Oct 2016 02:24:53 +0200 Subject: IuCS: rapidly release connections Do the same as we do in 2G: release the connection as soon as nothing else is pending for a given subscriber. Before, osmo-msc would wait for the UE "to get bored" and send an Iu release. But the CN should stay lean on connections. Also, 25.413[1] in section 7, 6th point states: "While the Iu release is managed from the CN, the RNC has the capability to request the release of all Iu connection resources from the corresponding Iu connection." So far we did not manage Iu release from osmo-msc at all. Use the same mechanism we use in 2G: from msc_release_connection(), just before freeing the gsm_subscriber_conn, invoke a CN initiated Iu Release command to the UE. This works around OS#1816 ("USSD only works when IuCS is released", on nano3G), because the Iu conn is now released right after every signalling, so that typically no two requests will use the same conn. In iu.h/iu.c, add iu_tx_release(), absorbing almost all of the code from ranap_handle_co_iu_rel_req(). Add stub to db_test.c, necessary to build it without linking libiu. [1] 3GPP TS 25.413 v12.4.0 Release 12 / ETSI TS 125 413 V12.4.0 (2015-04) Related: OS#1816 Change-Id: Ic12bd6f3666f6fd42bd6d9fdae1c93abee3b6786 --- openbsc/tests/db/db_test.c | 3 +++ 1 file changed, 3 insertions(+) (limited to 'openbsc/tests/db/db_test.c') diff --git a/openbsc/tests/db/db_test.c b/openbsc/tests/db/db_test.c index bf2e74599..2720b25e1 100644 --- a/openbsc/tests/db/db_test.c +++ b/openbsc/tests/db/db_test.c @@ -276,3 +276,6 @@ const char *mgcpgw_client_remote_addr_str(struct mgcpgw_client *mgcp) { return "0.0.0.0"; } uint32_t mgcpgw_client_remote_addr_n(struct mgcpgw_client *mgcp) { return 0; } +struct RANAP_Cause; +int iu_tx_release(struct ue_conn_ctx *ctx, const struct RANAP_Cause *cause) +{ return 0; } -- cgit v1.2.3