A software usage management method and system

Abstract

The present invention provides a software usage management method and system, which relates to the field of software management technology. When receiving user login information, traverse the preset permission management list according to the user login information and judge whether software usage management is required; if so, determine the management strategy, warning conditions and warning strategy according to the user login information; determine the target monitoring software according to the management strategy and obtain the usage information corresponding to the target monitoring software; when it is determined that the warning conditions are met according to the usage information, generate a software usage report; and perform software usage warning according to the warning strategy and the software usage report. Determine the corresponding management strategy, warning conditions and warning strategy according to the user login information, and realize the technical effect of automatically performing software management and control according to the login information; because the management strategy and the login information are matched, the technical effect of automatically switching the management strategy for different users is realized.

Description

Technical Field

[0001] The present application relates to the technical field of software management, and in particular to a software usage management method and system. Background Art

[0002] At present, the number of teenagers using the Internet is increasing day by day. When teenagers use terminals such as PCs, mobile phones, tablets or Internet TVs, they are often easily affected by electronic products because of their lack of self-control. If parents do not discover and control them in time, many adverse consequences may occur.

[0003] Therefore, how to reasonably manage the use of software on electronic devices has become a technical problem that needs to be solved urgently. Summary of the invention

[0004] In order to reasonably manage software usage on electronic devices, the present application provides a software usage management method and system.

[0005] In the first aspect, the present application provides a software usage management method using the following technical solution:

[0006] A software usage management method, the method comprising:

[0007] When receiving user login information, traverse the preset permission management list according to the user login information and determine whether software usage management is required;

[0008] If yes, determining the management strategy, warning conditions and warning strategy according to the user login information;

[0009] Determine the target monitoring software according to the management strategy and obtain usage information corresponding to the target monitoring software;

[0010] When it is determined according to the usage information that the warning condition is met, generating a software usage report;

[0011] Software usage warning is performed according to the warning strategy and the software usage report.

[0012] The step of traversing a preset permission management list according to the user login information and determining whether software use management is required upon receiving the user login information comprises:

[0013] Upon receiving the user login information, obtaining a user identifier corresponding to the user login information;

[0014] Traversing the preset authority management list according to the user identifier to obtain a traversal result;

[0015] When the traversal result is a type of user, determining that the user is a management user;

[0016] When the traversal result is a second-class user, determining that software usage management is required;

[0017] When the traversal result is a new user, the login features corresponding to the user login information are obtained, and whether software usage management is required is determined in a preset special management list based on the login features, wherein the login features include the user login IP address and / or login MAC address.

[0018] The step of determining the management strategy, warning conditions and warning strategy according to the user login information includes:

[0019] Determine a target user of the first category according to the user login information, and obtain a software management profile corresponding to the target user of the first category;

[0020] Determine the management object information according to the management target type label in the software management portrait;

[0021] Acquire current usage scenario information, and determine a management strategy based on the management mode label in the software management portrait and the usage scenario information;

[0022] The warning conditions and warning strategies are determined according to the management strategy.

[0023] The step of obtaining the current usage scenario information and determining the management strategy according to the management mode label in the software management portrait and the usage scenario information comprises:

[0024] Acquire current usage scenario information, and match the target scenario with the current usage scenario information in a preset scenario template;

[0025] Obtaining a management weight factor in the target scenario;

[0026] Generating a strategy set in a preset strategy set according to the management weight factor;

[0027] A management policy is determined according to the policy set.

[0028] The step of determining the target monitoring software according to the management policy and obtaining the usage information corresponding to the target monitoring software includes:

[0029] Obtaining a current software list, classifying software functions according to the current software list and obtaining classification results;

[0030] Determine the type of management software according to the management strategy and determine the target monitoring software in combination with the classification result;

[0031] The usage information corresponding to the target monitoring software is obtained through a preset interface.

[0032] The step of performing software usage warning according to the warning strategy and the software usage report comprises:

[0033] Determine the abnormality level and abnormal item content according to the software usage report;

[0034] Performing strategy screening in the early warning strategy according to the abnormality level to obtain a screening result;

[0035] Generate a target early warning strategy based on the abnormal item content and the screening results;

[0036] Software usage warning is performed according to the target warning strategy.

[0037] After the step of performing software usage warning according to the warning strategy and the software usage report, the method further includes:

[0038] Acquire user operation information, and determine whether the early warning strategy is effective according to the user operation information;

[0039] If it is determined that the early warning strategy is invalid, obtaining the corresponding management measures in the early warning strategy;

[0040] The target software is managed through the management measures combined with the user operation information and the user portrait information corresponding to the user login information is updated in the preset authority management list.

[0041] In a second aspect, the present application provides a software usage management system, comprising:

[0042] The rights management module is used to, upon receiving user login information, traverse the preset rights management list according to the user login information and determine whether software usage management is required;

[0043] a policy determination module, for determining a management policy, an early warning condition and an early warning policy according to the user login information;

[0044] A usage information module, used to determine the target monitoring software according to the management strategy and obtain usage information corresponding to the target monitoring software;

[0045] A software usage report module, used to generate a software usage report when it is determined that the warning condition is met according to the usage information;

[0046] The software usage warning module is used to perform software usage warning according to the warning strategy and the software usage report.

[0047] In summary, the present invention includes the following beneficial technical effects:

[0048] When receiving user login information, the present invention traverses the preset permission management list according to the user login information and determines whether software usage management is required; if so, the management strategy, warning conditions and warning strategy are determined according to the user login information; the target monitoring software is determined according to the management strategy and the usage information corresponding to the target monitoring software is obtained; when the warning conditions are determined to be met according to the usage information, a software usage report is generated; and software usage warning is performed according to the warning strategy and the software usage report. The corresponding management strategy, warning conditions and warning strategy are determined according to the user login information, achieving the technical effect of automatically performing software management and control according to the login information; because the management strategy and the login information are matched, the technical effect of automatically switching the management strategy for different users is achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Figure 1 It is a flowchart of the first embodiment of the software usage management method of the present invention.

[0050] Figure 2 It is a structural block diagram of the first embodiment of the software usage management system of the present invention. DETAILED DESCRIPTION

[0051] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below through the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0052] The present application embodiment provides a software usage management method, referring to Figure 1 , Figure 1 This is a flowchart of the first embodiment of the software usage management method of the present application.

[0053] In this embodiment, the software usage management method includes the following steps:

[0054] Step S10: When receiving the user login information, traverse the preset authority management list according to the user login information and determine whether software usage management is required.

[0055] It should be noted that the step of traversing the preset permission management list according to the user login information and judging whether software usage management is needed when the user login information is received includes: obtaining the user identifier corresponding to the user login information when the user login information is received; traversing the preset permission management list according to the user identifier to obtain the traversal result; when the traversal result is a type I user, determining that the user is a management user; when the traversal result is a type II user, determining that software usage management is needed; when the traversal result is a new user, obtaining the login features corresponding to the user login information, and judging whether software usage management is needed in the preset special management list according to the login features, wherein the login features include the user login IP address and / or login MAC address.

[0056] It should be noted that in this embodiment, the start condition is to receive the user login information, and the user level is determined according to the user login information. The user level can be set in advance according to the specific usage. For example, the user level can be divided into three categories: management user, managed user and default user. Among them, the use permission of the specific corresponding software can be set according to the specific level of the user. The access rights of the managed user and the default user to some software can be set to be prohibited.

[0057] It is understandable that after receiving the user login information, the preset permission management list will be traversed according to the account name in the user login information to obtain the management permission corresponding to the account name.

[0058] It should be noted that if the user is a default user, that is, the permission matching result cannot be obtained in the preset management list, the permission matching is performed based on the IP address in the user login feature or the MAC address corresponding to the user login device. The management user can set the user to be automatically bound as the default user in the user feature matching result, or pre-enter a special IP address or MAC address for permission setting according to actual usage. Set a group or a specific address, and automatically match it with the set permissions when the corresponding user feature is received.

[0059] In a specific implementation, the determination of whether software usage management is required is to traverse the preset authority management list according to the user login information, determine the user's current authority level according to the user login information, and determine whether the user is a manager or a managed person. In the preset authority management list, at least one management user and an information receiving port corresponding to the management user are bound to each managed user. After determining that the authority corresponding to the user login information is a managed person, a login report is generated according to the user login information. And the login report is sent to the information receiving port corresponding to the management user.

[0060] It should be noted that when it is determined that software management is required, the current user's software usage permissions will also be determined. For software that does not have permissions in the current device, access permissions will be closed.

[0061] It is understandable that the user login information includes: user name, password, device information, login time. The traversal conditions are established based on the user name, device information and login time, and whether software usage management is required is determined based on the traversal conditions in the preset permission management list. For example: User A does not need to perform software usage management during the time period of 8:00-10:00, but needs to perform software usage management during the time period of 19:00-21:00. Therefore, in this embodiment, the technical effect of accurately determining whether the current user login information needs software usage management is achieved by setting convenient conditions.

[0062] It should be noted that this embodiment includes three types of users: Class I users, Class II users and new users. Class I users are management users who have the authority to set management policies for related Class II users. Class II users correspond to at least one Class I user. The software usage rights of Class II users are subject to certain restrictions. New users will enter the default usage mode and obtain corresponding software usage rights based on the login characteristics of the new users.

[0063] Step S20: If yes, determine the management strategy, warning condition and warning strategy according to the user login information.

[0064] In a specific implementation, the step of determining the management strategy, warning conditions and warning strategy based on the user login information includes: determining a target category of users based on the user login information, and obtaining a software management portrait corresponding to the target category of users; determining management object information based on the management target type label in the software management portrait; obtaining current usage scenario information, and determining the management strategy based on the management mode label in the software management portrait combined with the usage scenario information; and determining warning conditions and warning strategies based on the management strategy.

[0065] It should be noted that the step of determining the management strategy based on the management mode label in the software management portrait in combination with the usage scenario information includes: obtaining the current usage scenario information, matching the target scenario in the preset scenario template in combination with the current usage scenario information; obtaining the management weight factor in the target scenario; generating a policy set in the preset policy set according to the management weight factor; and determining the management strategy based on the policy set.

[0066] It is understandable that when it is determined that the user login information needs to be managed for software use, the user identity will be determined based on the user login information, and the corresponding manager identity will be determined based on the user identity. The manager identity in this embodiment refers to the target type 1 user. The management strategy, warning conditions and warning strategy are determined by determining the software management portrait corresponding to the target type 1 user.

[0067] It should be noted that in this embodiment, the software management portrait in the policy refers to a set of management information tags, and the target user with the identity of the administrator can set the software management portrait according to their own management and use needs. This embodiment also provides a default management portrait template to enable a class of users to quickly formulate management needs. The specific default management portrait template can be set by the system administrator according to the actual situation, for example: a template for underage students, a template for college students, or a template for the elderly.

[0068] It is understandable that the current usage scenario information includes hardware information, time information, and whether there is preset management weight information. The preset management weight information corresponds to different usage preference modes, such as power saving mode, learning mode or other pre-set modes.

[0069] In a specific implementation, the management policy in this embodiment includes: the functions of device usage, usage time limit, and data access rights, which correspond to the use of the login device and the use of the software in the login device.

[0070] It is understandable that the warning conditions refer to the conditions that trigger the warning, such as: the usage time exceeds the set upper limit, the prohibited function is accessed, the data transmission volume exceeds the set threshold, etc.

[0071] It should be noted that the warning strategy in this embodiment refers to limiting the warning content, closing the authority, turning off the power supply, or sending warning information to the corresponding type of user reserved data transmission port when using the terminal.

[0072] Step S30: determining the target monitoring software according to the management policy and obtaining usage information corresponding to the target monitoring software.

[0073] It should be noted that the step of determining the target monitoring software according to the management policy and obtaining the usage information corresponding to the target monitoring software includes: obtaining the current software list, classifying the software functions according to the current software list and obtaining the classification results; determining the management software type according to the management policy and determining the target monitoring software in combination with the classification results; and obtaining the usage information corresponding to the target monitoring software through a preset interface.

[0074] It should be noted that, in this embodiment, the usage information of the target software is obtained through an API or a log collection tool, wherein the usage information includes information such as usage time, accessed functions, and data transmission volume.

[0075] It is understandable that by obtaining the software list downloaded from the device, the software can be classified according to the software usage or usage function. The classification result is to match the management strategy and determine the target monitoring software.

[0076] Step S40: When it is determined that the warning condition is met according to the usage information, a software usage report is generated.

[0077] In this embodiment, judging whether the warning condition is met according to the usage information refers to determining the specific warning behavior in the warning condition and implementing monitoring software usage information. Each usage information obtained in real time is compared with the specific warning behavior to finally determine whether the warning condition is met.

[0078] If it is determined that the early warning conditions are met, the acquired abnormal usage information is organized into a software usage report. The software usage report includes: usage time information, software usage information, specific behavior operation information, and usage evaluation information automatically generated based on the above information. The usage evaluation information in this embodiment will be collected based on the software usage in the network, and the usage of the same type of software or the current software will be compared at the current moment to generate a comparative evaluation report.

[0079] Step S50: Perform software usage warning according to the warning strategy and the software usage report.

[0080] It should be noted that the step of performing software usage warning based on the warning strategy and the software usage report includes: determining the abnormality level and abnormal item content based on the software usage report; performing strategy screening in the warning strategy based on the abnormality level to obtain screening results; generating a target warning strategy based on the abnormal item content and the screening results; and performing software usage warning based on the target warning strategy.

[0081] It should be noted that in this embodiment, different abnormal situations are classified, and the specific classification is determined by the software usage report. In the software usage report, different abnormal levels are determined according to the behavior content, and the warning strategies corresponding to different abnormal levels will also be different.

[0082] In the specific implementation, the abnormality level is determined first, and then screening is performed based on the abnormality level. After the screening result is determined, the target warning strategy is determined based on the content of the abnormal project, and then the software usage warning is performed based on the target warning strategy.

[0083] It can be understood that after the step of issuing a software usage warning based on the warning strategy and the software usage report, it also includes: obtaining user operation information, and judging whether the warning strategy is effective based on the user operation information; if the warning strategy is determined to be invalid, obtaining the corresponding management measures in the warning strategy; managing the target software through the management measures combined with the user operation information and updating the user portrait information corresponding to the user login information in the preset permission management list.

[0084] In the specific implementation, obtain the user's operation information after the warning, including the user's behavior changes, whether to continue abnormal operations, etc. According to the user operation information, evaluate the effectiveness of the warning strategy. If the warning strategy is effective, continue monitoring; if not, proceed to the next step.

[0085] It is understandable that this embodiment dynamically adjusts the management measures. If the evaluation result shows that the early warning strategy is invalid, the corresponding management measures are obtained from the early warning strategy. The target software is managed by combining the management measures with the user operation information. The user portrait information corresponding to the user login information is updated in the preset permission management list.

[0086] It should be noted that the purpose of updating the user portrait information in this embodiment is to integrate the user's behavior data into a behavior tag, and update the behavior tag history record corresponding to the user portrait according to the usage evaluation score of the current behavior tag. It is realized that the user portrait can be automatically updated after each use of the current user, and the accuracy of the user portrait in the preset permission management list is realized. And the corresponding type of user can grasp the historical usage record of the managed user by viewing the user portrait information.

[0087] When receiving user login information, this embodiment traverses the preset permission management list according to the user login information and determines whether software usage management is required; if so, the management strategy, warning conditions and warning strategy are determined according to the user login information; the target monitoring software is determined according to the management strategy and the usage information corresponding to the target monitoring software is obtained; when it is determined according to the usage information that the warning conditions are met, a software usage report is generated; and software usage warnings are issued according to the warning strategy and the software usage report. The corresponding management strategy, warning conditions and warning strategy are determined according to the user login information, achieving the technical effect of automatically performing software management and control according to the login information; because the management strategy and the login information are matched, the technical effect of automatically switching management strategies for different users is achieved.

[0088] Reference Figure 2 , Figure 2 This is a structural block diagram of the first embodiment of the software usage management system of this application.

[0089] like Figure 2 As shown, the software usage management system proposed in the embodiment of the present application includes:

[0090] The authority management module 10 is used to, upon receiving user login information, traverse the preset authority management list according to the user login information and determine whether software usage management is required;

[0091] A strategy determination module 20, for determining a management strategy, an early warning condition and an early warning strategy according to the user login information;

[0092] A usage information module 30, used to determine the target monitoring software according to the management strategy and obtain usage information corresponding to the target monitoring software;

[0093] A software usage report module 40, configured to generate a software usage report when it is determined that the warning condition is met according to the usage information;

[0094] The software usage warning module 50 is used to perform software usage warning according to the warning strategy and the software usage report.

[0095] When receiving user login information, this embodiment traverses the preset permission management list according to the user login information and determines whether software usage management is required; if so, the management strategy, warning conditions and warning strategy are determined according to the user login information; the target monitoring software is determined according to the management strategy and the usage information corresponding to the target monitoring software is obtained; when it is determined according to the usage information that the warning conditions are met, a software usage report is generated; and software usage warnings are issued according to the warning strategy and the software usage report. The corresponding management strategy, warning conditions and warning strategy are determined according to the user login information, achieving the technical effect of automatically performing software management and control according to the login information; because the management strategy and the login information are matched, the technical effect of automatically switching management strategies for different users is achieved.

[0096] It should be noted that the workflow described above is merely illustrative and does not limit the scope of protection of the present application. In practical applications, technicians in this field can select part or all of it according to actual needs to achieve the purpose of the present embodiment, and no limitation is made here.

[0097] In addition, for technical details not fully described in this embodiment, please refer to the method for software usage management provided in any embodiment of the present application, and will not be repeated here.

[0098] In addition, it should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or system. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or system including the element.

[0099] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0100] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as a read-only memory (ROM) / RAM, a disk, or an optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods of each embodiment of the present application. The above is only a preferred embodiment of the present application, and does not limit the scope of protection of the present application. All equivalent structures or equivalent process changes made using the contents of the present application specification and drawings, or directly or indirectly used in other related technical fields, are similarly included in the scope of protection of the present application.

Claims

1. A software usage management method, characterized in that: The method comprises: When receiving user login information, traverse the preset permission management list according to the user login information and determine whether software usage management is required; If yes, determining the management strategy, warning conditions and warning strategy according to the user login information; Determine the target monitoring software according to the management strategy and obtain usage information corresponding to the target monitoring software; When it is determined according to the usage information that the warning condition is met, generating a software usage report; Perform software usage warning according to the warning strategy and the software usage report; The step of determining the management strategy, warning conditions and warning strategy according to the user login information includes: Determine a target user of the first category according to the user login information, and obtain a software management profile corresponding to the target user of the first category; Determine the management object information according to the management target type label in the software management portrait; Acquire current usage scenario information, and determine a management strategy based on the management mode label in the software management portrait and the usage scenario information; Determining early warning conditions and early warning strategies according to the management strategy; The step of obtaining the current usage scenario information and determining the management strategy according to the management mode label in the software management portrait and the usage scenario information includes: Acquire current usage scenario information, and match the target scenario with the current usage scenario information in a preset scenario template; Obtaining a management weight factor in the target scenario; Generating a strategy set in a preset strategy set according to the management weight factor; A management policy is determined according to the policy set.

2. The software usage management method according to claim 1, characterized in that: The step of traversing a preset permission management list according to the user login information and determining whether software use management is required upon receiving the user login information comprises: Upon receiving the user login information, obtaining a user identifier corresponding to the user login information; Traversing the preset authority management list according to the user identifier to obtain a traversal result; When the traversal result is a type of user, determining that the user is a management user; When the traversal result is a second-class user, determining that software usage management is required; When the traversal result is a new user, the login features corresponding to the user login information are obtained, and whether software usage management is required is determined in a preset special management list based on the login features, wherein the login features include the user login IP address and / or login MAC address.

3. The software usage management method according to claim 1, characterized in that: The step of determining the target monitoring software according to the management policy and obtaining the usage information corresponding to the target monitoring software includes: Obtaining a current software list, classifying software functions according to the current software list and obtaining classification results; Determine the type of management software according to the management strategy and determine the target monitoring software in combination with the classification result; The usage information corresponding to the target monitoring software is obtained through a preset interface.

4. The software usage management method according to claim 1, characterized in that: The step of performing software usage warning according to the warning strategy and the software usage report comprises: Determine the abnormality level and abnormal item content according to the software usage report; Performing strategy screening in the early warning strategy according to the abnormality level to obtain a screening result; Generate a target early warning strategy based on the abnormal item content and the screening results; Software usage warning is performed according to the target warning strategy.

5. The software usage management method according to claim 1, characterized in that: After the step of performing software usage warning according to the warning strategy and the software usage report, the method further includes: Acquire user operation information, and determine whether the early warning strategy is effective according to the user operation information; If it is determined that the early warning strategy is invalid, obtaining the corresponding management measures in the early warning strategy; The target software is managed through the management measures combined with the user operation information and the user portrait information corresponding to the user login information is updated in the preset authority management list.

6. A software usage management system, characterized in that: The software usage management system comprises: The rights management module is used to, upon receiving user login information, traverse the preset rights management list according to the user login information and determine whether software usage management is required; a policy determination module, for determining a management policy, an early warning condition and an early warning policy according to the user login information; A usage information module, used to determine the target monitoring software according to the management strategy and obtain usage information corresponding to the target monitoring software; A software usage report module, used to generate a software usage report when it is determined that the warning condition is met according to the usage information; A software usage warning module, used for performing software usage warning according to the warning strategy and the software usage report; The policy determination module is further used to determine a target type 1 user according to the user login information, and obtain a software management profile corresponding to the target type 1 user; Determine the management object information according to the management target type label in the software management portrait; Acquire current usage scenario information, and determine a management strategy based on the management mode label in the software management portrait and the usage scenario information; Determining early warning conditions and early warning strategies according to the management strategy; The strategy determination module is further used to obtain current usage scenario information, and match the target scenario in the preset scenario template in combination with the current usage scenario information; Obtaining a management weight factor in the target scenario; Generating a strategy set in a preset strategy set according to the management weight factor; A management policy is determined according to the policy set.

Images