918 results about "Management object" patented technology

A management capability is provided for a virtual computing platform. In one example, this platform allows interconnected physical resources such as processors, memory, network interfaces and storage interfaces to be abstracted and mapped to virtual resources (e.g., virtual mainframes, virtual partitions). Virtual resources contained in a virtual partition can be assembled into virtual servers that execute a guest operating system (e.g., Linux). In one example, the abstraction is unique in that any resource is available to any virtual server regardless of the physical boundaries that separate the resources. For example, any number of physical processors or any amount of physical memory can be used by a virtual server even if these resources span different nodes. A virtual computing platform is provided that allows for the creation, deletion, modification, control (e.g., start, stop, suspend, resume) and status (i.e., events) of the virtual servers which execute on the virtual computing platform and the management capability provides controls for these functions. In a particular example, such a platform allows the number and type of virtual resources consumed by a virtual server to be scaled up or down when the virtual server is running. For instance, an administrator may scale a virtual server manually or may define one or more policies that automatically scale a virtual server. Further, using the management API, a virtual server can monitor itself and can scale itself up or down depending on its need for processing, memory and I / O resources. For example, a virtual server may monitor its CPU utilization and invoke controls through the management API to allocate a new processor for itself when its utilization exceeds a specific threshold. Conversely, a virtual server may scale down its processor count when its utilization falls. Policies can be used to execute one or more management controls. More specifically, a management capability is provided that allows policies to be defined using management object's properties, events and / or method results. A management policy may also incorporate external data (e.g., an external event) in its definition. A policy may be triggered, causing the management server or other computing entity to execute an action. An action may utilize one or more management controls. In addition, an action may access external capabilities such as sending notification e-mail or sending a text message to a telephone paging system. Further, management capability controls may be executed using a discrete transaction referred to as a “job.” A series of management controls may be assembled into a job using one or management interfaces. Errors that occur when a job is executed may cause the job to be rolled back, allowing affected virtual servers to return to their original state.

A device client that supports customer care and distribution of update packages to electronic devices makes it possible to efficiently manage and update firmware and software in electronic devices. A terminal management / device management server employs extensions to an industry standard device management protocol to update configuration information, to provision the electronic device, and to manage the electronic device, for example. The electronic device may receive update packages, and update agent(s) in the electronic device may update the firmware and / or software of the electronic device. A diagnostic client in the electronic device facilitates remote diagnosis and a traps client facilitates setting traps and retrieving collected information. A terminal management server may remotely invoke control actions within the electronic device using management objects not supported by the industry standard device management protocol. A user of the electronic device may use a self-care portal to administer self-care and to conduct diagnostics. A subsequent customer-care call may use such information collected during self-care.

One or more SLA-specified service-level monitors and / or one or more provider-owned service-level management monitors are used by the invention to monitor one or more quality measures of one or more QoS-assured service systems and to generate one or more service-level monitoring events when the monitored system does not conform to the respective quality measures. The invention includes a cross-SLA event manager that receives the monitoring events and determines which one or more SLA contracts are affected by the events. Then one or more SLA management objects (SMOs) track the SLA-specific events generated by the event manager according to each of the respective SLA contracts. The SMOs also determine how to allocate / deallocate / configure SLA management resources and / or to determine the effect of these changes on the service system operation to assure the contracted quality of service. A cross-SLA resource manager handles the SMOs' resource allocation requests and optimizes the allocation of available resources per the service provider's SLA management objectives. Finally, a SMO manager manages the execution of SMOs and facilitates the integration and management of service system testing-time and production-time activities.

Systems and processes for operating a digital assistant are provided. In one example, a method includes receiving a first speech input from a user. The method further includes identifying context information and determining a user intent based on the first speech input and the context information. The method further includes determining whether the user intent is to perform a task using a searching process or an object managing process. The searching process is configured to search data, and the object managing process is configured to manage objects. The method further includes, in accordance with a determination the user intent is to perform the task using the searching process, performing the task using the searching process; and in accordance with the determination that the user intent is to perform the task using the object managing process, performing the task using the object managing process.

