Electrical computers and digital processing systems: multicomput – Distributed data processing
Reexamination Certificate
1998-12-24
2002-11-12
Geckil, Mehmet B. (Department: 2152)
Electrical computers and digital processing systems: multicomput
Distributed data processing
C709S223000, C709S224000, C370S332000
Reexamination Certificate
active
06480879
ABSTRACT:
FIELD OF THE INVENTION
The present invention relates generally to distributed computing networks and, more particularly, to a system that provides quality of service across a distributed object-oriented computer network.
DESCRIPTION OF RELATED ART
The development and deployment of distributed applications has proliferated in recent years in part due to the creation of middleware. Middleware refers to a layer of software between the application and communication layers that offers a consistent, higher-level abstraction throughout the network. Middleware makes distributed applications easier to develop by facilitating communication between distributed applications.
An increasingly important category of distributed applications includes multimedia applications, such as video-on-demand. Multimedia applications demand high-performance communication layers. To meet these demands, communication layers offer features, such as quality of service (QoS) and multicasting, for multimedia applications to exploit. QoS refers to specific system performance requirements, such as the amount of a specific resource or group of resources devoted to satisfying a client (or caller) application's request. QoS allows for the reservation of guaranteed system properties. System properties include operational attributes, such as throughput and delay. Since these QoS features are offered only at the communication layer, new middleware must be developed to provide the application layer with access to these features.
Common Object Request Broker Architecture (CORBA) is middleware that was developed to facilitate such access. CORBA's interface description language (IDL) provides an important base for developing distributed applications because the IDL describes the programmatic interface to an object, including the type signature (i.e., a list of input and output parameters, along with the data types of each of the parameters) of the operations which the object embodies, independent of the underlying programming language, operating system, and communication medium. Through the programmatic interface, the IDL allows a programmer to develop a distributed application rapidly and transparently, without regard to the underlying services.
CORBA's IDL hides implementation details. As a result, distributed applications based on CORBA's IDL operate properly only as long as resources are plentiful. For example, distributed applications operate well where the programmers have prior knowledge of the system properties under which their code will execute and these properties remain relatively constant, such as where objects are either local (i.e., in the client's address space) or within the same local area network (LAN), and resources are plentiful.
In wide-area distributed environments, however, system properties are more dynamic, hostile, and less understood. This is a consequence of changing conditions, such as high delays, frequent failures, and low bandwidth, in the distributed system and the fact that programmers have no prior knowledge of these changing conditions.
As a result, usage patterns, QoS requirements, and underlying resources must be managed in order for a distributed application to operate properly over a wide-area network. Unfortunately, these features are precisely what is being hidden by the functional interface described by the IDL. To make a distributed application perform adequately, additional details regarding the design decisions embodied in an implementation of an object must be made available without sacrificing the software engineering gains, such as transparency, obtained by using object-oriented techniques.
A compounding factor that programmers face when developing distributed applications is that programmers are only used to handling the ideal system properties of local objects and not the dynamic system properties of distributed objects, such as their QoS properties. The system properties of local objects are considered ideal because the local objects do not fail independently of a client once they are created, and the delay for invoking a method is negligible.
Unfortunately, the system properties of distributed objects are far from ideal: they can fail unexpectedly and independently from a client, and the delay for a method invocation to return may be long due to communication overhead, for example. As a result, programmers typically include extra code with most invocations to remote objects to handle errors and performance conditions. Programmers find this coding very difficult to do, and the coding makes it even more difficult for programs to be used in an environment different from that for which they were originally hardcoded. Worse yet, the coding negates the benefits provided by the transparent interface definitions of the IDL.
Yet another factor that programmers encounter when they manage system properties in a distributed environment is that the information about the system properties becomes available at different times, in different locations, and from different sources. For example, information regarding system properties may come from many locations in a distributed system, such as from the client, the object, the communication layer, and the resources connecting them. The information may also come from many sources within the distributed system, such as the object designer, the client designer, the operations staff, and the end-user of the distributed application. If any of this information becomes unavailable for some reason, the distributed application will perform poorly.
Therefore, a need exists for a framework that supports QoS across wide-area and mobile environments to facilitate proper design and execution of distributed applications.
SUMMARY OF THE INVENTION
Systems and methods consistent with the present invention address this need through a quality objects (QuO) framework that includes a system of software components that provide a general purpose mechanism for the specification and satisfaction of application quality of service (QoS) requirements in a distributed, object-oriented computer software system. The QuO framework integrates knowledge of system properties over time, space, and source to facilitate proper operation of a distributed application.
In accordance with the purpose of the invention as embodied and broadly described herein, a system provides a quality of service by generating at least one system condition object storing a value, monitoring at least one resource in real time using the system condition object, and setting the value of the system condition object in response to the monitoring of the resource. The system determines a current quality of service based on the value stored in the system condition object. The system then regulates activity within the distributed system based on the determined quality of service.
REFERENCES:
patent: 6003079 (1999-12-01), Friedrich et al.
patent: 6055493 (2000-04-01), Ries et al.
patent: 6061724 (2000-05-01), Ries et al.
patent: 6141565 (2000-10-01), Feuerstein et al.
patent: 6189046 (2001-02-01), Moore et al.
Specifying and measurig quality of service in distributed object systems, Loyall, J.P.; Schantz, R.E.; Zinky, J.A.; Bakken, D.E., BBN Technology, Cambridge, MA, USA, ISBN: 0-8186-8430-5, pp. 43-52.*
David E. Bakken, Object-Oriented QoS for C2 Adaptivity and Evolvability, DARPA Workshop on Security Technology for Next-Generation C2 Systems, Institute for Defense Analyses, Alexandria VA, Jul. 29-30, 1996; (http://www.dist-systems.bbn.com/papers/1996/paper-96-01/paper-96-01.html printed Feb. 6, 1998 pp. 1-4.
Steve Vinoski et al., CORBA: Integrating Diverse Applications Within Distributed Heterogeneous Environments, IEEE Communications Magazine, vol. 35, No. 2, Feb. 1997; pp. 1-12.
John A. Zinky, Architectural Support for Quality of Service for CORBA Objects, Theory and Practice of Object Systems, Jan. 1997, pp. 55-73.
Robert Orfali et al., Chapter 2, The Essential Distributed Objects Survival Guide, John Wiley & sons, 1996, 24-29.
Robert Orfali et al., Chapter 4, The Essentia
Bakken David E.
Loyall Joseph P.
Schantz Richard R.
Vanegas Rodrigo
Zinky John A.
Geckil Mehmet B.
Genuity Inc.
Prieto Beatriz
Suchyta Leonard Charles
Weixel James K.
LandOfFree
Framework for providing quality of service requirements in a... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Framework for providing quality of service requirements in a..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Framework for providing quality of service requirements in a... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2954438