ASDF Working Group H. Lee, Ed. Internet-Draft J. Hong Intended status: Standards Track ETRI Expires: 29 August 2025 J-S. Youn Dong-eui Univ Y-G. Hong Daejeon University 25 February 2025 Semantic Definition Format (SDF) modeling for Digital Twin draft-lee-asdf-digital-twin-06 Abstract This memo specifies SDF modeling for a digital twin, i.e. a digital twin system, and its interactions. An SDF is a format to describe Things and their associated interactions, and to represent the various kinds of information that is exchanged for these interactions. Therefore, the SDF format can be used to define the behavior of things, i.e. physical objects, and related data and interaction models in a digital twin that contain objects as components. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on 29 August 2025. Copyright Notice Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved. Lee, et al. Expires 29 August 2025 [Page 1] Internet-Draft SDF modeling for digital twin February 2025 This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. SDF structure for digital twin . . . . . . . . . . . . . . . 3 3.1. New Element for digital twin . . . . . . . . . . . . . . 3 3.2. Architecture of Digital Twin . . . . . . . . . . . . . . 5 4. Requirements for digital twin . . . . . . . . . . . . . . . . 6 4.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Data acquisition . . . . . . . . . . . . . . . . . . . . 7 4.3. Data analysis . . . . . . . . . . . . . . . . . . . . . . 7 4.4. Identification . . . . . . . . . . . . . . . . . . . . . 7 4.5. Accuracy . . . . . . . . . . . . . . . . . . . . . . . . 7 4.6. Synchronization . . . . . . . . . . . . . . . . . . . . . 7 5. Procedures for digital twin . . . . . . . . . . . . . . . . . 7 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 8.1. Normative References . . . . . . . . . . . . . . . . . . 8 8.2. Informative References . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 1. Introduction A digital twin is defined as a digital representation of an object of interest and may require different capabilities, for example, synchronization and real-time support, according to the specific domain of application. [Y.4600]. Digital twin help organizations improve important functional objectives, including real-time control, off-line analytics, and predictive maintenance, by modeling and simulating objects in the real world. Therefore, it is important for a digital twin to represent as much real-world information about the object as possible when digitally representing the object. Nowadays, digital twin technologies are applied in various domains including manufacturing, energy, medical, farm, transportation, etc. And a common format is needed to represent the objects in the domains as digital twins. SDF [I-D.ietf-asdf-sdf] can be used for modeling objects as digital twins. Lee, et al. Expires 29 August 2025 [Page 2] Internet-Draft SDF modeling for digital twin February 2025 This document specifies the modeling and guidance on how to use SDF to represent objects as digital twins. 2. Terminology This specification uses the terminology specified in [I-D.ietf-asdf-sdf] in particular "Class Name Keyword", "Object", and "Affordance". The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. 3. SDF structure for digital twin This section describes SDF structure with the new Class Name Keyword, sdfNonAffordance, to represent a thing or an object as a digital twin. 3.1. New Element for digital twin The SDF language uses six Class Name Keywords, and sdfNonAffordance is added as a new Class Name Keyword for digital twin. The information attributes for digital twin are defined in [ISO23247-3]. Some of them, for example characteristics and status, can be described using existing Class Name Keywords. And the others, for example location, can be described using sdfNonAffordance. Lee, et al. Expires 29 August 2025 [Page 3] Internet-Draft SDF modeling for digital twin February 2025 { "info": { "title": "An example of the heater #1 in the boat #007", "version": "2025-01-27", "copyright": "Copyright 2025. All rights reserved.", }, "namespace": { "heater1": "https://example.com/heater1" }, "defaultNamespace": "heater1", "sdfObject": { "boat": { "sdfProperty": { "value": { "description": "The state of the heater #1 in a the boat #007; false for off and true for on.", "type": "boolean" } }, "sdfNonAffordance": { location:{ "wgs84": { "latitude": "35.2988233791372", "longitude": "129.25478376484913", "altitude": "0.0" }, "postal": { "city": "Ulsan", "post-code": "44110", "country": "South Korea" }, "w3w": { "what3words":"toggle.mopped.garages" } } report: { "value": { "description": "On February 24, 2025, the boat #007's heater #1 was on from 9 a.m. to 6 p.m.", "type": "string" } } } } } } Figure 1: An example of SDF for digital twin Lee, et al. Expires 29 August 2025 [Page 4] Internet-Draft SDF modeling for digital twin February 2025 3.2. Architecture of Digital Twin The architecture of a digital twin based on the SDF model is illustrated in Figure 2, , following the guidelines of [ISO23247-3]. The Physical Layer comprises affordance and non-affordance objects. From the real-world objects, only those deemed relevant are selected for representation as digital twins. The Digital Twin Layer is structured into three sublayers: the Device Communication Sublayer, the Digital Twin Sublayer, and the Application Sublayer. The Device Communication Sublayer is responsible for monitoring and collecting data from both affordance and non-affordance objects. This sublayer provides the necessary data to synchronize the physical objects with their digital twin counterparts. The Digital Twin Sublayer ensures synchronization between the affordance and non-affordance objects and their respective digital twins using the data provided by the Device Communication Sublayer. The Application Sublayer presents the synchronized values of the digital twins to users, facilitating informed decision-making. Lee, et al. Expires 29 August 2025 [Page 5] Internet-Draft SDF modeling for digital twin February 2025 +---------------------------------------------+ - - - - - - - - - - - | Application Sublayer | | +----------+ +------+ +--------+ +--------+ | | | Human | | HMI | | Apps | | Peers | | | +----------+ +------+ +--------+ +--------+ | +---------------------------------------------+ | Digital Twin Sublayer | | +----------+ +-------------+ +------------+ | | | Operation| | Application | | Resource | | | | and | | and | | access and | | | |management| | service | |interchange | | | +----------+ +-------------+ +------------+ | | +-----------------------------------------+ | Digital twin Layer | | Digital representation of objects | | | | +-------------+ +----------------+ | | | | | Affordance | | Non-Affordance | | | | | | objects | | objects | | | | | +-------------+ +----------------+ | | | +-----------------------------------------+ | +---------------------------------------------+ | Device Communication Sublayer | | +-------------+ +----------------+ | | | Data | | Object | | | | collection | | control | | | +-------------+ +----------------+ | +---------------------------------------------+ - - - - - - - - - - - | +-------------+ +----------------+ | | | Affordance | | Non-Affordance | | | | objects | | objects | | Physical Layer | +-------------+ +----------------+ | +---------------------------------------------+ - - - - - - - - - - - Figure 2: Basic Architecture of digital twin 4. Requirements for digital twin 4.1. Overview A digital twin is a partial representation of sdfThing or sdfObject that contains attributes such as sdfProperty, sdfAction and sdfEvent[ISO23247-1]. By representing sdfThing as a digital twin, crucial events that require appropriate action can be quickly detected and controlled. The requirements defined in [ISO23247-1] are applied to represent sdfThings and sdfObjects as digital twins. Lee, et al. Expires 29 August 2025 [Page 6] Internet-Draft SDF modeling for digital twin February 2025 4.2. Data acquisition Data related to sdfThing and sdfObject, such as sdfProperty, sdfEvent, and sdfAction, should be collected from IP and non-IP devices. 4.3. Data analysis The collected data needs to be analyzed to understand the state of sdfThing and sdfObject. 4.4. Identification The sdfThings and sdfObjects should contain data that uniquely identifies them as digital twins. 4.5. Accuracy The sdfThings and sdfObjects should be represented as digital twins with appropriate levels of detail and accuracy, depending on the application. 4.6. Synchronization The sdfThings and sdfObjects should be synchronized with their digital twins in real-time as appropriate for the application. Newly added or removed sdfThings and sdfObjects should be recognized and reflected in the digital twin. 5. Procedures for digital twin A procedure for representing sdfThing, as a digital twin in a domain is as follows: * defining a purpose for expressing the observable object, as known as a physical asset or an object of interest, as a digital twin in the domain * organizing data based on the roles of the observable object in the domain * configuring the observable object into the digital twin based on the data for the purposes * interworking with a digital twin of each of other domains in which the observable object performs a different role * synchronizing the observable object and the digital twin Lee, et al. Expires 29 August 2025 [Page 7] Internet-Draft SDF modeling for digital twin February 2025 6. Security Considerations Only authorized users should have the authority to manage sdfThings and sdfObjects. 7. IANA Considerations This document has no IANA actions. 8. References 8.1. Normative References [I-D.ietf-asdf-sdf] Koster, M., Bormann, C., and A. Keränen, "Semantic Definition Format (SDF) for Data and Interactions of Things", Work in Progress, Internet-Draft, draft-ietf- asdf-sdf-21, 19 February 2025, . [I-D.ietf-laari-asdf-relations] Laari, P., "Extended relation information for Semantic Definition Format (SDF)", Work in Progress, Internet- Draft, I-D.ietf-laari-asdf-relations-04, 28 January 2025, . [ISO23247-1] "Automation systems and integration Digital twin framework for manufacturing - Part 1: Overview and general principles, ISO 23247-1.", October 2021, . [ISO23247-3] "Automation systems and integration Digital twin framework for manufacturing - Part 3: Digital representation of manufacturing elements, ISO 23247-3.", October 2021, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . Lee, et al. Expires 29 August 2025 [Page 8] Internet-Draft SDF modeling for digital twin February 2025 [Y.4600] Union, I. T., ""Recommendation ITU-T Y.4600 (2022), Requirements and capabilities of a digital twin system for smart cities.", August 2022. 8.2. Informative References [saref4bldg] Poveda-Villaln, M. and R. Garcia-Castro, "SAREF extension for building", 5 June 2020, . Authors' Addresses Hyunjeong Lee (editor) Electronics and Telecommunications Research Institute 218 Gajeong-ro, Yuseong-gu Daejeon 34129 South Korea Phone: +82 42 860 1213 Email: hjlee294@etri.re.kr Jungha Hong Electronics and Telecommunications Research Institute 218 Gajeong-ro, Yuseong-gu Daejeon 34129 South Korea Phone: +82 42 860 0926 Email: jhong@etri.re.kr Joo-Sang Youn DONG-EUI University 176 Eomgwangno Busan_jin_gu Busan 47340 South Korea Phone: +82 51 890 1993 Email: joosang.youn@gmail.com Lee, et al. Expires 29 August 2025 [Page 9] Internet-Draft SDF modeling for digital twin February 2025 Yong-Geun Hong Daejeon University 62 Daehak-ro, Dong-gu Daejeon 34520 South Korea Phone: +82 42 280 4841 Email: yonggeun.hong@gmail.com Lee, et al. Expires 29 August 2025 [Page 10]