Abstract:
A buffer memory holding blocks of data received from a main host computer has dedicated portions for data destined for different sets of sender-receiver units. Each sender-receiver unit has a channel bus path to the buffer memory and each channel bus is monitored by an on-the-fly integrity checking circuit. 
     A control processor and associated bus arbitration logic provide signals to a multiplexer so as to allocate equal access periods to each channel bus for connection to the buffer memory. A data feeder control on each transfer channel senses the availability of data block words in each dedicated segment of the buffer memory so that partial transfers of word blocks may occur on minor cycles with subsequent completion of the blocks of data words on a major transfer cycle.

Description:
FIELD OF THE INVENTION 
     This disclosure refers to systems using multiple channels for data transfer with concurrent on-the-fly integrity checking for each channel. 
     BACKGROUND OF THE INVENTION 
     In the field of digital modules operating in networks, a basic operational function involves the transfer of data between the interconnected digital modules. During the course of data transfer, it is necessary to keep account of the amount of data being transferred and to insure that the data has been transferred with integrity on a reliable basis. 
     As seen in FIG. 2A, one generalized type of data transfer system involves the transfer of data between the host processor 4 and peripheral units such as disk drive units 70. The data transfer operations are seen to be transferred through a channel interface module 8 c  which then transfers the data to the device interface module 8 d  which can then communicate with the peripheral units 70 both for the output of data to the peripheral units and for the receipt of data from the peripheral units. 
     FIG. 2B shows a semi-detailed drawing of the device interface module 8 d  indicating that a memory buffer for temporary holding data being transferred can communicate with a SCSI Peripheral Controller SPC 80 in order to handle the transfers of data between the peripheral 70 and the memory buffer 24 d . During the course of data transfer along the bus 6, an integrity circuit 81 will continuously monitor the transfer of data and insure that the integrity of data transferred is valid. 
     FIG. 3 shows a more detailed view of the network which was basically shown in FIG. 2A. Here in FIG. 3 multiple numbers of host computers 4 a . . . 4 d  can communicate with channel interface modules 8 c1  and 8 c2 . Each channel interface module has a buffer memory 24 c1  and 24 c2  which can temporarily hold data for transfer through two ports 31 c  and 32 c . 
     The two ports 31 c  and 32 c  are connected to dual system busses 6 a  and 6 b  which enable any host computer 4 to communicate through either one of the channel interface modules and then through either one of the dual ports 31 c  -32 c  onto the system buses 6 a  and 6 b  which enables data transfers to be passed on through multiple numbers of device interface modules, such as 8 d1  and 8 d2 . 
     The device interface module 8 d1  and 8 d2  each have a buffer memory 24 d1  and 24 d2  which is connected through a multiplexor 24 x1  and 24 x2  on through multiple channels (6 0 , 6 1 , 6 2 , 6 3 ) to a set of four I/O ports designated as SCSI Protocol Controllers SPC 0 , (80 0 ), SPC 1 , (80 1 ), SPC 2 , (80 2 ), and SPC 3 , (80 3 ). It is then seen that the peripheral devices 70 a . . . 70 d  each can have dual I/O port connections to two sets of device interface modules. Thus, by allowing communication through two ports, there is also provision for communication to any one port should one of the other ports fail. 
     As seen in FIG. 5A, a block of data composed of &#34;X&#34; bytes will have a header portion which provides the address and destination of commands and includes information as to the size of the block. After the header, there is present the main bulk of the data block followed by a signature portion designated as the Error Detection Code (EDC) signature. The EDC signature is provided to characterize the value of the block of data and will represent the value of the data being transmitted in the main block. 
     Subsequently, as seen in FIG. 5B, there may be data block transfers of a different volume or size as shown by the block designated &#34;Y&#34; bytes. Here again the header will provide the address, destination commands, block size, and other pertinent data, after which the main portion holds the data to be transferred followed by the EDC (Error Detection Code) which characterizes the data being transferred. 
     When a block of data, such as that of &#34;X&#34; bytes or that of &#34;Y&#34; bytes, is being transferred, it is necessary that some means be provided to recognize the block size and insure that the integrity of the data transfer be validated. It is further necessary to monitor the data transfer to see that the entire preselected number of bytes has been transferred. 
     As seen in FIG. 6, there is shown an example of the transfer of two different block sizes to be transmitted between a sending and receiving digital module, the first block size being of 180 bytes with a header and EDC signature. This is followed by a larger block size of 512 bytes which also has its own personal header portion and succeeding EDC signature. The presently described system operates to insure that there will be no delay in the data transfer operation even though blocks of different sizes are being transferred and additionally, that the different block sizes will be concurrently checked on-the-fly for integrity without any delay to the data transfer operation. 
     As illustrated in FIG. 6, blocks of data to be transferred can occur in different block sizes. For example, the first block in FIG. 6 has a block size of 180 bytes and the second block has a size of 512 bytes. FIG. 6 also illustrates how the header contains information as to the block size and how the EDC signature provides a Hexspace of 36 bits. The first bit involves a parity check and the remaining number of bits are used to provide an original EDC signature. In the present system involving the four channel busses (6 0 , 6 1 , 6 2 , 6 3 ) shown in FIG. 1, there is seen a device interface module 8 d  which has a buffer memory 24 d  holding data to be transferred between peripheral units (70 p0 . . . 70 p3 ) and any one of the said host processor 4 a . . . 4 d  of FIG. 3. 
     The presently described system of FIG. 1 provides a device interface module 8 d  which permits four concurrently operating channels between the buffer memory 24 d  and the peripheral units 70. Each channel is provided with its own integrity checking circuit Ic (81 0 , 81 1 , 81 2 , 81 3 ) which operates on-the-fly and insures that the data transfer on that channel is a correct data transfer. 
     SUMMARY OF THE INVENTION 
     A multi-channel integrity checking data transfer system is provided wherein a plurality of peripherals are connected to one or more device interface modules (DIM). The device interface module provides multiple bus channels for data transfer and each of the data transfer channels has its own personal integrity checking circuit, Ic. 
     Each of the integrity checking circuits functions to check the parity of each word transferred and subsequently checks the Error Detection Code signature by generating its own internal error detection code (EDC) for comparison with the original detection code in the data block, thus, to verify the integrity of the data transferred. 
     The device interface module has a buffer memory for holding data blocks received from a main host computer which data blocks are destined for transfer through a selected one of multiple channel buses to a selected peripheral device. Data blocks can also be transferred from a peripheral device through an associated protocol controller, a channel bus, and multiplexer over to the buffer memory for subsequent transmission to a main host computer. 
     A bus arbitration controller, sensitive to requests from each of a plurality of protocol controllers and also to the control processor of the device interface module (DIM), regulates the multiplexer by allocating equal time periods to each of the channel buses when all of the channel buses seek access to/from the buffer memory. 
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS 
     FIG. 1 is a block diagram showing the multi-channel integrity checking system whereby the buffer memory can provide storage of data going to and from a plurality of peripheral devices; 
     FIG. 2A is a generalized block diagram of the overall system network; FIG. 2B, is a detailed block diagram of the device interface module (DIM) showing the channel bus 6 connecting the memory buffer with the protocol controller (SPC) and at the same time permitting an integrity circuit IC to check the data transferred on the bus; 
     FIG. 3 is a more detailed diagram of the overall system showing a network with multiple numbers of device interface modules connected to dual system busses and allowing interconnection of multiple host processors to multiple numbers of peripheral devices; 
     FIG. 4 is a diagram showing the integrity checking circuit connected to each of the channel busses; 
     FIG. 5A is a drawing showing the protocol arrangement of a short block of data; FIG. 5B is a drawing showing the arrangement of a longer block of data; 
     FIG. 6 shows a set of data blocks to be transferred which are of different size with the indication of the size of the data block indicated in the header and the error code data in the Error Detection Code signature areas; 
     FIG. 7 is a timing diagram showing the integrity checking operations which occur on-the-fly while data is being transferred on the channel bus. 
    
    
     DESCRIPTION OF PREFERRED EMBODIMENT 
     Referring to FIG. 1, there is seen a diagram of the device interface module 8 d  which provides four channel busses for data transfer to multiple numbers of peripheral devices 70 (70 p0 , 70 p1 , 70 p2 , 70 p3 ). 
     A buffer memory 24 d  is a temporary storage unit for data which is being transferred between a plurality of host processors 4 and a plurality of peripheral units such as the disk drives 70. 
     The buffer memory 24 d  has an internal bus connection to a multiplexor 24 x  which provides connection to four channel busses enabling data transfer to a series of protocol controllers designated SPC 80 (80 0 , 80 1 , 80 2 , 80 3 ). The multiplexor 24 x  connects the four channel buses designated 6 0 , 6 1 , 6 2 , and 6 3  for connection from buffer memory 24 d  to protocol controllers SPC 80. Each of the channel busses 6 is provided with its own individual integrity checking circuit (81 0 , 81 1 , 81 2 , 81 3 ). Thus, any data transfers on multiple channel busses 6 are individually checked for integrity by the integrity checking circuit 81 (I c ). 
     Referring to FIG. 1, there is seen a control processor 10 d  which is a functioning module in each device interface module (DIM) and which is used to control the data transfer operations. The control processor 10 d  will monitor the buffer 24 d  in order to recognize when data is destined for any one of the peripheral devices or when data is destined for one of the host processors 4. Likewise, the control processor 10 d  will monitor and initiate the integrity checking circuity 81 (81 0 , 81 1 , 81 2 , 81 3 ) and receive information as to whether or not the data transferred is valid. If the data transfer is found not be valid, then an interrupt signal will be transmitted to the control processor 10 d . 
     The control processor 10 d  (FIG. 1) also functions to: (i) get the number of data blocks (from CIM 8 c  FIG. 2A) to be transferred on a given major I/O cycle; (ii) places the data blocks received in portions of buffer memory 24 d  which are dedicated to each channel bus 6; (iii) determine whether the host command is a Read or a Write operation; (iv) inform each SPC 80 of the total number of blocks to be transferred on each major I/O cycle and also whether the major cycle is a Read or Write operation; (v) sets a counter in a data feed control circuit telling the SPC 80 how many data blocks are presently residing in buffer memory 24 d  (which may be less than the transfer for the major I/O cycle) which can be transferred at the moment. 
     An expanded view of a portion of the Device Interface Module (DIM) in FIG. 2B is shown in FIG. 4 wherein a memory buffer 24 d  is connected by means of a bus 6 over to a SCSI Protocol Controller, (SPC) 80. The protocol controller 80 connects the bus 78 (FIG. 2B) to peripheral units, such as disk units 70. Attached to the protocol controller channel bus 6 is seen an auxiliary connecting bus 6 i  which connects to two registers 22 and 14. The initialize register 22 and the input register 14 both function simultaneously to initialize the integrity checking circuit 81 and to store a duplicate of each data word (36 bits) being transferred on the protocol controller channel bus 6. Each word is placed momentarily in input register 14. 
     The initialize register 22 will also indicate the &#34;size&#34; of the block of data being transferred. The input register 14 makes a copy of each data word in the entire block. The input register 14 looks at each block and creates via generator 28 an internally generated error code signature. The purpose of this is to compare the original error detection code (EDC) signature provided at the end of each block (FIG. 4) with the locally internally generated EDC signature by generator 28. 
     The block counter 26 is used to count the number of data words (and bytes) transferred between the two digital modules 24 d  and 80. The SCSI Protocol Controller (SPC) 80 loads the &#34;size&#34; of the data block into the initialize register 22 before the data transfer. When the block counter 26 reaches a preset limit, the data in the initialize register 22 is loaded into the block counter 26 to indicate the block size of the next coming block. 
     The Protocol Controller 80 can read the initialization register 22 in order to save its content when it switches to data transfers of a different block size. Additionally, the SPC 80 can restore the old value of the block counter by writing into these registers. 
     The initialization register 22 is programmable by the SPC 80 dynamically. The SPC 80 has a processor which loads the data block size into the initialization register 22 before the data transfer when the block counter 26 reaches its preset limit, then the initialization register 22 information on block size is loaded into the block counter 16 for the next block transfer. This is done when the zero detector circuit 42 senses when the counter 26 has reached zero and thus permits a reloading of the counter. 
     A block size comparator 44 is used to check the block size on the bus 6 with the block size counted by the counter 26. The output of the block size comparator 44 is used to feed the error detection code (EDC) register 40 for comparison to see if the original EDC value does or does not match the internally generated EDC code from generator 28. 
     The output of the zero detector 42 is fed to a pipeline flip-flop 42 f  which is used to set the flip-flop 46 f  which is the error detection code (EDC) error flip-flop. The flip-flop 42 f  can only set up the flip-flop 46 f  after the zero detector 42 has reached its zero value. 
     The data input register 14 is fed to the EDC generator 28 and also to parity checking circuit 30. The parity checking 30 checks for proper parity of each data word being transferred and if a parity error is detected will initiate flip-flop 30 f  to generate a parity error interrupt signal 30 (FIG. 4) as the particular word is undergoing transfer. The EDC generator 28 generates an internal EDC signature for the data being transferred which is then compared to the original EDC signature sent along with the originally transmitted data block. The output of generator 28 is placed in the EDC register 40. From this, the error detection circuit 46 f  can detect whether there has been an error detected or not. If so, then the flip-flop 46 is initiated in order to provide a EDC error interrupt signal on line 46 e , which is conveyed to the control processor 10 d . 
     In the presently described embodiment, the initialize register 22 and the block counter 26 are 16 bytes wide. Thus, the maximum size allowed is 65,536 words of 36 bits each. When an error is detected by the error detection unit 46 or parity error checker 30, then respectively the JK flip-flop 46 f  and the JK flip-flop 30 f  are set by the hardware and latched into the interrupt register for the control processor 10 d . The two flip-flops 46 f  and 30 f  can be reset by the control processor by addressing the flip-flop and performing a write operation on it. The interrupt bit of the interrupt register in the control processor will be reset on the next clock. 
     It may be noted that the EDC error checking system and the parity error checking system can be &#34;disabled&#34; by the SPC 80 during initialization or when data blocks &#34;without EDC signatures&#34; are being transferred. In normal operation with EDC signatures, the system will allow the reporting of interrupts when the EDC error or parity error occurs. 
     The sequence of operation when data blocks are being transferred from the memory buffer 24 d  over to the SCSI Protocol Controller 80 will operate as follows. The initialize register 22 will receive data to sense the size of the block, for example &#34;X&#34; bytes or a block of &#34;Y&#34; bytes). The input register 14 simultaneously copies word by word, the data of the entire block, and the final EDC original signature is placed in the EDC register 40 and is compared with internally generated signature from the signature generator 28. If these match, then there has been no EDC error. On the other hand, if these do not match, then the error detection circuit 46 will activate the EDC error interrupt flip-flop 46 f  in order to send a interrupt signal on line 46 e . Thus, the signature generated in the EDC generator 28 is put in the EDC register 40 for comparison with the original EDC signature. The error detection 46 compares the two signatures and determines whether an EDC error has occurred. When a new block of data of a different size is subsequently being transferred, then the initialize register 22 will read the first word in order to tell the block size of the data block being transferred. 
     Referring to FIG. 7, there is illustrated a timing diagram of the sequence of functions involved. 
     Line A is illustrative of the timing clock signals. Line B shows data on the SPC bus 6 (clock I where the first word indicates the block size as being, for example, 512 bytes. Then on each succeeding clock 2, 3, 4, etc. another word (36 bits) is transferred until, at clock 512, the original EDC signature is transferred. FIG. 6 shows a typical example of an EDC signature. Line C indicates how the initialization register 22 will copy each data word being transferred on SPC bus 6. Line D indicates how input register 14 also copies each data word from the SPC bus 6, in order to generate an internal EDC signature. Line E shows how the EDC generator 28 works to generate a new code value for each word on each clock until, at clock 512, the complete internally generated EDC is completed and to be placed in EDC register 40. At clock 512, this internally generated EDC will be compared to the original EDC signature in register 44 (FIG. 4). If there is a mismatch, then error detector 46 will flag the processor via flip-flop 46 f . Line F indicates how the counter 26 (FIG. 4) counts down each byte from its original setting of 512 bytes. The counter 26 was originally set to 512 (bytes) by the initialization register 22 which received information on the length of the block (block size). The zero detector circuit 21 (FIG. 4) indicates when the 512 bytes of data have been transferred between digital modules, i.e. the end of the data block. Line G illustrates how the EDC comparison register operates to signal a &#34;match&#34; or &#34;mismatch&#34; after clock 512. Line H indicates how the zero detector circuit 44 will reset counter 26 after clock 512. Line I indicates how the parity check circuit 30 checks the parity of each word transferred on each clock 1, 2, 3, . . . 512. 
     Referring to FIG. 1, each channel bus 6 operates through multiplexer 24 x  to buffer memory 24 d . The multiplexer 24 x  is controlled by the arbitration logic 10 a  which allocates equal periods of time access to each of the channel buses 6 a . Thus no channel bus is starved or neglected. The arbitration logic 10 a  receives access request signals from the protocol controllers, SPC 80. For versatility the control processor 10 d  can be programmed to run the arbitration logic 10 a  so that only one requesting SPC will get access to its channel bus in situations where there is no activity needed on the other channel buses. 
     It should be indicated that concurrent I/O operations are on-going on all of the channel buses since while the SPC 0  may have a major I/O cycle to transfer 100 blocks and SPC 1 , may have a major I/O cycle of 200 blocks (with other block numbers in SPC 2 , SPC 3 ), the buffer memory 24 d  at a given time may only be storing 10 blocks for SPC 0  and only have 20 blocks for SPC 1 , etc. 
     In this situation, as seen in FIG. 1, each channel bus 6 has a Data Feeder Control circuit (DFC) designated as F 0 , F 1 , F 2 , F 3  which senses the data block availability in each segment of buffer memory 24 d  and provides a minor I/O cycle to permit transfer of the data block available in buffer memory 24 d  even though more data blocks will be forth coming to complete the major I/O transfer cycle. 
     With the situation where major I/O cycles are continuously being accomplished by using minor I/O cycles on a time sliced basis, it can be seen that each channel bus 6 must have its own dedicated integrity checking circuit, Ic, 81. If the architecture tried to use only one integrity circuit on bus 24 b  (FIG. 1) then it would not be possible to use the time slices of multiple minor I/O cycles to accomplish the major I/O cycles with integrity. 
     Since the buffer memory 24 d  operates at an input/output speed of 80 megabytes per second while the transfers between the peripheral and SPC 80 only run at 10 megabytes per second, it can be seen that there is no penalty for allocating time slices among the several channel buses, since so much more data is passed to the SPC that it must buffer data in internal FIFO registers. 
     Disclosed herein has been a data transfer system providing integrity of data performed on-the-fly by an associated integrity circuit which senses parity for each word transferred and also checks the error detection code (EDC) signature for each block transferred. The integrity circuitry can also be disabled when data transfers involve blocks which do not provide an EDC signature. The on-the-fly integrity checking occurs concurrently on each channel bus that is actively transferring data. Each of the multiple SCSI Protocol Controllers (SPC) can be concurrently operating in data transfer operations between the several peripheral devices and the several protocol controllers (SPCs). Data blocks can be transferred through a series of concurrent minor I/O cycles on each of the channel buses to fulfill a commanded major I/O cycle of block transfers with assurance of integrity. 
     While the preferred embodiment has been described, there may be other configurations which handle the problems of data transfer integrity using the concepts of the attached claims, but which are still taught by the attached claims.