Analog data acquisition method and system

Abstract

The invention provides an analog data acquisition method and system, and the method comprises the steps: enabling a recording switch of a corresponding expectation set when a service end requests to start data recording, and enabling the obtained analog data to be stored in the expectation set through a simulation server; the simulation server side forwards the interface request and the response message transmitted between the service side and the online server side, in the forwarding process, interface calling basic information in the interface request and interface output parameters in the response message are recorded for an interface needing data recording, and the recorded information is stored; and obtaining a plurality of pieces of interface simulation data stored in the expected set. According to the method, a developer only needs to configure the data recording information in the application program interface of the service end and operate in the application program according to the service handling steps, the operability is high, non-professional technicians can implement the method, the labor input cost is reduced, and the service handling efficiency is improved. Complete interface simulation data in a certain business scene can be conveniently and efficiently obtained.

Description

Technical Field

[0001] This application relates to the field of computer technology, and particularly to a method and system for obtaining simulated data. Background Art

[0002] Interface data simulation (Mock API) is a technology that uses simulated data to replace the data returned by real API interfaces. In the development and application of application programs, interface data simulation is widely used in the life cycle of application programs. For example, in the development stage, front-end testing is carried out by using the simulated interface data. After the application program is launched, the simulated interface data can be used to provide APP experience functions for unregistered new users. In the application program optimization stage, the simulated interface data can be used to test and optimize the performance, etc.

[0003] Currently, most of the simulated data used in interface data simulation technology is obtained through the following methods: First, manually review the code logic to determine the interfaces and pages involved in a certain business scenario. Then, clarify the logic of the pages to avoid missing key interfaces and removing unnecessary interfaces to determine the list of interfaces for which simulated data needs to be obtained. Finally, run the development code according to the logic of the pages, and in this process, use a packet capture tool to uniformly capture and save the interface data required for each interface in the interface list. Finally, batch-enter the interface data for each business scenario into the storage device as the interface simulation data for that business scenario.

[0004] This method requires a large amount of labor costs and takes a long time, and the efficiency of obtaining simulated data is not good. Summary of the Invention

[0005] Based on this, it is necessary to provide a method and system for obtaining simulated data for the above technical problems to solve the problem of low efficiency in obtaining simulated data.

[0006] In a first aspect, a method for obtaining simulation data is proposed, which is applied to the business side. The method includes: listening for whether the data recording switch of the application program is turned on. After the data recording switch is turned on, obtaining the data recording information configured by the user on the simulation workbench interface of the application program. The data recording information includes the first service scenario identifier for starting data recording and the first experience account; writing the data recording information into a recording start request and sending the recording start request to the simulation server, so that the simulation server turns on the recording switch of the first expected set. The first expected set is an expected set created by the simulation server in the storage space of the first experience account for the first service scenario identifier. The first expected set is used to store multiple interface simulation data in the first service scenario; obtaining the account logged in by the user in the application program; listening for the operations of the user in the application program and determining the basic information of interface calls required to respond to the user's operations; when constructing any interface request triggered by the user in the application program, adding the account logged in by the user and the basic information of interface calls to the interface request; sending the interface request to the simulation server, so that before the simulation server forwards the interface request to the online server, it determines whether there is an expected set with the recording switch turned on corresponding to the account logged in by the user in the interface request. If so, marking the interface request and recording the basic information of interface calls of the interface request, so that before the simulation server forwards the response message of the online server to the interface request to the business side, extracting the interface output parameters from the response message of the marked interface request and using the interface output parameters as the interface simulation data corresponding to the basic information of interface calls, and storing them in the expected set with the recording switch turned on, so as to store the interface simulation data for the first service scenario in the first expected set when the account logged in by the user is the first experience account; receiving the response message forwarded by the simulation server to respond to the user's operations based on the response message.

[0007] Second aspect, a method for obtaining simulated data is provided, which is applied to a simulation server. The method includes: receiving a recording start request sent by a service end, where the recording start request includes data recording information configured by a user on a simulation workbench interface of an application program, and the data recording information includes a first service scenario identifier for starting data recording and a first experience account; finding a first expected set jointly corresponding to the first service scenario identifier and the first experience account from a stored expected set, where the first expected set is used to store multiple pieces of interface simulation data in the first service scenario; setting the recording switch of the first expected set to the on state; receiving an interface request sent by the service end, where the interface request is triggered by the user in the application program, and the interface request includes the account logged in by the user and interface call basic information; determining whether an expected set with the recording switch in the on state corresponds to the account logged in by the user; if so, marking the interface request and recording the interface call basic information; forwarding the received interface request to an online server so that the online server returns a response message to the interface request; receiving the response message to the interface request and filtering out the response message to the marked interface request from it; copying the interface output parameter from the response message to the marked interface request; storing the interface output parameter as interface simulation data corresponding to the interface call basic information in the expected set with the recording switch in the on state, so as to store interface simulation data for the first service scenario in the first expected set when the account logged in by the user is the first experience account; forwarding all the received response messages to the service end so that the service end responds to the user operation based on the response message.

[0008] In a third aspect, a system for obtaining simulated data is provided. The system includes a business terminal, an online server, and a simulation server. The business terminal is configured to monitor whether the data recording switch of the application program is turned on. After the data recording switch is turned on, it obtains the data recording information configured by the user in the simulated workbench interface of the application program. The data recording information includes the first business scenario identifier for starting data recording and the first experience account. The business terminal is configured to write the data recording information into a recording start request and send the recording start request to the simulation server. The simulation server is configured to, after receiving the recording start request, find the first expected set corresponding to both the first business scenario identifier and the first experience account from the stored expected sets. The expected sets are used to store multiple pieces of interface simulation data for business scenarios. The simulation server is configured to set the recording switch of the first expected set to the on state. The business terminal is configured to obtain the account logged in by the user in the application program. The business terminal is configured to monitor the operations of the user in the application program and determine the basic information for interface calls required to respond to the user operations. When constructing any interface request triggered by the user in the application program, the business terminal is configured to add the account logged in by the user and the basic information for interface calls to the interface request, and send the interface request to the simulation server. The simulation server is configured to receive the interface request and determine whether there is an expected set with the recording switch in the on state corresponding to the account logged in by the user. If so, the simulation server is configured to mark the interface request and record the basic information for interface calls of the interface request. The simulation server is configured to forward the received interface request to the online server. The online server is configured to obtain the interface output parameters according to the basic information for interface calls in the interface request, write the interface output parameters into the response message of the interface request, and return the response message of the interface request to the simulation server. The simulation server is configured to receive the response message of the interface request and filter out the response messages of the marked interface requests from it. The simulation server is configured to copy the interface output parameters from the response messages of the marked interface requests. The simulation server is configured to store the interface output parameters as the interface simulation data corresponding to the basic information for interface calls in the expected set with the recording switch in the on state, so as to store the interface simulation data for the first business scenario in the first expected set when the account logged in by the user is the first experience account. The simulation server is configured to forward all the received response messages to the business terminal. The business terminal is configured to receive the response messages forwarded by the simulation server and respond to the user operations based on the response messages.

[0009] In summary, the present application proposes a method and system for obtaining simulation data. In this system, when the service end of the simulation receives a request from the business end to start data recording, it turns on the recording switch for the corresponding expected set, so as to store the obtained simulation data in this expected set. The simulation service end forwards the interface requests and response messages transmitted between the business end and the online service end. During the forwarding process, for the interfaces that need to record data, it records the basic information of the interface call in the interface request and the output parameters of the interface in the response message, and stores the recorded information, thereby obtaining multiple pieces of interface simulation data stored under the expected set. This method only requires developers to configure data recording information in the application program interface of the business end and operate in the application program according to the business handling steps. It has strong operability and can be implemented by non-professional technical personnel, reducing the labor input cost and enabling convenient and efficient acquisition of complete interface simulation data in a certain business scenario. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following will briefly introduce the drawings required to be used in the description of the embodiments of the present invention. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0011] Figure 1 is a schematic structural diagram of a system for obtaining simulation data according to an exemplary embodiment of the present application; Figure 2 is a flowchart of a method for obtaining simulation data according to another exemplary embodiment of the present application; Figure 3 is a flowchart of a method for obtaining simulation data according to another exemplary embodiment of the present application; Figure 4 is a flowchart of a method for obtaining simulation data according to another exemplary embodiment of the present application; Figure 5 is a flowchart of a method for obtaining simulation data according to another exemplary embodiment of the present application; Figure 6 is a flowchart of a method for obtaining simulation data according to another exemplary embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0012] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. The embodiments described by referring to the accompanying drawings are exemplary and are intended to explain the present application, and should not be construed as a limitation to the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present application.

[0013] The simulation data acquisition system proposed in the present application can be applied to obtain simulation data of the front-end call interface for an online application program. Subsequently, the simulation data of the front-end call interface can be used to provide a function for unregistered users, even for reviewers in enterprise application development, etc., to experience the business process on the APP without registration. For example, users can browse the page processes provided by the application program in different business scenarios and experience the interaction process with the application program.

[0014] Figure 1 is a schematic structural diagram of a simulation data acquisition system shown according to an exemplary embodiment of the present application, as Figure 1 shown, the simulation data acquisition system 1 may include a business end 10, a simulation server end 20, and an online server end 30; The business end 10 may be a terminal device loaded with an application program. The simulation server end 10 and the online server end 30 may be separate servers or a server cluster, and the present application does not make any restrictions.

[0015] Exemplarily, in addition to displaying the business handling interface to the user, the application program can also display the simulation workbench interface to the user. The switching between the business handling interface and the simulation workbench interface can be performed through the menu bar of the application program.

[0016] For example, on a financial credit software, the business handling interface is used to display the handling icons of various businesses. After the user clicks on a certain icon, the function page corresponding to the business will be displayed on this interface. In the simulation workbench interface, experience accounts available for the user to select and business scenarios available for the user to select can be displayed. Developers (i.e., the users involved in the process of obtaining simulation data) can register a new experience account / select a registered experience account, create a new business scenario / select a created business scenario in the simulation workbench interface, and then trigger the simulation data acquisition process of the business scenario at the business end to record the interface simulation data of the business scenario for this experience account. In addition, unregistered users (i.e., the users involved in the business scenario experience process) can also select an experience account from the experience accounts and business scenarios available for selection displayed on the simulation workbench interface to log in and select a business scenario to start the APP experience under this business scenario.

[0017] In the embodiment of the present application, the service end 10 can monitor in real time whether the data recording switch of the application program is turned on. The data recording switch can be set in the simulation workbench interface of the application program. When developers need to obtain interface simulation data in a certain business scenario, they can turn on the data recording switch in the simulation workbench interface.

[0018] After the data recording switch is turned on, the service end 10 will change the page displayed on the simulation workbench interface to the configuration page of data recording information, and developers can configure data recording information on the simulation workbench interface. The service end 10 obtains the data recording information configured by the developers.

[0019] For example, in an actual application scenario, developers can open the application program, enter the simulation workbench interface of the application program, and configure data recording information on the simulation workbench interface, such as the first business scenario identifier and the first experience account selected by the developers when turning on data recording.

[0020] An example is given regarding the developers' configuration of data recording information on the simulation workbench interface: Developers can register a new account on the simulation workbench interface as an experience account; fill in the basic information of the business scenario to create a new business scenario for which simulation data needs to be obtained, and the service end can create a business scenario identifier for this business scenario.

[0021] Alternatively, developers can select an experience account to log in on the simulation workbench interface and select an existing business scenario to carry out simulation data acquisition.

[0022] For the convenience of distinction, in the embodiment of the present application, the business scenario identifier and the experience account configured by the user on the simulation workbench interface and participating in data recording and simulation data acquisition are referred to as the first business scenario identifier and the first experience account.

[0023] After the service end obtains the data recording information configured by the developers, it will create a recording start request, and the recording start request includes the data recording information.

[0024] The service end sends the recording start request to the simulation server.

[0025] After receiving the recording start request, the simulation server can find the first expected set from the stored expected sets according to the data recording information. The first expected set can be the expected set jointly corresponding to the first experience account and the first business scenario identifier.

[0026] One expected set in the simulation server is used to store multiple interface simulation data in a business scenario.

[0027] After the simulation server finds the first expected set, it sets the recording switch of the first expected set to the on state.

[0028] The business side can also listen to the operations of the developer in the application after the developer starts the application.

[0029] After listening to the developer's login, obtain the account he logged in, that is, "the account the user logged in with".

[0030] The business side 10 listens to the operations of the user in the application in real time, such as click, input, drag and other operations. After the business side listens to the user's operation, it will respond to the operation; the operations that need to be responded to include the operations that can only be responded based on the data of the backend interface. For example, after the user clicks on a certain function icon, the business side 10 will display the operation page of the function to the user.

[0031] Therefore, for these operations, the business side 10 will determine the basic data for interface calls required to respond to the user's operation. For example, the basic data for interface calls may include the URL of the interface, the input parameters of the interface, etc.

[0032] When the business side 10 constructs any interface request triggered by the operation of the developer in the application, it adds the account that the developer logged in with and the basic information for interface calls determined in the above steps to the interface request, and sends the constructed interface request to the simulation server 20.

[0033] It should be noted that the above steps of constructing the interface request and sending the interface request executed by the business side 10 can be implemented only when the data recording switch is on. After the data recording switch is turned off, the interface request can be constructed according to the specific business needs and the interface request can be directly sent to the online server 30 for response. Or regardless of whether the data recording switch is on or off, the business side 10 will send the interface request that needs to be sent to the simulation server 20, and the simulation server 20 will forward it.

[0034] After the simulation server 20 receives the interface request sent by the business side, it first uses the account that the user logged in with parsed from the interface request, and then searches for the expected set corresponding to the account that the user logged in with from the stored expected sets, and judges whether the recording switch of the expected set is on.

[0035] If it is on, it can be considered that the simulation server 20 needs to obtain the simulation data of the interface. Therefore, mark the interface request, record the basic information for interface calls in the interface request, and then forward the interface request to the online server 30 for response.

[0036] If the expected set corresponding to the account that the user logged in with cannot be found, or the recording switch of the expected set corresponding to the account that the user logged in with is not on, then directly forward the interface request to the online server 30 for response.

[0037] After receiving the interface request, the online server 30 can parse out the basic information of the interface call from the interface request, and then obtain the interface output parameters according to the basic information of the interface call.

[0038] For example, use the interface URL in the basic information of the interface call to call the interface, provide the input parameters in the basic information of the interface call to the interface, and the interface will output the interface output parameters after running.

[0039] The online server 30 writes the interface output parameters into the response message of the interface request, and then sends the response message of the interface request to the simulation server 20.

[0040] After receiving the response message returned by the online server 30, the simulation server 20 can first determine whether the interface request corresponding to the response message is marked, so as to filter out the response messages of the marked interface requests. The simulation server 20 extracts the interface output parameters from the response messages of the marked interface requests.

[0041] The simulation server 20 can use the interface output parameters as an interface simulation data, and the interface simulation data can be identified by the basic information of the interface call corresponding to the interface output parameters. So that when applying the interface simulation data subsequently, the corresponding interface simulation data can be found through the basic information of the interface call.

[0042] The simulation server 20 stores the interface simulation data into the "expected set with the recording switch in the on state" determined in the above steps. And forwards the received response message to the service end 10.

[0043] The service end 10 can respond to the user operation based on the received response message.

[0044] In summary, the simulation data acquisition system proposed in the embodiments of the present application provides a configuration function for data recording for users at the service end, such as whether to turn on the data recording switch, the first service scenario identifier for turning on the data recording switch, and the first experience account. After the data recording switch is turned on, the service end requests the simulation server to turn on the recording switch for the first expected set corresponding to the first service scenario identifier and the first experience account. The service end listens to user operations in real time and constructs an interface request triggered by the user, which is an interface request triggered by the user when processing the page flow in this service scenario. The simulation server analyzes any interface request received to determine whether there is an expected set with the recording switch turned on for the account logged in by the user in the interface request. If so, it can be considered that simulation data needs to be stored for this interface request. Therefore, the present application marks such interface requests. The simulation server forwards all the received interface requests and forwards the response messages of the interface requests. The simulation server intercepts the response messages of the marked interface requests, copies the interface output parameters in the response messages, and stores the interface output parameters as interface simulation data corresponding to the interface call basic information in the expected set with the recording switch turned on. In this way, the present application intercepts and stores the real interface data in different service scenarios without affecting the normal operation of the application program, and uses it as the interface simulation data in this service scenario to provide the service scenario experience function for unregistered users at the service end. This method reduces the manual participation and can conveniently and efficiently obtain the complete interface simulation data in a certain service scenario.

[0045] In some embodiments, based on the expected sets stored in the simulation server, the service end can further provide APP experiences in different service scenarios for registered users.

[0046] For example, after the user opens the application program, an unregistered user can select an experience account to log in on the simulation workbench interface. Further, after selecting the experience account, the user can select the service scenario to be experienced from the service scenarios displayed on the simulation workbench interface and available for the user to select, so as to experience the page flow in this service scenario in the APP based on this experience account.

[0047] A registered user can log in to their registered account in the application program and use the registered account to conduct business processing in the application program.

[0048] Among them, the page flow can be understood as a series of pages and steps that a user experiences from opening the APP to completing a specific task or exiting the APP when using the APP. This process involves multiple aspects such as the interface design, interaction design, and user experience of the APP, and is a key link to ensure the smooth function and user-friendliness of the APP.

[0049] For example, the page process in the financial product purchase scenario can be as follows: First, a product browsing page is displayed to the user. After the user clicks on the thumbnail of a certain product, it jumps to the details page of that product. After the user clicks on the purchase button on the details page, it jumps to the user information filling page. After the user finishes filling in the information, it jumps to the payment page, and so on. The business side 10 can monitor the user's operations in real time. After the user logs in, the business side can monitor the account that the user logs in to in the application.

[0050] When the account that the user logs in to is the experience account selected by the user in the simulation workbench interface of the application, the business side 10 will display a list of business scenarios in the simulation workbench interface. This list of business scenarios includes one or more business scenarios that the user can choose from; the user can select the business scenario they want to experience from it, and the business side 10 can monitor the user's selection as the business scenario that the user selects to experience; After obtaining the business scenario that the user selects to experience, the business side 10 sends a request to enable the expectation set of this business scenario to the simulation server 20; After receiving this request to enable the expectation set, the simulation server 20 sets the expectation set of this business scenario to the enabled state.

[0051] Among them, the request to enable the expectation set may include the identifier of the business scenario that the user selects to experience, that is, the first business scenario identifier, so that after the simulation server 20 receives this request to enable the expectation set, it can find the expectation set of this business scenario according to the identifier of the business scenario and switch the state of the expectation set to the enabled state.

[0052] The simulation server 20 stores the expectation sets of different business scenarios. Each expectation set can store multiple pieces of interface simulation data under this business scenario. These interface simulation data can participate in building the page process of this business scenario on the front end; in this way, for unregistered users, even if they cannot respond to the user's operations through the online server, they can still respond to the user's operations through the simulation server 20 and simulate the page process of the business scenario for the user on the front end for unregistered users to experience the APP.

[0053] After the user logs in, the business side 20 will monitor the user's operations in the application in real time, such as click, input, drag and other operations. After the business side monitors the user's operations, it will respond to this operation; the operations that need to be responded to include the operations that can only be responded to based on the backend interface data. For example, after the user clicks on a certain function icon, the business side 10 will display the operation page of this function to the user.

[0054] Therefore, for these operations, the business side 10 will determine the basic data for interface calls required to respond to the user's operations. For example, the basic data for interface calls may include the URL of the interface, interface input parameters, and so on.

[0055] When constructing an interface request triggered by a user operation, add the identifier of the application, the account logged in by the user, and the basic information for interface invocation to the interface request to obtain the constructed interface request.

[0056] The service side 10 sends the constructed interface request to the simulation server 20. After receiving the interface request sent by the service side 10, the simulation server 20 parses the interface request to parse out the account logged in by the user, the identifier of the application, and the basic information for interface invocation. The simulation server 20 can first use the account logged in by the user and the identifier of the application to search in the space (i.e., the expected set) where the simulation server stores interface simulation data for the target expected set corresponding to both the account logged in by the user and the identifier of the application. Then, use the basic information for interface invocation to search for the target interface simulation data required for the above interface request from the target expected set.

[0057] When the simulation server 20 finds the target interface simulation data, it returns the target interface simulation data to the service side 10. After receiving the target interface simulation data, the service side 10 can respond to the user operation based on the target interface simulation data. In this way, based on the response of the simulation server to the user operation, the page process of the business scenario that the user wants to experience can be simulated on the business handling interface of the application.

[0058] In addition, when the simulation server 20 fails to find the target interface simulation data, it can return an information indicating that the data acquisition fails to the service side to remind the user to switch the experience account or business scenario.

[0059] This application also proposes a method for obtaining simulation data, which is applied to the above-mentioned service side 10. As Figure 2 shown, the method for obtaining simulation data may include the following steps: S201, monitor whether the data recording switch of the application is turned on. After the data recording switch is turned on, obtain the data recording information configured by the user on the simulation workbench interface of the application. The data recording information includes the first business scenario identifier for starting data recording and the first experience account.

[0060] S202, write the data recording information into a recording start request, and send the recording start request to the simulation server to enable the recording switch of the first expected set. The first expected set is the expected set created by the simulation server for the first business scenario identifier in the storage space of the first experience account, and the first expected set is used to store multiple interface simulation data in the first business scenario.

[0061] S203, obtain the account logged in by the user in the application.

[0062] S204, monitor the operations of the user in the application program, and determine the basic information of interface calls required to respond to the user operations.

[0063] S205, when constructing any interface request triggered by the user in the application program, add the account logged in by the user and the basic information of interface calls to the interface request.

[0064] S206, send the interface request to the simulation server, so that before the simulation server forwards the interface request to the online server, it determines whether there is a desired set with the recording switch turned on corresponding to the account logged in by the user in the interface request. If so, mark the interface request and record the basic information of interface calls of the interface request, so that before the simulation server forwards the response message of the online server to the service end for the interface request, extract the interface output parameters from the response message of the marked interface request, and use the interface output parameters as the interface simulation data corresponding to the basic information of interface calls, and store them in the desired set with the recording switch turned on, so as to store the interface simulation data for the first business scenario in the first desired set when the account logged in by the user is the first experience account.

[0065] S207, receive the response message forwarded by the simulation server, and respond to the user operations based on the response message.

[0066] The application program can display a business handling interface and a simulation workbench interface; the business handling interface is the interface provided by the application program for the user to handle business functions. For example, the home page of a financial credit APP, and different function sub-pages can be entered through the components provided by the business handling interface.

[0067] The simulation workbench interface is the interface provided by the application program for the user to configure data recording information and provide business scenario experience functions.

[0068] Developers can turn on the data recording switch, configure the first business scenario identifier and the first experience account for turning on data recording in the simulation workbench interface, so as to start the interface data recording of the first business scenario. The recorded interface data can be used as the interface simulation data in the first business scenario, and these interface simulation data are stored in the simulation server. The simulation server can regularly report the business scenario identifiers and experience accounts that have created desired sets locally to the online server. When the online server requests the configuration information of the application program from the service end, it sends these business scenario identifiers and experience accounts to the service end, and the service end can update the experience accounts and business scenarios available for the user to select displayed on the simulation workbench interface.

[0069] When an unregistered user wants to experience the APP page process in a certain business scenario, they can enable the business scenario experience function on the simulation workbench interface, select to log in to a certain experience account, and select the business scenario they want to experience. The business side can respond to the user's operation and request interface simulation data from the simulation server. In this way, the page process of the business scenario can be simulated for the user on the business handling interface for the user to experience.

[0070] The specific implementation manners of the above steps S201 - S207 can refer to the description of the above embodiments, and will not be elaborated here.

[0071] It should be noted that in the embodiments of the present application, the above steps S201 - S202 and the above steps S203 - S207 can be implemented in the same scenario or in different scenarios.

[0072] Exemplarily, the business side monitors the user's operations in the application program in real time. Such operations can be the operation of the user turning on the data recording switch, or the operation of the user handling business on the business handling interface, etc.

[0073] After the business side monitors that the data recording switch is turned on, it constructs and sends a recording start request to the simulation server; After the business side monitors other operations of the user, if it needs to call the backend interface data to respond to the user's operation, it constructs an interface request.

[0074] After the business side turns on the data recording switch, it can send the interface request triggered by the user to the simulation server; or it can send the interface requests triggered by the user both after and before turning on the data simulation switch to the simulation server.

[0075] The interface request sent by the business side includes the account logged in by the user and the basic information for interface call. When the data recording switch is turned on, the user can only select one account (i.e., the first experience account) from the experience accounts to log in. When the data recording switch is not turned on, the user can log in to other registered accounts.

[0076] The simulation server will respond to the recording start request of the business side and turn on the recording switch of the first expected set corresponding to the first experience account and the first business scenario identifier. Therefore, when the business side receives an interface request, if the account logged in by the user in the interface request is the first experience account, the simulation server will find the expected set corresponding to this account with the recording switch turned on. If the account logged in by the user is other registered accounts, the simulation server will not be able to find the expected set corresponding to this account with the recording switch turned on.

[0077] Therefore, after the data recording switch is turned on at the service end, the simulation data acquisition system can record information such as the input parameters, output parameters, and URLs of the interfaces without affecting the normal operation of the application program, and use this as the interface simulation data in a certain business scenario. After the data recording switch is turned off, the simulation data system can also normally respond to the interface requests sent by the service end.

[0078] In summary, the simulation data acquisition method proposed in the embodiments of the present application can be applied to the service end. After the service end detects that the data recording switch is turned on, it sends a recording start request including data recording information to the simulation server, so that the simulation server can turn on the recording switch of the first expected set jointly corresponding to the first business scenario identifier and the first experience account in the data recording information, so that the subsequent recorded interface output parameters can be stored in the first expected set as the interface simulation data in the first expected set. After the service end detects the user operation, if it needs to call an interface to respond to the user operation, it constructs a corresponding interface request, and transmits the interface request carrying the basic information of the interface call and the account logged in by the user to the simulation server, so that the simulation server can determine whether the account logged in by the user corresponds to an expected set with the recording switch turned on. If it exists, it can be considered that the response message of the interface request needs to be intercepted. The simulation server forwards the interface request and the response message of the interface request between the service end and the online server, and intercepts the response message that needs to be intercepted during the forwarding process, and copies out the interface output parameters in the response message. In this way, when developers need to obtain the simulation data of multiple interfaces in a certain business scenario, they can log in to the experience account at the service end, trigger a data recording request to the simulation server, and then operate the page process in the business scenario according to the business processing steps on the business processing interface of the application program. After the process ends, they can obtain the complete interface simulation data in the business scenario. This method is highly operable, not limited to professional technical personnel, can effectively reduce the investment in labor costs, and can obtain simulation data efficiently and conveniently.

[0079] Based on the above embodiments, the data recording information further includes the identifier of the application program; the interface request further includes the identifier of the application program.

[0080] The service end writes the data recording information into the recording start request and sends it to the simulation server. The simulation server searches for the expected set jointly corresponding to the first experience account and the first business scenario identifier from the stored expected sets. If the first expected set is not found, it creates an expected set for the first business scenario identifier in the storage space jointly corresponding to the first experience account and the identifier of the application program.

[0081] Correspondingly, when the service side constructs an interface request, it writes the identifier of the application program into the interface request. When the simulation server determines whether the account logged in by the user corresponds to an expected set with the recording switch turned on, it can be implemented through the following steps: Check whether there is a storage space corresponding to the account logged in by the user in the simulation server, then find the subspace corresponding to the identifier of the application program from this storage space, and finally determine whether there is an expected set with the recording switch turned on in this subspace.

[0082] In the embodiment of the present application, by further adding the identifier of the application program to the data recording information and the interface request, it is convenient for the simulation server to subdivide the expected set corresponding to an account, that is, store the expected sets belonging to the same application program in the same space. In this way, when searching for and managing the expected set, it can be clearer and the processing efficiency can be improved.

[0083] On the basis of the above embodiment, the interface request may further include the source domain name. Before the service side sends the interface request to the simulation server, the following steps may also be included: Remind the user to perform wireless network settings through the interaction component, so that the service side establishes a wireless connection with the preset wireless router, and the business end domain name allowed to participate in data recording is pre-stored in the preset wireless router. For example, the wireless network may be a wifi network, and the wireless router may be a wifi router.

[0084] Correspondingly, the service side sends the interface request to the simulation server, which can be implemented through the following steps: Send the interface request to the preset wireless router, so that the preset wireless router determines whether the source domain name in the interface request is the business end domain name stored in the preset wireless router; if so, send the interface request to the simulation server.

[0085] For example, a preset wireless router is set up within the enterprise developing the application program. For a new APP, after the APP is launched, developers can log in with an experience account by selecting it on the simulation workbench interface of the APP, and select the business scenario that needs to expand data recording after logging in, and set the network of the terminal device to the network provided by the preset wireless router. In this way, any interface request triggered by the developer on this APP will be forwarded by the preset wireless router to the simulation server.

[0086] It is not difficult to understand that the network coverage area is very large. After the network is turned on, multiple devices can be connected to it. In addition to the terminal device where the APP participating in data recording is located, there may also be other office devices or personal devices connected to the network corresponding to the preset wireless router. Therefore, the preset wireless router can judge the source domain name of the received interface requests. For other source domain names except for the business-side domain name of data recording, the interface requests under these domain names are uniformly forwarded to the online.

[0087] In the embodiment of the present application, the preset wireless router screens the interface requests entering the simulation server, and only forwards the above interface requests (that is, the interface requests including the business-side domain name allowing data recording) to the simulation server, so as to restrict the number of interface requests sent to the simulation server and ensure that the interface requests sent by the business side participating in data recording can be processed in time.

[0088] On the basis of the above embodiment, as Figure 3 shown, after "writing the data recording information into the recording start request and sending the recording start request to the simulation server" in the above step S202, the method for obtaining simulation data may further include the following steps: S301, monitor whether the data recording switch is turned off. After the data recording switch is turned off, write the data recording information into the recording stop request.

[0089] S302, send the recording stop request to the simulation server, so that the simulation server sets the recording switch of the first expected set to the off state.

[0090] Exemplarily, after the developer finishes data recording, enter the simulation workbench interface to turn off the data recording switch.

[0091] The business side can monitor in real time whether the data recording switch is turned off. After the data recording switch is turned off, write the data recording information configured by the developer when turning on the data recording switch into the recording stop request.

[0092] The business side sends the recording stop request to the simulation server.

[0093] After receiving the recording stop request, the simulation server sets the recording switch of the first expected set to the off state.

[0094] After the data recording switch is turned on in the embodiments of the present application, the state of the data recording switch is still monitored in real time. After the data recording switch is turned off, a recording close request is sent to the simulation server to request the simulation server to turn off the recording switch that is turned on for the first expected set, so as to avoid data recording and storage for interface requests triggered by developers after the data recording switch is turned off, which affects the matching degree between the interface simulation data in the expected set and the business scenarios corresponding to the expected set, that is, to avoid storing the interface output parameters in other business scenarios into the expected set corresponding to a certain business scenario.

[0095] The present application proposes a method for obtaining simulation data, which is applied to a simulation server. As Figure 4 shown, the method may include the following steps: S401, receiving a recording start request sent by a service terminal, where the recording start request includes data recording information configured by a user on the simulation workbench interface of an application program, and the data recording information includes a first business scenario identifier for starting data recording and a first experience account.

[0096] S402, finding a first expected set corresponding to both the first business scenario identifier and the first experience account from the stored expected sets, where the first expected set is used to store multiple pieces of interface simulation data in the first business scenario.

[0097] S403, setting the recording switch of the first expected set to the on state.

[0098] S404, receiving an interface request sent by the service terminal, where the interface request is triggered in the user application program, and the interface request includes the account logged in by the user and interface call basic information.

[0099] S405, determining whether there is an expected set with a recording switch in the on state corresponding to the account logged in by the user.

[0100] S406, if so, marking the interface request and recording the interface call basic information of the interface request.

[0101] S407, forwarding the received interface request to an online server so that the online server returns a response message to the interface request.

[0102] S408, receiving the response message to the interface request and filtering out the response message to the marked interface request from it.

[0103] S409, copying the interface output parameter from the response message to the marked interface request.

[0104] S410. Use the output parameter of the interface as the interface simulation data corresponding to the interface call basic information, and store it in the desired set where the recording switch is in the on state, so as to store the interface simulation data for the first service scenario in the first desired set when the account logged in by the user is the first experience account.

[0105] S411. Forward all the received response messages to the service end, so that the service end can respond to the user operation based on the response messages.

[0106] Exemplarily, the simulation server responds to the recording start request of the service end, and checks whether there is a desired set that matches the data recording information locally, such as the desired set jointly corresponding to the first service scenario identifier and the first experience account. If it exists, turn on the recording switch of this desired set. If it does not exist, create a desired set jointly corresponding to the first service scenario identifier and the first experience account, and then turn on the recording switch of this desired set.

[0107] After the simulation server receives any interface request, it can first determine whether there is a desired set in the locally stored desired sets that corresponds to the account logged in by the user provided in this interface request and whose recording switch is in the on state. If so, confirm that it is necessary to copy the output parameter obtained by this interface request to be used as the interface simulation data required by this interface request. Therefore, the simulation server will add a mark to this type of interface request. For the convenience of distinction, the marks added to each interface request can be different. If not, confirm that it is not necessary to copy the output parameter obtained by this interface request, and the simulation server can directly forward this type of interface request to the online server.

[0108] After the simulation server receives the response message of any interface request, it can first determine whether there is a mark for the interface request corresponding to this response message. If there is, copy the interface output parameter from this response message, and this interface output parameter can be used as the interface simulation data required by this interface request. And identify this interface simulation data with the interface call basic information in this interface request, so that when performing interface simulation later, the required interface simulation data can be quickly matched through the interface call basic information.

[0109] In summary, the method for obtaining simulated data proposed in this application can be applied to a simulation server. When the business side requests to start recording, the simulation server turns on the recording switch for the corresponding expected set so that the obtained simulated data can be stored in this expected set. The simulation server forwards the interface requests and response messages transmitted between the business side and the online server. During the forwarding process, for the interfaces that need to record data, it records the basic information of the interface call in the interface request and the output parameters of the interface in the response message, and stores the recorded information to obtain multiple pieces of interface simulated data stored under the expected set in this way. This method only requires developers to configure information in the application interface of the business side and operate in the application according to the business handling steps. It has strong operability and can be implemented by non-professional technical personnel, reducing the labor input cost and being able to obtain complete interface simulated data in a certain business scenario conveniently and efficiently.

[0110] In some embodiments, the simulation server can also be used to filter the received interface requests, and the steps are as follows: Judge whether the request domain name is a preset business domain name; judge whether the request belongs to the requests marked in the preset filtering list.

[0111] Exemplarily, after an interface request simultaneously meets the above two conditions, the interface request can be processed in steps S404 - S405. That is, the interface requests processed in steps S404 - S405 are all requests for the online server of the above application program, and this request does not belong to the requests marked in the preset filtering list.

[0112] The requests marked in the filtering list may include: interface requests that have nothing to do with the page flow construction in the business scenario, such as interface requests for reporting buried points, etc.

[0113] Based on the above embodiments, as Figure 5 shown, the step "find the first expected set corresponding to the first business scenario identifier and the first experience account from the stored expected sets" in the above step S402 may include the following steps: S501, check whether there is a storage space corresponding to the first experience account in the simulation server.

[0114] S502, if there is a storage space corresponding to the first experience account, then check whether there is an expected set corresponding to the first business scenario identifier in the storage space.

[0115] S503, if there is an expected set corresponding to the first business scenario identifier in the storage space, then use the expected set corresponding to the first business scenario identifier as the first expected set.

[0116] S504. If the expected set corresponding to the first service scenario identifier does not exist in the storage space, create in the storage space the expected set corresponding to the first service scenario identifier as the first expected set.

[0117] S505. If the storage space corresponding to the first experience account does not exist, create in the simulation server the storage space corresponding to the first experience account, and create in the storage space the expected set corresponding to the first service scenario identifier as the first expected set.

[0118] The implementation manners of the above steps S501 - S505 may refer to the description of the above embodiments, and will not be elaborated here.

