[go: up one dir, main page]

CN118672815A - Techniques for mitigating errors associated with software applications - Google Patents

Techniques for mitigating errors associated with software applications Download PDF

Info

Publication number
CN118672815A
CN118672815A CN202410301181.5A CN202410301181A CN118672815A CN 118672815 A CN118672815 A CN 118672815A CN 202410301181 A CN202410301181 A CN 202410301181A CN 118672815 A CN118672815 A CN 118672815A
Authority
CN
China
Prior art keywords
software application
user
user interface
indication
error
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202410301181.5A
Other languages
Chinese (zh)
Inventor
M·饶
K·I·科恩
N·J·休梅克
V·L·舒尔曼
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Apple Inc
Original Assignee
Apple Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US18/479,036 external-priority patent/US20240311220A1/en
Application filed by Apple Inc filed Critical Apple Inc
Publication of CN118672815A publication Critical patent/CN118672815A/en
Pending legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0718Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in an object-oriented system
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/079Root cause analysis, i.e. error or fault diagnosis
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0793Remedial or corrective actions

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Biomedical Technology (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本公开涉及用于缓解与软件应用相关的错误的技术。本文公开了一种用于缓解与软件应用相关的错误的技术。根据一些实施方案,该技术可以由服务器设备来实现,并且包括以下步骤:(1)识别与软件应用的用户相关联的至少一个错误,(2)识别与该用户相关联并且在其上安装有该软件应用的至少一个客户端设备;以及(3)向该至少一个客户端设备提供该至少一个错误的指示,以使得该软件应用在被加载和/或显示在该至少一个客户端设备上的同时:显示包括从该指示导出的信息的用户界面,其中该用户界面以防止该软件应用观察在该用户界面内发生的活动的方式从该软件应用进行沙箱化。

The present disclosure relates to techniques for mitigating errors associated with software applications. A technique for mitigating errors associated with software applications is disclosed herein. According to some embodiments, the technique may be implemented by a server device and includes the following steps: (1) identifying at least one error associated with a user of a software application, (2) identifying at least one client device associated with the user and having the software application installed thereon; and (3) providing an indication of the at least one error to the at least one client device so that the software application, while being loaded and/or displayed on the at least one client device: displays a user interface including information derived from the indication, wherein the user interface is sandboxed from the software application in a manner that prevents the software application from observing activities occurring within the user interface.

Description

用于缓解与软件应用相关的错误的技术Techniques for mitigating errors associated with software applications

技术领域Technical Field

所描述的实施方案阐述了用于缓解与软件应用相关的错误的技术。例如,该技术提供用于向软件应用的用户通知其支付凭据何时变为无效并且用于使得用户能够更新其支付凭据以缓解该无效的框架。The described embodiments set forth techniques for mitigating errors associated with software applications. For example, the techniques provide a framework for notifying users of software applications when their payment credentials become invalid and for enabling users to update their payment credentials to mitigate the invalidation.

背景技术Background Art

近年来,拥有和操作计算设备(例如,可穿戴设备、智能电话、平板设备等)的个人的数量已剧增。通常,个人全天使用他们的计算设备进行各种活动,例如拨打电话、发送和接收电子消息、访问互联网等。在一些情况下,安装在计算设备上的操作系统,特别是预先安装在操作系统上的本机软件应用,可以使得用户能够执行前述活动。然而,也可以安装第三方软件应用以使得用户能够执行附加的/增强的活动。例如,这些软件应用可包括社交网络软件应用、照片软件应用、游戏软件应用等。In recent years, the number of individuals who own and operate computing devices (e.g., wearable devices, smart phones, tablet devices, etc.) has increased dramatically. Typically, individuals use their computing devices throughout the day to perform a variety of activities, such as making phone calls, sending and receiving electronic messages, accessing the Internet, etc. In some cases, the operating system installed on the computing device, and particularly native software applications pre-installed on the operating system, can enable the user to perform the aforementioned activities. However, third-party software applications can also be installed to enable the user to perform additional/enhanced activities. For example, these software applications may include social networking software applications, photo software applications, game software applications, etc.

一种用于使得计算设备的用户能够利用软件应用的常见方法包括提供使得用户能够将软件应用下载到他们的计算设备上的软件应用商店,其在本文中被称为“应用商店”。具体地讲,应用商店使得软件应用的开发者能够将其软件应用连同描述、定价信息、屏幕快照等上载到应用商店。继而,用户可利用应用商店来探索和安装对他们来说有用/有趣的软件应用。例如,用户可使用特定关键字提交搜索查询以查找他们有兴趣下载的软件应用,可查看属于他们感兴趣的特定类别的所有软件应用(例如,游戏)等。又如,应用商店可以显示根据各种量度(例如,下载次数最多的软件应用、排名靠前的软件应用等)排名的软件应用,以使得用户能够识别当前在所有用户之中流行的软件应用。A common method for enabling users of computing devices to utilize software applications includes providing a software application store that enables users to download software applications to their computing devices, which is referred to herein as an "application store." Specifically, an application store enables developers of software applications to upload their software applications to the application store along with descriptions, pricing information, screenshots, etc. In turn, users can utilize the application store to explore and install software applications that are useful/interesting to them. For example, users can submit search queries using specific keywords to find software applications they are interested in downloading, can view all software applications that belong to a specific category of interest to them (e.g., games), etc. As another example, an application store can display software applications ranked according to various metrics (e.g., most downloaded software applications, top ranked software applications, etc.) to enable users to identify software applications that are currently popular among all users.

对于软件应用来说,为了最大限度地提高用户满意度,没有问题地执行是很重要的。值得注意的是,软件应用的支付结构根据其设计、其预期用户等存在很大差异。例如,一些软件应用可免费使用,一些软件应用提供“应用内购买”,一些软件应用需要预付和/或订阅支付,等等。就这一点而言,当涉及到维护准时和成功的软件应用支付时,维护有效的客户账单信息是至关重要的。此类账单信息可以包括例如有效的信用卡或借记卡号、有效的截止日期和有效的账单地址。如果没有有效账单信息,就无法处理支付,从而可能使收入来源紧张并且可能中断对用户期望的功能的访问。另外,当出现账单问题时,以既有效又非侵入性的方式通知用户可能是具有挑战性的。就这一点而言,软件开发人员可能不知道用于向用户通知账单问题以及推荐/促进补救措施的最有效方法。It is important for software applications to perform without problems in order to maximize user satisfaction. Notably, the payment structure of software applications varies widely depending on their design, their intended users, etc. For example, some software applications are free to use, some software applications offer "in-app purchases", some software applications require prepaid and/or subscription payments, etc. In this regard, maintaining valid customer billing information is critical when it comes to maintaining timely and successful software application payments. Such billing information may include, for example, a valid credit or debit card number, a valid expiration date, and a valid billing address. Without valid billing information, payments cannot be processed, which may strain revenue sources and may interrupt access to user-desired features. In addition, when billing issues arise, it may be challenging to notify users in a manner that is both effective and non-intrusive. In this regard, software developers may not be aware of the most effective methods for notifying users of billing issues and recommending/facilitating remedial actions.

发明内容Summary of the invention

所描述的实施方案阐述了用于缓解与软件应用相关的错误的技术。例如,该技术提供用于向软件应用的用户通知其支付凭据何时变为无效并且用于使得用户能够更新其支付凭据以缓解该无效的框架。The described embodiments set forth techniques for mitigating errors associated with software applications. For example, the techniques provide a framework for notifying users of software applications when their payment credentials become invalid and for enabling users to update their payment credentials to mitigate the invalidation.

一个实施方案阐述了一种用于缓解与软件应用相关的错误的方法。根据一些实施方案,该方法可以在服务器设备处实现,并且包括以下步骤:One embodiment describes a method for mitigating errors associated with software applications. According to some embodiments, the method can be implemented at a server device and includes the following steps:

(1)识别与软件应用的用户相关联的至少一个错误,(2)识别与该用户相关联并且在其上安装有该软件应用的至少一个客户端设备,以及(3)向该至少一个客户端设备提供该至少一个错误的指示,以使得该软件应用在被加载和/或显示在该至少一个客户端设备上的同时:显示包括从该指示导出的信息的用户界面,其中该用户界面以防止该软件应用观察在该用户界面内发生的活动的方式从该软件应用进行沙箱化。(1) identifying at least one error associated with a user of a software application, (2) identifying at least one client device associated with the user and on which the software application is installed, and (3) providing an indication of the at least one error to the at least one client device so that the software application, while loaded and/or displayed on the at least one client device: displays a user interface including information derived from the indication, wherein the user interface is sandboxed from the software application in a manner that prevents the software application from observing activities occurring within the user interface.

另一实施方案阐述了一种用于缓解与软件应用相关的错误的方法。根据一些实施方案,该方法可以在客户端设备处实现,并且包括以下步骤:Another embodiment describes a method for mitigating errors associated with software applications. According to some embodiments, the method can be implemented at a client device and includes the following steps:

(1)从服务器设备接收与安装在该客户端设备上的软件应用相关联的至少一个错误的指示,(2)存储该指示,(3)检测该软件应用的启动和/或显示,(4)提示该软件应用对显示与该至少一个错误的该指示相关联的信息的许可,以及(5)响应于接收到来自该软件应用的许可:使得该软件应用显示包括该信息的用户界面,其中该用户界面以防止该软件应用观察在该用户界面内发生的活动的方式从该软件应用进行沙箱化。(1) receiving from a server device an indication of at least one error associated with a software application installed on the client device, (2) storing the indication, (3) detecting launching and/or displaying of the software application, (4) prompting the software application for permission to display information associated with the indication of the at least one error, and (5) in response to receiving the permission from the software application: causing the software application to display a user interface including the information, wherein the user interface is sandboxed from the software application in a manner that prevents the software application from observing activities occurring within the user interface.

其他实施方案包括一种被配置为存储指令的非暂态计算机可读存储介质,该指令当由被包括在计算设备中的处理器执行时使得该计算设备执行上述方法中的任一方法的各步骤。另外的实施方案包括被配置为执行前述方法中任何方法的各种步骤的计算设备。Other embodiments include a non-transitory computer-readable storage medium configured to store instructions that, when executed by a processor included in a computing device, cause the computing device to perform the steps of any of the above methods. Additional embodiments include a computing device configured to perform various steps of any of the above methods.

根据结合以举例的方式示出所述实施方案的原理的附图而进行的以下详细描述,本文所述的实施方案的其他方面和优点将变得显而易见。Other aspects and advantages of the embodiments described herein will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, which illustrate by way of example the principles of the embodiments.

附图说明BRIEF DESCRIPTION OF THE DRAWINGS

所包括的附图用于说明性目的,并且仅用于提供所公开的用于提供无线计算设备的本发明装置和方法的可能的结构和布置方式的示例。这些附图决不限制本领域的技术人员在不脱离实施方案的实质和范围的情况下可对实施方案作出的在形式和细节上的任何改变。该实施方案通过以下结合附图的详细描述将易于理解,其中相似的附图标号指代相似的结构元件。The included drawings are for illustrative purposes and are only used to provide examples of possible structures and arrangements of the disclosed apparatus and methods for providing wireless computing devices. These drawings in no way limit any changes in form and detail that may be made to the embodiments by those skilled in the art without departing from the spirit and scope of the embodiments. The embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings, in which like reference numerals refer to like structural elements.

图1示出了根据一些实施方案的被配置为实现本文所述的各种技术的系统的不同部件的框图。1 illustrates a block diagram of different components of a system configured to implement the various techniques described herein, according to some embodiments.

图2示出了根据一些实施方案的用于缓解与软件应用相关的错误的技术的详细时序图。2 illustrates a detailed timing diagram of a technique for mitigating errors associated with software applications, according to some embodiments.

图3A至图3B示出根据一些实施方案的用于缓解与软件应用相关的错误的方法。3A-3B illustrate methods for mitigating errors associated with software applications according to some embodiments.

图4A至图4B示出根据一些实施方案的可以在客户端计算设备上显示的示例用户界面的概念图。4A-4B illustrate conceptual diagrams of example user interfaces that may be displayed on a client computing device according to some embodiments.

图5示出了根据一些实施方案的可用于实现本文所述的各个部件的计算设备的详细视图。5 illustrates a detailed view of a computing device that may be used to implement the various components described herein, according to some embodiments.

具体实施方式DETAILED DESCRIPTION

在本部分中提供了根据本发明所述的实施方案的装置和方法的代表性应用。提供这些示例仅为了添加上下文并有助于理解所描述的实施方案。因此对于本领域的技术人员将显而易见的是,当前描述的实施方案可在不具有这些具体细节中的一些或所有的情况下被实践。在其他实例中,未详细描述众所周知的工艺步骤,以便避免不必要地使当前描述的实施方案晦涩难懂。其它应用是可能的,使得以下示例不应被当作是限制性的。Representative applications of the apparatus and methods according to the embodiments described in the present invention are provided in this section. These examples are provided only to add context and to help understand the described embodiments. It will therefore be apparent to those skilled in the art that the embodiments currently described may be practiced without some or all of these specific details. In other instances, well-known process steps are not described in detail to avoid unnecessarily obscuring the embodiments currently described. Other applications are possible, so that the following examples should not be considered restrictive.

所描述的实施方案阐述了用于缓解与软件应用相关的错误的技术。例如,该技术提供用于向软件应用的用户通知其支付凭据何时变为无效并且用于使得用户能够更新其支付凭据以缓解该无效的框架。The described embodiments set forth techniques for mitigating errors associated with software applications. For example, the techniques provide a framework for notifying users of software applications when their payment credentials become invalid and for enabling users to update their payment credentials to mitigate the invalidation.

应注意,虽然以下公开内容主要集中于与软件应用相关联的与支付相关的错误,但实施方案决不限于这一范围。相反,实施方案适用于可能与软件应用相关联地出现的所有可想到的错误、问题等,诸如与用户账户、账单、配置等相关的错误、问题等。It should be noted that while the following disclosure focuses primarily on payment-related errors associated with software applications, the embodiments are by no means limited to this scope. Rather, the embodiments apply to all conceivable errors, problems, etc. that may arise in association with software applications, such as errors, problems, etc. related to user accounts, billing, configuration, etc.

图1示出了根据一些实施方案的可实现本文所述的各种技术的系统100的不同部件的框图。如图1所示,系统100可以包括一个或多个服务器计算设备102,这些服务器计算设备使得客户端计算设备114(例如,智能电话、平板设备、膝上型计算机、台式计算机等)的用户能够访问由服务器计算设备102托管的软件应用商店(图1中未示出)。在一些实施方案中,软件应用商店可以使得软件开发人员能够上载软件应用104以使其通过软件应用商店可获得。相反地,客户端计算设备114可以执行在本文中被称为软件应用商店客户端的对应软件应用(图1中未示出),其使得客户端计算设备114能够与由服务器计算设备102实现的软件应用商店交互。例如,软件应用商店客户端(在给定客户端计算设备114上执行)可以使得用户能够浏览他们可能有兴趣下载和安装的软件应用104,例如生产力软件应用、社交网络软件应用、游戏软件应用等。继而,当用户识别出感兴趣的特定软件应用104时,软件应用商店客户端可使得客户端计算设备114以无缝方式将软件应用104下载并安装到客户端计算设备114上。随后,用户可在其客户端计算设备114上访问软件应用104。FIG. 1 shows a block diagram of different components of a system 100 that can implement various technologies described herein according to some embodiments. As shown in FIG. 1 , the system 100 may include one or more server computing devices 102 that enable users of client computing devices 114 (e.g., smart phones, tablet devices, laptop computers, desktop computers, etc.) to access a software application store (not shown in FIG. 1 ) hosted by the server computing device 102. In some embodiments, the software application store may enable software developers to upload software applications 104 to make them available through the software application store. Conversely, the client computing device 114 may execute a corresponding software application (not shown in FIG. 1 ) referred to herein as a software application store client, which enables the client computing device 114 to interact with the software application store implemented by the server computing device 102. For example, a software application store client (executed on a given client computing device 114) may enable users to browse software applications 104 that they may be interested in downloading and installing, such as productivity software applications, social networking software applications, game software applications, etc. Then, when the user identifies a particular software application 104 of interest, the software application store client can cause the client computing device 114 to download and install the software application 104 in a seamless manner onto the client computing device 114. The user can then access the software application 104 on his client computing device 114.

简言之,需注意,本文所公开的实施方案不限于包括软件应用商店/软件应用商店客户端的前述架构。相反,服务器计算设备102可被配置为独立于软件应用商店的实现或在没有软件应用商店的实现的情况下提供本文所述的各种功能性。例如,服务器计算设备102可被配置为识别并帮助缓解与在客户端计算设备114上使用软件应用104相关而出现的支付凭据问题。此外,客户端计算设备114可被配置为独立于软件应用商店客户端的实现或在没有软件应用商店客户端的实现的情况下提供本文所述的各种功能性。例如,客户端计算设备114可被配置为安装、加载、显示等软件应用104,而不与软件应用商店交互(通常被称为“侧加载”)并且不与服务器计算设备102交互,即可获得本文所述的支付凭据问题识别/缓解技术的有益效果。In short, it should be noted that the embodiments disclosed herein are not limited to the aforementioned architecture including software application stores/software application store clients. Instead, the server computing device 102 may be configured to provide the various functionalities described herein independently of the implementation of the software application store or without the implementation of the software application store. For example, the server computing device 102 may be configured to identify and help mitigate payment credential issues associated with the use of the software application 104 on the client computing device 114. In addition, the client computing device 114 may be configured to provide the various functionalities described herein independently of the implementation of the software application store client or without the implementation of the software application store client. For example, the client computing device 114 may be configured to install, load, display, etc. the software application 104 without interacting with the software application store (commonly referred to as "side loading") and without interacting with the server computing device 102, and the beneficial effects of the payment credential problem identification/mitigation technology described herein can be obtained.

在任何情况下,如图1所示,每个客户端计算设备114可以具有安装在其上的任何数量的软件应用104,并且可以实现被配置为促进软件应用104的安装、执行(例如,加载、显示等)等的软件应用管理器116。每个客户端计算设备114还可以与用户配置文件106相关联。例如,当客户端计算设备114的用户使用客户端计算设备114提供创建、登录用户配置文件106等必要信息时,可以建立此类关联。根据一些实施方案,用户配置文件106可以包括用户名/密码信息、与用户相关联的联系信息、与用户相关联的人口统计信息等。需注意,前述示例并非旨在为限制性的,并且在不脱离本公开的范围的情况下,用户配置文件106可以以任何粒度级别存储任何用户相关(或其他)信息。用户配置文件106还可包括与用户相关联的一个或多个支付凭据108,该一个或多个支付凭据可包括信用卡信息、礼品卡信息、借记卡信息、银行账户信息等。需注意,前述示例并非旨在为限制性的,并且在不脱离本公开的范围的情况下,支付凭据108可以以任何粒度级别存储任何支付相关(或其他)信息。In any case, as shown in FIG. 1 , each client computing device 114 may have any number of software applications 104 installed thereon, and may implement a software application manager 116 configured to facilitate the installation, execution (e.g., loading, displaying, etc.) of the software applications 104. Each client computing device 114 may also be associated with a user profile 106. For example, such an association may be established when a user of the client computing device 114 provides necessary information for creating, logging into, etc. a user profile 106 using the client computing device 114. According to some embodiments, the user profile 106 may include username/password information, contact information associated with the user, demographic information associated with the user, etc. It should be noted that the foregoing examples are not intended to be limiting, and the user profile 106 may store any user-related (or other) information at any level of granularity without departing from the scope of the present disclosure. The user profile 106 may also include one or more payment credentials 108 associated with the user, which may include credit card information, gift card information, debit card information, bank account information, etc. Note that the foregoing examples are not intended to be limiting, and payment credentials 108 may store any payment-related (or other) information at any level of granularity without departing from the scope of the present disclosure.

如图1所示,服务器计算设备102可以将任意数量的用户配置文件106与给定的软件应用104相关联。此类关联可例如在给定软件应用104与已将软件应用104安装在至少一个客户端计算设备114上的用户的用户配置文件106之间形成。尽管图1中未示出,但服务器计算设备102可管理使得给定用户能够将不同支付凭据108用于不同软件应用104的信息。例如,用户可能更愿意使用第一支付凭据108来为第一软件应用104提供支付,并且使用第二支付凭据108来为第二软件应用104提供支付。就这一点而言,服务器计算设备102可以将一信息例如与软件应用104、用户配置文件106等一起存储,该信息针对与给定软件应用104相关联的每个用户配置文件106指示用户对该软件应用104的首选支付凭据108。As shown in FIG1 , the server computing device 102 may associate any number of user profiles 106 with a given software application 104. Such an association may be formed, for example, between a given software application 104 and a user profile 106 of a user who has installed the software application 104 on at least one client computing device 114. Although not shown in FIG1 , the server computing device 102 may manage information that enables a given user to use different payment credentials 108 for different software applications 104. For example, a user may prefer to use a first payment credential 108 to provide payment for a first software application 104, and a second payment credential 108 to provide payment for a second software application 104. In this regard, the server computing device 102 may store information, such as with the software applications 104, the user profiles 106, etc., that indicates, for each user profile 106 associated with a given software application 104, the user's preferred payment credential 108 for that software application 104.

另外,服务器计算设备102可被配置为实现支付凭据管理器110,该支付凭据管理器评估与用户配置文件106相关联的支付凭据108的有效性。在一些情况下,支付凭据管理器110可以自确定给定支付凭据108的有效性。例如,如果当前日期超过支付凭据108的到期日期,则支付凭据管理器110可以可靠地断定支付凭据108是无效的。又如,如果可用余额、信用额度等不足以满足即将到来的支付(例如,即将到来的将到期的订阅费),则支付凭据管理器110可以可靠地断定支付凭据是无效的。Additionally, the server computing device 102 may be configured to implement a payment credential manager 110 that evaluates the validity of the payment credential 108 associated with the user profile 106. In some cases, the payment credential manager 110 may self-determine the validity of a given payment credential 108. For example, if the current date is beyond the expiration date of the payment credential 108, then the payment credential manager 110 may reliably conclude that the payment credential 108 is invalid. As another example, if the available balance, credit line, etc. is insufficient to satisfy an upcoming payment (e.g., an upcoming subscription fee that is due), then the payment credential manager 110 may reliably conclude that the payment credential is invalid.

在其他情况下,支付凭据管理器110可与支付处理器112交互以确定支付凭据是否有效。例如,支付凭据管理器110可以向支付处理器112提供给定的支付凭据108以接收关于支付凭据108的有效性的指示。支付凭据108的这种提供可以例如周期性地、有条件地等等来执行。又如,当给定的支付凭据108已变得无效时,可由支付处理器112通知支付凭据管理器110。例如,当支付凭据管理器110尝试使用根据支付处理器112而无效的支付凭据108来促成交易时,可出现此类通知。需注意,前述示例并非旨在为限制性的,并且服务器计算设备102可以利用任何方法来有效地识别无效的支付凭据108。In other cases, the payment credential manager 110 may interact with the payment processor 112 to determine whether the payment credential is valid. For example, the payment credential manager 110 may provide a given payment credential 108 to the payment processor 112 to receive an indication of the validity of the payment credential 108. Such provision of the payment credential 108 may be performed, for example, periodically, conditionally, and the like. As another example, the payment credential manager 110 may be notified by the payment processor 112 when a given payment credential 108 has become invalid. For example, such a notification may occur when the payment credential manager 110 attempts to facilitate a transaction using a payment credential 108 that is invalid according to the payment processor 112. It is noted that the foregoing examples are not intended to be limiting, and the server computing device 102 may utilize any method to effectively identify an invalid payment credential 108.

根据一些实施方案,支付凭据管理器110可在识别出给定支付凭据108无效后采取任何数量的动作来补救问题。如图1所示,此类动作可包括在适当情况下提供一个或多个无效支付凭据指示118。例如,服务器计算设备102可识别将受无效支付凭据108影响的一个或多个软件应用104。所识别的一个或多个软件应用104可包括例如具有将在阈值时间周期内到期并且依赖于支付凭据108进行支付的订阅费、续订费、升级费等的软件应用。继而,服务器计算设备102可识别其上安装有一个或多个软件应用104的一个或多个客户端计算设备114。随后,服务器计算设备102可以向所识别的一个或多个客户端计算设备114上的软件应用管理器116提供无效支付凭据指示118。这样并且如本文更详细描述的,软件应用管理器116可有效地向用户通知该问题,以及提供补救该问题的途径。According to some embodiments, the payment credential manager 110 may take any number of actions to remedy the problem after identifying that a given payment credential 108 is invalid. As shown in FIG. 1 , such actions may include providing one or more invalid payment credential indications 118 where appropriate. For example, the server computing device 102 may identify one or more software applications 104 that will be affected by the invalid payment credential 108. The identified one or more software applications 104 may include, for example, software applications that have subscription fees, renewal fees, upgrade fees, etc. that will expire within a threshold time period and rely on the payment credential 108 for payment. Subsequently, the server computing device 102 may identify one or more client computing devices 114 on which the one or more software applications 104 are installed. Subsequently, the server computing device 102 may provide the invalid payment credential indication 118 to the software application manager 116 on the identified one or more client computing devices 114. In this way, and as described in more detail herein, the software application manager 116 can effectively notify the user of the problem and provide a way to remedy the problem.

应当理解,为了简化起见,图1例示的计算设备的各种部件以高层级给出。例如,尽管图1中未例示,但应当理解,各种计算设备可包括能够实现上述软件实体的常见硬件/软件部件。例如,计算设备中的每一者可包括一个或多个处理器,处理器与一个或多个易失性存储器(例如,动态随机存取存储器(DRAM))和一个或多个存储设备(例如,硬盘驱动器、固态驱动器(SSD)等)协同,使得能够执行本文所述的各种软件实体。此外,每个计算设备可包括使得计算设备能够在彼此之间传送信息(例如,使用互联网)的通信部件。It should be understood that, for simplicity, the various components of the computing device illustrated in FIG. 1 are given at a high level. For example, although not illustrated in FIG. 1 , it should be understood that various computing devices may include common hardware/software components that can implement the above-mentioned software entities. For example, each of the computing devices may include one or more processors that cooperate with one or more volatile memories (e.g., dynamic random access memory (DRAM)) and one or more storage devices (e.g., hard disk drives, solid-state drives (SSDs), etc.) to enable the execution of various software entities described herein. In addition, each computing device may include a communication component that enables the computing devices to transmit information (e.g., using the Internet) between each other.

下面结合图5提供了对这些硬件部件的更详细说明。另外,应当理解,在不脱离本公开的范围的情况下,计算设备可包括能够实现本文所述的各种技术的附加实体。还应当理解,在不脱离本公开的范围的情况下,本文所述的实体可被组合或分割成额外的实体。还应当理解,在不脱离本公开的范围的情况下,可使用基于软件或基于硬件的方法来实现本文所述的各种实体。A more detailed description of these hardware components is provided below in conjunction with FIG. 5 . In addition, it should be understood that a computing device may include additional entities capable of implementing the various techniques described herein without departing from the scope of the present disclosure. It should also be understood that the entities described herein may be combined or split into additional entities without departing from the scope of the present disclosure. It should also be understood that software-based or hardware-based methods may be used to implement the various entities described herein without departing from the scope of the present disclosure.

因此,图1提供了根据一些实施方案的系统100(具体地讲,服务器计算设备102和客户端计算设备114)可实现本文所述各种技术的方式的概述。现在将在下文结合图2、图3A至图3B和图4A至图4B提供可实现这些技术的方式的更详细分解。Thus, Figure 1 provides an overview of the manner in which the system 100 (specifically, the server computing device 102 and the client computing device 114) can implement various techniques described herein according to some embodiments. A more detailed breakdown of the manner in which these techniques can be implemented will now be provided below in conjunction with Figures 2, 3A-3B, and 4A-4B.

图2示出了根据一些实施方案的用于缓解与软件应用相关的错误的技术的详细时序图。如图2所示,时序图开始于步骤202,其中服务器计算设备102(例如,在服务器计算设备102上执行的支付凭据管理器110)确定与软件应用104相关联的用户的支付凭据108是无效的。支付凭据管理器110可使用本文所述技术中的任一技术来做出这种确定,例如通过自确定无效性、通过从支付处理器112接收指示等等。FIG2 illustrates a detailed timing diagram of a technique for mitigating errors associated with software applications according to some embodiments. As shown in FIG2 , the timing diagram begins at step 202, where the server computing device 102 (e.g., the payment credential manager 110 executed on the server computing device 102) determines that the payment credential 108 of the user associated with the software application 104 is invalid. The payment credential manager 110 may make such a determination using any of the techniques described herein, such as by self-determining invalidity, by receiving an indication from the payment processor 112, and the like.

在步骤204,支付凭据管理器110向在其上安装有软件应用104的客户端计算设备114上执行的软件应用管理器116提供对无效支付凭据108的指示。根据一些实施方案,该指示可以与也跟软件应用104相关联的唯一标识符相关联。简言之,需注意,为了简单起见,本文所述的实施方案和示例主要论述与单个客户端计算设备114交互的服务器计算设备102/支付凭据管理器110。然而,如上文结合图1所述,支付凭据管理器110可向软件应用104也安装于其上的其他客户端计算设备114上的其他软件应用管理器116提供指示。这在软件应用104被安装在同一用户的两个或更多个客户端计算设备114上的情况下可为有用的,因为可以在该用户碰巧操作的任何客户端计算设备114上向用户通知该问题(如下所述)。At step 204, the payment credential manager 110 provides an indication of the invalid payment credential 108 to a software application manager 116 executing on the client computing device 114 on which the software application 104 is installed. According to some embodiments, the indication may be associated with a unique identifier that is also associated with the software application 104. In brief, it is noted that, for simplicity, the embodiments and examples described herein primarily discuss a server computing device 102/payment credential manager 110 interacting with a single client computing device 114. However, as described above in conjunction with FIG. 1 , the payment credential manager 110 may provide indications to other software application managers 116 on other client computing devices 114 on which the software application 104 is also installed. This may be useful in situations where the software application 104 is installed on two or more client computing devices 114 of the same user, as the user may be notified of the problem (as described below) on any client computing device 114 that the user happens to be operating.

在步骤206,软件应用管理器116从支付凭据管理器110接收到该指示,并且将该指示存储于客户端计算设备114能够访问的存储装置(例如,本地存储装置、网络存储装置、云存储装置等)中。同样,当指示被发送到多个客户端计算设备114时,每个客户端计算设备114可以使用前述方法(或适合于客户端计算设备114的配置的替代方法)来存储该指示。At step 206, the software application manager 116 receives the indication from the payment credential manager 110 and stores the indication in a storage device (e.g., a local storage device, a network storage device, a cloud storage device, etc.) accessible to the client computing device 114. Likewise, when the indication is sent to multiple client computing devices 114, each client computing device 114 may store the indication using the aforementioned method (or an alternative method suitable for the configuration of the client computing device 114).

在步骤208,在客户端计算设备114上加载和/或显示软件应用104。如图2所示,加载和/或显示软件应用104可以涉及软件应用104和软件应用管理器116两者。例如,软件应用管理器116可以接收加载和/或显示软件应用104的请求(例如,通过选择与软件应用104相关联的图标),然后采取适当动作来处理该请求。例如,当客户端计算设备114的用户利用用户界面首次加载软件应用104(相对于客户端计算设备114的最后一次重置)以显示软件应用104(在其已被加载之后)等等时,可以发出该请求。就这一点而言,并且如下文更详细描述的,软件应用管理器116可以基于结合步骤206存储的指示来识别是否应当响应于软件应用104被加载和/或显示而采取附加动作。At step 208, the software application 104 is loaded and/or displayed on the client computing device 114. As shown in FIG. 2, loading and/or displaying the software application 104 may involve both the software application 104 and the software application manager 116. For example, the software application manager 116 may receive a request to load and/or display the software application 104 (e.g., by selecting an icon associated with the software application 104), and then take appropriate actions to process the request. For example, the request may be issued when a user of the client computing device 114 utilizes a user interface to load the software application 104 for the first time (relative to the last reset of the client computing device 114), to display the software application 104 (after it has been loaded), etc. In this regard, and as described in more detail below, the software application manager 116 may identify whether additional actions should be taken in response to the software application 104 being loaded and/or displayed based on the indication stored in conjunction with step 206.

在步骤210,软件应用管理器116结合加载和/或显示软件应用104来识别该指示(在步骤206处所接收/存储的)。例如,可以通过确定与软件应用104相关联的唯一标识符是否与存储在客户端计算设备114上的任何指示的唯一标识符相匹配来实现该识别。继而,响应于识别具有匹配标识符的指示,软件应用管理器116向支付凭据管理器110发出对支付凭据无效性信息的请求。At step 210, the software application manager 116 identifies the indication (received/stored at step 206) in conjunction with loading and/or displaying the software application 104. This identification may be accomplished, for example, by determining whether a unique identifier associated with the software application 104 matches a unique identifier of any indication stored on the client computing device 114. Then, in response to identifying an indication having a matching identifier, the software application manager 116 issues a request to the payment credential manager 110 for payment credential invalidity information.

在步骤212,支付凭据管理器110向软件应用管理器116提供支付凭据无效性信息。支付凭据无效性信息可以包括任何粒度级别的任何信息,这些信息有效地用于向用户通知有关支付凭据108的问题的性质。例如,支付凭据无效性信息可包括网页的统一资源定位符(URL),该网页在被呈现于客户端计算设备114上时有效地传达有关支付凭据108的问题的性质。又如,支付凭据无效性信息可包括超文本标记语言(HTML)代码,该HTML代码在被呈现于客户端计算设备114上时构成有效地传达有关支付凭据108的问题的性质的网页。又如,支付凭据无效性信息可包括二进制(例如,blob)信息,该二进制信息在被呈现于客户端计算设备114上时构成有效地传达有关支付凭据108的问题的性质的图像、视频、交互式用户界面等。需注意,前述示例并非旨在为限制性的,并且在不脱离本公开的范围的情况下,支付凭据无效性信息可采取有效地用于传达有关支付凭据的问题的性质的任何形式。At step 212, the payment credential manager 110 provides the payment credential invalidity information to the software application manager 116. The payment credential invalidity information may include any information at any level of granularity that is effective for notifying the user of the nature of the problem with the payment credential 108. For example, the payment credential invalidity information may include a uniform resource locator (URL) of a web page that, when presented on the client computing device 114, effectively communicates the nature of the problem with the payment credential 108. As another example, the payment credential invalidity information may include hypertext markup language (HTML) code that, when presented on the client computing device 114, constitutes a web page that effectively communicates the nature of the problem with the payment credential 108. As another example, the payment credential invalidity information may include binary (e.g., blob) information that, when presented on the client computing device 114, constitutes an image, video, interactive user interface, etc. that effectively communicates the nature of the problem with the payment credential 108. It is noted that the foregoing examples are not intended to be limiting, and the payment credential invalidity information may take any form that is effective for communicating the nature of the problem with the payment credential without departing from the scope of the present disclosure.

另外,支付凭据无效性信息可以包括任何粒度级别的任何信息,这些信息有效地用于使得用户能够缓解有关支付凭据的问题。例如,支付凭据无效性信息信息可包括网页的URL,该网页在被呈现于客户端计算设备114上时使得用户能够更新支付凭据108、提供新的支付凭据108等等。又如,支付凭据无效性信息可包括HTML代码,该HTML代码在被呈现于客户端计算设备114上时构成使得用户能够更新支付凭据108、提供新的支付凭据108等的网页。又如,支付凭据无效性信息可包括二进制(例如,blob)信息,该二进制信息在被呈现于客户端计算设备114上时构成使得用户能够更新支付凭据108、提供新的支付凭据108等的交互式用户界面。需注意,前述示例并非旨在为限制性的,并且在不脱离本公开的范围的情况下,支付凭据无效性信息可采取可用于有效地使得用户能够缓解有关支付凭据108的问题的任何形式。In addition, the payment credential invalidity information may include any information at any level of granularity that is effective for enabling a user to mitigate issues with payment credentials. For example, the payment credential invalidity information may include a URL of a web page that, when presented on the client computing device 114, enables a user to update the payment credential 108, provide a new payment credential 108, and the like. For another example, the payment credential invalidity information may include HTML code that, when presented on the client computing device 114, constitutes a web page that enables a user to update the payment credential 108, provide a new payment credential 108, and the like. For another example, the payment credential invalidity information may include binary (e.g., blob) information that, when presented on the client computing device 114, constitutes an interactive user interface that enables a user to update the payment credential 108, provide a new payment credential 108, and the like. It is noted that the foregoing examples are not intended to be limiting, and that the payment credential invalidity information may take any form that is effective for enabling a user to mitigate issues with payment credentials 108 without departing from the scope of the present disclosure.

需注意,在不脱离本发明的范围的情况下,可使用任何方法来格式化支付凭据无效性信息。例如,每个软件应用104可与支付凭据无效性信息可被格式化成的相应模板相关联。又如,特定模板可用于特定类型的软件应用104,例如,第一模板可用于基于订阅的软件应用104,第二模板可用于提供应用内购买的软件应用104,等等。需注意,前述示例并非旨在为限制性的,并且在不脱离本公开的范围的情况下,服务器计算设备102可利用任何粒度/特异性级别的任何数量的模板(等等)。It is noted that any method may be used to format the payment credential invalidity information without departing from the scope of the present invention. For example, each software application 104 may be associated with a corresponding template into which the payment credential invalidity information may be formatted. As another example, a particular template may be used for a particular type of software application 104, e.g., a first template may be used for a subscription-based software application 104, a second template may be used for a software application 104 that offers in-app purchases, and so on. It is noted that the foregoing examples are not intended to be limiting, and that the server computing device 102 may utilize any number of templates (etc.) at any level of granularity/specificity without departing from the scope of the present disclosure.

简言之,尽管在图2中未示出,但支付凭据管理器110可以在提供支付凭据无效性信息之前冗余地确定支付凭据108是否仍然无效(例如,通过重新执行步骤202)。这在支付凭据108在步骤202与步骤210之间的任何时间从无效转变为有效的情况下可为有利的。例如,当账户冻结被解除时、礼品卡余额增加时、可用信用额度增加时等等,可能发生此类转变。在/当这种情况发生的情况下,支付凭据管理器110可在步骤212处改为提供支付凭据108有效的指示。继而,软件应用管理器116可以从存储装置中移除该指示,并且可以忽略图2的时序图中的其余步骤。In short, although not shown in FIG. 2 , the payment credential manager 110 may redundantly determine whether the payment credential 108 is still invalid (e.g., by re-performing step 202) before providing payment credential invalidity information. This may be advantageous in the event that the payment credential 108 transitions from invalid to valid at any time between step 202 and step 210. For example, such a transition may occur when an account freeze is lifted, a gift card balance increases, an available credit line increases, and the like. In/when this occurs, the payment credential manager 110 may instead provide an indication that the payment credential 108 is valid at step 212. The software application manager 116 may then remove the indication from the storage device and the remaining steps in the timing diagram of FIG. 2 may be ignored.

现在返回图2,在步骤214,软件应用管理器116向软件应用104发出对显示支付凭据无效性信息的许可的请求。可使用有效地用于使得客户端计算设备114上的软件实体能够彼此通信的任何方法将该请求提供至软件应用104。例如,软件应用管理器116/软件应用104可以实现软件开发工具包(SDK)、应用编程接口(API)等,它们使得(1)软件应用管理器116能够将该请求发送至软件应用104并且使得(2)软件应用104能够接收/解译该请求。有利地,此类请求可以向与软件应用104相关联的被授权实体(例如,开发商、发行商等)提供抑制支付凭据无效性信息显示的能力。例如,在被授权实体计划增强软件应用104的功能、提高其定价等的情况下,这可为有用的,其中在已进行更新之后提示用户进行支付将更可能使得用户更新其支付凭据108以便可进行支付。Returning now to FIG. 2 , at step 214 , the software application manager 116 issues a request to the software application 104 for permission to display payment credential invalidity information. The request may be provided to the software application 104 using any method effective for enabling software entities on the client computing device 114 to communicate with each other. For example, the software application manager 116/software application 104 may implement a software development kit (SDK), an application programming interface (API), etc., which enables (1) the software application manager 116 to send the request to the software application 104 and (2) the software application 104 to receive/interpret the request. Advantageously, such a request may provide an authorized entity (e.g., a developer, a publisher, etc.) associated with the software application 104 with the ability to suppress the display of payment credential invalidity information. This may be useful, for example, in the event that the authorized entity plans to enhance the functionality of the software application 104, increase its pricing, etc., where prompting the user to make payment after an update has been made will make it more likely that the user will update their payment credentials 108 so that payment can be made.

继而,在步骤216,软件应用104向软件应用管理器116授予许可。根据一些实施方案,软件应用104可使用与上文结合步骤214所述的用于发送请求的方法相同(或不同)的方法来授予许可。需注意,当软件应用104拒绝许可时,软件应用管理器116可采取各种动作。例如,软件应用管理器116可将该指示保持在存储装置中,以便在每次发生步骤208时执行步骤210到214。又如,软件应用管理器116可根据对许可的拒绝而选择周期性地(例如,在每次、每隔一次软件应用104被加载/显示时等等)提示软件应用104。需注意,前述示例并非旨在限制性的,并且在不脱离本公开的范围的情况下,软件应用管理器116可响应于接收到来自软件应用104的拒绝而采取任何形式的任何动作,而不脱离本发明的范围。Then, at step 216, the software application 104 grants the permission to the software application manager 116. According to some embodiments, the software application 104 may grant the permission using the same (or different) method as described above in conjunction with step 214 for sending the request. It is noted that when the software application 104 denies the permission, the software application manager 116 may take a variety of actions. For example, the software application manager 116 may retain the indication in a storage device so that steps 210 to 214 are performed each time step 208 occurs. As another example, the software application manager 116 may choose to prompt the software application 104 periodically (e.g., each time, every other time the software application 104 is loaded/displayed, etc.) based on the denial of the permission. It is noted that the foregoing examples are not intended to be limiting, and the software application manager 116 may take any action of any form in response to receiving a denial from the software application 104 without departing from the scope of the present disclosure.

在步骤218,软件应用管理器116命令软件应用104显示支付凭据无效性信息。该步骤可以使用与上文分别结合步骤214/216所述的用于发送请求/许可的方法相同(或不同)的方法来实现。At step 218, the software application manager 116 instructs the software application 104 to display payment credential invalidity information. This step may be implemented using the same (or different) methods as described above in connection with steps 214/216, respectively, for sending requests/permissions.

在步骤220,软件应用管理器116/软件应用104通过从软件应用104沙箱化的用户界面显示(1)支付凭据无效性信息和(2)用于缓解无效性的方法(即,机制)。简言之,如本文所述,从软件应用104对用户界面进行沙盒化包括禁止软件应用104查看在用户界面内发生的活动。此类活动可以包括例如显示支付凭据无效性信息、接收输入(例如,经更新的支付凭据)等等。这样,软件应用104可了解正在发生账单问题(例如,通过步骤214和216),但不了解账单问题的具体性质以及通过用户界面进行的任何补救措施。At step 220, the software application manager 116/software application 104 displays (1) the payment credential invalidity information and (2) the method (i.e., mechanism) for mitigating the invalidity via a user interface that is sandboxed from the software application 104. In short, as described herein, sandboxing the user interface from the software application 104 includes prohibiting the software application 104 from viewing activities occurring within the user interface. Such activities may include, for example, displaying payment credential invalidity information, receiving input (e.g., updated payment credentials), and the like. In this way, the software application 104 may be aware that a billing problem is occurring (e.g., via steps 214 and 216), but is not aware of the specific nature of the billing problem and any remedial actions that may be taken via the user interface.

为了实现本文所述的沙箱化限制,第一示例办法可涉及使支付凭据无效性信息在软件应用104的用户界面的窗口内显示(例如,作为叠层)。这可以例如通过命令(例如,通过本文所述的API、SDK等)软件应用104允许显示软件应用104不具有访问权限的窗口来实现。又如,步骤220可涉及使支付凭据无效性信息显示在独立于并且不同于软件应用104的用户界面内,诸如由软件应用管理器116、客户端计算设备114的操作系统等控制的用户界面。根据这种方法,考虑到管理软件应用104的范围之外的用户界面,则自然禁止软件应用104访问该用户界面。需注意,前述示例并非旨在限制性的,并且可利用任何方法来有效地向客户端计算设备114的用户显示支付凭据无效性信息。To implement the sandboxing restrictions described herein, a first example approach may involve causing the payment credential invalidity information to be displayed within a window of a user interface of the software application 104 (e.g., as an overlay). This may be achieved, for example, by commanding (e.g., via an API, SDK, etc. described herein) the software application 104 to allow a window to be displayed to which the software application 104 does not have access rights. As another example, step 220 may involve causing the payment credential invalidity information to be displayed within a user interface that is separate from and distinct from the software application 104, such as a user interface controlled by the software application manager 116, an operating system of the client computing device 114, etc. According to this approach, given that the user interface is outside the scope of managing the software application 104, it is natural that the software application 104 is prohibited from accessing the user interface. It is noted that the foregoing examples are not intended to be limiting, and any method may be utilized to effectively display the payment credential invalidity information to the user of the client computing device 114.

在步骤222,软件应用管理器116向支付凭据管理器110提供经更新的支付凭据信息。根据一些实施方案,步骤222可响应于软件应用管理器116通过结合步骤220显示的用户界面接收到经更新的支付凭据信息而执行。然而,需注意,当220的用户界面显示链接到URL的网页时(如本文所述),可修改图2的时序图。根据这种方法,经更新的支付凭据由替代实体接收,从而消除了对实现步骤222的需要。相反,支付凭据管理器110可以从替代实体接收经更新的支付凭据,并且在适当情况下执行图2的时序图的其余步骤。At step 222, software application manager 116 provides updated payment credential information to payment credential manager 110. According to some embodiments, step 222 may be performed in response to software application manager 116 receiving updated payment credential information via a user interface displayed in conjunction with step 220. However, it is noted that the timing diagram of FIG. 2 may be modified when the user interface of 220 displays a web page linked to a URL (as described herein). According to this approach, the updated payment credential is received by an alternative entity, thereby eliminating the need to implement step 222. Instead, payment credential manager 110 may receive updated payment credentials from an alternative entity and, where appropriate, perform the remaining steps of the timing diagram of FIG. 2.

在步骤224,支付凭据管理器110与一个或多个支付处理器112交互以验证经更新的支付凭据信息有效。如本文所述,此步骤可包括例如尝试对到期款项的经更新支付凭据信息进行计费,请求确认经更新支付凭据信息将对于将到期的未来款项有效,等等。需注意,前述示例并不旨在为限制性的,并且在不脱离本公开范围的情况下,可使用任何方法来验证相对于账单问题的上下文的经更新支付凭据信息。At step 224, payment credential manager 110 interacts with one or more payment processors 112 to verify that the updated payment credential information is valid. As described herein, this step may include, for example, attempting to bill the updated payment credential information for an amount due, requesting confirmation that the updated payment credential information will be valid for future amounts due, etc. It is noted that the foregoing examples are not intended to be limiting, and any method may be used to verify the updated payment credential information relative to the context of a billing issue without departing from the scope of the present disclosure.

在步骤226,支付凭据管理器110向软件应用管理器116提供经更新支付凭据信息有效的指示。继而,在步骤228,支付凭据管理器110/软件应用104在用户界面内显示(上文结合步骤220所述)经更新支付凭据信息有效的通知。在步骤230,软件应用管理器116移除结合步骤206所存储的指示。需注意,当在步骤204提供的指示被提供至两个或更多个客户端计算设备114时,在一个客户端计算设备114处移除指示可致使(例如,通过直接通信、通过服务器计算设备102等)其他客户端计算设备114也移除该指示。这样,当发生软件应用104的后续加载和/或显示时,软件应用104将不被错误地通知账单问题。At step 226, the payment credential manager 110 provides an indication to the software application manager 116 that the updated payment credential information is valid. Subsequently, at step 228, the payment credential manager 110/software application 104 displays within the user interface (described above in connection with step 220) a notification that the updated payment credential information is valid. At step 230, the software application manager 116 removes the indication stored in connection with step 206. It is noted that when the indication provided at step 204 is provided to two or more client computing devices 114, removal of the indication at one client computing device 114 may cause the other client computing devices 114 to also remove the indication (e.g., through direct communication, through the server computing device 102, etc.). In this way, when a subsequent loading and/or display of the software application 104 occurs, the software application 104 will not be erroneously notified of the billing issue.

另外,需注意,当支付凭据管理器110从支付处理器112接收到经更新支付凭据信息无效的指示时,可实施对步骤226到228的适当调整。具体地,在步骤226,支付凭据管理器110可以向软件管理器116提供经更新支付凭据无效的指示。继而,在步骤228,支付凭据管理器110/软件应用104在用户界面内显示(上文结合步骤220所述)经更新支付凭据信息无效的通知,并且还可使得能够提供适当校正。当提供此类校正时,可重新执行步骤222到228直到获得有效的经更新支付凭据信息为止。继而,在步骤230,软件应用管理器116可移除结合步骤206所存储的指示,如本文所述。Additionally, it is noted that when the payment credential manager 110 receives an indication from the payment processor 112 that the updated payment credential information is invalid, appropriate adjustments to steps 226 to 228 may be implemented. Specifically, at step 226, the payment credential manager 110 may provide the software manager 116 with an indication that the updated payment credential is invalid. Then, at step 228, the payment credential manager 110/software application 104 displays within the user interface (described above in conjunction with step 220) a notification that the updated payment credential information is invalid, and may also enable appropriate corrections to be provided. When such corrections are provided, steps 222 to 228 may be re-executed until valid updated payment credential information is obtained. Then, at step 230, the software application manager 116 may remove the indication stored in conjunction with step 206, as described herein.

因此,图2阐述了根据一些实施方案的用于缓解与软件应用相关的错误的技术的详细时序图。下文描述的图3阐述了根据一些实施方案的可由服务器计算设备102/支付凭据管理器110实施的步骤的高级方法图。同样在下文描述的图4阐述了根据一些实施方案的可由客户端计算设备114/软件应用管理器116实施的步骤的高级方法图。最后,图4A至图4B阐述了根据一些实施方案的可根据本文所述的技术实现的示例用户界面的概念图。Thus, FIG. 2 sets forth a detailed timing diagram of a technique for mitigating errors associated with software applications, according to some embodiments. FIG. 3 , described below, sets forth a high-level method diagram of steps that may be implemented by server computing device 102 / payment credential manager 110, according to some embodiments. FIG. 4 , also described below, sets forth a high-level method diagram of steps that may be implemented by client computing device 114 / software application manager 116, according to some embodiments. Finally, FIG. 4A-4B set forth conceptual diagrams of example user interfaces that may be implemented according to the techniques described herein, according to some embodiments.

图3A示出根据一些实施方案的用于缓解与软件应用相关的错误的方法300。如图3所示,方法300开始于步骤302,其中服务器计算设备102(例如,在其上执行的支付凭据管理器110)识别具有用于处理与软件应用相关联的支付的无效支付凭据的软件应用的用户(例如,根据上文结合图2的步骤202所述的技术)。如本文所述,服务器设备可通过自检测至少一个问题、通过与支付处理器交互以检测至少一个问题等等来识别无效支付凭据。在步骤304,服务器计算设备102识别与用户相关联并且软件应用安装在其上的至少一个客户端设备(例如,根据上文结合图2的步骤202所述的技术)。FIG3A illustrates a method 300 for mitigating errors associated with a software application according to some embodiments. As shown in FIG3 , method 300 begins at step 302, where a server computing device 102 (e.g., a payment credential manager 110 executing thereon) identifies a user of a software application having invalid payment credentials for processing payments associated with the software application (e.g., according to the techniques described above in conjunction with step 202 of FIG2 ). As described herein, the server device may identify the invalid payment credentials by self-detecting at least one problem, by interacting with a payment processor to detect at least one problem, and so forth. At step 304, the server computing device 102 identifies at least one client device associated with the user and on which the software application is installed (e.g., according to the techniques described above in conjunction with step 202 of FIG2 ).

在步骤306,服务器计算设备102向至少一个客户端设备提供无效支付凭据的指示(例如,根据上文结合图2的步骤204所述的技术)。根据一些实施方案,该指示使得软件应用对该指示进行缓存(cache),直到该软件应用被加载和/或显示为止。如本文所述,该指示可最终使得软件应用在被加载和/或显示在至少一个客户端设备上的同时,显示包括从该指示导出的信息的用户界面,其中该用户界面以防止该软件应用观察在该用户界面内发生的活动的方式从该软件应用进行沙箱化(例如,根据上文结合图2的步骤208至220所述的技术)。At step 306, the server computing device 102 provides an indication of the invalid payment credentials to at least one client device (e.g., according to the techniques described above in conjunction with step 204 of FIG. 2). According to some embodiments, the indication causes the software application to cache the indication until the software application is loaded and/or displayed. As described herein, the indication may ultimately cause the software application, while being loaded and/or displayed on at least one client device, to display a user interface that includes information derived from the indication, wherein the user interface is sandboxed from the software application in a manner that prevents the software application from observing activities occurring within the user interface (e.g., according to the techniques described above in conjunction with steps 208 through 220 of FIG. 2).

根据一些实施方案,该信息描述与无效支付凭据相关联的至少一个问题,并且该至少一个问题包括与该无效支付凭据相关联的无效账单信息、资金不足或可用信用不足中的至少一者。根据一些实施方案,用户界面允许用户通过提供有效支付凭据信息来将无效支付凭据替换为有效支付凭据,并且该活动包括用户提供有效支付凭据信息。According to some embodiments, the information describes at least one problem associated with the invalid payment credential, and the at least one problem includes at least one of invalid billing information, insufficient funds, or insufficient available credit associated with the invalid payment credential. According to some embodiments, the user interface allows a user to replace the invalid payment credential with a valid payment credential by providing valid payment credential information, and the activity includes the user providing the valid payment credential information.

根据一些实施方案,尽管在图3A中未示出,但方法300可以包括允许软件应用在特定时间段内抑制用户界面的附加步骤,该特定时间段在结束时使得软件应用显示用户界面。According to some embodiments, although not shown in FIG. 3A , method 300 may include an additional step of allowing the software application to suppress the user interface for a specific time period, which at the end of the specific time period causes the software application to display the user interface.

图3B示出根据一些实施方案的用于缓解与软件应用相关的错误的方法350。如图3所示,方法350开始于步骤352,其中客户端计算设备114(例如,在其上执行的软件应用管理器116)从服务器设备接收与安装在客户端设备上的软件应用相关联的无效支付凭据的指示(例如,根据上文结合图2的步骤204所述的技术)。3B illustrates a method 350 for mitigating errors associated with software applications according to some embodiments. As shown in FIG3 , method 350 begins at step 352, where a client computing device 114 (e.g., a software application manager 116 executing thereon) receives an indication of invalid payment credentials associated with a software application installed on the client device from a server device (e.g., according to the techniques described above in conjunction with step 204 of FIG2 ).

在步骤354,客户端计算设备114存储该指示(例如,根据上文结合图2的步骤206所述的技术)。在步骤356,客户端计算设备114检测软件应用的启动和/或显示(例如,根据上文结合图2的步骤208所述的技术)。At step 354, client computing device 114 stores the indication (e.g., according to the techniques described above in connection with step 206 of FIG. 2). At step 356, client computing device 114 detects the launching and/or display of the software application (e.g., according to the techniques described above in connection with step 208 of FIG. 2).

在步骤358,客户端计算设备114提示软件应用对显示与无效支付凭据的指示相关联的信息的许可(例如,根据上文结合图2的步骤214所述的技术)。在步骤360,客户端计算设备114确定是否接收到许可(例如,根据上文结合图2的步骤214和216所述的技术)。如果在步骤360,客户端计算设备114确定接收到许可,则方法350前进至步骤362(例如,根据上文结合图2的步骤214和216所述的技术)。否则,方法350返回至步骤356(例如,根据上文结合图2的步骤214和216所述的技术)。At step 358, the client computing device 114 prompts the software application for permission to display information associated with the indication of the invalid payment credentials (e.g., according to the techniques described above in conjunction with step 214 of FIG. 2). At step 360, the client computing device 114 determines whether permission has been received (e.g., according to the techniques described above in conjunction with steps 214 and 216 of FIG. 2). If, at step 360, the client computing device 114 determines that permission has been received, the method 350 proceeds to step 362 (e.g., according to the techniques described above in conjunction with steps 214 and 216 of FIG. 2). Otherwise, the method 350 returns to step 356 (e.g., according to the techniques described above in conjunction with steps 214 and 216 of FIG. 2).

在步骤362,客户端计算设备114使得软件应用显示包括该信息的用户界面,其中该用户界面以防止该软件应用观察在该用户界面内发生的活动的方式从该软件应用进行沙箱化(例如,根据上文结合图2的步骤220所述的技术)。另外,虽然图3B中未示出,但方法350可包括以下附加步骤:(1)从服务器设备接收无效支付凭据已替换为有效支付凭据的第二指示,以及(2)从缓存(cache)中移除该指示(例如,根据上文结合图2的步骤226到230所述的技术)。At step 362, the client computing device 114 causes the software application to display a user interface that includes the information, wherein the user interface is sandboxed from the software application in a manner that prevents the software application from observing activities occurring within the user interface (e.g., according to the techniques described above in conjunction with step 220 of FIG. 2). Additionally, although not shown in FIG. 3B, method 350 may include the following additional steps: (1) receiving a second indication from the server device that the invalid payment credential has been replaced with a valid payment credential, and (2) removing the indication from a cache (e.g., according to the techniques described above in conjunction with steps 226 to 230 of FIG. 2).

图4A至图4B示出根据一些实施方案的可在客户端计算设备114上显示的示例用户界面的概念图400。具体地,用户界面402可结合所实现的图2的步骤208显示在客户端计算设备114处。接下来,用户界面404可结合所实现的图2的步骤202到220显示在客户端计算设备114处。此外,用户界面406可结合所实现的图2的步骤222和224显示在客户端计算设备114处。此外,用户界面408可结合所实现的图2的步骤228和230显示在客户端计算设备114处。需注意,图4A至图4B中示出的用户界面并不旨在为限制性的,并且在不脱离本公开的范围的情况下,本文所述的用户界面可使用任何方法来实现以显示任何形式的信息。4A-4B illustrate a conceptual diagram 400 of an example user interface that may be displayed on a client computing device 114 according to some embodiments. Specifically, user interface 402 may be displayed at the client computing device 114 in conjunction with step 208 of FIG. 2 being implemented. Next, user interface 404 may be displayed at the client computing device 114 in conjunction with steps 202 to 220 of FIG. 2 being implemented. Additionally, user interface 406 may be displayed at the client computing device 114 in conjunction with steps 222 and 224 of FIG. 2 being implemented. Additionally, user interface 408 may be displayed at the client computing device 114 in conjunction with steps 228 and 230 of FIG. 2 being implemented. Note that the user interfaces illustrated in FIGS. 4A-4B are not intended to be limiting, and the user interfaces described herein may be implemented using any method to display any form of information without departing from the scope of the present disclosure.

图5示出了根据一些实施方案的可用于实现本文所述的各个部件的计算设备500的详细视图。具体地,详细视图示出了可被包括在上文结合图1所述的服务器计算设备102、支付处理器112和客户端计算设备114中的各种部件。5 shows a detailed view of a computing device 500 that can be used to implement the various components described herein according to some embodiments. Specifically, the detailed view shows various components that can be included in the server computing device 102, payment processor 112, and client computing device 114 described above in conjunction with FIG.

如图5所示,计算设备500可包括表示用于控制计算设备500的总体操作的微处理器或控制器的处理器502。计算设备500还可包括用户输入设备508,该用户输入设备允许计算设备500的用户与计算设备500进行交互。例如,用户输入设备508可采取多种形式,诸如按钮、小键盘、拨号盘、触摸屏、音频输入接口、视觉/图像捕获输入接口、传感器数据形式的输入等。此外,计算设备500可包括可由处理器502控制以向用户显示信息的显示器510(屏幕显示器)。数据总线516可促进至少存储设备540、处理器502和控制器513之间的数据传输。控制器513可用于通过装置控制总线514来与不同装置进行交互并对其进行控制。计算设备500还可包括耦接至数据链路512的网络/总线接口511。在无线连接的情况下,网络/总线接口511可包括无线收发器。As shown in FIG. 5 , the computing device 500 may include a processor 502 representing a microprocessor or controller for controlling the overall operation of the computing device 500. The computing device 500 may also include a user input device 508 that allows a user of the computing device 500 to interact with the computing device 500. For example, the user input device 508 may take a variety of forms, such as buttons, keypads, dials, touch screens, audio input interfaces, visual/image capture input interfaces, input in the form of sensor data, etc. In addition, the computing device 500 may include a display 510 (screen display) that can be controlled by the processor 502 to display information to the user. The data bus 516 may facilitate data transmission between at least the storage device 540, the processor 502, and the controller 513. The controller 513 may be used to interact with and control different devices through the device control bus 514. The computing device 500 may also include a network/bus interface 511 coupled to the data link 512. In the case of a wireless connection, the network/bus interface 511 may include a wireless transceiver.

计算设备500还包括存储设备540,该存储设备可包括单个磁盘或多个磁盘(例如,SSD),并且包括管理存储设备540内的一个或多个分区的存储管理模块。在一些实施方案中,存储设备540可包括闪存存储器、半导体(固态)存储器等。该计算设备500还可包括随机存取存储器(RAM)520和只读存储器(ROM)522。ROM 522可存储将以非易失性方式执行的程序、实用程序或过程。RAM 520可提供易失性数据存储并存储与本文所述计算设备的操作相关的指令。The computing device 500 also includes a storage device 540, which may include a single disk or multiple disks (e.g., SSDs), and includes a storage management module that manages one or more partitions within the storage device 540. In some embodiments, the storage device 540 may include flash memory, semiconductor (solid-state) memory, etc. The computing device 500 may also include a random access memory (RAM) 520 and a read-only memory (ROM) 522. The ROM 522 may store programs, utilities, or processes to be executed in a non-volatile manner. The RAM 520 may provide volatile data storage and store instructions related to the operation of the computing device described herein.

可单独地或以任何组合使用所述实施方案的各个方面、实施方案、具体实施或特征。可由软件、硬件或硬件与软件的组合来实施所述实施方案的各个方面。所述实施方案也可体现为计算机可读介质上的计算机可读代码。计算机可读介质为可存储可被计算机系统读取的数据的任何数据存储设备。该计算机可读介质的示例包括只读存储器、随机存取存储器、CD-ROM、DVD、磁带、硬盘驱动器、固态驱动器和光学数据存储设备。计算机可读介质也可分布在网络耦接的计算机系统中,使得计算机可读代码以分布的方式被存储和执行。The various aspects, embodiments, implementations or features of the embodiments may be used individually or in any combination. The various aspects of the embodiments may be implemented by software, hardware, or a combination of hardware and software. The embodiments may also be embodied as computer readable code on a computer readable medium. A computer readable medium is any data storage device that can store data that can be read by a computer system. Examples of the computer readable medium include read-only memory, random access memory, CD-ROM, DVD, magnetic tape, hard disk drive, solid state drive, and optical data storage device. The computer readable medium may also be distributed in a network coupled computer system so that the computer readable code is stored and executed in a distributed manner.

为了说明的目的,前述描述使用具体命名以提供对所述实施方案的彻底理解。然而,对于本领域的技术人员而言将显而易见的是,不需要具体细节,以便实践所述实施方案。因此,具体实施方案的前述描述被呈现用于例示和描述的目的。前述描述不旨在为穷举性的或将所述的实施方案限制为所公开的精确形式。对于本领域的普通技术人员而言将显而易见的是,鉴于上面的教导内容,许多修改和变型是可行的。For the purpose of illustration, the foregoing description uses specific nomenclature to provide a thorough understanding of the embodiments. However, it will be apparent to those skilled in the art that specific details are not required in order to practice the embodiments. Therefore, the foregoing description of specific embodiments is presented for the purpose of illustration and description. The foregoing description is not intended to be exhaustive or to limit the embodiments described to the precise form disclosed. It will be apparent to those of ordinary skill in the art that, in view of the above teachings, many modifications and variations are feasible.

Claims (20)

1.一种用于缓解与软件应用相关的错误的方法,所述方法包括在服务器设备处:1. A method for mitigating errors associated with a software application, the method comprising, at a server device: 识别与软件应用的用户相关联的至少一个错误;identifying at least one error associated with a user of the software application; 识别与所述用户相关联并且在其上安装有所述软件应用的至少一个客户端设备;以及identifying at least one client device associated with the user and having the software application installed thereon; and 向所述至少一个客户端设备提供所述至少一个错误的指示,以使得所述软件应用在被加载和/或显示在所述至少一个客户端设备上的同时进行下述操作:providing an indication of the at least one error to the at least one client device so that the software application, while being loaded and/or displayed on the at least one client device, performs the following operations: 显示包括从所述指示导出的信息的用户界面,其中所述用户界面以防止所述软件应用观察在所述用户界面内发生的活动的方式从所述软件应用进行沙箱化。A user interface is displayed that includes information derived from the indication, wherein the user interface is sandboxed from the software application in a manner that prevents the software application from observing activities occurring within the user interface. 2.根据权利要求1所述的方法,其中所述信息描述与所述至少一个错误相关联的至少一个问题。2 . The method of claim 1 , wherein the information describes at least one problem associated with the at least one error. 3.根据权利要求2所述的方法,其中所述至少一个问题包括以下各项中的至少一者:3. The method of claim 2, wherein the at least one question comprises at least one of: 与所述用户和/或所述软件应用相关联的无效凭据信息,或者与所述用户和/或所述软件应用相关联的无效配置信息。Invalid credential information associated with the user and/or the software application, or invalid configuration information associated with the user and/or the software application. 4.根据权利要求2所述的方法,其中所述服务器设备通过检测所述至少一个问题来识别所述至少一个错误。The method of claim 2 , wherein the server device identifies the at least one error by detecting the at least one problem. 5.根据权利要求1所述的方法,其中:5. The method according to claim 1, wherein: 所述用户界面允许所述用户提供用于缓解所述至少一个错误的输入,并且The user interface allows the user to provide input for mitigating the at least one error, and 所述活动包括所述用户提供所述输入。The activity includes the user providing the input. 6.根据权利要求1所述的方法,还包括:6. The method according to claim 1, further comprising: 允许所述软件应用在特定时间段内抑制所述用户界面,所述特定时间段在结束时使得所述软件应用显示所述用户界面。The software application is allowed to suppress the user interface for a specific time period, which upon expiration causes the software application to display the user interface. 7.根据权利要求1所述的方法,其中所述指示使得所述软件应用对所述指示进行缓存,直到所述软件应用被加载和/或显示为止。7. The method of claim 1, wherein the indication causes the software application to cache the indication until the software application is loaded and/or displayed. 8.一种被配置为缓解与软件应用相关的错误的服务器设备,所述服务器设备包括:8. A server device configured to mitigate errors associated with a software application, the server device comprising: 用于识别与软件应用的用户相关联的至少一个错误的装置;means for identifying at least one error associated with a user of a software application; 用于识别与所述用户相关联并且在其上安装有所述软件应用的至少一个客户端设备的装置;和means for identifying at least one client device associated with the user and having the software application installed thereon; and 用于向所述至少一个客户端设备提供所述至少一个错误的指示以使得所述软件应用在被加载和/或显示在所述至少一个客户端设备上的同时进行下述操作的装置:Means for providing an indication of the at least one error to the at least one client device so that the software application, while being loaded and/or displayed on the at least one client device, performs the following operations: 显示包括从所述指示导出的信息的用户界面,其中所述用户界面以防止所述软件应用观察在所述用户界面内发生的活动的方式从所述软件应用进行沙箱化。A user interface is displayed that includes information derived from the indication, wherein the user interface is sandboxed from the software application in a manner that prevents the software application from observing activities occurring within the user interface. 9.根据权利要求8所述的服务器设备,其中所述信息描述与所述至少一个错误相关联的至少一个问题。9. The server device of claim 8, wherein the information describes at least one problem associated with the at least one error. 10.根据权利要求9所述的服务器设备,其中所述至少一个问题包括以下各项中的至少一者:10. The server device of claim 9, wherein the at least one question comprises at least one of: 与所述用户和/或所述软件应用相关联的无效凭据信息,或者与所述用户和/或所述软件应用相关联的无效配置信息。Invalid credential information associated with the user and/or the software application, or invalid configuration information associated with the user and/or the software application. 11.根据权利要求9所述的服务器设备,其中所述服务器设备通过检测所述至少一个问题来识别所述至少一个错误。11. The server device of claim 9, wherein the server device identifies the at least one error by detecting the at least one problem. 12.根据权利要求8所述的服务器设备,其中:12. The server device according to claim 8, wherein: 所述用户界面允许所述用户提供用于缓解所述至少一个错误的输入,并且The user interface allows the user to provide input for mitigating the at least one error, and 所述活动包括所述用户提供所述输入。The activity includes the user providing the input. 13.根据权利要求8所述的服务器设备,还包括:13. The server device according to claim 8, further comprising: 用于允许所述软件应用在特定时间段内抑制所述用户界面的装置,所述特定时间段在结束时使得所述软件应用显示所述用户界面。Means for allowing the software application to suppress the user interface for a specific time period, the specific time period upon expiration causing the software application to display the user interface. 14.根据权利要求8所述的服务器设备,其中所述指示使得所述软件应用对所述指示进行缓存,直到所述软件应用被加载和/或显示为止。14. The server device of claim 8, wherein the indication causes the software application to cache the indication until the software application is loaded and/or displayed. 15.一种用于缓解与软件应用相关的错误的方法,所述方法包括在客户端设备处:15. A method for mitigating errors associated with a software application, the method comprising, at a client device: 从服务器设备接收与安装在所述客户端设备上的软件应用相关联的至少一个错误的指示;receiving, from a server device, an indication of at least one error associated with a software application installed on the client device; 存储所述指示;storing the instructions; 检测所述软件应用的启动和/或显示;detecting launching and/or displaying of the software application; 提示所述软件应用对显示与所述至少一个错误的所述指示相关联的信息的许可;以及prompting the software application for permission to display information associated with the indication of the at least one error; and 响应于接收到来自所述软件应用的许可:In response to receiving the license from the software application: 使得所述软件应用显示包括所述信息的用户界面,其中所述用户界面以防止所述软件应用观察在所述用户界面内发生的活动的方式从所述软件应用进行沙箱化。The software application is caused to display a user interface including the information, wherein the user interface is sandboxed from the software application in a manner that prevents the software application from observing activities occurring within the user interface. 16.根据权利要求15所述的方法,其中:16. The method of claim 15, wherein: 所述方法由在所述客户端设备上执行的软件应用管理器来实现,The method is implemented by a software application manager executed on the client device, 所述软件应用管理器使得能够执行多个软件应用,并且The software application manager enables execution of a plurality of software applications, and 所述多个软件应用包括所述软件应用。The plurality of software applications includes the software application. 17.根据权利要求15所述的方法,其中存储所述指示包括将所述指示存储到所述客户端设备能够访问的缓存中。17. The method of claim 15, wherein storing the indication comprises storing the indication in a cache accessible to the client device. 18.根据权利要求17所述的方法,还包括:18. The method according to claim 17, further comprising: 从所述服务器设备接收所述至少一个错误已被缓解的第二指示;以及receiving from the server device a second indication that the at least one error has been mitigated; and 从所述缓存中移除所述指示。The indication is removed from the cache. 19.根据权利要求15所述的方法,其中所述信息描述与所述至少一个错误相关联的至少一个问题。19. The method of claim 15, wherein the information describes at least one problem associated with the at least one error. 20.根据权利要求15所述的方法,其中所述用户界面:20. The method of claim 15, wherein the user interface: 使得能够提供与所述客户端设备的用户相关联的有效凭据信息,或者enabling provision of valid credential information associated with a user of the client device, or 使得能够提供与所述用户和/或所述软件应用相关联的有效配置信息。Enabling provision of valid configuration information associated with the user and/or the software application.
CN202410301181.5A 2023-03-17 2024-03-15 Techniques for mitigating errors associated with software applications Pending CN118672815A (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US63/491,027 2023-03-17
US18/479,036 2023-09-30
US18/479,036 US20240311220A1 (en) 2023-03-17 2023-09-30 Techniques for mitigating errors tied to software applications

Publications (1)

Publication Number Publication Date
CN118672815A true CN118672815A (en) 2024-09-20

Family

ID=92719964

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202410301181.5A Pending CN118672815A (en) 2023-03-17 2024-03-15 Techniques for mitigating errors associated with software applications

Country Status (1)

Country Link
CN (1) CN118672815A (en)

Similar Documents

Publication Publication Date Title
US11467891B2 (en) Kernel event triggers for content item security
US10742632B2 (en) Passporting credentials between a mobile app and a web browser
US11245682B2 (en) Adaptive authorization using access token
US10382449B2 (en) Permissions decisions in a service provider environment
US10043174B1 (en) Bitcoin transaction using text message
US12062049B2 (en) Repurposing a transaction authorization channel to provide fraud notifications
CN110945850B (en) System and method for automating security control between computer networks
US9569602B2 (en) Mechanism for enforcing user-specific and device-specific security constraints in an isolated execution environment on a device
BRPI0720581A2 (en) PROGRAMMATICALLY APPLICATION BETWEEN PHONE DEVICES BASED ON LICENSE INFORMATION
US20230206234A1 (en) Methods and systems for shared resource access
US20140208399A1 (en) Method and system for accessing a computing resource
US20130124696A1 (en) Application products with in-application subsequent feature access using network-based distribution system
US9594751B1 (en) Predictive delivery of digital content items to mobile devices to support offline transactions
US20190102778A1 (en) Secure online transaction system and method therefor
JP6926349B2 (en) How to process secure financial transactions using commercial off-the-shelf or Internet of Things devices
CN112995244A (en) Subscription withholding method, resource access method and equipment
US9942183B2 (en) Processing connection request in online service
EP4432193A1 (en) Techniques for mitigating errors tied to software applications
CN118672815A (en) Techniques for mitigating errors associated with software applications
US20200410489A1 (en) Device manager to control data tracking on computing devices
US10506075B1 (en) Link correction system and methods
KR20150096158A (en) The method, server and system for providing application funding service
US10742635B2 (en) Multilevel sign-on
EP3364331A1 (en) Feature-based access to a multi-function peripheral application using an activation server
CN119048101A (en) Resource transfer method and device, computer program product and electronic equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination