Network devices and methods for communication

By structuring the destination address with a checksum-neutral network identifier sequence, the network device ensures error detection in segment routing without an SRH, addressing the challenge of verifying packet integrity across transmission paths.

WO2024235449A1PCT designated stage expired Publication Date: 2024-11-21HUAWEI TECH CO LTD +1
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2023/063062
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-16
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

In segment routing, the absence of a segment router header (SRH) prevents the destination network device from verifying the layer 4 checksum, as each network device along the path changes the destination address, making it impossible for the destination to detect errors during transmission.

Method used

A network device generates a destination address structure with a network identifier followed by multiple network device identifiers, where the checksum of all identifiers except the last one is zero, allowing the checksum to remain consistent across transmission, enabling error detection without an SRH.

Benefits of technology

This solution enables segment routing without an SRH, allowing the destination to verify packet integrity and perform error detection, while maintaining compatibility with conventional network protocols like IPv6.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2023063062_21112024_PF_FP_ABST
    Figure EP2023063062_21112024_PF_FP_ABST
Patent Text Reader

Abstract

The disclosure relates to a network device for communication. The network device is configured to generate a data structure comprising a destination address. The destination address comprises, starting from its most significant bit, a network identifier, multiple network device identifiers each identifying another network device, and a field directly preceding a last network device identifier of the multiple network device identifiers. A checksum of the field and all one or more consecutive network device identifiers of the multiple network device identifiers preceding the field equals zero. Another network device, and methods for communication are disclosed.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] NETWORK DEVICES AND METHODS FOR COMMUNICATION

[0002] TECHNICAL FIELD

[0003] The present disclosure relates to network devices for communication, and methods for communication.

[0004] BACKGROUND

[0005] The internet protocol version 6 (IPv6) is an example of a network protocol for communication between network devices that enables an optional feature called source routing. Source routing is a routing approach in which the source of a packet (e.g. network device transmitting the packet, may be referred to as sender) determines the path of the packet (to the destination, i.e. the intended network device) by incorporating a list of routers in the header (packet header) of the transmitted packet. The source may be referred to as source network device or sender. The destination may be referred to as destination network device or (intended) receiver. A variant of source routing is called segment routing (SR), in which the source of a packet may incorporate a segment routing header (SRH) as an extension header of a packet (e g. IPv6 packet), and the SRH includes the list of routers along the path from the source to the destination. Each router on the list is represented by a segment identifier (SID), which may be for example 128 bits long (in the case of IPv6).

[0006] A list of routers, where each router is represented by 128 bits, may incur a large overhead on IPv6 packets that include a SRH. Therefore, SRH compression is intended to reduce the overhead by compressing several router addresses into a single segment identifier (SID). Thus, an SRH may include multiple SIDs, where each SID is comprised of multiple compressed segment identifiers (C-SIDs).

[0007] The structure of a SID that includes a list of C-SIDs may comprise a prefix (may be referred to as Locator-Block) that specifies the network (or location) address and the list of C-SIDs.

[0008] SUMMARY

[0009] In source routing, for example in segment routing, layer 4 protocols, such as transmission control protocol (TCP) and user datagram protocol (UDP), may use a checksum function for error detection. The checksum may be a two-octet field (2-octet field) that resides in the layer 4 header (e.g. TCP header in case TCP is used as layer 4 protocol, or UDP header in case UDP is used as layer 4 protocol). The aforementioned checksum may be referred to as “layer 4 checksum”. The source (i.e. sender) of a packet, such as a TCP packet or UDP packet, may compute the value of the checksum field as a function of the header and data of the packet. The destination (i.e. the receiver) may re-compute the checksum value, and compares the recomputed checksum value to the received checksum value (that was computed by the source). If both values are equal, the check is successful. Otherwise, it is assumed that there is an error somewhere along the packet, and the packet is discarded.

[0010] The layer 4 checksum of a packet may be computed by performing a hash function that takes as an input the layer 4 header of the packet, the layer 4 payload of the packet and a layer 3 pseudo-header (e.g. IP pseudo-header in case the IP protocol is used for communication). The pseudo-header (e g. IP pseudo-header) comprises a few fields from the layer 3 header (e g IP header, such as IPv6 header in case of the IPv6 protocol) including the source and destination address (e.g. source and destination IP address, such as source and destination IPv6 address).

[0011] For example performing the hash function may comprise in a first step breaking the input, i.e. the layer 4 header, the layer 4 payload and the layer 3 pseudo-header into 16-bit words; in a second step computing the one’s complement sum of these words; and in a third step inverting the bits of the result. In this context, the one’s complement sum refers to a summation that satisfies the following conditions: The result of the sum always produces a 16-bit word. If the sum is a word that is represented by more than 16 bits due to a carry, then the aforementioned first step and second step of the hash function algorithm are repeated until the result is 16 bits long.

[0012] For example, assuming that the input to the hash function equals to the hexadecimal representation OxFO 00 F0 00, i.e. the layer 4 checksum of OxFO 00 F0 00 is to be computed, the following is performed. In the first step, the input OxFO 00 F0 00 is broken into 16 bits words, which are OxFO 00 and OxFO 00 for the assumed example. In the second step the one’s complement sum of these words is computed, which equals to OxlEOOO (i.e. OxFOOO+OxFOOO = OxlEOOO). Since the result (i.e. OxlEOOO) requires more than 16 bits to be represented, the aforementioned first step and second step are repeated. Thus, in the repeated first step, OxlEOOO is broken into 16 bits words, which are 0x0001 and Ox E000. In the repeated second step the one’s complement sum of these words is computed, which equals to OxEOOl (i.e. 0x0001 +0xE000 = OxEOOl = 0b 1110 0000 0000 0001).Since the result (i.e. OxEOOl = 0b 1110 0000 0000 0001) is a 16 bits word and, thus, does not require more than 16 bits the thirds step is performed. In the third step the bits of the result of the repeated step 2 (i.e. OxEOOl = Ob 1110 0000 0000 0001) are inverted, which equals to Ob 0001 1111 1111 1110 = OxlFFE. Thus, the layer 4 checksum computed for the input OxFO 00 FO 00 equals to Ob 0001 1111 1111 1110 in binary representation or OxlFFE in hexadecimal representation. In the above description, “Ox” denotes hexadecimal representation, and “Ob” denotes binary representation.

[0013] A property of the layer 4 checksum is that the inversion of the one’s complement sum of the 16 bits words generated in step 1 from the initial input for computing the checksum and the computed checksum equals to zero. In case of the above-described example, the two 16 bits words generated in step 1 from the initial input for computing the checksum are OxFO 00 and OxFO 00; and the computed checksum is OxlFFE The inversion of the one’s complement sum of these three 16 bits words equals to zero. Namely, OxFOOO+OxFOOO+OxlFFE = OxlFFFE, wherein the result has more than 16 bits. Thus, the result is broken into the two 16 bits words 0x0001 and OxFFFE. The sum of these two 16 bits words is computed OxOOOl+OxFFFE = OxFFFF. The result is a 16 bits word and, thus, the result is inverted, wherein the inverted result is 0x0000.

[0014] An example of an IPv6 data structure, such as an IPv6 packet, is shown in Fig. 7a. As shown in Fig. 7a, the data structure 200 comprises a layer 2 header 301, a layer 3 header 302 being an IPv6 header, a segment routing header 303 (SRH) (as a layer 3 header option), a layer 4 header 304 comprising a checksum 400 (may be referred to as layer 4 checksum) of the data structure and a layer 4 payload 305. In Fig. 7, the layer 2 is indicated by the references sign “L2”, the layer 3 is indicated by the reference sign “L3”, and the layer 4 is indicated by the reference sign “L4” .

[0015] A SRH, if included in the packet (e.g. an IPv6 packet), is not included in a computation of a layer 4 checksum.

[0016] As described above, the destination IP address (may be referred to as destination address) is included in the input of the layer 4 checksum computation by the source. However, if the packet includes an SRH, then according to the IPv6 protocol, the source of the packet computes the layer 4 checksum using the final destination IP address (may be referred to as final destination address) in the SRH instead of using the destination IP address in the IPv6 header. Therefore, when the packet (transmitted from the source by source routing, such as segment routing) reaches the destination at the end of the path (via which the packet has been transmitted from the source), the destination computes the checksum based on the destination IP address in the IPv6 header. The path may be understood as one or more network devices via which a data structure (e.g. packet) received by a destination has been sent from the source of the received data structure. A part of the path between two network devices (e g. the source and a network device being a router; two network devices each being a router or a network device being a router and the destination) may be referred to as “segment”.

