Process for storing transmission units and a network communications device

FIELD OF THE INVENTION

0001The present invention relates to a process for storing transmission units during the transfer of data between networks with differing data structures of transmission units used therein and to a corresponding network communications device. The networks can be in particular an ATM network and an Ethernet network.

BACKGROUND

0002To achieve so-called interworking, i.e. a transfer of data between networks with differing protocol structures, particularly between ATM networks and Ethernet networks, it is necessary to adapt the data flow and/or the data structure of transmission units between the network protocols concerned.

0003ATM network protocols provide for data to be transmitted in transmission units in the form of ATM cells with a fixed length. An ATM cell comprises a header section and a payload section, in which the header section contains administrative information. The data charge itself is contained in the payload section. ATM networks usually use payload sections of 48 bytes. Adaptation protocol layers which provide the transition to higher level protocols, e.g. AAL5 (ATM Adaptation Layer 5), provide for several ATM cells to be joined together into higher level transmission units. The higher level transmission units have no fixed length. The higher level transmission units are broken down into ATM cells for transmission and reassembled after transmission, i.e. brought back together.

0004In Ethernet networks, e.g. fast Ethernet networks or gigabit Ethernet networks the data is transmitted in transmission units in the form of Ethernet frames. The Ethernet frames may have variable length, typically greater than the length of the ATM cells described above.

0005For interworking, for example between an ATM network and an Ethernet network it is therefore necessary to adapt the data structures of the transmission units between the network protocols involved. This means that transmission units of one network protocol with a specific characteristic length have to be converted into transmission units of the other network protocol, whereby the transmission units of the other network may have a different length, which may vary from transmission unit to transmission unit. In the opposite direction, transmission units of the other network protocol have to be converted into transmission units of the first network protocol. In addition, the concatenation of transmission units into higher level transmission units has also to be taken into account in the conversion process. This conversion is generally carried out by a corresponding electronic storage and processing of the transmission units, which is associated with considerable effort. This is also associated with a correspondingly complex structure of an interworking device used for this purpose, e.g. in the form of a semiconductor network communications component.

0006It is an object of the present invention therefore to provide a process for the storage of transmission units and a corresponding network communications device which will solve the problem described above and particularly enable efficient storage and processing of the transmission units of various network protocols.

0007This object is achieved by a process according to embodiments of the present invention and by a network communications device according to embodiments of the invention.

SUMMARY

0008The present invention serves the transfer of data between a first network and at least one further network in the form of transmission units which in a payload section contain the data to be transferred. The first network uses transmission units which have payload sections that are the same length for each transmission unit. This network may be in particular an ATM network with transmission units or cells that have a payload section with a length of 48 bytes. According to the process in accordance with the invention, the transmission units are stored in a segmented memory which is segmented in such a way that the length of a segment corresponds to the length of the payload section of the transmission units in the first network. The segmented memory is preferably capable of being addressed by memory addresses. In addition, the first network can also use higher level transmission units formed from combining the transmission units named above. The second network may in particular be an Ethernet network, with transmission units formed from Ethernet frames.

0009The transmission units are preferably stored in the segmented memory in the form of lists, where each list comprises at least a descriptor segment to describe a data structure of the corresponding transmission unit and the data of the transmission unit are stored in at least one data segment. The descriptor segment is preferably a first element in the list. In particular, information from a header section of the transmission unit placed ahead of the payload section or information from a trailer section located after the payload section can be inserted into the descriptor segment. The description of the transmission unit's data structure in the descriptor segment may in particular be used when processing the header section of the transmission unit. For this purpose, for example, a memory section, i.e. that part of the data segment, in the descriptor segment may be defined in which the header section of the transmission unit is stored.

0010The data structure of the transmission units is preferably described by fields in the descriptor segment. Into these fields for example a number of processing procedures for the transmission unit, the number of segments in the transmission unit, the length of the transmission unit, the type of transmission unit or memory addresses of specific segments in the transmission unit, e.g. of the data segment found at the end of the list, may be inserted.

