Data management system

Abstract

A data management system is disclosed, comprising: a first device for acquiring first data associated with a first asset; a second device for acquiring second data associated with a second asset; and a management device connected to the first device and the second device and managing a first contract associated with data transmission between the first asset and the second asset, wherein the first device is configured to transmit at least a portion of the first data to the second device through a communication interface based on the first contract.

Description

Technology Field

[0001] The present disclosure relates to a data management system. Background Technology

[0002] A manufacturing process may include various procedures such as process control, quality monitoring, and safety management. These various procedures within the manufacturing process are organically interconnected, and the data generated from each procedure can be utilized collaboratively. For example, data for safety management can be generated using data produced during the quality monitoring procedure.

[0003] Meanwhile, data management systems are being introduced to manage the large volume of data generated according to manufacturing process procedures. Existing data management systems can integrate and manage data on a central server. However, due to technological advancements and data aggregation, data overload may occur where excessive data is concentrated on the central server, and sharing data within the central server may take a significant amount of time. Furthermore, existing data management systems find it difficult to integrate data of different formats, which can lead to data isolation and reduced interoperability. Accordingly, there is a demand for the development of technologies capable of efficiently managing data. The problem to be solved

[0004] The present disclosure provides a data management system for solving the above-mentioned problems. means of solving the problem

[0005] The present disclosure may be implemented in various ways, including methods, devices (systems), and / or computer programs stored on computer-readable storage media.

[0006] According to one embodiment of the present disclosure, a data management system comprises a first device for acquiring first data associated with a first asset, a second device for acquiring second data associated with a second asset, and a management device connected to the first device and the second device and managing a first contract associated with data transmission between the first asset and the second asset, wherein the first device may be configured to transmit at least a portion of the first data to the second device through a communication interface based on the first contract.

[0007] According to one embodiment, the management device may be configured to verify the validity of the first asset in response to receiving a request to register a first asset from a first device, and if the validity of the first asset is verified, to register the first asset, and in response to receiving a request to register a second asset from a second device, to verify the validity of the second asset, and if the validity of the second asset is verified, to register the second asset.

[0008] According to one embodiment, the management device may be configured to transmit information associated with the first contract to the first device in response to receiving information associated with the first contract from the second device, transmit information indicating whether the first contract is accepted to the second device in response to receiving information indicating whether the first contract is accepted from the first device, and store contract information of the first contract when the first contract is completed.

[0009] According to one embodiment, the management device may be configured to receive a request for provider information of data associated with a first asset from a second device, transmit information about the first device associated with the first asset to the second device, and the second device may verify the validity of the first device based on the information about the first device, and if the validity of the first device is verified, request the transmission of data associated with the first asset to the first device through a communication interface.

[0010] According to one embodiment, at least a portion of the first data transmitted to the second device may include real-time data associated with the first asset.

[0011] According to one embodiment, the communication interface may include at least one of an RPC interface or an OPC UA interface.

[0012] According to one embodiment, the communication interface may include a first communication interface operating based on a first network layer for real-time data transmission and a second communication interface operating based on a second network layer for semantic data transmission.

[0013] According to one embodiment, at least a portion of the first data transmitted to the second device may include data processed into a predetermined data format.

[0014] According to one embodiment, the predetermined data format may include a data format according to an AAS model.

[0015] According to one embodiment, the first device may be configured to generate data for the management of the first asset through a machine learning model that takes the first data as input.

[0016] According to one embodiment, the first device may be configured to further acquire third data associated with at least one third asset and to transmit at least a portion of the third data to the second device through a communication interface based on a second contract associated with data transmission between at least one third asset and the second asset.

[0017] According to one embodiment, the first device may be configured to generate data by integrating the first data and the third data, and to transmit at least a portion of the integrated data to the second device through a communication interface based on at least one of the first contract or the second contract.

[0018] According to one embodiment, the data management system further includes a third device for acquiring third data associated with a third asset, and the third device may be configured to receive at least a portion of first data from a first device through a communication interface based on a second contract associated with data transmission between a first asset and a third asset, and to receive at least a portion of second data from a second device through a communication interface based on a third contract associated with data transmission between a second asset and a third asset.

[0019] According to one embodiment, the third device may be configured to generate at least one of data for managing a first asset, data for managing a second asset, or data for managing a third asset through a machine learning model that takes as input at least a portion of first data received from a first device and at least a portion of second data received from a second device.

[0020] According to one embodiment, the third device may be configured to transmit data for managing the first asset to the first device through a communication interface when data for managing the first asset is generated, and to transmit data for managing the second asset to the second device through a communication interface when data for managing the second asset is generated.

[0021] According to one embodiment, the third device may be configured to apply at least a portion of the first data received from the first device and at least a portion of the second data received from the second device to a digital twin model pre-built for the first asset, the second asset, and the third asset.

[0022] According to one embodiment, the third device may be configured to transmit at least a portion of the third data to an external device through a communication interface and another communication interface.

[0023] According to one embodiment, the third device may be configured to perform a blockchain-based authentication procedure before transmitting at least a portion of the third data to an external device.

[0024] According to one embodiment, the management device may be configured to receive a request for the addition of a fourth asset from a fourth device that obtains fourth data associated with a fourth asset, verify the validity of the fourth asset, and if the validity of the fourth asset is verified, transmit information associated with the addition of the fourth asset to a third device.

[0025] According to one embodiment, the management device may be configured to authenticate a connection between the first device and the second device in response to receiving a request to change information associated with the first asset from the first device, and the first device may be configured to transmit at least a portion of the first data associated with the first asset obtained after the change of information to the second device through a communication interface when authentication is completed. Effects of the invention

[0026] According to some embodiments of the present disclosure, data is stored, generated, and managed by each device acquiring data associated with an asset, and by sharing data through data transmission and reception between devices, data overload where data is concentrated on a central server can be prevented and the speed of data sharing can be improved.

[0027] In addition, according to some embodiments of the present disclosure, by processing and managing data into a predetermined data format, data integration can be facilitated and data interoperability can be improved.

[0028] In addition, according to some embodiments of the present disclosure, authentication of the data sender and the data receiver and data sharing are performed simply by the data sender and the data receiver registering with a management device, thereby enabling data sharing more simply and quickly, and making it possible to share real-time data.

[0029] The effects of the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by a person skilled in the art to which the present disclosure pertains (referred to as "person skilled in the art") from the description in the claims. Brief explanation of the drawing

[0030] Embodiments of the present disclosure will be described with reference to the accompanying drawings described below, wherein similar reference numerals indicate similar elements, but are not limited thereto. FIG. 1 is a drawing showing a data management system according to one embodiment of the present disclosure. FIG. 2 is a schematic diagram showing a configuration in which an information processing system is connected to communicate with a plurality of user terminals in relation to data processing according to one embodiment of the present disclosure. FIG. 3 is a block diagram showing the internal configuration of a user terminal and an information processing system according to one embodiment of the present disclosure. FIG. 4 is a drawing for explaining the configuration of a device within a data management system according to one embodiment of the present disclosure. FIG. 5 is a drawing for explaining the configuration of another device within a data management system according to one embodiment of the present disclosure. FIG. 6 is a diagram illustrating a network layer for data transmission according to one embodiment of the present disclosure. FIG. 7 is a drawing for explaining a method for registering an asset according to one embodiment of the present disclosure. FIG. 8 is a drawing for explaining a method of contracting between assets according to one embodiment of the present disclosure. FIG. 9 is a diagram illustrating a method for transmitting and receiving data between assets according to one embodiment of the present disclosure. Specific details for implementing the invention

[0031] Hereinafter, specific details for implementing the present disclosure will be described in detail with reference to the attached drawings. However, in the following description, specific descriptions regarding widely known functions or configurations will be omitted if there is a risk that the gist of the present disclosure may be unnecessarily obscured.

[0032] In the attached drawings, identical or corresponding components are assigned the same reference numerals. Additionally, in the description of the following embodiments, the description of identical or corresponding components may be omitted. However, even if a description of a component is omitted, it is not intended that such component is not included in any embodiment.

