A method, device, equipment and storage medium for assigning cross-system data objects

Abstract

The present application discloses a method, device, equipment and storage medium for assigning values to cross-system data objects, relating to the technical field of data processing. The method includes: when an object assignment instruction is recognized, obtaining a source object from a source business system and an object to be assigned from a target business system; the source business system and the target business system are different systems for processing the same target business; performing a field name consistency check and a data type consistency check on the source object and the object to be assigned; when it is recognized that both the field name consistency check and the data type consistency check fail, performing a semantic similarity analysis on the metadata of the source object and the object to be assigned to obtain a semantic similarity analysis result; and assigning a value to the object to be assigned according to the semantic similarity analysis result and the source object. The above technical solution helps to ensure the efficiency and accuracy of value assignment on the basis of realizing automatic value assignment.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, in particular to the field of data processing technology, and specifically relate to a method, device, equipment and storage medium for assigning values to cross-system data objects. Background Art

[0002] During the development process, data assignment to each other is a very frequent operation. Some assignments are between objects of the same type but different, and some are between different objects of different types. These assignment operations are relatively mechanical and cumbersome, and it is very easy for programmers to feel boring.

[0003] Currently, there are already many IDE (Integrated Development Environment) plugins to reduce the repetitive operations of field assignment. However, these tools are all based on reflection during the program compilation stage, mapping and assigning the attributes of the source object to the target object. There are certain problems with this. For example, some fields will not be automatically assigned, but it cannot be perceived during the coding stage, and there may be format errors in the conversion of some field assignments, which also cannot be perceived during the coding stage. This will cause some problems to be exposed only when the program is running, and then coding repairs, packaging and compilation, release and deployment, etc. are carried out, wasting unnecessary time back and forth. Summary of the Invention

[0004] The present application provides a method, device, equipment and storage medium for assigning values to cross-system data objects to ensure the efficiency and accuracy of assignment on the basis of realizing automatic assignment.

[0005] According to one aspect of the present application, a method for assigning values to cross-system data objects is provided, which is applied to an object assignment development plugin; the method includes:

[0006] When an object assignment instruction is recognized, obtain a source object from a source business system and an object to be assigned from a target business system; the source business system and the target business system are different systems for processing the same target business;

[0007] Perform a field name consistency check and a data type consistency check on the source object and the object to be assigned;

[0008] When it is recognized that both the field name consistency check and the data type consistency check fail, perform a semantic similarity analysis on the metadata of the source object and the object to be assigned to obtain a semantic similarity analysis result; the metadata includes field meaning, field annotation and field note;

[0009] Assign a value to the object to be assigned according to the semantic similarity analysis result and the source object.

[0010] According to another aspect of the present application, there is provided an assignment device for cross-system data objects, configured in an object assignment development plugin; the device includes:

[0011] An object acquisition module, configured to, when an object assignment instruction is recognized, acquire a source object from a source business system and an object to be assigned from a target business system; the source business system and the target business system are different systems for processing the same target business;

[0012] An object verification module, configured to perform field name consistency verification and data type consistency verification on the source object and the object to be assigned;

[0013] A semantic analysis module, configured to, when it is recognized that both the field name consistency verification and the data type consistency verification fail, perform semantic similarity analysis on the metadata of the source object and the object to be assigned to obtain a semantic similarity analysis result; the metadata includes field meanings, field annotations, and field remarks;

[0014] An object assignment module, configured to assign values to the object to be assigned according to the semantic similarity analysis result and the source object.

[0015] According to another aspect of the present application, there is provided an electronic device, which includes:

[0016] One or more processors;

[0017] A memory, configured to store one or more programs;

[0018] When the one or more programs are executed by the one or more processors, the one or more processors implement any one of the cross-system data object assignment methods provided by the embodiments of the present application.

[0019] According to another aspect of the present application, there is provided a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, it implements any one of the cross-system data object assignment methods provided by the embodiments of the present application.

[0020] According to another aspect of the present application, there is provided a computer program product, including a computer program, and when the computer program is executed by a processor, it implements any one of the cross-system data object assignment methods provided by the embodiments of the present application.

[0021] In this application, when an object assignment instruction is recognized, the source object is obtained from the source business system, and the object to be assigned is obtained from the target business system; the source business system and the target business system are different systems for processing the same target business; the field name consistency check and data type consistency check are performed on the source object and the object to be assigned; when it is recognized that both the field name consistency check and the data type consistency check fail, the metadata of the source object and the object to be assigned is subjected to semantic similarity analysis to obtain a semantic similarity analysis result; the object to be assigned is assigned according to the semantic similarity analysis result and the source object. The above technical solution helps to ensure the efficiency and accuracy of the assignment on the basis of realizing automatic assignment. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 is a flowchart of a method for assigning cross-system data objects according to Embodiment 1 of this application;

[0023] Figure 2 is a flowchart of a method for assigning cross-system data objects according to Embodiment 2 of this application;

[0024] Figure 3 is a schematic structural diagram of a device for assigning cross-system data objects according to Embodiment 3 of this application;

[0025] Figure 4 is a schematic structural diagram of an electronic device for implementing the method for assigning cross-system data objects of the embodiments of this application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0026] In order to enable those skilled in the art to better understand the solutions of this application, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of this application. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in this application without creative efforts shall fall within the scope of protection of this application.

[0027] It should be noted that in the description and claims of this application and the above-mentioned drawings, terms such as "first" and "second" are used to distinguish similar objects, and do not necessarily describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of this application described here can be implemented in an order other than those illustrated or described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0028] In addition, it should also be noted that in the technical solution of this application, the processing of relevant data such as object assignment instructions and source objects, including collection, storage, use, processing, transmission, provision, and disclosure, complies with the provisions of relevant laws and regulations and does not violate public order and good customs.

[0029] Embodiment 1

[0030] Figure 1 is a flowchart of a method for assigning cross-system data objects according to Embodiment 1 of this application. This embodiment is applicable to the situation of mutual assignment of cross-system data and can be executed by an assignment device for cross-system data objects. The assignment device for cross-system data objects can be implemented in the form of hardware and / or software, and the assignment device for cross-system data objects can be configured in a computer device, such as an object assignment development plugin. As Figure 1 shown, this method is applied to an object assignment development plugin, and the method includes:

[0031] S110. When an object assignment instruction is recognized, obtain a source object from a source business system and an object to be assigned from a target business system; the source business system and the target business system are different systems for processing the same target business.

[0032] In this embodiment, the object assignment instruction refers to a code for starting the object assignment development plug-in and contains the relevant objects that need to be assigned. The source business system refers to the system responsible for providing the source of assignment data or the source object of assignment data in the business process. The source object refers to the data object obtained from the source business system, which usually contains some field data; exemplarily, the field data can be data used to describe user identity information, data used to describe construction environment information, etc. The target business system refers to the system that currently needs to perform an assignment operation. The object to be assigned refers to the data object that needs to be filled or updated in the target business system. It may already exist, but the field needs to be assigned or modified, and usually contains some field data; exemplarily, the field data can be data used to describe user identity information, data used to describe construction environment information, etc. The target business refers to the business field to which the field data contained in the source object and the object to be assigned belongs, which can be the user identity information field, the construction environment information field, etc.

[0033] In an optional implementation, after obtaining the source object from the source business system and the object to be assigned from the target business system, historical assignment statements are searched for using the source object and the object to be assigned as indexes; if there are historical assignment statements between the source object and the object to be assigned, the historical assignment statements and the source object are used to assign the object to be assigned; if there are no historical assignment statements between the source object and the object to be assigned, field name consistency check and data type consistency check are performed on the fields for which no historical assignment statements exist between the source object and the object to be assigned.

[0034] In this embodiment, the historical assignment statement refers to an assignment operation that has been executed before, and records the assignment relationship between the source object and the object to be assigned.

[0035] It should be noted that, when it is not the first assignment between the source object and the object to be assigned, and there is a historical assignment statement, the assignment using the historical assignment statement has the highest priority.

[0036] In another optional implementation, if there is at least one historical assignment statement for the same field to be assigned in the object to be assigned, the number of occurrences of the historical assignment statements are compared, and the historical assignment statement with the largest number of occurrences is used as the assignment statement for the field to be assigned.

[0037] It should be noted that the assignment statement can be used in both directions. There is an operation in which the source object assigns a value to the object to be assigned. The same method can also be used when the object to be assigned in the target business system assigns a value to the source object in the source business system.

[0038] S120: Perform field name consistency check and data type consistency check on the source object and the object to be assigned.

[0039] In this embodiment, the field name consistency check refers to checking whether there are consistent field names in the source object and the object to be assigned. The data type consistency check refers to checking whether there are matching data types in the corresponding fields of the source object and the object to be assigned.

[0040] In an alternative embodiment, when it is recognized that there are fields passing the field name consistency check, the candidate source fields passing the field name consistency check in the source object and the candidate fields to be assigned passing the field name consistency check in the object to be assigned are determined; a data type consistency check is performed on the candidate source fields and the candidate fields to be assigned to obtain a data type check result; and the object to be assigned is assigned according to the source object, the first metadata of the source object, the second metadata of the object to be assigned, and the data type check result.

