WO2016155430A1

WO2016155430A1 - Fault feedback method and fault feedback device

Info

Publication number: WO2016155430A1
Application number: PCT/CN2016/074127
Authority: WO
Inventors: 索浩森
Original assignee: 乐视移动智能信息技术（北京）有限公司
Priority date: 2015-03-27
Filing date: 2016-02-19
Publication date: 2016-10-06
Also published as: CN104866172A

Abstract

Provided are a fault feedback method and a fault feedback device. The method comprises: on an operation interface of a terminal, receiving a triggering signal entering a control center interface, displaying the control center interface, wherein a first triggering entry is displayed on the control center interface; detecting an activation signal for the first triggering entry, displaying a corresponding fault feedback interface, and automatically loading a screenshot of the operation interface and an identified terminal account onto the fault feedback interface; and detecting a submission confirmation signal, and sending data loaded onto the fault feedback interface to a background service center, giving a submission confirmation prompt to a user, and returning to the operation interface. In the method, a variety of information describing a fault is combined together by means of a fault feedback interface, to bring more convenience to operation and maintenance staff of a background service center to accurately learn about fault conditions, so that a fault is processed properly and correctly, thereby improving the fault reporting efficiency and accuracy.

Description

Fault feedback method and fault feedback device

cross reference

The present application is hereby incorporated by reference in its entirety in its entirety in its entirety in the entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire all all all all all all each

Technical field

The present application relates to the field of network communication technologies, and in particular, to a fault feedback method and a fault feedback device.

Background technique

Today, terminals are often pre-installed with applications. These applications are largely developed and installed by the manufacturer, and some may be third-party software. In actual use, these applications are likely to have various use failures, which is very common, and some faults may be easily solved by ordinary users, but some faults may require professional handling to solve.

But because a large part of these applications are developed by the manufacturer itself, for these applications, whether it is the application itself or the compatibility of the application with the operating system, the manufacturer's program developers are the most aware, obviously It is most appropriate for the program developers of the manufacturer to deal with these faults. They can not only provide direct solutions to individuals, but even when such problems are ubiquitous, they can be better launched directly in the face of the overall user solution. Program. However, for the failure of such applications, the user does not have a fault feedback mode that can be intelligently processed and highly adaptive. Due to the excessive manual operation, the existing schemes cause user operation difficulties, directly affecting the feedback enthusiasm of the users, and on the other hand, the fault reporting is unclear, and the operation and maintenance personnel cannot clearly know the fault condition.

For the third-party software on the terminal, there are similar problems as described above. Third-party software can be installed later or factory-installed, but no matter which installation method, there will inevitably be operational failures. For these failures, whether from the perspective of improving the software or for the user From the perspective of solving problems, third-party software developers are also willing to know the fault situation as quickly and accurately as possible, but third-party software obviously lacks such a way to obtain fault feedback.

Therefore, how to solve the existing problems of lack of fault feedback, difficult operation of fault reporting and unclear and accurate fault reporting has become a technical problem to be solved.

Summary of the invention

In view of the above, the present application has been made in order to provide a fault feedback method and fault feedback apparatus that overcomes the above problems or at least partially solves or alleviates the above problems.

According to an aspect of the present application, a fault feedback method is provided, including: receiving a trigger signal entering an operation center interface on an operation interface of the terminal, displaying a control center interface, and displaying the first on the control center interface Triggering an entry; detecting an activation signal for the first trigger entry, displaying a corresponding fault feedback interface, automatically loading a screenshot of the operation interface and the identified terminal account in the fault feedback interface; detecting a submission confirmation The signal sends the data loaded in the fault feedback interface to the background service center, and submits a confirmation prompt to the user, and returns to the operation interface.

Further, the screenshot of the operation interface is intercepted when the trigger signal for entering the control center interface is intercepted or when the activation signal for the first trigger entry is detected.

Further, detecting an activation signal for the first trigger entry, displaying a corresponding fault feedback interface, automatically loading a screenshot of the operation interface and the identified terminal account in the fault feedback interface, further including: adjusting Taking the name of the application corresponding to the operation interface, and displaying the name of the application in the fault feedback interface.

Further, the name of the application corresponding to the operation interface is invoked, including: invoking a task manager, and retrieving a task corresponding to a flag with the lowest value in the startup sequence, where the task corresponding to the lowest value flag is the operation interface Corresponding tasks, and selecting an application name corresponding to the task corresponding to the operation interface from the mapping table of the task and the application name according to the task corresponding to the operation interface.

Further, automatically loading a screenshot of the operation interface in the fault feedback interface, including: detecting whether a screenshot is saved in a period from the current time, and if so, automatically selecting a screenshot that is the closest to the current time. Load it.

Further, an activation signal to the first trigger entry is detected, and a corresponding fault is displayed. The feed interface automatically loads the screenshot of the operation interface and the identified terminal account in the fault feedback interface, and further includes: providing a description window on the fault feedback interface, identifying and loading the user in the description window Descriptive information about the fault entered inside.

Further, the description information about the fault input in the description window includes: text description information, and/or audio and video description information.

Further, after the screenshot of the operation interface and the identified terminal account are automatically loaded in the fault feedback interface, before the submission of the confirmation signal is detected, the method further includes: providing an automatic uploading entry in the fault feedback interface, and detecting To the activation signal of the automatic uploading portal, a manual selection interface is displayed, and a screenshot for selecting loading is displayed in the manual selection interface, and the selected screenshot is loaded.

