CN114661762A

CN114661762A - Query method and device for embedded database, storage medium and equipment

Info

Publication number: CN114661762A
Application number: CN202210260229.3A
Authority: CN
Inventors: 唐俊; 冉君尧; 陈磊
Original assignee: Asiainfo Technologies (chengdu) Inc
Current assignee: Asiainfo Technologies (chengdu) Inc
Priority date: 2022-03-16
Filing date: 2022-03-16
Publication date: 2022-06-24

Abstract

The invention discloses a query method, a query device, a storage medium and equipment of an embedded database, relates to the technical field of embedded databases, and is used for reducing the development cost of a client for accessing the embedded database. The method comprises the following steps: and after receiving the protocol format request sent by the client, the server sends the access protocol of the embedded database to the client. Subsequently, the server receives a query request for querying the target data, which is generated based on the access protocol, sent by the client. Then, the server side judges whether target data exist in the embedded database or not according to the query request; and sending the target data to the client under the condition that the embedded database is stored in the target data.

Description

Query method and device for embedded database, storage medium and equipment

Technical Field

The invention relates to the technical field of embedded databases, in particular to a query method, a query device, a storage medium and equipment of an embedded database.

Background

The embedded database is an efficient and compact database and is commonly applied to various electronic devices (such as smart phones, vehicle navigation devices, set top boxes and the like). The embedded database may be embedded not only in the software of the electronic device, but also in the hardware structure of the electronic device. Currently, all data operations in the embedded database by the application are performed through an Application Program Interface (API).

In the above implementation manner, in order to implement access of the application program to the embedded database, when a developer develops the application program, a large amount of code needs to be written to implement access of the application program to the embedded database. Resulting in higher development costs for accessing the embedded database.

Disclosure of Invention

The invention provides a query method, a query device, a storage medium and equipment of an embedded database, which are used for reducing the development cost of accessing the embedded database by a client.

In order to achieve the purpose, the invention adopts the following technical scheme:

in a first aspect, a query method for an embedded database is provided, which is applied to a server including the embedded database, and the method includes: responding to a protocol format request sent by a client, and sending an access protocol of an embedded database to the client; receiving a query request sent by a client; the query request is generated based on an access protocol; the query request is used for querying target data in the embedded database; responding to the query request, and judging whether target data exist in the embedded database; and sending the target data to the client under the condition that the embedded database is stored in the target data.

The invention provides a query method of an embedded database, which is applied to a server side comprising the embedded database. The server receives a query request sent by the client, wherein the query request is generated based on an access protocol. And responding to the query request, and sending the target data to the client by the server side under the condition that the embedded database stores the target data. Therefore, the client only needs to acquire the access protocol of the embedded database and then sends the query request based on the access protocol, and the embedded database does not need to be accessed through a plurality of codes input by each client, so that the development cost of accessing the embedded database by the client is reduced.

In a possible implementation manner, the "determining whether target data exists in the embedded database in response to the query request" includes: responding to the query request, and judging whether the query request comprises a preset identifier; the preset identifier is used for indicating that target data is inquired from a preset data set included in the embedded database; the preset data set is obtained according to at least one Pattern file; and under the condition that the query request comprises the preset identification, judging whether target data exist in the preset data set or not. Therefore, the file for storing the data in the embedded database is a Pattern file, so that the data only needs to be stored in the Pattern file and the dynamic library which encapsulates the query method without depending on database service. Therefore, the embedded database only needs to put the Pattern file and the dynamic library which encapsulates the query method into the electronic equipment, and does not need to migrate the data in the database.

In a possible implementation manner, the method further includes: under the condition that the Pattern file to be updated exists, generating a standby data set based on the Pattern file to be updated; after the spare data set is generated, the preset data set is replaced based on the spare data set. Therefore, according to the technical scheme provided by the invention, under the condition that the data is updated, the preset data set can still be used for inquiring the data in the process of generating the standby data set by the Pattern file to be updated. Namely, when the data is updated, the data can still be inquired, and the data inquiry service does not need to be stopped. After the data updating is completed and the standby data set is generated, the standby data set is determined to be the preset data set, and therefore the non-perception updating is achieved.

In a possible implementation manner, the "determining whether target data exists in the embedded database in response to the query request" includes: and responding to the query request based on the single thread, and judging whether the target data exists in the embedded database. Therefore, the technical scheme of the invention adopts a single thread to process the requirements of a plurality of clients and obtains the target data requested by the plurality of clients through a multiplexing technology. Due to the adoption of the single-thread technology, only one Pattern file needs to be loaded into the memory, and the occupation of memory resources is reduced.

In a second aspect, a query method for an embedded database is provided, which is applied to a client, and the method includes: generating a format protocol request, and sending the protocol format request to a server side comprising an embedded database; the protocol format request is used for requesting an access protocol of the embedded database; receiving an access protocol sent by a server; generating a query request based on an access protocol, and sending the query request to a server; the query request is used for requesting to query the target data in the embedded database; and receiving target data sent by the server.

In a third aspect, an apparatus for querying an embedded database is provided, which is applied to a server including the embedded database, and includes: a transmitting unit, a receiving unit and a judging unit; the sending unit is used for responding to a protocol format request sent by the client and sending an access protocol of the embedded database to the client; the receiving unit is used for receiving the query request sent by the client after the sending unit sends the access protocol to the client; the query request is generated based on an access protocol; the query request is used for querying target data in the embedded database; the judging unit is used for responding to the query request received by the receiving unit and judging whether the embedded database has target data or not; and the sending unit is also used for sending the target data to the client under the condition that the embedded database stores the target data.

In a possible implementation manner, the determining unit is specifically configured to: responding to the query request, and judging whether the query request comprises a preset identifier; the preset identification is used for indicating that target data are inquired from a preset data set included in the embedded database; the preset data set is obtained according to at least one Pattern file; and under the condition that the query request comprises the preset identification, judging whether target data exist in the preset data set or not.

In a possible implementation manner, the querying device further includes: a generation unit and a replacement unit; the generating unit is used for generating a standby data set based on the Pattern file to be updated under the condition that the Pattern file to be updated exists; and a replacement unit for replacing the preset data set based on the spare data set after the spare data set is generated.

In a possible implementation manner, the determining unit is specifically configured to determine whether target data exists in the embedded database based on a single thread response to the query request.

In a fourth aspect, an apparatus for querying an embedded database is provided, which is applied to a client, and includes: a generating unit, a transmitting unit and a receiving unit; a generating unit for generating a format protocol request; the protocol format request is used for requesting an access protocol of the embedded database; the sending unit is used for sending the protocol format request generated by the generating unit to the server; the server comprises an embedded database; the receiving unit is used for receiving the access protocol of the embedded database sent by the server after the sending unit sends the protocol format request to the server; the generating unit is also used for generating a query request based on the access protocol received by the receiving unit; the query request is used for querying target data in the embedded database; the sending unit is also used for sending the query request generated by the generating unit to the server; and the receiving unit is also used for receiving the target data sent by the server.

In a fifth aspect, a computer-readable storage medium is provided, in which instructions are stored, and when executed, the method for querying an embedded database according to the first aspect or the second aspect is implemented.

In a sixth aspect, a server is characterized by comprising: a processor, a memory, and a communication interface; the communication interface is used for communication between the communication device and other equipment or networks; the memory is used for storing one or more programs, the one or more programs include computer-executable instructions, and when the server runs, the processor executes the computer-executable instructions stored in the memory, so that the electronic device executes the query method of the embedded database according to the first aspect.

In a seventh aspect, a client is provided, including: a processor, a memory, and a communication interface; the communication interface is used for communication between the communication device and other equipment or networks; the memory is used for storing one or more programs, and the one or more programs comprise computer executable instructions which, when the client is run, the processor executes the computer executable instructions stored by the memory to cause the electronic device to execute the query method of the embedded database according to the second aspect.

Drawings

Fig. 1 is a schematic structural diagram of a query system of an embedded database according to an embodiment of the present invention;

fig. 2 is a flowchart illustrating a method for querying an embedded database according to an embodiment of the present invention;

fig. 3 is a second flowchart illustrating a query method for an embedded database according to an embodiment of the present invention;

fig. 4 is a third schematic flowchart of a query method for an embedded database according to an embodiment of the present invention;

fig. 5 is a fourth schematic flowchart of a query method for an embedded database according to an embodiment of the present invention;

fig. 6 is a fifth flowchart illustrating a query method of an embedded database according to an embodiment of the present invention;

fig. 7 is a sixth schematic flowchart of a query method for an embedded database according to an embodiment of the present invention;

fig. 8 is a schematic structural diagram of an embedded database query device according to an embodiment of the present invention;

fig. 9 is a schematic structural diagram of another query device for an embedded database according to an embodiment of the present invention;

fig. 10 is a schematic structural diagram of a server according to an embodiment of the present invention;

fig. 11 is a second schematic structural diagram of a server according to an embodiment of the present invention.

Detailed Description

In order to facilitate clear description of technical solutions of the embodiments of the present invention, in the embodiments of the present invention, terms such as "first" and "second" are used to distinguish the same items or similar items having substantially the same functions and actions. For example, the first filtering policy and the second filtering policy are only for distinguishing different indication information, and the sequence order thereof is not limited. Those skilled in the art will appreciate that the terms "first," "second," and the like do not denote any order or importance, but rather the terms "first," "second," and the like do not denote any order or importance.

It is to be understood that the terms "exemplary" or "such as" are used herein to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

In the present invention, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a alone, A and B together, and B alone, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple. Before describing the embodiments of the present invention, a brief introduction is made to some concepts related to the embodiments of the present invention:

RESP: a remote dictionary service (Redis) based serialized communication protocol can serialize different data types such as integers, strings, arrays. In addition, the protocol is binary secure and does not need to handle the size of block data transmitted from one process to another because it uses prefix length to transmit block data.

Pattern: the self-defined binary file starts with the file header comprising magic number, version information identification bits and the like, the middle part is provided with a plurality of data segments for storing data, and the tail part is provided with attribute information of each data segment.

An embedded database: different from a database, the embedded database and an application program can independently run a daemon process, and the embedded database and the application program run in the same program, so that the embedded database has the advantages of being customizable and small in size.

A localization query engine: based on self service logic, the encryption Pattern is packaged as a query engine of local built-in core data, and Application Program Interface (API) use and implementation rules are provided.

Dynamic library: also known as a Dynamic Link Library (DLL), is a library that contains code and data that can be used by multiple programs simultaneously, and is not an executable file.

Example (c): examples are a collection of "memory" and "background processes".

Hash table: the hash table is composed of key values, for example, one key value pair (Zhang III, 1318888999) in the hash table, that is "Zhang III" is a key, and 1318888999 is a value; both key and value are elements of the hash table.

The handle, the basis for the entire Windows programming. A handle refers to a unique integer value, i.e., a 4-byte (8-byte in a 64-bit program) long value, used to identify different objects in an application and different instances in the same class, such as a window, button, icon, scroll bar, output device, control, or file.

The above is an introduction of a part of concepts related to the embodiments of the present invention, and details are not described below.

With the rapid development of data storage, the application range of the database is more deep and concrete. The original database technology which is only suitable for personal computers and has large volume and long time delay can not meet the development requirement of embedded systems with strong pertinence. As the capacities of the memory and the permanent storage medium of the embedded system are continuously increased, the data processing amount in the embedded system is also continuously increased. In order to process the increasing data, a completely new database product, namely an embedded database, is generated.

When each application program is developed, a developer needs to input a lot of codes to acquire the relevant information of the embedded database interface; after obtaining the relevant parameters of the embedded database interface, developers need to input a plurality of codes according to the relevant parameters of the embedded database, and the codes form operation instructions. And accessing the embedded database through the embedded database interface according to the operation instruction. Therefore, the development efficiency of the application program is low, and the development cost is increased.

In order to solve the technical problem, according to the technical scheme of the invention, the server side responds to the protocol format request sent by the client side and sends the access protocol of the embedded database to the client side. The server receives a query request sent by the client, wherein the query request is generated based on an access protocol. And responding to the query request, and sending the target data to the client by the server side under the condition that the embedded database stores the target data. The technical scheme of the invention is that developers encapsulate API based on access protocol on the query engine of the embedded database of the server. And the server interacts with the embedded database through an API (application programming interface) of the access protocol according to the query request based on the access protocol sent by the client. Therefore, the client can query the data of the embedded database only by sending the protocol format request and the query request based on the access protocol, and does not need to input a lot of codes for each client to query the data through the API of the embedded database, thereby reducing the development cost of accessing the embedded database by the client.

Embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

The system architecture and the service scenario described in the embodiment of the present invention are for more clearly illustrating the technical solution of the embodiment of the present invention, and do not form a limitation on the technical solution provided in the embodiment of the present invention, and it can be known by those skilled in the art that the technical solution provided in the embodiment of the present invention is also applicable to similar technical problems along with the evolution of the network architecture and the appearance of a new service scenario.

The embedded database query method applied by the embodiment of the invention can be applied to a query system. Fig. 1 shows a schematic structural diagram of the query system. As shown in fig. 1, the query system 10 is used to reduce the development cost of client access to embedded databases. The query system 10 includes a server 11 and a client 12. The server 11 and the client 12 may be connected in a wired manner or in a wireless manner, which is not limited in the embodiment of the present invention.

The server 11 may be a mobile terminal or a Personal Computer (PC) used by the user. Such as a smart phone, a Personal Digital Assistant (PDA), a tablet computer, a laptop computer, a car computer (carputer), smart glasses, a smart watch, a wearable device, a virtual display device or a display enhancement device (e.g., Google Glass, Oculus Rift, Hololens, Gear VR), etc.

The server 11 is configured to receive a data query request sent by the client 12, and feed back a query result to the client 12. The server side comprises a storage module, and the storage module is used for storing the Pattern file.

It should be noted that the server 11 and the client 12 may be independent devices or may be integrated in the same device, and the present invention is not limited to this.

When the client 12 and the server 11 are integrated in the same device, the communication mode between the server 11 and the client 12 is the communication between the internal modules of the device. In this case, the communication flow between the two is the same as "the communication flow between the server 11 and the client 12 is independent of each other".

In the following embodiments provided by the present invention, the present invention is described by taking an example in which the server 11 and the client 12 are set independently of each other.

In practical applications, the query method for the embedded database provided by the embodiment of the present invention may be applied to a server and may also be applied to an electronic device.

The following describes a query method of an embedded database provided in an embodiment of the present invention. In addition, the actions, terms, and the like related to the embodiments of the present invention may be mutually referred to, and are not limited. In the embodiment of the present invention, the name of the message interacted among the devices or the name of the parameter in the message, etc. are only an example, and other names may also be used in the specific implementation, which is not limited.

Fig. 2 is a flowchart of an embedded database query method applied to a server and a client including an embedded database according to an embodiment of the present invention, where the method includes the following steps S201 to S207.

S201, the client generates a format protocol request.

Wherein the protocol format request is for an access protocol requesting the embedded database.

As a possible implementation manner, the client generates a format protocol request based on the identifier of the server and a preset message format.

For example, the preset message format may be a multi-protocol label switching (MPLS) message format, which is not limited in the embodiment of the present invention.

It should be noted that the format protocol request is generated based on data input by the user at the client. The input data at least comprises the identification of the server and the identification of the format protocol.

S202, the client sends a protocol format request to a server side comprising the embedded database.

As a possible implementation manner, the client sends a protocol format request to the server based on a preset communication protocol.

For example, the preset communication protocol User Datagram Protocol (UDP) may also be a Transmission Control Protocol (TCP), and the embodiment of the present invention is not limited thereto.

Correspondingly, the server receives the protocol format request sent by the client.

It should be noted that the server may be a redis server or other types of servers, which is not limited in the embodiment of the present invention

It can be understood that when a user as a program developer develops a program, many codes need to be input to query the relevant parameter information of the API of the embedded database. In the present invention, a user, as a program developer, encapsulates a query engine of an embedded database in an API generated based on an access protocol. Furthermore, when accessing the embedded database, the embedded database may be queried by a query request based on the access protocol. Before inquiring the embedded database, the client only needs to input a row of instructions of the protocol format request for inquiring the access protocol for accessing the embedded database.

S203, the server side responds to the protocol format request sent by the client side and sends the access protocol of the embedded database to the client side.

As a possible implementation manner, the server acquires the access protocol of the embedded database according to the protocol format request sent by the client, generates a message containing the access protocol of the embedded database, and further sends the message containing the access protocol of the embedded database to the client.

It should be noted that the access protocol may be stored in advance in the server. The server side can also determine the access protocol of the embedded database in real time. The embodiments of the present invention are not limited.

Illustratively, the access protocol may be the Redis serialization protocol RESP.

Correspondingly, the client receives the access protocol of the embedded database sent by the server.

S204, the client generates a query request based on the access protocol.

The query request is used for querying target data in the embedded database.

As a possible implementation manner, the client generates a query request based on the access protocol according to the access protocol.

It should be noted that the query request may include the identification of the server and the query value corresponding to the target data in the embedded database.

Illustratively, the client generates a query request including "GET zhang san" based on the RESP.

S205, the client sends a query request to the server.

Correspondingly, the server receives the query request sent by the client.

S206, the server side responds to the query request and judges whether the target data exist in the embedded database.

As a possible implementation manner, after receiving the query request sent by the client, the server parses the query request, and further obtains the identifier of the target data. Further, the server side inquires whether the target data exists in the embedded database or not through an inquiry engine of the embedded database based on the identification of the target data

Illustratively, the server analyzes the query request sent by the client, analyzes that the target data is Zhang III, and queries whether the target data corresponding to Zhang III exists in the embedded database through a query engine of the embedded database.

The detailed implementation of this step may refer to the following description of the embodiment of the present invention, and is not described herein again.

And S207, the server sends the target data to the client under the condition that the embedded database stores the target data.

As a possible implementation manner, the server obtains the target data when querying the target data. And the server generates a data packet based on the target data and the client identifier, and sends the data packet to the client through a preset communication protocol.

For example, based on the query request of "GET zhang san", the server queries the telephone number "198 xxxxxx" corresponding to "zhang san". The server acquires '198 xxxxxxxxxx' and sends the '198 xxxxxxxx' to the client, and generates a data packet based on '198 xxxxxxxxxx' and the identifier '192.168. xxx.xxx' of the client. The server sends the data packet to the client through the TCP.

In another case, if the embedded database does not include the target data, the server sends a query failure message to the client.

Correspondingly, the client receives the target data sent by the server.

The invention provides a query method of an embedded database, which is applied to a server side comprising the embedded database. The server receives a query request sent by the client, wherein the query request is generated based on an access protocol. And responding to the query request, and sending the target data to the client by the server side under the condition that the embedded database stores the target data. Namely, the technical scheme of the invention is that a user as a program developer encapsulates a query engine of an embedded database in an API generated based on an access protocol. And the server interacts with the embedded database through an API (application programming interface) of the access protocol according to the query request based on the access protocol sent by the client. Therefore, the client can query the data of the embedded database only by sending the protocol format request and the query request based on the access protocol, and does not need to input a lot of codes for each client to query the data through the query engine of the embedded database, thereby reducing the development cost of accessing the embedded database by the client.

In one design, in order to determine whether target data exists in the embedded database, as shown in fig. 3, S206 provided in the embodiment of the present invention may specifically include the following S2061 to S2062.

S2061, the server side responds to the query request and judges whether the query request comprises the preset identification.

The embedded database comprises a preset identifier, a preset database and a database server, wherein the preset identifier is used for indicating that target data are inquired from a preset data set included in the embedded database; the preset data set is obtained according to at least one Pattern file.

As a possible implementation manner, the server parses the query request, and determines whether a preset field in the query request includes a preset identifier.

It should be noted that the preset identifier is predefined by the server and the client.

It can be understood that the file for storing the data in the embedded database of the invention is a Pattern file, so that the invention does not need to rely on database service, and only needs the Pattern file for storing the data and the dynamic library for encapsulating the query method. Therefore, the embedded database of the invention only needs to put the Pattern file and the dynamic library which encapsulates the query method into the server, and does not need to migrate the data in the database.

S2062, under the condition that the query request comprises the preset identification, the server side judges whether the target data exists in the preset data set or not.

As a possible implementation manner, under the condition that the query request includes the preset identifier, the server parses the query Key of the query request, and queries whether target data corresponding to the query Key exists in a preset data set through a query engine of the embedded database based on the Key.

Specifically, under the condition that the query request includes the preset identifier, the server needs to query the target data from a preset data set stored in a Pattern memory through a Pattern query engine.

The Pattern memory is a memory for storing a preset data set. The Pattern query engine is used for querying a preset data set in a Pattern memory.

It should be noted that, before the target data needs to be queried from the preset data set in the Pattern memory by querying the Pattern engine, the server needs to load a Pattern file and construct a query engine. FIG. 4 shows a flowchart of a query engine for loading and building a Pattern file, and as shown in FIG. 4, the process of loading the Pattern file includes: s301, the server obtains the storage space occupied by the Pattern file, and applies for a Pattern memory for storing the Pattern file in the memory based on the storage space occupied by the Pattern file. And the space of the Pattern memory is larger than the storage space occupied by the Pattern file. S302, the server loads the Pattern file into a Pattern memory. And S303, calling a decryption algorithm corresponding to the Pattern file from the dynamic library by the server based on the Pattern file, and decrypting the Pattern file (the Pattern file is encrypted by the algorithm in the dynamic library). S304, the server side judges whether the decryption of the Pattern file is successful. S305, if the Pattern file is decrypted successfully, the server side constructs a hash table in a Pattern memory by using a Key Value Key-Value structure according to the content in the Pattern file and the category. If the server needs to construct a hash table for accurate query, Key is a determined value; if the server needs to construct a hash table for range query, the Key needs to contain two kinds of information: the minimum value of the range and the maximum value of the range. S306, after the hash table is built in the Pattern memory by the server, the query engine is successfully built. S307, if the Pattern file is not decrypted, the Pattern file is not initialized. S308, the server exits the process of loading the Pattern file and returns the identifier of loading failure.

Further, in the embodiment of the present invention, after the server successfully constructs the hash table in the applied Pattern memory, based on the query engine constructed by the hash table in the Pattern memory, two query modes may be used for querying the target data from the hash table in the Pattern memory: precision queries and range queries.

In one case, if the query request is an accurate query, that is, a Value of a Key is queried, the server directly queries the Value corresponding to the Key through the hash table according to the Key in the query request.

In another case, if the query request is in the range of the query request, that is, the query content is in the range of the maximum Value and the minimum Value of a certain Key, the server queries, by the bisection query, the Value corresponding to the query Value x from the hash table in the Pattern memory according to the query Value x in the query request. Wherein, the Key in the hash table is [ Key arranged in sequence₁，Key₂，Key₃……Key_n]N keys, satisfy Key_i[max]＜Key_i+1[min]，1≤i≤n，Key_i[max]Is the maximum value of the range in the ith Key_i+1[min]Is the minimum value of the range in the i +1 th Key.

As shown in fig. 5, the query flow by the dichotomy is as follows: s309, the server side determines the query value x of the query request. S310, the server judges the current query sequence [ Key₁，Key₂，Key₃……Key_n]Whether or not to satisfy Key_low＜Key_mid. Therein, Key_lowRepresenting the minimum value of the query sequence, Key_midRepresenting the median value of the query sequence. S311, if the Key is not satisfied_low＜Key_midThe server ends the query procedure. S312, if Key is satisfied_low＜Key_midThen the server side judges whether x is in Key_mid[min]To Key_mid[max]Within range, i.e. Key_mid[min]＜x＜Key_mid[max]. S313, if the Key is satisfied_mid[min]＜x＜Key_mid[max]Then the server returns Key_midCorresponding Value, and ending the query. S314, if not, Key_mid[min]＜x＜Key_mid[max]If, then, x < Key_mid[min]The query sequence for updating the query at the server side comprises

、Key_highAnd Key_mid(ii) a If x>Key_mid[max]If the query sequence for the server to update the query includes

、Key_lowAnd Key_mid(ii) a So that after repeated binary query, the Key is reached_mid[min]＜x＜Key_mid[max]Service side return Key_midAnd corresponding Value ends the query. Therein, Key_highRepresenting the maximum value of the query sequence, Key_mid[min]Representative Key_midMinimum value of (2)，Key_mid[max]Representative Key_midMaximum value of (1), Key_mid＝

，

Representing a rounding down.

In another case, if the query request does not include the preset identifier, the server determines whether the target data exists in the data set of the server.

As a possible implementation manner, under the condition that the query request does not include the preset identifier, the server determines whether target data exists in the data set of the server according to a query value of the query request.

Subsequently, under the condition that the target data exist in the data set of the server, the server acquires the target data and sends the target data to the client.

In one design, in order to query data during data update and implement the unaware update of the unaware embedded database, as shown in fig. 6, the embedded database query method provided in the embodiment of the present invention further includes following steps S208-S211.

S208, the server side detects whether the Pattern file to be updated exists.

As a possible implementation manner, the server detects and detects the identifier of the Pattern file to be updated periodically or in real time, and determines whether the Pattern file to be updated exists based on the identifier to be updated of the Pattern file.

Illustratively, the server periodically detects the value of the identifier to be updated of the Pattern file. And if the numerical value of the identifier to be updated of the Pattern file is '1', the server side determines that the Pattern file to be updated exists. And if the numerical value of the identifier to be updated of the Pattern file is '0', the server side determines that the Pattern file to be updated does not exist.

S209, under the condition that the Pattern file to be updated is detected, the server side obtains the Pattern file to be updated.

As a possible implementation manner, under the condition that the Pattern file to be updated exists based on the identifier to be updated of the Pattern file, the server side acquires the Pattern file to be updated from the storage module.

S210, the server generates a standby data set based on the Pattern file to be updated.

As a possible implementation manner, after decrypting the Pattern file to be updated, the server adds the Pattern file to be updated to the memory, and generates a standby data set in the memory based on the Pattern file to be updated.

Specifically, for the Pattern file to be updated, the server loads the Pattern file to be updated in the memory by using the reserved file handle, and generates a standby data set after the Pattern file to be updated is loaded successfully.

It should be noted that the present invention sets two file handles. A file handle is used as the currently used file handle for identifying the preset data set. And the other file handle is used as a reserved file handle, and when the Pattern file is updated, the Pattern file to be updated is loaded by using the reserved file handle.

In one case, in the process of generating the standby data set according to the Pattern file to be updated, the server side judges whether an inquiry request including a preset identifier is received. And if the server receives the query request comprising the preset identification, judging whether target data exist in the preset data set or not.

It can be understood that, because the data stored in the Pattern file has high business value and effectiveness, the server needs to update the Pattern file frequently. At present, a server cannot query data during the updating period of a Pattern file. And because the content of the Pattern file is encrypted, the server needs a long time in the process of decrypting and loading the updated Pattern file. Resulting in the user not being able to query for data for a longer period of time. In the embodiment of the invention, under the condition that the data in the Pattern file needs to be updated, for the Pattern file to be updated, in the process of loading the updated Pattern file into the memory, the server can still inquire whether the target data exists through the preset data set. Thus, data can still be queried during the updating of the Pattern file.

In another case, in the process of generating the standby data set according to the Pattern file to be updated, if the server does not receive the query request including the preset identifier, the standby data set is generated.

S211, after generating the spare data set, the server replaces the preset data set with the spare data set.

Specifically, after the spare data set is generated by using the reserved file handle, the server sets the reserved file handle as the currently used handle. Correspondingly, the server sets the handle used for identifying the current use of the preset data set as the reserved file handle setting.

It will be appreciated that the present invention provides for two file handles. A file handle is used as the currently used file handle for identifying the preset data set. And the other file handle is used as a reserved file handle, and when the Pattern file is updated, the server loads the Pattern file to be updated by using the reserved file handle. Therefore, when the Pattern file to be updated is loaded by using the reserved file handle, a preset data set also exists in the memory. In the process of generating the standby data set, if the user needs to query data, the server side queries the data by using the preset data set. After generating the spare data set, the server sets the reserved file handle as the currently used file handle. Namely, the server determines the spare data set as the preset data set. Therefore, in the process of generating the standby data set, the user can inquire data, and the non-perception updating is realized.

Further, a complete description of the method shown in S208-S211 above is provided. For example, fig. 7 is a flowchart of another embodiment of a query method for an embedded database according to the present invention. And S315, the server periodically or in real time detects whether the updated Pattern file exists. And S316, if the updated Pattern file is not detected, the server side continues to use the current Pattern file. And S317, if the updated Pattern file is detected, the server loads the updated Pattern file to the memory. And the server judges whether the updated Pattern file is loaded successfully or not. And S318, if the loading fails, the server side continues to use the current Pattern file. And S319, if the loading is successful, the server generates a new data set, starts the new data set, and changes the pointer of the current data set into the pointer of the new data set. And S320, stopping using the current data set by the server, and releasing the memory occupied by the current data set. S321, the server ends the updating process.

In one design, in order to reduce the occupation of the memory resources, S206 provided in the embodiment of the present invention specifically includes the following S2063.

S2063, responding to the query request based on the single thread, and judging whether the target data exists in the embedded database by the server side.

As a possible implementation manner, after receiving multiple query requests, the server processes the multiple query requests in a single thread through a multiplexing technique, so as to query whether target data exists in the embedded database based on one query request at a time.

Illustratively, the server receives 2 query requests at the same time, and then puts the 2 query requests into a single-threaded task queue. Further, the server processes the query request 1 based on a single thread. After obtaining the query result of the query request 1, the server processes the query request 2 based on the single thread, and queries whether the target data exists in the embedded database according to the query request 2.

It can be understood that, in order to query the embedded database with high performance, a user needs to start multiple query service instances at the server, and each instance needs to occupy a memory. Resulting in large memory resource occupation. In the embodiment of the present invention, a single thread processes multiple query requests through the multiplexing technique of the server, that is, only one query thread is required. Therefore, only one Pattern file needs to be loaded to the memory, and the occupation of memory resources is reduced.

More specifically, in order to test the effect of processing a query request by a single thread and a query request by multiple threads, a user of a program developer deploys a single-thread processing mode and a multi-thread query request mode at each server side under the same hardware environment, and writes a test script on another server. The performance of both modes is shown in table 1, with the same number of concurrencies (1500) and 1 hour of test time:

TABLE 1

Performance measurement	Single threaded processing	Multi-thread processing
			Average throughput	45623	30915

Based on the test results in table 1, it can be seen that, in the embodiment of the present invention, the server side employs the multiplexing technology, and a single thread processes multiple query requests, which not only reduces the occupation of memory resources, but also improves query performance and improves average throughput.

The scheme provided by the embodiment of the invention is mainly introduced from the perspective of a method. To implement the above functions, it includes hardware structures and/or software modules for performing the respective functions. Those of skill in the art will readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present embodiments.

In the embodiment of the present invention, the device may be divided into functional modules according to the method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. Optionally, the division of the modules in the embodiment of the present invention is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

Fig. 8 is a query device for an embedded database according to an embodiment of the present invention. As shown in fig. 8, the query device 40 may be located in the server. The inquiry apparatus 40 includes: a transmitting unit 401, a receiving unit 402 and a judging unit 403.

The sending unit 401 is configured to send an access protocol of the embedded database to the client in response to the protocol format request sent by the client. For example, in conjunction with fig. 2, the sending unit 401 may be configured to perform S203.

A receiving unit 402, configured to receive an inquiry request sent by a client after the sending unit sends an access protocol to the client; the query request is generated based on an access protocol; the query request is used to query the target data.

A judging unit 403, configured to judge whether target data exists in the embedded database in response to the query request received by the receiving unit 402. For example, in conjunction with fig. 2, the determination unit 403 may be configured to execute S206.

The sending unit 401 is further configured to send the target data to the client if the embedded database stores the target data. For example, in connection with fig. 2, the sending unit 401 may be configured to execute S207.

Optionally, the determining unit 403 is specifically configured to: responding to the query request, and judging whether the query request comprises a preset identifier; the preset identifier is used for indicating that target data is inquired from a preset data set included in the embedded database; the preset data set is obtained according to at least one Pattern file; and under the condition that the query request comprises the preset identification, judging whether target data exist in the preset data set or not. For example, in conjunction with fig. 3, the determination unit 403 may be used to perform S2061-2063.

Optionally, as shown in fig. 8, the querying device 40 further includes: a generation unit and a replacement unit;

the query device further comprises: a generation unit 404 and a replacement unit 405.

A generating unit 404, configured to generate a spare data set based on the Pattern file to be updated when the Pattern file to be updated exists. For example, in conjunction with fig. 6, the generating unit 404 may be configured to perform S210.

A replacing unit 405 for replacing the preset data set based on the spare data set after the spare data set is generated. For example, in conjunction with fig. 6, the replacement unit 405 may be used to perform S211.

Optionally, the determining unit 403 is further specifically configured to determine whether target data exists in the embedded database based on a single thread response to the query request. For example, the determination unit 403 may be configured to execute S2064.

Fig. 9 is a query device for an embedded database according to an embodiment of the present invention. As shown in fig. 9, the querying device 50 may be located in the client. The inquiry apparatus 50 includes: a generating unit 501, a transmitting unit 502 and a receiving unit 503.

A generating unit 501, configured to generate a format protocol request; the protocol format request is for an access protocol that requests the embedded database. For example, in conjunction with fig. 2, the generation unit 501 may be configured to perform S201.

A sending unit 502, configured to send the protocol format request generated by the generating unit 501 to the server; the server side comprises an embedded database. For example, in connection with fig. 2, the sending unit 502 may be configured to perform S202.

The receiving unit 503 is configured to receive an access protocol of the embedded database sent by the server after the sending unit sends the protocol format request to the server.

A generating unit 501, configured to generate a query request based on the access protocol received by the receiving unit 503; the query request is used for querying target data in the embedded database. For example, in conjunction with fig. 2, the generating unit 501 may be configured to perform S204.

The sending unit 502 is further configured to send the query request generated by the generating unit 501 to the server. For example, in connection with fig. 2, the sending unit 502 may be configured to execute S205.

The receiving unit 503 is further configured to receive target data sent by the server.

In the case of implementing the functions of the integrated modules in the form of hardware, the embodiment of the present invention provides a possible structural schematic diagram of the server involved in the above embodiments. As shown in fig. 10, the server 60 includes a processor 601, a memory 602, and a bus 603. The processor 601 and the memory 602 may be connected by a bus 603.

The processor 601 is a control center of the communication apparatus, and may be a single processor or a collective term for a plurality of processing elements. For example, the processor 601 may be a Central Processing Unit (CPU), or may be another general-purpose processor. Wherein the general purpose processor may be a microprocessor or any conventional processor or the like.

For one embodiment, processor 601 may include one or more CPUs, such as CPU 0 and CPU 1 shown in FIG. 10.

The memory 602 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that may store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that may store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

As a possible implementation, the memory 602 may be present separately from the processor 601, and the memory 602 may be connected to the processor 601 via a bus 603 for storing instructions or program code. The processor 601, when calling and executing instructions or program code stored in the memory 602, can implement the sensor determination method provided by the embodiments of the present invention.

In another possible implementation, the memory 602 may also be integrated with the processor 601.

The bus 603 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 10, but this is not intended to represent only one bus or type of bus.

It should be noted that the structure shown in fig. 10 does not constitute a limitation on the service end 60. In addition to the components shown in FIG. 10, the server 60 may include more or fewer components than shown, or some components may be combined, or a different arrangement of components.

As an example, in conjunction with fig. 8, the function implemented by the determination unit 403 in the querying device 40 is the same as that of the processor 601 in fig. 10.

Optionally, the server 60 provided in the embodiment of the present invention may further include a communication interface 604.

A communication interface 604 for connecting with other devices via a communication network. The communication network may be an ethernet network, a radio access network, a Wireless Local Area Network (WLAN), etc. The communication interface 604 may include a receiving unit for receiving data and a transmitting unit for transmitting data.

In one design, in the service end provided by the embodiment of the present invention, the communication interface may be further integrated in the processor.

Fig. 11 shows another hardware configuration of the server in the embodiment of the present invention. As shown in fig. 11, the server 70 may include a processor 701 and a communication interface 702. The processor 701 is coupled to a communication interface 702.

The functions of the processor 701 may refer to the description of the processor 601 above. The processor 701 also has a memory function, and the function of the memory 602 can be referred to.

The communication interface 702 is used to provide data to the processor 701. The communication interface 702 may be an internal interface of the communication device or an external interface of the communication device.

It should be noted that the configuration shown in fig. 11 does not constitute a limitation on the service end 70, and the service end 70 may include more or less components than those shown in fig. 11, or some components may be combined, or a different arrangement of components may be provided, in addition to the components shown in fig. 11.

Meanwhile, the schematic diagram of the hardware structure of the client provided in the embodiment of the present invention may also refer to the description of the server in fig. 10 or fig. 11, which is not described herein again.

Through the above description of the embodiments, it is clear for a person skilled in the art that, for convenience and simplicity of description, only the division of the above functional units is illustrated. In practical applications, the above function allocation can be performed by different functional units according to needs, that is, the internal structure of the device is divided into different functional units to perform all or part of the above described functions. For the specific working processes of the system, the apparatus and the unit described above, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described here again.

The embodiment of the present invention further provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the computer executes the instructions, the computer executes each step in the flow of the query method for the embedded database shown in the foregoing method embodiment.

Embodiments of the present invention further provide a computer program product including instructions, which when run on a computer, cause the computer to execute the method for querying an embedded database in the foregoing method embodiments.

The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, and a hard disk. Random Access Memory (RAM), Read-Only Memory (ROM), Erasable Programmable Read-Only Memory (EPROM), registers, a hard disk, an optical fiber, a portable Compact disk Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any other form of computer-readable storage medium, in any suitable combination, or as appropriate in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an Application Specific Integrated Circuit (ASIC). In embodiments of the invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

Since the server, the client, the computer-readable storage medium, and the computer program product in the embodiments of the present invention may be applied to the method described above, the technical effects obtained by the embodiments of the method may also refer to the embodiments of the method described above, and no further details are given in the embodiments of the present invention.

The above description is only an embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions within the technical scope of the present invention are intended to be covered by the scope of the present invention.

Claims

1. A query method of an embedded database is applied to a server side comprising the embedded database, and the method comprises the following steps:

responding to a protocol format request sent by a client, and sending an access protocol of the embedded database to the client;

receiving a query request sent by the client; the query request is generated based on the access protocol; the query request is used for querying target data in the embedded database;

responding to the query request, and judging whether the target data exists in the embedded database;

and sending the target data to the client under the condition that the embedded database is in the target data.

2. The method according to claim 1, wherein said determining whether the target data exists in the embedded database in response to the query request comprises:

responding to the query request, and judging whether the query request comprises a preset identifier; the preset identification is used for indicating that the target data is inquired from a preset data set included in the embedded database; the preset data set is obtained according to at least one Pattern file;

and under the condition that the query request comprises the preset identification, judging whether the target data exists in the preset data set or not.

3. The query method of claim 2, wherein the method further comprises:

under the condition that the Pattern file to be updated exists, generating a standby data set based on the Pattern file to be updated;

after generating the backup data set, replacing the preset data set based on the backup data set.

4. The query method according to any one of claims 1 to 3, wherein the determining whether the target data exists in the embedded database in response to the query request further comprises:

and responding to the query request based on single thread, and judging whether the target data exists in the embedded database.

5. A query method of an embedded database is applied to a client, and the method comprises the following steps:

generating a format protocol request, and sending the protocol format request to a server side comprising the embedded database; the protocol format request is used for requesting an access protocol of the embedded database;

receiving the access protocol sent by the server;

generating a query request based on the access protocol, and sending the query request to the server; the query request is used for requesting to query the target data in the embedded database;

and receiving the target data sent by the server.

6. An inquiry device of an embedded database, which is applied to a server side including the embedded database, the device comprising: a transmitting unit, a receiving unit and a judging unit;

the sending unit is used for responding to a protocol format request sent by a client and sending an access protocol of the embedded database to the client;

the receiving unit is configured to receive an inquiry request sent by the client after the sending unit sends the access protocol to the client; the query request is generated based on the access protocol; the query request is used for querying target data in the embedded database;

the judging unit is used for responding to the query request received by the receiving unit and judging whether the target data exists in the embedded database;

the sending unit is further configured to send the target data to the client when the embedded database is in the target data.

7. The query device according to claim 6, wherein the determining unit is specifically configured to:

8. The querying device of claim 7, wherein the querying device further comprises: a generation unit and a replacement unit;

the generating unit is used for generating a standby data set on the basis of the Pattern file to be updated under the condition that the Pattern file to be updated exists;

the replacing unit is used for replacing the preset data set based on the spare data set after the spare data set is generated.

9. The query device according to any one of claims 6 to 8, wherein the determining unit is further specifically configured to determine whether the target data exists in the embedded database in response to the query request based on a single thread.

10. An inquiry device of an embedded database, which is applied to a client, the device comprises: a generating unit, a transmitting unit and a receiving unit;

the generating unit is used for generating a format protocol request; the protocol format request is used for requesting an access protocol of the embedded database;

the sending unit is used for sending the protocol format request generated by the generating unit to a server side comprising the embedded database;

the receiving unit is configured to receive the access protocol sent by the server after the sending unit sends the protocol format request to the server;

the generating unit is further configured to generate a query request based on the access protocol received by the receiving unit; the query request is used for querying target data in the embedded database;

the sending unit is further configured to send the query request generated by the generating unit to the server;

the receiving unit is further configured to receive the target data sent by the server.

11. A computer-readable storage medium having stored therein instructions that, when executed by an electronic device, enable the electronic device to perform the method of querying an embedded database of any one of claims 1 to 4, or claim 5.

12. A server, comprising: a processor, a memory, and a communication interface; wherein, the communication interface is used for the communication device to communicate with other equipment or networks; the memory is used for storing one or more programs, the one or more programs comprise computer-executable instructions, and when the server runs, the processor executes the computer-executable instructions stored in the memory, so that the server executes the query method of the embedded database according to any one of claims 1 to 4.

13. A client, comprising: a processor, a memory, and a communication interface; wherein, the communication interface is used for the communication device to communicate with other equipment or networks; the memory is used for storing one or more programs, the one or more programs comprise computer-executable instructions, and when the client runs, the processor executes the computer-executable instructions stored in the memory to enable the client to execute the query method of the embedded database according to claim 5.