[0041] In this embodiment, the candidate source field refers to the source field in the source object with the same field name as the field in the object to be assigned. The candidate field to be assigned refers to the field to be assigned in the object to be assigned with the same field name as the field in the source object. The first metadata refers to the data used to describe the field data in the source object, usually including the meaning, annotation, and comment of the field data. The second metadata refers to the data used to describe the field data in the object to be assigned, usually including the meaning, annotation, and comment of the field data. The data type check result refers to the check result of the field used to describe whether there are the same data types between the candidate source field and the candidate field to be assigned, and its content may include the specific fields with the same data type and the specific fields with different data types between the candidate source field and the candidate field to be assigned.

[0042] Specifically, assigning the object to be assigned according to the source object, the first metadata of the source object, the second metadata of the object to be assigned, and the data type check result may be that if there are fields passing the data type consistency check in the data type check result, then according to the data type check result, the first available source field passing the data type consistency check is determined from the candidate source fields, and the first assignment field passing the data type consistency check is determined from the candidate fields to be assigned; the target object is assigned according to the candidate source fields, the first available source field, the source object, the first metadata of the source object, and the second metadata of the target object; if there are no fields passing the data type consistency check in the data type check result, then the target object is assigned according to the candidate source fields, the source object, the first metadata of the source object, and the second metadata of the target object.

[0043] In this embodiment, the first available source field refers to the field in the candidate source fields with the same data type as at least one candidate field to be assigned. The first assignment field refers to the field in the candidate assignment fields with the same data type as at least one candidate source field.

[0044] Further, the assignment to the target object based on the candidate source field, the source object, the first metadata of the source object, and the second metadata of the target object may be as follows: Based on the field name correspondence between the candidate source field and the candidate field to be assigned, perform type conversion on the candidate source field, and assign the value of the candidate source field after type conversion to the candidate field to be assigned; perform semantic similarity analysis on the first metadata of the source object and the second metadata of the target object to determine the similar assignment fields and non-similar assignment fields between the third assignment fields and the third available source fields; the third available source fields refer to other source fields in the source object except the candidate source field; the third assignment fields refer to other assignment fields in the target object except the candidate field to be assigned; assign the value of the third available source field corresponding to the similar assignment field to the similar assignment field, and add a description of no assignment data for the non-similar assignment fields.

[0045] In this embodiment, the third assignment fields refer to the fields in the target object that do not pass the field name consistency check. The third available source fields refer to the fields in the source object that do not pass the field name consistency check. The similar assignment fields refer to the fields in the third assignment fields that have semantic similarity with the third available fields. The non-similar fields refer to the fields in the third assignment fields that do not have semantic similarity with the third available fields.

[0046] Further, the assignment to the target object based on the candidate source field, the first available source field, the source object, the first metadata of the source object, and the second metadata of the target object may be as follows: Based on the field name correspondence between the first available source field and the first assignment field, directly assign the value of the first available source field to the first assignment field; based on the field name correspondence between the second available source field and the second assignment field, perform type conversion on the second available source field, and assign the value of the second available source field after type conversion to the second assignment field; the second available source fields refer to other source fields in the candidate source field except the first available source field; the second assignment fields refer to other fields to be assigned in the candidate field to be assigned except the first assignment field; assign values to the third assignment fields of the target object according to the third available source fields, the first metadata of the source object, and the second metadata of the target object; the third available source fields refer to other source fields in the source object except the candidate source field; the third assignment fields refer to other assignment fields in the target object except the candidate field to be assigned.

[0047] Further, according to the third available source field, the first metadata of the source object, and the second metadata of the target object, assigning values to the third assignment field of the target object may be to perform semantic similarity analysis on the first metadata of the source object and the second metadata of the target object to determine the similar assignment fields and dissimilar assignment fields between the third assignment field and the third available source field; assign the values of the third available source fields corresponding to the similar assignment fields to the similar assignment fields, and add no-assignment data descriptions for the dissimilar assignment fields.

[0048] It should be noted that the technical solution of this application can be executed based on priorities. The first priority is to assign values to the fields that pass the field name consistency check and the data type consistency check; the second priority is to assign values to the fields that pass the field name consistency check but fail the data type consistency check; the third priority is to assign values to the fields that fail both the field name consistency check and the data type consistency check.

[0049] S130. In the case where both the field name consistency check and the data type consistency check are not passed, perform semantic similarity analysis on the metadata of the source object and the object to be assigned values to obtain the semantic similarity analysis result; the metadata includes field meaning, field comment, and field annotation.

