Embed Size (px)
Citation preview
Presented by: For:
© ETSI 2019
23.10.2019
ETSI Technical Report 103 537 (STF 547 Task 7)Testing Semantic Interoperability
Michelle Wetterwald ETSI IoT Week 2019
© ETSI 2019 2
Outline
Objective of the study
What should be tested ?
Generic test configurations
Generic testing scenarios
Guidelines for running the test
Conclusion
ETSI IoT Week, 23/10/2019
© ETSI 2019 3
Objective of the study
Enable Plugtests™ preparation on Semantic InteroperabilityIn close cooperation with ETSI CTIWork performed as one of the tasks of STF547
Specific objectivesdefine and prepare the organization of a Plugtests™ event on Semantic Interoperabilitydemonstrate a more practical/industrial use of semantic interoperabilityprepare test configurations and scenarios deliver guidelines for the test organization and reporting
Target readersSystem Designer, System Developer, System DeployerDevice ManufacturerInteroperability test organizer, Interoperability test technical expert
ETSI IoT Week, 23/10/2019
© ETSI 2019 4
What should be tested ?
Different approaches for Semantic InteroperabilitySAREF and its extensions for the different verticalsoneM2M approaches, for example base ontology, FlexContainer resources, Smart Device Template…W3C Web of Things …
Interoperability demonstrates different capabilitiesExchange of meaningful, actionable information Shared understanding of the exchanged informationAgreed expectation for the request and the response to the exchange of information
FeaturesOntology management: acquisition, storage of the ontologies; instantiation mapped to the node data structure; ontology update [but not yet dynamically]Data management: generate a request, understand a request received, understand a gap in the ontology (missing information), generate a response
ETSI IoT Week, 23/10/2019
© ETSI 2019 5
Test configurations
Single IoT platformCFG‐01CFG‐02
Multiple IoT platforms with same ontology
CFG‐03CFG‐04
Multiple IoT platforms using different ontologies
CFG‐05CFG‐06
ETSI IoT Week, 23/10/2019
© ETSI 2018 6
Generic testing scenario ‐1
Scenario A‐1: Sensor data reporting on a single IoT platform using an ontologyPossible instantiation: luminosity sensor + oneM2M platform + SAREF ontology
Testing scenarioPre‐conditions:
The IoT platform in operating status.The IoT device is registered under the IoT platform.
Acquisition, storage and instantiation of the common ontology by the IoT platformUpdate of the common ontology in the IoT platformAbility of the IoT device to generate and send a request to the IoT platform referring to the common ontology (upstream)Ability of the IoT device to receive a response from the IoT platform referring to the common ontology (downstream)
ETSI IoT Week, 23/10/2019
Method to validate the success of the test at each step
© ETSI 2018 7
Generic testing scenario ‐2Scenario B‐1: sensor data reporting between platforms in the same vertical domain using the same ontology
Possible instantiation: Temperature sensor + oneM2M platform + ontology SAREF + smartphone application
Scenario B‐2: command sent by the IoT application
ETSI IoT Week, 23/10/2019
© ETSI 2018 8
Generic testing scenario ‐3Scenario D‐1: Interworking with Semantic‐unaware Systems
Possible instantiation:Platform A is a generic data collection platform, semantic‐unaware, with IoT sensor measuring a pressure value.Platform B is a process monitoring platform in which an entity V is defined, representing the status of a process vessel.Platform B obtains the needed data from Platform A, which is transformed into a data type, semantically characterized and tagged according to ontology Y before being transferred to application V.
ETSI IoT Week, 23/10/2019
Recommendation: data transformation should be considered at the border of the system rather than internally
© ETSI 2018 9
Generic testing scenario ‐4Scenario E‐2: Cross‐Domain Interoperability, Different Ontologies
Possible instantiation:Platform A is a platform enabled with ontology X, with an IoT sensor measuring a pressure value.Platform B is a process monitoring platform, enabled with ontology Y, in which an entity V is defined, representing the status of a process vessel.Platform B obtains the pressure data from Platform A, which is mapped to the corresponding semantic entity according to ontology Y before being transferred to application V.For example: ontology X = W3C SSN ; ontology Y = oneM2M base ontology
ETSI IoT Week, 23/10/2019
Recommendation: interworking between different ontologies should be considered at the border of a system rather than internally to a system
© ETSI 2019 10
Summary of guidelines for running the testChoose with interested stakeholders the objective and purpose of the test among the possible situations described before
Identify the relevant specifications and ontologies to be tested and the corresponding test configurations. Tests can be run:
inside one framework, using specifications from the same origin (for example, like the semantic interoperability that were organized by oneM2M in December 2017), or
across different frameworks and set of specifications (for example, mixing SAREF and SSN implementations), allowing more platforms and implementations to be involved in the test
Describe test configurations
Instantiate test sequences (generic sequences provided in the report) and methods to validate the successful result of the test
Design and set‐up the necessary IT infrastructure, test schedule …
Design and prepare a methodology for test reporting and if necessary, updates of the ontologies and / or mapping
ETSI IoT Week, 23/10/2019
© ETSI 2019 11
SummarySTF 547 has described all the steps needed for testing semantic interoperability
approach to IoT semantic interoperabilityIdentify the objective of the Plugtests™ event, together with the features to be tested Determine the testing configurations and testing scenariosprepare the logistics of the test itself
This methodology is in line with current testing methods used e.g. in oneM2M,
But new methods could be devised to adapt for example to a more dynamic operation of the semantics (see new STF on semantic discovery and query)
TR 103 537 has been published by ETSI SmartM2M and is available at https://www.etsi.org/deliver/etsi_tr/103500_103599/103537/01.01.01_60/tr_103537v010101p.pdf
This study has been contributed to the Semantic Interoperability White Paper: "Semantic IoT Solutions ‐ A Developer Perspective"
ETSI IoT Week, 23/10/2019
© ETSI 2019 12
Thank you for your attention. Questions?
Michelle WetterwaldNETELLANY / FBConsulting
ETSI IoT Week, 23/10/2019
