Data processing method and device, electronic equipment, medium and program product

Abstract

Embodiments of the present application disclose a data processing method and device, electronic equipment, medium and program product, which are applied to the technical field of computers. The method comprises the following steps: obtaining a first object description file of a first business object structure, obtaining a second object description file of a second business object structure, constructing at least one description data pair based on N first description data and M second description data, comparing the first description data and the second description data in each description data pair respectively, and determining difference description data between the first business object and the second business object according to a comparison result. By using the embodiments of the present application, the comparison accuracy of the object description file can be improved, and the accuracy of the obtained difference description data is further improved.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a data processing method, apparatus, electronic device, medium, and program product. Background Technology

[0002] Currently, it's possible to compare the business logic of two business objects to identify their differences. For example, the business logic of a web payment service and a mini-program payment service can be compared to determine the differences in their execution. Typically, this comparison involves obtaining the business logic description documents for both objects and comparing them line-by-line within one document. However, this method suffers from a fixed data format for each comparison, lacking flexibility and resulting in inaccurate results. Summary of the Invention

[0003] This application provides a data processing method, apparatus, electronic device, medium, and program product that can improve the flexibility of comparing object description files and improve the accuracy of comparison results.

[0004] On one hand, embodiments of this application provide a data processing method, the method comprising:

[0005] Obtain the structured first object description file of the first business object; the first object description file includes N structured first description data of the first business object; N is a positive integer;

[0006] Obtain the structured second object description file of the second business object; the second object description file includes M structured second description data of the second business object; M is a positive integer;

[0007] At least one description data pair is constructed based on N first description data and M second description data; any description data pair includes first description data and second description data that are similar in description.

[0008] The first and second description data in each description data pair are compared, and the difference description data between the first business object and the second business object is determined based on the comparison results.

[0009] On one hand, embodiments of this application provide a data processing apparatus, the apparatus comprising:

[0010] The acquisition module is used to acquire a structured first object description file of the first business object; the first object description file includes N structured first description data of the first business object; N is a positive integer;

[0011] The acquisition module is also used to acquire a structured second object description file for the second business object; the second object description file includes M structured second description data for the second business object; M is a positive integer;

[0012] The processing module is used to construct at least one description data pair based on N first description data and M second description data; any description data pair includes first description data and second description data that are similar in description.

[0013] The processing module is also used to compare the first description data and the second description data in each description data pair, and determine the difference description data between the first business object and the second business object based on the comparison results.

[0014] On one hand, embodiments of this application provide an electronic device including a processor and a memory, wherein the memory is used to store a computer program, the computer program including program instructions, and the processor is configured to invoke the program instructions to execute some or all of the steps in the above method.

[0015] On one hand, embodiments of this application provide a computer-readable storage medium storing a computer program, the computer program including program instructions, which, when executed by a processor, are used to perform some or all of the steps in the above-described method.

[0016] Accordingly, according to one aspect of this application, a computer program product or computer program is provided, comprising program instructions stored in a computer-readable storage medium. A processor of a computer device reads the program instructions from the computer-readable storage medium and executes the program instructions, causing the computer device to perform the data processing method provided above.

[0017] In this embodiment, a structured first object description file for a first business object and a structured second object description file for a second business object can be obtained. At least one description data pair is constructed based on N first description data and M second description data. The first and second description data in each description data pair are compared, and the difference description data between the first and second business objects is determined based on the comparison results. This method allows for the first construction of similar description data pairs based on the structured first and second object description files. These pairs are the description data to be compared, determined from the two object description files. The comparison of these pairs then identifies the difference description data, thereby improving the flexibility of object description file comparison, reducing the workload, and increasing the accuracy of the comparison results. This, in turn, improves the accuracy of the difference description data obtained based on the comparison results. Attached Figure Description

[0018] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 A schematic diagram of an application architecture provided for an embodiment of this application;

[0020] Figure 2 A flowchart illustrating a data processing method provided in an embodiment of this application;

[0021] Figure 3 This application provides a schematic diagram of a scenario for constructing descriptive data pairs.

[0022] Figure 4 A schematic diagram of a scenario for determining a first description module is provided in an embodiment of this application;

[0023] Figure 5 A flowchart illustrating a data processing method provided in an embodiment of this application;

[0024] Figure 6 This application provides a schematic diagram of a scenario for constructing descriptive data pairs.

[0025] Figure 7 This application provides a schematic diagram illustrating a scenario where the order of description changes.

[0026] Figure 8 A schematic diagram illustrating a comparison scenario of data pairs provided in an embodiment of this application;

[0027] Figure 9a A schematic diagram illustrating a data comparison scenario provided in an embodiment of this application;

[0028] Figure 9b A schematic diagram illustrating a data comparison scenario provided in an embodiment of this application;

[0029] Figure 9c A schematic diagram illustrating a data comparison scenario provided in an embodiment of this application;

[0030] Figure 9d A schematic diagram illustrating a data comparison scenario provided in an embodiment of this application;

[0031] Figure 10 A schematic diagram illustrating a conceptual model provided for an embodiment of this application;

[0032] Figure 11a A schematic diagram illustrating a data comparison scenario provided in an embodiment of this application;

[0033] Figure 11b A schematic diagram illustrating a data comparison scenario provided in an embodiment of this application;

[0034] Figure 11c A schematic diagram illustrating a data comparison scenario provided in an embodiment of this application;

[0035] Figure 12 This is a schematic diagram of the structure of a data processing device provided in an embodiment of this application;

[0036] Figure 13 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0037] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0038] The data processing method proposed in this application is implemented in an electronic device, which can be a server or a terminal. The server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. The terminal can be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, voice interaction device, smart home appliance, vehicle terminal, aircraft, etc., but is not limited to these.

[0039] In some embodiments, see Figure 1 , Figure 1 This is a schematic diagram of an application architecture provided for an embodiment of this application, through which the data processing method proposed in this application can be executed. For example... Figure 1As shown, the electronic device can acquire N structured first description data points of a first business object and M structured second description data points of a second business object. Based on these N first description data points and M second description data points, it constructs at least one description data pair. This description data pair includes first and second description data points that need to be compared and are similar in description. Each description data pair is then compared to determine the difference description data between the first and second business objects. Subsequently, the electronic device can display the difference description data in a display method that matches the difference description data, allowing relevant business personnel to view it intuitively. The electronic device may also include a trained data processing model, which implements the construction of the aforementioned description data pairs.

[0040] Understandable Figure 1 This is merely an illustrative representation of a possible application architecture for the technical solution of this application, and does not limit the specific architecture of the technical solution of this application. That is, the technical solution of this application may also provide other forms of application architecture.

[0041] Optionally, in some embodiments, the electronic device can execute the data processing method according to actual business needs to improve the accuracy of the comparison results for the description files. The technical solution of this application can be applied to any scenario of comparing differences between two business objects. That is, the electronic device can obtain a first business object and a second business object to be compared, and respectively obtain the corresponding first object description file and second object description file. The first object description file and the second object description file are structured object description files generated according to the same description rules. A description data pair is constructed based on the first object description file and the second object description file. The first description data and the second description data in the description data pair are compared to obtain the difference description data, thereby improving the flexibility and efficiency of the comparison. Subsequently, the difference business logic between the two business objects can also be determined through the difference description data.

[0042] Optionally, the data involved in this application, such as the first object description file and the second object description file, can be stored in a database or in a blockchain. This application does not limit the storage of such data through a blockchain distributed system.

[0043] It is understood that the above scenarios are merely examples and do not constitute a limitation on the application scenarios of the technical solutions provided in the embodiments of this application. The technical solutions of this application can also be applied to other scenarios. For example, as those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0044] Based on the foregoing description, this application proposes a data processing method that can be executed by the aforementioned electronic device. Please refer to... Figure 2 , Figure 2 This is a flowchart illustrating a data processing method provided in an embodiment of this application. Figure 2 As shown, the data processing method of this application embodiment may include the following flow:

[0045] S201. Obtain the first object description file of the first business object structure.

[0046] In some embodiments, the first object description file includes N structured first description data of the first business object; N is a positive integer. The first business object can be an object of any business type or business scenario (also known as a business use case). For example, it can be a program use case, such as a payment application; or it can be a functional use case in a program use case, such as a payment use case in a payment application; or it can be a specific sub-functional use case in a functional use case, such as a web payment use case in a payment use case (representing calling the associated payment function on a webpage); there is no limitation on the first business object here.

[0047] In some embodiments, the N first description data in the first object description file are description data composed of natural language, such as text, numbers, and English letters. The first object description file is used to describe the business logic of the first business object during execution using natural language. For example, if the first business object is a web payment use case, the first object description file can be used to describe the business logic of that web payment use case during execution, such as under what conditions web payment is triggered, how to interact with the backend to call the corresponding payment interface, etc.

[0048] In some embodiments, the first object description file is an object description file constructed by relevant business personnel for a first business object according to specified description rules. These specified description rules indicate that the business logic of the first business object is represented using the same language form and description structure. The same language form means that the natural language and description format used to express the same business logic or business information are identical. For example, even in different locations within the same object description file or in different object description files, when representing the business logic of "feedback error information," the corresponding description data is always specified as "feedback error information," and not related descriptions such as "error information feedback." Similarly, when representing the business logic of "first verify the validity of the user account, then verify the validity of the user's entered information," the corresponding description data is specified as "1.1 Verify the validity of the user account; 1.2 Verify the validity of the user's entered information," and not related descriptions such as "1.1 Verify the validity of the user's entered information; 1.2 Verify the validity of the user account." In the object description file, the detailed content contained in an object information unit, step, or sub-step can be called supplementary constraints; these supplementary constraints can include detailed business rules or business fields, etc. For example, fields representing "object description file name" or "version information". Furthermore, when representing business information in the "version information" field according to specified description rules, the corresponding description data is always defined as "v version number (update time)", and the update time format is "year-month-day hour:minute:second", without any descriptions such as "update time (v version number)".

[0049] The same descriptive structure indicates that the logical structure and order used when constructing a complete business logic are identical. For example, the logical order can be reflected through steps, such as indicating that a certain descriptive data corresponds to step 1 or 2, meaning there is a descriptive order between steps. Similarly, the logical order under a step can be reflected through sub-steps, such as indicating that a certain descriptive data corresponds to step 1.1 or 1.2, meaning there is a descriptive order between sub-steps. Furthermore, when describing the specific content under an object information unit, step, or sub-step, corresponding rules and fields can be set, such as indicating which rule or field under step 1 a certain descriptive data corresponds to (e.g., the call data packet field under step 1). For example, the descriptive structure may predefine the fields existing in the supplementary constraints of modules or steps, or set the order of fields; for example, if there are fields such as version information, system, and executor, the field sorting order may be "system," "version information," etc., or sorted alphabetically by the first letter of the field name.

[0050] Therefore, N structured first description data can be constructed based on the aforementioned specified description rules. In other words, the construction and generation process of the object description file includes the structuring of description data. Each first description data represents a structured data set with a structured identifier. This identifier indicates the type (also known as the description level) or order of the first description data. For example, a step represents description data of a certain type (description level), and steps 1 and 2 are sequential and represent description data of the same type (same description level). Similarly, a sub-step represents description data of a certain type, and steps 1.1 and 1.2 represent description data of the same type. A field represents description data of a certain type, and field 1 in step 1 and field 2 in step 2 represent description data of the same type. Subsequently, when storing the first object business file, the description data and structured identifier can be stored in a structured manner. Compared to generating a description document corresponding to the first object description file and directly storing the description document, this allows for more flexible storage and reduces storage memory requirements.

[0051] S202. Obtain the structured second object description file of the second business object.

[0052] In some embodiments, the description and principles of the second object description file can refer to the above explanation of the first object description file, that is, it can be an object description file constructed according to the specified description rules. Therefore, the first object description file and the second object description file to be compared have the same structure and the same description content corresponding to the same business logic. The second object description file includes M second description data structured for the second business object; M is a positive integer.

[0053] In some embodiments, the second business object can be an object of any business type or business scenario. This second business object is typically an object related to the first business object. For example, it can be an object of a different version from the first business object; for instance, if the first business object is version 1.0 of the web payment use case, the second business object can be version 2.0 of the web payment use case. Alternatively, it can be an object with a similar function to the first business object; for example, if the first business object is a web payment use case, the second business object can be a QR code payment use case (representing calling the associated payment function by scanning a QR code), etc. No limitations are imposed on the second business object here.

[0054] In some embodiments, the electronic device may obtain the corresponding first object description file and second object description file when it detects a comparison request generated by relevant business personnel based on a first business object and a second business object; or it may obtain the object description file of the business object before and after the update when it detects that a version update of a certain business object is detected and receives a test request for the business object. For example, in this case, the first business object may represent the business object before the update and the second business object may represent the business object after the update.

[0055] S203. Construct at least one description data pair based on N first description data and M second description data.

[0056] In some embodiments, constructing at least one description data pair based on N first description data and M second description data can be achieved by sequentially constructing a description data pair with each first description data and each second description data.

[0057] In some embodiments, the N first description data and M second description data each include description data at different description levels, such as description data representing steps or description data representing sub-steps. The description level of the description data can be determined based on structured identifiers. Specifically, during the comparison, the first description data and second description data at the same description level can also be compared. Therefore, constructing at least one description data pair based on the N first description data and M second description data can be achieved by sequentially constructing a description data pair between each first description data and the second description data at the same description level, according to the structured identifier of each first description data and the structured identifier of each second description data.

[0058] For example, such as Figure 3 As shown, Figure 3 This is a schematic diagram of a scenario for constructing description data pairs according to an embodiment of this application; wherein, N first description data pairs include description data A, description data B and description data C, and M second description data pairs include description data D and description data E; description data A, description data C and description data D are at the same description level, and description data B and description data E are at the same description level; therefore, the constructed description data pairs include [description data A, description data D], [description data C, description data D], and [description data B, description data E].

[0059] In some embodiments, a first object description file may include multiple first description modules, and N first description data belong to the description data within the multiple first description modules. A first description module may correspond to a step or object information unit, and all first description data associated with that step or object information unit are all description data under the corresponding first description module; the first description data associated with that step or object information unit may be determined by a structured identifier of the first description data. For example, such as... Figure 4 As shown, Figure 4 This is a schematic diagram of a scenario for determining a first description module provided in an embodiment of this application; wherein, N structured identifiers of the first description data indicate field 1 under object information unit 1 corresponding to description data 1, and indicate field 2 under step 1 corresponding to description data 2, step 1.1 under step 1 corresponding to description data 3, and step 2 under step 1.1 corresponding to description data 4; and indicate step 2 corresponding to description data 5 and step 2.1 under step 2; therefore, three first description modules can be obtained: one is the first description module corresponding to object information unit 1, and includes description data 1; one is the first description module corresponding to step 1, and includes description data 2-4; and one is the first description module corresponding to step 2, and includes description data 5-6.

[0060] In some embodiments, since the first description data in different first description modules are different, the specific business logic described by the first description module for the first business object in the first object description file can also be different. For example, one first description module may represent the business logic for triggering the web payment function, and another first description module may represent the business logic for interacting with the backend to call the corresponding payment interface, etc. Correspondingly, the second object description file may contain multiple second description modules, and M pieces of second description data belong to the description data in multiple second description modules. The specific business logic described by each second description module for the second business object can be different. For relevant descriptions and principles of the second description modules, please refer to the above explanation of the first description modules. Further details will not be repeated here.

[0061] Therefore, constructing at least one description data pair based on N first description data and M second description data can be achieved by: determining the business logic described by each first description module based on the first description data in each first description module, and determining the business logic described by each second description module based on the second description data in each second description module; and constructing at least one description data pair based on the business logic described by each first description module and the business logic described by each second description module. The determination of the business logic described by the first or second description module can be specified by relevant business personnel, determined by business keywords contained in the description data pair of the corresponding description module, or determined by model prediction. The specific process of determining the described business logic can be found in the relevant descriptions in the following embodiments.

[0062] In some embodiments, constructing at least one description data pair based on the business logic described by each first description module and the business logic described by each second description module can specifically involve combining first and second description modules with the same business logic to obtain at least one description module combination; any description module includes a first description module and a second description module with the same business logic; and constructing at least one description data pair based on the at least one description module combination. Wherein, any constructed description data pair includes first and second description data with similar descriptions. This similarity indicates that the business logic of the first description module to which the first description data belongs and the second description module to which the second description data belongs is the same.

[0063] In some embodiments, constructing at least one description data pair based on at least one description module combination can specifically involve constructing a description data pair by sequentially combining each first description data in the description module combination with each second description data. For example, if the description module combination 1 includes description data 1 and description data 2 as first description data and description data 3 as second description data, then the constructed description data pair is [description data 1, description data 3] and [description data 2, description data 3].

[0064] Furthermore, since both the first and second description data have description levels, when constructing at least one description data pair based on at least one description module combination, the specific method may be to construct a description data pair by sequentially combining each first description data in the description module combination with each second description data at the same description level. For example, if the first description data included in description module combination 1 are description data 1, description data 2, and description data 3, and the second description data included are description data 4 and description data 5, and description data 1, description data 2, and description data 4 are at the same description level (e.g., all are steps), and description data 3 and description data 5 are at the same description level (e.g., both are sub-steps), then the constructed description data pairs are [description data 1, description data 4], [description data 2, description data 4], and [description data 3, description data 5].

[0065] It is understandable that first and second description data that may be successfully compared only exist within the first and second description modules that share the same business logic. For example, comparing the description data "verify the validity of the request" in isolation is usually meaningless, as this description data may appear in one or more first (or second) description modules. However, comparisons are meaningful only when they occur within the first and second description modules that share the same business logic. Only when identical first and second description data appear can they represent the same business meaning and thus be successfully compared. The resulting pairs of similar description data represent first and second description data that are practically likely to be successfully compared. Compared to directly comparing each first and second description data, this approach improves the reliability of the comparison results, allows for initial screening of the data to be compared, reduces the workload, and increases efficiency.

[0066] S204. Compare the first and second description data in each description data pair, and determine the difference description data between the first business object and the second business object based on the comparison results.

[0067] In some embodiments, the electronic device can compare the first and second descriptive data in each descriptive data pair separately. If the first and second descriptive data in a descriptive data pair are identical, the comparison is considered successful. The comparison result indicates the successfully compared first and second descriptive data. Therefore, determining the difference descriptive data between the first business object and the second business object based on the comparison result can be achieved by identifying the first and second descriptive data (excluding the successfully compared first and second descriptive data) from N first descriptive data and M second descriptive data as the difference descriptive data. This makes the difference descriptive data obtained based on the comparison result more accurate and reliable. The descriptive data pairs have a corresponding order during construction, and the electronic device compares the descriptive data pairs sequentially based on this order. For example, description data 1 is paired with description data 3 and description data 4 in sequence to form a description data pair, and description data 2 is paired with description data 3 and description data 4 in sequence to form a description data pair; the description order of description data 1 and description data 2 is that description data 1 comes before description data 2, and the description order of description data 3 and description data 4 is that description data 3 comes before description data 4; then the comparison order can be [description data 1, description data 3], [description data 1, description data 4], [description data 2, description data 3], [description data 2, description data 4].

[0068] In some embodiments, at least one description data pair includes a first description data pair and a second description data pair. Specifically, comparing the first description data and the second description data in each description data pair can be as follows: comparing the first description data pair; if the current comparison of the first and second description data fails, then comparing the second description data pair; if the comparison succeeds, then determining whether the second description data pair contains the successfully compared first or second description data; if it contains it, then skipping the second description data pair and not performing a comparison; if it does not contain it, then comparing the second description data pair.

[0069] In some embodiments, the difference business logic between the first business object and the second business object can be determined based on the difference description data, and the difference business logic can be verified for the first or second business object. This difference business logic enables relevant business personnel to quickly understand the change characteristics and difference details of the first and second business objects. For example, if the first business object is the business object before the version update and the second business object is the business object after the version update, after obtaining the difference business logic between the first and second business objects, the difference business logic can be verified for the second business object to test whether the updated business object has been updated correctly.

[0070] In this embodiment, a structured first object description file for a first business object and a structured second object description file for a second business object can be obtained. At least one description data pair is constructed based on N first description data and M second description data. The first and second description data in each description data pair are compared, and the difference description data between the first and second business objects is determined based on the comparison results. This method allows for the first construction of similar description data pairs based on the structured first and second object description files. These pairs are the description data to be compared, determined from the two object description files. The comparison of these pairs then identifies the difference description data, thereby improving the flexibility of object description file comparison, reducing the workload, and increasing the accuracy of the comparison results. This, in turn, improves the accuracy of the difference description data obtained based on the comparison results.

[0071] Please see Figure 5 , Figure 5 This is a flowchart illustrating a data processing method provided in an embodiment of this application. This method can be executed by the aforementioned electronic device. Figure 5 As shown, the data processing method in this embodiment may include the following flow:

[0072] S501. Obtain the first object description file, which is a structured representation of the first business object. The specific implementation of step S501 can be found in the relevant descriptions of the above embodiments, and will not be repeated here.

[0073] S502. Obtain the structured second object description file of the second business object.

[0074] In some embodiments, the specific description in the second object description file can be the same as that in the first object description file. Both the first and second object description files can be constructed within a unified business object management system. This system can describe the object requirements (i.e., object business logic) of business objects in a structured form. Within the system, corresponding description rules can be generated according to the principles and requirements of UML (Unified Modeling Language), and business objects can be described based on these rules to generate structured object description files. For example, in this object description file, the business logic can be basically divided into sections such as "introduction-request-validation-response-feedback," and described in the form of units or steps. Detailed requirements and descriptions for business objects can be described in the form of supplementary constraints within the units or steps, such as fields, rules, and designs. All generated object description files can be displayed using the same display method and layout. Therefore, the first and second business objects to be compared can be selected within the business object management system, and the differences between them can be determined using the corresponding first and second object description files.

[0075] S503. Obtain multiple first description modules contained in the first object description file, and obtain multiple second description modules contained in the second object description file.

[0076] In some embodiments, multiple first description modules contained in the first object description file can be determined based on the structured identifier of each first description data in the first object description file. The first description data in each first description module are associated and correspond to the same business logic. A first description module may contain all description data under an object information unit or all description data under a step in the first object description file. Correspondingly, multiple second description modules contained in the second object description file can be determined based on the structured identifier of each second description data in the second object description file. The second description data in each second description module are associated and correspond to the same business logic. A second description module may contain all description data under an object information unit or all description data under a step in the second object description file.

[0077] S504. Based on the business logic described by each first description module and the business logic described by each second description module, construct at least one description data pair for N first description data and M second description data.

[0078] In some embodiments, the electronic device may determine the business logic specifically described by each first description module for a first business object and the business logic specifically described by each second description module for a second business object, and determine at least one set of first description data and second description data with similar descriptions from N first description data and M second description data according to the business logic of each first description module and the business logic of each second description module, and construct the at least one set of first description data and second description data into at least one description data pair.

[0079] In some embodiments, the process and principle by which the electronic device determines the business logic of each first description module and each second description module are the same. Here, we take one description module (target description module) as an example for illustration. Specifically, this can involve obtaining a set of business keywords for different business logics, matching all description data in the target description module with each set of business keywords, and determining the business logic corresponding to the set of business keywords containing the most business keywords in all description data as the business logic described by the target description module. The set of business keywords corresponding to these different business logics can be set by relevant business personnel according to the actual application scenario. Alternatively, it can be obtained through a trained data processing model, which predicts the described business logic based on all description data in the target description module. This data processing model is trained on an initial data processing model using sample data (sample description data and business logic labels). Alternatively, it can be specified by relevant business personnel when constructing the corresponding object description file.

[0080] In some embodiments, determining at least one set of similar first and second description data from N first description data and M second description data based on the business logic of each first description module and the business logic of each second description module can be achieved by combining first and second description modules with the same business logic to obtain at least one description module combination, and determining at least one set of similar first and second description data from each description module combination. For example, first description module 1 describes business logic A, first description module 2 describes business logic A, and third description module 3 describes business logic B; second description module 1 describes business logic A, and second description module 2 describes business logic B; therefore, first description module 1 and second description module 1 are combined, first description module 2 and second description module 1 are combined, and first description module 3 and second description module 2 are combined.

[0081] In some embodiments, any one of the at least one combination of description modules is represented as a target combination of description modules. Determining at least one set of first description data and second description data that are similar in description from each combination of description modules may involve determining the first description module in the target combination of description modules as a first comparison module, determining the second description module in the target combination of description modules as a second comparison module, and combining the first description data in the first comparison module and the second description data in the second comparison module to obtain at least one set of first description data and second description data that are similar in description, as at least one pair of description data.

[0082] In some embodiments, each first description data and each second description data has a description hierarchy. Determining at least one set of first and second description data with similar descriptions from each combination of description modules can also involve determining the first description module in the target description module combination as the first comparison module, determining the second description module in the target description module combination as the second comparison module, and sequentially combining the first description data in the first comparison module and the second description data at the same description hierarchy in the second comparison module to obtain at least one set of first and second description data with similar descriptions, serving as at least one description data pair, so that description data at the same description hierarchy can be compared. The description data as fields can exist independently, such as fields located in object information units, or they can belong to supplementary constraints of description data, such as fields located in steps or sub-steps. In this case, when constructing a description data pair containing fields, description data pairs can be constructed for fields in the same position. Furthermore, fields that do not need to be compared can be pre-defined, and in this case, these fields will not be constructed when constructing description data pairs. Further, description data pairs can also be constructed for fields with the same field name in the same position. For example, in the first object description file, the supplementary constraint in step 1 contains field 1, the supplementary constraint in step 1.1 contains field 2, and in the second object description file, the supplementary constraint in step 1.1 contains field 3. Then, only field 2 and field 3 are used to construct a description data pair; or, field 2 and field 3 are used to construct a description data pair only when field 2 and field 3 represent the same field name.

[0083] For example, such as Figure 6 As shown, Figure 6 This application provides a schematic diagram of a scenario for constructing descriptive data pairs; wherein, as shown in the embodiments of this application. Figure 6In (1), let N first description data pairs contain 3 first description modules, where first description modules 1-3 correspond to steps 1-3 respectively; M second description data pairs contain 4 second description modules, where second description modules 1-4 correspond to steps 1-4 respectively; the business logic described by first description module 1-2 is the same as that described by second description module 1-2, and the business logic described by first description module 3 is the same as that described by second description module 3-4; for example... Figure 6 In (2), the determined combination of description modules includes [first description module 1, second description module 1], [first description module 1, second description module 2], [first description module 2, second description module 1], [first description module 2, second description module 2], [first description module 3, second description module 3], [first description module 3, second description module 4]; such as Figure 6 In (3), description data pairs are constructed sequentially according to the same description level. Taking [first description module 1, second description module 1] as an example, the constructed description data pairs include [description data 1.①, description data 2.①], [description data 1.②, description data 2.②], [description data 1.②, description data 2.③], [description data 1.③, description data 2.④], [description data 1.③, description data 2.⑤], [description data 1.④, description data 2.⑥].

[0084] In one possible implementation, constructing at least one description data pair for N first description data and M second description data can also involve calculating the content similarity between the description data contained in each first description module and the description data contained in each second description module, determining the second description module that matches the content of each first description module, combining each first description module and the content-matching second description module to obtain at least one description module combination, and constructing at least one description data pair based on the at least one description module combination. Specifically, determining the second description module that matches the content of each first description module can be done by selecting the second description module with the highest content similarity or a content similarity greater than a preset threshold as the description module that matches the corresponding first description module. For details on how to construct at least one description data pair based on at least one description module combination, please refer to the above description of constructing at least one description data pair.

[0085] S505. Compare the first and second description data in each description data pair respectively.

[0086] In some embodiments, each of the N first description data has a corresponding description order and description priority in the first object description file; correspondingly, each of the M second description data has a corresponding description order in the second object description file. The electronic device may compare each description data pair sequentially according to the description order and description priority of the first description data in each pair. The description order and description priority of the N first description data are defined by the description rules used. Specifically, the description order may be determined by specifying the step (or sub-step) label of the description data; for example, the description order may be step 1, step 2, etc. The description order may also be determined by defining the arrangement order of the description data; for example, the arrangement order of fields under step 1 may be field 1, field 2, etc. The description priority is determined by the description hierarchy; for example, the description priority may be step, sub-step, supplementary constraints under any step (supplementary constraints may be rules, fields, etc. in sequence), supplementary constraints under any step, etc. Alternatively, each description data pair may be compared in other orders. For example, the comparison can be performed according to the construction order of the description data pairs; or it can be based on the order of the first description module. For example, in the first description module corresponding to step 1, the corresponding description data pairs can be compared in the order of step 1 - supplementary constraints of step 1 - step 1.1 - supplementary constraints of step 1.1 - ... - step 2 - ...

[0087] In some embodiments, when comparing each description data pair sequentially, the current description data pair is compared with the previously obtained comparison results to determine whether to skip the comparison process or continue the comparison. Assuming at least one description data pair includes a first description data pair and a second description data pair, comparing the first and second description data in each description data pair sequentially can be done by determining the first description data in the first description data pair as the first comparison data and the second description data in the first description data pair as the second comparison data, comparing the first and second comparison data to obtain a target comparison result. If the target comparison result indicates that the first and second comparison data are the same, and the second description data pair does not meet the comparison conditions, then the comparison process for the second description data pair is skipped. Specifically, if the second description data pair contains either the first or second comparison data, it indicates that the comparison conditions are not met; if the second description data pair does not contain either the first or second comparison data, it indicates that the comparison conditions are not met, and the second description data pair is then compared. Each descriptive data pair is evaluated based on the results of all previously determined target alignments. That is, if the first and second alignments have already been successfully matched, they will not be compared again.

[0088] For example, the data pairs include data pair 1 [description data ①, description data ③], data pair 2 [description data ①, description data ④], data pair 3 [description data ②, description data ③], and data pair 4 [description data ②, description data ④]. If data pair 1 fails to match, then data pair 2 is matched. If data pair 2 matches successfully, and data pair 3 does not include successfully matched description data, then data pair 3 is matched. If data pair 3 fails to match successfully, and data pair 4 includes successfully matched description data, then data pair 4 is skipped.

[0089] Furthermore, since the N first descriptive data and M second descriptive data all have a description order, this indicates that there is an execution logical order between the descriptive data. When the description order changes, it signifies that the business logic has changed. For example, as... Figure 7 As shown, Figure 7 This is a schematic diagram illustrating a scenario of a change in the description order provided in an embodiment of this application. The description data in object description file A indicates that request A is sent to system A first, followed by request B to system B. However, the description order in object description file B changes in this part, indicating that request B is sent to system B first, followed by request A to system A. Although the content of the description data and the operations performed by the device are the same, the change in description order indicates that the executed business logic has also changed.

[0090] Therefore, when comparing each pair of description data in turn, the current pair of description data can not only combine the previously obtained comparison results, but also the description order of the first and second description data that were successfully compared in the previous comparison, to determine whether to skip the comparison process or continue the comparison.