[0050] In this embodiment, metadata refers to the data used to describe field data, usually including the meaning, annotation, and comment of the field data. Semantic similarity analysis refers to analyzing the metadata of the source object and the object to be assigned values to evaluate the similarity at the semantic level between them; this usually relies on natural language processing and machine learning technologies to identify the semantic relevance between two fields. Field meaning refers to the actual meaning or business meaning of the data represented by a field; it explains the role and use of the field in the system or business. Field comment refers to a short explanation or description of a database field or a field in the code, usually added by developers or database designers so that other people can quickly understand the use of the field when querying the database; field comments are usually stored as part of the metadata in the database table structure. Field annotation refers to providing additional information for a field in the code, usually parsed and used in a framework or tool; field annotation is not only a description of the field, but may also include some configuration or constraint conditions (such as field validation, mapping relationships, etc.).

[0051] S140. Assign values to the object to be assigned values according to the semantic similarity analysis result and the source object.

[0052] In an alternative embodiment, after the assignment to the object to be assigned is completed, the assignment relationship between the source object and the object to be assigned can be saved, so that when the source object and the object to be assigned are assigned subsequently, this assignment relationship can be directly adopted, which helps to improve the efficiency of assignment.

[0053] In the embodiment of the present application, when an object assignment instruction is recognized, the source object is obtained from the source business system, and the object to be assigned is obtained from the target business system; the source business system and the target business system are different systems for processing the same target business; the field name consistency check and the data type consistency check are performed on the source object and the object to be assigned; when it is recognized that both the field name consistency check and the data type consistency check fail, the metadata of the source object and the object to be assigned is subjected to semantic similarity analysis to obtain a semantic similarity analysis result; the object to be assigned is assigned according to the semantic similarity analysis result and the source object. The above technical solution helps to ensure the efficiency and accuracy of assignment on the basis of realizing automatic assignment.

[0054] Embodiment 2

[0055] Figure 2 is a flowchart of a method for assigning cross-system data objects provided according to Embodiment 2 of the present application. On the basis of the technical solutions of the above embodiments, "assigning the object to be assigned according to the semantic similarity analysis result and the source object" is refined to "if there are no matchable fields in the semantic similarity analysis result, determine the fields that cannot be assigned to the object to be assigned, and obtain the first knowledge graph of the source object from the source business system and the second knowledge graph of the object to be assigned from the target business system; assign the fields that cannot be assigned according to the first knowledge graph and the second knowledge graph". It should be noted that for the parts not detailed in the embodiments of the present application, reference may be made to the relevant descriptions of other embodiments. As Figure 2 shown, the method includes:

[0056] S210. When an object assignment instruction is recognized, obtain the source object from the source business system and the object to be assigned from the target business system; the source business system and the target business system are different systems for processing the same target business.

[0057] S220. Perform a field name consistency check and a data type consistency check on the source object and the object to be assigned.

[0058] S230. When it is recognized that both the field name consistency check and the data type consistency check fail, perform semantic similarity analysis on the metadata of the source object and the object to be assigned to obtain a semantic similarity analysis result.

[0059] S240. If there are no matchable fields in the semantic similarity analysis result, determine the unassignable fields of the object to be assigned, obtain the first knowledge graph of the source object from the source business system, and obtain the second knowledge graph of the object to be assigned from the target business system.

[0060] In this embodiment, the unassignable fields refer to the fields in the object to be assigned that cannot pass the semantic similarity analysis and cannot be directly assigned using the source object. The knowledge graph refers to a knowledge network containing rich information and data constructed in the form of a graph; it represents entities and their relationships through nodes and edges, and is usually used to describe the knowledge structure of the real world. The first knowledge graph refers to the knowledge graph in the source business system, which is used to describe the relevant knowledge, entities, attributes of the source object, and the relationships between them. The second knowledge graph refers to the knowledge graph in the target business system, which is used to describe the relevant knowledge, entities, attributes of the object to be assigned, and the relationships between them; for example, the first knowledge graph of the source business system may contain the relationship between "user name" and "user ID", while the second knowledge graph of the target business system describes the relationship between "user name" and "user identifier".

[0061] Optionally, if there are matchable fields in the semantic similarity analysis result, determine the assignable source fields of the source object, the assignable fields of the object to be assigned, and the corresponding relationship between the assignable source fields and the assignable fields; based on the corresponding relationship between the assignable source fields and the assignable fields, assign the value of the assignable source field to the assignable field of the object to be assigned.

[0062] In this embodiment, the matchable fields refer to the fields with semantic similarity that can be matched between the source object and the object to be assigned. The assignable source fields refer to the fields in the source object that can be assigned to the object to be assigned through semantic similarity analysis. The assignable fields refer to the fields in the object to be assigned that have semantic similarity matching with the source object. The corresponding relationship between the assignable source fields and the assignable fields refers to the corresponding relationship of fields with the same semantic similarity between the assignable source fields and the assignable fields.

[0063] S250. Assign values to the unassignable fields according to the first knowledge graph and the second knowledge graph.

[0064] Optionally, establish a field semantic relationship mapping for the first knowledge graph and the second knowledge graph according to the domain ontology library of the target business to obtain a semantic relationship graph; use the unassignable fields as indexes to find the target source fields corresponding to the unassignable fields from the semantic relationship graph, and assign the values of the target source fields to the unassignable fields.

[0065] In this embodiment, the domain ontology library refers to the structured data that describes the knowledge and concepts of a specific domain (such as finance, healthcare, education, etc.); it includes all the core concepts, entities, attributes within the domain and the relationships between them, and provides detailed definitions of these concepts. The field semantic relationship mapping refers to establishing the semantic association between them by comparing the meanings and contexts of the fields in the source system and the target system; through this mapping, the fields with similar or identical meanings in the two systems can be found. The semantic relationship graph is a graphical structure formed by establishing the semantic relationships between the fields in the source business system and the target business system; it shows the semantic connections between the fields and how to perform data migration or transformation through semantic matching; for example, if "Customer ID (Identification)" in the source system is semantically similar to "User ID" in the target system, then they will be connected in the semantic relationship graph, indicating that these two fields can be transformed through semantic mapping. The target source field refers to the source business system field corresponding to the field of the target business system found through semantic relationship mapping in the semantic relationship graph; it is the field that can provide data for the fields that cannot be assigned values; for example, if the "Customer Email" field in the source system has a semantic relationship mapping with the "User Email" field in the target system, then the "Customer Email" field in the source system can provide a value for the "User Email" field in the target system.

[0066] It can be understood that by using the target business domain ontology library and combining the field information in the source system and the target system, the semantic relationship mapping between them is established. By comparing the domain ontology libraries of the two, it is determined which fields are similar or equivalent; according to the mapping results, a semantic relationship graph is constructed to graphically display the similar fields in the source system and the target system and clarify the relationships between them; through the semantic relationship graph, using the fields that cannot be assigned values as indexes, the target source fields that can provide values for them are searched. If relevant target source fields are found, their values can be assigned to the fields that cannot be assigned values; once the corresponding target source fields are found, the system can transfer the values in the target source fields to the fields that cannot be assigned values to complete the data filling or transformation. This process helps the system solve the problem of field mismatch during cross-system data assignment, enabling the data to be smoothly transformed and assigned.

[0067] In an alternative embodiment, during the process of using the source object to assign values to the object to be assigned, complex field existence verification can be performed on the source object and the object to be assigned; if there are complex fields and there is no historical assignment statement for such complex fields, then no assignment is performed on such complex fields.

[0068] In this embodiment, a complex field refers to a field with a multi-level structure or multiple data types, rather than just a simple single data type (such as numbers, text, etc.); it usually includes complex structures such as nested objects, arrays, lists, etc., or fields that combine multiple attributes; for example, an "address" field may include sub-fields such as "street", "city", "postal code", etc., or an "order" field may include multiple sub-fields such as "order ID", "product list", "total amount", etc. The existence check of complex fields refers to determining whether there are field attributes of complex classes in the fields of the source object and the object to be assigned.

[0069] In the embodiment of the present application, when an object assignment instruction is recognized, the source object is obtained from the source business system, and the object to be assigned is obtained from the target business system; the source business system and the target business system are different systems for processing the same target business; the field name consistency check and the data type consistency check are performed on the source object and the object to be assigned; when it is recognized that both the field name consistency check and the data type consistency check fail, the semantic similarity analysis is performed on the metadata of the source object and the object to be assigned to obtain the semantic similarity analysis result; if there are no matchable fields in the semantic similarity analysis result, the unassignable fields of the object to be assigned are determined, and the first knowledge graph of the source object is obtained from the source business system, and the second knowledge graph of the object to be assigned is obtained from the target business system; according to the first knowledge graph and the second knowledge graph, the unassignable fields are assigned. The above technical solution, in the case where the semantic similarity analysis cannot assign values to the unassignable fields of the object to be assigned, by introducing the combined use of the knowledge graph, the unassignable fields can be further analyzed, which helps to ensure the efficiency and accuracy of the assignment.

[0070] Embodiment III

[0071] Figure 3 It is a schematic structural diagram of an assignment device for cross-system data objects provided by Embodiment III of the present application, which is applicable to the case of mutual assignment of cross-system data. The assignment device for cross-system data objects can be implemented in the form of hardware and / or software, and the assignment device for cross-system data objects can be configured in a computer device, such as an object assignment development plugin. As Figure 3 shown, the device includes:

[0072] An object acquisition module 310, configured to obtain a source object from a source business system and an object to be assigned from a target business system when an object assignment instruction is recognized; the source business system and the target business system are different systems for processing the same target business;

[0073] An object verification module 320, configured to perform a field name consistency check and a data type consistency check on the source object and the object to be assigned;

[0074] A semantic analysis module 330, configured to perform semantic similarity analysis on the metadata of the source object and the object to be assigned when it is recognized that both the field name consistency check and the data type consistency check have failed, so as to obtain a semantic similarity analysis result; the metadata includes field meanings, field annotations, and field notes.

[0075] An object assignment module 340, configured to assign a value to the object to be assigned according to the semantic similarity analysis result and the source object.

[0076] In the embodiment of the present application, when an object assignment instruction is recognized, a source object is obtained from a source business system, and an object to be assigned is obtained from a target business system; the source business system and the target business system are different systems for processing the same target business; a field name consistency check and a data type consistency check are performed on the source object and the object to be assigned; when it is recognized that both the field name consistency check and the data type consistency check have failed, semantic similarity analysis is performed on the metadata of the source object and the object to be assigned to obtain a semantic similarity analysis result; and the object to be assigned is assigned a value according to the semantic similarity analysis result and the source object. The above technical solution helps to ensure the efficiency and accuracy of the assignment while realizing automatic assignment.

[0077] Optionally, the object assignment module 340 includes:

[0078] A knowledge graph acquisition unit, configured to determine the unassignable fields of the object to be assigned if there are no matchable fields in the semantic similarity analysis result, and obtain a first knowledge graph of the source object from the source business system and a second knowledge graph of the object to be assigned from the target business system.

[0079] A first field assignment unit, configured to assign values to the unassignable fields according to the first knowledge graph and the second knowledge graph.

[0080] Optionally, the first field assignment unit is specifically configured to:

[0081] Establish a field semantic relationship mapping for the first knowledge graph and the second knowledge graph according to the domain ontology library of the target business to obtain a semantic relationship graph.

[0082] Using the unassignable fields as indexes, search for the target source fields corresponding to the unassignable fields in the semantic relationship graph, and assign the values of the target source fields to the unassignable fields.

[0083] Optionally, the object assignment module 340 further includes a second field assignment unit; the second field assignment unit is configured to:

[0084] If there are matchable fields in the semantic similarity analysis result, determine the assignable source fields of the source object, the unassignable fields of the object to be assigned, and the correspondence between the assignable source fields and the fields to be assigned;

[0085] Based on the correspondence between the assignable source fields and the fields to be assigned, assign the values of the assignable source fields to the fields to be assigned.

[0086] Optionally, the device further includes a historical assignment module, which is used for:

[0087] After obtaining the source object from the source business system and the object to be assigned from the target business system, search for historical assignment statements using the source object and the object to be assigned as indexes;

[0088] If there is a historical assignment statement between the source object and the object to be assigned, use the historical assignment statement and the source object to assign values to the object to be assigned;

[0089] If there is no historical assignment statement between the source object and the object to be assigned, perform a field name consistency check and a data type consistency check on the fields for which there is no historical assignment statement between the source object and the object to be assigned.

[0090] Optionally, the object assignment module 340 is further used for:

[0091] In the case of identifying fields that pass the field name consistency check, determine the candidate source fields in the source object that pass the field name consistency check and the candidate fields to be assigned in the object to be assigned that pass the field name consistency check;

[0092] Perform a data type consistency check on the candidate source fields and the candidate fields to be assigned to obtain a data type check result;

[0093] Assign values to the object to be assigned according to the source object, the first metadata of the source object, the second metadata of the object to be assigned, and the data type check result.

[0094] The assignment device for cross-system data objects provided by the embodiments of the present application can execute the assignment method for cross-system data objects provided by any embodiment of the present application, and has the corresponding functional modules and beneficial effects for executing each assignment method for cross-system data objects.

[0095] According to the embodiments of the present application, the present application also provides an electronic device, a readable storage medium, and a computer program product.

[0096] Embodiment 4

[0097] Figure 4FIG. 0 is a schematic structural diagram of an electronic device 410 for implementing the method for assigning cross-system data objects in the embodiments of the present application. The electronic device is intended to represent various forms of digital computers, such as, laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as, personal digital processors, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present application described and / or claimed herein.

