Service information processing method, device and equipment

Abstract

The invention provides a business information processing method, device and equipment. The business information processing method comprises the following steps: receiving a to-be-uploaded business file in a target business service sent by a client; storing the service file, determining a first file identifier of the service file, and returning the first file identifier to the client; a second file identifier sent by the storage service in response to the service data submission request is received, the service data submission request is a request sent by the client to the storage service and used for storing service data related to the service file, and the service data submission request comprises the service data and the second file identifier of the service file; verifying the second file identifier according to the first file identifier to obtain a file identifier verification result; and returning the file identification verification result to the storage service, so that the storage service determines whether to store the business data according to the file identification result, thereby reducing the development cost of the information processing interface and improving the information processing efficiency.

Description

Technical Field

[0001] The embodiments of the present application relate to the technical field of data processing, and in particular, to a method, device, and equipment for processing service information. Background Art

[0002] Currently, an application can provide multiple service services, and each service service generally involves the processing of service information. For example, for a financial type of application, it can provide service services such as account opening registration service under financial market 1, order placement service under financial market 1, and account registration service under financial market 2. The completion of these service services all involves the upload or submission of service information such as service files and service materials.

[0003] However, in the related service information processing solution, generally, independent service information upload and download interfaces need to be provided for each service service. Therefore, every time a new service service appears, additional development of service information upload and download interfaces is required, resulting in waste of development resources and untimely information processing. Summary of the Invention

[0004] The present application provides a method, device, and equipment for processing service information, which can reduce the development cost of information processing interfaces and improve information processing efficiency.

[0005] In a first aspect, the present application provides a method for processing service information, including: receiving a service file to be uploaded in a target service service sent by a client; saving the service file, determining a first file identifier of the service file, and returning the first file identifier to the client; receiving a second file identifier sent by a storage service in response to a service material submission request, where the service material submission request is a request sent by the client to the storage service for storing service materials related to the service file, and the service material submission request includes service materials and a second file identifier of the service file; verifying the second file identifier according to the first file identifier to obtain a file identifier verification result; returning the file identifier verification result to the storage service so that the storage service determines whether to store the service materials according to the file identifier result.

[0006] In a second aspect, the present application provides a service information processing device, including: a file receiving module, configured to receive a service file to be uploaded in a target service sent by a client; a file uploading module, configured to save the service file, determine a first file identifier of the service file, and return the first file identifier to the client; an identifier receiving module, configured to receive a second file identifier sent by a storage service in response to a service data submission request, where the service data submission request is a request sent by the client to the storage service for storing service data related to the service file, and the service data submission request includes service data and the second file identifier of the service file; an identifier verification module, configured to verify the second file identifier according to the first file identifier to obtain a file identifier verification result; and a result returning module, configured to return the file identifier verification result to the storage service, so that the storage service determines whether to store the service data according to the file identifier result.

[0007] In a third aspect, the present application provides an electronic device, including: a processor and a memory, where the memory is configured to store a computer program, and the processor is configured to call and run the computer program stored in the memory to execute the method in the first aspect or its various implementation manners.

[0008] In a fourth aspect, the present application provides a computer-readable storage medium for storing a computer program, where the computer program causes a computer to execute the method in the first aspect or its various implementation manners.

[0009] In a fifth aspect, the present application provides a computer program product, including computer program instructions, where the computer program instructions cause a computer to execute the method in the first aspect or its various implementation manners.

[0010] In a sixth aspect, the present application provides a computer program, where the computer program causes a computer to execute the method in the first aspect or its various implementation manners.

[0011] Through the technical solution of the present application, a general uploading or saving service can be provided for each service file and service data, thereby avoiding waste of development resources and problems of untimely information processing, reducing the development cost of information processing interfaces, and improving information processing efficiency. At the same time, it is also possible to determine whether to store service data by verifying file identifiers, improving the accuracy and security of service information processing. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The following introduces the drawings required for the description of the embodiments.

[0013] Figure 1 FIG. is a schematic diagram of an application scenario provided by an embodiment of the present application;

[0014] Figure 2Flowchart of a business information processing method provided by an embodiment of the present application;

[0015] Figure 3 Schematic diagram of a business information processing method provided by an embodiment of the present application;

[0016] Figure 4 Schematic diagram of another business information processing method provided by an embodiment of the present application;

[0017] Figure 5 Schematic diagram of yet another business information processing method provided by an embodiment of the present application;

[0018] Figure 6 Schematic diagram of yet another business information processing method provided by an embodiment of the present application;

[0019] Figure 7 Schematic diagram of yet another business information processing method provided by an embodiment of the present application;

[0020] Figure 8 Schematic diagram of yet another business information processing method provided by an embodiment of the present application;

[0021] Figure 9 Schematic diagram of a business information processing device 900 provided by an embodiment of the present application;

[0022] Figure 10 Schematic diagram of an electronic device 1000 provided by an embodiment of the present application. Detailed implementation manners

[0023] It should be noted that the terms "first", "second", etc. in the specification, claims and drawings of the present application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that such used data can be interchanged under appropriate circumstances so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or server including a series of steps or units is not necessarily limited to those clearly listed steps or units, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0024] It should be understood that the technical solution of the present application can be applied to the following scenarios, but is not limited to:

[0025] In one embodiment, the present application can be applied to the scenario of uploading or saving business information, and specifically can be applied to the scenario of saving business files, business materials, etc.

[0026] For example, it can be applied to the scenario of uploading business documents and materials when a user opens an account based on a client.

[0027] In one embodiment, as Figure 1 shown, this application scenario may include a terminal device 110 and a server 120. The terminal device 110 and the server 120 can be connected via a wired network or a wireless network.

