fixeria has uploaded this change for review.

View Change

s1gw: test S1GW originated PFCP Heartbeat

Extend the existing TC_pfcp_heartbeat to send a Heartbeat Request
in the opposite direction (S1GW -> UPF) using the REST interface.

Change-Id: I28fb46be037a488e225d20a16b83d0479c6e067d
Related: SYS#7066
---
M s1gw/S1GW_Tests.ttcn
1 file changed, 12 insertions(+), 2 deletions(-)

git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/26/41126/1

diff --git a/s1gw/S1GW_Tests.ttcn b/s1gw/S1GW_Tests.ttcn
index 466e377..862f507 100644
--- a/s1gw/S1GW_Tests.ttcn
+++ b/s1gw/S1GW_Tests.ttcn
@@ -1003,13 +1003,23 @@
 	var integer rts := f_PFCPEM_get_recovery_timestamp();
 	var PDU_PFCP pfcp_pdu;
 
-	/* Tx Heartbeat Request */
+	/* [S1GW <- UPF] Heartbeat Request */
 	PFCP.send(ts_PFCP_Heartbeat_Req(rts));
 
-	/* Expect Heartbeat Response
+	/* [S1GW -> UPF] Heartbeat Response
 	 * TODO: validate the indicated Recovery Time Stamp against
 	 * the one that we received in the PFCP Association Setup. */
 	pfcp_pdu := f_ConnHdlr_pfcp_expect(tr_PFCP_Heartbeat_Resp);
+
+	/* [S1GW -> UPF] Heartbeat Request (triggered via the REST interface)
+	 * [S1GW <- UPF] Heartbeat Response (sent by the PFCP_ConnHdlr) */
+	if (mp_rest_enable) {
+		var OperationResult res := f_REST_PfcpHeartbeat();
+		if (not res.success) {
+			setverdict(fail, "PFCP Heartbeat (S1GW -> UPF) failed");
+		}
+	}
+
 	setverdict(pass);
 }
 testcase TC_pfcp_heartbeat() runs on test_CT {

To view, visit change 41126. To unsubscribe, or for help writing mail filters, visit settings.