Describing a device with a large language model

Abstract

The integration of devices into complex systems should be simplified. For this purpose, a method for automatically describing a device (1) in a specified format is proposed. First, a device description in a proprietary format and an example description in the proprietary format are provided, along with a transformed example description whose content corresponds to the example description in the specified format. The device description in the proprietary format, the example description in the proprietary format, and the transformed example description are input into a large language model (9). The large language model (9) outputs the device description (3) in the specified format.

Description

[0001] The present invention relates to a method for automatically writing a device in a predetermined format. Furthermore, the present invention also relates to a device for automatically writing a device and to a device arrangement comprising a device and an application device on which an application is implemented.

[0002] With an ever-growing number of IoT (Internet of Things) devices, for example, in industry or the energy sector, application developers face the challenge of creating interfaces and communicating with a heterogeneous landscape of different devices and device manufacturers using both open and proprietary protocols. Typical devices in industrial plants include sensors, electromechanical components, communication units, and drives. Common protocols used to facilitate communication between these components include HTTP, JSON, Modbus, XML, and so on.

[0003] In new projects, the effort required to implement protocol adapters for devices creates significant implementation costs and can undermine the overall goal of a solution. For example, an energy management system must read measured values ​​and send setpoints to a variety of devices, such as battery storage systems, inverters, charging stations, and so on.

[0004] The Web of Things approach (cf. Fig. 1) enables streamlined connectivity for applications 2 (apps) with various devices 1 and their specific device-specific connectivity. The devices 1 and their communication interfaces are abstracted by so-called thing descriptions 3 (TDs), which define the properties, actions, and events for an individual device (e.g., reading a temperature measurement, setting an active power setpoint, etc.). The applications 2 therefore no longer have to directly deal with proprietary formats 4 or proprietary protocols, but can instead rely on predefined or standardized protocols and formats.