[0028] Exemplarily, a user can select a business document to be uploaded based on the client installed on the terminal device 110. The client can obtain the business document and send it to the server 120; the server 120 can receive the business document and save it, and at the same time generate a unique identifier for the business document: the first file identifier, and return the first file identifier to the client; then, the client can determine a request for storing the business materials according to the first file identifier and the business materials filled in by the user related to the business document, and send the request to the storage service; the storage service can send the file identifier in the request to the server 120; the server 120 can verify the file identifier sent by the storage service according to the above-generated first file identifier, and send the verification result to the storage service, so that the storage service can determine whether to store the business materials according to the verification result.

[0029] Among them, the server 120 can be a single server, or a server cluster composed of multiple servers, or a cloud platform control center, but not limited thereto. The investor terminal device 110 or the custodian terminal device 130 can be a mobile phone, a tablet computer, a laptop computer or a desktop computer, etc., but not limited thereto. The storage service can be a unit of the server 120, or other servers similar to the server 120.

[0030] It should be noted that Figure 1 the terminal device and the server in

[0031] are only exemplary. Specifically, it may also include other quantities or types of terminal devices or servers.

[0032] Figure 2 is a flowchart of a business information processing method provided by an embodiment of the present application. This method can be executed by the server 120 in the above application scenario, but not limited thereto. As Figure 2 shown, this method may include the following steps:

[0033] S210: Receive a business document to be uploaded in a target business service sent by a client;

[0034] S220: Save the business document, determine the first document identifier of the business document, and return the first document identifier to the client;

[0035] S230: Receive the second document identifier sent by the storage service in response to the business data submission request. The business data submission request is a request sent by the client to the storage service for storing business data related to the business document, including the business data and the second document identifier of the business document;

[0036] S240: Verify the second document identifier according to the first document identifier to obtain a document identifier verification result;

[0037] S250: Return the document identifier verification result to the storage service so that the storage service can determine whether to store the business data according to the document identifier result.

[0038] It should be noted that both the business data and the business document belong to business information. Among them, the business document is business information in file format, for example, word file, xsls file or pdf file; the business data is generally business information in formats such as characters, arrays, charts, etc.

[0039] The business data and the business document can be related. Specifically, the business data and the business document can be business information under the same business service, that is, the target business service. For example, assuming the business service is an account opening service, the business document can be a company opening document, such as a company registration certificate, etc., and the business data can include basic company information such as company name, registered address, etc., and basic information of the person in charge such as name and contact information of the person in charge.

[0040] In one embodiment, assuming the target business service is an account opening service, as Figure 3 shown, the user can select or input a business document based on the business document upload page displayed by the client (i.e., the front end). The business document can be a company opening document, such as a company name change certificate, etc.; then, the client can obtain the business document to be uploaded and send it to the server; the server can receive the business document and save it. This can ensure that each business document has a unified storage location and avoid the need to download each business document from different storage locations.

[0041] Furthermore, when storing business files, there are multiple levels of storage media and their corresponding storage methods. The reading speeds of storage media at different levels are different, including but not limited to cache storage media, main memory storage media, cloud storage on the cloud platform, etc. Among them, after obtaining a business file, the file information of the business file, such as the business service corresponding to the business file, the file name, file type, and file size, can be matched one by one with the file information of other business files stored in the server to obtain k similar business files that belong to the same type of file as this business file, where k is an integer. Then, based on the download times and upload times corresponding to the similar business files, the storage parameters of this business file are determined.

[0042] For example, the storage parameter Par of the business file sto can be specifically calculated through the following formula (1):

[0043]

[0044] Among them, α and β respectively represent different storage factors, Dload_fre i represents the download times of the i-th similar business file, and Uload_fre i represents the upload times of the i-th similar business file.

[0045] After calculating the storage parameters through the above method, based on the set storage threshold range and its corresponding storage method, the storage method corresponding to the storage parameters is determined. For example, when there are high download frequencies and high upload frequencies for the similar business files corresponding to a business file, it means that the update frequency and usage frequency of this business file are high. The higher the corresponding storage parameter value, the target product will be stored in the storage medium corresponding to the storage method with a faster reading speed, such as cache storage medium; when there are low download frequencies or low upload frequencies for the similar business files corresponding to a business file, it means that the update frequency or usage frequency of this business file is low. The smaller the corresponding storage parameter value, the target product will be stored in the storage medium corresponding to the storage method with a slower reading speed, such as main memory storage medium, etc. By partitioning and grading the storage of different types of business files according to the update frequency or usage frequency in the above way, while ensuring the storage and reading efficiency of business files, the storage space is effectively saved.

[0046] For example, one storage threshold range can correspond to one storage method, and the storage method corresponding to the storage threshold range to which the storage parameter belongs can be determined as the storage method of the corresponding business file.

[0047] Exemplarily, the server can store the business file in the local storage unit of the server or in the corresponding cloud storage unit. Specifically, the target business service, the user's account information or account details, and the business file can be associated and stored, so as to facilitate subsequent downloading of the corresponding business file according to the business service or account information or account details.

[0048] In one embodiment, before saving the business file, the following at least one verification can be performed on the business file:

[0049] The first verification includes: querying the specific file verification field corresponding to the target business service based on the configuration center; in response to not querying the specific file verification field corresponding to the target business service, obtaining the preset file verification field and verifying the business file according to the preset file verification field; or, in response to querying the specific file verification field corresponding to the target business service, obtaining the specific file verification field corresponding to the target business service and verifying the business file according to the specific file verification field corresponding to the target business service.

[0050] Correspondingly, the above-mentioned saving of the business file includes: in response to passing the verification of the business file, saving the business file.

[0051] Among them, the configuration center can be a unit in the server or other services communicating with the server. The configuration center is used to set the preset file verification field and the specific file verification field corresponding to each business service.

[0052] Specifically, the specific file verification field is used to verify the business file under the corresponding business service. The business party of the corresponding business service can configure the specific file verification field based on the configuration center. Specifically, the configuration center can set the specific file verification field for the upload interface used to save the business file, and perform management operations such as saving the information corresponding to the specific file verification field through the configuration center. After that, before saving the business file based on the upload interface, the business file can be verified based on the configuration center. The preset file verification field can be understood as the default file verification field. When the specific file verification field under the target business service is not configured in the configuration center, the corresponding business file can be verified based on the preset file verification field set in the configuration center, so as to achieve the verification before saving any business file and avoid damage to the system caused by non-compliant business files.

[0053] For example, the file verification field can include at least one of the following: file type, file size, file name length.

[0054] Exemplarily, the preset file verification fields in the configuration center and the specific file verification fields corresponding to each business service may include, but are not limited to:

[0055] The preset file verification fields include the file size field "file-max-size" with a corresponding value of 20M and the file type field "file-type-scope" with corresponding values of "pdf, docx". The specific file verification fields under the target business service include the file size field "file-max-size" with a corresponding value of 30M and the file type field "file-type-scope" with corresponding values of "[pdf, docx, xlsx".

[0056] Exemplarily, when verifying a business file according to the preset file verification fields or specific file verification fields, the file size and file type of the business file can be obtained first; then, it is determined whether the file size of the business file is less than the file size indicated by the preset file verification fields or specific file verification fields, and at the same time, it is determined whether the file type of the business file is included in the file type indicated by the preset file verification fields or specific file verification fields; if the file size of the business file is less than the file size indicated by the preset file verification fields or specific file verification fields, and the file type of the business file is included in the file type indicated by the preset file verification fields or specific file verification fields, it is determined that the verification of the business file passes; otherwise, it is determined that the verification of the business file fails.

[0057] It can be understood that through the first verification, a fallback verification for business files can be achieved, avoiding damage to the system caused by the client not verifying the business file before it is saved.

[0058] The second verification includes: determining the frequency limit duration for the client account corresponding to the client and the maximum upload quantity within the frequency limit duration; determining the frequency limit keyword according to the account identifier of the client account and the service identifier of the target business service; obtaining the frequency limit value according to the frequency limit keyword, where the frequency limit value includes the historical quantity of historical business files uploaded within the frequency limit duration; and determining whether the historical quantity indicated by the frequency limit value is greater than the maximum upload quantity

[0059] Correspondingly, the above-mentioned saving of the business file includes: in response to the historical quantity indicated by the frequency limit value being less than or equal to the maximum upload quantity, saving the business file.

[0060] Specifically, the limited frequency duration for the client account corresponding to the client can be determined first, as well as the maximum number of uploads within the limited frequency duration; then, based on the account identifier of the client account and the service identifier of the target business service, the limited frequency keyword key can be determined; it is judged whether the limited frequency storage unit stores the limited frequency value value corresponding to the limited frequency keyword, where the limited frequency value includes the historical quantity of historical service files uploaded within the limited frequency duration; if the limited frequency value corresponding to the limited frequency keyword is stored, the limited frequency value is obtained from the limited frequency storage unit; if the limited frequency value corresponding to the limited frequency keyword is not stored, the limited frequency value in the initialization state is determined according to the limited frequency duration, where the historical quantity corresponding to the limited frequency value in the initialization state is 0; then, the historical quantity indicated by the limited frequency value can be incremented by the value 1; after that, it can be judged whether the historical quantity indicated by the limited frequency value is greater than the maximum number of uploads.

[0061] Exemplarily, after determining the limited frequency keyword, the server can also judge whether the limited frequency storage unit stores the limited frequency keyword; if the limited frequency keyword is stored, the corresponding limited frequency value is obtained from the limited frequency storage unit; if the limited frequency keyword is not stored, the limited frequency keyword is stored in the storage unit, and the limited frequency value in the initialization state is determined according to the limited frequency duration.

[0062] Exemplarily, the account identifier of the client account and the service identifier of the target business service can be combined to obtain the limited frequency keyword. For example, assuming the account identifier is "uid" and the service identifier is "business", the limited frequency keyword can be "{business}_{uid}".

[0063] Exemplarily, the limited frequency storage unit can be a database such as Redis, and the limited frequency keyword and the limited frequency value corresponding to the limited frequency keyword can be stored correspondingly based on the string type of Redis. This application does not make any restrictions on this. For example, in Redis, the key is "ins_file_{business}_{uid}" for recording each limited frequency keyword, and the structure of the value is "{createTimestamp}-{count}", where "{createTimestamp}" is used to record the current timestamp, and "{count}" is used to record the historical quantity. Among them, the current timestamp is used to match the limited frequency duration to determine whether the current time does not exceed the limited frequency duration. When the current time does not exceed the limited frequency duration, the historical quantity in the limited frequency value is determined. When the current time exceeds the limited frequency duration, the current timestamp and the limited frequency value can be initialized.

[0064] Specifically, it is possible to check whether the rate limit value corresponding to the rate limit keyword is stored in Redis through the GET command. If the rate limit value is stored, the GET command can be used to obtain the rate limit value; if the rate limit value is not stored, the SET command can be used to initialize the rate limit value.

[0065] Exemplarily, as Figure 4 shown, it is possible to first check whether the corresponding account data is stored in Redis, for example, the rate limit value corresponding to the rate limit keyword. When it is not stored, the rate limit value corresponding to the rate limit keyword can be initialized according to the above embodiments, and the rate limit duration, that is, the validity period, can be set to 1 minute; after the rate limit value is stored or the above initialization is performed, the historical quantity can be incremented, that is, the value is incremented by 1. Then it can be determined whether the historical quantity at this time is greater than the maximum upload quantity of 150. If it is greater, the upload request for the service file can be rejected; otherwise, the service file can be saved.