Further, after the loading of the screenshot of the operation interface and the identified terminal account, the method further includes: providing a fault attribute selection entry in the fault feedback interface, before detecting the submitting the confirmation signal, An activation signal for selecting the entry of the fault attribute is detected, a manual selection interface is displayed, and a corresponding fault attribute option for selection is displayed in the manual selection interface, and the selected fault attribute option is loaded.

Further, the fault attribute selection entry includes: a fault type selection entry and/or an appearance frequency selection entry.

Further, the terminal account includes: a terminal account in a login state, or a terminal account that has logged in and recorded.

According to an aspect of the present application, a fault feedback device is provided, including: a control center interface management module, configured to receive a trigger signal for entering the control center interface on an operation interface of the terminal, and display a control center interface. The first trigger entry is displayed on the control center interface, and the first trigger entry management module is configured to detect an activation signal for the first trigger entry, display a corresponding fault feedback interface, and automatically load the fault feedback interface. a screenshot of the operation interface and the identified terminal account; a submission confirmation management module, configured to detect the submission confirmation signal, send the data loaded in the fault feedback interface to the background service center, and submit the user Confirm the prompt and return to the operation interface.

Further, the first triggering entry management module is configured to retrieve the name of the application corresponding to the operation interface when the activation signal of the first trigger entry is detected, and the application is The name is displayed in the fault feedback interface.

Further, when the first trigger entry management module retrieves the name of the application corresponding to the operation interface, it is used to invoke the task manager to retrieve the task corresponding to the lowest value flag bit in the startup sequence, and the lowest value flag bit The corresponding task is a task corresponding to the operation interface, and the application name corresponding to the task corresponding to the operation interface is selected from the mapping table of the task and the application name according to the task corresponding to the operation interface.

Further, when the first trigger entry management module automatically loads the saved screenshot in the fault feedback interface, it is specifically used to detect whether a screenshot is saved in a period from the current time, and if so, automatically select the interception time from the current The most recent screenshot of the time is loaded.

Further, the first triggering entry management module, when detecting the activation signal to the first triggering entry, further provides a description window on the fault feedback interface, identifying and loading the user input in the description window Description information of the fault, wherein the description information about the fault input in the description window includes: text description information, and/or audio and video description information.

Further, the first triggering entry management module further provides an automatic uploading portal in the fault feedback interface, detects an activation signal to the automatic uploading portal, displays a manual selection interface, and displays the selective loading in the manual selection interface. Screenshot of the selected screenshot.

Further, the first triggering entry management module further provides a fault attribute selection entry in the fault feedback interface, detects an activation signal for selecting the fault attribute entry, displays a manual selection interface, and displays the content in the manual selection interface. Select the corresponding fault attribute option to load the selected fault attribute option.

Further, the screenshot of the operation interface is intercepted by the control center interface management module when receiving the trigger signal entering the control center interface or the first trigger entry management module intercepts the activation signal of the first trigger entry. of.

According to an aspect of the present application, a fault feedback apparatus is provided, including: a memory, a processor, wherein the memory is configured to store one or more instructions, wherein the one or more pieces An instruction for execution by the processor;

The processor is configured to receive a trigger signal that enters the control center interface on an operation interface of the terminal, and display a control center interface, where the first trigger entry is displayed on the control center interface; An activation signal triggering the portal, displaying a corresponding fault feedback interface, automatically loading a screenshot of the operation interface and the identified terminal account in the fault feedback interface; detecting a submission confirmation signal, and the fault feedback interface is The loaded data is sent to the background service center, and the user is presented with a confirmation prompt to return to the operation interface.

Further, the processor is further configured to: when receiving an activation signal for detecting the first trigger entry, retrieve a name of an application corresponding to the operation interface, and display the name of the application in the In the fault feedback interface.

Further, the processor is further configured to: when the name of the application corresponding to the operation interface is retrieved, the task manager is invoked to retrieve a task corresponding to the lowest value flag bit in the startup sequence, and the lowest value flag bit The corresponding task is a task corresponding to the operation interface, and the application name corresponding to the task corresponding to the operation interface is selected from the mapping table of the task and the application name according to the task corresponding to the operation interface.

Further, the processor is further configured to: when the saved screenshot is automatically loaded in the fault feedback interface, detect whether a screenshot is saved in a period from the current time, and if so, automatically select an intercept time from the current The most recent screenshot of the time is loaded.

Further, the processor is further configured to: when detecting an activation signal to the first trigger entry, further providing a description window on the fault feedback interface, identifying and loading a user input in the description window Descriptive information about the fault, wherein the description information about the fault input in the description window includes: text description information, and/or audio and video description information.

Further, the processor is further configured to: provide an automatic uploading portal in the fault feedback interface, detect an activation signal to the automatic uploading portal, display a manual selection interface, and display for selection in a manual selection interface Load the screenshot and load the selected screenshot.

Further, the processor is further configured to: provide a fault attribute selection entry in the fault feedback interface, detect an activation signal for selecting the fault attribute entry, display a manual selection interface, and display in a manual selection interface The corresponding fault attribute option is selected to load the selected fault attribute option.

Further, the processor is further configured to: the fault attribute selection entry, comprising: a fault type selection entry and/or an appearance frequency selection entry.

Further, the processor is further configured to: the terminal account, including: a terminal account in a login state, or a terminal account that has logged in and recorded.

Further, the processor is further configured to: the screenshot of the operation interface is intercepted when receiving a trigger signal entering the control center interface or the first trigger entry management module detects that the first trigger entry is Intercepted when the signal is activated.

Compared with the existing solutions, the technical effects obtained by the present application can combine various information describing faults through a fault feedback interface, and visually and rationally define faults from multiple angles and aspects. The display is more conducive to the operation and maintenance personnel of the background service center to accurately understand the fault situation, so that the fault is properly and correctly handled, and the efficiency and accuracy of the fault return are improved.

Of course, implementing any of the products of the present application necessarily does not necessarily require all of the technical effects described above to be achieved at the same time.

The above description is only an overview of the technical solutions of the present application, and the technical means of the present application can be more clearly understood, and the above and other objects, features and advantages of the present application can be more clearly understood. The following is a specific embodiment of the present application.

DRAWINGS

Various other advantages and benefits will become apparent to those skilled in the art from a The drawings are only for the purpose of illustrating the preferred embodiments and are not intended to be limiting. Throughout the drawings, the same reference numerals are used to refer to the same parts. In the drawing:

FIG. 1 is a flow chart schematically showing a fault feedback method according to an embodiment of the present application; FIG.

FIG. 2 is a flow chart schematically showing a fault feedback method according to an embodiment of the present application; FIG.

FIG. 3 is a flow chart schematically showing a fault feedback method according to an embodiment of the present application; FIG.

FIG. 4 is a schematic diagram showing the flow of a fault feedback method according to an embodiment of the present application. Figure

FIG. 5 is a schematic structural diagram of a fault feedback apparatus according to an embodiment of the present application; FIG.

Figure 6 is a schematic view showing the use of the application according to an application example of the present application;

Figure 7 is a schematic view showing the use of the application according to an application example of the present application;

Figure 8 is a schematic view showing the use of the application according to an application example of the present application;

Fig. 9 schematically shows a schematic view of the use according to an application example of the present application.

detailed description

The present application is further described below in conjunction with the drawings and specific embodiments. As shown in FIG. 1 , a fault feedback method according to an embodiment of the present application includes:

Step S100: Receive a trigger signal entering the control center interface on an operation interface of the terminal, and display a control center interface, where the first trigger entry is displayed on the control center interface;

The operation interface of the terminal refers to an application interface (app) opened by the user, such as a browser, a video playback tool, and the like. In actual use, these applications may generate various fault problems, such as flashback or error, etc., when the user can open the faulty operation interface of these applications, and then click the multitasking button on the terminal to issue the access control. The trigger signal of the center interface, the functions of this multitasking button are mainly:

1) Triggering to enter the control center interface, because the control center interface has a first trigger entry, and the first trigger entry is an activation entry of the fault feedback function, so that the fault can be reported and reported;

2) Take a screenshot of the operation interface displayed before clicking the multitasking button (of course, in addition to the screenshot at this timing, another implementation scheme may be applied, and the action of the screenshot is placed in step S102 to detect the first It is completed when the activation signal of the entry is triggered. Of course, those skilled in the art should know that the application is not limited to this. When the feedback is faulty, the screenshot needs to be attached, which will better explain the problem and make the processing personnel of the background service center more It is good to grasp the situation of the failure; this is also the reason why the user needs to operate the terminal to open the faulty operation interface of these applications, and then click on the multitasking case.

It should be noted that the multi-tasking button is an entry for triggering the control center interface that can perform fault feedback. When the multi-tasking button is clicked, an activation signal is triggered to start the control center interface. In actual use, it is not limited to the multi-tasking button of the terminal, but also can be a menu button, a custom button, a soft button, or even a voice trigger. The above is for the convenience of description, and is described by a multi-tasking button, but this is described. Those skilled in the art will appreciate that a variety of equivalents of the multitasking button functions as previously described may be implemented, and the present application is not limited to an implementation of multitasking buttons.

The terminal described herein may be a mobile terminal such as a mobile phone or a tablet computer, or may be a non-mobile terminal such as a desktop computer or a smart TV.

Step S102, detecting an activation signal for the first trigger entry, displaying a corresponding fault feedback interface, automatically loading a screenshot of the operation interface and the identified terminal account in the fault feedback interface;

If it is a screenshot taken when receiving the trigger signal entering the control center interface, after entering the control center interface through step S100, the user may not immediately trigger the first trigger entry to perform fault feedback (for example, due to some things) The discontinuity of the operation may cause the first trigger entry to be triggered after a period of time, or the user may not trigger the first trigger entry because the control center interface has other functions, and the user is likely to trigger not the first As a fault feedback function of the trigger entry, it is also possible that the user will immediately trigger the first trigger entry for fault feedback, and therefore the activation signal to the first trigger entry needs to be continuously detected.

After detecting the activation of the first trigger entry, a corresponding fault feedback interface is displayed, and the saved screenshot is automatically loaded in the fault feedback interface. When the saved screenshot is automatically loaded in the fault feedback interface, it is first detected whether a screenshot is saved in a period from the current time, and if so, a screenshot that is closest to the current time is automatically selected for loading.

As a condition for screening screenshots in a period from the current time, it is mainly considered: Case 1) In some cases, after entering the control center interface as in step S100, the user does not trigger the first trigger entry because the control center interface There are other functions, the user is likely to trigger the fault feedback function of the first trigger entry. At this time, the screenshot will still be taken in step S100. Of course, this screenshot is definitely not for reporting the fault interception. There are a lot of, when this operation activates the first trigger entry, in addition to this interception, the screenshots saved at this time may be intercepted a long time ago, not the target of this fault feedback;

Case 2) After the operation of step S100 is performed, the screenshot is completed, but the user does not immediately perform the operation of step S102, but delays the triggering of the first trigger entry, that is, from the completion of the screenshot to the automatic loading of the screenshot. The time interval is too long, and the accuracy of the fault returned by the user cannot be guaranteed at this time.

And automatically select a screenshot with the latest time from the current time to load. When there are multiple screenshots in the actual time period from the current time, only the last screenshot completed in step S100 is the current user preparation. The fault content of the feedback. For the processing of the screenshot in step S100, it is considered that in some cases, after entering the control center interface as in step S100, the user does not trigger the first trigger entry, but the screenshot has already occurred, so many screenshots are actually invalid screenshots. There is no practical effect, such screenshots can be cleaned regularly or the last screenshot can be deleted directly when it is detected that the user does not trigger the first trigger entry.

There is also an implementation method that does not take a screenshot when receiving the trigger signal entering the control center interface, but when the activation signal to the first trigger entry is detected in this step S102 (ie, the user triggers the first trigger) At the time of entry, at this time, by calling the task manager, the task corresponding to the lowest value flag (Flag) in the startup sequence needs to be retrieved, and the task corresponding to the lowest value flag is the most recent before entering the control center interface. For the task that is started, the content of the task manager and the startup sequence in this part can refer to the related description in step S202. After the recently opened task is found, a screenshot of the operation interface of the task is performed in the background. This screenshot is a screenshot of the operation interface in step S100, so that the screenshot can be automatically loaded in the fault feedback interface. . It should be noted that the present application can be implemented in the screenshot in step S100 and the selection of the screenshot in step S102.

The terminal account generally refers to a terminal account in a login state, so that after triggering the first trigger entry, the terminal is fully capable of automatically identifying the terminal account currently in the login, of course, if the current terminal does not log in to the terminal Account, but once logged in and recorded the terminal account in the local or cloud, the terminal also has the ability to automatically identify the terminal account. This account can be an email address, a mobile number, a terminal ID, and the like.

In this way, the terminal automatically loads the screenshot into the corresponding position in the fault feedback interface, and automatically sends the identified terminal account and the screenshot together to the background service center. The screenshot is convenient for the operation and maintenance personnel of the background service center to visually understand the current fault condition, and the terminal account is It is convenient for the operation and maintenance personnel to get in touch with the user in time to communicate and solve the problem.

Step S104, detecting the submission confirmation signal, sending the data loaded in the fault feedback interface to the background service center, and submitting a confirmation prompt to the user, and returning to the operation interface.

After clicking the corresponding button on the fault feedback interface, the user submits the screenshot and the terminal account in step S102, and then directly exits from the fault feedback interface to the operation interface opened before the trigger signal of the control center interface is sent in step S100.

As shown in FIG. 2, the method for fault feedback according to an embodiment of the present application includes:

Step S200: Receive a trigger signal entering the control center interface on an operation interface of the terminal, and display a control center interface, where the first trigger entry is displayed on the control center interface;

Referring to the description of step S100, details are not described again.

Step S202, detecting an activation signal for the first trigger entry, displaying a corresponding fault feedback interface, calling a name of an application corresponding to the operation interface, and displaying the name of the application in the fault feedback interface. Automatically loading the saved screenshot and the identified terminal account in the fault feedback interface;

Calling a task manager to retrieve a task corresponding to the lowest value flag (Flag) in the startup sequence, the task corresponding to the lowest value flag is the task that was recently opened before entering the control center interface (that is, the The task corresponding to the operation interface), and the application name corresponding to the recently opened task is selected from the mapping table of the task and the application name according to the recently opened task.

The task manager is an API function that manages tasks started in the system and maintains a startup sequence. For example, an application A is currently started, and the flag of the application A in the startup sequence is set to 0; then another application B is started, and the flag of the application B in the startup sequence is set to 0, and the application A is applied. The flag bit is set to 1; then another application C is started, and the flag of application C in the startup sequence is set to 0, and the flag of application B is set to 1, and the flag of application A is set to 2... By analogy, obviously, the larger the flag, the earlier the opening is, the smaller the flag is, indicating that the closer the opening time is, and the flag is 0, indicating that it is the task that has just started.

The mapping table between task and application name is pre-configured and saved locally, which can be called by the task manager. The mapping table is as follows, of course, those skilled in the art should know that The present application is not limited to this particular form of the mapping table.

任务ATask A	微信WeChat
任务BTask B	QQQQ
任务CTask C	浏览器Browser
任务DTask D	电子邮件e-mail

In this way, the terminal automatically loads the screenshot into the corresponding position in the fault feedback interface, automatically sends the identified terminal account and the screenshot together to the background service center, and also displays the name of the application in the fault feedback interface, and on the other hand, facilitates the user to confirm the report. The faulty application for the process is not confusing. On the other hand, the application name and screenshot together are more conducive to the operation and maintenance personnel of the background service center to accurately understand the current fault situation.

Regarding other parts of this step, referring to the description of step S102, details are not described again.

Step S204, detecting the submission confirmation signal, sending the name of the application, the loaded screenshot and the terminal account to the background service center, and submitting a confirmation prompt to the user, and returning to the operation interface.

Referring to the description of step S104, details are not described again.

As shown in FIG. 3, the method for fault feedback according to an embodiment of the present application includes:

Step S300, receiving a trigger signal entering the control center interface on an operation interface of the terminal, displaying a control center interface, where the first trigger entry is displayed on the control center interface;

Referring to the description of step S100, details are not described again.

Step S302, detecting an activation signal for the first trigger entry, displaying a corresponding fault feedback interface, automatically loading a screenshot of the operation interface and the identified terminal account in the fault feedback interface;

Referring to the description of step S102, details are not described again.

Step S304, providing a description window on the fault feedback interface, identifying and loading description information about the fault input by the user in the description window;

Because simply providing the name and screenshot of the application does not completely describe the fault, or that many faults are dynamic, not a screenshot can be clearly described. For dynamic processes The fault, for example, after the application is started, an add operation or a delete operation is performed, and after waiting for any time, the system will force the application to close. For such faults, it is obviously impossible to describe clearly through a screenshot. It must be accompanied by a description of the situation. This description is generally done by the user, so an entry that supports user input is required.

The solution of the present application is implemented by using a description window. The user can input a text in the description window to describe the fault condition, or input a voice or video described by the user about the fault itself in the description window to explain the fault condition. Of course, it is also possible to input the recording or screen recording video of the fault itself in the description window to explain the fault condition, and the terminal may identify the description information about the fault in the description window. Obviously, the input in the description window here refers not only to text input, but also to voice or video input, recording or screen recording video input. The input description information about the fault may be text description information and/or audio and video description information.

Step S306, detecting the submission confirmation signal, sending the description information about the fault input in the description window to the background service center along with the loaded screenshot and the terminal account, and submitting a confirmation prompt to the user, returning the description Operation interface.

The identified terminal account and screenshots, as well as the description information about the fault, are also sent to the background service center, which can be used by the operation and maintenance personnel of the background service center to completely understand the current fault situation, and there is almost no cognitive dead angle. Regarding the description of the other parts in this step with reference to step S104, details are not described again.

It should be noted that, in this embodiment, the manner of describing the information about the fault and the manner of the name applied in the previous embodiment may also be used in combination.

As shown in FIG. 4, the method for fault feedback according to an embodiment of the present application includes:

Step S400, receiving a trigger signal for entering the control center interface on an operation interface of the terminal, displaying a control center interface, where the first trigger entry is displayed on the control center interface;

Referring to the description of step S100, details are not described again.

Step S402, detecting an activation signal for the first trigger entry, displaying a corresponding fault feedback interface, automatically loading a screenshot of the operation interface and the identified terminal account in the fault feedback interface, respectively performing step S404 And/or step S406;

Referring to the description of step S102, details are not described again.

Step S404, providing an automatic uploading portal in the fault feedback interface, detecting an activation signal to the automatic uploading portal, displaying a manual selection interface, and displaying a screenshot for selecting loading in the manual selection interface, executing step S408;

There are multiple positions in the fault feedback interface where the screenshots are placed, that is to say, multiple screenshots can be loaded, and the screenshots automatically loaded in the fault feedback interface in step 402 are generally placed in the first position, and the automatic upload portal settings are automatically set. In the remaining positions, the user can enter the manual selection interface by triggering the automatic upload entry. The manual selection interface will list the screenshots that can be selected for loading, and load the images selected by the user in the remaining positions.

Step S406, providing a fault attribute selection entry in the fault feedback interface, detecting an activation signal for selecting the entry of the fault attribute, displaying a manual selection interface, and displaying a corresponding fault attribute option for selection in the manual selection interface, Entering the selected fault attribute option, executing step S408;

The fault attribute selection entry includes: a fault type selection entry and/or an appearance frequency selection entry.

For the fault attribute selection entry, the manual selection interface is displayed after activation. Generally, this interface is a drop-down menu, or a newly opened page lists all the options that can be clicked. For example, for the fault type selection entry, the fault attribute options that can be selected can be: default, slow response, unresponsive operation, forced exit, data loss, functional defects, improvement suggestions, insufficient design, other conditions, etc. Select the entry, the fault attribute options that can be selected can be: once, sometimes, every time, etc.

Step S408, detecting the submission confirmation signal, sending the selected fault attribute option, the loaded screenshot and the terminal account to the background service center, and submitting a confirmation prompt to the user, and returning to the operation interface.

Obviously, the fault attribute option is a kind of auxiliary data, but it can help the operation and maintenance personnel of the background service center to analyze the fault problem well, or help the operation and maintenance personnel of the background service center to classify the fault and assign it to the appropriate technician. Process it. In addition to the automatic loading of the screenshots, the screenshots manually selected by the user can provide a more comprehensive description and definition of the fault, because the perspective of the user's cognitive failure is more flexible than the machine perspective of the terminal. The other parts in this step refer to the description of step S104 and will not be described again.

It should be noted that, in this embodiment, the manner of the fault attribute option and/or the manual selection of the screenshot may be superimposed on the manner of the description information of the fault and the name of the application in the foregoing embodiment, or may be implemented in the foregoing manner. In the example, the way of describing the fault information and the name of the application are combined and used together to form a complete solution.

As shown in FIG. 5, the fault feedback device according to an embodiment of the present application includes:

The control center interface management module 500 is configured to receive a trigger signal for entering the control center interface on an operation interface of the terminal, and display a control center interface, where the first trigger entry is displayed on the control center interface;

The first triggering entry management module 502 is configured to detect an activation signal for the first triggering portal, display a corresponding fault feedback interface, automatically load a screenshot of the operating interface in the fault feedback interface, and identify the identified Terminal account

The submission confirmation management module 504 is configured to detect the submission confirmation signal, send the data loaded in the fault feedback interface to the background service center, and submit a confirmation prompt to the user, and return to the operation interface.

The screenshot of the operation interface is intercepted by the control center interface management module 500 when receiving the trigger signal entering the control center interface or when the first trigger entry management module 502 detects the activation signal for the first trigger entry. .

The above terminal account includes: a terminal account in a login state, or a terminal account that has been logged in and recorded.

When the first trigger entry management module 502 receives the activation signal for the first trigger entry, it is also used to retrieve the name of the application corresponding to the operation interface, and display the name of the application in the In the fault feedback interface;

The first trigger entry management module 502 is further configured to invoke a task manager to retrieve a task corresponding to a flag with the lowest value in the startup sequence when the name of the application corresponding to the operation interface is retrieved, and the flag with the lowest value corresponds to the flag. The task is the task corresponding to the operation interface, and the application name corresponding to the task corresponding to the operation interface is selected from the mapping table of the task and the application name according to the task corresponding to the operation interface.

The first trigger entry management module 502 automatically loads the saved screenshot on the fault feedback interface Specifically, it is used to detect whether a screenshot is saved in a period from the current time, and if so, automatically select a screenshot with the latest interception time from the current time to load.

When the activation signal of the first trigger entry is detected, the first trigger entry management module 502, in addition to the above operation, the first trigger entry management module 502 also provides a description window on the fault feedback interface, identifying and carrying Entering description information about the fault input by the user in the description window, wherein the description information about the fault input in the description window includes: text description information, and/or audio and video description information; and/or,

The first triggering entry management module 502 further provides an automatic uploading portal in the fault feedback interface, detects an activation signal to the automatic uploading portal, displays a manual selection interface, and displays a screenshot for selecting loading in the manual selection interface. , loading the selected screenshot; and/or,

The first trigger entry management module 502 further provides a fault attribute selection entry in the fault feedback interface, detects an activation signal for selecting the fault attribute entry, displays a manual selection interface, and displays the selected one in the manual selection interface. The corresponding fault attribute option loads the selected fault attribute option, wherein the fault attribute selects an entry, including: a fault type selection entry and/or an appearance frequency selection entry.

The fault feedback device as viewed in FIG. 5 corresponds to the features and schemes of the method embodiments shown in FIGS. 1-4. For the deficiencies described in the fault feedback device, please refer to FIG. 1-4. A description of the illustrated method embodiment.

The application will be described below through an application example. The terminal uses a mobile phone as an example for description, but the terminal of the present application is not limited thereto.

When users recently used the mobile phone's browser, they found that the browser was forcibly quit by the system, and this situation has become the norm in recent times, but it is impossible to find out the reason. It is hoped that the fault feedback mechanism will be used to report the fault to the backend server of the mobile phone, so as to find a solution.

Because the browser is faulty, the user clicks the browser icon on the system interface of the mobile phone to open the browser interface first, as shown in Figure 6. Of course, the browser is not necessarily the initial open state, and it is also possible to report the failure by using the open web page and the like.

In the open state of the browser interface as shown in FIG. 6, the user clicks the multitasking button on the keyboard of the mobile phone to automatically take a screenshot and save the opened browser interface, and simultaneously call out the control center interface, such as As shown in FIG. 7, it can be seen from the control center interface in FIG. 7 that the question mark icon pointed by the cursor is the first trigger entry.

At the same time, you can see that there are many other function icons in the control center interface. Therefore, for the mobile phone, it cannot be confirmed that each time the user enters the control center interface, it is for fault reporting, but the screenshot operation is executed every time the user control center interface is entered. . For example, after the user enters the control center interface, there is no first time question mark icon, but the wireless connection icon is triggered to open the wireless network connection, and the screen rotation icon is triggered to activate the smart rotation function of the mobile phone screen, and then the question mark icon is triggered. Note that the time it takes to trigger the wireless connection icon and trigger the screen rotation icon is approximately less than 2 minutes, so the time to trigger the question mark icon is about 2 minutes from the execution of the screenshot.

In this case, do the following:

1) The mobile phone detects whether there are screenshots saved in the last 5 minutes. Obviously, at least the screenshot of the browser interface will be found. Of course, other screenshots may be found. Of course, the latest screenshot from the current moment is definitely a screenshot of the browser interface, so Automatically select the latest screenshot - a screenshot of the browser interface to load, as shown in Figure 8. Of course, it is also shown in FIG. 8 that an automatic upload entry is provided after the screenshot is loaded, that is, a plus icon, the user clicks on the plus icon, the mobile phone displays a manual selection interface, and displays a screenshot for selection and loading in the manual selection interface. The user clicks on the screenshot that he also wants to load, and the mobile phone loads the selected screenshot.

2) The mobile phone needs to call the task manager to retrieve the task in the startup sequence with the flag value of flag 0, find the task com.android.browser, and map the task and application name according to com.android.browser Looking up, it is found that the corresponding app name of com.android.browser is "browser", and the name "browser" of the application is displayed in the corresponding position in the fault feedback interface, as shown in FIG. After the above two operations are completed, a description window is also provided on the fault feedback interface, and the user inputs the “forced exit after 5 seconds of use” by calling the input method in the description window, and the mobile phone recognizes and loads the user in the The description information about the fault input in the description window is as shown in FIG. 8.

