Object management method, apparatus and system

Abstract

A method, apparatus, and system for object management communication are provided. A unified management interface acquires a piece of information indicating an operation related to a first object to be performed in a first system, and instructs the first system to perform the operation. At least one attribute piece of information of the first object is recorded by at least one second object associated with the first object. Therefore, unified management of multiple objects in different systems can be achieved, and the attribute information of the first object can be recorded separately by the second object associated with the first object, thereby facilitating the modification and synchronization of the object's attribute information in different systems.

Description

Technical Field

[0001] This invention generally relates to the field of data management technology, and more particularly to an object management communication method, apparatus and system. Background Technology

[0002] Traditionally, data management systems such as Product Data Management (PDM), Product Lifecycle Management (PLM), Simulation Process and Data Management (SPDM), and Enterprise Resource Planning (ERP) use identifiers assigned when objects are created, which cannot be changed in the future. Additional identifiers are typically implemented as extended attributes defined by the information object. Any errors in the identifiers of information objects require the objects to be recreated.

[0003] More specifically, traditionally, an object's identification information is an attribute of that object and cannot be created or changed independently. If multiple identifiers are needed for the same object, additional identification attributes must be added to the system for that object.

[0004] In the study of the lifecycle management system of the system, there is a problem about the identification of information objects, because the same information object usually has some different identifiers.

[0005] The purpose of describing this background information is to disclose information that the applicant believes may be relevant to the present invention, and it is not intended to acknowledge, nor should it be construed as, any of the foregoing information constituting prior art in relation to the present invention. Summary of the Invention

[0006] In a first aspect, the present invention provides an object management method, comprising:

[0007] The management interface obtains a message, wherein the message indicates an operation related to a first object to be performed in the first system, wherein at least one attribute of the first object is recorded by at least one second object related to the first object, and each attribute of the at least one attribute is recorded as an attribute of the corresponding second object in the at least one second object;

[0008] In response to receiving a message, the management interface instructs the first system to perform the operation related to the first object.

[0009] Because the unified management interface can be used to instruct the first system to perform operations in response to obtaining relevant information about operations related to the first object, unified management of multiple objects in different systems can be achieved. Furthermore, the second object is used to record the attribute information of the first object; therefore, the attribute information of the first object can be recorded separately by the attributes of the second object associated with the first object, rather than as attributes of the first object itself. This allows attribute information to be created or modified by creating or modifying the corresponding second object, facilitating the modification and synchronization of the attribute information (e.g., identification information) of the same object in different systems.

[0010] In one possible implementation of the first aspect, the at least one second object is associated with the first object through at least one third object, wherein each of the at least one third object indicates a relationship between the first object and a corresponding second object among the at least one second object, the first object having a one-to-one correspondence with each of the at least one third object, and each of the at least one third object having a one-to-one correspondence with the corresponding second object among the at least one second object.

[0011] Two types of objects (i.e., a second object and a third object) are used to record the attribute information of the first object. The second object records the attribute information of the first object, and the third object indicates the relationship between the first and second objects. Therefore, multiple attribute records of the same object in different systems can be recorded by multiple second and third objects. When the identification information of the first object is recorded in this way, the creation and identification of the first object can be separated into two independent processes. In other words, creation and identification can be performed separately by creating the first object, the second object used to record the identification information, and the third object indicating the relationship between the first and second objects, where the first object is the object to be created. If it is necessary to add another identifier to the first object, another second object and another third object can be added. Therefore, it is possible to add different identifiers to the same object.

[0012] In one possible implementation of the first aspect, each of the at least one second object is deleted by deleting the corresponding third object among the at least one third object.

[0013] Since the attribute information of the first object is recorded by the second object, the attribute information of the first object can be easily deleted by deleting the corresponding third object. When the second object records additional identification information of the first object, the additional identification information can also be deleted from the first object in this way, thereby facilitating the management of objects in multiple systems and reducing some redundant manual operations for users.

[0014] In one possible implementation of the first aspect, the management interface is used to provide a unified interface and management entry point for managing objects from at least one system.

[0015] Since a unified management interface can provide a unified interface and management entry point for managing objects from at least one system, it can easily and efficiently manage multiple objects from different systems, thus reducing some redundant manual operations for users.

[0016] In one possible implementation of the first aspect, instructing the first system to perform the operation related to the first object includes:

[0017] The management interface instructs the first system to perform the operations related to the first object through a pre-configured interface and a communication protocol based on the first system's application programming interface (API).

[0018] The management interface can instruct the first system to perform operations through pre-configured interfaces and API-based communication protocols, which provides an implementation method for the management interface to instruct the first system.

[0019] In one possible implementation of the first aspect, the operation associated with the first object includes at least one of the following:

[0020] Create the first object in the first system;

[0021] Modify one attribute of the first object in the first system; or

[0022] The first system records one attribute information of the first object.

[0023] Because the unified management interface can be used to instruct the system to create objects, modify an object's attribute information, and / or record an object's attribute information, existing objects in the system can be managed uniformly, and new objects can be created easily.

[0024] In one possible implementation of the first aspect, the message indicates the creation of the first object in the first system.

[0025] Since the unified management interface can be used to instruct the first system to create new objects, it is possible to create new objects and their corresponding attribute information in a unified manner.

[0026] In one possible implementation of the first aspect, the information is obtained when the user adds the first object in the first system through the management interface;

[0027] The instruction to the first system to perform the operation related to the first object includes:

[0028] The management interface instructs the first system to create the first object in the first system and generate the first attribute information of the first object in the first system.

[0029] If a user wants to add a new object to the first system, the unified management interface allows for easy creation of new objects and generation of new attribute information within the first system, without the need for redundant operations.

[0030] In one possible implementation of the first aspect, the first object exists in the second system, and the first object has a second attribute information in the second system; the method further includes at least one of the following:

[0031] The management interface instructs the first system to record the second attribute information of the first object; or

[0032] The management interface instructs the second system to record the first attribute information of the first object.

[0033] If an object created in the first system also exists in other systems, then after creating an object with attribute information in the first system, the management interface can instruct the first system to record the attribute information of the object in other systems, and / or instruct other systems to record the attribute information of the first object in the first system, so that the first system and / or other systems can know the attribute information of the first object in different systems, thereby realizing the synchronization of the attribute information of the object in different systems.

[0034] In one possible implementation of the first aspect, the information indicates the modification of an attribute of the first object in the first system.

[0035] Since the unified management interface can be used to instruct the first system to modify the attribute information of the first object, the existing first attributes of objects in the system can be managed in a unified manner, which facilitates the unified management of attribute information of objects in different systems, especially modification.

[0036] In one possible implementation of the first aspect, the information is obtained when the user modifies the first attribute information of the first object to a first value in the first system through the management interface, and the information indicates that the first attribute information of the first object is modified to the first value;

[0037] The instruction to the first system to perform the operation related to the first object includes:

[0038] The management interface instructs the first system to modify the first attribute information of the first object to the first value within the first system.

[0039] When a user wants to modify the first attribute information of a first object in the first system, the unified management interface provides a management entry point to manage objects in different systems. Objects can be managed uniformly, and the attribute information of objects in the first system can be easily modified through the unified management interface without redundant operations.

[0040] In one possible implementation of the first aspect, the information is obtained by the management interface from the second system when the second system has modified the second attribute information of the first object to the second value in the second system, wherein the second system records that the second attribute information is related to the first object in the first system, and the information indicates that the second attribute information of the first object is modified to the second value;

[0041] The instruction to the first system to perform the operation related to the first object includes:

[0042] The management interface instructs the first system to modify the second attribute information of the first object to the second value within the first system.

[0043] If the second system has modified the second attribute information of the first object in the second system, and the second attribute information of the first object in the second system is related to the first object in the first system (meaning the first system also records the second attribute information of the first object), then the unified management interface can serve as a unified interface to manage objects in different systems. Specifically, the second system can use the unified management interface to notify the first system to modify the second attribute information of the first object to its second value in the first system. Therefore, the synchronization of object attribute information across different systems can be achieved in a simple and convenient way.

[0044] In one possible implementation of the first aspect, the method further includes:

[0045] The management interface responds to a query to see if the third attribute information in the third system has been modified from the first system, and obtains the third attribute information of the first object in the third system;

[0046] The management interface determines whether the third attribute information has been modified.

[0047] In response to determining that the third attribute information of the first object has been changed to a third value, instructing the first system to perform the operation related to the first object includes:

[0048] The management interface instructs the first system to modify the third attribute information of the first object to the third value within the first system.

[0049] In one possible implementation of the first aspect, the query to see whether the third attribute information in the third system has been modified is performed periodically.

[0050] The first system proactively queries the management interface to determine if the third system has modified the object's third attribute information in the third system. If the third system has modified the object's third attribute, the first system can modify the object's third attribute information recorded in the first system. Therefore, it is possible to synchronize object attribute information across different systems in a simple and convenient way. Furthermore, queries can be performed periodically, and the synchronization cycle can be set according to actual needs, providing a synchronization method with more options for different scenarios and conditions.

[0051] In one possible implementation of the first aspect, the information is obtained from the fourth system after the first object is created in the fourth system and the fourth attribute information of the first object is generated in the fourth system, and the information includes the fourth attribute information of the first object;

[0052] The instruction to the first system to perform the operation related to the first object includes:

[0053] The management interface instructs the first system to record the fourth attribute information of the first object.

[0054] If an object newly created in another system also exists in the first system, then after the object is created and attribute information is generated in the fourth system, the management interface can instruct the first system to record the attribute information of the object in the other system. This allows the first system to know that the other system also has the object and records the corresponding attribute information, thereby achieving the synchronization of the attribute information of the object in different systems.

[0055] In one possible implementation of the first aspect, the attribute indicates one of the following:

[0056] The identifier of the first object;

[0057] Description information of the first object; or

[0058] The address information of the first object.

[0059] The attribute information of an object can indicate various information, such as the object's identifier, description information, or address information. Therefore, different object information in different systems can be created, modified, and synchronized in a simple and convenient way through the management interface.

[0060] In one possible implementation of the first aspect, the first system is one of a production system, a supply chain system, a sales system, or an operation and maintenance system.

[0061] The management interface can be used to manage different systems such as production systems, supply chain systems, sales systems, or operation and maintenance systems, thereby enabling unified management of multiple objects in these systems.

[0062] Secondly, the present invention provides an object management method, comprising:

[0063] The first system obtains instructions from the management interface;

[0064] The first system responds to the instruction and performs an operation related to the first object;

[0065] The instruction indicates the operation related to the first object to be performed in the first system, wherein at least one attribute information of the first object is recorded by at least one second object related to the first object, and each of the at least one attribute information is recorded as an attribute of the corresponding second object in the at least one second object.

[0066] Instructions can be obtained from a unified management interface, and operations can be executed in response to these instructions. This enables unified management of multiple objects across different systems. Furthermore, the second object records the attribute information of the first object; therefore, the attribute information of the first object can be recorded separately by the attributes of the second object associated with the first object, rather than as attributes of the first object itself. This allows for the creation or modification of attribute information by creating or modifying the corresponding second object, facilitating the modification and synchronization of the same object's attribute information (e.g., identification information) across different systems.

[0067] In one possible implementation of the second aspect, the at least one second object is associated with the first object through at least one third object, wherein each of the at least one third object indicates a relationship between the first object and a corresponding second object among the at least one second object, the first object having a one-to-one correspondence with each of the at least one third object, and each of the at least one third object having a one-to-one correspondence with the corresponding second object among the at least one second object.

[0068] Two types of objects (i.e., a second object and a third object) are used to record the attribute information of the first object. The second object records the attribute information of the first object, and the third object indicates the relationship between the first and second objects. Therefore, multiple attribute records of the same object in different systems can be recorded by multiple second and third objects. When the identification information of the first object is recorded in this way, the creation and identification of the first object can be separated into two independent processes. In other words, creation and identification can be performed separately by creating the first object, the second object used to record the identification information, and the third object indicating the relationship between the first and second objects, where the first object is the object to be created. If it is necessary to add another identifier to the first object, another second object and another third object can be added. Therefore, it is possible to add different identifiers to the same object.

[0069] In one possible implementation of the second aspect, each of the at least one second object is deleted by deleting the corresponding third object among the at least one third object.

[0070] Since the attribute information of the first object is recorded by the second object, the attribute information of the first object can be easily deleted by deleting the corresponding third object. When the second object records additional identification information of the first object, the additional identification information can also be deleted from the first object in this way, thereby facilitating the management of objects in multiple systems and reducing some redundant manual operations for users.

[0071] In one possible implementation of the second aspect, the management interface is used to provide a unified interface and management entry point for managing objects from at least one system.

[0072] Since a unified management interface can provide a unified interface and management entry point for managing objects from at least one system, it can easily and efficiently manage multiple objects from different systems, thus reducing some redundant manual operations for users.

[0073] In one possible implementation of the second aspect, obtaining instructions from the management interface includes:

[0074] The first system obtains the instructions from the management interface through a pre-configured interface and a communication protocol based on the application programming interface (API) of the first system.

[0075] The first system can obtain instructions from the management interface through a pre-configured interface and an API-based communication protocol, which provides an implementation method for the first system to obtain instructions.

[0076] In one possible implementation of the second aspect, the operation associated with the first object includes at least one of the following:

[0077] Create the first object in the first system;

[0078] Modify one attribute of the first object in the first system; or

[0079] Record one attribute information of the first object in the first system.

[0080] Because the first system can instruct the creation of objects, modification of one attribute of an object, and / or recording of one attribute of an object through a unified management interface, existing objects in the system can be managed uniformly, and new objects can be created easily.

[0081] In one possible implementation of the second aspect, the instructions instruct the creation of the first object in the first system.

[0082] Since the first system can instruct the creation of new objects through a unified management interface, it can uniformly create new objects and their corresponding attribute information.

[0083] In one possible implementation of the second aspect, the instruction is obtained when the user adds the first object to the first system through the management interface;

[0084] The operations related to the first object include:

[0085] The first system creates the first object in the first system and generates the first attribute information of the first object in the first system.

[0086] If a user wants to add a new object to the first system, the unified management interface allows for easy creation of new objects and generation of new attribute information within the first system, without the need for redundant operations.

[0087] In one possible implementation of the second aspect, the first object exists in the second system, and the first object has a second attribute information in the second system; the method further includes:

[0088] The first system obtains the second attribute information of the first object from the management interface, and the first system records the second attribute information of the first object; or

[0089] The first system informs the second system of the first attribute information of the first object through the management interface.

[0090] If an object created in the first system also exists in other systems, then after creating an object with attribute information in the first system, the first system can obtain and record the attribute information of the object in the second system, and / or inform other systems of the attribute information of the generated first object, so that the first system and / or other systems can know the attribute information of the first object in different systems, thereby realizing the synchronization of the attribute information of the object in different systems.

[0091] In one possible implementation of the second aspect, the instruction instructs the modification of one attribute of the first object in the first system.

[0092] Since the first system can modify the attribute information of objects through a unified management interface, the existing primary attributes of objects in the system can be managed uniformly, which facilitates the unified management of attribute information of objects in different systems, especially modification.

[0093] In one possible implementation of the second aspect, the instruction is obtained when the user modifies the first attribute information of the first object to a first value in the first system through the management interface, and the instruction instructs the first attribute information of the first object to be modified to the first value.

[0094] The operations related to the first object include:

[0095] The first system modifies the first attribute information of the first object to the first value.

[0096] When a user wants to modify the first attribute information of a first object in the first system, the unified management interface provides a management entry point to manage objects in different systems. Objects can be managed uniformly, and the attribute information of objects in the first system can be easily modified through the unified management interface without redundant operations.

[0097] In one possible implementation of the second aspect, the instruction is obtained when the second system has already modified the second attribute information of the first object to a second value in the second system, the second system recording that the second attribute information is related to the first object in the first system, and the instruction instructing to modify the second attribute information of the first object to the second value;

[0098] The operations related to the first object include:

[0099] The first system modifies the second attribute information of the first object to the second value.

[0100] If the second system has modified the second attribute information of the first object in the second system, and the second attribute information of the first object in the second system is related to the first object in the first system (i.e., the first system also records the second attribute information of the first object), then the unified management interface can be used as a unified interface to manage objects in different systems. Furthermore, the first system can, through the management interface, modify the recorded second attribute information of the first object to its second value. Therefore, the synchronization of object attribute information across different systems can be achieved in a simple and convenient way.

[0101] In one possible implementation of the second aspect, the method further includes:

[0102] The first system queries whether the third attribute information in the third system has been modified;

[0103] The instruction is obtained when the third attribute information of the first object has been changed to a third value, and the instruction instructs to modify the third attribute information of the first object to the third value.

[0104] The operations related to the first object include:

[0105] The first system modifies the third attribute information of the first object to the third value.

[0106] In one possible implementation of the second aspect, the query to determine whether the third attribute information in the third system has been modified is performed periodically.

[0107] The first system proactively queries the management interface to determine if the third system has modified the object's third attribute information. If the third system has modified the object's third attribute information, the first system can then modify the object's third attribute information recorded in the first system. Therefore, synchronizing object attribute information across different systems can be achieved simply and conveniently. Furthermore, queries can be performed periodically, and the synchronization cycle can be set according to actual needs, providing a synchronization method with more options for different scenarios and conditions.

[0108] In one possible implementation of the second aspect, the instruction is obtained when the first object is created in the fourth system and the fourth attribute information of the first object is generated in the fourth system, and the instruction instructs to record the fourth attribute information of the first object;

[0109] The operations related to the first object include:

[0110] The first system records the fourth attribute information of the first object.

[0111] If an object newly created in another system also exists in the first system, then after the object is created and attribute information is generated in the fourth system, the first system can instruct the management interface to record the attribute information of the object in other systems. This allows the first system to know that other systems also have the object and record the corresponding attribute information, thereby achieving synchronization of the attribute information of the object in different systems.

[0112] In one possible implementation of the second aspect, the attribute information indicates one of the following:

[0113] The identifier of the first object;

[0114] Description information of the first object; or

[0115] The address information of the first object.

[0116] The attribute information of an object can indicate various information, such as the object's identifier, description information, or address information. Therefore, different object information in different systems can be created, modified, and synchronized in a simple and convenient way through the management interface.

[0117] In one possible implementation of the second aspect, the first system is one of a production system, a supply chain system, a sales system, or an operation and maintenance system.

[0118] The first system can be various systems such as production system, supply chain system, sales system or operation and maintenance system, thereby enabling unified management of multiple objects in various systems.

[0119] Thirdly, one possible implementation of the present invention provides a management interface including various modules for performing the object management method according to the first aspect or any possible implementation thereof.

[0120] Fourthly, one possible implementation of the present invention provides a first system comprising various modules for performing the object management method according to the second aspect or any possible implementation thereof.

[0121] Fifthly, one possible implementation of the present invention provides a management interface including processing circuitry for executing the object management method according to the first aspect or any possible implementation thereof.

[0122] In a sixth aspect, one possible implementation of the present invention provides a first system including processing circuitry for executing the object management method according to the second aspect or any possible implementation thereof.

[0123] In a seventh aspect, one possible implementation of the present invention provides an object management system, comprising: a management interface according to the third aspect or any possible implementation of the third aspect, or a management interface according to the fifth aspect; a first system according to the fourth aspect or any possible implementation of the fourth aspect, or a first system according to the sixth aspect; and at least one fifth system, wherein the at least one fifth system is one of a production system, a supply chain system, a sales system, or an operation and maintenance system.

[0124] Eighthly, one possible implementation of the present invention provides an object management system, comprising: a first processing circuit for executing the object management method according to the first aspect or any possible implementation thereof; a second processing circuit for executing the object management method according to the second aspect or any possible implementation thereof; and at least one third processing circuit, wherein the at least one third processing circuit belongs to one of a production system, a supply chain system, a sales system, or an operation and maintenance system.

[0125] In a ninth aspect, one possible implementation of the present invention provides a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, cause the processor to perform the object management method according to the first aspect or any possible implementation thereof, or the second aspect or any possible implementation thereof.

[0126] In a tenth aspect, one possible implementation of the present invention provides a computer program product including computer execution instructions that, when executed by a processor, cause the processor to perform the object management method according to the first aspect or any possible implementation thereof, or the second aspect or any possible implementation thereof.

[0127] This invention provides an object management communication method, apparatus, and system. After acquiring a message indicating an operation related to a first object to be performed in a first system, a unified management interface can be used to instruct the system to perform the operation related to the object in response to the message. At least one attribute of the first object is recorded by at least one second object associated with the first object, and each of the at least one attribute is recorded as an attribute of the corresponding second object in the at least one second object. Therefore, unified management of multiple objects in different systems can be achieved. Furthermore, since the second object is used to record the attribute information of the first object, the attribute information of the first object can be recorded separately by the attributes of the second objects associated with the first object, rather than as attributes of the first object itself. This allows the creation or modification of attribute information to be achieved by creating or modifying the corresponding second object, thereby facilitating the modification and synchronization of the attribute information (e.g., identification information) of the same object in different systems. Attached Figure Description

[0128] The following figures illustrate exemplary embodiments of the present invention by way of example, in which:

[0129] Figure 1 This is a simplified diagram of an item with a label.

[0130] Figure 2 This is a schematic diagram illustrating an application scenario provided by one or more exemplary embodiments of the present invention.

[0131] Figure 3 This is a schematic diagram illustrating an exemplary representation of a data object provided by one or more exemplary embodiments of the present invention.

[0132] Figure 4 This is a schematic diagram illustrating another exemplary representation of a data object provided by one or more exemplary embodiments of the present invention.

[0133] Figure 5 This is a schematic diagram illustrating the creation and identification of information objects provided by one or more exemplary embodiments of the present invention.

[0134] Figure 6 This is a schematic flowchart of an object management method provided by one or more exemplary embodiments of the present invention.

[0135] Figure 7 This is an interaction diagram of an object management method provided by one or more exemplary embodiments of the present invention.

[0136] Figure 8 This is another interaction diagram of the object management method provided by one or more exemplary embodiments of the present invention.

[0137] Figure 9 This is another interaction diagram of the object management method provided by one or more exemplary embodiments of the present invention.

[0138] Figure 10 This is another illustrative flowchart of an object management method provided by one or more exemplary embodiments of the present invention.

[0139] Figure 11 This is a schematic diagram of the structure of the management interface provided by one or more exemplary embodiments of the present invention.

[0140] Figure 12 This is a schematic diagram of the structure of a first system provided by one or more exemplary embodiments of the present invention. Detailed Implementation

[0141] In the following description, reference is made to the accompanying drawings, which form part of this invention, and which illustrate by way of description specific aspects of embodiments of the invention or aspects in which embodiments of the invention may be used. It should be understood that embodiments of the invention can be used in other aspects and include structural or logical variations not depicted in the drawings. Therefore, the following detailed description should not be construed in a limiting sense, and the scope of the invention is defined by the appended claims.

[0142] Figure 1 This is a simplified diagram of an identified project. For example, a PLM system uses a project, which is the root business object for all objects. A project represents any type of product, resource, material, or component that a company can purchase or build. Projects can be used to create structures so that one project instance can contain one or more other instances. Projects have a project_id attribute, which helps to uniquely identify projects such as part numbers. Project revisions are represented by the project revision business object. After participating in any project revision in any workflow, the revision receives a revision status (published) and metadata, along with the changed project blocks.

[0143] The creation process is the same as the object identification process.

[0144] In the study of the lifecycle management system of the system, there is a problem about the identification of information objects, because the same information object usually has some different identifiers, such as the identifier of information object in the local system, the identifier based on standard requirements, the internal identifier of the producer, the external identifier of the market, etc.

[0145] Because each type of identifier has different rules, it is impossible to use a uniform, unique identifier for all tasks, all industries, all producers, all standards, etc.

[0146] For example, automotive parts can have different identifiers, such as manufacturer identifiers, sub-manufacturer identifiers, repair parts identifier catalogs, workshop identifiers, and identifiers in PLM, ERP, and other systems. In this case, the main task of identifying, counting, and classifying automotive part information objects is to store all the different identifiers of the information object in the system to avoid the incorrect use of the object.

[0147] Furthermore, when using multiple identifiers, if one of the identifiers changes, the information object needs to be modified. This is a lengthy process that requires a special set of procedures (e.g., the Configuration Management II (CMII) standard).

[0148] Traditionally, data management systems in related technologies can only statically store identification information, and cannot dynamically modify or synchronize identification information across different systems. If the identification changes, users need to manually update the stored identification information; otherwise, errors may occur. Current data management systems cannot easily modify object identifiers created in each system.

[0149] This invention provides a service / system for industrial data management, and provides a unified interface (application collaboration interface) and management entry point to enable users to manage objects from multiple systems (e.g., production system A, supply chain system B, sales system C, or other user-owned systems), including the following functions:

[0150] 1. Unified management of objects created by users in other systems. (For example, multiple objects may be created in production system A, supply chain system B, and sales system C. Some objects may exist in multiple systems simultaneously, but the same object may have different IDs in different systems.) It can record the relationships of the same object in different systems, modify object identifiers in different systems, and synchronize identifier changes across different systems. In addition to modifying and synchronizing identifier information, it can also modify and synchronize other attribute information of objects.

[0151] 2. Users can create new objects in different systems (the object does not exist before creation).

[0152] To help understand the present invention, examples of system architecture or scenarios are described below.

[0153]

[0154] Figure 2 This is a schematic diagram illustrating an application scenario provided by one or more exemplary embodiments of the present invention.

[0155] To achieve unified management of multiple objects across different systems, this solution provides a management interface (application collaboration interface). Users can select one or more information systems (e.g., System 1 and System 2) to be used for creating object representations and provide the correct information based on rules. This information is provided by the API to System 1 and System 2 to create the necessary identifiers for these two systems, namely, identifier A for System 1 and identifier A for System 2. Furthermore, users can provide other information about object A in the same way, such as its name and description.

[0156] The application's collaboration interface uses the API calls of System 1 and System 2 to create an object A for these two systems.

[0157] In terms of data models, the representation of data objects includes two other types of information objects: object identifiers and identifier relationships. Figure 3 This is a schematic diagram illustrating an exemplary representation of a data object provided by one or more exemplary embodiments of the present invention.

[0158] like Figure 3 As shown, an object identifier has a unique identifier as an attribute, and this attribute can have special formation rules. The identification relationship is the relationship between an object and its object identifier. 1..1.

[0159] This pattern provides the possibility of adding different identifiers to the same object in the current system or in different systems.

[0160] To achieve unified management of multiple objects across different systems, this solution provides a new management interface. Users can create information object A on the management interface and define its name, attributes, and other information. Figure 4 This is a schematic diagram illustrating another exemplary representation of a data object provided by one or more exemplary embodiments of the present invention. For example... Figure 4 As shown, the identifier of object A in another system (for example, in production system A, object A has the identifier XXX) can be recorded as attribute information in the metadata of object A. That is, when object A is recorded in the system, its first attribute records the identifier XXX of object A in production system A. If the object also exists in supply chain system B or sales system C, users can add more attributes to object A through the management interface, such as adding second and third attributes. The second and third attributes record object A as YYY in supply chain system B and as ZZZ in sales system C.

[0161] Figure 5 This is a schematic diagram illustrating the creation and identification of information objects provided by one or more exemplary embodiments of the present invention.

[0162] like Figure 5 As shown, based on the current data model, the creation and identification process of information objects can be divided into two independent processes: creation and identification, which can be performed separately by the creator and the identifier. Specifically, the creator can create the information object and the identification relationship independently, and the identifier can create the object identifier independently.

[0163] Based on this method of treating information objects as queues, the creation and identification process of information objects can be time-divided, and additional identifiers (categories) can be easily added to or deleted from existing information objects.

[0164] If necessary, any identifying information can be deleted based on the deletion of relational object information.

[0165] In addition to recording and displaying object attribute information, the system can also automatically communicate with other existing systems to achieve collaborative data updates.

[0166] Figure 6 This is a schematic flowchart illustrating an object management method provided by one or more exemplary embodiments of the present invention. This method can be implemented through a management interface. Figure 6 As shown, the method may include the following steps.

[0167] S610: The management interface obtains a message, wherein the message indicates an operation related to a first object to be performed in the first system, at least one attribute of the first object is recorded by at least one second object related to the first object, and each attribute in the at least one attribute is recorded as an attribute of the corresponding second object in the at least one second object.

[0168] Specifically, the management interface can retrieve a piece of information. Since the unified management interface can be used to respond to information related to an operation associated with the first object and instruct the first system to perform that operation, unified management of multiple objects across different systems can be achieved. Furthermore, the second object is used to record the attribute information of the first object. Therefore, the attribute information of the first object can be recorded separately by the attributes of the second object associated with the first object, rather than as attributes of the first object itself. This allows attribute information to be created or modified by creating or modifying the corresponding second object, facilitating the modification and synchronization of the same object's attribute information (e.g., identification information) across different systems.

[0169] Furthermore, this message can be a request from a user or a system, without limitation. For example, a request could indicate an operation related to the first object to be performed in the first system.

[0170] Furthermore, at least one attribute of the first object can be recorded by at least one second object associated with the first object, and each of the at least one attribute is recorded as an attribute of the corresponding second object in the at least one second object. Taking the attribute information as identification information as an example, such as... Figure 3 As shown, the first object (e.g., Figure 3 The identification information of an object in the middle can be obtained through a second object (e.g., XXX) with a specific value (e.g., XXX). Figure 3 The attributes of the object identifier in the object (e.g., Figure 3 The identifier in the record is used to record.

[0171] In one possible implementation, at least one second object is associated with a first object through at least one third object, wherein each of the at least one third object indicates a relationship between the first object and a corresponding second object among the at least one second object, and there is a one-to-one correspondence between the first object and each of the at least one third object, and a one-to-one correspondence between each of the at least one third object and a corresponding second object among the at least one second object. In other words, the first object (e.g., an object) and the second object (e.g., an object identifier) ​​can be associated through a relationship between the first object and the second object (e.g., such as...). Figure 3 The identification relationships shown are interconnected. Based on this model, object creation and identification can be separated into two independent processes, and it provides the possibility of adding different identifications to the same object.

[0172] For example, object A could be a car component, identified as XXX in production system A, YYY in supply chain system B, and ZZZ in sales system C. Then, if... Figure 4As shown, object A is the first object. There are three second objects, labeled Object Identifier System A, Object Identifier System B, and Object Identifier System C, respectively. Each second object has an identifier attribute. Each second object records the identification information of object A in the corresponding system. Specifically, Object Identifier System A records the identification information XXX of object A in production system A, Object Identifier System B records the identification information YYY of object A in supply chain system B, and Object Identifier System C records the identification information ZZZ of object A in sales system C. There are three third objects, labeled Identification Relationship A, Identification Relationship B, and Identification Relationship C, respectively. These three third objects describe the one-to-one correspondence between object A and Object Identifier System A, Object Identifier System B, and Object Identifier System C. Based on this model, object A can have different identification information XXX, YYY, and ZZZ in different systems A, B, and C. If additional identification information needs to be added to object A, such as the identification information WWW of object A in the operation and maintenance system D, a corresponding second object (e.g., object identifier system D) and a third object can be added. The second object records the identification information DDD of object A in system D, and the third object describes the relationship between object A and the second object. If a piece of identification information of object A needs to be modified, it can be done by modifying the identifier of the corresponding second object. Of course, the above example is only for illustration and is not intended to be limiting.

[0173] As described above, two types of objects (i.e., a second object and a third object) are used to record the attribute information of the first object. The second object records the attribute information of the first object, and the third object indicates the relationship between the first and second objects. Therefore, multiple attribute information entries for the same object in different systems can be recorded by multiple second and third objects. When the identification information of the first object is recorded in this way, the creation and identification of the first object can be separated into two independent processes. In other words, creation and identification can be performed separately by creating the first object, the second object used to record the identification information, and the third object indicating the relationship between the first and second objects, where the first object is the object to be created. If it is necessary to add another identifier to the first object, another second object and another third object can be added. Therefore, it is possible to add different identifiers to the same object.

[0174] In one possible implementation, the second object can be deleted by deleting the corresponding third object. Taking object A as an example again, if it's necessary to delete the identifier information YYY of object A, this can be achieved by deleting the relation object identifier relationship B. In this way, since the attribute information of the first object is recorded by the second object, the attribute information of the first object can be easily deleted by deleting the corresponding third object. When the second object records additional identifier information of the first object, this additional identifier information can also be deleted from the first object in this way, thus facilitating the management of objects across multiple systems and reducing redundant manual operations for users.

[0175] In one possible implementation, the management interface can be used to provide a unified interface and management entry point for managing objects from at least one system. Because the unified management interface provides a consistent interface and management entry point for managing objects from at least one system, it allows for easy and efficient management of multiple objects from different systems, thus reducing some redundant manual operations for users.

[0176] S620: The management interface responds to receiving a message instructing the first system to perform an operation related to the first object.

[0177] Specifically, taking this single message request as an example, without further limitation, after obtaining a request from the user or system instructing the first system to perform an operation, the management interface can instruct the first system to execute that operation. Since the unified management interface can be used to respond to obtaining information related to an operation concerning a first object and instruct the first system to perform that operation, unified management of multiple objects across different systems can be achieved.

[0178] In one possible implementation, the management interface can instruct the first system to perform operations related to the first object through a pre-configured interface and a communication protocol based on the first system's application programming interface (API). This provides an implementation method for the management interface to instruct the first system. Of course, other implementation methods can also be used, and no limitation is made here.

[0179] In one possible implementation, the operation related to the first object includes at least one of the following: creating the first object in the first system; modifying one attribute of the first object in the first system; or recording one attribute of the first object in the first system. Of course, this operation may also include other actions, which are not limited here.

[0180] The following section will detail the possible implementation methods of this operation.

[0181] In one possible implementation, this information can instruct the creation of a first object in the first system. Specifically, new objects and their corresponding attribute information can be created uniformly based on the unified management interface provided by this invention.

[0182] In one possible implementation, this information could be obtained by the user when adding the first object in the first system through the management interface; then, the management interface could instruct the first system to create the first object in the first system and generate the first attribute information of the first object in the first system.

[0183] Specifically, taking object A as an example again, if a user wants to add object A to production system A, they would use the management interface to add object A. The management interface provided by this invention can be used to add object A to production system A in a convenient and simple way. After receiving a creation request from the user, the management interface can instruct production system A to create object A in production system A and generate the identifier XXX of object A in production system A. In other words, when a user wants to add a new object to the first system, a new object can be easily created in the first system and new attribute information can be generated through the unified management interface without redundant operations.

[0184] In some cases, the first object may also exist in other systems, such as the second system, and the first object may have other attribute information in the second system, such as a second attribute. In one possible implementation, the management interface may instruct the first system to record the second attribute information of the first object; and / or instruct the second system to record the first attribute information of the first object.

[0185] For example, object A may also exist in supply chain system B, with the identifier YYY. After object A with identifier XXX is created in production system A, the identifier YYY of object A in production system B may also need to be recorded in supply chain system A, and / or the identifier XXX of object A in production system A may also need to be recorded in supply chain system B. In this case, the management interface can instruct production system A and / or supply chain system B to record additional identification information of object A. Therefore, the management interface provided by this invention can instruct production system A to record the identifier YYY of object A in supply chain system B as additional identification information of object A in production system A, and / or instruct supply chain system B to record the identifier XXX of object A in production system A as additional identification information of object A in supply chain system B. In other words, if an object created in the first system also exists in other systems, after an object with attribute information is created in the first system, the management interface can instruct the first system to record the attribute information of the object in other systems, and / or instruct other systems to record the attribute information of the first object in the first system, so that the first system and / or other systems can know the attribute information of the first object in different systems, thereby realizing the synchronization of the attribute information of the object in different systems.

[0186] In one possible implementation, a piece of information obtained by the management interface can instruct the modification of a property of a first object in the first system. Specifically, the property information of an object can be modified uniformly based on the unified management interface provided by this invention.

[0187] In one possible implementation, this information may be obtained by the user when modifying the first attribute information of the first object to the first value in the first system through the management interface. This information indicates that the first attribute information of the first object is modified to the first value; the management interface may instruct the first system to modify the first attribute information of the first object to the first value in the first system.

[0188] Figure 7 This is an interaction diagram of an object management method provided by one or more exemplary embodiments of the present invention. For example... Figure 7As shown, taking the modification of object A's identifier as an example, if a user wants to update the object identifier XXX of production system A, the user can change the object identifier XXX of production system A to BBB through the management interface provided by this invention. In this case, the interface instructs production system A to change the object identifier XXX to BBB through a pre-configured interface and a communication protocol based on the system API. When production system A successfully updates, it receives a response, updates the first attribute information of object A, and updates the identifier of object A in production system A to BBB. In other words, when a user wants to modify the first attribute information of a first object in the first system, the unified management interface provides a management entry point to manage objects in different systems. Objects can be managed uniformly, and the attribute information of objects in the first system can be easily modified through the unified management interface without redundant operations. Through the management interface, users can also update other types of attribute information of objects in other systems (e.g., supply chain system B and sales system C as described above), such as name and description.

[0189] In one possible implementation, the first object may also exist in other systems, and these systems can record the object's attribute information in those systems. When the attribute information in other systems changes, the information recorded in the first system also needs to be updated to synchronize the object's attribute information across different systems. When the second system has modified the second attribute information of the first object to a second value in the second system, and the second system records that the second attribute information is related to the first object in the first system, the second system can send a message to the management interface instructing that the second attribute information of the first object be modified to a second value. After receiving this message from the second system, the management interface can instruct the first system to modify the second attribute information of the first object to a second value in the first system.

[0190] Figure 8 This is another interaction diagram of the object management method provided by one or more exemplary embodiments of the present invention. For example... Figure 8As shown, taking updating the identifier of object A as an example again, if supply chain system B updates the identifier of object A from YYY to CCC, and supply chain system B records that YYY is related to object A in production system A, then supply chain system B can notify production system A to update the second attribute of object A through the management interface. (Update the second attribute of object A to CCC to indicate that the ID of object A has been changed to CCC in supply chain system B.) The implementation of the update notification may require supply chain system B to modify and adapt to some extent. In other words, if the second system has modified the second attribute information of the first object in the second system, and the second attribute information of the first object in the second system is related to the first object in the first system, that is, the first system also records the second attribute information of the first object, then the unified management interface can serve as a unified interface to manage objects in different systems. In particular, the second system can notify the first system through the unified management interface to modify the second attribute information of the first object in the first system to the second value. Therefore, the synchronization of the attribute information of objects in different systems can be achieved in a simple and convenient way.

[0191] In one possible implementation, attribute information synchronization between different systems can be achieved based on queries. The management interface can respond to a query to see if the third attribute information in the third system has been modified from the first system, obtain the third attribute information of the first object in the third system, then determine whether the third attribute information has been modified, and in response to determining that the third attribute information of the first object has been changed to a third value, instruct the first system to modify the third attribute information of the first object to the third value in the first system.

[0192] In one possible implementation, determining whether the third attribute information has been changed can be done by the first system. For example, the first system can query the third attribute information of the first object in the third system through an open interface or a management interface. After obtaining the third attribute information, the first system can determine whether the third attribute information has been changed. If the third attribute information has been changed to a new value, the first system can update the recorded third attribute information to the new value.

[0193] In one possible implementation, querying the third attribute information and determining whether the third attribute information in the third system has been modified can be performed periodically. The synchronization period can be set according to actual needs, thus providing more options for different scenarios and conditions.

[0194] In one possible implementation, Figure 8The synchronization shown can also be achieved in another way. This method does not require modification or adaptation of supply chain system B or other systems. System A can periodically query through an open interface to determine if the ID of object A (e.g., YYYY) has been updated. If so, the second attribute of object A is updated. In other words, the first system will proactively query based on the open (management) interface to determine if the third system has modified the third attribute information of the object in the third system. If the third system has modified the third attribute of the object in the third system, the first system can modify the third attribute information of the object recorded in the first system. Therefore, the synchronization of the attribute information of an object in different systems can be achieved in a simple and convenient way. In addition, the query can be performed periodically, and the synchronization cycle can be set according to actual needs, which provides a synchronization method that offers more options for different scenarios and conditions.

[0195] In one possible implementation, the first object can be newly created in another system (e.g., a fourth system), where attribute information, such as a fourth attribute, can also be generated for the first object. After the first object is created in the fourth system and its fourth attribute information is generated there, the management interface can retrieve a message from the fourth system containing the fourth attribute information of the first object. The management interface can then instruct the first system to record this fourth attribute information.

[0196] Figure 9 This is another interaction diagram of the object management method provided by one or more exemplary embodiments of the present invention. For example... Figure 9As shown, taking object A as an example again, if object A only exists in production system A, supply chain system B, and sales system C, and the user wants to add this object to O&M system D, the user can create object A in O&M system D through the management interface provided by this invention. O&M system D generates a new identifier WWW for object A based on the system identifier creation rules and returns the new identifier WWW to the management interface. Then, the management interface can inform production system A of the object's identifier WWW. In this case, production system A records object A with four attributes. The first attribute is the identifier XXX of object A in production system A, the second attribute is the identifier YYYY of object A in supply chain system B, the third attribute is the identifier ZZZ of object A in sales system C, and the fourth attribute is the identifier WWW of object A in O&M system D. Furthermore, the management interface (application collaboration interface) can inform systems B and C that a new identifier needs to be added from system D. In other words, if a newly created object in another system also exists in the first system, then after the object is created and its attribute information is generated in the fourth system, the management interface can instruct the first system to record the attribute information of the object in other systems. This allows the first system to know that other systems also have the object and have recorded the corresponding attribute information, thereby achieving the synchronization of the object's attribute information in different systems.

[0197] In one possible implementation, the attribute information indicates one of the following: the identifier of the first object, the description information of the first object, or the address information of the first object.

[0198] Besides modifying and synchronizing identifier information, the system can also perform other functions. For example, users can record other attribute information of object A. The production system A corresponding to object A can use Chinese. In this case, the payload of the text message sent to production system A is sent in Chinese. (For example: modifying the description of object A in production system A.) Users can also configure the sales system corresponding to object A to use English. Then, the updated description of object A will be sent in English. By managing multiple attributes of object A, the system can create, update, and manage identifier-type and various non-identifier-type information (e.g., description information, address information, etc.). In other words, since the attribute information of an object can indicate various information, such as the object's identifier, description information, or address information, different object information in different systems can be created, modified, and synchronized in a simple and convenient way through the management interface.

[0199] In one possible implementation, the first system is one of a production system, a supply chain system, a sales system, or an operations and maintenance system, without any limitation here.

[0200] Specifically, the management interface can be used to manage different systems such as production systems, supply chain systems, sales systems, or operation and maintenance systems, thereby enabling unified management of multiple objects in these systems.

[0201] The object management communication method provided by this invention, after obtaining a message indicating an operation related to a first object to be performed in a first system, can use a unified management interface to respond to the message and instruct the system to perform the operation related to the object. At least one attribute of the first object is recorded by at least one second object associated with the first object, and each of the at least one attribute is recorded as an attribute of the corresponding second object within the at least one second object. Therefore, unified management of multiple objects in different systems can be achieved. Furthermore, since the second object is used to record the attribute information of the first object, the attribute information of the first object can be recorded separately by the attributes of the second object associated with the first object, rather than as an attribute of the first object itself. This allows the creation or modification of attribute information to be achieved by creating or modifying the corresponding second object, thereby facilitating the modification and synchronization of the attribute information (e.g., identification information) of the same object in different systems.

[0202] The above text combined Figures 6 to 9 The object management communication method of this invention is described from the perspective of the management interface. The following will combine... Figure 10 The object management communication method of the present invention is described from the perspective of a first system.

[0203] Figure 10 This is another illustrative flowchart of an object management method provided by one or more exemplary embodiments of the present invention. This method can be implemented using a first system. Figure 10 As shown, the method may include the following steps.

[0204] S1010: The first system obtains instructions from the management interface.

[0205] Specifically, the first system can obtain instructions from the management interface. Since the first system can execute operations related to the first object based on the instructions given through the unified management interface, unified management of multiple objects in different systems can be achieved.

[0206] S1020: In response to the instruction, the first system performs an operation related to the first object, wherein the instruction indicates the operation related to the first object to be performed in the first system, at least one attribute information of the first object is recorded by at least one second object related to the first object, and each attribute information in the at least one attribute information is recorded as an attribute of the corresponding second object in at least one second object.

[0207] Specifically, the first system can obtain instructions from a unified management interface and then execute operations in response to those instructions. This enables unified management of multiple objects across different systems. Furthermore, the second object records the attribute information of the first object. Therefore, the attribute information of the first object can be recorded separately by the attributes of the second object associated with the first object, rather than being recorded as attributes of the first object itself. This allows attribute information to be created or modified by creating or modifying the corresponding second object, facilitating the modification and synchronization of the same object's attribute information (e.g., identification information) across different systems.

[0208] Furthermore, at least one attribute of the first object can be recorded by at least one second object associated with the first object, and each of the at least one attribute is recorded as an attribute of the corresponding second object in the at least one second object. Taking the attribute information as identification information as an example, such as... Figure 3 As shown, the first object (e.g., Figure 3 The identification information of an object in the middle can be obtained through a second object (e.g., XXX) with a specific value (e.g., XXX). Figure 3 The attributes of the object identifier in the object (e.g., Figure 3 The identifier in the record is used to record.

[0209] In one possible implementation, at least one second object is associated with a first object through at least one third object, wherein each of the at least one third object indicates a relationship between the first object and a corresponding second object among the at least one second object, and there is a one-to-one correspondence between the first object and each of the at least one third object, and a one-to-one correspondence between each of the at least one third object and a corresponding second object among the at least one second object. In other words, the first object (e.g., an object) and the second object (e.g., an object identifier) ​​can be associated through a relationship between the first object and the second object (e.g., such as...). Figure 3 The identification relationships shown are interconnected. Based on this model, object creation and identification can be separated into two independent processes, and it provides the possibility of adding different identifications to the same object.

[0210] For example, object A could be a car component, identified as XXX in production system A, YYY in supply chain system B, and ZZZ in sales system C. Then, if... Figure 4As shown, object A is the first object. There are three second objects, labeled Object Identifier System A, Object Identifier System B, and Object Identifier System C, respectively. Each second object has an identifier attribute. Each second object records the identification information of object A in the corresponding system. Specifically, Object Identifier System A records the identification information XXX of object A in production system A, Object Identifier System B records the identification information YYY of object A in supply chain system B, and Object Identifier System C records the identification information ZZZ of object A in sales system C. There are three third objects, labeled Identification Relationship A, Identification Relationship B, and Identification Relationship C, respectively. These three third objects describe the one-to-one correspondence between object A and Object Identifier System A, Object Identifier System B, and Object Identifier System C. Based on this model, object A can have different identification information XXX, YYY, and ZZZ in different systems A, B, and C. If additional identification information needs to be added to object A, such as the identification information WWW of object A in the operation and maintenance system D, a corresponding second object (e.g., object identifier system D) and a third object can be added. The second object records the identification information DDD of object A in system D, and the third object describes the relationship between object A and the second object. If a piece of identification information of object A needs to be modified, it can be done by modifying the identifier of the corresponding second object. Of course, the above example is only for illustration and is not intended to be limiting.

[0211] As described above, two types of objects (i.e., a second object and a third object) are used to record the attribute information of the first object. The second object records the attribute information of the first object, and the third object indicates the relationship between the first and second objects. Therefore, multiple attribute information entries for the same object in different systems can be recorded by multiple second and third objects. When the identification information of the first object is recorded in this way, the creation and identification of the first object can be separated into two independent processes. In other words, creation and identification can be performed separately by creating the first object, the second object used to record the identification information, and the third object indicating the relationship between the first and second objects, where the first object is the object to be created. If it is necessary to add another identifier to the first object, another second object and another third object can be added. Therefore, it is possible to add different identifiers to the same object.

[0212] In one possible implementation, the second object can be deleted by deleting the corresponding third object. Taking object A as an example again, if it's necessary to delete the identifier information YYY of object A, this can be achieved by deleting the relation object identifier relationship B. In this way, since the attribute information of the first object is recorded by the second object, the attribute information of the first object can be easily deleted by deleting the corresponding third object. When the second object records additional identifier information of the first object, this additional identifier information can also be deleted from the first object in this way, thus facilitating the management of objects across multiple systems and reducing redundant manual operations for users.

[0213] In one possible implementation, the management interface can be used to provide a unified interface and management entry point for managing objects from at least one system. Because the unified management interface provides a consistent interface and management entry point for managing objects from at least one system, it allows for easy and efficient management of multiple objects from different systems, thus reducing some redundant manual operations for users.

[0214] In one possible implementation, the first system can obtain instructions from the management interface through a pre-configured interface and a communication protocol based on the first system's application programming interface (API). This provides one way for the first system to obtain instructions. Of course, other implementation methods can also be used, and no limitation is made here.

[0215] In one possible implementation, the operation related to the first object includes at least one of the following: creating the first object in the first system; modifying one attribute of the first object in the first system; or recording one attribute of the first object in the first system. Of course, this operation may also include other actions, which are not limited here.

[0216] The following section will detail the possible implementation methods of this operation.

[0217] In one possible implementation, the instruction directs the creation of a first object in a first system. Specifically, the creation of new objects and their corresponding attribute information can be unified based on the unified management interface provided by this invention.

[0218] In one possible implementation, the instruction is obtained when the user adds a first object in the first system through the management interface; then, the first system can create the first object in the first system and generate the first attribute information of the first object in the first system.

[0219] Specifically, taking object A as an example again, if a user wants to add object A to production system A, they use the management interface to add object A. The management interface provided by this invention can be used to add object A to production system A in a convenient and simple way. After receiving a creation request from the user, production system A can be instructed by the management interface to create object A in production system A and generate the identifier XXX of object A in production system A. In other words, when a user wants to add a new object to the first system, a new object can be easily created in the first system and new attribute information can be generated through the unified management interface without redundant operations.

[0220] In some cases, the first object may also exist in other systems, such as the second system, and the first object may have other attribute information in the second system, such as a second attribute. In one possible implementation, the first system can obtain the second attribute information of the first object from the management interface and record the second attribute information of the first object; or it can inform the second system of the first object's first attribute information through the management interface.

[0221] For example, object A may also exist in supply chain system B, with the identifier YYY. After object A with identifier XXX is created in production system A, the identifier YYY of object A in production system B may also need to be recorded in supply chain system A, and / or the identifier XXX of object A in production system A may also need to be recorded in supply chain system B. In this case, production system A and / or supply chain system B can instruct the recording of additional identification information of object A via a management interface. Therefore, the management interface provided by this invention can instruct production system A to record the identifier YYY of object A in supply chain system B as additional identification information of object A in production system A, and / or instruct supply chain system B to record the identifier XXX of object A in production system A as additional identification information of object A in supply chain system B. In other words, if an object created in the first system also exists in other systems, after an object with attribute information is created in the first system, the management interface can instruct the first system to record the attribute information of the object in other systems, and / or instruct other systems to record the attribute information of the first object in the first system, so that the first system and / or other systems can know the attribute information of the first object in different systems, thereby realizing the synchronization of the attribute information of the object in different systems.

[0222] In one possible implementation, the instruction directs the modification of an attribute of a first object within the first system. Specifically, the attribute information of an object can be modified uniformly based on the unified management interface provided by this invention.

[0223] In one possible implementation, the instruction could be obtained when a user modifies the first attribute information of a first object to a first value through a management interface in the first system. This instruction instructs the modification of the first attribute information of the first object to the first value; then, the first system can modify the first attribute information of the first object to the first value within the first system. An example is shown below. Figure 7 As shown, for the sake of simplicity, this will not be discussed further here. In other words, when a user wants to modify the first attribute information of a first object in the first system, the unified management interface provides a management entry point to manage objects in different systems. Objects can be managed uniformly, and the attribute information of objects in the first system can be easily modified through the unified management interface without redundant operations. Through the management interface, users can also update other types of attribute information of objects in other systems (e.g., supply chain system B and sales system C as mentioned above), such as name and description.

[0224] In one possible implementation, the first object can also exist in other systems, and these systems can record the object's attribute information in those systems. When the attribute information in other systems changes, the information recorded in the first system also needs to be updated to synchronize the object's attribute information across different systems. When the first system receives an instruction that the second attribute information of the first object has been modified to a second value in the second system, and the second system records that the second attribute information is related to the first object in the first system, and this instruction indicates that the second attribute information of the first object should be modified to a second value, the first system can then modify the second attribute information of the first object to a second value in the first system. An example is shown below. Figure 8 As shown, for the sake of simplicity, this will not be discussed further here. In other words, if the second system has modified the second attribute information of the first object in the second system, and the second attribute information of the first object in the second system is related to the first object in the first system (i.e., the first system also records the second attribute information of the first object), then the unified management interface can serve as a unified interface to manage objects in different systems. Furthermore, the first system can instruct, through the management interface, to modify the recorded second attribute information of the first object in the first system to the second value. Therefore, the synchronization of object attribute information across different systems can be achieved in a simple and convenient way.

[0225] In one possible implementation, attribute information synchronization between different systems can be achieved based on queries. The management interface can respond to a query to see if the third attribute information in the third system has been modified from the first system, obtain the third attribute information of the first object in the third system, then determine whether the third attribute information has been modified. Furthermore, in response to determining that the third attribute information of the first object has been changed to a third value, the first system can be instructed to modify the third attribute information of the first object to the third value in the first system.

[0226] In one possible implementation, determining whether the third attribute information has been changed can be done by the first system. For example, the first system can query the third attribute information of the first object in the third system through an open interface or a management interface. After obtaining the third attribute information, the first system can determine whether the third attribute information has been changed. If the third attribute information has been changed to a new value, the first system can update the recorded third attribute information to the new value.

[0227] In one possible implementation, querying the third attribute information and determining whether the third attribute information in the third system has been modified can be performed periodically. The synchronization period can be set according to actual needs, thus providing more options for different scenarios and conditions. In other words, the first system will actively query based on the open (management) interface to determine whether the third system has modified the object's third attribute information in the third system. If the third system has modified the object's third attribute in the third system, the first system can modify the object's third attribute information recorded in the first system. Therefore, the synchronization of object attribute information across different systems can be achieved in a simple and convenient way. Furthermore, the query can be performed periodically, and the synchronization period can be set according to actual needs, providing a synchronization method that offers more options for different scenarios and conditions.

[0228] In one possible implementation, the first object can be newly created in another system (e.g., a fourth system), and attribute information, such as a fourth attribute, can also be generated for the first object in that system. If the fourth system creates the first object and generates its fourth attribute in the fourth system, the first system can receive an instruction to record the fourth attribute of the first object; then, the first system can record the fourth attribute of the first object. An example is shown below. Figure 9As shown, for the sake of simplicity, this will not be discussed further here. In other words, if a newly created object in another system also exists in the first system, then after the object is created and its attribute information is generated in the fourth system, the first system can, through the management interface, instruct the recording of the object's attribute information in other systems. This allows the first system to know that other systems also have the object and have recorded the corresponding attribute information, thereby achieving synchronization of the object's attribute information across different systems.

[0229] In one possible implementation, the attribute information indicates one of the following: the identifier of the first object, the description information of the first object, or the address information of the first object.

[0230] Besides modifying and synchronizing identifier information, the system can also perform other functions. For example, users can record other attribute information of object A. The production system A corresponding to object A can use Chinese. In this case, the payload of the text message sent to production system A is sent in Chinese. (For example: modifying the description of object A in production system A.) Users can also configure the sales system corresponding to object A to use English. Then, the updated description of object A will be sent in English. By managing multiple attributes of object A, the system can create, update, and manage identifier-type and various non-identifier-type information (e.g., description information, address information, etc.). In other words, since the attribute information of an object can indicate various information, such as the object's identifier, description information, or address information, different object information in different systems can be created, modified, and synchronized in a simple and convenient way through the management interface.

[0231] In one possible implementation, the first system is one of a production system, a supply chain system, a sales system, or an operations and maintenance system, without any limitation here.

[0232] Specifically, the management interface can be used to manage different systems such as production systems, supply chain systems, sales systems, or operation and maintenance systems, thereby enabling unified management of multiple objects in these systems.

[0233] The object management communication method provided by this invention allows the first system to execute operations related to a first object after receiving instructions to perform such operations in the first system. At least one attribute of the first object is recorded by at least one second object associated with it, and each of these attribute pieces is recorded as an attribute of the corresponding second object within that first object. Therefore, unified management of multiple objects across different systems can be achieved. Furthermore, since the second object records the attribute information of the first object, the attribute information of the first object can be recorded separately by the attributes of the second object associated with it, rather than as an attribute of the first object itself. This allows the creation or modification of attribute information by creating or modifying the corresponding second object, facilitating the modification and synchronization of the attribute information (e.g., identification information) of the same object across different systems.

[0234] The following section will describe product examples related to object management communication methods.

[0235] Figure 11 This is a schematic diagram of the structure of the management interface provided by one or more exemplary embodiments of the present invention.

[0236] like Figure 11 As shown, the management interface 1100 includes: an acquisition module 1110, used to acquire a piece of information, wherein the piece of information indicates an operation related to a first object to be performed in the first system, at least one attribute information of the first object is recorded by at least one second object related to the first object, and each attribute information in the at least one attribute information is recorded as an attribute of the corresponding second object in the at least one second object; and an instruction module 1120, used to instruct the first system to perform an operation related to the first object in response to acquiring a piece of information.

[0237] In one possible implementation, at least one second object is associated with a first object through at least one third object, wherein each of the at least one third object indicates a relationship between the first object and a corresponding second object among the at least one second object, and there is a one-to-one correspondence between the first object and each of the at least one third object, and a one-to-one correspondence between each of the at least one third object and a corresponding second object among the at least one second object.

[0238] In one possible implementation, each of the at least one second object is deleted by deleting the corresponding third object in at least one third object.

[0239] In one possible implementation, the management interface is used to provide a unified interface and management entry point for managing objects from at least one system.

[0240] In one possible implementation, the instruction module 1120 is further configured to instruct the first system to perform operations related to the first object via a pre-configured interface and a communication protocol based on the first system's application programming interface (API).

[0241] In one possible implementation, the operation related to the first object includes at least one of the following: creating the first object in the first system; modifying one attribute of the first object in the first system; or recording one attribute of the first object in the first system.

[0242] In one possible implementation, the message instructs the creation of a first object in the first system.

[0243] In one possible implementation, this information is obtained by the user when adding the first object in the first system through the management interface; the instruction module 1120 is also used to instruct the first system to create the first object in the first system and generate the first attribute information of the first object in the first system.

[0244] In one possible implementation, the first object exists in the second system, and the first object has a second attribute information in the second system. The instruction module 1120 is also used to instruct the first system to record the second attribute information of the first object; or, the instruction module 1120 is also used to instruct the second system to record the first attribute information of the first object.

[0245] In one possible implementation, the message indicates the modification of an attribute of the first object in the first system.

[0246] In one possible implementation, the information is obtained when the user modifies the first attribute information of the first object to the first value in the first system through the management interface. The information indicates that the first attribute information of the first object is modified to the first value. The instruction module 1120 is also used to instruct the first system to modify the first attribute information of the first object to the first value in the first system.

[0247] In one possible implementation, the information is obtained by the management interface from the second system when the second system has modified the second attribute information of the first object to the second value in the second system. The second system records that the second attribute information is related to the first object in the first system, and the information indicates that the second attribute information of the first object should be modified to the second value. The instruction module 1120 is also used to instruct the first system to modify the second attribute information of the first object to the second value in the first system.

[0248] In one possible implementation, the acquisition module 1110 is further configured to acquire the third attribute information of the first object in the third system in response to querying whether the third attribute information in the third system has been modified from the first system. The management interface further includes: a determination module 1130, configured to determine whether the third attribute information has been modified, and in response to determining that the third attribute information of the first object has been changed to a third value, the instruction module 1120 is further configured to instruct the first system to modify the third attribute information of the first object to a third value in the first system.

[0249] In one possible implementation, the query to see if the third attribute information in the third system has been modified is performed periodically.

[0250] In one possible implementation, the information is obtained from the fourth system after the fourth system creates the first object and generates the fourth attribute information of the first object in the fourth system. The information includes the fourth attribute information of the first object, and the instruction module 1120 is also used to instruct the first system to record the fourth attribute information of the first object.

[0251] In one possible implementation, the attribute information indicates one of the following: the identifier of the first object, the description information of the first object, or the address information of the first object.

[0252] In one possible implementation, the first system is one of a production system, a supply chain system, a sales system, or an operations and maintenance system.

[0253] The management interface can execute the various steps of the object management method described in the possible implementations of the present invention. Those skilled in the art should understand that, in conjunction with the descriptions of the object management method in these possible implementations of the present invention, the descriptions of the modules described above in these possible implementations can be understood. The technical effects achieved by the management interface are similar to those achieved by the possible implementations of the present invention, and will not be repeated here.

[0254] Figure 12 This is a schematic diagram of the structure of a first system provided by one or more exemplary embodiments of the present invention.

[0255] like Figure 12 As shown, the first system 1200 includes: an acquisition module 1210 for acquiring instructions from a management interface; and an execution module 1220 for performing an operation related to a first object in response to the instructions. The instructions indicate the operation related to the first object to be performed in the first system. At least one attribute information of the first object is recorded by at least one second object related to the first object, and each attribute information in the at least one attribute information is recorded as an attribute of the corresponding second object in the at least one second object.

[0256] In one possible implementation, at least one second object is associated with a first object through at least one third object, wherein each of the at least one third object indicates a relationship between the first object and a corresponding second object among the at least one second object, and there is a one-to-one correspondence between the first object and each of the at least one third object, and a one-to-one correspondence between each of the at least one third object and a corresponding second object among the at least one second object.

[0257] In one possible implementation, each of the at least one second object is deleted by deleting the corresponding third object in at least one third object.

[0258] In one possible implementation, the management interface is used to provide a unified interface and management entry point for managing objects from at least one system.

[0259] In one possible implementation, the acquisition module 1210 is also used to acquire instructions from the management interface via a pre-configured interface and a communication protocol based on the application programming interface (API) of the first system.

[0260] In one possible implementation, the operation related to the first object includes at least one of the following: creating the first object in the first system; modifying one attribute of the first object in the first system; or recording one attribute of the first object in the first system.

[0261] In one possible implementation, the instruction directs the creation of a first object in a first system.

[0262] In one possible implementation, the instruction is obtained by the user when adding the first object in the first system through the management interface; the execution module 1220 is also used to create the first object in the first system and generate the first attribute information of the first object in the first system.

[0263] In one possible implementation, the first object exists in the second system, and the first object has a second attribute information in the second system; wherein, the acquisition module 1210 is further used to acquire the second attribute information of the first object from the management interface; the execution module 1220 is further used to: record the second attribute information of the first object, and inform the second system of the first attribute information of the first object through the management interface.

[0264] In one possible implementation, the instruction directs the modification of a property of a first object in the first system.

[0265] In one possible implementation, the instruction is obtained by the user when modifying the first attribute information of the first object to the first value through the management interface in the first system. The instruction indicates that the first attribute information of the first object should be modified to the first value. The execution module 1220 is also used to modify the first attribute information of the first object to the first value in the first system.

[0266] In one possible implementation, the instruction is obtained after the second system has modified the second attribute information of the first object to the second value in the second system. The second system records that the second attribute information is related to the first object in the first system. The instruction instructs to modify the second attribute information of the first object to the second value. The execution module 1220 is also used to modify the second attribute information of the first object to the second value in the first system.

[0267] In one possible implementation, the execution module 1220 is further configured to query whether the third attribute information in the third system has been modified; wherein, the instruction is obtained when the third attribute information of the first object has been changed to a third value, and the instruction indicates that the third attribute information of the first object be modified to a third value; the execution module 1220 is further configured to modify the third attribute information of the first object to a third value in the first system.

[0268] In one possible implementation, the query to see if the third attribute information in the third system has been modified is performed periodically.

[0269] In one possible implementation, the instruction is obtained when the fourth system creates the first object in the fourth system and generates the fourth attribute information of the first object. The instruction instructs the recording of the fourth attribute information of the first object. The execution module 1220 is also used to record the fourth attribute information of the first object.

[0270] In one possible implementation, the attribute information indicates one of the following: the identifier of the first object, the description information of the first object, or the address information of the first object.

[0271] In one possible implementation, the first system is one of a production system, a supply chain system, a sales system, or an operations and maintenance system.

[0272] The first system can execute the various steps of the object management method of the first system described in the above possible method implementations. Those skilled in the art should understand that, in conjunction with the relevant descriptions of the object management method in these possible implementations of the present invention, the relevant descriptions of the above-mentioned modules in these possible implementations of the present invention can be understood. The technical effects achieved by the first system described above are similar to those achieved by the above possible method implementations, and will not be repeated here.

[0273] One possible implementation of the present invention provides a management interface including a processing circuit, which is used to execute any of the corresponding object management methods described above on the management interface side, and will not be described in detail here.

[0274] One possible implementation of the present invention provides a management interface, including a processing circuit, which is used to execute any of the corresponding object management methods described above on the first system side, and will not be elaborated further here.

[0275] One possible implementation of the present invention provides an object management system, comprising: a management interface for executing any of the corresponding object management methods described above on the management interface side; a first system for executing any of the corresponding object management methods described above on the first system side; and at least one fifth system, wherein the at least one fifth system is one of a production system, a supply chain system, a sales system, or an operation and maintenance system. The methods described above will not be elaborated further here.

[0276] One possible implementation of the present invention provides an object management system, comprising: a first processing circuit for executing any of the corresponding object management methods described above on a management interface side; a second processing circuit for executing any of the corresponding object management methods described above on a first system side; and at least one third processing circuit, wherein the at least one third processing circuit belongs to one of a production system, a supply chain system, a sales system, or an operation and maintenance system.

[0277] One possible implementation of the present invention provides a computer-readable storage medium that stores computer-executable instructions that, when executed by a processor, cause the processor to perform any of the aforementioned sensing communication methods, which will not be elaborated further here.

[0278] One possible implementation of the present invention provides a computer program product including computer-executable instructions that, when executed by a processor, cause the processor to perform any of the aforementioned sensing communication methods, which will not be elaborated further here.

[0279]

[0280] 1. A new unified management interface is provided to manage user objects in different systems.

[0281] 2. The system provides a new set of working methods and processes for creating objects, modifying information (e.g., modifying IDs), and synchronizing information across multiple systems.

[0282]

[0283] 1. The interfaces include display, creation, and modification functions. Through these interfaces, we can provide object information management capabilities.

[0284] 2. Through the new interfaces and methods provided by this solution, users can manage the identifiers of objects in different systems.

[0285]

[0286] PLM: Product Lifecycle Management;

[0287] PDM: Product Data Management;

[0288] ERP: Enterprise Resource Planning

[0289] SPDM: Simulation Process and Data Management

[0290] O&M: Operations and Maintenance

[0291] A data model is an abstract model that organizes data elements and standardizes the relationships between these data elements and their relationships to the attributes of real-world entities. For example, a data model might specify that the data elements representing a car are composed of many other elements, which in turn represent the car's color and size and define its owner. Furthermore, in the data model of a data management system, different data objects exist to store object metadata and identification information.

[0292] Please note that different embodiments can be implemented individually or in combination. Although combinations of features are shown in the illustrated embodiments, it is not necessary to combine all features to achieve the advantages of the various embodiments of the invention. In other words, a system or method designed according to one embodiment of the invention does not necessarily include any of the features shown in the drawings or in all portions schematically illustrated in the drawings. Furthermore, selected features of one exemplary embodiment may be combined with selected features of other exemplary embodiments.

[0293] Although the invention has been described with reference to illustrative embodiments, this description is not intended to limit the invention. Those skilled in the art will understand, upon referring to this description, various modifications and combinations of the illustrative embodiments, as well as other embodiments of the invention. Therefore, the appended claims are intended to cover any such modifications or embodiments.

[0294] Although the present invention describes methods and processes by steps performed in a certain order, one or more steps in the methods and processes may be omitted or modified as appropriate. Where appropriate, one or more steps may be performed in an order other than that described.

[0295] Please note that the expression "at least one of A or B" used in this article is interchangeable with the expression "A and / or B". This expression refers to a list in which you can choose either A or B, or A and B. Similarly, the expression "at least one of A, B, or C" used in this article is interchangeable with "A and / or B and / or C" or "A, B, and / or C". This refers to a list in which you can choose: A or B or C, or A and B, or A and C, or B and C, or all of A, B, and C. The same principle applies to longer lists with the same format.

[0296] Although the invention has been described at least partially in terms of method, those skilled in the art will understand that the invention is also directed to various components for performing at least some aspects and features of the method, whether by hardware components, software, or any combination thereof. Accordingly, the technical solutions of the invention can be embodied in the form of a software product. Suitable software products can be stored in pre-recorded storage devices or other similar non-volatile or non-transitory computer-readable storage media, including DVDs, CD-ROMs, USB flash drives, removable hard drives, or other storage media. The software product includes instructions tangibly stored thereon that enable a processing device (e.g., a personal computer, server, or network device) to perform examples of the methods disclosed herein. Machine-executable instructions can be in the form of code sequences, configuration information, or other data that, when executed, cause a machine (e.g., a processor or other processing device) to perform the steps in the methods according to examples of the invention.

[0297] All values ​​and sub-ranges within the disclosed scope are also disclosed. Furthermore, while the systems, devices, and processes disclosed and illustrated herein may include a specific number of elements / components, these systems, devices, and components may be modified to include more or fewer of such elements / components. For example, although any element / component disclosed may be referenced as a single quantity, possible implementations disclosed herein may be modified to include multiple such elements / components. The topics described herein are intended to cover and encompass all appropriate technical changes.

Claims

1. An object management method, characterized in that, include: The management interface obtains a message, wherein the message indicates an operation related to a first object to be performed in the first system, wherein at least one attribute of the first object is recorded by at least one second object related to the first object, and each attribute of the at least one attribute is recorded as an attribute of the corresponding second object in the at least one second object; In response to receiving a message, the management interface instructs the first system to perform the operation related to the first object.

2. The method according to claim 1, characterized in that, The at least one second object is associated with the first object through at least one third object, wherein each of the at least one third object indicates the relationship between the first object and a corresponding second object among the at least one second object, and there is a one-to-one correspondence between the first object and each of the at least one third object, and a one-to-one correspondence between each of the at least one third object and the corresponding second object among the at least one second object.

3. The method according to claim 2, characterized in that, Each of the at least one second object is deleted by deleting the corresponding third object in the at least one third object.

4. The method according to any one of claims 1 to 3, characterized in that, The management interface is used to provide a unified interface and management entry point for managing objects from at least one system.

5. The method according to any one of claims 1 to 4, characterized in that, The instruction to the first system to perform the operation related to the first object includes: The management interface instructs the first system to perform the operations related to the first object through a pre-configured interface and a communication protocol based on the first system's application programming interface (API).

6. The method according to any one of claims 1 to 5, characterized in that, The operations associated with the first object include at least one of the following: Create the first object in the first system; Modify one attribute of the first object in the first system; or Record one attribute information of the first object in the first system.

7. The method according to any one of claims 1 to 6, characterized in that, The message indicates that the first object is created in the first system.

8. The method according to claim 7, characterized in that, The aforementioned piece of information is obtained when the user adds the first object in the first system through the management interface; The instruction to the first system to perform the operation related to the first object includes: The management interface instructs the first system to create the first object in the first system and generate the first attribute information of the first object in the first system.

9. The method according to claim 8, characterized in that, The first object exists in the second system, and the first object has a second attribute information in the second system. The method further includes at least one of the following: The management interface instructs the first system to record the second attribute information of the first object; or The management interface instructs the second system to record the first attribute information of the first object.

10. The method according to any one of claims 1 to 6, characterized in that, The message indicates that an attribute of the first object is modified in the first system.

11. The method according to claim 10, characterized in that, The information is obtained when the user modifies the first attribute information of the first object to the first value in the first system through the management interface. The information indicates that the first attribute information of the first object is modified to the first value. The instruction to the first system to perform the operation related to the first object includes: The management interface instructs the first system to modify the first attribute information of the first object to the first value within the first system.

12. The method according to claim 10, characterized in that, The aforementioned message is obtained by the management interface from the second system when the second system has modified the second attribute information of the first object to the second value in the second system. The second system records that the second attribute information is related to the first object in the first system, and the message indicates that the second attribute information of the first object has been modified to the second value. The instruction to the first system to perform the operation related to the first object includes: The management interface instructs the first system to modify the second attribute information of the first object to the second value within the first system.

13. The method according to any one of claims 1 to 6, characterized in that, Also includes: The management interface responds to a query to see if the third attribute information in the third system has been modified from the first system, and obtains the third attribute information of the first object in the third system; The management interface determines whether the third attribute information has been modified. In response to determining that the third attribute information of the first object has been changed to a third value, instructing the first system to perform the operation related to the first object includes: The management interface instructs the first system to modify the third attribute information of the first object to the third value within the first system.

14. The method according to claim 13, characterized in that, The query to determine whether the third attribute information in the third system has been modified is performed periodically.

15. The method according to any one of claims 1 to 6, characterized in that, The information is obtained from the fourth system after the first object is created in the fourth system and the fourth attribute information of the first object is generated in the fourth system. The information includes the fourth attribute information of the first object. The instruction to the first system to perform the operation related to the first object includes: The management interface instructs the first system to record the fourth attribute information of the first object.

16. The method according to any one of claims 1 to 15, characterized in that, The attribute information indicates one of the following: The identifier of the first object; Description information of the first object; or The address information of the first object.

17. The method according to any one of claims 1 to 16, characterized in that, The first system is one of the following: production system, supply chain system, sales system, or operation and maintenance system.

18. An object management method, characterized in that, include: The first system obtains instructions from the management interface; The first system responds to the instruction and performs an operation related to the first object; The instruction indicates the operation related to the first object to be performed in the first system, wherein at least one attribute information of the first object is recorded by at least one second object related to the first object, and each of the at least one attribute information is recorded as an attribute of the corresponding second object in the at least one second object.

19. The method according to claim 18, characterized in that, The at least one second object is associated with the first object through at least one third object, wherein each of the at least one third object indicates the relationship between the first object and a corresponding second object among the at least one second object, and there is a one-to-one correspondence between the first object and each of the at least one third object, and a one-to-one correspondence between each of the at least one third object and the corresponding second object among the at least one second object.

20. The method according to claim 19, characterized in that, Each of the at least one second object is deleted by deleting the corresponding third object in the at least one third object.

21. The method according to any one of claims 18 to 20, characterized in that, The management interface is used to provide a unified interface and management entry point for managing objects from at least one system.

22. The method according to any one of claims 18 to 21, characterized in that, The process of obtaining instructions from the management interface includes: The first system obtains the instructions from the management interface through a pre-configured interface and a communication protocol based on the application programming interface (API) of the first system.

23. The method according to any one of claims 18 to 22, characterized in that, The operations associated with the first object include at least one of the following: Create the first object in the first system; Modify one attribute of the first object in the first system; or Record one attribute information of the first object in the first system.

24. The method according to any one of claims 18 to 23, characterized in that, The instruction instructs that the first object be created in the first system.

25. The method according to claim 24, characterized in that, The instruction is obtained by the user when adding the first object in the first system through the management interface; The operations related to the first object include: The first system creates the first object in the first system and generates the first attribute information of the first object in the first system.

26. The method according to claim 25, characterized in that, The first object exists in the second system, and the first object has a second attribute information in the second system. The method further includes: The first system obtains the second attribute information of the first object from the management interface, and the first system records the second attribute information of the first object; The first system informs the second system of the first attribute information of the first object through the management interface.

27. The method according to any one of claims 18 to 23, characterized in that, The instruction instructs to modify one attribute of the first object in the first system.

28. The method according to claim 27, characterized in that, The instruction is obtained by the user when modifying the first attribute information of the first object to the first value in the first system through the management interface; the instruction indicates that the first attribute information of the first object be modified to the first value. The operations related to the first object include: The first system modifies the first attribute information of the first object to the first value.

29. The method according to claim 27, characterized in that, The instruction is obtained when the second system has already modified the second attribute information of the first object to the second value in the second system. The second system records that the second attribute information is related to the first object in the first system. The instruction indicates that the second attribute information of the first object be modified to the second value. The operations related to the first object include: The first system modifies the second attribute information of the first object to the second value.

30. The method according to any one of claims 18 to 23, characterized in that, Also includes: The first system queries whether the third attribute information in the third system has been modified; The instruction is obtained when the third attribute information of the first object has been changed to a third value, and the instruction instructs to modify the third attribute information of the first object to the third value. The operations related to the first object include: The first system modifies the third attribute information of the first object to the third value.

31. The method according to claim 30, characterized in that, The query to determine whether the third attribute information in the third system has been modified is performed periodically.

32. The method according to any one of claims 18 to 23, characterized in that, The instruction is obtained when the first object is created in the fourth system and the fourth attribute information of the first object is generated in the fourth system, and the instruction instructs to record the fourth attribute information of the first object; The operations related to the first object include: The first system records the fourth attribute information of the first object.

33. The method according to any one of claims 18 to 32, characterized in that, The attribute information indicates one of the following: The identifier of the first object; Description information of the first object; or The address information of the first object.

34. The method according to any one of claims 18 to 33, characterized in that, The first system is one of the following: production system, supply chain system, sales system, or operation and maintenance system.

35. A management interface, characterized in that, include: The acquisition module is used to acquire a piece of information, wherein the piece of information indicates an operation related to a first object to be performed in the first system, at least one attribute information of the first object is recorded by at least one second object related to the first object, and each attribute information in the at least one attribute information is recorded as an attribute of the corresponding second object in the at least one second object; An instruction module is used to instruct the first system to perform the operation related to the first object in response to the acquisition of a piece of information.

36. The management interface according to claim 35, characterized in that, The at least one second object is associated with the first object through at least one third object, wherein each of the at least one third object indicates the relationship between the first object and a corresponding second object among the at least one second object, and there is a one-to-one correspondence between the first object and each of the at least one third object, and a one-to-one correspondence between each of the at least one third object and the corresponding second object among the at least one second object.

37. The management interface according to claim 36, characterized in that, Each of the at least one second object is deleted by deleting the corresponding third object in the at least one third object.

38. The management interface according to any one of claims 35 to 37, characterized in that, The management interface is used to provide a unified interface and management entry point for managing objects from at least one system.

39. The management interface according to any one of claims 35 to 38, characterized in that, The instruction module is also used to instruct the first system to perform the operation related to the first object through a pre-configured interface and a communication protocol based on the first system's application programming interface (API).

40. The management interface according to any one of claims 35 to 39, characterized in that, The operations associated with the first object include at least one of the following: Create the first object in the first system; Modify one attribute of the first object in the first system; or Record one attribute information of the first object in the first system.

41. The management interface according to any one of claims 35 to 40, characterized in that, The message indicates that the first object is created in the first system.

42. The management interface according to claim 41, characterized in that, The aforementioned piece of information is obtained when the user adds the first object in the first system through the management interface; The instruction module is also used to instruct the first system to create the first object in the first system and generate the first attribute information of the first object in the first system.

43. The management interface according to claim 42, characterized in that, The first object exists in the second system, and the first object has a second attribute information in the second system. The instruction module is further configured to instruct the first system to record the second attribute information of the first object; or The instruction module is also used to instruct the second system to record the first attribute information of the first object.

44. The management interface according to any one of claims 35 to 40, characterized in that, The message indicates that an attribute of the first object is modified in the first system.

45. The management interface according to claim 44, characterized in that, The information is obtained when the user modifies the first attribute information of the first object to the first value in the first system through the management interface. The information indicates that the first attribute information of the first object is modified to the first value. The instruction module is also used to instruct the first system to modify the first attribute information of the first object to the first value in the first system.

46. ​​The management interface according to claim 44, characterized in that, The aforementioned message is obtained by the management interface from the second system when the second system has modified the second attribute information of the first object to the second value in the second system. The second system records that the second attribute information is related to the first object in the first system, and the message indicates that the second attribute information of the first object has been modified to the second value. The instruction module is also used to instruct the first system to modify the second attribute information of the first object to the second value in the first system.

47. The management interface according to any one of claims 35 to 40, characterized in that, The acquisition module is further configured to acquire the third attribute information of the first object in the third system in response to a query to see if the third attribute information in the third system has been modified from the first system; The management interface also includes: The determination module is used to determine whether the third attribute information has been modified; In response to determining that the third attribute information of the first object has been changed to a third value, the indication module is further configured to instruct the first system to modify the third attribute information of the first object to the third value in the first system.

48. The management interface according to claim 47, characterized in that, The query to determine whether the third attribute information in the third system has been modified is performed periodically.

49. The management interface according to any one of claims 35 to 40, characterized in that, The information is obtained from the fourth system after the first object is created in the fourth system and the fourth attribute information of the first object is generated in the fourth system. The information includes the fourth attribute information of the first object. The instruction module is also used to instruct the first system to record the fourth attribute information of the first object.

50. The management interface according to any one of claims 35 to 49, characterized in that, The attribute information indicates one of the following: The identifier of the first object; Description information of the first object; or The address information of the first object.

51. The management interface according to any one of claims 35 to 50, characterized in that, The first system is one of the following: production system, supply chain system, sales system, or operation and maintenance system.

52. A first system, characterized in that, include: The acquisition module is used to obtain instructions from the management interface; An execution module is configured to perform operations related to the first object in response to the instructions; The instruction indicates the operation related to the first object to be performed in the first system, wherein at least one attribute information of the first object is recorded by at least one second object related to the first object, and each of the at least one attribute information is recorded as an attribute of the corresponding second object in the at least one second object.

53. The first system according to claim 52, characterized in that, The at least one second object is associated with the first object through at least one third object, wherein each of the at least one third object indicates the relationship between the first object and a corresponding second object among the at least one second object, and there is a one-to-one correspondence between the first object and each of the at least one third object, and a one-to-one correspondence between each of the at least one third object and the corresponding second object among the at least one second object.

54. The first system according to claim 53, characterized in that, Each of the at least one second object is deleted by deleting the corresponding third object in the at least one third object.

55. The first system according to any one of claims 52 to 54, characterized in that, The management interface is used to provide a unified interface and management entry point for managing objects from at least one system.

56. The first system according to any one of claims 52 to 55, characterized in that, The acquisition module is also used to acquire the instructions from the management interface through a pre-configured interface and a communication protocol based on the application programming interface (API) of the first system.

57. The first system according to any one of claims 52 to 56, characterized in that, The operations associated with the first object include at least one of the following: Create the first object in the first system; Modify one attribute of the first object in the first system; or Record one attribute information of the first object in the first system.

58. The first system according to any one of claims 52 to 57, characterized in that, The instruction instructs that the first object be created in the first system.

59. The first system according to claim 58, characterized in that, The instruction is obtained by the user when adding the first object in the first system through the management interface; The execution module is also used to create the first object in the first system and generate the first attribute information of the first object in the first system.

60. The first system according to claim 59, characterized in that, The first object exists in the second system, and the first object has a second attribute information in the second system; The acquisition module is also used to acquire the second attribute information of the first object from the management interface; The execution module is also used for: Record the second attribute information of the first object; The management interface is used to inform the second system of the first attribute information of the first object.

61. The first system according to any one of claims 52 to 57, characterized in that, The instruction instructs to modify one attribute of the first object in the first system.

62. The first system according to claim 61, characterized in that, The instruction is obtained by the user when modifying the first attribute information of the first object to the first value in the first system through the management interface; the instruction indicates that the first attribute information of the first object be modified to the first value. The execution module is also used to modify the first attribute information of the first object to the first value in the first system.

63. The first system according to claim 61, characterized in that, The instruction is obtained when the second system has already modified the second attribute information of the first object to the second value in the second system. The second system records that the second attribute information is related to the first object in the first system. The instruction indicates that the second attribute information of the first object be modified to the second value. The execution module is also used to modify the second attribute information of the first object to the second value in the first system.

64. The first system according to any one of claims 52 to 57, characterized in that, The execution module is also used to query whether the third attribute information in the third system has been modified; The instruction is obtained when the third attribute information of the first object has been changed to a third value, and the instruction instructs to modify the third attribute information of the first object to the third value. The execution module is also used to modify the third attribute information of the first object to the third value in the first system.

65. The first system according to claim 64, characterized in that, The query to determine whether the third attribute information in the third system has been modified is performed periodically.

66. The first system according to any one of claims 52 to 57, characterized in that, The instruction is obtained when the fourth system creates the first object and generates the fourth attribute information of the first object in the fourth system, and the instruction instructs to record the fourth attribute information of the first object; the execution module is also used to record the fourth attribute information of the first object.

67. The first system according to any one of claims 52 to 66, characterized in that, The attribute information indicates one of the following: The identifier of the first object; Description information of the first object; or The address information of the first object.

68. The first system according to any one of claims 52 to 67, characterized in that, The first system is one of the following: production system, supply chain system, sales system, or operation and maintenance system.

69. A management interface, characterized in that, include: A processing circuit for performing the method according to any one of claims 1 to 17.

70. A first system, characterized in that, include: A processing circuit for performing the method according to any one of claims 18 to 34.

71. An object management system, characterized in that, include: The management interface according to any one of claims 35 to 51 or the management interface according to claim 69; The first system according to any one of claims 52 to 68 or the first system according to claim 70; At least one fifth system, wherein the at least one fifth system is one of a production system, a supply chain system, a sales system, or an operation and maintenance system.

72. An object management system, characterized in that, include: A first processing circuit is configured to perform the method according to any one of claims 1 to 17; A second processing circuit is configured to perform the method according to any one of claims 18 to 34; At least one third processing circuit, wherein the at least one third processing circuit belongs to one of the production system, supply chain system, sales system or operation and maintenance system.

73. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions that, when executed by a processor, cause the processor to perform the first system according to any one of claims 1 to 34.

74. A computer program product, characterized in that, The computer program product includes computer execution instructions that, when executed by a processor, cause the processor to perform the first system according to any one of claims 1 to 34.

Images