CN113645289B

CN113645289B - Quota data request method, quota data transmission method, client, server and quota data transmission system

Info

Publication number: CN113645289B
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: 2024-12-17
Anticipated expiration: 2041-08-03
Also published as: CN113645289A

Abstract

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

Description

Quota data request method, quota data transmission method, client, server and quota data transmission 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

Quota data, which is one of the main bases for calculating engineering costs, is generally compiled by government authorities and published in book form by publishers, and mainly includes quota entries and compilation specifications. The pricing software is used as tool software for assisting in calculating engineering cost, and a software public can process the issued quota data into an electronic version to be packaged together with the pricing software, and then the electronic version is downloaded, installed and used by a user as a whole.

However, errors may exist in processing the rating data into electronic versions, and over time and market changes, the published rating data may no longer be accurate, and thus government authorities may publish policy files for revising the rating data. When the quota data is wrong or a new policy file is released by a government department, the software company can update the quota data at regular time, package and release the updated quota data together with the pricing software, and then download and install the quota data by the whole user, so that the user can use the updated quota data in the pricing software.

The inventor found that, in the prior art, when the quota data is updated, the user must re-download the installed software if using the new quota data, and then use the updated quota data. The whole operation flow is complex and occupies a large memory space, and no effective solution is provided at present for the problem.

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 rating data request method including generating a rating data request based on attribute information and identification information of rating data, and transmitting the rating data request to a first server.

Optionally, 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.

Optionally, the step of generating the quota data request based on the attribute information and the identification information of the quota data comprises the steps of receiving a quota data insertion instruction, analyzing the quota data insertion instruction, determining the attribute information and the 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 includes obtaining identification information carried by the quota data insertion instruction as identification information associated with the quota data insertion instruction, obtaining region information carried by the quota data insertion instruction, determining a type of an engineering file used for inserting the quota data, determining version information of the quota data according to the type of the engineering file, and taking the region information and the determined version information in the quota data insertion instruction as 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 engineering file, wherein the step of taking 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 comprises the steps of determining the region information of a current available quota data packet matched with the region information in the quota data inserting instruction in a current available quota data packet attribute list when the type of the engineering file is a new type, acquiring the version information associated with the determined region information of the current available quota data packet, determining the latest version information from the acquired version information, taking the region information and the latest version information in the quota data inserting instruction as the attribute information associated with the quota data inserting instruction, and storing the region information and the version information of all the current available quota data packets in the first server in advance, wherein the current available quota data packet comprises the quota data packet with state information of an enabled state.

Optionally, the step of determining the version information of the quota data according to the type of the engineering file, and taking the region information in the quota data inserting instruction and the determined version information as the attribute information associated with the quota data inserting instruction comprises determining the version information of the quota data packet used by the engineering file when the type of the engineering file is a history type, and taking the version information and the region information in the quota data inserting instruction as the attribute information associated with the quota data inserting instruction.

Optionally, the step of sending the quota data request to the first server includes judging whether the quota data is currently in a networking state or not, searching whether the quota data is locally stored through a network engine interface when the quota data is currently in the networking state, if so, obtaining 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, caching the received quota data locally, and if not, searching whether the quota data is locally stored through an offline engine interface, if so, obtaining the quota data locally, otherwise, displaying prompt information for prompting that the user is required to obtain the quota data through networking.

Another aspect of the present invention provides a quota data transmitting method, which includes receiving a quota data request sent by a client, where the quota data request carries attribute information and identification information of quota data, 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 the quota data pointed by the identification information in the quota data request in the target quota data packet.

Optionally, the step of determining the target quota data packet according to the attribute information in the quota data request comprises the steps of determining the attribute information of the quota data packet matched with the attribute information in the quota data request in a preset first database, acquiring address information related to the attribute information of the determined quota data packet, determining a target database in all second databases for storing the quota data packet according to the acquired address information, and 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, wherein the attribute information of the quota data packet and the address information of the second database are prestored in the first database.

Optionally, the step of acquiring address information associated with the attribute information of the determined rated data packet includes acquiring state information associated with the attribute information of the determined rated data packet in the first database, acquiring the address information associated with the attribute information of the determined rated data packet when the acquired state information is in an enabled state, generating prompt information for prompting that a request is invalid and returning to the client when the acquired state information is in a disabled state or a deleted state, wherein the first database is also prestored with state information for representing the current state of the rated data packet.

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

