Abstract: This disclosure describes a pickup location determination system that determines a pickup location for a received transportation request by filtering out door points based on various factors and by utilizing a pickup location model to select a pickup location from the filtered door points. For example, the disclosed systems generate door points relative to intersection points within a request radius of a request location associated with a received transportation request. The disclosed systems generate potential pickup locations by filtering out door points that are impractical and/or inefficient based on proximity to other door points, locations relative to venues, locations relative to side streets, and/or locations between parallel road segments (e.g., medians). The disclosed systems further utilize a pickup location model to select a pickup location from the potential pickup locations.

Abstract: A storage device is divided into a trusted storage region (TSR) and a standard storage region (SSR). A backup and recovery tool (BRT) is used to generate a public/private key pair and provide the public key to the storage device. The BRT detects a trigger to back up a file from the SSR to the TSR and sends a write instruction to the storage device to perform the backup. The BRT signs the write instruction with the private key. The storage device uses the public key to verify the write instruction and performs the backup based on the verification. The TSR cannot be accessed without the private key, therefore if a malware attack is detected in the storage device, the device may be formatted to delete infected files. A fresh operating system may be installed on the formatted storage device and the file may be recovered from the TSR.

Abstract: A storage device is divided into a trusted storage region (TSR) and a standard storage region (SSR). A backup and recovery tool (BRT) is used to generate a public/private key pair and provide the public key to the storage device. The BRT detects a trigger to back up a file from the SSR to the TSR and sends a write instruction to the storage device to perform the backup. The BRT signs the write instruction with the private key. The storage device uses the public key to verify the write instruction and performs the backup based on the verification. The TSR cannot be accessed without the private key, therefore if a malware attack is detected in the storage device, the device may be formatted to delete infected files. A fresh operating system may be installed on the formatted storage device and the file may be recovered from the TSR.

Abstract: This invention relates to composite backing materials (e.g., polymer impregnated nonwoven fabrics) and coated abrasive articles that include such composite backing materials. This invention also relates to methods of making and using said composite backing materials and coated abrasive articles. The claimed processes and systems related to the use and manufacturing of coated abrasive articles are improved and cost effective.

Abstract: This invention relates to composite backing materials (e.g., polymer impregnated nonwoven fabrics) and coated abrasive articles that include such composite backing materials. This invention also relates to methods of making and using said composite backing materials and coated abrasive articles. The claimed processes and systems related to the use and manufacturing of coated abrasive articles are improved and cost effective.

Abstract: Method and apparatus relating to building distributed fault-tolerant/high-availability computer applications are described. In an embodiment, a system may include an application, a router, and an update module. The application may execute a process in a pure distributed mode, a pure fault tolerant mode, or a distributed fault tolerant mode. The router may route communications between the application and another application independent of location of the applications. The update module may provide distributed functionality in the application. Other embodiments are also disclosed.

Abstract: Software architecture for developing distributed fault-tolerant systems independent of the underlying hardware architecture and operating system. Systems built using architecture components are scalable and allow a set of computer applications to operate in fault-tolerant/high-availability mode, distributed processing mode, or many possible combinations of distributed and fault-tolerant modes in the same system without any modification to the architecture components. The software architecture defines system components that are modular and address problems in present systems. The architecture uses a System Controller, which controls system activation, initial load distribution, fault recovery, load redistribution, and system topology, and implements system maintenance procedures. An Application Distributed Fault-Tolerant/High-Availability Support Module (ADSM) enables an applications( ) to operate in various distributed fault-tolerant modes.