Device and method for generating user interface of fieldbus-based automatic control system interlinked with internet of things system

Abstract

An electronic device is disclosed for implementing a user interface from a CFG file containing design information of an automatic control system. The electronic device includes a fieldbus virtual I / O memory that stores input / output information transmitted and received via a fieldbus communication standard connected to an automatic control system; a configuration management unit that derives user interface configuration information based on a CFG (Configuration) file in which the name, address, format, and number of arrays of the input / output information and the relationship between the input / output information and user interface elements are defined; and a user interface connection unit that provides a user interface displayed on a user terminal device based on the user interface configuration information derived from the configuration management unit. The device is configured to implement user interface components and their operational connection relationships using the information in the CFG file.

Description

Technology Field

[0001] The present disclosure relates to a technical field for linking an Automatic Control System and an Internet of Things (IoT) system, and in particular, to an apparatus and method for dynamically generating a user interface of an Automatic Control System linked to an IoT system based on a Fieldbus communication standard, and a Configuration (CFG) file that structures this information into metadata. Background Technology

[0002] Recently, industrial environments across all sectors, including manufacturing, agriculture, and building management, require interoperability with Internet of Things (IoT) systems to improve the efficiency and flexibility of automatic control systems. Automatic control systems generally perform precise control and monitoring by transmitting and receiving data in real time with field devices using fieldbus communication standards (e.g., Modbus, CANopen, Profinet, etc.) through operating devices such as PLCs (Programmable Logic Controllers) or DCSs (Distributed Control Systems).

[0003] However, conventional automatic control systems have closed communication protocols and data structures, and in particular, the input / output data addresses and formats within operating devices vary by device or manufacturer, resulting in the following problems when interoperating with Internet of Things systems.

[0004] The complexity and inefficiency of data integration are cited as major issues when linking automatic control systems with Internet of Things (IoT) systems. For IoT systems to utilize fieldbus-based operational device data, a complex relay process is essential. This involves individually analyzing data address maps and formats that differ by fieldbus communication standards and operational devices, and converting them into IoT communication standards (e.g., MQTT, HTTP, etc.). This process significantly increases development time and costs.

[0005] Furthermore, there are difficulties in building and maintaining the user interface (UI). Previously, whenever the functionality of an operating device changed, the server code or client user interface code of the Internet of Things (IoT) system had to be modified manually. This severely hampered system flexibility, as even minor changes—such as adding I / O modules or modifying configuration values ​​in the automatic control system—caused the recompilation and redeployment of the entire system. The problem to be solved

[0006] The present disclosure was devised to solve the aforementioned conventional problems, and the purpose of the present disclosure is to provide a method for generating a standardized CFG file based on data from an automatic control system and generating a user interface based thereon, so that data from a fieldbus-based automatic control system can be utilized efficiently and flexibly in an Internet of Things environment.

[0007] The problems that the technical concept of the present disclosure aims to solve are not limited to those mentioned above, and other unmentioned problems will be clearly understood by those skilled in the art from the description below. means of solving the problem

[0008] An electronic device for implementing a user interface from a CFG file containing design information of an automatic control system according to one or more embodiments of the present disclosure comprises: a fieldbus virtual input / output memory that stores input / output information transmitted and received via a fieldbus communication standard connected to the automatic control system; a configuration management unit that derives user interface configuration information based on a CFG (Configuration) file in which the name, address, format, and array number of the input / output information and the relationship between the input / output information and user interface elements are defined; and a user interface connection unit that provides a user interface displayed on a user terminal device based on the user interface configuration information derived from the configuration management unit, and is configured to implement user interface components and their operational connection relationships using the information of the CFG file.

[0009] The above configuration management unit may include a data definition unit that defines the name, address, format, and array number of each of the input / output information stored in the fieldbus virtual input / output memory; and a user interface definition unit that defines the relationship between the input / output information and the user interface element.

[0010] The above user interface definition unit may include: a UI information definition unit that defines overall rules for displaying the user interface; a classification information definition unit that defines a hierarchical structure for hierarchically classifying the input / output information; a UI state definition unit that defines the display state of each of the input / output information; a value range definition unit that defines the display unit, display allowable range, and display decimal places of each of the input / output information; and a value definition unit that defines the value to which each of the input / output information is displayed.

[0011] The data definition unit includes an artificial intelligence-based data profiling engine that analyzes the real-time data profile of the input / output information stored in the fieldbus virtual input / output memory to automatically generate and optimize the metadata of the CFG file, and the artificial intelligence-based data profiling engine can define a deadband value and a minimum transmission period based on the rate of change and noise level of the input / output information.

[0012] The above value definition unit may include: a value attribute definition unit that defines a display name and additional description for the input / output information; a data definition linkage unit that links to the name and array index of the data defined by the data definition unit; a classification information definition linkage unit that links to the hierarchical structure defined by the classification information definition unit; a UI state definition linkage unit that defines the state in which the value is displayed by linking to a state variable defined by the UI state definition unit; a value range definition linkage unit that links to the value range definition name defined by the value range definition unit; an enum definition unit that defines the actual numeric code for the value and the label displayed to the user; and a record item definition unit that defines a record code, a record value number, and a record value ratio for record management of the value.

[0013] The electronic device may further include a CFG integrity verification unit that checks in real time whether the format and size information of the data defined in the CFG file matches the binary pattern and byte boundary of the data stored in the fieldbus virtual input / output memory, and performs automatic correction of the CFG file when an error is detected.

[0014] The above user interface connection unit can be linked with a prediction analysis information receiving unit that receives failure prediction and remaining life prediction information regarding the equipment status of the automatic control system, and can dynamically insert control elements and status display elements related to the predicted failure among the data defined in the CFG file into the user interface.

[0015] The electronic device further includes an address translation engine that manages a dual mapping table between the actual memory address of the operating device of the automatic control system and the address of the virtual input / output memory, and when the actual memory address of the operating device changes, the address translation engine can dynamically update the dual mapping table based on memory address change information obtained from the operating device and maintain the address of the virtual input / output memory.

[0016] The electronic device further includes a distributed identity processing unit that performs mutual authentication between the automatic control system and the Internet of Things system using blockchain-based distributed identity technology in communication between the automatic control system and the Internet of Things system, and the distributed identity processing unit can encrypt the creation and modification history of the CFG file and record it on the blockchain.

[0017] The electronic device may further include a location-based user interface determination unit that receives location information of a user terminal device and determines whether the location information is included within a predefined geographical area.

[0018] The above location-based user interface determination unit can dynamically activate or deactivate control authority for a specific facility within the automatic control system and a user interface specialized for the specific facility according to the location of the user terminal device. Effects of the invention

[0019] The apparatus and method for generating an Internet of Things (IoT) linked user interface for a fieldbus-based automatic control system according to the present disclosure solve the problems of complexity and inefficiency associated with the prior art.

[0020] The present disclosure generates a Configuration (CFG) file that defines detailed metadata, such as the characteristics, format, address, and array number of individual input / output information, based on fieldbus input / output information obtained from an operating device of an automatic control system. This CFG file provides a technical advantage by abstracting and standardizing complex and closed data of an automatic control system into a form suitable for an Internet of Things environment, thereby eliminating separate complex coding work for data integration and drastically shortening system construction time, improving development efficiency, and reducing system construction costs.

[0021] Furthermore, the present disclosure improves the flexibility of system maintenance by dynamically and automatically generating a user interface displayed on an Internet of Things system based on the CFG file, thereby allowing the user interface to be automatically updated solely by updating the CFG file even when the input / output of the automatic control system changes.

[0022] In addition, the present disclosure ensures logical consistency of data without physical dependency through fieldbus virtual input / output memory and facilitates interoperability with various Internet of Things systems through the universality of CFG files, thereby improving system compatibility and scalability.

[0023] Furthermore, the present disclosure allows the user interface of a system (or device) to be configured as a text-format file using a CFG file, thereby eliminating the need for a separate process for designing the screen. Additionally, by providing a user interface for the operating device using the CFG, the operation of the operating device's code can be easily verified and errors can be analyzed. Accordingly, information about the operating device can be checked and controlled without separate software, and the user interface can be easily modified. Brief explanation of the drawing

[0024] FIG. 1 is a drawing showing two different preferred embodiments to explain the system of the present disclosure. FIG. 2 is a drawing for explaining the configuration and operation of an electronic device according to one embodiment of the present disclosure. FIG. 3 is a block diagram for explaining the configuration and operation of an electronic device according to one embodiment of the present disclosure. FIG. 4 is a drawing for illustrating a CFG file according to one embodiment of the present disclosure. FIGS. 5a to 5c are drawings for explaining data defined to create a user interface according to one embodiment of the present disclosure. FIG. 6 is a drawing for illustrating a user interface according to one embodiment of the present disclosure. Specific details for implementing the invention

[0025] The embodiments are subject to various modifications and may have various forms; therefore, specific embodiments are illustrated in the drawings and described in detail in the detailed description. However, this is not intended to limit the scope of specific embodiments and should be understood to include various modifications, equivalents, and / or alternatives of the embodiments of the present disclosure. In relation to the description of the drawings, similar reference numerals may be used for similar components.

[0026] In describing the present disclosure, if it is determined that a detailed description of related known functions or configurations could unnecessarily obscure the essence of the present disclosure, such detailed description is omitted.

[0027] Additionally, the following embodiments may be modified in various other forms, and the scope of the technical concept of the present disclosure is not limited to the following embodiments. Rather, these embodiments are provided to make the present disclosure more faithful and complete and to fully convey the technical concept of the present disclosure to those skilled in the art.

[0028] The terms used in this disclosure are used merely to describe specific embodiments and are not intended to limit the scope of the rights. The singular expression includes the plural expression unless the context clearly indicates otherwise.

[0029] In the present disclosure, expressions such as “have,” “may have,” “include,” or “may include” indicate the presence of such features (e.g., numerical values, functions, actions, or components such as parts) and do not exclude the presence of additional features.

[0030] In the present disclosure, expressions such as “A or B,” “at least one of A and / or B,” or “one or more of A and / or B” may include all possible combinations of items listed together. For example, “A or B,” “A and / or B,” “at least one of A and B,” or “at least one of A or B” may refer to cases including (1) at least one A, (2) at least one B, or (3) both at least one A and at least one B.

[0031] Expressions such as "first," "second," "first," or "second" used in this disclosure may modify various components regardless of order and / or importance, and are used only to distinguish one component from another and do not limit said components.

[0032] Where it is stated that a certain component (e.g., a first component) is "(operatively or communicatively) coupled with / to" or "connected to" another component (e.g., a second component), it should be understood that the said certain component may be directly connected to the said other component or connected through another component (e.g., a third component).

[0033] On the other hand, when it is stated that a certain component (e.g., a first component) is "directly connected" or "directly coupled" to another component (e.g., a second component), it may be understood that no other component (e.g., a third component) exists between said certain component and said other component.

[0034] As used in this disclosure, the expression “configured to” may be replaced, depending on the context, with, for example, “suitable for,” “having the capacity to,” “designed to,” “adapted to,” “made to,” or “capable of.” The term “configured to” may not necessarily mean only “specifically designed to” in hardware.

[0035] Instead, in some situations, the expression “device configured to do something” may mean that the device is “capable of doing something” together with other devices or components. For example, the phrase “processor configured (or set) to perform A, B, and C” may mean a dedicated processor for performing those operations (e.g., an embedded processor), or a generic-purpose processor (e.g., a CPU or application processor) capable of performing those operations by executing one or more software programs stored in a memory device.

[0036] In the embodiments, the 'part' performs at least one function or operation and may be implemented in hardware or software, or a combination of hardware and software.

[0037] Meanwhile, various elements and areas in the drawings are depicted schematically. Accordingly, the technical concept of the present invention is not limited by the relative sizes or spacing depicted in the attached drawings.

[0038] Hereinafter, embodiments according to the present disclosure are described in detail with reference to the attached drawings so that those skilled in the art can easily implement them.

[0039] FIG. 1 is a drawing for illustrating an interlocking system according to two preferred embodiments of the present disclosure.

[0040] Referring to FIG. 1, the interlocking system (1) according to the present disclosure includes an automatic control system (10), an Internet of Things (IoT) system (20), and an electronic device (100) for interlocking the automatic control system (10) and the IoT system (20).

[0041] The automatic control system (10) is a system that automatically controls the input value of a control target so that the output value of the control target matches a preset target value.

[0042] The automatic control system (10) may include an operating device that manages information on input / output devices and provides the user with the functions of monitoring the status of input / output devices and changing settings. The operating device and the input / output devices may have a hierarchical relationship.

[0043] The automatic control system (10) can communicate with input / output devices (11, 12, 13), such as sensors and actuators, through fieldbus communication standards.

[0044] 필드버스 통신 규격은 IEC 61784, IEC 62026, ISO 11898, ISO 16484, ISO 11783, IEC 14543, IEC 14908, IEC 61375, ISO 11519 등의 표준에 포함된 것과 표준에 포함되지 않은 것이 있으며, FF H1(Foundation Fieldbus H1), FF HSE(FF High Speed Ethernet), CIP(Common Industrial Protocol), ControlNet, DeviceNet, PROFIBUS(PROcess FIeld BUS), PROFINET(PROcess FIeld NET), PNET(Process NETwork), WorldFIP(World Factory Instrumentation Protocol), INTERBUS, CC-Link(Control & Communication Link), HART(Highway Addressable Remote Transducer protocol), WirelessHART, SERCOS(SErial Realtime COmmunications System), MECHATROLINK, Vnet / IP, TCnet, EtherCAT(Ethernet for Control Automation Technology), Ethernet POWERLINK, MODBUS RTU, MODBUS ASCII, MODBUS TCP, RAPIEnet(Realtim Automation Protocols for Industrial Ethernet), SafetyNET, ADS-net, FL-net, AS-i(Actuator Sensor interface), BACS(Building Automation and Control System), BACnet(Building Automation and Control network), CAN(Control Area Network), CANopen, Instabus(Installation bus), ISOBUS, LonWorks,There are also those with individual names, such as TCN (Train Communication Network), MVB (Multifunction Vehicle Bus), WTB (Wire Train Bus), SDS (Smart Distributed System), and VAN (Vehicle Area Network).

[0045] The Internet of Things system (20) is a system that allows a user to access and manage and control Internet of Things devices through a user terminal device (22). The Internet of Things system (20) is implemented as an Internet of Things platform (IoT platform) that integrates and manages information of Internet of Things devices that exchange information of sensors and actuators using Internet of Things communication standards, and provides the user with functions such as monitoring the status of the Internet of Things devices and changing settings. The Internet of Things platform and the Internet of Things devices have a hierarchical relationship. Information exchange between the Internet of Things devices and the Internet of Things system (20) is carried out through messages, and input / output messages are transmitted and received to each other to read input information and write output information. In order for the Internet of Things system (20) to recognize the input / output information of the Internet of Things devices, the builder of the Internet of Things system must register message metadata defining the input / output messages of the Internet of Things devices in the Internet of Things system (20).

[0046] Internet of Things communication standards include HTTP (Hyper Text Transfer Protocol), HTTPS (HTTP Secure), MQTT (Message Queuing Telemetry Transport), MQTTS (MQTT Secure), AMQP (Advanced Message Queuing Protocol), and CoAP (Constrained Application Protocol) in Ethernet communication networks, and information is represented using XML (eXtensible Markup Language), JSON (JavaScript Object Notation), etc. When an electronic device (100) is difficult to connect directly to an Ethernet communication network and is connected to an Internet of Things system (20) via a network (21) such as an LPWA (Low Power, Wide Area) communication network, the Internet of Things communication standards use Sigfox, LoRa, Weightless, Wize, LTE-M, Telensa, Nwave, NBFi, MIoTy, LTE-Advanced, 5G, NB-IoT, Wi-SUN, DASH7, etc., and information is represented using character strings, number strings, etc.

[0047] The automatic control system (10) and the Internet of Things system (20) can be interconnected through an electronic device (100) according to the present disclosure. The electronic device (100) can be positioned below the automatic control system (10) and simultaneously below the Internet of Things system (20). At this time, the electronic device (100) can be connected to the automatic control system (10) as one of the input / output devices of the automatic control system (10), and can be connected to the Internet of Things system (20) as one of the Internet of Things devices.

[0048] Specifically, the electronic device (100) can be connected to the input / output devices (11, 12, 13) connected to the lower part of the automatic control system (10) using the same fieldbus communication standard. Since the configuration of the automatic control system (10) is general, the builder of the automatic control system (10) faces no significant difficulty in adding the electronic device (100) compared to adding existing input / output devices. This has the advantage of simplifying the interlocking tasks of the builder of the automatic control system (10).

[0049] Additionally, the electronic device (100) can be connected to the Internet of Things system (20) via an Internet of Things communication standard. Unlike in the past, where a builder required separate tasks to manage lower-level devices within the Internet of Things system (20) in order to connect devices other than general Internet of Things devices to the lower-level Internet of Things system (20), the electronic device (100) according to the present disclosure has the advantage of simplifying the builder's integration tasks of the Internet of Things system (20) by performing the integration process with only the task of adding general Internet of Things devices.

[0050] Meanwhile, the electronic device (100) according to the present disclosure can generate a user interface for checking the status of input / output devices connected to an automatic control system (10) and controlling their operation, and can transmit the generated user interface to an Internet of Things system (20). Accordingly, a user terminal device (22) connected to the Internet of Things system (20) can check the status of input / output devices connected to the automatic control system (10) and control their operation through the generated user interface.

[0051] In existing Internet of Things (IoT) systems, the configuration for checking device status and setting parameters was expressed only in a one-dimensional manner (utilizing classification and substitution). Since this failed to reflect the changing functions and states of the device in the user interface, existing IoT systems could only transmit fixed information without a separate implementation process.

[0052] The present disclosure creates and provides a user interface that responds to changing functions of a device and responds to real-time state changes of the device without a separate construction process. The present disclosure provides a user interface that flexibly responds to changing functions and states of the device.

[0053] Detailed information regarding the interlocking method according to the present disclosure will be explained with reference to the drawings below.

[0054] FIG. 2 is a drawing for explaining the configuration and operation of an electronic device according to one embodiment of the present disclosure.

[0055] Referring to FIG. 2, the electronic device (100) may include a fieldbus connection unit (110), a fieldbus virtual input / output memory (120), an Internet of Things connection unit (130), a configuration management unit (140), and a user interface connection unit (150). Some of the above components may be omitted, and the electronic device (100) may include additional components in addition to the above components.

[0056] The fieldbus connection unit (110) can be connected to the operating device of the automatic control system (10) based on fieldbus communication standards and operate as an input / output device. The fieldbus connection unit (110) can obtain input / output information from other input / output devices connected to the automatic control system (10).

[0057] The fieldbus virtual input / output memory (120) can store input / output information transmitted and received through the fieldbus connection (110).

[0058] Specifically, the fieldbus connection unit (110) is connected to the operating device of the automatic control system (10) based on fieldbus communication standards and operates as an input / output device, and can exchange data with the operating device. At this time, the fieldbus connection unit (110) has a multi-protocol conversion function that supports simultaneous connection and communication for multiple different fieldbus communication standards, thereby providing the ability to integrate and manage different types of automatic control systems (10) with a single electronic device (100).

[0059] Specifically, the fieldbus connection unit (110) can receive input / output data obtained from other input / output devices (sensors, valves, motors, etc.) included in the automatic control system (10) from the operating device of the automatic control system (10). In addition, the fieldbus connection unit (110) can transmit control commands for controlling the automatic control system (10) to the operating device of the automatic control system (10).

[0060] Data received by the fieldbus connection part (110) from the operating device of the automatic control system (10) can be stored in the fieldbus virtual input / output memory (120) of the electronic device (100).

[0061] The fieldbus virtual input / output memory (120) is a data mirror space that stores input / output data transmitted and received by the fieldbus connection unit (110) to and from the operating device, and is allocated to a memory space located inside the electronic device (100). The electronic device (100) can store the input / output data received from the operating device along with data status information (e.g., validity, timestamp) by mapping it to a logical unique identifier called a fieldbus virtual input / output memory address.

[0062] The fieldbus virtual input / output memory (120) can be configured to maintain logical consistency of virtual addresses assigned to specific data regardless of changes in input / output wiring within the automatic control system (10), changes in program variable names within the automatic control system (10), changes in memory storage locations, changes in operating device models, etc. This allows the data definition unit to subsequently generate a CFG file independent of the variable environment within the automatic control system (10).

[0063] To implement this, the electronic device (100) may include an address translation engine that manages a dual mapping table between the memory address of the operating device and the virtual I / O memory address inside the electronic device (100). The virtual I / O memory address corresponds to a unique identifier assigned on the memory of the operating device of the automatic control system (10), while also existing as a fixed address inside the electronic device (100) for CFG file definition. By defining data based on the fixed virtual address, the data definition unit ensures consistency in data management regardless of changes in the physical I / O wiring of the automatic control system (10) or changes within the operating device. The dual mapping table may be managed in a hash map structure such as {Physical Operating Device ID : {Operating Device Memory Address (D100): Virtual I / O Memory Address (40001)}}, and the address translation engine can monitor real-time fieldbus communication traffic and, when there is a data Read / Write request from the operating device, query this table to convert between the logical virtual address and the physical actual address.

[0064] For example, a specific input / output data 'Main Motor Status' is assigned to the initial operating device memory address (e.g., D100), and the virtual input / output memory address of the electronic device (100) can be assigned as 40001. Even if D100 is changed to D200 after a program change within the operating device, the data access path for 'Main Motor Status' within the electronic device (100) can always be maintained as 40001.

[0065] At this time, the address translation engine dynamically updates only the internal dual mapping table based on memory address change information obtained from the operating device. Once this update process is complete, all data access requests referencing the CFG file are accurately translated and transmitted to the changed operating device address. During this process, the address translation engine ensures data interoperability consistency without redefining the CFG file or redeploying the IoT system. This efficiently reduces system downtime and rework during data integration and migration of large-scale industrial systems.

[0066] Meanwhile, the Internet of Things connection unit (130) can be connected to the Internet of Things system (20) based on the Internet of Things communication standard and operate as an Internet of Things device.

[0067] The configuration management unit (140) can perform the function of deriving user interface configuration information based on a CFG (Configuration) file that defines the name, address, format, and array number of input / output information stored in the fieldbus virtual input / output memory (120) and the relationship between said input / output information and user interface elements. The configuration management unit (140) encompasses the functions of both the data definition unit and the user interface definition unit, and plays a key role in the creation of the CFG file and the definition of UI metadata.

[0068] The user interface connection unit (150) can perform the function of providing a user interface displayed on a user terminal device based on user interface configuration information derived from the configuration management unit (140). That is, the user interface connection unit (150) acts as an interface that transmits UI data to be finally rendered to the Internet of Things system (20), receives control commands (inputs) from the user terminal device, and transmits them to the configuration management unit (140) and the fieldbus connection unit (110).

[0069] The electronic device (100) is simultaneously connected to an automatic control system (10) and an Internet of Things system (20) based on the operation of the above-described configurations, so that the automatic control system (10) and the Internet of Things system (20) can be linked.

[0070] This linkage method has the advantage that the builder of the automatic control system (10) assigns the input / output information to be linked to the fieldbus virtual input / output memory (120), shares the address and data type of each assigned input / output information with the builder of the Internet of Things system (20), and the builder of the Internet of Things system (20) further defines the address of the input / output information in the message metadata to variably define the input / output message.

[0071] Traditionally, to integrate IoT systems with existing automatic control systems using IoT technology, a gateway was placed above the existing automatic control system. The gateway must perform the fundamental role of conforming fieldbus communication standards to IoT communication standards and integrating the information management systems, which vary by SCADA manufacturer, with the IoT information management system. Furthermore, depending on the configuration of the automatic control system, the gateway must perform the roles of an operational device, SCADA, or wide-area SCADA. When a gateway performs complex functions, it is referred to as an edge or fog gateway. When a gateway is placed between the IoT system and the automatic control system, the builder must perform tasks such as conforming to communication standards and information management systems, coding operations, and configuring the user interface. In other words, there was a problem in that the builder required extensive knowledge and the methods were complex to integrate the IoT system with the existing automatic control system using a gateway.

[0072] The interlocking system according to the present disclosure has the advantage of simplifying the implementation process by minimizing the knowledge that a builder must acquire to interlock an existing fieldbus-based automatic control system with an Internet of Things system.

[0073] Meanwhile, the present disclosure can create and provide a user interface that checks and controls the status of an automatic control system on an Internet of Things system without a separate construction process during the process of linking an Internet of Things system and an automatic control system. This will be explained in detail with reference to the drawings below.

[0074] FIG. 3 is a drawing for explaining the configuration of a shape management unit according to one embodiment of the present disclosure.

[0075] Referring to FIG. 3, the configuration management unit (140) may include a data definition unit and a user interface definition unit. The user interface definition unit may include a UI information definition unit, a classification information definition unit, a UI state definition unit, a value range definition unit, and a value definition unit. The value definition unit may include a value attribute definition unit, a data definition linkage unit, a classification information definition linkage unit, a UI state definition linkage unit, a value range definition linkage unit, an enum definition unit, and a record item definition unit.

[0076] Specific details regarding each component included in the configuration management unit (140) will be explained in detail below.

[0077] The configuration management unit (140) can perform operations to define and display a user interface based on a CFG file.

[0078] A CFG file may include data that defines the characteristics (input / output), format (variable type), address, array count, and other information of individual input / output information stored in a fieldbus virtual input / output memory (120), based on a virtual input / output memory address obtained from a fieldbus virtual input / output memory (120). Here, the CFG file serves not merely as a data specification, but as an executable metadata schema that drives the automatic generation of a user interface accessible in an Internet of Things system (20) and the real-time data processing logic. At least a portion of a CFG file according to one embodiment of the present disclosure may be as illustrated in FIG. 4.

[0079] Specifically, the CFG file can define whether the data assigned to a given address is input data or output data. This can be represented by the 'dir' field within the CFG file and can be used as basic information to determine whether to create monitoring elements or control elements for the data when creating a user interface. Based on this information, the user interface definition section can be utilized as a logical rule to automatically determine whether to create monitoring elements, such as gauges or graphs that simply display values, or control elements, such as buttons, sliders, or value input fields that can transmit control commands, when creating a user interface.

[0080] Additionally, the CFG file may specify the data type of the data stored at the corresponding address. This can be defined as bool, uint (unsigned integer), int (integer), real (real number / floating-point), etc. This can be represented as a type field within the CFG file and can be used to interpret the binary value of the data as an accurate value when creating a user interface.

[0081] In addition, in addition to the basic format described above, the CFG file may further define accurate bit length and byte order information for each data item to prevent data interpretation errors between heterogeneous devices when integrating heterogeneous fieldbus-based systems. This data can be used to convert binary data obtained by the electronic device (100) from the fieldbus virtual input / output memory (120) into a value identifiable by the Internet of Things system (20) in real time. The byte order information may be explicitly defined as either Big-Endian or Little-Endian, and the electronic device (100) ensures data integrity by performing byte order inverse conversion logic to accurately interpret binary byte streams of 16-bit, 32-bit, or 64-bit integer and real data based on this information.

[0082] In addition, the CFG file may define the visualization element most suitable for displaying data based on the type and orientation of the data (e.g., gauge or line graph by default for real type in data).

[0083] Additionally, the number of arrays of data may be defined in the CFG file. This can be represented as an array field within the CFG file. This definition of the number of arrays goes beyond simply indicating the number of values; it allows the data definition unit to group multiple related data into a single logical data group for processing. In particular, if the number of arrays is greater than 1, it is recognized as a single table, list, or group of repeating UI elements during user interface creation, and user interface elements can be automatically generated. This enables the dynamic creation of user interfaces for devices with multiple channels or repetitive structures (e.g., multi-channel meters, motor banks) without the need for separate manual coding.

[0084] Additionally, the CFG file may define other information necessary for data linkage and conversion, such as data size (size_byte), address offset (report_addr_offset), and data name (Name). For example, the data size specifies how many bytes a particular data is, ensuring accurate interpretation of the data size. Furthermore, the data name may include a name assigned to the data so that users can easily recognize it. This allows the data to be displayed by a user-recognizable name instead of its memory address in user interfaces created later.

[0085] As described above, the CFG file contains all the components necessary for the user interface definition section to dynamically generate a user interface. This file provides information such as the property (dir), type, and array determined during the data definition process by mapping it according to interface configuration rules. For example, for output data where the value of the dir field is “out,” a control button or value input field capable of transmitting control commands can be generated on the user interface.

[0086] In addition, the CFG file may additionally define 'Access Role' metadata that specifies read or write permissions for each input / output information for security and access control in the Internet of Things system (20) environment. This can enhance security by dynamically disabling or hiding specific control elements on the user interface according to the role of the user logged into the Internet of Things platform.

[0087] In addition, for all input / output data defined above, the CFG file may additionally define ontology-based semantic tag metadata that explains the meaning and function of the data. For example, tags such as 'controllable', 'measurement value', and 'RPM' are assigned to data named 'Motor_Speed', so that the Internet of Things system (20) can automatically identify the use of the data based on the CFG file and determine the optimal data processing and visualization method without a separate learning process. This has the effect of improving data utilization between heterogeneous systems.

[0088] Additionally, the CFG file may have additional metadata defined for each data item, such as 'Minimum Report Cycle' and 'Deadband', to effectively suppress unnecessary data transmission to the Internet of Things system (20). The electronic device (100) can refer to this deadband metadata to transmit data to the Internet of Things system (20) only when the range of change in the value exceeds a specified tolerance, and effectively reduce the system load by limiting traffic within the minimum report cycle.

[0089] Meanwhile, the electronic device (100) may further include an artificial intelligence-based data profiling engine that analyzes the real-time data profile of input / output information stored in the fieldbus virtual input / output memory (120) to automatically generate and optimize metadata for a CFG file. The engine automatically infers communication-related metadata, including the minimum transmission cycle and deadband value of the input / output information, and ontology-based semantic tag metadata using a learned machine learning model, and reflects the inference results in a CFG file to maximize the efficiency and compatibility of data linkage.

[0090] Specifically, the AI-based data profiling engine analyzes the rate of change, statistical distribution (minimum / maximum / average), and correlation with adjacent data of data assigned to a specific address of the fieldbus virtual input / output memory (120) over a certain period, automatically calculates the optimal deadband value based on the noise level of the data item, and can update the CFG file by dynamically adjusting the minimum transmission period based on the importance and change pattern of the data. In addition, the engine refers to an ontology database based on the name and unit information of the data (e.g., 'Main_Pump_Amperage', 'A') to automatically recommend or insert the most suitable semantic tag (e.g., 'control target', 'current', 'measurement value') corresponding to the function and meaning of the data, thereby preventing data interpretation errors between heterogeneous systems.

[0091] In a CFG file, all items defined as described above (characteristics, format, address, number of arrays, and other information) can be completed as a single logical group. Accordingly, complex and variable physical data of equipment within an automatic control system (10) is converted into metadata that can be utilized in an Internet of Things environment. At this time, the CFG file is designed to represent data from heterogeneous fieldbus systems as a single integrated CFG schema, thereby fundamentally eliminating the complexity of heterogeneous system integration.

[0092] The CFG file serves as an abstract data specification that connects variable field data of the automatic control system (10) with the service layer of the Internet of Things system (20). At this time, the CFG file can be generated in a language that the Internet of Things system (20) can understand regarding the variable input / output information of the automatic control system (10). For example, the CFG file can be generated in the form of structured text such as JSON (JavaScript Object Notation), XML (eXtensible Markup Language), or a table, which are generally universal data exchange formats. This ensures compatibility so that the Internet of Things system (20) can easily parse the file and interpret the data structure regardless of the platform type or operating environment.

[0093] In one embodiment of the present disclosure, at least some of the information defined within the CFG file may be generated in JSON form as shown in FIG. 4.

[0094] The above-described data definition and CFG file generation process may be performed by the electronic device (100) by referring to input / output data provided by the operating device of the automatic control system (10), or at least part of the CFG file generation process may be manually entered by a user or system administrator to generate the CFG file.

[0095] Meanwhile, the electronic device (100) may further include a CFG integrity verification unit that verifies in real time whether virtual input / output memory address and data format information defined in the CFG file matches the data structure (binary pattern and byte boundary of the stored data) stored in the actual fieldbus virtual input / output memory (120). The CFG integrity verification unit detects errors such as data inconsistency or memory overflow, and performs automatic correction of the CFG file when an error is detected to improve the reliability and integrity of the data linkage.

[0096] Specifically, the CFG integrity verification unit checks in real time whether metadata such as data format, size, and array size defined in the CFG file matches the binary pattern and byte boundary of the data recorded in the actual fieldbus virtual input / output memory (120). Through this check, data overflow or incorrect format conversion errors are detected in advance. In addition, the CFG integrity verification unit cross-verifies the consistency between the dual mapping table managed by the address translation engine and the virtual input / output memory address defined in the CFG file, thereby preventing the possibility of logical data errors caused by address changes. Furthermore, if data inconsistency or integrity error is detected, the CFG integrity verification unit notifies the Internet of Things system (20) of the error information, performs automatic correction of the CFG file for minor errors, and instructs the data definition unit to generate recommendations necessary for error correction for major errors, thereby supporting the system administrator's response.

[0097] The user interface definition unit can generate a user interface that can be displayed through the Internet of Things system (20) based on a CFG file. A user interface according to one embodiment of the present disclosure may be as shown in FIG. 5.

[0098] The user interface definition unit can create a user interface by parsing a CFG file and extracting the user interface items and rules defined therein. This process can be carried out by dynamically instantiating user interface components in a runtime environment based on the metadata included in the CFG file.

