CN114896293A - Data integration management method and device, storage medium and electronic equipment - Google Patents

Abstract

The embodiment of the disclosure discloses a data integration management method and device, a storage medium and an electronic device, wherein the method comprises the following steps: adapting at least one corresponding path for at least one database, and extracting data in the at least one database through the adapted path; obtaining at least one category label information corresponding to the data, and binding the category label information and the data to obtain an asset object; wherein the asset objects comprise category objects and ontology objects; compiling the asset object according to the distributed identification codes, and encapsulating the compiled asset object and the authority information corresponding to the asset information to obtain encapsulated data; and receiving a request message sent by a client, and determining whether to send the encapsulated data to the client according to the authority information of the client and the authority information corresponding to the asset object.

Description

Data integration management method and device, storage medium, electronic device

technical field

The present disclosure relates to a data integration management method and device, a storage medium, and an electronic device.

Background technique

In the prior art, the collected data is usually stored according to the convenience of the collection or business requirements, and the fields defined for the storage are usually in line with the perspective of business personnel and can be understood. However, there is a lack of a device that can flexibly organize data according to the perspective of the counterparty of the data being interacted with. At the same time, the existing general method is to directly fetch data from the database before communication, which is relatively simple, and the data source to be fetched is relatively simple.

SUMMARY OF THE INVENTION

In order to solve the above-mentioned technical problems, the present disclosure is made. Embodiments of the present disclosure provide a data integrated management method and apparatus, a storage medium, and an electronic device.

According to an aspect of the embodiments of the present disclosure, a data integration management method is provided, including:

Adapting at least one path corresponding to at least one database, and extracting data in the at least one database through the adapted path;

Obtain at least one category tag information corresponding to the data, bind the category tag information and the data, and obtain an asset object; wherein, the asset object includes a category object and an ontology object;

Compile the asset object according to the assigned identification code, and encapsulate the compiled asset object and the authority information corresponding to the asset object to obtain encapsulated data;

Receive the request message sent by the client, and determine whether to send the encapsulated data to the client according to the permission information of the client and the permission information corresponding to the asset object.

Optionally, the tag information includes the category tag information of a plurality of levels with affiliation; wherein, each of the levels includes at least one of the category tag information;

The obtaining at least one category tag information corresponding to the data, binding the category tag information and the data to obtain an asset object, including:

determining the category tag information of at least one level corresponding to the data based on the static attribute and/or dynamic attribute corresponding to the data;

Binding the data with at least one category tag information corresponding to the data to form the asset object; wherein the data is the data ontology of the asset object, and the category tag information is the asset The object's category object.

Optionally, determining the category tag information of at least one level corresponding to the data based on the static attribute and/or dynamic attribute corresponding to the data, including:

determining at least one meta-attribute describing the static attribute and/or the dynamic attribute based on the static attribute and/or the dynamic attribute corresponding to the data;

Based on the corresponding partial data in the at least one meta-attribute, the corresponding category tag information of at least one level is determined; wherein each category tag information corresponds to one piece of the partial data.

Optionally, the binding of the data with at least one category tag information corresponding to the data to form the asset object includes:

Associating and binding each of the partial data in the at least one partial data included in the data with the class tag information corresponding to the partial data to obtain at least one of the asset objects;

The affiliation between at least one of the asset objects is determined based on the affiliation between the levels corresponding to the category tag information.

Optionally, the receiving the request message sent by the client determines whether to send the encapsulated data to the client according to the permission information of the client and the permission information corresponding to the asset object, including:

Receive, through the protocol adapter, the request message sent by the client through the communication protocol, and determine the encapsulated data corresponding to the request message;

determining whether the authority information of the client matches the authority information corresponding to the asset object;

In response to the client's permission information being matched with the permission information corresponding to the asset object, the encapsulation data corresponding to the request message is sent to the client.

Optionally, the sending the encapsulation data corresponding to the request message to the client includes:

Perform parsing processing on the request message, and determine the operation type corresponding to the request message;

Based on the flag bit information included in the operation type, determine at least one category tag information corresponding to the request message;

The corresponding asset object is obtained based on the class tag information, and the package data corresponding to the asset object is sent to the client.

Optionally, performing parsing processing on the request message to determine an operation type corresponding to the request message, including:

Format conversion is performed on the request message to obtain message data including a plurality of data blocks; wherein, the data blocks include a transmission block, a control block, a data block and a voucher block;

Based on the flag bit information in the control block in the message data, the operation type corresponding to the message data is determined.

Optionally, determining at least one of the category tag information corresponding to the data based on the flag bit information included in the operation type includes:

Based on the flag bit information included in the operation type, matching the pre-stored at least one category tag information;

In response to the existence of the matching category tag information, determining the category tag information as the category object of the message data;

In response to no matching category tag information, category tag information is newly created based on the message data, and the newly created category tag information is used as a category object of the message data.

Optionally, compiling the asset object according to the assigned identification code, and encapsulating the compiled asset object and the authority information corresponding to the asset object to obtain encapsulated data, including:

Perform at least one verification operation respectively on at least one category object and at least one ontology object included in the asset object;

The asset object that has passed the verification is compiled according to the assigned identification code, and the compiled asset object is encapsulated with the authority information corresponding to the asset object to obtain encapsulated data.

According to another aspect of the embodiments of the present disclosure, a data integration management apparatus is provided, including:

a data extraction module, configured to adapt at least one path corresponding to at least one database, and extract data in the at least one database through the adapted path;

A data binding module, configured to obtain at least one category tag information corresponding to the data, bind the category tag information and the data to obtain an asset object; wherein the asset object includes a category object and an ontology object ;

an object compiling module, configured to compile the asset object according to the assigned identification code, and encapsulate the compiled asset object and the authority information corresponding to the asset information to obtain encapsulated data;

A data request module, configured to receive a request message sent by a client, and determine whether to send the encapsulated data to the client according to the permission information of the client and the permission information corresponding to the asset object.

Optionally, the tag information includes the category tag information of a plurality of levels with affiliation; wherein, each of the levels includes at least one of the category tag information;

The data binding module includes:

a category determination unit, configured to determine the category tag information of at least one level corresponding to the data based on the static attribute and/or dynamic attribute corresponding to the data;

An asset object unit, configured to bind the data with at least one category tag information corresponding to the data to form the asset object; wherein the data is the data ontology of the asset object, and the category The tag information is the category object of the asset object.

Optionally, the category determination unit is specifically configured to determine at least one meta attribute describing the static attribute and/or the dynamic attribute based on the static attribute and/or dynamic attribute corresponding to the data; based on The corresponding partial data in the at least one meta-attribute respectively determines the corresponding category tag information of at least one level; wherein each category tag information corresponds to one piece of the partial data.

Optionally, the asset object unit is specifically configured to associate and bind each of the partial data in the at least one partial data included in the data with the category tag information corresponding to the partial data, to obtain at least one of the partial data. One of the asset objects; determining the affiliation between at least one of the asset objects based on the affiliation between the levels corresponding to the category tag information.

Optionally, the data request module includes:

a request receiving unit, configured to receive, through a protocol adapter, a request message sent by the client through a communication protocol, and determine the encapsulation data corresponding to the request message;

an authority matching unit, configured to determine whether the authority information of the client matches the authority information corresponding to the asset object;

A data sending unit, configured to send the encapsulated data corresponding to the request message to the client in response to the matching between the permission information of the client and the permission information corresponding to the asset object.

Optionally, the data sending unit is specifically configured to perform parsing processing on the request message, and determine the operation type corresponding to the request message; and determine the request message based on the flag bit information included in the operation type. at least one category tag information corresponding to the message; obtaining the corresponding asset object based on the category tag information, and sending the package data corresponding to the asset object to the client.

Optionally, when the data sending unit parses the request message and determines the operation type corresponding to the request message, it is used to perform format conversion on the request message, and obtain a data block including multiple data blocks. The message data; wherein, the data block includes a transmission block, a control block, a data block and a voucher block; based on the flag bit information in the control block in the message data, determine the operation type corresponding to the message data .

Optionally, when the data sending unit determines at least one of the class tag information corresponding to the data based on the flag bit information included in the operation type, the data sending unit is used to base on the flag bit included in the operation type. information, match at least one of the pre-stored category tag information; in response to the existence of the matching category tag information, determine the category tag information as the category object of the message data; in response to the absence of the category tag information For the matched category tag information, create category tag information based on the message data, and use the newly created category tag information as the category object of the message data.

Optionally, the object compilation module is specifically configured to perform at least one verification operation on at least one category object and at least one ontology object included in the asset object; The assigned identification code is compiled, and the compiled asset object and the authority information corresponding to the asset object are encapsulated to obtain encapsulated data.

According to another aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided, where the storage medium stores a computer program, and the computer program is used to execute the data integration management method described in any of the foregoing embodiments.

According to another aspect of the embodiments of the present disclosure, there is provided an electronic device, the electronic device comprising:

processor;

a memory for storing the processor-executable instructions;

The processor is configured to read the executable instructions from the memory, and execute the instructions to implement the data integration management method described in any one of the foregoing embodiments.

Based on the data integration management method and apparatus, storage medium, and electronic device provided by the foregoing embodiments of the present disclosure, at least one path corresponding to at least one database is adapted, and data in the at least one database is extracted through the adapted path; Obtain at least one category tag information corresponding to the data, bind the category tag information and the data, and obtain an asset object; wherein, the asset object includes a category object and an ontology object; Compile the assigned identification code, and encapsulate the compiled asset object and the authority information corresponding to the asset information to obtain encapsulated data; receive the request message sent by the client, according to the authority information of the client and the asset object Corresponding authority information, determine whether to send the encapsulated data to the client; this embodiment can fetch data from multiple data sources and combine them into a new data model for data interaction In addition, in this embodiment, the existing system architecture is not changed, and the existing service operation is not affected, but an additional agent middleware device is further added on the basis.

The technical solutions of the present disclosure will be further described in detail below through the accompanying drawings and embodiments.

Description of drawings

The above and other objects, features and advantages of the present disclosure will become more apparent from the more detailed description of the embodiments of the present disclosure in conjunction with the accompanying drawings. The accompanying drawings are used to provide a further understanding of the embodiments of the present disclosure, and constitute a part of the specification, and are used to explain the present disclosure together with the embodiments of the present disclosure, and do not limit the present disclosure. In the drawings, the same reference numbers generally refer to the same components or steps.

1 is a schematic flowchart of a data integration management method provided by an exemplary embodiment of the present disclosure;

FIG. 2a is a schematic flowchart of step 104 in the embodiment shown in FIG. 1 of the present disclosure;

Fig. 2b is a schematic diagram of business requirements in an optional example proposed by the present disclosure;

2c is a schematic diagram of a category attribute architecture with consumers as entity objects in an optional example proposed by the present disclosure;

Fig. 2d is a schematic diagram of a dictionary recommendation part in the proxy device in an optional example proposed by the present disclosure;

3 is a schematic structural diagram of a category object in an optional example proposed by the present disclosure;

4 is a schematic structural diagram of an ontology object in an optional example proposed by the present disclosure;

5a is a schematic diagram of a generation process in an optional example proposed by the present disclosure;

FIG. 5b is a schematic diagram of the correspondence between category objects and ontology objects in an optional example proposed by the present disclosure;

FIG. 6 is a schematic flowchart of step 108 in the embodiment shown in FIG. 1 of the present disclosure;

FIG. 7a is a schematic diagram of verifying a category object in an optional example proposed by the present disclosure;

FIG. 7b is a schematic diagram of verifying category objects in another optional example proposed by the present disclosure;

FIG. 8 is a schematic structural diagram of a data integration management apparatus provided by an exemplary embodiment of the present disclosure;

9 is a schematic structural diagram of a data integration management system provided by an exemplary embodiment of the present disclosure;

FIG. 10 is a structural diagram of an electronic device provided by an exemplary embodiment of the present disclosure.

Detailed ways

Hereinafter, exemplary embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are only some of the embodiments of the present disclosure, not all of the embodiments of the present disclosure, and it should be understood that the present disclosure is not limited by the example embodiments described herein.

It should be noted that the relative arrangement of the components and steps, the numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present disclosure unless specifically stated otherwise.

Those skilled in the art can understand that terms such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different steps, devices, or modules, etc., and neither represent any specific technical meaning, nor represent any difference between them. the necessary logical order of .

It should also be understood that, in the embodiments of the present disclosure, "a plurality" may refer to two or more, and "at least one" may refer to one, two or more.

It should also be understood that any component, data or structure mentioned in the embodiments of the present disclosure can generally be understood as one or more in the case of no explicit definition or contrary indications given in the context.

In addition, the term "and/or" in the present disclosure is only an association relationship to describe associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, it can mean that A exists alone, and A and B exist at the same time , there are three cases of B alone. In addition, the character "/" in the present disclosure generally indicates that the related objects are an "or" relationship. The data referred to in this disclosure may include unstructured data such as text, images, and videos, or may be structured data.

It should also be understood that the description of the various embodiments in the present disclosure emphasizes the differences between the various embodiments, and the same or similar points can be referred to each other, and for the sake of brevity, they will not be repeated.

Meanwhile, it should be understood that, for the convenience of description, the dimensions of various parts shown in the accompanying drawings are not drawn in an actual proportional relationship.

The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the disclosure, its application or uses in any way.

Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail, but where appropriate, such techniques, methods, and apparatus should be considered part of the specification.

It should be noted that like numerals and letters refer to like items in the following figures, so once an item is defined in one figure, it does not require further discussion in subsequent figures.

Embodiments of the present disclosure can be applied to electronic devices such as terminal devices, computer systems, servers, etc., which can operate with numerous other general-purpose or special-purpose computing system environments or configurations. Examples of well-known terminal equipment, computing systems, environments and/or configurations suitable for use with terminal equipment, computer systems, servers, etc. electronic equipment include, but are not limited to: personal computer systems, server computer systems, thin clients, thick clients computer, handheld or laptop devices, microprocessor-based systems, set-top boxes, programmable consumer electronics, network personal computers, minicomputer systems, mainframe computer systems, and distributed cloud computing technology environments including any of the foregoing, among others.

Electronic devices such as terminal devices, computer systems, servers, etc., may be described in the general context of computer system-executable instructions, such as program modules, being executed by the computer system. Generally, program modules may include routines, programs, object programs, components, logic, data structures, etc. that perform particular tasks or implement particular abstract data types. Computer systems/servers may be implemented in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located on local or remote computing system storage media including storage devices.

This embodiment uses Product Lifecycle Management (PLM), Enterprise Resource Planning (ERP), Advanced Planning and Scheduling (APS), Manufacturing Execution System (Manufacturing Execution System) , MES) as an example of their respective functions and the basic data that need to communicate with each other, to analyze the integration of data between multiple systems. The core data of manufacturing enterprises are sales data, technical data, production data and procurement data. The data between PLM, ERP, APS, and MES has a cross relationship. Some data is required by multiple systems. If this part of data is shared among multiple systems, it can improve the efficiency of system maintenance and reduce the probability of maintenance data errors. The functionality of the information system has been improved. To analyze how to integrate data, it is necessary to know which data is used by multiple systems, and these data are the integration management objects in the embodiment of the present application. For example, sales data is related to ERP and APS; technical data is related to PLM and ERP; production inventory data is related to ERP and APS; procurement data is related to ERP and APS, and so on.

Exemplary method

FIG. 1 is a schematic flowchart of a data integration management method provided by an exemplary embodiment of the present disclosure. This embodiment can be applied to an electronic device, as shown in FIG. 1 , including the following steps:

Step 102: Adapt at least one path corresponding to at least one database, and extract data in at least one database through the adapted path.

Among them, the database is the place where the data to be transformed is initially stored, and the place belongs to the original information system of the enterprise. There are various types of the original information system of the enterprise, including but not limited to: used to support the whole life cycle of the product A series of application solutions for the creation, management, distribution and application of information, product life cycle management (PLM), enterprise resource planning (ERP) for enterprise business management, financial and human-related management, and other management platforms and controls systems, such as industrial Internet platforms, middle-end systems, software integration systems, etc.; the embodiments of this application do not limit the types of databases, provide different adaptation paths for different databases, and implement data extraction from databases through the adapted paths.

Step 104: Obtain at least one category tag information corresponding to the data, and bind the category tag information and data to obtain an asset object.

The asset objects include category objects and ontology objects.

In one embodiment, the data includes multiple sets of data obtained from multiple databases corresponding to the same enterprise, and these data all correspond to the same subject (for example, the same person, the same enterprise, etc.). Unified management of data.

Step 106: Compile the asset object according to the assigned identification code, and encapsulate the compiled asset object and the authority information corresponding to the asset information to obtain encapsulated data.

Optionally, in order to improve the data security of asset objects, assign identification codes to different asset objects (identification codes can be assigned in any coding method), compile gesture objects according to identification codes, and change the data format of asset objects, for example, The identifier is encoded as an encrypted password, and the asset object is encrypted by the encrypted password, that is, the compilation is realized; in order to control that only clients with set conditions can obtain the asset object, this embodiment encapsulates the authority information and the asset object, so that only The asset object can only be obtained by a client with corresponding permissions.

Step 108: Receive the request message sent by the client, and determine whether to send the encapsulated data to the client according to the permission information of the client and the permission information corresponding to the asset object.

On the basis of data security transmission and access control, further emphasis is placed on the decoupling of data and operations to ensure the security and privacy of coupling between them while they develop independently.

In a data integration management method provided by the above-mentioned embodiments of the present disclosure, at least one path corresponding to at least one database is adapted, and data in the at least one database is extracted through the adapted path; and at least one class corresponding to the data is obtained. target tag information, bind the category tag information and the data, and obtain an asset object; wherein, the asset object includes a category object and an ontology object; compile the asset object according to the assigned identification code, and compile the The obtained asset object is encapsulated with the permission information corresponding to the asset information to obtain encapsulated data; after receiving the request message sent by the client, it is determined whether to The encapsulated data is sent to the client; this embodiment can fetch data from multiple data sources and combine them into a data model of a new data interaction protocol, and then interact with this new data; in addition, this embodiment can It is also possible to further increase the additional agent middleware device on the basis of it without changing the existing system architecture or affecting the existing business operation.

The method provided in this embodiment can be implemented in a data integration management system, and the system further includes a display interaction module: interacting and controlling the agent conversion system through the Web and Restful interface, and the SDK is an open tool to display and interact with the embedded or The secondary development of resource-constrained devices provides directly usable tools, so that the agent conversion system can be applied in more scenarios.

As shown in Figure 2a, on the basis of the above-mentioned embodiment shown in Figure 1, the tag information includes category tag information of multiple levels with affiliation; wherein, each level includes at least one category tag information; Step 104 Can include the following steps:

Step 1041 , based on the static attribute and/or dynamic attribute corresponding to the data, determine at least one level of category tag information corresponding to the data.

Step 1042: Bind the data with at least one category tag information corresponding to the data to form an asset object.

The data is the data body of the asset object, and the category tag information is the category object of the asset object.

In this embodiment, from a business perspective, data can be divided into virtual or entity objects, objects are described by static/dynamic attributes, and attributes are described and defined by meta-attributes; for example, as shown in Figure 2b, the business requirements correspond to: "people" Entity objects, virtual objects of "relationships", entity objects of "things", virtual objects of "categories", and entity objects of "operations", these entity objects or virtual objects are described by static/dynamic attributes, for example, obtain The data includes a consumer's personality and hobby data, behavioral habit data, personality style data and demand difficulty data; at this time, these data correspond to different static or dynamic attributes; in an optional example, as shown in Figure 2c, with In the example of the category attribute structure of consumers as entity objects, the level of category tag information is determined to be the root directory of "consumer" by using consumers as entity objects, and the first-level categories include: basic attributes, geographic location, Relationship, asset credit; the second-level categories corresponding to basic attributes include: demographics, physical characteristics, education, occupational information, life stage, immediate family, account information, and ability value; the third-level categories corresponding to demographic statistics include: documents number, gender, date of birth, nationality, and contact information; the attribute fields corresponding to the date of birth include: ID card age, ID card age group, age, predicted age group, constellation, and zodiac.

Attributes can also be determined through dictionary recommendation and retrieval. The purpose of this embodiment of the present application is to map and aggregate data from multiple sources. In order to map the aggregated data into asset objects, it is necessary to use correct metadata or attribute fields. This attribute is standardized and defined. Commonly used standards include eclass and standard metadata defined by various enterprises and industry associations. For example, as shown in Figure 2d, the dictionary recommendation part in the proxy device is divided into an input part (the upper two boxes) and an output part (the lower one box), and different proxy devices share the same general data dictionary database, that is, all the same A database requests data, and the same data standards are used between communication systems. The data input part can be retrieved according to tags and keywords. For example, by entering clothing and specifications, the specifications corresponding to the corresponding clothing industry standards can be returned.

Extraction rules and mapping methods: In response to the mapping rules of the extracted data and the asset system, the specific mapping conversion function is realized.

On the basis of the above embodiment, step 1041 may further include:

Determine at least one meta-attribute describing the static attribute and/or dynamic attribute based on the static attribute and/or dynamic attribute corresponding to the data;

Based on the corresponding partial data in the at least one meta-attribute, the corresponding category tag information of at least one level is determined.

Among them, each category tag information corresponds to a part of data.

Asset objects (AO) include category objects and ontology objects; the structure of category objects. As shown in FIG. 3, Object ID represents an object identifier and is used to uniquely identify a category object. Registry Time is the time when it was created, indicating the time when the category object was created. Expiration Time is the expiration time, indicating the expiration time of the category object. Modified Time is the modification time, indicating the time when the category object is modified; Class Object is the object type, indicating that the type is a category object. Father represents the upper-level category object represented by the category object, and is represented by a set containing the identifiers of the inherited upper-level category objects, such as: {Object ID1, Object ID2, ...}. Child represents the next-level category object represented by the category object, and is represented by a set containing the identifiers of the next-level category objects, such as: {Object ID7, Object ID8, ...}. The meta-attribute information is used to indicate the catalogue, attribute characteristics, tags of attributes included in the ontology object corresponding to the category object, and attributes of the category object. For example, the meta-attribute information may include: the category standard to which the attribute belongs, attribute name, attribute description, attribute processing type, value dictionary, value type, example, update period, security level, object relationship, and the like. The category standard to which the attribute belongs: that is, the normative standard that the attribute follows, such as Eclass; attribute name: attribute naming should follow three principles: avoid privacy violation, use the same attribute name for the same attribute, and use the same sentence structure for similar attributes; attribute description: Explain the attribute name in one or two sentences to avoid the ambiguity, ambiguity, and polysemy of the attribute name due to the too short words; Algorithm class attributes, the original class attributes are fields that exist in the original data table. After simple processing (for example, deduplication, etc.), they become attributes and can be used by business personnel, such as age, job number, etc.; statistical attributes represent the original Data through processing, such as sum, average, regular expression and other simple mathematical functions, become attributes, such as the total number of products browsed in 7 days, etc.; algorithm attributes are the labels of deep processing after the original data is calculated by the model algorithm, such as "Consumption power", etc.; value dictionary: the enumeration of various possible values of the attribute, for example: the value dictionary of the "gender" attribute is [male, female]; value type: the data type of the attribute value, there are numeric types , character type, date type, etc.; example: specific example of attribute value; update cycle: refers to the update cycle of attribute data; security level: attribute data will exist in the process of attribute data acquisition from source data to data processing, attribute online, and attribute use Data security risks, therefore, it is necessary to formulate security levels for attributes, and generate different levels of attribute usage specifications according to the security levels of the attributes; object relationship: For the native attribute labels of the category objects of father and child, the object relationship can be further explained. Figure 4 shows the structure of an ontology object. As shown in Figure 4, the Object ID is an object identifier, which is used to uniquely identify an ontology object. Registry Time is the time when it was created, indicating the time when the ontology object was created. Expiration Time is the expiration time, indicating the expiration time of the ontology object. Modified Time is the modification time, indicating the modification time of the ontology object; Data/Opera is the object type, indicating the type of the ontology object, Data indicates that the ontology object is a data object, Opera indicates that the ontology object is an operation object, and Reference ID is the reference ID, indicating the ontology Object ID of the category object corresponding to the object. The data ontology representation is the specific actual data or data operation interface address under the category object to which the ontology object belongs. The data format, semantics, period, security level, etc. need to be consistent with those defined in the category object to which it belongs. The category object is used to represent the ideal subordination relationship between AOs (more complex relationships can also be defined based on the attribute table), category description information, meta-attribute information, etc. The ontology object is a specific instance, which needs to be consistent with the definition in the category object. Not all inclusive; affiliations may also be instance specific.

The asset object format ensures that the data is a standardized and structured asset object during production, which greatly improves the efficiency of the enterprise and reduces the waste of resources; The bottom-up concept, the category attribute structure is constructed and used by users, which is highly inclusive and universal; this embodiment will promote the digital transformation of enterprises, further development of the digital economy, and further release of data value.

On the basis of the above embodiment, step 1042 may further include:

Associating and binding each partial data in the at least one partial data included in the data with the class tag information corresponding to the partial data to obtain at least one asset object;

The affiliation between at least one asset object is determined based on the affiliation between the levels corresponding to the category tag information.

In this embodiment, by comparing each partial data (character hobby data, behavioral habit data, character style data and demand difficulty data in the embodiment shown in FIG. 2c correspond to different partial data respectively); The corresponding category tag information is bound to determine the corresponding asset object. For example, as shown in Figure 5a, in a production process, a raw material C0 is processed to C1 in one step. At this time, it needs to be assembled with A, and then Continue to process into C2, then assemble B, and then process into C3. A simple parent and child table cannot express the front-to-back process relationship of parts. In the production planning and scheduling APS system, the assembly relationship and the sequence flow of parts before and after production must be expressed in order to carry out correct and instructive scheduling. This embodiment of the present application integrates process data and data in various business systems by establishing asset objects. As shown in Figure 5b, corresponding ontology objects are included under the root category, the second-level category, and the third-level category. , and the corresponding ontology object may not be included in the first-level category. At this time, since the third-level category belongs to the second-level category, the second-level category belongs to the first-level category, and the first-level category belongs to the root category. Therefore, the ontology object corresponding to the third-level category belongs to the ontology object corresponding to the second-level category, and the ontology object corresponding to the second-level category belongs to the ontology object corresponding to the root category (because the first-level category has no ontology object, Therefore, the second-level category inherits the affiliation of the first-level category); in this specific example, through the corresponding processing processes of different levels of categories, the more primary the processing step, the lower the corresponding category level, and the final processing result corresponds to root category.

As shown in FIG. 6 , on the basis of the above-mentioned embodiment shown in FIG. 1 , step 108 may include the following steps:

Step 1081: Receive the request message sent by the client through the communication protocol through the protocol adapter, and determine the encapsulation data corresponding to the request message.

This embodiment implements multi-protocol adaptation. The protocol adapter can receive message data of any existing protocol, and the protocol detection device can identify which protocol the received message data adopts. For example, there are currently two possibilities. Unique solution: 1) Apply the parsing method of handle, then the communication method with it is clarified in serviceinfo, so it can directly guide the communication method of the target communication object; 2) Implement protocol detection through machine learning methods.

After the communication protocol is determined, the corresponding block is selected according to the pre-set QOS through adaptation conversion, so as to adapt to the existing protocol to achieve the purpose of compatibility.

Step 1082: Determine whether the authority information of the client matches the authority information corresponding to the asset object.

