Data processing method, apparatus, device, medium, and program product

Abstract

The application provides a data processing method, device, equipment, medium and program product, relates to the technical field of financial technology, and the method comprises the steps that a protocol identifier associated with a user is acquired, a current protocol version is determined in a preset protocol rule configuration information table, a protocol text identifier is obtained in a preset protocol version configuration information table according to the protocol identifier and the current protocol version, protocol content information is acquired in a preset protocol text configuration table according to the protocol identifier and the protocol text identifier, confirmation information input by the user according to the protocol content information is acquired, a block chain transaction identifier is generated according to the protocol content information and the confirmation information, the confirmation information at least includes a user identifier and a protocol confirmation date, and the user identifier, the protocol identifier, the current protocol version, the protocol confirmation date and the block chain transaction identifier are stored in a preset protocol signing information table in association. The technical scheme can avoid that the user signs a low-version protocol, and improves the accuracy of protocol signing.

Description

Technical Field

[0001] This application relates to the field of financial technology, and in particular to a data processing method, apparatus, device, medium, and program product. Background Technology

[0002] Currently, before conducting business through online channels, users typically sign an agreement document to outline various terms and requirements. By signing this agreement, users acknowledge its contents and reach a consensus with the service provider.

[0003] In existing technologies, when signing an agreement, the content of the agreement, the confirmation information submitted by the user during the signing process, and the signing date are usually recorded. After the recording is completed, this agreement-related information is saved.

[0004] However, with the rapid iteration and update of the protocol version in this existing technology, users may sign an older version of the protocol due to the lack of differentiation between the old and new versions after a new version is released, resulting in an error in signing the agreement. Summary of the Invention

[0005] This application provides a data processing method, apparatus, device, medium, and program product to address the problem that existing protocol versions are updated rapidly, making it easy for users to sign outdated protocols and causing errors in protocol signing.

[0006] In a first aspect, embodiments of this application provide a data processing method, including:

[0007] When the conditions for signing the agreement are triggered, obtain the agreement identifier associated with the user;

[0008] The current protocol version associated with the protocol identifier is determined in the preset protocol rule configuration information table;

[0009] Based on the protocol identifier and the current protocol version, the protocol body information associated with the protocol identifier and the current protocol version is obtained by querying the preset protocol version configuration information table. The protocol body information includes at least the protocol text identifier.

[0010] Based on the protocol identifier and protocol text identifier, obtain the protocol content information associated with the protocol identifier and protocol text identifier from the preset protocol text configuration table;

[0011] Obtain confirmation information input by the user based on the protocol content information, and generate a blockchain transaction identifier based on the protocol content information and the confirmation information. The confirmation information includes at least the user identifier and the protocol confirmation date.

[0012] The user identifier, protocol identifier, current protocol version, protocol confirmation date, and blockchain transaction identifier are associated and stored in a preset protocol signing information table.

[0013] In one possible design of the first aspect, obtaining the protocol identifier associated with the user includes:

[0014] In response to receiving a user's transaction request, a transaction identifier is obtained from the transaction request;

[0015] Based on the transaction identifier, the protocol identifier corresponding to the transaction identifier is obtained by querying the preset transaction and protocol configuration relationship table.

[0016] In another possible design of the first aspect, the method further includes:

[0017] Obtain the user's user identifier;

[0018] Based on the user identifier and the agreement identifier, determine whether there is a historical blockchain transaction identifier associated with the user identifier and the agreement identifier in the preset agreement signing information table;

[0019] If the historical blockchain transaction identifier exists in the preset protocol signing information table, then the historical protocol version, current protocol version, and version compatibility identifier associated with the protocol identifier are obtained from the preset protocol rule configuration information table.

[0020] Based on the historical protocol version associated with the protocol identifier, the current protocol version, and the version compatibility identifier, determine whether the conditions for triggering the agreement signing are met.

[0021] In another possible design of the first aspect, the triggering conditions for signing the agreement include:

[0022] The agreement signing conditions are triggered when the historical protocol version is different from the current protocol version and the version compatibility identifier indicates that the historical protocol version is incompatible with the current protocol version.

[0023] In another possible design of the first aspect, the triggering conditions for signing the agreement include:

[0024] If the historical blockchain transaction identifier is not present in the preset agreement signing information table, the agreement signing conditions are triggered.

[0025] In yet another possible design of the first aspect, the method further includes:

[0026] In response to a protocol version update request associated with the protocol identifier, the release date and version compatibility identifier of the protocol version to be updated are obtained from the protocol version update request;

[0027] The release date and version compatibility identifier of the protocol version to be updated are associated with and updated in the preset protocol rule configuration information table.

[0028] In yet another possible design of the first aspect, the method further includes:

[0029] Obtain the protocol text identifier, protocol effective date, protocol description information, and identifier information of the protocol publishing object associated with the protocol version to be updated;

