KR102642572B1 - Modeling method and system for managing full cycle of object in linked data structure of digital twin data platform - Google Patents

Abstract

The present disclosure provides a modeling method for object life cycle management in a digital twin data platform linked data structure performed by at least one processor. The method is responsive to changing a first function of a particular object included in the digital twin model to a second function, providing a row containing a first revision identifier and a first session part identifier associated with the second function. adding to a table 1, adding a row including an instance identifier and a first session part identifier associated with a second function of a specific object to a second table, and object relationship information associated with a second function of a specific object and a first It may include adding a row containing a session part identifier to a third table.

Description

Digital twin data platform Modeling method and system for object life cycle management in linked data structure {MODELING METHOD AND SYSTEM FOR MANAGING FULL CYCLE OF OBJECT IN LINKED DATA STRUCTURE OF DIGITAL TWIN DATA PLATFORM}

This disclosure relates to a modeling method for managing the life cycle of an object in a digital twin data platform linked data structure. Specifically, a modeling method and system for managing the life cycle associated with a change in the function of an object in a digital twin data platform linked data structure. It's about.

Digital Twin technology is being used in the fields of cities, energy, transportation, manufacturing, and logistics to predict future situations and manage them efficiently. A digital twin is the implementation of machines, equipment, and objects from the real world into a virtual world inside a computer. Machines, equipment, objects, etc. included in the digital twin model are simulated in various operation methods, and through these simulations, problems in each operation method can be identified in advance.

A representative example of a digital twin model may be that equipment included in a semiconductor manufacturing plant is implemented in a virtual world. In other words, a digital twin model that reflects the internal space of the semiconductor manufacturing plant is created, and a plurality of semiconductor facilities can be placed in the digital twin model. Users can use the digital twin model to perform simulations such as relocating or removing specific facilities. Additionally, users can use digital twins to perform simulations for deploying new facilities. Users can change the operating parameters of each facility included in the digital twin model and perform a simulation of the manufacturing process. Through simulation using a digital twin, problems that may arise in the real world can be identified in advance in the digital twin model.

In order to implement this digital twin model, a digital twin data platform must be established. Here, the digital twin data platform can be understood as a database system for visually implementing the digital twin.

A relational database structure with high development convenience is used, and the database structure included in the digital twin data platform is mainly constructed. In this case, the digital twin data platform includes multiple tables, and relationships between two or more tables are formed.

However, after the construction of the digital twin data platform is completed, if changes are needed to specific functions of the digital twin model, the digital twin data platform must be redesigned. For example, when a specific function is changed or added to the digital twin model, at least one column associated with this function must be added to at least one table, and a change operation on the row associated with the added column is required. It must be done. When columns are added to the table in this way, the amount of additional work that must be processed later increases, requiring a lot of redesign time and a lot of labor.

Additionally, after the function of a specific object is changed in a digital twin model, a situation may arise when the function of a specific object must be rolled back to its previous function. Even if rollback of these object functions needs to be performed, the digital twin data platform must be redesigned or the stored tables of the database must be recovered using backed up data.

Accordingly, there is a need for a digital twin data platform that allows easy function change and rollback.

The present disclosure provides a modeling method for object life cycle management in a digital twin data platform linked data structure, a computer program and a device (system) stored in a recording medium to solve the above problems.

The present disclosure may be implemented in various ways, including as a method, device (system), and/or a computer program stored in a computer-readable storage medium.

According to an embodiment of the present disclosure, a modeling method for object life cycle management in a digital twin data platform linked data structure performed by at least one processor provides a first function of a specific object included in the digital twin model. 2 In response to changing to a function, adding a row to the first table including a first revision identifier and a first session part identifier associated with the second function, an instance identifier associated with the second function of the particular object. and adding a row containing a first session part identifier to a second table and adding a row containing the first session part identifier and object relationship information associated with a second function of a specific object to a third table. can do.

According to an embodiment of the present disclosure, attribute information of the instance associated with the first revision is recorded in the first table, detailed information about the instance associated with the instance identifier is recorded in the second table, and the source instance and the third table are recorded. Object relationship information about relationships between target instances may be recorded.

According to an embodiment of the present disclosure, the row added to the first table, the row added to the second table, and the row added to the third table may be linked to each other by the first session part identifier. there is.

According to one embodiment of the present disclosure, the first table may be stored in a non-relational database, and the second table and third table may be stored in a relational database.

According to an embodiment of the present disclosure, after adding a row including object relationship information associated with a second function of a specific object and a first session part identifier to a third table, a modeling method for object life cycle management, In response to changing the second function of the specific object to a third function, adding a row to the first table including a second revision identifier and a second session part identifier associated with the third function, the third function of the specific object adding a row containing an instance identifier and a second session part identifier associated with the function to the second table, and adding a row containing the second session part identifier and object relationship information associated with the third function of the specific object to the third table. Additional steps may be included.

According to an embodiment of the present disclosure, after adding a row including object relationship information associated with the second function of a specific object and a first session part identifier to the third table, the modeling method for object life cycle management is In response to receiving a user input for removing the second function of the specific object, deleting the row containing the second revision identifier in the first table, thereby removing the third function of the specific object from the digital twin model. And it may further include removing the second function of the specific object from the digital twin model by deleting the row including the first revision identifier in the first table.

According to one embodiment of the present disclosure, removing the third function of a specific object from the digital twin model includes deleting a row containing a second session part identifier from each of the second table and the third table, , the step of removing the second function of a specific object from the digital twin model may include deleting a row including the first session part identifier from each of the second table and the third table.

According to an embodiment of the present disclosure, after the step of removing the second function of a specific object, the modeling method for object life cycle management includes dividing the row containing the second session part identifier into the second table and the second table, respectively. It may further include restoring the third function by adding a row including a second revision identifier to the first table.

According to an embodiment of the present disclosure, a modeling method for object life cycle management includes storing a row including a first revision identifier deleted from a first table in a first temporary table, and storing a row including a first revision identifier deleted from a first table. 1, storing a row containing a session part identifier in a second temporary table, and storing a row containing the first session part identifier deleted from the third table in a third temporary table, and storing the deleted second session part identifier in a third temporary table. In response to the functionality not recovering for a predetermined period of time, the row containing the first revision identifier is deleted from the first temporary table, and the row containing the second session part identifier is deleted from the second temporary table and the third temporary table, respectively. can be deleted from

According to an embodiment of the present disclosure, a modeling method for object life cycle management includes, when the second function of a specific object is removed, identifying an instance identifier associated with a second function of a specific object, the identified instance identifier. The method may further include identifying a row from at least one of the first table, the second table, and the third table, and changing the instance identifier included in the identified row to an identifier related to an unspecified row.

In order to execute the modeling method for object life cycle management described above on a computer, a computer program stored in a computer-readable recording medium may be provided.

According to one embodiment of the present disclosure, the information processing system includes a memory and at least one processor connected to the memory and configured to execute at least one computer-readable program included in the memory, and the at least one program is a digital In response to changing the first function of a particular object included in the twin model to a second function, adding a row containing the first revision identifier and the first session part identifier associated with the second function to the first table and adding a row including an instance identifier and a first session part identifier associated with a second function of a specific object to the second table, and including object relationship information and a first session part identifier associated with a second function of the specific object. May contain commands for adding rows to a third table.

According to some embodiments of the present disclosure, the entire cycle (i.e., full cycle) associated with the functional change of the object included in the digital twin is recorded in a table, and the entire cycle of the object is recorded based on the cycle associated with the functional change recorded in the table. Can be easily managed.

According to some embodiments of the present disclosure, the functionality of an object may be rolled back to a previous time through the row associated with the functionality of the object being deleted from the table. Accordingly, rollback of object functions can be performed stably and quickly without changing the design of the database.

According to some embodiments of the present disclosure, the attribute table may be created using a non-relational database structure, and other tables may be created using a relational database structure. Additionally, the attribute table and other tables may be associated with each other based on the session part identifier. By using a digital twin data platform with this hybrid database structure, the scalability and compatibility of the digital twin data platform can be improved.