A CORBA Gateway between CORBA-based applications and an enterprise manager may be configurable to manage various networked objects, such as printers, scanners, copiers, telephone systems, cell phones, phone systems, faxes, routers, switches, etc., which may be interconnected via networks. Various embodiments of the CORBA Gateway may include an Event Gateway which manages object events. The CORBA Event Gateway is designed to leverage existing Event Distribution Server (EDS) sinks to provide EDS filtering functionality and EDS object level access control functionality. The approach leverages existing EDS solutions by providing a common sink for all events / notifications and using a unique Event Port Registry to manage the subscriptions of various TMN clients that subscribe for such events / notifications. Generally, the approach described provides the capability to filter events according to criteria presented by client event subscriptions. In one embodiment, the events may be filtered to enforce policy-based access control on TMN events / notifications, determining which CORBA client applications have access to which events. The filtering of events at the sink based upon client subscriptions decreases unnecessary network traffic in that events may be “pushed” to the client, rather than delivered upon client request. In addition, the approach may provide easy-to-use IDL APIs that allow CORBA clients to directly subscribe / unsubscribe to events based on criteria such as object class, object instance, and event type.

A projected management server coupled with a computer network, such as the Internet. A spec server may also be incorporated into the project management environment for completing specs, generating requests for price quotations, purchase orders and the like. A project tree represents project management objects, which can be of any type. Object types are defined for each particular implementation of the system. Typical examples of project management object types include organizational entities, work-groups, people, projects, budgets, tasks, costs, timesheets, specs, requisitions, purchase orders, and to-do lists. The objects are generally organized in a hierarchical data structure referred to as a project management tree or project tree. Each object in a project tree comprises a number of methods that describe the way the object behaves. Such methods include, for example, methods that describe the way the object is added to the tree, edited, deleted from the tree, and archived.

Embodiments of a system and method for generating SAN management objects corresponding to heterogeneous Storage Access Network (SAN) components from discovered SAN information. In order to manage and monitor SAN components with heterogeneous management interfaces, embodiments may use one or more user-editable rules files for interpreting discovered SAN information, including management interface information, when generating SAN management objects used in managing and monitoring corresponding SAN components. Embodiments may include a mechanism for generating manageable objects for heterogeneous SAN components, including proxy agents and their corresponding proxied SAN components, by applying rules from the rules file(s) to discovered SAN information including proxy agent management interface information.

A run-time executive of an object management system for managing execution of software components in an object execution environment uses a component context object to store intrinsic context properties related to an associated component. The run-time executive maintains an implicit association of the component context object with the application component. For example, the context properties can include a client id, an activity id, and a transaction reference. The component context object also provides an interface accessible to the associated component, with member functions for use in transaction processing, in creating additional other application components inheriting component's context properties, and in access control based on abstract user classes (roles).

A system for employing SyncML DM for updating firmware in mobile handsets and other devices. The system employs enhancements to SyncML DM specifications. A SyncML management client employs new commands, specified by the present invention, for retrieving update packages for firmware updates, for the verification of a received update package, the command for saving the update package in an appropriate management object, the command for initiating an update process by an update agent and the command for the subsequent notification of the results of processing by the update agent (success, failure, etc.). More specifically, the SyncML DM management client employs new commands, specified by the present invention, for retrieving update packages for firmware updates and for updating the firmware selectively based on appropriateness, security and authentication, employing fault tolerant means.

A management information base (MIB) for a multi-domain network address translator provides management objects for configuring and controlling the multi-domain network address translator. The MIB includes management objects for defining a domain-specific source address filter range, which is a range of addresses used to detect domain-specific packets that require domain-specific network address translation forwarding. The domain-specific source address filter management objects include a beginning address, a prefix length, a domain indicator, and a domain-specific translation pool indicator. The MIB also includes management objects for defining a domain-specific translation pool, which is a range of addresses from which domain-specific translation addresses are selected for domain-specific network address translation forwarding. The domain-specific translation pool management objects include a beginning address, a prefix length, and a domain indicator.

There is provided, in a computer processing system, an apparatus for managing object data. The apparatus includes a changed objects manager for creating and managing a changed objects list that at least identifies the objects that have changed based on time of change. The changed objects list is associated with a plurality of time buckets. Each of the plurality of time buckets is associated with a respective date and time period and with object change records for objects having a timestamp falling within the respective date and time period. Each of the object change records is associated with a unique object identifier and the timestamp for a corresponding one of the objects. The timestamp specifies a date and a time corresponding to a latest one of a creation time or a most recent update time for the corresponding one of the objects.

An interface control system of network equipment, includes: a logical interface which is an interface of a logical group; physical ports which belong to the logical group; and an interface control section configured to incorporate the logical interface and the physical ports as management objects into a management interface when validation of a predetermined function has been performed to each of the logical interface and the physical ports.

Systems and processes for operating a digital assistant are provided. In one example, a method includes receiving a first speech input from a user. The method further includes identifying context information and determining a user intent based on the first speech input and the context information. The method further includes determining whether the user intent is to perform a task using a searching process or an object managing process. The searching process is configured to search data, and the object managing process is configured to manage objects. The method further includes, in accordance with a determination the user intent is to perform the task using the searching process, performing the task using the searching process; and in accordance with the determination that the user intent is to perform the task using the object managing process, performing the task using the object managing process.

Distributing software involves providing a software installation package configured to allow installing one or more programs on a computing arrangement. The software installation package is configured as a managed object compliant with the Open Mobile Alliance Device Management (OMA DM) specification. A certificate configured as a second managed object compliant with the OMA DM specification is also provided. One or more programs are installed to a computing arrangement using the software installation package. The one or more programs are bound to the computing arrangement using the certificate. Operation of the one or more programs is enabled based on the binding of the one or more programs to the computing arrangement.

A method of managing data with high granularity, comprises identifying data objects and an associated data management policy. The policy uses features and a common semantic to define a feature-based sequence of data management actions of a data management operation that varies for different objects depending on respective features. Features of the data objects are obtained and then used to associate a data management action with the object using the policy so that the object is managed individually according to its own features, thus achieving high granularity of data management precision and also high flexibility.

A gateway between client manager applications and an enterprise manager may be provided to manage various networked objects. In one embodiment, CORBA-based TMN manager applications may be communicatively coupled to a CORBA Object Request Broker (ORB) and may be operable to send Interface Definition Language (IDL) requests to, and receive IDL responses and CORBA events from, managed objects through the CORBA ORB. The client manager may first be authenticated to the gateway by username and password, or other validation information associated with the client manager, which may be represented in a user profile. Once the initial client authentication is accomplished, the gateway may provide object-level access control between manager applications and managed objects at an individual object level so that one of the managers is granted access to one of the managed objects while being prevented from interfacing with a different one of the managed objects.

In a method for the delivery of deployment components to an electronic device, a management session is set-up between the electronic device and a server. The electronic device receives a location for a deployment component from the server. A target state is received for the deployment component in the electronic device from the server. A place for a management object representing the deployment component in a management object data structure is determined in the electronic device based on the target state. The deployment component is downloaded in the electronic device from the location.

Access control approaches are disclosed wherein managed object in Simple Network Management Protocol (SNMP) Management Information Bases (MIBs) are accessed on a per-Virtual Private Network (VPN)-basis with no modifications to existing MIBs. A manager and an SNMP Agent operating in a VPN environment agree on a mapping between SNMP securityNames and VPN IDs. Under the agreed mapping, the target VPN of any SNMP management request can be unambiguously determined from the securityName alone. For each securityName, one or more MIB Views are configured using in a View-based Access Control Model MIB (VACM MIB) table; the MIB Views specify which portions of the managed object tree can be viewed or modified by a corresponding VPN. Thereafter, a VPN-enabled device provides SNMP requests in which a VPN ID value is passed in the securityName field of the context string in the community string. The receiving device extracts the securityName, locates corresponding MIB Views using the VACM MIB table, and allows the requesting device to access only objects that are identified in the MIB Views.

A device management server uses both point-to-point and broadcast transport protocols to remotely manage a plurality of electronic devices. The server uses extensions to a standard device management protocol to access, via the point-to-point transport protocol, device management information in memory of the electronic device. The device management information permits the electronic device to receive information using the broadcast transport protocol. Results from processing the received information are returned to the server using the point-to-point transport protocol. The device management server also employs handset control and enterprise control management objects to conduct device wipe, lock, unlock and other operations.

A system and method for managing group policy objects in a network, including interfaces that allow access by programs or a user interface component to functions of a group policy management console that performs management tasks on group policy objects and other related objects. The interfaces abstract the underlying data storage and retrieval, thereby facilitating searching for objects, and providing the ability to delegate, view, change and permissions on those objects, and check and save those permissions. Modeling and other test simulations are facilitated by other interfaces. Other interfaces provide dynamic and interactive features, such as to convey progress and rich status messages, and allow canceling of an ongoing operation. Still other interfaces provide methods for operating on group policy related data, including group policy object backup, restore, import, copy and create methods, and methods for linking group policy objects to scope of management objects.

An agent includes a control processing section for performing a control of selectively collecting a plurality of management objects from a managed device, and a memory section for storing the management objects collected from the managed device. Particularly, the control processing section includes an object managing section, having a plurality of classification data items for classifying the plurality of management objects respectively, for collecting those of the management objects in advance which are classified to a specific type by the classification data to store the collected management objects in the memory section, for checking, at a time of receiving an object collection request, the classification data item for a management object requested by the object collection request, for retrieving the management object confirmed by a check result as being of the specific type from the memory section to transmit the retrieved management object, and for collecting the management object confirmed by the check result as being of a type other than the specific type from the managed device to transmit the collected management object.

Methods and system for managing demand for an object includes capturing information about the object through a mobile device associated with a user. The mobile device is configured to capture information about the object that include one or more of a spatial, temporal, topical and social attributes of the object. The identity of the object is verified and validated using this metadata captured by the user through the device from the real world object or its proxy. Upon successful verification and validation, the object and its metadata are automatically added to a wish list of the user. An aggregate list is generated using the attributes and metadata of the object from a plurality of users. The aggregate list defines a source of demand for the object. The object is tracked as it progresses through various phases of ownership cycle using dynamic demand calculations based on the information associated with the objects, the users and the aggregate lists.

Methods, systems, and computer programs for performing management tasks in a virtual infrastructure are presented. The method includes detecting an increase, beyond a predetermined threshold, in the number of tasks waiting to be processed by a first virtual center (VC), which executes as a virtual machine (VM) in the virtual infrastructure. Further, the method includes operations for spawning one or more additional VCs executing as VMs in the virtual infrastructure and for distributing the managed objects handled by the first VC among the additional VCs. The tasks waiting to be processed are reallocated among the first VC and the additional VCs, and the reallocated tasks are then processed by the corresponding VC.

An automatic service discovery approach allows a network management system to discover service managed objects from the network, eliminating the need for a user or other management application to provide such information. As a result, a network management system can automatically perform network-level or services level discovery of objects and services for which network components have no understanding. Embodiments are applicable, for example, in the context of management of packet voice (VoIP, VoATM) and metro Ethernet (TLS service) domains, as well as other domains.

A system and method for managing network devices. The framework may provide a suitable system for managed object data type conversions between various data description languages, such as an interface definition language (e.g., OMG IDL) and an abstract syntax notation (e.g., ASN1). This conversion facility may be used in both request and event network traffic, so common libraries may be used. Two separate libraries may be used: a converter framework library and a converter implementation library. The framework library provides a collection classes that may be used by the clients of the converter libraries. Most classes in the converter framework library are handle classes (or wrappers) to the real implementation (or body) classes in the converter implementation library. Framework classes hide the details of the real implementation classes and provide a simple, consistent interface to any data type converter via IDL. The converter implementation library provides the implementation needed by the framework to function properly, and may allow various different mappings to be used easily by implementing them as plug-in modules. The combination of using IDL and generic typing provides an efficient, generic solution to mapping data types across multiple platforms, multiple programming languages, and multiple object classes.

Methods and apparatus operate in a computer system for managing resources and provide a method for displaying managed object data associated with managed resources. Embodiments of the invention retrieve a data dictionary containing a master view definition, task definitions, view definitions and managed object data definitions. The embodiments then display the master view definition on the graphical user interface and receive a managed object selection and a task selection to apply to the managed object selection. The embodiments then identify a view definition corresponding to the task selection with which to display managed object data related to the managed object selection. The embodiments then display a view corresponding to the at least one view definition on a graphical user interface of the computer system and obtain managed object data related to the managed object selection based upon managed object data references contained in the view definition. The embodiments then display the managed object data related to the managed object selection within the view on the graphical user interface of the computer system.

A system and method are disclosed for using directory services to manage resources in a virtual execution environment. A directory repository is populated with resource, administration, roles, policy, and service level agreement (SLA) objects. A service request is received by a virtual machine manager (VMM) administrator, which determines its requirements. The directory repository is queried with a directory service to identify available resources to fulfill the service request. The service request is routed to the VMM of the virtual machine (VM) host comprising the available resources. If an active VM comprises the available resources, then its roles, policy, and SLA objects are retrieved from the directory repository. The objects are then used to respectively determine if the service request has sufficient authentication and authorizations, if the VM's configuration meets the service request's resource requirements, and if service levels requirements can be maintained. If so, then the service request is fulfilled by the target VM. If the resources are available, but not on a currently executing VM, then an administration object is created to execute a new VM and roles, policy, and SLA objects are created that match the requirements of the service request. The newly created objects are then stored in the directory repository and the service request is fulfilled by the new VM.