[0033] The advantages and features of the disclosed embodiments and the methods for achieving them will become clear by referring to the embodiments described below in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms, and the embodiments provided are merely to make the present disclosure complete and to fully inform those skilled in the art of the scope of the invention.

[0034] The terms used in this specification will be briefly explained, and the disclosed embodiments will be described in detail. The terms used in this specification have been selected to be as generally used as possible, taking into account their functions in this disclosure; however, these terms may vary depending on the intent of those skilled in the art, case law, the emergence of new technologies, etc. Additionally, in specific cases, terms may be arbitrarily selected by the applicant, and in such cases, their meanings will be described in detail in the relevant description of the invention. Therefore, the terms used in this disclosure should be defined not merely by their names, but based on their meanings and the content throughout this disclosure.

[0035] In this specification, singular expressions include plural expressions unless the context clearly specifies them as singular. Additionally, plural expressions include singular expressions unless the context clearly specifies them as plural. Throughout the specification, when a part is described as including a certain component, this means that, unless specifically stated otherwise, it does not exclude other components but may include additional components.

[0036] Additionally, the terms 'module' or 'part' as used in the specification refer to software or hardware components, and the 'module' or 'part' performs certain roles. However, the meaning of 'module' or 'part' is not limited to software or hardware. The 'module' or 'part' may be configured to reside in an addressable storage medium or configured to run on one or more processors. Thus, as an example, the 'module' or 'part' may include components such as software components, object-oriented software components, class components, and task components, and at least one of processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, or variables. The components and the functions provided within the 'module' or 'part' may be combined into a smaller number of components and 'modules' or 'parts', or further separated into additional components and 'modules' or 'parts'.

[0037] According to one embodiment of the present disclosure, a ‘module’ or ‘part’ may be implemented as a processor and memory. The term ‘processor’ should be broadly interpreted to include a general-purpose processor, a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a controller, a microcontroller, a state machine, etc. In some environments, the term ‘processor’ may refer to an application-specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc. The term ‘processor’ may also refer to a combination of processing devices, such as, for example, a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors combined with a DSP core, or any other combination of such configurations. Additionally, the term ‘memory’ should be broadly interpreted to include any electronic component capable of storing electronic information. 'Memory' may refer to various types of processor-readable media, such as Random Access Memory (RAM), Read-Only Memory (ROM), Non-Volatile Random Access Memory (NVRAM), Programmable Read-Only Memory (PROM), Erasable-Programmable Read-Only Memory (EPROM), Electrically Erasable PROM (EEPROM), Flash Memory, Magnetic or Optical Data Storage Devices, Registers, etc. If a processor can read information from memory and / or write information to memory, the memory is said to be in an electronic communication state with the processor. Memory integrated into a processor is in an electronic communication state with the processor.

[0038] In addition, terms such as first, second, A, B, (a), (b), etc. used in the following embodiments are used merely to distinguish one component from another, and the essence, order, or sequence of the said component is not limited by such terms.

[0039] Additionally, in the following embodiments, where it is stated that one component is 'connected', 'coupled', or 'joined' to another component, it should be understood that the component may be directly connected or joined to the other component, but that another component may also be 'connected', 'coupled', or 'joined' between each component.

[0040] Additionally, the terms 'comprises' and / or 'comprising' as used in the following embodiments do not exclude the presence or addition of one or more other components, steps, actions, and / or elements to the mentioned components, steps, actions, and / or elements.

[0041] Hereinafter, various embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0042] FIG. 1 is a drawing illustrating a data management system (100) according to one embodiment of the present disclosure. Referring to FIG. 1, the data management system (100) may include a plurality of devices (110, 120, 130, 140) and a management device (150) for acquiring data (112, 122, 132, 142, 144) associated with each of a plurality of assets (102, 104, 106, 107, 108). Here, an asset may refer to a unit that realizes the digitalization of a process, such as a physical or functional component that generates data in a process (e.g., a manufacturing process) or performs a function using usable data. Additionally, an asset may represent any tangible or intangible unit that is manageable and capable of mutual data exchange for the operation of the process. For example, an asset may correspond to at least one of a machine used in a process, a line of a process, a raw material used in a process, a product produced through a process, a factory, or a company, but is not limited thereto. Additionally, the data transmission and reception relationship and structure formed by a plurality of devices (110, 120, 130, 140) and a management device (150) that acquire data (112, 122, 132, 142, 144) associated with each of a plurality of assets (102, 104, 106, 107, 108) within a data management system (100) may be referred to as a data space. Here, the data space may represent a digital space that supports data sharing between a data sender (or data provider) and a data receiver (or data consumer). This data space can be separated from the physical space that forms the basis of the actual data. Additionally, data transactions, contracts, exchanges, and sharing can be performed within the data space through designated algorithms, protocols, etc.In the present disclosure, the data management system (100) may refer to a system that manages such data space.

[0043] Each of the plurality of devices (110, 120, 130, 140) can acquire data associated with at least one asset corresponding to the device among the plurality of assets (102, 104, 106, 107, 108). For example, the first device (110) can acquire data (112) associated with the first asset (102), the second device (120) can acquire data (122) associated with the second asset (104), the third device (130) can acquire data (132) associated with the third asset (106), and the fourth device (140) can acquire data (142) associated with the fourth asset (107) and data (144) associated with the fifth asset (108). The data may include, for example, at least one of operational information, status information, action plan information of the asset, or information about a product generated from the asset, but is not limited thereto.

[0044] According to one embodiment, a device (110, 120, 130) can acquire data (112, 122, 132) associated with an asset (102, 104, 106). In this case, the device (110, 120, 130) may be attached to the asset (102, 104, 106) or installed inside the asset (102, 104, 106). For example, the device (110, 120, 130) may include an on-device device.

[0045] According to one embodiment, the device (140) can acquire data (142, 144) associated with a plurality of assets (107, 108). At this time, the device (140) can manage the data (142, 144) associated with the plurality of assets (107, 108) individually or manage them in an integrated manner.

[0046] A management device (150) is connected to a plurality of devices (110, 120, 130, 140) within a data management system (100) and can manage a contract related to data transmission between a plurality of assets (102, 104, 106, 107, 108) corresponding to the plurality of devices (110, 120, 130, 140). Accordingly, based on the contract, a data sender among the plurality of devices (110, 120, 130, 140) can transmit at least a portion of the data sender's data to a data receiver among the plurality of devices (110, 120, 130, 140). At this time, the data transmitted by the data sender may include at least one of real-time data or semantic data associated with the asset. Here, real-time data refers to data measured in real-time from assets (e.g., temperature, production volume, etc.) and can be transmitted and received between assets in real-time. Real-time data may include, for example, raw data. Additionally, semantic data refers to data with defined meaning and context, and may include data that has been processed and managed into an information form that the device can interpret and that can be interoperable. Semantic data may include, for example, data in which the meaning of the data or the relationships between data are expressed through metadata, or data expressed in a structured form (e.g., RDF (resource description framework), OWL (web ontology language), etc.).

[0047] Before concluding a contract between assets, the data sender and the data receiver may register themselves with the management device (150). For convenience of explanation, the first device (110) is the data sender and the second device (120) is the data receiver. The management device (150) may, in response to receiving a request to register the first asset (102) from the first device (110), verify the validity of the first asset (102), and if the validity of the first asset (102) is verified, register the first asset (102). Additionally, the management device (150) may, in response to receiving a request to register the second asset (104) from the second device (120), verify the validity of the second asset (104), and if the validity of the second asset (104) is verified, register the second asset (104). Here, the fact that an asset is registered in the management device (150) may indicate that information associated with the asset is registered and stored in the management device (150). Additionally, the information associated with the asset may include unique information of the asset, such as the asset's identifier, metadata, operational status, function, etc. According to one embodiment, if the management device (150) receives a request to register an invalid asset, it may refuse the registration of the asset.

[0048] Once the registration of the data sender and the data receiver is completed, the management device (150) can mediate a contract related to data transmission between the data sender and the data receiver. For example, the management device (150) can transmit information related to the contract to the first device (110) in response to receiving information related to the contract from the second device (120). Additionally, the management device (150) can transmit information indicating whether the contract is accepted to the second device (120) in response to receiving information indicating whether the contract is accepted from the first device (110). Then, when the contract is completed, the management device (150) can store the contract information. Here, the contract information is information corresponding to the contract conditions and may include at least one of the type of data to be transmitted and received, the scope of the data, the content of the data, or the contract period.

[0049] After the contract is completed, if we look at the data transmission and reception process, first, the second device (120) can request provider information of data (112) associated with the first asset (102) from the management device (150). Then, in response to receiving the request for provider information of data (112) associated with the first asset (102) from the second device (120), the management device (150) can transmit information about the first device (110) associated with the first asset (102) to the second device (120). A second device (120) that has received information about a first device (110) associated with a first asset (102) may verify the validity of the first device (110) based on the information about the first device (110), and if the validity of the first device (110) is verified, may request the transmission of data (112) associated with the first asset (102) to the first device (110) through a communication interface. Then, the first device (110) that has received the request for transmission of data (112) associated with the first asset (102) may transmit at least a portion of the data (112) associated with the first asset (102) to the second device (120) through a communication interface based on a contract related to data transmission between the first asset (102) and the second asset (104). In this process, the management device (150) only provides information about the data provider (e.g., a list of providers), and since data transmission and reception are performed directly between the data sender and the data receiver, data can be shared more simply and quickly, making it possible to share real-time data. For example, at least a portion of the data (112) associated with the first asset (102) transmitted to the second device (120) may include real-time data associated with the first asset (102).

[0050] It may operate similarly even if the data sender is a device that acquires data associated with multiple assets (e.g., a fourth device (140)). For example, when the fourth device (140) that acquires data (142, 144) associated with multiple assets (107, 108) is the data sender, the fourth device (140) may transmit at least a portion of the data (142) associated with the fourth asset (107) to the second device (120) via a communication interface based on a contract related to data transmission between the fourth asset (107) and the second asset (104), and transmit at least a portion of the data (144) associated with the fifth asset (108) to the second device (120) via a communication interface based on a contract related to data transmission between the fifth asset (108) and the second asset (104). According to one embodiment, when the fourth device (140) generates data that integrates data (142) associated with the fourth asset (107) and data (144) associated with the fifth asset (108), it may transmit at least a portion of the integrated data to the second device (120) through a communication interface based on at least one of a contract for data transmission between the fourth asset (107) and the second asset (104) or a contract for data transmission between the fifth asset (108) and the second asset (104).

[0051] According to one embodiment, prior to the transmission or reception of data, a data recipient, i.e., a data consumer, may transmit a search request for data to a management device (150). In this case, the management device (150) may search for data associated with an asset registered in the management device (150) in response to the data search request. At this time, the management device (150) may search for data associated with an asset based on contract information concluded between assets. Alternatively, the management device (150) may search for data associated with an asset based on metadata registered and stored in the management device (150). Here, the metadata may include information regarding which data is associated with which asset.

[0052] According to one embodiment, data transmitted and received between a plurality of devices (110, 120, 130, 140) may include data processed into a predetermined data format. Here, the predetermined data format may include a data format according to an AAS (asset administration shell) model. According to one embodiment, data processed into a data format according to an AAS model may be converted into a data format according to a submodel (SM) profile and output.

[0053] According to one embodiment, each of the plurality of devices (110, 120, 130, 140) can generate data for managing assets through a machine learning model that takes data (112, 122, 132, 142, 144) associated with assets (102, 104, 106, 107, 108) as input. Accordingly, each of the plurality of assets (102, 104, 106, 107, 108) can be operated independently using the data for managing assets (102, 104, 106, 107, 108). For example, each of the plurality of devices (110, 120, 130, 140) can generate a control command based on data for managing an asset (102, 104, 106, 107, 108) and can transmit the generated control command to the asset. The data for managing the asset (102, 104, 106, 107, 108) may include at least one of data related to predictive maintenance of the asset (102, 104, 106, 107, 108) or action plan information of the asset (102, 104, 106, 107, 108). For example, data for managing assets (102, 104, 106, 107, 108) may be operational data of assets (102, 104, 106, 107, 108), and may include monitoring data, fault detection and prediction data, automated response plan data, etc. Such operational data may be used to automate and optimize process operations.

[0054] According to one embodiment, a machine learning model can be trained to predict and output future data of an asset (102, 104, 106, 107, 108) by taking data (112, 122, 132, 142, 144) associated with an asset (102, 104, 106, 107, 108) as input. For example, the machine learning model can output future state information, future operation information, etc. of an asset (102, 104, 106, 107, 108) based on data (112, 122, 132, 142, 144) associated with an asset (102, 104, 106, 107, 108), but is not limited thereto. In this case, each of the plurality of devices (110, 120, 130, 140) can generate at least one of data associated with the predictive maintenance of assets (102, 104, 106, 107, 108) or action plan information of assets (102, 104, 106, 107, 108) (e.g., action plan information associated with the production recipe of the assets) based on data output through a machine learning model.

[0055] Multiple assets (102, 104, 106, 107, 108) within the data management system (100) may have a hierarchical structure. For example, at least one asset (e.g., first asset (102)) among the multiple assets (102, 104, 106, 107, 108) may include at least one other asset (e.g., second asset (104), third asset (106), fourth asset (107), or fifth asset (108)). For example, when the first asset (102) corresponds to a factory, the second asset (104), third asset (106), fourth asset (107), and fifth asset (108) may correspond to machines within the factory. At this time, an asset that includes at least one other asset may be referred to as a parent asset, and an asset included in the other asset may be referred to as a child asset.

[0056] A device that acquires data associated with a higher asset can receive and manage data associated with a lower asset from a device that acquires data associated with a lower asset. For example, the first device (110) can receive at least a portion of data (122) associated with the second asset (104) from the second device (120) via a communication interface based on a contract related to data transmission between the first asset (102) and the second asset (104). Additionally, the first device (110) can receive at least a portion of data (132) associated with the third asset (106) from the third device (130) via a communication interface based on a contract related to data transmission between the first asset (102) and the third asset (106). Likewise, the first device (110) may receive at least a portion of data (142) associated with the fourth asset (107) from the fourth device (140) via a communication interface based on a contract related to data transmission between the first asset (102) and the fourth asset (107), and may receive at least a portion of data (144) associated with the fifth asset (108) from the fourth device (140) via a communication interface based on a contract related to data transmission between the first asset (102) and the fifth asset (108). Alternatively, the first device (110) may receive at least a portion of data integrating data (142) associated with the fourth asset (107) and data (144) associated with the fifth asset (108) from the fourth device (140) via a communication interface, based on at least one of a contract associated with data transmission between the first asset (102) and the fourth asset (107) or a contract associated with data transmission between the first asset (102) and the fifth asset (108).

[0057] According to one embodiment, a device for acquiring data associated with a higher asset receives data associated with a lower asset from a device for acquiring data associated with a lower asset, and can generate at least one of data for managing a higher asset or data for managing a lower asset. For example, the first device (110) can generate at least one of data for managing the first asset (102), data for managing the second asset (104), data for managing the third asset (106), data for managing the fourth asset (107), or data for managing the fifth asset (108) through a machine learning model that takes as input at least one of the following: at least a portion of data (122) associated with the second asset (104) received from the second device (120), at least a portion of data (132) associated with the third asset (106) received from the third device (130), at least a portion of data (142) associated with the fourth asset (107) received from the fourth device (140), or at least a portion of data (144) associated with the fifth asset (108) received from the fourth device (140).

[0058] Then, the first asset (102) may be operated using data for the management of the first asset (102). Alternatively, the first asset (102) may be operated using at least one of data for the management of the first asset (102), data for the management of the second asset (104), data for the management of the third asset (106), data for the management of the fourth asset (107), or data for the management of the fifth asset (108).

[0059] Additionally, when data for managing the second asset (104) is generated, the first device (110) transmits the data for managing the second asset (104) to the second device (120) via a communication interface; when data for managing the third asset (106) is generated, it transmits the data for managing the third asset (106) to the third device (130) via a communication interface; and when data for managing at least one of the fourth asset (107) or the fifth asset (108) is generated, it transmits the data for managing at least one of the fourth asset (107) or the fifth asset (108) to the fourth device (140) via a communication interface. In this case, the device that receives the data for managing the asset can generate a control command based on the data for managing the asset and can transmit the generated control command to the asset.

[0060] According to one embodiment, a device for acquiring data associated with a parent asset may apply at least some of the data associated with the parent asset or the data associated with the child asset to a digital twin model that has been pre-built for the parent asset and the child asset. For example, the first device (110) may apply at least a portion of the data (122) associated with the second asset (104) received from the second device (120), at least a portion of the data (132) associated with the third asset (106) received from the third device (130), at least a portion of the data (142) associated with the fourth asset (107) received from the fourth device (140), and at least a portion of the data (144) associated with the fifth asset (108) received from the fourth device (140) to a digital twin model that has been pre-built for the first asset (102), the second asset (104), the third asset (106), the fourth asset (107), and the fifth asset (108) received from the fourth device (140). Accordingly, the device acquiring data associated with the upper asset can perform simulations on the upper asset and the lower asset, and the simulation data can be used to detect problems that may occur in the process in advance.

[0061] According to one embodiment, a device for acquiring data associated with a parent asset can construct an ontology-based database based on data associated with a child asset. Here, the ontology-based database may include the meaning and relationships of the data associated with the child asset. For example, the ontology-based database may include graph data composed of nodes associated with the meaning of the data associated with the child asset and edges connecting each node associated with the relationships of the data associated with the child asset. The parent asset can improve knowledge inference and interoperability associated with the child asset by utilizing the ontology-based database.

[0062] To describe the process of adding a new asset within a data management system (100) built as a data space, a management device (150) may receive a request to add a new asset from a device that acquires data associated with the new asset. In response to receiving the request to add a new asset, the management device (150) may verify the validity of the new asset, and if the validity of the new asset is verified, it may transmit information associated with the addition of the new asset to a device that acquires data associated with a parent asset (e.g., a first device (110)).

[0063] Looking at the process of changing information within a data management system (100) built as a data space, a management device (150) may receive a request to change information associated with an asset from a device corresponding to the asset whose information has been changed. In response to receiving the request to change information associated with an asset, the management device (150) may identify an asset that has a contractual relationship with the asset whose information has been changed. Then, the management device (150) may authenticate a connection between the asset whose information has been changed and the asset identified as having a contractual relationship with the asset whose information has been changed. Once authentication is complete, the device corresponding to the asset whose information has been changed may transmit at least a portion of the data associated with the asset obtained after the change of information to the device corresponding to the asset identified as having a contractual relationship through a communication interface.

[0064] According to one embodiment, a communication interface used for transmitting and receiving data, that is, a communication interface used for connecting between a plurality of devices (110, 120, 130, 140), may include a first communication interface operating based on a first network layer for real-time data transmission and a second communication interface operating based on a second network layer for semantic data transmission. The first communication interface may include, for example, at least one of a remote procedure call (RPC) interface or an open platform communications unified architecture (OPC UA) interface.

[0065] According to one embodiment, a device for acquiring data associated with a top-level asset may transmit at least a portion of the data to an external device through a communication interface different from the communication interface used for connecting between a plurality of devices (110, 120, 130, 140). For example, if the data space established by the data management system (100) illustrated in FIG. 1 is referred to as an internal data space, the device for acquiring data associated with a top-level asset may transmit and receive data with a device in an external data space. In this case, the communication interface used for transmitting and receiving data in the external data space may be different from the communication interface used for transmitting and receiving data in the internal data space. According to one embodiment, the communication interface used for transmitting and receiving data in the external data space may include a blockchain-based authentication procedure for the asset. For example, the device for acquiring data associated with a top-level asset may perform a blockchain-based authentication procedure (e.g., a decentralized identifier (DID) authentication procedure) before transmitting at least a portion of the data to an external device.

[0066] FIG. 2 is a schematic diagram showing a configuration in which an information processing system (230) is connected to communicate with a plurality of user terminals (210_1, 210_2, 210_3) in relation to data processing according to one embodiment of the present disclosure. The information processing system (230) (e.g., the data management system (100) of FIG. 1) may include system(s) capable of providing a data processing service (e.g., a data management service). In one embodiment, the information processing system (230) may include one or more server devices and / or databases capable of storing, providing, and executing computer-executable programs (e.g., downloadable applications) and data related to the data processing service, or one or more distributed computing devices and / or distributed databases based on cloud computing services. For example, the information processing system (230) may include separate systems (e.g., servers) for the data processing service.

[0067] Data processing services, etc. provided by the information processing system (230) can be provided to the user through a data processing application, a web browser application, etc. installed on each of the multiple user terminals (210_1, 210_2, 210_3).

[0068] Multiple user terminals (210_1, 210_2, 210_3) can communicate with an information processing system (230) through a network (220). The network (220) can be configured to enable communication between the multiple user terminals (210_1, 210_2, 210_3) and the information processing system (230). Depending on the installation environment, the network (220) may be configured as a wired network such as Ethernet, Power Line Communication, telephone line communication devices and RS-serial communication, a mobile communication network, a Wireless LAN (WLAN), Wi-Fi, Bluetooth and ZigBee, or a combination thereof. The communication method is not limited and may include not only communication methods utilizing communication networks that the network (220) may include (e.g., mobile communication network, wired internet, wireless internet, broadcasting network, satellite network, etc.) but also short-range wireless communication between user terminals (210_1, 210_2, 210_3).

[0069] For example, multiple user terminals (210_1, 210_2, 210_3) can transmit a data processing request and a command associated with a user request for data processing to an information processing system (230) through a network (220), and the information processing system (230) can receive this.

[0070] In FIG. 2, a mobile phone terminal (210_1), a tablet terminal (210_2), and a PC terminal (210_3) are illustrated as examples of user terminals, but are not limited thereto. The user terminals (210_1, 210_2, 210_3) may be any computing device capable of wired and / or wireless communication and capable of installing and running data processing applications. For example, user terminals may include smartphones, mobile phones, navigation systems, computers, laptops, digital broadcasting terminals, PDAs (Personal Digital Assistants), PMPs (Portable Multimedia Players), tablet PCs, game consoles, wearable devices, IoT (Internet of Things) devices, VR (Virtual Reality) devices, AR (Augmented Reality) devices, etc. Additionally, FIG. 2 illustrates three user terminals (210_1, 210_2, 210_3) communicating with an information processing system (230) through a network (220), but is not limited thereto, and may be configured so that a different number of user terminals communicate with an information processing system (230) through a network (220).

[0071] FIG. 3 is a block diagram showing the internal configuration of a user terminal (210) and an information processing system (230) according to one embodiment of the present disclosure. The user terminal (210) may refer to any computing device capable of executing data processing applications, etc., and capable of wired / wireless communication, and may include, for example, the mobile phone terminal (210_1), tablet terminal (210_2), PC terminal (210_3) of FIG. 2. As illustrated, the user terminal (210) may include a memory (312), a processor (314), a communication module (316), and an input / output interface (318). Similarly, the information processing system (230) may include a memory (332), a processor (334), a communication module (336), and an input / output interface (338). As illustrated in FIG. 3, the user terminal (210) and the information processing system (230) may be configured to communicate information and / or data through the network (220) using their respective communication modules (316, 336). Additionally, the input / output device (320) may be configured to input information and / or data to the user terminal (210) or output information and / or data generated from the user terminal (210) through the input / output interface (318).

[0072] The memory (312, 332) may include any non-transient computer-readable recording medium. According to one embodiment, the memory (312, 332) may include a non-perishable permanent mass storage device such as ROM (read-only memory), a disk drive, an SSD (solid-state drive), or a flash memory. As another example, a non-perishable permanent mass storage device such as ROM, an SSD, a flash memory, or a disk drive may be included in the user terminal (210) or the information processing system (230) as a separate permanent storage device distinct from the memory. Additionally, the memory (312, 332) may store an operating system and at least one program code (e.g., code for an application associated with a data processing service).

[0073] These software components may be loaded from a computer-readable recording medium separate from memory (312, 332). This separate computer-readable recording medium may include a recording medium that can be directly connected to the user terminal (210) and the information processing system (230), for example, a computer-readable recording medium such as a floppy drive, disk, tape, DVD / CD-ROM drive, or memory card. As another example, the software components may be loaded into memory (312, 332) via a communication module (316, 336) rather than a computer-readable recording medium. For example, at least one program may be loaded into memory (312, 332) based on a computer program (e.g., an application associated with a data processing service, etc.) that is installed by files provided through a network (220) by developers or a file distribution system that distributes installation files for the application.

[0074] The processor (314, 334) may be configured to process instructions of a computer program by performing basic arithmetic, logic, and input / output operations. Instructions may be provided to the processor (314, 334) by memory (312, 332) or a communication module (316, 336). For example, the processor (314, 334) may be configured to execute instructions received according to program code stored in a recording device such as memory (312, 332).

[0075] The communication module (316, 336) may provide a configuration or function for the user terminal (210) and the information processing system (230) to communicate with each other via the network (220), and may provide a configuration or function for the user terminal (210) and / or the information processing system (230) to communicate with another user terminal or another system (e.g., a separate cloud system). For example, a request or data (e.g., a data processing request or data, etc.) generated by the processor (314) of the user terminal (210) according to program code stored in a recording device such as memory (312) may be transmitted to the information processing system (230) via the network (220) under the control of the communication module (316). Conversely, a control signal or command provided under the control of the processor (334) of the information processing system (230) can be received by the user terminal (210) through the communication module (336) and the network (220) via the communication module (316) of the user terminal (210).

[0076] The input / output interface (318) may be a means for interfacing with an input / output device (320). As an example, the input device may include a device such as a camera including an audio sensor and / or an image sensor, a keyboard, a microphone, or a mouse, and the output device may include a device such as a display, a speaker, or a haptic feedback device. As another example, the input / output interface (318) may be a means for interfacing with a device in which the configuration or function for performing input and output is integrated into one, such as a touchscreen. Although the input / output device (320) is depicted in FIG. 3 as not being included in the user terminal (210), it is not limited thereto and may be configured as a single device with the user terminal (210). Additionally, the input / output interface (338) of the information processing system (230) may be a means for interfacing with a device (not shown) for input or output that is connected to the information processing system (230) or that the information processing system (230) may include. In FIG. 3, the input / output interface (318, 338) is shown as an element configured separately from the processor (314, 334), but is not limited thereto, and the input / output interface (318, 338) may be configured to be included in the processor (314, 334).

[0077] The user terminal (210) and the information processing system (230) may include more components than those of FIG. 3. However, it is not necessary to clearly illustrate most of the conventional technical components. In one embodiment, the user terminal (210) may be implemented to include at least some of the input / output devices (320) described above. Additionally, the user terminal (210) may further include other components such as a transceiver, a GPS (Global Positioning System) module, a camera, various sensors, a database, etc. For example, if the user terminal (210) is a smartphone, it may include components that are generally included in a smartphone, and may be implemented to include various components such as an accelerometer, a gyroscope, a microphone module, a camera module, various physical buttons, buttons using a touch panel, input / output ports, and a vibrator for vibration.

[0078] According to one embodiment, the processor (314) of the user terminal (210) may be configured to operate a data processing application or a web browser application that provides data processing services. At this time, program code associated with the application may be loaded into the memory (312) of the user terminal (210). While the application is operating, the processor (314) of the user terminal (210) may receive information and / or data provided from an input / output device (320) through an input / output interface (318) or receive information and / or data from an information processing system (230) through a communication module (316), and may process the received information and / or data and store it in the memory (312). Additionally, such information and / or data may be provided to the information processing system (230) through the communication module (316).

[0079] While the data processing application is in operation, the processor (314) may receive voice data, text, images, videos, etc., that are input or selected through an input device such as a touch screen, keyboard, audio sensor and / or image sensor, camera, microphone, etc., connected to the input / output interface (318), and may store the received voice data, text, images and / or videos, etc. in memory (312) or provide them to an information processing system (230) through a communication module (316) and a network (220). In one embodiment, the processor (314) may receive user input input through an input device and provide data / requests corresponding to the received user input to an information processing system (230) through a network (220) and a communication module (316).

[0080] The processor (314) of the user terminal (210) can transmit information and / or data to an input / output device (320) through an input / output interface (318) and output it. For example, the processor (314) of the user terminal (210) can output the processed information and / or data through an output device (320), such as a display output device (e.g., touch screen, display, etc.) or a voice output device (e.g., speaker).

[0081] The processor (334) of the information processing system (230) may be configured to manage, process, and / or store information and / or data received from a plurality of user terminals (210) and / or a plurality of external systems. The information and / or data processed by the processor (334) may be provided to the user terminals (210) through a communication module (336) and a network (220).

[0082] FIG. 4 is a diagram illustrating the configuration of a device (400) within a data management system according to one embodiment of the present disclosure. The device (400) illustrated in FIG. 4 may be a device (e.g., a second device (120), a third device (130), or a fourth device (140)) corresponding to a sub-asset among a plurality of assets within a data management system (e.g., the data management system (100) of FIG. 1). Referring to FIG. 4, the device (400) may acquire data associated with an asset. To this end, the device (400) may include a communication circuit (or communication module) (410), a memory (420), and a processor (430). However, the configuration of the device (400) is not limited thereto. According to various embodiments, the device (400) may omit at least one of the above-described components and may include at least one additional component. As an example, the device (400) may include a display for displaying data.

[0083] The communication circuit (410) can support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between the device (400) and an external device, and the performance of communication through the established communication channel. For example, the communication circuit (410) can provide a configuration or function for the device (400) and the external device to communicate with each other through a network. For example, control signals, commands, data, etc. provided under the control of the processor (430) of the device (400) can be transmitted to the external device through the communication circuit (410) and the network, and through the communication circuit of the external device. For example, the device (400) can transmit at least a portion of the data associated with assets to the external device through the communication circuit (410).

[0084] The memory (420) may store various data used by at least one other component of the device (400), e.g., the processor (430). The data may include, for example, input data or output data for software (or programs) and related instructions. According to one embodiment, the memory (420) may store data associated with assets.

[0085] The processor (430) can execute software (or a program) to control at least one other component (e.g., a hardware or software component) of the device (400) connected to the processor (430) and can perform various data processing or operations. According to one embodiment, as at least part of the data processing or operations, the processor (430) can load instructions or data received from another component (e.g., a communication circuit (410)) into volatile memory, process the instructions or data stored in volatile memory, and store the resulting data in non-volatile memory. In FIG. 4, the processor (430) is depicted as a single processor, but this is for convenience of explanation only, and the processor (430) may include a plurality of processors.

[0086] According to one embodiment, the processor (430) may perform functions related to the management of data associated with an asset. To perform functions related to the management of data associated with an asset, the processor (430) may execute at least one computer-readable program contained in memory (420). Here, the at least one program may include instructions for acquiring data associated with an asset, processing the acquired data, generating data for the management of an asset through a machine learning model that takes the acquired data as input, and transmitting and receiving data. For convenience of explanation, in the following description, the execution of at least one program by the processor (430) to perform functions related to the management of data associated with an asset may be described as the processor (430) performing functions related to the management of data associated with an asset. For example, the inclusion of instructions related to the management of data associated with an asset by at least one program may be a description corresponding to the processor (430) performing functions related to the management of data associated with an asset.

