Business model data processing method and device, computer equipment, readable storage medium and program product

Abstract

The invention relates to a business model data processing method and device, computer equipment, a readable storage medium and a program product. The method comprises the following steps: pre-generating a cache configuration pool containing each configuration item of business model data, querying the cache configuration pool based on a determined target configuration item and target business model data, and determining each associated entity data associated with the target business model data and each configuration item associated with the target configuration item; and according to the target business model data, the associated entity data, the target configuration item and each associated configuration item, determining a query result corresponding to the entity query instruction. Compared with traditional manual data processing, according to the scheme, the query result is formed by pre-caching the configuration pool of the configuration items, extracting the target business model data and the associated entity data corresponding to the target business model data, and extracting the target configuration items and the associated configuration items of the target configuration items, and the business model data processing efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a business model data processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] As businesses in enterprises develop, they need to use cloud-based distributed databases to manage the business data of each business. Business data management needs to be implemented through business models. Currently, business models are very complex, and the data processing process of business models involves data processing in multiple environments. To ensure the normal operation of the business, the efficiency of the data processing process of the business model needs to be guaranteed. Currently, the way to process data for business models is usually through manual data processing. However, as the business expands, the data components that the business model needs to process are complex, and manual data processing will reduce the efficiency of data processing.

[0003] Therefore, the current method of processing data for business models has the defect of low processing efficiency. Summary of the invention

[0004] Based on this, it is necessary to provide a business model data processing method, device, computer equipment, computer-readable storage medium and computer program product that can improve processing efficiency in response to the above technical problems.

[0005] In a first aspect, the present application provides a method for processing business model data, the method comprising:

[0006] Obtaining an entity query instruction, and determining corresponding target configuration items and target business model data according to the entity query instruction;

[0007] According to the target configuration item and the target business model data, a cache configuration pool is queried to determine each associated entity data associated with the target business model data and each configuration item associated with the target configuration item; the cache configuration pool includes each configuration item corresponding to each business model data;

[0008] A query result corresponding to the entity query instruction is determined according to the target business model data, each of the associated entity data, the target configuration item, and each of the configuration items associated with the target configuration item.

[0009] In a second aspect, the present application provides a business model data processing device, the device comprising:

[0010] An acquisition module, used to acquire an entity query instruction, and determine corresponding target configuration items and target business model data according to the entity query instruction;

[0011] A determination module, configured to query a cache configuration pool according to the target configuration item and the target business model data, and determine each associated entity data associated with the target business model data, and each configuration item associated with the target configuration item; the cache configuration pool includes each configuration item corresponding to each business model data;

[0012] A processing module is used to determine a query result corresponding to the entity query instruction according to the target business model data, each of the associated entity data, the target configuration item and each of the configuration items associated with the target configuration item.

[0013] In a third aspect, the present application provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the above method when executing the computer program.

[0014] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program implements the steps of the above method when executed by a processor.

[0015] In a fifth aspect, the present application provides a computer program product, including a computer program, which implements the steps of the above method when executed by a processor.

[0016] The above-mentioned business model data processing method, apparatus, computer equipment, computer-readable storage medium and computer program product pre-generate a cache configuration pool containing various configuration items of business model data, query the cache configuration pool based on the determined target configuration item and target business model data, determine the various associated entity data associated with the target business model data and the various configuration items associated with the target configuration item, and determine the query result corresponding to the entity query instruction according to the target business model data, the associated entity data, the target configuration item and its associated configuration items. Compared with the traditional manual data processing, this solution pre-caches the configuration pool of configuration items, extracts the target business model data and its corresponding associated entity data, as well as the target configuration item and its associated configuration items, forms the query result, and improves the efficiency of business model data processing. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0018] Figure 1A flowchart of a method for processing business model data in one embodiment;

[0019] Figure 2 A schematic diagram of a flow chart of configuring a pool cache step in an embodiment;

[0020] Figure 3 A schematic diagram of a flow chart of a first association relationship determination step in an embodiment;

[0021] Figure 4 A schematic diagram of a flow chart of a second association relationship determination step in one embodiment;

[0022] Figure 5 A schematic diagram of a flow chart of a data extraction step in an embodiment;

[0023] Figure 6 A schematic diagram of a data backup process in one embodiment;

[0024] Figure 7 A schematic diagram of a flow chart of a data synchronization step in an embodiment;

[0025] Figure 8 is a structural block diagram of a business model data processing device in one embodiment;

[0026] Fig. 9 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0027] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0028] In one embodiment, Figure 1 As shown, a business model data processing method is provided. This embodiment uses the method applied to a server as an example for illustration. It can be understood that the method can also be applied to a terminal, and can also be applied to a system including a terminal and a server, and is implemented through the interaction between the terminal and the server, including the following steps S202 to S206. Among them:

[0029] Step S202: Acquire an entity query instruction, and determine corresponding target configuration items and target business model data according to the entity query instruction.

[0030] Among them, the above-mentioned server can be a distributed cloud platform that can process data for human resources business. When processing data for the business model, it includes data extraction, data backup and data synchronization. For example, the business model can be a human resources business model, data extraction can be to query the data in the business model to form a data packet, data backup can be to backup the queried data packet, and data synchronization can be the data migration process of synchronizing the data packet to other environments. The human resources business model is a very complex business model, including the migration of model configuration data such as customized historical business models and multi-entity query models. In the process of configuration data migration, data configuration of multiple environments is involved, such as test environment, UAT (user acceptance testing) environment, production drill environment, production environment, etc. The process of migrating to different environments for configuration is the data synchronization process.

[0031] When processing the business model data of the human resources business model, it is necessary to extract the corresponding entity data and configuration items based on the data query instructions and the reference relationship and association relationship between the business model data. The entity data may be the entity corresponding to the business model data, and the configuration items may include multiple attributes and parameters related to human resources. The server may receive an entity query instruction triggered by a user, for example, the user selects relevant business model data and configuration items to form an entity query instruction. The server may determine the corresponding target configuration items and target business model data according to the entity query instruction. Thus, the server may extract the associated entity data and configuration items based on the target configuration items and target business model data.