0011In order to secure efficient processing of the transmission units stored in the segmented memory, it is advantageous to include further fields into the descriptor segment, which describe insert, replace or delete operations. For this purpose, these further fields can define a memory section within a data segment or a repeated execution of an operation on succeeding data segments on a list. If this is a read operation, it is easy to define a memory section which extends over several data segments in the list. In addition, additional data can be inserted into the further fields so that for example the transmission units can be supplemented during a processing operation. The function or the type of the further fields is preferably defined by a subfield of the further fields.

0012It is particularly advantageous to keep variable a number of the further fields in which at least one descriptor element of the list can be used, so that memory space is not used unnecessarily for unused functions. In this context it is particularly advantageous to mark the end of a sequence of used further fields with a specific type of further field in which there is at least one descriptor segment. Such a sequence of used further fields may if required extend across several descriptor segments.

0013It is also advantageous to connect the segments in the segmented memory to the lists by using a table memory. The table memory is addressable via memory addresses which correspond to the memory addresses of the segmented memory, and an entry in the table memory points to another entry in the table memory so that lists of entries of the table memory are formed, corresponding to the lists of segments in the segmented memory. A list of this kind of entries in the table memory can for example comprise the memory addresses of all segments of a transmission unit or the memory addresses of all unused or free segments in the segmented memory.

0014The storage of transmission units described above is particularly suited to use in a network communications device, e.g. for interworking between the ATM network and the Ethernet network. In a network communications device which stores the transmission units using the process described above, the transmission units can be stored in a particularly efficient manner and be efficiently processed to adapt their data structures. Thus, for example, processing of the header section of a transmission units can be done in a simple way by dividing into descriptor segments and data segments. The information inserted into the fields of the descriptor segment is of particular importance in this context.

0015There is a significant advantage in using lists to store transmission units, in particular with reference to transmission units which have no fixed length. Thus, the content of the transmission unit can be flexibly distributed over several data segments. Equally, several elementary transmission units which belong together of a higher level transmission unit, e.g. of a higher level AAL5 transmission unit which comprises several ATM cells, can be stored in a common list.

0016When adapting the data structure of the transmission units, it is particularly advantageous to use a processing based on pointers which point to the segments of a list so that there is only a movement of the pointers but not of the data in the segmented memory.

0017Further advantages of the present invention can be seen in the following detailed description.

0018In the following the invention will be described in more detail with reference to the embodiments described hereinafter.

0019Hereinafter, a preferred embodiment of the invention will be described in more detail with reference to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

0020<figref idref="DRAWINGS">FIG. 1</figref> is a schematic representation of the structure of a transmission unit in the form of a list of segments according to an embodiment of the present invention,

0021<figref idref="DRAWINGS">FIG. 2</figref> is a schematic representation of the structure of a descriptor segment according to the embodiment of the present invention,

0022<figref idref="DRAWINGS">FIG. 3</figref> is a schematic representation of the structure of a segmented memory, and a linkage of segments to lists in the segmented memory via a table memory according to the embodiment of the present invention,

0023<figref idref="DRAWINGS">FIG. 4</figref> is a schematic representation of the data flow in a network communications device for transferring data between an ATM network and an Ethernet network according to the embodiment of the present invention,

0024<figref idref="DRAWINGS">FIG. 5</figref> shows the data flow from the ATM network to the Ethernet network in the network communication device according to the embodiment of the present invention,

0025<figref idref="DRAWINGS">FIG. 6</figref> shows the data flow from the Ethernet network to the ATM network in the network communication device according to the embodiment of the present invention.

DETAILED DESCRIPTION

0026In <figref idref="DRAWINGS">FIG. 1</figref> a list <b>40</b> of segments is shown by which a transmission unit is stored in a segmented memory, using a process according to the embodiment of the present invention. The segmentation of the segmented memory is selected in accordance with a length of the payload section of elementary transmission units in the form of ATM cells in an ATM network of 48 bytes. The list comprises descriptor segments <b>100</b> and data segments <b>200</b>. The segments are stored in a segmented memory which is addressable by memory addresses. The first element in the list is a descriptor segment <b>100</b>, which contains a reference to the memory address of a data segment <b>200</b> at the end of the list <b>40</b>. The list may store an Ethernet frame, i.e. a transmission unit of an Ethernet network or an AAL5 transmission unit which is made up of several ATM cells. As the length of these transmission units exceeds the length of the segments in the segmented memory, they are stored in several data segments <b>200</b>. Thus, the first data segment <b>200</b> of the list <b>40</b> may contain a header section of the Ethernet frame. Special information from the header section is inserted into the descriptor segments <b>100</b>.

0027If the transmission unit is a AAL5 transmission unit which encompasses a trailer section which is placed after the payload section in the transmission unit, special information from this trailer section may be inserted into the descriptor segments <b>100</b>.

0028The storage of a complete ATM cell including its header section with a length of 5 bytes and its payload section with a length of 48 bytes may for example be effected in a list consisting of a descriptor segment <b>100</b> and two data segments <b>200</b>, the first of the data segments <b>200</b> containing the header section of the ATM cell. In this case, which memory section in the first data segment <b>200</b> is allocated to the header section, is defined in the descriptor segment <b>100</b>.

0029As shown in <figref idref="DRAWINGS">FIG. 2</figref>, the descriptor segments comprise fields <b>101</b>, <b>103</b>, <b>105</b>, <b>106</b>, <b>107</b>, <b>108</b>, <b>109</b>, <b>110</b>, which describe the data structure of the transmission unit in the segmented memory. Depending upon their function, the fields have differing numbers of bits or bytes.

0030An output enumerator field <b>101</b> describes a number of planned processing procedures for this descriptor segment <b>100</b> and the corresponding transmission unit. This is particularly advantageous in the case of so-called multicast procedures when for example multiple parallel output of a transmission unit is planned.

0031A segment enumerator field <b>103</b> describes the number of segments <b>100</b>, <b>200</b> which the transmission unit in the segmented memory contains. A length field <b>105</b> describes the length of the transmission unit in bytes.

0032A status field <b>106</b> contains several subfields which indicate whether a further descriptor segment follows in the list and whether an error has occurred in the transmission unit. The errors can be for example checksum errors, a maximum permissible transmission unit length being exceeded or a memory overflow error.

0033A type field <b>107</b> describes the type of transmission unit. transmission units can be of AAL5 protocol for an EoA (Ethernet over ATM), i.e. to send Ethernet frames over the ATM network, Ethernet frames, PTM transmission units (PTM=packet transport mode), AoE transmission units, i.e. ATM cells encapsulated in Ethernet frames, or administration cells filtered out from an EoA flow, so-called AOM cells. The AoE transmission units and the EoA transmission units are of particular importance for ATM-Ethernet interworking.

0034A connection identification field <b>108</b> serves to identify the transmission units in connection with an individual connection allocation. A memory address field <b>109</b> contains the memory address of the data segment at the end of the list and thus defines the end of the list.

0035The descriptor segment <b>100</b> also contains ten further fields <b>110</b> whose function or type is defined in each case by a subfield contained within each one. The number of the further fields <b>110</b> used in one of the descriptor segments <b>100</b> is variable, i.e. these fields are optional. A sequence of used further fields <b>110</b> is terminated by a specific further field <b>110</b> whose function is defined as end field by the subfield contained within it, i.e. this type of the variable fields <b>110</b> marks the end of the sequence. If in one of the descriptor segments <b>100</b> no features of the transmission unit to be defined via the further fields <b>110</b>, a first of the further fields <b>110</b> is characterised as end field.

0036The further fields <b>110</b> may for example contain the memory address of a specified data segment <b>200</b> and therein define a memory section. This can be in particular header section to be modified during the adaptation of the data structure, which is stored in the defined data segment <b>200</b>.

0037In addition, the further fields <b>110</b> can define a repeated execution of a specified operation on subsequent elements of a list <b>40</b>. This can in particular be read operations. The field then contains the memory address of those data segments <b>200</b> which are located at the beginning of the memory section to be defined, and the number of repetitions, i.e. the number of segments on which the operation is to be carried out. In this way, using a repeated read operation enables a large memory section to be defined. This type of further fields <b>110</b> is particularly advantageous for defining a memory section which comprises several data segments <b>200</b>, e.g. to define the memory section in which the payload section of an Ethernet frame is stored.

