Communications network

Abstract: A communications network including several ports 30, 32, 34, 36, 42, 44, 46 and 48 where each port is connected to at least one data processing system element. The ports are interconnected by an information bus 52. Additionally, the ports are connected to a matrix switch 40 that has the capability of providing a direct communications channel between any two of the ports. Each port includes control circuitry for communicating with other ports over the bus 52 and, through the bus, regulating the matrix switch in order for the matrix switch 40 to provide the direct communication channels between two ports.

Description: This invention relates to communications networks and provides for information transfer between different data processing systems elements. Data processing systems require information transfer between data processing system components. There are several methods of providing information transfer within data processing systems. One method that is very advantageous is to transfer information simultaneously between several data processing system elements by using a cross point switch. An example of a cross point switch is illustrated in US-A-4,630,045. A cross point switch provides simultaneous communication connections between pairs of data processing system elements so that several of these connected pairs may exchange information at the same time through these switch. The cross point switch in US-A-4,630,045 illustrates the prior art implementation of a cross point switch, whereby the ports of the cross point switch that are connected to the data processing elements are interconnected to a switching matrix and a centralised control circuit which governs the operations of the ports and their interconnection through the switch matrix itself. US-A-4,814,762 illustrates another embodiment of a cross point switch where the actual communications between the ports of a cross point switch are contained in a delta network. When a port is attempting to access another port it sends a request message for the specified connection over the delta network. This communication takes place outside the cross point switch itself. The present invention is intended to provide conmunications through the cross point switch and, thus, provides inband communication for not only the data transfer but also for specifying the interconnections desired. US-A-4,752,777 teaches the delta network for control of cross point switch ports. US-A-4,695,999 discloses a multiplaned cross point switch. However, the control of ports connected to the cross point switch is not disclosed. US-A-4,845,722 discloses an interconnect coupler system that includes a centralised switch logic circuit for controlling the switch matrix. US-A-4,580,011 discloses a switching system having a centralised controller that receives control signals from the line couplers to direct interconnection through a cross point switching matrix. IBM Technical Disclosure Bulletin , Vol. 28, No. 2, July, 1985, pp. 510-512, discloses a switch matrix control system having ports that communicate with a central management controller to control the operation of a cross point switch. IBM Technical Disclosure Bulletin , Vol. 29, No. 3, August, 1986, pp. 1356-1360, discloses a reconfigurable switch designed to support multiple networks of different types. This configuration includes a switch controller that controls the access of the ports to the switch. IBM Technical Disclosure Bulletin , Vol. 32, No. 1, June, 1989, pp. 427-433, discloses a controller for a packet bus. A packet bus allows only a single transfer of information at a time, as opposed to a cross point switch which allows simultaneous and continuous transfers of information between communicating pairs of system elements. IBM Technical Disclosure Bulletin , Vol. 20, No. 2, July, 1977, pp. 816-817, discloses a cross point switch with a controller which regulates port access over a cross point switch. IBM Technical Disclosure Bulletin , Vol. 29, No. 4, September, 1986, pp. 1769-1771, discloses a switch providing "packet-like" communication capability. Packet transmission provides for only a single pair of communications at a time. IBM Technical Disclosure Bulletin , Vol. 27, No. 4B, September, 1984, pp. 2704-2708, discloses a three level switching mechanism for a packet transmission network using central control to establish a path interconnection. IBM Technical Disclosure Bulletin , Vol. 24, No. 7A, December, 1981, pp. 3352-3356, discloses a centralised control switching mechanism allowing interprocessor communication through input/output channels. IBM Technical Disclosure Bulletin , Vol. 28, No. 8, January, 1986, pp. 3272-3273, describes a telecommunication system using distributed parallel processors to control a distribution network. Other methods of data transfer are provided in the prior art. One such method employs an information bus allowing only one message passing at a time. An example of this bus method is in US-A-4,586,175, which discloses a bus controlled by two bus controllers. US-A-4,363,093 discloses a local area network intercommunications system between processors. Again, only one message will be allowed on the system at a time. US-A-4,821,170 also discloses a system providing two system buses, but not employing a switch to facilitate intersystem communication. Other examples of bus type commnunication are disclosed in US-A-4,704,606, which discloses a packet switching system for variable length packets. US-A-4,631,534 discloses a packet switching system where each port includes the intelligence to provide destination port and station addresses in the packets. US-A-4,630,258 discloses a packet switching system using an N x M switch from N input ports to be routed to M output ports. The switch is centrally controlled. US-A-4,773,069 discloses a data transmission network including modems, and having at least two controllers interconnected to the modems. Other general communication teachings showing a switch include IBM Technical Disclosure Bulletin , Vol. 25, No. 7A, December, 1982, pp. 3578-3582, which discloses a host processor communicating with a plurality of satellite processors through a data switch matrix. The switch and the operation of the satellites are being controlled by the host processor. IBM Technical Disclosure Bulletin , Vol. 29, No. 7, December, 1986, pp. 3070-3072, discloses a rotary switch. IBM Technical Disclosure Bulletin , Vol. 30, No. 1, June, 1987, pp. 403-405, discloses a single port providing access to a digital telephone switch system. IBM Technical Disclosure Bulletin, Vol.ll, No.10, March 1969, pp 1231-1232, discloses a multiply redundant switching arrangement for a digital computer. All the prior art previously discussed discloses the use of centralised control for the switching network. An additional prior art teaching, EP-A-0,356,110, discloses the use of distributed control of the switching network, where each processor has its own control circuit. However, in this latter teaching, the destination processor must send a dedicated control signal to the crossbar switch fabric, thus taking up valuable bus cycles. It is an object of the present invention to provide a distributed control across the ports connected to the switch more cost effectively to regulate the interconnection of the ports to the switch, and, thus, communication across the switch. In accordance with the present invention, a communications network is provided that includes a plurality of ports with each port connected to at least one data processing system element. A bus is provided that interconnects the ports. A matrix switch is provided that is connected to the ports and the bus connecting the ports. The matrix switch provides the capability to connect a communications channel between any two of the ports. Each of the ports includes control logic connected to the bus for communicating with other ports and the matrix switch to regulate the establishment of communications channels between ports. The scope of the invention is defined in the appended claims; and how it can be carried into effect is hereinafter particularly described with reference to the accompanying drawings in which: Fig. 1 is a block diagram illustrating eight systems connected to a first cross point switch and one connected to a second cross point switch; Fig. 2 is a block diagram illustrating the contents of a cross point switch; Fig. 3 is a block diagram illustrating the contents of a cross point switch port circuit; Fig. 4 is a block diagram of the cross point switch; Fig. 5A is an event diagram illustrating the events between port A, port B and the cross point switch in establishing a link between port A and port B; Fig. 5B is an event diagram illustrating a disconnection between port A and port B; Fig. 6 is a flow chart illustrating the control of the port when a communications frame is received from its link; Fig. 7 is a flow chart illustrating the control of the port when a request is received from the communications bus; Fig. 8 is a flow chart illustrating the termination of communications by the port; and Fig. 9 is a flow chart illustrating the control of the matrix switch during the port-to-port communications. A communications system (Fig. 1) includes several systems 14, 16, 18, 20, 22, 24, 26 and 28 that are each connected to a cross point switch 10. Each of the systems, such as system 14, is connected to cross point switch 10 through a port 8. Note that each system, such as system 24, can be alternatively connected to additional cross point switches (such as switch 12) for redundancy or connectivity. In the preferred embodiment, system 14 and system 24 are RISC System/6000 workstations that are connected by a serial fibre optic channel to the cross point switch 10. In this preferred embodiment, each RISC System/6000 can include four ports to implement the serial link interconnections. An example of a protocol used with the serial link interconnection is ESCON (Enterprise System Connection for the IBM 3090 Enterprise System Serial Input/Output Channel). It should be understood in this preferred embodiment that when a system is to connect to another system to provide information to the second system, all information is provided through this serial link fibre optic channel. The originating system will send out a frame of information of up to thirty two bytes to initially establish communications with the receiving system. After the first frame has been sent and received, establishing the connection through the cross point switch 10, this connection is maintained so that the originating system may continually pass additional frames of information to the receiving system until a disconnect frame has been sent to alert the receiving system and the switch 10 that it is being disconnected. In the preferred embodiment, the cross point switch is an N x N switch supporting N x N ports to provide simultaneous communication between connected ports and the systems connected to the ports. In the preferred embodiment of the cross point data switch 10 (Fig. 2), a 16 x 16 switch 40 is provided, but for this description only eight ports of the sixteen are shown. Each port 30 is connected to a port arbitration bus 50, port control bus 52 and data transfer lines (such as lines 54 and 55 for ports 30 and 42, respectively). Each of the ports is connected through these data lines to the 16 x 16 matrix switch 40. The matrix switch 40 can be an off-the-shelf part such as the GIGABIT Logic 10G051, which provides cross point interconnection between ports (with the exception of logic 600 and address latches 602, Fig. 4). In the preferred embodiment, each port provides an optical-to-electrical conversion in order that the information is passed electrically between ports through the 16 x 16 matrix 40. Initially, a port, such as 30, may attempt a connection to another port, such as port 32. First, port 30 requests arbitration. That is, port 30 requests a grant on the arbitration bus 50 through a bus arbiter 38. Upon receiving a grant, a connect request is passed over the control bus 52 to port 32. A status is then received. In Fig. 2, an example is illustrated where port 32 is attempting to contact port 30 by sending a request symbolically indicated by the arrow 58. Port 30 sends a busy signal indicated symbolically by the dashed arrow 56 back to port 32 declining the transfer request. Note that during this initial attempt at port-to-port connection, the 16 x 16 matrix has not been accessed. This is possible by having the control of the switch mechanism distributed among the ports. In other words, it is only after confirmation is received that the data transfer can take place the switch 40 is involved in the connection between the ports. The matrix switch 40 is connected to the control bus 52. This may enable the matrix switch 40 to respond to commands directed to it. In the preferred embodiment, the only commands that are directed to the matrix switch 40 are those of a diagnostic nature. During normal operation, the matrix switch 40 merely monitors the control bus 52 and the control communication between ports to determine when connections are to be made or terminated. When connections are made, lines such as 54 are connected to lines such as 55 to allow for data transfers between ports such as port 30 and port 42 without requiring explicit commands to the switch from the ports or from some other control. The disconnection operation is performed by the matrix switch 40 without any commands from the ports. The matrix switch 40 eavesdrops on the command bus 52 to determine when the disconnection is to be made by examining the commands for a disconnect on the control bus 52. When a termination frame is being sent from one system to another, the matrix switch 40 by monitoring the control bus 52 automatically determines the connection is to be broken, thus saving time by not requiring a separate command protocol to tell the matrix switch to disconnect. This is important because the disconnection operation is a high priority, as further connections with either of these ports can only be made when this disconnection occurs. Fig. 3 is a block diagram of the logic contained in each port, such as port 30. The master control state machine and connect/busy state machine 78 control the operation of the port logic. State logic 78 is connected to an interrupt control 82 that provides interrupts for error conditions to and from the control bus 52. The state logic 78 is further connected to the handshake logic 88. The handshake logic operation is of the type discussed in IBM Technical Disclosure Bulletin , Vol. 32, No. 6A, November, 1989, pp. 21-22. When a frame is first received from a system, it is received over a bus 59B where it is initially latched a character at a time in a receive register 102. The contents of this register are then loaded into the connect/synchronisation buffer 104, where write control or read control logic 90 and 92, respectively, together with state logic 78, determines whether buffer 104 acts as a pass-through First-In/First-Out buffer or a capture buffer. The write control 90 determines where in the buffer 104 the data is to be written. The read control logic 92 determines whence in the buffer 104, the next character is to be read out. The decode and error detection logic 106 is also connected to the state logic 78 to signify any error conditions. If the frame is to be passed to another port, a request for connection is passed through the control bus. As discussed earlier, a port sends a request to the bus arbiter 38 over bus 50 through the arbitration and control bus interface 100. Upon a grant, the port state machine 78 sends a connect request and evaluates the status received over the control bus 52 from the port to be connected. If the port to be connected is not busy, then the connection is automatically established by the matrix 40 and the data from the connect/synchronisation buffer 104 is passed through register 108 onto the data line 54B to the matrix switch. The receive multiplexer 94 determines if data from the link 59B or the handshake logic 88 is to be loaded into register 108. Likewise, data being received from the matrix switch on line 54A passes through the register 80 through a merge logic circuit 76 which prevents block code errors through the transmit multiplexer 72 to the transmit register 70 to be passed out on bus 59A. Note that in the transmission side, both busy and reject logic 74 and decode and error detect logic 84 are provided for error conditions. The busy/reject logic 74 determines when a busy indication has been received from the control bus 52 and provides a busy frame on line 59A. Frame buffer 86 is provided to transmit previously specified frames indicating specific error conditions. Fig. 5A is an event diagram illustrating an interconnection between port A and port B. In Fig. 5A, a frame is first received by a port on a bus such as 59 (Fig.2) at event 120. At event 122, the port logic examines the frame and determines to establish a connection and, at event 124, to arbitrate for the control bus. The bus arbiter 38 receives the request at event 126 and grants the request at event 128. At that time, the port A logic issues a connect request 130 which includes the port addresses involved on the control bus 52 indicated by event 132. The matrix logic 600, Fig. 4, observes this request at event 134, and latches the addresses of the port which are latched in latches 602 while the port B logic sees this request at event 136. The port B logic then sends a response 142, which is seen by the matrix logic 600 at event 140 over the control bus 52, as illustrated by event 138. This response is read by the port A logic at event 144. In this example, a successful connection is being performed. Therefore, the matrix logic 600 loads the port address from latches 602 to the registers such as 614 and 624 to enable the data select circuits 608 and 620 to connect internal bus 606 to internal bus 622. Port A logic then provides handshake signals with port B over the matrix bus, such as 54A and 54B in events 148 and 150. First handshake out events 152 and 154 are provided from both ports and then from both ports handshake in events 156 and 158 are provided back to the opposing ports. Note that the matrix logic has automatically connected ports A and B through the matrix switch 40 at event 146. Finally, the frame is sent at event 160 out on the matrix bus at event 162 to the matrix in line to port B at event 166 where the port logic examines the frame at event 164. This frame is then provided on the output of the link to the connected device at event 168. Fig. 5B is an event diagram illustrating a disconnect operation. In this example, port A receives a disconnect frame from its connected device at event 200. This is passed to the matrix out bus event 202. This is received by port B on the matrix in bus at event 208 where the logic checks the frame at event 206 and the frame is dispatched to the linked device at event 204. The logic in port B then determines to arbitrate for the control bus at event 212 and an arbitration request is received by the bus arbiter 38 at event 210, which grants the request at event 214. The port B logic then issues the disconnect command at event 222, which is seen on the control bus at event 218, by the matrix logic at event 220, and by port A logic at event 216. Then the handshake is provided through the control bus at events 232 and 224 by ports B and A, respectively, through the matrix in and matrix out lines for the respective ports at events 226, 228, 234 and 236, respectively. The important event is when the matrix logic 40 automatically disconnects ports A and B at event 230 by eavesdropping on the command bus and having seen the disconnect command successfully issued. It should be understood by those skilled in the art that by eavesdropping on the bus to see connect commands and disconnect commands, that further bus cycles are not required for controlling the switch, even though the switch operates in a manner to maintain an autonomous relationship between the ports. Fig. 6 is a flow chart illustrating the state logic 78 of a port when it receives a frame. In block 300 a frame is received from the device connected to the link side of the port. The logic first determines in step 302 if the frame is for an existing connection. This is an event when a previous frame has established the connection and this existing frame is merely one in a sequence of frames that is being passed through the existing connection. In step 304, the frame is passed through the existing connection to the matrix bus to the matrix switch. The control logic then returns to step 300 to wait for the next frame. However, if in step 302, the connection has not been previously established, the control logic determines in step 306 if the buffer 104 is full. If so, the frame is discarded in step 308 and the control logic returns to wait for another frame. If the frame buffer is not full, the frame is placed in the buffer in step 310 and the control logic arbitrates for the control bus in step 312. In step 314, the logic waits for the grant to be received, at which time it proceeds to issue a connect request in step 318. In step 320, the control logic reads the requested port's response. The response is examined in step 324 to determine if it is successful. If not, a further examination is made in step 326 to determine if it is busy, at which time a busy message is passed. If not, it is examined in step 328 to determine if the port indicates that it is malfunctioned, at which time a malfunction message is passed back in step 334. In either case, the buffer 104 is flushed in step 316. Returning to step 324, if the response is successful, the port is marked as connected in step 330 and the send handshake is started in step 336 through the matrix. When the receive handshake is received in step 338 it is examined in step 340. If it is not alright, an error report is issued in step 342, at which time the buffer 104 is flushed in step 316. Returning to step 340, if the handshake is completed successfully, the frame is then sent to the matrix switch 40 in step 344 and the logic proceeds to node A in Fig. 8. In Fig. 7, a flow chart is provided that illustrates the operation of port control logic when a request has been received from the control bus. This occurs in step 400. At that time, the port determines whether or not it is connected in step 402. If so, the port responds in step 404 with a busy signal. If not, in step 406, the port responds that it can complete the connection. In step 408, the port stores an indication that it is connected, and, in step 410, provides the handshake. The response handshake is received in step 412 and is examined in step 414 to determine if it is alright. If not, then an error is reported in step 416 and the port marks itself as unconnected in step 418, returning to step 400. If, however, in step 414 the handshake response is alright, then the control logic proceeds to node A. Node A is illustrated in Fig. 8 as connecting the logic in Figs. 6 and 7 to step 420, which passes frames from the matrix to the link. Frames may also be passed from the link to the matrix, if required. In step 424, the port logic determines if a disconnect frame has been received from the matrix switch. If not, then the port logic determines in step 426 if a disconnect command has been received from the control bus. If not, then the port logic returns to step 420 to continue frame passing. Returning to step 424, if a disconnect frame has been received through the matrix switch, then, in step 428, am issue disconnect command on the control bus is made. The port is then marked as unconnected in step 430. Likewise, in step 426, if the disconnect command is received from the control bus, the port is marked unconnected in step 430. Fig. 9 is a flow chart illustrating the control logic of the matrix switch 40. Note that the matrix switch 40 is a slave device that eavesdrops on the control bus and controls the switch connections accordingly. In step 500, the switch control logic determines if a command has been issued on the control bus. If not, it continues to wait. If a command is present, then the port addresses are latched in step 502. In step 504, the command is examined to see if it is a connect command. If so, in step 506, the port response is then monitored and checked. If the response is alright in step 508, then the bus connection between the ports is connected in step 514. Likewise, in step 510, the command is examined to see if it is a disconnect command, and, if so, then the port connections are disconnected in step 512. It should be apparent to one of skill in the art that the eavesdropping logic of the matrix switch can also be used to control functions other than the mere connection or disconnection of devices. For example, the eavesdropping logic of the matrix switch can be used to determine when a specific event has occurred by examining information related to the connection of the two ports and for supervising the operation of autonomous devices such as preventing two consecutive connections to the same port or a disconnect operation to an unconnected port. While this invention has been described with reference to the illustrated embodiment, this description is not intended to be construed in a limiting sense. Various modifications of the illustrated embodiment, as well as other embodiments within the scope of the invention will become apparent to those persons skilled in the art upon reference to this description. A communications system involving eavesdropping is described and claimed in EP-A-0 491 569, filed contemporaneously with this application. A serial link communications system is described and claimed in EP-A-0 492 972, filed contemporaneously with this application.

Claims: A communications network comprising a plurality of ports (30), each connected to at least one data processing system element, bus means (52) interconnecting the ports (8) for providing information transfer between the ports (30) and a matrix switch (10) connected to the ports (30) and the bus means (52); characterised by said matrix switch (10) for latching an identifier of at least one of the ports (30) prior to approval of a requested connection by monitoring communications between the ports (30) on the bus means (52) and for providing a direct communications channel between any two of the ports (30) upon approval of the requested connection; and each port (30) including control means connected to the bus means (52) for communicating with other ports (30) to immediately establish direct communications through the matrix switch (10) for an undefined time interval. A network according to Claim 1, wherein each port (30) includes logic (78) connected to the bus means (52) to determine a communications state of any other of the ports (30). A network according to Claim 1 or 2, wherein each port (30) includes means (102) for receiving communications request from its connected data processing system element (14) and means for communicating with another port (30) via the bus means (52) for establishing a communications channel through the matrix switch (10). A network according to Claim 1, 2 or 3, wherein the bus means (52) includes an arbitration means (38) for receiving bus access requests from ports (30) and granting control on the bus means (52) for port to port communications over said bus means (52). A communications network according to any preceding Claim, wherein each port (30) includes means (108) for requesting a communications channel through the matrix switch (10) to another port (30) and means (80) for receiving an acknowledgement from another port (30) indicating that such request has been granted. A network according to Claim 5, wherein the matrix switch means (10) includes means (600) for establishing a communications channel between the requesting port (30) and the granting port (30). A network according to any preceding Claim, wherein each port (30) is connected to the matrix switch (10) by two communications lines (54A, 54B) for two way communications between the matrix switch (10) and the connected port (30). A method for establishing a continuous communications channel between data processing elements connected to different ports (30) in a communications network having a plurality of ports (30), each connected to at least one data processing element and each port connected to all other ports with a bus (52), the network further including a matrix switch (10) interconnected to each port (30) and the bus (52), comprising the steps of: (a) receiving by the port (30) a request from a connected data processing element (14) for a communications channel through a second port to a second data processing element; (b) sending a request for establishing a communications channel from the receiving port to the second port over the bus (52); characterised by (c) latching an identifier of at least one of the ports (30), by the matrix switch (10) which monitors communications between the ports (30) on the bus (52), prior to grant of the request by the second port; and (d) immediately establishing said communications channel through the matrix switch (10), which monitors communications between the ports (30) on the bus (52), upon the grant of the request by the second port for an undefined time-interval. A method according to Claim 8, wherein step (b) includes the steps of (b1) requesting access to the bus (52) and (b2), upon grant of said access, requesting through the bus (52) access to the second port through the matrix switch (10). A method according to Claim 9, wherein step (c) further includes denying matrix switch (10) access by the receiving port or the second port of any other requesting ports while the communications channel is established.

Inventors: KAISER JOHN MICHAEL, YOUNGBLOOD LOYAL DAVID, KAISER, JOHN MICHAEL, YOUNGBLOOD, LOYAL DAVID
Applicants: IBM, INTERNATIONAL BUSINESS MACHINES CORPORATION
Application year: 1991
Main classification: H04L12
IPC codes: H04L12, G06F15, G06F13