[0032] Step S204, query the cache configuration pool according to the target configuration item and the target business model data to determine each associated entity data associated with the target business model data and each configuration item associated with the target configuration item; the cache configuration pool includes each configuration item corresponding to each business model data.

[0033] Among them, the server can pre-build a cache configuration pool. For example, the server can obtain the associated configuration items based on the data types of metadata and business model data, and further cache the configuration items to obtain the above-mentioned configuration pool. Among them, the configuration pool caches the various configuration items corresponding to the various business model data, as well as the association relationship between the various configuration items. The server can also determine the entity data associated with the business model data based on the configuration items. For example, the server can construct the configuration items of the entity data based on the association relationship between the entity data. Thus, the server can query the cache configuration pool according to the above-mentioned target configuration items and target business model data, and determine the various associated entity data associated with the target business model data, as well as the various configuration items associated with the target configuration items. Thus, the server can realize the extraction of business model-related configurations and entities from the configuration pool. Among them, the above-mentioned target business model data, the various associated entity data, the target configuration items, and the various configuration items associated with the target configuration items can all be data related to human resources business.

[0034] Step S206: determining a query result corresponding to the entity query instruction according to the target business model data, each associated entity data, the target configuration item and each configuration item associated with the target configuration item.

[0035] After the server obtains the target business model data, each associated entity data, target configuration item, and each configuration item associated with the target configuration item based on the cached configuration pool, the query result corresponding to the entity query instruction can be obtained according to the target business model data, each associated entity data, target configuration item, and each configuration item associated with the target configuration item. The query result can be output in the form of a data packet. For example, the server can generate a corresponding data packet according to the target business model data, each associated entity data, target configuration item, and each configuration item associated with the target configuration item, that is, the server puts each configuration item queried and its referenced entity data into a stack in a first-in-last-out manner, and generates the data packet through a FILO (First In Last Out) algorithm. Thus, the server can obtain each configuration item associated with the target configuration item, and each associated entity data corresponding to the target business model data. Based on the above configuration items and entity data, the server can determine the configuration and entity data related to the human resources business model. Thus, the server can back up each configuration item and entity data in the above data packet, or synchronize the above configuration items and entity data to other environments to achieve configuration migration. The server can thus quickly respond to data extraction, backup and synchronization of various complex business models, and ensure data security through encryption algorithms.

[0036] In the above-mentioned business model data processing method, a cache configuration pool containing various configuration items of business model data is generated in advance, and the cache configuration pool is queried based on the determined target configuration item and target business model data to determine the various associated entity data associated with the target business model data and the various configuration items associated with the target configuration item. According to the target business model data, the associated entity data, the target configuration item and its associated configuration items, the query result corresponding to the entity query instruction is determined. Compared with the traditional manual data processing, this solution pre-caches the configuration pool of configuration items, extracts the target business model data and its corresponding associated entity data, as well as the target configuration item and its associated configuration items, to form a query result, thereby improving the efficiency of business model data processing.

[0037] In one embodiment, it also includes: obtaining metadata entities corresponding to each business model data, and determining business types of each business model data according to each metadata entity; obtaining preset configuration policies corresponding to each business type, and configuration items corresponding to the metadata entity; determining first association relationships and second association relationships between configuration items according to each preset configuration policy; the first association relationship represents the data reference association between configuration items, and the second association relationship represents the entity association between configuration items; generating a cache configuration pool according to each configuration item, each first association relationship and each second association relationship.

[0038] In this embodiment, the server can pre-configure the cache based on the business model data, and then obtain the above-mentioned configuration pool. Among them, the above-mentioned business model data can be data related to human resources business, and the human resources business includes multiple businesses, each business has different business types, and the above-mentioned business model data has corresponding metadata entities. Among them, metadata is data about data, which describes the structure, content, source, quality, context and other attributes of the data. In this embodiment, metadata plays a vital role. It is the cornerstone for realizing functions such as data integration, system interoperability, and business automation. Through metadata, users can clearly understand the overall picture of the data, including the fields, types, relationships, etc. of the data, so as to perform data management and business operations more efficiently. Thereby, the server can obtain the metadata entities corresponding to the above-mentioned business model data, and determine the business types of each business model data according to each metadata entity.

[0039] For different business types, the configuration strategies used by the server when configuring them are different. The server can determine the preset configuration strategies corresponding to each business type according to each business type, and determine the configuration items corresponding to the metadata entity according to each business type. The configuration items corresponding to the metadata entity can be determined based on the reference information in the metadata entity. Thus, the server can determine the first association relationships and the second association relationships between the configuration items according to the above preset configuration strategies.

[0040] Among them, the first association relationship and the second association relationship can represent different types of association relationships. The first association relationship represents the data reference relationship between various configuration items, for example, a configuration item references certain attributes of another configuration item, but there is no rigid or direct dependency between them, that is, it can be a logical reference relationship. The second association relationship represents the entity association between various configuration items, for example, the relationship associated with a certain configuration item is clearly indicated in the configuration item. The server can generate a cache configuration pool based on the above-mentioned configuration items, each first association relationship and each second association relationship. Among them, the above-mentioned preset configuration policy can correspond to the business type.

[0041] In one embodiment, each preset configuration strategy corresponding to each business type is obtained, including: for each business type, determining one or more of the historical business model data configuration, verification configuration, data matching dimension configuration, and encryption configuration according to the business type; according to one or more of the historical business model data configuration, verification configuration, data matching dimension configuration, and encryption configuration, obtaining the preset configuration strategy corresponding to the business type.

[0042] In this embodiment, the above-mentioned business types may include multiple ones, and they may be various business types corresponding to human resources business. For each business type, the server may determine the historical business model data configuration according to the above-mentioned business type, such as the configuration information of the business type in the business model of the historical version, and may also determine one or more of the verification configuration, data matching dimension configuration, and encryption configuration. Among them, the verification configuration represents the policy configuration for verifying business data during synchronization; the data matching dimension configuration represents the configuration of the matching strategy used when performing data query; and the encryption configuration represents the configuration of the strategy when encrypting business data. Thus, the server may obtain the preset configuration policy corresponding to the business type according to one or more of the above-mentioned historical business model data configuration, verification configuration, data matching dimension configuration, and encryption configuration. Thus, the server may determine the first association relationship and the second association relationship between each configuration item based on the above-mentioned preset configuration policy, and then the server generates a cache configuration pool based on each configuration item, each first association relationship, and each second association relationship.

[0043] Specifically, Figure 2 As shown, Figure 2 The flowchart of the configuration pool cache step in one embodiment is shown. The server can obtain each business model data, also called configuration item business entity, and perform metadata analysis on it to obtain metadata entity, also called business entity. Thus, the server can perform basic configuration of configuration items based on business entities. Among them, the server configures the relevant business entity as a configuration item scheme according to the needs of business collection. The server identifies whether the business entity object is a historical entity, whether it is a controlled entity, which binding business objects are referenced, and the basic data of the landing storage based on the configuration item, such as whether the business unit, administrative organization or other information is referenced. When it is determined to be a controlled entity, the default configuration of the controlled entity is obtained, and when it is determined to be a historical entity, the default configuration of the historical entity is obtained, and the post-service governance registration is performed based on the default configuration of the controlled entity and the default configuration of the historical entity, and whether it has a binding table or self-binding table attribute, and then the server can determine the configuration of the associated sub-entity. Among them, the controlled entity represents the entity data controlled by permissions or policies in the system, and the historical entity represents the entity data of the historical version. The historical entity exists in the historical model, and the historical model represents the data version distinction within the business object, that is, the data version model that changes with time.

[0044] The server can then determine the business type of the above business entity and identify which business model the business object belongs to. The server can perform flexible configuration based on the identified business model type. For example, the server detects whether the above business entity needs all versions of historical model data, whether it needs to perform mandatory verification of the existence of referenced basic data, determine the configuration method of data matching dimensions, determine the data attribute value encryption configuration method, and determine the configuration of post-services and other sub-granular configurations.

[0045] Among them, Figure 3 As shown, Figure 3 A flowchart of the first association determination step in an embodiment. The dependency between configuration items can be a virtual dependency, i.e., the first association mentioned above. Specifically, it includes but is not limited to the association between the salary schedule template and the salary accounting scenario, work process design, salary calculation steps, salary accounting group and salary period in the human resources business; and the association between the salary accounting scenario and the calculation rules, post-accounting processing plan, accounting list rules, salary calculation method, and accounting list display plan; the calculation rules and salary items; the association between the salary period and the frequency, etc. The above-mentioned first associations are only reference relationships based on references, and there is no need to configure specific dependent associations.

[0046] The server can also configure the configuration item associated sub-entities. If the server detects that the metadata entity does not reference the association relationship of the basic data, but must be transmitted together as a data packet, the server can configure the corresponding association sub-entity solution, that is, the determination of the above-mentioned second association relationship. Figure 4 As shown, Figure 4 The flowchart of the second association relationship determination step in one embodiment is shown. The second association relationship includes, but is not limited to, associations between exception schemes and rule engines, policy management, decision tables, and runtime rules in human resources business. Each sub-entity of the above association can be used as subsequent association entity data, and the associated sub-entities are stored in a tree structure, and the server can configure multiple levels of association entities to form a cascading association relationship. Thus, the server can perform configuration pool cache management based on the above configuration items, the above first association relationship, and the second association relationship. For example, the server saves the information that has been configured and generated into the redis (RemoteDictionary Server) cache to form a cache configuration pool.

[0047] Thus, the server uses the cache technology to cache the metadata entities in all configuration pools. For example, it can be an entity configuration pool based on the solution configuration, reducing the problem of data input and output at the database level. And through the pooling technology, this embodiment can also solve the performance problem of data extraction and synchronization. The above cache configuration pool can also be expanded. For example, the server can achieve scalability and robustness in the solution through factory registration technology.

[0048] Through the above embodiments, the server uses the business model data and the corresponding preset configuration policies to determine the configuration items, the first association relationship and the second association relationship of each corresponding metadata entity, and generates a corresponding cache configuration pool, and uses the cache configuration pool to perform query and extraction processing on the business model data, thereby improving the processing efficiency of the business model data.

[0049] In one embodiment, querying a cache configuration pool according to a target configuration item and a target business model data to determine each associated entity data associated with the target business model data and each configuration item associated with the target configuration item includes: obtaining a target business type of the target business model data, and determining, according to the target business type, a set of associated configuration items corresponding to the target configuration item and a set of associated entity data corresponding to the target business model data; for each configuration item in the associated configuration item set and each associated entity data in the associated entity data set, querying a cache configuration pool according to the configuration item and the associated entity data to obtain unqueried configuration items having a first association relationship with the configuration item and unqueried associated entity data having a second association relationship with the associated entity data; and returning to the step of querying the cache configuration pool according to the configuration item and the associated entity data according to the unqueried configuration items and the unqueried associated entity data, until each configuration item and each associated entity data has been queried in the cache configuration pool, and each configuration item and each associated entity data associated with the target configuration item is obtained.

[0050] In this embodiment, the above-mentioned target business model has a corresponding business type. For example, it can be a related business type in human resources business. The user can select the corresponding target business model data in the server, and perform data query and extraction based on the target business model data and its associated entity data and configuration items. Then, after obtaining the target business model data and target configuration items selected by the user, the server can obtain the target business type of the target business model data, and determine the associated configuration item set corresponding to the target configuration item according to the target business type. The server can also determine the associated entity data set corresponding to the target business model data according to the above-mentioned target business type. Among them, the associated configuration item combination includes multiple configuration items related to the target configuration item, but the reference dependency relationship between each configuration item and the target configuration item needs to be further determined. The associated entity data set includes multiple associated entity data related to the target business model data, but the reference dependency relationship between each associated entity data and the target business model data needs to be further determined.

[0051] The above target business types include historical business model entities and controlled business model entities. For different business types, the server may determine the associated entity data set in different ways.

[0052] In one embodiment, the step of determining the associated entity data set corresponding to the target business model data according to the target business type includes: if the target business type is a historical business model entity, obtaining each historical version identifier corresponding to the target business model data, generating an object relationship mapping query condition according to each historical version identifier, and determining the associated entity data set corresponding to the target business model data according to the object relationship mapping query condition.

[0053] In this embodiment, the server can determine the target business type of the target business model data. If the server detects that the target business type is a historical business model entity, the server can obtain the historical version identifiers corresponding to the target business model data, and generate object-relational mapping query conditions based on the historical version identifiers, that is, ORM (Object-Relational Mapping) query conditions. The server can determine the associated entity data set corresponding to the target business model based on the object-relational mapping query conditions as a dimension.

[0054] In addition, in another embodiment, if the server detects that the target business type is a controlled business model entity, the server can obtain the primary key information corresponding to the target business model data, and the above primary key information represents the primary key information of the data object in the target business model data, so that the server can determine the controlled association information corresponding to the target business model data based on the primary key information, and determine the associated entity data set corresponding to the target business model data based on the controlled association information.

[0055] After the server determines the above-mentioned associated configuration item set and associated entity data set, it can query the associated entity data and the configuration item. For each configuration item in the associated configuration item set, and for each associated entity data in the associated entity data set, the server can query the cache configuration pool according to the above-mentioned configuration items and associated entity data associated with the target configuration item, so that the server can query the cache configuration pool to obtain configuration items that have a first association relationship with the configuration item and have not been queried, and query to obtain the target associated entity data that has a second association relationship with the associated entity data and has not been queried. Among them, the configuration items that have not been queried represent configuration items whose association relationships have not been found in the cache configuration pool, and the associated entity data that have not been queried represent associated entity data whose association relationships have not been found in the cache configuration pool.

[0056] Thus, the server can return to the step of querying the cache configuration pool according to the configuration items and associated entity data that have not been queried, and perform further queries. The server can loop the above query process until each configuration item and each associated entity data has queried the cache configuration pool. The server can obtain each configuration item and each associated entity data associated with the target configuration item according to each queried configuration item and associated entity data. Thus, the server can obtain each configuration item associated with the target configuration item including the reference dependency relationship between each configuration item, and each associated entity data including the reference dependency relationship between entity data. The server can also form a corresponding data packet based on the above target configuration item, each configuration item associated with the target configuration item, the target business model data and each associated entity data, and output the query result based on the data packet.

[0057] In some embodiments, the above-mentioned querying the cache configuration pool according to the target configuration item and the target business model data to determine the various associated entity data associated with the target business model data and the various configuration items associated with the target configuration item also includes: obtaining the target business type of the target business model data, and determining, according to the target business type, a set of associated configuration items corresponding to the target configuration item and a set of associated entity data corresponding to the target business model data; for each configuration item in the associated configuration item set and each associated entity data in the associated entity data set, querying the cache configuration pool according to the configuration item and the associated entity data to obtain each configuration item and each associated entity data associated with the target configuration item.

[0058] In this embodiment, after obtaining the target business model data and target configuration items selected by the user, the server determines the target business type of the target business model data, and then determines the associated configuration item set corresponding to the target configuration item according to the target business type. The server can also determine the associated entity data set corresponding to the target business model data according to the above target business type. Then, the server can further determine the reference dependency relationship between the associated entity data and the target business model data.

[0059] For each configuration item in the associated configuration item set and each associated entity data in the associated entity data set, the server can query the cache configuration pool according to the configuration item and the associated entity data to obtain each configuration item and each associated entity data associated with the target configuration item. For example, the server can obtain each configuration item from the associated configuration item set, and based on multiple threads and the cache configuration pool, concurrently determine the first association relationship between each configuration item in the associated configuration item set, and then obtain each configuration item associated with the target configuration item;

[0060] The server can also obtain each associated entity data from the associated entity data set, and concurrently determine the second association relationship between each associated entity data in the associated entity data set based on multiple threads and the cache configuration pool, and then obtain each associated entity data associated with the target configuration item. Thus, each configuration item and each associated entity data associated with the target configuration item is queried based on multiple threads and the cache configuration pool, thereby improving the processing efficiency of the business model.

[0061] Specifically, Figure 5 As shown, Figure 5It is a flowchart of the data extraction step in one embodiment. The user can query the configuration items and entity data. The query results include the configuration items and their associated configuration items, as well as the entity data and the entity data associated with them. The server can parse the metadata model object when the query is needed, obtain the reference relationship between the configuration items and the entity, and can also package the metadata type of dependent cascade data, and ensure the dependency order between entities through the recursive algorithm and the stack FILO algorithm. Among them, for the data generation of each entity, the server can first determine which business model entity the current entity is, including historical model entities and controlled model entities. If the server detects that it is a historical model entity, the server can obtain the historical transaction entity data, that is, the server finds the corresponding boid with the data selected by the user, and determines whether to call the historical version data according to the configuration information. The server can also generate a query condition for the entity as a dimension ORM, and query the corresponding data in the ORM way to obtain the entity data set associated with the current entity and the business model, that is, the above-mentioned associated entity data set. Among them, boid is used to determine the identifiers of all versions in the historical model business object. If the server detects that it is a controlled model entity, the server can obtain data such as controlled association tables, that is, the server can parse the primary key information of the data object queried by the entity, and then perform JDBC (Java Database Connectivity) processing on the data of the controlled association table based on the table as the dimension. JDBC processing refers to the process of using the JDBC interface to connect to, query, insert, update, delete, and other operations with the database in a Java application.

