CN116340903A - Function use authorization method, system and storage medium based on Android system - Google Patents

Abstract

The invention relates to a function use authorization method, a system and a storage medium based on an Android system, which comprise the following steps: before issuing an APK or an SDK, generating an authorization file containing a list to be authorized; when the APK or SDK of the current equipment initializes authorization verification, acquiring the authorization file, acquiring a corresponding identifier, extracting a list to be authorized from the authorization file, and allowing authorization if the identifier is in the list to be authorized. In the application, the corresponding authorization file is generated through the to-be-authorized list and is used for judging whether the corresponding equipment or software is in the to-be-authorized list in the subsequent step, so that whether authorization can be given is judged.

Description

Function use authorization method, system and storage medium based on Android system

Technical Field

The invention relates to the field of use authorization, in particular to a function use authorization method, system and storage medium based on an Android system.

Background

Currently, with the development of technology, mobile phone applications are becoming more and more popular. Due to the universality of the Android platform, the Android installation package (AndrpidPackage, APK) can be installed on various Android devices, such as a mobile phone, a tablet and the like after being downloaded, namely, the APK which is completed in the current device debugging can be installed on other different devices. And the Android SDK can be optionally installed after being integrated into the APK. In addition, the APK or the SDK can check related technical problems through operations such as decompilation and the like, and can be modified at will and repacked for installation.

In order to control the use of APK or SDK, the prior art mostly adopts a cloud authorization scheme, and needs to update or obtain an authorization file online when devices are networked, if the current network environment is not connected to an external network or the network is weak, the authorization fails frequently.

Aiming at the problems existing in the prior art, the invention designs a function use authorization method, system and storage medium based on an Android system.

Disclosure of Invention

Aiming at the problems in the prior art, the invention aims to provide a function use authorization method, system and storage medium based on an Android system, which can effectively solve at least one problem in the prior art.

The technical scheme of the invention is as follows:

a function use authorization method based on an Android system comprises the following steps:

before issuing an APK or an SDK, generating an authorization file containing a list to be authorized;

when the APK or SDK of the current equipment initializes authorization verification, acquiring the authorization file, acquiring a corresponding identifier, extracting a list to be authorized from the authorization file, and allowing authorization if the identifier is in the list to be authorized.

Further, the generating the authorization file containing the list to be authorized includes: storing a hardware identifier list of equipment to be authorized as a list file, encrypting the list file through a public key, and generating an authorization file;

the extracting the hardware identifier list of the device to be authorized from the authorization file comprises: and analyzing the authorization file through a private key to obtain the list file, and reading the list file to obtain a hardware identifier list of the equipment to be authorized.

Further, the object to be authorized is an APK based on an Android system;

before issuing an APK, collecting a hardware identifier list of equipment to be authorized to generate an authorization file containing the list to be authorized, and providing the authorization file to a receiver;

before the authorization file is acquired, executing: acquiring a path of the authorized file saved by a receiver, and defining a path of an AIDL interface for outputting the authorized file;

the obtaining the authorization file includes: and calling the AIDL interface to acquire the path of the authorization file, and acquiring the authorization file according to the path of the authorization file.

Further, the identifier is a hardware identifier of the device, the receiver informs the So library of the path of the authorization file through the AIDL interface, the device to be authorized acquires the hardware identifier of the current device through the application layer and sends the hardware identifier to the bottom interface So library, the bottom layer analyzes a hardware identifier list of the device to be authorized contained in the authorization file, if the hardware identifier of the current device is in the hardware identifier list, the bottom layer reports a comparison result to the application layer, and the application layer generates an authorization code to the current device So that the current device is allowed to be authorized.

Further, after allowing authorization of the current device, performing: and signing the obtained authorized APK, storing signature information, acquiring current signature information corresponding to the APK when the APK is started, sending the current signature information to the bottom layer, comparing the current signature information with the original signature information through the bottom layer, and refusing to provide services corresponding to the APK if the current signature information and the original signature information are not matched.

Further, the object to be authorized is an SDK based on an Android system;

before issuing the SDK, generating a check value of unique representative original information according to the initial authorization condition of the function in the SDK, generating an authorization file containing a list to be authorized according to the check value of the unique representative original information, and embedding the corresponding authorization file into the SDK;

the identifier is a check value which uniquely represents the original information, the authorization file is acquired when the SDK of the current device initializes authorization verification, the current authorization condition of the function of the device is acquired to generate the check value which uniquely represents the current information, the check value which uniquely represents the original information and corresponds to the initial authorization condition is extracted from the authorization file, the current authorization condition of the function of the device is compared to generate the check value which uniquely represents the current information, and if the check values are the same, the current SDK is allowed to be authorized.

Further, the check value uniquely representing the original information and the check value uniquely representing the current information are both MD5 values.

Further, generating the check value uniquely representing the original information based on the initial authorization status of the function in the SDK includes: and generating a check value which uniquely represents the original information together with the function in the SDK and the initial authorization condition corresponding to the function.

The utility model further provides a function use authorization system based on Android system, which comprises the following modules:

the authorization file generation module is used for generating an authorization file containing a list to be authorized before issuing the APK or the SDK;

and the authorization module is used for acquiring the authorization file, acquiring a corresponding identifier, extracting a list to be authorized from the authorization file when the APK or SDK of the current equipment initializes authorization verification, and allowing authorization if the identifier is in the list to be authorized.

Further provided is a computer readable storage medium storing a computer program which when executed by a processor implements a method for authorizing the use of functionality based on the Android system.

Accordingly, the present invention provides the following effects and/or advantages:

in the application, the corresponding authorization file is generated through the to-be-authorized list and is used for judging whether the corresponding equipment or software is in the to-be-authorized list in the subsequent step, so that whether authorization can be given is judged.

And the present application makes different strategies for SDKs and APKs.

For an APK file, the method and the device adopt the steps that a hardware identifier list of a device to be authorized, which can be authorized, is stored as a list file and is issued to a receiver, and whether a winner of the device can be authorized or not is judged by the receiver providing the hardware identifier of the device to be authorized and judging whether the hardware identifier is in the hardware identifier list of the device to be authorized or not. Therefore, after the receiver can acquire the authorization file once, the hardware in the receiver can be authorized without networking and other operations.

Aiming at the characteristic that the SDK file has no signature protection, the method and the device adopt the method that the MD5 value is generated by the initial authorization condition of the function in the SDK and is used for generating the authorization file containing the list to be authorized, so that the built-in function of the SDK and the permission condition of the built-in function can be locked, the MD5 value is integrated in the SDK, and only when the built-in function in the SDK and the permission condition of the built-in function are the same as the initial factory setting condition, the MD5 values of the built-in function and the permission condition of the built-in function are the same, so that whether software is tampered is verified, the software which is not tampered is authorized once is realized, and the technical effects of subsequent networking activation and the like are not needed.

The application can effectively control the three-party user to randomly use the related technical functions under the condition of unauthorized, and meanwhile, the authorized party can collect certain authorization fees. The colleague has the characteristics of low cost, simple operation and the like.

It is to be understood that both the foregoing general description and the following detailed description of the present invention are exemplary and explanatory and are intended to provide further explanation of the invention as claimed.

Drawings

FIG. 1 is a schematic flow chart of the present invention.

Fig. 2 is a flowchart illustrating the process of obtaining authorization through a MAC address according to one embodiment of the present invention.

Fig. 3 is a schematic flow chart of the supplying and obtaining of the authorization file according to one embodiment of the present invention.

Fig. 4 is a flow chart of signature verification according to one embodiment of the present invention.

Detailed Description

For the purpose of facilitating understanding to those skilled in the art, the present invention will now be described in further detail with reference to the accompanying drawings: it should be understood that, in this embodiment, the steps mentioned in this embodiment may be performed sequentially or sequentially, or may be performed simultaneously or partially, unless specifically stated otherwise.

Referring to fig. 1, a function usage authorization method based on an Android system includes the following steps:

s1, generating an authorization file containing a list to be authorized before issuing an APK or an SDK;

in this embodiment, the list to be authorized may be a table file, where an identifier that can be authorized is recorded through the table file, if some devices that can be authorized are recorded in the table file, a hardware identifier of each device that can be authorized, for example, a MAC address, a unique hardware code, etc., and if some software that can be authorized is recorded in the table file, an identifier of each software that can be authorized, for example, an MD5 value, a hash value, etc. of each software that can be authorized is recorded in the table file. And generating a corresponding authorization file through the list to be authorized, and judging whether corresponding equipment or software is in the list to be authorized in the subsequent step, thereby judging whether authorization can be given.

S2, when the APK or SDK of the current equipment initializes authorization verification, acquiring the authorization file, acquiring a corresponding identifier, extracting a list to be authorized from the authorization file, and allowing authorization if the identifier is in the list to be authorized.

In this step, corresponding to the authorization file in S1, when the APK or the SDK of the current device initializes authorization verification, the corresponding hardware or software may be allowed to obtain authorization by parsing the list to be authorized in the authorization file and obtaining the hardware identifier or the software check value of the device.

The generating the authorization file containing the list to be authorized comprises the following steps: storing a hardware identifier list of equipment to be authorized as a list file, encrypting the list file through a public key, and generating an authorization file;

the extracting the hardware identifier list of the device to be authorized from the authorization file comprises: and analyzing the authorization file through a private key to obtain the list file, and reading the list file to obtain a hardware identifier list of the equipment to be authorized.

In this step, in order to prevent the authorized file from being tampered, the information stored in the authorized file may be protected by encryption and decryption.

Example 1

In this embodiment, the object to be authorized is APK based on the Android system; since the APK file has a signature function and cannot be tampered with, in this embodiment, attention is paid to how to authorize the device hardware that can be authorized. That is, in this embodiment, the device is identified according to the hardware identifier of the device, and when the hardware identifier of the device is allowed to be authorized, the APK installed in the device is directly authorized. Referring to fig. 2, in this embodiment, the current device (three-party user) provides its MAC address, and the APK provider collects the MAC address that can be authorized in advance and generates a corresponding authorization file, and only needs to compare whether the current device (three-party user) provides its MAC address in the MAC address that can be authorized and covered by the authorization file, so as to determine whether it can be authorized. The process can be issued to the three-party user after the APK provider generates the authorization file, so that the three-party user can obtain authorization without accessing the Internet after receiving the authorization file.

Specifically: with reference to figure 3 of the drawings,

before issuing an APK, collecting a hardware identifier list of equipment to be authorized to generate an authorization file containing the list to be authorized, and providing the authorization file to a receiver;

through this step, the hardware identifier of the device that can be authorized can be packaged at one time to generate an authorization file.

Before the authorization file is acquired, executing: acquiring a path of the authorized file saved by a receiver, and defining a path of an AIDL interface for outputting the authorized file;

the obtaining the authorization file includes: and calling the AIDL interface to acquire the path of the authorization file, and acquiring the authorization file according to the path of the authorization file.

The APK provider develops an interface into which the authorization file can be imported, an APK provider authorizer can import the authorization file through an internal tool, or a three-party user can upload the authorization file by himself and notify the APK provider of the authorization file path through an AIDL interface. The technical problems of issuing and acquiring the authorization file can be solved through the steps, so that the three-party user can receive the authorization file once, and the requirement of networking authorization is not needed.

Further, the identifier is a hardware identifier of the device, the receiver informs the So library of the path of the authorization file through the AIDL interface, the device to be authorized acquires the hardware identifier of the current device through the application layer and sends the hardware identifier to the bottom interface So library, the bottom layer analyzes a hardware identifier list of the device to be authorized contained in the authorization file, if the hardware identifier of the current device is in the hardware identifier list, the bottom layer reports a comparison result to the application layer, and the application layer generates an authorization code to the current device So that the current device is allowed to be authorized.

In this step, the APK application layer notifies the so of the path of the authorization file, the APK performs initialization authorization verification after being started, the APK application layer obtains the MAC address of the device and transmits the MAC address to the APK bottom layer interface, such as the so library, the bottom layer firstly analyzes the current MAC address according to the stored authorization file through the private key, then compares the current MAC address with the input of the application layer, reports the comparison result to the application layer, and the application layer performs judgment processing, if the verification fails, prompts unauthorized use, and cannot use the corresponding function.