[0099] Specifically, the user interface definition section may include a UI information definition section, a classification information definition section, a UI state definition section, a value range definition section, and a value definition section. Here, each definition section may be implemented as a separate component or as a logical module. These configurations can generate a user interface by reflecting the metadata structure that constitutes the UI section of the CFG file.

[0100] Alternatively, the electronic device (100) may perform a process of generating a user interface that can be displayed through the Internet of Things system (20) based on a CFG file.

[0101] The electronic device (100) may create a user interface by parsing a CFG file and extracting user interface items and rules defined therein. This process may be carried out by dynamically instantiating user interface components in a runtime environment based on metadata included in the CFG file. The UI information definition unit may define overall rules for displaying the user interface. Specifically, the UI information definition unit may perform the function of defining all metadata and logical rules for the entire user interface corresponding to the input / output data of the automatic control system (10). This encompasses all sub-definition items (state linkage, range, value representation, record item, classification information, etc.) required for creating the user interface, thereby enabling the user interface definition unit to create a user interface that flexibly responds to the variable data structure of the field. The UI information definition unit may define UI screen setting information within the CFG file, such as the title of the entire UI, the maximum number of parts (max_part), whether to save the log file (log_file_on), and the log storage period (log_month_duration).

[0102] In addition, the UI information definition unit can generate a user interface by additionally defining interface rendering logic, such as the display location, relative size, visual hierarchy, and priority of user interface elements, in the CFG file, or by referencing a separate UI template file, in addition to the metadata defined in the CFG file. This goes beyond merely generating data display elements and supports the dynamic configuration of the user interface with a layout optimized for various access environments, such as mobile, web, and desktop. To this end, the UI information definition unit can receive the metadata from the CFG file as input and dynamically generate responsive web components based on CSS (Cascading Style Sheets) or JSON schemas.

[0103] The classification information definition unit can define a hierarchical structure for hierarchically classifying individual input / output information. Specifically, the classification information definition unit performs the function of managing information by grouping various input / output information by function or by adding information that classifies it into a hierarchical structure according to the system diagram through the 'branch' section within the CFG file. This supports simplifying vast amounts of data in complex automatic control system configurations and simplifying management in an intuitive form. The classification information can define hierarchical relationships based on parent-child relationships by including attributes such as parent part identifiers (parent_id), unique identifiers (id), and display labels (label). For example, as shown in FIG. 5a, "Common," "Field," and "Paddy" can be hierarchically defined under "Overall Packaging," and zone information such as "Zone 1," "Zone 2," etc., can be defined under "Field."

[0104] The classification information definition section classifies input / output information into functional groups and hierarchical structures through the 'branch' section within the CFG file, and defines hierarchical relationships based on parent-child relationships by including parent part identifier (parent_id), unique identifier (id), and user display label (label) attributes.

[0105] The UI state definition unit can define the display state of individual input / output information. Specifically, the UI state definition unit (183) can define a state variable by assigning a specific array index to data defined as a Boolean through the 'show' section in the CFG file and assigning a logical name to it. This can be used to implement a user interface that responds to a state that changes in real time. For example, the UI state definition unit can be utilized to implement a dynamic user interface that responds to the state of specific data that changes in real time and interacts with the visibility or activation / deactivation functions of other user interface elements. UI state information can include the logical name (data), index, and state name attributes of the data, and can specify which index of which data will be used as which state name.

[0106] The value range definition section can define the display unit, allowable display range, and display decimal places for individual input / output information. Specifically, the value range definition section can set user interface display attributes, primarily for analog value data, through the 'number_range' section within the CFG file. The value range definition section sets attributes such as the data name, unit, display range (min, max), and decimal places (round), which can be utilized in the user interface for the maximum / minimum range of a slider, the display of a valid range for a gauge, or the validation of text input fields. The value range definition information includes the {name, unit, min, max, round} attributes.

[0107] The value range definition section sets display attributes for analog value or set value data through the 'number_range' section in the CFG file, which provides {name, unit, min, max, round} attributes in a structured format.

[0108] The value definition unit can define the value for which individual input / output information is displayed. That is, the value definition unit performs the function of displaying a value corresponding to a specific index of data defined in the CFG file on the user interface through the 'value' section within the CFG file. For example, the value definition unit can determine whether the user interface element is visible by linking the information of the previously defined UI state definition unit, and can convert the data into the form most suitable for the user and visualize it by linking the information of the value range definition unit (184) to reflect the range of the value and related additional characteristics (e.g., unit, decimal point processing).

[0109] The value definition unit integrates all metadata defined in the CFG file to perform final presentation logic that defines how individual input / output information will be visually represented on the user interface, and links the information from the UI state definition unit and the value range definition unit to reflect the visibility, unit, range, etc. of the value so that it can be visualized.

[0110] Meanwhile, the value definition section may include a value attribute definition section, a data definition linkage section, a classification information definition linkage section, a UI state definition linkage section, a value range definition linkage section, an enum definition section, and a record item definition section.

[0111] The value attribute definition section defines a display name (name) and an additional description (desc) for the above input / output information. Here, the display name (name) is used as the title or label of the corresponding value item on the user interface, and the additional description (desc) can be used to provide additional context to the user by providing information on the source of the value (e.g., soil, irrigation, manual) or characteristics.

[0112] The value attribute definition section defines a user-friendly display name and additional description for the above input / output information to convey semantic context.

[0113] The data definition linkage unit performs the function of logically linking data items among the input / output data items defined in the 'data' section of the CFG file by the data definition unit, by including the logical name (data) of the data to be referenced by the value definition information and, if the data is defined as an array, an array index (index) that specifies the location within the array. Through this linkage, the value definition unit (185) can accurately identify the location and format of specific input / output information within the fieldbus virtual input / output memory (120) and retrieve the value.

[0114] The data definition linkage unit performs the function of linking data items in an address-independent logical manner, including the logical name (data) and array index (index) of the data items to be referenced by the corresponding value definition information among the data items defined in the 'data' section of the CFG file.

[0115] The classification information definition linkage unit can specify which logical or physical zone (e.g., Test Zone 1, Zone 2) the corresponding value definition information belongs to by linking it to the part identifier (part) of the hierarchical structure defined by the classification information definition unit. This ensures that the corresponding value item is placed in the correct location within a hierarchical menu structure (e.g., tree menu) when creating a user interface.

[0116] The UI state definition linkage can define whether the value is displayed on the user interface (visibility) by referencing the state variable (show) defined in the UI state definition. For example, by implementing logic to set the 'manual control button' to be displayed (show) only when a specific device is in 'manual mode', a dynamic interface suitable for the user's operation context can be provided. The UI state definition linkage can provide a dynamic interface by implementing specific conditional rendering logic.

[0117] The value range definition linkage unit can link the display unit, allowable range, and decimal places for the corresponding value by referencing the value range definition name (number_range) defined by the value range definition unit (184). Through this linkage, analog data (e.g., temperature 28.0°C) is expressed up to one decimal place according to the value range definition and visualized along with the unit (°C). The value range definition linkage unit links the display unit, allowable range, and decimal places for the corresponding value and can display a visual warning for values ​​outside the valid range.

