Abstract: A mechanism for allowing a user to prove their identity on touch-based devices employing the use of a touch surface in firmware-controlled environments is discussed. The user may prove his or her identity by entering a series of strokes on the touch-based device to form a word or image. Characteristics of the entered strokes such as stroke order and stroke direction are compared to stored stroke characteristics that were gathered from a drawing of the same word or image during a user enrollment process. If the stroke characteristics comparison is acceptable, the user identity is verified.

Abstract: This application describes compounds and methods that can inhibit Scavenger receptor class B, type I (SR-BI) activity, which compounds and methods can used, for example, to mediate high-density lipoprotein (HDL) lipid uptake and treat hepatitis C viral infections.

Abstract: Disclosed are compounds that can be used for treating tuberculosis.

Abstract: Disclosed are compounds, such as pyridazinones, that can be, inter alia, used for treating cancer.

Abstract: A mechanism for firmware to gain control from the operating system of an Advanced Configuration and Power Interface (ACPI)-compliant computing device during sleep-state transitions even if the computing device lacks a dedicated means for such a change to occur is discussed. Embodiments of the present invention report a CPU-only reset register in place of a sleep control register for an ACPI-compliant computing device in which an operating system is attempting a sleep-state transition. A CPU reset value is substituted for a sleep type value in a sleep-state object and written to the CPU-only reset register that was reported instead of the sleep control register thereby triggering a CPU-only reset. Firmware code operating at a known CPU reset vector may perform specified processing and then authorize a transition to the originally requested sleep-state.

Abstract: A specialized boot path for speeding up resume from a sleep state is discussed. In a UEFI-compliant system, a specially constructed alternate firmware volume is created which contains only the code modules used during resumption from an S3 sleep state. This alternate firmware volume is copied into Random Access Memory (RAM) during a normal boot. When the system subsequently enters the S3 sleep state and then begins the resume boot process, code in the boot sequence detects it is a resume from an S3 sleep state, restores a RAM configuration and jumps execution to a Pre-EFI Initialization (PEI) core entry point in the alternate firmware volume in RAM instead of to a firmware volume in ROM. This alternate firmware volume performs specified S3 resume tasks and then returns control to the operating system.

Abstract: Techniques for firmware providing a simulated system management mode (SMM) while being executed by a non-x86 platform, such as an ARM platform. In response to receiving a service call from an OS interface driver, the firmware may determine a requested service identified by the service call. Thereafter, the firmware may identify an appropriate service handler to perform the requested service. After the appropriate service handler performs the requested service, the appropriate service handler notifies the OS interface driver. Since the SMM is emulated by the firmware, the firmware may execute on an x86 platform or a non-x86 platform, such as an ARM platform.

Abstract: A system for identifying users and controlling access to a radiotherapy apparatus, comprising: a portable identification device, comprising a memory for storing identification information corresponding to a user of the device and an antenna; and a control mechanism for a radiotherapy apparatus, comprising: a wireless transceiver for communicating with the portable identification device and identifying the user of the portable identification device; and a display for displaying a user interface and receiving inputs for controlling the radiotherapy apparatus on the basis of the identified user when the portable identification device is placed on the display.

Abstract: A technique for improving application window displays in a multi-window graphical user interface in a touch-based computing device is discussed. By selecting an application window or corresponding thumbnail icon in a multi-window graphical user interface using a finger touch and dragging the application window or icon to an edge of the screen indicated by another finger, the edge of the selected application window may be automatically aligned with respect to that screen edge. Additionally, already open application windows may be automatically re-sized and re-positioned to accommodate the newly re-sized application window.

Abstract: Techniques for determining whether firmware should trust an application sufficiently so as to provide a service to the application. Firmware, executing on a device, receives an indication that an application, also executing on the device, is requesting a service provided by the firmware. The firmware obtains (a) an operating system signature associated with the application and (b) a firmware signature associated with the application. The operating system signature is a signature that is used by the operating system, executing on the device, to authenticate the application, while the firmware signature is a signature that is used by the firmware to authenticate the application. If the firmware determines that the operating system signature matches the firmware signature, then the firmware storing trust data that permits the application to access the service provided by the firmware. The firmware need not calculate a signature based on the in-memory image of the application.

Abstract: A specialized boot path for speeding up resume from a sleep state is discussed. In a UEFI-compliant system, a specially constructed alternate firmware volume is created which contains only the code modules used during resumption from an S3 sleep state. This alternate firmware volume is copied into Random Access Memory (RAM) during a normal boot. When the system subsequently enters the S3 sleep state and then begins the resume boot process, code in the boot sequence detects it is a resume from an S3 sleep state, restores a RAM configuration and jumps execution to a Pre-EFI Initialization (PEI) core entry point in the alternate firmware volume in RAM instead of to a firmware volume in ROM. This alternate firmware volume performs specified S3 resume tasks and then returns control to the operating system.

Abstract: A method of identifying compounds as direct inhibitors of Keap1-Nrf2 interaction through high-throughput screening and lead development. The direct inhibitors of Keap1-Nrf2 interaction are more specific and free of various undesirable effects than existing indirect inhibitors, and are potential drug candidates of chemopreventive and therapeutic agents for treatment of various diseases or conditions involving oxidative stress and/or inflammation, including but not limited to cancers, diabetes, Alzheimer's, and Parkinson's. Novel compounds are identified and methods of preventing or treating diseases or conditions related to Keap1-Nrf2 interaction activity by use of the novel compounds identified or compositions containing such compounds are also disclosed.

Abstract: In example methods and systems described, a medical device can store information locally and in a separate database on a server, for example. If the device fails, or a patient is moved to a second device, information may be transferred to the second device such that the second device can resume a complex therapy at a point where the initial medical device left off. The data necessary to restart the complex therapy system may include certain underlying patient-specific parameters according to a model capturing the patient's physiological response to the medication in question. As a result, it is not necessary for the second device to restart the complex therapy or regress to an initial set of baseline assumptions.

Abstract: The present invention relates to a drug delivery device for setting and dispensing of a dose of a medicament is presented comprising a housing to accommodate a cartridge filled with the medicament, an electrically operated drive mechanism to be operably engaged with the cartridge to expel a predefined dose of the medicament from the cartridge, and at least one dose element displaceably arranged relative to the housing to set and/or to dispense the dose of the medicament, wherein the dose element and the drive mechanism are mechanically decoupled from each other.

Abstract: A mechanism for firmware to gain control from the operating system of an Advanced Configuration and Power Interface (ACPI)-compliant computing device during sleep-state transitions even if the computing device lacks a dedicated means for such a change to occur is discussed. Embodiments of the present invention report a CPU-only reset register in place of a sleep control register for an ACPI-compliant computing device in which an operating system is attempting a sleep-state transition. A CPU reset value is substituted for a sleep type value in a sleep-state object and written to the CPU-only reset register that was reported instead of the sleep control register thereby triggering a CPU-only reset. Firmware code operating at a known CPU reset vector may perform specified processing and then authorize a transition to the originally requested sleep-state.

Abstract: A mechanism for allowing a user to prove their identity on touch-based devices employing the use of a touch surface in firmware-controlled environments is discussed. The user may prove his or her identity by entering a series of strokes on the touch-based device to form a word or image. Characteristics of the entered strokes such as stroke order and stroke direction are compared to stored stroke characteristics that were gathered from a drawing of the same word or image during a user enrollment process. If the stroke characteristics comparison is acceptable, the user identity is verified.

Abstract: A system for reducing the risk of an incorrect selection or dispensing of a drug dose for use with a cartridge and a cartridge holder so as to prevent unwanted reservoir cross use. The coding system for use with the drug delivery device includes a first partial code feature and a second partial code feature. The first partial code feature and the second partial code feature cooperate to supply a combined visual indicator when the cartridge is assembled to the holder for indicating that a correct cartridge has been assembled to the holder.

Abstract: Techniques for firmware providing a simulated system management mode (SMM) while being executed by a non-x86 platform, such as an ARM platform. In response to receiving a service call from an OS interface driver, the firmware may determine a requested service identified by the service call. Thereafter, the firmware may identify an appropriate service handler to perform the requested service. After the appropriate service handler performs the requested service, the appropriate service handler notifies the OS interface driver. Since the SMM is emulated by the firmware, the firmware may execute on an x86 platform or a non-x86 platform, such as an ARM platform.

Abstract: Techniques for determining whether firmware should trust an application sufficiently so as to provide a service to the application. Firmware, executing on a device, receives an indication that an application, also executing on the device, is requesting a service provided by the firmware. The firmware obtains (a) an operating system signature associated with the application and (b) a firmware signature associated with the application. The operating system signature is a signature that is used by the operating system, executing on the device, to authenticate the application, while the firmware signature is a signature that is used by the firmware to authenticate the application. If the firmware determines that the operating system signature matches the firmware signature, then the firmware storing trust data that permits the application to access the service provided by the firmware. The firmware need not calculate a signature based on the in-memory image of the application.