Data security method and device for computer modules

- Acqis Technology, Inc.

A security method for an attached computer module in a computer system. The security method reads a security identification number in an attached computer module and compares it to a security identification number in a console, which houses the attached computer module. Based upon a relationship between these numbers, a security status is selected. The security status determines the security level of operating the computer system.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description

Notice: More than one reissue application has been filed for the reissue of U.S. Pat. No. 6,643,777. The reissue applications are U.S. application Ser. Nos. 11/056,604 (a parent reissue application), Ser. No. 11/545,056 (which is a continuation reissue of the parent reissue application), and Ser. No. 12/561,138 (the present application, which is a continuation reissue of the parent reissue application).

This application is a continuation reissue of U.S. application Ser. No. 11/056,604 filed Feb. 10, 2005 now U.S. Pat. No. RE41,092, which is a reissue of U.S. Pat. No. 6,643,777, which are incorporated herein by reference.

BACKGROUND OF THE INVENTION

The present invention relates to computing devices. More particularly, the present invention provides a method and device for securing a personal computer or set-top box. Merely by way of example, the present invention is applied to a modular computing environment for desk top computers, but it will be recognized that the invention has a much wider range of applicability. It can be applied to other portable or modular computing applications.

Many desktop or personal computers, which are commonly termed PCs, have been around and used for over ten years. The PCs often come with state-of-art microprocessors such as the Intel Pentium™ microprocessor chips. They also include a hard or fixed disk drive including memory in the giga-byte range. Additionally, the PCs often include a random access memory integrated circuit device such as a dynamic random access memory device, which is commonly termed DRAM. The DRAM devices now provide up to millions of memory cells (i.e., mega-bit) on a single slice of silicon. PCs also include a high resolution display such as cathode ray tubes or CRTs. In most cases, the CRTs are at least 15 inches or 17 inches or 19 inches in diameter. High resolution flat panel displays are also used with PCs.

Many external or peripheral devices can be used with the PCs. Among others, these peripheral devices include mass storage devices such as a Zip™ Drive product sold by Iomega Corporation of Utah. Other storage devices include external hard drives, tape drives, and others. Additional devices include communication devices such as a modem, which can be used to link the PC to a wide area network of computers such as the Internet. Furthermore, the PC can include output devices such as a printer and other output means. Moreover, the PC can include special audio output devices such as speakers the like.

PCs also have easy to use keyboards, mouse input devices, and the like. The keyboard is generally configured similar to a typewriter format. The keyboard also has the length and width for easily inputting information by way of keys to the computer. The mouse also has a sufficient size and shape to easily move a cursor on the display from one location to another location.

Other types of computing devices include portable computing devices such as “laptop” computers and the like. Although somewhat successful, laptop computers have many limitations. These computing devices have expensive display technology. In fact, these devices often have a smaller flat panel display that has poor viewing characteristics. Additionally, these devices also have poor input devices such as smaller keyboards and the like. Furthermore, these devices have limited common platforms to transfer information to and from these devices and other devices such as PCs.

Up to now, there has been little common ground between these platforms including the PCs and laptops in terms of upgrading, ease-of-use, cost, performance, and the like. Many differences between these platforms, probably somewhat intentional, has benefited computer manufacturers at the cost of consumers. A drawback to having two separate computers is that the user must often purchase both the desktop and laptop to have “total” computing power, where the desktop serves as a “regular” computer and the laptop serves as a “portable” computer. Purchasing both computers is often costly and runs “thousands” of dollars. The user also wastes a significant amount of time transferring software and data between the two types of computers. For example, the user must often couple the portable computer to a local area network (i.e., LAN), to a serial port with a modem and then manually transfer over files and data between the desktop and the portable computer. Alternatively, the user often must use floppy disks to “zip” up files and programs that exceed the storage capacity of conventional floppy disks, and transfer the floppy disk data manually.

Another drawback with the current model of separate portable and desktop computer is that the user has to spend money to buy components and peripherals the are duplicated in at least one of these computers. For example, both the desktop and portable computers typically include hard disk drives, floppy drives, CD-ROMs, computer memory, host processors, graphics accelerators, and the like. Because program software and supporting programs generally must be installed upon both hard drives in order for the user to operate programs on the road and in the office, hard disk space is often wasted.

One approach to reduce some of these drawbacks has been the use of a docking station with a portable computer. Here, the user has the portable computer for “on the road” use and a docking station that houses the portable computer for office use. The docking station typically includes a separate monitor, keyboard, mouse, and the like and is generally incompatible with other desktop PCs. The docking station is also generally not compatible with portable computers of other vendors. Another drawback to this approach is that the portable computer typically has lower performance and functionality than a conventional desktop PC. For example, the processor of the portable is typically much slower than processors in dedicated desktop computers, because of power consumption and heat dissipation concerns. As an example, it is noted that at the time of drafting of the present application, some top-of-the-line desktops include 400 MHz processors, whereas top-of-the-line notebook computers include 266 MHz processors.

Another drawback to the docking station approach is that the typical cost of portable computers with docking stations can approach the cost of having a separate portable computer and a separate desktop computer. Further, as noted above, because different vendors of portable computers have proprietary docking stations, computer users are held captive by their investments and must rely upon the particular computer vendor for future upgrades, support, and the like.

To date, most personal computers provide data file security through software only. A wide variety of removable storage media are available for a personal computer. These removable media do not provide any access security protection in hardware. Data encryption program often must be used for protection. Such program is cumbersome to handle for the user requiring extra cost and time. Data encryption is more commonly used for communication over an unprotected network or the Internet. Having a large number of frequently used files managed by encryption software is not practical. Without software security program, any file can be read and copied illegally from a hard disk drive on a PC or any removable media.

PC architecture generally allows freedom of data flow between memory and peripheral devices within the allowed memory and I/O address spaces. In conventional PC architecture, a peripheral bus, i.e. PCI bus, is used to control all data transactions among peripheral devices. PCI bus allows any device to be a bus master and perform data transaction with another device. Also when a software program is in control, it can move data between any two devices. There is no hardware or protocol security mechanism on a standard peripheral bus such as PCI Bus to detect or block data transactions. Operating system may have individual files read or write protected. These types of special security feature require significant additional user interaction to control. This is too cumbersome for a typical user to manage. There is no mechanism in current PCs to allow access to the primary hard disk drive and yet prevent copying of its content. The conventional PC is a single machine that does not have a mechanism to perform security ID matching in hardware.

Thus, what is needed are computer systems that provide improved security features to prevent illegal or unauthorized access to information.

SUMMARY OF THE INVENTION

According to the present invention, a technique including a method and device for securing a computer module in a computer system is provided. In an exemplary embodiment, the present invention provides a security system for an attached computer module (“ACM”). In an embodiment, the ACM inserts into a computer module bay (CMB) within a peripheral console to form a functional computer. A security program reads an identification number in a security memory device to determine a security level of the ACM according to one embodiment.

In a specific embodiment, the present invention provides a system for secured information transactions. The system has a console (e.g., computer housing) comprising a peripheral controller housed in the console; and a security memory device (e.g., flash memory device) coupled to the peripheral controller. The system also has an attached computer module (i.e., a removable module with memory and microprocessor) coupled to the console. The attached computer module has a host interface controller housed within the attached computer module to interface to the security memory device through the peripheral controller.

In an alternative embodiment, the present invention provides a security protection method for a computer module. The method includes steps or acts of inserting the computer module into a console. Once the module has been inserted, the method initiates a security program in the module to read a security identification of the console and to read a security identification of the computer module. Based upon a relationship of the console identification and the computer module identification, a predetermined security status is determined from, for example, a look up table or the like. The method then selects the predetermined security status, which can be one of many. The method then operates the computer module based upon the security status.

In a further alternative embodiment, the present invention provides a method for identifying a user for a computer module. The method includes inserting a computer module into a console; and initiating a security program in memory of the computer module. The method prompts a plurality of input fields corresponding to respective input information on a user interface to be provided by a user of the computer module. Next, the method inputs the input information into the user interface of the computer module. The input information includes a user (e.g., owner) name, a user (e.g., owner) password, a business name, a business password, and a location.

Still further, the present invention provides a system for secured information transactions, e.g., data security, electronic commerce, private communications. The system includes a console comprising a peripheral controller housed in the console. A user identification input device (e.g., keyboard, retinal reader, finger print reader, voice recognition unit) is coupled to the peripheral controller. The user identification input device is provided for user identification data of the user. The system has an attached computer module coupled to the console. The attached computer module has a security memory device (e.g., flash memory device) stored with the user identification data.

Numerous benefits are achieved using the present invention over previously existing techniques. The present invention provides mechanical and electrical security systems to prevent theft or unauthorized use of the computer system in a specific embodiment. Additionally, the present invention substantially prevents accidental removal of the ACM from the console. In some embodiments, the present invention prevents illegal or unauthorized use during transit. The present invention is also implemented using conventional technologies that can be provided in the present computer system in an easy and efficient manner. Depending upon the embodiment, one or more of these benefits can be available. These and other advantages or benefits are described throughout the present specification and are described more particularly below.

These and other embodiments of the present invention, as well as its advantages and features, are described in more detail in conjunction with the text below and attached FIGS.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified diagram of a computer system according to an embodiment of the present invention;

FIG. 2 is a simplified diagram of a computer module according to an embodiment of the present invention;

FIG. 3 is a simplified top-view diagram of a computer module according to an embodiment of the present invention;

FIG. 4 is a simplified illustration of security systems according to embodiments of the present invention;

FIG. 5 is a simplified diagram of a computer module in a console according to an embodiment of the present invention;

FIG. 6 is a simplified diagram of a security method for a module according to an embodiment of the present invention; and

FIG. 7 is a simplified diagram of a method according to an embodiment of the present invention.

FIG. 8 is a simplified diagram of a system 800 according to an alternative embodiment of the present application.

FIG. 9 depicts a peripheral console configuration.

FIG. 10 is a block diagram of one embodiment of a computer system employing the present invention.

FIG. 11 is a block diagram of an attached computing module (ACM).

FIG. 12 is a block diagram of a peripheral console (PCON).

FIG. 13 is a block diagram of one embodiment of a computer system using the interface of the present invention.

FIG. 14 is a detailed block diagram of one embodiment of the host interface controller of the present invention.

FIG. 15 is a detailed block diagram of one embodiment of the PIC of the present invention.

FIG. 16 is a schematic diagram of the signal lines PCK, PD0 to PD3, and PCN.

FIG. 17 is a partial block diagram of a computer system using the interface of the present invention as a bridge between the north and south bridges of the computer system.

FIG. 18 is a partial block diagram of a computer system in which the north and south bridges are integrated with the host and peripheral interface controllers, respectively.

FIG. 19 shows an attached computer module with Integrated CPU/NB/Graphics and Integrated HIC/SB.

FIG. 20 shows an attached computer module with single chip fully integrated: CPU, Cache, Core Logic, Graphics controller and Interface controller.

 DESCRIPTION OF THE SPECIFIC EMBODIMENTS

FIG. 1 is a simplified diagram of a computer system 1 according to an embodiment of the present invention. This diagram is merely an illustration and should not limit the scope of the claims herein. One of ordinary skill in the art would recognize other variations, modifications, and alternatives. The computer system 1 includes an attached computer module (i.e., ACM) 10, a desktop console 20, among other elements. The computer system is modular and has a variety of components that are removable. Some of these components (or modules) can be used in different computers, workstations, computerized television sets, and portable or laptop units.

In the present embodiment, ACM 10 includes computer components, as will be described below, including a central processing unit (“CPU”), IDE controller, hard disk drive, computer memory, and the like. The computer module bay (i.e., CMB) 40 is an opening or slot in the desktop console. The CMB houses the ACM and provides communication to and from the ACM. The CMB also provides mechanical protection and support to ACM 10. The CMB has a mechanical alignment mechanism for mating a portion of the ACM to the console. The CMB further has thermal heat dissipation sinks, electrical connection mechanisms, and the like. Some details of the ACM can be found in co-pending U.S. patent application Ser. Nos. 09/149,882 and 09/149,548 filed Sep. 8, 1998 commonly assigned, and hereby incorporated by reference for all purposes.

In a preferred embodiment, the present system has a security system, which includes a mechanical locking system, an electrical locking system, and others. The mechanical locking system includes at least a key 11. The key 11 mates with key hole 13 in a lock, which provides a mechanical latch 15 in a closed position. The mechanical latch, in the closed position, mates and interlocks the ACM to the computer module bay. The mechanical latch, which also has an open position, allows the ACM to be removed from the computer module bay. Further details of the mechanical locking system are shown in the FIG. below.

FIG. 2 is a simplified diagram of a computer module 10 according to an embodiment of the present invention. This diagram is merely an illustration and should not limit the scope of the claims herein. One of ordinary skill in the art would recognize other variations, modifications, and alternatives. Some of the reference numerals are similar to the previous FIG. for easy reading. The computer module 10 includes key 11, which is insertable into keyhole 13 of the lock. The lock has at least two position, including a latched or closed position and an unlatched or open position. The latched position secures the ACM to the computer module bay. The unlatched or open position allows the ACM to be inserted into or removed from the computer bay module. As shown, the ACM also has a slot or opening 14, which allows the latch to move into and out of the ACM. The ACM also has openings 17 in the backside for an electrical and/or mechanical connection to the computer module bay, which is connected to the console.

FIG. 3 is a simplified top-view diagram 10 of a computer module for computer system according to an embodiment of the present invention. This diagram is merely an illustration and should not limit the scope of the claims herein. One of ordinary skill in the art would recognize other variations, modifications, and alternatives. The layout diagram illustrates the top-view of the module 10, where the backside components (e.g., Host Interface Controller) are depicted in dashed lines. The layout diagram has a first portion, which includes a central processing unit (“CPU”) module 400, and a second portion, which includes a hard drive module 420. A common printed circuit board 437 houses these modules and the like. Among other features, the ACM includes the central processing unit module 400 with a cache memory 405, which is coupled to a north bridge unit 421, and a host interface controller 401. The host interface controller includes a lock control 403. As shown, the CPU module is disposed on a first portion of the attached computer module, and couples to connectors 17. Here, the CPU module is spatially located near connector 17.

The CPU module can use a suitable microprocessing unit, microcontroller, digital signal processor, and the like. In a specific embodiment, the CPU module uses, for example, a 400 MHz Pentium II microprocessor module from Intel Corporation and like microprocessors from AMD Corporation, Cyrix Corporation (now National Semiconductor Corporation), and others. In other aspects, the microprocessor can be one such as the Compaq Computer Corporation Alpha Chip, Apple Computer Corporation PowerPC G3 processor, and the like. Further, higher speed processors are contemplated in other embodiments as technology increases in the future.

In the CPU module, host interface controller 401 is coupled to BIOS/flash memory 405. Additionally, the host interface controller is coupled to a clock control logic, a configuration signal, and a peripheral bus. The present invention has a host interface controller that has lock control 403 to provide security features to the present ACM. Furthermore, the present invention uses a flash memory that includes codes to provide password protection or other electronic security methods.

The second portion of the attached computer module has the hard drive module 420. Among other elements, the hard drive module includes north bridge 421, graphics accelerator 423, graphics memory 425, a power controller 427, an IDE controller 429, and other components. Adjacent to and in parallel alignment with the hard drive module is a personal computer interface (“PCI”) bus 431, 432. A power regulator 435 is disposed near the PCI bus.

In a specific embodiment, north bridge unit 421 often couples to a computer memory, to the graphics accelerator 423, to the IDE controller, and to the host interface controller via the PCI bus. Graphics accelerator 423 typically couples to a graphics memory 423, and other elements. IDE controller 429 generally supports and provides timing signals necessary for the IDE bus. In the present embodiment, the IDE controller is embodied as a 643U2 PCI-to IDE chip from CMD Technology, for example. Other types of buses than IDE are contemplated, for example EIDE, SCSI, USB, and the like in alternative embodiments of the present invention.

The hard drive module or mass storage unit 420 typically includes a computer operating system, application software program files, data files, and the like. In a specific embodiment, the computer operating system may be the Windows98 operating system from Microsoft Corporation of Redmond Washington. Other operating systems, such as WindowsNT, MacOS8, Unix, and the like are also contemplated in alternative embodiments of the present invention. Further, some typical application software programs can include Office98 by Microsoft Corporation, Corel Perfect Suite by Corel, and others. Hard disk module 420 includes a hard disk drive. The hard disk drive, however, can also be replaced by removable hard disk drives, read/write CD ROMs, flash memory, floppy disk drives, and the like. A small form factor, for example 2.5″, is currently contemplated, however, other form factors, such as PC card, and the like are also contemplated. Mass storage unit 240 may also support other interfaces than IDE.

In a specific embodiment, the present invention provides a file and data protection security system and method for a removable computer module or ACM. ACM contains the primary hard disk drive (HDD) where the operating system, application programs, and data files reside. The security system is used to prevent illegal access and copying of any file residing on the HDD inside ACM. An ACM is a self-contained computing device that can be armed with security software and hardware to protect its owner's private files and data. ACM docks with a computer bay in a wide variety of peripheral consoles. The combined ACM and peripheral console function as a personal computer. A computer module interface bus connects ACM and peripheral device. In some embodiments, all ACM data passes through computer module interface (CMI) bus to reach any device in the peripheral console, i.e. floppy drive, removable media, secondary hard disk drive, modem, and others. CMI bus data transfer is controlled by a pair of interface controllers on either side of the bus. This partitioning of a personal computer offer a way of protecting against illegal access of data residing within ACM by guarding data transaction through the computer module interface bus.

In a specific embodiment, a secured ACM has an enclosure that includes the following components:

    • 1) ACPU,
    • 2) Main memory,
    • 3) A primary Hard Disk Drive (HDD),
    • 4) Operating System, application software, data files on primary HDD,
    • 5) Interface circuitry and connectors to peripheral console,
    • 6) Flash memory used for storing security code and ID,
    • 7) Data detection and control circuitry to manage data flow to peripheral console,
    • 8) Circuit board connecting the above components, and others.

A peripheral console includes some of the following elements:

1) Input means, e.g. keyboard and mouse,

    • 2) Display means, e.g. CRT monitor, or integrated LCD display,
    • 3) Removable storage media subsystem, e.g. Floppy drive, CDROM drive,
    • 4) Communication device, e.g. LAN or modem,
    • 5) Computer Module Bay, interface device and connectors to ACM,
    • 6) Flash memory with security ID,
    • 7) Power supply or battery system, and other devices.

The Computer Module Bay (CMB) is an opening in a peripheral console that receives ACM. CMB provides mechanical protection and electrical connection to ACM. The Computer Module Interface bus is made up of 3 bus components: video bus, peripheral data bus, and power bus. Video Bus consists of video output of graphics devices, i.e. analog RGB and control signals for monitor, or digital video signals to drive flat panel displays. Power bus supplies the power for ACM. Peripheral data bus is a high speed, compressed, peripheral bridge bus managed by a Host Interface Controller in ACM and a peripheral Interface Controller in peripheral console. In some embodiments, all peripheral data transaction passes through the interface controllers.

The implementation of the secured ACM generally includes the following elements:

    • 1) A programmable Flash memory controlled by the Peripheral Interface Controller containing the security ID for the peripheral console,
    • 2) A programmable Flash memory controlled by the Host Interface Controller containing hardware specific security code and ID for the computer module,
    • 3) A data detection and control circuitry within Host Interface Controller to detect and manage data going out of ACM, and
    • 4) A low level hardware dependent security code to perform security ID matching, hardware programming to manage data flow,
    • 5) A high-level security program to manage user interface, program security ID, program security level, and other functions.

The hardware and software implementation allow more flexibility in the level of security protection offered to an ACM owner. Some examples of security levels are:

    • 1) No access—Security IDs do not match according to owner's requirement. The Host Interface Controller blocks all peripheral data traffic between ACM and peripheral console except for keyboard and mouse,
    • 2) Peripheral Read-only—No files can be written to any peripheral devices. All peripheral devices in peripheral console are managed as Read-only devices. The primary hard disk drive in ACM can be accessed freely,
    • 3) Limited access—Certain peripheral devices are allowed read/write access, i.e. modem, and other devices are Read-only, i.e. removable media devices,
    • 4) Full access—No restriction, and others.

Upon power up, the low level security code is executed to compare security ID between the respective flash memory between ACM and peripheral console. Typical security ID can include:

    • 1) User ID
    • 2) User password
    • 3) User Access privilege
    • 4) Business ID
    • 5) Business password
    • 6) Equipment ID
    • 7) Equipment access privilege, and any other security IDs.

The user through the security program can activate different levels of password protection, which can be stored in a look up table. The company through the security program can control different levels of access privilege of a user, a business group, or equipment. The security code then program the security level allowed by the access privilege determined by the security ID matching result. For example, if an unidentified peripheral console is detected upon power up by the low level security code, e.g. a home unit, the access privilege can set to Peripheral Read-only. With Read-only access privilege for all peripheral devices in peripheral console, the data detection and control circuitry is programmed to monitor all data traffic going to the peripheral console. Any memory block transfer to peripheral console will be detected and blocked. Under this mode, a user can use the computer with free access to the primary HDD in ACM. Any files can be read from other storage media in the peripheral console. But no files from the primary HDD can be copied to another media.

The data detection circuitry separately monitors peripheral bus operation type and memory address range being accessed. A specific address range for memory accesses and for I/O accesses can be programmed for the data detection circuitry to flag a match. A data blocking circuitry is triggered by the detection circuitry when a match occurs, and blank out the data that is being sent to the peripheral console. For the security system to be effective, a temper tamper resistant enclosure must be used to prevent removal of the hard disk drive and the flash memory inside ACM. Further details are shown throughout the present specification and more particularly below.

FIG. 4 is a simplified illustration of security systems 300 according to embodiments of the present invention. This illustration is merely an example, which should not limit the scope of the claims herein. One of ordinary skill in the art would recognize other variations, modifications, and alternatives. The systems show various examples of ways to implement the present invention. Here, a user relies upon certain consoles to access information. A company's shared portable console 325 can access general company information 303. Selected security identification information 315 is entered into the shared console to access the information via a network. The information generally includes owner, owner password, business, business password, console type, location, and access privilege information, which is displayed on a user display. The owner is generally the user name. Owner password is the user password. The business is the business unit name and business password is the business unit password. The console type can be portable for laptops, notebooks, and the like. Alternatively, the console type can be a desktop. The location generally specifies the desktop location or address for a networked system. Alternatively, the location can also be a home location. Access privilege can be categorized into many different levels. For example, the user can access general company information, but not information directed to other business units. The user can also be limited to access his/her private information, which is company related. Many other types of information can be restricted or accessed depending upon the embodiment.

Other types of access can be granted depending upon the consoles. For example, various consoles include, among others, a console at a user's home, e.g., “John Doe's,” a console in the user's office 329, a console in a co-worker's office 331, which the user can access. The access from John Doe's home console uses security identification 317 and provides restricted access 305. The user's use of the module 307 can be from a variety of consoles and is accessed using security identification 319. Here, access privilege is private, which allows the user to access private personal information or private company information that the user has created. The user's access from his office relies upon security identification 321, which grants access to private information and general company information. The co-worker's console can also be used with security identification 323, which allows the user to access general company information but not private information of John Doe, for example. Depending upon the console used by the user, the security system can provide partial or full access to information on servers via network as well as an attached computer module. Information can also be limited to read only for certain information sources such as a server, a hard drive, a floppy drive, and others.

In a specific embodiment, the present invention also provides a security feature for the ACM 307. Here, the user of the ACM can be granted access to information in the ACM if the correct security identification information 319 is provided to the combination of ACM and console. Once the correct information is provided, the user can access the information on the hard drive of the ACM, which can be for private use. Other levels of access and security can also be provided depending upon the application.

FIG. 5 is a simplified diagram 500 of a computer module in a console according to an embodiment of the present invention. This diagram is merely an illustration which should not limit the scope of the claims herein. One of ordinary skill in the art would recognize other variations, modifications, and alternatives. The block diagram 500 includes an attached computer module 501 and a peripheral console 503, as well as other elements as desired. These elements have a variety of features such as those noted above, as well as others. In the present diagram, different reference numerals are used to show the operation of the present system.

The block diagram 500 illustrates attached computer module 501. The module 501 has a central processing unit 502, which communicates to a north bridge 541, by way of a CPU bus 527. The north bridge couples to main memory 523 via memory bus 529. The main memory can be any suitable high speed memory device or devices such as dynamic random access memory (“DRAM”) integrated circuits and others. The DRAM includes at least 32 Meg. or 64 Meg. and greater of memory, but can also be less depending upon the application. Alternatively, the main memory can be coupled directly with the CPU in some embodiments. The north bridge also couples to a graphics subsystem 515 via bus 542. The graphics subsystem can include a graphics accelerator, graphics memory, and other devices. Graphics subsystem transmits a video signal to an interface connector, which couples to a display, for example.

The attached computer module also includes a primary hard disk drive 509 that serves as a main memory unit for programs and the like. The hard disk can be any suitable drive that has at least 2 GB and greater. As merely an example, the hard disk is a Marathon 2250 (2.25 GB, 2½ inch drive) product made by Seagate Corporation of Scotts Valley, but can be others. The hard disk communicates to the north bridge by way of a hard disk drive controller and bus lines 502 and 531. The hard disk drive controller couples to the north bridge by way of the host PCI bus 531, which connects bus 537 to the north bridge. The hard disk includes computer codes that implement a security program according to the present invention. Details of the security program are provided below.

The attached computer module also has a flash memory device 505 with a BIOS. The flash memory device 505 also has codes for a user password that can be stored in the device. The flash memory device generally permits the storage of such password without a substantial use of power, even when disconnected. As merely an example, the flash memory device has at least 512 kilobits or greater of memory, or 1 megabits or greater of memory. The flash memory device can store a security identification number or the like. The flash memory device is generally non-volatile and can preserve information even when the power is turned off, for example. The flash memory generally has at least 128 kilobits storage cells or more. The flash memory can be any product such as a W29C020 product made by a company called Winbond of Taiwan, but can also be others. The flash memory cell and user identification will be more fully described below in reference to the FIGS. A host interface controller 507 communications to the north bridge via bus 535 and host PCI bus. The host interface controller also has a data control 511. Host interface controller 507 communicates to the console using bus 513, which couples to connection 515.

Peripheral console 503 includes a variety of elements to interface to the module 501, display 551, and network 553. The console forms around south bridge 571, which couples to bus 563, which couples to bus 561. Bus 561 is in communication with network card 555, which is a local area network for Ethernet, for example. South bridge also couples through control 569 to peripheral interface controller 567, which also communicates to bus 561. Peripheral interface controller also couples to host interface controller through connection 515 and bus 513. The peripheral console has a primary removable drive 559 connected to south bridge through bus 575. South bridge also couples to secondary hard disk through bus 577.

In a specific embodiment, the peripheral console also has a serial EEPROM memory device 575, which is coupled to the peripheral interface controller. The memory device can store a security identification number or the like. The memory device is generally non-volatile and can preserve information even when the power is turned off, for example. The memory generally has at least 16 kilobits of storage cells or more. Preferably, the memory device is a 16 kilobit device or 64 megabit device or greater, depending upon the application. The memory can be any product such as a X24320 product made by a company called Xicor, but can also be others. The memory cell and user identification will be more fully described below in reference to the FIGS.

FIG. 6 is a simplified diagram of a security method 600 for a module according to an embodiment of the present invention. This diagram is merely an illustration which should not limit the scope of the claims herein. One of ordinary skill in the art would recognize other variations, modifications, and alternatives. The present method shows an example of how the present security method can be implemented. The present method uses a combination of software 601 and hardware 603, which is in the computer module. A plurality of external devices can be accessed depending upon the embodiment. These external devices include a secondary hard drive 618, a removable drive 619, a network (e.g., LAN, modem) device 621, and others. A keyboard 623 is also shown, which can act locally.

The software 601 includes an operating system 609, application programs 607, and a data security and initialization program 605. Other programs can also exist. Additionally, some of these programs may not exist. Preferably, the data security and initialization program exists. This data security and initialization program is initiated once the attached computer module is inserted into the console. The program interface and oversees a variety of hardware features, which will be used to control access to the external devices, for example. Of course, the particular configuration of the software will depend upon the application.

Hardware features can be implemented using a primary hard disk 611 coupled to a CPU/cache combination, which includes a main memory. The main memory is often a volatile memory such as dynamic random access memory. Data from any one of the external devices can enter the CPU/cache combination. For example, the secondary hard disk memory and I/O address range data is transferred 624 to the CPU/cache combination. The removable drive memory and I/O address range data can also transfer 625 to the CPU/cache combination. The LAN memory and 1/0 address range data can also transfer 626 to the CPU/cache combination. Keyboard data can also transfer 627 to the CPU/cache combination. To write data from the module into any one of these external elements, the data security program interfaces with the data detection and control circuit to determine of such data should be transferred to any one of the external elements. As noted, the external elements include, among others, secondary hard disk, and removable drive. Here, the data security program checks the security identification number with other numbers to determine the security access level. There are many other ways that the present invention can be implemented. These methods are described more fully below.

FIG. 7 is a simplified diagram 700 of a method according to an embodiment of the present invention. This diagram is merely an illustration which should not limit the scope of the claims herein. One of ordinary skill in the art would recognize other variations, modifications, and alternatives. The present method begins at power up, which is step 701. The present method reads a security code, which has been entered by a user, for example, in step 703. The security code can be a string of characters, including numbers and letters. The security code is preferably a mixture of numbers and letters, which are at least about 6 characters in length, but is not limited.

The present method reads (step 703) the security code, which has been entered. Next, the security code is compared with a stored code, which is in flash memory or the like (step 705). If the compared code matches with the stored code, the method resumes to step 708. Alternatively, the method goes to step 707 via branch 706 where no access is granted. When no access is granted, all data are blocked out from the user that attempts to log onto the system. Alternatively, the method determines if a certain level of access is granted, step 708. Depending upon the embodiment, the present method can grant full access, step 710, via branch 716. The present method allows full access based upon information stored in the flash memory device. Alternatively, the method can allow the user to access a limited amount of information.

Here, the present method allows for at least one or more than two levels of access. In a specific embodiment, the present method allows for the user of the module to access peripheral storage (step 711). The access privilege is read-only. The user can read information on the peripheral storage including hard disks and the like. Once the user accesses the storage, the method data control , step 719, takes over, where the hardware prevents the user from accessing other information, step 721. In a specific embodiment, the method can allow information to be removed from the peripheral storage. If the method allows for data to be removed, step 723, the method goes through branch 731 to let data out, which can occur through the module. Alternatively, the method goes to block data (step 725) via branch 733. Depending upon the embodiment, the method returns to the decision block, step 723. Alternatively, the method traverses branch 714 to a peripheral read-only process, step 712. The read-only process programs data control, step 713. Next, the hardware takes over (step 715). The method blocks all data from being accessed by the user, step 717.

FIG. 8 is a simplified diagram of a system 800 according to an alternative embodiment of the present invention. This diagram is merely an example which should not limit the scope of the claims herein. One of ordinary skill in the art would recognize many other variations, modifications, and alternatives. The system 800 includes an attached computer module 801, which can be inserted into one of a plurality of console devices to create a “plug and play” operation. For example, the console device can be peripheral console 801 or peripheral console 805. Each peripheral console can have similar or different connection characteristics. Peripheral console 803 couples to a local area network using Ethernet 817. Peripheral console 805 couples to a DSL line 827 through a DSL modem 825. Other consoles can also be included to use other types of networks such as ADSL, Cable Modem, wireless, Token Ring, and the like.

As shown, the attached computer module has elements such as a memory region 807, which stores BIOS information, a security code, and a security identification number on a flash memory device or the like. The memory region couples to a central processing region 809, which can include CPU, chipset, cache memory, graphics, and a hard disk drive, as well as other features. The central processing region couples to a host interface controller, which interfaces the attached computer module to one of the peripheral consoles. Any of the above information can also be included in the attached computer module.

Each peripheral console also has a variety of elements. These elements include a region 813, 821, which has a flash memory device with a security identification number, a password, access information, access privileges, internet service provider access information, as well as other features, which were previously noted. The peripheral console also has an interface controller 815, 823, which couples region 813, 821, respectively to a networking device 817, 825. The networking device can be an Ethernet card 817, which allows communication to the local area network 819. Alternatively, the networking device can be a DST, modem 825, which allows communication to a DSL (or ADSL) phone line. Other types of networking device can also be used, depending upon the application.

Each console provides a selected connection based upon set of predefined factors. These factors include communication hardware information so that software in attached computer module can read and allow a connection to a network. Here, access information can be provided to the user. Information about connection information will also be included. This connection information includes telephone numbers, account numbers, passwords (local), or a company password. The console and module combination will take care of charges, etc. based upon time bases. Module will have credit card information, but will have security. In a specific embodiment, the module inserts into the console. The module then asks the console which hardware will be used. If the hardware is an Ethernet connect, the module configures connection information to access the Ethernet connection. Alternatively, if the hardware requires a DSL connection, the module configures connection information to access the DSL connection. Other configuration information such as company server information, password, can also be provided.

A personal computer system that comprises two physically separate units and the interconnection between them is disclosed. The first unit, an attached computing module (ACM), contains the core computing power and environment for a computer user. The second unit, a peripheral console (PCON), contains the power supply and primary input and output devices for the computer system. An ACM and a PCON are coupled with one another to form a fully functional personal computer system.

FIG. 9 depicts a notebook computer PCON configuration. The opening of the computer bay 992 is visible at the side of the PCON unit 900. The PCON 900 provides an integrated LCD display panel 910 as the user's primary display device. The PCON 900 provides an integrated keyboard 922 as the user's primary input device.

FIG. 10 is a block diagram of the components in one computer system. The computer system comprises an attached computer module (ACM) 1000, a peripheral console (PCON) 1001, and the interconnection apparatus 1003 between them. The ACM 1000 includes the central processing unit (CPU) 1010, system memory 1020, high performance devices 1050, primary mass storage 1030, and related interface and support circuitry 1040. The PCON 1001 includes primary display 1011, primary input 1021, secondary mass storage 1051, other devices 1061, expansion slots 1071, the primary power supply 1031, and related interface and support circuitry 1041. The interconnection apparatus 1003 includes circuitry to convey power and operational signals between the ACM 1000 and PCON 1001.

Within the ACM 1000, the CPU 1010 executes instructions and manipulates data stored in the system memory 1020. The CPU 1010 and system memory 1020 represent the user's core computing power. The core computing power may also include high performance devices 1050 such as advanced graphics processor chips that greatly increase overall system performance and which, because of their speed, need to be located close to the CPU 1010. The primary mass storage 1030 contains persistent copies of the operating system software, application software, configuration data, and user data. The software and data stored in the primary mass storage device 1030 represent the user's computing environment. Interface and support circuitry 1040 primarily includes interface chips and signal busses that interconnect the CPU 1010, system memory 1020, high performance devices 1050, and primary mass storage 1030. The interface and support circuitry 1040 also connects ACM-resident components with the ACM-to-PCON interconnection apparatus 1003 as needed.

Within the PCON 1001, the primary display component 1011 may include an integrated display device or connection circuitry for an external display device. This primary display device 1011 may be, for example, an LCD, plasma, or CRT display screen used to display text and graphics to the user for interaction with the operating system and application software. The primary display component 1011 is the primary output of the computer system, i.e., the paramount vehicle by which programs executing on the CPU 1010 can communicate toward the user.

The primary input component 1021 of the PCON 1001 may include an integrated input device or connection circuitry for attachment to an external input device. The primary input 1021 may be, for example, a keyboard, touch screen, keypad, mouse, trackball, digitizing pad, or some combination thereof to enable the user to interact with the operating system and application software. The primary input component 1021 is the paramount vehicle by which programs executing on the CPU 1010 receive signals from the user.

The PCON 1001 may contain secondary mass storage 1051 to provide additional high capacity storage for data and software. Secondary mass storage 1051 may have fixed or removable media and may include, for example, devices such as diskette drives, hard disks, CD-ROM drives, DVD drives, and tape drives.

The PCON 1001 may be enhanced with additional capability through the use of integrated “Other Devices” 1061 or add-on cards inserted into the PCON's expansion slots 1071. Examples of additional capability include sound generators, LAN connections, and modems. Interface and support circuitry 1041 primarily includes interface chips, driver chips, and signal busses that interconnect the other components within the PCON 1001. The interface and support circuitry 1041 also connects PCON-resident components with the ACM-to-PCON interconnection apparatus 1003 as needed.

Importantly, the PCON 1001 houses the primary power supply 1031. The primary power supply 1031 has sufficient capacity to power both the PCON 1001 and the ACM 1000 for normal operation. Note that the ACM 1000 may include a secondary “power supply” in the form, for example, of a small battery. Such a power supply would be included in the ACM 1000 to maintain, for example, a time-of-day clock, configuration settings when the ACM 1000 is not attached to a PCON, or machine state when moving an active ACM immediately from one PCON to another. The total energy stored in such a battery would, however, be insufficient to sustain operation of the CPU 1010 at its rated speed, along with the memory 1020 and primary mass storage 1030, for more than a fraction of an hour, if the battery were able to deliver the required level of electrical current at all.

FIG. 11 is a block diagram of an attached computing module (ACM) 1100. The physical ACM package 1100 contains the ACM functional components 1101 and the ACM side of the ACM-to-PCON Interconnection 1700. The ACM 1101 comprises a CPU component 1110, a system memory component 1120, a primary mass storage component 1130, a high performance devices components 1150, and an interface and support component 1140.

The ACM side of the ACM-to-PCON Interconnection 1700 comprises a Host Interface Controller (HIC) component 1720 and an ACM connector component 1730. The HIC 1720 and connector 1730 components couple the ACM functional components 1100 with the signals of an ACM-to-PCON interface bus 1710 used to operatively connect an ACM with a PCON. The ACM-to-PCON interface bus 1710 comprises conveyance for electrical power 1714 and signals for a peripheral bus 1712, video 1716, video port 1717, and console type 1718. The preferred ACM-to-PCON Interconnection 1700 is described in detail in a companion U.S. patent application Ser. No. 09/149,882, entitled “A Communication Channel and Interface Devices for Bridging Computer Interface Buses,” by the same inventor, filed on Sep. 8, 1998, and hereby incorporated by reference. The preferred ACM-to-PCON interconnection 1700 includes circuitry to transmit and receive parallel bus information from multiple signal paths as a serial bit stream on a single signal path. This reduces the number of physical signal paths required to traverse the interconnection 1700. Further, employing low-voltage differential signaling (LVDS) on the bit stream data paths provides very reliable, high-speed transmission across cables. This represents a further advantage of the present invention.

Clocking circuitry 1144 generates clock signals for distribution to other components within the ACM 1100 that require a timing and synchronization clock source. The CPU 1110 is one such component. Often, the total power dissipated by a CPU is directly proportional to the frequency of its main clock signal. The presently described embodiment of the ACM 1100 includes circuitry that can vary the frequency of the main CPU clock signal conveyed to the CPU 1110 via signal path 1162, in response to a signal received from the host interface controller (HIC) 1720 via signal path 1161. The generation and variable frequency control of clocking signals is well understood in the art. By varying the frequency, the power consumption of the CPU 1110 (and thus the entire ACM 1100) can be varied.

The variable clock rate generation may be exploited to match the CPU power consumption to the available electrical power. Circuitry in the host interface controller (HIC) 1720 of the presently described embodiment adjusts the frequency control signal sent via signal path 1161 to the clocking circuitry 1144, based on the “console type” information signal 1718 conveyed from the peripheral console (PCON) by the CPU-to-PCON interconnection 1700.

FIG. 12 is a block diagram of a peripheral console (PCON). A peripheral console couples with an ACM to form an operating personal computer system. The peripheral console (PCON) supplies an ACM with primary input, display, and power supply; the ACM supplies the core computing power and environment of the user. In the presently described embodiment the physical PCON package 1200 contains the PCON functional components 1201 and the PCON side of the ACM-to-PCON Interconnection 1800. The PCON functional components 1201 comprise primary display 1210, a primary input 1220, a primary power supply 1230, interface and support 1240, secondary mass storage 1250, other devices 1260, and expansion slots 1270.

The PCON side of the ACM-to-PCON Interconnection 1800 comprises a Peripheral Interface Controller (PIC) component 1840, a PCON connector component 1850, console-type component 1842, and flash memory device 1848. The PIC 1840 and connector 1850 components couple the PCON functional components 1201 with the signals of an ACM-to-PCON interface bus 1810 used to operatively connect an ACM with a PCON. The ACM-to-PCON interface bus 1810 comprises conveyance for electrical power 1814 and signals for a peripheral bus 1812, video 1816, video port 1817, and console-type 1818. The preferred ACM-to-PCON Interconnection 1800 is described in detail in the U.S. patent application entitled “A Communication Channel and Interface Devices for Bridging Computer Interface Buses,” already incorporated herein by reference.

Connector component 1850 may be selected to mate directly with the connector component 1730 of an ACM (shown in FIG. 11). Alternatively, connector component 1850 may be selected to mate with, for example, the connector on one end of a cable intervening between the PCON and an ACM in a particular embodiment. The ACM-to-PCON interconnection described in the aforementioned companion patent application has the advantage of providing reliable signal conveyance across low cost cables.

Flash memory device 1848 provides non-volatile storage. This storage may be accessible to devices in both the ACM and the PCON, including the host interface controller and the peripheral interface controller 1840 to which it is connected. As such, flash memory 1848 may be used to store configuration and security data to facilitate an intelligent mating between an ACM and a PCON that needs no participation of the CPU.

The secondary mass storage component 1250 of the PCON functional circuitry 1201 of the presently described embodiment comprises diskette drive 1254, hard disk drive 1252, and CD-ROM drive 1256. Secondary mass storage 1250 generally provides low-cost, non-volatile storage for data files which may include software program files. Data files stored on secondary mass storage 1250 are not part of a computer user's core computing power and environment. Secondary mass storage 1250 may be used to store, for example, seldom used software programs, software programs that are used only with companion hardware devices installed in the same peripheral console 1200, or archival copies of data files that are maintained in primary mass storage 1130 of an ACM (shown in FIG. 11). Storage capacities for secondary mass storage 1250 devices may vary from the 1.44 megabytes of the 3.5-inch high density diskette drive 1254, to more than 10 gigabytes for a large format (5-inch) hard disk drive 1252. Hard disk drive 1252 employs fixed recording media, while diskette drive 1254 and CD-ROM drive 1256 employ removable media. Diskette drive 1254 and hard disk drive 1252 support both read and write operations (i.e., data stored on their recording media may be both recalled and modified) while CD-ROM drive 1256 supports only read operations.

Two PCI or PCI-like buses are interfaced using a non-PCI or non-PCI-like channel. PCI control signals are encoded into control bits, and the control bits, rather than the control signals that they represent, and are transmitted on the interface channel. At the receiving end, the control bits representing control signals are decoded back into PCI control signals prior to being transmitted to the intended PCI bus.

The fact that control bits rather than control signals are transmitted on the interface channel allows using a smaller number of signal channels and a correspondingly small number of conductive lines in the interface channel than would otherwise be possible. This is because the control bits can be more easily multiplexed at one end of the interface channel and recovered at the other end than control signals. This relatively small number of signal channels used in the interface channel allows using LVDS channels for the interface. As mentioned above, an LVDS channel is more cable friendly, faster, consumes less power, and generates less noise than a PCI bus channel. Therefore, an LVDS channel is advantageously used for the hereto unused purpose of interfacing PCI or PCI-like buses. The relatively smaller number of signal channels in the interface also allows using connectors having smaller pins counts. As mentioned above an interface having a smaller number of signal channels and, therefore, a smaller number of conductive lines is less bulky and less expensive than one having a larger number of signal channels. Similarly, connectors having a smaller number of pins are also less expensive and less bulky than connectors having a larger number of pins.

In one embodiment, the present invention encompasses an apparatus for bridging a first computer interface bus and a second computer interface bus, in a microprocessor based computer system where each of the first and second computer interface buses have a number of parallel multiplexed address/data bus lines and operate at a clock speed in a predetermined clock speed range having a minimum clock speed and a maximum clock speed. The apparatus comprises an interface channel having a clock channel and a plurality of bit channels for transmitting bits; a first interface controller coupled to the first computer interface bus and to the interface channel to encode first control signals from the first computer interface bus into first control bits to be transmitted on the interface channel and to decode second control bits received from the interface channel into second control signals to be transmitted to the first computer interface bus; and a second interface controller coupled to the interface channel and the second computer interface bus to decode the first control bits from the interface channel into third control signals to be transmitted on the second computer interface bus and to encode fourth control signals from the second computer interface bus into the second control bits to be transmitted on the interface channel.

In one embodiment, the first and second interface controllers comprise a host interface controller (HIC) and a peripheral interface controller (PIC), respectively, the first and second computer interface buses comprise a primary PCI and a secondary PCI bus, respectively, and the interface channel comprises an LVDS channel.

In a preferred embodiment, the interface channel has a plurality of serial bit channels numbering fewer than the number of parallel bus lines in each of the PCI buses and operates at a clock speed higher than the clock speed at which any of the bus lines operates. More specifically, the interface channel includes two sets of unidirectional serial bit channels which transmit data in opposite directions such that one set of bit channels transmits serial bits from the HIC to the PIC while the other set transmits serial bits from the PIC to the HIC. For each cycle of the PCI clock, each bit channel of the interface channel transmits a packet of serial bits.

The HIC and PIC each include a bus controller to interface with the first and second computer interface buses, respectively, and to manage transactions that occur therewith. The HIC and PIC also include a translator coupled to the bus controller to encode control signals from the first and second computer interface buses, respectively, into control bits and to decode control bits from the interface channel into control signals. Additionally, the HIC and PIC each include a transmitter and a receiver coupled to the translator. The transmitter converts parallel bits into serial bits and transmits the serial bits to the interface channel. The receiver receives serial bits from the interface channel and converts them into parallel bits.

FIG. 13 is a block diagram of one embodiment of a computer system 1300 using the interface of the present invention. Computer system 1300 includes an attached computer module (ACM) 1305 and a peripheral console 1310, which are described in greater detail in the application of William W. Y. Chu, Ser. No. 09/149,548, for “Personal Computer Peripheral Console With Attached Computer Module” filed on Sep. 8, 1998 and incorporated herein by reference. The ACM 1305 and the peripheral console 1310 are interfaced through an exchange interface system (XIS) bus 1315. The XIS bus 1315 includes power bus 1316, video bus 1317 and peripheral bus (XPBus) 1318, which is also herein referred to as an interface channel. The power bus 1316 transmits power between ACM 1305 and peripheral console 1310. In a preferred embodiment power bus 1316 transmits power at voltage levels of 3.3 volts, 5 volts and 12 volts. Video bus 1317 transmits video signals between the ACM 1305 and the peripheral console 1310. In a preferred embodiment, the video bus 1317 transmits analog Red Green Blue (RGB) video signals for color monitors, digital video signals (such as Video Electronics Standards Association (VESA) Plug and Display's Transition Minimized Differential Signaling (TMDS) signals for flat panel displays), and television (TV) and/or super video (S-video) signals. The XPBus 1318 is coupled to host interface controller (HIC) 1319 and to peripheral interface controller (PIC) 1320, which is also sometimes referred to as a bay interface controller.

In the embodiment shown in FIG. 13, HIC 1319 is coupled to an integrated unit 1321 that includes a CPU, a cache and a north bridge. In another embodiment, a CPU and north bridge are separate rather than integrated units. In yet another embodiment, the HIC and PIC are integrated with the north and south bridges, respectively, such that integrated HIC and north bridge unit includes an HIC and a north bridge, while integrated PIC and south bridge unit includes a PIC and a south bridge.

FIG. 14 is a detailed block diagram of one embodiment of the HIC of the present invention. As shown in FIG. 14, HIC 1600 comprises bus controller 1610, translator 1620, transmitter 1630, receiver 1640, a PLL 1650, an address/data multiplexer (A/D MUX) 1660, a read/write controller (RD/WR Cntl) 1670, a video serial to parallel converter 1680 and a CPU control & general purpose input/output latch/driver (CPU CNTL & GPIO latch/driver) 1690.

HIC 1600 is coupled to an optional flash memory BIOS configuration unit 1601. Flash memory unit 1601 stores basic input output system (BIOS) and PCI configuration information and supplies the BIOS and PCI configuration information to A/D MUX 1660 and RD/WR Control 1670, which control the programming, read, and write of flash memory unit 1601.

Bus controller 1610 is coupled to the host PCI bus, which is also referred to herein as the primary PCI bus, and manages PCI bus transactions on the host PCI bus. Bus controller 1610 includes a slave (target) unit 1611 and a master unit 1616. Both slave unit 1611 and master unit 1616 each include two first in first out (FIFO) buffers, which are preferably asynchronous with respect to each other since the input and output of the two FIFOs in the master unit 1616 as well as the two FIFOs in the slave unit 1611 are clocked by different clocks, namely the PCI clock and the PCK. Additionally, slave unit 1611 includes encoder 1622 and decoder 1623, while master unit 1616 includes encoder 1627 and decoder 1628. The FIFOs 1612, 1613, 1617 and 1618 manage data transfers between the host PCI bus and the XPBus, which in the embodiment shown in FIG. 14 operate at 33 MHz and 66 MHz, respectively. PCI address/data (AD) from the host PCI bus is entered into FIFOs 1612 and 1617 before they are encoded by encoders 1622 and 1627. Encoders 1622 and 1627 format the PCI address/data bits to a form more suitable for parallel to serial conversion prior to transmittal on the XPBus. Similarly, address and data information from the receivers is decoded by decoders 1623 and 1628 to a form more suitable for transmission on the host PCI bus.

The multiplexed parallel A/D bits and some control bits input to transmitter 1630 are serialized by parallel to serial converters 1632 of transmitter 1630 into 10 bit packets. These bit packets are then output on data lines PD0 to PD3 of the XPBus. Other control bits are serialized by parallel to serial converter 1633 into 10 bit packets and sent out on control line PCN of the XPBus.

FIG. 15 is a detailed block diagram of one embodiment of the PIC of the present invention. PIC 11100 is nearly identical to HIC 1600 in its function, except that HIC 1600 interfaces the host PCI bus to the XPBus while PIC 11100 interfaces the secondary PCI bus to the XPBus. Similarly, the components in PIC 11100 serve the same function as their corresponding components in HIC 1600. Reference numbers for components in PIC 11100 have been selected such that a component in PIC 11100 and its corresponding component in HIC 1600 have reference numbers having the same two least significant digits. Thus for example, the bus controller in PIC 11100 is referenced as bus controller 11110 while the bus controller in HIC 1600 is referenced as bus controller 1610. As many of the elements in PIC 11100 serve the same functions as those served by their corresponding elements in HIC 1600 and as the functions of the corresponding elements in HIC 1600 have been described in detail above, the function of elements of PIC 11100 having corresponding elements in HIC 1600 will not be further described herein. Reference may be made to the above description of FIG. 14 for an understanding of the functions of the elements of PIC 11100 having corresponding elements in HIC 1600.

FIG. 16 is a schematic diagram of lines PCK, PD0 to PD3, and PCN. These lines are unidirectional LVDS lines for transmitting clock signals and bits from the HIC to the PIC. The bits on the PD0 to PD3 and the PCN lines are sent synchronously within every clock cycle of the PCK. Another set of lines, namely PCKR, PDR0 to PDR3, and PCNR, are used to transmit clock signals and bits from the PIC to HIC. The lines used for transmitting information from the PIC to the HIC have the same structure as those shown in FIG. 16, except that they transmit data in a direction opposite to that in which the lines shown in FIG. 16 transmit data. In other words they transmit information from the PIC to the HIC. The bits on the PDR0 to PDR3 and the PCNR lines are sent synchronously within every clock cycle of the PCKR. Some of the examples of control information that may be sent in the reverse direction, i.e., on PCNR line, include a request to switch data bus direction because of a pending operation (such as read data available), a control signal change in the target requiring communication in the reverse direction, target busy, and transmission error detected.

The XPBus which includes lines PCK, PD0 to PD3, PCN, PCKR, PDR0 to PDR3, and PCNR, has two sets of unidirectional lines transmitting clock signals and bits in opposite directions. The first set of unidirectional lines includes PCK, PD0 to PD3, and PCN. The second set of unidirectional lines includes PCKR, PDR0 to PDR3, and PCNR. Each of these unidirectional set of lines is a point-to-point bus with a fixed transmitter and receiver, or in other words a fixed master and slave bus. For the first set of unidirectional lines, the HIC is a fixed transmitter/master whereas the PIC is a fixed receiver/slave. For the second set of unidirectional lines, the PIC is a fixed transmitter/master whereas the HIC is a fixed receiver/slave. The LVDS lines of XPBus, a cable friendly and remote system I/O bus, transmit fixed length data packets within a clock cycle.

The XPBus lines, PD0 to PD3, PCN, PDR0 to PDR3 and PCNR, and the video data and clock lines, VPD and VPCK, are not limited to being LVDS lines, as they may be other forms of bit based lines. For example, in another embodiment, the XPBus lines may be IEEE 1394 lines.

It is to be noted that although each of the lines PCK, PD0 to PD3, PCN, PCKR, PDR0 to PDR3, PCNR, VPCK, and VPD is referred to as a line, in the singular rather than plural, each such line may contain more than one physical line. For example, in the embodiment shown in FIG. 16, each of lines PCK, PD0 to PD3 and PCN includes two physical lines between each driver and its corresponding receiver. The term line, when not directly preceded by the terms physical or conductive, is herein used interchangeably with a signal or bit channel of one or more physical lines for transmitting a signal. In the case of non-differential signal lines, generally only one physical line is used to transmit one signal. However, in the case of differential signal lines, a pair of physical lines is used to transmit one signal. For example, a pair of physical lines together transmit a signal in a bit line or bit channel in an LVDS or IEEE 1394 interface.

A bit based line (i.e., a bit line) is a line for transmitting serial bits. Bit based lines typically transmit bit packets and use a serial data packet protocol. Examples of bit lines include an LVDS line, an IEEE 1394 line, and a Universal Serial Bus (USB) line.

In the embodiment shown in FIG. 13, HIC 1319 is coupled to an integrated unit 1321 that includes a CPU, a cache and a north bridge. In another embodiment, such as that shown in FIG. 17, the CPU 1705 and north bridge 1710 are separate rather than integrated units. In yet another embodiment, such as that shown in FIG. 18, the HIC and PIC are integrated with the north and south bridges, respectively, such that integrated HIC and north bridge unit 1805 includes an HIC and a north bridge, while integrated PIC and south bridge unit 1810 includes a PIC and a south bridge. FIG. 19 shows an attached computer module with integrated CPU/NB/Graphics 1915 and Integrated HIC/SB 1920. FIG. 20 shows an attached computer module with single chip 2025 fully integrated: CPU, Cache, Core Logic, Graphics controller and Interface controller.

Although the functionality above has been generally described in terms of a specific sequence of steps, other steps can also be used. Here, the steps can be implemented in a combination of hardware, firmware, and software. Either of these can be further combined or even separated. Depending upon the embodiment, the functionality can be implemented in a number of different ways without departing from the spirit and scope of the claims herein. One of ordinary skill in the art would recognize other variations, modifications, and alternatives.

While the above is a full description of the specific embodiments, various modifications, alternative constructions and equivalents may be used. Therefore, the above description and illustrations should not be taken as limiting the scope of the present invention which is defined by the appended claims.

Claims

1. A security protection method for a computer module, said method comprising:

inserting the computer module into a console;
initiating a security program in said module to read a security identification of said console and to read a security identification of said computer module;
determining of a predetermined security status based upon a relationship of said console identification and said computer module identification;
selecting said predetermined security status; and
operating said computer module based upon said security status.

2. The method of claim 1 wherein said predetermined security status disables a network access to the computer module.

3. The method of claim 1 wherein said predetermined security status disables a secondary storage of information from said computer module to substantially prevent information to be transferred from a memory of the computer module to said secondary storage.

4. The method of claim 1 wherein said security program is provided in a system BIOS.

5. The method of claim 1 wherein said step of initiating reads said security identification of said computer module from a flash memory device.

6. The method of claim 1 wherein said step of initiating reads said security identification of said console from a flash memory device.

7. The method of claim 1 wherein said console is selected from a desktop home computing device, an office desktop computing device, a mobile computing device, a television sot-top computing device, and a co-worker's computing device.

8. A system for secured information transactions, the system comprising:

a console comprising a peripheral controller housed in the console;
a user identification input device coupled to the peripheral controller, the user identification input device being provided for user identification data; and
an attached computer module coupled to the console, the attached computer module comprising a security memory device stored with the user identification data.

9. The system of claim 8 wherein the user identification input device is a finger print reader.

10. The system of claim 8 wherein the user identification input device is a voice processing device.

11. A method for operating a module computer into one of a plurality of network systems, the method comprising:

providing a computer module, the module comprising a connection program;
inserting the computer module into a computer console, the computer console having access to a network;
receiving connection information from the computer console;
configuring the connection program to adapt to the connection information; and
establish a connection between the computer module and a server coupled to the network.

12. The method of claim 11 wherein the connection information comprises a connection protocol for providing the connection.

13. The method of claim 12 wherein the connection protocol is selected from TCP/IP, or mobile IP.

14. A system for information transaction, the system comprising:

a console comprising a first low voltage differential signal channel comprising two sets of unidirectional, multiple serial bit channels to transmit data in opposite directions, a first interface controller coupled to the first low voltage differential signal channel to communicate an encoded serial bit stream of Peripheral Component Interconnect (“PCI”) bus transaction, a power supply, and a hard disk drive housed in the console; and
a computer module coupled to the console, the computer module comprising a central processing unit, a peripheral bridge directly coupled to the central processing unit without any intervening PCI bus, the peripheral bridge comprising a second interface controller, a second differential signal channel extending directly from the second interface controller, the second differential signal channel comprising two sets of unidirectional, serial bit channels to transmit data in opposite directions, a mass storage device coupled to the central processing unit through the peripheral bridge, and a security mechanism to provide access protection for the computer module,
wherein the computer module is configured to receive power from the power supply.

15. The system of claim 14, wherein the computer module further comprises a computing environment for a user.

16. The system of claim 14, wherein the computer module is coupled to the console through serial bit stream data paths employing low voltage differential signaling.

17. A system for information transaction, the system comprising:

a console comprising an integrated Liquid Crystal Display and a first low voltage differential signal channel comprising two sets of unidirectional, multiple serial bit channels to communicate an encoded serial bit stream of Peripheral Component Interconnect (“PCI”) bus transaction in opposite directions; and
a computer module coupled to the console in a “plug and play” operation, the computer module comprising a central processing unit, a peripheral bridge directly coupled to the central processing unit without any intervening PCI bus, the peripheral bridge comprising an interface controller that is integrated with the peripheral bridge, a second differential signal channel extending directly from the interface controller, the second differential signal channel comprising two sets of unidirectional, serial bit channels to transmit data in opposite directions, a mass storage device coupled to the central processing unit, and wherein the interface controller is configured to communicate a differential signaling serial bit stream with the console through the second differential signal channel.

18. The system of claim 17, wherein the computer module further comprises a computing environment for a user.

19. The system of claim 17, wherein the computer module further comprises a hardware dependent security code to perform security identification matching.

20. A system for information transaction, the system comprising:

a console comprising a power supply, a first low voltage differential signal channel comprising two sets of unidirectional, serial bit channels to transmit data in opposite directions, and a removable media drive housed in the console; and
a computer module coupled to the console, the computer module comprising a central processing unit comprising an interface controller, a mass storage device coupled to the central processing unit, and a second low voltage differential signal channel extending directly from the interface controller, the second low voltage differential signal channel comprising two sets of unidirectional, serial bit channels to transmit data in opposite directions, and wherein the interface controller is coupled to the console through the second low voltage differential signal channel, wherein the computer module is configured to receive power from the power supply.

21. The system of claim 20, wherein the first low voltage differential signal channel and the second low voltage differential signal channel are configured to transmit data in 10-bit packets.

22. The system of claim 20, wherein the computer module further comprises a computing environment for a user.

23. The system of claim 20, wherein the first low voltage differential signal channel is coupled to the second low voltage differential signal channel upon coupling of the computer module to the console.

24. A system to connect a computer module to a network, the system comprising:

a console comprising a power supply, a first low voltage differential signal channel comprising two sets of unidirectional, multiple serial bit channels to communicate an encoded serial bit stream of Peripheral Component Interconnect (“PCI”) bus transaction in opposite directions, and an Ethernet controller to provide access to a network; and
a computer module coupled to the console and powered by the power supply, the computer module comprising a central processing unit comprising an integrated interface controller, a second low voltage differential signal channel directly coupled to the integrated interface controller, the second low voltage differential signal channel comprising two sets of unidirectional, serial bit channels to transmit data in opposite directions, a mass storage device coupled to the central processing unit, and a connection software code,
wherein, upon coupling to the console, the computer module is configured to establish a connection to the network using the connection software code.

25. The system of claim 24, wherein the computer module is coupled to the console in a “plug and play” operation.

26. The system of claim 24, wherein the computer module further comprises a computing environment for a user.

27. An information transaction system comprising:

a console comprising an integrated keyboard, an integrated Liquid Crystal Display, a first low voltage differential signal channel comprising two sets of unidirectional, serial bit channels to transmit data in opposite directions, and an interface controller coupled to the first low voltage differential signal channel to communicate an encoded serial bit stream of Peripheral Component Interconnect (“PCI”) bus transaction; and
a computer module coupled to the console in a “plug and play” operation, the computer module comprising a central processing unit, a peripheral bridge coupled to the central processing unit without any intervening PCI bus, a second low voltage differential signal channel coupled to the peripheral bridge, the second low voltage differential signal channel comprising two sets of unidirectional, serial bit channels to transmit data in opposite directions, and a mass storage device comprising a flash memory.

28. The system of claim 27, wherein the central processing unit comprises an integrated circuit chip to operate on a varying clock frequency to vary a power consumption of the integrated circuit chip while in operation.

29. The system of claim 27, wherein the computer module further comprises a computing environment for a user.

30. The system of claim 27, wherein the peripheral bridge is directly coupled to the second low voltage differential signal channel to communicate a serial bit stream to the console.

31. A system for information transaction, the system comprising:

a console comprising an integrated keyboard, an integrated Liquid Crystal Display, and a first low voltage differential signal channel comprising two sets of unidirectional, serial bit channels to transmit data in opposite directions; and
a computer module coupled to the console, the computer module comprising a central processing unit, a peripheral bridge directly coupled to the central processing unit without any intervening Peripheral Component Interconnect bus, the peripheral bridge comprising an interface controller, a mass storage device comprising a flash memory, and a second low voltage differential signal channel extending directly from the interface controller, the second low voltage differential signal channel comprising two sets of unidirectional, serial bit channels to transmit data in opposite directions,
wherein the interface controller is coupled to the console through the second low voltage differential signal channel,
wherein the first low voltage differential signal channel is coupled to the second low voltage differential signal channel upon coupling of the computer module to the console.

32. The system of claim 31, wherein the computer module further comprises a security program to specify a security identification.

33. The system of claim 31, wherein the computer module further comprises a computing environment for a user.

34. An information transaction system comprising:

a console comprising a power supply, a first low voltage differential signal channel comprising two sets of unidirectional, serial bit channels to transmit data in opposite directions, and a removable media drive housed in the console; and
a computer module coupled to the console, the computer module comprising an integrated interface controller and central processing unit configured as a single chip, a flash memory comprising a security identification to provide access protection for the computer module, and a second low voltage differential signal channel extending directly from the integrated interface controller and central processing unit, the second low voltage differential signal channel comprising two sets of unidirectional, serial bit channels to transmit data in opposite directions,
wherein the integrated interface controller and central processing unit is coupled to the console through the second low voltage differential signal channel,
wherein the computer module is configured to receive power from the power supply.

35. The system of claim 34, wherein the computer module further comprises a computing environment for a user.

36. The system of claim 34, wherein the first low voltage differential signal channel is coupled to the second low voltage differential signal channel upon coupling of the computer module to the console.

37. (Twice Amended) A method to connect a computer module to a network, the method comprising:

providing a computer module, the computer module comprising (a) a central processing unit and (b) a storage device comprising a connection program;
inserting the computer module into a computer console in a “plug and play” operation, the computer console comprising (a) a low voltage differential signal channel comprising two sets of unidirectional, multiple serial bit channels to communicate an encoded serial bit stream of Peripheral Component Interconnect (“PCI”) bus transaction in opposite directions and (b) a networking device to provide access to an external network;
receiving connection information from the computer console to the computer module; and
using the connection program, establishing a connection between the computer module and the external network.

38. The method of claim 37, further comprising coupling the computer module to the low voltage differential signal channel.

39. The method of claim 37, wherein establishing the connection between the computer module and the external network comprises communicating with the external network through Ethernet.

40. A computer system comprising:

a console comprising a power supply and a first low voltage differential signal channel comprising two sets of unidirectional, serial bit channels to transmit data in opposite directions; and
a computer module coupled to the console, the computer module comprising a central processing unit to operate on a varying clock frequency to vary a power consumption of the central processing unit while in operation, a mass storage unit coupled to the central processing unit, a second low voltage differential signal channel comprising two sets of unidirectional, serial bit channels to transmit data in opposite directions, and a peripheral bridge directly coupled to the central processing unit without any intervening Peripheral Component Interconnect bus, the peripheral bridge comprising an interface controller to output a serial bit stream that is conveyed over the second low voltage differential signal channel,
wherein the interface controller is coupled to the console through the second low voltage differential signal channel,
wherein the computer module is configured to receive power from the power supply.

41. The computer system of claim 40, wherein the computer module further comprises a computing environment for a user.

42. The computer system of claim 40, wherein the first low voltage differential signal channel is coupled to the second low voltage differential signal channel upon coupling of the computer module to the console for data communication.

43. The computer system of claim 40, wherein the computer module is configured for insertion into the console as a “plug and play” operation.

44. A system to connect a computer module to a network, the system comprising:

a console comprising a power supply and a connection to a network; and
a computer module coupled to the console in a “plug and play” operation, the computer module comprising a processing unit, a low voltage differential signal channel comprising two sets of unidirectional, multiple serial bit channels to transmit data in opposite directions, a peripheral bridge comprising an interface controller coupled to the low voltage differential signal channel to communicate an encoded serial bit stream of address and data of Peripheral Component Interconnect (“PCI”) bus transaction, the peripheral bridge coupled to the processing unit without any intervening PCI bus, and a mass storage device comprising a connection program,
wherein the computer module is configured to receive power from the power supply, and the connection program is configured to establish communication with the network through the console.

45. The system of claim 44, wherein the processing unit comprises an integrated circuit chip to operate on a varying clock frequency to vary a power consumption of the integrated circuit chip while in operation.

46. The system of claim 44, wherein the connection to the network comprises an Ethernet connection.

47. The system of claim 44, wherein the computer module further comprises a computing environment for a user.

48. A computer system comprising:

a console comprising a power supply; and
a computer module coupled to the console, the computer module comprising a central processing unit, a low voltage differential signal channel comprising two sets of unidirectional, multiple serial bit channels to transmit data in opposite directions, an integrated interface controller and bridge unit coupled to the low voltage differential signal channel to communicate an encoded serial bit stream of address and data of Peripheral Component Interconnect (“PCI”) bus transaction, the integrated interface controller and bridge unit directly coupled to the central processing unit without any intervening PCI bus, and a mass storage device coupled to the central processing unit,
wherein the computer module is configured to receive power from the power supply, and the computer module is configured to communicate, through Ethernet, to a local area network upon coupling of the computer module to the console.

49. The computer system of claim 48, wherein the computer module is configured for insertion into the console as a “plug and play” operation.

50. The computer system of claim 48, wherein the mass storage device is a first mass storage device, and the console further comprises a second mass storage device coupled to the computer module and configured to receive power from the power supply.

51. The computer system of claim 48, wherein the central processing unit is configured to operate on a varying clock frequency to vary a power consumption of the central processing unit while in operation.

52. A computer system comprising:

a console comprising a power supply; and
a computer module coupled to the console, the computer module comprising a central processing unit to operate on a varying clock frequency to vary a power consumption of the central processing unit while in operation, a low voltage differential signal channel comprising two sets of unidirectional, multiple serial bit channels to transmit data in opposite directions, a peripheral bridge comprising an interface controller coupled to the low voltage differential signal channel to communicate an encoded serial bit stream of Peripheral Component Interconnect (“PCI”) bus transaction, the interface controller coupled to the central processing unit without any intervening PCI bus, and a graphics controller coupled to the central processing unit,
wherein the computer module is configured to receive power from the power supply.

53. The computer system of claim 52, wherein the computer module further comprises a core computing environment for a user.

54. The computer system of claim 52, wherein the computer module is configured for insertion into the console as a “plug and play” operation.

55. A computer system for secured information transaction, the computer system comprising:

a console to connect to a network;
a keyboard coupled to the console; and
a computer module coupled to the console, the computer module comprising a central processing unit, a low voltage differential signal channel comprising two sets of unidirectional, multiple serial bit channels to transmit data in opposite directions, a peripheral bridge comprising an interface controller coupled to the low voltage differential signal channel to communicate an encoded serial bit stream of Peripheral Component Interconnect (“PCI”) bus transaction, the interface controller coupled to the central processing unit without any intervening PCI bus, and a mass storage unit storing a security program and a first user identification data,
wherein the security program is configured to receive a second user identification data via the keyboard, perform a comparison of the first user identification data and the second user identification data, and permit access to the computer module based on the comparison.

56. The computer system of claim 55, wherein the security program is further configured to identify a predetermined security status and control a level of access privilege to the computer module.

57. The computer system of claim 55, wherein the central processing unit is configured to operate on a varying clock frequency to vary a power consumption of the central processing unit while in operation.

58. An information system comprising:

a console comprising a power supply and a first low voltage differential signal channel comprising two sets of unidirectional, serial bit channels to transmit data in opposite directions; and
a computer module coupled to the console, the computer module comprising a central processing unit comprising an integrated interface controller, a mass storage device coupled to the central processing unit, a graphics controller coupled to the central processing unit, and a second low voltage differential signal channel extending directly from the central processing unit, the second low voltage differential signal channel comprising two sets of unidirectional, serial bit channels to transmit data in opposite directions,
wherein the interface controller is coupled to the console through the second low voltage differential signal channel,
wherein the computer module is configured to receive power from the power supply.

59. The information system of claim 58, wherein the first low voltage differential signal channel is coupled to the second low voltage differential signal channel for data communication upon coupling of the computer module to the console.

60. The information system of claim 58, wherein the computer module is configured for insertion into the console as a “plug and play” operation.

61. The system of claim 14, wherein the encoded serial bit stream comprises 10 bit packets.

62. The system of claim 61, wherein the first interface controller is configured to output encoded PCI address and data bits in serial form that are conveyed over the first low voltage differential signal channel.

63. The system of claim 14, wherein the second interface controller is integrated with the peripheral bridge as a single integrated unit.

64. The system of claim 17, wherein the encoded serial bit stream of PCI bus transaction comprises information to permit decoding to create a PCI bus transaction across the first low voltage differential signal channel.

65. The system of claim 17, wherein the mass storage device is coupled to the central processing unit through the peripheral bridge.

66. The system of claim 20, wherein the central processing unit and the interface controller are integrated in a single chip.

67. The system of claim 66, wherein the central processing unit comprises a graphics subsystem integrated in the single chip.

68. The system of claim 24, wherein the encoded serial bit stream comprises encoded PCI address and data bits in serial form that are conveyed over the first low voltage differential signal channel as 10 bit packets.

69. The system of claim 24, wherein the integrated interface controller is configured to output a serial bit stream that is conveyed over the second low voltage differential signal channel as data packets.

70. The system of claim 69, wherein the serial bit stream comprises information of Universal Serial Bus protocol.

71. The system of claim 30, wherein the peripheral bridge is configured to output the serial bit stream that is conveyed over the second low voltage differential signal channel as data packets.

72. The system of claim 71, wherein the serial bit stream comprises information of Universal Serial Bus protocol.

73. The system of claim 31, wherein the interface controller is integrated with the peripheral bridge as a single integrated unit.

74. The system of claim 73, wherein the interface controller is configured to output a serial bit stream that is conveyed over the second low voltage differential signal channel as 10 bit packets.

75. The system of claim 34, wherein the integrated interface controller and central processing unit comprises a graphics subsystem integrated in the single chip.

76. The system of claim 34, wherein the integrated interface controller and central processing unit is configured to output a serial bit stream that is conveyed over the second low voltage differential signal channel as data packets.

77. The system of claim 76, wherein the serial bit stream comprises information of Universal Serial Bus protocol.

78. The method of claim 37, further comprising conveying, over the low voltage differential signal channel, the encoded serial bit stream as 10 bit packets.

79. The method of claim 78, wherein conveying the encoded serial bit stream comprises conveying information to permit decoding to create a PCI bus transaction across the low voltage differential signal channel.

80. The computer system of claim 40, wherein the interface controller is integrated with the peripheral bridge as a single integrated unit.

81. The computer system of claim 80, wherein the serial bit stream is conveyed over the second low voltage differential signal channel as 10 bit packets.

82. The computer system of claim 80, wherein the serial bit stream comprises information of Universal Serial Bus protocol.

83. The system of claim 44, wherein the encoded serial bit stream comprises 10 bit packets.

84. The system of claim 83, wherein the interface controller is configured to output the encoded serial bit stream that is conveyed over the low voltage differential signal channel.

85. The computer system of claim 48, wherein the integrated interface controller and bridge unit is configured as a single integrated unit.

86. The computer system of claim 85, wherein the integrated interface controller and bridge unit is configured to output the encoded serial bit stream as 10 bit packets that are conveyed over the low voltage differential signal channel.

87. The computer system of claim 52, wherein the peripheral bridge is directly coupled to the central processing unit without any intervening PCI bus.

88. The computer system of claim 87, wherein the interface controller is configured to output the encoded serial bit stream as 10 bit packets that are conveyed over the low voltage differential signal channel.

89. The computer system of claim 88, wherein the encoded serial bit stream comprises information to permit decoding to create a PCI bus transaction across the low voltage differential signal channel.

90. The computer system of claim 55, wherein the peripheral bridge is directly coupled to the central processing unit without any intervening PCI bus.

91. The computer system of claim 90, wherein the interface controller is integrated with the peripheral bridge as a single integrated unit.

92. The computer system of claim 91, wherein the encoded serial bit stream comprises encoded PCI address and data bits in serial form.

93. The information system of claim 58, wherein the integrated interface controller is configured to output a serial bit stream that is conveyed over the second low voltage differential signal channel.

94. The information system of claim 93, wherein the serial bit stream is conveyed over the second low voltage differential signal channel as 10 bit packets.

95. The information system of claim 93, wherein the serial bit stream comprises information of Universal Serial Bus protocol.

Referenced Cited
U.S. Patent Documents
3996585 December 7, 1976 Hogan
4141068 February 20, 1979 Mager et al.
4228496 October 14, 1980 Katzman et al.
4453215 June 5, 1984 Reid
4623964 November 18, 1986 Getz et al.
4670837 June 2, 1987 Sheets
4680674 July 14, 1987 Moore
4700362 October 13, 1987 Todd et al.
4760276 July 26, 1988 Lethellier
4769764 September 6, 1988 Levanon
4791524 December 13, 1988 Teigen et al.
4799258 January 17, 1989 Davies
4872091 October 3, 1989 Maniwa et al.
4890282 December 26, 1989 Lambert et al.
4918572 April 17, 1990 Tarver et al.
4939735 July 3, 1990 Fredericks et al.
5056141 October 8, 1991 Dyke
5086499 February 4, 1992 Mutone
5103446 April 7, 1992 Fischer
5187645 February 16, 1993 Spalding et al.
5191581 March 2, 1993 Woodbury et al.
5251097 October 5, 1993 Simmons et al.
5278509 January 11, 1994 Haynes et al.
5278730 January 11, 1994 Kikinis
5282247 January 25, 1994 McLean et al.
5293487 March 8, 1994 Russo et al.
5293497 March 8, 1994 Free
5311397 May 10, 1994 Harshberger et al.
5317441 May 31, 1994 Sidman
5317477 May 31, 1994 Gillett
5319771 June 7, 1994 Takeda
5325517 June 28, 1994 Baker et al.
5331509 July 19, 1994 Kikinis
5339408 August 16, 1994 Bruckert et al.
5355391 October 11, 1994 Horowitz et al.
5428806 June 27, 1995 Pocrass
5430607 July 4, 1995 Smith
5432939 July 11, 1995 Blackledge, Jr. et al.
5436857 July 25, 1995 Nelson et al.
5436902 July 25, 1995 McNamara et al.
5463742 October 31, 1995 Kobayashi
5519843 May 21, 1996 Moran et al.
5533125 July 2, 1996 Bensimon et al.
5537544 July 16, 1996 Morisawa et al.
5539616 July 23, 1996 Kikinis
5546463 August 13, 1996 Caputo et al.
5550710 August 27, 1996 Rahamim et al.
5550861 August 27, 1996 Chan et al.
5552776 September 3, 1996 Wade et al.
5572441 November 5, 1996 Boie
5577205 November 19, 1996 Hwang et al.
5578940 November 26, 1996 Dillon
5588850 December 31, 1996 Pan et al.
5590377 December 31, 1996 Smith
5600800 February 4, 1997 Kikinis et al.
5603044 February 11, 1997 Annapareddy et al.
5606717 February 25, 1997 Farmwald et al.
5608608 March 4, 1997 Flint et al.
5623637 April 22, 1997 Jones et al.
5630057 May 13, 1997 Hait
5638521 June 10, 1997 Buchala et al.
5640302 June 17, 1997 Kikinis
5648762 July 15, 1997 Ichimura et al.
5659773 August 19, 1997 Huynh et al.
5663661 September 2, 1997 Dillon et al.
5673172 September 30, 1997 Hastings et al.
5673174 September 30, 1997 Hamirani
5680126 October 21, 1997 Kikinis
5680536 October 21, 1997 Tyuluman
5689654 November 18, 1997 Kikinis
5708840 January 13, 1998 Kikinis et al.
5721837 February 24, 1998 Kikinis
5721842 February 24, 1998 Beasley et al.
5724591 March 3, 1998 Hara et al.
5737194 April 7, 1998 Hopkins et al.
5737524 April 7, 1998 Cohen et al.
5745733 April 28, 1998 Robinson
5751711 May 12, 1998 Sakaue
5752080 May 12, 1998 Ryan
5764924 June 9, 1998 Hong
5774703 June 30, 1998 Weiss et al.
5774704 June 30, 1998 Williams
5795228 August 18, 1998 Trumbull
5802391 September 1, 1998 Hwang
5805903 September 8, 1998 Elkhoury
5809262 September 15, 1998 Potter
5809538 September 15, 1998 Pollmann
5815681 September 29, 1998 Kikinis
5819050 October 6, 1998 Boehling et al.
5826048 October 20, 1998 Dempsey et al.
5838932 November 17, 1998 Alzien
5848249 December 8, 1998 Garbus
5859669 January 12, 1999 Prentice
5862350 January 19, 1999 Coulson
5862381 January 19, 1999 Advani et al.
5878211 March 2, 1999 Delagrange et al.
5884049 March 16, 1999 Atkinson
5884053 March 16, 1999 Clouser
5907566 May 25, 1999 Benson et al.
5930110 July 27, 1999 Nishigaki et al.
5933609 August 3, 1999 Walker et al.
5941965 August 24, 1999 Moroz
5948047 September 7, 1999 Jenkins et al.
5960213 September 28, 1999 Wilson
5965957 October 12, 1999 Bourgeois
5968144 October 19, 1999 Walker et al.
5971804 October 26, 1999 Gallagher et al.
5974486 October 26, 1999 Siddappa
5977989 November 2, 1999 Lee et al.
5978821 November 2, 1999 Freeny
5978919 November 2, 1999 Doi et al.
5982363 November 9, 1999 Naift
5982614 November 9, 1999 Reid
5991163 November 23, 1999 Marconi et al.
5991844 November 23, 1999 Khosrowpour
5999952 December 7, 1999 Jenkins et al.
6002442 December 14, 1999 Li et al.
6003105 December 14, 1999 Vicard
6006243 December 21, 1999 Karidis
6009488 December 28, 1999 Kavipurapu
6011546 January 4, 2000 Bertram
6012145 January 4, 2000 Mathers
6016252 January 18, 2000 Pignolet et al.
6025989 February 15, 2000 Ayd et al.
6028643 February 22, 2000 Jordan et al.
6029183 February 22, 2000 Jenkins et al.
6038621 March 14, 2000 Gale et al.
6040792 March 21, 2000 Watson et al.
6046571 April 4, 2000 Bovio et al.
6049823 April 11, 2000 Hwang
6052513 April 18, 2000 MacLaren
6069615 May 30, 2000 Abraham et al.
6070211 May 30, 2000 Neal
6070214 May 30, 2000 Ahern
6078503 June 20, 2000 Gallagher et al.
6088224 July 11, 2000 Gallagher et al.
6088620 July 11, 2000 Ninomiya et al.
6088752 July 11, 2000 Ahern
6091737 July 18, 2000 Hong et al.
6104921 August 15, 2000 Cosley et al.
6145085 November 7, 2000 Tran et al.
6157534 December 5, 2000 Gallagher et al.
6161524 December 19, 2000 Akbarian et al.
6163464 December 19, 2000 Ishibashi et al.
6175490 January 16, 2001 Papa et al.
6188602 February 13, 2001 Alexander et al.
6202169 March 13, 2001 Razzaghe-Ashrafi et al.
6208522 March 27, 2001 Manweiler et al.
6216185 April 10, 2001 Chu
6256689 July 3, 2001 Khosrowpour
6256691 July 3, 2001 Moroz et al.
6260155 July 10, 2001 Dellacona
6266539 July 24, 2001 Pardo
6289376 September 11, 2001 Taylor et al.
6297955 October 2, 2001 Frank, Jr. et al.
6301637 October 9, 2001 Krull et al.
6304895 October 16, 2001 Schneider et al.
6311268 October 30, 2001 Chu
6311287 October 30, 2001 Dischler et al.
6314522 November 6, 2001 Chu et al.
6317329 November 13, 2001 Dowdy et al.
6321335 November 20, 2001 Chu
6324605 November 27, 2001 Rafferty et al.
6325636 December 4, 2001 Hipp et al.
6332180 December 18, 2001 Kauffman et al.
6345330 February 5, 2002 Chu
6366951 April 2, 2002 Schmidt
6378009 April 23, 2002 Pinkston, II et al.
6381602 April 30, 2002 Shoroff et al.
6393561 May 21, 2002 Hagiwara et al.
6401124 June 4, 2002 Yang et al.
6411506 June 25, 2002 Hipp et al.
6425033 July 23, 2002 Conway
6452789 September 17, 2002 Pallotti et al.
6452790 September 17, 2002 Chu et al.
6453344 September 17, 2002 Ellsworth et al.
6496361 December 17, 2002 Kim et al.
6498361 December 24, 2002 Osann, Jr.
6549966 April 15, 2003 Dickens et al.
6564274 May 13, 2003 Heath et al.
6567877 May 20, 2003 Lewis et al.
6578103 June 10, 2003 Hill
6581125 June 17, 2003 Lange
6606253 August 12, 2003 Jackson et al.
6643777 November 4, 2003 Chu
6664377 December 16, 2003 Xu
6715100 March 30, 2004 Hwang
6718415 April 6, 2004 Chu
6725317 April 20, 2004 Bouchier et al.
6742068 May 25, 2004 Gallagher et al.
6747878 June 8, 2004 Hip et al.
6757748 June 29, 2004 Hipp
6948047 September 20, 2005 Maruska et al.
6985967 January 10, 2006 Hipp
7017001 March 21, 2006 Hill et al.
7020735 March 28, 2006 Kikinis
7099981 August 29, 2006 Chu
7146446 December 5, 2006 Chu
7328297 February 5, 2008 Chu
7339786 March 4, 2008 Bottom et al.
7363415 April 22, 2008 Chu
7363416 April 22, 2008 Chu
7376779 May 20, 2008 Chu
RE41076 January 12, 2010 Chu
RE41092 January 26, 2010 Chu
7676624 March 9, 2010 Chu
RE41294 April 27, 2010 Chu
7818487 October 19, 2010 Chu
RE41961 November 23, 2010 Chu
20010011312 August 2, 2001 Chu
20050182882 August 18, 2005 Chu
20090157939 June 18, 2009 Chu
20100174844 July 8, 2010 Chu
Foreign Patent Documents
722138 July 1996 EP
6-289953 October 1994 JP
6-289956 October 1994 JP
7-64672 March 1995 JP
7-84675 March 1995 JP
WO 92/18924 October 1992 WO
WO 94/00097 January 1994 WO
WO 94/00970 January 1994 WO
WO 95/13640 May 1995 WO
W09700481 January 1997 WO
WO 97/005618 February 1997 WO
Other references
  • Agerwala, T. et al., “SP2 System Architecture”, IBM Systems Journal, vol. 34, No. 2 (1995).
  • Bernal, Carlos, product brochure entitled: “PowerSMP Series 4000”, (Mar. 1998) <<http://www/winnetmag.com/Windows/Article/ArticleID/3095//3095.html, downloaded from web on Jun. 22, 2004, 2 pgs.
  • Cragle, Jonathan, “Density System 1100”, (May 1999) <<http://www.winnetmag.com/Windows/Article/ArtideID/5199/5199.html>>, downloaded from web on Jun. 21, 2004, 3 pgs.
  • Feldman, Jonathan, “Rack Steady: The Four Rack-Mounted Servers That Rocked Our Network”, <<http://www.networkcomputing.com/shared/printArtide.jhtml?article=/910/910r3sidel.htm...>> Jun. 23, 2004, 3 pgs.
  • Fetters, Dave, “Cubix High-Density Server Leads the Way With Standout Management Software”, (Feb. 8, 1999) <<http://www.—nwc.—com/shared/printArticle.jhtml?article=/1003/1003r3full.html&pub=nwc>>, downloaded from web on Jun. 23, 2004, 5 pgs.
  • Gardner, Michael and Null, Christopher, “A Server Condominium”, <<http://www.lantimes.com/testing/98jun/806a042a.html>>, Jun. 23, 2004, 3 pgs.
  • Harrison, Dave, “VME in the Military: The M1A2 Main Battle Tank Upgrade Relies on COTS VME” <<http://www.dy4.com>>, (Feb. 9, 1998), pp. 1-34.
  • Williams, Dennis, “Consolidated Servers”, (Feb. 17, 1997) <<http://www.lantimes.com/testing/97compare/pcconsol.html>> downloaded from web on Jun. 23, 2004, 2 pgs.
  • Williams, Dennis, “Executive Summary: Consolidate Now”, (Feb. 17, 1997) <<http://www.lantimes.com/testing/97feb/702b064a.html>> downloaded from web on Jun. 23, 2004, 2 pgs.
  • Williams, Dennis, “Top ″Scores for Useability and Openness”, (Feb. 17, 1997) <<http://www.lantimes.com/testing/97feb/702b064a.html>> downloaded from web on Jun. 23, 2004, 2 pgs.
  • Williams, Dennis, “ChatCom Inc. Chatterbox”, (Feb. 17, 1997) <<http://www.lantimes.com/testing/97feb/702b066a.html>> downloaded from web on Jun. 23, 2004, 3 pgs.
  • Williams, Dennis, “EVERSYS Corp. System 8000”, (Feb. 17, 1997) <<http://www.lantimes.com/testing/97feb/702b070b.html>> downloaded from web on Jun. 22, 2004, 4 pgs.
  • Williams, Dennis, “Cubix Corp. ERS/FT II”, (Feb. 17, 1997) <<http://www.lantimes.com/testing/97feb/702b068b.html>> downloaded from web on Jun. 23, 2004, 4 pgs.
  • Crystal Group, “Rackmount Computers”, (©2000-2004) <<http://www.crystalpc.com/products/roservers.asp>>, downloaded from web on Jun. 17, 2004, 8 pgs.
  • Crystal Group, “QuickConnect® Cable Management”, (© 2000-2004) <<http://www.crystalpc.com/products/quickconnect.asp>> downloaded from web on Jute 17, 2004, 4 pgs.
  • Cubix Product Brochure entitled, “Density System”, (© 2000) <<http://64.173.211.7/support/techinfo/system/density/density10.htm>> downloaded from web on Jun. 22, 2004, 3 pgs.
  • Cubix Product Brochure entitled, “Density System, Technical Specifications”, (© 2000) <<http://64.173.211.7/support/techinfo/system/density/info/spec.htm>> downloaded from web on Jun. 22, 2004, 2 pgs.
  • Cubix Product Manual entitled, “Density System”, Chapter 1—Introduction, (© 2000) <<http://64.173.211.7/support/techinfo/manuals/density/Chap-1.htm>> downloaded from web on Jun. 22, 2004, 5 pgs.
  • Cubix, “Click on the front panel that matches your system”, (© 2000) <<http://64.173.211.7/support/techinfo/system/density/density.htm>>, downloaded from web on Jun. 22, 2004, 1 pg.
  • Cubix Product Manual entitled, “Density System”, Chapter 2—Installation, (© 2000) <<http://64.173.211.7/support/techinfo/manuals/density/Chap-2.htm>> downloaded from web on Jun. 22, 2004, 9 pgs.
  • Cubix Product Manual entitled, “Density System”, Chapter 3—Operation, (© 2000) <<http:://64.173.211.7/support/techinfo/manuals/density/Chap-3.htm>> downloaded from web on Jun. 22, 2004, 4 pgs.
  • Cubix Product Manual entitled, “Density System”, Chapter 4—Maintenance and Repair, (© 2000) <<http://64.173.211.7/support/techinfo/manuals/density/Chap-4.htm>> downloaded from web on Jun. 22, 2004, 5 pgs.
  • Cubix, “What are Groups?”, (© 2000) <<http://64.173.211.7/support/techinfo/system/density/info/groups.htm>>, downloaded from web on Jun. 22, 2004, 3 pgs.
  • Cubix, “SP 5200XS Series Plug-in Computers”, (© 2000) <<http://64.173.211.7/support/techinfo/bc/sp5200xs/intro.htm>>, downloaded from web on Jun. 22, 2004, 2 pgs.
  • Cubix, “SP 5200XS Series Technical Specifications”, (© 2000) <<http://64.173.211.7/support/techinfo/bc/sp5200xs/spec.htm>>, downloaded from web on Jun. 22, 2004, 2 pgs.
  • Cubix, “SP 5200 Series” Chapter 1—Introduction, (© 2000) <<http://64.173.211.7/support/techinfo/manuals/sp5200/chap-1.htm>>, downloaded from web on Jun. 22, 2004, 3 pgs.
  • Cubix, “SP 5200 Series” Chapter 2—Switches & Jumpers, (© 2000) <<http://64.173.211.7/support/techinfo/manuals/sp5200/chap-2.htm>>, downloaded from web on Jun. 22, 2004, 3 pgs.
  • Cubix, “SP 5200 Series” Chapter 3—Installation, (© 2000) <<http://64.173.211.7/support/techinfo/manuals/sp5200/chap-3.htm>>, downloaded from web on Jun. 22, 2004, 4 pgs.
  • Cubix, “SP 5200 Series” Chapter 4—Technical Reference, (© 2000) <<http://64.173.211.7/support/techinfo/manuals/sp5200/chap-4.htm>>, downloaded from web on Jun. 22, 2004, 3 pgs.
  • Cubix, “DP 6200 ‘D’ Series Plug-in Computers” <<http://64.173.211.7/support/techinfo/bc/dp/6200d/intro.htm >>, downloaded from web on Jun. 22, 2004, 3 pgs.
  • Cubix, “Installing DP or SP Series Boards” (© 2000) <<http://64.173.211.7/support/techinfo/bc/dp/6200d/intro.htm>>, downloaded from web on Jun. 22, 2004, 2 pgs.
  • Cubix, “Powering On/Off or Resetting Plug-in Computers in an Density System”, (® 2000) <<http://64.173.211.7/support/techinfo/system/density/info/power.htm>>, downloaded from web on Jun. 22, 2004, 2 pgs.
  • Cubix, “Multiplexing Video, Keyboard & Mouse with Multiple Density Systems”, (© 2000) <<http://64.173.211.7/support/techinfo/system/density/'info/vkm-mux.htm>>, downloaded from web on Jun. 22, 2004, 2 pgs.
  • eBay Advertisement for “Total IT Group Network Engines”, <<http://cgi.ebay.com/we/eBayISAP1.dll?ViewItem&item=5706388046&sspagename+STRK%3AMDB1%3AMEB13AIT&rd=1>>, downloaded from web on Jun. 25, 2004, 1 pg.
  • “Features Chart”, (Feb. 1, 1997) <<http://www.lantimes.com/testing/97feb/702b072a.html>>, downloaded from web on Jun. 23, 2004, 3 pgs.
  • Internet Telephony Roundup, “Industrial Computers” <<http://www.tmcnet.com/articles/itmag/0499/0499roundup.htm>>, downloaded from web on Jun. 23, 2004, pp. 1-5.
  • Press Release: “Crystal Group Products Offer Industrial PCs with Built-in Flexibility”, Hiawatha, Iowa, (Mar. 1, 1997) <<http://www.crystalpc.com/news/pressreleases/prodpr.asp>>, downloaded from web on May 14, 2004, 2 pgs.
  • Press Release: “Enhanced COTS SBC from DY 4 Systems features 166MHz Pentium™ Processor” Kanata, Ontario, Canada, (Apr. 1998) <<http://www.realtime-info.be/ VPR/layout/display/pr.asp?/pr.asp?PRID=363>>, 2 pgs.
  • DY 4 Systems, Inc., SVME/DM-192 Pentium™ Single Board Computer (Jun. 1999) pp. 1-9.
  • Bomara Associates, “System 8000”, <<http://www.bomara.com/Eversys/briefDefault.htm>>, downloaded from web on Jun. 22, 2004, 4 pgs.
  • Cubix, “ERS/FT II System”, (© 2000) <<http://64.173.211.7/support/techinfo/system/ersft2/ersft2.htm>>, downloaded from web on Jun. 22, 2004, 4 pgs.
  • Cubix, “ERS II and ERS/ FT II”, Chap. 3, System Components, <<http://64.173.211.7/support/techinfo/manuals/ers2/ers2-c3.htm>>, downloaded from web on Jun. 22, 2004, 21 pgs.
  • Product Manual entitled: “ERS II and ERS/FT II”, Chap. 6, Component Installation, <<http://64.173.211.7/support/techinfo/manuals/ers2/ers2-c6.htm>>, downloaded from web on Jun. 22, 2004, 18 pgs.
  • Windows Magazine, “Cubix PowerSMP Series 4000”, Nov. 1997, <http://<www.techweb.com/winmag/library/1997/1101/ntent008.htm>> downloaded from the web on Jun. 22, 2004, p. NT07.
  • CETIA Brochure “CETIA Powerengine CVME 603e” pp. 1-6 downloaded from the internet @ http://www.cetia.com/Products—Addons/wp-47-01.pdf on Feb. 15, 2006.
  • MPL Brochure,“The First Rugged AI in One Industrial 486FDX-133 Mhz PC”, (1998), pp. 53.
  • MPL Brochure “IPM 486 Brochure/IPM5 User Manual”, pp. 1-9, downloaded from the internet @ http://www.mplch/DOCS./u48600xd.pdf on Feb. 15, 2006.
  • Snyder, Joel, “Better Management Through Consolidation,” pp. 1-6 http://www.opus1.com/www/jms/nw-con-0818rev.html. (Aug. 18, 1997).
  • Eversys Corporation, “Eversys System 8000 Consolidated Network Server Market and Product Overview,” Slide presentation, downloaded from <http://eversys.com>, product to be released Mar. 1, 1997, 20 pages (no date on document).
  • “SQL Server and NT Cluster Manager Availability Demo, ”Microsoft Server Programmer Developers Conference, Nov. 1996, 15 pages.
  • HP: HDMP-1636, Gigabit Ethernet Transceiver Chip, Preliminary Technical Data (May 1997) (No. 123.pdf).
  • ACCTON, Gigabit Ethernet PCI Adapter (1999) (2 pp) (No. 122.pdf).
  • Intel, 82559 Fax Ethernet Multifunction PCI/Cardbus Controller (Jan. 1999) (56 pp.) (No. 128.pdf).
  • Intel, 21143 PCI/CardBus 10/100Mb/s Ethernet LAN Controller, Product Datasheet (Oct. 1998) (8 pp.) (No. 127.pdf).
  • KTI Networks, Installation Guide 10/100 Dual-speed Fast Ethernet PCI Adapters (1999) (24 pp.) (No. 126.pdf).
  • Micronet SP2500R Series Etherfast 10/100 MBPS Adapter, User's Guide (1999) (10 pp.) (No. 136.pdf).
  • PCI Local Bus Specification (Rev. 2.2, Dec. 1998) (322 pp.) (No. 135.pdf).
  • EIA-422A—Standard (Superseded), Electrical Characteristics of Balanced Voltage Digital Interface Circuits (Dec. 1978) (20 pp) (No. 118a.pdf).
  • TIA/EIA (644) Standard Electrical Characteristics of Low Voltage Differential Signaling (LVDS) Interface Circuits (Mar. 1996) (42 pp) (No. 118c.pdf).
  • Huq et al. “An Overview of LVDS Technology” National Semiconductor Corp. (Jul. 1998) (6 pp.) (No. 118d.pdf).
  • Ziatech Corporation-Ketris9000 Product Manual (2000) (159 pp.) (No. 18.pdf).
  • Ziatech Corp. ZT 8907 Product Description (1998) (4 pp) (No. 19b.pdf).
  • Ziatech Corp. ZT 8908 Product Description (1998)+A249 (6 pp) (No. 19c.pdf).
  • Ziatech Corp. System Designer's Guide: Hot Swap Capability on STD 32 Computers (Jan. 1996) (6 pp) (No. 19e.pdf).
  • Ziatech Corp. Press Release (Feb. 1996) (2 pp) (No. 19i.pdf).
  • Ziatech Corp. Industrial BIOS for CompacktPCI and STD 32 Systems Software Manual (Jul. 1998) (134 pp) No. 19h.pdf).
  • Ziatech Corp.System Designers Guide: Expanding STD Bus Performance Through Multiprocessing. (Apr. 1996) (6 pp.) (No. 19d.pdf).
  • Ziatech, STD 32 Star System Product Description(6 pp) (No. 19a.pdf).
  • Network Engines: P6000EXP Fault-Tolerant Load-Balanced Cluster Server (NEI00095) (1997) (4 pp.) (No. 22a.pdf).
  • Whitecross Data Exploration Configuration and Maintenance Manual. Draft. (Jul. 2000) (699 pp.) (No. 26e.pdf).
  • Whitecross WX-DES Hardware Maintenance (2000) (284 pp) (No. 26g.pdf).
  • Whitecross WX-DES Technical Overview (2000) (211 pp) (No. 26h.pdf).
  • Microsoft Cluster Service Center, MSCS Basics, downloaded from <<http://www.networks.com/mscsbasics.htm. Feb. 7, 2005, 6 pages.
  • PC Magazine, “Think Modular” (Jun. 10, 1997).
  • Liquorman, “Convergent Technologies Had This Idea” (Dec. 5, 1997).
  • Berst, “Hope For The Modular PCs We all Really Want” (Dec. 5, 1997).
  • Boyd-Merritt, “Upgradable-PC Effort Takes Divergent Paths” (EE Times 1997) http://techweb.cmp/com/eet/news/97/949news/effort.html.
  • Faegre, et al., “Unisys' Best-Kept Secret Is An Operating System Built For Distributed Business Applications.” BYTE (Dec. 1994).
  • Spang, “Component House: Design Technology For ‘PCs in a snap’—NeoSystems Offers Building Blocks” Techweb (Apr. 21, 1997:732).
  • 8260 ATM Product Architecture, IBM International Technical Support Organization, Raleigh Center, Sep. 1997, First Edition, International Business Machines Corporation, 220 pages.
  • 8265 Nways ATM Switch, Product Description, Sep. 1998, Fifth Edition, International Business Machines Corporation, 141 pages.
  • Origin2000 Rackmount Owner's Guide, Document No. 007-3456-003, 1997, Silicon Graphics, Inc., 146 pages.
  • QuantumNet, Inc., QuantumNet Product Overview [online], 1996 [retrieved on Nov. 16, 2009], Retrieved from the Internet: <URL: http://web.archive.org/web/19971011194003/www.quantumnet.com/products.htm>, 1 page.
  • QuantumNet, Inc., QuantumNet: The Next Generation Computing and Networking Environment [online], 1996 [retrieved on Nov. 16, 2009], Retrieved from the Internet: <URL: http://web.archive.org/web/19971011194123/www.quantumnet.com/qnetovw.htm>, 7 pages.
  • QuantumNet, Inc., QuantumNet 6500 Processor Modules [online], 1996 [retrieved on Nov. 16, 2009], Retrieved from the Internet: <URL:http://web.archive.org/web/19971011194317/www.quantumnet.com/ds6500.htm>, 4 pages.
  • QuantumNet, Inc., QuantumServer Chassis [online], 1996 [retrieved on Nov. 16, 2009], Retrieved from the Internet: <URL: http://web.archive.org/web/19971011194309/www.quantumnet.com/dsq6000.htm>, 3 pages.
  • Cubix Corporation, White Paper: Benefits of High-Density Servers [online], 1997 [retrieved on Jul. 31, 2009], Retrieved from the Internet: <URL: http://web.archive.org/web/19970716204215/www.cubix.com/corporate/whitep/densit.htm>, 6 pages.
  • Cubix Corporation, Datasheet: Single-Board Computers with Pentium Processors [online], 1997 [retrieved on Jul. 31, 2009], Retrieved from the Internet: <URL: http://web.archive.org/web/19970716204717/www.cubix.com/corporate/data/bcp5t.htm>, 5 pages.
  • Cubix Corporation, Datasheet: ERS/FT II Server Chassis [online], 1997 [retrieved on Jul. 31, 2009], Retrieved from the Internet: <URL: http://web.archive.org/web/19970716204623/www.cubix.com/corporate/data/ersft2.htm>, 3 pages.
  • Cubix Corporation, Cubix ERS/FT II Systems [online], 1997 [retrieved on Jul. 31, 2009], Retrieved from the Internet: <URL: http://web.archive.org/web/19980124213320/www.cubix.com/support/steps/ers-ft2/intro.htm>, 5 pages.
  • Cubix Corporation, Cubix Product Catalog, Summer 1995, 56 pages.
  • Cubix Corporation, BC Series, Processor Boards Installation Guide, DOC 800A, Aug. 1994, 149 pages.
  • Cubix Corporation, ERS/FT II—Enhanced Resource Subsystem/Fault Tolerant II, Nov. 1994, 4 pages.
  • Cubix Corporation, Density Series Plug-In Servers, Plug-In Computers for Managed Server Farms, Sep. 15, 1998, 2 pages.
  • Cubix Corporation, Cubix Pentium II Plug-In Computers for Density Series Systems, Sep. 15, 1998, 1 page.
  • Cubix Corporation, Density Series Multi-Server Systems, Sep. 10, 1999, 4 pages.
  • Compaq Computer Corporation, White Paper, “Order and Configuration Guide for Compaq ProLiant Cluster Series F Model 100,” Sep. 1998, pp. 1-8.
  • Compaq Computer Corporation, Compaq Performance Brief, ProLiant 1600 ServerBench Performance Summary, Aug. 1998, pp. 1-7.
  • Compaq Computer Corporation, Compaq ActiveAnswers Installation Guide, Installation and Configuration Guide for Linux and Apache Web Server on Compaq Prosignia and ProLiant Servers, May 1999, pp. 1-40.
  • Compaq Computer Corporation, Compaq White Paper, “Microsoft Internet Information Server 4.0 on the Compaq ProLiant 6500,” Aug. 1998, pp. 1-14.
  • Compaq Computer Corporation, Compaq White Paper, “Accelerating Financial Spreadsheet Simulations with Workstation Clusters,” Oct. 1998, pp. 1-14.
  • Compaq Computer Corporation, ProLiant 6500-PDC/O1000 C/S with 4 ProLiant 1850R, TPC-C Rev. 3.4, Report Date: Dec. 22, 1998, pp. 1-3.
  • Black Box Corporation, Black Box Network Services, Black Box ServSwitch Duo, Jul. 1998, 52 pages.
  • Compaq Computer Corporation, Compaq White Paper, “ServerNet—A High Bandwith, Low Latency Cluster Interconnection,” Sep. 1998, pp. 1-9.
  • JL ChatCom, Inc.—Web Site, JL ChatCom, Inc., ChatterBox Communications and Server Solutions [online], 1996 [retrieved on Dec. 2, 2009], Retrieved from the Internet: <URL: http://web.archive.org/web/19970104221841/http://www.jlchatcom.com/>, 1 page.
  • JL ChatCom, Inc.—Scaleable Application and Communication Servers, “ChatCom, Inc. Announces Complete Line of Scaleable Application and Communication Servers,”Aug. 30, 1996 [retrieved on Dec. 2, 2009], JL ChatCom, Inc., ChatterBox Communications and Server Solutions [online], Retrieved from the Internet: <URL: http://web.archive.org/web/19970104221932/www.jlchatcom.com/cpofrel.htm>, 4 pages.
  • JL ChatCom, Inc.—Highly Adaptable Intranet and Web Servers, “ChatCom, Inc. Announces Highly Adaptable Intranet and Web Servers,” Sep. 3, 1996 [retrieved on Dec. 2, 2009], JL ChatCom, Inc., ChatterBox Communications and Server Solutions [online], Retrieved from the Internet: <URL: http://web.archive.org/web/19970104221941/www.jlchatcom.com/chat4int.htm>, 2 pages.
  • JL ChatCom, Inc., “ChatPower Plus,” 1996 [retrieved on Dec. 2, 2009], JL ChatCom, Inc., ChatterBox Communications and Server Solutions [online], Retrieved from the Internet: <URL: http://web.archive.org/web/19970104222122/www.jlchatcom.com/chatplus.htm>, 3 pages.
  • JL ChatCom, Inc., “ChatterBox ChatPower Plus,” (undated) [retrieved on Dec. 2, 2009], JL ChatCom, Inc., ChatterBox Communications and Server Solutions [online], Retrieved from the Internet: <URL: http://web.archive.org/web/19970104222556/www.jlchatcom.com/cpp1.gif>, 1 page.
  • JL ChatCom, Inc., “ChatExpress PB5 Series P166 Pentium PCI/ISA CPU Card,” 1996 [retrieved on Dec. 2, 2009], JL ChatCom, Inc., ChatterBox Communications and Server Solutions [online], Retrieved from the Internet: <URL: http://web.archive.org/web/19970104222157/www.jlchatcom.com/chatp599.htm>, 2 pages.
  • JL ChatCom, Inc., “ChatExpress—2 Slot,” [retrieved on Dec. 2, 2009], JL ChatCom, Inc., ChatterBox Communications and Server Solutions [online], Retrieved from the Internet: <URL: http://web.archive.org/web/19970104222644/www.jlchatcom.com/exp2ill.gif>, 1 page.
  • Intel Corporation, Intel 82559 Fast Ethernet Multifunction PCI/Cardbus Controller, Networking Silicon, Preview Datasheet, Jan. 1999, 56 pages.
  • Ziatech Corporation, STD 32 zVID2 Local Bus Super VGA/FPD Adapter, Apr. 1996, 2 pages.
  • Network Engines, Inc., Network Engines ClusterDirector User's Manual, Jun. 1998, 32 pages.
  • Eversys Corporation, System 8000 Consolidated Server, (undated), [retrieved on Nov. 9, 2009], Retrieved from C: drive <path: file://C:\Documents and Settings\Daniel\M Documents\Eversys\Eversys Web Site Master...>, 6 pages.
  • Eversys Corporation, System 8000 Consolidated Network Server, Pentium II Processor Module User's Guide for Module version P2D-BXT, Jan. 1998, 49 pages.
  • Eversys Corporation, Eversys System 8000 Peripheral Sharing Switch (PSS) User's Guide, 1st Edition—Jun. 1997, 2nd Edition—Jan. 1998, 17 pages.
  • Eversys Corporation, WebView 8000 version 1.1 User's Guide, Web-Based Management Software fo the Eversys System 8000 Consolidated Server, Revision A—Nov. 1998, Revision B—Dec. 1998, 56 pages.
  • Eversys Corporation, S8000 Single Module Body Assemby, Oct. 9, 1998, 9 pages.
  • Eversys CAPserver Product Brief [online], (undated), [retrieved on Nov. 16, 2009], Retrieved from the Internet: <URL: http://web.archive.org/web/19961104093115/www.eversys.com/CAPbrief.htm>, 10 pages.
  • Eversys CAPcard 9500/sa Product Brief [online], (undated), [retrieved on Nov. 16, 2009], Retrieved from the Internet: <URL: http://web.archive.org/web/19961104093144/www.eversys.com/cc95sa—Brief.htm>, 3 pages.
  • Phillips, J., “9800 Disk Card Design Specification,” May 26, 1998, White Cross Systems Limited, pp. 1-44.
  • Phillips, J., “9800 Disk Card Layout Specification,” Apr. 6, 1998, White Cross Systems Limited, pp. 1-22.
  • Feakes, L., “Disk Connector Card Functional Requirement Specification,” Jan. 14, 1998, White Cross Systems Limited, pp. 1-4.
  • Feakes, L., “Disk Connector Card Layout Specification,” Jan. 14, 1998, White Cross Systems Limited, pp. 1-6.
  • Burrow, M., WhiteCross Data Exploration, “A Technical Overview of the WXDES/9800,” Mar. 2, 1999, Revision 2.00, White Cross Systems Limited, pp. 1-90.
  • Burrow, M., WhiteCross Data Exploration, “A Technical Overview of the WXDES/9800,” Apr. 21, 1999, White Cross Systems Limited, 222 pages.
  • Khan, M. F., “Ethernet Switch Card Design Specification,” Mar. 8, 2001, White Cross Systems Limited, pp. 1-32.
  • Khan, M. F., “Ethernet Switch Card Layout Specifications,” Mar. 8, 2001, pp. 1-31.
  • Smith, B., Processor Backplane Functional Requirement Specification, Jul. 31, 1997, White Cross Systems Limited, pp. 1-11.
  • Smith, B., “Processor Backplane Design Specification,” Feb. 3, 1998, White Cross Systems Limited, pp. 1-16.
  • Smith, B., “Processor Backplane Layout Specification,” Nov. 12, 1997, White Cross Systems Limited, pp. 1-7.
  • Phillips, J., “9800 Processor Card Design Specification,” Feb. 25, 1998, White Cross Systems Limited, pp. 1-41.
  • Phillips, J., “9800 Processor Card Layout Specification,” Sep. 29, 1997, White Cross Systems Limited, pp. 1-13.
  • Miastkowski, S. (Editor), “A Whale of a System,” BYTE, Aug. 1991, 4 pages, vol. 16, No. 8.
  • Advanced Micro Devices, Inc., “AMD-K6-III Processor Data Sheet,” 21918B/0, Oct. 1999, 326 pages.
  • Black•Box Corporation, “Black Box Serve Switch Duo,” Black Box Network Services Manual, Jul. 1998, 52 pages.
  • Cisco Systems, Inc., “Cisco AS5800 Universal Access Server Dial Shelf Controller Card Installation and Replacement,” Doc. No. 78-4653-02, 1997, 28 pages.
  • Digital Equipment Corporation, “Digital AlphaServer 4000 and 4100 systems,” [Brochure], 1998, 4 pages.
  • Eversys, “CAPserver Product Brief” [online], [retrieved on Nov. 16, 2009], Retrieved from the Internet: <URL: http://web.archieve.org/web/19961104093115/www.eversys.com/CAPbrief.htm>, 10 pages.
  • Eversys, “CAPcard 9500/sa Product Brief,” [online], [retrieved on Nov. 16, 2009], Retrieved from the Internet: <URL: http://web.archieve.org/web/19961104093144/www.eversys.com/cc95sa—Brief.htm>, 3 pages.
  • Grow, R. et al., “Gigabit Media Independent Interface Proposal,” Nov. 11, 1996, IEEE 802.3Z, Vancouver, 22 pages.
  • Intel, “Pentium® II Processor at 350 MHz, 400 MHz, and 450 MHz, Datasheet,” Order No. 243657-003, Aug. 1998, 83 pages.
  • Ellis, S., “IRIS FailSafe™ Administrator's Guide,” Document No. 007-3109-003, Apr. 6, 1997, 212 pages.
  • NEC, “Server HX4500 User's Guide,” PN: 456-00005-000, Dec. 1998, 160 pages.
  • Novell, Inc., “NoVell's NetWare 4.1 Momentum Continues—NetWare 4 Now World's Best-Selling Network Operating System,” [online], Mar. 21, 1996, [retrieved on Nov. 16, 2009]. Retrieved from the Internet: <URL: http://www.novell.com/news/press/archive/1996/03/pr96056.html>, 2 pages.
  • Network Engines, “P6000EXP Fault-tolerant Load-balanced Clustered Server,” 1997, 3 pages.
  • Sun Microsystems Computer Company, “Sun™ Enterprise™ 250 Server Owner's Guide,” Jun. 1998, Part No. 805-5160-10, Revision A, 324 pages.
  • Sun Microsystems, Inc., “UltraSPARC™ -II CPU Module, Datasheet 400 MHz CPU, 2.0 MP E-Cache,” Jul. 1999, 28 pages.
  • Sun Microsystems, Inc., White Paper, “Netra™ ft 1800,” Apr. 1999, Revision 09, 50 pages.
  • Compaq Computer Corporation, et al., “Universal Serial Bus Specification,” Sep. 23, 1998, Revision 1.1, 327 pages.
  • Compaq Computer Corporation, et al., “Universal Serial Bus Specification,” Apr. 27, 2000, Revision 2.0, 650 pages.
  • Silicon Graphics International, “Additional Information for: IRIS FailSafe Administrator's Guide (IRIX 6.4),” [online], Document No. 007-3109-003, Published Apr. 6, 1997, [retrieved on Nov. 5, 2009], Retrieved from the Internet: <URL: http://techpubs.sgi.com/library/tpl/cgi-bin/summary.cgi?coll=0640&db=bks&docnumber=...>, 2 pages.
  • Origin and Onyx Theory of Operations Manual, Document No. 007-3439-002, 1997, Silicon Graphics, Inc., 124 pages.
  • QuantumNet, Inc., QuantumNet 6000 Sharing Modules [online], 1996 [retrieved on Nov. 16, 2009], Retrieved from the Internet: <URL: http://web.archive.org/web/19971011194326/www.quantumnet.com/dsq60xx.htm>, 3 pages.
  • JL ChatCom, Inc., “ChatTwin,” [retrieved on Dec. 2, 2009], JL ChatCom, Inc., ChatterBox Communications and Server Solutions [online], Retrieved from the Internet: <URL: http://web.archive.org/web/19970104222644/www.jlchatcom.com/chattwin.htm>, 2 pages.
  • Eversys, “Welcome to EverSys” [online], [retrieved on Nov. 16, 2009], Retrieved from the Internet: <URL: http://web.archieve.org/web/19961104092834/www.eversys.com/index2.htm>, 1 page.
  • Eversys, “Products” [online], [retrieved on Nov. 16, 2009], Retrieved from the Internet: <URL: http://web.archieve.org/web/19961104093103/www.eversys.com/prodinfo.htm> 2 pages.
  • “Microsoft Press Computer Dictionary, Third Edition,” Microsoft Press, 1997, pp. 199 and 332, Kim Fryer ed.
  • Excerpt from “Microsoft Computer Dictionary, 5th Edition”, Microsoft Press, 2002, pp. 96 and 547.
  • Excerpt from IEEE 100: The Authoritative Dictionary of IEEE Standards Terms (7th Ed., 2000), pp. 78, 79 and 128.
  • Anderson, C.R. et al., “IEEE 1355 HS-Links: Present Status and Future Prospects,” [online], 1998, [retrieved on Aug. 11, 2010], Retrieved from the Internet: <URL: http://www94.web.cern.ch/HIS/dshs/publications/wotug21/hslink/pdf/hslinkpaper.pdf>, 14 pages.
  • Mamakos, L. et al., “Request for Comments 2516—A method for Transmitting PPP Over Ethernet (PPPoE),” [online], 1999, [retrieved on Aug. 18, 2010], Retrieved from the Internet: <URL: http://ttols.ietf.org/html/rfc2516>, 35 pages.
  • Haas, S., “The IEEE 1355 Standard: Developments, Performance and Application in High Energy Physics,” Thesis for degree of Doctor of Philosophy, University of Liverpool, Dec. 1998, 138 pages.
  • “IEEE Std 1355-1995 Standard for Heterogeneous InterConnect (HIC),” Open Micro-processor systems Initiative (OMI), [online], Oct. 30, 1998, [retrieved on Aug. 6, 2010], Retrieved from the Internet: <URL: http://grouper.ieee.org/groups/1355/index.html>, 6 pages.
  • Galles, M., “Spider: A Hide-Speed Network Interconnect,” IEEE Micro, 1997, pp. 34-39. (6 pages).
  • Excerpt from “Microsoft Computer Dictionary, 4th Edition”, Microsoft Press, 1999, pp. 184-185, 241, 432 (7 pages).
  • Excerpt from “Microsoft Computer Dictionary, 4th Edition”, Microsoft Press, 1999, pp. 40, 241, 432 (6 pages).
  • Excerpt from IEEE 100: The Authoritative Dictionary of IEEE Standards Terms (7th Ed., 2000), pp. 181, 304 and 771.
  • “Family of VME Technology Specifications,” [online], date unknown, [retrieved on Dec. 29, 2010], Retrieved from the Internet: <URL: http://www.vita.com/specifications.html>, 1 page.
  • Cubix Customer Service Support System, “Click on the Front Panel That Matches Your System,” © 2000, Cubix [online], [retrieved on Jun. 22, 2004]. Retrieved from the Internet at <URL: http://64.173.211.7/support/techinfo/density/density.htm>, 1 page.
  • International Search Report for International Patent Application No. PCT/US99/09369, report mailed Nov. 16, 1999, 7 pages.
  • International Preliminary Examination Report for International Patent Application No. PCT/US99/09369, report completed Jul. 5, 2000, 4 pages.
  • IBM Corporation, “Grounding Spring for Peripheral Device and Bezel Bracket,” IBM Technical Disclosure Bulletin, Nov. 1, 1993, vol. 36, No. 11, 2 pages.
  • Digital Semiconductor Product Brief, “21152 PCI-to-PCI Bridge,” Feb. 1996, 6 pages.
  • Intel Corporation Architectural Overview, “Intel 430TX PCISET: 82439TX System Controller (MTXC),” Feb. 1997, 4 pages.
  • Intel Corporation Architectural Overview, “Intel 82371AB PCI-to-ISA/IDE XCEL-ERATOR (PIIX4),” Apr. 1997, 3 pages.
  • Intel Corporation Advance Information, “Intel 440LX AGPSET: 82443LX PCI A.G.P. Controller (PAC),” Aug. 1997, 4 pages.
  • National Semiconductor, DS90CR215/DS90CR216 +3.3V Rising Edge Data Strobe LVDS 21-Bit Channel Link-66 MHz, Jul. 1997, 2 pages.
  • National Semiconductor Product Folder, “DS90CR215 Plus-3.3V Rising Edge Data Strobe LVDS 21-Bit Channel and Link—66 MHz,” National Semiconductor Corporation [online], [retrieved on Oct. 30, 1997]. Retrieved from the Internet at <URL: http://www.national.com/search/search.cgi/design?keywords=DS90CR215>, 2 pages.
  • Video Electronics Standards Association (VESA), Plug and Display (P&D) Standard, P&D and Digital Transition Minimized Differential Signaling (TMDS) Video Transmission Overview, 1997, Version 1, Revision 0, pp. 13 & 31-34.
  • Liquorman, M., “Convergent Technologies Had This Idea,” Dec. 5, 1997, Jesse Berst's Anchor Desk [online], [retrieved on Jul. 10, 1998]. Retrieved from the Internet at: <URL: http://www.zdnet.com/anchordesk/talkback/talkback—56555.html>, 1 page.
  • Berst, J., “Hope for the Modular PCs We All Really Want,” Dec. 5, 1997, Jesse Berst's Anchor Desk [online], [retrieved on Jul. 10, 1998]. Retrieved from the Internet at: <URL: http://www.zdnet.com/anchordesk/story/story—1504.html>, 3 pages.
  • Boyd-Merritt, R., “Upgradable-PC Effort Takes Divergent Paths,” EE Times—Headline News [online], [retrieved on Jul. 31, 1998]. Retrieved from the Internet at : <URL: http://techweb.cmp.com/eet/news/97/949news/effort.html>, 3 pages.
  • Faegre, D. S. et al., “CTOS Revealed—Unisys' Best-Kept Secret Is An Operating System Built For Distributed Business Applications,” Dec. 1994, Core Technologies, BYTE [online], [retrieved on Jul. 10, 1998]. Retrieved from the Internet at: <URL: http://www.byte.com/art/9412/sec13/art2.htm>, 6 pages.
  • Spang, K., “Component House: Design Technology for ‘PCs in a Snap’—NeoSystems Offers Building Blocks,” Computer Reseller News, Apr. 21, 1997, Issue: 732, Section: Channel Assembly, TechWeb [online], [retrieved on Jul. 31, 1998]. Retrieved from the Internet at: <URL: http://www.techweb.com/se/directlink.cgi?CRN19970421S0054>, 2 pages.
  • “Think Modular,” Jun. 10, 1997, PC Magazine [online], [retrieved on Jul. 31, 1998]. Retrieved from the Internet at: <URL: wysiwyg://60/http://homezdnet.com/pcmag/issues/1611/pcmg0072.htm>, 1 page.
  • Office Action for U.S. Patent No. 6,718,415, mailed Oct. 10, 2002, 7 pages.
  • Response for U.S. Patent No. 6,718,415, filed Nov. 7, 2002, 9 pages.
  • Office Action for U.S. Patent No. 6,718,415, mailed Jan. 29, 2003, 7 pages.
  • Response for U.S. Patent No. 6,718,415, filed Mar. 6, 2003, 8 pages.
  • Office Action for U.S. Patent No. 6,718,415, mailed Jun. 4, 2003, 8 pages.
  • Response for U.S. Patent No. 6,718,415, filed Sep. 4, 2003, 10 pages.
  • Amendment Submitted With RCE for U.S. Patent No. 7,099,981, filed Mar. 1, 2006, 23 pages.
  • Office Action for U.S. Patent No. 7,363,415, mailed on Apr. 12, 2007, 23 pages.
  • Response for U.S. Patent No. 7,363,415, filed on Apr. 24, 2007, 25 pages.
  • Office Action for U.S. Patent No. 7,328,297, mailed Feb. 8, 2007, 5 pages.
  • Response for U.S. Patent No. 7,328,297, filed Apr. 19, 2007, 32 pages.
  • Office Action for U.S. Patent No. 7,328,297, mailed Jul. 12, 2007, 13 pages.
  • Response for U.S. Patent No. 7,328,297, filed Jul. 23, 2007, 20 pages.
  • Office Action for U.S. Patent No. 7,363,416, mailed Apr. 12, 2007, 23 pages.
  • Response for U.S. Patent No. 7,363,416, filed Apr. 24, 2007, 23 pages.
  • Office Action for U.S. Patent No. 7,376,779, mailed Sep. 28, 2007, 24 pages.
  • Response for U.S. Patent No. 7,376,779, filed Oct. 16, 2007, 23 pages.
  • Office Action for U.S. Patent No. 7,676,624, mailed Dec. 1, 2008, 8 pages.
  • Response for U.S. Patent No. 7,676,624, filed Jan. 13, 2009, 14 pages.
  • Supplemental Response for U.S. Patent No. 7,676,624, filed on Feb. 6, 2009, 13 pages.
  • Office Action for U.S. Patent No. 7,818,487, mailed Sep. 29, 2009, 10 pages.
  • Response for U.S. Patent No. 7,818,487, filed Nov. 6, 2009, 3 pages.
  • Amendment for U.S. Patent No. 7,818,487, filed May 11, 2010, 15 pages.
  • Amendment Submitted After Notice of Allowance for U.S. Patent No. 7,818,487, filed Aug. 17, 2010, 14 pages.
  • Office Action for U.S. Publication No. 2010/0174844, mailed Oct. 28, 2010, 11 pages.
  • Office Action for U.S. Patent No. 6,216,185, mailed Apr. 12, 2000, 9 pages.
  • Response for U.S. Patent No. 6,216,185, filed Aug. 3, 2000, 15 pages.
  • Office Action for U.S. Patent No. 6,216,185, mailed Aug. 25, 2000, 9 pages.
  • Response for U.S. Patent No. 6,216,185, filed Oct. 24, 2000, 10 pages.
  • Office Action for U.S. Patent No. 6,345,330, mailed Jun. 15, 2000, 7 pages.
  • Amendment for U.S. Patent No. 6,345,330, filed Sep. 12, 2000, 5 pages.
  • Restriction Requirement for U.S. Patent No. 6,345,330, mailed Dec. 19, 2000, 5 pages.
  • Amendment filed with Continued Prosecution Application for U.S. Patent No. 6,345,330, filed Jan. 17, 2001, 5 pages.
  • Office Action for U.S. Patent No. 6,345,330, mailed Mar. 23, 2001, 6 pages.
  • Response to Office Action for U.S. Patent No. 6,345,330, filed Jul. 19, 2001, 5 pages.
  • Office Action for U.S. Appl. No. 09/642,628, mailed Apr. 5, 2001, 9 pages.
  • Office Action for U.S. Appl. No. 10/963,825, mailed Oct. 27, 2005, 25 pages.
  • Response for U.S. Appl. No. 10/963,825, filed Jan. 9, 2006, 22 pages.
  • Office Action for U.S. Appl. No. 10/963,825, mailed May 31, 2006, 29 pages.
  • Amendment Submitted with RCE for U.S. Appl. No. 10/963,825, filed Jul. 27, 2006, 29 pages.
  • Office Action for U.S. Appl. No. 10/963,825, mailed Oct. 20, 2006, 28 pages.
  • Appellants' Brief for U.S. Appl. No. 10/963,825, filed Jan. 8, 2007, 31 pages.
  • Revised Appellants' Brief for U.S. Appl. No. 10/963,825, filed Apr. 20, 2007, 34 pages.
  • Examiner's Answer for U.S. Appl. No. 10/963,825, mailed Aug. 8, 2007, 30 pages.
  • Reply Brief for U.S. Appl. No. 10/963,825, filed Sep. 4, 2007, 4 pages.
  • Decision on Appeal for U.S. Appl. No. 10/963,825, mailed Feb. 4, 2009, 13 pages.
  • Amendment Submitted with RCE for U.S. Appl. No. 10/963,825, filed Feb. 20, 2009, 24 pages.
  • Office Action for U.S. Appl. No. 10/963,825, mailed May 14, 2009, 5 pages.
  • Response for U.S. Appl. No. 10/963,825, filed May 22, 2009, 2 pages.
  • Office Action for U.S. Appl. No. 10/963,825, mailed Sep. 15, 2009, 14 pages.
  • Response for U.S. Appl. No. 10/963,825, filed Oct. 1, 2009, 7 pages.
  • Office Action for RE 41,294, mailed Nov. 16, 2007, 10 pages.
  • Response for RE 41,294, filed Dec. 20, 2007, 21 pages.
  • Office Action for Re 41,294, mailed Apr. 15, 2008, 10 pages.
  • Amendment Submitted with RCE for RE 41,294, filed May 27, 2008, 14 pages.
  • Supplemental Amendment Submitted with RCE for RE 41,294, filed Jul. 8, 2008, 12 pages.
  • Office Action for RE 41,294, mailed Sep. 16, 2008, 11 pages.
  • Response for RE 41,294, filed Oct. 30, 2008, 14 pages.
  • Supplemental Response for RE 41,294, filed Feb. 20, 2009, 13 pages.
  • Supplemental Response for RE 41,294, filed Aug. 17, 2009, 3 pages.
  • Examiner Interview Summary Record, mailed Jan. 15, 2009, 1 page.
  • Office Action for RE 41,076, mailed Jul. 13, 2007, 38 pages.
  • Response for RE 41,076, filed Sep. 26, 2007, 18 pages.
  • Office Action for RE 41,076, mailed Oct. 17, 2007, 55 pages.
  • Amendment Submitted with RCE for RE 41,076, filed Nov. 5, 2007, 19 pages.
  • Office Action for RE 41,076, mailed Feb. 11, 2008, 62 pages.
  • Response for RE 41,076, filed Apr. 7, 2008, 18 pages.
  • Office Action for RE 41,076, mailed Jun. 9, 2008, 25 pages.
  • Amendment Submitted with RCE for RE 41,076, filed Dec. 8, 2008, 44 pages.
  • Office Action for RE 41,076, mailed Dec. 30, 2008, 8 pages.
  • Response for RE 41,076, filed Jan. 16, 2009, 14 pages.
  • Amendment Submitted with RCE for RE 41,076, filed Aug. 4, 2009, 2 pages.
  • Examiner Interview Summary Record, mailed Feb. 24, 2009, 4 pages.
  • Applicant Summary of Interview, filed Mar. 24, 2009, 1 page.
  • Examiner Interview Summary Record, mailed Sep. 22, 2009, 5 pages.
  • Office Action for U.S. Appl. No. 12/322,858, mailed Mar. 4, 2010, 24 pages.
  • Response for U.S. Appl. No. 12/322,858, filed Jun. 4, 2010, 15 pages.
  • Office Action for U.S. Appl. No. 12/322,858, mailed Jun. 25, 2010, 22 pages.
  • Response for U.S. Appl. No. 12/322,858, filed Oct. 25, 2010, 12 pages.
  • Office Action for U.S. Appl. No. 12/577,074, mailed Apr. 13, 2010, 7 pages.
  • Response for U.S. Appl. No. 12/577,074, filed Jul. 13, 2010, 3 pages.
  • Office Action for U.S. Appl. No. 12/577,074, mailed Nov. 10, 2010, 6 pages.
  • Office Action for U.S. Appl. No. 09/312,199, mailed Mar. 26, 2003, 5 pages.
  • Response for U.S. Appl. No. 09/312,199, filed Jun. 11, 2003, 5 pages.
  • Office Action for RE 41,092, mailed Sep. 17, 2008, 8 pages.
  • Response for RE 41,092, filed Oct. 27, 2008, 27 pages.
  • Examiner's Amendment for RE 41,092, mailed Nov. 4, 2009, 4 pages.
  • Office Action for U.S. Appl. No. 11/545,056, mailed Mar. 12, 2010, 26 pages.
  • Response for U.S. Appl. No. 11/545,056, filed Jun. 14, 2010, 18 pages.
  • Office Action for U.S. Appl. No. 12/561,138, mailed Sep. 29, 2010, 4 pages.
  • Request for Ex Parte Reexamination of US Patent No. 6,216,185, Control No. 90/010,816, filed Jan. 8, 2010, 39 pages.
  • Request for Ex Parte Reexamination of US Patent No. 6,216,185, Control No. 90/010,816, filed Jan. 8, 2010, Exhibit AA to Request Claim Charts with respect to the Hitachi '953 for Anticipation and Obviousness, 136 pages.
  • Request for Ex Parte Reexamination of US Patent No. 6,216,185, Control No. 90/010,816, filed Jan. 8, 2010, Exhibit BB Claim Charts with respect to Kobayashi for Anticipation and Obviousness, 128 pages.
  • Request for Ex Parte Reexamination of US Patent No. 6,216,185, Control No. 90/010,816, filed Jan. 8, 2010, Exhibit CC Claim Charts with respect to Byte for Anticipation and Obviousness, 122 pages.
  • Request for Ex Parte Reexamination of US Patent No. 6,216,185, Control No. 90/010,816, filed Jan. 8, 2010, Exhibit DD Claim Charts with respect to the Hitachi '675 for Anticipation and Obviousness, 119 pages.
  • Office Action in Ex Parte Reexamination of US Patent No. 6,216,185, Control No. 90/010,816, mailed Jul. 27, 2010, 103 pages.
  • Patent Owner's Response to Office Action in Ex Parte Reexamination of US Patent No. 6,216,185, Control No. 90/010,816, filed Sep. 27, 2010, 55 pages.
  • Request for Inter Partes Reexamination of US Patent No. 6,718,415, Control No. 95/001,276, filed Dec. 2, 2009, 44 pages.
  • Request for Inter Partes Reexamination of US Patent No. 6,718,415, Control No. 95/001,276, filed Dec. 2, 2009, Exhibit O, Declaration Under 37 CFR 1.132 of Vincent P. Conroy, Nov. 24, 2009, 3 pages.
  • Request for Inter Partes Reexamination of US Patent No. 6,718,415, Control No. 95/001,276, Replacement Exhibit AA, Claim Charts with respect to QuantumNet for Anticipation and Obviousness, filed Jan. 5, 2010, 109 pages.
  • Request for Inter Partes Reexamination of US Patent No. 6,718,415, Control No. 95/001,276, Replacement Exhibit BB, Claim Charts with respect to Chatcom for Anticipation and Obviousness, filed Jan. 5, 2010, 91 pages.
  • Request for Inter Partes Reexamination of US Patent No. 6,718,415, Control No. 95/001,276, Replacement Exhibit CC, Claim Charts with respect to QuantumNet for Anticipation and Obviousness, filed Jan. 5, 2010, 85 pages.
  • Request for Inter Partes Reexamination of US Patent No. 6,718,415, Control No. 95/001,276, Replacement Exhibit DD, Claim Charts with respect to the Origin2000 Manual for Obviousness, filed Jan. 5, 2010, 72 pages.
  • Request for Inter Partes Reexamination of US Patent No. 6,718,415, Control No. 95/001,276, Replacement Exhibit EE, Claim Charts with respect to Gallagher for Anticipation and Obviousness, filed Jan. 5, 2010, 107 pages.
  • Office Action in Inter Partes Reexamination of US Patent No. 6,718,415, Control No. 95/001,276, mailed May 26, 2010, 39 pages.
  • Patent Owner's Response to Office Action in Inter Partes Reexamination of US Patent No. 6,718,415, Control No. 95/001,276, filed Jul. 27, 2010, 41 pages.
  • Patent Owner's Response to Office Action in Inter Partes Reexamination of US Patent No. 6,718,415, Control No. 95/001,276, Exhibit A, Declaration of William Henry Mangione-Smith under 37 C.F.R. 1.132, filed Jul. 27, 2010, 29 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,099,981, Control No. 95/001,310, filed Feb. 9, 2010, 33 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,099,981, Control No. 95/001,310, filed Dec. 2, 2009, Exhibit O, Declaration Under 37 CFR 1.132 of Vincent P. Conroy, Nov. 24, 2009, 3 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,099,981, Control No. 95/001,310, Exhibit AA, Claim Charts with respect to Gallagher for Anticipation and Obviousness, filed Feb. 9, 2010, 164 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,099,981, Control No. 95/001,310, Exhibit BB, Claim Charts with respect to QuantumNet for Anticipation and Obviousness, filed Feb. 9, 2010, 158 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,099,981, Control No. 95/001,310, Exhibit CC, Claim Charts with respect to Chatcom for Anticipation and Obviousness, filed Feb. 9, 2010, 167 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,099,981, Control No. 95/001,310, Exhibit DD, Claim Charts with respect to the Eversys for Obviousness, filed Feb. 9, 2010, 111 pages.
  • Office Action in Inter Partes Reexamination of US Patent No. 7,099,981, Control No. 95/001,310, mailed Jul. 6, 2010, 83 pages.
  • Patent Owner's Response to Office Action in Inter Partes Reexamination of US Patent No. 7,099,981, Control No. 95/001,310, filed Sep. 3, 2010, 52 pages.
  • Patent Owner's Response to Office Action in Inter Partes Reexamination of US Patent No. 7,099,981, Control No. 95/001,310, Exhibit A, Declaration of William Henry Mangione-Smith under 37 C.F.R. 1.132, filed Sep. 3, 2010, 63 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,146,446, Control No. 95/001,328, filed Mar. 19, 2010, 35 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,146,446, Control No. 95/001,328, Exhibit AA (Part 1), Claim Charts with respect to Gallagher for Anticipation and Obviousness, filed Mar. 19, 2010, 186 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,146,446, Control No. 95/001,328, Exhibit AA (Part 2), Claim Charts with respect to Gallagher for Anticipation and Obviousness, filed Mar. 19, 2010, 161 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,146,446, Control No. 95/001,328, Exhibit BB (Part 1), Claim Charts with respect to QuantumNet for Anticipation and Obviousness, filed Mar. 19, 2010, 139 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,146,446, Control No. 95/001,328, Exhibit BB (Part 2), Claim Charts with respect to QuantumNet for Anticipation and Obviousness, filed Mar. 19, 2010, 128 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,146,446, Control No. 95/001,328, Exhibit CC, Claim Charts with respect to Chatcom for Anticipation and Obviousness, filed Mar. 19, 2010, 68 pages.
  • Office Action in Inter Partes Reexamination of US Patent No. 7,146,446, Control No. 95/001,328, mailed Jun. 24, 2010, 86 pages.
  • Patent Owner's Response to Office Action in Inter Partes Reexamination of US Patent No. 7,146,446, Control No. 95/001,328, filed. Aug. 24, 2010, 45 pages.
  • Patent Owner's Response to Office Action in Inter Partes Reexamination of US Patent No. 7,146,446, Control No. 95/001,328, Exhibit A, Declaration of William Henry Mangione-Smith under 37 C.F.R. 1.132, filed Sep. 3, 2010, 61 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,328,297, Control No. 95/001,336, filed Apr. 19, 2010, 33 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,328,297, Control No. 95/001,336, Exhibit AA, Claim Charts with respect to Gallagher for Obviousness, filed Apr. 19, 2010, 131 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,328,297, Control No. 95/001,336, Exhibit BB, Claim Charts with respect to QuantumNet for Obviousness, filed Apr. 19, 2010, 139 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,328,297, Control No. 95/001,336, Exhibit CC, Claim Charts with respect to Chatcom for Obviousness, filed Apr. 19, 2010, 114 pages.
  • Office Action in Inter Partes Reexamination of US Patent No. 7,328,297, Control No. 95/001,336, mailed Aug. 4, 2010, 95 pages.
  • Patent Owner's Response to Office Action in Inter Partes Reexamination of US Patent No. 7,328,297, Control No. 95/001,336, filed Oct. 4, 2010, 49 pages.
  • Patent Owner's Response to Office Action in Inter Partes Reexamination of US Patent No. 7,328,297, Control No. 95/001,336, Exhibit A, Declaration of William Henry Mangione-Smith under 37 C.F.R. 1.132, filed Oct. 4, 2010, 61 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,363,415, Control No. 95/001,424, filed Aug. 25, 2010, 34 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,363,415, Control No. 95/001,424, Exhibit AA, Claim Charts with respect to Gallagher and Other References for Obviousness, filed Aug. 25, 2010, 114 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,363,415, Control No. 95/001,424, Exhibit AB, Claim Charts with respect to Gallagher and Other References for Obviousness, filed Aug. 25, 2010, 92 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,363,415, Control No. 95/001,424, Exhibit BA, Claim Charts with respect to QuantumNet and Other References for Obviousness, filed Aug. 25, 2010, 121 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,363,415, Control No. 95/001,424, Exhibit BB, Claim Charts with respect to QuantumNet and Other References for Obviousness, filed Aug. 25, 2010, 99 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,363,415, Control No. 95/001,424, Exhibit CA, Claim Charts with respect to Chatcom and Other References for Obviousness, filed Aug. 25, 2010, 91 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,363,415, Control No. 95/001,424, Exhibit CB, Claim Charts with respect to Chatcom and Other References for Obviousness, filed Aug. 25, 2010, 94 pages.
  • Office Action in Inter Partes Reexamination of US Patent No. 7,363,415, Control No. 95/001,424, mailed Nov. 1, 2010, 75 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,376,779, Control No. 95/001,475, filed Oct. 27, 2010, 35 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,376,779, Control No. 95/001,475, Exhibit AA, Claim Charts with respect to Gallagher and Other References for Obviousness, filed Oct. 27, 2010, 128 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,376,779, Control No. 95/001,475, Exhibit AB, Claim Charts with respect to Gallagher and Other References for Obviousness, filed Oct. 27, 2010, 153 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,376,779, Control No. 95/001,475, Exhibit BA, Claim Charts with respect to QuantumNet and Other References for Obviousness, filed Oct. 27, 2010, 108 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,376,779, Control No. 95/001,475, Exhibit BB, Claim Charts with respect to QuantumNet and Other References for Obviousness, filed Oct. 27, 2010, 112 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,376,779, Control No. 95/001,475, Exhibit CA, Claim Charts with respect to Chatcom and Other References for Obviousness, filed Oct. 27, 2010, 112 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,376,779, Control No. 95/001,475, Exhibit CB, Claim Charts with respect to Chatcom and Other References for Obviousness, filed Oct. 27, 2010, 118 pages.
  • Office Action in Inter Partes Reexamination of US Patent No. 7,376,779, Control No. 95/001,475, mailed Dec. 20, 2010, 105 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,363,416, Control No. 95/001,476, filed Oct. 27, 2010, 37 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,363,416, Control No. 95/001,476, Exhibit AA, Claim Charts with respect to Gallagher and Other References for Obviousness, filed Oct. 27, 2010, 70 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,363,416, Control No. 95/001,476, Exhibit AB, Claim Charts with respect to Gallagher and Other References for Obviousness, filed Oct. 27, 2010, 64 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,363,416, Control No. 95/001,476, Exhibit BA, Claim Charts with respect to QuantumNet and Other References for Obviousness, filed Oct. 27, 2010, 64 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,363,416, Control No. 95/001,476, Exhibit BB, Claim Charts with respect to QuantumNet and Other References for Obviousness, filed Oct. 27, 2010, 71 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,363,416, Control No. 95/001,476, Exhibit CA, Claim Charts with respect to Chatcom and Other References for Obviousness, filed Oct. 27, 2010, 64 pages.
  • Request for Inter Partes Reexamination of US Patent No. 7,363,416, Control No. 95/001,476, Exhibit CB, Claim Charts with respect to Chatcom and Other References for Obviousness, filed Oct. 27, 2010, 67 pages.
  • Office Action in Inter Partes Reexamination of US Patent No. 7,363,416, Control No. 95/001,476, mailed Dec. 6, 2010, 63 pages.
  • “Defendants' Amended Invalidity Contentions,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 18 pages.
  • “Exhibit A (Asserted Claims),” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 2 pages.
  • “Exhibit B—Table 1,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 75 pages.
  • “Exhibit C,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 2 pages.
  • “Exhibit D,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 106 pages.
  • “Exhibit E,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 2 pages.
  • “Invalidity Chart for Base Reference IBM 8260,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 53 pages.
  • “Invalidity Chart for Base Reference IBM 8265,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 56 pages.
  • “Invalidity Chart for Base Reference U.S. Patent No. 4,453,215 (Reid),” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 56 pages.
  • “Invalidity Chart for Base Reference Origin2000,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 56 pages.
  • “Invalidity Chart for Base Reference QuantumNet,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 49 pages.
  • “Invalidity Chart for Base Reference U.S. Patent No. 6,564,274 (Heath),” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 57 pages.
  • “Invalidity Chart for Base Reference U.S. Patent No. 5,577,205,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 60 pages.
  • “Invalidity Chart for Base Reference U.S. Patent No. 5,802,391,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 61 pages.
  • “Invalidity Chart for Base Reference U.S. Patent No. 6,715,100,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 64 pages.
  • “Invalidity Chart for Base Reference Cubix BC/Density,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 64 pages.
  • “Invalidity Chart for Base Reference JP6-289956,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 62 pages.
  • “Invalidity Chart for Base Reference Gallagher 068 and Gallagher 503,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 108 pages.
  • “Invalidity Chart for Base Reference Compaq ProLiant Cluster,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 81 pages.
  • “Invalidity Chart for Base Reference U.S. Patent No. 5,325,517 to Baker et al. (Appendix 1, Exhibit 15),” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 59 pages.
  • “Invalidity Chart for Japanese Patent Application H7-64672 (Toshiba '672),” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 55 pages.
  • “Invalidity Chart for Base Reference ChatCom,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 52 pages.
  • “Invalidity Chart for Base Reference Ziatech Corp. Ketris 9000 System,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 68 pages.
  • “Invalidity Chart for Base Reference Ziatech STD 32 Star System,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 62 pages.
  • “Invalidity Chart for Base Reference U.S. Patent No. 7,339,786 (Bottom et al.),” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 57 pages.
  • “Invalidity Chart for Base References RLX Patents, U.S. Patent Nos. 6,747,878, 6,411,506, 6,325,636, 6,757,748, and 6,985,967 (Hipp et al.),” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 58 pages.
  • “Invalidity Chart for Base Reference Network Engines P6000 Server,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 59 pages.
  • “Invalidity Chart for Base Reference Eversys 8000 System,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 60 pages.
  • “Invalidity Chart for Base Reference Eversys CAPserver,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 59 pages.
  • “Invalidity Chart for Base Reference U.S. 5,809,262,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 62 pages.
  • “Invalidity Chart for Base Reference WhiteCross 9800 System,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 62 pages.
  • “Invalidity Chart for Base Reference U.S. 5,339,408,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 61 pages.
  • “Invalidity Chart for Base Reference Tyuluman 536,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 76 pages.
  • “Invalidity Chart for Base Reference Hong 737,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 77 pages.
  • “Invalidity Chart for Base Reference U.S. 5,436,857 (Nelson),” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 6 pages.
  • “Invalidity Chart for Base Reference U.S. 5,999,952 (Jenkins)”, submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 6 pages.
  • “Invalidity Chart for Base Reference U.S. 5,608,608 (Flint)”, submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 6 pages.
  • “Invalidity Chart for Base Reference U.S. 5,978,821 (Freeny)”, submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 6 pages.
  • “Invalidity Chart for Base Reference WO 92/18924 (Wallsten)”, submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 6 pages.
  • “Invalidity Chart for Base Reference Ergo Moby Brick”, submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 5 pages.
  • “Invalidity Chart for Base Reference U.S. Patent No. 5,463,742 (Kobayashi)”, submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 5 pages.
  • “Invalidity Chart for Base Reference Japanese Patent Application Publication H6-289953 (Hitachi)”, submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 5 pages.
  • “Invalidity Chart for Base Reference Japanese Patent Application Publication H7-84675 (Hitachi)”, submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 5 pages.
  • “Invalidity Chart for Base Reference U.S. Patent No. 5,187,645 (Spalding)”, submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 6 pages.
  • “Defendants' Notice of Errata Relating to Defendants' P.R. 3-3 Invalidity Contentions,” submitted by the Defendants in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2010, 14 pages.
  • U.S. Appl. No. 12/322,858, filed Feb. 5, 2009, Chu.
  • U.S. Appl. No. 11/545,056, filed Oct. 6, 2006, Chu.
  • Part 3: Carrier sense multiple access with collision detertion (CSMA/CD) access method and physical layer specifications, IEEE Standard 802.3z, The Institute of Electrical and Electronics Engineers, Inc., Jul. 1998, 1262 pages.
  • Excerpt from “Microsoft Computer Dictionary, 5th Edition”, Microsoft Press, 2002, pp. 96, 329, 624 and 625.
  • Intel Corporation, Intel 82559 Fast Ethernet Controller, [retrieved on Mar. 14, 2011], Retrieved from the Internet: <URL: http://www.intel.com/design/network/products/lan/controllers/82559.htm>, 1 page.
  • Gruener, J., “Vendors Pack in More Servers,” PC Week, vol. 14, No. 1, Mar. 17, 1997, 2 pages.
  • Grigonis, R., “Fault Resilient PC's,” Flatiron Publishing, 1996, 314 pages.
  • Microsoft Press Computer User's Dictionary, pp. 82 and 232, Kim Fryer ed., Microsoft Press, 1998, 5 pages.
  • IBM Thinkpad Product Information Guide, IBM PC Company, Apr. 28, 1998, 26 pages.
  • The American Heritage Dictionary, pp. 536, 607 and 770, Dell Publishing, 1994, 5 pages.
  • The New IEEE Standard Dictionary of Electrical and Electronics Terms, Fifth Ed., p. 1236, The Institute of Electrical and Electronics Engineers, Inc., 1993, 3 pages.
  • Microsoft Press Computer Dictionary, Third Ed., pp. 96, 313, and 355, Kim Fryer ed., Microsoft Press, 1997, 5 pages.
  • IBM Dictionary of Computing, Tenth Ed., pp. 139, 439, 480 and 629, George McDaniel ed., McGraw-Hill, Inc., Aug. 1993, 16 pages.
  • IEEE 100: The Authoritative Dictionary of IEEE Standards Terms, Seventh Ed., pp. 703, 704, 856 and 1064, The Institute of Electrical and Electronics Engineers, Inc., 2000, 13 pages.
  • Microsoft Press Computer Dictionary, Second Edition, pp. 82, 92, 93 and 260, Alice Smith ed., Microsoft Press, 1994, 13 pages.
  • Microsoft Press Computer User's Dictionary, pp. 232, 262, and 275, Kim Fryer ed., Microsoft Press, 1998, 12 pages.
  • Feibel, W., Encyclopedia of Networking, Third Edition, p. 265, the Network Press, 2000, 4 pages.
  • System 8000, Consolidated Network Server, Product Brief, Eversys Corporation, undated, 2 pages.
  • System 8000, Consolidated Server, Presentation, Eversys Corporation, undated, 23 pages.
  • IEEE Standard for a High Performance Serial Bus, IEEE Std 1394-1995, The Institute of Electrical and Electronics Engineers, Inc., 1996, 392 pages.
  • RLX System 324 Hardware Installation Guide, RLX Technologies, Inc., 2001, 80 pages.
  • RLX System 324 Platform Guide: RLX Linux Web Server, RLX Technologies, Inc., 2001, 73 pages.
  • RLX System 324 Platform Guide—Windows Powered Web Server—Online, undated, 39 pages.
  • RLX System 324 Technical Guide: RLX Control Tower SNMP Implementation, RLX Techologies, 2001, 32 pages.
  • RLX System 324 Technical Guide: RLX Control Tower SNMP Implementation, Supplementary Document, Draft, RLX Techologies, May 26, 2001, 48 pages.
  • RLX System 324 Technical Guide: RLX Control Tower Backup/Restore, Draft, RLX Techologies, May 18, 2001, 8 pages.
  • “RocketLogix Passive I/O Board Topology,” RocketLogix, Inc., Revision 6, May 24, 2000, 1 page.
  • “RocketLogix Switched I/O Board Topology,” RocketLogix, Inc., Revision 6, May 24, 2000, 1 page.
  • HotDock and Orbiter 3360—Technical Specifications, Product Overview, and Configurations, RocketLogix, Inc., 2000, 4 pages.
  • “Redefining Server Economics—Take Control,” RLX Technologies, 2001, 2 pages.
  • RLX Technologies Presentation, RLX Technologies, Inc., Apr. 27, 2001, 44 pages.
  • “Engineering Design Proposal for RocketLogix, Inc.,” Anigma, Inc., Apr. 19, 2000, 35 pages.
  • RLX Blade, RLX Technologies, 2001, 2 pages.
  • “RLX System 324 Technical Guide: RLX Red Hat Installation,” RLX Technologies, Inc., 2001, 22 pages.
  • “Firmware Interface Specification,Orbiter 1680, Orbiter 3360,” Anigma, Inc., Aug. 17, 2000, 16 pages.
  • Board Specifications for DataModule Board, DataStation Backplane, DataStation Front Bezel, and BaseStation Backplane, Rev. E, Anigma, Inc., Mar. 2, 2000, 5 pages.
  • “Logical Management Process,” RocketLogix, Rev. 5, Apr. 5, 2000, 1 page.
  • Eversys Corporation Business Plan, Eversys Corporation, Mar. 21, 1997, 53 pages.
  • System 8000 Web Product Brief, Eversys Corporation, [retrieved on Oct. 22, 2009], Retrieved from the Internet: <URL: http://www.web.archive.org/web/1997052509465/www.eversys.com/Products/S8000/Brief/Index/htm, 6 pages.
  • Nicholls, T., “9800 First level design,” White Cross Systems Limited, Mar. 26, 1997, 26 pages.
  • Nicholls, T., “9800 System Architecture,” White Cross Systems Limited, Mar. 27, 1997, 28 pages.
  • Feakes. L., “Fast Ethernet Switch Card Design Specification,” Revision 4.00, White Cross Systems Limited, Jul. 27, 2010, 23 pages.
  • Phillips, J., “9800 Power System Backplane Design Specification,” Revision 1.00, White Cross Systems Limited, Oct. 22, 1997, 11 pages.
  • Phillips, J., “9800 Auxiliary PSU Design Specification,” Revision 1.00, White Cross Systems Limited, Oct. 27, 1997, 13 pages.
  • “Narus and Whitecross Join Forces to Deliver Comprehensive Usage Pattern Analysis Applications for IP Service Providers,” Press Release, Palo Alto, CA, Mar. 27, 2000, 4 pages.
  • “P6000 Fault-Tolerant Multiprocessor Application Server,” Powerstation Technologies, Inc., 1996, 3 pages.
  • Network Engines P6000 System Guide, Revision C, Network Engines, Inc., Jul. 1998, 89 pages.
  • Network Engines P6000EXP System Guide, Revision A, Network Engines, Inc., Jan. 1998, 106 pages.
  • Powerstation Technologies P6000 System Guide, Powerstation Technologies, Inc., 1996, 65 pages.
  • Network Engines™ SBC2000ST Reference Guide, Rev. A, Network Engines, Inc., Oct. 1998, 178 pages.
  • Network Engines™ SBC2000S Reference Guide, Rev. 1.0, Network Engines, Inc., Sep. 1998, 156 pages.
  • Network Engines™ SBC2000 User's Manual, Rev. 1.0, Network Engines, Inc., Jul. 1998, 140 pages.
  • Network Engines™ SBC1000 User's Manual, Rev. E Draft, Network Engines, Inc., Jun. 1998, 78 pages.
  • Pentium Processor™ Network Engines™ P586 Guide, Issue 0.0.20 Preliminary, Network Engines, Inc., Nov. 10, 1997, 58 pages.
  • “PTI Fault Tolerant System Working Document Specification,” Rev 0, Feb. 26, 1996, 2 pages.
  • Network Engines Network, Network Engines, Inc., Jun. 22, 1999, 20 pages.
  • “HMU—586 Card Guide (Mustang) Pentium PCI,” Issue 0.0.14 Preliminary, HM Systems, Inc., Nov. 18, 1996, 57 pages.
  • “TLD Queries Complete Call Detail Record Database with WhiteCross Data Exploration Server,” Data Mining Product Reviews, Feb. 2000, 1 page.
  • “WhiteCross Data Exploration Announces ExplorationSTUDIO™,” Press Release, New York, NY, Sep. 2, 1999, 2 pages.
  • “WhiteCross Introduces ‘World's Most Powerful Exploration Warehouse System,’” Press Release, New York, NY, Sep. 2, 1999, 2 pages.
  • Charlesworth, I., “Technology Audit, Data Exploration Server,” Butler Group, Sep. 1999, 8 pages.
  • Groom, P., “WhiteCross 9800 pre-release configuration details and USA Pricing Information,” WhiteCross Systems Limited, Nov. 3, 1998, 4 pages.
  • Letter to Barac from Pacotti, Jr. with attachments on WhiteCross Data Exploration, undated, 12 pages.
  • “Kognitio—Infrastructure Partners,” Retrieved from the Internet on Sep. 8, 2010, Retrieved at URL: www.kognito.com/partners/infrastructure.php, 2 pages.
  • RocketLogix Presentation, RocketLogix, Inc., Apr. 6, 2000, 84 pages.
  • “Expanding the Reach of the Internet with a New Breed of Web Server Appliances,” RocketLogix, Inc., May 2000, 10 pages.
  • Radigan, J., “A Solution to the Power Shortage?” CFO.com, Jan. 17, 2001, [online] Retrieved from the Internet on Dec. 14, 2007, Retrieved at URL: www.cfo.com/article.cfm/2991376?f=singlepage, 3 pages.
  • Goldman, A, “ISP Profiles: RLX Technologies,” ISP-Planet, May 17, 2001, retrieved from the Internet on Jul. 26, 2001, Retrieved at URL: www.isp-planet.com/profiles/2001/rlx.html, 3 pages.
  • Rosencrance, L., “IBM agrees to resell RLX high-density servers,” Computerworld, May 8, 2001, retrieved from the Internet on Jul. 25, 2001, Retrieved at URL: www.itworld.com/Comp/1362/CWD010508STO60353/pfindex.html, 3 pages.
  • “ChatCom, Inc. Announces Results for the Dec. 31, 1996 Quarter,” ChatCom, Inc., Press Release, Feb. 12, 1997, 2 pages.
  • “ChatCom Defines Specification for Future Consolidated Server Products, RAINS™ Concept to Accelerate the Adoption of Consolidated Servers,” ChatCom, Inc., Press Release, Mar. 31, 1997, 2 pages.
  • “ChatCom, Inc. Announces PentiumPro/200 MHz Server Module, Server Module Offers Scalability and High Availability for File Server Environments,” ChatCom, Inc., Press Release, Mar. 24, 1997, 3 pages.
  • “ChatCom Strengthens Sales Management Team, Three New Sales Directors to Address Growing Demand for ChatCom's ChatterBox™,” ChatCom, Inc., Press Release, Mar. 18, 1997, 2 pages.
  • “ChatCom Announces Major Push into International Markets, Significant International Sales Opportunities for ChatCom's Consolidated Server Technology,” ChatCom, Inc., Press Release, Mar. 18, 1997, 2 pages.
  • “ChatCom Receives Product Award From LAN Times Magazine, Consolidated Server Product Comparison Puts ChatCom on Top,” ChatCom, Inc., Press Release, Feb. 20, 1997, 2 pages.
  • “Astro Sciences Corporation Shareholders Elect Two New Directors, and Vote to Change Corporate Name to ChatCom, Inc.,” Astro Sciences Corporation, Press Release, Feb. 12, 1996, 2 pages.
  • “ChatCom, Inc., (Formerly Astro Sciences Corporation) Trades Under New Symbol—NASDAQ/NMS: CHAT,” ChatCom, Inc., News Release, Feb. 22, 1996, 1 page.
  • “ChatCom Names James B. Mariner President/CEO,” ChatCom, Inc., Press Relase, Mar. 7, 1996, 2 pages.
  • “ChatCom Selected as Partner in Anixter Race '96 Program and Completes First Part of Financing,” ChatCom, Inc., Press Release, Mar. 26, 1996, 2 pages.
  • “Astro Sciences Corporation Announces Results for The Third Quarter,” Astro Sciences Corporation, Press Release, Feb. 8, 1996, 23 pages.
  • “Telecom Australia to Receive Astro Sciences/J&L 486 Services,” Astro Sciences Corporatoin, Press Release, Jan. 4, 1996, 1 page.
  • “Astro Sciences Receives Microsoft Certification and Announces New Director,” Astro Sciences Corporation, Press Release, Nov. 21, 1995, 2 pages.
  • “Astro Sciences Corp. Announces Results for Second Quarter,” Astro Sciences Corporation, Press Release, Nov. 17, 1995, 2 pages.
  • “Astro Sciences Corp. Signs Agreement With Storage Computer Corp.,” Astro Sciences Corporation, Press Release, Nov. 7, 1995, 2 pages.
  • “Astro Sciences Corporation Appoints Interim President/CEO Board Expanded by Two Seats,” Astro Sciences Corporation, Press Release, Aug. 17, 1995, 1 page.
  • “Astro Sciences Corporation Announces Results for the First Quarter of the Fiscal Year,” Astro Sciences Corporation, Press Release, Aug. 3, 1995, 1 page.
  • “Astro Sciences Corporation Retains Technology Strategies and Alliance Partners,” Astro Sciences Corporation, News Release, Jun. 29, 19951 page.
  • “Astro Sciences Corporation Receives Patent for Network Security and Management,” Astro Sciences Corporation, News Release, Jun. 6, 1995, 1 pages.
  • “Astro Sciences Corporation Introduces New Generation of Products at PC Expo Show,” Astro Sciences Corporation, Press Release, Jun. 23, 1995, 1 page.
  • “Astro Sciences Corporation Announces Results for the Fourth Quarter and the Fiscal Yeart,” Astro Sciences Corporation, News Release, Jun. 26, 1995, 2 pages.
  • “Astro Sciences Corporation Announces Signing of $4 Million Credit Facility With Deutsche Financial Services,” Astro Sciences Corporation, News Release, May 19, 1995, 1 page.
  • “Astro Sciences Corporation to Strengthen Management Team Board,” Astro Sciences Corporation, News Release, Apr. 21, 1995, 1 page.
  • “J&L Announces their ChatExpress—P75Applications Server at Networks Expo,” J&L Information Systems, Press Release, Feb. 13, 1994, 3 pages.
  • “J&L Information Systems Announces two DX4 for their ChatterBox Family of Remote Access Servers,” J&L Information Systems, Press Release, Feb. 13, 1994, 2 pages.
  • “J&L Announces the NRS-T10RS™ a Fault Tolerant Applications Server Platform at FOSE,” J&L Information Systems, Press Release, Mar. 20, 1994, 2 pages.
  • “J&L Announces their ChatAccess™ Family of Remote LAN Node Servers at Networld+Intertop Las Vegas,” J&L Information Systems, Press Release, Mar. 27, 1994, 2 pages.
  • “J&L Announces ChatExpress—P120 Rackmounted Applications Server at PC Expo, New York,” J&L Information Systems, Press Release, Jun. 19, 1994, 2 pages.
  • “ChatCom Books Additional Orders with Major Facilities-Based Carrier Companies, ChatCom Products Provide Internet Platforms for Carrier's Customers Worldwide,” ChatCom, Inc., Press Release, Mar. 12, 1997, 2 pages.
  • “ChatCom Announces Comprehensive VAR Program, Commitment to VARs is Key to Corporate Strategy,” ChatCom, Inc., Press Release, Jan. 13, 1997, 1 page.
  • “ChatCom, Inc. Reports Completion of $2.5 Million Private Placement,” ChatCom, Inc., Press Release, Jan. 9, 1997, 2 pages.
  • “ChatCom Announces Mass Storage Subsystem, ChatRAID to Address Application Server Market,” ChatCom, Inc., Press Release, Aug. 12, 1996, 1 page.
  • “ChatCom, Inc. Announces Commitment to ISO 9001 Quality Certification, ISO 9001 Quality Control Programs are High Priority Company Imperative,” ChatCom, Inc., Press Release, Aug. 1, 1996, 1 page.
  • “ChatCom Adds New Senior Management Team Members,” ChatCom, Inc., Press Release, Jul. 2, 1996, 1 page.
  • “ChatCom Announces Mass Storage Subsystem, ChatRAID to Address Application Server Market,” ChatCom, Inc., Press Release, Aug. 14, 1996, 2 pages.
  • “ChatCom Announces Complete Line of Scaleable Application and Communication Servers,” ChatCom, Inc., Press Release, Aug. 30, 1996, 4 pages.
  • “ChatCom, Inc. Announces Highly Adaptable Intranet and Web Servers, Servers reduce costs associated with radical change,” Press Release, Sep. 3, 1996, 1 page.
  • J&L Introduces Twin Pentium for ChatterBox Systems, J&L Information Systems, Press Release, Jan. 29, 1996, 1 page.
  • “ChatterBox/SAS™—Scaleable Access Server™,” J&L Information Systems, Networks Expo—Boston '96, Dec. 22, 1995, 1 page.
  • “J&L Information Systems Announces ChatPower-Plus™ a Revolutionary Redundant Power Supply System,” J&L Information Systems, Press Release, Jun. 19, 1995, 2 pages.
  • “J&L Announces ChatAccess/PC™, a PCMCIA Based Remote LAN Node Server,” J&L Information Systems, Press Release, Jun. 19, 1995, 2 pages.
  • “J&L Announces Two Patents,” J&L Information Systems, Press Release, Feb. 9, 1995, 1 page.
  • “J&L Announces their ChatExpress-P100 Rackmounted Applications Server at Networks Expo. Boston,” J&L Information Systems, Press Release, Feb. 13, 1994, 3 pages.
  • “J&L Doubles the Rack-Mounted Communications Server Density with ChatVantage/486™,” J&L Information Systems, Press Release, Sep. 11, 1995, 2 pages.
  • “ChatCom, Inc. Announces Results for the Jun. 30 Quarter,” ChatCom, Inc., News Release, Aug. 16, 1996, 2 pages.
  • “Introducing the new ChatterBox™ Corporate and Office Series . . . the Power Behind Your Network,” ChatCom, Inc., May 31, 1996, 15 pages.
  • “ChatterBox Communications and Server Solutions,” ChatCom, Inc., Mar. 7, 1996, 12 pages.
  • “ChatterBox Communications and Server Solutions Products,” ChatCom, Inc., Apr. 24, 1996, 7 pages.
  • Lazik, G., “Remote Access—a Historical Perspective,” Network News, vol. 3, No. 7, NPA The Network Professional Association, Jul. 1994, 6 pages.
  • Lazik, G., “Remote Access—Part II, Cost Analysis,” Network News, vol. 3, No. 8, NPA The Network Professional Association, Sep. 1994, 5 pages.
  • “Plexnet™ Product Overview,” Plexcom, Inc., 1992, 8 pages.
  • “Thin Client Servers High-Speed Data Switching Technical Summary,” QuantumNet, Inc., Aug. 29, 2010, 28 pages.
  • Facsimile from Procrass to Paunovich attaching “QuantumNet Network Computing Systems,” Aug. 30, 2010, 8 pages.
  • World Wide System Price Guide, Network Engines, Inc., Sep. 26, 1997, 10 pages.
  • P6000 System Price Guide, Network Engines, Inc., Feb. 24, 1998, 9 pages.
  • “Venture financing is fuel for Powerstation's Growth Plans,” Mass High Tech Communications, Inc., Jun. 2, 1997, 1 page.
  • Grigonis, R., “Life-Saving Computers: Network Engines,” Computer Telephony, Sep. 1997, 1 page.
  • Rodgers, A., “NT Clustering Hardware Readied, Vendor Racks up Windows NT Clustering Options at NetWorld+Interop,” Internetweek, Oct. 20, 1997, 1 page.
  • “Network Engines Awarded Best of Show at Networld+Interop 97, New company debuts product and wins,” Network Engines, Inc., Press Release, Oct. 14, 1997, 2 pages.
  • Network Engines Website, Network Engines, Inc., [retrieved on Feb. 27, 1998], Retrieved from the Internet: <URL: http://www.networkengines.com/>, 12 pages.
  • Network Engines, Inc., Company Overview, Aug. 26, 2010, 21 pages.
  • Network Engines ClusterDirector Users' Manual, Revision B, Network Engines, Inc., Jun. 1998, 88 pages.
  • Network Engines ClusterDirector Users' Manual, Network Engines, Inc., Jan. 1998, 52 pages.
  • MP700 User Guide, Issue 0.0.89, Network Engines, Inc., Oct. 16, 1997, 29 pages.
  • “ClusterDirector™ Product Description, Fault Tolerance for Industry Standard Processors, Operating Systems, and Applications,” Network Engines, Inc., 1998, 4 pages.
  • “Network Engines Announces New Clustered Application Servers for Web, Thin-Client and Windows NT Enterprise Environments,” Network Engines, Inc., Press Release, Oct. 8, 1997, 3 pages.
  • “Network Engines Announces Partnership With Telegration Associates, Inc.,” Network Engines, Inc., Press Release, Dec. 10, 1997, 2 pages.
  • “Network Engines Debuts ClusterDirector in Internet/Intranet Load Balanced Environment,” Network Engines, Inc., Press Release, Jan. 27, 1998, 3 pages.
  • Stallings, W., “Computer Organization and Architecture—Designing for Performance,” Sixth Edition, Pearson Education, Inc., 2003, pp. 69-89.
  • Hill, Goff (editor), “The Cable and Telecommunications Professional's Reference: vol. 1,” Third Edition, Focal Press, 2007, pp. 225-229, 7 pages.
  • Dell, Inc., White Paper, “PCI Express Technology,” Feb. 2004, pp. 1-11.
  • Athavale, A., “How to Lower the Cost of PCI Express Adoption by Using FPGAs,” EETimes Design [online] Apr. 26, 2006, [retrieved on May 3, 2011]. Retrieved from the Internet at <URL: http://www.eetimes.com/General/DisplayPrintViewContent?contentItemID=4014824>, 6 pages.
  • Thoms, I., “IBM Hit with $9M Judgment in Server Patent Suit,” Law360 [online], [retrieved on May 3, 2011], Retrieved from the Internet at <URL: http://www.law360.com/articles/229575/print?section=ip>, 2 pages.
  • McKenzie, L., “Fujitsu Reaches Deal in Acqis Blade Server IP Spat,” Law360 [online], [retrieved on Jun. 16, 2010], Retrieved from the Internet at <URL: http://ip.law360.com/print—article/175004>, 2 pages.
  • PCI Local Bus Specification, Rev. 2.1, the PCI Special Interest Group, Jun. 1, 1995, 298 pages.
  • “National Semiconductor Design Guide,” LVDS Owner's Manual, Spring 1997, 65 pages.
  • Intel Corporation, “PCI Express* to PCI-X* Bridge Architecture: Where Interface Standards Meet,” 2003, 8 pages.
  • Desai, D.M. et al., “BladeCenter system overview,” IBM Journal of Research and Development, vol. 49, No. 6, Nov. 2005, pp. 809-821, 13 pages.
  • Spring, Tom, “Top of the News—Broadband Users Still Sing the Blues,” PC World, Jun. 2011, pp. 42-54, 13 pages.
  • San Jose Mercury News, “Business & Stocks—Top Stories from the Mercury News,” Jun. 28, 2001, [online], [retrieved on Jun. 30, 2001], Retrieved from the Internet at <URL: http://www0.mercurycenter.com/premium/business/docs—technews28.htm>, 5 pages.
  • “iMod Pad,” Wired Magazine, Mar. 2001, 1 page.
  • “Amended Invalidity Chart for Base Reference Network Engines P6000 Server,” submitted by the Defendants in connection with Case No. 6:09-cv-148-LED on Jun. 4, 2010, 64 pages.
  • Email from Emanuel to Juarez including Invalidity Chart for Base Reference IBM BladeCenter, submitted by the Defendants in connection with Case No. 6:09-cv-148-LED, dated Aug. 20, 2010, 54 pages.
  • Letter from Martiniak to Byers regarding Proposed Amendment to the Invalidity Contentions based on products from RLX Systems and a description of RLX products, dated Jul. 15, 2010, 2 pages.
  • Defendant's Invalidty Chart for Base Reference RLX System 324, proposed in connection with Case No. 6:09-cv-148-LED on Jul. 15, 2010, 58 pages.
  • “Disclosure of Asserted Claims and Infringement Contentions,” submitted by the Plaintiff in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED, served on Sep. 14, 2009, 5 pages.
  • “Exhibit 1, Disclosure of Asserted Claims and Infringement Contentions for Defendant Appro International, Inc.,” submitted by the Plaintiff in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED, served on Sep. 14, 2009, 105 pages.
  • “Exhibit 2, Disclosure of Asserted Claims and Infringement Contentions for Defendant ClearCube Technology, Inc.,” submitted by the Plaintiff in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED, served on Sep. 14, 2009, 163 pages.
  • “Exhibit 3, Disclosure of Asserted Claims and Infringement Contentions for Defendant Dell Inc.,” submitted by the Plaintiff in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED, served on Sep. 14, 2009, 184 pages.
  • “Exhibit 4, Disclosure of Asserted Claims and Infringement Contentions for Defendant Fujitsu America, Inc.,” submitted by the Plaintiff in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED, served on Sep. 14, 2009, 210 pages.
  • “Exhibit 5, Disclosure of Asserted Claims and Infringement Contentions for Defendant Hewlett-Packard Co.,” submitted by the Plaintiff in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED, served on Sep. 14, 2009, 279 pages.
  • “Exhibit 6, Disclosure of Asserted Claims and Infringement Contentions for Defendant IBM Corp.,” submitted by the Plaintiff in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED, served on Sep. 14, 2009, 242 pages.
  • “Exhibit 7, Disclosure of Asserted Claims and Infringement Contentions for Defendant NEC Corp. Of America,” submitted by the Plaintiff in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED, served on Sep. 14, 2009, 166 pages.
  • “Exhibit 8, Disclosure of Asserted Claims and Infringement Contentions for Defendant Sun Microsystems, Inc.,” submitted by the Plaintiff in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED, served on Sep. 14, 2009, 243 pages.
  • “Exhibit 9, Disclosure of Asserted Claims and Infringement Contentions for Defendant Super Micro Computer, Inc.,” submitted by the Plaintiff in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED, served on Sep. 14, 2009, 220 pages.
  • “Disclosure of Plaintiff's Reduced List of Asserted Claims ,” submitted by the Plaintiff in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-00148-LED, served on Jul. 30, 2010, 6 pages.
  • “Memorandum Opinion and Order Construing Claim Terms and Denying Defendants' Motion for Partial Summary Judgment,” Issued by the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Aug. 2, 2010, 18 pages.
  • “Memorandum Opinion and Order Construing Claim Terms,” Issued by the U.S. District Court for the Eastern District of Texas, Tyler Division, Case No. 6:09-cv-148-LED, Document 602, Feb. 3, 2011, 12 pgs.
  • “Jury Verdict Form,” Returned by the Jury in the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Feb. 23, 2011, 2 pages.
  • “Final Judgement,” Issued by the U.S. District Court for the Eastern District of Texas, Case No. 6:09-cv-148-LED on Mar. 1, 2011, 1 page.
  • “Complaint for Patent Infringement,” Acqis v. Appro Int'l, Inc. et al., Case No. 6:09-cv-00148, filed Apr. 2, 2009, 13 pages.
  • “First Amended Complaint for Patent Infringement,” Acqis v. Appro Int'l, Inc. et al., Case No. 6:09-cv-00148, filed May 18, 2009, 14 pages.
  • “Defendant Clearcube Technology, Inc.'s Answer, Counterclaims to Acqis LLC's First Amended Complaint for Patent Infringement, and Jury Demand,” Case No. 6:08-cv-00148, filed Jul. 2, 2009, 28 pages.
  • “Defendant Nex Computers Technology, Inc.'s Answer to Acqis LLC's First Amended Complaint for Patent Infringement, and Jury Demand,” Case No. 6:09-cv-00148-LED, filed Jul. 8, 2009, 16 pages.
  • “Defendant Hitachi Ameirca, Ltd.'s, Answer to Acqis LLC's First Amended Complaint for Patent Infringement, and Affirmative Defenses and Counterclaims,” Case No. 6:09-cv-00148-LED, filed Jul. 8, 2009, 22 pages.
  • “Defendant International Business Machines Corp.'s Answer to Acqis LLC's First Amended Complaint, Affirmative Defenses, and Counterclaims,” Case No. 6:09-cv-148-LED, filed Jul. 8, 2009, 22 pages.
  • “Second Amended Complaint for Patent Infringement,” Acqis v. Appro Int'l, Inc. et al., Case No. 6:09-cv-00148, filed Jul. 22, 2009, 49 pages.
  • “Defendant Appro's Answer, Affirmative Defenses, and Counterclaims to Acqis LLC's Second Amended Complaint for Patent Infringement,” Case No. 6:09-cv-148, filed Aug. 5, 2009, 43 pages.
  • “Defendant International Business Machines Corp.'s Answer to Acqis LLC's Second Amended Complaint, Affirmative Defenses, and Counterclaims,” Case No. 6:09-cv-148-LED, filed Aug. 10, 2009, 28 pages.
  • “Defendant Super Micro Computer, Inc.'s Answer and Counterclaims to Acqis LLC's Second Amended Complaint for Patent Infringement,” Case No. 6:09-cv-148, filed Aug. 10, 2009, 96 pages.
  • “Defendant Sun Microsystems, Inc.'s Answer and Counterclaims to Acqis LLC's Second Amended Complaint for Patent Infringement,” Case No. 6:09-cv-148, filed Aug. 10, 2009, 95 pages.
  • “NEC Corporation of America's Answer, Affirmative Defenses, and Counterclaims to Acqis LLC's Second Amended Complaint for Patent Infringement,” Case No. 6:09-cv-00148-LED, filed Aug. 10, 2009, 38 pages.
  • “Answer to Plaintiff's Second Amended Complaint and Counterclaims of Defendant Fujitsu Computer Systems Corp., n/k/a/ Fujitsu America, Inc. To Acqis LLC's Second Amended Complaint for Patent Infringement,” Case No. 6:09-cv-00148-LED, filed Aug. 10, 2009, 34 pages.
  • “Answer, Affirmative Defenses, and Counterclaims of Defendant Hewlett-Packard Company to Acqis LLC's Second Amended Complaint for Patent Infringement,” Case No. 6:09-cv-148-LED, filed Aug. 10, 2009, 40 pages.
  • “Defendant Clearcube Technology, Inc.'s Answer, Counterclaims to Acqis LLC's Second Amended Complaint for Patent Infringement, and Jury Demand,” Case No. 6:08-cv-00148, filed Aug. 10, 2009, 39 pages.
  • “Dell's Answer and Counterclaims to Acqis LLC's Second Amended Complaint,” Case No. 6:09-cv-00148-LED, filed Aug. 10, 2009, 36 pages.
  • “Defendant Nex Computers Technology, Inc.'s Answer to Acqis LLC's Second Amended Complaint for Patent Infringement, and Jury Demand,” Case No. 6:09-cv-00148-LED, filed Aug. 10, 2009, 28 pages.
  • “Defendant Clearcube Technology, Inc.'s First Amended Answer, Counterclaims to Acqis LLC's Second Amended Complaint for Patent Infringement and Jury Demand,” Case No. 6:09-cv-00148, filed Aug. 11, 2009, 39 pages.
  • “Plaintiff Acqis LLC's Answer to Defendant Appro International, Inc.'s Counterclaims,” Case No. 6:09-00148-LED, filed Aug. 28, 2009, 16 pages.
  • “Defendant Clearcube Technology, Inc.'s Second Amended Answer Counterclaims to Acqis LLC's Second Amended Complaint for Patent Infringement and Jury Demand,” Case No. 6:09-Cv-00148, filed Aug. 31, 2009, 45 pages.
  • “Plaintiff Acqis LLC's Answer to Defendant International Business Machines Corp.'s Counterclaims,” Case No. 6:09-00148-LED, filed Sep. 2, 2009, 11 pages.
  • “Plaintiff Acqis LLC's Answer to Defendant Super Micro Computer, Inc.'s Counterclaims,” Case No. 6:09-00148-LED, filed Sep. 2, 2009, 15 pages.
  • “Plaintiff Acqis LLC's Answer to Defendant Sun Microsystems, Inc.'s Counterclaims,” Case No. 6:09-cv-00148-LED, filed Sep. 2, 2009, 14 pages.
  • “Plaintiff Acqis LLC's Answer to Defendant Dell Inc.'s Counterclaims,” Case No. 6:09-00148-LED, filed Sep. 2, 2009, 16 pages.
  • “Plaintiff Acqis LLC's Answer to Defendant Fujitsu Computer Systems Corp., N/K/A Fujitsu America, Inc.'s Counterclaims,” Case No. 6:09-00148-LED, filed Sep. 16, 2009, 7 pages.
  • “Plaintiff Acqis LLC's Answer to Defendant Hewlett-Packard Company's Counterclaims,” Case No. 6:09-00148-LED, filed Sep. 16, 2009, 14 pages.
  • “Plaintiff Acqis LLC's Answer to Defendant NEC Corporation of America's Counterclaims,” Case No. 6:09-00148-LED, filed Sep. 16, 2009, 8 pages.
  • “Defendant Clearcube Technology, Inc.'s Third Amended Answer to Acqis LLC's Second Amended Complaint for Patent Infringement and Jury Demand,” Case No. 6:09-cv-00148, filed Nov. 11, 2009, 26 pages.
  • “Defendant Clearcube Technology, Inc.'s Fourth Amended Answer to Acqis LLC's Second Amended Complaint for Patent Infringement and Jury Demand,” Case No. 6:09-cv-00148, filed Jan. 8, 2010, 26 pages.
  • “Dell's First Amended Answer and Counterclaims to Plaintiffs Second Amended Complaint,” Case No. 6:09-cv-00148-LED, filed Apr. 22, 2010, 38 pages.
  • “Plaintiff Acqis LLC's Answer to Defendant Dell Inc.'s First Amended Counterclaims,” Case No. 6:09-00148-LED, filed May 10, 2010, 16 pages.
  • “Affidavit of Timothy P. Cremen in Support of NEC Corporation of America's Opposition to Plaintiffs Motion to Dismiss and Strike,” Case No. 6:09-cv-00148-LED, filed Oct. 9, 2009, 4 pages.
  • “Comparison [by NEC] of Rejected Elements in Office Action and Elements of Exemplary Claims of Acqis's Patents,” Case No. 6:09-cv-00148-LED, filed Oct. 9, 2009, 7 pages.
  • “Defendant NEC Corporation of America's Opposition to Plaintiffs Motion to Dismiss and Motion to Strike,” Case No. 6:09-cv-00148-LED, filed Oct. 9, 2010, 36 pages.
  • “Motion to Dismiss Counterclaim Pursuant to Rule 12(b)(6) and Motion to Strike Affirmative Defense Pursuant to Rule 12(f),” Case 6:09-00148-LED, filed Sep. 16, 2009, 18 pages.
  • “Transcript of Videotaped Deposition of William Mangione-Smith,” taken by the Defendants in connection with Case No. 6:09-cv-148-LED in the U.S. District Court for the Eastern District of Texas, Sep. 9, 2010, 192 pages.
  • “Defendant Sun Microsystems, Inc.'s Responses and Objections to Plaintiff Acqis LLC's Second Set of Common Interrogatories,” Case No. 6:09-cv-00148-LED, filed May 12, 2010, 9 pages.
  • “Plaintiff Acqis LLP's Objections and Responses to Defendants' First Set of Interrogatories,” Case No. 6:09-cv-00148-LED, filed Aug. 5, 2010, 21 pages.
  • “Plaintiff Acqis LLP's Objections and Responses to Defendants' Third Set of Interrogatories,” Case No. 6:09-cv-00148-LED, filed Aug. 5, 2010, 13 pages.
  • “Plaintiff Acqis LLP's First Supplemental Objections and Responses to Defendants' Third Set of Interrogatories,” Case No. 6:09-cv-00148-LED, filed Aug. 5, 2010, 14 pages.
  • “Declaration of Jennifer Chen in Support of Defendants' Motion for Leave to Amend Defendants' Invalidity Contentions,” Case No. 6:09-cv-00148-LED, Aug. 5, 2010, 3 pages.
  • Excerpts of Transcript of “Videotaped Deposition of William W.Y. Chu,” taken by the Defendants in connection with Case No. 6:09-cv-148-LED in the U.S. District Court for the Eastern District of Texas, Jun. 7, 2010, 20 pages.
  • “Declaration of Monty McGraw in Support of Defendants' Motion for Leave to Amend Defendants' Invalidity Contentions,” Case No. 6:09-cv-00148-LED, Aug. 5, 2010, 3 pages.
  • “Plaintiff's Opening Brief Regarding Claim Construction,” Case No. 6:09-cv-00148-LED, filed Jun. 1, 2010, 35 pages.
  • “Declaration of Carolyn V. Juarez in Support of Plaintiff Acqis LLC's Opening Brief Regarding Claim Construction,” Case No. 6:09-cv-00148-LED, filed Jun. 1, 2010, 3 pages.
  • “Defendant's Brief in Response to Plaintiffs Opening Brief Regarding Claim Construction,” Case No. 6:09-cv-00148-LED, filed Jun. 15, 2010, 40 pages.
  • “Proposed Claim Construction Statement,” Case No. Case No. 6:09-cv-00148-LED, filed Jun. 15, 2010, 39 pages.
  • “Claim Chart for International Business Machines Corp.,” Case No. 6:09-cv-00148-LED, filed Jun. 15, 2010, 12 pages.
  • “Acqis LLC's Disclosure of Proposed Terms and Claim Elements for Construction Pursuant to Patent Rule 4-1,” Case No. 6:09-cv-00148-LED, filed Mar. 5, 2010, 3 pages.
  • “Defendant's List of Proposed Terms and Claim Elements for Construction,” Case No. 6:09-cv-00148-LED, filed Mar. 5, 2010, 15 pages.
  • “Defendant's Amended List of Proposed Terms and Claim Elements for Construction,” Case No. 6:09-cv-00148-LED, filed Mar. 31, 2010, 11 pages.
  • “Defendant's Corrected List of Proposed Terms and Claim Elements for Construction,” Case No. 6:09-cv-00148-LED, filed Apr. 2, 2010, 9 pages.
  • “Acqis, LLC's P.R.-4-2 Disclosure of Preliminary Claim Constructions and Extrinsic Evidence,” Case No. 6:09-cv-00148-LED, filed Apr. 14, 2010, 10 pages.
  • “Defendant's P.R.-4-2 Disclosure of Preliminary Claim Constructions and Extrinsic Evidence,” Case No. 6:09-cv-00148-LED, filed Apr. 14, 2010, 16 pages.
  • “Joint Claim Construction Statement,” Case No. 6:09-cv-00148-LED, filed Apr. 30, 2010, 46 pages.
  • “Amended Joint Claim Construction Statement,” Case No. 6:09-cv-00148-LED, filed May 5, 2010, 44 pages.
  • “Corrected p. 13 of Plaintiff's Opening Brief Concerning Claim Construction (D.I. 261),” Case No. 6:09-cv-00148-LED, filed Jun. 2, 2010, 2 pages.
  • “Plaintiff's Reply Brief Regarding Claim Construction,” Case No. 6:09-cv-00148-LED, filed Jun. 28, 2010, 14 pages.
Patent History
Patent number: RE42984
Type: Grant
Filed: Sep 16, 2009
Date of Patent: Nov 29, 2011
Assignee: Acqis Technology, Inc. (Mountain View, CA)
Inventor: William W. Y. Chu (Los Altos, CA)
Primary Examiner: Hosuk Song
Attorney: Cooley LLP
Application Number: 12/561,138
Classifications
Current U.S. Class: Access Control Or Authentication (726/2); Access Control (726/27); Via Power Supply (726/36)
International Classification: G06F 17/30 (20060101); G06F 1/26 (20060101);