CN110955869A - Terminal software authority management method and device, terminal and storage medium - Google Patents
Terminal software authority management method and device, terminal and storage medium Download PDFInfo
- Publication number
- CN110955869A CN110955869A CN201811126562.5A CN201811126562A CN110955869A CN 110955869 A CN110955869 A CN 110955869A CN 201811126562 A CN201811126562 A CN 201811126562A CN 110955869 A CN110955869 A CN 110955869A
- Authority
- CN
- China
- Prior art keywords
- terminal
- software
- identification information
- information
- unique identification
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims description 87
- 238000000034 method Methods 0.000 claims abstract description 33
- 238000004590 computer program Methods 0.000 claims description 21
- 238000000605 extraction Methods 0.000 claims description 11
- 230000006870 function Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 239000000284 extract Substances 0.000 description 4
- 238000001514 detection method Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/12—Protecting executable software
- G06F21/121—Restricting unauthorised execution of programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/101—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM] by binding digital rights to specific entities
- G06F21/1011—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM] by binding digital rights to specific entities to devices
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Multimedia (AREA)
- Technology Law (AREA)
- Computer Hardware Design (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Storage Device Security (AREA)
Abstract
The application relates to a method, a device, a terminal and a storage medium for managing terminal software authority, wherein the method comprises the following steps: acquiring unique identification information of a terminal; the terminal unique identification information is a unique identity of the terminal; extracting software permission information corresponding to the acquired terminal unique identification information from the stored data; the software permission information and the terminal unique identification information are stored in the storage data in advance, and the software permission information and the terminal unique identification information have a preset binding relationship; and setting software permission according to the extracted software permission information. The software in different terminals is subjected to authority management according to the unique identification information of the terminal, the operation is simple, convenient and reliable, third-party encryption software is not required, the software is not easy to crack, and the software encryption safety is improved.
Description
Technical Field
The present application relates to the technical field of rights authentication management, and in particular, to a method, an apparatus, a terminal and a storage medium for managing rights of terminal software.
Background
With the development of science and technology and the continuous progress of equipment, software is installed on a terminal to perform corresponding function operation, so that the software is more and more widely used in daily work and life of people, and the problem of how to ensure the use safety of the installed software is very important.
The traditional software authority management mode is to protect the software encryption externally by means of an encryption tool, such as third-party software like a dongle, and if the encryption is broken, the software functions can still be used arbitrarily. The traditional software authority management mode has the defect of low encryption security.
Disclosure of Invention
In view of the above, it is desirable to provide a method, an apparatus, a terminal and a storage medium for managing software rights of a terminal, which can improve security of software encryption.
A terminal software authority management method comprises the following steps:
acquiring unique identification information of a terminal; the terminal unique identification information is a unique identity of the terminal;
extracting software permission information corresponding to the acquired terminal unique identification information from the stored data; the storage data is stored with software permission information and terminal unique identification information in advance, and the software permission information and the terminal unique identification information have a preset binding relationship;
and setting software permission according to the extracted software permission information.
According to the terminal software permission management method, the permission management is carried out on the software in the terminal according to the unique identification information of the terminal, the operation is simple, convenient and reliable, the third party encryption software is not needed, the software cannot be easily cracked, and the software encryption safety is improved.
In one embodiment, the terminal unique identification information includes a Media Access Control (MAC) address of the terminal, or the terminal unique identification information includes a Central Processing Unit (CPU) information and a MAC address of the terminal.
And the software permission information is bound according to the unique MAC address of the terminal or the combination of the MAC address of the terminal and the CPU information, so that the software permission management corresponding to different terminals is realized, and the operation reliability is high.
In one embodiment, after the obtaining of the unique terminal identification information, before extracting the software permission information corresponding to the obtained unique terminal identification information from the stored data of the software permission information and the unique terminal identification information, the method further includes:
detecting whether the acquired unique terminal identification information exists in the stored data;
and if so, extracting the software permission information corresponding to the acquired unique terminal identification information from the stored data of the software permission information and the unique terminal identification information.
If the terminal unique identification information is detected to be stored and acquired, the terminal is indicated to have the software use right, and corresponding software permission information is extracted according to the terminal unique identification information. When the terminal is determined to have the software use right, corresponding software permission information is extracted to set the software permission, and if the terminal does not have the software use right, information extraction is not needed, so that the operation convenience is improved.
In an embodiment, if there is no acquired unique terminal identification information in the stored data of the software permission information and the unique terminal identification information, the method may further include:
and outputting the software permission setting failure information.
When the acquired terminal unique identification information is not stored, the software permission setting failure information is output to inform the user, so that the operation convenience of software permission management is improved.
In one embodiment, before the obtaining of the terminal unique identification information, the method further includes the following steps:
receiving and storing software permission information and terminal unique identification information which are sent by permission management equipment and have a preset binding relationship; and the authority management equipment is used for establishing a binding relationship between the unique terminal identification information and the corresponding software authority information.
And receiving the terminal unique identification information with the preset binding relationship and the software permission information in advance for storage so as to perform software permission management operation in the following.
In an embodiment, before receiving and storing the software permission information and the terminal unique identification information with the preset binding relationship, which are sent by the permission management device, the method further includes:
and sending terminal unique identification information to the authority management equipment, wherein the terminal unique identification information is used for establishing a binding relationship between the authority management equipment and the software authority information and encrypting the binding relationship.
And sending the terminal unique identification information to the authority management equipment so that the authority management equipment can establish a binding relationship between the software authority information and the terminal unique identification information and encrypt the binding relationship, thereby reducing the risk of data leakage and improving the safety of software authority management.
In one embodiment, the software permission information includes software usage permission and a software usage validity period.
The use authority and the use validity period of the software in the terminal are managed simultaneously through the terminal unique identification information of the terminal, and the convenience of software authority management is improved.
A terminal software right management apparatus, comprising:
the information acquisition module is used for acquiring the unique identification information of the terminal; the terminal unique identification information is a unique identity of the terminal;
the information extraction module is used for extracting software permission information corresponding to the acquired terminal unique identification information from the stored data; the storage data is stored with software permission information and terminal unique identification information in advance, and the software permission information and the terminal unique identification information have a preset binding relationship;
and the permission setting module is used for setting the software permission according to the extracted software permission information.
According to the terminal software permission management device, the permission management is carried out on the software in the terminal according to the unique identification information of the terminal, the operation is simple, convenient and reliable, the third party encryption software is not needed, the software cannot be easily cracked, and the software encryption safety is improved.
A terminal comprising a memory and a processor, the memory storing a computer program, the processor when executing the computer program implementing the steps of: acquiring unique identification information of a terminal; the terminal unique identification information is a unique identity of the terminal; extracting software permission information corresponding to the acquired terminal unique identification information from the stored data; the software permission information and the terminal unique identification information are stored in the storage data in advance, and the software permission information and the terminal unique identification information have a preset binding relationship; and setting software permission according to the extracted software permission information.
According to the terminal, the authority management is carried out on the software in the terminal according to the unique identification information of the terminal, the operation is simple, convenient and reliable, the third party encryption software is not needed, the software is not easy to crack, and the software encryption safety is improved.
A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of: acquiring unique identification information of a terminal; the terminal unique identification information is a unique identity of the terminal; extracting software permission information corresponding to the acquired terminal unique identification information from the stored data; the storage data is stored with software permission information and terminal unique identification information in advance, and the software permission information and the terminal unique identification information have a preset binding relationship; and setting software permission according to the extracted software permission information.
The computer readable storage medium manages the authority of the software in the terminal according to the unique identification information of the terminal, is simple, convenient and reliable to operate, does not need to encrypt the software by a third party, is not easy to crack, and improves the encryption safety of the software.
Drawings
FIG. 1 is a flowchart of a method for managing terminal software rights in an embodiment;
FIG. 2 is a flowchart of a method for rights management of terminal software in another embodiment;
FIG. 3 is a block diagram of a terminal software rights management device according to an embodiment;
FIG. 4 is a block diagram of a terminal software rights management device in another embodiment;
FIG. 5 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
In one embodiment, a method for managing software permission of a terminal is provided, which is suitable for setting software permission of the terminal. As shown in fig. 1, the method includes:
step S130: and acquiring the unique identification information of the terminal.
The terminal unique identification information is the unique identity of the terminal. Specifically, the terminal may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and when a user installs software in the terminal, the user needs to set the authority of the software. The unique terminal identification information may be acquired after the permission setting starting signal is detected, or the unique terminal identification information may be acquired when a user is detected to install new software or the user clicks and starts software to be used, and the unique terminal identification information is used as a basis for subsequent permission setting on the software. The method for obtaining the unique identification information of the terminal is not unique, and the unique identification information of the terminal can be obtained by directly detecting the identification information of the terminal or reading the stored identification information from a memory of the terminal.
The specific type of the terminal unique identification information is not unique, and in one embodiment, the terminal unique identification information includes a MAC address of the terminal, or the terminal unique identification information includes the MAC address of the terminal and CPU information. The CPU information may be a CPU model, etc. And the software permission information is bound according to the unique MAC address of the terminal or the combination of the MAC address of the terminal and the CPU information, so that the software permission management corresponding to different terminals is realized, and the operation reliability is high.
Step S150: and extracting software permission information corresponding to the acquired terminal unique identification information from the stored data.
The software permission information and the terminal unique identification information are stored in the storage data in advance, and the software permission information and the terminal unique identification information have a preset binding relationship. It can be understood that, if the terminal needs to set the permissions of a plurality of pieces of software, the terminal may pre-store the corresponding relationship between the unique identification information of the terminal and the software permission information for different pieces of software. For example, the terminal stores the corresponding relationship between the authority information of the software a and the unique terminal identification information, the corresponding relationship between the authority information of the software B and the unique terminal identification information, and the corresponding relationship between the authority information of the software C and the unique terminal identification information in advance, and when the authority of the software a, the software B, and the software C needs to be set, the corresponding authority information is found according to the corresponding relationship between the authority information of each software and the unique terminal identification information, so that the authority information is used as the terminal to perform authority management on the software a, the software B, and the software C respectively. If the terminal only needs to apply for the authority of one software, the terminal only stores the corresponding relation between the authority information of the software and the unique terminal identification information, and after the unique terminal identification information is obtained, the software authority information corresponding to the unique terminal identification information is directly found according to the stored corresponding relation.
Specifically, if the unique identification information of the terminal only includes the MAC address, the terminal stores the correspondence between the MAC address and the software permission information in the database in advance, and directly extracts the corresponding software permission information after knowing the MAC address of the terminal. If the unique terminal identification information includes the MAC address and the CPU information of the terminal, the terminal may store a correspondence between different combinations of the MAC address and the CPU information and the software permission information in the database. And after the MAC address and the CPU information of the terminal are known, finding out corresponding software permission information according to the combination relationship of the MAC address and the CPU information.
Step S160: and setting software permission according to the extracted software permission information.
And after the terminal extracts the software authority information corresponding to the unique identification information of the terminal, managing the software authority according to the software authority information. The specific type of the software permission information is not unique, and in one embodiment, the software permission information may specifically include software usage permission and a software usage validity period. The use authority and the use validity period of the software in the terminal are managed simultaneously through the terminal unique identification information of the terminal, and the convenience of software authority management is improved.
Taking computer use test software as an example, when software with certain authority needs to be encrypted and limited, corresponding use authority and use date are obtained according to the MAC address and the CPU information of the computer, and a computer user with the MAC address can only use the related functions of opening the authority. Such as: a certain test software can manually test the computer with the authority of 1, the computer with the authority of 2 can realize semi-automation, and the computer with the authority of 3 can realize full-automation; the terminal software permission management method ensures the functions of certain encryption of the software and different functions distributed according to the permission. Computers without the MAC address in the database cannot use the software, and certain application value is provided for software encryption and authority distribution.
In one embodiment, as shown in fig. 2, before step S130, the method may further include step S120.
Step S120: and receiving and storing the software permission information with the preset binding relationship and the unique terminal identification information which are sent by the permission management equipment.
And the authority management equipment is used for establishing a binding relationship between the unique terminal identification information and the corresponding software authority information. The right management device may be specifically a management terminal or a server, the management terminal may be a personal computer, a notebook computer, a smart phone, or a tablet computer, and the server may be implemented by an independent server or a server cluster formed by a plurality of servers. The management personnel can collect the unique identification information of different terminals through the authority management equipment, establish the binding relationship between the unique identification information of the terminals and the software authority information according to the software use authority allowed by each terminal and issue the binding relationship to the terminals for storage. The terminal receives and stores the terminal unique identification information and the software permission information with the preset binding relationship in advance so as to perform software permission management operation in the following.
Further, in one embodiment, before step S120, the method further comprises step S110.
Step S110: and sending the unique identification information of the terminal to the authority management equipment.
And the terminal unique identification information is used for establishing a binding relationship between the authority management equipment and the software authority information and encrypting the binding relationship. And the administrator collects the unique identification information of each terminal through the authority management equipment, binds the unique identification information with the software authority information, stores the unique identification information in the database file, encrypts the database file, and then issues the encrypted database file to a position appointed by the terminal for storage so that the terminal can set the authority of the installed software through the stored database file.
And sending the terminal unique identification information to the authority management equipment so that the authority management equipment can establish a binding relationship between the software authority information and the terminal unique identification information and encrypt the binding relationship, thereby reducing the risk of data leakage and improving the safety of software authority management. The encryption mode is not unique, and in this embodiment, the rights management device performs MD5(MD5Message-Digest Algorithm, MD5Message Digest Algorithm) encryption on the bound software rights information and the terminal unique identification information.
In one embodiment, with continued reference to fig. 2, after step S130, and before step S150, the method further includes step S140.
Step S140: and detecting whether the acquired unique terminal identification information exists in the stored data. If yes, go to step S150.
If the terminal detects that the terminal unique identification information is stored and acquired, the terminal is indicated to have the software use right, and corresponding software permission information is extracted according to the terminal unique identification information. When the terminal is determined to have the software use right, corresponding software permission information is extracted to set the software permission, and if the terminal does not have the software use right, information extraction is not needed, so that the operation convenience is improved.
Further, in an embodiment, if the acquired unique terminal identification information does not exist in the stored data, the method further includes step S170.
Step S170: and outputting the software permission setting failure information. If the terminal does not store the acquired terminal unique identification information, the terminal does not have the software use permission, and the software permission setting failure information is output to inform the user, for example, the user can be informed to perform terminal registration, so that the terminal has the permission to use the software.
When the acquired terminal unique identification information is not stored, the software permission setting failure information is output to inform the user, so that the operation convenience of software permission management is improved. The specific way of outputting the software permission setting failure information is not unique, and can be one or more of controlling a display screen to display preset information, controlling a loudspeaker to sound or controlling an alarm lamp to give an alarm.
In order to better understand the above terminal software permission management method, the following uses the terminal as a computer, and performs a detailed explanation of software permission setting according to the MAC address of the computer.
The user of the computer sends the MAC address of the computer to the authority management equipment, an administrator using the authority management equipment binds the MAC address and the related authority attributes one by one and stores the MAC address and the related authority attributes into the database file, the database file is encrypted by using the MD5 and is issued to the computer to be provided for the user, and the user places the database file at a designated computer position. After a user starts software on a computer, the software can automatically go to a designated path to inquire a database file and analyze the database file, if an MAC address of the computer is stored in the database file, the computer is authorized, and meanwhile, the use permission information corresponding to the computer with the MAC address is obtained, and the authorized computer can use the software and related permissions, so that the functions of encryption and permission allocation are achieved through the method.
According to the terminal software permission management method, the permission management is carried out on the software in different terminals according to the unique identification information of the terminals, the operation is simple, convenient and reliable, the third party encryption software is not needed, the software cannot be easily cracked, and the software encryption safety is improved.
It should be understood that although the various steps in the flow charts of fig. 1-2 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 1-2 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternating with other steps or at least some of the sub-steps or stages of other steps.
In one embodiment, a terminal software rights management device is provided, as shown in fig. 3, including an information acquisition module 130, an information extraction module 150, and a rights setting module 160.
The information obtaining module 130 is configured to obtain the terminal unique identification information.
The terminal unique identification information is the unique identity of the terminal. The terminal may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices. When a user installs software in a terminal, the authority of the software needs to be set. The unique terminal identification information may be acquired after the permission setting starting signal is detected, or the unique terminal identification information may be acquired when a user is detected to install new software or the user clicks and starts software to be used, and the unique terminal identification information is used as a basis for subsequent permission setting on the software. The specific type of the terminal unique identification information is not unique, and in one embodiment, the terminal unique identification information includes a MAC address of the terminal, or the terminal unique identification information includes the MAC address of the terminal and CPU information.
The information extraction module 150 is configured to extract software permission information corresponding to the acquired terminal unique identification information from the stored data.
The software permission information and the terminal unique identification information are stored in the storage data in advance, and the software permission information and the terminal unique identification information have a preset binding relationship. It can be understood that, if the terminal needs to set the permissions of a plurality of pieces of software, the terminal may pre-store the corresponding relationship between the unique identification information of the terminal and the software permission information for different pieces of software. When the authority of different software needs to be set, corresponding authority information is found according to the corresponding relation between the authority information of each software and the unique identification information of the terminal, so that the authority information is used as the authority management of each software by the terminal. If the terminal only needs to apply for the authority of one software, the terminal only stores the corresponding relation between the authority information of the software and the unique terminal identification information, and after the unique terminal identification information is obtained, the software authority information corresponding to the unique terminal identification information is directly found according to the stored corresponding relation.
Specifically, if the terminal unique identification information only includes the MAC address, the corresponding relationship between the MAC address and the software permission information is established in advance for storage, and after the MAC address of the terminal is known, the information extraction module 150 directly extracts the corresponding software permission information. If the unique terminal identification information includes the MAC address and the CPU information of the terminal, the corresponding relationship between the combination of different MAC addresses and CPU information and the software permission information may be stored in the database. After the MAC address and the CPU information of the terminal are known, the information extraction module 150 finds corresponding software permission information according to a combination relationship of the MAC address and the CPU information.
The permission setting module 160 is configured to perform software permission setting according to the extracted software permission information.
After extracting the software permission information corresponding to the terminal unique identification information, the permission setting module 160 performs software permission setting according to the extracted software permission information. In one embodiment, the software permission information may specifically include software usage permission and a software usage validity period. The use authority and the use validity period of the software in the terminal are managed simultaneously through the terminal unique identification information of the terminal, and the convenience of software authority management is improved.
In one embodiment, as shown in FIG. 4, the apparatus may further include a data import module 120.
The data importing module 120 is configured to receive and store the software permission information and the terminal unique identification information with a preset binding relationship, which are sent by the permission management device, before the information obtaining module 130 obtains the terminal unique identification information. And the authority management equipment is used for establishing a binding relationship between the unique terminal identification information and the corresponding software authority information. The terminal receives and stores the terminal unique identification information and the software permission information with the preset binding relationship in advance so as to perform software permission management operation in the following.
Further, in one embodiment, the apparatus may also include an information upload module 110. The information uploading module 110 is configured to send the terminal unique identification information to the rights management device before the data importing module 120 receives and stores the software rights information and the terminal unique identification information that are sent by the rights management device and have a preset binding relationship.
And the terminal unique identification information is used for establishing a binding relationship between the authority management equipment and the software authority information and encrypting the binding relationship. And sending the terminal unique identification information to the authority management equipment so that the authority management equipment can establish a binding relationship between the software authority information and the terminal unique identification information and encrypt the binding relationship, thereby reducing the risk of data leakage and improving the safety of software authority management. In this embodiment, the rights management device performs MD5 encryption on the bound software rights information and the terminal unique identification information.
In one embodiment, with continued reference to fig. 4, the apparatus may further include an information detection module 140. The information detection module 140 is configured to detect whether the acquired unique terminal identification information exists in the stored data after the information acquisition module 130 acquires the unique terminal identification information and before the information extraction module 150 extracts the software permission information corresponding to the acquired unique terminal identification information from the stored data. If yes, the control information extraction module 150 extracts software permission information corresponding to the acquired terminal unique identification information from the stored data.
If the terminal unique identification information is detected to be stored and acquired, the terminal is indicated to have the software use right, and corresponding software permission information is extracted according to the terminal unique identification information. When the terminal is determined to have the software use right, corresponding software permission information is extracted to set the software permission, and if the terminal does not have the software use right, information extraction is not needed, so that the operation convenience is improved.
Further, in an embodiment, if the acquired unique terminal identification information does not exist in the stored data, the information detection module 140 further outputs the software permission setting failure information. When the acquired terminal unique identification information is not stored, the software permission setting failure information is output to inform the user, so that the operation convenience of software permission management is improved. The specific way of outputting the software permission setting failure information is not unique, and can be one or more of controlling a display screen to display preset information, controlling a loudspeaker to sound or controlling an alarm lamp to give an alarm.
According to the terminal software permission management device, the permission management is carried out on the software in different terminals according to the unique identification information of the terminals, the operation is simple, convenient and reliable, the third party encryption software is not needed, the software cannot be easily cracked, and the software encryption safety is improved.
For specific limitations of the terminal software right management device, reference may be made to the above limitations of the terminal software right management method, which is not described herein again. The modules in the terminal software right management device can be wholly or partially realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as shown in fig. 5. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a terminal software rights management method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
Those skilled in the art will appreciate that the architecture shown in fig. 5 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, there is provided a terminal comprising a memory and a processor, the memory storing a computer program, the processor implementing the following steps when executing the computer program: acquiring unique identification information of a terminal; the terminal unique identification information is a unique identity of the terminal; extracting software permission information corresponding to the acquired terminal unique identification information from the stored data; the software permission information and the terminal unique identification information are stored in the storage data in advance, and the software permission information and the terminal unique identification information have a preset binding relationship; and setting software permission according to the extracted software permission information.
In one embodiment, the processor, when executing the computer program, further performs the steps of: and detecting whether the acquired unique terminal identification information exists in the stored data.
In one embodiment, the processor, when executing the computer program, further performs the steps of: and outputting the software permission setting failure information.
In one embodiment, the processor, when executing the computer program, further performs the steps of: receiving and storing software permission information and terminal unique identification information which are sent by permission management equipment and have a preset binding relationship; and the authority management equipment is used for establishing a binding relationship between the unique terminal identification information and the corresponding software authority information.
In one embodiment, the processor, when executing the computer program, further performs the steps of: and sending the terminal unique identification information to the authority management equipment, wherein the terminal unique identification information is used for establishing a binding relationship between the authority management equipment and the software authority information and encrypting the binding relationship.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: acquiring unique identification information of a terminal; the terminal unique identification information is a unique identity of the terminal; extracting software permission information corresponding to the acquired terminal unique identification information from the stored data; the software permission information and the terminal unique identification information are stored in the storage data in advance, and the software permission information and the terminal unique identification information have a preset binding relationship; and setting software permission according to the extracted software permission information.
In one embodiment, the computer program when executed by the processor further performs the steps of: and detecting whether the acquired unique terminal identification information exists in the stored data.
In one embodiment, the computer program when executed by the processor further performs the steps of: and outputting the software permission setting failure information.
In one embodiment, the computer program when executed by the processor further performs the steps of: receiving and storing software permission information and terminal unique identification information which are sent by permission management equipment and have a preset binding relationship; and the authority management equipment is used for establishing a binding relationship between the unique terminal identification information and the corresponding software authority information.
In one embodiment, the computer program when executed by the processor further performs the steps of: and sending the terminal unique identification information to the authority management equipment, wherein the terminal unique identification information is used for establishing a binding relationship between the authority management equipment and the software authority information and encrypting the binding relationship.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A terminal software authority management method is characterized by comprising the following steps:
acquiring unique identification information of a terminal; the terminal unique identification information is a unique identity of the terminal;
extracting software permission information corresponding to the acquired terminal unique identification information from the stored data; the storage data is stored with software permission information and terminal unique identification information in advance, and the software permission information and the terminal unique identification information have a preset binding relationship;
and setting software permission according to the extracted software permission information.
2. The method according to claim 1, wherein the terminal unique identification information comprises a MAC address of the terminal, or the terminal unique identification information comprises the MAC address of the terminal and CPU information.
3. The method according to claim 1, wherein after the obtaining of the unique terminal identification information, before extracting the software permission information corresponding to the obtained unique terminal identification information from the stored data of the software permission information and the unique terminal identification information, the method further comprises:
detecting whether the acquired unique terminal identification information exists in the stored data;
and if so, extracting the software permission information corresponding to the acquired unique terminal identification information from the stored data of the software permission information and the unique terminal identification information.
4. The method of claim 3, wherein if the acquired unique terminal identification information does not exist in the stored data of the software permission information and the unique terminal identification information, further comprising:
and outputting the software permission setting failure information.
5. The method according to claim 1, wherein before obtaining the terminal unique identification information, the method further comprises the following steps:
receiving and storing software permission information and terminal unique identification information which are sent by permission management equipment and have a preset binding relationship; and the authority management equipment is used for establishing a binding relationship between the unique terminal identification information and the corresponding software authority information.
6. The method according to claim 5, wherein before receiving and storing the software permission information and the terminal unique identification information with the preset binding relationship, which are sent by the permission management device, the method further comprises:
and sending terminal unique identification information to the authority management equipment, wherein the terminal unique identification information is used for establishing a binding relationship between the authority management equipment and the software authority information and encrypting the binding relationship.
7. The method according to any one of claims 1 to 6, wherein the software permission information includes software usage permission and a software usage validity period.
8. A terminal software right management apparatus, comprising:
the information acquisition module is used for acquiring the unique identification information of the terminal; the terminal unique identification information is a unique identity of the terminal;
the information extraction module is used for extracting software permission information corresponding to the acquired terminal unique identification information from the stored data; the storage data is stored with software permission information and terminal unique identification information in advance, and the software permission information and the terminal unique identification information have a preset binding relationship;
and the permission setting module is used for setting the software permission according to the extracted software permission information.
9. A terminal comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method according to any of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811126562.5A CN110955869A (en) | 2018-09-26 | 2018-09-26 | Terminal software authority management method and device, terminal and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811126562.5A CN110955869A (en) | 2018-09-26 | 2018-09-26 | Terminal software authority management method and device, terminal and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110955869A true CN110955869A (en) | 2020-04-03 |
Family
ID=69966226
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811126562.5A Pending CN110955869A (en) | 2018-09-26 | 2018-09-26 | Terminal software authority management method and device, terminal and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110955869A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112507291A (en) * | 2020-11-18 | 2021-03-16 | 北京深思数盾科技股份有限公司 | Method and device for generating unique identifier of Android device |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101964901A (en) * | 2010-10-11 | 2011-02-02 | 杭州海康威视数字技术股份有限公司 | Right management method and equipment for video monitoring equipment |
| CN102314572A (en) * | 2011-10-14 | 2012-01-11 | 迈普通信技术股份有限公司 | Registration information file generation method and device, and use authorization method of application software |
| CN103020498A (en) * | 2012-11-19 | 2013-04-03 | 广东亚仿科技股份有限公司 | Intelligent dynamic access control method and system |
| CN104317626A (en) * | 2014-11-13 | 2015-01-28 | 北京奇虎科技有限公司 | Application software permission control method, device and system for terminal equipment |
| CN104537299A (en) * | 2014-12-10 | 2015-04-22 | 深圳先进技术研究院 | Method and system for detecting electronic device, and related apparatuses |
| CN104618369A (en) * | 2015-01-27 | 2015-05-13 | 广州市戴为智能科技有限公司 | Method, device and system for unique authorization of Internet-of-Things equipment based on OAuth |
| CN105677385A (en) * | 2015-12-29 | 2016-06-15 | 北京金山安全软件有限公司 | Application program adaptation method and device and electronic equipment |
| CN106254404A (en) * | 2015-06-10 | 2016-12-21 | 中兴通讯股份有限公司 | Application software authority recommends methods, devices and systems |
| CN106537288A (en) * | 2016-10-21 | 2017-03-22 | 北京小米移动软件有限公司 | Application autostart control method and device |
| CN106650320A (en) * | 2016-09-27 | 2017-05-10 | 武汉米企通网络科技有限公司 | Generation method of software certificate |
| CN107729764A (en) * | 2017-09-30 | 2018-02-23 | 广东欧珀移动通信有限公司 | Guard method, device, storage medium and the electronic equipment of sensitive information |
| CN108108595A (en) * | 2017-12-29 | 2018-06-01 | 晨星半导体股份有限公司 | The method and system authorized to the software in electronic equipment |
-
2018
- 2018-09-26 CN CN201811126562.5A patent/CN110955869A/en active Pending
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101964901A (en) * | 2010-10-11 | 2011-02-02 | 杭州海康威视数字技术股份有限公司 | Right management method and equipment for video monitoring equipment |
| CN102314572A (en) * | 2011-10-14 | 2012-01-11 | 迈普通信技术股份有限公司 | Registration information file generation method and device, and use authorization method of application software |
| CN103020498A (en) * | 2012-11-19 | 2013-04-03 | 广东亚仿科技股份有限公司 | Intelligent dynamic access control method and system |
| CN104317626A (en) * | 2014-11-13 | 2015-01-28 | 北京奇虎科技有限公司 | Application software permission control method, device and system for terminal equipment |
| CN104537299A (en) * | 2014-12-10 | 2015-04-22 | 深圳先进技术研究院 | Method and system for detecting electronic device, and related apparatuses |
| CN104618369A (en) * | 2015-01-27 | 2015-05-13 | 广州市戴为智能科技有限公司 | Method, device and system for unique authorization of Internet-of-Things equipment based on OAuth |
| CN106254404A (en) * | 2015-06-10 | 2016-12-21 | 中兴通讯股份有限公司 | Application software authority recommends methods, devices and systems |
| CN105677385A (en) * | 2015-12-29 | 2016-06-15 | 北京金山安全软件有限公司 | Application program adaptation method and device and electronic equipment |
| CN106650320A (en) * | 2016-09-27 | 2017-05-10 | 武汉米企通网络科技有限公司 | Generation method of software certificate |
| CN106537288A (en) * | 2016-10-21 | 2017-03-22 | 北京小米移动软件有限公司 | Application autostart control method and device |
| CN107729764A (en) * | 2017-09-30 | 2018-02-23 | 广东欧珀移动通信有限公司 | Guard method, device, storage medium and the electronic equipment of sensitive information |
| CN108108595A (en) * | 2017-12-29 | 2018-06-01 | 晨星半导体股份有限公司 | The method and system authorized to the software in electronic equipment |
Non-Patent Citations (2)
| Title |
|---|
| 方英兰等: "一种针对已有应用服务的单点登录解决方案", 《北方工业大学学报》 * |
| 汪彩梅等: "一种基于弹性保护机制的软件保护模型", 《合肥学院学报(综合版)》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112507291A (en) * | 2020-11-18 | 2021-03-16 | 北京深思数盾科技股份有限公司 | Method and device for generating unique identifier of Android device |
| CN112507291B (en) * | 2020-11-18 | 2022-09-13 | 深思数盾(天津)科技有限公司 | Method and device for generating unique identifier of Android device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110365670B (en) | Blacklist sharing method and device, computer equipment and storage medium | |
| CN108833355B (en) | Data processing method, data processing device, computer equipment and computer readable storage medium | |
| US9560026B1 (en) | Secure computer operations | |
| CN109325342B (en) | Identity information management method, device, computer equipment and storage medium | |
| CN102624699B (en) | Method and system for protecting data | |
| CN112818380A (en) | Method, device, equipment and system for backtracking processing of business behaviors | |
| US9165151B2 (en) | Systems, methods, and devices for encrypted data management | |
| CN104683336A (en) | Security-region-based method and system for protecting Android private data | |
| CN112597481A (en) | Sensitive data access method and device, computer equipment and storage medium | |
| CN107395359B (en) | Electronic data evidence fixing method, terminal and system | |
| CN112632581A (en) | User data processing method and device, computer equipment and storage medium | |
| CN109768979B (en) | Data encryption transmission method and device, computer equipment and storage medium | |
| CN110572355A (en) | Webpage data monitoring method and device, computer equipment and storage medium | |
| CN111241555B (en) | Access method and device for simulating user login, computer equipment and storage medium | |
| CN109587154B (en) | Digital identity verification method, device, computer equipment and storage medium | |
| TWI724684B (en) | Method, system and device for performing cryptographic operations subject to identity verification | |
| CN104318146A (en) | Fingerprint-identification-based cloud storage method | |
| CN111475823A (en) | Data sharing method, equipment, server and readable storage medium | |
| CN114257376A (en) | Digital certificate updating method and device, computer equipment and storage medium | |
| CN115022091A (en) | Digital certificate-based autonomous authorization method and system | |
| CN109132741B (en) | Ladder calling method and device based on two-dimensional code | |
| JP4947562B2 (en) | Key information management device | |
| KR102537788B1 (en) | Server and method for determining the integrity of the appliacion using thereof | |
| WO2016173267A1 (en) | Completeness checking method and apparatus | |
| CN112087417B (en) | Terminal authority control method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 330096 No.699 Tianxiang North Avenue, Nanchang hi tech Industrial Development Zone, Nanchang City, Jiangxi Province Applicant after: OFilm Microelectronics Technology Co.,Ltd. Address before: 330029 No. 1189 Jingdong Avenue, Nanchang high tech Zone, Jiangxi Applicant before: NANCHANG OFILM BIO-IDENTIFICATION TECHNOLOGY Co.,Ltd. Address after: 330096 No.699 Tianxiang North Avenue, Nanchang hi tech Industrial Development Zone, Nanchang City, Jiangxi Province Applicant after: Jiangxi OMS Microelectronics Co.,Ltd. Address before: 330096 No.699 Tianxiang North Avenue, Nanchang hi tech Industrial Development Zone, Nanchang City, Jiangxi Province Applicant before: OFilm Microelectronics Technology Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20200403 |
|
| WD01 | Invention patent application deemed withdrawn after publication |