CN117716349A

CN117716349A - Knowledge management system, method, device, electronic equipment and storage medium

Info

Publication number: CN117716349A
Application number: CN202180100338.2A
Authority: CN
Inventors: 高亮; 王文科; 李强
Original assignee: Siemens AG
Current assignee: Siemens AG
Priority date: 2021-07-30
Filing date: 2021-07-30
Publication date: 2024-03-15
Also published as: WO2023004807A1

Abstract

The application provides a knowledge management system, a method, a device, an electronic device and a storage medium, wherein the knowledge management system comprises: at least one knowledge management node, the at least one knowledge management node deployed on a blockchain; the knowledge management node is configured to perform the following processing: acquiring a target semantic data set input by a knowledge creator; after the target semantic data set is stored, acquiring a unique identifier of the target semantic data set; after determining that the target semantic data set is authentic according to the intelligent contract stored on the blockchain, storing a unique identification of the target semantic data set on the blockchain. The scheme can improve the safety of the semantic data set.

Description

Knowledge management system, method, device, electronic equipment and storage medium

Technical Field

The present disclosure relates to the field of knowledge management technologies, and in particular, to a knowledge management system, method, apparatus, electronic device, and storage medium.

Background

The Knowledge Graph (knowledgegraph) is a Knowledge system formed by structuring Knowledge, which contains basic facts, general rules and other related information, and is commonly used for tasks such as Knowledge extraction, storage and reasoning in the field of artificial intelligence. The semantic data sets (Semantics Datasets) may be used to construct knowledge-graphs that a user may utilize to develop applications, such as developing data retrieval applications, based on the knowledge-graphs constructed from the semantic data sets.

At present, a centralized management system is generally adopted to manage knowledge, when a plurality of parties participate in the preparation work of a semantic data set, each party can create a new semantic data set and update the created semantic data set, and the creation/update record of the semantic data set can be tampered, so that the security of the semantic data set cannot be ensured.

Disclosure of Invention

In view of this, the knowledge management system, method, apparatus, electronic device and storage medium provided by the present application can improve the security of the semantic data set.

In a first aspect, embodiments of the present application provide a knowledge management system, at least one knowledge management node, the at least one knowledge management node deployed on a blockchain;

the knowledge management node is configured to perform the following processing:

acquiring a target semantic data set input by a knowledge creator;

after the target semantic data set is stored, acquiring a unique identifier of the target semantic data set;

after determining that the target semantic data set is authentic according to the intelligent contract stored on the blockchain, storing a unique identification of the target semantic data set on the blockchain.

In a second aspect, embodiments of the present application further provide a knowledge management method performed by a knowledge management system, wherein the knowledge management system includes at least two knowledge management nodes deployed on a blockchain, the knowledge management method comprising:

the knowledge management node acquires a target semantic data set input by a knowledge creator;

the knowledge management node obtains a unique identification of the target semantic data set after the target semantic data set is stored;

the knowledge management node stores the unique identification of the target semantic data set on the blockchain after determining that the target semantic data set is trusted according to the intelligent contract stored on the blockchain.

In a third aspect, an embodiment of the present application further provides a knowledge management apparatus, including a module configured to implement an operation performed by the knowledge management node in the method provided in the second aspect.

In a fourth aspect, embodiments of the present application further provide an electronic device, including: the device comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;

The memory is configured to store at least one executable instruction that causes the processor to perform the operations performed by the knowledge management node in the method provided in the second aspect.

In a fifth aspect, embodiments of the present application further provide a computer readable storage medium having stored thereon computer instructions that, when executed by a processor, cause the processor to perform the operations performed by the knowledge management node in the method provided in the second aspect above.

After the trust of the target semantic data set is verified through the intelligent contract, the unique identification of the target semantic data set is stored on the blockchain, namely, the semantic data set stored on the blockchain corresponding to the unique identification is approved and trusted, so that the correctness and the safety of the target semantic data set are ensured from the source. In addition, when the user inquires the semantic data set, after the semantic data set required by the user is acquired, the unique identifier of the semantic data set is acquired through the blockchain, the acquired unique identifier is used for verifying the semantic data to determine whether the acquired semantic data set is tampered, and the semantic data set is sent to the user after the semantic data set is determined to be not tampered, so that the semantic data set sent to the user is ensured to be not tampered, and the safety of the semantic data set is further ensured.

For any of the above aspects, optionally, the knowledge management system further comprises a data storage node, the data storage node being disposed on the distributed storage system. The knowledge management node sends the target semantic data set to the data storage node, the data storage node stores the target semantic data set on the distributed storage system, a first index file used for indexing the ontology file in the target semantic data set is generated, the first index file is stored, the unique identification of the first index file is calculated, the unique identification of the first index file is sent to the knowledge management node, after the knowledge management node determines that the target semantic data set is reliable, the unique identification of the first index file is stored on the blockchain, the first index file is linked to a second index file, and the second index file is used for indexing the ontology file in the semantic data set from the knowledge management node last time.

After the target semantic data set is stored on the distributed storage system, a first index file for indexing the target semantic data set is generated, the first index file is stored on the distributed storage system, then the unique identification of the first index file is calculated, after the trust of the target semantic data set is verified, the unique identification of the first index file is stored on the blockchain, so that the unique identification of the first index file cannot be tampered, whether the storage path of the target semantic data set in the distributed storage system is tampered or not can be verified according to the unique identification of the first index file on the blockchain, the first index file can be searched from the distributed storage system through the unique identification of the first index file, so that the semantic data set which is created or updated by a user at each time can be searched from the distributed storage system more conveniently, the user can feed back the required semantic data set to the user more quickly when referring to the semantic data set, and the use experience of the user is improved.

For any of the above aspects, optionally, the data storage node generates at least one domain folder according to at least one service domain related to the target semantic data set, and further generates a first index file for linking to each domain folder and the second index file, where each service domain corresponds to one domain folder, different service domains correspond to different domain folders, each domain folder has a file link recorded therein, the file link is a link of each entity file belonging to the service domain corresponding to the domain folder and being the latest version in the distributed storage system, and the entity file includes data of the service domain in the target semantic data set.

Because the knowledge creator may create or update the semantic data sets in different business fields at the same time, when the target semantic data set input by the knowledge creator is stored, a domain folder is created according to the business field related to the target semantic data set, so that the different business fields related to the target semantic data set correspond to different domain folders, and then according to the business field to which each ontology file in the target semantic data set belongs, the links of the ontology file in the target semantic data set are recorded into the domain folders corresponding to the corresponding business fields, so that each domain folder is linked to the latest version of the ontology file in the corresponding business field, thereby storing the semantic data set according to the domains and versions, and facilitating management and version tracing of the semantic data set.

For any of the above aspects, optionally, the data storage node calculates a unique identifier of each domain folder and a unique identifier of an ontology file recorded in each domain folder, and sends the unique identifier of each domain folder and the unique identifier of the ontology file recorded in each domain folder to the knowledge management node, and the knowledge management node stores the unique identifier of each domain folder and the unique identifier of the ontology file recorded in each domain folder onto the blockchain after determining that the target semantic dataset is authentic.

The unique identification of the first index file is stored on the blockchain, when a user needs to inquire the target semantic data set, the unique identification of the first index file can be obtained by triggering the intelligent contract, the first index file is obtained from the distributed storage system according to the unique identification of the first index file, and then the target semantic data set can be obtained through the first index file, so that the semantic data set needed by the user can be conveniently searched from the distributed storage system. The unique identifiers of the domain folders linked to the first index file and the unique identifiers of the body files recorded by each domain folder are stored in the blockchain, so that the unique identifiers of the domain folders linked to the first index file and the unique identifiers of the body files recorded by each domain folder can be prevented from being tampered, and further the unique identifiers of the domain folders linked to the first index file and the unique identifiers of the body files recorded by each domain folder stored in the blockchain can be utilized to verify whether the corresponding body files are tampered or not, and the safety of a semantic data set is ensured.

For any of the above aspects, optionally, the knowledge management node encrypts the unique identification of the first index file with a key set by the knowledge creator and stores the encrypted unique identification of the first index file on the blockchain when storing the unique identification of the first index file on the blockchain.

By encrypting the unique identifier of the first index file, only the authenticated user can acquire the unique identifier of the first index file, and then the data on the distributed storage system is accessed according to the unique identifier of the first index file, so that the security of the data on the distributed storage system can be ensured.

For any of the above aspects, optionally, the knowledge management system further comprises at least one application node, the at least one application node deployed on the blockchain. The application node obtains a knowledge query request of a user for querying a target semantic data set, and sends the obtained knowledge query request to a knowledge management node; when the knowledge management node locally stores the target semantic data set, the knowledge management node verifies the trust of the target semantic data set through the intelligent contract according to the knowledge query request, and then sends the target semantic data set to the application node so as to supply the application node to visualize the target semantic data set.

When a user needs to access a semantic data set, firstly checking whether the semantic data set to be accessed by the user is cached in the knowledge management node, and if so, acquiring data from a distributed storage system is not needed, and the speed of feeding back the needed semantic data set to the user is improved, so that the use experience of the user can be improved.

For any of the above aspects, optionally, when the knowledge management node does not store the target semantic data set locally, the knowledge management node obtains the unique identifier of the first index file from the blockchain according to the knowledge query request, and sends the unique identifier of the first index file to the data storage node; the data storage node acquires a first index file from the distributed storage system according to the received unique identifier of the first index file, acquires each domain folder linked to the first index file from the distributed storage system according to the acquired first index file, acquires a target semantic data set from the distributed storage system according to each file link recorded in each acquired domain folder, and transmits the acquired target semantic data set to the knowledge management node; after the knowledge management node verifies that the obtained target semantic data set is credible through the intelligent contract, the target semantic data set is stored to the knowledge management node locally, and the target semantic data set is sent to the application node so as to be visualized by the application node.

When a user needs to access the target semantic data set, if the knowledge management node does not store the target semantic data set locally, the target semantic data set is acquired from the distributed storage system, and after the target semantic data set is verified to be credible, the target semantic data set is stored locally of the knowledge management node and is sent to the application node for visualization. The knowledge management node locally stores the semantic data sets accessed by the user, so that the times of accessing the distributed storage system can be reduced, the calculation pressure of the knowledge management system can be reduced, and the required semantic data sets can be returned to the user more quickly.

For any of the above aspects, optionally, the blockchain is a private chain. Because the unique identification of the index file is stored on the blockchain and the smart contract is also stored on the blockchain, the index file and smart contract do not want all users to have access to it for security reasons, and access rights to the content stored on the blockchain can be restricted through the private chain.

For any of the above aspects, optionally, the distributed storage system may be an interstellar file system, which may be better combined with a blockchain to implement secure storage of data, thereby further ensuring security of managed knowledge.

Drawings

FIG. 1 is a schematic diagram of a knowledge management system provided in an embodiment of the present application;

FIG. 2 is a schematic diagram of another knowledge management system provided in an embodiment of the application;

FIG. 3 is a schematic diagram of a data storage structure in a distributed storage system according to an embodiment of the present application;

FIG. 4 is a schematic diagram of yet another knowledge management system provided by an embodiment of the application;

FIG. 5 is a schematic diagram of a semantic data set storage method according to an embodiment of the present application;

FIG. 6 is a flow chart of a knowledge management method provided by an embodiment of the present application;

FIG. 7 is a schematic diagram of a knowledge management apparatus provided in an embodiment of the present application;

FIG. 8 is a schematic diagram of another knowledge management apparatus provided in an embodiment of the application;

fig. 9 is a schematic diagram of an electronic device shutdown in an embodiment of the present application.

List of reference numerals:

10: knowledge management system 20: blockchain 30: distributed storage system

60: knowledge management method 11: knowledge management node 12: data storage node

13: application node 14: knowledge approval node 21: intelligent contract

40: knowledge creator 700: knowledge management apparatus 701: data acquisition module

702: the identifier acquisition module 703: the storage module 704: transceiving module

900: electronic device 902: processor 904: communication interface

906: memory 908: communication bus 910: program

601: the knowledge management node obtains the target semantic data set input by the knowledge creator

602: after the target semantic data set is stored, the knowledge management node acquires the unique identifier of the target semantic data set

603: after determining that the target semantic data set is authentic, storing a unique identification of the target semantic data set on the blockchain

Detailed Description

As described above, a centralized management system is generally used to manage knowledge at present, the semantic data sets, the data models and the knowledge maps are all stored in a centralized manner on a server, multiple parties participating in the preparation of the semantic data sets can create new semantic data sets and update original semantic data sets, and the creation records and update records of the semantic data sets can also be modified. Since each participant can freely create and update the semantic data sets and the creation record and the update record of the semantic data sets can also be modified, there is a risk of maliciously creating or updating the semantic data sets by tampering with the creation record and the update record of the semantic data sets, and therefore the security of the semantic data sets cannot be ensured.

In the embodiment of the application, after the knowledge creator uploads the semantic data set in a creating or updating mode, the semantic data set is stored, the unique identifier of the semantic data set is obtained, and after the semantic data set is determined to be credible according to the intelligent contract stored on the blockchain, the unique identifier of the semantic data set is stored on the blockchain. The trust of the semantic data sets is verified through the intelligent contracts, the content validity of the semantic data sets uploaded by a knowledge creator is guaranteed, in addition, the unique identification of the semantic data sets is stored on the blockchain, the fact that the unique identification of the semantic data sets cannot be tampered can be guaranteed based on the characteristics of the blockchain, whether the stored semantic data sets are tampered or not can be verified according to the unique identification of the semantic data sets stored on the blockchain, and therefore the safety of the semantic data sets can be guaranteed.

The following describes in detail the knowledge management system, method, apparatus and electronic device provided in the embodiments of the present application with reference to the accompanying drawings.

As shown in fig. 1, an embodiment of the present application provides a knowledge management system 10, comprising: at least one knowledge management node 11, each knowledge management node 11 deployed on a blockchain 20;

the knowledge management node 11 is configured to obtain a target semantic data set input by a knowledge creator, obtain a unique identifier of the target semantic data set after the target semantic data set is stored, and store the unique identifier of the target semantic data set on the blockchain 20 after determining that the target semantic data set is trusted according to an intelligent contract stored on the blockchain 20.

In the embodiment of the application, for the target semantic data set uploaded by the knowledge creator, after the trust of the target semantic data set is verified through the intelligent contract, the unique identification of the target semantic data set is stored on the blockchain, namely, the semantic data set stored on the blockchain corresponding to the unique identification is approved and trusted, so that the correctness and the safety of the target semantic data set are ensured from the source. In addition, when the user inquires the semantic data set, after the semantic data set required by the user is acquired, the unique identifier of the semantic data set is acquired through the blockchain, the acquired unique identifier is used for verifying the semantic data to determine whether the acquired semantic data set is tampered, and the semantic data set is sent to the user after the semantic data set is determined to be not tampered, so that the semantic data set sent to the user is ensured to be not tampered, and the safety of the semantic data set is further ensured.

In the present embodiment, the knowledge management node 11 is located within a blockchain 20, and the blockchain 20 may be a point-to-point (P2P) network, with unique identifications of smart contracts and semantic data sets stored on the blockchain 20.

It should be noted that, the unique identifier of the semantic data set is used to identify the semantic data set, different semantic data sets correspond to different unique identifiers, and whether the semantic data set is tampered can be determined according to the unique identifiers. For example, the unique identifier of the semantic data set may be a hash value, an MD5 value, etc. of the semantic data set, that is, the semantic data set is calculated by an encryption algorithm such as a hash algorithm, an MD5 algorithm, etc. to obtain a hash value, an MD5 value, etc. that can uniquely identify the semantic data set as the unique identifier of the semantic data set.

In one possible implementation, on the basis of the knowledge management system 10 shown in fig. 1, after receiving the target semantic data set input by the knowledge creator, the target semantic data set may be stored on the distributed storage system, and an index file for indexing the ontology file in the target semantic data set is generated, and meanwhile, the index file generated for the semantic data set received this time is linked with the index file generated for the semantic data set received last time, so as to facilitate version management of the semantic data set. FIG. 2 is a schematic diagram of another knowledge management system 10 provided in an embodiment of the application, the knowledge management system 10 further comprising data storage nodes 12, as shown in FIG. 2, the data storage nodes 12 being deployed on a distributed storage system 30;

