Verizon Business Global LLC

Mci, Inc.

Verizon Patent and Licensing Inc.

William Sprott Greene

James A Robertson

Matthew C Pierret

Chris Stillwell

Andrew N Wille

Sanjiv Singh

Christine Coffey

A data processing system accesses a group of events to identify a group of types of events and aggregates at least some of the events into a group of items. Each of the events is aggregated by binding another event to an event identified as a particular type of event based on a correspondence between the event and the particular type of event and binding additional information to the event identified as the particular type of event based on a relationship between the additional information and the particular type of event. The data processing system also rendezvous one of the items with an event.

Method and system for realizing a rendezvous service in a management operations center implemented in a global ecosystem of interrelated services

A data processing system may be implemented as a program product embodied on a processing system readable medium for implementing a method for using mobile code for implementing a service in a global ecosystem of interrelated services in an enterprise. The enterprise may include a group of network domains, where each of the network domains further includes a group of servers; at least one service container running on each of the servers; and a group of interrelated services, where each of the interrelated services may run on any of the at least one service container. The program product may include instructions for loading mobile service code for implementing a service on a code server, where the code server is accessible to at least some of the servers in the enterprise; instructions for determining information related to the service, where the information related to the service includes configuration information and a proxy reference for the service, the proxy reference including a codebase containing an address for a code server holding the mobile service code of a proxy for the service; and instructions for launching the service in a network domain.

Method and system for realizing an avatar in a management operations center implemented in a global ecosystem of interrelated services

A Global Information Bus (GIB) architecture is an infrastructure for deploying and managing individual services on a global scale. The GIB is a series of services that may change from one execution to another, finding and collaborating with other services dynamically. This series of collaborating services may start to resemble an ecosystem, and GIB architecture may maintain the interconnectedness and stability of this ecosystem as it continually changes. To that end, the GIB includes an enterprise repository service for storing related information related to services running in the enterprise where the enterprise consists of a group of network domains.

Method and system for implementing a global information bus in a global ecosystem of interrelated services

In accordance with an exemplary embodiment of the present invention, a global enterprise lookup (enterprise repository) is disclosed for providing a client with a mechanism for locating a needed service without knowing where that service is currently running in the enterprise. Whenever a service is launched in a container, that service registers itself with its domain registrar in order to make itself visible to the client in its own local domain but is visible only in the domain in which the service is running. A service must be registered with an enterprise level registry, the global enterprise lookup, to be visible throughout the enterprise. Clients needing a particular service that is not listed in the local registrar as running locally are directed to a global enterprise lookup (which may be implemented as a service for finding an enterprise repository) for the location of a global enterprise lookup within the enterprise. Additionally, the global enterprise lookup also manages VM container leases. When a service is launched, it acquires an enterprise lease with a local registrar. It must periodically renew the enterprise lease with the registrar to maintain its listing in the global enterprise lookup. If a service does not renew its lease within the time period of the lease, it is de-listed from the global enterprise lookup. If renewals are handled by the local domain registrars through replication and the like, the registrar may notify the global enterprise lookup of an enterprise lease renewal. Alternatively, specialized enterprise leasing services may be employed for tracking individual leases for services and notify the global enterprise lookup whenever an enterprise lease expires. Still alternatively, the enterprise employs a series of enterprise registrar services that trawl local registrars for registrations of services and registers the service with the enterprise repository.

Method and system for implementing a global lookup in a global ecosystem of interrelated services

In a computing environment, a method for forming an association between a first data object and a second data object includes forming a first association fragment, where the first association fragment includes information relevant to accessing the first data object. The method also includes forming a second association fragment. The second association fragment may include information relevant to accessing the second data object. The first association fragment and the second association fragment cause an association to be effectively formed between the first data object and the second data object.

Method and system for managing partitioned data resources

In accordance with an exemplary embodiment of the present invention, a DataBus data management architecture is presented for the NewWave service platform. It presents an architecture for creating a consistent, enterprise-wide data persistence layer which allows clients to access shared enterprise data. The DataBus achieves this enterprise-wide look by decoupling shared enterprise data from specific applications (breaking down the stovepipes) and opening up the data layer to across-the-enterprise access (given proper authorization). The DataBus architecture is designed from the ground up for global scalability and accommodation of evolving business data models in a highly-distributed physical deployment. Scaling is realized predominantly through the partitioning, while individual partitions are mapped to logical data domains that are defined along more relevant dimensions than entity-type dimensions (e.g., geography, line of business, etc.) and cut across traditional entity boundaries. Central to the DataBus data model is the notion that a data layer represents a shared asset of the corporation that is decoupled from the separate production applications requiring access to this data. The DataBus data architecture combines several main features or facets, such as partitioning, multi-hop finder strategies, externalized associations, object layer mediating access to underlying data storage, support for logical domains and transaction management.

Method and system for implementing a databus in a global ecosystem of interrelated services

The aggregator service associates/correlates a primary event with related events and bundles them together, determines what other related information is needed and builds a work document from the bundled events and the other related information, runs rules to determine the cause of the problem, and controls the life of the work to be done. The aggregator service receives an event from an information bus where the event relates to a state change, identifies primary events and correlates primary events with relates lesser events it receives by applying rules that deal with the understanding or categorization of the problem and binds the events together to produce a work document according to a predetermined organization of work integration. The rules are held in an easily-modifiable form in a rules service and runtime loaded to the aggregator service, thus the rules can be updated or modified at any time by expert problem-solving personnel and not developers.

Aggregrating related events into a single bundle of events with incorporation of bundle into work protocol based on rules

A service container provides a runtime operating environment for services managed remotely, configured remotely, load their code remotely, and found and communicated with remotely. The container scheme is the concept of a generic service container into which arbitrary software services may be homed to a host server at runtime. Each virtual machine runs a small set of code which identifies it as a service container and registers it with registries for making the service container visible and allows for remote communication.

Method and system for implementing improved containers in a global ecosystem of interrelated services

The present invention is directed to a system, method and software product for balancing resource services are always available to match the desired work to be done through the use of 'sticky services.'. Sticky services are defined as services that you know you want to have available as resources and as such they need to be present in the environment of cooperative applications; it may be that you want these always present or it may be that you want them present whenever certain conditions occur (see NewWave policy service). The general assumption of distributed systems is to not count on the environment you want being present, or put another way assume failure will occur. Therefore distributed environments like Jini assume all services are transient and will be garbage collected when not in active use. For the inside out approach to work, a mechanism should exist that, when desired, counters the transit design assumptions. This implies that two things are needed: (1) a mechanism for providing services as needed; (2) a mechanism for insuring the correct balance of resource services are always available to match the desired work to be done.

System and method for creating and managing survivable, service hosting networks

In accordance with an exemplary embodiment of the present invention, association forming entities are: a) maintained as objects in a like manner to the data objects being associated; and b) are themselves partitioned objects comprising two or more association fragments, each association fragment being mostly concerned with the interfaces to a particular data object participating in the association. In accordance with an exemplary embodiment of the present invention, each association fragment affiliated with a particular data object is stored in a location that enhances the ease of interaction between the association fragment and the data object. For example, where a first data object and second data object are maintained in data stores at some distance from one another, physically or logically, then a first association fragment will be located with or near to the first data object, and a second association fragment will be located with or near the second data object, at least within the same partition. This arrangement may be preferable because the volume of interaction between a data object and its respective association fragment may far outweigh the interaction needed between the two association fragments. This arrangement may also be preferable as the volume of interaction between a client application and both the data object and respective association fragment may exceed the interaction needed between the two association fragments. Some interactions will employ only one of the association fragments with the net result being a reduction in communications requirements and an improvement in performance. The present invention further provides for defining logical domains which are arbitrary and entirely orthogonal to partitions.

The present invention is directed to a method and management service platform for implementing a global ecosystem of interrelated services. The service platform is comprised of three distinct layers: a physical machine layer; a virtual machine layer and a layer of interrelated services. The physical machine layer may be deployed on large numbers of small generic servers in many geographic locations distributed for enterprise use. Associated with one or more servers are particular resources managed by that particular server. Any server in any geographic location can process any service needed by any client in any other geographic area. The operating system of each physical server is not used directly in the operating environment, but instead, each server runs a platform-independent programming language virtual machine on top of the operating system&#x2014;this is the virtual machine layer. Services are location independent processing entities that are managed dynamically, configured dynamically, load their code remotely, and found and communicated with dynamically. A generic service container is a CPU process into which arbitrary software services may be homed to a host server at runtime. Thus, a virtual machine layer is an interface layer of service which supports the layer of interrelated srvices rather than the operating system of the physical machines.

Growing community of inventors

Fairview, TX, United States of America

William Sprott Greene