Patent application number | Description | Published |
20090019056 | Method, Sensor Network, and Sensor Node for Accessing Sensed Data - There is provided a sensor node, a network, and a method for accessing data from a sensor service. Sensor nodes comprise information related to sensor service(s) they provide and to services provided by other sensor nodes of the network, including description of external sensor services, the address of the sensor nodes providing the external sensor services, and identification of the service owner. When a sensor node receives a request for a sensor service from a requester, it determines that it does not support the sensor service, and further identifies another sensor node that supports the sensor service. Then, in a first variant, the sensor node returns to the requester the other sensor node's identification so that the requester can request the sensor service. In another variant, the sensor node requests from the other sensor node data related to the requested sensor service, and transmits it to the requester. | 01-15-2009 |
20110270595 | MODEL DRIVEN APPROACH FOR AVAILABILITY MANAGEMENT FRAMEWORK (AMF) CONFIGURATION GENERATION - A method and system for generating an Availability Management Framework (AMF) configuration based on a model driven approach. The AMF configuration is an instance of an AMF sub-profile that can be used to model resources and services to be protected, and is generated from an instance of the Entity Type Files (ETF) sub-profile and an instance of the Configuration Requirements (CR) sub-profile. The ETF sub-profile can be used to model the resources provided by vendors, and the CR sub-profile can be used to model configuration requirements. Each of the AMF sub-profile, the ETF sub-profile and the CR sub-profile is a specialization of pre-defined Unified Modeling Language (UML) meta-classes. An input that includes an ETF model and a CR model, which are instances of the ETF sub-profile and the CR sub-profile, respectively, is transformed into an AMF model as the AMF configuration. | 11-03-2011 |
20120192157 | HEURISTIC APPROACH ON CHECKING SERVICE INSTANCE PROTECTION FOR AVAILABILITY MANAGEMENT FRAMEWORK (AMF) CONFIGURATIONS - A configuration including Service Instances (SIs) and a list of Service Units (SUs) is to be validated. The SIs are to be allocated to the SUs for protection of the service represented by the SIs. A set of heuristics is applied to determine whether, for each of the SI assignments, the SI can be allocated to one of the SUs whose capacities support the required capacities of the SI. The heuristic then walks the list in order, to find a first SU that supports a current SI. If none of the SUs in the list can support the current SI, the heuristic indicates that the configuration is not validated. In response to a result that at least one of the heuristics in the set indicates the SUs can support all of the SIs, a final result is generated indicating that the configuration is valid. | 07-26-2012 |
20120233501 | Configuration Based Service Availability Analysis of AMF Managed Systems - An Availability Management Framework (AMF) configuration describes how configuration entities of a highly available system are grouped and includes information on service provision and service protection policies against resource failure. The AMF configuration defines a set of failure types for each component and each node, and specifies a failure rate and a recommended recovery for each failure type. A method for evaluating service availability receives the AMF configuration as input, and analyzes it to obtain an actual recovery that the highly available system is to perform when the given component fails. The method maps the AMF configuration to a stochastic model that captures the dependencies among the components and among the configuration entities at multiple levels of the hierarchy. The method utilizes the model to calculate the service availability of the AMF configuration based on the failure rate, the actual recovery and the dependencies. | 09-13-2012 |
20130091485 | BRIDGING THE GAP BETWEEN HIGH LEVEL USER REQUIREMENTS AND AVAILABILITY MANAGEMENT FRAMEWORK CONFIGURATIONS - Configuration requirements for an Availability Management Framework (AMF) configuration are generated from high level user requirements that specify a subset of properties of an AMF configuration. The user requirements are first mapped into entity prototypes defined in an extended Entity Types File (ETF) model. A computer system identifies additional entity prototypes and dependency thereof that support functionalities of the mapped entity prototypes under a set of grouping conditions. The computer system calculates the required number of component service instances (CSIs) and service instances (SIs) that satisfy the user requirements. The calculation is based on the subset of the properties specified by the user requirements and measurements associated with the entity prototypes in the extended ETF model. The computer system then forms configuration requirements including the required number of CSIs and SIs for generating the AMF configuration that satisfies the user requirements. | 04-11-2013 |
20140101634 | ONTOLOGY-BASED USER REQUIREMENT DECOMPOSITION FOR COMPONENT SELECTION FOR SERVICE PROVISION - Configuration requirements that specify the provision of services using a system-level description are automatically generated from user requirements. The user requirements are decomposed into one or more levels of decomposed functionalities using an ontology as input. The ontology stores known decompositions of functionalities and relations between the known decompositions. The lowest level of the decomposed functionalities is mapped into a set of components provided by vendors, and additional components on which the set of components depend are identified. Based on the set of components and the additional components, a required number of instances of service workload is calculated to generate the configuration requirements of the system that satisfy the user requirements. | 04-10-2014 |
20140259002 | Staging Calculation for Upgrade Campaign Generation - An upgrade campaign is generated for software deployment configuration, based on a source configuration and a target configuration for a software subsystem. A delta between the source configuration and the target configuration is determined. The delta includes a first set, a second set and a third set of the entities to be removed, added and upgraded, respectively, in the software subsystem. Based on dependencies among the entities, a sequence of stages is generated for removing, adding and upgrading the first, second and third sets of the entities, such that the entities are removed, added and upgraded according to a temporal order defined by the sequence of stages. | 09-11-2014 |