System and method for forwarding messages in a layered network architecture using variable length addresses

By introducing variable length addressing into the network layer protocol header, traditional IP addressing is solved, and the problem of address exhaustion and inefficiency in the Internet of Things is achieved, saving resources and power and reducing processing time is achieved.

CN115428415BActive Publication Date: 2024-11-15HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080099884.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-04-16
Publication Date
2024-11-15
Estimated Expiration
2040-04-16

AI Technical Summary

Technical Problem

The traditional IP addressing mechanism has problems such as address exhaustion and low packet carrying efficiency in the Internet of Things environment, resulting in waste of resources and power and increased processing time.

Method used

A variable-length addressable network layer protocol header is introduced. By modifying the source address and destination address length, data packets are routed in the network, adapting to different subnet structures, reducing address overhead and improving processing efficiency.

Benefits of technology

It expands the address space, reduces resource and power consumption, improves the transmission efficiency of data packets in the network, and reduces processing time.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115428415B_ABST
    Figure CN115428415B_ABST
Patent Text Reader

Abstract

The present invention relates to transmitting a data message from a source to a destination within a communication network. A data message is received from the source located in a local subnet of the network, wherein the data message comprises a network layer protocol header having a source address comprising a local subnet address of the source, a destination address of the destination, a first field indicating the length of the source address, and a second field indicating the length of the destination address; the local subnet address of the source is converted by modifying the source address and the first field indicating the length of the source address, so that the modification comprises appending a prefix of the subnet to the local subnet address so that the source address becomes an address of a higher-level network; and the data message is then forwarded to the destination in the higher-level network.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention generally relates to routing data messages in a network via variable length addressing. Background Art

[0002] Internet Protocol (IP) addresses are used to identify devices and provide the location of devices in IP networks. For example, an IP header includes a source address that identifies a source device and a destination address that identifies a destination device in an IP network. The IP network can determine a path for an IP message to be transmitted from a source device to a destination device based on the source IP address and the destination IP address. With the continuous development of the Internet, traditional IP addressing (e.g., IPv4 and IPv6) faces more and more problems, such as address exhaustion and low message carrying efficiency in the Internet of Things (IoT). For example, in IoT, machine-to-machine communication or object-to-object communication via wireless connections dominates. This type of communication is often chatty, and the frequent exchange of short messages is energy-sensitive and requires low latency. This type of communication is not conducive to traditional IP addressing mechanisms because traditional IP addressing mechanisms use fixed addressing lengths, which can cause huge overhead, waste useful resources and electricity, and increase processing time. Summary of the invention

[0003] According to one aspect of the present invention, a method for transmitting a data message from a source to a destination within a communication network is provided. The method comprises: receiving a data message from the source located in a local subnet of the network, wherein the data message comprises a first network layer protocol header, the first network layer protocol header having a source address including a local subnet address of the source, a destination address of the destination, a first field indicating the length of the source address, and a second field indicating the length of the destination address; converting the first network layer protocol header by modifying the source address and the first field indicating the length of the source address, wherein the modification comprises appending a prefix of the subnet to the local subnet address so that the source address becomes an address of a higher-level network; and forwarding the data message including the converted local subnet address to the destination in the higher-level network.

[0004] Optionally, in any of the above aspects, the method also includes: receiving a second data packet having a second local subnet address of a second source and a second destination address in a second network layer protocol header; converting the second network layer protocol header by modifying the second destination address and a third field representing the length of the second destination address, wherein the modification includes removing the prefix of the high-level network from the second destination address; and forwarding the second data packet including the converted destination address to the second destination address.

[0005] Optionally, in any of the above aspects, the first data packet and the second data packet are the same data packet.

[0006] Optionally, in any of the above aspects, the method also includes: when the length of the source address represented by the first field is less than the length of the destination address represented by the second field, determining that the destination is outside the local subnet of the source, wherein the conversion and forwarding are in response to the determination.

[0007] Optionally, in any of the above aspects, the modification further includes modifying at least one of the first field representing the length of the source address and the second field representing the length of the destination address.

[0008] Optionally, in any of the above aspects, the communication network includes multiple sources and destinations arranged in a nested hierarchical subnet structure.

[0009] Optionally, in any of the above aspects, the source address is a local subnet address used to forward the data packet to the destination address.

[0010] Optionally, in any of the above aspects, the first field representing the length of the source address and the second field representing the length of the destination address are both of fixed length.

[0011] According to another aspect of the present invention, a router for transmitting a data message from a source to a destination within a communication network is provided. The router comprises: a non-transient memory comprising instructions; one or more processors communicating with the memory and the one or more sensors, wherein the one or more processors execute the instructions to perform the following steps: receiving a data message from the source located in a local subnet of the network, wherein the data message comprises a first network layer protocol header, the first network layer protocol header having a source address including a local subnet address of the source, a destination address of the destination, a first field indicating the length of the source address, and a second field indicating the length of the destination address; converting the network layer protocol header by modifying the source address and the first field indicating the length of the source address, wherein the modification comprises appending a prefix of the subnet to the local subnet address so that the source address becomes an address of a higher-level network; forwarding the data message including the converted local subnet address to the destination of the higher-level network.

[0012] According to another aspect of the present invention, a non-transitory computer-readable medium storing computer instructions is provided. The computer instructions are used to transmit a data message from a source to a destination within a communication network, and when the computer instructions are executed by one or more processors, the one or more processors perform the following steps: receiving a data message from the source located in a local subnet of the network, wherein the data message includes a first network layer protocol header, the first network layer protocol header having a source address including a local subnet address of the source, a destination address of the destination, a first field indicating the length of the source address, and a second field indicating the length of the destination address; converting the first network layer protocol header by modifying the source address and the first field indicating the length of the source address, wherein the modification includes appending a prefix of the subnet to the local subnet address so that the source address becomes an address of a higher-level network; and forwarding the data message including the converted local subnet address to the destination in the higher-level network.

[0013] According to another aspect of the present invention, a network layer protocol header is provided. The network layer protocol header includes: a first field including a source address length (SAL); a second field including a destination address length (DAL); a third field including a variable length source address field, wherein the variable length is limited by the SAL; and a fourth field including a variable length destination address field, wherein the variable length is limited by the DAL.

[0014] According to another aspect of the present invention, a method for transmitting a data message from a source to a destination in a communication network is provided. The method comprises: receiving a data message from the source located in a local subnet of the network, wherein the data message comprises a network layer protocol header, the network layer protocol header having a source address including a local subnet address of the source, a destination address of the destination, a length of the source address, and a length of the destination address; converting the destination address to an address in a next-layer subnet by modifying the destination address and the length of the destination address, wherein the modification comprises removing a prefix of a lower-layer parent subnet attached to the local subnet address from the destination address; and forwarding the data message including the converted local subnet address to the destination.

[0015] The purpose of this summary is to introduce a selection of concepts that are further described in the following detailed description in a simplified form. The purpose of this summary is not to identify the key features or essential features of the subject matter for which protection is sought, nor is it to help determine the scope of the subject matter for which protection is sought. The subject matter for which protection is sought is not limited to implementations that solve any or all of the shortcomings noted in the background technology. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The various aspects of the present invention are illustrated by way of example and not limitation in the accompanying figures in which like references indicate elements.

