CN113645289A

CN113645289A - Quota data request method, sending method, client, server and system

Info

Publication number: CN113645289A
Application number: CN202110885143.5A
Authority: CN
Inventors: 徐翔; 吴森阳
Original assignee: Glodon Co Ltd
Current assignee: Glodon Co Ltd
Priority date: 2021-08-03
Filing date: 2021-08-03
Publication date: 2021-11-12

Abstract

The invention discloses a quota data request method and a quota data sending method, wherein the quota data request method comprises the following steps: generating a rating data request based on attribute information and identification information of the rating data; sending the quota data request to a first server. The quota data sending method comprises the following steps: receiving a quota data request sent by a client, wherein the quota data request carries attribute information and identification information of quota data; and determining the quota data based on the attribute information and the identification information in the quota data request, and returning the quota data to the client. The method can effectively improve the convenience of using the new quota data by the user.

Description

Quota data request method, sending method, client, server and system

Technical Field

The invention relates to the technical field of computers, in particular to a quota data request method, a quota data sending method, a client, a server and a quota data management system.

Background

The quota data is one of the main bases for calculating the construction cost, is generally compiled by a government department and is published in a book form by a publisher, and mainly comprises quota items and compilation specifications. The pricing software is used as tool software for assisting in calculating the construction cost, and a software company can process issued quota data into an electronic edition to be packaged with the pricing software, and then the pricing software is downloaded and installed by a user integrally for use.

However, there may be errors in the process of processing the rating data into electronic versions, and the published rating data may no longer be accurate over time and market changes, so that government agencies may issue policy documents for revising the rating data. When the quota data is in error or a government department publishes a new policy document, the software company updates the quota data at regular time, packages and publishes the updated quota data and the pricing software together, and then downloads and installs the updated quota data integrally by the user, so that the user can use the updated quota data in the pricing software.

The inventor has found that when rating data is updated in the prior art, the user must re-download the installation software if using the new rating data and then use the updated rating data. The whole operation flow is complex and occupies a large storage space, and an effective solution to the problem is not provided at present.

Disclosure of Invention

The invention aims to provide a quota data request method, a quota data sending method, a client, a server and a quota data management system, which can solve the technical problems.

One aspect of the present invention provides a quota data request method, the method comprising: generating a rating data request based on attribute information and identification information of the rating data; sending the quota data request to a first server.

Optionally, the attribute information is used to determine a target quota data packet in the first server, and the identification information is used to identify the quota data in the target quota data packet.

Optionally, the step of generating a rating data request based on the attribute information and the identification information of the rating data comprises: receiving a quota data insertion instruction; analyzing the quota data insertion instruction, and determining attribute information and identification information associated with the quota data insertion instruction; and generating the quota data request according to the attribute information and the identification information associated with the quota data insertion instruction.

Optionally, the step of determining attribute information and identification information associated with the quota data insertion instruction comprises: acquiring identification information carried by the quota data insertion instruction as identification information associated with the quota data insertion instruction; and acquiring the region information carried by the quota data insertion instruction, determining the type of the project file for inserting the quota data, determining the version information of the quota data according to the type of the project file, and taking the region information and the determined version information in the quota data insertion instruction as the attribute information associated with the quota data insertion instruction.

Optionally, the step of determining the version information of the quota data according to the type of the project file, and using the region information in the quota data insertion instruction and the determined version information as the attribute information associated with the quota data insertion instruction includes: when the type of the engineering file is a new type, determining the region information of the current available quota data packet matched with the region information in the quota data insertion instruction in a current available quota data packet attribute list, and acquiring version information associated with the determined region information of the current available quota data packet; determining latest version information from the acquired version information; taking the region information and the latest version information in the quota data insertion instruction as attribute information associated with the quota data insertion instruction; the attribute list of the current available quota data packet prestores the region information and the version information of all current available quota data packets in the first server, and the current available quota data packet comprises a quota data packet of which the state information is an enabled state.

Optionally, the step of determining the version information of the quota data according to the type of the project file, and using the region information in the quota data insertion instruction and the determined version information as the attribute information associated with the quota data insertion instruction includes: when the type of the project file is a history type, determining the version information of a quota data packet used by the project file; and taking the version information and the region information in the quota data insertion instruction as attribute information associated with the quota data insertion instruction.

Optionally, the step of sending the quota data request to a first server comprises: judging whether the network is in a networking state at present; when the network is in a networking state, searching whether quota data are stored locally through a network engine interface, if so, acquiring the quota data locally, if not, sending the quota data request to the first server, receiving the quota data returned by the first server based on the quota data request, and caching the received quota data locally; and when the current state is not in a networking state, searching whether quota data are stored locally or not through an offline engine interface, if so, acquiring the quota data locally, and if not, displaying prompt information for prompting to request to network to acquire the quota data.

Another aspect of the present invention provides a method for transmitting quota data, the method comprising: receiving a quota data request sent by a client, wherein the quota data request carries attribute information and identification information of quota data; and determining the quota data based on the attribute information and the identification information in the quota data request, and returning the quota data to the client.

Optionally, the step of determining the quota data based on the attribute information and the identification information in the quota data request comprises: determining a target quota data packet according to the attribute information in the quota data request; and identifying quota data pointed to by the identification information in the quota data request in the target quota data packet.

Optionally, the step of determining a target quota packet according to the attribute information in the quota data request includes: determining attribute information of the quota data packet matched with the attribute information in the quota data request in a preset first database, and acquiring address information associated with the determined attribute information of the quota data packet; determining a target database in all second databases for storing quota data packets according to the acquired address information; searching the quota data packet related to the attribute information of the determined quota data packet in the target database to serve as the target quota data packet; the first database is pre-stored with attribute information of the quota data packet and address information of the second database.

Optionally, the step of obtaining address information associated with the attribute information of the determined quota packet includes: acquiring state information associated with the attribute information of the determined quota data packet in the first database; when the acquired state information is in a starting state, acquiring address information associated with the attribute information of the determined quota data packet; when the acquired state information is in a forbidden state or a deleted state, generating prompt information for prompting that the request is invalid and returning the prompt information to the client; and the first database is also pre-stored with state information used for representing the current state of the quota data packet.

Optionally, before the step of determining a target quota packet according to the attribute information in the quota data request, the method further comprises: receiving the target quota data packet uploaded by the second server; determining the data amount of the target rated data packet and the remaining storage capacity of each second database for storing the rated data packet; when a second database with the residual storage capacity larger than or equal to the data volume exists, taking any second database with the residual storage capacity larger than or equal to the data volume as a second database to be used, otherwise, generating a new database with the residual storage capacity larger than or equal to the data volume as the second database to be used according to a preset capacity expansion mechanism; and storing the target quota data packet into the second database needing to be used.

Optionally, after the step of storing the target quota data packet in the second database for use, the method further comprises: acquiring attribute information of the target quota data packet and address information of the second database required to be used; and associating the attribute information of the target quota data packet with the address information of the second database required to be used, and storing the associated attribute information and address information into the first database.

Optionally, after the step of associating the attribute information of the target quota packet with the address information of the second database that needs to be used, and storing the associated attribute information and address information in the first database, the method further includes: receiving an enabling instruction sent by the second server for the target quota data packet, setting the state information of the target quota data packet in the first database as an enabling state, and associating the state information with the attribute information of the target quota data packet and the address information of the second database required to be used; or receiving a disabling instruction sent by the second server for the target quota data packet, setting the state information of the target quota data packet in the first database as a disabling state, and associating the state information with the attribute information of the target quota data packet and the address information of the second database required to be used; or receiving a deletion instruction sent by the second server for the target quota data packet, setting the state information of the target quota data packet in the first database as a deletion state, associating the state information with the attribute information of the target quota data packet and the address information of the second database required to be used, and deleting the target quota data packet in the second database required to be used.

Optionally, before the step of receiving a quota data request sent by a client, the method further comprises: receiving a current available quota data packet attribute request sent by the client, and extracting attribute information of a quota data packet with state information in an enabling state from the first database; and generating a current available quota data packet attribute list according to the extracted attribute information, and returning the current available quota data packet attribute list to the client.

Yet another aspect of the present invention provides a client, including: the generation module is used for generating a quota data request based on the attribute information and the identification information of the quota data; and the sending module is used for sending the quota data request to the first server.

A further aspect of the invention provides a server comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the rating data sending method according to any of the embodiments described above when executing the computer program.

Yet another aspect of the present invention provides a quota data management system, the system comprising a client, a first server and a second server, wherein: the client is used for executing the quota data request method in any embodiment; the first server is configured to execute the quota data sending method according to any of the above embodiments; the second server is used for uploading a target quota data packet to the first server, and sending an enabling instruction or a disabling instruction or a deleting instruction aiming at the target quota data packet to the first server after the uploading is completed.

According to the method and the device, the quota data of the electronic edition are converted into the quota data packet which can be directly called, the quota data packet is stored in the first server, when the client needs to load the quota data, software does not need to be downloaded and installed as in the prior art, the required quota data are directly obtained from the first server through a request, and the storage space of the client does not need to be additionally occupied. And when the current quota data needs to be updated, only an engineer needs to upload the updated quota data packet to the first server, when a client needs to load the quota data, the latest quota data can be directly requested to the first server through the preset logic, and for a user, the updated quota installation packet does not need to be downloaded and installed again as in the prior art.

Drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:

FIG. 1 is a block diagram of a quota data management system according to an embodiment of the present invention;

FIG. 2 is a diagram illustrating a relationship between a first database and a second database according to an embodiment of the present invention;

FIG. 3 is a schematic diagram illustrating a client operation flow according to an embodiment of the present invention;

FIG. 4 is a diagram illustrating a quota data management system according to an embodiment of the present invention;

fig. 5 is a flowchart illustrating a quota data transmitting method according to a second embodiment of the present invention;

FIG. 6 is a flow chart of a quota data request method according to a third embodiment of the present invention;

FIG. 7 is a block diagram of a client according to a fourth embodiment of the present invention;

fig. 8 is a block diagram of a computer device suitable for implementing a quota data request method or a quota data transmission method according to a fifth embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

It should be noted that, in this document, 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, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Fig. 1 shows a block diagram of a quota data management system according to an embodiment of the present invention, where the quota data management system 100 may include a first server 101, a second server 102, and a client 103, where the first server 101 may be a cloud server, and the second server 102 may be a backend server, and for convenience of understanding, an interaction flow among the first server 101, the second server 102, and the client 103 is described in detail by taking a target quota data packet as an example, specifically:

the second server 102 is configured to upload a target quota data packet to the first server 101.

After the paper quota book is processed into the electronic version of data, the second server can convert the electronic version of data into a format that can be read by the second server, namely a quota data packet. The rating data in the rating package may include rating entries and organizational specifications. In addition, the quota data packet may further include its own attribute information, where the attribute information includes region information and version information, where the region information is used to define a region range to which the quota data packet is applicable, for example, a quota data packet in the beijing region is applicable to the beijing whole area, and the version information is used to define a version of the quota data packet. For example, when the quota packet needs to be updated, the second server generates a new version of the quota packet, so that the same region information can be associated with multiple versions of information.

It should be noted that the quota data package described in this embodiment is different from the quota installation package, the quota installation package needs to be installed locally before being used, and the quota data package can be directly used without installation.

The first server 101 is configured to: receiving the target quota data packet uploaded by the second server 102; determining the data amount of the target rated data packet and the remaining storage capacity of each second database for storing the rated data packet; when a second database with the residual storage capacity larger than or equal to the data volume exists, taking any second database with the residual storage capacity larger than or equal to the data volume as a second database required to be used; when the second database with the residual storage capacity larger than or equal to the data volume does not exist, generating a new database with the residual storage capacity larger than or equal to the data volume according to a preset capacity expansion mechanism as the second database required to be used; storing the target quota data packet into the second database needing to be used; acquiring attribute information of the target quota data packet and address information of the second database required to be used; and associating the attribute information of the target quota data packet with the address information of the second database required to be used, and storing the associated attribute information and address information into the first database.

In the present embodiment, there may be one second database or a plurality of second databases, or one first database or a plurality of first databases. Each second database may store a plurality of quota packets, and each first database may store a plurality of index information. The index information is information that can accurately locate the desired target quota packet. Each piece of index information in this embodiment includes: attribute information of the quota packet and address information of the second database in which the quota packet is stored.

As shown in fig. 2, the database instance 0 is a first database, the database instances 1 to 3 are respectively a second database, each second database stores a plurality of rating data packets, and the rating data packets stored in each second database may include rating data packets of different regions, and may also include rating data packets of different versions in the same region. Wherein V1 may represent version 1, V2 may represent version 2, and may represent other versions, such as version 3, version 4 …

In the embodiment, the quota data packet is stored in a distributed database mode, so that the problem that a single database cannot store data when the data volume is too large is effectively solved, and dynamic capacity expansion can be realized when all the second databases cannot store the quota data packet. In addition, the first database is used for managing the relation between the quota data packet and the second database, so that the second database storing the required quota data packet can be conveniently and quickly positioned, and the speed of determining the quota data is increased.

The second server 102 is further configured to: after uploading the target quota data packet is completed, an enabling instruction or a disabling instruction or a deleting instruction for the target quota data packet is sent to the first server 101.

The first server 101 is further configured to: receiving an enabling instruction sent by the second server 102 for the target quota data packet, setting the state information of the target quota data packet in the first database as an enabling state, and associating the state information with the attribute information of the target quota data packet and the address information of the second database required to be used; or, receiving a disable instruction sent by the second server 102 for the target quota packet, setting the state information of the target quota packet in the first database as a disable state, and associating the state information with the attribute information of the target quota packet and the address information of the second database required to be used; or, receiving a deletion instruction sent by the second server 102 for the target quota packet, setting the state information of the target quota packet in the first database as a deletion state, associating the state information with the attribute information of the target quota packet and the address information of the second database to be used, and deleting the target quota packet in the second database to be used.

The operation interface of the second server may display information that the target quota data packet has been uploaded, after which:

the second server may send an enabling instruction for the target quota data packet to the first server, and the first server finds the index information of the target quota data packet in the first database according to the enabling instruction, and then sets the state information of the target quota data packet in the index information as an enabling state.

The second server can also send a disabling instruction aiming at the target quota data packet to the first server, the first server finds the index information of the target quota data packet in the first database according to the enabling instruction, and then the state information of the target quota data packet is set to be a disabling state in the index information.

The second server may also send a deletion instruction for the target quota data packet to the first server, where the first server finds the index information of the target quota data packet in the first database according to the enabling instruction, then sets the state information of the target quota data packet in the index information as a deletion state, obtains address information from the index information, determines the second database to which the address information points, and then deletes the target quota data packet stored in the second database.

The state information is used for representing the current state of the target quota data packet.

It should be noted that, when the status information of the target quota packet is set for the first time (that is, when the status information of the target quota packet does not exist in the first database), the setting described in this embodiment is addition, that is, the status information of the target quota database is added in the first database; when the state information of the target quota data packet is not set for the first time (namely, when the state information of the target quota data packet is already set in the first database), the state information of the target data packet only needs to be changed into the state corresponding to the current instruction (such as an enabling instruction, a disabling instruction or a deleting instruction).

The client 103 is configured to send a request for attributes of a currently available quota data packet to the first server 101.

When a user inserts quota data into a project file through a client (which can be pricing software or equipment provided with the pricing software), the client can request the first server to acquire the quota data. Firstly, a user enables rating software, and then after the rating software is started, in order to avoid the defect that a series of operations are useless and time and labor are wasted after rating data packets of subsequently requested rating data belong to a disabled state or a deleted state, a client sends a current available rating data packet attribute request to a first server, wherein the current available rating data packet attribute request is used for requesting to obtain a current available rating data packet attribute list, the current available rating data packet attribute list comprises area information and version information of a current available rating data packet related to the first server, and the current available rating data packet is a rating data packet with state information in an enabled state, so that the requested data are ensured to be valid data.

The first server 101 is further configured to: receiving a current available quota data packet attribute request sent by the client 103, and extracting attribute information of a quota data packet with state information in an enabled state from the first database; and generating a current available quota data packet attribute list according to the extracted attribute information, and returning the current available quota data packet attribute list to the client.

The first server extracts the attribute information of all quota databases of which the state information is in the starting state from the first database, then stores the extracted attribute information in a data table to obtain a current available quota data packet attribute list, and further returns the current available quota data packet attribute list to the client.

The client 103 is further configured to: receiving the current available quota data packet attribute list returned by the first server 101, and storing the current available quota data packet attribute list locally.

The client may store the list of attributes of the currently available quota data packets in a local memory, or may store the list of attributes of the currently available quota data packets in a local disk.

The client 103 is further configured to: generating a rating data request based on attribute information and identification information of the rating data; the quota data request is sent to the first server 101.

The attribute information is used for determining a target quota data packet in the first server, and the identification information is used for identifying the quota data in the target quota data packet. As an example, the identification information comprises a unique identification of the rating data, by means of which the requested rating data can be accurately queried.

The client 103, when performing the step of generating the rating data request based on the attribute information and the identification information of the rating data, is further configured to: receiving a quota data insertion instruction; analyzing the quota data insertion instruction, and determining attribute information and identification information associated with the quota data insertion instruction; and generating the quota data request according to the attribute information and the identification information associated with the quota data insertion instruction.

Said client 103, when performing said step of determining attribute information and identifying information associated with said quota data insertion instruction, is further configured to: acquiring identification information carried by the quota data insertion instruction as identification information associated with the quota data insertion instruction; and acquiring the region information carried by the quota data insertion instruction, determining the type of the project file for inserting the quota data, determining the version information of the quota data according to the type of the project file, and taking the region information and the determined version information in the quota data insertion instruction as the attribute information associated with the quota data insertion instruction.

When the client determines the identification information and the attribute information, wherein the area information in the identification information and the attribute information is both contained in the quota data insertion instruction, the identification information and the area information can be directly obtained from the quota data insertion instruction, but the attribute information is not completely determined at this time, so that the type of the project file for inserting the quota data can be further determined, the version information in the attribute information is determined according to the type of the project file, and the area information and the version information are used as the attribute information.

When the step of determining the version information of the quota data according to the type of the project file and using the region information and the determined version information in the quota data insertion instruction as the attribute information associated with the quota data insertion instruction is executed by the client 103, the method further comprises: when the type of the engineering file is a new type, determining the region information of the current available quota data packet matched with the region information in the quota data insertion instruction in a current available quota data packet attribute list, and acquiring version information associated with the determined region information of the current available quota data packet; determining latest version information from the acquired version information; taking the region information and the latest version information in the quota data insertion instruction as attribute information associated with the quota data insertion instruction; the attribute list of the current available quota data packet prestores area information and version information of the current available quota data packet associated with the first server 101, where the current available quota data packet includes a quota data packet whose state information is an enabled state.

When the step of determining the version information of the quota data according to the type of the project file and using the region information and the determined version information in the quota data insertion instruction as the attribute information associated with the quota data insertion instruction is executed by the client 103, the method further comprises: when the type of the project file is a history type, determining the version information of a quota data packet used by the project file; and taking the version information and the region information in the quota data insertion instruction as attribute information associated with the quota data insertion instruction.

The quota data insertion instruction carries identification information, and the identification information is directly acquired from the quota data insertion instruction and can be used as identification information associated with the quota data insertion instruction. The identification information may be a quota data identifier, and quota data associated with the identification information may be identified from a corresponding quota data packet by the identification information.

The quota data insertion instruction also carries region information, and after the version information required this time is determined, the region information in the quota data insertion instruction and the version information required this time can be used as attribute information associated with the quota data insertion instruction. In this embodiment, the version information required at this time may be determined by the type of the project file used to insert the quota data. Specifically, the method comprises the following steps: A. if a user opens a historical project file, the type of the project file (namely the historical project file) used for inserting the quota data is a historical type, the project file is historically associated with the version information of the quota data package used by the project file, and at the moment, the version information of the quota data package associated with the project file is directly obtained according to the association relationship; B. if a user creates a new project file, the type of the project file used for inserting the rating data (i.e. the newly created project file) is the new type, and at this time, the project file is not associated with any rating data packet, so that the version information required this time can be determined according to the currently available rating data packet attribute list obtained by interaction with the first server, specifically, all the version information associated with the region information in the rating data insertion instruction is determined from the currently available rating data packet attribute list, and then the latest version information is determined from the version information and is used as the version information required this time. Further, the version information finally determined by the A or the B and the area information in the quota data insertion instruction are used as attribute information associated with the quota data insertion instruction.

The client 103, when performing the step of sending the quota data request to the first server 101, is further configured to: judging whether the network is in a networking state at present; when the network is in a networking state, searching whether quota data are stored locally through a network engine interface, if so, acquiring the quota data locally, if not, sending the quota data request to the first server, receiving the quota data returned by the first server based on the quota data request, and caching the received quota data locally; and when the current state is not in a networking state, searching whether quota data are stored locally or not through an offline engine interface, if so, acquiring the quota data locally, and if not, displaying prompt information for prompting to request to network to acquire the quota data.

In order to flexibly acquire quota data, the client is preset with two engine interfaces, and determines which engine interface requests the quota data through the current networking state. Specifically, as shown in fig. 3, a quota engine interface layer is called, whether the current state is in a networking state is judged, if the current state is in the networking state, whether requested quota data is stored locally is searched through a network engine interface (namely, a network version quota engine), if the requested quota data is obtained locally, otherwise, a quota data request is directly sent to a second server (a cloud quota application service is a module in the second server) through a network, and then the quota data returned by the second server is received through the network and stored locally; if not, searching whether quota data is cached locally through an offline engine interface (namely a local engine), if so, displaying prompt information for prompting to request the network to acquire the quota data, otherwise, displaying the prompt information, wherein the prompt information is acquired locally. Optionally, the obtained quota data may be downloaded to a local cache, and then the quota data may be directly obtained from the local cache next time, which has the effect of convenience and rapidness.

The first server 101 is further configured to: receiving a quota data request sent by a client 103; the quota data request carries attribute information and identification information of quota data; and determining the requested quota data based on the attribute information and the identification information in the quota data request, and returning the quota data to the client.

The quota data request carries attribute information and identification information, the attribute information and the identification information can be obtained by analyzing the quota data request, the attribute information is used for determining a target quota data packet in the first server, and the identification information is used for identifying the quota data in the target quota data packet.

The first server 101, when performing the step of determining the quota data based on the attribute information and the identification information in the quota data request, is further configured to: determining a target quota data packet according to the attribute information in the quota data request; and identifying quota data pointed to by the identification information in the quota data request in the target quota data packet.

The first server can determine a target quota data packet according to the attribute information in the quota data request, can identify quota data from the target quota data packet according to the identification information in the quota data request, and returns the quota data to the client. It should be noted that, after receiving the quota data returned by the first server, the client inserts the quota data into the project file, and caches the quota data locally.

The first server 101, when performing the step of determining a target quota data packet according to the attribute information in the quota data request, is further configured to: determining attribute information of the quota data packet matched with the attribute information in the quota data request in a preset first database, and acquiring address information associated with the determined attribute information of the quota data packet; determining a target database in all second databases for storing quota data packets according to the acquired address information; searching the quota data packet related to the attribute information of the determined quota data packet in the target database to serve as the target quota data packet; the first database is pre-stored with attribute information of the quota data packet and address information of the second database.

The first server traverses the first database, determines the attribute information of the quota data packet matched with the attribute information in the quota data request, then screens out the index information containing the attribute information of the determined quota data packet from all index information of the first database, acquires the address information contained in the screened index information, determines a second database to which the address information points as a target database, wherein the target database necessarily contains the quota data packet related to the attribute information of the determined quota data packet, and takes the quota data packet as the target quota data packet to be searched.

The first server 101, when performing the step of obtaining the address information associated with the attribute information of the determined quota data packet, is further configured to: acquiring state information associated with the attribute information of the determined quota data packet in the first database; when the acquired state information is in a starting state, acquiring address information associated with the attribute information of the determined quota data packet; when the acquired state information is in a forbidden state or a deleted state, generating prompt information for prompting that the request is invalid and returning the prompt information to the client; and the first database is also pre-stored with state information used for representing the current state of the quota data packet.

In order to further ensure that the requested quota data is valid data and avoid useless operation, the second server may further determine state information associated with the attribute information of the quota data packet, and further acquire address information associated with the attribute information of the quota data packet only when the state information is in an enabled state; and when the state information is in a disabled state or a deleted state, indicating that quota data wanted to be acquired is unavailable, at this time, the useless operation of acquiring the address information is not executed, but prompt information for prompting that the request is invalid is directly generated and returned to the client, so that the client makes corresponding adjustment based on the prompt information.

The following describes an interaction flow between the first server, the second server and the client by taking fig. 4 as an example.

The second server may include a library tool module and a release management module. After the paper quota book is processed into the data of the electronic version, the data of the electronic version can be converted into a format which can be read by the first server, namely a quota data packet, through the library making tool module. For the convenience of understanding, the present embodiment details the interaction flow between the client, the first server and the second server by taking a target quota data packet as an example. Specifically, the publishing management module has an online publishing function, and the target quota data packet can be uploaded to the first server through the publishing management module. The cloud quota application service in the first server receives the target quota data packet uploaded by the publishing management module, stores the target quota data packet in an available database (also called a second database required to be used), and then stores the attribute information of the target quota data packet and the address information of the second database required to be used in a management database (also called a first database) in a correlation manner, at this time, an operation interface of the second server can display that the target quota data packet is uploaded completely. Further, the issuing management module further has an enabling function, a disabling function and a deleting function, after the target quota data packet is uploaded, the issuing management module may execute the enabling function, the disabling function or the deleting function to send an enabling instruction, a disabling instruction or a deleting instruction for the quota data packet to the first server, the cloud quota application service module receives the corresponding instruction, adds state information used for representing that the current state of the target quota data packet is an enabling state, a disabling state or a deleting state in the first database, and then associates the state information with the attribute information of the target quota data packet stored in the first database and the address information of the second database which is required to be used correspondingly.

Based on this, when the user inserts quota data (also called to-be-inserted quota data) into the engineering file through the pricing software installed on the client, the client can request the first server to acquire the to-be-inserted quota data. Specifically, after the pricing software is started, the client sends a request for attributes of currently available quota data packets to the first server, the cloud quota application service of the first server responds to the request, collects attribute information of all quota data packets of which the status information is in an enabled status from the first database, stores the collected attribute information in a data table and returns the data table to the client, wherein the data table in which the attribute information is stored is also called a current available quota data packet attribute list. The client receives the list and stores the list locally, and in response to a quota data insertion instruction triggered by a user, determines attribute information and identification information associated with the quota data insertion instruction. Further, the client generates a quota data request through attribute information and identification information associated with the quota data insertion instruction, calls a quota engine interface layer to judge whether the client is currently in a networking state, searches whether quota data to be inserted is stored locally through an offline engine interface if the client is not in the networking state, acquires the quota data locally if the client is not in the networking state, and otherwise displays prompt information for prompting the client to acquire the quota data to be inserted through the networking; if the network is connected, whether quota data to be inserted are stored locally or not is searched through a network engine interface, if yes, the quota data are obtained locally, otherwise, a quota data request is sent to a first server, a cloud quota application service of the first server analyzes attribute information and identification information carried by the request, the attribute information of a quota data packet matched with the attribute information in the quota data request is searched in a first database, state information associated with the attribute information of the determined quota data packet is judged, if the state information is in an enabled state, address information associated with the attribute information of the determined quota data packet is obtained, a second database to which the obtained address information points is determined and is marked as a target database, further, the quota data packet associated with the attribute information of the determined quota data packet is searched in the target database and is taken as the target quota data packet, and then, quota data pointed by the identification information in the quota data request are extracted from the target quota data packet, the extracted quota data are returned to the client as to-be-inserted quota data, the client stores the received to-be-inserted quota data locally, and meanwhile, the received to-be-inserted quota data are inserted into the engineering file.

According to the method and the device, the quota data of the electronic edition are converted into the quota data packet which can be directly called, the quota data packet is stored in the first server, when the client needs to load the quota data, software does not need to be downloaded and installed as in the prior art, the required quota data are directly obtained from the first server through a request, and the storage space of the client does not need to be additionally occupied. And when the current quota data needs to be updated, only an engineer needs to upload the updated quota data package to the first server, when a client needs to load the quota data, the latest quota data can be directly requested to the first server through the preset logic, and for a user, the updated quota installation package does not need to be downloaded and installed again as in the prior art.

Example two

The quota data sending method provided by the second embodiment is applied to the first server, as shown in fig. 5, fig. 5 shows a flowchart of the quota data sending method provided by the second embodiment of the present invention, and the quota data determining method may include steps S1 to S2, where:

step S1, receiving a quota data request sent by a client, wherein the quota data request carries attribute information and identification information of quota data;

step S2, determining the requested quota data based on the attribute information and the identification information in the quota data request, and returning the quota data to the client.

Optionally, the step S3 includes steps S31 to S2, wherein:

step S31, determining a target quota data packet according to the attribute information in the quota data request;

step S31, identifying in the target quota packet, quota data pointed to by the identification information in the quota data request

Alternatively, step S31 may include steps S311 to S313, in which:

step S311, determining the attribute information of the quota data packet matched with the attribute information in the quota data request in a preset first database, and acquiring the address information associated with the attribute information of the determined quota data packet;

step S312, determining a target database in all second databases for storing quota data packets according to the acquired address information;

step 313, searching for the quota data packet associated with the attribute information of the determined quota data packet in the target database as the target quota data packet;

the first database is pre-stored with attribute information of the quota data packet and address information of the second database.

Optionally, the step of acquiring the address information associated with the attribute information of the fixed quota packet in step S311 includes steps S3111 to S3113, where:

step S3111, acquiring status information associated with attribute information of the fixed quota packet in the first database;

step S3112, when the acquired status information is an enabled status, acquiring address information associated with the attribute information of the quota packet;

step S3113, when the acquired status information is in a disabled status or a deleted status, generating prompt information for prompting that the request is invalid and returning the prompt information to the client;

and the first database is also pre-stored with state information used for representing the current state of the quota data packet.

Optionally, before step S31, the quota data transmission further comprises step a1 to step a5, wherein:

step A1, receiving the target quota data packet uploaded by the second server;

step A2, determining the data quantity of the target quota data packet and the remaining storage capacity of each second database for storing quota data packets;

step A3, when there is a second database with the residual storage capacity being equal to or larger than the data amount, using any one of the second databases with the residual storage capacity being equal to or larger than the data amount as a second database to be used;

step A4, when there is no second database with the residual storage capacity greater than or equal to the data volume, generating a new database with the residual storage capacity greater than or equal to the data volume as the second database to be used according to a preset capacity expansion mechanism;

step a5, storing the target quota data packet in the second database to be used.

Optionally, after the step a5, the quota data transmitting method further comprises a step B1 and a step B2, wherein:

step B1, acquiring the attribute information of the target quota data packet and the address information of the second database required to be used;

and step B2, associating the attribute information of the target quota data packet with the address information of the second database which needs to be used, and storing the associated attribute information and address information into the first database.

Optionally, after the step B2, the quota data transmitting method further comprises a step C1, a step C2 or a step C3, wherein:

step C1, receiving an enabling instruction sent by the second server for the target quota packet, setting the state information of the target quota packet in the first database as an enabling state, and associating the state information with the attribute information of the target quota packet and the address information of the second database to be used; or

Step C2, receiving a disable instruction sent by the second server for the target quota packet, setting the status information of the target quota packet in the first database as a disable status, and associating the status information with the attribute information of the target quota packet and the address information of the second database to be used; or

Step C3, receiving a delete instruction sent by the second server for the target quota packet, setting the status information of the target quota packet in the first database as a delete status, associating the status information with the attribute information of the target quota packet and the address information of the second database to be used, and deleting the target quota packet in the second database to be used.

Optionally, before the step S1, the quota data transmitting method further comprises a step D1 and a step D2, wherein:

step D1, receiving the attribute request of the current available quota data packet sent by the client, and extracting the attribute information of the quota data packet with the state information of the enabled state from the first database;

and D2, generating a current available quota data packet attribute list according to the extracted attribute information, and returning the current available quota data packet attribute list to the client.

EXAMPLE III

The method for requesting rated data provided by the third embodiment is applied to the client, as shown in fig. 6, fig. 6 shows a flowchart of the method for requesting rated data provided by the third embodiment of the present invention, and the method for requesting rated data may include steps S1 'to S2', where:

step S1', generating a rating data request based on the attribute information and the identification information of the rating data;

step S2', sending the quota data request to a first server.

Optionally, the step S1 ' includes steps S11 ' to S13 ', wherein:

step S11', receiving a quota data insertion instruction;

step S12', parsing the quota data insertion instruction, and determining attribute information and identification information associated with the quota data insertion instruction;

step S13', the quota data request is generated according to the attribute information and the identification information associated with the quota data insertion instruction.

Optionally, the step of determining the attribute information and the identification information associated with the quota data insertion instruction in step S12 ' includes step S121 ' and step S122 ', in which:

step S121', obtaining identification information carried by the quota data insertion instruction as identification information associated with the quota data insertion instruction; as an example, the identification information comprises a unique identification of the rating data, by means of which the requested rating data can be accurately queried.

Step S122', obtaining the region information carried by the quota data insertion instruction, determining the type of the project file used for inserting the quota data, determining the version information of the quota data according to the type of the project file, and using the region information and the determined version information in the quota data insertion instruction as the attribute information associated with the quota data insertion instruction.

Step S121 'is for determining identification information, step S122' is for determining attribute information, the attribute information includes region information and version information, wherein, the identification information and the region information are both included in the quota data insertion instruction, so that the identification information and the region information can be directly obtained from the quota data insertion instruction, but at this time, the attribute information is not completely determined, it is necessary to further determine the type of the project file for inserting the quota data, determine the version information according to the type of the project file, and further use the region information and the version information as the attribute information.

Optionally, the step S122' of determining the version information of the quota data according to the type of the project file, and the step of using the region information and the determined version information in the quota data inserting instruction as the attribute information associated with the quota data inserting instruction includes steps E1 to E3, where:

step E1, when the type of the project file is a new type, determining the area information of the current available quota data packet matched with the area information in the quota data insertion instruction in the attribute list of the current available quota data packet, and acquiring the version information associated with the determined area information of the current available quota data packet;

step E2, determining the latest version information from the acquired version information;

step E3, the area information and the latest version information in the quota data insertion instruction are used as the attribute information associated with the quota data insertion instruction;

the attribute list of the current available quota data packet prestores area information and version information of the current available quota data packet associated with the first server, and the current available quota data packet comprises a quota data packet of which the state information is an enabled state.

Optionally, the step S122' of determining the version information of the quota data according to the type of the project file, and the step of using the region information and the determined version information in the quota data inserting instruction as the attribute information associated with the quota data inserting instruction includes steps F1 and F2, in which:

step F1, when the type of the project file is history type, determining the version information of the quota data packet used by the project file;

step F2, the version information and the area information in the rating data insertion instruction are used as the attribute information associated with the rating data insertion instruction.

Optionally, the step S2 ' includes steps S21 ' to S23 ', wherein:

step S21', judging whether the network is in the state of networking;

step S22', when the network is in the networking state, searching whether quota data is stored locally through a network engine interface, if so, acquiring the quota data locally, if not, sending the quota data request to the first server, receiving the quota data returned by the first server based on the quota data request, and caching the received quota data locally;

and step S23', when the network is not in the on-line state, searching whether quota data is stored locally through an off-line engine interface, if so, acquiring the quota data locally, and if not, displaying prompt information for prompting to request the network to acquire the quota data.

Example four

Fig. 7 shows a block diagram of a client according to a fourth embodiment of the present invention, and as shown in fig. 7, the client 700 includes a generating module 701 and a sending module 702, where:

a generating module 701, configured to generate a quota data request based on attribute information and identification information of quota data;

a sending module 702, configured to send the quota data request to a first server.

Optionally, the generating module is specifically configured to: receiving a quota data insertion instruction; analyzing the quota data insertion instruction, and determining attribute information and identification information associated with the quota data insertion instruction; and generating the quota data request according to the attribute information and the identification information associated with the quota data insertion instruction.

Optionally, the generating module, when executing the step of determining the attribute information and the identification information associated with the quota data insertion instruction, is specifically configured to: acquiring identification information carried by the quota data insertion instruction as identification information associated with the quota data insertion instruction; and acquiring the region information carried by the quota data insertion instruction, determining the type of the project file for inserting the quota data, and determining the attribute information associated with the quota data insertion instruction according to the region information in the quota data insertion instruction and the type of the project file.

Optionally, the generating module is configured to perform a step of determining attribute information associated with the quota data insertion instruction according to the area information in the quota data insertion instruction and the type of the project file, and specifically configured to: when the type of the engineering file is a new type, determining the region information of the current available quota data packet matched with the region information in the quota data insertion instruction in a current available quota data packet attribute list, and acquiring version information associated with the determined region information of the current available quota data packet; determining latest version information from the acquired version information; taking the region information and the latest version information in the quota data insertion instruction as attribute information associated with the quota data insertion instruction; the attribute list of the current available quota data packet prestores the region information and the version information of all current available quota data packets in the first server, and the current available quota data packet comprises a quota data packet of which the state information is an enabled state.

Optionally, when the step of determining the attribute information associated with the quota data insertion instruction according to the area information in the quota data insertion instruction and the type of the project file is executed by the generation module, the generation module is specifically configured to: when the type of the project file is a history type, determining the version information of a quota data packet used by the project file; and taking the version information and the region information in the quota data insertion instruction as attribute information associated with the quota data insertion instruction.

Optionally, when the step of sending the quota data request to the first server is executed by the sending module, the sending module is specifically configured to: judging whether the network is in a networking state at present; when the network is in a networking state, searching whether quota data are stored locally through a network engine interface, if so, acquiring the quota data locally, if not, sending the quota data request to the first server, receiving the quota data returned by the first server based on the quota data request, and caching the received quota data locally; and when the current state is not in a networking state, searching whether quota data are stored locally or not through an offline engine interface, if so, acquiring the quota data locally, and if not, displaying prompt information for prompting to request to network to acquire the quota data.

EXAMPLE five

Fig. 8 is a block diagram of a computer device suitable for implementing a quota data request method or a quota data transmission method according to a fifth embodiment of the present invention. When the computer device implements the quota data request method, the computer device may specifically be a client, specifically: a client comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor when executing the computer program implementing the quota data request method of embodiment three; when the computer device implements the quota data sending method, the computer device may specifically be a server, and specifically: a server comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor being configured to implement the quota data sending method of embodiment two when executing the computer program. In this embodiment, the computer device 800 may be a smart phone, a tablet computer, a notebook computer, a desktop computer, a rack server, a blade server, a tower server, or a rack server (including an independent server or a server cluster composed of a plurality of servers), and the like that execute programs. As shown in fig. 8, the computer device 800 of the present embodiment includes at least but is not limited to: a memory 801, a processor 802, a network interface 803, which may be communicatively coupled to each other via a system bus. It is noted that FIG. 8 only illustrates the computer device 800 having components 801 and 803, but it is to be understood that not all illustrated components need be implemented and that more or fewer components can alternatively be implemented.

In this embodiment, the memory 803 includes at least one type of computer-readable storage medium, which includes flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the storage 801 may be an internal storage unit of the computer device 800, such as a hard disk or a memory of the computer device 800. In other embodiments, the memory 801 may also be an external storage device of the computer device 800, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), etc. provided on the computer device 800. Of course, the memory 801 may also include both internal and external memory units to the computer device 800. In the present embodiment, the memory 801 is generally used to store an operating system and various types of application software installed in the computer apparatus 800, such as a program code of a rating data requesting method or a program code of a rating data transmitting method.

Processor 802 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments. The processor 802 generally operates to control the overall operation of the computer device 800. Such as performing control and processing related to data interaction or communication with computer device 800. In this embodiment, the processor 802 is configured to execute the program code of the rating data requesting method or the program code of the rating data transmitting method stored in the memory 801.

In this embodiment, the quota data request method or the quota data transmission method stored in the memory 801 may be further divided into one or more program modules and executed by one or more processors (in this embodiment, the processor 802) to complete the present invention.

The network interface 803 may include a wireless network interface or a wired network interface, and the network interface 803 is typically used to establish communications links between the computer device 800 and other computer devices. For example, the network interface 803 is used to connect the computer apparatus 800 with an external terminal via a network, establish a data transmission channel and a communication link between the computer apparatus 800 and the external terminal, and the like. The network may be a wireless or wired network such as an Intranet (Intranet), the Internet (Internet), a Global System of Mobile communication (GSM), Wideband Code Division Multiple Access (WCDMA), a 4G network, a 5G network, Bluetooth (Bluetooth), or Wi-Fi.

EXAMPLE six

The present embodiment also provides a computer-readable storage medium including a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, a server, an App application mall, etc., on which a computer program is stored, which when executed by a processor, implements the steps of a quota data request method or a quota data transmission method.

It will be apparent to those skilled in the art that the modules or steps of the embodiments of the invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, embodiments of the invention are not limited to any specific combination of hardware and software.

It should be noted that the numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner.

The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims

1. A method of quorum data request, the method comprising:

generating a rating data request based on attribute information and identification information of the rating data;

sending the quota data request to a first server.

2. The method of claim 1, wherein said attribute information is used to determine a target quota packet in said first server, and wherein said identification information is used to identify said quota data in said target quota packet.

3. The method according to claim 1 or 2, wherein the step of generating a rating data request based on attribute information and identification information of rating data comprises:

receiving a quota data insertion instruction;

analyzing the quota data insertion instruction, and determining attribute information and identification information associated with the quota data insertion instruction;

and generating the quota data request according to the attribute information and the identification information associated with the quota data insertion instruction.

4. The method of claim 3, wherein the step of determining attribute information and identification information associated with the quota data insertion instruction comprises:

acquiring identification information carried by the quota data insertion instruction as identification information associated with the quota data insertion instruction;

and acquiring the region information carried by the quota data insertion instruction, determining the type of the project file for inserting the quota data, determining the version information of the quota data according to the type of the project file, and taking the region information and the determined version information in the quota data insertion instruction as the attribute information associated with the quota data insertion instruction.

5. The method according to claim 4, wherein the step of determining version information of the rating data according to the type of the project file, and using the region information and the determined version information in the rating data insertion instruction as attribute information associated with the rating data insertion instruction comprises:

when the type of the engineering file is a new type, determining the region information of the current available quota data packet matched with the region information in the quota data insertion instruction in a current available quota data packet attribute list, and acquiring version information associated with the determined region information of the current available quota data packet;

determining latest version information from the acquired version information;

taking the region information and the latest version information in the quota data insertion instruction as attribute information associated with the quota data insertion instruction;

the attribute list of the current available quota data packet prestores the region information and the version information of all current available quota data packets in the first server, and the current available quota data packet comprises a quota data packet of which the state information is an enabled state.

6. The method according to claim 4, wherein the step of determining version information of the rating data according to the type of the project file, and using the region information and the determined version information in the rating data insertion instruction as attribute information associated with the rating data insertion instruction comprises:

when the type of the project file is a history type, determining the version information of a quota data packet used by the project file;

and taking the version information and the region information in the quota data insertion instruction as attribute information associated with the quota data insertion instruction.

7. The method of claim 1, wherein sending the quota data request to a first server comprises:

judging whether the network is in a networking state at present;

when the network is in a networking state, searching whether quota data are stored locally through a network engine interface, if so, acquiring the quota data locally, if not, sending the quota data request to the first server, receiving the quota data returned by the first server based on the quota data request, and caching the received quota data locally;

and when the current state is not in a networking state, searching whether quota data are stored locally or not through an offline engine interface, if so, acquiring the quota data locally, and if not, displaying prompt information for prompting to request to network to acquire the quota data.

8. A method for transmitting quota data, the method comprising:

receiving a quota data request sent by a client, wherein the quota data request carries attribute information and identification information of quota data;

and determining the quota data based on the attribute information and the identification information in the quota data request, and returning the quota data to the client.

9. The method of claim 8, wherein the step of determining the quota data based on the attribute information and the identification information in the quota data request comprises:

determining a target quota data packet according to the attribute information in the quota data request;

and identifying quota data pointed to by the identification information in the quota data request in the target quota data packet.

10. The method of claim 9, wherein the step of determining a target quota packet based on attribute information in the quota data request comprises:

determining attribute information of the quota data packet matched with the attribute information in the quota data request in a preset first database, and acquiring address information associated with the determined attribute information of the quota data packet;

determining a target database in all second databases for storing quota data packets according to the acquired address information;

searching the quota data packet related to the attribute information of the determined quota data packet in the target database to serve as the target quota data packet;

11. The method of claim 10, wherein the step of obtaining address information associated with the attribute information of the determined quota packet comprises:

acquiring state information associated with the attribute information of the determined quota data packet in the first database;

when the acquired state information is in a starting state, acquiring address information associated with the attribute information of the determined quota data packet;

when the acquired state information is in a forbidden state or a deleted state, generating prompt information for prompting that the request is invalid and returning the prompt information to the client;

12. The method of claim 9, wherein prior to the step of determining a target quota packet based on attribute information in the quota data request, the method further comprises:

receiving the target quota data packet uploaded by the second server;

determining the data amount of the target rated data packet and the remaining storage capacity of each second database for storing the rated data packet;

when a second database with the residual storage capacity larger than or equal to the data volume exists, taking any second database with the residual storage capacity larger than or equal to the data volume as a second database to be used, otherwise, generating a new database with the residual storage capacity larger than or equal to the data volume as the second database to be used according to a preset capacity expansion mechanism;

and storing the target quota data packet into the second database needing to be used.

13. The method of claim 12, wherein after the step of storing the target quota packet in the second database of required use, the method further comprises:

acquiring attribute information of the target quota data packet and address information of the second database required to be used;

and associating the attribute information of the target quota data packet with the address information of the second database required to be used, and storing the associated attribute information and address information into the first database.

14. The method according to claim 13, wherein after the step of associating the attribute information of the target quota packet with the address information of the second database to be used and storing the associated attribute information and address information in the first database, the method further comprises:

receiving an enabling instruction sent by the second server for the target quota data packet, setting the state information of the target quota data packet in the first database as an enabling state, and associating the state information with the attribute information of the target quota data packet and the address information of the second database required to be used; or

Receiving a disabling instruction sent by the second server for the target quota data packet, setting the state information of the target quota data packet in the first database as a disabling state, and associating the state information with the attribute information of the target quota data packet and the address information of the second database required to be used; or

Receiving a deletion instruction sent by the second server for the target quota data packet, setting the state information of the target quota data packet in the first database as a deletion state, associating the state information with the attribute information of the target quota data packet and the address information of the second database required to be used, and deleting the target quota data packet in the second database required to be used.

15. The method of claim 11, wherein prior to the step of receiving a request for quota data sent by a client, the method further comprises:

receiving a current available quota data packet attribute request sent by the client, and extracting attribute information of a quota data packet with state information in an enabling state from the first database;

and generating a current available quota data packet attribute list according to the extracted attribute information, and returning the current available quota data packet attribute list to the client.

16. A client, the client comprising:

the generation module is used for generating a quota data request based on the attribute information and the identification information of the quota data;

and the sending module is used for sending the quota data request to the first server.

17. A server, characterized in that the server comprises a memory, a processor and a computer program stored on the memory and executable on the processor, the processor being configured to implement the method of any of claims 8 to 15 when executing the computer program.

18. A quorum data management system, the system comprising a client, a first server, and a second server, wherein:

the client is used for executing the method of any one of claims 1-7;

the first server is configured to perform the method of any of claims 8-15;

the second server is used for uploading a target quota data packet to the first server, and sending an enabling instruction or a disabling instruction or a deleting instruction aiming at the target quota data packet to the first server after the uploading is completed.