CN114896286A

CN114896286A - Data resource query method and device

Info

Publication number: CN114896286A
Application number: CN202210615432.8A
Authority: CN
Inventors: 王海龙
Original assignee: Hangzhou Dt Dream Technology Co Ltd
Current assignee: Hangzhou Dt Dream Technology Co Ltd
Priority date: 2022-05-31
Filing date: 2022-05-31
Publication date: 2022-08-12

Abstract

The application provides a method and a device for querying data resources, which are applied to a service system, wherein the method comprises the following steps: responding to a query request aiming at a target data resource by a query party, and determining a target data resource entity corresponding to the target data resource; determining a target physical data table corresponding to the target data resource entity according to a mapping relation between the stored data resource entity and a physical data table in a data source; and acquiring the target data resource recorded in the target physical data table, and returning the target data resource to the inquiring party.

Description

Data resource query method and device

Technical Field

The present application relates to the field of data resource query, and in particular, to a method, an apparatus, a device, and a computer-readable storage medium for querying data resources.

Background

The data resources refer to data per se, namely various data records accumulated in the operation of the enterprise, such as client records, sales records, personnel records, purchase records, financial data, inventory data and the like. Through the butt joint between the service system and the data source, a user can access the data resources stored in the data source based on the service system.

In the related art, data resources may come from different data sources, or originally adopted data sources may also be changed, so that for each data source, service codes for completing the interfacing need to be redeveloped in the service system.

Disclosure of Invention

In order to overcome the problems in the related art, the present application provides a data resource query method, apparatus, device and computer readable storage medium, which can solve the above problems.

According to a first aspect of an embodiment of the present application, a data resource query method is provided, where the method includes:

responding to a query request aiming at a target data resource by a query party, and determining a target data resource entity corresponding to the target data resource;

determining a target physical data table corresponding to the target data resource entity according to a mapping relation between the stored data resource entity and a physical data table in a data source;

and acquiring the target data resource recorded in the target physical data table, and returning the target data resource to the inquiring party.

According to a second aspect of the embodiments of the present application, there is provided a data resource query apparatus, including:

the query unit is used for responding to a query request of a query party for a target data resource and determining a target data resource entity corresponding to the target data resource;

the mapping unit is used for determining a target physical data table corresponding to the target data resource entity according to the mapping relation between the stored data resource entity and the physical data table in the data source;

and the returning unit is used for acquiring the target data resource recorded in the target physical data table and returning the target data resource to the inquiring party.

According to a third aspect of embodiments of the present application, there is provided an electronic apparatus, including: a processor, a memory;

the memory for storing a computer program;

the processor is configured to execute the data resource query method according to the first aspect by calling the computer program.

According to a fourth aspect of embodiments of the present application, there is provided a computer-readable storage medium on which a computer program is stored, which when executed by a processor, implements the data resource query method according to the first aspect.

The technical scheme provided by the embodiment of the application can have the following beneficial effects:

in the embodiment of the application, by establishing the data resource entity, a mapping relation is established between the data resource entity and the physical data table in the database, and it is ensured that the service code in the service system is used for butt access to the data resource entity, so that even if the physical data table corresponding to the data resource entity changes due to data source change, the butt access between the service code in the service system and the data resource entity is not affected, and the access to the changed physical data table can be smoothly completed only by updating the mapping relation corresponding to the data resource entity and changing the original physical data table into the changed physical data table without modifying the service code of the service system, thereby greatly reducing the extra workload brought by the data source change.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this application, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.

FIG. 1 is an architectural diagram of a data resource system shown in accordance with an exemplary embodiment of the present application.

FIG. 2 is a flow chart illustrating a data resource query method according to an exemplary embodiment of the present application.

FIG. 3 is a multi-party interaction diagram illustrating a data resource querying method according to an exemplary embodiment of the present application.

Fig. 4 is a schematic structural diagram of an electronic device in which a data query device according to an exemplary embodiment is located.

FIG. 5 is a block diagram of a data query device shown in the present application according to an exemplary embodiment.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

Next, examples of the present application will be described in detail.

FIG. 1 is a network architecture diagram of a data resource query system, shown herein in accordance with an exemplary embodiment. As shown in fig. 1, the data resource query system of the present application may include user-side devices 11-12, a service system 13, data sources 14-16, and the like.

The user-side devices 11-12 may be a mobile phone, a desktop computer, a tablet device, a notebook computer or a palmtop computer (PDAs), and a wearable device (such as smart glasses, VR glasses, etc.), which is not limited in the present application. Based on the technical architecture adopted between the user-side devices 11-12 and the service system 13, there may be some differences, such as: when the client is based on the C/S architecture, a client corresponding to the service system 13 (for example, a client of a service application running on the service system 13) may be installed and run on the user-side device 11-12, and when the client is based on the B/S architecture, a browser is installed and run on the user-side device 11-12; accordingly, the user can implement data interaction with the service system 13 through the above-mentioned client or browser running on the user-side device 11-12. Specifically, when the user is the inquiring party, the user-side device 11-12 may send an inquiry request to the service system 13 according to the user operation, and provide the target data resource returned by the service system 13 to the user, for example, display the target data resource on a display screen of the user-side device 11-12.

The service system 13 may be an independent host or a host cluster, or may be a virtual server carried by the independent host or the host cluster. The service system 13 may run a service end with a service application, and is configured to perform data interaction with the user-side devices 11-12 and the data sources 14-16. Specifically, the service system 13 may query the target data resources maintained by the data sources 14-16 according to the query request sent by the user-side device 11-12, and provide the target data resources returned by the data sources 14-16 to the user-side device 11-12.

The data sources 14-16 may be databases. The types of data sources 14-16 may include: mysql, oracle, Hbase, Gbase, neo4j, ES, etc., which the present application does not limit. The service system 13 may interface one or more data sources, and specifically, an administrator of the service system 13 may manage the data sources according to actual service requirements. The data sources 14-16 are used for maintaining, such as storing and managing, a physical data table containing data resources, and performing data interaction with the business system 13 to provide the target data resources that the business system 13 needs to query. In particular, the data sources 14-16 may return the target data resource to the business system 13 based on a query action of the business system 13.

In the related art, the service code of the service system 13 is used to directly search the corresponding physical data table during execution, i.e. the service system 13 is directly interfaced with the data sources 14-16, so that there is a coupling relationship between the service system 13 and the data sources 14-16 or the physical data tables maintained by the data sources 14-16. Therefore, when the data source 14-16 is changed, for example, the change may be deletion, addition or change of a physical data table in the data source 14-16, or addition of a new data source or deletion of an original data source, etc., the original service code may not find the corresponding physical data table after being executed, and thus the target data resource may not be searched. Since the coupling between the business system 13 and the physical data tables in the data sources 14-16 is based on the business code deployed on the business system 13, new business code needs to be developed to be able to adapt to the data source changes.

In view of the above problems, the embodiments of the present application provide a data resource query scheme, which can achieve successful query of a target data resource without re-developing a service code when a data source or a physical mapping table in the data source changes, greatly reduce development of the service code, and achieve an effect of reducing research and development costs.

FIG. 2 is a flowchart of a data resource query method according to an exemplary embodiment. As shown in fig. 2, the method is applied to a business system (which may be, for example, business system 13 shown in fig. 1). The method may comprise the steps of:

s101: and responding to a query request aiming at the target data resource by a query party, and determining a target data resource entity corresponding to the target data resource.

In an embodiment, the querying party may refer to an object having a query requirement, for example, the object may be a user, or may be an application, or an AI program, which is not limited in this application. The inquiring party can complete the inquiring process through the user side devices 11-12 shown in fig. 1. The data resource that the inquiring party needs to inquire is a target data resource, and the type of the target data resource is often related to an actual application scenario, for example, the target data resource may be a client record, a sales record, a personnel record, a purchase record, financial data, inventory data, and the like, which is not limited in this application.

In an embodiment, the service system may provide a query page to the querying party, where the page includes a page element corresponding to a preset data resource, for example, the page element may be a virtual module displayed in the page, and description information of the data resource corresponding to the page element may be displayed on or near the page element, for example, in a specific scenario, the query page may include a virtual module displaying characters such as "customer record", "sales record", and "personnel record", so that the querying party may select the page element corresponding to the target data resource from all the page elements according to the characters, and then trigger the page element by clicking a mouse, touching, and the like. And the query request is generated by triggering the page element corresponding to the target data resource by the query party.

A physical data table is maintained in the data source and used for recording corresponding data resources. The data resource entity may be a data object established locally in the business system, or may be a data object established on a third-party device outside the business system or the data source. The data object itself does not contain data resources, but has a mapping relation with the data resources.

