CN112651040A

CN112651040A - Permission application method, component, device and computer readable storage medium

Info

Publication number: CN112651040A
Application number: CN202011477694.XA
Authority: CN
Inventors: 郑文添; 魏猛
Original assignee: China Unionpay Co Ltd
Current assignee: China Unionpay Co Ltd
Priority date: 2020-12-15
Filing date: 2020-12-15
Publication date: 2021-04-13
Also published as: WO2022127214A1

Abstract

The invention provides a permission application method, a permission application assembly, a permission application device and a computer readable storage medium, wherein the permission application method comprises the following steps: receiving an authority application request of an external application, wherein the authority application request comprises an authority name of a target authority; if the target authority is not authorized, a transparent authority application container is established according to the current stack top page (Activity) component; applying a target permission to the android system by using the permission application container, and receiving a permission application result from the android system; and calling a corresponding callback function according to the permission application result so as to realize successful callback or failed callback of the target permission. By using the method, the process of authority application can be greatly simplified, and the redundancy of codes is reduced.

Description

Permission application method, component, device and computer readable storage medium

Technical Field

The invention belongs to the field of authority application, and particularly relates to an authority application method, an authority application component, an authority application device and a computer readable storage medium.

Background

This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.

A wide variety of applications may be installed in terminal devices such as cell phones, tablet computers, and the like. The application program needs to have corresponding system authority for realizing certain functions. For example, when an application needs to implement a function of recommending a friend of an address book to a user, the application needs to have a right to acquire address book information. The android system adds a dynamic authority mechanism behind the 6.0 version, that is, when a certain application program uses a certain authority (such as a camera authority, a recording authority, and the like) for the first time, the user needs to apply the use authority to the user through a system popup, and the application program can be used after the user agrees.

When a developer writes application program codes, the developer finds that the process of realizing the dynamic application permission in the prior art is complicated, redundant codes are too much, and dynamic application permission in any module cannot be easily realized.

Disclosure of Invention

In view of the above problems in the prior art, an authority application method, an authority application assembly, an authority application apparatus, and a computer-readable storage medium are provided.

The present invention provides the following.

In a first aspect, a permission application method is provided, and is applied to an android platform, and the method includes: receiving an authority application request of an external application, wherein the authority application request comprises an authority name of a target authority; if the target authority is not authorized, a transparent authority application container is established according to the current stack top page (Activity) component; applying a target permission to the android system by using the permission application container, and receiving a permission application result from the android system; and calling a corresponding callback function according to the permission application result so as to realize successful callback or failed callback of the target permission.

In some possible implementations, the rights application container includes a transparent fragment (fragment) control.

In some possible embodiments, the method for applying for the permission to the android system by using the permission application container and receiving a permission application result from the android system includes: after a transparent fragment (fragment) control is created, triggering a permission request method of the transparent fragment (fragment) control, wherein the permission request method is used for triggering an android system to initiate a permission application process aiming at a target permission; if the android system receives an authorized click event aiming at the target authority, the android system calls back a method for requesting an authority result of a transparent fragment (fragment) control, and the authority application result is updated to be the authority application success; and if the android system receives an authorization rejection click event aiming at the target authority, the authority application result is updated to be the authority application failure through a method for calling back the authority request result of the transparent fragment (fragment) control by the android system.

In some possible embodiments, creating a transparent fragment (fragment) control from a current top of stack page (Activity) component further comprises: monitoring real-time stack elements through a page (Activity) life cycle callback interface provided by an android system, and maintaining a page list by using a monitoring result, wherein newly generated elements are added in the page list in real time and destroyed elements are deleted; acquiring the last pushed element as a current stack top page (Activity) component by using the page list; in factory mode, according to the type of the top of stack page (Activity) component, a transparent fragment (fragment) control of the corresponding type is created.

In some possible embodiments, only one permission application container is maintained in each permission application, a label is marked for the permission application container, and in the subsequent permission application process, the corresponding permission application container is preferentially found according to the label to execute the permission application; and when the stack top page (Activity) component bound by the rights application container is destroyed, the rights application container is also destroyed.

In some possible embodiments, the permission application request includes: dynamic authority application and special authority application; and, the method further comprises: when the authority application request is a dynamic authority application, calling a callback function of the success of the dynamic authority application or a callback function of the failure of the dynamic authority application according to the authority application result; and when the authority application request is a special authority application, calling a callback function of the success of the special authority application or a callback function of the failure of the special authority application according to the authority application result.