Further, after allowing authorization of the current device, performing: and signing the obtained authorized APK, storing signature information, acquiring current signature information corresponding to the APK when the APK is started, sending the current signature information to the bottom layer, comparing the current signature information with the original signature information through the bottom layer, and refusing to provide services corresponding to the APK if the current signature information and the original signature information are not matched.

Referring to fig. 4, to prevent APKs from being hacked and repackaged, APKs may incorporate APK signature verification. After the APK is started, signature information of the current APK is acquired and then transmitted to the bottom layer, the bottom layer can be compared with the original stored signature, and if the comparison fails, the APK is modified again, the corresponding APK software on the device is directly refused to be used.

Example two

In this embodiment, the object to be authorized is an SDK based on an Android system; since the SDK does not apply a signature, a signature anti-cracking scheme is not suitable for APKs. In this embodiment, a specific function class name MD5 value is added to the SDK for verification.

Specifically:

before issuing the SDK, generating a check value of unique representative original information according to the initial authorization condition of the function in the SDK, generating an authorization file containing a list to be authorized according to the check value of the unique representative original information, and embedding the corresponding authorization file into the SDK;

further, the check value uniquely representing the original information and the check value uniquely representing the current information are both MD5 values.

Further, generating the check value uniquely representing the original information based on the initial authorization status of the function in the SDK includes: and generating a check value which uniquely represents the original information together with the function in the SDK and the initial authorization condition corresponding to the function.

In this step, the SDK may include function 1, function 2, and function 3 …, and the use of a certain function may be permitted before the SDK is issued, for example, the use of function 1 is permitted, the use of function 2 and function 3 is not permitted, in which case, the first MD5 value is generated for the function on condition in the SDK, and only when the function included in the SDK and the corresponding permitted condition are identical to the above condition, the corresponding MD5 value is identical to the above first MD5 value. If the three-party user tampers with the function permission in the SDK, for example, changes the function 2 which is not allowed to be used into the allowed use, the corresponding MD5 value will be different from the first MD5 value.

The identifier is a check value which uniquely represents the original information, the authorization file is acquired when the SDK of the current device initializes authorization verification, the current authorization condition of the function of the device is acquired to generate the check value which uniquely represents the current information, the check value which uniquely represents the original information and corresponds to the initial authorization condition is extracted from the authorization file, the current authorization condition of the function of the device is compared to generate the check value which uniquely represents the current information, and if the check values are the same, the current SDK is allowed to be authorized.

In this embodiment, the SDK generates a verification value MD5 value uniquely representing the original information for the function class to be protected, integrates the MD5 values into a file, encrypts the file according to a public key by using a PC authorization tool to generate an authorization file, embeds the authorization file into a directory of the SDK, when a user of three parties introduces the SDK and initializes the SDK, the bottom library of the SDK reads the authorization file in the directory, decrypts the authorization file by using a private key, and analyzes whether the MD5 value after decryption is equal to the verification value MD5 value uniquely representing the original information in the class. Only when the file function file contained in the SDK and the authorization condition corresponding to the file function are identical to those of the SDK when the SDK is released, the verification value MD5 value generated uniquely representing the original information is identical to the verification value MD5 value generated uniquely representing the current information, and the SDK is allowed to be used under the condition.

The utility model further provides a function use authorization system based on Android system, which comprises the following modules:

the authorization file generation module is used for generating an authorization file containing a list to be authorized before issuing the APK or the SDK;

and the authorization module is used for acquiring the authorization file, acquiring a corresponding identifier, extracting a list to be authorized from the authorization file when the APK or SDK of the current equipment initializes authorization verification, and allowing authorization if the identifier is in the list to be authorized.

Further provided is a computer readable storage medium storing a computer program which when executed by a processor implements a method for authorizing the use of functionality based on the Android system.

It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the invention.

In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms should not be understood as necessarily being directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.

Claims (10)

1. A function use authorization method based on an Android system is characterized by comprising the following steps of: the method comprises the following steps:

before issuing an APK or an SDK, generating an authorization file containing a list to be authorized;

when the APK or SDK of the current equipment initializes authorization verification, acquiring the authorization file, acquiring a corresponding identifier, extracting a list to be authorized from the authorization file, and allowing authorization if the identifier is in the list to be authorized.

2. The Android system-based function use authorization method as claimed in claim 1, wherein: the generating the authorization file containing the list to be authorized comprises the following steps: storing a hardware identifier list of equipment to be authorized as a list file, encrypting the list file through a public key, and generating an authorization file;

the extracting the hardware identifier list of the device to be authorized from the authorization file comprises: and analyzing the authorization file through a private key to obtain the list file, and reading the list file to obtain a hardware identifier list of the equipment to be authorized.

3. The Android system-based function use authorization method as claimed in claim 1, wherein: the object to be authorized is an APK based on an Android system;

before issuing an APK, collecting a hardware identifier list of equipment to be authorized to generate an authorization file containing the list to be authorized, and providing the authorization file to a receiver;

before the authorization file is acquired, executing: acquiring a path of the authorized file saved by a receiver, and defining a path of an AIDL interface for outputting the authorized file;

the obtaining the authorization file includes: and calling the AIDL interface to acquire the path of the authorization file, and acquiring the authorization file according to the path of the authorization file.

4. The Android system-based function use authorization method according to claim 3, wherein: the identifier is a hardware identifier of the device, the receiver informs the So library of the path of the authorization file through an AIDL interface, the device to be authorized acquires the hardware identifier of the current device through an application layer and sends the hardware identifier to the bottom interface So library, the bottom layer analyzes a hardware identifier list of the device to be authorized contained in the authorization file, if the hardware identifier of the current device is in the hardware identifier list, the bottom layer reports a comparison result to the application layer, and the application layer generates an authorization code to the current device So that the current device is allowed to be authorized.

5. The Android system-based function use authorization method according to claim 3, wherein: after allowing authorization for the current device, performing: and signing the obtained authorized APK, storing signature information, acquiring current signature information corresponding to the APK when the APK is started, sending the current signature information to the bottom layer, comparing the current signature information with the original signature information through the bottom layer, and refusing to provide services corresponding to the APK if the current signature information and the original signature information are not matched.

6. The Android system-based function use authorization method as claimed in claim 1, wherein: the object to be authorized is an SDK based on an Android system;

before issuing the SDK, generating a check value of unique representative original information according to the initial authorization condition of the function in the SDK, generating an authorization file containing a list to be authorized according to the check value of the unique representative original information, and embedding the corresponding authorization file into the SDK;

the identifier is a check value which uniquely represents the original information, the authorization file is acquired when the SDK of the current device initializes authorization verification, the current authorization condition of the function of the device is acquired to generate the check value which uniquely represents the current information, the check value which uniquely represents the original information and corresponds to the initial authorization condition is extracted from the authorization file, the current authorization condition of the function of the device is compared to generate the check value which uniquely represents the current information, and if the check values are the same, the current SDK is allowed to be authorized.

7. The Android system-based function use authorization method as claimed in claim 6, wherein: and the check value of the unique representative original information and the check value of the unique representative current information are both MD5 values.

8. The Android system-based function use authorization method as claimed in claim 6, wherein: generating a check value uniquely representing the original information based on the initial authorization status of the function in the SDK comprises: and generating a check value which uniquely represents the original information together with the function in the SDK and the initial authorization condition corresponding to the function.

9. Function use authorization system based on Android system, its characterized in that: the method comprises the following modules:

the authorization file generation module is used for generating an authorization file containing a list to be authorized before issuing the APK or the SDK;

and the authorization module is used for acquiring the authorization file, acquiring a corresponding identifier, extracting a list to be authorized from the authorization file when the APK or SDK of the current equipment initializes authorization verification, and allowing authorization if the identifier is in the list to be authorized.

10. A computer readable storage medium storing a computer program, wherein the computer program when executed by a processor implements a function usage authorization method based on an Android system according to any one of claims 1 to 8.

Images