An unmanned vehicle, UV, system providing network data connectivity, the UV system comprising: a plurality of UV nodes (110, 111; 200), each comprising a hardware communication interface and processor to transmit and receive data in a network comprised of the plurality of UV nodes (110, 111; 200) and other nodes according to a routing protocol; and a plurality of fixed nodes (105, 106) with a wired or wireless connection to a destination terminal, wherein a UV node (110, 111; 200) of the plurality of UV nodes (110, 111; 200) receives data from a source terminal for transmission to a destination terminal, and when the UV node (110, 111; 200) is within range of a node in the network connected the destination terminal, the UV node (110, 111; 200) transmits the received data to the node within range for forwarding the data to the destination terminal via the network, wherein the UV node (110, 111; 200) is programmed with a travel route, and during travel on the programmed travel route, the UV node (110, 111; 200) broadcasts a beacon ID to identify terminals (104, 210) within range of the UV node (110, 111; 200) during its travel on the travel route, wherein the UV node (110, 111; 200) receives a connection request from the source terminal in response to the terminal receiving the broadcasted beacon ID, and the UV node (110, 111; 200) receives the data from the source terminal after establishing (406, 407) a connection with the source terminal in response to the connection request, wherein the received connection request includes a terminal ID of the source terminal, and the UV node (110, 111; 200) determines whether the terminal ID is for a terminal (104, 210) expected to be at the UV node's current location on the programmed travel route, and if the source terminal is determined to be an expected terminal (104, 210) for the current location, the UV node (110, 111; 200) establishes the connection with the source terminal, wherein if the UV node (110, 111; 200) determines the received terminal ID is not for an expected terminal, the UV node (110, 111; 200) determines whether the terminal is an approved terminal (104, 210) before establishing (424, 425) a connection with the terminal, characterized in that if the UV node (110, 111; 200) determines the terminal is an approved terminal (104, 210), the UV node (110, 111; 200) determines an amount of data to be transmitted to the UV node (110, 111; 200) from the terminal, and wherein the UV node (110, 111; 200) determines whether its travel route is to be modified based on the amount of data to be transmitted from the terminal to the UV node (110, 111; 200). a plurality of UV nodes (110, 111; 200), each comprising a hardware communication interface and processor to transmit and receive data in a network comprised of the plurality of UV nodes (110, 111; 200) and other nodes according to a routing protocol; and a plurality of fixed nodes (105, 106) with a wired or wireless connection to a destination terminal, wherein a UV node (110, 111; 200) of the plurality of UV nodes (110, 111; 200) receives data from a source terminal for transmission to a destination terminal, and when the UV node (110, 111; 200) is within range of a node in the network connected the destination terminal, the UV node (110, 111; 200) transmits the received data to the node within range for forwarding the data to the destination terminal via the network, wherein the UV node (110, 111; 200) is programmed with a travel route, and during travel on the programmed travel route, the UV node (110, 111; 200) broadcasts a beacon ID to identify terminals (104, 210) within range of the UV node (110, 111; 200) during its travel on the travel route, wherein the UV node (110, 111; 200) receives a connection request from the source terminal in response to the terminal receiving the broadcasted beacon ID, and the UV node (110, 111; 200) receives the data from the source terminal after establishing (406, 407) a connection with the source terminal in response to the connection request, wherein the received connection request includes a terminal ID of the source terminal, and the UV node (110, 111; 200) determines whether the terminal ID is for a terminal (104, 210) expected to be at the UV node's current location on the programmed travel route, and if the source terminal is determined to be an expected terminal (104, 210) for the current location, the UV node (110, 111; 200) establishes the connection with the source terminal, wherein if the UV node (110, 111; 200) determines the received terminal ID is not for an expected terminal, the UV node (110, 111; 200) determines whether the terminal is an approved terminal (104, 210) before establishing (424, 425) a connection with the terminal, characterized in that if the UV node (110, 111; 200) determines the terminal is an approved terminal (104, 210), the UV node (110, 111; 200) determines an amount of data to be transmitted to the UV node (110, 111; 200) from the terminal, and wherein the UV node (110, 111; 200) determines whether its travel route is to be modified based on the amount of data to be transmitted from the terminal to the UV node (110, 111; 200).