throbber
IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`Docket No.: 31436/43994
`
`(PATENT)
`
`In re Patent Application of:
`Michael Tasler
`
`Application N0.: 11/467,073
`
`Confirmation N0.: 3012
`
`Filed: August 24, 2006
`
`For:
`
`ANALOG DATA GENERATING AND
`PROCESSING DEVICE HAVING A MULTI-
`
`USE AUTOMATIC PROCESSOR (as
`amended)
`
`Art Unit: 2181
`
`Examiner: C. K. Lee
`
`AMENDMENT
`
`MS Amendment
`Commissioner for Patents
`PO. Box 1450
`
`Alexandria, VA 22313—1450
`
`Dear Sir:
`
`INTRODUCTORY COMMENTS
`
`Please enter this amendment in response to the Office Action mailed from the USPTO on
`
`February 24, 2009. A petition and fee for a three-month extension of time are filed herewith.
`
`Amendments to the Title and the Drawings are on page 2 of this paper.
`
`Amendments to the Specification start on page 2 of this paper.
`
`The Listing of the Claims begins on page 8 of this paper.
`
`Remarks/Arguments begin on page 21 of this paper.
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 1
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 1
`
`

`

`Application No. 11/467,073
`Amendment
`
`Date August 13, 2009
`
`Amendment T0 The Title:
`
`Docket No.: 31436/43994
`
`Please amend the title of this application to read as follows: Analog Data Generating
`
`And Processing Device Having A Multi—Use Automatic Processor.
`
`Amendment To The Drawings:
`
`Replacement drawings are submitted herewith to add a lead line in Figure 2 from number
`
`1260 to the EFF box as noted in the Office Action. Approval of the replacement drawings is
`
`earnestly solicited.
`
`Amendments T0 The Specification:
`
`1.
`
`Replace paragraph [0001] of the specification in its entirety with the following
`
`paragraph:
`
`[000]]
`
`This application is a continuation of application Ser. No. 1 1/078,778, filed March
`
`11, 2005, now eHEenEl-ypending expressly abandoned, which is a continuation of application
`
`Ser. No. 10/219,105, filed August 15, 2002, now Pat. No. 6,895,449, which is a divisional of
`
`application Ser. No. 09/331,002, filed Jun. 14, 1999, now Pat. No. 6,470,399.
`
`2.
`
`Replace paragraph [0009] of the specification in its entirety with the following
`
`paragraph:
`
`[0009]
`
`A solution to this problem is offered by the interface devices of IOtech (business
`
`address: 25971 Cannon Road, Cleveland, Ohio 44146, USA) which are suitable for laptops
`
`such as the WaveBook/512 (registered trademark). The interface devices are connected by
`
`means of a plug-in card, approximately the size of a credit card, to the PGMGLArpersonal
`
`computer memory card association {PCMIAQ interface which is now a standard feature in
`
`laptops. The plug-in card converts the PCMCIA interface into an interface known in the art
`
`’7A
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 2
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 2
`
`

`

`Application No. 11/467,073
`Amendment
`
`Date August 13, 2009
`
`Docket No.: 31436/43994
`
`as IrEEEInstitute of Electrical and Electronics {IEEE[ 1284. The said plug-in card provides a
`
`special printer interface which is enhanced as regards the data transfer rate and delivers a
`
`data transfer rate of approximately 2 MBps as compared with a rate of approx. 1 MBps for
`
`known printer interfaces. The known interface device generally consists of a driver
`
`component, a digital signal processor, a buffer and a hardware module which terminates in a
`
`connector to which the device whose data is to be acquired is attached. The driver
`
`component is attached directly to the enhanced printer interface thus permitting the known
`
`interface device to establish a connection between a computer and the device whose data is to
`
`be acquired.
`
`3.
`
`Replace paragraph [0013] of the specification in its entirety with the following
`
`paragraph:
`
`[0013]
`
`The specialist publication IBM Technical Disclosure Bulletin, Vol. 38, No. 05,
`
`page 245; "Communication Method between Devices through FDD Interface" discloses an
`
`interface which connects a host device to a peripheral device via a floppy disk drive
`
`interface. The interface consists in particular of an address generator, an Wmodifled
`
`frequency modulation [MFM] encoder/decoder, a serial/parallel adapter and a format signal
`
`generator. The interface makes it possible to attach not only a floppy disk drive Mbut
`
`also a further peripheral device to the FDD host controller of a host device. The host device
`
`assumes that a floppy disk drive is always attached to its floppy disk drive controller and
`
`communication is initiated if the address is correct. However, this document contains no
`
`information as to how communication should be possible if the interface is connected to a
`
`multi-purpose interface instead of to a floppy disk drive controller.
`
`4.
`
`Replace paragraph [0015] of the specification in its entirety with the following
`
`paragraph:
`
`[0015]
`
`The present invention is based on the finding that both a high data transfer rate
`
`and host device—independent use can be achieved if a driver for an input/output device
`
`customary in a host device, normally present in most commercially available host devices, is
`
`utilized. Drivers for input/output devices customary in a host device which are found in
`
`3
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 3
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 3
`
`

`

`Application No. 11/467,073
`Amendment
`
`Date August 13, 2009
`
`Docket N0.: 31436/43994
`
`practically all host devices are, for example, drivers for hard disks, for graphics devices or for
`
`printer devices. As however the hard disk interfaces in common host devices which can be,
`
`for example, IBM PCs—personal computers [PCs [, IBM-compatible PCs, Commodore PCs,
`
`Apple computers or even workstations, are the interfaces with the highest data transfer rate,
`
`the hard disk driver is utilized in the preferred embodiment of the interface device of the
`
`present invention. Drivers for other storage devices such as floppy disk drives, GD-
`
`R—OMcompact disk read-only memory [CD-ROM] drives or tape drives could also be utilized
`
`in order to implement the interface device according to the present invention.
`
`5.
`
`Replace paragraph [0016] of the specification in its entirety with the following
`
`paragraph:
`
`[0016]
`
`As described in the following, the interface device according to the present
`
`invention is to be attached to a host device by means of a multi-purpose interface of the host
`
`device which can be implemented, for example, as an SGS—I—small computer systems interface
`
`{LSD interface or as an enhanced printer interface. Multi—purpose interfaces comprise both
`
`an interface card and specific driver software for the interface card. The driver software can
`
`be designed so that it can replace the BIOS—basic input/output system [B108] driver routines.
`
`Communication between the host device and the devices attached to the multi-purpose
`
`interface then essentially takes place by means of the specific driver software for the multi—
`
`purpose interface and no longer primarily by means of BIOS routines of the host device.
`
`Recently however drivers for multi-puipose interfaces can also already be integrated in the
`
`BIOS system of the host device as, alongside classical input/output interfaces, multi—purpose
`
`interfaces are becoming increasingly common in host devices. It is of course also possible to
`
`use BIOS routines in parallel with the specific driver software for the multi-purpose
`
`interface, if this is desired.
`
`6.
`
`Replace paragraph [0023] of the specification in its entirety with the following
`
`paragraph:
`
`[0023]
`
`Communication between the host system or host device and the interface device is
`
`based on known standard access commands as supported by all known operating systems
`
`4
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 4
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 4
`
`

`

`Application No. 11/467,073
`Amendment
`
`Date August 13, 2009
`
`Docket N0.: 31436/43994
`
`(e. g. DQ—S—DOSQ, Windews—Windows®, Uni-)eUniXQ). Preferably, the interface device
`
`according to the present invention simulates a hard disk with a root directory whose entries
`
`are "virtual" files which can be created for the most varied functions. When the host device
`
`system with which the interface device according to the present invention is connected is
`
`booted and a data transmit/receive device is also attached to the interface device 10, usual
`
`BIOS routines or multi-purpose interface programs issue an instruction, known by those
`
`skilled in the art as the INQUIRY instruction, to the input/output interfaces in the host
`
`device. The digital signal processor 13 receives this inquiry instruction via the first
`
`connecting device and generates a signal which is sent to the host device (not shown) again
`
`via the first connecting device 12 and the host line 11. This signal indicates to the host
`
`device that, for example, a hard disk drive is attached at the interface to which the INQUIRY
`
`instruction was sent. Optionally, the host device can send an instruction, known by those
`
`skilled in the art as "Test Unit Ready", to the interface device to request more precise details
`
`regarding the queried device.
`
`7.
`
`Replace paragraph [0027] of the specification in its entirety with the following
`
`paragraph:
`
`[0027]
`
`In addition to the digital signal processor instruction memory, which comprises
`
`the operating system of the digital signal processor and can be implemented as an EPROM
`
`erasable programmable read-only memory 1EPROM] or EE—PRQMelectrically erasable
`
`programmable read-only memory (EEPROM), the memory means 14 can have an additional
`
`buffer for purposes of synchronizing data transfer from the data transmit/receive device to
`
`the interface device 10 and data transfer from the interface device 10 to the host device.
`
`8.
`
`Replace paragraph [0028] of the specification in its entirety with the following
`
`paragraph:
`
`[0028]
`
`Preferably, the buffer is implemented as a fast random access memory or R—A—M
`
`random access memory [RAM] buffer.
`
`9.
`
`Replace paragraph [0030] of the specification in its entirety with the following
`
`paragraph:
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 5
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 5
`
`

`

`Application No. 11/467,073
`Amendment
`
`Date August 13, 2009
`
`Docket No.: 31436/43994
`
`[0030]
`
`As a result of the option of storing any files in agreed formats in the memory
`
`means 14 of the interface device 10, taking into account the maximum capacity of the
`
`memory means, any enhancements or even completely new functions of the interface device
`
`10 can be quickly implemented. Even files executable by the host device, such as batch files
`
`or executable files (BAT or EXE files), and also help files can be implemented in the
`
`interface device, thus achieving independence of the interface device 10 from any additional
`
`software (with the exception of the BIOS routines) of the host device. On the one hand, this
`
`avoids licensing and/or registration problems and, on the other hand, installation of certain
`
`routines which can be frequently used, for example an FFJEfast Fourier transformation gFFTg
`
`routine to examine acquired time-domain data in the frequency domain, is rendered
`
`unnecessary as the EXE files are already installed on the interface device 10 and appear in
`
`the virtual root directory, by means of which the host device can access all programs stored
`
`on the interface device 10.
`
`10.
`
`Replace paragraph [0041] of the specification in its entirety with the following
`
`paragraph:
`
`[0041]
`
`The complete interface device 10 is supplied with power by an external AGLDG
`
`alternating current to direct current (AC/DC: converter 2230 which delivers a digital supply
`
`voltage of .+—.5 V and is attached to a DGILDGdirect current to direct current {DC/DC}
`
`converter 2240 which can deliver analog supply voltages of .+-.5 V and .+-.15 V as required
`
`for the interface device 10. Further, the DGLDGdirect current to direct current (DC/DC)
`
`converter controls a precision voltage reference 2250 which controls the 8 Bayonet Neill
`
`Concelman {ENC} inputs 1505 and the ADC 1530 as well as a digital/analog converter
`
`(DAC) 2260 which permits, via an output amplifier block with 4 output amplifiers 2270 and
`
`a 9-pin connector 2280, analog output direct from the DSP 1300 to an output device, e. g.
`
`printer device or monitor device, which can be attached via the 9—pin connector 2280, thus
`
`providing the option of monitoring the data transferred to the host device or also, for
`
`example, of viewing an FFT to obtain rapid and comprehensive data analysis without using
`
`processor time of the host device.
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 6
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 6
`
`

`