the knowledge management node 11 is configured to send the target semantic data set to the data storage node 12;

the data storage node 12 is configured to store the received target semantic data set on the early distributed storage system 30, generate a first index file for indexing an ontology file in the target semantic data set, and store the first index file on the distributed storage system 30, where the first index file is linked to a second index file, and the second index file is configured to index the ontology file in the semantic data set from the knowledge management node 11 last time;

The data storage node 12 is further configured to calculate a unique identifier of the first index file, and send the unique identifier of the first index file to the knowledge management node 11;

the knowledge management node 11 is further configured to store a unique identification of the first index file onto the blockchain 20 after determining that the target semantic data set is authentic.

In the embodiment of the present application, after receiving the target semantic data set input by the knowledge creator, the knowledge management node 11 sends the target semantic data set to the data storage node 12, and the data storage node 12 stores the target semantic data set on the distributed storage system 30. The target semantic data set is stored on the distributed storage system 30, and based on the characteristics of the distributed storage system 30, the difficulty of tampering of the target semantic data set can be increased, and meanwhile, the risk of losing the target semantic data set due to unexpected reasons can be reduced, so that the safety of the target semantic data set is improved.

After the data storage node 12 stores the target semantic data set on the distributed storage system 30, the data storage node 12 generates a first index file for indexing the ontology file in the target semantic data set, and at the same time, the first index file is further linked to a second index file, where the second index file is used for indexing the ontology file in the semantic data set received by the previous knowledge management node 11. The body files included in the target semantic data set can be obtained from the distributed storage system 30 through the first index file, and since the target semantic data set is a semantic data set newly created by a knowledge creator or a semantic data set after version update of the original semantic data set, after the target semantic data set is stored in the distributed storage system 30, the body files included in the target semantic data set are all the latest versions, that is, the body files of the latest versions can be obtained from the distributed storage system 30 through the first index file. Since the first index file is further linked to the second index file, the second index file is used for indexing the ontology file in the semantic data set stored in the distributed storage system 30 last time, and the second index file is further linked to the index file generated for the semantic data set stored in the distributed storage system 30 earlier, that is, the second index file can be obtained through the first index file, and further the ontology file of the old version can be obtained from the distributed storage system 30 through the second index file, so that version tracing and version management can be conveniently performed on the semantic data set through the index file.

After generating the first index file, the data storage node 12 stores the first index file on the distributed storage system 30, calculates a unique identifier of the first index file, and sends the unique identifier of the first index file to the knowledge management node 11, and the knowledge management node 11 stores the unique identifier of the first index file on the blockchain 20 after verifying that the target semantic data set is authentic. After determining that the target semantic data set is trusted, the knowledge management node 11 stores the unique identifier of the first index file on the blockchain 20, so that the unique identifier of the first index file cannot be tampered, and therefore whether the storage path of the target semantic data set in the distributed storage system 30 is tampered can be verified according to the unique identifier of the first index file on the blockchain, and the first index file can be searched from the distributed storage system 30 through the unique identifier of the first index file.

It should be noted that, corresponding to the unique identifier of the semantic data set, the unique identifier of the first index file may be a hash value, an MD5 value, or the like of the first index file.

It should be further noted that, storing the target semantic data set on the distributed storage system is only an alternative implementation manner of the embodiment of the present application, in other embodiments, the target semantic data set may be stored in a local storage of the knowledge management node 11, or the target semantic data set may be stored on a blockchain, or the target semantic data set may be stored in a cloud server, where the storage location of the target semantic data set is not limited in this embodiment of the present application.

In a possible implementation manner, after receiving the target semantic data set, the data storage node 12 generates at least one domain folder according to at least one service domain related to the target semantic data set, and further generates a first index file for linking to each domain folder and the second index file, where each service domain corresponds to one domain folder, different service domains correspond to different domain folders, each domain folder has a file link recorded therein, and the file link is a link of each entity file in the distributed storage system 30, which belongs to the service domain corresponding to the domain folder and is the latest version of each entity file, and the entity file includes data of the service domain in the target semantic data set.

In the embodiment of the application, since the knowledge creator may create or update the semantic data sets in different business fields at the same time, when the target semantic data set input by the knowledge creator is stored, the domain folder is created according to the business field related to the target semantic data set, so that the different business fields related to the target semantic data set correspond to the different domain folders, and then according to the business fields to which each body file belongs in the target semantic data set, the links of the body files in the target semantic data set are recorded in the domain folders corresponding to the corresponding business fields, so that each domain folder is linked to the latest version of the body file in the corresponding business field, thereby storing the semantic data set in the different fields and according to the version, and facilitating management and version tracing of the semantic data set.

In the embodiment of the present application, since the target semantic data set is a semantic data set newly created by the knowledge creator or a semantic data set after version update of the original semantic data set, after the target semantic data set is stored on the distributed storage system 30, the ontology files included in the target semantic data set are all the latest versions, so that links of the ontology files in the target semantic data set are all recorded in the corresponding domain folders. In addition, since the knowledge management system 10 can manage knowledge in different business fields, in order to more conveniently manage knowledge in different business fields, a domain folder can be generated according to the business fields, so that corresponding ontology files can be acquired through the generated domain folder.

In the embodiment of the present application, each time the knowledge creator creates a new semantic data set or updates an original semantic data set, the data storage node 12 generates one or more domain folders according to the service domain involved in the semantic data set after storing the semantic data set on the distributed storage system 30, and the domain folders are used for recording links of each ontology file of the latest version after the new semantic data set is created or the version of the semantic data set is updated. For distinction, the newly created domain folder of the data storage node 12 is referred to as a first domain folder, and the domain folder previously created by the data storage node 12 is referred to as a second domain folder. Since the knowledge creator may not update all of the semantic data sets stored on the distributed storage system 30 at the same time, the first domain folder and the second domain folder may have recorded links to the same ontology file. For example, links of the body file 1-V1, the body file 2-V2 and the body file 3-V1 are recorded in the second domain folder which is generated recently, and the knowledge creator only updates the body file 1-V1 to the body file 1-V2, then after the knowledge creator updates the body file 1-V1 to the body file 1-V2, links of the body file 1-V2, the body file 2-V2 and the body file 3-V1 are recorded in the first domain folder which is generated recently.

In the present embodiment, after each domain folder is generated for the target semantic dataset, the data storage node 12 also generates a first index file for linking to each domain folder. Because the first index file is linked to each domain folder, each domain folder can be obtained by obtaining the first index file, and then the body file can be obtained according to the file links recorded in the domain folder. For convenience of distinction, the index file linked to each first domain folder is referred to as a first index file, and the index file linked to each second domain folder is referred to as a second index file.

In the embodiment of the application, after the knowledge creator updates the semantic data set each time (including creating a new semantic data set or updating an original semantic data set), an index file is generated, and the latest version of each ontology file in the corresponding service field after the update of the semantic data set is recorded in each domain folder linked to the index file, so that a user can obtain the latest version of each ontology file after the update of the semantic data set according to the index file, and version management can be conveniently performed on the semantic data set by using the index file. In addition, index file links pointing to index files generated before are recorded in the index files generated recently, and body files of all old versions can be obtained through the index file links, so that version tracing of the semantic data set can be conveniently carried out through the index files. In addition, for each business field, the domain folder newly generated for the business field can be linked to the domain folder previously generated for the business field, namely, the domain folder recorded with the ontology file of the new version, and can be linked to the domain folder recorded with the ontology file of the old version, so that the semantic data set can be conveniently traced back in version through the domain folder.

The first index file is linked to the second index file, specifically, at least one index file link pointing to the second index file is recorded in the first index file, when one index file link is recorded in the first index file, the index file link may point to a recently generated second domain folder (i.e., a domain folder formed according to a semantic data set stored in the distributed storage system 30 last time), and when a plurality of index file links are recorded in the first index file, the index file links may sequentially point to N (N > 2) recently generated second domain folders. Because each domain folder records each ontology file of the latest version of the corresponding business field after the semantic data set is created or after the semantic data set is updated, and each generated domain folder is linked to one index file, the index file can be used as the creation record and the update record of the semantic data set on the distributed storage system 30, the data storage node 12 can store each index file on the distributed storage system 30, and the knowledge management node 11 can store the unique identification of each index file as the transaction record on the blockchain 20, thereby ensuring that the creation record and the update record of the semantic data set cannot be tampered and further improving the security of the semantic data set.

In one possible implementation, the data storage node 12 is further configured to calculate a unique identifier of each domain folder and a unique identifier of an ontology file recorded in each domain folder (i.e. an ontology file corresponding to a file link recorded in a domain folder), and send the unique identifier of each domain folder and the unique identifier of the ontology file recorded in each domain folder to the knowledge management node 11. After the smart contract determines that the target semantic data set is authentic, the knowledge management node 11 stores the received unique identification of each domain folder and the unique identification of the body file recorded in each domain folder onto the blockchain 20.

In this embodiment, after the smart contract determines that the target semantic data set is trusted, the knowledge management node 11 stores the unique identifier of the first index file on the blockchain 20, and stores the unique identifier of each domain folder to which the first index file is linked and the unique identifier of each body file recorded by each domain folder in the blockchain 20. When a user needs to query a target semantic data set, the unique identifier of the first index file can be obtained by triggering the intelligent contract, the unique identifier of the first index file is sent to the data storage node 12, and the data storage node 12 can obtain the first index file from the distributed storage system 30 according to the unique identifier of the first index file, so that the target semantic data set can be obtained through the first index file. Storing the unique identifier of each domain folder linked to the first index file and the unique identifier of each body file recorded by each domain folder into the blockchain 20 can avoid tampering of the unique identifier of each domain folder linked to the first index file and the unique identifier of each body file recorded by each domain folder, and further can verify whether the corresponding body file is tampered or not by using the unique identifier of each domain folder linked to the first index file and the unique identifier of each body file recorded by each domain folder stored in the blockchain 20.

It should be noted that, corresponding to the unique identifier of the semantic data set, the unique identifier of the domain folder may be a hash value, an MD5 value, etc. of the domain folder, and the unique identifier of the body file may be a hash value, an MD5 value, etc. of the body file.

In the embodiment OF the application, fig. 3 schematically shows a structural form OF data storage in the distributed storage system 30, where the distributed storage system 30 stores an ontology file OF1-V1, an ontology file OF2-V1, an ontology file OF1-V2, an ontology file OF3, a domain folder DF-V1, a domain folder DF-V2, and index files C1 to Cn, where the ontology file OF1-V2 is a new version OF the ontology file OF 1-V1.

The domain folder DF-V1 is linked to the body files OF1-V1, OF2-V1 and OF3 (i.e., the file links OF the body files OF1-V1, OF2-V1 and OF3 are recorded in the domain folder DF-V1), and the domain folder DF-V2 is linked to the body files OF1-V2, OF2-V1 and OF3 (i.e., the file links OF the body files OF1-V2, OF2-V1 and OF3 are recorded in the domain folder DF-V2).

Index file C1 is linked to domain folder DF-V1, index file C2 is linked to domain folder DF-V2, index file Cn is linked to domain folder DF-Vn (domain folder DF-Vn is not shown in the figure), and index file C2 has index file link P1 pointing to index file C1 recorded therein, and index file Cn has index file link Pn-1 pointing to index file Cn-1 recorded therein.

The index files C1 through Cn are stored sequentially into each of the blocks 1 through n in the blockchain 20, where the block n is located at the end of the blockchain 20.

After the knowledge creator updates the version OF the body file OF1 to obtain the body files OF1-V2, the body files OF2-V1 and OF3 are still the latest versions OF the respective body files OF2-V1 and OF3 because the body files OF2 and OF3 are not updated, so the domain folder DF-V2 generated by the data storage node 12 is linked to the body files OF1-V2, OF2-V1 and OF3.

It should be noted that fig. 3 is only an example of a storage structure in the distributed storage system 30, and more ontology files, domain folders, and index files are actually included in the distributed storage system 30, and there may be a case where the same index file is linked to a plurality of domain folders.

In one possible implementation, the knowledge management node 11, when storing the unique identification of the first index file onto the blockchain 20, first encrypts the unique identification of the first index file with a key set by the knowledge creator and then stores the encrypted unique identification onto the blockchain 20.

In this embodiment of the present application, the knowledge creator may set a key before uploading the target semantic data set, and the knowledge management node 11 encrypts the unique identifier of the first index file by using the key set by the knowledge creator, and further stores the encrypted unique identifier on the blockchain 20. Because the unique identifier of the first index file is used for searching the first index file from the distributed storage system 30, by encrypting the unique identifier of the first index file, only the authenticated user can acquire the unique identifier of the first index file, and then the data on the distributed storage system 30 is accessed according to the unique identifier of the first index file, so that the security of the data on the distributed storage system 30 can be ensured.

In one possible implementation, based on the knowledge management system 10 shown in fig. 2, as shown in fig. 4, the knowledge management system 10 may further include at least one application node 13, wherein each application node 13 is deployed on the blockchain 20;

the application node 13 is configured to obtain a knowledge query request of a user for querying a target semantic data set, and send the knowledge query request to the knowledge management node 11;

after receiving the knowledge query request, the knowledge management node 11 sends the target semantic data set to the application node 13 after checking that the locally stored target semantic data set is trusted through the intelligent contract if the target semantic data set is stored locally in the knowledge management node 11, so that the application node 13 can visualize the target semantic data set.

In this embodiment of the present application, after the application node 13 sends the knowledge query request to the knowledge management node 11, the knowledge management node 11 first checks whether a target semantic data set to be accessed by the user is stored locally according to the knowledge query request, if the knowledge management node 11 already stores the target semantic data set locally, the knowledge management node 11 verifies that the locally stored target semantic data set is trusted through an intelligent contract, and then sends the locally stored target semantic data set to the application node 13, so that the application node 13 visualizes the target semantic data set. When the semantic data set required by the user is stored locally in the knowledge management node 11, after the reliability of the semantic data set stored locally is verified, the semantic data set stored locally is sent to the user, so that the semantic data set is not required to be acquired by frequently accessing the distributed storage system 30, on one hand, the network bandwidth required by the knowledge management system 10 can be reduced, on the other hand, the rate of feeding back the semantic data set to the user can be improved, and further the use experience of the user is improved.

In this embodiment of the present application, when the knowledge management node 11 checks the target semantic data set through the intelligent contract, the intelligent contract may acquire the unique identifier of the target semantic data set from the blockchain 20, calculate the target semantic data set according to a preset encryption algorithm to acquire the unique identifier of the target semantic data set, then compare the unique identifier acquired by calculation with the unique identifier acquired from the blockchain 20, if the two identifiers are the same, determine that the target semantic data set is trusted, and if the two identifiers are different, determine that the target semantic data set is not trusted.

In one possible implementation, as shown in fig. 4, after receiving the knowledge query request, if the knowledge management node 11 does not locally store the target semantic data set to be accessed by the user, the knowledge management node 11 obtains the unique identifier of the first index file from the blockchain 20 according to the knowledge query request, and sends the unique identifier of the first index file to the data storage node 12. The data storage node 12 obtains the first index file from the distributed storage system 30 according to the received unique identifier of the first index file, obtains each domain folder to which the first index file is linked from the distributed storage system 30 according to the obtained first index file, obtains the target semantic data set from the distributed storage system 30 according to each file link recorded in each obtained domain folder, and sends the obtained target semantic data set to the knowledge management node 11. The knowledge management node 11 verifies whether the received target semantic data set is trusted through the intelligent contract, stores the target semantic data set to the local of the knowledge management node 11 after determining that the target semantic data set is trusted, and sends the target semantic data set to the application node 13 so as to supply the application node 13 to visualize the target semantic data set.

In this embodiment of the present application, after the application node 13 sends the knowledge query request to the knowledge management node 11, the knowledge management node 11 first checks whether a target semantic data set to be accessed by the user is already stored locally according to the knowledge query request, if the target semantic data set is not stored locally by the knowledge management node 11, the target semantic data set is obtained from the distributed storage system 30 through the application node 13, and after verifying that the target semantic data set is trusted, the target semantic data set is stored locally by the knowledge management node 11 and sent to the application node 13. The knowledge management node 11 locally stores the semantic data sets accessed by the user, so that the number of times of accessing the distributed storage system 30 can be reduced, the calculation pressure of the knowledge management system 10 can be reduced, and the required semantic data sets can be returned to the user more quickly.

In one possible implementation, on the basis of the knowledge management system 10 shown in fig. 4, the knowledge management system 10 further includes: the coordination node and at least one knowledge approval node are both deployed on the blockchain 20;

the coordination node is used for distributing accounts for users, different accounts have different rights, and after the users log in the equipment through the accounts distributed by the coordination node, the equipment is used as a knowledge management node 11, an application node 13 or a knowledge approval node in the knowledge management system 10 according to the rights of the logged-in accounts;

The coordination node also distributes different user identifications for each knowledge management node 11, each application node 13 and each knowledge approval node respectively, so that information interaction can be performed between the knowledge management nodes 11, the application nodes 13 and the knowledge approval nodes according to the user identifications of each other.

In the embodiment of the present application, since the knowledge management node 11 and the coordination node are in a central position in the entire knowledge management system 10, in order to ensure the security of the knowledge management node 11 and the coordination node, the knowledge management node 11 and the coordination node are selected through the intelligent contract with the highest voting authority, and the voting result can be updated according to the configured time interval.

In this embodiment of the present application, the coordinating node may allocate different user identifiers to each knowledge management node 11, each application node 13, and each knowledge approval node, so as to determine, by using the user identifiers, a group to which each node belongs, so that the knowledge management node 11 may perform information interaction with each application node 13 and each knowledge approval node according to the user identifiers, thereby ensuring orderly and safe operation of the entire knowledge management system 10.

In this embodiment of the present application, as shown in fig. 5, after obtaining the target semantic data set uploaded by the knowledge creator 40, the knowledge management node 11 sends the target semantic data set to the data storage node 12, the data storage node 12 stores the target semantic data set on the distributed storage system 30, on the other hand, the knowledge management node 11 generates a knowledge approval request for requesting the knowledge approver to approve the target semantic data set, and sends the generated knowledge approval request to at least one knowledge approval node 14 according to the intelligent contract 21, the knowledge approval node 14 that receives the knowledge approval request sends the approval result given by the knowledge approver to the intelligent contract 21, the intelligent contract 21 determines whether the target semantic data set is authentic according to each received approval result, and after obtaining the result that the intelligent contract 21 determines that the target semantic data set is authentic, the knowledge management node 11 stores the unique identifier of the target semantic data set on the block chain 20.

If the smart contract determines that the target semantic data is not trusted based on the received approval results, the knowledge management node 11 does not store a unique identification of the target semantic data set on the blockchain 20, thereby indicating that the target semantic data set is not trusted. Further, after determining that the target semantic data set is not trusted, the knowledge management node 11 may delete the target semantic data set from the distributed storage system 30 according to the intelligent contract, or may keep the target semantic data set in the distributed storage system 30, but set an untrusted flag for the target semantic data set to give an untrusted hint when the user queries the target semantic data set.

In the embodiment of the application, the knowledge approver is an expert in the field, sends a knowledge approval request to one or more knowledge approval nodes according to the intelligent contract, the corresponding knowledge approver approves the target semantic data set and gives out a corresponding approval result, and finally the intelligent contract determines whether the target semantic data set is credible or not according to the approval result returned by each knowledge approval node. The intelligent contract can determine whether the target semantic data set is credible according to the approval passing proportion in each approval result, for example, when more than 80% of the approval results are approval passing, the target semantic data set is determined to be credible.

In this embodiment of the present application, the target semantic data set acquired by the knowledge management node 11 may be a new semantic data set created by a knowledge creator, or may be an updated version of a stored semantic data set by the knowledge creator, so that the knowledge management system 10 may safely manage the new created semantic data set, or may safely manage semantic data sets of different versions updated by the knowledge creator.

In addition, the knowledge management node 11 may also generate a target knowledge graph according to the target semantic data set, and store the target semantic data set and the generated target knowledge graph together in the distributed storage system 30 through the data storage node 12. Correspondingly, the knowledge management node 11 may also generate a knowledge approval request for requesting approval of the target knowledge graph, and send the knowledge approval request to at least one knowledge approval node according to the intelligent contract, where the knowledge approval node may send an approval result of an approver for approving the target knowledge graph to the intelligent contract, and after the intelligent contract determines that the target knowledge graph is authentic according to the approval result, the knowledge management node 11 stores the unique identifier of the target knowledge graph on the blockchain 20. Therefore, the knowledge management system 10 provided in the embodiment of the present application can manage the semantic data set to ensure the security of the semantic data set, and can also manage the knowledge graph generated according to the semantic data set to ensure the security of the knowledge graph.

It should be noted that, each portion included in the knowledge management system 10 provided in the embodiment of the present application may be processed separately for a semantic data set, or may be processed for the semantic data set and a knowledge graph generated according to the semantic data set at the same time. In the foregoing embodiments, the knowledge graph generated from the semantic data set and the semantic data set may be used as the parallel knowledge management objects, and the knowledge graph may be managed by each part included in the knowledge management system 10 in the same manner as the semantic data set.

In one possible implementation, the blockchain 20 may be a private chain based on the knowledge management system 10 provided by the various embodiments described above. Because the unique identifier of the index file is stored on the blockchain 20, and the intelligent contract is also stored on the blockchain 20, for security reasons, the index file and the intelligent contract do not want all users to be able to access, and access rights to the content stored on the blockchain 20 can be limited through the private chain, so that the system is more suitable for the application scenario of the knowledge management system 10 provided by the application.

In one possible implementation, based on the knowledge management system 10 provided by the embodiments described above, the distributed storage system 30 may be an interstellar file system (InterPlanetary File System, IPFS), which may be better combined with the blockchain 20 to implement secure storage of data, thereby further ensuring the security of the knowledge management system 10 provided by the present application for managed knowledge.

The knowledge management method provided in the embodiments of the present application is described below, and may be implemented based on the knowledge management system 10 described above. Unless specifically stated otherwise, the distributed storage system involved in the knowledge management method described below may be the aforementioned distributed storage system 30, the knowledge management node involved in the knowledge management method described below may be the aforementioned knowledge management node 11, the data storage node involved in the knowledge management method described below may be the aforementioned data storage node 12, the application node involved in the knowledge management method described below may be the aforementioned application node 13, and the blockchain involved in the knowledge management method described below may be the aforementioned blockchain 20.

As shown in fig. 6, one embodiment of the present application provides a knowledge management method 60, which may include the steps of:

601. the knowledge management node acquires a target semantic data set input by a knowledge creator;

602. after the target semantic data set is stored, the knowledge management node acquires the unique identifier of the target semantic data set;

603. the knowledge management node stores the unique identification of the target semantic data set on the blockchain after determining that the target semantic data set is trusted according to the intelligent contract stored on the blockchain.

In one possible implementation, after the target semantic data set is obtained, the target semantic data set may be stored on the distributed storage system through the data storage node. The target semantic data set is stored, which can be realized by the following steps:

S1, a knowledge management node sends a target semantic data set to a data storage node;

s2, the data storage node stores the target semantic data set on a distributed storage system;

s3, the data storage node generates a first index file for indexing the ontology file in the target semantic data set, wherein the first index file is linked to a second index file, and the second index file is used for indexing the ontology file in the semantic data set from the knowledge management node last time;

s4, the data storage node stores the first index file;

s5, the data storage node calculates the unique identifier of the first index file and sends the unique identifier of the first index file to the knowledge management node;

s6, after the knowledge management node determines that the target semantic data set is credible, storing the unique identification of the first index file on the blockchain.

In the embodiment of the application, after the target semantic data set input by the knowledge creator is received, the target semantic data set is stored on the distributed storage system, and the difficulty of tampering of the target semantic data set can be increased based on the characteristics of the distributed storage system, and meanwhile, the risk of losing the target semantic data set due to unexpected reasons can be reduced, so that the safety of the target semantic data set is improved.

In the embodiment of the application, after the target semantic data set is stored on the distributed storage system, a first index file for indexing the target semantic data set is generated, the first index file is stored on the distributed storage system, then the unique identification of the first index file is calculated, after the trust of the target semantic data set is verified, the unique identification of the first index file is stored on the blockchain, so that the unique identification of the first index file cannot be tampered, whether the storage path of the target semantic data set in the distributed storage system is tampered or not can be verified according to the unique identification of the first index file on the blockchain, the first index file can be searched from the distributed storage system through the unique identification of the first index file, so that the semantic data set which is created or updated by a user each time can be searched from the distributed storage system more conveniently, the user can feed back the required semantic data set to the user more quickly when referring to the semantic data set, and the use experience of the user is improved.

In a possible implementation manner, when the first index file is generated, at least one domain folder may be generated according to at least one service domain related to the target semantic data set, and further a first index file for linking to each domain folder and the second index file is generated, where each service domain corresponds to one domain folder, different service domains correspond to different domain folders, file links are recorded in each domain folder, and the file links are links of each entity file belonging to the service domain corresponding to the domain folder and being the latest version in the distributed storage system, and the entity file includes data of the service domain in the target semantic data set.

In one possible implementation, based on the knowledge management method 60 shown in fig. 6, after determining each domain folder to which the first index file is linked, a unique identifier of each domain folder and a unique identifier of an ontology file recorded in each domain folder may be calculated, and after determining that the target semantic data set is trusted by the intelligent contract, the unique identifier of each domain folder and the unique identifier of the ontology file recorded in each domain folder are stored on the blockchain.

In the embodiment of the application, the unique identifier of the first index file is stored on the blockchain, when a user needs to query the target semantic data set, the unique identifier of the first index file can be obtained by triggering the intelligent contract, the first index file is obtained from the distributed storage system according to the unique identifier of the first index file, and then the target semantic data set can be obtained through the first index file, so that the semantic data set needed by the user can be conveniently searched from the distributed storage system. The unique identifiers of the domain folders linked to the first index file and the unique identifiers of the body files recorded by each domain folder are stored in the blockchain, so that the unique identifiers of the domain folders linked to the first index file and the unique identifiers of the body files recorded by each domain folder can be prevented from being tampered, and further the unique identifiers of the domain folders linked to the first index file and the unique identifiers of the body files recorded by each domain folder stored in the blockchain can be utilized to verify whether the corresponding body files are tampered or not, and the safety of a semantic data set is ensured.

In one possible implementation, when storing the unique identification of the first index file onto the blockchain, the unique identification of the first index file is first encrypted using a key set by the knowledge creator, and then the encrypted unique identification is stored onto the blockchain.

In the embodiment of the application, since the unique identifier of the first index file is used for searching the first index file from the distributed storage system, only the authenticated user can acquire the unique identifier of the first index file by encrypting the unique identifier of the first index file, and then the data on the distributed storage system is accessed according to the unique identifier of the first index file, so that the security of the data on the distributed storage system can be ensured.

In one possible implementation, on the basis of the knowledge management method 60 shown in fig. 6, the knowledge management method 60 further includes:

the application node obtains a knowledge query request of a user for querying a target semantic data set;

the application node sends the acquired knowledge inquiry request to a knowledge management node;

when the knowledge management node locally stores the target semantic data set, the knowledge management node verifies the credibility of the target semantic data set through the intelligent contract and then sends the target semantic data set to the application node so as to visualize the target semantic data set for the application node.

In the embodiment of the application, the semantic data set accessed by the user is cached in the local of the knowledge management node, when the user needs to access one semantic data set, whether the semantic data set to be accessed by the user is cached in the local of the knowledge management node is checked, if the semantic data set to be accessed by the user is cached in the local of the knowledge management node, the data does not need to be acquired from the distributed storage system, and the speed of feeding back the needed semantic data set to the user is improved, so that the use experience of the user can be improved.

when the knowledge management node does not store the target semantic data set locally, the knowledge management node acquires the unique identification of the first index file from the intelligent contract according to the knowledge query request;

the knowledge management node sends the unique identification of the first index file to the data storage node;

the data storage node acquires the first index file from the distributed storage system according to the received unique identifier of the first index file;

the data storage node acquires each domain folder linked to the first index file from the distributed storage system according to the acquired first index file;

the data storage node acquires a target semantic data set from the distributed storage system according to the acquired file links recorded in the domain folders, and sends the acquired target semantic data set to the knowledge management node;

after the knowledge management node verifies that the obtained target semantic data set is credible through the intelligent contract, the target semantic data set is stored and cached to the knowledge management node;

the knowledge management node sends the target semantic data set to the application node for the application node to visualize the target semantic data set.

In the embodiment of the application, when a user needs to access a target semantic data set, if the knowledge management node does not store the target semantic data set locally, the target semantic data set is acquired from the distributed storage system, and after the target semantic data set is verified to be credible, the target semantic data set is stored locally at the knowledge management node and is sent to an application node for visualization. The knowledge management node locally stores the semantic data sets (ontology files) accessed by the user, so that the number of times of accessing the distributed storage system can be reduced, the calculation pressure of the knowledge management system can be reduced, and the required semantic data sets can be returned to the user more quickly.

In one possible implementation, the blockchain may be a private chain based on the knowledge management method 60 shown in FIG. 6. Because the unique identification of the index file is stored on the blockchain and the smart contract is also stored on the blockchain, the index file and smart contract do not want all users to have access to it for security reasons, and access rights to the content stored on the blockchain can be restricted through the private chain.

In one possible implementation, based on the knowledge management method 60 shown in fig. 6, the distributed storage system may be an interstellar file system (InterPlanetary File System, IPFS), which may be better combined with a blockchain to implement secure storage of data, thereby further ensuring the security of the managed knowledge.

It should be noted that, the knowledge management method provided by the foregoing embodiments is implemented based on the knowledge management system provided by the foregoing embodiments, and the knowledge management method and the knowledge management system are based on the same inventive concept, and specific content of the knowledge management method may be referred to the description in the foregoing knowledge management system embodiments, which is not described herein again.

Fig. 7 is a schematic diagram of a knowledge management apparatus 700 provided in an embodiment of the present application, where the knowledge management apparatus 700 includes modules for implementing operations performed by the knowledge management node 11 in the foregoing method embodiment, specifically, as shown in fig. 7, the knowledge management apparatus 700 includes:

a data acquisition module 701, configured to acquire a target semantic data set input by a knowledge creator;

an identifier obtaining module 702, configured to obtain a unique identifier of the target semantic data set after the target semantic data set obtained by the data obtaining module 701 is stored;

the storage module 703 is configured to store the unique identifier of the target semantic data set on the blockchain after determining that the target semantic data set is trusted according to the intelligent contract stored on the blockchain.

In this embodiment of the present application, after the data acquisition module 701 acquires the target semantic data set, the identifier acquisition module 702 acquires the unique identifier of the target semantic data set, and after the target semantic data set is verified to be trusted by the smart contract, the storage module 703 stores the unique identifier of the target semantic data set in the blockchain. Because the blockchain is not tamper-proof, the semantic data sets stored on the blockchain corresponding to the unique identification are trusted, and the correctness and the safety of the target semantic data sets are ensured from the source. In addition, the storage module 703 stores the unique identifier of the target semantic data set on the blockchain, when the user queries the target semantic data set, the target semantic data set can be verified by the unique identifier stored on the blockchain to determine whether the target semantic data set is tampered, and after determining that the target semantic data set is not tampered, the target semantic data set is sent to the user, so that the target semantic data set sent to the user is ensured to be not tampered, and the security of the semantic data set can be further ensured.

Optionally, fig. 8 is a schematic diagram of another knowledge management apparatus 700 provided in an embodiment of the present application, as shown in fig. 8, the knowledge management apparatus 700 further includes:

the transceiver module 704 is configured to send the target semantic data set to the data storage node, store the target semantic data set on the distributed storage system by the data storage node, receive a unique identifier of a first index file from the data storage node, and send the unique identifier of the first index file to the storage module 703, where the first index file is used to index an ontology file included in the target semantic data set in the distributed storage system, the first index file is linked to a second index file, and the second index file is used to index the ontology file in the semantic data set acquired last time by the data acquisition module 701 in the distributed storage system;

the storage module 703 is further configured to store the unique identifier of the first index file onto the blockchain after determining that the target semantic data set is authentic.

Optionally, as shown in fig. 8, the transceiver module 704 is further configured to receive the unique identifier of each domain folder from the data storage node, and the unique identifier of the body file recorded in each domain folder, and send the received unique identifier of each domain folder and the unique identifier of the body file recorded in each domain folder to the storage module 703, where the storage module 703 is further configured to store the unique identifier of each domain folder and the unique identifier of the body file recorded in each domain folder onto the blockchain after determining that the target semantic dataset is authentic.

Optionally, as shown in fig. 8, the storage module 703 is further configured to encrypt the unique identifier of the first index file with a key set by the knowledge creator when storing the unique identifier of the first index file on the blockchain, and store the encrypted unique identifier of the first index file on the blockchain.

Optionally, as shown in fig. 8, the transceiver module 704 is further configured to receive a knowledge query request from an application node, and if the knowledge management node has a target semantic data set locally stored therein and accessed by the knowledge query request, after checking that the target semantic data set locally stored in the knowledge management node is trusted through the intelligent contract, send the target semantic data set to the application node, so as to provide the application node with a visualization of the target semantic data set.

Optionally, as shown in fig. 8, the transceiver module 704 is further configured to receive a knowledge query request from the application node, and if the local of the knowledge management node does not store the target semantic data set to be accessed by the knowledge query request, acquire the unique identifier of the first index file from the block chain according to the knowledge query request, and send the acquired unique identifier of the first index file to the data storage node. The transceiver module 704 is further configured to receive a target semantic data set from the data storage node, store the target semantic data set to a local location of the knowledge management node after verifying that the target semantic data set is authentic by the smart contract, and send the target semantic data set to the application node for visualization of the target semantic data set by the application node.

It should be noted that, the interactions between the modules in the above-mentioned knowledge management apparatus embodiment and the knowledge management system embodiment and the knowledge management method embodiment are based on the same inventive concept, and specific content may be referred to the descriptions in the foregoing knowledge management system embodiment and the knowledge management method embodiment, which are not repeated herein.

Fig. 9 is a schematic diagram of an electronic device provided in an embodiment of the present application, and the embodiment of the present application is not limited to a specific implementation of the electronic device. Referring to fig. 9, an electronic device 900 provided in an embodiment of the present application includes: a processor 902, a communication interface (Communications Interface), a memory 906, and a communication bus 908. Wherein:

processor 902, communication interface 904, and memory 906 communicate with each other via a communication bus 908.

A communication interface 904 for communicating with other electronic devices or servers.

The processor 902 is configured to execute the program 910, and specifically may perform the operations performed by the knowledge management node 11 in any of the foregoing knowledge management method embodiments.

In particular, the program 910 may include program code including computer-operating instructions.

The processor 902 may be a central processing unit, CPU, or specific integrated circuit ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement embodiments of the present application. The one or more processors comprised by the smart device may be the same type of processor, such as one or more CPUs; but may also be different types of processors such as one or more CPUs and one or more ASICs.

A memory 906 for storing a program 910. Memory 906 may comprise high-speed RAM memory or may also include non-volatile memory (non-volatile memory), such as at least one disk memory.

The program 910 may be specifically configured to cause the processor 902 to perform operations performed by the knowledge management node 11 in any of the foregoing knowledge management method embodiments.

The specific implementation of each step in the procedure 910 may refer to corresponding steps and corresponding descriptions in units in any of the foregoing knowledge management method embodiments, which are not described herein in detail. It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the apparatus and modules described above may refer to corresponding procedure descriptions in the foregoing method embodiments, which are not repeated herein.

According to the electronic equipment, after the target semantic data set uploaded by the knowledge creator is verified to be trusted through the intelligent contract, the unique identification of the target semantic data set is stored on the blockchain, namely, the semantic data set stored on the blockchain corresponding to the unique identification is approved to be trusted, so that the accuracy and the safety of the target semantic data set are ensured from the source. In addition, when the user inquires the semantic data set, after the semantic data set required by the user is acquired, the unique identifier of the semantic data set is acquired through the blockchain, the acquired unique identifier is used for verifying the semantic data to determine whether the acquired semantic data set is tampered, and the semantic data set is sent to the user after the semantic data set is determined to be not tampered, so that the semantic data set sent to the user is ensured to be not tampered, and the safety of the semantic data set is further ensured.

The present application also provides a computer readable storage medium storing instructions for causing a machine to perform the operations performed by the knowledge management node 11 in any of the knowledge management method embodiments described above. Specifically, a system or apparatus provided with a storage medium on which a software program code realizing the functions of any of the above embodiments is stored, and a computer (or CPU or MPU) of the system or apparatus may be caused to read out and execute the program code stored in the storage medium.

In this case, the program code itself read from the storage medium may realize the functions of any of the above-described embodiments, and thus the program code and the storage medium storing the program code form part of the present application.

Examples of the storage medium for providing the program code include a floppy disk, a hard disk, a magneto-optical disk, an optical disk (e.g., CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD+RW), a magnetic tape, a nonvolatile memory card, and a ROM. Alternatively, the program code may be downloaded from a server computer by a communication network.

Further, it should be apparent that the functions of any of the above-described embodiments may be implemented not only by executing the program code read out by the computer, but also by causing an operating system or the like operating on the computer to perform part or all of the actual operations based on the instructions of the program code.

Further, it is understood that the program code read out by the storage medium is written into a memory provided in an expansion board inserted into a computer or into a memory provided in an expansion module connected to the computer, and then a CPU or the like mounted on the expansion board or the expansion module is caused to perform part and all of actual operations based on instructions of the program code, thereby realizing the functions of any of the above embodiments.

It should be noted that not all the steps and modules in the above flowcharts and the system configuration diagrams are necessary, and some steps or modules may be omitted according to actual needs. The execution sequence of the steps is not fixed and can be adjusted as required. The system structure described in the above embodiments may be a physical structure or a logical structure, that is, some modules may be implemented by the same physical entity, or some modules may be implemented by multiple physical entities, or may be implemented jointly by some components in multiple independent devices.

In the above embodiments, the hardware module may be mechanically or electrically implemented. For example, a hardware module may include permanently dedicated circuitry or logic (e.g., a dedicated processor, FPGA, or ASIC) to perform the corresponding operations. The hardware modules may also include programmable logic or circuitry (e.g., a general-purpose processor or other programmable processor) that may be temporarily configured by software to perform the corresponding operations. The particular implementation (mechanical, or dedicated permanent, or temporarily set) may be determined based on cost and time considerations.

While the present application has been illustrated and described in detail in the drawings and in the preferred embodiments, the present application is not limited to the disclosed embodiments, and it will be appreciated by those skilled in the art that the code audits of the various embodiments described above may be combined to obtain further embodiments of the present application, which are also within the scope of the present application.

Claims

A knowledge management system (10), comprising: at least one knowledge management node (11), the at least one knowledge management node being deployed on a blockchain (20);

the knowledge management node is configured to perform the following processing:

acquiring a target semantic data set input by a knowledge creator;

after the target semantic data set is stored, acquiring a unique identifier of the target semantic data set;

after determining that the target semantic data set is authentic according to the smart contract stored on the blockchain (20), storing a unique identification of the target semantic data set on the blockchain (20).
The system of claim 1, wherein the knowledge management system (10) further comprises: a data storage node (12);

the data storage nodes (12) are deployed on a distributed storage system;

-the knowledge management node (11) further for sending the target semantic data set to the data storage node (12);

the data storage node (12) is configured to store the target semantic data set on the distributed storage system, generate a first index file for indexing an ontology file in the target semantic data set, store the first index file, calculate a unique identifier of the first index file, and send the unique identifier of the first index file to the knowledge management node (11), wherein the first index file is linked to a second index file, and the second index file is configured to index the ontology file in the semantic data set from the knowledge management node (11) last time;

the knowledge management node (11) is further configured to store a unique identification of the first index file onto the blockchain (20) after determining that the target semantic data set is authentic.
The system according to claim 2, wherein the data storage node (12) is adapted to perform the following process:

generating at least one domain folder according to at least one service field related to the target semantic data set, wherein each service field corresponds to one domain folder, different service fields correspond to different domain folders, file links are recorded in each domain folder, the file links are links of all ontology files which belong to the service field corresponding to the domain folder and are in the latest version in the distributed storage system, and the ontology files comprise data of the service field in the target semantic data set;

The first index file is generated for linking to each of the domain folders and the second index file.
The system of claim 3, wherein the system further comprises a controller configured to control the controller,

the data storage node (12) is further configured to calculate a unique identifier of each domain folder and a unique identifier of an ontology file recorded in each domain folder, and send the unique identifier of each domain folder and the unique identifier of the ontology file recorded in each domain folder to the knowledge management node (11);

the knowledge management node (11) is further configured to store, after determining that the target semantic data set is authentic, a unique identifier of each domain folder and a unique identifier of an ontology file recorded in each domain folder onto the blockchain (20).
The system of claim 2, wherein the system further comprises a controller configured to control the controller,

the knowledge management node (11) is further configured to encrypt the unique identifier of the first index file with a key set by the knowledge creator and store the encrypted unique identifier of the first index file on the blockchain (20) when storing the unique identifier of the first index file on the blockchain (20).
A system according to claim 3, characterized in that the knowledge management system (10) further comprises: at least one application node (13);

-said at least one application node (13) is deployed on said blockchain (20);

the application node (13) is configured to obtain a knowledge query request for querying the target semantic data set by a user, and send the obtained knowledge query request to the knowledge management node (11);

the knowledge management node (11) is further configured to, when the knowledge management node (11) has locally stored the target semantic data set, verify, according to the knowledge query request, that the target semantic data set is authentic through the intelligent contract, and then send the target semantic data set to the application node (13) so that the application node (13) can visualize the target semantic data set.
The system of claim 6, wherein the system further comprises a controller configured to control the controller,

the knowledge management node (11) is further configured to obtain, when the knowledge management node (11) does not locally store the target semantic data set, a unique identifier of the first index file from the blockchain (20) according to the knowledge query request, and send the unique identifier of the first index file to the data storage node (12);

The data storage node (12) is further configured to obtain the first index file from the distributed storage system according to the received unique identifier of the first index file, obtain each domain folder to which the first index file is linked from the distributed storage system according to the obtained first index file, obtain the target semantic data set from the distributed storage system according to each file link recorded in each obtained domain folder, and send the obtained target semantic data set to the knowledge management node (11);

the knowledge management node (11) is further configured to store the target semantic data set to the knowledge management node (11) locally after the target semantic data set obtained through the intelligent contract verification is trusted, and send the target semantic data set to the application node (13) so that the application node (13) can visualize the target semantic data set.
The system according to any one of claims 1 to 7, wherein,

the blockchain (20) is a private chain and/or the distributed storage system is an interplanetary file system (IPFS).
A knowledge management method, characterized by being performed by a knowledge management system (10), wherein the knowledge management system (10) comprises at least two knowledge management nodes (11) deployed on a blockchain (20), the knowledge management method comprising:

the knowledge management node (11) acquires a target semantic data set input by a knowledge creator;

the knowledge management node (11) acquires a unique identifier of the target semantic data set after the target semantic data set is stored;

the knowledge management node (11) stores a unique identification of the target semantic data set on the blockchain (20) after determining that the target semantic data set is authentic according to the intelligent contract stored on the blockchain (20).
The method of claim 9, wherein the knowledge management system (10) further comprises a data storage node (12), the data storage node (12) being deployed on a distributed storage system, the method further comprising:

-the knowledge management node (11) sending the target semantic data set to the data storage node (12);

the data storage node (12) storing the target semantic data set on the distributed storage system;

The data storage node (12) generates a first index file for indexing an ontology file in the target semantic data set, wherein the first index file is linked to a second index file, and the second index file is used for indexing the ontology file in the semantic data set from the knowledge management node (11) last time;

the data storage node (12) stores the first index file;

the data storage node (12) calculates the unique identifier of the first index file and sends the unique identifier of the first index file to the knowledge management node (11);

the knowledge management node (11) stores a unique identification of the first index file onto the blockchain (20) upon determining that the target semantic data set is authentic.
The method of claim 10, wherein generating a first index file for indexing an ontology file in the target semantic dataset comprises:

generating at least one domain folder according to at least one service field related to the target semantic data set, wherein each service field corresponds to one domain folder, different service fields correspond to different domain folders, file links are recorded in each domain folder, the file links are links of all ontology files which belong to the service field corresponding to the domain folder and are in the latest version in the distributed storage system, and the ontology files comprise data of the service field in the target semantic data set;

The first index file is generated for linking to each of the domain folders and the second index file.
The method of claim 11, wherein the method further comprises:

the data storage node (12) calculates a unique identifier of each of the domain folders and a unique identifier of an ontology file recorded in each of the domain folders;

the data storage node (12) sends the unique identification of each domain folder and the unique identification of the body file recorded in each domain folder to the knowledge management node (11);

the knowledge management node (11) stores a unique identification of each domain folder and a unique identification of an ontology file recorded in each domain folder onto the blockchain (20) after determining that the target semantic data set is authentic.
The method of claim 10, wherein said storing the unique identification of the first index file onto the blockchain (20) comprises:

encrypting the unique identifier of the first index file by using a key set by the knowledge creator;

storing the unique identification of the encrypted first index file onto the blockchain (20).
The method of claim 11, wherein the knowledge management system (10) further comprises at least one application node (13), the application node (13) being deployed on the blockchain (20), the method further comprising:

the application node (13) obtains a knowledge query request for a user to query the target semantic data set;

the application node (13) sends the acquired knowledge query request to the knowledge management node (11);

when the knowledge management node (11) locally stores the target semantic data set, the knowledge management node (11) verifies that the target semantic data set is trusted through the intelligent contract according to the knowledge query request, and then the target semantic data set is sent to the application node (13) so that the application node (13) can visualize the target semantic data set.
The method of claim 14, wherein the method further comprises:

when the knowledge management node (11) does not store the target semantic data set locally, the knowledge management node (11) acquires a unique identifier of the first index file from the intelligent contract according to the knowledge query request;

-the knowledge management node (11) sending a unique identification of the first index file to the data storage node (12);

the data storage node (12) acquires the first index file from the distributed storage system according to the received unique identifier of the first index file;

the data storage node (12) acquires each domain folder to which the first index file is linked from the distributed storage system according to the acquired first index file;

the data storage node (12) acquires the target semantic data set from the distributed storage system according to the acquired file links recorded in the domain folders, and sends the acquired target semantic data set to the knowledge management node (11);

after the knowledge management node (11) verifies that the obtained target semantic data set is credible through the intelligent contract, the target semantic data set is stored and cached to the knowledge management node (11) locally;

the knowledge management node (11) sends the target semantic data set to the application node (13) for the application node (13) to visualize the target semantic data set.
The method according to any one of claims 9 to 15, wherein,

the blockchain (20) is a private chain and/or the distributed storage system is an interplanetary file system (IPFS).
Knowledge management apparatus comprising means for implementing the operations performed by the knowledge management node (11) in the method of any one of claims 9-16.
An electronic device, comprising: -a processor (902), a communication interface (904), a memory (906) and a communication bus (908), said processor (902), said memory (906) and said communication interface (904) completing communication with each other through said communication bus (908);

the memory (906) is configured to store at least one executable instruction that causes the processor (902) to perform the operations performed by the knowledge management node (11) in the method of any one of claims 9-16.
A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon computer instructions, which when executed by a processor, cause the processor to perform the operations performed by the knowledge management node (11) in the method of any of claims 9-16.