[0017] In conventional segment routing using an SRH, the layer 4 checksum is computed by the source according to the destination address. In segment routing, such as compressed segment routing, without using an SRH, the layer 4 checksum is computed according to the transmitted destination address, which means the destination cannot verify the checksum. Namely, during the segment routing each network device (i.e. router) of the path from the source to the destination changes the destination address. Thus, the destination address received by the destination differs from the initial destination address that was transmitted by the source. Therefore, a layer 4 checksum computation by the source using the initial destination address differs from a layer 4 checksum computation by the destination using the destination address received by the destination. Therefore, in segment routing, such as compressed segment routing, without using an SRH the destination cannot use a computation of the layer 4 checksum in order to check whether an error along the data structure has occurred during transmission via the path from the source to the destination.

[0018] In view of the above, this disclosure aims to provide network devices and methods for communication that are improved with regard to segment routing (SR). An object is to provide network devices and methods for communication that allow performing segment routing (e.g. compressed segment routing) without a segment router header (SRH) while allowing a destination network device to check whether an error has occurred during transmission of a received data structure via a path from a source or to check whether an error is present along a data structure received by the destination network device.

[0019] These and other objectives are achieved by the solution of this disclosure as described in the independent claims. Advantageous implementations are further defined in the dependent claims. A first aspect of this disclosure provides a network device for communication. The network device is configured to generate a data structure comprising a destination address. The destination address comprises, starting from its most significant bit, a network identifier, multiple network device identifiers each identifying another network device, and a field directly preceding a last network device identifier of the multiple network device identifiers. A checksum of the field and all one or more consecutive network device identifiers of the multiple network device identifiers preceding the field equals zero.

[0020] In other words, according to the first aspect a network device is proposed that generates a data structure comprising a destination address such that all, except the last network device identifier, of the network device identifiers of the destination address have not impact on a computation of a checksum, such as a layer 4 checksum, of the data structure. The term “effect” may be used as a synonym for the term “impact”. Namely, the checksum of the field and the one or more consecutive network device identifiers preceding the field equals to zero. Therefore, changing the multiple network device identifiers (such as deleting a network device identifier adjacent to the network identifier) when transmitting the data structure from the network device to a router network device (may be referred to as router) does not cause a difference between a computation result of computing the checksum (such as the layer 4 checksum) at the network device and a computation result of computing the checksum at the destination network device. This is true as long as no error occurs during the transmission of the data structure from the network device via one or more routers to the destination and, thus, there is no error along the data structure received by the destination. Namely, when the layer 4 checksum is computed at the network device, the one or more consecutive network device identifiers preceding the field do not contribute to the checksum, because the checksum of the field and the one or more consecutive network device identifiers equals to zero. Thus, when the data structure with the destination address is received by the destination, wherein the received destination address merely comprises the network identifier and the last network device identifier of the initial destination address, the computation of the layer 4 checksum by the destination (assuming no error has occurred during the transmission of the data structure from the source to the destination) will generate the same result as the computation of the layer 4 checksum by the network device. Namely, as described already above, due to the field of the initial destination address the one or more consecutive network device identifiers preceding the field of the initial destination address do not contribute to the checksum. Thus, for the initial destination address, only the network identifier and the last network device identifier contribute to the checksum. The initial destination address is the destination address of the data structure generated by the network device.

[0021] Thus, the network device of the first aspect allows performing segment routing (e.g. compressed segment routing) without a segment router header (SRH) while allowing a destination network device to check whether an error has occurred during transmission of a data structure received by the destination network device. The network device of the first aspect achieves this without changing a network protocol, such as the IPv6 protocol, for communicating the data structure.

[0022] Further, since the network device according to the first aspect merely adds an additional field to the destination address without changing the network device identifiers, conventional segment routing may be performed. That is, the data structure may be transmitted by the network device to a conventional network device, such as a conventional router. This allows establishing a hybrid network with network devices according to this disclosure and conventional network devices.

[0023] The network device may be configured to communicate according to a network protocol. That is, the network device may be a network device for communication according to a network protocol. The network protocol may be the internet protocol (IP). For example, the network protocol may be IPv6. IPv6 stands for “internet protocol version 6”. The destination address may be abbreviated by the term “address”. The destination address may be an IP address, i.e. destination IP address, such as destination IPv6 address. The network device may be a node of a network, i.e. it may be part of the network. The network device may be a host. The network device may be a computer. The network device may be a server. The network device may be a network interface card (NIC). The network device may be referred to as “source” or “source network device”.

[0024] The destination address of the data structure comprises information on a destination network device (for which the data structure is intended) and on the path (to the destination network device). The last network device identifier (from the perspective of the most significant bit of the destination address) of the multiple network device identifiers of the destination address may indicate a destination network device. That is, it may be a destination network device identifier. The term “destination identifier” may be used as a synonym for the term “destination network device identifier”. The one or more other network device identifiers of the multiple network device identifiers of the destination address may indicate one or more router network devices (may be referred to as one or more routers) for forwarding or routing the data structure from the network device to the destination. That is, the one or more other network device identifiers may be one or more router network device identifiers. The term “router identifier” may be used as a synonym form the term “router network device identifier”.

[0025] At least one, optionally each, of the multiple network device identifier may comprise location information (e.g. a location field) and optionally function information (e g. a function field). Optionally, at least two of the multiple network device identifiers may have a different length (i.e. equal to a different number of bits). The multiple network device identifiers may be an integer number of 16-bit words. That is, each network device identifier may have a number of bits that equals to 16 bits or an integer multiple of 16 bits, wherein the integer multiple is greater or equal to two.

[0026] The destination address of the data structure comprises information on routing the data structure to a destination network device. The routing may be a segment routing, such as compressed segment routing. The network device may be configured to perform segment routing (e.g. compressed segment routing) by generating the data structure with the destination address, as described herein. The network device may be configured to provide or allow segment routing (SR), such as compressed segment routing. The network device may be configured to generate the data structure with the destination address according to a segment routing scheme (e.g. compressed segment routing scheme). The destination address may comprise 128 bits, for example in case the network device is configured to communicate the data structure according to the IPv6 protocol.

[0027] The data structure may be a packet, e.g. a data packet. For example, the data structure may be an IPv6 packet.

[0028] The network identifier may be a prefix of the destination address. The network identifier may be referred to as “locator block” or “location”. The network identifier may be a network ID or net ID. The network identifier may be the IPv6 network identifier in case the network device is configured to communicate according to the IPv6 network protocol. The network device may be configured for segment routing. The network device identifiers may be compressed segment identifiers (C-SIDs). The network device identifiers may be a segment list of multiple C-SIDs. The terms “multiple” and “two or more” may be used as synonyms. The terms “identifier of a network” and “identifier of a network device” may be used as synonyms for the terms “network identifier” and “network device identifier”, respectively.

[0029] The field may be referred to as “checksum neutral value field”. The checksum may be a layer 4 checksum. For example, the checksum may be a layer 4 checksum according to the IP protocol, e.g. the IPv6 protocol. The checksum of the field and all one or more consecutive network device identifiers of the multiple network device identifiers preceding the field may be computed by performing a hash function. The network device may be configured to compute (i.e. generate) the field such that the checksum (e.g. the layer 4 checksum) of the field and all one or more consecutive network device identifiers of the multiple network device identifiers preceding the field equals zero.

[0030] Optionally, the destination address of the data structure additionally comprises a last field arranged directly after the last network device identifier of the multiple network device identifiers; wherein a checksum of the last field and all one or more consecutive network device identifiers of the multiple network device identifiers preceding the last field equals zero. The aforementioned one or more consecutive network device identifiers of the multiple network device identifiers preceding the last field is or comprise the last network device identifier of the multiple network device identifiers. The term “end field” may be used as a synonym for the term “last field”. The term “last field” or “end field” is not to be understood such that there are no optional implementation forms, in which additional information (i.e. bits) may be arranged after the “last field” or “end field”. That is, optionally the destination address of the data structure may comprise information (i.e. bits) after the optional last field. Thus, the term “last field” is chosen to highlight that the last field is arranged directly after the last network device identifier of the multiple network device identifiers. Nevertheless, there may be optional implementation forms, in which there is not additional information (i.e. bits) arranged after the last field.

[0031] The network device may be configured to compute (i.e. generate) the last field such that the checksum (e.g. layer 4 checksum) of the last field and all one or more consecutive network device identifiers of the multiple network device identifiers preceding the last field equals zero. Optionally, in case the destination address comprises two network device identifiers, the field and the optional last field, each network device identifier has a field directly arranged after it. Thus, the destination address comprises the network identifier that may be followed by pairs of a network device identifier and a field, wherein the checksum of the network device identifier and the field of each pair equals zero. The aforementioned pairs may be compressed segment identifiers (C-SIDs).

[0032] The description with regard to the field (directly preceding the last network device identifier) is correspondingly valid for the optional last field. In case a checksum is mentioned herein, the checksum may be a layer 4 checksum.

[0033] The term “consecutive” means “following one after another without others coming in between”, i.e. “following each other continuously (without any interruption)”. For example, consecutive network device identifiers are network device identifiers that are adjacent to each other without anything else, such as a field, being arranged between any two of the aforementioned network device identifiers. In other words, consecutive network device identifiers are network device identifiers arranged next to each other or in succession such that any two of them are not separated by anything else, such as a field.

[0034] The passages “(arranged) in front of’ and “(arranged) previous to” may be used as synonym for the term “preceding”. Accordingly, the passages “(arranged) directly in front of’ and “(arranged) directly previous to” may be used as synonym for the term “directly preceding”.

[0035] The passage “a field directly preceding a last network device identifier of the multiple network device identifiers” may mean that the field is arranged between the second last network device identifier and the last network device identifier of the multiple network device identifiers, from the perspective of the most significant bit of the destination address.

[0036] In an implementation form of the first aspect, the network device is configured to transmit the data structure to a network device that is indicated by a network device identifier adjacent to the network identifier of the destination address.

[0037] The network device may be configured to generate and transmit the data structure with the destination address according to a segment routing scheme (e.g. compressed segment routing scheme). In other words, the network device may be configured to transmit the data structure according to the segment routing scheme (e.g. compressed segment routing scheme). The network device may be configured to transmit the data structure with the destination address to a destination network device (i.e. destination) via one or more router network devices (i.e. one or more routers) optionally according to a segment routing scheme (e.g. compressed segment routing scheme). The one or more router network devices may be one or more network devices according to the second aspect of the disclosure. Optionally, in case of multiple router network devices, at least one of the multiple router network devices (except of the router network device directly before the destination network device) may be a conventional router network device. The aforementioned router network device directly before the destination network device may be referred to as “last-hop-router”. The destination network device may be a conventional destination network device.

[0038] The network device, the one or more router network devices and the destination network device may be nodes of a network, i.e. they may be part of a network. The number of router network devices via which the network device intends to transmit the data structure to a destination network device is one less than the number of multiple network device identifiers of the destination address of the data structure.

[0039] The passage “network device identifier directly after the network identifier” may be used as a synonym for the passage “network device identifier adjacent to the network identifier”. The term “next to” may be used as a synonym for the term “adjacent”. The term “adjacent” is to be under-stood such that a first element (e g. a network device identifier”) that is adjacent to a second element (e.g. the network identifier) means that the first element and the second element are arranged next to each other without anything else, such as field, being arranged between them.

[0040] Optionally, the network device may be configured to transmit the data structure directly to a destination network device. In this case, the network device may be configured to generate the data structure such that the destination address of the data structure comprises, starting from its most significant bit, a network identifier, a network device identifier identifying another network device (i.e. the destination network device), and optionally a last field that is directly arranged after the network identifier, wherein a checksum of the optional last field and the network device identifiers directly preceding the field equals zero.

[0041] In an implementation form of the first aspect, the destination address of the data structure additionally comprises at least one further field directly preceding a network device identifier of the multiple network device identifiers that is not adjacent to the network identifier and not the last network device identifier; and the further field is generated such that the checksum of the further field and all one or more consecutive network device identifiers of the multiple network device identifiers preceding the further field equals zero.

[0042] In other words, the checksum of the further field and all one or more consecutive network device identifiers of the multiple network device identifiers preceding the further field equals zero. The checksum may be the layer 4 checksum. The network device may be configured to compute (i.e. generate) the further field such that the checksum (e g. layer 4 checksum) of the further field and all one or more consecutive network device identifiers of the multiple network device identifiers preceding the further field equals zero.

[0043] The description with regard to the field (directly preceding the last network device identifier) is correspondingly valid for the optional at least one further field.

[0044] In an implementation form of the first aspect, the destination address of the data structure additionally comprises a further field directly preceding each network device identifier of the multiple network device identifiers that is not adjacent to the network identifier and not the last network device identifier; and the further field is generated such that the checksum of the further field and a network device identifier of the multiple network device identifiers directly preceding the further field equals zero.

[0045] In other words, the checksum of the further field (i.e. each further field) and a network device identifier of the multiple network device identifiers directly preceding the further field equals zero. The checksum may be the layer 4 checksum. The network device may be configured to compute (i.e. generate) the further field (i.e. each further field) such that the checksum (e g. layer 4 checksum) of the further field and the network device identifier of the multiple network device identifiers directly preceding the further field equals zero.

[0046] The description with regard to the field (directly preceding a last network device identifier) is correspondingly valid for each optional further field.

[0047] In the aforementioned optional implementation form, optionally the aforementioned last field may be arranged directly after the last network device identifier of the multiple network device identifiers; wherein a checksum of the last field and the last network device identifier of the multiple network device identifiers directly preceding the last field equals zero. Optionally, in case the destination address comprises three or more network device identifiers, the field, an optional the one or more further fields and the last field, each network device identifier has a field directly arranged after it. Thus, the destination address comprises the network identifier that may be followed by pairs of a network device identifier and a field, wherein the checksum of the network device identifier and the field of each pair equals zero. The aforementioned pairs may be compressed segment identifiers (C-SIDs).

[0048] The description with regard to the field (directly preceding a last network device identifier) and optional further field(s) is correspondingly valid for the optional last field.

[0049] In an implementation form of the first aspect, the further field comprises 16 bits.

[0050] In an implementation form of the first aspect, the data structure does not comprise a segment routing header.

[0051] In other words, the network device may be configured to generate the data structure such that the data structure does not comprise a segment routing header.

[0052] In an implementation form of the first aspect, a layer 3 header of the data structure comprises the destination address.

[0053] In other words, the network device may be configured to generate the data structure such that a layer 3 header of the data structure comprises the destination address. In case the network device is configured to communicate according to the IP protocol, e.g. the IPv6 protocol, the layer 3 header is an IP header, e g. IPv6 header.

[0054] In an implementation form of the first aspect, the network device is configured to compute the checksum of a part of the destination address that is adjacent to the network identifier of the destination address, wherein a layer 4 header of the data structure comprises the computed checksum.

[0055] In other words, the network device may be configured to compute the checksum of the multiple network device identifiers, the field and optionally the one or more optional further fields of the destination address. Optionally, the network device may be configured to compute the checksum of the multiple network device identifiers, the field and optionally the one or more optional further fields and the optional last field of the destination address. In an implementation form of the first aspect, the field comprises 16 bits.

[0056] In order to achieve the network device according to the first aspect of the disclosure, some or all of the implementation forms and optional features of the first aspect, as described above, may be combined with each other.

[0057] A second aspect of this disclosure provides a network device for communication. The network device is configured to receive a data structure with a destination address, and determine whether a network identifier and a network device identifier adjacent to the network identifier of the destination address equal an address of the network device. The network device is configured to, in case the network identifier and the network device identifier equal the address of the network device, generate a changed destination address of the received data structure by deleting the network device identifier of the destination address and shifting a rest of the destination address adjacent to the network identifier of the destination address, or deleting the network device identifier and a field directly after the network device identifier of the destination address and shifting a rest of the destination address adjacent to the network identifier of the destination address.

[0058] In other words, the network device is configured to delete the network identifier and shift a rest of the destination address adjacent to the network identifier of the destination address, in case no field (e.g. the field or optionally the optional further field as described with regard to the network device of the first aspect) is present directly after the network device identifier that is adjacent to the network identifier. The network device is configured to delete the network device identifier and a field directly after the network device identifier of the destination address and shift a rest of the destination address adjacent to the network identifier of the destination address, in case the field (e.g. the field or optionally the optional further field as described with regard to the network device of the first aspect) is present directly after the network device identifier that is adjacent to the network identifier.

[0059] The network device may be configured to communicate according to a network protocol. That is, the network device may be a network device for communication according to a network protocol. The network device may be a node of a network, i.e. it may be part of the network. The network device may be a computer. The network device may be a network interface card (NIC). The network device may be a router. The network device may be a switch (e.g. network switch).

