About: Hardware Platform Interface is a research topic. Over the lifetime, 10 publications have been published within this topic receiving 117 citations.
TL;DR: In this paper, a universal interface layer is configured such that a gaming platform is hardware platform independent and such that the hardware platform is gaming platform independent, which can facilitate the interchangeability of one platform without a corresponding need to modify the other platform.
Abstract: Gaming machines and systems having a universal interface layer linking a gaming platform to a hardware platform are disclosed. In particular, the universal interface layer is configured such that the gaming platform is hardware platform independent and such that the hardware platform is gaming platform independent. Platform independence can facilitate the interchangeability of one platform without a corresponding need to modify the other platform. The gaming platform can include various gaming modules and an operating system, while the universal interface layer can include firmware, various additional gaming modules, hardware specific drivers and various APIs to facilitate communication between the gaming platform and other universal interface layer components. A safe storage manager can be included to utilize a non-volatile storage component to store data regarding a gaming machine state, with the state being recoverable after a substantial interruption to the machine.
TL;DR: In this article, the authors describe a system for implementing the Hardware Platform Interface (HPI) specification for platform management of computer systems, which includes a user library, a resource program, a domain program and a bridge program.
Abstract: A computer program product and a system are provided for implementing the Hardware Platform Interface (HPI) specification for platform management of computer systems. Software, implemented by the computer program product includes a user library, a resource program, a domain program and a bridge program. The user library accepts calls from user application programs for accessing management data and management capabilities incorporated in a running instance of the resource program. The running instance of the resource program provides access to the management data and the management capabilities. This access is through restrictions to a set of running instances of the domain program. In addition, access to the user application programs is indirect through a set of running instances of the domain program. A running instance of the domain program provides access of a set of running instances of the resource program to a pre-defined set of user application programs, based on access restrictions defined for the domain program. The bridge program enables communication with remotely-connected computer systems.
TL;DR: In this article, the authors present an experimental evaluation of two approaches for Dependable Mobile Internet Services: OpenHPI: An Open Source Reference Implementation of the SA Forum Hardware Platform Interface and SA Forum Checkpoint and AMF Services.
Abstract: ISAS 2004- Architecture of Highly Available Databases- Data Persistence in Telecom Switches- Distributed Redundancy or Cluster Solution? An Experimental Evaluation of Two Approaches for Dependable Mobile Internet Services- OpenHPI: An Open Source Reference Implementation of the SA Forum Hardware Platform Interface- Quality of Service Control by Middleware- Benefit Evaluation of High-Availability Middleware- A Measurement Study of the Interplay Between Application Level Restart and Transport Protocol- Service-Level Management of Adaptive Distributed Network Applications- A Methodology on MPLS VPN Service Management with Resilience Constraints- Highly Available Location-Based Services in Mobile Environments- On Enhancing the Robustness of Commercial Operating Systems- A Modular Approach for Model-Based Dependability Evaluation of a Class of Systems- Rolling Upgrades for Continuous Services- First Experience of Conformance Testing an Application Interface Specification Implementation- On the Use of the SA Forum Checkpoint and AMF Services
TL;DR: OpenHPI is production ready reference implementation of the SA Forum HPI specification designed to be easy to setup and use, as well as utilize and compliment existing hardware management standards.
Abstract: OpenHPI is production ready reference implementation of the SA Forum HPI specification. It is designed to be easy to setup and use, as well as utilize and compliment existing hardware management standards. OpenHPI is available as open source so it can be easily productized by anyone requiring an HPI implementation for their hardware.
TL;DR: This paper tries to evaluate recent implementation of the only one open source AIS-compliant middleware, OpenAIS, to see whether it satisfies the critical needs of failure impact in many carrier-grade applications.
Abstract: The Service Availability Forum (SA Forum) was formed to foster an ecosystem as a building block for carrier-grade system development It published a series of high availability specifications, commonly referred to as Application Interface Specification (AIS) and Hardware Platform Interface (HPI) In this paper, we try to evaluate recent implementation of the only one open source AIS-compliant middleware, OpenAIS, to see whether it satisfies the critical needs of failure impact in many carrier-grade applications Our benchmark is conducted in two cases: processor leave and processor join, and evaluates several parameters crucial to the usefulness of the membership protocol The result shows good performance for both cases Finally we point out some possible directions to improve the worst-case time of OpenAIS