BS ISO/IEC 21823-4:2022:2023 Edition
$189.07
Internet of things (IoT). Interoperability for IoT systems – Syntactic interoperability
Published By | Publication Date | Number of Pages |
BSI | 2023 | 48 |
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
4 | Blank Page |
5 | CONTENTS |
7 | FOREWORD |
8 | INTRODUCTION |
9 | 1 Scope 2 Normative references 3 Terms and definitions |
10 | 4 Abbreviated terms 5 Principle for IoT syntactic interoperability 5.1 General 5.2 Principle for IoT syntactic interoperability |
11 | 5.3 Relevant technologies for syntactic interoperability 5.3.1 Metamodel and syntactic interoperability |
12 | 5.3.2 Metamodel-driven approaches supporting interoperability issues 5.4 The overall structure of the proposed approach Figures Figure 1 – The overall structure of the proposed approach |
13 | 5.5 The methodology of metamodel-driven information exchange Figure 2 – Model hierarchies and metamodel-driven information exchange rules |
14 | 5.6 Information exchange rules 5.6.1 Categories of information exchange rules Figure 3 – Categories of information exchange rules |
15 | 5.6.2 Information exchange rules expression 5.6.3 Information exchange rules expression example 6 Requirements on information related to IoT devices 6.1 General Figure 4 – Excerpted information exchange rules for Annex B |
16 | 6.2 General requirements on the translation rules 6.2.1 General 6.2.2 Required intrinsic properties of physical IoT devices (IPIoT) Figure 5 – Classifications of requirements on information related to IoT devices |
17 | 6.2.3 Required extrinsic properties of physical IoT devices (EPIoT) Tables Table 1 – Required intrinsic properties of physical IoT devices |
18 | 6.3 General requirements on the operation rules 6.3.1 Overview of mismatches between IoT systems Table 2 – Required extrinsic properties of physical IoT devices |
19 | Figure 6 – A procedure for mismatch detection and resolution |
20 | 6.3.2 Required properties and syntactic resolutions for potential IoT mismatches Figure 7 – An example of mismatch detection and resolution |
21 | 6.3.3 Details of required properties and syntactic resolutions for potential IoT mismatches Table 3 – Required properties and resolutions for potential IoT mismatches |
22 | Table 4 – Mismatch1: Synchronization mismatch |
23 | Table 5 – Mismatch2: Sampling frequency mismatch |
24 | Table 6 – Mismatch3: Location mismatch |
25 | Table 7 – Mismatch4: Data recording pattern mismatch |
26 | Table 8 – Mismatch5: Precision mismatch |
27 | Table 9 – Mismatch6: Significant figure mismatch |
28 | Table 10 – Mismatch7:Range mismatch |
29 | Table 11 – Mismatch8: Calibration mismatch |
30 | Table 12 – Mismatch9: Response time mismatch |
31 | Table 13 – Mismatch10: Acquisition status mismatch |
32 | Table 14 – Mismatch11: Unit mismatch |
33 | 7 A framework for IoT syntactic interoperability 7.1 General Figure 8 – A framework for processes on developing information exchangerules related to IoT devices from the syntactic viewpoint |
34 | 7.2 A conceptual model for dataset of operation rules (DOR) 7.3 Detailed procedures for a syntactic interoperability framework 7.3.1 Procedure A to prepare the required properties and resolutions Figure 9 – An excerpted conceptual model of DOR (dataset of operation rules) |
35 | 7.3.2 Procedure B to create information exchange rules (DIER) 7.3.3 Procedure C to execute the information exchange rules and check the result Figure 10 – Steps of Procedure A |
36 | Annex A (informative)Properties for physical IoT devices and data A.1 Intrinsic properties of physical IoT devices Table A.1 – Intrinsic properties of physical IoT devices |
38 | A.2 Extrinsic properties of physical IoT devices |
39 | Table A.2 – Extrinsic properties of physical IoT devices |
40 | Annex B (informative)A use case B.1 General B.2 The use case overview: Connected car and vehicle in smart city Figure B.1 – Overall view of use case 1 |
41 | B.3 A scenario of this use case B.3.1 The architecture of this use case B.3.2 Scenario: Data exchange between a connected car and a traffic management system (TMS) Figure B.2 – Architecture of connected car and vehicle in smart city use case Figure B.3 – Information exchange between a car and a TMS |
42 | B.4 Examples used in this use case B.4.1 General |
43 | B.4.2 Illustrated example files and their relationships Figure B.4 – Relationships of example files for this use case |
44 | Annex C (informative)Other metamodel definitions Table C.1 – Definitions of metamodel in various resources |
45 | Bibliography |