A data interaction method and device

Abstract

The application provides a data interaction method and device, applied to the field of information security technology, to improve the security of front-end and back-end system data interaction. The method comprises: receiving a target request message from a terminal; wherein the target request message contains at least two operation instructions, and the execution order of the operation corresponding to each operation instruction; analyzing the target request message, and sequentially executing the operation corresponding to the operation instruction based on the execution order; when the operation corresponding to the last operation instruction in the target request message is completed, sending operation completion information to the terminal, so that the terminal determines the operation result corresponding to the target request message based on the operation completion information.

Description

Technical Field

[0001] This application relates to the field of information security technology, specifically to a data interaction method and apparatus. Background Technology

[0002] With the continuous development of internet technology and the increasing popularity of mobile devices, more and more users are choosing to use mobile devices to complete operations that were previously only possible offline or at fixed business locations. For example, payment operations that were originally completed offline are now gradually being replaced by mobile payments, with users opting for more convenient and faster online transactions.

[0003] To meet users' online operation needs, the developers have provided a solution for separate front-end and back-end deployment. The front-end system is deployed on the terminal device, and the back-end system is deployed on the server. Through the combined effect of the front-end and back-end systems, users can be provided with complete online operation.

[0004] For example, in the mobile payment scenario, users provide operation instructions and identity information to the backend system through the front-end system on their own terminal devices. The backend system on the server then performs the corresponding payment operation based on the received content, continuously feeding back various information about the payment process to the front-end system. In this way, through the interaction between the front-end and back-end, payment service providers can provide stable payment services to a large number of users.

[0005] However, within this operational framework, a security issue that cannot be ignored exists. Because users choose from a wide variety of front-end systems, most of which connect to back-end systems via application programming interfaces (APIs) to complete front-end and back-end interaction, the environment in which the front-end system operates cannot guarantee its own security. For example, malware files potentially present on the terminal device can severely compromise the security of the front-end system; and during front-end and back-end data interaction, important data may be hijacked or tampered with during the transfer process. All these issues affect the security of data exchange between the front-end and back-end systems.

[0006] Therefore, improving the security of data interaction between front-end and back-end systems is an urgent problem to be solved. Summary of the Invention

[0007] This application provides a data processing method and apparatus to improve the security of data interaction between front-end and back-end systems.

[0008] In a first aspect, this application provides a data interaction method applied to a server in a financial system. The method includes: receiving a target request message from a terminal; wherein the target request message contains at least two operation instructions and an execution order of operations corresponding to each operation instruction; parsing the target request message and, based on the execution order, sequentially executing the operations corresponding to the operation instructions; and, after completing the operation corresponding to the last operation instruction in the target request message, sending operation completion information to the terminal so that the terminal determines the operation result corresponding to the target request message based on the operation completion information.

[0009] In this solution, the server receives all operation instructions and corresponding information at once through the target request message, reducing the number of interactions between the terminal and the server, lowering the risk of data leakage during data flow, and improving the security of data interaction. Simultaneously, the financial system's server controls the data flow between the terminal and the server internally, leveraging the inherent security of the financial system server itself, reducing data transmission over the internet, and avoiding the problem of excessive data exposure leading to interception or bypassing.

[0010] Optionally, the target request message includes a first array and a second array; the elements in the first array are used to indicate the operation instruction identifier, execution order identifier, and attribute information identifier contained in each operation instruction; wherein, the execution order identifier is used to indicate the execution order of the operation corresponding to each operation instruction among all the operations corresponding to all operation instructions; the elements in the second array are used to indicate that each attribute information identifier in the first array corresponds to at least one attribute information; wherein, the attribute information is used to indicate the information required to perform the operation.

[0011] In this approach, the first array records the operation instruction identifier, execution order identifier, and attribute information identifier corresponding to each operation instruction through its elements. Thus, when faced with different numbers of operation instructions, the information of each operation instruction can be recorded in a structured manner using different numbers of elements, effectively improving the scalability of the first array. Furthermore, by recording the attribute information of each operation through the second array, the elements in the second array can be flexibly matched according to the request content of each operation in actual use, achieving dynamic scalability of the target request message.

[0012] Optionally, the step of sequentially executing the operations corresponding to the operation instructions based on the execution order includes: sequentially executing the operations corresponding to the operation instructions based on the execution order; when any operation corresponding to the operation instruction fails to execute, stopping the response to subsequent operation instructions and sending an abnormal alarm message to the terminal.

[0013] In this approach, when any operation fails, the server needs to send an error alarm to the terminal, thus preventing the information from being tampered with and effectively improving the security of this solution.

[0014] Optionally, if the at least two operation instructions include an authentication instruction, and the authentication instruction is the first execution object in the execution order, then before executing other operations among the at least two operation instructions other than the authentication instruction, the method further includes: when it is determined that the operation corresponding to the authentication instruction has been completed and the execution result of the operation corresponding to the authentication instruction has been obtained, determining the execution result of the operation corresponding to the authentication instruction; if it is determined that the execution result is that the identity information is legitimate, then continuing to execute the other operations; if it is determined that the execution result is that the identity information is illegitimate, then stopping the execution of the other operations and sending the abnormal alarm information to the terminal.

[0015] In this approach, when an authentication command is present, the server can only perform subsequent operations after confirming that the authentication operation has been performed and that the authentication is valid. This reduces the risk of the authentication operation being skipped or tampered with, and further improves the security of this solution.

[0016] Secondly, this application provides a data interaction method applied to a terminal in a financial system. The method includes: generating a target request message; wherein the target request message contains at least two operation instructions and an execution order of operations corresponding to each operation instruction; sending the target request message to a server, so that the server parses the target request message and, based on the execution order, sequentially executes the operations corresponding to the operation instructions; after completing the operation corresponding to the last operation instruction in the target request message, sending operation completion information to the terminal; receiving the operation completion information from the server, and determining the operation result corresponding to the target request message based on the operation completion information.

[0017] In this solution, the terminal generates a target request message by combining request information from several operations and sends it to the server. After the server completes all operations, the terminal receives operation completion information from the server and determines the operation result of the target request message based on this information. This minimizes the number of data transfers between the terminal and the server, effectively reducing the risk of data leakage during data interaction and improving the security of this solution.

[0018] Optionally, generating the target request message includes: in response to a target scenario triggering instruction, generating the at least two operation instructions and obtaining at least one attribute information corresponding to each operation instruction; wherein the attribute information is used to indicate the information required to execute the operation corresponding to each operation instruction; determining the execution order when the server executes the operations corresponding to the at least two operation instructions based on the configuration information of the target scenario; and generating the target request message based on the at least two operation instructions, the attribute information corresponding to each operation instruction, and the execution order.

[0019] In this approach, based on scenario requirements, after receiving a trigger command for the target scenario, the terminal can generate at least two operation commands and then generate a target request message based on these operation commands. Thus, the generated target request message contains all the information needed to perform the aforementioned operations, thereby improving the feasibility of this solution. Furthermore, requiring only one trigger operation to generate at least two operation commands effectively reduces the number of operations required by the user, improves the efficiency of solution implementation, and enhances the user experience.

[0020] Optionally, the target request message includes a first array and a second array; the elements in the first array are used to indicate the operation instruction identifier, execution order identifier, and attribute information identifier contained in each operation instruction; wherein, the execution order identifier is used to indicate the execution order of the operation corresponding to each operation instruction among all the operations corresponding to all operation instructions; the elements in the second array are used to indicate that each attribute information identifier in the first array corresponds to at least one attribute information.

[0021] Thirdly, this application provides a data interaction device applied to a server in a financial system. The device includes: a first receiving module for receiving a target request message from a terminal; wherein the target request message contains at least two operation instructions and an execution order of operations corresponding to each operation instruction; a first processing module for parsing the target request message and, based on the execution order, sequentially executing the operations corresponding to the operation instructions; and a first sending module for sending operation completion information to the terminal after completing the operation corresponding to the last operation instruction in the target request message, so that the terminal determines the operation result corresponding to the target request message based on the operation completion information.

[0022] Optionally, the target request message includes a first array and a second array; the elements in the first array are used to indicate the operation instruction identifier, execution order identifier, and attribute information identifier contained in each operation instruction; wherein, the execution order identifier is used to indicate the execution order of the operation corresponding to each operation instruction among all the operations corresponding to all operation instructions; the elements in the second array are used to indicate that each attribute information identifier in the first array corresponds to at least one attribute information; wherein, the attribute information is used to indicate the information required to perform the operation.

[0023] Optionally, when the first processing module is used to execute the operations corresponding to the operation instructions sequentially based on the execution order, it is specifically used to: execute the operations corresponding to the operation instructions sequentially based on the execution order; when any operation corresponding to the operation instruction fails to execute, stop responding to subsequent operation instructions and send an abnormal alarm message to the terminal.

[0024] Optionally, the at least two operation instructions include an authentication instruction, which is the first execution object in the execution order. Before executing any other operations among the at least two operation instructions besides the authentication instruction, the first processing module is further configured to: when it is determined that the operation corresponding to the authentication instruction has been completed and the execution result of the operation corresponding to the authentication instruction has been obtained, determine the execution result of the operation corresponding to the authentication instruction; if it is determined that the execution result indicates that the identity information is valid, then continue executing the other operations; if it is determined that the execution result indicates that the identity information is invalid, then stop executing the other operations and send the abnormal alarm information to the terminal.

[0025] Fourthly, this application provides a data interaction device applied to a terminal in a financial system. The device includes: a second processing module for generating a target request message; wherein the target request message contains at least two operation instructions and an execution order of operations corresponding to each operation instruction; a second sending module for sending the target request message to a server, so that the server parses the target request message and, based on the execution order, sequentially executes the operations corresponding to the operation instructions; and, after completing the operation corresponding to the last operation instruction in the target request message, sends operation completion information to the terminal; and a second receiving module for receiving the operation completion information from the server and determining the operation result corresponding to the target request message based on the operation completion information.

[0026] Optionally, when the second processing module generates the target request message, it is specifically configured to: generate the at least two operation instructions in response to a target scenario triggering instruction, and obtain at least one attribute information corresponding to each operation instruction; wherein the attribute information is used to indicate the information required to execute the operation corresponding to each operation instruction; determine the execution order of the server executing the operations corresponding to the at least two operation instructions based on the configuration information of the target scenario; and generate the target request message based on the at least two operation instructions, the attribute information corresponding to each operation instruction, and the execution order.

[0027] Optionally, the target request message includes a first array and a second array; the elements in the first array are used to indicate the operation instruction identifier, execution order identifier, and attribute information identifier contained in each operation instruction; wherein, the execution order identifier is used to indicate the execution order of the operation corresponding to each operation instruction among all the operations corresponding to all operation instructions; the elements in the second array are used to indicate that each attribute information identifier in the first array corresponds to at least one attribute information.

[0028] Fifthly, an electronic device is provided, comprising: 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, and the at least one processor, by executing the instructions stored in the memory, causes the at least one processor to perform the method described in the first aspect or any optional embodiment of the first aspect.

[0029] In a sixth aspect, a computer-readable storage medium is provided for storing instructions that, when executed, cause a method as described in the first aspect or any alternative embodiment of the first aspect to be implemented.

[0030] In a seventh aspect, a computer program product comprising instructions is provided, the computer program product storing instructions that, when executed on a computer, cause the computer to perform the method as described in the first aspect or any optional embodiment of the first aspect.

[0031] The technical effects or advantages of one or more technical solutions provided in the third, fourth, fifth, sixth and seventh aspects of this application can all be explained by the corresponding technical effects or advantages of one or more technical solutions provided in the first or second aspect. Attached Figure Description

[0032] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying 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.

[0033] Figure 1 This is a schematic diagram illustrating possible application scenarios provided for embodiments of this application;

[0034] Figure 2 A flowchart illustrating a data interaction method provided in an embodiment of this application;

[0035] Figure 3 A flowchart illustrating a method for generating a target request message provided in this application embodiment;

[0036] Figure 4 A schematic diagram illustrating the format of a target request message provided in an embodiment of this application;

[0037] Figure 5 A flowchart illustrating a data interaction method provided in an embodiment of this application;

[0038] Figure 6 A flowchart illustrating a data interaction method provided in an embodiment of this application;

[0039] Figure 7 This is a schematic diagram of the structure of a data interaction device provided in an embodiment of this application;

[0040] Figure 8 This is a schematic diagram of the structure of a data interaction device provided in an embodiment of this application;

[0041] Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0042] The technical solution of this application will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the embodiments and specific features in the embodiments are detailed descriptions of the technical solution of this application, rather than limitations thereof. In the absence of conflict, the embodiments and technical features in the embodiments can be combined with each other.

[0043] It should be understood that in the description of the embodiments of this application, terms such as "first" and "second" are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance, nor should they be construed as indicating or implying order. In the description of the embodiments of this application, "multiple" refers to two or more.

[0044] The term "and / or" in the embodiments of this application is merely a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0045] In this embodiment of the application, the collection, dissemination, and use of data all comply with the requirements of relevant national laws and regulations.

[0046] A mobile internet product typically consists of a front-end system and a back-end system. The front-end system (hereinafter referred to as the front-end) is user-facing, deployed on the customer's mobile device, and usually belongs to a third-party platform. Its security is affected by the client (such as the application shell). The back-end system (hereinafter referred to as the back-end) generally includes product systems, information systems, deposit systems, etc., and is deployed in a private cloud of a service provider with a higher security level. In typical front-end and back-end interaction scenarios, such as mobile payment, the data sent from the front-end to the back-end contains a lot of customer information. To ensure the security of user data, the front-end separates identity verification and payment operations into two parts. The front-end first agrees with the back-end on a unique identifier for the user. After the back-end verifies the user's identity, it continues with subsequent operations.

[0047] However, the front end is usually handled by a third-party platform, and its security is not stable. It is easy for the customer identity verification step to be bypassed or intercepted in the front end security verification scenario. This can lead to the situation where the tampered customer data is sent to the back end for actual payment operation, thus failing to guarantee the security of customer transaction data.

[0048] In view of this, embodiments of this application provide a data interaction method to improve the security of data interaction between front-end and back-end systems.

[0049] The following is a brief introduction to the application scenarios to which the technical solutions of the embodiments of this application are applicable. It should be noted that the application scenarios described below are only for illustrating the embodiments of this application and are not intended to limit the scope. In specific implementation, the technical solutions provided by the embodiments of this application can be flexibly applied according to actual needs.

[0050] See Figure 1 This is a schematic diagram of a possible application scenario provided by an embodiment of this application. In this scenario, a terminal device 101 and a server 102 may be included.

[0051] Terminal device 101 can be a mobile phone, tablet computer (PAD), personal computer (PC), wearable device, vehicle terminal, etc., or it can be a camera, video camera, dashcam, etc. Server 102 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery network (CDN), and big data and artificial intelligence platforms.

[0052] Terminal device 101 and server 102 can communicate directly or indirectly through one or more communication networks 103. The communication network 103 can be a wired network or a wireless network. For example, the wireless network can be a mobile cellular network or a Wireless-Fidelity (WIFI) network. Of course, it can also be other possible networks, and this embodiment of the invention does not limit them.

[0053] It should be noted that, Figure 1 The examples shown are merely illustrative; in reality, the number of terminal devices and servers, as well as the communication methods, are not limited and are not specifically restricted in the embodiments of this application.

[0054] The following describes the data interaction method provided by the exemplary embodiments of this application in conjunction with the application scenarios described above and with reference to the accompanying drawings. It should be noted that the above application scenarios are only shown to facilitate understanding of the spirit and principles of this application, and the embodiments of this application are not limited in any way in this respect.

[0055] The data interaction method provided in this application is applied to servers and terminals in a financial system, realizing data interaction through the operation and interaction between the server and the terminal. To facilitate understanding of this solution, the method provided in this application will be described below from three aspects: terminal, server, and interaction between terminals and servers.

[0056] See Figure 2 This is a flowchart illustrating a data interaction method provided in an embodiment of this application. Figure 2 As shown, the execution entity of this method is a terminal in the financial system, and the specific implementation steps are as follows:

[0057] Step S201: Generate a target request message, wherein the target request message contains at least two operation instructions and the execution order of the operations corresponding to each operation instruction.

[0058] First, it should be noted that the terminal that generates the target request message is the terminal device where the user-facing front-end is located. In practical applications, the front-end can be a web page, or a certain interface or function in an application, as long as it can communicate with the back-end and complete the target function. This application does not limit its specific form.

[0059] Optionally, when the terminal generates the target request message, it can be achieved in several different ways.

[0060] Method 1: By receiving various operation commands input by the user on the terminal, confirming that the commands can be combined, and then generating a target request message for the combined operation.

[0061] Specifically, when the terminal receives operation instructions input by the user, it can collect all operation instructions input by the user to the terminal and the front end within the target time period, and based on these operation instructions, select several operation instructions that meet preset conditions and combine them to generate a corresponding target request message for these combined operation instructions.

[0062] Method 2: By pre-setting different scenarios and receiving scenario triggering instructions from users, several operation instructions associated with the scenario can be generated, and corresponding target request messages can be generated based on these operation instructions.

[0063] Specifically, the terminal can perform the following operations to achieve the above method.

[0064] See Figure 3 This is a flowchart of a method for generating a target request message provided in an embodiment of this application.

[0065] like Figure 3 As shown, the specific implementation steps of this method are as follows:

[0066] Step S301: In response to the target scene trigger command, generate at least two operation commands and obtain at least one attribute information corresponding to each operation command; wherein, the attribute information is used to indicate the information required for the operation corresponding to each operation command.

[0067] In this step, the terminal needs to respond to the trigger command of the target scenario to complete other subsequent operations. The specific target scenario and how to obtain the trigger command require further explanation.

[0068] First, for the various functions provided by the front-end, different scenarios can be pre-configured, such as payment scenarios, query scenarios, consultation scenarios, etc. The configuration information for these different scenarios includes the corresponding operation instructions to be generated for each scenario, as well as the order in which these operation instructions are executed on the server. Thus, when a user completes a scenario trigger command on the terminal, the terminal can generate several corresponding operation instructions based on the trigger command and the scenario's configuration information, and assign them different execution orders.

[0069] Then, after the user completes the triggering of the target scene, the terminal needs to obtain at least one attribute information corresponding to each generated operation instruction.

[0070] When the terminal obtains this attribute information, it can either display a corresponding operation interface to the user, allowing the user to input the corresponding attribute information based on the operation interface, or it can obtain at least one attribute information required for the operation command based on the information stored locally.

[0071] For example, suppose a user is preparing to transfer funds during a mobile payment process. At this time, the user can click on the trigger command for the target scenario (transfer) on the operation page displayed on the terminal. Upon receiving such a trigger command, the terminal immediately responds to the target scenario trigger command and generates at least one operation command based on the configuration information of the target scenario. In this payment scenario, the generated at least one operation command can be an authentication command and a transfer command.

[0072] For authentication and transfer instructions, subsequent operations require obtaining user identity information, transfer recipient information, and transfer amount information. Therefore, for authentication instructions, the corresponding attribute information is account information and password information; for transfer instructions, the corresponding attribute information is transfer account information and transfer amount information.

[0073] In order to obtain the aforementioned attribute information, the terminal can display input options to the user through the operation page, allowing the user to enter their own account, password, transfer amount, and other information, thereby enabling the terminal to obtain the attribute information required to execute various instructions.

[0074] Step S302: Based on the configuration information of the target scenario, determine the execution order when the server executes at least two operation instructions.

[0075] After the terminal generates at least one operation instruction associated with the target scene and obtains the corresponding attribute information, the terminal also needs to configure the execution order of these operation instructions.

[0076] Specifically, the configuration information for the target scenario includes both the at least two operation instructions that need to be generated and the execution order of these instructions when executed by the server. Therefore, when the terminal generates the target request message, it needs to determine the execution order of each operation instruction based on the configuration information of the target scenario.

[0077] Using the payment scenario mentioned above as an example, after generating the authentication command and payment command, the terminal also needs to determine, based on the configuration information, whether the server needs to execute the authentication command first, and only after the authentication command has been executed can the payment command be executed.

[0078] Step S303: Generate a target request message based on at least two operation instructions and the attribute information and execution order corresponding to each operation instruction.

[0079] After generating the operation command and obtaining the corresponding attribute information and execution order, the terminal can generate the corresponding target request message based on this information.

[0080] Optionally, the generated target request message can be in several different formats.

[0081] For example, since each operation instruction is similar to a regular operation instruction, each different operation instruction itself corresponds to various sub-request messages. Thus, when generating the target request message, one possible method is to simply combine the sub-request messages corresponding to each operation instruction and send them directly to the server as the target request message.

[0082] For example, when generating a target request message, a dual array data structure can be used to deconstruct and reassemble the information of different operation instructions to obtain a target request message containing all the necessary information.

[0083] Specifically, the target request message includes a first array and a second array. The elements in the first array indicate the operation instruction identifier, execution order identifier, and attribute information identifier contained in each operation instruction. The execution order identifier indicates the execution order of the operation corresponding to each operation instruction among all the operations corresponding to all operation instructions.

[0084] Since the operation instruction identifier and execution order identifier in the elements of the first array can be directly recorded through the identifier, the information corresponding to the attribute information cannot be displayed through the identifier alone.

[0085] Therefore, for a target request message containing a second array, its purpose is to record the attribute information corresponding to the attribute information identifier. In other words, the elements in the second array are used to indicate at least one attribute information corresponding to each attribute information identifier in the first array.

[0086] For example, taking the payment scenario described above, when the terminal generates a target request message corresponding to all operation instructions, each operation instruction can be treated as an object in the first array, recording its operation instruction identifier, execution order identifier, and attribute information identifier. The operation instruction identifier can be implemented using operation instruction encoding, which uniquely identifies the operation during the interaction between the terminal and the server. The execution order identifier can be implemented using numbers or characters, so that after receiving the target request message, the server can determine the response order of each operation instruction based on the execution order identifier in the target request message.

[0087] Since the attribute information corresponding to each operation instruction cannot be simply recorded using a single identifier, the terminal can record at least one attribute information corresponding to each operation instruction through a second array in the target request message. For example, a key-value pair structure can be introduced into the second array, with each key-value pair recording the corresponding attribute information.

[0088] See Figure 4 This is a schematic diagram illustrating the format of a target request message provided in an embodiment of this application. Figure 4 As shown, the first array contains three elements that record the operation instruction identifier, execution order identifier, and attribute information identifier corresponding to the operation instruction, respectively. The elements in the second array corresponding to the attribute information identifier can record at least one attribute information corresponding to the operation instruction in the form of key-value pairs.

[0089] Taking the identity verification instruction in the aforementioned payment scenario as an example, the attribute information corresponding to this instruction needs to record the user's account and password to verify identity. Therefore, in the target request message, the three elements in the first array will respectively record the operation instruction identifier (such as a numeric code identifier like 212), the execution order identifier (such as a sequence identifier like 01), and the attribute information identifier of the identity verification instruction; among them, the attribute information identifier is used to indicate the recording address of the attribute information of the identity verification instruction in the second array. Correspondingly, the second array can record the two attribute information corresponding to the identity verification instruction through key-value pairs within the array. For example, the key field records the attribute name, and the value field records the value of the attribute information. In the identity information, this corresponds to recording the identity account (0000222) and password (000000) through two key-value pairs.

[0090] After generating the target request message using the above method, the terminal can send the generated target request message to the server. The specific implementation method for this step is as follows:

[0091] Step S202: Send a target request message to the server so that the server can parse the target request message and execute the operations corresponding to the operation instructions in sequence according to the execution order. When the server completes the operation corresponding to the last operation instruction in the target request message, it sends operation completion information to the terminal.

[0092] After the terminal sends a target request message to the server, it can wait for the server to complete all the operations corresponding to the operation instructions in the target request message, without having to interact with the server for important data. This effectively reduces the risk of data leakage or tampering during the data transfer process.

[0093] Step S203: Receive operation completion information from the server, and determine the operation result corresponding to the target request message based on the operation completion information.

[0094] After receiving the operation completion information from the server, the terminal can determine that all operation instructions in the target request message have been successfully completed, and based on the received operation completion information, it can display the operation results corresponding to the target scenario trigger instructions to the user on the terminal's operation page.

[0095] In this solution, the terminal generates a target request message by combining request information from several operations and sends it to the server. After the server completes all operations, the terminal receives operation completion information from the server and determines the operation result of the target request message based on this information. This minimizes the number of data transfers between the terminal and the server, effectively reducing the risk of data leakage during data interaction and improving the security of this solution.

[0096] The above describes the specific implementation of the data interaction method provided in this application embodiment applied to the terminal side. Correspondingly, the following will describe the specific implementation of the data interaction method provided in this application embodiment applied to the server side.

[0097] See Figure 5 This is a flowchart illustrating a data interaction method provided in an embodiment of this application. Figure 5 As shown, this method is applied to a server in a financial system, and the specific implementation steps are as follows:

[0098] S501: Receive a target request message from the terminal; wherein the target request message contains at least two operation instructions and the execution order of the operations corresponding to each operation instruction.

[0099] After the terminal generates and sends a target request message based on the user's trigger, the server can receive the target request message accordingly.

[0100] The specific format and content of the target request message can be found in the description of the target request message in step S303 above, and will not be repeated here.

[0101] Optionally, the execution order of operations contained in the target request message can be represented in several ways. Besides recording the execution order identifier for each operation instruction separately, as mentioned above, it can also be achieved by recording all operation instructions as a whole. For example, a separate field recording the overall execution order can be added to the target request message. In this way, the server can respond to the operation instructions in the target request message sequentially based on this overall field.

[0102] Step S502: Parse the target request message and, based on the execution order in the target request message, execute the operations corresponding to each operation instruction in the target request message in sequence.

[0103] After parsing and obtaining the various operation instructions in the target request message and their corresponding execution order, the server can execute the operations corresponding to each operation instruction in the target request message in sequence based on this information.

[0104] Optionally, during the sequential execution of each operation, the server also needs to check the result of the previous operation each time a subsequent operation is performed.

[0105] Specifically, during the process of the server executing the operations corresponding to the operation instructions sequentially based on the execution order obtained from the target request message, the server also needs to perform the following operations each time it executes an operation corresponding to an operation instruction, in order to determine whether to continue executing subsequent operations.

[0106] First, the server can execute the operations corresponding to the current operation instructions based on the execution order. Examples include authentication, user matching, information retrieval, and fund transfer operations.

[0107] Then, after completing the operation, the server needs to evaluate the result to determine whether the expected outcome was achieved. For example, does the identity verification operation confirm that the identity is legitimate? Does the user matching operation confirm that the user is a stored user? Or, does the information query operation retrieve the target information?

[0108] The server will only continue to execute subsequent operations once it has determined that the result of the current operation is the expected result.

[0109] Otherwise, if the server determines that the obtained operation result is not the one corresponding to the operation, it can mark the operation corresponding to the operation instruction as failed, thereby stopping the response to subsequent operation instructions and sending an exception alarm message to the terminal to indicate to the front end that there is an exception in this operation and suggest reviewing the operation problem or repeating the operation.

[0110] In this way, during the server's response to the target request message, if any operation command fails, the server can stop responding to all subsequent operation commands and send an exception alarm message to the terminal. This ensures that the server executes all operations in the correct order, and determines whether to execute subsequent operations by checking if the previous operation failed, preventing any operation from being tampered with or skipped, thus affecting the overall security of data interaction.

[0111] Step S503: After completing the operation corresponding to the last operation instruction in the target request message, send operation completion information to the terminal so that the terminal can determine the operation result corresponding to the target request message based on the operation completion information.

[0112] Once the server confirms that all operations have been executed successfully—in other words, once the server has completed the operation corresponding to the last operation instruction in the target request message—the server can send operation completion information to the terminal, enabling the terminal to determine the operation result corresponding to the target request message based on the received operation completion information.

[0113] In this way, the server has completed all response operations for the target request message.

[0114] In this solution, the server receives all operation instructions and corresponding information at once through the target request message, reducing the number of interactions between the terminal and the server, lowering the risk of data leakage during data flow, and improving the security of data interaction. Simultaneously, the financial system's server controls the data flow between the terminal and the server internally, leveraging the inherent security of the financial system server itself, reducing data transmission over the internet, and avoiding the problem of excessive data exposure leading to interception or bypassing.

[0115] Optionally, among the at least two operation instructions included in the aforementioned target request message, there is an authentication instruction, which is the first to be executed in the execution order of the target request message.

[0116] The operation corresponding to the authentication command is the password verification operation, such as verifying whether the user's identity is legitimate, or verifying whether the user's identity is a user recorded by this system, or whether the account and password information provided by the user match, etc.

[0117] Therefore, when the server responds to the target request message containing authentication instructions, before executing any of the other operations besides the authentication instructions in at least two of the operation instructions in the target request message, the server also needs to perform the following operations:

[0118] First, the server needs to determine whether the operation corresponding to the authentication command has been completed. If the server determines that the corresponding operation has not been completed, it cannot perform any subsequent operations but will continue to wait until it confirms that the operation corresponding to the authentication command has been completed. Optionally, the server can also set a timer specifically for waiting for this authentication command. When the timer expires and it has not yet determined whether the operation corresponding to the authentication command has been completed, the server can consider the operation corresponding to the authentication command to have failed and send an exception alarm message to the terminal.

