Object management method, apparatus, and system

Abstract

Provided are object management communication method, apparatus, and system. A unified management interface obtains a piece of information indicating an operation related to a first object to be performed in a first system and instruct the first system to perform the operation. At least one piece of attribute information of the first object is recorded by at least one second object in relation to the first object. Therefore, unified management of multiple objects in different systems could be realized, and the attribute information of the first object could be separately recorded by the second object in relation to the first object, thereby facilitating the modification and synchronization of the attribute information of objects in different systems.

Description

OBJECT MANAGEMENT METHOD, APPARATUS, AND SYSTEMTECHNICAL FIELD

[0001] The present disclosure relates generally to the field of data management technologies and, in particular, to an object management communication method, apparatus, and system.BACKGROUND

[0002] Traditionally, data management systems, such as Product Data Management (PDM), Product Lifecycle Management (PLM), Simulation Process and Data Management (SPDM), Enterprise Resource Planning (ERP) etc. use identification which is assigned during creation of objects and this identification cannot be changed in the future. Additional identification is usually realized as an extended attribute which is defined by an information object. Any mistakes in identification with information objects require to recreate these objects.

[0003] More specifically, traditionally identification information for an object is the attribute of this object, and cannot be created or changed separately of the object. If there is a need to provide multi-identification for the same object, an additional identification attribute needs to be added for the object in the system.

[0004] During work on systems' lifecycle management systems there is a problem with identification of information objects, because the same information object usually has some different identification.]0005] This background information is provided to reveal information believed by the applicant to be of possible relevance to the present disclosure. No admission is necessarily intended, nor should be construed, that any of the preceding information constitutes prior art against the present disclosure.SUMMARY

[0006] In a first aspect, the present disclosure provides an object management method, including: obtaining, by a management interface, a piece of information, where the piece of information indicates an operation related to a first object to be performed in a first system, at least one piece of attribute information of the first object is recorded by at least one second object in relation to the first object, and each of the at least one piece of attribute information is recorded as an attribute of a respective second object in the at least one second object; instracting, by the management interface, the first system to perform the operation related to the first object in response to the obtaining of the piece of information.

[0007] Because a unified management interface could be used to instruct a first system to perform an operation related to the first object in response to obtaining information related to the operation, unified management of multiple objects in different systems could be realized. In addition, a second object is used for recording the attribute information of the first object, and thus, the attribute information of the first object could be separately recorded by the attribute of the second object in relation to the first object, instead of being recorded as an attribute of the first object itself. In this way, the creation or modification of the attribute information could be implemented by creating or modifying a corresponding second object, thereby facilitating the modification and synchronization of the attribute information (e.g. identification information) of the same object in different systems.

[0008] In a possible implementation of the first aspect, the at least one second object is in relation to the first object through at least one third object, where each of the at least one third object indicates a relation between thefirst object and a respective second object in the at least one second object, and where the first object is in one-to- one relationship with each of the at least one third object, and each of the at least one third object is in one-to-one relationship with the respective second object in the at least one second object.

[0009] Two types of objects, i.e., the second object and the third object, are used for recording the attribution information of the first object, where the second object records the attribution information of the first object, and the third object indicates a relation between the first object and the second object, and thus multiple pieces of attribute information of a same object in different systems could be recorded by multiple second objects and third objects. When the identification information of the first object is recorded in this way, the creation and identification of the first object could be split to two independent processes. In other words, the creation and the identification could be perform separately by creating a first object, which is the object intended to be created, and creating a second object for recording identification information and a third object indicating a relation between the first object and the second object. If another identification needs to be added for the first object, another second object and another third object could be added. Therefore, a possibility to add different identification for the same object could be provided.

[0010] In a possible implementation of the first aspect, each of the at least one second object is removed by removing a respective third object in the at least one third object.

[0011] Because the attribute information of the first object is recorded by the second object, the attribute information of the first object could be easily removed by removing a corresponding third object. When additional identification information of the first object is recorded by the second object, it could also be removed from the first object in this way, thereby facilitating the management of objects in multiple systems, and reducing some redundancy manual operations of users.

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

[0013] Because the unified management interface could provide a unified interface and a management entry for managing objects from at least one system, multiple objects of different systems could be managed easily and efficiently through the unified management interface, which could reduce some redundancy manual operations of users.[0014[ In a possible implementation of the first aspect, the instructing the first system to perform the operation related to the first object includes: instructing, by the management interface, the first system through a pre-configured interface and a communication protocol based on an application programming interface (API) of the first system to perform the operation related to the first object.

[0015] The management interface could instruct the first system to perform the operation through a pre- configured interface and communication protocol based on an API, which provides an implementation manner for the management interface to instruct the first system.

[0016] In a possible implementation of the first aspect, the operation related to the first object includes at least one of: creating the first object in the first system; modifying a piece of attribute information of the first object in the first system; or recording a piece of attribute information of the first object in the first system.

[0017] Because the unified management interface could be used to instruct the system to create an object, modify a piece of attribute information of the object and / or record a piece of attribute information of the object, the objects existing in the system could be managed in a unified manner and a new object could be created in an easy way.

[0018] In a possible implementation of the first aspect, the piece of information indicates creating the first object in the first system.

[0019] Because the unified management interface could be used to instruct the first system to create a new object, a new object and its corresponding attribute information could be created in a unified manner.

[0020] In a possible implementation of the first aspect, the piece of information is obtained when a user adds, through the management interface, the first object in the first system; and the instructing the first system to perform the operation related to the first object includes: instructing, by the management interface, the first system to create the first object in the first system and generate a first piece of attribute information of the first object in the first system.

[0021] Under the circumstance that a user wants to add a new object in the first system, the ne object could be created and new attribute information could be generated easily in the first system through the unified management interface without paying redundancy operation.

[0022] In a possible implementation of the first aspect, the first object exists in a second system, and the first object has a second piece of attribute information in the second system, and the method further includes at least one of: instructing, by the management interface, the first system to record the second piece of attribute information of the first object; or instructing, by the management interface, the second system to record the first piece of attribute information of the first object.

[0023] If a created object in the first system also exists in other systems, after the creation of the object with the attribute information in the first system, the management interface could 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 could know the attribute information of the first object in different systems, thereby realizing synchronization of the attribute information of the object in different systems.

[0024] In a possible implementation of the first aspect, the piece of information indicates modifying a piece of attribute information of the first object in the first system.

[0025] Because the unified management interface could be used to instruct the first system to modify the attribute information of the first object, an existing first attribute of the object in the system could be managed in a unified manner, facilitating unified management, especially modification, of the attribute information of the object in different system.

[0026] In a possible implementation of the first aspect, the piece of information is obtained when a user modifies, through the management interface, a first piece of attribute information of the first object to a first value in the first system, and the piece of information indicates modifying the first piece of attribute information of the first object to the first value; and the instructing the first system to perform the operation related to the first object includes: instructing, by the management interface, the first system to modify the first piece of attribute information of the first object to the first value in the first system.

[0027] Under the circumstance that a user wants to modify the first attribute information of the first object in the first system, the unified management interface provides a management entry for managing objects of different systems, the object could be managed in a unified manner, and the attribute information of the object in the first system could be easily modified through the unified management interface without paying redundancy operation.

[0028] In a possible implementation of the first aspect, the piece of information is obtained by the management interface from a second system when the second system has modified a second piece of attribute information of the first object to a second value in the second system, where the second system records that the second piece of attribute information is related to the first object in the first system, and the piece of information indicates modifying the second piece of attribute information of the first object to the second value; andthe instructing the first system to perform the operation related to the first object includes: instructing, by the management interface, the first system to modify the second piece of attribute information of the first object to the second value in the first system.

[0029] Under the circumstance that a second system has modified the second attribute information of the first object in the second system, and the second piece of attribute information of the first object in the second system is related to the first object in the first system, which means that the first system also records the second piece of attribute information of the first object, the unified management interface could act as an unified interface for managing the object in different systems, especially, the second system could notify, through the unified management interface, the first system of modifying the second piece of attribute information of the first object to the second value in the first system. Therefore, synchronization of the attribute information of the object in different systems could be realized in an easy and convenient manner.

[0030] In a possible implementation of the first aspect, the method further includes: obtaining, by the management interface, a third piece of attribute information of the first object in a third system in response to a query of whether the third piece of attribute information in the third system has been modified from the first system; determining, by the management interface, whether the third piece of attribute information has been modified; and in response to a determination that the third piece of attribute information of the first object has been changed to a third value, the instructing the first system to perform the operation related to the first object includes: instructing, by the management interface, the first system to modify in the first system the third piece of attribute information of the first object to the third value.

[0031] In a possible implementation of the first aspect, the query of whether the third piece of attribute information in the third system has been modified is conducted periodically.

[0032] The first system would actively query based on the management interface to determine whether a third system has modified the third piece of attribute information of the object in the third system. Under the circumstance that the third system has modified the third attribute of the object in the third system, the first system could modify the third attribute information of the object recorded in the first system. Therefore, the synchronization of the attribute information of the object in different systems can be realized in an easy and convenient manner. Moreover, the query could be conducted periodically, a period for synchronization could be set according to actual needs, which provides a synchronization manner, and more choices could be provided for different scenarios and conditions.

[0033] In a possible implementation of the first aspect, the piece of information is obtained from a fourth system after the fourth system creates the first object and generates a fourth piece of attribute information of the first object in the fourth system, and the piece of information includes the fourth piece of attribute information of the first object; the instructing the first system to perform the operation related to the first object includes: instructing, by the management interface, the first system to record the fourth piece of attribute information of the first object.

[0034] If an object newly created in the other systems also exists in the first system, after the creation of the object and generation of the attribute information in the fourth system, the management interface could instruct the first system to record the attribute information of the object from other systems so that the first system could know that the other systems also have the object and record the corresponding attribute information, thereby realizing synchronization of the attribute information of the object in different systems.

[0035] In a possible implementation of the first aspect, the attribute indicates one of: an identifier of the first object; description information of the first object; or address information of the first object.

[0036] The atribute information of the object could indicate various kinds of information, such as an identifier of the object, description information of the object, or address information of the object, and thus, different object information in different systems could be created, modified and synchronized through the management interface in an easy and convenient manner.]0037] In a 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.

[0038] The management interface could be used for managing different systems, such as a production system, a supply chain system, a sales system, or an operation and maintenance system, and thus, unified management of multiple objects in these systems could be realized.

[0039] In a second aspect, the present disclosure provides an object management method, including: obtaining, by a first system, an instruction from a management interface; and performing, by the first system, an operation related to a first object in response to the instruction; where the instruction indicates the operation related to the first object to be performed in the first system, at least one piece of attribute information of the first object is recorded by at least one second object in relation to the first object, and each of the at least one piece of atribute information is recorded as an atribute of a respective second object in the at least one second object.

[0040] An instruction could be obtained from a unified management interface, and then an operation could be performed in response to the instruction. In this way, unified management of multiple objects in different systems could be realized. In addition, the second object is used for recording the attribute information of the first object, and thus, the atribute information of the first object could be separately recorded by the attribute of the second object in relation to the first object, instead of being recorded as an attribute of the first object itself. In this way, the creation or modification of the atribute information could be implemented by creating or modifying a corresponding second object, thereby facilitating the modification and synchronization of the atribute information (e.g. identification information) of the same object in different systems.

[0041] In a possible implementation of the second aspect, the at least one second object is in relation to the first object through at least one third object, where each of the at least one third object indicates a relation between the first object and a respective second object in the at least one second object, and where the first object is in one-to- one relationship with each of the at least one third object, and each of the at least one third object is in one-to-one relationship with the respective second object in the at least one second object.

[0042] Two types of objects, i.e., the second object and the third object, are used for recording the atribution information of the first object, where the second object records the attribution information of the first object, and the third object indicates a relation between the first object and the second object, and thus multiple pieces of atribute information of a same object in different systems could be recorded by multiple second objects and third objects. When the identification information of the first object is recorded in this way, the creation and identification of the first object could be split to two independent processes. In other words, the creation and the identification could be perform separately by creating a first object, which is the object intended to be created, and creating a second object for recording identification information and a third object indicating a relation between the first object and the second object. If another identification needs to be added for the first object, another second object and another third object could be added. Therefore, a possibility to add different identification for the same object could be provided.

[0043] In a possible implementation of the second aspect, each of the at least one second object is removed by removing a respective third object in the at least one third object.

[0044] Because the attribute information of the first object is recorded by the second object, the attribute information of the first object could be easily removed by removing a corresponding third object. When additional identification information of the first object is recorded by the second object, it could also be removed from the first object in this way, thereby facilitating the management of objects in multiple systems, and reducing some redundancymanual operations of users.

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

[0046] Because the unified management interface could provide a unified interface and a management entry for managing objects from at least one system, multiple objects of different systems could be managed easily and efficiently through the unified management interface, which could reduce some redundancy manual operations of users.100471 In a possible implementation of the second aspect, the obtaining an instruction from a management interface includes: obtaining, by the first system, the instruction from the management interface through a pre-configured interface and a communication protocol based on an application programming interface (API) of the first system.

[0048] The first system could obtain the instruction from the management interface through a pre-configured interface and communication protocol based on an API, which provides an implementation manner for the first system to obtain the instruction.

[0049] In a possible implementation of the second aspect, the operation related to the first object includes at least one of: creating the first object in the first system; modifying a piece of attribute information of the first object in the first system; or recording a piece of attribute information of the first object in the first system.

[0050] Because the first system could be instructed by the unified management interface to create an object, modify a piece of attribute information of the object and / or record a piece of attribute information of the object, the objects existing in the system could be managed in a unified manner and a new object could be created in an easy way.

[0051] In a possible implementation of the second aspect, the instruction indicates creating the first object in the first system.

[0052] Because the first system could be instructed by the unified management interface to create a new object, a new object and its corresponding attribute information could be created in a unified manner.

[0053] In a possible implementation of the second aspect, the instruction is obtained in a case that a user adds, through the management interface, the first object in the first system; and the performing an operation related to a first object includes: creating, by the first system, the first object in the first system and generate a first piece of attribute information of the first object in the first system.

[0054] Under the circumstance that a user wants to add a new object in the first system, the new object could be created and new attribute information could be generated easily in the first system through the unified management interface without paying redundancy operation.

[0055] In a possible implementation of the second aspect, the first object exists in a second system, and the first object has a second piece of attribute information in the second system, and the method further includes: obtaining, by the first system, from the management interface, the second piece of attribute information of the first object, and recording, by the first system, the second piece of attribute information of the first object; or informing, by the first system, through the management interface, the second system of the first piece of attribute information of the first object.

[0056] If a created object in the first system also exists in other systems, after the creation of the object with the attribute information in the first system, the first system could obtain and record the attribute information of the object in the second system, and / or inform other systems of the generated attribute information of the first object so that the first system and / or other systems could know the attribute information of the first object in different systems,system has modified the third attribute information of the object in the third system. Under the circumstance that the third system has modified the third piece of attribute information of the object in the third system, the first system could modify the third attribute information of the object recorded in the first system. Therefore, the synchronization of the attribute information of the object in different systems can be realized in an easy and convenient manner. Moreover, the query could be conducted periodically, a period for synchronization could be set according to actual needs, which provides a synchronization manner, and more choices could be provided for different scenarios and conditions.

[0066] In a possible implementation of the second aspect, the instruction is obtained in a case that a fourth system creates the first object and generates a fourth piece of attribute information of the first object in the fourth system, and the instruction indicates recording the fourth piece of attribute information of the first object; and the performing an operation related to a first object includes: recording, by the first system, the fourth piece of attribute information of the first object.

[0067] If an object newly created in the other systems also exists in the first system, after the creation of the object and generation of the attribute information in the fourth system, the first system could be instructed by the management interface to record the attribute information of the object from other systems so that the first system could know that the other systems also have the object and record the corresponding attribute information, thereby realizing synchronization of the attribute information of the object in different systems.

[0068] In a possible implementation of the second aspect, the attribute information indicates one of: an identifier of the first object; description information of the first object; or address information of the first object.

[0069] The attribute information of the object could indicate various kinds of information, such as an identifier of the object, description information of the object, or address information of the object, and thus, different object information in different systems could be created, modified and synchronized through the management interface in an easy and convenient manner.

[0070] In a 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.

[0071] The first system could be various systems, such as a production system, a supply chain system, a sales system, or an operation and maintenance system, and thus, unified management of multiple objects in various systems could be realized.

[0072] In a third aspect, a possible implementation of the present disclosure provides a management interface , including various modules configured to execute the object management method according to the first aspect or any possible implementation of the first aspect.

[0073] In a fourth aspect, a possible implementation of the present disclosure provides a first system, including various modules configured to execute the object management method according to the second aspect or any possible implementation of the second aspect.

[0074] In a fifth aspect, a possible implementation of the present disclosure provides a management interface , including a processing circuitry for executing the object management method according to the first aspect or any possible implementation of the first aspect.

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

[0076] In a seventh aspect, a possible implementation of the present disclosure provides an object management system, including: 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 anypossible implementation of the fourth aspect or a first system according to the sixth aspect; and at least one fifth system, where 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.

[0077] In an eighth aspect, a possible implementation of the present disclosure provides an object management system, including: a first processing circuitry for executing the object management method according to the first aspect or any possible implementation of the first aspect; a second processing circuitry for executing the object management method according to the second aspect or any possible implementation of the second aspect; and at least one third processing circuitry, wherein the at least one third processing circuitry belongs to one of a production system, a supply chain system, a sales system, or an operation and maintenance system.

[0078] In a ninth aspect, a possible implementation of the present disclosure provides a computer -readable storage medium storing computer execution instructions which, when executed by a processor, cause the processor to execute the object management method according to the first aspect or any possible implementation of the first aspect or the second aspect or any possible implementation of the second aspect.

[0079] In a tenth aspect, a possible implementation of the present disclosure provides a computer program product including computer execution instructions which, when executed by a processor, cause the processor to execute the object management method according to the first aspect or any possible implementation of the first aspect or the second aspect or any possible implementation of the second aspect.

[0080] The present disclosure provides an object management communication method, apparatus, and system. After obtaining a piece of information indicating an operation related to a first object to be performed in a first system, the unified management interface could be used to instruct the system to perform the operation related to the object in response to the piece of information. At least one piece of attribute information of the first object is recorded by at least one second object in relation to the first object, and each of the at least one piece of attribute information is recorded as an attribute of a respective second object in the at least one second object. Therefore, unified management of multiple objects in different systems could be realized. In addition, a second object is used for recording the attribute information of the first object, and thus, the attribute information of the first object could be separately recorded by the attribute of the second object in relation to the first object, instead of being recorded as an attribute of the first object itself. In this way, the creation or modification of the attribute information could be implemented by creating or modifying a corresponding second object, thereby facilitating the modification and synchronization of the attribute information (e.g. identification information) of the same object in different systems.BRIEF DESCRIPTION OF DRAWINGS

[0081] Reference will now be made, by way of example, to the accompanying drawings which show example embodiments of the present disclosure, and in which:

[0082] FIG. 1 is a simplified schematic illustration of an item with identification.

[0083] FIG. 2 is a schematic illustration of an application scenario according to one or more example embodiments of the present disclosure.

[0084] FIG. 3 is a schematic illustration of an example representation of data object according to one or more example embodiments of the present disclosure.

[0085] FIG. 4 is a schematic illustration of another example representation of data object according to one or more example embodiments of the present disclosure.

[0086] FIG. 5 is a schematic illustration of creation and identification of information object according to one or more example embodiments of the present disclosure.

[0087] FIG. 6 is a schematic flowchart of an object management method according to one or more exampleembodiments of the present disclosure.

[0088] FIG. 7 is an interaction diagram of an object management method according to one or more example embodiments of the present disclosure.

[0089] FIG. 8 is another interaction diagram of an object management method according to one or more example embodiments of the present disclosure.

[0090] FIG. 9 is another interaction diagram of an object management method according to one or more example embodiments of the present disclosure.]0091] FIG. 10 is another schematic flowchart of an object management method according to one or more example embodiments of the present disclosure.

[0092] FIG. 11 is a schematic structural diagram of a management interface according to one or more example embodiments of the present disclosure.

[0093] FIG. 12 is a schematic structural diagram of a first system according to one or more example embodiments of the present disclosure.DESCRIPTION OF EMBODIMENTS