[0066] Through the second item of verification, it is possible to limit the frequency of the user uploading service files, avoid malicious traffic brushing, and reduce the risk to the system.

[0067] The third item of verification includes: obtaining the login status of the client account corresponding to the client and the upload ticket corresponding to the client's request to upload a service file, and verifying the login status and the upload ticket.

[0068] Correspondingly, the above-mentioned saving of the service file includes: if the verification of the login status and the upload ticket passes, the service file is saved.

[0069] Among them, the upload ticket includes at least one of the following: the validity status, the expiration status, the revocation status of the upload operation corresponding to the client's request to upload a service file, and the matching status between the upload request corresponding to the client's request to upload a service file and the upload operation.

[0070] Exemplarily, the server can store the login status of the client account corresponding to the client and the upload ticket corresponding to the client's request to upload a service file in a unified ticket center; before saving the service file, the login status and the upload ticket can be obtained through the ticket center based on the upload interface and verified.

[0071] Specifically, the server can first initialize the login status and the upload ticket in the ticket center, and then, according to the user's operations based on the client, update them accordingly, so as to obtain the latest login status and upload ticket and verify them.

[0072] For example, regarding the login status, the server can, based on the ticket center, preset the login status corresponding to each client account as the non-logged-in status in advance. After that, the server can, according to the user's login operation or logout operation for the client, update the login status corresponding to the client account in the ticket center in real time: in response to the user's login operation for the client, obtain the corresponding client account and set the login status corresponding to the client account as the logged-in status; or, in response to the user's logout operation for the client, obtain the corresponding client account and set the login status corresponding to the client account as the non-logged-in status.

[0073] Correspondingly, if the verified login status is the logged-in status, it is determined that the verification of the login status passes; otherwise, it is determined that the verification of the login status fails.

[0074] Regarding the uploaded ticket, the server can, based on the ticket center, preset the uploaded ticket corresponding to the client's request to upload a business file as the initial uploaded ticket status. In the initial uploaded ticket status, the following statuses corresponding to the uploaded ticket: the validity status of the upload operation corresponding to the client's request to upload a business file is the valid status, the expiration status is the non-expired status, the revocation status is the non-revoked status, and the matching status between the upload request and the upload operation corresponding to the client's request to upload a business file is the matched status. After that, the server can, according to the user operation, user permissions, and the request time of the upload request corresponding to the client's request to upload a business file, update the above initial uploaded ticket status in real time: if a user's cancel upload operation based on the client is obtained, update the revocation status to the revoked status; if a user's exit operation for the business file upload page based on the client is obtained, update the validity status to the invalid status; if it is determined that the request time of the corresponding upload request does not belong to the preset request time, update the expiration status to the expired status; if it is determined that the user permissions do not include the upload permission for the business file, update the matching status to the unmatched status.

[0075] Correspondingly, if the validity status in the uploaded ticket is the valid status, the expiration status is the non-expired status, the revocation status is the non-revoked status, and the matching status is the matched status, it is determined that the verification of the uploaded ticket passes; otherwise, it is determined that the verification of the uploaded ticket fails.

[0076] Through the third item of verification, it is possible to verify the user's login status and uploaded ticket, avoid hotlinking and non-compliant upload operations, and reduce the risks to the system.

[0077] In one embodiment, determining the first file identifier of the business document includes: obtaining the identifier generation information corresponding to the business document, where the identifier generation information includes at least one of the following: client information of the client, business service information of the target business service, file information of the business document, and account information of the client account corresponding to the client; generating a target universally unique identifier (UUID) of the business document according to the identifier generation information; obtaining the historical UUID of the historical business document; determining whether the target UUID is the same as the historical UUID; if the target UUID is not the same as the historical UUID, determining the target UUID as the first file identifier; if the UUID is the same as the historical UUID, continuing to execute generating the target UUID of the business document according to the identifier generation information until the target UUID is not the same as the historical UUID, and obtaining the first file identifier.

[0078] Exemplarily, the UUID can be a string with a length of 32 bits, and the present application does not limit this. Specifically, the UUID can be UUID (Universally Unique Identifier).

[0079] Exemplarily, the client information of the client can include: version number of the client, operating system, device type, etc.; the business service information of the target business service can include: name of the target business service, version, server where it is located, etc.; the file information of the business document can include: file name, file type, file size, creation time, etc.; the account information of the client account corresponding to the client can include: client account identifier, corresponding user name, organization to which it belongs, etc.

[0080] Exemplarily, generating the target UUID of the business document according to the identifier generation information includes: obtaining the current time; performing a hash process on the current time and the generated identifier according to a hash function (such as SHA-256) to obtain a hash value with a fixed length as the target UUID.

[0081] In the above content, compared with the method of determining all file identifiers based on the auto-incrementing ID (Identity), the file identifiers generated by the above method are more random and do not have an inherent pattern, so they are not easily brute-forced, and the security of file storage can be improved.

[0082] In one embodiment, after generating the first file identifier, the server can return it to the client. At the same time, the client can obtain the business materials related to the business file input or selected by the user, and determine a business material submission request (including the business materials and the file identifier of the business file, such as the second file identifier). Then, the client can send the business material submission request to the storage service. After that, the storage service can obtain and parse the business material submission request, thereby determining the second file identifier and sending it to the server. The server can verify the first file identifier and the second file identifier. If it is determined that the first file identifier and the second file identifier are consistent, the file identifier verification result is determined to be that the file identifier verification passes. If it is determined that the first file identifier and the second file identifier are inconsistent, the file identifier verification result is determined to be that the file identifier verification fails. Then, the server can send the file identifier verification result to the storage service. If the file identifier verification result is that the file identifier verification passes, the storage service can store the business materials. If the file identifier verification result is that the file identifier verification fails, the storage service can refrain from storing the business materials.

[0083] It can be understood that if the client that sends the business material submission request to the storage service is the same client that sends the business file to be uploaded in the target business service to the server, then the second file identifier is the same as the first file identifier, that is, the second file identifier is the first file identifier, and thus the file identifier verification result will surely be that the file identifier verification passes, and the storage service will surely store the business materials. On the contrary, if the client that sends the business material submission request to the storage service is not the same client that sends the business file to be uploaded in the target business service to the server, then the second file identifier and the first file identifier will surely be different, that is, the second file identifier is inconsistent with the first file identifier, and thus the file identifier verification result will surely be that the file identifier verification fails, and the storage service will surely not store the business materials. Therefore, the correct storage of the business materials related to the business file can be achieved, ensuring the relevance between the business materials and the business file, thereby maintaining the data consistency and avoiding the generation of dirty data.

[0084] Exemplarily, as Figure 5 shown, the server includes a file service. Before the user submits the business materials based on the client, the business file can be first sent to the file service. The file service can save the business file and return the first file identifier to the client. After that, the client can submit the business materials to the storage service with the second file identifier (the same as or different from the first file identifier). The storage service can call the interface provided by the file service to batch verify the legality of the file identifier, verify whether the first file identifier and the second file identifier are consistent, obtain the file identifier verification result, and determine whether to perform data storage on the business materials according to the file identifier verification result.

[0085] Through the above, the storage of business documents and business materials can be achieved. After that, based on this, the basic file information of business documents can be stored, queried, or the business documents can be downloaded. This application will be introduced in the following embodiments.

[0086] It should be noted that historical business documents can refer to business documents that have been saved, for example, the target business documents that have been saved.

[0087] In one embodiment, as Figure 6 shown, the client needs to display basic file information such as the file name (for example, file name A, etc.) and the file upload time (for example, 2024 / 09 / 14) on the corresponding page. Therefore, it is necessary to pre-store the basic file information of each historical business document and batch obtain it when needed to improve the data acquisition ability and display efficiency. Specifically, it can be achieved through the following steps:

[0088] S260-1: Obtain the historical file basic information of at least one historical business document respectively. The historical file basic information includes at least one of the following: file name, file size, file upload time, and file uploader information;

[0089] S260-2: Associatively store the file identifiers and historical file basic information of at least one historical business document respectively;

[0090] S260-3: Receive the first file basic information query request sent by the client. The first file basic information query request includes: the file identifiers of at least one historical business document returned by the storage service to the client in response to the second file basic information query request sent by the client;

[0091] S260-4: In response to the first file basic information query request, based on the associative storage, obtain the basic file information of at least one historical business document respectively according to the file identifiers of at least one historical business document;

[0092] S260-5: Return the basic file information of at least one historical business document respectively to the client.

[0093] Exemplarily, after the server obtains the historical business document to be uploaded sent by the client, it can parse the historical business document to obtain the file name and file size of the historical business document, determine the time when the historical business document is obtained from the client as the file upload time, and determine the client account of the client as the file uploader information.

[0094] Exemplarily, as Figure 7As shown, the server includes a file service. The storage service can obtain and respond to a second file basic information query request sent by the client. This request is used to obtain specific business files existing under specific data information, that is, at least one historical business file. The storage service can return a file identifier list including the file identifiers of at least one historical business file to the client. The client can send the file identifier list to the file service to batch obtain the file basic information of each of at least one historical business file.

[0095] In one embodiment, the download of historical business files can be achieved through the following steps:

[0096] S270-1: Receive a first file download request sent by the client. The first file download request includes: the file identifier of the historical business file to be downloaded that the storage service returns to the client in response to the second file download request sent by the client;

[0097] S270-2: In response to the first file download request, obtain the historical business file to be downloaded according to the file identifier of the historical business file to be downloaded;

[0098] S270-3: Return the historical business file to be downloaded to the client.

[0099] Exemplarily, as Figure 8 shown, the client can first send a second file download request to the storage service to request data, for example, the historical business file to be downloaded. The storage service can return the file identifier of the historical business file to be downloaded to the client in response to the second file download request. After that, the client can send a first file download request including the file identifier of the historical business file to be downloaded to the file service. The file service can, in response to the first file download request, obtain the historical business file to be downloaded according to the file identifier of the historical business file to be downloaded and return it to the client.

[0100] Exemplarily, before the above S270-2, it further includes: obtaining the login status of the client account corresponding to the client and the download ticket corresponding to the first file download request; obtaining the account identifier of the client account and the upload user account identifier corresponding to the historical business file to be downloaded; determining whether the account identifier is consistent with the upload user account identifier, and verifying the login status and the download ticket.

[0101] Correspondingly, S270-2 includes: if the account identifier is consistent with the upload user account identifier and the verification of the login status and the download ticket passes, then in response to the first file download request, obtain the historical business file to be downloaded according to the file identifier of the historical business file to be downloaded.

[0102] Among them, the downloaded bill includes at least one of the following: the validity status, expiration status, revocation status of the download operation corresponding to the first file download request, and the matching status between the first file download request and the download operation. The processes and methods for verifying the login status and the downloaded bill can refer to the content corresponding to the third item of verification above. To avoid repetition, this application will not elaborate on this.

[0103] Through the above authentication operation, it can be ensured that users can only download the business files they upload, and cannot view the business files uploaded by other users, avoiding user over-authorization and ensuring the storage security of business files.

[0104] Through the above embodiments, the client can directly connect to the server to implement file upload and download, without the need for repeated development for different business services. Moreover, a configuration center is provided for configuration management of the verification of the file name length, file size, file type, etc. corresponding to each business service, which can adapt to multiple business services without the need for coding for specific scenarios. In addition, in order to ensure the security of business files, designs such as anti-malicious traffic brushing, anti-over-authorization download, and anti-leeching are carried out.

[0105] It should be noted that all the above technical solutions can be combined arbitrarily to form optional embodiments of this application, which will not be elaborated one by one here.

[0106] It should be noted that in the specific implementation of this application, it involves relevant data such as business files, business materials, file basic information, login status, and bills. When the embodiments of this application are applied to specific products or technologies, user permission, consent, or authorization is required, and the collection, use, and processing of relevant data need to comply with the relevant laws, regulations, and standards of relevant countries and regions.

[0107] Figure 9 It is a schematic diagram of a business information processing device 900 provided by an embodiment of this application. As Figure 9 shown, the device 900 includes: a file receiving module 901, a file uploading module 902, an identifier receiving module 903, an identifier verification module 904, a result returning module 905, a field query module 906, a field verification module 907, a first determination module 908, a second determination module 909, a frequency limiting processing module 910, a second judgment module 911, a first obtaining module 912, an associated storage module 913, a request receiving module 914, a second obtaining module 915, an information returning module 916, a first receiving module 917, a third obtaining module 918, a first returning module 919, a fourth obtaining module 920, a fifth obtaining module 921, a third judgment module 922, a sixth obtaining module 923, and a bill verification module 924.

[0108] In one embodiment, a file receiving module 901 is configured to receive a service file to be uploaded in a target service sent by a client; a file uploading module 902 is configured to save the service file, determine a first file identifier of the service file, and return the first file identifier to the client; an identifier receiving module 903 is configured to receive a second file identifier sent by a storage service in response to a service data submission request, where the service data submission request is a request sent by the client to the storage service for storing service data related to the service file, and the service data submission request includes service data and the second file identifier of the service file; an identifier verification module 904 is configured to verify the second file identifier according to the first file identifier to obtain a file identifier verification result; and a result returning module 905 is configured to return the file identifier verification result to the storage service, so that the storage service determines whether to store the service data according to the file identifier result.

[0109] In one embodiment, a field query module 906 is configured to query specific file verification fields corresponding to a target service based on a configuration center, where the configuration center is used to set preset file verification fields and specific file verification fields corresponding to each service; a field verification module 907 is configured to, in response to not querying the specific file verification fields corresponding to the target service, obtain the preset file verification fields and verify the service file according to the preset file verification fields; or, in response to querying the specific file verification fields corresponding to the target service, obtain the specific file verification fields corresponding to the target service and verify the service file according to the specific file verification fields corresponding to the target service; where the file verification fields include at least one of the following: file type, file size, and file name length; correspondingly, the file uploading module 902 is specifically configured to save the service file in response to passing the verification of the service file.

[0110] In one embodiment, a first determination module 908 is configured to determine a frequency limit duration for a client account corresponding to the client and a maximum upload quantity within the frequency limit duration; a second determination module 909 is configured to determine a frequency limit keyword according to the account identifier of the client account and the service identifier of the target service; a frequency limit processing module 910 is configured to obtain a frequency limit value according to the frequency limit keyword, where the frequency limit value includes the historical quantity of historical service files uploaded within the frequency limit duration; a second judgment module 911 is configured to judge whether the historical quantity indicated by the frequency limit value is greater than the maximum upload quantity; correspondingly, the file uploading module 902 is specifically configured to save the service file in response to the historical quantity indicated by the frequency limit value being less than or equal to the maximum upload quantity.

[0111] In one embodiment, the file upload module 902 is specifically configured to: obtain the identification generation information corresponding to the service file, where the identification generation information includes at least one of the following: the client information of the client, the service information of the target service, the file information of the service file, and the account information of the client account corresponding to the client; generate the target universal unique identifier of the service file according to the identification generation information; obtain the historical universal unique identifier of the historical service file; determine whether the target universal unique identifier is consistent with the historical universal unique identifier; if the target universal unique identifier is not consistent with the historical universal unique identifier, determine the target universal unique identifier as the first file identifier; if the universal unique identifier is consistent with the historical universal unique identifier, continue to execute generating the target universal unique identifier of the service file according to the identification generation information until the target universal unique identifier is not consistent with the historical universal unique identifier, and obtain the first file identifier.

[0112] In one embodiment, the first acquisition module 913 is configured to acquire the respective historical file basic information of at least one historical service file, where the historical file basic information includes at least one of the following: file name, file size, file upload time, and file uploader information; the associated storage module 913 is configured to perform associated storage on the respective file identifiers and historical file basic information of at least one historical service file; the request receiving module 914 is configured to receive the first file basic information query request sent by the client, where the first file basic information query request includes: the file identifiers of at least one historical service file returned by the storage service to the client in response to the second file basic information query request sent by the client; the second acquisition module 915 is configured to, in response to the first file basic information query request, acquire the respective file basic information of at least one historical service file based on the associated storage according to the file identifiers of at least one historical service file; the information return module 916 is configured to return the respective file basic information of at least one historical service file to the client.

[0113] In one embodiment, the first receiving module 917 is configured to receive the first file download request sent by the client, where the first file download request includes: the file identifier of the historical service file to be downloaded returned by the storage service to the client in response to the second file download request sent by the client; the third acquisition module 918 is configured to, in response to the first file download request, acquire the historical service file to be downloaded according to the file identifier of the historical service file to be downloaded; the first return module 919 is configured to return the historical service file to be downloaded to the client.

[0114] In one embodiment, a fourth acquisition module 920 is configured to acquire the login status of a client account corresponding to a client and a download ticket corresponding to a first file download request; a fifth acquisition module 921 is configured to acquire an account identifier of the client account and an upload user account identifier corresponding to a historical service file to be downloaded; a third determination module 922 is configured to determine whether the account identifier is consistent with the upload user account identifier, and verify the login status and the download ticket; wherein the download ticket includes at least one of the following: a validity status, an expiration status, a revocation status, and a matching status between the first file download request and the download operation of the download operation corresponding to the first file download request; a third acquisition module 918 is specifically configured to, if the account identifier is consistent with the upload user account identifier and the verification of the login status and the download ticket passes, in response to the first file download request, acquire the historical service file to be downloaded according to the file identifier of the historical service file to be downloaded.

[0115] In one embodiment, a sixth acquisition module 923 is configured to acquire the login status of a client account corresponding to a client and an upload ticket corresponding to a client request to upload a service file, and a ticket verification module 924 is configured to verify the login status and the upload ticket; wherein the upload ticket includes at least one of the following: a validity status, an expiration status, a revocation status, and a matching status between the client request to upload the service file and the upload operation of the upload operation corresponding to the client request to upload the service file; a file upload module 902 is specifically configured to, if the verification of the login status and the upload ticket passes, save the service file.

[0116] It should be understood that the apparatus embodiments and the method embodiments can correspond to each other, and similar descriptions can refer to the method embodiments. To avoid repetition, details are not described herein again. Specifically, Figure 9 The illustrated apparatus 900 can execute the foregoing method embodiments, and the foregoing and other operations and / or functions of each module in the apparatus 900 respectively implement the corresponding processes in the foregoing various methods. For the sake of brevity, details are not described herein again.

[0117] The device 900 according to the embodiments of the present application has been described above from the perspective of functional modules with reference to the accompanying drawings. It should be understood that these functional modules can be implemented in the form of hardware, or in the form of instructions in software, or in a combination of hardware and software modules. Specifically, the steps of the method embodiments in the present application can be completed by the integrated logic circuit in the hardware of the processor and / or instructions in the form of software. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of the hardware and software modules in the decoding processor. Optionally, the software module can be located in a mature storage medium in the art such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps in the above method embodiments.

[0118] Figure 10 Schematic diagram of an electronic device 1000 provided by an embodiment of the present application.

[0119] As Figure 10 shown, the electronic device 1000 may include:

[0120] A memory 1010 and a processor 1020. The memory 1010 is used to store a computer program and transmit the program code to the processor 1020. In other words, the processor 1020 can call and run the computer program from the memory 1010 to implement the method in the embodiments of the present application.

[0121] For example, the processor 1020 can be used to execute the above method embodiments according to the instructions in the computer program.

[0122] In some embodiments of the present application, the processor 1020 may include, but is not limited to:

[0123] General-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and so on.

[0124] In some embodiments of the present application, the memory 1010 includes, but is not limited to:

[0125] Volatile memory and / or non-volatile memory. Among them, the non-volatile memory can be Read-Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically Erasable PROM (EEPROM), or flash memory. The volatile memory can be Random Access Memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double DataRate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synch Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0126] In some embodiments of the present application, the computer program may be divided into one or more modules, and the one or more modules are stored in the memory 1010 and executed by the processor 1020 to complete the method provided by the present application. The one or more modules may be a series of computer program instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer program in the electronic device.

[0127] As Figure 10 shown, the electronic device may further include:

[0128] A transceiver 1030, which may be connected to the processor 1020 or the memory 1010.

[0129] Among them, the processor 1020 may control the transceiver 1030 to communicate with other devices. Specifically, it may send information or data to other devices, or receive information or data sent by other devices. The transceiver 1030 may include a transmitter and a receiver. The transceiver 1030 may further include an antenna, and the number of antennas may be one or more.

[0130] It should be understood that each component in the electronic device is connected through a bus system. Among them, in addition to the data bus, the bus system also includes a power bus, a control bus, and a status signal bus.

[0131] The present application also provides a computer storage medium, on which a computer program is stored. When the computer program is executed by a computer, the computer can execute the methods in the above method embodiments. Or rather, the embodiments of the present application also provide a computer program product containing instructions. When the instructions are executed by a computer, the computer executes the methods in the above method embodiments.

[0132] When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the computer can execute all or part of the corresponding processes in the methods in the embodiments of the present application and generate the functions that can be realized by the methods in the embodiments of the present application. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from a website, a computer, a server, or a data center to another website, computer, server, or data center in a wired manner (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or a wireless manner (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrating one or more available media. The available medium can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a Digital Video Disc (DVD)), or a semiconductor medium (such as a Solid State Disk (SSD)).

[0133] Those of ordinary skill in the art can realize that the modules and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or by a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0134] In several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the modules is only a logical function division. In actual implementation, there may be other division methods. For example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling, direct coupling, or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of the devices or modules can be in electrical, mechanical, or other forms.

[0135] The modules described as separate components may or may not be physically separated. The components displayed as modules may or may not be physical modules, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. For example, in each embodiment of the present application, the functional modules can be integrated in a processing module, or each module can exist physically alone, or two or more modules can be integrated in one module.

Claims

1. A business information processing method, characterized in that: include: Receive the business files to be uploaded in the target business service sent by the client; The business file is saved, a first file identifier of the business file is determined, and the first file identifier is returned to the client; Receiving a second file identifier sent by the storage service in response to a business profile submission request, wherein the business profile submission request is a request sent by the client to the storage service for storing business profile related to the business file, and the business profile submission request includes the business profile and the second file identifier of the business file; Verifying the second file identifier according to the first file identifier to obtain a file identifier verification result; The file identification verification result is returned to the storage service, so that the storage service determines whether to store the business data according to the file identification result.

2. The method according to claim 1, characterized in that Before saving the business file, the method further includes: Querying the specific file verification field corresponding to the target business service based on the configuration center, wherein the configuration center is used to set the preset file verification field and the specific file verification field corresponding to each business service; In response to not finding the specific file verification field corresponding to the target business service, obtaining the preset file verification field, and verifying the business file according to the preset file verification field; or, In response to querying the specific file verification field corresponding to the target business service, obtaining the specific file verification field corresponding to the target business service, and verifying the business file according to the specific file verification field corresponding to the target business service; The file check field includes at least one of the following: file type, file size, and file name length; Accordingly, the storing of the business file includes: In response to the business file being verified to be successful, the business file is saved.

3. The method according to claim 1, characterized in that Before saving the business file, the method further includes: Determine a frequency limit duration for a client account corresponding to the client and a maximum number of uploads within the frequency limit duration; Determining a frequency-limited keyword according to the account identifier of the client account and the service identifier of the target business service; Acquire a frequency limit value according to the frequency limit keyword, wherein the frequency limit value includes a historical number of historical service files uploaded within the frequency limit duration; Determine whether the historical number indicated by the frequency limit value is greater than the maximum upload number; Accordingly, the storing of the business file includes: In response to the historical number indicated by the frequency limit value being less than or equal to the maximum upload number, the business file is saved.

4. The method according to claim 1, characterized in that: The determining the first file identifier of the business file includes: Acquire identification generation information corresponding to the business file, the identification generation information including at least one of the following: client information of the client, business service information of the target business service, file information of the business file, and account information of a client account corresponding to the client; Generate a target universal unique identification code for the business file according to the identification generation information; Obtain the historical universal unique identification code of historical business documents; Determining whether the target universal unique identifier is consistent with the historical universal unique identifier; If the target universal unique identifier is not consistent with the historical universal unique identifier, determining the target universal unique identifier as the first file identifier; If the universal unique identifier is consistent with the historical universal unique identifier, the step of generating the target universal unique identifier of the business file according to the identifier generation information is continued until the target universal unique identifier is no longer consistent with the historical universal unique identifier, and the first file identifier is obtained.

5. The method according to any one of claims 1 to 4, characterized in that: Also includes: Acquire historical file basic information of at least one historical business file, where the historical file basic information includes at least one of the following: file name, file size, file upload time, and file uploader information; storing the file identifier and the historical file basic information of each of the at least one historical business files in an associated manner; receiving a first basic file information query request sent by the client, wherein the first basic file information query request includes: a file identifier of the at least one historical business file returned to the client by the storage service in response to a second basic file information query request sent by the client; In response to the first file basic information query request, acquiring the file basic information of each of the at least one historical business file based on the associated storage and the file identifier of the at least one historical business file; The basic file information of each of the at least one historical business file is returned to the client.

6. The method according to any one of claims 1 to 4, characterized in that: Also includes: receiving a first file download request sent by the client, wherein the first file download request includes: a file identifier of a historical service file to be downloaded returned to the client by the storage service in response to a second file download request sent by the client; In response to the first file download request, acquiring the historical service file to be downloaded according to the file identifier of the historical service file to be downloaded; The historical service file to be downloaded is returned to the client.

7. The method according to claim 6, characterized in that Before the step of obtaining the historical service file to be downloaded according to the file identifier of the historical service file to be downloaded in response to the first file download request, the step further includes: Obtaining the login status of the client account corresponding to the client and the download ticket corresponding to the first file download request; Obtaining the account ID of the client account and the uploading user account ID corresponding to the historical business file to be downloaded; Determine whether the account ID is consistent with the uploading user account ID, and verify the login status and the download ticket; The download ticket includes at least one of the following: the validity status, expiration status, and revocation status of the download operation corresponding to the first file download request, and the matching status between the first file download request and the download operation; The step of obtaining the historical service file to be downloaded according to the file identifier of the historical service file to be downloaded in response to the first file download request includes: If the account identifier is consistent with the uploading user account identifier and the login status and the download ticket are verified, the historical business file to be downloaded is obtained according to the file identifier of the historical business file to be downloaded in response to the first file download request.

8. The method according to any one of claims 1 to 4, characterized in that: Before saving the business file, the method further includes: Obtaining the login status of the client account corresponding to the client and the upload ticket corresponding to the client requesting to upload the business file, Verifying the login status and the uploaded ticket; The upload ticket includes at least one of the following: the validity status, expiration status, and revocation status of the upload operation corresponding to the client's request to upload the business file, and the matching status between the upload request corresponding to the client's request to upload the business file and the upload operation; The storing of the business file includes: If the login status and the uploaded ticket are verified, the business file is saved.

9. A business information processing device, characterized in that: include: The file receiving module is used to receive the business files to be uploaded in the target business service sent by the client; A file upload module, used for saving the business file, determining a first file identifier of the business file, and returning the first file identifier to the client; an identification receiving module, configured to receive a second file identification sent by the storage service in response to a business data submission request, wherein the business data submission request is a request sent by the client to the storage service for storing business data related to the business file, and the business data submission request includes the business data and the second file identification of the business file; an identification verification module, used to verify the second file identification according to the first file identification, and obtain a file identification verification result; The result returning module is used to return the file identification verification result to the storage service so that the storage service determines whether to store the business data according to the file identification result.

10. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; The processor is configured to perform the method of any one of claims 1 to 8 by executing the executable instructions.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 8 is implemented.

Images