[0062] The server can also generate cascaded associated sub-entity data based on the configuration item, that is, determine the configuration items associated with the above-mentioned various associated entity data and the target configuration item. For example, the server can first parse out the data of the configuration item entity that has been queried according to the configuration relationship of the associated sub-entities of the configuration item, and then parse out the value set of the corresponding associated attributes according to the relationship of the associated attributes. If there are multiple peer relationships, the server will start multiple threads from the thread pool to perform associated entity data query processing, and finally merge them into the sub-package with the configuration item, that is, obtain the various associated entity data associated with the above-mentioned target business model data and the various configuration items associated with the target configuration item. For example, the server can detect the basic information referenced in the associated sub-entity, detect whether the referenced basic information is a configuration item, and if not, the server determines the configuration item associated with the configuration item currently being queried, or the entity data associated with the associated entity data currently being queried based on the identifier, number and name of the basic information. If it is a configuration item, the server further determines whether it is a solution for this business, for example, whether it is a solution for human resources business. If so, it returns to the step of performing an associated query based on the configuration item. If not, the server can further detect whether it is a system-based configuration item, also known as a sys configuration item. If so, the server can obtain the entity code and identifier of the configuration item it depends on in the server platform as the queried configuration item associated with the target configuration item.

[0063] In addition, the server can also package and encrypt the configuration items and associated entity data queried above. For example, the server can query the corresponding business entity data according to the configuration information of the configuration item, and in the process of converting it into a Bean object, the server can encrypt the attribute value of the business entity data to ensure data security. In addition, the server can also integrate external scenarios, generate multi-entity query data using different fields of multiple entities, and generate multi-entity query entities through flexible combinations of flexible configuration schemes, thereby obtaining the above-mentioned target business model data and its corresponding associated entity data, as well as the target configuration item and its corresponding configuration item. Among them, the above-mentioned Bean object is the abbreviation of Enterprise Java Bean, that is, EJB, which is a component model.

[0064] That is, the server can obtain the entity model of the specified configuration item through the platform cache, and parse the entity reference relationship on the metadata model in multiple dimensions, such as the direct reference relationship of the metadata model, the relationship on the configuration scheme, etc. After parsing the current entity, the next metadata entity is parsed through the recursive algorithm, that is, after querying the current configuration item and entity data, the next configuration item and entity data are queried through the above recursive algorithm. In addition, the server can also use the directed graph algorithm to determine whether there is a circular reference in the reference relationship of the metadata model, and eliminate it when a circular reference is detected.

[0065] Through the above embodiment, the server can query and extract associated entity data and configuration items with multi-level association relationships based on the various configuration items and entity data in the cached configuration pool, using the selected target business model data and target configuration items, thereby improving the processing efficiency of the business model data.

[0066] In one embodiment, after determining the query result corresponding to the entity query instruction according to the target business model data, each associated entity data, the target configuration item and each configuration item associated with the target configuration item, it also includes: determining each business model entity to be synchronized according to the target business model data, each associated entity data, the target configuration item and each configuration item associated with the target configuration item in the query result; converting each business model entity into a backup script file; encrypting and compressing the backup script file, and backing up and saving the encrypted and compressed backup script file.

[0067] In this embodiment, after the server obtains the above query results, it can further back up the obtained query results. Among them, the above query results can be a data packet, which can include target business model data, various associated entity data, target configuration items, and various configuration items associated with the target configuration items. Before synchronizing the data to other environments, the server can back up the queried data. For example, the server can determine the various business model entities to be synchronized based on the above target business model data, various associated entity data, target configuration items, and various configuration items associated with the target configuration items. Among them, the business model entity includes the target configuration item and the entity corresponding to the configuration item, and can also include the target entity data and the entity corresponding to the associated entity data. The server can convert each business model entity into a backup script file, encrypt and compress the backup script file, and back up and save the encrypted and compressed backup script file.

[0068] Specifically, Figure 6 As shown, Figure 6 The flowchart of the data backup step in an embodiment is shown in FIG. 1 . The server can determine multiple entities based on the configuration items, and generate a data backup file before synchronization. Before synchronization and storage, the server can use the entity as a dimension, and for the data to be synchronized, use the data unique matching attribute rule to generate a unique matching attribute and value set for each entity to query the entity data, and then obtain the above-mentioned business model entities. The server converts the queried business model entity data into a dynamic object set, generates a file in the form of a ksql script, and generates a corresponding backup script, so that the server can roll back the data to a specified version based on the backup script file. Ksql is a database statement obtained based on a subset of SQL92. All applications that communicate with the above-mentioned database can achieve communication by sending ksql statements to the database server, which is independent of the user interface of the application.

[0069] The server can also encrypt and compress the backup script file. For example, for the backup script file generated by the backup, the server encrypts the backup script file through encryption algorithms such as sha-256, and then generates a compressed file through compression algorithms such as GZIP, that is, the encrypted and compressed backup script file is obtained, and its compression rate can reach 100 times, reducing storage pressure. When saving the backup script file, the server can save the above file on the file server, for example, the server uploads the encrypted and compressed backup script file to the file server, thereby reducing the storage pressure of the database in the server.

[0070] Through this embodiment, the server can use various configuration items and entity data in the query results to perform encrypted backup of the entity before data synchronization, thereby improving the security and stability of the business model data.

[0071] In one embodiment, after determining the query result corresponding to the entity query instruction according to the target business model data, each associated entity data, the target configuration item and each configuration item associated with the target configuration item, it also includes: obtaining a data synchronization request for the target business scenario, and obtaining the target business model data, each associated entity data, the target configuration item and each configuration item associated with the target configuration item in the data packet according to the data synchronization request; determining each first data to be synchronized and obtaining a business data table in the target business scenario according to the target business model data, each associated entity data, the target configuration item and each configuration item associated with the target configuration item; the business data table includes each second data; for each second data in the business data table, if there is target data matching the second data in the data packet, the storage location of the target data in the business data table is determined as the storage location corresponding to the second data; according to object-relationship mapping, synchronizing each first data and each target data with a determined storage location to the business data table in the target business scenario.