[0112] FIG. 5 is a schematic illustration of creation and identification of information object according to one or more example embodiments of the present disclosure.

[0113] As shown in FIG. 5, based on present data schema, the process of creation and identification of information object can be split to two independent processes: creation and identification, which can be perform by creator and identificator separately. Specifically, the creator could create the information object and the identification relation, and the identificator could create the object identifier, separately.

[0114] Based on this approach of information objects as a cortege it is possible to time splitting the processes of the creation and the identification of the information objects, and easily add additional identification (classification) or remove this for existing information objects.

[0115] If needed, any identification information can be removed based on removing relation object information.

[0116] In addition to recording and displaying the attribute information of object, the system can automatically communicate with other existing systems to implement collaborative data update.

[0117] FIG. 6 is a schematic flowchart of an object management method according to one or more example embodiments of the present disclosure. The method can be implemented by a management interface. As shown in FIG. 6, the method can include the following steps.

[0118] S610, a management interface obtains a piece of information, where the piece of information indicates an operation related to a first object to be performed in a first system, at least one piece of attribute information of the first object is recorded by at least one second object in relation to the first object, and each of the at least one piece of attribute information is recorded as an attribute of a respective second object in the at least one second object.

[0119] In details, the management interface may obtain a piece of information. Because a unified management interface could be used to instruct a first system to perform an operation related to the first object in response to obtaining information related to the operation, unified management of multiple objects in different systems could be realized. In addition, a second object is used for recording the atribute information of the first object, and thus, the attribute information of the first object could be separately recorded by the attribute of the second object in relation to the first object, instead of being recorded as an attribute of the first object itself. In this way, the creation or modification of the attribute information could be implemented by creating or modifying a corresponding second object, thereby facilitating the modification and synchronization of the attribute information (e.g. identification information) of the same object in different systems.

[0120] Further, the piece of information could be a request from a user or a system, which is not limited herein. Taking the request as an example, the request may indicates an operation related to a first object to be performed in a first system.

[0121] Moreover, at least one piece of attribute information of the first object may be recorded by at least one second object in relation to the first object, and each of the at least one piece of attribute information is recorded as an attribute of a respective second object in the at least one second object. Taking the attribute information is identification information as an example, as shown in FIG. 3, the identification information of the first object (e.g. Object in FIG. 3) could be recorded by the attribute (e.g. Identifier in FIG. 3) of the second object (e.g. Object Identifier in FIG. 3) with a specific value, such as XXX.

[0122] In a possible implementation, the at least one second object is in relation to the first object through at least one third object, where each of the at least one third object indicates a relation between the first object and a respective second object in the at least one second object, and where the first object is in one-to-one relationship with each of the at least one third object, and each of the at least one third object is in one-to-one relationship with the respective second object in the at least one second object. In other words, the first object, e.g. the Object, and the second object, e.g. the Object Identifier, could be in connection with each other by the relation between the first object and the second object, e.g. the Identification Relation as shown in FIG. 3. Based one this schema, the creation and identification of object could be split to two independent processes, and a possibility to add differentidentification for the same object could be provided.

[0123] For another example, an object A, which may be a car component, is identified as XXX in a production system A, identified as YYY in a supply chain system B and identified as ZZZ in a sales system C. Then, as shown in FIG. 4, Object A is the first object, and there are three second objects, labeled as Object Identifier System A, Object Identifier System B, Object Identifier System C, respectively, each of which has an attribute, Identifier. Each second object records the identification information of Object A in a corresponding system. Specifically, Object Identifier System A records the identification information XXX of Object A in the production system A, Object Identifier System B records the identification information YYY of Object A in the supply chain system B, and Object Identifier System C records the identification information ZZZ of Object A in the sales system C. There are three third objects labeled as Identification Relation A, Identification Relation B, and Identification Relation C and describing a one-to-one relation between Object A and Object Identifier System A, Object Identifier System B and Object Identifier System C, respectively. Based such schema, the Object A can have different identification information XXX, YYY, ZZZ in different systems A, B and C. If additional identification information, for example identification information WWW of Object A in an operation and maintenance system D is required to be added for Object A, a corresponding second object, e.g. Object Identifier System D, recording the identification information DDD of Object A in the system D and a third object describing the relation between Object A and this second object can be added. If a piece of identification information of Object A needs to be modified, the modification can be implemented by modifying the Identifier of a corresponding second object. Certainly, the above example is only for illustration, which is not limited herein.

[0124] As illustrated above, two types of objects, i.e., the second object and the third object, are used for recording the attribution information of the first object, where the second object records the attribution information of the first object, and the third object indicates a relation between the first object and the second object, and thus multiple pieces of atribute information of a same object in different systems could be recorded by multiple second objects and third objects. When the identification information of the first object is recorded in this way, the creation and identification of the first object could be split to two independent processes. In other words, the creation and the identification could be perform separately by creating a first object, which is the object intended to be created, and creating a second object for recording identification information and a third object indicating a relation between the first object and the second object. If another identification needs to be added for the first object, another second object and another third object could be added. Therefore, a possibility to add different identification for the same object could be provided.

[0125] In a possible implementation, a second object could be removed by removing a corresponding third object. Taking the object A as an example again, if the identification information YYY of Object A needs to be removed, it can be implemented by removing the relation object Identification Relation B. In this way, because the attribute information of the first object is recorded by the second object, the attribute information of the first object could be easily removed by removing a corresponding third object. When additional identification information of the first object is recorded by the second object, it could also be removed from the first object in this way, thereby facilitating the management of objects in multiple systems, and reducing some redundancy manual operations of users.

[0126] In a possible implementation, the management interface may be configured to provide a unified interface and a management entry for managing objects from at least one system. Because the unified management interface could provide a unified interface and a management entry for managing objects from at least one system, multiple objects of different systems could be managed easily and efficiently through the unified management interface, which could reduce some redundancy manual operations of users.

[0127] S620, the management interface instructs the first system to perform the operation related to the first object in response to the obtaining of the piece of information.

[0128] In details, taking the piece of information to be a request as an example, which is not limited herein. After obtaining the request from a user or a system, which indicates an operating to be performed in the first system, the management interface could instruct the first system to perform the operation. Because a unified management interface could be used to instruct a first system to perform an operation related to the first object in response to obtaining information related to the operation, unified management of multiple objects in different systems could be realized.

[0129] In a possible implementation, the management interface may instruct the first system through a preconfigured interface and a communication protocol based on an application programming interface (API) of the first system to perform the operation related to the first object, which provides an implementation manner for the management interface to instruct the first system. Certainly, other implementation manners could also be adopted, which is not limited herein.

[0130] In a possible implementation, the operation related to the first object includes at least one of: creating the first object in the first system; modifying a piece of attribute information of the first object in the first system; or recording a piece of attribute information of the first object in the first system. Certainly, the operation may also comprises other actions, which is not limited herein.

[0131] Next, the specific possible implementation of the operation would be described as follows in detail.

[0132] In a possible implementation, the piece of information may indicate creating the first object in the first system. In details, a new object and its corresponding attribute information could be created in a unified manner based on the unified management interface provided by the present disclosure.

[0133] In a possible implementation, the piece of information may be obtained when a user adds, through the management interface, the first object in the first system; and then the management interface may instruct the first system to create the first object in the first system and generate a first piece of attribute information of the first object in the first system.

[0134] In details, taking the object A as an example again, the user hopes adding the object A in the production system A, and then uses the management interface to add the object A. The management interface provided by the present disclosure could be used to add the object A in the production system A in a convenient and easy way. After receiving the creation request from the user, the management interface could instruct the production system A to create the object A in the production system A and generate Identifier XXX of the object A in the production system A. In other words, under the circumstance that the user wants to add a new object in the first system, the new object could be created and new attribute information could be generated easily in the first system through the unified management interface without paying redundancy operation.

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

[0136] For example, the object A may also exists in the supply chain system B with Identifier YYY. After the creation of the object A with Identifier XXX in the production system A, the identifier YYY of the object A in the production system B may also need to be recorded in the supply chain system A, and / or, the identifier XXX of the object A in the production system A may need to be recorded in the supply chain system B. In such situation, the management interface may instruct the production system A and / or the supply chain system B to record additional identification information of the object A. Therefore, the management interface provided by the present disclosure may instruct the production system A to record the Identifier YYY of the object A in the supply chain system B as additional identification information of the object A in the production system A, and / or, instruct the supply chain system B to record the Identifier XXX of the object A in the production system A as additional identificationinformation of the object A in the supply chain system B. In other words, If a created object in the first system also exists in other systems, after the creation of the object with the attribute information in the first system, the management interface could 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 could know the attribute information of the first object in different systems, thereby realizing synchronization of the attribute information of the object in different systems.

[0137] In a possible implementation, the piece of information obtained by the management interface may indicate modifying a piece of attribute information of the first object in the first system. In details, the attribute information of objects could be modified in a unified manner based on the unified management interface provided by the present disclosure.

[0138] In a possible implementation, the piece of information may be obtained when a user modifies, through the management interface, a first piece of attribute information of the first object to a first value in the first system, and the piece of information indicates modifying the first piece of attribute information of the first object to the first value; and the management interface may instruct the first system to modify the first piece of attribute information of the first object to the first value in the first system.

[0139] FIG. 7 is an interaction diagram of an object management method according to one or more example embodiments of the present disclosure. As shown in FIG. 7, taking modifying the identifier of the object A as an example, if a user wants to update the object Identifier XXX of the production system A, the user can change the object Identifier XXX of the production system A to BBB on the management interface provided by the present disclosure. In this case, the interface instructs production system A to change the object Identifier XXX to BBB through the pre-configured interface and communication protocol based on system’s API. When the production system A is updated successfully, a response is received, the first attribute information of the object A is updated, and the identifier of the object A in the production system A is updated to BBB. In other words, under the circumstance that a user wants to modify the first attribute information of the first object in the first system, the unified management interface provides a management entry for managing objects of different systems, the object could be managed in a unified manner, and the attribute information of the object in the first system could be easily modified through the unified management interface without paying redundancy operation. Through the management interface, a user may also update other types of attribute information, such as Name, Description, of objects in other systems, such the supply chain system B, the sales system C as mentioned above.

