A method and device for dynamically managing differentiated service data

CN115640978BActive Publication Date: 2026-09-29SHENZHEN COMTOP INFORMATION TECH
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202211376553.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-11-04
Publication Date
2026-09-29
Estimated Expiration
2042-11-04

AI Technical Summary

Benefits of technology

[0064]本发明实施例中,提供了一种差异化业务数据的动态管控方法,该方法包括:确定待编排的所有逻辑单元以及每个逻辑单元的单元数据;

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115640978B_ABST
    Figure CN115640978B_ABST
Patent Text Reader

Abstract

The application discloses a kind of dynamic management and control method and device of differentiated service data, the method includes: determining all logical units to be arranged and the unit data of each logical unit;The unit data of each logical unit is executed metadata conversion operation, and the conversion data of each logical unit is obtained;According to flow chart construction algorithm, determine logical parameter, to generate at least one logical flow chart;According to the conversion data of all logical units, all logical flow chart combination data deployment scheduling algorithm, generate service scheduling model;According to the service scheduling model, the data arrangement scheduling operation of input service data is executed, and the arrangement scheduling result corresponding to service data is obtained, and arrangement scheduling result is used to feedback to the processing personnel responsible for service data, to make processing personnel check arrangement scheduling result.It can be seen that the application can reduce the difficulty of processing differentiated regional business service management, and improve the efficiency of differentiated regional business service management.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of data orchestration, scheduling and control technology, and in particular to a method and apparatus for dynamic control of differentiated business data. Background Technology

[0002] As the power grid management platform undergoes iterative updates, its current business logic becomes increasingly complex and diverse. Simultaneously, with the platform's application and expansion across different subsidiaries, the corresponding business rules will also exhibit greater differentiation.

[0003] For example, when the same business process passes through the same approval node in different regions, the business matters processed at that node will differ based on the approval rules of each business region. For a given approval node, when handling approval events from different business regions, it is necessary to adapt the key control information and data thresholds for business flows in different regions. Furthermore, the business display interfaces and business data analysis reports for different regions will become increasingly complex and diverse as the platform expands and iterates. Therefore, it is particularly important to address the challenges of high difficulty and low efficiency in regional business management caused by the differences in regional business rules within the power grid management platform. Summary of the Invention

[0004] The technical problem to be solved by the present invention is to provide a method and apparatus for dynamic management and control of differentiated business data, which can reduce the difficulty of business management of differentiated regional businesses and improve the efficiency of business management of differentiated regional businesses.

[0005] To address the aforementioned technical problems, the first aspect of this invention discloses a method for dynamic management and control of differentiated business data, the method comprising:

[0006] Determine all logical units to be arranged and the unit data of each logical unit;

[0007] Perform a preset metadata transformation operation on the unit data of each logical unit to obtain the transformed data of each logical unit;

[0008] The logical parameters are determined according to a preset flowchart construction algorithm, and at least one logical flowchart is generated according to the logical parameters, wherein the logical parameters are the parameters required to construct the logical flowchart;

[0009] Based on the transformation data of all the logical units, all the logical flowcharts, and a preset data deployment and scheduling algorithm, a business scheduling model is generated. The business scheduling model is used to perform data orchestration and scheduling operations on the data input to the business scheduling model.

[0010] According to the business scheduling model, the data orchestration and scheduling operation is performed on the input business data to obtain the orchestration and scheduling result corresponding to the business data. The orchestration and scheduling result is used to feed back to the personnel responsible for processing the business data so that the personnel can verify the orchestration and scheduling result.

[0011] As an optional implementation, in the first aspect of the present invention, the logical parameters include orchestration parameters, structure and return value parameters, node logical parameters, and sequence parameters;

[0012] The orchestration parameters include target information required for managing the logic flowchart. The target information includes identification information, encoding information, and description information. The identification information is the identification information corresponding to each logical component in the logic flowchart. The encoding information includes the encoding and decoding method used to construct the logic flowchart. The description information includes description information of all logical components and / or the functions corresponding to the logic flowchart.

[0013] The structure and return value parameters are used to define the data structure collected when constructing the logic flowchart and the corresponding return result data when executing the constructed logic flowchart;

[0014] The node logic parameters are used to indicate the node logic corresponding to all logic nodes used in constructing the logic flowchart;

[0015] The sequence parameter is used to define the execution order between different logical nodes.

[0016] As an optional implementation, in the first aspect of the present invention, each of the logical flowcharts includes a process code corresponding to the logical flowchart. The process code is used to call the logical flowchart corresponding to the process code. The process code is also used to perform at least one of the following operations: data storage, data update, and data verification operations on all the logical flowcharts under the set of flowcharts controlled by the process code.

[0017] As an optional implementation, in the first aspect of the present invention, the step of performing the data orchestration and scheduling operation on the input service data according to the service scheduling model to obtain the orchestration and scheduling result corresponding to the service data includes:

[0018] Based on the input business data, determine the business process code corresponding to that business data;

[0019] Based on the business scheduling model, determine the business logic flowchart that matches the business process code;

[0020] Using the starting node included in the business logic flowchart as the base point, the business data is sequentially input into each execution logic node of the business logic flowchart according to the execution logic corresponding to the business logic flowchart;

