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

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

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a quota data request method, a quota data sending method, a client, a server and a quota data management system. Background Art

[0002] As one of the main bases for calculating engineering cost, quota data is generally compiled by government departments and published by publishers in the form of books, which mainly include quota items and compilation specifications. Pricing software is a tool software that assists in calculating engineering cost. Software companies will process the published quota data into an electronic version and package it together with the pricing software, and then users can download and install it as a whole.

[0003] However, there may be errors in the process of processing quota data into electronic version, and as time goes by and the market changes, the published quota data may no longer be accurate, so the government department will issue a policy document for revising the quota data. When there is an errata in the quota data or the government department issues a new policy document, the software company will update the quota data regularly and package the updated quota data and the pricing software together, and then the user will download and install it as a whole, so that the user can use the updated quota data in the pricing software.

[0004] The inventors have found that in the prior art, when the quota data is updated, if the user wants to use the new quota data, he must download and install the software again, and then use the updated quota data. The entire operation process is complicated and occupies a large storage space. There is currently no effective solution to this problem. Summary of the invention

[0005] The purpose of the present invention is 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 above technical problems.

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

[0007] 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.

[0008] Optionally, the step of generating a quota data request based on the attribute information and identification information of the quota data includes: receiving a quota data insertion instruction; parsing the quota data insertion instruction to determine the attribute information and identification information associated with the quota data insertion instruction; and generating the quota data request based on the attribute information and identification information associated with the quota data insertion instruction.

[0009] Optionally, the step of determining the attribute information and identification information associated with the quota data insertion instruction includes: obtaining the identification information carried by the quota data insertion instruction as the identification information associated with the quota data insertion instruction; obtaining the regional information carried by the quota data insertion instruction, and determining the type of engineering file used to insert the quota data, determining the version information of the quota data according to the type of the engineering file, and using the regional information and the determined version information in the quota data insertion instruction as the attribute information associated with the quota data insertion instruction.

[0010] Optionally, the step of determining version information of the quota data according to the type of the project file, and using the regional information in the quota data insertion instruction and the determined version information as attribute information associated with the quota data insertion instruction includes: when the type of the project file is a new type, in the attribute list of currently available quota data packets, determining the regional information of the currently available quota data packets that matches the regional information in the quota data insertion instruction, and obtaining version information associated with the determined regional information of the currently available quota data packets; determining the latest version information from the obtained version information; using the regional information in the quota data insertion instruction and the latest version information as attribute information associated with the quota data insertion instruction; wherein the attribute list of currently available quota data packets pre-stores the regional information and version information of all currently available quota data packets in the first server, and the currently available quota data packets include quota data packets whose status information is enabled.

[0011] Optionally, the step of determining version information of the quota data according to the type of the project file, and using the regional information in the quota data insertion instruction and the determined version information as attribute information associated with the quota data insertion instruction includes: when the type of the project file is a historical type, determining the version information of the quota data package used by the project file; and using the version information and the regional information in the quota data insertion instruction as attribute information associated with the quota data insertion instruction.

[0012] Optionally, the step of sending the quota data request to the first server includes: determining whether the server is currently in an online state; when the server is currently in an online state, searching through a network engine interface whether the quota data is stored locally, and 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, and caching the received quota data locally; when the server is currently not in an online state, searching through an offline engine interface whether the quota data is stored locally, and if so, obtaining the quota data locally; if not, displaying a prompt message prompting the server to connect to the Internet to obtain the quota data.

[0013] Another aspect of the present invention provides a quota data sending method, the method comprising: receiving a quota data request sent by a client, the quota data request carrying 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.

[0014] Optionally, the step of determining the quota data based on the attribute information and 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 in the target quota data packet the quota data pointed to by the identification information in the quota data request.

[0015] Optionally, the step of determining a target quota data packet based on the attribute information in the quota data request includes: determining the attribute information of a quota data packet that matches the attribute information in the quota data request in a preset first database, and obtaining address information associated with the attribute information of the determined quota data packet; determining a target database in all second databases used to store quota data packets based on the obtained address information; 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 quota data packet and the address information of the second database are pre-stored in the first database.

[0016] Optionally, the step of obtaining address information associated with the attribute information of the determined quota data packet includes: obtaining status information associated with the attribute information of the determined quota data packet in the first database; when the obtained status information is in an enabled state, obtaining address information associated with the attribute information of the determined quota data packet; when the obtained status information is in a disabled state or a deleted state, generating a prompt message indicating that the request is invalid and returning it to the client; wherein, the first database also pre-stores status information for characterizing the current state of the quota data packet.

[0017] Optionally, before the step of determining the target quota data packet according to the attribute information in the quota data request, the method also includes: receiving the target quota data packet uploaded by the second server; determining the data volume of the target quota data packet and the remaining storage capacity of each second database used to store the quota data packet; when there is a second database whose remaining storage capacity is greater than or equal to the data volume, using any second database whose remaining storage capacity is greater than or equal to the data volume as the second database to be used, otherwise generating a new database whose remaining storage capacity is greater than or equal to the data volume according to a preset expansion mechanism as the second database to be used; and storing the target quota data packet in the second database to be used.

[0018] Optionally, after the step of storing the target quota data packet in the second database to be used, the method further includes: obtaining attribute information of the target quota data packet and address information of the second database to be used; 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 in the first database.

[0019] Optionally, after the step of 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 in the first database, the method further includes: receiving an enable instruction sent by the second server for the target quota data packet, setting the status information of the target quota data packet to an enable state in the first database, and associating the status information with the attribute information of the target quota data packet and the address information of the second database to be used; or receiving a disable instruction sent by the second server for the target quota data packet, setting the status information of the target quota data packet to a disable state in the first database, and associating the status information with the attribute information of the target quota data packet and the address information of the second database to be used; or receiving a delete instruction sent by the second server for the target quota data packet, setting the status information of the target quota data packet to a delete state in the first database, associating the status information with the attribute information of the target quota data packet and the address information of the second database to be used, and deleting the target quota data packet from the second database to be used.

[0020] Optionally, before the step of receiving a quota data request sent by the client, the method further includes: receiving a request for attributes of a currently available quota data packet sent by the client, extracting attribute information of a quota data packet whose status information is enabled from the first database; generating a currently available quota data packet attribute list based on the extracted attribute information, and returning the list to the client.

[0021] Another aspect of the present invention provides a client, comprising: a generating module for generating a quota data request based on attribute information and identification information of the quota data; and a sending module for sending the quota data request to a first server.

[0022] Another aspect of the present invention provides a server, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the quota data sending method described in any of the above embodiments when executing the computer program.

[0023] Another aspect of the present invention provides a quota data management system, which includes a client, a first server and a second server, wherein: the client is used to execute the quota data request method described in any of the above embodiments; the first server is used to execute the quota data sending method described in any of the above embodiments; the second server is used to upload a target quota data packet to the first server, and after the uploading is completed, send an enable instruction, a disable instruction or a delete instruction for the target quota data packet to the first server.

[0024] This application converts the electronic version of quota data into a quota data package that can be directly called, and stores the quota data package in the first server. When the client needs to load quota data, it does not need to download and install software as in the prior art, but directly requests the required quota data from the first server, without occupying additional storage space on the client. And when the current quota data needs to be updated, the engineer only needs to upload the updated quota data package to the first server. When the client needs to load quota data, it can directly request the latest quota data from the first server through the preset logic. For users, there is no need to re-download and install the updated quota installation package as in the prior art. The entire operation process is very simple. This application solves the technical problem in the prior art that users must download and install software in advance to use quota data, which results in a complicated operation process and large storage space. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present invention. Moreover, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0026] Figure 1 A block diagram of a quota data management system provided by Embodiment 1 of the present invention is shown;

[0027] Figure 2 A schematic diagram showing the relationship between the first database and the second database provided in the first embodiment of the present invention;

[0028] Figure 3 A schematic diagram showing a client operation process provided by Embodiment 1 of the present invention;

[0029] Figure 4 A schematic diagram of a quota data management system provided by Embodiment 1 of the present invention is shown;

[0030] Figure 5 A flow chart of a quota data sending method provided by Embodiment 2 of the present invention is shown;

[0031] Figure 6 A flowchart of a quota data request method provided in Embodiment 3 of the present invention is shown;

[0032] Figure 7 A block diagram of a client provided by Embodiment 4 of the present invention is shown;

[0033] Figure 8 A block diagram of a computer device suitable for implementing a quota data request method or a quota data sending method provided in a fifth embodiment of the present invention is shown. DETAILED DESCRIPTION

[0034] In order to make the purpose, technical scheme and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0035] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0036] Figure 1 The block diagram of the quota data management system provided by the first embodiment of the present invention is shown. The quota data management system 100 may include a first server 101, a second server 102 and a client 103, wherein the first server 101 may be a cloud server, and the second server 102 may be a backend server. For ease of understanding, this embodiment takes a target quota data packet as an example to elaborate on the interaction process between the first server 101, the second server 102 and the client 103, specifically:

[0037] The second server 102 is used to upload a target quota data packet to the first server 101 .

[0038] After the paper quota book is processed into electronic data, the electronic data can be converted into a format that can be read by the second server, that is, a quota data packet. The quota data in the quota data packet may include quota items and compilation specifications. In addition, the quota data packet may also contain its own attribute information, which includes regional information and version information. The regional information is used to limit the regional scope to which the quota data packet is applicable. For example, the quota data packet in the Beijing area is applicable to the entire Beijing area, and the version information is used to limit the version of the quota data packet. Among them, the quota data packet of the same regional information may have multiple versions. For example, when the quota data packet needs to be updated, the second server will generate a new version of the quota data packet, so the same regional information can be associated with multiple version information.

[0039] 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 it can be used, while the quota data package can be used directly without installation.

[0040] The first server 101 is used to: receive the target quota data packet uploaded by the second server 102; determine the data volume of the target quota data packet and the remaining storage capacity of each second database used to store the quota data packet; when there is a second database whose remaining storage capacity is greater than or equal to the data volume, use any second database whose remaining storage capacity is greater than or equal to the data volume as the second database to be used; when there is no second database whose remaining storage capacity is greater than or equal to the data volume, generate a new database whose remaining storage capacity is greater than or equal to the data volume according to a preset expansion mechanism as the second database to be used; store the target quota data packet in the second database to be used; obtain the attribute information of the target quota data packet and the address information of the second database to be used; associate the attribute information of the target quota data packet with the address information of the second database to be used, and store the associated attribute information and address information in the first database.

[0041] There are multiple database instances in the first server, each database instance used to store a quota data packet is called a second database, and each database instance used to store index information is called a first database. In this embodiment, there can be one second database or multiple second databases, and there can be one first database or multiple first databases. Multiple quota data packets can be stored in each second database, and multiple index information can be stored in each first database. The so-called index information is information that can accurately locate the required target quota data packet. Each index information in this embodiment includes: attribute information of the quota data packet and address information of the second database storing the quota data packet.

