Mail early warning system based on cloud platform

Abstract

The early warning method of the mail early warning system based on the cloud platform comprises the following steps: (1) designing a database table structure; (2) reporting an early warning process by a receiving terminal: when equipment fails, the terminal senses and pushes a message to mqtt, a background monitors a topic corresponding to the mqtt, and receives the early warning message; an early warning entity object is generated and stored in a table; a message is notified to a front end through mqtt, and an early warning pop-up window prompt function is performed; and (3) a mail pushing and early warning process: obtaining an early warning strategy of the current tenant, judging whether pushing is needed or not, obtaining groups needing mail early warning, obtaining early warning members and mailbox addresses, sending a mail through JavaMailSensor, obtaining an execution result, and returning the execution result to a front end. According to the invention, the early warning information of the cloud platform equipment is timely and rapidly sent to each operator and is copied to related leaders, so that recipients can carry out corresponding processing on the equipment according to actual conditions.

Description

Technical Field

[0001] The present invention relates to the technical field of cloud platform systems, and in particular to an email early warning system based on a cloud platform. Background Art

[0002] With the rapid development of cloud computing technology, cloud platforms are increasingly being used in various fields. Pingmei Anbo Cloud System is a product that focuses on content playback security and equipment operation security. Through this platform, users can safely and compliantly play public information, government and enterprise propaganda, commercial advertisements, emergency broadcasts and other content on the big screen, and remotely monitor the operating status of large-screen devices. In addition, the platform also has functions such as content publishing, equipment management, equipment control, large-screen playback video acquisition, AI machine review and program visualization production, which can fully meet users' needs for large-screen content operation and equipment operation and maintenance.

[0003] With the widespread application of Pingmei Ando Cloud System, more and more devices are connected to the system, so there is an urgent need for an email warning system, that is, the email warning system of Pingmei Ando Cloud Platform. Summary of the invention

[0004] In order to make up for the deficiencies of the prior art, the present invention provides an email warning system based on a cloud platform which is timely in response and easy to use.

[0005] The present invention is achieved through the following technical solutions: An early warning method for an email early warning system based on a cloud platform, characterized in that it includes the following steps: (1) Database table structure design: (2) Process of receiving terminal reporting warning: Start receiving warning process → Equipment failure, terminal perception and push message to MQTT → Background monitoring of MQTT corresponding topic, receive warning message → Parse and query database data, generate warning entity object and save it to the table → Notify the message to the front end through MQTT, and make warning pop-up prompt → End of receiving warning process; (3) Email push warning process: Start the email push warning process → Get the current tenant warning strategy and determine whether it needs to be pushed → Get the group that needs email warning → Get the warning members and email addresses → Send emails through JavaMailSender → Get the execution results and return them to the front end → The email push warning process ends.

[0006] (1) Database table structure design: The database tables include the following: Device warning message table, device_error_record: requires primary key id, exception type, processing method, processing status, whether there is a warning picture, picture suffix, message id, exception message, exception occurrence time, message generation time, background notification warning status, whether to send email notification, number of email notifications, tenant, and logical deletion fields.

[0007] The device warning address table, device_error_alarm_addressees, is used to record the email address to which a warning message is pushed: it contains the primary key id, device_error_record_id (device_error_record associated id), push type, and push address fields.

[0008] The main table of mail groups is used to manage each group information, smsb_message_group: contains fields such as primary key id, message group name, notification level received by the message group, notification enumeration class received by the message group, message group status, creator, creation time, update time, tenant, etc.

[0009] The mail group member table is used to save the member information of each group in the mail group main table. smsb_message_group_member: contains the primary key id, group id, user type, Ando Cloud user id, user enable / disable status, user name, user mobile number, user email address, primary / copy type, creator, creation time, update time and other fields.

[0010] Tenant warning notification strategy table. Different tenants may have different warning notification strategies. Therefore, to isolate the notification strategies of each tenant according to the tenant, the tenant_exception_inform_strategy table is required: including the tenant, whether to enable the prompt level warning notification, whether to enable the intermediate level warning notification, whether to enable the emergency level warning notification, whether to enable the SMS warning, whether to enable the email warning and other fields.

[0011] (2) Process of receiving terminal reporting warning: The details are as follows: When the terminal senses a device failure, it will send a message to the background through MQTT. MQTT is a lightweight message transmission protocol that occupies less bandwidth and can ensure the quality of message transmission when the network is unstable. The background only needs to subscribe to the corresponding topic of the corresponding channel of MQTT to receive the message of device failure. After receiving the warning message, the background needs to parse the message, obtain valid data, query the device table of the database, obtain other data of the device, fill in the entity object information of device_error_record and save it to the table. At this time, the background will display the warning message on the front page through the pop-up window prompt on the web page through MQTT.

[0012] (3) Email push warning process: Details are as follows: (3-1) When the backend receives an early warning, it first goes to the tenant_exception_inform_strategy table to obtain the early warning strategy of the tenant according to the current tenant. Specifically, the early warning level is divided into three levels: prompt early warning, intermediate early warning, and emergency early warning. Each early warning level can be configured to enable SMS and email early warnings, which can be configured on the front end. Obviously, the backend needs to determine whether the early warning needs to be pushed by email based on the early warning strategy.

[0013] (3-2) If email push is required, the backend needs to obtain the members who need to receive emails based on the smsb_message_group table. Specifically, the email user master table will record the warning level and warning enumeration class received by the group, which can be configured on the front end. That is to say, users can choose which level of warning the members under this group receive, or customize them so that these members only receive certain specific warnings, such as the broadcast controller going online, the broadcast controller going offline, etc. Since each warning has its own warning level, the groups that need to be pushed by email can be filtered out based on the information in the smsb_message_group table. At this time, the smsb_message_group_member table is associated to obtain the members under each group, and all the member information that needs to be notified by the warning message can be obtained. Note that deduplication should be performed here because a member can appear in different groups. In addition, since the user information of the Pingmei Anbo Cloud Platform is stored in keycloak, it is also necessary to access keycloak to obtain the member's email address.

[0014] (3-3) Email push is implemented through JavaMailSender, which is an interface for sending emails in the Spring framework. It is based on the JavaMail API and provides a convenient email sending function. JavaMailSender can configure and use the SMTP server to send emails, supporting multiple email types such as text, HTML content, and attachments. When using it, you only need to configure the email content, email title, sender, recipient, and CC to push the email. When the push is successful, you need to add the corresponding email address to the device_error_alarm_addressees table for recording, and call back the email push result for the front-end display. The user can intuitively see whether this warning email is sent successfully and the email address that received the email on the front-end interface.

[0015] The beneficial effect of the present invention is that the cloud platform-based email warning system is used to send the warning information of the equipment (such as equipment online failure, equipment offline, etc.) to each operating personnel in a timely and rapid manner, and copy it to the relevant leaders so that the recipient can handle the equipment accordingly according to the actual situation. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 This is a schematic diagram of the process of receiving early warnings of the present invention, Figure 2 This is a schematic diagram of the email push warning process of the present invention. DETAILED DESCRIPTION

[0017] The accompanying drawings show a specific embodiment of the present invention.

[0018] The early warning method of the email early warning system based on the cloud platform of the present invention comprises the following steps: (1) Database table structure design: (2) Process of receiving terminal reporting warning: Start receiving warning process → Equipment failure, terminal perception and push message to MQTT → Background monitoring of MQTT corresponding topic, receive warning message → Parse and query database data, generate warning entity object and save it to the table → Notify the message to the front end through MQTT, and make warning pop-up prompt → End of receiving warning process; (3) Email push warning process: Start the email push warning process → Get the current tenant warning strategy and determine whether it needs to be pushed → Get the group that needs email warning → Get the warning members and email addresses → Send emails through JavaMailSender → Get the execution results and return them to the front end → The email push warning process ends.

[0019] The detailed steps are as follows: The following three points need to be completed to implement the email warning function of the cloud platform: (1) Database table structure design: The database tables include the following: Device warning message table, device_error_record: requires primary key id, exception type, processing method, processing status, whether there is a warning picture, picture suffix, message id, exception message, exception occurrence time, message generation time, background notification warning status, whether to send email notification, number of email notifications, tenant, and logical deletion fields.

[0020] The device warning address table, device_error_alarm_addressees, is used to record the email address to which a warning message is pushed: it contains the primary key id, device_error_record_id (device_error_record associated id), push type, and push address fields.

[0021] The main table of mail groups is used to manage each group information, smsb_message_group: contains fields such as primary key id, message group name, notification level received by the message group, notification enumeration class received by the message group, message group status, creator, creation time, update time, tenant, etc.

[0022] The mail group member table is used to save the member information of each group in the mail group main table. smsb_message_group_member: contains the primary key id, group id, user type, Ando Cloud user id, user enable / disable status, user name, user mobile number, user email address, primary / copy type, creator, creation time, update time and other fields.

[0023] Tenant warning notification strategy table. Different tenants may have different warning notification strategies. Therefore, to isolate the notification strategies of each tenant according to the tenant, the tenant_exception_inform_strategy table is required: including the tenant, whether to enable the prompt level warning notification, whether to enable the intermediate level warning notification, whether to enable the emergency level warning notification, whether to enable the SMS warning, whether to enable the email warning and other fields.

[0024] (2) Process of receiving terminal reporting warning: Start receiving warning process → Equipment failure, terminal perception and push message to MQTT → Background monitoring of MQTT corresponding topic, receive warning message → Parse and query database data, generate warning entity object and save it to the table → Notify the message to the front end through MQTT, and make warning pop-up prompt → End of receiving warning process; The detailed process of receiving warnings is as follows. When the terminal senses a device failure, it will send a message to the background through MQTT. MQTT is a lightweight message transmission protocol that occupies less bandwidth and can ensure the quality of message transmission when the network is unstable. The background only needs to subscribe to the corresponding topic of the corresponding channel of MQTT to receive the message of device failure. After receiving the warning message, the background needs to parse the message, obtain valid data, query the device table of the database, obtain other data of the device, fill in the entity object information of device_error_record and save it to the table. At this time, the background will display the warning message on the front page through the pop-up window prompt of the web page through MQTT.

[0025] (3) Email push warning process: Start the email push warning process → Get the current tenant warning strategy and determine whether it needs to be pushed → Get the group that needs email warning → Get the warning members and email addresses → Send emails through JavaMailSender → Get the execution results and return them to the front end → The email push warning process ends.

[0026] Details are as follows: (3-1) When the backend receives an early warning, it first goes to the tenant_exception_inform_strategy table to obtain the early warning strategy of the tenant according to the current tenant. Specifically, the early warning level is divided into three levels: prompt early warning, intermediate early warning, and emergency early warning. Each early warning level can be configured to enable SMS and email early warnings, which can be configured on the front end. Obviously, the backend needs to determine whether the early warning needs to be pushed by email based on the early warning strategy.

[0027] (3-2) If email push is required, the backend needs to obtain the members who need to receive emails based on the smsb_message_group table. Specifically, the email user master table will record the warning level and warning enumeration class received by the group, which can be configured on the front end. That is to say, users can choose which level of warning the members under this group receive, or customize them so that these members only receive certain specific warnings, such as the broadcast controller going online, the broadcast controller going offline, etc. Since each warning has its own warning level, the groups that need to be pushed by email can be filtered out based on the information in the smsb_message_group table. At this time, the smsb_message_group_member table is associated to obtain the members under each group, and all the member information that needs to be notified by the warning message can be obtained. Note that deduplication should be performed here because a member can appear in different groups. In addition, since the user information of the Pingmei Anbo Cloud Platform is stored in keycloak, it is also necessary to access keycloak to obtain the member's email address.

[0028] (3-3) Email push is implemented through JavaMailSender, which is an interface for sending emails in the Spring framework. It is based on the JavaMail API and provides a convenient email sending function. JavaMailSender can configure and use the SMTP server to send emails, supporting multiple email types such as text, HTML content, and attachments. When using it, you only need to configure the email content, email title, sender, recipient, and CC to push the email. When the push is successful, you need to add the corresponding email address to the device_error_alarm_addressees table for recording, and call back the email push result for the front-end display. The user can intuitively see whether this warning email is sent successfully and the email address that received the email on the front-end interface.

[0029] The devices in the cloud platform usually refer to the screens used to play content. Common warnings include: the broadcast controller is offline, the broadcast controller is online, the screen content is not compliant, the receiving card is offline, there is a gap in the schedule, the broadcast controller is offline during the working period, the temperature sensor alarm, the broadcast controller network fluctuation, and the standby warning.

[0030] The Pingmei Ando Cloud Platform consists of the front-end, back-end and terminal. The front-end mainly provides the management interface of the platform, including device details, merchant information and contract information. The back-end is developed in Java language, and uses middleware such as MinIO, Redis, MySQL and RabbitMQ to realize the interconnection of functional modules. MinIO is an open source object storage server for resource storage; Redis is an open source memory data structure storage, used as a middleware for caching data; MySQL is an open source relational database management system for data storage; RabbitMQ is an open source message broker software. The terminal device is a large-screen device, which is responsible for content presentation and reporting data to the back-end, while the back-end is responsible for processing and managing this data.

[0031] MQTT (Message Queue Telemetry Transport) is a message protocol based on the publish / subscribe paradigm under the ISO standard (ISO / IEC PRF 20922). It works on the TCP / IP protocol family and is a publish / subscribe messaging protocol designed for remote devices with low hardware performance and poor network conditions. MQTT is a client-server based message publish / subscribe transport protocol.

Claims

1. An early warning method for an email early warning system based on a cloud platform, characterized in that: The following steps are involved: (1) Database table structure design: (2) Process of receiving terminal reporting warning: Start receiving warning process → Equipment failure, terminal perception and push message to MQTT → Background monitoring of MQTT corresponding topic, receive warning message → Parse and query database data, generate warning entity object and save it to the table → Notify the message to the front end through MQTT, and make warning pop-up prompt → End of receiving warning process; (3) Email push warning process: Start the email push warning process → Get the current tenant warning strategy and determine whether it needs to be pushed → Get the group that needs email warning → Get the warning members and email addresses → Send emails through JavaMailSender → Get the execution results and return them to the front end → The email push warning process ends.

2. The cloud platform-based email warning system according to claim 1, characterized in that: In step (1), the database table includes the following parts: Device warning message table, device_error_record: needs to have primary key id, exception type, processing method, processing status, whether there is a warning picture, picture suffix, message id, exception message, exception occurrence time, message generation time, background notification warning status, whether to send email notification, number of email notifications, tenant, logical deletion field; Device alarm address table, device_error_alarm_addressees, is used to record the email address of a certain alarm information push: including primary key id, device_error_record_id (device_error_record associated id), push type, and push address fields; The main table of mail grouping is used to manage each group information, smsb_message_group: contains fields such as primary key id, message group name, notification level received by the message group, notification enumeration class received by the message group, message group status, creator, creation time, update time, tenant, etc. The mail group member table is used to save the member information of each group in the mail group main table. smsb_message_group_member: contains fields such as primary key id, group id, user type, Ando Cloud user id, user enable / disable status, user name, user mobile number, user email address, primary / copy type, creator, creation time, and update time. Tenant warning notification strategy table. Different tenants may have different warning notification strategies. Therefore, to isolate the notification strategies of each tenant according to the tenant, the tenant_exception_inform_strategy table is required: including the tenant, whether to enable the prompt level warning notification, whether to enable the intermediate level warning notification, whether to enable the emergency level warning notification, whether to enable the SMS warning, whether to enable the email warning and other fields.

3. The cloud platform-based email warning system according to claim 2 is characterized in that: The detailed steps of step (2) are as follows: When the terminal senses a device failure, it will send a message to the background through MQTT. MQTT is a lightweight message transmission protocol that occupies less bandwidth and can ensure the quality of message transmission when the network is unstable. The background only needs to subscribe to the corresponding topic of the corresponding channel of MQTT to receive the message of device failure; after receiving the warning message, the background needs to parse the message, obtain valid data, query the device table in the database, obtain other data of the device, fill in the entity object information of device_error_record and save it to the table. At this time, the background will use MQTT to display the warning message on the front-end page through a pop-up window prompt on the web page.

4. The cloud platform-based email warning system according to claim 2, characterized in that: The detailed steps of step (3) are as follows: (3-1) When the backend receives an early warning, it first goes to the tenant_exception_inform_strategy table to obtain the early warning strategy of the tenant according to the current tenant. The early warning level is divided into three levels: prompt early warning, intermediate early warning, and emergency early warning; Each warning level can be configured to enable SMS or email warnings, which can be configured on the front end; the back end needs to determine whether the warning needs to be pushed by email based on the warning strategy; (3-2) If email push is required, the backend needs to obtain the members who need to receive emails according to the smsb_message_group table. Specifically, the email user master table will record the warning level and warning enumeration class received by the group. These can be configured on the front end, that is, the user can choose which level of warning the members under this group receive, and can also customize them so that these members only receive certain specific warnings, including the broadcast controller going online and the broadcast controller going offline. Since each warning has its own warning level, the group that needs to be pushed by email can be filtered out according to the information in the smsb_message_group table. At this time, the smsb_message_group_member table is associated to obtain the members under each group. All member information that needs to be notified by the warning message can be obtained, and deduplication should be performed here because a member can appear in different groups. In addition, since the user information of the Pingmei Anbo Cloud Platform is stored in keycloak, it is also necessary to access keycloak to obtain the member's email address. (3-3) Email push is implemented through JavaMailSender. JavaMailSender is an interface for sending emails in the Spring framework. It is based on the JavaMail API and provides a convenient email sending function. JavaMailSender can configure and use the SMTP server to send emails. It supports multiple email types such as text, HTML content, and attachments. When using it, you only need to configure the email content, email title, sender, recipient, and CC to push the email. When the push is successful, you need to add the corresponding email address to the device_error_alarm_addressees table for record, and call back the email push result for front-end display. Users can then intuitively see whether this warning email is sent successfully and the email address that received the email on the front-end interface.

Images