[0017] Figure 1 An exemplary system in which the embodiments of the present invention can be implemented is shown.

[0018] Figure 2 Shown is the Figure 1 Internet Protocol (IP) messages that carry routing information in a network.

[0019] Figure 3 The conventional IPv6 header format is shown.

[0020] Figure 4 An exemplary network layer protocol header format provided by an embodiment of the present invention is shown.

[0021] Figure 5 An exemplary hierarchical network and a corresponding address scheme provided by the embodiments disclosed herein are shown.

[0022] Figure 6 Shows Figure 4 An example of an IPvn header is provided in the embodiment.

[0023] 7A to 7C It is a flow chart of transmitting data packets in a network provided by the embodiment disclosed in this article.

[0024] Fig. 8A and Figure 8B Shown is the Figure 5 An exemplary forwarding table for routing data packets in a network.

[0025] Fig.9A An example of routing data packets between entities in the same subnet is shown.

[0026] Fig. 9B An example of routing data packets between entities in different subnets is shown.

[0027] Fig.10 An embodiment of a node provided by an embodiment of the present invention is shown.

[0028] Fig.11 An exemplary embodiment of a computing system for implementing an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0029] The present invention is described below with reference to the accompanying drawings, which generally relate to techniques for establishing trust relationships in a distributed system.

[0030] The present invention generally relates to routing data messages in a network via variable length addressing.

[0031] Traditional address schemes such as IPv4 and IPv6 use fixed-length addresses, which limit the number of addressable devices, consume a lot of overhead, increase processing time, and waste resources and electricity. The present invention introduces a header (e.g., a network layer protocol header, such as a layer 3 protocol header) that supports variable-length addressing as the next generation Internet protocol, which expands the address length, increases processing time, but does not waste resources and electricity. The entities in the network are set in hierarchical subnets. Among other fields, the header also includes a source address length and a destination address length, wherein the source address length determines the length of the source address and the destination address length determines the length of the destination address. When a data message passes through a path from one entity in different subnets to another entity in the network, the router converts the header to modify the source address and the source address length or the destination address and the destination address length. If the communicating entities are located in the same subnet, the local source address of each entity can be used without any conversion.

[0032] It should be understood that the current embodiment of the present invention can be realized in many different forms, and the scope of the claims should not be understood to be limited to the embodiments set forth herein. On the contrary, these embodiments are provided to make the present invention thorough and complete, and to fully convey the inventive embodiment concepts to those skilled in the art. In fact, the present invention is intended to cover substitutes, modifications and equivalents of these embodiments included in the spirit and scope of the present invention as defined by the appended claims. In addition, in the following detailed description of the current embodiment of the present invention, many specific details are set forth in order to provide a thorough understanding. However, it is clear to those of ordinary skill in the art that the current embodiment of the present invention can be implemented without providing these specific details.

[0033] Figure 1 1 shows an exemplary system that can be implemented in embodiments of the present invention. System 100 includes a computing device 110 and a network node 120 connected via a network 130. In one embodiment, system 100 is a distributed system, wherein computing device 110 and / or network node 120 includes a trusted execution environment (TEE), as described below. Figure 1Specific components in system 100 are shown, but system 100 is not limited to these components and may also include more and / or different components. For example, in some examples, system 100 may include a network storage device, a maintenance manager, and / or other suitable components (not shown). Figure 1 The computing device 110 shown can be located in various locations such as local, cloud, etc. For example, the computing device 110 can be located at a client, a server, etc.

[0034] The network 130 may be a wired or wireless network, and may include a public network or a private network, including but not limited to a local area network (LAN), a wide area network (WAN), a satellite network, a cable network, a WiMax network, and communication networks such as LTE and 5G networks. Figure 1 As shown, the network 130 may include one or more network nodes 120 that interconnect multiple computing devices 110 and connect the computing devices 110 to an external network 140, such as the Internet or an intranet. For example, the network node 120 may include any number of different devices that facilitate network communication, such as servers, switches, routers, hubs, gateways, access points, firewalls, base stations, repeaters, backbone devices, network controllers, or other network elements. In some examples, the computing devices 110 may be organized into racks, activity areas, groups, sets, or other suitable partitions. For example, in the example shown, the computing devices 110 are divided into three host sets, identified as the first, second, and third host sets 110, respectively. In the example shown, each host set 110 is coupled to a corresponding network node by operation, and these network nodes are generally referred to as "racks" or "TOR" network nodes. Then, the TOR network node 120 can be coupled to other network nodes 120 by operation to form a computer network of a hierarchical, flat, mesh, or other suitable type of topology that implements communication between the computing device 110 and the external network 140. In other examples, multiple sets of hosts 110 may share a single network node 120 .

[0035] The computing devices 110 may be any type of general or special computing devices. For example, these computing devices may be user devices, such as desktop computers, laptop computers, tablet computers, display devices, cameras, printers, Internet of Things (IoT) devices, wearable computing devices, mobile devices, or smart phones. However, in a data center environment, these computing devices may be server devices, such as application server computers, virtual computing host computers, or file server computers. Moreover, the computing devices 110 may be used alone to provide computing, storage, and / or other suitable computing services.

[0036] Figure 2 Shown is the Figure 1 In one embodiment, IP message 201 may include, but is not limited to, IP header 202, transmission control protocol (TCP) user datagram protocol (UDP) header (TCP (UDP) header) and data (payload). IP header 202 is a prefix of IP message 201, including information about IP version, message length, source address and destination address, etc., as shown below. Figure 3 As described. In the IP header of IPv6, the length of address 203 is 128 bits, including 8 16-bit fields, each of which is delimited by a colon. Each field includes a hexadecimal number, while the IPv4 address uses dotted decimal notation. Address 203 includes prefix 203a, subnet ID 203b and interface ID 203c, where X represents a hexadecimal number. For example, address 203 can be expressed as 2001:0db8:3c4d:0015:0000:0000:1a2f:1a2b.

[0037] In the above example, the three leftmost fields (48 bits) include prefix 203a. The prefix describes the public topology assigned to the site, typically by an Internet Service Provider (ISP) or a Regional Internet Registry (RIR). The next field is a 16-bit subnet ID 203b, which is assigned to the address. The subnet ID describes the private topology, also known as the site topology. The four rightmost fields (64 bits) include interface ID 203c, also known as a token. Interface ID 203c can be automatically configured based on the MAC address of the interface or manually configured in EUI-64 format. Therefore, in the above example, address 203 shows all 128 bits of the IPv6 address, where the first 48 bits 2001:0db8:3c4d include the site prefix, indicating the public topology. The next 16 bits 0015 include the subnet ID, indicating the private topology of the site. The rightmost low-order 64 bits 0000:0000:1a2f:1a2b include the interface ID.

[0038] Figure 3The traditional IPv6 header format is shown. As shown, the first field of header 310 is the version number that defines the Internet Protocol version, which includes 4 bits. The next field of header 310 is the traffic class, which includes 8 bits and is used for traffic management. After the traffic class is a flow label field with a length of 20 bits, the source uses the flow label field to mark the message sequence processed as a single message. The next field of header 310 is the payload length, which is a 16-bit segment. After the payload length is the next header field with a length of 8 bits, followed by the hop limit field including 8 bits. The next header field identifies the type of header that follows the header, and the hop count is reduced by 1 until it reaches 0. Therefore, the portion of header 310 dominated by the address field includes 160 bits of information.

[0039] After the initial portion of the header 310, the IPv6 header format includes a source address (SA) of 128 bits in length. Similarly, the destination address (DA) is also a 128-bit address. The length of the source address and the destination address are fixed. Compared to the IPv4 format, where both the source address and the destination address are 32 bits, the IPv6 header format extends both the source address and the destination address to 128 bits. As can be seen from the figure, the entire header 310 in the IPv6 format is 40 octets in length and is located before the information payload transmitted over the Internet.

[0040] It should be understood that fixed address lengths (both in IPv4 and IPv6) define an overall address space in which each entity or device is assigned a flat address as its global identifier, which is used to communicate with other entities and devices. To prevent address exhaustion (i.e., address exhaustion), one technique is to migrate to a larger address space and reallocate longer addresses to entities and devices. Of course, the introduction of such a process can result in service interruptions and delays due to the necessary application, protocol stack, and global network updates.

[0041] Figure 4An exemplary network layer protocol header format provided by an embodiment of the present invention is shown. A network protocol layer header (e.g., hereinafter referred to as the "header" or "IP header" or "IPvn header" of the next generation IP protocol) is introduced to solve problems associated with fixed addressing schemes (e.g., those described above in conjunction with IPv6), such as address exhaustion. In one embodiment, the IPvn header has a variable length address (extended or shortened address), wherein the base address can remain unchanged while expanding the address space itself. The IPvn header 412 is similar to the IPv6 header 310, but with the following major exceptions: the IPvn header 412 includes other fields of source address length (source address length, SAL) and destination address length (destinationaddresslength, DAL), and the length of the source address (source address, SA) and the destination address (destinationaddress, DA) is variable. These two other fields represent an updated header that supports variable length addresses so that entities (devices) can communicate using the shortest address length, as described in detail below.

[0042] Figure 5 An exemplary hierarchical network and corresponding address scheme provided by the embodiments disclosed herein are shown. Hierarchical network 501 is a hierarchical tree structure of an organizational network based on each domain, including devices such as routers and computing devices. Each domain can have 0 or more associated devices. A network may include one or more domains, which can be used to define the structure of an entity or a group of entities. Multiple domains can divide large and geographically distant parts of an entity into smaller and more manageable parts, and control management access to each part. For example, a small entity may include a single domain for its entire network. On the other hand, a large international entity may have dozens of domains to represent each of its regional networks around the world. In this case, the domains can be set in a hierarchical tree structure similar to the entity structure.

[0043] The term "entity" as defined herein may be any network addressable device. In one embodiment, an entity uses a global address (or globally unique ID) to communicate with other entities in a network. Such a global address can be recognized by each other entity in the network. This allows entities to communicate with each other across different networks or subnets. However, entities in the same network or subnet do not need to use a full address to communicate with each other because they share the same subnet prefix. Instead, entities can use local addresses (e.g., global address suffixes) to communicate with each other in the same network or subnet. As described below, an entity can use its local address as a source address, which can be converted in a way that a destination entity can be located in a different subnet.

[0044] In one embodiment, entities are grouped into subnets based on criteria such as geographic location, ownership, and logical relationships. If each subnet is grouped into a higher-level subnet in a similar manner, a hierarchical network is formed in which the shortest possible addresses can be used for communication. For example, if the subnet includes fewer than 256 entities, an 8-bit local address is sufficient to distinguish each entity. When entities need to communicate with each other, their local addresses can be used. In this case, since each entity shares the same prefix, the prefix can be appended (added) to the local address to provide a unique addressable entity in a higher-level subnet.

[0045] In operation, an entity uses an address in the lowest level subnet to which it belongs. When an entity (e.g., a source entity) communicates with another entity (e.g., a destination entity) in the same subnet, the local addresses of the source entity and the destination entity associated with the same subnet may be used. In this case, datagrams may be forwarded from the source entity to the destination entity via an intra-subnet router (ISR). As the name implies, an ISR handles intra-subnet forwarding. In one embodiment, the addresses of entities in a subnet are statically configured. In another embodiment, the addresses of entities in a subnet are dynamically configured (e.g., DHCP). A detailed explanation is provided below in conjunction with the various figures.

[0046] In another embodiment, when the source entity communicates with a destination entity outside the current subnet (i.e., the source entity and the destination entity are located in different subnets), the source entity obtains the "global" address (destination address) of the destination entity, which is the complete address of the destination entity in their common lowest-level subnet. The global address has a relative meaning between two communicating entities (for example, the shortest address that one entity can be uniquely identified by another entity). That is, the address of the subnet of the two subnets that include the two communicating entities is the shortest address to be uniquely identified. In this case, the subnet gateway router (SGR) of the subnet stores the prefix of the subnet in a forwarding table, which can be used to convert a local address (identifiable within the subnet) to a global address (identifiable outside the local subnet). In one embodiment, the SGR is a gateway router located at the boundary of the subnet. A detailed explanation is provided below in conjunction with the various accompanying drawings.

[0047] As shown in the figure, the hierarchical network 501 is nested and includes four sub-networks (subnets) 503, 505, 507, and 509. Each sub-network 503, 505, 507, and 509 has a corresponding gateway router 502, 504, 508, and 510, and also has other routers such as router 506. Computing devices 506a, 506b, 508a, 510a, and 512 are respectively coupled to the corresponding routers in a communication manner. In one embodiment, computing devices 506a, 506b, 508a, 510a, and 512 are Figure 1 The computing device 110 in FIG.

[0048] A subnet can include multiple subnets, each of which can be of different sizes. The local addresses of two entities in the same lowest level subnet (i.e., there is no subnetting in the subnet) in the subnet are global to each other (each entity can uniquely identify the other entity with the shortest address (local address in this case)). In other words, an entity only needs to know its local address in the direct subnet. For two entities in different subnets, their lowest level parent subnet (i.e., the subnet that includes the two subnets of the two entities and has the shortest address) is global to each other.

[0049] In one embodiment, each subnet has one or more SGRs that are responsible for forwarding messages into or out of the subnet. Within a subnet, the ISR is responsible for intra-subnet message forwarding. During message forwarding, for discussion purposes, it is assumed that the source address and destination address are known. The address-related fields in the IP header are modified by the SGR in the network. To achieve this, the SGR of the subnet stores a prefix that can be appended to the source address from the subnet to become an address in a higher-level subnet, as described below. If the SGR needs to forward an internal message out of the subnet, the prefix is ​​appended to the source address and then the corresponding source address length is updated. Conversely, if the SGR receives a data message from the outside that is destined for the local subnet (i.e., the subnet prefix matches the destination address), the subnet prefix is ​​removed from the data message destination address and then the destination address length is updated. In contrast, the ISR does not modify the address field. Instead, the ISR can determine the message forwarding direction by simply comparing its source address length with its destination address length, because a destination address that is longer than the source address can indicate that the message needs to be forwarded to a higher-level subnet without looking at the contents of the destination address. Then, depending on the comparison result, the message can be forwarded to the higher or lower subnet, as detailed below.