Optionally, after the step of storing the target quota packet in the second database to be used, the method further comprises obtaining attribute information of the target quota packet and address information of the second database to be used, 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.

Optionally, 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 the address information in the first database, the method further comprises the steps of 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, 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 receiving a disabling 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 a disabling 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, or receiving an 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 a deleting state, and deleting the target quota packet in the second database, and deleting the target quota packet in the required state, and deleting the target quota packet.

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

In yet another aspect, the invention provides a client comprising a generation module for generating a quota data request based on attribute information and identification information of the quota data, and a transmission module for transmitting the quota data request to a first server.

In yet another aspect, the present 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 quota data transmission method according to any of the embodiments described above when executing the computer program.

In a further aspect, the present invention provides a quota data management system, which includes a client, a first server, and a second server, where the client is configured to execute the quota data request method in any of the foregoing embodiments, the first server is configured to execute the quota data sending method in any of the foregoing embodiments, and the second server is configured to upload a target quota data packet to the first server, and send an enable instruction or a disable instruction or a delete instruction for the target quota data packet to the first server after the uploading is completed.

The application converts the quota data of the electronic edition into the quota data packet which can be directly called, and stores the quota data packet in the first server, when the client needs to load the quota data, the client does not need to download and install software as in the prior art, but directly requests to acquire the required quota data from the first server, and does not need to occupy the storage space of the client additionally. When the current quota data needs to be updated, only an engineer is required to upload the updated quota data package to the first server, and when the client needs to load the quota data, the latest quota data can be directly requested to the first server through preset logic, so that the updated quota installation package does not need to be downloaded and installed again like the prior art for a user, the whole operation flow is very simple, and the technical problems that the operation flow is complex and the storage space is large because the user needs to download the installation software in advance when using the quota data in the prior art are solved.

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 designate like parts throughout the figures. In the drawings:

FIG. 1 is a block diagram of a quorum data management system in accordance with a first embodiment of the present invention;

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

FIG. 3 is a schematic diagram illustrating a client operation flow provided in accordance with a first embodiment of the present invention;

FIG. 4 is a schematic diagram of a quota data management system provided in accordance with a first embodiment of the invention;

fig. 5 shows a flowchart of a quota data transmission method according to a second embodiment of the invention;

FIG. 6 is a flow chart of a quota data request method provided in a third embodiment of the 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 adapted to implement the quota data request method or the quota data transmission method according to the fifth embodiment of the invention.

Detailed Description

The present invention will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present invention more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the 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 one 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 provided in an embodiment of the 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 back-end server, and in order to facilitate understanding, in this embodiment, an interaction flow between 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:

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

After the paper quota is processed into electronic version data, the electronic version data can be converted into a format which can be read by the second server, namely a quota data packet. The quota data in the quota data package may include a quota entry and a formulation specification. In addition, the quota data packet may further include attribute information of the quota data packet itself, where the attribute information includes region information and version information, the region information is used to define a region range to which the quota data packet is applicable, for example, the quota data packet in the Beijing region is applicable to the Beijing full region, and the version information is used to define a version of the quota data packet. The rate packet of the same area information may have multiple versions, for example, when the rate packet needs to be updated, the second server generates a new version of the rate packet, so that the same area information may be associated with multiple versions of the information.

It should be noted that, the quota packet in this embodiment is different from the quota installation packet, and the quota installation packet may be used only after being locally installed, and the quota packet may be directly used without being installed.

The first server 101 is configured to receive the target quota packet uploaded by the second server 102, determine a data volume of the target quota packet and a remaining storage capacity of each second database for storing the quota packet, when the second database with the remaining storage capacity being greater than or equal to the data volume exists, use any second database with the remaining storage capacity being greater than or equal to the data volume as a second database to be used, when the second database with the remaining storage capacity being greater than or equal to the data volume does not exist, generate a new database with the remaining storage capacity being greater than or equal to the data volume according to a preset capacity expansion mechanism as a second database to be used, store the target quota packet into the second database to be used, acquire attribute information of the target quota packet and address information of the second database to be used, associate the attribute information of the target quota packet with the address information of the second database to be used, and store the associated attribute information into the second database.

In the first server, there are a plurality of database instances, each of which is referred to as a second database, each of which is referred to as a first database, and each of which is referred to as a second database, and in this embodiment there may be one second database or a plurality of second databases, and there may be one first database or a plurality of first databases. A plurality of quota data packages may be stored in each second database, and a plurality of index information may be stored in each first database. The index information is information that enables accurate positioning of a desired target quota packet. Each piece of index information in the present embodiment includes attribute information of a quota packet and address information of a second database storing the quota packet.

