Amazon Technologies, Inc.

Microsoft Technology Licensing, LLC

Mark Aran Aiken

Raghunathan Kothandaraman

Gurdeep Singh Pall

Dennis A Morgan

Gaurav Gupta

Rohan Mutagi

Adam Barry Fineberg

Roger Robert Webster

Stanislaw Ignacy Pasko

Olusanya Temitope Soyannwo

Ankit Kumar

Philip Alexander Lee

Makarand Damle

Vibhav Hemant Salgaonkar

Sasanka Rajaram

Deep Dixit

Dhaval Parmar

Galen Clyde Hunt

James R Larus

Manuel Alfred Fahndrich

Antonio Vargas Garcia

Chris Hawblitzel

Caglar Iskender

Milan Krneta

Sam L Nelson

Brandt Elster

Timothy Etters

Ryan O'Donnell

Adam DeLisse

A hub is configured to provide voice control without assistance from a remote system, which allows the hub to provide a user with the ability to control second devices in an environment by issuing voice commands, even when the hub is unable to communicate with the remote system over a wide area network (e.g., the Internet). The hub is also configured to execute rules without assistance from the remote system, which allows the hub to execute rules, even when the hub is unable to communicate with the remote system over a wide area network (e.g., the Internet).

Architecture for a hub configured to control a second device while a connection to a remote system is unavailable

Techniques for enabling entities to provide a system with data representing specific relationships of various endpoint devices for the purpose of responding to user inputs are described. A system may include an application program interface (API) that enables an entity to provide the system with data describing related endpoint devices, as well as data representing terminology that a user may use to refer to a specific endpoint device. After the system receives such data, when a user associates an endpoint device with their user profile, the system can associate that endpoint device with various other endpoint devices based on data previously received from an entity. When the system receives a user input, the system may traverse endpoint device relationships, represented in a user profile, to determine an endpoint device that should be invoked to respond to the user input.

Endpoint device relationships in processing user inputs

Disclosed are various embodiments for intelligent backfill and data migration operations performed using an event processing architecture. A backfill system may identify backfill operations to migrate legacy data from a first system to a second system and generate events to provide to an event processor, where each of the events causes a backfill operation to be performed. Access to the events may be selectively controlled using an event processing queue such that the events are processed and the backfill operations are performed when a computing resource has available computing resources, regardless of a time of day.

Intelligent data backfill and migration operations utilizing event processing architecture

Disclosed are various embodiments for monitoring software computations of potentially arbitrary length and duration for event processing and related systems. A pattern of events describing user interaction with a client application or a network site may be received, where a virtual process is generated to match events received from various computing resources to the pattern. A self-healing watchdog process may be generated that, after a period of time, periodically checks a state of the virtual process relative to matching the pattern of events. Any detected anomalies may be stored in a delay queue and returned to the watchdog process after a period of time.

Monitoring software computations of arbitrary length and duration

Disclosed are various embodiments for filters and event schema for categorizing and processing streaming event data. An event may be generated by a service that describes user interaction a client application executable on a client device. The event may be received as a data structure in a first format. A filter, such as a regular expression filter, may be applied to the data structure to identify an event type for the event. The data structure may be converted from the first format to a second format in accordance with a common event schema able to be interpreted by virtual compute engines.

Filters and event schema for categorizing and processing streaming event data

Disclosed are various embodiments for event processing architecture for real-time user engagement. Events that describe user interactions with client applications are analyzed in real-time when received in a data stream. The events are compared to patterns specified, for example, by administrators. If a pattern is matched based on a comparison to events received in the data stream, a predetermined action may be performed. The processing of events may be performed by a compute engine, which may include a virtual machine or a thread implemented in a parallel computing arrangement.

Event processing architecture for real-time member engagement

A first plurality of operating system processes is assigned to a first protection domain, and a second plurality of operating system processes is assigned to a second protection domain. One or more hardware protection mechanisms are used to prevent the first plurality of operating system processes from accessing the memory space of the second plurality of operating system processes, and also to prevent the second plurality of operating system processes from accessing the memory space of the first plurality of operating system processes.

Process isolation using protection domains

A software network bridge which allows connected network segments to be presented as a single network unit to the host computer. The software bridge can be implemented as an intermediate network driver, abstracting multiple network segments into a single network interface for higher level protocols and applications. The intermediate network driver can simultaneously send the same data packet through multiple network interfaces by creating multiple packet descriptors, each pointing to the same data, but each given individually to the underlying network interfaces to control during their transmission.

Exposing a bridged network as a single virtual segment

A software network bridge is disclosed which allows the connected network segments to be presented as a single network unit to the host computer. The software bridge can be implemented as an intermediate network driver, abstracting multiple network segments into a single network interface for higher level protocols and applications. While the intermediate network driver acts as a software bridge implementing the Spanning Tree Algorithm, it also acts a network interface driver to higher level protocols, conglomerating information from the multiple underlying network interface cards and forwarding along commands from the higher level software to the appropriate network interface card. The intermediate network driver can also simultaneously send the same data packet through multiple network interfaces by creating multiple packet descriptors, each pointing to the same data, but each given individually to the underlying network interfaces to control during their transmission. Further efficiencies can also be achieved by the software bridge, implemented as an intermediate network driver, through the use of a dynamic allocation scheme which increases the size of the useable buffers of each network interface without increasing the overall memory consumption, and the use of a queuing scheme which preliminarily examines incoming data packets to determine if any processing needs to be performed, and queues the packets should they require processing. Additionally, a user interface is presented exposing this functionality of the intermediate network driver.

Bridging multiple network segments and exposing the multiple network segments as a single network to a higher level networking software on a bridging computing device

Exposing multiple network interfaces as a single network interface to a higher level networking software

A method and system allows nodes on different segments to communicate with one another as if they were on a single segment. In one implementation, an intermediate computer linked in communication with the different segments relays data between the nodes and selectively substitutes the hardware addresses of its own network interface cards for the hardware addresses of the nodes themselves. The nodes are then able to communicate with one another using hardware addresses of the intermediate computer while still using their own network addresses.

Method and system for facilitating communication between nodes on different segments of a network

A dynamic resource allocation scheme is disclosed which allows flexibility in granting resources to a requestor, while maintaining a safety buffer should other requesters need resources. A portion of available resources are declared to be a &ldquo;safety buffer&rdquo;, and all of the available resources are divided amongst the requesters. The resulting divisions are each requestors &ldquo;fair share&rdquo;. A requestor is granted resources so long as their resource usage is less than their fair share and so long as there are any available resources. A requestor is also granted resources, even if they are currently exceeding their fair share if the available resources exceed the safety buffer. The application of these two rules results in a dynamic resource allocation scheme which decreases the number of times a request is denied without unfairly limiting the access to resources by other requesters.

Growing community of inventors

Seattle, WA, United States of America

Mark Aran Aiken