CN114615559A

CN114615559A - Method, device and system for uploading real scene fault for terminal

Info

Publication number: CN114615559A
Application number: CN202210199738.XA
Authority: CN
Inventors: 梁建平
Original assignee: Seerof Information Technology Shanghai Co ltd
Current assignee: Seerof Information Technology Shanghai Co ltd
Priority date: 2022-03-02
Filing date: 2022-03-02
Publication date: 2022-06-10

Abstract

The invention relates to a method, a device and a system for uploading real scene faults of a terminal, wherein the method comprises the steps of acquiring a log recording starting instruction under the condition that the faults need to be uploaded; recording a fault reproduction process; acquiring a log recording stopping instruction to generate an initial file; adding problem description information to an initial file to generate a log file; attempting to upload a log file; judging whether log files are uploaded successfully or not; and deleting the log file under the condition that the log file is uploaded successfully. The method has the advantages that the terminal user directly reports the fault to the terminal manufacturer/browser manufacturer, uploading time is shortened, uploading steps are reduced, fault solution waiting time is reduced, information transmission errors are avoided, the fault solution period is shortened, fault feedback efficiency is improved, repeated confirmation is not needed, a quick response effect is achieved, and user experience is improved.

Description

Method, device and system for uploading real scene fault for terminal

Technical Field

The invention relates to the technical field of terminal fault processing, in particular to a method and a device for uploading real scene faults for a terminal, computer equipment and a computer readable storage medium.

Background

In the smart television browser, many end users may encounter many problems in actual use scenarios, for example, some apps cannot be normally used, television operation is abnormal, and the like; the general users can only use the app by default or only find the corresponding superior provider, and finally can feed the app back to the browser for a long time after layer-by-layer feedback.

At present, the reporting terminal user reports the bug, and the bug can reach a browser end which really solves the problem only through layer-by-layer reporting and multi-layer information and time transmission.

At present, no effective solution is provided for the problems of prolonged problem solving period, time and labor consumption and the like in the related art.

Disclosure of Invention

The present application aims to overcome the defects in the prior art, and provides a method, an apparatus, a system, a computer device and a computer-readable storage medium for uploading real scene failures for a terminal, so as to solve at least the problems of long solution period, time and labor consumption, and the like in the related art.

In order to achieve the purpose, the technical scheme adopted by the application is as follows:

in a first aspect, the present invention provides a method for uploading a real scene fault to a terminal, including:

acquiring a log recording starting instruction under the condition that a fault needs to be uploaded;

recording a fault reproduction process;

acquiring a log recording stopping instruction to generate an initial file;

adding problem description information to the initial file to generate a log file;

attempting to upload the log file;

judging whether the log file is uploaded successfully or not;

and deleting the log file when the log file is uploaded successfully.

In some of these embodiments, the recording failure recurrence process comprises:

and stopping the recording process under the condition of abnormality.

In some embodiments, after determining whether the log file is uploaded successfully, the method further includes:

under the condition that the log file uploading fails, uploading failure information is generated, wherein the uploading failure information is used for indicating the reason of uploading failure;

under the condition that the uploading failure information is generated, judging whether to continuously try to upload the log file;

attempting to upload the log file with continued attempts to upload the log file;

deleting the log file without continuing to attempt to upload the log file.

In some of these embodiments, determining whether the log file was uploaded successfully comprises:

obtaining the number of attempted uploading of the log file;

judging whether the number of times of attempted uploading is not more than a preset number of times;

judging whether uploading the log file is successful or not under the condition that the number of times of attempted uploading is less than or equal to the preset number of times;

and in the case that the number of attempted uploads is greater than the preset number, failing to upload the log file.

acquiring the number of attempted uploading of the log file under the condition that the log file uploading fails;

under the condition that the number of times of attempted uploading is not more than the preset number of times, acquiring the time of attempted uploading of the log file of the last attempt and the current time;

calculating a time difference between the current time and the attempted upload time;

judging whether the time difference is not less than a preset time threshold value or not;

and in the case that the time difference value is not smaller than the preset time threshold value, trying to upload the log file again.

In some embodiments, the time interval between two consecutive attempts to upload the log file is 0.5-2 min.

In some embodiments, the predetermined number of times is 3 to 8 times.

In some embodiments, before acquiring the log recording start instruction in the case of a fault needing to be uploaded, the method further includes:

judging whether the log system has log files or not;

in the case that the log system has the log file, deleting the log file and initializing the log system;

initializing the log system in the absence of the log file by the log system.

In some embodiments, after deleting the log file, further comprising:

acquiring a solution corresponding to the fault;

according to the solution, the fault is repaired.

In a second aspect, the present invention provides an apparatus for uploading real scene fault for a terminal, including:

the recording instruction acquisition unit is used for acquiring a log recording start instruction and a log recording stop instruction under the condition that the fault needs to be uploaded;

the recording unit is used for recording a fault recurrence process under the condition of acquiring the log recording starting instruction and stopping recording under the condition of acquiring the log stopping instruction;

an initial file generating unit, configured to generate an initial file when the recording of the fault recurrence process is completed;

a log file generating unit for adding problem description information to the initial file to generate a log file;

an uploading unit, configured to attempt to upload the log file;

the first judgment unit is used for judging whether the log file is uploaded successfully or not;

and the deleting unit is used for deleting the log file under the condition that the log file is uploaded successfully.

In some embodiments thereof, further comprising:

the number of attempts acquisition unit is used for acquiring the number of attempts of uploading the log file;

the second judgment unit is used for judging whether the number of times of the attempted uploading is not more than the preset number of times;

the first judging unit is further configured to judge that the log file is successfully uploaded if the number of attempted uploads is not greater than the preset number, and judge that the log file is unsuccessfully uploaded if the number of attempted uploads is greater than the preset number.

In some of these embodiments, further comprising:

the time acquisition unit is used for acquiring the uploading time of the last attempt of uploading the log file and the current time;

a time calculation unit for calculating a time difference between the current time and the attempted upload time;

the third judging unit is used for judging whether the time difference value is smaller than a preset time threshold value or not;

the uploading unit is further used for trying to upload the log file again under the condition that the time difference value is not smaller than the preset time threshold value.

In some of these embodiments, further comprising:

the feedback information generating unit is used for generating uploading failure information under the condition that the log file is unsuccessfully uploaded;

a fourth judging unit configured to judge whether to continue attempting to upload the log file in a case where the upload failure information is generated;

the uploading unit is further used for attempting to upload the log file under the condition that the log file is continuously attempted to be uploaded;

the deletion unit is further configured to delete the log file without continuing an attempt to upload the log file.

In some embodiments, the feedback information generating unit is further configured to generate upload success information if the log file is successfully uploaded.

In some of these embodiments, further comprising:

the fifth judging unit is used for judging whether the log system has log files or not;

an initialization unit for initializing the log system in case the log system does not have the log file;

the deleting unit is further configured to delete the log file if the log system has the log file.

In some of these embodiments, further comprising:

a solution acquiring unit configured to acquire a solution corresponding to the failure after deleting the log file;

a repair unit for repairing the fault according to the solution.

In a third aspect, the present invention provides a system for uploading real scene fault to a terminal, including:

the terminal is used for recording a fault recurrence process and generating a log file under the condition of a fault;

the server side is used for acquiring the log file transmitted by the terminal, generating a solution corresponding to the log file and transmitting the solution to the terminal;

the terminal is further configured to repair the fault according to the solution.

In some embodiments, the server is connected to a plurality of the terminals respectively.

In a fourth aspect, the present invention provides a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the method for uploading real scene failures as described above when executing the computer program.

In a fifth aspect, the present invention provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method of uploading real scene failures as described above.

Compared with the related art, the method, the device, the system, the equipment and the medium for uploading the real scene faults for the terminal provided by the embodiment of the application have the advantages that the terminal user directly reports the faults to the terminal manufacturer/browser manufacturer, the uploading time is shortened, the uploading steps are reduced, the fault resolution waiting time is reduced, the information transmission errors are avoided, the fault resolution period is shortened, the fault feedback efficiency is improved, repeated confirmation is not needed, the quick response effect is achieved, and the user experience is improved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 is a flowchart (one) of a method for uploading real scene faults according to an embodiment of the present application;

fig. 2 is a flowchart (ii) of a method for uploading real scene failures according to an embodiment of the present application;

fig. 3 is a flowchart (iii) of a method for uploading real scene failures according to an embodiment of the present application;

fig. 4 is a flowchart (iv) of a method for uploading real scene failures according to an embodiment of the present application;

fig. 5 is a flowchart (v) of a method for uploading real scene failures according to an embodiment of the present application;

fig. 6 is a flowchart (vi) of a method of uploading real scene failures according to an embodiment of the present application;

fig. 7 is a block diagram (one) of an upload real scene failure apparatus according to an embodiment of the present application;

fig. 8 is a frame diagram of an upload real scene fault apparatus according to an embodiment of the present application (ii);

fig. 9 is a block diagram (iii) of an upload real scene failure apparatus according to an embodiment of the present application;

fig. 10 is a block diagram (iv) of an upload real scenario failure apparatus according to an embodiment of the present application;

fig. 11 is a frame diagram (v) of an upload real scene failure apparatus according to an embodiment of the present application;

fig. 12 is a block diagram (vi) of an upload real scenario fault device according to an embodiment of the present application;

FIG. 13 is a block diagram of an upload real scenario fault system according to an embodiment of the present application;

FIG. 14 is a block diagram of an embodiment of a system for uploading real scene faults according to an embodiment of the present application;

fig. 15 is a flowchart illustrating a specific implementation of a method for uploading a real scene fault according to an embodiment of the present disclosure.

Wherein the reference numerals are: 700. uploading a real scene fault device; 701. a recording instruction acquisition unit; 702. a recording unit; 703. an initial file generation unit; 704. a log file generating unit; 705. an uploading unit; 706. a first judgment unit; 707. a deletion unit; 708. an attempt number acquisition unit; 709. a second judgment unit; 710. a time acquisition unit; 711. a time calculation unit; 712. a third judgment unit; 713. a feedback information generating unit; 714. a fourth judgment unit; 715. a fifth judging unit; 716. an initialization unit; 717. a solution acquisition unit; 718. a repair unit;

800. uploading a real scene fault system; 810. a terminal; 820. and (5) a server side.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more clearly understood, the present application is described and illustrated below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments provided in the present application without any inventive step are within the scope of protection of the present application.

It is obvious that the drawings in the following description are only examples or embodiments of the present application, and that it is also possible for a person skilled in the art to apply the present application to other similar contexts on the basis of these drawings without inventive effort. Moreover, it should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another.

Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the specification. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of ordinary skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments without conflict.

Unless defined otherwise, technical or scientific terms referred to herein shall have the ordinary meaning as understood by those of ordinary skill in the art to which this application belongs. Reference to "a," "an," "the," and similar words throughout this application are not to be construed as limiting in number, and may refer to the singular or the plural. The present application is directed to the use of the terms "including," "comprising," "having," and any variations thereof, which are intended to cover non-exclusive inclusions; for example, a process, method, system, article, or apparatus that comprises a list of steps or elements (elements) is not limited to the listed steps or elements, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Reference to "connected," "coupled," and the like in this application is not intended to be limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The term "plurality" as referred to herein means two or more. "and/or" describes an association relationship of associated objects, meaning that three relationships may exist, for example, "A and/or B" may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. Reference herein to the terms "first," "second," "third," and the like, are merely to distinguish similar objects and do not denote a particular ordering for the objects.

Example 1

Fig. 1 is a flowchart (one) of a method for uploading real scene failures according to an embodiment of the present invention. As shown in fig. 1, a method for uploading a real scene fault to a terminal includes:

step S102, under the condition that a fault needs to be uploaded, a log recording starting instruction is obtained;

step S104, recording a fault reproduction process;

step S106, obtaining a log recording stopping instruction to generate an initial file;

step S108, adding problem description information to an initial file to generate a log file;

step S110, attempting to upload log files;

step S112, judging whether log files are uploaded successfully or not;

and step S114, deleting the log file under the condition that the log file is uploaded successfully.

The terminal refers to a user terminal, such as a smart television, and includes a browser.

In some embodiments, steps S102 to S114 are performed in the terminal or a browser of the terminal.

In step S102, the fault includes, but is not limited to, that application software (app) installed in the terminal is not available, that software of the terminal itself is not available, that the terminal is not operable, and the like.

In step S102, the method for acquiring the log recording start instruction includes, but is not limited to, acquiring an instruction generated by touching the recording button, and acquiring an instruction generated by clicking the recording button.

In some embodiments, in step S104, the method further includes:

in the case where an abnormality occurs, the recording process is stopped, and then step S102 is repeated.

In step S106, the method for acquiring the log recording stop instruction includes, but is not limited to, acquiring an instruction generated by touching the stop button, and acquiring an instruction generated by clicking the stop button.

In step S106, the initial file is a file without a text description.

In step S108, adding the question description information includes setting a file name, adding a question description, and the like.

In step S110, before attempting to upload the log file, an upload instruction is further obtained.

The obtaining of the upload instruction includes, but is not limited to, obtaining an instruction generated by touching an upload button, and obtaining an instruction generated by clicking the upload button.

Further, step S114 is:

and under the condition that the log file is successfully uploaded, generating uploading success information and deleting the log file.

Further, after step S114, the method further includes:

step S116, acquiring an action instruction;

and step S118, executing the action corresponding to the action command.

