Cross-system data object assignment method and device, equipment and storage medium

Abstract

The invention discloses a cross-system data object assignment method and device, equipment and a storage medium, and relates to the technical field of data processing. The method comprises the steps of obtaining a source object from a source business system and obtaining a to-be-assigned object from a target business system under the condition that an object assignment instruction is identified; the source service system and the target service system are different systems for processing the same target service; performing field name consistency verification and data type consistency verification on the source object and the object to be assigned; under the condition that it is recognized that the field name consistency verification and the data type consistency verification are not passed, semantic similarity analysis is conducted on metadata of the source object and metadata of the object to be assigned, and a semantic similarity analysis result is obtained; and assigning the object to be assigned according to the semantic similarity analysis result and the source object. According to the technical scheme, on the basis of realizing automatic assignment, the high efficiency and accuracy of assignment can be ensured.

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 to a method, apparatus, device and storage medium for assigning values ​​to cross-system data objects. Background Art

[0002] During the development process, data assignment is a very frequent operation. Some assignments are between different objects of the same type, and some are between different objects of different types. These assignment operations are relatively mechanical and cumbersome, which can easily make programmers feel boring.

[0003] There are already many IDE (Integrated Development Environment) plug-ins to reduce the repetitive operations of field assignment, but these tools are based on reflection in the program compilation phase, mapping the attributes of the source object to the target object. This has certain problems, such as some fields will not be automatically assigned, but it cannot be perceived in the coding phase, and some field assignment conversions may have format errors, which cannot be perceived in the coding phase. This will cause some problems to be exposed only when the program is running, and then the coding repair, packaging and compilation, release and deployment, etc., wasting unnecessary time. Summary of the invention

[0004] The present application provides a method, apparatus, device and storage medium for assigning values ​​to cross-system data objects, so as to ensure the efficiency and accuracy of the assignment while 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 object assignment development plug-ins; the method comprises:

[0006] When an object assignment instruction is identified, 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;

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

[0008] When it is identified that both the field name consistency check and the data type consistency check have failed, a 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; the metadata includes field meaning, field comment and field annotation;

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

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

[0011] An object acquisition module is used to acquire 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 identified; the source business system and the target business system are different systems for processing the same target business;

[0012] An object verification module is used 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, for performing semantic similarity analysis on the metadata of the source object and the object to be assigned when it is identified that both the field name consistency check and the data type consistency check have failed, to obtain a semantic similarity analysis result; the metadata includes field meaning, field comment and field annotation;

[0014] The object assignment module is used to assign a value 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, an electronic device is provided, the electronic device comprising:

[0016] one or more processors;

[0017] A memory for storing 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 in the embodiments of the present application.

[0019] According to another aspect of the present application, a computer-readable storage medium is provided, on which a computer program is stored. When the program is executed by a processor, any cross-system data object assignment method provided in the embodiments of the present application is implemented.

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

[0021] This application obtains the source object from the source business system and the object to be assigned from the target business system when an object assignment instruction is identified; the source business system and the target business system are different systems for processing the same target business; the source object and the object to be assigned are checked for field name consistency and data type consistency; when it is identified that both the field name consistency check and the data type consistency check have failed, a 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; the object to be assigned is assigned based on 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. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 is a flow chart of a method for assigning values ​​to cross-system data objects provided according to Embodiment 1 of the present application;

[0023] Figure 2 It is a flowchart of a method for assigning values ​​to cross-system data objects provided according to Embodiment 2 of the present application;

[0024] Figure 3 It is a structural diagram of a device for assigning values ​​to cross-system data objects provided according to Embodiment 3 of the present application;

[0025] Figure 4 It is a structural diagram of an electronic device that implements the cross-system data object assignment method of an embodiment of the present application. DETAILED DESCRIPTION

[0026] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0027] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

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

[0029] Embodiment 1

[0030] Figure 1 This is a flowchart of a method for assigning values ​​to cross-system data objects according to the first embodiment of the present application. This embodiment is applicable to the case of assigning values ​​to each other between cross-system data, and can be executed by a cross-system data object assignment device. The cross-system data object assignment device can be implemented in the form of hardware and / or software. The cross-system data object assignment device can be configured in a computer device, such as an object assignment development plug-in. Figure 1 As shown, the method is applied to object assignment development plug-in, and the method includes:

[0031] S110 . When an object assignment instruction is identified, 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.

[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, field name consistency check refers to checking whether there are consistent field names in the source object and the object to be assigned. Data type consistency check refers to checking whether there are matching data types in the corresponding fields in the source object and the object to be assigned.

[0040] In an optional implementation, when it is identified that there are fields that have passed the field name consistency check, candidate source fields in the source object that have passed the field name consistency check and candidate to-be-assigned fields in the to-be-assigned object that have passed the field name consistency check are determined; data type consistency check is performed on the candidate source fields and the candidate to-be-assigned fields to obtain a data type check result; and the to-be-assigned object is assigned based on the source object, the first metadata of the source object, the second metadata of the to-be-assigned object, and the data type check result.

[0041] In this embodiment, the candidate source field refers to the source field in the source object that has the same field name as the object to be assigned. The candidate field to be assigned refers to the field to be assigned in the object to be assigned that has the same field name as the source object. The first metadata refers to the data used to describe the field data in the source object, usually including the meaning, annotations and comments 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, annotations and comments of the field data. The data type verification result refers to the verification result used to describe whether there are fields of the same data type between the candidate source field and the candidate field to be assigned, and its content may include specific fields of the same data type and specific fields of different data types between the candidate source field and the candidate field to be assigned.

[0042] Specifically, 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 verification result, the object to be assigned can be assigned as follows: if there is a field that passes the data type consistency check in the data type verification result, then according to the data type verification result, determine the first available source field that passes the data type consistency check from the candidate source fields, and determine the first assignment field that passes the data type consistency check from the candidate fields to be assigned; assign the target object 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 is no field that passes the data type consistency check in the data type verification result, then assign the target object 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 a field in the candidate source fields that has a data type consistent with at least one candidate field to be assigned a value. The first assigned value field refers to a field in the candidate assigned value fields that has a data type consistent with at least one candidate source field.

[0044] Furthermore, assigning a value to a target object according to the candidate source field, the source object, the first metadata of the source object and the second metadata of the target object may be: based on the field name correspondence between the candidate source field and the candidate field to be assigned, performing type conversion on the candidate source field, and assigning the value of the candidate source field after type conversion to the candidate field to be assigned; performing semantic similarity analysis on the first metadata of the source object and the second metadata of the target object, determining similar assignment fields and non-similar assignment fields between the third assignment field and the third available source field; the third available source field refers to other source fields in the source object except the candidate source field; the third assignment field refers to other assignment fields in the target object except the candidate field to be assigned; assigning the value of the third available source field corresponding to the similar assignment field to the similar assignment field, and adding a no assignment data description to the non-similar assignment field.

[0045] In this embodiment, the third valued field refers to a field in the target object that has not passed the field name consistency check. The third available source field refers to a field in the source object that has not passed the field name consistency check. A similar valued field refers to a field in the third valued field that has semantic similarity with the third available field. A non-similar field refers to a field in the third valued field that has no semantic similarity with the third available field.

[0046] Furthermore, assigning a value to the target object according to 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 can be: based on the field name correspondence between the first available source field and the first value assignment field, directly assigning the value of the first available source field to the first value assignment field; based on the field name correspondence between the second available source field and the second value assignment field, performing type conversion on the second available source field, and assigning the value of the second available source field after type conversion to the second value assignment field; the second available source field refers to other source fields in the candidate source field except the first available source field; the second value assignment field refers to other fields to be assigned in the candidate fields to be assigned except the first value assignment field; assigning a third value assignment field to the target object according to the third available source field, the first metadata of the source object and the second metadata of the target object; the third available source field refers to other source fields in the source object except the candidate source field; the third value assignment field refers to other assignment fields in the target object except the candidate fields to be assigned.

[0047] Furthermore, assigning a value to the third value assignment field of the target object according to the third available source field, the first metadata of the source object and the second metadata of the target object can be: performing a semantic similarity analysis on the first metadata of the source object and the second metadata of the target object to determine similar value assignment fields and non-similar value assignment fields in the third value assignment field that are related to the third available source field; assigning the value of the third available source field corresponding to the similar value assignment field to the similar value assignment field, and adding a no value assignment data description to the non-similar value assignment field.

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

[0049] S130. When it is identified that both the field name consistency check and the data type consistency check have failed, a 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; the metadata includes field meaning, field comment and field annotation.

[0050] In this embodiment, metadata refers to data used to describe field data, usually including the meaning, annotations and comments of field data. Semantic similarity analysis refers to analyzing the metadata of the source object and the object to be assigned to evaluate the similarity between them at the semantic level; this usually relies on natural language processing and machine learning technology 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 purpose of the field in the system or business. Field annotation refers to a brief 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 purpose of the field when querying the database; field annotations are usually stored as part of the metadata in the database table structure. Field annotations refer to providing additional information for fields in the code, usually parsed and used in frameworks or tools; field annotations are not only descriptions of fields, but may also include some configuration or constraints (such as field validation, mapping relationships, etc.).

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

[0052] In an optional implementation, after the assignment of 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 subsequently assigned, the assignment relationship can be directly used, which helps to improve the efficiency of the assignment.

[0053] The embodiment of the present application obtains the source object from the source business system and the object to be assigned from the target business system when an object assignment instruction is identified; the source business system and the target business system are different systems for processing the same target business; the source object and the object to be assigned are checked for field name consistency and data type consistency; when it is identified that both the field name consistency check and the data type consistency check have failed, a 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; the object to be assigned is assigned based on 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 This is a flow chart of a method for assigning cross-system data objects provided in accordance with the second embodiment of the present application. Based on the technical solutions of the above embodiments, this embodiment refines "assigning the object to be assigned according to the semantic similarity analysis results and the source object" into "if there are no matching fields in the semantic similarity analysis results, determining the unassignable fields of the object to be assigned, and obtaining 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; assigning the unassignable fields according to the first knowledge graph and the second knowledge graph". It should be noted that for the parts not described in detail in the embodiments of the present application, please refer to the relevant statements of other embodiments. Figure 2 As shown, the method includes:

[0056] S210 . When an object assignment instruction is identified, 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.

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

[0058] S230: When it is identified that both the field name consistency check and the data type consistency check have failed, a 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.

[0059] S240. If there are no matching fields in the semantic similarity analysis results, 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 field refers to a field in the object to be assigned that has not passed the semantic similarity analysis and cannot be directly assigned using the source object. A 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 and the relationships between the object to be assigned; illustratively, the first knowledge graph of the source business system may contain the relationship between "user name" and "user name", while the second knowledge graph of the target business system describes the relationship between "user name" and "user ID".

[0061] Optionally, if there are matching fields in the semantic similarity analysis results, 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 are determined; based on the correspondence between the assignable source fields and the assignable fields, the value of the assignable source field is assigned to the assignable field of the object to be assigned.

[0062] In this embodiment, the matchable field refers to a field that can match the semantic similarity between the source object and the object to be assigned. The assignable source field refers to a field in the source object that can be assigned to the object to be assigned through semantic similarity analysis. The assignable field refers to a field in the object to be assigned that matches the semantic similarity with the source object. The correspondence between the assignable source field and the field to be assigned refers to the field correspondence between the assignable source field and the assignable field with the same semantic similarity.

[0063] S250. Assign values ​​to the fields that cannot be assigned values ​​according to the first knowledge graph and the second knowledge graph.

[0064] Optionally, based on the domain ontology library of the target business, a field semantic relationship mapping is established for the first knowledge graph and the second knowledge graph to obtain a semantic relationship graph; using the unassignable field as an index, the target source field corresponding to the unassignable field is searched from the semantic relationship graph, and the value of the target source field is assigned to the unassignable field.

[0065] In this embodiment, the domain ontology library refers to structured data that describes the knowledge and concepts of a specific field (such as finance, medical care, education, etc.); it includes all core concepts, entities, attributes and the relationships between them in the field, and provides detailed definitions of these concepts. Field semantic relationship mapping refers to establishing semantic associations between fields in the source system and the target system by comparing their meanings and contexts; through this mapping, fields with similar or identical meanings in the two systems can be found. The semantic relationship graph is a graphical structure formed by establishing semantic relationships between fields in the source business system and the target business system; it shows the semantic connection between fields and how to migrate or convert data 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 the two fields can be converted 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 a field that can provide data for fields that cannot be assigned values; for example, if the "customer email" field of the source system has a semantic relationship mapping with the "user email" field of the target system, then the "customer email" field of the source system can provide a value for the "user email" field in the target system.

[0066] It can be understood that the semantic relationship mapping between the source system and the target system is established by using the target business domain ontology library and combining the field information in the source system and the target system. By comparing the domain ontology libraries of the two, determine which fields are similar or equivalent; based on the mapping results, build a semantic relationship map to graphically display similar fields in the source system and the target system to clarify the relationship between them; through the semantic relationship map, use the unassignable field as an index to find the target source field that can provide a value for it. If the relevant target source field is found, its value can be assigned to the unassignable field; once the corresponding target source field is found, the system can pass the value in the target source field to the unassignable field to complete the filling or conversion of the data. This process helps the system solve the problem of field mismatch when assigning data across systems, so that data can be smoothly converted and assigned.

[0067] In an optional implementation, in the process of using the source object to assign a value to the object to be assigned, the source object and the object to be assigned may be checked for the existence of complex fields; if a complex field exists and there is no historical assignment statement for the complex field, the complex field will not be assigned.

[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 contains complex structures such as nested objects, arrays, lists, or fields with multiple attributes combined together; for example, an "address" field may include sub-fields such as "street", "city", and "postal code", or an "order" field may include multiple sub-fields such as "order ID", "product list", and "total amount". Complex field existence check 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] The embodiment of the present application obtains the source object from the source business system and the object to be assigned from the target business system when an object assignment instruction is identified; the source business system and the target business system are different systems for processing the same target business; the source object and the object to be assigned are subjected to field name consistency check and data type consistency check; when it is identified that both the field name consistency check and the data type consistency check have not passed, a 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; if there is no matching field in the semantic similarity analysis result, the unassignable field of the object to be assigned is 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; the unassignable field is assigned according to the first knowledge graph and the second knowledge graph. The above technical solution, when the semantic similarity analysis cannot assign a value to the unassignable field of the object to be assigned, can further analyze the unassignable field by introducing the combined use of the knowledge graph, which helps to ensure the efficiency and accuracy of the assignment.

[0070] Embodiment 3

[0071] Figure 3 This is a schematic diagram of the structure of a cross-system data object assignment device provided in accordance with the third embodiment of the present application, which can be applied to the case where cross-system data are assigned to each other. The cross-system data object assignment device can be implemented in the form of hardware and / or software. The cross-system data object assignment device can be configured in a computer device, such as an object assignment development plug-in. Figure 3 As shown, the device comprises:

[0072] The object acquisition module 310 is used to acquire the source object from the source business system and the object to be assigned from the target business system when an object assignment instruction is identified; the source business system and the target business system are different systems for processing the same target business;

[0073] The object verification module 320 is used to perform field name consistency verification and data type consistency verification on the source object and the object to be assigned;

[0074] The semantic analysis module 330 is used to perform semantic similarity analysis on the metadata of the source object and the object to be assigned when it is identified that both the field name consistency check and the data type consistency check have failed, and obtain a semantic similarity analysis result; the metadata includes field meaning, field comment and field annotation;

[0075] The object assignment module 340 is used to assign a value to the object to be assigned according to the semantic similarity analysis result and the source object.

[0076] The embodiment of the present application obtains the source object from the source business system and the object to be assigned from the target business system when an object assignment instruction is identified; the source business system and the target business system are different systems for processing the same target business; the source object and the object to be assigned are checked for field name consistency and data type consistency; when it is identified that both the field name consistency check and the data type consistency check have failed, a 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; the object to be assigned is assigned based on 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.

[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 matching fields in the semantic similarity analysis result, and to acquire the first knowledge graph of the source object from the source business system, and to acquire the second knowledge graph of the object to be assigned from the target business system;

[0079] The first field assignment unit is used to assign values ​​to fields that cannot be assigned values ​​according to the first knowledge graph and the second knowledge graph.

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

[0081] According to the domain ontology library of the target business, a field semantic relationship mapping is established between the first knowledge graph and the second knowledge graph to obtain a semantic relationship graph;

[0082] Using the unassignable field as an index, search the semantic relationship graph for the target source field corresponding to the unassignable field, and assign the value of the target source field to the unassignable field.

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

[0084] If there are matching 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 corresponding relationship between the assignable source fields and the fields to be assigned;

[0085] Based on the corresponding relationship between the assignable source field and the field to be assigned, the value of the assignable source field is assigned to the field to be assigned.

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

[0087] After obtaining the source object from the source business system and the object to be assigned from the target business system, the historical assignment statements are searched 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, the historical assignment statement and the source object are used to assign the object to be assigned;

[0089] If there is no historical assignment statement between the source object and the object to be assigned, a field name consistency check and a data type consistency check are performed 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 where a field that has passed the field name consistency check is identified, candidate source fields that have passed the field name consistency check in the source object and candidate to-be-assigned fields that have passed the field name consistency check in the to-be-assigned object are determined;

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

[0093] 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 verification result.

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

[0095] According to an embodiment 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 44 is a schematic diagram of the structure of an electronic device 410 that implements the cross-system data object assignment method of the embodiment of the present application. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, 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 processing, 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 examples and are not intended to limit the implementation of the present application described and / or required herein.

[0098] like Figure 4 As shown, the electronic device 410 includes at least one processor 411, and a memory connected to the at least one processor 411 in communication, such as a read-only memory (ROM) 412, a random access memory (RAM) 413, etc., wherein the memory stores a computer program that can be executed by at least one processor, and 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 to the random access memory (RAM) 413. In RAM413, various programs and data required for the operation of the electronic device 410 can also be stored. The processor 411, ROM412 and RAM413 are connected to each other via a bus 414. An 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 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 may be a variety of general and / or special 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 special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 411 executes the various methods and processes described above, such as the assignment method of cross-system data objects.

[0101] In some embodiments, the method for assigning a value to a cross-system data object may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 418. In some embodiments, part or all of the computer program may be loaded and / or installed on 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 a value to a cross-system data object described above may be performed. Alternatively, in other embodiments, the processor 411 may be configured as the method for assigning a value to a cross-system data object in any other appropriate manner (e.g., by means of firmware).

[0102] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0103] 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 a processor of a general-purpose computer, a special-purpose computer, or other programmable cross-system data object assignment device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine as a stand-alone software package and partially on a remote machine, or entirely on a remote machine or server.

[0104] In the context of the present application, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, device, or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0105] To provide interaction with a user, the systems and techniques described herein may 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 trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0106] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations 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 may be interconnected by any form or medium of digital data communication (e.g., 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 remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0108] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this application can be executed in parallel, sequentially or in different orders, as long as the expected results of the technical solution of this application can be achieved, and this document is not limited here.

[0109] The above specific implementations do not constitute a limitation on the protection scope of this application. It should be understood by those skilled in the art 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 principles of this application should be included in the protection scope of this application.

Claims

1. A method for assigning values ​​to cross-system data objects, characterized in that: Applied to object assignment development plug-in; the method comprises: When an object assignment instruction is identified, 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; Performing field name consistency check and data type consistency check on the source object and the object to be assigned; When it is identified that both the field name consistency check and the data type consistency check have failed, a 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; the metadata includes field meaning, field comment and field annotation; The object to be assigned is assigned a value according to the semantic similarity analysis result and the source object.

2. 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 is no matching field in the semantic similarity analysis result, determining the unassignable field of the object to be assigned, and obtaining the first knowledge graph of the source object from the source business system, and obtaining the second knowledge graph of the object to be assigned from the target business system; According to the first knowledge graph and the second knowledge graph, the unassignable field is assigned a value.

3. The method according to claim 2, characterized in that Assigning a value to the unassignable field according to the source object, the first knowledge graph, and the second knowledge graph, including: According to the domain ontology library of the target business, a field semantic relationship mapping is established for the first knowledge graph and the second knowledge graph to obtain a semantic relationship graph; Using the unassignable field as an index, searching the semantic relationship graph for a target source field corresponding to the unassignable field, and assigning the value of the target source field to the unassignable field.

4. 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, determining 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 field and the assignable field, the value of the assignable source field is assigned to the assignable field of the object to be assigned.

5. The method according to claim 1, characterized in that After obtaining the source object from the source business system and obtaining the object to be assigned from the target business system, the method further includes: Using the source object and the object to be assigned as indexes, searching for historical assignment statements; If there is a historical assignment statement between the source object and the object to be assigned, assign the object to be assigned using the historical assignment statement and the source object; If there is no historical assignment statement between the source object and the object to be assigned, a field name consistency check and a data type consistency check are performed on the fields for which there is no historical assignment statement between the source object and the object to be assigned.

6. The method according to claim 1, characterized in that The method further comprises: In the case of identifying that there is a field that passes the field name consistency check, determining a candidate source field that passes the field name consistency check in the source object and a candidate to-be-assigned field that passes the field name consistency check in the to-be-assigned object; Performing a data type consistency check on the candidate source field and the candidate to-be-assigned field to obtain a data type check result; The object to be assigned is assigned a value according to the source object, the first metadata of the source object, the second metadata of the object to be assigned a value, and the data type verification result.

7. A device for assigning values ​​to cross-system data objects, characterized in that: Configured in object assignment development plug-in; the device includes: An object acquisition module is used to acquire 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 identified; the source business system and the target business system are different systems for processing the same target business; An object verification module is used to perform field name consistency verification and data type consistency verification on the source object and the object to be assigned; A semantic analysis module, for performing semantic similarity analysis on the metadata of the source object and the object to be assigned when it is identified that both the field name consistency check and the data type consistency check have failed, to obtain a semantic similarity analysis result; the metadata includes field meaning, field comment and field annotation; The object assignment module is used to assign a value to the object to be assigned according to the semantic similarity analysis result and the source object.

8. An electronic device, characterized in that: include: one or more processors; A memory for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the cross-system data object assignment method as described in any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method for assigning a value to a cross-system data object as described in any one of claims 1 to 6 is implemented.

10. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the computer program implements the method for assigning a value to a cross-system data object according to any one of claims 1 to 6.

Images