Lucent Technologies Inc.

Alcatel-lucent USA Inc.

Alcatel Lucent

Lockheed Martin Corporation

Richard Wayne Buskens

Yow-Jian Lin

Oscar J Gonzalez

Tim Thengsen Liim

Sunil K Mishra

Muhammad A Siddiqui

Thomas F La Porta

Li Kuang

Kazutaka Murakami

Timothy A Suchaczewski

Arun N Netravali

Krishan Kumar Sabnani

Ramachandran Ramjee

Sandra Ramos Thuel

Ramesh Viswanathan

Leet E Denton, Iii

Pravish Prabhakar

Kenneth Owens

Edward Jones

Ramakrishnan Srinivasan

Sanjoy Paul

Kuo-Wei Herman Chen

Yansong Ren

Michael Patrick Deitz

Weilin Gong

Yansong J Ren

John Harris Blevin

Douglas Streeter Daudelin

Muhammad Ali Siddiqui

A data model representing a multi-model database of a product system includes a multi-model repository that holds said multi-model database's artifacts under version control. The multi-model repository holds a plurality of constituent models, wherein each model represents a discrete aspect of the system, a model registry containing a list of the constituent models in the multi-model database, a set of input attributes and a set of output attributes corresponding to each of the models, a set of interfaces representing a tuple corresponding to each of the models, a set of attribute constraints associated with the input and output attributes; and a set of notifications associated with each of the models for informing the models of defined events.

Method for representing multi-models

A computer database system for multi-model integration includes remote client-side components and a multi-model database having a plurality of artifacts that define the multi-model database and a multi-model repository that holds the artifacts under version control. The remore client-side components include a multi-model manager, one or more connectors, execution automation engine, a sandbox, and a version control system client. The multi-model repository includes a plurality of models, wherein each model represents a discrete aspect of the system, a model registry containing a list of the models in the multi-model database, a set of input attributes and a set of output attributes corresponding to each of the models, a set of interfaces representing a tuple corresponding to each of the models, wherein said tuple contains a mapping operation and the input and output attributes, a set of attribute constraints associated with the input and output attributes, and a set of notifications associated with each of the models for informing the models of defined events.

System and method for constructing and editing multi-models

Information can be transported over domains operated by different service providers at required Quality-of-Service (QoS) levels without disclosing inter- and/or intra-domain information to ensure that the topology of a given service provider's domain (e.g., network) is not disclosed.

Methods and devices for computing paths to assure the inter-domain transport of QoS sensitive information

An apparatus in one example comprises: a first manager component responsible for one or more first software components within one or more first executables of a distributed software application; and a second manager component responsible for one or more second software components within one or more second executables of the distributed software application. The first and second manager components communicate to initialize and/or shut down the one or more first software components and the one or more second software components in an ordered sequence based on one or more dependency relationships among two or more of: the one or more first software components; and/or the one or more second software components.

First and second manager components that communicate to initialize and/or shut down software components in an ordered sequence

A manager component of an apparatus in one example handles one or more checkpoint procedures for one or more software components of a distributed software application that runs within a plurality of executables.

Manager component for checkpoint procedures

An apparatus in one example comprises a first manager component that performs one or more first management operations on a software and/or hardware entity and a second manager component that performs one or more second management operations on the software and/or hardware entity.

First and second manager components that perform one or more first and second management operations on a software and/or hardware entity

A distributed software application comprises a first and second software component. A manager component of a management infrastructure for the distributed software application in one example causes a first software component of the distributed software application to obtain information from a second software component of the distributed software application for initialization of the first software component.

Manager component that causes first software component to obtain information from second software component

The time it takes to recover from a system initialization failure may be reduced by determining whether to enable a recovery process immediately, or defer such a process. Sometimes it is desirable to defer a recovery process until certain interdependencies between system components are satisfied.

Methods and devices for recovering from initialization failures

Techniques for tracing the real-time operation of software for the purposes of testing, debugging, or performance analysis are disclosed. Diagnostic instrumentation for generating records containing details of software operation is incorporated in the software by inserting calls to diverse macros or inline functions. Each macro takes an argument specifying both a subsystem and a category of instrumentation within the subsystem. Based on the specified subsystem and category, the instrumentation can be included or excluded from the compiled object code and, if included, can be dynamically enabled at run-time. Disabled instrumentation does not result in a function call, but only a single, inline 'if,' thereby reducing overhead. One macro accepts both software parameters and a custom format specifier describing how the parameters should be displayed. However, the parameters are not formatted during logging, nor is the format specifier included in the record. Instead, the formatting is performed when displayed.

Real-time software diagnostic tracing

An apparatus in one example comprises a manager component that upon receipt of an indication of a need for a communication channel between a first software component and a second software component, instructs management support software of the first software component to set up the communication channel between the first software component and the second software component.

Instructing management support software of a first software component to set up a communication channel between the first software component and a second software component

An apparatus in one example comprises a manager component for a distributed software application that based on one or more of a characteristic of an executable of the distributed software application and/or a characteristic of one or more of a plurality of processors, selects a processor from the plurality of processors to run the executable upon startup of the distributed software application.

Selecting a processor to run an executable of a distributed software application upon startup of the distributed software application

A manager component of an apparatus in one example initializes a plurality of software components of a distributed software application, within one or more executables, in an ordered sequence based on one or more dependency relationships among the plurality of software components.

Software component initialization in an ordered sequence

An apparatus in one example comprises a manager component in communication with a distributed software application. The distributed software application comprises a plurality of software components that run within one or more executables. The manager component shuts down the plurality of software components in an ordered sequence based on one or more dependency relationships among the plurality of software components.

Shutting down a plurality of software components in an ordered sequence

An apparatus in one example comprises a substitute manager component that upon failure of a first manager component, obtains management responsibility for a distributed software application from the first manager component and queries one or more software components of the distributed software application for state information of the one or more software components. The substitute manager component employs the state information to determine whether one or more recovery actions are needed for the distributed software application to recover from the failure of the first manager component.

Growing community of inventors

Robbinsville, NJ, United States of America

Richard Wayne Buskens