Further, the method also comprises the following steps:

step S116, under the condition that the fault does not need to be uploaded, an action instruction is obtained;

step S118, the action corresponding to the action command is executed.

Step S116 is parallel to step S102.

Specifically, the steps S116 to S118 are steps for the end user to continue using the terminal.

Through the steps, the terminal user directly reports the fault to the terminal manufacturer/browser manufacturer, uploading time is shortened, uploading steps are reduced, fault solution waiting time is reduced, information transmission errors are avoided, the fault solution period is shortened, fault feedback efficiency is improved, repeated confirmation is not needed, the quick response effect is achieved, and user experience is improved.

Fig. 2 is a flowchart (ii) of a method for uploading real scene failures according to an embodiment of the present invention. As shown in fig. 2, after determining whether the log file is uploaded successfully, the method further includes:

step S202, under the condition that log file uploading fails, uploading failure information is generated, wherein the uploading failure information is used for indicating the reason of uploading failure;

step S204, under the condition of generating uploading failure information, judging whether to continuously try to upload the log file;

step S206, under the condition of continuously trying to upload the log file, trying to upload the log file;

and step S208, deleting the log file under the condition that the log file is not continuously tried to be uploaded.

In step S202, the upload failure information is used to indicate whether the transmitting end (terminal) has an error (i.e., cannot transmit the log file) or the receiving end (terminal manufacturer/browser manufacturer) has an error (i.e., cannot receive the log file).

In some embodiments, the upload failure information is an error code, where the error code corresponds to the failure cause, that is, the error code with an error at the transmitting end is different from the error code with an error at the receiving end.

After step S206, step S110 is performed.

After step S208, step S116 is performed.

In some embodiments, the user of the terminal may choose to continue attempting the upload or not to continue the upload regardless of whether the transmitting end or the receiving end has an error.

Through the steps, under the condition of uploading failure, the reason of uploading failure is prompted, and a terminal user can select whether to continue uploading or cancel uploading and continue normal use.

Fig. 3 is a flowchart (iii) of a method for uploading real scene failures according to an embodiment of the present invention. As shown in fig. 3, determining whether the log file is uploaded successfully includes:

step S302, acquiring the number of attempted uploading of the log file;

step S304, judging whether the number of times of trial uploading is not more than the preset number of times;

step S306, judging whether log files are successfully uploaded or not under the condition that the number of times of attempted uploading is less than or equal to the preset number of times;

and step S308, under the condition that the number of times of trying to upload is larger than the preset number of times, uploading the log file fails.

In step S304, the predetermined number of times is 3-8. Preferably, the preset number of times is 5.

Step S306 is followed by step S110 or S114, and step S308 is followed by step S202.

Through the steps, the number of times of trying to upload is limited, unlimited uploading is avoided, resource occupation is saved, and user waiting time is reduced.

Fig. 4 is a flowchart (iv) of a method for uploading real scene failures according to an embodiment of the present invention. As shown in fig. 4, determining whether the log file is uploaded successfully includes:

step S402, under the condition that log file uploading fails, obtaining the number of times of log file uploading attempts;

step S404, judging whether the number of times of trial uploading is not more than the preset number of times;

step S406, under the condition that the number of attempted uploading is not more than the preset number, acquiring the attempted uploading time and the current time of the log file of the last attempted uploading;

step S408, calculating a time difference between the current time and the time of attempting to upload;

step S410, judging whether the time difference value is not less than a preset time threshold value;

and step S412, under the condition that the time difference value is not less than the preset time threshold value, trying to upload the log file again.

After step S412, step S110 is performed.

In step S404, the preset number of times is 3 to 8 times. Preferably, the preset number of times is 5.

In step S410, the preset time threshold refers to a time interval between two attempts to upload the log file.

In step S410, the preset time threshold is 0.5-2 min. Preferably, the preset time threshold is 1 min.

Further, after step S404, the method further includes:

in case the number of attempts to upload is greater than a preset number, uploading the log file fails.

Wherein, after the log file is failed to be uploaded, the step S202 is performed.

Further, after step S410, the method further includes:

in case the time difference is smaller than the preset time threshold, step S406 is performed.

Through the steps, the retransmission mechanism combining the trial uploading times and the trial uploading time interval is utilized, the short-time unlimited uploading is avoided, the resource occupation is saved, and the user waiting time is reduced.

Fig. 5 is a flowchart (v) of a method for uploading real scene failures according to an embodiment of the present invention. As shown in fig. 5, in the case that an upload failure is required, before acquiring a log recording start instruction, the method further includes:

step S502, judging whether a log system has log files or not;

step S504, under the condition that the log system has log files, deleting the log files and initializing the log system;

and step S506, initializing the log system under the condition that the log system has no log file.

Wherein, after step S504 and step S506, step S102 is executed.

Through the steps, the log system can be detected under the condition that the terminal/browser is started, the log file generated before is prevented from not being cleared, the problems that the log file is remained and uploaded are solved, and the log file generation and log file uploading are prevented from being influenced.

Fig. 6 is a flowchart (vi) of a method of uploading a real scene fault according to an embodiment of the present invention. As shown in fig. 6, after deleting the log file, the method further includes:

step S602, acquiring a solution corresponding to the fault;

and step S604, repairing the fault according to the solution.

In step S602, the solution is formed by the terminal manufacturer/browser manufacturer for the failure, including but not limited to remote guidance, pushing an application installation package, and the like.

Through the steps, the faults of the terminal user can be solved in a targeted manner, the solving steps are reduced, the solving time is shortened, and the solving efficiency is improved.

Fig. 7 is a block diagram (one) of an upload real scene fault apparatus according to an embodiment of the present invention. As shown in fig. 7, an upload real scene failure apparatus 700 for a terminal includes a recording instruction acquisition unit 701, a recording unit 702, an initial file generation unit 703, a log file generation unit 704, an upload unit 705, a first determination unit 706, and a deletion unit 707. The recording instruction acquisition unit 701 is configured to acquire a log recording start instruction and a log recording stop instruction under the condition that a fault needs to be uploaded; the recording unit 702 is configured to record a failure recurrence procedure in a case where a log recording start instruction is acquired, and stop recording in a case where a log stop instruction is acquired; the initial file generating unit 703 is configured to generate an initial file when the recording failure reproduction process is completed; the log file generating unit 704 is configured to add the problem description information to the initial file to generate a log file; the uploading unit 705 is used for attempting to upload a log file; the first judging unit 706 is configured to judge whether the log file is uploaded successfully; the deletion unit 707 is configured to delete the log file in a case where the log file upload is successful.

The recording instruction acquisition unit 701, the recording unit 702, the initial file generation unit 703, the log file generation unit 704, the upload unit 705, the first judgment unit 706, and the deletion unit 707 are in communication connection, including but not limited to wired connection and wireless connection.

The device 700 for uploading a real scene fault is a terminal or a browser installed in the terminal.

Fig. 8 is a block diagram of an apparatus for uploading real scene failures according to an embodiment of the present invention (ii). As shown in fig. 8, the apparatus for uploading real scene fault 700 further includes an attempt number acquisition unit 708 and a second determination unit 709. Wherein, the number of attempts acquisition unit 708 is configured to acquire the number of attempts to upload the log file; the second determining unit 709 is configured to determine whether the number of attempted uploads is not greater than a preset number; the first judging unit 706 is further configured to judge that the log file is successfully uploaded if the number of times of the attempted upload is not greater than a preset number, and judge that the log file is unsuccessfully uploaded if the number of times of the attempted upload is greater than the preset number.

The recording instruction obtaining unit 701, the recording unit 702, the initial file generating unit 703, the log file generating unit 704, the uploading unit 705, the trial number obtaining unit 708, the second judging unit 709, the first judging unit 706, and the deleting unit 707 are in communication connection, including but not limited to wired connection and wireless connection.

Fig. 9 is a block diagram (iii) of an upload real scene failure apparatus according to an embodiment of the present invention. As shown in fig. 9, the apparatus for uploading real scene fault 700 further includes a time obtaining unit 710, a time calculating unit 711, and a third determining unit 712. The time obtaining unit 710 is configured to obtain an upload attempt time of a log file that is uploaded in the last attempt and a current time; the time calculation unit 711 is configured to calculate a time difference between the current time and the time of attempting to upload; the third determining unit 712 is configured to determine whether the time difference is smaller than a preset time threshold; the uploading unit 705 is further configured to try to upload the log file again if the time difference is not less than the preset time threshold.

The recording instruction obtaining unit 701, the recording unit 702, the initial file generating unit 703, the log file generating unit 704, the uploading unit 705, the trial number obtaining unit 708, the second judging unit 709, the time obtaining unit 710, the time calculating unit 711, the third judging unit 712, the first judging unit 706, and the deleting unit 707 are in communication connection, which includes but is not limited to wired connection and wireless connection.

Fig. 10 is a block diagram (iv) of an upload real scene failure apparatus according to an embodiment of the present invention. As shown in fig. 10, the apparatus for uploading real scene fault 700 further includes a feedback information generating unit 713 and a fourth determining unit 714. The feedback information generating unit 713 is configured to generate upload failure information when log file upload fails; a fourth judging unit 714 configured to judge whether to continue attempting to upload the log file in a case where the upload failure information is generated; the uploading unit 705 is further configured to attempt to upload the log file if an attempt to upload the log file continues; the deletion unit 707 is also configured to delete the log file without continuing an attempt to upload the log file.

The recording instruction obtaining unit 701, the recording unit 702, the initial file generating unit 703, the log file generating unit 704, the uploading unit 705, the first judging unit 706, the feedback information generating unit 713, the fourth judging unit 714, and the deleting unit 707 are in communication connection, which includes but is not limited to wired connection and wireless connection.

The feedback information generating unit 713 is further configured to generate upload success information in the case that the log file is successfully uploaded.

Fig. 11 is a frame diagram (v) of an upload real scene failure apparatus according to an embodiment of the present invention. As shown in fig. 11, the apparatus for uploading real scene fault 700 further includes a fifth judging unit 715 and an initializing unit 716. The fifth judging unit 715 is configured to judge whether the log system has a log file; the initialization unit 716 is configured to initialize the log system if the log system has no log file; the deletion unit 707 is also configured to delete the log file in a case where the log system has the log file.

The fifth judging unit 715, the initializing unit 716, the recording instruction acquiring unit 701, the recording unit 702, the initial file generating unit 703, the log file generating unit 704, the uploading unit 705, the first judging unit 706, and the deleting unit 707 are in communication connection, which includes but is not limited to wired connection and wireless connection.

Fig. 12 is a block diagram (vi) of an upload real scene fault apparatus according to an embodiment of the present invention. As shown in fig. 12, the upload real scene failure apparatus 700 further includes a solution acquisition unit 717 and a repair unit 718. Wherein, the solution acquiring unit 717 is configured to acquire a solution corresponding to the failure after deleting the log file; the repair unit 718 is used to repair the failure according to the solution.

The recording instruction obtaining unit 701, the recording unit 702, the initial file generating unit 703, the log file generating unit 704, the uploading unit 705, the first judging unit 706, the deleting unit 707, the solution obtaining unit 717, and the repairing unit 718 are in communication connection, which includes but is not limited to wired connection and wireless connection.

Fig. 13 is a block diagram of an upload real scenario failure system according to an embodiment of the present invention. As shown in fig. 13, an upload real scenario failure system 800 for a terminal includes at least a terminal 810 and a server 820. The terminal 810 is configured to record a fault recurrence process and generate a log file when a fault occurs; the server 820 is used for acquiring a log file transmitted by the terminal, generating a solution corresponding to the log file, and transmitting the solution to the terminal; the terminal 810 is also used to repair the failure according to the solution.

Wherein, several terminals 810 are respectively connected with the server 820 in communication, and the terminals 810 are not connected with each other.

The terminal 810 includes an upload real scene failure apparatus 700.

In addition, the method for uploading the real scene fault can be realized by computer equipment. Components of the computer device may include, but are not limited to, a processor and a memory storing computer program instructions.

In some embodiments, the processor may include a Central Processing Unit (CPU), or A Specific Integrated Circuit (ASIC), or may be configured to implement one or more Integrated circuits of embodiments of the present Application.

In some embodiments, the memory may include mass storage for data or instructions. By way of example, and not limitation, memory may include a Hard Disk Drive (Hard Disk Drive, abbreviated HDD), a floppy Disk Drive, a Solid State Drive (SSD), flash memory, an optical disc, a magneto-optical disc, tape, or a Universal Serial Bus (USB) Drive or a combination of two or more of these. The memory may include removable or non-removable (or fixed) media, where appropriate. The memory may be internal or external to the data processing apparatus, where appropriate. In a particular embodiment, the memory is a Non-Volatile (Non-Volatile) memory. In particular embodiments, the Memory includes Read-Only Memory (ROM) and Random Access Memory (RAM). The ROM may be mask-programmed ROM, Programmable ROM (PROM), Erasable PROM (EPROM), Electrically Erasable PROM (EEPROM), Electrically rewritable ROM (EAROM), or FLASH Memory (FLASH), or a combination of two or more of these, where appropriate. The RAM may be a Static Random-Access Memory (SRAM) or a Dynamic Random-Access Memory (DRAM), where the DRAM may be a Fast Page Mode Dynamic Random-Access Memory (FPMDRAM), an Extended Data Out Dynamic Random Access Memory (EDODRAM), a Synchronous Dynamic Random Access Memory (SDRAM), and the like.

The memory may be used to store or cache various data files for processing and/or communication use, as well as possibly computer program instructions for execution by the processor.

The processor reads and executes the computer program instructions stored in the memory to implement any one of the above-described methods for uploading real scene failures.

In some of these embodiments, the computer device may also include a communication interface and a bus. The processor, the memory and the communication interface are connected through a bus and complete mutual communication.

The communication interface is used for realizing communication among units, devices, units and/or equipment in the embodiment of the application. The communication interface may also be implemented with other components such as: the data communication is carried out among external equipment, image/data acquisition equipment, a database, external storage, an image/data processing workstation and the like.

A bus comprises hardware, software, or both that couple components of a computer device to one another. Buses include, but are not limited to, at least one of the following: data Bus (Data Bus), Address Bus (Address Bus), Control Bus (Control Bus), Expansion Bus (Expansion Bus), and Local Bus (Local Bus). By way of example, and not limitation, a Bus may include an Accelerated Graphics Port (AGP) or other Graphics Bus, an Enhanced Industry Standard Architecture (EISA) Bus, a Front-Side Bus (FSB), a Hyper Transport (HT) Interconnect, an ISA (ISA) Bus, an InfiniBand (InfiniBand) Interconnect, a Low Pin Count (LPC) Bus, a memory Bus, a microchannel Architecture (MCA) Bus, a PCI-Express (PCI-X) Bus, a Serial Advanced Technology Attachment (SATA) Bus, abbreviated VLB) bus or other suitable bus or a combination of two or more of these. A bus may include one or more buses, where appropriate. Although specific buses are described and shown in the embodiments of the application, any suitable buses or interconnects are contemplated by the application.

The computer device can execute the method for uploading the real scene fault in the embodiment of the application.

In addition, in combination with the method for uploading real scene faults in the above embodiments, embodiments of the present application may provide a computer-readable storage medium to implement. The computer readable storage medium having stored thereon computer program instructions; the computer program instructions, when executed by a processor, implement any of the above embodiments of an upload real scenario failure method for a blockchain.

Example 2

This embodiment is a specific embodiment of the present invention.

Fig. 14 is a framework diagram of a specific implementation of a system for uploading real scenario failures according to an embodiment of the present application. As shown in fig. 14, the system for uploading real scene faults includes a server end and a plurality of client ends, wherein the server end is in communication connection with the plurality of client ends in decibels.

Specifically, a browser software end (i.e., a terminal) establishes a client end for collecting and sending logs, and a browser company (i.e., a server end) establishes a server end for receiving and storing logs.

The direct interaction channel is established between the demand side (terminal) and the supply side (browser company), so that the problems of long period, wrong information transmission and the like caused by intermediate multi-party transmission are avoided. By deploying a log system client end and a server end for receiving and storing logs in a company deployment manner at a television software end, the problem of user report is directly processed, so that the time period for solving the problem of user report can be solved, and the workload of intermediate redundant transmission can be solved to ensure the reliability of information and reduce the workload of intermediate transmission; finally, the optimization of user experience and the timeliness of problem handling are achieved.

Fig. 15 is a flowchart illustrating an implementation of a method for uploading real scene faults according to an embodiment of the present disclosure. As shown in fig. 15, the method for uploading real scene faults includes:

step S1501, starting up;

step S1502, initializing and resetting a log system (including detecting and deleting legacy logs);

step S1503, judging whether the problem needs to be reported, executing step S1504 under the condition that the problem needs to be reported, and executing step S1512 under the condition that the problem does not need to be reported;

step S1504, clicking a log recording start button;

step S1505, reproducing the problem, and clicking the recording stopping button;

step S1506, adding problem description and clicking a report button;

step S1507, start to try to send log;

step S1508 of determining whether or not the number of times is 5 or less, and if the number of times is 5 or less, step S1509 is executed, and if the number of times is 5 or more, step S1510 is executed;

step S1509, determining whether the transmission is successful, executing step S1511 if the transmission is successful, and executing step S1507 if the transmission is failed;

step S1510, popping up an error frame, wherein the user selects whether to continue transmission, and if the user selects to continue transmission, the step S1507 is executed, and if the user selects not to continue transmission, the step S1511 is executed;

step S1511, deleting the log file, and executing step S1512;

step S1512, normal use.

Step S1502 corresponds to steps S502 to S506.

Step S1504 corresponds to step S102.

Step S1505 corresponds to steps S104 to S106.

Step S1506 corresponds to step S108.

Step S1507 corresponds to step S110.

Step S1508 corresponds to steps S302 to S308, and steps S402 to S412.

Step S1509 corresponds to step S112.

Step S1510 corresponds to step S202 to step S204.

Step S1511 corresponds to step S114 or step 208.

Step S1512 corresponds to steps S116 to S118.

For step S1502, the browser starts up to initialize the log system and detect or clear the previously left-behind log of the last capture. Specifically, at present, the log is placed in a directory fixed by the system, and the log is deleted after being downloaded and uploaded under normal conditions, so that a system error is prevented when a file is deleted, and the file is not deleted.

In step S1504 to step S1506, when the terminal user needs to upload bug, the terminal user only needs to click the recording button of the log system, then the problem can be copied, click to stop recording after the problem is reproduced, and click the log uploading button after the problem description is filled, and then normally upload the log to the deployed server.

In steps S1507 to S1510, when the log report fails, retransmission is performed by a retransmission mechanism. After a user clicks a report button, the retransmission mechanism has a certain threshold value, and at present, the maximum number of attempts is determined to be 5 times, and the interval between the two times is 1 minute; if still fails, we will return an error code, explaining the reason; two reasons exist at present, one is server end error, and the second is client end error; and meanwhile, a selection page is provided, so that the user can select to continue uploading or cancel the uploading.

After log files are uploaded successfully, the browser company can analyze specific problems according to the problem description and log recorded by a specific server.

Specifically, the client side sends information to the server side, where the data substantially includes: the method comprises the steps that a mac address, description information input by a client, a contact way and a log file recorded manually are recorded on a server after the server receives the information, and then the problem is analyzed according to the information transmitted by the client by the technology.

Specifically, the recording manner is as shown in the following table:

serial number	MAC	E-mail	Description information	LOG
					1	XXXXXXXX	XXXXXXXX	XXXXXXXX	XXXXXXXX
2	XXXXXXXX	XXXXXXXX	XXXXXXXX	XXXXXXXX
					3	XXXXXXXX	XXXXXXXX	XXXXXXXX	XXXXXXXX
4	XXXXXXXX	XXXXXXXX	XXXXXXXX	XXXXXXXX

The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A real scene fault uploading method for a terminal is characterized by comprising the following steps:

recording a fault reproduction process;

acquiring a log recording stopping instruction to generate an initial file;

attempting to upload the log file;

judging whether the log file is uploaded successfully or not;

and deleting the log file when the log file is uploaded successfully.

2. The method for uploading real scene fault according to claim 1, after determining whether the log file is uploaded successfully, further comprising:

deleting the log file without continuing to attempt to upload the log file.

3. The method for uploading real scene failures according to claim 1 or 2, wherein judging whether the log file is uploaded successfully comprises:

obtaining the number of attempted uploading of the log file;

under the condition that the number of attempted uploading is greater than the preset number, failing to upload the log file; and/or

Judging whether the log file is uploaded successfully comprises the following steps:

and under the condition that the time difference value is not smaller than the preset time threshold value, attempting to upload the log file again.

4. The method for uploading real scene fault according to claim 1, wherein before acquiring a log recording start instruction in case of a fault needing to be uploaded, the method further comprises:

judging whether a log system has log files or not;

initializing the log system in the event that the log system does not have the log file.

5. The method for uploading real scene failures according to claim 1, further comprising, after deleting the log file:

acquiring a solution corresponding to the fault;

repairing the fault according to the solution.

6. An upload real scene failure device for a terminal, comprising:

an initial file generating unit, configured to generate an initial file when recording of the failure reproduction process is completed;

an upload unit configured to attempt to upload the log file;

7. The upload real scene failure device of claim 6, further comprising:

the first judging unit is further configured to judge that the log file is successfully uploaded if the number of attempted uploads is not greater than the preset number, and judge that the log file is unsuccessfully uploaded if the number of attempted uploads is greater than the preset number; and/or

the uploading unit is further used for trying to upload the log file again under the condition that the time difference value is not smaller than the preset time threshold value; and/or

The feedback information generating unit is used for generating uploading failure information under the condition that the log file is uploaded unsuccessfully;

the deleting unit is further configured to delete the log file without continuing to attempt to upload the log file; and/or

the deleting unit is further configured to delete the log file if the log system has the log file; and/or

a repair unit for repairing the fault according to the solution.

8. A upload real scene failure system for a terminal, comprising:

9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the upload real scenario failure method of any one of claims 1 to 5 when executing the computer program.

10. A computer-readable storage medium on which a computer program is stored, the program, when executed by a processor, implementing the method for uploading real scene failures as claimed in any one of claims 1 to 5.