WO2016155430A1 - 故障反馈方法及故障反馈装置 - Google Patents

故障反馈方法及故障反馈装置 Download PDF

Info

Publication number
WO2016155430A1
WO2016155430A1 PCT/CN2016/074127 CN2016074127W WO2016155430A1 WO 2016155430 A1 WO2016155430 A1 WO 2016155430A1 CN 2016074127 W CN2016074127 W CN 2016074127W WO 2016155430 A1 WO2016155430 A1 WO 2016155430A1
Authority
WO
WIPO (PCT)
Prior art keywords
interface
fault
fault feedback
screenshot
entry
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2016/074127
Other languages
English (en)
French (fr)
Inventor
索浩森
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lemobile Information Technology (Beijing) Co Ltd
Original Assignee
Lemobile Information Technology (Beijing) Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lemobile Information Technology (Beijing) Co Ltd filed Critical Lemobile Information Technology (Beijing) Co Ltd
Publication of WO2016155430A1 publication Critical patent/WO2016155430A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance

Definitions

  • the present application relates to the field of network communication technologies, and in particular, to a fault feedback method and a fault feedback device.
  • 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.
  • a fault feedback method 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • description information about the fault input in the description window includes: text description information, and/or audio and video description information.
  • 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.
  • 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.
  • the fault attribute selection entry includes: a fault type selection entry and/or an appearance frequency selection entry.
  • the terminal account includes: a terminal account in a login state, or a terminal account that has logged in and recorded.
  • a fault feedback device 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the fault attribute selection entry includes: a fault type selection entry and/or an appearance frequency selection entry.
  • the terminal account includes: a terminal account in a login state, or a terminal account that has logged in and recorded.
  • 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.
  • a fault feedback apparatus 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the processor is further configured to: the fault attribute selection entry, comprising: a fault type selection entry and/or an appearance frequency selection entry.
  • 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.
  • 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.
  • 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.
  • FIG. 1 is a flow chart schematically showing a fault feedback method according to an embodiment of the present application
  • FIG. 2 is a flow chart schematically showing a fault feedback method according to an embodiment of the present application
  • FIG. 3 is a flow chart schematically showing a fault feedback method according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram showing the flow of a fault feedback method according to an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a fault feedback apparatus according to an embodiment of the present application.
  • 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.
  • a fault feedback method 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.
  • 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:
  • step S102 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.
  • the application is not limited to this.
  • 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.
  • the multi-tasking button is an entry for triggering the control center interface that can perform fault feedback.
  • an activation signal is triggered to start the control center interface.
  • 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.
  • 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;
  • 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
  • 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.
  • a corresponding fault feedback interface is displayed, and the saved screenshot is automatically loaded in the fault feedback interface.
  • 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.
  • Case 1 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;
  • step S100 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.
  • step S100 automatically selects a screenshot with the latest time from the current time to load.
  • the last screenshot completed in step S100 is the current user preparation.
  • the fault content of the feedback 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.
  • step S102 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)
  • 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.
  • the content of the task manager and the startup sequence in this part can refer to the related description in step S202.
  • 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. .
  • 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.
  • 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.
  • the user 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.
  • the method for fault feedback 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;
  • 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;
  • 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...
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • step S104 details are not described again.
  • 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;
  • 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;
  • 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;
  • 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.
  • the recording or screen recording video of the fault itself in the description window may identify the description information about the fault in the description window.
  • 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.
  • 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.
  • 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;
  • 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;
  • 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;
  • the screenshots 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.
  • 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.
  • the manual selection interface is displayed after activation.
  • this interface is a drop-down menu, or a newly opened page lists all the options that can be clicked.
  • 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.
  • 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.
  • 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.
  • 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.
  • the way of describing the fault information and the name of the application are combined and used together to form a complete solution.
  • the fault feedback device 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.
  • the first trigger entry management module 502 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.
  • the first trigger entry management module 502 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.
  • FIG. 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 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.
  • DSP digital signal processor
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the processor is further configured to: the fault attribute selection entry, comprising: a fault type selection entry and/or an appearance frequency selection entry.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • phrase "in one embodiment" is not necessarily referring to the same embodiment.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

提供一种故障反馈方法及故障反馈装置，所述方法包括：在终端的一操作界面上，收到进入控制中心界面的触发信号，显示控制中心界面，所述控制中心界面上显示有第一触发入口；检测到对所述第一触发入口的激活信号，显示相应的故障反馈界面，自动在所述故障反馈界面载入所述操作界面的截图以及所识别到的终端账户；检测到提交确认信号，将所述故障反馈界面中所载入的数据发送到后台服务中心，并对用户进行提交确认提示，返回所述操作界面。该方法通过故障反馈界面，将描述故障的各种信息组合在一起，更加有利于后台服务中心的运维人员准确地了解到故障情况，使故障得到妥善的、正确的处理，提高故障回报的效率和准确性。

Description

故障反馈方法及故障反馈装置
交叉引用
本申请引用于2015年03月27日递交的名称为“故障反馈方法及故障反馈装置”的第201510140169.1号中国专利申请，其通过引用被全部并入本申请。
技术领域
本申请涉及网络通信技术领域，尤其涉及一种故障反馈方法及故障反馈装置。
背景技术
现今，终端在出厂时往往就预安装有应用程序，这些应用程序很大一部分是生产厂商自行开发并安装的，还有一部分可能是第三方软件。在实际使用中，这些应用程序很可能会发生各种使用故障，这是非常常见的，有些故障可能普通用户很容易解决，但是对于一些故障可能需要专业人员处理才可以解决。
但是因为这些应用程序有很大一部分是生产厂商自行开发的，对于这些应用程序，不论是应用程序本身，还是应用程序与操作系统的兼容程度，生产厂商的程序开发人员都是最为了解的，显然由生产厂商的程序开发人员对这些故障进行处理是最适宜的，他们不仅可以对个体提供直接的解决方案，甚至当这类问题普遍存在时，可以更好地直接推出在面对整体用户的解决方案。但是目前对于这类应用程序的故障，用户并没有一个能够智能处理、自适应程度高的故障反馈模式。现有的方案因为手动操作过多，一方面造成了用户操作困难，直接影响了用户的反馈热情，另一方面也造成了故障汇报的不清晰，使运维人员不能清晰获知故障情况。
而对于终端上的第三方软件，也存在类似上述的问题。第三方软件可以是后续安装的，也可以是出厂预装的，但是无论哪种安装方式，也会不可避免的会存在运行故障。对于这些故障，不论是从改进软件的角度还是为用户 解决问题的角度，第三方软件的开发人员也是有意愿尽快、准确地获知故障情况的，但是第三方软件显然缺少这样一种获取故障反馈的途径。
因此，如何解决现有的缺少故障反馈途径、故障汇报操作困难以及故障汇报不清晰准确的问题，便成为亟待解决的技术问题。
发明内容
鉴于上述目的，提出了本申请以便提供一种克服上述问题或者至少部分地解决或者减缓上述问题的故障反馈方法及故障反馈装置。
根据本申请的一个方面，提供了一种故障反馈方法，包括：在终端的一操作界面上，收到进入控制中心界面的触发信号，显示控制中心界面，所述控制中心界面上显示有第一触发入口；检测到对所述第一触发入口的激活信号，显示相应的故障反馈界面，自动在所述故障反馈界面载入所述操作界面的截图以及所识别到的终端账户；检测到提交确认信号，将所述故障反馈界面中所载入的数据发送到后台服务中心，并对用户进行提交确认提示，返回所述操作界面。
进一步地，所述操作界面的截图为收到进入控制中心界面的触发信号时截取的或者检测到对所述第一触发入口的激活信号时截取的。
进一步地，检测到对所述第一触发入口的激活信号，显示相应的故障反馈界面，自动在所述故障反馈界面载入所述操作界面的截图以及所识别到的终端账户，还包括：调取所述操作界面对应的应用的名称，并将所述应用的名称显示在所述故障反馈界面中。
进一步地，调取所述操作界面对应的应用的名称，包括：调用任务管理器，检索启动序列中数值最低的标志位对应的任务，所述数值最低的标志位对应的任务是所述操作界面对应的任务，并根据所述操作界面对应的任务从任务与应用名称的映射表中选中所述操作界面对应的任务相应的应用名称。
进一步地，自动在所述故障反馈界面载入所述操作界面的截图，包括：检测在距当前时间的一时段内是否保存有截图，如果有，自动选取截取时间距当前时间最近的一张截图进行加载。
进一步地，检测到对所述第一触发入口的激活信号，显示相应的故障反 馈界面，自动在所述故障反馈界面载入所述操作界面的截图以及所识别到的终端账户，还包括：在所述故障反馈界面提供一描述窗口，识别并载入用户在所述描述窗口内输入的关于故障的描述信息。
进一步地，在所述描述窗口内输入的关于故障的描述信息，包括：文字描述信息，和/或音视频描述信息。
进一步地，自动在所述故障反馈界面载入所述操作界面的截图以及所识别到的终端账户之后，检测到提交确认信号之前，还包括：在所述故障反馈界面中提供自动上传入口，检测到对所述自动上传入口的激活信号，显示手动选取界面，并在手动选取界面内显示供选择加载的截图，载入被选中的截图。
进一步地，自动在所述故障反馈界面载入所述操作界面的截图以及所识别到的终端账户之后，检测到提交确认信号之前，还包括：在所述故障反馈界面中提供故障属性选择入口，检测到对所述故障属性选择入口的激活信号，显示手动选取界面，并在手动选取界面内显示供选择的相应故障属性选项，载入被选中的故障属性选项。
进一步地，所述故障属性选择入口，包括：故障类型选择入口和/或出现频率选择入口。
进一步地，所述终端账户，包括：处于登陆状态的终端账户，或曾登陆过并记录的终端账户。
根据本申请的一个方面，还提供了一种故障反馈装置，包括：控制中心界面管理模块，用于在终端的一操作界面上，收到进入控制中心界面的触发信号，显示控制中心界面，所述控制中心界面上显示有第一触发入口；第一触发入口管理模块，用于检测到对所述第一触发入口的激活信号，显示相应的故障反馈界面，自动在所述故障反馈界面载入所述操作界面的截图以及所识别到的终端账户；提交确认管理模块，用于检测到提交确认信号，将所述故障反馈界面中所载入的数据发送到后台服务中心，并对用户进行提交确认提示，返回所述操作界面。
进一步地，第一触发入口管理模块，收到检测到对所述第一触发入口的激活信号时，还用于调取所述操作界面对应的应用的名称，并将所述应用的 名称显示在所述故障反馈界面中。
进一步地，第一触发入口管理模块，调取所述操作界面对应的应用的名称时，用于调用任务管理器，检索启动序列中数值最低的标志位对应的任务，所述数值最低的标志位对应的任务是所述操作界面对应的任务，并根据所述操作界面对应的任务从任务与应用名称的映射表中选中所述操作界面对应的任务相应的应用名称。
进一步地，第一触发入口管理模块自动在所述故障反馈界面载入所保存的截图时，具体用于检测在距当前时间的一时段内是否保存有截图，如果有，自动选取截取时间距当前时间最近的一张截图进行加载。
进一步地，第一触发入口管理模块，检测到对所述第一触发入口的激活信号时，还在所述故障反馈界面提供一描述窗口，识别并载入用户在所述描述窗口内输入的关于故障的描述信息，其中，在所述描述窗口内输入的关于故障的描述信息，包括：文字描述信息，和/或音视频描述信息。
进一步地，第一触发入口管理模块，还在所述故障反馈界面中提供自动上传入口，检测到对所述自动上传入口的激活信号，显示手动选取界面，并在手动选取界面内显示供选择加载的截图，载入被选中的截图。
进一步地，第一触发入口管理模块，还在所述故障反馈界面中提供故障属性选择入口，检测到对所述故障属性选择入口的激活信号，显示手动选取界面，并在手动选取界面内显示供选择的相应故障属性选项，载入被选中的故障属性选项。
进一步地，所述故障属性选择入口，包括：故障类型选择入口和/或出现频率选择入口。
进一步地，所述终端账户，包括：处于登陆状态的终端账户，或曾登陆过并记录的终端账户。
进一步地，所述操作界面的截图为控制中心界面管理模块在收到进入控制中心界面的触发信号时截取的或者第一触发入口管理模块在检测到对所述第一触发入口的激活信号时截取的。
根据本申请的一个方面，还提供了一种故障反馈装置，包括：内存、处理器，其中，所述内存，用于存储一条或多条指令，其中，所述一条或多条 指令以供所述处理器调用执行；
所述处理器被配置为：在终端的一操作界面上，收到进入控制中心界面的触发信号，显示控制中心界面，所述控制中心界面上显示有第一触发入口；检测到对所述第一触发入口的激活信号，显示相应的故障反馈界面，自动在所述故障反馈界面载入所述操作界面的截图以及所识别到的终端账户；检测到提交确认信号，将所述故障反馈界面中所载入的数据发送到后台服务中心，并对用户进行提交确认提示，返回所述操作界面。
进一步地，所述处理器进一步被配置为：收到检测到对所述第一触发入口的激活信号时，调取所述操作界面对应的应用的名称，并将所述应用的名称显示在所述故障反馈界面中。
进一步地，所述处理器进一步被配置为：调取所述操作界面对应的应用的名称时，调用任务管理器，检索启动序列中数值最低的标志位对应的任务，所述数值最低的标志位对应的任务是所述操作界面对应的任务，并根据所述操作界面对应的任务从任务与应用名称的映射表中选中所述操作界面对应的任务相应的应用名称。
进一步地，所述处理器进一步被配置为：自动在所述故障反馈界面载入所保存的截图时，检测在距当前时间的一时段内是否保存有截图，如果有，自动选取截取时间距当前时间最近的一张截图进行加载。
进一步地，所述处理器进一步被配置为：检测到对所述第一触发入口的激活信号时，还在所述故障反馈界面提供一描述窗口，识别并载入用户在所述描述窗口内输入的关于故障的描述信息，其中，在所述描述窗口内输入的关于故障的描述信息，包括：文字描述信息，和/或音视频描述信息。
进一步地，所述处理器进一步被配置为：在所述故障反馈界面中提供自动上传入口，检测到对所述自动上传入口的激活信号，显示手动选取界面，并在手动选取界面内显示供选择加载的截图，载入被选中的截图。
进一步地，所述处理器进一步被配置为：在所述故障反馈界面中提供故障属性选择入口，检测到对所述故障属性选择入口的激活信号，显示手动选取界面，并在手动选取界面内显示供选择的相应故障属性选项，载入被选中的故障属性选项。
进一步地，所述处理器进一步被配置为：所述故障属性选择入口，包括：故障类型选择入口和/或出现频率选择入口。
进一步地，所述处理器进一步被配置为：所述终端账户，包括：处于登陆状态的终端账户，或曾登陆过并记录的终端账户。
进一步地，所述处理器进一步被配置为：所述操作界面的截图为在收到进入控制中心界面的触发信号时截取的或者第一触发入口管理模块在检测到对所述第一触发入口的激活信号时截取的。
与现有的方案相比，本申请所获得的技术效果：可以通过故障反馈界面，将描述故障的各种信息组合在一起，从多个角度多个方面对故障进行形象地、理性地定义和展示，更加有利于后台服务中心的运维人员准确地了解到故障情况，使故障得到妥善的、正确的处理，提高故障回报的效率和准确性。
当然，实施本申请的任一产品必不一定需要同时达到以上所述的所有技术效果。
上述说明仅是本申请技术方案的概述，为了能够更清楚了解本申请的技术手段，而可依照说明书的内容予以实施，并且为了让本申请的上述和其它目的、特征和优点能够更明显易懂，以下特举本申请的具体实施方式。
附图说明
通过阅读下文优选实施方式的详细描述，各种其他的优点和益处对于本领域普通技术人员将变得清楚明了。附图仅用于示出优选实施方式的目的，而并不认为是对本申请的限制。而且在整个附图中，用相同的参考符号表示相同的部件。在附图中：
图1示意性示出了根据本申请一个实施例所述的故障反馈方法的流程图；
图2示意性示出了根据本申请一个实施例所述的故障反馈方法的流程图；
图3示意性示出了根据本申请一个实施例所述的故障反馈方法的流程图；
图4示意性示出了根据本申请一个实施例所述的故障反馈方法的流程 图；
图5示意性示出了根据本申请一个实施例所述的故障反馈装置的结构图；
图6示意性示出了根据本申请一个应用实例所述的使用示意图；
图7示意性示出了根据本申请一个应用实例所述的使用示意图；
图8示意性示出了根据本申请一个应用实例所述的使用示意图；
图9示意性示出了根据本申请一个应用实例所述的使用示意图。
具体实施方式
下面结合附图和具体的实施方式对本申请作进一步的描述。如图1所示，为本申请一个实施例所述的故障反馈方法，包括：
步骤S100，在终端的一操作界面上，收到进入控制中心界面的触发信号，显示控制中心界面，所述控制中心界面上显示有第一触发入口；
终端的操作界面，是指用户开启的一个应用程序的界面(app)，比如浏览器、影音播放工具等等。实际使用中，这些应用程序可能产生了各种故障问题，比如闪退或者报错等等，这时用户可以打开这些应用程序的发生故障的操作界面，然后点击终端上的多任务按键从而发出进入控制中心界面的触发信号，这个多任务按键的功能主要有：
1)触发进入控制中心界面，因为控制中心界面中具有第一触发入口，这个第一触发入口就是故障反馈功能的激活入口，这样就可以对故障进行反馈上报；
2)对点击多任务按键之前所显示的操作界面进行截图(当然，除了在这个时机可以截图，也可以应用另一种实现方案，将截图的动作放到步骤S102中检测到对所述第一触发入口的激活信号时来完成，当然本领域技术人员应当知晓本申请并不限于此)，后面反馈故障时需要附上这张截图，会更好的说明问题，让后台服务中心的处理人员更好的掌握故障发生的情况；这也是需要用户操作终端打开这些应用程序的发生故障的操作界面之后，再点击多任务案件的原因。
需要说明的是，这个多任务按键是触发进入可以进行故障反馈的控制中心界面的入口，点击多任务按键后会触发激活信号从而启动控制中心界面。实际使用中，不仅局限于通过终端的多任务按键来实现，也可以是菜单按键、自定义按键、软按键、甚至是语音触发，以上是为了描述简便，以多任务按键来进行描述，但是本领域技术人员应当知晓，可以实现多任务按键功能的如前所述的多种等同方式，本申请并不限于多任务按键这一种实现方式。
这里所述的终端，可以是手机、平板电脑等移动终端，也可以是台式机电脑、智能电视等非移动终端。
步骤S102，检测到对所述第一触发入口的激活信号，显示相应的故障反馈界面，自动在所述故障反馈界面载入所述操作界面的截图以及所识别到的终端账户；
如果是在收到进入控制中心界面的触发信号时进行的截图，在通过步骤S100进入控制中心界面后，用户可能并不会立刻就触发所述第一触发入口进行故障反馈(比如因为一些事造成操作的不连续导致会间隔一段时间再触发所述第一触发入口)，也可能用户并没有触发所述第一触发入口，因为控制中心界面还有其他的功能，用户很可能触发的并不是第一触发入口的故障反馈功能，还有可能用户会立刻触发所述第一触发入口进行故障反馈，因此需要不断检测对所述第一触发入口的激活信号。
检测到对所述第一触发入口的激活后，显示相应的故障反馈界面，自动在所述故障反馈界面载入所保存的截图。自动在所述故障反馈界面载入所保存的截图时，首先检测在距当前时间的一时段内是否保存有截图，如果有，自动选取截取时间距当前时间最近的一张截图进行加载。
通过距当前时间的一时段内作为筛选截图的条件，主要是考虑：情况1)在一些情况下通过如步骤S100进入控制中心界面后，用户并没有触发所述第一触发入口，因为控制中心界面还有其他的功能，用户很可能触发的并不是第一触发入口的故障反馈功能，这时步骤S100中还是会进行截图，当然这个截图肯定不是为了汇报故障截取的，类似这样的所保存截图肯定有很多，当本次操作激活第一触发入口时，这时所保存的截图中除了本次截取的，还有一些可能是很久之前截取的，并不是本次故障反馈的目标；
情况2)在执行完步骤S100的操作后，完成了截图，但是用户并没有立刻执行本步骤S102的操作，而是延迟很久才触发第一触发入口，也就是说，从截图完成到自动加载截图的时间间隔过长，此时并不能保证用户反馈的故障的准确程度。
而自动选取截取时间距当前时间最近的一张截图进行加载，当在实际使用中距当前时间的一时段内存在多幅截图时，只有步骤S100中所完成的最近一次的截图才是当前用户准备反馈的故障内容。对于在步骤S100中进行截图的处理，考虑到在一些情况下通过如步骤S100进入控制中心界面后，用户并没有触发所述第一触发入口，但是截图已经发生，因此很多截图其实是无效截图，并没有实际作用，可定期对此类截图进行清理或者在检测到用户并没有触发所述第一触发入口时，直接删除最近一次的截图。
而还有一种实现手段，在收到进入控制中心界面的触发信号时并不进行截图，而是在本步骤S102中检测到对所述第一触发入口的激活信号时(即用户触发第一触发入口时)，此时需要通过调用任务管理器(task manager)，检索启动序列中数值最低的标志位(Flag)对应的任务，所述数值最低的标志位对应的任务就是进入控制中心界面之前最近开启的任务，关于本部分任务管理器和启动序列的内容可以参照后面步骤S202中的相关描述。这样在找到最近开启的任务后，在后台对该任务的操作界面进行截图，这幅截图就是步骤S100中的所述操作界面的截图，这样这幅截图就可以自动在所述故障反馈界面载入。需要说明的是，在步骤S100中截图以及在步骤S102中截图可以择一的选用，都可以实现本申请。
所述终端账户，一般是指处于登陆状态的终端账户，这样在触发所述第一触发入口后，终端完全有能力自动识别到当前处于登陆中的终端账户，当然，如果当前终端并未登陆终端账户，但是曾经登陆过并记录了终端账户在本地或云端，终端也有能力自动识别到终端账户。这个账户可以是邮件地址、手机号码、终端ID等等。
这样终端自动把截图加载在故障反馈界面中相应位置，自动把识别到的终端账户和截图一起发送到后台服务中心，截图便于后台服务中心的运维人员形象地了解到当前故障情况，终端账户则方便运维人员及时和用户取得联系以沟通解决故障。
步骤S104，检测到提交确认信号，将所述故障反馈界面中所载入的数据发送到后台服务中心，并对用户进行提交确认提示，返回所述操作界面。
用户在故障反馈界面点击相应按钮后，对步骤S102中的截图、终端账户进行提交，提交后直接由故障反馈界面退出到步骤S100中发出进入控制中心界面的触发信号之前开启的操作界面。
如图2所示，为本申请一个实施例所述的故障反馈方法，包括：
步骤S200，在终端的一操作界面上，收到进入控制中心界面的触发信号，显示控制中心界面，所述控制中心界面上显示有第一触发入口；
参照步骤S100的描述，不再赘述。
步骤S202，检测到对所述第一触发入口的激活信号，显示相应的故障反馈界面，调取所述操作界面对应的应用的名称，并将所述应用的名称显示在所述故障反馈界面中，自动在所述故障反馈界面载入所保存的截图以及所识别到的终端账户；
调用任务管理器(task manager)，检索启动序列中数值最低的标志位(Flag)对应的任务，所述数值最低的标志位对应的任务就是进入控制中心界面之前最近开启的任务(也就是所述操作界面对应的任务)，并根据最近开启的任务从任务与应用名称的映射表中选中最近开启的任务相应的应用名称。
任务管理器(task manager)为一种API函数，对于系统中启动的任务进行管理，并维护一启动序列。例如，当前启动一应用A，同时将应用A在启动序列中的标志位设置为0；之后又启动另一应用B，同时将应用B在启动序列中的标志位设置为0，而应用A的标志位设置为1；之后又启动另一应用C，同时将应用C在启动序列中的标志位设置为0，而应用B的标志位设置为1，应用A的标志位设置为2…以此类推，显然，标志位越大，说明开启越早，标志位越小，说明开启时间越近，而标志位为0时，说明是最近刚刚开始的任务。
而任务与应用名称的映射表是预先配置好并保存在本地，可由任务管理器(task manager)调用的。映射表如下所示，当然本领域技术人员应当知晓， 对于映射表的具体形态，本申请并不限于此。
任务A 微信
任务B QQ
任务C 浏览器
任务D 电子邮件
这样终端自动把截图加载在故障反馈界面中相应位置，自动把识别到的终端账户和截图一起发送到后台服务中心，还把应用的名称也显示在故障反馈界面中，一方面是方便用户确认汇报过程中所针对的出现故障的应用没有错乱，另一方面通过应用的名字和截图一起更加有利于后台服务中心的运维人员准确地了解到当前故障情况。
关于本步骤的其他部分，参照步骤S102的描述，不再赘述。
步骤S204，检测到提交确认信号，将应用的名称、载入的截图及终端账户发送到后台服务中心，并对用户进行提交确认提示，返回所述操作界面。
参照步骤S104的描述，不再赘述。
如图3所示，为本申请一个实施例所述的故障反馈方法，包括：
步骤S300，在终端的一操作界面上，收到进入控制中心界面的触发信号，显示控制中心界面，所述控制中心界面上显示有第一触发入口；
参照步骤S100的描述，不再赘述。
步骤S302，检测到对所述第一触发入口的激活信号，显示相应的故障反馈界面，自动在所述故障反馈界面载入所述操作界面的截图以及所识别到的终端账户；
参照步骤S102的描述，不再赘述。
步骤S304，在所述故障反馈界面提供一描述窗口，识别并载入用户在所述描述窗口内输入的关于故障的描述信息；
因为单纯提供应用的名称和截图，并不能完全将故障描述清楚，或者说很多故障是动态的过程，并不是一副截图可以描述清晰的。对于动态过程的 故障，比如在开启应用后，进行了添加操作或者删除操作，等待任意时间后，系统将应用强制关闭。对于这类故障，通过一副截图显然是无法描述清晰的，必须配以情况说明，这个说明一般是用户完成，所以需要提供一个支持用户输入的入口。
本申请的方案使用描述窗口来实现，用户可以在描述窗口中输入文字对故障的情况进行说明，也可以在描述窗口中输入关于故障本身的由用户叙述的语音或者视频对故障的情况进行说明，当然，还可以在描述窗口中输入对故障本身进行的录音或录屏视频对故障的情况进行说明，终端会识别所述描述窗口内的关于故障的描述信息。显然，这里的在所述描述窗口内输入不仅是指文字输入，还可以是语音或视频输入、录音或录屏视频输入。而输入的关于故障的描述信息可以是文字描述信息和/或音视频描述信息。
步骤S306，检测到提交确认信号，将在所述描述窗口内输入的关于故障的描述信息，随载入的截图及终端账户一起发送到后台服务中心，并对用户进行提交确认提示，返回所述操作界面。
把识别到的终端账户和截图，以及关于故障的描述信息也一起发送到后台服务中心，可以供后台服务中心的运维人员完全清晰地了解到当前故障情况，几乎没有认知死角。关于本步骤中其他部分参照步骤S104的描述，不再赘述。
需要说明的是，本实施例中对于关于故障的描述信息的方式，与上一实施例中应用的名称的方式，也可以叠加使用。
如图4所示，为本申请一个实施例所述的故障反馈方法，包括：
步骤S400，在终端的一操作界面上，收到进入控制中心界面的触发信号，显示控制中心界面，所述控制中心界面上显示有第一触发入口；
参照步骤S100的描述，不再赘述。
步骤S402，检测到对所述第一触发入口的激活信号，显示相应的故障反馈界面，自动在所述故障反馈界面载入所述操作界面的截图以及所识别到的终端账户，分别执行步骤S404和/或步骤S406；
参照步骤S102的描述，不再赘述。
步骤S404，在所述故障反馈界面中提供自动上传入口，检测到对所述自动上传入口的激活信号，显示手动选取界面，并在手动选取界面内显示供选择加载的截图，执行步骤S408；
故障反馈界面中放置截图的位置有多个，也就是说可以加载多幅截图，步骤402中自动在所述故障反馈界面载入所保存的截图一般是放置在第一个位置，自动上传入口设置在剩余的位置上，用户通过触发自动上传入口就可以进入手动选取界面，手动选取界面中会罗列出可以选择加载的截图，载入被用户选中的图片在剩余的位置上。
步骤S406，在所述故障反馈界面中提供故障属性选择入口，检测到对所述故障属性选择入口的激活信号，显示手动选取界面，并在手动选取界面内显示供选择的相应故障属性选项，载入被选中的故障属性选项，执行步骤S408；
所述故障属性选择入口，包括：故障类型选择入口和/或出现频率选择入口。
对于故障属性选择入口，激活后显示手动选取界面，一般这个界面是一个下拉菜单，也可能是一个新开启的页面罗列了所有可点选的选项。例如，对于故障类型选择入口，可以选择的故障属性选项可以是：默认、反应迟缓、操作无响应、系统强行退出、数据丢失、功能缺陷、改进建议、设计不足、其他情况等等，对于出现频率选择入口，可以选择的故障属性选项可以是：出现一次、有时、每次必现等等。
步骤S408，检测到提交确认信号，将选中的故障属性选项、载入的截图及终端账户发送到后台服务中心，并对用户进行提交确认提示，返回所述操作界面。
显然，故障属性选项是一种辅助性的数据，但是可以很好地帮助后台服务中心的运维人员分析故障问题，或者帮助后台服务中心的运维人员对故障进行分类并分派到适合的技术人员进行处理。而截图除了自动载入的之外，用户手动选择的截图可以更全面的提供对故障进行描述、定义，因为用户认知故障的视角相对于终端的机器视角更为灵活。本步骤中其他部分参照步骤S104的描述，不再赘述。
需要说明的是，本实施例中对于关于故障属性选项和/或手动选取截图的方式，可以分别与前述实施例中故障的描述信息的方式、应用的名称的方式叠加使用，也可以与前述实施例中故障的描述信息的方式、应用的名称的方式组合在一起叠加使用，形成一个完整方案。
如图5所示，为本申请一个实施例所述的故障反馈装置，包括：
控制中心界面管理模块500，用于在终端的一操作界面上，收到进入控制中心界面的触发信号，显示控制中心界面，所述控制中心界面上显示有第一触发入口；
第一触发入口管理模块502，用于检测到对所述第一触发入口的激活信号，显示相应的故障反馈界面，自动在所述故障反馈界面载入所述操作界面的截图以及所识别到的终端账户；
提交确认管理模块504，用于检测到提交确认信号，将所述故障反馈界面中所载入的数据发送到后台服务中心，并对用户进行提交确认提示，返回所述操作界面。
所述操作界面的截图为控制中心界面管理模块500在收到进入控制中心界面的触发信号时截取的或者第一触发入口管理模块502在检测到对所述第一触发入口的激活信号时截取的。
上述终端账户，包括：处于登陆状态的终端账户，或曾登陆过并记录的终端账户。
第一触发入口管理模块502，收到检测到对所述第一触发入口的激活信号时，还用于调取所述操作界面对应的应用的名称，并将所述应用的名称显示在所述故障反馈界面中；
第一触发入口管理模块502，调取所述操作界面对应的应用的名称时，进一步用于调用任务管理器，检索启动序列中数值最低的标志位对应的任务，所述数值最低的标志位对应的任务是所述操作界面对应的任务，并根据所述操作界面对应的任务从任务与应用名称的映射表中选中所述操作界面对应的任务相应的应用名称。
第一触发入口管理模块502自动在所述故障反馈界面载入所保存的截图 时，具体用于检测在距当前时间的一时段内是否保存有截图，如果有，自动选取截取时间距当前时间最近的一张截图进行加载。
检测到对所述第一触发入口的激活信号时，第一触发入口管理模块502除了完成上述操作以外，第一触发入口管理模块502，还在所述故障反馈界面提供一描述窗口，识别并载入用户在所述描述窗口内输入的关于故障的描述信息，其中，在所述描述窗口内输入的关于故障的描述信息，包括：文字描述信息，和/或音视频描述信息；和/或，
第一触发入口管理模块502，还在所述故障反馈界面中提供自动上传入口，检测到对所述自动上传入口的激活信号，显示手动选取界面，并在手动选取界面内显示供选择加载的截图，载入被选中的截图；和/或，
第一触发入口管理模块502，还在所述故障反馈界面中提供故障属性选择入口，检测到对所述故障属性选择入口的激活信号，显示手动选取界面，并在手动选取界面内显示供选择的相应故障属性选项，载入被选中的故障属性选项，其中所述故障属性选择入口，包括：故障类型选择入口和/或出现频率选择入口。
图5中所视出的故障反馈装置，与图1-4中所示的方法实施例的特征和方案相互对应，上述对于故障反馈装置中描述的不足之处，请参考图1-4中所示的方法实施例的描述。
以下再通过一个应用实例对本申请进行说明。终端以手机为例进行说明，但是本申请的终端并不限于此。
用户在最近使用手机的浏览器时，发现浏览器会被系统强行退出，且在近一段时间这种情况已经变成了常态，但是又无法找出原因。希望借助故障反馈机制，将故障汇报给手机的后台服务器，从而寻求解决办法。
因为准备汇报浏览器的故障，用户点击手机的系统界面上浏览器图标，先开启浏览器界面，参见图6。当然，浏览器并不一定是初始开启状态，置于打开网页等使用状态下来汇报故障也是可以的。
在如图6的浏览器界面的开启状态下，用户点击手机键盘上的多任务按键，自动对开启的浏览器界面进行截图并保存，同时呼出控制中心界面，如 图7所示，从图7中的控制中心界面上可以看到，光标指向的问号图标就是第一触发入口。
同时可以看到控制中心界面中还有很多别的功能图标，所以对于手机来说，不能确认每次用户进入控制中心界面就是为了故障汇报，但是截图操作在每次进入用户控制中心界面时都会执行。比如此次用户进入控制中心界面后并没有第一时间出发问号图标，而是触发无线连接图标开启了无线网连接，并触发屏幕旋转图标开启了手机屏幕的智能旋转功能，之后才触发了问号图标，注意触发无线连接图标和触发屏幕旋转图标所消耗的时间大致为不到2分钟，所以触发问号图标距执行截图的时间大概为2分钟左右。
此时要进行以下操作：
1)手机检测在最近5分钟内是否保存有截图，显然，至少会找到浏览器界面的截图，当然也可能会找到其他截图，当然距离当前时刻最近的最新截图肯定是浏览器界面的截图，所以自动选取最新截图——浏览器界面的截图进行加载，如图8所示。当然，图8中还示出，在加载截图的后面还提供自动上传入口，即加号图标，用户点击加号图标，手机显示手动选取界面，并在手动选取界面内显示供选择加载的截图，用户点选中还希望加载的截图，手机载入被选中的截图。
2)手机需要调用任务管理器(task manager)，检索启动序列中标志位flag数值为0的任务，发现是任务com.android.browser，并根据com.android.browser从任务与应用名称的映射表查找，发现com.android.browser相应的app名称是“浏览器”，将所述应用的名称“浏览器”显示在所述故障反馈界面中相应位置，如图8所示。在做完以上两个操作后，还会在所述故障反馈界面提供一描述窗口，用户在描述窗口内通过调用输入法输入“使用5秒后，系统强制退出”，手机识别并载入用户在所述描述窗口内输入的关于故障的描述信息，如图8所示。
另外，在所述故障反馈界面中，用户触发故障类型按钮，会显示手动选取界面，可以用下拉菜单实现，下拉菜单中提供选项，如“默认、反应迟缓、操作无响应、系统强行退出、数据丢失、功能缺陷、改进建议、设计不足、其他情况”，用户选择的相应故障属性选项“系统强行退出”，下拉菜单收起，并显示“系统强行退出”，如图8所示。
在所述故障反馈界面中，用户触发出现频率按钮，会显示手动选取界面，可以用下拉菜单实现，下拉菜单中提供选项，如“出现一次、有时、每次必现”，用户选择的相应故障属性选项“每次必现”，下拉菜单收起，并显示“每次必现”，如图8所示。
用户确认了应用名称、描述信息、加载的截图、故障类型、出现频率，点击提交确认，手机将所述故障反馈界面中所载入的这些数据发送到后台服务中心，并在手机的界面上显示提示框，提示用户已经提交后台，如图9所示，返回所述操作界面。后台服务中心可以用机器自动根据故障反馈界面的数据对故障进行处理，如果处理不了，可以根据故障反馈界面的数据对故障进行有效分类，并相应派送给相应技术领域的运维人员进行处理。
以下再通过另一个应用实例对本申请进行说明。终端以手机为例进行说明，但是本申请的终端并不限于此。
与上一个应用实例的不同在于，在如图6的浏览器界面的开启状态下，用户点击手机键盘上的多任务按键，并没有对浏览器界面进行截图并保存，同只是出控制中心界面，如图7所示。
控制中心界面中还有很多别的功能图标，对于手机来说，不能确认每次用户进入控制中心界面就是为了故障汇报，为了避免截图过多影响手机资20源，只有在用户触发了问号图标的同时，才进行截图，并开启故障反馈界面。之后的操作相同，手机检测在最近5分钟内是否保存有截图，对浏览器截图进行加载，并手机需要调用任务管理器(task manager)，获取所述应用的名称“浏览器”，和描述信息、故障类型、出现频率一起显示在所述故障反馈界面中相应位置，如图8所示，对于这些部分可以参考上一应用实例。
用户确认了应用名称、描述信息、加载的截图、故障类型、出现频率，点击提交确认，手机将所述故障反馈界面中所载入的这些数据发送到后台服务中心，并在手机的界面上显示提示框，提示用户已经提交后台，如图9所示，返回所述操作界面。后台服务中心可以用机器自动根据故障反馈界面的数据对故障进行处理，如果处理不了，可以根据故障反馈界面的数据对故障进行有效分类，并相应派送给相应技术领域的运维人员进行处理。
本申请的各个部件实施例可以以硬件实现，或者以在一个或者多个处理器上运行的软件模块实现，或者以它们的组合实现。本领域的技术人员应当理解，可以在实践中使用微处理器或者数字信号处理器(DSP)来实现根据本申请实施例中的一些或者全部部件的一些或者全部功能。
本申请还提供了一种故障反馈装置，包括：内存、处理器，其中，所述内存，用于存储一条或多条指令，其中，所述一条或多条指令以供所述处理器调用执行；
所述处理器被配置为：在终端的一操作界面上，收到进入控制中心界面的触发信号，显示控制中心界面，所述控制中心界面上显示有第一触发入口；检测到对所述第一触发入口的激活信号，显示相应的故障反馈界面，自动在所述故障反馈界面载入所述操作界面的截图以及所识别到的终端账户；检测到提交确认信号，将所述故障反馈界面中所载入的数据发送到后台服务中心，并对用户进行提交确认提示，返回所述操作界面。
进一步地，所述处理器进一步被配置为：收到检测到对所述第一触发入口的激活信号时，调取所述操作界面对应的应用的名称，并将所述应用的名称显示在所述故障反馈界面中。
进一步地，所述处理器进一步被配置为：调取所述操作界面对应的应用的名称时，调用任务管理器，检索启动序列中数值最低的标志位对应的任务，所述数值最低的标志位对应的任务是所述操作界面对应的任务，并根据所述操作界面对应的任务从任务与应用名称的映射表中选中所述操作界面对应的任务相应的应用名称。
进一步地，所述处理器进一步被配置为：自动在所述故障反馈界面载入所保存的截图时，检测在距当前时间的一时段内是否保存有截图，如果有，自动选取截取时间距当前时间最近的一张截图进行加载。
进一步地，所述处理器进一步被配置为：检测到对所述第一触发入口的激活信号时，还在所述故障反馈界面提供一描述窗口，识别并载入用户在所述描述窗口内输入的关于故障的描述信息，其中，在所述描述窗口内输入的关于故障的描述信息，包括：文字描述信息，和/或音视频描述信息。
进一步地，所述处理器进一步被配置为：在所述故障反馈界面中提供自动上传入口，检测到对所述自动上传入口的激活信号，显示手动选取界面，并在手动选取界面内显示供选择加载的截图，载入被选中的截图。
进一步地，所述处理器进一步被配置为：在所述故障反馈界面中提供故障属性选择入口，检测到对所述故障属性选择入口的激活信号，显示手动选取界面，并在手动选取界面内显示供选择的相应故障属性选项，载入被选中的故障属性选项。
进一步地，所述处理器进一步被配置为：所述故障属性选择入口，包括：故障类型选择入口和/或出现频率选择入口。
进一步地，所述处理器进一步被配置为：所述终端账户，包括：处于登陆状态的终端账户，或曾登陆过并记录的终端账户。
进一步地，所述处理器进一步被配置为：所述操作界面的截图为在收到进入控制中心界面的触发信号时截取的或者第一触发入口管理模块在检测到对所述第一触发入口的激活信号时截取的。
本申请还可以实现为用于执行这里所描述的方法的一部分或者全部的设备或者装置程序(例如，计算机程序和计算机程序产品)。这样的实现本申请的程序可以存储在计算机可读介质上，或者可以具有一个或者多个信号的形式。这样的信号可以从因特网网站上下载得到，或者在载体信号上提供，或者以任何其他形式提供。
本文中所称的“一个实施例”、“实施例”或者“一个或者多个实施例”意味着，结合实施例描述的特定特征、结构或者特性包括在本申请的至少一个实施例中。此外，请注意，这里“在一个实施例中”的词语例子不一定全指同一个实施例。
在此处所提供的说明书中，说明了大量具体细节。然而，能够理解，本申请的实施例可以在没有这些具体细节的情况下被实践。在一些实例中，并未详细示出公知的方法、结构和技术，以便不模糊对本说明书的理解。应该注意的是上述实施例对本申请进行说明而不是对本申请进行限制，并且本领域技术人员在不脱离所附权利要求的范围的情况下可设计出替换实施例。在 权利要求中，不应将位于括号之间的任何参考符号构造成对权利要求的限制。单词“包含”不排除存在未列在权利要求中的元件或步骤。位于元件之前的单词“一”或“一个”不排除存在多个这样的元件。本申请可以借助于包括有若干不同元件的硬件以及借助于适当编程的计算机来实现。
在列举了若干装置的单元权利要求中，这些装置中的若干个可以是通过同一个硬件项来具体体现。单词第一、第二、以及第三等的使用不表示任何顺序。可将这些单词解释为名称。
此外，还应当注意，本说明书中使用的语言主要是为了可读性和教导的目的而选择的，而不是为了解释或者限定本申请的主题而选择的。因此，在不偏离所附权利要求书的范围和精神的情况下，对于本技术领域的普通技术人员来说许多修改和变更都是显而易见的。对于本申请的范围，对本申请所做的公开是说明性的，而非限制性的，本申请的范围由所附权利要求书限定。
本领域普通技术人员可以理解：实现上述方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成，前述的程序可以存储于一计算机可读取存储介质中，该程序在执行时，执行包括上述方法实施例的步骤；而前述的存储介质包括：ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是：以上各实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述各实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (19)

  1. 一种故障反馈方法，其特征在于，包括：
    在终端的一操作界面上，收到进入控制中心界面的触发信号，显示控制中心界面，所述控制中心界面上显示有第一触发入口；
    检测到对所述第一触发入口的激活信号，显示相应的故障反馈界面，自动在所述故障反馈界面载入所述操作界面的截图以及所识别到的终端账户；
    检测到提交确认信号，将所述故障反馈界面中所载入的数据发送到后台服务中心，并对用户进行提交确认提示，返回所述操作界面。
  2. 如权利要求1所述的故障反馈方法，其特征在于，
    所述操作界面的截图为收到进入控制中心界面的触发信号时截取的或者检测到对所述第一触发入口的激活信号时截取的。
  3. 如权利要求1所述的故障反馈方法，其特征在于，检测到对所述第一触发入口的激活信号，显示相应的故障反馈界面，自动在所述故障反馈界面载入所述操作界面的截图以及所识别到的终端账户，还包括：
    调取所述操作界面对应的应用的名称，并将所述应用的名称显示在所述故障反馈界面中。
  4. 如权利要求3所述的故障反馈方法，其特征在于，调取所述操作界面对应的应用的名称，进一步包括：
    调用任务管理器，检索启动序列中数值最低的标志位对应的任务，所述数值最低的标志位对应的任务是所述操作界面对应的任务，并根据所述操作界面对应的任务从任务与应用名称的映射表中选中所述操作界面对应的任务相应的应用名称。
  5. 如权利要求1所述的故障反馈方法，其特征在于，自动在所述故障反馈界面载入所述操作界面的截图，进一步包括：
    检测在距当前时间的一时段内是否保存有截图，如果有，自动选取截取时间距当前时间最近的一张截图进行加载。
  6. 如权利要求1所述的故障反馈方法，其特征在于，检测到对所述第一触发入口的激活信号，显示相应的故障反馈界面，自动在所述故障反馈界 面载入所述操作界面的截图以及所识别到的终端账户，还包括：
    在所述故障反馈界面提供一描述窗口，识别并载入用户在所述描述窗口内输入的关于故障的描述信息。
  7. 如权利要求6所述的故障反馈方法，其特征在于，在所述描述窗口内输入的关于故障的描述信息，包括：文字描述信息，和/或音视频描述信息。
  8. 如权利要求1所述的故障反馈方法，其特征在于，自动在所述故障反馈界面载入所述操作界面的截图以及所识别到的终端账户之后，检测到提交确认信号之前，还包括：
    在所述故障反馈界面中提供自动上传入口，检测到对所述自动上传入口的激活信号，显示手动选取界面，并在手动选取界面内显示供选择加载的截图，载入被选中的截图。
  9. 如权利要求1所述的故障反馈方法，其特征在于，自动在所述故障反馈界面载入所述操作界面的截图以及所识别到的终端账户之后，检测到提交确认信号之前，还包括：
    在所述故障反馈界面中提供故障属性选择入口，检测到对所述故障属性选择入口的激活信号，显示手动选取界面，并在手动选取界面内显示供选择的相应故障属性选项，载入被选中的故障属性选项。
  10. 如权利要求9所述的故障反馈方法，其特征在于，所述故障属性选择入口，包括：故障类型选择入口和/或出现频率选择入口。
  11. 如权利要求1所述的故障反馈方法，其特征在于，所述终端账户，包括：处于登陆状态的终端账户，或曾登陆过并记录的终端账户。
  12. 一种故障反馈装置，其特征在于，包括：
    控制中心界面管理模块，用于在终端的一操作界面上，收到进入控制中心界面的触发信号，显示控制中心界面，所述控制中心界面上显示有第一触发入口；
    第一触发入口管理模块，用于检测到对所述第一触发入口的激活信号，显示相应的故障反馈界面，自动在所述故障反馈界面载入所述操作界面的截图以及所识别到的终端账户；
    提交确认管理模块，用于检测到提交确认信号，将所述故障反馈界面中所载入的数据发送到后台服务中心，并对用户进行提交确认提示，返回所述操作界面。
  13. 如权利要求12所述的故障反馈装置，其特征在于，
    所述第一触发入口管理模块，收到检测到对所述第一触发入口的激活信号时，还用于调取所述操作界面对应的应用的名称，并将所述应用的名称显示在所述故障反馈界面中。
  14. 如权利要求13所述的故障反馈装置，其特征在于，
    所述第一触发入口管理模块，调取所述操作界面对应的应用的名称时，用于调用任务管理器，检索启动序列中数值最低的标志位对应的任务，所述数值最低的标志位对应的任务是所述操作界面对应的任务，并根据所述操作界面对应的任务从任务与应用名称的映射表中选中所述操作界面对应的任务相应的应用名称。
  15. 如权利要求12所述的故障反馈装置，其特征在于，
    所述第一触发入口管理模块自动在所述故障反馈界面载入所保存的截图时，具体用于检测在距当前时间的一时段内是否保存有截图，如果有，自动选取截取时间距当前时间最近的一张截图进行加载。
  16. 如权利要求12所述的故障反馈装置，其特征在于，
    所述第一触发入口管理模块，检测到对所述第一触发入口的激活信号时，还在所述故障反馈界面提供一描述窗口，识别并载入用户在所述描述窗口内输入的关于故障的描述信息，其中，在所述描述窗口内输入的关于故障的描述信息，包括：文字描述信息，和/或音视频描述信息。
  17. 如权利要求12所述的故障反馈装置，其特征在于，
    所述第一触发入口管理模块，还在所述故障反馈界面中提供自动上传入口，检测到对所述自动上传入口的激活信号，显示手动选取界面，并在手动选取界面内显示供选择加载的截图，载入被选中的截图。
  18. 如权利要求12所述的故障反馈装置，其特征在于，
    所述第一触发入口管理模块，还在所述故障反馈界面中提供故障属性选 择入口，检测到对所述故障属性选择入口的激活信号，显示手动选取界面，并在手动选取界面内显示供选择的相应故障属性选项，载入被选中的故障属性选项。
  19. 一种故障反馈装置，其特征在于，包括：
    内存、处理器，其中，所述内存，用于存储一条或多条指令，其中，所述一条或多条指令以供所述处理器调用执行；
    所述处理器被配置为：在终端的一操作界面上，收到进入控制中心界面的触发信号，显示控制中心界面，所述控制中心界面上显示有第一触发入口；检测到对所述第一触发入口的激活信号，显示相应的故障反馈界面，自动在所述故障反馈界面载入所述操作界面的截图以及所识别到的终端账户；检测到提交确认信号，将所述故障反馈界面中所载入的数据发送到后台服务中心，并对用户进行提交确认提示，返回所述操作界面。
PCT/CN2016/074127 2015-03-27 2016-02-19 故障反馈方法及故障反馈装置 Ceased WO2016155430A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510140169.1 2015-03-27
CN201510140169.1A CN104866172A (zh) 2015-03-27 2015-03-27 故障反馈方法及故障反馈装置

Publications (1)

Publication Number Publication Date
WO2016155430A1 true WO2016155430A1 (zh) 2016-10-06

Family

ID=53912040

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/074127 Ceased WO2016155430A1 (zh) 2015-03-27 2016-02-19 故障反馈方法及故障反馈装置

Country Status (2)

Country Link
CN (1) CN104866172A (zh)
WO (1) WO2016155430A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111950743A (zh) * 2020-07-08 2020-11-17 北京思特奇信息技术股份有限公司 一种用于移动终端故障工单解决的方法及系统

Families Citing this family (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104866172A (zh) * 2015-03-27 2015-08-26 乐视致新电子科技（天津）有限公司 故障反馈方法及故障反馈装置
CN105868994A (zh) * 2015-11-13 2016-08-17 乐视移动智能信息技术（北京）有限公司 故障反馈方法及装置、移动设备
CN105653266A (zh) * 2015-12-24 2016-06-08 武汉明德生物科技股份有限公司 自助咨询系统、定量分析仪及自助咨询方法
CN105812698A (zh) * 2016-03-10 2016-07-27 深圳市元征科技股份有限公司 汽车诊断终端的屏幕录制方法及装置
CN106020594A (zh) * 2016-05-12 2016-10-12 珠海金山网络游戏科技有限公司 一种手机游戏快速提交反馈的方法和装置
CN106209471A (zh) * 2016-07-25 2016-12-07 北京小米移动软件有限公司 故障反馈方法及装置
CN106412574B (zh) * 2016-11-30 2018-11-20 北京数码视讯软件技术发展有限公司 机顶盒运行过程中的缺陷记录方法及装置
CN109388313B (zh) * 2017-08-08 2021-12-07 北京国双科技有限公司 一种反馈邮件的发送方法及装置
CN107368053B (zh) * 2017-08-23 2021-01-12 上海云统信息科技有限公司 一种基于集散控制系统的生产线停机反馈系统
CN107612735A (zh) * 2017-09-21 2018-01-19 北京天元创新科技有限公司 一种宽带故障在线处理方法、服务器及用户终端
CN109558185B (zh) * 2017-09-26 2022-07-08 北京嘀嘀无限科技发展有限公司 数据处理方法、装置、移动终端和计算机可读存储介质
CN107835296A (zh) * 2017-10-12 2018-03-23 无线生活（杭州）信息科技有限公司 一种问题反馈方法及装置
CN109255060B (zh) * 2018-09-26 2021-05-18 Oppo广东移动通信有限公司 反馈处理方法、电子装置及计算机可读存储介质
CN109597799A (zh) * 2018-11-05 2019-04-09 北京百度网讯科技有限公司 问题定位方法及装置、计算机设备、存储介质
CN109542294A (zh) * 2018-11-23 2019-03-29 泰康保险集团股份有限公司 意见反馈方法、装置与存储介质
CN109815050A (zh) * 2018-12-14 2019-05-28 深圳壹账通智能科技有限公司 一种应用故障信息的修复方法、系统及设备
CN109684177A (zh) * 2018-12-26 2019-04-26 浙江口碑网络技术有限公司 信息反馈方法及装置
CN109976854B (zh) * 2019-03-22 2023-02-24 维沃移动通信有限公司 一种应用程序处理方法及终端设备
CN112181236B (zh) * 2019-07-04 2022-04-29 广州汽车集团股份有限公司 一种电子车辆手册及其操作方法、车辆信息提供装置
CN111611044B (zh) * 2020-05-26 2022-10-25 北京字节跳动网络技术有限公司 上传任务的反馈处理方法及相关设备
CN114371963B (zh) * 2020-10-14 2024-10-11 华为技术有限公司 一种故障检测方法及电子终端
CN114138398B (zh) * 2022-02-07 2022-05-31 浙江口碑网络技术有限公司 信息反馈方法及装置
CN114900632A (zh) * 2022-05-11 2022-08-12 深圳创维－Rgb电子有限公司 测试问题提交方法、系统、设备及计算机可读存储介质
CN116301523A (zh) * 2022-12-22 2023-06-23 中国联合网络通信集团有限公司 一种工单创建方法、装置及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103618962A (zh) * 2013-12-09 2014-03-05 乐视网信息技术（北京）股份有限公司 进入智能电视的特定视频应用的控制方法和控制装置
CN103618918A (zh) * 2013-11-27 2014-03-05 青岛海信电器股份有限公司 一种智能电视的显示控制方法及装置
CN103699396A (zh) * 2014-01-21 2014-04-02 北京搜狐新媒体信息技术有限公司 一种信息反馈方法及终端设备
CN103747312A (zh) * 2013-12-23 2014-04-23 乐视致新电子科技（天津）有限公司 一种鼠标控制智能电视的方法及智能电视
CN104866172A (zh) * 2015-03-27 2015-08-26 乐视致新电子科技（天津）有限公司 故障反馈方法及故障反馈装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101164999B1 (ko) * 2010-12-07 2012-07-13 주식회사에이메일 모바일 애플리케이션 분석과 대응하는 서비스정보 제공 시스템 및 그 방법
CN103268183A (zh) * 2013-05-10 2013-08-28 华为软件技术有限公司 信息上报处理方法和装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103618918A (zh) * 2013-11-27 2014-03-05 青岛海信电器股份有限公司 一种智能电视的显示控制方法及装置
CN103618962A (zh) * 2013-12-09 2014-03-05 乐视网信息技术（北京）股份有限公司 进入智能电视的特定视频应用的控制方法和控制装置
CN103747312A (zh) * 2013-12-23 2014-04-23 乐视致新电子科技（天津）有限公司 一种鼠标控制智能电视的方法及智能电视
CN103699396A (zh) * 2014-01-21 2014-04-02 北京搜狐新媒体信息技术有限公司 一种信息反馈方法及终端设备
CN104866172A (zh) * 2015-03-27 2015-08-26 乐视致新电子科技（天津）有限公司 故障反馈方法及故障反馈装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111950743A (zh) * 2020-07-08 2020-11-17 北京思特奇信息技术股份有限公司 一种用于移动终端故障工单解决的方法及系统

Also Published As

Publication number Publication date
CN104866172A (zh) 2015-08-26

Similar Documents

Publication Publication Date Title
CN104866172A (zh) 故障反馈方法及故障反馈装置
US10762277B2 (en) Optimization schemes for controlling user interfaces through gesture or touch
CN101371255B (zh) 在电子表格生成过程期间标识潜在设计问题的方法和系统
US20090044146A1 (en) Associating file types with web-based applications for automatically launching the associated application
US20210124675A1 (en) Methods and systems for automated testing using browser extension
US20090132919A1 (en) Appending Hover Help to Hover Help for a User Interface
US10521333B2 (en) Automated system for fixing and debugging software deployed to customers
US20150331784A1 (en) System and method for controlling test script execution by smartphone
US20110022899A1 (en) Producing or executing a script for an operation test of a terminal server
CN109542289B (zh) Mes的操作方法、装置、设备及存储介质
US12226916B2 (en) Triggering dynamic robotic process automation
US10877778B2 (en) Sequence detection and automation for complex portal environments
CN107102937B (zh) 一种用户界面测试方法和装置
WO2021129335A1 (zh) 操作监控方法及装置、操作分析方法及装置
CN106815374A (zh) 一种页面跳转方法及装置
US8538414B1 (en) Mobile interaction with software test cases
TWI566165B (zh) 適應性呼叫應用程式的方法及其電子裝置
US20140081683A1 (en) Business process management for mobile portal clients
CN110750460A (zh) 浏览器兼容性的检测方法、装置、设备及可读存储介质
US20230333866A1 (en) Method and system for calling/executing an action from an outside application within an existing open application
WO2024022399A1 (zh) 基于rpa和ai的ia机器人监控方法及装置
JP2014215993A (ja) ソフトウェアをテストする装置およびプログラム
CN111611162A (zh) 一种测试方法、装置、电子设备和存储介质
CN112068763A (zh) 目标信息的管理方法、装置、电子设备以及存储介质
CN109684525B (zh) 文档显示方法、装置、存储介质及测试设备

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: 16771185

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: 16771185

Country of ref document: EP

Kind code of ref document: A1