Anti-GPS spoofing Sample Clauses

Anti-GPS spoofing. 3.1.5.1 Problem and challenges Network slicing and management rely on the characteristics of user equipment (UE) mobility pattern and UE density. Such systems need the UE to report its location information to allocate the communication resources to a certain area. Nowadays, the Global Navigation Satellite System (GNSS), specifically GPS, is the primary location technology used by UE due to its global coverage and accuracy. However, the unencrypted civil GPS signals are inherently vulnerable to spoofing attacks. Indeed, an attacker can use low-cost Software Defined Radio (SDR) tools, such as Universal Software Radio Peripheral (USRP), to generate fake GPS signals to fool the GPS receiver into calculating false positions. In another attack scenario, an adversary may deliberately report false GPS data to platform, which can lead to collision risks. Thus, without an accurate verification of the position claimed by a UE in an adversarial setting, the network may be deceived into allocating more resources to a mirage use case.

Anti-GPS spoofing. The API for anti-GPS spoofing is defined following the OpenAPI format. As illustrated in Figure 33, the API includes two interfaces, one for GPS verification and the other for model update. The modelUpdate interface is designed to update the spoofing detection model on the edge base station server, requiring the model ID, cellular ID and the update timestamp, and the response is whether the model has been updated successfully or not. The gpsVerification interface is used by the UAV with POST method. It takes as inputs the location information, which is an array containing GPS positions and corresponding timestamps, and delivers a report specifying if the location positions are spoofed or not. Figure 33: REST API of Anti-GPS Spoofing enabler 6 Demonstration of D3.3 enablers