WO2023050568A1 - 数据查询的方法、数据服务和电子设备 - Google Patents
数据查询的方法、数据服务和电子设备 Download PDFInfo
- Publication number
- WO2023050568A1 WO2023050568A1 PCT/CN2021/136184 CN2021136184W WO2023050568A1 WO 2023050568 A1 WO2023050568 A1 WO 2023050568A1 CN 2021136184 W CN2021136184 W CN 2021136184W WO 2023050568 A1 WO2023050568 A1 WO 2023050568A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- ontology
- target
- data service
- instance
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 54
- 238000013507 mapping Methods 0.000 claims description 19
- 238000004891 communication Methods 0.000 claims description 16
- 230000004927 fusion Effects 0.000 claims description 15
- 238000010586 diagram Methods 0.000 description 13
- 230000006870 function Effects 0.000 description 7
- 238000012545 processing Methods 0.000 description 6
- 238000007726 management method Methods 0.000 description 5
- 238000004590 computer program Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000013499 data model Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 238000013473 artificial intelligence Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/33—Querying
- G06F16/332—Query formulation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/36—Creation of semantic tools, e.g. ontology or thesauri
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/951—Indexing; Web crawling techniques
Definitions
- the present application relates to the field of data query, and more specifically, to a data query method, data service and electronic equipment.
- IT information technology
- OT operational technology
- the present application provides a data query method, data service and electronic equipment, which can effectively improve the efficiency of data query on the basis of reducing costs.
- a data query method including: a data service receives first input information, and the first input information includes an identifier of a target ontology; and the data service outputs target data based on the identifier of the target ontology , the target data includes instance data of the target ontology and/or instance data of at least part of the ontology that has a connection relationship with the target ontology, and the instance data of the target ontology and the instance data of at least part of the ontology come from multiple systems.
- the target data output by the data service is the instance data of the target ontology and/or the instance data of the ontology that has a connection relationship with the target ontology, that is to say, the data that the user queries based on the target ontology is largely of interest to the user. That is, the data that is concerned, that is, the embodiment of the present application makes the data obtained by the user more valuable.
- the instance data of the target ontology and at least part of the instance data of the ontology come from multiple systems, the data in multiple systems can be queried through the data service of the embodiment of this application, avoiding the need to The question of querying one by one further improves the efficiency of data query.
- the first input information further includes at least one of the following parameters: the attribute of the target ontology; the connection relationship between the target ontology and the first ontology, and the first ontology There is a connection relationship with the target ontology, and the at least part of the ontology includes the first ontology; wherein, the target data includes instance data of the target ontology and instance data of the first ontology.
- the first input information includes the attributes of the target ontology and/or the connection relationship between the target ontology and other ontology
- the other ontology is the ontology associated with the data that the user wants to obtain.
- the method further includes: the data service fuses multiple knowledge graphs to obtain a fused knowledge graph, where the fused knowledge graph includes the target ontology, the at least part of the ontology, and the A connection relationship between the target ontology and the at least part of the ontologies; wherein, the fused knowledge graph further includes access information of each ontology in the fused knowledge graph, and the access information is used to indicate the access information used to access the Raw data service for each ontology.
- the data service can integrate multiple knowledge graphs, so that data can be output for users based on the fused knowledge graphs, so that information islands can be eliminated, and users can query multiple data subject domain systems using one data service.
- Data realizing higher-dimensional data services and providing higher-value data services.
- the data service outputs target data based on the target ontology identification, including: the data service based on the target ontology identification and access to the target ontology in the fused knowledge graph information to determine the original data service used to access the target ontology; the data service controls the original data service used to access the target ontology to output the target data.
- the data service can accurately determine the original data service that accesses the target ontology based on the access information indicating the original data service that accesses the target ontology, and makes the original data service output Target data, so that the data queried by users can be more accurate.
- the data service includes a self-describing interface, and the self-describing interface is used to indicate a data service type provided by the data service.
- the data service includes a self-describing interface for indicating the type of data service it provides, so that users can selectively use the data service according to the requirements of data query and the self-description information of the data service, effectively improving the efficiency of data query .
- the data service includes a data query interface, and the data query interface is a semantic interface
- the data service receiving first input information includes: the data service receiving the first input information through the data query interface;
- the data service outputting the target data based on the target ontology identifier includes: the data service outputting the target data through the data query interface based on the target ontology identifier.
- the above technical solution sets the data query interface as a semantic interface.
- the semantic interface can provide a complete and easy-to-understand API interface data description, enabling users to accurately query the data they need, and does not need to implement other more More codes make API interface development easier and more efficient.
- users query different data in the data service they only need to modify the input information input to the data service, and do not need to establish an interface for data query every time they perform data query, which is beneficial to reduce data The cost of the query.
- the data service outputting the target data based on the target ontology identifier includes: the data service outputs the target data based on the target ontology identifier and the mapping relationship between ontology and instance data.
- the target data, the mapping relationship between the ontology and instance data is determined according to the attributes of the ontology and the attributes of the instance data.
- a data service including units for performing the methods in the above first aspect or various implementations thereof.
- an electronic device including: a memory for storing programs; a processor for executing the programs stored in the memory, and when the programs stored in the memory are executed, the processor is used for executing The above first aspect or the method in each implementation manner thereof.
- a computer-readable storage medium storing program code for execution by a device, where the program code includes instructions for executing the steps in the method in the above-mentioned first aspect or each implementation manner thereof.
- FIG. 1 is a schematic diagram of a data query method according to an embodiment of the present application.
- Fig. 2 is a schematic diagram of a KG of the embodiment of the present application.
- FIG. 3 is a schematic diagram of a KGA accessed by data service A according to an embodiment of the present application.
- Fig. 4 is a schematic diagram of the KGB accessed by the data service B according to the embodiment of the present application.
- Fig. 5 is a schematic diagram of KGC after the fusion of KGA shown in Fig. 3 and KGB shown in Fig. 4 according to the embodiment of the present application.
- Fig. 6 is a schematic diagram of a data service according to an embodiment of the present application.
- Fig. 7 is a schematic diagram of an electronic device according to an embodiment of the present application.
- the data service receives first input information
- the data server outputs target data based on the identifier of the target ontology
- serial numbers of the processes do not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, rather than by the implementation order of the embodiments of the present application.
- the implementation process constitutes no limitation.
- the financial system includes customer information, contract information, and asset information.
- the dealer management system includes contract information and inventory information.
- the financial system and dealer management systems are isolated from each other. .
- the embodiment of the present application proposes a data query method, which can effectively improve the efficiency of data query on the basis of reducing costs.
- FIG. 1 shows a schematic flowchart of a data query method 100 according to an embodiment of the present application. As shown in FIG. 1 , the method 100 may include at least part of the following contents.
- a data service receives first input information, and the first input information includes an identifier of a target ontology (ontology).
- the data service outputs target data based on the identification of the target ontology, the target data includes instance data of the target ontology and/or instance data of at least part of the The instance data of some ontology come from multiple systems.
- the target data output by the data service is the instance data of the target ontology and/or the instance data of the ontology connected with the target ontology. That is, the data that is concerned, that is, the embodiment of the present application makes the data obtained by the user more valuable.
- the data service of the embodiment of the present application can query the target data in at least one system, avoiding the need to The system queries one by one, which further improves the efficiency of data query.
- the data service in the embodiment of the present application is applied to the entire system, the data service can be understood as a node in the system.
- an ontology may be a semantic data model that is used to define types of practices in a domain and the attributes that can be used to describe them.
- Ontology can be understood as a generalized data model, which means that ontology only models the general types of things with certain attributes, and does not contain information about specific individuals in the domain.
- Figure 2 includes three ontologies, namely non conformity report (NCR), material and worker.
- NCR non conformity report
- the ontology in this embodiment of the present application may be established based on an existing standard, that is, the ontology is a standardized ontology.
- the ontology may be established based on the ISA95 standard.
- Ontology is a standardized ontology. In this way, when users use this data service for data query, they do not need to consider whether the multiple systems queried through this data service are the same. Users can use this data service in different scenarios.
- the ontology of this embodiment of the present application may be defined by a knowledge graph (knowledge graph, KG).
- KG can essentially be a knowledge base called a semantic network, that is, a knowledge base with a directed graph structure.
- Figure 2 is a KG, and the ontology is the node of the KG.
- the edges in Figure 2 represent various semantic relationships between ontologies, such as the connection relationship between two ontologies.
- Data service can access KG, and KG defines multiple ontologies. Since the ontology is a standardized ontology, the data service in the embodiment of the present application is also a standardized data service. That is, the data service in this embodiment of the application is standardized through ontology.
- the instance data of the ontology may come from at least one system.
- the at least one system may be, but not limited to, the aforementioned IT system or OT system, such as an enterprise resource planning system (enterprise resource planning, ERP), a manufacturing execution system (manufacturing execution system, MES) or data acquisition and monitoring System (supervisory control and data acquisition, SCADA), etc.
- ERP enterprise resource planning
- MES manufacturing execution system
- SCADA supervisory control and data acquisition
- the at least one system may be a heterogeneous system.
- the data service can further output target data based on the mapping relationship between ontology and instance data.
- the data service can output target data based on the identification of the target ontology and the mapping relationship between ontology and instance data.
- mapping relationship between the ontology and the instance data may be determined according to the attributes of the ontology and the attributes of the instance data.
- the attributes of the ontology may be parameters such as the size of the house, the area of the house, the location of the house, and the shape of the house, for example.
- mapping relationship between ontology and instance data may be manually determined by developers.
- the mapping relationship between ontology and instance data may be determined by developers based on artificial intelligence (AI).
- AI artificial intelligence
- Using AI to determine the mapping relationship between ontology and instance data can greatly improve the work efficiency of developers.
- mapping relationship between ontology and instance data may be implemented by the service engine module in the data service.
- it may also be implemented by other modules, which is not specifically limited in this embodiment of the present application.
- Fig. 3 shows a schematic diagram of the mapping relationship between the ontology in the KGA accessed by the data service A and the instance data in the system. It should be noted that the KGA and the mapping relationship in Figure 3 are included in the data service A, but it does not mean that the data service A includes the KGA and the mapping relationship, but only to show that the data service A can access the KGA and the mapping relationship.
- the KGA includes three ontologies, namely the ontology EA, the ontology EB and the ontology EC.
- the ontology EA and the ontology EB have a connection relationship
- the ontology EA and the ontology EC have a connection relationship.
- the IT system includes three sets of instance data, which are instance data DA, instance data DB, and instance data DC. Among them, ontology EA is mapped to instance data DA, ontology EB is mapped to instance data DB, and ontology EC is mapped to instance data DC.
- the data service A can output the instance data of the ontology EA to the user, that is, the output instance Data DA; or, in addition to outputting the instance data DA, the instance data of the ontology EB and EC that have a connection relationship with the ontology EA can also be output, that is, the instance data DB and the instance data DC.
- the first input information may also include attributes of the target ontology and/or a connection relationship between the target ontology and the first ontology, and the first ontology has a connection relationship with the target ontology.
- the target data includes instance data of the target ontology and instance data of the first ontology.
- the target ontology is Ontology EA
- the user wants to query not only the instance data of Ontology EA but also the instance data of Ontology EB, then the user can input Ontology EA and the relationship between Ontology EA and Ontology EB to data service A.
- the data service can output the instance data of ontology EA and instance data of ontology EB, that is, instance data DA and instance data DB.
- the user when the user needs to query the instance data of the ontology EB and the instance data of the ontology EC, it can be seen from Fig. 3 that there is no edge between the ontology EB and the ontology EC, that is, there is no connection relationship. Therefore, the user can input the ontology EB, the ontology EC, the connection relationship between the ontology EB and the ontology EA, and the connection relationship between the ontology EA and the ontology EC to the data service. In this way, the data service can output the instance data of the Ontology EB and the instance data of the Ontology EC to the user, that is, the instance data DB and the instance data DC.
- the first input information includes the attributes of the target ontology and/or the connection relationship between the target ontology and other ontology
- the other ontology is the ontology associated with the data that the user wants to obtain.
- ontology EA, ontology EB, and ontology EC in Fig. 3 can be mapped to instance data DA, instance data DB, and instance data DC one by one, and can also have a mapping relationship with multiple instance data.
- ontology EA can also be mapped to instance data DB and instance data DC.
- instance data in the embodiment of the present application may also be called a data model, a data table, data or other names.
- the data service may include a self-describing interface, and the self-describing interface may be used to indicate the data service type provided by the data service.
- the data service type may be classified with reference to the classification method of the data subject field.
- data service types can be classified into human resource (HR) data services, product data services, financial data services, and equipment data services.
- HR human resource
- the data service includes a self-describing interface for indicating the type of data service it provides, so that users can selectively use the data service according to the requirements of data query and the self-description information of the data service, effectively improving the efficiency of data query .
- data services can also include ontology query interfaces.
- the ontology query interface can be used to indicate the instance data of the ontology. For example, if the data service type provided by the data service is HR data service, the user can confirm that the HR data service can specifically query company data, salary data, employee data, etc. through the ontology query interface.
- the data service may also include a data query interface.
- step 110 may specifically be: the data service receives the first input information through the data query interface;
- step 120 may specifically be: the data service outputs the target data through the data query interface based on the identifier of the target ontology.
- the data query interface may be a semantic interface.
- the data query interface may be an interface of SPARQL syntax, or the data query interface may be an interface of GraphQL syntax.
- Semantic interfaces can provide a complete and easy-to-understand application programming interface (application programming interface, API) data description, enabling users to accurately query the data they need, and do not need to implement other more codes, making API Interface development becomes simpler and more efficient.
- API application programming interface
- users query different data in the data service they only need to modify the input information input to the data service, and do not need to establish an interface for data query every time they perform data query, which is beneficial to reduce data The cost of the query.
- the data query interface may include an interface. Due to the high cost of developing an interface, compared with the solution that requires the development of an interface for one query of data, the data query interface includes one interface, which greatly reduces the cost of data query.
- the data query interface is a semantic interface
- users need to query ontology EA and ontology EB, they can enter ontology EA, ontology EB, and the connection relationship between ontology EA and ontology EB in data service A; when users need to query ontology EA and ontology EB
- Ontology EC Ontology EA, Ontology EC, and the connection relationship between Ontology EA and Ontology EC can be input in data service A, and there is no need to convert the data query interface.
- the data query interface is another type of interface
- an interface needs to be developed, which is used to realize the function of querying ontology EA and ontology EB
- an interface needs to be developed, which is used to realize the function of querying ontology EA and ontology EC.
- data service A can realize the purpose of querying all data with only one data query interface.
- the data query interface may be another interface except the semantic interface.
- different data services can access the same ontology.
- the data service A shown in Figure 3 can access the KGA including ontology EA, ontology EB and ontology EC
- the data service B shown in Figure 4 can access the KGA including ontology EA, ontology EC and ontology ED The KGB. It can be seen that both data service A and data service B can access ontology EA and EC.
- the instance data of the same ontology mapping accessed by different data services can be the same or different.
- the ontology EA accessed by data service A in Figure 3 is mapped to the instance data DA of the IT system
- the ontology EA accessed by data service B in Figure 4 is mapped to the instance data DE of the OT system.
- the mapped instance data are different.
- the method 100 may further include: the data service merges multiple KGs to obtain the merged KG.
- the fused KG may include the target ontology, at least part of the ontologies mentioned above, and connection relationships between the target ontology and at least part of the ontologies.
- a fused KG may include ontologies in multiple KGs and connection relationships between ontologies.
- the data service can integrate the KGA shown in Figure 3 and the KGB shown in Figure 4 to obtain the fused KGC shown in Figure 5.
- KGA includes ontology EA, ontology EB, and ontology EC
- KGB includes ontology EA, ontology EC, and ontology ED.
- the fusion KGC includes ontology EA, ontology EB, ontology EC, and ontology ED, and includes ontology EA, ontology EC, and ontology ED. Connection relationship between ontology EB, ontology EC, and ontology ED.
- data services can be fused based on a service mesh network and accessed through self-describing interfaces of each KG's data services. Specifically, by accessing the self-describing interface of each KG's data service, you can determine whether the data service provided by the data service is the data service you are interested in, for example, whether it is the data service you need. Instead of merging all the KGs accessed by all data services.
- the above technical solution integrates multiple KGs, so that information islands can be eliminated, and users can query data from multiple systems using one data service, realizing higher-dimensional data services and providing higher-value data services.
- the fused KG may not only include ontologies and connections between ontologies, but also include the access information of each ontology in the fused KG, which may be used to indicate the fusion The data service previously used to access the ontology.
- the data service indicated by the access information is referred to as an original data service or a standard data service.
- the data services shown in Figure 3 and Figure 4 are all original data services.
- Original data services can be understood as data services that only access an ontology of a data subject domain.
- the ontologies accessed by an original data service are all based on the company’s operating domain Yes, in the operation domain, there may be topics such as the analysis of event publicity effects, and another ontology for raw data service access is based on the human domain, and the human domain may include topics such as the company's employees.
- the data service for accessing the converged KG is called a converged data service, as shown in FIG. 5 .
- Converged data services can be understood as data services that can access ontologies of multiple data subject domains.
- fused data services can access ontologies in the operation domain and human resources domain in the examples above.
- DSA and DSB can be the access information of ontology EA
- DSA indicates that original data service A can access ontology EA
- DSB indicates that original data service B can access ontology EA
- Ontology ED DSB is the access information of Ontology ED
- DSB indicates that the original data service B can access Ontology ED.
- Each ontology in the fused KG may include at least one new edge, if at least one new edge is associated with other nodes (also referred to as instance nodes) other than the ontology to indicate that the original data service of the ontology can be accessed . If at least two of the original data services can access the same ontology, the ontology in the fusion KG can include multiple new edges; if an ontology is only accessed by one original data service, then the ontology in the fusion KG The ontology includes a new edge.
- both data service A and data service B can access ontology EA and ontology EC
- the ontology EA and ontology EC integrated with KGC each include two new edges, and each new edge is associated with two nodes, where One node is the ontology, and the other node is the source information of the ontology.
- the nodes associated with one of the two new edges are ontology EA and DSA
- DSA is the source information of ontology EA.
- Ontology EB is only accessed by data service A, and ontology ED is only accessed by data service B. Therefore, both ontology EB and ontology ED include only one new edge.
- the data service can output the target data based on the identification of the target ontology and the access information of the target ontology.
- the fused data service can determine the original data service that accesses the target ontology based on the access information of the target ontology, and then the fused data service can control the original data service to output the target data.
- the target ontology is EA in Fig. 5 as an example for illustration.
- the fusion data service C determines that both the data service A and the data service B can access the ontology EA according to the source information of the ontology EA in the fusion KGC. Therefore, the fusion data service C controls the data service A outputs the instance data DA of the ontology EA, and controls the data service B to output the instance data DE of the ontology EA, then the target data is the instance data DA and the instance data DE.
- the fused data service can accurately determine the original data service that accesses the target ontology based on the access information indicating the original data service that accesses the target ontology, and makes the original data service output target data , so that the data queried by users can be more accurate.
- microservice governance may also be performed on multiple original data services, so that multiple original data services can discover each other.
- microservice governance can mainly include: service discovery, load balancing, current limiting, circuit breaker, timeout, retry, and service tracking.
- the network framework of the microservice can be a service mesh network. Due to the adoption of service mesh, multiple data services can form a decentralized data service query network. In this case, even if a certain data service is unavailable, other data services will not be affected, thereby improving the availability of data services.
- Fig. 6 shows a schematic block diagram of a data service 600 according to an embodiment of the present application.
- the data service 600 may execute the data query method 100 in the above embodiment of the present application, and the data service 600 may serve the data in the foregoing method.
- the data service 600 includes:
- a communication unit 610 configured to receive first input information, where the first input information includes an identifier of a target ontology
- the output unit 620 is configured to output target data based on the identification of the target ontology, the target data includes instance data of the target ontology and/or instance data of at least some ontologies that are connected to the target ontology, the target The instance data of the ontology and the at least part of the instance data of the ontology come from a plurality of systems.
- the first input information further includes at least one of the following parameters: attributes of the target ontology; a connection relationship between the target ontology and the first ontology, and The first ontology has a connection relationship with the target ontology, and the at least part of the ontology includes the first ontology; wherein the target data includes instance data of the target ontology and instance data of the first ontology.
- the data service further includes a fusion unit configured to fuse multiple knowledge graphs to obtain a fused knowledge graph, where the fused knowledge graph includes the target ontology, the at least A partial ontology and a connection relationship between the target ontology and the at least partial ontology; wherein, the fusion knowledge graph further includes access information of each ontology in the fusion knowledge graph, and the access information is used to indicate A raw data service for accessing each of the ontologies.
- the output unit 620 may be specifically configured to: determine the target ontology for accessing the target ontology based on the identifier of the target ontology and the access information of the target ontology in the fused knowledge graph.
- the raw data service of ; controls the raw data service used to access the target ontology to output target data.
- the data service includes a self-describing interface, and the self-describing interface is used to indicate a data service type provided by the data service.
- the data service includes a data query interface, and the data query interface is a semantic interface
- the communication unit 610 is specifically configured to receive the first input information through the data query interface
- the output unit 620 is specifically configured to output the target data through the data query interface based on the first input information.
- the output unit 620 is specifically configured to output the target data, the ontology and the instance data based on the identification of the target ontology and the mapping relationship between the ontology and the instance data
- the mapping relationship of data is determined according to the attribute of the ontology and the attribute of the instance data.
- FIG. 7 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present application.
- the electronic device 700 shown in FIG. 7 includes a memory 701 , a processor 702 , a communication interface 703 and a bus 704 .
- the memory 701 , the processor 702 , and the communication interface 703 are connected to each other through a bus 704 .
- the memory 701 may be a read-only memory (read-only memory, ROM), a static storage device and a random access memory (random access memory, RAM).
- the memory 701 may store a program.
- the program stored in the memory 701 is executed by the processor 702, the processor 702 and the communication interface 703 are used to execute each step of the method for data query in the embodiment of the present application.
- the program stored in the memory 701 may be the data service mentioned above.
- the processor 702 may be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application specific integrated circuit (application specific integrated circuit, ASIC), a graphics processing unit (graphics processing unit, GPU) or one or more
- the integrated circuit is used to execute related programs to realize the functions required by the units in the data service of the embodiments of the present application, or to execute the data query method of the embodiments of the present application.
- the processor 702 may also be an integrated circuit chip, which has a signal processing capability.
- each step of the data query method in the embodiment of the present application may be completed by an integrated logic circuit of hardware in the processor 1002 or instructions in the form of software.
- processor 702 can also be general-purpose processor, digital signal processor (digital signal processing, DSP), ASIC, off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic device, discrete gate or transistor logic devices, discrete hardware components.
- DSP digital signal processor
- ASIC off-the-shelf programmable gate array
- FPGA field programmable gate array
- Various methods, steps, and logic block diagrams disclosed in the embodiments of the present application may be implemented or executed.
- a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.
- the steps of the methods disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.
- the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register.
- the storage medium is located in the memory 701, and the processor 1002 reads the information in the memory 701, and combines its hardware to complete the functions required by the units included in the device of the embodiment of the present application, or execute the data query method of the embodiment of the present application.
- the communication interface 703 implements communication between the electronic device 700 and other devices or communication networks by using a transceiver device such as but not limited to a transceiver.
- the electronic device 700 may receive the first input information through the communication interface 703 .
- the bus 704 may include a path for transferring information between various components of the electronic device 700 (eg, memory 701 , processor 702 , communication interface 703 ).
- the electronic device 700 only shows a memory, a processor, and a communication interface, in a specific implementation process, those skilled in the art should understand that the electronic device 700 may also include other devices necessary for normal operation. Meanwhile, according to specific needs, those skilled in the art should understand that the electronic device 700 may also include hardware devices for implementing other additional functions. In addition, those skilled in the art should understand that the electronic device 700 may only include components necessary to implement the embodiment of the present application, and does not necessarily include all the components shown in FIG. 7 .
- the embodiment of the present application also provides a computer-readable storage medium, which stores program code for device execution, where the program code includes instructions for executing the steps in the above data query method.
- the embodiment of the present application also provides a computer program product, the computer program product includes a computer program stored on a computer-readable storage medium, the computer program includes program instructions, and when the program instructions are executed by the computer, the The computer executes the above data query method.
- the above-mentioned computer-readable storage medium may be a transitory computer-readable storage medium, or a non-transitory computer-readable storage medium.
- the disclosed devices and methods may be implemented in other ways.
- the device embodiments described above are only illustrative.
- the division of the units is only a logical function division. In actual implementation, there may be other division methods.
- multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
- the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
- the aspects, implementations, implementations or features of the described embodiments can be used alone or in any combination. Aspects of the described embodiments can be implemented by software, hardware or a combination of hardware and software.
- the described embodiments may also be embodied by a computer-readable medium storing computer-readable code comprising instructions executable by at least one computing device.
- the computer readable medium can be associated with any data storage device that can store data that can be read by a computer system.
- Exemplary computer readable media may include read-only memory, random access memory, compact disc read-only memory (CD-ROM), hard disk drive (HDD), digital Video disc (digital video disc, DVD), magnetic tape, and optical data storage device, etc.
- the computer readable medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed manner.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Mathematical Physics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
Claims (10)
- 一种数据查询的方法,其特征在于,包括:数据服务接收(110)第一输入信息,所述第一输入信息包括目标本体的标识;所述数据服务基于所述目标本体的标识,输出(120)目标数据,所述目标数据包括所述目标本体的实例数据和/或与所述目标本体有连接关系的至少部分本体的实例数据,所述目标本体的实例数据和所述至少部分本体的实例数据来自于多个系统。
- 根据权利要求1所述的方法,其特征在于,所述第一输入信息还包括以下参数中的至少一项:所述目标本体的属性;所述目标本体与第一本体之间的连接关系,所述第一本体与所述目标本体具有连接关系,所述至少部分本体包括所述第一本体;其中,所述目标数据包括所述目标本体的实例数据和所述第一本体的实例数据。
- 根据权利要求1或2所述的方法,其特征在于,所述方法还包括:所述数据服务对多个知识图谱进行融合,得到融合知识图谱,所述融合知识图谱包括所述目标本体、所述至少部分本体以及所述目标本体和所述至少部分本体之间的连接关系;其中,所述融合知识图谱还包括所述融合知识图谱中每个本体的访问信息,所述访问信息用于指示融合前用于访问所述每个本体的原始数据服务。
- 根据权利要求3所述的方法,其特征在于,所述数据服务基于所述目标本体的标识,输出(120)目标数据,包括:所述数据服务基于所述目标本体的标识以及所述融合知识图谱中所述目标本体的访问信息,确定用于访问所述目标本体的原始数据服务;所述数据服务控制用于访问所述目标本体的原始数据服务输出(120)所述目标数据。
- 根据权利要求1至4中任一项所述的方法,其特征在于,所述数据服务包括自描述接口,所述自描述接口用于指示所述数据服务提供的数据服 务类型。
- 根据权利要求1至5中任一项所述的方法,其特征在于,所述数据服务包括数据查询接口,所述数据查询接口为语义化的接口;所述数据服务接收(110)第一输入信息,包括:所述数据服务通过所述数据查询接口,接收(110)所述第一输入信息;所述数据服务基于所述目标本体的标识,输出(120)目标数据,包括:所述数据服务基于所述目标本体的标识,通过所述数据查询接口输出(120)所述目标数据。
- 根据权利要求1至6中任一项所述的方法,其特征在于,所述数据服务基于所述目标本体的标识,输出(120)目标数据,包括:所述数据服务基于所述目标本体的标识,以及基于本体和实例数据的映射关系,输出(120)所述目标数据,所述本体和实例数据的映射关系是根据所述本体的属性和所述实例数据的属性确定的。
- 一种数据服务(600),其特征在于,包括:通信单元(610),用于接收第一输入信息,所述第一输入信息包括目标本体的标识;输出单元(620),用于基于所述目标本体的标识,输出目标数据,所述目标数据包括所述目标本体的实例数据和/或与所述目标本体有连接关系的至少部分本体的实例数据,所述目标本体的实例数据和所述至少部分本体的实例数据来自于多个系统。
- 一种电子设备(700),其特征在于,包括:存储器(701),用于存储程序;处理器(702),用于执行所述存储器(701)存储的程序,当所述存储器(701)存储的程序被执行时,所述处理器(702)用于执行根据权利要求1至7中任一项所述的数据查询的方法。
- 一种计算机可读存储介质,其特征在于,所述计算机可读介质存储用于设备执行的程序代码,所述程序代码包括用于执行根据权利要求1至7中任一项所述的数据查询的方法中的步骤的指令。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202180101715.4A CN117940917A (zh) | 2021-09-30 | 2021-12-07 | 数据查询的方法、数据服务和电子设备 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2021/122407 WO2023050403A1 (zh) | 2021-09-30 | 2021-09-30 | 数据查询的方法、数据服务和计算机可读存储介质 |
CNPCT/CN2021/122407 | 2021-09-30 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023050568A1 true WO2023050568A1 (zh) | 2023-04-06 |
Family
ID=85781174
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2021/122407 WO2023050403A1 (zh) | 2021-09-30 | 2021-09-30 | 数据查询的方法、数据服务和计算机可读存储介质 |
PCT/CN2021/136184 WO2023050568A1 (zh) | 2021-09-30 | 2021-12-07 | 数据查询的方法、数据服务和电子设备 |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2021/122407 WO2023050403A1 (zh) | 2021-09-30 | 2021-09-30 | 数据查询的方法、数据服务和计算机可读存储介质 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN117940917A (zh) |
WO (2) | WO2023050403A1 (zh) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140114949A1 (en) * | 2012-10-22 | 2014-04-24 | Bank Of America Corporation | Knowledge Management System |
CN106959963A (zh) * | 2016-01-12 | 2017-07-18 | 杭州海康威视数字技术股份有限公司 | 一种数据查询方法、装置及系统 |
CN109840259A (zh) * | 2018-12-29 | 2019-06-04 | 北京三快在线科技有限公司 | 数据查询方法、装置、电子设备及可读存储介质 |
CN110020243A (zh) * | 2017-10-31 | 2019-07-16 | 中移物联网有限公司 | 物联网数据的查询方法、装置、物联网服务器和存储介质 |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9262527B2 (en) * | 2011-06-22 | 2016-02-16 | New Jersey Institute Of Technology | Optimized ontology based internet search systems and methods |
CN102682122B (zh) * | 2012-05-15 | 2014-11-26 | 北京科技大学 | 基于本体构建材料科学领域语义数据模型的方法 |
CN107341215B (zh) * | 2017-06-07 | 2020-05-12 | 北京航空航天大学 | 一种基于分布式计算平台的多源垂直知识图谱分类集成查询系统 |
CN109410650B (zh) * | 2018-10-10 | 2020-05-19 | 中国电子科技集团公司第二十八研究所 | 面向全系统信息管理的基于情景与语义的信息聚合方法 |
CN110019844A (zh) * | 2019-02-20 | 2019-07-16 | 众安信息技术服务有限公司 | 一种保险行业知识图谱问答系统构建方法及装置 |
-
2021
- 2021-09-30 WO PCT/CN2021/122407 patent/WO2023050403A1/zh unknown
- 2021-12-07 WO PCT/CN2021/136184 patent/WO2023050568A1/zh active Application Filing
- 2021-12-07 CN CN202180101715.4A patent/CN117940917A/zh active Pending
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140114949A1 (en) * | 2012-10-22 | 2014-04-24 | Bank Of America Corporation | Knowledge Management System |
CN106959963A (zh) * | 2016-01-12 | 2017-07-18 | 杭州海康威视数字技术股份有限公司 | 一种数据查询方法、装置及系统 |
CN110020243A (zh) * | 2017-10-31 | 2019-07-16 | 中移物联网有限公司 | 物联网数据的查询方法、装置、物联网服务器和存储介质 |
CN109840259A (zh) * | 2018-12-29 | 2019-06-04 | 北京三快在线科技有限公司 | 数据查询方法、装置、电子设备及可读存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CN117940917A (zh) | 2024-04-26 |
WO2023050403A1 (zh) | 2023-04-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10033597B2 (en) | Type-to-type analysis for cloud computing technical components with translation scripts | |
US11436361B2 (en) | Computer-implemented methods, systems comprising computer-readable media, and electronic devices for secure multi-datasource query job status notification | |
US20100125584A1 (en) | Intelligent event query publish and subscribe system | |
JP2017503421A (ja) | ネットワーク機能仮想化nfv障害管理の装置、デバイス、および方法 | |
US20190208404A1 (en) | Method and arrangement for on-boarding network service descriptions from various sources in a common service catalogue of NFV orchestration platform | |
US20210075693A1 (en) | Enterprise control plane for data streaming service | |
CN112882900B (zh) | 一种记录业务数据变更日志的方法及设备 | |
CN111858615A (zh) | 数据库表生成方法、系统、计算机系统和可读存储介质 | |
US20090228506A1 (en) | Information processing apparatus | |
WO2023050568A1 (zh) | 数据查询的方法、数据服务和电子设备 | |
CN113312242B (zh) | 接口信息管理方法、装置、设备及存储介质 | |
CN113486099A (zh) | 一种内存计算服务框架及实现系统 | |
WO2023225785A1 (zh) | 一种汽车开放系统架构模型构建方法及装置 | |
WO2024034057A1 (ja) | ネットワーク管理装置、ネットワーク管理方法及びプログラム | |
Rönnberg et al. | Data ingestion architecture for telecom applications | |
TW202123001A (zh) | 劃分服務的解耦系統及其方法 | |
CN113504973A (zh) | 业务数据并发处理方法、装置及系统 | |
CN116719865A (zh) | 业务数据的融合方法、装置、设备、存储介质及程序产品 | |
CN117914891A (zh) | 用于城市运管服平台的多源异构数据共享交换系统及方法 | |
CN116346643A (zh) | 信息处理方法、装置、设备及存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 21959128 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202180101715.4 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2021959128 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2021959128 Country of ref document: EP Effective date: 20240328 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |