Add circle and not locationUnknown response (adafed55) · Commits · EMTEL - Emergency Communications / NG112 Conformance Test Suites

test_purposes/lis.tplan2

+63 −4

Original line number	Diff line number	Diff line
		@@ -38,6 +38,7 @@ Package NG112_LIS {
		}

		// Const {
		// DEVICE_NUMBER: "+331234567890"
		// POINT_POS: "-34.400 134.4000";
		// CIRCLE_POS: "-35.500 135.5000";
		// CIRCLE_RADIUS: "15";
		@@ -74,7 +75,7 @@ Package NG112_LIS {

		PICS Selection PICS_HTTP_POST_REQUEST PICS_LOCATION_HELD
		Initial conditions with {
		the IUT entity havingLocationMappingFor the "deviceNumber" containing
		the IUT entity havingLocationMappingFor the DEVICE_NUMBER containing
		"point" containing
		"position" indicating value POINT_POS
		;
		@@ -93,7 +94,7 @@ Package NG112_LIS {
		version indicating value "1.0",
		element "locationRequest" inNamespace "urn:ietf:params:xml:ns:geopriv:held" containing
		element "device" inNamespace "urn:ietf:params:xml:ns:geopriv:held:id" containing
		element "uri" inNamespace "urn:ietf:params:xml:ns:geopriv:held:id" indicating value "deviceNumber"
		element "uri" inNamespace "urn:ietf:params:xml:ns:geopriv:held:id" indicating value DEVICE_NUMBER
		;
		;
		;
		@@ -147,7 +148,7 @@ Package NG112_LIS {

		PICS Selection PICS_HTTP_POST_REQUEST PICS_LOCATION_HELD
		Initial conditions with {
		the IUT entity havingLocationMappingFor the "deviceNumber" containing
		the IUT entity havingLocationMappingFor the DEVICE_NUMBER containing
		"circle" containing
		"position" indicating value CIRCLE_POS,
		"radius" indicating value CIRCLE_RADIUS
		@@ -167,7 +168,7 @@ Package NG112_LIS {
		version indicating value "1.0",
		element "locationRequest" inNamespace "urn:ietf:params:xml:ns:geopriv:held" containing
		element "device" inNamespace "urn:ietf:params:xml:ns:geopriv:held:id" containing
		element "uri" inNamespace "urn:ietf:params:xml:ns:geopriv:held:id" indicating value "deviceNumber"
		element "uri" inNamespace "urn:ietf:params:xml:ns:geopriv:held:id" indicating value DEVICE_NUMBER
		;
		;
		;
		@@ -208,4 +209,62 @@ Package NG112_LIS {
		}
		}
		}

		Test Purpose {
		TP Id TP_LIS_HTTP_POST_BV_03

		Test objective
		"IUT successfully responds with an error responds when it receives a HTTP POST location request for an unknown device"
		Reference
		"ETSI TS 103 479 Vm.t.e (yyyy-mm) Clause 5.5 Location Information Server (LIS)",
		"Next Generation 112 Long Term Definition http://www.eena.org/uploads/gallery/files/pdf/2013-03-15-eena_ng_longtermdefinitionupdated.pdf Clause 4.10",
		"https://tools.ietf.org/html/rfc5985"

		//Config Id CFG_LIS_01

		PICS Selection PICS_HTTP_POST_REQUEST PICS_LOCATION_HELD
		Initial conditions with {
		the IUT entity havingLocationMappingFor the "deviceNumber" containing
		"circle" containing
		"position" indicating value CIRCLE_POS,
		"radius" indicating value CIRCLE_RADIUS
		;
		;
		}
		Expected behaviour
		ensure that {
		when {
		the IUT entity receives a POST containing
		Uri indicating value "/location",
		Host,
		not Accept,
		Content_type indicating value "application/held+xml;charset=utf-8",
		body containing
		xmlMessage containing
		version indicating value "1.0",
		element "locationRequest" inNamespace "urn:ietf:params:xml:ns:geopriv:held" containing
		element "device" inNamespace "urn:ietf:params:xml:ns:geopriv:held:id" containing
		element "uri" inNamespace "urn:ietf:params:xml:ns:geopriv:held:id" indicating value DEVICE_NUMBER
		;
		;
		;
		;
		;
		}
		then {
		the IUT entity sends a httpResponse containing
		Status_Code indicating value "200 OK",
		version indicating value "1.0",
		Content_type indicating value "application/held+xml;charset=utf-8",
		body containing
		xmlMessage containing
		version indicating value "1.0",
		element "error" inNamespace "urn:ietf:params:xml:ns:geopriv:held" containing
		attribute "code" indicating value "locationUnknown";
		;
		;
		;
		}
		}
		}
		}
		No newline at end of file