User behavior monitoring method based on operation and maintenance transfer machine network traffic

Abstract

The invention discloses a user behavior monitoring method based on operation and maintenance transfer machine network traffic, and relates to the technical field of network monitoring. The method comprises the following steps that an authority management module obtains an authority record table from a database, the authority record table is written into the database by an administrator through an input module to be stored, the data read-write authority of each user is set in the authority record table, a management unit establishes a hard authority hierarchy graph, and the hard authority and subordination relation of each user are set; the hard permission is specifically a data range which can be read and written by a user in a database, the method has the advantages that the soft permission is set, the matched read-write permission is automatically generated according to the data range which is not set by an administrator by using the read-write operation of the user, the work log is generated, the cache module is used for data redundancy, and the data write-in operation can be withdrawn; the operation beyond the permission range is avoided, and the encryption module is arranged to divide and alternately display the output picture, so that the sensitive data leakage is avoided.

Description

Technical Field

[0001] The present invention relates to the technical field of network monitoring, and in particular to a user behavior monitoring method based on the network traffic of an operation and maintenance transfer machine. Background Technique

[0002] Traditional power grid equipment maintenance plans, work order systems, and monitoring systems are independent of each other and communicate by exchanging data in an operation and maintenance transfer machine.

[0003] Existing network traffic behavior monitoring cannot well match the huge power grid system, and it is impossible to monitor the permissions and read / write operations of each power grid-related personnel. There is a risk of operating beyond the authorized scope and a lack of data redundancy. There are too many practitioners in the power grid system, and setting personnel permissions is a complex and huge data task. There are always unconfigured data ranges or read / write permissions in application software or databases. At the same time, there is a risk of data leakage of sensitive data in the power grid system. Therefore, designing a monitoring method that can automatically plan personnel permissions and optimize itself is a technical problem that needs to be solved by those skilled in the art. Summary of the Invention

[0004] Aiming at the deficiencies of the prior art, the present invention provides a user behavior monitoring method based on the network traffic of an operation and maintenance transfer machine, which solves the problems raised in the above background technique.

[0005] To achieve the above objectives, the present invention is realized through the following technical solutions: A user behavior monitoring method based on the network traffic of an operation and maintenance transfer machine, which is realized based on a display window, an encryption module, a database, a cache module, a management unit, and an input module. The management unit includes a permission management module and a data management module. The output end of the input module is respectively connected to the input ends of the permission management module and the data management module. The ports of the permission management module and the data management module establish communication. The output end of the permission management module is connected to the input end of the encryption module. The output end of the encryption module is connected to the input end of the display window. The output end of the data management module is connected to the input end of the cache module. The output end of the cache module is connected to the input end of the database. The output end of the database is connected to the input end of the data management module. The display window is used to display the output screen for the user to view. The input module is used for the user to perform read / write operations. The encryption module is used to encrypt the screen information output by the display window. The data is used to store data, permission records tables, hard permission hierarchy diagrams, and soft permission hierarchy diagrams. The cache module is used to temporarily store the write operations of soft permissions to avoid overwriting the original data in the database. It includes the following steps:

[0006] Step 1: The permission management module sends an application to the data management module. The data management module obtains the permission record table from the database through the cache module and feeds it back to the permission management module. The permission record table is written into the database and saved by the administrator using the input module through the data management module and the cache module in sequence. The data read and write permissions of each user are set in the permission record table, and the data saved in the database is the power grid business and related operation and maintenance plans;

[0007] Step 2: The management unit establishes a hard permission hierarchy diagram based on the permission record table. The hard permissions and subordination relationships of each user are set in the hard permission hierarchy diagram. The hard permissions are specifically the data ranges that users can read and write in the database, and the subordination relationships are specifically the superior or subordinate connection relationships existing between each user. Users with a peer-to-peer relationship have the same data ranges that they can read and write in the hard permissions, so there is no such relationship in the subordination relationship, that is, there is no connection relationship between peer users;

[0008] Step 3: For the data ranges and subordination relationships not set in the permission record table, the management unit establishes a soft permission hierarchy diagram. The data management module marks the data ranges with overlapping hard permissions or not covered by all users' hard permissions in the database as soft permissions and incorporates them into the soft permission hierarchy diagram. Compared with hard permissions, soft permissions generally have limited data importance in the database, and the data ranges of soft permissions are more complex, which is not conducive to unified data management. Therefore, it is necessary to automatically judge whether the data ranges corresponding to the soft permissions can be read and written by recording the read and write behaviors of each user. Steps 4 - 5, Step 6, and Step 7 are all in a parallel relationship and are executed without a specific order;

[0009] Step 4: When a user requests to read and write the corresponding data range in the soft permission database through the input module, the permission management module in the management unit obtains the number of users k from the database through the data management module and the cache module in sequence. The permission management module of the management unit sets the initial weight of the i-th user requesting to read and write this soft permission as w0i. The permission management module sets the time decay coefficient α and the frequency correction coefficient γ. The permission management module calculates the data weight w of each user for this soft permission;

[0010] Step 5: The permission management module of the management unit judges whether to authorize the read and write application for new users based on the data weight w of each soft permission;

[0011] Step 6: The data management module of the management unit records the operation records of each user and aggregates them into a work log. The data management module saves the work log to the cache module and then to the database. Every day, the work log saved the previous day is pushed to the designated user for viewing and modification;

[0012] Step 7: On the premise of obtaining permission, the user reads the data range corresponding to the soft permission, converts the obtained data into an output screen through the management unit, and transmits it to the encryption module. The encryption module encrypts the output screen displayed in the display window to prevent data leakage.

[0013] Furthermore, the calculation of the data weight w specifically includes the following steps:

[0014] Step 401: The permission management module of the management unit sets the initial weight of the i-th user who reads and writes this soft permission as i = [1, 2, 3,..., k] The permission management module sets the minimum value of the initial weight w0i;

[0015] Step 402: The permission management module sets the calculation formula of the time decay coefficient α as α = e( -Δt×β ), where Δt is the interval time since the user last applied to read and write the soft permission, and β is the decay rate parameter set by the permission management module;

[0016] Step 403: The permission management module sets the calculation formula of the frequency correction coefficient γ as c is the number of times the user applies to read and write the soft permission within a fixed period. The larger the value of the number c, the closer the value of the frequency correction coefficient γ is to 1, and the longer the interval time Δt, the smaller the value of the frequency correction coefficient γ;

[0017] Step 404: The permission management module calculates the data weight w of each user for this soft permission according to the formula w = w0 × α × γ. The data weight w of each user for each soft permission needs to be recalculated by the permission management module every day.

[0018] Furthermore, the steps for a new user to apply to read and write the soft permission are as follows:

[0019] Step 501: The permission management module obtains the data state before the soft permission is marked. When the soft permission is not covered by the hard permission, the next step is executed. Conversely, when the soft permission overlaps with the hard permission, the data weight w extraction calculation is executed;

[0020] Step 502: The permission management module of the management unit counts the data weight w of each soft permission and sums them up to obtain the total weight W;

[0021] Step 503: The permission management module arranges the data weights w in descending order and accumulates the data weights w in turn. When the accumulated data weight w is greater than half of the total weight W in Step 502, the permission management module arranges the accumulated users in descending order of the data weight w to obtain the first permission sequence;

[0022] Step 504: The permission management module sends read / write requests for soft permissions to users in the order of the first permission sequence. The application content is displayed in the display module of the corresponding user through the encryption module. Each user is bound to a corresponding input module and display module for operations. After all users in the first permission sequence agree to the application through the input module, the new user can read and write the data range corresponding to the soft permission. Otherwise, if any user in the first permission sequence does not agree to the new user's soft permission read / write application, the permission management module cancels the new user's read / write application for the soft permission. At the same time, the permission management module reduces the data weight w of the user who does not agree to the new user's soft permission read / write application to avoid over - deep binding of the soft permission to a single user.

[0023] Further, the work log includes a hard - permission log and a soft - permission log. The collection and push of the work log specifically include the following steps:

[0024] Step 601: The user performs read / write operations on the data range corresponding to their own hard permissions in the database. Among them, the write operation includes creating and modifying data. The data after the read / write operation is directly saved to the database. The data management module records the read / write operations on the data range corresponding to the hard permissions and marks them as hard - permission logs;

[0025] Step 602: The data management module obtains the subordinate relationship in the hard - permission hierarchy diagram and regularly transfers the hard - permission logs marked the previous day to the display window of the user's upper - level user for viewing every day;

[0026] Step 603: Under the premise of obtaining permission, the user performs read / write operations on the data range corresponding to the soft permissions in the database. The data after the read / write operation is temporarily stored in the cache module. The write operation of the soft permission involves the modification of an application or software. Temporarily transfer the data ports of the application and software to the cache module. When the data in the cache module is transferred to the database or deleted, the data ports of the application and software are transferred back to the database. The original data of the soft permissions with uncompleted read / write operations is saved in the database as a backup of the data. The data management module records the read / write operations on the data range corresponding to the soft permissions and marks them as soft - permission logs;

[0027] Step 604: The data management module obtains the subordinate relationship in the hard - permission hierarchy diagram and regularly transfers the soft - permission logs marked the previous day to the display windows of all upper - level users of the user for viewing every day. All upper - level users are represented as the user's upper - level user, upper - two - level user, upper - three - level user until the top - most user. When the user views the soft - permission logs, they are arranged from high to low according to the subordinate relationship in the hard - permission hierarchy diagram to avoid a too - long soft - permission log list being unfavorable for the user to distinguish;

[0028] Step 605: When the user at the upper level views the soft - permission logs, the user determines whether the soft - permission logs are effective through the input module.

[0029] Furthermore, the specific steps for the encryption module to encrypt the output screen are as follows:

[0030] Step 701: The encryption module obtains the number g of software permissions in the software permission hierarchy diagram, and the encryption module divides the output screen into g 2 blocks, that is, the length and width of the rectangular output screen are evenly divided into g parts;

[0031] Step 702: The encryption module sets the screenshot frame and the hidden frame, and the encryption module randomly extracts blocks of the output screen and inputs them into the screenshot frame, and the remaining unextracted blocks are input into the hidden frame;

[0032] Step 703: The screenshot frame and the hidden frame are alternately refreshed to form the output screen. When the refresh rate is sufficient, the refresh rates of both the screenshot frame and the hidden frame are half of the display window refresh rate. When the refresh rate is insufficient, that is, the refresh rate of the display serial port is lower than the fixed frequency, the refresh rate of the screenshot frame is fixed, and the refresh rate of the hidden frame is the frame difference between the display window and the screenshot frame. When the user uses the input module to take a screenshot of the display window, the screenshot time point is always the screenshot frame.

[0033] Furthermore, the specific steps for the user to determine whether the software permission log is effective are as follows:

[0034] Step 6051: When the user views the software permission log through the display window, the input device is used to determine the read and write operations of each software permission in the software permission log;

[0035] Step 6052: If the user determines that the read and write operations of the software permission are effective, the next step is executed. Conversely, if the user determines that the read and write operations of the software permission are ineffective, jump to step 6054;

[0036] Step 6053: For write operations, the data management module inputs the read and write operations temporarily stored in the cache module into the database for replacement and overwrite. For read operations, the authorized user can continue to perform read operations on this software permission;

[0037] Step 6054: For write operations, the data management module deletes the read and write operations temporarily stored in the cache module, regarded as withdrawal. For read operations, the authorized user cannot perform read operations on this software permission subsequently.

[0038] Furthermore, for the read and write operations of the same software permission, when the judgments of the users receiving the pushed software permission log are opposite, the data management module, according to the subordinate relationship in the hardware hierarchy diagram, takes the judgment of the user with a higher level as the standard.

[0039] Furthermore, the specific steps for calculating the extraction of the data weight w are as follows:

[0040] It should be noted that steps 502 - 504 and steps 505 - 509 are in a parallel relationship and can be executed simultaneously without a specific order;

[0041] Step 505: The permission management module calculates the data weight w of the users corresponding to the overlapping hard permissions respectively, and extracts the data weight w with the largest value;

[0042] Step 506: The permission management module obtains the subordinate relationship of the users for whom the data weight w has been calculated from the hard permission hierarchy diagram. If there are subordinate users for this user, then in the subordinate users of the user for whom the data weight w has been calculated, step 505 is re - executed to calculate the data weight w of all subordinate users and extract the data weight w with the largest value. The subordinate users connected to each user for whom the data weight w has been calculated are at the same level;

[0043] Step 507: Repeat step 506 until the bottom - most user in the subordinate relationship, that is, this user has no subordinate users. The permission management module of the management unit statistics each extracted data weight w and sums them up to obtain the total weight W;

[0044] Step 508: The permission management module arranges the extracted data weights w in descending order of their values and accumulates the data weights w in sequence. When the accumulated data weight w is greater than half of the total weight W in step 507, the permission management module arranges the users that have been accumulated in descending order of the data weight w value to obtain the second permission sequence;

[0045] Step 509: The permission management module sends read - write requests for soft permissions to users in the order of the second permission sequence. The application content is displayed in the display module of the corresponding user through the encryption module. After all users in the second permission sequence agree to the application through the input module, the new user can read and write the data range corresponding to the soft permission. Similarly, if any user in the second permission sequence does not agree to the new user's soft - permission read - write application, the permission management module cancels the new user's read - write application for the soft permission, and at the same time, the permission management module reduces the data weight w of the user who does not agree to the new user's soft - permission read - write application.

[0046] Furthermore, in step 2, when the user's read - write operation exceeds their own data range, it is necessary to obtain the authorization of the superior user in the subordinate relationship before the operation can be carried out. In addition, when the user needs to read and write data ranges outside the non - subordinate relationship, that is, the data ranges involved by users in other departments with non - superior - subordinate relationships, it is necessary to obtain the authorization of the user corresponding to the data range before the operation can be carried out.

[0047] Further, each soft permission in the soft permission hierarchy diagram is arranged from largest to smallest according to the sum of its own data weights w. Both the soft permissions and the hard permissions are specifically data packets, and the data in the database can be incorporated into different data packets for reading and writing operations. Users can perform reading and writing operations on either the soft permissions or the hard permissions, or on the data.

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

[0049] 1. By setting soft permissions, the data range not set by the administrator is automatically generated with matching read and write permissions using the reading and writing operations of the user. At the same time, all users' reading and writing operations are monitored to generate a work log and a cache module is used for data redundancy, so that the operation of writing data can be withdrawn, avoiding operations beyond the permission range.

[0050] 2. By setting an encryption module to split and alternately display the output screen, screenshots or camera tools cannot obtain the data of the soft permissions in the database through the display window, avoiding the leakage of sensitive data.

[0051] Of course, any product implementing the present invention does not necessarily need to achieve all the above-mentioned advantages simultaneously. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following will briefly introduce the drawings required for describing the embodiments. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0053] Figure 1 It is a system block diagram of the user behavior monitoring method based on the network traffic of the operation and maintenance transfer machine of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0054] The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the drawings in the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, rather than all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present invention.

[0055] Please refer to Figure 1, the present invention provides a technical solution: a user behavior monitoring method based on the network traffic of an operation and maintenance transfer machine, which is implemented based on a display window, an encryption module, a database, a cache module, a management unit, and an input module. The management unit includes a permission management module and a data management module. The output end of the input module is respectively connected to the input ends of the permission management module and the data management module. The ports of the permission management module and the data management module establish communication. The output end of the permission management module is connected to the input end of the encryption module. The output end of the encryption module is connected to the input end of the display window. The output end of the data management module is connected to the input end of the cache module. The output end of the cache module is connected to the input end of the database. The output end of the database is connected to the input end of the data management module. The display window is used to display the output screen for the user to view. The input module is used for the user to perform read and write operations. The encryption module is used to encrypt the screen information output by the display window. The data is used to store data, permission record tables, hard permission hierarchy diagrams, and soft permission hierarchy diagrams. The cache module is used to temporarily store the write operations of soft permissions to prevent the original data in the database from being overwritten. It includes the following steps:

[0056] Step 1: The permission management module sends an application to the data management module. The data management module obtains the permission record table from the database through the cache module and feeds it back to the permission management module. The permission record table is written into the database by the administrator using the input module sequentially through the data management module and the cache module for storage. The data read and write permissions of each user are set in the permission record table. The data stored in the database is power grid services and related operation and maintenance plans;

[0057] Step 2: The management unit establishes a hard permission hierarchy diagram according to the permission record table. The hard permissions and subordinate relationships of each user are set in the hard permission hierarchy diagram. The hard permissions are specifically the data ranges that users can read and write in the database. The subordinate relationship is specifically the superior or inferior connection relationship existing between each user. The data ranges that users with a peer relationship can read and write in the hard permissions are the same. Therefore, there is no connection relationship in the subordinate relationship, that is, there is no connection relationship between peer users;

[0058] Step 3: For the data ranges and subordinate relationships not set in the permission record table, the management unit establishes a soft permission hierarchy diagram. The data management module marks the data ranges where there are overlapping hard permissions or where the hard permissions of all users do not cover in the database as soft permissions and incorporates them into the soft permission hierarchy diagram. Compared with hard permissions, soft permissions generally have limited data importance in the database, and the data ranges of soft permissions are more complex, which is not conducive to unified data management. Therefore, it is necessary to automatically judge whether the data ranges corresponding to soft permissions can be read and written by recording the read and write behaviors of each user. Steps 4 - Step 5, Step 6, and Step 7 are all in a parallel relationship and are executed without a specific order;

[0059] Step 4: When the user requests to read and write the corresponding data range in the soft permission database through the input module, the permission management module in the management unit sequentially obtains the number of users k from the database through the data management module and the cache module. The permission management module in the management unit sets the initial weight of the i-th user who requests to read and write this soft permission as w0i. The permission management module sets the time decay coefficient α and the frequency correction coefficient γ. The permission management module calculates the data weight w of each user for this soft permission;

[0060] Step 5: The permission management module in the management unit determines whether to authorize the read and write application of the new user according to the data weight w of each soft permission;

[0061] Step 6: The data management module in the management unit records the operation records of each user and aggregates them into a work log. The data management module saves the work log to the cache module and then saves it to the database. Every day, the work log saved the previous day is pushed to the specified user for viewing and modification;

[0062] Step 7: On the premise of obtaining permission, the user reads the data range corresponding to the soft permission, converts the obtained data into an output screen through the management unit and transmits it to the encryption module. The encryption module encrypts the output screen displayed in the display window to prevent data leakage.

[0063] Among them, the calculation of the data weight w specifically includes the following steps:

[0064] Step 401: The permission management module in the management unit sets the initial weight of the i-th user who reads and writes this soft permission as i = [1, 2, 3,..., k]. For example, for the first user who applies to read and write the soft permission, w0 = 1, and for the second user who applies to read and write the soft permission, w0 = 0.9, and so on. As the order of applying to read and write the soft permission increases, the initial weight decreases in turn. The permission management module sets the minimum value of the initial weight w0i, specifically 0.01;

[0065] Step 402: The permission management module sets the calculation formula of the time decay coefficient α as α = e( -Δt×β ), Δt is the interval time since the user last applied to read and write the soft permission, and β is the decay rate parameter set by the permission management module, with the default value of 0.1;

[0066] Step 403: The permission management module sets the calculation formula of the frequency correction coefficient γ as c is the number of times the user applies to read and write the soft permission within the most recent 30 days in a fixed cycle. The larger the value of the number c, the closer the value of the frequency correction coefficient γ is to 1, and the longer the interval time Δt, the smaller the value of the frequency correction coefficient γ;

[0067] Step 404: The permission management module calculates the data weight w of each user for this soft permission according to the formula w = w0 × α × γ. The data weight w of each user for each soft permission needs to be recalculated by the permission management module at zero o'clock every day.

[0068] The following is an example calculation:

[0069] User AA is the first user to apply for the read-write soft permission BB. The initial weight of user AA is 1. User AB is the second user to apply for the read-write soft permission BB. The initial weight of user AB is 0.9. After 3 days, the interval time Δt of user AA is 3 days, and the number of times c is 5 times. The interval time Δt of user AB is 3 days, and the number of times c is 2 times.

[0070] The time decay coefficient α of user AA = e( -3×0.1 ) = 0.7408. The frequency correction coefficient of user AA Therefore, after 3 days, the data weight w of user AA for the soft permission BB = 1 × 0.7408 × 0.417 ≈ 0.309.

[0071] The time decay coefficient α of user AB = e( -3×0.1 ) = 0.7408. The frequency correction coefficient of user AB Therefore, after 3 days, the data weight w of user AB for the soft permission BB = 0.9 × 0.7408 × 0.323 ≈ 0.215.

[0072] Among them, the steps for a new user to apply for a read-write soft permission are as follows:

[0073] Step 501: The permission management module obtains the data status before the soft permission is marked. When the soft permission is not covered by the hard permission, the next step is executed. Conversely, when the soft permission overlaps with the hard permission, the data weight w extraction calculation is executed.

[0074] Step 502: The permission management module of the management unit counts the data weight w of each soft permission and sums them up to obtain the total weight W.

[0075] Step 503: The permission management module arranges the data weights w in descending order of their values and accumulates the data weights w in turn. When the accumulated data weight w is greater than half of the total weight W in Step 502, the permission management module arranges the accumulated users in descending order of the data weight w values to obtain the first permission sequence.

[0076] Step 504: The permission management module sends read / write requests for soft permissions to users in the order of the first permission sequence. The application content is displayed in the display module of the corresponding user through the encryption module. Each user is bound to a corresponding input module and display module for operations. The input module is specifically an input device such as a keyboard or a mouse, and the display module is specifically a display device such as a liquid crystal display. After all users in the first permission sequence agree to the application through the input module, the new user can read and write the data range corresponding to the soft permission. Otherwise, if any user in the first permission sequence does not agree to the read / write application of the new user's soft permission, the permission management module cancels the read / write application of the new user for the soft permission. At the same time, the permission management module reduces the data weight w of the user who does not agree to the read / write application of the new user's soft permission, specifically reducing it by 0.02 based on the data weight w, to avoid the over - deep binding of this soft permission to a single user;

[0077] The following is an example calculation:

[0078] The data weight w of user AA corresponding to soft permission BB is 0.235, and the data weight w of user AB corresponding to soft permission BB is 0.178. The total weight W corresponding to soft permission BB is 0.512. When user AC applies to read and write soft permission BB, the cumulative data weight w after both user AA and user AB agree is 0.413, and half of the total weight W value is 0.256. Since 0.413 > 0.256, the permission management module allows user AC to read and write soft permission BB.

[0079] Among them, the work log includes a hard - permission log and a soft - permission log. The collection and push of the work log specifically include the following steps:

[0080] Step 601: The user performs read / write operations on the data range corresponding to their own hard permissions in the database. Among them, the write operation includes creating and modifying data. The data after the read / write operation is directly saved to the database, and the data management module records the read / write operations on the data range corresponding to the hard permissions and marks them as hard - permission logs;

[0081] Step 602: The data management module obtains the subordinate relationship in the hard - permission hierarchy diagram and regularly transfers the hard - permission logs marked the previous day to the display window of the user's upper - level user for viewing every day;

[0082] Step 603: On the premise of obtaining permission, the user performs read and write operations on the data range corresponding to the soft permission in the database. The data completed with the read and write operations is temporarily stored in the cache module. The write operation of the soft permission involves the modification of the application or software. Temporarily transfer the data ports of the application and software to the cache module. When the data in the cache module is transferred to the database or deleted, the data ports of the application and software are transferred back to the database. The original data of the soft permission with uncompleted read and write operations is saved in the database as a backup of the available data. The data management module records the read and write operations of the data range corresponding to the soft permission and marks it as a soft permission log;

[0083] Step 604: The data management module obtains the subordinate relationship in the hard permission hierarchy diagram and regularly transfers the soft permission logs marked the previous day to the display windows of all the user's superior users for their viewing every day. All superior users are represented as the user's first-level superior user, second-level superior user, third-level superior user until the topmost user. When the user views the soft permission logs, they are arranged from high to low according to the subordinate relationship in the hard permission hierarchy diagram to avoid the soft permission log list being too long and unfavorable for the user to distinguish;

[0084] Step 605: When the user at the superior level views the soft permission logs, the user determines whether the soft permission logs are effective through the input module.

[0085] Among them, the specific steps for the encryption module to encrypt the output screen include the following:

[0086] Step 701: The encryption module obtains the number g of soft permissions in the soft permission hierarchy diagram. The encryption module divides the output screen into g 2 blocks, that is, evenly divides the length and width of the rectangular output screen into g parts;

[0087] Step 702: The encryption module sets the screenshot frame and the hidden frame. The encryption module randomly extracts blocks and inputs them into the screenshot frame, and inputs the remaining unextracted blocks into the hidden frame;

[0088] Step 703: The screenshot frame and the hidden frame are alternately refreshed to form the output screen. When the refresh rate is sufficient, the refresh rates of both the screenshot frame and the hidden frame are half of the refresh rate of the display window. For example, if the refresh rate of the display window is 90 Hz, the refresh rates of both the screenshot frame and the hidden frame are 45 Hz. When the refresh rate is insufficient, that is, the refresh rate of the display serial port is lower than 48 Hz, the refresh rate of the screenshot frame is fixed at 24 Hz, and the refresh rate of the hidden frame is the frame difference between the display window and the screenshot frame. For example, if the refresh rate of the display window is 30 Hz, the refresh rate of the screenshot frame is 24 Hz, and the refresh rate of the hidden frame is 6 Hz. When the user uses the input module to take a screenshot of the display window, the screenshot time point is always the screenshot frame.

[0089] Among them, the specific steps for the user to judge whether the soft permission log is effective include the following:

[0090] Step 6051: When the user views the soft permission log through the display window, determine the read and write operations of each soft permission in the soft permission log through the input device;

[0091] Step 6052: If the user determines that the read and write operations of the soft permission are valid, perform the next step. Conversely, if the user determines that the read and write operations of the soft permission are invalid, jump to Step 6054;

[0092] Step 6053: For the write operation, the data management module replaces and overwrites the read and write operations temporarily stored in the cache module into the database. For the read operation, the user who has obtained permission can continue to perform the read operation on the soft permission;

[0093] Step 6054: For the write operation, the data management module deletes the read and write operations temporarily stored in the cache module, regarded as a withdrawal. For the read operation, the user who has obtained permission cannot perform the read operation on the soft permission subsequently.

[0094] Among them, for the read and write operations of the same soft permission, when the users who are pushed the soft permission log make opposite judgments, the data management module, according to the subordinate relationship in the hardware hierarchy diagram, takes the judgment of the user with a higher level as the standard. For example, for the write operation of the soft permission, the upper-level user judges it as invalid, and the upper-second-level user judges it as valid. Finally, the data management module will judge the write operation of the soft permission as valid and perform subsequent operations.

[0095] Among them, the specific calculation of the data weight w includes the following steps:

[0096] It should be noted that Step 502 - Step 504 and Step 505 - Step 509 are in a parallel relationship and can be executed simultaneously without a specific order;

[0097] Step 505: The permission management module calculates the data weight w of the users corresponding to the overlapping hard permissions respectively, and extracts the data weight w with the largest value;

[0098] Step 506: The permission management module obtains the subordinate relationship of the users who have completed the calculation of the data weight w from the hard permission hierarchy diagram. If this user has subordinate users, re-execute Step 505 in the subordinate users of the user who has completed the calculation of the data weight w to calculate the data weight w of all subordinate users and extract the data weight w with the largest value. The subordinate users connected to each user who has completed the calculation of the data weight w are at the same level;

[0099] Step 507; Repeat Step 506 until the bottommost user in the subordinate relationship, that is, this user has no subordinate users. The permission management module of the management unit counts each extracted data weight w and sums them to obtain the total weight W;

[0100] Step 508: The permission management module arranges the extracted data weights w in descending order and accumulates the data weights w in sequence. When the accumulated data weight w is greater than half of the total weight W in Step 507, the permission management module arranges the accumulated users in descending order of the data weight w values to obtain the second permission sequence;

[0101] Step 509: The permission management module sends read / write requests for soft permissions to users in the order of the second permission sequence. The application content is displayed in the display module of the corresponding user through the encryption module. After all users in the second permission sequence agree to the application through the input module, the new user can read and write the data range corresponding to the soft permission. Similarly, if any user in the second permission sequence does not agree to the new user's read / write request for the soft permission, the permission management module cancels the new user's read / write request for the soft permission, and at the same time, the permission management module reduces the data weight w of the user who does not agree to the new user's read / write request for the soft permission, specifically reducing it by 0.01 based on the data weight w.

[0102] Among them, in Step 2, when a user's read / write operation exceeds their own data range, they need to be authorized by the superior user in the subordinate relationship before they can perform the operation. In addition, when a user needs to read / write a data range outside the subordinate relationship, that is, the data range involved by users in other departments who are not in a superior-subordinate relationship, they need to be authorized by the user corresponding to the data range before they can perform the operation. For example, when a user reads the data range corresponding to a peer user outside the subordinate relationship, they need to be authorized by the peer user corresponding to the data range. The authorized user sends a request to read the data to the authorizing user, and the authorized user can read the data from the authorizing user's data range only after the authorizing user agrees.

[0103] Among them, each soft permission in the soft permission hierarchy diagram is arranged in descending order according to the sum of its own data weights w. Both soft permissions and hard permissions are specifically data packets. The data in the database can be included in different data packets for read / write operations. Users can perform read / write operations on soft permissions or hard permissions, or on data.

[0104] As described above, the above is only a preferred specific implementation manner of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present invention, according to the technical solution and inventive concept of the present invention, makes equivalent replacements or changes, and all should be covered within the protection scope of the present invention.

Claims

1. A method for monitoring user behavior based on the network traffic of an operation and maintenance transfer machine, characterized in that: It includes the following steps: Step 1: The permission management module obtains the permission record table from the database. The permission record table is written into the database by the administrator using the input module for storage. Each user's data read and write permissions are set in the permission record table; Step 2: The management unit establishes a hard permission hierarchy diagram, sets the hard permissions and subordinate relationships of each user. The hard permissions are specifically the data ranges read and written by the user in the database, and the subordinate relationship is specifically the superior-subordinate connection relationship existing between each user; Step 3: Establish a soft permission hierarchy diagram, mark the data ranges with overlapping hard permissions or un-covered hard permissions in the database as soft permissions and incorporate them into the soft permission hierarchy diagram; Step 4: When a user requests to read and write the data range of soft permissions, obtain the number of users k, set the initial weight of the i-th user as w0i, set the time decay coefficient α and the frequency correction coefficient γ, and calculate the data weight w of each user; Step 5: Judge whether a new user is authorized for the read and write application according to the data weight w of each soft permission; Step 6: Record the operation records of each user and aggregate them into a work log. Save the work log to the cache module and then to the database, and regularly push the saved work log to the specified user for viewing and modification; Step 7: On the premise of obtaining permission, the user reads the data range corresponding to the soft permission, converts the obtained data into an output screen and transmits it to the encryption module, and the encryption module encrypts the output screen displayed in the display window.

2. The user behavior monitoring method based on the network traffic of the operation and maintenance transfer machine according to claim 1, wherein The calculation of the data weight w specifically includes the following steps: Step 401: The permission management module of the management unit sets the initial weight of the i-th user as i = [1, 2, 3,..., k], and sets the minimum value of the initial weight w0i; Step 402: Set the calculation formula of the time decay coefficient α as α = e( -Δt×β ), where Δt is the interval time since the user last applied for read / write soft permission, and β is the set decay rate parameter; Step 403: Set the calculation formula of the frequency correction coefficient γ as c is the number of times the user applies for read / write soft permissions within a fixed period; Step 404: Calculate the data weight w of each user according to the formula w = w0 × α × γ. The data weight w of each user for each soft permission needs to be recalculated every day.

3. The user behavior monitoring method based on the network traffic of the operation and maintenance transfer machine according to claim 1, wherein, The steps for a new user to apply for reading and writing soft permissions are as follows: Step 501: The permission management module obtains the data state before the soft permission is marked. When the soft permission is not covered by the hard permission, execute the next step. Otherwise, when the soft permission overlaps with the hard permission, execute the extraction and calculation of the data weight w; Step 502: Statistically sum the data weights w of each soft permission to obtain the total weight W; Step 503: Arrange in descending order according to the value of the data weight w and accumulate the data weights w in turn. When the accumulated data weight w is greater than half of the total weight W in Step 502, the users whose data weights have been accumulated obtain the first permission sequence; Step 504: Send the read and write application of the soft permission to the user in the order of the first permission sequence. The application content is displayed in the corresponding display module. After all the users in the first permission sequence agree to the application, the new user can read and write the data range corresponding to the soft permission. Otherwise, if any user in the first permission sequence does not agree to the new user's soft permission read and write application, the permission management module cancels the new user's read and write application for the soft permission, and at the same time the permission management module reduces the data weight w of the disagreeing user.

4. The user behavior monitoring method based on the network traffic of the operation and maintenance transfer machine according to claim 1, wherein The work log includes a hard permission log and a soft permission log. The aggregation and pushing of the work log specifically include the following steps: Step 601: The user performs read and write operations on the data range corresponding to their own hard permissions in the database. The data after the read and write operations is directly saved to the database, and the data management module records the read and write operations of the hard permissions and marks them as hard permission logs; Step 602: Obtain the subordination relationship in the hard permission hierarchy diagram, and regularly transmit the marked hard permission logs to the user's upper-level user for viewing; Step 603: Under the premise of obtaining permission, the user performs read and write operations on the data range corresponding to the soft permission in the database. The data after the read and write operations is temporarily stored in the cache module, and the read and write operations of the soft permission are recorded and marked as soft permission logs; Step 604: Obtain the subordination relationship in the hard permission hierarchy diagram, and regularly transmit the marked soft permission logs to all upper-level users of the user for viewing. When the user views the soft permission logs, they are arranged from high to low according to the subordination relationship in the hard permission hierarchy diagram; Step 605: When the user views the soft permission logs, the user determines whether the soft permission logs are effective.

5. The user behavior monitoring method based on the network traffic of the operation and maintenance transfer machine according to claim 1, wherein The specific steps for the encryption module to encrypt the output screen include the following: Step 701: The encryption module obtains the number g of soft permissions in the soft permission hierarchy diagram and divides the output screen into g 2 pieces of tiles; Step 702: The encryption module sets the screenshot frame and the hidden frame, and the encryption module randomly extracts blocks of the screenshot frame, and inputs the remaining unextracted blocks into the hidden frame; Step 703: The screenshot frame and the hidden frame are alternately refreshed to form the output screen. When the refresh rate is sufficient, the refresh rates of both the screenshot frame and the hidden frame are half of the display window refresh rate. When the refresh rate is insufficient, the refresh rate of the screenshot frame is fixed, and the refresh rate of the hidden frame is the frame difference between the display window and the screenshot frame. When the user uses the input module to take a screenshot of the display window, the screenshot time point is always the screenshot frame.

6. The user behavior monitoring method based on the network traffic of the operation and maintenance transfer machine according to claim 4, wherein The specific steps for the user to determine whether the soft permission logs are effective include the following: Step 6051: When the user views the soft permission logs, determine the read and write operations of each soft permission in the soft permission logs; Step 6052: If the user determines that the read and write operations of the soft permission are effective, then proceed to the next step. Conversely, if the user determines that the read and write operations of the soft permission are ineffective, jump to Step 6054; Step 6053: For the write operation, the data management module replaces and overwrites the read and write operations temporarily stored in the cache module into the database. For the read operation, the user who has obtained permission can continue to perform read operations on the soft permission; Step 6054: For the write operation, delete the read and write operations temporarily stored in the cache module. For the read operation, the user who has obtained permission cannot perform read operations on the soft permission subsequently.

7. The user behavior monitoring method based on the network traffic of the operation and maintenance transfer machine according to claim 6, wherein For the read and write operations of the same soft permission, when the judgments of the users who are pushed the soft permission logs are opposite, the data management module, according to the subordination relationship in the hardware hierarchy diagram, takes the judgment of the user with a higher level as the standard.

8. The user behavior monitoring method based on the network traffic of the operation and maintenance transfer machine according to claim 3, wherein The specific steps for calculating and extracting the data weight w include the following: It should be noted that Step 502 - Step 504 and Step 505 - Step 509 are in a parallel relationship; Step 505: The permission management module calculates the data weight w of the users corresponding to the overlapping hard permissions respectively, and extracts the data weight w with the largest value; Step 506: Obtain the subordination relationship of the user from the hard permission hierarchy diagram. If the user has subordinate users, re-execute Step 505 in the user's subordinate users to calculate the data weight w of all subordinate users and extract the data weight w with the largest value; Step 507; Repeat Step 506 until the bottommost user in the subordination relationship, and sum up each extracted data weight w to obtain the total weight W; Step 508: Arrange the data weights w in descending order and accumulate the data weights w in sequence. When the accumulated data weight w is greater than half of the total weight W in Step 507, the users whose data weights have been accumulated will obtain the second permission sequence; Step 509: Send read and write requests for soft permissions to the users in the order of the second permission sequence. The application content is displayed in the corresponding display module. After all the users in the second permission sequence agree to the application, the new user can read and write the data range corresponding to the soft permission. If any user in the second permission sequence does not agree to the new user's read and write request for the soft permission, the permission management module cancels the new user's read and write request for the soft permission, and at the same time, the permission management module reduces the data weight w of the disagreeing user.

9. The user behavior monitoring method based on the network traffic of the operation and maintenance transfer machine according to claim 1, wherein In Step 2, when the user's read and write operation exceeds their own data range, they need the authorization of the superior user in the subordinate relationship to perform the operation. When the user needs to read and write the data range outside the non-subordinate relationship, they need the authorization of the user corresponding to the data range to perform the operation.

10. The user behavior monitoring method based on the network traffic of the operation and maintenance transfer machine according to claim 1, wherein, In the soft permission hierarchy diagram, each soft permission is arranged in descending order according to the sum of its own data weights w. Both soft permissions and hard permissions are data packets. The data in the database is incorporated into different data packets for read and write operations. The user performs read and write operations on both soft permissions or hard permissions and on the data.

Images