AN ADAPTIVE MANAGEMENT METHOD AND SYSTEM WITH AUTOMATIC DEPENDENCY RESOLUTION
    1.
    发明申请
    AN ADAPTIVE MANAGEMENT METHOD AND SYSTEM WITH AUTOMATIC DEPENDENCY RESOLUTION 审中-公开
    自适应管理方法和系统具有自动依赖性分辨率

    公开(公告)号:WO2004017201A3

    公开(公告)日:2005-02-24

    申请号:PCT/EP0310081

    申请日:2003-08-13

    CPC classification number: G06F8/60 Y10S707/99943

    Abstract: A resource management method (300) and a corresponding system are proposed. In the solution of the invention, an authority publishes (324) multiple rules, each one defining a desired target configuration for a category of subjects (without any information about their dependencies). Each subject retrieves (320-322, 326) the rules corresponding to its category in a random order. The rules are then applied (427-439) on the subject according to a trial-and-fail approach. Particularly, the application of any failed rule is continually repeated (427-448), until all the rules are successfully applied (463) or a deadlock condition is detected (451). In this way, any dependency is automatically resolved on the subject at run time. Moreover, as soon as all the rules have been successfully applied the compliance of the subject to the rules is verified (455-57) again; should the subject be not compliant to one or more rules any longer, an infinite loop condition is detected (466).

    Abstract translation: 提出了一种资源管理方法(300)和相应的系统。 在本发明的解决方案中,授权者发布(324)多个规则,每个规则定义用于一类主题的期望的目标配置(没有关于其依赖性的任何信息)。 每个对象以随机顺序检索(320-322,326)与其类别对应的规则。 然后根据试验和失败的方法对该主题应用规则(427-439)。 特别地,不断重复应用任何失败的规则(427-448),直到所有规则成功应用(463)或检测到死锁条件(451)为止。 这样,任何依赖关系在运行时自动解决。 此外,一旦成功地应用所有规则,再次验证该主题对规则的遵守情况(455-57); 如果主体不再符合一个或多个规则,则检测到无限循环条件(466)。

    Running software application with dynamic action delegation

    公开(公告)号:GB2516833A

    公开(公告)日:2015-02-11

    申请号:GB201313660

    申请日:2013-07-31

    Applicant: IBM

    Abstract: A first component of a first computer system, such as a wireless mobile device, registers that it can execute various actions requested by applications running on the system. The actions may be sensing a physical quantity or running a background service. When a request to execute an action is received, the component determines whether the action should be executed by a local component or a remote component. The remote component may be on a further mobile device near the first computer system or it may be a remote computer provided by a network service. The first component executes the action on a remote component if there is no local component capable of executing the action. If there are suitable local and remote components, the choice may be based on a metric, such as battery level, network bandwidth, processor usage or memory usage.

Patent Agency Ranking