[0098] As Figure 4 shown, the electronic device 410 includes at least one processor 411, and a memory communicatively connected to the at least one processor 411, such as a read-only memory (ROM) 412, a random access memory (RAM) 413, etc. The memory stores a computer program executable by the at least one processor. The processor 411 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 412 or the computer program loaded from the storage unit 418 into the random access memory (RAM) 413. In the RAM 413, various programs and data required for the operation of the electronic device 410 can also be stored. The processor 411, the ROM 412, and the RAM 413 are connected to each other through a bus 414. The input / output (I / O) interface 415 is also connected to the bus 414.

[0099] Multiple components in the electronic device 410 are connected to the I / O interface 415, including: an input unit 416, such as a keyboard, a mouse, etc.; an output unit 417, such as various types of displays, speakers, etc.; a storage unit 418, such as a magnetic disk, an optical disk, etc.; and a communication unit 419, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 419 allows the electronic device 410 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0100] The processor 411 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the processor 411 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The processor 411 executes the various methods and processes described above, such as the method for assigning cross-system data objects.

[0101] In some embodiments, the method for assigning cross-system data objects may be implemented as a computer program tangibly embodied in a computer-readable storage medium, such as storage unit 418. In some embodiments, part or all of the computer program may be loaded and / or installed onto the electronic device 410 via the ROM 412 and / or the communication unit 419. When the computer program is loaded into the RAM 413 and executed by the processor 411, one or more steps of the method for assigning cross-system data objects described above may be performed. Alternatively, in other embodiments, the processor 411 may be configured to the method for assigning cross-system data objects by any other suitable means (e.g., by means of firmware).

[0102] The various embodiments of the systems and techniques described above in this document may be implemented in digital electronic circuitry, integrated circuit systems, field programmable gate arrays (FPGA), application specific integrated circuits (ASIC), application specific standard products (ASSP), systems on a chip (SOC), complex programmable logic devices (CPLD), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include: implemented in one or more computer programs that may be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a special-purpose or general-purpose programmable processor that receives data and instructions from a storage system, at least one input device, and at least one output device, and transmits the data and instructions to the storage system, the at least one input device, and the at least one output device.

[0103] The computer programs for implementing the methods of the present application may be written in any combination of one or more programming languages. These computer programs may be provided to the processor of a general-purpose computer, a special-purpose computer, or other programmable apparatus for assigning cross-system data objects, such that the computer programs, when executed by the processor, cause the functions / operations specified in the flowchart and / or block diagram to be implemented. The computer programs may be executed entirely on the machine, partially on the machine, as a stand-alone software package partially on the machine and partially on a remote machine, or entirely on the remote machine or server.

[0104] In the context of this application, a computer-readable storage medium can be a tangible medium that can contain or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer-readable storage medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. Alternatively, the computer-readable storage medium can be a machine-readable signal medium. More specific examples of the machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0105] To provide for interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the electronic device. Other kinds of devices can also be used to provide for interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0106] The systems and techniques described herein can be implemented in a computing system that includes backend components (such as, for example, a data server), or a computing system that includes middleware components (such as, for example, an application server), or a computing system that includes frontend components (such as, for example, a user computer having a graphical user interface or a web browser through which the user can interact with an implementation of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system can be interconnected by any form or medium of digital data communication (such as, for example, a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0107] A computing system may include a client and a server. The client and the server are generally far from each other and usually interact via a communication network. The client-server relationship is created by computer programs running on respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or a cloud host, which is a host product in the cloud computing service system, and solves the defects of difficult management and weak business scalability existing in traditional physical hosts and VPS services.

[0108] It should be understood that various forms of processes shown above can be used, steps can be reordered, added or deleted. For example, the steps described in this application can be executed in parallel, sequentially or in a different order, as long as the desired results of the technical solution of this application can be achieved, and no limitation is made herein.

[0109] The above specific embodiments do not constitute a limitation on the protection scope of this application. Those skilled in the art should understand that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principle of this application shall be included within the protection scope of this application.

Claims

1. A method for assigning cross-system data objects, characterized in that, A plug-in applied to object assignment development; the method includes: When an object assignment instruction is recognized, obtain a source object from a source business system and an object to be assigned from a target business system; the source business system and the target business system are different systems for processing the same target business; Search for historical assignment statements using the source object and the object to be assigned as indexes; If there is a historical assignment statement between the source object and the object to be assigned, use the historical assignment statement and the source object to assign a value to the object to be assigned; If there is no historical assignment statement between the source object and the object to be assigned, perform a field name consistency check and a data type consistency check on the fields where there is no historical assignment statement between the source object and the object to be assigned; When it is recognized that both the field name consistency check and the data type consistency check fail, perform a semantic similarity analysis on the metadata of the source object and the object to be assigned to obtain a semantic similarity analysis result; the metadata includes field meanings, field notes, and field annotations; Assign a value to the object to be assigned according to the semantic similarity analysis result and the source object; Among them, the assigning a value to the object to be assigned according to the semantic similarity analysis result and the source object includes: If there are no matchable fields in the semantic similarity analysis result, determine the fields of the object to be assigned that cannot be assigned, and obtain the first knowledge graph of the source object from the source business system and the second knowledge graph of the object to be assigned from the target business system; the fields that cannot be assigned refer to the fields that fail the semantic similarity analysis and cannot be directly assigned a value using the source object; Assign a value to the fields that cannot be assigned according to the first knowledge graph and the second knowledge graph; Among them, during the process of assigning a value to the object to be assigned, perform a complex field existence check on the source object and the object to be assigned; if there are complex fields and there is no historical assignment statement for such complex fields, do not assign a value to such complex fields.

2. The method according to claim 1, wherein Assigning a value to the fields that cannot be assigned according to the source object, the first knowledge graph, and the second knowledge graph includes: Establish a field semantic relationship mapping for the first knowledge graph and the second knowledge graph according to the domain ontology library of the target business to obtain a semantic relationship graph; Using the fields that cannot be assigned as indexes, search for the target source fields corresponding to the fields that cannot be assigned from the semantic relationship graph, and assign the values of the target source fields to the fields that cannot be assigned.

3. The method according to claim 1, characterized in that, The assigning a value to the object to be assigned according to the semantic similarity analysis result and the source object includes: If there are matchable fields in the semantic similarity analysis result, determine the assignable source fields of the source object, the assignable fields of the object to be assigned, and the correspondence between the assignable source fields and the assignable fields; Based on the correspondence between the assignable source fields and the assignable fields, assign the values of the assignable source fields to the assignable fields of the object to be assigned.

4. The method according to claim 1, wherein The method further includes: In the case where a field passing the field name consistency check is recognized, determining a candidate source field passing the field name consistency check in the source object and a candidate field to be assigned passing the field name consistency check in the object to be assigned; Performing a data type consistency check on the candidate source field and the candidate field to be assigned to obtain a data type check result; Assigning a value to the object to be assigned according to the source object, the first metadata of the source object, the second metadata of the object to be assigned, and the data type check result.

5. An assignment device for cross-system data objects, characterized in that, Configured in an object assignment development plugin; the device includes: An object acquisition module, configured to, in the case where an object assignment instruction is recognized, acquire a source object from a source business system and an object to be assigned from a target business system; the source business system and the target business system are different systems for processing the same target business; A historical assignment module, configured to search for historical assignment statements using the source object and the object to be assigned as indexes; if there is a historical assignment statement between the source object and the object to be assigned, using the historical assignment statement and the source object to assign a value to the object to be assigned; if there is no historical assignment statement between the source object and the object to be assigned, performing a field name consistency check and a data type consistency check on the fields where there is no historical assignment statement between the source object and the object to be assigned; A semantic analysis module, configured to, in the case where it is recognized that both the field name consistency check and the data type consistency check fail, perform a semantic similarity analysis on the metadata of the source object and the object to be assigned to obtain a semantic similarity analysis result; the metadata includes field meanings, field annotations, and field notes; An object assignment module, configured to assign a value to the object to be assigned according to the semantic similarity analysis result and the source object; Wherein, the object assignment module includes: A knowledge graph acquisition unit, configured to, if there is no matchable field in the semantic similarity analysis result, determine the fields that cannot be assigned in the object to be assigned, and acquire a first knowledge graph of the source object from the source business system and a second knowledge graph of the object to be assigned from the target business system; the fields that cannot be assigned refer to the fields that do not pass the semantic similarity analysis and cannot be directly assigned using the source object; A first field assignment unit, configured to assign values to the fields that cannot be assigned according to the first knowledge graph and the second knowledge graph; Wherein, the object assignment module is further configured to: During the process of assigning a value to the object to be assigned, perform a complex field existence check on the source object and the object to be assigned; if there is a complex field and there is no historical assignment statement for this complex field, do not assign a value to this complex field.

6. An electronic device, characterized in that, Includes: One or more processors; A memory, configured to store one or more programs; When the one or more programs are executed by the one or more processors, enabling the one or more processors to implement the cross-system data object assignment method according to any one of claims 1-4.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by a processor, it implements the method for assigning cross-system data objects according to any one of claims 1-4.

8. A computer program product, comprising a computer program which, when executed by a processor, implements the method for assigning cross-system data objects according to any one of claims 1-4.

Images