Permission Management Method and Terminal Device
US-2023297700-A1 · Sep 21, 2023 · US
US12561474B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12561474-B2 |
| Application number | US-202318507363-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 13, 2023 |
| Priority date | May 13, 2021 |
| Publication date | Feb 24, 2026 |
| Grant date | Feb 24, 2026 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Embodiments of this specification provide computer-implemented methods, apparatuses, and computer-readable storage media for interface invocation request processing. In an example interface invocation request processing method, an invocation request for a first interface of an operating system is received from a client application, and the first interface is configured to obtain privacy data. First scenario information is obtained, where the first scenario information is description information of a use scenario of the first interface declared when the client application applies for an invocation permission of the first interface. Current scenario information of the client application is obtained. The invocation request is executed in response to at least that the current scenario information matches the first scenario information.
Opening claim text (preview).
What is claimed is: 1 . A computer-implemented method, comprising: receiving an invocation request for a first interface of an operating system from a client application, wherein the first interface is configured to obtain privacy data; obtaining first scenario information, wherein the first scenario information comprises a first element of the client application and a second element of the client application, wherein the second element is configured to be activated subsequent to the first element of the client application based on a use scenario of the first interface declared by the client application when the client application applies for an invocation permission of the first interface; obtaining current scenario information of the client application; and executing the invocation request in response to at least that the current scenario information matches the first scenario information, wherein the first scenario information comprises a page list, the first element of the client application includes a first page of the client application, the second element of the client application includes a second page, and the current scenario information comprises a current display page and a previous display page of the client application; and the executing the invocation request in response to at least that the current scenario information matches the first scenario information comprises: executing the invocation request in response to at least that the current display page matches the second element of the client application and the previous display page matches the first element of the client application, and wherein the first scenario information comprises an interface list, the first element of the client application includes a second interface of the client application that invokes the first interface, the second element of the client application includes a third interface of the client application that invokes the first interface, and the current scenario information comprises a current invoking interface and a previous invoking interface of the first interface; and the executing the invocation request in response to at least that the current scenario information matches the first scenario information comprises: executing the invocation request in response to at least that the current invoking interface matches the second element of the client application and the previous invoking interface matches the first element of the client application. 2 . The computer-implemented method of claim 1 , before the receiving the invocation request for the first interface of the operating system from the client application, further comprising: receiving an invocation permission application for an invocation permission of the first interface from the client application, wherein the invocation permission application comprises at least the use scenario of the first interface declared by the client application; and configuring the first scenario information based on the use scenario of the first interface declared by the client application. 3 . The computer-implemented method of claim 2 , wherein the invocation permission application further comprises identity information of the client application, and before the configuring the first scenario information, the computer-implemented method further comprises: determining, based on the identity information, whether the client application has the invocation permission of the first interface; and the configuring the first scenario information based on the use scenario of the first interface declared by the client application comprises: in response to at least that the client application has the invocation permission, configuring the first scenario information based on the use scenario of the first interface declared by the client application. 4 . An apparatus for interface invocation request processing, the apparatus comprising: one or more processors; and one or more computer-readable memories coupled to the one or more processors and having instructions stored thereon, wherein the instructions, when executed by the one or more processors, cause the one or more processors to perform operations comprising: receiving an invocation request for a first interface of an operating system from a client application, wherein the first interface is configured to obtain privacy data; obtaining first scenario information, wherein the first scenario information comprises a first element of the client application and a second element of the client application, wherein the second element is configured to be activated subsequent to the first element of the client application based on a use scenario of the first interface declared by the client application when the client application applies for an invocation permission of the first interface; obtaining current scenario information of the client application; and executing the invocation request in response to at least that the current scenario information matches the first scenario information, wherein the first scenario information comprises a page list, the first element of the client application includes a first page of the client application, the second element of the client application includes a second page, and the current scenario information comprises a current display page and a previous display page of the client application; and the executing the invocation request in response to at least that the current scenario information matches the first scenario information comprises: executing the invocation request in response to at least that the current display page matches the second element of the client application and the previous display page matches the first element of the client application, and wherein the first scenario information comprises an interface list, the first element of the client application includes a second interface of the client application that invokes the first interface, the second element of the client application includes a third interface of the client application that invokes the first interface, and the current scenario information comprises a current invoking interface and a previous invoking interface of the first interface; and the executing the invocation request in response to at least that the current scenario information matches the first scenario information comprises: executing the invocation request in response to at least that the current invoking interface matches the second element of the client application and the previous invoking interface matches the first element of the client application. 5 . The apparatus of claim 4 , wherein, before the receiving the invocation request for the first interface of the operating system from the client application, the operations further comprise: receiving an invocation permission application for the invocation permission of the first interface from the client application, wherein the invocation permission application comprises at least the use scenario of the first interface declared by the client application; and configuring the first scenario information based on the use scenario of the first interface declared by the client application. 6 . The apparatus of claim 5 , wherein the invocation permission application further comprises identity information of the client application, and before the configuring the first scenario information, the operations further comprise: determining, based on the identity information, whether the client application has the invocation permission of the first interface; and the configuring the first scenario information based on the use scenario of the first interface declared by the client application comprises: in response to at least that the client application has the
Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII] · CPC title
Specific access rights for resources, e.g. using capability register · CPC title
at program execution time, where the protection is within the operating system · CPC title
Interprogram communication · CPC title
Access rights, e.g. capability lists, access control lists, access tables, access matrices · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.