2017-01-25 2019-06-09 2017-09-08 2019-06-09 2019-07-21 This work is distributed under a Creative Commons Attribution License (http://creativecommons.org/licenses/by/3.0/). Industrial IoT Architecture Ontology Standards Ontology sto sto_iot https://w3id.org/i40/sto# An ontology to describe standards related to Industry 4.0 and Smart Manufacturing An ontology to describe the landscape of IIoT, Industry 4.0 and Smart Manufacturing The Internet of things (IoT) is the network of devices such as vehicles, and home appliances that contain electronics, software, sensors, actuators, and connectivity which allows these things to connect, interact and exchange data. 0.2 0.3 Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource. 1999-07-02 2008-01-14 An account of the resource. Description A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation. 1999-07-02 2008-01-14 A name given to the resource. Title A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation. Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource. 2008-01-14 2008-01-14 An account of the resource. Description 2000-07-11 2008-01-14 A related resource that is a version, edition, or adaptation of the described resource. Has Version This term is intended to be used with non-literal values as defined in the DCMI Abstract Model (http://dublincore.org/documents/abstract-model/). As of December 2007, the DCMI Usage Board is seeking a way to express this intention with a formal range declaration. 2000-07-11 2008-01-14 Date of formal issuance (e.g., publication) of the resource. Date Issued alternative label definition note preferred label has unit Represents Standards that are component of other Standards. This relation is not transitive is Component Of A relation between collections and entities, e.g. 'the Night Watch by Rembrandt is in the Rijksmuseum collection'; 'Davide is member of the Pen Club', 'Igor is one the subjects chosen for the experiment'. is member of è membro di Standard A has influences in Standard B. For example, IEC_61499 hasInfluenceIn IEC_61804-2(EDDL) https://www.w3.org/TR/prov-o/#wasGeneratedBy was Generated By indicates that some Standard Classification entity has a similar scope as another. This property most probably is symmetric but not transitive. alignes With A Standard Organization that belongs to the country belongs To A relation specifying that a vewpoint regards a Concern. frames Languages in which the document of the Standard is available, e.g., English, French, Spanish Points to Languages in which the standard document is available, e.g., English, French, etc. Defined as subProperty of dcterms:language has Available Language hasAvailableLanguage An Standard is isCategorizedBy a given Categorization Area which is connected to a specific Standarization Initiative has Classification The organization that developed this Standard has Developer The size of document file in some unit, e.g., 104 Kilobyte. has File Size 1. Reference for om2:Measure <http://www.ontology-of-units-of-measure.org/page/om-2/Measure> 2. om2:Measure om2:hasNumericalValue xsd:float; 3. om2:Measure om2:hasUnit om2:Unit; 4. om2:hasUnit om2:InformationCapacityUnit; is another possibility for range that could not be verified. 5. rdfs:seeAlso <http://www.ontology-of-units-of-measure.org/page/om-2/kilobyte> 6. Documentation on Measure <https://github.com/HajoRijgersberg/OM> Denotes the countries in which the Headquarter of the organization who publishes the Standart has Headquater In Serves as a catalogue of International Classification For Standards has ICS Indicates the list of Standards that are previous versions of a Standard. For example,IEC 60038:2009 has IEC 60038:1983+AMD1:1994+AMD2:1997,IEC 60038:1983/AMD2:1997,IEC 60038:1983/AMD1:1994,IEC 60038:1983,IEC 60038:1975/AMD1:1977,IEC 60038:1975,IEC 60038:1967,IEC 60038:1954,IEC 60038:1938,IEC 60038:1927 as previous versions. has Previous Version The organization that published this Standard has Publisher The relation declaring that a standard is relevant or targets a certain concern. has Target Concern Specifies the Technical Committee or a Sub-Committee that is responsible for creation and maintenance of a standard has Technical Committee Links the Standarization Frameworks with the Classification of Standards is Described in Represent the relation that connects two standards when standard A is the implementation of standard B, e.g., B2MML isImplementationOf ISA-95. is Implementation Of Represent any type of relation that connects two standards. related To has Associated Standard Standard A uses the structure of Standard B. For example, OPC UA uses Structure Of IEC_61804 (EDDL) use Structure Of Defines that Standard A uses Standard B. For example, IEC_62714(AML) uses MathML. uses indicates that some Standard Classification entity has a similar scope as another. This property most probably is symmetric but not transitive. alignes With A relation specifying that a vewpoint regards a Concern. frames A relation between two different concerns where dealing with the subject Concern supports in achieving the object concern supports has numerical value Abbreviated name of the thing. has Abbreviated Name Points the Standard with the name of the Industrial Domain has Domain Name Formation date of the Organization has Formation Date Indicates the current Edition/Version number of the document. has Edition Describes the name of the implementation or serialization format of the Publication, e.g., XML, Document, binary, batch has Implementation Format Specifies the objectives for the different ISA 95 levels. has Objective Point to the URL of a recognized Ontology representation of the Standard has Ontology Indicates the number of pages in the document. has Pages Publication date of the Publication has Publication Date Stability date of a publication. Publications are valid for a certain period, i.e., the Stability Period. This property defines the end of the stability period. has Stability Date The data specified is not actually a Date but an Year Publication status of the Standard, e.g., Valid, Revised, Published, under preparation, Released has Status Specifies the tasks for the different ISA 95 levels. has Task Name of the Organization Org Name Name of the standard part. std Part Name sebastian Often these enabling functions, the so-called crosscutting functions, need to be made available across many of the system functional components. For Reference Architecture 6: Functional Viewpoint example, system functions need to be connected so they can interact with each other to complete functionality at the system level. IIRA Crosscutting Function IIRA Functional Domain IIRA System Characteristic A legal document giving official permission to do something with a Resource. License Document IDS RAM Perspective Describes the Administration Shell concept to organize/classify standards into submodels Admin Shell Sub Model RAMI Hierarchy Level RAMI IT Layer RAMI Life Cycle Layer http://www.zvei.org/en/subjects/Industry-40/Pages/The-Reference-Architectural-Model-RAMI-40-and-the-Industrie-40-Component.aspx It describes the different Life Cycle and Value Stream layers for the RAMI model according to the IEC 62890 Standard. RAMI Life Cycle Layer Alliance of Industrial Internet Architecture Classification A Reference Architecture describes the structure of a system with its element types and their structures, as well as their interaction types, among each other and with their environment. Describing this, a Reference Architecture defines restrictions for an instantiation (concrete architecture). Through abstraction from individual details, a Reference Architecture is universally valid within a specific domain. Further architectures with the same functional requirements can be constructed based on the reference architecture. Along with reference architectures comes a recommendation, based on experiences from existing developments as well as from a wide acceptance and recognition by its users or per definition. [ISO/IEC42010] Note: It is important to distinguish the Reference Architecture from a Reference Architecture Description. While the first refers to a mental model or shared concept, the second is potentially only one of several different documents describing this model. A Reference Architecture describes the structure of a system with its element types and their structures, as well as their interaction types, among each other and with their environment. Describing this, a Reference Architecture defines restrictions for an instantiation (concrete architecture). Through abstraction from individual details, a Reference Architecture is universally valid within a specific domain. Further architectures with the same functional requirements can be constructed based on the reference architecture. Along with reference architectures comes a recommendation, based on experiences from existing developments as well as from a wide acceptance and recognition by its users or per definition. [ISO/IEC42010] Note: It is important to distinguish the Reference Architecture from a Reference Architecture Description. While the first refers to a mental model or shared concept, the second is potentially only one of several different documents describing this model. ISO 42010 definition of an Architecture Description Architecture Description https://www.iso.org/standard/50508.html Suply Chain Management Business Cycle. Business Cycle SCM https://en.wikipedia.org/wiki/Supply_chain_management Connectivity Layer of the Internet Connectivity Framework Connectivity Layer Represents the Domains in which the Standards can be used Domain Edgecross Layer IDS RAM Layer sebastian Describes the ISA95 levels to classify the industry Standards according to those levels. Eg., Device, SCADA, etc. It has strong relation to the RAMI Hierarchy levels ISA 95 Level A IVI Layer describes one of three layers of smart manufactoring as proposed by the Industrial Value Chain Initiative (IVI). IVI Layer Describes the layers of the standardization frameworks. In some cases, the layers are connected to dimensions of the frameworks. Layer NGSI-LD NGSI Context Information Management API OCF Framework Block PLM is the process of managing the entire lifecycle of a product from inception, through engineering design and manufacture, to service and disposal of manufactured products. Related areas are PLMManagement, Modeling Practice, Product Model Data exchange, Manufacturing Model Data, Product Catalog Data. Product Development Life-Cycle Phase https://en.wikipedia.org/wiki/Product_lifecycle Product Development Life Cycle Collections of machines, equipment, and auxiliary systems organized to create goods and services from various resources. Production System Life Cycle Specifies a Publication. E.g., International Standards,Technical Specifications,Publicly Available Specifications,Amendments Technical Corrigenda,Interpretation Sheets,Technical Reports,Guides Publication Describes the layers of the standardization frameworks. In some cases, the layers are connected to dimensions of the frameworks. A stakeholder is an individual, team, organization or classes thereof,having an interest in a concern and by extension an interest in the viewpoint and system. Layer Stakeholder IIC:PUB:G1:V1.80:20170131 Publications referred: 'IIC:PUB:G1:V1.80:20170131' '4.1 STAKEHOLDERS' 'Page 20' Describes categorization areas that the different Standardizations Initiatives use to category Standards. Standard Classification Define the standards organizations that develop and publish industry standards StandardOrganization Typically Standards are divided into parts. E.g., ISA 95 has part Part 1: Models and Terminology, Part 2: Object Model Attributes, etc. StandardPart Describes existings Standardizations Initiatives, e.g, RAMI, NIST. Standarization Framework Reference Architecture sebastian A Technology is an implementation of one or many standards in order to achieve a goal. Technology ISO 42010 definition of a Viewpoint Viewpoint x-road Section IDS RAM Layer Artificial intelligence (AI) is intelligence exhibited by machines. In computer science, an ideal "intelligent" machine is a flexible rational agent that perceives its environment and takes actions that maximize its chance of success at some goal. Colloquially, the term "artificial intelligence" is applied when a machine mimics "cognitive" functions that humans associate with other human minds, such as "learning" and "problem solving". (source: wikipedia) Artificial Intelligence AMQP (Advanced Message Queuing Protocol): An open standard application layer protocol for message-oriented middleware. The defining features of AMQP are message orientation, queuing, routing (including point-to-point and publish-and-subscribe), reliability and security. (source: https://www.postscapes.com/internet-of-things-protocols/) AMQP Access to the service shall be regulated by access policies. Users entitled in access policies to envoke a given service must be able to actually envoke it. Access Policy IoT-A Requirement UNI.604 Access Rights for IoT-Cloud TODO what is the IoT Cloud? A system built using the ARM shall support the reversing of the pseudonymization processes in order to guarantee mutual accountability Accountability IoT-A Requirement UNI.605 Sending data or a signal to a kind of actuating device, which leads to a change in a defined environment. Actuation Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.1 THE CONTROL DOMAIN' 'Page 28' Because of clients' need and time's requirements, there ought to be constant change in the system of associated devices for Internet of Things. Adaptability is continuously a need for survival and development of Internet of Things. Adaptability TODO merge with programmability or evolveability Represents the classifications of the standards according to the submodels of the administration shell. Administration Shell Aeron - Efficient reliable UDP unicast, UDP multicast, and IPC message transport. (source: https://www.postscapes.com/internet-of-things-protocols/) Aeron Agility as a key pillar that enables quick and astute business operational decisions for an OpenFog System. The predicted scale of the data generated by IoT means that it is highly unlikely that humans alone will be able to comprehend the data, derive knowledge and make wise decisions about how to best leverage their IoT assets for the benefit of their businesses. In the OpenFog architecture the agility pillar is about making sure that the valuable data generated in the IoT can be rapidly transformed into actionable insights that drive rapid decisions and further levels of automation to support business interest. Spurce: OpenFog Consortum Architecture Whitepaper Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.7 Agility Pillar' 'Page 31' AII Data Classification Page 32 Page 25 AII Network Classification pdf Page 25 Page 10 AII Security Classification pdf Page 37 Page 32 The AllSeen Alliance is a nonprofit consortium dedicated to enabling and driving the widespread adoption of products, systems and services that support the Internet of Everything with an open, universal development framework supported by a vibrant ecosystem and thriving technical community' (source: https://www.postscapes.com/internet-of-things-protocols/) AllSeen Alliance Alliance Industrie du Futur Alliance of Industrial Internet 工业互联网产业联盟 Alljoyn - An open source software framework that makes it easy for devices and apps to discover and communicate with each other. (source: https://www.postscapes.com/internet-of-things-protocols/) Alljoyn pdf Page 29 Page 28 pdf Page 29 Page 28 pdf pdf Anonymity is the guarantee for a user to interact with a system without being tracked or connected to its real-world identity. Anonymity UNI.322 IoT-A Requirement UNI.001 IoT-A Requirement UNI.322 Arrowhead Framework Arrowhead Project The concern of being able to manage the system onboarding, configuration, policy, software/firmware updates and other lifecycle management operations. Asset Management Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.1 THE CONTROL DOMAIN' 'Page 29' Authentication before opening a valid connection; this can be done by just verifying the server identity or doing mutual authentication. Authentication IoT-A Requirement UNI.612 IoT-A Requirement UNI.618 IoT-A Requirement UNI.319 IoT-A Requirement UNI.502 IoT-A Requirement UNI.503 Autoscaling, also spelled auto scaling or auto-scaling, and sometimes also called automatic scaling, is a method used in cloud computing, whereby the amount of computational resources in a server farm, typically measured in terms of the number of active servers, scales automatically based on the load on the farm. It is closely related to, and builds upon, the idea of load balancing. Auto Scaling TODO already covered by scalability? Authonomous Communication frames all requirements in order to autonomously establish communication channels between participants of a network. In most cases, this will be a machine-to-machine communication channel. Main challenges are related to interoperability. Autonomous Communication IoT-A Requirement UNI.005 IoT-A Requirement UNI.012 IoT-A Requirement UNI.708 A system built using the Reference Architecture shall be able to remotely control and configure devices. Autonomous Configuration IoT-A Requirement UNI.015 IoT-A Requirement UNI.031 IoT-A Requirement UNI.032 IoT-A Requirement UNI.060 IoT-A Requirement UNI.247 IoT-A Requirement UNI.509 IoT-A Requirement UNI.704 IoT-A Requirement UNI.706 IoT-A Requirement UNI.717 Publications referred: '<https://doi.org/10.1016/j.jksuci.2016.10.003>' '1.2. Utilities of IoT' 'Page 295' In reliability theory and reliability engineering, the term availability has the following meanings: * The degree to which a system, subsystem or equipment is in a specified operable and committable state at the start of a mission, when the mission is called for at an unknown, i.e. a random, time. Simply put, availability is the proportion of time a system is in a functioning condition. This is often described as a mission capable rate. Mathematically, this is expressed as 100% minus unavailability. * The ratio of (a) the total time a functional unit is capable of being used during a given interval to (b) the length of the interval. For example, a unit that is capable of being used 100 hours per week (168 hours) would have an availability of 100/168. However, typical availability values are specified in decimal (such as 0.9998). In high availability applications, a metric known as nines, corresponding to the number of nines following the decimal point, is used. With this convention, "five nines" equals 0.99999 (or 99.999%) availability. (source: wikipedia) Availability IoT-A Requirement UNI.058 IoT-A Requirement UNI.064 IoT-A Requirement UNI.239 IoT-A Requirement UNI.321 IoT-A Requirement UNI.601 IoT-A Requirement UNI.610 IoT-A Requirement UNI.616 Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.6 Reliability, Availability, and Serviceability (RAS)Pillar' 'Page 29' Awareness is the ability to directly know and perceive, to feel, or to be cognizant of events. More broadly, it is the state of being conscious of something. Another definition describes it as a state wherein a subject is aware of some information when that information is directly available to bring to bear in the direction of a wide range of behavioral processes. The concept is often synonymous to consciousness and is also understood as being consciousness itself. Awareness Big Data Value Association BDVA In computing, bandwidth is the maximum rate of data transfer across a given path. Bandwidth may be characterized as network bandwidth, data bandwidth, or digital bandwidth. Bandwidth The Cloud and High Performance Computing (HPC): Effective Big Data processing and data management might imply the effective usage of Cloud and High Performance Computing infrastructures. This area is separately elaborated further in collaboration with the Cloud and High Performance Computing (ETP4HPC) communities. BDVA Cloud and High Performance Computing Page 40 Page 37 Page 40 Page 37 Effective communication and connectivity mechanisms are necessary in providing support for Big Data. This area is separately further elaborated, along with various communication communities, such as the 5G community. BDVA Communication and Connectivity Page 40 Page 37 Page 40 Page 37 Page 40 Page 37 Page 40 Page 38 Page 40 Page 37 Big Data often need support to maintain security and trust beyond privacy and anonymisation. The aspect of trust frequently has links to trust mechanisms such as blockchain technologies, smart contracts and various forms of encryption. BDVA Cybersecurity and Trust Page 40 Page 37 Page 40 Page 37 Data analytics to improve data understanding, deep learning and the meaningfulness of data. BDVA Data Analytics Page 40 Page 37 Page 40 Page 37 Principles and techniques for data management BDVA Data Management Page 40 Page 37 Page 40 Page 37 Optimised and scalable architectures for analytics of both data-at-rest and data-in-motion, with low latency delivering real-time analytics. BDVA Data Processing Architectures Page 40 Page 37 Page 40 Page 37 Privacy and anonymisation mechanisms to facilitate data protection. This is shown related to data management and processing as there is a strong link here, but it can also be associated with the area of cybersecurity. BDVA Data Protection Page 40 Page 37 Page 40 Page 37 Data sharing and trading are seen as important ecosystem enablers in the data economy, although closed and personal data present particular challenges for the free flow of data. The following two conceptual solutions – Industrial Data Platforms (IDPs) and Personal Data Platforms (PDPs) – introduce new approaches to addressing this particular need to regulate closed proprietary and personal data. BDVA Data Sharing Platforms Page 40 Page 37 Page 40 Page 37 Engineering and DevOps for building Big Data Value systems: This topic will be elaborated in greater detail along with the NESSI Software and Service community. Data Visualisation and User Interaction Page 40 Page 37 Page 40 Page 37 Engineering and DevOps for building Big Data Value systems: This topic will be elaborated in greater detail along with the NESSI Software and Service community. BDVA Engineering and DevOps Page 40 Page 37 Page 40 Page 37 BDVA Strategic Research and Innovation Agenda This Strategic Research and Innovation Agenda (SRIA) defines the overall goals, main technical and non-technical priorities, and a research and innovation roadmap for the European Public Private Partnership (PPP) on Big Data Value. The SRIA has been developed by the Big Data Value Association (BDVA), an industry-led organisation representing large businesses, small and medium-sized enterprises (SMEs), and research organisations in Europe. BDVA SIRA Page 106 Page 1 Page 106 Page 1 Standardisation of Big Data technology areas to facilitate data integration, sharing and interoperability BDVA Standards Page 40 Page 37 Page 40 Page 37 IoT, CPS, Edge and Fog Computing: A main source of Big Data is sensor data from an IoT context and actuator interaction in Cyber Physical Systems. In order to meet real-time needs it will often be necessary to handle Big Data aspects at the edge of the system. This area is separately elaborated further in collaboration with the IoT (Alliance for Internet of Things Innovation (AIOTI)) and CPS communities BDVA IoT CPS and Edge Computing Page 40 Page 37 Page 40 Page 37 Big data is a term for data sets that are so large or complex that traditional data processing applications are inadequate to deal with them. Challenges include analysis, capture, data curation, search, sharing, storage, transfer, visualization, querying, updating and information privacy. The term "big data" often refers simply to the use of predictive analytics, user behavior analytics, or certain other advanced data analytics methods that extract value from data, and seldom to a particular size of data set. (source: wikipedia) Big Data Applications The term Blockchain refers to a set of technologies for distributed databases. Blockchain Bluetooth works in the 2.4 GHz ISM band and uses frequency hopping. With a data rate up to 3 Mbps and maximum range of 100m. Each application type which can use Bluetooth has its own profile. (source: https://www.postscapes.com/internet-of-things-protocols/) Bluetooth Electronic business, or e-business, is the application of information and communication technologies in support of all the activities of business. Commerce constitutes the exchange of products and services between businesses, groups and individuals and can be seen as one of the essential activities of any business. (source: wikipedia) Business Context Business process management Business process management (BPM) is a field in operations management that focuses on improving corporate performance by managing and optimizing a company's business processes. It can therefore be described as a "process optimization process." It is argued that BPM enables organizations to be more efficient, more effective and more capable of change than a functionally focused, traditional hierarchical management approach. These processes can impact the cost and revenue generation of an organization. As a policy-making approach, BPM sees processes as important assets of an organization that must be understood, managed, and developed to announce value-added products and services to clients or customers. This approach closely resembles other total quality management or continual improvement process methodologies and BPM proponents also claim that this approach can be supported, or enabled, through technology. As such, many BPM articles and scholars frequently discuss BPM from one of two viewpoints: people and/or technology. (source: wikipedia) BPM IoT-A Requirement UNI.211 IoT-A Requirement UNI.212 IoT-A Requirement UNI.214 IoT-A Requirement UNI.215 IoT-A Requirement UNI.229 A financial transaction is an agreement, communication, or movement carried out between a buyer and a seller to exchange an asset for payment. It involves a change in the status of the finances of two or more businesses or individuals. The buyer and seller are separate entities or objects, often involving the exchange of items of value, such as information, goods, services, and money. It is still a transaction if the goods are exchanged at one time, and the money at another. This is known as a two-part transaction: part one is giving the money, part two is receiving the goods. (source: wikipedia) Business Transactions Business Value Publications referred: '(IIC:PUB:G1:V1.80:20170131' '4 BUSINESS VIEWPOINT' 'Page 20' Data Artefacts from different Data Providers are delivered in order to provide additional insights (e.g. Collaborative Predictive Maintenance). Cardinality of Participants Certification refers to the confirmation of certain characteristics of an object, person, or organization. This confirmation is often, but not always, provided by some form of external review, education, assessment, or audit. Accreditation is a specific organization's process of certification. (source: wikipedia) Certification Cloud computing is a type of Internet-based computing that provides shared computer processing resources and data to computers and other devices on demand. It is a model for enabling ubiquitous, on-demand access to a shared pool of configurable computing resources (e.g., computer networks, servers, storage, applications and services), which can be rapidly provisioned and released with minimal management effort. Cloud computing and storage solutions provide users and enterprises with various capabilities to store and process their data in third-party data centers that may be located far from the user–ranging in distance from across a city to across the world. Cloud computing relies on sharing of resources to achieve coherence and economy of scale, similar to a utility (like the electricity grid) over an electricity network. (source: wikipedia) Cloud Computing Capability IoT-A Requirement UNI.102 IoT-A Requirement UNI.234 IoT-A Requirement UNI.021 IoT-A Requirement UNI.095 IoT-A Requirement UNI.303 IoT-A Requirement UNI.306 IoT-A Requirement UNI.307 IoT-A Requirement UNI.308 IoT-A Requirement UNI.309 IoT-A Requirement UNI.310 IoT-A Requirement UNI.311 IoT-A Requirement UNI.312 IoT-A Requirement UNI.313 IoT-A Requirement UNI.315 IoT-A Requirement UNI.318 IoT-A Requirement UNI.321 IoT-A Requirement UNI.324 IoT-A Requirement UNI.716 Complex Event Processing Event processing is a method of tracking and analyzing (processing) streams of information (data) about things that happen (events), and deriving a conclusion from them. Complex event processing, or CEP, is event processing that combines data from multiple sources to infer events or patterns that suggest more complicated circumstances. The goal of complex event processing is to identify meaningful events (such as opportunities or threats) and respond to them as quickly as possible. (source: wikipedia) CEP IoT-A Requirement UNI.232 In general, compliance means conforming to a rule, such as a specification, policy, standard or law. Regulatory compliance describes the goal that organisations aspire to achieve in their efforts to ensure that they are aware of and take steps to comply with relevant laws and regulations. Due to the increasing number of regulations and need for operational transparency, organizations are increasingly adopting the use of consolidated and harmonized sets of compliance controls. This approach is used to ensure that all necessary governance requirements can be met without the unnecessary duplication of effort and activity from resources. (source: wikipedia) Compliance Confidentiality involves a set of rules or a promise usually executed through confidentiality agreements that limits access or places restrictions on certain types of information. Confidentiality Internet of Things associates various smart devices through the Internet, and it gives a facility to concentrated checking and control of associated equipment. Connectivity System Architect TODO Data-memory-constrained devices must be able to participate in communication. This means that a system built using the ARM shall support communication stacks with small data footprint. Small devices with limited CPU, memory, and power resources, so-called "constrained devices" (often used as sensors/actuators, smart objects, or smart devices) can form a network, becoming "constrained nodes" in that network. Such a network may itself exhibit constraints, e.g., with unreliable or lossy channels, limited and unpredictable bandwidth, and a highly dynamic topology. (source: https://tools.ietf.org/html/rfc7228) Constrained Devices UNI.306 IoT-A Requirement UNI.306 IoT-A Requirement UNI.307 Developer The look-up service of the system shall withold or grant information depending on context. Context includes application involved, requesting entity, and security permissions. Context Awareness UNI.407 IoT-A Requirement UNI.407 IoT-A Requirement UNI.420 IoT-A Requirement UNI.421 Publications referred: '<https://doi.org/10.1016/j.jksuci.2016.10.003>' '1.2. Utilities of IoT' 'Page 296' Cost Efficiency DataRecovery System Architect A system built using the ARM shall support identity-locator split, i.e. making the device's identity independent from its locator. Cross-domain Identity Management IoT-A Requirement UNI.314 The resources sharing by contrasting users keeps cloud service provider from having the capacity to customize their services to meet the diverse necessities of customers Customization DIN 77005-1:2018-09 DIN EN 50129 DIN EN 50155 DIN EN 61511 Data access typically refers to software and activities related to storing, retrieving, or acting on data housed in a database or other repository. [...] Data access crucially involves authorization to access different data repositories. (source: wikipedia) Data Access IoT-A Requirement UNI.022 Automated access control based on formalized descriptions. In the fields of physical security and information security, access control (AC) is the selective restriction of access to a place or other resource. The act of accessing may mean consuming, entering, or using. Permission to access a resource is called authorization. Locks and login credentials are two analogous mechanisms of access control. (source: wikipedia) Data Access Control IoT-A Requirement UNI.002 IoT-A Requirement UNI.067 IoT-A Requirement UNI.410 IoT-A Requirement UNI.411 IoT-A Requirement UNI.412 IoT-A Requirement UNI.413 IoT-A Requirement UNI.504 Data Aggregation is the compiling the data before Data Processing Data Aggregation Analysis of data is a process of inspecting, cleaning, transforming, and modeling data with the goal of discovering useful information, suggesting conclusions, and supporting decision-making. Data analysis has multiple facets and approaches, encompassing diverse techniques under a variety of names, in different business, science, and social science domains. Data mining is a particular data analysis technique that focuses on modeling and knowledge discovery for predictive rather than purely descriptive purposes. Business intelligence covers data analysis that relies heavily on aggregation, focusing on business information. (source: wikipedia) Data Analytics IoT-A Requirement UNI.232 Data at rest in information technology means inactive data that is stored physically in any digital form (e.g. databases, data warehouses, spreadsheets, archives, tapes, off-site backups, mobile devices etc.). Data at rest is used as a complement to the terms data in use and data in transit which together define the three states of digital Data. (source: wikipedia) Data at rest Methods to unambiguously describe data resources. Data Description IoT-A Requirement UNI.004 IoT-A Requirement UNI.240 How to find desired resources, Data Assets, Data Artifacts in a defined environment. Data Discovery IoT-A Requirement UNI.236 IoT-A Requirement UNI.408 IoT-A Requirement UNI.422 Business aspects of data exchange Digital economy refers to an economy that is based on digital computing technologies. The digital economy is also sometimes called the Internet Economy, the New Economy, or Web Economy. Increasingly, the "digital economy" is intertwined with the traditional economy making a clear delineation harder. (source: wikipedia) Data Economy The resources sharing by contrasting users keeps cloud service provider from having the capacity to customize their services to meet the diverse necessities of customers Customization Data secrecy and encryption Data integrity is the maintenance of, and the assurance of the accuracy and consistency of, data over its entire life-cycle, and is a critical aspect to the design, implementation and usage of any system which stores, processes, or retrieves data. Data Integrity Isolation is one of the ACID (Atomicity, Consistency, Isolation, Durability) properties adopted by the database systems Data Isolation Data lifecycle management includes every phase of a "record" from its beginning to its end. And while it is generally applied to information that rises to the classic definition of a record (and thus related to records management), it applies to all informational assets. During its existence, information can become a record by being identified as documenting a business transaction or as satisfying a business need. (source: wikipedia) Data lifecycle management One of the features of cloud computing is geodistribution of data among several servers. But this can be an issue for the enterprise, as the location of the data is unknown to the user. Data Location Data Market Austria DMA Data as an economic good; it's offered, demanded, and priced. Data Markets Data Ownership declare the possesion on an information resource that is independent of its location, e.g. personal data belongs to the related person no matter where it is stored. Data Ownership Data processing and analytic components from the App Store create flexible data processing pipelines. Data Processing IoT-A Requirement UNI.018 Data protection is the relationship between collection and dissemination of data, technology, the public expectation of privacy, and the legal and political issues surrounding them. Privacy concerns exist wherever personally identifiable information or other sensitive information is collected, stored, used, and finally destroyed or deleted – in digital form or otherwise. Improper or non-existent disclosure control can be the root cause for privacy issues. (source: wikipedia) Data Protection Datenschutz Information privacy Data Publishing is the concern regarding all aspects of getting data (publicly) available. Data Publishing Data quality refers to the level of quality of data. There are many definitions of data quality but data are generally considered high quality if "they are fit for their intended uses in operations, decision making and planning." (Tom Redman<Redman, T.C. (2008). Data driven: Profiting from your most important business asset (p. 56). Boston, Mass.: Harvard Business Press.>). Alternatively, data is deemed of high quality if it correctly represents the real-world construct to which it refers. Furthermore, apart from these definitions, as data volume increases, the question of internal consistency within data becomes significant, regardless of fitness for use for any particular external purpose. People's views on data quality can often be in disagreement, even when discussing the same set of data used for the same purpose. (source: wikipedia) Data Quality IoT-A Requirement UNI.235 IoT-A Requirement UNI.236 IoT-A Requirement UNI.237 Data Sovereignty The IoT data are collected from various data sources in different structures and formats. IoT enables the collected data to be stored both in physical devices and cloud storage. Data Storage The Data Transfer Project (DTP) extends data portability beyond a user’s ability to download a copy of their data from their service provider (“provider”), to providing the user the ability 1 to initiate a direct transfer of their data into and out of any participating provider. The Data Transfer Project is an open source initiative to encourage participation of as many providers as possible. The DTP will enhance the data portability ecosystem by reducing the infrastructure burden on both providers and users, which should in turn increase the number of services offering portability. The protocols and methodology of the DTP enable direct, service-to-service data transfer with streamlined engineering work. Data Transfer Project The Data Transfer Project Whitepaper provides a brief overview on the intends of the Data Transfer Project and the targeted approach. Data Transfer Project Whitepaper Data usage control can be seen as an extension of data access control. It is about the specification and enforcement of restrictions regulating what is allowed to happen with data, and what is not. Data usage control thus is concerned with requirements that pertain to data processing (obligations) rather than data access (provisions). It is primarily relevant in the context of intellectual property protection, privacy protection, compliance with regulations, and digital rights management. Data Usage Control The data in IoT are always mass, distributed, and time-related and position related. At the same time, the data sources of the IoT are heterogeneous. There is a vast amount of real-time data collected by the IoT devices. Data Collection In edge computing, user private data is outsourced to the edge server and its ownership and control are separated, which causes users to lose their physical control over the outsourced data. Data Confidentiality Data Transfer Project Overview and Fundamentals These are business Decision makers Decision maker Publications referred: '(IIC:PUB:G1:V1.80:20170131' '3.5.1 BUSINESS VIEWPOINT' 'Page 15' 'Priyanka' Device Security Device Authentication DMA Architecture This document presents the DMA Data Technology Specification and Development Roadmap regarding the ongoing work in WP6 of the DMA project. The document relates to deliverable D2.2 “D2.2 Community-driven Data-Services Ecosystem Requirements (1st version)” which formulates the requirements of the DMA community. It will be explained in what way the requirements formulated in D2.2 are going to be addressed. The document gives an overview about the components which are going to be developed in WP6 and how these components are planned to be employed to provide DMA core services. The expected outputs of these services are described and a procedure of describing a 3rd party service for DMA platform is addressed. DMA Service Technology Specification and Development Roadmap The architecture description of the Data Transfer Project has not yet been published in a sufficient manner. Data Transfer Project Architecture DTP Deployment DTP Ecosystem DTP Security & Privacy DTP System A systems ability to adjust its behaviour on dynamic changes in its environment. Dynamic Adjustability IoT-A Requirement UNI.713 A systems ability to retrive according information on required assets and components on-the-fly. Dynamic Discovery IoT-A Requirement UNI.418 IoT-A Requirement UNI.419 IoT-A Requirement UNI.420 IoT-A Requirement UNI.421 The concern of being able to understanding the states, conditions and behaviors of the systems under control and other systems by interpreting and correlating data gathered from sensors and other systems. Edge Analytics Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.1 THE CONTROL DOMAIN' 'Page 29' Edge Computing is pushing the frontier of computing applications, data, and services away from centralized nodes to the logical extremes of a network. It enables analytics and knowledge generation to occur at the source of the data. This approach requires leveraging resources that may not be continuously connected to a network such as laptops, smartphones, tablets and sensors. Edge Computing covers a wide range of technologies including wireless sensor networks, mobile data acquisition, mobile signature analysis, cooperative distributed peer-to-peer ad hoc networking and processing also classifiable as Local Cloud/Fog computing and Grid/Mesh Computing, dew computing, mobile edge computing, cloudlet, distributed data storage and retrieval, autonomic self-healing networks, remote cloud services, augmented reality, and more. (source: wikipedia) Edge computing Edgecross Architecture Edgecross Consortium Edgecross Edgecomputing Layer pdf Page 15 Page 9 pdf Page 15 Page 9 Edgecross FA pdf Page 15 Page 9 pdf Page 15 Page 9 Edgecross IT Systems Layer pdf Page 15 Page 9 pdf Page 15 Page 9 pdf pdf Edgecross Whitepaper Edgecross Consortium to Address Edge Integration in IIoT-enabled Architectures Methods to unambiguously describe client and server endpoints. Endpoint Description Mechanisms to interact with a service and to access it through the network. Endpoint Invocation IoT-A Requirement UNI.100 IoT-A Requirement UNI.417 Energy Control IoT-A Requirement UNI.100 IoT-A Requirement UNI.101 IoT-A Requirement UNI.309 IoT-A Requirement UNI.310 IoT-A Requirement UNI.505 IoT-A Requirement UNI.512 IoT-A Requirement UNI.714 Efficient energy use, sometimes simply called energy efficiency, is the goal to reduce the amount of energy required to provide products and services. Energy Efficiency BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017 Event-Driven Messaging IoT-A Requirement UNI.005 IoT-A Requirement UNI.233 A system shall accomodate fast developmental changes in applications and network. Evolvability IoT-A Requirement UNI.701 IoT-A Requirement UNI.702 The system's ability to flexibly connect/adjust data flows in order to reach a defined target. Execution Variability "Extensibility could be a huge challenge at the edge of the network, unlike a mobile system, the things in the IoT could be very dynamic. When the owner purchases a new thing, can it be easily added to the current service without any problem? Or when one thing is replaced due to wearing out, can the previous service adopt a new node easily? These problems should be solved with a flexible and extensible design of service management layer in the edgeOS." Extensibility The FIWARE platform contains market-ready open source software, combining components that enable the connection to IoT with Context Information Management and Big Data services in the Cloud. FIWARE Architecture How can a fair and non-discriminating access to (compute and storage) resources be established? Fairness Fault tolerance is the property that enables a system to continue operating properly in the event of the failure of some (one or more faults within) of its components. If its operating quality decreases at all, the decrease is proportional to the severity of the failure, as compared to a naively designed system in which even a small failure can cause total breakdown. Fault Tolerance FIWARE The Generic Enablers (GEs) from the Advanced Web-based User Interface (WebUI) chapter cover a set of GEs that provide an advanced user experience using HTML-5 and a Web-based UI approach. The objective of the Advanced Web-based UI GE is to significantly improve the user experience for the Future Internet by adding new user input and interaction capabilities, such as interactive 3D graphics, immersive interaction with the real and virtual world via Augmented Reality, virtualizing the display and driving them over the network, and many more. FIWARE Advanced Web-based User Interface The Generic Enablers (GE) for the Apps Chapter together build an ecosystem of applications, services and data that is sustainable and fosters innovation as well as cross-fertilization. In particular the Apps Generic Enablers supports managing applications, services and data in a business framework across the whole service life cycle from creation through composition of applications and data to monetization and revenue sharing. A couple of basic GEs are important to realize the vision of such an applications, services and data business framework, which enables new business models in an agile and flexible way. Among them: a store, a marketplace, a revenue sharing engine, an application composer through mashup and a data visualization and analysis component. The Business Framework is heavily relying on USDL as common uniform description format for services which does not only focus on technical aspects of service, but also on business aspects as well as functional and non-functional service attributes. The Application Mashup GE aims at allowing end users without programming skills to quickly compose beautiful web applications and dashboards/cockpits mashing up widgets, operators and data sources from a shared catalogue. The Data Visualisation GE aims at creating agile, beautiful visualizations and meaningful reports useful to present the large variety of datasets. Data stakeholders will bring in the play as well as providing customisable data analytics. FIWARE Applications Services and Data Delivery The Cloud Chapter offers Generic Enablers (GEs) that comprise the foundation for designing a modern cloud hosting infrastructure that can be used to develop, deploy and manage Future Internet applications and services. Provided hosting capabilities are of several kinds and at several levels of resource abstraction -- aiming at the needs of different applications hosted on the cloud. The IaaS Data Center Resource Management (DCRM) GE is offering provisioning and life cycle management of virtualized resources (compute, storage, network) associated with virtual machines. The Object Storage GE offers provisioning and life cycle management of object-based storage containers and elements. The Job Scheduler GE offers the application to submit and manage computational jobs in a unified and scalable manner. The Edgelet Management GE offers the capability to host lightweight application components, called edgelets. Moreover, the IaaS Service Management (SM) GE provides the means to host complex applications. Lastly, the PaaS Management GE uses the above capabilities to offer provisioning and management of complete PaaS environments, leveraging also the Software Deployment and Configuration (SDC) GE which offers a flexible framework for installation and customization of software products (via Chef recipes) within individual virtual machines. FIWARE Cloud Hosting The Data/Context Management FIWARE chapter aims at providing outperforming and platform-like GEs that will ease development and provision of innovative Applications that require gathering, publication, processing and exploitation of information and data streams in real-time and at massive scale. Combined with GEs coming from the Apps Chapters, Application Providers will be able to build innovative business models based on exploitation of massive data provided by end users. FIWARE Data/Context Management GEs allow to gather information from context and other sources (Context Broker), mediate metadata among GEs and applications (Metadata pre-processor) query stored information through an homogeneous layer (Query Broker), , annotate existing information (Semantic Annotation), store and manage semantic information (Semantic Application Support), generate new knowledge from big data stores using a Map & Reduce paradigm (Big Data analysis) and react to different types of scenarios (Complex Event Processing). It also provides GEs for media management, as easy creation of advanced video applications (Stream Oriented GE) and specifically, video analysis in the compressed domain (CDVA). FIWARE Data/Context Management The deployment of the architecture of the IoT Service Enablement chapter is typically distributed across a large number of Devices, several Gateways and the Backend. A device is a hardware entity, component or system that either measures properties of a thing/group of things or influences the properties of a thing/group of things or both measures/influences. Sensors and actuators are devices. IoT Resources are computational elements (software) that provide the technical means to perform sensing and/or actuation on the device. The resource is usually hosted on the device. IoT GEs have been spread in two different domains: Gateway and Backend. While IoT Gateway GEs provide inter-networking and protocol conversion functionalities between devices and the IoT Backend GEs, the IoT Backend GEs provide management functionalities for the devices and IoT domain-specific support for the applications. FIWARE IoT Services Enablement The Future Internet services will always be exposed to different types of threats that can lead to severe misuse and damage. Creating secured and trusted services without sacrificing much of the desired functionality, usability, performance and cost efficiency is a great challenge, especially in a dynamic environment where new threats and attack methods emerge on a daily basis. The overall ambition of the Security Architecture of FIWARE is to demonstrate that the Vision of an Internet that is "secure by design" is becoming reality. Based on achievements to date and/or to come in the short-term (both from a technological but also a standardization perspective) we will show that "secure by design" is possible. Security, Privacy and Trust in FIWARE is mainly focusing on delivering tools and techniques to have the above-mentioned security needs properly met. Furthermore a decision making support and the automation of countermeasures allow alleviating the workload of users and administrators while raising their security awareness. The high-level Reference Architecture is formed by four main blocks of GEs: Cybersecurity, Identity and Access Management (and Enforcement), Privacy, Trust and Trustworthiness. FIWARE Security A system built using the ARM shall support physical entity location tracking (geo spatial and/or logical location) Geo tracking IoT-A Requirement UNI.016 Discovery and lookup services of the system shall allow locating physical entities based on geographical parameters. Geospatial data and information UNI.401 UNI.402 UNI.403 UNI.404 IoT-A Requirement UNI.402 IoT-A Requirement UNI.403 IoT-A Requirement UNI.404 IoT-A Requirement UNI.405 IoT-A Requirement UNI.406 IoT-A Requirement UNI.415 IoT-A Requirement UNI.420 IoT-A Requirement UNI.421 The system energy consumption is expanding at a high rate because of increment in information rates, an increment in quantity of Internet-empowered services and fast development of Internet associated edgedevices. The future IoT will cause a critical increase in the network energy consumption. Greening of IoT International Data Spaces Association IDSA ensures that the special economic interests of business are specifically integrated into the research work of Industrial Date Space. IDSA IDS RAM Business Layer pdf Page 21 Page 17 IDS RAM Certification Perspective pdf Page 84 Page 79 IDS Data Market IDS RAM Functional Layer pdf Page 25 Page 21 IDS RAM Governance Perspective pdf Page 88 Page 84 IDS RAM Information Layer pdf Page 56 Page 32 IDS Interoperability pdf pdf IDS RAM Process Layer pdf Page 32 Page 25 Industrial Data Space Reference Architecture Model IDS RAM The IDS Security Architecture provides means to identify participants, protect communication and data exchange transactions between them, and control the use of data after it has been sent. IDS RAM Security Perspective pdf Page 79 Page 63 IDS RAM System Layer pdf Page 62 Page 56 IDS REFERENCE ARCHITECTURE MODEL INDUSTRIAL DATA SPACE VERSION 2.0 Founded in 2014 to further development, adoption and wide-spread use of interconnected machines, intelligent analytics and people at work. (source: https://www.postscapes.com/internet-of-things-protocols/) IIC Industrial Internet Consortium Industrial Internet Connectivity Framework IICF IICF Framework Layer IICF Framework Layer an instance of the IICF Connectivity Layer IICF Framework Layer pdf Page 17 Page 14 pdf Page 17 Page 14 IICF Link Layer pdf Page 17 Page 14 pdf Page 17 Page 14 IICF Network Layer pdf Page 17 Page 14 pdf Page 17 Page 14 IICF Physical Layer pdf Page 17 Page 14 pdf Page 17 Page 14 IICF Transport Layer pdf Page 17 Page 14 pdf Page 17 Page 14 IIC Vocabulary The Industrial Internet of Things Volume G1: Reference Architecture IIC:PUB:G1:V1.80:20170131 The IIRA addresses the need for a common architecture framework to develop interoperable IIoT systems for diverse applications across a broad spectrum of industrial verticals in the public and private sectors to achieve the true promise of IIoT. Industrial Internet Reference Architecture IIRA Publications referred: 1. The Industrial Internet of Things Volume G1: Reference Architecture (IIC:PUB:G1:V1.80:20170131) IIRA Application Domain Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.4 THE APPLICATION DOMAIN' 'Page 34' pdf Page 35 Page 34 pdf Page 35 Page 34 IIRA Business Domain Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.5 THE BUSINESS DOMAIN' 'Page 34' pdf Page 35 Page 34 pdf Page 35 Page 34 The business viewpoint frames economic aspects and business relations regarded by the IIC Reference Architecture. IIRA Business Viewpoint Publications referred: '(IIC:PUB:G1:V1.80:20170131' '3.5.1 BUSINESS VIEWPOINT' 'Page 15' pdf Page 22 Page 20 pdf Page 22 Page 20 IIRA Connectivity pdf Page 127 Page 8 pdf Page 127 Page 8 IIRA Control Domain Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.1 THE CONTROL DOMAIN' 'Page 27' pdf Page 30 Page 27 pdf Page 30 Page 27 pdf Page 36 Page 34 pdf Page 36 Page 34 IIRA Distributed Data Management The IIRA Functional Viewpoint contains the IIRA Domains in order to describe technical relations and communications between the several dimensions of IoT devices. IIRA Functional Viewpoint Publications referred: '(IIC:PUB:G1:V1.80:20170131' '3.5.3 FUNCTIONAL VIEWPOINT' 'Page 16' pdf Page 38 Page 25 pdf Page 38 Page 25 IIRA Implementation Viewpoint Publications referred: '(IIC:PUB:G1:V1.80:20170131' '3.5.4 IMPLEMENTATION VIEWPOINT' 'Page 16' pdf Page 47 Page 38 pdf Page 47 Page 38 IIRA Information Domain Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.3 THE INFORMATION DOMAIN' 'Page 32' pdf Page 34 Page 32 pdf Page 34 Page 32 There is a renewed movement to distribute computational capability toward the network peripheries, away from concentrated computation centers, to benefit from a reduction in movement of data and communication latency, and enhancement in local intelligent control and, more importantly, resilience. source: Industrial Internet Reference Archietcture IIRA Intelligent and Resilient Control IIRA Operation Domain Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.2 THE OPERATIONS DOMAIN' 'Page 30' pdf Page 32 Page 30 pdf Page 32 Page 30 Computational capabilities ranging from very limited (e.g. in a smart sensor) to reasonably rich (e.g. a cluster of servers) are placed in, attached to or collocated with physical systems (e.g. in smart sensors, devices or machines). These capabilities are connected through a variety of connectivity technologies including wireless. IIRA Physical Systems IIRA Privacy IIRA Reliability Publications referred: '<https://www.iiconsortium.org/pdf/IIC_PUB_G4_V1.00_PB-3.pdf IIC:PUB:G4:V1.0:PB:20160926>' '3.4 RELIABILITY' 'Page 18' pdf Page 19 Page 18 pdf Page 19 Page 18 IIRA Resilience pdf Page 20 Page 19 pdf Page 19 Page 18 pdf Page 19 Page 18 pdf Page 20 Page 19 IIRA Safety pdf Page 18 Page 17 pdf Page 18 Page 17 IIRA Scalability IIRA Security pdf Page 121 Page 11 pdf Page 121 Page 11 IIC Security Framework Publications referred: '<https://www.iiconsortium.org/pdf/IIC_PUB_G4_V1.00_PB-3.pdf IIC:PUB:G4:V1.0:PB:20160926>' pdf Page 121 Page 11 pdf Page 121 Page 11 pdf Page 121 Page 11 pdf Page 121 Page 11 IIRA Usage Viewpoint Publications referred: '(IIC:PUB:G1:V1.80:20170131' '3.5.2 USAGE VIEWPOINT' 'Page 16' pdf Page 25 Page 22 pdf Page 25 Page 22 Industrial Internet Connectivity Framework IICF The Alliance is a global non-profit organization serving the various communities seeking to establish the Internet Protocol as the network for the connection of Smart Objects by providing coordinated marketing efforts available to the general public. (source: https://www.postscapes.com/internet-of-things-protocols/) IPSO System Architect Communication with non-IPv6 networks must be possible (IPv4, others). IPv4 Support IoT-A Requirement UNI.313 IPv6, is an Internet Layer protocol for packet-switched internetworking and provides end-to-end datagram transmission across multiple IP networks. (source: https://www.postscapes.com/internet-of-things-protocols/) IPv6 System Architect A system built using the ARM shall use/support common-addressing-schemes such as IPv6. IPv6 Support IoT-A Requirement UNI.312 ISO/IEC 29115 ISO 50001 ISO 9000 ISO/IEC 9594 X.509 ISO/IEC 9594-8 The Reference Architecture (IVRA) of the Industrial Value Chain Initive (IVI) proposes a system architecture for the manufactoring domain targeting interoperability and communicational aspects. Industrial Value Chain Reference Architecture IVRA The concern how to identify a participant (client, endpoint etc.) in the internet. Identification IoT-A Requirement UNI.030 IoT-A Requirement UNI.425 IoT-A Requirement UNI.428 IoT-A Requirement UNI.622 Publications referred: '<https://doi.org/10.1016/j.jksuci.2016.10.003>' 'Survey on domain specific IoT architectures' 'Page 299' In computer security, identity and access management (IAM) is the security and business discipline that "enables the right individuals to access the right resources at the right times and for the right reasons".It addresses the need to ensure appropriate access to resources across increasingly heterogeneous technology environments and to meet increasingly rigorous compliance requirements. (source: wikipedia) Identity Management IoT-A Requirement UNI.048 IoT-A Requirement UNI.432 pdf Page 17 Page 14 pdf Page 17 Page 14 AII Industrial Internet Architecture Industrial Internet Architecture Version 1 Industrial Internet of Things Volume G4: Security Framework Industrial Internet of Things Volume G4: Security Framework IIC:PUB:G4:V1.0:PB:20160926 Industrial Value Chain Reference Architecture (IVRA) Industrial Value Chain Initiative Industrial Value Chain Reference Architecture (IVRA) Industrial Value Chain Reference Architecture (IVRA)- Next Industrial Value Chain Reference Architecture (IVRA) Industrial Value Chain Initiative Next Information Security The IoT utilizes different sort of object distinguishing proof advancements, e.g., RFID, 2D-standardized tags and so forth. Since each kind of day by day use articles will convey these recognizable proof labels and insert the particular object data, it is important to take legal protection measures and prevent unauthorized access. Information Privacy Device/Service Owner In telecommunications, the term system integrity has the following meanings: 1. * That condition of a system wherein its mandated operational and technical parameters are within the prescribed limits. 2. * The quality of an AIS when it performs its intended function in an unimpaired manner, free from deliberate or inadvertent unauthorized manipulation of the system. 3. * The state that exists when there is complete assurance that under all conditions an IT system is based on the logical correctness and reliability of the operating system, the logical completeness of the hardware and software that implement the protection mechanisms, and data integrity. (source: wikipedia) Integrity protection and verification of the software stack installed; local integrity protection would be something like trusted boot; remote integrity verification means support for remote attestation. Integrity Protection and Verification IoT-A Requirement UNI.066 IoT-A Requirement UNI.603 IoT-A Requirement UNI.620 Attestation The GEs in the I2ND chapter provide three sets of functionalities. The first is an advanced integration middleware to be used by all FIWARE GEs with high performance communication needs Open networking elements enable cloud network application developers to build value-added services in private, enterprise and public settings. The third set of functionalities enables the management of robots by means of platform components and interfaces towards other FIWARE GEs, allowing users to develop smarter and faster robotic applications. FIWARE Interface to Networks and Devices A systems ability to connect with other systems. Interoperability refers to the ability of two or more devices from the same vendor, or different vendors, to exchange information and use that information for correct co-operation [IEC61850-2010]. Interoperability IoT-A Requirement UNI.008 IoT-A Requirement UNI.010 IoT-A Requirement UNI.023 IoT-A Requirement UNI.042 IoT-A Requirement UNI.047 IoT-A Requirement UNI.093 IoT-A Requirement UNI.094 IoT-A Requirement UNI.232 IoT-A Requirement UNI.712 Internet of Things The internet of things (IoT) is the internetworking of physical devices, vehicles (also referred to as "connected devices" and "smart devices"), buildings and other items—embedded with electronics, software, sensors, actuators, and network connectivity that enable these objects to collect and exchange data. (source: wikipedia) IoT IoT-A Requirement UNI.213 IoT Architecture After much discussion about the core concepts of the IoT for several years, in 2009 a group of researchers from more than 20 large industrial companies and research institutions joined forces to lay the foundation for the much needed common ground or a common “architecture” for the Internet of Things: the IoTArchitecture project (IoT-A) was born. IoT-A has become the European Commission’s flagship project in the European Union’s Seventh Framework Program for Research and Development with respect to establishing an architecture for the Internet of Things. IoT-A IoTivity is an open source project hosted by the Linux Foundation, and sponsored by the OIC. (source: https://www.postscapes.com/internet-of-things-protocols/) IoTivity IoT-A Availability and Resilience pdf Page 156 Page 155 pdf Page 156 Page 155 IoT-A Deployment and Operation pdf Page 149 Page 141 pdf Page 149 Page 141 IoT-A Evolution and Interoperability pdf Page 151 Page 150 pdf Page 151 Page 150 IoT-A Functional Viewpoint pdf Page 126 Page 105 pdf Page 126 Page 105 One of the main purposes of connected and smart objects in the IoT is the exchange of information between each other and also with external systems. Therefore the way how to define, structure, store, process, manage and exchange information is very important. The information view helps to generate an overview about static information structure and dynamic information flow. (source: Bassi et al.: Enabling Things to Talk) IoT-A Information Viewpoint pdf Page 141 Page 126 pdf Page 141 Page 126 IoT-A Performance and Scalability pdf Page 152 Page 151 pdf Page 152 Page 151 pdf Page 156 Page 149 pdf Page 156 Page 149 IoT-A Reference Architecture pdf Page 482 Page 1 pdf Page 482 Page 1 IoT-A Trust Security and Privacy pdf Page 155 Page 152 pdf Page 155 Page 152 IPSO Application Framework (PDF): This design defines sets of REST interfaces that may be used by a smart object to represent its available resources, interact with other smart objects and backend services. This framework is designed to be complementary to existing Web profiles including SEP2 and oBIX. (source: https://www.postscapes.com/internet-of-things-protocols/) IPSO App Framework Industrial Value Chain Initiative The Industrial Value Chain Initiative (IVI) is a forum to design a new society by combining manufacturing and information technologies, and for all enterprises to take an initiative collaboratively. IVI The activity layer has a view point of activities actually conducted at various places in manufacturers. People and machines acting voluntarily, human activity, machine processes, and information as an object og such activities and processes are brought up for discussion. In every production site of every manufacturer, concrete manufacturing activities are conducted in a different way. (source: IVRA-Next) IVI Activity Layer pdf Page 5 Page 4 pdf Page 6 Page 5 IVI Activity View pdf Page 3 Page 2 pdf Page 4 Page 2 IVI Asset View pdf Page 2 Page 1 pdf Page 2 Page 1 In the business layer, from a perspective of enterprise management, the focus of discussions is placed on the fundamentel structure of manufacturing, organization forms for manufacturing, presence of essential perspectives and axes as well as a philosophy and concept of values underpinning the big picture. (source: IVRA-Next) IVI Business Layer pdf Page 5 Page 4 pdf Page 6 Page 5 IVI Management View pdf Page 4 Page 3 pdf Page 4 Page 3 In the specification layer, the following will be considered: Specific operations based on human activities and machine processes and the things and information items that are their subjects, as well as the data and their attributes that are the subject of the processes executed by logic in software. (source: IVRA-Next) IVI Specification Layer pdf Page 5 Page 4 pdf Page 6 Page 5 JMS (Java Message Service) - A Java Message Oriented Middleware (MOM) API for sending messages between two or more clients. (source: https://www.postscapes.com/internet-of-things-protocols/) JMS It is often challenging to alter resources, for example, the server or data centres to a particular geographic area. Load balancing service provider of the cloud, the availability of the network, or the performance of the data centre are few factors that determine where the data is stored. Accordingly, an organization data might be stored in a different location with various legal jurisdictions and diverse laws concerning the security issues, such as the protection and interruptions of the data Jurisdictional Issues Latency is a time interval between the stimulation and response, or, from a more general point of view, a time delay between the cause and the effect of some physical change in the system being observed. LatencyReduction 6LoWPAN is an acronym of IPv6 over Low power Wireless Personal Area Networks. It is an adaption layer for IPv6 over IEEE802.15.4 links. This protocol operates only in the 2.4 GHz frequency range with 250 kbps transfer rate. (source: https://www.postscapes.com/internet-of-things-protocols/) 6LoWPAN Describes the means by which local data is protected. Local Data Confidentiality The process of recording incidents and events regarding a specific service, data resource or device in order to make status changes transparent. Logging IoT-A Requirement UNI.409 IoT-A Requirement UNI.710 The provider should not go broke, be financially in a close-fitting corner or close down the business. Organizations should be sure and know how to move your data to another cloud provider. And should know how to have a backup at another public cloud of data for redundancy Long Term Business Sustainability Machine learning is the subfield of computer science that "gives computers the ability to learn without being explicitly programmed" (Arthur Samuel, 1959). Evolved from the study of pattern recognition and computational learning theory in artificial intelligence, machine learning explores the study and construction of algorithms that can learn from and make predictions on data – such algorithms overcome following strictly static program instructions by making data-driven predictions or decisions, through building a model from sample inputs. (source: wikipedia) Machine Learning The ability of a system to be maintained. Maintenance Cost Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '3 Use Cases for Fog' 'Page 13' Publications referred: 'IIC:PUB:G1:V1.80:20170131' '4 BUSINESS VIEWPOINT' 'Page 20' Message precedence is an indicator attached to a message indicating its level of urgency. (source: wikipedia) Message precedence IoT-A Requirement UNI.028 How to handle the massive mobility of vehicles? In the case of an application scenario that involves connected vehicles, mobility is a major issue and includes data consumer as well as data producer. In this particular case, one of the influencing factors is the potential speed of a vehicle. High-speed mobility may lead to situations in which a request for data or a service may not be answered before the vehicle disconnects and re-connects to another network entry point. This leads to unfulfilled requests and potential duplication of efforts. Mobil Devices Muhammad Usman Data Artefacts are received by 1 to m Data Consumer. Multilateralism Cardinality of Participants Multicast Devices must be able to switch between different networks without losing connections (Network handover/handoff support). Multiple Identities UNI.320 Next Generation Service Interface The FIWARE NGSI (Next Generation Service Interface) API defines - a data model for context information, based on a simple information model using the notion of context entities - a context data interface for exchanging information by means of query, subscription, and update operations - a context availability interface for exchanging information on how to obtain context information (whether to separate the two interfaces is currently under discussion). NGSI Network performance refers to measures of service quality of a network as seen by the customer. There are many different ways to measure the performance of a network, as each network is different in nature and design. (source: wikidata) Network performance IoT-A Requirement UNI.252 Data flow is an integral part of any cloud service over the network of computers or clusters of systems using internet. Any intruder can analyze the data packet to detect any weakness in the system and can gain access to applications and data using some kind of remote access mechanism and injection like SQL and some bad command, Denial of Service (DoS), Distributed DoS (DDoS), man in the middle attacks, social networking attacks and some unauthorized attacks are the major entrance level attacks in cloud computing environment. network security The system shall support network virtualisation, i.e. the usage of virtual overlay networks. Network Virtualization UNI.328 IoT-A Requirement UNI.328 NGSI-LD API Operation NGSI-LD Architecture NGSI-LD Data Representation The FIWARE data models have been harmonized to enable data portability for different applications including, but not limited, to Smart Cities. They are intended to be used together with FIWARE NGSI version 2. If you want to contribute and create additional data models, please have a look at our repository of data models and the data model development guidelines. (source: https://www.fiware.org/developers/data-models/) NGSI-LD Information Model In digital security, non-repudiation means: (a) A service that provides proof of the integrity and origin of data. (b) An authentication that can be said to be genuine with high confidence. The most common method of verifying the digital origin of data is through digital certificates, a form of public key infrastructure that includes digital signatures. Non-repudiation IoT-A Requirement UNI.619 The Open Digital Rights Language (ODRL) is a policy expression language that provides a flexible and interoperable information model, vocabulary, and encoding mechanisms for representing statements about the usage of content and services. The ODRL Information Model describes the underlying concepts, entities, and relationships that form the foundational basis for the semantics of the ODRL policies. Policies are used to represent permitted and prohibited actions over a certain asset, as well as the obligations required to be meet by stakeholders. In addition, policies may be limited by constraints (e.g., temporal or spatial constraints) and duties (e.g. payments) may be imposed on permissions. ODRL Open Digital Rights Language The agility pillar addresses business operational decisions for an OpenFog RA deployment. It is not possible for humans alone to analyze the data generated at the scale predicted by IoT as the basis for rapid, sound business and operational decisions. The agility pillar focuses on transforming this volume of data into actionable insights. Agility also deals with the highly dynamic nature of fog deployments and the need to respond quickly to change. source: OpenFog Reference Architecture OpenFog Agility Pillar Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.7 Agility Pillar' 'Page 31' pdf Page 32 Page 31 pdf Page 32 Page 31 The autonomy pillar enables fog nodes to continue to deliver the designed functionality in the face of the external service failures. In this architecture, autonomy is supported throughout the hierarchy. Decision making will be made at all levels of a deployment’s hierarchy including near the device or higher order layers. Centralized decision-making in the cloud is no longer the only option. Autonomy at the network edge means intelligence from local devices and peer data can be used to fulfill the business’ mission at the point where it makes the most business sense. OpenFog AutonomyPillar Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.4 Autonomy Pillar' 'Page 27' pdf Page 29 Page 27 pdf Page 29 Page 27 OpenFog Data Analytics and Control Perspective pdf Page 56 Page 54 pdf Page 56 Page 54 How fog software and fog systems are deployed to address a given scenario is also very important. There are many deployment types ranging from embedded to large clustered systems that are fully interconnected. The deployment type(s) chosen are scenario specific, but key aspects of the architecture remain visible regardless of deployment type. However, some may grow or shrink in importance. source: OpenFog Reference Architecture OpenFog Deployment Viewpoint pdf Page 40 Page 39 pdf Page 40 Page 39 The functional viewpoint of the architecture shows how we apply the OpenFog architectural elements and views to address the various concerns of the stakeholders to satisfy a given scenario. Each scenario chosen will focus on a different aspects and market opportunities for fog computing. We fully expect that the architectural description, views, and perspective may change over time. This change and refinement should be driven from testbeds and application of the OpenFog RA to multiple different markets we see as important to fog computing. source: OpenFog Reference Architecture OpenFog Functional Viewpoint pdf Page 39 Page 38 pdf Page 39 Page 38 OpenFog RA computing resources can be seen as a logical hierarchy based on the functional requirements of an end-to-end IoT system. Depending on the scale and nature of the scenario being addressed, the hierarchy may be a network of smart and connected partitioned systems arranged in physical or logical layers, or it may collapse into a single physical system (scalability pillar). source: OpenFog Reference Architecture OpenFog Hierarchy Pillar Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.8 Hierarchy Pillar' 'Page 31' pdf Page 34 Page 31 pdf Page 34 Page 31 Fog applications and services should have the flexibility to span and interoperate with various levels in a fog hierarchy. This is a foundational aspect of fog computing that enables a multi-vendor ecosystem. In addition, the data that is collected or generated by one fog node should be shareable with other nodes in the hierarchy. The figure below shows a cross-fog application spanning east to west nodes (it would also be able to span north to south). source: OpenFog Reference Architecture OpenFog IT Business and Cross-fog Applications Perspective pdf Page 57 Page 56 pdf Page 57 Page 56 Many fog computing deployments involve machine vision, and associated human-like functions. As such, they have the ability to see, respond, remember, move, and make autonomous decisions in order to participate in other fog services. This range of actions requires a higher level of manageability than a traditional static model. In addition, fog nodes may be deployed in a wide range of locations: remote, fixed and non-fixed, and environmentally harsh conditions. source: OpenFog Reference Architecture OpenFog Manageability Perspective pdf Page 54 Page 51 pdf Page 54 Page 51 The node view is the lowest level view we currently utilize in the architectural description. The stakeholders involved in formulating the viewpoint (and subsequently this view) are the system on a chip designers, silicon manufacturers, firmware architects, and system architects. source: OpenFog Reference Architecture OpenFog Node View pdf Page 73 Page 56 pdf Page 73 Page 56 Openness is essential for the success of a ubiquitous fog computing ecosystem for IoT platforms and applications. Proprietary or single vendor solutions can result in limited supplier diversity, which can have a negative impact on system cost, quality and innovation. The openness pillar importance is highlighted in our desire for fully interoperable systems, supported by a vibrant supplier ecosystem. source: OpenFog Reference Architecture OpenFog Opennes Pillar Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.3 Openness Pillar' 'Page 26' pdf Page 27 Page 26 pdf Page 27 Page 26 Performance and Scale Perspective pdf Page 47 Page 46 pdf Page 47 Page 46 The programmability pillar enables highly adaptive deployments including support for programming at the software and hardware layers. This means that re-tasking a fog node or cluster of fog nodes for accommodating operational dynamics, can be completely automated. The re-tasking can be done with the help of the fog nodes inherent programmability interfaces which we describe using general purpose compute or accelerator interfaces. source: OpenFog Reference Architecture OpenFog Programmability Pillar Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.5 Programmability Pillar' 'Page 29' pdf Page 30 Page 29 pdf Page 30 Page 29 The scalability pillar addresses the dynamic technical and business needs behind fog deployments. Elastic scalability cuts across all fog computing applications and verticals. The hierarchical properties of fog and its location at logical edges of networks add additional scaling opportunities. source: OpenFog Reference Architecture OpenFog Scalability Pillar Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.2 Scalability Pillar' 'Page 24' pdf Page 26 Page 24 pdf Page 26 Page 24 OpenFog Security Perspective pdf Page 51 Page 47 pdf Page 51 Page 47 Security implementations have many different descriptions and attributes such as privacy, anonymity, integrity, trust, attestation, verification, and measurement. These are key attributes for the OpenFog RA. Achieving the foundational elements for security requires an approach to discover, attest, and verify all smart and connected “things” before trust can be established source: OpenFog Reference Architecture Security in the OpenFog RA is not a one-size-fits-all architecture. Rather, it describes all of the mechanisms that can be applied to make a fog node secure from silicon to software application. Business case, target market, and vertical use case, as well as the location of the node itself, will all create a set of requirements for that node. However, there are certain foundational parts of the architecture, which must be in place in order to build a secure execution environment. source: OpenFog Reference Architecture OpenFog Security Pillar Publications referred: ' <https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.1 Security Pillar' 'Page 23' pdf Page 24 Page 23 pdf Page 24 Page 23 pdf Page 24 Page 23 pdf Page 24 Page 23 OpenFog Software Architecture View The software view of the OpenFog RA is composed of software running on a platform that is comprised of one or more node views coupled with other components to create a system addressing a given scenario. The stakeholders of the software view include the system integrators, software architects, solution designers, and application developers of a fog computing environment. The software running on fog platforms is used to satisfy a given deployment scenario. A robust fog deployment requires that the relationship between a fog node, fog platform, and fog software are seamless. source: OpenFog Reference Architecture pdf Page 89 Page 77 pdf Page 89 Page 77 The system view of the OpenFog RA is composed of one or more node views coupled with other components to create a platform. The stakeholders which typically create these systems to facilitate a fog deployment comprise the concerns of this viewpoint. Subsequently this view is intended to address the concerns of the system architects, hardware OEMs, and platform manufacturers. They also need to understand the Node view such that the systems they create can be deployed to address a given scenario. source: OpenFog Reference Architecture OpenFog System Architecture View pdf Page 78 Page 73 pdf Page 78 Page 73 Reliability, availability, and serviceability (RAS) is resident throughout successful system architectures and, as such, takes on great importance in the OpenFog RA. Hardware, software, and operations are the three main areas of the RAS pillar. source: OpenFog Reference Architecture OpenFog RAS Pillar Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.6 Reliability, Availability, and Serviceability (RAS)Pillar' 'Page 29' pdf Page 31 Page 29 pdf Page 31 Page 29 OMA (Open Mobile Alliance) is the Leading Industry Forum for Developing Market Driven, Interoperable Mobile Service Enablers (source: https://www.postscapes.com/internet-of-things-protocols/) Open Mobile Alliance The motivation of LightweightM2M is to develop a fast deployable client-server specification to provide machine to machine service.<br> LightweightM2M is principly a device management protocol, but it should be designed to be able to extend to meet the requirements of applications. LightweightM2M is not restricted to device management, it should be able transfer service / application data. (source: https://www.postscapes.com/internet-of-things-protocols/) Lightweight M2M v1.0 Data Distribution Service for real-time systems The Data Distribution Service for real-time systems (DDS) is an Object Management Group (OMG) machine-to-machine (sometimes called middleware) standard that aims to enable scalable, real-time, dependable, high-performance and interoperable data exchanges using a publish–subscribe pattern. DDS addresses the needs of applications like financial trading, air-traffic control, smart grid management, and other big data applications. The standard is used in applications such as smartphone operating systems, transportation systems and vehicles, software-defined radio, and by healthcare providers. DDS was promoted for use in the Internet of things. OMG DDS The IoT comprises of a huge number of perception objects that spread over a few geographic zone; it is important to keep the intruder's access to the items that may make physical harm them or may change their operation Objects Safety and Security Ocean Protocol Business Viewpoint Page 41 Page 1 Page 41 Page 1 Ocean Protocol Marketplace Viewpoint Page 27 Page 1 Page 27 Page 1 Ocean is a decentralized protocol and network of artificial intelligence (AI) data/services. It incentivizes for a vast supply of relevant AI data/services. This network helps to power AI data/service marketplaces, as well as public commons data. The heart of Ocean’s network is a new construction: a Curated Proofs Market. CPMs bridge predicted relevance with actual relevance of each AI service, by having curation markets for cryptographic proofs (e.g. proof of data availability). (source: https://oceanprotocol.com/tech-whitepaper.pdf) Ocean Protocol Ocean Protocol is supported by a Singapore based non-profit foundation, whose mandate is to ensure open access to the protocol and platform, provide data governance, encourage the network ecosystem growth and take measures to ensure that the platform becomes ever more decentralized with time. Ocean Protocol Foundation Ocean Protocol System Viewpoint Page 59 Page 1 Page 59 Page 1 Ocean Protocol: A Decentralized Data Exchange Protocol,powered by blockchain technology and a cryptotoken. Business Strategy. Oct 2017 Ocean Protocol: A Decentralized Data Exchange Protocol to Unlock Data for Artificial Intelligence. Reference Marketplace Framework. Feb 2019 Ocean Protocol: A Decentralized Substrate for AI Data & Services . Technical Whitepaper. Apr 2019 OCF Core Framework Page 14 Page 11 OCF Data Models Page 14 Page 11 OCF Framework Page 14 Page 11 OCF L2 Connectivity Page 14 Page 11 OCF Networking Page 14 Page 11 OCF Security Page 14 Page 11 The OpenAPI Specification (originally known as the Swagger Specification) is a specification for machine-readable interface files for describing, producing, consuming, and visualizing RESTful web services. A variety of tools can generate code, documentation and test cases given an interface file. Development of the OpenAPI Specification (OAS) is overseen by the Open API Initiative, an open source collaborative project of the Linux Foundation. (source: wikipedia) OpenAPI The Open Connectivity Foundation (OCF) is an industry group whose stated mission is to develop specification standards, promote a set of interoperability guidelines, and provide a certification program for devices involved in the Internet of Things (IoT). It has become one of the biggest industrial connectivity standards organizations for IoT, including in its membership Samsung Electronics, Intel, Microsoft, Qualcomm and Electrolux. Currently, there are more than 300 member companies. source: wikipedia Open Connectivity Foundation OpenFog Architecture Overview The OpenFog Architecture is a system-level architecture that extends elements of compute, networking and storage across the cloud through to the edge of the network. This approach is particularly suited to IoT systems and accelerates the decision-making velocity. This architecture serves a specific subset of business problems that can’t be successfully implemented using “cloud only” based architectures or relying solely on intelligent edge devices. OpenFog should be thought of as complementary to, and an extension of the traditional cloud based model where implementations of the architecture can reside in multiple layers of a network’s topology. The goal of the OpenFog architecture is to facilitate deployments which highlight interoperability, performance, security, scalability, programmability, reliability, availability, serviceability, and agility. Proprietary or single vendor solutions can result in limited supplier diversity, which can have a negative impact on market adoption, system cost, quality and innovation. OpenFog Architecture Whitepaper The OpenFog Consortium work is done by committees and workgroups focused on specific tasks aligned to our mission. This work includes technical work; influencing standards development through liaisons with other organizations; testbed; promoting innovation and industry interest in fog computing; and industry education. OpenFog Consortium OpenFog Consortium The OpenFog Reference Architecture (OpenFog RA) is intended to help business leaders, software developers, silicon architects, and system designers create and maintain the hardware, software and system elements necessary for fog computing. OpenFog Reference Architecture OpenFog Reference Architecture for Fog Computing ORION Context Broker Performance is completion of a task with application of knowledge, skills and abilities Performance Periodic Communication IoT-A Requirement UNI.005 Physical Connectivity is the concern including all aspects of low-level connectivity and transporting a physical (electrical) signal from A to B. This might be achieved through wired connections (e.g. ethernet) but also wireless (e.g. WIFI). Physical Connectivity Physical Web - The Physical Web enables you to see a list of URLs being broadcast by objects in the environment around you with a Bluetooth Low Energy (BLE) beacon. (source: https://www.postscapes.com/internet-of-things-protocols/) Physical Web Platform Industry 4.0 Plattform Industrie 4.0 Information privacy, or data privacy (or data protection), is the relationship between collection and dissemination of data, technology, the public expectation of privacy, and the legal and political issues surrounding them. Privacy concerns exist wherever personally identifiable information or other sensitive information is collected, stored, used, and finally destroyed or deleted – in digital form or otherwise. Improper or non-existent disclosure control can be the root cause for privacy issues. Data privacy issues can arise in response to information from a wide range of sources, such as: * Healthcare records * Criminal justice investigations and proceedings * Financial institutions and transactions * Biological traits, such as genetic material * Residence and geographic records * Ethnicity * Privacy breach * Location-based service and geolocation * Web surfing behavior or user preferences using persistent cookies. (source: wikipedia) Privacy IoT-A Requirement UNI.423 IoT-A Requirement UNI.424 IoT-A Requirement UNI.606 IoT-A Requirement UNI.623 "Isolation would be another issue at the edge of the network. In mobile OS, if an application fails or crashes, the whole system will usually crash and reboot. Or in a distributed system the shared resource could be managed with different synchronization mechanisms such as a lock or token ring. " Isolation Product Liability Publications referred: '(IIC:PUB:G1:V1.80:20170131' '4 BUSINESS VIEWPOINT' 'Page 20' Product Manager Publications referred: '(IIC:PUB:G1:V1.80:20170131' '3.5.1 BUSINESS VIEWPOINT' 'Page 15' 'Priyanka' In the edge computing, computation is offloaded from the cloud, and the edge nodes are most likely heterogeneous platforms. In this case, the runtime of these nodes differ from each other, and the programmer faces huge difficulties to write an application that may be deployed in the edge computing paradigm. Programmability Publications referred: ' <https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.5 Programmability Pillar' 'Page 29' Data provenance includes the data's origins, what happens to it and where it moves/moved over time. Provenance Tracking IoT-A Requirement UNI.041 IoT-A Requirement UNI.606 While complete anonymity is not feasibe in an IoT scenario, pseudonimity should be supported. Pseudonimity IoT-A Requirement UNI.624 Quality of service (QoS) is the overall performance of a telephony or computer network, particularly the performance seen by the users of the network. To quantitatively measure quality of service, several related aspects of the network service are often considered, such as error rates, bit rate, throughput, transmission delay, availability, jitter, etc. In the field of computer networking and other packet-switched telecommunication networks, quality of service refers to traffic prioritization and resource reservation control mechanisms rather than the achieved service quality. (source: wikipedia) Quality of Service IoT-A Requirement UNI.613 IoT-A Requirement UNI.614 IoT-A Requirement UNI.717 RAMI Asset Layer pdf Page 23 Page 22 pdf Page 23 Page 22 pdf Page 31 Page 30 pdf Page 31 Page 30 RAMI Business Layer pdf Page 21 Page 20 pdf Page 21 Page 20 RAMI Communication Layer pdf Page 22 Page 21 pdf Page 22 Page 21 pdf Page 24 Page 23 pdf Page 24 Page 23 pdf Page 24 Page 23 pdf Page 24 Page 23 pdf Page 24 Page 23 pdf Page 24 Page 23 pdf Page 24 Page 23 pdf Page 24 Page 23 RAMI Functional Layer pdf Page 21 Page 20 pdf Page 21 Page 20 Administration Shell Header find better class assignment pdf Page 31 Page 30 pdf Page 31 Page 30 RAMI Information Layer pdf Page 22 Page 21 pdf Page 22 Page 21 RAMI Integration Layer pdf Page 23 Page 22 pdf Page 23 Page 22 pdf Page 24 Page 23 pdf Page 24 Page 23 pdf Page 24 Page 23 pdf Page 24 Page 23 RAML (RESTful API Modeling Language) - Makes it easy to manage the whole API lifecycle from design to sharing. It's concise - you only write what you need to define - and reusable. (source: https://www.postscapes.com/internet-of-things-protocols/) RAML REST (Representational state transfer) - RESTful HTTP (source: https://www.postscapes.com/internet-of-things-protocols/) REST Requirements for Internet Hosts -- Communication Layers This is one RFC of a pair that defines and discusses the requirements for Internet host software. This RFC covers the communications protocol layers: link layer, IP layer, and transport layer; its companion RFC-1123 covers the application and support protocols. RFC 1122 The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. It is a generic, stateless, protocol which can be used for many tasks beyond its use for hypertext, such as name servers and distributed object management systems, through extension of its request methods, error codes and headers. A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the data being transferred. HTTP/1.1 RFC 2616 HTTP/1.1 This memo describes how to use TLS to secure HTTP connections over the Internet. Current practice is to layer HTTP over SSL (the predecessor to TLS), distinguishing secured traffic from insecure traffic by the use of a different server port. This document documents that practice using TLS. A companion document describes a method for using HTTP/TLS over the same port as normal HTTP [RFC2817]. HTTPS RFC 2818 Lightweight Directory Access Protocol LDAP This document specifies Version 1.2 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications security over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. This document specifies Version 1.2 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications security over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. RFC 5246 This specification describes how to use bearer tokens in HTTP requests to access OAuth 2.0 protected resources. Any party in possession of a bearer token (a "bearer") can use it to get access to the associated resources (without demonstrating possession of a cryptographic key). To prevent misuse, bearer tokens need to be protected from disclosure in storage and in transport. This specification describes how to use bearer tokens in HTTP requests to access OAuth 2.0 protected resources. Any party in possession of a bearer token (a "bearer") can use it to get access to the associated resources (without demonstrating possession of a cryptographic key). To prevent misuse, bearer tokens need to be protected from disclosure in storage and in transport. RFC 6750 OAuth2.0 2014-06-01 The Constrained Application Protocol The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks. The nodes often have 8-bit microcontrollers with small amounts of ROM and RAM, while constrained networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) often have high packet error rates and a typical throughput of 10s of kbit/s. The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation. RFC 7252 CoAP JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted. JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted. JSON Web Token RFC 7519 This specification describes an optimized expression of the semantics of the Hypertext Transfer Protocol (HTTP), referred to as HTTP version 2 (HTTP/2). HTTP/2 enables a more efficient use of network resources and a reduced perception of latency by introducing header field compression and allowing multiple concurrent exchanges on the same connection. It also introduces unsolicited push of representations from servers to clients. This specification is an alternative to, but does not obsolete, the HTTP/1.1 message syntax. HTTP's existing semantics remain unchanged. HTTP/2 RFC 7540 SCIM Use Cases This document provides definitions and an overview of the System for Cross-domain Identity Management (SCIM). It lays out the system's concepts, models and flows, and includes user scenarios, use cases, and requirements. RFC 7642 SCIM Core Schema This document provides a platform neutral schema and extension model for representing users and groups and other resource types in JSON format. This schema is intended for exchange and use with cloud service providers. RFC 7643 SCIM API The System for Cross-Domain Identity Management (SCIM) specification is an HTTP based protocol that makes managing identities in multi domain scenarios easier to support through a standardized service. Examples include but are not limited to enterprise to cloud service providers, and inter-cloud based scenarios. The specification suite seeks to build upon experience with existing schemas and deployments, placing specific emphasis on simplicity of development and integration, while applying existing authentication, authorization, and privacy models. SCIM's intent is to reduce the cost and complexity of user management operations by providing a common user schema, an extension model, and a service protocol defined by this document. RFC 7644 User Datagram Protocol (UDP) In computer networking, the User Datagram Protocol (UDP) is one of the core members of the Internet protocol suite. The protocol was designed by David P. Reed in 1980 and formally defined in RFC 768. With UDP, computer applications can send messages, in this case referred to as datagrams, to other hosts on an Internet Protocol (IP) network. Prior communications are not required in order to set up communication channels or data paths. RFC 768 TRANSMISSION CONTROL PROTOCOL This document describes the DoD Standard Transmission Control Protocol (TCP). There have been nine earlier editions of the ARPA TCP specification on which this standard is based, and the present text draws heavily from them. There have been many contributors to this work both in terms of concepts and in terms of text. This edition clarifies several details and removes the end-of-letter buffer-size adjustments, and redescribes the letter mechanism as a push function. RFC 793 CoAP (Constrained Application Protocol) is an application layer protocol that is intended for use in resource-constrained internet devices, such as WSN nodes. CoAP is designed to easily translate to HTTP for simplified integration with the web, while also meeting specialized requirements such as multicast support, very low overhead, and simplicity. The CoRE group has proposed the following features for CoAP: RESTful protocol design minimizing the complexity of mapping with HTTP, Low header overhead and parsing complexity, URI and content-type support, Support for the discovery of resources provided by known CoAP services. Simple subscription for a resource, and resulting push notifications, Simple caching based on max-age. (source: https://www.postscapes.com/internet-of-things-protocols/) CoAP ROLL / RPL (IPv6 routing for low power/lossy networks) (source: https://www.postscapes.com/internet-of-things-protocols/) ROLL RPMA (Random phase multiple access) A technology communication system employing direct-sequence spread spectrum (DSSS) with multiple access. (source: https://www.postscapes.com/internet-of-things-protocols/) RPMA The user shall be able to control the radio activity of the system. Radio activity control IoT-A Requirement UNI.021 A standard for asynchronous stream processing with non-blocking back pressure on the JVM. (source: https://www.postscapes.com/internet-of-things-protocols/) Reactive Streams In computer science, real-time computing (RTC), or reactive computing describes hardware and software systems subject to a "real-time constraint", for example from event to system response. Real-time programs must guarantee response within specified time constraints, often referred to as "deadlines". Systems of this type whose correctness depends on their temporal aspects as well as their functional aspects. Real-time responses are often understood to be in the order of milliseconds, and sometimes microseconds. Real Time Analytics IoT-A Requirement UNI.020 Organizations are ultimately legally responsible for their process compliance and data security, Even though the data is in a public cloud. Regulatory Compliance In computer networking, a reliable protocol provides reliability properties with respect to the delivery of data to the intended recipient(s), as opposed to an unreliable protocol, which does not provide notifications to the sender as to the delivery of transmitted data. (source: wikipedia) Reliability IoT-A Requirement UNI.065 Publications referred: '<https://www.iiconsortium.org/pdf/IIC_PUB_G4_V1.00_PB-3.pdf IIC:PUB:G4:V1.0:PB:20160926>' Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.6 Reliability, Availability, and Serviceability (RAS)Pillar' 'Page 29' Resilience is the ability to provide and maintain an acceptable level of service in the face of faults and challenges to normal operation.” Threats and challenges for services can range from simple misconfiguration over large scale natural disasters to targeted attacks. As such, network resilience touches a very wide range of topics. In order to increase the resilience of a given communication network, the probable challenges and risks have to be identified and appropriate resilience metrics have to be defined for the service to be protected. (source: wikipedia) Resilience IoT-A Requirement UNI.012 IoT-A Requirement UNI.040 IoT-A Requirement UNI.058 IoT-A Requirement UNI.064 IoT-A Requirement UNI.718 Return On Investment Publications referred: '(IIC:PUB:G1:V1.80:20170131' '4 BUSINESS VIEWPOINT' 'Page 20' Organizations will be generally exposed to a broad range of different risks, by adopting the cloud computing. Managing these risks is very important concern, as the successful implementation of cloud computing relies upon the appropriate managing, reducing, as well as mitigating these risks linked to cloud computing Risk Management The necessity to categorize participants of a network (users or components) by roles according to the contributions they provide and the demands they have. Examples are identity provider, analytics service, data provider etc. Not to be confused with 'role-based access control', which distinguishes users according to their organizational group, e.g. adimistrators, managers, data analysts etc. Role Categorization IETF System for Cross-domain Identity Management (SCIM) 2.0 The System for Cross-domain Identity Management (SCIM) specification is designed to make managing user identities in cloud-based applications and services easier. The specification suite seeks to build upon experience with existing schemas and deployments, placing specific emphasis on simplicity of development and integration, while applying existing authentication, authorization, and privacy models. Its intent is to reduce the cost and complexity of user management operations by providing a common user schema and extension model, as well as binding documents to provide patterns for exchanging this schema using standard protocols. In essence: make it fast, cheap, and easy to move users in to, out of, and around the cloud. SCIM Functional safety (as defined by the IDS) is the ability of a system to prevent physical damage. Safety is the state of being "safe" (from French sauf), the condition of being protected from harm or other non-desirable outcomes. Safety can also refer to the control of recognized hazards in order to achieve an acceptable level of risk. (source: wikipedia) Safety Scalability is the capability of a system, network, or process to handle a growing amount of work, or its potential to be enlarged in order to accommodate that growth. For example, it can refer to the capability of a system to increase its total output under an increased load when resources (typically hardware) are added. An analogous meaning is implied when the word is used in an economic context, where scalability of a company implies that the underlying business model offers the potential for economic growth within the company. Scalability, as a property of systems, is generally difficult to define and in any particular case it is necessary to define the specific requirements for scalability on those dimensions that are deemed important. It is a highly significant issue in electronics systems, databases, routers, and networking. (source: wikipedia) Scalability IoT-A Requirement UNI.026 IoT-A Requirement UNI.234 IoT-A Requirement UNI.511 IoT-A Requirement UNI.711 This concern frames everything necessary to establish and conduct a secure communication channel, which cannot be read, intercepted or altered by a third party. Especially relevant are encrypting techniques. Secure Communication IoT-A Requirement UNI.022 IoT-A Requirement UNI.062 IoT-A Requirement UNI.501 IoT-A Requirement UNI.607 IoT-A Requirement UNI.608 IoT-A Requirement UNI.609 Information security, sometimes shortened to InfoSec, is the practice of defending information from unauthorized access, use, disclosure, disruption, modification, inspection, recording or destruction. It is a general term that can be used regardless of the form the data may take (e.g. electronic, physical). (source: wikipedia) Security IoT-A Requirement UNI.040 IoT-A Requirement UNI.507 IoT-A Requirement UNI.626 IoT-A Requirement UNI.719 Users should be able to monitor and control the security and privacy settings of all the devices that they own. Security Configuration IoT-A Requirement UNI.625 Due to the diversity of cloud computing service suppliers, it is a challenge for organizations to pick am appropriate service supplier. In selection of a cloud provider, organizations ought to look at different elements, like the reputation and size of the company of service supplier, in terms of number of employees, share of the market, as well as their other resources Selection of Service Provider Beyond the ability of two or more computer systems to exchange information, semantic interoperability is the ability to automatically interpret the information exchanged meaningfully and accurately in order to produce useful results as defined by the end users of both systems. To achieve semantic interoperability, both sides must refer to a common information exchange reference model. source: <https://en.wikipedia.org/wiki/Interoperability> Semantic Interoperability IoT-A Requirement UNI.003 IoT-A Requirement UNI.070 IoT-A Requirement UNI.073 IoT-A Requirement UNI.213 IoT-A Requirement UNI.426 IoT-A Requirement UNI.427 Publications referred: '<https://doi.org/10.1016/j.jksuci.2016.10.003>' '3.2. Direction toward Io<*>' 'Page 315' The concern of being able to measure values from a defined environment. Sensing Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.1 THE CONTROL DOMAIN' 'Page 28' Service access control is the selective restriction of access to a specific (web) service or process. The act of accessing may mean consuming, entering, or using. Permission to access a service is called service authorization. Locks and login credentials are two analogous mechanisms of access control. (source: wikipedia) Service Access Control IoT-A Requirement UNI.611 2 to n Data Apps/Services/Data Provider are connected (without a central coordinator) Service choreography is a form of service composition in which the interaction protocol between several partner services is defined from a global perspective.The intuition underlying the notion of service choreography can be summarised as follows: “Dancers dance following a global scenario without a single point of control" That is, at run-time each participant in a service choreography executes its part of it (i.e. its role) according to the behavior of the other participants.A choreography's role specifies the expected messaging behavior of the participants that will play it in terms of the sequencing and timing of the messages that they can consume and produce. (source: wikipedia) Service Choreography IoT-A Requirement UNI.096 IoT-A Requirement UNI.704 2 to n Data Apps/Devices/Services are connected In computing, service composability is a design principle, applied within the service-orientation design paradigm, that encourages the design of services that can be reused in multiple solutions that are themselves made up of composed services. The ability to recompose the service is ideally independent of the size and complexity of the service composition. This principle is directly responsible for the agility promised by SOA as it promotes composing new solutions by reusing existing services. (source: wikipedia) Service Composition IoT-A Requirement UNI.014 IoT-A Requirement UNI.031 IoT-A Requirement UNI.043 IoT-A Requirement UNI.089 IoT-A Requirement UNI.094 IoT-A Requirement UNI.234 IoT-A Requirement UNI.244 IoT-A Requirement UNI.245 IoT-A Requirement UNI.247 IoT-A Requirement UNI.251 IoT-A Requirement UNI.253 Software deployment is all of the activities that make a software system available for use. The general deployment process consists of several interrelated activities with possible transitions between them. These activities can occur at the producer side or at the consumer side or both. Because every software system is unique, the precise processes or procedures within each activity can hardly be defined. Therefore, "deployment" should be interpreted as a general process that has to be customized according to specific requirements or characteristics. (source: wikipedia) Service Deployment IoT-A Requirement UNI.429 A Service Description plays an important role in enabling access to a service. Most service description languages are designed for machine consumption, allowing for the automatic creation of code skeletons, easier search, and classification of services. However, people may also find descriptions useful to learn about the use of parameters or the precise semantics of some operation. (https://www.w3.org/standards/webofservices/description) Service Description IoT-A Requirement UNI.004 IoT-A Requirement UNI.036 IoT-A Requirement UNI.042 IoT-A Requirement UNI.240 IoT-A Requirement UNI.715 How to find desired (Web) services, Data Apps, functionalities. Service Discovery IoT-A Requirement UNI.406 IoT-A Requirement UNI.408 IoT-A Requirement UNI.414 IoT-A Requirement UNI.415 IoT-A Requirement UNI.416 IoT-A Requirement UNI.422 IoT-A Requirement UNI.427 Publications referred: '<https://doi.org/10.1016/j.jksuci.2016.10.003>' '2.8.2. Societal data service' 'Page 309' Service isolation via a process group (as done with Docker) or by least privilege with clear separation and support for additional security modules (as done by trustme). Service Isolation A service-level agreement (SLA) is defined as an official commitment that prevails between a service provider and the customer. Particular aspects of the service – quality, availability, responsibilities – are agreed between the service provider and the service user. The most common component of SLA is that the services should be provided to the customer as agreed upon in the contract. As an example, Internet service providers and telcos will commonly include service level agreements within the terms of their contracts with customers to define the level(s) of service being sold in plain language terms. In this case the SLA will typically have a technical definition in terms of mean time between failures (MTBF), mean time to repair or mean time to recovery (MTTR); identifying which party is responsible for reporting faults or paying fees; responsibility for various data rates; throughput; jitter; or similar measurable details. (source: wikipedia) Service level agreement IoT-A Requirement UNI.060 Information lifecycle management (ILM) refers to strategies for administering storage systems on computing devices. ILM is the practice of applying certain policies to effective information management. This practice had its basis in the management of information in paper or other physical forms (microfilm, negatives, photographs, audio or video recordings and other assets). ILM includes every phase of a "record" from its beginning to its end. And while it is generally applied to information that rises to the classic definition of a record (and thus related to records management), it applies to all informational assets. (source: wikipedia) Service life-cycle management IoT-A Requirement UNI.087 A Service/Data App are connected with Data Provider, other Services/Data Apps in order to fulfill a certain task, orchestrates by a central entity. Service Orchestration IoT-A Requirement UNI.010 Publications referred: '<https://doi.org/10.1016/j.jksuci.2016.10.003>' '2.2.2. Middleware enablement' 'Page 300' The ability of a system to invoke or deploy the desired service/Data App. Service Selection Organizations should make sure that the cloud provider imitates the data and provides services in case the major site is down. Find out the time to restore services and the data loss if any, in case the chief site goes down. Service Recovery Software update is the process that prevents compromise an IoT based system. Organizations are yet to be geared up with mechanisms to Remotely Patch Connected Devices. Software Updates A system shall have a semantic understanding of distance and location. Spatial modeling IoT-A Requirement UNI.098 Copyright © 2016 IEC Geneva, Switzerland. IS Stream processing is a computer programming paradigm, equivalent to dataflow programming, event stream processing, and reactive programming, that allows some applications to more easily exploit a limited form of parallel processing. (source: wikipedia) Stream processing If two or more systems are capable of communicating with each other, they exhibit syntactic interoperability when using specified data formats and communication protocols. XML or SQL standards are among the tools of syntactic interoperability. This is also true for lower-level data formats, such as ensuring alphabetical characters are stored in a same variation of ASCII or a Unicode format (for English or international text) in all the communicating systems. source: <https://en.wikipedia.org/wiki/Interoperability> Syntactic Interoperability UNI.327 IoT-A Requirement UNI.071 IoT-A Requirement UNI.096 IoT-A Requirement UNI.241 IoT-A Requirement UNI.318 IoT-A Requirement UNI.326 IoT-A Requirement UNI.327 IoT-A Requirement UNI.506 IoT-A Requirement UNI.709 Publications referred: '<https://doi.org/10.1016/j.jksuci.2016.10.003>' '2.8.2. Societal data service' 'Page 308' System Engineer Publications referred: '(IIC:PUB:G1:V1.80:20170131' '3.5.1 BUSINESS VIEWPOINT' 'Page 15' 'Priyanka' Software evolution is the term used in software engineering (specifically software maintenance) to refer to the process of developing software initially, then repeatedly updating it for various reasons. (source: wikipedia) System evolution IoT-A Requirement UNI.211 IoT-A Requirement UNI.229 System Recovery http://www.iec.ch TR http://www.iec.ch TS Industrial Internet Architecture Version 1 The Industrial Internet of Things Volume G1: Reference Architecture IIC:PUB:G1:V1.80:20170131 The Industrial Internet of Things Volume G5: Connectivity Framework The Industrial Internet of Things Volume G5: Connectivity Framework IIC:PUB:G5:V1.0:PB:20170228 'Things' in terms of physical objects in the IoT need to be described in order to identify them and to provide further information. Thing description IoT-A Requirement UNI.036 IoT-A Requirement UNI.042 IoT-A Requirement UNI.213 IoT-A Requirement UNI.237 IoT-A Requirement UNI.240 IoT-A Requirement UNI.404 IoT-A Requirement UNI.509 IoT-A Requirement UNI.512 A Thing in terms of Internet of Things (IoT) needs to be moveable. Thing mobility IoT-A Requirement UNI.050 IoT-A Requirement UNI.233 Physical objects need to be represented. Thing representation IoT-A Requirement UNI.239 Synchronization refers to one of two distinct but related concepts: synchronization of processes, and synchronization of data. Process synchronization refers to the idea that multiple processes are to join up or handshake at a certain point, in order to reach an agreement or commit to a certain sequence of action. Data synchronization refers to the idea of keeping multiple copies of a dataset in coherence with one another, or to maintain data integrity. Process synchronization primitives are commonly used to implement data synchronization. (sourc: wikipedia) Time Synchronization IoT-A Requirement UNI.089 The advent of the Industrial Internet of Things (IIoT) also raises challenges with respect to security and privacy of sensitive and personal data that is created by sensors and processed by services hosted in different administrative domains. The Industrial Data Space initiative addresses these challenges and proposes a secure edge gateway platform named "Trusted Connector". In this report, we introduce the main security building blocks of the Trusted Connector and point out how they help protecting business-critical data and preserving the user's privacy. IDS Trusted Connector Trustworthiness is the degree of confidence one has that the system performs as expected in respect to all the key system characteristics in the face of environmental disruptions, human errors, system faults and attacks. source: IISF Trustworthiness IoT-A Requirement UNI.062 IoT-A Requirement UNI.602 IoT-A Requirement UNI.613 one-to-one connectivity Unicast IoT-A Requirement UNI.301 IoT-A Requirement UNI.304 Developer System Architect Productive systems must inherently cover issues caused by unreliable networks. Unreliable Network IoT-A Requirement UNI.308 IoT-A Requirement UNI.318 Interaction design, often abbreviated as IxD, is defined as "the practice of designing interactive digital products, environments, systems, and services." While the digital side of this statement is true, Interaction design is also valid when creating physical (non-digital) products, covering the ideology of how a user may interact with it. (source: wikipedia) User Interaction IoT-A Requirement UNI.019 IoT-A Requirement UNI.092 IoT-A Requirement UNI.214 IoT-A Requirement UNI.252 Users can have the possibility to prefer one service over another for any reason. User Preferences IoT-A Requirement UNI.253 There is a lot of competition among vendors to dominate the cloud market. According to Columbus’ report, a study conducted by IDG Cloud Computing Study realized that Cloud investment rose by 19% in larger scale enterprises consisting of more than a thousand employees who spend a mean of $3.3 million annually. Vendor Lockin Entities are provided through a virtual form. Virtual Entity UNI.030 UNI.066 UNI.402 Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.1 THE CONTROL DOMAIN' 'Page 28' X-Road Architecture Technical Specification Version: 1.0 18.09.2015 15 pages Doc. ID: ARC-G iSHARE is a uniform set of agreements or a scheme for identification, authentication and authorization. All companies that join the iSHARE Scheme comply with the set of agreements. They all use the same methods to both provide and gain access to data. (source: iShare: 'It is not a platform…') iShare It is a guide intended for those who want to acquaint themselves more thoroughly with the X-tee (e.g. theose who are working for an organisation which will soon join the X-tee). It introduces the X-tee’s complex terminological system slowly and in a comprehensible way, so that the reader can painlessly achieve the preliminary familiarity with the X-tee necessary to engage with more explicitly technical and complex manuals. (source: https://www.ria.ee/en/state-information-system/x-tee/introduction-x-tee.html) Introduction of X-tee x-road x-road Deplyoment View Page 16 Page 15 x-road Protocols and Interfaces Page 14 Page 10 x-road System Components Page 10 Page 7 x-road Technology Matrix Page 15 Page 14 x-Tee TODO: model IDS concepts correctly Trusted Connector Examples of a Creator include a person, an organization, or a service. 2008-01-14 2010-10-11 An entity primarily responsible for making the resource. Creator 2000-07-11 2008-01-14 Date on which the resource was changed. Date Modified 2008-01-14 2010-10-11 A name given to the resource. Title A Stakeholder Group is a party of people who have common interests and concerns. A stakeholder is everyone with an interest in a system. Stakeholder Group Stakeholders are interpreted in the same manner as outlined by ISO 42010: '<system> individual, team, organization, or classes thereof, having an interest in a system' Family Name mbox name IoT-A Requirement UNI.247 sebastian The BDV Reference Model distinguishes between two different elements. On the one hand, it describes the elements that are at the core of the BDVA; on the other, it outlines the features that are developed in strong collaboration with related European activities. The BDV Reference Model is structured into horizontal and vertical concerns. Horizontal concerns cover specific aspects along the data processing Vertical concerns address cross-cutting issues, which may affect all the horizontal concerns. In addition, vertical concerns may also involve non-technical aspects. The BDV Reference Model distinguishes between two different elements. On the one hand, it describes the elements that are at the core of the BDVA; on the other, it outlines the features that are developed in strong collaboration with related European activities. The BDV Reference Model is structured into horizontal and vertical concerns. Horizontal concerns cover specific aspects along the data processing Vertical concerns address cross-cutting issues, which may affect all the horizontal concerns. In addition, vertical concerns may also involve non-technical aspects. The BDV Reference Model distinguishes between two different elements. On the one hand, it describes the elements that are at the core of the BDVA; on the other, it outlines the features that are developed in strong collaboration with related European activities. The BDV Reference Model is structured into horizontal and vertical concerns. Horizontal concerns cover specific aspects along the data processing Vertical concerns address cross-cutting issues, which may affect all the horizontal concerns. In addition, vertical concerns may also involve non-technical aspects. BDVA Concern A business manager is responsible for the running of the business and to make large profits. Business Manager IIC:PUB:G1:V1.80:20170131 Publications referred: 'IIC:PUB:G1:V1.80:20170131' '1.5 AUDIENCE' 'Page 7' A concern regards a specific challenge or topic as defined by ISO42010. Each concern should at least be regarded by one view of an architecture. Concern IoT-A Requirement UNI.097 This class frames all organizations with the main intend to create, specify and implement a data sharing concept with according interfaces, components, data descriptions, and retrieval algorithms. Data Sharing Initiative sebastian Following is a description of the Reference Architecture linked to the different chapters of FIWARE. A description of FIWARE Generic Enablers (GEs) being supported in each chapter is provided, including the high-level description of the APIs that each FIWARE Generic Enabler (GE) exposes to application developers or it uses to connect to another FIWARE GEs. Fiware Chapter IoT-A Requirement UNI.401 Often these enabling functions, the so-called crosscutting functions, need to be made available across many of the system functional components. For Reference Architecture 6: Functional Viewpoint example, system functions need to be connected so they can interact with each other to complete functionality at the system level. IIRA Crosscutting Function Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.6 CROSSCUTTING FUNCTIONS AND SYSTEM CHARACTERISTICS' 'Page 34' IIRA Functional Domain IIRA System Characteristic An IT manager is responsible for the functioning of the IT services of an organisation. IT Manager IIC:PUB:G1:V1.80:20170131 Publications referred: 'IIC:PUB:G1:V1.80:20170131' '1.5 AUDIENCE' 'Page 7' IDS RAM Perspective Connectivity Layer of the Internet Connectivity Framework Connectivity Layer IICF Connectivity Layer IoT-A Perspective IoT-A Requirement UNI.302 IoT-A Requirement UNI.303 IoT-A Requirement UNI.304 IoT-A Requirement UNI.305 IoT-A Requirement UNI.320 A plant manager is responsible for the functioning of a plant/facility. Plant Manager IIC:PUB:G1:V1.80:20170131 Facility Manager Publications referred: 'IIC:PUB:G1:V1.80:20170131' '1.5 AUDIENCE' 'Page 7' IoT-A Requirement UNI.244 A document, established by consensus and approved by a recognized body, that provides, for common and repeated use, rules, guidelines or characteristics for activities or their results, aimed at the achievement of the optimum degree of order in a given context. Standard IoT-A Requirement UNI.311 IoT-A Requirement UNI.312 IoT-A Requirement UNI.313 IoT-A Requirement UNI.315 Specifies that a given Publication is a Technical Report Technical Reports contain collected data of a kind different from that normally published as an International Standard, for example data obtained from a survey carried out among national committees, data of work in other international organizations or data on "the state of the art" in relation to standards of national committees on a particular subject.Technical Reports are entirely informative in nature and shall not contain matter implying that they are normative Technical Report Specifies that a given Publication is a Technical Specification Technical Specifications are often published when the subject under question is still under development or when insufficient consensus for approval of an International Standard is available.Technical Specifications approach International Standards in terms of detail and completeness, but have not yet passed through all approval stages either because consensus has not been reached or because standardization is seen to be premature. Technical Specification IoT-A Requirement UNI.409 The relation declaring that a standard is relevant or targets a certain concern. has Target Concern