Business processing method and device, equipment and storage medium
By adding a random verification code to the protocol document and confirming its consistency in the business processing device, the problem of inability to verify user consent in the prior art is solved, and the reliability of business processing is improved.
Patent Information
- Application Number
- CN202411522969.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-29
- Publication Date
- 2024-12-31
AI Technical Summary
In the prior art, the service processing device cannot verify whether the user reads and agrees to the content of the agreement document, resulting in low reliability of the service processing.
By generating and adding a random verification code at the end of the protocol document, the user can only obtain the verification code after reading the protocol document. The business processing device only processes the business request after confirming that the verification code is consistent, ensuring that the user agrees to the agreement content.
Improve the reliability of business processing, ensure that users read and agree to the content of the agreement document, and reduce subsequent deniability.
Smart Images

Figure CN119228522A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a business processing method, device, equipment and storage medium. Background Art
[0002] In some scenarios, the service processing device can process the service request proposed by the user. For example, in a financial scenario, the banking system can process the service requested by the enterprise system.
[0003] In related technologies, when a user needs to request a business service provided by a business processing device, he or she can first download the preset protocol document in the business processing device through the Application Programming Interface (API), and then send a business request to the business processing device. After receiving the business request, the business processing device only needs to verify whether the user has downloaded the protocol document. After successful verification, the business service requested by the user can be processed.
[0004] However, in the above method, the business processing device cannot verify whether the user has read and agreed to the content of the agreement document, and may subsequently deny the agreement content, resulting in low reliability of business processing. Summary of the invention
[0005] The present application provides a business processing method, apparatus, device and storage medium to solve the problem of low reliability of business processing.
[0006] In a first aspect, the present application provides a business processing method, including:
[0007] Receiving a service processing request sent by an electronic device, the service processing request including user information and a service type, the service processing request being used to request processing of a target service;
[0008] Generate a service identifier and a target protocol text according to the user information, the service type and the current time;
[0009] Generate a first random verification code, and generate a protocol document according to the service identifier, the target protocol text and the first random verification code, wherein the first random verification code is located at the bottom of the protocol document;
[0010] Sending the protocol document to the electronic device, and receiving a second random verification code sent by the electronic device;
[0011] When the first random verification code and the second random verification code are the same, the target service is processed.
[0012] In a possible design, the initial protocol text is updated according to the user information, the service type and the current time to obtain the target protocol text, including:
[0013] Determining user-related text, service-related text and time-related text in the initial agreement text;
[0014] In the initial protocol text, the user-related text is updated according to the user information, the service-related text is updated according to the service type, and the time-related text is updated according to the current moment to obtain the target protocol text.
[0015] In a possible design, generating a protocol document according to the service identifier, the target protocol text and the first random verification code includes:
[0016] Get the preset document template;
[0017] Generate a first digital signature corresponding to the target protocol text;
[0018] The service identifier, the target agreement text, the first random verification code and the first digital signature are filled into the document template to obtain the agreement document.
[0019] In one possible design, generating a first digital signature corresponding to the target protocol text includes:
[0020] Get the preset private key;
[0021] Performing a hash operation on the target protocol text by using a hash algorithm to obtain a hash value;
[0022] The hash value is encrypted using the private key to obtain the first digital signature.
[0023] In a possible design, after the protocol document is generated according to the service identifier, the target protocol text and the first random verification code, the method further includes:
[0024] Generate a correspondence between the service identifier, the target protocol text and the first random verification code;
[0025] Setting the processing status of the corresponding relationship to a pending confirmation status;
[0026] In the second database, the corresponding relationship and the processing status are stored correspondingly.
[0027] In a possible design, when the first random verification code and the second random verification code are the same, processing the target service includes:
[0028] According to the service identifier, obtaining the first random verification code from the second database;
[0029] Determining whether the first random verification code and the second random verification code are the same;
[0030] If yes, the target business is processed and the processing status is set to a confirmed status.
[0031] In a possible design, the protocol document further includes a first digital signature; and the method further includes:
[0032] receiving a verification request, wherein the verification request is used to request verification of whether the protocol document has been tampered with;
[0033] Acquire the first digital signature in the protocol document according to the verification request;
[0034] Performing a hash operation on the target protocol text in the protocol document by using a hash algorithm to obtain a second digital signature;
[0035] If the first digital signature and the second digital signature are the same, it is determined that the protocol document has not been tampered with;
[0036] If the first digital signature and the second digital signature are not identical, it is determined that the protocol document has been tampered with.
[0037] In a second aspect, the present application provides a service processing device, including: a receiving module, a first generating module, a second generating module, a transceiver module and a processing module, wherein:
[0038] The receiving module is used to receive a service processing request sent by an electronic device, wherein the service processing request includes user information and a service type, and the service processing request is used to request processing of a target service;
[0039] The first generating module is used to generate a service identifier and a target protocol text according to the user information, the service type and the current time;
[0040] The second generating module is used to generate a first random verification code, and generate a protocol document according to the service identifier, the target protocol text and the first random verification code, wherein the first random verification code is located at the bottom of the protocol document;
[0041] The transceiver module is used to send the protocol document to the electronic device and receive a second random verification code sent by the electronic device;
[0042] The processing module is used for processing the target service when the first random verification code and the second random verification code are the same.
[0043] In a possible design, the first generating module is specifically used for:
[0044] Acquire an initial protocol text in the first database according to the service type, and add one to the acquisition number to obtain a target acquisition number, where the target acquisition number is used to indicate the number of times the initial protocol text is acquired in the first database in the current cycle;
[0045] Generate the service identifier according to the service type, the current time and the target acquisition number;
[0046] The initial protocol text is updated according to the user information, the service type and the current time to obtain the target protocol text.
[0047] In a possible design, the first generating module is specifically used for:
[0048] Determining user-related text, service-related text and time-related text in the initial agreement text;
[0049] In the initial protocol text, the user-related text is updated according to the user information, the service-related text is updated according to the service type, and the time-related text is updated according to the current moment to obtain the target protocol text.
[0050] In a possible design, the second generating module is specifically used to:
[0051] Get the preset document template;
[0052] Generate a first digital signature corresponding to the target protocol text;
[0053] The service identifier, the target agreement text, the first random verification code and the first digital signature are filled into the document template to obtain the agreement document.
[0054] In a possible design, the second generating module is specifically used to:
[0055] Get the preset private key;
[0056] Performing a hash operation on the target protocol text by using a hash algorithm to obtain a hash value;
[0057] The hash value is encrypted using the private key to obtain the first digital signature.
[0058] In a possible design, the second generating module is further used for:
[0059] Generate a correspondence between the service identifier, the target protocol text and the first random verification code;
[0060] Setting the processing status of the corresponding relationship to a pending confirmation status;
[0061] In the second database, the corresponding relationship and the processing status are stored correspondingly.
[0062] In a possible design, the second generating module is further used for:
[0063] According to the service identifier, obtaining the first random verification code from the second database;
[0064] Determining whether the first random verification code and the second random verification code are the same;
[0065] If yes, the target business is processed and the processing status is set to a confirmed status.
[0066] In a possible design, the service processing device further includes a receiving and obtaining module, a calculation module and a determination module, wherein:
[0067] The receiving and obtaining module is specifically used to receive a verification request, where the verification request is used to request verification of whether the protocol document has been tampered with; and obtain the first digital signature in the protocol document according to the verification request;
[0068] The operation module is specifically used to perform a hash operation on the target protocol text in the protocol document through a hash algorithm to obtain a second digital signature;
[0069] The determination module is specifically used to determine that the protocol document has not been tampered with if the first digital signature and the second digital signature are the same; if the first digital signature and the second digital signature are not the same, determine that the protocol document has been tampered with.
[0070] In a third aspect, an embodiment of the present application provides an electronic device, comprising: at least one processor and a memory; the memory stores computer execution instructions; at least one processor executes the computer execution instructions stored in the memory, so that the at least one processor executes the business processing method as described in the first aspect above and various possible designs of the first aspect.
[0071] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer execution instructions are stored. When a processor executes the computer execution instructions, the business processing method as described in the first aspect and various possible designs of the first aspect are implemented.
[0072] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program. When the computer program is executed by a processor, it implements the business processing method as described in the first aspect and various possible designs of the first aspect.
[0073] The business processing method, device, equipment and storage medium provided by the present application can determine the protocol document according to the user's information, the type of business request and the current time when business processing is required for the business request, and add a first random verification code at the bottom of the end of the protocol document, send the protocol document to the user's electronic device, and receive the second random verification code returned by the electronic device. When the first random verification code and the second random verification code are the same, the business is processed. Since the electronic device can only obtain the random verification code at the bottom of the protocol document after the user has read the protocol document, that is, the above method can ensure that the user has read and agreed to the content of the protocol document, thereby improving the reliability of business processing. BRIEF DESCRIPTION OF THE DRAWINGS
[0074] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0075] Figure 1 A schematic diagram of the system architecture provided for an embodiment of the present application;
[0076] Figure 2 A flowchart of a business processing method provided in an embodiment of the present application;
[0077] Figure 3 A schematic diagram of a visual operation window of a business processing system provided in an embodiment of the present application;
[0078] Figure 4 A schematic diagram of the generation process of the protocol document provided in the embodiment of the present application;
[0079] Figure 5 A schematic diagram of a protocol document provided for an embodiment of the present application;
[0080] Figure 6 A schematic diagram of the interaction process between a service processing device and a service requesting device provided in an embodiment of the present application;
[0081] Figure 7 A schematic diagram of the structure of a service processing device provided in an embodiment of the present application;
[0082] Figure 8 A schematic diagram of the structure of another service processing device provided in an embodiment of the present application;
[0083] Fig. 9 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.
[0084] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION
[0085] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.
[0086] In the technical solution of this application, the collection, storage, use, processing, transmission, provision and disclosure of information such as financial data or user data involved shall comply with the provisions of relevant laws and regulations and shall not violate public order and good morals.
[0087] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.
[0088] For ease of understanding, the following Figure 1 , the system architecture applicable to the embodiments of the present application is described.
[0089] Figure 1 This is a schematic diagram of the system architecture provided by the embodiment of this application. Figure 1 , including a service request device 101 and a service processing device 102. The service request device 101 may be a local terminal device of a user, and the user may send a service processing request to the service processing device 102 through the service request device 101. The service processing device 102 may be a remote terminal device, and the service processing device 102 may process the service processing request sent by the service request device 101.
[0090] In the related art, when a user needs to request a business service provided by a business processing device, he can first download the preset protocol document in the business processing device through the application programming interface API, and then send a business request to the business processing device. After receiving the business request, the business processing device only needs to verify whether the user has downloaded the protocol document. After successful verification, the business service requested by the user can be processed. However, in the above method, the business processing device cannot verify whether the user has read and agreed to the content of the protocol document, and there may be subsequent denial of the content of the agreement, resulting in low reliability of business processing.
[0091] In view of the above technical problems, in an embodiment of the present application, when a business request needs to be processed, the protocol document can be determined according to the user's information, the type of business request and the current time, and a first random verification code can be added to the bottom of the end of the protocol document, and the protocol document can be sent to the user's electronic device, and a second random verification code returned by the electronic device can be received. When the first random verification code and the second random verification code are the same, the business is processed. Since the electronic device can only obtain the random verification code at the bottom of the protocol document after the user has read the protocol document, that is, the above method can ensure that the user has read and agreed to the content of the protocol document, thereby improving the reliability of business processing.
[0092] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.
[0093] Figure 2 A flowchart of a business processing method provided in an embodiment of the present application. Figure 2 As shown, the method may include the following steps:
[0094] S201: Receive a service processing request sent by an electronic device.
[0095] The execution subject of the embodiment of the present application may be a service processing device, or a service processing apparatus arranged in the service processing device. The service processing apparatus may be implemented by software, or by a combination of software and hardware.
[0096] The electronic device may refer to a user's terminal device, and a service processing system may be provided in the electronic device. The visual operation interface of the service processing system may have an "apply" control, and the user may click the "apply" control to enable the electronic device to generate a service processing request. Figure 1 The business request device in.
[0097] The business processing request includes user information and business type, and the business processing request is used to request the processing of the target business. User information is used to indicate a unique user. For example, user information may refer to the user's name and personal ID number, or may refer to the unified social credit code of the user's company. The target business may refer to the business applied for by the user. The business type may be determined based on the target business. For example, if the target business may be credit card processing, the business type corresponding to the target business may be a bank card business type. The business type is used to indicate the type of the target business. For example, the business type may include a deposit business type, a consulting business type, etc.
[0098] Next, combine Figure 3 , through specific examples, the visual operation window of the business processing system is explained.
[0099] Figure 3 For a schematic diagram of a visual operation window of a business processing system provided in an embodiment of the present application, see Figure 3 , including a user information input module, a business type selection module and an "apply" control. The user can input the user's ID in the user information input module, the user can select the business type to be handled in the business type selection module, and generate a business processing request by clicking the "apply" control.
[0100] S202: Generate a service identifier and a target protocol text according to user information, service type and current time.
[0101] The current time may refer to the time when the business processing device receives the business processing request sent by the electronic device. For example, the current time may be 12:45 on October 12, 2024.
[0102] The business identifier can be used to uniquely indicate the number of a business processing request. The business identifier can refer to a string of numbers or a combination of numbers and letters.
[0103] The service identifier can be determined in the following manner: the initial protocol text is obtained in the first database according to the service type, and the target acquisition number is obtained by adding one to the acquisition number, where the target acquisition number is used to indicate the number of times the initial protocol text is obtained in the first database within the current cycle; the service identifier is generated according to the service type, the current time and the target acquisition number.
[0104] The first database may be located in the storage space of the business processing device and may be used to store the initial agreement text. The user may preset the current period, for example, the current period may be one day, one week, one month, etc. The business type may be indicated by numbers or letters, for example, the business type of the deposit business may be indicated by 169.
[0105] For example, assuming that the business type is 169, the current time is 4:36 on October 12, 2024, and the target acquisition number is 45, the business identifier can be 16920241012043645.
[0106] The target protocol text may refer to the protocol text agreed upon by the service processing device and the user. The target protocol text may include user information for applying for service processing, the type of service that the user needs to handle, the time of the service request, and the initial protocol text.
[0107] The target protocol text may be determined in the following manner: an initial protocol text is acquired in a first database according to the service type; and the initial protocol text is updated according to user information, service type and current time to obtain the target protocol text.
[0108] The initial agreement text may refer to an agreement template, which usually includes common terms and agreement content. The update process may refer to the service processing device updating the initial agreement text according to user information, service type and current time, and the update process may include adding user information, service type and current time to the initial agreement text.
[0109] For example, assuming that the user information is Zhang San, the business type is an investment business type, and the current time is 4:36 on October 12, 2024, the initial agreement template may include "Applicant (user information) applies for (business type) at (current time)", then the target agreement text after the update processing may be "Zhang San applied for investment business at 4:36 on October 12, 2024".
[0110] S203: Generate a first random verification code, and generate a protocol document according to the service identifier, the target protocol text and the first random verification code.
[0111] The first random verification code may refer to a character string randomly generated by the service processing device, and the first random verification code may be composed of numbers, letters and symbols, and the first random verification code is unique. The first random verification code is located at the bottom of the protocol document.
[0112] The agreement document can be generated in the following manner: obtain a preset document template; generate a first digital signature corresponding to the target agreement text; fill the business identifier, target agreement text, a first random verification code and a first digital signature into the document template to obtain the agreement document.
[0113] The first digital signature can be used to verify whether the protocol document has been tampered with.
[0114] The first digital signature may be generated in the following manner: obtaining a preset private key; performing a hash operation on the target protocol text using a hash algorithm to obtain a hash value; and encrypting the hash value using the private key to obtain the first digital signature.
[0115] The private key may be determined by a digital certificate preset in the business processing device, and also includes a public key. The public key may be used to verify the signature, and the private key is used to create the signature.
[0116] After the protocol document is generated, the business processing device can also generate a corresponding relationship. The corresponding relationship can be generated in the following way: generate a corresponding relationship between the business identifier, the target protocol text and the first random verification code; set the processing status of the corresponding relationship to a pending confirmation status; and store the corresponding relationship and the processing status in a second database.
[0117] The processing status of the corresponding relationship may include a pending confirmation status and a confirmed status. The second database may be located in the storage space of the business processing device, and is used to store the corresponding relationship and the processing status.
[0118] S204: Send a protocol document to the electronic device, and receive a second random verification code sent by the electronic device.
[0119] The electronic device can receive the protocol document sent by the service processing device and obtain the second random verification code, wherein the second random verification code is located at the bottom of the protocol document, and the second random verification code can be obtained only after the user has finished reading the protocol document on the electronic device.
[0120] The business processing system on the electronic device can also be provided with a second random verification code input module and a "confirm" control. The user can input the obtained second random verification code into the second random verification code input module and click the "confirm" control to send the second random verification to the business processing device.
[0121] S205: When the first random verification code and the second random verification code are the same, process the target service.
[0122] Whether to process the target business can be confirmed in the following way: according to the business identifier, obtain a first random verification code from the second database; determine whether the first random verification code and the second random verification code are the same; if so, process the target business and set the processing status to confirmed status; if not, reject the business processing request.
[0123] Optionally, the first digital signature may be verified to determine whether the protocol document has been tampered with.
[0124] The first digital signature can be verified in the following manner: receiving a verification request, the verification request is used to request verification of whether the protocol document has been tampered with; obtaining the first digital signature in the protocol document according to the verification request; performing a hash operation on the target protocol text in the protocol document through a hash algorithm to obtain a second digital signature; if the first digital signature and the second digital signature are the same, it is determined that the protocol document has not been tampered with; if the first digital signature and the second digital signature are different, it is determined that the protocol document has been tampered with.
[0125] In an embodiment of the present application, when business processing is required, the user information and business type of the target business can be determined according to the business processing request; according to the user information, business type and current time, a business identifier and a target protocol text can be generated; a first random verification code is generated, and a protocol document is generated according to the business identifier, the target protocol text and the first random verification code, and the first random verification code is located at the bottom of the protocol document; the protocol document is sent to an electronic device, the electronic device obtains a second random verification code in the protocol document, and sends it to a business processing device; the business processing device confirms whether the first random verification code and the second random verification code are the same. If they are the same, it indicates that the user has read the protocol text and the content of the protocol text has not been tampered with, thereby improving the reliability of business processing.
[0126] Based on any of the above embodiments, Figure 4 , the generation process of the protocol document ( Figure 2 S202-S203) in the embodiment are described in detail.
[0127] Figure 4 Schematic diagram of the generation process of the protocol document provided in the embodiment of this application. Figure 4 , the method may include:
[0128] S401. Obtain an initial protocol text from a first database according to a service type.
[0129] The initial agreement text may refer to an agreement template, and the initial agreement text may include common terms and agreement contents.
[0130] The initial protocol text may be obtained in the following manner: the service processing device may determine the service type according to the service processing request; and according to the service type, perform a query operation in the first database to obtain the initial protocol text.
[0131] S402: Determine the target acquisition times.
[0132] A counter for recording the number of acquisitions may be provided in the first database. The initial value of the counter may be 0. Each time the service processing device acquires the initial protocol text from the first database, the value of the counter will be increased by one to obtain the target number of acquisitions.
[0133] The target acquisition number may be used to indicate the number of times the service processing device acquires the initial protocol text from the first database in the current cycle. For example, the target acquisition number may be 10 times, 35 times, and the like.
[0134] The current cycle may refer to a cycle that can be preset by the user. Each time a cycle is restarted, the service processing device will clear the value of the counter. For example, assuming that the current cycle is one day, the counter will be cleared at zero every day.
[0135] S403: Generate a service identifier according to the service type, current time and target acquisition times.
[0136] The business type can be converted into numbers or letters for representation; the current moment can be extracted and processed to convert the date and time into numbers. For example, assuming that the business type is a contract signing type, the business type can be represented as QSHT, or the digital representation of the contract signing type can be found as 237 according to the business type comparison table, where the business type comparison table can be a list document pre-set by the user, and the business type comparison table can record the correspondence between business types and numbers; assuming that the current moment is 22:16 on April 18, 2024, the digital representation of the current moment is 202404182216.
[0137] The service identifier may be composed of the service type, the current time, and the target acquisition number. For example, assuming that the service type is 24, the current time is 15:37 on January 24, 2022, and the target acquisition number is 107, the service identifier may be 24202201241537107.
[0138] S404: Determine user-related text, service-related text, and time-related text in the initial agreement text.
[0139] The initial agreement text may include user-related text, business-related text, and time-related text.
[0140] The user-related text may refer to the text related to user information in the initial agreement text, for example, the text related to the applicant of the target service in the agreement. The user-related text contains a position to be filled with user information.
[0141] The business-related text may refer to the relevant text related to the business type in the initial agreement text, for example, the relevant text related to the target business service content corresponding to the business type in the agreement. There is a position to be filled in for the business type in the business-related text.
[0142] The time-related text may refer to the text related to the current time in the initial protocol text, for example, the text related to the start time of the target service in the protocol. The time-related text has a position to be filled in at the current time.
[0143] S405: Update the user-related text according to the user information, update the service-related text according to the service type, and update the time-related text according to the current time to obtain the target protocol text.
[0144] The target protocol text can be obtained in the following manner: update the user information to the to-be-filled position of the user information in the user-related text, update the service type to the to-be-filled position of the service type in the service-related text, and update the current time to the to-be-filled position of the current time in the time-related text to obtain the target protocol text.
[0145] S406: Obtain a preset document template.
[0146] The preset document template may refer to a layout template of the target protocol document, and the service identifier, the target protocol text, the first random verification code and the first digital signature may be layouted according to the preset document template. The preset document template may be obtained in the first database.
[0147] S407: Generate a first digital signature corresponding to the target protocol text.
[0148] It should be noted that the execution process of the above S407 can refer to S203, which will not be repeated here.
[0149] S408: Fill the service identifier, the target agreement text, the first random verification code and the first digital signature into the document template to obtain the agreement document.
[0150] For the first random verification code, a description text may also be generated before the first random verification code, and the description text is used to describe that the user has read and confirmed all the contents in the target agreement text. For example, the description text may be "Before obtaining this verification code, I have read and agreed to all the contents in this agreement."
[0151] According to the preset document template, the service identifier, the target agreement text, the first random verification code, the first digital signature and the description text may be typeset to obtain the agreement document.
[0152] Next, combine Figure 5 , the protocol document is explained through specific examples.
[0153] Figure 5 For a schematic diagram of the protocol document provided for the embodiment of this application, please see Figure 5The protocol document includes a service identifier, a target protocol text, a first random verification code, a first digital signature and a description text, and the first random verification code is located at the bottom of the protocol document.
[0154] In an embodiment of the present application, when business processing is required, a protocol document needs to be generated. According to the business type, the initial protocol text can be obtained from the first database; the target acquisition number is determined according to the number of times the business processing device obtains the initial protocol text from the first database in the current cycle; the business identifier is generated according to the business type, the current time and the target acquisition number; the user-related text, business-related text and time-related text are determined in the initial protocol text, and the user-related text is updated according to the user information, the business-related text is updated according to the business type, and the time-related text is updated according to the current time to obtain the target protocol text; the preset document template is obtained, and the first digital signature corresponding to the target protocol text is generated; the business identifier, the target protocol text, the first random verification code and the first digital signature are filled in according to the preset document template to obtain the protocol document. By setting a random verification code at the bottom of the protocol document, the reliability of business processing is improved.
[0155] Based on any of the above embodiments, Figure 6 , the interaction process between the service processing device and the service requesting device (electronic device) is described in detail.
[0156] Figure 6 Schematic diagram of the interaction process between the service processing device and the service request device (electronic device) provided in the embodiment of the present application. Figure 6 , the method may include:
[0157] S601: A service request device sends a service request to a service processing device.
[0158] S602: The service processing device generates a service identifier and a target protocol text according to user information, service type and current time.
[0159] S603: The service processing device generates a first random verification code, and generates a protocol document according to the service identifier, the target protocol text and the first random verification code.
[0160] S604: The service processing device sends a protocol document to the service requesting device.
[0161] S605: The service requesting device obtains a second random verification code according to the protocol document.
[0162] S606: The service requesting device sends a second random verification code to the service processing device.
[0163] S607: The service processing device compares the first random verification code and the second random verification code to see whether they are the same.
[0164] S608: If they are the same, process the target business.
[0165] A business processing method provided in an embodiment of the present application can execute the technical solution shown in the above method embodiment, and its implementation principle and beneficial effects are similar, which will not be repeated here.
[0166] Figure 7 This is a schematic diagram of the structure of a service processing device provided in an embodiment of the present application. Figure 7 The service processing device 10 includes: a receiving module 11, a first generating module 12, a second generating module 13, a transceiver module 14 and a processing module 15, wherein:
[0167] The receiving module 11 is used to receive a service processing request sent by an electronic device, wherein the service processing request includes user information and a service type, and the service processing request is used to request processing of a target service;
[0168] The first generating module 12 is used to generate a service identifier and a target protocol text according to the user information, the service type and the current time;
[0169] The second generating module 13 is used to generate a first random verification code, and generate a protocol document according to the service identifier, the target protocol text and the first random verification code, wherein the first random verification code is located at the bottom of the protocol document;
[0170] The transceiver module 14 is used to send the protocol document to the electronic device and receive a second random verification code sent by the electronic device;
[0171] The processing module 15 is configured to process the target service when the first random verification code and the second random verification code are the same.
[0172] A business processing device provided in an embodiment of the present application can execute the technical solution shown in the above method embodiment, and its implementation principle and beneficial effects are similar, which will not be repeated here.
[0173] In a possible design, the first generating module 12 is specifically used for:
[0174] Acquire an initial protocol text in the first database according to the service type, and add one to the acquisition number to obtain a target acquisition number, where the target acquisition number is used to indicate the number of times the initial protocol text is acquired in the first database in the current cycle;
[0175] Generate the service identifier according to the service type, the current time and the target acquisition number;
[0176] The initial protocol text is updated according to the user information, the service type and the current time to obtain the target protocol text.
[0177] In a possible design, the first generating module 12 is specifically used for:
[0178] Determining user-related text, service-related text and time-related text in the initial agreement text;
[0179] In the initial protocol text, the user-related text is updated according to the user information, the service-related text is updated according to the service type, and the time-related text is updated according to the current moment to obtain the target protocol text.
[0180] In a possible design, the second generating module 13 is specifically used for:
[0181] Get the preset document template;
[0182] Generate a first digital signature corresponding to the target protocol text;
[0183] The service identifier, the target agreement text, the first random verification code and the first digital signature are filled into the document template to obtain the agreement document.
[0184] In a possible design, the second generating module 13 is specifically used for:
[0185] Get the preset private key;
[0186] Performing a hash operation on the target protocol text by using a hash algorithm to obtain a hash value;
[0187] The hash value is encrypted using the private key to obtain the first digital signature.
[0188] In a possible design, the second generating module 13 is further used for:
[0189] Generate a correspondence between the service identifier, the target protocol text and the first random verification code;
[0190] Setting the processing status of the corresponding relationship to a pending confirmation status;
[0191] In the second database, the corresponding relationship and the processing status are stored correspondingly.
[0192] In a possible design, the second generating module 13 is further used for:
[0193] According to the service identifier, obtaining the first random verification code from the second database;
[0194] Determining whether the first random verification code and the second random verification code are the same;
[0195] If yes, the target business is processed and the processing status is set to a confirmed status.
[0196] Figure 8 A schematic diagram of the structure of another service processing device provided in an embodiment of the present application. Figure 7 Based on the examples shown, see Figure 8 The business processing device 10 further includes: a receiving and obtaining module 16, a calculation module 17 and a determination module 18, wherein:
[0197] The receiving and obtaining module 16 is specifically used to receive a verification request, where the verification request is used to request verification of whether the protocol document has been tampered with; and obtain the first digital signature in the protocol document according to the verification request;
[0198] The operation module 17 is specifically used to perform a hash operation on the target protocol text in the protocol document through a hash algorithm to obtain a second digital signature;
[0199] The determination module 18 is specifically used to determine that the protocol document has not been tampered with if the first digital signature and the second digital signature are the same; if the first digital signature and the second digital signature are not the same, determine that the protocol document has been tampered with.
[0200] A business processing device provided in an embodiment of the present application can execute the technical solution shown in the above method embodiment, and its implementation principle and beneficial effects are similar, which will not be repeated here.
[0201] Fig. 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Fig. 9 As shown, the electronic device 20 may include: a transceiver 21 , a processor 22 , and a memory 23 .
[0202] The processor 22 executes the computer execution instructions stored in the memory, so that the processor 22 executes the scheme in the above embodiment. The processor 22 can be a general-purpose processor, including a central processing unit CPU, a network processor (NP), etc.; it can also be a digital signal processor DSP, an application-specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
[0203] The memory 23 is connected to the processor 22 via a system bus and completes communication between them. The memory 23 is used to store computer program instructions.
[0204] The transceiver 21 may be used to obtain tasks to be executed and configuration information of the tasks to be executed.
[0205] The system bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The system bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. The transceiver is used to realize the communication between the database access device and other computers (such as clients, read-write libraries, and read-only libraries). The memory may include random access memory (RAM) and may also include non-volatile memory.
[0206] The electronic device provided in the embodiment of the present application may be the terminal device of the above embodiment.
[0207] An embodiment of the present application also provides a chip for running instructions, which is used to execute the technical solution of the business processing method in the above embodiment.
[0208] An embodiment of the present application further provides a computer-readable storage medium, in which computer instructions are stored. When the computer instructions are executed on a computer, the computer executes the technical solution of the business processing method in the above embodiment.
[0209] An embodiment of the present application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium. When at least one processor executes the computer program, it can implement the technical solution of the business processing method in the above embodiment.
[0210] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of modules is only a logical function division, and there may be other division methods in actual implementation, such as multiple modules can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, which can be electrical, mechanical or other forms.
[0211] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to implement the solution of this embodiment.
[0212] In addition, each functional module in each embodiment of the present application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The above-mentioned module-composed unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
[0213] The above-mentioned integrated module implemented in the form of a software function module can be stored in a computer-readable storage medium. The above-mentioned software function module is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform some steps of the methods of various embodiments of the present application.
[0214] It should be understood that the above processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the invention can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor.
[0215] The memory may include a high-speed RAM memory, and may also include a non-volatile storage NVM, such as at least one disk memory, and may also be a USB flash drive, a mobile hard disk, a read-only memory, a magnetic disk or an optical disk, etc.
[0216] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of this application is not limited to only one bus or one type of bus.
[0217] The above storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The storage medium can be any available medium that can be accessed by a general or special purpose computer.
[0218] An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the storage medium can also exist as discrete components in an electronic control unit or a main control device.
[0219] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.
[0220] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.
Claims
1. A business processing method, characterized in that: include: Receiving a service processing request sent by an electronic device, the service processing request including user information and a service type, the service processing request being used to request processing of a target service; Generate a service identifier and a target protocol text according to the user information, the service type and the current time; Generate a first random verification code, and generate a protocol document according to the service identifier, the target protocol text and the first random verification code, wherein the first random verification code is located at the bottom of the protocol document; Sending the protocol document to the electronic device, and receiving a second random verification code sent by the electronic device; When the first random verification code and the second random verification code are the same, the target service is processed.
2. The method according to claim 1, characterized in that Generate a service identifier and a target protocol text according to the user information, the service type and the current time, including: Acquire an initial protocol text in the first database according to the service type, and add one to the acquisition number to obtain a target acquisition number, where the target acquisition number is used to indicate the number of times the initial protocol text is acquired in the first database in the current cycle; Generate the service identifier according to the service type, the current time and the target acquisition number; The initial protocol text is updated according to the user information, the service type and the current time to obtain the target protocol text.
3. The method according to claim 2, characterized in that The initial protocol text is updated according to the user information, the service type and the current time to obtain the target protocol text, including: Determining user-related text, service-related text and time-related text in the initial agreement text; In the initial protocol text, the user-related text is updated according to the user information, the service-related text is updated according to the service type, and the time-related text is updated according to the current moment to obtain the target protocol text.
4. The method according to any one of claims 1 to 3, characterized in that: Generating a protocol document according to the service identifier, the target protocol text and the first random verification code includes: Get the preset document template; Generate a first digital signature corresponding to the target protocol text; The service identifier, the target agreement text, the first random verification code and the first digital signature are filled into the document template to obtain the agreement document.
5. The method according to claim 4, characterized in that Generating a first digital signature corresponding to the target protocol text includes: Get the preset private key; Performing a hash operation on the target protocol text by using a hash algorithm to obtain a hash value; The hash value is encrypted using the private key to obtain the first digital signature.
6. The method according to any one of claims 1 to 5, characterized in that: After the protocol document is generated according to the service identifier, the target protocol text and the first random verification code, the method further includes: Generate a correspondence between the service identifier, the target protocol text and the first random verification code; Setting the processing status of the corresponding relationship to a pending confirmation status; In the second database, the corresponding relationship and the processing status are stored correspondingly.
7. The method according to claim 6, characterized in that When the first random verification code and the second random verification code are the same, processing the target service includes: According to the service identifier, obtaining the first random verification code from the second database; Determining whether the first random verification code and the second random verification code are the same; If yes, the target business is processed and the processing status is set to a confirmed status.
8. The method according to any one of claims 1 to 7, characterized in that: The protocol document also includes a first digital signature; the method also includes: receiving a verification request, wherein the verification request is used to request verification of whether the protocol document has been tampered with; Acquire the first digital signature in the protocol document according to the verification request; Performing a hash operation on the target protocol text in the protocol document by using a hash algorithm to obtain a second digital signature; If the first digital signature and the second digital signature are the same, it is determined that the protocol document has not been tampered with; If the first digital signature and the second digital signature are not identical, it is determined that the protocol document has been tampered with.
9. A service processing device, characterized in that: include: A receiving module, a first generating module, a second generating module, a transceiver module and a processing module, wherein: The receiving module is used to receive a service processing request sent by an electronic device, wherein the service processing request includes user information and a service type, and the service processing request is used to request processing of a target service; The first generating module is used to generate a service identifier and a target protocol text according to the user information, the service type and the current time; The second generating module is used to generate a first random verification code, and generate a protocol document according to the service identifier, the target protocol text and the first random verification code, wherein the first random verification code is located at the bottom of the protocol document; The transceiver module is used to send the protocol document to the electronic device and receive a second random verification code sent by the electronic device; The processing module is used for processing the target service when the first random verification code and the second random verification code are the same.
10. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 8.
11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 8 when executed by a processor.
12. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 8 when being executed by a processor.