`Application No. 11/467,073
`Amendment
`
`Date August 13, 2009
`
`Docket N0.: 31436/43994
`
`11.
`
`Replace paragraph [0048] of the specification in its entirety with the following
`
`paragraph:
`
`[0048]
`
`As described above, the interface device 10 is supplied with power by means of
`
`an external AC/DC adapter which has a universal power input (85-264 VAC, 47—63 Hz ).
`
`Interference suppression complies with the standards EN 55022, curve B and FFC, Class B9.
`
`Further, it is also in accordance with international safety regulationsWGSA. TuV
`
`1Technischer Uberwachongsverein), UL {Underwriters Laboratories !. CSA {Canadian
`
`Standard Association). The interface device 10 is externally shielded and achieves a value of
`
`55 dB at 30-60 MHz and a value of approximately 40 dB at 1 GHz, and therefore complies
`
`with the Wmilitary standarsd {MILSTD1285—1 standard.
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 7
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 7
`
`

`

`Application No. 11/467,073
`Amendment
`
`Date August 13, 2009
`
`Docket No.: 31436/43994
`
`Amendments T0 The Claims:
`
`Please cancel claims 1-236 and please add new claims 237-322 as follows:
`
`1—236. (cancelled).
`
`237.
`
`(new) An analog data generating and processing device (ADGPD), comprising:
`
`an input/output (i/o) port;
`
`a program memory;
`
`a data storage memory;
`
`a sensor designed to transmit data;
`
`a processor operatively interfaced with the i/o port, the program memory, the data
`
`storage memory and the sensor;
`
`wherein the processor is adapted to be involved in a data generation process by
`
`which the sensor generates analog data, the analog data is processed, and the processed analog
`
`data is stored in the data storage memory as at least one file of digitized analog data;
`
`wherein the processor also is adapted to be involved in an automatic recognition
`
`process in which, when the i/o port is operatively interfaced with a multi-purpose interface of a
`
`computer, the processor executes at least one instruction set stored in the program memory and
`
`thereby causes at least one parameter which provides identification information regarding the
`
`ADGPD to be automatically sent through the i/o port and to the multi-purpose interface of the
`
`computer (a) without requiring any end user to load any software onto the computer at any time,
`
`(b) without requiring any end user to interact with the computer to set up a file system in the
`
`ADGPD at any time, (c) before a time when the computer is able to receive the at least one file
`
`of digitized analog data from the data storage memory and (d) regardless of the identity of a
`
`8
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 8
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 8
`
`

`

`Application No. 11/467,073
`Amendment
`
`Date August 13, 2009
`
`manufacturer of the computer; and
`
`Docket N0.: 31436/43994
`
`wherein the processor is further adapted to be involved in an automatic file
`
`transfer process in which, when the i/o port is operatively interfaced with the multi-purpose
`
`interface of the computer, and after the at least one parameter has been received by the multi-
`
`purpose interface of the computer, the processor executes at least one other instruction set stored
`
`in the program memory and thereby causes the at least one file of digitized analog data to be
`
`transferred to the computer regardless of the identity of the manufacturer of the computer and
`
`without requiring any user-loaded file transfer enabling software to be loaded on or installed in
`
`the computer at any time.
`
`238.
`
`(new) The ADGPD of claim 237, wherein the i/o port, the program memory, the
`
`data storage memory, and the processor form an interface device that is designed to have the
`
`analog data transferred to it from the sensor.
`
`239.
`
`(new) The ADGPD of claim 238, wherein the interface device comprises a
`
`portable interface device.
`
`240.
`
`(new) The ADGPD of claim 238, wherein the interface device comprises a
`
`flexible interface device.
`
`241.
`
`(new) The ADGPD of claim 238, wherein the interface device comprises a
`
`universal interface device.
`
`242.
`
`(new) The ADGPD of claim 238, wherein the interface device comprises a stand
`
`alone interface device.
`
`243.
`
`(new) The ADGPD of claim 238, wherein the interface device includes a parallel
`
`logic circuit.
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 9
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 9
`
`

`

`Application No. 11/467,073
`Amendment
`
`Date August 13, 2009
`
`Docket No.: 31436/43994
`
`244.
`
`(new) The ADGPD of claim 238, wherein the interface device includes a SCSI
`
`interface circuit.
`
`245.
`
`(new) The ADGPD of claim 238, wherein the interface device is designed so that
`
`the sensor is detachable from the interface device.
`
`246.
`
`(new) The ADGPD of claim 238, wherein the interface device allows for a
`
`plurality of different data transmit devices to be attached thereto and detached therefrom.
`
`247.
`
`(new) The ADGPD of claim 238, wherein the sensor is designed to be readily
`
`disconnected from the interface device.
`
`248.
`
`(new) The ADGPD of claim 238, wherein the interface device is designed so that
`
`a user can attach the sensor to or detach the sensor from the interface device.
`
`249.
`
`(new) The ADGPD of claim 237, wherein the i/o port comprises a parallel port.
`
`250.
`
`(new) The ADGPD of claim 237, wherein the i/o port comprises a SCSI
`
`connector.
`
`251.
`
`(new) The ADGPD of Claim 237, wherein the i/o port is adapted to be interfaced
`
`with a multi-purpose interface of an external computing device only by means of a cable.
`
`252.
`
`(new) The ADGPD of claim 237, wherein the i/o port is adapted to be physically
`
`connected to a multi-purpose interface of an external computing device by a cable.
`
`253.
`
`(new) The ADGPD of claim 237, wherein the sensor comprises a data
`
`transmit/receive device.
`
`254.
`
`(new) The ADGPD of claim 253, wherein the data transmit/receive device is
`
`designed for two—way communication with a host device.
`
`255.
`
`(new) The ADGPD of claim 253, wherein the data transmit/receive device is
`
`10
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 10
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 10
`
`

`

`Application No. 11/467,073
`Amendment
`
`Date August 13, 2009
`
`Docket No.: 31436/43994
`
`designed for one-way or two-way communication with a host device.
`
`256.
`
`(new) The ADGPD of claim 253, wherein the data transmit/receive device is
`
`designed to receive data from a host device.
`
`257.
`
`(new) The ADGPD of claim 237, wherein the processor is designed so that the
`
`sensor is detach able therefrom.
`
`258.
`
`(new) The ADGPD of claim 237, wherein the processor allows for a plurality of
`
`different data transmit devices to be attached thereto and detached therefrom.
`
`259.
`
`(new) The ADGPD of claim 237, wherein the sensor is designed to be readily
`
`disconnected from the processor.
`
`260.
`
`(new) The ADGPD of claim 237, wherein the processor is designed so that a user
`
`can attach the sensor to or detach the sensor therefrom.
`
`261.
`
`(new) The ADGPD of claim 237, wherein the sensor comprises a multimeter.
`
`262.
`
`(new) The ADGPD of claim 237, wherein the sensor includes at least first and
`
`second transducers both of which are designed to transmit data.
`
`263.
`
`(new) The ADGPD of claim 237, wherein the at least one parameter is consistent
`
`with the ADGPD being an information storage device other than a magnetic floppy disk drive.
`
`264.
`
`(new) The ADGPD of claim 237, wherein the at least one parameter is consistent
`
`with the ADGPD being a mass storage device.
`
`265.
`
`(new) The ADGPD of claim 237, wherein the at least one parameter is consistent
`
`with the ADGPD being responsive to a SCSI inquiry command.
`
`266.
`
`(new) The ADGPD of claim 237, wherein the at least one parameter is not
`
`consistent with the true nature of the ADGPD.
`
`11
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 11
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 11
`
`

`

`Application No. 11/467,073
`Amendment
`
`Date August 13, 2009
`
`Docket No.: 31436/43994
`
`267.
`
`(new) The ADGPD of claim 237, wherein the at least one parameter does not
`
`indicate that the ADGPD includes the sensor.
`
`268.
`
`(new) The ADGPD of Claim 237, wherein the at least one parameter is consistent
`
`with the ADGPD being an input/output device.
`
`269.
`
`(new) The ADGPD of claim 237, wherein the at least one parameter is consistent
`
`with the ADGPD being an input/output device located within an interior of a housing of a
`
`personal computing device.
`
`270.
`
`(new) The ADGPD of claim 237, wherein the at least one parameter is consistent
`
`with the ADGPD being adapted to operate in a manner consistent with a hard disk drive.
`
`271.
`
`(new) The ADGPD of claim 237, wherein the at least one parameter is consistent
`
`with the ADGPD being a hard disk drive.
`
`272.
`
`(new) The ADGPD of claim 237, wherein the at least one parameter is consistent
`
`with the ADGPD being an input/output device that is customary in a host device.
`
`273.
`
`(new) The ADGPD of Claim 237, wherein the at least one parameter is consistent
`
`with the ADGPD being responsive to commands issued from a customary driver.
`
`274.
`
`(new) The ADGPD of claim 237, wherein the data storage memory comprises a
`
`temporary memory.
`
`275.
`
`(new) The ADGPD of claim 237, wherein the data storage memory comprises a
`
`semiconductor based memory.
`
`276.
`
`(new) The ADGPD of claim 237, wherein the data storage memory comprises
`
`random acces S memory.
`
`277.
`
`(new) The ADGPD of claim 237, wherein the data storage memory comprises a
`
`12
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 12
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 12
`
`

`

`Application No. 11/467,073
`Amendment
`
`Date August 13, 2009
`
`single memory device.
`
`Docket N0.: 31436/43994
`
`278.
`
`(new) The ADGPD of claim 237, wherein the program memory comprises
`
`electronically programmable read only memory.
`
`279.
`
`(new) The ADGPD of claim 237, wherein the processor is adapted to, when the
`
`i/o port is operatively interfaced with the multi-purpose interface of the computer, and after the at
`
`least one parameter has been sent to the multi-purpose interface of the computer, execute at least
`
`one set of computer code stored in the program memory and thereby cause ADGPD file system
`
`information to be automatically sent to the i/o port (a) without requiring any end user to load any
`
`software onto the computer at any time, (b) without requiring any end user to interact with the
`
`computer to set up a file system in the ADGPD at any time , (c) before a time when the computer
`
`is able to receive the at least one file of digitized analog data from the data storage memory and
`
`(d) regardless of the identity of a manufacturer of the computer.
`
`280.
`
`(new) The ADGPD of claim 279, wherein the ADGPD file system information
`
`comprises at least an indication of the type of a file system that is used to store the at least one
`
`file of digitized analog data in the data storage memory.
`
`281.
`
`(new) The ADGPD of claim 279, wherein the at least one parameter is consistent
`
`with the ADGPD being an information storage device other than a magnetic floppy disk drive.
`
`282.
`
`(new) The ADGPD of claim 281, wherein the at least one parameter is consistent
`
`with the ADGPD being a mass storage device.
`
`283.
`
`(new) The ADGPD of claim 282,
`
`wherein the processor and the program memory are configured to cause, after the
`
`at least one parameter has been sent to the i/o port, file allocation table information to be sent to
`
`13
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 13
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 13
`
`

`

`Application No. 11/467,073
`Amendment
`
`Date August 13, 2009
`
`the i/o port,
`
`Docket N0.: 31436/43994
`
`wherein the processor and the program memory are configured to cause a virtual
`
`boot sequence to be sent to the i/o port which includes at least information that is representative
`
`of a number of sectors of a storage disk, and
`
`wherein the file allocation table information includes at least a start location of a
`
`file allocation table.
`
`284.
`
`(new) The ADGPD of claim 283, wherein the at least one parameter is consistent
`
`with the ADGPD being adapted to operate in a manner consistent with a hard disk drive.
`
`285.
`
`(new) The ADGPD of claim 284, wherein the at least one parameter is consistent
`
`with the ADGPD being a hard disk drive.
`
`286.
`
`(new) The ADGPD of claim 237, wherein the processor includes a single central
`
`processing unit.
`
`287.
`
`(new) The ADGPD of claim 237, wherein the program memory comprises a
`
`single memory device.
`
`288.
`
`(new) The ADGPD of claim 237, wherein the program memory is formed in a
`
`single chip.
`
`289.
`
`(new) The ADGPD of claim 237, wherein the processor comprises a
`
`microprocessor.
`
`290.
`
`(new) The ADGPD of claim 237, wherein the processor comprises a single
`
`microprocessor.
`
`291.
`
`(new) The ADGPD of claim 237, wherein the processor comprises a digital
`
`signal processor.
`
`14
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 14
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 14
`
`

`

`Application No. 11/467,073
`Amendment
`
`Date August 13, 2009
`
`Docket N0.: 31436/43994
`
`292.
`
`(new) The ADGPD of claim 237, wherein the processor comprises a single
`
`digital signal processor.
`
`293.
`
`(new) The ADGPD of claim 237, wherein the processor and the program
`
`memory are configured to initiate a process by which the at least one file of digitized analog data
`
`stored in the data storage memory are directly transferred to an input/output device by means of
`
`the i/o port.
`
`294.
`
`(new) The ADGPD of claim 293, wherein the processor and the program
`
`memory are adapted to allow an aspect of operation of the ADGPD other than the transfer of at
`
`least some of the at least one file of digitized analog data from the data storage memory to the i/o
`
`port to be controlled by means of the computer.
`
`295.
`
`(new) The ADGPD of claim 237, wherein the ADGPD comprises at least a
`
`portion of a medical device.
`
`296.
`
`(new) The ADGPD of claim 237, wherein the ADGPD comprises at least a
`
`portion of a data acquisition system.
`
`297.
`
`(new) The ADGPD of claim 237, wherein the ADGPD is designed for use with
`
`an external computing device that has an operating system that is designed by a particular
`
`software company.
`
`298.
`
`(new) The ADGPD of claim 237, wherein the processor is adapted to, when it is
`
`involved in the automatic recognition process, to execute the at least one instruction set to
`
`thereby directly cause the at least one parameter regarding the ADGPD to be automatically sent.
`
`299.
`
`(new) The ADGPD of claim 237, wherein the processor is adapted to be
`
`employed in the automatic recognition process.
`
`15
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 15
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 15
`
`

`

`Application No. 11/467,073
`Amendment
`
`Date August 13, 2009
`
`Docket No.: 31436/43994
`
`300.
`
`(new) The ADGPD of claim 237, wherein the processor is adapted to be directly
`
`involved in all aspects of the automatic recognition process.
`
`301.
`
`(new) The ADGPD of claim 237, wherein the processor is adapted to be
`
`employed in the data generation process.
`
`302.
`
`(new) The ADGPD of claim 237, wherein the processor is adapted to be directly
`
`involved in all aspects of the data generation process.
`
`303.
`
`(new) The ADGPD of claim 237, wherein the analog data is, when the analog
`
`data generation process takes place, processed by being subject to a fast Fourier transform.
`
`304.
`
`(new) The ADGPD of claim 237, wherein the processed analog data is stored in
`
`the data storage memory as only one file of digitized analog data.
`
`305.
`
`(new) The ADGPD of claim 237, wherein the ADGPD is designed so that both
`
`the analog data generation and automatic file transfer processes, when they occur, take place
`
`only after the automatic recognition process has been executed.
`
`306.
`
`(new) The ADGPD of Claim 237, wherein the analog data generation and
`
`automatic file transfer processes, when they occur, at least partially overlap in time.
`
`307.
`
`(new) The ADGPD of claim 237, wherein the ADGPD is designed so that the
`
`analog data generation process, when it occurs, takes place only after the i/o port is interfaced
`
`with the computer.
`
`308.
`
`(new) The ADGPD of claim 237, wherein the sensor is designed for two-way
`
`communication with the computer.
`
`309.
`
`(new) The ADGPD of claim 237, wherein the sensor is designed for one—way or
`
`two-way communication with the computer.
`
`16
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 16
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 16
`
`

`

`Application No. 11/467,073
`Amendment
`
`Date August 13, 2009
`
`Docket No.: 31436/43994
`
`310.
`
`(new) The ADGPD of claim 237, wherein the sensor is designed to receive data
`
`from the computer.
`
`311.
`
`(new) The ADGPD of claim 237, wherein the sensor is designed to receive
`
`signals from the computer.
`
`312.
`
`(new) The ADGPD of claim 237, wherein the ADGPD is designed so that at least
`
`one aspect of how the ADGPD creates the at least one file of digitized analog data can be
`
`controlled by means of commands that are is sueable from a source external to the ADGPD.
`
`313.
`
`(new) The ADGPD of claim 312, wherein the ADGPD is designed so that the at
`
`least one aspect is controlled by means of a configuration file.
`
`314.
`
`(new) The ADGPD of claim 237, wherein the ADGPD is designed to be
`
`responsive to a test unit ready command.
`
`315.
`
`(new) The ADGPD of claim 237, wherein the set of instructions executed by the
`
`processor in the automatic recognition process is stored in a single memory device.
`
`316.
`
`(new) The ADGPD of Claim 237, wherein the set of instructions executed by the
`
`processor in the automatic file transfer process is stored in a single memory device.
`
`317.
`
`(new) A combination comprising the ADGPD of claim 237 and a computer.
`
`318.
`
`(new) The combination of claim 317, wherein the computer includes a driver for
`
`an input/output device customary in a host device.
`
`319.
`
`(new) The combination of claim 317, wherein the computer includes at least one
`
`customary driver.
`
`320.
`
`(new) The combination of claim 317, wherein the computer includes at least one
`
`driver for an input/output device customary in a host device.
`
`17
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 17
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 17
`
`

`

`Application No. 11/467,073
`Amendment
`
`Date August 13, 2009
`
`Docket No.: 31436/43994
`
`321.
`
`(new) An analog data generating and processing device (ADGPD), comprising:
`
`an input/output (i/o) port;
`
`a program memory;
`
`a data storage memory;
`
`a sensor designed to transmit data;
`
`a processor operatively interfaced with the i/o port, the program memory, the data
`
`storage memory and the sensor;
`
`wherein the processor is adapted to be involved in a data generation process by
`
`which the sensor generates analog data, the analog data is processed, and the processed analog
`
`data is stored in the data storage memory as at least one file of digitized analog data;
`
`wherein the processor also is adapted to be involved in an automatic recognition
`
`process in which, when the i/o port is operatively interfaced with a multi-purpose interface of a
`
`computer, the processor executes at least one instruction set stored in the program memory and
`
`thereby causes at least one parameter which provides identification information regarding the
`
`ADGPD to be automatically sent through the i/o port and to the multi-purpose interface of the
`
`computer (a) without requiring any end user to load any software onto the computer at any time,
`
`(b) without requiring any end user to interact with the computer to set up a file system in the
`
`ADGPD at any time, (c) before a time when the computer is able to receive the at least one file
`
`of digitized analog data from the data storage memory and (d) regardless of the identity of a
`
`manufacturer of the computer;
`
`wherein the processor is adapted to, when the i/o port is operatively interfaced
`
`with the multi-purpose interface of the computer, and after the at least one parameter has been
`
`18
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 18
`
`Papst Licensing GmbH & Co. KG - Exhibit 2009, p. 18
`
`

`

`Application No. 11/467,073
`Amendment
`
`Date August 13, 2009
`
`Docket No.: 31436/43994
`
`sent to a multi-purpose interface of the computer, execute at l

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket