Device location verification for updated map data
AssigneeHERE Global B.V.
InventorMike Beauford
Life of this patent
Estimating the term…
Abstract
Systems and methods for verifying a device requesting map data is within an approved geographic boundary. The method includes receiving a request including a route hop count and a latency value calculated from the device to a network node. The route hop count and latency values are compared against threshold values. The device is determined to be within the approved geographic boundary based on the comparison.
Claims20
A method for verifying a device requesting map data is within an approved geographic boundary, the method comprising:
- receiving, by a processor, a request from the device for map data, the request including a first route hop count and a first latency value calculated from the device to a first network node;
- comparing, by the processor, the first route hop count to a first threshold hop count;
- comparing, by the processor, the first latency value to a first latency threshold;
- and
- determining, by the processor, whether the device is within the approved geographic boundary based on the comparison of the first route hop count and the first latency value.
A system for verifying a device is within an approved geographic boundary, the system comprising:
- a geographic database configured to store map data;
- a receiving module configured to receive a request from the device for the map data, the request including a route hop count and a latency value calculated from the device to a network node;
- a threshold identification module configured to calculate a threshold hop count and a threshold latency value that correspond to the network node and the approved geographic boundary;
- a location verification module configured to determine based on the rout hop count, the latency value, the threshold hop count, and the threshold latency value that the device is within the approved geographic boundary;
- and
- a transmitting module configured to transmit the map data to the device when the device is within the approved geographic boundary.
A method for distributing map data to a device, the method comprising:
- generating, by a server, a blockchain including a smart contract for map data, wherein the smart contract includes a condition that a device be within a geographic boundary;
- receiving, by the server, a transaction including a hop count value and a latency value calculated from the device to a network node of a plurality of network nodes;
- receiving, by the server, a validation of the transaction by the plurality of network nodes storing the blockchain;
- determining, by the server, based on the hop count value and the latency value whether the device is within the geographic boundary;
- and
- transmitting, by the server, the map data to the device when the condition is true.
A method for verifying a device requesting map data is within an approved geographic boundary, the method comprising:
- transmitting, by the device, a first plurality of messages to a network node;
- receiving, by the device, a second plurality of messages from the network node;
- calculating, by the device, a number of route hops from the device to the network node from the first plurality of messages and the second plurality of messages;
- calculating, by the device, a latency value for a round trip from the device to the network node from the first plurality of messages and the second plurality of messages;
- transmitting, by the device, a request for the map data including an identity of the network node, the number of route hops, and the latency value;
- and
- receiving, by the device, the map data when a location of the device is verified to be within the approved geographic boundary based on the identity of the network node, the number of route hops, and the latency value.
Dependencies are inferred from the claim text.