One-key fault reporting method, device and equipment, medium and computer program product

Abstract

The invention provides a one-key fault reporting method and device, equipment, a medium and a computer program product. The method comprises the following steps: acquiring fault reporting information; wherein the fault reporting information comprises identity information, system fault information and fault reporting time; identity information in the fault reporting information is authenticated; establishing an event work order according to the identity information in the fault reporting information, the fault reporting time and the system fault information under the condition that the identity information authentication is passed; and determining the tolerance according to the system fault occurrence time and the fault reporting time, and determining the fault repair time based on the tolerance. According to the method, the problem that fault reporting is tedious in the traditional applet customization development process can be solved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a one-click fault reporting method, device, equipment, medium and computer program product. Background Art

[0002] Traditional mini-program development generally uses mini-program template development, applies ready-made mini-program templates, and combines functions into a template mini-program. It is a standardized product, so only standardized mini-program functional requirements can be met. In reality, many requirements need to be customized, and mini-program template development cannot meet the requirements for the implementation of the requirements. Therefore, on this basis, mini-program customized development solves the problem of non-standardized demand implementation. In the process of mini-program customized development, the traditional fault reporting method is cumbersome, resulting in users' needs not being solved in a timely manner. Summary of the invention

[0003] The present application provides a one-click fault reporting method, device, equipment, medium and computer program product to solve the problem of cumbersome fault reporting in the process of custom development of traditional mini-programs.

[0004] In a first aspect, the present application provides a one-key fault reporting method, comprising:

[0005] Obtaining fault reporting information; wherein the fault reporting information includes identity information, system fault information and fault reporting time;

[0006] Authenticating the identity information in the fault reporting information;

[0007] If the identity information authentication is passed, an event work order is created according to the identity information, fault reporting time and system fault information in the fault reporting information;

[0008] The tolerance is determined according to the system fault occurrence time and the fault reporting time, and the fault repair time is determined based on the tolerance.

[0009] In one possible implementation, authenticating the identity information in the fault reporting information includes:

[0010] Based on the identity information database, the identity information is authenticated; wherein the identity information database includes a plurality of identity reserved information;

[0011] If there is a reserved identity information in the identity information database that matches the identity information, then determining that the identity information authentication is successful;

[0012] If the identity information database does not contain the reserved identity information that matches the identity information, it is determined that the identity information authentication fails, and first information is fed back, where the first information is used to guide the identity information that fails the authentication to perform authentication registration.

[0013] In one achievable manner, when the identity information authentication is passed, an event work order is created according to the identity information, fault reporting time and system fault information in the fault reporting information, including:

[0014] The fault reporting information corresponding to each authenticated identity information is stored in the data table;

[0015] Aggregate the fault reporting information in the data table and aggregate the same system fault information into one fault reporting data;

[0016] Create an incident work order based on the fault reporting data.

[0017] In an implementable manner, determining the tolerance according to the system fault occurrence time and the fault reporting time includes:

[0018] The time difference between the system fault occurrence time and the fault reporting time is used as the tolerance.

[0019] In an implementable manner, determining the fault repair time based on the tolerance includes:

[0020] The normalized tolerance is used as the time impact coefficient;

[0021] The fault repair time is determined based on the set repair time and the time influence coefficient.

[0022] In an implementable manner, before obtaining the fault reporting information, the method further includes:

[0023] Randomly generate verification information, and obtain fault reporting information when the verification information is verified within a first set time;

[0024] Based on the second set time, if the identity information in the fault reporting information is not obtained within the second set time, the fault reporting information is obtained.

[0025] In an achievable manner, after determining the fault repair time based on the tolerance, the method further includes:

[0026] Based on the fault repair time and the event work order, feedback information is generated; wherein the feedback information includes the number of the event work order and the fault repair time.

[0027] In a second aspect, the present application provides a one-key fault reporting device, comprising: an information acquisition module, used to obtain fault reporting information; wherein the fault reporting information includes identity information, system fault information and fault reporting time;

[0028] An identity authentication module, used to authenticate the identity information in the fault reporting information;

[0029] A work order creation module, used to create an event work order according to the identity information, fault reporting time and system fault information in the fault reporting information when the identity information authentication is passed;

[0030] The time determination module is used to determine the tolerance according to the system fault occurrence time and the fault reporting time, and determine the fault repair time based on the tolerance.

[0031] In a third aspect, the present application provides an electronic device, comprising: a processor and a memory; the memory is used to store instructions; the processor is used to execute the instructions in the memory, so that the electronic device executes the method described in the first aspect.

[0032] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the method described in the first aspect.

[0033] In a fifth aspect, the present application provides a computer program product, including a computer program, which implements the method described in the first aspect when executed by a processor.

[0034] The one-click fault reporting method, device, equipment, medium and computer program product provided in the present application adopt an identity authentication method to obtain the corresponding system fault information only when the identity authentication is passed, and considers the fault reporting time and the system fault time to determine the user's tolerance, and determines the fault repair time based on the tolerance, so that users can have a good experience while realizing customized needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0036] Figure 1 This is an implementation scenario diagram shown for an exemplary embodiment;

[0037] Figure 2 This is a flow chart of a one-key fault reporting method shown in an exemplary embodiment;

[0038] Figure 3 Another flow chart of a one-key fault reporting method shown in an exemplary embodiment;

[0039] Figure 4 This is a structural diagram of a one-key fault reporting device shown as an exemplary embodiment;

[0040] Figure 5 The present invention is a block diagram of an electronic device showing an exemplary embodiment.

[0041] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0042] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0043] It should be noted that the fault reporting information, identity information and other related information involved in this application (including but not limited to data used for analysis, stored data, displayed data, etc.) are all information and data understood and authorized by the relevant users or fully authorized by all parties, and the collection, use, processing, transmission, provision, disclosure and application of the relevant data comply with the laws, regulations and standards of relevant countries and regions, take necessary confidentiality measures, do not violate public order and good morals, and comply with the principles of legality, legitimacy and necessity.

[0044] First, the terms involved in this application are explained:

[0045] ITSM front-end system: ITSM front-end system is a work order management system based on ITIL (IT Infrastructure Library). It is a tool used to standardize, coordinate and manage IT services. It can help enterprises effectively manage the planning, development, implementation and operation of IT systems.

[0046] BPM monitoring system: By adopting bypass monitoring technology, it converts network mirror traffic into business transactions without modifying applications or affecting production. It provides real process data and fully reflects business behaviors and processes with high precision and low latency. The BPM monitoring system combines threshold alarms with time feature alarms to quantify the real-time status of business system operation through golden indicators such as business volume, response time, response rate, and success rate. It supports second-level and minute-level alarms to meet the business needs of different users. Intelligent fault root cause analysis The fault root cause analysis function can automatically locate the dimensional level and dimensional value that cause the alarm, and associate the dimensional indicators through multi-dimensional statistical analysis functions to deeply analyze the root cause of the application system failure.

[0047] Customized development based on the applet api (interface) development, as the name implies, is to customize the applet development according to the needs of customers. The following technologies are involved in the development process: wxml, wxss, js, operating environment and database. Among them, wxml is a common language for applet, which is used to organize the page structure. wxss is more like css, and its main implementation ideas are basically the same as the development technology of web pages, which is used to define the page style. It is mainly a simple replacement of some tags, most of which are basically the same as the original css, and are implemented by calling the same page. js is one of the essential technologies for developing applet. It is used to implement the interactive logic of applet. Server languages ​​java, springBoot, etc. are used as the development and operation environment of applet to implement the back-end business logic. The database language mysql is used as the database for applet docking to store the data information submitted by the applet.

[0048] For customers with special functional requirements, customized development of mini programs is an option, as mini program template development cannot meet current needs.

[0049] Based on this, a one-click fault reporting method, device, equipment, medium and computer program product are proposed in this embodiment, which aims to solve the problem that the development of mini-program templates cannot meet current needs. Through a simple and fast fault reporting method, users can directly report and obtain feedback on a system fault according to their needs, and reasonably plan the fault repair time, thereby meeting the needs of users for customized development of mini-programs.