In some possible embodiments, after receiving the request for the permission application from the external application, the method further includes: detecting whether the target authority is authorized according to the authority name; if the target permission is authorized, the target permission is directly successfully recalled without executing subsequent steps.

In some possible embodiments, the method further comprises: before detecting whether the target authority is authorized, judging whether the authority name exists in a pre-registered authority name list, if not, stopping the authority application and generating error report information.

In some possible embodiments, the method further comprises: before detecting whether the target authority is authorized, judging whether the authority application request is a dynamic authority application or a special authority application; if the authority application request is not a dynamic authority application or a special authority application and the android system is a version before android6.0, successfully calling back the target authority directly; and if the authority application request is a dynamic authority application or a special authority application, or the android system is android6.0 or later, further detecting whether the target authority is authorized.

In some possible embodiments, the permission application request further includes permission bullet box information, and the permission bullet box information is used for indicating whether to apply for the target permission in a permission prompt box manner; and before creating a transparent fragment (fragment) control from a current stack top page (Activity) component, the method further comprises: judging whether a target authority needs to be applied in an authority prompt box mode or not according to the authority pop box information; if the target authority needs to be applied in the authority prompt box mode, displaying preset authority prompt information to a user in the external application in the authority prompt box mode, responding to a user refusing event related to the authority prompt information and ending authority application, or responding to a user confirmation event related to the authority prompt information and continuing to execute transparent fragment (fragment) control creation according to a current stack top page (Activity) component and subsequent steps; and if the target authority does not need to be applied in the manner of the authority prompt box, directly continuing to execute the steps of creating a transparent fragment (fragment) control according to the current stack top page (Activity) component and the subsequent steps.

In a second aspect, a rights application component is provided, comprising: the application module is used for receiving an authority application request of an external application, wherein the authority application request comprises an authority name of a target authority; the life cycle module is used for creating a transparent permission application container according to a current stack top page (Activity) component when the target permission is not authorized; the container module is used for applying the target permission to the android system by using the permission application container and receiving a permission application result from the android system; and the callback module is used for calling the corresponding callback function according to the permission application result so as to realize successful callback or failed callback of the target permission.

In some possible embodiments, the container module is further configured to: after a transparent fragment (fragment) control is created, triggering a permission request method of the transparent fragment (fragment) control, wherein the permission request method is used for triggering an android system to initiate a permission application process aiming at a target permission; if the android system receives an authorized click event aiming at the target authority, the android system calls back a method for requesting an authority result of a transparent fragment (fragment) control, and the authority application result is updated to be the authority application success; and if the android system receives an authorization rejection click event aiming at the target authority, the authority application result is updated to be the authority application failure through a method for calling back the authority request result of the transparent fragment (fragment) control by the android system.

In some possible embodiments, the lifecycle module is further to: monitoring real-time stack elements through a page (Activity) life cycle callback interface provided by an android system, and maintaining a page list by using a monitoring result, wherein newly generated elements are added in the page list in real time and destroyed elements are deleted; acquiring the last pushed element as a current stack top page (Activity) component by using the page list; in factory mode, according to the type of the top of stack page (Activity) component, a transparent fragment (fragment) control of the corresponding type is created.

In some possible embodiments, the permission application request includes: dynamic authority application and special authority application; and the callback module is further configured to: when the authority application request is a dynamic authority application, calling a callback function of the success of the dynamic authority application or a callback function of the failure of the dynamic authority application according to the authority application result; and when the authority application request is a special authority application, calling a callback function of the success of the special authority application or a callback function of the failure of the special authority application according to the authority application result.

In some possible embodiments, the assembly further comprises a detection module for: after receiving an authority application request of an external application, detecting whether a target authority is authorized or not according to an authority name; if the target permission is authorized, the target permission is directly successfully recalled without executing subsequent steps.

In some possible embodiments, the assembly further comprises a first determining module configured to: before detecting whether the target authority is authorized, judging whether the authority name exists in a pre-registered authority name list, if not, stopping the authority application, and generating error report information.

In some possible embodiments, the assembly further comprises a second determining module configured to: before detecting whether the target authority is authorized, judging whether the authority application request is a dynamic authority application or a special authority application; if the authority application request is not a dynamic authority application or a special authority application and the android system is a version before android6.0, successfully calling back the target authority directly; and if the authority application request is a dynamic authority application or a special authority application, or the android system is android6.0 or later, further detecting whether the target authority is authorized.

In some possible embodiments, the permission application request further includes permission bullet box information, and the permission bullet box information is used for indicating whether to apply for the target permission in a permission prompt box manner; the component also comprises a prompt module which is used for judging whether a target authority needs to be applied in an authority prompt box mode according to the authority bullet box information before a transparent fragment (fragment) control is created according to the current stack top page (Activity) component; if the target authority needs to be applied in the authority prompt box mode, displaying preset authority prompt information to a user in the external application in the authority prompt box mode, responding to a user refusing event related to the authority prompt information and ending authority application, or responding to a user confirmation event related to the authority prompt information and continuing to execute transparent fragment (fragment) control creation according to a current stack top page (Activity) component and subsequent steps; and if the target authority does not need to be applied in the manner of the authority prompt box, directly continuing to execute the steps of creating a transparent fragment (fragment) control according to the current stack top page (Activity) component and the subsequent steps.

In a third aspect, there is provided a rights application apparatus, including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method according to the first aspect.

In a fourth aspect, there is provided a computer readable storage medium storing a program which, when executed by a multicore processor, causes the multicore processor to perform the method of the first aspect.

The embodiment of the application adopts at least one technical scheme which can achieve the following beneficial effects: in the embodiment, a transparent permission application container is created according to the current stack top page (Activity) component, and the permission application container applies the target permission to the android system, so that the permission application process can be greatly simplified, and the redundancy of codes is reduced.

It should be understood that the above description is only an overview of the technical solutions of the present invention, so as to clearly understand the technical means of the present invention, and thus can be implemented according to the content of the description. In order to make the aforementioned and other objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in detail below.

Drawings

The advantages and benefits described herein, as well as other advantages and benefits, will be apparent to those of ordinary skill in the art upon reading the following detailed description of the exemplary embodiments. The drawings are only for purposes of illustrating exemplary embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like elements throughout. In the drawings:

FIG. 1 is a flowchart illustrating a rights application method according to an embodiment of the present invention;

FIG. 2 is a flowchart illustrating a rights application method according to another embodiment of the present invention;

FIG. 3 is a schematic diagram of a rights application component according to an embodiment of the invention;

fig. 4 is a schematic structural diagram of a rights application apparatus according to an embodiment of the invention.

In the drawings, the same or corresponding reference numerals indicate the same or corresponding parts.

Detailed Description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

In the description of the embodiments of the present application, it is to be understood that terms such as "including" or "having" are intended to indicate the presence of the features, numbers, steps, actions, components, parts, or combinations thereof disclosed in the specification, and are not intended to preclude the presence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

Unless otherwise stated, "/" indicates an OR meaning, e.g., A/B may indicate A or B; "and/or" herein is merely an association describing an associated object, and means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone.

The terms "first", "second", etc. are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first," "second," etc. may explicitly or implicitly include one or more of that feature. In the description of the embodiments of the present application, "a plurality" means two or more unless otherwise specified.

All code in this application is exemplary and variations will occur to those skilled in the art based upon the programming language used, the specific needs and personal habits without departing from the spirit of the application.

The permission application method provided by the embodiment of the application runs on the electronic equipment. The permission application assembly and the permission application device provided by the embodiment of the application are arranged in the electronic equipment. The electronic device may correspond to a smart phone, a portable phone, a game machine, a television, a display unit, a heads-up display unit for a vehicle, a notebook computer, a laptop computer, a tablet Personal Computer (PC), a Personal Media Player (PMP), a Personal Digital Assistant (PDA), and the like, corresponding to products on the market. The electronic device may also be implemented as a communication terminal having a communication module, and the communication terminal may communicate with an external electronic device such as a server or the like or perform an operation by interworking with the external electronic device.

It should be noted that the embodiments and features of the embodiments may be combined with each other without conflict. The present invention will be described in detail below with reference to the embodiments with reference to the attached drawings.

The embodiment of the invention provides a permission application method, and the invention concept of the method is introduced firstly.

When a user uses an android application installed on a terminal device, in some cases, the android application needs to use some privacy elements in the user device and wants to obtain permission of the privacy elements. Based on this, an embodiment of the present invention provides a permission application method, where when a permission application request for a target permission sent by an external application is received, if the target permission is not authorized, a transparent permission application container may be created according to a current stack top page (Activity) component, and a target permission is applied to an android system by using the created permission application container, and a corresponding callback function is called according to a permission application result received from the android system, so as to finally implement a successful callback or a failed callback of the target permission. The embodiment of the application is different from a traditional authority application mode, and by managing and applying current stack information, a transparent container is generated through a stack top page (Activity) to apply for authority when any module applies for the authority, so that the current situation that a traditional authority application scheme highly depends on business View is eliminated.

Those skilled in the art will appreciate that the described application scenario is only one example in which an embodiment of the present invention may be implemented. The scope of applicability of the embodiments of the present invention is not limited in any way. Having described the general principles of the invention, various non-limiting embodiments of the invention are described in detail below.

Fig. 1 is a flowchart illustrating a permission application method 100 applied to an android platform according to an embodiment of the present application, where an execution subject may be one or more electronic devices from a device perspective; from the program perspective, the execution main body may accordingly be a program loaded on these electronic devices.

As shown in fig. 1, the method 100 may include:

step 101, receiving an authority application request of an external application, wherein the authority application request comprises an authority name of a target authority;

in the embodiment of the present application, Permission (Permission) refers to Permission that an android application needs to be granted by a user in order to use some privacy elements of the user. The target permission may be, for example, a permission of the external application to use the camera of the device, a permission of the external application to access the address book of the device, and the like.

Starting from Android6.0, an authority application mechanism is introduced into an Android system, and all authorities are divided into normal authorities and dangerous authorities, wherein the normal authorities can not directly bring risks to the privacy authority of a user, and the dangerous authorities can grant the authority of application access to confidential data of the user. The application program needs to dynamically apply for the relevant dangerous rights before using some functions. In general, if an application requires a dangerous right, it is checked whether the application has the dangerous right before performing an operation requiring the dangerous right each time. For example, if the application needs to use the photographing function, it needs to first determine whether the application has the camera right, if not, the application needs to be applied, the application can be performed after the user agrees, and if the user refuses, the application cannot be performed.

In some possible embodiments, the rights application request may include a dynamic rights application and a special rights application.

The dynamic permission applications include one or more of the following hazard class permission applications: memory card file read-write permission application, microphone recording permission application, camera permission application, location permission application, calendar permission application, contact permission application, short message permission application, sensor permission application, and the like. After android6.0, all hazard class rights need to be dynamically applied in the application,

the application for special permission includes one or more of the following: install untrusted source permission applications, system permission notification permissions and system floating window permission applications, etc.

In one example, a component for implementing the method for applying for a permission is exposed to the outside and an external application can call the following interface, so that a dynamic permission application or a special permission application can be implemented by using a line of code.

(1) Dynamic authority application realized by one line of codes

Permission.getInstance().

.withSpecialPermission(SpecialPermission specialPermission)

.withSpecialPermissionCallback(RequestSpecialPermissionCallback callback)

.withRequestCode(Integer requestCode).requestSpecialPermission()；

Wherein, the parameters are as follows: properties: the authority name to be applied is a must-pass parameter; callback of authority application, which is a necessary transmission parameter; requestCode: the user-defined request code can be null; isRational, whether a prompt box is needed or not is a necessary parameter; dialog: user-defined prompt box

(2) One line of codes realizes special permission application

Permission.getInstance().

.withSpecialPermission(SpecialPermission specialPermission)

.withSpecialPermissionCallback(RequestSpecialPermissionCallback callback)

.withRequestCode(Integer requestCode).requestSpecialPermission()；

Wherein, the parameters are as follows: specialPermission: the self-defined special permission is a must-pass parameter and mainly comprises three types: private _ APP _ SOURCE, install untrusted SOURCE, private permission notification, and private permission system suspend window; requestCode: request code, Integer type, may pass null value, use system default code; a callback: calling back the interface after the application of the special permission as a must-pass parameter

