An event push method and system based on device health code

Abstract

The present invention discloses an event push method and system based on a device health code, aiming to solve the problem that the current event status of a device is long and results in low operation and maintenance efficiency. The method includes: establishing a device trigger event library according to device historical data and event criticality, and establishing a mapping relationship between device trigger events and health code color change events; and obtaining device trigger information and health code color information; subsequently generating a first health code image after preprocessing, and transmitting the first health code image to a server to form a second health code image; the user end obtains and scans the second health code image of the server end, obtains the first health code image through a primary verification, obtains the original health code image through a secondary verification, and obtains the event status of the device from the original health code image; a system is also proposed; combining the device health code to realize rapid event push, reduce the verification time of the device event status, and improve operation and maintenance efficiency.

Description

Technical Field

[0001] The present invention relates to the technical field of device event push technology, and in particular to a device health code-based event push method and system. Background Art

[0002] The number, types, and complexity of power equipment are increasing day by day. Lean arrangement of operation and maintenance has become a top priority. Faced with different power equipment, manual inspections or manual retrieval of equipment information are often required. After the retrieval is completed, the current status of the equipment still needs to be verified, which takes a long time and affects operation and maintenance efficiency.

[0003] "A method and system for evaluating the operating status of electric power dispatching equipment" disclosed in Chinese patent literature has a publication number of CN115438893A and a publication date of December 6, 2022. It discloses a method and system for evaluating the operating status of electric power dispatching equipment, wherein the method includes: obtaining the network operating status value, protocol transmission status value and control business status value of the electric power dispatching system corresponding to the fault event occurring in the electric power dispatching equipment, and taking the maximum value of the network operating status value, protocol transmission status value and control business status value as the electric power dispatching system status value corresponding to the fault event; judging whether the electric power dispatching system status value meets the preset threshold conditions; however, the Chinese patent with publication number CN115438893A only involves the equipment operating status evaluation method, and does not involve the optimization method in the push process of equipment events, and cannot improve the overall operation and maintenance efficiency. Summary of the Invention

[0004] The present invention solves the problem that the long time required to verify the event status of equipment leads to low operation and maintenance efficiency. It proposes an event push method and system based on the equipment health code, which combines the equipment health code to realize the rapid push of events, reduce the verification time of equipment event status, and improve operation and maintenance efficiency.

[0005] In order to achieve the above object, the present invention adopts the following technical solution: a method for pushing events based on a device health code, comprising the following steps:

[0006] S1: Establish a device trigger event library based on device historical data and event severity, and establish a mapping relationship between device trigger events and health code color change events;

[0007] S2, obtaining device trigger information and health code color information based on the mapping relationship between device trigger events and health code color change events;

[0008] S3: Generate a pre-processed first health code image based on the device trigger information and the health code color information, and transmit the first health code image to the server to form a second health code image;

[0009] S4, the user end obtains and scans the second health code image of the server end, obtains the first health code image through one verification, obtains the original health code image through two verifications, and obtains the event status of the device from the original health code image.

[0010] In the present invention, first, a device trigger event library is established, which includes device historical data and the corresponding event criticality. Then, a mapping relationship between device trigger events and health code color change events in the device trigger event library is created; secondly, the mapping relationship is extracted and the device trigger information and health code color information are obtained; thereafter, an original health code image is generated according to the device trigger information and the health code color information, and the original health code image is preprocessed to form a first health code image and transmitted, and a second health code image is formed on the server side; finally, the user side performs a secondary verification on the health code image and obtains the event status of the device according to the original health code image; the method of the present invention preprocesses the device data while improving the operation and maintenance efficiency, thereby greatly ensuring the security of the device data.

[0011] Preferably, step S1 includes the following steps:

[0012] S11, determining applicable equipment types, obtaining historical data for different equipment types, analyzing the corresponding event criticality based on the fault conditions of different equipment types, and establishing an equipment trigger event library containing equipment historical data and event criticality;

[0013] S12, determine the specific type of the health code color change event, and establish a mapping relationship between the device trigger event and the health code color change event in sequence according to the device type.

[0014] In the present invention, first, the device type to which the present invention is applicable is selected, and the historical data of the corresponding device type is retrieved according to the device type. The corresponding time criticality is analyzed as a whole, and several criticality levels are established. Then, a device trigger event library is established; secondly, the specific type of the health code color change event needs to be obtained, and this type is also divided into several types. Finally, a mapping relationship between the device trigger event and the health code color change event is established, that is, the corresponding device trigger event can be found according to the health code color change event of the corresponding device type.

[0015] Preferably, step S3 includes the following steps:

[0016] S31, after verifying the device trigger information and the health code color information, generating an original health code image, the original health code image being in the form of a colored QR code;

[0017] S32, grayscale processing the original health code image using a floating-point algorithm, and segmenting the grayscale-processed original health code image to generate r*r segmented images, where r is an integer greater than 2;

[0018] S33, after inverting the color of the partially segmented images, recombining them according to the order generated in the random permutation library to generate a first health code image;

[0019] S34, sending the first health code image to the server through the private network to form a second health code image, and the second health code image is accompanied by the time when the event occurred.

[0020] In the present invention, the device trigger information and health code color information generated in step S2 are first verified, and an original health code image is generated in the initial image generation unit. Subsequently, the floating-point algorithm is used to complete the grayscale processing. After the grayscale processing is completed, the original image is segmented; some of the segmented images are inverted and recombined. The order of recombination is randomly generated according to the random permutation library. The first health code image generated by the recombination is sent to the server through a private network, and a second health code image is generated on the server. The second health code image can be obtained by qualified user terminals.

[0021] Preferably, the step S32 also includes a private key corresponding to the first health code image, and the private key includes the order generated in the random permutation library and the position of the segmented image after inversion processing.

[0022] In the present invention, the private key is transmitted through the public network, and the private key arrives at the server before the first health code image. The signal included in the private key can act on the first health code image after reaching the server to achieve the purpose of restoration.

[0023] Preferably, the random permutation library randomly generates a permutation order that is different from the permutation order of the original health code image according to the number of segmented images, and the permutation orders generated in two adjacent random permutation libraries are different.

[0024] In the present invention, the random permutation library can randomly generate an order that matches the number of segmented images, and the order must be different from the arrangement order of the original health code images.

[0025] Preferably, step S4 includes the following steps:

[0026] S41, the user terminal sends an acquisition instruction to the server terminal to obtain the second health code image of the corresponding device;

[0027] S42, obtaining a first health code image through a primary verification, where the primary verification includes user information verification;

[0028] S43, obtaining the original health code image through secondary verification, which includes device and user relevance verification and decryption startup verification;

[0029] S44, obtain the event status of the device based on the original health code image and perform corresponding processing.

[0030] In the present invention, after completing step S3, the user end obtains the second health code image of the device, performs a verification after acquisition to check whether the user information is correct, and performs a secondary verification after successful verification to verify the correlation between the device and the user and the decryption startup. The original health code image can be viewed only after passing the verification.

[0031] Preferably, the device and user relevance verification includes:

[0032] When the device type is determined, the management or operation and maintenance user corresponding to the device is detected. At this time, the correlation between the device and the user is 100%;

[0033] Verify whether the management or operation user has been delegated. If the user has been delegated n times, the device-user relevance is (100-nA)%, where A is the set decrement amount for each delegation. If (100-nA)% is less than 60%, the device-user relevance verification fails.

[0034] In the present invention, for the verification of the relevance between equipment and users, the user types are mainly limited. For users who directly manage or operate the equipment, the relevance is 100%, and they can pass the verification directly. For the delegated users of the above users, the relevance between equipment and users decreases according to the number of delegations. If the relevance is less than 60%, the verification cannot be passed, and it is necessary to reduce the number of delegations or transform A for adaptive adjustment.

[0035] An event push system based on a device health code is applicable to the above-mentioned event push method based on a device health code, including a user end, the user end is connected to a server end, the server end is connected to a control end, the control end is connected to several devices, the control end includes a preprocessing unit and several device trigger event libraries, and an initial image generation unit is provided between the preprocessing unit and the several device trigger event libraries.

[0036] In the present invention, the user end and the server end are connected by remote communication, and the server end and the control end are also connected by remote communication. The control end and the device can be connected by remote communication or wired connection; the control end includes multiple device trigger event libraries, and after the device trigger event library is established, a mapping relationship is established with the health code color change event, and then the device trigger information and health code color information are generated, and the original health code image is generated in the initial image generation unit. Finally, the original health code image is subjected to a series of transformation processes in the preprocessing unit to obtain the first health code image and send it to the server end; the system of the present invention realizes the rapid push of events and provides sufficient time for equipment maintenance.

[0037] Preferably, the preprocessing unit includes a segmentation area, the segmentation area is connected to a combination area, and the combination area is connected to a transmission area for sending the first health code image to the server.

[0038] In the present invention, the segmentation area performs grayscale processing and segmentation on the original health code image, the combination area recombines the segmented image, and the transmission area is connected to the server to send the generated first health code image to the server.

[0039] Preferably, a mapping model unit is further provided between the device trigger event library and the initial image generation unit, and the mapping model unit includes a mapping relationship between the device trigger event and the health code color change event.

[0040] In the present invention, the mapping model unit not only includes the mapping relationship between the device trigger event and the health code color change event, but also includes the generated device trigger information and health code color information.

[0041] The present invention has the following beneficial effects:

[0042] 1. The present invention relates to a device health code-based event push method and system, which combines the device health code to achieve rapid event push, reduce the verification time of device event status, and improve operation and maintenance efficiency; in addition, the health code has a clear identification function, which is convenient for users to view;

[0043] 2. The method of the present invention not only improves operation and maintenance efficiency, but also pre-processes device data, greatly ensuring device data security;

[0044] 3. The system of the present invention can realize the rapid push of events, providing sufficient time for equipment maintenance. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Figure 1 This is a flow chart of a method for pushing an event based on a device health code according to the present invention;

[0046] Figure 2This is a schematic diagram of an event push system based on device health code in the present invention;

[0047] Figure 3 This is a schematic diagram of a preprocessing unit of an event push system based on device health code of the present invention. DETAILED DESCRIPTION

[0048] In order to make the objectives, technical solutions and advantages of the present invention more clear, the present invention is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific implementation method described herein is only an optimal embodiment of the present invention, which is only used to explain the present invention and does not limit the scope of protection of the present invention. All other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0049] Example 1:

[0050] This embodiment proposes an event push method based on the device health code, refer to Figure 1 , including the following steps.

[0051] Step S1: Establish a device trigger event library based on device historical data and event criticality, and establish a mapping relationship between device trigger events and health code color change events; specifically, this step mainly includes the following sub-steps.

[0052] Step S11, determine the applicable equipment type, obtain historical data of different equipment types respectively, and analyze the corresponding event criticality according to the fault conditions of different equipment types, and establish an equipment trigger event library containing equipment historical data and event criticality; specifically, after determining the equipment type applicable to this embodiment, retrieve historical data based on the equipment type respectively, and divide different fault conditions of the same equipment type into different event criticality. In this embodiment, the event criticality is divided into three levels, namely emergency, warning and normal; then establish an equipment trigger event library, and the corresponding equipment historical data and event criticality in the equipment trigger event library correspond one to one.

[0053] Step S12, determine the specific type of the health code color change event, and establish a mapping relationship between the device trigger event and the health code color change event in sequence according to the device type; specifically, among the specific types of health code color change events in this embodiment, the health code colors are red, yellow, green and gray, and there are 12 corresponding color change events.

[0054] Step S2, obtain the device trigger information and health code color information according to the mapping relationship between the device trigger event and the health code color change event; specifically, after obtaining the separate device trigger information and health code color information, subsequent image generation and preprocessing can be performed; in this embodiment, the device trigger information includes the device trigger time and the device trigger specific event, and the health code color information includes the starting color information, color change information and end color information.

[0055] Step S3, a pre-processed first health code image is generated according to the device trigger information and the health code color information, and the first health code image is transmitted to the server to form a second health code image; specifically, this step includes the following sub-steps.

[0056] In step S31, after verifying the device trigger information and the health code color information, an original health code image is generated. The original health code image is in the form of a colored QR code. Specifically, after verifying the information generated in step S2, the original health code image can be generated.

[0057] Step S32: Use a floating-point algorithm to grayscale the original health code image, and segment the grayscale-processed original health code image to generate r*r segmented images, where r is an integer greater than 2. Specifically, the specific calculation formula for the floating-point algorithm is as follows:

[0058] G=0.299R+0.587G+0.114B, where R, G, and B represent the colors of the three color channels respectively, and G is the grayscale value after grayscale processing; after grayscale processing, the original health code is segmented into several segmented images.

[0059] In addition, step S32 also includes a private key corresponding to the first health code image, and the private key includes the order generated in the random permutation library and the position of the segmented image after inversion processing; in this embodiment, the private key is transmitted through the public network, and the private key arrives at the server before the first health code image. The signal included in the private key can act on the first health code image after reaching the server to achieve the purpose of restoration.

[0060] Step S33, after inverting the color of some of the segmented images, they are recombined in the order generated in the random permutation library to generate a first health code image; specifically, after segmenting the image, r*r segmented images are generated, and some of the r*r segmented images are inverted, and then overlapped and combined in the order generated by the random permutation library to generate the first health code image after preprocessing.

[0061] The random permutation library randomly generates a permutation order that is different from the permutation order of the original health code image based on the number of segmented images, and the permutation orders generated by two consecutive random permutation libraries are different. Specifically, the random permutation library can randomly generate an order that matches the number of segmented images, and this order must be different from the permutation order of the original health code image.

[0062] Step S34, the first health code image is sent to the server through the private network to form a second health code image, and the second health code image is accompanied by the time of the event; specifically, after sending it to the server, the server classifies and stores it to generate a second health code image.

[0063] The preprocessing process in the present invention includes the above-mentioned grayscale processing process, segmentation process, recombination process and transmission process.

[0064] In step S4, the user terminal obtains and scans the second health code image of the server terminal, obtains the first health code image through one verification, obtains the original health code image through two verifications, and obtains the event status of the device from the original health code image; this step includes the following sub-steps.

[0065] In step S41, the user terminal sends an acquisition instruction to the server terminal to acquire the second health code image of the corresponding device; specifically, the second health code image is stored in the storage unit of the server terminal.

[0066] Step S42, obtain the first health code image through one-time verification, and the one-time verification includes user information verification; specifically, for one-time verification, the user's registration information is mainly verified. If the verification passes, the first health code image is obtained. If the verification fails, the first health code image cannot be obtained, and step S43 cannot be entered.

[0067] Step S43, obtain the original health code image through secondary verification, the secondary verification includes device and user relevance verification and decryption startup verification; specifically, the secondary verification performs device and user relevance verification and decryption startup verification in sequence.

[0068] Specifically, the verification of device and user relevance mainly includes the following steps:

[0069] When the device type is determined, the management or operation and maintenance user corresponding to the device is detected. At this time, the correlation between the device and the user is 100%;

[0070] Verify that the management or operation user has been delegated. If n delegations have been made, the device-user relevance is (100-nA)%, where A is the decrement per delegation. If (100-nA)% is less than 60%, the device-user relevance verification fails. In this embodiment, A is 10. If n is 5, that is, after 5 delegations, (100-nA)% is less than 60%, indicating that the device-user relevance verification fails.

[0071] Step S44: Obtain the event status of the device based on the original health code image and perform corresponding processing.

[0072] In this embodiment, a device trigger event library is first established, which includes device historical data and the corresponding event criticality. Subsequently, a mapping relationship between device trigger events and health code color change events in the device trigger event library is created; secondly, the mapping relationship is extracted and the device trigger information and health code color information are obtained; thereafter, an original health code image is generated based on the device trigger information and health code color information, and the original health code image is preprocessed to form a first health code image and transmitted, and a second health code image is formed on the server side; finally, the user side performs a secondary verification on the health code image and obtains the event status of the device based on the original health code image; the method of the present invention preprocesses the device data while improving the operation and maintenance efficiency, thereby greatly ensuring the security of the device data.

[0073] In this embodiment, first, the device type to which the present invention is applicable is selected, and the historical data of the corresponding device type is retrieved according to the device type. The corresponding time criticality is analyzed as a whole, and several criticality levels are established. Then, a device trigger event library is established; secondly, the specific type of the health code color change event needs to be obtained, and this type is also divided into several types. Finally, a mapping relationship between the device trigger event and the health code color change event is established, that is, the corresponding device trigger event can be found according to the health code color change event of the corresponding device type.

[0074] In this embodiment, the device trigger information and health code color information generated in step S2 are first verified, and an original health code image is generated in the initial image generation unit. Subsequently, the floating-point algorithm is used to complete the grayscale processing. After the grayscale processing is completed, the original image is segmented; some segmented images are inverted and recombined. The order of recombination is randomly generated according to the random permutation library. The recombined first health code image is sent to the server through a private network, and a second health code image is generated on the server. The second health code image can be obtained by qualified user terminals.

[0075] In this embodiment, after completing step S3, the user terminal obtains the second health code image of the device, performs a verification after acquisition to check whether the user information is correct, and performs a secondary verification after successful verification to verify the relevance between the device and the user and the decryption startup. The original health code image can be viewed only after passing the verification.

[0076] In this embodiment, the verification of the relevance between equipment and users mainly limits the types of users. For users who directly manage or operate the equipment, the relevance is 100%, and they can pass the verification directly. For the delegated users of the above users, the relevance between equipment and users decreases according to the number of delegations. If the relevance is less than 60%, the verification cannot be passed, and it is necessary to reduce the number of delegations or transform A for adaptive adjustment.

[0077] This embodiment also proposes an event push system based on the device health code, refer to Figure 2 , the above-mentioned device health code-based event push method is applicable, including a user end, the user end is connected to a server end, the server end is connected to a control end, the control end is connected to several devices, the control end includes a pre-processing unit and several device trigger event libraries, and an initial image generation unit is provided between the pre-processing unit and the several device trigger event libraries. In this embodiment, the user end and the server end are connected via remote communication. The server end and the control end are also connected via remote communication. The control end and the device can be connected via remote communication or wired connection.

[0078] refer to Figure 3 The preprocessing unit includes a segmentation area, the segmentation area is connected to the combination area, and the combination area is connected to the transmission area that sends the first health code image to the server; specifically, the segmentation area performs grayscale processing and segmentation on the original health code image, the combination area recombines the segmented image, and the transmission area is connected to the server to send the generated first health code image to the server.

[0079] In the present invention, the control end includes multiple device trigger event libraries. After the device trigger event library is established, a mapping relationship is established with the health code color change event. In this embodiment, the process of establishing the mapping relationship occurs between the device trigger event library and the initial image generation unit, and then the device trigger information and health code color information are generated, and the original health code image is generated in the initial image generation unit. Finally, the original health code image is subjected to a series of transformation processes in the preprocessing unit to obtain the first health code image and send it to the server end; the system of the present invention realizes the rapid push of events and provides sufficient time for equipment maintenance.

[0080] Example 2

[0081] Based on Example 1, a mapping model unit (not shown in the figure) is further provided between the device trigger event library and the initial image generation unit. The mapping model unit includes a mapping relationship between the device trigger event and the health code color change event. In this embodiment, the mapping model unit not only includes the mapping relationship between the device trigger event and the health code color change event, but also includes the generated device trigger information and health code color information.

Claims

1. A method for pushing events based on a device health code, characterized in that: include: S1: Establish a device trigger event library based on device historical data and event severity, and establish a mapping relationship between device trigger events and health code color change events; S2, obtaining device trigger information and health code color information based on the mapping relationship between device trigger events and health code color change events; S3, generating a pre-processed first health code image according to the device trigger information and the health code color information, and transmitting the first health code image to the server to form a second health code image; include: S31, after verifying the device trigger information and the health code color information, generating an original health code image, which is in the form of a colored QR code; S32, using a floating-point algorithm to perform grayscale processing on the original health code image, segmenting the grayscale-processed original health code image, and generating r*r segmented images, where r is an integer greater than 2; S33, after inverting the color of the partially segmented images, recombining them according to the order generated in the random permutation library to generate a first health code image; S4, the user end obtains and scans the second health code image of the server end, obtains the first health code image through one verification, obtains the original health code image through two verifications, and obtains the event status of the device from the original health code image.

2. The event push method based on the device health code according to claim 1 is characterized in that: The step S1 comprises the following steps: S11, determining applicable equipment types, obtaining historical data for different equipment types, analyzing the corresponding event criticality based on the fault conditions of different equipment types, and establishing an equipment trigger event library containing equipment historical data and event criticality; S12, determine the specific type of the health code color change event, and establish a mapping relationship between the device trigger event and the health code color change event in sequence according to the device type.

3. The event push method based on the device health code according to claim 1 or 2, characterized in that: The step S3 also includes S34, sending the first health code image to the server through the private network to form a second health code image, and the second health code image is accompanied by the time when the event occurred.

4. The event push method based on the device health code according to claim 3 is characterized in that: The step S32 also includes a private key corresponding to the first health code image, and the private key includes the order generated in the random permutation library and the position of the segmented image after inversion processing.

5. The event push method based on the device health code according to claim 4 is characterized in that: The random permutation library randomly generates a permutation order that is different from the permutation order of the original health code image according to the number of segmented images, and the permutation orders generated in two adjacent random permutation libraries are different.

6. The event push method based on the device health code according to claim 1, 2 or 4, characterized in that: The step S4 comprises the following steps: S41, the user terminal sends an acquisition instruction to the server terminal to obtain the second health code image of the corresponding device; S42, obtaining a first health code image through a primary verification, where the primary verification includes user information verification; S43, obtaining the original health code image through secondary verification, which includes device and user relevance verification and decryption startup verification; S44, obtain the event status of the device based on the original health code image and perform corresponding processing.

7. The event push method based on the device health code according to claim 6 is characterized in that: The device and user relevance verification includes: When the device type is determined, the management or operation and maintenance user corresponding to the device is detected. At this time, the correlation between the device and the user is 100%; Verify whether the management or operation user has been delegated. If the user has been delegated n times, the device-user relevance is (100-nA)%, where A is the set decrement amount for each delegation. If (100-nA)% is less than 60%, the device-user relevance verification fails.

8. An event push system based on a device health code, applicable to an event push method based on a device health code according to any one of claims 1 to 7, characterized in that: It includes a user end, the user end is connected to a server end, the server end is connected to a control end, the control end is connected to several devices, the control end includes a preprocessing unit and several device trigger event libraries, and an initial image generation unit is provided between the preprocessing unit and the several device trigger event libraries.

9. The event push system based on device health code according to claim 8 is characterized in that: The preprocessing unit includes a segmentation area, the segmentation area is connected to a combination area, and the combination area is connected to a transmission area that sends the first health code image to the service end.

10. An event push system based on device health code according to claim 8 or 9, characterized in that: A mapping model unit is also provided between the device trigger event library and the initial image generation unit, and the mapping model unit includes a mapping relationship between the device trigger event and the health code color change event.

Images