[0050] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0051] The one-key fault reporting method provided in this application can be implemented on any electronic device with data processing capabilities, or it can be a one-key fault reporting system. It should be noted that the one-key fault reporting system can be deployed separately on an electronic device in any environment (for example: deployed separately on an edge server in an edge environment), or it can be deployed entirely in a cloud environment, or it can be deployed in a distributed manner in different environments.

[0052] For example, the one-click fault reporting system can be logically divided into multiple parts, each with different functions. The various parts of the one-click fault reporting system can be deployed in any two or three of the electronic device (located on the user side, such as the client), the edge environment, and the cloud environment. The edge environment is an environment that includes a collection of edge electronic devices that are close to the electronic device. The edge electronic devices include: edge servers, edge stations with computing power, etc. The various parts of the one-click fault reporting system deployed in different environments or devices work together to realize the functions of the data processing platform.

[0053] It should be understood that this application does not restrict the deployment of which parts of the one-key fault reporting system are deployed in what specific environment. In actual application, it can be adaptively deployed according to the computing power of the electronic device, the resource usage of the edge environment and the cloud environment, or the specific application requirements.

[0054] like Figure 1 This is an implementation scenario diagram showing an exemplary embodiment. The one-key fault reporting system corresponding to the implementation scenario includes a client 10 and a server 11. The client 10 and the server 11 are connected via network communication.

[0055] The executor of the method of the embodiment of the present application is the server 11, and the client 10 communicates with the server 11. The client 10 sends the fault reporting information to the server 11 through the network. The server 11 is used for one-click fault reporting, and obtains the event work order and fault repair time of the fault reporting information, and can feed back the event work order and fault repair time to the client 10. The client 10 has a graphic user interface, and the one-click fault reporting results can be displayed on the graphic interface.

[0056] In some embodiments, after obtaining the fault reporting information, the server 11 authenticates the identity information in the fault reporting information; if the identity information authentication is successful, an event ticket is established based on the identity information, fault reporting time and system fault information in the fault reporting information; the tolerance is determined based on the system fault occurrence time and fault reporting time, and the fault repair time is determined based on the tolerance.

[0057] Understandably, the one-key fault reporting system can be set up Figure 1 In the server 11, but the example shown in this embodiment Figure 1 The implementation environment shown is only exemplary. In other embodiments, the one-key fault reporting method can also be applied to other implementation environments, and the one-key fault reporting system can also be set in other structures in other implementation environments. No specific limitations are made here.

[0058] In this embodiment, the client 10 is an electronic device on the user side, which can be a wired terminal with a visualization structure or a wireless terminal. In other embodiments, the terminal can be an electronic device with a visualization structure such as a mobile phone, a computer, a tablet, and a vehicle-mounted device.

[0059] The server 11 can be an edge environment and a cloud environment, such as a physical server, a server cluster, and a cloud server, etc., and no specific limitations are given here.

[0060] It is understandable that the one-button fault alarm device can be set at Figure 1 In the server 11, but the example shown in this embodiment Figure 1 The implementation environment shown is only exemplary. In other embodiments, the one-key fault reporting method can also be applied to other implementation environments, and the one-key fault reporting device can also be set in other structures in other implementation environments. No specific limitations are made here.

[0061] Figure 2 A flowchart of a one-key fault reporting method is shown as an exemplary embodiment, which is applied to Figure 1 The server 11 in Figure 2 As shown, the method includes steps S210 to S240, which are described in detail as follows:

[0062] S210: Obtain fault reporting information; wherein the fault reporting information includes identity information, system fault information and fault reporting time.

[0063] In this embodiment, the fault reporting information is sent by the user through the client 10. The identity information is the basic information of the user, such as the user name, user code, etc., where the user name and user code are unique, that is, each different user has a different user name and user code. The system fault information is the fault information reported corresponding to the identity information, for example, it can be the system fault code that appears when the user customizes the development of the applet, and the fault reporting time is the time when the fault reporting information is sent.