[0119] If the server determines that the operation corresponding to the authentication command has been completed, the server also needs to obtain the execution result of the operation corresponding to the authentication command and make a judgment on it.

[0120] Then, only when the server determines that the identity information is valid can the server continue to execute other operations in the target request message.

[0121] However, when the server determines that the identity information is invalid, it needs to stop executing other operations contained in the target request message and send an exception alarm message to the terminal.

[0122] In this approach, when an authentication command is present, the server can only perform subsequent operations after confirming that the authentication operation has been performed and that the authentication is valid. This reduces the risk of the authentication operation being skipped or tampered with, and further improves the security of this solution.

[0123] The specific implementation steps of a data interaction method provided by the embodiments of this application have been described above from the perspectives of the terminal side and the server side, respectively. In order to facilitate the overall understanding of the implementation ideas and processes of this solution, the following will introduce a data interaction method provided by the embodiments of this application through the interaction between the terminal and the server and the combination of the above-mentioned multiple implementation methods.

[0124] See Figure 6 This is a flowchart illustrating a data interaction method provided in an embodiment of this application. Figure 6 As shown, this method uses the terminal and server as the execution entities, and the specific implementation steps are as follows:

[0125] Step S601: The terminal responds to the target scene trigger command and generates at least two operation commands.

[0126] Step S602: The terminal obtains at least one attribute information corresponding to each of the above at least two operation instructions, and determines the execution order when the server executes the operations corresponding to the above at least two operation instructions based on the configuration information of the target scenario.

[0127] Step S603: The terminal generates a target request message based on at least two operation instructions and the attribute information and execution order corresponding to each operation instruction.

[0128] The target request message generated by the terminal contains at least two operation instructions, as well as the execution order of the operations corresponding to each operation instruction. Furthermore, the target request message also includes at least one attribute information corresponding to each operation instruction. This attribute information indicates the information required when the corresponding operation is executed. For example, when the operation corresponding to the authentication instruction is executed, it requires the user's account information and password information, and the at least one attribute information corresponding to this authentication instruction is the aforementioned account information and password information.

[0129] Thus, when generating a target request message, the terminal can generate a target request message containing both a first array and a second array based on the dual array structure. For example, when the target request message only contains authentication instructions and transfer operation instructions, the target request message containing the first array and the second array can record all information using the following structure: First, for authentication instructions, the three elements in the first array can be used to record the instruction operation identifier, execution sequence identifier, and attribute information identifier corresponding to the authentication instruction, respectively; similarly, for transfer operation instructions, the other three elements in the first array can also be used to record the instruction operation identifier, execution sequence identifier, and attribute information identifier corresponding to the transfer operation instruction, respectively.

[0130] Meanwhile, the second array in the target request message can record all attribute information corresponding to each operation instruction in a key-value pair manner, and associate it with the attribute information identifier element in the first array, thereby clarifying all information corresponding to each operation instruction.

[0131] Step S604: The terminal sends the target request message generated above to the server; correspondingly, the server accepts the target request message from the terminal.

[0132] Step S605: The server parses the received target request message and obtains the execution order of the operations corresponding to each operation instruction.

[0133] Step S606: Perform the corresponding operations in the order described above.

[0134] Step S607: After each operation is completed, the server determines whether the operation was successful; if the operation fails, proceed to step S608; if the operation is successful, proceed to step S609.

[0135] Step S608: The server sends an abnormal alarm message to the terminal; correspondingly, the terminal receives the abnormal alarm message from the server.

[0136] Step S609: The server determines whether the operation being performed is the operation corresponding to the last operation instruction indicated in the execution sequence; if yes, then proceed to step S610; if no, then continue to step S606.

[0137] Step S610: The server sends an operation completion message to the terminal; correspondingly, the terminal receives the operation completion message from the server.

[0138] Step S611: The terminal determines the operation result corresponding to the target request message based on the operation completion information.

[0139] Thus, through the interaction between the terminal and the server, a data interaction method provided in this application embodiment can be realized.

[0140] Based on the same inventive concept, embodiments of this application also provide a data interaction device.

[0141] See Figure 7 This is a schematic diagram of the structure of a data interaction device provided in an embodiment of this application. The device may be the server mentioned above or a chip or integrated circuit in the device. The device includes modules / units / technical means for executing the method executed by the server in the above method embodiment.

[0142] For example, the device 700 includes:

[0143] The first receiving module 701 is used to receive a target request message from a terminal; wherein the target request message contains at least two operation instructions and the execution order of the operations corresponding to each operation instruction;

[0144] The first processing module 702 is used to parse the target request message and, based on the execution order, execute the operations corresponding to the operation instructions in sequence;

[0145] The first sending module 703 is used to send operation completion information to the terminal after completing the operation corresponding to the last operation instruction in the target request message, so that the terminal can determine the operation result corresponding to the target request message based on the operation completion information.

[0146] As one example, Figure 7The device described can be used to perform Figure 5 The method described in the illustrated embodiment is therefore relevant to the functions that each functional module of the device can achieve. Figure 5 The description of the embodiments shown will not be repeated here.

[0147] Based on the same inventive concept, embodiments of this application also provide a data interaction device.

[0148] See Figure 8 This is a schematic diagram of the structure of a data interaction device provided in an embodiment of this application. The device may be the aforementioned terminal device or a chip or integrated circuit in the device. The device includes modules / units / technical means for executing the method executed by the terminal device in the above method embodiment.

[0149] For example, the device 800 includes:

[0150] The second processing module 801 is used to generate a target request message; wherein the target request message contains at least two operation instructions and the execution order of the operations corresponding to each operation instruction;

[0151] The second sending module 802 is used to send the target request message to the server so that the server parses the target request message and executes the operations corresponding to the operation instructions in sequence according to the execution order. After completing the operation corresponding to the last operation instruction in the target request message, the server sends operation completion information to the terminal.

[0152] The second receiving module 803 is used to receive the operation completion information from the server and determine the operation result corresponding to the target request message based on the operation completion information.

[0153] As one example, Figure 8 The device described can be used to perform Figure 2 The method described in the illustrated embodiment is therefore relevant to the functions that each functional module of the device can achieve. Figure 2 The description of the embodiments shown will not be repeated here.

[0154] It should be noted that although several modules or sub-modules of the device have been mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to embodiments of the present invention, the features and functions of two or more units described above can be embodied in a single module. Conversely, the features and functions of a module described above can be further divided and embodied by multiple modules.

[0155] As one possible product form of the aforementioned device, see [link to product description]. Figure 9This application also provides an electronic device 900, comprising:

[0156] At least one processor 901; and a communication interface 903 communicatively connected to the at least one processor 901; the at least one processor 901 causes the electronic device 900 to perform the method steps performed by any device in the above method embodiments through the communication interface 903 by executing instructions stored in the memory 902.

[0157] Optionally, the memory 902 is located outside the electronic device 900.

[0158] Optionally, the electronic device 900 includes the memory 902, which is connected to the at least one processor 901, and stores instructions executable by the at least one processor 901. (Appendix) Figure 9 The dashed line indicates that memory 902 is optional for electronic device 900.

[0159] The processor 901 and the memory 902 can be coupled through an interface circuit or integrated together; no restriction is imposed here.

[0160] This application embodiment does not limit the specific connection medium between the processor 901, memory 902, and communication interface 903. This application embodiment... Figure 9 The processor 901, memory 902, and communication interface 903 are connected via a bus 904. Figure 9 The connections between other components are shown in bold and are for illustrative purposes only, not as limiting information. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 9 The text uses only a single thick line to represent a bus, but this does not imply that there is only one bus or one type of bus. It should be understood that the processor mentioned in the embodiments of this application can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory.

[0161] For example, the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0162] It should be understood that the memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate Synchronous DRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct RAM (DR RAM).

[0163] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0164] It should be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

[0165] As another possible product form, this application embodiment also provides a computer-readable storage medium for storing instructions that, when executed, cause a computer to perform the method steps performed by any of the devices in the above method examples.

[0166] As another possible product form, this application embodiment also provides a computer program product containing instructions, wherein the computer program product stores instructions that, when run on a computer, cause the computer to execute the method steps performed by any device in the above method embodiments.

[0167] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application 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.

[0168] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should 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. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

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

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

[0171] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A data interaction method, characterized in that, A server used in a financial system, the server being connected to at least one terminal device, each terminal device running a front-end system communicatively connected to the server, the method comprising: The system receives a target request message from a terminal; wherein the terminal is one of the at least one terminal device, and the target request message is generated by the terminal in response to a target scenario triggering instruction; the target request message contains at least two operation instructions and the execution order of the operations corresponding to each operation instruction; the at least two operation instructions are used to jointly participate in the financial data exchange process under the target scenario; each operation instruction corresponds to corresponding attribute information, and the attribute information is used to indicate the information required to perform the operation; The target request message is parsed, and the operations corresponding to the at least two operation instructions are executed sequentially based on the execution order; wherein, during the sequential execution of the at least two operation instructions, after each operation instruction is executed, if it is determined that the operation result obtained in this execution meets the expectations, execution continues; After completing the operation corresponding to the last operation instruction in the target request message, operation completion information is sent to the terminal so that the terminal can determine the operation result corresponding to the target request message based on the operation completion information and complete the response operation for the target scenario.

2. The method as described in claim 1, characterized in that, The target request message includes a first array and a second array; The elements in the first array are used to indicate the operation instruction identifier, execution order identifier, and attribute information identifier contained in each operation instruction; wherein, the execution order identifier is used to indicate the execution order of the operation corresponding to each operation instruction among all the operations corresponding to all operation instructions; The elements in the second array are used to indicate that each attribute information identifier in the first array corresponds to at least one attribute information; wherein, the attribute information is used to indicate the information required to perform the operation.

3. The method as described in claim 1, characterized in that, The step of sequentially executing the operations corresponding to the operation instructions based on the execution order includes: Based on the execution order, the operations corresponding to the operation instructions are executed sequentially; If any operation corresponding to the operation instruction fails to be executed, the system stops responding to subsequent operation instructions and sends an abnormal alarm message to the terminal.

4. The method according to any one of claims 1-3, characterized in that, The at least two operation instructions include an authentication instruction, and the authentication instruction is the first execution target in the execution order; Before executing any of the at least two operation instructions other than the authentication instruction, the method further includes: When it is determined that the operation corresponding to the authentication instruction has been completed and the execution result of the operation corresponding to the authentication instruction has been obtained, the execution result of the operation corresponding to the authentication instruction is determined. If the execution result indicates that the identity information is legitimate, then continue with the other operations. If the execution result indicates that the identity information is illegal, then the execution of the other operations is stopped, and the abnormal alarm information is sent to the terminal.

5. A data interaction method, characterized in that, A terminal used in a financial system, the terminal being connected to a server in the financial system, the server being connected to at least one terminal device, the terminal being one of the at least one terminal device, each of the terminal devices running a front-end system communicating with the server, the method comprising: A target request message is generated in response to a target scenario trigger instruction; wherein, the target request message contains at least two operation instructions and the execution order of the operations corresponding to each operation instruction; the at least two operation instructions are used to jointly participate in the financial data exchange process under the target scenario; each operation instruction has corresponding attribute information, and the attribute information is used to indicate the information required to perform the operation; The target request message is sent to the server so that the server parses the target request message and executes the operations corresponding to the at least two operation instructions in sequence based on the execution order. In the process of executing the at least two operation instructions in sequence, after each operation instruction is executed, if it is determined that the operation result obtained in this execution meets the expectations, the execution continues. After the operation corresponding to the last operation instruction in the target request message is completed, operation completion information is sent to the terminal. The system receives the operation completion information from the server, determines the operation result corresponding to the target request message based on the operation completion information, and completes the response operation for the target scenario.

6. The method as described in claim 5, characterized in that, The generation of the target request message includes: In response to a target scene trigger command, at least two operation commands are generated, and at least one attribute information corresponding to each operation command is obtained; wherein, the attribute information is used to indicate the information required to execute the operation corresponding to each operation command; Based on the configuration information of the target scenario, determine the execution order when the server executes the operations corresponding to the at least two operation instructions; The target request message is generated based on the at least two operation instructions, the attribute information corresponding to each operation instruction, and the execution order.

7. The method as described in claim 5 or 6, characterized in that, The target request message includes a first array and a second array; The elements in the first array are used to indicate the operation instruction identifier, execution order identifier, and attribute information identifier contained in each operation instruction; wherein, the execution order identifier is used to indicate the execution order of the operation corresponding to each operation instruction among all the operations corresponding to all operation instructions; The elements in the second array are used to indicate that each attribute information identifier in the first array corresponds to at least one attribute information.

8. A data interaction device, characterized in that, A server used in a financial system, the server being connected to at least one terminal device, each terminal device running a front-end system communicating with the server, the apparatus comprising: A first receiving module is configured to receive a target request message from a terminal; wherein the terminal is one of the at least one terminal device, and the target request message is generated by the terminal in response to a target scenario triggering instruction; the target request message contains at least two operation instructions and the execution order of operations corresponding to each operation instruction; the at least two operation instructions are used to jointly participate in the financial data exchange process under the target scenario; each operation instruction corresponds to corresponding attribute information, and the attribute information is used to indicate the information required to perform the operation; The first processing module is used to parse the target request message and, based on the execution order, sequentially execute the operations corresponding to the at least two operation instructions; wherein, during the sequential execution of the at least two operation instructions, after each operation instruction is executed, if it is determined that the operation result obtained in this execution meets the expectations, execution continues; The first sending module is used to send operation completion information to the terminal after completing the operation corresponding to the last operation instruction in the target request message, so that the terminal can determine the operation result corresponding to the target request message based on the operation completion information and complete the response operation for the target scenario.

9. The apparatus as claimed in claim 8, characterized in that, The target request message includes a first array and a second array; The elements in the first array are used to indicate the operation instruction identifier, execution order identifier, and attribute information identifier contained in each operation instruction; wherein, the execution order identifier is used to indicate the execution order of the operation corresponding to each operation instruction among all the operations corresponding to all operation instructions; The elements in the second array are used to indicate that each attribute information identifier in the first array corresponds to at least one attribute information; wherein, the attribute information is used to indicate the information required to perform the operation.

10. The apparatus as claimed in claim 8, characterized in that, When the first processing module is used to execute the operations corresponding to the operation instructions sequentially based on the execution order, it is specifically used for: Based on the execution order, the operations corresponding to the operation instructions are executed sequentially; If any operation corresponding to the operation instruction fails to be executed, the system stops responding to subsequent operation instructions and sends an abnormal alarm message to the terminal.

11. The apparatus according to any one of claims 8-10, characterized in that, The at least two operation instructions include an authentication instruction, and the authentication instruction is the first execution target in the execution order; Before executing any of the at least two operation instructions other than the authentication instruction, the first processing module is further configured to: When it is determined that the operation corresponding to the authentication instruction has been completed and the execution result of the operation corresponding to the authentication instruction has been obtained, the execution result of the operation corresponding to the authentication instruction is determined. If the execution result indicates that the identity information is legitimate, then continue with the other operations. If the execution result indicates that the identity information is illegal, then the execution of the other operations is stopped, and the abnormal alarm information is sent to the terminal.

12. A data interaction device, characterized in that, A terminal used in a financial system, the terminal being connected to a server in the financial system, the server being connected to at least one terminal device, the terminal being one of the at least one terminal device, each of the terminal devices running a front-end system communicating with the server, the device comprising: The second processing module is used to generate a target request message in response to a target scenario trigger instruction; wherein, the target request message contains at least two operation instructions and the execution order of the operations corresponding to each operation instruction; the at least two operation instructions are used to jointly participate in the financial data exchange process under the target scenario; each operation instruction corresponds to corresponding attribute information, and the attribute information is used to indicate the information required to perform the operation; The second sending module is used to send the target request message to the server so that the server can parse the target request message and, based on the execution order, sequentially execute the operations corresponding to the at least two operation instructions. In the process of sequentially executing the at least two operation instructions, after each operation instruction is executed, if it is determined that the operation result obtained in this execution meets the expectations, the execution continues. After completing the operation corresponding to the last operation instruction in the target request message, the module sends operation completion information to the terminal. The second receiving module is used to receive the operation completion information from the server, determine the operation result corresponding to the target request message based on the operation completion information, and complete the response operation for the target scenario.

13. The apparatus as claimed in claim 12, characterized in that, When the second processing module generates the target request message, it is specifically used for: In response to a target scene trigger command, at least two operation commands are generated, and at least one attribute information corresponding to each operation command is obtained; wherein, the attribute information is used to indicate the information required to execute the operation corresponding to each operation command; Based on the configuration information of the target scenario, determine the execution order when the server executes the operations corresponding to the at least two operation instructions; The target request message is generated based on the at least two operation instructions, the attribute information corresponding to each operation instruction, and the execution order.

14. The apparatus as claimed in claim 12 or 13, characterized in that, The target request message includes a first array and a second array; The elements in the first array are used to indicate the operation instruction identifier, execution order identifier, and attribute information identifier contained in each operation instruction; wherein, the execution order identifier is used to indicate the execution order of the operation corresponding to each operation instruction among all the operations corresponding to all operation instructions; The elements in the second array are used to indicate that each attribute information identifier in the first array corresponds to at least one attribute information.

15. An electronic device, characterized in that, include: 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 executes the instructions stored in the memory to perform the method as described in any one of claims 1-4 or 5-7.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store instructions that, when executed, cause the method as described in any one of claims 1-4 or 5-7 to be implemented.

17. A computer program product containing instructions, characterized in that, The computer program product stores instructions that, when run on a computer, cause the computer to perform the method as described in any one of claims 1-4 or 5-7.

Images