A front-end and back-end message processing method, device and medium

Abstract

The application provides a front-end and back-end message processing method, device and medium. Based on a first operation of a user on a user terminal, at least one interaction request information is determined. The interaction request information is sent to a server to parse the interaction request information by the server and obtain an interaction information list corresponding to the interaction request information. The interaction information list includes at least one back-end message box, and the back-end message box includes at least an interaction information label, an interaction information attribute, an interaction prompt information and an interaction information content. Each interaction information in the interaction information list is sequentially added to an interaction information array. The interaction information array includes at least one front-end message box. The front-end message box is a pre-constructed information interaction container. Based on the interaction information array, an interaction feedback information corresponding to the interaction request information is generated. The interaction feedback information includes at least one interaction information content.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to a front-end and back-end message processing method, device and medium. Background Technology

[0002] In the software development industry, the mainstream technology is a front-end and back-end separation architecture, which generates a user-system interaction requirement. Under the current logic, the interaction behavior is relatively cumbersome and generates many fragmented requests, resulting in significant resource locking and connection consumption on the server during resource waiting.

[0003] Therefore, the key is to facilitate multiple interactions with users while minimizing backend resource consumption, processing all requests at once as much as possible, and avoiding data sharding. Summary of the Invention

[0004] This application provides a front-end and back-end message processing method, device, and medium to enable the back-end to conveniently interact with the user multiple times, while minimizing the back-end's resource consumption and processing all requests at once as much as possible to avoid fragmentation.

[0005] On the one hand, embodiments of this application provide a front-end and back-end message processing method, the method including:

[0006] Based on the user's first action on the user terminal, at least one interactive request information is determined;

[0007] The interaction request information is sent to the server so that the server can parse the interaction request information and obtain the interaction information list corresponding to the interaction request information; the interaction information list includes at least one backend message box, and the backend message box includes at least an interaction information number, interaction information attributes, interaction prompt information, and interaction information content;

[0008] Each interactive message in the interactive information list is added to the interactive information array in sequence; the interactive information array includes at least one front-end message box; the front-end message box is a pre-built information interaction container;

[0009] Based on the interaction information array, corresponding interaction feedback information is generated for the interaction request information; the interaction feedback information includes at least one interaction information content.

[0010] In one implementation of this application, when the server receives the interaction request information, it parses the interaction request information and determines the logical judgment sub-information corresponding to the interaction request information;

[0011] The server matches the logical judgment type corresponding to each logical judgment sub-information in the preset database;

[0012] Based on the logical judgment type and the logical judgment result of the corresponding logical judgment sub-information, the server generates backend message boxes for each logical judgment sub-information and generates the interactive information list in a predetermined order.

[0013] In one implementation of this application, when the logical judgment type is an authorization judgment type, the logical judgment result of the corresponding logical judgment sub-information is determined, so as to determine whether to generate the backend message box based on the logical judgment result;

[0014] When the logical judgment type is an inquiry business type, a backend message box for the logical judgment sub-information is generated, and the backend message box is added to the interaction information list in a predetermined order.

[0015] In one implementation of this application, the interaction information attribute corresponding to each message element in the interaction information array is determined;

[0016] Message elements whose interactive information attributes satisfy the same first preset attribute are identified as message elements to be merged.

[0017] The message elements to be merged are merged in a predetermined order to determine the merged message elements, and the interactive feedback information is generated based on the merged message elements and the interactive information array.

[0018] In one implementation of this application, when the message element has an interaction information attribute of a second preset attribute, a custom pop-up corresponding to the message element with the second preset attribute is matched; the custom pop-up is preset.

[0019] The interactive feedback information is generated based on the custom pop-up and its corresponding message elements and the merged message elements.

[0020] In one implementation of this application, it is determined whether the interaction information label in the interaction information array is consistent with the interaction information label in the interaction list;

[0021] If so, match the display call logic corresponding to each message element in the interaction information array;

[0022] The interactive feedback information is generated based on the display call logic.

[0023] In one implementation of this application, each merged message element and each unmerged message element in the interaction information array are sequentially displayed on the user terminal as the interaction feedback information;

[0024] Based on the user's second operation on the user terminal, the callback method corresponding to each of the interactive feedback messages is matched respectively.

[0025] In one implementation of this application, the method is applied to a blockchain platform; the blockchain platform includes several nodes; the user terminal corresponds to any node; after matching the callback methods corresponding to each of the interactive feedback information based on the user's second operation on the user terminal, the method further includes:

[0026] The user's second action and the interaction feedback information are sent to any block of the blockchain platform.

[0027] On the other hand, embodiments of this application also provide a front-end and back-end message processing device, the device comprising:

[0028] At least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

[0029] Based on the user's first action on the user terminal, at least one interactive request information is determined;

[0030] The interaction request information is sent to the server so that the server can parse the interaction request information and obtain the interaction information list corresponding to the interaction request information; the interaction information list includes at least one backend message box, and the backend message box includes at least an interaction information number, interaction information attributes, interaction prompt information, and interaction information content;

[0031] Each interactive message in the interactive information list is added to the interactive information array in sequence; the interactive information array includes at least one front-end message box; the front-end message box is a pre-built information interaction container;

[0032] Based on the interaction information array, corresponding interaction feedback information is generated for the interaction request information; the interaction feedback information includes at least one interaction information content.

[0033] Furthermore, embodiments of this application also provide a non-volatile computer storage medium for front-end and back-end message processing, storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0034] Based on the user's first action on the user terminal, at least one interactive request information is determined;

[0035] The interaction request information is sent to the server so that the server can parse the interaction request information and obtain the interaction information list corresponding to the interaction request information; the interaction information list includes at least one backend message box, and the backend message box includes at least an interaction information number, interaction information attributes, interaction prompt information, and interaction information content;

[0036] Each interactive message in the interactive information list is added to the interactive information array in sequence; the interactive information array includes at least one front-end message box; the front-end message box is a pre-built information interaction container;

[0037] Based on the interaction information array, corresponding interaction feedback information is generated for the interaction request information; the interaction feedback information includes at least one interaction information content.

[0038] This application, through the aforementioned solution, enables convenient multiple interactions between the backend and the user, while minimizing backend resource consumption and processing all requests in one go as much as possible, avoiding fragmentation. It also improves the convenience of user-system interaction by using the standard input and output parameters defined in this application. The message box group (frontend message box, backend message box) serves as an interaction bridge for frontend and backend data, interface, logic control, and communication, making system-user interaction easier and allowing the system to more clearly understand user choices. Furthermore, the display effect when asking whether to continue supports customization.

[0039] This application enables systems with a front-end and back-end separation architecture to facilitate interaction between the front-end and back-end systems, and between users and the front-end system, making development faster, saving coding effort, improving coding efficiency, enhancing communication efficiency between the front-end and back-end, and reducing the development cost of complex interactive software. Attached Figure Description

[0040] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0041] Figure 1 This is a flowchart illustrating a front-end and back-end message processing method in an embodiment of this application.

[0042] Figure 2 This is a schematic diagram of the structure of a front-end and back-end message processing device in an embodiment of this application. Detailed Implementation

[0043] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0044] In the software development industry, the mainstream technology is a front-end and back-end separation architecture. This generates a user-system interaction requirement. Under complex logic, each click of a user's interactive pop-up prompts a further request, which is cumbersome and generates many fragmented requests. This puts significant resource locking on the server and consumes connections while waiting for resources. Given this situation, how to facilitate multiple interactions with the user while minimizing back-end resource consumption and processing all requests at once as much as possible, avoiding fragmentation, becomes of paramount importance.

[0045] This application provides a front-end and back-end message processing method, device, and medium to enable the back-end to conveniently interact with the user multiple times, while minimizing the back-end's resource consumption and processing all requests at once as much as possible to avoid fragmentation.

[0046] The various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0047] This application provides a front-end and back-end message processing method, such as... Figure 1 As shown, the method may include steps S101-S104:

[0048] S101, the front-end server determines at least one interactive request information based on the user's first operation on the user terminal.

[0049] Users can perform operations through the user terminal's display page. For example, when submitting a business expense report, after entering the expense report information on the page, such as amount, remarks, and name, the user clicks to submit the expense report information, which is the first operation. The front-end server can receive the interaction request information corresponding to this first operation.

[0050] An interactive request can be understood as a user submitting expense reports. The server can then review each item in the expense report, such as the amount and any notes. The review results are then confirmed with the user, thus generating the interactive action.

[0051] S102, the front-end server sends the interaction request information to the server so that the server can parse the interaction request information and obtain the list of interaction information corresponding to the interaction request information.

[0052] The interactive information list must include at least one backend message box, and the backend message box must include at least the interactive information label, interactive information attributes, interactive prompts, and interactive information content.

[0053] The interaction information labels in the backend message box and the frontend message box are consistent, which ensures that the messages in the backend message box and the frontend message box are the same set of message content.

[0054] The aforementioned server refers to the backend server.

[0055] In this embodiment of the application, the interaction request information is sent to the backend server so that the server can parse the interaction request information and obtain a list of interaction information corresponding to the interaction request information, specifically including:

[0056] Upon receiving an interaction request, the server parses the request and determines the corresponding logical judgment sub-information. The server matches the logical judgment type corresponding to each sub-information in a pre-defined database. Based on the logical judgment type and the logical judgment result of its corresponding sub-information, the server generates backend message boxes for each sub-information and creates an interaction information list in a predetermined order.

[0057] Specifically, when the logical judgment type is the permission judgment type, the logical judgment result of the corresponding logical judgment sub-information is determined, so as to determine whether to generate a backend message box based on the logical judgment result.

[0058] When the logical judgment type is a query business type, generate a backend message box for logical judgment sub-information and add the backend message box to the interaction information list in a predetermined order.

[0059] In other words, the backend server can parse the interaction request information. For example, the interaction request information may include four logical judgment sub-information, such as w, x, y, and z. For instance, w is the permission judgment type, and its logical judgment result is that it is permissible at this time. x is a query business type: prompting the user whether to continue the interaction. In this case, x is added to the interaction information list List. <backbillmessagebox>A backend message box (backBillMessageBox) is defined, where the interaction information label (code) is assigned the value 'x', and the interaction prompt message (message) is assigned the value asking whether to continue. The interaction information attribute (group) is set to 1, indicating that it can be merged. 'y' represents another query business type, and similarly, these are pushed into a List. <backbillmessagebox>A `backBillMessageBox` needs to prompt the user whether to continue (y). A group of 1 allows for merging. `z` represents a table query indicating the business type, prompting the user whether to continue if the table's data has reached a critical state. Similarly, it can continue pushing data into a `List`. <backbillmessagebox>A backBillMessageBox needs to prompt the user whether to continue. The group is 0 and cannot be merged. The value of the interactive message is the table data to be displayed.

[0060] S103, the front-end server adds each piece of interactive information from the interactive information list to the interactive information array in sequence.

[0061] The interactive information array must include at least one front-end message box. The front-end message box is a pre-built information interaction container.

[0062] Generate an interactive information list on the backend server, and store the backend List. <backbillmessagebox>The data is sent to the front-end server, which receives the List using interactive information data. <backbillmessagebox>The front-end message box in the interactive information array is a pre-built interactive information container jsBillMessageBox containing pre-defined parameters: interactive information label: code, display call logic: func, and callback method: callBack.

[0063] S104, the front-end server generates corresponding interactive feedback information based on the interactive information array.

[0064] Interactive feedback information must include at least one piece of interactive information content.

[0065] In this embodiment, the front-end server can determine whether message elements in the interaction information array need to be merged, and based on the interaction information array, generate corresponding interaction feedback information for the interaction request information, specifically including:

[0066] First, the front-end server determines the interaction information attributes corresponding to each message element in the interaction information array.

[0067] This interactive information attribute corresponds to the interactive information attribute of the backend message box, including whether it can be merged or not.

[0068] Next, the front-end server determines message elements whose interaction information attributes satisfy the same first preset attribute as message elements to be merged.

[0069] The first default attribute is group=1. If you need to merge the content of group=1, then combine the two messages into one after adding a newline.

[0070] Then, the front-end server merges each message element to be merged in a predetermined order, determines the message elements to be merged, and generates interactive feedback information based on the merged message elements and the interaction information array.

[0071] In one embodiment of this application, when a message element has an interactive information attribute of a second preset attribute, a custom pop-up corresponding to the message element with the second preset attribute is matched. The custom pop-up is preset.

[0072] The second preset attribute is group=0.

[0073] The front-end server generates interactive feedback information based on the custom pop-up and its corresponding message elements, as well as the merged message elements.

[0074] In this embodiment of the application, there may also be a third preset attribute and group=2, and the front-end message box of the third preset attribute may also have a corresponding custom pop-up.

[0075] In this embodiment of the application, the custom pop-up can be provided by the developers of the backend server, such as a pop-up template that displays table information.

[0076] In this embodiment of the application, the front-end server generates interactive feedback information corresponding to the interactive request information based on the interactive information array, specifically including:

[0077] The front-end server determines whether the interaction information number in the interaction information array matches the interaction information number in the interaction list.

[0078] If the interaction information number in the interaction information array matches the interaction information number in the interaction list, the display call logic corresponding to each message element in the interaction information array is matched. Based on the display call logic, interactive feedback information is generated.

[0079] This display call logic can trigger the call to the corresponding call method in the message returned by the backend, so as to control the execution of the frontend logic. For example, based on the same message number, this custom call method can be used to display whether the message sent by the backend is a chart or a text query.

[0080] The implementation code is as follows:

[0081] front end:

[0082]

[0083] rear end:

[0084]

[0085]

[0086] In this embodiment of the application, the front-end message box also includes a description of the actual business significance corresponding to the front-end message box.

[0087] After the front-end server generates the corresponding interaction feedback information based on the interaction information array, it also includes:

[0088] The front-end server displays the merged and unmerged message elements from the interaction information array sequentially as interactive feedback information to the user's terminal. Based on the user's second action on the user's terminal, the front-end server matches the callback method corresponding to each interactive feedback information.

[0089] In other words, when displaying interactive feedback information on the front-end server, message elements with group=1 can be combined for display. For example, after a reimbursement form is submitted, if the amount and account name information on the form are inconsistent with the corresponding information stored in the back-end, the user may need to be prompted to confirm whether to continue. In existing front-end and back-end interactions, the back-end and front-end need to display the confirmation message separately. The front-end server in this application can recombine the interactive information, merging the amount and account name confirmation messages, and then displaying the confirmation message in a pop-up window.

[0090] This application's embodiments can be applied to a blockchain platform. The blockchain platform includes several nodes. A user terminal corresponds to any node. Based on the user's second operation on the user terminal, after matching the callback methods corresponding to each interactive feedback message, the method further includes:

[0091] The front-end server sends the user's second action and interaction feedback information to any block on the blockchain platform.

[0092] For example, in business expense reporting, the information includes the account name, amount, and specific reporting type. After the user clicks submit, the front-end sends the data to the back-end. The back-end determines whether to merge the data. Based on whether the data is merged or not, the front-end matches the displayed logic and then displays interactive feedback. Next, it retrieves the user's actions and, based on those actions, calls callback methods to determine the corresponding callback functions. Then, it adjusts the relevant message content, such as generating a record item table to record the operation. For example, if someone else is reporting an expense on behalf of another and the account name is incorrect, but the user still chooses to continue, a record table for reporting an expense on behalf of another can be generated to record this operation. This application can send the record table for reporting an expense on behalf of another to the blockchain platform.

[0093] In this embodiment of the application, the application can be executed in a loop, displaying each front-end message box in the interaction information array until all the content that needs to be prompted in the back-end server corresponding to the interaction request information is displayed and interacted with by the user.

[0094] In one embodiment of this application, the front-end and back-end message processing method can make a back-end request once and return content to the front-end that supports multiple pop-up query interfaces and interaction with the user, supports merging multiple messages, and supports custom style pop-ups for messages.

[0095] The message box needs to be divided into a front-end message box and a back-end message box. The front-end message box includes: message ID, calling method, callback method, and description. The back-end message box includes: message ID, message notification information, message type flag, and message content.

[0096] And it is able to:

[0097] (1) One backend request: The frontend interface makes one request, and the backend obtains all the necessary information to interact with the user and ask whether to continue based on the requested interface, forming several sets of business logic to be asked. Then, when returning, it is put into the backend message box to be returned and transmitted to the frontend.

[0098] (2) Supports multiple pop-up queries: The returned business logic is looped through by the front-end script and the user is asked whether to continue. If the user clicks yes, the user will continue to ask for the next message.

[0099] (3) Support message merging: merge the content of messages asking whether to continue and display them to the front-end user at once.

[0100] (4) Support for custom style pop-ups: The pop-up asking whether to continue can be changed to a custom style pop-up, making the message more intuitive, clear and easy to understand.

[0101] This application, through the aforementioned solution, enables convenient multiple interactions between the backend and the user, while minimizing backend resource consumption and processing all requests in one go as much as possible, avoiding fragmentation. It also improves the convenience of user-system interaction by using the standard input and output parameters defined in this application. The message box group (frontend message box, backend message box) serves as an interaction bridge for frontend and backend data, interface, logic control, and communication, making system-user interaction easier and allowing the system to more clearly understand user choices. Furthermore, the display effect when asking whether to continue supports customization.

[0102] This application enables systems with a front-end and back-end separation architecture to facilitate interaction between the front-end and back-end systems, and between users and the front-end system, making development faster, saving coding effort, improving coding efficiency, enhancing communication efficiency between the front-end and back-end, and reducing the development cost of complex interactive software.

[0103] Figure 2 A front-end and back-end message processing device provided in this application embodiment includes:

[0104] At least one processor. And a memory communicatively connected to the at least one processor. The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to:

[0105] Based on the user's first action on the user terminal, at least one interactive request message is determined.

[0106] The interaction request information is sent to the server, which then parses it to obtain a list of corresponding interaction information. The list of interaction information includes at least one backend message box, which in turn includes at least an interaction information label, interaction information attributes, interaction prompts, and interaction information content.

[0107] Each interactive message in the interactive message list is added sequentially to the interactive message array. The interactive message array must contain at least one front-end message box. The front-end message box is a pre-built information interaction container.

[0108] Based on the interaction information array, generate corresponding interaction feedback information for the interaction request information. The interaction feedback information must include at least one interaction information item.

[0109] This application embodiment also provides a non-volatile computer storage medium for front-end and back-end message processing, storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0110] Based on the user's first action on the user terminal, at least one interactive request message is determined.

[0111] The interaction request information is sent to the server, which then parses it to obtain a list of corresponding interaction information. The list of interaction information includes at least one backend message box, which in turn includes at least an interaction information label, interaction information attributes, interaction prompts, and interaction information content.

[0112] Each interactive message in the interactive message list is added sequentially to the interactive message array. The interactive message array must contain at least one front-end message box. The front-end message box is a pre-built information interaction container.

[0113] Based on the interaction information array, generate corresponding interaction feedback information for the interaction request information. The interaction feedback information must include at least one interaction information item.

[0114] Those skilled in the art will understand that embodiments of this specification can be provided as methods, apparatus, or computer program products. Therefore, embodiments of this specification can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, embodiments of this specification can take the form of computer program products 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.

[0115] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. 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, create a machine 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.

[0116] 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.

[0117] 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.

[0118] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0119] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0120] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0121] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0122] This specification can be described in the general context of computer-executable instructions that are executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This specification can also be practiced in distributed computing environments, where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0123] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments for devices and non-volatile computer storage media are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0124] The devices, media, and methods provided in this application are one-to-one correspondences. Therefore, the devices and media also have similar beneficial technical effects as their corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0125] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0126] The above description is merely one or more embodiments of this specification and is not intended to limit this specification. Various modifications and variations can be made to the one or more embodiments of this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of one or more embodiments of this specification should be included within the scope of the claims of this specification.< / backbillmessagebox> < / backbillmessagebox> < / backbillmessagebox> < / backbillmessagebox> < / backbillmessagebox>

Claims

1. A front-end and back-end message processing method, characterized in that, The method includes: Based on the user's first action on the user terminal, at least one interactive request information is determined; The interaction request information is sent to the server so that the server can parse the interaction request information and obtain the interaction information list corresponding to the interaction request information; the interaction information list includes at least one backend message box, and the backend message box includes at least an interaction information number, interaction information attributes, interaction prompt information, and interaction information content; Each interactive message in the interactive information list is added to the interactive information array in sequence; the interactive information array includes at least one front-end message box; the front-end message box is a pre-built information interaction container; Based on the interaction information array, corresponding interaction feedback information is generated for the interaction request information; the interaction feedback information includes at least one interaction information content. Specifically, the interaction request information is sent to a server, which then parses the interaction request information to obtain a list of interaction information corresponding to the interaction request information. When the server receives the interaction request information, it parses the interaction request information and determines the logical judgment sub-information corresponding to the interaction request information. The server matches the logical judgment type corresponding to each logical judgment sub-information in the preset database; The server generates backend message boxes for each logical judgment sub-information based on the logical judgment type and the logical judgment result of the corresponding logical judgment sub-information, and generates the interactive information list in a predetermined order; specifically including: When the logical judgment type is an authorization judgment type, the logical judgment result of the corresponding logical judgment sub-information is determined, so as to determine whether to generate the backend message box based on the logical judgment result; When the logical judgment type is an inquiry business type, a backend message box for the logical judgment sub-information is generated, and the backend message box is added to the interaction information list in a predetermined order; Specifically, generating interactive feedback information corresponding to the interactive request information based on the interactive information array includes: Determine the interaction information attribute corresponding to each message element in the interaction information array; Message elements whose interactive information attributes satisfy the same first preset attribute are identified as message elements to be merged. The message elements to be merged are merged in a predetermined order to determine the merged message elements, and the interactive feedback information is generated based on the merged message elements and the interactive information array.

2. The method according to claim 1, characterized in that, The method further includes: In the case of a message element whose interactive information attribute is a second preset attribute, a custom pop-up corresponding to the message element with the second preset attribute is matched; the custom pop-up is preset. The interactive feedback information is generated based on the custom pop-up and its corresponding message elements and the merged message elements.

3. The method according to claim 1, characterized in that, Based on the interaction information array, corresponding interaction feedback information is generated for the interaction request information, specifically including: Determine whether the interaction information index in the interaction information array is consistent with the interaction information index in the interaction information list; If so, match the display call logic corresponding to each message element in the interaction information array; The interactive feedback information is generated based on the display call logic.

4. The method according to claim 1, characterized in that, After generating the corresponding interactive feedback information based on the interactive information array, the method further includes: Each merged message element and each unmerged message element in the interactive information array are sequentially displayed on the user terminal using the interactive feedback information. Based on the user's second operation on the user terminal, the callback method corresponding to each of the interactive feedback messages is matched respectively.

5. The method according to claim 4, characterized in that, The method is applied to a blockchain platform; the blockchain platform includes several nodes; the user terminal corresponds to any one of the nodes; Based on the user's second operation on the user terminal, after matching the callback methods corresponding to each of the interactive feedback messages, the method further includes: The user's second action and the interaction feedback information are sent to any block of the blockchain platform.

6. A front-end and back-end message processing device, characterized in that, The device includes: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform a front-end and back-end message processing method as described in any one of claims 1-5.

7. A non-volatile computer storage medium for front-end and back-end message processing, storing computer-executable instructions, characterized in that, The computer-executable instructions are capable of executing a front-end and back-end message processing method as described in any one of claims 1-5.

Images