[0030] Update the protocol text identifier, version release date, protocol effective date, protocol description information, and identifier information of the protocol release object to the preset protocol version configuration information table.

[0031] In yet another possible design of the first aspect, the method includes:

[0032] Obtain the protocol content information associated with the protocol version to be updated;

[0033] Update the protocol text identifier and protocol content information to the preset protocol text configuration table.

[0034] Secondly, embodiments of this application provide a data processing apparatus, including:

[0035] The protocol identifier acquisition module is used to acquire the protocol identifier associated with the user when the conditions for signing the agreement are triggered.

[0036] The protocol version acquisition module is used to determine the current protocol version associated with the protocol identifier from the preset protocol rule configuration information table;

[0037] The protocol information acquisition module is used to query the protocol body information associated with the protocol identifier and the current protocol version in a preset protocol version configuration information table based on the protocol identifier and the current protocol version. The protocol body information includes at least the protocol text identifier.

[0038] The protocol content acquisition module is used to obtain protocol content information associated with the protocol identifier and the protocol text identifier from a preset protocol text configuration table based on the protocol identifier and the protocol text identifier.

[0039] The identifier generation module is used to obtain the confirmation information input by the user according to the protocol content information, and generate a blockchain transaction identifier according to the protocol content information and the confirmation information. The confirmation information includes at least the user identifier and the protocol confirmation date.

[0040] The associated storage module is used to associate and store the user identifier, protocol identifier, current protocol version, protocol confirmation date, and blockchain transaction identifier into a preset protocol signing information table.

[0041] Thirdly, embodiments of this application provide a computer device, including: a processor, and a memory communicatively connected to the processor; the memory stores computer execution instructions; the processor executes the computer execution instructions stored in the memory to implement the method described above.

[0042] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer instructions that, when executed by a processor, are used to implement the method described above.

[0043] Fifthly, embodiments of this application provide a computer program product, including computer instructions that, when executed by a processor, implement the above-described method.

[0044] The data processing method, apparatus, device, medium, and program product provided in this application embodiment can establish a protocol rule configuration information table, manage the protocol versions in the protocol rule configuration information table in real time, promptly discover the latest version of the protocol and output it to the user for signing, thereby improving the accuracy of protocol signing. Attached Figure Description

[0045] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application;

[0046] Figure 1 A schematic diagram of a scenario for the data processing method provided in the embodiments of this application;

[0047] Figure 2 A flowchart illustrating the data processing method provided in an embodiment of this application;

[0048] Figure 3 A schematic diagram of an agreement signing information table provided in an embodiment of this application;

[0049] Figure 4 A schematic diagram of the preset protocol rule configuration information table provided in the embodiments of this application;

[0050] Figure 5 A schematic diagram of a preset protocol version configuration information table provided in an embodiment of this application;

[0051] Figure 6 A schematic diagram of a preset protocol text configuration table provided in an embodiment of this application;

[0052] Figure 7 A schematic diagram of a preset agreement signing information table provided in an embodiment of this application;

[0053] Figure 8A schematic diagram of the preset transaction and protocol configuration relationship table provided in the embodiments of this application;

[0054] Figure 9 A schematic diagram of the configuration information table for the updated preset protocol rules;

[0055] Figure 10 This is a representation of the updated preset protocol version configuration information provided in the embodiments of this application.

[0056] Figure 11 A schematic diagram of the agreement signing process provided in this application embodiment;

[0057] Figure 12 This is a schematic diagram of the structure of the data processing apparatus provided in the embodiments of this application;

[0058] Figure 13 A schematic diagram of the structure of a computer device provided in an embodiment of this application.

[0059] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0060] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0061] It should be noted that the data processing methods, apparatus, equipment, media, and programs disclosed herein can be used in the financial sector, as well as in any other sector. The application areas of these data processing methods, apparatus, equipment, media, and programs are not limited.

[0062] Figure 1 This is a schematic diagram of a scenario for the data processing method provided in the embodiments of this application, such as... Figure 1As shown, a network connection is established between a terminal device 11 (such as a smartphone, personal laptop, tablet, etc.) and a server 12, allowing users to conduct business online through the terminal device 11. Before conducting business, the terminal device 11 typically displays various agreements related to the business. After the user reads and confirms the signing of these agreements, it signifies that the user is aware of the agreement content, allowing the server 12 to continue providing business services to the user. However, because agreements are usually updated and iterated rapidly, and the agreement signing process typically only focuses on the agreement content, the agreement signing date, and the signing confirmation information submitted by the user, users are often unsure whether they have signed the latest version of the agreement. For example, an agreement may include the latest version 1.1 and the older version 1.0. Different versions may be compatible or incompatible. In the case of version incompatibility, if the user signs the 1.0 version agreement, it is equivalent to signing an incorrect agreement, requiring the user to re-sign the new version. This results in low efficiency and low accuracy of agreement signing.

[0063] To address the aforementioned issues, the data processing methods, apparatus, devices, media, and program products provided in this application, in order to resolve the problem of users signing the wrong version of the agreement due to the rapid pace of agreement updates, require version checking to ensure that users sign the latest version. Specifically, by establishing a protocol rule configuration information table and managing the protocol versions in the table in real time, the latest version of the agreement can be promptly identified and provided to the user for signing, thereby improving the accuracy of agreement signing.

[0064] The technical solution of this application will now be described in detail through specific embodiments. It should be noted that the following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0065] Figure 2 This is a flowchart illustrating the data processing method provided in an embodiment of this application. This method can be applied to processing devices such as computer equipment or servers. Taking a server as the executing entity as an example, ... Figure 2 As shown, the method may specifically include the following steps: Step S201, when the conditions for signing the agreement are triggered, obtain the agreement identifier associated with the user.

[0066] In this embodiment, taking the need for a user to conduct a transaction as an example, different users typically have corresponding user IDs and transaction IDs when conducting different transactions. The user ID identifies different users, and the transaction ID identifies different transactions.

[0067] The conditions for signing the agreement are triggered based on the user's relevant information, such as whether the user has signed an agreement before conducting the transaction. If no agreement has been signed before, the conditions for signing the agreement will be triggered. Similarly, if the user has previously signed an older version of the agreement when conducting the transaction, the conditions for signing the agreement will also be triggered, requiring the user to sign a new version of the agreement.

[0068] In this embodiment, the protocol identifier can refer to a protocol ID. Different protocols have different protocol IDs, while different versions of the protocol have the same protocol ID. For example, Figure 3 This is a schematic diagram of the agreement signing information table provided in an embodiment of this application. The server can pre-build the agreement signing information table and store it in a database. When a user initiates a business request, the server can query the agreement ID (i.e., the agreement identifier) ​​associated with that user based on the user's user ID. The agreement signing information table can also store relevant transaction description information, providing a brief description of the transaction.

[0069] Step S202: Determine the current protocol version associated with the protocol identifier in the preset protocol rule configuration information table.

[0070] In this embodiment, a relationship between protocol identifiers and protocol versions is established in the preset protocol rule configuration information table. By using the protocol identifier, the current protocol version (i.e., the latest protocol version) can be found in the preset protocol rule configuration information table. Figure 4 A schematic diagram of the preset protocol rule configuration information table provided in the embodiments of this application, as shown below. Figure 4 As shown, different protocol IDs (i.e., protocol identifiers) are associated with corresponding current latest version, previous version, version compatibility identifier, and version start date. The same protocol ID may have one current latest version and one previous version, or it may only have one current latest version.

[0071] Step S203: Based on the protocol identifier and the current protocol version, query the preset protocol version configuration information table to obtain the protocol body information associated with the protocol identifier and the current protocol version. The protocol body information includes at least the protocol text identifier.

[0072] In this embodiment, the same protocol identifier may have different versions, such as those described above. Figure 4 Taking the protocol ID "00002" as an example, it includes both the current latest version 1.2 and the older version 1.1. The same protocol ID is associated with different protocol body information in different versions.

[0073] For example, Figure 5 A schematic diagram of the preset protocol version configuration information table provided in the embodiments of this application, as shown below. Figure 5As shown, the preset protocol version configuration information table includes protocol ID "00001" and protocol ID "00002". Protocol ID "00001" has two protocol versions (i.e., version 1.0 and version 1.1). The protocol body information corresponding to different versions is different (including protocol text ID (protocol text identifier), protocol brief description, protocol release date, protocol effective date, and protocol publisher ID (i.e., the identifier information of the protocol publisher object)).

[0074] Step S204: Based on the protocol identifier and the protocol text identifier, obtain the protocol content information associated with the protocol identifier and the protocol text identifier from the preset protocol text configuration table.

[0075] In this embodiment, the preset protocol text configuration table stores protocol ID, protocol text ID, and protocol content information. The protocol content information can be in the form of a hash value, i.e., a protocol text hash. For example, Figure 6 A schematic diagram of the preset protocol text configuration table provided in the embodiments of this application, as shown below. Figure 6 As shown, each protocol ID and protocol text ID has a corresponding protocol text hash and blockchain evidence ID (the protocol text hash and blockchain evidence ID contain protocol content information). By using the protocol ID and protocol text ID, the associated protocol content information can be found from the preset protocol text configuration table.

[0076] Step S205: Obtain the confirmation information input by the user based on the agreement content information, and generate a blockchain transaction identifier based on the agreement content information and the confirmation information. The confirmation information includes at least the user identifier and the agreement confirmation date.

[0077] In this embodiment, the blockchain transaction identifier can refer to the blockchain transaction ID, and the confirmation information can be user information entered by the user (such as user signature, user fingerprint, etc.). The blockchain transaction identifier refers to the blockchain ID, and the confirmation information, blockchain evidence ID and agreement signing date are bound together to form the blockchain transaction ID.

[0078] The agreement content information can be displayed in the above-mentioned sections. Figure 1 The terminal device 11 displays the agreement for users to view. After reading it, users can enter their personal signature, fingerprint, or other information as part of the confirmation information, representing that the user has confirmed that they have signed the agreement.

[0079] Step S206: Associate and store the user identifier, protocol identifier, current protocol version, protocol confirmation date, and blockchain transaction identifier in a preset protocol signing information table.

[0080] For example, Figure 7 This is a schematic diagram of a preset agreement signing information table provided in an embodiment of this application, as shown below. Figure 7 As shown, each user ID is associated with a protocol ID, protocol version, protocol confirmation date, and blockchain transaction ID.

[0081] This application embodiment establishes a protocol rule configuration information table to manage the protocol versions in the table in real time. This allows for the timely discovery of the latest version of the protocol and its output to the user for signing, improving the accuracy of protocol signing. Furthermore, after the agreement is signed, related protocol information is stored in a preset protocol signing information table for recording, allowing users to view their protocol signing records in real time and effectively maintain and manage the signed agreements.

[0082] In some embodiments, the "obtaining the protocol identifier associated with the user" in step S201 above can be implemented through the following steps: in response to receiving a user's transaction request, obtaining the transaction identifier from the transaction request; and querying the preset transaction and protocol configuration relationship table to obtain the protocol identifier corresponding to the transaction identifier based on the transaction identifier.

[0083] In this embodiment, when a user initiates a transaction request, the transaction request carries a user ID and a transaction ID (i.e., a transaction identifier). The preset transaction and protocol configuration relationship table includes each transaction ID and the protocol ID (i.e., a protocol identifier) ​​associated with the transaction ID.

[0084] For example, Figure 8 A schematic diagram of the preset transaction and protocol configuration relationship table provided in the embodiments of this application, as shown below. Figure 8 As shown, the protocol ID associated with transaction ID "T00001" is "000001", and the protocol ID associated with transaction ID "00002" is "000002". For example, the preset transaction and protocol configuration relationship table also includes transaction description information.

[0085] This application embodiment maintains the association between transaction IDs and protocol IDs by setting a preset transaction and protocol configuration relationship table. When a user initiates a transaction request, the associated protocol ID can be found based on the transaction ID. Based on the protocol ID, it is convenient and quick to find out which protocols are needed for this transaction, which improves the efficiency and accuracy of transactions and also facilitates maintenance and management by staff.

[0086] In some embodiments, the above method further includes the step of obtaining the user's user identifier;

[0087] Based on the user identifier and the agreement identifier, determine whether there is a historical blockchain transaction identifier associated with the user identifier and the agreement identifier in the preset agreement signing information table; if there is a historical blockchain transaction identifier in the preset agreement signing information table, obtain the historical agreement version, current agreement version and version compatibility identifier associated with the agreement identifier from the preset agreement rule configuration information table; based on the historical agreement version, current agreement version and version compatibility identifier associated with the agreement identifier, determine whether the conditions for triggering agreement signing are met.

[0088] In this embodiment, the preset agreement signing information table stores the agreements signed by users, which are associated with user IDs (i.e., user identifiers). For example, please refer to the above... Figure 7 When a user with user ID "C0000011" initiates a transaction request, the system can find the protocol signed by that user in the preset protocol signing information table (i.e., the protocol with protocol ID "000001"). The blockchain transaction ID of this protocol is "c031d365d1fa", and the protocol version is 1.1. Based on the protocol ID "000001", the system can find the latest version of this protocol in the preset rule information configuration table, which is 1.1. The historical version is also "1.1", and the version compatibility flag is "No". Based on this information associated with the protocol ID in the preset rule information configuration table, it can be determined that the protocol signed by the user is the latest version, and there is no need to trigger the protocol signing conditions again.

[0089] This application embodiment allows users to view a preset agreement signing information table to see whether they have signed an agreement before. When a user has signed an agreement, the system can also determine whether the agreement version has been updated based on the signed agreement identifier. If an update exists, the agreement signing conditions need to be triggered to re-sign the latest version of the agreement, ensuring the accuracy of the agreements signed by the user.

[0090] Furthermore, based on the above embodiments, in some other embodiments, when determining whether to trigger the agreement signing conditions, the following steps can be taken: when the historical protocol version is different from the current protocol version and the version compatibility flag indicates that the historical protocol version is incompatible with the current protocol version, the agreement signing conditions are triggered.

[0091] In this embodiment, reference continues to the above. Figure 4 , Figure 4The system provides two protocol IDs: protocol ID "000001" and protocol ID "000002". Protocol ID "000001" currently has a latest version of 1.1, with a protocol compatibility indicator of "No". Its historical protocol version is 1.1, meaning the protocol version has not changed and the agreement signing conditions will not be triggered. As for protocol ID "000002", its current latest version is 1.2, with a protocol compatibility indicator of "Yes". Its historical protocol version is 1.1. Since the historical protocol version is compatible with the latest protocol version, the agreement signing conditions will also not be triggered.

[0092] For example, for protocol ID "000002", if the protocol compatibility flag is "No", and the current latest version is 1.2, while the historical protocol version is 1.1, then the protocol signing conditions will be triggered.

[0093] This application embodiment can quickly determine whether a user needs to re-sign the agreement by searching the historical agreement version, current agreement version, and version compatibility identifier recorded in the preset agreement rule configuration information table. It also facilitates the maintenance and management of various agreement versions, ensuring that when a new version of the agreement is released, the user can sign the latest version of the agreement, further improving the accuracy of agreement signing.

[0094] In other embodiments, the "triggering the agreement signing conditions" in step S201 above can be specifically implemented by the following steps: if there is no historical blockchain transaction identifier in the preset agreement signing information table, then the agreement signing conditions are triggered.

[0095] In this embodiment, if there is no historical blockchain transaction identifier in the preset agreement signing information table, it means that the user has not signed an agreement. If the user initiates a transaction request, he / she needs to sign an agreement related to the transaction.

[0096] Specifically, when a user signs an agreement related to the transaction, the associated agreement ID can be obtained from the preset transaction and agreement configuration relationship table based on the transaction ID. Then, based on the agreement ID, the latest version of the agreement can be found from the preset agreement rule configuration information table and output to the user, so that the user can sign the latest version of the agreement.

[0097] This application embodiment maintains a preset agreement signing information table to determine whether there is a historical blockchain transaction identifier in the preset agreement signing information table. When there is no historical blockchain transaction identifier, the agreement signing conditions can be triggered to obtain the latest version of the agreement for the user to sign, which facilitates the management and maintenance of user agreement signing and improves the efficiency of user agreement signing.

[0098] In some embodiments, the above method further includes the following steps: in response to a protocol version update request associated with a protocol identifier, obtaining the version release date and version compatibility identifier of the protocol version to be updated from the protocol version update request; and associating the version release date and version compatibility identifier of the protocol version to be updated with a preset protocol rule configuration information table.

[0099] In this embodiment, when a new version of the protocol is released, the relevant information of the new version needs to be maintained and updated in the preset protocol rule configuration information table. For example, refer to the above... Figure 4 When a new version of the protocol is released, the protocol version and version compatibility identifier of the new version can be maintained in the preset protocol rule configuration information table.

[0100] For example, Figure 9 This diagram illustrates the configuration information table for the updated preset protocol rules. Taking the protocol ID "000001" as an example, it shows a new version 1.3 that needs to be released. Figure 9 As shown, the latest version of protocol ID "000001" is 1.3, the historical version is 1.2, and the version compatibility indicator is "No".

[0101] This application embodiment maintains and updates the preset protocol rule configuration information table, ensuring that after a new version of the protocol is released, the latest protocol version can be found for users to sign. It also makes it easier for protocol maintenance personnel to see protocol version changes, preventing users from signing incompatible low-version protocols and further improving the accuracy of protocol signing.

[0102] Furthermore, based on the above embodiments, in some embodiments, the above method further includes: obtaining the protocol text identifier, protocol effective date, protocol description information and identifier information of the protocol publishing object associated with the protocol version to be updated; and updating the protocol text identifier, version release date, protocol effective date, protocol description information and identifier information of the protocol publishing object to a preset protocol version configuration information table.

[0103] In this embodiment, reference continues to the above. Figure 5 The preset protocol version configuration information table includes the protocol ID, the protocol version associated with the protocol ID, the protocol text ID, the protocol release date, the protocol effective date, the protocol description information, and the identification information of the protocol publishing object (i.e., the ID of the protocol publisher). For example, Figure 10 The updated preset protocol version configuration information provided in the embodiments of this application represents the intended meaning, such as... Figure 10As shown, the protocol version of protocol ID "000001" will be updated to 1.3, the protocol text ID is "10000003", the protocol release date is 2022 / 1 / 1, the protocol effective date is 2022 / 1 / 1, and the protocol publisher ID is 33333.

[0104] This application embodiment maintains and updates the preset protocol version configuration information table, ensuring that after a new version of the protocol is released, the latest protocol version can be found based on the protocol ID for users to sign. It also makes it easier for protocol maintenance personnel to see protocol version changes, preventing users from signing incompatible low-version protocols and further improving the accuracy of protocol signing.

