Permission management method and apparatus, device, storage medium, and program product
Determine and manage the permission policies of the target application through the permission configuration interface, which solves the risk of unauthorized use of enterprises or organizations in application use permission management, and realizes unified and standardized management of application permissions and improves efficiency.
Patent Information
- Application Number
- PCT/CN2024/092936
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-16
- Filing Date
- 2024-05-13
- Publication Date
- 2024-11-21
AI Technical Summary
When enterprises or organizations manage the use permissions of applications, they are prone to unauthorized use beyond the predetermined number, resulting in potential risks.
Provide a permission management method and device, determine the target application to be configured through the permission configuration interface, and obtain the permission policy, at least indicating the target scope authorized to be used and the disposal policy outside the target scope, and manage the execution of the target application based on this policy. .
It realizes unified and standardized management of application usage permissions within the organization, improves management efficiency, and reduces risks related to unauthorized use.
Smart Images

Figure CN2024092936_21112024_PF_FP_ABST
Abstract
Description
Rights management method, device, equipment, storage medium and program product
[0001] This application claims priority to the Chinese invention patent application with application number 202310554413.3 filed on May 16, 2023 and entitled “Method, apparatus, device and storage medium for rights management”, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] Example embodiments of the present disclosure generally relate to the field of computers, and more particularly, to methods, apparatuses, devices, computer-readable storage media, and program products for rights management. Background Art
[0003] Managing software or application usage is a critical task within an enterprise or organization. An enterprise or organization may obtain a predetermined number of installation or usage permissions for certain applications. This may result in unauthorized use or installation beyond this limit, potentially posing a risk to the enterprise or organization.
[0004] Summary of the Invention
[0005] In a first aspect of the present disclosure, a method for permissions management is provided. The method comprises: determining a target application to be configured in a permissions configuration interface for managing users and / or devices in a target organization; obtaining a permissions policy to be applied to the target application using the permissions configuration interface, wherein the permissions policy indicates at least a target scope within the target organization that is authorized to use the target application and a policy for handling use of the target application outside the target scope, wherein the target scope includes a set of target users and / or a set of target devices; and managing execution of the target application in the target organization based on the permissions policy.
[0006] In a second aspect of the present disclosure, a device for permission management is provided. The device includes: a determination module configured in a permission configuration interface for managing users and / or devices in a target organization to determine a target application to be configured; an acquisition module configured to use the permission configuration interface to acquire a permission policy to be applied to the target application, the permission policy indicating at least a target scope in the target organization that is authorized to use the target application and a disposal policy for using the target application outside the target scope, the target scope including a group of target users and / or a group of target devices; and a management module configured to manage the execution of the target application in the target organization based on the permission policy.
[0007] In a third aspect of the present disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit. When executed by the at least one processing unit, the instructions cause the device to perform the method of the first aspect.
[0008] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, wherein a computer program is stored on the computer-readable storage medium, and the computer program can be executed by a processor to implement the method of the first aspect.
[0009] In a fifth aspect of the present disclosure, there is provided a computer program product tangibly stored in a computer storage medium and comprising computer executable instructions which, when executed by a device, cause the device to perform the method according to the first aspect.
[0010] It should be understood that the content described in this summary section is not intended to limit the key features or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:
[0012] FIG1 shows a schematic diagram of an example environment in which embodiments according to the present disclosure may be implemented;
[0013] FIG2 shows a flowchart of an example process of rights management according to some embodiments of the present disclosure;
[0014] 3A to 3F illustrate example permission configuration interfaces according to some embodiments of the present disclosure;
[0015] FIG4 shows a schematic structural block diagram of an apparatus for rights management according to some embodiments of the present disclosure; and
[0016] FIG5 shows a block diagram of an electronic device capable of implementing various embodiments of the present disclosure. DETAILED DESCRIPTION
[0017] The following describes embodiments of the present disclosure in more detail with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.
[0018] It should be noted that the titles of any section / subsection provided herein are not limiting. Various embodiments are described throughout this document, and any type of embodiment may be included under any section / subsection. Furthermore, the embodiments described in any section / subsection may be combined in any manner with any other embodiments described in the same section / subsection and / or in different sections / subsections.
[0019] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may be included below. The terms "first", "second", etc. may refer to different or the same objects. Other explicit and implicit definitions may be included below.
[0020] The embodiments of the present disclosure may involve user data, data acquisition and / or use, etc. These aspects shall comply with the corresponding laws, regulations and relevant provisions. In the embodiments of the present disclosure, all data collection, acquisition, processing, processing, forwarding, use, etc. are carried out on the premise that the user is aware of and confirms them. Accordingly, when implementing the various embodiments of the present disclosure, the types, scope of use, and usage scenarios of the data or information that may be involved should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with the relevant laws and regulations. The specific notification and / or authorization method may vary according to the actual situation and application scenario, and the scope of the present disclosure is not limited in this respect.
[0021] If this specification and the solutions in the examples involve the processing of personal information, such processing will be done only with a legitimate basis (such as with the consent of the subject of personal information or as necessary for the performance of a contract) and only within the prescribed or agreed scope. A user's refusal to process personal information other than that required for basic functions will not affect the user's use of basic functions.
[0022] As briefly mentioned above, managing the compliant use of applications within an organization is a critical task for businesses and other organizations. This requires ensuring that members use applications within the authorized scope, which can be challenging.
[0023] The embodiments of the present disclosure propose a scheme for permission management. According to the scheme, the target application to be configured can be determined in the permission configuration interface for managing users and / or devices in the target organization. Furthermore, the permission configuration interface can be used to obtain the permission policy to be applied to the target application. The permission policy at least indicates the target scope of the target organization that is authorized to use the target application and the disposal policy for using the target application outside the target scope. The target scope includes a group of target users and / or a group of target devices. Accordingly, the execution of the target application in the target organization can be managed based on the permission policy.
[0024] In this way, embodiments of the present disclosure can support unified and standardized management of application usage permissions in an organization, thereby improving the efficiency of application permission management and reducing risks associated with unauthorized use.
[0025] Various example implementations of this solution are described in detail below in conjunction with the accompanying drawings.
[0026] Sample Environment
[0027] FIG1 shows a schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented. As shown in FIG1 , the environment 100 may include a management device 110 .
[0028] As described in detail below, the management device 110 can be configured to manage usage permissions for applications 130 within an organization. An "organization" may include a group of multiple users, such as a company, department, or institution. An "application" may include any suitable program product that can be installed and used by a terminal device, and in some scenarios, may also be software.
[0029] For example, the management device 110 can utilize the permission configuration interface 160 provided by the terminal device 120 to implement permission management for the application 130. Such a terminal device 120 may correspond to an electronic device used by an administrator within an organization. It should be understood that although the management device 110 and the terminal device 120 are shown as separate boxes in FIG1 , they may also be implemented in the same electronic device.
[0030] For example, the management device 110 may utilize the permission configuration interface 160 to determine a target scope of the authorization scope, such as a group of devices 140 and / or a group of users 150. Such a permission configuration interface 160 may be used to manage users and / or devices in a target organization.
[0031] Additionally, the management device 110 can also manage handling measures for using the application 130 outside the target scope. For example, the management device 110 can disable the application 130 for users and / or devices in the organization that are not within the target scope based on the configuration information obtained by the permission configuration interface 160.
[0032] The specific process of authority configuration will be described in detail below with reference to FIG2 .
[0033] In some embodiments, the terminal device 120 can be any type of mobile terminal, fixed terminal or portable terminal, including a mobile phone, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a media computer, a multimedia tablet, a personal communication system (PCS) device, a personal navigation device, a personal digital assistant (PDA), an audio / video player, a digital camera / camcorder, a positioning device, a television receiver, a radio broadcast receiver, an e-book device, a gaming device or any combination thereof, including accessories and peripherals of these devices or any combination thereof. The management device 110 can be, for example, various types of computing systems / servers capable of providing computing capabilities, including but not limited to mainframes, edge computing nodes, computing devices in cloud environments, and the like.
[0034] It should be understood that the structure and function of the various elements in the environment 100 are described for illustrative purposes only and do not imply any limitation on the scope of the present disclosure.
[0035] Some example embodiments of the present disclosure will be described below with continued reference to the accompanying drawings.
[0036] Example Process
[0037] FIG2 shows a flow chart of an example process 200 for rights management according to some embodiments of the present disclosure. Process 200 may be implemented at the terminal device 120 (or in combination with the management device 120). Process 200 is described below with reference to FIG1.
[0038] As shown in FIG. 2 , in block 210 , the terminal device 120 determines a target application 130 to be configured using the permission configuration interface 160 for managing users and / or devices in a target organization.
[0039] As shown in FIG. 3A , the terminal device 120 may provide a permission configuration interface 300A as shown in FIG. 3A for a management user within an organization, for example.
[0040] Taking Figure 3A as an example, the terminal device 120 can present a group of candidate applications (for example, candidate application 310-1 to candidate application 310-4, individually or collectively referred to as candidate application 310) in the permission configuration interface 300A, and determine the target application to be configured based on the selection operation of the management user on a group of candidate applications.
[0041] For example, such a set of candidate applications 310 may include a set of preset candidate applications. For example, the terminal device 120 and / or the management device 110 may configure a set of commonly used preset applications in the organization as candidate applications that can be used for management according to the usage needs of the organization.
[0042] Alternatively, such a set of candidate applications 310 may also be determined based on the organization's procurement information and include a set of applications that the organization has already procured.
[0043] In some embodiments, if the application that the management user desires to configure is not in the list, the management user may also trigger the selection of other applications by, for example, operating the add control 305 .
[0044] For example, upon receiving a selection for the add control 305, the terminal device 120 may present, for example, an interface 300B. As shown in FIG3B , in interface 300B, the terminal device 120 may present a set of candidate applications 315 determined based on application installation information within the organization. This application installation information may, for example, be reported by users within the organization, or determined based on information uploaded by user devices within the organization with the users' knowledge and permission. The administrative user may, for example, add these candidate applications 315 to the managed application list shown in FIG3A .
[0045] In some embodiments, the terminal device 120 may further provide the management user with a group of candidate applications determined by the detection. As shown in Figure 3C, the terminal device 120 may further provide an interface 300C as shown in Figure 3C.
[0046] In the interface 300C, the terminal device 120 may provide, for example, a set of candidate applications 320 determined based on real-time reference detection within the organization. Accordingly, the management device 120 may also add such candidate applications to the management application list shown in FIG3A .
[0047] Additionally, in the event that none of the candidate applications above include a target application for desired configuration, the terminal device 120 may further support, for example, managing the target application for desired configuration input by the user. For example, upon receiving a selection for the add entry 325 as shown in FIG3C , the terminal device 120 may present, for example, an interface 300D as shown in FIG3D .
[0048] As shown in Figure 3D, the interface 300D may allow the user to input application description information on the interface 300D. Such application description information may include, for example, the name of the application, the operating system of the application, the BUNDLE ID (bundle identifier) of the application, the version number of the application, etc.
[0049] After completing such application description information, the terminal device 120 may support adding the target application determined based on the input application description information to the management application list as shown in FIG. 3A .
[0050] In this way, the embodiments of the present disclosure can support multi-channel configuration application addition, thereby facilitating unified management of applications within an organization and improving the efficiency of application management.
[0051] Continuing with reference to Figure 2, in box 220, the terminal device 120 uses the permission configuration interface 160 to obtain the permission policy to be applied to the target application 130, wherein the permission policy at least indicates the target scope in the target organization that is authorized to use the target application and the disposal policy for using the target application outside the target scope, and the target scope includes a group of target users and / or a group of target devices.
[0052] 3A , the application 310 - 1 in the management application list is used as an example of a selected target application. The management user can select the target application 310 - 1 as the target application to be managed by, for example, clicking “Open Permission”.
[0053] Furthermore, the terminal device 120 may allow the management user to configure the permissions for the target application in a “per-device authorization” or “per-user authorization” manner.
[0054] Furthermore, the terminal device 120 may present a configuration component 300E as shown in FIG3E . As shown in FIG3E , the terminal device 120 may present a set of candidate devices 335 in the configuration component 300E. Such a set of candidate devices may include, for example, a set of candidate devices preset within the organization, such as a set of devices that the current administrative user has permission to manage.
[0055] Alternatively or additionally, the configuration component 300E may further include a search portal 330, through which the management user may enter a search term to screen or filter candidate devices. For example, such a search term may be associated with device description information of the device, such as the device identifier, the device type, the user corresponding to the device, and the like.
[0056] Further, the configuration component 300E can allow the administrative user to add one or more devices from the candidate devices 335 as target devices authorized to use the target application within the organization.
[0057] In some examples, as shown in Figure 3E, the configuration component 300E can also be used to configure an upper limit on the number of devices within the organization that are allowed to use the target application. Such an upper limit can be determined based on the organization's application purchase information and can be less than or equal to the total purchase amount.
[0058] In some further embodiments, when the management user selects “per user authorization” to configure permissions, the terminal device 120 may, for example, provide a configuration component 300F as shown in FIG3F .
[0059] 3F , the terminal device 120 may present a group of candidate users in the configuration component 300F. Such a group of candidate users may include, for example, a group of candidate users 345 preset within the organization, such as a set of users that the current management user has the authority to manage.
[0060] Alternatively or additionally, the configuration component 300E may further include a search portal 340, through which the administrative user may enter a search term to screen or filter candidate users. For example, such a search term may be associated with user description information of the user, such as the user's ID, the user's role, the user's department, etc.
[0061] Furthermore, the configuration component 300E can allow the administrative user to add one or more devices from the candidate users 345 as target users within the organization who are authorized to use the target application.
[0062] Through the above-discussed approach, the embodiments of the present disclosure can further provide flexibility in application permission management and better match different permission modes of application per-device permission and per-user permission, thereby increasing the scope of application of the solution.
[0063] In some further embodiments, the terminal device 120 may further support managing the handling policy input by the user regarding the use of the target application outside the target range. Continuing with the target application 310 - 1 in FIG. 3A as an example.
[0064] In some embodiments, the terminal device 120 may, for example, adopt a default handling policy when no specific user input is received. Such a default handling policy may be appropriately configured according to organizational needs, for example, to prohibit unauthorized users or devices from using the target application.
[0065] In some embodiments, as shown in FIG3A , the administrative user can also configure permissions for the target application 310-1 by, for example, clicking on the "Disable Software" entry. For example, upon receiving the "Disable Software" selection, the terminal device 110 may determine that the disposal policy selected by the administrative user indicates that the target application is disabled outside the target scope. In this case, even if unauthorized users and / or devices have installed the target application 310-1, they will not be able to launch it.
[0066] In some embodiments, the administrative user may also configure reminders regarding unauthorized use or unauthorized attempts to use the application. For example, the administrative user may configure that when an unauthorized user attempts to launch the target application or attempts to launch the target application on an unauthorized device, the target application will not be launched, and the administrative user may control the device to provide a reminder that the current device and / or current user is not authorized to use the application.
[0067] As another example, the administrative user may also configure a reminder to be generated during the first unauthorized use of a user and / or device. That is, when an unauthorized user attempts to launch a target application or attempts to launch a target application on an unauthorized device, the target application may be launched normally for the first time, and the device may provide a reminder during use that the current device and / or current user is not authorized to use the application and should obtain authorization as soon as possible.
[0068] In some embodiments, a reminder regarding unauthorized use and / or attempted use of the target application outside the target scope may also be generated for the administrative user. For example, a reminder regarding unauthorized use or attempted use within the organization may be provided to the administrative user via appropriate means such as email, office system message, instant messaging, or the like.
[0069] In some other embodiments, as discussed above, the terminal device 120 may also receive a designation of an upper limit on authorized devices and / or authorized users. In some embodiments, the terminal device 120 may also receive a configuration for managing an excess number and / or an excess ratio of management users.
[0070] For example, such excess number and / or excess ratio can be appropriately configured based on the organization's application procurement information, for example, to reduce the risk of usage beyond the scope of procurement. As an example, the administrative user can, for example, configure the upper limit of the number of devices authorized to use the target application within the organization to 100, and can configure the excess ratio to 15% (for example, the organization's procurement quantity is 120). Thus, when the total number of devices authorized for use and unauthorized for use within the organization exceeds 115, a reminder about exceeding the quota can be sent to the administrative user of the target organization through appropriate means such as email, office system message, instant messaging message, etc., so that the administrative user's terminal device displays the reminder. In some examples, such an excess reminder can occur, for example, when the administrative user has not disabled usage outside the target scope.
[0071] Based on this approach, the embodiments of the present disclosure can support detailed configuration of permission policies for target applications, specifying authorized users and / or devices within an organization, and specifying policies for handling unauthorized use. Based on this approach, the embodiments of the present disclosure can greatly reduce the difficulty of application management within an organization and improve management efficiency.
[0072] 2 , in block 230 , the terminal device 120 manages execution of the target application in the target organization based on the permission policy.
[0073] For example, the terminal device 120 can determine the users or devices within the organization that are authorized to use the target application based on the permission policy, and enable the devices within the organization to respond to the permission policy. For example, the device within the organization can allow the user to install or use the target application if it is determined that the device is an authorized device or the logged-in user is an authorized user.
[0074] Conversely, if it is determined that the device is not an authorized device and the logged-in user is not an authorized user, the device within the organization can determine whether to prohibit the user from launching or using the target application based on the permission policy. For example, when the user double-clicks to launch the application, the device may not respond and may generate a reminder that the current device and / or current user is not authorized to use the application. Alternatively, after the application is successfully launched, the device may generate a reminder that authorization is required as soon as possible.
[0075] Through the above process, the embodiments of the present disclosure can provide a unified configuration interface for application permission management within an organization, allowing target applications to be added from multiple sources and managing the use of target applications within the organization through multiple permission policies. As a result, the embodiments of the present disclosure can improve the uniformity of application management and reduce the time cost of application permission management.
[0076] In some further embodiments, with continued reference to FIG. 3A , the permission configuration interface 300A may further provide application statistics information, where the application statistics information indicates a comparison between authorized usage of at least one application within the target organization and the total usage.
[0077] Taking the application 310-2 in FIG3A for which management has been enabled as an example, the information in the column "Permitted / Total" can, for example, indicate a comparison between the number of devices or users authorized by the administrator (e.g., number C) and the total number of devices or users within the organization that have installed or used the application (e.g., number B). In some examples, the permission configuration interface 300A can also directly provide information on the ratio of number C to number B, rather than providing specific numerical values for the two.
[0078] In some embodiments, terminal device 120 may provide risk description information generated based on the comparison results. This risk description information may indicate whether the use of a specific application within the target organization poses a risk of exceeding or not being authorized. For example, if number B is greater than number C, the application may be determined to pose a risk of unauthorized use. Accordingly, permission configuration interface 300A may, for example, indicate that the application may currently pose a risk through a "Software Risk" column.
[0079] In some other embodiments, the terminal device 120 may further provide a purchase suggestion for the application 310 - 2 based on the comparison result. For example, if the number B is greater than the number C, the terminal device 120 may generate a purchase suggestion for additionally purchasing the application 310 - 2 .
[0080] Based on this approach, the embodiments of the present disclosure can also achieve information aggregation for applications to be managed within an organization, thereby further improving the efficiency of application management within the organization.
[0081] Example devices and equipment
[0082] The embodiments of the present disclosure also provide corresponding devices for implementing the above methods or processes.
[0083] 4 shows a schematic structural block diagram of an apparatus 400 for rights management according to certain embodiments of the present disclosure. Apparatus 400 may be implemented as or included in terminal device 120. Each module / component in apparatus 400 may be implemented by hardware, software, firmware, or any combination thereof.
[0084] As shown in Figure 4, the device 400 includes a determination module 410, which is configured to determine the target application to be configured in a permission configuration interface for managing users and / or devices in the target organization; an acquisition module 420, which is configured to use the permission configuration interface to obtain a permission policy to be applied to the target application, the permission policy at least indicating a target scope in the target organization that is authorized to use the target application and a disposal policy for using the target application outside the target scope, the target scope including a group of target users and / or a group of target devices; and a management module 430, which is configured to manage the execution of the target application in the target organization based on the permission policy.
[0085] In some embodiments, the determination module 410 is further configured to: display a group of candidate applications in the permission configuration interface; and receive a selection of a target application from the group of candidate applications.
[0086] In some embodiments, the group of candidate applications includes at least one of the following: a preset first group of applications, a second group of applications determined based on application installation information, and a third group of applications determined based on real-time application detection.
[0087] In some embodiments, the determination module 410 is further configured to: obtain application description information input in the permission configuration interface; and determine the target application based on the application description information.
[0088] In some embodiments, the acquisition module 420 is further configured to: provide a first configuration component corresponding to the device configuration in the permission configuration interface, the first configuration component displaying a group of candidate devices; and determine the target scope in the target organization that is authorized to use the target application based on the selection of at least one device from the group of candidate devices.
[0089] In some embodiments, the group of candidate devices includes: a first group of candidate devices preset in the target organization, a second group of candidate devices matching a first search term, and the first search term is associated with device description information of the device.
[0090] In some embodiments, the acquisition module 420 is further configured to: provide a second configuration component corresponding to the user configuration in the permission configuration interface, and the first configuration component displays a group of candidate users; and based on the selection of at least one user from the group of candidate users, determine the target scope in the target organization that is authorized to use the target application.
[0091] In some embodiments, the group of candidate users includes: a first group of candidate users preset in the target organization, a second group of candidate users matching a second search term, and the second search term is associated with user description information of the user.
[0092] In some embodiments, the acquisition module 420 is further configured to: utilize the permission configuration interface to receive input regarding a handling policy for use of the target application outside the target scope, wherein the handling policy includes at least one of the following: a first handling policy indicating that the target application is disabled outside the target scope; a second handling policy indicating that a first reminder is generated for unauthorized use and / or attempted use of the target application outside the target scope, so that a first device associated with the unauthorized use and / or attempted use displays the first reminder; and / or, a third handling policy indicating that a second reminder is generated for unauthorized use exceeding a predetermined number so that a terminal device associated with an administrative user of the target organization displays a second reminder, wherein the predetermined number is configured using the permission configuration interface.
[0093] In some embodiments, the apparatus 400 further includes a display module configured to: display application statistics information in the permission configuration interface, where the application statistics information indicates a comparison result between authorized usage of at least one application within the target organization and all usage.
[0094] In some embodiments, the presentation module is further configured to provide risk description information for at least one application, where the risk description information is generated based on the comparison result.
[0095] FIG5 shows a block diagram of an electronic device 500 in which one or more embodiments of the present disclosure may be implemented. It should be understood that the electronic device 500 shown in FIG5 is merely exemplary and should not be construed as limiting the functionality and scope of the embodiments described herein. The electronic device 500 shown in FIG5 can be used to implement the terminal device 120 and / or the management device 110 of FIG1 .
[0096] As shown in FIG5 , electronic device 500 is a general-purpose electronic device. Components of electronic device 500 may include, but are not limited to, one or more processors or processing units 510, memory 520, storage device 530, one or more communication units 540, one or more input devices 550, and one or more output devices 560. Processing unit 510 may be a real or virtual processor and is capable of performing various processes according to programs stored in memory 520. In a multi-processor system, multiple processing units execute computer-executable instructions in parallel to enhance the parallel processing capabilities of electronic device 500.
[0097] The electronic device 500 typically includes a plurality of computer storage media. Such media can be any accessible media that can be obtained by the electronic device 500, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 520 can be a volatile memory (e.g., a register, a cache, a random access memory (RAM)), a non-volatile memory (e.g., a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 530 can be a removable or non-removable medium and can include a machine-readable medium, such as a flash drive, a disk, or any other medium that can be used to store information and / or data (e.g., training data for training) and can be accessed within the electronic device 500.
[0098] The electronic device 500 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown in FIG. 5 , a disk drive for reading from or writing to a removable, non-volatile disk (e.g., a “floppy disk”) and an optical drive for reading from or writing to a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to a bus (not shown) by one or more data media interfaces. The memory 520 may include a computer program product 525 having one or more program modules configured to perform various methods or actions of various embodiments of the present disclosure.
[0099] The communication unit 540 enables communication with other electronic devices via a communication medium. Additionally, the functions of the components of the electronic device 500 can be implemented in a single computing cluster or multiple computing machines that can communicate via a communication connection. Thus, the electronic device 500 can operate in a networked environment using a logical connection with one or more other servers, a network personal computer (PC), or another network node.
[0100] Input device 550 may be one or more input devices, such as a mouse, keyboard, or trackball. Output device 560 may be one or more output devices, such as a display, a speaker, or a printer. Electronic device 500 may also communicate with one or more external devices (not shown) via communication unit 540 as needed, such as a storage device, a display device, or the like, with one or more devices that allow a user to interact with electronic device 500, or with any device that allows electronic device 500 to communicate with one or more other electronic devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface (not shown).
[0101] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are stored, wherein the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above.
[0102] Various aspects of the present disclosure are described herein with reference to flowcharts and / or block diagrams of methods, apparatuses, devices, and computer program products implemented according to the present disclosure. It should be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.
[0103] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, such that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device is generated that implements the functions / actions specified in one or more blocks in the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, where these instructions cause the computer, programmable data processing device, and / or other device to operate in a specific manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing various aspects of the functions / actions specified in one or more blocks in the flowchart and / or block diagram.
[0104] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.
[0105] The flow charts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the systems, methods and computer program products according to multiple implementations of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a part for a module, program segment or instruction, and a part for a module, program segment or instruction comprises one or more executable instructions for realizing the logical function of the specification. In some alternative implementations, the functions marked in the box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.
[0106] While various implementations of the present disclosure have been described above, the foregoing description is intended to be illustrative, not exhaustive, and not limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is selected to best explain the principles of the implementations, their practical applications, or improvements to existing technologies, or to enable others skilled in the art to understand the various implementations disclosed herein.
Claims
1. A method for rights management, comprising: In a permission configuration interface for managing users and / or devices in a target organization, determining a target application to be configured; Acquire a permission policy to be applied to the target application by using the permission configuration interface, the permission policy at least indicating a target scope in the target organization that is authorized to use the target application and a disposal policy for using the target application outside the target scope, the target scope including a group of target users and / or a group of target devices; as well as Based on the permission policy, the execution of the target application in the target organization is managed.
2. The method according to claim 1, wherein determining the target application to be configured comprises: Displaying a group of candidate applications in the permission configuration interface; as well as A selection of the target application from the set of candidate applications is received.
3. The method according to claim 2, wherein the set of candidate applications includes at least one of the following: The first set of preset applications, A second group of applications determined based on the application installation information, A third group of applications is determined based on real-time application detection.
4. The method according to claim 1, wherein determining the target application to be configured comprises: In the permission configuration interface, obtaining input application description information; as well as Based on the application description information, the target application is determined.
5. The method according to claim 1, wherein using the permission configuration interface to obtain the permission policy to be applied to the target application comprises: Providing a first configuration component corresponding to the device configuration in the permission configuration interface, wherein the first configuration component displays a group of candidate devices; as well as Based on the selection of at least one device from the group of candidate devices, the target scope in the target organization that is authorized to use the target application is determined.
6. The method of claim 5, wherein the set of candidate devices comprises: A first group of candidate devices preset in the target organization, A second group of candidate devices matching the first search term, wherein the first search term is associated with device description information of the device.
7. The method according to claim 1, wherein using the permission configuration interface to obtain the permission policy to be applied to the target application comprises: Providing a second configuration component corresponding to the user configuration in the permission configuration interface, wherein the first configuration component displays a group of candidate users; as well as Based on the selection of at least one user from the group of candidate users, the target scope in the target organization that is authorized to use the target application is determined.
8. The method of claim 7, wherein the set of candidate users comprises: A first group of candidate users preset in the target organization, A second group of candidate users matching a second search term, wherein the second search term is associated with user description information of the user.
9. The method according to claim 1, wherein using the permission configuration interface to obtain the permission policy to be applied to the target application comprises: receiving, by using the permission configuration interface, an input of the handling policy for using the target application outside the target scope, The treatment strategy includes at least one of the following: A first handling policy indicating that the target application is disabled outside the target range; A second handling policy instructs to generate a first reminder for unauthorized use and / or attempted use of the target application outside the target range, so that a first device associated with the unauthorized use and / or attempted use displays the first reminder; A third handling policy indicates generating a second reminder for unauthorized use exceeding a predetermined number, so that a terminal device associated with the management user of the target organization displays the second reminder, wherein the predetermined number is configured using the permission configuration interface.
10. The method according to claim 1, further comprising: Display application statistics in the permission configuration interface, the application statistics indicating the authorized use and total use of at least one application in the target organization The comparison results.
11. The method according to claim 10, further comprising: Providing risk description information for the at least one application, the risk description information being generated based on the comparison result.
12. A device for rights management, comprising: A determination module configured to determine a target application to be configured in a permission configuration interface for managing users and / or devices in a target organization; an acquisition module, configured to acquire, by using the permission configuration interface, a permission policy to be applied to the target application, the permission policy at least indicating a target scope in a target organization that is authorized to use the target application and a disposal policy for using the target application outside the target scope, the target scope including a group of target users and / or a group of target devices; as well as The management module is configured to manage the execution of the target application in the target organization based on the permission policy.
13. An electronic device comprising: at least one processing unit; as well as At least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method according to any one of claims 1 to 11 when executed by the at least one processing unit.
14. A computer-readable storage medium having a computer program stored thereon, wherein the computer program can be executed by a processor to implement the method according to any one of claims 1 to 11.
15. A computer program product tangibly stored in a computer storage medium and comprising computer executable instructions which, when executed by a device, cause the device to perform the method according to any one of claims 1 to 11.
Citation Information
Patent Citations
System and method for managing software
CN103400066A
Terminal software management platform
CN111124472A
Authority management method and device, electronic equipment and storage medium
CN114297590A
Authority management method and device, equipment and storage medium
CN116561716A
Method of managing a software item on a managed computer system
US7627902B1