[0005] Although such an approach solves the connectivity challenge for application developers with respect to applications 2, each device 1 must first be described in a suitable format (thing description). This requires considerable work, as each new device type must be manually integrated into a system with all manufacturer-provided connectivity information (e.g., directly from the manufacturer's manual).

[0006] For solutions without a Web of Things approach, application developers would have to manually implement the connectivity stack (connection table for input and output ports) for each device in the project and configure each device according to the manual. With the Web of Things approach (specifically https: / / www.w3.org / WoT / ), a commissioning engineer would still have to manually fill out a Thing Description 3 from the device's manual, which sometimes contains several hundred properties.

[0007] US 2022 / 0 058 502 A1 discloses a gateway for transforming a description of industrial process equipment into a semantically enriched and graph-based information model for automation purposes.

[0008] WO 2019 / 240743 A1 discloses a system for managing the complete lifecycle of a field device, which utilizes a linked ontology containing information from relevant standards and a rule validation model that verifies a device's conformity to the ontology. A device description is converted into a digital model partially based on the ontology.

[0009] DE 20 2021 106 310 U1 discloses a computer-implemented process module for a modular industrial plant, which comprises a process orchestration layer that, through the interpretation of a module description package, enables the computer-implemented process module to address the computer-implemented process module in the same way as at least one active process module. The active process module is designed to physically influence a process executed by the modular industrial plant.

[0010] Regardless of the grammatical gender of a particular term, persons with male, female or other gender identities are included.

[0011] The object of the present invention is therefore to simplify the integration of a device into a complex system.

[0012] According to the invention, this object is achieved by a method and a device according to the independent claims. Advantageous developments of the invention emerge from the subclaims.

[0013] According to the present invention, a (computer-implemented) method for automatically describing a device in a predetermined format is provided. As mentioned above, the device can be, for example, a measuring device (sensor), an electromechanical element (e.g., a robot arm), a communication device (e.g., transmitter / receiver), a drive (e.g., an electric motor), and the like. The device is to be described automatically, in particular with regard to its connectivity (connection ports). Thus, the description of the device is not done manually, but with the aid of an automated process (e.g., implemented on a computer).

[0014] First, a device description is provided in a proprietary format. The device description concerns the physical parameters of the device, particularly those relating to input and output connections. For example, according to the device description, a current temperature in degrees Celsius is represented using two bytes. Similarly, according to a proprietary format, reactive energy in VAh can be specified using four bytes.

[0015] In addition, an example description in the proprietary format is provided together with a transformed example description whose content corresponds to the example description in the specified format. An example description can relate to any example device, such as a temperature sensor. For the example description, as for the device description above, a description (e.g. "maximum current"), a unit (e.g. A), a byte length (e.g. 2) and, if applicable, other variables such as registers, device version, and the like are provided. A transformed example description with the same content in the specified format (e.g. JSON format) is provided for this example description. Thus, two example descriptions with the same content are provided in two different formats (proprietary format and specified format), from which the format transformation emerges.

[0016] In a next step, the device description in the proprietary format, the example description in the proprietary format, and the transformed example description in the specified format are entered into a large language model (LLM). In addition to these three descriptions as input variables, an instruction is also entered into the large language model as usual, according to which the device description is to be transformed from the proprietary format to the specified format, analogous to the example descriptions. If necessary, additional instructions can also be entered into the large language model.

[0017] The large language model outputs the device description in the specified format. Due to the format transformation defined by the example descriptions, the large language model is able to transform the device description in the proprietary format into a novel device description in the specified format. It is not necessary for the large language model to undergo a lengthy training phase. Instead, the large language model can be used instantly using the example input.

[0018] This advantageously results in a user-friendly approach that leverages a large language model to automatically generate valid object descriptions directly from plant manuals and the like. The proposed approach will significantly reduce commissioning effort. The main advantage of the proposed approach is that the connection of new devices (e.g., during commissioning of an industrial building) can be fully automated. Compared to conventional approaches, this drastically reduces the effort required to commission a new site. With this approach, untapped potential for data-driven use cases, e.g., energy management systems, can be easily tapped to increase energy efficiency, for example.

[0019] In one embodiment, a raw device description is automatically captured, and the device description is automatically extracted and provided in the proprietary format. The raw device description is, for example, an image file scanned from a manual. The capture of the raw device description is thus (semi-)automatic, e.g., using a scanner.

[0020] The current device description is then extracted from the raw device description (e.g., image file) in the proprietary format, e.g., based on automatic text recognition. Providing the device description is thus preceded by an automatic capture process consisting of two automated steps: capturing the raw device description and extracting the device description from it. This advantageously provides a highly automated capture process.

[0021] According to another embodiment, the specified format is a standardized format. The specified format into which the device description is transformed is thus a standardized format. This means that, for example, during commissioning, the developers of corresponding applications can rely on standardized formats for the device descriptions.

[0022] In a further embodiment of the method according to the invention, the device description contains connection data and / or connection data specific to the device. As already indicated above, the device description can thus contain connection data, for example, relating to input or output or relating to registers, ports, and the like. In general, all known physical quantities can be described with the device description.

[0023] According to another embodiment, the device description can be extracted from a manual by the large language model for provision. For example, the entire manual can be available in PDF format. Under certain circumstances, the entire manual is then made available to the large language model. If necessary, a suitable extraction algorithm recognizes a connection table in the manual, which is then extracted and transformed into the specified format.

[0024] In a further embodiment, the device description output by the large language model in the specified format is automatically validated with respect to the specified format. This validation step checks whether the specified or standardized format is adhered to in the device description. This validation can be performed automatically using a validation algorithm.

[0025] According to another embodiment, the device description output by the large language model is validated in the specified format in a validation dialog with a user. This means that a validation interface must be provided that allows the user to check the device description for format and, if necessary, supplement or modify it. This ensures that the automatically generated device description in the specified format is also error-free.

[0026] In a further embodiment, at least one further example description in the proprietary format and one further transformed example description for outputting the device description in the specified format are input into the large language model. This means that the language model receives not just a single example for the format transformation, but at least two examples. This can increase the security of the format transformation.

[0027] According to another embodiment, the device description is output in the specified format in a JSON format. The JSON format is a widely used format for describing connectivity. This allows the device description to be provided in a very common format, making the method more universally applicable.

[0028] In a further embodiment, it is provided that, in addition to the device description in the proprietary format, a user enters one or more instructions into the large language model for outputting the device description in the specified format. Thus, in addition to the device description and the at least two example descriptions, at least one user instruction is entered into the large language model. Such instructions can, for example, relate to the type of parameters that may appear in the device description to be output. Likewise, an instruction can relate to which parameters (names) may not be used. Furthermore, an instruction can also relate to inserting parameters such as maximum or minimum if necessary. Such instructions instruct the large language model precisely how the output should be carried out.

[0029] Thus, a method can be provided for communicating between an application and a device by describing the device in a predefined format according to a method as described above, and for the application to communicate with the device based on the device description in the predefined format. Communication between an application and a device can thus be realized based on a predefined connection protocol rather than a proprietary connection protocol.

[0030] The communication method can further provide for the application to communicate with the device to transmit a value of an operating parameter of the device from the device to the application and / or from the application to the device. In this way, values ​​can be exchanged between the application and the device. For example, an application can read a measured value from a device or an application can configure a device setting on a device.

[0031] The object formulated above can also be achieved according to the invention by a device for automatically describing a device in a predetermined format, comprising a memory device for providing a device description (which describes physical quantities of the device) in a proprietary format and for providing an example description in the proprietary format together with a transformed example description which corresponds in content to the example description in the predetermined format, a processor device on which a large language model is implemented, wherein the device description in the proprietary format, the example description in the proprietary format and the transformed example description can be input from the memory device into the processor device, and wherein the device description in the predetermined format can be output by the processor device using the large language model.

[0032] The advantages and further development possibilities listed above in connection with the method according to the invention also apply mutatis mutandis to the device according to the invention. Accordingly, the method features mentioned can be viewed as functional features of corresponding means or devices of the device.

[0033] Furthermore, according to the invention, a device arrangement can be provided comprising a device, an application device on which an application is implemented, and a device as mentioned above with which the device can be written to in the specified format, enabling communication between the application and the device based on the specified format. The application device can be a computer or a similar computing device.

[0034] The above-mentioned object is further achieved by a computer program product with program code means that cause an electronic computing device to perform a method of the above-mentioned type when the program code means are processed by the electronic computing device. Furthermore, a computer-readable storage medium with at least one computer program product of the above type can be provided.

[0035] For use cases or application situations that may arise during the method and which are not explicitly described here, it may be provided that, in accordance with the method, an error message and / or a request to enter user feedback is issued and / or a default setting and / or a predetermined initial state is set.

[0036] The present invention will now be explained in more detail with reference to the accompanying drawings, in which: Fig. 1 a schematic view of a Web of Things approach to simplifying device connectivity; Fig. 2 is a schematic view of a method example according to the present invention; and Fig. 3 an example of a graphical user interface for creating a device description in a given format.

[0037] The exemplary embodiments described in more detail below represent preferred embodiments of the present invention.

[0038] The following examples are based on descriptions using the Web of Things standard (thing descriptions). However, the present invention can also be implemented using other IoT connectivity approaches.

[0039] According to Fig. 2, a device manual 5 is available for device 1. The device manual 5 can be available, for example, in a spreadsheet format, a PDF format, an HTML format, or the like. In some cases, only a section of the device manual 5 may be available in such a format. In the following, such a section is also referred to as the device manual 5.

[0040] In an optional step of the embodiment of Fig. 2, the extraction 6 of a connection specification from the device manual 5 takes place. Thus, the device manual 5 of a device 1 to be integrated into a system (e.g., a PDF file, an HTML page, an Excel spreadsheet) is used to extract the relevant information for the connectivity of the device 1, preferably in a table format. Alternatively, a large language model (hereinafter referred to as LLM) could be used to query the entire PDF file and find the corresponding table. However, this requires an additional call to the LLM with, if necessary, a predefined set of usable tokens / items.

[0041] Table 1 below shows an example of such a specification. Table 1 may be reproduced in the manual in the format shown. Measurement and state variables Table Register Länge Beschreibung Format Einheit POC1000 5ST3COM 5SL6COM 3072 2 Current temperature FP32 °C x x x 3074 2 Average temperature FP32 °C x x x 3076 2 Actual current L FP32 A - - x 3078 2 Average current L FP32 A - - x 3080 2 Maximum current L FP32 A - - x 3082 2 L-N voltage FP32 V - - x 3084 2 Line frequency FP32 Hz - - x 3086 2 Active power {L} FP32 W - - x 3088 2 Apparent power {L} FP32 VA - - x 3090 2 Total reactive powerQtot {L} FP32 V - - x 3092 2 Power factor {L} FP32 - - x 3094 4 Imported activeenergy FP64 Wh - - x 3098 4 Exported activeenergy FP64 Wh - - x 3102 4 Imported reactiveenergy FP64 varh - - x 3106 4 Exported reactiveenergy FP64 varh - - x 3110 1 Status of the(mounted) U16 - x x

[0042] The displayed table can be an image or already in a table format. Depending on this, conversion to a table format may or may not be necessary. Conversion to a table format can be done either manually, i.e., by copying the content and formatting it with a spreadsheet program such as Excel, or by automatically converting the table using an LLM (e.g., ChatGPT). In the latter case, the LLM converts text input into a table format. The connectivity information can now be extracted from this table and evaluated in the following steps.

[0043] First, a so-called “prompt” for the LLM must be created from the table containing the connectivity information.

[0044] For example, a raw device description with the connection data of device 1 was automatically captured from device manual 5, e.g., as a PDF file (e.g., by scanning). Extraction step 6 extracts the device description with the connection specification from the raw device description. The latter is thus available in a proprietary format.

[0045] Now a prompt for an LLM (e.g. ChatGPT) is created. For this purpose, a processing step 7 in Fig. 2. This generates a portion of the prompt for the LLM 8, which contains information about the device 1 to be integrated. Another portion of the prompt consists of training examples 9.

[0046] For example, a standard prompt consists of a sequence of two training examples, each with the desired output for a corresponding input. The input is defined as a dictionary of the values ​​of a row of the documentation table or device description. No specific column names are required. If the respective name has a meaning, it is processed correctly by the LLM. The output is, for example, a property description in a JSON format.

[0047] In processing step 7, the user has the option of specifying additional instructions, such as general instructions (for example, “all integer variables should be described as floating-point numbers”) or an additional example.

[0048] In a further step, the LLM 9 is called. The prepared prompt, including the device description and one or more training examples 8, is fed to the LLM 9. There may be a restriction regarding the maximum number of input tokens for the LLM 9. Under certain circumstances, the prompt is split if the required device configuration or device description is longer than the maximum possible token size.

[0049] The LLM 9 generates a preliminary thing description 3' from the prompt.

[0050] In an optional validation step 10, the generated preliminary thing description 3' is validated against a standard (e.g., Web of Things), resulting in a validated thing description 3. This validation is performed to generally check the format of the generated thing description. If the LLM 9 does not recognize relevant information in the table, additional context can be added by the user and iterated with the LLM 9 in an optional validation dialog 11. The two optional validation steps 10 and 11 thus result in the validated thing description 3. In principle, validation could, of course, be omitted if the LLM 9 directly outputs the thing description 3.

[0051] In a further optional validation step, the actual connectivity to a real device could be tested.

[0052] The generated object description 3 of device 1 can be used directly by application 2 for the interface to device 1. For example, measured values ​​can be read from device 1 using application 2. Likewise, setting values ​​can now be written to device 1 using the application or application 2 via object description 3.

[0053] To further understand the inventive approach, the inventive method is illustrated using a process for onboarding a single property of a new battery. A standard prompt template for any device is used. The subsequent prompt consists of a multi-line instruction section followed by an "input" section and an "output" section.

[0054] The only valid descriptions for the parameter "type" are "integer", "boolean", "number" and "string".

[0055] The only valid descriptions for the modbus:type parameter in the forms description are integer, boolean, number, and string.

[0056] The only valid names for the parameter “modbus:entity” in the description of “forms” are “coil”, “discreteinput”, “inputregister” and “holdingregister”.

[0057] It is absolutely forbidden to name a parameter 'enum'.

[0058] The parameters 'maximum' and 'minimum' can be added if required.

[0059] The "Input" part is generated from the device description, i.e., the table extracted from the device manual 5. The "Output" part displays the data from the "Input" part in a transformed format, e.g., JSON format. The example with the "Input" and "Output" parts is intended to demonstrate to LLM 9 how the format transformation should take place.

[0060] Based on Fig. 3 now shows how the method according to the invention can be used, for example, with the aid of a simple user interface (GUI).

[0061] The first step involves extracting connectivity information. To do this, a line from a documentation table in a device manual (e.g., copied from a PDF file) is inserted into a text area 12. This represents a raw device description. It is converted into a table 13 below it, which can be evaluated. This table 13 can be referred to as the device description.

[0062] By clicking the button 14 "Generate json," table 13 is converted into a suitable input for the LLM. The LLM 8 is started with the prompt shown above. This creates the thing description. In the example from Fig. 3, a JSON file is created as output or output 15. It is located in the lower part of Fig. 3 can be recognized.

[0063] With the generated battery thing description according to Issue 15, any application (e.g. an energy management system) can directly receive measurements and send setpoints to the device without having to worry about the underlying connection protocol. List of reference symbols 1 device 2 Application 3 Description of things 3' preliminary description of the thing 4 Format 5 Device manual 6 Extraction 7 Processing 8 LLM 9 training examples 10 Validation step 11 Validation dialog 12 Text area 13 Table 14 Button 15th issue

Claims

[1] Method for automatically describing a device (1) in a predetermined format, characterized by - Providing a device description of the device (1) in a proprietary format, - Providing an example description in the proprietary format together with a transformed example description that corresponds in content to the example description in the specified format, - entering the device description in the proprietary format, the example description in the proprietary format and the transformed example description into a large language model (9), - Output of the device description in the specified format (3) by the large language model (9). [2] The method of claim 1, wherein a raw device description is automatically captured and the device description in the proprietary format is automatically extracted (6) and provided from the raw device description. [3] The method of claim 1 or 2, wherein the predetermined format is a standardized format. [4] Method according to one of the preceding claims, wherein the device description contains connection data and / or connection data specific to the device (1). [5] Method according to claim 4, wherein the device description is extracted (6) from a manual (5) by the large language model (9) for providing. [6] Method according to one of the preceding claims, wherein the device description output by the large language model (9) in the predetermined format is automatically validated (10) with respect to the predetermined format. [7] Method according to one of the preceding claims, wherein the device description output by the large language model (9) is validated in the predetermined format in a validation dialogue (11) with a user. [8] Method according to one of the preceding claims, wherein at least one further example description in the proprietary format and a further transformed example description for outputting the device description in the predetermined format is input into the large language model (9). [9] Method according to one of the preceding claims, wherein the output of the device description in the predetermined format is carried out in a JSON format. [10] Method according to one of the preceding claims, wherein, in addition to the device description in the proprietary format, a user enters one or more instructions into the large language model (9) for outputting the device description in the predetermined format (3). [11] Method for communicating an application (2) with a device (1) by describing the device (1) in a predetermined format according to a method according to one of the preceding claims and communicating the application (2) with the device (1) on the basis of the device description in the predetermined format (3). [12] The method of claim 11, wherein communicating the application with the device (1) includes transmitting a value of an operating parameter of the device (1) from the device (1) to the application (2) and / or from the application (2) to the device (1). [13] Device for automatically writing a device (1) in a predetermined format, characterized by - a storage device for providing a device description in a proprietary format and for providing an example description in the proprietary format together with a transformed example description which corresponds in content to the example description in the predetermined format, - a processor device on which a large language model (9) is implemented, wherein - the device description in the proprietary format, the example description in the proprietary format and the transformed example description can be input from the storage device into the processor device, and wherein - the device description can be output by the processor device in the predetermined format (3) by means of the large language model (9). [14] Device arrangement with - a device (1), - an application device on which an application (2) is implemented, - a device according to claim 13, with which the device (1) can be written in the predetermined format, so that - communication between the application (2) and the device (1) is possible on the basis of the specified format. [15] Computer program product with program code means which cause an electronic computing device to carry out a method according to one of claims 1 to 12 when the program code means are processed by the electronic computing device.

Images