CN115757336A - Data processing method, apparatus, device, medium, and program product - Google Patents

Abstract

The present application provides a data processing method, device, device, medium and program product, which relate to the technical field of financial technology. The method includes: obtaining the protocol identification associated with the user, and determining the current protocol version in the preset protocol rule configuration information table , according to the protocol identifier and the current protocol version, query the protocol text identifier in the preset protocol version configuration information table, obtain the protocol content information in the preset protocol text configuration table according to the protocol identifier and protocol text identifier, and obtain the The confirmation information of the information input, and according to the agreement content information and confirmation information, generate a block chain transaction identification, the confirmation information includes at least the user identification and the agreement confirmation date, and the user identification, agreement identification, current agreement version, agreement confirmation date and block The chain transaction identifier is associated and stored in the default agreement signing information table. This technical solution can prevent users from signing low-version agreements and improve the accuracy of agreement signing.

Description

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

technical field

The present application relates to the technical field of financial technology, and in particular to a data processing method, device, equipment, medium and program product.

Background technique

At present, users usually sign an agreement document before conducting business through online channels, which is used to show the terms and conditions of some aspects. By signing an agreement with the user, it means that the user knows the content of the agreement and reaches an agreement between the user and the service provider. .

In the prior art, when signing an agreement, the content of the agreement, the confirmed information submitted by the user during the signing of the agreement, the date of signing, etc. are usually recorded. After the recording is completed, these agreement-related information will be saved.

However, in this way of the existing technology, due to the fast iterative update of the protocol version, after the release of the new version of the protocol, due to the lack of identification of the old and new versions of the protocol, users may sign an agreement with a lower version in the process of signing the agreement , resulting in an agreement signing error.

Contents of the invention

This application provides a data processing method, device, equipment, medium and program product, which are used to solve the problem that the iterative update speed of the existing agreement version is fast, and the user is easy to sign the agreement of the lower version, resulting in the wrong signing of the agreement.

In the first aspect, the embodiment of the present application provides a data processing method, including:

When the conditions for signing an agreement are triggered, obtain the agreement identifier associated with the user;

Determine the current protocol version associated with the protocol identifier in the preset protocol rule configuration information table;

According to the protocol identifier and the current protocol version, query the preset protocol version configuration information table to obtain the protocol subject information associated with the protocol identifier and the current protocol version, and the protocol subject information includes at least the protocol text identifier;

Obtain the protocol content information associated with the protocol identifier and the protocol text identifier in the preset protocol text configuration table according to the protocol identifier and the protocol text identifier;

Obtain the confirmation information input by the user according to the agreement content information, and generate a blockchain transaction identifier according to the agreement content information and the confirmation information, and the confirmation information includes at least the user identification and the agreement confirmation date;

The user identification, agreement identification, current agreement version, agreement confirmation date and blockchain transaction identification are associated and stored in the preset agreement signing information table.

In a possible design of the first aspect, the acquiring the protocol identifier associated with the user includes:

In response to receiving a transaction request from a user, obtain a transaction identifier from the transaction request;

According to the transaction identifier, the protocol identifier corresponding to the transaction identifier is obtained by querying the preset transaction and protocol configuration relationship table.

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

Obtain the user ID of the user;

According to the user identification and the agreement identification, determine whether there is a historical blockchain transaction identification associated with the user identification and the agreement identification in the preset agreement signing information table;

If the historical block chain transaction identifier exists in the preset agreement signing information table, the historical agreement version, current agreement version and version associated with the agreement identifier are obtained in the preset agreement rule configuration information table Compatibility logo;

According to the historical protocol version associated with the protocol identifier, the current protocol version and the version compatibility identifier, determine whether the triggering condition for signing the agreement is met.

In yet another possible design of the first aspect, the triggering conditions for signing an agreement include:

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 condition is triggered.

In yet another possible design of the first aspect, the triggering conditions for signing an agreement include:

If the historical blockchain transaction identifier does not exist in the preset agreement signing information table, the agreement signing condition is triggered.

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

In response to the protocol version update request associated with the protocol identifier, 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 of the protocol version to be updated and the version compatibility identifier are associated and updated to the preset protocol rule configuration information table.

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

Obtain the agreement text identification, agreement effective date, agreement description information and identification information of the agreement release object associated with the agreement version to be updated;

Updating the protocol text identifier, version release date, protocol effective date, protocol description information, and protocol release object identification information to the preset protocol version configuration information table.

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

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

Updating the protocol text identifier and protocol content information to the preset protocol text configuration table.

In a second aspect, an embodiment of the present application provides a data processing device, including:

The agreement identification acquisition module is used to obtain the agreement identification associated with the user when the agreement signing condition is triggered;

A protocol version acquisition module, configured to determine the current protocol version associated with the protocol identifier in the preset protocol rule configuration information table;

The protocol information acquisition module is used to query the preset protocol version configuration information table to obtain the protocol subject information associated with the protocol identifier and the current protocol version according to the protocol identifier and the current protocol version, and the protocol subject information includes at least There is an agreement text mark;

A protocol content acquisition module, configured to acquire protocol content information associated with the protocol identifier and the protocol text identifier in the preset protocol text configuration table according to the protocol identifier and the protocol text identifier;

An identification generation module, configured to obtain confirmation information input by the user according to the agreement content information, and generate a block chain transaction identification according to the agreement content information and the confirmation information, and the confirmation information includes at least the user identification and the agreement confirmation date;

An associative storage module, configured to associate and store the user identification, agreement identification, current agreement version, agreement confirmation date, and blockchain transaction identification in a preset agreement signing information table.

In a third aspect, the embodiment of the present application provides a computer device, including: a processor, and a memory connected in communication with the processor; the memory stores computer-executable instructions; and the processor executes the computer-executable instructions stored in the memory. instructions to implement the method as described above.

In a fourth aspect, the embodiments of the present application provide a computer-readable storage medium, where computer instructions are stored in the computer-readable storage medium, and the computer instructions are used to implement the above method when executed by a processor.

In a fifth aspect, the embodiments of the present application provide a computer program product, including computer instructions, and when the computer instructions are executed by a processor, the foregoing method is implemented.

The data processing method, device, equipment, medium, and program product provided by the embodiments of the present application can discover the current latest version of the protocol in time and output it to Users sign, improve the accuracy of agreement signing.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments consistent with the application and together with the description serve to explain the principles of the application;

FIG. 1 is a schematic diagram of a scenario of a data processing method provided in an embodiment of the present application;

FIG. 2 is a schematic flow diagram of a data processing method provided in an embodiment of the present application;

FIG. 3 is a schematic diagram of the agreement signing information form provided by the embodiment of the present application;

FIG. 4 is a schematic diagram of a preset protocol rule configuration information table provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of a preset protocol version configuration information table provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of a preset protocol text configuration table provided by an embodiment of the present application;

FIG. 7 is a schematic diagram of the preset agreement signing information table provided by the embodiment of the present application;

FIG. 8 is a schematic diagram of a preset transaction and protocol configuration relationship table provided by the embodiment of the present application;

FIG. 9 is a schematic diagram of an updated preset protocol rule configuration information table;

FIG. 10 is a schematic diagram of an updated preset protocol version configuration information table provided by the embodiment of the present application;

Figure 11 is a schematic diagram of the agreement signing process provided by the embodiment of the present application;

FIG. 12 is a schematic structural diagram of a data processing device provided in an embodiment of the present application;

FIG. 13 is a schematic structural diagram of a computer device provided by an embodiment of the present application.

By means of the above drawings, specific embodiments of the present application have been shown, which will be described in more detail hereinafter. These drawings and text descriptions are not intended to limit the scope of the concept of the application in any way, but to illustrate the concept of the application for those skilled in the art by referring to specific embodiments.

Detailed ways

In order to make the purposes, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments It is a part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of this application.

It should be noted that the data processing method, device, equipment, medium and program product disclosed in the present disclosure can be used in the financial field. It can also be used in any field other than the financial field. The application field of the data processing method, device, equipment, medium and program product is not limited.

Fig. 1 is a schematic diagram of the scene of the data processing method provided by the embodiment of the present application, as shown in Fig. The device 11 performs business processing on the online channel. Before the business is handled, the terminal device 11 usually displays various agreements related to the business. After the user reads these agreements and confirms signing, it means that the user knows the content of the agreement, so that the server 12 can continue to provide business services for the user. However, because the agreement is usually updated and iterated quickly, and the agreement signing process usually only pays attention to the agreement content, the agreement signing date and the signing confirmation information submitted by the user, so that the user does not know whether the agreement he signed is the latest version, such as a certain agreement Including the latest version 1.1 and the old version 1.0, different versions may be compatible or incompatible. For the case of version incompatibility, if the user signs the agreement of version 1.0, it will be equivalent to signing the wrong agreement. Subsequent users are required to re-sign a new version, which leads to low efficiency and low accuracy of agreement signing.

