CN111010300A - Method, system, storage medium and terminal device for fault announcement - Google Patents

Method, system, storage medium and terminal device for fault announcement Download PDF

Info

Publication number
CN111010300A
CN111010300A CN201911306112.9A CN201911306112A CN111010300A CN 111010300 A CN111010300 A CN 111010300A CN 201911306112 A CN201911306112 A CN 201911306112A CN 111010300 A CN111010300 A CN 111010300A
Authority
CN
China
Prior art keywords
fault
file
user
server
file server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN201911306112.9A
Other languages
Chinese (zh)
Inventor
桂豪纵
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
TCL China Star Optoelectronics Technology Co Ltd
Original Assignee
Shenzhen China Star Optoelectronics Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen China Star Optoelectronics Technology Co Ltd filed Critical Shenzhen China Star Optoelectronics Technology Co Ltd
Priority to CN201911306112.9A priority Critical patent/CN111010300A/en
Publication of CN111010300A publication Critical patent/CN111010300A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0686—Additional information in the notification, e.g. enhancement of specific meta-data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The invention relates to the technical field of communication, and provides a method, a system, a storage medium and a terminal device for fault announcement, which comprises the steps of checking a service state when a user successfully logs in an APP at a user side; when the service state is abnormal, configuring a fault announcement file in a management background according to the fault identification, and feeding back the fault announcement file to a file server; when the user logs in the APP at the user side and the logging is abnormal, the fault announcement file is obtained from the file server; and when the failure notice file is failed to be acquired from the file server, sending first prompt information, wherein the first prompt information is used for prompting the internal abnormality of the file server. The invention can self-define the content of the announcement, the fault announcement does not influence the normal service use, the user can be informed quickly after the fault content is configured, the fault announcement does not depend on the service, the fault announcement is highly customized, the fault announcement can take effect quickly, and the invention is friendly to operation and maintenance and customer service.

Description

Method, system, storage medium and terminal device for fault announcement
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method, a system, a storage medium, and a terminal device for fault notification.
Background
When the server is released and deployed and fails, part or all functions cannot be normally used, and no prompt is provided for a user, so that the user can complain in a large area and product public praise is influenced.
When long-connection push is used for pushing fault information to a client, a lot of user information is often required to be inquired, but at the moment, user service or related service may not be available, so that push efficiency is affected or push is not achieved at all.
Disclosure of Invention
The invention aims to provide a fault announcement method, a fault announcement system, a storage medium and terminal equipment, which can inform a user of fault information in time without depending on user service when a server has a fault and reduce the effect of a large number of complaints on a line.
The technical scheme provided by the invention is as follows:
the invention provides a fault announcement method, which comprises the following steps:
and when the user successfully logs in the APP at the user side, checking the service state.
And when the service state is abnormal, configuring a fault announcement file in a management background according to the fault identification, and feeding back the fault announcement file to a file server.
And when the user logs in the APP at the user side and the logging is abnormal, acquiring the fault announcement file from the file server.
Further, when the user logs in the APP at the user side and the login is abnormal, the method includes the following steps after obtaining the fault announcement file from the file server:
and when the failure notice file is failed to be acquired from the file server, sending first prompt information, wherein the first prompt information is used for prompting the internal exception of the file server.
And when the fault bulletin file is successfully acquired from the file server, sending second prompt information, wherein the second prompt information is used for showing the content of the fault bulletin file to the user.
Further, the checking the service status specifically includes the steps of:
and the user side establishes long connection with the access layer server.
And the user side sends a heartbeat packet to the access layer server.
After receiving the heartbeat packet, the access layer server feeds a heartbeat response packet back to the user side; the heartbeat response packet includes a service status therein.
Further, after the access layer server receives the heartbeat packet, the method for sending a heartbeat response packet back to the user side includes the following steps:
and when the service state is abnormal, the access layer server sends a fault identifier to the management background.
Further, after the access layer server receives the heartbeat packet, the method further includes the following steps after a heartbeat response packet is fed back to the user side:
and when the service state is normal, the user side continuously sends the heartbeat packet to the access layer server.
The invention provides a system for fault announcement, which comprises:
and the user side is used for logging in the APP.
And the service state checking module is connected with the user side and used for checking the service state.
And the management background is connected with the file server and used for configuring the fault announcement file according to the fault identification and feeding the fault announcement file back to the file server.
And the file server is connected with the user side and used for acquiring the fault announcement file from the file server when the user logs in the APP at the user side and the logging is abnormal.
Further, still include:
and the first prompting module is connected with the file server and used for sending first prompting information to prompt the user that the interior of the file server is abnormal when the fault notice file is failed to be obtained from the file server.
And the second prompting module is connected with the file server and used for sending out second prompting information when the fault notice file is successfully acquired from the file server and displaying the content of the fault notice file to the user.
Further, the service status checking module comprises:
the access layer server is connected with the user side and used for establishing long connection with the user side and feeding back a heartbeat response packet to the user side after receiving the heartbeat packet; the heartbeat response packet includes a service status therein.
The invention also provides a computer-readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, is adapted to carry out the method of fault notification as defined in any one of the above.
The invention also provides a terminal device, which comprises a memory and a processor, wherein the memory stores a computer program running on the processor, and the terminal device is characterized in that the processor executes the computer program to realize the fault notification method.
The fault announcement method provided by the invention has the following beneficial effects:
1) in order to avoid the problems that a server is released and deployed and fails, partial functions or all functions cannot be normally used, and no prompt is provided for a user, which causes large-area complaints to the user, after logging in an APP successfully, service state inspection is carried out during use, when the service state is abnormal, operation and maintenance personnel configure fault announcement contents to be fed back to a file server in a self-defining manner in a management background, when a service fault occurs, a user side acquires a fault announcement file edited by the operation and maintenance personnel from the file server, after the fault content configuration is completed, the user can be informed quickly, service of the operation and maintenance personnel and the user is not dependent on business service, and the operation and maintenance personnel and the user are friendly.
2) When a service fault occurs, a user side acquires a fault announcement file configured by an operation and maintenance worker in a background from a file server, when the user side fails to acquire the fault announcement file from the file server, a first prompt message is sent to prompt a user that the file server is abnormal, and when the user side successfully acquires the fault announcement file from the file server, the content of the fault announcement is displayed on a user side screen to inform the user of the fault reason, the fault state and the like. When the server fails, the fault information including fault reasons, influence ranges, predicted recovery time and the like can be informed to the user in time without depending on user service, and a large number of complaints on the line are effectively reduced.
3) After the APP is successfully logged in, the user side and the access layer server establish long connection, the user side sends a heartbeat package to the access layer server, the access layer feeds back a heartbeat response package to the user side, the package contains a service abnormal state, operation and maintenance personnel edit a fault announcement file to the file server at a management background according to a fault identification, the user side obtains the fault announcement file from the file server, the heartbeat check service state is sent regularly during the use period of the user, when the operation and maintenance personnel find the fault recovery, the fault state is modified at the management background, and the effect that the fault announcement is cancelled when the APP finds that the fault state of the heartbeat package is recovered to be normal.
Drawings
The above features, technical features, advantages and implementations of a method, system, storage medium and terminal device for fault notification will be further described in the following detailed description of preferred embodiments in a clearly understandable manner, in conjunction with the accompanying drawings.
FIG. 1 is a flow diagram of one embodiment of a method of fault notification of the present invention;
FIG. 2 is a flow chart of another embodiment of a method of fault notification of the present invention;
FIG. 3 is a flow chart of yet another embodiment of a method of fault notification of the present invention;
FIG. 4 is a flow chart of yet another embodiment of a method of fault notification of the present invention;
FIG. 5 is a flow chart of one embodiment of a method of fault notification of the present invention;
FIG. 6 is a schematic block diagram of one embodiment of a system for fault notification of the present invention;
fig. 7 is a schematic structural diagram of an embodiment of a terminal device of the present invention.
The reference numbers illustrate: 10. a memory; 11. a computer program; 12. a processor; 20. a user side; 21. a file server; 22. managing a background; 23. a first prompt module; 24. a second prompt module; 30. a service status check module; 31. and accessing the layer server.
Detailed Description
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following description will be made with reference to the accompanying drawings. It is obvious that the drawings in the following description are only some examples of the invention, and that for a person skilled in the art, other drawings and embodiments can be derived from them without inventive effort.
For the sake of simplicity, the drawings only schematically show the parts relevant to the present invention, and they do not represent the actual structure as a product. In addition, in order to make the drawings concise and understandable, components having the same structure or function in some of the drawings are only schematically illustrated or only labeled. In this document, "one" means not only "only one" but also a case of "more than one".
One embodiment of the present invention, as shown in fig. 1, is a method for fault notification, comprising the steps of:
s100 checks the service status when the user successfully logs in the APP at the user terminal 20.
Specifically, the user performs APP login operation at the user end 20, and the user end 20 includes but is not limited to a smart watch, a mobile phone, and a tablet computer. And if the APP login is successful, the user uses the APP device to check whether the service state is abnormal.
S200, when the service state is abnormal, configuring a fault announcement file in the management background 22 according to the fault identification, and feeding back the fault announcement file to the file server 21.
Specifically, after the management background 22 configures the fault bulletin file, two actions are generated, one is to upload the fault bulletin file to the file server; secondly, the fault identifier in the heartbeat response packet of the access layer server 31 is modified into 'service fault'. If the login is abnormal, the fault notice is directly obtained from the file server, the login is not abnormal, if some service functions are abnormal, whether a service fault exists or not is judged through the fault identification of the heartbeat response packet, and if the service fault exists, the fault notice is obtained from the file server. The difference between login and non-login is that some apps are connected to the access layer server after login is needed, in the using process, when a service fails, a user operation and maintenance personnel is timely notified through heartbeat that a service failure or a release change and other conditions affecting normal service use of the service occur, namely when the service state is abnormal, the fault announcement file content is configured and the fault state is modified in the background management system, and the fault announcement file content is fed back to the file server 21. The function of the file server 21 is to provide files to the server. It strengthens the function of memory and simplifies the management of network data. The performance of the system is improved, the availability of data is improved, the complexity of management is reduced, and the operation cost is reduced.
S300, when the user logs in the APP at the user side 20 and the login is abnormal, the fault announcement file is obtained from the file server 21.
Specifically, when the user logs in the APP at the user end 20 and has login abnormality, such as http status codes 502 and 504, the user end 20 obtains the fault announcement file from the file server 21. http status code 502 indicates that an invalid response is received from an upstream server when a server operating as a gateway or proxy attempts to execute a request. The http status code 404 indicates that the request failed, that the resource desired by the request was not found on the server, and that there is no information to tell the user whether the situation is temporary or permanent, and if the server knows that it is, the http status code 410 should be used to tell that the old resource is permanently unavailable because of some internal configuration mechanism problem, and that there is no address to jump to. 404 this status code is widely used in situations where the server does not want to reveal why the request was denied or no other suitable response is available.
Specifically, in this embodiment, in order to avoid server release deployment and failure, some functions or all functions cannot be used normally, and there is no prompt to the user, which results in the problem of large-area complaints of the user, after the APP is successfully logged in, during the use, the service state is checked, when the service state is abnormal, the operation and maintenance staff self-defines the configuration fault announcement content in the management background 22 and feeds back the configuration fault announcement content to the file server 21, when the service failure occurs, the user side 20 obtains the fault announcement file edited by the operation and maintenance staff from the file server 21, after the configuration of the fault content is completed, the user can be notified relatively quickly, the operation and maintenance staff and the customer service are not dependent on the service, and the user friendliness is provided.
Another embodiment of the present invention, as shown in fig. 2, is a method for fault notification, comprising the steps of:
s100 checks the service status when the user successfully logs in the APP at the user terminal 20.
Specifically, the user performs APP login operation at the user end 20, and the user end 20 includes but is not limited to a smart watch, a mobile phone, and a tablet computer. And if the APP login is successful, the user uses the APP device to check whether the service state is abnormal.
S101 the user side 20 executes the business logic.
Specifically, when the user logs in the APP successfully at the user end 20, on the one hand, the service state is checked, and on the other hand, the service logic, that is, the APP is executed.
S200, when the service state is abnormal, configuring a fault announcement file in the management background 22 according to the fault identification, and feeding back the fault announcement file to the file server 21.
Specifically, when discovering that there is a service failure or there is a distribution change that affects normal service use, that is, when the service state is abnormal, the operation and maintenance staff configures the content of the fault announcement file and modifies the fault state in the background management system, and feeds back the content of the fault announcement file to the file server 21. The function of the file server 21 is to provide files to the server. It enhances the functionality of the memory 10 and simplifies the management of network data. The performance of the system is improved, the availability of data is improved, the complexity of management is reduced, and the operation cost is reduced.
S300, when the user logs in the APP at the user side 20 and the login is abnormal, the fault announcement file is obtained from the file server 21.
Specifically, when the user logs in the APP at the user end 20 and has login abnormality, such as http status codes 502 and 504, the user end 20 obtains the fault announcement file from the file server 21. http status code 502 indicates that an invalid response is received from an upstream server when a server operating as a gateway or proxy attempts to execute a request. The http status code 404 indicates that the request failed, that the resource desired by the request was not found on the server, and that there is no information to tell the user whether the situation is temporary or permanent, and if the server knows that it is, the http status code 410 should be used to tell that the old resource is permanently unavailable because of some internal configuration mechanism problem, and that there is no address to jump to. 404 this status code is widely used in situations where the server does not want to reveal why the request was denied or no other suitable response is available.
In another embodiment of the present invention, as shown in fig. 3, a method for fault notification includes the steps of:
s100 checks the service status when the user successfully logs in the APP at the user terminal 20.
Specifically, the user performs APP login operation at the user end 20, and the user end 20 includes but is not limited to a smart watch, a mobile phone, and a tablet computer. And if the APP login is successful, the user uses the APP device to check whether the service state is abnormal.
S200, when the service state is abnormal, configuring a fault announcement file in the management background 22 according to the fault identification, and feeding back the fault announcement file to the file server 21.
Specifically, when discovering that there is a service failure or there is a distribution change that affects normal service use, that is, when the service state is abnormal, the operation and maintenance staff configures the content of the fault announcement file and modifies the fault state in the background management system, and feeds back the content of the fault announcement file to the file server 21. The function of the file server 21 is to provide files to the server. It enhances the functionality of the memory 10 and simplifies the management of network data. The performance of the system is improved, the availability of data is improved, the complexity of management is reduced, and the operation cost is reduced.
S300, when the user logs in the APP at the user side 20 and the login is abnormal, the fault announcement file is obtained from the file server 21.
Specifically, when the user logs in the APP at the user end 20 and has login abnormality, such as http status codes 502 and 504, the user end 20 obtains the fault announcement file from the file server 21. http status code 502 indicates that an invalid response is received from an upstream server when a server operating as a gateway or proxy attempts to execute a request. The http status code 404 indicates that the request failed, that the resource desired by the request was not found on the server, and that there is no information to tell the user whether the situation is temporary or permanent, and if the server knows that it is, the http status code 410 should be used to tell that the old resource is permanently unavailable because of some internal configuration mechanism problem, and that there is no address to jump to. 404 this status code is widely used in situations where the server does not want to reveal why the request was denied or no other suitable response is available.
S310, when the failure notice file is failed to be acquired from the file server 21, sending a first prompt message, wherein the first prompt message is used for prompting the internal abnormality of the file server 21.
Specifically, when the client 20 fails to obtain the fault bulletin file from the file server 21, that is, the fault bulletin file cannot be obtained from the file server 21, it indicates that the file server 21 is abnormal, and at this time, the client 20 sends a first prompt message to prompt the user that the file server 21 is abnormal.
S320, when the fault bulletin file is successfully acquired from the file server 21, sending a second prompt message, where the second prompt message is used to show the content of the fault bulletin file to the user.
Specifically, when the client 20 successfully obtains the fault notice file from the file server 21, the content of the fault notice is displayed on the screen of the client 20 for informing the user of the fault reason, the fault state, and the like.
Based on the foregoing embodiment, in this embodiment, when a service failure occurs, the user 20 obtains the failure notice file configured by the operation and maintenance staff in the background from the file server 21, when the user 20 fails to obtain the failure notice file from the file server 21, a first prompt message is sent to prompt the user that the file server 21 is abnormal, and when the user 20 successfully obtains the failure notice file from the file server 21, the content of the failure notice is displayed on the screen of the user 20, so as to notify the user of the reason of the failure, the state of the failure, and the like. When the server fails, the fault information including fault reasons, influence ranges, predicted recovery time and the like can be informed to the user in time without depending on user service, and a large number of complaints on the line are effectively reduced.
Still another embodiment of the present invention, as shown in fig. 1 and fig. 4, is a method for fault notification, comprising the steps of:
s100 checks the service status when the user successfully logs in the APP at the user terminal 20.
Specifically, the user performs APP login operation at the user end 20, and the user end 20 includes but is not limited to a smart watch, a mobile phone, and a tablet computer. And if the APP login is successful, the user uses the APP device to check whether the service state is abnormal.
Specifically, the checking the service state specifically includes the steps of:
s110 the user terminal 20 establishes a long connection with the access stratum server 31.
Specifically, a long connection means that multiple data packets can be continuously transmitted over one connection, and during the connection holding period, if no data packet is transmitted, a link detection packet needs to be transmitted by two parties. Long connections are often used for frequent, point-to-point communications and the number of connections cannot be too great. Each TCP connection needs three-step handshake, which requires time, if each operation is short connection, the processing speed is greatly reduced if the operation is repeated, so that each operation is not disconnected after the operation is finished, and a data packet can be directly sent during the next processing without establishing TCP connection.
S120 the user terminal 20 sends a heartbeat packet to the access stratum server 31.
Specifically, the access layer server 31 is a service that maintains a tcp long connection with the client, like a gateway service.
S130, after receiving the heartbeat packet, the access layer server 31 feeds back a heartbeat response packet to the user terminal 20; the heartbeat response packet includes a service status therein.
Specifically, the fault flag in the heartbeat response packet fed back by the access stratum server 31 is modified to "there is a service fault". If the login is abnormal, the fault notice is directly obtained from the file server, the login is not abnormal, if some service functions are abnormal, whether a service fault exists or not is judged through the fault identification of the heartbeat response packet, and if the service fault exists, the fault notice is obtained from the file server. The difference between login and non-login is that some apps are connected to the access layer server after login is needed, and in the using process, when the service fails, the user is timely notified through heartbeat. After the user terminal 20 establishes the long connection with the access stratum server 31, the user terminal 20 sends a heartbeat packet to the access stratum server 31, and after receiving the heartbeat packet, the access stratum server 31 feeds back a heartbeat response packet to the user terminal 20. Two programs on the network exchange data via a bidirectional communication link, one end of which is called a SOCKET. Both receiving and sending data in the network are implemented using socks. But if the socket is disconnected, there must be a problem when sending and receiving data. To determine if this socket is still available, a heartbeat mechanism is created in the system. The heartbeat is to send a self-defined structure (heartbeat packet or heartbeat frame) at regular time to let the other party know that the other party is online so as to ensure the validity of the link. The heartbeat packet is a self-defined command word which is used for regularly informing the self state of the other side between the client side and the server, is sent at a certain time interval, is similar to the heartbeat, and is called as the heartbeat packet.
S131, when the service status is abnormal, the access layer server 31 sends a fault identifier to the management background 22.
Preferably, when the user 20 does not send a heartbeat packet to the access stratum server 31, or the access stratum server 31 does not receive a heartbeat packet, or the access stratum does not feed back a heartbeat response packet to the user 20, the service state is abnormal, at this time, the access stratum server 31 sends a fault identifier to the management background 22, and when the maintenance personnel discovers that a service fault or a distribution change or the like affects normal service use, the fault notification file content is configured and the fault state is modified in the background management system.
S132, when the service status is normal, the ue 20 continues to send the heartbeat packet to the access stratum server 31.
Specifically, when the service status is normal, in the IDLE, the ue 20 continues to send the heartbeat packet to the access stratum server 31, and the IDLE is a time interval between two heartbeat packets sent by the ue 20 to the access stratum server 31.
S200, when the service state is abnormal, configuring a fault announcement file in the management background 22 according to the fault identification, and feeding back the fault announcement file to the file server 21.
Specifically, when discovering that there is a service failure or there is a distribution change that affects normal service use, that is, when the service state is abnormal, the operation and maintenance staff configures the content of the fault announcement file and modifies the fault state in the background management system, and feeds back the content of the fault announcement file to the file server 21. The function of the file server 21 is to provide files to the server. It enhances the functionality of the memory 10 and simplifies the management of network data. The performance of the system is improved, the availability of data is improved, the complexity of management is reduced, and the operation cost is reduced.
S300, when the user logs in the APP at the user side 20 and the login is abnormal, the fault announcement file is obtained from the file server 21.
Specifically, when the user logs in the APP at the user end 20 and has login abnormality, such as http status codes 502 and 504, the user end 20 obtains the fault announcement file from the file server 21. http status code 502 indicates that an invalid response is received from an upstream server when a server operating as a gateway or proxy attempts to execute a request. The http status code 404 indicates that the request failed, that the resource desired by the request was not found on the server, and that there is no information to tell the user whether the situation is temporary or permanent, and if the server knows that it is, the http status code 410 should be used to tell that the old resource is permanently unavailable because of some internal configuration mechanism problem, and that there is no address to jump to. 404 this status code is widely used in situations where the server does not want to reveal why the request was denied or no other suitable response is available.
In this embodiment, after the APP logs in successfully, the user 20 establishes long connection with the access layer server 31, the user 20 sends a heartbeat packet to the access layer server 31, the access layer feeds back a heartbeat response packet to the user 20, the packet includes a service abnormal state, the operation and maintenance staff edits the fault announcement file to the file server 21 in the management background 22 according to the fault identifier, the user 20 obtains the fault announcement file from the file server 21, the user sends a heartbeat check service state regularly during use, when the operation and maintenance staff finds that the fault is recovered, the management background 22 modifies the fault state, and the APP cancels the effect of the fault announcement if the fault state of the heartbeat packet is recovered normally.
One embodiment of the present invention, as shown in fig. 5, is a method for fault notification, including:
s1 when the operation and maintenance personnel find that the normal use of the service is affected by service failure, release change and the like, the operation and maintenance personnel configure the content of the failure notice file and modify the failure state in the background management system.
S2, the user logs in, if App logs in abnormally (http status codes 502 and 404, etc.), then step S3 is executed. The login successfully executes step S4.
S3 acquires the bulletin file from the file server 21, and the address of the bulletin file is written to the app. And prompting internal abnormity of the service when the acquisition of the notice file fails, and prompting notice content when the acquisition is successful.
S4 establishes a long connection with the access stratum server 31.
S5 sends heartbeat packets after successful connection. The access stratum server 31 returns a heartbeat response packet, which includes a service exception status. If the status is abnormal, step S3 is executed, and if normal, no processing is performed.
S6 timed heartbeat check service status during user usage
And S7, if the operation and maintenance personnel find that the fault is recovered, the fault state is modified in the management background 22, and if the app finds that the fault state of the heartbeat package is recovered to be normal, the fault notice is cancelled.
Specifically, the method further includes the steps after the user successfully logs in the APP at the user terminal 20;
s8 the user terminal 20 executes the service logic.
Preferably, in this embodiment, the fault notification may also be pushed through a long connection.
Specifically, in this embodiment, the content of the bulletin can be customized, the fault bulletin does not affect normal service usage, the user can be notified quickly after the fault content is configured, the fault bulletin does not depend on service, the fault bulletin is highly customized, can take effect quickly, and is friendly to operation and maintenance and customer service. Ensuring that the file server 21 and the access stratum server 31 are stably available is a key factor of the present invention.
One embodiment of the present invention, as shown in fig. 6, is a system for fault notification, including:
and the user terminal 20 is used for logging in the APP.
A service status checking module 30 connected to the user terminal 20 for checking a service status;
the management background 22 is connected with the file server 21 and is used for configuring a fault announcement file according to the fault identification and feeding the fault announcement file back to the file server 21;
and the file server 21 is connected with the user side 20 and is used for acquiring the fault announcement file from the file server 21 when the user logs in the APP at the user side 20 and the logging is abnormal.
Specifically, still include:
the first prompting module 23 is connected to the file server 21, and configured to send a first prompting message to prompt the user that the file server 21 is abnormal when the failure notice file is failed to be acquired from the file server 21;
and the second prompting module 24 is connected to the file server 21, and configured to send a second prompting message when the fault notification file is successfully acquired from the file server 21, and display the content of the fault notification file to the user.
Specifically, the service status check module 30 includes:
the access layer server 31 is connected with the user terminal 20, and is used for establishing long connection with the user terminal 20 and feeding back a heartbeat response packet to the user terminal 20 after receiving the heartbeat packet; the heartbeat response packet includes a service status therein.
The access layer server 31 is connected to the user terminal 20, and is further configured to send a fault identifier to the management background 22 when the service status is abnormal.
The access layer server 31 is connected to the user terminal 20, and is further configured to, when the service state is normal, the user terminal 20 continues to send the heartbeat packet to the access layer server 31.
An embodiment of the invention provides a computer-readable storage medium, on which a computer program 11 is stored, which computer program 11, when being executed by a processor 12, carries out all or part of the method steps of the embodiments described above.
The present invention can implement all or part of the flow in the method of the above embodiments, and can also be implemented by using a computer program 11 to instruct related hardware, where the computer program 11 can be stored in a computer-readable storage medium, and when the computer program 11 is executed by a processor 12, the steps of the above method embodiments can be implemented. The computer program 11 comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying computer program code, recording medium, U.S. disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution media, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
An embodiment of the present invention further provides a terminal device, as shown in fig. 7, which includes a memory 10 and a processor 12, the memory 10 stores a computer program 11 running on the processor 12, and the processor 12 executes the computer program 11 to implement all or part of the method steps in the first embodiment.
The Processor 12 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. The general purpose processor may be a microprocessor or the processor 12 may be any conventional processor or the like, the processor 12 being the control center for the computer device and various interfaces and lines connecting the various parts of the overall computer device.
The memory 10 may be used to store computer programs and/or modules, and the processor 12 implements various functions of the computer apparatus by running or executing the computer programs and/or modules stored in the memory 10 and invoking data stored in the memory 10. The memory 10 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, video data, etc.) created according to the use of the cellular phone, etc. Further, the memory 10 may include a high speed random access memory, and may also include a non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a flash memory Card (FlashCard), at least one magnetic disk storage device, a flash memory device, or other volatile solid state storage device.
The invention can inform the fault information to the user in time without depending on the service of the user when the server has a fault, thereby reducing the effect of a large amount of complaints on line.
It should be noted that the above embodiments can be freely combined as necessary. The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.

