IoT Security 261
a coverage area and while a drone moves from one area to another, the new LRC will
be responsible for connectivity and related procedures.
If the IoT anomaly detection module detects a suspicious pattern in the data received
from any drone, it will inform the associated LRC to initiate a mitigation strategy. The
mitigation strategy starts with cancellation of the task, triggering automatic clean‐up of
malwares or malicious content. If the automatic clean‐up activity fails, LRC sends a
message to the service center to perform manual clean‐up and de‐authenticate malicious drones from the network. In case the suspicious drone does not belong to an
Robot
Yes
Yes
Forward the traffic
No
No
Local Robot
Controller
Is it safe
traffic?
Drop the traffic and inform
parent core network
Is it safe
traffic?
Send to parent
Orchestrator to inform
other Orchestrators
Orchestrators informs
their related Local Robot
Controllers
loT Anomaly
Detection
Inform core network and
Local Robot Controller
Figure 11.9 Robot anomaly detection and mitigation procedure.
Robot
Local Robot
Controller
Attach Request
(IMSI/PTIMSI)
Attach Request
(IMSI/PTIMSI)
NAS Security Setup
NAS Security Setup
Authentication
Request
Robot Location
Update
Authentication
Response
Attach Response
Robot User Plane
Control Plane
Session
Establishment
eNB
MME
S/P Gateway
HSS
IoT Anomaly
Detection
Figure 11.10 Robot authentication and sessions establishment.
a coverage area and while a drone moves from one area to another, the new LRC will
be responsible for connectivity and related procedures.
If the IoT anomaly detection module detects a suspicious pattern in the data received
from any drone, it will inform the associated LRC to initiate a mitigation strategy. The
mitigation strategy starts with cancellation of the task, triggering automatic clean‐up of
malwares or malicious content. If the automatic clean‐up activity fails, LRC sends a
message to the service center to perform manual clean‐up and de‐authenticate malicious drones from the network. In case the suspicious drone does not belong to an
Robot
Yes
Yes
Forward the traffic
No
No
Local Robot
Controller
Is it safe
traffic?
Drop the traffic and inform
parent core network
Is it safe
traffic?
Send to parent
Orchestrator to inform
other Orchestrators
Orchestrators informs
their related Local Robot
Controllers
loT Anomaly
Detection
Inform core network and
Local Robot Controller
Figure 11.9 Robot anomaly detection and mitigation procedure.
Robot
Local Robot
Controller
Attach Request
(IMSI/PTIMSI)
Attach Request
(IMSI/PTIMSI)
NAS Security Setup
NAS Security Setup
Authentication
Request
Robot Location
Update
Authentication
Response
Attach Response
Robot User Plane
Control Plane
Session
Establishment
eNB
MME
S/P Gateway
HSS
IoT Anomaly
Detection
Figure 11.10 Robot authentication and sessions establishment.