According to some embodiments of the present disclosure, when a row associated with a specific function is added to the table, the specific function may be added or changed in the digital twin model. Accordingly, the functions of the digital twin model can be easily changed.

The effects of the present disclosure are not limited to the effects mentioned above, and other effects not mentioned are clear to those skilled in the art (referred to as 'ordinary skilled in the art') from the description of the claims. It will be understandable.

Embodiments of the present disclosure will be described with reference to the accompanying drawings described below, in which like reference numerals indicate like elements, but are not limited thereto.
1 is a diagram illustrating a relationship between instances using graphic-based information, according to an embodiment of the present disclosure.
Figure 2 is a schematic diagram showing a configuration in which an information processing system is connected to communicate with a plurality of user terminals, according to an embodiment of the present disclosure.
Figure 3 is a block diagram showing the internal configuration of a user terminal and an information processing system according to an embodiment of the present disclosure.
4 is a diagram illustrating a class table, an instance table, and a tag table, according to an embodiment of the present disclosure.
5 is a diagram illustrating a relationship type table and a relationship table, according to an embodiment of the present disclosure.
FIG. 6 is a diagram illustrating an instance table and a tag table to which a row associated with a second function is added, according to an embodiment of the present disclosure.
FIG. 7 is a diagram illustrating a relationship type table, a relationship table, and an attribute table to which a row associated with a second function is added, according to an embodiment of the present disclosure.
FIG. 8 is a diagram illustrating an instance table and a tag table to which rows associated with the third function and the fourth function are added, according to an embodiment of the present disclosure.
FIG. 9 is a diagram illustrating a relationship type table, a relationship table, and an attribute table to which rows associated with a third function and a fourth function are added, according to an embodiment of the present disclosure.
FIG. 10 is a diagram illustrating information in which the relationship between instances is visualized, according to an embodiment of the present disclosure.
FIG. 11 is a diagram illustrating an instance table and a tag table from which a row associated with a third function has been deleted, according to an embodiment of the present disclosure.
FIG. 12 is a diagram illustrating a relationship type table, a relationship table, and an attribute table from which a row associated with a third function has been deleted, according to an embodiment of the present disclosure.
FIG. 13 is a diagram illustrating a visualization of an instance relationship changed as the third function of a specific object is deleted, according to an embodiment of the present disclosure.
FIG. 14 is a flowchart illustrating a modeling method for object life cycle management in a digital twin data platform linked data structure, according to an embodiment of the present disclosure.

Hereinafter, specific details for implementing the present disclosure will be described in detail with reference to the attached drawings. However, in the following description, detailed descriptions of well-known functions or configurations will be omitted if there is a risk of unnecessarily obscuring the gist of the present disclosure.

In the accompanying drawings, identical or corresponding components are given the same reference numerals. Additionally, in the description of the following embodiments, overlapping descriptions of identical or corresponding components may be omitted. However, even if descriptions of components are omitted, it is not intended that such components are not included in any embodiment.

Advantages and features of the disclosed embodiments and 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 and may be implemented in various different forms. The present embodiments are merely provided to ensure that the present disclosure is complete and that the present disclosure does not convey the scope of the invention to those skilled in the art. It is provided only for complete information.

Terms used in this specification will be briefly described, and the disclosed embodiments will be described in detail. The terms used in this specification are general terms that are currently widely used as much as possible while considering the function in the present disclosure, but this may vary depending on the intention or precedent of a technician working in the related field, the emergence of new technology, etc. In addition, in certain cases, there are terms arbitrarily selected by the applicant, and in this case, the meaning will be described in detail in the description of the relevant invention. Accordingly, the terms used in this disclosure should be defined based on the meaning of the term and the overall content of the present disclosure, rather than simply the name of the term.

In this specification, singular expressions include plural expressions, unless the context clearly specifies the singular. Additionally, plural expressions include singular expressions, unless the context clearly specifies plural expressions. When it is said that a certain part includes a certain element throughout the specification, this does not mean excluding other elements, but may further include other elements, unless specifically stated to the contrary.

Additionally, the term 'module' or 'unit' used in the specification refers to a software or hardware component, and the 'module' or 'unit' performs certain roles. However, 'module' or 'unit' is not limited to software or hardware. A 'module' or 'unit' may be configured to reside on an addressable storage medium and may be configured to run on one or more processors. Thus, as an example, a 'module' or 'part' refers to components such as software components, object-oriented software components, class components and task components, processes, functions and properties. , procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, or variables. Components and 'modules' or 'parts' may be combined into smaller components and 'modules' or 'parts' or further components and 'modules' or 'parts'. Could be further separated.

According to an embodiment of the present disclosure, a 'module' or 'unit' may be implemented with a processor and memory. 'Processor' should be interpreted broadly to include general-purpose processors, central processing units (CPUs), microprocessors, digital signal processors (DSPs), controllers, microcontrollers, state machines, etc. In some contexts, 'processor' may refer to an application-specific integrated circuit (ASIC), programmable logic device (PLD), field programmable gate array (FPGA), etc. 'Processor' refers to a combination of processing devices, for example, a combination of a DSP and a microprocessor, a combination of a plurality of microprocessors, a combination of one or more microprocessors in combination with a DSP core, or any other such combination of configurations. You may. Additionally, 'memory' should be interpreted broadly to include any electronic component capable of storing electronic information. 'Memory' refers to 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), May also refer to various types of processor-readable media, such as electrically erasable PROM (EEPROM), flash memory, magnetic or marking data storage, registers, etc. A memory is said to be in electronic communication with a processor if the processor can read information from and/or write information to the memory. The memory integrated into the processor is in electronic communication with the processor.

In the present disclosure, 'system' may include at least one of a server device and a cloud device, but is not limited thereto. For example, a system may consist of one or more server devices. As another example, a system may consist of one or more cloud devices. As another example, the system may be operated with a server device and a cloud device configured together.

In addition, terms such as first, second, A, B, (a), (b) used in the following embodiments are only used to distinguish one component from another component, and the terms The nature, sequence, or order of the relevant components are not limited.

Additionally, in the following embodiments, when a component is described as being 'connected', 'coupled' or 'connected' to another component, the component may be directly connected or connected to the other component. , it should be understood that another component may be 'connected', 'combined', or 'connected' between each component.

In addition, as used in the following embodiments, 'comprises' and/or 'comprising' means that the mentioned component, step, operation, and/or element includes one or more other components, steps, or operations. and/or the presence or addition of elements.

Before describing various embodiments of the present disclosure, the terms used will be explained.

In embodiments of the present disclosure, a 'class' may be a template for an instance containing the same or similar properties and methods. For example, a 'road_class' associated with the properties and behavior of a two-way national highway/road may be defined, and instances associated with each road may be created based on the 'road_class'. As another example, 'cross_road_class' associated with the properties and behavior of an intersection may be defined, and instances associated with each intersection may be created based on 'cross_road_class'.

In embodiments of the present disclosure, an 'instance' is the parent of a tag and may be a data set created from a class. For example, a specific class may be used and an instance associated with the class may be created. For example, 'road_class' may be used to create a first road instance and a second road instance.

In embodiments of the present disclosure, a 'tag' is a label for each data included in an instance and may be related to a comment on the instance.

In embodiments of the present disclosure, 'attribute' may relate to a characteristic about an instance or other data. Attributes can be associated with various characteristics such as size, price, volume, color, quantity, etc., and a unique identifier can be assigned to each attribute. Additionally, an attribute value may be determined for each attribute. For example, a first attribute identifier associated with the budget may be determined in the 'budget' instance, and '1,000,000 won' may be determined as the value for the first attribute. As another example, a second attribute identifier associated with the building height may be determined for the 'building' instance, and '3rd floor' may be determined as the value for the second attribute.

In embodiments of the present disclosure, a 'Digital Twin Model' may be a model that implements machines, equipment, objects, etc. in the real world in a virtual world in a computer.