Claims (10)

1. A method of fault notification, comprising the steps of:
when the user successfully logs in the APP at the user side, checking the service state;
when the service state is abnormal, configuring a fault announcement file in a management background according to the fault identification, and feeding back the fault announcement file to a file server;
and when the user logs in the APP at the user side and the logging is abnormal, acquiring the fault announcement file from the file server.
2. The method of claim 1, wherein after the user logs in the APP at the user side and login abnormality occurs, the method obtains the fault notification file from the file server, and comprises the following steps:
when the failure notice file is failed to be acquired from the file server, sending first prompt information, wherein the first prompt information is used for prompting internal abnormality of the file server;
and when the fault bulletin file is successfully acquired from the file server, sending second prompt information, wherein the second prompt information is used for showing the content of the fault bulletin file to the user.
3. The method of claim 1, wherein the checking the service status specifically comprises the steps of:
the user side establishes long connection with an access layer server;
the user side sends a heartbeat packet to the access layer server;
after receiving the heartbeat packet, the access layer server feeds a heartbeat response packet back to the user side; the heartbeat response packet includes a service status therein.
4. The method of claim 3, wherein after the access stratum server receives the heartbeat packet and feeds back a heartbeat response packet to the user terminal, the method comprises the steps of:
and when the service state is abnormal, the access layer server sends a fault identifier to the management background.
5. The method of claim 3, wherein after the access stratum server receives the heartbeat packet and feeds back a heartbeat response packet to the user terminal, the method further comprises the steps of:
and when the service state is normal, the user side continuously sends the heartbeat packet to the access layer server.
6. A system for fault notification, comprising:
the user side is used for logging in the APP;
the service state checking module is connected with the user side and used for checking the service state;
the management background is connected with the file server and used for configuring a fault announcement file according to the fault identification and feeding the fault announcement file back to the file server;
and the file server is connected with the user side and used for acquiring the fault announcement file from the file server when the user logs in the APP at the user side and the logging is abnormal.
7. The system of fault notification according to claim 6, further comprising:
the first prompting module is connected with the file server and used for sending first prompting information to prompt the user that the interior of the file server is abnormal when the fault notice file is failed to be obtained from the file server;
and the second prompting module is connected with the file server and used for sending out second prompting information when the fault notice file is successfully acquired from the file server and displaying the content of the fault notice file to the user.
8. The system of claim 6, wherein the service status checking module comprises:
the access layer server is connected with the user side and used for establishing long connection with the user side and feeding back a heartbeat response packet to the user side after receiving the heartbeat packet; the heartbeat response packet includes a service status therein.
9. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method of any one of claims 1 to 5.
10. A terminal device comprising a memory and a processor, the memory having stored thereon a computer program for execution on the processor, wherein the processor, when executing the computer program, implements the method of any one of claims 1 to 5.
CN201911306112.9A 2019-12-18 2019-12-18 Method, system, storage medium and terminal device for fault announcement Pending CN111010300A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911306112.9A CN111010300A (en) 2019-12-18 2019-12-18 Method, system, storage medium and terminal device for fault announcement

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911306112.9A CN111010300A (en) 2019-12-18 2019-12-18 Method, system, storage medium and terminal device for fault announcement

Publications (1)

Publication Number Publication Date
CN111010300A true CN111010300A (en) 2020-04-14

Family

ID=70116371

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911306112.9A Pending CN111010300A (en) 2019-12-18 2019-12-18 Method, system, storage medium and terminal device for fault announcement

Country Status (1)

Country Link
CN (1) CN111010300A (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103391303A (en) * 2012-05-09 2013-11-13 腾讯科技（深圳）有限公司 Service fault noticing method and server using same
CN104734896A (en) * 2013-12-18 2015-06-24 青岛海尔空调器有限总公司 Method and system for acquiring running situations of service sub-systems
CN106034039A (en) * 2015-03-13 2016-10-19 腾讯科技（深圳）有限公司 Fault notification method and system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103391303A (en) * 2012-05-09 2013-11-13 腾讯科技（深圳）有限公司 Service fault noticing method and server using same
CN104734896A (en) * 2013-12-18 2015-06-24 青岛海尔空调器有限总公司 Method and system for acquiring running situations of service sub-systems
CN106034039A (en) * 2015-03-13 2016-10-19 腾讯科技（深圳）有限公司 Fault notification method and system

Similar Documents

Publication Publication Date Title
CN106844137B (en) Server monitoring method and device
US8467303B2 (en) Method and apparatus for preventing network conflict
CN109347934B (en) Message pushing method and system, server, storage medium and electronic device
EP2087644B1 (en) Retrieval of Performance Indicator from an Electronic Device
CN111190747A (en) Message loss detection method and device for message queue
CN111858007A (en) Task scheduling method and device based on message middleware
US20170280410A1 (en) Method, device and system for implementing information self-registration, and computer storage medium
US20060009198A1 (en) Apparatus and method for delivering messages to a mobile information terminal
CN112187903B (en) Message pushing method and device and message service system
US8340652B2 (en) System and method of waste management
CN110881055A (en) Micro-service processing method and device based on Redis
CN110809262A (en) Internet of things equipment operation and maintenance management method based on COAP protocol
CN102412983B (en) Reporting method for equipment alarm
JP6132021B2 (en) Delivery control apparatus and method, push delivery system, and computer program
CN111010300A (en) Method, system, storage medium and terminal device for fault announcement
CN106713464B (en) service management method and device of enterprise service bus
CN105262845A (en) File transmission processing method and system
CN113347035B (en) Ethernet switch configuration persistence method and device
CN114697339A (en) Load balancing method and device under centralized architecture
CN113590355A (en) Method for realizing workflow callback message and message gateway system
JP2001142810A (en) Device and method for judging terminal equipment action in directory server
CN108989467B (en) Centralized addressing method
CN102439959A (en) Communication apparatus and communication method
CN113138862A (en) Message processing method, server, device, system and storage medium
CN105306238A (en) Terminal access method, terminal access device and terminal access system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20200414