IoT Security 263
associated MVNO, it will be de‐authenticated, blacklisted and a blacklist will be updated
to all MVNOs and LRCs in the network. Afterwards, that malicious drone will not be
authenticated anymore to harm the services or network elements.
11.5.3 Robot Attack
Figure 11.12 shows robot attack scenarios, which were discussed in Section 11.4. The
attack detection considering the whole MVNO has been illustrated here. Consider there
are 3 drones; drone 2 is an attacker, whereas drone 1 and drone 3 are victims. Drone 1
and drone 2 are in one cell (cell 1) and belong to the same LRC, but drone 3 belongs to a
different cell (cell 2) and belongs to a different LRC. Drone 2 can attack in two ways:
1) drone 2 may either attack drone 1 directly using LRC; or
2) drone 2 may attack drone 3 indirectly via MVNO.
11.5.4 Robot Communication
There are three types of communication between robots:
1) Intra MVNO communication: a robot communicates to other robots inside its
MVNO;
2) Inter MVNO communication: a robot communicates to other robots inside other
MVNOs;
3) Roaming between MVNOs: a robot moves to different MVNOs and tries to communicate to other robots. As shown in the Figure 11.13, a robot has been arriving
earlier at a certain location and later has been physically moved to another location.
The authentication request will be to send the robot to the nearby LRC of the service
provider.
A robot sends a handover request through LRC and the source base station, for
example an evolved Node B (eNB) to an IoT anomaly detection module. If the received
data is safe, the IoT anomaly detection module will forward the request to a source MME.
Then a source MME sends the relocation request to a target MME, and a source
MME receives a relocation response. The source MME returns the handover response
to the source eNB, which then forwards the handover response to the robot through
LRC. The source eNB sends an eNB status transfer notification to source MME, which
indicates to source MME of the robot handover to target eNB. Target MME then
informs target eNB of an MME status transfer and a handover confirmation will then
be sent to the target eNB via LRC.
11.6 Conclusion
In this chapter, we reviewed 5G network features for machine type communication,
Internet of Things (IoT) services, IoT threats, mobile cloud robot security challenges
and finally proposed a distributed security platform for mobile cloud robots.
The proposed platform has two sections: robot section and mobile network section.
The robot section includes robots and Local Robot Controller (LRC). LRC is a central
associated MVNO, it will be de‐authenticated, blacklisted and a blacklist will be updated
to all MVNOs and LRCs in the network. Afterwards, that malicious drone will not be
authenticated anymore to harm the services or network elements.
11.5.3 Robot Attack
Figure 11.12 shows robot attack scenarios, which were discussed in Section 11.4. The
attack detection considering the whole MVNO has been illustrated here. Consider there
are 3 drones; drone 2 is an attacker, whereas drone 1 and drone 3 are victims. Drone 1
and drone 2 are in one cell (cell 1) and belong to the same LRC, but drone 3 belongs to a
different cell (cell 2) and belongs to a different LRC. Drone 2 can attack in two ways:
1) drone 2 may either attack drone 1 directly using LRC; or
2) drone 2 may attack drone 3 indirectly via MVNO.
11.5.4 Robot Communication
There are three types of communication between robots:
1) Intra MVNO communication: a robot communicates to other robots inside its
MVNO;
2) Inter MVNO communication: a robot communicates to other robots inside other
MVNOs;
3) Roaming between MVNOs: a robot moves to different MVNOs and tries to communicate to other robots. As shown in the Figure 11.13, a robot has been arriving
earlier at a certain location and later has been physically moved to another location.
The authentication request will be to send the robot to the nearby LRC of the service
provider.
A robot sends a handover request through LRC and the source base station, for
example an evolved Node B (eNB) to an IoT anomaly detection module. If the received
data is safe, the IoT anomaly detection module will forward the request to a source MME.
Then a source MME sends the relocation request to a target MME, and a source
MME receives a relocation response. The source MME returns the handover response
to the source eNB, which then forwards the handover response to the robot through
LRC. The source eNB sends an eNB status transfer notification to source MME, which
indicates to source MME of the robot handover to target eNB. Target MME then
informs target eNB of an MME status transfer and a handover confirmation will then
be sent to the target eNB via LRC.
11.6 Conclusion
In this chapter, we reviewed 5G network features for machine type communication,
Internet of Things (IoT) services, IoT threats, mobile cloud robot security challenges
and finally proposed a distributed security platform for mobile cloud robots.
The proposed platform has two sections: robot section and mobile network section.
The robot section includes robots and Local Robot Controller (LRC). LRC is a central