Method for issuing emergency maintenance notification of information system

Abstract

The invention discloses a method for issuing an emergency maintenance notification of an information system, and the method comprises the steps: building a user file, classifying users, and classifying the users into key users and non-key users; acquiring an online state of a user; determining a mode of notifying the user according to the user online state and the user classification; informing all online users of using the system; notices are directly pushed to offline key users through mobile phone short messages, official accounts and APPs; the method comprises the following steps of: preferentially pushing a notification message to an offline non-key user by using an official account, pushing an APP message when the official account associated information cannot be found, and notifying by using a mobile phone short message if the associated information is not found at an APP end; the notification information is pushed; according to the method, non-key users and key users can be quickly and effectively selected, the timeliness and accuracy of notification receiving of the key users need to be ensured in case of emergency, and the receiving rate of notification information of common users is further increased through the behavior of coexistence of multiple notification modes.

Description

Technical Field

[0001] The present invention relates to the technical field of notification issuance, in particular to a method for issuing an emergency maintenance notification for an information system. Background Art

[0002] In recent years, with the development of science and technology, IT information technology has been increasingly valued by enterprises and has become an indispensable and important part of modern enterprises. In some leading enterprises, the innovative application capabilities of IT information technology have become their core competitiveness. Whether it is personnel management, planned production, internal and external sales, logistics and transportation, administrative management and other aspects of business, they all rely on the stable operation of information systems.

[0003] Currently, large enterprises categorize their information systems according to their importance to facilitate risk assessment. These categorizations are typically divided into five levels: core systems, critical systems, important systems, auxiliary systems, and general systems. Core systems are key assets that ensure the normal operation of the enterprise, and their maintenance is a top priority for the enterprise's IT department. Routine maintenance typically involves periodic inspections and feature updates, planned from the outset of the system's launch. These are typically scheduled after get off work, at night, or during idle business hours. System users are aware of these maintenance tasks, or are notified of them via system notifications some time in advance. Emergency maintenance typically involves unexpected situations, such as hardware or network failures, feature update errors, and other serious issues that require immediate attention from operations personnel. These issues are unpredictable and cannot be notified in advance.

[0004] Once emergency maintenance is required, the IT department needs to promptly notify system users to avoid abnormal business operations and loss of business data caused by system maintenance. The existing system makes it difficult to promptly and accurately notify system users during emergency maintenance. In particular, key users of the system are an important part of the IT department's information system risk management.

[0005] Therefore, in order to solve the above problems, a method for issuing emergency maintenance notice of information system is proposed. Summary of the Invention

[0006] In order to make up for the deficiencies of the prior art and solve the problem of emergency information, the present invention proposes a method for issuing emergency maintenance notifications for an information system.

[0007] A method for issuing an emergency maintenance notice for an information system, comprising the following steps:

[0008] S1: Create user profiles and classify users into key users and non-key users;

[0009] S2: Get the user's online status;

[0010] S3: Determine the method of notifying the user based on the user's online status and user classification;

[0011] Use system notifications for all online users;

[0012] Push notifications directly to key users who are offline via SMS, official accounts, and APPs;

[0013] For non-critical users who are offline, push notifications to the official account first. If no relevant information about the official account can be found, push notifications to the app. If no relevant information is found on the app, SMS notifications will be used.

[0014] S4: Notification information push.

[0015] Preferably, the method for establishing a user profile is:

[0016] Collect user's mobile phone number, user rank, key business position and usage frequency;

[0017] The user classification includes weighting the user's job level S1, key business position S2, and usage frequency S3, and subdividing each item.

[0018] Preferably, the scoring criteria for the user's job level S1 segmentation are: company senior management: S1 = 50; middle-level cadres: S1 = 30; grassroots backbones: S1 = 20; ordinary employees: S1 = 10;

[0019] The scoring criteria for user key business positions S2 are: Senior technicians: S2 = 50; Intermediate technicians: S2 = 30; Junior technicians: S2 = 20; Intern technicians: S2 = 10;

[0020] The scoring criteria for usage frequency S3 are as follows: obtain the user's daily login frequency a and daily button click frequency b, where a is the ratio of the number of logins on the day A to the daily average number of logins C, and b is the ratio of the number of operation button clicks B to the daily average number of operation button clicks D;

[0021] First calculate the daily login frequency a = A / C and the daily button click frequency b = B / D;

[0022] Then a simple linear weighting method is used to combine these two frequency indicators to determine the frequency score.

[0023] S3=K1*a+K2*b

[0024] Among them, K1 and K2 are pre-set coefficients used to adjust the impact of login frequency and button click frequency on the final score, and satisfy K1+K2=1;

[0025] The weight of user rank is W1, the weight of key business position is W2, and the weight of usage frequency is W3, and W1+W2+W3=1.

[0026] Final weighted score S = W1*S1+W2*S2+W3*S3;

[0027] Set a weight critical value S4. Users with S greater than or equal to S4 are key users, and users with S less than S4 are non-key users.

[0028] Preferably, the method for determining the online status of a user is as follows: after the user successfully logs into the system, the front-end and back-end establish a connection according to the websocket two-way communication protocol, the front-end sends a message to the back-end at fixed intervals, and after receiving the message, the back-end responds with a message to the front-end within a fixed time. When the back-end service receives the message from the front-end within the fixed time, it can be determined that the current user's status is online;

[0029] When the backend service does not receive a message from the frontend within a fixed time, it can be determined that the current user's status is offline and marked as offline in the memory database. User status information is generally maintained in memory or an in-memory database and synchronized from the memory or in-memory database to the relational database at regular intervals.

[0030] Preferably, the method of determining to notify the user includes collecting the user's mobile phone number from the user profile, and the system login function is designed so that users determined by the system as key users need to enter a mobile phone verification code at regular intervals to update the changed user's mobile phone number.

[0031] Preferably, the method of determining the notification user also includes establishing a public account for message notification, guiding system users to follow the public account, collecting the openid of the system user associated with the public account, collecting the installation and usage information of mobile APP applications within the enterprise, and obtaining APP-side message push interface information.

[0032] Preferably, the method for pushing notification information includes: notifying online users and offline users, as well as key users and non-key users respectively in multiple ways according to whether the users are online and user classification;

[0033] Push system messages to online users. For users who have not interacted with system messages within a certain period of time, public account push notifications will be prioritized. If no public account related information is found, APP message push will be used. If no related information is found on the APP side, SMS notification will be used.

[0034] For offline non-critical users, push notifications to the official account first. If no relevant information about the official account can be found, push notifications to the app. If no relevant information is found on the app, SMS notifications will be used.

[0035] For key users who are not online, SMS, public accounts, and APP push are carried out simultaneously.

[0036] Preferably, the notification message push includes establishing a public service system for message push, providing a unified API interface to the outside world, and setting parameters: message type and template id, which are used to fill in the template data, and executing specific message push according to the different parameters passed in.

[0037] The present invention is beneficial in that:

[0038] 1. The present invention can quickly and effectively select general users and key users by setting weights for three major items: user rank, key business position, and frequency of use. In the event of an emergency, since the emergency has a greater impact on key users, it is necessary to ensure that key users receive notifications in a timely and accurate manner. In addition, the coexistence of multiple notification methods further increases the reception rate of notification information for ordinary users.

[0039] 2. The present invention first determines whether the user is online, so that the system can push notifications to the user in different ways later. When sending notifications, for general system users, WeChat official accounts are given priority to push notification messages. When no official account related information is found, APP message push is performed. APP message push lags behind official account, and message sending is not very reliable. If the APP side also does not find related information, mobile phone text message notification is used. Official account>APP>SMS, which is economical and affordable. For key system users, mobile phone text message + official account + APP are used to push messages at the same time to ensure that key users can receive messages quickly and accurately.

[0040] 3. The present invention classifies users and distinguishes and compares traditional single SMS notifications and public account message pushes. This method uses certain logical processing and comprehensive consideration of multiple message types in the message push method, which has a higher success rate in pushing notification information to key users. The technical difficulty of implementing this method is not high. Most information systems can fully implement this method after certain modifications, which significantly reduces the information system operation and maintenance pressure of the enterprise IT department, and can largely guarantee the accuracy of user business operations, the integrity and consistency of business data; it reduces the operational risks of the business system, and greatly improves the friendliness of the application system and the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0042] Figure 1 A flowchart of key user screening according to an embodiment of the present invention;

[0043] Figure 2 A breakdown graph is configured for key user screening rating items in one embodiment of the present invention;

[0044] Figure 3 A flow chart of contact channel collection according to an embodiment of the present invention;

[0045] Figure 4 Establish a flow chart for a notification strategy for one embodiment of the present invention;

[0046] Figure 5 This is a notification message push flow chart of an embodiment of the present invention;

[0047] Figure 6 A flowchart of changing a user's mobile phone number according to an embodiment of the present invention;

[0048] Figure 7 The figure is an overall flow chart of an embodiment of the present invention. DETAILED DESCRIPTION

[0049] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making any creative efforts shall fall within the scope of protection of the present invention.

[0050] See also Figures 1 to 7 As shown, a method for issuing an emergency maintenance notice for an information system includes the following steps:

[0051] S1: Create user profiles and classify users into key users and non-key users;

[0052] S2: Get the user's online status;

[0053] S3: Determine the method of notifying the user based on the user's online status and user classification;

[0054] Use system notifications for all online users;

[0055] Push notifications directly to key users who are offline via SMS, official accounts, and APPs;

[0056] For non-critical users who are offline, push notifications to the official account first. If no relevant information about the official account can be found, push notifications to the app. If no relevant information is found on the app, SMS notifications will be used.

[0057] S4: Notification information push.

[0058] Furthermore, the method for establishing a user profile is:

[0059] Collect user's mobile phone number, user rank, key business position and usage frequency;

[0060] The user classification includes weighting the user's job level S1, key business position S2, and usage frequency S3, and subdividing each item.

[0061] Furthermore, the user's job level S1 is divided into the following scoring criteria: senior management: S1 = 50; middle management: S1 = 30; grass-roots backbone: S1 = 20; ordinary employees: S1 = 10;

[0062] The scoring criteria for user key business positions S2 are: Senior technicians: S2 = 50; Intermediate technicians: S2 = 30; Junior technicians: S2 = 20; Intern technicians: S2 = 10;

[0063] The scoring criteria for usage frequency S3 are as follows: obtain the user's daily login frequency a and daily button click frequency b, where a is the ratio of the number of logins on the day A to the daily average number of logins C, and b is the ratio of the number of operation button clicks B to the daily average number of operation button clicks D;

[0064] First calculate the daily login frequency a = A / C and the daily button click frequency b = B / D;

[0065] Then a simple linear weighting method is used to combine these two frequency indicators to determine the frequency score.

[0066] S3=K1*a+K2*b

[0067] Among them, K1 and K2 are pre-set coefficients used to adjust the impact of login frequency and button click frequency on the final score, and satisfy K1+K2=1;

[0068] The weight of user rank is W1, the weight of key business position is W2, and the weight of usage frequency is W3, and W1+W2+W3=1.

[0069] Final weighted score S = W1*S1+W2*S2+W3*S3;

[0070] Set a weight critical value S4. Users with S greater than or equal to S4 are key users, and users with S less than S4 are non-key users.

[0071] Furthermore, the method for determining the user's online status is as follows: after the user successfully logs into the system, the front-end and back-end establish a connection according to the websocket two-way communication protocol. The front-end sends a message to the back-end at a fixed interval. After receiving the message, the back-end responds to the front-end with a message within a fixed time. When the back-end service receives the message from the front-end within the fixed time, it can be determined that the current user's status is online.

[0072] When the backend service does not receive a message from the frontend within a fixed time, it can be determined that the current user's status is offline and marked as offline in the memory database. User status information is generally maintained in memory or an in-memory database and synchronized from the memory or in-memory database to the relational database at regular intervals.

[0073] Furthermore, the method of determining the notification user includes collecting the user's mobile phone number from the user file, and the system login function is designed so that users determined by the system as key users need to enter a mobile phone verification code at regular intervals to update the changed user's mobile phone number.

[0074] Furthermore, the method of determining the notification user also includes establishing a public account for message notification, guiding system users to follow the public account, collecting the openid of the system user associated with the public account, collecting the installation and usage information of mobile APP applications within the enterprise, and obtaining APP-side message push interface information.

[0075] Furthermore, the method for pushing notification information includes: notifying online users and offline users, as well as key users and non-key users in multiple ways according to whether the users are online and user categories;

[0076] Push system messages to online users. For users who have not interacted with system messages within a certain period of time, public account push notifications will be prioritized. If no public account related information is found, APP message push will be used. If no related information is found on the APP side, SMS notification will be used.

[0077] For offline non-critical users, push notifications to the official account first. If no relevant information about the official account can be found, push notifications to the app. If no relevant information is found on the app, SMS notifications will be used.

[0078] For key users who are not online, SMS, public accounts, and APP push are carried out simultaneously.

[0079] Furthermore, the notification message push includes establishing a public service system for message push, providing a unified API interface to the outside world, and setting parameters: message type and template id, which are used to fill in the template data, and executing specific message push according to the different parameters passed in.

[0080] Working principle: First, create two tables in the database: a scoring item configuration table and a weight grading table. The scoring item configuration table sets the name and score of the scoring item, and the sum of all item scores equals 100; the weight grading table sets the specific score for each item. The score of each record in the grading table cannot exceed the score of the item in the configuration. Finally, the weight critical value is compared to screen out key users and non-key users.

[0081] The user's online status, user mobile phone number, public account openid, and app device identification are collected separately, and websocket is used to manage the user's online status. After the user successfully logs into the system, a long connection is established between the front-end and the back-end. The front-end sends a message to the back-end every few seconds. After receiving the message, the back-end stores the information in redis, sets an expiration time for the current KEY, and continuously updates the expiration time of the KEY. The user's mobile phone number is obtained from the user information. In order to ensure that the changes in the mobile phone numbers of key users can be updated in the system in a timely manner as much as possible, the system login is set to multi-factor identity authentication, which consists of a username, password and SMS verification code. In general, the username and password are used for login verification. During the login verification process, it is judged whether the user is a key user. The login request determined to be a key user is compared with the current time based on the time of the last verification using the SMS verification code to determine whether the current login requires a second verification using the SMS verification code. This is a good way to update the mobile phone number of key users.

[0082] The public account openid and app device identifier are stored in the user information and are obtained directly from the user information. To obtain the public account openid, you need to first create a WeChat public account, develop the binding function, guide system users to follow the public account, and perform identity binding operations. The background service load of this operation will store the openid in the corresponding user information. To obtain the app device identifier, you need to have an APP that can push system messages. You need to create a developer account in the developer center of a mainstream mobile phone brand, submit information, and perform authentication. When logging into the APP, you need to obtain the current device identifier and store it in the corresponding user information.

[0083] First determine whether the user is online. If the user is online, directly push the system message to the user and pop up a notification box. If you do not click the confirmation button, you cannot perform any subsequent operations. The system sets a very short time, such as 10 seconds, to confirm that the user information of the operation is in redis. 15 seconds after the message is sent, immediately perform subsequent operations and check the users in redis. If there are users not in redis, start other message reminder operations.

[0084] Determine the user type. For general system users, WeChat Official Account push notifications are prioritized. If no relevant information can be found on the Official Account, app push notifications are used. App push notifications lag behind Official Account push notifications and are less reliable. If the App also fails to find relevant information, SMS notifications are used. The formula is: Official Account > App > SMS. For users identified by the system as critical system users, SMS, Official Account, and App push notifications are used simultaneously.

[0085] In business system design, try to extract complex and reusable logic into independent services with high cohesion and low coupling. Such a design will be much easier for future adjustments and maintenance.

[0086] The main message push program starts to execute. After certain logical processing, the users who need to be notified are obtained, and the users who have performed notification message interaction operations within the system are removed. The user information is sent to the notification policy service. The policy service calls the user type judgment service and returns to the main program. The main program continues to call the public message push service, and the message push is completed.

[0087] Build a public message push service that provides a unified calling API and triggers different message pushes by sending different parameters.

[0088] The parameters of the API to be called can be set as follows:

[0089] typeMessage type

[0090] template_id template id

[0091] data contains the data used to populate the variables in the template.

[0092] Throughout this specification, references to terms such as "one embodiment," "example," or "specific example" indicate that the specific features, structures, materials, or characteristics described in conjunction with that embodiment or example are included in at least one embodiment or example of the present invention. In this specification, schematic representations of these terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

[0093] The basic principles, main features, and advantages of the present invention are shown and described above. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The above embodiments and descriptions are merely illustrative of the principles of the present invention. Various changes and modifications may be made to the present invention without departing from the spirit and scope of the present invention, and such changes and modifications fall within the scope of the invention as claimed.

Claims

1. A method for issuing an emergency maintenance notice for an information system, characterized by: The following steps are involved: S1: Create user profiles and classify users into key users and non-key users; S2: Get the user's online status; S3: Determine the method of notifying the user based on the user's online status and user classification; Use system notifications for all online users; Push notifications directly to key users who are offline via SMS, official accounts, and APPs; For non-critical users who are offline, push notifications to the official account first. If no relevant information about the official account can be found, push notifications to the app. If no relevant information is found on the app, SMS notifications will be used. S4: Notification information push.

2. The method for issuing an emergency maintenance notice for an information system according to claim 1, characterized in that: The method for establishing a user profile is: Collect user's mobile phone number, user rank, key business position and usage frequency; The user classification includes weighting the user's job level S1, key business position S2, and usage frequency S3, and subdividing each item.

3. The method for issuing an emergency maintenance notice for an information system according to claim 2, characterized in that: The scoring criteria for the user's job level S1 segmentation are: company senior management: S1 = 50; middle-level cadres: S1 = 30; grassroots backbones: S1 = 20; ordinary employees: S1 = 10; The scoring criteria for user key business positions S2 are: Senior technical personnel: S2 = 50; Intermediate technical personnel: S2=30; Junior technicians: S2=20; Trainee technicians: S2=10; The scoring criteria for usage frequency S3 are as follows: obtain the user's daily login frequency a and daily button click frequency b, where a is the ratio of the number of logins on the day A to the daily average number of logins C, and b is the ratio of the number of operation button clicks B to the daily average number of operation button clicks D; First calculate the daily login frequency a = A / C and the daily button click frequency b = B / D; Then a simple linear weighting method is used to combine these two frequency indicators to determine the frequency score. S3=K1*a+K2*b Among them, K1 and K2 are pre-set coefficients used to adjust the impact of login frequency and button click frequency on the final score, and satisfy K1+K2=1; The weight of user rank is W1, the weight of key business position is W2, and the weight of usage frequency is W3, and W1+W2+W3=1. Final weighted score S = W1*S1+W2*S2+W3*S3; Set a weight critical value S4. Users with S greater than or equal to S4 are key users, and users with S less than S4 are non-key users.

4. The method for issuing an emergency maintenance notice for an information system according to claim 1, wherein: The method for determining the user's online status is as follows: after the user successfully logs in to the system, the front-end and back-end establish a connection according to the websocket two-way communication protocol. The front-end sends a message to the back-end at a fixed interval. After receiving the message, the back-end responds to the front-end within a fixed time. When the back-end service receives the message from the front-end within the fixed time, it can be determined that the current user's status is online; When the backend service does not receive a message from the frontend within a fixed time, it can be determined that the current user's status is offline and marked as offline in the memory database. User status information is generally maintained in memory or an in-memory database and synchronized from the memory or in-memory database to the relational database at regular intervals.

5. The method for issuing an emergency maintenance notice for an information system according to claim 1, characterized in that: The method of determining and notifying users includes collecting user mobile phone numbers from user files. The system login function is designed so that users determined by the system as key users need to enter mobile phone verification codes at regular intervals to update the changed user mobile phone numbers.

6. The method for issuing an emergency maintenance notice for an information system according to claim 5, characterized in that: The method of determining the notified user also includes establishing a public account for message notification, guiding system users to follow the public account, collecting the openids of system users associated with the public account, collecting installation and usage information of mobile APP applications within the enterprise, and obtaining APP-side message push interface information.

7. The method for issuing an emergency maintenance notice for an information system according to claim 1, characterized in that: The method for pushing notification information includes: notifying online users and offline users, as well as key users and non-key users in multiple ways according to whether the users are online and the user classification; Push system messages to online users. For users who have not interacted with system messages within a certain period of time, public account push notifications will be prioritized. If no public account related information is found, APP message push will be used. If no related information is found on the APP side, SMS notification will be used. For offline non-critical users, push notifications to the official account first. If no relevant information about the official account can be found, push notifications to the app. If no relevant information is found on the app, SMS notifications will be used. For key users who are not online, SMS, public accounts, and APP push are carried out simultaneously.

8. The method for issuing an emergency maintenance notice for an information system according to claim 7, characterized in that: The notification message push includes establishing a public service system for message push, providing a unified API interface to the outside world, and setting parameters: message type and template id, which are used to fill in the template data, and executing specific message push according to the different parameters passed in.

Images