[0064] S220: Authenticate the identity information in the fault reporting information.

[0065] In this embodiment, Figure 1 Among the clients 10 that communicate with the server 11, the server 11 only serves users who are authenticated and registered on the server 11. The authentication and registration process may be: the client 11 sends a registration application to the server 11, and if the registration application is approved, receives a registration form sent by the server 11, and after filling in the corresponding identity information according to the registration form, the server 11 generates identity reservation information based on the registered identity information and stores it in the identity information library. In the actual execution process, if the identity information authentication in the fault reporting information fails, the service will be interrupted, that is, the server 11 will not continue to execute the subsequent steps S230 and S240. At this time, the server 11 can feedback a prompt message to the client 10 that sent the fault reporting information, reminding that the user's authorization authentication needs to be completed first.

[0066] In some embodiments, step S220 may include:

[0067] S221. authenticating the identity information based on the identity information database; wherein the identity information database includes a plurality of identity reserved information;

[0068] S222. If there is a reserved identity information in the identity information database that matches the identity information, it is determined that the identity information authentication is successful;

[0069] S223: If the identity information database does not contain the reserved identity information that matches the identity information, it is determined that the identity information authentication fails, and first information is fed back, where the first information is used to guide the identity information that fails the authentication to perform authentication registration.

[0070] In a specific embodiment, a specific method for establishing a secure identity authentication and session mechanism is provided. The server 11 can use the wx.request interface provided by the framework to send an https request, and implement identity information authentication through the account system and login module implemented by the mini program (for example, identifying the user identity through openid or unionid, and establishing an account binding relationship), and if the identity information authentication is passed, a unique user session identifier with a certain complexity is established, and a timeout exit mechanism is set. If a certain idle time is exceeded, the session identifier will become invalid.

[0071] In a specific embodiment, when a user encounters a system failure during the process of customizing and developing a small program through the client 10, the user can communicate with the server 11 and send the corresponding fault reporting information. When the user is an unauthorized user (i.e., the identity authentication information fails), the server 11 will feedback to the client 10: "You are an unauthorized user, please complete your personal information in the company's OA system", and no further operations will be performed on the fault reporting information sent by the client 10. When the user is an authorized user, the subsequent step S230 is executed.

[0072] S230: When the identity information authentication is passed, an event work order is created according to the identity information, fault reporting time and system fault information in the fault reporting information.

[0073] In some embodiments, step S230 may include:

[0074] S231. Store the fault reporting information corresponding to each authenticated identity information in a data table.

[0075] In this embodiment, an exemplary data table is shown in Table 1.

[0076] Serial number Identity information System fault information Fault reporting time 1 <![CDATA[A1]]> <![CDATA[B1]]> <![CDATA[t1]]> 2 <![CDATA[A2]]> <![CDATA[B2]]> <![CDATA[t2]]> 3 <![CDATA[A3]]> <![CDATA[B3]]> <![CDATA[t3 <!-- 5 -->]]> 4 <![CDATA[A4]]> <![CDATA[B4]]> <![CDATA[t4]]> ... ... ... ... i-1 <![CDATA[A i-1 ]]> <![CDATA[B i-1 ]]> <![CDATA[t i-1 ]]> i <![CDATA[A i ]]> <![CDATA[B i ]]> <![CDATA[t i ]]>

[0077] Table 1

[0078] As shown in Table 1, i pieces of fault reporting information can be stored in the data table, where each piece of fault reporting information is numbered according to the order of acquisition time to be stored in the data table. For example, the sequence numbers 1 to i, a smaller sequence number means that the server 11 acquires the fault reporting information earlier, A, B and t represent the identity information, system fault information and fault reporting time respectively, and their subscripts correspond to the sequence numbers of the fault reporting information, such as A1, B1 and t1 respectively represent the identity information, system fault information and fault reporting time included in the first fault reporting information.

[0079] It should be noted that the above-mentioned data table is merely an example and is not intended to limit the present application. It is understandable that in other implementations, the data table is not in the form shown in Table 1, or when it is in the form shown in Table 1, it may have more rows and columns, such as when the fault reporting information also includes other information, there may be more columns.

[0080] S232. Aggregate the fault reporting information in the data table, and aggregate the same system fault information into one fault reporting data.

[0081] In this embodiment, one fault reporting data can be represented by C, where C is a collection of system fault information of the same type, that is, one fault reporting data includes at least one system fault information and the identity information and reporting time corresponding to the system fault information. Its function is to aggregate users with the same repair requirements to facilitate the subsequent determination of the repair time for system faults of the same category.

[0082] S233. Create an event work order based on the fault reporting data.

[0083] In a specific embodiment, step S230 may be processed by the ITSM front-end system. That is, in this embodiment, the ITSM front-end system is used to process the user's fault reporting needs. The specific steps of using the ITSM front-end system to process the fault reporting information are as follows:

[0084] S2301, the ITSM front-end system stores the information transmitted by the "One-click Fault Reporting" applet into the data table;

[0085] S2302, ITSM gathers fault reporting information;

[0086] S2303. ITSM creates a work order based on the aggregated information.

[0087] S240: Determine a tolerance level according to the system fault occurrence time and fault reporting time, and determine the fault repair time based on the tolerance level.

[0088] In this embodiment, the system failure occurrence time can be acquired by the BPM monitoring system.

[0089] In a specific embodiment, the server 11 may be configured with an ITSM front-end system and a BPM monitoring system at the same time, wherein the ITSM front-end system is connected to the BPM monitoring system to obtain the corresponding system fault information provided in the fault reporting information to determine the time when the system fault occurs, and calculate the tolerance based on the fault reporting time, and determine the fault repair time according to the tolerance, so as to determine the fault repair time, thereby ensuring the user experience. Specifically, step S240 may include the following steps:

[0090] S241. Get the user fault reporting time from the ITSM system.

[0091] S242. Find the corresponding time when the system failure occurred from the BPM system.

[0092] S243. Calculate the time difference and analyze user tolerance.

[0093] In this embodiment, the system failure occurrence time can be determined through the BPM monitoring system and the fault reporting time can be obtained through the ITSM front-end system, and the time node difference between ITSM and BPM can be compared to analyze the user experience.

[0094] In some embodiments, the tolerance is determined based on the system fault occurrence time and the fault reporting time, including: taking the time difference between the system fault occurrence time and the fault reporting time as the tolerance. For example, the calculation formula can be:

[0095] ε=T1-T2

[0096] In the formula, ε represents the tolerance; T1 represents the fault reporting time, and T2 represents the time when the system fault occurs.

[0097] In some embodiments, based on the tolerance, the fault repair time is determined by the following steps:

[0098] S2401. Use the normalized tolerance as the time impact coefficient.

[0099] In this embodiment, the calculation formula of the time impact coefficient may be:

[0100]

[0101] In the formula, ε' represents the time influence coefficient, ε min Represents the minimum value of tolerance, ε max Indicates the maximum value of tolerance.

[0102] S2402: Determine the fault repair time based on the set repair time and the time impact coefficient.

[0103] In this embodiment, the set repair time can be determined based on the historical fault repair time. The historical fault repair time refers to the time from the fault reporting time to the start of fault repair, represented by the symbol t0. For example, the set repair time can be the mean, median or minimum value of the historical fault repair time. The fault repair time represents the time from the current fault reporting time to the start of fault repair, represented by the symbol t. The fault repair time can be calculated by the following formula:

[0104] t=t0+t0ε'

[0105] In the above formula, when calculating the fault repair time, the tolerance is taken into account. The greater the tolerance, the greater the value of the fault repair time t, and the smaller the tolerance, the smaller the value of the fault repair time.

[0106] In some embodiments, Figure 3 FIG. 1 is another flow chart of a one-key fault reporting method according to an exemplary embodiment. Figure 3 As shown, before obtaining the fault reporting information, the method further includes:

[0107] S310: randomly generate verification information, and when the verification information is verified within a first set time, obtain fault reporting information;