[0105] In other embodiments, the method further includes the following steps: obtaining protocol content information associated with the protocol version to be updated; and updating the protocol text identifier and protocol content information to a preset protocol text configuration table.

[0106] In this embodiment, reference continues to the above. Figure 6 For example, when a new version of the protocol associated with the protocol ID "10000001" is released, the protocol content information associated with the protocol ID "10000001" will also be updated in the preset protocol text configuration table.

[0107] This application embodiment maintains and updates the preset protocol text configuration table, ensuring that after a new version of the protocol is released, the latest protocol version can be found based on the protocol ID for users to sign. It also makes it easier for protocol maintenance personnel to see protocol version changes, preventing users from signing incompatible low-version protocols and further improving the accuracy of protocol signing.

[0108] For example, Figure 11 This is a schematic diagram of the agreement signing process provided in an embodiment of this application, such as... Figure 11 As shown, it includes the following steps: S1110, User accesses the function. Step S1120, Obtain the protocol ID. Step S1130, Determine if the user needs to sign an agreement. Step S1131, Check if the user has previously signed an agreement. Step S1132, If the user has previously signed an agreement, determine if the agreement is valid. Step S1133, If the protocol version is compatible, then signing an agreement is not required. Step S1140, Obtain protocol configuration information. Step S1150, Query the protocol rule configuration information table. Step S1160, Query the protocol version configuration information table. Step S1170, Query the protocol text configuration table. Step S1180, Display the protocol. Step S1190, Confirm signing the agreement. Step S1111, Blockchain notarization. Step S1112, Record the user's signing information to the protocol signing information table.

[0109] When a user performs a business operation on a terminal device and enters a certain function or section to handle the corresponding business, a transaction ID mentioned above will be generated. Based on the transaction ID, the transaction and protocol configuration relationship table can be queried to obtain the protocol configuration information (the protocol configuration information includes at least the protocol ID).

[0110] Additionally, the agreement signing information table allows users to view previously signed agreements and their versions, while the agreement rule configuration information table indicates the validity of the agreement (e.g., whether the current latest version is compatible with historical versions). If an agreement does not meet compatibility or latest version requirements, the user is required to sign it. The agreement content information is then retrieved by querying the agreement rule configuration information table, agreement version configuration information table, and agreement text configuration table, and presented to the user for signing. After the user signs the agreement, the blockchain notarization ID of the agreement text, user information, and signing date are bound together using the blockchain. A blockchain transaction ID is generated, and the user ID, agreement ID, agreement version, signing date, and blockchain transaction ID are stored in the agreement signing information table for further storage.

[0111] In addition, after a user signs an agreement, the user can check the specific text information of the signed agreement by querying the agreement signing information table.

[0112] This application embodiment constructs a protocol management and maintenance system by pre-setting a transaction and protocol configuration relationship table, a protocol rule configuration information table, a protocol version configuration information table, a protocol text configuration table, and a protocol signing information table. This improves the security of the protocol storage mode and supports the application of multiple protocol scenarios and the iteration of protocol versions by maintaining and managing the protocol versions, making it convenient for users to query the protocols.

[0113] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0114] Figure 12 This is a schematic diagram of the structure of the data processing device provided in the embodiments of this application. The data processing device can be integrated into a computer device or server, or it can be implemented independently of the processing device but in collaboration with it. Figure 12 As shown, the data processing device 1201 includes a protocol identifier acquisition module 1202, a protocol version acquisition module 1203, a protocol information acquisition module 1204, a protocol content acquisition module 1205, an identifier generation module 1206, and an associated storage module 1207.

[0115] The protocol identifier acquisition module 1202 is used to acquire the protocol identifier associated with the user when the protocol signing conditions are triggered. The protocol version acquisition module 1203 is used to determine the current protocol version associated with the protocol identifier in the preset protocol rule configuration information table. The protocol information acquisition module 1204 is used to query the protocol body information associated with the protocol identifier and the current protocol version in the preset protocol version configuration information table based on the protocol identifier and the current protocol version. The protocol body information includes at least the protocol text identifier. The protocol content acquisition module 1205 is used to acquire the protocol content information associated with the protocol identifier and the protocol text identifier in the preset protocol text configuration table based on the protocol identifier and the protocol text identifier. The identifier generation module 1206 is used to acquire the confirmation information input by the user based on the protocol content information, and generate a blockchain transaction identifier based on the protocol content information and the confirmation information. The confirmation information includes at least the user identifier and the protocol confirmation date. The associated storage module 1207 is used to associate and store the user identifier, protocol identifier, current protocol version, protocol confirmation date, and blockchain transaction identifier in the preset protocol signing information table.

[0116] Optionally, when the protocol identifier acquisition module obtains the protocol identifier associated with the user, it can specifically be used to respond to receiving a user's transaction request, obtain the transaction identifier from the transaction request, and query the preset transaction and protocol configuration relationship table to obtain the protocol identifier corresponding to the transaction identifier.

[0117] Optionally, the data processing device may further include a condition judgment module, used to obtain the user's user identifier; determine whether there is a historical blockchain transaction identifier associated with the user identifier and the protocol identifier in the preset protocol signing information table based on the user identifier and the protocol identifier; if there is a historical blockchain transaction identifier in the preset protocol signing information table, obtain the historical protocol version, current protocol version and version compatibility identifier associated with the protocol identifier from the preset protocol rule configuration information table; and determine whether the conditions for triggering the protocol signing are met based on the historical protocol version, current protocol version and version compatibility identifier associated with the protocol identifier.

[0118] Optionally, when determining the conditions for triggering the signing of a protocol, the aforementioned protocol identifier acquisition module may specifically be used to: trigger the conditions for signing a protocol when the historical protocol version is different from the current protocol version and the version compatibility identifier indicates that the historical protocol version is incompatible with the current protocol version.

[0119] Optionally, when determining the conditions for triggering the signing of a protocol, the aforementioned protocol identifier acquisition module may specifically be used to: trigger the signing of a protocol if there is no historical blockchain transaction identifier in the preset protocol signing information table.

[0120] Optionally, the data processing device may further include a protocol rule configuration information table update module, used to: in response to a protocol version update request associated with a protocol identifier, obtain the version release date and version compatibility identifier of the protocol version to be updated from the protocol version update request; and update the version release date and version compatibility identifier of the protocol version to be updated to a preset protocol rule configuration information table.

[0121] Optionally, the data processing device may further include a protocol version configuration information table update module, used to: obtain the protocol text identifier, protocol effective date, protocol description information and protocol publishing object identification information associated with the protocol version to be updated; and update the protocol text identifier, version release date, protocol effective date, protocol description information and protocol publishing object identification information to a preset protocol version configuration information table.

[0122] Optionally, the data processing device may further include a protocol text configuration table update module, used to: obtain protocol content information associated with the protocol version to be updated; and update the protocol text identifier and protocol content information to a preset protocol text configuration table.

[0123] The apparatus provided in this application embodiment can be used to execute the methods in the above embodiments, and its implementation principle and technical effect are similar, so they will not be described again here.

[0124] It should be noted that the division of the various modules in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, these modules can be implemented entirely in software via processing element calls; they can be fully implemented in hardware; or some modules can be implemented in software via processing element calls, while others are implemented in hardware. For example, the protocol identifier acquisition module can be a separate processing element, or it can be integrated into a chip in the above device. Alternatively, it can be stored as program code in the memory of the above device, and its function can be called and executed by a processing element of the device. The implementation of other modules is similar. Moreover, these modules can be fully or partially integrated together, or they can be implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules can be completed through integrated logic circuits in the hardware of the processor element or through software instructions.

[0125] Figure 13 A schematic diagram of the structure of a computer device provided in an embodiment of this application. For example... Figure 13As shown, the computer device 1300 includes at least one processor 1301, a memory 1302, a bus 1303, and a communication interface 1304. The processor 1301, communication interface 1304, and memory 1302 communicate with each other via the bus 1303. The communication interface is used to communicate with other devices. The processor 1301 executes computer instructions stored in the memory 1302, specifically performing the relevant steps in the methods described in the above embodiments. The processor may be a central processing unit, an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention. The one or more processors included in the computer device may be processors of the same type, such as one or more CPUs; or they may be processors of different types, such as one or more CPUs and one or more ASICs. The memory stores computer instructions. The memory may include high-speed RAM and may also include non-volatile memory, such as at least one disk storage device.

[0126] This embodiment also provides a computer-readable storage medium storing computer instructions. When at least one processor of a computer device executes the computer instructions, the computer device performs the data processing methods provided in the various embodiments described above.

[0127] This embodiment also provides a computer program product including computer instructions stored in a readable storage medium. At least one processor of a computer device can read the computer instructions from the readable storage medium, and the at least one processor executes the computer instructions to cause the computer device to perform the data processing methods provided in the various embodiments described above.

