Interface link layer device to build a distributed network

Abstract

An interface link layer device ( 1 ) of an interface which allows the interconnection of different networks to build a distributed network according to the present invention routes complete data packets directly to another interface link layer device ( 1 ) that serves the destination via uplink means ( 10, 11, 12, 13, 14, 17 ) to accept a data packet from a first data bus ( 2 ) that has a predetermined destination on a second data bus and to transmit it via said transmission path ( 3 ) to said other interface link layer device ( 1 ), and downlink means ( 20, 21 ) to output data packets received via said transmission path ( 3 ) from one other interface link layer device ( 1 ) to a predetermined destination on the first data bus ( 2 ). Furtheron, the interface link layer device according to the present invention introduces the concept that not all packets have to be transmitted via the interface on basis of an appropriate acknowledge code and response packet generation of an acknowledge/response means ( 18, 19 ) included in the interface link layer device. The present invention is in particular applicable to build up a disrtibuted network on basis of several IEEE 1394 networks that are interconnected via an interface consisting of a coaxial cable.

1 . A portal for communicating data in-between a source node and a destination node, the portal being connected to the source node via a first serial data bus and connected to a second portal through a transmission path, the second portal being connected to the destination node via a second serial data bus, the portal comprising; 
 means for receiving asynchronous packets corresponding to a request action from said first node and for monitoring all of said received asynchronous packets;    means for deciding whether a destination ID assigned to said received asynchronous packet corresponds to a destination ID identifying said destination node or said second serial data bus;    means for forwarding or discarding said asynchronous packets and for transmitting acknowledgements so that if said destination ID of the received asynchronous packet corresponds to said destination ID identifying said destination node or said second serial data bus, the received asynchronous packet is forwarded to said second portal and a pending acknowledgement indicating a pending action is transmitted to said source node, and else if said destination ID of the received asynchronous packet is different from said destination ID identifying said destination node or said second serial data bus, the received asynchronous packet is discarded.    
   
   
       2 . Portal according to  claim 1 , wherein said means for receiving asynchronous packets is further adapted for receiving asynchronous packets corresponding to a response action, and 
 said means for forwarding or discarding said asynchronous packets and for transmitting said acknowledgements transmits a completed acknowledgement for indicating a completed action, If a packet corresponding to said response action is received by as-id means for receiving asynchronous packets.    
   
   
       3 . A portal for communicating data In-between a source node and a destination node, the portal being connected to a second portal through a transmission path, said second portal being connected to said source node via a first serial data bus and said portal being connected to said destination node via a second serial data bus, the portal comprising: 
 means for receiving asynchronous packets corresponding to a response action from said destination node and for monitoring all of said received asynchronous packets;    mean for deciding whether a destination ID assigned to said received asynchronous packet corresponds to a destination ID identifying said source node or said destination first serial data bus;    means for forwarding or discarding said asynchronous packets and for transmitting acknowledgements so that if said destination ID of the received asynchronous packet corresponds to said destination ID identifying said source node or said destination first serial data bus, the received asynchronous packet is forwarded to said second portal and for transmitting a completed acknowledgement indicating a completed action is transmitted to said destination node, and else if said destination ID of the received asynchronous packet is different from said destination ID identifying said source node or said source bus, the received asynchronous packets is discarded.    
   
   
       4 . Portal according to  claim 3 , wherein said means for receiving asynchronous packets is further adapted for receiving asynchronous packets corresponding to a request action, and 
 said means for forwarding or discarding said asynchronous packets and for transmitting acknowledgements transmits a pending acknowledgement for indicating a pending action, if a packet corresponding to a request action is received by said means for receiving asynchronous packets.    
   
   
       5 . A transaction device for routing asynchronous packets in-between two nodes which are provided in two serial data bus networks, the transaction device comprising: 
 means for receiving asynchronous packets corresponding to a request or response action from one of said nodes via a serial data bus;    means for routing the received asynchronous packets from one to the other serial data bus network through a transmission path;    wherein said routing means, when said routing means receives said request action, transmits a pending acknowledgement for indicating a pending action to the one node via said serial data bus and forwards said request action to the other node through said transmission path, and when said routing means receives said response action, said routing means transmits a completed acknowledgement for indicating a completed action to the one node via said serial data bus and forwards said response action to the other node through said transmission path.    
   
   
       6 . A portal for routing asynchronous packets in-between two IEEE1394 serial bus networks, the portal comprising: 
 means for monitoring all incoming asynchronous packets and for filtering asynchronous packets to be forwarded to the other IEEE1394 serial bus network from said all incoming asynchronous packets;    means for forwarding the filtered asynchronous packets to said other IEEE1394 serial bus network 1  and for transmitting an acknowledgement when said asynchronous packets are forwarded to said other IEEE1394 serial bus network and for discarding the unfiltered asynchronous packets.    
   
   
       7 . A portal for routing asynchronous packets in-between at least two IEEE1394 serial bus networks, the portal comprising: 
 means for monitoring all incoming asynchronous packets of one of said IEEE 1394 serial bus networks;    means for forwarding asynchronous packets to the other IEEE1394 serial bus network if said asynchronous packets to be forwarded have a destination m Identifying the other IEEE 1394 serial bus network or a node provided in said other IEEE1394 serial bus network; and    means for selectively transmitting an acknowledgement indicating a pending action or a completed action to a node of said one IEEE1394 aerial bus network in response to a request action and response action, respectively, originating from said node.    
   
   
       8 . A portal connected to a first data bus and via a transmission path to at least one other portal that is connected to a respective second data bus of a plurality of second data buses, comprising: 
 an uplink section adapted to accept a data packet from the first data bus that has a predetermined destination or that has a channel number of a data channel that leads from the first data bus to one of said respective second data busses and to transmit said data packet via said transmission path to said other portal serving said predetermined destination;    a downlink section adapted to output data packets received via said transmission path from one of said at least one other portal to a predetermined destination on the first data bus; and    an acknowledge code generator adapted to generate and send an acknowledgement to an originator of a data packet accepted from the data bus the portal is connected to.    
   
   
       9 . A portal connected to a first data bus and via a transmission path to a coportal that is connected to a respective second data bus of a plurality of second data buses, comprising 
 a register adapted to store at least one destination ID of at least one predetermined destination:    a controller adapted to accept a data packet from the first data bus that has a predetermined destination ID stored in said register and to transmit it via said transmission path to said co-portal serving said predetermined destination;    a downlink section adapted to output data packets received via said transmission path from said co-portal to a predetermined destination on the first data bus; and    an acknowledge code generator adapted to generate and send an acknowledgement to an originator of a data packet accepted from the data bus the portal is connected to.    
   
   
       10 . A portal connected to a first data bus and via a transmission path to a coportal that is connected to a respective second data bus of a plurality of second data buses, comprising: 
 a register adapted to store at least one channel number of a data channel that leads from the first data bus to one of said respective second data busses;    a controller adapted to accept a data packet from the first data bus that has a channel number of a data channel stored in said register and to transmit it via said transmission path to said co-portal serving said predetermined destination;    a downlink section adapted to output data packets received via said transmission path from said co-portal to a predetermined destination on the first data bus; and    an acknowledge code generator adapted to generate and send an acknowledgement to an originator of a data packet accepted from the data bus the portal is connected to.    
   
   
       11 . A portal connected to a first data bus and via a transmission path to a co portal that is connected to a respective second data bus of a plurality of second data buses, comprising: 
 a first register adapted to store at least one destination ID of at least one destination;    a second register adapted to store at least one channel number of a data channel that leads from the first data bus to one of said respective second data busse;    a controller adapted to accept a data packet from the first data bus that has a predetermined destination stored in said first register or that has a channel number of a data channel stored in said second register and to transmit it via said transmission path to said co-portal serving said predetermined destination;    a downlink section adapted to output data packets received via said transmission path from said co-portal to a predetermined destination on the first data bus; and    an acknowledge code generator adapted to generate and send an acknowledgement to an originator of a data packet accepted from the data bus the portal is connected to.    
   
   
       12 . A portal connected to a first data bus and via a transmission path to at inst one other portal that is connected to a respective second data bus of a plurality of second data buses, comprising: 
 an uplink section adapted to accept a data packet from the first data bus that has a predetermined destination or that has a channel number of a data channel that leads from the first data bus to one of said respective second data busses and to transmit it via said transmission path to said other portal serving said predetermined destination, wherein said data packet corresponds to a request;    a downlink section adapted to output data packets received via said transmission path from one of said at least one other portal to a predetermined destination on the first data bus; and    an acknowledge code generator adapted to generate an acknowledgement of ack_pending to be sent to the originator of a data packet accepted from the data bus the portal is connected to.    
   
   
       13 . A portal connected to a first data bus and via a transmission path to at least one other portal that is connected to a respective second data bus of a plurality of second data buses, comprising: 
 an uplink section adapted to accept a data packet from the first data bus that has a predetermined destination or that has a channel number of a data channel that leads from the first data bus to one of said, respective second data bus and to transmit it via said transmission path to said other portal serving said predetermined destination, wherein said data packet corresponds to a response;    a downlink section adapted to output data packets received via said transmission path from one of said at least one other portal to a predetermined destination on the first data bus; and    an acknowledge code generator adapted to generate an acknowledgement of ack_complete to be sent to the originator of a data packet accepted from the data bus the portal is connected to.    
   
   
       14 . A portal connected to a first data bus and via a transmission path to at least one other portal that is connected to a respective second data bus of a p1w-aRty of second data buses, comprising: 
 an uplink section adapted to accept a data packet from the first data bus that has a predetermined destination or that has a channel number of a data channel that leads from the first data bus to one of said respective second data busses and to transmit it via said transmission path to said other portal serving said predetermined destination, wherein said data packet corresponds to a request or to a response;    a downlink section adapted to output data packets received via said transmission path from one of said at least one other portal to a predetermined destination on the first data bus; and    an acknowledge code generator adapted to generate an acknowledgement to be sent to the originator of a data packet accepted from the data bus the portal is connected to, wherein, if said data packet corresponds to a request, said acknowledgment is equal to ack_pending, and if said data packet corresponds to a response, said acknowledgement is equal to ack_complete.    
   
   
       15 . A portal connected to a first IZKE13O4 serial bus network and via a transmission path to a co-portal that is connected to a respective IEEE1SQ4 serial bus network, comprising: 
 an uplink section adapted to accept a data packet from the first IEEEZS94 serial bus network that has a predetermined destination or that has a channel number of a data channel that leads from the first IEEE1394 serial bus network to one of said respective second IEEE1394 serial bus network and to transmit it via said transmission path to said co-portal serving said predetermined destination, wherein said data packet corresponds to a request or to a response;    a downlink section adapted to output data packets received via said transmission path from said co-portal to a predetermined destination on the first IEEE1394 serial bus network; and    an acknowledge code generator adapted to generate an acknowledgement to be sent to the originator of a data packet accepted from the serial bus network the portal is connected to, wherein, if said data packet corresponds to a request, said acknowledgement is equal to ack_pending, and if said data packet corresponds to a response, said acknowledgement is equal to ack_complete.    
   
   
       16 . A portal connected to a first data bus and via a transmission path to at least one other portal that is connected to a respective data bus of a plurality of second data busses, comprising; 
 uplink means to accept a data packet from the first data bus that has a predetermined destination or that has a channel number of a data channel that leads from the first data bus to one of the respective second data bus and to transmit it via said transmission path to said other portal serving said predetermined destination; and    downlink means to output data packets received via said transmission path from one of said at least one other portal to a predetermined destination on the first data bus,    wherein said uplink means comprise a first register that reflects destination identifiers which will be accepted, and    wherein said destination identifier is a bus identifier of said respective second data bus and said first register comprises a bus enable register identifying said respective second data bus that is serving said predetermined destinations.    wherein said uplink means comprises a packetizer that is able to repack data packets received from the first data bus into a format of the transmission path that is different to the format of the first data bus.    
   
   
       17 . A portal connected to a first data bus and via a transmission path to at least one other portal that is connected to a respective data bus of a plurality of second data busses, comprising: 
 uplink means to accept a data packet from the first data bus that has a predetermined destination or that has a channel number of a data channel that leads from the first data bus to one of the respective second data bus and to transmit it via said transmission path to said other portal serving said predetermined destination; and    downlink means to output data packets received via said transmission path from one of said at least one other portal to a predetermined destination on the first data bus,    wherein said uplink means comprise a first register that reflects destination identifiers which will be accepted, and    wherein said destination identifier is a bus identifier of said respective second data bus and said first register comprises a bus enable register identifying said respective second data bus that is serving said predetermined destinations,    wherein said downlink means comprises a packet separator that is able to repack data packets received from the transmission path into a format of the first data bus that is different to the format of the transmission path.    
   
   
       18 . A portal adapted to communicate data in-between a source node and a destination node, the portal being connected to the source node via a first serial data bus and connected to a second portal through a transmission path, the second portal being connected to the destination node via a second serial data bus, the portal comprising: 
 an uplink section adapted to receive asynchronous packets corresponding to a request action from said first node and to monitor all of said received asynchronous packets; and    a controller adapted to decide whether a destination ID assigned to said received asynchronous packet corresponds to a destination ID identifying said destination node or said second serial data bus, and further adapted to forward or discard said asynchronous packets; and    an acknowledge code generator adapted to transmit acknowledgements so that if said destination ID of the received asynchronous packet corresponds to said destination ID identifying said destination node or said second serial data bus, the received asynchronous packet is forwarded to said second portal and a pending acknowledgement indicating a pending action is transmitted to said source node, and else if said destination II) of the received asynchronous packet is different from said destination ID identifying said destination node or said second serial data bus, the received asynchronous packet is discarded.    
   
   
       19 . Portal according to  claim 18 , wherein said uplink section is further adapted to receive asynchronous packets corresponding to a response action, and 
 said acknowledge code generator transmits a completed acknowledgement for indicating a completed action, if a packet corresponding to said response action is received by said uplink section.    
   
   
       20 . A portal adapted to communicate data in-between a source node and a destination node, the portal being connected to a second portal through a transmission path, said second portal being connected to said source node via a first serial data 
 bus and said portal being connected to said destination node via a second serial data bus, the portal comprising:    an uplink section adapted to receive asynchronous packets corresponding to a response action from said destination node and to monitor all of said received asynchronous packets;    a controller adapted to decide whether a destination ID assigned to said received asynchronous packet corresponds to a destination ID identifying said source node or said destination first serial data bus; and further adapted to forward or discard said asynchronous packets; and    an acknowledge code generator adapted to transmit acknowledgements so that if said destination ID of the received asynchronous packet corresponds to said destination ID identifying said source node or said destination first serial data bus, the received asynchronous packet is forwarded to said second portal and for transmitting a completed acknowledgement indicating a completed action is transmitted to said destination node, and else if said destination ID of the received asynchronous packet is different from said destination ID Identifying said source node or said source bus, the received asynchronous packets is discarded.    
   
   
       21 . Portal according to  claim 20 , wherein said uplink section is further adapted to receive asynchronous packets corresponding to a request action, and 
 said acknowledge code generator transmits a pending acknowledgement for indicating a pending action, if a packet corresponding to a request action is received by said uplink section.    
   
   
       22 . A transaction device adapted to route asynchronous packets in-between two nodes which are provided in two serial data bus networks, the transaction device comprising: 
 an uplink section adapted to receive asynchronous packets corresponding to a request or response action from one of said nodes via a serial data bus;    a controller adapted to route the received asynchronous packets from one to the other serial data bus network through a transmission path, wherein said controller, when said controller receives said request action, transmits a pending acknowledgement for Indicating a pending action to the one node via said serial data bus and forwards said request action to the other node through said transmission path, and when said controller receives said response action, said controller transmits a completed acknowledgement for indicating a completed action to the one node via said serial data bus and forwards said response action to the other node through said transmission path.    
   
   
       23 . A portal adapted to route asynchronous packets In-between two IEEE 1594 serial bus networks, the portal comprising: 
 a controller adapted to monitor all incoming asynchronous packets and to filter asynchronous packets to be forwarded to the other IEEE1394 serial bus network from said all incoming asynchronous packets:    a downlink section adapted to forward the filtered asynchronous packets to said other IEEE1394 serial bus network, and to transmit an acknowledgement when said asynchronous packets are forwarded to said other IEEE1394 serial bus network, and further adapted to discard the unfiltered asynchronous packets.    
   
   
       24 . A portal adapted to route asynchronous packets in-between at least two IEEE1394 serial bus networks, the portal comprising: 
 a controller adapted to monitor all incoming asynchronous packets of one of said IEEE 1394 serial bus networks;    a downlink section adapted to forward asynchronous packets to the other IEEE1394 serial bus network if said asynchronous packets to be forwarded have a destination ID identifying the other IEEE 1394 serial bus network or a node provided in said other IEEE 1394 serial bus network; and    an acknowledge code generator adapted to selectively transmit an acknowledgement indicating a pending action or a completed action to a node of said one IEEE 1394 serial bus network in response to a request action and response action, respectively, originating from said node.