Current mobile devices (e.g., smartphones) are equipped with several sensors that allow different forms of userinteraction. They also offer several connectivity options and a growing computing power which supports itsuse in new Human Computer Interaction (HCI) scenarios. This paper presents the mobileWheel, a system thatexploits the capabilities of current mobile devices as a means of interaction with a real-time graphical drivingsimulation running on a desktop computer. The application on the mobile device performs data acquisitionfrom various sensors (focusing on the 3D accelerometer) and also provides different types of feedback tothe user. This system represents a ubiquitous, simple and affordable alternative approach to the traditionalcontrol of virtual vehicles in driving simulators and could also be applied in other similar architectures. Toevaluate and validate this approach several tests were conducted with volunteer users. The control mode wherethe virtual vehicle is fully controlled by the accelerometer had the highest acceptance and produced the bestresults.

Virtual CPEs address the low agility, slow time-to-market and high costs (of development, deployment and support) that are inheritable to traditional CPEs. They take advantage of the economics of Cloud Computing and the ability to run Virtual Network Functions in a general computing platform to build richer services, with faster development and deployment times, all whilst reducing costs. When coupled together with Service Function Chaining and the ability to build/enter chains dynamically, an opportunity arises to enhance this system by making the whole vCPE's functionality policy-driven. We will start by constructing the vCPE within an OpenSource cloud platform (OpenStack), which will have dynamic SFC capablities added through own extensions. Then we will make the traffic classification through a DPI (ntop's nDPI), which will mark flows according to a configurable policy (REST interface) that will determine which service chain that flow must follow. Some virtual functions within a chain may trigger events (such as reaching the traffic quota for a certain service), being the policy immediately enforced at the VNFs and an on-the-fly policy change possible through the REST interface (for instance, change the throttle amount to a given application traffic). A live Proof-of-Concept was made which allowed real devices to connect to the vCPE

The fact that most IoT solutions are provided by 3rd-parties, along with the pervasiveness of the collected data, raises privacy and security concerns. There is a need to verify which data is being sent to the 3rd-party, as well as preventing those channels from becoming an exploitation avenue. We propose to use existing API definition languages to create contracts which define the data that can be transmitted, in what format, and with which constraints. To verify the compliance with these contracts, we propose a converging "Multi-Access Edge Computing" architecture which validates RESTalike API requests/responses against a Swagger schema. We deal with encrypted traffic using an SFC-enabled Man-in-the-Middle, allowing us to do verifications in "real-time". We devised a Proof of Concept and shown that we were able to detect (and stop) contract violations.

The fact that most IoT solutions are provided by third parties, along with the pervasiveness of the collected data, raises privacy and security concerns. There is a need to verify which data is being sent to the third party, as well as preventing those channels from becoming an exploitation avenue. We propose to use existing API definition languages to create contracts which define the data that can be transmitted, their format and constraints. To verify the compliance with these contracts, we propose a Network Service architecture which validates REST-like API requests/responses against a Swagger schema. We deal with encrypted traffic using an Service Function Chaining (SFC)-enabled Man-in-the-Middle (MITM), allowing verifications in “real-time.” We devised a Proof of Concept and showed that we were able to detect (and stop) contract violations.

Network slicing emerges as a key technology in next generation networks, boosted by the integration of software‐defined networking and network functions virtualization. However, while allowing resource sharing among multiple tenants, such networks must also ensure the security requirements needed for the scenarios they are employed. This letter presents the leading security challenges on the use of network slices at the packet core, the solutions that academy and industry are proposing to address them, pointing out some directions that should be considered.

In this paper, we propose an architecture based on NFV and SDN which allows to balance traffic analysis techniques using a Classifier. It steers flows to the appropriate Service Function Chaining (to open traffic or not) according to network requirements (such as, effectiveness, flexibility, scalability, performance, and privacy). The SSL/TLS traffic processing is carried-out by the centerpiece of this work, the SFC-enabled MITM. A Proof-of-Concept was conducted (focusing on our SFC-enabled MITM) which showed that functionalities lost due to encryption (Content Optimization, Caching, Network Anti-virus, and Content Filter) were recovered when processing opened traffic within its Service Function Chains. We also evaluated its impact on performance. The results show that cipher suite overhead plays a role but can be mitigated, the Classifier can alleviate the performance overhead of different traffic analysis techniques, network functions have lower impact to performance, and Service Function Chaining length influences page load time.

Submitted by phemiran@stj.jus.br (phemiran@stj.jus.br) on 2022-03-09T19:13:41Z No. of bitstreams: 2 estudo_comparado_plea_cunha.pdf: 2448972 bytes, checksum: 18b25b3a4024e322f143186dd5081c45 (MD5) license.txt: 1239 bytes, checksum: c9b4c351324448672315a00808efb725 (MD5)

The studies that address the front-end of innovation diverge regarding its core phases. To cope with this issue, this study analysed models in the literature to identify its core phases. The results showed three predominant phases : opportunity identification, concept generation and project definition. This fact represents a first step towards the alignment of models of the front-end of innovation.