[0087] The processor (430) may include a data acquisition module (432), a data processing module (434), and an AI module (436) for managing data associated with assets. However, the types of components included in the processor (430) are classified according to functions related to the management of data associated with assets, and the types and number thereof are not limited thereto. Additionally, at least one of the components included in the processor (430) may be implemented in the form of an instruction stored in memory (420).

[0088] The data acquisition module (432) can acquire data associated with an asset corresponding to the device (400). The data may include, for example, at least one of operation information, status information, action plan information, or information about a product generated from the asset, but is not limited thereto.

[0089] According to one embodiment, the data acquisition module (432) can acquire data associated with an asset. In this case, the device (400) may be attached to the asset or installed inside the asset. For example, the device (400) may include an on-device device.

[0090] According to one embodiment, the data acquisition module (432) can acquire data associated with a plurality of assets. At this time, the device (400) can manage the data associated with the plurality of assets individually or manage them in an integrated manner.

[0091] The data processing module (434) can process the data obtained through the data acquisition module (432) into a predetermined data format. The predetermined data format may include a data format according to an AAS model. According to one embodiment, the data processed into a data format according to an AAS model may be converted into a data format according to a sub-model profile.

[0092] The AI ​​module (436) can generate data for asset management through a machine learning model that takes data associated with the asset as input. The data for asset management may include at least one of data associated with predictive maintenance of the asset or action plan information of the asset. For example, the data for asset management may be operational data of the asset, including monitoring data, fault detection and prediction data, automated response plan data, etc. Such operational data may be used to automate and optimize process operations.

[0093] FIG. 5 is a diagram illustrating the configuration of another device (500) within a data management system according to one embodiment of the present disclosure. The device (500) illustrated in FIG. 5 may be a device (e.g., the first device (110) of FIG. 1) corresponding to a higher asset among a plurality of assets within a data management system (e.g., the data management system (100) of FIG. 1). Referring to FIG. 5, the device (500) may acquire data associated with an asset. To this end, the device (500) may include a communication circuit (or communication module) (510), a memory (520), and a processor (530). However, the configuration of the device (500) is not limited thereto. According to various embodiments, the device (500) may omit at least one of the above-described components and may include at least one additional component. As an example, the device (500) may include a display for displaying data.

[0094] The communication circuit (510) can support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between the device (500) and an external device, and the performance of communication through the established communication channel. For example, the communication circuit (510) can provide a configuration or function for the device (500) and the external device to communicate with each other through a network. For example, control signals, commands, data, etc. provided under the control of the processor (530) of the device (500) can be transmitted to the external device through the communication circuit (510) and the network, and through the communication circuit of the external device. For example, the device (500) can receive at least a portion of data associated with assets from the external device through the communication circuit (510).

[0095] The memory (520) may store various data used by at least one other component of the device (500), e.g., the processor (530). The data may include, for example, input data or output data for software (or programs) and related instructions. According to one embodiment, the memory (520) may store data associated with assets.

[0096] The processor (530) can execute software (or a program) to control at least one other component (e.g., a hardware or software component) of the device (500) connected to the processor (530) and can perform various data processing or operations. According to one embodiment, as at least part of the data processing or operations, the processor (530) can load instructions or data received from another component (e.g., a communication circuit (510)) into volatile memory, process the instructions or data stored in volatile memory, and store the resulting data in non-volatile memory. In FIG. 4, the processor (530) is depicted as a single processor, but this is for convenience of explanation only, and the processor (530) may include multiple processors.

[0097] According to one embodiment, the processor (530) may perform functions related to the management of data associated with an asset. To perform functions related to the management of data associated with an asset, the processor (530) may execute at least one computer-readable program contained in memory (520). Here, the at least one program may include instructions for acquiring data associated with an asset, processing the acquired data, generating data for the management of the asset through a machine learning model that takes the acquired data as input, applying the acquired data to a digital twin model, and transmitting and receiving data. For convenience of explanation, in the following description, the execution of at least one program by the processor (530) to perform functions related to the management of data associated with an asset may be described as the processor (530) performing functions related to the management of data associated with an asset. For example, the fact that at least one program includes instructions related to the management of data associated with an asset may be a description corresponding to the processor (530) performing functions related to the management of data associated with an asset.

[0098] The processor (530) may include a data acquisition module (532), a data processing module (534), an AI module (536), and a DT module (538) for managing data associated with assets. However, the types of components included in the processor (530) are classified according to functions related to the management of data associated with assets, and the types and number thereof are not limited thereto. Additionally, at least one of the components included in the processor (530) may be implemented in the form of an instruction stored in memory (520).

[0099] The data acquisition module (532) can acquire data associated with an asset corresponding to the device (500). The data may include, for example, at least one of operation information, status information, action plan information of the asset, or information about a product generated from the asset, but is not limited thereto.

[0100] According to one embodiment, the data acquisition module (532) can acquire data associated with an asset. In this case, the device (500) may be attached to the asset or installed inside the asset. For example, the device (500) may include an on-device device.

[0101] According to one embodiment, the data acquisition module (532) can acquire data associated with a plurality of assets. At this time, the device (500) can manage the data associated with the plurality of assets individually or manage them in an integrated manner.

[0102] According to one embodiment, the data acquisition module (532) can acquire data associated with another asset (e.g., a sub-asset) from an external device (e.g., a device corresponding to the sub-asset) through a communication circuit (510). For example, the data acquisition module (532) can receive at least a portion of the data associated with another asset from an external device through the communication circuit (510) based on a contract with the other asset.

[0103] The data processing module (534) can process the data obtained through the data acquisition module (532) into a predetermined data format. The predetermined data format may include a data format according to an AAS model. According to one embodiment, the data processed into a data format according to an AAS model may be converted into a data format according to a sub-model profile.

[0104] The AI ​​module (536) can generate data for asset management through a machine learning model that takes data associated with the asset as input. The data for asset management may include at least one of data associated with predictive maintenance of the asset or action plan information of the asset. For example, the data for asset management may be operational data of the asset, including monitoring data, fault detection and prediction data, automated response plan data, etc. Such operational data may be used to automate and optimize process operations.

[0105] According to one embodiment, the AI ​​module (536) can generate at least one of data for managing an asset corresponding to the device (500) or data for managing other assets by using data associated with other assets. For example, the AI ​​module (536) can generate at least one of data for managing an asset corresponding to the device (500) or data for managing other assets through a machine learning model that takes data associated with other assets as input.

[0106] The DT module (538) can apply at least some of the data associated with the asset corresponding to the device (500) or the data associated with other assets to a pre-built digital twin model for the asset corresponding to the device (500) and other assets (e.g., sub-assets). For example, the DT module (538) can apply data acquired through the data acquisition module (532) or data processed by the data processing module (534) to the pre-built digital twin model for the asset corresponding to the device (500) and other assets. Accordingly, the device (500) can perform simulations for the asset corresponding to the device (500) and other assets, and the simulation data can be used to detect problems that may occur in the process in advance.

[0107] FIG. 6 is a diagram illustrating a network layer (602, 604) for data transmission according to an embodiment of the present disclosure. Referring to FIG. 6, a communication interface (602, 604) used for transmitting and receiving data (612, 614, 622, 624) between devices (610, 620) may include a first communication interface (602) operating based on a first network layer for transmitting real-time data (612, 622) and a second communication interface (604) operating based on a second network layer for transmitting semantic data (614, 624). Here, the real-time data (612, 622) is data measured in real-time from an asset (e.g., temperature, production volume, etc.) and may be transmitted and received in real-time between devices (610, 620). The real-time data (612, 622) may include, for example, raw data. Additionally, semantic data (614, 624) is data with defined meaning and context, and may include data processed and managed in an information form that can be interpreted by the device (610, 620) and has interoperability. Semantic data (614, 624) may include, for example, data in which the meaning of the data or the relationships between data are expressed through metadata, or data expressed in a structured form (e.g., RDF, OWL, etc.).

[0108] According to one embodiment, the first communication interface (602) for transmitting real-time data (612, 622) may include at least one of an RPC interface or an OPC UA interface.

[0109] FIG. 7 is a diagram illustrating a method for registering an asset according to an embodiment of the present disclosure. Referring to FIG. 7, a data management system (e.g., the data management system (100) of FIG. 1) may include a first device (710) that is a data sender, a second device (720) that is a data receiver, and a management device (730). In step 722, the second device (720) may request the management device (730) to register an asset corresponding to the second device (720).

[0110] A management device (730) that receives a request for registration of an asset corresponding to the second device (720) from the second device (720) can verify the validity of the asset corresponding to the second device (720) in step 732. At this time, if the asset corresponding to the second device (720) is not valid, the management device (730) may refuse to register the asset corresponding to the second device (720). If the validity of the asset corresponding to the second device (720) is verified, the management device (730) may register the asset corresponding to the second device (720). For example, the management device (730) may register and store information associated with the asset corresponding to the second device (720). Here, information associated with an asset corresponding to the second device (720) may include unique information of the asset, such as an identifier, metadata, operating status, function, etc. of the asset corresponding to the second device (720).

[0111] When the registration of an asset corresponding to the second device (720) is completed, the management device (730) can transmit a registration completion notification to the second device (720) in step 724. For example, the management device (730) can transmit a signal indicating a registration completion notification to the second device (720).

[0112] Likewise, in step 712, the first device (710) may request the management device (710) to register an asset corresponding to the first device (710).

[0113] A management device (730) that receives a request for registration of an asset corresponding to the first device (710) from the first device (710) can verify the validity of the asset corresponding to the first device (710) in step 734. At this time, if the asset corresponding to the first device (710) is not valid, the management device (730) may refuse to register the asset corresponding to the first device (710). If the validity of the asset corresponding to the first device (710) is verified, the management device (730) may register the asset corresponding to the first device (710). For example, the management device (730) may register and store information associated with the asset corresponding to the first device (710). Here, information associated with an asset corresponding to the first device (710) may include unique information of the asset, such as an identifier, metadata, operating status, function, etc. of the asset corresponding to the first device (710).

[0114] When the registration of an asset corresponding to the first device (710) is completed, the management device (730) can transmit a registration completion notification to the first device (710) in step 714. For example, the management device (730) can transmit a signal indicating a registration completion notification to the first device (710).

[0115] FIG. 7 illustrates a state in which the registration process of the second device (720), which is the data receiver, is performed before the registration process of the first device (710), which is the data sender, but is not limited thereto. According to various embodiments, the registration process of the first device (710), which is the data sender, may be performed before the registration process of the second device (720), which is the data receiver, and the registration process of the first device (710), which is the data sender, and the registration process of the second device (720), which is the data receiver, may be performed in parallel.

[0116] FIG. 8 is a diagram illustrating a method for contracting between assets according to one embodiment of the present disclosure. Referring to FIG. 8, a data management system (e.g., the data management system (100) of FIG. 1) may include a first device (810) as a data sender, a second device (820) as a data receiver, and a management device (830). As in FIG. 7, once the registration of the data sender and the data receiver is completed, the management device (830) may mediate a contract related to data transmission between the data sender and the data receiver. For example, in step 822, the second device (820) may transmit information related to the contract to the management device (830).

[0117] The management device (830) that receives information related to the contract from the second device (820) can transmit the information related to the contract to the first device (110) in step 832.

[0118] The first device (810), having received information related to the contract from the management device (830), can verify the information related to the contract in step 812. For example, the first device (810) can verify the validity of the asset corresponding to the second device (810), which is a party to the contract, as well as verify the contract conditions of the contract.

[0119] When verification is complete, the first device (810) may transmit information indicating whether the contract is accepted to the management device (830). Here, the information indicating whether the contract is accepted may include information indicating acceptance of the contract or information indicating rejection of the contract. For example, if the first device (810) succeeds in verifying the information associated with the contract, it may transmit information indicating acceptance of the contract to the management device (830). For another example, if the first device (810) fails to verify the information associated with the contract, it may transmit information indicating rejection of the contract to the management device (830).

[0120] The management device (830) that receives information indicating whether the contract is accepted from the first device (810) can transmit the information indicating whether the contract is accepted to the second device (120) in step 834.

[0121] According to one embodiment, the management device (830) may store contract information when a contract is concluded. Here, the contract information is information corresponding to the contract conditions and may include at least one of the type of data to be transmitted and received, the range of the data, the content of the data, or the contract period.

[0122] FIG. 9 is a diagram illustrating a method for transmitting and receiving data between assets according to an embodiment of the present disclosure. Referring to FIG. 9, a data management system (e.g., the data management system (100) of FIG. 1) may include a first device (910) as a data sender, a second device (920) as a data receiver, and a management device (930). As in FIG. 8, when a contract is concluded (or completed) between the data sender and the data receiver, data transmission and reception between the data sender and the data receiver may be performed.

[0123] In step 922, the second device (920) may request provider information of data associated with other assets (or data to be received) from the management device (150).

[0124] The management device (930), having received a request for data provider information from the second device (920), can transmit information about the first device (910), which is the data provider, to the second device (120) in step 932. Here, the information about the first device (910) may be included in the provider list.

[0125] The second device (120) that has received information about the first device (910) can verify the validity of the first device (910) based on the information about the first device (910) at step 924.

[0126] If the verification of the validity of the first device (910) fails, the second device (920) may not request the transmission of data to the first device (910). If the verification of the validity of the first device (910) succeeds, the second device (920) may, at step 926, request the transmission of data associated with an asset corresponding to the first device (910) to the first device (910) through a communication interface.

[0127] The first device (910), having received a request for data transmission from the second device (920), may, in step 912, transmit at least a portion of the data associated with the asset corresponding to the first device (910) to the second device (920) through a communication interface, based on a contract related to data transmission between the asset corresponding to the first device (910) and the asset corresponding to the second device (920). For example, the first device (910) may transmit data to the second device (920) that corresponds to the type of data, the scope of the data, and the content of the data included in the contract conditions.

[0128] In this process, the management device (930) only provides information on the data provider (e.g., a list of providers), and since data transmission and reception are performed directly between the data sender and the data receiver, data can be shared more simply and quickly, making it possible to share real-time data. For example, at least a portion of the data associated with the asset corresponding to the first device (910) transmitted to the second device (920) may include real-time data associated with the asset corresponding to the first device (910).

[0129] The above-described flowchart and description are merely examples and may be implemented differently in some embodiments. For instance, in some embodiments, the order of each step may be changed, some steps may be repeated, some steps may be omitted, or some steps may be added.

[0130] The method described above may be provided as a computer program stored on a computer-readable recording medium for execution on a computer. The medium may continuously store a program executable by a computer, or temporarily store it for execution or download. Additionally, the medium may be various recording or storage means in the form of a single or multiple hardware components combined, and may not be limited to a medium directly connected to a computer system but may exist distributed over a network. Examples of media may include magnetic media such as hard disks, floppy disks, and magnetic tapes; optical recording media such as CD-ROMs and DVDs; magneto-optical media such as floptical disks; and media configured to store program instructions, including ROM, RAM, and flash memory. Furthermore, other examples of media may include recording or storage media managed by app stores that distribute applications or sites and servers that supply or distribute various other software.

[0131] The methods, operations, or techniques of the present disclosure may be implemented by various means. For example, these techniques may be implemented in hardware, firmware, software, or a combination thereof. Those skilled in the art will understand that the various exemplary logical blocks, modules, circuits, and algorithmic steps described in connection with the disclosure herein may be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate such interchangeability between hardware and software, various exemplary components, blocks, modules, circuits, and steps have been generally described above in terms of their functional aspects. Whether such functions are implemented in hardware or in software depends on the design requirements imposed on the specific application and the overall system. Those skilled in the art may implement the functions described in various ways for each specific application, but such implementations should not be construed as departing from the scope of the present disclosure.