[0119] Based on the above embodiments, the data recording information further includes the identifier of the application; in the above step S502, "checking whether the expected set corresponding to the first service scenario identifier exists in the storage space" may include the following steps: Check whether a subspace corresponding to the identifier of the application exists in the storage space; If a subspace corresponding to the identifier of the application exists, check whether the expected set corresponding to the first service scenario identifier exists in the subspace; If the expected set corresponding to the first service scenario identifier exists in the subspace, confirm that the expected set corresponding to the first service scenario identifier exists in the storage space; If the expected set corresponding to the first service scenario identifier does not exist in the subspace, confirm that the expected set corresponding to the first service scenario identifier does not exist in the storage space; In the above steps S504 and S505, "creating in the storage space the expected set corresponding to the first service scenario identifier" may include the following steps: If a subspace corresponding to the identifier of the application exists in the storage space and the expected set corresponding to the first service scenario identifier does not exist in the subspace corresponding to the identifier of the application, create in the subspace corresponding to the identifier of the application the expected set corresponding to the first service scenario identifier; If a subspace corresponding to the identifier of the application does not exist in the storage space, create in the storage space the subspace corresponding to the identifier of the application, and create in the subspace corresponding to the identifier of the application the expected set corresponding to the first service scenario identifier; Correspondingly, the interface request further includes the identifier of the application; In the above step S405, "judging whether the account logged in by the user corresponds to an expected set with the recording switch turned on" may include the following steps: Find the subspace corresponding to the application program identifier from the storage space corresponding to the account logged in by the user; determine whether there is an expected set with the recording switch turned on in the subspace corresponding to the application program identifier.

[0120] Based on the above embodiments, the simulated data acquisition method executed by the simulation server may further include the step of closing the recording switch of the expected set: the simulation server receives the recording closing request sent by the service side, and the recording closing request includes data recording information; the simulation server sets the recording switch of the first expected set to the closed state.

[0121] Based on the above embodiments, as Figure 6 shown, the method for acquiring simulated data proposed in this application further includes: S601, determine the expected sets newly created on the simulation server within a preset time period.

[0122] S602, send the second service scenario identifier and the second experience account corresponding to the newly created expected set to the online server, so that when the online server issues the configuration information of the application program, it issues the second service scenario identifier and the second experience account to different service sides, so that the service side updates the service scenario identifier and the experience account displayed on the simulation workbench interface.

[0123] Exemplarily, the simulation server can regularly sort out the expected sets newly created locally and sort out the service scenario identifiers and experience accounts corresponding to the expected sets. For the convenience of distinction, in the embodiments of this application, the service scenario identifier corresponding to the newly created expected set is expressed as the second service scenario identifier, and the experience account corresponding to the newly created expected set is expressed as the third experience account.

[0124] The simulation server can report the sorted second service scenario identifier and the second experience account to the online server corresponding to the application program; when the service side requests the configuration file of the application program, the online server issues these second service scenario identifiers and second experience accounts to different service sides, and the service side updates the issued second service scenario identifier and second experience account to the simulation workbench interface to expand the service scenarios and experience accounts available for unregistered users to select.

[0125] For example, developers only need to create an experience account and a business scenario on a terminal device and start recording the interface data under the business scenario. The simulation server will report these experience accounts and business scenarios to the online server, which will then distribute them to different terminal devices. In this way, the users of different terminal devices can enter the simulation workbench interface of the application, log in to the experience account, and select the business scenario they want to experience. The terminal device can request interface simulation data from the simulation server based on the experience account logged in by the user and the selected business scenario, so as to simulate the page process for unregistered users.

[0126] In the embodiments of the present application, by regularly reporting the business scenario identifiers and experience accounts of the newly created desired set to the online server so that the online server can synchronize them to different terminal devices, the applicable range of the obtained interface simulation data is enhanced.

[0127] Those of ordinary skill in the art can understand that all or part of the processes of implementing the methods in the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, storage, database, or other medium used in the embodiments provided in the present application can include non-volatile and / or volatile memories. Non-volatile memories can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memories can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0128] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the above division of each functional unit and module is used as an example. In actual applications, the above functions can be allocated to different functional units and modules according to needs, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0129] The above-described embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present application, and should all be included within the protection scope of the present application.

Claims

1. A method for obtaining analog data, characterized in that, Applied to the business side, the method includes: Listening for whether the data recording switch of the application is turned on. After the data recording switch is turned on, obtaining the data recording information configured by the user on the simulated workbench interface of the application, where the data recording information includes the first business scenario identifier for starting data recording and the first experience account; Writing the data recording information into a recording start request and sending the recording start request to the simulation server, so that the simulation server turns on the recording switch of the first expected set. The first expected set is an expected set created by the simulation server for the first business scenario identifier in the storage space of the first experience account, and the first expected set is used to store multiple interface simulation data under the first business scenario; Obtaining the account logged in by the user in the application; Listening for the operations of the user in the application and determining the basic information of the interface call required to respond to the user's operations; When constructing any interface request triggered by the user in the application, adding the account logged in by the user and the basic information of the interface call to the interface request; Sending the interface request to the simulation server, so that before the simulation server forwards the interface request to the online server, it determines whether there is an expected set with the recording switch turned on corresponding to the account logged in by the user in the interface request. If so, marking the interface request and recording the basic information of the interface call of the interface request, so that before the simulation server forwards the response message of the online server to the interface request to the business side, extracting the interface output parameters from the response message of the marked interface request and using the interface output parameters as the interface simulation data corresponding to the basic information of the interface call, and storing them in the expected set with the recording switch turned on, so as to store the interface simulation data for the first business scenario in the first expected set when the account logged in by the user is the first experience account; Receiving the response message forwarded by the simulation server to respond to the user's operations based on the response message.

2. The method according to claim 1, wherein The data recording information further includes the identifier of the application; the interface request further includes the identifier of the application; The first expected set is an expected set created by the simulation server for the first business scenario identifier in the storage space jointly corresponding to the first experience account and the identifier of the application.

3. The method according to claim 1, characterized in that, The interface request further includes the source domain name. Before sending the interface request to the simulation server, the method further includes: Reminding the user to perform a wireless network setting through an interaction component, so that the business side establishes a wireless connection with a preset wireless router, and the preset wireless router stores in advance the domain name of the business side allowed to participate in data recording; The sending the interface request to the simulation server includes: Sending the interface request to the preset wireless router, so that the preset wireless router determines whether the source domain name in the interface request is the domain name of the business side stored in the preset wireless router; If so, sending the interface request to the simulation server.

4. The method according to any one of claims 1 to 3, characterized in that After writing the data recording information into the recording start request and sending the recording start request to the simulation server, the method further includes: Listening for whether the data recording switch is turned off. After the data recording switch is turned off, write the data recording information into a recording stop request; Send the recording stop request to the simulation server, so that the simulation server sets the recording switch of the first expected set to the off state.

5. A method for obtaining analog data, characterized in that, Applied to the simulation server, the method includes: Receive a recording start request sent by the service side. The recording start request includes data recording information configured by the user in the simulation workbench interface of the application program. The data recording information includes a first service scenario identifier for starting data recording and a first experience account; From the stored expected sets, find the first expected set jointly corresponding to the first service scenario identifier and the first experience account. The first expected set is used to store multiple interface simulation data in the first service scenario; Set the recording switch of the first expected set to the on state; Receive an interface request sent by the service side. The interface request is triggered by the user in the application program. The interface request includes the account logged in by the user and basic interface call information; Determine whether there is an expected set with the recording switch in the on state corresponding to the account logged in by the user; If so, mark the interface request and record the basic interface call information; Forward the received interface request to the online server, so that the online server returns a response message to the interface request; Receive the response message of the interface request and filter out the response message of the marked interface request from it; Copy the interface output parameters from the response message of the marked interface request; Use the interface output parameters as the interface simulation data corresponding to the basic interface call information and store them in the expected set with the recording switch in the on state, so as to store the interface simulation data for the first service scenario in the first expected set when the account logged in by the user is the first experience account; Forward all the received response messages to the service side, so that the service side responds to the user operation based on the response messages.

6. The method according to claim 5, characterized in that, The finding the first expected set jointly corresponding to the first service scenario identifier and the first experience account from the stored expected sets includes: Check whether there is a storage space corresponding to the first experience account in the simulation server; If there is a storage space corresponding to the first experience account, check whether there is an expected set corresponding to the first service scenario identifier in the storage space; If there is an expected set corresponding to the first service scenario identifier in the storage space, use the expected set corresponding to the first service scenario identifier as the first expected set; If there is no expected set corresponding to the first service scenario identifier in the storage space, create an expected set corresponding to the first service scenario identifier in the storage space and use it as the first expected set; If there is no storage space corresponding to the first experience account, create a storage space corresponding to the first experience account in the simulation server, and create an expectation set corresponding to the first business scenario identifier in the storage space as the first expectation set.

7. The method according to claim 5, wherein The method further includes: Receiving a recording shutdown request sent by the service terminal, where the recording shutdown request includes the data recording information; Setting the recording switch of the first expectation set to the off state.

8. The method according to claim 5, characterized in that The method further includes: Determining the newly created expectation sets on the simulation server within a preset time period; Sending the second business scenario identifier and the second experience account corresponding to the newly created expectation set to the online server, so that when the online server issues the configuration information of the application program, the second business scenario identifier and the second experience account are issued to different service terminals, so that the service terminal updates the business scenario identifier and the experience account displayed on the simulation workbench interface.

9. The method according to claim 6, characterized in that, The data recording information further includes the identifier of the application program; The step of finding whether there is an expectation set corresponding to the first business scenario identifier in the storage space includes: Finding whether there is a subspace corresponding to the identifier of the application program in the storage space; If there is a subspace corresponding to the identifier of the application program, finding whether there is an expectation set corresponding to the first business scenario identifier in the subspace; If there is an expectation set corresponding to the first business scenario identifier in the subspace, confirming that there is an expectation set corresponding to the first business scenario identifier in the storage space; If there is no expectation set corresponding to the first business scenario identifier in the subspace, confirming that there is no expectation set corresponding to the first business scenario identifier in the storage space; The step of creating an expectation set corresponding to the first business scenario identifier in the storage space includes: If there is a subspace corresponding to the identifier of the application program in the storage space and there is no expectation set corresponding to the first business scenario identifier in the subspace corresponding to the identifier of the application program, create an expectation set corresponding to the first business scenario identifier in the subspace corresponding to the identifier of the application program; If there is no subspace corresponding to the identifier of the application program in the storage space, create a subspace corresponding to the identifier of the application program in the storage space, and create an expectation set corresponding to the first business scenario identifier in the subspace corresponding to the identifier of the application program; The interface request further includes the identifier of the application program; the step of determining whether the account logged in by the user corresponds to an expectation set with the recording switch in the on state includes: Finding the subspace corresponding to the identifier of the application program from the storage space corresponding to the account logged in by the user; Judging whether there is an expectation set with the recording switch in the on state in the subspace corresponding to the identifier of the application program.

10. A system for acquiring analog data, characterized in that, The system includes a service terminal, a simulation server, and an online server; The business end is used to monitor whether the data recording switch of the application is turned on. After the data recording switch is turned on, it obtains the data recording information configured by the user in the simulated workbench interface of the application. The data recording information includes the first business scenario identifier for enabling data recording and the first experience account. The business end is used to write the data recording information into a recording start request and send the recording start request to the simulation server. The simulation server is used to, after receiving the recording start request, find in the stored expected set the first expected set jointly corresponding to the first business scenario identifier and the first experience account. The expected set is used to store multiple pieces of interface simulation data in a business scenario. The simulation server is used to set the recording switch of the first expected set to the on state. The business end is used to obtain the account logged in by the user in the application. The business end is used to monitor the operations of the user in the application and determine the basic information for interface calls required to respond to the user's operations. When constructing any interface request triggered by the user in the application, the business end is used to add the account logged in by the user and the basic information for interface calls to the interface request. And send the interface request to the simulation server. The simulation server is used to receive the interface request and determine whether there is an expected set with the recording switch in the on state corresponding to the account logged in by the user. If so, the simulation server is used to mark the interface request and record the basic information for interface calls of the interface request. The simulation server is used to forward the received interface request to the online server. The online server is used to obtain the interface output parameters according to the basic information for interface calls in the interface request, write the interface output parameters into the response message of the interface request, and return the response message of the interface request to the simulation server. The simulation server is used to receive the response message of the interface request and filter out the response messages of the marked interface requests from it. The simulation server is used to copy the interface output parameters from the response messages of the marked interface requests. The simulation server is used to use the interface output parameters as the interface simulation data corresponding to the basic information for interface calls and store them in the expected set with the recording switch in the on state, so as to store the interface simulation data for the first business scenario in the first expected set when the account logged in by the user is the first experience account. The simulation server is used to forward all the received response messages to the business end. The business end is used to receive the response messages forwarded by the simulation server to respond to the user's operations based on the response messages.

Images