`v.
`2009
`
`1207
`
`
`Petitioner Translation
`
`(19) Japan Patent Office (JP)
`
`Patent Owner Translation
`
`(19) JAPAN PATENT OFFICE (JP)
`
`(12) Official Gazette of Unexamined Patent Applications
`(A)
`
`(11) Japanese Unexamined Patent Application Publication
`Number
`
`(11) Patent Application Publication Number: H4‐15853
`
`(43) Patent Application Publication Date:
`1992
`
`January 21,
`
`Identification Code
`(51) Int. Cl.5
`Nos. G 06 F 13/36
`320
`A
`
`Internal File
`7052‐5B
`
`Request for Examination: Received
`
`Number of Claims: 1
`
`(Total of 6 Pages)
`
`(54) Title of the Invention: SCSI Device Converter
`
`(21)
`
`(22)
`
`Application Number:
`
`H2‐120493
`
`Application Date: May 9, 1990
`
`(12) JAPANESE UNEXAMINED PATENT
`
`APPLICATION PUBLICATION (A) H4‐15853
`
`(51) INT. CL.5 IDENTIFICATION CODES JPO FILE
`NUMBERS
`(43) PUBLICATION DATE JANUARY
`21, 1992
`
`G 06 F 13/36 320 A 7052—5B
`
`
`
`
`
`REQUEST FOR EXAMINATION: REQUESTED
`NUMBER OF CLAIMS: 1 (TOTAL OF 6 PAGES)
`
`(54) TITLE OF THE INVENTION SCSI DEVICE
`ADAPTER
`
`Noboru KAWAGUCHI Sanyo Machine
`
` (21) JAPANESE PATENT APPLICATION H2‐120493
`
`(72) Inventor:
`Works, Ltd.
`
`1, Azaoka, Oazaoki‐mura, Nishiharu‐cho,
`
`Nishikasugai‐gun, Aichi‐ken
`
`(72) Inventor: Mitsutoshi GOTO
`
`Sanyo Machine Works, Ltd.
`
`1, Azaoka, Oazaoki‐mura, Nishiharu‐cho,
`
`Nishikasugai‐gun, Aichi‐ken
`
`(71) Applicant:
`
`Sanyo Machine Works, Ltd.
`
`1, Azaoka, Oazaoki‐mura, Nishiharu‐cho,
`
`Nishikasugai‐gun, Aichi‐ken
`
`(74) Agent:
`
`Shogo EHARA, Patent Attorney
`
`
`
`
`
`
`
`Specification
`
`1. Title of the Invention
`
`SCSI Device Converter
`
`2. Claims
`
` (22) DATE OF APPLICATION MAY 9, 1990
`
`KAWAGUCHI, NOBORU ℅
`(72) INVENTOR
`SANYO MACHINE WORKS, LTD.
`
`1 OKA, OKIMURA, NISHIHARU‐MACHI, NISHI
`KASUGAI‐GUN, AICHI PREFECTURE
`
`GOTO, MITSUTOSHI
`(72) INVENTOR
`SANYO MACHINE WORKS, LTD.
`
`℅
`
`1 OKA, OKIMURA, NISHIHARU‐MACHI, NISHI
`KASUGAI‐GUN, AICHI PREFECTURE
`
`SANYO MACHINE WORKS,
`(71) APPLICANT
`LTD. 1 OKA, OKIMURA, NISHIHARU‐MACHI, NISHI
`KASUGAI‐GUN, AICHI PREFECTURE
`
`(74) AGENT PATENT ATTORNEY EHARA, SHOGO
`
`
`
`
`
`SPECIFICATION
`
`
`
`1. TITLE OF THE INVENTION
`
`SCSI Device Adapter
`
`2. SCOPE OF PATENT CLAIMS
`
`Papst Licensing GmbH & Co. KG's Patent Owner Response, Ex. 2010, p. 1
`
`
`
`1207
`
`
`
`
`Side By Side Comparison of Kawaguchi Translations
`v.
`2009
`
`(1) A SCSI device adapter, comprising:
`
`(1) A SCSI device converter comprising: a SCSI interface
`connected to a SCSI interface in an engineering
`workstation (EWS) for connecting a hard disk;
`
`a device interface for connecting a peripheral device;
`
`a SCSI interface that is connected to a SCSI interface for
`connecting an EWS (Engineering WorkStation) device;
`
`a device interface for connecting to a peripheral
`device;
`
`a data writing unit, data reading unit, control data writing
`unit, and an interrupt data reading unit each identified by
`the EWS through the SCSI interface by a different ID
`number (or by the same ID number but a different unit
`number);
`
`a data writing portion, a data reading portion, a control
`data writing portion, and an interrupt data reading
`portion that are identified with different ID numbers (or
`with identical ID numbers and different unit numbers)
`from the EWS through the SCSI interface;
`
`a code converting unit interposed between the data
`writing unit, the reading unit, and the device interface for
`converting data between the SCSI format and the
`peripheral device bus format;
`
`a code converting portion for converting data between
`a SCSI format and a peripheral device bus format,
`positioned between the data writing portion and data
`reading portion and a device interface;
`
`a controlling portion for controlling sending and
`receiving of data between the EWS and the peripheral
`device, carried out through relaying through the data
`writing portion and reading portion; and
`
`an interrupt controlling device for outputting, to the
`EWS, through the SCSI interface, a disconnect signal
`when, for an interrupt data read command sent from the
`EWS, the interrupt data is not ready in the interrupt data
`reading portion, to release the EWS circuit, and for
`sending, to the EWS, through the SCSI interface, a
`reconnect signal when interrupt data has been inputted
`from the interrupt data reading portion thereafter, to
`enable the EWS to read out the interrupt data.
`
`[STAMP
`INVENTION
`3. DETAILED EXPLANATION OF THE
`INDICATING THAT THIS IS A VALID AMENDMENT TO A
`DIFFERENT SPELLING OF THE SAME MESSAGE]
`
`[AREA OF USE IN INDUSTRY]
`
`The present invention relates to a general‐use SCSI
`device able to connect easily PC peripheral devices and
`devices such as sequencers to a SCSI interface of an EWS
`(Engineering WorkStation).
`
`[PRIOR ART AND PROBLEM SOLVED BY THE PRESENT INVENTION]
`
`Engineering workstations, given their multi‐tasking,
`multi‐windowing
`processing
`and
`comparatively
`inexpensive equipment structure enable high‐speed data
`processing, and are used by consumers.
`
`An EWS is equipped with a SCSI interface, as a standard
`interface, for the purpose of connecting a hard disk or a
`magnetic tape device. However, it does not have a slot
`for an expansion board, such as in a PC. Consequently, it
`
`a control unit for controlling the transmission/reception of
`data between the EWS and the peripheral device through
`the data writing unit and reading unit are interrupted; and
`
`an interrupt control unit for outputting a disconnect signal
`via the SCSI interface to the EWS to release an EWS line
`when the data reading unit has not prepared interrupt
`data for an interrupt data read command sent from the
`EWS, and afterwards for sending a reconnect signal to the
`EWS via the SCSI interface to enable the EWS to read
`interrupt data when interrupt data has been inputted
`from a device to the interrupt data reading unit.
`
`
`
`3. Detailed Description of the Invention (Field of Industrial
`Applicability)
`
`The present invention relates to a general SCSI device
`converter which is able to easily connect a device such as a
`PC peripheral device or a sequencer to a SCSI interface on
`an engineering workstation (EWS).
`
`
`
`(Prior Art and Problem Solved by the Invention)
`
`Engineering workstations (EWS) include a collection of
`inexpensive devices which facilitate high‐speed processing
`via multi‐tasking and multi‐window processing.
`
`
`
`An EWS includes, as a standard interface, a SCSI interface
`used to connect hard disks and magnetic disk drives.
`However, they do not include expansion slots such as
`
`Papst Licensing GmbH & Co. KG's Patent Owner Response, Ex. 2010, p. 2
`
`
`
`1207
`
`personal computers. As a result, output devices such as
`plotters and sequencers which have a personal computer
`I/O bus or bi‐ directional parallel bus with interrupt for a
`personal computer cannot be connected directly to an
`EWS. In other words, because current EWS only have an
`initiator function, a circuit connection cannot be
`established from a converter to an EWS.
`
`
`
`While a personal computer can be connected to a wider
`variety of peripheral devices by using the expansion slot, it
`has a slower processing speed and not practical because
`of single‐task processing. An higher grade EWS has a
`dedicated bus for connecting peripheral devices, but it is
`for specific device, so it cannot be connected to any
`peripheral device and the system configuration is very
`expensive.
`
`When an EWS is connected to a peripheral device with a
`PC‐compatible bus, the process requires a standard SCSI
`interface designed to accommodate a hard disk, a PC‐
`compatible GPIB interface, and a code converter
`connected to these interfaces to perform the necessary
`code conversion.
`
`
`
`However, current SCSI interfaces designed for hard disks
`do not have an interrupt function, and the device which is
`required to interrupt on the host end such as by a
`sequencer cannot be connected.
`
`
`
`Therefore, it is an object of the present invention to
`provide a general SCSI device converter which enables a
`peripheral device having a bus standard differ from SCSI
`such as PC bus to be easily connected to the SCSI interface
`on a EWS designed to connect a hard disk, and especially
`allows the peripheral device end to interrupt.
`
`
`
`(Means of Solving the Problem)
`
`The present invention is a SCSI device converter
`comprising: a SCSI interface connected to a SCSI interface
`in an engineering workstation (EWS) for connecting a hard
`disk; a device interface for connecting a peripheral device;
`a data writing unit, data reading unit, control data writing
`unit, and an interrupt data reading unit each identified by
`the EWS via the SCSI interface by a different ID number (or
`by the same ID number but a different unit number); a
`code converting unit interposed between the data writing
`
`Side By Side Comparison of Kawaguchi Translations
`v.
`2009
`
`has not been possible to connect directly, to an EWS,
`output devices such as plotters, or sequencers, or the
`like, that have a PC I/O bus or a bidirectional parallel bus
`with interrupts, which are PC‐compatible buses. That is
`to say, because the existing EWS has only an initiator
`function, adapters cannot be wired and connected to an
`EWS.
`
`Note that while a personal computer has a high degree
`of flexibility in connecting peripheral devices through the
`use of expansion slots, the processing uses a single stack,
`so the processing speed
`is slow and
`impractical.
`Moreover, while high‐end EWSs are provided with
`specialized buses for connecting peripheral devices, they
`are compatible only with specific devices, and are unable
`to connect freely to arbitrary devices, and the system
`structure is extremely expensive.
`
`If peripheral devices that have PC‐compatible buses are
`to be connected to EWSs, then a code converter for
`converting codes between [those of] the SCSI interface
`that
`is the standard equipment that
`is designed
`compatible with the existing hard disks, and [those of]
`the GPIB interface, for example, that is a PC‐compatible
`bus, should be manufactured.
`
`However, the existing SCSI interface that is designed
`for hard disk use has no interrupt function, and thus
`cannot be connected to a device that requires interrupts
`to be applied to the host side, such as a sequencer, or the
`like.
`
`Given this, the object of the present invention is to
`provide a general‐use SCSI device adapter that can easily
`connect a peripheral device that has a standard bus that
`is different from that of an SCSI bus, such as a PC‐
`compatible bus, or the like, to the SCSI interface of an
`EWS that was built for the purpose of connecting with a
`hard disk, and, in particular, to provide a general‐use SCSI
`device adapter that can apply an interrupt from the
`peripheral device side.
`
`[MEANS FOR SOLVING THE PROBLEM]
`
`The present invention provides a SCSI device adapter,
`comprising: a SCSI interface that is connected to a SCSI
`interface
`for
`connecting
`an
`EWS
`(Engineering
`WorkStation) device; a device interface for connecting to
`a peripheral device; a data writing portion, a data reading
`portion, a control data writing portion, and an interrupt
`data reading portion that are identified with different ID
`numbers (or with identical ID numbers and different unit
`numbers) from the EWS through the SCSI interface; a
`code converting portion for converting data between a
`
`Papst Licensing GmbH & Co. KG's Patent Owner Response, Ex. 2010, p. 3
`
`
`
`1207
`
`unit, the reading unit, and the device interface for
`converting data between the SCSI format and the
`peripheral device bus format; a control unit for managing
`the transmitting/receiving of data between the EWS and
`the peripheral device via the data writing unit and reading
`unit are interrupted; and an interrupt control unit for
`outputting a disconnect signal (conforming to SCSI
`standards) via the SCSI interface to the EWS to release an
`EWS line when the data reading unit has not prepared
`interrupt data for an interrupt data read command sent
`from the EWS, and afterwards for sending a reconnect
`signal (conforming to the SCSI standards) to the EWS via
`the SCSI interface to enable the EWS to read interrupt
`data when interrupt data has been inputted from a device
`to the interrupt data reading unit.
`
`
`
`(Operation)
`
`The above‐described SCSI device converter is able to input
`and output data to a SCSI interface of an EWS using the
`same standards as SCSI interface for a hard disk, and
`enables the above‐described four units, i.e., the data
`writing units and data reading units, which allow the EWS
`to operate as a data relay point with a peripheral device,
`to write and read data.
`
`This SCSI device converter also inputs data to and outputs
`data from a peripheral device via a device interface by
`using a device bus standard, and the data is converted into
`SCSI standard data by a code converting unit, and is
`inputted to and outputted from the above‐described four
`units, i.e., the data writing units and data reading units.
`
`To an interrupt data read command from the EWS, the
`interrupt control unit temporarily releases the line to the
`EWS using a disconnect signal and reconnect signal of SCSI
`standards when data is not prepared in the interrupt data
`reading unit, and data reading is performed when the data
`is prepared thereafter.
`
`This operation enables the SCSI interface of the EWS,
`which is not equipped to handle an interrupt from a
`device, to perform a virtual‐interrupt operation, and
`enables the SCSI interface of the EWS, which is designed
`for connecting a hard disk, to connect a device requiring
`an interrupt.
`
`(Embodiment)
`
`The following is an explanation of a configuration shown in
`FIG. 1 in which a peripheral device is connected to an EWS
`using a SCSI device converter in an embodiment of the
`
`Side By Side Comparison of Kawaguchi Translations
`v.
`2009
`
`SCSI format and a peripheral device bus format,
`positioned beteen the data writing portion and data
`reading portion and a device interface; a controlling
`portion for controlling sending and receiving of data
`between the EWS and the peripheral device, carried out
`through relaying through the data writing portion and
`reading portion; and an interrupt controlling device for
`outputting, to the EWS, through the SCSI interface, a
`disconnect signal when, for an interrupt data read
`command sent from the EWS, the interrupt data is not
`ready in the interrupt data reading portion, to release the
`EWS circuit, and for sending, to the EWS, through the
`SCSI interface, a reconnect signal when interrupt data has
`been inputted from the interrupt data reading portion
`thereafter, to enable the EWS to read out the interrupt
`data.
`
`[OPERATION]
`
`The SCSI device adapter performs input/output of data
`to/from an EWS SCSI
`interface through the same
`standard as the SCSI interface for a hard disk, the EWS to
`write and read arbitrary data to/from four types of data
`writing portions and reading portions that function as
`data relays with the peripheral device.
`
`Moreover, this SCSI device adapter performs input and
`output of data to/from the peripheral device through the
`interface for the device through the bus standard of that
`device, and converts the data thereof, through the code
`converting portion, to data of the SCSI standard, to
`input/output to/from the four types of data writing
`portions and reading portions.
`
`When there is no data ready in the interrupt data
`reading portion in response to an interrupt data read
`command from the EWS, the
`interrupt controlling
`portion uses a SCSI‐standard Disconnect signal and
`Reconnect signal to release the EWS line, and then,
`thereafter, cause the data to be read out once the data is
`ready.
`
`This operation enables a device that requires interrupts
`to be connected to the SCSI interface of an EWS that was
`designed for connecting a hard disk, through causing a
`virtual interrupt operation, in a SCSI interface for an EWS
`that has not been designed for interrupts.
`
`[EMBODIMENTS]
`
`An example of a structure wherein a peripheral device
`is connected to an EWS using a SCSI interface converter
`according to one embodiment according to the present
`invention will be explained using FIG. 1.
`
`Papst Licensing GmbH & Co. KG's Patent Owner Response, Ex. 2010, p. 4
`
`
`
`Side By Side Comparison of Kawaguchi Translations
`v.
`2009
`
`In this figure, (1) is a relatively inexpensive EWS
`(Engineering WorkStation) of a desktop type, and has, as
`standard equipment, a SCSI interface (2) for connecting a
`hard disk. (3) is a SCSI device adapter that is assembled in
`a single board, peripheral devices, such as, for example,
`an output device (4), such as a plotter, an input device
`(5), such as a CD‐ROM, and a device (6) that carries out
`like, are
`interrupt control of a sequencer, or the
`connected to the EWS (1).
`
`
`
`The SCSI device adapter (3) has a SCSI interface (7) for
`connecting to the EWS (1), and has, as a device interface
`for connecting peripheral devices, PC I/O bus interfaces
`(8) and (9), and a bidirectional interrupt‐capable parallel
`bus interface (10). Moreover, in the SCSI device adapter
`(3), a data writing portion (11), a data reading portion
`(12), a control data writing portion (13), and an interrupt
`data reading portion (14) that are
`identified with
`different ID numbers N, N + 1,…, N + 3 (or with identical
`ID numbers and different unit numbers N, N + 1,…, N + 3)
`through the SCSI interfaces (2) and (7) from the EWS (1),
`a code converting portion (15) for converting to a data
`format between the SCSI standard and a bus standard of
`the interface for the device, between the individual data
`writing portions and data reading portions (11), (12),
`(13), and (14) and the device interfaces (8), (9), and (10),
`a controlling portion (16) for controlling sending and
`receiving of data between the EWS and the peripheral
`device that is carried out relayed by the aforementioned
`data writing and reading portions; and an interrupt
`controlling portion (17) for generating a control signal so
`as to enable the EWS (1) to receive an interrupt signal
`from a device through the SCSI interfaces (2) and (7)
`without interrupting processing, are structured from a
`microcomputer, a ROM, and a RAM.
`
`
`
`Note that the device interface of the SCSI device
`adapter (3) may also use, depending on the connected
`device, other types of I/O bus interfaces (8) and (9) and
`bidirectional interrupt‐compatible parallel interfaces (10)
`from those described above. For example, an A/D
`converter (19) able to input analog data from an analog
`device (18), such as a sensor, may be built in. Here the
`device interface may be an RS‐232, a standard interface
`such as a Centronics or VME bus, or a specialized
`interface such as an expansion bus of a specific PC.
`
`The EWS device adapter (3), structured as described
`
`1207
`
`present invention.
`
`In this drawing, (1) indicates a relatively inexpensive EWS
`(Engineering Workstation) such as a desk top typewhich
`has a SCSI interface (2) as standard equipment for
`connecting with the hard disk. (3) indicates a SCSI device
`converter installed in one boardwhich connects the EWS
`(1) to a peripheral device, for example, an output device
`(4) such as a plotter, an input device (5) such as a CD‐
`ROM, and a device (6) that performs interrupt control
`such as a sequencer.
`
`
`
`The SCSI device converter (3) includes a SCSI interface (7)
`for connecting to the EWS (1), and includes personal
`computer I/O bus interfaces (8) (9) and an interface for a
`bi‐directional parallel bus interface (10) with interrupt
`function as interface for connecting peripheral devices.
`The SCSI device converter (3) also implements a data
`writing unit (11), a data reading unit (12), a control data
`writing unit (13), an interrupt data reading unit (14), a
`code converting unit (15), a control unit (16) and an
`interrupt control unit (17) by using a microcomputer, ROM
`and RAM. The data writing unit (11), the data reading unit
`(12), the control data writing unit (13) and the interrupt
`data reading unit (14) are identified in different ID
`numbers N, N+1, …, and N+3 (or by the same ID number
`but different unit numbers N, N+1, …, and N+3) by the
`EWS (1) through the SCSI interface (2) (7). The
`codeconverting unit (15) and the control unit (16) are
`located between each of the data writing units and
`reading units (11) (12) (13) (14) and the device interfaces
`(8) (9) (10). The code converting unit (15) converts the
`data format between SCSI standards and device‐interface
`bus standards.The control unit (16) controls the data
`transmission/reception between the EWS and the
`peripheral devices which is performed by relaying the data
`writing units and reading units. The interrupt control unit
`(17) generates a control signal so that the EWS (1) can
`receive interrupt signals from the devices through the SCSI
`interfaces (2) and (7) without terminating processing.
`
`In addition to the I/O interfaces (8) (9) and interface for a
`bi‐directional parallel bus with interrupt (10) mentioned
`above, the SCSI device converter(3) can be adapted to
`accommodate any other type of device interface. For
`example, an A/D converter (19) may be installed to receive
`analog data from an analog device (18) such as a sensor.
`The device interface used here can be a standard interface
`such as a RS‐232, Centronics, or VME bus, or a special
`interface such as the expansion buses used in each
`personal computer.
`
`Papst Licensing GmbH & Co. KG's Patent Owner Response, Ex. 2010, p. 5
`
`
`
`Side By Side Comparison of Kawaguchi Translations
`v.
`2009
`
`1207
`
`The following is an explanation of the operations
`performed by an EWS device converter (3) with this
`configuration.
`
`above, operates as follows.
`
`
`
`The SCSI interface of the EWS (1) is designed so as to
`enable connection of up to 8 hard disks. Given this, in the
`present invention ID numbers (or a single ID number with
`different unit numbers) (N, N + 1,…, N + 3) are assigned
`to the individual writing portions and reading portions
`(11) through (14) so as to enable identification, as
`perceived by the EWS (1), of the data writing portion of
`(11), the data reading portion (12), the control data
`writing portion (13), and the interrupt data reading
`portion (14), as four of those hard disk devices. That is,
`the EWS (1) merely operates by reading from, or writing
`to, the individual writing portions and reading portions
`using the same procedure as for four hard disk devices.
`
`On the other hand, the controlling portion (16) controls
`the
`inputting and outputting of data from/to the
`peripheral devices (4), (5), and (6) through the device
`interfaces (8), (9) and (10). That is, it outputs, to an
`output device (4) such as a plotter, the data that is
`written to the data writing portion (11), inputs, into the
`data reading portion (12) the data that has been written
`in from an input device (5), such as a CD‐ ROM, or the
`like, outputs, to the device (6) that carries out interrupt
`control, such as a sequencer, data that has been written
`to the control data writing portion (13), and inputs, into
`the interrupt data reading portion (14), interrupt data
`from the device (6) that carries out interrupt control. The
`input/output control of the controlling portion (17) is
`carried out with prescribed timing through decoding of
`commands sent from the EWS (1). Note that in the
`exchange of data between the device interfaces (8), (9),
`and (10) and the individual data writing portions and
`reading portions
`(11),
`(12),
`(13), and
`(14), code
`conversion between the SCSI standard and the various
`bus standards is carried out through the interposition of
`the code converting portion (15). Moreover, even if the
`device interfaces (8), (9), and (10) each have respective
`pluralities of channels, control is possible through the
`code converting portion (15), the controlling portion (16),
`and the interrupt controlling portion (17).
`
`In the present invention, the EWS (1) recognizes the
`individual writing portions and reading portions (11),
`(12), (13), and (14) as individual devices, and thus, in the
`EWS (1), the processing efficiency is high, as the different
`writing programs and reading programs for the individual
`writing portions and reading portions (11), (12), (13), and
`(14) are
`launched simultaneously and processed
`in
`parallel.
`
`
`
`The SCSI interface in the EWS (1) is designed to connect up
`to eight hard disks. In the present invention, the various
`writing units and reading units (11) … (14) are assigned ID
`numbers (or the same ID number but different unit
`numbers) (N, N+1, …, N+3) so that the EWS (1) can
`identify, in appearance, the data writing unit (11), the data
`reading unit (12), the control data writing unit (13), and
`the interrupt data reading unit (14) as four hard disk
`devices . In other words, the EWS (1) writes or reads data
`to each writing unit or from each reading unit using the
`same method as that for four hard disks.
`
`
`
`The control unit (16) controls the input and output of data
`to the peripheral devices (4) (5) (6) via the device
`interfaces (8) (9) (10). In other words, data written to the
`data writing unit (11) is outputted to an output device(4)
`such as a plotter, data read from an input device (5) such
`as a CD‐ROM is inputted to the data reading unit (12), data
`written to the control data writing unit (13) is outputted to
`a device (6) performing interrupt control such as a
`sequencer, and interrupt data from the device (6)
`performing interrupt control is inputted to the interrupt
`data reading unit (14). The input/output control by the
`interrupt control unit (17) is performed on a
`predetermined timing by interpreting commands sent
`from the EWS (1). The code converting unit (15) is involved
`in data transmission/reception between the device
`interfaces (8) (9) (10) and the data writing units and
`reading units (11) (12) (13) (14) to convert code between
`the SCSI standards and each bus standard. The device
`interfaces (8) (9) (10) can be controlled by the code
`converting unit (15), the control unit (16) and the interrupt
`control unit (17) even when a plurality of channels exist.
`
`
`
`In the present invention, the EWS (1) recognizes the
`writing units and reading units (11) (12) (13) (14) as
`separate devices. As a result, the EWS(1) can
`simultaneously launch separate a writing program and a
`reading program for these writing units and reading units
`(11) (12) (13) (14) and perform parallel processing for
`
`Papst Licensing GmbH & Co. KG's Patent Owner Response, Ex. 2010, p. 6
`
`
`
`Side By Side Comparison of Kawaguchi Translations
`v.
`2009
`
`1207
`
`higher processing efficiency.
`
`
`
`The major distinctive feature of the present invention
`is that virtual interrupts are caused to be carried out,
`from the device side, in the SCSI interface (2) of an EWS
`(1) that was not designed for interrupts. That is, when
`there is a read command from the EWS (1) to the
`interrupt data reading portion (14), if interrupt data is
`not ready (where, unlike the case wherein data is ready
`in response to a read command from the EWS (1) in a CD‐
`ROM inputting device (1), here the interrupt is made with
`unspecified timing depending on the status on the device
`side, so often the interrupt data is not ready), the
`interrupt controlling portion (17) sends a Disconnect
`signal to the EWS (1) to release the EWS circuit. This
`enables the EWS (1) to carry out other processes. When,
`thereafter, interrupt 12 data is ready in the interrupt data
`reading portion (14), the interrupt controlling portion
`(17) sends a Reconnect signal to the EWS (1). The EWS (1)
`that has received this signal carries out interrupt data
`reading, to complete the reading of the interrupt data by
`the EWS (1).
`
`The operation described above will be explained in the
`series of operations in the SCSI driver (software) of the
`EWS (1). The EWS SCSI driver was developed as a driver
`for connecting a hard disk. As a result, the device of the
`present invention acts as an emulation of a hard disk. The
`procedure sequence is performed following the flowchart
`illustrated in FIG. 2.
`
`
`
`In this flowchart, the "Start" through "Mode Sense" is
`the hard disk initializing procedure, where "Inquiry" is
`information for the properties of the target and logical
`unit (the device type identification code); the "Start/Stop
`unit" starts/stops the logical unit; the "Test Unit Ready" is
`a test of whether or not the logical unit is in a usable
`state; and the "Mode Sense" is information for the
`various parameter values (data format and structure of
`the recording medium). Through this, the individual
`writing portions and reading portions (11), (12), (13), and
`(14) go into an active state, relative to the EWS (1).
`
`After the initializing sequence, the EWS (1) executes
`reading from, or writing to, the
`individual writing
`portions and reading portions (11), (12), (13), and (14).
`Specifically, the "Read Extended" reads out a specified
`block, that is, reads the data reading portion (12) or the
`
` A
`
` major feature of the present invention is to cause the
`SCSI interface (2) of the EWS (1), which is not equipped to
`handle an interrupt from a device, to perform a virtual
`interruption. In other words, if interrupt data is not
`prepared when a read command is issued from the EWS
`(1) to the interrupt data reading unit (14) (since an
`interrupt is occurred at unspecified timing in accordance
`with a state of the device, interrupt data is not prepared in
`many cases, unlike a case in which the input device (5)
`such as CD‐ROM prepares data in response to the read
`command from the EWS (1)), the interrupt control unit
`(17) sends a disconnect signal to the EWS (1), and
`temporarily disconnects the line to the EWS. Thus, the
`EWS (1) can perform another process. Thereafter, when
`interrupt data is prepared in the interrupt data reading
`unit (14), the interrupt control unit (17) sends a reconnect
`signal to the EWS (1). The EWS (1), which has been
`received the reconnect signal, reads the interrupt data,
`and then the reading of interrupt data by the EWS (1)
`ends.
`
`The following is an explanation of the operations
`performed by a SCSI driver (software) of the EWS (1)
`performing the above‐described operation.
`
`The SCSI driver of the EWS has been developed as a driver
`for connecting a hard disk. Therefore, the apparatus in the
`present invention operates in a manner emulating the
`hard disk. This processing procedure is performed
`according to a flowchart shown in FIG. 2.
`
`In this flowchart, steps from ‘Start’ to ‘Mode Sense’
`represent an initialization process for a hard disk, ‘Inquiry’
`represents reporting of attribute information of a target
`and logical units (identification code of a device type),
`‘Start/Stop Unit’ represents start/stop of the logical unit,
`‘Test Unit Ready’ represents testing whether or not the
`logical unit is available, and ‘Mode Sense’ represents
`reporting of various parameter values (data format,
`storage medium configuration). In this way, the writing
`units and reading units (11) (12) (13) (14) can be activated
`for the EWS (1).
`
`After the initialization process, the EWS (1) performs
`writing to or reading from the writing units and reading
`
`Papst Licensing GmbH & Co. KG's Patent Owner Response, Ex. 2010, p. 7
`
`
`
`1207
`
`units (11) (12) (13) (14). In other words, ‘Read Extended’
`represents reading data from a designated block, i.e., the
`data reading unit (12) or the interrupt data reading unit
`(14), and ‘Write Extended’ represents writing data to