Lucent Technologies Inc.

Other

Alcatel Lucent

The Ohio State University

Gang Zhou

Richard Baxter Hull

Bharat Kumar

Xia Cao

L James Lee

Francois Llirbat

Guozhu Dong

Jianwen Su

Reinhard P Klemm

Daniel Francis Lieuwen

Eric Simon

Vijay Kumar Gurbani

Timothy G Griffin

Suhasini Sabnis

Victoria Hiering

Luis Nieto

Aniruddha Gokhale

A composite material having polymeric resin with disperse phases of reinforcing fibers and nanoparticle materials and its manufacture is disclosed herein. The nanoparticles may be bound together and added to the polymeric resin as microscale aggregations, and then unbound to create a disperse phase of nanoparticles in the resin. In other embodiments, the nanoparticles may be bound to a substrate, such as long fibers, and added to a polymeric resin. The nanoparticles are then unbound from the substrate and dispersed throughout the polymeric resin. The polymeric resin may have multiple components where one component may control the dispersion of the nanoparticles.

Reinforced nancomposites and method of producing the same

Method of preparing a composite with disperse long fibers and nanoparticles

A customer relationship management system is disclosed for matching a given work item with an agent. The system includes a database to hold customer information, agent information, and system information, and a network contact center server operative to receive the given work item from the customer and route it to the agent based at least in part on the information in the database. The network contact center server is configured to control the conduction of an automated web dialogue with the customer via a separate web server and is further configured to control the conduction of an automated voice dialogue with the customer via an interactive voice response system. The automated web dialogue and the automated voice dialogue are thereby both conductable under the control of the network contact center server.

Customer relationship management system with network contact center server configured to control automated web and voice dialogues

An object-focused workflow system for processing a received object in accordance with a declarative workflow specification. The specification includes modules and attributes, where module execution results in the evaluation of attributes, and may include the initiation of a side-effect action performed by an external component. Whether modules are to be executed for a particular received object is determined by associated enabling conditions. Attributes may be evaluated in accordance with computation rules and a combining policy, where the computation rules specify how values are to be contributed to an attribute, and the combining policy indicates how those contributed values are combined in order to assign a value to the attribute. Tasks in the workflow system may be executed eagerly in order to improve the performance of the workflow system. The eager evaluation of tasks includes the determination of whether such tasks are eligible for eager evaluation, and whether the tasks are unneeded or necessary for the processing of the received event. Workflows which satisfy described design properties allow for improved algorithms for the determination of the whether tasks are eligible, eager, and/or necessary. A graphical user interface is provided for displaying a representation of the evaluation status of the modules and attributes during workflow execution.

Eager evaluation of tasks in a workflow system

Data item evaluation based on the combination of multiple factors

Declarative workflow system supporting side-effects

Computer and telecommunication systems employing workflow (contact flow) processes are enhanced by employing dynamic random differential treatment of so-called instances (contacts) entering the workflow (contact flow). This is realized, for example, by associating a prescribed distinguishing function with the workflow (contact flow), and to use a value given by this prescribed distinguishing function in one or more decisions relating to how the object instance (contact) should be processed. Each decision is essentially a choice between two or more paths in a workflow (contact flow), or a choice between two or more workflows (contact flows). For example, the prescribed distinguishing function could associate a distinguishing value having an integer value between 1 and 100 with object instances (contacts), and a selection function for making a decision to use one or more of a plurality of workflows (contact flows) is related to a prescribed parameter &ldquo;x&rdquo; that has a value from 0 to 100. For example, each object instance (contact) with a prescribed distinguishing value&lE;x is routed to a first of the plurality of possible treatments and each object instance (contact) with distinguishing value>x is routed to at least another of the plurality of possible treatments. Additionally, dynamic control is utilized over the parameters employed by the selection function that control whether object instances (contacts) are routed to the first treatment or to some other treatment. For the preceding example, this is accomplished by permitting dynamic control over the value of prescribed parameter x. This dynamic control is effected either manually or automatically. In a particular embodiment of the invention, dynamically controlled differentiation is realized by associating a random number (or other randomly chosen value) with each object instance (contact), and to use this random number in one or more decisions relating to how the object instance (contact) should be processed. That is, a randomized differentiator is utilized as the dynamically controlled differentiator.

System and method including dynamic differential treatment in workflows and contact flow

A logical data architecture for fetch-intensive database applications includes a first and a second logical database. The second database includes materialized views over the first database. Updates are propagated from the first database to the second database using so-called view maintenance techniques. In preferred embodiments, the first database may be optimized for update transactions and the second database may be optimized for read transactions. At least one of the materialized views included in the second database is based on a pre-defined application read transaction. The update processing overhead associated with view maintenance is substantially performed at the first database.

Data architecture for fetch-intensive database applications

Growing community of inventors

Basking Ridge, NJ, United States of America

Gang Zhou