[0108] S320: Based on the second set time, if the identity information in the fault reporting information is not obtained within the second set time, the fault reporting information is obtained.

[0109] In this embodiment, before the server 11 obtains the fault report information from the client 10, a verification code should be added when submitting the fault report to the user to prevent frequent malicious submission of fault tickets and DOS attacks; at the same time, the same account shall not repeatedly submit the same fault within a period of time.

[0110] In some embodiments, after determining the fault repair time based on the tolerance, the method further includes: generating feedback information based on the fault repair time and the event work order; wherein the feedback information includes the number of the event work order and the fault repair time.

[0111] In this embodiment, the server 11 generates feedback information based on the fault repair time and the event work order, and feeds back the feedback information to the corresponding client 10. For example, the client 10 may be fed back: "The *** system fault you reported is being processed, the work order number is *****, and it is currently in the ** stage.", where the "** stage" is determined based on the fault repair time and the current time.

[0112] When feeding back the information submitted by the customer to the client 10, pay attention to desensitizing the private data in the echo data. Specifically, when the data is transmitted between systems, it needs to be uniformly encoded, and special characters need to be encoded or filtered to prevent SQL injection or XSS injection. Since it involves user privacy information, the data needs to be encrypted during transmission to ensure that personal sensitive data is not leaked. Encode the output content of the work order. Format the time data type.

[0113] Figure 4 FIG. 4 is a structural diagram of a one-key fault reporting device shown in an exemplary embodiment. The one-key fault reporting device 400 includes:

[0114] The information acquisition module 410 is used to acquire fault reporting information; wherein the fault reporting information includes identity information, system fault information and fault reporting time;

[0115] The identity authentication module 430 is used to authenticate the identity information in the fault reporting information;

[0116] The work order creation module 450 is used to create an event work order according to the identity information, fault reporting time and system fault information in the fault reporting information when the identity information authentication is passed;

[0117] The time determination module 470 is used to determine the tolerance according to the system fault occurrence time and the fault reporting time, and determine the fault repair time based on the tolerance.

[0118] In one possible implementation, the identity authentication module includes:

[0119] An information authentication unit, used to authenticate identity information based on an identity information database; wherein the identity information database includes a plurality of identity reserved information;

[0120] The identity matching unit is used to determine that the identity information authentication is successful if there is an identity reserved information matching the identity information in the identity information database; if the identity reserved information matching the identity information does not exist in the identity information database, determine that the identity information authentication is unsuccessful, and feedback the first information, the first information is used to guide the identity information that failed the authentication to be authenticated and registered.

[0121] In one possible implementation, the work order creation module includes:

[0122] A data storage unit, used to store the fault reporting information corresponding to each authenticated identity information in a data table;

[0123] A data aggregation unit is used to aggregate the fault reporting information in the data table and aggregate the same system fault information into one fault reporting data;

[0124] The work order building unit is used to create an event work order based on the fault reporting data.

[0125] In one possible implementation, the time determination module includes:

[0126] The tolerance calculation unit is used to use the time difference between the system fault occurrence time and the fault reporting time as the tolerance.

[0127] In one possible implementation, the time determination module includes:

[0128] A coefficient calculation unit, used for taking a normalized tolerance as a time influence coefficient;

[0129] The time calculation unit is used to determine the fault repair time based on the set repair time and the time influence coefficient.

[0130] In one possible implementation, the one-key fault reporting device further includes:

[0131] A verification unit, used to randomly generate verification information, and obtain fault reporting information when the verification information is verified within a first set time;

[0132] The time authentication unit is used to obtain the fault reporting information based on a second set time, if the identity information in the fault reporting information is not obtained within the second set time.

[0133] In one possible implementation, the one-key fault reporting device further includes:

[0134] The information feedback unit is used to generate feedback information based on the fault repair time and the event work order; wherein the feedback information includes the number of the event work order and the fault repair time.

[0135] The one-key fault reporting device provided in this embodiment can be used to execute the above-mentioned one-key fault reporting method. Its implementation principle and technical effects are similar, and this embodiment will not be repeated here.