[0050] For example, each subnet 503, 505, 507, 509 has an address space. Subnet 502 has a 32-bit address space and two lower subnets (subnets 505 and 509 and entity 512 (m)). Subnet 505 has a 16-bit address space and includes entity 506a (x), entity 506b (y), and subnet 507. Subnet 507 (including entity 508a (z)) and subnet 509 (n) each have an 8-bit address space. For the purpose of the following discussion, the entity address and subnet prefix are marked in the hierarchical network 501 as shown.

[0051] exist Figure 5 In the example of , entities 506a and 506b are located in the same subnet. Therefore, in order to communicate, their local addresses in subnet 505 (i.e., addresses "0001" and "0002") can be used as their global addresses. For entities in different subnets, such as entities 506a and 508a, local addresses are not sufficient for communication. In order to communicate, the addresses are converted (modified) to include the lowest level common subnet. For example, entity 506a is located in subnet 505 and entity 508a is located in subnet 507. In order for entities 506a and 508a to communicate, the subnet prefix "0xbb" of entity 508a (the prefix (SGR F) of subnet 507) is appended (or added) to its local address (0x01), becoming a global address (0xbb01).

[0052] As another example, in order for entity 508a to communicate with entity 510a (n), their global addresses in subnet 503 are required. That is, entity 508a is uniquely identified by entity 510a with address "0xaaaabb01", and entity 510a is uniquely identified by entity 508a with address "0xcccccc01". If entity 508a needs to send a message to entity 510a, entity 508a must first obtain the "global" address of entity 510a (0xcccccc01). However, entity 508a only knows its local address "0x01" and uses this local address as the source address in the message. These addresses are stored in the IP header of the data message forwarded to router 508, and the prefix "0xbb" of subnet 507 of router 508 is appended to the source address. The data message is forwarded to 504, and the prefix "0xaaaa" (the address of subnet 505 of router 504) is also appended to the source address. At router 504, the source address and the destination address have the same length, which indicates that the two entities are located in a common subnet at their lowest level. The message can then be forwarded in this subnet to reach router 510 in subnet 509. Before forwarding the message, router 510 removes (or deletes) the prefix "0xcccccc" from the destination address. The remaining address "0x01" is now sufficient to uniquely identify entity 510a in subnet 509.

[0053] The details of the conversion are described below in conjunction with the various drawings.

[0054] Using these techniques, an entity does not need to know the prefix of its direct subnet, and a subnet does not need to know the prefix of a higher level subnet. Instead, this information can be stored in the direct subnet gateway router. The entity itself simply maintains local addresses in its direct subnet. In addition, if address exhaustion occurs (address expansion becomes necessary), another level of subnets can be added, while existing subnets and their corresponding addresses are not affected.

[0055] Figure 6 FIG. 6 shows an example of an IP header related address field provided by an embodiment of the present invention. The IP header related address field 601 (for example, Figure 4The IP header 412 in FIG. 4 includes a source address length (SAL) 603, a destination address length (DAL) 605, a source address (SA) 603a, and a destination address (DA) 605a. The length of the source address 603a is indicated by SAL 603, and the length of the destination address 605a is indicated by DAL 605. In one embodiment, SAL 603 and DAL 605 are fixed. The lengths of the source address 603a and the destination address 605a are variable, as indicated by SAL 603 and DAL 605.

[0056] In the following non-limiting example, for the purpose of discussion, it is assumed that all fields are byte-aligned. However, it should be understood that the length unit of the address can be bytes, bits, nibbles (half bytes) or any other known length unit. Using lengths in bytes can help reduce the size of SAL and DAL, but may produce coarse subnet granularity, which reduces the efficiency of address allocation. For example, 4-bit SAL and DAL are sufficient to encode 16 address lengths (up to 16 bytes) of the subnet using equivalent decimal values ​​(i.e., "0b0000" is 16). By using this length unit, the higher-level subnets are at least expanded by 256 times. On the other hand, using lengths in bits is conducive to achieving finer subnet granularity, but SAL and DAL require more space. For example, 8-bit SAL and DAL can support up to 256-bit addresses, while the higher-level subnets can only be twice as large as before.

[0057] In either embodiment, using this addressing scheme significantly reduces IP header overhead. For example, for communication between entities 506a and 506b ( Figure 5 ), the total IP header overhead associated with the address is at most 6 bytes (24 bits). This is in stark contrast to the 8 bytes (32 bits) required for IPv4 and the 32 bytes (128 bits) required for IPv6. For local communication, for example, communication within the same subnet, the saved overhead can be directly translated into resource, energy and latency gains. For communication outside the local subnet, there is still a significant overhead savings due to intra-network address manipulation.

[0058] 7A to 7CFlowchart of transmitting data message in network provided by the disclosed embodiment of this paper. In the following discussion, intra-band sub-network router (ISR) or sub-network gateway router (SGR) performs these processes. However, it should be understood that any other functional unit or processing unit can implement the process described herein, and the present invention is not limited to being implemented by a router.

[0059] like Fig. 7A As shown, in step 702, the entities (or devices) are organized into a hierarchical network of subnets, as described above in conjunction with Figure 5 Then, in step 704, for example, the IP address of each device in each subnet is obtained using static or dynamic configuration. When an entity (source entity) wants to communicate with another entity (destination entity), the source entity obtains the destination address of the destination entity. Then, in step 706, the source entity forwards the datagram to the destination entity. In one embodiment, according to the protocol (e.g., IPv4) and the routing flow ( Figure 7B or Figure 7C ) forwards data packets in the network. In another embodiment, each entity and router maintains (stores) a forwarding table (e.g., Fig. 8A and Fig.9A The forwarding table shown in the figure) is used to determine the next hop of the data message based on its destination address or address length comparison.

[0060] Figure 7B An exemplary flow of data packets within the same subnet performed by the ISR is shown. In this case, if the source entity and the destination entity are located in the same subnet, the ISR examines the IP header of the data packet sent by the source entity. If in step 708, the ISR determines that the destination address length (DAL) is greater than the source address length (SAL), then in step 710, the data packet is forwarded to the SGR connected to the higher-level supernet. In one embodiment, the data packet can pass through more than one ISR before reaching the SGR. If the DAL is less than or equal to the SAL, then in step 712, the data packet is forwarded to the destination address within the same subnet. In either case, the ISR handles the forwarding without considering the actual source address or destination address.

[0061] Figure 7CAn exemplary flow of data packets performed by the SGR when the source entity and the destination entity are located in different subnets is shown. When the source entity (e.g., source entity 506a) and the destination entity (e.g., destination entity 510a) are located in different subnets, the complete address (i.e., global address) of the destination entity is obtained. This can be achieved by forwarding the data packet to the SGR, which converts the local source address of the source entity when certain conditions are met.

[0062] The terms "super-network" (supernet) and "sub-network" (subnet) are used in the following discussion. From the perspective of a particular SGR, a super-network as defined herein is a high-level network. From the perspective of a particular SGR, a sub-network as defined herein is a low-level network. For example, refer to Figure 5 , the supernet of SGR F (508) is the high-level network 505, and the subnet of SGR F (508) is the low-level network 507. Therefore, in one embodiment, the datagram can be forwarded from the supernet (e.g., the high-level network 505) to the SGR. In another embodiment, the datagram can be forwarded from the subnet (e.g., the low-level network 507) to the SGR. Whether the datagram is received from the supernet or subnet of the SGR and other factors will determine how the datagram is processed.

[0063] In step 714, when a data message is received at the SGR, the SGR determines whether the DAL is greater than the SAL. If the DAL is greater than the SAL, the process proceeds to step 715 to determine whether the SAL is less than the higher-level network (supernet) length. The determination result in step 715 determines whether the data message received at the SGR is from the supernet of the SGR or from the subnet. For example, if the SAL is not less than the supernet length, the data message is from the supernet. If the SAL is less than the supernet length, the data message is from the subnet.

[0064] In the first scenario, when the SAL is less than the supernet length, the process proceeds to step 716, where the local subnet address of the source entity is converted by modifying the source address and the SAL. In the context of the present invention, a local subnet address is any address of a source or destination located within a network whose length is suitable for a subnet. In this case, modifying the source address and the SAL includes appending a prefix of the lower-level network address of the SGR to the source address. In one embodiment, the prefix of the parent subnet is appended to the local subnet address of the message. In one embodiment, the prefix of the lowest-level parent subnet shared by the source and destination in the network is appended to the local subnet address of the message. Then, in step 718, the data message is forwarded to the higher-level network (i.e., supernet) of the SGR.

[0065] In the second scenario, when the SAL is not less than the supernet length (e.g., SAL = supernet length), the process proceeds to step 718. In step 718, the data message is forwarded to the higher-level network (i.e., supernet) of the SGR without any conversion of the local subnet address of the source entity. It is worth noting that there is no need to perform conversion in this scenario. Fig.9A and Fig. 9B Provides detailed examples.

[0066] In step 714, if the router determines that the DAL is less than or equal to the SAL, the process proceeds to step 720 to determine whether the datagram is from the supernet of the SGR or from a subnet. This can be achieved by determining whether the DAL is greater than the subnet length of the lower layer network of the SGR. If in step 720, it is determined that the DAL is not greater than the length of the lower layer network of the SGR (for example, if the DAL is equal to the subnet length of the lower layer network of the SGR), then in step 726, the datagram is forwarded within the same lower layer subnet (the datagram is from the subnet of the SGR).

[0067] If, in step 720, the DAL is greater than the subnet length (the datagram is from the supernet of the SGR), then, in step 722, the destination address is compared to the subnet prefix to determine if there is a match. If the first portion of the destination address and the subnet prefix match, then the destination address is converted to an address in the next subnet by modifying the destination address and the DAL. In this case, modifying the destination address includes removing the subnet prefix from the destination address in step 724. Then, in step 726, the datagram is forwarded within the subnet. If, in step 722, the first portion of the destination address and the subnet prefix do not match, then in step 718, the datagram is forwarded to the upper subnet (i.e., the supernet) for further processing.

[0068] Although the flowchart described above details the overall process, there are some exceptions that are not described. These exceptions can include, for example, a data packet that includes an illegal SAL or DAL arriving at a router. For example, if the address space of a subnet is N bytes, and the SAL or DAL of a data packet in the subnet is less than N, then there is an error. If an error occurs, the packet is discarded.

[0069] Fig. 8A and Figure 8B Shown is the Figure 5800 and 802. The configuration of the subnet is shown in forwarding table 800, and the configuration of the host is shown in forwarding table 802. Specifically, forwarding table 800 is a subnet forwarding table, which stores information about subnets (sub-netework / subnet), the length of addresses in the subnet in bytes, and prefixes of upper-level subnets (the number after the slash " / " represents the length of the prefix in bits). Forwarding table 802 is a host forwarding table, which stores information about host names, subnets to which hosts belong, and addresses of hosts in subnets. In one embodiment, for example, forwarding tables 800 and 802 can be stored in entities and routers (including ISRs and SGRs) of hierarchical network 501.

[0070] Fig.9A An example of routing data packets between entities located in the same subnet is shown. In one example, reference Figure 5 , source entity 506a(x) in subnet 505 sends a datagram to destination entity 506b(y) in subnet 505. The datagram initially arrives at router 506 (ISR C) in subnet 505 using the local source address and destination address. Since the source entity and the destination entity are in the same subnet 505, Figure 7B The routing protocol shown in indicates the path of the data message. In one embodiment, the data message is routed to the destination entity along the shortest path.

[0071] As shown in the figure, only the SAL 901a, DAL 901b, source address 902 and destination address 904 of the IP header (e.g., IPvn header 312) are shown in the data message. SAL 901a, DAL 901b, source address 902 and destination address 904 are collectively referred to as the address-related field 901 of the IPvn header 312 in this article. For the purpose of this example, SAL 901a and DAL 901b have a fixed length of 8 bits to encode the address length in bytes, but any number of bits can be used. As shown in the above example, the fixed address lengths of SAL 901a and DAL 901b are both "0x02", the source address 902 is "0x0001", and the destination address 904 is "0x0002" (also as shown in FIG. 1 ). Figure 5 shown).

[0072] Before the source entity 506a transmits the data packet to the destination entity 506b, the source entity 506a obtains the local address of the destination entity. Fig. 8A and Figure 8B), the datagram (including the address related field 901) is forwarded to the router 506 (ISR C) within its current subnet. When received at the router 506, the DAL 901b is compared with the SAL 901a (step 708).

[0073] In one embodiment, if the router 506 determines that the DAL 901b is greater than the SAL 901a, the datagram is forwarded in the direction of the SGR of the current subnet for continued processing (step 710).

[0074] In another embodiment, if router 505 determines that DAL 901b is not greater than SAL 901a (i.e., SAL is less than or equal to DAL), the datagram is forwarded to destination entity 506b within the current subnet (step 712). In this case, since SAL and DAL are the same length (i.e., SAL and DAL are equal to 0x02), source entity 506a and destination entity 506b are located in the same subnet (e.g., subnet 505). Therefore, the local address can be used to forward the datagram. For example, if Fig.9A As shown, the datagram is forwarded from source entity (x) at source address 902 (0x0001) to ISR C, and then to destination entity (y) at destination address 904 (0x0002) within subnet 505 without making any changes to address-related fields 901. It is worth noting that since only local addresses are used to forward datagrams between the two entities, address space is saved.

[0075] Fig. 9B An example of routing data packets between entities in different subnets is shown. In the example shown, reference Figure 5 , source entity 506a(x) in subnet 505 uses Figure 7C The routing protocol described in detail in FIG. 5 sends the datagram to the destination entity 510a(n) in subnet 510. Since the datagram is forwarded to the destination entity in a different subnet than the source entity, Fig.9A Unlike the example in , the local address of the destination entity 510a is not sufficient to forward the datagram. However, the source entity can obtain the global address of the destination entity. For example, the destination address can be obtained from a mechanism such as the domain name system (DNS).

[0076] and Fig.9AThe example of is similar to that of , only the address-related fields of the IPvn header 312 are shown. In one embodiment, since the address can be converted when forwarding a data message, the address-related fields 906 can be modified. The address-related fields 906 initially include, for example, SAL 900a, DAL 900b, source address 906a, and destination address 906b. For the purpose of this example, SAL 900a and DAL 900b have a fixed length of 8 bits to encode the address length in bytes, but any number of bits can be used. In this case, the fixed address lengths of the source address and the destination address initially have different lengths (sizes). As shown in the figure, the address length of SAL 900a is "0x02", the address length of DAL 900b is "0x04", the source address 906a is "0x0001", and the destination address 906b is "0xcccccc01" (the destination address is twice as long as the source address, as shown in SAL and DAL, but SAL and DAL are fixed and the same). These addresses are also Figure 5 The hierarchical network structure is shown in FIG.

[0077] In one embodiment, the source entity 506a obtains the local address of the destination entity before forwarding the data message. Fig. 8A and Figure 8B )as well as Figure 7C The datagram (including the address-related field 906) is forwarded in the direction of router 504 (SGR B) within its current subnet. When received at router 504, DAL 901b is compared with SAL 801a (step 714).

[0078] In one embodiment, router 504 determines that DAL 900b is greater than SAL 900a. In this case, source address 906a and SAL 900a (the length of the source address) are converted (step 716) by modifying source address 906a to append the prefix of the lower-level parent subnet and modifying SAL 900a to match the new address length. For example, referring to Figure 5 , the prefix 908x "0xaaaa" of the lower subnet 505 (used in the upper subnet 503) is added to modify the source address 906a so that the source address becomes "0xaaaa0001" (i.e., the prefix of the upper subnet and the original source address). Then, the SAL 900a is modified to "0x04" (i.e., the length of the modified address). The modified source address (908x and 906a) and the modified SAL 900a are shown in the modified related address field 908. Then, the data message including the modified address related field 908 can be forwarded (step 718) within the upper supernet. In the above example, the message is forwarded to the router 510 (SGRE).

[0079] In another embodiment, DAL 900b is not greater than SAL 900a. For example, the modified SAL 900a and DAL 900b in the address-related field (address-related field 908) are compared (step 714). Since the modified SAL 900a and DAL 900b are equal (SAL and DAL are equal to "0x04" at router 504 (SGR B)), this indicates that source entity 506a and destination entity 510a are located in a common subnet (i.e., subnet 503) at their lowest level, the process next compares DAL 900b with the current subnet length (step 720).

[0080] In one embodiment, if the comparison result is that DAL 900b is equal to the subnet length, the datagram is forwarded within the subnet (step 726), and the process is repeated.

[0081] In another embodiment, at router 510 (SGR E), if DAL 900b is greater than the subnet length, the destination address is compared to the subnet prefix. Following the current example, the length of DAL 900b is "0x04" and the address length of subnet 509 is 1 (as shown in forwarding table 800). Therefore, the prefix of destination address 906b in modified address-related field 908 is compared to the subnet address prefix (i.e., the address of subnet 509) (step 722). For example, destination address 906b "0xcccccc01" in address-related field 908 is compared to the prefix "0xcccccc" of subnet 509 of router 510 (SGR E).

[0082] In one embodiment, if the destination address 906b in the address-related field 908 does not match the subnet prefix, the datagram is forwarded to an upper subnet (step 718) for continued processing as described above.

[0083] In another embodiment, if the destination address 906b in the address-related field 908 matches the subnet prefix, the destination address 906b is modified by removing the prefix from the translated local subnet address and the DAL 900b is modified to be consistent with the new address length, and the destination address 906b and DAL 900b (the length of the destination address) are converted (step 724). For example, referring to Figure 5, remove the prefix 906b (0xcccccc) of the converted local subnet address (0xcccccc01) to modify the destination address 906b so that the destination address 906b becomes "0x01" (i.e., the destination address of the entity 510a in the subnet 509). Then, the DAL 900b is modified to "0x01" (i.e., the length of the modified address). The modified destination address (910a) and the modified DAL 900b are shown in the modified related address field 910. Then, the data packet including the modified address related field 910 can be forwarded (step 726) to the next hop in the subnet. In the above example, the next hop in the subnet is the router 510 (SGR E), and then the router 510 forwards the data packet to the entity 510a (n).

[0084] Fig.10 An embodiment of a node provided by an embodiment of the present invention is shown. A node (e.g., a router) can transmit and receive data (e.g., IP packets) between at least one electronic device and / or a server 110, etc., through a network such as a network 130 (e.g., a global network). The node 1000 can transmit an IP packet received through the network to another electronic device 110 through a local network. In addition, the node 100 can transmit an IP packet received from another electronic device to an electronic device or a server 110 through a network.

[0085] In one embodiment, the node 1000 may include: a plurality of input / output ports 1010 / 1030 and / or a receiver (Rx) 1012 and a transmitter (Tx) 1032 for receiving and sending data from other nodes; a processor 1020 including an address translation circuit to process data and determine to which node the data is to be sent; a memory 1022 including a cache 1024 and a long-term memory 1026; and a direct memory access (DMA) controller 1032. Although the processor 1020 is shown as a single processor, the processor 1020 is not limited thereto and may include multiple processors. The processor 1020 may be implemented as one or more central processing unit (CPU) chips, one or more cores (e.g., a multi-core processor), one or more field-programmable gate arrays (FPGAs), one or more application specific integrated circuits (ASICs), and / or one or more digital signal processors (DSPs), and / or may be part of one or more ASICs. The processor 1020 may be used to implement any of the solutions described herein using any one or combination of the steps described in the embodiments. In addition, the processor 1020 may be implemented using hardware, software, or both hardware and software.

[0086] Storage (storage / memory) 1022 may include cache 1024 and long-term storage 1026, and may be used to store routing tables, forwarding tables, or other tables or information disclosed herein. Although storage 1022 is shown as a single memory, storage 1022 may be implemented as a combination of read-only memory (ROM), random access memory (RAM), or auxiliary memory (e.g., one or more disk drives or tape drives for non-volatile storage of data).

[0087] The DMA controller 1032 may support data transfer between components in the node 1000. In an exemplary embodiment, the DMA controller 500 may control the transmission of IP packets between the processor 1020 and the memory 1022. In addition, the DMA controller 1032 may transmit the header of the IP packet stored in the memory 1022 to the address conversion circuit 1028 in the processor 1020 and / or store the header converted by the address conversion circuit 1028 in the memory 1022.

[0088] In one embodiment, according to an embodiment of the present invention, the network address of the IP message received by the node can be transformed or converted by the address conversion circuit 1028. The IP message including the transformed or converted network address can be stored in the memory 1022. The processor 1020 can transform or convert the network address of the IP message to comply with the address system recognizable by the electronic device or server 110. Other electronic devices or servers 110 in the network can process the IP message including the transformed or converted network address. In another embodiment, the processor 1020 can transform or convert the network address of the IP message to shorten the address, and transmit the IP message including the transformed or converted network address to the destination device, such as the electronic device or server 110 or another node 1000.

[0089] Fig.11 An exemplary embodiment of a computing system for implementing an embodiment of the present invention is shown. Computer system 1100 includes a processor 1104 and a memory 1108, which communicate with each other and with other components via a bus 1112. Bus 1112 may include any of several types of bus structures, including but not limited to a memory bus, a memory controller, a peripheral bus, a local bus, and any combination thereof using any of a variety of bus architectures.

[0090] The memory 1108 may include various components (e.g., machine-readable media), including, but not limited to, random access memory components, read-only components, and any combination thereof. In one example, a basic input / output system (BIOS) 1116 may be stored in the memory 1108, the BIOS 1116 including basic routines that help transfer information between elements within the computer system 1100 during the boot process. The memory 1108 may also include instructions (e.g., software) 1120 (e.g., stored in one or more machine-readable media) to embody any one or more aspects and / or methods of the present invention. In another example, the memory 1108 may also include any number of program modules, including, but not limited to, an operating system, one or more application programs, other program modules, program data, and any combination thereof.

