Granted Patent B2

US 12,376,000 · App. 17/846,712 · Granted Jul 29, 2025

Inventor: Paulo Mendes (Munich, DE)

Assignee: Airbus (S.A.S.)

H04W40/246H04W40/06H04W40/20H04W48/16H04W48/20H04W84/18H04W88/08

Abstract

Claims (57)

1. A method for routing data packets between a first end device and a second end device via a mobile ad-hoc network that comprises multiple routing devices that are communicatively interconnected with each other, the method comprising:

generating, by the first end device, a data request message;

sending the data request message to a first routing device;

forwarding, by the first routing device the data request message to at least two neighbor routing devices by using a first opportunistic forwarding mechanism, wherein the data request message is forwarded to each of the at least two neighbor routing devices via different routes through the mobile ad-hoc network;

providing, by the second end device and in response to the data request message, a requested data packet to a second routing device;

forwarding, by the second routing device, the requested data packet via the mobile ad-hoc network to the first end device by using a source based forwarding mechanism;

determining, by the second routing device, if the source based forwarding mechanism fails in forwarding the requested data packet to the first end device; and

in response to the source based forwarding mechanism failing to forward the requested data packet to the first end device, using a second opportunistic forwarding mechanism for forwarding the requested data packet to the first end device;

wherein forwarding, by the first routing device, the data request message to at least two neighbor routing devices by using a first opportunistic forwarding mechanism comprising:

generating a source tuple identifying the first end device;

generating a destination tuple identifying the second end device;

defining a path quality tuple identifying a minimum bandwidth and a minimum accumulative transmission latency in a data transmission path;

defining a path vector identifying a list of all nodes crossed by the data request message; and

adding the source tuple, the destination tuple, the path quality tuple, and the path vector to a header of the data request message; and

wherein the method further comprises:

in response to the requested data packet being available in the content store, adding the path quality tuple and the path vector tuple contained in the header of the data request message to a local vector associated with the source tuple contained in the data request message to identify the first end device; and

in response to the path quality tuple contained in the header of the data request message meeting the path quality required for transmitting the requested data packet, formatting the requested data packet to be transmitted to the first end device based on the information stored in the header of the data request message.

2. The method of claim 1 , further comprising:

determining, by the first routing device, if a requested data packet is available in a content store of the first routing device;

when the requested data packet is available in the content store, forwarding the requested data packet to the first end device by using the source based forwarding mechanism;

when the requested data packet is not available in the content store, continuing the method with forwarding the data request message to at least two neighbor routing devices.

3. The method of claim 2 , further comprising storing, by the first routing device, the requested data packet in the content store of the first routing device.

4. The method of claim 1 , wherein the forwarding, by using the source based forwarding mechanism, comprises forwarding a requested data packet based on a list of next hops that is stored in a header of the requested data packet.

5. The method of claim 1 , wherein the first opportunistic forwarding mechanism and/or the second opportunistic forwarding mechanism is or are configured to forward the data request message and the data packet, respectively, based on a correlation of a destination location, the location of a current network node, and the location of neighbors of the current network node.

6. The method of claim 1 , further comprising providing a data identifier identifying the requested data packet.

7. The method of claim 1 , wherein the source tuple includes at least a geolocation of the source, and optionally a direction value and a speed value; and

wherein the destination tuple includes at least a geolocation of the destination, and optionally a direction value and a speed value.

8. The method of claim 1 , wherein the method comprises:

when the requested data packet is not available in the content store:

determining if the destination tuple contains a geolocation, a direction value, and a speed value, and if so, updating the geolocation in the destination tuple based on the direction value and the speed value, and forwarding the data request message towards a current geolocation of the second end device;

when a distance of the first routing device to the second end device is higher than a predetermined hop count value, forwarding, by the first routing device, the data request message to a plurality of routing devices that are closer to the geolocation of the second end device;

when the distance of the first routing device to the second end device is smaller than the predetermined hop count value, broadcasting the data request message to all neighbors of the first routing device.

9. The method of claim 1 , wherein the forwarding, by the second routing device, the requested data packet via the mobile ad-hoc network to the first end device by using a source based forwarding mechanism comprises:

generating a source tuple identifying the second end device;

generating a destination tuple identifying the first end device;

defining a path vector identifying a list of all nodes that define a path of the requested data packet through the mobile ad-hoc network; and

adding the source tuple, the destination tuple, and the path vector to a header of the requested data packet.

10. The method of claim 9 ,

wherein, when the path vector in the header of the requested data packet is not null, forwarding the requested data packet to the next routing device in the path vector;

when forwarding to the next routing device in the path vector fails, deleting the path vector in the header of the requested data packet and forwarding the requested data packet following an opportunistic forwarding mechanism.

11. A routing device for routing data packets between a first end device and a second end device via a mobile ad-hoc network,

wherein the routing device is configured to:

receive, from the first end device, a data request message;

forward the data request message to at least two neighbor routing devices via different routes through the mobile ad-hoc network and by using a first opportunistic forwarding mechanism;

receive, from the second end device or a neighbor routing device, a requested data packet;

forward the requested data packet to the first end device by using a source based forwarding mechanism;

determine if the source based forwarding mechanism fails in forwarding the requested data packet to the first end device;

use a second opportunistic forwarding mechanism to forward the requested data packet to the first end device in response to the source based forwarding mechanism failing to forward the requested data packet to the first end device;

wherein forwarding the data request message to at least two neighbor routing devices includes the routing device being configured to use a first opportunistic forwarding mechanism, including the routing device being configured to:

generate a source tuple identifying the first end device;

generate a destination tuple identifying the second end device;

define a path quality tuple identifying a minimum bandwidth and a minimum accumulative transmission latency in a data transmission path;

define a path vector identifying a list of all nodes crossed by the data request message; and

add the source tuple, the destination tuple, the path quality tuple, and the path vector to a header of the data request message; and

wherein the routing device is further configured to:

in response to the requested data packet being available in the content store, add the path quality tuple and the path vector tuple contained in the header of the data request message to a local vector associated with the source tuple contained in the data request message to identify the first end device; and

in response to the path quality tuple contained in the header of the data request message meeting the path quality required for transmitting the requested data packet, format the requested data packet to be transmitted to the first end device based on the information stored in the header of the data request message.

Assignments (1)

Priority Claims (1)

Continuity (1)

References Cited (24)