Source: http://www.google.com/patents/US6449660?dq=mezick
Timestamp: 2015-08-03 11:31:14
Document Index: 798733972

Matched Legal Cases: ['Application No. 94', 'Application No. 94', 'Application No. 94', 'Application No. 94', 'Application No. 94', 'Application No. 94', 'Application No. 95', 'Application No. 95', 'Application No. 95']

Patent US6449660 - Object-oriented I/O device interface framework mechanism - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsAt the most general level, the I/O framework mechanism of the present invention is made up of three interdependent controllers. These controllers are referred to herein as the hardware resource administrator, the information controller, and the device controller. The hardware resource administrator is...http://www.google.com/patents/US6449660?utm_source=gb-gplus-sharePatent US6449660 - Object-oriented I/O device interface framework mechanismAdvanced Patent SearchPublication numberUS6449660 B1Publication typeGrantApplication numberUS 08/509,619Publication dateSep 10, 2002Filing dateJul 31, 1995Priority dateJul 31, 1995Fee statusPaidPublication number08509619, 509619, US 6449660 B1, US 6449660B1, US-B1-6449660, US6449660 B1, US6449660B1InventorsWilliam Frederick Berg, John David Dietel, Edward John RowlanceOriginal AssigneeInternational Business Machines CorporationExport CitationBiBTeX, EndNote, RefManPatent Citations (29), Non-Patent Citations (179), Referenced by (25), Classifications (7), Legal Events (9) External Links: USPTO, USPTO Assignment, EspacenetObject-oriented I/O device interface framework mechanism
US 6449660 B1Abstract
At the most general level, the I/O framework mechanism of the present invention is made up of three interdependent controllers. These controllers are referred to herein as the hardware resource administrator, the information controller, and the device controller. The hardware resource administrator is responsible for organizing information about I/O devices and for making the organized information available to the other controllers. The information controller is responsible for gathering information about I/O devices and for changing and/or updating certain I/O device information. Accordingly, the information controller is made up of individual objects that each represent the characteristics of a particular I/O device. The device controller is responsible for controlling the actual operation of the individual devices, and for performing statistical and diagnostic analysis on the individual I/O devices.
The present invention relates in general to the data processing field. More specifically, the present invention relates to the field of input-output device interface mechanisms.
The development of the EDVAC computer system of 1948 is often cited as the beginning of the computer era. Since that time, computer systems have evolved into extremely sophisticated devices. However, even today's most sophisticated computer systems continue to include many of the basic elements that were present in some of the first computer systems. Such elements include the computer system's processor, memory, and input-output devices (I/O devices for short). A computer system's processor is the intelligent portion of the computer system. The processor is responsible for executing programs that interpret and manipulate information that is given to the computer system by the computer system's user or users. I/O devices are extremely important because they play a major role in getting the necessary information into the computer system, storing the information, and making the information available to the computer system's users. After all, how valuable would a computer system be if there were no way to get information in or out? Example I/O devices include information entry and retrieval devices such as personal terminals and workstations, mass storage devices such as magnetic tape and disk devices, and output devices such as printers.
It is, therefore, a principal object of this invention to provide an enhanced I/O device interface mechanism that controls and manages I/O devices in a way that permits speedy change or addition of I/O devices.
FIG. 8 shows a block diagram of the computer system of the present invention. The computer system of the preferred embodiment is an enhanced IBM AS/400 client-server computer system. However, any computer system could be used.
FIG. 11C shows the utility functions class in more detail. The utility functions class is the last class of the hardware resource administrator category. As previously mentioned, classes like the utility functions class are class utilities that are used to define utility operations that are needed, but not directly related to any one class definition. As shown, the utility functions class of I/O framework 813 has definitions for four operations, the generateUid( ) operation, the mapUidToloPtr( ) operation, the notify_client( ) operation and the mapSridToPtr( ) operation. The generateUid( ) operation is used to generate a universal Id for an I/O device. Universal Ids are explained in the text associated with FIG. 11A. The mapUidToloPtr( ) operation is used to attempt to associate a generated Uid with an existing IoHri object. The operation returns the object when the association can be made and an error message when the association cannot be made. The notify_client( ) operation is used by client programs (i.e., those of application programs 810 in the case of computer system 800) when the client programs want to be notified when devices matching certain descriptions are “powered-on.” For example, client programs may use this operation to automatically bring-up a workstation to computer connection every time a users powers-on a workstation. The mapSridToPtr( ) operation is used by client programs that wish to obtain an IoHri object for a particular device from any given Srid.
IoHwDevWs, which stands for I/O hardware device workstation, is the class that is used for all the different types of workstations. This class is an abstract extensible class that provides four operation definitions to its subclasses. The activated( ) and deactivated operations are defined to be used to activate and deactivate workstations. The write Screen( ) operation is defined to send a “screens worth” of data to a workstation while the screen Response( ) operation is defined to be used to receive information from a workstation.
FIG. 14A is an object diagram that shows an example object interaction that takes place within I/O framework 813 when computer system 800 is “powered-on.” For the purposes of explanation, only the initialization of DASD device 882 is shown. However, those skilled in the art will understand that other object interactions occur for other types of I/O devices. The interaction is initiated when operating system 865 initializes DASD interface 874 [step 1]. Next, operating system 865 instantiates an IoHw object for DASD device 882 [step 2]. (Hw objects are defined in the class hierarchy shown on FIG. 13A.) It should be understood that step 2 and the series of steps that follow take place for every I/O interface. For the purposes of explanation, the steps are described once with respect to I/O interface 874. Instantiation occurs through a call from operating system 865 to a constructor( ) operation. Since constructor operations are well known to those skilled in the art of OO design, specifics about constructor operations are not shown or described.
Once the IoHri object has been created (through whichever means), the IoHw object for DASD device 882 opens a functional connection to DASD device 882 [step 13]. This completed, the IoHw object for DASD device 882 returns control to the IoHw object for DASD interface 874. This IoHw object then reads the vital product data (VPD) from DASD interface 874. The VPD generally includes all of the important information about all of the devices that are attached to a device interface. For example, DASD interfaces may well have capacity information about all of their connected DASD devices. Once collected, the VPD for the specific device is sent to all of IoHw objects for all of the devices that are attached to the device interface at issue (i.e., DASD device interface 874 in this case) [step 14]. The IoHw objects then relay the information to the respective IoHri objects [step 15]. Once steps 1-15 have been processed, DASD device 882 is ready to be used and the IoHw object for DASD device 882 so notifies the IoHw object for DASD interface 874 [step 16]. At this point, I/O framework mechanism 813 will attempt to notify other devices about the presence of DASD 882. More specifically, I/O framework 813 will attempt to notify all the devices of computer system 800 that can be said to have “parent” or “child” relationship with DASD device 882. In our example, DASD device 882 has no real parent or children. If, however, DASD device 882 were a DASD controller instead of a simple DASD device, it would be necessary to notify all of the DASD controller's children (i.e., the connected DASD devices) of the presence of the DASD controller. Similarly, if DASD device 882 were connected to a DASD controller that was itself connected to DASD interface 874, it would be necessary to notify the parent of DASD device 882 (i.e., the DASD controller) of the presence of DASD device 882. Steps 21 through 26 of FIG. 14A show this functionality.
A system that is modeled by an object-oriented framework can be represented at a high level of abstraction by a diagram called a top-level class diagram. FIG. 1 of the drawings is an example of a top-level class diagram containing boxes that represent abstractions of the modeled system. the boxes are arranged in a hierarchy such that boxes representing abstractions close to the physical components of the system are at the lower levels of the diagram and boxes representing more abstract, functional components are closer to the top of the diagram. In FIG. 1, the boxes are labelled as “mechanisms” to denote that the abstractions comprise means for implementing modeled system components. The boxes (mechanisms) can be thought of as categories comprising groups of similar classes defined according to object-oriented programming concepts. FIG. 1 represents a zoo administration model and therefore the lower hierarchy boxes include a box called Animal Mechanism, which represents animals within the zoo model, and a box called Containment Unit Mechanism, which represents animal pens and cages. At the highest level of FIG. 1, the box called Zoo Administration represents a functional abstraction that encompasses a variety of administrative tasks that are performed by personal.
Some objects may be active, meaning that they embody their own thread of control. That is, such objects are not simply sequential. Active objects may have a variety of concurrency characteristics. If an object has multiple threads of control, then synchronization must be specified. Message synchronization can be synchronous, meaning that the client will wait until the supplier accepts the message. Synchronous synchronization is indicated with an “X” with an arrowhead. Synchronization can encompass balking message-passing, meaning that the client will abandon the message if the supplier cannot immediately service the message. Balking is indicated with an arrowhead turned back on itself. Synchronization can encompass a time-out synchronization, meaning that the client will abandon the message if the supplier cannot service the message within a specified amount of time. Time-out synchronization is indicated with a clock face representation adjacent a linking arrowhead. Finally, synchronization can encompass an asynchronous message, meaning that the client sends an event to a supplier for processing, the supplier queues the message, and the client then proceeds without waiting for the supplier. Those. skilled in the art will appreciate that asynchronous message synchronization is analogous to interrupt handling. Asynchronous message synchronization is indicated with a half arrowhead.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS4943932Apr 15, 1987Jul 24, 1990Cimflex Teknowledge CorporationArchitecture for composing computational modules uniformly across diverse developmental frameworksUS5057996Jun 29, 1989Oct 15, 1991Digital Equipment CorporationWaitable object creation system and method in an object based computer operating systemUS5101364Feb 9, 1990Mar 31, 1992Massachusetts Institute Of TechnologyMethod and facility for dynamic video composition and viewingUS5119475Aug 29, 1991Jun 2, 1992Schlumberger Technology CorporationObject-oriented framework for menu definitionUS5181162Dec 6, 1989Jan 19, 1993Eastman Kodak CompanyDocument management and production systemUS5195172Jul 2, 1990Mar 16, 1993Quantum Development CorporationSystem and method for representing and solving numeric and symbolic problemsUS5226161Aug 31, 1992Jul 6, 1993Wang Laboratories, Inc.Integration of data between typed data structures by mutual direct invocation between data managers corresponding to data typesUS5247693Nov 17, 1992Sep 21, 1993The Foxboro CompanyComputer language structure for process control applications and method of translating same into program code to operate the computerUS5249270Mar 29, 1991Sep 28, 1993Echelon CorporationDevelopment system protocolUS5257384Sep 9, 1991Oct 26, 1993Compaq Computer CorporationAsynchronous protocol for computer system managerUS5261080Aug 28, 1992Nov 9, 1993Wang Laboratories, Inc.Matchmaker for assisting and executing the providing and conversion of data between objects in a data processing system storing data in typed objects having different data formatsUS5274572Mar 6, 1990Dec 28, 1993Schlumberger Technology CorporationMethod and apparatus for knowledge-based signal monitoring and analysisUS5276775Oct 13, 1992Jan 4, 1994Texas Instruments Inc.System and method for building knowledge-based applicationsUS5287447Jun 28, 1991Feb 15, 1994International Business Machines CorporationMethod and system for providing container object attributes to a non-container objectUS5293470Jan 28, 1991Mar 8, 1994International Business Machines CorporationData processing system for defining and processing objects in response to system user operationsUS5297283Oct 16, 1992Mar 22, 1994Digital Equipment CorporationObject transferring system and method in an object based computer operating systemUS5301323 *Oct 30, 1992Apr 5, 1994International Business Machines Corp.Data processing system including dynamic channel path managementUS5315703Dec 23, 1992May 24, 1994Taligent, Inc.Object-oriented notification framework systemUS5367633Jan 11, 1994Nov 22, 1994Taligent, Inc.Objected oriented notification framework systemUS5369766Mar 25, 1993Nov 29, 1994Taligent, Inc.Object-oriented loader system with support for different load formatsUS5379430Aug 4, 1993Jan 3, 1995Taligent, Inc.Object-oriented system locator systemUS5379431 *Dec 21, 1993Jan 3, 1995Taligent, Inc.Boot framework architecture for dynamic staged initial program loadUS5388264Sep 13, 1993Feb 7, 1995Taligent, Inc.Object oriented framework system for routing, editing, and synchronizing MIDI multimedia information using graphically represented connection objectUS5390325Dec 23, 1992Feb 14, 1995Taligent, Inc.Automated testing systemUS5396626Aug 4, 1993Mar 7, 1995Taligent, Inc.Object-oriented locator systemUS5398336Jul 16, 1993Mar 14, 1995Consilium, Inc.Object-oriented architecture for factory floor managementUS5495610 *Jul 13, 1995Feb 27, 1996Seer Technologies, Inc.Software distribution system to build and distribute a software releaseUS5544302 *Jun 3, 1993Aug 6, 1996Taligent, Inc.Object-oriented framework for creating and using container objects with built-in propertiesUS5557796 *Jan 21, 1994Sep 17, 1996Digital Equipment Corp.Extensible entity management system including a dispatching kernel and modules which independently interpret and execute commands* Cited by examinerNon-Patent CitationsReference1Abstract for EPO Patent No. 619544, S. Danforth, Oct. 12, 1994, "Language-Neutral Object-Oriented Programming".2Abstract for U.S. Patent No. 5,119,475, Schoen et al., Jun. 2, 1992, "Object-Oriented Framework for Menu Definition".3Abstract for U.S. Patent No. 5,369,766, Heninger et al., Nov. 29, 1994, "Object Oriented Application Processing Apparatus".4Abstract for U.S. Patent No. 5,388,264, Milne et al., Feb. 7, 1995, "Object-Oriented Framework System for Enabling Multimedia Presentation with Routing and Editing of MIDI Information".5Abstract for WIPO Patent Application No. 94/15281, Anderson et al., Jul. 7, 1994, "Atomic Command Object-Oriented System Software Platform".6Abstract for WIPO Patent Application No. 94/15282, Anderson et al., Jul. 7, 1994, "Dialog System Object-Oriented System Software Platform".7Abstract for WIPO Patent Application No. 94/15286, Goldsmith et al., Jul. 7, 1994, "Object-Oriented Framework for Object Operating System".8Abstract for WIPO Patent Application No. 94/19740, Goldsmith et al., Sep. 1, 1994, "Framework Processor of Object-Oriented Application".9Abstract for WIPO Patent Application No. 94/19751, Anderson et al., Sep. 1, 1994, "Concurrent Framework Processing Apparatus for Application Users".10Abstract for WIPO Patent Application No. 94/19752, Anderson et al., Sep. 1, 1994, "Concurrent Framework Processing Apparatus for Two or More Users".11Abstract for WIPO Patent Application No. 95/01610, Koko et al., Jan. 12, 1995, "Object Oriented Product Structure Management in Computer-Aided Product Design".12Abstract for WIPO Patent Application No. 95/02219, Helgeson et al., Jan. 19, 1995, "Distributed Computation Based on Movement, Execution and Insertion of Processes in Network".13Abstract for WIPO Patent Application No. WO 94/23364, Heninger et al., Oct. 13, 1994, "Framework Processing Apparatus for Application Software".14Abstract for WIPO Patent Application No. WO 95/04966, F. T. Nguyen, Feb. 16, 1995, "Automatic Management of Components in Object-Oriented System".15Abstract for WIPO Patent No. 94/20912, Sep. 15, 1994, "Object-Oriented System for Managing Financial Instruments".16Abstract fpr WIPO Patent Application No. 95/04967, Feb. 16, 1995, "Access Method to Data Held in Primary Memory Based Data Base".17Abstract from EPO Patent Application No. EP 622730, "Encapsulation of Extracted Portions of Documents Into Objects", M. A. Malamud, Nov. 2, 1994.18Abstract from U.S. Patent No. 5,371,891, "Object Constructions in Compiler in Object Oriented Programming Language", J. Gray et al., Dec. 6, 1994.19Abstract from WIPO Patent Application No. WO 9415285, Jul. 7, 1994, "Object-Oriented Notification Framework System", D. R. Anderson et al.20Abstract from WIPO Patent Application No. WO 9422081, Sep. 29, 1994, "Hardware-Independent Interface for Interrupt Processing", G. O. Norman et al.21Abstract No. 95-091003/12, "Flexible Multi-Platform Partitioning for Computer Applications in Object Oriented System".22 *F. Metthijs, Y. Berbers, P. Verbaeten, "A Flexible I/O Framework for Parallel and Distributed Systesm", IEEE, pp. 187-190, 1995.*23Inspec Abastract No. 4152687, from M. Wolczko, 1992, "Encapsulation, Delegation and Inheritance in Object-Oriented Languages".24Inspec Abstract No. 4050569, from Di Giovanni et al., 1990, "HOOD Nets".25Inspec Abstract No. 4060084, from Muller et al., 1990, "ODICE: Object-Oriented Hardware Description in CAD Environment".26Inspec Abstract No. 4067033, from Shaw et al., 1990, "Experience with the ET++ Application Framework".27Inspec Abstract No. 4077440, from A. Mahler, 1991, "Organizing Tools in a Uniform Environment Framework".28Inspec Abstract No. 4090970, from P. Kougiouris, 1991, "Device Management Framework for an Object-Oriented Operating System".29Inspec Abstract No. 4117514, from Wuwongse et al., 1991, "An Object-Oriented Approach to Model Management".30Inspec Abstract No. 4234438, from Madany et al., 1991, "Organizing and Typing Persistent Objects Within an Object-Oriented Framework".31Inspec Abstract No. 4244023, from George et al., 1991, "An Object-Oriented Data Model to Represent Uncertainty in Coupled Artificial Intelligence-Database Systems".32Inspec Abstract No. 4258051, from Rundensteiner et al., 1992, "Set Operations in Object-Based Data Models".33Inspec Abstract No. 4258492, from M. Ball, 1992, "Inside Templates: Implementing C++ Strategies".34Inspec Abstract No. 4270125, from Becker et al., 1991, "Reusable Object-Oriented Specifications for Decision Support Systems".35Inspec Abstract No. 4270361, from Artale et al., 1991, "Introducing Knowledge Representation Techniques in Database Models".36Inspec Abstract No. 4275693, from Giannotti et al., 1991, "Non-Determinism in Deductive Databases".37Inspec Abstract No. 4275698, from Van den Bussche et al., 1991, "Evaluation and Optimization of Complex Object Selections".38Inspec Abstract No. 4275707, from Tsukamoto et al., 1991, "DOT: A Term Representation Using DOT Algebra for Knowledge-Bases".39Inspec Abstract No. 4281362, from Marshall et al., 1991, "Using VDM within an Object-Oriented Framework".40Inspec Abstract No. 4287814, from Natarajan et al., 1992, "Issues in Building Dynamic Real-Time Systems".41Inspec Abstract No. 4297404, from Tanaka et al., 1992, "Two-Level Schemata and Generalized Links for Hypertext Database Models".42Inspec Abstract No. 4298324, from S. Nichol, 1992, "Extending Turbo Vision".43Inspec Abstract No. 4302722, from Eggenschwiler et al., 1992, "ET++SwapsManager: Using Object Technology in the Financial Engineering Domain".44Inspec Abstract No. 4318465, from P. Madany, 1992, "Object-Oriented Framework for File Systems".45Inspec Abstract No. 4331060, from Lau et al., 1992, "An Object-Oriented Class Library for Scalable Parallel Heuristic Search".46Inspec Abstract No. 4341376, from Bertino et al., 1992, "Optimization of Object-Oriented Queries Using Path Indices".47Inspec Abstract No. 4356300, from Bertino et al., 1993, "Path-Index: An Approach to the Efficient Execution of Object-Oriented Queries".48Inspec Abstract No. 4366189, from Holt et al., 1992, "A Framework for Using Formal Methods in Object-Oriented Software Development".49Inspec Abstract No. 4387201, from Chu et al., 1992, "A Pattern Based Approach of Integrating Data and Knowledge to Support Cooperative Query Answering".50Inspec Abstract No. 4391388, from Thomas et al., 1992, "A Generic Object-Oriented Concurrency Mechanism for Extensibility and Reuse of Synchronization Components".51Inspec Abstract No. 4395549, from Hogstrom et al., 1992, "Portability and Data Structures in Scientific Computing-Object-Oriented Design of Utility Routines in Fortran".52Inspec Abstract No. 4400350, from Y. Shoham, 1993, "Agent-Oriented Programming".53Inspec Abstract No. 4408394, from Allen et al., 1992, "GEM: Global Event Management in CAD Frameworks".54Inspec Abstract No. 4411998, from Yi Deng et al., 1992, "Unifying Multi-Paradigms in Software System Design".55Inspec Abstract No. 4417563, from E. Maim, 1992, "Recognizing Objects from Constraints".56Inspec Abstract No. 4417604, from Kraiem et al, 1992, "Mapping of Conceptual Specifications Into Object-Oriented Programs".57Inspec Abstract No. 4425343, from Demurjian et al., 1993, "Programming Versus Databases in Object-Oriented Paradigm".58Inspec Abstract No. 4426852, from Benveniste et al., 1992, "Concurrent Programming Notations in the Object-Oriented Language Arche".59Inspec Abstract No. 4447153, from Klein et al., 1992, "An Object-Oriented Framework for Curves and Surfaces".60Inspec Abstract No. 4459325, from Kesim et al., 1992, "On the Evolution of Objects in a Logic Programming Framework".61Inspec Abstract No. 4512593, from H. Sakai, 1993, "A Method for Contract Design and Delegation in Object Behavior Modeling".62Inspec Abstract No. 4525743, from Hakimzadeh et al., 1993, "Instance Variable Access Locking for Object-Oriented Databases".63Inspec Abstract No. 4528985, from Beneventano et al, 1993, "Taxonomic Reasoning with Cycles in LOGIDATA+".64Inspec Abstract No. 4534330, from Istavrinos et al., 1992, "Experiences with an Object-Oriented Mapper for Coherent Distributed Shared Memory".65Inspec Abstract No. 4534334, from Campbell et al., 1991, "A Technique for Documenting the Framework of an Object-Oriented System".66Inspec Abstract No. 4540729, from Bailes et al., "The Ecology of Class Refinement".67Inspec Abstract No. 4550414, from Parrish et al., 1993, "Automated Flow Graph-Based Testing of Object-Oriented Software Modules".68Inspec Abstract No. 4565630, from Karpovich et al, 1993, "A Parallel Object-Oriented Framework for Stencil Algorithms".69Inspec Abstract No. 4566447, from J. Rossazza, 1992, "An Object-Centered Fuzzy Representation".70Inspec Abstract No. 4588834, from G. Olander, 1992, "Chembench: Redesign of a Large Commercial Application Using Object-Oriented Techniques".71Inspec Abstract No. 4588839, from L. Fisher, 1992, "Constructing a Class Library for Microsoft Windows".72Inspec Abstract No. 4593721, Periyasamy et al., 1993, "A Formal Framework for Design and Verification of Robotic Agents".73Inspec Abstract No. 4596323, from Frank et al., 1993, "An Integrated Environment for Designing Object-Oriented Enterprise Models".74Inspec Abstract No. 4603430, from G. Booch, 1994, "Designing an Application Framework".75Inspec Abstract No. 4613481, from Thieme et al., 1993, "Schema Integration in Object-Oriented Databases".76Inspec Abstract No. 4618974, from Bowers, 1993, "Some Principles for the Encapsulation of the Bahaviour of Aggregate Objects".77Inspec Abstract No. 461931, from Islan et al, 1993, "Uniform Co-Scheduling Using Object-Oriented Design Techniques".78Inspec Abstract No. 4622794, from Campbell et al., 1993, "A Technique for Documenting the Framework of an Object-Oriented System".79Inspec Abstract No. 4626386, from Arora et al., 1993, "Building Diverse Environments with PCTE Workbench".80Inspec Abstract No. 4642214, from Marshall et al., 1992, "Using VDM Within an Object-Oriented Framework".81Inspec Abstract No. 4647921, from Uhorchak et al., 1993, "An Object-Oriented Class Library for Creating Engineering Graphs Using PHIGS".82Inspec Abstract No. 4664213, "Maintaining Information about Persistent Replicated Objects in a Distributed System", 1993 IEEE Conference on Distributed Computing Systems.83Inspec Abstract No. 89003142, from Tenma et al., 1986, "A System for Generating Language-Oriented Editors".84Inspec Abstract No. B90075006, from Gossain et al., 1989, "Designing a Class Hierarchy for Domain Representation and Reusability".85Inspec Abstract No. B91052096, from Cusack et al., 1990, "Object-Oriented Specification in LOTOS and Z, or My Cat Really is Object-Oriented!".86Inspec Abstract No. B9310-6210L-099, "Templates, Types and Classes in Open Distributed Processing", 1993.87Inspec Abstract No. B9409-6210M-025, from Hellemans et al., 1994, "An Object-Oriented Approach to Dynamic Service Descriptions".88Inspec Abstract No. B9412-6210Q-016, from Oingzhong et al., 1992, "An Object-Oriented Model for Ingelligent Networks".89Inspec Abstract No. B9503-8110B-023, from Mautref et al., 1995, "An Object-Oriented Framework for the Development of Interactive Decision Support Systems".90Inspec Abstract No. C81005505, from Mylopoulos et al., 1980, "Some Features of the TAXIS Data Model".91Inspec Abstract No. C84005713, from Meyer et al., 1983, "Towards a Two-Dimensional Programming Environment".92Inspec Abstract No. C86024804, from Greenspan et al., 1986, "A Requirements Modeling Language and Its Logic".93Inspec Abstract No. C86039588, from K. Fukunaga., 1985; "Prompter: A Knowledge Based Support Tool for Code Understanding".94Inspec Abstract No. C87007043, from Whitted et al., 1986, "Exploiting Classes in Modeling and Display Software".95Inspec Abstract No. C88007447, from P. Allen, 1987, "A Framework for Implementing Multisensor Robotic Tasks".96Inspec Abstract No. C88013915, from Woelk et al., 1987, "Multimedia Information Management in an Object-Oriented Database System".97Inspec Abstract No. C89014870, from R. King, 1988, "Semantic and Object-Oriented Database Support for Software Environments".98Inspec Abstract No. C89033226, from Corradi et al., 1988, "PO: An Object Model to Epxress Parallelism".99Inspec Abstract No. C89039001, from Brophy et al., 1989, "A Framework for Multiple, Concurrent Graphical Representation".100Inspec Abstract No. C89049257, from Madany et al., 1989, "Class Hierarchy for Building Stream-Oriented File Systems".101Inspec Abstract No. C89056727, from Campbell et al., 1989, "Principles of Object-Oriented Operating System Design".102Inspec Abstract No. C89056859, from Hull et al, 1989, "On Accessing Object-Oriented Databases: Expressive Power, Complexity, and Restrictions".103Inspec Abstract No. C89062837, from Pasquier-Boltuck et al., 1988, "Prototyping an Interactive Electronic Book System Using an Object-Oriented Approach".104Inspec Abstract No. C90007733, from Weinand et al., 1989, "Design and Implementation of ET++, A Seamless Object-Oriented Application Framework".105Inspec Abstract No. C90030609, from Forde et al., 1990, "Object-Oriented Finite Element Analysis".106Inspec Abstract No. C90034818, from Q. Chen, 1988, "Extending the Object-Oriented Paradigm for Supporting Complex Objects".107Inspec Abstract No. C90047457, from Yokoyama et al., 1990, "A Constraint-Based and Object-Oriented Knowledge Representation".108Inspec Abstract No. C90052277, from I. Tervonen, 1990, "Object-Oriented Development as a Multiview Software Construction Methodology".109Inspec Abstract No. C90052627, from Schrefl et al., 1988, "A Knowledge-Based Approach to Overcome Structural Differences in Object Oriented Database Integration".110Inspec Abstract No. C91003997, from J. Muys-Vasovic, 1989, "MacApp: An Object-Oriented Application Framework".111Inspec Abstract No. C91004708, from Bertino et al., 1990, "Optimization of Queries Using Nested Indices".112Inspec Abstract No. C91010951, from T. Helton, 1990, "Level5 Object".113Inspec Abstract No. C91024852, from Pierra et al., 1990, "An Object Oriented Approach to Ensure Portability of CAD Standard Parts Libraries".114Inspec Abstract No. C91041980, from Choi et al., 1991, "Graph Interpretation of Methods: A Unifying Framework for Polymorphism in Object-Oriented Programming".115Inspec Abstract No. C91042655, from Q. Li, 1991, "Extending Semantic Object Model: Towards More Unified View of Information Objects".116Inspec Abstract No. C91042802, from T. Yokoyama, 1990, "An Object-Oriented and Constraint-Based Knowledge Representation System for Design Object Modeling".117Inspec Abstract No. C91053151, from E. Cusack, 1991, "Refinement, Conformance and Inheritance".118Inspec Abstract No. C91053475, from Queinnec et al., 1988, "An Open Ended Data Representation Model for EU-LISP".119Inspec Abstract No. C91058815, from Menga et al., 1990, "G++: An Environment for Object Oriented Analysis and Prototyping".120Inspec Abstract No. C91064580, from Gamma et al., 1989, "Integration of a Programming Environment into ET++-A Case Study".121Inspec Abstract No. C91064787, from Madany et al, 1989, "A Class Hierarchy for Building Stream-Oriented File Systems".122Inspec Abstract No. C91072016, from A. Lane, 1991, "/DOS/C++-Application Frameworks".123Inspec Abstract No. C91072574, from Hemery et al., "An Analysis of Communication and Multiprogramming in the Helios Operating System".124Inspec Abstract No. C91072815, from Holtkamp et al, 1990, "DEMOM-A Description Based Media Object Data Model".125Inspec Abstract No. C9402-6150G-002, from Bruegge et al., 1993, "A Framework for Dynamic Program Analyzers".126Inspec Abstract No. C9403-6180-027, 1991, "An Event-Object Recovery Model for Object-Oriented User Interfaces" from Proceedings of ACMSymposium on User Interface Software & Technology.127Inspec Abstract No. C9405-6180G-031, from Woyak et al., 1993, "A Motif-Like Object-Oriented Interface Framework Using PHIGS".128Inspec Abstract No. C9406-0310F-011, 1993, "Cost-Benefit Analysis of Object-Oriented Technology".129Inspec Abstract No. C9406-6110J-007, from J. D. Grimes, 1993, "Objects 101-An Implementation View", Proceedings of COMPCON 1994.130Inspec Abstract No. C9406-6110J-029, "A Comparison of Object-Oriented Analysis and Design Methods", Proceedings of C++ World 1993.131Inspec Abstract No. C9406-6115-048, 1993, "Constructing Multi-View Editing Environments Using MViews".132Inspec Abstract No. C9406-6150N-015, from Schmidt et al., 1994, "The Service Configurator Framework: An Extensible Architecture for Dynamically Configuring Concurrent, Multi-Service Network Daemons".133Inspec Abstract No. C9406-7490-012, "A Discrete-Event Object-Oriented Modeling Environment for Sawmill Simulation".134Inspec Abstract No. C9407-6140D-014, from Satoh et al., 1994, Semantics for a Real-Time Object-Oriented Programming Language.135Inspec Abstract No. C9407-7420D-045, from Desai et al., "Controller Structure Definition Via Intelligent Process Control".136Inspec Abstract No. C9408-6110B-016, from Chen et al., 1994, "An Experimental Study of Using Reusable Software Design Frameworks to Achieve Software Reuse".137Inspec Abstract No. C9408-6110J-011, from Gyu-Chung et al., 1993, "System Methodologies of Object-Oriented Programs".138Inspec Abstract No. C9408-7420-021, from Pirklbauer et al., 1994, "Object-Oriented Process Control Software".139Inspec Abstract No. C9409-6180-059, from Wang et al., 1993, "A Framework for User Customization".140Inspec Abstract No. C9410-6180G-015, from Eichelberg et al., 1993, "Integrating Interactive 3D-Graphics into an Object-Oriented Application Framework".141Inspec Abstract No. C9411-6115-035, from Mili et al., 1991, "SoftClass: An Object-Oriented Tool for Software-Reuse".142Inspec Abstract No. C9411-6130B-108, from Mili et al., 1992, "Building a Graphical Interface for a Reuse-Oriented Case Tool".143Inspec Abstract No. C9411-6160J-011, from Odberg et al., 1992, "A Framework for Managing Schema Versioning in Object-Oriented Databases".144Inspec Abstract No. C9411-7100-029, from C. Le Pape, 1994, "Implementation of Resource Constraints in ILOG Schedule: A Library for the Development of Constraint-Based Scheduling Systems".145Inspec Abstract No. C9412-6110B-221, Berghel et al., 1992, "A Generic Object-Oriented Concurrency Mechanism for Extensibility and Reuse of Synchronization Components".146Inspec Abstract No. C9412-6110J-006, from Lau et al., 1993, "Using SOM for Tool Integration".147Inspec Abstract No. C9412-6110J-014 from Griss et al., 1994, "Object-Oriented Reuse".148Inspec Abstract No. C9412-6160J-025 from J. Livari, 1994, "Object-Oriented Information Systems Analysis: A Comparison of Six Object-Oriented Analysis Methods".149Inspec Abstract No. C9412-7330-186, from Righter et al., 1994, "An Object-Oriented Characterization of Spatial Ecosystem Information".150Inspec Abstract No. C9412-7810-003, from Jung et al., 1993, "Development of an Object-Oriented Anthropometric Database for an Ergonomic Man Model".151Inspec Abstract No. C94204-6110J-017, "Choices, Frameworks and Refinement", R. H. Campbell et al., 1991.152Inspec Abstract No. C9501-6115-039, from Elia et al., 1993, "G++: An Object Oriented Environment for Developing Distributed Applications".153Inspec Abstract No. C9501-6140D-005, S. Vinoski, 1994, "Mapping CORBA IDL Into C++".154Inspec Abstract No. C9501-7160-020, C. Le Pape, 1993, "The Cost of Genericity: Experiments With Constraint-Based Representations of Time-Tables".155Inspec Abstract No. C9501-7330-007, Salminen et al., 1994, "Modelling Trees Using an Object-Oriented Scheme".156Inspec Abstract No. C9502-6130G-006, "Support for Enterprise Modelling in CSCW", P. Hennessy et al., 1994.157Inspec Abstract No. C9502-7160-026, from Menga et al., 1995, "An Object-Oriented Framework for Enterprise Modelling".158Inspec Abstract No. C9502-7810C-058, from Lin et al., 1995, "Can CAL Software Be More Like Computer Games?".159Inspec Abstract No. C9503-6110B-045, from Rosiene et al., 1995, "A Data Modeling Framework for Queueing Network Models".160Inspec Abstract No. C9503-6140D-045, Satoh et al., 1995, "Process Algebra Semantics for a Real Time Object Oriented Programming Language".161Inspec Abstract No. C9504-6130B-049, from A. van Dam, 1995, "VR as a Forcing Function: Software Implications of a New Paradigm".162Inspec Abstract No. C9504-6140D-024, from Sheffler et al., 1995, "An Object-Oriented Approach to Nested Data Parallelism".163Inspec Abstract No. C9504-7460-042, Coleman et al., 1995, "An End-to-End Simulation of A Surveillance System Employing Architecture Independence, Variable Fidelity Components and Software Reuse".164Inspec Abstract No. C9504-7460-043, Sells et al., 1995, "Implementation of the Architecture for a Time-Domain Dynamical System Simulation in a Very High-Level Pictorial Object-Oriented".165Text of IBM Technical Disclosure Bulletin, Allard et al., Feb. 1990, "Object-Oriented Programming in C-the Linnacus System", pp. 437-439.166Text of IBM Technical Disclosure Bulletin, Allard et al., Feb. 1990, "Object-Oriented Programming in C—the Linnacus System", pp. 437-439.167Text of IBM Technical Disclosure Bulletin, Baker et al., Jun. 1991, "Distribution List Class", p. 159.168Text of IBM Technical Disclosure Bulletin, Baker et al., Oct. 1991, "Model View Schema", pp. 321-322.169Text of IBM Technical Disclosure Bulletin, Baker et al., Oct. 1991, "Office Container Class", pp. 309-310.170Text of IBM Technical Disclosure Bulletin, Cavendish et al., Jul. 1991, "Icon Pane Class", pp. 118-119.171Text of IBM Technical Disclosure Bulletin, Cavendish et al., Jun. 1991, "Object-Oriented Documentation Tool", pp. 50-51.172Text of IBM Technical Disclosure Bulletin, vol. 36, Coskun, N., Jun. 1993, "Persistent Framework Independent Record/Playback Framework", pp. 261-264.173Text of IBM Technical Disclosure Bulletin, vol. 37, DeBinder et al., Feb. 1994, "Results Folder Framework", pp. 431-432.174Text of IBM Technical Disclosure Bulletin, vol. 37, No. 12, Dec. 1994, pp. 19-20, Al-Karmi et al., "Events Set for Event Tracing in Distributed Object-Oriented Systems".175Text of IBM Technical Disclosure Bulletin, vol. 37, No. 12, Dec. 1994, pp. 375-378, Acker et al., "Automatically Generating Formatted Documentation for Object-Oriented Class Libraries".176Text of IBM Technical Disclosure Bulletin, vol. 37, No. 6B, Jun. 1994, pp. 553-556, Gest et al., "Portable Object-Oriented Event Manager".177Text of IBM Technical Disclosure Bulletin, vol. 37, No. 7, Jul. 1994, pp. 145-146, Banda et al., "Exception Management Algorithm for Multi-Threaded Method Invocation".178Text of IBM Technical Disclosure Bulletin, vol. 37, No. II, Nov. 1994, pp. 71-72, Behrs et al., "Device Support Framework to Support ISO DPA 10175 and POSIX 1387.4".179Text of IBM Technical Disclosure Bulletin, vol. 38, No. 1, Jan. 1995, pp. 411-414, J. Knapman, "Generating Specific Server Programs in Distributed Object-Oriented Customer Information Control System".* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS6591214 *Jan 29, 2001Jul 8, 2003International Business Machines CorporationCommunication interface unit, connection tool for test, wrap test tool, and wrap testing methodUS7032021 *Mar 9, 2000Apr 18, 2006Siemens AktiengesellschaftMethod and network element for operating a telecommunications networkUS7089532 *Jan 4, 2002Aug 8, 2006International Business Machines CorporationObject oriented information retrieval framework mechanismUS7099886 *May 31, 2001Aug 29, 2006Microsoft CorporationMethod and apparatus for identifying programming object attributesUS7308288Aug 22, 2003Dec 11, 2007Sbc Knowledge Ventures, Lp.System and method for prioritized interface designUS7324922Oct 26, 2005Jan 29, 2008International Business Machines CorporationRun-time performance verification systemUS7392527 *Dec 10, 2003Jun 24, 2008Microsoft CorporationDriver-specific context for kernel-mode shimmingUS7415710 *Jul 7, 2003Aug 19, 2008Hewlett-Packard Development Company, L.P.Method and system for maintaining a module type definition tableUS7451159Mar 11, 2005Nov 11, 2008Micosoft CorporationMethod and apparatus for identifying programming object attributesUS7457821Jul 13, 2005Nov 25, 2008Microsoft CorporationMethod and apparatus for identifying programming object attributesUS7584169Mar 11, 2005Sep 1, 2009Microsoft CorporationMethod and apparatus for identifying programming object attributesUS7747414Nov 29, 2007Jun 29, 2010International Business Machines CorporationRun-Time performance verification systemUS7908580 *Sep 7, 2006Mar 15, 2011Microsoft CorporationConnecting an integrated development environment with an application instanceUS8312252 *Apr 26, 2005Nov 13, 2012Sony CorporationContent receiving apparatus and method, storage medium, and serverUS8589812Oct 29, 2007Nov 19, 2013At&T Intellectual Property I, L.P.Prioritized user interfaceUS8850388Sep 7, 2006Sep 30, 2014Microsoft CorporationControlling application featuresUS8930888 *Jun 28, 2012Jan 6, 2015International Business Machines CorporationModelling serialized object streamsUS20020010809 *May 31, 2001Jan 24, 2002Ralph LipeMethod and apparatus for identifying programming object attributesUS20020065957 *Jan 4, 2002May 30, 2002International Business Machines CorporationObject oriented information retrieval framework mechanismUS20050054384 *Aug 22, 2003Mar 10, 2005Sbc Knowledge Ventures, L.P.System and method for prioritized interface designUS20050071257 *Nov 18, 2004Mar 31, 2005Jarbridge, Inc.Merged images viewed via a virtual storage closetUS20050120145 *Nov 30, 2004Jun 2, 2005International Business Machines CorporationCoupling of peripherals to a computer systemUS20050187880 *Apr 26, 2005Aug 25, 2005Sony CorporationContent receiving apparatus and method, storage medium, and serverUS20070235535 *Apr 5, 2006Oct 11, 2007Davoust David MMethod and software for determining the eligibility of a voter and for providing pollworker trainingUS20130007695 *Jun 28, 2012Jan 3, 2013International Business Machines CorporationModelling serialized object streams* Cited by examinerClassifications U.S. Classification710/1, 717/100, 719/321International ClassificationG06F9/445, G06F3/00Cooperative ClassificationG06F9/4411European ClassificationG06F9/44A4Legal EventsDateCodeEventDescriptionOct 20, 1995ASAssignmentOwner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW YFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BERG, WILLIAM FREDERICK;DIETEL, JOHN DAVID;ROWLANCE, EDWARD JOHN;REEL/FRAME:007676/0820;SIGNING DATES FROM 19950731 TO 19951013Nov 18, 2005FPAYFee paymentYear of fee payment: 4Apr 19, 2010REMIMaintenance fee reminder mailedSep 3, 2010FPAYFee paymentYear of fee payment: 8Sep 3, 2010SULPSurcharge for late paymentYear of fee payment: 7Apr 18, 2014REMIMaintenance fee reminder mailedAug 27, 2014SULPSurcharge for late paymentYear of fee payment: 11Aug 27, 2014FPAYFee paymentYear of fee payment: 12Mar 13, 2015ASAssignmentOwner name: LINKEDIN CORPORATION, CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTERNATIONAL BUSINESS MACHINES CORPORATION;REEL/FRAME:035201/0479Effective date: 20140331RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services