[0091] The computer system 1100 also includes a storage device 1124. Examples of storage devices (e.g., storage device 1124) include, but are not limited to, hard disk drives, disk drives, optical disk drives combined with optical media, solid-state memory devices, and any combination thereof. The storage device 1124 can be connected to the bus 1112 via a suitable interface (not shown). Exemplary interfaces include, but are not limited to, SCSI, advanced technology attachment (ATA), serial ATA, universal serial bus (USB), IEEE 1394 (Firewire interface), and any combination thereof. In one example, the storage device 1124 (or one or more of its components) can be removably connected to the computer system 1100 (e.g., via an external port connector (not shown)). Specifically, the storage device 1124 and the associated machine-readable medium 1128 can provide non-volatile and / or volatile storage of machine-readable instructions, data structures, program modules, and / or other data for the computer system 1100. In one example, the software 1120 can be located entirely or partially within the machine-readable medium 1128. In another example, the software 1120 may reside completely or partially within the processor 1104 .

[0092] The computer system 1100 may also include an input device 1132. In one example, a user of the computer system 1100 may input commands and / or other information into the computer system 700 via the input device 1132. Examples of the input device 1132 include, but are not limited to, an alphanumeric input device (e.g., a keyboard), a pointing device, a joystick, a game pad, an audio input device (e.g., a microphone, a voice response system, etc.), a cursor control device (e.g., a mouse), a touch pad, an optical scanner, a video capture device (e.g., a still camera, a video camera), a touch screen, and any combination thereof. The input device 1132 may be connected to the bus 1112 via any of a variety of interfaces (not shown), including, but not limited to, a serial interface, a parallel interface, a game port, a USB interface, a FireWire interface, a direct interface to the bus 1112, and any combination thereof. The input device 1132 may include a touch screen interface, which may be part of or separate from the display 1136, as will be discussed further below. The input device 1132 may be used as a user selection device to select one or more graphical representations in the graphical interface as described above.

[0093] The user may also input commands and / or other information to the computer system 1100 through the storage device 1124 (e.g., a removable disk drive, a flash drive, etc.) and / or the network interface device 1140. Network interface devices such as the network interface device 1140 may be used to connect the computer system 1100 to one or more of various networks (e.g., the network 1144) and one or more remote devices 1148 connected thereto. Examples of network interface devices include, but are not limited to, network interface cards (e.g., mobile network interface cards, LAN cards), modems, and any combination thereof. Examples of networks include, but are not limited to, wide area networks (e.g., the Internet, enterprise networks), local area networks (e.g., networks associated with offices, buildings, campuses, or other relatively small geographic spaces), telephone networks, data networks associated with telephone / voice providers (e.g., mobile communications provider data and / or voice networks), direct connections between two computing devices, and any combination thereof. Networks such as the network 1144 may use wired and / or wireless communication modes. In general, any network topology may be used. Information (e.g., data, software 1120, etc.) may be transmitted between computer systems 1100 via the network interface device 1140.

[0094] The computer system 1100 may also include a video display adapter 1152 for sending a displayable image to a display device, such as a display device 1136. Examples of display devices include, but are not limited to, a liquid crystal display (LCD), a cathode ray tube (CRT), a plasma display, a light emitting diode (LED) display, and any combination thereof. The display adapter 1152 and the display device 1136 may be used in conjunction with the processor 1104 to provide graphical representations of various aspects of the present invention. In addition to the display device, the computer system 1100 may also include one or more other peripheral output devices, including, but not limited to, audio speakers, printers, and any combination thereof. Such peripheral output devices may be connected to the bus 1112 via a peripheral interface 1156. Examples of peripheral interfaces include, but are not limited to, serial ports, USB connections, FireWire interface connections, parallel connections, and any combination thereof.

[0095] It should be understood that the subject matter of the present invention can be embodied in many different ways and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to make this subject matter thorough and complete, and to fully convey the present invention to those skilled in the art. In fact, the purpose of this subject matter is to cover the substitutes, modifications and equivalents of these embodiments, which are included in the scope and spirit of this subject matter defined by the appended claims. Moreover, in the detailed description of the subject matter of the present invention below, many specific details are set forth in order to provide a thorough understanding of the subject matter of the present invention. However, it is clear to those of ordinary skill in the art that the subject matter of the present invention can be practiced without these specific details.

[0096] Various aspects of the present invention are described herein in conjunction with the flowchart and / or block diagram of the method, device (system) and computer program product provided in the embodiment of the present invention. It should be understood that each square frame of the flowchart and / or block diagram and the combination of square frames in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable instruction execution device produce a mechanism for implementing the function / action described in detail in the flowchart and / or block diagram.

[0097] Non-transitory computer-readable media include all types of computer-readable media, including magnetic storage media, optical storage media, and solid-state storage media, but specifically do not include signals. It should be understood that the software can be installed in a device and sold with the device. Alternatively, the software can be obtained and loaded into the device, including via optical disk media or any other means of obtaining the software from a network or distribution system, including (for example) obtaining the software from a server owned by the creator of the software or from a server that the creator of the software does not own but uses. For example, the software can be stored in a server for distribution over the Internet.

[0098] Computer-readable storage media do not include propagating signals, are accessible by computers and / or processors, and include volatile and non-volatile removable and / or non-removable internal and / or external media. Various types of storage media hold stored data in any suitable digital format for a computer. Those skilled in the art will appreciate that other types of computer-readable media, such as compression drives, solid-state drives, magnetic tapes, flash cards, flash drives, boxes, etc., may be used to store computer-executable instructions for performing the novel methods (actions) of the disclosed architecture.

[0099] The terms used herein are only for the purpose of describing specific aspects and are not intended to limit the present invention. Unless the context clearly indicates otherwise, the singular forms "a", "an" and "said" used herein include plural meanings. It should also be understood that the term "comprising" used in this specification is used to illustrate the presence of the described features, integers, steps, operations, elements and / or parts, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or combinations thereof.

[0100] The description of the present invention is presented for illustration and description purposes only and is not intended to be exhaustive or to limit the present invention in any disclosed manner. Various modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the present invention. Various aspects of the present invention are selected and described in order to better explain the principles and practical applications of the present invention and to enable those of ordinary skill in the art to understand the present invention and various modifications suitable for the intended specific use.

[0101] For the purposes of this document, each process associated with the disclosed technology can be performed serially by one or more computing devices. Each step in the process can be performed by the same or different computing devices used in other steps, and each step does not have to be performed by a single computing device.

[0102] Although the subject matter has been described in language specific to structural features and / or method actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Instead, the specific features and actions described above are disclosed as exemplary ways to implement the claims.

Claims