In embodiments of the present disclosure, an 'object' may be an object, person, etc. included in a digital twin model. Objects can be associated with instances. Graphical elements can be used to allow objects to be visualized in a digital twin model. Additionally, the size, color, shape, etc. of the object may be determined based on the properties of the instance. For example, if the digital twin model is a model related to traffic flow, virtually realized objects of each road's facilities (e.g., overpasses, crosswalks, underpasses, signs, etc.) may be included in the digital twin model. As another example, if the digital twin model is a model related to a building, objects that are virtually realized facilities (eg, desks, chairs, air conditioners, elevators, stairs, etc.) within the building may be included in the digital twin model.

In an embodiment of the present disclosure, 'cycle' may be associated with the point in time when an object's function changes. In other words, a cycle may be associated with a revision in which the function of a specific object changes. For example, the first cycle may be associated with the time when the first revision in which the first function of a specific object is changed to the second function has progressed, and the second cycle may be related to the time in which the second revision has progressed in which the second function has been changed to the third function. It can be related to the point of view. Additionally, a full cycle may be associated with all revision points at which the functionality of a specific object was sequentially changed.

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

FIG. 1 is a diagram illustrating the relationship between instances using graphic-based information 110 and 120 according to an embodiment of the present disclosure. This graphic-based information 110, 120 can be output through a digital twin data platform. Here, the digital twin data platform includes at least one digital twin model and may be software and/or hardware for visualizing objects included in the digital twin model in the virtual world using graphic elements. Additionally, the digital twin data platform can visualize the relationships of each instance using graphic elements. Here, graphic elements may include colors, shapes, text, animation, etc.

As illustrated in FIG. 1 , instances 112 to 122 are output as specific graphic elements (eg, circles), and instances 112 to 122 with which relationships are formed may be connected with connection lines. Here, instances 112 to 122 may be associated with objects included in the digital twin model.

One instance 112 to 122 may be output as one graphic element. Based on data included in the connection table described later, it may be determined whether each instance 112 to 122 has a relationship.

As illustrated in the first graphic information 110 of FIG. 1, a relationship may be formed between each instance 112 to 118. With this relationship established, an instance 122 may be added to change the function of a specific object. As illustrated in the second graphic information 120 of FIG. 1, an instance 122 for changing the function of a specific object may be added. When an instance 122 for changing the function of a specific object is added, a row related to changing the function of the specific object may be inserted into a table stored in the database.

The database structure included in the digital twin data platform may be a mixed database structure including relational database (RDB: Relation DataBase) and non-relational database.

Multiple tables can be stored in a relational database. A relational database may include a class table, a relation table, a relation type table, an instance table, and a tag table. The class table contains information related to classes, and the relationship table may contain information about relationships between instances. Additionally, the relationship type table may include information about the role of each instance. For example, in a relationship formed between a first instance and a second instance, information about the role of the first instance and the role of the second instance may be included in the relationship type table. Additionally, the instance table may include information about the instance, and the tag table may include comments related to detailed information about the instance.

Meanwhile, an attribute table can be stored in a non-relational database. Attribute tables included in a non-relational database may not form relationships with other tables. A row containing a revision identifier and instance attribute information may be recorded in the attribute table. Here, the revision identifier may be associated with the number of changes (i.e., change cycle) to the function of a specific object included in the digital twin model. For example, if the revision identifier is 'Rev1', this may mean that the function of the object has been changed for the first time, and if the revision identifier is 'Rev2', this may mean that the function of the object has been changed for the second time. With reference to FIGS. 4 to 9, each column constituting each table will be described in detail later.

Figure 2 is a schematic diagram showing a configuration in which the information processing system 230 according to an embodiment of the present disclosure is connected to communicate with a plurality of user terminals 210_1, 210_2, and 210_3. As shown, a plurality of user terminals 210_1, 210_2, and 210_3 may be connected to the information processing system 230 that can provide a digital twin service through the network 220. Here, the digital twin service may be a service that can be accessed as a digital twin model.

In one embodiment, information processing system 230 may include one or more server devices and/or databases capable of storing, serving, and executing computer-executable programs (e.g., downloadable applications) and data associated with digital twin services, etc., or It may include one or more distributed computing devices and/or distributed databases based on cloud computing services. The digital twin service provided by the information processing system 230 may be provided to users through digital twin-related applications installed on each of the plurality of user terminals 210_1, 210_2, and 210_3. For example, the information processing system 230 may receive data from the user terminals 210_1, 210_2, and 210_3 through a digital twin-related application, etc., and process the received data. According to one embodiment, the information processing system 230 may include a digital twin data platform.

A plurality of user terminals 210_1, 210_2, and 210_3 may communicate with the information processing system 230 through the network 220. For example, a plurality of user terminals 210_1, 210_2, and 210_3 access the digital twin model implemented in the information processing system 230 through the network 220, and then display at least one object included in the digital twin model in three dimensions. You can rotate/zoom in/out. Additionally, a plurality of user terminals 210_1, 210_2, and 210_3 may obtain detailed information about a specific object included in the digital twin model.

The network 220 may be configured to enable communication between a plurality of user terminals 210_1, 210_2, and 210_3 and the information processing system 230. Depending on the installation environment, the network 220 may be, for example, a wired network such as Ethernet, a wired home network (Power Line Communication), a telephone line communication device, and RS-serial communication, a mobile communication network, a wireless LAN (WLAN), It may consist of wireless networks such as Wi-Fi, Bluetooth, and ZigBee, or a combination thereof. The communication method is not limited, and includes communication methods that utilize communication networks that the network 220 may include (e.g., mobile communication networks, wired Internet, wireless Internet, broadcasting networks, satellite networks, etc.) as well as user terminals (210_1, 210_2, 210_3) ) may also include short-range wireless communication between

In Figure 2, the mobile phone terminal (210_1), tablet terminal (210_2), and PC terminal (210_3) are shown as examples of user terminals, but they are not limited thereto, and the user terminals (210_1, 210_2, 210_3) use wired and/or wireless communication. This may be any computing device capable of installing and executing an application or a web browser. For example, user terminals include smartphones, mobile phones, navigation devices, computers, laptops, digital broadcasting terminals, PDAs (Personal Digital Assistants), PMPs (Portable Multimedia Players), tablet PCs, game consoles, and wearable devices ( It may include a wearable device), IoT (internet of things) device, VR (virtual reality) device, AR (augmented reality) device, set-top box, etc. In addition, in Figure 2, three user terminals (210_1, 210_2, 210_3) are shown as communicating with the information processing system 230 through the network 220, but this is not limited to this, and a different number of user terminals are connected to the network ( It may be configured to communicate with the information processing system 230 through 220).

Figure 3 is a block diagram showing the internal configuration of the user terminal 210 and the information processing system 230 according to an embodiment of the present disclosure. The user terminal 210 may refer to any computing device capable of executing digital twin-related applications, etc. and capable of wired/wireless communication, for example, the mobile phone terminal 210_1 and tablet terminal 210_2 in FIG. 2. , PC terminal (210_3), etc.

As shown, the user terminal 210 may include a memory 312, a processor 314, a communication module 316, and an input/output interface 318. Similarly, information processing system 230 may include memory 332, processor 334, communication module 336, and input/output interface 338. As shown in FIG. 3, the user terminal 210 and the information processing system 230 are configured to communicate information and/or data through the network 220 using respective communication modules 316 and 336. It can be. Additionally, the input/output device 320 may be configured to input information and/or data to the user terminal 210 through the input/output interface 318 or to output information and/or data generated from the user terminal 210.

Memories 312 and 332 may include any non-transitory computer-readable recording medium. According to one embodiment, the memories 312 and 332 are non-permanent mass storage devices such as read only memory (ROM), disk drive, solid state drive (SSD), flash memory, etc. It can be included. As another example, non-perishable mass storage devices such as ROM, SSD, flash memory, disk drive, etc. may be included in the user terminal 210 or the information processing system 230 as a separate persistent storage device that is distinct from memory. Additionally, the memories 312 and 332 may store an operating system and at least one program code (for example, code for a digital twin-related application installed and running on the user terminal 210, etc.).

These software components may be loaded from a computer-readable recording medium separate from the memories 312 and 332. This separate computer-readable recording medium may include a recording medium directly connectable to the user terminal 210 and the information processing system 230, for example, a floppy drive, disk, tape, DVD/CD- It may include computer-readable recording media such as ROM drives and memory cards. As another example, software components may be loaded into the memories 312 and 332 through a communication module rather than a computer-readable recording medium. For example, at least one program is loaded into memory 312, 332 based on a computer program installed by files provided over the network 220 by developers or a file distribution system that distributes installation files for applications. It can be.

The processors 314 and 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 processors 314 and 334 by memories 312 and 332 or communication modules 316 and 336. For example, the processors 314 and 334 may be configured to execute instructions received according to program codes stored in a recording device such as the memory 312 and 332.

The communication modules 316 and 336 may provide a configuration or function for the user terminal 210 and the information processing system 230 to communicate with each other through the network 220, and may provide a configuration or function for the user terminal 210 and/or information processing. The system 230 may provide a configuration or function for communicating with other user terminals or other systems (for example, a separate cloud system, etc.). For example, a request or data generated by the processor 314 of the user terminal 210 according to a program code stored in a recording device such as the memory 312 is transmitted through the network 220 under the control of the communication module 316. It may be delivered to processing system 230. Conversely, at least one of the control signals, commands, or data provided under the control of the processor 334 of the information processing system 230 passes through the communication module 336 and the network 220 to the communication module of the user terminal 210. It can be received by the user terminal 210 through 316.

The input/output interface 318 may be a means for interfacing with the input/output device 320. As an example, input devices may include devices such as cameras, keyboards, microphones, mice, etc., including audio sensors and/or image sensors, and output devices may include devices such as displays, speakers, haptic feedback devices, etc. You can. As another example, the input/output interface 318 may be a means for interfacing with a device that has components or functions for performing input and output, such as a touch screen, integrated into one. For example, the processor 314 of the user terminal 210 uses information and/or data provided by the information processing system 230 or another user terminal when processing instructions of a computer program loaded in the memory 312. A service screen, etc. constructed by doing so may be displayed on the display through the input/output interface 318. In FIG. 3 , the input/output device 320 is shown not to be included in the user terminal 210, but the present invention is not limited to this 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 connected to the information processing system 230 or means for interfacing with a device (not shown) for input or output that the information processing system 230 may include. It can be. In FIG. 3, the input/output interfaces 318 and 338 are shown as elements configured separately from the processors 314 and 334, but the present invention is not limited thereto, and the input/output interfaces 318 and 338 may be configured to be included in the processors 314 and 334. there is.

The user terminal 210 and information processing system 230 may include more components than those in FIG. 3 . However, there is no need to clearly show most prior art components. According to 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 global positioning system (GPS) module, a camera, various sensors, and a database.

While a program for an application providing a digital twin service is running, the processor 314 uses input devices such as a touch screen, a keyboard, a camera including an audio sensor and/or an image sensor, and a microphone connected to the input/output interface 318. It is possible to receive text, images, videos, voices, and/or actions that are input or selected through, and store the received text, images, videos, voices, and/or actions in the memory 312 or store them in the communication module 316 and It can be provided to the information processing system 230 through the network 220.

The processor 314 of the user terminal 210 manages, processes, and/or stores information and/or data received from the input/output device 320, other user terminals, the information processing system 230, and/or a plurality of external systems. It can be configured to do so. Information and/or data processed by processor 314 may be provided to information processing system 230 via communication module 316 and network 220. The processor 314 of the user terminal 210 may transmit information and/or data to the input/output device 320 through the input/output interface 318 and output the information. For example, the processor 314 outputs the received information and/or data, so that the received information and/or data is displayed on the screen of the user terminal 210, using a display device included in or connected to the user terminal 210. You can control it.

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. Information and/or data processed by the processor 334 may be provided to the user terminal 210 through the communication module 336 and the network 220. The information processing system 230 may include a hybrid database for digital twin services. According to one embodiment, the information processing system 230 may include relational databases and non-relational databases.

FIG. 4 is a diagram illustrating a class table 410, an instance table 420, and a tag table 430, according to an embodiment of the present disclosure. The tables 410, 420, and 430 illustrated in FIG. 4 may be created using a relational database structure. For example, a Relational DataBase Management System (RDBMS) may be used to create each of the class table 410, instance table 420, and tag table 430. The class table 410, instance table 420, and tag table 430 may be stored in a relational database.

The class table 410 is a table that defines classes, including class identifier (class code), ID, description, icon, class group (class_group), parent, dataset identifier (dataset_code), visual It may be composed of a column containing information about availability (visible), data type (data_type), and session part identifier (part_of_seesion). Here, the class identifier (class code) is a unique code assigned to the class, and a number may be recorded in the class identifier (class code) field. Additionally, the ID may be a class ID composed of a string, the description may be a comment for the class, and the icon may be a graphic element for the class. If the icon for the class is not used, NULL may be recorded in the icon field. Here, icons can be used to visualize objects in the digital twin model.

Additionally, the identifier for the group to which the class belongs may be recorded in the class_group field, and the identifier of the class corresponding to the parent of the class may be recorded in the parent field. In addition, the dataset identifier (dataset_code) field records the identifier of the dataset associated with the class, and the information on whether the class is visualized and output on the digital twin model is recorded in the visual status field (visible). You can. For example, if the class is visualized and output in a digital twin model, '1' may be recorded in the information field about whether it is visual, otherwise '0' may be recorded.

The session part identifier (part_of_session) may be a means to form links between rows included in each table. Each table according to an embodiment of the present disclosure may include a session part identifier. By using the session part identifier, the link structure of each data, i.e., row, can be identified, and the link structure of data for storage included in the hybrid database can be designed.

The instance table 420 is a table containing instance information, including an instance identifier (instance_code), a tag identifier (tag_code), a class identifier (class_code), a previous version (previous_version), a next version (next_version), and a session part identifier (part_of_seesion). It may be composed of a column containing . The instance identifier (instance_code) may be a unique code assigned to an instance, and the tag identifier (tag_code) may be a unique code assigned to a tag. Through a tag identifier (tag_code), a relationship can be formed between data (ie, rows) included in the instance table and data (ie, rows) included in the tag table. The class identifier (class_code) may be a unique code assigned to the class. Through the class identifier (class_code), a relationship can be formed between the instance table and the class table. The previous version (previous_version) and the next version (next_version) may be recorded as versions associated with the instance.

The tag table 430 is a table containing detailed information about the instance, including tag identifier (tag_code), instance identifier (instance_code), context identifier (context_code), ID, full ID (full_ID), description (description), and session part. It may consist of a column containing an identifier (part_of_seesion). The tag identifier (tag_code) is a unique code assigned to the tag and may be a number. Additionally, the instance identifier (instance_code) may be a unique code assigned to the instance. Through the instance identifier (instance_code), a relationship can be formed between the instance table and the tag table.

The context identifier (context_code) may be a context code associated with the instance. Additionally, the ID may be a string that briefly represents the instance, and the full ID (full_ID) may represent the instance as a long string. The string recorded in the ID and the string recorded in the entire ID may be the same or different. The description may be a comment about the instance.

FIG. 5 is a diagram illustrating a relationship type table 510 and a relationship table 520 according to an embodiment of the present disclosure. The tables 510 and 520 illustrated in FIG. 5 may be created using a relational database structure. For example, a Relational DataBase Management System (RDBMS) may be used to create the relationship type table 510 and the relationship table 520, respectively. The relationship type table 510 and relationship table 520 may be stored in a relational database.