In addition, in the fault feedback interface, the user triggers the fault type button, and the manual selection interface is displayed, which can be implemented by using a pull-down menu, and options are provided in the pull-down menu, such as “default, slow response, no response, forced exit, data” Loss, functional defects, improvement suggestions, inadequate design, other situations, the user selected the corresponding fault attribute option "system forced exit", the drop-down menu is closed, and the "system forced exit" is displayed, as shown in Figure 8.

In the fault feedback interface, the user triggers the frequency button, and the manual selection interface is displayed, which can be implemented by using a pull-down menu, and an option is provided in the drop-down menu, such as “appear once, sometimes, every time”, the corresponding fault selected by the user. The attribute option "Every time must be", the drop-down menu is collapsed, and "Every time must be present" is displayed, as shown in Figure 8.

The user confirms the application name, description information, loaded screenshot, fault type, frequency of occurrence, click submit confirmation, the mobile phone sends the data loaded in the fault feedback interface to the background service center, and displays on the interface of the mobile phone. A prompt box prompts the user to submit the background, as shown in FIG. 9, and returns to the operation interface. The background service center can automatically process the fault according to the data of the fault feedback interface. If the fault is not processed, the fault can be effectively classified according to the data of the fault feedback interface, and sent to the operation and maintenance personnel of the corresponding technical field for processing.

The application will be described below by another application example. The terminal uses a mobile phone as an example for description, but the terminal of the present application is not limited thereto.

The difference from the previous application example is that, in the open state of the browser interface as shown in FIG. 6, the user clicks the multitasking button on the keyboard of the mobile phone, and does not take a screenshot and save the browser interface, just the control center interface. As shown in Figure 7.

There are many other function icons in the control center interface. For the mobile phone, it is not confirmed that every time the user enters the control center interface, it is for fault reporting. In order to avoid the excessive impact of the screenshots on the source of mobile phone resources, only the user triggers the question mark icon. At the same time, the screenshot is taken and the fault feedback interface is opened. After the operation is the same, the mobile phone detects whether the screenshot is saved in the last 5 minutes, loads the screenshot of the browser, and the mobile phone needs to call the task manager to obtain the name of the application, the browser, and the description information. The fault type and the appearance frequency are displayed together in the corresponding position in the fault feedback interface, as shown in FIG. 8, and the previous application example can be referred to for these parts.

The various component embodiments of the present application can be implemented in hardware, or in a software module running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or digital signal processor (DSP) may be used in practice to implement some or all of the functionality of some or all of the components in accordance with embodiments of the present application.

The present application also provides a fault feedback device, including: a memory, a processor, wherein the memory is configured to store one or more instructions, wherein the one or more instructions are for execution by the processor ;

The application can also be implemented as a device or device program (e.g., a computer program and a computer program product) for performing some or all of the methods described herein. Such a program implementing the present application may be stored on a computer readable medium or may be in the form of one or more signals. Such signals may be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.

"an embodiment," or "an embodiment," or "one or more embodiments" as used herein means that the particular features, structures, or characteristics described in connection with the embodiments are included in at least one embodiment of the present application. In addition, it is noted that the phrase "in one embodiment" is not necessarily referring to the same embodiment.

In the description provided herein, numerous specific details are set forth. However, it is understood that the embodiments of the present application can be practiced without these specific details. In some instances, well-known methods, structures, and techniques are not shown in detail so as not to obscure the understanding of the description. It should be noted that the above-described embodiments are illustrative of the present application and are not intended to limit the scope of the application, and those skilled in the art can devise alternative embodiments without departing from the scope of the appended claims. In In the claims, any reference signs placed between parentheses shall not be construed as a limitation. The word "comprising" does not exclude the presence of the elements or steps that are not recited in the claims. The word "a" or "an" The application can be implemented by means of hardware comprising several distinct elements and by means of a suitably programmed computer.

In the unit claims enumerating several means, several of these means can be embodied by the same hardware item. The use of the words first, second, and third does not indicate any order. These words can be interpreted as names.

In addition, it should be noted that the language used in the specification has been selected for the purpose of readability and teaching, and is not intended to be interpreted or limited. Therefore, many modifications and changes will be apparent to those skilled in the art without departing from the scope of the invention. The disclosure of the present application is intended to be illustrative, and not restrictive, and the scope of the application is defined by the appended claims.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to the program instructions. The foregoing program may be stored in a computer readable storage medium, and the program is executed when executed. The foregoing steps include the steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Finally, it should be noted that the above embodiments are only for explaining the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that The technical solutions described in the foregoing embodiments may be modified, or some or all of the technical features may be equivalently replaced; and the modifications or substitutions do not deviate from the technical solutions of the embodiments of the present application. range.

Claims

A fault feedback method, comprising:

Receiving a trigger signal for entering the control center interface on an operation interface of the terminal, displaying a control center interface, where the first trigger entry is displayed on the control center interface;

Detecting an activation signal for the first trigger entry, displaying a corresponding fault feedback interface, automatically loading a screenshot of the operation interface and the identified terminal account in the fault feedback interface;

A submission confirmation signal is detected, and the data loaded in the fault feedback interface is sent to the background service center, and the user is presented with a confirmation prompt to return to the operation interface.
A fault feedback method according to claim 1, wherein

The screenshot of the operation interface is intercepted when the trigger signal for entering the control center interface is intercepted or when the activation signal for the first trigger entry is detected.
The fault feedback method according to claim 1, wherein an activation signal for the first trigger entry is detected, a corresponding fault feedback interface is displayed, and a screenshot of the operation interface is automatically loaded in the fault feedback interface. And the identified terminal accounts, including:

The name of the application corresponding to the operation interface is retrieved, and the name of the application is displayed in the fault feedback interface.
The fault feedback method according to claim 3, wherein the calling the name of the application corresponding to the operation interface further includes:

Calling the task manager to retrieve a task corresponding to the lowest value of the flag in the startup sequence, the task corresponding to the lowest value flag is the task corresponding to the operation interface, and according to the task corresponding to the operation interface from the task and application Select the application name corresponding to the task corresponding to the operation interface in the mapping table of the name.
The fault feedback method of claim 1 , wherein automatically loading a screenshot of the operation interface in the fault feedback interface further comprises:

It is detected whether a screenshot is saved in a period from the current time, and if so, a screenshot with the latest interception time from the current time is automatically selected for loading.
The fault feedback method according to claim 1, wherein an activation signal to the first trigger entry is detected, and a corresponding fault feedback interface is displayed, automatically in the fault feedback boundary. The screenshot of loading the operation interface and the identified terminal account also include:

A description window is provided on the fault feedback interface to identify and load description information about the fault input by the user in the description window.
The fault feedback method according to claim 6, wherein the description information about the fault input in the description window comprises: text description information, and/or audio and video description information.
The fault feedback method of claim 1 , further comprising: automatically loading the screenshot of the operation interface and the identified terminal account after the fault feedback interface is loaded, and before detecting the submission of the confirmation signal, further comprising:

An automatic uploading portal is provided in the fault feedback interface, an activation signal for the automatic uploading portal is detected, a manual selection interface is displayed, and a screenshot for selecting loading is displayed in the manual selection interface, and the selected screenshot is loaded.
The fault feedback method of claim 1 , further comprising: automatically loading the screenshot of the operation interface and the identified terminal account after the fault feedback interface is loaded, and before detecting the submission of the confirmation signal, further comprising:

Providing a fault attribute selection entry in the fault feedback interface, detecting an activation signal for selecting the entry of the fault attribute, displaying a manual selection interface, and displaying a corresponding fault attribute option for selection in the manual selection interface, and loading is selected Fault attribute options.
The fault feedback method according to claim 9, wherein the fault attribute selection entry comprises: a fault type selection entry and/or an appearance frequency selection entry.
The fault feedback method according to claim 1, wherein the terminal account comprises: a terminal account in a login state, or a terminal account that has been logged in and recorded.
A fault feedback device, comprising:

The control center interface management module is configured to receive a trigger signal for entering the control center interface on an operation interface of the terminal, and display a control center interface, where the first trigger entry is displayed on the control center interface;

a first trigger entry management module, configured to detect an activation signal for the first trigger entry, display a corresponding fault feedback interface, automatically load a screenshot of the operation interface and the identified terminal in the fault feedback interface Account

The submission confirmation management module is configured to detect the submission confirmation signal, send the data loaded in the fault feedback interface to the background service center, and submit a confirmation prompt to the user, and return to the operation interface.
A fault feedback device according to claim 12, wherein

The first triggering entry management module is configured to retrieve the name of the application corresponding to the operation interface when the activation signal of the first trigger entry is detected, and display the name of the application in the In the fault feedback interface.
The fault feedback device of claim 13 wherein:

The first trigger entry management module is configured to invoke a task manager to retrieve a task corresponding to a flag with the lowest value in the startup sequence when the name of the application corresponding to the operation interface is retrieved, and the flag with the lowest value corresponds to the flag The task is the task corresponding to the operation interface, and the application name corresponding to the task corresponding to the operation interface is selected from the mapping table of the task and the application name according to the task corresponding to the operation interface.
A fault feedback device according to claim 12, wherein

The first trigger entry management module automatically detects whether the saved screenshot is saved in the time interval from the current time when the saved feedback screenshot is loaded, and if so, automatically selects the intercept time from the current time. A recent screenshot is loaded.
A fault feedback device according to claim 12, wherein

The first trigger entry management module further provides a description window on the fault feedback interface when detecting an activation signal for the first trigger entry, and identifies and loads a fault about the user input in the description window. Descriptive information, wherein the description information about the fault input in the description window includes: text description information, and/or audio and video description information.
A fault feedback device according to claim 12, wherein

The first triggering entry management module further provides an automatic uploading portal in the fault feedback interface, detects an activation signal to the automatic uploading portal, displays a manual selection interface, and displays the selected loading in the manual selection interface. Screenshot, loading the selected screenshot.
A fault feedback device according to claim 12, wherein

The first triggering entry management module further provides fault attribute selection in the fault feedback interface Selecting the portal, detecting an activation signal for selecting the entry of the fault attribute, displaying a manual selection interface, and displaying a corresponding fault attribute option for selection in the manual selection interface, and loading the selected fault attribute option.
A fault feedback device, comprising:

a memory, a processor, wherein the memory is configured to store one or more instructions, wherein the one or more instructions are for execution by the processor;

The processor is configured to receive a trigger signal that enters the control center interface on an operation interface of the terminal, and display a control center interface, where the first trigger entry is displayed on the control center interface; An activation signal triggering the portal, displaying a corresponding fault feedback interface, automatically loading a screenshot of the operation interface and the identified terminal account in the fault feedback interface; detecting a submission confirmation signal, and the fault feedback interface is The loaded data is sent to the background service center, and the user is presented with a confirmation prompt to return to the operation interface.