[0140] Ln a possible implementation, the first object may also exist in some other systems, and the first system may record the attribute information of the first object in other systems. When there is a change in the attribute information of other systems, the information recorded in the first system also needs to be updated for the synchronization of attribute information of objects in different systems. When the second system has modified a second piece of attribute information of the first object to a second value in the second system, and the second system records that the second piece of attribute information is related to the first object in the first system, the second system may send a piece of information to the management interface, which indicates modifying the second piece of attribute information of the first object to the second value. After receiving the piece of information from the second system, the management interface may instruct the first system to modify the second piece of attribute information of the first object to the second value in the first system.

[0141] FIG. 8 is another interaction diagram of an object management method according to one or more example embodiments of the present disclosure. As shown in FIG. 8, taking updating the identifier of the object A as an example again, if the supply chain system B updates the identifier of object A from YYY to CCC, and the supply chain system B records that YYY is related to object A in the production system A, the supply chain system B may notify, through the management interface, the production system A to update the second attribute of object A. (Update the second attribute of object A to CCC, to show that in supply chain system B the ID of object A has been changedto CCC.) The implementation of the update notification may need modification and adaptation of the supply chain system B to a certain extent. In other words, under the circumstance that a second system has modified the second attribute information of the first object in the second system, and the second piece of attribute information of the first object in the second system is related to the first object in the first system, which means that the first system also records the second piece of attribute information of the first object, the unified management interface could act as an unified interface for managing the object in different systems, especially, the second system could notify, through the unified management interface, the first system of modifying the second piece of attribute information of the first object to the second value in the first system. Therefore, synchronization of the attribute information of the object in different systems could be realized in an easy and convenient manner.

[0142] In a possible implementations, the synchronization of attribute information in different systems may be implemented based on query. The management interface may obtain a third piece of attribute information of the first object in a third system in response to a query of whether the third piece of attribute information in the third system has been modified from the first system, then the management interface may determine whether the third piece of attribute information has been modified, and in response to a determination that the third piece of attribute information of the first object has been changed to a third value, instruct the first system to modify in the first system the third piece of attribute information of the first object to the third value.

[0143] In a possible implementation, the determination of whether the third piece of attribute information has been changed could be conducted by the first system. For example, the first system may query through an open interface or through the management interface about the third piece of attribute information of the first object in the third system, and after obtaining the third piece of attribute information, the first system may determine whether the third piece of attribute information has been changed, and when the third piece of attribute information has been changed to a new value, the first system may update the recorded third piece of attribute information to the new value.

[0144] In a possible implementation, the query about the third piece of attribute information and the determination on whether the third piece of attribute information in the third system has been modified may be conducted periodically. The period for synchronization could be set according to actual needs, which could provide more choices for different scenarios and conditions.

[0145] In a possible implementation, the synchronization as shown in FIG. 8 can also be implemented in another manner. This manner does not require the modification and adaptation of the supply chain system B or other systems. The system A may periodically query through an open interface to determine that whether the object A’ ID (such as YYYY) is updated. If yes, the second attribute of object A is updated. In other words, the first system would actively query based on the open (management) interface to determine whether a third system has modified the third attribute information of the object in the third system. Under the circumstance that the third system has modified the third attribute of the object in the third system, the first system could modify the third attribute information of the object recorded in the first system. Therefore, the synchronization of the attribute information of the object in different systems can be realized in an easy and convenient manner. Moreover, the query could be conducted periodically, a period for synchronization could be set according to actual needs, which provides a synchronization manner, and more choices could be provided for different scenarios and conditions.

[0146] In a possible implementation, the first object may be newly created in another system, e.g., a fourth system, and attribute information, e.g. a fourth piece of attribute information may also be generated for the first object in that system. The management interface may obtain a piece of information from the fourth system after the fourth system creates the first object and generates the fourth piece of attribute information of the first object in the fourth system, where the piece of information includes the fourth piece of attribute information of the first object, and then, the management interface may instruct the first system to record the fourth piece of attribute information of the first object.

[0147] FIG. 9 is another interaction diagram of an object management method according to one or more example embodiments of the present disclosure. As shown in FIG. 9, taking the object A as an example again, if object A exists only in production system A, supply chain system B, and sales system C, and the user wants to add the object in O&M system D, the user can create object A in O&M system D through the management interface provided by the present disclosure. The O&M system D generates a new identifier WWW of the object A based on the creation rule of the system identifier, and returns the new identifier WWW of the object A to the management interface. Then, the management interface may inform the production system A of the identifier WWW of the object. In this case, the production system A records that the object A has four attributes. The first attribute is an identifier XXX of the object A in the production system A. The second attribute is an identifier YYYY of the object A in the supply chain system B, the third attribute is an identifier ZZZ of the object A in the sales system C, and the fourth attribute is an identifier WWW of the object A in the O&M system D. In addition, the management interface (Application Collaboration interface) can inform System B and C about a need to add new identifier from System D. In other words, If an object newly created in the other systems also exists in the first system, after the creation of the object and generation of the attribute information in the fourth system, the management interface could instruct the first system to record the attribute information of the object from other systems so that the first system could know that the other systems also have the object and record the corresponding attribute information, thereby realizing synchronization of the attribute information of the object in different systems.

[0148] In a possible implementation, the attribute information indicates one of: an identifier of the first object; description information of the first object; or address information of the first object.

[0149] In addition to identifier information modification and synchronization, the system can also implement other functions. For example, the user can record the other attribute information of object A. The production system A corresponding to object A may use Chinese. In this case, the payload of the text information sent to the production system A is sent in Chinese. (For example, modify the description of object A in production system A.). User can also configure the sales system corresponding to object A to use English language. Then, the updated description of object A will be sent in English. Through the management of multiple attributes of object A, the system can realize the creation, update and management of identification class and various non-identification class information (such as description information, address information, etc.). In other words, because the attribute information of the object could indicate various kinds of information, such as an identifier of the object, description information of the object, or address information of the object, and thus different object information in different systems could be created, modified and synchronized through the management interface in an easy and convenient manner.|0150] In a possible implementation, the first system is one of a production system, a supply chain system, a sales system, or an operation and maintenance system, which is not limited herein.|0151] In details, the management interface could be used for managing different systems, such as a production system, a supply chain system, a sales system, or an operation and maintenance system, and thus, unified management of multiple objects in these systems could be realized.

[0152] With the object management communication method provided by the present disclosure, after obtaining a piece of information indicating an operation related to a first object to be performed in a first system, the unified management interface could be used to instruct the system to perform the operation related to the object in response to the piece of information. At least one piece of attribute information of the first object is recorded by at least one second object in relation to the first object, and each of the at least one piece of attribute information is recorded as an attribute of a respective second object in the at least one second object. Therefore, unified management of multiple objects in different systems could be realized. In addition, a second object is used for recording the attribute information of the first object, and thus, the attribute information of the first object could be separately recorded by the attribute of the second object in relation to the first object, instead of being recorded as an attribute of the first object itself. In this way, the creation or modification of the attribute information could be implemented by creatingor modifying a corresponding second object, thereby facilitating the modification and synchronization of the attribute information (e.g. identification information) of the same object in different systems.

[0153] In the above, the object management communication method of the present disclosure is described from the perspective of the management interface in combination with FIG. 6 to FIG. 9. In the following, an object management communication method of the present disclosure will be described from the perspective of the first system in combination with FIG. 10.

[0154] FIG. 10 is another schematic flowchart of an object management method according to one or more example embodiments of the present disclosure. The method can be implemented by a first system. As shown in FIG.10, the method can include the following steps.

[0155] S 1010, a first system obtains an instruction from a management interface.

[0156] In details, a first system may obtain an instruction from a management interface. Because the first system could be instructed by the unified management interface to perform an operation related to the first object based on the instruction, unified management of multiple objects in different systems could be realized.

[0157] S 1020, the first system performs an operation related to a first object in response to the instruction; where the instruction indicates the operation related to the first object to be performed in the first system, at least one piece of attribute information of the first object is recorded by at least one second object in relation to the first object, and each of the at least one piece of attribute information is recorded as an attribute of a respective second object in the at least one second object.

[0158] In details, the first system could obtain an instruction from a unified management interface, and then an operation could be performed in response to the instruction. In this way, unified management of multiple objects in different systems could be realized. In addition, a second object is used for recording the attribute information of the first object, and thus, the attribute information of the first object could be separately recorded by the attribute of the second object in relation to the first object, instead of being recorded as an attribute of the first object itself. In this way, the creation or modification of the attribute information could be implemented by creating or modifying a corresponding second object, thereby facilitating the modification and synchronization of the attribute information (e.g. identification information) of the same object in different systems.

[0159] Further, at least one piece of attribute information of the first object may be recorded by at least one second object in relation to the first object, and each of the at least one piece of attribute information is recorded as an attribute of a respective second object in the at least one second object. Taking the attribute information is identification information as an example, as shown in FIG. 3, the identification information of the first object (e.g. Object in FIG. 3) could be recorded by the attribute (e.g. Identifier in FIG. 3) of the second object (e.g. Object Identifier in FIG. 3) with a specific value, such as XXX.

[0160] In a possible implementation, the at least one second object is in relation to the first object through at least one third object, where each of the at least one third object indicates a relation between the first object and a respective second object in the at least one second object, and where the first object is in one-to-one relationship with each of the at least one third object, and each of the at least one third object is in one-to-one relationship with the respective second object in the at least one second object. In other words, the first object, e.g. the Object, and the second object, e.g. the Object Identifier, could be in connection with each other by the relation between the first object and the second object, e.g. the Identification Relation as shown in FIG. 3. Based one this schema, the creation and identification of object could be split to two independent processes, and a possibility to add different identification for the same object could be provided.

[0161] For another example, an object A, which may be a car component, is identified as XXX in a production system A, identified as YYY in a supply chain system B and identified as ZZZ in a sales system C. Then, as shown in FIG. 4, Object A is the first object, and there are three second objects, labeled as Object Identifier System A, Object Identifier System B, Object Identifier System C, respectively, each of which has an attribute, Identifier. Eachsecond object records the identification information of Object A in a corresponding system. Specifically, Object Identifier System A records the identification information XXX of Object A in the production system A, Object Identifier System B records the identification information YYY of Object A in the supply chain system B, and Object Identifier System C records the identification information ZZZ of Object A in the sales system C. There are three third objects labeled as Identification Relation A, Identification Relation B, and Identification Relation C and describing a one-to-one relation between Object A and Object Identifier System A, Object Identifier System B and Object Identifier System C, respectively. Based such schema, the Object A can have different identification information XXX, YYY, ZZZ in different systems A, B and C. If additional identification information, for example identification information WWW of Object A in an operation and maintenance system D is required to be added for Object A, a corresponding second object, e.g. Object Identifier System D, recording the identification information DDD of Object A in the system D and a third object describing the relation between Object A and this second object can be added. If a piece of identification information of Object A needs to be modified, the modification can be implemented by modifying the Identifier of a corresponding second object. Certainly, the above example is only for illustration, which is not limited herein.

[0162] As illustrated above, two types of objects, i.e., the second object and the third object, are used for' recording the attribution information of the first object, where the second object records the attribution information of the first object, and the third object indicates a relation between the first object and the second object, and thus multiple pieces of attribute information of a same object in different systems could be recorded by multiple second objects and third objects. When the identification information of the first object is recorded in this way, the creation and identification of the first object could be split to two independent processes. In other words, the creation and the identification could be perform separately by creating a first object, which is the object intended to be created, and creating a second object for recording identification information and a third object indicating a relation between the first object and the second object. If another identification needs to be added for the first object, another second object and another third object could be added. Therefore, a possibility to add different identification for the same object could be provided.

[0163] In a possible implementation, a second object could be removed by removing a corresponding third object. Taking the object A as an example again, if the identification information YYY of Object A needs to be removed, it can be implemented by removing the relation object Identification Relation B. In this way, because the attribute information of the first object is recorded by the second object, the attribute information of the first object could be easily removed by removing a corresponding third object. When additional identification information of the first object is recorded by the second object, it could also be removed from the first object in this way, thereby facilitating the management of objects in multiple systems, and reducing some redundancy manual operations of users.

[0164] In a possible implementation, the management interface may be configured to provide a unified interface and a management entry for managing objects from at least one system. Because the unified management interface could provide a unified interface and a management entry for managing objects from at least one system, multiple objects of different systems could be managed easily and efficiently through the unified management interface, which could reduce some redundancy manual operations of users.

[0165] In a possible implementation, the first system may obtain the instruction from the management interface through a pre-configured interface and a communication protocol based on an application programming interface (API) of the first system, which provides an implementation manner for the first system to obtain the instruction. Certainly, other implementation manners could also be adopted, which is not limited herein.

[0166] In a possible implementation, the operation related to the first object includes at least one of: creating the first object in the first system; modifying a piece of attribute information of the first object in the first system; or recording a piece of attribute information of the first object in the first system. Certainly, the operation may alsocomprises other actions, which is not limited herein.

[0167] Next, the specific possible implementation of the operation would be described as follows in detail.

[0168] In a possible implementation, the instruction indicates creating the first object in the first system. In details, a new object and its corresponding attribute information could be created in a unified manner based on the unified management interface provided by the present disclosure.

[0169] In a possible implementation, the instruction may be obtained in a case that a user adds, through the management interface, the first object in the first system; and then the first system may create the first object in the first system and generate a first piece of attribute information of the first object in the first system.

[0170] In details, taking the object A as an example again, the user hopes adding the object A in the production system A, and then uses the management interface to add the object A. The management interface provided by the present disclosure could be used to add the object A in the production system A in a convenient and easy way. After receiving the creation request from the user, the production system A could be instructed by the management interface to create the object A in the production system A and generate Identifier XXX of the object A in the production system A. In other words, under the circumstance that the user wants to add a new object in the first system, the new object could be created and new attribute information could be generated easily in the first system through the unified management interface without paying redundancy operation.

[0171] In some cases, the first object also exists in some other systems, such a second system, and the first object may have other attribute information, such as a second piece of attribute information, in the second system. In a possible implementation, the first system may obtain, from the management interface, the second piece of attribute information of the first object, and record the second piece of attribute information of the first object; or inform, through the management interface, the second system of the first piece of attribute information of the first object.

[0172] For example, the object A may also exists in the supply chain system B with Identifier YYY. After the creation of the object A with Identifier XXX in the production system A, the identifier YYY of the object A in the production system B may also need to be recorded in the supply chain system A, and / or, the identifier XXX of the object A in the production system A may need to be recorded in the supply chain system B. In such situation, the production system A and / or the supply chain system B could be instructed by the management interface to record additional identification information of the object A. Therefore, the management interface provided by the present disclosure may instruct the production system A to record the Identifier YYY of the object A in the supply chain system B as additional identification information of the object A in the production system A, and / or, instruct the supply chain system B to record the Identifier XXX of the object A in the production system A as additional identification information of the object A in the supply chain system B. In other words, If a created object in the first system also exists in other systems, after the creation of the object with the attribute information in the first system, the management interface could 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 could know the attribute information of the first object in different systems, thereby realizing synchronization of the attribute information of the object in different systems.

[0173] In a possible implementation, the instruction indicates modifying a piece of attribute information of the first object in the first system. In details, the attribute information of objects could be modified in a unified manner based on the unified management interface provided by the present disclosure.

[0174] In a possible implementation, the instruction may be obtained in a case that a user modifies, through the management interface, a first piece of attribute information of the first object to a first value in the first system, and the instruction indicates modifying the first piece of attribute information of the first object to the first value; and then the first system may modify the first piece of attribute information of the first object to the first value in the first system. The example is shown in FIG. 7, which will not be discussed herein for brevity. In other words, under the circumstance that a user wants to modify the first attribute information of the first object in the first system, theunified management interface provides a management entry for managing objects of different systems, the object could be managed in a unified manner, and the attribute information of the object in the first system could be easily modified through the unified management interface without paying redundancy operation. Through the management interface, a user may also update other types of attribute information, such as Name, Description, of objects in other systems, such the supply chain system B, the sales system C as mentioned above.

[0175] In a possible implementation, the first object may also exist in some other systems, and the first system may record the attribute information of the first object in other systems. When there is a change in the attribute information of other systems, the information recorded in the first system also needs to be updated for the synchronization of attribute information of objects in different systems. When the first system obtains the instruction in a case that a second system has modified a second piece of attribute information of the first object to a second value in the second system, and the second system records that the second piece of attribute information is related to the first object in the first system, and the instruction indicates modifying the second piece of attribute information of the first object to the second value; the first system may modify the second piece of attribute information of the first object to the second value in the first system. The example is shown in FIG. 8, which will not be discussed herein for brevity. In other words, under the circumstance that a second system has modified the second attribute information of the first object in the second system, and the second piece of attribute information of the first object in the second system is related to the first object in the first system, which means that the first system also records the second piece of attribute information of the first object, the unified management interface could act as an unified interface for managing the object in different system, and the first system could be instructed by the management interface to modify the recorded second piece of attribute information of the first object to the second value in the first system. Therefore, synchronization of the attribute information of the object in different systems could be realized in an easy and convenient manner.

[0176] In a possible implementations, the synchronization of attribute information in different systems may be implemented based on query. The management interface may obtain a third piece of attribute information of the first object in a third system in response to a query of whether the third piece of attribute information in the third system has been modified from the first system, then the management interface may determine whether the third piece of attribute information has been modified, and in response to a determination that the third piece of attribute information of the first object has been changed to a third value, the first system could be instructed to modify in the first system the third piece of attribute information of the first object to the third value.[0177[ In a possible implementation, the determination of whether the third piece of attribute information has been changed could be conducted by the first system. For example, the first system may query through an open interface or through the management interface about the third piece of attribute information of the first object in the third system, and after obtaining the third piece of attribute information, the first system may determine whether the third piece of attribute information has been changed, and when the third piece of attribute information has been changed to a new value, the first system may update the recorded third piece of attribute information to the new value.

[0178] In a possible implementation, the query about the third piece of attribute information and the determination on whether the third piece of attribute information in the third system has been modified may be conducted periodically. The period for synchronization could be set according to actual needs, which could provide more choices for different scenarios and conditions. In other words, the first system would actively query based on the open (management) interface to determine whether a third system has modified the third attribute information of the object in the third system. Under the circumstance that the third system has modified the third attribute of the object in the third system, the first system could modify the third attribute information of the object recorded in the first system. Therefore, the synchronization of the attribute information of the object in different systems can be realized in an easy and convenient manner. Moreover, the query could be conducted periodically, a period forsynchronization could be set according to actual needs, which provides a synchronization manner, and more choices could be provided for different scenarios and conditions.

[0179] In a possible implementation, the first object may be newly created in another system, e.g., a fourth system, and attribute information, e.g. a fourth piece of attribute information may also be generated for the first object in that system. The first system may obtain the instruction in a case that a fourth system creates the first object and generates a fourth piece of attribute information of the first object in the fourth system, and the instruction indicates recording the fourth piece of attribute information of the first object; then the first system may record the fourth piece of attribute information of the first object. The example is shown in FIG. 9, which will not be discussed herein for brevity. In other words, If an object newly created in the other systems also exists in the first system, after the creation of the object and generation of the attribute information in the fourth system, the first system could be instructed by the management interface to record the attribute information of the object from other systems so that the first system could know that the other systems also have the object and record the corresponding attribute information, thereby realizing synchronization of the attribute information of the object in different systems.

[0180] In a possible implementation, the attribute information indicates one of: an identifier of the first object; description information of the first object; or address information of the first object.

[0181] In addition to identifier information modification and synchronization, the system can also implement other functions. For example, the user can record the other attribute information of object A. The production system A corresponding to object A may use Chinese. In this case, the payload of the text information sent to the production system A is sent in Chinese. (For example, modify the description of object A in production system A.). User can also configure the sales system corresponding to object A to use English language. Then, the updated description of object A will be sent in English. Through the management of multiple attributes of object A, the system can realize the creation, update and management of identification class and various non-identification class information (such as description information, address information, etc.). In other words, because the attribute information of the object could indicate various kinds of information, such as an identifier of the object, description information of the object, or address information of the object, and thus different object information in different systems could be created, modified and synchronized through the management interface in an easy and convenient manner.

[0182] In a possible implementation, the first system is one of a production system, a supply chain system, a sales system, or an operation and maintenance system, which is not limited herein.

[0183] In details, the management interface could be used for managing different systems, such as a production system, a supply chain system, a sales system, or an operation and maintenance system, and thus, unified management of multiple objects in these systems could be realized.

[0184] With the object management communication method provided by the present disclosure, after obtaining an instruction indicating an operation related to a first object to be performed in a first system, the first system could perform the operation related to the object. At least one piece of attribute information of the first object is recorded by at least one second object in relation to the first object, and each of the at least one piece of attribute information is recorded as an attribute of a respective second object in the at least one second object. Therefore, unified management of multiple objects in different systems could be realized. In addition, a second object is used for recording the attribute information of the first object, and thus, the attribute information of the first object could be separately recorded by the attribute of the second object in relation to the first object, instead of being recorded as an attribute of the first object itself. In this way, the creation or modification of the attribute information could be implemented by creating or modifying a corresponding second object, thereby facilitating the modification and synchronization of the attribute information (e.g. identification information) of the same object in different systems.

[0185] Next, examples of products related to the object management communication methods will be described.

[0186] FIG. 11 is a schematic structural diagram of a management interface according to one or more example embodiments of the present disclosure.

[0187] As shown in FIG. 11, a management interface 1100, including: an obtaining module 1110, configured to obtain a piece of information, where the piece of information indicates an operation related to a first object to be performed in a first system, at least one piece of attribute information of the first object is recorded by at least one second object in relation to the first object, and each of the at least one piece of attribute information is recorded as an attribute of a respective second object in the at least one second object; an instructing module 1120, configured to instruct the first system to perform the operation related to the first object in response to the obtaining of the piece of information.

[0188] In a possible implementation, the at least one second object is in relation to the first object through at least one third object, where each of the at least one third object indicates a relation between the first object and a respective second object in the at least one second object, and where the first object is in one-to-one relationship with each of the at least one third object, and each of the at least one third object is in one-to-one relationship with the respective second object in the at least one second object.

[0189] In a possible implementation, each of the at least one second object is removed by removing a respective third object in the at least one third object.

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

[0191] In a possible implementation, the instructing module 1120 is further configured to instruct the first system through a pre-configured interface and a communication protocol based on an application programming interface (API) of the first system to perform the operation related to the first object.

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

[0193] In a possible implementation, the piece of information indicates creating the first object in the first system.

[0194] In a possible implementation, the piece of information is obtained when a user adds, through the management interface, the first object in the first system; and the instructing module 1120 is further configured to instruct the first system to create the first object in the first system and generate a first piece of attribute information of the first object in the first system.

[0195] In a possible implementation, the first object exists in a second system, and the first object has a second piece of attribute information in the second system, and the instructing module 1120 is further configured to instruct the first system to record the second piece of attribute information of the first object; or the instructing module 1120 is further configured to instruct the second system to record the first piece of attribute information of the first object.

[0196] In a possible implementation, the piece of information indicates modifying a piece of attribute information of the first object in the first system.

[0197] In a possible implementation, the piece of information is obtained when a user modifies, through the management interface, a first piece of attribute information of the first object to a first value in the first system, and the piece of information indicates modifying the first piece of attribute information of the first object to the first value; and the instructing module 1120 is further configured to instruct the first system to modify the first piece of attribute information of the first object to the first value in the first system.

[0198] In a possible implementation, the piece of information is obtained by the management interface from a second system when the second system has modified a second piece of attribute information of the first object to a second value in the second system, where the second system records that the second piece of attribute information is related to the first object in the first system, and the piece of information indicates modifying the second piece of attribute information of the first object to the second value; and the instructing module 1120 is further configured to instruct the first system to modify the second piece of attribute information of the first object to the second value in the first system.

[0199] In a possible implementation, the obtaining module 1110 is further configured to obtain a third piece of attribute information of the first object in a third system in response to a query of whether the third piece of attribute information in the third system has been modified from the first system; where the management interface further includes: a determining module 1130, configured to determine whether the third piece of attribute information has been modified; and in response to a determination that the third piece of attribute information of the first object has been changed to a third value, the instructing module 1120 is further configured to instruct the first system to modify in the first system the third piece of attribute information of the first object to the third value.

[0200] In a possible implementation, the query of whether the third piece of attribute information in the third system has been modified is conducted periodically.

[0201] In a possible implementation, the piece of information is obtained from a fourth system after the fourth system creates the first object and generates a fourth piece of attribute information of the first object in the fourth system, and the piece of information includes the fourth piece of attribute information of the first object; and the instructing module 1120 is further configured to instruct the first system to record the fourth piece of attribute information of the first object

[0202] In a possible implementation, the attribute information indicates one of: an identifier of the first object; description information of the first object; or address information of the first object.

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

[0204] The management interface may perform the steps of the object management method of the management interface as described in the above possible method implementations. It should be understood by a person skilled in the art that, the relevant description of the above modules in these possible implementations of the present disclosure may be understood with reference to the relevant description of the object management method in these possible implementations of the present disclosure. The technical effect achieved by the above management interface is similar as that achieved by the above possible method implementation, which is not repeated herein.

[0205] FIG. 12 is a schematic structural diagram of a first system according to one or more example embodiments of the present disclosure.

[0206] As shown in FIG. 12, a first system 1200, including: an obtaining module 1210, configured to obtain an instruction from a management interface; and a performing module 1220, configured to perform an operation related to a first object in response to the instruction; where the instruction indicates the operation related to the first object to be performed in the first system, at least one piece of attribute information of the first object is recorded by at least one second object in relation to the first object, and each of the at least one piece of attribute information is recorded as an attribute of a respective second object in the at least one second object.

[0207] In a possible implementation, the at least one second object is in relation to the first object through at least one third object, where each of the at least one third object indicates a relation between the first object and a respective second object in the at least one second object, and where the first object is in one-to-one relationship with each of the at least one third object, and each of the at least one third object is in one-to-one relationship with the respective second object in the at least one second object.

[0208] In a possible implementation, each of the at least one second object is removed by removing a respective third object in the at least one third object.

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

[0210] In a possible implementation, the obtaining module 1210 is further configured to obtain the instruction from the management interface through a pre-configured interface and a communication protocol based on an application programming interface (API) of the first system.

[0211] In a possible implementation, the operation related to the first object includes at least one of: creatingthe first object in the first system; modifying a piece of attribute information of the first object in the first system; or recording a piece of attribute information of the first object in the first system.

[0212] In a possible implementation, the instruction indicates creating the first object in the first system.

[0213] In a possible implementation, the instruction is obtained when a user adds, through the management interface, the first object in the first system; and the performing module 1220 is further configured to create the first object in the first system and generate a first piece of attribute information of the first object in the first system.

[0214] In a possible implementation, the first object exists in a second system, and the first object has a second piece of attribute information in the second system; where the obtaining module 1210 is further configured to obtain, from the management interface, the second piece of attribute information of the first object; and the performing module 1220 is further configured to: record the second piece of attribute information of the first object; and inform, through the management interface, the second system of the first piece of attribute information of the first object.

[0215] In a possible implementation, the instruction indicates modifying a piece of attribute information of the first object in the first system.

[0216] In a possible implementation, the instruction is obtained when a user modifies, through the management interface, a first piece of attribute information of the first object to a first value in the first system, and the instruction indicates modifying the first piece of attribute information of the first object to the first value; and the performing module 1220 is further configured to modify the first piece of attribute information of the first object to the first value in the first system.

[0217] In a possible implementation, the instruction is obtained in a case that a second system has modified a second piece of attribute information of the first object to a second value in the second system, the second system records that the second piece of attribute information is related to the first object in the first system, and the instruction indicates modifying the second piece of attribute information of the first object to the second value; and the performing module 1220 is further configured to modify the second piece of atribute information of the first object to the second value in the first system.

[0218] In a possible implementation, the performing module 1220 is further configured to ask whether a third piece of attribute information in a third system has been modified; where the instruction is obtained in a case that the third piece of attribute information of the first object has been changed to a third value, and the instruction indicates modifying the third piece of attribute information of the first object to the third value; and the performing module 1220 is further configured to modify in the first system the third piece of attribute information of the first object to the third value.

[0219] In a possible implementation, the query of whether the third piece of attribute information in the third system has been modified is conducted periodically.

[0220] In a possible implementation, the instruction is obtained in a case that a fourth system creates the first object and generates a fourth piece of attribute information of the first object in the fourth system, and the instruction indicates recording the fourth piece of attribute information of the first object; and the performing module 1220 is further configured to record the fourth piece of attribute information of the first object.

[0221] In a possible implementation, the attribute information indicates one of: an identifier of the first object; description information of the first object; or address information of the first object.

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

[0223] The first system may perform the steps of the object management method of the first system as described in the above possible method implementations. It should be understood by a person skilled in the art that, the relevant description of the above modules in these possible implementations of the present disclosure may be understood with reference to the relevant description of the object management method in these possible implementations of the present disclosure. The technical effect achieved by the above first system is similar as that achieved by the abovepossible method implementations, which is not repeated herein.

[0224] A possible implementation of the present disclosure provides a management interface, including: a processing circuitry for executing any of the above corresponding object management methods at the management interface side, which is not repeated herein.

[0225] A possible implementation of the present disclosure provides a management interface, including: a processing circuitry for executing any of the above corresponding object management methods at the first system side, which is not repeated herein.

[0226] A possible implementation of the present disclosure provides an object management system, including: a management interface for executing any of the above corresponding object management method at the management interface side; a first system for executing any of the above corresponding object management method at the first system side; and at least one fifth system, where 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 above method is not repeated herein.

[0227] A possible implementation of the present disclosure provides an object management system, including: a first processing circuitry for executing any of the above corresponding object management method at the management interface side; a second processing circuitry for executing any of the above corresponding object management method at the first system side; and at least one third processing circuitry, where the at least one third processing circuitry belongs to one of a production system, a supply chain system, a sales system, or an operation and maintenance system .[022S] A possible implementation of the present disclosure provides a computer-readable storage medium storing computer execution instructions which, when executed by a processor, cause the processor to execute any of the above sensing communication methods, which is not repeated herein.

[0229] A possible implementation of the present disclosure provides a computer program product including computer execution instructions which, when executed by a processor, cause the processor to execute any of the above sensing communication methods, which is not repeated herein.

[0230] Main Innovative Points of the Present Invention1. A new unified management interface is provided to manage objects of users in different systems.2. The system provides a new set of working methods and processes to create objects, modify information (such as ID modification), and synchronize information for multiple systems.

[0231] Corresponding Advantageous Effects1. The interface includes such as display, creation, and modification etc. Through these interfaces we can provide object information management functions2. Through the new interface and new method provided by this solution, users can manage identification of objects in different systems.

[0232] Example concepts of some termsPLM: Product Lifecycle Management;PDM: Product Data Management;ERP: Enterprise Resource PlanningSPDM: Simulation Process and Data ManagementO&M: Operation and MaintenanceData model: an abstract model that organizes elements of data and standardizes how they relate to one another and to the properties of real-world entities. For instance, a data model may specify that the data element representing a car be composed of a number of other elements which, in turn, represent the color and size of the car and define its owner. Moreover, there are different data objects for storing object metadata and identification information in data model in data management system.

[0233] Please note that the different embodiments may be implemented separately or combined. Although acombination of features is shown in the illustrated embodiments, not all of them need to be combined to realize the benefits of various embodiments of this disclosure. In other words, a system or method designed according to an embodiment of this disclosure will not necessarily include all of the features shown in any one of the Figures or all of the portions schematically shown in the Figures. Moreover, selected features of one example embodiment may be combined with selected features of other example embodiments.

[0234] Although this disclosure has been described with reference to illustrative embodiments, this description is not intended to be construed in a limiting sense. Various modifications and combinations of the illustrative embodiments, as well as other embodiments of the disclosure, will be apparent to persons skilled in the art upon reference to the description. It is therefore intended that the appended claims encompass any such modifications or embodiments.

[0235] Although the present disclosure describes methods and processes with steps in a certain order, one or more steps of the methods and processes may be omitted or altered as appropriate. One or more steps may take place in an order other than that in which they are described, as appropriate.

[0236] Note that the expression “at least one of A or B”, as used herein, is interchangeable with the expression “A and / or B”. It refers to a list in which you may select A or B or both A and B. Similarly, “at least one of A, B, or C”, as used herein, is interchangeable with “A and / or B and / or C” or “A, B, and / or C”. It refers to a list in which you may select: A or B or C, or both A and B, or both A and C, or both B and C, or all of A, B and C. The same principle applies for longer lists having a same format.

[0237] Although the present disclosure is described, at least in part, in terms of methods, a person of ordinary skill in the art will understand that the present disclosure is also directed to the various components for performing at least some of the aspects and features of the described methods, be it by way of hardware components, software or any combination of the two. Accordingly, the technical solution of the present disclosure may be embodied in the form of a software product. A suitable software product may be stored in a pre-recorded storage device or other similar non-volatile or non-transitory computer readable storage medium, including DVDs, CD-ROMs, USB flash disk, a removable hard disk, or other storage media, for example. The software product includes instructions tangibly stored thereon that enable a processing device (e.g., a personal computer, a server, or a network device) to execute examples of the methods disclosed herein. The machine-executable instructions may be in the form of code sequences, configuration information, or other data, which, when executed, cause a machine (e.g., a processor or other processing device) to perform steps in a method according to examples of the present disclosure.

[0238] All values and sub-ranges within disclosed ranges are also disclosed. Also, although the systems, devices and processes disclosed and shown herein may include a specific number of elements / components, the systems, devices and assemblies could be modified to include additional or fewer of such elements / components. For example, although any of the elements / components disclosed may be referenced as being singular, the possible implementations disclosed herein could be modified to include a plurality of such elements / components. The subject matter described herein intends to cover and embrace all suitable changes in technology.

Claims

CLAIMS1. An object management method, comprising: obtaining, by a management interface, a piece of information, wherein the piece of information indicates an operation related to a first object to be performed in a first system, at least one piece of attribute information of the first object is recorded by at least one second object in relation to the first object, and each of the at least one piece of attribute information is recorded as an attribute of a respective second object in the at least one second object; instructing, by the management interface, the first system to perform the operation related to the first object in response to the obtaining of the piece of information.

2. The method according to claim 1, wherein the at least one second object is in relation to the first object through at least one third object, wherein each of the at least one third object indicates a relation between the first object and a respective second object in the at least one second object, and wherein the first object is in one-to-one relationship with each of the at least one third object, and each of the at least one third object is in one-to-one relationship with the respective second object in the at least one second object.

3. The method according to claim 2, wherein each of the at least one second object is removed by removing a respective third object in the at least one third object.

4. The method according to any one of claims 1 to 3, wherein the management interface is configured to provide a unified interface and a management entry for managing objects from at least one system.

5. The method according to any one of claims 1 to 4, wherein the instructing the first system to perform the operation related to the first object comprises: instructing, by the management interface, the first system through a pre-configured interface and a communication protocol based on an application programming interface (API) of the first system to perform the operation related to the first object.

6. The method according to any one of claims 1 to 5, wherein the operation related to the first object comprises at least one of: creating the first object in the first system; modifying a piece of attribute information of the first object in the first system; or recording a piece of attribute information of the first object in the first system.

7. The method according to any one of claims 1 to 6, wherein the piece of information indicates creating the first object in the first system.

8. The method according to claim 7, wherein the piece of information is obtained when a user adds, through the management interface, the first object in the first system; and the instructing the first system to perform the operation related to the first object comprises: instructing, by the management interface, the first system to create the first object in the first system and generate a first piece of attribute information of the first object in the first system.

9. The method according to claim 8, wherein the first object exists in a second system, and the first object has a second piece of attribute information in the second system, and the method further comprises at least one of: instructing, by the management interface, the first system to record the second piece of attribute information of the first object; or instructing, by the management interface, the second system to record the first piece of attribute information of the first object.

10. The method according to any one of claims 1 to 6, wherein the piece of information indicates modifying a piece of attribute information of the first object in the first system.

11. The method according to claim 10, wherein the piece of information is obtained when a user modifies, through the management interface, a first piece of attribute information of the first object to a first value in the firstsystem, and the piece of information indicates modifying the first piece of attribute information of the first object to the first value; and the instructing the first system to perform the operation related to the first object comprises: instructing, by the management interface, the first system to modify the first piece of attribute information of the first object to the first value in the first system.

12. The method according to claim 10, wherein the piece of information is obtained by the management interface from a second system when the second system has modified a second piece of attribute information of the first object to a second value in the second system, wherein the second system records that the second piece of attribute information is related to the first object in the first system, and the piece of information indicates modifying the second piece of attribute information of the first object to the second value; and the instructing the first system to perform the operation related to the first object comprises: instructing, by the management interface, the first system to modify the second piece of attribute information of the first object to the second value in the first system.

13. The method according to any one of claims 1 to 6, further comprising: obtaining, by the management interface, a third piece of attribute information of the first object in a third system in response to a query of whether the third piece of attribute information in the third system has been modified from the first system; determining, by the management interface, whether the third piece of attribute information has been modified; and in response to a determination that the third piece of attribute information of the first object has been changed to a third value, the instructing the first system to perform the operation related to the first object comprises: instructing, by the management interface, the first system to modify in the first system the third piece of attribute information of the first object to the third value.

14. The method according to claim 13, wherein the query of whether the third piece of attribute information in the third system has been modified is conducted periodically.

15. The method according to any one of claims 1 to 6, wherein the piece of information is obtained from a fourth system after the fourth system creates the first object and generates a fourth piece of attribute information of the first object in the fourth system, and the piece of information comprises the fourth piece of attribute information of the first object; the instructing the first system to perform the operation related to the first object comprises: instructing, by the management interface, the first system to record the fourth piece of attribute information of the first object.

16. The method according to any one of claims 1 to 15, wherein the attribute information indicates one of: an identifier of the first object; description information of the first object; or address information of the first object.

17. The method according to any one of claims 1 to 16, wherein the first system is one of a production system, a supply chain system, a sales system, or an operation and maintenance system.

18. An object management method, comprising: obtaining, by a first system, an instruction from a management interface; and performing, by the first system, an operation related to a first object in response to the instruction; wherein the instruction indicates the operation related to the first object to be performed in the first system, at least one piece of attribute information of the first object is recorded by at least one second object in relation to the first object, and each of the at least one piece of attribute information is recorded as an attribute of a respective second object in the at least one second object.

19. The method according to claim 18, wherein the at least one second object is in relation to the first object through at least one third object, wherein each of the at least one third object indicates a relation between the first object and a respective second object in the at least one second object, and wherein the first object is in one-to-one relationship with each of the at least one third object, and each of the at least one third object is in one-to-one relationship with the respective second object in the at least one second object.

20. The method according to claim 19, wherein each of the at least one second object is removed by removing a respective third object in the at least one third object.

21. The method according to any one of claims 18 to 20, wherein the management interface is configured to provide a unified interface and a management entry for managing objects from at least one system.

22. The method according to any one of claims 18 to 21, wherein the obtaining an instruction from a management interface comprises: obtaining, by the first system, the instruction from the management interface through a pre-configured interface and a communication protocol based on an application programming interface (API) of the first system.

23. The method according to any one of claims 18 to 22, wherein the operation related to the first object comprises at least one of: creating the first object in the first system; modifying a piece of attribute information of the first object in the first system; or recording a piece of attribute information of the first object in the first system.

24. The method according to any one of claims 18 to 23, wherein the instruction indicates creating the first object in the first system.

25. The method according to claim 24, wherein the instruction is obtained when a user adds, through the management interface, the first object in the first system; and the performing an operation related to a first object comprises: creating, by the first system, the first object in the first system and generate a first piece of attribute information of the first object in the first system.

26. The method according to claim 25, wherein the first object exists in a second system, and the first object has a second piece of attribute information in the second system, and the method further comprises: obtaining, by the first system, from the management interface, the second piece of attribute information of the first object, and recording, by the first system, the second piece of attribute information of the first object; informing, by the first system, through the management interface, the second system of the first piece of attribute information of the first object.

27. The method according to any one of claims 18 to 23, wherein the instruction indicates modifying a piece of attribute information of the first object in the first system.

28. The method according to claim 27, wherein the instruction is obtained when a user modifies, through the management interface, a first piece of attribute information of the first object to a first value in the first system, and the instruction indicates modifying the first piece of attribute information of the first object to the first value; and the performing an operation related to a first object comprises: modifying, by the first system, the first piece of attribute information of the first object to the first value in the first system.

29. The method according to claim 27, wherein the instruction is obtained in a case that a second system has modified a second piece of attribute information of the first object to a second value in the second system, the second system records that the second piece of attribute information is related to the first object in the first system, and the instruction indicates modifying the second piece of attribute information of the first object to the second value; and the performing an operation related to a first object comprises: modifying, by the first system, the second piece of attribute information of the first object to the second valuein the first system.

30. The method according to any one of claims 18 to 23, further comprising: querying, by the first system, whether a third piece of attribute information in a third system has been modified; wherein the instruction is obtained in a case that the third piece of attribute information of the first object has been changed to a third value, and the instruction indicates modifying the third piece of attribute information of the first object to the third value; and the performing an operation related to a first object comprises: modifying, by the first system, in the first system the third piece of attribute information of the first object to the third value.

31. The method according to claim 30, wherein the query of whether the third piece of attribute information in the third system has been modified is conducted periodically.

32. The method according to any one of claims 18 to 23, wherein the instruction is obtained in a case that a fourth system creates the first object and generates a fourth piece of attribute information of the first object in the fourth system, and the instruction indicates recording the fourth piece of attribute information of the first object; and the performing an operation related to a first object comprises: recording, by the first system, the fourth piece of attribute information of the first object.

33. The method according to any one of claims 18 to 32, wherein the attribute information indicates one of: an identifier of the first object; description information of the first object; or address information of the first object.

34. The method according to any one of claims 18 to 33, wherein the first system is one of a production system, a supply chain system, a sales system, or an operation and maintenance system.

35. A management interface, comprising: an obtaining module, configured to obtain a piece of information, wherein the piece of information indicates an operation related to a first object to be performed in a first system, at least one piece of attribute information of the first object is recorded by at least one second object in relation to the first object, and each of the at least one piece of attribute information is recorded as an attribute of a respective second object in the at least one second object; an instructing module, configured to instruct the first system to perform the operation related to the first object in response to the obtaining of the piece of information.

36. The management interface according to claim 35, wherein the at least one second object is in relation to the first object through at least one third object, wherein each of the at least one third object indicates a relation between the first object and a respective second object in the at least one second object, and wherein the first object is in one- to-one relationship with each of the at least one third object, and each of the at least one third object is in one-to-one relationship with the respective second object in the at least one second object.

37. The management interface according to claim 36, wherein each of the at least one second object is removed by removing a respective third object in the at least one third object.

38. The management interface according to any one of claims 35 to 37, wherein the management interface is configured to provide a unified interface and a management entry for managing objects from at least one system.

39. The management interface according to any one of claims 35 to 38, wherein the instructing module is further configured to instruct the first system through a pre -configured interface and a communication protocol based on an application programming interface (API) of the first system to perform the operation related to the first object.

40. The management interface according to any one of claims 35 to 39, wherein the operation related to the first object comprises at least one of: creating the first object in the first system; modifying a piece of attribute information of the first object in the first system; orrecording a piece of attribute information of the first object in the first system.

41. The management interface according to any one of claims 35 to 40, wherein the piece of information indicates creating the first object in the first system.

42. The management interface according to claim 41, wherein the piece of information is obtained when a user adds, through the management interface, the first object in the first system; and the instructing module is further configured to instruct the first system to create the first object in the first system and generate a first piece of attribute information of the first object in the first system.

43. The management interface according to claim 42, wherein the first object exists in a second system, and the first object has a second piece of attribute information in the second system, and the instructing module is further configured to instruct the first system to record the second piece of attribute information of the first object; or the instructing module is further configured to instruct the second system to record the first piece of attribute information of the first object.

44. The management interface according to any one of claims 35 to 40, wherein the piece of information indicates modifying a piece of attribute information of the first object in the first system.

45. The management interface according to claim 44, wherein the piece of information is obtained when a user modifies, through the management interface, a first piece of attribute information of the first object to a first value in the first system, and the piece of information indicates modifying the first piece of attribute information of the first object to the first value; and the instructing module is further configured to instruct the first system to modify the first piece of attribute information of the first object to the first value in the first system.

46. The management interface according to claim 44, wherein the piece of information is obtained by the management interface from a second system when the second system has modified a second piece of attribute information of the first object to a second value in the second system, wherein the second system records that the second piece of attribute information is related to the first object in the first system, and the piece of information indicates modifying the second piece of attribute information of the first object to the second value; and the instructing module is further configured to instruct the first system to modify the second piece of 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, wherein the obtaining module is further configured to obtain a third piece of attribute information of the first object in a third system in response to a query of whether the third piece of attribute information in the third system has been modified from the first system; where the management interface further comprises: a determining module, configured to determine whether the third piece of attribute information has been modified; and in response to a determination that the third piece of attribute information of the first object has been changed to a third value, the instructing module is further configured to instruct the first system to modify in the first system the third piece of attribute information of the first object to the third value.

48. The management interface according to claim 47, wherein the query of whether the third piece of attribute information in the third system has been modified is conducted periodically.

49. The management interface according to any one of claims 35 to 40, wherein the piece of information is obtained from a fourth system after the fourth system creates the first object and generates a fourth piece of attribute information of the first object in the fourth system, and the piece of information comprises the fourth piece of attribute information of the first object; and the instructing module is further configured to instruct the first system to record the fourth piece of attribute information of the first object.

50. The management interface according to any one of claims 35 to 49, wherein the attribute information indicates one of: an identifier of the first object; description information of the first object; or address information of the first object.

51. The management interface according to any one of claims 35 to 50, wherein the first system is one of a production system, a supply chain system, a sales system, or an operation and maintenance system.

52. A first system, comprising: an obtaining module, configured to obtain an instruction from a management interface; and a performing module, configured to perform an operation related to a first object in response to the instruction; wherein the instruction indicates the operation related to the first object to be performed in the first system, at least one piece of attribute information of the first object is recorded by at least one second object in relation to the first object, and each of the at least one piece of attribute information is recorded as an attribute of a respective second object in the at least one second object.

53. The first system according to claim 52, wherein the at least one second object is in relation to the first object through at least one third object, wherein each of the at least one third object indicates a relation between the first object and a respective second object in the at least one second object, and wherein the first object is in one-to-one relationship with each of the at least one third object, and each of the at least one third object is in one-to-one relationship with the respective second object in the at least one second object.

54. The first system according to claim 53, wherein each of the at least one second object is removed by removing a respective third object in the at least one third object.

55. The first system according to any one of claims 52 to 54, wherein the management interface is configured to provide a unified interface and a management entry for managing objects from at least one system.

56. The first system according to any one of claims 52 to 55, wherein the obtaining module is further configured to obtain the instruction from the management interface through a pre-configured interface and a communication protocol based on an application programming interface (API) of the first system.

57. The first system according to any one of claims 52 to 56, wherein the operation related to the first object comprises at least one of: creating the first object in the first system; modifying a piece of attribute information of the first object in the first system; or recording a piece of attribute information of the first object in the first system.

58. The first system according to any one of claims 52 to 57, wherein the instruction indicates creating the first object in the first system.

59. The first system according to claim 58, wherein the instruction is obtained when a user adds, through the management interface, the first object in the first system; and the performing module is further configured to create the first object in the first system and generate a first piece of attribute information of the first object in the first system.

60. The first system according to claim 59, wherein the first object exists in a second system, and the first object has a second piece of attribute information in the second system; where the obtaining module is further configured to obtain, from the management interface, the second piece of attribute information of the first object ; and the performing module is further configured to: record the second piece of attribute information of the first object; and inform, through the management interface, the second system of the first piece of attribute information of the first object.

61. The first system according to any one of claims 52 to 57, wherein the instruction indicates modifying a piece of attribute information of the first object in the first system.

62. The first system according to claim 61, wherein the instruction is obtained when a user modifies, through the management interface, a first piece of attribute information of the first object to a first value in the first system, and the instruction indicates modifying the first piece of attribute information of the first object to the first value ; and the performing module is further configured to modify the first piece of attribute information of the first object to the first value in the first system.

63. The first system according to claim 61, wherein the instruction is obtained in a case that a second system has modified a second piece of attribute information of the first object to a second value in the second system, the second system records that the second piece of attribute information is related to the first object in the first system, and the instruction indicates modifying the second piece of attribute information of the first object to the second value; and the performing module is further configured to modify the second piece of 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, wherein the performing module is further configured to ask whether a third piece of attribute information in a third system has been modified; wherein the instruction is obtained in a case that the third piece of attribute information of the first object has been changed to a third value, and the instruction indicates modifying the third piece of attribute information of the first object to the third value; and the performing module is further configured to modify in the first system the third piece of attribute information of the first object to the third value.

65. The first system according to claim 64, wherein the query of whether the third piece of attribute information in the third system has been modified is conducted periodically.

66. The first system according to any one of claims 52 to 57, wherein the instruction is obtained in a case that a fourth system creates the first object and generates a fourth piece of attribute information of the first object in the fourth system, and the instruction indicates recording the fourth piece of attribute information of the first object; and the performing module is further configured to record the fourth piece of attribute information of the first object.

67. The first system according to any one of claims 52 to 66, wherein the attribute information indicates one of: an identifier of the first object; description information of the first object; or address information of the first object.

68. The first system according to any one of claims 52 to 67, wherein the first system is one of a production system, a supply chain system, a sales system, or an operation and maintenance system.

69. A management interface, comprising: a processing circuitry for executing the method according to any one of claims 1 to 17.

70. A first system, comprising: a processing circuitry for executing the method according to any one of claims 18 to 34.

71. An object management system, comprising: a management interface according to any one of claims 35 to 51 or a management interface according to claim 69; a first system according to any one of claims 52 to 68 or a first system according to claim 70; 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.

72. An object management system, comprising:a first processing circuitry for executing the method according to any one of claims 1 to 17; a second processing circuitry for executing the method according to any one of claims 18 to 34; and at least one third processing circuitry, wherein the at least one third processing circuitry belongs to one of a production system, a supply chain system, a sales system, or an operation and maintenance system .

73. A computer-readable storage medium storing computer execution instructions which, when executed by a processor, cause the processor to execute the first system according to any one of claims 1 to 34.

74. A computer program product comprising computer execution instructions which, when executed by a processor, cause the processor to execute the first system according to any one of claims 1 to 34.

Images