William S Greene

Address:

17431 S Smt Cyn Dr, Houston, TX 77095

Phone:

2813040706

VIN:

2D4GP44L47R251273

Make:

DODGE

Model:

CARAVAN

Year:

2007

US Patent:

7194543, Mar 20, 2007

Filed:

Nov 12, 2002

Appl. No.:

10/292256

Inventors:

James A. Robertson - The Woodlands TX, US
William Sprott Greene - Fairview TX, US
Chris Stillwell - Plano TX, US
Matthew C. Pierret - Plano TX, US

Assignee:

MCI, LLC - Basking Ridge NJ

International Classification:

G06F 15/173

US Classification:

709226, 709223, 709224, 709230, 714 4, 714 13, 714 39, 714 41, 714 47

Abstract:

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.

US Patent:

7401131, Jul 15, 2008

Filed:

Mar 29, 2002

Appl. No.:

10/113691

Inventors:

James A. Robertson - The Woodlands TX, US
William S. Greene - Fairview TX, US
Chris Stillwell - Plano TX, US

Assignee:

Verizon Business Global LLC - Basking Ridge NJ

International Classification:

G06F 15/177
G06F 15/16
G06F 7/00

US Classification:

709220, 709245, 707 10, 707100

Abstract:

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.

US Patent:

7802264, Sep 21, 2010

Filed:

Mar 29, 2002

Appl. No.:

10/110000

Inventors:

James A. Robertson - The Woodlands TX, US
William S. Greene - Fairview TX, US
Andrew N. Wille - Cedar Rapids IA, US

Assignee:

Verizon Business Global LLC - Basking Ridge NJ

International Classification:

G06F 3/00
G06F 9/44
G06F 9/46
G06F 13/00

US Classification:

719316, 707609, 719319, 709203

Abstract:

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.

US Patent:

7856486, Dec 21, 2010

Filed:

Mar 29, 2002

Appl. No.:

10/113969

Inventors:

James A. Robertson - The Woodlands TX, US
William S. Greene - Fairview TX, US
Matthew C. Pierret - Plano TX, US

Assignee:

Verizon Business Global LLC - Basking Ridge NJ

International Classification:

G06F 15/177

US Classification:

709220

Abstract:

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.

US Patent:

20020174191, Nov 21, 2002

Filed:

Mar 29, 2002

Appl. No.:

10/113968

Inventors:

James Robertson - The Woodlands TX, US
William Greene - Fairview TX, US

International Classification:

G06F015/16

US Classification:

709/217000, 707/010000

Abstract:

In accordance with an exemplary embodiment of the present invention, mobile code is used for implementing a global ecosystem of interrelated services. Both service code and service configuration information should be accessible at runtime configurations from anywhere in the world. This is accomplished by storing mobile code on web servers and configuration information in an enterprise repository which are both visible enterprise-wide. Many HyperText Transport Protocol (HTTP) servers are deployed to serve up code, that is, Java class files and resources, which may be physically located within the enterprise or essentially anywhere on the Internet. Through administrative APIs, the service supplier indicates the URL address that identifies in which one of the servers a particular service code resides. The API method allows any requestor to start a service executing in the service container by supplying parameters that identify the URL for the code-base of the service code, the fully-qualified class name of the Java object that is the service's root object and initialization payload object. A service may need a particular resource to be local to the service as it runs (e.g., as database, rules engine, etc.) or might run in a generic container. All service containers' configuration information in the enterprise are analyzed for necessary attributes and select only the service container(s) that have attributes matching the service's requirements (the service's configuration requirements are also available in a registry if the service is being restarted). Further distinctions between specific service containers may be made by logical locations based on the URL address of the containers matching the requirements. Once an appropriate service container is selected, the service is launched in the selected service container by passing a reference (URL address or host name) for the HTTP server holding the service code to the service container. Using a reference to the code server for the service code, the service container fetches the service code from the HTTP server at runtime and the service begins running in the container.

US Patent:

20030126079, Jul 3, 2003

Filed:

Nov 12, 2002

Appl. No.:

10/292118

Inventors:

James Roberson - The Woodlands TX, US
William Greene - Fairview TX, US

International Classification:

G06F017/60

US Classification:

705/040000

Abstract:

The present invention is directed to a system, method and software program product for implementing a policy payment agent which, based on policy thresholds set by the consumer, determines whether or not to autonomously issue a payment. Initially, the consumer sets the payment policy through the selection of payment parameters such as the type of consumable or transaction, maximum one-time payment amount, and recent spending rate. If the payment request meets the payment policy criteria, then the payment agent autonomously issues a payment. Otherwise, the request is passed to the user for manual intervention.