The relationship type table 510 may record information related to the role of each instance in the relationship between instances recorded in the relationship table 520. As illustrated in Figure 5, the relationship type table 510 may be composed of a column including a relationship type identifier (relation_type_code), a description (description), and a session part identifier (part_of_seesion). Relationship type identifier (relation_type_code) is a unique code assigned to the relationship type, and description is a comment on the relationship type, which can be associated with the role between each instance. One included in the relationship type table 510 The row may be a row related to an instance relationship definition. For example, the first row included in the relationship type table 510 may be a row defining the relationship between the source instance and the target instance as an assembly relationship, , the second row included in the relationship type table 510 may be a row defining the relationship between the source instance and the target instance as a dataset relationship.

The relationship table 520 may be composed of columns including a relationship identifier (relation_code), a relationship type identifier (relation_type_code), a source instance (source), a target instance (target), and a session part identifier (part_of_seesion). Here, the relationship identifier (relation_code) may be a unique code assigned to the relationship, and the relationship type identifier (relation_type_code) may be a unique code assigned to the relationship type. A relationship between a relationship table and a relationship type table can be formed through a relationship type identifier (relation_type_code).

Meanwhile, the function of specific objects included in the digital twin model may change. For example, the information processing system may receive a first user input that changes a function of a specific object or adds a function to a specific object. At this time, the first user input may include data related to changing or adding functions. Based on data included in user input, new rows can be added to each table.

Hereinafter, with reference to FIGS. 6 and 7, the rows inserted into each table when the first function is changed to the second function will be described. Here, the first function may be an original function for a specific object included in the digital twin model, and the second function may be a function changed by updating the first function. Here, changing the function of an object may mean that the properties of the object, such as size, color, budget, etc., are changed. Additionally, objects included in the digital twin model may be associated with instances included in the database. For example, based on instance-related data included in at least one table, the corresponding object may be visualized in the digital twin model.

6 and 7, it may be assumed that the second function is a function related to the first revision (Rev1).

FIG. 6 is a diagram illustrating an instance table 610 and a tag table 620 to which a row associated with a second function has been added, according to an embodiment of the present disclosure. As illustrated in FIG. 6 , a row associated with a second function of a specific object may be added to the instance table 610 . Here, the row associated with the second function is illustrated as being located at the bottom. That is, instance information associated with the second function of a specific object is created, and a row containing this instance information may be added to the instance table 610.

Additionally, a row associated with the second function of a specific object may be added to the tag table 620. Here, the row associated with the second function is illustrated as being located at the bottom. That is, tag information associated with the second function of a specific object is generated, and a row containing this tag information may be added to the tag table 620.

FIG. 7 is a diagram illustrating a relationship type table 710, a relationship table 720, and an attribute table 730 to which a row associated with a second function is added, according to an embodiment of the present disclosure. As illustrated in FIG. 7 , a row associated with a second function of a specific object may be added to the relationship type table 710. Here, the row associated with the second function is illustrated as being located at the bottom. That is, relationship type information associated with the second function of a specific object is created, and a row containing this relationship type information may be added to the relationship type table 710. The row added to the bottom of the relationship type table 710 is illustrated as containing information (e.g., Successor) associated with the function of the source instance being inherited by the target instance. That is, the function of the source instance is inherited from the target instance. It is illustrated as being changed to the function of the instance, where the source instance may be associated with the first function of a specific object included in the digital twin model, and the target instance may be associated with the first function of the specific object.

Additionally, a row associated with the second function of a specific object may be added to the relationship table 720. Here, the row associated with the second function is illustrated as being located at the bottom. That is, relationship information of instances related to the second function of a specific object may be created, and a row containing this relationship information may be added to the relationship table 720. The row added to the bottom of the relationship table 720 may include a relationship identifier, a source instance identifier, and a target instance identifier. Additionally, a row added to the relationship table 720 may include a session part identifier.

Additionally, a row associated with the second function of a specific object may be added to the attribute table 730. That is, a row containing an instance identifier, a revision identifier, a part identifier, and at least one attribute information associated with the second function of a specific object may be added to the attribute table 730. Here, the attribute information may include an attribute identifier (att#n_class_code, where #n is a natural number) and a first attribute value (attribute#n, where #n is a natural number). The attribute identifier may be a unique code assigned to the attribute. Attributes may include various elements such as size, price, volume, color, etc., and a unique identifier may be assigned to each attribute.

Multiple attribute information may be associated with one instance. For example, multiple attributes may be determined for one instance. It is illustrated that rows containing a plurality of attribute information are recorded in the attribute table 730 of FIG. 7 . In FIG. 7, it is illustrated that first attribute information and second attribute information are associated with an instance having the identifier '10011'. Here, the first attribute identifier (att1_class_code) included in the first attribute information is '43' and the first attribute value (attribute1) for the first attribute is '10000000'. In addition, it is exemplified that the second attribute identifier (att2_class_code) included in the second attribute information is '44' and the second attribute value (attribute2) for the second attribute is 'URL1'. Here, 'URL1' may be associated with the address of an external device.

According to one embodiment, the attribute table 730 may be created using a non-relational database structure. For example, a non-relational DBMS (DataBase Management System) may be used to create the attribute table 730. As a non-relational DBMS, a NoSQL-based DBMS can be used.

As illustrated in FIGS. 6 and 7 , the row associated with the second function (i.e., the row of the last line) may include the same session part identifier (i.e., 203). Based on this session part identifier, a link may be formed between rows associated with the second function so that they may be related to each other.

Meanwhile, three or more attribute information may be recorded in the attribute table 730. Expansion of attribute information can be made if necessary. In other words, since the attribute table 730 is a non-relational database structure, it is not tied to columns, and if necessary, rows with n (n is a natural number) number of attribute information (i.e. attribute identifiers and attribute values) are attributes. Can be added to table 730. Accordingly, the number of columns included in a row may be different. For example, the first row may include two attribute information, the second row may include one attribute information, and the third row may include three attribute information.

As described above, when the function of a specific object is added/changed in the digital twin model, a row related to this function is added to each table, so that the function of the added/changed object can be reflected in each table. Accordingly, compared to the method of changing the overall structure of each table by adding a row to each table, the embodiment of the present disclosure simplifies the database change work and can dramatically save change time.

Meanwhile, the second function of a specific object included in the digital twin model may be changed to a third function, and the third function may be changed to a fourth function. For example, the information processing system receives a second user input to change the second function of a specific object to a third function, and then receives a third user input to change the third function of a specific object to a fourth function. can do. The second user input may include data associated with the third function, and a new row may be added to at least one table based on the data associated with the third function. The third user input may include data associated with the fourth function, and a new row may be added to at least one table based on the data associated with the fourth function.

Hereinafter, with reference to FIGS. 8 and 9, when the second function is changed to the third function and the third function is changed to the fourth function, the rows added to each table will be explained by example. Do this. Here, the third function may be a function changed by updating the second function, and the fourth function may be a function changed by updating the third function. Additionally, in FIGS. 8 and 9 , it may be assumed that the third function is a function associated with the second revision (Rev2), and the fourth function is a function associated with the third revision (Rev3).

FIG. 8 is a diagram illustrating an instance table 810 and a tag table 820 to which rows related to the third function and the fourth function have been added, according to an embodiment of the present disclosure. As illustrated in FIG. 8 , a row associated with the third function and a row associated with the fourth function of a specific object may be added to the instance table 810. That is, instance information related to the third function of a specific object may be created and a row containing this instance information may be added to the instance table 810. Afterwards, instance information associated with the fourth function of a specific object may be created and a row containing this instance information may be added to the instance table 810. Here, the row associated with the third function is illustrated as being the second row from the bottom, and the row associated with the fourth function is illustrated as being the row located at the bottom.

Additionally, a row associated with the third function of a specific object may be added to the tag table 820, and a row associated with the fourth function of a specific object may be added to the tag table 820. That is, tag information related to the third function of a specific object is generated, and a row containing this tag information may be added to the tag table 820. Afterwards, tag information associated with the fourth function of a specific object is generated, and a row containing this tag information may be added to the tag table 820. Here, the row associated with the third function is illustrated as being the second row from the bottom, and the row associated with the fourth function is illustrated as being the row located at the bottom.

FIG. 9 is a diagram illustrating a relationship type table 910, a relationship table 920, and an attribute table 930 to which rows associated with the third function and the fourth function are added, according to an embodiment of the present disclosure. As illustrated in FIG. 9 , a row associated with a third function of a specific object may be added to the relationship type table 910. That is, relationship type information related to the third function of a specific object is created, and a row containing this relationship type information may be added to the relationship type table 910. Afterwards, relationship type information associated with the fourth function of a specific object is generated, and a row containing this relationship type information may be added to the relationship type table 910. Here, the row associated with the third function is illustrated as being the second row from the bottom, and the row associated with the fourth function is illustrated as being the row located at the bottom.

In the relationship type table 910, the row with the description 'Successor' is illustrated as containing role information related to the function of the source instance being inherited to the target instance. That is, the row associated with the function of the source instance being changed to the function of the target instance may be a row with the description 'Successor'. Here, the source instance may be associated with the second function/third function of the digital twin model, and the target instance may be associated with the third function/fourth function of the digital twin model.

Additionally, a row associated with the third function and a row associated with the fourth function of a specific object may be added to the relationship table 920. That is, relationship information of instances related to the third function of a specific object may be created, and a row containing this relationship information may be added to the relationship table 920. Afterwards, relationship information of instances associated with the fourth function of a specific object is generated, and a row containing this relationship information may be added to the relationship table 920. Here, the row associated with the third function is illustrated as being the second row from the bottom, and the row associated with the fourth function is illustrated as being the row located at the bottom.

Each row included in the relationship table 920 may include a relationship identifier, a source instance identifier, and a target instance identifier. Additionally, rows included in the relationship table 920 may include a session part identifier.

Additionally, a row associated with a third function of a specific object may be added to the attribute table 930. That is, a row containing an instance identifier, a revision identifier, a part identifier, and at least one attribute information associated with the third function of a specific object may be added to the attribute table 930. Afterwards, a row containing an instance identifier, a revision identifier, a part identifier, and at least one attribute information associated with the fourth function of a specific object may be added to the attribute table 930. Referring to the second row having the revision identifier 'Rev2' in the attribute table 930 of FIG. 9, it is illustrated in FIG. 9 that the first attribute value (attribute1) associated with the second revision has been changed. Referring to the last row with the revision identifier 'Rev3' in the attribute table 930 of FIG. 9, it is illustrated in FIG. 9 that the first attribute value (attribute1) has changed in the third revision.

As illustrated in Figures 8 and 9, the row associated with the third function (second row from the bottom) may contain the same session part identifier (i.e., 204). Based on this session part identifier, a link may be formed between rows related to the third function and they may be related to each other. Additionally, the row associated with the fourth function (the bottom row) may contain the same session part identifier (i.e., 205). Based on this session part identifier, a link may be formed between rows related to the fourth function and they may be related to each other.

As described above, when the function of a specific object in the digital twin model is changed, a row related to this function is added to each table so that the changed function of the object can be reflected in the database.

Meanwhile, revision information of each instance can be visualized. For example, the relationship of each instance can be visualized based on data recorded in the relationship type table, relationship table, and tag table. According to one embodiment, in response to receiving user input requesting revision information, a process may proceed in which the relationships of each instance are visualized.

FIG. 10 is a diagram illustrating information 1000 in which the relationship between instances is visualized, according to an embodiment of the present disclosure. As illustrated in FIG. 10 , instances are displayed as specific graphic elements (eg, circles) and may be connected by connection lines between instances with which relationships are formed. One instance may be output as one graphic element (1010 to 1070). Based on data included in the connection table, the relationship of each instance may be determined.

The ID for the instance contained in the tag table can be used and displayed within the graphic element. Additionally, identification information about the relationship type may be output around the connection line connecting a plurality of instances. According to one embodiment, a description included in the relationship type table may be output around the connection line as identification information for the relationship type.

As illustrated in Figure 10, revision relationships can be visualized. In FIG. 10, the function of an instance 1040 with an ID of 'E28 data center BMS DATASET' is illustrated as an instance 1050 with an ID of 'E28 data center BMS DATASET{Rev1}'. In addition, the function of the instance 1050 with the ID 'E28 Data Center BMS DATASET{Rev1}' is changed to the instance 1060 with the ID 'E28 Data Center BMS DATASET{Rev2}', and the function of the instance 1060 with the ID 'E28 Data Center BMS DATASET{Rev2}' is changed. It is illustrated that the function of the instance 1060 with the ID 'BMS DATASET{Rev2}' has been changed to the instance 1070 with the ID 'E28 data center BMS DATASET{Rev3}'. Through the identification information for the relationship type displayed with the connection line being 'Successor', the instance 1040 associated with the original function is changed to the instance 1050 associated with the first revision, and the instance 1050 associated with the first revision It can be intuitively seen that is changed to the instance 1060 associated with the second revision, and the instance 1060 associated with the second revision is changed to the instance 1070 associated with the third revision.

Meanwhile, features associated with revisions may be removed. In this case, it is determined whether the revision associated with the function to be deleted is the latest revision (i.e., the last revision), and if it is determined that it is not the most recent revision, the revision is sequentially performed from the row associated with the most recent revision to the revision-related row associated with the function to be deleted. can be deleted. At this time, the session part identifier corresponding to the revision identifier is identified in the attribute table, and the row associated with the session part identifier can be deleted from each table.

With reference to FIGS. 11 and 12 , a method by which an object function is rolled back will be described.

FIG. 11 is a diagram illustrating an instance table 1110 and a tag table 1120 from which a row associated with a third function has been deleted according to an embodiment of the present disclosure, and FIG. 12 is a diagram illustrating a third function according to an embodiment of the present disclosure. This diagram illustrates the relationship type table 1210, relationship table 1220, and attribute table 1230 from which rows related to functions have been deleted.

In response to receiving a user input for removal of a third function for a specific object included in the digital twin model, a revision identifier and a session part identifier associated with the third function of the specific object may be identified. For example, based on rows included in the attribute table 1230, a revision identifier and a session part identifier associated with the third function of a specific object may be identified. 11 and 12, the third function and revision identifier are 'Rev2', and the session part identifier is '204'.

Before deleting the revision identifier 'Rev2' from each table, the rows associated with the revision identifier and the subsequently added revision identifier 'Rev3' must first be deleted from each table so that the third function of a specific object can be removed from the digital twin model. there is. To this end, the session part identifier associated with the revision identifier 'Rev3' is identified in the attribute table 1230, and the row associated with the session part identifier can be deleted from each table. As illustrated in the attribute table 1230 of FIG. 12, when the function associated with the revision identifier 'Rev3' is the fourth function and the part section identifier associated with the revision identifier 'Rev3' is recorded in the attribute table as '205', By deleting the row containing the part section identifier '205' (i.e., the bottom row) from each table, the fourth function of the specific object can be removed from the digital twin model. That is, a row containing the part section identifier '205' may be deleted from each of the instance table 1110, tag table 1120, relationship type table 1210, relationship table 1220, and attribute table 1230. That is, rows linked by the part session identifier '205' can be deleted from each table.

For row recovery related to the fourth function, rows deleted from each table (1110, 1120, 1210, 1220, and 1230) may be stored in a temporary table. According to one embodiment, a first temporary table for storing rows deleted from the instance table 1110 and a second temporary table for storing rows deleted from the tag table 1120 may be included in the digital twin data platform. . The first temporary table may be composed of a plurality of columns included in the instance table 1110, and the second temporary table may be composed of a plurality of columns included in the tag table 1120.

In addition, a third temporary table for storing rows deleted from the relationship type table 1210, a fourth temporary table for storing rows deleted from the relationship table 1220, and the deleted rows are stored in the attribute table 1230. A fifth temporary table for this purpose can be created in advance in the digital twin data platform. The third temporary table may be composed of a plurality of columns included in the relationship type table 1210, the fourth temporary table may be composed of a plurality of columns included in the relationship table 1220, and the fifth temporary table may be composed of an attribute table. It may be composed of a plurality of columns included in 1230. Each temporary table can only store rows for a predetermined time, and when the predetermined time elapses, rows stored in the temporary table can be automatically deleted.

According to one embodiment, the row associated with the fourth function deleted from the instance table 1110 is stored in the first temporary table, and the row associated with the fourth function deleted from the tag table 1120 is stored in the second temporary table. It can be. In addition, the row associated with the fourth function deleted from the relationship type table 1210 is stored in the third temporary table, the row associated with the fourth function deleted from the relationship table 1220 is stored in the fourth temporary table, and the attribute The row associated with the fourth function deleted from the table 1230 may be stored in the fifth temporary table.

Afterwards, the session part identifier associated with the revision identifier 'Rev2' is identified in the attribute table 1230, and the rows associated with the session part identifier are deleted from each table 1110, 1120, 1210, 1220, and 1230, thereby creating a specific object. A third function can be removed from the digital twin model. As illustrated in Figures 11 and 12, when the function associated with the revision identifier 'Rev2' is the third function and the part section identifier associated with the revision identifier 'Rev2' is recorded in the attribute table 1230 as '204', By deleting the row containing the part section identifier '204' from each table (1110, 1120, 1210, 1220, 1230), the third function of the specific object can be removed from the digital twin model. That is, a row containing the part section identifier '204' may be deleted from each of the instance table 1110, tag table 1120, relationship type table 1210, relationship table 1220, and attribute table 1230.

According to one embodiment, the row associated with the third function deleted from the instance table 1110 is stored in a first temporary table, and the row associated with the third function deleted from the tag table 1120 is stored in the second temporary table. It can be. Additionally, the row associated with the third function deleted from the relationship type table 1210 is stored in the third temporary table, the row associated with the third function deleted from the relationship table 1220 is stored in the fourth temporary table, and the attribute The row associated with the third function deleted from the table 1230 may be stored in the fifth temporary table.

Afterwards, the process of recovering the fourth function may proceed. Additionally, since only the third function is subject to removal and the fourth function is not, the process of recovering the fourth function may proceed. According to one embodiment, a row associated with the fourth function is extracted from the first temporary table and added to the instance table 1110, and a row associated with the fourth function is extracted from the second temporary table and added to the tag table 1120. It can be. Additionally, a row associated with the fourth function is extracted from the third temporary table and added to the relationship type table 1210, and a row associated with the fourth function is extracted from the fourth temporary table and added to the relationship table 1220. The fourth function of the specific object can be recovered by extracting the row associated with the fourth function from the fifth temporary table and adding it to the attribute table 1230.

In Figures 11 and 12, the row located in the second line from the bottom in each table is illustrated as being deleted. 11 and 12, deleted rows are illustrated as shaded. Here, the row located in the second line from the bottom in each table may be a row related to the third function of a specific object. Additionally, in Figures 11 and 12, it is illustrated that the row located at the bottom of each table is not deleted. Here, the row located at the bottom of each table may be a row related to the fourth function of a specific object.

Meanwhile, when the third function of a specific object is removed from the digital twin model, subsequent processing must be performed on instances associated with the third function of the specific object. In other words, the data contained in each table must be managed so that instances related to third functions do not form relationships with other instances. According to one embodiment of the present disclosure, an instance identifier associated with a third function of a specific object is identified, and a row containing the identified instance identifier may be identified from each table. Subsequently, the instance identifier included in the identified row can be changed to an identifier related to unspecified (eg, UNKNOWN). Accordingly, the instance associated with the deleted third function can be prevented from forming a relationship with another instance.

In the relationship table 1220 of FIG. 12, the identifier of the target instance in the bottom row is illustrated as being changed from '10012' to an identifier related to unspecified (eg, UNKNOWN).

FIG. 13 is a diagram illustrating a visualization of an instance relationship changed as the third function of a specific object is deleted, according to an embodiment of the present disclosure. Comparing Figures 10 and 13, it can be seen that the relationship between instances 1310, 1320, and 1330 related to revisions is changed.

Additionally, it can be seen that the ID of the instance associated with the third function is not specified and an identifier (UNKNOWN) related to it is output. In addition, it can be seen that the connection relationship of the instance 1310 with the ID of E28 data center BMS DATASET{Rev1} has changed.

Meanwhile, rows related to the third function may be stored in the first to fifth temporary tables for a predetermined time. If the third function is to be restored, rows associated with the third function stored in the first to fifth temporary tables may be added to each table. That is, a row associated with the third function may be extracted from the first temporary table and added to the instance table 1110, and a row associated with the third function may be extracted from the second temporary table and added to the tag table 1120. Additionally, a row associated with the third function is extracted from the third temporary table and added to the relationship type table 1210, and a row associated with the third function is extracted from the fourth temporary table and added to the relationship table 1220. Rows associated with 3 functions may be extracted from the fifth temporary table and added to the attribute table 1230.

When the third function is restored by adding rows to each table, the instance identifier associated with the third function is obtained from the row restored to the instance table 1110, and the identifier associated with the unspecified function may be changed to the obtained instance identifier. Taking the relationship table 1220 of FIG. 12 as an example, the identifier of the target instance in the bottom row may be changed from an identifier related to unspecified (eg, UNKNOWN) to '10012'. Through this process, the third function of a specific object can be restored normally.

FIG. 14 is a flowchart illustrating a modeling method 1400 for object life cycle management in a digital twin data platform linked data structure, according to an embodiment of the present disclosure. The method shown in FIG. 14 is only an example to achieve the purpose of the present disclosure, and of course, some steps may be added or deleted as needed. Additionally, the method shown in FIG. 14 may be performed by at least one processor included in at least one processor included in the information processing system. For convenience of explanation, it will be described that each step shown in FIG. 14 is performed by a processor included in the information processing system shown in FIG. 3.

In response to changing a first function of a particular object included in the digital twin model to a second function, the processor generates a first row containing a first revision identifier and a first session part identifier associated with the second function. It can be added to the table (S1410).

Afterwards, the processor may add a row including an instance identifier and a first session part identifier associated with the second function of a specific object to the second table (S1420).

Subsequently, the processor may add a row including object relationship information associated with the second function of a specific object and the first session part identifier to the third table (S1430).

According to one embodiment, attribute information of the instance associated with the first revision is recorded in the first table, detailed information about the instance associated with the instance identifier is recorded in the second table, and information between the source instance and the target instance is recorded in the third table. Object relationship information about the relationship may be recorded. For example, the first table may be an attribute table, the second table may be an instance table, and the third table may be a relationship table.

According to one embodiment, the row added to the first table, the row added to the second table, and the row added to the third table may be linked to each other by the first session part identifier. Additionally, the first table may be stored in a non-relational database, and the second table and third table may be stored in a relational database.

The processor may then, in response to changing the second function of the particular object to a third function, add a row to the first table containing a second revision identifier and a second session part identifier associated with the third function. . The processor then adds a row containing an instance identifier and a second session part identifier associated with the third function of the specific object to the second table, and the object relationship information and the second session part identifier associated with the third function of the specific object. Containing rows can be added to a third table.

The processor then, in response to receiving a user input for removal of the second function of the specific object, deletes the row containing the second revision identifier in the first table to remove the third function of the specific object in the digital twin model. can be removed. Additionally, the processor may delete the row containing the second session part identifier from each of the second table and third table.

The processor may then delete the row containing the first revision identifier in the first table, thereby removing the second function of the specific object from the digital twin model. Additionally, the processor may delete the row containing the first session part identifier from each of the second table and third table.

The processor may then restore the third function by adding a row containing the second session part identifier in each of the second table and the second table, and adding a row containing the second revision identifier in the first table. .

Meanwhile, the processor stores a row containing a first revision identifier deleted from the first table in a first temporary table, and stores a row containing a first session part identifier deleted from the second table in a second temporary table. , a row including the first session part identifier in the third table may be stored in the third temporary table. According to one embodiment, in response to the deleted second function not being restored for a predetermined period of time, the row containing the first revision identifier is deleted from the first temporary table, and the row containing the second session part identifier is deleted from the first temporary table. It can be deleted from each of the second and third temporary tables.

The processor may identify an instance identifier associated with the second function of the particular object once the second function of the particular object is removed. Subsequently, the processor may identify a row including the identified instance identifier from at least one of the first table, the second table, and the third table, and change the instance identifier included in the identified row to an identifier related to an unspecified one.

The above flowchart and above description are only examples and may be implemented differently in some embodiments. For example, in some embodiments, the order of each step may be changed, some steps may be performed repeatedly, some steps may be omitted, or some steps may be added.

The above-described method may be provided as a computer program stored in a computer-readable recording medium for execution on a computer. Media may be used to continuously store executable programs on a computer, or may be temporarily stored for execution or download. In addition, the medium may be a variety of recording or storage means in the form of a single or several pieces of hardware combined. It is not limited to a medium directly connected to a computer system and may be distributed over a network. Examples of media 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 There may be something configured to store program instructions, including ROM, RAM, flash memory, etc. Additionally, examples of other media include recording or storage media managed by app stores that distribute applications, sites or servers that supply or distribute various other software, etc.

The methods, operations, or techniques of this 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 illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented in electronic hardware, computer software, or combinations of both. To clearly illustrate this interchange of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and design requirements imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementations should not be interpreted as causing a departure from the scope of the present disclosure.

In a hardware implementation, the processing units used to perform the techniques may include 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, and other electronic units designed to perform the functions described in this disclosure. , a computer, or a combination thereof.

Accordingly, the various illustrative logical blocks, modules, and circuits described in connection with this disclosure may be general-purpose processors, DSPs, ASICs, FPGAs or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or It may be implemented or performed as any combination of those designed to perform the functions described in. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other configuration.

For firmware and/or software implementations, techniques include random access memory (RAM), read-only memory (ROM), non-volatile random access memory (NVRAM), and PROM ( on computer-readable media such as programmable read-only memory (EPROM), electrically erasable PROM (EEPROM), flash memory, compact disc (CD), magnetic or marked data storage devices, etc. It may also be implemented as stored instructions. Instructions may be executable by one or more processors and may cause the processor(s) to perform certain aspects of the functionality described in this disclosure.

When implemented in software, the techniques described above may be stored on or transmitted through a computer-readable medium as one or more instructions or code. Computer-readable media includes both computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Storage media may be any available media that can be accessed by a computer. By way of 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 the desired program code in the form of instructions or data structures. It can be used to transfer or store data and can include any other media that can be accessed by a computer. Any connection is also properly termed a computer-readable medium.

For example, if the 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, , fiber optic cable, twisted pair, digital subscriber line, or wireless technologies such as infrared, radio, and microwave are included within the definition of medium. As used herein, disk and disk include CD, laser disk, optical disk, digital versatile disc (DVD), floppy disk, and Blu-ray disk, where disks are usually magnetic. It reproduces data optically, while discs reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

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

Although the above-described embodiments have been described as utilizing aspects of the presently disclosed subject matter in one or more standalone computer systems, the disclosure is not limited thereto and may also be implemented in conjunction with any computing environment, such as a network or distributed computing environment. . Furthermore, aspects of the subject matter of this disclosure may be implemented in multiple processing chips or devices, and storage may be similarly effected across the multiple devices. These devices may include PCs, network servers, and portable devices.

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

210: user terminal
220: network
230: Information processing system

Claims (12)

In a modeling method for object life cycle management in a digital twin data platform linked data structure, performed by at least one processor,
In response to the first function (property) of a specific object included in the digital twin model being updated and changed to a second function, a row including a first revision identifier and a first session part identifier associated with the second function. adding to the first table;
adding a row including an instance identifier associated with a second function of the specific object and the first session part identifier to a second table; and
Adding a row containing object relationship information associated with a second function of the specific object and the first session part identifier to a third table.
Including,
A change in the function of an object indicates a change in the properties of the object,
The first table records attribute information of the instance associated with the first revision identifier, the second table records detailed information about the instance associated with the instance identifier, and the third table records information between the source instance and the target instance. A modeling method for object life cycle management in which object relationship information about relationships is recorded.
delete According to paragraph 1,
The row added to the first table, the row added to the second table, and the row added to the third table are linked to each other by the first session part identifier, and object life cycle management is performed. modeling method for
According to paragraph 1,
The first table is stored in a non-relational database, and the second table and the third table are stored in a relational database.
In a modeling method for object life cycle management in a digital twin data platform linked data structure, performed by at least one processor,
In response to the first function (property) of a specific object included in the digital twin model being updated and changed to a second function, a row including a first revision identifier and a first session part identifier associated with the second function. adding to the first table;
adding a row including an instance identifier associated with a second function of the specific object and the first session part identifier to a second table; and
Adding a row containing object relationship information associated with a second function of the specific object and the first session part identifier to a third table.
Including,
A change in the function of an object indicates a change in the properties of the object,
After adding a row containing object relationship information associated with a second function of the specific object and the first session part identifier to the third table,
In response to the second function of the specific object being updated and changed to a third function, adding a row including a second revision identifier and a second session part identifier associated with the third function to the first table;
adding a row including an instance identifier associated with a third function of the specific object and the second session part identifier to the second table; and
Adding a row containing object relationship information associated with a third function of the specific object and the second session part identifier to the third table.
A modeling method for object life cycle management, further comprising:
According to clause 5,
After adding a row containing object relationship information associated with a second function of the specific object and the first session part identifier to the third table,
In response to receiving a user input for removing the second function of the specific object, delete the row containing the second revision identifier from the first table to remove the third function of the specific object in the digital twin model. removing; and
Removing a second function of the specific object from the digital twin model by deleting a row containing the first revision identifier from the first table
A modeling method for object life cycle management, further comprising:
According to clause 6,
The step of removing the third function of the specific object from the digital twin model is,
Deleting a row containing the second session part identifier from each of the second table and the third table.
Including,
The step of removing the second function of the specific object from the digital twin model is,
Deleting a row containing the first session part identifier from each of the second table and the third table.
A modeling method for object life cycle management, including.
In clause 7,
After removing the second function of the specific object,
adding a row including the second session part identifier to each of the second table and the third table; and
Recovering a third function of the specific object by adding a row containing the second revision identifier to the first table.
A modeling method for object life cycle management, further comprising:
In clause 7,
storing a row including the first revision identifier deleted from the first table in a first temporary table; and
A row containing the first session part identifier deleted from the second table is stored in a second temporary table, and a row containing the first session part identifier deleted from the third table is stored in a third temporary table. steps to do
It further includes,
In response to the deleted second function not being restored for a predetermined period of time, the row containing the first revision identifier is deleted from the first temporary table, and the row containing the second session part identifier is deleted from the first temporary table. A modeling method for object life cycle management, which is deleted from each of the second temporary table and the third temporary table.
According to clause 6,
When the second function of the specific object is removed from the digital twin model, identifying an instance identifier associated with the second function of the specific object;
identifying a row containing the identified instance identifier from at least one of the first table, the second table, or the third table; and
Changing the instance identifier included in the identified row to an identifier associated with unspecified
A modeling method for object life cycle management, further comprising:
A computer program stored in a computer-readable recording medium for executing the method according to any one of claims 1 and 3 to 10 on a computer.
As an information processing system,
Memory; and
At least one processor connected to the memory and configured to execute at least one computer-readable program included in the memory
Including,
The at least one program is,
In response to the first function (property) of a specific object included in the digital twin model being updated and changed to a second function, a row including a first revision identifier and a first session part identifier associated with the second function. Add to the first table,
Add a row containing an instance identifier associated with a second function of the specific object and the first session part identifier to a second table,
Includes instructions for adding a row containing object relationship information associated with a second function of the specific object and the first session part identifier to a third table,
A change in the function of an object indicates a change in the properties of the object,
The first table records attribute information of the instance associated with the first revision identifier, the second table records detailed information about the instance associated with the instance identifier, and the third table records information between the source instance and the target instance. An information processing system in which object relationship information about relationships is recorded.

Images