From b619dd031299af3db274e12f42e4b19e48fb2843 Mon Sep 17 00:00:00 2001
From: piscione <piscione@etsi.org>
Date: Thu, 16 Nov 2023 15:52:26 +0100
Subject: [PATCH] First version of Test cases for MEC033 v3.1.1 specification.
---
MEC033/MEX/IOTDEV/RegisteredDevices.robot | 226 +++++++++
MEC033/MEX/IOTDEV/environment/variables.txt | 20 +
MEC033/MEX/IOTDEV/jsons/DeviceInfo.json | 6 +
MEC033/MEX/IOTDEV/jsons/DeviceInfoBR.json | 7 +
MEC033/MEX/IOTDEV/jsons/DeviceInfoUpdate.json | 15 +
.../MEX/IOTDEV/jsons/DeviceInfoUpdateBR.json | 16 +
.../MEX/IOTDEV/schemas/DeviceInfo.schema.json | 427 +++++++++++++++++
.../IOTDEV/schemas/DeviceInfoList.schema.json | 430 ++++++++++++++++++
8 files changed, 1147 insertions(+)
create mode 100644 MEC033/MEX/IOTDEV/RegisteredDevices.robot
create mode 100644 MEC033/MEX/IOTDEV/environment/variables.txt
create mode 100644 MEC033/MEX/IOTDEV/jsons/DeviceInfo.json
create mode 100644 MEC033/MEX/IOTDEV/jsons/DeviceInfoBR.json
create mode 100644 MEC033/MEX/IOTDEV/jsons/DeviceInfoUpdate.json
create mode 100644 MEC033/MEX/IOTDEV/jsons/DeviceInfoUpdateBR.json
create mode 100644 MEC033/MEX/IOTDEV/schemas/DeviceInfo.schema.json
create mode 100644 MEC033/MEX/IOTDEV/schemas/DeviceInfoList.schema.json
diff --git a/MEC033/MEX/IOTDEV/RegisteredDevices.robot b/MEC033/MEX/IOTDEV/RegisteredDevices.robot
new file mode 100644
index 0000000..efb9309
--- /dev/null
+++ b/MEC033/MEX/IOTDEV/RegisteredDevices.robot
@@ -0,0 +1,226 @@
+Y''[Documentation] robot --outputdir ../../../outputs ./RegisteredDevices.robot
+... Test Suite to validate the Registered IOT Device (IOTDEV) operations.
+
+*** Settings ***
+Resource environment/variables.txt
+Resource ../../../pics.txt
+Resource ../../../GenericKeywords.robot
+Library REST ${SCHEMA}://${HOST}:${PORT} ssl_verify=false
+Library OperatingSystem
+
+*** Test Cases ***
+TP_MEC_MEC033_IOTS_IOTDEV_001_OK_01
+ [Documentation]
+ ... Check that the IUT responds with the list of registered IoT devices when queried by a Service Consumer
+ ... ETSI GS MEC 033 V3.1.1, clause 7.3.3.1
+ ... https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf
+ Retrieve all registered IOT Device information
+ Check HTTP Response Status Code Is 200
+ Check HTTP Response Body Json Schema Is DeviceInfoList
+ FOR ${element} IN @{response['body']}
+ Log ${element}
+ Should Be Equal As Strings ${element}[imsi] ${EXPECTED_IMSI}
+ Should Be Equal As Strings ${element}[supi] ${EXPECTED_SUPI}
+ Should Be Equal As Strings ${element}[enabled] ${False}
+ END
+
+
+TP_MEC_MEC033_IOTS_IOTDEV_001_OK_02
+ [Documentation]
+ ... "Check that the IUT responds with the list of registered IoT devices when queried using a filter by a Service Consumer
+ ... ETSI GS MEC 033 V3.1.1, clause 7.3.3.1
+ ... https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf
+ Retrieve all registered IOT Device information with filter or query param ${FILTER_ON_ENABLE}
+ Check HTTP Response Status Code Is 200
+ Check HTTP Response Body Json Schema Is DeviceInfoList
+ FOR ${element} IN @{response['body']}
+ Should Be Equal As Strings ${element}[enabled] ${False}
+ END
+
+
+TP_MEC_MEC033_IOTS_IOTDEV_001_OK_03
+ [Documentation]
+ ... "Check that the IUT responds with the list of registered IoT devices when queried by a Service Consumer filtering one field
+ ... ETSI GS MEC 033 V3.1.1, clause 7.3.3.1
+ ... https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf
+ Retrieve all registered IOT Device information with filter or query param ${DEVICE_ID_FIELDS}
+ Check HTTP Response Status Code Is 200
+ Check HTTP Response Body Json Schema Is DeviceInfoList
+
+TP_MEC_MEC033_IOTS_IOTDEV_001_OK_04
+ [Documentation]
+ ... "Check that the IUT responds with the list of registered IoT devices when queried by a Service Consumer filtering one field
+ ... ETSI GS MEC 033 V3.1.1, clause 7.3.3.1
+ ... https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf
+ Retrieve all registered IOT Device information with filter or query param ${FIELDS_AND_FILTER}
+ Check HTTP Response Status Code Is 200
+ Check HTTP Response Body Json Schema Is DeviceInfoList
+
+
+TP_MEC_MEC033_IOTS_IOTDEV_001_OK_02
+ [Documentation]
+ ... Check that the IUT registers the information of an IoT device when requested by a Service Consumer
+ ... ETSI GS MEC 033 V3.1.1, clause 7.3.3.4
+ ... https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf
+ Register IOT Device information DeviceInfo
+ Check HTTP Response Status Code Is 201
+ Check HTTP Response Body Json Schema Is DeviceInfo
+ ${file}= Catenate SEPARATOR= jsons/ DeviceInfo .json
+ ${body}= Get File ${file}
+ ${json}= evaluate json.loads('''${body}''') json
+ Should Be Equal As Strings ${response['body']['deviceId']} ${json}[deviceId]
+ Should Be Equal As Strings ${response['body']['imsi']} ${json}[imsi]
+ Should Be Equal As Strings ${response['body']['supi']} ${json}[supi]
+ Should Be Equal As Strings ${response['body']['enabled']} ${False}
+
+
+
+TP_MEC_MEC033_IOTS_IOTDEV_001_BR_02
+ [Documentation]
+ ... Check that the IUT returns an error when Service Consumer request to register an IoT device with incorrect parameters
+ ... ETSI GS MEC 033 V3.1.1, clause 7.3.3.4
+ ... https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf
+ Register IOT Device information DeviceInfoBR
+ Check HTTP Response Status Code Is 400
+
+
+TP_MEC_MEC033_IOTS_IOTDEV_003_OK
+ [Documentation]
+ ... Check that the IUT returns the IoT device information when requested by Service Consumer specifying the device identifier
+ ... ETSI GS MEC 033 V3.1.1, clause 7.4.3.1
+ ... https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf
+ Retrieve specific registered IOT Device information ${DEVICE_ID}
+ Check HTTP Response Status Code Is 200
+ Check HTTP Response Body Json Schema Is DeviceInfo
+ Should Be Equal As Strings ${response['body']['deviceId']} ${DEVICE_ID}
+
+
+TP_MEC_MEC033_IOTS_IOTDEV_003_NF
+ [Documentation]
+ ... Check that the IUT returns error when Service Consumer request to retrieve a not registered IoT device
+ ... ETSI GS MEC 033 V3.1.1, clause 7.4.3.1
+ ... https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf
+ Retrieve specific registered IOT Device information ${NOT_EXISTING_DEVICE_ID}
+ Check HTTP Response Status Code Is 404
+
+
+TP_MEC_MEC033_IOTS_IOTDEV_004_OK
+ [Documentation]
+ ... Check that the IUT returns an error when Service Consumer request to register an IoT device with incorrect parameters
+ ... ETSI GS MEC 033 V3.1.1, clause 7.4.3.2
+ ... https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf
+ Update IOT Device information ${DEVICE_ID} DeviceInfoUpdate
+ Check HTTP Response Status Code Is 200
+ Check HTTP Response Body Json Schema Is DeviceInfo
+
+TP_MEC_MEC033_IOTS_IOTDEV_004_NF
+ [Documentation]
+ ... Check that the IUT returns an error when a Service Consumer requests to update a not registered IoT device
+ ... ETSI GS MEC 033 V3.1.1, clause 7.4.3.2
+ ... https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf
+ Update IOT Device information ${NOT_EXISTING_DEVICE_ID} DeviceInfoUpdate
+ Check HTTP Response Status Code Is 404
+
+
+TP_MEC_MEC033_IOTS_IOTDEV_004_BR
+ [Documentation]
+ ... Check that the IUT returns an error when a Service Consumer requests to update an existing IoT device with incorrect parameters
+ ... ETSI GS MEC 033 V3.1.1, clause 7.4.3.2
+ ... https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf
+ Update IOT Device information ${NOT_EXISTING_DEVICE_ID} DeviceInfoUpdateBR
+ Check HTTP Response Status Code Is 400
+
+
+TP_MEC_MEC033_IOTS_IOTDEV_005_OK
+ [Documentation]
+ ... Check that the IUT deregisters an IoT device information when requested by a Service Consumer specifying the IoT registered device identifier
+ ... ETSI GS MEC 033 V3.1.1, clause 7.4.3.5
+ ... https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf
+ Deregister IOT Device information ${DEVICE_ID}
+ Check HTTP Response Status Code Is 204
+
+
+TP_MEC_MEC033_IOTS_IOTDEV_005_NF
+ [Documentation]
+ ... "Check that the IUT returns an error when a Service Consumer requests to deregisters an IoT device using incorrect parameters
+ ... ETSI GS MEC 033 V3.1.1, clause 7.4.3.5
+ ... https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf
+ Deregister IOT Device information ${NOT_EXISTING_DEVICE_ID}
+ Check HTTP Response Status Code Is 404
+
+############################################################################
+############################################################################
+############################################################################
+
+*** Keywords ***
+Retrieve all registered IOT Device information
+ Should Be True ${PIC_MEC_PLAT} == 1
+ Should Be True ${PIC_SERVICES} == 1
+ Set Headers {"Accept":"application/json"}
+ Set Headers {"Content-Type":"*/*"}
+ Set Headers {"Authorization":"${TOKEN}"}
+ GET ${apiRoot}/${apiName}/${apiVersion}/registered_devices
+ ${output}= Output response
+ Set Suite Variable ${response} ${output}
+
+Retrieve all registered IOT Device information with filter or query param
+ [Arguments] ${filter_and_query_param}
+ Should Be True ${PIC_MEC_PLAT} == 1
+ Should Be True ${PIC_SERVICES} == 1
+ Set Headers {"Accept":"application/json"}
+ Set Headers {"Content-Type":"*/*"}
+ Set Headers {"Authorization":"${TOKEN}"}
+ GET ${apiRoot}/${apiName}/${apiVersion}/registered_devices?${filter_and_query_param}
+ ${output}= Output response
+ Set Suite Variable ${response} ${output}
+
+Retrieve specific registered IOT Device information
+ [Arguments] ${deviceId}
+ Should Be True ${PIC_MEC_PLAT} == 1
+ Should Be True ${PIC_SERVICES} == 1
+ Set Headers {"Accept":"application/json"}
+ Set Headers {"Content-Type":"*/*"}
+ Set Headers {"Authorization":"${TOKEN}"}
+ GET ${apiRoot}/${apiName}/${apiVersion}/registered_devices/${deviceId}
+ ${output}= Output response
+ Set Suite Variable ${response} ${output}
+
+Register IOT Device information
+ [Arguments] ${content}
+ Should Be True ${PIC_MEC_PLAT} == 1
+ Should Be True ${PIC_SERVICES} == 1
+ Set Headers {"Accept":"application/json"}
+ Set Headers {"Content-Type":"application/json"}
+ Set Headers {"Authorization":"${TOKEN}"}
+ ${file}= Catenate SEPARATOR= jsons/ ${content} .json
+ ${body}= Get File ${file}
+ POST ${apiRoot}/${apiName}/${apiVersion}/registered_devices ${body}
+ ${output}= Output response
+ Set Suite Variable ${response} ${output}
+
+
+Update IOT Device information
+ [Arguments] ${deviceId} ${content}
+ Should Be True ${PIC_MEC_PLAT} == 1
+ Should Be True ${PIC_SERVICES} == 1
+ Set Headers {"Accept":"application/json"}
+ Set Headers {"Content-Type":"application/json"}
+ Set Headers {"Authorization":"${TOKEN}"}
+ ${file}= Catenate SEPARATOR= jsons/ ${content} .json
+ ${body}= Get File ${file}
+ PUT ${apiRoot}/${apiName}/${apiVersion}/registered_devices/${deviceId} ${body}
+ ${output}= Output response
+ Set Suite Variable ${response} ${output}
+
+
+Deregister IOT Device information
+ [Arguments] ${deviceId}
+ Should Be True ${PIC_MEC_PLAT} == 1
+ Should Be True ${PIC_SERVICES} == 1
+ Set Headers {"Accept":"application/json"}
+ Set Headers {"Content-Type":"*/*"}
+ Set Headers {"Authorization":"${TOKEN}"}
+ DELETE ${apiRoot}/${apiName}/${apiVersion}/registered_devices/${deviceId}
+ ${output}= Output response
+ Set Suite Variable ${response} ${output}
+#####
\ No newline at end of file
diff --git a/MEC033/MEX/IOTDEV/environment/variables.txt b/MEC033/MEX/IOTDEV/environment/variables.txt
new file mode 100644
index 0000000..35e88fe
--- /dev/null
+++ b/MEC033/MEX/IOTDEV/environment/variables.txt
@@ -0,0 +1,20 @@
+*** Variables ***
+# Generic variables
+${SCHEMA} http
+${HOST} 127.0.0.1
+${PORT} 8084
+${response} {}
+${TOKEN} asic YWxhZGRpbjpvcGVuc2VzYW1l
+${apiRoot}
+${apiName} amsi
+${apiVersion} v1
+${EXPECTED_IMSI} 310170845466094
+${EXPECTED_SUPI} 310170845466094
+${EXPECTED_ENABLED} false
+
+${FILTER_ON_ENABLE} (eq,enabled,false)
+${DEVICE_ID_FIELDS} fields=deviceId
+
+${FIELDS_AND_FILTER} fields=deviceId&filter=(eq,enabled,false)
+${DEVICE_ID} deviceId
+${NOT_EXISTING_DEVICE_ID} notExistingDeviceId
\ No newline at end of file
diff --git a/MEC033/MEX/IOTDEV/jsons/DeviceInfo.json b/MEC033/MEX/IOTDEV/jsons/DeviceInfo.json
new file mode 100644
index 0000000..842d5e0
--- /dev/null
+++ b/MEC033/MEX/IOTDEV/jsons/DeviceInfo.json
@@ -0,0 +1,6 @@
+{
+ "deviceAuthenticationInfo": "Some custom info",
+ "deviceId": "deviceA",
+ "imsi": "310170845466094",
+ "supi": "310170845466094"
+}
\ No newline at end of file
diff --git a/MEC033/MEX/IOTDEV/jsons/DeviceInfoBR.json b/MEC033/MEX/IOTDEV/jsons/DeviceInfoBR.json
new file mode 100644
index 0000000..fbba9ff
--- /dev/null
+++ b/MEC033/MEX/IOTDEV/jsons/DeviceInfoBR.json
@@ -0,0 +1,7 @@
+{
+ "deviceAuthenticationInfo": "Some custom info",
+ "deviceId": "deviceId",
+ "enabled":"false",
+ "imsi": "310170845466094",
+ "supi": "310170845466094"
+}
\ No newline at end of file
diff --git a/MEC033/MEX/IOTDEV/jsons/DeviceInfoUpdate.json b/MEC033/MEX/IOTDEV/jsons/DeviceInfoUpdate.json
new file mode 100644
index 0000000..385caf3
--- /dev/null
+++ b/MEC033/MEX/IOTDEV/jsons/DeviceInfoUpdate.json
@@ -0,0 +1,15 @@
+{
+ "deviceAuthenticationInfo": "Some custom info",
+ "deviceId": "deviceId",
+ "imsi": "310170845466094",
+ "supi": "310170845466094",
+ "requestedIotPlatformId": "iotPlatform",
+ "TrafficRuleDescriptor": {
+ "trafficRuleId": "trafficRule123",
+ "filterType": "FLOW",
+ "action": "FORWARD_AS_IS",
+ "trafficFilter": {
+ "qCI": 5
+ }
+ }
+}
\ No newline at end of file
diff --git a/MEC033/MEX/IOTDEV/jsons/DeviceInfoUpdateBR.json b/MEC033/MEX/IOTDEV/jsons/DeviceInfoUpdateBR.json
new file mode 100644
index 0000000..aba5992
--- /dev/null
+++ b/MEC033/MEX/IOTDEV/jsons/DeviceInfoUpdateBR.json
@@ -0,0 +1,16 @@
+{
+ "deviceAuthenticationInfo": "Some custom info",
+ "deviceId": "deviceId",
+ "imsi": "310170845466094",
+ "supi": "310170845466094",
+ "enabled":true,
+ "requestedIotPlatformId": "iotPlatform",
+ "TrafficRuleDescriptor": {
+ "trafficRuleId": "trafficRule123",
+ "filterType": "FLOW",
+ "action": "FORWARD_AS_IS",
+ "trafficFilter": {
+ "qCI": 5
+ }
+ }
+}
\ No newline at end of file
diff --git a/MEC033/MEX/IOTDEV/schemas/DeviceInfo.schema.json b/MEC033/MEX/IOTDEV/schemas/DeviceInfo.schema.json
new file mode 100644
index 0000000..3374491
--- /dev/null
+++ b/MEC033/MEX/IOTDEV/schemas/DeviceInfo.schema.json
@@ -0,0 +1,427 @@
+{
+ "type": "object",
+ "properties": {
+ "deviceAuthenticationInfo": {
+ "description": "Information needed for secondary authentication of the IoT device to the data network - see ETSI TS 129 561 [i.4] and ETSI TS 129 061 [i.5] for 5G and LTE procedures, respectively. This attribute is implementation dependent and should be logically linked to the identifiers of the IoT device listed hereafter.",
+ "type": "string"
+ },
+ "deviceMetadata": {
+ "description": "Additional information about the IoT device. This attribute is implementation dependent and may be expressed as an array of keyvalue pairs. ",
+ "type": "array",
+ "items": {
+ "description": "Key-value pairs for device metadata",
+ "type": "object",
+ "properties": {
+ "key": {
+ "type": "string"
+ },
+ "value": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "gpsi": {
+ "description": "GPSI of the IoT device if 5G-enabled (see note 1).",
+ "type": "string"
+ },
+ "pei": {
+ "description": "PEI of the IoT device if 5G-enabled (see note 1).",
+ "type": "string"
+ },
+ "supi": {
+ "description": "SUPI of the IoT device if 5G-enabled (see note 1).",
+ "type": "string"
+ },
+ "msisdn": {
+ "description": "MSISDN of the IoT device if LTE-enabled (see note 1).",
+ "type": "string"
+ },
+ "imei": {
+ "description": "IMEI of the IoT device if LTE-enabled (see note 1).",
+ "type": "string"
+ },
+ "imsi": {
+ "description": "IMSI of the IoT device if LTE-enabled (see note 1).",
+ "type": "string"
+ },
+ "iccid": {
+ "description": "ICCID of the IoT device (see note 1).",
+ "type": "string"
+ },
+ "deviceId": {
+ "description": "Human-readable identifier of the IoT device.",
+ "type": "string"
+ },
+ "requestedMecTrafficRule": {
+ "description": "MEC traffic rules the IoT device is requested to be associated to (see note 2). The data type definition is as per ETSI GS MEC 010-2 [i.6].",
+ "type": "array",
+ "items": {
+ "title": "TrafficRuleDescriptor",
+ "type": "object",
+ "properties": {
+ "trafficRuleId": {
+ "description": "Identifies the traffic rule.",
+ "type": "string"
+ },
+ "filterType": {
+ "type": "string",
+ "description": "Definition of filter type: per FLOW or PACKET\n\nIf it is per FLOW, the filter matches upstream (e.g. UE->EPC) packets and downstream (e.g. EPC->UE) packets are handled by the same context.\n",
+ "enum": [
+ "per FLOW",
+ "per PACKET"
+ ]
+ },
+ "priority": {
+ "description": "Priority of this traffic rule within the range 0 to 255. If traffic rule conflicts, the one with higher priority take precedence. See note 1.",
+ "type": "integer"
+ },
+ "trafficFilter": {
+ "description": "The filter used to identify specific flow/packets that need to be handled by the MEC host.",
+ "type": "array",
+ "items": {
+ "title": "TrafficFilter",
+ "type": "object",
+ "properties": {
+ "srcAddress": {
+ "description": "An IP address or a range of IP addresses.\nFor IPv4, the IP address could be an IP address plus mask, or an individual IP address, or a range of IP addresses.\nFor IPv6, the IP address could be an IP prefix, or a range of IP prefixes.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "dstAddress": {
+ "description": "An IP address or a range of IP addresses.\nFor IPv4, the IP address could be an IP address plus mask, or an individual IP address, or a range of IP addresses.\nFor IPv6, the IP address could be an IP prefix, or a range of IP prefixes.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "srcPort": {
+ "description": "A port or a range of ports.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "dstPort": {
+ "description": "A port or a range of ports.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "protocol": {
+ "description": "Specify the protocol of the traffic filter.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "tag": {
+ "description": "Used for tag based traffic rule.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "uri": {
+ "description": "An URI label, in application layer, i.e. in HTTP message, is used to filter the traffic.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "packetLabel": {
+ "description": "A customized packet label in network layer, as defined by the owner of the MEC platform, is used to filter the traffic.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "srcTunnelAddress": {
+ "description": "Used for GTP tunnel based traffic rule.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "tgtTunnelAddress": {
+ "description": "Used for GTP tunnel based traffic rule.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "srcTunnelPort": {
+ "description": "Used for GTP tunnel based traffic rule.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "dstTunnelPort": {
+ "description": "Used for GTP tunnel based traffic rule.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "qCI": {
+ "description": "Used to match all packets that have the same QCI.",
+ "type": "integer"
+ },
+ "dSCP": {
+ "description": "Used to match all IPv4 packets that have the same DSCP.",
+ "type": "integer"
+ },
+ "tC": {
+ "description": "Used to match all IPv6 packets that have the same TC.",
+ "type": "integer"
+ }
+ }
+ }
+ },
+ "action": {
+ "type": "string",
+ "description": "Identifies the action of the MEC host data plane, when a packet matches the trafficFilter, the example actions include:\nDROP,\nFORWARD_DECAPSULATED,\nFORWARD_ENCAPSULATED,\nPASSTHROUGH,\nDUPLICATE_DECAPSULATED,\nDUPLICATE_ENCAPSULATED ",
+ "enum": [
+ "SEE_DESCRIPTION"
+ ]
+ },
+ "dstInterface": {
+ "description'": "Describes the destination interface information. If the action is FORWARD_DECAPSULATED, FORWARD_ENCAPSULATED or PASSTHROUGH, one value shall be provided. If the action is DUPLICATE_DECAPSULATED or DUPLICATE_ENCAPSULATED, two values shall be provided. See note 2. If the action is DROP, no value shall be provided.",
+ "title": "InterfaceDescriptor",
+ "type": "object",
+ "properties": {
+ "interfaceType": {
+ "type": "string",
+ "description": "Type of interface: TUNNEL, MAC, IP, etc.",
+ "enum": [
+ "TUNNEL",
+ "MAC",
+ "IP"
+ ]
+ },
+ "tunnelInfo": {
+ "description'": "Included only if the destination address type is tunnel.",
+ "title": "TunnelInfo",
+ "type": "object",
+ "properties": {
+ "tunnelType": {
+ "type": "string",
+ "description": "Type of tunnel: GTP-U, GRE, etc.",
+ "enum": [
+ "GTP-U",
+ "GRE"
+ ]
+ },
+ "tunnelDstAddress": {
+ "description": "Destination address of the tunnel.",
+ "type": "string"
+ },
+ "tunnelSrcAddress": {
+ "description": "Source address of the tunnel.",
+ "type": "string"
+ },
+ "tunnelSpecificData": {
+ "description": "Parameters specific to the tunnel.",
+ "type": "string"
+ }
+ },
+ "required": [
+ "tunnelType",
+ "tunnelDstAddress",
+ "tunnelSrcAddress"
+ ]
+ },
+ "srcMACAddress": {
+ "description": "If the interface type is MAC, the source address identifies the MAC address of the interface.",
+ "type": "string"
+ },
+ "dstMACAddress": {
+ "description": "If the interface type is MAC, the destination address identifies the MAC address of the destination. Only used for dstInterface.",
+ "type": "string"
+ },
+ "dstIPAddress": {
+ "description": "If the interface type is IP, the destination address identifies the IP address of the destination. Only used for dstInterface.",
+ "type": "string"
+ }
+ },
+ "required": [
+ "interfaceType"
+ ]
+ }
+ },
+ "required": [
+ "trafficRuleId",
+ "filterType",
+ "priority",
+ "trafficFilter",
+ "action"
+ ],
+ "description": "NOTE 1: Value indicates the priority in descending order, i.e. with 0 as the highest priority and 255 as the lowest\n priority.\nNOTE 2: Some applications (like inline/tap) require two interfaces. The first interface in the case of inline/tap is on the\n client (e.g. UE) side and the second on the core network (e.g. EPC) side. \n"
+ }
+ },
+ "requestedIotPlatformId": {
+ "description": "IoT platform to which the IoT device is requested to be associated to (see note 2).",
+ "type": "string"
+ },
+ "requestedUserTransportId": {
+ "description": "User transport to which the IoT device is requested to be associated to (see note 2).",
+ "type": "string"
+ },
+ "deviceSpecificMessageFormats": {
+ "description": "Format of the messages to be published by the MEC IoTS on the user transport provided by the associated IoT platform in case the MEC IoTS acts on behalf of the IoT device.",
+ "type": "object",
+ "properties": {
+ "eventMsgFormat": {
+ "description'": "Event message format configuration.",
+ "title": "EventMsg",
+ "type": "object",
+ "properties": {
+ "eventTopic": {
+ "description": "Topic where the message containing application-specific information should be published. ",
+ "type": "string"
+ },
+ "selectedSerializer": {
+ "description'": "Type of serializer to be used for the topic as per ETSI GS MEC 011 [i.2].",
+ "type": "string",
+ "description": "The enumeration SerializerType represents types of serializers.",
+ "enum": [
+ "JSON",
+ "XML",
+ "PROTOBUF3"
+ ]
+ },
+ "includeDeviceAddr": {
+ "description": "Indication whether to include the IP address of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeDeviceMetadata": {
+ "description": "Indication whether to include the metadata about the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includePei": {
+ "description": "Indication whether to include the PEI of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeSupi": {
+ "description": "Indication whether to include the SUPI of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeImei": {
+ "description": "Indication whether to include the IMEI of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeImsi": {
+ "description": "Indication whether to include the IMSI of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeIccid": {
+ "description": "Indication whether to include the ICCID of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeDeviceId": {
+ "description": "Indication whether to include the human-readable identified of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "eventTopic",
+ "selectedSerializer"
+ ]
+ },
+ "uplinkMsgFormat": {
+ "description'": "Uplink message format configuration.",
+ "title": "UplinkMsg",
+ "type": "object",
+ "properties": {
+ "uplinkTopic": {
+ "description": "Topic where the message containing the data generated by the IoT device(s) should be published, in order to be consumed by the end IoT application(s).",
+ "type": "string"
+ },
+ "selectedSerializer": {
+ "description'": "Type of serializer to be used for the topic as per ETSI GS MEC 011 [i.2].",
+ "type": "string",
+ "description": "The enumeration SerializerType represents types of serializers.",
+ "enum": [
+ "JSON",
+ "XML",
+ "PROTOBUF3"
+ ]
+ },
+ "includeDevicePort": {
+ "description": "Indication whether to include the UDP port of the remote IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeDeviceAddr": {
+ "description": "Indication whether to include the IP address of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeDeviceMetadata": {
+ "description": "Indication whether to include the metadata about the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includePei": {
+ "description": "Indication whether to include the PEI of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeSupi": {
+ "description": "Indication whether to include the SUPI of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeImei": {
+ "description": "Indication whether to include the IMEI of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeImsi": {
+ "description": "Indication whether to include the IMSI of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeIccid": {
+ "description": "Indication whether to include the ICCID of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeDeviceId": {
+ "description": "Indication whether to include the human-readable identified of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "uplinkTopic",
+ "selectedSerializer"
+ ]
+ }
+ }
+ },
+ "downlinkInfo": {
+ "description": "Downlink communication configuration of the user transport provided by the associated IoT platform in case the MEC IoTS acts on behalf of the IoT device.",
+ "type": "object",
+ "properties": {
+ "downlinkTopic": {
+ "description": "Topic associated to the IoT device. This topic should be used by an end IoT application to send downlink data to the IoT device.",
+ "type": "string"
+ },
+ "devicePort": {
+ "description": "UDP port to be used by the MEC IoTS for the outgoing downlink packets towards the IoT device. In case a default value is used, this attribute is optional.",
+ "type": "integer"
+ }
+ }
+ },
+ "clientCertificate": {
+ "description": "Client-side SSL/TLS certificate to be used by the MEC IoTS to interact with the user transport provided by the associated IoT platform in case the MEC IoTS acts on behalf of the IoT device.",
+ "type": "string"
+ },
+ "enabled": {
+ "description": "Indication whether the IoT device has a valid associated traffic rule (TRUE) or not (FALSE). See note 3.",
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "deviceAuthenticationInfo",
+ "deviceId",
+ "enabled"
+ ],
+ "description": "NOTE 1: At least one attribute among gpsi, pei, supi, msisdn, imei, imsi, and iccid should be provided. Sufficient security\n measures shall be put in place when any attribute among PEI, SUPI, IMEI, and IMSI is disclosed over the API.\nNOTE 2: Until a valid traffic rule is not provided, the device will not be able to use the IoTS. A valid traffic rule is provided\n by one of the following options:\n • the requestedMecTrafficRule attribute;\n • the requestedIotPlatformId attribute when the IoT platform offers only one user transport;\n • the combination of requestedIotPlatformId and requestedUserTransportId.\nNOTE 3: Enabled is a pseudo-attribute which needs to be maintained by the IoTS based on the presence or not of a valid\n traffic rule associated to the device. It cannot be set directly by the service consumer. \n"
+}
\ No newline at end of file
diff --git a/MEC033/MEX/IOTDEV/schemas/DeviceInfoList.schema.json b/MEC033/MEX/IOTDEV/schemas/DeviceInfoList.schema.json
new file mode 100644
index 0000000..4ee52dc
--- /dev/null
+++ b/MEC033/MEX/IOTDEV/schemas/DeviceInfoList.schema.json
@@ -0,0 +1,430 @@
+{
+ "type": "array",
+ "items": {
+ "type": "object",
+ "properties": {
+ "deviceAuthenticationInfo": {
+ "description": "Information needed for secondary authentication of the IoT device to the data network - see ETSI TS 129 561 [i.4] and ETSI TS 129 061 [i.5] for 5G and LTE procedures, respectively. This attribute is implementation dependent and should be logically linked to the identifiers of the IoT device listed hereafter.",
+ "type": "string"
+ },
+ "deviceMetadata": {
+ "description": "Additional information about the IoT device. This attribute is implementation dependent and may be expressed as an array of keyvalue pairs. ",
+ "type": "array",
+ "items": {
+ "description": "Key-value pairs for device metadata",
+ "type": "object",
+ "properties": {
+ "key": {
+ "type": "string"
+ },
+ "value": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "gpsi": {
+ "description": "GPSI of the IoT device if 5G-enabled (see note 1).",
+ "type": "string"
+ },
+ "pei": {
+ "description": "PEI of the IoT device if 5G-enabled (see note 1).",
+ "type": "string"
+ },
+ "supi": {
+ "description": "SUPI of the IoT device if 5G-enabled (see note 1).",
+ "type": "string"
+ },
+ "msisdn": {
+ "description": "MSISDN of the IoT device if LTE-enabled (see note 1).",
+ "type": "string"
+ },
+ "imei": {
+ "description": "IMEI of the IoT device if LTE-enabled (see note 1).",
+ "type": "string"
+ },
+ "imsi": {
+ "description": "IMSI of the IoT device if LTE-enabled (see note 1).",
+ "type": "string"
+ },
+ "iccid": {
+ "description": "ICCID of the IoT device (see note 1).",
+ "type": "string"
+ },
+ "deviceId": {
+ "description": "Human-readable identifier of the IoT device.",
+ "type": "string"
+ },
+ "requestedMecTrafficRule": {
+ "description": "MEC traffic rules the IoT device is requested to be associated to (see note 2). The data type definition is as per ETSI GS MEC 010-2 [i.6].",
+ "type": "array",
+ "items": {
+ "title": "TrafficRuleDescriptor",
+ "type": "object",
+ "properties": {
+ "trafficRuleId": {
+ "description": "Identifies the traffic rule.",
+ "type": "string"
+ },
+ "filterType": {
+ "type": "string",
+ "description": "Definition of filter type: per FLOW or PACKET\n\nIf it is per FLOW, the filter matches upstream (e.g. UE->EPC) packets and downstream (e.g. EPC->UE) packets are handled by the same context.\n",
+ "enum": [
+ "per FLOW",
+ "per PACKET"
+ ]
+ },
+ "priority": {
+ "description": "Priority of this traffic rule within the range 0 to 255. If traffic rule conflicts, the one with higher priority take precedence. See note 1.",
+ "type": "integer"
+ },
+ "trafficFilter": {
+ "description": "The filter used to identify specific flow/packets that need to be handled by the MEC host.",
+ "type": "array",
+ "items": {
+ "title": "TrafficFilter",
+ "type": "object",
+ "properties": {
+ "srcAddress": {
+ "description": "An IP address or a range of IP addresses.\nFor IPv4, the IP address could be an IP address plus mask, or an individual IP address, or a range of IP addresses.\nFor IPv6, the IP address could be an IP prefix, or a range of IP prefixes.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "dstAddress": {
+ "description": "An IP address or a range of IP addresses.\nFor IPv4, the IP address could be an IP address plus mask, or an individual IP address, or a range of IP addresses.\nFor IPv6, the IP address could be an IP prefix, or a range of IP prefixes.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "srcPort": {
+ "description": "A port or a range of ports.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "dstPort": {
+ "description": "A port or a range of ports.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "protocol": {
+ "description": "Specify the protocol of the traffic filter.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "tag": {
+ "description": "Used for tag based traffic rule.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "uri": {
+ "description": "An URI label, in application layer, i.e. in HTTP message, is used to filter the traffic.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "packetLabel": {
+ "description": "A customized packet label in network layer, as defined by the owner of the MEC platform, is used to filter the traffic.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "srcTunnelAddress": {
+ "description": "Used for GTP tunnel based traffic rule.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "tgtTunnelAddress": {
+ "description": "Used for GTP tunnel based traffic rule.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "srcTunnelPort": {
+ "description": "Used for GTP tunnel based traffic rule.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "dstTunnelPort": {
+ "description": "Used for GTP tunnel based traffic rule.",
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ },
+ "qCI": {
+ "description": "Used to match all packets that have the same QCI.",
+ "type": "integer"
+ },
+ "dSCP": {
+ "description": "Used to match all IPv4 packets that have the same DSCP.",
+ "type": "integer"
+ },
+ "tC": {
+ "description": "Used to match all IPv6 packets that have the same TC.",
+ "type": "integer"
+ }
+ }
+ }
+ },
+ "action": {
+ "type": "string",
+ "description": "Identifies the action of the MEC host data plane, when a packet matches the trafficFilter, the example actions include:\nDROP,\nFORWARD_DECAPSULATED,\nFORWARD_ENCAPSULATED,\nPASSTHROUGH,\nDUPLICATE_DECAPSULATED,\nDUPLICATE_ENCAPSULATED ",
+ "enum": [
+ "SEE_DESCRIPTION"
+ ]
+ },
+ "dstInterface": {
+ "description'": "Describes the destination interface information. If the action is FORWARD_DECAPSULATED, FORWARD_ENCAPSULATED or PASSTHROUGH, one value shall be provided. If the action is DUPLICATE_DECAPSULATED or DUPLICATE_ENCAPSULATED, two values shall be provided. See note 2. If the action is DROP, no value shall be provided.",
+ "title": "InterfaceDescriptor",
+ "type": "object",
+ "properties": {
+ "interfaceType": {
+ "type": "string",
+ "description": "Type of interface: TUNNEL, MAC, IP, etc.",
+ "enum": [
+ "TUNNEL",
+ "MAC",
+ "IP"
+ ]
+ },
+ "tunnelInfo": {
+ "description'": "Included only if the destination address type is tunnel.",
+ "title": "TunnelInfo",
+ "type": "object",
+ "properties": {
+ "tunnelType": {
+ "type": "string",
+ "description": "Type of tunnel: GTP-U, GRE, etc.",
+ "enum": [
+ "GTP-U",
+ "GRE"
+ ]
+ },
+ "tunnelDstAddress": {
+ "description": "Destination address of the tunnel.",
+ "type": "string"
+ },
+ "tunnelSrcAddress": {
+ "description": "Source address of the tunnel.",
+ "type": "string"
+ },
+ "tunnelSpecificData": {
+ "description": "Parameters specific to the tunnel.",
+ "type": "string"
+ }
+ },
+ "required": [
+ "tunnelType",
+ "tunnelDstAddress",
+ "tunnelSrcAddress"
+ ]
+ },
+ "srcMACAddress": {
+ "description": "If the interface type is MAC, the source address identifies the MAC address of the interface.",
+ "type": "string"
+ },
+ "dstMACAddress": {
+ "description": "If the interface type is MAC, the destination address identifies the MAC address of the destination. Only used for dstInterface.",
+ "type": "string"
+ },
+ "dstIPAddress": {
+ "description": "If the interface type is IP, the destination address identifies the IP address of the destination. Only used for dstInterface.",
+ "type": "string"
+ }
+ },
+ "required": [
+ "interfaceType"
+ ]
+ }
+ },
+ "required": [
+ "trafficRuleId",
+ "filterType",
+ "priority",
+ "trafficFilter",
+ "action"
+ ],
+ "description": "NOTE 1: Value indicates the priority in descending order, i.e. with 0 as the highest priority and 255 as the lowest\n priority.\nNOTE 2: Some applications (like inline/tap) require two interfaces. The first interface in the case of inline/tap is on the\n client (e.g. UE) side and the second on the core network (e.g. EPC) side. \n"
+ }
+ },
+ "requestedIotPlatformId": {
+ "description": "IoT platform to which the IoT device is requested to be associated to (see note 2).",
+ "type": "string"
+ },
+ "requestedUserTransportId": {
+ "description": "User transport to which the IoT device is requested to be associated to (see note 2).",
+ "type": "string"
+ },
+ "deviceSpecificMessageFormats": {
+ "description": "Format of the messages to be published by the MEC IoTS on the user transport provided by the associated IoT platform in case the MEC IoTS acts on behalf of the IoT device.",
+ "type": "object",
+ "properties": {
+ "eventMsgFormat": {
+ "description'": "Event message format configuration.",
+ "title": "EventMsg",
+ "type": "object",
+ "properties": {
+ "eventTopic": {
+ "description": "Topic where the message containing application-specific information should be published. ",
+ "type": "string"
+ },
+ "selectedSerializer": {
+ "description'": "Type of serializer to be used for the topic as per ETSI GS MEC 011 [i.2].",
+ "type": "string",
+ "description": "The enumeration SerializerType represents types of serializers.",
+ "enum": [
+ "JSON",
+ "XML",
+ "PROTOBUF3"
+ ]
+ },
+ "includeDeviceAddr": {
+ "description": "Indication whether to include the IP address of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeDeviceMetadata": {
+ "description": "Indication whether to include the metadata about the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includePei": {
+ "description": "Indication whether to include the PEI of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeSupi": {
+ "description": "Indication whether to include the SUPI of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeImei": {
+ "description": "Indication whether to include the IMEI of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeImsi": {
+ "description": "Indication whether to include the IMSI of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeIccid": {
+ "description": "Indication whether to include the ICCID of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeDeviceId": {
+ "description": "Indication whether to include the human-readable identified of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "eventTopic",
+ "selectedSerializer"
+ ]
+ },
+ "uplinkMsgFormat": {
+ "description'": "Uplink message format configuration.",
+ "title": "UplinkMsg",
+ "type": "object",
+ "properties": {
+ "uplinkTopic": {
+ "description": "Topic where the message containing the data generated by the IoT device(s) should be published, in order to be consumed by the end IoT application(s).",
+ "type": "string"
+ },
+ "selectedSerializer": {
+ "description'": "Type of serializer to be used for the topic as per ETSI GS MEC 011 [i.2].",
+ "type": "string",
+ "description": "The enumeration SerializerType represents types of serializers.",
+ "enum": [
+ "JSON",
+ "XML",
+ "PROTOBUF3"
+ ]
+ },
+ "includeDevicePort": {
+ "description": "Indication whether to include the UDP port of the remote IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeDeviceAddr": {
+ "description": "Indication whether to include the IP address of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeDeviceMetadata": {
+ "description": "Indication whether to include the metadata about the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includePei": {
+ "description": "Indication whether to include the PEI of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeSupi": {
+ "description": "Indication whether to include the SUPI of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeImei": {
+ "description": "Indication whether to include the IMEI of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeImsi": {
+ "description": "Indication whether to include the IMSI of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeIccid": {
+ "description": "Indication whether to include the ICCID of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ },
+ "includeDeviceId": {
+ "description": "Indication whether to include the human-readable identified of the IoT device (TRUE) or not (FALSE).",
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "uplinkTopic",
+ "selectedSerializer"
+ ]
+ }
+ }
+ },
+ "downlinkInfo": {
+ "description": "Downlink communication configuration of the user transport provided by the associated IoT platform in case the MEC IoTS acts on behalf of the IoT device.",
+ "type": "object",
+ "properties": {
+ "downlinkTopic": {
+ "description": "Topic associated to the IoT device. This topic should be used by an end IoT application to send downlink data to the IoT device.",
+ "type": "string"
+ },
+ "devicePort": {
+ "description": "UDP port to be used by the MEC IoTS for the outgoing downlink packets towards the IoT device. In case a default value is used, this attribute is optional.",
+ "type": "integer"
+ }
+ }
+ },
+ "clientCertificate": {
+ "description": "Client-side SSL/TLS certificate to be used by the MEC IoTS to interact with the user transport provided by the associated IoT platform in case the MEC IoTS acts on behalf of the IoT device.",
+ "type": "string"
+ },
+ "enabled": {
+ "description": "Indication whether the IoT device has a valid associated traffic rule (TRUE) or not (FALSE). See note 3.",
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "deviceAuthenticationInfo",
+ "deviceId",
+ "enabled"
+ ],
+ "description": "NOTE 1: At least one attribute among gpsi, pei, supi, msisdn, imei, imsi, and iccid should be provided. Sufficient security\n measures shall be put in place when any attribute among PEI, SUPI, IMEI, and IMSI is disclosed over the API.\nNOTE 2: Until a valid traffic rule is not provided, the device will not be able to use the IoTS. A valid traffic rule is provided\n by one of the following options:\n • the requestedMecTrafficRule attribute;\n • the requestedIotPlatformId attribute when the IoT platform offers only one user transport;\n • the combination of requestedIotPlatformId and requestedUserTransportId.\nNOTE 3: Enabled is a pseudo-attribute which needs to be maintained by the IoTS based on the presence or not of a valid\n traffic rule associated to the device. It cannot be set directly by the service consumer. \n"
+ }
+}
\ No newline at end of file
--
GitLab