Microsoft Technology Licensing, LLC

Intel Corporation

Boaz Ein-Gil

Shira Weinberg

Shimi Ezra

Mikael Sitruk

Nir Nice

Jiahe Helen Wang

Ron Mondri

Omri Mendels

Oren Trutner

Tomer Shiran

Opher Dubrovsky

Uri Ben-Zew

Adi Kurtz

Adina Hagege

Alex Rapoport

Keren Goltz

Linda Lior

Technology for interoperability is disclosed by enabling the sharing of user context or preferences for a computing experience across computing devices, operating systems, applications, or locations. A platform and application programming interface (API) are provided for computer applications and services to store and retrieve context data associated with a computing experience. Access to the context data for sharing may be managed by an access controller, which enables a user to manage access permissions for the sharing of the context data. The context data may be defined according to a common schema, which specifies the information for sharing and may be communicated using common communication channels or protocols. Thus context data may be shared across nearly any application or service including those developed in different computer programming languages or operating on different types of computing devices or devices running different operating systems or by different software developers.

Sharing user context and preferences

A system for filtering device information to be provided to a user by a digital device or system according to physiological information collected from the user. The physiological information may be used to determine the user's present cognitive stress, wherein the device information may be prioritized, withheld, delayed, or deleted if the present cognitive stress exceeds a predetermined threshold. The device information may be further evaluated with contextual information such as different aspects of the device information or non-physiological user information (e.g. location, time of the day). The system may manage device information with minimal or less user interaction than user defined rule systems.

User-stress based notification system

A single passcode can be used for validation by a user of several entities in a system without compromising security. The source of the entity providing validation credentials, along with the passcode, is considered when determining validity. A one-time password system validates credentials if a validation credentials, such as a user's valid passcode and the source of the credentials, have not been used previously. In a one-time passcode system, a validation processor receives validation credentials from a client processor. If the client processor has not previously sent the validation credentials to the validation processor, and the credentials are valid, the validation processor will validate the credentials. Otherwise, the credentials are invalid. Other client processors can utilize the same passcode and their respective source identifiers, and as long as the other client processors have not previously utilized the credentials, the credentials are declared valid.

One-time password validation in a multi-entity environment

An exemplary computer-implementable method () transforms or 'immunizes' information to reduce or eliminate risk of exploitation of a known vulnerabilty of a software service and includes receiving information () in response to a request, transforming the information () to produce transformed information and sending the transformed information (). An exemplary firewall server () includes server software () that allows the firewall server () to receive information from a resource () via a network and to send information to a client computer () and an immunization component () for immunizing the information to prevent exploitation of a vulnerabilty of browser software () on the client computer (). Various other exemplary methods, devices, systems, etc., are also disclosed.

Immunizing HTML browsers and extensions from known vulnerabilities

The described systems and methods are directed at managing networks using network templates. Each network template is associated with a different network topology and includes parameters for implementing the associated network topology. A user may implement a particular network topology by selecting a corresponding network template. A configurator may be used to configure a network device to implement the network topology associated with the selected network template based, at least in part, on the parameters.

Systems and methods for managing networks

Growing community of inventors

Tzrufa, Israel

Boaz Ein-Gil