[0128] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates an "or" relationship between the preceding and following related objects; in formulas, the character " / " indicates a "division" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0129] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. In the embodiments of this application, the order of the above-mentioned process numbers does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0130] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A data processing method, characterized in that, include: When the conditions for signing the agreement are triggered, obtain the agreement identifier associated with the user; The current protocol version associated with the protocol identifier is determined in the preset protocol rule configuration information table; Based on the protocol identifier and the current protocol version, the protocol body information associated with the protocol identifier and the current protocol version is obtained by querying the preset protocol version configuration information table. The protocol body information includes at least the protocol text identifier. Based on the protocol identifier and protocol text identifier, obtain the protocol content information associated with the protocol identifier and protocol text identifier from the preset protocol text configuration table; Obtain confirmation information input by the user based on the protocol content information, and generate a blockchain transaction identifier based on the protocol content information and the confirmation information. The confirmation information includes at least the user identifier and the protocol confirmation date. The user identifier, protocol identifier, current protocol version, protocol confirmation date, and blockchain transaction identifier are associated and stored in a preset protocol signing information table; The method further includes: Obtain the user's user identifier; Based on the user identifier and the agreement identifier, determine whether there is a historical blockchain transaction identifier associated with the user identifier and the agreement identifier in the preset agreement signing information table; If the historical blockchain transaction identifier exists in the preset protocol signing information table, then the historical protocol version, current protocol version, and version compatibility identifier associated with the protocol identifier are obtained from the preset protocol rule configuration information table. Based on the historical protocol version associated with the protocol identifier, the current protocol version, and the version compatibility identifier, it is determined whether the conditions for triggering the agreement signing are met; wherein, the conditions for triggering the agreement signing include: triggering the agreement signing conditions when the historical protocol version is different from the current protocol version and the version compatibility identifier indicates that the historical protocol version is incompatible with the current protocol version; The method further includes: In response to a protocol version update request associated with the protocol identifier, the release date and version compatibility identifier of the protocol version to be updated are obtained from the protocol version update request; The release date and version compatibility identifier of the protocol version to be updated are associated with and updated in the preset protocol rule configuration information table.

2. The method according to claim 1, characterized in that, The acquisition of the protocol identifier associated with the user includes: In response to receiving a user's transaction request, a transaction identifier is obtained from the transaction request; Based on the transaction identifier, the protocol identifier corresponding to the transaction identifier is obtained by querying the preset transaction and protocol configuration relationship table.

3. The method according to claim 1, characterized in that, The conditions for triggering the signing of the agreement include: If the historical blockchain transaction identifier is not present in the preset agreement signing information table, the agreement signing conditions are triggered.

4. The method according to claim 1, characterized in that, The method further includes: Obtain the protocol text identifier, protocol effective date, protocol description information, and identifier information of the protocol publishing object associated with the protocol version to be updated; Update the protocol text identifier, version release date, protocol effective date, protocol description information, and identifier information of the protocol release object to the preset protocol version configuration information table.

5. The method according to claim 1, characterized in that, The method includes: Obtain the protocol content information associated with the protocol version to be updated; Update the protocol text identifier and protocol content information to the preset protocol text configuration table.

6. A data processing apparatus, characterized in that, include: The protocol identifier acquisition module is used to acquire the protocol identifier associated with the user when the conditions for signing the agreement are triggered. The protocol version acquisition module is used to determine the current protocol version associated with the protocol identifier from the preset protocol rule configuration information table; The protocol information acquisition module is used to query the protocol body information associated with the protocol identifier and the current protocol version in a preset protocol version configuration information table based on the protocol identifier and the current protocol version. The protocol body information includes at least the protocol text identifier. The protocol content acquisition module is used to obtain protocol content information associated with the protocol identifier and the protocol text identifier from a preset protocol text configuration table based on the protocol identifier and the protocol text identifier. The identifier generation module is used to obtain the confirmation information input by the user according to the protocol content information, and generate a blockchain transaction identifier according to the protocol content information and the confirmation information. The confirmation information includes at least the user identifier and the protocol confirmation date. The associated storage module is used to associate and store the user identifier, protocol identifier, current protocol version, protocol confirmation date, and blockchain transaction identifier into a preset protocol signing information table. The condition judgment module is used to obtain the user's user identifier; Based on the user identifier and the agreement identifier, determine whether there is a historical blockchain transaction identifier associated with the user identifier and the agreement identifier in the preset agreement signing information table; If the historical blockchain transaction identifier exists in the preset protocol signing information table, then the historical protocol version, current protocol version, and version compatibility identifier associated with the protocol identifier are obtained from the preset protocol rule configuration information table. Based on the historical protocol version associated with the protocol identifier, the current protocol version, and the version compatibility identifier, determine whether the conditions for triggering the agreement signing are met; When determining the conditions for triggering the signing of a protocol, the protocol identifier acquisition module is specifically used to trigger the conditions for signing a protocol when the historical protocol version is different from the current protocol version and the version compatibility identifier indicates that the historical protocol version is incompatible with the current protocol version. The protocol rule configuration information table update module is used to respond to the protocol version update request associated with the protocol identifier and obtain the version release date and version compatibility identifier of the protocol version to be updated from the protocol version update request; The release date and version compatibility identifier of the protocol version to be updated are associated with and updated in the preset protocol rule configuration information table.

7. A computer device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed by a processor, are used to implement the method as described in any one of claims 1-5.

9. A computer program product comprising computer instructions, characterized in that, When executed by a processor, the computer instructions implement the method described in any one of claims 1-5.

Images