WO2009074840A2 - Transmission de façon séparée d'une partie des informations de protocole - Google Patents

Transmission de façon séparée d'une partie des informations de protocole Download PDF

Info

Publication number
WO2009074840A2
WO2009074840A2 PCT/IB2007/003922 IB2007003922W WO2009074840A2 WO 2009074840 A2 WO2009074840 A2 WO 2009074840A2 IB 2007003922 W IB2007003922 W IB 2007003922W WO 2009074840 A2 WO2009074840 A2 WO 2009074840A2
Authority
WO
WIPO (PCT)
Prior art keywords
dfonp
stpi
node
frame
switch
Prior art date
Application number
PCT/IB2007/003922
Other languages
English (en)
Other versions
WO2009074840A3 (fr
Inventor
George Madathilparambil George
Susan George
Mammen Thomas
Original Assignee
George Madathilparambil George
Susan George
Mammen Thomas
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by George Madathilparambil George, Susan George, Mammen Thomas filed Critical George Madathilparambil George
Priority to PCT/IB2007/003922 priority Critical patent/WO2009074840A2/fr
Publication of WO2009074840A2 publication Critical patent/WO2009074840A2/fr
Publication of WO2009074840A3 publication Critical patent/WO2009074840A3/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00Packet switching elements
    • H04L49/25Routing or path finding in a switch fabric
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/324Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC

Definitions

  • the present invention relates to efficient transfer of datalink frame or network packets in a "custom" network.
  • the network is "custom" as all switches and end nodes need to create or process datalink frames or data packets of special formats.
  • the OSI, or Open System Interconnection, model defines a networking framework for implementing protocols in seven layers. Most networking protocols do not implement all seven layers, but only a subset of layers. For example, TCP and IP protocol corresponds to layers 4 (TCP) and 3 (IP) respectively. Network packets contain protocol layer information corresponding to the packet. For example, a TCP/IP packet contains a header with both TCP and IP information corresponding to the packet.
  • the physical layer (layer 1) specifies how a bits stream is created on a network medium and physical and electrical characteristics of the medium.
  • the datalink layer (layer 2) specifies framing, addressing and frame level error detection. For outgoing . packets to the network, the datalink layer receives network packets from networking layer (layer 3) and creates datalink frames by adding datalink (layer 2) protocol information and passes the frame to the physical layer. For incoming packets from network, datalink layer receives datalink frames from physical layer (layer 1), removes the datalink (layer 2) protocol information and passes network packet to the networking layer.
  • the network layer (layer 3) specifies network address and protocols for end to end delivery of packets.
  • Network packets contain protocol layer information corresponding to the packet.
  • Fig. IA illustrates a network packet containing 010001 layer 1, 010002 layer 2, 010003 layer 3, 010004 layer 4 headers, 010005 Data and 010008 layer 1, 010007 layer 2, 010006 layer 3 trailers.
  • Fig. IB illustrates a network packet with 010101 layer 1, 010102 layer 2 (data link) , 010103 layer 3 (networking) and 010104 layer 4 (transport) headers and 010108 layer 1 and 010107 layer 2 trailers and 010105 Data.
  • the corresponding header and trailer together contain all the protocol information required to send the packet/frame to the the consumer of the data in a remote node.
  • headers/trailers corresponding to a TCP/IP packet in a lOBaseT Ethernet LAN are: 1. Physical layer header contains Start-of-Stream
  • Data link layer header contains Preamble, Start-of- Frame Delimiter, Ethernet Addresses, Length/Type Field etc.
  • IP header contains Version, Length, IP Address etc.
  • TCP header contains Port Numbers, Window, Flags etc.
  • Datalink layer trailer contains 32 bit FCS
  • Physical layer trailer contains End-of-Stream Delimiter .
  • US Patent 6,917,620 specifies a method and apparatus for a switch that separates the data portion and the header portion. This method has a disadvantage that overhead and logic for separating the data portion and the header portion and then combining the header portion and the data portion before transmission is required. This method also cannot consolidate headers from more than one packet for transmission to the next node or delay packet arrival if the destination path of the packet is congested and therefore, cannot avoid congestion.
  • the header portion of a packet is decoded prior to the receipt of full packet to determine the destination node.
  • This invention can help with faster processing of the packet within a switch. This method cannot consolidate headers from more than one packet for transmission to the next node or delay packet arrival if the destination path of the packet is congested and therefore, cannot avoid congestion.
  • US Patent 6,032,190 specifies an apparatus and method of separating the header portion of an incoming packet and keeping the header portion in a set of registers and combining the header portion with the data portion before transmitting the packet.
  • This method has a disadvantage that overhead and logic for separating the data portion and the header portion is required.
  • This method cannot consolidate headers from more than one packet for transmission to the next node or delay packet arrival if the destination path of the packet is congested and therefore, cannot avoid congestion.
  • US Patent 6,408,001 improves transport efficiency by identifying plurality of packets having a common destination node, transmitting at least one control message, assigning a label to these packets and removing part or all of the header.
  • This method has a disadvantage that switches need to identify messages with a common destination node and additional logic to remove the header and add a label. This method cannot delay packet arrival if the destination path of the packet is congested and therefore, cannot avoid congestion .
  • the Separately Transmitted Protocol Information is referred to as STPI. Network congestion can be reduced or avoided using STPI.
  • DFoNP which contains the data and rest of the protocol information not contained in STPI, corresponding to each STPI.
  • DFoNP there should be only one DFoNP corresponding to each STPI.
  • the creation of STPI and DFoNP is done by the originator of the frame or packet such as an operating system in an end node.
  • the format (contents and location of each information in a frame or packet) of the frame or packet containing STPI and DFoNP should be recognized by the final destination of the frame or packet.
  • the format of STPI and DFoNP should also be recognized by switches in the network. So preferably, all STPIs and DFoNP in a given network should be of fixed formats.
  • one or more STPIs are transmitted in a datalink frame or a network packet.
  • the datalink frame containing STPIs is referred to as STPI Frame.
  • the network packet containing STPIs is referred to as STPI packet.
  • the switches in this case should be capable of extracting each STPI in an incoming STPI Frame or STPI packet and forwarding it to the next node in a different STPI Frame or STPI
  • the switches can add each STPI from an incoming STPI Frame or STPI Packet into an STPI Frame or STPI Packet it creates.
  • the layer 2 address in the datalink frame containing multiple STPIs will be the next hop node address .
  • STPI Frame or STPI Packet contains the number of STPIs or length of the STPI frame.
  • STPI Frame or STPI Packet contains the offset or position of STPIs in the STPI frame - this is required only if STPIs supported by the network are not of fixed length.
  • STPI Frame or STPI Packet does not contain the number of STPIs and switches in the network are capable of identifying the number of STPIs from length of the frame as they are of fixed length.
  • protocol information contained in STPI may not be contained in the corresponding DFoNP.
  • protocol information contained in STPI and the corresponding DFoMP need not be mutually exclusive.
  • the switches obtain both STPI and the corresponding DFoNP before the STPI and the corresponding DFoNP are forwarded.
  • STPI need not be forwarded to the end node if sufficient protocol information is contained in the corresponding DFoNP.
  • the proposed invention can be employed for data, control and/or RDMA packets in a network.
  • the proposed method allows switches to read more than one STPI, and then delay obtaining the corresponding DFoNP.
  • the DFoNP may be read or forwarded in a different order compared to the order in which STPI are read or forwarded. This method allows switches to optimize resources and packet/frame forwarding efficiency.
  • STPI contain temporary information such as current node or port number of the node containing the corresponding DFoNP.
  • STPI also contains an address of a buffer containing the corresponding DFoNP or an offset in a buffer where the corresponding DFoNP is stored or an index of the corresponding DFoNP in an array. This information helps in associating STPI to the corresponding DFoNP.
  • the exact information contained in STPI whether it is an address or an offset or an index or a combination of these is implementation specific.
  • STPI may contain originating node identifier and a sequence number. Such information can help in reporting errors when STPI or corresponding DFoNP are corrupted or lost.
  • STPI may contain other vendor specific or DFoNP related miscellaneous information.
  • DFoNP may contain some information that helps in associating itself with corresponding STPI, such as originating node identifier and a sequence number.
  • DFoNP sequence number is same as the sequence number of the corresponding STPI .
  • DFoNP may contain other vendor specific miscellaneous information.
  • the originating node creating an STPI by creating and initializing one or more data structures. Preferably, there is only one data structure containing STPI.
  • a switch receiving both frames, one containing STPI and the corresponding DFoNP before forwarding a frame containing STPI or DFoNP to the next switch or node.
  • a switch receiving frame containing STPI before reading the corresponding DFoNP Preferably, a switch receiving frame containing STPI before reading the corresponding DFoNP.
  • a switch can delay transmitting or reading DFoNP after the corresponding STPI is transmitted or received, allowing the switch to optimize its resource usage and improve efficiency.
  • a switch can read DFoNPs corresponding to a switch port with minimum outbound traffic, ahead of other DFoNPs, thereby improving link efficiency.
  • the switch modifying temporary information in STPI such as node number or port number corresponding to the node containing corresponding DFoNP and buffer pointer or index or offset for the corresponding DFoNP, when the DFoNP is transmitted to another node.
  • layer 2 information in STPI and DFoNP should be updated to be compatible with the subnet to which it is forwarded. For example, in an IP network when a packet moves from Ethernet to ATM, layer 2 protocol information will have to be modified to be made compatible with the ATM network.
  • the switch transmitting both the DFoNPs and the STPI to all next hop nodes identified by the address .
  • a switch can delay reading or forwarding the DFoNP after the corresponding STPI is received or forwarded, and vice versa.
  • a switch may or may not receive or transmit DFoNPs in the same order as the corresponding STPIs are received or transmitted from a switch port.
  • a switch may receive or transmit one or more DFoNP in one frame.
  • STPI For networks that support layer 5/6/7 (example OSI networks) , STPI optionally containing part of or all of layer 5/6/7 information. Preferably, no layer 5/6/7 information may be contained in STPI.
  • Fig. 1 illustrates datalink frames in normal networks .
  • Fig. 2 illustrates examples of different design options for frames containing STPIs and the corresponding Df oNPs .
  • Fig. 3 illustrates an option for transmitting STPI and the corresponding DFoNP to next hop node.
  • Fig. 4 illustrates an option for transmitting STPI and the corresponding DFoNP to next hop node.
  • Fig. 5 illustrates an option for transmitting STPI and the corresponding DFoNP to next hop node.
  • Fig. 6 illustrates an option for transmitting STPI and the corresponding DFoNP to next hop node.
  • Fig. 7 illustrates an option for transmitting DFoNP and optionally, the corresponding STPI to destination node.
  • Fig. 8 illustrates examples of different design options for frames containing Read-STPI request.
  • Fig. 9 illustrates examples of different design options for frames containing Read-DFoNP requests.
  • Fig. 10 illustrates examples of different design options for frames containing Number-of-STPIs message.
  • Fig. 11 illustrates Ethernet frames adhering to this invention .
  • Fig. 12 illustrates PCI-Express transactions adhering to this invention.
  • Fig. 13 illustrates examples of design options for frames containing more than one type of requests or messages .
  • Fig. 14 illustrates how this invention can be used by switches to reorder transmission of DFoNPs . MODES FOR CARRYING OUT THE INVENTION
  • Fig. 2 illustrates some examples of different formats in which the STPI and the corresponding DFoNP can be created adhering to this invention.
  • the layer 2, layer 3, and layer 4 information that may be present in the DFoNP and STPI may or may not be mutually exclusive and is dependent on specific format or formats of STPI and DFoNP supported by switches and endnodes.
  • Each network will employ only a few STPI/DFoNP formats (preferably, as few as 1-3) , one each for a subtype of a packet or a frame.
  • a network may employ only one format for STPI and one format for DFoNP to reduce complexity in switches and endnodes.
  • STPI should have enough information for the switch to find the port for the next hop.
  • Fig. 2 ⁇ illustrates example formats for DFoNP, the corresponding STPI and an STPI frame which contain
  • STPIs All layer 2 020202 020207 (including Destination Node Address used for routing) , layer 3 020203 and layer 4 020204 information are in STPI and the DFoNP contains no layer 3 and 4 information. DFoNP contains minimal layer 2 020002 020007 information mandated by datalink layer (an example of optional layer 2 information is the VLAN tag in Ethernet) . Frame Type in the frame gives the type of frame, DFoNP 020009, STPI 020109, etc. All data 020005 are in DFoNP. Three STPIs 020110 are sent in a STPI Frame. The destination address 020102 of the STPI Frame is the next hop switch or node address.
  • 3rd STPI 020111 in the STPI Frame corresponds to the DFoNP shown.
  • the STPI contains the length 020213 of the corresponding DFoNP and the current node number 020212 and current buffer address 020213 containing the corresponding DFoNP.
  • Fig. 2B illustrates example formats for DFoNP, the corresponding STPI and an STPI frame which contain STPIs. The frames in this network do not have layer 2 trailer.
  • All layer 2 020502 (includes destination node address for routing) , RDMA address 020502 for STPI in the destination node, KDMA address 020514 for DFoNP in the destination node, layer 3 020503 and layer 4 020504 information are in STPI.
  • the DFoNP contains no layer 3 and 4 information. In this network, layer 2 020302 020402 contains frame type and hence, no additional field for frame type is present.
  • DFoNP contains layer 2 header 020302 with next hop node address.
  • STPI contains the node number 020512 and an index 020513 to the array containing the corresponding DFoNP. When DFoNP is transmitted to the next node, the node number 020512 and the index 020513 in the corresponding STPI are updated.
  • STPI also contains Source Node Number 020515 (the node number of the node which created the STPI) and STPI sequence number 020516.
  • the STPI 020410 020411 is the only STPI in the ST
  • Fig. 2C illustrates example formats for DFoNP, the corresponding STPI and an STPI frame which contain STPIs. All layer 3 020803 and layer 4 020804 information are in STPI and the DFoNP contains all 020602 layer 2 information. In this network, switches use 020803 layer 3 address to find next hop port. So 020702 layer 2 of STPI Frame does not have next hop node address .
  • Frame Type in the frame gives the type of frame, DFoNP 020609, STPI 020709, etc. There are 2 STPIs 020710 in the STPI Packet and the first STPI
  • STPI contains the DFoNP Current Node Port Number 020812 corresponding to the node containing DFoNP and an offset 020813 in a buffer to the current location of the corresponding DFoNP .
  • the port number 020812 is the port number on the switch containing STPI.
  • the port number 020812 and offset 020813 in the corresponding STPI are updated.
  • the port number 020813 is also updated when STPI is transmitted to the next node.
  • STPI also contains Source Node Number 020815 and a sequence number 020816.
  • Fig. 2D illustrates example formats for DFoNP, the corresponding STPI and an STPI frame which contain STPIs.
  • STPI contains layer 3 021103, layer 4 021104, and part of layer 2 021102 protocol information (including route to the destination) , RDMA address 021102 for STPI in the destination node.
  • DFoNP contains data 020905, part of layer 2 protocol information 020902 020907 and RDMA address 020902 for the DFoNP in the destination node.
  • STPI contains 021113 DFoNP length and the port number 021112 and the buffer address 021113 to the location of the corresponding to DFoNP.
  • DFoNP Port number 021112 is also updated when STPI is transmitted to the next node.
  • Both STPI and DFoNP contains originating node number 021115 020915 and STPI sequence number 021116 020916.
  • the address in the datalink header 021002 of the STPI Frame is the final destination node address in the subnet indicating all STPIs in the STPI Frame are to the same final destination and switching can be done using STPI Frame address .
  • Frame Type in the frame gives the type of frame, DFoNP 020909, STPI 021009, etc.
  • STPI Frame does not contain the number of STPIs as STPIs are of fixed length and the number of STPIs can be derived from the length of STPI frame.
  • the first STPI 021011 in the frame corresponds to the DFoNP shown.
  • Fig. 2E illustrates example formats for DFoNP, the corresponding STPI and an STPI frame which contain STPIs.
  • STPI contains part of layer 2 021402 (Layer 2 in STPI contains destination address used for routing) , RDMA address 021402 for STPI in the destination node, part of layer 3 information 021403 and all of layer 4 information 021404.
  • the DFoNP contains layer 2 protocol information 021202, RDMA address 021202 for DFoNP in the destination node and part of layer 3 information 021203.
  • Frame Type in the frame gives the type of frame, DFoNP 021209, STPI 021309, etc.
  • STPI corresponding to the DFoNP shown is the first STPI 021311 in the STPI Frame.
  • STPI contains the current node number 021412 and index 021413 to the location of the corresponding DFoNP.
  • the node number 021412 and index 021413 in the corresponding STPI are updated.
  • STPI also contains Source Node Number 021415, STPI Sequence Number 021416 and miscellaneous 021417 information.
  • the layer 2 header 021302 of the STPI frame contains next hop node address.
  • Fig. 2F illustrates example formats for DFoNP, the corresponding STPI and an STPI frame which contain STPIs .
  • the network medium does not support layer 1 header or trailer.
  • STPI contains part of layer 2 021702 (including destination node identifier used for routing) and part of layer 3 021703 protocol information.
  • DFoNP contains layers 2 021502, part of layer 3 021503 and all of layer 4 021504 protocol information.
  • STPI contains the buffer address 021713 and an index 021713 in the buffer to the location of the corresponding to DFoNP. When DFoNP is transmitted to the next node, buffer address 021713 and index 021713 for the corresponding STPI are updated.
  • STPI also contains Source Node Number 021715, STPI sequence number 021716 and miscellaneous 021717 information.
  • Frame Type in the frame gives the type of frame, DFoNP 021509, STPI 021609, etc.
  • the STPI Frame contains length 021610 of STPIs and since STPIs of this network are of fixed length, the position of the STPIs in the frame can be determined by the switch. Expanded view of the second STPI 021611 in the STPI frame is shown.
  • the layer 2 header 021602 of the STPI frame contains next hop node address.
  • Fig. 2G illustrates example formats for DFoNP, the corresponding STPI and an STPI frame which contain STPIs.
  • the network medium does not support layer 1 header or trailer.
  • STPI contains part of layer 2 022002 (including destination node address for routing) , part of layer 3 022003 and part of layer 4 022004 protocol information.
  • DFoNP contains layer 2 021802, part of layer 3 021803 and part of layer 4 021804 protocol information.
  • STPI contains the current node number
  • STPI also contains the Source Node Number 022015 and miscellaneous 022017 information.
  • Frame Type in the frame gives the type of frame, DFoNP 021809, STPI 021909, etc.
  • the STPI Frame contains length 021910 of STPIs and since STPIs of this example are of fixed length, the position of the STPIs in the frame can be determined by the switch. Expanded view of the second STPI 021911 in the frame is shown.
  • the layer 2 header 021902 of the STPI frame contains next hop node address.
  • Fig. 2H illustrates example formats for DFoNP, the corresponding STPI and an STPI frame which contain STPIs.
  • STPI contains part of layer 2 022302 (including destination node address for routing) and all of layer 3 022303 protocol information.
  • the DFoNP contains layer 2 022102 and layer 4 022104 protocol information.
  • STPI contains the length 022312 of the corresponding DFoNP and the current node identifier 022312, buffer address 022313 and an offset 022313 in a buffer to the location of the corresponding DFoNP.
  • the Current Node identifier 022312, buffer address 022313 and the offset 022313 in the corresponding STPI are updated.
  • STPI also contains Source Node Number 022315 and STPI Sequence Number 022316.
  • Frame Type in the frame gives the type of frame, DFoNP 022109, STPI 022209, etc.
  • the STPI Frame in this example is allowed to have only one STPI 022211.
  • the layer 2 header 022202 of the STPI frame contains next hop node address. Expanded view of the STPI is shown .
  • Fig. 21 illustrates example formats for DFoNP, the corresponding STPI and an STPI frame which contain STPIs.
  • the network supports protocol layers 5, 6 and 7 in addition to lower layers.
  • STPI contains layer 2 022602 and layer 3 022603 information.
  • the OFoNP contains minimal layer 2 022402 protocol information allowed by the datalink layer, layer 4, layer 5, layer 6, and layer 7 022418 protocol information.
  • STPI contains the current node number 022612, a buffer address 022613 in the node and an offset 022613 in the buffer to the location of the corresponding DFoNP. When DFoNP is transmitted to the next node, the node number 022612, the buffer address 022613 and the offset 022613 in the corresponding STPI are updated.
  • STPI also contains Source Node Number 022615 and STPI sequence number 022616.
  • Frame Type in the frame gives the type of frame, DFoNP 022409, STPI 022509, etc.
  • the STPI Frame in this example is allowed to have only one STPI 022511 and layer 2 022502 of the STPI frame contains address of the destination node in the subnet which is used for routing the STPI frame. Expanded view of the STPI is shown.
  • Fig. 2J illustrates example formats for DFoNP, the corresponding STPI and an STPI frame which contain
  • STPIs contains layer 2 022902 protocol information (including destination node address for routing) .
  • the DFoNP contains part of layer 2 022702 and all of layer 3 and layer 4 022718 protocol information.
  • Frame Type in the frame gives the type of frame, DFoNP 022709, STPI 022809, etc.
  • the STPI[I] 022811 is the only STPI 022810 in the STPI Frame.
  • STPI contains the current node number 022912 and the buffer address 022913 in the node to the location of the corresponding DFoNP. When DFoNP is transmitted to the next node, the node number 022912 and the buffer address 022913 in the corresponding STPI are updated.
  • STPI also contains Source Node Number 022915 and STPI Sequence Number 022916.
  • DFoNP contains Source Node Number 022715 and a DFoKP sequence number 022719 which is different from STPI sequence number.
  • the layer 2 header 022802 of the STPI frame contains next hop node address. Expanded view of the STPI[I] is shown. 11.
  • Fig. 2K illustrates example formats for DFoNP, the corresponding STPI and an STPI frame which contain STPIs.
  • STPI contains layer 2 023202 information (including destination node address for routing) .
  • the DFoNP contains minimal layer 2 023002 mandated by datalink layer of the subnetwork and all of layer 3 and 4 023018 information.
  • the DFoNP contains control data 023005 such as requests to open a file in addition to data 023005.
  • layer 2 023002 023102 protocol information contains frame type and hence, no additional field for frame type is present.
  • the STPI[I] 023111 is the only STPI 023110 in the STPI Frame.
  • STPI contains the length 023212 of the corresponding DFoNP and the node number 023212 and the buffer address 023213 in the node to the location of the corresponding to DFoNP.
  • the node number 023212 and buffer address 023213 in STPI are updated.
  • STPI also contains the Source Node Number 023215 and STPI sequence number 023216.
  • DFoNP contains Source Node Number 023015 and a DFoNP Sequence Number 023019 which is different from STPI sequence number. Expanded view of STPI[I] is shown. 12.
  • Fig. 2L illustrates example formats for DFoNP, the corresponding STPI and an STPI frame which contain STPIs.
  • STPI contains layer 2 023502 (including destination node address for routing) and layer 3 information 023503 and part of layer 5/6/7 023518 protocol information.
  • the DFoNP contains minimal layer 2 Header 023302 mandated by datalink layer of the subnet, layer 4 023304 and part of layer 5/6/7 023318 protocol information.
  • the DFoNP contains control data 023305 such as requests to open a file in addition to data 023305.
  • STPI[I] 023411 is the only STPI 023410 in the STPI Frame.
  • STPI contains the node number 023512 and buffer address 023513 in the node to the location of the corresponding DFoNP.
  • the node number 023512 and buffer address 023513 in the corresponding STPI are updated.
  • STPI also contains the Source Node Number 023515 and STPI sequence number 023516.
  • the layer 2 header 023402 of the STPI frame contains next hop node address. Expanded view of the STPI[I] 023411 is shown. 13. Fig.
  • 2M illustrates example formats for DFoNP, the corresponding STPI and an STPI frame which contain STPIs.
  • STPI contains layer 2 023802 (including destination node identifier used for routing) , layer 3 023803 and layers 5/6/7 023818 protocol information.
  • the DFoNP contains layers 2 023602, layer 3 023603 and layer 4 023604 protocol information.
  • Frame Type in the frame gives the type of frame, DFoNP 023609, STPI 023709, etc.
  • STPI frame contains two STPIs 023710 and expanded view of the 2nd STPI (STPI [2]) 023711 is shown.
  • the STPI frame contains offsets 023720 to all STPIs in the frame.
  • the network in this example supports more than one length for STPIs.
  • STPI[I] offset 023720 gives the location of the first STPI (STPI[I] 023711) in the STPI frame.
  • STPI [2] offset 023720 gives the location of the second STPI 023711 in the STPI frame. Offsets in this example are with respect to beginning of the frame.
  • STPI contains the node number 023812 and buffer address 023813 in the node to the location of the corresponding DFoNP . When DFoNP is transmitted to the next node, the node number 023812 and buffer address 023813 in STPI are updated.
  • STPI also contains Source Node Number 023815 and STPI sequence number 023816.
  • the layer 2 header 023702 of the STPI frame contains next hop node address. 14. Fig.
  • FIG. 2N illustrates example formats for DFoNP, the corresponding STPI and an STPI frame which contain STPIs.
  • STPI contains layer 2 024102 (including destination node identifier used for routing) protocol information.
  • the DFoNP contains layer 2 023902, layers 3 023918 and layer 4 023918 protocol information.
  • Frame Type in the frame gives the type of frame, Read Completion 023909 for DFoNP frame and Write 024009 for STPI frame.
  • the STPI Frame contains the length of write 024022 (which is the sum of the length of STPI[I]
  • DFoNP contains Read Requester ID 023921 (Identifier) and a tag 023921 to identify the read request. DFoNP also contains address 023921 from which the layer 3/4 headers and the data 023905 is read and the length 023921 of the the read.
  • the STPI Frame contains two STPIs and expanded view of the 2nd STPI (STPI [2]) 024011 is shown. STPI contains the node number 024112 and buffer address 024113 in the node to the location of the corresponding DFoNP and the length of the DFoNP 024123. This information is used to read the corresponding DFoNP .
  • STPI When DFoNP is transmitted to the next node, the node number 024112 and buffer address 024113 in STPI are updated. STPI also contains Source Node Number 024115, STPI Sequence Number 024116 and Miscellaneous 024123 information. The layer 2 header 024002 of the STPI frame contains next hop node address .
  • Any of the first 4 methods can be used for transferring STPI and the corresponding DFoNP from the originating node or a switch to another switch or end node.
  • the fifth method can be used for transferring STPI and the corresponding DFoNP to a destination end node.
  • a request message from a node to an adjacent node to send STPIs to the node that sent the request is referred to as Read-STPI request.
  • a request message from a node to an adjacent node to send DFoNPs to the node that sent the request is referred to as Read-DFoNP request .
  • Fig. 3 illustrates one of the options that could be used in a given network for transmitting STPI and DFoNP to the next hop node.
  • a switch/node responds to Read-STPI request by transmitting STPIs.
  • the switch/node receiving STPIs sends Read-DFoNP requests using the information contained in STPIs to fetch the corresponding DFoNPs.
  • a frame containing a Read-STPI request is called Read-STPI Frame.
  • a frame containing Read-DFoNP requests is called Read-DFoNP Frame.
  • Switch/Node A 030001 contains an STPI 030003 and the corresponding DFoMP 030004 to be transmitted to the Switch/Node B 030002.
  • Fig. 3A Switch/Node A 030001 contains an STPI 030003 and the corresponding DFoMP 030004 to be transmitted to the Switch/Node B 030002.
  • Fig. 3A Switch/Node A 030001 contains an STPI 030003 and the corresponding
  • the Switch/Node B transmits Read-STPI Frame 030005 to the Switch/Node A giving the maximum number of STPIs that can be transmitted.
  • the maximum number of STPIs 030005 that can be transmitted from Switch/Node A to Switch Node B is 5 in the example.
  • the Switch/Node A responds by sending an STPI frame 030106 containing the STPI 030003 (the STPI frame in this example can contain upto 5 STPIs) .
  • the Switch/Node B decides to fetch the DFoNP corresponding to the STPI 030003 and sends Read-DFoNP Frame 030207 to the Switch/Node A containing the Read-DFoNP request for the DFoNP 030004.
  • the Read-DFoNP request contains the location (a location could be a buffer address or an offset in a buffer or an index or a combination of addresses, offsets or indexes) of the DFoNP 030004 in the Switch/Node A.
  • the location of the DFoNP to be used in Read-DFoNP request will be present or can be derived from the contents of the corresponding STPI 030003.
  • the Switch/Node A responds to the Read-DFoNP request for the DFoNP by sending the DFoNP 030004.
  • the STPI 030003 is updated with the identifier of the Switch/Node B and the location of the DFoNP 030004 in the Switch/Node B.
  • Fig. 4 illustrates another option for transmitting STPI and the corresponding DFoNP to the next hop node.
  • a switch/node transmits STPIs followed by DFoNPs corresponding to the STPIs transmitted.
  • Switch/Node A 040001 contains an STPI 040003 and the corresponding DFoNP 040004 to be transmitted to the Destination Node B 040002.
  • the Switch/Node A transmits an STPI Frame 040106 containing the STPI 040003 to the Switch/Node B.
  • the Switch/Node A transmits the DFoNP 040004 to the Switch/Node B.
  • the Switch/Node B updates the STPI 040003 with the location of the DFoNP 040004 in the Switch/Node B.
  • Fig. 5 illustrates another option for transmitting STPI and the corresponding DFoNP to the next hop node.
  • a switch/node transmits STPIs and the switch/node receiving STPIs sends Read-DFoNP requests using information contained in STPIs to fetch the corresponding DFoNPs.
  • Switch/Node A 050001 contains an STPI 050003 and the corresponding DFoNP 050004 to be transmitted to the Switch/Node B 050002.
  • Fig. 5B Switch/Node A transmits a frame 050106 containing the STPI to the Switch/Node B.
  • Fig. 5 illustrates another option for transmitting STPI and the corresponding DFoNP to the next hop node.
  • a switch/node transmits STPIs and the switch/node receiving STPIs sends Read-DFoNP requests using information contained in STPIs to fetch the corresponding DFoNPs.
  • Switch/Node A 050001 contains an STPI
  • the Switch/Node B decides to fetch the DFoNP corresponding to the STPI and sends Read-DFoNP Frame 050207 to the Switch/Node A containing DFoNP request for the DFoNP 050004.
  • the DFoNP request contains the location of the DFoNP 050004.
  • the location of the DFoNP used in the Read-DFoNP request will be present or can be derived from the contents of the corresponding STPI 050003.
  • the Switch/Node A responds to the Read-DFoNP request by transmitting the DFoNP 050004.
  • the STPI 050003 is updated with identifier of Switch/Node B and the location of the corresponding DFoNP 050004 in the Switch/Node B.
  • Fig. 6 illustrates another option for transmitting STPI and DFoNP to the next hop node.
  • a switch/node responds to Read-STPI request by transmitting STPIs followed by the corresponding DFoNPs.
  • Switch/Node A 060001 contains an STPI 060003 and the corresponding DFoNP 060004 to be transmitted to the Switch/Node B 060002. The
  • Switch/Node B transmits Read-STPI Frame 060005 to the Switch/Node A giving the maximum number of STPIs that can be transmitted.
  • the maximum number of STPIs 060005 is 0 in the example indicating that all STPIs can be transmitted.
  • the Switch/Node A responds by sending an STPI frame 060106 containing all STPIs to be transmitted to the Switch/Node B.
  • the Switch/Node A transmits the DFoNP 060004 corresponding to the STPI to the Switch/Node B.
  • the STPI 060003 is updated with identifier of the Switch/Node B and the location of the corresponding DFoNP 060004 in the Switch/Node B. 5.
  • Fig. 7 illustrates an option which can be used for transmitting DFoNP and optionally the corresponding
  • Switch/Card A 070001 contains an STPI 070003 and the corresponding DFoNP 070004 to be transmitted to the Destination End Node B 070002.
  • Switch/Card A transmits the DFoNP 070004 to the Destination End Node B and updates the STPI 070003 with the location (DMA address) of the DFoNP in the Destination End Node B.
  • Fig. 7C Switch/Card A transmits the STPI in an STPI frame 070206 to the Destination End Node B.
  • both STPI 070003 and DFoNP 070004 are received by End Node B.
  • a switch can employ one of the STPI and DFoNP transfer options (strategies) listed above, for each port. Both ports on a point-to-point link must agree to the same frame transmitting option. All ports on a link or bus must follow the same frame transmitting option.
  • a network employs only one of the four STPI/DFoNP transfer options listed in Fig.3, Fig.4, Fig.5 and Fig. 6.
  • a network also employs the STPI/DFoNP transfer option listed in Fig. 7. For the option corresponding to Fig.7, updating STPI with address (location) of DFoNP in the end node is optional.
  • DFoNPs do not contain information (such as originating node identifier, DFoNP identifier, DFoNP address in previous node, etc.) that allow a DFoNP to be mapped to the corresponding STPI, then the DFoNPs must be transmitted in the same order as requested in Read-DFoNP frame/s with design options listed in Fig.3 and Fig.5. With design options listed in Fig.4 and Fig.6, if DFoNPs do not contain information that allow the DFoNP to be mapped to the corresponding STPI, DFoNPs must be transmitted in the same order as the corresponding STPIs are transmitted. This will allow switches to identify STPI corresponding to an DFoNP that is received.
  • information such as originating node identifier, DFoNP identifier, DFoNP address in previous node, etc.
  • more than one DfoNP may be transmitted in one DfoNP frame.
  • Fig. 8 illustrates some examples of different formats in which the Read-STPI Frames can be created adhering to this invention.
  • a given network employs only one format (design option) for Read-STPI request to keep the design of switches and end nodes simple.
  • Fig. 8A illustrates a Read-STPI frame with Frame Type "Read-STPI” 080009 and "Number of STPIs" 080024 set to 3.
  • the frame also contains Miscellaneous 080025 field.
  • Fig. 8B illustrates a Read-STPI frame in a network where explicit frame type specification is not required.
  • the frame specifies an address 080126 for read (the location of the STPIs) in the node receiving the Read-STPI Frame.
  • the frame also provides the length 080127 for read.
  • the address where STPIs are stored can be dynamically configured on the switch for each node/switch it is connected to.
  • Fig. 8C illustrates a Read-STPI frame in a network without layer 1 headers or trailers.
  • Frame Type 080209 is "Read-STPI".
  • the "Number of STPIs" 080224 is 0 indicating permission to transmit an STPI Frame with as many STPIs for the node transmitting Read-STPI Frame as possible, from the node receiving the Read-STPI Frame.
  • the frame also contains a Miscellaneous 080225 field.
  • Fig. 8D illustrates a Read-STPI frame in a network without layer 1 headers or trailers.
  • Layer 2 header 080302 contains Frame Type (Read-STPI) .
  • the "Number of STPIs" 080324 is -1 indicating permission to transmit all STPIs for the node transmitting Read-STPI Frame, from the node receiving the Read-STPI Frame.
  • a Read—DFoNP Frame contains one or more Read-DFoNP requests and each Read-DFoNP request contains the location of the requested DFoNP.
  • Fig. 9 illustrates some examples of different formats in which the Read—DFoNP Frame can be created adhering to this invention.
  • a given network employs only one format (design option) for Read-DFoNP request to keep the design of switches and end nodes simple. 1.
  • FIG. 9A illustrates an example of a Read-DFoNP frame with Frame Type 090009 "Read-DFoNP” and "Number of Read-DFoNP requests" 090028 set to 2.
  • the DFoNP[I] 090029 and DFoNP [2] 090029 buffer addresses provide the location of the DFoNPs in the node receiving the Read- DFoNP Frame.
  • the frame also contains Miscellaneous 090031 field.
  • Fig. 9B illustrates an example of a Read-DFoNP frame in a network where explicit frame type specification is not required.
  • Frame specifies an address 090129 for read (the location of the DFoNP) in the node receiving the Read-DFoNP Frame.
  • the frame also provides the length 090130 for read.
  • Fig. 9C illustrates an example of a Read-DFoNP frame in a network without layer 1 headers or trailers.
  • Frame Type 090209 is "Read-DFoNP"
  • the "Number of Read-DFoNP requests" 090228 is 3.
  • Each Read-DFoNP request contains a buffer address and an offset.
  • the DFoNP[I] 090229, DFoNP [2] 090229 and DFoNP [3] 090229 buffer addresses and offsets provide the location of the DFoNPs in the node receiving -the Read-DFoNP Frame.
  • Fig. 9D illustrates an example of a Read—DFoNP frame in a network without layer 1 headers or trailers.
  • Frame Type (Read-DFoNP) is contained in layer 2 header 090302. Only one Read-DFoNP request is allowed in the frame and the the Read-DFoNP request gives the index 090332 of the DFoNP to be read.
  • a switch or node can send the number of STPIs available for transmission to the next hop node or switch.
  • Fig. 10 illustrates some examples of different formats in which the Number-of-STPIs Frame can be created adhering to this invention.
  • a given network employs only one format for Number-of—STPI message to keep the design of switches and end nodes simple.
  • Fig. 1OA illustrates an example of a Number-of- STPIs frame with Frame Type 100009 "Number-of-STPIs" and "Number of STPIs" 100033 set to 3.
  • the frame also contains a Miscellaneous 100034 field.
  • Fig. 1OB illustrates an example of a Number-of-STPIs frame in a network where explicit frame type specification is not required.
  • the frame specifies an address 100135 to the location where value of Number of STPIs will be written.
  • the frame also contains the length 100136 of the field to be written.
  • the next field contains data (Number of STPIs) 100137 for the write, which is 2 in this example.
  • Fig. 1OC illustrates an example of a Number-of-STPIs frame in a network without layer 1 headers or trailers.
  • Frame Type 100209 is "Number-of-STPIs".
  • the "Number of STPIs" 100233 is 3.
  • the frame also contains a Miscellaneous 100234 field.
  • Fig. 1OD illustrates an example of a Number-of-STPIs frame in a network without layer 1 headers or trailers.
  • Layer 2 header 100302 contains Frame Type (Number-of- STPIs) .
  • the "Number of STPIs" 100333 is 1 in this example .
  • the network described in this invention can be connected to an I/O card (in a server or embedded system) or to a PCI bus.
  • Ethernet header contains destination MAC:
  • Ethernet header contains source MAC address: A DFoNP frame can contain the MAC address of the originating node in this field. All other types of frames (STPI, Read- STPI, Read-DFoNP, Number-of-STPI) can contain MAC address of the node transmitting the frame in this field. iii.
  • the Ethernet header contains length field as per Ethernet Protocol standard, iv. The first byte of the data field contains the "Frame Type": one bit each for STPI, DFoNP, Read-STPI, Read-DFoNP and Number-of-
  • Each STPI will contain the final destination MAC address.
  • each STPI can also contain source MAC address of the originating node of the STPI.
  • the formats specified examples such as Fig. 2A, Fig. 2C etc., can be used with Ethernet .
  • the Ethernet trailer contains FCS for the frame.
  • Fig. HA illustrates an example of DFoNP and STPI frames which can be used with Ethernet.
  • Fig. HB illustrates an example Read-DFoNP frame which can be used with Ethernet.
  • Destination MAC address 110038 in OFoNP frame is the MAC address corresponding to the port or node (next hop node) receiving the frame.
  • Source MAC address 110039 in the DFoNP frame is the MAC address of the node that created the DFoNP.
  • the length field 110040 provides the length as per Ethernet Protocol standard, iv.
  • Ethernet Frame is Frame Type 110009 and Frame Type of DFoNP frame is DFoNP (DFoNP bit is set) .
  • DFoNP DFoNP bit is set
  • the DFoNP contains layer 3 110003, layer 4
  • the STPI frame in this example contains 2
  • STPIs 110110 are expanded. xi. Expanded view of the second STPI 110111 is shown. xii. Each STPI contains the Final Destination
  • the STPI contains the Source MAC
  • the STPI contains the MAC address of the node containing DFoNP 110212, buffer address 110213 of the DFoNP in this node and length
  • Fig. HB illustrates a 20 Read-DFoNP frame containing 3 Read-DFoNP requests .
  • xviii The destination MAC address 110338 in the Read-DFoNP frame is the "DFoNP Current Node MAC address" 110212 from the STPI.
  • Read-DFoNP frame is the MAC address corresponding to the port transmitting the Read—DFoNP Frame.
  • the length field 110340 provides the 30 length as per Ethernet Protocol standard.
  • xxi The first field in the data portion of the Ethernet Frame is Frame Type 110309 and Frame Type of Read-DFoNP frame is "Read- DFoNP" ("Read-DFoNP" bit is set) .
  • 35 xxii The Number of DFoNPs 110328 being requested from the node receiving Read-DFoNP frame is 3 in this example.
  • xxiii The DFoNP buffer address 110329 and the length 110329 of DFoNP in Read-STPI frame are from DFoNP Current Buffer Address 110213 and DFoNP Length 110213 fields in STPI. 2.
  • the switch corresponding to this invention behaves like an end node.
  • the switch will use PCI transactions to communicate with the server.
  • the host in turn the PCI root bridge
  • PCI memory write transaction to transfer STPIs to a switch corresponding to this invention
  • the switch can use PCI memory read transaction to read
  • the host can use PCI memory write transaction to write the address of the memory location holding STPIs which the switch can use for PCI Memory Read transaction.
  • the switch can use PCI read transaction to read each DFoNP using the buffer address contained in the corresponding STPI.
  • the host (in turn the PCI root bridge) can optionally use PCI write transaction to write the number of STPIs to a switch corresponding to this invention.
  • the switch can use PCI memory write to write DFoNPs and STPIs to the memory of the destination node. e. Fig.
  • PCI Express TM is a trade mark of PCI—SI6
  • STPIs and DFoNPs from root bridge to a switch corresponding to this invention and vice versa.
  • Example in Fig. 12A illustrates format of PCI Express Read Completion containing DFoNP from a root bridge in response to a Memory Read request from a switch.
  • the first field of PCI Express Read Completion data provides the Frame Type 120009 which is DFoNP.
  • the rest of the Read Completion data is layer 3/4 protocol information 120018 and Data 120005 being transmitted to the remote node.
  • FIG. 12B illustrates format of PCI Express Read Completion containing STPIs from a root bridge in response to a Memory Read request from a switch.
  • the first field of data provides the Frame Type 120109 which is STPI.
  • the second field in data is "Number of STPIs" 120110 which is 3 in this example. This field is followed by three STPIs 120111.
  • Each STPI contains "Final Destination Node Identifier” 120238 which is used by switches for routing, Source Node Identifier 120215 which is the identifier of the node that created the STPI, "Destination STPI Address"
  • DFoNP Current Node ID 120212
  • DFoNP Length DFoNP Current Address
  • DFoNP Current Address 120213
  • the DFoNP Length field 120213 is also used for RDMAing DFoNP to the memory of the destination node, iii.
  • Example in Fig. 12C illustrates a PCI Express Memory Write transaction containing
  • the first field of PCI Express Memory Write transaction data provides the Frame Type 120309 which is DFoNP.
  • the rest of the Read Completion data is layer 3/4 protocol information 120318 and Data 120305 that arrived from the remote node, iv.
  • Example in Fig. 12D illustrates a PCI Express Memory Write transaction containing STPIs, from a switch to a root bridge.
  • the first field of PCI Express Memory Write data provides the Frame Type 120409 which is STPI.
  • the second field in the data is "Number of STPIs" 120410 which is 2 in this example. This field is followed by two STPIs 120411.
  • Each STPI contains "Final Destination Node Identifier" 120538 which is used by switch for routing, Source Node Identifier 120515 which is the identifier of the node that created the STPI, a miscellaneous field 120517, "DFoNP Current Node Identifier” 120512, DFoNP Current Buffer Address 120513 and DFoNP Length 120513 to be used for reading DFoNP from the node where it is currently stored.
  • the DFoNP Length field 120513 is also used for doing PCI Express Memory Write transaction to the root bridge (DMAing DFoNP to the memory of the destination node) .
  • the DFoNP and STPI are
  • both STPI and DFoNP are transmitted to all next hop nodes identified by the Multicast or Broadcast address.
  • switches and nodes may employ retransmission of the corrupted or lost frame.
  • the retransmission policy and error recovery are link (example PCI) and vendor specific.
  • Some networks allow more than one type of content to be present in the same frame.
  • the types of contents are STPI, DFoNP, Read-STPI request, Read-DFoNP request and Number-of-STPIs message.
  • Fig. 13A illustrates an example of a frame containing both Number-of-STPIs message and Read-DFoNP requests.
  • the Frame Type 130009 is a bit-OR of "Number- of-STPIs" and "Read-DFoNP".
  • the "Number of STPIs" 130033 is 5 indicating that there are 5 STPIs available to be transmitted to the receiving node.
  • the "Number of DFoNPs" 130028 is 3 in this example and the receiving node is expected to respond to the request by transmitting the three DFoNFs requested.
  • Fig. 13B illustrates an example of a frame containing both Read-STPI request and Read-DFoNP requests.
  • the Frame Type 130109 is a bit-OR of "Read- STPI" and "Read-DFoNP".
  • the "Number of STPIs" field 130124 is 2 and the "Number of DFoNPs" field 130128 is 3 in this example.
  • the node receiving the frame is expected to respond with two STPIs and the three requested DfoNPs.
  • Fig.14 illustrates an example of reading DFoNPs in a different order compared to the order in which STPIs are received.
  • Switch A 140001 has 3 DFoNPs 140004 to be transmitted to Switch B 140002.
  • the Switch A forwards 3 STPIs corresponding to the DFoNPs in an STPI frame 140006 to Switch B.
  • the Switch B has 10 STPIs in its queue 140006 for its link to node D.
  • the switch B has no STPIs in its queue 140005 for its link to node C.
  • Fig. 14A Switch A 140001 has 3 DFoNPs 140004 to be transmitted to Switch B 140002.
  • the Switch A forwards 3 STPIs corresponding to the DFoNPs in an STPI frame 140006 to Switch B.
  • the Switch B has 10 STPIs in its queue 140006 for its link to node D.
  • the switch B has no STPIs in its queue 140005 for its link to node C.
  • the switch identifies that STPI[I] and STPI [2] received are for node D and adds STPI[I] and STPI [2] to the queue 140006 for the node D.
  • the Switch B delays reading DFoNP[I] and DFoNP [2] since there are a large of STPIs already queued for the node D.
  • the Switch B identifies that STPI [3] received is for the node C and queues STPI [3] to the queue 140005 for the node C.
  • the Switch B sends Read-DFoNP Frame 140107 to the Switch A with DFoNP [3] address.
  • STPI contains a priority or QoS field
  • a switch can use it for controlling the order in which DFoNPs are read.
  • a priority or QoS field in STPI or DFoNP could be used by switches or nodes to control the order in which STPIs are transmitted to the next node.
  • a network corresponding to this invention could be used to connect a server or servers to storage devices (such as disks, disk arrays, JBODs, Storage Tapes, DVD drives etc.).
  • iSCSI and iSER iSCSI Extensions for RDMA are examples in which SCSI commands and SCSI data are transmitted using networks technologies used for server interconnect .
  • a switch can delay receiving DFoNP for paths which are already congested.
  • a switch can read DFoNP corresponding to a lightly loaded link ahead of other DFoNPs and transmit STPI and
  • a switch can delay reading DFoNPs based on QoS or priority field in STPI.
  • a switch can optimize switch resources, memory and frame/packet queues as congestions are minimized by delaying DFoNPs for ports which are already congested.
  • the switch can ensure higher throughput on all links by rearranging order in which DFoNPs are read.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)

Abstract

Des trames de liaison de données ou des paquets de mise en réseau contiennent des informations de protocole dans l'en-tête et éventuellement dans l'en-queue d'une trame ou d'un paquet. L'invention concerne un procédé dans lequel une partie ou la totalité des informations de protocole correspondant à une trame ou à un paquet sont transmises de façon séparée dans une autre trame de liaison de données. Les 'informations de protocole transmises de façon séparée' sont désignées par STPI. Les STPI contiennent assez d'informations de protocole pour identifier le prochain nœud ou port du bond. Les STPI peuvent être utilisées pour éviter un encombrement du réseau et améliorer l'efficacité de la liaison. De préférence, il existera une trame de liaison de données ou un paquet de réseau correspondant à chaque STPI, contenant les données et le reste des informations de protocole et cette trame/ce paquet est désigné(e) par DFoNP. La création des STPI et du DFoNP est effectuée par l'expéditeur de la trame ou du paquet tel qu'un système d'exploitation.
PCT/IB2007/003922 2007-12-10 2007-12-10 Transmission de façon séparée d'une partie des informations de protocole WO2009074840A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/IB2007/003922 WO2009074840A2 (fr) 2007-12-10 2007-12-10 Transmission de façon séparée d'une partie des informations de protocole

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2007/003922 WO2009074840A2 (fr) 2007-12-10 2007-12-10 Transmission de façon séparée d'une partie des informations de protocole

Publications (2)

Publication Number Publication Date
WO2009074840A2 true WO2009074840A2 (fr) 2009-06-18
WO2009074840A3 WO2009074840A3 (fr) 2016-06-09

Family

ID=40755939

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2007/003922 WO2009074840A2 (fr) 2007-12-10 2007-12-10 Transmission de façon séparée d'une partie des informations de protocole

Country Status (1)

Country Link
WO (1) WO2009074840A2 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI492588B (zh) * 2012-12-17 2015-07-11 高通公司 用於多跳混合網路的無縫切換
US9461777B2 (en) 2011-11-21 2016-10-04 Qualcomm Incorporated Hybrid networking system with seamless path switching of streams

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5282207A (en) * 1991-03-28 1994-01-25 Sprint International Communications Corp. Frame compression in integrated services networks
EP0676878A1 (fr) * 1994-04-07 1995-10-11 International Business Machines Corporation Procédé efficient de routage point à point et point à multipoint pour des noeuds commutateurs de paquets dans un réseau de transmission de données à haute vitesse
US6721315B1 (en) * 1999-09-30 2004-04-13 Alcatel Control architecture in optical burst-switched networks
US6763192B1 (en) * 2000-03-03 2004-07-13 Alcatel Integration of all-optical crossconnect functionality in an optical packet switching apparatus
GB0408877D0 (en) * 2004-04-21 2004-05-26 Level 5 Networks Ltd Signalling data reception
WO2006008885A1 (fr) * 2004-07-16 2006-01-26 Brother Kogyo Kabushiki Kaisha Dispositif de contrôle de mode de connexion, méthode de contrôle de mode de connexion et programme de mode de connexion
JP4241660B2 (ja) * 2005-04-25 2009-03-18 株式会社日立製作所 負荷分散装置

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9461777B2 (en) 2011-11-21 2016-10-04 Qualcomm Incorporated Hybrid networking system with seamless path switching of streams
TWI492588B (zh) * 2012-12-17 2015-07-11 高通公司 用於多跳混合網路的無縫切換
US9722943B2 (en) 2012-12-17 2017-08-01 Qualcomm Incorporated Seamless switching for multihop hybrid networks

Also Published As

Publication number Publication date
WO2009074840A3 (fr) 2016-06-09

Similar Documents

Publication Publication Date Title
US11398985B2 (en) Data link frame reordering
CN101129027B (zh) 转发表缩减和多路径网络转发
US8774215B2 (en) Fibre channel over Ethernet
US6738821B1 (en) Ethernet storage protocol networks
US7031904B1 (en) Methods for implementing an ethernet storage protocol in computer networks
US7099337B2 (en) Mechanism for implementing class redirection in a cluster
US20080159260A1 (en) Fibre channel over ethernet frame
US20050129047A1 (en) Switch capable of controlling data packet transmission and related method
US20060212563A1 (en) Split socket send queue apparatus and method with efficient queue flow control, retransmission and sack support mechanisms
US20100002714A1 (en) PCI express network
US20030120852A1 (en) Multiple port allocation and configurations for different port operation modes on a host
US20090213861A1 (en) Reliable Link Layer Packet Retry
Voruganti et al. An analysis of three gigabit networking protocols for storage area networks
US20020198927A1 (en) Apparatus and method for routing internet protocol frames over a system area network
US20030016669A1 (en) Full transmission control protocol off-load
US7447229B2 (en) Method for providing prioritized data movement between endpoints connected by multiple logical channels
US20020078265A1 (en) Method and apparatus for transferring data in a network data processing system
WO2009074840A2 (fr) Transmission de façon séparée d'une partie des informations de protocole
US7447207B2 (en) Method of and apparatus for transporting SCSI data over a network
JP3792538B2 (ja) ネットワークインタフェースカードを用いるピアレベル通信用システムおよび方法
Bonaventure Computer networking: principles, protocols and practice
Wadekar Handbook of Fiber Optic Data Communication: Chapter 11. InfiniBand, iWARP, and RoCE
Guendert Fibre Channel Standard
Wadekar InfiniBand, iWARP, and RoCE

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07859050

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC OF 140910

122 Ep: pct application non-entry in european phase

Ref document number: 07859050

Country of ref document: EP

Kind code of ref document: A2