A Case Study on the Deployment of a Tactile Internet Application in a Hybrid Cloud, Edge, and Mobile Ad Hoc Cloud Environment

2021 ◽  
pp. 1-12
Author(s):  
Yassine Jebbar ◽  
Nattakorn Promwongsa ◽  
Fatna Belqasmi ◽  
Roch H. Glitho
Keyword(s):  
Ad Hoc ◽  
Hybrid Cloud ◽  
Cloud Environment ◽  
Internet Application ◽  
Mobile Ad Hoc

scholarly journals How to Achieve Compliance with GDPR Article 17 in a Hybrid Cloud Environment

Sci ◽  
2020 ◽  
Vol 2 (2) ◽  
pp. 22
Author(s):  
Miriam Kelly ◽  
Eoghan Furey ◽  
Kevin Curran
Keyword(s):  
Ad Hoc ◽  
Data Repository ◽  
Hybrid Cloud ◽  
Cloud Environment ◽  
Cloud Infrastructure ◽  
General Data Protection Regulation ◽  
Right To Be Forgotten ◽  
Personally Identifiable Information ◽  
General Data ◽  
The Right

On 25 May 2018, the General Data Protection Regulation (GDPR)Article 17, the Right to Erasure (‘Right to be Forgotten’) came into force making it vital for organisations to identify, locate and delete all Personally Identifiable Information (PII) where a valid request is received from a data subject to erase their PII and the contractual period has expired. This must be done without undue delay and the organisation must be able to demonstrate reasonable measures were taken. Failure to comply may incur significant fines, not to mention impact to reputation. Many organisations do not understand their data, and the complexity of a hybrid cloud infrastructure means they do not have the resources to undertake this task. The variety of available tools are quite often unsuitable as they involve restructuring so there is one centralised data repository. This research aims to demonstrate compliance with GDPR’s Article 17 Right to Erasure (‘Right to be Forgotten’) is achievable in a Hybrid cloud environment by following a list of recommendations. However, 100% retrieval, 100% of time will not be possible, but we show that small organisations running an ad-hoc Hybrid cloud environment can demonstrate that reasonable measures were taken to be Right to Erasure (‘Right to be Forgotten’) compliant.

scholarly journals How to Achieve Compliance with GDPR Article 17 in a Hybrid Cloud Environment

Sci ◽  
2021 ◽  
Vol 3 (1) ◽  
pp. 3
Author(s):  
Miriam Kelly ◽  
Eoghan Furey ◽  
Kevin Curran
Keyword(s):  
Ad Hoc ◽  
Data Repository ◽  
Hybrid Cloud ◽  
Cloud Environment ◽  
Cloud Infrastructure ◽  
General Data Protection Regulation ◽  
Right To Be Forgotten ◽  
Personally Identifiable Information ◽  
General Data ◽  
The Right

On 25 May 2018, the General Data Protection Regulation (GDPR) Article 17, the Right to Erasure (“Right to be Forgotten”) came into force, making it vital for organisations to identify, locate and delete all Personally Identifiable Information (PII) where a valid request is received from a data subject to erase their PII and the contractual period has expired. This must be done without undue delay and the organisation must be able to demonstrate that reasonable measures were taken. Failure to comply may incur significant fines, not to mention impact to reputation. Many organisations do not understand their data, and the complexity of a hybrid cloud infrastructure means they do not have the resources to undertake this task. The variety of available tools are quite often unsuitable as they involve restructuring so there is one centralised data repository. This research aims to demonstrate that compliance with GDPR’s Article 17 Right to Erasure (“Right to be Forgotten”) is achievable in a hybrid cloud environment by following a list of recommendations. However, full retrieval, all of the time will not be possible, but we show that small organisations running an ad-hoc hybrid cloud environment can demonstrate that reasonable measures were taken to be Right to Erasure (“Right to be Forgotten”) compliant.

scholarly journals Evaluasi Kinerja Protokol Perutean AODV dan SDGR+R pada VANET dengan Studi Kasus Pelabuhan Lembar

2020 ◽  
Vol 2 (1) ◽  
pp. 59-67
Author(s):  
Valian Yoga Pudya Ardhana ◽  
Esther Sanda Manapa ◽  
Tommy Wijaya Sagala ◽  
Yonathan Anggian Sihaan ◽  
Eliyah Acantha M Sampetoding
Keyword(s):  
Routing Protocol ◽  
Ad Hoc Network ◽  
Ad Hoc ◽  
Data Communication ◽  
Port Area ◽  
Packet Data ◽  
Mobile Ad Hoc ◽  
Hoc Networks ◽  
Better Than

The Vehicular ad-hoc Network (VANET) is a subclass of Mobile ad-hoc networks (MANETs).VANET is a wireless network created from the concept of building a vehicle network (node) toexchange data information (data communication). There is a new concept technique forVANET communication used, namely the use of the concept of Software Defined Network(SDN) on VANET. For data communication between vehicles, a routing protocol required. Themost common routing protocol used on VANET since 2003 is AODV. In 2014 several studieswere using the SDN paradigm tried on VANET technology to improve the performance ofQuality of Service (QoS), one of which is a Geographic-based SDN, called SDGR in 2016.Multicast is a method of routing data on a network that allows one node or a group of nodes tocommunicate efficiently with the receiving node. The multicast concept supports one-to-manyrouting in nodes that send packet data to a group of nodes. The development of the SDGRrouting protocol using the idea of multicast technique to SDGR based on the Direction calledSDGR + R carried out in 2019. This study uses a case study of vehicle transportationsimulations in the Lamber Port area of Lombok. The simulation results knew that SDGR + Ris better than AODV in terms of service quality (QoS) at a latency of 15.58% and packet deliveryratio (PDR) of 47.78%.

Sign in / Sign up

Export Citation Format

Share Document