[0021] Collect the process return values ​​of the end nodes included in the business logic flowchart, and after determining that the process return value is not a preset start return value, determine that the process return value is the orchestration and scheduling result corresponding to the business data.

[0022] As an optional implementation, in the first aspect of the present invention, after determining that the process return value is not a preset initial return value, and before determining that the process return value is the orchestration and scheduling result corresponding to the business data, the method further includes:

[0023] Obtain the deployment information of the business logic flowchart, wherein the deployment information is used to record version change information after the business logic flowchart is executed;

[0024] When the deployment information indicates that the version of the business logic flowchart has changed after the execution of the business logic flowchart, a retrospective information is generated and the operation of determining that the return value of the process is the orchestration and scheduling result corresponding to the business data is triggered. The retrospective information is used to retrospectively deploy the information back to the deployment information before the execution of the business logic flowchart.

[0025] As an optional implementation, in the first aspect of the present invention, after determining that the process return value is the orchestration and scheduling result corresponding to the business data, the method further includes:

[0026] Analyze historical orchestration and scheduling data and the orchestration and scheduling results to obtain analysis results. The historical orchestration and scheduling data is the data corresponding to the recorded calls to the business logic flowchart. The historical orchestration and scheduling data includes verification parameters used to perform exception verification operations.

[0027] When the analysis result indicates that the verification match value between the orchestration and scheduling result and the verification parameter exceeds the standard verification match value, a logic correction operation is performed on the business logic flowchart based on the historical orchestration and scheduling data and the verification parameter, so that the verification match value between the corrected data orchestration result and the verification parameter is lower than or equal to the standard verification match value.

[0028] As an optional implementation, in the first aspect of the present invention, performing a preset metadata transformation operation on the unit data of each logical unit to obtain transformed data for each logical unit includes:

[0029] For each logical unit, the unit type of the logical unit is determined. The unit type includes a first type or a second type. The first type is the type corresponding to the logical unit and the data processing space of the business scheduling model to be constructed being in the same virtual space. The second type is the type that matches the preset REST service processing logic.

[0030] Based on the unit type of each logical unit, a preset metadata transformation operation is performed on the unit data of the logical unit to obtain the transformed data of each logical unit.

[0031] A second aspect of the present invention discloses a dynamic management and control device for differentiated business data, the device comprising:

[0032] The determination module is used to determine all logical units to be arranged and the unit data of each logical unit;

[0033] The data conversion module is used to perform a preset metadata conversion operation on the unit data of each logical unit to obtain the converted data of each logical unit;

[0034] The determining module is further configured to determine logical parameters based on a preset flowchart construction algorithm;

[0035] A generation module is used to generate at least one logic flowchart based on the logic parameters, wherein the logic parameters are parameters required to construct the logic flowchart.

[0036] The generation module is further configured to generate a business scheduling model based on the transformation data of all the logical units, all the logical flowcharts, and a preset data deployment scheduling algorithm. The business scheduling model is used to perform data orchestration and scheduling operations on the data input to the business scheduling model.

[0037] The orchestration and scheduling module is used to perform the data orchestration and scheduling operation on the input business data according to the business scheduling model, and obtain the orchestration and scheduling result corresponding to the business data. The orchestration and scheduling result is used to feed back to the personnel responsible for processing the business data so that the personnel can verify the orchestration and scheduling result.

[0038] As an optional implementation, in a second aspect of the present invention, the logical parameters include orchestration parameters, structure and return value parameters, node logical parameters, and sequence parameters;

[0039] The orchestration parameters include target information required for managing the logic flowchart. The target information includes identification information, encoding information, and description information. The identification information is the identification information corresponding to each logical component in the logic flowchart. The encoding information includes the encoding and decoding method used to construct the logic flowchart. The description information includes description information of all logical components and / or the functions corresponding to the logic flowchart.

[0040] The structure and return value parameters are used to define the data structure collected when constructing the logic flowchart and the corresponding return result data when executing the constructed logic flowchart;

[0041] The node logic parameters are used to indicate the node logic corresponding to all logic nodes used in constructing the logic flowchart;

[0042] The sequence parameter is used to define the execution order between different logical nodes.

[0043] As an optional implementation, in a second aspect of the present invention, each of the logical flowcharts includes a process code corresponding to the logical flowchart. The process code is used to call the logical flowchart corresponding to the process code. The process code is also used to perform at least one of the following operations: data storage, data update, and data verification operations on all the logical flowcharts under the set of flowcharts controlled by the process code.

[0044] As an optional implementation, in a second aspect of the invention, the orchestration and scheduling module includes:

[0045] The determination submodule is used to determine the business process code corresponding to the input business data.

[0046] The determining submodule is further configured to determine a business logic flowchart that matches the business process code based on the business scheduling model;

[0047] The logic processing submodule is used to input the business data into each execution logic node of the business logic flowchart in sequence, based on the starting node included in the business logic flowchart and according to the execution logic corresponding to the business logic flowchart.

[0048] The logic processing submodule is also used to collect the process return value of the end node included in the business logic flowchart, and after determining that the process return value is not a preset start return value, determine that the process return value is the orchestration and scheduling result corresponding to the business data.

[0049] As an optional implementation, in a second aspect of the invention, the orchestration and scheduling module further includes:

[0050] The deployment processing submodule is used to obtain the deployment information of the business logic flowchart after the logic processing submodule determines that the return value of the process is not a preset starting return value, and before determining that the return value of the process is the orchestration and scheduling result corresponding to the business data. The deployment information is used to record the version change information after the execution of the business logic flowchart.

[0051] A generation submodule is used to generate backtracking information and trigger the execution of the operation that determines the return value of the process as the orchestration and scheduling result corresponding to the business data when the version of the business logic flowchart is changed after the deployment information indicates that the process has been executed. The backtracking information is used to backtrack the deployment information to the deployment information before the execution of the business logic flowchart.

[0052] As an optional implementation, in a second aspect of the invention, the apparatus further includes:

[0053] The analysis module is used to analyze historical orchestration and scheduling data and the orchestration and scheduling result after the logic processing submodule determines that the return value of the process is the orchestration and scheduling result corresponding to the business data, and to obtain the analysis result. The historical orchestration and scheduling data is the data corresponding to the recorded call to the business logic flowchart. The historical orchestration and scheduling data includes verification parameters used to perform exception verification operations.

[0054] The logic correction module is used to perform a logic correction operation on the business logic flowchart based on the historical orchestration data and the verification parameters when the analysis result indicates that the verification match value between the orchestration and scheduling result and the verification parameters exceeds the standard verification match value, so that the verification match value between the corrected data orchestration result and the verification parameters is lower than or equal to the standard verification match value.

[0055] As an optional implementation, in a second aspect of the present invention, the data conversion module performs a preset metadata conversion operation on the unit data of each logical unit to obtain the converted data of each logical unit, specifically including:

[0056] For each logical unit, the unit type of the logical unit is determined. The unit type includes a first type or a second type. The first type is the type corresponding to the logical unit and the data processing space of the business scheduling model to be constructed being in the same virtual space. The second type is the type that matches the preset REST service processing logic.

[0057] Based on the unit type of each logical unit, a preset metadata transformation operation is performed on the unit data of the logical unit to obtain the transformed data of each logical unit.

[0058] A third aspect of the present invention discloses another dynamic management and control device for differentiated business data, the device comprising:

[0059] Memory containing executable program code;

[0060] A processor coupled to the memory;

[0061] The processor calls the executable program code stored in the memory to execute the dynamic management and control method for differentiated business data disclosed in the first aspect of the present invention.

[0062] The fourth aspect of the present invention discloses a computer storage medium storing computer instructions, which, when invoked, are used to execute the dynamic management and control method for differentiated business data disclosed in the first aspect of the present invention.

[0063] Compared with the prior art, the embodiments of the present invention have the following beneficial effects:

[0064] In this embodiment of the invention, a dynamic management and control method for differentiated business data is provided, the method comprising: determining all logical units to be orchestrated and the unit data of each logical unit;

[0065] For each logical unit, a preset metadata transformation operation is performed on the unit data to obtain the transformed data for each logical unit. Logical parameters are determined according to a preset flowchart construction algorithm, and at least one logical flowchart is generated based on these parameters. The logical parameters are those required to construct the logical flowcharts. Based on the transformed data of all logical units, all logical flowcharts, and a preset data deployment and scheduling algorithm, a business scheduling model is generated. This business scheduling model is used to perform data orchestration and scheduling operations on the data input to it. Based on the business scheduling model, data orchestration and scheduling operations are performed on the input business data to obtain the orchestration and scheduling results corresponding to the business data. These results are then fed back to the personnel responsible for processing the business data so that they can verify the orchestration and scheduling results. Therefore, implementing this invention can intelligently perform metadata transformation operations on the unit data of all determined logical units to be orchestrated, in order to construct a business scheduling model. This generates several logical flowcharts based on the determined logical parameters. Finally, based on all the transformed data, the generated logical flowcharts, and the data deployment and scheduling algorithm, a business scheduling model is generated for orchestrating and scheduling the input differentiated business data. The generated business scheduling model, based on several pre-prepared logical flowcharts and various intelligent logical orchestration algorithms, can support differentiated business and dynamic business invocation requirements, which helps reduce the management difficulty of differentiated business, while improving the management efficiency and accuracy of differentiated business. Attached Figure Description

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

[0067] Figure 1 This is a flowchart illustrating a dynamic management and control method for differentiated business data disclosed in an embodiment of the present invention;

[0068] Figure 2 This is a flowchart illustrating another dynamic management and control method for differentiated business data disclosed in an embodiment of the present invention;

[0069] Figure 3 This is a schematic diagram of the structure of a dynamic management and control device for differentiated business data disclosed in an embodiment of the present invention;

[0070] Figure 4 This is a schematic diagram of another dynamic management and control device for differentiated business data disclosed in an embodiment of the present invention;

[0071] Figure 5 This is a schematic diagram of the structure of another dynamic management and control device for differentiated business data disclosed in an embodiment of the present invention;

[0072] Figure 6 This is a schematic diagram of another dynamic management and control device for differentiated business data disclosed in an embodiment of the present invention. Detailed Implementation

[0073] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0074] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this invention are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, apparatus, product, or end that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or ends.

[0075] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of the invention. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0076] This invention discloses a dynamic management and control method and apparatus for differentiated business data. It intelligently performs metadata transformation operations on the unit data of all determined logical units to be orchestrated, for use in constructing a business scheduling model. This generates several logical flowcharts based on determined logical parameters. Finally, based on all transformed data, the generated logical flowcharts, and a data deployment scheduling algorithm, a business scheduling model is generated for orchestrating and scheduling input differentiated business data. This generated business scheduling model, based on several pre-prepared logical flowcharts and various intelligent logical orchestration algorithms, can support differentiated business and dynamic business invocation requirements, reducing the management difficulty of differentiated business while improving management efficiency and accuracy. Detailed descriptions follow.

[0077] Example 1

[0078] Please see Figure 1 , Figure 1 This is a flowchart illustrating a dynamic management method for differentiated business data disclosed in an embodiment of the present invention. Figure 1 The described dynamic management method for differentiated business data can be applied to a dynamic management device for differentiated business data, and this embodiment of the invention is not limited thereto. Figure 1 As shown, the dynamic management method for differentiated business data can include the following operations:

[0079] 101. Determine all logic units to be arranged and the unit data of each logic unit.

[0080] 102. Perform a preset metadata transformation operation on the unit data of each logical unit to obtain the transformed data of each logical unit.

[0081] In this embodiment of the invention, step 102 performs a preset metadata transformation operation on the unit data of each logical unit to obtain the transformed data of each logical unit. Specifically, this includes:

[0082] For each logical unit, determine the unit type of the logical unit. The unit type includes a first type or a second type. The first type is the type corresponding to the logical unit and the data processing space of the business scheduling model to be built being in the same virtual space. The second type is the type that matches the preset REST service processing logic.

[0083] Based on the unit type of each logical unit, a preset metadata transformation operation is performed on the unit data of that logical unit to obtain the transformed data of each logical unit.

[0084] In this embodiment of the invention, when processing each logical unit, the unit type of each logical unit can be intelligently determined, thereby adjusting the metadata conversion method used to process the logical unit according to the unit type of each logical unit, which improves the accuracy and reliability of the final converted metadata.

[0085] 103. Determine the logical parameters according to the preset flowchart construction algorithm, and generate at least one logical flowchart based on the logical parameters. The logical parameters are the parameters required to construct the logical flowchart.

[0086] In this embodiment of the invention, the logical parameters include orchestration parameters, structure and return value parameters, node logical parameters, and sequence parameters;

[0087] The orchestration parameters include target information required for managing the logic flowchart. The target information includes identification information, encoding information, and description information. The identification information is the identification information corresponding to each logical component in the logic flowchart. The encoding information includes the encoding and decoding method used to construct the logic flowchart. The description information includes the description information of the functions corresponding to all logical components and / or the logic flowchart.

[0088] The structure and return value parameters are used to define the data structure collected when building the logic flowchart and the corresponding return result data when the completed logic flowchart is executed;

[0089] Node logic parameters are used to indicate the node logic corresponding to all logic nodes used in the construction logic flowchart;

[0090] The sequence parameter is used to define the execution order between different logical nodes.

[0091] In this embodiment of the invention, each logical flowchart further includes a flow code corresponding to the logical flowchart. The flow code is used to call the logical flowchart corresponding to the flow code. The flow code is also used to perform at least one of the following operations: data storage, data update, and data verification operations on all logical flowcharts under the set of flowcharts controlled by the flow code.

[0092] 104. Generate a business scheduling model based on the transformation data of all logical units, all logical flowcharts, and a preset data deployment scheduling algorithm.

[0093] In this embodiment of the invention, the service scheduling model is used to perform data orchestration and scheduling operations on the data input to the service scheduling model.

[0094] 105. Based on the business scheduling model, perform data orchestration and scheduling operations on the input business data to obtain the orchestration and scheduling results corresponding to the business data.

[0095] In this embodiment of the invention, the orchestration and scheduling results are used to feed back to the personnel responsible for processing business data, so that the personnel can verify the orchestration and scheduling results.

[0096] It should be noted that you should refer to [link / reference]. Figure 6 This is a schematic diagram of another dynamic management and control device for differentiated business data disclosed in an embodiment of the present invention. In practical applications, this business scheduling model may include a dynamic engine for business scheduling execution and a business scheduling orchestrator. Specifically, the business scheduling orchestrator may include an access module for accessing business logic metadata (including metadata transformation) and a business orchestration designer. The access module can be used to access local services, REST services, and other services. The business orchestration designer includes multiple sub-functions such as local method orchestration, REST service orchestration, exception mechanism orchestration, message orchestration, gateway orchestration, import / export functions, temporary file processing, and node alignment. The dynamic engine for business scheduling execution can be further subdivided into logical scheduling and scheduling script deployment functions. The logical scheduling function includes local method logical scheduling, exception handling, transaction compensation, REST service requests, message publishing, message processing, and expression parsing. The scheduling script deployment includes logical deployment, version management, logical verification, and definition parsing functions, which are not limited in this embodiment of the present invention.

[0097] It is evident that implementation Figure 1 The described dynamic management method for differentiated business data intelligently performs metadata transformation operations on the unit data of all determined logical units to be orchestrated, in order to construct a business scheduling model. This generates several logical flowcharts based on defined logical parameters. Finally, based on all transformed data, the generated logical flowcharts, and a data deployment scheduling algorithm, a business scheduling model is generated for orchestrating and scheduling the input differentiated business data. This generated business scheduling model, based on several pre-prepared logical flowcharts and various intelligent logical orchestration algorithms, can support differentiated business and dynamic business invocation requirements, helping to reduce the management difficulty of differentiated businesses while improving management efficiency and accuracy.

[0098] Example 2

[0099] Please see Figure 2 , Figure 2 This is a flowchart illustrating another dynamic management method for differentiated business data disclosed in an embodiment of the present invention. Figure 2The described dynamic management method for differentiated business data can be applied to a dynamic management device for differentiated business data, and this embodiment of the invention is not limited thereto. Figure 2 As shown, the dynamic management method for differentiated business data can include the following operations:

[0100] 201. Determine all logic units to be arranged and the unit data of each logic unit.

[0101] 202. Perform a preset metadata transformation operation on the unit data of each logical unit to obtain the transformed data of each logical unit.

[0102] 203. Determine the logical parameters according to the preset flowchart construction algorithm, and generate at least one logical flowchart based on the logical parameters. The logical parameters are the parameters required to construct the logical flowchart.

[0103] 204. Based on the transformation data of all logical units, all logical flowcharts, and the preset data deployment scheduling algorithm, generate a business scheduling model.

[0104] 205. Based on the business scheduling model, perform data orchestration and scheduling operations on the input business data to obtain the orchestration and scheduling results corresponding to the business data.

[0105] For further descriptions of steps 201-205 in this embodiment of the invention, please refer to the other specific descriptions of steps 101-105 in Embodiment 1. These descriptions will not be repeated in this embodiment of the invention.

[0106] 206. After determining that the process return value is the orchestration and scheduling result corresponding to the business data, analyze the historical orchestration and scheduling data and the orchestration and scheduling results to obtain the analysis results.

[0107] In this embodiment of the invention, the historical orchestration and scheduling data is the data corresponding to the recorded business logic flowchart. The historical orchestration and scheduling data includes verification parameters used to perform exception verification operations.

[0108] 207. When the analysis results indicate that the verification match value between the orchestration and scheduling results and the verification parameters exceeds the standard verification match value, perform a logic correction operation on the business logic flowchart based on historical orchestration and scheduling data and verification parameters.

[0109] In this embodiment of the invention, step 207 is performed to make the verification match value between the corrected data arrangement result and the verification parameter lower than or equal to the standard verification match value.

[0110] It should be noted that, in practical applications, the generated business scheduling model differs from traditional business data processing methods. A corresponding orchestration module (engine) aspect has been added to this business scheduling model. When input data is detected, the orchestration engine aspect is activated, which can perform online visualization enhancement of existing business methods. Specifically, the orchestration engine aspect can be used to take the result of each engine execution as a process parameter and reintroduce it into the context of the original / real-time process, thus achieving the function of keeping the input parameter return value unchanged.

[0111] It is evident that implementation Figure 2 The described dynamic management method for differentiated business data, after obtaining the orchestration and scheduling results, sets up a corresponding verification and analysis process. This process verifies and analyzes the orchestration and scheduling results using historical orchestration and scheduling data and the verification parameters included in that data. Specifically, if the verification match between the orchestration and scheduling results and the verification parameters exceeds the standard verification match value, a logical correction operation is automatically performed on the orchestration and scheduling results, thereby improving the accuracy of the final orchestration and scheduling results. Furthermore, this verification process can also be used to optimize the business scheduling model, thus improving the reliability of the final business scheduling module model.

[0112] In an optional embodiment, the method of performing data orchestration and scheduling operations on the input business data according to the service scheduling model to obtain the orchestration and scheduling results corresponding to the business data specifically includes:

[0113] Based on the input business data, determine the business process code corresponding to that business data;

[0114] Based on the business scheduling model, determine the business logic flowchart that matches the business process code;

[0115] Using the starting node included in the business logic flowchart as the base point, and according to the execution logic corresponding to the business logic flowchart, the business data is sequentially input into each execution logic node of the business logic flowchart;

[0116] Collect the process return values ​​of the end nodes included in the business logic flowchart, and after determining that the process return value is not the preset start return value, determine that the process return value is the orchestration and scheduling result corresponding to the business data.

[0117] In this optional embodiment, after determining that the process return value is not a preset initial return value and before determining that the process return value is the orchestration and scheduling result corresponding to the business data, the method further includes:

[0118] Obtain the deployment information of the business logic flowchart. The deployment information is used to record version change information after the business logic flowchart is executed.

[0119] When the deployment information indicates that the version of the business logic flowchart has changed after the execution of the business logic flowchart, a retrospective information is generated and the operation corresponding to the orchestration and scheduling result corresponding to the business data is triggered. The retrospective information is used to trace the deployment information back to the deployment information before the execution of the business logic flowchart.

[0120] As can be seen, in this optional embodiment, for the input business data, the business process code and the business logic flowchart matching the business process code can be automatically determined. Thus, with the starting node of the business logic flowchart as the base point, the business data is intelligently input into each logical point, thereby realizing the data orchestration and scheduling of the business data and improving the processing efficiency and accuracy of the data orchestration and scheduling of the business data. In addition, after each call to deploy the business logic flowchart, corresponding backtracking information can be generated to facilitate the subsequent call to the previous version of the business logic flowchart.

[0121] Example 3

[0122] Please see Figure 3 , Figure 3 This is a schematic diagram of the structure of a dynamic management and control device for differentiated business data disclosed in an embodiment of the present invention. The dynamic management and control device for differentiated business data can be a dynamic management and control terminal for differentiated business data, a dynamic management and control equipment for differentiated business data, a dynamic management and control system for differentiated business data, or a dynamic management and control server for differentiated business data. The dynamic management and control server for differentiated business data can be a local server, a remote server, or a cloud server (also known as a cloud server). When the dynamic management and control server for differentiated business data is a non-cloud server, the non-cloud server can communicate with the cloud server. This embodiment of the present invention does not impose any limitations. Figure 3 As shown, the dynamic management and control device for differentiated business data may include a determination module 301, a data transformation module 302, a generation module 303, and an orchestration and scheduling module 304, wherein:

[0123] The determination module 301 is used to determine all the logic units to be arranged and the unit data of each logic unit.

[0124] The data conversion module 302 is used to perform preset metadata conversion operations on the unit data of each logical unit to obtain the converted data of each logical unit.

[0125] Optionally, the data conversion module 302 performs a preset metadata conversion operation on the unit data of each logical unit, and the specific methods for obtaining the converted data of each logical unit include:

[0126] For each logical unit, determine the unit type of the logical unit. The unit type includes a first type or a second type. The first type is the type corresponding to the logical unit and the data processing space of the business scheduling model to be built being in the same virtual space. The second type is the type that matches the preset REST service processing logic.

[0127] Based on the unit type of each logical unit, a preset metadata transformation operation is performed on the unit data of that logical unit to obtain the transformed data of each logical unit.

[0128] As can be seen, in the embodiments of the present invention, when processing each logical unit, the unit type of each logical unit can be intelligently determined, thereby adjusting the metadata conversion method used to process the logical unit according to the unit type of each logical unit, which improves the accuracy and reliability of the final converted metadata.

[0129] The determination module 301 is also used to determine logical parameters based on a preset flowchart construction algorithm.

[0130] The generation module 303 is used to generate at least one logic flowchart based on logic parameters, which are the parameters required to construct the logic flowchart.

[0131] It should be noted that logical parameters include orchestration parameters, structure and return value parameters, node logical parameters, and sequence parameters;

[0132] The orchestration parameters include target information required for managing the logic flowchart. The target information includes identification information, encoding information, and description information. The identification information is the identification information corresponding to each logical component in the logic flowchart. The encoding information includes the encoding and decoding method used to construct the logic flowchart. The description information includes the description information of the functions corresponding to all logical components and / or the logic flowchart.

[0133] The structure and return value parameters are used to define the data structure collected when building the logic flowchart and the corresponding return result data when the completed logic flowchart is executed;

[0134] Node logic parameters are used to indicate the node logic corresponding to all logic nodes used in the construction logic flowchart;

[0135] The sequence parameter is used to define the execution order between different logical nodes.

[0136] Furthermore, each logical flowchart includes a corresponding flowchart code. The flowchart code is used to call the logical flowchart corresponding to the flowchart code. The flowchart code is also used to perform at least one of the following operations on all logical flowcharts under the flowchart set controlled by the flowchart code: data storage, data update, and data verification.

[0137] The generation module 303 is also used to generate a business scheduling model based on the transformation data of all logical units, all logical flowcharts and a preset data deployment scheduling algorithm. The business scheduling model is used to perform data orchestration and scheduling operations on the data input to the business scheduling model.

[0138] The orchestration and scheduling module 304 is used to perform data orchestration and scheduling operations on the input business data according to the business scheduling model, and obtain the orchestration and scheduling results corresponding to the business data. The orchestration and scheduling results are used to feed back to the personnel responsible for processing the business data so that the personnel can verify the orchestration and scheduling results.

[0139] It is evident that implementation is as follows Figure 3 The described dynamic management and control device for differentiated business data can intelligently perform metadata transformation operations on the unit data of all determined logical units to be orchestrated, in order to construct a business scheduling model. This generates several logical flowcharts based on determined logical parameters. Finally, based on all the transformed data, the generated logical flowcharts, and a data deployment scheduling algorithm, a business scheduling model is generated for orchestrating and scheduling the input differentiated business data. This generated business scheduling model, based on several pre-prepared logical flowcharts and various intelligent logical orchestration algorithms, can support differentiated business and dynamic business invocation requirements, helping to reduce the management difficulty of differentiated businesses while improving management efficiency and accuracy.

[0140] In an optional embodiment, such as Figure 4 As shown, the orchestration and scheduling module 304 includes a determination submodule 3041 and a logic processing submodule 3042, wherein:

[0141] The determination submodule 3041 is used to determine the business process code corresponding to the input business data.

[0142] Submodule 3041 is also used to determine the business logic flowchart that matches the business process code based on the business scheduling model.

[0143] The logic processing submodule 3042 is used to input business data into each execution logic node of the business logic flowchart in sequence, based on the starting node included in the business logic flowchart and according to the execution logic corresponding to the business logic flowchart.

[0144] The logic processing submodule 3042 is also used to collect the process return values ​​of the end nodes included in the business logic flowchart, and after determining that the process return value is not the preset start return value, determine that the process return value is the orchestration and scheduling result corresponding to the business data.

[0145] Optional, such as Figure 4As shown, the orchestration and scheduling module 304 also includes a deployment processing submodule 3043 and a generation submodule 3044, wherein:

[0146] The deployment processing submodule 3043 is used to obtain the deployment information of the business logic flowchart after the logic processing submodule 3042 determines that the process return value is not the preset initial return value, and before it determines that the process return value is the orchestration and scheduling result corresponding to the business data. The deployment information is used to record the version change information after the execution of the business logic flowchart.

[0147] The generation submodule 3044 is used to generate backtracking information and trigger the execution of the operation corresponding to the orchestration and scheduling result corresponding to the business data when the version of the business logic flowchart is changed after the deployment information indicates that the business logic flowchart has been executed. The backtracking information is used to backtrack the deployment information to the deployment information before the execution of the business logic flowchart.

[0148] It is evident that implementation is as follows Figure 4 The described dynamic management and control device for differentiated business data can automatically determine the business process code and the matching business logic flowchart for the input business data. Using the starting node of the business logic flowchart as the base point, it intelligently inputs business data into each logical point, thereby achieving data orchestration and scheduling of business data and improving the processing efficiency and accuracy of business data execution orchestration and scheduling. Furthermore, after each deployment of the business logic flowchart, it can generate corresponding backtracking information to facilitate subsequent calls to the previous version of the business logic flowchart.

[0149] In another alternative embodiment, such as Figure 4 As shown, the device also includes an analysis module 305 and a logic correction module 306, wherein:

[0150] The analysis module 305 is used to analyze historical orchestration and scheduling data and orchestration and scheduling results after the logic processing submodule 3042 determines that the process return value is the orchestration and scheduling result corresponding to the business data, and to obtain the analysis results. The historical orchestration and scheduling data is the data corresponding to the recorded call to the business logic flowchart. The historical orchestration and scheduling data includes the verification parameters used to perform the exception verification operation.

[0151] The logic correction module 306 is used to perform a logic correction operation on the business logic flowchart based on historical orchestration data and verification parameters when the analysis result indicates that the verification match value between the orchestration and scheduling result and the verification parameters exceeds the standard verification match value, so that the verification match value between the corrected data orchestration result and the verification parameters is lower than or equal to the standard verification match value.

[0152] It is evident that implementation is as follows Figure 4The described dynamic management and control device for differentiated business data, after obtaining the orchestration and scheduling results, sets up a corresponding verification and analysis process. Through historical orchestration and scheduling data and the verification parameters included in the historical orchestration and scheduling data, it verifies and analyzes the orchestration and scheduling results. In cases where the verification match value between the orchestration and scheduling results and the verification parameters exceeds the standard verification match value, it automatically performs a logical correction operation on the orchestration and scheduling results, thereby improving the accuracy of the final orchestration and scheduling results. On the other hand, the verification process can also be used to optimize the business scheduling model, which is conducive to improving the reliability of the final business scheduling module model.

[0153] Example 4

[0154] Please see Figure 5 , Figure 5 This is a schematic diagram of the structure of another dynamic management and control device for differentiated business data disclosed in an embodiment of the present invention. Figure 5 As shown, the dynamic management and control device for differentiated business data may include:

[0155] Memory 401 storing executable program code;

[0156] Processor 402 coupled to memory 401;

[0157] The processor 402 calls the executable program code stored in the memory 401 to execute the steps in the dynamic management and control method for differentiated business data described in Embodiment 1 or Embodiment 2 of the present invention.

[0158] Example 5

[0159] This invention discloses a computer storage medium storing computer instructions. When these computer instructions are invoked, they are used to execute the steps in the dynamic management and control method for differentiated business data described in Embodiment 1 or Embodiment 2 of this invention.

[0160] Example 6

[0161] This invention discloses a computer program product, which includes a non-transitory computer storage medium storing a computer program, and the computer program is operable to cause a computer to execute the steps in the dynamic management method for differentiated business data described in Embodiment 1 or Embodiment 2.

[0162] The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0163] Through the detailed description of the above embodiments, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer storage medium, including read-only memory (ROM), random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), one-time programmable read-only memory (OTPROM), electrically-erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, disk storage, magnetic tape storage, or any other computer-readable medium that can be used to carry or store data.

[0164] Finally, it should be noted that the dynamic management method and apparatus for differentiated business data disclosed in the embodiments of the present invention are merely preferred embodiments of the present invention and are only used to illustrate the technical solutions of the present invention, not to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for dynamic management and control of differentiated business data, characterized in that, The method includes: Determine all logical units to be arranged and the unit data of each logical unit; Perform a preset metadata transformation operation on the unit data of each logical unit to obtain the transformed data of each logical unit; The logical parameters are determined according to a preset flowchart construction algorithm, and at least one logical flowchart is generated according to the logical parameters, wherein the logical parameters are the parameters required to construct the logical flowchart; Based on the transformation data of all the logical units, all the logical flowcharts, and a preset data deployment and scheduling algorithm, a business scheduling model is generated. The business scheduling model is used to perform data orchestration and scheduling operations on the data input to the business scheduling model. According to the business scheduling model, the data orchestration and scheduling operation is performed on the input business data to obtain the orchestration and scheduling result corresponding to the business data. The orchestration and scheduling result is used to feed back to the personnel responsible for processing the business data so that the personnel can verify the orchestration and scheduling result. The step of performing the data orchestration and scheduling operation on the input business data according to the business scheduling model to obtain the orchestration and scheduling result corresponding to the business data includes: Based on the input business data, determine the business process code corresponding to that business data; Based on the business scheduling model, determine the business logic flowchart that matches the business process code; Using the starting node included in the business logic flowchart as the base point, the business data is sequentially input into each execution logic node of the business logic flowchart according to the execution logic corresponding to the business logic flowchart; Collect the process return values ​​of the end nodes included in the business logic flowchart, and after determining that the process return value is not a preset start return value, determine that the process return value is the orchestration and scheduling result corresponding to the business data; After determining that the process return value is not a preset initial return value, and before determining that the process return value is the orchestration and scheduling result corresponding to the business data, the method further includes: Obtain the deployment information of the business logic flowchart, wherein the deployment information is used to record version change information after the business logic flowchart is executed; When the deployment information indicates that the version of the business logic flowchart has changed after the execution of the business logic flowchart, a retrospective information is generated and the operation of determining that the return value of the process is the orchestration and scheduling result corresponding to the business data is triggered. The retrospective information is used to retrospectively deploy the information back to the deployment information before the execution of the business logic flowchart.

2. The dynamic management and control method for differentiated business data according to claim 1, characterized in that, The logical parameters include orchestration parameters, structure and return value parameters, node logical parameters, and sequence parameters; The orchestration parameters include target information required for managing the logic flowchart. The target information includes identification information, encoding information, and description information. The identification information is the identification information corresponding to each logical component in the logic flowchart. The encoding information includes the encoding and decoding method used to construct the logic flowchart. The description information includes description information of all logical components and / or the functions corresponding to the logic flowchart. The structure and return value parameters are used to define the data structure collected when constructing the logic flowchart and the corresponding return result data when executing the constructed logic flowchart; The node logic parameters are used to indicate the node logic corresponding to all logic nodes used in constructing the logic flowchart; The sequence parameter is used to define the execution order between different logical nodes.

3. The dynamic management and control method for differentiated business data according to claim 2, characterized in that, Each of the logical flowcharts includes a corresponding flowchart code. The flowchart code is used to call the logical flowchart corresponding to the flowchart code. The flowchart code is also used to perform at least one of the following operations on all the logical flowcharts under the flowchart set controlled by the flowchart code: data storage, data update, and data verification.

4. The method for dynamic management and control of differentiated business data according to any one of claims 1-3, characterized in that, After determining that the return value of the process is the orchestration and scheduling result corresponding to the business data, the method further includes: Analyze historical orchestration and scheduling data and the orchestration and scheduling results to obtain analysis results. The historical orchestration and scheduling data is the data corresponding to the recorded calls to the business logic flowchart. The historical orchestration and scheduling data includes verification parameters used to perform exception verification operations. When the analysis result indicates that the verification match value between the orchestration and scheduling result and the verification parameter exceeds the standard verification match value, a logic correction operation is performed on the business logic flowchart based on the historical orchestration and scheduling data and the verification parameter, so that the verification match value between the corrected data orchestration result and the verification parameter is lower than or equal to the standard verification match value.

5. The dynamic management and control method for differentiated business data according to claim 4, characterized in that, The step of performing a preset metadata transformation operation on the unit data of each logical unit to obtain transformed data for each logical unit includes: For each logical unit, the unit type of the logical unit is determined. The unit type includes a first type or a second type. The first type is the type corresponding to the logical unit and the data processing space of the business scheduling model to be constructed being in the same virtual space. The second type is the type that matches the preset REST service processing logic. Based on the unit type of each logical unit, a preset metadata transformation operation is performed on the unit data of the logical unit to obtain the transformed data of each logical unit.

6. A dynamic management and control device for differentiated business data, characterized in that, The apparatus is used to execute the dynamic management and control method for differentiated business data as described in any one of claims 1-5, and the apparatus comprises: The determination module is used to determine all logical units to be arranged and the unit data of each logical unit; The data conversion module is used to perform a preset metadata conversion operation on the unit data of each logical unit to obtain the converted data of each logical unit; The determining module is further configured to determine logical parameters based on a preset flowchart construction algorithm; A generation module is used to generate at least one logic flowchart based on the logic parameters, wherein the logic parameters are parameters required to construct the logic flowchart. The generation module is further configured to generate a business scheduling model based on the transformation data of all the logical units, all the logical flowcharts, and a preset data deployment scheduling algorithm. The business scheduling model is used to perform data orchestration and scheduling operations on the data input to the business scheduling model. The orchestration and scheduling module is used to perform the data orchestration and scheduling operation on the input business data according to the business scheduling model, and obtain the orchestration and scheduling result corresponding to the business data. The orchestration and scheduling result is used to feed back to the personnel responsible for processing the business data so that the personnel can verify the orchestration and scheduling result.

7. A dynamic management and control device for differentiated business data, characterized in that, The device includes: Memory containing executable program code; A processor coupled to the memory; The processor calls the executable program code stored in the memory to execute the dynamic management and control method for differentiated business data as described in any one of claims 1-5.

8. A computer storage medium, characterized in that, The computer storage medium stores computer instructions, which, when invoked, are used to execute the dynamic management and control method for differentiated business data as described in any one of claims 1-5.

Citation Information

Patent Citations

  • Distributed software version release method and system thereof

    CN106453549A

  • Business process arrangement method and device, computer equipment and storage medium

    CN114595919A