As shown in fig. 2, the database example 0 is a first database, the database examples 1-3 are respectively a second database, each second database stores a plurality of quota data packets, and each quota data packet stored in the second database may include quota data packets in different regions, and may also include quota data packets in different versions in the same region. Where V1 may represent version 1, V2 may represent version 2, and x may represent other versions, such as version 3, version 4.

According to the method, the device and the system, the quota data package is stored in a distributed database mode, the problem that a single database cannot be stored when the data volume is too large is effectively solved, and dynamic capacity expansion can be achieved when all second databases cannot store the quota data package. In addition, the relation between the quota data package and the second database is managed through the first database, so that the second database storing the required quota data package can be conveniently and quickly positioned, and the determination speed of the quota data is increased.

The second server 102 is further configured to send an enable instruction or a disable instruction or a delete instruction for the target quota packet to the first server 101 after the uploading of the target quota packet is completed.

The first server 101 is further configured to receive an enabling instruction sent by the second server 102 for the target quota packet, set state information of the target quota packet in the first database as an enabling state, and associate the state information with attribute information of the target quota packet and address information of the second database to be used, or receive an disabling instruction sent by the second server 102 for the target quota packet, set state information of the target quota packet in the first database as a disabling state, and associate the state information with attribute information of the target quota packet and address information of the second database to be used, or receive a deleting instruction sent by the second server 102 for the target quota packet, set state information of the target quota packet in the first database as a deleting state, associate the state information with attribute information of the target quota packet and address information of the second database to be used, and associate the state information with the second database to be used in the second database to be used.

The second server may display information that the target quota package has been uploaded on an operation interface, after which:

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

The second server may further send a disable instruction for the target quota packet to the first server, where the first server searches index information of the target quota packet in the first database according to the enable instruction, and then sets state information of the target quota packet in the index information to be in a disable state.

The second server may also send a deletion instruction for the target quota packet to the first server, where the first server searches index information of the target quota packet in the first database according to the enabling instruction, then sets state information of the target quota packet in the index information to be a deletion state, obtains address information from the index information, determines a second database pointed by the address information, and deletes the target quota 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 state information of the target quota packet is set for the first time (i.e., when the state information of the target quota packet does not exist in the first database), the setting in this embodiment is adding, i.e., adding the state information of the target quota database in the first database, and when the state information of the target quota packet is not set for the first time (i.e., when the state information of the target quota packet exists in the first database), only the state information of the target data packet needs to be changed to the state corresponding to the current instruction (e.g., the enabling instruction, the disabling instruction, or the deleting instruction).

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

When a user inserts rating data in an engineering file through a client (either rating software or a device in which the rating software is installed), the client may request the first server to obtain the rating data. First, the user will enable the rating software, then after the rating software is started, in order to avoid the defect that the rating data packet to which the subsequent requested rating data belongs is in a disabled state or a deleted state, which never causes a series of operations to be useless operations and is time-consuming and labor-consuming, the client will send a current available rating data packet attribute request to the first server, where the current available rating data packet attribute request is used to request to obtain a current available rating data packet attribute list, and the current available rating data packet attribute list includes area information and version information of the current available rating data packet associated with the first server, where the current available rating data packet is a rating data packet whose state information is in an enabled state, so as to try to ensure that the requested data is valid data.

The first server 101 is further configured to receive a current available quota packet attribute request sent by the client 103, extract attribute information of a quota packet with state information being an enabled state from the first database, generate a current available quota packet attribute list according to the extracted attribute information, and return the current available quota packet attribute list to the client.

The first server extracts the attribute information of all quota data packages with the state information being the enabling state in the first database, then stores the extracted attribute information in a data table to obtain a currently available quota data package attribute list, and further returns the currently available quota data package attribute list to the client.

The client 103 is further configured to receive the currently available quota packet attribute list returned by the first server 101, and store the currently available quota packet attribute list locally.

The client may store the list of currently available quota packet attributes in local memory, and may also store the list in local disk.

The client 103 is further configured to generate a quota data request based on the attribute information and the identification information of the quota data, and send the quota data request 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 includes a unique identification of the quota data by which the requested quota data can be accurately queried.

The client 103 is further configured to, when executing the step of generating the quota data request based on the attribute information and the identification information of the quota data, receive a quota data insertion instruction, parse the quota data insertion instruction, determine the attribute information and the identification information associated with the quota data insertion instruction, and generate the quota data request according to the attribute information and the identification information associated with the quota data insertion instruction.

The client 103 is further configured to obtain identification information carried by the quota data insertion instruction as identification information associated with the quota data insertion instruction, obtain region information carried by the quota data insertion instruction, determine a type of an engineering file used for inserting the quota data, determine version information of the quota data according to the type of the engineering file, and use the region information and the determined version information in the quota data insertion instruction as attribute information associated with the quota data insertion instruction when executing the step of determining the attribute information and the identification information associated with the quota data insertion instruction.

When determining the identification information and the attribute information, the client side can directly acquire the identification information and the area information from the quota data insertion instruction because the area information in the identification information and the attribute information are contained in the quota data insertion instruction, but the attribute information is not completely determined at the moment, so that the type of the engineering file for inserting the quota data can be further determined, version information in the attribute information is determined according to the type of the engineering file, and the area information and the version information are further used as the attribute information.

The client 103 is further configured to, when executing the step of determining version information of the quota data according to the type of the engineering file and taking the region information and the determined version information in the quota data insertion instruction as attribute information associated with the quota data insertion instruction, determine region information and version information of a current available quota data packet matching the region information in the quota data insertion instruction in a current available quota data packet attribute list when the type of the engineering file is a newly created type, and acquire version information associated with the determined region information of the current available quota data packet, determine latest version information from the acquired version information, and take the region information and the latest version information in the quota data insertion instruction as attribute information associated with the quota data insertion instruction, wherein the current available quota data packet attribute list pre-stores the region information and the version information of the current available quota data packet associated with the first server 101, and the current available quota data packet includes the quota data packet with state information of which is a state.

The client 103 is further configured to, when executing the step of determining version information of the quota data according to the type of the engineering file and using the region information in the quota data insertion instruction and the determined version information as attribute information associated with the quota data insertion instruction, determine version information of a quota data packet used by the engineering file when the type of the engineering file is a history type, and use 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 can be directly obtained 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 the quota data associated with the identification information may be identified from the corresponding quota data packet through the identification information.

The quota data insertion instruction also carries region information, and after the required version information is determined, the region information in the quota data insertion instruction and the required version information 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 for inserting the quota data. Specifically, if a user opens a history engineering file, the type of the engineering file (i.e. the history engineering file) used for inserting the quota data is a history type, the engineering file is historically associated with version information of a quota data packet used by the engineering file, at the moment, version information of the quota data packet associated with the engineering file is obtained directly according to an association relation, and if a user newly builds an engineering file, the type of the engineering file (i.e. the newly built engineering file) used for inserting the quota data is a new type, at the moment, the engineering file is not associated with any quota data packet, so that the required version information of the time can be determined according to a currently available quota data packet attribute list obtained by interacting with a first server, specifically, all version information associated with region information in a quota data insertion instruction is determined from the currently available quota data packet attribute list, and then the latest version information is determined from the version information as the required version information of the time. Further, the version information and the region information in the quota data insertion instruction finally determined by the A or the B are used as attribute information associated with the quota data insertion instruction.

The client 103 is further configured to determine whether the quota data is currently in a networking state when executing the step of sending the quota data request to the first server 101, search whether the quota data is locally stored through a network engine interface when the client is currently in the networking state, if yes, obtain the quota data locally, if not, send the quota data request to the first server, receive the quota data returned by the first server based on the quota data request, and cache the received quota data locally, and if not, search whether the quota data is locally stored through an offline engine interface, if yes, obtain the quota data locally, if not, display prompt information for prompting that the client requests to obtain the quota data in a networking mode.

The client side is provided with two engine interfaces in advance for flexibly acquiring the quota data, and determines from which engine interface the quota data is requested according to the current networking state. Specifically, as shown in fig. 3, the rating engine interface layer is invoked to determine whether the current network state is in the networking state, if the current network state is in the networking state, the network engine interface (i.e. the network version rating engine) is used for searching whether the requested rating data is locally stored, if the requested rating data is locally acquired, otherwise, the request of the rating data is directly sent to the second server (the cloud rating application service is a module in the second server) through the network, then the rating data returned by the second server is received through the network and is stored locally, if the current network state is not in the networking state, the offline engine interface (i.e. the local engine) is used for searching whether the requested rating data is locally cached, if the requested rating data is locally acquired, otherwise, prompt information for prompting the request of the network acquisition of the rating data is displayed. Optionally, the obtained quota data can be downloaded to the local cache, so that the quota data can be directly obtained from the local cache next time, and the effect of convenience and rapidness is achieved.

