Amazon Technologies, Inc.

Tristam Kyle MacDonald

Christoph Saalfeld

Alexandra Elizabeth Baoboe Lee

Shyam Krishnamoorthy

Justin Robert Knoepfler

Bryant Cutler

Calvin Yue-Ren Kuo

Kyle Michael Roche

Gary Keith Wicker

Aditya Bhalla

Frank Lovecchio

Qing Ju

James Christopher Sorenson

David Craig Yanacek

Jonathan I Turow

Andrew Dean Christian

Sudarshan Anand Chitre

Yadunandan Parthasarathy

Josh Pearl

Jennifer Nicole Loomis

Dinkar Pataballa

Donald Gillespie

A technology is described for modifying a message frequency of a device. In one example, a network connection is identified between a device and a service provider environment. A message frequency is set for which to send reachability messages between the device and the service provider environment to maintain the network connection. The reachability messages may be sent between the device and the service provider environment at the message frequency. After testing whether the networking connection is maintained at the message frequency, the message frequency may be modified to a modified message frequency.

Message frequency modification for connection maintenance

A socket service may be used to link a peer socket to another peer socket. The peer socket is for communicating data to and from a client device and the other peer socket is for communicating data to and from another client device. If a socket opens and the corresponding peer socket is not yet open then the socket waits for the corresponding peer socket to open. When a client device requests a socket to be opened, the client device requests a particular client-defined function mapping to be associated with the socket. When the socket is opened, the endpoint specified in the client-defined function mapping is invoked. An identifier associated with the client device is sent to the endpoint. If the endpoint returns a socket identifier for another socket, then the socket service links the peer socket to the other peer socket, linking the client device to another client device.

Socket peering

Compute hosts and a routing system may be used for connection and application state migration for uninterrupted service availability. In response to an indication to transfer a connection from a particular compute host to another compute host, the particular compute host obtains a connection state and an application state for the connection and sends the connection state and the application state to the other compute host. The connection state includes information for a connection-oriented protocol and the application state includes information for an application-layer protocol. The other compute host receives and applies the connection state and the application state in order to establish a termination point to terminate the connection at the other compute host instead of at the particular compute host. The data for the connection is routed to the other compute host, wherein the client is unaware of transfer of the connection to the other compute host.

Connection and application state migration for uninterrupted service availability

A socket service may be used to implement client-defined function mappings (e.g., custom protocols) for sockets hosted by the socket service so that when a particular socket is opened for a particular client device, the socket operates according to a particular client-defined function mapping requested by the particular client device. To establish a particular client-defined function mapping, a socket manager may receive request from a user that specifies a particular endpoint (e.g., a client-registered function). When a client device requests a socket to be opened, the client device requests the particular client-defined function mapping to be associated with the socket. When the socket is opened, the endpoint is invoked. The particular client-defined function mapping may also specify one or more receive criteria for data received at the socket. If the one or more receive criteria is met, the endpoint is invoked by sending the data to the endpoint.

Managed secure sockets

Technology is described for migrating connections for Internet of Things (IoT) devices. Data packets may be received from an IoT device for forwarding to a first physical host in a computing service environment. A determination to migrate the connection for the IoT device from the first physical host to a second physical host in the computing service environment may be performed when a throughput of the data packets received from the IoT device for the first physical host exceeds a defined threshold. A connection migration procedure may be initiated to migrate the connection for the IoT device from the first physical host to the second physical host. The connection migration procedure may include an exchange of session state information for the IoT device from the first physical host to the second physical host to enable the migration of the connection to the second physical host.

Connection migration for Internet of Things (IoT) devices

A WiFi-enabled user device charger is disclosed that may include a processor, a WiFi antenna, a connector for receiving power, a user device charging and data transmission connector, and a memory storing computer-executable instructions configuring the processor to connect to a server using the WiFi antenna to fetch data; queue a portion of the data to transfer to the user device; determine that the user device is connected to the WiFi-enabled user device charger; transmit at least a portion of the data to the user device using the device charging and data transmission connector; and transfer power to the user device using the device charging and data transmission connector. The WiFi-enabled user device charger may not provide any functionality that is not related to charging the user device or transferring data between the user device and the server.

Network-enabled user device charger

Growing community of inventors

Boston, MA, United States of America

Tristam Kyle MacDonald