WO2021012741A1 - 基于经验库的异常前端操作提醒的方法及相关设备 - Google Patents
基于经验库的异常前端操作提醒的方法及相关设备 Download PDFInfo
- Publication number
- WO2021012741A1 WO2021012741A1 PCT/CN2020/087468 CN2020087468W WO2021012741A1 WO 2021012741 A1 WO2021012741 A1 WO 2021012741A1 CN 2020087468 W CN2020087468 W CN 2020087468W WO 2021012741 A1 WO2021012741 A1 WO 2021012741A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- abnormal
- feedback
- end operation
- basic
- operations
- Prior art date
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/3438—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 monitoring of user actions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/903—Querying
- G06F16/90335—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/90—Details of database functions independent of the retrieved data types
- G06F16/903—Querying
- G06F16/9038—Presentation of query results
Definitions
- This application relates to the field of detection models, and in particular to a method and related equipment for reminding abnormal front-end operations based on an experience database.
- this application provides a method and related equipment for reminding abnormal front-end operations based on an experience database.
- the first aspect provides a method for reminding abnormal front-end operations based on an experience database, including:
- the preset feedback table describes whether each back-end feedback is abnormal back-end feedback and the corresponding Exception type
- the back-end feedback is abnormal back-end feedback
- determine the abnormal type of the abnormal back-end feedback based on the preset feedback table, and determine the front-end operation as the abnormal front-end operation in the scenario
- a device for reminding abnormal front-end operations based on an experience database including:
- the establishment module is used to establish an experience database, which contains basic front-end operations corresponding to each scene;
- the first determination module is configured to determine the scene corresponding to the front-end operation in response to the front-end operation performed by the user terminal, and monitor the front-end operation and the corresponding back-end feedback;
- the second determining module is configured to determine whether the back-end feedback is abnormal based on the comparison between the back-end feedback and a preset feedback table, and the preset feedback table describes whether each back-end feedback is abnormal back-end feedback, and The type of abnormality corresponding to the back-end feedback of each abnormality;
- the third determining module is configured to, if the back-end feedback is abnormal back-end feedback, determine the abnormal type of the abnormal back-end feedback based on the preset feedback table, and determine that the front-end operation is the situation Abnormal front-end operation;
- An extraction module for extracting basic front-end operations corresponding to the scene from the experience database
- a fourth determining module configured to compare the abnormal front-end operation with each of the basic front-end operations based on the abnormal type, and determine the abnormal problem corresponding to the abnormal front-end operation;
- the sending module is used to send reminder information for the abnormal front-end operation to the user terminal.
- an electronic device for reminding abnormal front-end operations based on an experience database including:
- Memory configured to store executable instructions
- the processor is configured to execute executable instructions stored in the memory to implement a method for reminding abnormal front-end operations based on an experience library:
- the method for reminding abnormal front-end operation based on experience database includes:
- the preset feedback table describes whether each back-end feedback is abnormal back-end feedback and the corresponding Exception type
- the back-end feedback is abnormal back-end feedback
- determine the abnormal type of the abnormal back-end feedback based on the preset feedback table, and determine the front-end operation as the abnormal front-end operation in the scenario
- a computer-readable storage medium which stores computer program instructions, when the computer instructions are executed by the computer, the computer executes a method for reminding abnormal front-end operations based on an experience database:
- the method for reminding abnormal front-end operation based on experience database includes:
- the preset feedback table describes whether each back-end feedback is abnormal back-end feedback and the corresponding Exception type
- the back-end feedback is abnormal back-end feedback
- determine the abnormal type of the abnormal back-end feedback based on the preset feedback table, and determine the front-end operation as the abnormal front-end operation in the scenario
- the embodiment of this application establishes an experience database that stores basic front-end operations in each scenario, and while monitoring the front-end operations of the user terminal, the front-end operations that have not caused abnormal back-end feedback are used as a basis for the corresponding scenarios.
- the front-end operations are stored in the experience database to enrich the "experience" of the basic front-end operations of the experience database; for abnormal front-end operations that cause abnormal back-end feedback, store them and the corresponding abnormal problems into the corresponding scenarios in the experience database , Enabling the experience database to obtain "experience" on abnormal front-end operations. Therefore, when the system monitors the front-end operation of the user terminal, it first matches it with the record of abnormal front-end operation in the experience database.
- the front-end operation of the user terminal is an abnormal front-end operation
- it can immediately remind the user terminal to save it.
- the system back-end response process to the abnormal front-end operation is improved, and the efficiency of the abnormal front-end operation reminder is improved.
- Fig. 1 shows a flowchart of an abnormal front-end operation reminder based on an experience database according to an exemplary embodiment of the present application.
- Fig. 2 shows a block diagram of a device for reminding abnormal front-end operations based on an experience database according to an exemplary embodiment of the present application.
- FIG. 3 shows a detailed flow chart of determining a scene corresponding to the front-end operation in response to a front-end operation performed by a user terminal according to an exemplary embodiment of the present application, and monitoring the front-end operation and the corresponding back-end feedback.
- Fig. 4 shows a detailed flowchart of comparing the abnormal front-end operation with each of the basic front-end operations based on the abnormal type according to an exemplary embodiment of the present application to determine the abnormal problem corresponding to the abnormal front-end operation.
- Fig. 5 shows a system architecture diagram of an abnormal front-end operation reminder based on an experience database according to an exemplary embodiment of the present application.
- Fig. 6 shows a diagram of an electronic device for reminding an abnormal front-end operation based on an experience database according to an exemplary embodiment of the present application.
- Fig. 7 shows a computer-readable storage medium diagram of an abnormal front-end operation reminder based on an experience database according to an exemplary embodiment of the present application.
- Fig. 1 shows a flowchart of an abnormal front-end operation reminder based on an experience database according to an exemplary embodiment of the present application:
- Step S100 Establish an experience database, which includes basic front-end operations corresponding to each scene;
- Step S110 In response to the front-end operation performed by the user terminal, determine the scene corresponding to the front-end operation, and monitor the front-end operation and the corresponding back-end feedback;
- Step S120 Determine whether the back-end feedback is abnormal based on the comparison between the back-end feedback and a preset feedback table, and the preset feedback table describes whether each back-end feedback is abnormal back-end feedback and each abnormal back-end Feedback the corresponding abnormal type;
- Step S130 if the back-end feedback is abnormal back-end feedback, determine the abnormal type of the abnormal back-end feedback based on the preset feedback table, and determine the front-end operation as the abnormal front-end operation in the scenario;
- Step S140 Extract each basic front-end operation corresponding to the scene from the experience database
- Step S150 Based on the abnormal type, the abnormal front-end operation is compared with each of the basic front-end operations to determine the abnormal problem corresponding to the abnormal front-end operation;
- Step S160 Send reminder information for the abnormal front-end operation to the user terminal.
- step S100 an experience database is established, which includes basic front-end operations corresponding to each scene.
- the experience database refers to a database that stores various front-end operation records, so that the system can summarize and learn from it.
- Scenario refers to the scenario where a specific business is performed in the system, which usually depends on the existence of the page.
- the scene corresponding to the login page is the login scene.
- Basic front-end operations refer to front-end operations performed by the user terminal in a corresponding scenario that meet the predetermined rules of the scenario. That is, the basic front-end operation is the standard and correct front-end operation in the corresponding scenario.
- the system stores the basic front-end operations corresponding to each scene into the experience database, where the front-end operations can be independent operation steps or a set of sequence of operation steps; the basic front-end operations corresponding to each scene can be A single basic front-end operation can also be multiple basic front-end operations.
- the front-end operations can be independent operation steps or a set of sequence of operation steps; the basic front-end operations corresponding to each scene can be A single basic front-end operation can also be multiple basic front-end operations.
- a basic front-end operation stored in this scenario: "Enter a user name consisting of 4 characters -> enter a password -> enter a verification code -> click the'login' button”
- another A basic front-end operation "Enter the email address that meets the format requirements -> enter the password -> enter the verification code -> click the'login' button”.
- the advantage of this embodiment is that by establishing an experience database storing basic front-end operations, each basic front-end operation can be referenced by the system, so that the system can accumulate experience related to front-end operations based on the experience database.
- the following describes the process of monitoring related processes in response to front-end operations performed by the user terminal.
- step S110 in response to a front-end operation performed by the user terminal, a scene corresponding to the front-end operation is determined, and the front-end operation and the corresponding back-end feedback are monitored.
- Back-end feedback refers to the corresponding feedback generated by the system in the back-end in response to front-end operations.
- the user terminal When the user terminal performs front-end operations at the front end of the system, it will trigger the system to monitor related processes.
- the system will determine the current scene based on the front-end operation, and while monitoring the front-end operation, it will also monitor the corresponding back-end feedback in the scene.
- step S110 includes:
- Step S1101 Determine a scene corresponding to the front-end operation based on the current page where the user terminal is located;
- Step S1102 Monitor the front-end operation and the corresponding back-end feedback.
- the system determines the scene corresponding to the front-end operation according to the current page where the user terminal is located. For example, if the current page where the user terminal performs the front-end operation is the login page, the scene corresponding to the front-end operation is the login scene. The system monitors the front-end operation and the corresponding back-end feedback in this scenario.
- the advantage of this implementation is that the monitored front-end operations and corresponding back-end feedback are bound to the scene, so that it can be used as a part of the experience library to enrich the content of the experience library.
- the monitoring of the front-end operation and the corresponding back-end feedback includes:
- the back-end feedback is monitored and process recorded.
- Page embedding refers to embedding a script on the page, and the script automatically monitors and records the activities on the page.
- the system embeds points in the pages corresponding to each scene in advance, so that when the user terminal performs front-end operations, the script will automatically trigger the monitoring and process recording of the front-end operations. At the same time, the system monitors and records the corresponding back-end feedback by monitoring the back-end interface.
- step S120 it is determined whether the back-end feedback is abnormal based on the comparison between the back-end feedback and a preset feedback table, and the preset feedback table describes whether each back-end feedback is abnormal back-end feedback and each abnormality.
- the back-end feedback corresponding abnormal type.
- the feedback table preset in the system describes whether various back-end feedbacks are abnormal back-end feedbacks, and the abnormal type corresponding to each abnormal back-end feedback.
- the feedback form is described in header 1: back-end feedback "TRUE” is non-abnormal back-end feedback; in header 2: back-end feedback “XXXL” is abnormal back-end feedback, and its abnormal type is "input format” Abnormal”; described in the header 3: Back-end feedback "10774" is an abnormal back-end feedback, and its abnormal type is "abnormal operation sequence”...
- the system compares the monitored back-end feedback with the preset feedback table to determine whether the back-end feedback is abnormal back-end feedback, and if the back-end feedback is abnormal back-end feedback, the abnormal The back-end feedback corresponding abnormal type.
- the advantage of this embodiment is that it can quickly determine whether the back-end feedback is abnormal or not through the preset feedback table.
- the method includes:
- the corresponding front-end operation is determined to be a basic front-end operation of the scene and recorded in the experience database.
- the basic front-end operations contained therein describe the correct front-end operations in the corresponding scenario.
- the correct front-end operations in the same scenario may have various forms, the basic front-end operations included in the initial establishment of the experience database are only a single example for reference, and may not cover all the correct front-end operations in this scenario. Therefore, in the actual monitoring and process recording process, the front-end operation that does not cause abnormal back-end feedback is recorded in the experience database as a basic front-end operation in the scenario to enrich the information in the experience database.
- the advantage of this embodiment is that as the monitoring of the front-end operation and the back-end feedback is carried out, the information of various basic front-end operations in each scene stored in the experience database is continuously enriched.
- step S130 if the back-end feedback is abnormal back-end feedback, determine the abnormal type of the abnormal back-end feedback based on the preset feedback table, and determine the front-end operation as the abnormal front-end in the scenario operating.
- the system when the system monitors the front-end operation performed by the user terminal and the corresponding back-end feedback, it determines that the back-end feedback is abnormal back-end feedback.
- the system determines the abnormal type of the abnormal back-end feedback according to the preset feedback table, and determines the front-end operation as the abnormal front-end operation. In order to perform follow-up processing based on the abnormal front-end operation, so as to remind the user terminal.
- step S140 each basic front-end operation corresponding to the scene is extracted from the experience database.
- the system needs to extract the basic front-end operations in the scenario from the experience database as a reference, so as to be able to determine the abnormal problems in the abnormal front-end operations.
- the system can determine the current scene based on the abnormal front-end operation, and extract the basic front-end operations in the scene from the experience database.
- the following describes the process of determining abnormal problems in abnormal front-end operations by taking each of the basic front-end operations as a reference.
- step S150 based on the abnormal type, the abnormal front-end operation is compared with each of the basic front-end operations to determine the abnormal problem corresponding to the abnormal front-end operation.
- An abnormal problem refers to a problem in an abnormal front-end operation that causes an abnormal back-end feedback operation step.
- the system preliminarily determines the scope of the abnormal problem based on the abnormal type fed back from the abnormal backend. Furthermore, the abnormal front-end operation is compared with each base-level front-end operation in the scene within the range, so as to find out the abnormal problem corresponding to the abnormal front-end operation.
- the advantage of this embodiment is that the abnormal problem corresponding to the abnormal front-end operation is determined, so that when the abnormal front-end operation is monitored again in the future, the user terminal can be reminded of the abnormal problem, so that the user terminal can identify the specific abnormal problem and improve The efficiency of subsequent correction of abnormal problems by the user terminal.
- step S150 includes:
- Step S1501 Determine an operation step to be compared based on the abnormal type
- Step S1502 Compare the abnormal front-end operation with each of the basic front-end operations on the operation steps to be compared, and determine the attributes that are different from each of the basic front-end operations;
- Step S1503 Determine the uniformly different attributes as the abnormal problem.
- the basic front-end operations stored in the experience database are correct operation steps that will not cause abnormal back-end feedback in each operation step. Therefore, by comparing the abnormal front-end operation with the basic front-end operation in each corresponding operation step, the abnormal problem can be determined.
- the system determines the operation steps to be compared according to the abnormal type corresponding to the abnormal front-end operation. For example, if the exception type is "input format exception", it can be determined, and the operation step to be compared is a step involving input. Therefore, the system compares the input format of the abnormal front-end operation with the basic front-end operations in the scenario in steps involving input. By comparison, the system found that the information input in the "ID Card Information Input Item" of each basic front-end operation is 18 characters, while the information input in the "ID Card Information Input Item" of the abnormal front-end operation is 17 characters. It is different from the basic front-end operations. As a result, the system can determine that the abnormal problem is "input error of ID card information".
- the advantage of this embodiment is that the abnormal problem is made more specific by comparing the specific operation steps.
- the abnormality type is determined as the corresponding abnormality problem.
- the abnormal type is regarded as the abnormal problem. For example, if the exception type is "abnormal input format", the abnormal problem is "abnormal input format”.
- the advantage of this embodiment is that the abnormal type is directly determined as the abnormal problem, which improves the efficiency and applicability of determining the abnormal problem.
- the method includes:
- the scenario, the abnormal front-end operation, and the abnormal problem are entered into the experience database, so that when the abnormal front-end operation in the scenario is monitored again, the user terminal is reminded of the corresponding abnormal problem.
- the system records the abnormal front-end operation and the corresponding abnormal problem into the corresponding scenario in the experience database.
- the corresponding abnormal problem can be immediately sent to the user terminal as a reminder.
- the advantage of this embodiment is that the abnormal problem is entered into the experience database, so that when the corresponding abnormal front-end operation is monitored again, there is no need to perform the comparison between the abnormal front-end operation and the basic front-end operations, and the process of determining the abnormal problem immediately Reminding the user terminal improves the reminding efficiency.
- step S160 a reminder message for the abnormal front-end operation is sent to the user terminal.
- the corresponding reminder information is sent to the user terminal, so that the user terminal corrects the front-end operation according to the reminder information.
- the method includes:
- the system records the process based on the monitoring of abnormal front-end operations and the corresponding abnormal back-end feedback, and then generates a problem report that can show the abnormal front-end operation process and the corresponding abnormal back-end feedback.
- the report is sent to the receiving terminal of the problem report.
- the advantage of this embodiment is that the generated problem report can more vividly show the abnormal front-end operation process and the corresponding abnormal back-end feedback, so that the problem report receiving terminal can more accurately determine the abnormal problem.
- the problem report may be in the form of a report or a flowchart.
- the problem report receiving terminal may be a management terminal or a user terminal.
- a device for reminding abnormal front-end operations based on an experience database which specifically includes:
- the establishment module 210 is used to establish an experience database, which includes basic front-end operations corresponding to each scene;
- the first determining module 220 is configured to determine the scene corresponding to the front-end operation in response to the front-end operation performed by the user terminal, and to monitor the front-end operation and the corresponding back-end feedback;
- the second determining module 230 is configured to determine whether the back-end feedback is abnormal based on the comparison between the back-end feedback and a preset feedback table, and the preset feedback table describes whether each back-end feedback is abnormal back-end feedback, And the abnormal type corresponding to each abnormal back-end feedback;
- the third determining module 240 is configured to, if the back-end feedback is abnormal back-end feedback, determine the abnormal type of the abnormal back-end feedback based on the preset feedback table, and determine that the front-end operation is in the scenario Abnormal front-end operation;
- the extraction module 250 is configured to extract the basic front-end operations corresponding to the scene from the experience database;
- the fourth determining module 260 is configured to compare the abnormal front-end operation with each of the basic front-end operations based on the abnormal type, and determine the abnormal problem corresponding to the abnormal front-end operation;
- the sending module 270 is configured to send reminder information for the abnormal front-end operation to the user terminal.
- the exemplary embodiments described herein can be implemented by software, or can be implemented by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (can be a CD-ROM, U disk, mobile hard disk, etc.) or on the network , Including several instructions to make a computing device (which may be a personal computer, server, mobile terminal, or network device, etc.) execute the method according to the embodiment of the present application.
- a non-volatile storage medium can be a CD-ROM, U disk, mobile hard disk, etc.
- Including several instructions to make a computing device which may be a personal computer, server, mobile terminal, or network device, etc.
- Fig. 5 shows a system architecture diagram of an abnormal front-end operation reminder based on an experience database according to an exemplary embodiment of the present application.
- the system architecture includes: a user terminal 310, a system 320, and an experience database 330.
- the system 320 establishes an experience database 330, and the experience database 330 stores basic front-end operations corresponding to each scene.
- the system 320 determines the scene corresponding to the front-end operation, and monitors the front-end operation and the corresponding back-end feedback; the system 320 combines the back-end feedback with the preset feedback Compare the table to determine whether the back-end feedback is abnormal back-end feedback. If the back-end feedback is an abnormal back-end feedback, the abnormal type is determined based on the predetermined feedback table, and the front-end operation is determined to be an abnormal front-end operation.
- the abnormal front-end operation is compared with the basic front-end operation in the scenario extracted from the experience database, the abnormal problem of the abnormal front-end operation is determined, and the user terminal 310 is reminded.
- system architecture described here can realize the functions of each module in the device for reminding abnormal front-end operations based on the experience database shown in FIG. 2.
- the electronic device 400 according to this embodiment of the present application will be described below with reference to FIG. 6.
- the electronic device 400 shown in FIG. 6 is only an example, and should not bring any limitation to the function and use scope of the embodiments of the present application.
- the electronic device 400 takes the form of a general-purpose computing device.
- the components of the electronic device 400 may include but are not limited to: the aforementioned at least one processing unit 410, the aforementioned at least one storage unit 420, and a bus 430 connecting different system components (including the storage unit 420 and the processing unit 410).
- the storage unit stores program code, and the program code can be executed by the processing unit 410, so that the processing unit 410 executes the various exemplary methods described in the "Exemplary Method" section of this specification. Implementation steps.
- the processing unit 410 may perform step S100 as shown in FIG.
- step S110 determine the front-end operations performed by the user terminal The scene corresponding to the front-end operation, and monitor the front-end operation and the corresponding back-end feedback
- step S120 determine whether the back-end feedback is abnormal based on the comparison between the back-end feedback and the preset feedback table, the The preset feedback table describes whether each back-end feedback is abnormal back-end feedback, and the abnormal type corresponding to each abnormal back-end feedback
- step S130 if the back-end feedback is abnormal back-end feedback, based on the preset feedback table Determine the abnormal type of the abnormal back-end feedback, and determine the front-end operation as the abnormal front-end operation in the scenario
- step S140 extract each basic front-end operation corresponding to the scenario from the experience database
- step S150 Based on the abnormal type, compare the abnormal front-end operation with each of the basic front-end operations to determine the abnormal problem corresponding to the abnormal front-end operation
- step S160 send the abnormal front-end
- the storage unit 420 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 4201 and/or a cache storage unit 4202, and may further include a read-only storage unit (ROM) 4203.
- RAM random access storage unit
- ROM read-only storage unit
- the storage unit 420 may also include a program/utility tool 4204 having a set of (at least one) program module 4205.
- program module 4205 includes but is not limited to: an operating system, one or more application programs, other program modules, and program data, Each of these examples or some combination may include the implementation of a network environment.
- the bus 430 may represent one or more of several types of bus structures, including a storage unit bus or a storage unit controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local area using any bus structure among multiple bus structures. bus.
- the electronic device 400 can also communicate with one or more external devices 500 (such as keyboards, pointing devices, Bluetooth devices, etc.), and can also communicate with one or more devices that enable a user to interact with the electronic device 400, and/or communicate with Any device (such as a router, modem, etc.) that enables the electronic device 400 to communicate with one or more other computing devices. This communication can be performed through an input/output (I/O) interface 450.
- the electronic device 400 may also communicate with one or more networks (for example, a local area network (LAN), a wide area network (WAN), and/or a public network, such as the Internet) through the network adapter 460.
- networks for example, a local area network (LAN), a wide area network (WAN), and/or a public network, such as the Internet
- the network adapter 460 communicates with other modules of the electronic device 400 through the bus 430. It should be understood that although not shown in the figure, other hardware and/or software modules can be used in conjunction with the electronic device 400, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives And data backup storage system, etc.
- the exemplary embodiments described herein can be implemented by software, or can be implemented by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (can be a CD-ROM, U disk, mobile hard disk, etc.) or on the network , Including several instructions to make a computing device (which may be a personal computer, server, terminal device, or network device, etc.) execute the method according to the embodiment of the present application.
- a non-volatile storage medium can be a CD-ROM, U disk, mobile hard disk, etc.
- Including several instructions to make a computing device which may be a personal computer, server, terminal device, or network device, etc.
- a computer-readable storage medium is also provided.
- the storage medium is a volatile storage medium or a non-volatile storage medium.
- Program product In some possible implementation manners, various aspects of the present application can also be implemented in the form of a program product, which includes program code. When the program product runs on a terminal device, the program code is used to enable the The terminal device executes the steps according to various exemplary embodiments of the present application described in the above-mentioned "Exemplary Method" section of this specification.
- a program product 600 for implementing the above method according to an embodiment of the present application is described. It can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be installed in a terminal device, For example, running on a personal computer.
- CD-ROM compact disk read-only memory
- the program product of this application is not limited to this.
- the readable storage medium can be any tangible medium that contains or stores a program, and the program can be used by or combined with an instruction execution system, device, or device.
- the program product can use any combination of one or more readable media.
- the readable medium may be a readable signal medium or a readable storage medium.
- the readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or a combination of any of the above. More specific examples (non-exhaustive list) of readable storage media include: electrical connections with one or more wires, portable disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Type programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.
- the computer-readable signal medium may include a data signal propagated in baseband or as a part of a carrier wave, and readable program code is carried therein. This propagated data signal can take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
- the readable signal medium may also be any readable medium other than a readable storage medium, and the readable medium may send, propagate, or transmit a program for use by or in combination with the instruction execution system, apparatus, or device.
- the program code contained on the readable medium can be transmitted by any suitable medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.
- the program code used to perform the operations of this application can be written in any combination of one or more programming languages.
- the programming languages include object-oriented programming languages-such as Java, C++, etc., as well as conventional procedural programming languages. Programming language-such as "C" language or similar programming language.
- the program code can be executed entirely on the user's computing device, partly on the user's device, executed as an independent software package, partly on the user's computing device and partly executed on the remote computing device, or entirely on the remote computing device or server Executed on.
- the remote computing device can be connected to a user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using Internet service providers) Business to connect via the Internet).
- LAN local area network
- WAN wide area network
- Internet service providers Internet service providers
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Data Mining & Analysis (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Information Transfer Between Computers (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
本申请公开了一种基于经验库的异常前端操作提醒的方法及相关设备，涉及检测模型领域，该方法包括：建立经验库；确定前端操作对应的场景，并对所述前端操作、及对应的后端反馈进行监测；基于所述后端反馈与预设反馈表的对比，确定所述后端反馈是否异常；若所述后端反馈为异常后端反馈，基于所述预设反馈表确定所述异常后端反馈的异常类型，并将所述前端操作确定为所述场景下的异常前端操作；从所述经验库中提取出所述场景对应的各基础前端操作；基于所述异常类型，将所述异常前端操作与各所述基础前端操作进行对比，确定所述异常前端操作对应的异常问题；向所述用户终端
Description
本申请要求于2019年07月24日提交中国专利局、申请号为201910671339.7，发明名称为“基于经验库的异常前端操作提醒的方法及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
本申请涉及检测模型领域，特别是涉及一种基于经验库的异常前端操作提醒的方法及相关设备。
在互联网技术高速发展的今天，各种服务于用户的系统每天都要处理大量用户于系统前端进行的各类操作。很多时候，出于各种原因，用户会作出不符合规范的异常前端操作，从而导致系统功能无法正常使用。在现有技术中，系统是在后端接口对前端操作作出反馈之后，才会根据后端反馈的内容判断该前端操作是否异常，再进一步对用户进行相应的提醒。发明人意识到，在很多情况下，用户进行的许多异常前端操作是重复的，例如，每天都会许多用户在进行登录操作时，输入错误格式的身份证信息。即使是重复接收过的异常前端操作，系统也只能在确实得到相应的后端反馈后才能向用户进行提醒，效率低下。
发明概述
问题的解决方案
基于此，为解决相关技术中如何从技术层面上更加高效地对异常前端操作进行提醒所面临的技术问题，本申请提供了一种基于经验库的异常前端操作提醒的方法及相关设备。
第一方面，提供了一种基于经验库的异常前端操作提醒的方法，包括：
建立经验库，所述经验库包含各场景对应的基础前端操作；
响应于用户终端进行的前端操作，确定所述前端操作对应的场景，并对所述前 端操作、及对应的后端反馈进行监测；
基于所述后端反馈与预设反馈表的对比，确定所述后端反馈是否异常，所述预设反馈表描述了各后端反馈是否为异常后端反馈、及各异常后端反馈对应的异常类型；
若所述后端反馈为异常后端反馈，基于所述预设反馈表确定所述异常后端反馈的异常类型，并将所述前端操作确定为所述场景下的异常前端操作；
从所述经验库中提取出所述场景对应的各基础前端操作；
基于所述异常类型，将所述异常前端操作与各所述基础前端操作进行对比，确定所述异常前端操作对应的异常问题；
向所述用户终端发送对所述异常前端操作的提醒信息。
根据本申请的第二方面，提供了一种基于经验库的异常前端操作提醒的装置，包括：
建立模块，用于建立经验库，所述经验库包含各场景对应的基础前端操作；
第一确定模块，用于响应于用户终端进行的前端操作，确定所述前端操作对应的场景，并对所述前端操作、及对应的后端反馈进行监测；
第二确定模块，用于基于所述后端反馈与预设反馈表的对比，确定所述后端反馈是否异常，所述预设反馈表描述了各后端反馈是否为异常后端反馈、及各异常后端反馈对应的异常类型；
第三确定模块，用于若所述后端反馈为异常后端反馈，基于所述预设反馈表确定所述异常后端反馈的异常类型，并将所述前端操作确定为所述场景下的异常前端操作；
提取模块，用于从所述经验库中提取出所述场景对应的各基础前端操作；
第四确定模块，用于基于所述异常类型，将所述异常前端操作与各所述基础前端操作进行对比，确定所述异常前端操作对应的异常问题；
发送模块，用于向所述用户终端发送对所述异常前端操作的提醒信息。
根据本申请的第三方面，提供了一种基于经验库的异常前端操作提醒的电子设备，包括：
存储器，配置为存储可执行指令；
处理器，配置为执行存储器中存储的可执行指令，以实现一种基于经验库的异常前端操作提醒的方法：
其中，所述基于经验库的异常前端操作提醒的方法包括：
建立经验库，所述经验库包含各场景对应的基础前端操作；
响应于用户终端进行的前端操作，确定所述前端操作对应的场景，并对所述前端操作、及对应的后端反馈进行监测；
基于所述后端反馈与预设反馈表的对比，确定所述后端反馈是否异常，所述预设反馈表描述了各后端反馈是否为异常后端反馈、及各异常后端反馈对应的异常类型；
若所述后端反馈为异常后端反馈，基于所述预设反馈表确定所述异常后端反馈的异常类型，并将所述前端操作确定为所述场景下的异常前端操作；
从所述经验库中提取出所述场景对应的各基础前端操作；
基于所述异常类型，将所述异常前端操作与各所述基础前端操作进行对比，确定所述异常前端操作对应的异常问题；
向所述用户终端发送对所述异常前端操作的提醒信息。
根据本申请的第四方面，提供一种计算机可读存储介质，其存储有计算机程序指令，当所述计算机指令被计算机执行时，使计算机执行一种基于经验库的异常前端操作提醒的方法：
其中，所述基于经验库的异常前端操作提醒的方法包括：
建立经验库，所述经验库包含各场景对应的基础前端操作；
响应于用户终端进行的前端操作，确定所述前端操作对应的场景，并对所述前端操作、及对应的后端反馈进行监测；
基于所述后端反馈与预设反馈表的对比，确定所述后端反馈是否异常，所述预设反馈表描述了各后端反馈是否为异常后端反馈、及各异常后端反馈对应的异常类型；
若所述后端反馈为异常后端反馈，基于所述预设反馈表确定所述异常后端反馈的异常类型，并将所述前端操作确定为所述场景下的异常前端操作；
从所述经验库中提取出所述场景对应的各基础前端操作；
基于所述异常类型，将所述异常前端操作与各所述基础前端操作进行对比，确定所述异常前端操作对应的异常问题；
向所述用户终端发送对所述异常前端操作的提醒信息。
本申请的实施例通过建立一存储着各场景下基础前端操作的经验库，在监测用户终端的前端操作的同时，对未引起异常后端反馈的前端操作，将其作为对应场景下的一基础前端操作存储进经验库中，对该经验库关于基础前端操作的“经验”进行丰富；对引起异常后端反馈的异常前端操作，将其及对应的异常问题存储进经验库中的对应场景下，使得该经验库获取关于异常前端操作的“经验”。从而使得系统在监测用户终端的前端操作时，先将其与经验库中关于异常前端操作的记录进行匹配，一旦确定用户终端的前端操作为异常前端操作，可立即对用户终端进行提醒，省去了系统后端对该异常前端操作的响应过程，提高了异常前端操作提醒的效率。
本申请的其他特性和优点将通过下面的详细描述变得显然，或部分地通过本申请的实践而习得。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性的，并不能限制本申请。
发明的有益效果
对附图的简要说明
图1示出根据本申请一示例实施方式的基于经验库的异常前端操作提醒的流程图。
图2示出根据本申请一示例实施方式的基于经验库的异常前端操作提醒的装置方框图。
图3示出根据本申请一示例实施方式的响应于用户终端进行的前端操作，确定所述前端操作对应的场景，并对所述前端操作、及对应的后端反馈进行监测的详细流程图。
图4示出根据本申请一示例实施方式的基于所述异常类型，将所述异常前端操作与各所述基础前端操作进行对比，确定所述异常前端操作对应的异常问题的 详细流程图。
图5示出根据本申请一示例实施方式的基于经验库的异常前端操作提醒的系统架构图。
图6示出根据本申请一示例实施方式的基于经验库的异常前端操作提醒的电子设备图。
图7示出根据本申请一示例实施方式的基于经验库的异常前端操作提醒的计算机可读存储介质图。
发明实施例
图1示出根据本申请一示例实施方式的基于经验库的异常前端操作提醒的流程图：
步骤S100：建立经验库，所述经验库包含各场景对应的基础前端操作；
步骤S110：响应于用户终端进行的前端操作，确定所述前端操作对应的场景，并对所述前端操作、及对应的后端反馈进行监测；
步骤S120：基于所述后端反馈与预设反馈表的对比，确定所述后端反馈是否异常，所述预设反馈表描述了各后端反馈是否为异常后端反馈、及各异常后端反馈对应的异常类型；
步骤S130：若所述后端反馈为异常后端反馈，基于所述预设反馈表确定所述异常后端反馈的异常类型，并将所述前端操作确定为所述场景下的异常前端操作；
步骤S140：从所述经验库中提取出所述场景对应的各基础前端操作；
步骤S150：基于所述异常类型，将所述异常前端操作与各所述基础前端操作进行对比，确定所述异常前端操作对应的异常问题；
步骤S160：向所述用户终端发送对所述异常前端操作的提醒信息。
下面，将结合附图对本示例实施方式中上述基于经验库的异常前端操作提醒的各步骤进行详细的解释以及说明。
首先描述建立经验库的过程。
在步骤S100中，建立经验库，所述经验库包含各场景对应的基础前端操作。
经验库是指存储着各种前端操作记录的数据库，使得系统可以从中总结、学习经验。
场景是指系统中进行特定业务的场景，通常依托于页面存在。例如，登录页面对应的场景即为登录场景。
基础前端操作是指在对应场景下，用户终端所进行的符合该场景预定规则的前端操作。即，基础前端操作为对应场景下标准的、正确的前端操作。
在一实施例中，系统将各场景对应的基础前端操作存储进经验库中，其中，前端操作可以是独立的操作步骤，也可以是一组操作步骤序列；各场景对应的基础前端操作可以为单个基础前端操作，也可以为多个基础前端操作。例如，对于登录场景，该场景下存储有一基础前端操作：“输入4位字符组成的用户名-＞输入密码-＞输入验证码-＞点击‘登录’按钮”；该场景下还可以存储有另一基础前端操作：“输入符合格式要求的邮箱地址-＞输入密码-＞输入验证码-＞点击‘登录’按钮”。
该实施例的优点在于，通过建立存储有基础前端操作的经验库，每一基础前端操作都可以被系统所参考，使得系统可以基于经验库积累有关前端操作的经验。
下面描述响应于用户终端进行的前端操作，对相关过程进行监测的过程。
在步骤S110中，响应于用户终端进行的前端操作，确定所述前端操作对应的场景，并对所述前端操作、及对应的后端反馈进行监测。
后端反馈是指系统响应于前端操作，于后端产生的相应的反馈。
当用户终端于系统前端进行前端操作时，就会触发系统对相关过程的监测。系统会根据前端操作确定当前所在场景，对该前端操作进行监测的同时，也会对该场景下相应的后端反馈进行监测。
在一实施例中，如图3所示，步骤S110包括：
步骤S1101：基于所述用户终端所在的当前页面，确定所述前端操作对应的场景；
步骤S1102：对所述前端操作、及对应的后端反馈进行监测。
在一实施例中，当用户终端于系统前端进行前端操作时，系统即根据用户终端 所在的当前页面，确定该前端操作对应的场景。例如：用户终端进行前端操作所在的当前页面为登录页面，则该前端操作对应的场景为登录场景。系统对该前端操作、及该场景下对应的后端反馈进行监测。
该实施的优点在于，将监测的前端操作、对应的后端反馈与场景绑定在一起，使得其能作为经验库的一部分，以丰富经验库的内容。
在一实施例中，所述对所述前端操作、及对应的后端反馈进行监测，包括：
基于页面埋点，对所述前端操作进行监测、过程记录；
基于后端接口，对所述后端反馈进行监测、过程记录。
页面埋点是指于页面埋入脚本，由该脚本对该页面进行的活动进行自动监测、记录。
在一实施例中，系统于各场景对应的页面中预先进行了埋点，使得当用户终端进行前端操作时，会自动触发脚本对前端操作的监测、过程记录。同时，系统通过监测后端接口，对对应的后端反馈进行监测、过程记录。
下面描述对监测到的后端反馈进行判断的过程。
在步骤S120中，基于所述后端反馈与预设反馈表的对比，确定所述后端反馈是否异常，所述预设反馈表描述了各后端反馈是否为异常后端反馈、及各异常后端反馈对应的异常类型。
在一实施例中，系统中预设的反馈表描述了各种后端反馈是否为异常后端反馈，以及各异常后端反馈对应的异常类型。例如，反馈表在表头1中描述：后端反馈“TRUE”为非异常后端反馈；在表头2中描述：后端反馈“XXXL”为异常后端反馈，其异常类型为“输入格式异常”；在表头3中描述：后端反馈“10774”为异常后端反馈，其异常类型为“操作顺序异常”......
在一实施例中，系统将监测到的后端反馈与预设反馈表进行对比，从而确定该后端反馈是否为异常后端反馈，以及，若该后端反馈为异常后端反馈，该异常后端反馈对应的异常类型。
该实施例的优点在于，通过预设的反馈表，能够快速确定后端反馈异常与否。
在一实施例中，在所述基于所述后端反馈与预设反馈表的对比，确定所述后端反馈是否异常之后，包括：
若所述后端反馈为非异常后端反馈，将所述对应的前端操作确定为该场景的一基础前端操作记录在所述经验库中。
在一实施例中，经验库建立之初，其包含的基础前端操作描述了对应场景下、正确的前端操作。但由于同一场景下的正确的前端操作可能存在多种形式，经验库建立之初包含的基础前端操作只是用于参考的单独示例，可能无法涵盖该场景下所有正确的前端操作。因此，在实际监测、过程记录过程中，将未引起异常后端反馈的前端操作作为该场景下的、一基础前端操作记录在经验库中，以丰富经验库的信息。
该实施例的优点在于，随着对前端操作、及后端反馈的监测的进行，不断丰富经验库存储的各场景下各种基础前端操作的信息。
下面描述对异常后端反馈进行相关处理的过程。
在步骤S130中，若所述后端反馈为异常后端反馈，基于所述预设反馈表确定所述异常后端反馈的异常类型，并将所述前端操作确定为所述场景下的异常前端操作。
在一实施例中，系统对用户终端进行的前端操作、及对应的后端反馈进行监测时，确定该后端反馈为异常后端反馈。系统即根据预设反馈表，确定该异常后端反馈的异常类型，并将该前端操作确定为异常前端操作。以便以该异常前端操作为基础进行后续处理，从而向用户终端进行提醒。
在步骤S140中，从所述经验库中提取出所述场景对应的各基础前端操作。
当监测到异常后端反馈时，即证明对应的前端操作是异常前端操作，需要向用户终端进行提醒。在提醒之前，要首先确定异常前端操作在哪一步上出现了异常。为达到此目的，系统要从经验库中提取出该场景下的各基础前端操作，以作为参考，从而能够确定出异常前端操作中出现的异常问题。
在一实施例中，系统将异常后端反馈对应的前端操作确定为异常前端操作后，由于前端操作及对应的后端反馈均是与场景绑定在一起的。因此，系统可以根据该异常前端操作确定当前场景，并从经验库中提取出该场景下的各基础前端操作。
下面描述以各所述基础前端操作作为参考，确定异常前端操作中异常问题的过 程。
在步骤S150中，基于所述异常类型，将所述异常前端操作与各所述基础前端操作进行对比，确定所述异常前端操作对应的异常问题。
异常问题是指异常前端操作中，导致异常后端反馈的操作步骤的问题。
在一实施例中，系统根据异常后端反馈的异常类型，初步判断出异常问题出现的范围。进而，将该异常前端操作与该场景下各基层前端操作在该范围内进行对比，从而找出该异常前端操作对应的异常问题。
该实施例的优点在于，确定出异常前端操作对应的异常问题，使得以后再次监测到该异常前端操作时，能够向用户终端提醒该异常问题，使得用户终端能够明确具体的异常问题所在，提高了用户终端后续更正异常问题的效率。
在一实施例中，如图4所示，步骤S150包括：
步骤S1501：基于所述异常类型，确定待对比操作步骤；
步骤S1502：将所述异常前端操作与各所述基础前端操作、于所述待对比操作步骤上进行对比，确定所述异常前端操作与各所述基础前端操作均相异的属性；
步骤S1503：将所述均相异的属性确定为所述异常问题。
由于经验库中存储的基础前端操作在各操作步骤上都是不会引起异常后端反馈的、正确的操作步骤。因此，通过将异常前端操作与基础前端操作在各对应的操作步骤上进行对比，即可确定出异常问题所在。
在一实施例中，系统根据异常前端操作对应的异常类型，确定出待对比操作步骤。例如，异常类型为“输入格式异常”，即可确定，待对比操作步骤为涉及到输入的步骤。因此，系统将该异常前端操作与该场景下各基础前端操作，于涉及到输入的步骤上，进行输入格式的对比。通过对比，系统发现，各基础前端操作于“身份证信息输入项”中输入的信息均为18位字符，而该异常前端操作于“身份证信息输入项”中输入的信息为17位字符，与各基础前端操作均相异。由此，系统即可确定，异常问题为“身份证信息输入错误”。
该实施例的优点在于，通过具体到操作步骤的对比，使得异常问题更为具体。
在一实施例中，将异常类型确定为对应的异常问题。
当经验库中存储的基础前端操作数量较少，无法有效支持在操作步骤上的对比时，异常前端操作与各基层前端操作在待对比操作步骤上均相异的属性会出现复数个，其中，只有一小部分均相异的属性是异常问题所在，其他的均相异的属性是另一种正确的形式。只是由于经验库的“经验”(即，基础前端操作)过少，无法判断这些均相异的属性中，哪些是异常的，哪些是正常的。在这种情况下，系统无法确定具体的异常问题所在。因此，将异常类型作为异常问题。例如，异常类型为“输入格式异常”，则异常问题为“输入格式异常”。
该实施例的优点在于，直接将异常类型确定为异常问题，提高了确定异常问题的效率与适用性。
在一实施例中，在所述基于所述异常类型，将所述异常前端操作与各所述基础前端操作进行对比，确定所述异常前端操作对应的异常问题之后，包括：
将所述场景、所述异常前端操作及所述异常问题录入所述经验库，使得再次监测到所述场景下所述异常前端操作时，向用户终端提醒对应的异常问题。
在一实施例中，系统将该异常前端操作及对应的异常问题录入经验库中对应场景下。当再次监测到与该异常前端操作一致的前端操作时，即可立即将对应的异常问题发送给用户终端，以作提醒。
该实施例的优点在于，将异常问题录入经验库中，使得再次监测到对应的异常前端操作时，无需再次进行异常前端操作与各基层前端操作的对比、以及异常问题的确定的过程，可以立即向用户终端进行提醒，提高了提醒效率。
在步骤S160中，向所述用户终端发送对所述异常前端操作的提醒信息。
在一实施例中，确定了用户终端进行的异常前端操作对应的异常问题后，向用户终端发送对应的提醒信息，以使得用户终端根据提醒信息更正前端操作。
在一实施例中，在所述向所述用户终端发送对所述异常前端操作的提醒信息之后，包括：
对所述异常前端操作、及对应的异常后端反馈的过程记录，生成问题报告，并将所述问题报告发送到问题报告接收终端。
在一实施例中，系统基于对异常前端操作、及对应的异常后端反馈的监测进行 过程记录，进而生成能够展示出异常前端操作流程、及对应的异常后端反馈的问题报告，并将问题报告发送给问题报告接收终端。
该实施例的优点在于，生成的问题报告可以更为形象地展示出异常前端操作中的流程、及对应的异常后端反馈，从而使得问题报告接收终端能够更准确地判断出异常问题所在。
在一实施例中，问题报告可以为报表的形式，也可以为流程图的形式。
在一实施例中，问题报告接收终端可以为管理端，也可以为用户终端。
在一实施例中，如图2所示，提供了一种基于经验库的异常前端操作提醒的装置，具体包括：
建立模块210，用于建立经验库，所述经验库包含各场景对应的基础前端操作；
第一确定模块220，用于响应于用户终端进行的前端操作，确定所述前端操作对应的场景，并对所述前端操作、及对应的后端反馈进行监测；
第二确定模块230，用于基于所述后端反馈与预设反馈表的对比，确定所述后端反馈是否异常，所述预设反馈表描述了各后端反馈是否为异常后端反馈、及各异常后端反馈对应的异常类型；
第三确定模块240，用于若所述后端反馈为异常后端反馈，基于所述预设反馈表确定所述异常后端反馈的异常类型，并将所述前端操作确定为所述场景下的异常前端操作；
提取模块250，用于从所述经验库中提取出所述场景对应的各基础前端操作；
第四确定模块260，用于基于所述异常类型，将所述异常前端操作与各所述基础前端操作进行对比，确定所述异常前端操作对应的异常问题；
发送模块270，用于向所述用户终端发送对所述异常前端操作的提醒信息。
上述装置中各个模块的功能和作用的实现过程具体详见上述基于经验库的异常前端操作提醒的方法中对应步骤的实现过程，在此不再赘述。
应当注意，尽管在上文详细描述中提及了用于动作执行的设备的若干模块或者单元，但是这种划分并非强制性的。实际上，根据本申请的实施方式，上文描述的两个或更多模块或者单元的特征和功能可以在一个模块或者单元中具体化 。反之，上文描述的一个模块或者单元的特征和功能可以进一步划分为由多个模块或者单元来具体化。
此外，尽管在附图中以特定顺序描述了本申请中方法的各个步骤，但是，这并非要求或者暗示必须按照该特定顺序来执行这些步骤，或是必须执行全部所示的步骤才能实现期望的结果。附加的或备选的，可以省略某些步骤，将多个步骤合并为一个步骤执行，以及/或者将一个步骤分解为多个步骤执行等。
通过以上的实施方式的描述，本领域的技术人员易于理解，这里描述的示例实施方式可以通过软件实现，也可以通过软件结合必要的硬件的方式来实现。因此，根据本申请实施方式的技术方案可以以软件产品的形式体现出来，该软件产品可以存储在一个非易失性存储介质(可以是CD-ROM，U盘，移动硬盘等)中或网络上，包括若干指令以使得一台计算设备(可以是个人计算机、服务器、移动终端、或者网络设备等)执行根据本申请实施方式的方法。
图5示出根据本申请一示例实施方式的基于经验库的异常前端操作提醒的系统架构图。该系统架构包括：用户终端310、系统320、经验库330。
在一实施例中，系统320建立经验库330，经验库330中存储着各场景对应的基础前端操作。当一用户终端310于系统320的前端进行前端操作时，系统320确定该前端操作对应的场景，并对该前端操作及对应的后端反馈进行监测；系统320通过将后端反馈与预设反馈表进行对比，确定该后端反馈是否为异常后端反馈。若该后端反馈为异常后端反馈，则基于预定反馈表确定其异常类型，并将该前端操作确定为异常前端操作。将该异常前端操作与从经验库中提取出的该场景下的基础前端操作进行对比，确定该异常前端操作的异常问题，并向该用户终端310进行提醒。
通过以上对系统架构的描述，本领域的技术人员易于理解，这里描述的系统架构能够实现图2所示的基于经验库的异常前端操作提醒的装置中各个模块的功能。
在本申请的示例性实施例中，还提供了一种能够实现上述方法的电子设备。
所属技术领域的技术人员能够理解，本申请的各个方面可以实现为系统、方法或程序产品。因此，本申请的各个方面可以具体实现为以下形式，即：完全的 硬件实施方式、完全的软件实施方式(包括固件、微代码等)，或硬件和软件方面结合的实施方式，这里可以统称为“电路”、“模块”或“系统”。
下面参照图6来描述根据本申请的这种实施方式的电子设备400。图6显示的电子设备400仅仅是一个示例，不应对本申请实施例的功能和使用范围带来任何限制。
如图6所示，电子设备400以通用计算设备的形式表现。电子设备400的组件可以包括但不限于：上述至少一个处理单元410、上述至少一个存储单元420、连接不同系统组件(包括存储单元420和处理单元410)的总线430。
其中，所述存储单元存储有程序代码，所述程序代码可以被所述处理单元410执行，使得所述处理单元410执行本说明书上述“示例性方法”部分中描述的根据本申请各种示例性实施方式的步骤。例如，所述处理单元410可以执行如图1中所示步骤S100：建立经验库，所述经验库包含各场景对应的基础前端操作；步骤S110：响应于用户终端进行的前端操作，确定所述前端操作对应的场景，并对所述前端操作、及对应的后端反馈进行监测；步骤S120：基于所述后端反馈与预设反馈表的对比，确定所述后端反馈是否异常，所述预设反馈表描述了各后端反馈是否为异常后端反馈、及各异常后端反馈对应的异常类型；步骤S130：若所述后端反馈为异常后端反馈，基于所述预设反馈表确定所述异常后端反馈的异常类型，并将所述前端操作确定为所述场景下的异常前端操作；步骤S140：从所述经验库中提取出所述场景对应的各基础前端操作；步骤S150：基于所述异常类型，将所述异常前端操作与各所述基础前端操作进行对比，确定所述异常前端操作对应的异常问题；步骤S160：向所述用户终端发送对所述异常前端操作的提醒信息。
存储单元420可以包括易失性存储单元形式的可读介质，例如随机存取存储单元(RAM)4201和/或高速缓存存储单元4202，还可以进一步包括只读存储单元(ROM)4203。
存储单元420还可以包括具有一组(至少一个)程序模块4205的程序/实用工具4204，这样的程序模块4205包括但不限于：操作系统、一个或者多个应用程序、其它程序模块以及程序数据，这些示例中的每一个或某种组合中可能包括网 络环境的实现。
总线430可以为表示几类总线结构中的一种或多种，包括存储单元总线或者存储单元控制器、外围总线、图形加速端口、处理单元或者使用多种总线结构中的任意总线结构的局域总线。
电子设备400也可以与一个或多个外部设备500(例如键盘、指向设备、蓝牙设备等)通信，还可与一个或者多个使得用户能与该电子设备400交互的设备通信，和/或与使得该电子设备400能与一个或多个其它计算设备进行通信的任何设备(例如路由器、调制解调器等等)通信。这种通信可以通过输入/输出(I/O)接口450进行。并且，电子设备400还可以通过网络适配器460与一个或者多个网络(例如局域网(LAN)，广域网(WAN)和/或公共网络，例如因特网)通信。如图所示，网络适配器460通过总线430与电子设备400的其它模块通信。应当明白，尽管图中未示出，可以结合电子设备400使用其它硬件和/或软件模块，包括但不限于：微代码、设备驱动器、冗余处理单元、外部磁盘驱动阵列、RAID系统、磁带驱动器以及数据备份存储系统等。
通过以上的实施方式的描述，本领域的技术人员易于理解，这里描述的示例实施方式可以通过软件实现，也可以通过软件结合必要的硬件的方式来实现。因此，根据本申请实施方式的技术方案可以以软件产品的形式体现出来，该软件产品可以存储在一个非易失性存储介质(可以是CD-ROM，U盘，移动硬盘等)中或网络上，包括若干指令以使得一台计算设备(可以是个人计算机、服务器、终端装置、或者网络设备等)执行根据本申请实施方式的方法。
在本申请的示例性实施例中，还提供了一种计算机可读存储介质，所述存储介质为易失性存储介质或非易失性存储介质，其上存储有能够实现本说明书上述方法的程序产品。在一些可能的实施方式中，本申请的各个方面还可以实现为一种程序产品的形式，其包括程序代码，当所述程序产品在终端设备上运行时，所述程序代码用于使所述终端设备执行本说明书上述“示例性方法”部分中描述的根据本申请各种示例性实施方式的步骤。
参考图7所示，描述了根据本申请的实施方式的用于实现上述方法的程序产品600，其可以采用便携式紧凑盘只读存储器(CD-ROM)并包括程序代码，并可以在 终端设备，例如个人电脑上运行。然而，本申请的程序产品不限于此，在本文件中，可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。
所述程序产品可以采用一个或多个可读介质的任意组合。可读介质可以是可读信号介质或者可读存储介质。可读存储介质例如可以为但不限于电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。可读存储介质的更具体的例子(非穷举的列表)包括：具有一个或多个导线的电连接、便携式盘、硬盘、随机存取存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(EPROM或闪存)、光纤、便携式紧凑盘只读存储器(CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。
计算机可读信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了可读程序代码。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。可读信号介质还可以是可读存储介质以外的任何可读介质，该可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。
可读介质上包含的程序代码可以用任何适当的介质传输，包括但不限于无线、有线、光缆、RF等等，或者上述的任意合适的组合。
可以以一种或多种程序设计语言的任意组合来编写用于执行本申请操作的程序代码，所述程序设计语言包括面向对象的程序设计语言-诸如Java、C++等，还包括常规的过程式程序设计语言-诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算设备上执行、部分地在用户设备上执行、作为一个独立的软件包执行、部分在用户计算设备上部分在远程计算设备上执行、或者完全在远程计算设备或服务器上执行。在涉及远程计算设备的情形中，远程计算设备可以通过任意种类的网络，包括局域网(LAN)或广域网(WAN)，连接到用户计算设备，或者，可以连接到外部计算设备(例如利用因特网服务提供商来通过因特网连接)。
Claims (20)
- 一种基于经验库的异常前端操作提醒的方法，其中，所述方法包括：建立经验库，所述经验库包含各场景对应的基础前端操作；响应于用户终端进行的前端操作，确定所述前端操作对应的场景，并对所述前端操作、及对应的后端反馈进行监测；基于所述后端反馈与预设反馈表的对比，确定所述后端反馈是否异常，所述预设反馈表描述了各后端反馈是否为异常后端反馈、及各异常后端反馈对应的异常类型；若所述后端反馈为异常后端反馈，基于所述预设反馈表确定所述异常后端反馈的异常类型，并将所述前端操作确定为所述场景下的异常前端操作；从所述经验库中提取出所述场景对应的各基础前端操作；基于所述异常类型，将所述异常前端操作与各所述基础前端操作进行对比，确定所述异常前端操作对应的异常问题；向所述用户终端发送对所述异常前端操作的提醒信息。
- 根据权利要求1所述的方法，其中，所述响应于用户终端进行的前端操作，确定所述前端操作对应的场景，并对所述前端操作、及对应的后端反馈进行监测，包括：基于所述用户终端所在的当前页面，确定所述前端操作对应的场景；对所述前端操作、及对应的后端反馈进行监测。
- 根据权利要求2所述的方法，其中，所述对所述前端操作、及对应的后端反馈进行监测，包括：基于页面埋点，对所述前端操作进行监测、过程记录；基于后端接口，对所述后端反馈进行监测、过程记录。
- 根据权利要求2所述的方法，其中，所述对所述前端操作、及对应的后端反馈进行监测，包括：基于页面埋点，对所述前端操作进行监测、过程记录；基于后端接口，对所述后端反馈进行监测、过程记录。
- 根据权利要求1所述的方法，其中，所述基于所述异常类型，将所述异常前端操作与各所述基础前端操作进行对比，确定所述异常前端操作对应的异常问题，包括：基于所述异常类型，确定待对比操作步骤；将所述异常前端操作与各所述基础前端操作、于所述待对比操作步骤上进行对比，确定所述异常前端操作与各所述基础前端操作均相异的属性；将所述均相异的属性确定为所述异常问题。
- 根据权利要求1所述的方法，其中，在所述基于所述异常类型，将所述异常前端操作与各所述基础前端操作进行对比，确定所述异常前端操作对应的异常问题之后，包括：将所述场景、所述异常前端操作及所述异常问题录入所述经验库，使得再次监测到所述场景下所述异常前端操作时，向用户终端提醒对应的异常问题。
- 根据权利要求1所述的方法，其中，在所述向所述用户终端发送对所述异常前端操作的提醒信息之后，包括：对所述异常前端操作、及对应的异常后端反馈的过程记录，生成问题报告，并将所述问题报告发送到问题报告接收终端。
- 一种基于经验库的异常前端操作提醒的装置，其中，包括：建立模块，用于建立经验库，所述经验库包含各场景对应的基础前端操作；第一确定模块，用于响应于用户终端进行的前端操作，确定所述前端操作对应的场景，并对所述前端操作、及对应的后端反馈进行监测；第二确定模块，用于基于所述后端反馈与预设反馈表的对比，确定所述后端反馈是否异常，所述预设反馈表描述了各后端反馈是 否为异常后端反馈、及各异常后端反馈对应的异常类型；第三确定模块，用于若所述后端反馈为异常后端反馈，基于所述预设反馈表确定所述异常后端反馈的异常类型，并将所述前端操作确定为所述场景下的异常前端操作；提取模块，用于从所述经验库中提取出所述场景对应的各基础前端操作；第四确定模块，用于基于所述异常类型，将所述异常前端操作与各所述基础前端操作进行对比，确定所述异常前端操作对应的异常问题；发送模块，用于向所述用户终端发送对所述异常前端操作的提醒信息。
- 一种基于经验库的异常前端操作提醒的电子设备，其中，包括：存储器，配置为存储可执行指令；处理器，配置为执行所述存储器中存储的可执行指令，以执行一种基于经验库的异常前端操作提醒的方法：其中，所述基于经验库的异常前端操作提醒的方法包括：建立经验库，所述经验库包含各场景对应的基础前端操作；响应于用户终端进行的前端操作，确定所述前端操作对应的场景，并对所述前端操作、及对应的后端反馈进行监测；基于所述后端反馈与预设反馈表的对比，确定所述后端反馈是否异常，所述预设反馈表描述了各后端反馈是否为异常后端反馈、及各异常后端反馈对应的异常类型；若所述后端反馈为异常后端反馈，基于所述预设反馈表确定所述异常后端反馈的异常类型，并将所述前端操作确定为所述场景下的异常前端操作；从所述经验库中提取出所述场景对应的各基础前端操作；基于所述异常类型，将所述异常前端操作与各所述基础前端操作进行对比，确定所述异常前端操作对应的异常问题；向所述用户终端发送对所述异常前端操作的提醒信息。
- 根据权利要求9所述的电子设备，其中，所述响应于用户终端进行的前端操作，确定所述前端操作对应的场景，并对所述前端操作、及对应的后端反馈进行监测，包括：基于所述用户终端所在的当前页面，确定所述前端操作对应的场景；对所述前端操作、及对应的后端反馈进行监测。
- 根据权利要求10所述的电子设备，其中，所述对所述前端操作、及对应的后端反馈进行监测，包括：基于页面埋点，对所述前端操作进行监测、过程记录；基于后端接口，对所述后端反馈进行监测、过程记录。
- 根据权利要求9所述的电子设备，其中，在所述基于所述后端反馈与预设反馈表的对比，确定所述后端反馈是否异常之后，包括：若所述后端反馈为非异常后端反馈，将所述对应的前端操作确定为该场景的一基础前端操作记录在所述经验库中。
- 根据权利要求9所述的电子设备，其中，所述基于所述异常类型，将所述异常前端操作与各所述基础前端操作进行对比，确定所述异常前端操作对应的异常问题，包括：基于所述异常类型，确定待对比操作步骤；将所述异常前端操作与各所述基础前端操作、于所述待对比操作步骤上进行对比，确定所述异常前端操作与各所述基础前端操作均相异的属性；将所述均相异的属性确定为所述异常问题。
- 根据权利要求9所述的电子设备，其中，在所述基于所述异常类型，将所述异常前端操作与各所述基础前端操作进行对比，确定所述异常前端操作对应的异常问题之后，包括：将所述场景、所述异常前端操作及所述异常问题录入所述经验库，使得再次监测到所述场景下所述异常前端操作时，向用户终端 提醒对应的异常问题。
- 根据权利要求9所述的电子设备，其中，在所述向所述用户终端发送对所述异常前端操作的提醒信息之后，包括：对所述异常前端操作、及对应的异常后端反馈的过程记录，生成问题报告，并将所述问题报告发送到问题报告接收终端。
- 一种计算机可读存储介质，其中，其存储有计算机程序指令，当所述计算机指令被计算机执行时，使计算机执行一种基于经验库的异常前端操作提醒的方法：其中，所述基于经验库的异常前端操作提醒的方法包括：建立经验库，所述经验库包含各场景对应的基础前端操作；响应于用户终端进行的前端操作，确定所述前端操作对应的场景，并对所述前端操作、及对应的后端反馈进行监测；基于所述后端反馈与预设反馈表的对比，确定所述后端反馈是否异常，所述预设反馈表描述了各后端反馈是否为异常后端反馈、及各异常后端反馈对应的异常类型；若所述后端反馈为异常后端反馈，基于所述预设反馈表确定所述异常后端反馈的异常类型，并将所述前端操作确定为所述场景下的异常前端操作；从所述经验库中提取出所述场景对应的各基础前端操作；基于所述异常类型，将所述异常前端操作与各所述基础前端操作进行对比，确定所述异常前端操作对应的异常问题；向所述用户终端发送对所述异常前端操作的提醒信息。
- 根据权利要求16所述的计算机可读存储介质，其中，所述响应于用户终端进行的前端操作，确定所述前端操作对应的场景，并对所述前端操作、及对应的后端反馈进行监测，包括：基于所述用户终端所在的当前页面，确定所述前端操作对应的场景；对所述前端操作、及对应的后端反馈进行监测。
- 根据权利要求16所述的计算机可读存储介质，其中，所述对所述前端操作、及对应的后端反馈进行监测，包括：基于页面埋点，对所述前端操作进行监测、过程记录；基于后端接口，对所述后端反馈进行监测、过程记录。
- 根据权利要求16所述的计算机可读存储介质，其中，在所述基于所述后端反馈与预设反馈表的对比，确定所述后端反馈是否异常之后，包括：若所述后端反馈为非异常后端反馈，将所述对应的前端操作确定为该场景的一基础前端操作记录在所述经验库中。
- 根据权利要求16所述的计算机可读存储介质，其中，所述基于所述异常类型，将所述异常前端操作与各所述基础前端操作进行对比，确定所述异常前端操作对应的异常问题，包括：基于所述异常类型，确定待对比操作步骤；将所述异常前端操作与各所述基础前端操作、于所述待对比操作步骤上进行对比，确定所述异常前端操作与各所述基础前端操作均相异的属性；将所述均相异的属性确定为所述异常问题。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910671339.7A CN110457548A (zh) | 2019-07-24 | 2019-07-24 | 基于经验库的异常前端操作提醒的方法及相关设备 |
| CN201910671339.7 | 2019-07-24 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2021012741A1 true WO2021012741A1 (zh) | 2021-01-28 |
Family
ID=68483268
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2020/087468 WO2021012741A1 (zh) | 2019-07-24 | 2020-04-28 | 基于经验库的异常前端操作提醒的方法及相关设备 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN110457548A (zh) |
| WO (1) | WO2021012741A1 (zh) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113553034A (zh) * | 2021-07-07 | 2021-10-26 | 北京计算机技术及应用研究所 | 一种前端埋点系统输出方法 |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110457548A (zh) * | 2019-07-24 | 2019-11-15 | 深圳壹账通智能科技有限公司 | 基于经验库的异常前端操作提醒的方法及相关设备 |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140115386A1 (en) * | 2012-10-24 | 2014-04-24 | Hon Hai Precision Industry Co., Ltd. | Server and method for managing server |
| CN107977303A (zh) * | 2017-11-30 | 2018-05-01 | 努比亚技术有限公司 | 一种操作行为监控方法、移动终端以及计算机可读存储介质 |
| CN108334436A (zh) * | 2018-01-31 | 2018-07-27 | 平安普惠企业管理有限公司 | 应用软件的优化方法、装置、设备及计算机可读存储介质 |
| CN109376071A (zh) * | 2018-09-03 | 2019-02-22 | 平安普惠企业管理有限公司 | 应用软件异常反馈方法、装置、计算机设备及存储介质 |
| CN109660502A (zh) * | 2018-09-28 | 2019-04-19 | 平安科技（深圳）有限公司 | 异常行为的检测方法、装置、设备及存储介质 |
| CN110457548A (zh) * | 2019-07-24 | 2019-11-15 | 深圳壹账通智能科技有限公司 | 基于经验库的异常前端操作提醒的方法及相关设备 |
-
2019
- 2019-07-24 CN CN201910671339.7A patent/CN110457548A/zh active Pending
-
2020
- 2020-04-28 WO PCT/CN2020/087468 patent/WO2021012741A1/zh active Application Filing
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140115386A1 (en) * | 2012-10-24 | 2014-04-24 | Hon Hai Precision Industry Co., Ltd. | Server and method for managing server |
| CN107977303A (zh) * | 2017-11-30 | 2018-05-01 | 努比亚技术有限公司 | 一种操作行为监控方法、移动终端以及计算机可读存储介质 |
| CN108334436A (zh) * | 2018-01-31 | 2018-07-27 | 平安普惠企业管理有限公司 | 应用软件的优化方法、装置、设备及计算机可读存储介质 |
| CN109376071A (zh) * | 2018-09-03 | 2019-02-22 | 平安普惠企业管理有限公司 | 应用软件异常反馈方法、装置、计算机设备及存储介质 |
| CN109660502A (zh) * | 2018-09-28 | 2019-04-19 | 平安科技（深圳）有限公司 | 异常行为的检测方法、装置、设备及存储介质 |
| CN110457548A (zh) * | 2019-07-24 | 2019-11-15 | 深圳壹账通智能科技有限公司 | 基于经验库的异常前端操作提醒的方法及相关设备 |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113553034A (zh) * | 2021-07-07 | 2021-10-26 | 北京计算机技术及应用研究所 | 一种前端埋点系统输出方法 |
| CN113553034B (zh) * | 2021-07-07 | 2022-04-05 | 北京计算机技术及应用研究所 | 一种前端埋点系统输出方法 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110457548A (zh) | 2019-11-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2018113385A1 (zh) | 对客户端的应用程序动态埋点的方法、系统、客户端及服务器 | |
| WO2021051563A1 (zh) | 目标数据归档方法、装置、电子设备及计算机非易失性可读存储介质 | |
| US20150341795A1 (en) | Instant messaging message processing method and device and storage medium | |
| US20100225653A1 (en) | Information notification method and information notification system | |
| WO2020177734A1 (zh) | 小程序触发方法、计算机设备及存储介质 | |
| US8448138B2 (en) | Recording user-driven events within a computing system | |
| WO2021012741A1 (zh) | 基于经验库的异常前端操作提醒的方法及相关设备 | |
| CN111385148A (zh) | 业务告警方法、装置、计算机设备及存储介质 | |
| CN112188277B (zh) | 投屏控制方法、装置、电子设备和计算机程序介质 | |
| CN110324416B (zh) | 下载路径跟踪方法、装置、服务器、终端及介质 | |
| CN111552633A (zh) | 接口的异常调用测试方法、装置、计算机设备及存储介质 | |
| WO2021155683A1 (zh) | 日志打印方法、装置、电子设备和存储介质 | |
| CN108874441B (zh) | 一种板卡配置方法、装置、服务器和存储介质 | |
| CN111930703A (zh) | 日志文件自动抓取方法、装置和计算机设备 | |
| CN109889922B (zh) | 流媒体数据的转发方法、装置、设备和存储介质 | |
| CN110881224B (zh) | 一种网络长连接方法、装置、设备及存储介质 | |
| US11019004B1 (en) | System, method, and computer program for performing bot engine abstraction | |
| CN109600722B (zh) | 短信接收验证方法及装置、电子设备、存储介质 | |
| CN113238815A (zh) | 一种接口访问控制方法、装置、设备及存储介质 | |
| EP3818445B1 (en) | Automated control of distributed computing devices | |
| CN110888791A (zh) | 一种日志处理方法、装置、设备和存储介质 | |
| CN113612659B (zh) | 设备连网测试方法、装置、电子设备及存储介质 | |
| CN114553663B (zh) | 一种异常检测方法、装置、设备和存储介质 | |
| CN112818204B (zh) | 一种业务的处理方法、装置、设备及存储介质 | |
| CN112866979B (zh) | 基于5g服务化接口的用户信息关联方法、装置、设备和介质 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20844166 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 20844166 Country of ref document: EP Kind code of ref document: A1 |
|
| 32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 05.08.2022) |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 20844166 Country of ref document: EP Kind code of ref document: A1 |