Interface invocation request processing methods and apparatuses

US12561474B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-12561474-B2
Application numberUS-202318507363-A
CountryUS
Kind codeB2
Filing dateNov 13, 2023
Priority dateMay 13, 2021
Publication dateFeb 24, 2026
Grant dateFeb 24, 2026

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

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.

First claim

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

Assignees

Inventors

Classifications

  • 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

  • G06F9/54Primary

    Interprogram communication · CPC title

  • Access rights, e.g. capability lists, access control lists, access tables, access matrices · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US12561474B2 cover?
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. F…
Who is the assignee on this patent?
Alipay Hangzhou Inf Tech Co Ltd
What technology area does this patent fall under?
Primary CPC classification G06F9/54. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Feb 24 2026 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 6 related publications on this page (citations in our corpus or others sharing the same primary CPC).