[0042] like Figure 2 As shown, database instance 0 is the first database, and database instances 1-3 are second databases respectively. Each second database stores multiple quota data packages, and the quota data packages stored in each second database may include quota data packages of different regions, and may also include quota data packages of different versions in the same region. Among them, V1 can represent version 1, V2 can represent version 2, and * can represent other versions, such as version 3, version 4...

[0043] This embodiment stores quota data packets in a distributed database manner, effectively solving the problem that a single database cannot store data when the amount of data is too large, and can also achieve dynamic capacity expansion when all second databases cannot store quota data packets. In addition, by managing the relationship between quota data packets and second databases through the first database, it is easy to quickly locate the second database that stores the required quota data packets, thereby speeding up the determination of quota data.

[0044] The second server 102 is further configured to: after the target quota data packet is uploaded, send an enable instruction, a disable instruction, or a delete instruction for the target quota data packet to the first server 101 .

[0045] The first server 101 is also used to: receive an enable instruction sent by the second server 102 for the target quota data packet, set the status information of the target quota data packet to an enable state in the first database, and associate the status information with the attribute information of the target quota data packet and the address information of the second database to be used; or, receive a disable instruction sent by the second server 102 for the target quota data packet, set the status information of the target quota data packet to a disable state in the first database, and associate the status information with the attribute information of the target quota data packet and the address information of the second database to be used; or, receive a delete instruction sent by the second server 102 for the target quota data packet, set the status information of the target quota data packet to a delete state in the first database, associate the status information with the attribute information of the target quota data packet and the address information of the second database to be used, and delete the target quota data packet in the second database to be used.

[0046] The second server's operation interface will display a message that the target quota data package has been uploaded. After that:

[0047] The second server may send an activation instruction for the target quota data packet to the first server. The first server searches for index information of the target quota data packet in the first database according to the activation instruction, and then sets the status information of the target quota data packet in the index information to an activated state.

[0048] The second server may also send a disabling instruction for the target quota data packet to the first server. The first server searches the index information of the target quota data packet in the first database according to the enabling instruction, and then sets the status information of the target quota data packet to a disabled state in the index information.

[0049] The second server may also send a deletion instruction for the target quota data packet to the first server. The first server searches for the index information of the target quota data packet in the first database according to the activation instruction, and then sets the status information of the target quota data packet to a deletion status in the index information, obtains the address information from the index information, determines the second database pointed to by the address information, and then deletes the target quota data packet stored in the second database.

[0050] The above-mentioned status information is used to represent the current status of the target quota data packet.

[0051] It should be noted that, when the status information of the target quota data packet is set for the first time (that is, when the status information of the target quota data packet does not exist in the first database), the setting described in this embodiment is addition, that is, adding the status information of the target quota database in the first database; when it is not the first time to set the status information of the target quota data packet (that is, when the status information of the target quota data packet already exists in the first database), it is only necessary to change the status information of the target data packet to the status corresponding to this instruction (such as enable instruction, disable instruction or delete instruction).

[0052] The client 103 is used to send a currently available quota data packet attribute request to the first server 101 .

[0053] When the user inserts quota data into the project file through the client (which can be the pricing software or the device with the pricing software installed), the client can request the first server to obtain the quota data. First, the user will enable the pricing software, and then after the pricing software is started, in order to avoid the quota data package to which the subsequently requested quota data belongs being in a disabled state or a deleted state, thus never causing a series of operations to be useless and time-consuming and laborious, the client will send a currently available quota data package attribute request to the first server. The currently available quota data package attribute request is used to request to obtain a currently available quota data package attribute list. The currently available quota data package attribute list includes the region information and version information of the currently available quota data package associated with the first server. The currently available quota data package is a quota data package whose status information is enabled, thereby trying to ensure that the requested data is valid data.

[0054] The first server 101 is also used to: receive a request for attributes of currently available quota data packets sent by the client 103, extract attribute information of quota data packets whose status information is enabled in the first database; generate a list of attributes of currently available quota data packets based on the extracted attribute information, and return it to the client.

[0055] The first server extracts the attribute information of all quota database packages in the first database whose status information is enabled, and then stores the extracted attribute information in a data table, obtains a list of currently available quota data packages attributes, and further returns the list of currently available quota data packages attributes to the client.

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

[0057] The client may store the currently available quota data packet attribute list in local memory and may also store it in local disk.

[0058] The client 103 is further configured to: generate a quota data request based on the attribute information and identification information of the quota data; and send the quota data request to the first server 101 .

[0059] The attribute information is used to determine the 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. As an example, the identification information includes a unique identifier of the quota data, through which the requested quota data can be accurately queried.

[0060] When executing the step of generating a quota data request based on the attribute information and identification information of the quota data, the client 103 is also used to: receive a quota data insertion instruction; parse the quota data insertion instruction to determine the attribute information and identification information associated with the quota data insertion instruction; and generate the quota data request according to the attribute information and identification information associated with the quota data insertion instruction.

[0061] When executing the step of determining the attribute information and identification information associated with the quota data insertion instruction, the client 103 is also used to: obtain the identification information carried by the quota data insertion instruction as the identification information associated with the quota data insertion instruction; obtain the regional information carried by the quota data insertion instruction, and determine the type of engineering file used to insert the quota data, determine the version information of the quota data according to the type of the engineering file, and use the regional information and the determined version information in the quota data insertion instruction as the attribute information associated with the quota data insertion instruction.

[0062] When the client determines the identification information and attribute information, the regional information in the identification information and attribute information are all included in the quota data insertion instruction. Therefore, the identification information and regional information can be obtained directly from the quota data insertion instruction, but the attribute information has not been fully determined at this time. Therefore, the type of the project file used to insert the quota data can be further determined, and the version information in the attribute information can be determined according to the type of the project file, and then the regional information and version information can be used as attribute information.

[0063] When executing the step of determining the version information of the quota data according to the type of the project file, and using the regional information in the quota data insertion instruction and the determined version information as the attribute information associated with the quota data insertion instruction, the client 103 is also used to: when the type of the project file is a new type, determine the regional information of the currently available quota data packet that matches the regional information in the quota data insertion instruction in the currently available quota data packet attribute list, and obtain the version information associated with the determined regional information of the currently available quota data packet; determine the latest version information from the obtained version information; use the regional information in the quota data insertion instruction and the latest version information as the attribute information associated with the quota data insertion instruction; wherein the currently available quota data packet attribute list pre-stores the regional information and version information of the currently available quota data packet associated with the first server 101, and the currently available quota data packet includes a quota data packet whose status information is enabled.

[0064] When the client 103 executes the step of determining the version information of the quota data according to the type of the project file, and using the regional information in the quota data insertion instruction and the determined version information as the attribute information associated with the quota data insertion instruction, it is also used to: when the type of the project file is a historical type, determine the version information of the quota data package used by the project file; and use the version information and the regional information in the quota data insertion instruction as the attribute information associated with the quota data insertion instruction.

[0065] The quota data insertion instruction carries identification information, and the identification information can be directly obtained from the quota data insertion instruction as the identification information associated with the quota data insertion instruction. The identification information can be a quota data identifier, and the quota data associated with the identification information can be identified from the corresponding quota data packet through the identification information.

[0066] The quota data insertion instruction also carries the regional information. After determining the version information required this time, the regional information in the quota data insertion instruction and the version information required this time can be used as the attribute information associated with the quota data insertion instruction. In this embodiment, the version information required this time can be determined by the type of the engineering file used to insert the quota data. Specifically: A. If the user opens a historical engineering file, the type of the engineering file used to insert the quota data (that is, the historical engineering file) is a historical type. The engineering file has been historically associated with the version information of the quota data packet used by it. At this time, the version information of the quota data packet associated with the engineering file can be directly obtained according to the association relationship; B. If the user creates a new engineering file, the type of the engineering file used to insert the quota data (that is, the newly created engineering file) is a newly created type. At this time, the engineering file has not been associated with any quota data packet. Therefore, the version information required this time can be determined according to the current available quota data packet attribute list obtained by interacting with the first server before. Specifically, all version information associated with the regional information in the quota data insertion instruction is determined from the current available quota data packet attribute list, and then a latest version information is determined from these version information as the version information required this time. Furthermore, the version information finally determined by A or B and the region information in the quota data insertion instruction are used as attribute information associated with the quota data insertion instruction.

[0067] When executing the step of sending the quota data request to the first server 101, the client 103 is also used to: determine whether it is currently in an online state; when it is currently in an online state, search whether the quota data is stored locally through the network engine interface, if so, obtain the quota data from the local, 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; when it is not currently in an online state, search whether the quota data is stored locally through the offline engine interface, if so, obtain the quota data from the local, if not, display a prompt message for connecting to the Internet to obtain the quota data.

[0068] In order to flexibly obtain quota data, the client pre-sets two engine interfaces and determines which engine interface to request quota data from based on the current network status. Figure 3As shown, the quota engine interface layer is called to determine whether it is currently in an online state. If it is in an online state, the network engine interface (i.e., the network version of the quota engine) is used to find out whether the requested quota data is stored locally. If it is, it is obtained locally. Otherwise, the quota data request is directly sent to the second server (the cloud quota application service is a module in the second server) through the network, and then the quota data returned by the second server is received through the network and stored locally; if it is not in an online state, the offline engine interface (i.e., the local engine) is used to find out whether the quota data is cached locally. If it is obtained locally, otherwise, a prompt message is displayed to prompt you to go online to obtain the quota data. Optionally, the obtained quota data can be downloaded to the local cache, so the quota data can be directly obtained from the local cache next time, which is convenient and fast.

[0069] The first server 101 is also used to: receive a quota data request sent by the client 103; 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 identification information in the quota data request, and return the quota data to the client.

[0070] The quota data request carries attribute information and identification information, which can be obtained by parsing the quota data request. The attribute information is used to determine the 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.

[0071] When executing the step of determining the quota data based on the attribute information and identification information in the quota data request, the first server 101 is also used to: determine a target quota data packet based on the attribute information in the quota data request; and identify in the target quota data packet the quota data pointed to by the identification information in the quota data request.

[0072] The first server can determine a target quota data packet according to the attribute information in the quota data request, identify the quota data from the target quota data packet according to the identification information in the quota data request, and return the quota data to the client. It should be noted that after the client receives the quota data returned by the first server, it will insert the quota data into the project file and cache the quota data locally.

[0073] When executing the step of determining the target quota data packet according to the attribute information in the quota data request, the first server 101 is also used to: determine the attribute information of the quota data packet that matches the attribute information in the quota data request in a preset first database, and obtain address information associated with the attribute information of the determined quota data packet; determine a target database in all second databases used to store quota data packets according to the obtained address information; search in 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 quota data packet and the address information of the second database are pre-stored in the first database.

[0074] The first server traverses the first database, determines the attribute information of the quota data packet that matches the attribute information in the quota data request, and then filters out the index information containing the attribute information of the determined quota data packet from all the index information in the first database, obtains the address information contained in the filtered index information, and determines the second database pointed to by the address information as the target database. The target database must contain the quota data packet associated with the attribute information of the determined quota data packet, and the quota data packet can be used as the target quota data packet to be found.

[0075] When executing the step of obtaining the address information associated with the attribute information of the determined quota data packet, the first server 101 is also used to: obtain the status information associated with the attribute information of the determined quota data packet in the first database; when the obtained status information is in an enabled state, obtain the address information associated with the attribute information of the determined quota data packet; when the obtained status information is in a disabled state or a deleted state, generate a prompt message for indicating that the request is invalid and return it to the client; wherein, the first database also pre-stores status information for characterizing the current state of the quota data packet.

[0076] In order to further ensure that the requested quota data is valid data and avoid useless operations, the second server can also first determine the status information associated with the attribute information of the quota data packet, and only when the status information is enabled, further obtain the address information associated with the attribute information of the quota data packet; when the status information is disabled or deleted, it means that the quota data to be obtained is unavailable. At this time, the useless operation of obtaining the address information is no longer performed, but a prompt message for indicating that the request is invalid is directly generated and returned to the client, so that the client can make corresponding adjustments based on the prompt information.

[0077] Below Figure 4 Take the example to explain the interaction process between the first server, the second server and the client.

[0078] The second server may include a library tool module and a publishing management module. After the paper quota book is processed into electronic data, the electronic data can be converted into a format that can be read by the first server, that is, a quota data packet, through the library tool module. For ease of understanding, this embodiment takes a target quota data packet as an example to elaborate on the interaction process between the client, the first server and the second server. 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 referred to as the second database to be used), and then associates the attribute information of the target quota data packet with the address information of the second database to be used and stores it in a management database (also referred to as the first database). At this time, the operation interface of the second server can display that the target quota data packet has been uploaded. Furthermore, the publishing management module also has an enabling function, a disabling function and a deleting function. After the target quota data packet is uploaded, the publishing 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 instructions and adds status information in the first database to characterize that the current status of the target quota data packet is an enabling state, a disabling state or a deleting state, and then associates the status information with the attribute information of the target quota data packet stored in the first database and the address information of the corresponding second database to be used.

[0079] Based on this, when the user inserts quota data (also called quota data to be inserted) into the project file through the pricing software installed on the client, the client can request the first server to obtain the quota data to be inserted. Specifically, after starting the pricing software, the client will send a request for the attributes of the currently available quota data packet to the first server. The cloud quota application service of the first server responds to the request, summarizes the attribute information of all quota data packets whose status information is enabled from the first database, and then stores the summarized attribute information in a data table and returns it to the client, wherein the data table after storing these attribute information is also called the currently available quota data packet attribute list. The client receives the list and stores it locally, and in response to the quota data insertion instruction triggered by the user, determines the attribute information and identification information associated with the quota data insertion instruction. Furthermore, the client generates a quota data request through the attribute information and identification information associated with the quota data insertion instruction, and calls the quota engine interface layer to determine whether the client is currently connected to the Internet. If not, the offline engine interface is used to check whether the quota data to be inserted is stored locally. If so, it is obtained from the local area. Otherwise, a prompt message is displayed to prompt the client to connect to the Internet to obtain the quota data to be inserted. If connected to the Internet, the network engine interface is used to check whether the quota data to be inserted is stored locally. If so, it is obtained from the local area. Otherwise, the quota data request is sent to the first server. The cloud quota application service of the first server parses the attribute information and identification information carried by the request, and searches the first database for a quota that matches the attribute information in the quota data request. The attribute information of the quota data packet is determined, and the status information associated with the attribute information of the determined quota data packet is determined. If the status information is in the enabled state, the address information associated with the attribute information of the determined quota data packet is obtained, and the second database pointed to by the obtained address information is determined, which is recorded as the target database. Further, the quota data packet associated with the attribute information of the determined quota data packet is searched from the target database as the target quota data packet, and then the quota data pointed to by the identification information in the quota data request is extracted from the target quota data packet, and the extracted quota data is returned to the client as the quota data to be inserted, and the client stores the received quota data to be inserted locally, and inserts the received quota data to be inserted into the project file at the same time.

[0080] This application converts the electronic version of quota data into a quota data package that can be directly called, and stores the quota data package in the first server. When the client needs to load quota data, it does not need to download and install software as in the prior art, but directly requests the required quota data from the first server, without occupying additional storage space on the client. And when the current quota data needs to be updated, the engineer only needs to upload the updated quota data package to the first server. When the client needs to load quota data, it can directly request the latest quota data from the first server through the preset logic. For users, there is no need to re-download and install the updated quota installation package as in the prior art. The entire operation process is very simple. This application solves the technical problem in the prior art that users must download and install the entire software to use quota data, which results in a complicated operation process and a large amount of storage space.

[0081] Embodiment 2

[0082] The quota data sending method provided in the second embodiment is applied to the first server, such as Figure 5 As shown, Figure 5 The flowchart of the quota data sending method provided by the second embodiment of the present invention is shown. The quota data determination method may include steps S1 to S2, wherein:

[0083] Step S1, receiving a quota data request sent by a client, wherein the quota data request carries attribute information and identification information of the quota data;

[0084] Step S2: determining the requested quota data based on the attribute information and identification information in the quota data request, and returning the quota data to the client.

[0085] 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.

[0086] Optionally, step S3 includes steps S31 to S2, wherein:

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

[0088] Step S31, identifying the quota data pointed to by the identification information in the quota data request in the target quota data packet

[0089] Optionally, step S31 may include steps S311 to S313, wherein:

[0090] Step S311, determining the attribute information of the quota data packet that matches the attribute information in the quota data request in a preset first database, and acquiring the address information associated with the determined attribute information of the quota data packet;

[0091] Step S312, determining a target database from among all second databases used to store quota data packets according to the acquired address information;

[0092] 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;

[0093] The first database pre-stores attribute information of the quota data packet and address information of the second database.

[0094] Optionally, the step of acquiring the address information associated with the attribute information of the determined quota data packet in step S311 includes steps S3111 to S3113, wherein:

[0095] Step S3111, acquiring status information associated with the attribute information of the determined quota data packet in the first database;

[0096] Step S3112, when the acquired state information is in an enabled state, acquiring address information associated with the attribute information of the determined quota data packet;

[0097] Step S3113: when the acquired status information is a disabled status or a deleted status, a prompt message for prompting that the request is invalid is generated and returned to the client;

[0098] The first database also pre-stores status information for characterizing the current status of the quota data packet.

[0099] Optionally, before step S31, the quota data sending further includes steps A1 to A5, wherein:

[0100] Step A1, receiving the target quota data packet uploaded by the second server;

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

[0102] Step A3, when there is a second database whose remaining storage capacity is greater than or equal to the data amount, any second database whose remaining storage capacity is greater than or equal to the data amount is used as the second database to be used;

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

[0104] Step A5: storing the target quota data packet into the second database required for use.

[0105] Optionally, after step A5, the quota data sending method further includes steps B1 and B2, wherein:

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

[0107] 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 in the first database.

[0108] Optionally, after step B2, the quota data sending method further includes step C1, step C2 or step C3, wherein:

[0109] Step C1, receiving an activation instruction sent by the second server for the target quota data packet, setting the state information of the target quota data packet to an activation state in the first database, 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

[0110] Step C2, receiving a disabling instruction sent by the second server for the target quota data packet, setting the status information of the target quota data packet to a disabled state in the first database, and associating the status information with the attribute information of the target quota data packet and the address information of the second database to be used; or

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

[0112] Optionally, before step S1, the quota data sending method further includes step D1 and step D2, wherein:

[0113] Step D1, receiving a request for attributes of a currently available quota data packet sent by the client, and extracting attribute information of a quota data packet whose status information is an enabled status from the first database;

[0114] Step D2, generating a currently available quota data packet attribute list according to the extracted attribute information, and returning it to the client.

[0115] Embodiment 3

[0116] The quota data request method provided in the third embodiment is applied to the client. Figure 6 As shown, Figure 6 The flowchart of the quota data request method provided by the third embodiment of the present invention is shown. The quota data request method may include steps S1' to S2', wherein:

[0117] Step S1', generating a quota data request based on the attribute information and identification information of the quota data;

[0118] Step S2': sending the quota data request to the first server.

[0119] 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.

[0120] Optionally, step S1' includes steps S11' to S13', wherein:

[0121] Step S11', receiving a quota data insertion instruction;

[0122] Step S12', parsing the quota data insertion instruction, and determining the attribute information and identification information associated with the quota data insertion instruction;

[0123] Step S13': generating the quota data request according to the attribute information and identification information associated with the quota data insertion instruction.

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

[0125] 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 includes a unique identifier of the quota data, through which the requested quota data can be accurately queried.

[0126] Step S122', obtain the regional information carried by the quota data insertion instruction, and determine the type of engineering file used to insert the quota data, determine the version information of the quota data according to the type of engineering file, and use the regional information and the determined version information in the quota data insertion instruction as attribute information associated with the quota data insertion instruction.

[0127] Step S121' is used to determine the identification information, and step S122' is used to determine the attribute information, the attribute information including the region information and the version information, wherein the identification information and the region information are both included in the quota data insertion instruction, and therefore the identification information and the region information can be directly obtained from the quota data insertion instruction, but the attribute information has not been fully determined at this time, and it is necessary to further determine the type of the engineering file used to insert the quota data, and determine the version information based on the type of the engineering file, and then use the region information and version information as the attribute information.

[0128] Optionally, the step of determining the version information of the quota data according to the type of the project file in step S122', 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 includes steps E1 to E3, wherein:

[0129] Step E1, when the type of the project file is a new type, in the attribute list of the currently available quota data package, determining the region information of the currently available quota data package that matches the region information in the quota data insertion instruction, and obtaining the version information associated with the determined region information of the currently available quota data package;

[0130] Step E2, determining the latest version information from the acquired version information;

[0131] Step E3, using the region information and the latest version information in the quota data insertion instruction as attribute information associated with the quota data insertion instruction;

[0132] The currently available quota data package attribute list pre-stores the region information and version information of the currently available quota data packages associated with the first server, and the currently available quota data packages include quota data packages whose status information is enabled.

[0133] Optionally, the step of determining the version information of the quota data according to the type of the project file in step S122' 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 step F1 and step F2, wherein:

[0134] Step F1, when the type of the project file is a historical type, determining the version information of the quota data package used by the project file;

[0135] Step F2: Using the version information and the region information in the quota data insertion instruction as attribute information associated with the quota data insertion instruction.

[0136] Optionally, step S2' includes steps S21' to S23', wherein:

[0137] Step S21', determining whether the current state is connected to the Internet;

[0138] Step S22', when currently in a networked state, searching through a network engine interface whether the quota data is stored locally, 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, and caching the received quota data locally;

[0139] Step S23', when the network is not currently connected, check whether the quota data is stored locally through the offline engine interface, if so, obtain the quota data locally, if not, display a prompt message for connecting to the network to obtain the quota data.

[0140] Embodiment 4

[0141] Figure 7 A block diagram of a client provided by Embodiment 4 of the present invention is shown, Figure 7 As shown, the client 700 includes a generating module 701 and a sending module 702, wherein:

[0142] A generating module 701, for generating a quota data request based on the attribute information and identification information of the quota data;

[0143] The sending module 702 is used to send the quota data request to the first server.

[0144] 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.

[0145] Optionally, the generation module is specifically used to: receive a quota data insertion instruction; parse the quota data insertion instruction to 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 identification information associated with the quota data insertion instruction.

[0146] It can be selected that when the generation module executes the step of determining the attribute information and identification information associated with the quota data insertion instruction, it is specifically used to: obtain the identification information carried by the quota data insertion instruction as the identification information associated with the quota data insertion instruction; obtain the regional information carried by the quota data insertion instruction, and determine the type of engineering file used to insert the quota data, and determine the attribute information associated with the quota data insertion instruction based on the regional information in the quota data insertion instruction and the type of the engineering file.

[0147] Optionally, the generation module, when executing the step of determining the attribute information associated with the quota data insertion instruction according to the regional information in the quota data insertion instruction and the type of the project file, is specifically used for: when the type of the project file is a new type, determining the regional information of the currently available quota data packet that matches the regional information in the quota data insertion instruction in the attribute list of the currently available quota data packet, and obtaining the version information associated with the determined regional information of the currently available quota data packet; determining the latest version information from the obtained version information; using the regional information in the quota data insertion instruction and the latest version information as the attribute information associated with the quota data insertion instruction; wherein the attribute list of the currently available quota data packet pre-stores the regional information and version information of all currently available quota data packets in the first server, and the currently available quota data packets include quota data packets whose status information is enabled.

[0148] Optionally, when the generation module executes the step of determining the attribute information associated with the quota data insertion instruction based on the regional information in the quota data insertion instruction and the type of the project file, it is specifically used to: when the type of the project file is a historical type, determine the version information of the quota data package used by the project file; and use the version information and the regional information in the quota data insertion instruction as the attribute information associated with the quota data insertion instruction.

[0149] Optionally, when the sending module executes the step of sending the quota data request to the first server, it is specifically used to: determine whether it is currently in an online state; when it is currently in an online state, search whether the quota data is stored locally through the network engine interface, and if so, obtain the quota data from the local; 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; when it is not currently in an online state, search whether the quota data is stored locally through the offline engine interface, and if so, obtain the quota data from the local; if not, display a prompt message for connecting to the Internet to obtain the quota data.

[0150] Embodiment 5

[0151] Figure 8 A block diagram of a computer device suitable for implementing a quota data request method or a quota data sending method provided in Embodiment 5 of the present invention is shown. Wherein, when the computer device implements the quota data request method, the computer device may specifically be a client, specifically: a client, including a memory, a processor, and a computer program stored on the memory and executable on the processor, and the processor is used to implement the quota data request method described in Embodiment 3 when executing the computer program; when the computer device implements the quota data sending method, the computer device may specifically be a server, specifically: a server, including a memory, a processor, and a computer program stored on the memory and executable on the processor, and the processor is used to implement the quota data sending method described in Embodiment 2 when executing the computer program. In this embodiment, the computer device 800 may be a smart phone, a tablet computer, a laptop computer, a desktop computer, a rack server, a blade server, a tower server, or a cabinet server (including an independent server, or a server cluster composed of multiple servers), etc. that executes the program. Figure 8 As shown, the computer device 800 of this embodiment includes at least but is not limited to: a memory 801, a processor 802, and a network interface 803 that can be interconnected through a system bus. It should be noted that Figure 8 Only a computer device 800 having components 801 - 803 is shown, but it should be understood that implementing all of the components shown is not a requirement, and more or fewer components may alternatively be implemented.

[0152] In this embodiment, the memory 803 includes at least one type of computer-readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, 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 can 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 can also be an external storage device of the computer device 800, such as a plug-in hard disk equipped on the computer device 800, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. Of course, the memory 801 can also include both the internal storage unit of the computer device 800 and its external storage device. In this embodiment, the memory 801 is generally used to store an operating system and various application software installed in the computer device 800, such as program codes of a quota data request method or a quota data sending method.

[0153] In some embodiments, the processor 802 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips. The processor 802 is generally used to control the overall operation of the computer device 800. For example, the processor 802 performs control and processing related to data interaction or communication with the computer device 800. In this embodiment, the processor 802 is used to run the program code of the quota data request method or the program code of the quota data sending method stored in the memory 801.

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

[0155] The network interface 803 may include a wireless network interface or a wired network interface, and the network interface 803 is generally 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, and to establish a data transmission channel and a communication link between the computer device 800 and the external terminal. The network may be a wireless or wired network such as an intranet, the Internet, the Global System of Mobile communication (GSM), Wideband Code Division Multiple Access (WCDMA), 4G network, 5G network, Bluetooth, Wi-Fi, etc.

[0156] Embodiment 6

[0157] This embodiment also provides a computer-readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (for example, 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, disk, optical disk, server, App application store, etc., on which a computer program is stored, and when the computer program is executed by a processor, the steps of the quota data request method or the quota data sending method are implemented.

[0158] Obviously, those skilled in the art should understand that the modules or steps of the above-mentioned embodiments of the present invention can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, and optionally, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order from that here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. In this way, the embodiments of the present invention are not limited to any specific combination of hardware and software.

[0159] It should be noted that the serial numbers of the embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0160] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method.

[0161] The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A quota data request method, characterized in that: The method comprises: Sending a currently available quota data packet attribute request to the first server, and receiving a currently available quota data packet attribute list returned by the first server; the currently available quota data packet attribute list pre-stores the region information and version information of all currently available quota data packets in the first server, and the currently available quota data packets include quota data packets whose status information is enabled; generating a quota data request based on attribute information and identification information of the quota data; the attribute information includes the region information and the version information; 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; The quota data request is sent to the first server.

2. The method according to claim 1, characterized in that The step of generating a quota data request based on the attribute information and identification information of the quota data comprises: Receive quota data insertion instructions; parsing the quota data insertion instruction to determine attribute information and identification information associated with the quota data insertion instruction; The quota data request is generated according to the attribute information and identification information associated with the quota data insertion instruction.

3. The method according to claim 2, characterized in that The step of determining the attribute information and identification information associated with the quota data insertion instruction comprises: Acquire identification information carried by the quota data insertion instruction as identification information associated with the quota data insertion instruction; Acquire the regional information carried by the quota data insertion instruction, and determine the type of the engineering file used to insert the quota data, determine the version information of the quota data according to the type of the engineering file, and use the regional information and the determined version information in the quota data insertion instruction as attribute information associated with the quota data insertion instruction.

4. The method according to claim 3, characterized in that 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 comprises: When the type of the project file is a new type, in the attribute list of the currently available quota data package, the regional information of the currently available quota data package matching the regional information in the quota data insert instruction is determined, and the version information associated with the determined regional information of the currently available quota data package is obtained; Determine the latest version information from the obtained version information; The region information and the latest version information in the quota data insertion instruction are used as attribute information associated with the quota data insertion instruction.

5. The method according to claim 3, characterized in that: 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 comprises: When the type of the engineering file is a historical type, determining version information of the quota data package used by the engineering file; The version information and the region information in the quota data insertion instruction are used as attribute information associated with the quota data insertion instruction.

6. The method according to claim 1, characterized in that The step of sending the quota data request to the first server comprises: Determine whether the network is currently connected; When currently in a networked state, searching through a network engine interface whether the quota data is stored locally, 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, and caching the received quota data locally; When the network is not currently connected, the offline engine interface is used to check whether the quota data is stored locally. If so, the quota data is obtained locally. If not, a prompt message is displayed to prompt the user to connect to the network to obtain the quota data.

7. A quota data sending method, characterized in that: The method comprises: receiving a currently available quota data packet attribute request sent by a client, and extracting attribute information of the quota data packet whose status information is an enabled status from a first database; Generate a currently available quota data packet attribute list according to the extracted attribute information, and return it to the client; receiving a quota data request sent by a client, wherein the quota data request carries 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 step of determining the quota data based on the attribute information and identification information in the quota data request comprises: Determine a target quota data packet according to the attribute information in the quota data request; The quota data pointed to by the identification information in the quota data request is identified in the target quota data packet.

8. The method according to claim 7, characterized in that The step of determining the target quota data packet according to the attribute information in the quota data request comprises: Determining in a preset first database the attribute information of the quota data packet that matches the attribute information in the quota data request, and acquiring address information associated with the determined attribute information of the quota data packet; Determining a target database among all second databases used to store quota data packets according to the acquired address information; 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; The first database pre-stores attribute information of the quota data packet and address information of the second database.

9. The method according to claim 8, characterized in that The step of obtaining the address information associated with the attribute information of the determined quota data packet includes: Acquiring, in the first database, state information associated with attribute information of the determined quota data packet; When the acquired state information is in an enabled state, acquiring address information associated with the attribute information of the determined quota data packet; When the acquired status information is 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; The first database also pre-stores status information for characterizing the current status of the quota data packet.

10. The method according to claim 7, characterized in that Before the step of determining the target quota data packet according to the attribute information in the quota data request, the method further includes: receiving the target quota data packet uploaded by the second server; Determining the data volume of the target quota data packet and the remaining storage capacity of each second database for storing the quota data packet; When there is a second database with a remaining storage capacity greater than or equal to the data volume, any second database with a remaining storage capacity greater than or equal to the data volume is used as the second database to be used; otherwise, a new database with a remaining storage capacity greater than or equal to the data volume is generated according to a preset expansion mechanism as the second database to be used; The target quota data packet is stored in the second database required for use.

11. The method according to claim 10, characterized in that After the step of storing the target quota data packet in the second database required for use, the method further includes: Acquire the attribute information of the target quota data packet and the address information of the second database to be used; The attribute information of the target quota data packet is associated with the address information of the second database to be used, and the associated attribute information and address information are stored in the first database.

12. The method according to claim 11, characterized in that After the step of 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 in the first database, the method further includes: receiving an activation instruction sent by the second server for the target quota data packet, setting the state information of the target quota data packet to an activation state in the first database, 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 receiving a disabling instruction sent by the second server for the target quota data packet, setting the status information of the target quota data packet to a disabled state in the first database, and associating the status information with the attribute information of the target quota data packet and the address information of the second database to be used; or Receive a deletion instruction sent by the second server for the target quota data packet, set the status information of the target quota data packet to a deletion status in the first database, associate the status information with the attribute information of the target quota data packet and the address information of the second database to be used, and delete the target quota data packet in the second database to be used.

13. A client for implementing the method according to any one of claims 1 to 6, characterized in that: The client comprises: A generating module, used for generating a quota data request based on the attribute information and identification information of the quota data; A sending module is used to send the quota data request to the first server.

14. A server, characterized in that: The server includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor is used to implement the method according to any one of claims 7 to 12 when executing the computer program.

15. A quota data management system, characterized in that: The system comprises a client, a first server and a second server, wherein: The client is used to execute the method according to any one of claims 1 to 6; The first server is used to execute the method according to any one of claims 7 to 12; The second server is used to upload the target quota data packet to the first server, and send an enable instruction, a disable instruction, or a delete instruction for the target quota data packet to the first server after the uploading is completed.

Images