会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 13. 发明授权
    • Event aggregation for background work execution
    • 后台工作执行的事件聚合
    • US09063775B2
    • 2015-06-23
    • US13224154
    • 2011-09-01
    • James A. Schwartz, Jr.Arun U. KishanRichard K. NevesDavid B. ProbertHari PulapakaAlain F. Gefflaut
    • James A. Schwartz, Jr.Arun U. KishanRichard K. NevesDavid B. ProbertHari PulapakaAlain F. Gefflaut
    • G06F13/00G06F9/48
    • G06F9/4812
    • Systems, methods, and apparatus for separately managing foreground work and background work. In some embodiments, an operating system may identify at least one foreground component and at least one background component of a same application or different applications, and may manage the execution of the components differently. For example, the operating system may receive a request that at least one background component of an application be executed in response to at least one event. In response to detecting an occurrence of the at least one event, the operating system may determine whether at least one first condition set by the application is satisfied and whether at least one second condition set by the operating system is satisfied, and may execute the at least one background component when it is determined that the at least one first and second conditions are satisfied following the occurrence of the at least one event.
    • 用于单独管理前台工作和后台工作的系统,方法和装置。 在一些实施例中,操作系统可以标识相同应用或不同应用的至少一个前台组件和至少一个后台组件,并且可以不同地管理组件的执行。 例如,操作系统可以接收响应于至少一个事件来执行应用的至少一个后台组件的请求。 响应于检测到所述至少一个事件的发生,操作系统可以确定是否满足由应用设置的至少一个第一条件以及是否满足由操作系统设置的至少一个第二条件,并且可以执行at 当确定在所述至少一个事件的发生之后满足所述至少一个第一和第二条件时,至少一个后台部件。
    • 20. 发明授权
    • Thread-related actions based on historical thread behaviors
    • 基于历史线程行为的线程相关动作
    • US08677360B2
    • 2014-03-18
    • US13106627
    • 2011-05-12
    • Pedro Miguel Sequeira de Justo TeixeiraArun U. Kishan
    • Pedro Miguel Sequeira de Justo TeixeiraArun U. Kishan
    • G06F9/46
    • G06F11/3476G06F11/3404G06F2201/865
    • Various embodiments provide techniques for managing threads based on a thread history. In at least some embodiments, a behavior associated with currently existing threads is observed and a thread-related action is performed. A result of the thread-related action with respect to the currently existing threads, resources associated with the currently existing threads (e.g., hardware and/or data resources), and/or other threads, is then observed. A thread history is recorded (e.g., as part of a thread history database) that includes the behavior associated with the currently existing threads, the thread related action that was performed, and the result of the thread-related action. The thread history can include information about multiple different thread behaviors and can be referenced to determine whether to perform thread-related actions in response to other observed thread behaviors.
    • 各种实施例提供了基于线程历史来管理线程的技术。 在至少一些实施例中,观察与当前存在的线程相关联的行为,并且执行线程相关动作。 然后,观察到关于当前存在的线程的线程相关动作的结果,与当前存在的线程(例如,硬件和/或数据资源)和/或其他线程相关联的资源。 记录线程历史(例如,作为线程历史数据库的一部分),其包括与当前存在的线程相关联的行为,所执行的与线程相关的动作以及线程相关动作的结果。 线程历史可以包括关于多个不同线程行为的信息,并且可以被引用以确定是否响应于其他观察到的线程行为执行线程相关动作。