[0060] The above description of the network device according to the first aspect, such as the description of the data structure, the type of communication, the type of network protocol, the field and so on, is correspondingly valid for the network device of the second aspect. The network device of the second aspect may be the network device of the first aspect.

[0061] In an implementation form of the second aspect, the network device is configured to transmit the data structure with the changed destination address to a network device identified by a network device identifier adjacent to the network identifier of the change destination address.

[0062] In other words, the network device may be configured to route the received data structure with the changed destination address. The network device may be configured to provide or allow segment routing (SR), such as compressed segment routing. The network device may be configured to generate the changed destination address of the data structure according to a segment routing scheme (SR scheme), such as a compressed segment routing scheme, and transmit the data structure. In other words, the network device may be configured to transmit the data structure according to the segment routing scheme.

[0063] In an implementation form of the second aspect, the network device is configured to, in case the network identifier and the network device identifier adjacent to the network identifier of the destination address does not equal the address of the network device, determine, using the destination address, a network device, to which the data structure is to be transmitted; and transmit the received data structure with the destination address to the determined network device.

[0064] In other words, the network device may be configured to, in case the network identifier and the network device identifier adjacent to the network identifier of the destination address does not equal the address of the network device, perform conventional routing, e.g. conventional segment routing. In an implementation form of the second aspect, the network device is configured to be triggered by information of the network device identifier adjacent to the network identifier of the destination address to delete the network device identifier of the destination address and shift the rest of the destination address adjacent to the network identifier of the destination address, or delete the network device identifier and the field directly after the network device identifier of the destination address and shift the rest of the destination address adjacent to the network identifier of the destination address.

[0065] The information of the network device identifier adjacent to the network identifier of the destination address may indicate whether a field (e.g. the field or optionally the optional further field as described with regard to the network device of the first aspect) is present directly after itself. Optionally, the aforementioned information is location information (e.g. a location field) and optionally function information (e.g. a function field) of the network device identifier adjacent to the network identifier of the destination address. In case a field (such as the field or the optional further field described with regard to the network device of the first aspect) is arranged directly after the network device identifier adjacent to the network identifier, the information of the network device identifier adjacent to the network identifier may indicate to the network device to delete the network device identifier and the field directly after the network device identifier of the destination address and shift the rest of the destination address adjacent to the network identifier of the destination address.

[0066] Optionally, the network device may be configured to be triggered by information received from outside the network device (e g. a network controller) to delete the network device identifier of the destination address and shift the rest of the destination address adjacent to the network identifier of the destination address, or delete the network device identifier and the field directly after the network device identifier of the destination address and shift the rest of the destination address adjacent to the network identifier of the destination address.

[0067] In an implementation form of the second aspect, the field comprises 16 bits. The above description of the network device according to the second aspect may be correspondingly valid for the network device of the first aspect.

[0068] The network device of the second aspect and its implementation forms and optional features achieve the same advantages as the network device of the first aspect and its respective implementation forms and respective optional features.

[0069] In order to achieve the network device according to the second aspect of the disclosure, some or all of the implementation forms and optional features of the second aspect, as described above, may be combined with each other.

[0070] A third aspect of the disclosure provides a method for communication. The method comprises generating a data structure comprising a destination address. The destination address comprises, starting from its most significant bit, a network identifier, multiple network device identifiers each identifying another network device, and a field directly preceding a last network device identifier of the multiple network device identifiers. A checksum of the field and all one or more consecutive network device identifiers of the multiple network device identifiers preceding the field equals zero.

[0071] The method may be a method for communicating according to a network protocol. The protocol may be for example IPv6.

[0072] In an implementation form of the third aspect, the method comprises transmitting the data structure to a network device that is indicated by a network device identifier adjacent to the network identifier of the destination address.

[0073] In an implementation form of the third aspect, the destination address of the data structure additionally comprises at least one further field directly preceding a network device identifier of the multiple network device identifiers that is not adjacent to the network identifier and not the last network device identifier; and the further field is generated such that the checksum of the further field and all one or more consecutive network device identifiers of the multiple network device identifiers preceding the further field equals zero.

[0074] In an implementation form of the third aspect, the destination address of the data structure additionally comprises a further field directly preceding each network device identifier of the multiple network device identifiers that is not adjacent to the network identifier and not the last network device identifier; and the further field is generated such that the checksum of the further field and a network device identifier of the multiple network device identifiers directly preceding the further field equals zero.

[0075] In an implementation form of the third aspect, the further field comprises 16 bits.

[0076] In an implementation form of the third aspect, the data structure does not comprise a segment routing header.

[0077] In an implementation form of the third aspect, a layer 3 header of the data structure comprises the destination address.

[0078] In an implementation form of the third aspect, the method comprises computing the checksum of a part of the destination address that is adjacent to the network identifier of the destination address, wherein a layer 4 header of the data structure comprises the computed checksum.

[0079] In an implementation form of the third aspect, the field comprises 16 bits.

[0080] The description of the network device of the first aspect is correspondingly valid for the method of the third aspect.

[0081] The method of the third aspect and its implementation forms and optional features achieve the same advantages as the network device of the first aspect and its respective implementation forms and respective optional features.

[0082] In order to achieve the method according to the third aspect of the disclosure, some or all of the implementation forms and optional features of the third aspect, as described above, may be combined with each other.

[0083] A fourth aspect of the disclosure provides a method for communication. The method comprises receiving a data structure with a destination address, and determining whether a network identifier and a network device identifier adjacent to the network identifier of the destination address equal an address of the network device. The method comprises, in case the network identifier and the network device identifier equal the address of the network device, generating a changed destination address of the received data structure by deleting the network device identifier of the destination address and shifting a rest of the destination address adjacent to the network identifier of the destination address, or deleting the network device identifier and a field directly after the network device identifier of the destination address and shifting a rest of the destination address adjacent to the network identifier of the destination address.

[0084] The method may be a method for communicating according to a network protocol. The protocol may be for example IPv6.

[0085] In an implementation form of the fourth aspect, the method comprises transmitting the data structure with the changed destination address to a network device identified by a network device identifier adjacent to the network identifier of the change destination address.

[0086] In an implementation form of the fourth aspect, the method comprises, in case the network identifier and the network device identifier adjacent to the network identifier of the destination address does not equal the address of the network device, determine, using the destination address, a network device, to which the data structure is to be transmitted; and transmit the received data structure with the destination address to the determined network device.

[0087] In an implementation form of the fourth aspect, the method comprises being triggered by information of the network device identifier adjacent to the network identifier of the destination address to delete the network device identifier of the destination address and shift the rest of the destination address adjacent to the network identifier of the destination address, or delete the network device identifier and the field directly after the network device identifier of the destination address and shift the rest of the destination address adjacent to the network identifier of the destination address.

[0088] In an implementation form of the fourth aspect, the field comprises 16 bits.

[0089] The description of the network device of the second aspect is correspondingly valid for the method of the fourth aspect.

[0090] The method of the fourth aspect and its implementation forms and optional features achieve the same advantages as the network device of the first aspect and its respective implementation forms and respective optional features. In order to achieve the method according to the fourth aspect of the disclosure, some or all of the implementation forms and optional features of the fourth aspect, as described above, may be combined with each other.

[0091] It has to be noted that all devices, elements, units and means described in the present application could be implemented in software or hardware elements or any kind of combination thereof. All steps which are performed by the various entities described in the present application as well as the functionalities described to be performed by the various entities are intended to mean that the respective entity is adapted to or configured to perform the respective steps and functionalities. Even if, in the following description of specific embodiments, a specific functionality or step to be performed by external entities is not reflected in the description of a specific detailed element of that entity which performs that specific step or functionality, it should be clear for a skilled person that these methods and functionalities can be implemented in respective software or hardware elements, or any kind of combination thereof.

[0092] BRIEF DESCRIPTION OF DRAWINGS

[0093] The above described aspects and implementation forms will be explained in the following description of specific embodiments in relation to the enclosed drawings, in which

[0094] Fig- 1 shows an example of a network device according to this disclosure.

[0095] Fig- 2 shows an example of the network device of Fig. 1.

[0096] Fig- 3 shows an example of the network device of Fig. 1.

[0097] Fig. 4 shows an example of the network device of Fig. 1.

[0098] Fig. 5 shows an example of a network device according to this disclosure.

[0099] Fig. 6 shows an example of the network device of Fig. 5.

[0100] Fig. 7a shows an example of a data structure.

[0101] Fig. 7b shows an example of a data structure according to this disclosure. Fig. 8a shows an example of a destination address of a data structure according to this disclosure.

[0102] Fig. 8b shows an example of a destination address of a data structure according to this disclosure.

[0103] Fig. 9 shows an example of a method according to this disclosure.

[0104] Fig. 10 shows an example of a method according to this disclosure.

[0105] In the Figures, corresponding elements are labeled with the same reference sign.

[0106] DETAILED DESCRIPTION OF EMBODIMENTS

[0107] Fig. 1 shows an example of a network device according to this disclosure. The network device of Fig. 1 is an example of the network device according to the first aspect of this disclosure. The description of the network device according to the first aspect of this disclosure is correspondingly valid for the network device of Fig. 1. In the Figures, the reference sign “MSB” indicates the most significant bit, and the reference sign “LSB” indicates the least significant bit.

[0108] The network device 1 of Fig. 1 is a network device for communication, wherein the network device is configured to generate a data structure 200 comprising a destination address 100. The destination address 100 comprises, starting from its most significant bit MSB, a network identifier 101, multiple network device identifiers 102 each identifying another network device, and a field 103 a directly preceding a last network device identifier 102c of the multiple network device identifiers 102. A checksum (e.g. layer 4 checksum) of the field 103a and all consecutive network device identifiers 104a of the multiple network device identifiers 102 preceding the field 103a equals zero. In the Figures, the reference sign “102a” indicates a network device identifier of the multiple network device identifiers 102 that is adjacent to the network identifier 101; the reference sign “102c” indicates the last network device identifier of the multiple network device identifiers 102, and the reference sign “102b” indicates any network device identifier of the multiple network device identifiers 102 that is not adjacent to the network identifier 101 and not the last network device identifier 102c. The number of network device identifiers 102 shown in Fig. 1 is only by way of example and, thus, may be different. That is, the destination address 100 may comprise two or more network device identifiers 102. In case of the destination address 100 comprising two network device identifiers 102, there is only one network device identifier 104a (being a network device identifier 102a adjacent to the network identifier 101) preceding the field 103a. The following description with regard to multiple consecutive network device identifiers 104a preceding the field 103a is correspondingly valid to the one network device identifier 104a preceding the field 103a in the case of the destination address comprising only two network device identifiers 102.

[0109] Since the checksum (e.g. layer 4 checksum) of the field 103 a and all consecutive network device identifiers 104a of the multiple network device identifiers 102 preceding the field 103 a equals zero, the consecutive network device identifiers 104a of the multiple network device identifiers 102 preceding the field 103a do not contribute to a checksum (e.g. layer 4 checksum) computation of the data structure 200. In other words, when the destination address 100 is used for computing a checksum, such as a layer 4 checksum, of the data structure 200, merely the network identifier 101 and the last network identifier 102c may contribute to the checksum. The other network device identifiers 104a of the destination address 100 do not contribute to the checksum of the destination address, because the checksum of these network device identifiers 104a of the destination address 100 and the field 103a equal to zero. That is, the contribution of these network device identifiers 104a to the checksum of the destination address 100 is nullified or prevented by the field 103a.

[0110] The network device identifier(s) 102a and optionally 102b except of the last network device identifier 102c of the multiple network device identifiers 102 of the destination address 100 may be router identifiers for identifying a respective router, which is to route or transmit the data structure 200 from the network device 1 to a destination network device (for which the data structure 200 is intended for). Thus, network device identifier(s) 102a and optionally 102b except of the last network device identifier 102c of the multiple network device identifiers 102 may comprise information (e.g. may define) a path from the network device 1 to the destination network device for which the data structure 200 is intended for.

[0111] Since the consecutive network device identifiers 104a that precede the field 103a do not have an impact on the checksum computation of the destination address 100, all these network device identifiers 104a may be deleted by router network devices via which the data structure 200 may be transmitted together with the field 103a so that the destination network device merely receives a data structure with a changed destination address comprising the network field 101 and the last network device identifier 102c of the destination address 100 generated by the network device 1. Namely, as long as no error has occurred during a transmission of the data structure 200 from the network device 1 via one or more routers to the destination network device (for which the data structure 200 generated by the network device 1 is intended), the checksum of the changed destination address received by the destination may equal to the checksum of the destination address 100 generated by the network device 1. As outlined before, the checksum of the changed destination address received by the destination may correspond to computing the checksum of the network identifier 101 and the last network device identifier 102c of the destination address 100 generated by the network device 1. The checksum of the destination address 100 generated by the network device 1 may correspond to computing the checksum of the network identifier 101, the multiple network device identifiers 102 and the field 103a. As outlined already above, due to the field 103a the network device identifiers 104a preceding the field 103a do not contribute to the checksum of the destination address 100. Thus, computing the checksum of the network identifier 101, the multiple network device identifiers 102 and the field 103 a of the destination address 100 yields the same result as computing the checksum of merely the network identifier 101 and the last network device identifier 102c of the destination address.

[0112] Thus, the network device 1 of Fig. 1 allows performing segment routing (e.g. compressed segment routing) without a segment router header (SRH) while allowing a destination network device to check whether an error has occurred during transmission of a received data structure via a path from a source. Namely, as outlined above the checksum of the whole destination address 100 as generated by the network device 1 and the checksum of the network identifier 101 and the last network device identifier 102c of the destination address 100 equal to each other. That is, assuming that no error has occurred during transmission of the data structure 200 from the network device 1 via one or more routers to the destination device, the checksum of the destination address 100 computed by the network device 1 will equal to the checksum of a changed destination address computed by the destination network device, wherein the changed destination address comprises, starting from the most significant bit MSB, the network identifier 101 and the last network device identifier 102c of the destination address 100.

[0113] Fig. 8a shows an example of the destination address 100 (that may be generated by the network device 1) and the changed destination address 600 that may be received by a destination network device after the data structure 200 is transmitted from the network device 1 via one or more routers to the destination network device.

[0114] The network device 1 may comprise a processor or processing circuitry (not shown) configured to perform, conduct or initiate the various operations of the network device 1 described herein. The processing circuitry may comprise hardware and / or the processing circuitry may be controlled by software. The hardware may comprise analog circuitry or digital circuitry, or both analog and digital circuitry. The digital circuitry may comprise components such as application-specific integrated circuits (ASICs), field-programmable arrays (FPGAs), digital signal processors (DSPs), or multi-purpose processors. The network device 1 may further comprise memory circuitry, which stores one or more instruction(s) that can be executed by the processor or by the processing circuitry, in particular under control of the software. For instance, the memory circuitry may comprise a non-transitory storage medium storing executable software code which, when executed by the processor or the processing circuitry, causes the various operations of the network device 1 to be performed. In one example, the processing circuitry comprises one or more processors and a non-transitory memory connected to the one or more processors. The non-transitory memory may carry executable program code which, when executed by the one or more processors, causes the network device 1 to perform, conduct or initiate the operations or methods described herein.

[0115] For further information on the network device of Fig. 1 reference is made to the description of the network device according to the first aspect of this disclosure.

[0116] Fig. 2 shows an example of the network device of Fig. 1. The description of the network device of Fig. 1 is correspondingly valid for the network device of Fig. 2.

[0117] As shown in Fig. 2, the network device 1 may be configured to transmit the data structure 200 comprising the destination address 100 to a network device 2 that is indicated by the network device identifier 102a of the multiple network device identifiers 102 that is adjacent to the network identifier 101 of the destination address 100. Thus, the address of the other network device 2 may equal to the network identifier 101 and the network device identifier 102a that is adjacent to the network identifier 101 of the destination address 100.

[0118] For further information on the other network device 2 reference is made to the description of the network device of Fig. 5. That is, the other network device 2 may be the network device of Fig. 5 Fig. 3 shows an example of the network device of Fig. 1. The description of the network device of Figs. 1 and 2 is correspondingly valid for the network device of Fig. 3.