The first server 101 is further configured to receive a quota data request sent by a client 103, where the quota data request carries attribute information and identification information of the quota data, determine the requested quota data based on the attribute information and the identification information in the quota data request, and return 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 a first server, and the identification information is used for identifying the quota data in the target quota data packet.

The first server 101 is further configured to, when executing the step of determining the quota data based on the attribute information and the identification information in the quota data request, determine a target quota data packet according to the attribute information in the quota data request, and identify, in the target quota data packet, quota data to which the identification information in the quota data request is directed.

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 the client receives the quota data returned by the first server, the quota data is inserted into the engineering file, and the quota data is cached locally.

The first server 101 is further configured to determine, when executing the step of determining a target quota packet according to the attribute information in the quota data request, attribute information of the quota packet matching the attribute information in the quota data request in a preset first database, obtain address information associated with the determined attribute information of the quota packet, determine a target database in all second databases for storing the quota packet according to the obtained address information, and search the target database for the quota packet associated with the determined attribute information of the quota packet as the target quota packet, wherein the attribute information of the quota packet and the address information of the second database are prestored in the first 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, 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 the second database pointed by the address information as a target database, and the target database necessarily contains the quota data packet associated with 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 is further configured to, when executing the step of acquiring address information associated with the attribute information of the determined quota packet, acquire state information associated with the attribute information of the determined quota packet in the first database, acquire address information associated with the attribute information of the determined quota packet when the acquired state information is in an enabled state, generate prompt information for prompting that a request is invalid and return to the client when the acquired state information is in a disabled state or a deleted state, where state information for characterizing a current state of the quota packet is pre-stored in the first database.

In order to further ensure that the requested quota data is valid data and avoid useless operations, the second server may further determine state information associated with the attribute information of the quota data packet, 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 characterize that the quota data to be acquired is not available when the state information is in a disabled state or a deleted state, and at this time, the useless operation of acquiring the address information is not performed any more, 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 the interaction flow between the first server, the second server and the client, taking fig. 4 as an example.

The second server may include a library tool module and a publication management module. After the paper quota is processed into the electronic version data, the electronic version data can be converted into a format which can be read by a first server through a database-making tool module, namely a quota data packet. For ease of understanding, this embodiment takes a target quota packet as an example to describe the interaction flow among the client, the first server, and the second server in detail. Specifically, the release management module has an online release function, and the target quota data package can be uploaded to the first server through the release 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), then stores attribute information of the target quota data packet and address information of the second database required to be used in a management database (also called a first database), and can display that the uploading of the target quota data packet is completed on an operation interface of the second server. Further, the release management module is further provided with an enabling function, a disabling function and a deleting function, after the uploading of the target quota data packet is completed, the release management module can 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 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 attribute information of the target quota data packet stored in the first database and address information of a second database which corresponds to the required use.

Based on this, when a user inserts rating data (also referred to as rating data to be inserted) in an engineering file through rating software installed on the client, the client may request to obtain the rating data to be inserted from the first server. Specifically, after the pricing software is started, the client sends a request for attributes of currently available quota data packages to the first server, and the cloud quota application service of the first server responds to the request, gathers attribute information of all quota data packages with state information being enabled from the first database, and then stores the summarized attribute information in a data table and returns the data table to the client, wherein the data table after storing the attribute information is also called a currently available quota data package attribute list. The client receives the list and stores the list locally, and in response to a user-triggered quota data insertion instruction, 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 a quota data insertion instruction, invokes a quota engine interface layer to judge whether the client is in a networking state currently, searches whether the local area stores the quota data to be inserted through an offline engine interface if the client is not in the networking state, if the client is in the networking state, obtains the prompting information for prompting the client to acquire the quota data to be inserted through the networking, if the client is in the networking state, searches whether the local area stores the quota data to be inserted through the network engine interface, obtains the prompting information from the local area, otherwise sends the quota data request to a first server, analyzes the attribute information and the identification information carried by the request by a cloud quota application service of the first server, searches the attribute information of a quota data packet matched with the attribute information in the quota data request in the first database, judges the state information associated with the attribute information of the determined quota data packet, obtains address information associated with the attribute information of the determined quota data packet if the state information is in the enabling state, determines a second database pointed by the obtained address information to the target data, further obtains the target data packet, and sends the target data packet to the target data to be inserted into the target data packet, and the target data packet is extracted from the target data packet, and the target data packet is inserted into the target data packet, and the target data packet is extracted from the target data packet to be inserted into the target data packet.

The application converts the quota data of the electronic edition into the quota data packet which can be directly called, and stores the quota data packet in the first server, when the client needs to load the quota data, the client does not need to download and install software as in the prior art, but directly requests to acquire the required quota data from the first server, and does not need to occupy the storage space of the client additionally. When the current quota data needs to be updated, only an engineer is required to upload the updated quota data package to the first server, and when the client needs to load the quota data, the latest quota data can be directly requested to the first server through preset logic, so that the updated quota installation package does not need to be downloaded and installed again as in the prior art for a user, the whole operation flow is very simple, and the technical problems that the operation flow is complex and the storage space is large because the user needs to download and install the whole software by using the quota data in the prior art are solved.

Example two

The quota data transmission method provided in the second embodiment is applied to the first server, as shown in fig. 5, fig. 5 shows a flowchart of the quota data transmission method provided in the second embodiment of the invention, and the quota data determination 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;

and 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, step S3 includes step S31 to step S2, wherein:

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

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

Optionally, step S31 may include step S311 to step S313, where:

step S311, determining attribute information of a 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;

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

Step S313, searching the target database for a quota data packet associated with the attribute information of the determined quota data packet as the target quota data packet;

Wherein, the attribute information of the rated data packet and the address information of the second database are prestored in the first database.

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

step S3111, acquiring state information associated with the attribute information of the determined quota data package in the first database;

step S3112, when the acquired state information is an enabling state, acquiring address information associated with the determined attribute information of the quota data packet;

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

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

Optionally, before step S31, the sending of the quota data further includes step A1 to step A5, where:

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

Step A2, determining the data volume of the target quota data packet and the residual storage capacity of each second database for storing the quota data packet;

A3, when a second database with the residual storage capacity being more than or equal to the data volume exists, taking any second database with the residual storage capacity being more than or equal to the data volume as a second database to be used;

Step A4, 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 as a second database required to be used according to a preset capacity expansion mechanism;

and step A5, storing the target quota data packet into the second database required to be used.

Optionally, after step A5, the quota data transmission method further includes step B1 and step B2, wherein:

Step B1, obtaining attribute information of the target quota data packet and address information of the second database to be used;

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

Optionally, after step B2, the quota data transmission method further includes step C1, step C2, or step C3, wherein:

Step C1, 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 to be used, or

Step C2, 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 to be used, or

And C3, receiving a deleting instruction sent by the second server aiming at the target quota data packet, setting the state information of the target quota data packet in the first database as a deleting 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 step S1, the quota data transmission method further includes step D1 and step D2, where:

Step D1, 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 being an enabling state from the first database;

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

Example III

Fig. 6 shows a flowchart of a quota data request method provided in the third embodiment of the present invention, where the quota data request method may include steps S1 'to S2', where:

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

and step S2', the quota data request is sent to a first server.

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

Step S11', receiving a quota data insertion instruction;

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

And step S13', 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 in step S12' includes step S121' and step S122', wherein:

Step S121', the identification information carried by the quota data inserting instruction is obtained and used as the identification information associated with the quota data inserting instruction, and the identification information comprises a unique identifier of the quota data as an example, and the requested quota data can be accurately inquired through the unique identifier.

Step S122', the regional information carried by the quota data insertion instruction is obtained, the type of the engineering file used for inserting the quota data is determined, the version information of the quota data is determined according to the type of the engineering file, and the regional information in the quota data insertion instruction and the determined version information are used as attribute information associated with the quota data insertion instruction.

Step S121 'is used for determining identification information, and step S122' is used for determining attribute information, wherein the attribute information includes region information and version information, and 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 the attribute information is not completely determined at this time, the type of the engineering file for inserting the quota data needs to be further determined, the version information is determined according to the type of the engineering file, and the region information and the version information are further used as the attribute information.

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

e1, 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;

e2, determining the latest version information from the acquired version information;

e3, 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 currently available quota data packet prestores area information and version information of the currently available quota data packet associated with the first server, and the currently available quota data packet comprises a quota data packet with state information being in an enabling state.

Optionally, in step S122', the step of determining version information of the quota data according to the type of the engineering file, and taking the region information and the determined version information in the quota data insertion instruction as attribute information associated with the quota data insertion instruction includes step F1 and step F2, wherein:

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

And F2, 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, step S2' includes step S21' to step S23', wherein:

Step S21', judging whether the current state is in a networking state;

Step S22', when the network is in the networking state currently, searching whether the 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;

step S23', when the network is not in the current state, searching whether the quota data is stored locally through an offline engine interface, if so, obtaining the quota data locally, and if not, displaying prompt information for prompting that the network is requested to obtain the quota data.

Example IV

Fig. 7 shows a block diagram of a client provided by a fourth embodiment of the present invention, 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 the 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 receive a quota data insertion instruction, parse the quota data insertion instruction, determine attribute information and identification information associated with the quota data insertion instruction, and generate the quota data request according to the attribute information and the identification information associated with the quota data insertion instruction.

Optionally, the generating module is specifically configured to obtain identification information carried by the quota data inserting instruction as identification information associated with the quota data inserting instruction when executing the step of determining attribute information and identification information associated with the quota data inserting instruction, obtain region information carried by the quota data inserting instruction, determine a type of an engineering file for inserting the quota data, and determine attribute information associated with the quota data inserting instruction according to the region information in the quota data inserting instruction and the type of the engineering file.

Optionally, the generating module is used for determining the attribute information associated with the quota data inserting instruction according to the region information in the quota data inserting instruction and the type of the engineering file, and particularly used for determining the region information of the current available quota data packet matched with the region information in the quota data inserting instruction in a current available quota data packet attribute list when the type of the engineering file is a new type, acquiring version information associated with the determined region information of the current available quota data packet, determining the latest version information from the acquired version information, taking the region information in the quota data inserting instruction and the latest version information as the attribute information associated with the quota data inserting instruction, wherein the current available quota data packet attribute list 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 quota data packets with state information in an enabled state.

Optionally, the generating module is specifically configured to, when executing the step of determining the attribute information associated with the quota data inserting instruction according to the region information in the quota data inserting instruction and the type of the engineering file, determine version information of a quota data packet used by the engineering file when the type of the engineering file is a history type, and take the version information and the region information in the quota data inserting instruction as the attribute information associated with the quota data inserting instruction.

Optionally, the sending module is specifically configured to determine whether the quota data is currently in a networking state when the sending module performs the step of sending the quota data request to the first server, and search whether the quota data is locally stored through a network engine interface when the sending module is currently in the networking state, if yes, obtain the quota data locally, if not, send the quota data request to the first server, receive the quota data returned by the first server based on the quota data request, and buffer the received quota data locally, and if not, search whether the quota data is locally stored through an offline engine interface, if yes, obtain the quota data locally, and if not, display prompt information for prompting that the quota data is requested to be obtained in a networking mode.

Example five

Fig. 8 is a block diagram of a computer device adapted to implement the quota data request method or the quota data transmission method according to the fifth embodiment of the invention. The method for transmitting the quota data comprises the steps of storing a quota data in a memory, storing a processor and executing the computer program on the processor, wherein when the computer device realizes the quota data request method, the computer device can be a client, specifically a client comprises a memory, a processor and the computer program stored in the memory and capable of running on the processor, the processor is used for realizing the quota data request method of the third embodiment when executing the computer program, and when the computer device realizes the quota data transmission method, the computer device can be a server, specifically a server comprises a memory, a processor and the computer program stored in the memory and capable of running on the processor, and the processor is used for realizing the quota data transmission method of the second embodiment 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-mounted server, a blade server, a tower server, or a rack-mounted server (including a stand-alone server or a server cluster formed by a plurality of servers) for executing a program, etc. 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, and a network interface 803, which can be communicatively connected to each other through a system bus. It is noted that FIG. 8 only shows a computer device 800 having components 801-803, but it is understood that not all of the illustrated components are required to be implemented and that more or fewer components may be implemented instead.

In this embodiment, the memory 803 includes at least one type of computer-readable storage medium including flash memory, hard disk, multimedia card, card memory (e.g., SD or DX memory, etc.), random Access Memory (RAM), static Random Access Memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 801 may be an internal storage unit of the computer device 800, such as a hard disk or 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 provided on the computer device 800, a smart memory card (SMART MEDIA CARD, SMC), a Secure Digital (SD) card, a flash memory card (FLASH CARD), or the like. Of course, the memory 801 may also include both internal storage elements of the computer device 800 and external storage devices. 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 device 800, such as a program code of a quota data request method or a program code of a quota data transmission method.

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

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

The network interface 803 may include a wireless network interface or a wired network interface, the network interface 803 typically being used to establish a communication link between the computer device 800 and other computer devices. For example, the network interface 803 is used to connect the computer device 800 to an external terminal through a network, establish a data transmission channel and a communication link between the computer device 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 for mobile communications (Global System of Mobile communication, abbreviated as GSM), wideband code division multiple access (Wideband Code Division Multiple Access, abbreviated as WCDMA), a 4G network, a 5G network, bluetooth (Bluetooth), wi-Fi, etc.

Example six

The present embodiment also provides a computer-readable storage medium including a flash memory, a hard disk, a multimedia card, a card 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 store, 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 in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, they may alternatively be implemented in program code executable by computing devices, so that they may be stored in a storage device for execution by computing devices, and in some cases, the steps shown or described may be performed in a different order than what is shown or described, or they may be separately fabricated into individual integrated circuit modules, or a plurality of modules or steps in 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 embodiment numbers of the present invention are only for description, and do not represent the advantages and disadvantages of the embodiments.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment.

The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.

Claims

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

The method comprises the steps of sending a current available quota data packet attribute request to a first server, and receiving a current available quota data packet attribute list returned by the first server, wherein the current available quota data packet attribute list prestores area information and version information of all current available quota data packets in the first server, and the current available quota data packets comprise quota data packets with state information being an enabling state;

Generating a quota data request based on attribute information and identification information of the quota data, wherein the attribute information comprises the region information and the version information, 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 quota data request is sent to a first server.

2. The method of claim 1, wherein the step of generating the request for quota data based on the attribute information and the identification information of the quota 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.

3. The method of claim 2, 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;

The regional information carried by the quota data inserting instruction is obtained, the type of an engineering file used for inserting the quota data is determined, the version information of the quota data is determined according to the type of the engineering file, and the regional information and the determined version information in the quota data inserting instruction are used as attribute information associated with the quota data inserting instruction.

4. A method according to claim 3, 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 the 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 the latest version information from the acquired version information;

And 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.

5. A method according to claim 3, 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 history type, determining version information of a quota data packet used by the engineering 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.

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

judging whether the current state is in a networking state or not;

When the network is in a networking state currently, searching whether the quota data is stored locally through a network engine interface, if so, acquiring the quota data from the local, 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 in the local;

And when the network is not in the networking state currently, searching whether the quota data is locally stored or not through an offline engine interface, if so, obtaining the quota data locally, and if not, displaying prompt information for prompting that the network is requested to obtain the quota data.

7. A method of quota data transmission, the method comprising:

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

Generating a currently available quota data packet attribute list according to the extracted attribute information, and returning to the client;

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

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 step of determining the quota data based on the attribute information and the identification information in the quota data request includes:

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

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

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

Determining attribute information of a 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 rated data packets according to the acquired address information;

Searching a quota data packet associated with the attribute information of the determined quota data packet in the target database as the target quota data packet;

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

Acquiring state information associated with the attribute information of the determined quota data packet from the first database;

When the acquired state information is an enabling 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 to the client;

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

Receiving the target quota data packet uploaded by a second server;

determining the data amount of the target quota data package and the residual storage capacity of each second database for storing the quota data package;

When the second database with the residual storage capacity being more than or equal to the data volume exists, any second database with the residual storage capacity being more than or equal to the data volume is used as a second database to be used, otherwise, a new database with the residual storage capacity being more than or equal to the data volume is generated according to a preset capacity expansion mechanism to be used as the second database to be used;

And storing the target quota data packet into a second database required to be used.

11. The method of claim 10, wherein after the step of storing the target quota package in the second database of desired uses, the method further comprises:

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

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

12. The method according to claim 11, 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 state information of the target quota data packet in the first database as an enabling state, and associating the state information with attribute information of the target quota data packet and address information of the second database to be used, or

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

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

13. A client for implementing the method of any one of claims 1 to 6, the client comprising:

a generation module 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.

14. A server 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 being adapted to implement the method of any one of claims 7-12.

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

The client being adapted to perform the method of any of claims 1-6;

The first server being adapted to perform the method of any of claims 7-12;

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 for the target quota data packet to the first server after uploading is completed.