[0091] In some embodiments, comparing the first and second description data in each description data pair sequentially may further include determining the first description data in the second description data pair as the third comparison data and determining the second description data in the second description data pair as the fourth comparison data. If the target comparison result indicates that the first and second comparison data are the same, and the second description data pair does not meet the comparison conditions, then the comparison process for the second description data pair is skipped. Specifically, if the description order of the third comparison data is less than or equal to the description order of the first comparison data, or the description order of the fourth comparison data is less than or equal to the description order of the second comparison data, then the comparison conditions are not met. Each description data pair is judged based on all previously determined target comparison results during comparison. That is, the first or second description data whose description order precedes that of a successfully compared description data pair will not be compared; even if identical second or first description data exists, it is still considered as differing description data. In this case, when comparing the description order, the third (or fourth) alignment data under the same description level is compared with the first (or second) alignment data.

[0092] In some embodiments, since there are description levels within the description levels of the first description data, if the comparison is performed in order of description priority, between the successfully matched first and second description data, a comparison is made between the first description data of the next description level associated with the first description data and the first description data of the next description level associated with the second description data. For example, the first description data is step 1, and the associated next description level is steps 1.1, 1.2, etc. under step 1. That is, after comparing the first and second comparison data to obtain the target comparison result, if the target comparison result indicates that the first comparison data and the second comparison data are the same, and the third comparison data is the description data of the next description level associated with the first comparison data, and the fourth comparison data is the description data of the next description level associated with the second comparison data, then the comparison process for the second description data pair is executed. Each description data pair is judged based on all previously determined comparison results during the comparison. The comparison of the first and second description data will only be performed when the comparison of the description data pair consisting of the description data of the previous description level associated with the first description data and the description data of the previous description level associated with the second description data is successful.

[0093] For example, such as Figure 8 As shown, Figure 8This is a schematic diagram of a comparison scenario for descriptive data pairs provided in an embodiment of this application; wherein, the descriptive data pairs constructed at this time are assumed to include data pair 1 [first step 1, second step 1], data pair 2 [first step 1, second step 2], data pair 3 [first step 2, second step 1], data pair 4 [first step 2, second step 2], data pair 5 [first step 1.1, second step 1.1], data pair 6 [first step 1.1, second step 1.2], data pair 7 [first step 1.1, second step 1.3], data pair 8 [first step 1.2, second step 1.1], data pair 9 [first step 1.2, second step 1.2], data pair 10 [first step 1.2, second step 1.3], data pair 11 [first step 2.1, second step 1.1], data pair 12 [first step 2.1, second step 1.2], and data pair 13 [first step 2.1, second step 1.3].

[0094] Therefore, the comparison process is as follows: Data pair 1 is compared, and the comparison is successful; data pairs 2-3 all include successfully compared descriptive data, so data pairs 2-3 are not compared; data pair 4 is compared, and the comparison is unsuccessful; in data pair 5, if the previous descriptive level associated with step 1.1 in step 1.1 and the previous descriptive level associated with step 2.1 in step 2.1 are successfully compared, then data pair 5 is compared, and the comparison is unsuccessful; similarly, data pair 6 is compared, and the comparison is successful; data pair 7 includes successfully compared descriptive data. If the description order of step 1.1 in step 2 of data pair 8 is earlier than that of step 1.2 of the successfully matched data pair 8, then data pair 8 will not be compared; if data pair 9 includes successfully matched description data, then data pair 9 will not be compared; if data pair 10 meets the comparison conditions, then data pair 10 will be compared; if the description order of step 2 of the previous description level associated with the first description data in data pairs 11-13 is not successfully matched with step 1 of the previous description level associated with the second description data, then data pairs 11-13 will not be compared.

[0095] In one possible implementation, when comparing description data pairs, the content matching degree of the first and second description data in the description data pair can be further determined to obtain the highest content matching degree of each first description data in all its description data pairs. This content matching degree represents the content overlap rate of the first and second description data. If the first and second description data are the same, the content matching degree can be 1; if the first and second description data are different, the content matching degree can be less than 1.

[0096] In some embodiments, if the highest content matching degree of the first description data is 1, it indicates that the first description data has successfully matched second description data; if the highest content matching degree is less than 1 but greater than a preset matching degree threshold, it indicates that the first description data has not been successfully matched but has second description data with similar content. The second description data can be marked as similar description data associated with the first description data, and this marking result is included in the final comparison result. Therefore, if the similar second description data associated with the first description data at the previous description level in the current description data pair to be compared is the description data associated with the second description data at the previous description level in the description data pair, then the description data pair can continue to be compared. For example, with... Figure 8 Taking the description data pairs as an example, if neither data pair 1 nor data pair 2 is successfully matched, and the first description data in data pair 2 has the highest content matching degree with the second description data and is greater than the matching degree threshold, it means that the second description data can be the description data modified based on the first description data. Therefore, the comparison process for data pairs 4-8 can be executed in the manner described above.

[0097] S506. Determine the difference description data between the first business object and the second business object based on the comparison results.

[0098] In some embodiments, the comparison result indicates the same first description data and second description data. The electronic device may use description data other than the same first description data and second description data from N first description data and M second description data as difference description data between the first business object and the second business object.

[0099] In some embodiments, the differential business logic between the first business object and the second business object can be determined based on the differential description data, and the business logic of the first or second business object can be optimized based on the differential business logic. For example, if the first business object is a web payment use case and the second business object is a QR code payment use case, after obtaining the differential business logic between the first and second business objects, an optimization scheme for the second business object can be determined based on the differential business logic. For example, if the differential business logic indicates that the web payment use case can perform facial verification during payment, the QR code payment use case can be optimized to add facial verification as a business logic.

[0100] In some embodiments, the comparison result may also indicate similar first and second descriptive data. The electronic device may also use deleted or added differences between similar first and second descriptive data as difference descriptive data. For example, if the first descriptive data is "Display user information" and the second descriptive data is "Display advanced user information," then "advanced" is the difference. The number of these difference descriptive data is at least one. Subsequently, the difference type of each difference descriptive data can be determined, and a display method matching the difference type of each difference descriptive data can be obtained. Each difference descriptive data is then displayed in the object display interface according to the display method matching the difference type of each difference descriptive data. The display method matching the corresponding difference type may also be different for difference descriptive data in different types of descriptive data. The difference type and display method of the difference descriptive data can be set by relevant business personnel based on experience. The definition and display method of the difference type are not limited here. This object display interface is used to display the first object description file and the second object description file for intuitive comparison of differences.

[0101] The determination of the difference type of the difference description data can be as follows: the difference type of the difference description data belonging to N first description data is the first deletion data type, and the difference type of the difference content belonging to the first description data is the second deletion data type; the difference type of the difference description data belonging to M second description data is the first addition difference type, and the difference type of the difference content belonging to the second description data is the second addition difference type; if the same or similar first description data and second description data have supplementary constraints, and the aforementioned two supplementary constraints contain difference description data, then it can be indicated that there is a difference between the two supplementary constraints as a whole, and the difference type is the modification data type; and so on.

[0102] The display method for difference type matching can be as follows: a first display form showing the difference description data of the first deleted data type, such as highlighting the difference description data with a light red background; a second display form showing the difference description data of the second deleted data type, such as highlighting the difference description data with a dark red background; a third display form showing the difference description data of the first added data type, such as highlighting the difference description data with a light green background; a fourth display form showing the difference description data of the second added data type, such as highlighting the difference description data with a dark green background; and a fifth display form showing the difference description data of the modified data type, such as highlighting the difference description data with a yellow background or special text markings, such as "There are differences in the supplementary constraint content"; and so on.

[0103] For example, such as Figures 9a-9d As shown, Figures 9a-9dThis is a schematic diagram of a data comparison scenario provided in an embodiment of this application; wherein, the display interface of the object description file can be as follows: Figure 9a You can view the object information unit containing multiple fields (such as version information, target system, use case name, etc.), as well as the basic information of multiple steps and supplementary constraints in the steps (such as the number of fields, the number of rules, etc.). By clicking on a specific step or supplementary constraint, you can jump to the details interface.