[0118] The enum definition defines the actual numeric code (number) for the above value and the label displayed to the user, so that complex device status codes (e.g., 0, 1, 2) can be converted into text that the user can recognize (e.g., remote operation, manual operation, automatic operation). The enum definition can be represented as an array of {number, label} pairs.

[0119] The enum definition (185f) can support the interpretation of complex device status codes by defining a numeric code representing the actual device status for the value and an intuitive string label displayed to the user.

[0120] The record item definition unit defines a record code (log_code), record value number (log_val_no), and record value rate (log_val_rate) for the record management of the above value, thereby supporting the history management of specific data and the setting of alarm policies. This can provide metadata necessary to store and analyze the history of changes in the corresponding value in a database or log system on an IoT platform. The record item definition unit can provide data tracking metadata that supports the history management of specific data and the setting of alarm policies.

[0121] Meanwhile, although not shown in the drawing, the user interface definition unit may further include a user interaction learning unit that analyzes the user's interface usage history (e.g., frequency of viewing specific data, number of control command inputs, menu access path) collected through the Internet of Things system (20). The user interaction learning unit learns a machine learning model based on the acquired usage history data to select data that is predicted to be most important or frequently used according to the user's work context among the data defined in the CFG file, and dynamically optimizes the user interface so that the user interface definition unit places the data in a priority area at the top of the screen. This can provide the user with a personalized and intelligent user interface.

[0122] Specifically, the machine learning model of the user interaction learning unit analyzes user behavior patterns in real time and can execute algorithms that identify the control elements the user accesses first, particularly in complex situations (e.g., alarms, system mode changes), and either highlight those elements in advance or dynamically reconfigure the layout to minimize the path to those elements. This can provide an intelligent user interface that supports users in operating the system quickly and accurately in emergency situations.

[0123] Additionally, the user interface definition unit may further include a prediction-based user interface creation function that receives failure prediction and remaining life prediction information regarding the equipment status of the automatic control system (10) in conjunction with a prediction analysis information receiving unit, selects control elements or status display elements related to the predicted failure among the data items defined in the CFG file, dynamically injects them into the user interface, and displays them as the highest priority.

[0124] Alternatively, the electronic device (100) may further include a prediction-based user interface creation function that receives failure prediction and remaining life prediction information regarding the equipment status of the control system (10) in conjunction with a prediction analysis information receiving unit, selects control elements or status display elements related to the predicted failure among data items defined in the CFG file, dynamically injects them into the user interface, and displays them as the highest priority.

[0125] This prediction-based user interface generation function enables the user interface definition unit to parse a CFG file and immediately identify metadata related to 'Pump A', such as 'operating status', 'operating current', and 'maintenance command button', when the prediction analysis information receiving unit receives information that the remaining life of a specific facility (e.g., 'Pump A') is predicted to be below a threshold value. Based on this information, the user interface definition unit generates an 'emergency maintenance recommendation panel' on the user interface that is independent of the existing UI structure, thereby visually notifying the user of potential risks to the facility and providing a dedicated button to issue preemptive control commands (e.g., calling a maintenance team), which drastically reduces system downtime and enables preemptive maintenance.

[0126] Alternatively, this prediction-based user interface generation function can also enable the electronic device (100) to parse a CFG file and immediately identify metadata such as 'operating status', 'operating current', and 'maintenance command button' related to 'pump A' when the prediction analysis information receiver receives information that the remaining life of a specific facility (e.g., 'pump A') is predicted to be below a threshold value, and based on this information, create an 'emergency maintenance recommendation panel' on the user interface that is independent of the existing UI structure to visually notify the user of potential risks to the facility and provide a dedicated button to issue preemptive control commands (e.g., call a maintenance team), thereby significantly reducing system downtime and enabling preemptive maintenance.

[0128] The prediction of failure and remaining lifespan of the above equipment may be performed by referring to data on the Internet of Things platform received from the Internet of Things by the Internet of Things connection unit (130). The Internet of Things connection unit (130) may also generate prediction data based on data regarding the equipment status of the automatic control system (10) and current operating status data, and by reflecting this in a user interface, it may support an administrator in monitoring or displaying necessary measures.

[0129] Additionally, the user interface definition unit may further include a location-based user interface determination unit that receives location information (GPS, Wi-Fi, Beacon signal, etc.) of a user terminal device (22) and determines whether the location information is included within a predefined geo-fencing area. The location-based user interface determination unit can dynamically activate / deactivate control authority for a specific facility (e.g., 'first zone pump') within the automatic control system (10) or a user interface specialized for the facility based on the user's physical location, thereby providing different user interfaces when the user is at the site and when the user is at a remote location, thereby providing an efficient, safe, and optimized user experience.

[0130] Furthermore, the user interface definition unit may further include an augmented reality metadata definition unit that generates AR overlay metadata for overlaying Internet of Things data onto physical equipment in an augmented reality (AR) environment based on hierarchical structure information and classification information of data defined in a CFG file.

[0131] The augmented reality metadata definition unit outputs an AR schema that defines spatial anchors and visualization types (e.g., gauges, text labels) by linking the hierarchical structure information of the CFG file with the three-dimensional (3D) model of the equipment received from the outside and the sensor location information, so that each data item (e.g., 'Temperature 1', 'Valve 1') is connected to a specific point of the physical equipment. Accordingly, when a field worker projects the actual equipment through the user terminal device (22), real-time data (e.g., 28.0°C) obtained according to the definition of the CFG file is displayed directly on the equipment, thereby providing a field-oriented user experience that allows for intuitive diagnosis and control of the equipment's status without the need for separate drawings or device verification. At this time, the user terminal device (22) can be implemented as various types of wearable devices, such as a head-up display, in addition to a smartphone. Spatial anchors can be defined as GPS coordinates or 3D spatial coordinates based on VPS (Visual Positioning System), and the augmented reality metadata definition unit creates a spatial partitioning data structure using the separation information and hierarchical structure information of the CFG file, thereby supporting selective data streaming that selects and transmits only the necessary AR overlay data in real time according to the field worker's viewing angle and position.

[0132] Meanwhile, the electronic device (100) according to the present disclosure may further include a blockchain-based distributed identity processing unit to enhance mutual authentication and data integrity with an automatic control system (10) and an Internet of Things system (20). The distributed identity processing unit generates a unique identifier of the electronic device (100) as an identity document and registers it with the Internet of Things system (20) to provide a security mechanism that prevents tampering that may occur during communication between devices. Specifically, the distributed identity processing unit encrypts the creation and modification history of the CFG file and records it on the blockchain, thereby ensuring the integrity of the CFG file and supporting an administrator to transparently verify the modification history in the future.

[0133] Meanwhile, information generated to create a user interface and an example of the user interface created therefrom will be explained with reference to the drawings below.

[0134] First, hierarchical information in which data or control items are grouped according to a logical / physical structure may be as shown in Fig. 5a below.

[0135] And, a specific index of a specific data item is named, and the state / visibility linkage information used to control the visibility or enabled / disabled state of other user interface elements may be as shown in FIG. 5b.

[0136] In addition, the range (min, max), unit, and decimal precision for displaying numerical data on the user interface or performing validation when inputting control commands may be as shown in FIG. 5c below.

[0137] And, using the data described above, the generated user interface may be as shown in FIG. 6.

[0138] As described above, the generated user interface can be displayed through a user terminal device (22) connected to the Internet of Things system (20). However, the user terminal device (22) is not limited to a device connected to the Internet of Things (20), and may be implemented as the electronic device (100) itself, or may refer to a device connected to the electronic device (100) through a separate network. The user can access the user interface through a browser, etc., installed on the user terminal device (22), and can monitor the status of the device and control the operation of the device through the user interface.

[0139] Although various embodiments have been described above, each embodiment is not necessarily implemented individually, and may be combined with at least one other embodiment, either wholly or partially, to be implemented together in a single product.

[0140] Meanwhile, the term “part” as used in this disclosure includes a unit composed of hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit, for example. “Part” may be a component formed integrally, or a minimum unit or part thereof that performs one or more functions. For example, “part” may be composed of an application-specific integrated circuit (ASIC).

[0141] Various embodiments of the present disclosure may be implemented as software comprising instructions stored on machine-readable storage media (e.g., a computer). The machine may include an electronic device (100) according to the disclosed embodiments, which is a device capable of calling instructions stored from the storage media and operating according to the called instructions. When the instructions are executed by a processor, the processor may perform a function corresponding to the instructions directly or using other components under the control of the processor. The instructions may include code generated or executed by a compiler or an interpreter. The machine-readable storage media may be provided in the form of non-transitory storage media. Here, "non-transitory" means only that the storage media does not contain a signal and is tangible, and does not distinguish whether data is stored semi-permanently or temporarily in the storage media.

[0142] According to one or more embodiments, the method according to the various embodiments disclosed herein may be provided as included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)) or online through an application store (e.g., Play Store™). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created in a storage medium such as the memory of a manufacturer's server, an application store's server, or a relay server.

[0143] Each component (e.g., module or program) according to various embodiments may consist of a singular or multiple entities, and some of the aforementioned sub-components may be omitted, or other sub-components may be further included in various embodiments. Generally or additionally, some components (e.g., module or program) may be integrated into a single entity to perform the same or similar functions as those performed by each of the respective components prior to integration. The operations performed by the module, program, or other components according to various embodiments may be executed sequentially, in parallel, iteratively, or heuristically, or at least some operations may be executed in a different order, omitted, or other operations added. Explanation of the symbols

[0145] 10: Automatic control system 20: Internet of Things system 21: Network 22: User terminal device 100: Electronic device 110: Fieldbus connector 120: Fieldbus virtual I / O memory 130: Internet of Things connection unit 140: Configuration Management Unit 150: User Interface Connection Unit

Claims

Claim 1 An electronic device for implementing a user interface from a CFG file containing design information of an automatic control system for controlling a plurality of heterogeneous devices, comprising: a fieldbus virtual I / O memory for storing input / output information transmitted and received via a fieldbus communication standard connected to the automatic control system; a configuration management unit for deriving user interface configuration information based on a CFG (Configuration) file in which the name, address, format, data direction, and number of arrays of the input / output information and the operational connection relationship between the input / output information and user interface elements are defined in an integrated manner; and a user interface connection unit for providing a user interface displayed on a user terminal device based on the user interface configuration information derived from the configuration management unit, wherein the user interface is configured to control the plurality of heterogeneous devices on a single integrated screen, and is configured to implement user interface components and their operational connection relationships by distinguishing between monitoring elements and control elements using information from the CFG file including the data direction. Claim 2 An electronic device according to claim 1, wherein the configuration management unit comprises: a data definition unit that defines the name, address, format, and array number of each of the input / output information stored in the fieldbus virtual input / output memory; and a user interface definition unit that defines the relationship between the input / output information and the user interface element. Claim 3 In paragraph 2, the user interface definition unit comprises: a UI information definition unit that defines overall rules for displaying the user interface; a classification information definition unit that defines a hierarchical structure for hierarchically classifying the input / output information; a UI state definition unit that defines the display state of each of the input / output information; a value range definition unit that defines the display unit, display allowable range, and display decimal places of each of the input / output information; and a value definition unit that defines the value in which each of the input / output information is displayed. Claim 4 In paragraph 2, the data definition unit includes an artificial intelligence-based data profiling engine that automatically generates and optimizes metadata of the CFG file by analyzing a real-time data profile of input / output information stored in the fieldbus virtual input / output memory, and the artificial intelligence-based data profiling engine defines a deadband value and a minimum transmission period based on the rate of change and noise level of the input / output information, an electronic device. Claim 5 In paragraph 3, the electronic device comprises: a value definition unit that defines a display name and additional description for the input / output information; a data definition linkage unit that links to the name and array index of the data defined by the data definition unit; a classification information definition linkage unit that links to the hierarchical structure defined by the classification information definition unit; a UI state definition linkage unit that defines the state in which the value is displayed in conjunction with a state variable defined by the UI state definition unit; a value range definition linkage unit that links to the value range definition name defined by the value range definition unit; an enum definition unit that defines an actual numeric code for the value and a label displayed to the user; and a record item definition unit that defines a record code, a record value number, and a record value ratio for record management of the value. Claim 6 The electronic device according to claim 1 further comprises a CFG integrity verification unit that checks in real time whether the format and size information of the data defined in the CFG file matches the binary pattern and byte boundary of the data stored in the fieldbus virtual input / output memory, and performs automatic correction of the CFG file upon detection of an error. Claim 7 The electronic device according to claim 1 further comprises an address translation engine that manages a dual mapping table between the actual memory address of the operating device of the automatic control system and the address of the virtual input / output memory, wherein when the actual memory address of the operating device is changed, the address translation engine dynamically updates the dual mapping table based on memory address change information obtained from the operating device and maintains the address of the virtual input / output memory. Claim 8 The electronic device according to claim 1 further comprises a distributed identity processing unit that performs mutual authentication between the automatic control system and the Internet of Things system using blockchain-based distributed identity technology in communication between the automatic control system and the Internet of Things system, and the distributed identity processing unit encrypts the creation and modification history of the CFG file and records it on the blockchain. Claim 9 The electronic device according to claim 1 further comprises a location-based user interface determination unit that receives location information of a user terminal device and determines whether the location information is included within a predefined geographical area, and the location-based user interface determination unit dynamically activates or deactivates control authority for a specific facility within the automatic control system and a user interface specialized for the specific facility according to the location of the user terminal device.

Images