[0072] In this embodiment, the query result includes a data packet, which includes target business model data, various associated entity data, target configuration items, and various configuration items associated with the target configuration items. The server can use the queried data packet to synchronize data for the target business scenario to deploy the various business model data of the work order in the above configuration items in the target business scenario. For example, the server can obtain a data synchronization request for the target business scenario, and obtain the target business model data, various associated entity data, target configuration items, and various configuration items associated with the target configuration items in the data packet according to the data synchronization request. Among them, each configuration item includes an association relationship with each configuration item and each entity data, and each associated entity data includes a reference relationship of each referenced configuration item and an association relationship with the entity data.

[0073] The server can determine the first data to be synchronized based on the target business model data, the associated entity data, the target configuration item, and the configuration items associated with the target configuration item, and the server can also obtain the business data table in the target business scenario. The first data can be determined based on the target business model data, the associated entity data, the target configuration item, and the configuration items associated with the target configuration item; the business data table includes the second data, and the second data represents the business data currently existing in the target business environment.

[0074] For each second data in the business data table, the server can first detect whether there is target data that has been matched with the second data in the data packet. If so, the server can determine the storage location of the target data in the business data table as the storage location corresponding to the second data. For example, the identifier of the target data is updated to the data row identifier of the above-mentioned matched second data. After the server performs the above-mentioned matching process and replacement on each second data, it can synchronize each first data and each target data with a determined storage location to the business data table in the target business scenario according to object relational mapping, that is, the above-mentioned ORM algorithm.

[0075] Before synchronization, the server may also perform security verification on the acquired target business model data, each associated entity data, the target configuration item, and each configuration item associated with the target configuration item.

[0076] In one embodiment, after obtaining the target business model data, each associated entity data, the target configuration item and each configuration item associated with the target configuration item in the data packet according to the data synchronization request, it also includes: obtaining each first reference identifier in the target business model data, obtaining each data identifier and each second reference identifier in each associated entity data; obtaining each third reference identifier in the target configuration item, obtaining each configuration identifier and each fourth reference identifier in each configuration item associated with the target configuration item; if each first reference identifier matches each data identifier, there is a matching data identifier in each second reference identifier, each third reference identifier matches each configuration identifier and there is a matching data identifier in each fourth reference identifier, it is determined that the data verification of the data packet has passed; and based on the target business model data, each associated entity data, the target configuration item and each configuration item associated with the target configuration item in the data packet that has passed the data verification, each first data to be synchronized is determined.

[0077] In this embodiment, the above-mentioned target business model data, each associated entity data, target configuration item, and each configuration item associated with the target configuration item may include reference identifiers to other parts, so the server may obtain each first reference identifier in the target business model data, each data identifier and each second reference identifier in each associated entity data, each third reference identifier in the target configuration item, and each configuration identifier and each fourth reference identifier in each configuration item associated with the target configuration item. Thus, the server may determine, based on the reference identifier, that there is real data corresponding to the reference identifier, and further determine whether the data is safe.

[0078] For example, if the server detects that each first reference identifier matches each data identifier, that there is a matching data identifier in each second reference identifier, that each third reference identifier matches each configuration identifier, and that there is a matching data identifier in each fourth reference identifier, it is determined that the data packet has passed the data verification; otherwise, it fails. If the server determines that the data verification has passed, the server can determine each first data to be synchronized based on the target business model data, each associated entity data, the target configuration item, and each configuration item associated with the target configuration item in the data packet that has passed the data verification.

[0079] Specifically, Figure 7 As shown, Figure 7 The figure is a flowchart of the data synchronization step in an embodiment. The above data packet may be an encrypted data packet, and the server parses and decrypts the data packet to obtain various data in the data packet, such as the above target business model data, various associated entity data, target configuration items, and various configuration items associated with the target configuration items. If the server detects that the data cannot be decrypted, the server can detect whether the data has been tampered with, and output the corresponding detection result to ensure data integrity.

[0080] The server can perform the data synchronization process based on the target business model data, each associated entity data, the target configuration item and the configuration items in each configuration item associated with the target configuration item. Among them, before synchronization, the server can verify the existence of the reference relationship data of the basic data dependent on the entity, the controlling business unit and other dependent data. When performing the verification, the server can first match the identifier of the above-mentioned first data with the identifier of the second data. If the identifiers do not match, the server can match the number of the first data with the number of the second data. The above matching rules can be determined based on the basic configuration of the basic items. If they match, it means that the dependent reference data exists, otherwise the verification fails. If the verification fails, the server will output a prompt message, which includes the reason for the problem that the dependent data does not exist, so that users can quickly and accurately locate and solve the problem.

[0081] Before synchronization, the server can also replace and update the data that already exists in the target business scenario. For example, if the server detects that there is already a data row corresponding to the unique matching attribute in the target business environment, that is, the first data matching the second data, the server can use the comparison algorithm to compare multiple attribute values ​​according to the configuration matching rules. If all matching attributes are the same, the server determines that there is business data that is the same as the target business environment. The server can update the identifier of the matching first data to the data row identifier in the data of the target business environment, and then delete the data row of the target business environment, and finally save the new data.

[0082] During synchronization, the server can synchronize the above-mentioned first data to the business domain table in the target business environment, that is, the above-mentioned business data table. The server can parse the file in the data packet, generate the corresponding business domain entity data dynamic object, and synchronize and save it through ORM entity data with the entity as the dimension, thereby reducing unnecessary verification, ensuring that the data synchronization process is not hindered by any scenario, and eliminating obstacles that prevent synchronization from taking effect. The server can perform the above process for each configuration item in the data packet, and after all configuration items and their corresponding entity data are synchronized, output the corresponding synchronization result, such as whether the synchronization is successful.

[0083] Through the above embodiment, the server can use the existence of the reference relationship to perform a security check before synchronization, thereby improving the security of business model data synchronization processing; and the server uses the various configuration items in the queried data packet and their associated entity data to synchronize data and configuration to the target business environment, thereby improving the efficiency of business model data processing.

[0084] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0085] Based on the same inventive concept, the embodiment of the present application also provides a business model data processing device for implementing the business model data processing method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more business model data processing device embodiments provided below can refer to the limitations on the business model data processing method above, and will not be repeated here.

[0086] In an exemplary embodiment, Figure 8 As shown, a business model data processing device is provided, including: an acquisition module 500, a determination module 502 and a processing module 504, wherein:

[0087] The acquisition module 500 is used to acquire an entity query instruction and determine corresponding target configuration items and target business model data according to the entity query instruction.

[0088] The determination module 502 is used to query the cache configuration pool according to the target configuration item and the target business model data to determine each associated entity data associated with the target business model data and each configuration item associated with the target configuration item; the cache configuration pool includes each configuration item corresponding to each business model data.

[0089] The processing module 504 is used to determine the query result corresponding to the entity query instruction according to the target business model data, each associated entity data, the target configuration item and each configuration item associated with the target configuration item.

[0090] In one embodiment, the above-mentioned device also includes: a cache module, which is used to obtain each metadata entity corresponding to each business model data, and determine each business type of each business model data according to each metadata entity; obtain each preset configuration policy corresponding to each business type, and each configuration item corresponding to the metadata entity; according to each preset configuration policy, determine each first association relationship and each second association relationship between each configuration item; the first association relationship represents the data reference association between each configuration item, and the second association relationship represents the entity association between each configuration item; generate a cache configuration pool according to each configuration item, each first association relationship and each second association relationship.

[0091] In one embodiment, the above-mentioned cache module is used to determine one or more of the historical business model data configuration, verification configuration, data matching dimension configuration and encryption configuration for each business type according to the business type; and obtain the preset configuration strategy corresponding to the business type according to one or more of the historical business model data configuration, verification configuration, data matching dimension configuration and encryption configuration.

[0092] In one embodiment, the determination module 502 is used to obtain the target business type of the target business model data, and determine the associated configuration item set corresponding to the target configuration item and the associated entity data set corresponding to the target business model data according to the target business type; for each configuration item in the associated configuration item set and each associated entity data in the associated entity data set, query the cache configuration pool according to the configuration item and the associated entity data to obtain the unqueried configuration items having a first association relationship with the configuration item and the unqueried associated entity data having a second association relationship with the associated entity data; return to the step of querying the cache configuration pool according to the configuration items and the associated entity data according to the unqueried configuration items and the unqueried associated entity data, until the cache configuration pool has been queried for each configuration item and each associated entity data, and each configuration item and each associated entity data associated with the target configuration item is obtained.

[0093] In one embodiment, the above-mentioned determination module 502 is used to obtain each historical version identifier corresponding to the target business model data if the target business type is a historical business model entity, generate an object relationship mapping query condition based on each historical version identifier, and determine the associated entity data set corresponding to the target business model data based on the object relationship mapping query condition.

[0094] In one embodiment, the above-mentioned determination module 502 is used to obtain the primary key information corresponding to the target business model data if the target business type is a controlled business model entity, determine the controlled association information corresponding to the target business model data according to the primary key information, and determine the associated entity data set corresponding to the target business model data according to the controlled association information.

[0095] In one embodiment, the above-mentioned device also includes: a backup module, which is used to determine the business model entities to be synchronized based on the target business model data, the associated entity data, the target configuration items and the configuration items associated with the target configuration items in the query results; convert each business model entity into a backup script file; encrypt and compress the backup script file, and back up and save the encrypted and compressed backup script file.

[0096] In one embodiment, the above-mentioned device also includes: a synchronization module, which is used to obtain a data synchronization request for a target business scenario, and obtain the target business model data, each associated entity data, the target configuration item and each configuration item associated with the target configuration item in the data packet according to the data synchronization request; determine each first data to be synchronized according to the target business model data, each associated entity data, the target configuration item and each configuration item associated with the target configuration item, and obtain a business data table in the target business scenario; the business data table includes each second data; for each second data in the business data table, if there is target data matching the second data in the data packet, the storage position of the target data in the business data table is determined as the storage position corresponding to the second data; according to object-relational mapping, synchronize each first data and each target data with a determined storage position to the business data table in the target business scenario.

[0097] In one embodiment, the above-mentioned device also includes: a verification module, which is used to obtain each first reference identifier in the target business model data, obtain each data identifier and each second reference identifier in each associated entity data; obtain each third reference identifier in the target configuration item, obtain each configuration identifier and each fourth reference identifier in each configuration item associated with the target configuration item; if each first reference identifier matches each data identifier, there is a matching data identifier in each second reference identifier, each third reference identifier matches each configuration identifier, and there is a matching data identifier in each fourth reference identifier, it is determined that the data verification of the data packet has passed; based on the target business model data, each associated entity data, the target configuration item and each configuration item associated with the target configuration item in the data packet that has passed the data verification, the first data to be synchronized are determined.

[0098] Each module in the above-mentioned business model data processing device can be implemented in whole or in part by software, hardware and a combination thereof. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.

[0099] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Fig. 9As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store business model data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a business model data processing method is implemented.

[0100] Those skilled in the art will understand that Fig. 9 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0101] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the above-mentioned business model data processing method when executing the computer program.

[0102] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the above-mentioned business model data processing method is implemented.

[0103] In one embodiment, a computer program product is provided, including a computer program, which implements the above-mentioned business model data processing method when executed by a processor.

[0104] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0105] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0106] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0107] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A business model data processing method, characterized in that: The method comprises: Obtaining an entity query instruction, and determining corresponding target configuration items and target business model data according to the entity query instruction; According to the target configuration item and the target business model data, a cache configuration pool is queried to determine each associated entity data associated with the target business model data and each configuration item associated with the target configuration item; the cache configuration pool includes each configuration item corresponding to each business model data; A query result corresponding to the entity query instruction is determined according to the target business model data, each of the associated entity data, the target configuration item, and each of the configuration items associated with the target configuration item.

2. The method according to claim 1, characterized in that: The method further comprises: Acquire each metadata entity corresponding to each business model data, and determine each business type of each business model data according to each metadata entity; Obtaining each preset configuration strategy corresponding to each of the business types and the configuration items corresponding to the metadata entity; Determine, according to each of the preset configuration strategies, each of the first association relationships and each of the second association relationships between the configuration items; the first association relationship represents the data reference association between the configuration items, and the second association relationship represents the entity association between the configuration items; A cache configuration pool is generated according to each of the configuration items, each of the first association relationships, and each of the second association relationships.

3. The method according to claim 2, characterized in that The obtaining of each preset configuration strategy corresponding to each service type includes: For each of the business types, determine one or more of historical business model data configuration, verification configuration, data matching dimension configuration, and encryption configuration according to the business type; According to one or more of the historical business model data configuration, the verification configuration, the data matching dimension configuration and the encryption configuration, a preset configuration strategy corresponding to the business type is obtained.

4. The method according to claim 1, characterized in that The querying the cache configuration pool according to the target configuration item and the target business model data to determine each associated entity data associated with the target business model data and each configuration item associated with the target configuration item includes: Acquire a target business type of the target business model data, and determine, according to the target business type, a set of associated configuration items corresponding to the target configuration item and a set of associated entity data corresponding to the target business model data; For each configuration item in the associated configuration item set and each associated entity data in the associated entity data set, query the cache configuration pool according to the configuration item and the associated entity data to obtain unqueried configuration items that have a first association relationship with the configuration item and unqueried associated entity data that have a second association relationship with the associated entity data; According to the configuration items that have not been queried and the associated entity data that have not been queried, return to the step of querying the cache configuration pool according to the configuration items and the associated entity data, until the cache configuration pool has been queried for each of the configuration items and each of the associated entity data, and each of the configuration items and each of the associated entity data associated with the target configuration item are obtained.

5. The method according to claim 4, characterized in that The target business type includes a historical business model entity and a controlled business model entity; The step of determining, according to the target business type, a set of associated entity data corresponding to the target business model data comprises: If the target business type is the historical business model entity, obtaining each historical version identifier corresponding to the target business model data, generating an object relationship mapping query condition according to each historical version identifier, and determining a set of associated entity data corresponding to the target business model data according to the object relationship mapping query condition; and / or, If the target business type is a controlled business model entity, obtain the primary key information corresponding to the target business model data, determine the controlled association information corresponding to the target business model data according to the primary key information, and determine the associated entity data set corresponding to the target business model data according to the controlled association information.

6. The method according to any one of claims 1 to 5, characterized in that: After determining the query result corresponding to the entity query instruction according to the target business model data, each of the associated entity data, the target configuration item and each of the configuration items associated with the target configuration item, the method further includes: Determine each business model entity to be synchronized according to the target business model data, each associated entity data, the target configuration item, and each configuration item associated with the target configuration item in the query result; Convert each of the business model entities into a backup script file; The backup script file is encrypted and compressed, and the encrypted and compressed backup script file is backed up and saved.

7. The method according to any one of claims 1 to 5, characterized in that: The query result includes a data packet, and the data packet includes the target business model data, each of the associated entity data, the target configuration item, and each of the configuration items associated with the target configuration item; After determining the query result corresponding to the entity query instruction according to the target business model data, each of the associated entity data, the target configuration item and each of the configuration items associated with the target configuration item, the method further includes: Obtaining a data synchronization request for a target business scenario, and obtaining the target business model data, each of the associated entity data, the target configuration item, and each of the configuration items associated with the target configuration item in the data packet according to the data synchronization request; Determine the first data to be synchronized according to the target business model data, the associated entity data, the target configuration item and the configuration items associated with the target configuration item, and obtain a business data table in the target business scenario; the business data table includes the second data; For each second data in the business data table, if there is target data matching the second data in the data packet, determining the storage position of the target data in the business data table as the storage position corresponding to the second data; According to object relationship mapping, each of the first data and each of the target data with a determined storage location are synchronized to a business data table in the target business scenario.

8. The method according to claim 7, characterized in that After acquiring the target business model data, each of the associated entity data, the target configuration item, and each of the configuration items associated with the target configuration item in the data packet according to the data synchronization request, the method further includes: Acquire each first reference identifier in the target business model data, and acquire each data identifier and each second reference identifier in each associated entity data; Acquire each third reference identifier in the target configuration item, and acquire each configuration identifier and each fourth reference identifier in each configuration item associated with the target configuration item; If each of the first reference identifiers matches each of the data identifiers, a matching data identifier exists in each of the second reference identifiers, each of the third reference identifiers matches each of the configuration identifiers, and a matching data identifier exists in each of the fourth reference identifiers, it is determined that the data verification of the data packet has passed; The first data to be synchronized are determined according to the target business model data, the associated entity data, the target configuration item and the configuration items associated with the target configuration item in the data packet that has passed data verification.

9. A business model data processing device, characterized in that: The device comprises: An acquisition module, used to acquire an entity query instruction, and determine corresponding target configuration items and target business model data according to the entity query instruction; A determination module, configured to query a cache configuration pool according to the target configuration item and the target business model data, and determine each associated entity data associated with the target business model data, and each configuration item associated with the target configuration item; the cache configuration pool includes each configuration item corresponding to each business model data; A processing module is used to determine a query result corresponding to the entity query instruction according to the target business model data, each of the associated entity data, the target configuration item and each of the configuration items associated with the target configuration item.

10. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 8 are implemented.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.

12. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.

Images