For example, in some embodiments, when a user of a business system needs to display a data resource related to an "business situation" on a user interface, a business configurator needs to add data sources, such as a data source a and a data source B, storing corresponding data resources, and then create a data resource entity corresponding to the data source A, B, for example, establish a data resource entity name corresponding to the data source a as "administrative permission", and establish a data resource entity name corresponding to the data source B as "external investment", where both the two data resource entities are data resource entities corresponding to related data resources required by the "business situation" module. Then, the service configurator needs to establish a mapping relationship between the data resource entity and the data source, for example, a mapping relationship between "administrative permission" and the data source a, and a mapping relationship between "external investment" and the data source B. After the business system determines the data resource entity, the target data source can be determined based on the created mapping relation, and then the target data resource can be obtained from the target data source.

It should be explained that the configuring party of the business system refers to a person who can configure the business system. For example, the configuring party may be an administrator of the service system, or may be a user who has configuration authority and uses the service system. The user of the service system refers to the user using the service system. For example, the user may be a user of the business system, or may be an administrator of the business system.

In some embodiments, the method of determining a target data resource entity corresponding to a target data resource may include the following steps a1-a 2:

step A1: and acquiring configuration information of the target data resource according to the query request, wherein the configuration information comprises a data resource entity ID.

The configuration information refers to some information created by a service system configurator and required for acquiring the target data resource.

In some embodiments, the configuration information may be generated in advance and stored in a service system, and the service system may obtain different configuration information for different target data resources according to the query request.

In some embodiments, a configurator of the business system can perform custom configuration on configuration information of the data resources on a page provided by the business system according to requirements.

For example, in a scenario where a user interface needs to display data resources related to an "operation status", the need is to acquire related data resources stored in different data sources for the "operation status" resources, and assemble a generated page according to a preset format for output. In this scenario, the user may configure information for user interface display as desired, such as: module name, column name, text color, external link, page display style, etc., and may also be configured with data resource entity IDs, such as the IDs of the data resource entities that are "administrative permits" and "investments in the outside" in this scenario. It should be noted that the configuration information may not only include the data resource entity ID, but also include other information such as "module content", "module type", "data list", "table name", and the like, and the configuration information may be used to obtain data or front-end page display. The module content is the name of a page element corresponding to the preset data resource in the front-end page display. The module type is a self-defined configuration template type provided for the inquiring party by the service application, and the inquiring party can carry out self-defined configuration to a certain extent on the basis of the template. The data list is a preset data resource corresponding to the page element in the front-end page display. The table name is the name of the data list. These aforementioned messages are used as front-end page presentations. The data resource entity ID is used to retrieve the data.

It should be noted that the configuration information may be stored in the service application, or may be stored in other suitable places, such as a configuration center, for example, a data resource entity.

Step A2: and determining a target data resource entity corresponding to the target data resource according to the data resource entity ID.

The data resource entity ID in the configuration information may correspond to the target data resource entity one to one. Based on the data resource entity ID, a target data resource entity may be determined. The data resource entity ID is only an exemplary configuration information name, and other configuration information with similar functions and features should also be within the scope of the present application.

The data resource entity determined by the service application based on the service code in the application is not determined by the physical data table in the data source based on the service code as in the related art. This allows the business code to be changed when a change occurs to the data source.

S102: and determining a target physical data table corresponding to the target data resource entity according to the mapping relation between the stored data resource entity and the physical data table in the data source.

The physical data table in the embodiment of the present application is a carrier stored in the data source for recording the data resource, and the form, format, and data storage manner of the physical data table may be different depending on the type of the data source, and this difference has no influence on the present application. The physical data table is specifically used for establishing a mapping relation with the data resource entity in advance, determining the physical data table stored by the target data resource when the business system performs an inquiry action on the data source, and returning the target data resource stored in the physical data table to the business system.

The mapping relationship mentioned in the present application is actually established between the data resource entity ID and the information on the physical data table, and the corresponding information on the physical data table can be found by means of the mapping relationship. The information on the physical data table includes information indicating the physical data table, such as a header of the physical data table, index information, and the like. And obtaining the mapping relation of the data resource entity ID according to the data resource entity ID, finding a target physical data table according to the mapping relation, and searching the required target data resource according to the physical data table.

When the business application receives the query request and determines the target data resource entity corresponding to the target data, the mapping relation between the target data resource entity and the target physical data table in the data source can be determined. Furthermore, a target physical data table corresponding to the target data can be determined through the mapping relation.

Therefore, when the data source is changed, only a new mapping relation needs to be established between the data resource entity and the changed data source or the physical data table, and modification of the codes of the business application is avoided. Therefore, the technical effects of saving workload and avoiding developing new service codes are achieved.

In some embodiments, when the data source is changed, the service configurator may update the mapping relationship between the stored data resource entity and the physical data table in the data source, so that the updated target physical data table corresponding to the target data resource may be determined through the updated mapping relationship, and a user may obtain the target data resource according to the determined target physical data table.

Therefore, under the condition that the data source is changed, the mapping relation is adjusted according to the change condition to ensure that a user can normally acquire the data without modifying the codes of the business application, and the workload is saved. In addition, a user does not need to know data sources, does not need to deeply know services, is friendly to the user, and improves the experience of the user.

In some embodiments, the condition that the data source is changed includes that the data source corresponding to the data resource entity or a physical data table in the data source is added, deleted or replaced. For example, the physical data table in the data source corresponding to the original "administrative permission" data entity is added, deleted or replaced.

Therefore, when the data resources are updated, the service system can add, delete or replace the data source or the physical data table in the data source in real time by the configuration party of the service system, so that the data resources are updated in time, and the experience of poor use party caused by mismatching of the data resources and the latest requirements of the use party or the fact that the data are not updated after laggard is avoided.

S103: and acquiring the target data resource recorded in the target physical data table, and returning the target data resource to the inquiring party.

The present application provides a practical method for obtaining the target data resource.

When the service system acquires the configuration information, the configuration information may include data resource description information predefined by the inquiring party, in addition to the data resource entity ID.

If the configuration information does not have the data resource description information predefined by the inquiring party, the physical data table is found by using the mapping relation through the data resource entity ID, and when the target data resource in the physical data table is obtained, all or default target data resources in the physical data table are obtained. And all or default acquired target data resources are returned to the service system, and the service system returns the acquired target data resources to the user side equipment.

And if the configuration information also contains data resource description information predefined by the inquiring party, finding out the physical data table by using the mapping relation through the data resource entity ID, and acquiring the target data resource matched with the data resource description information predefined by the inquiring party in the physical data table when acquiring the target data resource in the physical data table. And returning the acquired matched target data resource to the service system, and returning the acquired matched target data resource to the user side equipment by the service system.

Therefore, the data resources stored in the physical data table can be screened and matched to a certain extent by virtue of the data resource description information predefined by the inquiring party, so that the inquiring party can obtain the required specific data resources by self-defining. The function that users can conveniently acquire data resources with different requirements in different industries of different regions is realized.

After the target data resource is obtained, when the data resource is returned to the user side equipment, the method is concretely implemented, and the function of custom configuration of the front-end display page is realized.

When the service system acquires the configuration information, the configuration information may include front-end page display information predefined by the inquiring party, in addition to the data resource entity ID.

If no front-end page display information exists, the service system directly returns the target data resource to the user side equipment after acquiring the target data resource. At this time, the front-end page display information is the basic style originally set by the service system.

And if the user has the requirement of self-defining the front-end page display and the configuration information contains the front-end page display information predefined by the inquiring party, the business system assembles the target data resource according to the front-end page display information after acquiring the target data resource and returns the target data resource assembled with the front-end page display information to the user-side equipment. The user-defined function of the display page is realized.

The front-end page display information may include: text, color, width, table style, module name, etc. When the service system configures the data resource based on the front-end page display information, the user-defined configuration of specific details of the front-end page information such as font type, font color, font size, form presentation style, name of the data resource when being presented and the like can be performed on the data resource when being displayed.

In order to better understand the technical solution disclosed in the present application, the following description is made with reference to a specific embodiment. It should be noted that the embodiment is only exemplary and explanatory and does not limit the present application.

The data query method of the embodiment is applied to an archive management scene of an enterprise, and the archive management scene includes an interaction process of user-side equipment, a service system, a management center and a data source, which can be understood by combining with the multi-party interaction diagram of fig. 3. The management center stores the data resource entity constructed by the configurator, and the management center can be a third-party device outside the service system or the data source. The data resource entities are data objects established in the management center.

Before the method is used, a configurator of a service system needs to add a data source, a physical data table is maintained in the data source and used for recording corresponding data resources, and the configurator also needs to construct a data resource entity of a management center and establish a mapping relation between the data resource entity and the physical data table in the data source.

The virtual module is shown on the front-end page, and the user can send a query request to the service application by triggering the virtual module.

Specifically, a virtual module to be queried may include a plurality of data resource entities, for example, a "business situation" virtual module to be queried by a user may include 2 data resource entities, namely "administrative approval" and "investment in outside". The present embodiment is not limited to the module construction mode.

The configurator may configure the "business situation" virtual module and the corresponding information of the "administrative permission" and "external investment" of the data resource entity in advance according to the requirements of the user on the data resource, for example, the data resource of the "business situation" module needs to be queried, and/or the requirements on the front-end page display style, for example, the requirements on the module name, the module type, the column name, the character color, the external link, the page display style, and the like, which is called configuration information. The configuration information can also comprise information for front-end page display and information for acquiring data, and is configured by a user side in a self-defined way. Such as module name, module type, column name, text color, external link, page display style, etc. for front-end page presentation, such as data resource entity ID for data acquisition, data resource description information. The module name is, for example, "basic information", "stock right information", "business condition", and the like, which are displayed on the interface. The module types may include "basic type", "custom" and the like.

The following are steps of the specific data query.

S201: the service system provides a query page to the user side equipment, and the page comprises page elements corresponding to the preset data resources.

The business application provides a query page for user side equipment of a certain enterprise, and the query page relates to the display of the virtual module, such as basic information, operation conditions, stock right information, industrial and commercial information, hazardous chemical substance information and the like.

S202: the user side equipment sends out a query request to the service system.

For example, the user sends a query request for the "business situation" data resource to the business application by triggering the "business situation" module.

S203: the service system queries the configuration information.

The service application first queries the configuration information corresponding to the "business situation", which may include a stored data resource entity ID, for acquiring the data resource. The data resource entity ID is here the ID of the data resource entity of "administrative approval" and "investments in the outside" described above. Information for front-end page presentation and data asset description information may also be included.

S204: and the service system determines the data resource entity according to the ID of the data resource entity.

In this embodiment, the data resource entities of "administrative approval" and "invested-in" are determined by the data resource entity IDs of "administrative approval" and "invested-in".

S205: and the management center returns the mapping relation between the data resource entity and the physical data table in the data source to the service system.

In this embodiment, the management center is located on the device of the business application. And finding the mapping relation of the physical data table in the corresponding data source through the determined target data resource entity, and returning the mapping relation to the service application.

In another embodiment, the management center may be located on two different devices outside the service application, which is not limited in this application.

S206: and the service system determines a physical data table in the data source based on the acquired mapping relation.

In this embodiment, the physical data table referred to is a physical data table storing target data resources of "administrative approval" and "investment in the outside world".

S207: and the service system acquires the matched target data resources in the physical data table according to the configuration information.

In this embodiment, according to the specific content of the data resource description information in the configuration information, the data resources in the physical data table are matched, and the matched target data resources are returned to the service system.

S208: and the service system assembles the target data resource according to the configuration information.

In this embodiment, after the target data resource is obtained, the target data resource may be assembled with information for front-end page display in the configuration information.

S209: and the service system returns the assembled target data resource to the user side equipment.

In this embodiment, the assembled matched target data resources may be rendered into a table or list of pages and presented to the user.

Corresponding to the embodiment of the data query method, the application also provides an embodiment of a data query device.

Referring to fig. 4, fig. 4 is a schematic structural diagram of an electronic device where a data query device is located in an embodiment of the present application. At the hardware level, the apparatus includes a processor 410, a network interface 420, a memory 430, and a non-volatile memory 440, although it may also include hardware required for other services. One or more embodiments of the present application may be implemented in software, such as by processor 410 reading corresponding computer programs from non-volatile memory 440 into memory 430 and then running. Of course, besides software implementation, other implementations are not excluded from one or more embodiments of the present application, such as logic devices or a combination of software and hardware, and so on, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.

Referring to fig. 5, fig. 5 is a block diagram of a data query device according to an embodiment of the present application. The page access device can be applied to the electronic device shown in fig. 4 to implement the technical solution of the present application. The data query system is applied to a service system, and the configuration information and the mapping relationship are stored in cache data of the service system, and may include:

a querying unit 510, configured to determine, in response to a query request for a target data resource by a querying party, a target data resource entity corresponding to the target data resource;

a mapping unit 520, configured to determine, according to a mapping relationship between a stored data resource entity and a physical data table in a data source, a target physical data table corresponding to the target data resource entity;

a returning unit 530, configured to obtain the target data resource recorded in the target physical data table, and return the target data resource to the querying party.

Optionally, the method further includes:

and the updating mapping unit 540 is used for updating the mapping relation between the stored data resource entities and the physical data tables in the data source when the data source is changed.

Optionally, the case that the data source is changed includes:

the addition, deletion, or replacement of a data source or a physical data table in the data source occurs.

Optionally, the querying unit 510 is specifically configured to:

acquiring configuration information of the target data resource according to the query request, wherein the configuration information comprises a data resource entity ID;

and determining a target data resource entity corresponding to the target data resource according to the data resource entity ID.

Optionally, the configuration information further includes:

data resource description information predefined by the querier; optionally, the returning unit 530 is specifically configured to:

and acquiring the data resource which is recorded in the target physical data table and matched with the data resource description information as the target data resource.

Optionally, the configuration information further includes:

front-end page presentation information predefined by the inquiring party; optionally, the returning unit 530 is specifically configured to:

and performing data assembly on the target data resource according to the front-end page display information, and returning the obtained assembled target data resource to the inquiring party.

Optionally, the querying unit 510 is specifically configured to:

providing a query page to the query party, wherein the page comprises page elements corresponding to preset data resources;

and the query request is generated by triggering the page element corresponding to the target data resource by the query party.

In this embodiment, the querying unit may be configured to:

responding to a query request of the query party for a target data resource, acquiring configuration information based on the query request, and determining a data resource entity ID in the configuration information to determine a target data resource entity corresponding to the target data resource.

The mapping unit may specifically be configured to:

and determining a target physical data table stored in the data source corresponding to the target data resource entity according to the mapping relation between the stored data resource entity and the physical data table in the data source and the determined data resource entity.

The return unit may specifically be configured to:

and acquiring a target data resource matched with the configuration information in the physical data table, returning the target data resource to the service system, assembling the target data resource by the service system according to the configuration information, and returning the assembled target data resource to the inquiring party.

The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.

For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to some descriptions of the method embodiments for relevant indications. The above-described embodiments of the apparatus are only illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.

In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, and those skilled in the art will also appreciate that instead of implementing the controller in purely computer readable program code, the method steps may well be programmed logically to cause the controller to perform the same functions in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a server system. Of course, this application does not exclude that with future developments in computer technology, the computer implementing the functionality of the above described embodiments may be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device or a combination of any of these devices.

Although one or more embodiments of the present application provide method operation steps as described in the embodiments or flowcharts, more or fewer operation steps may be included based on conventional or non-inventive means. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual apparatus or end product executes, it may execute sequentially or in parallel (e.g., parallel processors or multi-threaded environments, or even distributed data processing environments) according to the method shown in the embodiment or the figures. The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, the presence of additional identical or equivalent elements in a process, method, article, or apparatus that comprises the recited elements is not excluded. For example, if the terms first, second, etc. are used to denote names, they do not denote any particular order.

For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, when implementing one or more of the present applications, the functions of each module may be implemented in one or more software and/or hardware, or a module implementing the same function may be implemented by a combination of multiple sub-modules or sub-units, etc. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage, graphene storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

One skilled in the art will recognize that one or more embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

One or more embodiments of the present application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present application are described in a progressive manner, and the same and similar parts among the embodiments can be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment. In the description of the present application, reference to the description of the terms "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. In this application, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this application can be combined and combined by those skilled in the art without contradiction.

The foregoing is merely exemplary of one or more embodiments of the present application and is not intended to limit the scope of the present application. Various modifications and alterations to one or more embodiments of the present application will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims.

Claims

1. A data resource query method is characterized by comprising the following steps:

2. The method of claim 1, further comprising:

and updating the mapping relation between the stored data resource entity and a physical data table in the data source under the condition that the data source is changed.

3. The method of claim 2, wherein the occurrence of a change in the data source comprises:

4. The method according to claim 1, wherein the determining a target data resource entity corresponding to the target data resource comprises:

5. The method according to claim 4, wherein the configuration information further includes data resource description information predefined by the inquiring party; the acquiring the target data resource recorded in the target physical data table includes:

6. The method of claim 4, wherein the configuration information further comprises front-end page presentation information predefined by the querying party; the returning the target data resource to the inquiring party includes:

7. The method of claim 1, further comprising:

providing a query page to the query party, wherein the query page comprises page elements corresponding to preset data resources;

8. A data resource query apparatus, comprising:

9. An electronic device, comprising: a processor, a memory;

the memory for storing a computer program;

the processor, configured to execute the data resource query method according to any one of claims 1 to 7 by calling the computer program.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the data resource querying method according to any one of claims 1 to 7.