Step 1083: In response to the client's authority information matching the authority information corresponding to the asset object, send the encapsulation data corresponding to the request message to the client.

Optionally, sending the encapsulated data corresponding to the request message to the client may include: loading the encapsulated data into a data block in the data interoperability protocol message; The transmission method determined by the configuration strategy will effectively share the encapsulated data.

It may also include, in response to the client's permission information not matching the permission information corresponding to the asset object, feeding back information that does not have permission to the client.

In view of the solidified status quo of existing protocols and the natural needs of industrial Internet communication; this embodiment provides rich multi-protocol adaptation strategies to ensure real-time, efficient, and flexible data distribution in complex network environments. Real-time communication application requirements; through the rich and flexible protocol adapters (adaptation strategy, AS, AdaptationStrategy) to meet the data transmission in the complex heterogeneous network environment, it is the most widely adopted application, and has become the unified use in the industrial Internet. protocol.

The permission request access mechanism centered on the asset object includes: data access permission control is based on the data object or even one of its attributes. Permission request and response mechanism. In each data object, or in the attribute metadata that needs permission control, it is necessary to set a standard asset object model for standardized access control, support a relatively standardized access control mechanism, or specify a centralized normalization paradigm. At the same time, it should be based on the digital asset system that has been stored.

The adaptation strategy provided in this embodiment has the following characteristics: 1. Integrity and orderliness: For adaptation to unreliable transmission protocols such as UDP, errors based on retransmission, forward error correction, congestion control, and hybrid mechanisms can be used. The control strategy ensures the integrity and order of data transmission; 2. Volume control: For the communication of industrial edge devices with different storage and computing capabilities, compression algorithms of different strategies can be used to control the data volume to ensure smooth communication. 3. Priority: Corresponding priority policies can be used for messages of different importance levels to ensure that important data is obtained first. At the same time, it is necessary to ensure the priority inheritance relationship between messages.

The protocol adapter provided in this embodiment has high adaptability: rich and flexible adaptation strategies allow reliable, safe, and effective data transmission in complex heterogeneous network environments; high resource utilization: for different adaptation protocols, policies can be It avoids the transmission of some redundant data; high scalability: the protocol can predefine some strategies for most scenarios.

Optionally, on the basis of the foregoing embodiment, step 1083 may include:

Parse and process the request message to determine the operation type corresponding to the request message;

Determine at least one category tag information corresponding to the request message based on the flag bit information included in the operation type;

The corresponding asset object is obtained based on the class tag information, and the package data corresponding to the asset object is sent to the client.

In this embodiment, for the published asset object data, after passing the authority identification, the published asset object will be improved and recommended, so as to maximize the meaning of the unified consensus metadata and form a unified standard; the discrimination mechanism includes: firstly and The existing category objects are compared, and if the registered ones are similar, it will return to the existing registered category objects, and it is recommended that users use the registered category objects. If no similar already exists, it is compared with the recommended metadata standard from the top node. Determine the similarity between each field (metadata) and the definition in the metadata standard (the similarity can be determined by using space vector distance, etc.), if the similarity is less than the set value (set according to the situation), replace it with the standard element If the data is greater than the set value, it will be retained, and a temporary standard database will be created in the standard database and stored in it; at the same time, the improved category object will be returned through the publish response (PUB RESP). If the RP (Repeat) flag is 1 (it has been modified through the automated process), then make a judgment. If the uploaded one is the same as the last recommended one, go to the next step; if the recommended one is different from the uploaded one, pass The category object registration bureau will be judged by specialized personnel. The objects uploaded uniformly will go to the next step. If they do not agree, they will give revision opinions.

Optionally, the request message is parsed and processed to determine the operation type corresponding to the request message, including:

Convert the format of the request message to obtain message data including a plurality of data blocks; wherein, the data blocks include a transmission block, a control block, a data block and a voucher block;

The data block can also include basic headers (the version of the storage protocol, and the check code information, etc.); the transmission block is used to control the transmission strategy of the data packet to better adapt to the network protocol environment; the control block is used to control the release, The specific method in the subscription process; the data block is used to carry the specific data to be transmitted, and the related processing defined for it; the security and verification information of the credential block message being processed.

Optionally, when the published data is a category object, based on the flag bit information included in the operation type, at least one category tag information corresponding to the data is determined, including:

Based on the flag bit information included in the operation type, match the pre-stored at least one category tag information;

In response to the existence of matching category tag information, determine the category tag information as the category object of the message data;

In response to no matching category tag information, category tag information is created based on the message data, and the newly created category tag information is used as a category object of the message data.

Optionally, determine whether the data identifier is released for the first time through the value of the RP (Repeat) flag; when RP is set to 0, it means that the data identifier is released for the first time, and when RP is set to 1, it means the data Identifiers have been issued before, without success.

Optionally, on the basis of the foregoing embodiment, step 106 may further include:

Perform at least one verification operation respectively on at least one category object and at least one ontology object included in the asset object;

The asset object that has passed the verification is compiled according to the assigned identification code, and the compiled asset object is encapsulated with the permission information corresponding to the asset object to obtain encapsulated data.

Among them, at least one inspection operation includes but is not limited to: legality and compliance inspection: the digital asset object registration authority and the object examiner conduct legality and compliance inspections of the uploaded objects, including whether the content is compliant and whether There are false or false situations, etc.; Normative and conformity inspection: that is, to verify whether the ontology object is consistent with the provisions of the reference ID category object, including size, data type, value range, etc.; association Sex and Inheritance Test: Detect whether there is a conflict of inheritance and association between objects. The type of conflict includes inconsistency in the category relationship; for example, the child in the first-level category is inconsistent with the father in the second-level category, There is an extra ciid in the child in the upper-level category, which was originally identified as the root category but the upper-level category appears again; or there is an obvious logical conflict in the inheritance between categories, etc., in some optional examples , traverse all the category objects in the asset object, check whether the relationship between them is legal and logical, there may be various problems, for example, as shown in Figure 7a, the parent node of the next level object and the previous level The sub-nodes of the object do not match, indicating that the category objects in the asset object have association conflicts; for another example, as shown in Figure 7b, a sub-object that is not recognized by the upper-level appears in the next level, indicating that the asset object has a Category objects have inheritance conflicts; in the asset category system, parent nodes and child nodes may be inconsistent. Therefore, when traversing, traverse from high-level nodes (category objects) to low-level nodes, and then from low-level nodes to high-level nodes. Level nodes are traversed to achieve bidirectional traversal to avoid omissions.

Step 106 provided in this embodiment may be implemented in a basic service module in the data integration management system, and the basic service module is used to implement key authentication, legal verification, multiple operating environments, dictionary recommendation, extraction and mapping methods, and the like.

The method provided in this embodiment is applicable to various operating environments: performing an ontology object operation of a custom operation type. After the write permission is granted, the system obtains a list of operations that the user can perform on the instance. The operation list is obtained through user authentication, including whether the user has the read permission to customize the operation object. The system gets the custom action in the action list. Execute custom operations: The system provides multiple operating environments such as JS, python, and C++, parses the instance body data according to the instance identifier being operated, and obtains the main method (main) of the custom operation, and passes the instance body data as parameters to the main method. Perform custom actions. That is, users can expand custom operations in the editor, perform self-programming under the multi-environment conditions of the original system, and add new programming methods to the main function, so as to perform richer operations on objects.

Any data integration management method provided by the embodiments of the present disclosure may be executed by any appropriate device with data processing capabilities, including but not limited to: terminal devices and servers. Alternatively, any of the data integration management methods provided by the embodiments of the present disclosure may be executed by a processor, for example, the processor executes any of the data integration management methods mentioned in the embodiments of the present disclosure by invoking corresponding instructions stored in the memory. No further description will be given below.

Exemplary device

FIG. 8 is a schematic structural diagram of a data integration management apparatus provided by an exemplary embodiment of the present disclosure. As shown in FIG. 8 , the device provided in this embodiment includes:

A data extraction module 81, configured to adapt at least one path corresponding to at least one database, and extract data in at least one database through the adapted path;

The data binding module 82 is used to obtain at least one category object tag information corresponding to the data, bind category object tag information and data, and obtain an asset object; wherein, the asset object includes a category object and an ontology object;

The object compiling module 83 is used to compile the asset object according to the assigned identification code, and encapsulate the compiled asset object and the authority information corresponding to the asset information to obtain encapsulated data;

The data request module 84 is configured to receive the request message sent by the client, and determine whether to send the encapsulated data to the client according to the permission information of the client and the permission information corresponding to the asset object.

A data integration management apparatus provided by the above embodiments of the present disclosure adapts at least one path corresponding to at least one database, extracts data in at least one database through the adapted path, and obtains at least one category tag corresponding to the data information, bind the category tag information and the data to obtain an asset object; wherein, the asset object includes a category object and an ontology object; the asset object is compiled according to the assigned identification code, and the compiled The asset object is encapsulated with the authority information corresponding to the asset information to obtain encapsulated data; the request message sent by the client is received, and according to the authority information of the client and the authority information corresponding to the asset object, it is determined whether to encapsulate the encapsulation The data is sent to the client; this embodiment can fetch data from multiple data sources and combine them into a data model of a new data interaction protocol, and then interact with the new data; in addition, this embodiment can also It does not need to change the existing system architecture, does not affect the existing business operation, but is an additional agent middleware device that is further increased on its basis.

Optionally, the tag information includes category tag information of multiple levels of affiliation; wherein, each level includes at least one category tag information;

Data binding module 82, including:

a category determination unit, configured to determine category tag information of at least one level corresponding to the data based on the static attribute and/or dynamic attribute corresponding to the data;

The asset object unit is used to bind the data with at least one category tag information corresponding to the data to form an asset object; wherein the data is the data body of the asset object, and the category tag information is the category object of the asset object.

Optionally, a category determination unit, specifically configured to determine at least one meta attribute describing the static attribute and/or dynamic attribute based on the static attribute and/or dynamic attribute corresponding to the data; Part of the data, to determine the corresponding at least one level of category tag information; wherein, each category tag information corresponds to a piece of data.

Optionally, the asset object unit is specifically used to associate and bind each partial data in the at least one partial data included in the data with the category tag information corresponding to the partial data to obtain at least one asset object; based on the category tag The affiliation between the levels corresponding to the information determines the affiliation between at least one asset object.

Optionally, the data request module 84 includes:

The request receiving unit is used for receiving the request message sent by the client through the communication protocol through the protocol adapter, and determining the encapsulation data corresponding to the request message;

a permission matching unit, used to determine whether the permission information of the client matches the permission information corresponding to the asset object;

The data sending unit is configured to send the encapsulated data corresponding to the request message to the client in response to the matching between the authority information of the client and the authority information corresponding to the asset object.

Optionally, the data sending unit is specifically configured to parse and process the request message, and determine the operation type corresponding to the request message; based on the flag bit information included in the operation type, determine at least one category tag information corresponding to the request message ; Obtain the corresponding asset object based on the class tag information, and send the package data corresponding to the asset object to the client.

Optionally, when the data sending unit parses the request message and determines the operation type corresponding to the request message, it is used to perform format conversion on the request message to obtain message data including multiple data blocks; The block includes a transmission block, a control block, a data block and a voucher block; based on the flag bit information in the control block in the message data, the operation type corresponding to the message data is determined.

Optionally, when determining at least one category tag information corresponding to the data based on the flag bit information included in the operation type, the data sending unit is used to send the pre-stored at least one category tag information based on the flag bit information included in the operation type. In response to the existence of matching category tag information, the category tag information is determined as the category object of the message data; in response to the absence of matching category tag information, the category tag information is newly created based on the packet data to The newly created category tag information is used as the category object of the packet data.

Optionally, an object compilation module, specifically configured to perform at least one verification operation on at least one category object and at least one ontology object included in the asset object; , encapsulate the compiled asset object and the permission information corresponding to the asset object to obtain encapsulated data.

FIG. 9 is a schematic structural diagram of a data integration management system provided by an exemplary embodiment of the present disclosure. As shown in Fig. 9, data extraction is performed on source databases or data warehouses such as PLM, ERP, management platform, etc. through the adapter. The adapter 91 stores these original information systems in their own interfaces, and the adapter 91 is required to extract them through appropriate channels. come out. The class tag system management module 92 is mainly divided into the following parts, showing the interaction module, the business module, the basic service module, and the class tag data storage module.

Display interaction module: It is used to interact and control the agent conversion system through the Web and Restful interface, which is convenient to use.

Business management module: mainly includes category object management unit, ontology object management unit (including data objects and operation objects), user management unit, data source management unit and transformation mode management unit.

Category object management unit: including the creation and deletion of category objects, corresponding permission control, and the recommended use of the normalized metadata dictionary used; it may not include category object management. In this case, the response is directly extracted from the database The fixed data is mapped using the data in the category attribute system database, thereby simplifying the complexity of the device and making it more friendly to edge devices. Ontology object management unit: including query, retrieval and reference of related category objects in the existing category object system database, based on the selected category object, a function of creating, deleting and editing the ontology object . User management unit: including user object creation, user rights management, user object deletion and other functions. Data source management unit: stable and effective management of different data sources that need to be connected, including the ability to configure database addresses, request commands, and permissions. At the same time, you can also configure a certain extraction period, and other parameters. Mode management module unit: It is to select the mode of the asset object data, that is, the processing method of the digital asset system formed by aggregation and mapping, including: cache-send mode, and storage-send mode; among them, the cache-send mode is not. Storage, the object to be transmitted is formed directly in the cache, and sent directly to the outside; the storage-send mode is to store the asset object data in the database and send it out according to the received request.

The basic service module includes: key authentication, legal verification, multiple operating environments, dictionary recommendation, extraction and mapping methods.

Key authentication: The user fills in the user ID and authentication key, parses the public key information in the user ID through the identification system, and verifies the key entered by the user. If the verification is passed, the authentication is successful, otherwise it fails.

Permission control: Permission control mainly includes several important contents, including the user's read and write permissions for the category object (defined by the data publisher), and the read and write permissions for the ontology object. In particular, individual objects will even define and describe the read and write permissions of the attributes in the object.

Legal verification: including legal compliance verification, association and inheritance verification, and normative and compliance verification.

Among them, legality and compliance inspection: The digital asset agency conversion system performs legality and compliance inspections on the uploaded objects, including whether the content is compliant and whether there is any false or untrue situation.

Associativity and Inheritance Test: Detects whether there are inheritance and association conflicts between objects. Types of conflicts include inconsistencies in category relationships. For example, the child in the first-level category is inconsistent with the father in the second-level category, the child in the upper-level category has redundant ciid, which was originally identified as the root category but the upper-level category appears again; or the class There are obvious logical conflicts in the inheritance between objects and so on.

Normative and conformity inspection: that is, to verify whether the ontology object is consistent with what is specified in the referenced (reference ID) category object, including size, data type, value range, etc.

Multi-running environment: Perform the operation of the ontology object of the custom operation type. After the write permission is granted, the system obtains a list of operations that the user can perform on the instance. The operation list is obtained through user authentication, including whether the user has the read permission to customize the operation object. The system gets the custom action in the action list. Execute custom operations: The system provides multiple operating environments such as JS, python, and C++, parses the instance body data according to the instance identifier being operated, and obtains the main method (main) of the custom operation, and passes the instance body data as parameters to the main method. Perform custom actions. That is, users can expand custom operations in the editor, perform self-programming under the multi-environment conditions of the original system, and add new programming methods to the main function, so as to perform richer operations on objects.

Dictionary recommendation and retrieval: The purpose of this application is to map and aggregate data sources from multiple sources. In order to map the aggregated data into a digital asset system, it is necessary to use correct metadata or attribute fields. This attribute is standardized Specifications and definitions, commonly used standards include eclass and standard metadata defined by various enterprises and industry associations.

Extraction rules and mapping methods: This module manages the mapping rules of the data and asset systems in response to the extraction. Responsible for specific mapping conversion functions.

Permission request access mechanism centered on digital assets: In the new data service system, the access permission control of data is based on the data object or even one of its attributes. If a user wants to obtain permission to access a certain data, The corresponding permission request and response mechanism should be established with it. In each data object, or in the attribute metadata that needs permission control, it is necessary to set a standard asset object model for standardized access control, support a relatively standardized access control mechanism, or specify a centralized normalization paradigm. At the same time, it should be based on the digital asset system that has been stored.

Category tag system storage module 93 : using data warehouse, mysql and other multi-database methods to store the constructed asset category system.

Coding module 94: This stage is to attach the Industrial Internet logo to the newly constructed category tagging system (for details, please refer to the Industrial Internet Logo Management Measures). Specifically how to apply for a logo, the whole process of approval is explained.

The discrimination module 95 is used for associating the construction of the class tag system with the mode management in the management module. If the cache module is selected, the constructed data is directly transmitted through the communication module. If the storage mode is adopted, the encapsulation obtained by encapsulating the transformed and aggregated asset objects needs to be stored.

The asset object database 96 is used to store the encapsulation obtained by encapsulating the transformed and converged asset objects for other use or transmission.

The communication module 97 mainly includes: a protocol detection unit, an adaptation conversion unit, a data loading unit and a transmission and transmission unit.

The protocol detection unit is used for identifying which protocol the received message data adopts through the protocol detection device.

The adaptation conversion unit selects the corresponding block according to the pre-set QOS through the adaptation conversion, so as to adapt to the existing protocol to achieve the purpose of compatibility.

The data loading unit effectively shares the encapsulated data according to the command specification defined by the data interoperability protocol and in combination with the transmission mode determined by the adaptation strategy.

The sending transmission unit is used to effectively share the encapsulated data according to the command specification defined by the data interoperability protocol and in combination with the transmission mode determined by the adaptation strategy.

Exemplary Electronics

Hereinafter, an electronic device according to an embodiment of the present disclosure will be described with reference to FIG. 10 . The electronic device may be either or both of the first device and the second device, or a stand-alone device independent of them that can communicate with the first device and the second device to receive the collected data from them input signal.

10 illustrates a block diagram of an electronic device according to an embodiment of the present disclosure.

As shown in FIG. 10 , the electronic device 10 includes one or more processors 11 and a memory 12 .

Processor 11 may be a central processing unit (CPU) or other form of processing unit having data processing capabilities and/or instruction execution capabilities, and may control other components in electronic device 10 to perform desired functions.

Memory 12 may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and/or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and/or cache memory (cache). The non-volatile memory may include, for example, a read only memory (ROM), a hard disk, a flash memory, and the like. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 11 may execute the program instructions to implement the data integration management method and/or the various embodiments of the present disclosure described above. Other desired features. Various contents such as input signals, signal components, noise components, etc. may also be stored in the computer-readable storage medium.

In one example, the electronic device 10 may also include an input device 13 and an output device 14 interconnected by a bus system and/or other form of connection mechanism (not shown).

For example, when the electronic device is the first device or the second device, the input device 13 may be the above-mentioned microphone or microphone array for capturing the input signal of the sound source. When the electronic device is a stand-alone device, the input device 13 may be a communication network connector for receiving the collected input signals from the first device and the second device.

In addition, the input device 13 may also include, for example, a keyboard, a mouse, and the like.

The output device 14 can output various information to the outside, including the determined distance information, direction information, and the like. The output device 14 may include, for example, displays, speakers, printers, and communication networks and their connected remote output devices, among others.

Of course, for simplicity, only some of the components in the electronic device 10 related to the present disclosure are shown in FIG. 10 , and components such as buses, input/output interfaces, and the like are omitted. Besides, the electronic device 10 may also include any other suitable components according to the specific application.

Exemplary computer program product and computer readable storage medium

In addition to the methods and apparatus described above, embodiments of the present disclosure may also be computer program products comprising computer program instructions that, when executed by a processor, cause the processor to perform the "exemplary method" described above in this specification The steps in the data integration management method according to various embodiments of the present disclosure are described in the section.

The computer program product may write program code for performing operations of embodiments of the present disclosure in any combination of one or more programming languages, including object-oriented programming languages, such as Java, C++, etc. , also includes conventional procedural programming languages, such as "C" language or similar programming languages. The program code may execute entirely on the user computing device, partly on the user device, as a stand-alone software package, partly on the user computing device and partly on a remote computing device, or entirely on the remote computing device or server execute on.

In addition, embodiments of the present disclosure may also be computer-readable storage media having computer program instructions stored thereon that, when executed by a processor, cause the processor to perform the above-described "Example Method" section of this specification Steps in a data integration management method according to various embodiments of the present disclosure described in .

The computer-readable storage medium may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may include, for example, but not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses or devices, or a combination of any of the above. More specific examples (non-exhaustive list) of readable storage media include: electrical connections with one or more wires, portable disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