In addition, the difference between the dynamic authority application and the special authority application further includes: the dynamic permission application can perform permission authorization on an application interface based on the click operation of a user, and the special permission application needs to jump to a set device interface (such as a system setting page) and perform permission authorization based on the click operation of the user.

102, if the target authority is not authorized, creating a transparent authority application container according to a current stack top page (Activity) component;

the Activity component is one of components of an android application program and is responsible for interaction between a user and a system, and in the android system, the Activity is equivalent to a WEB page or a client interface of a PC (personal computer) end and is used for not only displaying information to the user but also monitoring and responding to the operation of the user. The same application usually has multiple Activities, but only one of the Activities that is active is presented to the user at the same time, with the others being paused or stopped.

In some possible implementations, the transparent rights application container is a transparent fragment (fragment) control. The fragment control is a small module of an Android application page (Activity), is a fragment which can be embedded in the page (Activity), is used for displaying interface content, and can accept interactive operations such as clicking and dragging by a user. For example, clicking a menu in one page enters a second level page, which may be implemented through a Fragment (Fragment) control.

In some possible embodiments, step 102 may further include: monitoring real-time stack elements through a page (Activity) life cycle callback interface provided by an android system, and maintaining a page list by using a monitoring result, wherein newly generated elements are added in the page list in real time and destroyed elements are deleted; acquiring the last pushed element as a current stack top page (Activity) component by using the page list; in factory mode, according to the type of the top of stack page (Activity) component, a transparent fragment (fragment) control of the corresponding type is created.

In particular, real-time stack elements of an application may be monitored through the Activity Lifecycle Callbacks method provided by the android system. A page (Activity) list is maintained in the Activity management system, when a new Activity is generated, the new Activity is added into the page (Activity) list, and when the Activity is destroyed, the Activity is deleted from the page (Activity) list. Through the page (Activity) list, a stack top page (the last element to be pushed) can be obtained, and then a permission application container is generated.

In some possible embodiments, only one permission application container is maintained in each permission application, a label is marked for the permission application container, and in the subsequent permission application process, the corresponding permission application container is preferentially found according to the label to execute the permission application; and when the stack top page (Activity) component bound by the rights application container is destroyed, the rights application container is also destroyed. In the embodiment of the application, the fragment management efficiency can be greatly improved by only maintaining one container.

103, applying the target permission to an android system by using the permission application container, and receiving a permission application result from the android system;

in the embodiment of the application, functions such as dynamic permission application and special permission application of Android can be processed by using a transparent fragment (fragment) control. Due to the iterative update of the Android system, pages (Activity) are of two types, and fragment (fragment) controls are of two types correspondingly. And (3) creating a corresponding transparent Fragment (Fragment) according to the type of the incoming stack top page (Activity) by using a factory mode, and processing different fragments (fragments) through a proxy mode to perform operations such as dynamic permission application, special permission application and the like. The creation and management of fragments (fragments) of different types are relatively complicated matters, and operations such as starting, stopping, adding, deleting and the like of the Fragment (Fragment) transaction can be uniformly managed in a factory class, so that the authority container can be effectively managed.

In some possible embodiments, referring to fig. 2, step 103 may further include the following refinement steps:

201. after the transparent fragments are created, triggering a permission requesting method of the transparent fragments, wherein the permission requesting method is used for triggering the android system to initiate a permission application process aiming at target permissions;

202. if the android system receives an authorized click event aiming at the target authority, the authority application result is updated to be the authority application success by the method for calling back the authority request result of the transparent fragment through the android system;

203. and if the android system receives the authorization rejection click event aiming at the target permission, the permission application result is updated to be permission application failure through a permission request result method of the transparent fragment called back by the android system.

Wherein, the created transparent Fragment (Fragment) provides a result callback of dynamic application permission and a result callback of special permission application, and the result is notified to the external application after the permission application is finished. Specifically, after the Fragment (Fragment) is created, a request permission method of the Fragment (Fragment) is triggered, and an authority application flow of the android system is triggered. Based on this, the android system inquires whether the user agrees to the permission application request, and responds to the user click event, and the android system calls back a request permission result method for notifying a transparent Fragment (Fragment) so as to update the permission application result. If the permission application passes, calling a code for success of the permission application through a callback function in the transparent Fragment (Fragment) to inform the external application that the permission application succeeds. Otherwise, calling the code of the permission application failure through the callback function in the transparent Fragment (Fragment) to perform corresponding failure processing logic.

And 104, calling a corresponding callback function according to the permission application result so as to realize successful callback or failed callback of the target permission.

Among them, a callback interface providing various request operations may be registered in advance. Callback interface comprising dynamic authority application success callback function, application failure callback function, special authority application success callback function, special authority application failure callback function, and authority prompt box confirm key and cancel key

In one example, the component for implementing the permission application method exposes the following interface to the outside, and calls the callback interface when the component needs to be used subsequently.

(1) The dynamic permission application callback interface, exemplary code is as follows:

(2) the special permission application callback interface, exemplary code is as follows:

(3) the custom prompt box callback, exemplary code is as follows:

in some possible embodiments, the permission application request includes: step 104 further comprises: when the authority application request is a dynamic authority application, calling a callback function of the success of the dynamic authority application or a callback function of the failure of the dynamic authority application according to the authority application result; and when the authority application request is a special authority application, calling a callback function of the success of the special authority application or a callback function of the failure of the special authority application according to the authority application result.

In some possible embodiments, after step 101, the method may further include:

step 301, judging whether the authority name exists in the authority name list registered in advance.

If not, step 302 is executed, the permission application is stopped, and error reporting information is generated.

On the contrary, if the authority name exists in the pre-registered authority name list, the subsequent authority application step is continuously executed.

In other words, it is equivalent to first determine whether the authority name is legal, and if the authority name carried in the authority application request is not a legal authority name, the subsequent authority application step is not required.

In some possible embodiments, after step 101, the method may further include:

step 303, judging whether the permission application request is a dynamic permission application or a special permission application;

if the authority application request is not a dynamic authority application or a special authority application and the android system is a version before android6.0, successfully calling back the target authority directly; and if the authority application request is a dynamic authority application or a special authority application, or the android system is android6.0 or later, continuing to execute the subsequent authority application steps.

In the embodiment of the application, since the permission application mechanism is introduced from the Android6.0, if the permission application request is not a dynamic permission application or a special permission application and the Android system is a version before Android6.0, the callback can be directly and successfully carried out.

Optionally, step 303 may be performed after or before step 301, which is not particularly limited in this application.

In some possible embodiments, before step 102, the method may further include performing:

and step 304, detecting whether the target authority is authorized according to the authority name.

If the target permission is authorized, the callback interface corresponding to the permission application success for realizing the target permission is directly called without executing subsequent steps. If the target authority is not authorized, the steps 202 and 204 are continued.

Alternatively, step 304 may be performed after steps 301 and 303.

In some possible embodiments, when the authority application request is a dynamic application request, the authority application request further includes authority pop frame information, and the authority pop frame information is used for indicating whether to apply for the target authority in the manner of an authority prompt box; and, after step 304, the method may further comprise:

305, judging whether a target authority needs to be applied in an authority prompt box mode according to the authority pop box information; wherein the content of the first and second substances,

if the target authority needs to be applied in the manner of the authority prompt box, executing:

step 306, displaying preset permission prompt information to a user in an external application in a permission prompt box mode; and when the user refusing event aiming at the authority prompting box occurs, further executing step 307, and responding to the user refusing event about the authority prompting information to end the authority application, or when the user confirming event aiming at the authority prompting box occurs, responding to the user confirming event about the authority prompting information to continue executing step 102 and the subsequent steps.

If the target authority does not need to be applied in the authority prompt box mode, the step 102 and the subsequent steps are directly executed continuously.

In the embodiment of the application, in order to enable the user to clearly know the reason of the current permission application, sometimes a developer needs to provide an additional permission prompt box to prompt the user, and the embodiment of the application can provide the developer with a function of privately customizing the permission prompt box. For example, a custom Dialog Fragment can be used to allow a developer to customize the personal rights prompt box. And entering the main process of the authority application after the user clicks and agrees.

It should be noted that when the Android application is built using the MVVM mode, all the service logic is handled in the ViewModel, and the same is true for the permission application. However, according to the related introduction of the permission application in the Android official document, the permission application needs to operate in Activity or Fragment. Thus, the ViewModel needs to communicate with View (Activity or Fragment) additionally, which is not in accordance with the design concept of MVVM. In the application, the permission application can be carried out in any module by adopting the transparent permission application container, and the permission application method can be perfectly integrated into the application program developed in the MVVM mode.

Based on the same technical concept, the embodiment of the present invention further provides a rights application component 300, which is used for implementing the rights application method provided by any of the above embodiments. Fig. 3 is a schematic structural diagram of a rights application component according to an embodiment of the present invention.

Referring to fig. 3, the rights application component 300 includes:

the application module is used for receiving an authority application request of an external application, wherein the authority application request comprises an authority name of a target authority;

the life cycle module is used for creating a transparent permission application container according to a current stack top page (Activity) component when the target permission is not authorized;

the container module is used for applying the target permission to the android system by using the permission application container and receiving a permission application result from the android system;

and the callback module is used for calling the corresponding callback function according to the permission application result so as to realize successful callback or failed callback of the target permission.

It should be noted that the permission application component in the embodiment of the present application can implement each process of the embodiment of the permission application method, and achieve the same effect and function, which is not described herein again.

Fig. 4 is a rights application apparatus according to an embodiment of the present application, configured to execute the rights application method shown in fig. 1, where the apparatus includes: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of the above embodiments.

According to some embodiments of the present application, there is provided a non-transitory computer storage medium of a rights application method having stored thereon computer-executable instructions configured to, when executed by a processor, perform: the method as described in the above example.

The embodiments in the present application are described in a progressive manner, and the same and similar parts among the embodiments can be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus, device, and computer-readable storage medium embodiments, the description is simplified because they are substantially similar to the method embodiments, and reference may be made to some descriptions of the method embodiments for their relevance.

The apparatus, the device, and the computer-readable storage medium provided in the embodiment of the present application correspond to the method one to one, and therefore, the apparatus, the device, and the computer-readable storage medium also have advantageous technical effects similar to those of the corresponding method.

As will be appreciated by one skilled in the art, 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 flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. Moreover, while the operations of the method of the invention are depicted in the drawings in a particular order, this does not require or imply that the operations must be performed in this particular order, or that all of the illustrated operations must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.

While the spirit and principles of the invention have been described with reference to several particular embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, nor is the division of aspects, which is for convenience only as the features in such aspects may not be combined to benefit. The invention is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

1. A permission application method is applied to an android platform, and comprises the following steps:

receiving an authority application request of an external application, wherein the authority application request comprises an authority name of a target authority;

if the target authority is not authorized, a transparent authority application container is established according to a current stack top page (Activity) component;

applying the target permission to an android system by using the permission application container, and receiving a permission application result from the android system;

and calling a corresponding callback function according to the permission application result so as to realize successful callback or failed callback of the target permission.

2. The method of claim 1, wherein the rights application container includes a transparent fragment (fragment) control.

3. The method according to claim 2, wherein the steps of applying for the permission to the android system by using the permission application container and receiving permission application results from the android system include:

after the transparent fragment (fragment) control is created, triggering a permission request method of the transparent fragment (fragment) control, wherein the permission request method is used for triggering the android system to initiate a permission application process aiming at the target permission;

if the android system receives an authorized click event aiming at the target authority, the android system calls back an authority request result method of the transparent fragment (fragment) control, and the authority application result is updated to be the authority application success;

and if the android system receives an authorization-refusing click event aiming at the target permission, the permission request result method of the transparent fragment (fragment) control is called back through the android system, and the permission application result is updated to be a permission application failure.

4. The method of claim 2, wherein creating a transparent fragment (fragment) control from a current top of stack page (Activity) component further comprises:

monitoring real-time stack elements through a page (Activity) life cycle callback interface provided by an android system, and maintaining a page list by using a monitoring result, wherein newly generated elements are added to the page list in real time and destroyed elements are deleted;

acquiring the last pushed element as the current stack top page (Activity) component by utilizing the page list;

in a factory mode, according to the type of the stack top page (Activity) component, a transparent fragment (fragment) control of a corresponding type is created.

5. The method of claim 2,

only one permission application container is maintained in each permission application, a label is marked for the permission application container, and in the subsequent permission application process, the corresponding permission application container is preferentially found according to the label to execute the permission application; and the number of the first and second groups,

when the stack top page (Activity) component bound by the rights application container is destroyed, the rights application container is also destroyed.

6. The method according to any one of claims 1-5, wherein the permission application request comprises: dynamic authority application and special authority application; and, the method further comprises:

when the authority application request is a dynamic authority application, calling a callback function of a dynamic authority application success or a callback function of a dynamic authority application failure according to the authority application result;

and when the authority application request is a special authority application, calling a callback function of the success of the special authority application or a callback function of the failure of the special authority application according to the authority application result.

7. The method of claim 1, wherein after receiving a request for permission application from an external application, the method further comprises:

detecting whether the target authority is authorized according to the authority name; wherein the content of the first and second substances,

and if the target permission is authorized, directly and successfully calling back the target permission without executing subsequent steps.

8. The method of claim 7, further comprising:

before detecting whether the target authority is authorized, judging whether the authority name exists in a pre-registered authority name list, if not, stopping the authority application, and generating error information.

9. The method of claim 7, further comprising:

before detecting whether the target authority is authorized, judging whether the authority application request is a dynamic authority application or a special authority application; wherein the content of the first and second substances,

if the authority application request is not the dynamic authority application or the special authority application and the android system is a version before android6.0, successfully calling back the target authority directly;

if the authority application request is the dynamic authority application or the special authority application, or the android system is android6.0 or later, whether the target authority is authorized is further detected.

10. The method according to claim 2, wherein the permission application request further includes permission popup information for indicating whether to apply for the target permission in a permission prompt box manner; and the number of the first and second groups,

before creating a transparent fragment (fragment) control from a current top of stack page (Activity) component, the method further comprises:

judging whether the target authority needs to be applied in the authority prompt box mode or not according to the authority pop box information; wherein the content of the first and second substances,

if the target authority needs to be applied in a manner of an authority prompt box, displaying preset authority prompt information to a user in the manner of the authority prompt box in the external application, and ending the authority application in response to a user rejection event related to the authority prompt information, or continuing to execute the steps of creating a transparent fragment (fragment) control according to a current stack top page (Activity) component and the subsequent steps in response to a user confirmation event related to the authority prompt information;

and if the target authority does not need to be applied in the manner of the authority prompt box, directly continuing to execute the steps of creating a transparent fragment (fragment) control according to the current stack top page (Activity) component and the subsequent steps.

11. An authority application assembly, applied to an android platform, the assembly comprising:

and the callback module is used for calling a corresponding callback function according to the permission application result so as to realize successful callback or failed callback of the target permission.

12. The component of claim 11, wherein the rights application container includes a transparent fragment (fragment) control.

13. The assembly of claim 12, wherein the container module is further configured to:

after the transparent fragment (fragment) control is created, triggering a request permission component of the transparent fragment (fragment) control, wherein the request permission component is used for triggering the android system to initiate a permission application process aiming at the target permission;

if the android system receives an authorized click event aiming at the target authority, a permission request result component of the transparent fragment (fragment) control is called back through the android system, and the permission application result is updated to be successful in permission application;

if the android system receives an authorization-refusing click event aiming at the target permission, the android system calls back the permission request result component of the transparent fragment (fragment) control, and the permission application result is updated to be permission application failure.

14. The assembly of claim 12, wherein the lifecycle module is further to:

15. The assembly of claim 12,

16. An assembly according to any one of claims 11 to 15, wherein the rights application request includes: dynamic authority application and special authority application; and the callback module is further configured to:

17. The assembly of claim 11, further comprising a detection module to:

after receiving an authority application request of an external application, detecting whether the target authority is authorized or not according to the authority name; wherein the content of the first and second substances,

18. The assembly of claim 17, further comprising a first determination module configured to:

19. The assembly of claim 17, further comprising a second determination module configured to:

20. The component of claim 12, wherein the permission application request further comprises permission box information, the permission box information indicating whether to apply for the target permission in a manner of a permission prompt box; and the number of the first and second groups,

the assembly further comprises a prompt module for:

before a transparent fragment (fragment) control is created according to a current stack top page (Activity) component, judging whether the target authority needs to be applied in the authority prompt box mode or not according to the authority bullet box information; wherein the content of the first and second substances,

21. An authority application apparatus, comprising:

at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to perform: the method of any one of claims 1-10.

22. A computer-readable storage medium storing a program that, when executed by a multi-core processor, causes the multi-core processor to perform the method of any one of claims 1-10.