[0119] As shown in Fig. 3, the destination address 100 of the data structure 200 may additionally comprise at least one further field 103b directly preceding a network device identifier 102b of the multiple network device identifiers 102 that is not adjacent to the network identifier 101 and not the last network device identifier 102c. The checksum of the further field 103b and all one or more consecutive network device identifiers 104bi of the multiple network device identifiers 102 preceding the further field 103b equals zero. The arrangement of the further field 103b directly preceding a network device identifier 102b of the multiple network device identifiers 102 that is not adjacent to the network identifier 101 and not the last network device identifier 102c, as shown in Fig. 3, is only by way of example and, thus, may be different. The description of Fig. 3 is correspondingly valid in case of a different arrangement of the further field 103b in the destination address. The number of the at least one further field 103b shown in Fig. 3 (i.e. one further field 103b) is only by way of example and may be different. The destination address 100 may comprise between one further field 103b and a number of further fields 103b that is smaller by two than the number of network device identifiers 102 of the destination address 100. The description of Fig. 3 is correspondingly valid in case of two or more further fields 103b in the destination address 100. Fig. 4 shows an example in which the number of further fields 103b of the destination address 100 equals a number that smaller by two than the number of network device identifiers 102 of the destination address 100.

[0120] As shown in Fig. 3, due to the presence of the further field 103b in the destination address 100, the consecutive network device identifiers 104a of the multiple network device identifiers 102 preceding the field 103a that directly precedes the last network device identifier 102c of the multiple network device identifiers 102c does not comprise the network device identifier 102a adjacent to the network identifier 101, compared to the consecutive network device identifiers 104a preceding the field 103a of the destination address 100 of Fig. 1. The reason for this is that the term “consecutive” means “following one after another without others coming in between”, i.e. “following each other continuously (without any interruption)”. That is, consecutive network device identifiers are network device identifiers that are adjacent to each other without anything else, such as a field, being arranged between any two of the aforementioned network device identifiers. In other words, consecutive network device identifiers are network device identifiers arranged next to each other or in succession such that any two of them are not separated by anything else, such as a field. In the example of Fig. 3, the network device identifier 102a adjacent to the network identifier 101 is not part of the consecutive network device identifiers 104a preceding the field 103a because the further field 103b is arranged between the network device identifier 102a adjacent to the network identifier 101 and the, from the perspective of the most significant bit MSB of the destination address 100, first network device identifier 102b of the consecutive network device identifiers 104a preceding the field 103a.

[0121] The example of the network device of Fig. 3 has the same advantages as described above with regard to the network device of Fig. 1, because when computing a checksum (e.g. layer 4 checksum) of the destination address 100 of Fig. 3, merely the network identifier 101 and the last network device identifier 102c contribute to the checksum. This is due to the fact, that the checksum (e.g. layer 4 checksum) of the further field 103b and the network device identifier 104bi preceding the further field 103b equals to zero; and the checksum of the field 103a and all consecutive network device identifiers 104a preceding the field 103a equals to zero.

[0122] Fig- 4 shows an example of the network device of Fig. 1. The description of the network device of Figs. 1, 2 and 3 is correspondingly valid for the network device of Fig. 4.

[0123] As shown in Fig. 4, the destination address 100 of the data structure 200 may additionally comprise a further field 103b directly preceding each network device identifier 102a of the multiple network device identifiers 102 that is not adjacent to the network identifier 101 and not the last network device identifier 103. The checksum of the further field 103b and a network device identifier 104bi or 104b2 of the multiple network device identifiers 102 directly preceding the further field 103b equals zero. That is, the checksum of each further field 103b and a respective network device identifier 104bi or 1042 of the multiple network device identifiers 102 directly preceding the further field 103b equals zero. The number of network device identifiers 102 of the destination address 100 shown in Fig. 4 is merely by way of example and may be different. The number of further fields 103b of the destination address 100 shown in Fig. 4 is merely by way of example and may be different. The description of Fig. 4 is correspondingly valid in case of a different number of network device identifiers 102 and / or a different number of further fields 103b. According to the example of Fig. 4 the number of further fields 103b equals a number that is smaller by two than the number of network device identifiers 102 of the destination address 100. Thus, since the destination address 100 of Fig. 4 exemplarily comprises four network device identifiers 102, the destination address 100 of Fig. 4 comprises two further fields 103b, which is smaller by two than the number of network device identifiers 102 of the destination address 100 (i.e. 4 network device identifiers 102 - 2 = 2 further fields 103b).

[0124] The optionally features of at least two of the network devices of Fig. 2, Fig. 3 and Fig. 4 may be combined with each other

[0125] Fig- 5 shows an example of a network device according to this disclosure. The network device 2 of Fig. 5 is an example of the network device according to the second aspect of this disclosure. The description of the network device according to the second aspect of this disclosure is correspondingly valid for the network device of Fig. 5.

[0126] The network device 2 of Fig. 5 is a network device for communication. The network device 2 is configured to receive a data structure 200 with a destination address 100. The description of the destination address 100 of Fig. 1 is valid for the destination address 100 of Fig. 5. The network device 2 is configured to determine whether the network identifier 101 and the network device identifier 102a adjacent to the network identifier 101 of the destination address 100 equal an address of the network device 2. According to the example of Fig. 5, the network identifier 101 may be referred to as “Net-ID”, the multiple network device identifiers 102 may be referred to as “ND-IDi, ND-ID2, ... , ND-IDn-i, and ND-IDn”, and the field 103a may be referred to as “Fid”. The number of network device identifiers 102 of the destination address 100 is only by way of example and may be different. That is, the destination address 100 may comprise two or more network device identifiers 102 (i.e. the index n may greater than or equal to two, n > 2). The description of Fig. 5 is correspondingly valid.

[0127] The network device 2 is configured to, in case the network identifier 101 and the network device identifier 102a adjacent to the network identifier 101 equal the address of the network device 2, generate a changed destination address 500 of the received data structure 200 by deleting the network device identifier 102a of the destination address 100 and shifting a rest of the destination address 100 adjacent to the network identifier 101 of the destination address 100 (as shown in Fig. 5 by the dashed errors), or deleting the network device identifier 102a and a field directly after the network device identifier 102a of the destination address 100 and shifting a rest of the destination address 100 adjacent to the network identifier 101 of the destination address 100 (not shown in Fig. 5).

[0128] The second alternative would be the case, when the network device identifier ND-IDn-i would be the network device identifier 102a adjacent to the network identifier 101. Namely, in this case the field 103 is to be deleted together with the network device identifier ND-IDn-i. The aforementioned field in the second alternative of deleting the network device identifier 102a that is adjacent to the network identifier 101 may be either the field 103a (that directly precedes the last network device identifier 102c) or a further field 103b (that directly precedes a network device identifier 102b that is not adjacent to the network identifier 101 and not the last network device identifier 102c, as exemplarily shown in Fig. 2 or 3).

[0129] In the example of Fig. 5, it is assumed that the network device identifier 102a adjacent to the network identifier 101 of the destination address 100 indicates the network device 2 (as indicated by “ND-IDi” in Fig. 5) and that there is only the field 103a directly preceding the last network device identifier 102c of the multiple network device identifiers 102. Thus, the network device 2 may determine that its address equals the network identifier 101 and the network device identifier 102a adjacent to the network identifier 101. Thus, the network device 2 may generate a changed destination address 500 of the received data structure 200 by deleting the network device identifier 102a of the destination address 100 and shifting the rest of the destination address 100 adjacent to the network identifier 101 of the destination address 100. Therefore, as shown in Fig. 5, the network identifier 501 of the changed destination address 500 is the network identifier “Net-ID” of the destination address 100, the network device identifier 502a adjacent to the network identifier 501 of the changed address 500 (i.e. the first network device identifier 502a from the perspective of the most significant bits MSB) is the network device identifier ND-ID2 (i.e. the second network device identifier 102b) of the destination address 100 and so on.

[0130] As shown in Fig. 5, the bits of the changed destination address 500 after the last network device identifier 502c of the changed destination address 500 (equaling to the last network device identifier 102c of the destination address 100) may be set to arbitrary values or to zeros. In case the bits are set to arbitrary values, a network protocol for communication may define that a destination network device computes a checksum (e.g. layer 4 checksum) of a received destination address by computing the checksum of only the network identifier and the network device identifier adjacent to the network identifier. Alternatively or additionally, the aforementioned may be defined by information that may be stored and / or received by the destination network device. The number of bits that may be set to arbitrary values or to zeros may be the number of bits of the network device identifier 102a adjacent to the network identifier 101 of the destination address 100 that is removed.

[0131] Further a scenario (not shown in Fig. 5) is assumed, in which the destination address 100 merely comprises, starting from the most significant bit MSB, the network identifier Net-ID, the network device identifier ND-IDn-i as the network device identifier 102a adjacent to the network identifier Net-ID, the network device identifier ND-IDnas the last network device identifier 102c, and the field 103a preceding the last network device identifier 102c and arranged directly after the network device identifier 102a. This scenario may be the case when the data structure 200 has been transmitted already via network devices (i.e. routers) that are indicated by the network device identifiers ND-IDi, ND-ID2, ..., ND-IDn-2 and the network device 2 is indicated by the network device identifier ND-IDn-i (not shown in Fig. 5). In the aforementioned scenario the network device 2 may determine that its address equals the network identifier 101 (i.e. Net-ID) and the network device identifier 102a (i.e. ND-IDn-i) adjacent to the network identifier 101. Thus, the network device 2 may generate a changed destination address of the received data structure 200 by deleting the network device identifier 102a (i.e. ND-IDn-i) and the field 103a (i.e. Fid) directly after the network device identifier 102a of the destination address 100 and shifting the rest of the destination address 100 adjacent to the network identifier 101 of the destination address 100. The bits of the changed destination address after the last network device identifier of the changed destination address may be set to arbitrary values or to zeros.

[0132] The network device 2 may configured to be triggered by information of the network device identifier 102a adjacent to the network identifier 101 of the destination address 100 to delete the network device identifier 102a adjacent to the network identifier 101 of the destination address 100 and shift the rest of the destination address 100 adjacent to the network identifier 101 of the destination address 100, or delete the network device identifier 102a adjacent to the network identifier 101 and the field directly after the network device identifier 102a of the destination address and shift the rest of the destination address 100 adjacent to the network identifier 101 of the destination address 100. Thus, in the example of Fig. 5, information of the network device identifier 102a adjacent to the network identifier 101 of the destination address 100 may cause or trigger the network device 2 to delete the network device identifier 102a adjacent to the network identifier 101 of the destination address 100 and shift the rest of the destination address 100 adjacent to the network identifier 101 of the destination address 100 (to generate the changed destination address 500 as shown in Fig. 5). Alternatively or additionally, the aforementioned may be defined by information that may be stored and / or received by the destination network device 2.

[0133] In the above described assumed scenario (not shown in Fig. 5), the information of the network device identifier 102a adjacent to the network identifier 101 of the destination address 100 may cause or trigger the network device 2 to delete the network device identifier 102a adjacent to the network identifier 101 (being ND-IDn-i) and the field 103a (being Fid) directly after the network device identifier 102a of the destination address and shift the rest of the destination address 100 adj cent to the network identifier 101 of the destination address 100. Alternatively or additionally, the aforementioned may be defined by information that may be stored and / or received by the destination network device 2.

[0134] The network device 2 may comprise a processor or processing circuitry (not shown) configured to perform, conduct or initiate the various operations of the network device 2 described herein. The processing circuitry may comprise hardware and / or the processing circuitry may be controlled by software. The hardware may comprise analog circuitry or digital circuitry, or both analog and digital circuitry. The digital circuitry may comprise components such as application-specific integrated circuits (ASICs), field-programmable arrays (FPGAs), digital signal processors (DSPs), or multi-purpose processors. The network device 2 may further comprise memory circuitry, which stores one or more instruction(s) that can be executed by the processor or by the processing circuitry, in particular under control of the software. For instance, the memory circuitry may comprise a non-transitory storage medium storing executable software code which, when executed by the processor or the processing circuitry, causes the various operations of the network device 2 to be performed. In one example, the processing circuitry comprises one or more processors and a non-transitory memory connected to the one or more processors. The non-transitory memory may carry executable program code which, when executed by the one or more processors, causes the network device 2 to perform, conduct or initiate the operations or methods described herein. For further information on the network device of Fig. 5 reference is made to the description of the network device according to the second aspect of this disclosure.

[0135] Fig. 6 shows an example of the network device of Fig. 5. The description of the network device of Fig. 5 is correspondingly valid for the network device of Fig. 6.

[0136] As shown in Fig. 6, the network device 2 may be configured to transmit the data structure 200 with the changed destination address 500 to a network device 3 identified by the network device identifier 502a adjacent to the network identifier 501 of the change destination address 500. Thus, the address of the network device 3 may equal to the network identifier 501 and the network device identifier 502a that is adjacent to the network identifier 501 of the changed destination address 500, as indicated in Fig. 6. The network device 3 may be implemented in line with the network device 2 of Fig. 5. Thus, the description of the network device 2 of Fig. 5 may be valid for the network device 3 of Fig. 6.

[0137] Fig. 7a shows an example of a data structure. Figure7b shows an example of a data structure according to this disclosure.

[0138] As shown in Fig. 7b, the data structure 200 comprises a layer 2 header 301, a layer 3 header 302 that may be an IPv6 header in case the communication protocol for communicating the data structure 200 is IPv6, a layer 4 header 304 and a layer 4 payload 305. In Fig. 7b, the layer 2 is indicated by the references sign “L2”, the layer 3 is indicated by the reference sign “L3”, and the layer 4 is indicated by the reference sign “L4”. As indicated in Fig. 7b, the layer 3 header 302 may comprise the destination address 100 (or changed destination address 500) of the data structure 200, and the layer 4 header 304 may comprise a checksum 400 (may be referred to as layer 4 checksum). The checksum 400 may be computed using the destination address 100 of the data structure 200. The checksum 400 is the checksum of the data structure 200 that is computed by the source network device that transmits the data structure 200 to a destination network device via one or more routers. The one or more routers represent the path between the source and the destination. The destination address 100 of the data structure 200 defines the one or more routers and the destination network device, as described above.

[0139] Thus, the example of the data structure 200 according to this disclosure of Fig. 7b differs from the data structure 200 of Fig. 7a, in that the data structure 200 of Fig. 7b does no comprise a segment routing header 303 (SRH). Fig. 8a shows an example of a destination address of a data structure according to this disclosure. Fig. 8b shows an example of a destination address of a data structure according to this disclosure. The destination address 100 of Fig. 8a is a destination address of a data structure that is initially transmitted by a source network device, such as the network device of any one of Figs. 1 to 4, in order to be transmitted via multiple network device routers (indicated by the network device identifiers ND-IDi, ND-ID2, ... , ND-IDn-i) to a destination network device (indicated by the network device identifier ND-IDn). The source network device may be a network device according to any one of Figs. 1 to 4. The multiple router network devices may each be a network device according to Fig. 5 or 6. The description of the destination address 100 of Fig. 1 and the description of the destination address 100 of Fig. 5 is correspondingly valid for the destination address 100 of Fig. 8a. The destination address 100 of Fig. 8a may be received by a router network device, such as the network device 2 of Fig. 5 or 6, that is indicated by the network device indicator 102a that is adjacent to the network identifier 101 of the destination address 100. The destination address 600 of Fig. 8b is a changed destination address that originates from the (initial) destination address 100 of Fig. 8a. The destination address 600 of Fig. 8b shows the changed destination address of the data structure (initially transmitted from the source network device) that is transmitted from the last network device router of the path (indicated by the network device identifier ND-IDn-i of the destination address 100) to the destination network device (assuming that no error has occurred during the transmission from the source via the path). That is, Fig. 8b shows the changed destination address (originating from the destination address of Fig. 8a) of the data structure as received by the destination network device (assuming that no error has occurred during the transmission from the source via the path to the destination).

[0140] As may be derived from Figs. 8a and 8b, a computation of the checksum (e.g. layer 4 checksum) of the destination address 100 of Fig. 8a and a computation of the checksum (e.g. layer 4 checksum) of the changed destination address 600 of Fig. 8b will have the same computation result. Namely, the checksum of the field 103 a and all consecutive network device identifiers 104a of the multiple network device identifiers 102 preceding the field 103 a equals zero. Thus, the aforementioned consecutive network device identifiers 104a preceding the field 103a as well as the field 103a itself do not contribute to a computation of the checksum of the destination address 100. That is, when computing the checksum of the destination address 100 of Fig. 8a merely the network identifier 101 and the last network device identifier 102c contribute to the checksum computation. When the destination network device computes the checksum of the destination address 600 of Fig. 8b, merely the network device identifier 601 (being the network identifier 101 of the destination address 100 of Fig. 8a) and the network device identifier 602a (being the last network device identifier 102c of the destination address 100 of Fig. 8a) contribute to the checksum computation. Namely, the bits after the network device identifier 602a are set to zero or arbitrary values that are not to contribute to the checksum computation. Bits that are zeros do not contribute to the checksum. In case the bits are set to arbitrary values, a network protocol for communication may define that the destination network device computes a checksum (e.g. layer 4 checksum) of the received destination address 600 by computing the checksum of only the network identifier 601 and the network device identifier 602a adjacent to the network identifier 601. Alternatively or additionally, the aforementioned may be defined by information that may be stored and / or received by the destination network device.

[0141] Thus, as may be derived from the example of Figs. 8a and 8b, the present disclosure allows a destination network device to check whether an error has occurred in a transmission of a data structure from a source network device via one or more router network devices to the destination network device by computing a checksum (e.g. layer 4 checksum) of the data structure using the destination address 600 of the received data structure. In case the computed checksum equals to the checksum computed by the source network device using the (initial) destination address 100 no error has occurred. Otherwise, the destination network device may know that an error has occurred.

[0142] Fig- 9 shows an example of a method according to this disclosure. The method of Fig. 9 is an example of the method according to the third aspect of this disclosure. The description of the method according to the third aspect of this disclosure is correspondingly valid for the method ofFig. 9.

[0143] The method ofFig. 9 is a method for communication. As shown in Fig. 9, the method comprises, in a step SI, generating a data structure comprising a destination address, wherein the destination address comprises, starting from its most significant bit, a network identifier, multiple network device identifiers each identifying another network device, and a field directly preceding a last network device identifier of the multiple network device identifiers. The checksum (e.g. layer 4 checksum) of the field and all one or more consecutive network device identifiers of the multiple network device identifiers preceding the field equals zero. The network device 1 of any one of Figs. 1 to 4 may be configured to perform the method of Fig. 9. The network device 2 of Fig. 5 or 6 may be configured to perform the method of Fig.

[0144] 9.

[0145] For further information on the method of Fig. 9 reference is made to the description of the method according to the third aspect of this disclosure.

[0146] Fig. 10 shows an example of a method according to this disclosure. The method of Fig. 10 is an example of the method according to the fourth aspect of this disclosure. The description of the method according to the fourth aspect of this disclosure is correspondingly valid for the method of Fig. 10.

[0147] The method of Fig. 10 is a method for communication. As shown in Fig. 10, the method comprises, in a step S10, receiving a data structure with a destination address. The method comprises, in a step S20 following the step S10, determining whether a network identifier and a network device identifier adjacent to the network identifier of the destination address equal an address of the network device. The method comprises, in a step S30 following the step S20, in case the network identifier and the network device identifier equal an address of the network device generating a changed destination address of the received data structure by deleting the network device identifier of the destination address and shifting a rest of the destination address adjacent to the network identifier of the destination address, or deleting the network device identifier and a field directly after the network device identifier of the destination address and shifting a rest of the destination address adjacent to the network identifier of the destination address.

[0148] The network device 2 of Fig. 5 or 6 may be configured to perform the method of Fig. 10.

[0149] The network device 1 of any one of Figs. 1 to 4 may be configured to perform the method of Fig. 10.

[0150] For further information on the method of Fig. 10 reference is made to the description of the method according to the fourth aspect of this disclosure.

[0151] The present disclosure has been described in conjunction with various embodiments as examples as well as implementations. However, other variations can be understood and effected by those persons skilled in the art and practicing the claimed matter, from the studies of the drawings, this disclosure and the independent claims. In the claims as well as in the description the word “comprising” does not exclude other elements or steps and the indefinite article “a” or “an” does not exclude a plurality. A single element or other unit may fulfill the functions of several entities or items recited in the claims. The mere fact that certain measures are recited in the mutual different dependent claims does not indicate that a combination of these measures cannot be used in an advantageous implementation.

Claims

CLAIMS1. A network device (1) for communication, wherein the network device (1) is configured to generate a data structure comprising a destination address (100), wherein the destination address (100) comprises, starting from its most significant bit, a network identifier (101), multiple network device identifiers (102) each identifying another network device, and a field (103a) directly preceding a last network device identifier (102c) of the multiple network device identifiers (102); and wherein a checksum of the field (103 a) and all one or more consecutive network device identifiers (104a) of the multiple network device identifiers (102) preceding the field (103a) equals zero.

2. The network device (1) according to claim 1, wherein the network device (1) is configured to transmit the data structure (200) to a network device (2) that is indicated by a network device identifier (102a) adjacent to the network identifier (101) of the destination address (100).

3. The network device (1) according to claim 1 or 2, wherein the destination address (100) of the data structure additionally comprises at least one further field (103b) directly preceding a network device identifier (102b) of the multiple network device identifiers (102) that is not adjacent to the network identifier (101) and not the last network device identifier (102c); and the further field (103b) is generated such that the checksum of the further field (103b) and all one or more consecutive network device identifiers (104bi) of the multiple network device identifiers (102) preceding the further field (103b) equals zero.

4. The network device (1) according to claim 1 or 2, whereinthe destination address (100) of the data structure additionally comprises a further field (103b) directly preceding each network device identifier (102b) of the multiple network device identifiers (102) that is not adjacent to the network identifier (101) and not the last network device identifier (102c); and the further field (103b) is generated such that the checksum of the further field (103b) and a network device identifier (104bi, 104b2) of the multiple network device identifiers (102) directly preceding the further field (103b) equals zero.

5. The network device (1) according to claim 3 or 4, wherein the further field (103b) comprises 16 bits.

6. The network device (1) according to any one of the previous claims, wherein the data structure (200) does not comprise a segment routing header (303).

7. The network device (1) according to any one of the previous claims, wherein a layer 3 header (302) of the data structure (200) comprises the destination address (100, 500).

8. The network device (1) according to any one of the previous claims, wherein the network device (1) is configured to compute the checksum (400) of a part of the destination address (100, 500) that is adjacent to the network identifier (101, 501) of the destination address (100, 500), and wherein a layer 4 header (304) of the data structure (200) comprises the computed checksum (400).

9. A network device (2) for communication, wherein the network device (2) is configured to receive a data structure (200) with a destination address (100), determine whether a network identifier (101) and a network device identifier (102a) adjacent to the network identifier (101) of the destination address (100) equal an address of the network device (2);in case the network identifier (101) and the network device identifier (102a) equal the address of the network device (2) generate a changed destination address (500) of the received data structure (200) by deleting the network device identifier (102a) of the destination address (100) and shifting a rest of the destination address (100) adjacent to the network identifier (101) of the destination address (100), or deleting the network device identifier (102a) and a field directly after the network device identifier (102a) of the destination address (100) and shifting a rest of the destination address (100) adjacent to the network identifier (101) of the destination address (100).

10. The network device (2) according to claim 9, wherein the network device (2) is configured to transmit the data structure (200) with the changed destination address (500) to a network device (3) identified by a network device identifier (502a) adjacent to the network identifier (501) of the change destination address (500).

11. The network device (2) according to claim 9 or 10, wherein the network device (2) is configured to, in case the network identifier (101) and the network device identifier (102a) adjacent to the network identifier (101) of the destination address (100) does not equal the address of the network device (2), determine, using the destination address (100), a network device, to which the data structure (200) is to be transmitted; and transmit the received data structure (200) with the destination address (100) to the determined network device.

12. The network device (2) according to any one of claims 9 to 11, wherein the network device (2) is configured to be triggered by information of the network device identifier (102a) adjacent to the network identifier (101) of the destination address (100) to delete the network device identifier (102a) of the destination address (100) and shift the rest of the destination address (100) adjacent to the network identifier (101) of the destination address (100), ordelete the network device identifier (102a) and the field directly after the network device identifier (102a) of the destination address and shift the rest of the destination address (100) adjacent to the network identifier(lOl) of the destination address (100).

13. The network device (1, 2) according to any one of the previous claims, wherein the field (103a) comprises 16 bits.

14. A method for communication, wherein the method comprises generating (SI) a data structure comprising a destination address, wherein the destination address comprises, starting from its most significant bit, a network identifier, multiple network device identifiers each identifying another network device, and a field directly preceding a last network device identifier of the multiple network device identifiers; and wherein a checksum of the field and all one or more consecutive network device identifiers of the multiple network device identifiers preceding the field equals zero15. A method for communication, wherein the method comprises receiving (S10) a data structure with a destination address, determining (S20) whether a network identifier and a network device identifier adjacent to the network identifier of the destination address equal an address of the network device; in case the network identifier and the network device identifier equal the address of the network device generating (S30) a changed destination address of the received data structure by deleting the network device identifier of the destination address and shifting a rest of the destination address adjacent to the network identifier of the destination address, ordeleting the network device identifier and a field directly after the network device identifier of the destination address and shifting a rest of the destination address adjacent to the network identifier of the destination address.

Citation Information

Patent Citations

  • Minimizing differences in segment identifiers for segment routing

    WO2021211209A1