Abstract: A reader element is associated with an identity verification element. The reader element has a biometric input device and is configured, through enrollment of a biometric element is used to encrypt a character sequence associated with the identity verification element. In a verification phase subsequent to the enrollment, a user may be spared a step of providing the character sequence by, instead, providing the biometric element. Responsive to receiving the biometric element, the reader element may decrypt the character sequence and provide the character sequence to the identity verification element.

Abstract: A handle assembly comprises a handle (110) on one side of a vehicle tailgate liftglass (120). The handle (110) is connected to a shaft member (150) that passes through a hole (140) in the liftglass (120). A motor (200) pivots the assembly into either a closed position, in which the handle (110) lies adjacent to the liftglass (120), or an open position, FIG. 2, in which a gap (210) is left between the handle (110) and the liftglass (120) into which the user may place his hand in order to pull the handle (110) or push the liftglass (120). Preferably there is a resilient element between the motor and the handle.

Abstract: A user interface manager acts to cache state information and thread information provided to it by user interface modules, before the user interface modules cease execution. When a new user interface module commences execution, or the old user interface module recommences execution, the user interface module may request, from the user interface manager, the cached state information and thread information.

Abstract: A user interface manager, interposed between a Windows service and user interface modules that communicate with the Windows service in distinct system status scenarios, can record interaction between the Windows service and each of the user interface modules. The recorded interaction, along with information collected from the user interface modules, can be used in conjunction so that user interaction with a first one of the user interface modules may continue with a second one of the user interface modules after a switch from one system status (e.g., logged on) to another system status (e.g., locked). Alternatively, responsive to the switch from one system status to another system status the user interface manager may simply stop the executing user interface module so that the interaction may be started over in the new system status.