0038A further type of further fields <b>110</b> is used to record data to be used or inserted during a specified operation. These data can be data from the trailer section of AAL5 transmission units, which for example contain the length of an AAL5 transmission unit, so that when adapting the data structure of the AAL5 transmission unit no separate calculation of its length is necessary. This data may also be a so-called UUI field (user-user-indication field) from the trailer section of AAL5 transmission units. The latter is particularly advantageous as this data from the trailer section has to be passed on to higher protocol layers.

0039The fields <b>101</b>, <b>103</b>, <b>105</b>, <b>106</b>, <b>107</b>, <b>108</b>, <b>109</b>, <b>110</b> of the descriptor segments <b>100</b> are used to describe the data structure of the corresponding transmission unit. The information contained therein is necessary for efficient processing during the adaptation of the transmission unit's data structure to a different network protocol. In this case, in particular the optional further fields <b>110</b> are used which describe insert, replace and erase operations.

0040In the event that the ten further fields <b>110</b> of the first descriptor segment <b>100</b> are not adequate to store the required information, it is provided that the corresponding list <b>40</b> contains further descriptor segments <b>100</b>. The further descriptor segments <b>100</b> of the list differ solely by the further fields <b>110</b> of the first descriptor segment <b>100</b>. A final descriptor segment <b>100</b> in the list <b>40</b> differs also in the subfield of the status field <b>106</b> which indicates whether further descriptor segments <b>100</b> follow in the list from the remaining descriptor segments <b>100</b> of the list.

0041<figref idref="DRAWINGS">FIG. 3</figref> is a schematic representation of the structure of the segmented memory <b>10</b> and of the connection of segments in the segmented memory <b>10</b> through a table memory <b>20</b> of the lists <b>40</b>. The segmented memory <b>10</b> shows two descriptor segments <b>100</b> and two data segments <b>200</b>. The descriptor segments <b>100</b> and the data segments <b>200</b> belong to the same list <b>40</b>. The first descriptor segment <b>100</b> contains the memory address of the data segment <b>200</b> in the memory address field <b>109</b> at the end of the list.

0042Entries <b>22</b> in a table memory <b>20</b> are addressable via the memory addresses of the segments on the segmented memory <b>19</b>, which are allocated to the corresponding entries <b>22</b>. In the table memory <b>20</b>, one entry <b>22</b> is allocated to each of the segments in the segmented memory <b>10</b> and contains the memory address of a next entry <b>22</b> in the table memory <b>10</b>. In this manner the entries <b>22</b> in the table memory <b>20</b> are linked to lists so that the lists of the entries <b>22</b> in the table memory <b>20</b> contain memory addresses of the lists <b>40</b> of segments in the segmented memory <b>10</b>.

0043The lists of segments in the segmented memory <b>10</b> can be the lists <b>40</b> of descriptor segments <b>100</b> and data segments <b>200</b>, by which a transmission unit is stored or a list of free segments in the segmented memory <b>10</b>.

0044Access to the lists in the segmented memory is through list entry fields <b>40</b><i>a</i>, <b>40</b><i>b. </i>

0045<figref idref="DRAWINGS">FIG. 4</figref> is a schematic representation of the data flow in a network communications component according to the embodiment of the present invention. The network communication component is connected with the ATM network and the Ethernet network through interfacing means <b>50</b><i>a</i>, <b>50</b><i>b</i>. The interfacing means <b>50</b><i>a</i>, <b>50</b><i>b </i>are specifically a first bidirectional interface <b>50</b><i>a </i>to the ATM network and two further bidirectional interfaces <b>50</b><i>b </i>to the Ethernet network. The latter can be fast Ethernet interfaces or gigabit Ethernet interfaces.

0046Data received from the interfacing means <b>50</b><i>a</i>, <b>50</b><i>b </i>are converted into an internal format within the formatting blocks <b>52</b><i>a </i><b>52</b><i>b</i>. The internal format uses units with a header section with a length of 16 bytes and a payload section with a length of 48 bytes. The formatting of transmission units that have been received from the Ethernet network differs from that of transmission units that are received from the ATM network and is therefore executed in a separate formatting block <b>52</b><i>b</i>. One input memory driver <b>60</b><i>a</i>, <b>60</b><i>b </i>in a processing block <b>80</b> is allocated to each of the interfacing means <b>50</b><i>a</i>, <b>50</b><i>b</i>. The processing block contains the segmented memory <b>10</b> and the memory drivers <b>60</b><i>a</i>, <b>60</b><i>b </i>undertake the storage of the data in the segmented memory <b>10</b>. The transmission units are processed in the processing block <b>80</b>. Transmission units whose processing has been completed are read out through output memory drivers <b>62</b><i>a</i>, <b>62</b><i>b </i>allocated to interfacing means <b>50</b><i>a</i>, <b>50</b><i>b</i>. Transfer to the interfacing means <b>50</b><i>b </i>to the Ethernet network occurs directly. In the case of the interfacing means <b>50</b><i>a </i>to the ATM network, an additional format conversion takes place in the formatting block <b>52</b><i>a</i>. The memory drivers <b>60</b><i>a</i>, <b>60</b><i>b</i>, <b>62</b><i>a</i>, <b>62</b><i>b </i>are DMA engines implemented at hardware level. In order to keep its manufacture and use as simple and effective as possible, the network communication component is integrated on a single semiconductor chip.

0047<figref idref="DRAWINGS">FIG. 5</figref> is a detail view of the data flow from the ATM network to the Ethernet network in the processing block <b>80</b>. The data arrive at the input memory driver <b>60</b><i>a </i>in the internal format. The transmission units are stored in lists <b>40</b> made up of the descriptor segments <b>100</b> and the data segments <b>200</b>. The storage and the compilation of transmission units containing Ethernet frames made up of several ATM cells, i.e. EoA transmission units occurs in input segment lists allocated for that purpose. Such a list <b>40</b> is released for processing when the EoA transmission unit assembled in it is complete, by passing the memory address <b>24</b> of the first descriptor segment <b>100</b> of the list <b>40</b> to a processing list <b>45</b> for incoming transmission units. For ATM cells which are destined to be encapsulated in an Ethernet frame, i.e. AoE transmission units the corresponding memory address <b>24</b> is directly passed to the processing list <b>45</b> for incoming transmission units.

0048The processing of the transmission units to adapt the data structure occurs sequentially through a special processing list <b>45</b> in a processing unit <b>70</b>. During processing in particular the header sections of the transmission units are deleted, inserted or modified. This is done using the information held in the fields of the descriptor segment <b>100</b>.

0049After processing has been competed the segments of the transmission units are assembled in output segment lists. Such a list <b>40</b> is released for output by passing the memory address <b>24</b> of the first descriptor element <b>100</b> of the list <b>40</b> to a processing list <b>45</b> for outgoing data. For the AoE transmission units the corresponding memory address <b>24</b> is directly passed to the processing list <b>45</b> for outgoing transmission units, without first being assembled in a list <b>40</b>.

0050<figref idref="DRAWINGS">FIG. 6</figref> shows the data flow from the Ethernet network to the ATM network in the processing block <b>80</b>. In this case the EoA transmission units are Ethernet frames which are encapsulated into the AAL5 transmission units and the AoE transmission units are ATM cells encapsulated in Ethernet frames. The processing of the AoE transmission units and of the EoA transmission units happens basically in analogue fashion to the data flow explained under <figref idref="DRAWINGS">FIG. 5</figref>. However, it is not necessary to assemble the transmission units into output segment lists as the transmission units passed to the ATM network correspond to individual ATM cells.

0051The storage of transmission units for interworking described above, as described in the example of the network communication component, represents a particularly efficient solution. In particular, it facilitates efficient storage of the payload section of ATM cells, e.g. for reassembly within the AAL5 protocol, efficient storage of Ethernet frames with variable length, storage of complete ATM cells including header section and payload section, and flexible processing of the stored transmission units.