CN113282477A - Mobile terminal form behavior record query method, system, equipment and storage medium - Google Patents
Mobile terminal form behavior record query method, system, equipment and storage medium Download PDFInfo
- Publication number
- CN113282477A CN113282477A CN202110822288.0A CN202110822288A CN113282477A CN 113282477 A CN113282477 A CN 113282477A CN 202110822288 A CN202110822288 A CN 202110822288A CN 113282477 A CN113282477 A CN 113282477A
- Authority
- CN
- China
- Prior art keywords
- protocol
- log
- mobile terminal
- time axis
- behavior
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/26—Visual data mining; Browsing structured data
Abstract
The invention discloses a mobile terminal form behavior record query method, which comprises the steps that a mobile terminal sends a login request to a log server, the log server responds and issues a first instruction to a log tracker, and the first instruction is used for constructing a log user ID according to collected user information of the mobile terminal; the mobile terminal enters a form page to trigger all event behaviors so that the form sends corresponding protocols to a log server, then enters a tracking display terminal to perform login verification, and sends a log query instruction to the log server when the verification is passed; and the mobile terminal queries on a behavior record display page, wherein the behavior record display page comprises a form time axis, an event time axis and a behavior time axis. According to the invention, through a graphical log display mode, the working efficiency is improved, and the dependence on platform developers is reduced.
Description
Technical Field
The invention relates to the technical field of log data analysis, in particular to a method, a system, equipment and a storage medium for inquiring form behavior records of a mobile terminal.
Background
In the software development and test process, the configuration of the form and the behavior record of the mobile terminal are very important. When configuring the form, the existing developer mainly configures the form through a server and issues the form to a corresponding mobile App to execute the form. However, due to the complexity of the business and the technical ability of the implementing developers, the quality levels of the configured forms are not uniform, and various problems occur in the running process. For example: because the App engine environment operated by the form is not directly open to the outside, once an error occurs, the form is difficult to locate; if an error code occurs, because the error report of the interface cannot be checked by self, the error can be searched only by unlocking the engine environment, so that the operation is complex and the efficiency is low; in addition, the existing scheme usually collects and analyzes error information through log burying points, but because the log files are huge in number and do not have data interaction with each other, the troubleshooting work is often difficult to carry out, even if errors are located, the reasons for the errors are difficult to restore, and the work difficulty of developers is further increased.
Disclosure of Invention
The invention aims to provide a method, a system, equipment and a storage medium for inquiring form behavior records of a mobile terminal, so as to solve the problems of difficult error positioning and low investigation efficiency in the conventional form behavior inquiry.
In order to overcome the defects in the prior art, the invention provides a mobile terminal form behavior record query method, which comprises the following steps:
the mobile terminal sends a login request to a log server, the log server responds and issues a first instruction to a log tracker, and the first instruction is used for constructing a log user ID according to the collected user information of the mobile terminal;
the mobile terminal enters a form page and triggers all event behaviors to enable the form to send a corresponding protocol to the log server; the protocols comprise a PBegin protocol, an EBegin protocol, an ABegin protocol, an AAtion protocol, an AEnd protocol, an EEnd protocol and a PENd protocol;
the mobile terminal enters a tracking display terminal to perform login verification, and when the verification is passed, a log query instruction is sent to the log server, the log server sends a queried log file and a corresponding protocol to the tracking display terminal, and the tracking display terminal converts the log file and draws a behavior record display page according to a converted result;
and the mobile terminal queries the behavior record display page, wherein the behavior record display page comprises a form time axis, an event time axis and a behavior time axis.
Further, the PBegin protocol is used for the tracking end displayer to draw the form time axis; the EBegin protocol is used for the tracking end displayer to draw the form event time axis; the ABegin protocol is used for drawing a form behavior time axis by a tracking end displayer; the AAtion protocol is used for recording form behavior information and context information related to the form behavior; the AEnd protocol is used for the tracing end displayer to finish drawing the form behavior time axis; the EEnd protocol is used for the tracking end displayer to finish drawing the form event time axis; the PEnd protocol is used for the tracking end displayer to finish drawing the form time axis.
Further, the form triggers multiple AAtion protocols when an event action occurs.
Further, the form is also used to cycle through the ABegin protocol and the AEnd protocol until all events and all actions are performed.
Further, the protocol sent by the form passes through the log tracker and is then sent to the log server.
Further, the constructing a log user ID according to the user information includes:
acquiring login information and system information of a user; the login information comprises a tenant number, a post number and a login ID; the system information comprises an app version and a mobile terminal system version;
converting the login information and the character string of the system information into a decimal number array, and encrypting by using a public key;
and converting the encrypted key into a character string as a log user ID.
The invention also provides a mobile terminal form behavior record query system, which comprises:
the log user ID constructing unit is used for sending a login request to a log server by the mobile terminal, the log server responds and issues a first instruction to the log tracker, and the first instruction is used for constructing a log user ID according to the collected user information of the mobile terminal;
the protocol sending unit is used for the mobile terminal to enter a form page and trigger all event behaviors to enable the form to send a corresponding protocol to the log server; the protocols comprise a PBegin protocol, an EBegin protocol, an ABegin protocol, an AAtion protocol, an AEnd protocol, an EEnd protocol and a PENd protocol;
the display page drawing unit is used for enabling the mobile terminal to enter the tracking display terminal for login verification, sending a log query instruction to the log server when the verification is passed, sending the queried log file and the corresponding protocol to the tracking display terminal by the log server, converting the log file by the tracking display terminal, and drawing a behavior record display page according to the converted result;
and the query unit is used for the mobile terminal to query the behavior record display page, and the behavior record display page comprises a form time axis, an event time axis and a behavior time axis.
Further, the PBegin protocol is used for the tracking end displayer to draw the form time axis; the EBegin protocol is used for the tracking end displayer to draw the form event time axis; the ABegin protocol is used for drawing a form behavior time axis by a tracking end displayer; the AAtion protocol is used for recording form behavior information and context information related to the form behavior; the AEnd protocol is used for the tracing end displayer to finish drawing the form behavior time axis; the EEnd protocol is used for the tracking end displayer to finish drawing the form event time axis; the PEnd protocol is used for the tracking end displayer to finish drawing the form time axis.
The present invention also provides a terminal device, including:
one or more processors;
a memory coupled to the processor for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the mobile end form behavior record query method as described in any of the above.
The invention also provides a computer readable storage medium, on which a computer program is stored, the computer program being executed by a processor to implement the mobile terminal form behavior record query method as described in any of the above.
Compared with the prior art, the invention has the beneficial effects that:
1) according to the method, the log information is displayed graphically, so that an implementer can visually check the log information and the positioning problem through a graphical display interface, the positioning difficulty of the problem is reduced, the troubleshooting efficiency is improved, and the dependence on platform developers is reduced;
2) the context environment information is graphically displayed, so that the execution effect of the form logic configured by an implementer is truly reflected, the execution effect meets the service requirement, but the execution logic is not executed as designed;
3) through graphical display of historical time lines, implementation can locate errors according to a clue and further assist in solving the problems by context environments in case of errors; meanwhile, the graphical log is attached with command line interaction capability, more log information can be extracted and aggregated according to the result of graphical representation through an auxiliary command line command, and problems can be positioned and analyzed more conveniently.
Drawings
In order to more clearly illustrate the technical solution of the present invention, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flowchart of a method for querying a form behavior record of a mobile terminal according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of data interaction for constructing a user log ID according to an embodiment of the present invention;
FIG. 3 is a diagram illustrating a data interaction between a form engine and a log server via a log collection module according to an embodiment of the present invention;
fig. 4 is a data interaction diagram for verifying a mobile end user ID at a tracking and displaying end according to an embodiment of the present invention;
FIG. 5 is a diagram of data interaction when a time axis is plotted at a trace show end according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a mobile terminal form behavior record query system according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be understood that the step numbers used herein are for convenience of description only and are not used as limitations on the order in which the steps are performed.
It is to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the specification of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
The terms "comprises" and "comprising" indicate the presence of the described features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The term "and/or" refers to and includes any and all possible combinations of one or more of the associated listed items.
In a first aspect:
referring to fig. 1, an embodiment of the present invention provides a method for querying a mobile terminal form behavior record, including:
s10, the mobile terminal sends a login request to a log server, the log server responds and issues a first instruction to a log tracker, and the first instruction is used for constructing a log user ID according to the collected user information of the mobile terminal;
in this step, mainly the mobile terminal performs data interaction with the log server, as shown in fig. 2, fig. 2 provides a data interaction flowchart of step S10. Specifically, step S10 includes:
1) after an implementer logs in the main interface by using the mobile terminal, the log tracker stores the complete information of the current login user in the log server, and simultaneously, partial contents in the complete information are used for constructing a log user ID which is used as a unique certificate of the log tracking displayer and log token information of the subsequent user login.
It should be noted that, the "log tracker", i.e. the log collection module, is a piece of logic code running in the app and is used for recording all operations and data and interface changes generated by the operations when the user uses the form, and sending the data to the back-end server. These operations are: form open/close (corresponding to PBegin/Pend protocol), event start execution/event done execution (corresponding to EBegin/EEnd protocol), action start execution/action done (corresponding to ABegin/AEnd protocol). It should be noted that there are multiple events in a form, and a user can trigger the events any number of times, and each event is composed of any number of behaviors, and each behavior has its own business meaning and logic.
In one specific embodiment, the log user ID generated in step 1) is generated as follows:
1.1) obtaining login information of a user, comprising: tenant number, post number, login ID;
1.2) acquiring system information of a user, comprising: an app version and a mobile terminal system version;
1.3) respectively converting the character strings into 10-system digital arrays, and encrypting the 10-system digital arrays by using public and private keys;
4) the resulting key is converted to a string, which is the log user ID.
S20, the mobile terminal enters a form page and triggers all event behaviors to enable the form to send a corresponding protocol to the log server; the protocols comprise a PBegin protocol, an EBegin protocol, an ABegin protocol, an AAtion protocol, an AEnd protocol, an EEnd protocol and a PENd protocol;
in this step, mainly the form engine and the log collection module perform data interaction with the log server, as shown in fig. 3. Wherein, the log collection module mainly adopts a tool which is a tracking end display. The data interaction process between the two is mainly represented by step 2) entering the form from the main interface.
Specifically, step 2) further comprises:
2.1) open the form, at which time the form issues the PBegin protocol, which is used by the trace-end presenter to begin drawing the form timeline.
It should be noted that the PBegin protocol is a protocol specifically designed for the tracker and the tracking end presenter, and is used for recording information such as the opening time of a form, a form ID, a form name, and a form protocol, and since the protocol only contains original information at the time of recording and cannot be directly used for interface drawing of the tracking end presenter, the protocol is further converted into a PDBegin protocol later, and the protocol adds style parameters such as pixels and drawing styles for starting drawing on the original basis.
2.2) when the form event is triggered, the form sends out an EBegin protocol which is used for the tracking end displayer to draw the time axis of the form event.
Similar to PBegin, EBegin is a specially designed protocol for recording the start execution time, event ID, event name, execution logic of an event, and execution result of an event in a form. The form event timeline is similar to the form timeline and is used for displaying the start and end ranges of an event in relative time, visually displaying the life cycle of the event in a graphical mode, and meanwhile, a user can acquire detailed execution information of the event, such as an event name, the execution start and completion time of the event, an execution result of the event and logic triggered during the event execution by clicking the timeline, and display the acquired information in forms, graphs and the like, so that a series of expressions of the user when the event is triggered can be restored in a visual mode.
The tracking end displayer is used for restoring, displaying and drawing the logic code of the operation behavior running on the pc end and the web end. The form time axis refers to a UI interactive control of the log display interface, and is used for displaying a start range and an end range of the form in relative time, and visually displaying a life cycle of the form in a graphical manner, and meanwhile, a user can click the form time axis to acquire detailed information of the form, such as a form name, a form protocol, and an opening time and a closing time of the form, and display the acquired information in forms, diagrams, and the like, so as to visually display data information of the form.
2.3) when the form event is composed of any plurality of behaviors, the form sends out an ABegin protocol which is used by the tracer end displayer to draw a form behavior time axis.
The ABegin is also a specially designed protocol for recording the action name and the action ID of any action in the event. The form behavior time axis is used for displaying the starting and ending range of the behavior in relative time, the life cycle of the behavior is visually displayed in a graphical mode, meanwhile, a user can acquire the execution detailed information of the behavior by clicking the time axis, such as the behavior name, the execution starting and finishing time of the behavior, the execution result of the behavior, the logic triggered during the behavior execution, and the data and data change generated during the behavior form, and the acquired information is displayed in a form, a chart and the like, so that a series of expressions of the behavior can be restored in a visual mode.
In a specific embodiment, the following two points need to be explained in step 2.3):
a) when the ABegin protocol is sent out, the behavior sends out all the context information of the behavior and the current detailed information of the behavior contained in the AAtion protocol;
b) one action will issue any number of AAtion protocols
Generally, ABegin and AEnd can only record the start and end time and result of a behavior, and cannot record the change of execution logic and data of a specific behavior, so a protocol needs to be designed and dedicated to the recording of different behaviors, in fact, AAtion is a general term for a specific behavior, and the specific behavior further includes: ADataSubmitAction record data submission behavior protocol, adataresultsaction record data request behavior protocol, AScriptAction record script execution behavior protocol, ALinkAction record form jump behavior protocol, and the like.
2.4) when the action execution is finished, the form sends out an AEnd protocol which is used by the tracer end displayer to finish drawing the form action time axis.
It should be noted that, because there are any multiple behaviors, the form will loop out the ABegin and the AEnd protocol until all the behaviors of all the events are executed, wherein the AEnd protocol is paired with the ABegin and used for recording the end time and the execution result of the behaviors.
2.5) when all the actions of the event are executed, namely the event is executed completely, the form sends out an EEnd protocol which is used for drawing the time axis of the form event when the tracking end displayer finishes drawing.
It should be noted that, because a single table has any number of behaviors, the EBegin and the EEnd protocols are issued whenever an event is triggered. The EEnd protocol is paired with EBegin and is used for recording the end time and the execution result of the event.
2.6) when the form is closed, the form issues the PENd protocol, which is used by the tracer displayer to draw the form timeline when the exhibition is finished.
In this step, the PEnd protocol corresponds to PBegin and is used to record the end time of the form. It should be noted that each protocol is sent to the log server through the log tracker before being sent.
S30, the mobile terminal enters a tracking display terminal to perform login verification, when the verification is passed, a log query instruction is sent to the log server, the log server sends a queried log file and a corresponding protocol to the tracking display terminal, the tracking display terminal converts the log file, and a behavior record display page is drawn according to a converted result;
referring to fig. 4, the operation of step S30 mainly includes the following steps:
3) and opening the tracking display end, displaying the login two-dimensional code by the tracking display end, scanning the two-dimensional code by the app, and sending the log user ID to the log server end for verification.
3.1) after the log user ID is sent to a log server, a 10-system digital array is analyzed by using a private key;
3.2) converting the 10-system array into character strings, and comparing the character strings with tenant numbers, post numbers, login IDs, app versions and mobile terminal system versions stored in a log server one by one;
and 3.3) after the comparison is successful, the log server side informs the tracking display side to switch the two-dimensional code interface to a log query interface to wait for the use of a user.
4) The log query interface automatically brings out the tenant name, the post name, the account number, the app version and the mobile terminal system version of the current user according to the log user ID, and for a common user, the content serving as the query option is locked on the interface and cannot be modified, and for an administrator, the content can be modified.
5) The user inputs the form name for query, and the query mode is as follows:
5.1) forming a query path by a tenant number corresponding to the tenant name, a post number corresponding to the post name, an account ID corresponding to the account, an app version, a mobile terminal system version, a time date and a form name and delivering the query path to a log server
5.2) the log service end returns the PBegin, PENd, EBegin, EEnd, ABegin, AEnd and AAtion log files which are inquired to the tracking and showing end.
6) The returned log file is stored in the form action storage container, and conversion processing is performed thereon, as shown in fig. 5. Wherein, drawing is performed in a time period of 400 pixels = =1000 milliseconds on a scale, specifically, the conversion operation content is as follows:
6.1) calculating the life cycle duration of the form according to PBegin and PENd protocols, and converting the PBegin and PENd into a TDBegin protocol and a TDEnd protocol, wherein the TDBegin protocol and the TDEnd protocol are used for drawing a time axis scale on an interface, and the termination time of the time axis scale is the life cycle time of the form;
6.2) converting the PBegin and PENd protocols into PDBegin and PDEnd protocols, and drawing a form time axis below a time axis scale;
6.3) converting the EBegin and EEnd protocols into EDBegin and EDEnd protocols, and drawing an event time axis below the form time axis;
6.4) converting ABegin and AEnd protocols into ADBegin and ADEnd protocols which plot a behavior timeline below an event timeline;
6.5) existing multiple sets of ADBegin and ADEnd protocols, each set of protocols being drawn next to the lower side of the previous set;
6.6) existing sets of EDBegin and EDEnd protocols, each set of protocols being drawn next to the back of the previous set.
And S40, the mobile terminal queries the behavior record display page, wherein the behavior record display page comprises a form time axis, an event time axis and a behavior time axis.
It should be noted that, an implementer respectively clicks the form timeline, the event timeline, and the behavior timeline on the tracking end, and the three timelines respectively acquire detailed information from the form action storage container for display, for example, the behavior timeline may acquire a corresponding AAtion protocol and convert the AAtion protocol into an ADAtion protocol, and the protocol may draw detailed contents in various forms such as a table on an interface according to different details, and the tracking display end queries a part of the overall interface.
According to the query method provided by the embodiment of the invention, through graphically displaying the log information, an implementer can visually check the log information and the positioning problem through a graphical display interface, the positioning difficulty of the problem is reduced, the troubleshooting efficiency is improved, and the dependence on platform developers is reduced; the context environment information is graphically displayed, the execution effect of the form logic configured by the implementers is truly reflected, and the execution effect is prevented from meeting the business requirement but the execution logic is not executed as designed; through graphical display of historical time lines, implementation can locate errors according to a clue and further assist in solving the problems by context environments in case of errors; meanwhile, the graphical log is attached with command line interaction capability, more log information can be extracted and aggregated according to the result of graphical representation through an auxiliary command line command, and problems can be positioned and analyzed more conveniently.
In a second aspect:
referring to fig. 6, an embodiment of the present invention further provides a system for querying a mobile-end form behavior record, including:
the log user ID constructing unit 01 is used for the mobile terminal to send a login request to a log server, the log server responds and issues a first instruction to the log tracker, and the first instruction is used for constructing a log user ID according to the collected user information of the mobile terminal;
the protocol sending unit 02 is used for the mobile terminal to enter a form page and trigger all event behaviors to enable the form to send a corresponding protocol to the log server; the protocols comprise a PBegin protocol, an EBegin protocol, an ABegin protocol, an AAtion protocol, an AEnd protocol, an EEnd protocol and a PENd protocol;
the display page drawing unit 03 is used for enabling the mobile terminal to enter the tracking display terminal for login verification, sending a log query instruction to the log server when the verification is passed, sending the queried log file and a corresponding protocol to the tracking display terminal by the log server, converting the log file by the tracking display terminal, and drawing a behavior record display page according to a converted result;
and the query unit 04 is used for the mobile terminal to query the behavior record display page, and the behavior record display page comprises a form time axis, an event time axis and a behavior time axis.
Further, the PBegin protocol is used for the tracking end displayer to draw the form time axis; the EBegin protocol is used for the tracking end displayer to draw the form event time axis; the ABegin protocol is used for drawing a form behavior time axis by a tracking end displayer; the AAtion protocol is used for recording form behavior information and context information related to the form behavior; the AEnd protocol is used for the tracing end displayer to finish drawing the form behavior time axis; the EEnd protocol is used for the tracking end displayer to finish drawing the form event time axis; the PEnd protocol is used for the tracking end displayer to finish drawing the form time axis.
According to the query system provided by the embodiment of the invention, through graphically displaying the log information, an implementer can visually check the log information and the positioning problem through a graphical display interface, the positioning difficulty of the problem is reduced, the troubleshooting efficiency is improved, and the dependence on platform developers is reduced; the context environment information is graphically displayed, the execution effect of the form logic configured by the implementers is truly reflected, and the execution effect is prevented from meeting the business requirement but the execution logic is not executed as designed; through graphical display of historical time lines, implementation can locate errors according to a clue and further assist in solving the problems by context environments in case of errors; meanwhile, the graphical log is attached with command line interaction capability, more log information can be extracted and aggregated according to the result of graphical representation through an auxiliary command line command, and problems can be positioned and analyzed more conveniently.
In a third aspect:
an embodiment of the present invention further provides a terminal device, including:
one or more processors;
a memory coupled to the processor for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement a mobile end form behavior record query method as described above.
The processor is used for controlling the overall operation of the terminal equipment so as to complete all or part of the steps of the mobile terminal form behavior record query method. The memory is used to store various types of data to support operation at the terminal device, and these data may include, for example, instructions for any application or method operating on the terminal device, as well as application-related data. The Memory may be implemented by any type of volatile or non-volatile Memory device or combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic Memory, flash Memory, magnetic disk, or optical disk.
The terminal Device may be implemented by one or more Application Specific 1 integrated circuits (AS 1C), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a controller, a microcontroller, a microprocessor, or other electronic components, and is configured to execute the mobile terminal form behavior record query method according to any of the embodiments described above, and achieve technical effects consistent with the methods described above.
An embodiment of the present invention further provides a computer-readable storage medium including program instructions, which when executed by a processor implement the steps of the method for querying a behavior record of a mobile terminal form according to any one of the embodiments described above. For example, the computer-readable storage medium may be the above-mentioned memory including program instructions, and the above-mentioned program instructions may be executed by a processor of a terminal device to implement the method for querying a behavior record of a mobile terminal form according to any of the above-mentioned embodiments, and achieve the technical effects consistent with the above-mentioned method.
While the foregoing is directed to the preferred embodiment of the present invention, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention.
Claims (10)
1. A method for inquiring form behavior records of a mobile terminal is characterized by comprising the following steps:
the mobile terminal sends a login request to a log server, the log server responds and issues a first instruction to a log tracker, and the first instruction is used for constructing a log user ID according to the collected user information of the mobile terminal;
the mobile terminal enters a form page and triggers all event behaviors to enable the form to send a corresponding protocol to the log server; the protocols comprise a PBegin protocol, an EBegin protocol, an ABegin protocol, an AAtion protocol, an AEnd protocol, an EEnd protocol and a PENd protocol;
the mobile terminal enters a tracking display terminal to perform login verification, and when the verification is passed, a log query instruction is sent to the log server, the log server sends a queried log file and a corresponding protocol to the tracking display terminal, and the tracking display terminal converts the log file and draws a behavior record display page according to a converted result;
and the mobile terminal queries the behavior record display page, wherein the behavior record display page comprises a form time axis, an event time axis and a behavior time axis.
2. The mobile terminal form behavior record query method according to claim 1,
the PBegin protocol is used for drawing a form time axis by the tracking end displayer; the EBegin protocol is used for the tracking end displayer to draw the form event time axis; the ABegin protocol is used for drawing a form behavior time axis by a tracking end displayer; the AAtion protocol is used for recording form behavior information and context information related to the form behavior; the AEnd protocol is used for the tracing end displayer to finish drawing the form behavior time axis; the EEnd protocol is used for the tracking end displayer to finish drawing the form event time axis; the PEnd protocol is used for the tracking end displayer to finish drawing the form time axis.
3. The method according to claim 2, wherein the form triggers multiple AAtion protocols when an event action occurs.
4. The mobile end form behavior record query method of claim 2, wherein the form is further configured to trigger the ABegin protocol and the AEnd protocol in a loop until all events and all behaviors are performed.
5. The method as claimed in claim 1, wherein the protocol sent by the form is first passed through a log tracker and then sent to the log server.
6. The method for querying the mobile terminal form behavior record according to claim 1, wherein the constructing a log user ID according to the user information comprises:
acquiring login information and system information of a user; the login information comprises a tenant number, a post number and a login ID; the system information comprises an app version and a mobile terminal system version;
converting the login information and the character string of the system information into a decimal number array, and encrypting by using a public key;
and converting the encrypted key into a character string as a log user ID.
7. A mobile terminal form behavior record query system is characterized by comprising:
the log user ID constructing unit is used for sending a login request to a log server by the mobile terminal, the log server responds and issues a first instruction to the log tracker, and the first instruction is used for constructing a log user ID according to the collected user information of the mobile terminal;
the protocol sending unit is used for the mobile terminal to enter a form page and trigger all event behaviors to enable the form to send a corresponding protocol to the log server; the protocols comprise a PBegin protocol, an EBegin protocol, an ABegin protocol, an AAtion protocol, an AEnd protocol, an EEnd protocol and a PENd protocol;
the display page drawing unit is used for enabling the mobile terminal to enter the tracking display terminal for login verification, sending a log query instruction to the log server when the verification is passed, sending the queried log file and the corresponding protocol to the tracking display terminal by the log server, converting the log file by the tracking display terminal, and drawing a behavior record display page according to the converted result;
and the query unit is used for the mobile terminal to query the behavior record display page, and the behavior record display page comprises a form time axis, an event time axis and a behavior time axis.
8. The mobile end form behavior record query system of claim 7,
the PBegin protocol is used for drawing a form time axis by the tracking end displayer; the EBegin protocol is used for the tracking end displayer to draw the form event time axis; the ABegin protocol is used for drawing a form behavior time axis by a tracking end displayer; the AAtion protocol is used for recording form behavior information and context information related to the form behavior; the AEnd protocol is used for the tracing end displayer to finish drawing the form behavior time axis; the EEnd protocol is used for the tracking end displayer to finish drawing the form event time axis; the PEnd protocol is used for the tracking end displayer to finish drawing the form time axis.
9. A terminal device, comprising:
one or more processors;
a memory coupled to the processor for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the mobile end form behavior record query method of any of claims 1-6.
10. A computer-readable storage medium having stored thereon a computer program, wherein the computer program is executed by a processor to implement the mobile terminal form behavior record query method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110822288.0A CN113282477B (en) | 2021-07-21 | 2021-07-21 | Mobile terminal form behavior record query method, system, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110822288.0A CN113282477B (en) | 2021-07-21 | 2021-07-21 | Mobile terminal form behavior record query method, system, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113282477A true CN113282477A (en) | 2021-08-20 |
| CN113282477B CN113282477B (en) | 2021-11-09 |
Family
ID=77286769
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110822288.0A Active CN113282477B (en) | 2021-07-21 | 2021-07-21 | Mobile terminal form behavior record query method, system, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113282477B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112861053A (en) * | 2021-01-18 | 2021-05-28 | 北京致远互联软件股份有限公司 | Form tracking system of task system call link |
| CN116127226A (en) * | 2022-12-29 | 2023-05-16 | 广州市玄武无线科技股份有限公司 | Page generation method and device based on service form and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101847160A (en) * | 2010-05-19 | 2010-09-29 | 深圳市五巨科技有限公司 | Method and device for pushing personalized pages to mobile terminal |
| CN104410649A (en) * | 2014-12-23 | 2015-03-11 | 合一网络技术(北京)有限公司 | Cross-screen synchronous logging method based on identity code |
| CN110717119A (en) * | 2019-10-10 | 2020-01-21 | 北京字节跳动网络技术有限公司 | Page jump method and device, electronic equipment and storage medium |
| US20200183901A1 (en) * | 2014-04-11 | 2020-06-11 | Douglas T. Migliori | No-Code, Event-Driven Edge Computing Platform |
| CN112905943A (en) * | 2020-12-09 | 2021-06-04 | 广州市玄武无线科技股份有限公司 | Dynamic chart display method and system based on mobile terminal |
-
2021
- 2021-07-21 CN CN202110822288.0A patent/CN113282477B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101847160A (en) * | 2010-05-19 | 2010-09-29 | 深圳市五巨科技有限公司 | Method and device for pushing personalized pages to mobile terminal |
| US20200183901A1 (en) * | 2014-04-11 | 2020-06-11 | Douglas T. Migliori | No-Code, Event-Driven Edge Computing Platform |
| CN104410649A (en) * | 2014-12-23 | 2015-03-11 | 合一网络技术(北京)有限公司 | Cross-screen synchronous logging method based on identity code |
| CN110717119A (en) * | 2019-10-10 | 2020-01-21 | 北京字节跳动网络技术有限公司 | Page jump method and device, electronic equipment and storage medium |
| CN112905943A (en) * | 2020-12-09 | 2021-06-04 | 广州市玄武无线科技股份有限公司 | Dynamic chart display method and system based on mobile terminal |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112861053A (en) * | 2021-01-18 | 2021-05-28 | 北京致远互联软件股份有限公司 | Form tracking system of task system call link |
| CN116127226A (en) * | 2022-12-29 | 2023-05-16 | 广州市玄武无线科技股份有限公司 | Page generation method and device based on service form and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113282477B (en) | 2021-11-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113282477B (en) | Mobile terminal form behavior record query method, system, equipment and storage medium | |
| US20090164979A1 (en) | System landscape trace | |
| US8234633B2 (en) | Incident simulation support environment and business objects associated with the incident | |
| CN111832236B (en) | Chip regression testing method and system, electronic equipment and storage medium | |
| US8443340B2 (en) | Execution capture and replay based debugging | |
| CN107102947B (en) | ATM transaction flow testing device and method | |
| US10565089B2 (en) | Identification of code features potentially associated with code behavior | |
| CN109815119B (en) | APP link channel testing method and device | |
| US9454463B2 (en) | Rapid automation front-end framework library and executable graphic user interface testing system and method | |
| CN108509344B (en) | Daily cutting batch test method, equipment and readable storage medium | |
| US11436133B2 (en) | Comparable user interface object identifications | |
| JP2017539031A (en) | Separation of test verification from test execution | |
| CN115422063A (en) | Low-code interface automation system, electronic equipment and storage medium | |
| CN114880240A (en) | Automatic testing system and method for Internet of things equipment, storage medium and equipment | |
| CN106980638B (en) | Operation record system, method and operation object change information query method | |
| CN113296653B (en) | Simulation interaction model construction method, interaction method and related equipment | |
| CN114840410A (en) | Test analysis method and device, computer equipment and storage medium | |
| CN115757175A (en) | Transaction log file processing method and device | |
| CN111400173B (en) | VTS test method, device and equipment | |
| CN109660587A (en) | Data push method, device, storage medium and server based on random number | |
| Marra | A live debugging approach for big data processing applications | |
| CN114297961A (en) | Chip test case processing method and related device | |
| CN113515455A (en) | Automatic test method and system | |
| CN113326193A (en) | Applet testing method and device | |
| CN111931465A (en) | Method and system for automatically generating user manual based on user operation |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP02 | Change in the address of a patent holder |
Address after: 510000 room 23bd, No. 109, TIYU West Road, Tianhe District, Guangzhou City, Guangdong Province Patentee after: GUANGZHOU XUANWU WIRELESS TECHNOLOGY Co.,Ltd. Address before: 32B, no.103b, TianLiHe Road, Guangzhou, 510000 Patentee before: GUANGZHOU XUANWU WIRELESS TECHNOLOGY Co.,Ltd. |
|
| CP02 | Change in the address of a patent holder |