Content uploaded by Prem Singh Bist
Author content
All content in this area was uploaded by Prem Singh Bist on Feb 07, 2021
Content may be subject to copyright.
A preview of the PDF is not available
Thesis - Real Time Distributed Fleet Monitoring System ( MASTER OF TECHNOLOGY in Computer Science & Engineering)
Abstract and Figures
It is always the challenging task for every one when it comes to security. The companies depend heavily
on fleets to deliver product on time and in good condition. With existing company name on fleet, if any
driver has no complaint behavior, the company may fail to protect its brand value. It’s a huge concern for
the fleet serving companies to monitor different activities on going on the fleets across the different geographical location. How does a company would ensure that a driver is not recklessly driving when a fleet
collided with another fleet? Varieties of such other use cases are pertinent where a monitoring of fleet is
must in order to ensure the safety of people and assets.
The monitoring of fleet is all sound good, but real problem arises on handling of such large volume of data.
A single vehicle would capture at least one gigabyte of video data per day. If 100 vehicles are monitored,
they would need hundred gigabytes of storages per day. With traditional vertical system based servers, it is
extremely difficult and costly to manage such high volume of data. Furthermore, the cost for solution to
operate is far higher which is never possible for most the companies to afford for monitoring.
This dissertation entitled Real Time Distributed Fleet Monitoring System “RTDFMS” approaches on
research to effectively handle and manage such a large volume of data. It focuses on several of aspect of
parallel programming in distributed environment in order to make a system more reliable and horizontally
scalable which ultimately would reduce the overall cost of monitoring fleets in near real-time.
Figures - uploaded by Prem Singh Bist
Author content
All figure content in this area was uploaded by Prem Singh Bist
Content may be subject to copyright.
ResearchGate has not been able to resolve any citations for this publication.
In recent years, High Performance Computing (HPC) systems have been shifting from expensive massively parallel architectures to clusters of commodity PCs to take advantage of cost and performance benefits. Fault tolerance in such systems is a growing concern for long-running applications. In this paper, we briefly review the failure rates of HPC systems and also survey the fault tolerance approaches for HPC systems and issues with these approaches. Rollback-recovery techniques which are most often used for long-running applications on HPC clusters are discussed because they are widely used for long-running applications on HPC systems. Specifically, the feature requirements of rollback-recovery are discussed and a taxonomy is developed for over twenty popular checkpoint/restart solutions. The intent of this paper is to aid researchers in the domain as well as to facilitate development of new checkpointing solutions.
This paper presents a vehicular data acquisition and analysis system for fleet management automation. It exploits On-Board Diagnostic (OBD), GPS, RFID, and WiFi technologies. Although many systems currently integrate position tracking, OBD and wireless networking to allow for remote position tracking and remote diagnostic system, few systems provide the capability to automate the fleet management process. This paper describes a vehicle embedded data acquisition system places in vehicle as well as a database server and web interface for fleet management automation. This system design is based on wireless networking technology (WiFi), which does not need a base station to upload the collected data to a web server. Data collected in a database forms the basis for decision making, performance monitoring, remote diagnostics, and vehicle and driver performance optimization. The main parts of this system are in-vehicle embedded system, and vehicle monitor server and database. The in-vehicle embedded system obtains the location of the vehicle from GPS receiver, the vehicle status from OBD interface, and the driver ID from the RFID. Then the in-vehicle embedded system connects the vehicle to web server through WiFI network to transmit the collected data when vehicle return to the parking place. Besides the reliability and cost effectiveness of this system, it also can be exploited for inter-vehicle communication and traffic monitoring.
Immortal DB is a transaction time database system that is built into a commercial database system rather than being layered on top. This enables it to have performance that is very close to the performance of an unversioned current time database system. Achieving such competitive performance is essential for wide acceptance of this temporal functionality. In this paper we describe further performance improvements in two critical dimensions. First Immortal DB range search performance is improved for current time data via improved current version storage utilization, making this performance essentially the same as unversioned performance. Second, Immortal DB update performance is increased by further reducing the cost for the timestamping of versions. Finally, we show how a simple modification, integrated into the timestamping mechanism, can provide a foundation for auditing database activity. Our algorithms have been incorporated into a commercial database engine and experiments using this database engine demonstrate the effectiveness of our approach.
By software fault tolerance in the application layer, we mean a set of application level software components to detect and recover from faults that are not handled in the hardware or operating system layers of a computer system. We consider those faults that cause an application process to crash or hang; they include application software faults as well as faults in the underlying hardware and operating system layers if they are undetected in those layers. We define four levels of software fault tolerance based on availability and data consistency of an application in the presence of such faults. We describe three reusable software components that provide up to the third level of software fault tolerance. Those components perform automatic detection and restart of failed processes, periodic checkpointing and recovery of critical volatile data, and replication and synchronization of persistent data in an application software system. These components have been ported to a numbe...
Heterogeneous parallel computing applications often process large data sets that require multiple GPUs to jointly meet their needs for physical memory capacity and compute throughput. However, the lack of high-level abstractions in previous heterogeneous parallel programming models force programmers to resort to multiple code versions, complex data copy steps and synchronization schemes when exchanging data between multiple GPU devices, which results in high software development cost, poor maintainability, and even poor performance. This paper describes the HPE runtime system, and the associated architecture support, which enables a simple, efficient programming interface for exchanging data between multiple GPUs through either interconnects or cross-node network interfaces. The runtime and architecture support presented in this paper can also be used to support other types of accelerators. We show that the simplified programming interface reduces programming complexity. The research presented in this paper started in 2009. It has been implemented and tested extensively in several generations of HPE runtime systems as well as adopted into the NVIDIA GPU hardware and drivers for CUDA 4.0 and beyond since 2011. The availability of real hardware that support key HPE features gives rise to a rare opportunity for studying the effectiveness of the hardware support by running important benchmarks on real runtime and hardware. Experimental results show that in a exemplar heterogeneous system, peer DMA and double-buffering, pinned buffers, and software techniques can improve the inter-accelerator data communication bandwidth by 2 . They can also improve the execution speed by 1.6
Fleet management is an important topic in research and development nowadays. Companies, security and emergency forces need to keep track of their trucks and cars and know where a vehicle is at a moment in time, and when, where and for how long a vehicle stopped. In this paper, a system for automating fleet management systems is described. The hardware of our system is a microprocessor-based embedded system. The software consists of firmware embedded in the hardware in addition to remote high-level software that keeps track of the position of the units and prepares reports to be sent to the customers. The system is currently operational in a couple of Arab countries. More than 2000 units are currently operational in a variety of modes that are described in the paper. The paper also contains suggestions for future research based on the accomplishments reported here.
This paper presents a prototype computer system that supports FMEA on the Internet. The general procedure of applying the web-based FMEA is as follows. The user, whether in Hong Kong or Mainland China or other parts of the world, uses the web browser to connect the client machine to the FMEA web server which may be located in Hong Kong headquarters or at manufacturing plants in Mainland China. Once connected, the user follows the system instructions and enters the necessary inputs on the appropriate web pages. The inputted data are analysed locally by the client machines or sent to the server for relevant processing. Both inputted data and derived data are stored in a database which may reside in the client machine or the FMEA web server or another networked database server. Hard copies of relevant documents may be generated and printed out as necessary according to the client requests.
We propose a small number of basic concepts that can be used to explain the architecture of fault-tolerant distributed systems and we discuss a list of architectural issues that we find useful to consider when designing or examining such systems. For each issue we present known solutions and design alternatives, we discuss their relative merits and we give examples of systems which adopt one approach or the other. The aim is to introduce some order in the complex discipline of designing and understanding fault-tolerant distributed systems. 1 1 Introduction Computing systems consist of a multitude of hardware and software components that are bound to fail eventually. In many systems, such component failures can lead to unanticipated, potentially disruptive failure behavior and to service unavailability. Some systems are designed to be fault-tolerant: they either exhibit a well-defined failure behavior when components fail or mask component failures to users, that is, continue t...