1. A method for transmitting a data message from a source to a destination in a communication network, characterized in that The method comprises: receiving a data packet from the source located in a local subnet of the network, wherein the data packet includes a first network layer protocol header having a source address including a local subnet address of the source, a destination address of the destination, a first field indicating a length of the source address, and a second field indicating a length of the destination address; The first network layer protocol header is converted by modifying the source address and the first field indicating the length of the source address, wherein the modification includes appending the prefix of the subnet to the local subnet address so that the source address becomes the address of a higher-level network; the modification also includes modifying at least one of the first field indicating the length of the source address and the second field indicating the length of the destination address; Forwarding the data message including the converted local subnet address to the destination in the high-level network; The first field includes: a source address length SAL; the second field includes a destination address length DAL; The method further comprises: If the DAL is greater than the SAL, determining whether the SAL is less than the high-level network length; If so, forwarding the data message within the high-level network by modifying the source address and the SAL, converting the network layer protocol header; If not, forwarding the data message within the high-level network; If the DAL is not greater than the SAL, determining whether the DAL is greater than the length of the lower layer subnet; If yes, determine whether the DAL matches the lower subnet prefix, if yes, convert the network layer protocol header by modifying the destination address and the DAL, and forward the data message in the lower subnet, if no, forward the data message in the higher network; If not, forward the data message within the lower subnet.

2. The method according to claim 1, characterized in that The method further comprises: receiving a second data packet having a second local subnet address of a second source and a second destination address in a second network layer protocol header; transforming the second network layer protocol header by modifying the second destination address and a third field indicating a length of the second destination address, wherein the modification includes removing a prefix of the higher-layer network from the second destination address; The second data packet including the converted destination address is forwarded to the second destination address.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: When the length of the source address represented by the first field is less than the length of the destination address represented by the second field, it is determined that the destination is outside the local subnet of the source, wherein the converting and forwarding are responsive to the determination.

4. The method according to claim 1 or 2, characterized in that: The communication network includes a plurality of sources and destinations arranged in a nested hierarchical subnet structure.

5. The method according to claim 1 or 2, characterized in that: The source address is a local subnet address used to forward the data message to the destination address.

6. The method according to claim 1 or 2, characterized in that: The first field indicating the length of the source address and the second field indicating the length of the destination address are both of fixed length.

7. A router for transmitting data packets from a source to a destination in a communication network, characterized in that The router comprises: A non-transitory memory including instructions; One or more processors in communication with the memory, wherein the one or more processors execute the instructions to perform the following steps: receiving a data packet from the source located in a local subnet of the network, wherein the data packet includes a first network layer protocol header having a source address including a local subnet address of the source, a destination address of the destination, a first field indicating a length of the source address, and a second field indicating a length of the destination address; The first network layer protocol header is converted by modifying the source address and the first field indicating the length of the source address, wherein the modification includes appending the prefix of the subnet to the local subnet address so that the source address becomes the address of a higher-level network; the modification also includes modifying at least one of the first field indicating the length of the source address and the second field indicating the length of the destination address; Forwarding the data message including the converted local subnet address to the destination of the high-level network; The first field includes: a source address length SAL; the second field includes a destination address length DAL; The one or more processors execute the instructions to further perform the following steps: If the DAL is greater than the SAL, determining whether the SAL is less than the high-level network length; If so, forwarding the data message within the high-level network by modifying the source address and the SAL, converting the network layer protocol header; If not, forwarding the data message within the high-level network; If the DAL is not greater than the SAL, determining whether the DAL is greater than the length of the lower layer subnet; If yes, determine whether the DAL matches the lower subnet prefix, if yes, convert the network layer protocol header by modifying the destination address and the DAL, and forward the data message in the lower subnet, if no, forward the data message in the higher network; If not, forward the data message within the lower subnet.

8. The router according to claim 7, characterized in that: The one or more processors further execute the instructions to perform the following steps: receiving a second data packet having a second local subnet address of a second source and a second destination address in a second network layer protocol header; transforming the second network layer protocol header by modifying the second destination address and a third field indicating a length of the second destination address, wherein the modification includes removing a prefix of the higher-layer network from the second destination address; The second data packet including the converted destination address is forwarded to the second destination address in the higher-level network.

9. The router according to claim 7 or 8, characterized in that: The one or more processors also execute the instructions to perform the following steps: when the length of the source address represented by the first field is less than the length of the destination address represented by the second field, determine that the destination is outside the local subnet of the source, wherein the converting and forwarding steps are in response to the determining steps.

10. The router according to claim 7 or 8, characterized in that: The communication network includes a plurality of sources and destinations arranged in a nested hierarchical subnet structure.

11. The router according to claim 7 or 8, characterized in that: The source and destination addresses for each device are either statically configured or dynamically configured.

12. The router according to claim 7 or 8, characterized in that: The source address is a local subnet address used to forward the data message to the destination address.

13. The router according to claim 7 or 8, characterized in that: The first field indicating the length of the source address and the second field indicating the length of the destination address are both of fixed length.

14. A non-transitory computer readable medium storing computer instructions, characterized in that: The computer instructions are used to transmit a data message from a source to a destination within a communication network, and when the computer instructions are executed by one or more processors, the one or more processors perform the following steps: receiving a data packet from the source located in a local subnet of the network, wherein the data packet includes a first network layer protocol header having a source address including a local subnet address of the source, a destination address of the destination, a first field indicating a length of the source address, and a second field indicating a length of the destination address; The first network layer protocol header is converted by modifying the source address and the first field indicating the length of the source address, wherein the modification includes appending the prefix of the subnet to the local subnet address so that the source address becomes the address of a higher-level network; the modification also includes modifying at least one of the first field indicating the length of the source address and the second field indicating the length of the destination address; Forwarding the data message including the converted local subnet address to the destination in the high-level network; The first field includes: a source address length SAL; the second field includes a destination address length DAL; When the computer instructions are executed by one or more processors, the one or more processors further perform the following steps: If the DAL is greater than the SAL, determining whether the SAL is less than the high-level network length; If so, forwarding the data message within the high-level network by modifying the source address and the SAL, converting the network layer protocol header; If not, forwarding the data message within the high-level network; If the DAL is not greater than the SAL, determining whether the DAL is greater than the length of the lower layer subnet; If yes, determine whether the DAL matches the lower subnet prefix, if yes, convert the network layer protocol header by modifying the destination address and the DAL, and forward the data message in the lower subnet, if no, forward the data message in the higher network; If not, forward the data message within the lower subnet.

15. The non-transitory computer readable medium of claim 14, wherein: The one or more processors also perform the following steps: receiving a second data packet having a second local subnet address of a second source and a second destination address in a second network layer protocol header; transforming the second network layer protocol header by modifying the second destination address and a third field indicating a length of the second destination address, wherein the modification includes removing a prefix of the higher-layer network from the second destination address; The second data packet including the converted destination address is forwarded to the second destination address.

16. The non-transitory computer readable medium according to claim 14 or 15, characterized in that: The one or more processors also perform the following steps: when the length of the source address represented by the first field is less than the length of the destination address represented by the second field, determine that the destination is outside the local subnet of the source, wherein the converting and forwarding steps are in response to the determining step.

17. The non-transitory computer readable medium according to claim 14 or 15, characterized in that: The communication network includes a plurality of sources and destinations arranged in a nested hierarchical subnet structure.

18. The non-transitory computer readable medium according to claim 14 or 15, wherein: The source address is a local subnet address used to forward the data message to the destination address.

19. The non-transitory computer readable medium according to claim 14 or 15, wherein: The first field indicating the length of the source address and the second field indicating the length of the destination address are both of fixed length.