In view of the above problems, the data processing method, device, equipment, media and program products provided by the embodiments of the present application, in order to solve the problem that the protocol update iteration speed is fast and easily cause the user to sign the wrong version of the protocol, it is necessary to check the version of the protocol, To enable users to sign the latest version of the current agreement. Specifically, by establishing a protocol rule configuration information table and managing the protocol version in the protocol rule configuration information table in real time, the current latest version of the protocol can be found in time and output to the user for signing, improving the accuracy of signing the agreement.

Below, the technical solution of the present application will be described in detail through specific embodiments. It should be noted that the following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments.

Fig. 2 is a schematic flow chart of the data processing method provided by the embodiment of the present application. This method can be applied to processing devices such as computer equipment or servers. Taking the server as the execution subject as an example, as shown in Fig. 2, the method can specifically include the following Step: step S201, when the condition for signing an agreement is triggered, the agreement identifier associated with the user is acquired.

In this embodiment, take a user who needs to handle transaction business as an example. Generally, when different users handle different transaction services, they have corresponding user IDs and transaction IDs. Different users are identified by user IDs, and different users are identified by transaction IDs. different transactions.

The basis for the triggering of the agreement signing conditions is the relevant information of the user, such as whether the user has signed an agreement before handling the transaction business. If the agreement has not been signed before, the agreement signing condition will be triggered. Another example is that the user has signed a lower version of the agreement when handling the transaction business. At this time, the conditions for signing the agreement will also be triggered, requiring the user to sign a new version of the agreement again.

In this embodiment, the protocol identifier may refer to a protocol ID. The protocol IDs of different protocols are different, and the protocol IDs of different versions of the protocols are the same. Exemplarily, FIG. 3 is a schematic diagram of the agreement signing information table provided by the embodiment of the present application. The server can pre-build the agreement signing information table and store it in the database. When a user initiates a service request, it can query the information based on the user ID of the user. Obtain the protocol ID (that is, the protocol identifier) associated with the user. Wherein, the agreement signing information table may also store related transaction description information, and briefly describe the transaction.

Step S202, determine the current protocol version associated with the protocol identifier in the preset protocol rule configuration information table.

In this embodiment, the association relationship between the protocol identifier and the protocol version is established in the preset protocol rule configuration information table. By using the protocol identifier, the current protocol version (that is, the latest protocol version) can be found in the preset protocol rule configuration information table. Version). Figure 4 is a schematic diagram of the preset protocol rule configuration information table provided by the embodiment of the present application. As shown in Figure 4, different protocol IDs (i.e., protocol identifiers) are associated with corresponding current latest versions, old versions, version compatible identifiers and versions start date. The same protocol ID may have a current latest version and an old version, or may only have a current latest version.

Step S203, according to the protocol identifier and the current protocol version, query the protocol subject information associated with the protocol identifier and the current protocol version in the preset protocol version configuration information table. Wherein, the agreement body information includes at least an agreement text identifier.

In this embodiment, the same protocol ID may have different versions. For example, take the protocol ID "00002" in FIG. 4 as an example, which includes the latest version 1.2 and the old version 1.1. Among them, for the same protocol identifier, the protocol subject information associated with different versions is different.

Exemplarily, FIG. 5 is a schematic diagram of the preset protocol version configuration information table provided by the embodiment of the present application. As shown in FIG. 5, the preset protocol version configuration information table includes the protocol ID "00001" and the protocol ID "00002 ", where the protocol ID "00001" has two protocol versions (i.e. version 1.0 and version 1.1), and different versions correspond to different protocol body information (including protocol text ID (protocol text identification), protocol brief description, protocol release date, the effective date of the agreement, and the agreement issuer ID (that is, the identification information of the agreement issue object)).

Step S204, according to the protocol identifier and the protocol text identifier, obtain the protocol content information associated with the protocol identifier and the protocol text identifier in the preset protocol text configuration table.

In this embodiment, a protocol ID, a protocol text ID, and protocol content information are stored in the preset protocol text configuration table, wherein the protocol content information may be in the form of a hash value, that is, a protocol text hash. Exemplarily, FIG. 6 is a schematic diagram of the preset protocol text configuration table provided by the embodiment of the present application. As shown in FIG. 6, each protocol ID and protocol text ID has a corresponding protocol text hash and blockchain deposit certificate ID (protocol text hash and blockchain storage ID include 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.

Step S205, obtaining confirmation information input by the user according to the agreement content information, and generating a blockchain transaction identifier according to the agreement content information and confirmation information. Wherein, the confirmation information includes at least a user identification and an agreement confirmation date.

In this embodiment, the block chain transaction identification can refer to the block chain transaction ID, the confirmation information can be the user information (such as user signature, user fingerprint, etc.) input by the user, and the block chain transaction identification refers to the block chain ID , to bind the confirmation information, the blockchain storage certificate ID and the signing date of the agreement to form a blockchain transaction ID.

Among them, the agreement content information can be displayed on the display interface of the terminal device 11 in FIG. 1 for the user to review. After reading, the user can input personal signature, personal fingerprint and other information as part of the confirmation information, on behalf of the user to confirm that the contract has been signed. protocol.

Step S206, associate and store the user ID, agreement ID, current agreement version, agreement confirmation date, and blockchain transaction ID into the preset agreement signing information table.

Exemplarily, FIG. 7 is a schematic diagram of the preset agreement signing information table provided by the embodiment of the present application. As shown in FIG. 7, each user ID is associated with an agreement ID, agreement version, agreement confirmation date and blockchain transaction ID.

In this embodiment of the present application, by establishing a protocol rule configuration information table and managing the protocol version in the protocol rule configuration information table in real time, the current latest version of the agreement can be found in time and output to the user for signing, thereby improving the accuracy of the agreement signing, and at the same time, after signing the agreement Afterwards, the relevant information of the agreement after signing will be stored in the default agreement signing information table for recording, so that users can view their agreement signing records in real time and effectively maintain and manage the signed agreements.

In some embodiments, in the above step S201, "obtaining the protocol identification associated with the user" can be specifically implemented through the following steps: in response to receiving the transaction request from the user, obtaining the transaction identification from the transaction request; according to the transaction identification, in The protocol identifier corresponding to the transaction identifier is obtained by querying the preset transaction and protocol configuration relationship table.

In this embodiment, when a user initiates a transaction request, the transaction request carries the user ID and the transaction ID (that is, the transaction identifier), and the preset transaction and protocol configuration relationship table includes each transaction ID and the transaction ID associated with the transaction ID. Protocol ID (that is, protocol identifier).

Exemplarily, FIG. 8 is a schematic diagram of the preset transaction and protocol configuration relationship table provided by the embodiment of the present application. As shown in FIG. 8, the protocol ID associated with the transaction ID "T00001" is "000001", and the transaction ID "00002" is associated with The protocol ID is "000002". Wherein, for example, the preset transaction and protocol configuration relationship table also includes transaction description information.

In this embodiment of the present application, by setting the preset transaction and protocol configuration relationship table, the relationship between the transaction ID and the protocol ID is maintained through the preset transaction and protocol configuration relationship table. When the user initiates a transaction request, it can be found based on the transaction ID. The associated protocol ID, based on the protocol ID, can easily and quickly find out which protocols need to be used in this exchange, which improves the efficiency and accuracy of the transaction and facilitates staff maintenance and management.

In some embodiments, the above method further includes the following steps: acquiring the user ID of the user;

According to the user ID and the agreement ID, determine whether there is a historical blockchain transaction ID associated with the user ID and the agreement ID in the default agreement signing information table; if there is a historical blockchain transaction ID in the preset agreement signing information table, Then obtain the historical protocol version, current protocol version, and version compatibility identifier associated with the protocol identifier in the preset protocol rule configuration information table; determine whether the trigger is satisfied according to the historical protocol version, current protocol version, and version compatibility identifier associated with the protocol identifier Agreement signing conditions.

In this embodiment, the preset agreement signing information table stores the agreements signed by users, which are associated by user IDs (ie, user identifiers). Exemplarily, you can continue to refer to Figure 7 above. When a user with a user ID of "C0000011" initiates a transaction request, you can find out that the preset agreement signing information table includes the agreement signed by the user based on the user ID of the user (that is, the agreement protocol with ID "000001"), the blockchain transaction ID of this protocol is "c031d365d1fa", and the protocol version is 1.1. Based on the protocol ID "000001", it can be found in the preset rule information configuration table that the current latest version of the protocol is 1.1, the historical version is "1.1", and the version compatibility flag is "No". Based on the information associated with the agreement ID in the preset rule information configuration table, it can be determined that the agreement signed by the user is the latest version of the agreement, and there is no need to trigger the agreement signing condition.

In the embodiment of the present application, by checking the preset agreement signing information table, the user can check whether the agreement has been signed. When the user has signed the agreement, it can also determine whether there is an update to the agreement version of the agreement based on the signed agreement identifier. If there is an update It is necessary to start the agreement signing conditions and re-sign the latest version of the agreement to ensure the accuracy of the agreement signed by the user.

Further, on the basis of the above-mentioned embodiments, in some other embodiments, when determining whether to trigger the agreement signing condition, it can be specifically implemented through the following steps: when the historical protocol version is different from the current protocol version and the version compatibility flag represents the history When the agreement version is incompatible with the current agreement version, the agreement signing condition is triggered.

In this embodiment, continue to refer to Figure 4 above. Figure 4 provides two protocol IDs, namely the protocol ID "000001" and the protocol ID "000002", wherein the current latest version of the protocol ID "000001" is 1.1, and the protocol The compatibility flag is "No", and the historical agreement version is 1.1. At this time, the agreement version has not changed, and the agreement signing conditions will not be triggered. For the protocol ID "000002", the current latest version is 1.2, the protocol compatibility flag is "Yes", and the historical protocol version is 1.1. At this time, the historical protocol version is compatible with the latest protocol version, so the agreement will not be signed condition.

Exemplarily, for the agreement ID "000002", if the agreement compatibility flag is "No", and the current latest version is 1.2, and the historical agreement version is 1.1, the agreement signing condition will be triggered.

In this embodiment of the application, by searching the historical protocol version, current protocol version, and version compatibility flag recorded in the preset protocol rule configuration information table, it can quickly determine whether the user needs to re-sign the agreement, and it is also convenient to maintain and manage the agreements of each version , to ensure that when a new version of the agreement is released, users can sign the latest version of the agreement, further improving the accuracy of agreement signing.

In some other embodiments, the "triggering the agreement signing condition" in the above step S201 can be specifically implemented through the following steps: if there is no historical blockchain transaction identifier in the preset agreement signing information table, trigger the agreement signing condition.

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 at present, and if the user initiates a transaction request at this time, he needs to sign an agreement related to the transaction.

Wherein, when the 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, and then the agreement ID can be found from the preset agreement rule configuration information table based on the agreement ID. The current latest version of the agreement is output to the user, so that the user can sign the current latest version of the agreement.

In this embodiment of the application, by maintaining the preset agreement signing information table, it is determined 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 condition can be triggered to obtain the latest version The agreement is signed by the user, which facilitates the management and maintenance of the user agreement signing, and improves the efficiency of the user signing the agreement.

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

In this embodiment, when a new version of the protocol is released, it is necessary to maintain and update the relevant information of the released new version to the preset protocol rule configuration information table. For example, referring to FIG. 4 above, when a new version of the protocol is released, the protocol version and version compatibility identifier of the new version of the protocol can be maintained in the preset protocol rule configuration information table.

Exemplarily, FIG. 9 is a schematic diagram of the updated preset protocol rule configuration information table. Taking the protocol ID “000001” and a new version 1.3 that needs to be released as an example, as shown in FIG. 9, the protocol ID is “000001” at this time The current latest version is 1.3, the historical version is 1.2, and the version compatibility flag is "No".

In this embodiment of the application, by maintaining and updating the preset protocol rule configuration information table, it can ensure that after the release of the new version of the protocol, the current latest protocol version can be queried for users to sign, and it is also convenient for protocol maintainers to view changes in the protocol version. Prevent users from signing incompatible low-version agreements, and further improve the accuracy of agreement signing.

Further, on the basis of the above-mentioned embodiments, in some embodiments, the above-mentioned method further includes: obtaining the protocol text identification, the protocol effective date, the protocol description information and the identification information of the protocol release object associated with the protocol version to be updated; The protocol text identifier, version release date, protocol effective date, protocol description information, and protocol release object identification information are updated to the preset protocol version configuration information table.

In this embodiment, continue to refer to Figure 5 above, 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 (that is, the ID of the protocol publisher). Exemplarily, FIG. 10 is a schematic diagram of the updated preset protocol version configuration information table provided by the embodiment of the present application. As shown in FIG. 10, the protocol version of the protocol ID "000001" will be updated to 1.3, and the protocol text ID is "10000003 ", the agreement release date is 2022/1/1, the agreement effective date is 2022/1/1, and the agreement issuer ID is 33333.

In this embodiment of the application, by maintaining and updating the preset protocol version configuration information table, it can ensure that after the release of the new version of the protocol, the current latest protocol version can be queried based on the protocol ID for users to sign, and it is also convenient for protocol maintainers to view the protocol Version changes prevent users from signing incompatible low-version agreements, and further improve the accuracy of agreement signing.

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

In this embodiment, continue to refer to Figure 6 above, taking the protocol ID "10000001" as an example, when the protocol associated with the protocol ID "10000001" releases a new version, the protocol content information associated with the protocol ID "10000001" also It will be updated to the default protocol text configuration table.

In this embodiment of the application, by maintaining and updating the preset protocol text configuration table, it can ensure that after the release of the new version of the protocol, the current latest protocol version can be queried based on the protocol ID for users to sign, and it is also convenient for protocol maintainers to view the protocol version Changes to prevent users from signing incompatible low-version agreements, and further improve the accuracy of agreement signing.

Exemplarily, FIG. 11 is a schematic diagram of the agreement signing process provided by the embodiment of the present application. As shown in FIG. 11 , it includes the following steps: S1110, the user enters the function. Step S1120, acquiring a protocol ID. Step S1130, determine whether the user needs to sign an agreement. Step S1131, query whether the user has ever signed an agreement. Step S1132, if the user has signed an agreement, then determine whether the agreement is valid. Step S1133, if the protocol version is compatible, then no agreement needs to be signed. Step S1140, acquiring 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, displaying the protocol. In step S1190, it is determined to sign an agreement. Step S1111, blockchain storage certificate. Step S1112, recording the signing information of the user in the agreement signing information table.

Among them, when the user performs business operations on the terminal device and enters a certain function or column to handle the corresponding business, the corresponding transaction ID mentioned above will be generated, and the transaction and protocol configuration relationship table can be queried according to the transaction ID , to obtain protocol configuration information (the protocol configuration information includes at least a protocol ID).

In addition, through the agreement signing information table, the agreement and agreement version signed by the user can be queried, and whether the agreement is valid (for example, whether the latest version is compatible with the previous version) can be queried through the agreement rule configuration information table. If the agreement does not meet the compatibility requirements and the latest version requirements, it is determined that the user needs to sign the agreement, and the agreement content information is obtained by querying the protocol rule configuration information table, querying the protocol version configuration information table, and querying the protocol text configuration table, and showing it to the user for signing. After the user signs the agreement, the blockchain storage certificate ID, user information, and signing date of the agreement text are bundled through the blockchain, and the blockchain transaction ID is generated through the blockchain, and the user ID, agreement ID, agreement version, The signing date and blockchain transaction ID are stored in the agreement signing information table for storage.

At the same time, after the user has signed the agreement, the user can query the specific text information of the signed agreement by querying the agreement signing information form.

The embodiment of this application builds a protocol management and maintenance system by presetting the transaction and protocol configuration relationship table, protocol rule configuration information table, protocol version configuration information table, protocol text configuration table, and agreement signing information table, and improves the secure protocol storage mode. , and through the maintenance and management of the protocol version, it supports the application of multi-protocol scenarios and the version update iteration of the protocol, which is convenient for users to query the protocol.

The following are device embodiments of the present application, which can be used to implement the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

Fig. 12 is a schematic structural diagram of a data processing device provided by an embodiment of the present application. The data processing device may be integrated in a processing device such as a computer device or a server, or may be independent of the processing device and cooperate with the processing device to implement the solution. As shown in FIG. 12 , the data processing device 1201 includes a protocol identification acquisition module 1202 , a protocol version acquisition module 1203 , a protocol information acquisition module 1204 , a protocol content acquisition module 1205 , an identification generation module 1206 and an associated storage module 1207 .

Wherein, the agreement identification obtaining module 1202 is used to obtain the agreement identification associated with the user when the agreement signing condition is 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 configured to query the preset protocol version configuration information table to obtain the protocol subject information associated with the protocol identifier and the current protocol version according to the protocol identifier and the current protocol version. Wherein, the agreement body information includes at least an agreement text identifier. The protocol content acquiring module 1205 is configured to acquire protocol content information associated with the protocol identifier and the protocol text identifier in the preset protocol text configuration table according to the protocol identifier and the protocol text identifier. The identification generation module 1206 is used to obtain the confirmation information input by the user according to the agreement content information, and generate a block chain transaction identification according to the agreement content information and confirmation information. Wherein, the confirmation information includes at least a user identification and an agreement confirmation date. The associated storage module 1207 is used for associating and storing the user identification, agreement identification, current agreement version, agreement confirmation date and blockchain transaction identification in the preset agreement signing information table.

Optionally, when the protocol identification acquisition module acquires the protocol identification associated with the user, it can specifically be used to obtain the transaction identification from the transaction request in response to receiving the user's transaction request; according to the transaction identification, in the preset transaction and protocol configuration The protocol identifier corresponding to the transaction identifier is obtained by querying the relational table.

Optionally, the above-mentioned data processing device may also include a condition judging module, which is used to acquire the user ID of the user; and determine whether there is a history associated with the user ID and the agreement ID in the preset agreement signing information table according to the user ID and the agreement ID. Blockchain transaction identifier; if there is a historical blockchain transaction identifier in the default agreement signing information table, then obtain the historical protocol version, current protocol version, and version compatibility identifier associated with the protocol identifier in the preset agreement rule configuration information table ; According to the historical protocol version associated with the protocol identifier, the current protocol version and the version compatible identifier, determine whether the triggering agreement signing condition is satisfied.

Optionally, when the above-mentioned protocol identification acquisition module determines the conditions for triggering agreement signing, it can be specifically used to: trigger the agreement Sign the conditions.

Optionally, when the above-mentioned agreement identification acquisition module determines the conditions for triggering agreement signing, it can be specifically used to: trigger the agreement signing conditions if there is no historical blockchain transaction identification in the preset agreement signing information table.

Optionally, the above-mentioned data processing device may also include a protocol rule configuration information table update module, configured to: respond to the protocol version update request associated with the protocol identifier, obtain the version release date and the version release date of the protocol version to be updated from the protocol version update request. Version compatibility identifier; update the version release date of the protocol version to be updated and the version compatibility identifier associated to the default protocol rule configuration information table.

Optionally, the above-mentioned data processing device may also include a protocol version configuration information table update module, which is used to: obtain the protocol text identifier associated with the protocol version to be updated, the protocol effective date, the protocol description information, and the identification information of the protocol release object; The protocol text identifier, version release date, protocol effective date, protocol description information, and protocol release object identification information are updated to the preset protocol version configuration information table.

Optionally, the above-mentioned data processing device may also include a protocol text configuration table update module, configured to: acquire 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.

The device provided in the embodiment of the present application can be used to execute the method in the above embodiment, and its implementation principle and technical effect are similar, and will not be repeated here.

It should be noted that it should be understood that the division of each module of the above device is only a division of logical functions, and may be fully or partially integrated into one physical entity or physically separated during actual implementation. And these modules can all be implemented in the form of calling software through processing elements; they can also be implemented in the form of hardware; some modules can also be implemented in the form of calling software through processing elements, and some modules can be implemented in the form of hardware. For example, the protocol identification acquisition module can be a separate processing element, and can also be integrated in a chip of the above-mentioned device. In addition, it can also be stored in the memory of the above-mentioned device in the form of program code. The processing element invokes and executes the function of the above protocol identification acquisition module. The implementation of other modules is similar. In addition, all or part of these modules can be integrated together, and can also be implemented independently. The processing element here may be an integrated circuit, which has a signal processing capability. In the implementation process, each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or an instruction in the form of software.

FIG. 13 is a schematic structural diagram of a computer device provided by an embodiment of the present application. As shown in FIG. 13 , the computer device 1300 includes: at least one processor 1301 , a memory 1302 , a bus 1303 and a communication interface 1304 . Wherein: the processor 1301 , the communication interface 1304 and the memory 1302 communicate with each other through the bus 1303 . Communication interface for communicating with other devices. The processor 1301 is configured to execute the computer-executed instructions stored in the memory 1302, and may specifically execute relevant steps in the methods described in the foregoing embodiments. The processor may be a central processing unit, or an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention. The one or more processors included in the computer device may be of the same type, such as one or more CPUs, or may be different types of processors, such as one or more CPUs and one or more ASICs. Memory, used to store computer-executable instructions. The memory may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk memory.

This embodiment also provides a computer-readable storage medium. Computer instructions are stored in the readable storage medium. When at least one processor of the computer device executes the computer instructions, the computer device performs the data processing provided by the above-mentioned various embodiments. method.

This embodiment also provides a computer program product, where the program product includes computer instructions, and the computer instructions are stored in a readable storage medium. At least one processor of the computer device may read the computer instructions from the readable storage medium, and the at least one processor executes the computer instructions so that the computer device implements the data processing methods provided in the above-mentioned various implementations.

In this application, "at least one" means one or more, and "multiple" means two or more. "And/or" describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural. The character "/" generally indicates that the contextual objects are an "or" relationship; in the formula, the character "/" indicates that the contextual objects are 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 item (piece) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein, a, b, c can be single or multiple indivual.

It can be understood that the various numbers involved in the embodiments of the present application are only for convenience of description, and are not used to limit the scope of the embodiments of the present application. In the embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not constitute a component of the implementation process of the embodiments of the present application. Any restrictions.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and are not intended to limit it; although the application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: It is still possible to modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical solutions of the various embodiments of the present application. scope.

Claims (12)

1. A data processing method, comprising:

acquiring a protocol identifier associated with a user when a protocol signing condition is triggered;

determining the current protocol version associated with the protocol identifier in a preset protocol rule configuration information table;

according to the protocol identification and the current protocol version, inquiring in a preset protocol version configuration information table to obtain protocol body information associated with the protocol identification and the current protocol version, wherein the protocol body information at least comprises a protocol text identification;

acquiring protocol content information associated with the protocol identifier and the protocol text identifier in a preset protocol text configuration table according to the protocol identifier and the protocol text identifier;

acquiring confirmation information input by a user according to the protocol content information, and generating a block chain transaction identifier according to the protocol content information and the confirmation information, wherein the confirmation information at least comprises a user identifier and a protocol confirmation date;

and storing the user identification, the protocol identification, the current protocol version, the protocol confirmation date and the blockchain transaction identification into a preset protocol signing information table in an associated manner.

2. The method of claim 1, wherein obtaining the protocol identifier associated with the user comprises:

in response to receiving a transaction request of a user, acquiring a transaction identifier from the transaction request;

and inquiring in a preset transaction and protocol configuration relation table according to the transaction identifier to obtain a protocol identifier corresponding to the transaction identifier.

3. The method of claim 1, further comprising:

acquiring a user identifier of the user;

determining whether a historical blockchain transaction identifier associated with the user identifier and the protocol identifier exists in the preset protocol signing information table or not according to the user identifier and the protocol identifier;

if the historical blockchain transaction identification exists in the preset protocol signing information table, acquiring a historical protocol version, a current protocol version and a version compatible identification which are associated with the protocol identification in the preset protocol rule configuration information table;

and determining whether the protocol signing triggering condition is met or not according to the historical protocol version, the current protocol version and the version compatible identification associated with the protocol identification.

4. The method of claim 3, wherein the triggering an agreement subscription condition comprises:

and when the historical protocol version is different from the current protocol version and the version compatible identifier represents that the historical protocol version is not compatible with the current protocol version, triggering the protocol signing condition.

5. The method of claim 3, wherein the triggering an agreement subscription condition comprises:

and if the historical block chain transaction identification does not exist in the preset protocol signing information table, triggering the protocol signing condition.

6. The method according to any one of claims 1-5, further comprising:

responding to a protocol version updating request associated with the protocol identifier, and acquiring a version release date and a version compatible identifier of a protocol version to be updated from the protocol version updating request;

and updating the version release date and the version compatible identification of the protocol version to be updated to the preset protocol rule configuration information table in an associated manner.

7. The method of claim 6, further comprising:

acquiring a protocol text identifier, a protocol effective date, protocol description information and protocol release object identifier information which are associated with the protocol version to be updated;

and updating the protocol text identifier, the version release date, the protocol effective date, the protocol description information and the identifier information of the protocol release object to the preset protocol version configuration information table.

8. The method of claim 6, wherein the method comprises:

acquiring protocol content information associated with the protocol version to be updated;

and updating the protocol text identification and the protocol content information to the preset protocol text configuration table.

9. A data processing apparatus, characterized by comprising:

the protocol identification acquisition module is used for acquiring a protocol identification associated with a user when a protocol signing condition is triggered;

the protocol version acquisition module is used for determining the current protocol version associated with the protocol identifier in a preset protocol rule configuration information table;

a protocol information obtaining module, configured to query a preset protocol version configuration information table according to the protocol identifier and the current protocol version to obtain protocol body information associated with the protocol identifier and the current protocol version, where the protocol body information at least includes a protocol text identifier;

the protocol content acquisition module is used for acquiring protocol content information associated with the protocol identifier and the protocol text identifier in a preset protocol text configuration table according to the protocol identifier and the protocol text identifier;

the identification generation module is used for acquiring confirmation information input by a user according to the protocol content information and generating a block chain transaction identification according to the protocol content information and the confirmation information, wherein the confirmation information at least comprises a user identification and a protocol confirmation date;

and the association storage module is used for storing the user identifier, the protocol identifier, the current protocol version, the protocol confirmation date and the blockchain transaction identifier into a preset protocol signing information table in an associated manner.

10. A computer device, comprising: a processor, and a memory communicatively coupled to the processor;

the memory stores computer-executable instructions;

the processor executes computer-executable instructions stored by the memory to implement the method of any of claims 1-8.

11. A computer-readable storage medium having computer instructions stored therein, which when executed by a processor, are configured to implement the method of any one of claims 1-8.

12. A computer program product comprising computer instructions, characterized in that the computer instructions, when executed by a processor, implement the method of any one of claims 1-8.

Images