[0136] Figure 5 is a block diagram of an electronic device according to an exemplary embodiment. Figure 5 The electronic device 500 may include: a processor 51 and a memory 52, wherein the processor 51 and the memory 52 can communicate; exemplarily, the processor 51 and the memory 52 communicate via a communication bus 53, the memory 52 is used to store instructions, and the processor 51 is used to call the instructions in the memory to execute the one-key fault reporting method shown in any of the above method embodiments.

[0137] The processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the present application may be directly implemented as being executed by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor.

[0138] The present application provides a computer-readable storage medium, on which computer execution instructions are stored; when the computer execution instructions are executed by a processor, they are used to implement a one-click fault reporting method as in any of the above embodiments.

[0139] An embodiment of the present application provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the above-mentioned one-key fault reporting method is implemented.

[0140] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0141] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A one-key fault reporting method, characterized in that: include: Obtaining fault reporting information; wherein the fault reporting information includes identity information, system fault information and fault reporting time; Authenticating the identity information in the fault reporting information; If the identity information authentication is passed, an event work order is created according to the identity information, fault reporting time and system fault information in the fault reporting information; The tolerance is determined according to the system fault occurrence time and the fault reporting time, and the fault repair time is determined based on the tolerance.

2. The method according to claim 1, characterized in that Authenticating the identity information in the fault reporting information includes: Based on the identity information database, the identity information is authenticated; wherein the identity information database includes a plurality of identity reserved information; If there is a reserved identity information in the identity information database that matches the identity information, then determining that the identity information authentication is successful; If the identity information database does not contain the reserved identity information that matches the identity information, it is determined that the identity information authentication fails, and first information is fed back, where the first information is used to guide the identity information that fails the authentication to perform authentication registration.

3. The method according to claim 1, characterized in that If the identity information authentication is passed, an event work order is created based on the identity information, fault reporting time and system fault information in the fault reporting information, including: The fault reporting information corresponding to each authenticated identity information is stored in the data table; Aggregate the fault reporting information in the data table and aggregate the same system fault information into one fault reporting data; Create an incident work order based on the fault reporting data.

4. The method according to any one of claims 1 to 3, characterized in that Determining the tolerance based on the system fault occurrence time and fault reporting time includes: The time difference between the system fault occurrence time and the fault reporting time is used as the tolerance.

5. The method according to any one of claims 1 to 3, characterized in that: The determining of the fault repair time based on the tolerance includes: The normalized tolerance is used as the time impact coefficient; The fault repair time is determined based on the set repair time and the time influence coefficient.

6. The method according to claim 1, characterized in that Before obtaining the fault reporting information, the method further includes: Randomly generate verification information, and obtain fault reporting information when the verification information is verified within a first set time; Based on the second set time, if the identity information in the fault reporting information is not obtained within the second set time, the fault reporting information is obtained.

7. The method according to any one of claims 1 to 3, characterized in that After determining the fault repair time based on the tolerance, the method further includes: Based on the fault repair time and the event work order, feedback information is generated; wherein the feedback information includes the number of the event work order and the fault repair time.

8. A one-button fault reporting device, characterized in that: include: An information acquisition module, used to acquire fault reporting information; wherein the fault reporting information includes identity information, system fault information and fault reporting time; An identity authentication module, used to authenticate the identity information in the fault reporting information; A work order creation module, used to create an event work order according to the identity information, fault reporting time and system fault information in the fault reporting information when the identity information authentication is passed; The time determination module is used to determine the tolerance according to the system fault occurrence time and the fault reporting time, and determine the fault repair time based on the tolerance.

9. An electronic device, characterized in that: The electronic device comprises: a processor and a memory; the memory is used to store instructions; the processor is used to execute the instructions in the memory, so that the electronic device executes the method as claimed in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 7 when executed by a processor.

11. A computer program product, characterized in that The method comprises a computer program, which implements the method according to any one of claims 1 to 7 when being executed by a processor.

Images