Method and apparatus for collaborative maintenance of transaction messages by multiple users

Abstract

This invention discloses a method and apparatus for collaborative maintenance of transaction messages by multiple users, applicable to the field of message processing technology. The method includes: upon receiving a message maintenance request for a transaction message, generating a message record and storing it in a database; generating a first encrypted string corresponding to the message record and adding it to the message record; creating a new thread corresponding to the message record; upon receiving a field maintenance request for a field, executing the following steps in the thread corresponding to the message record: generating a second encrypted string corresponding to the transaction message; verifying the second encrypted string against the first encrypted string; if the verification passes, comparing the field information in the field maintenance request with the field information of the corresponding field in the database; if the comparison is inconsistent, updating the field information of the field and broadcasting it so that other user terminals update the corresponding field information upon receiving the broadcast message. This invention can improve the efficiency of message maintenance and enhance the security of sensitive customer information.

Description

Technical Field

[0001] This invention relates to the field of message processing technology, and in particular to a method and apparatus for collaborative maintenance of transaction messages by multiple users. Background Technology

[0002] This section is intended to provide background or context for the embodiments of the invention set forth in the claims. The description herein is not an admission that it is prior art simply because it is included in this section.

[0003] The current entry point for maintaining transaction messages is mainly through manual input by banking staff on a webpage.

[0004] First, banking staff manually input various information for transaction messages through an existing message information table on a webpage. A separate master process table records the current process status, linking the message information table and the master process table via process number. If banking staff review and authorize messages through the message review and authorization pages respectively, the message status is updated to "Reviewed" and "Authorized."

[0005] Currently, manual input of messages on the page only supports one person at a time. When a business person starts maintenance, the message status will be locked as "under maintenance", and other business personnel will be prohibited from performing maintenance at this time.

[0006] In addition, the existing maintenance solutions do not handle sensitive information in the transaction messages, which is a major concern for the secure use of such information and therefore have low security. Summary of the Invention

[0007] This invention provides a method for collaborative maintenance of transaction messages by multiple users, enabling collaborative maintenance of bank transaction messages, improving maintenance efficiency, and enhancing the security of sensitive customer information. This method is applied to each user terminal maintaining transaction messages and includes:

[0008] Upon receiving a message maintenance request from the current user for a transaction message of the target type, a message record is generated based on the current user's message maintenance request and stored in the database;

[0009] Generate the first encrypted string corresponding to the message record and add it to the message record;

[0010] Create a new thread corresponding to this message record;

[0011] After receiving a field maintenance request from the current user for a field in a transaction message, the following steps are executed in the thread corresponding to that message record:

[0012] Generate the second encrypted string corresponding to the transaction message;

[0013] The newly generated second encrypted string is compared with the first encrypted string of the message record stored in the database;

[0014] If the verification passes, the field information of the field in the field maintenance request will be compared with the field information of the corresponding field in the message record stored in the database;

[0015] If the comparison is inconsistent, the field information of that field is updated in the database, and the field information of that field is broadcast to other user terminals that maintain transaction messages of the target type via a broadcast message, so that other user terminals can update the field information of the corresponding field after receiving the broadcast message.

[0016] This invention also provides a device for collaborative maintenance of transaction messages by multiple users, enabling collaborative maintenance of bank transaction messages, improving maintenance efficiency, and enhancing the security of sensitive customer information. This device is applied to each user terminal maintaining transaction messages and includes:

[0017] The message record generation module is used to generate a message record and store it in the database after receiving a message maintenance request from the current user for a transaction message of a target type.

[0018] The first encryption string generation module is used to generate the first encryption string corresponding to the message record and add it to the message record;

[0019] The thread creation module is used to create a new thread corresponding to this message record;

[0020] The field maintenance module, upon receiving a field maintenance request from the current user for a field in a transaction message, performs the following steps in the thread corresponding to that message record:

[0021] Generate the second encrypted string corresponding to the transaction message;

[0022] The newly generated second encrypted string is compared with the first encrypted string of the message record stored in the database;

[0023] If the verification passes, the field information of the field in the field maintenance request will be compared with the field information of the corresponding field in the message record stored in the database;

[0024] If the comparison is inconsistent, the field information of that field is updated in the database, and the field information of that field is broadcast to other user terminals that maintain transaction messages of the target type via a broadcast message, so that other user terminals can update the field information of the corresponding field after receiving the broadcast message.

[0025] This invention also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the above-mentioned method for collaborative maintenance of transaction messages by multiple users.

[0026] This invention also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the aforementioned method for collaborative maintenance of transaction messages by multiple users.

[0027] This invention also provides a computer program product, which includes a computer program that, when executed by a processor, implements the aforementioned method for collaborative maintenance of transaction messages by multiple users.

[0028] In this embodiment of the invention, upon receiving a message maintenance request from the current user for a transaction message of a target type, a message record is generated and stored in the database according to the current user's message maintenance request; a first encrypted string corresponding to the message record is generated and added to the message record; a new thread corresponding to the message record is created; upon receiving a field maintenance request from the current user for a field of a transaction message, the following steps are executed in the thread corresponding to the message record: a second encrypted string corresponding to the transaction message is generated; the newly generated second encrypted string is verified against the first encrypted string of the message record stored in the database; if the verification passes, the field information of the field in the field maintenance request is compared with the field information of the corresponding field stored in the message record in the database; if the comparison is inconsistent, the field information of the field is updated in the database, and the field information of the field is broadcast to other user terminals maintaining transaction messages of the target type via a broadcast message, so that other user terminals update the field information of the corresponding field after receiving the broadcast message. In the above process, the started thread processes asynchronously in the background without waiting, and updates the data maintained by others in real time after successful data synchronization, and this scheme also avoids most invalid updates. Meanwhile, based on the need for secure use of the large amount of sensitive information contained in transaction messages, additional encryption strings are provided at multiple stages through multi-threaded processing to enhance the security of customers' sensitive information. Attached Figure Description

[0029] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:

[0030] Figure 1This is a flowchart of a method for multiple people to collaboratively maintain transaction messages in an embodiment of the present invention;

[0031] Figure 2 This is a schematic diagram illustrating the method for multiple people collaboratively maintaining transaction messages in an embodiment of the present invention.

[0032] Figure 3 This is a flowchart illustrating how the user terminal processes received broadcast messages in an embodiment of the present invention.

[0033] Figure 4 This is a schematic diagram of a device for multiple people to collaboratively maintain transaction messages in an embodiment of the present invention;

[0034] Figure 5 This is a schematic diagram of a computer device in an embodiment of the present invention. Detailed Implementation

[0035] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings. Here, the illustrative embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention.

[0036] The acquisition, storage, use, and processing of data in this application all comply with the relevant provisions of national laws and regulations.

[0037] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0038] In this embodiment of the invention, the transaction message includes messages involved in the banking transaction process, such as the ISO20022 remittance message. ISO20022 is a new message standard that includes customer remittance messages, customer remittance-refund messages, interbank position transfer messages, status notification messages, debit and credit notification messages, and end-of-day statement messages. This discussion focuses only on the most frequently used customer remittance message, which requires maintenance by branch business, and the ISO20022 customer remittance message is simply referred to as a remittance message. Taking this remittance message as an example, when a customer prepares to initiate a remittance, banking personnel enter the reference number, currency, amount, value date, remitter number, remitter name, remitter address, payee number, payee name, payee address, institutional account information, fee payment method, entrusting institution information, receiving bank information, intermediary institution information, remittance information, and transaction remarks, which then constitute a remittance message. Based on the existing method of entering remittance messages, the existing technical solution is as follows:

[0039] Bank staff enter single remittance message information into the bank's system. The entry method for a single ISO20022 remittance message is as follows: the bank staff clicks "Start Maintaining Remittance Message" in the system, at which point the message is locked, allowing only one person to maintain it. Afterwards, the staff enters each element of the remittance message and saves it. Only after saving can the staff responsible for filling in other information continue to maintain the message. This method of remittance message entry typically results in multiple bank staff waiting for the same message for a long time, placing enormous pressure on branch operations responsible for maintaining different parts of the message. It is time-consuming and labor-intensive, increases the time it takes for remittances to arrive, and also increases the difficulty of customer acquisition.

[0040] Currently, due to concerns about potential deadlocks or unnecessary repeated updates in concurrent scenarios, updates are limited to one business user at a time. Additionally, the large amount of sensitive information contained in ISO 2022 remittance messages requires further consideration.

[0041] Figure 1 This is a flowchart of a method for collaborative maintenance of transaction messages by multiple users, as described in this embodiment of the invention. The method is applied to each user terminal maintaining transaction messages and includes:

[0042] Step 101: After receiving the message maintenance request from the current user for the target type of transaction message, generate a message record according to the current user's message maintenance request and store it in the database;

[0043] Step 102: Generate the first encrypted string corresponding to the message record and add it to the message record;

[0044] Step 103: Create a new thread corresponding to this message record;

[0045] Step 104: After receiving a field maintenance request from the current user for a field of a transaction message, the following steps are executed in the thread corresponding to that message record:

[0046] Generate the second encrypted string corresponding to the transaction message;

[0047] The newly generated second encrypted string is compared with the first encrypted string of the message record stored in the database;

[0048] If the verification passes, the field information of the field in the field maintenance request will be compared with the field information of the corresponding field in the message record stored in the database;

[0049] If the comparison is inconsistent, the field information of that field is updated in the database, and the field information of that field is broadcast to other user terminals that maintain transaction messages of the target type via a broadcast message, so that other user terminals can update the field information of the corresponding field after receiving the broadcast message.

[0050] In this embodiment of the invention, the started thread processes asynchronously in the background without waiting. Once data synchronization is successful, it updates the data maintained by others in real time, and this solution also avoids most invalid updates. Furthermore, based on the need for secure use of the large amount of sensitive information contained in transaction messages, multi-threaded processing provides additional encryption strings at multiple stages, enhancing the security of sensitive customer information.

[0051] The generated message record is currently under maintenance.

[0052] Each step is described in detail below. Figure 2 This is a schematic diagram illustrating the principle of a method for multiple people collaboratively maintaining transaction messages in an embodiment of the present invention. Figure 1 correspond, Figure 2 In the process, maintenance begins when a message maintenance request for the target type of transaction message is received from the current user. Each user client corresponds to one thread, and user clients can interact with each other. Figure 2 The example provided involves three user clients, with the leftmost user performing maintenance and broadcasting to the other two. Multiple users can initiate maintenance simultaneously, resulting in multiple records in the database with a status of "under maintenance."

[0053] In this embodiment of the invention, the message maintenance request is triggered by the current user selecting a transaction message identifier of the target type on the front-end page;

[0054] The field maintenance request is triggered when the current user leaves the field box after editing a field on the front-end page.

[0055] In one embodiment, the method further includes:

[0056] For each message record, if no field maintenance request is received within a preset time period, the encrypted string of the message record is destroyed through the thread of the message record, and the message record is deleted from the database.

[0057] By following the steps above, resources can be released in a timely manner, thus avoiding resource congestion.

[0058] In this embodiment of the invention, the first encrypted string is generated based on the machine identifier of the current user terminal, user information, current system time, and expiration time, wherein the expiration time is used to determine whether the message record has expired;

[0059] The second encrypted string is generated based on the current user's machine identifier, user information, current system time, and expiration time;

[0060] The newly generated second encrypted string is verified against the first encrypted string of the message record stored in the database. This includes: if the machine identifier and user information in the first encrypted string are consistent with the machine identifier and user information in the second encrypted string, and the current system time in the first encrypted string is earlier than the current system time in the second encrypted string, the verification is confirmed to be successful; otherwise, the verification fails.

[0061] In one embodiment, broadcasting the field information of this field to other user terminals that maintain transaction messages of the target type via a broadcast message includes:

[0062] Replace the first encrypted string with the second encrypted string and add it to the message record;

[0063] Retrieve the second encrypted string from other users' transaction messages for the target type from the database;

[0064] Add the second encrypted string to the broadcast message;

[0065] The field information of this field is broadcast to other user terminals that maintain transaction messages of the target type via a broadcast message.

[0066] In the above embodiment, the current user terminal will search the database to find the latest encrypted string, i.e. the second encrypted string, of the message record of each other user terminal, then add a broadcast message, and then send it to the corresponding other user terminal.

[0067] After other user terminals receive the broadcast message, they then determine whether to update. Figure 3 The flowchart for the user terminal processing the received broadcast message in this embodiment of the invention needs to determine whether the current user has modified the update field. If no modification has been made, the update is performed directly. If a modification has been made, the user should be prompted whether to update and decide whether to accept the update.

[0068] In one embodiment, the method further includes:

[0069] Upon receiving a broadcast message from another user, the following steps are executed in the thread corresponding to the transaction message in the broadcast message for the current user:

[0070] Generate the third encrypted string for the transaction message in the broadcast message;

[0071] Verify the third encrypted string against the second encrypted string in the broadcast message;

[0072] If the verification passes, check whether a field in the transaction message is being edited by the user.

[0073] If not, update the current field with the field information from the received transaction message;

[0074] If so, generate a notification message indicating that the field has changed;

[0075] If the current user receives the changes according to the prompt, update the current field with the field information in the received transaction message;

[0076] If the current user refuses to make changes based on the prompt, the system will receive the current user's field maintenance request for that field.

[0077] The third encrypted string is generated based on the current user's machine identifier, user information, current system time, and expiration time.

[0078] The third encrypted string is verified against the second encrypted string in the broadcast message. This includes: if the machine identifier and user information in the second encrypted string are consistent with the machine identifier and user information in the third encrypted string, and the current system time in the second encrypted string is earlier than the current system time in the third encrypted string, the verification is confirmed to be successful; otherwise, the verification fails.

[0079] This is because, for the user receiving the broadcast message, the second encrypted string in the broadcast message is specific to the currently receiving user, so the third encrypted string can be verified against the second encrypted string in the broadcast message.

[0080] In this embodiment of the invention, relying on multi-threaded processing, when certain fields (such as remittance amount) are modified to values ​​exceeding a certain limit, the permissions of the message will be dynamically elevated. After the permissions are elevated, based on the judgment of some existing management positions in the system, the message records of some users who do not have the permission to view the registered message will be locked, and a broadcast will be made to indicate that the current user's permissions cannot continue to modify the message. At the same time, the front-end page will gray out the relevant maintainable fields of the user and change them to an unmaintainable state.

[0081] In one embodiment, before generating the second encrypted string corresponding to the transaction message, the method further includes:

[0082] Determine whether the field information in the field maintenance request exceeds the editing range corresponding to the current user's editing permissions;

[0083] If so, gray out the field box containing that field and generate a prompt indicating that editing permissions have been exceeded;

[0084] If not, generate the second encrypted string corresponding to the transaction message.

[0085] In one embodiment, the method further includes:

[0086] After receiving a broadcast message from another user, determine whether the fields of the transaction message in the broadcast message exceed the editing range corresponding to the current user's editing permissions;

[0087] If so, gray out the field box containing that field and generate a prompt indicating that editing permissions have been exceeded.

[0088] This invention also proposes a device for multiple people to collaboratively maintain transaction messages. Its principle is similar to that of the method for multiple people to collaboratively maintain transaction messages, and will not be described in detail here.

[0089] Figure 4 This is a schematic diagram of a device for collaborative maintenance of transaction messages by multiple users, as described in an embodiment of the present invention. The device is applied to each user terminal maintaining transaction messages and includes:

[0090] The message record generation module 401 is used to generate a message record and store it in the database after receiving a message maintenance request from the current user for a transaction message of a target type.

[0091] The first encryption string generation module 402 is used to generate the first encryption string corresponding to the message record and add it to the message record;

[0092] Thread creation module 403 is used to create a new thread corresponding to this message record;

[0093] The field maintenance module 404, upon receiving a field maintenance request from the current user for a field in a transaction message, performs the following steps in the thread corresponding to the message record:

[0094] Generate the second encrypted string corresponding to the transaction message;

[0095] The newly generated second encrypted string is compared with the first encrypted string of the message record stored in the database;

[0096] If the verification passes, the field information of the field in the field maintenance request will be compared with the field information of the corresponding field in the message record stored in the database;

[0097] If the comparison is inconsistent, the field information of that field is updated in the database, and the field information of that field is broadcast to other user terminals that maintain transaction messages of the target type via a broadcast message, so that other user terminals can update the field information of the corresponding field after receiving the broadcast message.

[0098] In one embodiment, the message maintenance request is triggered when the current user selects a transaction message identifier of the target type on the front-end page;

[0099] The field maintenance request is triggered when the current user leaves the field box after editing a field on the front-end page.

[0100] In one embodiment, a message record destruction module is further included, used for:

[0101] For each message record, if no field maintenance request is received within a preset time period, the encrypted string of the message record is destroyed through the thread of the message record, and the message record is deleted from the database.

[0102] In one embodiment, the field maintenance module is used for:

[0103] Replace the first encrypted string with the second encrypted string and add it to the message record;

[0104] Retrieve the second encrypted string from other users' transaction messages for the target type from the database;

[0105] Add the second encrypted string to the broadcast message;

[0106] The field information of this field is broadcast to other user terminals that maintain transaction messages of the target type via a broadcast message.

[0107] In one embodiment, the apparatus further includes a broadcast message processing module, configured to:

[0108] Upon receiving a broadcast message from another user, the following steps are executed in the thread corresponding to the transaction message in the broadcast message for the current user:

[0109] Generate the third encrypted string for the transaction message in the broadcast message;

[0110] Verify the third encrypted string against the second encrypted string in the broadcast message;

[0111] If the verification passes, check whether a field in the transaction message is being edited by the user.

[0112] If not, update the current field with the field information from the received transaction message;

[0113] If so, generate a notification message indicating that the field has changed;

[0114] If the current user receives the changes according to the prompt information, update the current field with the field information in the received transaction message;

[0115] If the current user refuses to make changes based on the prompt, the system will receive the current user's field maintenance request for that field.

[0116] In one embodiment, the first encrypted string is generated based on the machine identifier of the current user terminal, user information, current system time, and expiration time, wherein the expiration time is used to determine whether the message record has expired;

[0117] The second encrypted string is generated based on the current user's machine identifier, user information, current system time, and expiration time;

[0118] The field maintenance module is specifically used to: if the machine identifier and user information in the first encrypted string are consistent with the machine identifier and user information in the second encrypted string, and the current system time in the first encrypted string is earlier than the current system time in the second encrypted string, the verification is confirmed to be successful; otherwise, the verification fails.

[0119] The third encrypted string is generated based on the current user's machine identifier, user information, current system time, and expiration time;

[0120] The broadcast message processing module is used to: determine that the verification passes if the machine identifier and user information in the second encrypted string are consistent with the machine identifier and user information in the third encrypted string, and the current system time in the second encrypted string is earlier than the current system time in the third encrypted string; otherwise, the verification fails.

[0121] The broadcast message processing module is also used for:

[0122] Before generating the second encrypted string corresponding to the transaction message, determine whether the field information in the field maintenance request exceeds the editing range corresponding to the current user's editing permissions;

[0123] If so, gray out the field box containing that field and generate a prompt indicating that editing permissions have been exceeded;

[0124] If not, generate the second encrypted string corresponding to the transaction message.

[0125] In one embodiment, the field maintenance module is used for:

[0126] After receiving a broadcast message from another user, determine whether the fields of the transaction message in the broadcast message exceed the editing range corresponding to the current user's editing permissions;

[0127] If so, gray out the field box containing that field and generate a prompt indicating that editing permissions have been exceeded.

[0128] In summary, the method and apparatus proposed in the embodiments of the present invention have the following beneficial effects:

[0129] Upon receiving a message maintenance request from the current user for a transaction message of the target type, a message record is generated and stored in the database based on the request. A first encrypted string corresponding to this message record is generated and added to the record. A new thread is created for this message record. Upon receiving a field maintenance request from the current user for a field of the transaction message, the following steps are performed in the thread corresponding to that message record: a second encrypted string corresponding to the transaction message is generated; the newly generated second encrypted string is verified against the first encrypted string of the message record stored in the database; if the verification passes, the field information in the field maintenance request is compared with the field information of the corresponding field stored in the message record in the database; if the comparison is inconsistent, the field information is updated in the database, and the field information is broadcast to other users maintaining transaction messages of the target type via a broadcast message, so that other users update their corresponding field information upon receiving the broadcast message. In the above process, the started thread processes asynchronously in the background without waiting. Data maintained by others is updated in real time after successful data synchronization, and this scheme also avoids most invalid updates. Meanwhile, based on the need for secure use of the large amount of sensitive information contained in transaction messages, additional encryption strings are provided at multiple stages through multi-threaded processing to enhance the security of customers' sensitive information.

[0130] This invention also provides a computer device. Figure 5 This is a schematic diagram of a computer device in an embodiment of the present invention. The computer device 500 includes a memory 510, a processor 520, and a computer program 530 stored in the memory 510 and executable on the processor 520. When the processor 520 executes the computer program 530, it implements the above-mentioned method for collaborative maintenance of transaction messages by multiple users.

[0131] This invention also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the aforementioned method for collaborative maintenance of transaction messages by multiple users.

[0132] This invention also provides a computer program product, which includes a computer program that, when executed by a processor, implements the aforementioned method for collaborative maintenance of transaction messages by multiple users.

[0133] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0134] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0135] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0136] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0137] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above descriptions are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for collaborative maintenance of transaction messages by multiple users, characterized in that, Applied to each client that maintains transaction messages, including: Upon receiving a message maintenance request from the current user for a transaction message of the target type, a message record is generated based on the current user's message maintenance request and stored in the database; Generate the first encrypted string corresponding to the message record and add it to the message record; Create a new thread corresponding to this message record; After receiving a field maintenance request from the current user for a field in a transaction message, the following steps are executed in the thread corresponding to that message record: Generate the second encrypted string corresponding to the transaction message; The newly generated second encrypted string is compared with the first encrypted string of the message record stored in the database; If the verification passes, the field information of the field in the field maintenance request will be compared with the field information of the corresponding field in the message record stored in the database; If the comparison is inconsistent, the field information of that field is updated in the database, and the field information of that field is broadcast to other user terminals that maintain transaction messages of the target type via a broadcast message, so that other user terminals can update the field information of the corresponding field after receiving the broadcast message.

2. The method as described in claim 1, characterized in that, The message maintenance request is triggered when the current user selects the target type of transaction message identifier on the front-end page; The field maintenance request is triggered when the current user leaves the field box after editing a field on the front-end page.

3. The method as described in claim 1, characterized in that, Also includes: For each message record, if no field maintenance request is received within a preset time period, the encrypted string of the message record is destroyed through the thread of the message record, and the message record is deleted from the database.

4. The method as described in claim 1, characterized in that, The field information of this field is broadcast via a broadcast message to other user terminals that maintain transaction messages of the target type, including: Replace the first encrypted string with the second encrypted string and add it to the message record; Retrieve the second encrypted string from other users' transaction messages for the target type from the database; Add the second encrypted string to the broadcast message; The field information of this field is broadcast to other user terminals that maintain transaction messages of the target type via a broadcast message.

5. The method as described in claim 4, characterized in that, Also includes: Upon receiving a broadcast message from another user, the following steps are executed in the thread corresponding to the transaction message in the broadcast message for the current user: Generate the third encrypted string for the transaction message in the broadcast message; Verify the third encrypted string against the second encrypted string in the broadcast message; If the verification passes, check whether a field in the transaction message is being edited by the user. If not, update the current field with the field information from the received transaction message; If so, generate a notification message indicating that the field has changed; If the current user accepts the changes according to the prompt, update the current field with the field information from the received transaction message; If the current user refuses to make changes based on the prompt, the system will receive the current user's field maintenance request for that field.

6. The method as described in claim 5, characterized in that, The first encrypted string is generated based on the current user's machine identifier, user information, current system time, and expiration time. The expiration time is used to determine whether the message record has expired. The second encrypted string is generated based on the current user's machine identifier, user information, current system time, and expiration time; The newly generated second encrypted string is verified against the first encrypted string of the message record stored in the database. This includes: if the machine identifier and user information in the first encrypted string are consistent with the machine identifier and user information in the second encrypted string, and the current system time in the first encrypted string is earlier than the current system time in the second encrypted string, the verification is confirmed to be successful; otherwise, the verification fails. The third encrypted string is generated based on the current user's machine identifier, user information, current system time, and expiration time; The third encrypted string is verified against the second encrypted string in the broadcast message. This includes: if the machine identifier and user information in the second encrypted string are consistent with the machine identifier and user information in the third encrypted string, and the current system time in the second encrypted string is earlier than the current system time in the third encrypted string, the verification is confirmed to be successful; otherwise, the verification fails.

7. The method as described in claim 1, characterized in that, Before generating the second encrypted string corresponding to the transaction message, the process also includes: Determine whether the field information in the field maintenance request exceeds the editing range corresponding to the current user's editing permissions; If so, gray out the field box containing that field and generate a prompt indicating that editing permissions have been exceeded; If not, generate the second encrypted string corresponding to the transaction message.

8. The method as described in claim 7, characterized in that, Also includes: After receiving a broadcast message from another user, determine whether the fields of the transaction message in the broadcast message exceed the editing range corresponding to the current user's editing permissions; If so, gray out the field box containing that field and generate a prompt indicating that editing permissions have been exceeded.

9. A device for collaborative maintenance of transaction messages by multiple users, characterized in that, Applied to each client that maintains transaction messages, including: The message record generation module is used to generate a message record and store it in the database after receiving a message maintenance request from the current user for a transaction message of a target type. The first encryption string generation module is used to generate the first encryption string corresponding to the message record and add it to the message record; The thread creation module is used to create a new thread corresponding to this message record; The field maintenance module, upon receiving a field maintenance request from the current user for a field in a transaction message, performs the following steps in the thread corresponding to that message record: Generate the second encrypted string corresponding to the transaction message; The newly generated second encrypted string is compared with the first encrypted string of the message record stored in the database; If the verification passes, the field information of the field in the field maintenance request will be compared with the field information of the corresponding field in the message record stored in the database; If the comparison is inconsistent, the field information of that field is updated in the database, and the field information of that field is broadcast to other user terminals that maintain transaction messages of the target type via a broadcast message, so that other user terminals can update the field information of the corresponding field after receiving the broadcast message.

10. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method of any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method of any one of claims 1 to 8.

12. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the method of any one of claims 1 to 8.

Images