[0104] When displaying difference description data, you can display specific difference description data according to the instructions of relevant business personnel. For example, you can display difference description data for specific steps. Figure 9b As shown in the figure, identical or similar first and second description data are aligned. In the first object description file on the left, description data without any markings are successfully matched; description data marked with a single underscore represents deleted difference description data in the first object description file; and description data marked with square brackets represents the deleted differences between the first and similar second description data (e.g., steps 1.1 in the first and second description data are similar). In the second object description file on the right, description data without any markings are successfully matched; description data marked with double underscores represents newly added difference description data in the second object description file; and description data marked with curly braces represents the newly added differences between the second and similar first description data. Regarding basic information about supplementary constraints (such as the number of fields), in identical or similar first and second description data, if the number of fields in the first description data is greater than the number of fields in the second description data, it indicates that fields may have been deleted, and the number of fields can be marked in dark gray; if the number of fields in the first description data is less than the number of fields in the second description data, it indicates that fields may have been added, and the number of fields can be marked in light gray.

[0105] Displaying specified difference description data can also display difference description data for supplementary constraints targeting a specified step, such as... Figure 9cAs shown in the figure, the first and second description data that are identical or similar are aligned. The supplementary constraint includes multiple rules. The description data corresponding to a rule includes a rule summary and rule details. The rule details can be viewed by triggering the rule summary. On the left, description data without any markings are successfully matched description data. Description data marked with a single underscore is deleted difference description data. Description data marked with angle brackets and text markings (if there are differences) is modified difference description data, indicating that the two rules are different but similar. Description data marked with square brackets indicates deleted difference content. On the right, description data without any markings are successfully matched description data. Description data marked with double underscores is newly added difference description data in the second object description file. Description data marked with angle brackets and text markings (if there are differences) is modified difference description data, indicating that the two rules are different but similar. Description data marked with curly braces indicates newly added difference content.

[0106] Displaying specified difference description data can also display difference description data for specified cells, such as... Figure 9d As shown, this unit includes multiple fields, with the description data corresponding to each field being the field value. It can be seen that each field name to be displayed is predefined, and Field 1 and Field 2 are set as fields that do not require comparison. Therefore, on the left, description data without any markings represents successfully compared and uncompared description data; description data marked with a single underscore represents deleted difference description data; and description data marked with square brackets represents deleted difference content. On the right, description data without any markings represents successfully compared and uncompared description data; description data marked with double underscores represents newly added difference description data; and description data marked with curly braces represents newly added difference content.

[0107] In some embodiments, in a business object management system, a schematic diagram of a conceptual model describing a use case can be as follows: Figure 10As shown, for a single use case, the steps, fields, and rules describing the business requirements are the three most important elements, and the remaining elements are typically built around these three. Therefore, comparing the business logic between use cases mainly involves performing the aforementioned comparison process on these three structured elements. In the business object management system, each use case identifier is associated with the identifier of the corresponding object description file (or the structured identifier of each description data). After selecting a use case, the object description file or each description data is retrieved sequentially according to the association relationship, and the identified differences are displayed in different ways. The structured first and second object description files can be represented as a structured object description tree. Different description data or different description levels can be reflected by the position of the tree nodes. Comparing the first and second object description files is equivalent to comparing the two object description trees to achieve accurate hierarchical or sequential difference comparison. When comparing two object description trees, the two object description trees are considered to be unrelated. For example, when the second object description file is obtained by directly modifying the first object description file, the unmodified description data in the two object description files are considered to be the same and related description data. However, during the comparison, the two object description files are still considered to be unrelated, and the comparison process is based on each first description data and each second description data contained therein.

[0108] For example, such as Figures 11a-11c As shown, Figures 11a-11c This application provides a schematic diagram of a data comparison scenario; wherein the comparison process based on an object description tree is as follows: Figure 11a The process is as follows: S1. Obtain the first object description file (first object description tree) and the second object description file (second object description tree); S2. Obtain the list A of tree nodes at the target level in the first object description tree and the list B of tree nodes at the target level in the second object description tree; S3. Compare the list A of tree nodes and the list B of tree nodes to obtain the comparison result; S4. Determine whether each tree node in the list A of tree nodes has child nodes; S5. If there are child nodes, then based on the comparison result, execute the comparison process for the child nodes in sequence, that is, treat the child node as an object description tree and compare the child node tree with the child nodes contained in the tree nodes in the node list B according to the aforementioned process; S6. If there are no child nodes, then end the comparison.

[0109] First object description tree and second object description tree are as follows Figure 11bAs shown, the comparison is first performed on the first-level tree node list (tree node list A: steps 1-3; tree node list B: steps 1-5) to obtain the first comparison result. Then, the child nodes of each tree node in tree node list A are traversed. Based on the first comparison result, the comparison is performed on the second-level tree node list (tree node list A: steps 1.1-1.2, 2.1-2.3; tree node list B: 1.1-1.2, 4.1-4.3) to obtain the second comparison result. Then, the tree nodes of the next level are traversed, and the above process is continued.

[0110] The comparison process employs the LCS (Longest Common Subsequence) algorithm. Specifically, taking the first-level tree node list as an example, the business logic of each first step is determined based on all descriptive data contained in each step (referred to as each first step) of tree node list A. Similarly, the business logic of each second step is determined based on all descriptive data contained in each step (referred to as each second step) of tree node list B. This involves first comparing multiple descriptive data lines in the first and second object description trees (essentially comparing multiple lines of descriptive text), then refining the comparison to the individual descriptive data lines. First and second steps with the same business logic are combined, and the combined first and second steps are then compared. For example... Figure 11b The first step 1 and the second step 1 are combined, the first step 2 and the second step 4 are combined, and the first step 3 and the second step 5 are combined. The remaining description data related to the second step 2 and the second step 3 can be regarded as the difference description data of the first newly added data type. Subsequently, the first object description tree is traversed, and the child nodes of the second level are compared based on the combination results and the comparison results. For example, the first step 1.1 can be compared with the second step 1.1 and the second step 1.2 in sequence. If the first step 1.1 and the second step 1.1 are successfully compared, then the first step 1.2 is only compared with the second step 1.2 and the comparison is successful. In the next comparison, let's assume that the comparison between step 2.1 and step 4.1 is successful, the comparison between step 2.2 and step 4.2 is successful, and the comparison between step 2.3 and step 4.3 is successful. Subsequently, the first object description tree is traversed, and based on the combination result and the comparison, the third level of child nodes is continued. For example, it can be the comparison between step 1.1a and step 1.1a. If the comparison is successful, then step 1.1b and step 1.1c are no longer compared, and the description data related to step 1.1b and step 1.1c can be regarded as the difference description data of the first deleted data type.

[0111] The code structure of the constructed object description tree can be as follows: Figure 11c`leftTree` represents the first object description tree, and `rightTree` represents the second object description tree. The code structure of the first and second object description trees is the same. Taking the first object description tree as an example: "Id:1001" represents the node identifier of the first tree node at the first level in the first object description tree; "Label:'a1'" represents the node sequence value of the first tree node, which is associated with the description data indicated by the tree node; "Id:1001" represents the node identifier of the second tree node at the first level in the first object description tree; "Label:'a2'" represents the node sequence value of the second tree node; "Children:[{Id:1003,Label:'b1'}" indicates that the second tree node has child nodes, and the node identifier of the child node is "1003" and the node sequence value is "b1". Therefore, each tree node (or child node) has a corresponding node identifier and node sequence value, which is associated with the description data indicated by the tree node. Each tree node... A node can have child nodes, each with a corresponding node identifier and node sequence value. During alignment, the node list of each level is retrieved sequentially, including the corresponding node sequence value, and the alignment is performed based on the node list. After alignment, the alignment results for the two object description trees are output sequentially. The alignment results indicate relevant information for each node, such as its position (e.g., the line number in the object description file display interface), identifier, whether it is differential description data, and differential type (e.g., using the code "" to indicate that it is not differential data, and using the code "-" to indicate that it belongs to the first deleted data type). For example, the alignment result of a node in the first object description tree is represented as: "{Id:100x,Label:'ax',lineNumer:13,Prefix:"-"}". This indicates that the node with the identifier 100x and the node sequence value ax has a line number of 13, and the description data indicated by this node belongs to differential description data and the differential type is the differential type indicated by "-". The alignment results of other nodes are represented in the same way.

[0112] In this embodiment, a structured first object description file for a first business object and a structured second object description file for a second business object can be obtained. Multiple first description modules contained in the first object description file and multiple second description modules contained in the second object description file can also be obtained. Based on the business logic described by each first description module and each second description module, at least one description data pair is constructed for N first description data and M second description data. The first and second description data in each description data pair are compared, and the difference description data between the first business object and the second business object is determined based on the comparison results. Through this method, similar description data pairs can be constructed first based on the structured first and second object description files. These description data pairs are the description data to be compared from the two object description files. Then, these description data pairs are compared to determine the difference description data. This improves the flexibility of comparing object description files, reduces the workload, and improves the accuracy of the comparison results, thereby improving the accuracy of the difference description data obtained based on the comparison results.

[0113] Please see Figure 12 , Figure 12 This is a schematic diagram of a data processing device provided in this application. It should be noted that... Figure 12 The data processing apparatus shown is used to execute this application. Figure 2 and Figure 5 The methods in the illustrated embodiments are shown only in the parts relevant to the embodiments of this application for ease of explanation; specific technical details are not disclosed. Reference to this application is required. Figure 2 and Figure 5 The illustrated embodiment. The data processing device 1200 may include: an acquisition module 1201 and a processing module 1202. Wherein:

[0114] The acquisition module 1201 is used to acquire a structured first object description file of the first business object; the first object description file includes N structured first description data of the first business object; N is a positive integer;

[0115] The acquisition module 1201 is also used to acquire a structured second object description file of the second business object; the second object description file includes M structured second description data of the second business object; M is a positive integer;

[0116] Processing module 1202 is used to construct at least one description data pair based on N first description data and M second description data; any description data pair includes first description data and second description data that are similar in description;

[0117] The processing module 1202 is also used to compare the first description data and the second description data in each description data pair respectively, and determine the difference description data between the first business object and the second business object based on the comparison result.

[0118] In some embodiments, the first object description file includes a plurality of first description modules, and N first description data belong to the description data in the plurality of first description modules; the second object description file includes a plurality of second description modules, and M second description data belong to the description data in the plurality of second description modules.

[0119] When processing module 1202 is used to construct at least one description data pair based on N first description data and M second description data, it is specifically used for:

[0120] The business logic described by each first description module is determined based on the first description data in each first description module.

[0121] The business logic described by each second description module is determined based on the second description data in each second description module.

[0122] Combining a first description module and a second description module that have the same business logic yields at least one description module combination; any description module combination includes a first description module and a second description module that have the same business logic.

[0123] At least one descriptive data pair is constructed by combining at least one descriptive module.

[0124] In some embodiments, any one of the at least one combination of description modules is represented as a target combination of description modules; when the processing module 1202 is used to construct at least one description data pair based on at least one combination of description modules, it is specifically used to:

[0125] The first description module in the target description module combination is determined as the first comparison module, and the second description module in the target description module combination is determined as the second comparison module;

[0126] The first description data in the first comparison module and the second description data in the second comparison module are combined to obtain at least one description data pair.

[0127] In some embodiments, at least one description data pair includes a first description data pair and a second description data pair;

[0128] The processing module 1202 is specifically used for comparing the first and second description data in each description data pair respectively:

[0129] The first description data in the first description data pair is determined as the first comparison data, and the second description data in the first description data pair is determined as the second comparison data;

[0130] The first and second comparison data are compared to obtain the target comparison result;

[0131] If the target alignment result is used to indicate that the first alignment data and the second alignment data are the same, and the second description data pair contains either the first alignment data or the second alignment data, then the alignment process for the second description data pair is skipped.

[0132] In some embodiments, each of the N first description data has a corresponding description order in the first object description file, and each of the M second description data has a corresponding description order in the second object description file; the processing module 1202 is further configured to:

[0133] The first description data in the second description data pair is determined as the third comparison data, and the second description data in the second description data pair is determined as the fourth comparison data;

[0134] If the target alignment result indicates that the first alignment data is the same as the second alignment data, and the description order of the third alignment data is less than or equal to the description order of the first alignment data, or the description order of the fourth alignment data is less than or equal to the description order of the second alignment data, then the alignment process for the second description data pair is skipped.

[0135] In some embodiments, the difference description data is at least one; the processing module 1202 is further configured to:

[0136] Determine the difference type for each difference description data and obtain the display method that matches the difference type for each difference description data;

[0137] Each difference description is displayed separately according to the display method that matches the difference type of each difference description.

[0138] In some embodiments, the processing module 1202 is further configured to:

[0139] Determine the difference business logic between the first business object and the second business object based on the difference description data;

[0140] Verify the different business logic for the first business object or the second business object.

[0141] In this embodiment, the acquisition module acquires a structured first object description file of a first business object; the acquisition module acquires a structured second object description file of a second business object; the processing module constructs at least one description data pair based on N first description data and M second description data; the processing module compares the first and second description data in each description data pair, and determines the difference description data between the first business object and the second business object based on the comparison results. Through the above apparatus, similar description data pairs can be constructed first based on the structured first and second object description files. These description data pairs are the description data to be compared determined from the two object description files. Then, these description data pairs are compared to determine the difference description data, thereby improving the flexibility of object description file comparison, reducing the comparison workload, and improving the accuracy of the comparison results. This, in turn, improves the accuracy of the difference description data obtained based on the comparison results.

[0142] In the various embodiments of this application, the functional units can be integrated into one module (unit), or each unit can exist physically separately, or two or more units can be integrated into one module. The integrated module (unit) can be implemented in hardware or as a software functional module, and this application does not impose any limitations on this.

[0143] Please see Figure 13 , Figure 13 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 13 As shown, the electronic device 1300 includes at least one processor 1301 and a memory 1302. Optionally, the electronic device may also include a network interface. The processor 1301, memory 1302, and network interface can exchange data. The network interface, controlled by the processor 1301, is used to send and receive messages. The memory 1302 stores a computer program, which includes program instructions. The processor 1301 executes the program instructions stored in the memory 1302. The processor 1301 is configured to invoke the program instructions to execute the aforementioned method.

[0144] The memory 1302 may include volatile memory, such as random-access memory (RAM); the memory 1302 may also include non-volatile memory, such as flash memory, solid-state drive (SSD), etc.; the memory 1302 may also include a combination of the above types of memory.

[0145] The processor 1301 may be a central processing unit (CPU). In one embodiment, the processor 1301 may also be a graphics processing unit (GPU). The processor 1301 may also be a combination of a CPU and a GPU.

[0146] In some embodiments, the memory 1302 is used to store program instructions, which the processor 1301 can invoke to perform the following steps:

[0147] Obtain the structured first object description file of the first business object; the first object description file includes N structured first description data of the first business object; N is a positive integer;

[0148] Obtain the structured second object description file of the second business object; the second object description file includes M structured second description data of the second business object; M is a positive integer;

[0149] At least one description data pair is constructed based on N first description data and M second description data; any description data pair includes first description data and second description data that are similar in description.

[0150] The first and second description data in each description data pair are compared, and the difference description data between the first business object and the second business object is determined based on the comparison results.

[0151] In some embodiments, the first object description file includes a plurality of first description modules, and N first description data belong to the description data in the plurality of first description modules; the second object description file includes a plurality of second description modules, and M second description data belong to the description data in the plurality of second description modules.

[0152] When the processor 1301 is used to construct at least one description data pair based on N first description data and M second description data, it is specifically used for:

[0153] The business logic described by each first description module is determined based on the first description data in each first description module.

[0154] The business logic described by each second description module is determined based on the second description data in each second description module.

[0155] Combining a first description module and a second description module that have the same business logic yields at least one description module combination; any description module combination includes a first description module and a second description module that have the same business logic.

[0156] At least one descriptive data pair is constructed by combining at least one descriptive module.

[0157] In some embodiments, any one of the at least one combination of description modules is represented as a target combination of description modules; when the processor 1301 is used to construct at least one description data pair based on at least one combination of description modules, it is specifically used to:

[0158] The first description module in the target description module combination is determined as the first comparison module, and the second description module in the target description module combination is determined as the second comparison module;

[0159] The first description data in the first comparison module and the second description data in the second comparison module are combined to obtain at least one description data pair.

[0160] In some embodiments, at least one description data pair includes a first description data pair and a second description data pair;

[0161] The processor 1301 is specifically used for comparing the first and second description data in each description data pair, respectively:

[0162] The first description data in the first description data pair is determined as the first comparison data, and the second description data in the first description data pair is determined as the second comparison data;

[0163] The first and second comparison data are compared to obtain the target comparison result;

[0164] If the target alignment result is used to indicate that the first alignment data and the second alignment data are the same, and the second description data pair contains either the first alignment data or the second alignment data, then the alignment process for the second description data pair is skipped.

[0165] In some embodiments, each of the N first description data has a corresponding description order in the first object description file, and each of the M second description data has a corresponding description order in the second object description file; the processor 1301 is further configured to:

[0166] The first description data in the second description data pair is determined as the third comparison data, and the second description data in the second description data pair is determined as the fourth comparison data;

[0167] If the target alignment result indicates that the first alignment data is the same as the second alignment data, and the description order of the third alignment data is less than or equal to the description order of the first alignment data, or the description order of the fourth alignment data is less than or equal to the description order of the second alignment data, then the alignment process for the second description data pair is skipped.

[0168] In some embodiments, the difference description data is at least one; the processor 1301 is further configured to:

[0169] Determine the difference type for each difference description data and obtain the display method that matches the difference type for each difference description data;

[0170] Each difference description is displayed separately according to the display method that matches the difference type of each difference description.

[0171] In some embodiments, the processor 1301 is further configured to:

[0172] Determine the difference business logic between the first business object and the second business object based on the difference description data;

[0173] Verify the different business logic for the first business object or the second business object.

[0174] In specific implementations, the data processing device, processor, memory, etc. described above can execute the implementation methods described in the above method embodiments, or they can execute the implementation methods described in the embodiments of this application, which will not be repeated here.

[0175] This application also provides a computer-readable storage medium storing a computer program. The computer program includes program instructions, which, when executed by a processor, enable the processor to perform some or all of the steps described in the above method embodiments. Optionally, the computer storage medium can be volatile or non-volatile. The computer-readable storage medium may primarily include a program storage area and a data storage area. The program storage area may store an operating system, at least one application program required for a given function, etc.; the data storage area may store data created based on the use of blockchain nodes, etc.

[0176] This application also provides a computer program product, which includes computer instructions that, when executed by a processor, can implement some or all of the steps in the above-described method.

[0177] In this article, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0178] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The aforementioned program can be stored in a computer storage medium, which can be a computer-readable storage medium. When executed, the program can include the processes of the embodiments of the above methods. The aforementioned storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0179] The above-disclosed embodiments are merely some of the embodiments of this application, and should not be construed as limiting the scope of this application. Those skilled in the art can understand that all or part of the processes for implementing the above embodiments, and equivalent changes made in accordance with the claims of this application, still fall within the scope of this application.

Claims

1. A data processing method, characterized in that, The method includes: Obtain a structured first object description file for the first business object; the first object description file includes N structured first description data of the first business object; N is a positive integer; Obtain a structured second object description file for the second business object; the second object description file includes M structured second description data for the second business object; M is a positive integer; At least one description data pair is constructed based on the N first description data and the M second description data; any description data pair includes first description data and second description data that are similar in description; The first and second description data in each description data pair are compared respectively, and the difference description data between the first business object and the second business object is determined based on the comparison results. Wherein, the at least one description data pair includes a first description data pair and a second description data pair; the comparison of the first description data and the second description data in each description data pair includes: The first description data in the first description data pair is determined as the first comparison data, and the second description data in the first description data pair is determined as the second comparison data; The first comparison data and the second comparison data are compared to obtain the target comparison result; If the target alignment result indicates that the first alignment data and the second alignment data are the same, and the second description data pair contains either the first alignment data or the second alignment data, then the alignment process for the second description data pair is skipped.

2. The method according to claim 1, characterized in that, The first object description file contains multiple first description modules, and the N first description data belong to the description data in the multiple first description modules; the second object description file contains multiple second description modules, and the M second description data belong to the description data in the multiple second description modules. The construction of at least one description data pair based on the N first description data and the M second description data includes: The business logic described by each first description module is determined based on the first description data in each first description module; The business logic described by each second description module is determined based on the second description data in each second description module; Combining a first description module and a second description module that have the same business logic yields at least one description module combination; any description module combination includes a first description module and a second description module that have the same business logic. The at least one description data pair is constructed by combining the at least one description module.

3. The method according to claim 2, characterized in that, Any one of the at least one combination of description modules is represented as a target combination of description modules; the step of constructing the at least one description data pair based on the at least one combination of description modules includes: The first description module in the target description module combination is determined as the first comparison module, and the second description module in the target description module combination is determined as the second comparison module; The first description data in the first comparison module and the second description data in the second comparison module are combined to obtain the at least one description data pair.

4. The method according to claim 1, characterized in that, Each of the N first description data has a corresponding description order in the first object description file, and each of the M second description data has a corresponding description order in the second object description file; the method further includes: The first description data in the second description data pair is determined as the third comparison data, and the second description data in the second description data pair is determined as the fourth comparison data; If the target alignment result indicates that the first alignment data and the second alignment data are the same, and the description order of the third alignment data is less than or equal to the description order of the first alignment data, or the description order of the fourth alignment data is less than or equal to the description order of the second alignment data, then the alignment process for the second description data pair is skipped.

5. The method according to claim 1, characterized in that, The difference description data is at least one; the method further includes: Determine the difference type for each difference description data, and obtain the display method that matches the difference type for each difference description data; Each difference description data is displayed in a manner that matches the difference type of each difference description data.

6. The method according to claim 1, characterized in that, The method further includes: Based on the difference description data, determine the difference business logic between the first business object and the second business object; The difference business logic is verified on the first business object or the second business object.

7. A data processing apparatus, characterized in that, The device includes: The acquisition module is used to acquire a structured first object description file of the first business object; the first object description file includes N structured first description data of the first business object; N is a positive integer; The acquisition module is further configured to acquire a structured second object description file of the second business object; the second object description file includes M structured second description data of the second business object; M is a positive integer; The processing module is configured to construct at least one description data pair based on the N first description data and the M second description data; any description data pair includes first description data and second description data that are similar in description. The processing module is further configured to compare the first description data and the second description data in each description data pair respectively, and determine the difference description data between the first business object and the second business object based on the comparison result; Wherein, the at least one description data pair includes a first description data pair and a second description data pair; the processing module compares the first description data and the second description data in each description data pair, including: The first description data in the first description data pair is determined as the first comparison data, and the second description data in the first description data pair is determined as the second comparison data; The first comparison data and the second comparison data are compared to obtain the target comparison result; If the target alignment result indicates that the first alignment data and the second alignment data are the same, and the second description data pair contains either the first alignment data or the second alignment data, then the alignment process for the second description data pair is skipped.

8. An electronic device, characterized in that, The device includes a processor and a memory, wherein the memory is used to store a computer program, the computer program including program instructions, and the processor is configured to invoke the program instructions to perform the method as described in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, the computer program including program instructions that, when executed by a processor, cause the processor to perform the method as described in any one of claims 1-6.

10. A computer program product, characterized in that, The computer program product includes computer instructions that, when executed by a processor, implement the method as described in any one of claims 1-6.

Images