The basic principles of the present disclosure have been described above with reference to specific embodiments. However, it should be pointed out that the advantages, advantages, effects, etc. mentioned in the present disclosure are only examples rather than limitations, and these advantages, advantages, effects, etc. should not be considered to be A must-have for each embodiment of the present disclosure. In addition, the specific details disclosed above are only for the purpose of example and easy understanding, but not for limitation, and the above details do not limit the present disclosure to be implemented by using the above specific details.

The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the various embodiments may be referred to each other. As for the system embodiment, since it basically corresponds to the method embodiment, the description is relatively simple, and for related parts, please refer to the partial description of the method embodiment.

The block diagrams of devices, apparatuses, apparatuses, and systems referred to in this disclosure are merely illustrative examples and are not intended to require or imply that the connections, arrangements, or configurations must be in the manner shown in the block diagrams. As those skilled in the art will appreciate, these means, apparatuses, apparatuses, systems may be connected, arranged, configured in any manner. Words such as "including", "including", "having" and the like are open-ended words meaning "including but not limited to" and are used interchangeably therewith. As used herein, the words "or" and "and" refer to and are used interchangeably with the word "and/or" unless the context clearly dictates otherwise. As used herein, the word "such as" refers to and is used interchangeably with the phrase "such as but not limited to".

The methods and apparatus of the present disclosure may be implemented in many ways. For example, the methods and apparatus of the present disclosure may be implemented in software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order of steps for the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Furthermore, in some embodiments, the present disclosure can also be implemented as programs recorded in a recording medium, the programs including machine-readable instructions for implementing methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

It should also be noted that, in the apparatus, device and method of the present disclosure, each component or each step may be decomposed and/or recombined. These disaggregations and/or recombinations should be considered equivalents of the present disclosure.

The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects without departing from the scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the aspects shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

The foregoing description has been presented for the purposes of illustration and description. Furthermore, this description is not intended to limit embodiments of the present disclosure to the forms disclosed herein. Although a number of example aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, changes, additions and sub-combinations thereof.

Claims (12)

1. a data integration management method, is characterized in that, comprises: Adapting at least one path corresponding to at least one database, and extracting data in the at least one database through the adapted path; Obtain at least one category tag information corresponding to the data, bind the category tag information and the data, and obtain an asset object; wherein, the asset object includes a category object and an ontology object; Compile the asset object according to the assigned identification code, and encapsulate the compiled asset object and the authority information corresponding to the asset object to obtain encapsulated data; Receive the request message sent by the client, and determine whether to send the encapsulated data to the client according to the permission information of the client and the permission information corresponding to the asset object. 2 . The method according to claim 1 , wherein the tag information includes the category tag information of a plurality of levels with affiliation; wherein each of the levels includes at least one category tag information. 3 . ; The obtaining at least one category tag information corresponding to the data, binding the category tag information and the data to obtain an asset object, including: determining the category tag information of at least one level corresponding to the data based on the static attribute and/or dynamic attribute corresponding to the data; Binding the data with at least one category tag information corresponding to the data to form the asset object; wherein the data is the data ontology of the asset object, and the category tag information is the asset The object's category object. 3. The method according to claim 2, characterized in that, determining the category tag information of at least one level corresponding to the data based on the static attributes and/or dynamic attributes corresponding to the data, comprising: determining at least one meta-attribute describing the static attribute and/or the dynamic attribute based on the static attribute and/or the dynamic attribute corresponding to the data; Based on the corresponding partial data in the at least one meta-attribute, the corresponding category tag information of at least one level is determined; wherein each category tag information corresponds to one piece of the partial data. 4 . The method according to claim 3 , wherein the data is bound with at least one category tag information corresponding to the data to form the asset object, comprising: 4 . Associating and binding each of the partial data in the at least one partial data included in the data with the class tag information corresponding to the partial data to obtain at least one of the asset objects; The affiliation between at least one of the asset objects is determined based on the affiliation between the levels corresponding to the category tag information. 5. The method according to any one of claims 1-4, characterized in that, in said receiving a request message sent by a client, determining whether to send the The encapsulated data is sent to the client, including: Receive, through the protocol adapter, the request message sent by the client through the communication protocol, and determine the encapsulated data corresponding to the request message; determining whether the authority information of the client matches the authority information corresponding to the asset object; In response to the client's permission information being matched with the permission information corresponding to the asset object, the encapsulation data corresponding to the request message is sent to the client. 6. The method according to claim 5, wherein the sending the encapsulated data corresponding to the request message to the client comprises: Perform parsing processing on the request message, and determine the operation type corresponding to the request message; Based on the flag bit information included in the operation type, determine at least one category tag information corresponding to the request message; The corresponding asset object is obtained based on the class tag information, and the package data corresponding to the asset object is sent to the client. 7. The method according to claim 6, characterized in that, performing parsing processing on the request message to determine an operation type corresponding to the request message, comprising: Format conversion is performed on the request message to obtain message data including a plurality of data blocks; wherein, the data blocks include a transmission block, a control block, a data block and a voucher block; Based on the flag bit information in the control block in the message data, the operation type corresponding to the message data is determined. 8. The method according to claim 7, wherein the determining at least one of the category tag information corresponding to the data based on the flag bit information included in the operation type comprises: Based on the flag bit information included in the operation type, matching the pre-stored at least one category tag information; In response to the existence of the matching category tag information, determining the category tag information as the category object of the message data; In response to no matching category tag information, category tag information is newly created based on the message data, and the newly created category tag information is used as a category object of the message data. 9. The method according to any one of claims 1-4, wherein the asset object is compiled according to the assigned identification code, and the compiled asset object is compiled with permission information corresponding to the asset object. Encapsulate, get encapsulated data, including: Perform at least one verification operation respectively on at least one category object and at least one ontology object included in the asset object; The asset object that has passed the verification is compiled according to the assigned identification code, and the compiled asset object is encapsulated with the authority information corresponding to the asset object to obtain encapsulated data. 10. A data integration management device, comprising: a data extraction module, configured to adapt at least one path corresponding to at least one database, and extract data in the at least one database through the adapted path; A data binding module, configured to obtain at least one category tag information corresponding to the data, bind the category tag information and the data to obtain an asset object; wherein the asset object includes a category object and an ontology object ; an object compiling module, configured to compile the asset object according to the assigned identification code, and encapsulate the compiled asset object and the authority information corresponding to the asset information to obtain encapsulated data; A data request module, configured to receive a request message sent by a client, and determine whether to send the encapsulated data to the client according to the permission information of the client and the permission information corresponding to the asset object. 11. A computer-readable storage medium, wherein the storage medium stores a computer program, and the computer program is used to execute the data integration management method according to any one of the preceding claims 1-9. 12. An electronic device, characterized in that the electronic device comprises: processor; a memory for storing the processor-executable instructions; The processor is configured to read the executable instructions from the memory and execute the instructions to implement the data integration management method according to any one of the preceding claims 1-9.

Images