hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2b19cd9d2873d1be8003ecd211dcf476 | 103 828 | 2 References | |
2b19cd9d2873d1be8003ecd211dcf476 | 103 828 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
2b19cd9d2873d1be8003ecd211dcf476 | 103 828 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
2b19cd9d2873d1be8003ecd211dcf476 | 103 828 | 3 Definition of terms, symbols and abbreviations | |
2b19cd9d2873d1be8003ecd211dcf476 | 103 828 | 3.1 Terms | For the purposes of the present document, the following terms apply: Digital Twin (DT): set of virtual information constructs that fully describes a potential or actual physical manufactured product from the micro atomic level to the macro geometrical level ontology: formal specification of a conceptualization used to ... |
2b19cd9d2873d1be8003ecd211dcf476 | 103 828 | 3.2 Symbols | Void. |
2b19cd9d2873d1be8003ecd211dcf476 | 103 828 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AI Artificial Intelligence AMS Administrative Management Service API Application Programming Interface ArcGIS Aeronautical Reconnaissance Coverage Geographic Information System BIM Building Information Models CSIRO Commonwealth Scientific and ... |
2b19cd9d2873d1be8003ecd211dcf476 | 103 828 | 4 Recap of priority gaps | In ETSI TR 103 827 [i.1], it has been identified, through the analysis of the DT landscape with a focus on the urban domain, two priority gaps that, once solved, may enable the modelling of complex DT through the exclusive use of the SAREF suite: 1) to enhance the interoperable communication between entities composing ... |
2b19cd9d2873d1be8003ecd211dcf476 | 103 828 | 5.1 Extending SAREF to enable service modelling | This clause describes how services can be represented in the oneM2M Base ontology and in SAREF. Furthermore, it shows the relationship between service representations in both ontologies. More details about how services are represented in the oneM2M Base Ontology and in SAREF can be found in their respective specificati... |
2b19cd9d2873d1be8003ecd211dcf476 | 103 828 | 5.2 Extending SAREF to enable time series modelling | The second priority gap to fill related to the modelling of time series aiming to equip SAREF (ETSI TS 103 264 [1]) with the appropriate conceptualization to represent the relationships between the data observed within each DT and the timing metadata associated with them. In the present document, it is described the pa... |
2b19cd9d2873d1be8003ecd211dcf476 | 103 828 | 6.1 Introduction | For the entities described in the present document, it is indicated whether they are defined as a SAREF extension or elsewhere by the prefix included before their identifier, i.e. if the element is defined in SAREF4CITY (ETSI TS 103 410-4 [i.8]) the prefix is s4city, whereas if the element is reused from another ontolo... |
2b19cd9d2873d1be8003ecd211dcf476 | 103 828 | 6.2 Digital Twin Victoria | Digital Twin Victoria [i.2] is a program to create a virtual replica of the State of Victoria, Australia. The program supports developing the digital foundations for a future-ready Victoria, employing data to reply to new questions and make better data-led decisions. Their vision is to create Victoria online so that go... |
2b19cd9d2873d1be8003ecd211dcf476 | 103 828 | 6.3 Interoperable Urban Digital Twins | Cities are complex systems where different DTs may be developed for different domains (e.g. mobility, environment, health). This use case motivates the need for semantic interoperability and coordination mechanisms between DTs within a cross-vertical application. ETSI ETSI TS 103 828 V1.1.1 (2024-03) 16 The modelling a... |
2b19cd9d2873d1be8003ecd211dcf476 | 103 828 | 7 Observations | The present document aimed to provide a comprehensive set of guidelines about how the SAREF suite may fill the priority gaps identified in ETSI TR 103 827 [i.1] and how it may be extended and applied concerning the modelling of complex DTs. Such guidelines represent important insights the engineers should follow to mak... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 1 Scope | The present document has several key goals. It aims to design and present a clear blueprint for how Digital Twins (DTs) can be designed and structured, how they work and communicate with respect to both physical and digital entities. The present document relies on the insights and information coming from use cases pres... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 2 References | |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 3 Definition of terms, symbols and abbreviations | |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 3.1 Terms | For the purposes of the present document, the following terms apply: Digital Twin (DT): comprehensive software representation of an individual Physical Object NOTE 1: Denoted also a Physical Twin. NOTE 2: It includes the properties, conditions, relationships, events and behaviour(s) of the real-life object through mode... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 3.2 Symbols | Void. |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AF Augmentation Function API Application Programming Interface CoAP Constrained Application Protocol CPS Cyber-Physical System CPU Central Processing Unit DA Digital Adapter DI Digital Interface DT Digital Twin DTD Digital Twin Description DTM... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 4 Digital Twin Abstraction & Core Functionalities | |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 4.0 Foreword | As previously analysed and presented in ETSI TR 103 844 [i.2] and ETSI TS 103 845 [i.3] DTs stand as dynamic entities at the intersection of the physical and digital domains, encapsulating a spectrum of core functionalities that collectively define their essence and purpose. This clause delves into the profound core fu... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 4.1 Physical Communication | Interacting with the physical world in the realm of the Internet of Things (IoT) presents a multifaceted landscape rife with challenges and complexities that should be navigated in the creation and definition of a Digital Twin. One of the foremost challenges stems from the diverse array of devices and systems comprisin... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 4.2 Digital Communication | Interacting with the digital world presents several challenges and complexities in the creation and definition of a DT architecture, especially concerning their representation for seamless interoperability within the digital ecosystem. A key challenge arises from the heterogeneous nature of digital systems, each employ... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 4.3 Digital Twin Model | The model of a DT shall serve as the foundational element responsible for defining and executing the behaviour of the twin, dictating how it interacts with its physical counterpart and presents its state to the digital world. In essence, the model shall be the driving force behind the digitalization process. It shall p... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 4.4 Digital Twin State | In essence, DTs aim to digitalize and represent their physical counterparts, yet capturing every detail may not always be practical or necessary. A DT should be modelled with specific goals in mind and tailored to its operational context. It should at least encompass essential properties, events, behaviours, and relati... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 4.5 Digitalization Process | The Digitalization Process of a DT, also known as reflection or shadowing, involves multiple steps to ensure an accurate representation of the physical asset's state in the digital realm and enable bidirectional communication between the physical and digital worlds through the DT Model. Figure 7: Involved steps associa... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 4.6 Digital Twin Augmentation | DT augmentation represents the process of enhancing the capabilities and functionality of a DT beyond its basic digital representation of the physical entity. This augmentation should be deeply intertwined with the DT Model, which serves as the blueprint defining the behaviour and characteristics of the DT. The augment... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 4.7 Digital Twin - Digital Representation | Having an interoperable and standard Digital Twin Representation (DTR) on the digital space shall be a fundamental principle in the design of a DT Software Architecture and results crucial for ensuring seamless integration and effective communication between DTs and external digital components such as applications, ser... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 4.8 Life Cycle | In the realm of advanced technologies and intelligent systems, the lifecycle of a DT emerges as a crucial foundational element that should model and represent the different evolution of the DT through its internal phases across its evolution. The possibility to structure and model the life cycle of a DT shall be a fund... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 4.9 Digital Twin Management | Effective management of DT is essential for ensuring their optimal performance, adaptability, and scalability within complex digital ecosystems where multiple twins can be executed, and their behaviour and execution should be managed and potentially orchestrated by authorized entities (e.g. applications, users and plat... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 4.10 Digital Twin Monitoring | Monitoring DT instances should be essential for ensuring optimal performance, reliability, and effectiveness in achieving their intended goal and be aligned with external entities managing and monitoring twins. By collecting and analysing performance metrics from various domains, including networking, software, and ope... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 5 Digital Twin Blueprint Architecture | |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 5.0 Foreword | In this clause, the blueprint architecture of a DT is explored, considering the requirements identified in previous documents and the technical aspects highlighted in the previous clause and schematically illustrated in Figure 14. For instance, imagine a scenario where a manufacturing company wants to implement a Digit... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 5.1 Physical Interface & Physical Adapters | The PI shall stand as a crucial bridge connecting the digital and physical domains within the DT architecture. It shall facilitate seamless communication, interoperability, and adaptability, enabling effective interactions between various physical twins (such as objects, devices, or assets) and their digital counterpar... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 5.2 Digital Twin Model & State | The Digital Twin Model (DTM) shall serve as the foundation for capturing and representing the PT in the digital realm with an appropriate level of abstraction associate to the DT context and the target application and deployment goals. This abstraction should help in focusing on domain-level information rather than tec... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 5.3 Digitalization Management | The process of managing DT digitalization involves the intricate coordination between the physical and digital realms to ensure synchronization and effective communication through the adoption of the Digital Twin Model (DTM) as the reference for shaping and implementing DT behaviour. As anticipated in clause 5.2, the d... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 5.4 Digital Interface & Digital Adapters | On the opposite end of the spectrum from the PI a DT Software architecture shall have another critical component of design denoted as Digital Interface (DI) and in charge of handling in a structured and modular way the communications with the cyber world accordingly to the nature and behaviour of the target twin (as sc... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 5.5 Digital Twin Augmentation Management | Augmentation represents a foundational capability of DTs, serving to amplify the functionalities of their physical counterparts via their digital representations. A DT's Software architecture should support the integration of multiple Augmentation Functions (AFs) to be implemented and executed to integrate within the t... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 5.6 Digital Twin Description | A critical aspect of designing and implementing DT architectures should the precise definition, description, and discoverability of twins within one or multiple deployments. In this context, the definition and support for a Digital Twin Description (DTD) should play a pivotal role in harnessing the full potential of DT... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 5.7 Life Cycle Management | The design and implementation of a DT Software Architecture should include also the definition and characterization of its life cycle. As previously anticipated and introduced in clause 4.8, at least with five states and phases of a DT's life cycle should be identified with respect also to the presented blueprint archi... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 5.8 Management Interface | At the core of DT management and orchestration a Management Interface (MNI) should be present as a fundamental element that empowers administrators and operators to dynamically control, configure, and manage the behaviour of running DT instances throughout their deployments. This interface should be in charge of enabli... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 5.9 Monitoring Interface | At the core of DT design should be taken into account also the Monitoring Interface (MOI), a structural and fundamental element that should provide insight into how DTs operate over time during their cyber-physical lifecycle. This interface should be all about capturing, conveying, and analysing a wealth of data and me... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 6 Digital Twins Adoption & Deployment | |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 6.0 Foreword | DTs, as transformative entities, find varied adoption strategies and deployment architectures based on the specific needs and contexts of different domains [i.10]. This clause explores key aspects of DTs adoption and deployment, shedding light on distributed and centralized approaches, considerations for edge and cloud... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 6.1 Distributed & Centralized Approaches | The adoption of DTs often involves critical decisions regarding the architectural approach. Organizations may opt for distributed or centralized models based on factors such as system complexity, scalability requirements, and data governance. Distributed approaches allow to distribute the computational load across mult... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 6.2 Edge & Cloud Deployments | The deployment landscape for DTs spans a spectrum from edge to cloud environments as illustrated in Figure 24. Edge deployments and Edge DTs [i.8] involve placing computational resources closer to the physical assets, reducing latency and enabling real-time processing. Conversely, cloud deployments leverage the vast co... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 6.3 Cyber-Physical Awareness | The effectiveness of DTs hinges on their ability to seamlessly bridge the cyber and physical realms. Cyber-physical awareness for DTs is the comprehensive understanding and live integration of digital models with their physical counterparts, achieved through continuous monitoring, data analysis, and feedback mechanisms... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 6.4 Digital Twin Monitoring & Management | The operational success of DTs should be based and rely on robust monitoring and management practices, which are crucial for ensuring their reliability, performance, and adaptability in dynamic environments. Monitoring DTs should involves tracking various metrics and indicators to assess their performance, resource uti... |
20b5722501d6dbe93db42bb38eb3dee6 | 103 846 | 6.5 Digital Twin Discoverability | Discovering and accessing DTs instances within a complex ecosystem is crucial for their applicability considering both a local discoverability and a distributed on with respect to the vision of building an ecosystem of DTs as illustrated in Figure 25. Robust discoverability capabilities as supported by [i.7] and [i.12]... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 1 Scope | The present document specifies the definition and communication aspects for Digital Twins (DTs), defining their fundamental characteristics and the requirements for their communications and interoperability, through edge-cloud continuum deployments and with respect to their Physical and Digital Interfaces. The purpose ... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 2 References | |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 3 Definition of terms, symbols and abbreviations | |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 3.1 Terms | For the purposes of the present document, the following terms apply: Digital Twin (DT): comprehensive software representation of an individual Physical Object NOTE 1: Denoted also a Physical Twin. NOTE 2: It includes the properties, conditions, relationships, events and behaviour(s) of the real-life object through mode... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 3.2 Symbols | Void. |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: API Application Programming Interface CDT Composed Digital Twin CoAP Constrained Application Protocol DCA Digital Communication Adapter DCC Digital Communication Channel DT Digital Twin DTD Digital Twin Description HTTP Hypertext Transfer Prot... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 4 Digital Twin Communication Patterns | |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 4.0 Introduction | In the realm of Digital Twins (DTs), communication is the fundamental cyber-physical capability that enables these virtual counterparts to digitalize, interact, and evolve in harmony with their physical counterparts. Clause 4 delves into the most important communication patterns that characterize the functioning of DTs... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 4.1 Physical Interaction | One of the foundational aspects that underpin the functionality of DTs is their ability to seamlessly interact with their physical counterparts. This interaction takes place through the Physical Communication Channel (PCC), a fundamental component that a DT shall include in its design and implementation and that serves... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 4.2 Digital Interaction | In the intricate world of Digital Twins (DTs), the Digital Interaction Pattern emerges as a fundamental component responsible for facilitating communication between the DT and the external digital universe. The Digital Communication Channel (DCC) is one of the core components of a DT instance that enables interoperabil... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 4.3 Digital Twin Replication | As introduced in [i.3], the Replication within the realm of DTs represents a transformative concept, offering the remarkable ability to reproduce and relocate physical objects into diverse environments, both virtually and within digital ecosystems. This dynamic capability essentially for softwarizes physical entities s... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 4.4 Digital Twin Composition | As introduced in [i.3], DT's Composition (or Composability) is a dynamic capability that allows the digitalization and visualization of complex systems as compositions of sub-parts or the amalgamation of individual objects as depicted in Figure 10. Take, for example, a car; it can be perceived as a single entity or as ... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 4.5 Replication & Composition in Cross-Domain Scenarios | Cross-domain communication in DT ecosystems is a pivotal capability that shall be implemented to enable interoperability and collaboration between DTs belonging to different domains or application scenarios. This capability unlocks a wide range of opportunities and applications, facilitating the exchange of information... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 4.6 Cyber-Physical Awareness | In the context of DTs, the possibility to model and monitor over time the cyber-physical relationship between the PT and the DT (denoted also as entanglement in [i.3]) has emerged as a strategic property that should characterize the nature of communication and the fundamental aspect of a DT driven architecture or imple... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 4.7 Edge-to-Cloud Communication | The concept of the Edge-to-Cloud compute continuum involves a distributed architectural pattern that spans from edge devices to cloud infrastructure. This approach is highly relevant to DTs scenarios as it accommodates multiple instances deployed in both edge and cloud environments and more in general in any required d... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 5 Digital Twin Communication Requirements | |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 5.0 Foreword | The upcoming clause 5.1 delves into a comprehensive analysis of the communication requirements that are associated with the design and implementation of a DT. Communication lies at the heart of enabling twins to fulfill their intended functionalities and seamlessly interact within the intricate landscapes of both the p... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 5.1 Digital Twin Communication Flows | As previously anticipated and introduced, in the realm of DTs, communication flows are pivotal for enabling seamless interactions and collaborations within the complex landscapes of both the physical and digital domains. These interaction flows (depicted in Figure 16) can be structured into two primary categories assoc... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 5.2 Physical Communication Requirements | This clause delves into the key requirements for the design, implementation, and deployment of the PCC of a DT. This layer serves as the vital bridge between the DT and the physical world, enabling seamless communication with various physical assets and entities. The main capabilities and requirements that should be ta... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 5.3 Digital Communication Requirements | The DCC of a DT together with its modular structure and the presence of different adapters DCAs serves as a crucial bridge between the twin's core model and the broader digital environment. This layer should meet a set of distinct requirements to ensure effective communication, interoperability, and seamless integratio... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 5.4 Replication Requirements | Replication is a transformative capability within the realm of DTs that allows for the cloning, transformation, and distribution of physical objects and their digital representations across various environments. To effectively harness replication capabilities, certain requirements should be met to ensure the successful... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 5.5 Composition Requirements | In a DT ecosystem, Composition capabilities play a crucial role in creating hierarchical structures, managing DT descriptions, and facilitating communication between DTs. These capabilities extend the scope of DT functionalities and have significant implications for the overall architecture. Figure 22: Composed DT comm... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 5.6 Cyber-Physical Awareness Requirements | Cyber-physical awareness together with structure entanglement monitoring and support central to the successful design, implementation, and deployment of DTs. This clause outlines the key requirements associated with entanglement support and awareness, as well as the capabilities for both direct and indirect communicati... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 5.7 Cross-Domain Communication Requirements | Cross-domain DTs bridge the boundaries between different application domains and enable interoperability and collaboration across diverse contexts. In this context, the DCC and its associated DCAs play a critical role in facilitating seamless communication, data exchange, and interaction among DTs operating in disparat... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 5.8 Edge-to-Cloud Communication Requirements | Edge and Cloud DTs serve as key components of the digital ecosystem, offering distinct advantages and capabilities. For a seamless integration and effective management, synchronization, and communication between Edge and Cloud DTs, careful consideration should be applied with respect to both PCC and DCC together with t... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 6 Digital Twin Description & Interoperability | |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 6.0 Introduction | As previously anticipated and introduced in previous clauses 4 and 5 and taking into account the ever-evolving and challenging landscape of DTs, a fundamental aspect that should be taken into account in the design and implementation of DT oriented architectures and framework is the ability to precisely define, describe... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 6.1 Digital Twin Description Requirements | A DTD is a vital component in the world of DTs, serving as the blueprint structure that defines and represents the essence of a twin. It shall encapsulate various characteristics and attributes that are instrumental in comprehensively describing a DT, enabling seamless interaction, monitoring, and interoperability acro... |
b56bf026b9303900e220ae949b75ca17 | 103 845 | 6.2 Digital Twin Description Discoverability & Requirements | In the context of DTs, effective discoverability of DTDs is crucial for enabling seamless interactions, promoting interoperability, and supporting the deployment of a wide range of applications and digital services across diverse domains. Discoverability, in this context, involves the ability for applications and poten... |
3ca377d4c5751335835aa6befc637a62 | 103 840 | 1 Scope | |
3ca377d4c5751335835aa6befc637a62 | 103 840 | 1.1 Context for the present document | The oneM2M ETSI standard (oneM2M TS-0001 [1]) is now mature: multiple deployments exist all over the world at both experimental and operational levels. The experimental deployments are conducted for multiple reasons: • To evaluate the capabilities of the standard in terms of expressiveness, usability on specific equipm... |
3ca377d4c5751335835aa6befc637a62 | 103 840 | 1.2 Scope of the present document | The present document identifies additional requirements to be potentially submitted to oneM2M in the areas of performance evaluation by means of a MM able to characterize application representation and deployment in the oneM2M standard. The present document is structured as follows: • Clauses 1 to 3 set the scene and p... |
3ca377d4c5751335835aa6befc637a62 | 103 840 | 2 References | |
3ca377d4c5751335835aa6befc637a62 | 103 840 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
3ca377d4c5751335835aa6befc637a62 | 103 840 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
3ca377d4c5751335835aa6befc637a62 | 103 840 | 3 Definition of terms, symbols and abbreviations | |
3ca377d4c5751335835aa6befc637a62 | 103 840 | 3.1 Terms | For the purposes of the present document, the following terms apply: guidelines and good practices: methodological document that gives hints to deploy a oneM2M infrastructure oneM2M Implementations Standard (OIS): list of the implementations of the oneM2M standard oneM2M Numerosity Objects (ONO): scalability of a oneM2... |
3ca377d4c5751335835aa6befc637a62 | 103 840 | 3.2 Symbols | Void. |
3ca377d4c5751335835aa6befc637a62 | 103 840 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in oneM2M TS-0011 [i.1] and the following apply: ACP Access Control Policy ADN Application Dedicated Node AE Application Entity API Application Program Interface BER Bit Error Rate CIN Content INstance CNT Container COAP Constrained Application Protocol ... |
3ca377d4c5751335835aa6befc637a62 | 103 840 | 4 Multi-models For IoT solutions based on oneM2M | |
3ca377d4c5751335835aa6befc637a62 | 103 840 | 4.1 Multi-layer abstraction | A view of a layered IoT system used in the present document is shown in figure 1. This model makes it possible to break down all the physical, hardware, software and human entities involved. Each layer has interactions with the other layers and finally merges to constitute the IoT system and its environment of use. ETS... |
3ca377d4c5751335835aa6befc637a62 | 103 840 | 4.2 Meta Model | The MM on figure 2 integrates and links OASD, OCPD, and OSDD descriptions. Each model is represented by a different color. The root item of an IoT system is represented by the Solution class. This one is connected to one or several "IoT application layer" made of one or multiple applications. Each application runs on h... |
3ca377d4c5751335835aa6befc637a62 | 103 840 | 5.1 Introduction | Key Performance Indicators (KPI) and Key Configuration Parameters (KCP) have been selected and validated by the oneM2M community to express important input of IoT systems and performance requirements. |
3ca377d4c5751335835aa6befc637a62 | 103 840 | 5.2 Key Performance Indicators | This list is naturally not exhaustive, but it will be suitable to be extended according to usage and extension of use cases: • Running time. • Memory space. • Data transfer volume. • Per CRUD Operation: - [Min, Avg, Max, Variance, Std-Dev] Processing Time. - [Min, Avg, Max, Variance, Std-Dev] Persistence Delay. - [Min,... |
3ca377d4c5751335835aa6befc637a62 | 103 840 | 5.3 Key Configuration Parameters | These parameters will be able to measure the impact of key parameters of the IoT application on KPI of the simulation. Those key parameters could be: • Infrastructure Layer aspects: - Total Number of IoT devices. - Number of IoT devices per CSE. - Type of access networks (Rate, Delay, PER, BER). ETSI ETSI TS 103 840 V1... |
3ca377d4c5751335835aa6befc637a62 | 103 840 | 6 oneM2M Application Scenario Descriptor (OASD) | The objective of the OASD model in figure 3 is to represent the behavior of the IoT application. To do so, sensors and actuators are endowed with a behavior modelled by event generation (for the sensors). The policy for the generation of sensor data is based on different distribution profiles i.e. constant (equivalent ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.