[0132] In a hardware implementation, the processing units used to perform the techniques may be implemented in one or more ASICs, DSPs, digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described in this disclosure, computers, or a combination thereof.

[0133] Accordingly, the various exemplary logic blocks, modules, and circuits described in connection with the present disclosure may be implemented or performed by any combination of general-purpose processors, DSPs, ASICs, FPGAs or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or those designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors coupled with a DSP core, or any other combination of configurations.

[0134] In firmware and / or software implementations, techniques may be implemented as instructions stored on a computer-readable medium such as random access memory (RAM), read-only memory (ROM), non-volatile random access memory (NVRAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable PROM (EEPROM), flash memory, compact disc (CD), magnetic or optical data storage devices, etc. The instructions may be executable by one or more processors, and may cause the processor(s) to perform specific aspects of the functions described in this disclosure.

[0135] When implemented in software, the techniques described above may be stored on a computer-readable medium as one or more instructions or code, or transmitted through a computer-readable medium. Computer-readable media include both computer storage media and communication media, including any medium that facilitates the transmission of a computer program from one place to another. Storage media may be any available media accessible by a computer. As a non-limiting example, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium accessible by a computer that can be used to transfer or store desired program code in the form of instructions or data structures. Additionally, any connection is appropriately referred to as a computer-readable medium.

[0136] For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair cable, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, coaxial cable, fiber optic cable, twisted pair cable, digital subscriber line, or wireless technologies such as infrared, radio, and microwave are included within the definition of a medium. As used herein, disks and discs include CDs, laser discs, optical discs, DVDs (digital versatile discs), floppy disks, and Blu-ray discs, wherein disks usually play data magnetically, whereas discs play data optically using a laser. The above combinations should also be included within the scope of computer-readable media.

[0137] The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other known form of storage medium. An exemplary storage medium may be connected to a processor so that the processor can read information from the storage medium or write information to the storage medium. Alternatively, the storage medium may be integrated into the processor. The processor and the storage medium may exist within an ASIC. The ASIC may exist within a user terminal. Alternatively, the processor and the storage medium may exist as separate components within the user terminal.

[0138] Although the embodiments described above have been described as utilizing aspects of the subject matter disclosed herein in one or more standalone computer systems, the present disclosure is not limited thereto and may be implemented in conjunction with any computing environment, such as a network or a distributed computing environment. Furthermore, aspects of the subject matter in the present disclosure may be implemented in a plurality of processing chips or devices, and storage may be similarly affected across a plurality of devices. Such devices may include PCs, network servers, and portable devices.

[0139] Although the present disclosure has been described in relation to some embodiments, various modifications and changes may be made without departing from the scope of the present disclosure as understood by a person skilled in the art to which the invention of the present disclosure pertains. Furthermore, such modifications and changes should be considered to fall within the scope of the claims appended to this specification. Explanation of the symbols

[0140] 100: Data Management System 102, 104, 106, 107, 108: Assets 110, 120, 130, 140: Device 112, 122, 132, 142, 144: Data 150: Management unit

Claims

Claim 1 In a data management system, a first device for acquiring first data associated with a first asset; a second device for acquiring second data associated with a second asset; and includes a management device connected to the first device and the second device, and managing a first contract associated with data transmission between the first asset and the second asset; the first device is configured to transmit at least a portion of the first data to the second device through a communication interface based on the first contract; the management device transmits information associated with the first contract to the first device in response to receiving information associated with the first contract from the second device, and transmits information indicating acceptance of the first contract to the second device in response to receiving information indicating acceptance of the first contract from the first device; and when the first contract is completed, the management device is configured to store contract information of the first contract, wherein the contract information includes at least one of the type of data to be transmitted and received, the range of the data, the content of the data, or the contract period; when the first asset is a parent asset of the second asset, data sharing between the first asset and the second asset is performed using the communication interface, and is managed by the management device and another management device. A data management system wherein data sharing between the first asset and another higher asset is performed using the communication interface and another communication interface, wherein the communication interface includes a registration procedure for the asset of the management device, and the other communication interface includes a blockchain-based authentication procedure for the asset of the other management device. Claim 2 A data management system according to claim 1, wherein the management device is configured to verify the validity of the first asset in response to receiving a request for registration of the first asset from the first device, and if the validity of the first asset is verified, register the first asset, and in response to receiving a request for registration of the second asset from the second device, verify the validity of the second asset, and if the validity of the second asset is verified, register the second asset. Claim 3 delete Claim 4 A data management system according to claim 1, wherein the management device, in response to receiving a request for provider information of data associated with the first asset from the second device, transmits information about the first device associated with the first asset to the second device, and the second device verifies the validity of the first device based on the information about the first device, and when the validity of the first device is verified, requests the transmission of data associated with the first asset to the first device through the communication interface. Claim 5 A data management system according to claim 1, wherein at least a portion of the first data transmitted to the second device includes real-time data associated with the first asset. Claim 6 A data management system according to claim 1, wherein the communication interface comprises at least one of an RPC (remote procedure call) interface or an OPC UA (open platform communications unified architecture) interface. Claim 7 A data management system according to claim 1, wherein the communication interface comprises a first communication interface operating based on a first network layer for real-time data transmission and a second communication interface operating based on a second network layer for semantic data transmission. Claim 8 A data management system according to claim 1, wherein at least a portion of the first data transmitted to the second device comprises data processed into a predetermined data format. Claim 9 In paragraph 8, the above-mentioned predetermined data format is a data management system including a data format according to an AAS (asset administration shell) model. Claim 10 In claim 1, the first device is a data management system configured to generate data for the management of the first asset through a machine learning model that takes the first data as input. Claim 11 A data management system according to claim 1, wherein the first device further acquires third data associated with at least one third asset and is configured to transmit at least a portion of the third data to the second device through the communication interface based on a second contract associated with data transmission between the at least one third asset and the second asset. Claim 12 A data management system according to claim 11, wherein the first device is configured to generate data by integrating the first data and the third data, and to transmit at least a portion of the integrated data to the second device through the communication interface based on at least one of the first contract or the second contract. Claim 13 A data management system according to claim 1, further comprising a third device for acquiring third data associated with a third asset, wherein the third device is configured to receive at least a portion of the first data from the first device through the communication interface based on a second contract associated with data transmission between the first asset and the third asset, and to receive at least a portion of the second data from the second device through the communication interface based on a third contract associated with data transmission between the second asset and the third asset. Claim 14 In claim 13, the third device is a data management system configured to generate at least one of data for managing the first asset, data for managing the second asset, or data for managing the third asset through a machine learning model that takes as input at least a portion of the first data received from the first device and at least a portion of the second data received from the second device. Claim 15 A data management system according to claim 14, wherein the third device is configured to transmit data for the management of the first asset to the first device through the communication interface when data for the management of the first asset is generated, and to transmit data for the management of the second asset to the second device through the communication interface when data for the management of the second asset is generated. Claim 16 In claim 13, the third device is a data management system configured to apply at least a portion of the first data received from the first device and at least a portion of the second data received from the second device to a digital twin model pre-built for the first asset, the second asset and the third asset. Claim 17 In paragraph 13, the third device is a data management system configured to transmit at least a portion of the third data to an external device through a communication interface other than the communication interface. Claim 18 In claim 17, the third device is a data management system configured to perform a blockchain-based authentication procedure before transmitting at least a portion of the third data to the external device. Claim 19 A data management system according to claim 13, wherein the management device is configured to receive a request for the addition of the fourth asset from a fourth device that acquires fourth data associated with the fourth asset, verify the validity of the fourth asset, and, if the validity of the fourth asset is verified, transmit information associated with the addition of the fourth asset to the third device. Claim 20 A data management system according to claim 1, wherein the management device authenticates a connection between the first device and the second device in response to receiving a request to change information associated with the first asset from the first device, and the first device is configured to transmit at least a portion of the first data associated with the first asset obtained after the change of information to the second device through the communication interface when the authentication is completed.

Images