Question

Write an application case study with network design diagram including the following topics: - IoT - Bluetooth - Fog Computing - Redundant - Resilient and measures of resilience - Troubleshooting with half split and move method Highlight in bold each of the above keywords.

Answer 1

IOT

The Tesla IoT Car: Case Study

MITCNC, the MIT Club of Northern California, is the regional alumni club of Massachusetts Institute of Technology in Northern California. They have a blog at https://blogmitcnc.org/ where they post on emerging trends and discoveries in science and technology. Displaying their best Car & Driver reviewer, while keeping their propeller hats on to look at IoT, data, privacy and security, this is a unique look at the most talked about car this century.

Bluetooth

The 2017 release of the Bluetooth® mesh specifications have paved the way for the emergence of connected lighting as the key use case in building automation. One of the driving forces behind the momentum in connected lighting is the added benefit of leveraging that same Bluetooth wireless lighting grid as a platform for additional services.

According to ABI Research, by 2021, 40% of all connected end points will be smart lighting based. In fact, retail, healthcare, airports, and museums are all early case studies for implementing this technology and have become proving grounds for the capabilities of Bluetooth technology in the smart building.

Fog Computing

Internet of Things technology provides a competent and structured approach to improve health and wellbeing of

mankind. One of the feasible ways to offer healthcare services based on IoT is to monitor humans health in real-time using ubiquitous health monitoring systems which have the ability to acquire bio-signals from sensor nodes and send the data to the gateway via a particular wireless communication protocol. The real-time data is then transmitted to a remote cloud server for real-time processing, visualization, and diagnosis. In this paper, we enhance such a health monitoring system by exploiting the concept of fog computing at smart gateways providing advanced techniques and services such as embedded data mining, distributed storage, and notification service at the edge of net- work. Particularly, we choose Electrocardiogram (ECG) feature extraction as the case study as it plays an important role in diagnosis of many cardiac diseases. ECG signals are analyzed in smart gateways with features extracted including heart rate, P wave and T wave via a flexible template based on a lightweight wavelet transform mechanism. Our experimental results reveal that fog computing helps achieving more than 90% bandwidth efficiency and offering low-latency real time response at the edge of the network

Resiliency and redundancy

In the domain of computer networking, resilience and redundancy establish fault tolerance within a system, allowing it to remain functional despite the occurrence of issues such as power outage, cyber-attacks, system overload, and other causes of downtime. In this context, the terms can be defined as follows:

• Redundancy is the intentional duplication of system components in order to increase a system’s dependability.
• Resilience refers to a system’s ability to recover from a fault and maintain persistency of service dependability in the face of faults.

With these definitions, redundancy and resilience are not interchangeable but complementary: Redundancy is required to enhance a system’s resilience, and resilience of individual system components ensures that redundant components can recover to functional state following a fault occurrence. Redundancy is an absolute measure of the additional components supporting system resilience, whereas resiliency is a relative (and continuous) measure of the impact of fault on the system operation.

Troubleshooting with half split

A split-half search is a technique for systematically isolating the source of an issue. You start by eliminating roughly half of the items you are checking, then trying to re-create the issue. You continue halving your search group until you find the source of the issue. A split-half search requires applying your knowledge of the product, its common issues, and the symptoms as you check one possible cause after another, in a logical order.

This part of the troubleshooting process can be the most difficult and the most time-consuming. That's why a logical and methodical plan is so important. We've found that the following order has been effective:

1. User errors. Check for user errors in the course of gathering information, duplicating the issue, and trying quick fixes. But keep in mind the possibility of incorrectly set switches or preferences, incompatible equipment, and incorrect assumptions on the user's part; take nothing for granted.

2. Software-related issues. Software that is unusable or that doesn't work with other software, viruses, extension conflicts, duplicate System folders, and other software issues can cause symptoms that may look like hardware issues. But replacing hardware won't solve these problems, and it wastes time and money, so always check for software issues before replacing any hardware. MacTest Pro system software tests can detect and repair many software issues of this type. Remember that you must check applications and the Mac OS.

3. Software viruses. As you most likely know, a virus is a program that replicates itself and often modifies other programs. When a virus gets into system software, the computer may not start up, the system may stop responding, or the software may work incorrectly. (It may be helpful to define this for a customer who really isn't sure why a virus could be such a big issue.) Although Macintosh computers are less likely to become infected with viruses than computers running other operating systems, it is still possible to get a virus on a Mac. Email attachments and other files downloaded from the Internet are common sources of virus infection.

   To check for a virus, ask customers these questions:
   • Did you recently receive software from another user or a common source and add the software to your system?
   • Did you experience the issue before you obtained the software?
   • Did you share this file with others? Are they having similar issues?

   You can find up-to-date virus information on the Internet at a variety of locations. Third-party virus utilities such as McAfee Virex (www.networkassociates.com) can check systems and remove viruses from them. Virex is available as a free download to all .Mac subscribers.

   If you do detect a virus, make sure you find the original source file and delete it. Then reinstall all affected system and application software, and dispose of any unusable data files.

4. Hardware issues. When you are convinced that user error, a virus, or other software has not caused the issue, hardware is what is left. Here are some tips:

   • Simplify the issue. Remove external devices and internal cards (except the video card, if needed for display) and test the main unit alone. If the issue remains, you have isolated it to the computer itself. If the issue disappears, reinstall the cards and peripherals one by one, until the symptoms reappear. When they do, you have found the culprit—or at least a clue.
   • If the system can be tested with AHT, do so. This can often save you considerable time when checking for hardware issues.
   • Find the “problem space.” Try to identify the functional area—sometimes called a problem space—that the issue affects. For instance, the general functional areas for a typical Mac could be considered software, logic and control, memory, video, input/output (I/O), and power.